Transport Application Changes

Hindustan Unilever Limited Confidential Basis Helpdesk Manual

© Hindustan Unilever Limited - PROPRIETARY Information December 2007 For use exclusively by HUL employees and approved associates. 1

CRM_DNO_MONITOR-Transports to Quality/Production 1.0 Description

Changes to the SAP applications are carried out in the Development Landscape, transported and tested for quality in the Quality Landscape before they are transported to the Production Landscape of SAP. The changes are tracked and made available for transport to Quality and Production stages using SAP Solution Manager. Through the Solution Manager, the SAP BASIS support team (responsible for carrying out the transports) receives an email alert. Depending on the nature of email (Transport to Quality or Transport to Production), appropriate workflows are considered.

1.1 Transport to Quality, 1.1.1 As and when the mail pertaining to transport to quality is received, the activities pertaining to

the transport are carried out by the BASIS support team. 1.2 Transport to Production,

1.2.1 As and when the email pertaining to transport to production is received, it is automatically forwarded (using Outlook facility) to the GATE control team of IT-SOX (HUL, IT-SAP).

1.2.2 The GATE control team of IT-SOX reviews and confirms that the transport request is in tune with HUL Program Change Management Security Policies and conveys its “approval” or “instruction to hold” as the case may be through email to the BASIS support team.

1.2.3 On receipt of approval, the BASIS support team carries out the Transport to Production activity.

1.2.4 In cases of emergency, based on verbal/telephonic approval by the GATE control team of IT-SOX, the BASIS support team carries out the transport activity for specific requests. However, formal approval is sought by the BASIS support team.

2.0 Schedule of Authority

2.1 Gate Control Team Leader of IT-SOX 2.2 L1 Team Lead. 2.3 L2 Team Lead and HUL Basis Manager 2.4 HUL Basis Project Manager

3.0 Prerequisites

3.1 Appropriate CRM_DNO_MONITOR authorization under SAP Solution Manager.



4.0 Process Flow Diagram





5.0 Task Overview & Issue Escalation Matrix

Step No Activity Description Responsibility Escalation (if any) Escalation Window

6.1 Check email for receipt of Transport to Quality requests

Identified L1 Team member L1 Team Lead N/A

6.2 Transport to Quality Identified L1 Team member L1 Team Lead 4 hours

6.3 Check email for receipt of approved Transport to Production requests

Identified L1 Team member L1 Team Lead N/A

6.4 Transport to Production Identified L1 Team member L1 Team Lead 4 hours



6.0 Processing Steps

6.1 Check email for receipt of Transport to Quality requests

6.1.1 Check the Outlook mailbox for any Quality Transport mails that are pending for action. For checking, look for the mails received from Solution Manager’s workflow with the subject line “Urgent Correction <Change No.> - Being developed”.

6.1.2 If found,

6.1.2.1 Note the Change No. mentioned in the Subject line.

6.1.2.2 Review the General Note and if mentioned, note the Processor’s identity for testing.

6.1.2.3 Perform 6.2 Transports to Quality.

6.1.3 Repeat 6.1.1 to 6.1.2.3 until all the pending requests for transport to quality are completed.



6.2 Transport to Quality

6.2.1 Login to the SAP Solution Manager module and initiate CRM_DNO_MONITOR. Enter the Change No. under the “Transaction No.” field of the Service Process screen segment (noted in step 6.1.2.1) and click on Execute button. In the example given below, the Change No. entered is 48185.

6.2.2 In the resulting display, for the change no. concerned, note the name under Person Responsible. If the processor’s identity has not been mentioned in the general note, obtain the same from the person responsible. Ensure that the Status is In Development.



6.2.3 Double click on the row pertaining to the Change No. In the resulting display, ensure that the status is In Development and click on the Change button.

6.2.4 Enter the Processor’s identity (obtained in step 6.1.2.2 or 6.2.2) in the Current Processor box and click on the Action dropdown button. In the example, the Current Processor has been changed to 932.

6.2.5 Choose the Pass Correction to Test option and click on the Save button.



6.2.6 Import target/s will be displayed. By clicking on the Enter button, confirm the starting of the import. Wait for the import to be completed.

6.2.7 After the completion of import, click on the Action button and choose the Go to Task Plan option.



6.2.8 In the displayed task plan, under Target Systems, Quality Assurance System … tree item, select the Display TMS Import History and choose Execute option.

6.2.9 In the resulting display, locate the change no. for which the transport was carried out. Under the RC column of the display, check the color of the shape display against the change no.



6.2.9.1 If the color of the shape under the RC column is RED,

6.2.9.1.1 Double click on the row concerned and obtain screenshot of the error log.

6.2.9.1.2 In addition to the automatic email alert sent by Solution Manager, send email intimation along with the screenshot of the log to the email id of the person responsible for the change (noted in step 6.2.2).

6.2.9.2 If the color of the shape under the RC column is other than red (Green-Transported without Warnings/Errors, Yellow-Transported with warnings), no further action is required as Solution Manager sends an automatic email alert.



6.3 Check email for receipt of approved Transport to Production requests

6.3.1 Check the Outlook mailbox for any Production Transport mails that are pending for action. For checking, look for the mails received from HUL, IT-SAP with the subject line “RE: Urgent Correction <Change No.> - Released for Import”.

6.3.2 If found,

6.3.2.1 Note the Change No. mentioned in the Subject line.

6.3.2.2 Perform 6.4 Transports to Production.

6.3.3 Repeat 6.3.1 to 6.3.2.2 until all the pending requests for transport to production are completed.



6.4 Transport to Production

6.4.1 Login to the SAP Solution Manager module and initiate CRM_DNO_MONITOR. Enter the Change No. under the “Transaction no” field of the Service Process screen segment (noted in step 6.3.2.1) and click on Execute button.

6.4.2 Double click on the row pertaining to the required Change no.

6.4.3 For the change no. concerned, note the name under Person Responsible column. Ensure that the Status is Authorized for Import and click on the Change button.



6.4.4 The Options button for the change will be display. Click on the Option button and choose the Import Correction to Production option and click on the Save button.

6.4.5 Import target/s will be displayed. By clicking on the Enter button, confirm the starting of the import. Wait for the import to be completed.



6.4.6 After the completion of import, click on the Option button and choose the Go to Task Plan option.

6.4.7 In the displayed task plan, under Production Systems tree item, select the Display TMS Import History and choose Execute option.



6.4.8 In the displayed screen, locate the change no. for which the transport was carried out. Under the RC column of the display, check the color of the shape display against the change no.

6.4.8.1 If the color of the shape under the RC column is RED,



6.4.8.1.1 Double click on the row concerned and obtain screenshot of the error log.

6.4.8.1.2 In addition to the automatic email alert sent by Solution Manager, send email intimation along with the screenshot of the log to the email id of the person responsible for the change (noted in step 6.4.3).

6.4.8.2 If the color of the shape under the RC column is other than red (Green-Transported without Warnings/Errors, Yellow-Transported with warnings), no further action is required as Solution Manager sends an automatic email alert.



7.0 Templates & Formats

7.1 Weekly Report prepared by L1 team by using the details made available by Solution Manager.

8.0 Process Linkages - None

9.0 Data Record Management

9.1 Input(s) 9.1.1 Email Id used by Solution manager for communicating Transport to Production requests to

BASIS support team. 9.1.2 The string in the subject part of the email sent by Solution Manager. 9.1.3 Email Id used by the GATE control team (IT-SOX) for communication

9.2 Output(s) 9.2.1 Weekly Report prepared by L1 team by regarding the status of Transports to Production.

Documents

Transport Application Changes