Create SUS Scenario For Services 1

END USER MANUAL

SAP SRM Create SUS Scenario For Services

Version No. 1.1

Document Status

Draft

In Review

Final

Document Owner(s) FEWA

Document Author(s) Amal Raj

Functional Area Supplier Relationship

Management / SRM

Document Contributor

Name Role

Amal Raj Application & Business Analyst

Document Approver

Name Role

Surendar Boora Enterprise Architect Manager

HCM Payroll Reports 2

Table of Contents

1 Execution Instruction ................................................................................................ Error! Bookmark not defined.

1.1. Flow Diagram for MM-SUS Cycle .......................................................................... Error! Bookmark not defined.

1.2. Creating a Purchase Order ........................................................................................ Error! Bookmark not defined.

1.3. Release the Purchase Order in ME29N .................................................................... Error! Bookmark not defined.

1.4. SUS System Login ..................................................................................................................................................... 3

1.5. MM-SUS CYCLE FOR SERVICES PURCHASE ORDER ..................................................................................... 3

1.6. Check the Service Entry Sheet in ECC- MM in ME23N (Purchase Order History) ................................................. 8

1.7. Release the Service Entry Sheet against the above Purchase Order in ML81N ........................................................ 8

1.8. SUS System Login ..................................................................................................................................................... 9

1.9. MM-SUS CYCLE ..................................................................................................................................................... 9

1.10. Check the Parked Invoice in ECC-MM in MIR7 .................................................................................................... 13

2 Appendices .............................................................................................................................................................. 15

Create SUS Scenario For Services 3

1.1. SUS System Login

Below Web Browsers are compatible for MM-SUS Scenario

Ensure Correct URL to login .

http://webportal.fewa.gov.ae:8040/sap/bc/nwbc

Enter User ID and Password

1.2. MM-SUS CYCLE FOR SERVICES PURCHASE ORDER

1.2.1. Check the Purchase Order Created in SUS as Sales Order A Purchase Order released by FEWA to SUS Vendor will immediately be available to the vendor for

processing.

The Vendor can access FEWA’s Purchase Order as shown below.

Click on the Tab

Create SUS Scenario For Services 4

Select the Purchase Order sent by FEWA.

To see the document in a larger screen by hiding the search column, please click on the as shown

Create SUS Scenario For Services 5

Click on to see the printout of business document

1.2.2. Create Confirmation The first step for vendor in the MM-SUS for services is to create a confirmation of services.

Create SUS Scenario For Services 6

Scenario 1: Create Confirmation for the complete Open quantity of Purchase Order.

For this click on and . The Outlines and the service lines are all selected and

their open (outstanding) quantities are proposed by the system.

Click to update the price for the proposed quantity. Whenever the quantity is modified please

make a note to click on the “Update Prices” to change the net value for the new quantity.

1 2

Create SUS Scenario For Services 7

Scenario 1: Create Confirmation for the partial quantity or partial lines

Vendor also has an option to create confirmation for partial quantity / partial lines. For this Vendor can click

on the selected line item quantity and change / enter it directly.

Click on

The Confirmation which is created can be printed out.

1

2

Create SUS Scenario For Services 8

1.3. Check the Service Entry Sheet in ECC- MM in ME23N (Purchase Order History) The confirmation created by SUS Vendor is automatically updated in the relevant Purchase Order. The same is visible in the Confirmation tab of the each line item.

1.4. Release the Service Entry Sheet against the above Purchase Order in ML81N

The Confirmation created by SUS vendor needs to be accepted by FEWA. Without which the Vendor will not

be able to create invoice.

In T code ML81N enter the Service Entry sheet number and click on change.

Create SUS Scenario For Services 9

After Accepting, save the document.

Important Note: The service note can either be accepted by clicking or rejected by clicking . On

rejection, the Vendor will have to create one more service entry sheet and submit again.

1.5. SUS System Login

Please make sure to use the Web Browsers or

Ensure Correct URL to login .

http://webportal.fewa.gov.ae:8080/sap/bc/nwbc

Enter User ID and Password

1.6. MM-SUS CYCLE

1.6.1. Check the Confirmation acceptance posted in SUS. The below screenshots show the steps to accepted confirmation and create invoice.

Click on the tab Purchase Orders.

Create SUS Scenario For Services 10

Click on the require purchase orders from the list.

Click on

Create SUS Scenario For Services 11

Select Confirmation

The accepted Confirmation can be printed out if required.

Create SUS Scenario For Services 12

1.6.2. Create Invoice

The Vendor can create invoice for each accepted confirmation by clicking

Click on and then click on

1 2

Create SUS Scenario For Services 13

1.7. Check the Parked Invoice in ECC-MM in MIR7

The incoming SUS Invoice is always parked in SAP MM system. The same is updated in ME33k in “PO History”

Select line item as okay.

Create SUS Scenario For Services 14

1.7.1. SUS invoice

The SUS invoice is updated with status as “Accepted by Customer”

After the payment is made using T – Code F-53, the status is updated in SUS system by clicking

on

Create SUS Scenario For Services 15

Documentation References This section provides a list of the related documents that were referenced in this document. The table below

includes the document reference and name, the related BBP/ Re-engineering that reference the document, and

the path to the location of the document referenced.

Document Document Name Document Path

1 Appendices