Price mismatch between two SAP systems in outline agreement

[ravi109]

Hi All,

I am struck in one issue. As we have one SAP system(PPC) which will send prices different SAP systems (Based on region like AMS,APJ&EMEA)

PPC system sent updated prices through idoc for an outline agreement number.

We can see the same agreement number in our reginal boxes as well.

Recent idoc was received from PPC system & we can see the updated price in the IDOC level.

But when i checked the updated price was not updated in outline agreement in SAP.

Can anybody help on this please.

Regards
Ravi Uppu

[MOHAMMED_BASER · Accepted solution]

Dear Ravi,
Refer to the issue you shared, it seams like the SAP IDoc integration issue. My suggestion is to focus some key areas to investigate why the updated price from the PPC system isn't reflecting in the outline agreement in the regional SAP systems (AMS, APJ, EMEA):

1. IDoc Processing Status
Check the status of the IDoc in the receiving system (e.g., WE02 or WE05).
If the status is not “53” (successfully posted), it means the IDoc was received but not processed correctly.
Look for error messages or warnings in the IDoc logs.

2. Function Module or Message Type Mapping
Confirm that the correct message type (e.g., ORDERS, CONTRACT, etc.) and function module are being used to update outline agreements.
If the function module doesn’t support price updates or is misconfigured, the update won’t reflect.

3. Change Pointers / ALE Configuration
Ensure change pointers are active for price changes in the PPC system.
Check if the distribution model (BD64) and partner profiles (WE20) are correctly set up for price updates.

4. Authorization Issues
The user or RFC destination used to post the IDoc might lack authorization to update outline agreements.
Check for authorization errors in the IDoc logs or ST22 dumps.

5. Custom Logic or User Exits
If there’s custom logic (e.g., in EXIT_SAPLEINM_002 or BADI implementations), it might be preventing the update.
Review any user exits or enhancements that could block or override the price update.

6. Outline Agreement Locking
If the outline agreement was locked during IDoc posting (e.g., someone was editing it), the update might have failed silently.
Check SM12 for lock entries.

7. Data Mapping Issues
Ensure the price field in the IDoc is correctly mapped to the outline agreement field.
Sometimes the IDoc contains the correct data, but it’s not mapped to the right field in the target system.

I suggest you to do the following steps mentioned below.

1. Run transaction WE02/WE05 to check IDoc status and logs.
2. Use BD87 to reprocess the IDoc manually and observe any errors. 
3. Check SM13 for update failures.
4. Review custom code or enhancements that might interfere.
5. Validate partner profile and distribution model setup.
6. Confirm that the outline agreement is not locked during posting.

Hope this will resolve the issue, if done please confirm

[ravi109 · Accepted solution]

Hello Baser,

[ravi109 · Accepted solution]

Hello Baser, Thank you for your reply. i have checked the inbound idoc & status of the IDOC is 53 status. In the Inbound Idoc i can see the updated price. But in the document level price was not updated. Even i have checked SM13 logs also. I dont see any thing..