This document will give you an overview about the document flow in the SRM-SUS and MM-SUS scenarios and about the interfaces used to transfer the documents between systems.
The XI content needed for the SUS scenarios can be found in the following content depending on your SRM_SERVER release:
SAP SRM SERVER 5.0
SAP SRM SERVER 5.5
SRM SERVER 7.0
SRM SERVER 7.01
SRM SERVER 7.02
SRM SERVER 7.13
SRM SERVER 7.14
Additionally to above content you will also need the XI content for SAP APPL depending on your SAP_APPL software version in the backend. The integration scenarios in the SRM enhancement packages are always synchronized with a specific ECC EHP because new interfaces required for new integration scenarios are not available in lower ECC EHPs. So SRM 700 is in sync with ECC 604, SRM 701 with ECC 605 and SRM 702 with ECC 606. The standard templates in the scenario builder always refer to the XI content according to above pairing. For example should you use SRM 701 with ECC 606, you will still be required to deploy the XI content for ECC 605 as well in order to display it in the configuration builder.
In this scenario the PO is always created in MM and transferred to SUS. According to your SRM and backend releases there are two possible solutions for this scenario.
1. Plan Driven Procurement Scenario
This scenario supports only material items. It uses IDOC interfaces on ECC side for all document types and XML interfaces on SUS side. A mapping between IDOC and XML will take place in the XI processing. The scenario can be used with all current SRM and ECC backend releases.
Name of the XI scenario used: Plan_Driven_Procurement_SupplierEnablement
2. Service Procurement Scenario
This scenario supports both material and service items. For the transfer of purchase orders and service confirmations ESOA XML messages are used on both ECC and SUS side. For all other document types it uses the same IDOC interfaces on ECC side and XML interfaces on SUS side as in the previous scenario. The scenario is supported as of SRM 7.0 in connection with an ECC 6.0 Ehp 4 backend or upwards.
Name of the XI scenario used: SE_Services_Procurement
For the SRM-SUS scenario the purchase order needs to be created in SRM and then transferred to SUS. This means from the three different SRM scenarios the local scenario must be used. The extended classic scenario is supported only partly, it is restricted to document types PO and PO response. Please also refer to note 543544 and note 1403475 to enable the scenario via a consulting solution. The classic scenario cannot be used with SRM-SUS, as in this case the PO is created in the ECC backend. Please consider the MM-SUS scenario for this case.
Name of the XI scenario used: Service_Procurement_SupplierEnablement
Related SAP Notes/KBAs
SAP Note: 543544 - SUS: Extended Classic Scenario for EBP not supported
SAP Note: 1403475 - Consulting service: Functional enhancement in SAP SRM