ESOA Debugging for SRM sourcing scenario

1. Choose the XML file and message ID, save the data in payload

- SXI_MONITOR (More criteria, preferred)

- SXMB_MONI 

2. Set breakpoint in mapping class

- Class SAPSRM/CL_CH_SOA_MAP_*

- SOA package SAPSRM/CH_SOA

- Mapper class /SAPSRM/CH_SOA_MAPPER

   Example: For PO creation

/SAPSRM/CL_CH_SOA_MAP_PO_OUT Base mapper class for PO PO_CREATE_OUT

   Example: For item mapping:

Class /SAPSRM/CL_CH_SOA_DO_PO_ITEM method MAP_ITEMS

   Example: For Confirmation in:

Class /SAPSRM/CL_CH_SOA_MAP_PO_CONIN method /SAPSRM/IF_CH_SOA_MAP_PO_CONIN~CREATE_CONFIRMATION

   Example: For Source of supply mapping

/SAPSRM/CL_CH_SOA_MAP_SUSPO_HD SUS PO Map Header Class

/SAPSRM/CL_CH_SOA_MAP_SUSPO_IT SUS PO Item Mapper

3. Find out the interface (you can find it in XML file, the second line), upload the file and debug

- SPROXY (Preferred)

- SXI_SUPPORT

 

Scenario 1

A Purchase Requisition is sent from ERP to SRM to create a shopping cart in SRM.

-PurchaseRequestERPSourcingRequest_out

-PurchaseRequestERPSourcingRequest_in

-PurchaseRequestERPSourcingConfirmation_out

-PurchaseRequestERPSourcingConfirmation_in

 

Scenario 2:

Purchase Requisition is sent from ERP to SRM to create draft RFx in SRM

- RFQRequestSuiteRequest_Out

- RFQRequestSuiteRequest_In

- RFQRequestSuiteConfirmation_Out

- RFQRequestSuiteConfirmation_In

 

Service Procurement Service

- PurchasingContractERPRequest_Out_V1

- PurchasingContractERPConfirmation_In

- PurchaseOrderERPRequest_Out_V1

- PurchaseOrderERPConfirmation_In

- PurchaseOrderERPRequest_In_V1

- PurchaseOrderERPConfirmation_Out_V1

- ServiceAcknowledgementERPCreateRequest_Out

- ServiceAcknowledgementERPConfirmation_In

- ServiceAcknowledgementERPNotification_In

 

Central Contract Management Service

- PurchasingContractSRMReplicationRequest_Out

- PurchasingContractSRMReplicationConfirmation_In

- PurchaseOrderSRMPricingSimulateQueryResponse_In

- PurchaseOrderERPContractReleaseNotification_In

- PurchasingContractSRMArchivingCheckQueryResponse_Out

 

Error Handling via FEH

- FEH tool is a framework containing supporting features like error persistency, monitor capabilities, derivation and triggering of resolution strategies, message editing.

- /SAPPO/PPO2 transaction

- /SAPPO/RESUBMIT transaction - resubmission of post processing orders (FEH REJECT and FEH RETRY)

- Background Job PPO (FEH) RESUBMIT ENT. SERVICES

- Activate FEH in SPRO (FEHV_ACTIVE in sm30) and entry in a table via the transaction /n/SAPPO/LOGSYS, where the logical system must be assigned to the software component (ex CA-SOA-ESM-SRM-PUR)

 

For troubleshooting SOA Services - refer SAP Note 1270081

 

Note: 1878611, 1771075 (does not consider status in method /SAPSRM/CL_CH_SOA_DO_PR_ITM~GET_SOURC_STATUS_CODE)

Note: 1736956, 1843352 (issue triggered by ME55)

Note: 1872766