CPPR is an MM functionality used to directly transfer backend PR manually into SRM for external

sourcing. It covers the same function as MM function Assign and Process Purchase Requisitions
(transaction ME57

When buyer decides to create an RFx for particular PRs that does not satisfy BAdI logic. In that scenario
buyer just uses CPPR functionality for further actions in SRM. Also when business does not want to
transfer requirements automatically to SRM, then PDP is not required and buyers would use CPPR
function for sourcing activities

CPPR Configeration SAP Note 1263876.

The BAdI which is used for linkage is ME_REQ_SOURCING_CUST.

Method 1: IF_EX_ME_REQ_SOURCE_CUST~ACTIVE:
Here, three output parameters need to be set to true. By default, coding from the sample class
will be copied. There is no need to modify anything here.

 When the parameter CV_AUT_SOURCING is set to true, external sourcing (e.g. SAP
SRM system) is active in SAP ERP system,
 When the parameter CV_EXT_RFX_IND is set to true, RFx can be created out of PR
directly from SAP ERP system using application CPPR,
 When the parameter CV_EXT_SC_IND is set to true, PR in SAP ERP system will be
transferred to SAP SRM using application CPPR.

Method 2: IF_EX_ME_REQ_SOURCE_CUST~CHECK_EXTERNAL_SOURCE:

 This method has output parameter CV_EXT_SOURCING. When the output parameter
variables are set, the Purchase Request will be transferred to SAP SRM without any
manual interaction in Collaborative Processing of Purchase Requisition (CPPR). Hence
the code logic here needs to be adopted based on parameters in the Purchase Request
(e.g. Material Group and Purchasing Group can be used as parameters to determine the
Purchase Request to be transferred to SAP SRM).

Activate event type linkages for external sourcing:

1. Run transaction SWETYPV in SAP ERP system.

2. Ensure that the following entries are present:

BOR Object Type BUS2105 RFXREQUESTED WS53800009 No errors

BOR Object Type BUS2105 SOURCINGREQUESTED WS53800009 No errors

3. If they are not present, then copy the entry for event Created for object type
BUS2105 and Receiver Type WS53800009 and change the event name.
1. Define ECC setting

a) Create Business system in ECC SLD. Perform SLDCHECK to cross-check setup.

b) Goto tcode SXMB_ADM >> Configuration >> Integration Engine Configuration

Select role of Business system as “LOC Application System”. Also provide relevant Integration
server path.

c) Perform Check in SXMB_ADM

2. Define PI setting
Setup interfaces “RFQRequestSUITERequest_Out” , “RFQRequestSUITERequest_In”,
“RFQRequestSUITEConfirmation_Out” and “RFQRequestSUITEConfirmation_In”

RFQRequestSUITE:

RFQRequestSUITEConfirmation:

3. Define SRM setting

a) Create Business system in SRM SLD. Perform SLDCHECK to cross-check setup.

b) Goto tcode SXMB_ADM >> Configuration >> Integration Engine Configuration

Select role of Business system as “LOC Application System”. Also provide relevant Integration
server path.

c) Provide relevant SLD Name in “Define System Landscape”

d) Activate the VM Container as per SAP Note 854170

Update the Threshold value for Background processing:

SPRO >> SAP Supplier Relationship Management >> SRM Server >> Cross-Application Basic Settings >>
Background Processing >> Define Threshold Value for Background Processing