Quantcast
Channel: SCN : Document List - Supplier Relationship Management (SAP SRM)
Viewing all articles
Browse latest Browse all 198

Forward Error Handling in SAP SRM

$
0
0

This article present benefit of leveraging FEH (Forward Error Handling) concept in SOA (Service Oriented Architecture) to monitor failed error messages and perform troubleshooting based on displayed error messages.


Sometimes SAP SRM Central Contract will not successfully distribute to ERP backend and we may not get detail error message from SRM Portal to perform further investigation.

 

As a prerequisite, FEH should be activated in SAP SRM as well as SAP ECC backend.

Below screenshot depicts this configuration in SAP SRM.

 

image1.jpg

 

 

image2.jpg

 

 

 

As an example, below is shown one SRM Central contract which has System Status as “In Distribution” meaning it is not successfully distributed to SAP ECC backend.

 

image3.jpg

 

 

Based on SRM Portal screen it is very difficult and time consuming to find exact error why this SRM Central Contract unable to distribute to ECC.In this case FEH(Forward Error Handling) come as very useful tool to diagnose the issue.

Assuming all the required configurations are completed in SRM as well as ECC, execute transaction /SAPPO/PPO2 in SAP ECC.

Enter filter criteria as per your data requirement.

 

image4.jpg

 

After executing the transaction we will get below screen with error message

 

image5.jpg

 

Double click object/key to display detail message

 

image6.jpg

 

From above screen it shows that Material is flagged for deletion. This is a reason for failure of distribution of contract to ECC.

This can also be verified by checking Material Status in SAP ECC

 

image7.jpg

 

It is recommended to check this transaction /SAPPO/PPO2 in SAP ECC regularly to proactively monitor and resolve the issues identified based on the result of this transaction.


Viewing all articles
Browse latest Browse all 198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>