Challenges in Central contract Distribution Process:-
During distribution of Central contract it might be possible that some line items (Materials) are not maintained in respective backend systems .For example it might possible that Material not maintained Respected Plant/Deleted from plant etc .These status of Products not updated to SRM system .
From buyer perspective central contract distribution stuck due to Master data issue .In these cases currently following steps need to be performed for successful distribution of central contract :-
- Get the updates from buyer that Central contract fail to replicate in backed system OR
- Perform Monitoring for erroneous documents
- Maintained/Update Master data .I.e. Extend material in respective plants.
- Discard/After confirmation of data maintenance Reprocess the message from Forward Error Handling (FEH)
- Inform the Buyer to redistribute the Central contract.
This is two way activity where buyer have to wait until he received Master Data update and than redistribute respective central contract .Upon successful distribution Outline Agreement created based upon configuration.
Solution Approach to overcome Data dependency
We should use “Error and Conflict Handler” in system landscape to get the actual update for distributed document which flows through from Process Integration (PI).In case Business Document i.e. Central contract stuck in FEH of backend system due to some Master data issues can be notified to document processing person or business user.
We can use BAPI call/custom development which will be call from portal where Material Extend/Update can be maintained by contract processing officer.
Contract officers can access these iViews (to call BAPI/custom FM) .Master data i.e. Material can be process in backed using following ways:-
- Using BAPIs Material can be extend/update in plants
- Custom Function Module
- BDC call in backend system
On successful completion of Master data creation we can Re-Process FEH Message or Discard FEH Message and contract officer will re-distribute the central contract.
- Activate Forward Error Handling (FEH)
Customer has to maintain the followed table: /n/SAPPO/LOGSYS, where he should assign the logical system to
software component (ex CA-SOA-ESM-SRM-PUR) as shown below :-
FEH needs to be activated to capture the error messages using Cross-Application Components -> Processes
and Tools for Enterprise Applications Enterprise Services -> Error and Conflict Handler ->
Activate Error and Conflict Handler.
- Error and Conflict Handler
The Error and Conflict Handler requires the use of the Post-processing Office component
SAP Note: – 1270081