In this blog post, you will learn where do party fields “bill-from” and “ship-to” come from in the outbound message of the SOAP API Customer Invoice – Send (B2B) (CO_EDI_INVOICE_REQUEST_OUT).
In the outbound message of the SOAP API Customer Invoice – Send (B2B), you may be confused about the existence of the party fields “bill-from” and “ship-to”. These fields do not exist in the header of a supplier invoice and are not supposed to appear in the outbound message. This blog post explains how these two fields appear in the outbound message.
The “bill-from” party field that does not exist in a supplier invoice header but appears in the outbound message comes from either of the following sources:
The “bill-from” field that comes from table EDPAR can be maintained via Central Business Configuration (CBC) or “Manage Your Solution” app.
You can define the value of the “bill-from” party field in table EDPAR by performing the configuration step/configuration activity Convert External to Internal Partner Numbers, where you define the internal partner number of “bill-to” and the partner function “bill-from”. Based on this configuration, then the system converts the internal partner number to an external partner number. This external partner number is the value of the “bill-from” party field sent in the outbound message.
If no value is defined for the “bill-from” party field in table EDPAR, the field value comes from “Account at customer” defined in the business partner master data.
The “ship-to” party field in the outbound message can come from the header and items of a supplier invoice. Normally, the “ship-to” party field is not configured in the partner determination for the invoice header. So, the “ship-to” party field that appears in the outbound message usually comes from the items of a supplier invoice. When you configure the “ship-to” party field in partner determination for billing header, the “ship-to” party fields from both invoice header items are sent out in the outbound message. If the values are the same for the “ship-to” party fields from the invoice header and items, one “ship-to” party field is sent. If the values are different, the fields with different values are sent.
The “bill-from” and “ship-to” party fields appear in the outbound message of the SOAP API Customer Invoice – Send (B2B) after you make the above-mentioned configuration in this blog post. If you have any questions regarding this blog post, please feel free to contact us or provide your feedback in a comment.
SAP S/4HANA Cloud for Sales Topic Page
Ask questions about SAP S/4HANA Cloud for Sales and follow
Read other SAP S/4HANA Cloud for Sales and follow blog posts
ivan2013#overview
In the outbound message of the SOAP API Customer Invoice – Send (B2B), you may be confused about the existence of the party fields “bill-from” and “ship-to”. These fields do not exist in the header of a supplier invoice and are not supposed to appear in the outbound message. This blog post explains how these two fields appear in the outbound message.
“Bill-from”
The “bill-from” party field that does not exist in a supplier invoice header but appears in the outbound message comes from either of the following sources:
- The “bill-from” field in tableEDPAR
- The “Account at customer” field defined in the business partner master data
The “bill-from” field that comes from table EDPAR can be maintained via Central Business Configuration (CBC) or “Manage Your Solution” app.
Figure 1: Define the value for the “bill-from” party field in table EDPAR
You can define the value of the “bill-from” party field in table EDPAR by performing the configuration step/configuration activity Convert External to Internal Partner Numbers, where you define the internal partner number of “bill-to” and the partner function “bill-from”. Based on this configuration, then the system converts the internal partner number to an external partner number. This external partner number is the value of the “bill-from” party field sent in the outbound message.
Figure 2: Conversion logic for the value of the “bill-from” party field
If no value is defined for the “bill-from” party field in table EDPAR, the field value comes from “Account at customer” defined in the business partner master data.
Figure 3: Define the value for Account at customer in the business partner master data
“Ship-to”
The “ship-to” party field in the outbound message can come from the header and items of a supplier invoice. Normally, the “ship-to” party field is not configured in the partner determination for the invoice header. So, the “ship-to” party field that appears in the outbound message usually comes from the items of a supplier invoice. When you configure the “ship-to” party field in partner determination for billing header, the “ship-to” party fields from both invoice header items are sent out in the outbound message. If the values are the same for the “ship-to” party fields from the invoice header and items, one “ship-to” party field is sent. If the values are different, the fields with different values are sent.
Figure 4: Configure partner determination for the invoice header
Conclusion
The “bill-from” and “ship-to” party fields appear in the outbound message of the SOAP API Customer Invoice – Send (B2B) after you make the above-mentioned configuration in this blog post. If you have any questions regarding this blog post, please feel free to contact us or provide your feedback in a comment.
Related Info
Issues of BillFrom Party in the invoice EDI InvoiceRequest_Out
SAP S/4HANA Cloud for Sales Topic Page
Ask questions about SAP S/4HANA Cloud for Sales and follow
Read other SAP S/4HANA Cloud for Sales and follow blog posts
ivan2013#overview
- SAP Managed Tags:
