Discuss business intelligence, integration, compliance and a host of other SAP-related topics – implementation, best practices and resources to negotiate the world of SAP better!

« BSI TUBS for US Payroll taxes - Tips and Tricks & Best Practices | Main | Bitcoins - should we care? »

HR -LCP's Year End Process User Guide

Monitor - bi-weekly

a)      Monitor SAP website  bi-weekly https://websmp205.sap-ag.de/patches to determine if notes available SAP Component (verify system component level in production) and download or print appropriate notes  and review

b)      Coordinator will schedule recurring monthly meeting to discuss if  SAP notes for the same is available and the relative  support pack level which needs to be attained  for each component.

c)      If notes  are available Coordinator will schedule meeting with Basis and Testing teams  and submit a Change control board Engagement form for a Project Creation for the LCP's.

d)     SAP Component Leads will create a charm document for manual corrections

 

Support Pack, Patches, and Legal Change Pack Process

 

 

 

1)      Monitor - bi-weekly

a)      Monitor SAP website  bi-weekly https://websmp205.sap-ag.de/patches to determine if notes available SAP Component (verify system component level in production) and download or print appropriate notes  and review

b)      Coordinator will schedule recurring monthly meeting to discuss if  SAP notes for the same is available and the relative  support pack level which needs to be attained  for each component.

c)      If notes  are available Coordinator will schedule meeting with Basis and Testing teams  and submit a Change control board Engagement form for a Project Creation for the LCP's.

d)     SAP Component Leads will create a charm document for manual corrections

 

2)      Schedule - Based on Production Release Timeline

a)      Coordinator of SAP changes - set-up meeting with Basis and Testing team to discuss corresponding SAP Notes for each component levels to apply, predefined dates for transporting into various environments, and testing

b)      Send e-mail to Basis, Testing team  and SAP Component Leads providing the calendar. Information to be assimilated to  others within your group that are required to assist with reviewing, testing information for scenarios, testing, and defect fixes

3)      Review and Testing information

a)      Review notes by designated date

b)      If determined testing required - Provide the detailed information for the impacted Functionality on the SAP notes  to T  in a summarized document .

i)        Separate spreadsheet for each component:

(1)   Note Number

(2)   Note title

(3)   Analyst Name

(4)   Provide  detailed testing information

4)      Testing Team  - Test Scenario creation

(1)   Testing team  to create new positive /negative test scenarios and also regression test scenarios  based on information provided

(2)   New script reviewed and approved by SME (Subject Matter expert)

5)      Testing - In Quality client

a)      Testing team   to test in Quality  client  based on established scenarios and test cases  and new scenarios provided by designated date mentioned as per project calender.

b)      Each team for each SAP component is responsible for testing  any notes or programs that Testing team does not have a current valid scenario available

6)      Defects

a)      Defects for any errors will be raised by Testing team

b)      Defects are sent to the SAP Component Lead to assign for appropriate action (fixing the configuration/code)  within their group .

c)      Analyst will review, and/or fix, provide feedback to Testing team so that it can taken up for further retest.

d)     Mandatory - All pending defects needs to be in  fixed state  and then subsequently retested and closed by testing team  in QC before notes are approved and moved to production

7)      SPAU and SPDD  Adjustments  

a)      Completed by designated programmer

8)      Move to production

a)      Once all testing has been completed transports are moved to Production based on the production rail release scheduled date.

 

Post a comment

(If you haven't left a comment here before, you may need to be approved by the site owner before your comment will appear. Until then, it won't appear on the entry. Thanks for waiting.)

Please key in the two words you see in the box to validate your identity as an authentic user and reduce spam.

Subscribe to this blog's feed

Follow us on

Blogger Profiles

Infosys on Twitter