- SAP Managed Tags:
What is the requirement?
We implemented SRM 5 ECS for our client a long ago, it's been decided to implement Ariba Procurement and transform all of SRM functionalities to Ariba. PDP (MRP) scenario was one of those items.
Standard Ariba provides ways to incorporate this scenario via requisition import process. I would like to share with you our method so that it can be reused if you have to implement it for your client.
Design and Implementation
a. Create a new procurement profile as AR in T160PR
b. Create entries in T160EX table with AR procurement profile. With this setting, MRP PRs will make their way to EPRTRANS table.
c. Develop a report that will pick entries from EPRTRANS table and fetch corresponding records from EBAN table and then delete records in EPRTRANS table.
d. As Ariba requisition import task needs the requisition data in three files as shown below, we need to create three custom tables in SAP with matching fields.
e. These import task file formats are given by Ariba (export template from export task) and scope for custom fields (i.e. cus_StorageLocation.UniqueName) can be discussed with customer and incorporated in header, detail and accounting files as needed.
f. Aforesaid report must map the data in EBAN records to fit these tables and make entries. Among many fields, the header table will have two key fields, one is to mention whether it is new requisition or it contains updates to a requisition that is already sent to Ariba.
g. Other field is a flag that denotes whether the entry is sent to Ariba or yet to be sent, this will not be part of the zip file.
h. Develop a report that will fetch ‘to be sent’ records from all these tables and create a .zip file and put it in a destined path in SAP directory (AL11).
i. Folder must be exclusive to REQ import files only.
j. ITK script in PO (Process Orchestration) system will pick up the file and transfer it to Ariba and integration task will create requisitions on Ariba.
k. Schedule the reports as batch jobs.
Note: Requisition number in the header is the MRP requisition number. So when the corresponding Ariba requisition generates PO on Ariba and is sent to SAP, the SAP PO should be pointing at MRP requisition (EKPO-BANFN). It has to reflect in WSDL mapping sheet for PO creation/change/cancel.
Conclusion: As it is an asynchronous process, multiple requisitions can be sent at once. Requisition can also be sent to Ariba via webservice, you can explore the options and share it.
We implemented SRM 5 ECS for our client a long ago, it's been decided to implement Ariba Procurement and transform all of SRM functionalities to Ariba. PDP (MRP) scenario was one of those items.
Standard Ariba provides ways to incorporate this scenario via requisition import process. I would like to share with you our method so that it can be reused if you have to implement it for your client.
Design and Implementation
a. Create a new procurement profile as AR in T160PR
b. Create entries in T160EX table with AR procurement profile. With this setting, MRP PRs will make their way to EPRTRANS table.
c. Develop a report that will pick entries from EPRTRANS table and fetch corresponding records from EBAN table and then delete records in EPRTRANS table.
d. As Ariba requisition import task needs the requisition data in three files as shown below, we need to create three custom tables in SAP with matching fields.
e. These import task file formats are given by Ariba (export template from export task) and scope for custom fields (i.e. cus_StorageLocation.UniqueName) can be discussed with customer and incorporated in header, detail and accounting files as needed.
f. Aforesaid report must map the data in EBAN records to fit these tables and make entries. Among many fields, the header table will have two key fields, one is to mention whether it is new requisition or it contains updates to a requisition that is already sent to Ariba.
g. Other field is a flag that denotes whether the entry is sent to Ariba or yet to be sent, this will not be part of the zip file.
h. Develop a report that will fetch ‘to be sent’ records from all these tables and create a .zip file and put it in a destined path in SAP directory (AL11).
i. Folder must be exclusive to REQ import files only.
j. ITK script in PO (Process Orchestration) system will pick up the file and transfer it to Ariba and integration task will create requisitions on Ariba.
k. Schedule the reports as batch jobs.
Note: Requisition number in the header is the MRP requisition number. So when the corresponding Ariba requisition generates PO on Ariba and is sent to SAP, the SAP PO should be pointing at MRP requisition (EKPO-BANFN). It has to reflect in WSDL mapping sheet for PO creation/change/cancel.
Conclusion: As it is an asynchronous process, multiple requisitions can be sent at once. Requisition can also be sent to Ariba via webservice, you can explore the options and share it.
1 Comment
