Skip to Content

SRM: Service Entry Sheet from SRM not created in ECC but no error shown in SRM

Apr 12, 2017 at 08:14 AM


avatar image


when creating a service confirmation in SRM we occasionally have the problem that the Entry Sheet is not created in ECC (the corresponding material document is also not created). This is due to an ECC validation error. But in SRM the "Tracking" tab of the PO shows the status of the Entry Sheet as "posted in backend" and also a backend document number is shown (there is no second line for a corresponding confirmation shown as it is in normal case). In ECC no Entry Sheet for the shown backend document number exist (e. g. no entry in table ESSR, etc.). Confirming for this PO in SRM is still possible for this PO, but always the same problem of course.

If we create the Entry Sheet directly in ML81N an error message is shown after acceptance (e.g. invalid HFM mapping, invalid field entry, etc. - different reasons possible, all related to ECC validations). In this case SRM shows no Entry Sheet status, but the Entry Sheet number exists in ECC.

Has anybody an idea how we can monitor such failing service confirmations and in best case see the ECC error message? As service confirmations are created by using RFC we can´´t use the IDoc log. But also all other monitoring we had in mind doesn´t show any error (e.g. SRM Application Monitor, RZ20, SMQ1, SMQ2, etc.).

Any idea is much appreciated.

Best regards

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Ivy Li
Jul 21, 2017 at 02:28 AM


idoc is used to transfer confirmation, so you may check if there is any error in inbound idoc in ERP side.

you may also consider creating test data for BAPI_ENTRYSHEET_CREATE. Please refer to the wiki page below to create the test data. The same process applies to all kind of BAPIs.

Last but not least, please also go to customizing "Activate Extended Classic Scenario" to tick indicator for 'Display Back-End Msgs as Errors'. For most cases, backend errors will be displayed in SRM documents, but not all errors will be shown.


10 |10000 characters needed characters left characters exceeded