SAP Knowledge Base Article - Preview

3193281 - Confirm/Reject of critical change is not distributed via IDoc

Symptom

You've activated the 4-eye-principle for critical changes in the system.
Customer and vendor master data are maintained centrally in one client (for example, client A) and distributed by Debmas/Cremas-IDocs to another client (for example, client B).
A change in a critical field is therefore transferred to client B and triggers that the customer or vendor needs to be confirmed by a different user in client B.
However, execution of FD08 / FK08 in client A is not distributed to client B.
You would like to know if there is a standard solution to get the confirm/release action in client B automatically after it has been done in client A.


Read more...

Environment

  • SAP ERP 6.0
  • SAP ERP Central Component 6.0
  • SAP enhancement package 1 for SAP ERP 6.0
  • SAP enhancement package 2 for SAP ERP 6.0
  • SAP enhancement package 3 for SAP ERP 6.0
  • SAP enhancement package 4 for SAP ERP 6.0
  • SAP enhancement package 4 for SAP ERP 6.0 on SAP enhancement package for SAP NetWeaver 7.0
  • SAP enhancement package 5 for SAP ERP 6.0
  • SAP enhancement package 6 for SAP ERP 6.0
  • SAP enhancement package 6 for SAP ERP 6.0, version for SAP HANA
  • SAP enhancement package 7 for SAP ERP 6.0
  • SAP enhancement package 8 for SAP ERP 6.0

Product

SAP ERP 6.0

Keywords

KBA , LO-MD-BP-CM , Customer Master , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.