| Description | Manage Accounting Regrouping Run |
| Name | ManageReceivablePayableLedgerAccountRegroupingRunIn |
| Namespace | http://sap.com/xi/A1S/Global |
| Process Component Description | Financial Accounting |
| Process Component Name | Accounting |
| Process Component Namespace | http://sap.com/xi/AP/FinancialAccounting/Global |
| Deployment Unit Description | Financials |
| Endpoint Activation | By Scoping of Process Component | Operations |
| Release Status | Released |
An interface to perform reclassification run for accounts receivables, payables.
The web service interface Manage Receivable Payable Ledger Account Regrouping Run In enables you to connect external applications to your SAP Business ByDesign system and to create and start reclassification runs. The web service interface Manage Receivable Payable Ledger Account Regrouping Run In is relevant if your company wants to schedule reclassification runs from external applications.
The web service interface Manage Receivable Payable Ledger Account Regrouping Run In offers following operations
CreateAndStartAccountsReceivablePayableLedgerAccountRegroupingRun
Here is an example of a simple web service request:
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <AccountsReceivablePayableLedgerAccountRegroupingRun> <ObjectNodeSenderTechnicalID></ObjectNodeSenderTechnicalID> <CompanyID>MC10000</CompanyID> <Description languageCode="EN">Sample ARP RGRP Run</Description> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
The change state ID does not apply to the account receivables payables regrouping run, as the run is only configured for creation and execution of the mass data run and cannot perform update operations.
You can find general information about Web services, their structure and consumption in the Web Services documentation.
Possible scenarios include the following:
Create and Start Accounts Receivable Payable Ledger Account Regrouping Run
| Description | Account receivable payable regrouping run create and start run |
| Name | CreateAndStartAccountsReceivablePayableLedgerAccountRegroupingRun |
| Synchronous | yes |
| Release Status | Released |
To create and start accounts receivable payable ledger account regrouping run
The request message of the operation CreateAndStartAccountsReceivablePayableLedgerAccountRegroupingRun contains a BasicMessageHeader node element as well as an AccountsReceivablePayableLedgerAccountRegroupingRun message node element which contains the selection data that is needed to create accounts receivable payable ledger account regrouping run. The detailed structure of the AccountsReceivablePayableLedgerAccountRegroupingRun node will be explained in the following sub-chapters. The AccountsReceivablePayableLedgerAccountRegroupingRun node can occur only once in the request message – this means that user is allowed to create only either accounts payables or receivable ledger account regrouping run through a single web service request.
The response message type of the operation CreateAndStartAccountsReceivablePayableLedgerAccountRegroupingRun contains log items, processing information and a node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as Run ID.
The AccountsReceivablePayableLedgerAccountRegroupingRun message node element contains all generic attributes that is relevant for accounts receivable payable regrouping run like company id, set of books id, party role category code etc.
There are few mandatory attributes that must be present in the request message to start and execute accounts receivable payable ledger account regrouping run. The following are the attributes:
Company id
Accounting closing step code
Party role category code
Fiscal year
Fiscal period
| If the XML request contains empty tag of either of above then appropriate error message is raised. On the contrary, if even the empty tag is not supplied then service itself will fail and throw exception against the corresponding elements |
Apart from these, request message have other attributes to process the accounts receivable or payable ledger accounts regrouping run.
Test Run Indicator
Description
Set of books id
Business partner id
It is a mandatory selection parameter in the request message for both accounts receivable and payable ledger account regrouping run.
Here is an example of a simple payable ledger account regrouping run with empty company id
Show full documentation
Show full documentation
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader>
<!--Optional:-->
<ID/>
<!--Optional:-->
<UUID/>
<!--Optional:-->
<ReferenceID/>
<!--Optional:-->
<ReferenceUUID/>
</BasicMessageHeader>
<AccountsReceivablePayableLedgerAccountRegroupingRun>
<!--Optional:-->
<ObjectNodeSenderTechnicalID/>
<CompanyID></CompanyID>
<!--Optional:-->
<SetOfBooksID>0001</SetOfBooksID>
<!--Optional:-->
<Description languageCode="EN">Sample Payable rgrp run wo company id</Description>
<!--Optional:-->
<TestRunIndicator>true</TestRunIndicator>
<PartyRoleCategoryCode>3</PartyRoleCategoryCode>
<BusinessPartnerID>MC2000</BusinessPartnerID>
<AccountingClosingStepCode>020</AccountingClosingStepCode>
<AccountingPeriodID>003</AccountingPeriodID>
<FiscalYearID>2016</FiscalYearID>
</AccountsReceivablePayableLedgerAccountRegroupingRun>
</n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEE0790B9EDE26CC59C31A:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>040(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Company is required</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation>
The accounting closing step code is a mandatory parameter for both accounts receivable or payable ledger account regrouping run. In case empty tag of account closing step is provided in the service request, then web service will default the value '000' as accounting closing step code.
Here is an example of a simple payable ledger account regrouping run with empty accounting closing step code
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Payable rgrp run wo closing step</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode></AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEE0790B9EDE26CC59C31A:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>258(/FIA_ACC_ADJUSTMENT/)</TypeID> <SeverityCode>1</SeverityCode> <Note>Check for closing step Operational postings to be closed before run execution skipped for test runs</Note> </Item> <Item> <TypeID>007(/JOB_MESSAGE/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>MDRO instance is not active</Note> </Item> <Item> <TypeID>024(/FIA_PERIOD_LOCK/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Period 003 in fiscal year 2016 closed in set of books 0001 for closing step 000</Note> </Item> <Item> <TypeID>024(/FIA_PERIOD_LOCK/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Period 004 in fiscal year 2016 closed in set of books 0001 for closing step 000</Note> </Item> <Item> <TypeID>040(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Company is required</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation>
The party role category code differentiates the run whether it is a payable ledger account regrouping run or receivable ledger account regrouping run.
| User Interface | PartyRoleCategoryCode |
|---|---|
| Payable Regrouping Run | 3 |
| Receivable Regrouping Run | 4 |
In case empty tag of party role category code is provided in the service request, the system will raise appropriate error message.
Here is an example of a simple regrouping run with empty party role category code.
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample rgrp run wo party role</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode></PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEE0790B9EDE26CC59C31A:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>005(/FIA_ARP_RGRP_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Party role must be entered for debitor or creditor</Note> </Item> <Item> <TypeID>258(/FIA_ACC_ADJUSTMENT/)</TypeID> <SeverityCode>1</SeverityCode> <Note>Check for closing step Operational postings to be closed before run execution skipped for test runs</Note> </Item> <Item> <TypeID>007(/FIA_ARP_RGRP_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Business partner MC2000 (AMS) not found</Note> </Item> <Item> <TypeID>024(/FIA_PERIOD_LOCK/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Period 003 in fiscal year 2016 closed in set of books 0001 for closing step Closing entries</Note> </Item> <Item> <TypeID>024(/FIA_PERIOD_LOCK/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Period 004 in fiscal year 2016 closed in set of books 0001 for closing step Closing entries</Note> </Item> <Item> <TypeID>040(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Company is required</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation>
Here is an example of a simple payable regrouping run
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Payable rgrp run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
Here is an example of a simple receivable regrouping run
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable rgrp run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
Both fiscal year and period are mandatory parameters like in regrouping run for payables and receivables in the UI.
Here is an example of a simple payable regrouping run without fiscal period
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample payable rgrp wo fiscal period</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID></AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEE0790B9EDE26CC59C31A:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>258(/FIA_ACC_ADJUSTMENT/)</TypeID> <SeverityCode>1</SeverityCode> <Note>Check for closing step Operational postings to be closed before run execution skipped for test runs</Note> </Item> <Item> <TypeID>001(/FIA_ARP_RGRP_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Selections are missing for fiscal year or period</Note> </Item> <Item> <TypeID>007(/JOB_MESSAGE/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>MDRO instance is not active</Note> </Item> <Item> <TypeID>040(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Company is required</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation>
Here is an example of a simple payable regrouping run without fiscal year
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample payable rgrp wo fiscal year</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID></FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEE0790B9EDE26CC59C31A:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>258(/FIA_ACC_ADJUSTMENT/)</TypeID> <SeverityCode>1</SeverityCode> <Note>Check for closing step Operational postings to be closed before run execution skipped for test runs</Note> </Item> <Item> <TypeID>001(/FIA_ARP_RGRP_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Selections are missing for fiscal year or period</Note> </Item> <Item> <TypeID>007(/JOB_MESSAGE/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>MDRO instance is not active</Note> </Item> <Item> <TypeID>040(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Company is required</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleConfirmation>
Test run indicator decides the mode of the run whether the particular run would be a test run or an update run
| User Interface | TestRunIndicator |
|---|---|
| Test run | true |
| Update run | false |
This is an optional field and by default it takes false i.e. update run
Here is an example of a simple test receivable ledger account regrouping run
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable test rgrp run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
Here is an example of a simple update receivable ledger account regrouping run
Scenario 1:
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable update rgrp run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
Scenario 2:
<n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountRegroupingRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable update rgrp run</Description> <!--Optional:--> <TestRunIndicator/> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <BusinessPartnerID>MC2000</BusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountRegroupingRun> </n0:AccountsReceivablePayableLedgerAccountRegroupingRunCreateAndStartRunMessageBundleRequest>
This is a optional field and request can have empty tag against the element in the request message and in that case the description of the accounts receivable payable ledger account regrouping run would be empty.
This is a optional field and request can have empty tag against the element in the request message and in that case the run would be executed for all the set of books. Otherwise, the run would be executed only for the particular set of books.
This is an optional field and request can have empty tag against the element in the request message and in that case the run would be executed for all the business partner. Otherwise, the run would be executed only for the particular business partner.