Work Flow Process Upon Releasing Transport Request In ERMS 1.

Maintain approver group id and email address in custom table T9B32 in both DEV and TCC use transaction code SM30

Click button

to enter the values

2. Release Transport Request in DEV using transaction code SE09/SE10

Case: Without Notify Approver a. Release the TR

b. Below pop up window is displayed

c. Click on search help button displayed

and listing of the approver group id is

d. If choose invalid entry of the approver group id, below error message will be displayed. Eg: Approver Group ID = 03

Below error message is displayed

If click on button , the TR is not release and message will be displayed on bottom of the screen.

Note: The TR only can be released if enter valid approver group id which is maintained in custom table T9B32

e. Choose the valid entry and click on button

The TR is released and will get below screen

Below message is displayed on below of the screen

3. Release Transport Request in DEV using transaction code SE09/SE10

Case: With Notify Approver a. Release the TR

b. Below pop up window is displayed

c. Click on search help button displayed

and listing of the approver group id is

d. Tick check box Notify Approver. Button are automatically enabled.

and button

e. Option Additional TR

This button is to allow user notify approver to approve more than 1 transport request if any If there is only 1 transport request pending for approval under the approver group id and the owner, below warning message is displayed and user is not allow to proceed.

Otherwise, below screen is displayed.

Tick which TR that needs to be notified to the approver and enter the sequence number ( 1-99 ) of the TR as well if any. Otherwise, leave it blank.

Click on button cancel the process.

if you confirm the TR or click on button

to

f. Option Add Comments

This button is to allow user put extra comments on the email body if any up to 3 lines

Sample comments:

Click on button body.

is confirm with the changes or click on button

to cancel. If cancel, there will be no comments put in the emails

g. Below pop up window is displayed and click on button

to proceed.

If the selected approver group id doesnt have email address, below message is displayed.

The TR cannot be released unless the email address is maintained or uncheck the check box Notify Approver. h. If there is no error display, the TR is released and below screen is displayed

Below message is displayed on below of the screen to notify that the email has been sent to the selected approver group id.

i.

Below is the email that sent To the all approver under the same approver group id and CC the requestor

4. List of files captured in directory /usr/sap/trans/bin/zbstms which is stored text files that involved in the workflow Store all the transport requests that has been released: erms_master_pending_tr.txt

5. Approver transport the TR a. Login to staging

b. Go to transaction code ZBSTMS i. Below list is automatically displayed shows that list of TR needs to be transported to TCC by the approver

ii. Tick which TR that wants to be transported and click on button

Note: Basically the program will set the requestors email address by using the TRs owner. Eg:Owner = 28425 Email address = 10028425@tnb.com.my But there is case whereby the TRs owner is not TNBs staff eg: Consultant/Vendor, therefore the approver must maintain manually the requestors email address first before click on button Click on button address to maintain the requestors email address up to 3 email

Sample requestors email address entered

Click on button Click on button

to proceed or button

to cancel the process.

and below confirmation box is displayed.

If click on button Yes, the TR is transported to TCC and email is automatically sent

iii.

Below is the email sent out after the TR transported to TCC To the requestor and CC the approver

iv.

Below are the list of file that has been updated during the transporting process in directory /usr/sap/trans/bin/zbstms

1. erms_complete_tr.txt store all the TR has been transported to TCC on that day 2. erms_master_complete_tr.txt store all the TR has been transported to TCC

v.

Run again transaction code ZBSTMS. The TR that has been transported to TCC before is not in the list anymore.

6. Approver Re-transport TR. a. Run transaction code ZBSTMS b. Click on button

c. Below screen is displayed. Enter the TR number.

The program will check the TR number against TR list in file erms_master_complete_tr.txt in directory /usr/sap/trans/bin/zbstms. If the TR doesnt exist, below error message will be displayed.

Enter the valid TR number

Press Enter and details of the TR will be displayed on the screen as shown below. If you have more than 1 TR to re-transport, enter the other TR number on the next line and press Enter. If there is sequence of the TR, enter the sequence number from 1-99. The program will re-transport the TR based on the sequence number given. Otherwise, it will re-transport based on the TR entered on the screen.

Click on button button

to re-transport the entered TR. Otherwise, click on to cancel the process.

If you click on button , below message will be displayed on bottom of the screen which means the TR is being transporting.

Once done, the TR number will be inserted on the screen as shown below and email is automatically sent out.

Email is sent out To the requestor and CC to the approver

d. If try to re-transport TR that already in the screen list as shown below, error message will be displayed.

Additional program Program: ZEBSH002 Purpose: To clean up master pending TR in directory /usr/sap/trans/bin/zbstms Process: 1. Get file erms_master_pending_tr.txt 2. Get file erms_complete_tr.txt 3. Delete TR in file erms_master_pending_tr.txt if TR number exist in file erms_complete_tr.txt 4. Delete file erms_complete_tr.txt

Note: This program must be scheduled at midnight everyday in DEV. This program doesnt have to transport to TCC.