‎2025 Jan 28 2:41 PM - edited ‎2025 Jan 28 2:45 PM
Hello SAP Community,
I have configured the "Customer Invoice - Send (B2B)" API to send EDI messages when a customer invoice is completed. (https://api.sap.com/api/CO_EDI_INVOICE_REQUEST_OUT/resource)
The message is sent but there are inconsistency in it, in the "Party" nodes.
Example:
For example, my billing document has those Business Partners:
==>The Sold-to, Bill-to and Payer is the customer: "Client FR 1 (CUSTFR1)"
The Supplier is the Company (FR10).
Outbound message:
The "SupplierPartyIDs I receive in the outbound message in the Party part is:
<Party PartyType="BillFrom">
<SupplierPartyID>CUSTFR1</SupplierPartyID>
...
</Party>
<Party PartyType="SoldTo">
<SupplierPartyID>CUSTFR1</SupplierPartyID>
...
</Party>
<Party PartyType="BillTo">
<SupplierPartyID>CUSTFR1</SupplierPartyID>
...
</Party>
<Party PartyType="Payer">
<SupplierPartyID>CUSTFR1</SupplierPartyID>
...
</Party>
<Party PartyType="ShipTo">
<SupplierPartyID>CUSTFR1</SupplierPartyID>
...
</Party>
All SupplierPartyIDs are the customer's, but the BillFrom type Party's should be the company's.
I think it may be something missing in the configuration, but I don't know what.
Has someone an idea of what can be missing ?
Thank you for your help,
Marion Marolany
Request clarification before answering.
Hello,
It seems like the issue you're facing is related to incorrect mapping of the business partner IDs in the "Customer Invoice - Send (B2B)" API. The problem lies in the fact that the "SupplierPartyID" for all the different PartyTypes, including "BillFrom", is being populated with the customer's ID ("CUSTFR1") instead of the company's ID (which should be "FR10" for "BillFrom").
Here's a checklist of actions that can help resolve this issue:
1. **Mapping Configuration**: Ensure that your mapping configuration in the middleware or the integration tool (such as SAP Process Integration/Orchestration, SAP Integration Suite, or any other integration platform) is correctly set up. The configuration should map the correct business partner IDs for each PartyType. Specifically, the "BillFrom" PartyType should map to the company's ID ("FR10").
2. **Master Data Alignment**: Verify that the business partner master data is correctly maintained in your SAP S/4HANA Cloud system. The IDs for Sold-to, Bill-to, Payer, and Supplier should be accurate and aligned with your configuration in the middleware.
3. **API Configuration**: Double-check the configuration settings of the "Customer Invoice - Send (B2B)" API. Make sure that the API is correctly set up to fetch and assign the appropriate business partner IDs based on the roles they are serving in the transaction.
4. **Integration Flow Debugging**: If possible, debug the integration flow to see where the mapping might be going wrong. Check for transformation logic that might inadvertently set the wrong values.
Best regards,
Dequan Xu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
First of all, thank you for your response.
In my case, the data I get didn't pass through any middleware yet, so if I understand well the problem must be within the API configuration or the BP Master Data.
For the API Configuration option, the communication arrangement is really basic so I don't think there a problem here:
I created a communication arrangement for SAP_COM_0444 with basic authentification, and it is sending data to CPI. The data we are analyzing is the data that are received to CPI but without any transformations. The outbound messages are only send if the BP is CUSTFR1:
For the BP Master Data configuration option:
As you can see in the screen shot from the initial question, in the Customer Invoice in the "Business Partners" section, there is a Sold-to Party, a Bill-to Party and a Payer Party, but not any Supplier Party mentionned. And I don't think it's possible to add a BP of Supplier's type on the Sales Order either.
I feel like something may be missing here, but I don't understand what.
| User | Count |
|---|---|
| 33 | |
| 17 | |
| 14 | |
| 13 | |
| 9 | |
| 4 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.