cancel
Showing results for 
Search instead for 
Did you mean: 

SRM 7.02 Supplier Enablement & Supplier Portal - Need Urgent Help !

Former Member
0 Kudos

Hi Folks again,

I also need general information about customizing steps for SRM-SUS Scenario and Supplier Enablement Logic urgently.

Could you give me detail information or documents/links for customizing SUS ??


Also I have checked the customizing steps, for SUS there are different document types as I painted in yellow.

How can I configure this document types for creating by any vendors in the supplier portal??


Another question, should the SUS logic (portal) be configured in different client on the SRM server or can we configure the SUS in same client already?

What will be the pros&cons of configuring SUS in same client/diffrent client??



Thanks in advance.

Dolunay

Accepted Solutions (0)

Answers (1)

Answers (1)

vinita_kasliwal
Active Contributor
0 Kudos

Hi Dolunay

Customizing step for SAP SUS should be available in solman or you can check in service market place

However the below link and information would be helpful as a first hand information .

SUS is part of SRM. If you install SRM, you should have SUS also. Typically SUS is configured in its own client.

Can I implement EBP, SUS in the same system and same client ?

As of release SRM4.0, you can have both EBP and SUS in the same system.  You can also run both EBP and SUS both in the one client of the same system. However, SAP recommends this only for test and demo systems.  SAP recommends separate clients for purchasing application (EBP) and Supplier Application (SUS).  Please refer note 573383 for more details.  

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

http://wiki.scn.sap.com/wiki/display/SRM/Interfaces+used+in+the+SRM-SUS+scenario

http://wiki.scn.sap.com/wiki/display/SRM/Overview+of+the+SUS+scenarios+and+interfaces+used

http://help.sap.com/saphelp_srm50/helpdata/en/06/0f343e47fd6b2ee10000000a114084/frameset.htm

SAP Note  573383 EBP and SUS  implementation  in the same client

SAP Note: 543544   SUS: Extended Classic Scenario for EBP not supported

SAP Note: 1403475  Consulting service: Functional enhancement in SAP SRM

Let me know if this helps .

Regards

vinita

Former Member
0 Kudos

Hi Vinita,

Thanks a lot for your answer. I will check the documentation in service marketplace.

But I understood that we can't do this implementation without SAP PI module (so-called XI also) and SAP recommends that we must set the SUS side to different client.

By the way, I will use extended-classic scenario in SRM side (process starts with SC on SRM side, than PO and GR will be created in SRM side also but PO will transfer to the ECC side after approvals)

and I need to set the SUS client for receiving PO Responses from Suppliers.

Maybe I should set the implementation that let the suppliers to make the GR for the PO afterwards.

Keep in touch, I will inform you about the news.

Regards,

Dolunay

robin_janke
Contributor
0 Kudos

Hi,

PI is mandatory for the purchase order/purchase order response in the SUS scenario. RFx/BID is point to point enabled and can be done without PI.

Regards,

Robin