Accepted Solutions (1)
Dear @byd,
Question 1.
Answer: Yes
Standard API:
- API name (business): Business Partner (A2X) OData API
- Technical service name: API_BUSINESS_PARTNER
- Protocol: OData V2
- Communication scenario (S/4HANA Cloud, public edition):
Business Partner, Customer and Supplier Integration (SAP_COM_0008)
More details below:
This API allows read, create, update, delete of Business Partner, Customer, and Supplier data
More details below:
Extension custom fields:
Answer: Yes, custom BP fields can be read via this API, provided they are created and enabled correctly:
1. Create the custom field in business context
Master Data: Business Partner (BP_CUSTVEND1) using the Custom Fields app
More details below:
2. On the UI tab enable usage for the Business Partner (A2X) service, then Publish.
The Business Partner (A2X) help explicitly states the API entities are extensible via Custom Fields
3. After publishing the custom field:
- Appears in the OData service metadata.
- Can be selected in $select and returned in read calls
So BP master data including extension fields is fully retrievable via API_BUSINESS_PARTNER as long as those fields are defined via Key User extensibility and enabled for the service.
Older IDoc-based options like DEBMAS/CREMAS exist but are explicitly not recommended for new integrations in current Public Cloud releases
More details below:
Question 2.
Answer: Yes, but via the generic Journal Entry change SOAP API, not an AR-specific OData service.
On the FI open item journal entry line side, the payment block is stored as:
- Field: PaymentBlockingReason the payment block key
- It is available on the Operational Journal Entry Item / DebtorItem/CreditorItem structures
More details below:
Standard API that can change this:
- API name (business): Journal Entry Change (Asynchronous)
- Inbound service: JournalEntryBulkChangeRequest_In (SOAP)
- Communication scenario: Finance Posting Integration (SAP_COM_0002)
More details below:
The Finance API documentation explicitly describes this service as the way to change journal entry data and notes that it can be extended with custom fields as well
More details below:
The Operational Journal Entry Item help lists PaymentBlockingReason as a field in the structure used together with the Journal Entry APIs
More details below:
Summary: Yes, you can toggle the payment block on AR open items via SOAP using Journal Entry Change (Asynchronous)
Question 3.
Answer: Yes
Standard OData API:
- API name (business): Payment Advice (A2X)
- Technical service name: API_PAYMENT_ADVICE_SRV
- Protocol: OData V2
- Communication scenario: Finance – Payment Advice Integration (SAP_COM_0331)
More details below:
To register (create) a payment advice:
- Send POST to
/sap/opu/odata/sap/API_PAYMENT_ADVICE_SRV/A_PaymentAdvice
with payload including PaymentAdviceType, CompanyCode, PaymentAdviceNumber, etc.
More details below:
The same service exposes entity sets for Payment Advice and Payment Advice Line Item and the Operations for Payment Advice documentation lists the standardCRUD operations
More details below:
There is also a SOAP API:
- Payment Advice Create (PaymentAdviceNotification_In)
- Also under the Finance Payment Advice Integration (SAP_COM_0331)
More details below:
In Public Cloud the documentation about Automatic Payment Advice Processing explicitly refers to both Payment Advice (A2X) and Payment Advice Create as the standard integration options
More details below:
Summary:
- BP master + extension fields:
Yes, Business Partner (A2X) OData API API_BUSINESS_PARTNER with custom fields enabled via Custom Fields - AR open item payment block toggle:
Yes, via Journal Entry Change (Asynchronous) SOAP (JournalEntryBulkChangeRequest_In, scenario SAP_COM_0002). No AR-specific OData API, but line-item PaymentBlockingReason is supported there - Payment advice registration:
Yes, Payment Advice (A2X) OData API API_PAYMENT_ADVICE_SRV (scenario SAP_COM_0331) and optionally SOAP Payment Advice Create
Best Regards,
Dawid
Answers (1)
Dear @byd,
I apologize but I didn't see your comment earlier. Below are the answers to your questions
Question 1
In this API the item key is AccountingDocument + CompanyCode + FiscalYear + AccountingDocumentItemID
So:
YES Accounting Journal Entry / FI Accounting Document number is CORRECT
IF Customer Invoice Document Number is only correct if it is the same FI Accounting Document number produced by the posting often yes in FI-based invoicing runs but not the SD Billing Document number
NO AR Open Item Document Number isn’t a separate key here the open item is a line item in the accounting document
Question 2
In Public Cloud the item number is specified as 3 numeric characters for example 001 BUT it’s mixing between documentation and system. Correct key you will find in Manage Journal Entries app below:
More details below:
Question 3
Yes the standard Change pattern in this API is:
Put the new value in the …Change node and
Set FieldValueChangeIsRequested to true so SAP actually applies the change
To clear the payment block, you send an initial/blank value for PaymentBlockingReasonCode and FieldValueChangeIsRequested=true
Best Regards,
Dawid
Bluesky| User | Count |
|---|---|
| 41 | |
| 4 | |
| 4 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.