Definition
An interface to manage the financial data of customer and supplier accounts master data
Business Context and Use
The web service interface Manage Trade Receivables Payables Account In enables you to update the Financial Data of a supplier or customer account master data.
The Financial Data of an account can be used to denote if a business partner that has a supplier and customer account can be blocked for netting. It can also be used to put a block on dunning processes for said account. It can also be used to enable the doubtful debtors indicator or to specify the dunning procedure code.
The web service interface offers the operations MaintainBundle and CheckMaintainBundle, the latter of which does not execute a save.
If fields within the request message are maintained, then the update will be carried out according to these. If a field is left out, no update will be carried out for said field.
If the DoubtfulDebtorIndicator passed is true, then the parameter
DunningBlockingReasonCode needs to be provided. If the DoubtfulDebtorIndicator passed is true and the DunningBlockingExpirationDate is not provided, it will be defaulted to 9999.12.31
Prerequisites
Existence of referenced business objects:
The following business objects are only referenced and will not be created by the service operation. They must exist in the system already at the time the web service is called:
More Information
Here is a simple example of an update message
<n0:TradeReceivablesPayablesAccountBundleMaintainRequest_sync xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<TradeReceivablesPayablesAccount actionCode="02">
<CompanyID>mc10000</CompanyID>
<BusinessPartnerInternalID>BUS_PARTNER</BusinessPartnerInternalID>
<NettingBlockedIndicator>true</NettingBlockedIndicator>
<DebtorDoubtfulIndicator>true</DebtorDoubtfulIndicator>
<DunningBlockedIndicator>true</DunningBlockedIndicator>
<DunningBlockingExpirationDate>2019-01-24</DunningBlockingExpirationDate>
<DunningBlockingReasonCode>02</DunningBlockingReasonCode>
<NewDunningProcedureCode>03</NewDunningProcedureCode>
</TradeReceivablesPayablesAccount>
</n0:TradeReceivablesPayablesAccountBundleMaintainRequest_sync>
You can find general information about Web services, their structure and consumption in the Web Services documentation. Please open the Web Services document in a new window.
Definition
Bundle operation to update Financial Data of a Customer or Supplier Account.
Prerequisites
Existence of referenced business objects:
The following business objects are only referenced and will not be created by the service operation. They must exist in the system already at the time the web service is called:
Structure
All of the fields of the request message are optional and if not provided will be ignored. However some fields may be ignored if their parent indicator is not provided or if it is not valid. This will be explained below.
NettingBlockedIndicator is an indicator which can be used in the context of a business partner having both a customer and a supplier account. If the business partner has both, then this indicator, if true, will not allow items of a supplier to be cleared against items of a customer and visa versa.
DunningBlockingExpirationDate and DunningBlockingReasonCode are displayed on the Customer Account UI. The DunningBlockedIndicator is not on the UI, but must be set to true on the request message if you wish to enable Dunning Blocking. The DunningBlockingExpirationDate is seen on the UI as Dunning Block Expiry Date and DunningBlockingReasonCode as Dunning Block Reason.
Definition
To check whether Trade Receivables Payables Accounts can be created, updated, or deleted without errors.
Business Context and Use
The CheckMaintainBundle offers the same functionality of the MaintainBundle without saving the change made.
The explainations given for the MaintainBundle can therefore also be applied to the CheckMaintainBundle operation.
Show full documentation
Show full documentation