Hi Experts,
Need advise on SAP SLC (Supplier Life Cycle Management) Deployment Scenario :
Background – The scope of this project does not have SAP Back end (ECC). Hence Standalone scenario was recommended in order to cover PO process, Contracts, Suppliers areas. All of PO and Supplier Data will be pushed to 12+ ERP systems via interfaces and majority of PO creation would occur via Interface Feed from PLM (Siemens).
We have made few decisions based on ToBe landscape and business processes but would like to get feedback from you Experts.
- 1. SLC (Supplier Life Cycle Mgmt) will be used for on-boarding Supplier and Portfolio Management of suppliers –(Buy and Sell side). The question is concerning the Supplier Life Cycle Management servers and Deployment requirements.
Integrated Deployment – SLC Buy side as Add-on on SRM and SLC Sell side on SUS component which is part of SAP SRM Standard offering.
Our Recommendation– Since there is no SUS (Supplier Self Services) in scope, we recommend SLC Hub scenario where both Buy and Sell side clients will reside on single server (separate from SRM server) per environment (Dev/QA/Prod). Buy and Sell side clients will exchange via RFC and so does between Buy side and SRM.
- 2. SAP recommended 2 Enterprise Portals for SLC Sell and Buy Side. Although we are aware of dual EP usage, we recommended 1 EP for both Sell and Buy side of SLC. Firewall, Secured connection and security Roles will restrict External users into Lear.
- 3. SRM will be used for Direct Procurement without ECC Backend. Hence we came up with “Standalone Deployment Scenario” where SRM will house the PO, and will be distributed to SAP and non-SAP systems via TIBCO (middleware).
- 4. SAP SRM will host Master Data such as Plant, and receive other master data such as Part master, Prod categories, and suppliers from SRM.
Kindly Advise.