Description | Manage Accounting Adjustment Run |
Name | ManageAccountingAdjustmentRunIn |
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 Accounting Adjustment Runs namely foreign currency re-measurement run for accounts receivables, payabales and cash ledger account and for fixed asset depreciation run.
The web service interface Manage AAR Run In enables you to connect external applications to your SAP Business ByDesign system and to create and start accounting adjustment runs. The web service interface Manage AAR Run In is relevant if your company wants to schedule accounting adjustment runs from external applications.
The web service interface Manage AAR Run In offers following operations
create_and_start_fxa_depr_run
create_and_start_cash_fcre_run
create_and_start_arp_fcre_run
create_and_start_prdla_ohc_run
Here is an example of a simple web service request:
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <Description languageCode="EN">Sample ARP FCRE Run</Description> <TestRunIndicator>true</TestRunIndicator> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Existence of referenced business documents:
The following business documents are only referenced and will not be created by the service operations. They should exist in the system already at the time the web service call:
Account Receivable Payable Accounts
Cash Ledger Accounts
Fixed Assets
Production Lots
For this web service, the change state ID does not apply to the Account Receivable Payables run, Cash Ledger run, Fixed Asset Depreciation run or Production Ledger Account overhead cost calculation run, as the run is only configured for creation and execution of the MDRO 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 foreign currency remeasurement run
Create and start cash ledger account foreign currency remeasurement run
Create and start fixed asset depreciation run
Create and start production ledger account overhead cost calculation run
Here is an example web service request to create an Accounts Payable ledger account foreign currency Remeasurement Run:
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample ARP FCRE Run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Here is an example web service request to create and start Accounts Receivable ledger account foreign currency remeasurement Run:
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample ARP FCRE Run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Here is an example web service request to create and start Cash ledger account foreign currency remeasurement Run:
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <CashLedgerAccountForeignCurrencyRemeasurementRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">SKDNFLSKDNF</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID>2015</FiscalYearID> </CashLedgerAccountForeignCurrencyRemeasurementRun> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Here is an example web service request to create and start Fixed Asset Depreciation Run:
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">SDNFLSNFL</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <AccountingClosingStepCode>010</AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
Here is a sample web service request to create and start a Production Ledger Account Overhead Cost Calculation run:
<n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <ProductionLedgerAccountOverheadCostCalculationRun> <ObjectNodeSenderTechnicalID/> <!--Optional:--> <Description languageCode="EN">TR Test A2X</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <PermanentEstablishmentID>MC67810</PermanentEstablishmentID> <!--Optional:--> <ProductionLotID>31</ProductionLotID> <AccountingClosingStepCode>010</AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </ProductionLedgerAccountOverheadCostCalculationRun> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest>
Description | Production ledger account overhead cost calculation run create and start run |
Name | CreateAndStartProductionLedgerAccountOverheadCostCalculationRun |
Synchronous | yes |
Release Status | Released |
To create and start production ledger account overhead cost calculation run
The request message of the operation create_and_start_prdla_ohc_run contains a BasicMessageHeader node, as well as a ProductionLedgerAccountOverheadCostCalculationRun node that contains the relevant selection data that is needed to create a production ledger account overhead cost calculation run (Overhead Run for Production Lots). The detailed structure of the ProductionLedgerAccountOverheadCostCalculationRun node will be explained in the following sub-chapters. This node can only occur once in a request - if more than one instance of this node occurs in the request, the run will only be created for the first one.
The response message type of the operation create_and_start_prdla_ohc_run contains log items, processing information and an account-specific node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as Run ID.
The ProductionLedgerAccountOverheadCostCalculationRun message node contains all the attributes relevant for creating an overhead run for production lots, such as company ID, set of books ID, etc.
There are some mandatory attributes that must be present in the request message in order to create and execute the run successfully. These are:
Company ID
Fiscal year
Fiscal period
Accounting Closing Step Code
If the XML request contains empty tag of any of the above then an appropriate error message is raised. Even if the empty tag is just not supplied then the service itself will fail and throw an exception against the corresponding elements |
Aside from these mandatory attributes, the request message has some other attributes to process the overhead cost calculation run:
Test Run Indicator
Description
Set of books ID
Permanent Establishment ID
Production Lot ID
This is a mandatory selection parameter in the request message for production ledger account overhead cost calculation run. If this is not given in the request message, or if the company ID is invalid, an error will be thrown and run will not be created.
Here is an example of a simple overhead cost calculation run with empty Company ID:
<n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <ProductionLedgerAccountOverheadCostCalculationRun> <ObjectNodeSenderTechnicalID/> <!--Optional:--> <Description languageCode="EN">TR Test A2X</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <PermanentEstablishmentID></PermanentEstablishmentID> <!--Optional:--> <ProductionLotID></ProductionLotID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </ProductionLedgerAccountOverheadCostCalculationRun> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest>
The following is the response of such a message:
<?xml version="1.0"?> <n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEC952D347769542C358EC: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:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation>
These is a mandatory selection parameter in the request message for production ledger account overhead cost calculation run. If these are not given in the request message, an error will be thrown and run will not be created.
Here is an example of a simple overhead cost calculation run with empty Fiscal Period:
<n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <ProductionLedgerAccountOverheadCostCalculationRun> <ObjectNodeSenderTechnicalID/> <!--Optional:--> <Description languageCode="EN">TR Test A2X</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <PermanentEstablishmentID></PermanentEstablishmentID> <!--Optional:--> <ProductionLotID></ProductionLotID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID></AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </ProductionLedgerAccountOverheadCostCalculationRun> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest>
The following is the response of such a message:
<?xml version="1.0"?> <n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEC952D347769542C358EC:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>007(/JOB_MESSAGE/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>MDRO instance is not active</Note> </Item> <Item> <TypeID>013(/FIA_PRDLA_SEC/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Select fiscal year and period for run execution</Note> </Item> <Item> <TypeID>062(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Combination of fiscal year 2016 and period 000 not permitted</Note> </Item> </Log> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation>
Here is the an example of a request message referring to a closed period in the fiscal year:
<n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <ProductionLedgerAccountOverheadCostCalculationRun> <ObjectNodeSenderTechnicalID/> <!--Optional:--> <Description languageCode="EN">TR Test A2X</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <PermanentEstablishmentID></PermanentEstablishmentID> <!--Optional:--> <ProductionLotID></ProductionLotID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </ProductionLedgerAccountOverheadCostCalculationRun> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest>
And the following is the expected response message:
<?xml version="1.0"?> <n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEC952D347769542C358EC:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>007(/JOB_MESSAGE/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>MDRO instance is not active</Note> </Item> <Item> <TypeID>006(/FIA_PERIOD_LOCK/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Fiscal year 2013 closed for set of books 0001 and company MC10000 (Akron Heating Technologies INC.)</Note> </Item> </Log> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation>
Here is the an example of a request message that does not have accounting closing step code value filled:
<n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <ProductionLedgerAccountOverheadCostCalculationRun> <ObjectNodeSenderTechnicalID/> <!--Optional:--> <Description languageCode="EN">TR Test A2X</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <PermanentEstablishmentID></PermanentEstablishmentID> <!--Optional:--> <ProductionLotID></ProductionLotID> <AccountingClosingStepCode></AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2017</FiscalYearID> </ProductionLedgerAccountOverheadCostCalculationRun> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleRequest>
And the following is the expected response message:
<?xml version="1.0"?> <n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAEC952D347769542C358EC:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <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 001 in fiscal year 2017 closed in set of books 0001 for closing step 000</Note> </Item> </Log> </n0:ProductionLedgerAccountOverheadCostCalculationRunCreateAndStartRunMessageBundleConfirmation>
This is an optional field. This indicator is used to specify whether the run is a test run or an update run. Value true indicates that it is a test run and value false indicates that it is an update run. If the flag is not set, it will default to true (test run).
This is an optional field and can be empty - in which case, the run description would be empty.
This is an optional field. If the tag is left empty, the run will be executed for all sets of books for the company.
This is an optional field. If it is left empty, run will be executed for all business residences associated with this company. If specified, the run will just be executed for the specified residence.
This is an optional field. If it is left empty, run will be executed for all production lots under this company. If specified, run will only be executed for this production lot.
Description | Fixed asset depreciation create and start run |
Name | CreateAndStartFixedAssetDepreciationRun |
Synchronous | yes |
Release Status | Released |
To create and start fixed asset depreciation run
The request message of the operation create_and_start_fxa_depr_run contains a BasicMessageHeader node element as well as a fixed_asset_depr_run message node element contains the selection data that is needed to create and execute fixed asset depreciation run. The detailed structure of the fixed_asset_depr_run node will be explained in the following sub-chapters. The fixed_asset_depr_run node can occur only once in the request message – this means that user is allowed to create and execute only one fixed asset depreciation run through a single web service request.
The response message type of the operation create_and_start_fxa_depr_run contains log items, processing information and an account-specific node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as Run ID.
The fixed_asset_depr_run message node element contains all generic attributes that is relevant for fixed asset depreciation run like company id, set of books id, etc.
There are few manadatory attributes that must be present in the request message to create and execute fixed asset depreciation run. The following are the attributes:
Company id
Account closing step 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 attribute to process the fixed asset depreciation run.
Test run indicator
Description
Set of books id
Fixed asset id
Sub asset id
Fixed asset class code
Fixed asset valuation view id
It is a mandatory selection parameter in the request message for fixed asset depreciation run. In case the request message fails to contain valid company id, appropriate error message would be thrown in the response message.
Here is an example of a simple fixed asset depreciation run with empty company id
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample FXA depreciation run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <AccountingClosingStepCode>010</AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:FixedAssetDepreciationRunCreateAndStartRunConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE3B8256FA3EEDA4D41B51: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:FixedAssetDepreciationRunCreateAndStartRunConfirmation>
It is a mandatory selection parameter in the request message for fixed asset depreciation run. In case the request message fails to contain valid account closing step code, appropriate error message would be thrown in the response message.
Here is an example of a simple fixed asset depreciation run with empty closing step code
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample FXA Depreciation run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <AccountingClosingStepCode></AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:FixedAssetDepreciationRunCreateAndStartRunConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE3B8256FA3EEDA4D41B51:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3 </MaximumLogItemSeverityCode> <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item>- <Item> <TypeID>024(/FIA_PERIOD_LOCK/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Period 001 in fiscal year 2016 closed in set of books 0001 for closing step 000</Note> </Item> </Log> </n0:FixedAssetDepreciationRunCreateAndStartRunConfirmation>
It is a mandatory selection parameter in the request message for fixed asset depreciation run. In case the request message fails to contain valid fiscal year or period, appropriate error message would be thrown in the response message.
Here is an example of a simple fixed asset depreciation run with empty fiscal period
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample FXA Depreciation run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID></AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:FixedAssetDepreciationRunCreateAndStartRunConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE3B8256FA3EEDA4D41B51:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3 </MaximumLogItemSeverityCode> <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item> <Item> <TypeID>062(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Combination of fiscal year 2016 and period 000 not permitted</Note> </Item> </Log> </n0:FixedAssetDepreciationRunCreateAndStartRunConfirmation>
Here is an example of a simple fixed asset depreciation run with empty fiscal year
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample FXA Depreciation run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID></FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:FixedAssetDepreciationRunCreateAndStartRunConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE3B8256FA3EEDA4D41B51:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3 </MaximumLogItemSeverityCode> <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item> <Item> <TypeID>062(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Combination of fiscal year 2016 and period 000 not permitted</Note> </Item> </Log> </n0:FixedAssetDepreciationRunCreateAndStartRunConfirmation>
Test run indicator decide 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 took abap_false i.e. update run
Here is an example of a simple test fixed asset depreciation run
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample FXA depreciation run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <AccountingClosingStepCode>010</AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
Here is an example of a simple update fixed asset depreciation run
Example 1:
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample FXA depreciation run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <AccountingClosingStepCode>010</AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
Example 2
<n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <FixedAssetDepreciationRun> <ObjectNodeSenderTechnicalID/> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample FXA depreciation run</Description> <!--Optional:--> <TestRunIndicator></TestRunIndicator> <AccountingClosingStepCode>010</AccountingClosingStepCode> <AccountingPeriodID>001</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </FixedAssetDepreciationRun> </n0:FixedAssetDepreciationRunCreateAndStartRunMessageBundleRequest>
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 fixed asset depreciation 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 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 fixed assets. Otherwise, the run would be executed only for the particular master fixed asset id and sub asset id.
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 fixed assets. Otherwise, the run would be executed only for all the fixed assets assigned to particular fixed asset class.
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 fixed assets. Otherwise, the run would be executed only for particular valuation view of all the fixed assets.
Description | Cash foreign currency remeasurement run create and start run |
Name | CreateAndStartCashLedgerAccountForeignCurrencyRemeasurementRun |
Synchronous | yes |
Release Status | Released |
To create and start cash ledger account foreign currency remeasurement run
The request message of the operation create_and_start_cash_fcre_run contains a BasicMessageHeader node element as well as a cash_fcre_run message node element contains the selection data that is needed to create and start cash ledger account foreign currency remeasurement run. The detailed structure of the cash_fcre_run node will be explained in the following sub-chapters. The cash_fcre_run node can occur only once in the request message – this means that user is allowed to create and execute only one cash ledger account foreign currency remeasurment run through a single web service request.
The response message type of the operation create_and_start_cash_fcre_run contains log items, processing information and an account-specific node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as Run ID and Run UUID.
The cash_fcre_run message node element contains all generic attributes that is relevant for cash foreign currency remeasurement run like company id, set of books id, etc.
There are few manadatory attributes that must be present in the request message to start and execute cash ledger account foreign currency remeasurement run. The following are the attributes:
Company id
Account closing step code
Fiscal year
Fiscal period
If the XML request contains empty tag of either of above elements 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 attribute to process the run.
Test Run Indicator
Description
Set of books id
Currency code
It is a mandatory parameter for cash ledger account foreign currency remeasurement run.
Here is an example of a simple cash ledger account foreign currency remeasurement run with empty company id
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <CashLedgerAccountForeignCurrencyRemeasurementRun> <ObjectNodeSenderTechnicalID/> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Cash FCRE Run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID>2015</FiscalYearID> </CashLedgerAccountForeignCurrencyRemeasurementRun> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the _response of similar request
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE216FD5585E1DD0B749E5: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:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Like in the cash foreign currency remeasurement run on the UI, customer have to provide appropriate account closing step code. The functionality and validation against the field would remain same.
The account closing step code is a mandatory parameter for cash ledger account foreign currency remeasurement run. In case empty tag of account closing step is provided in the service request, then web service will default the value '000' as account closing step code.
Here is an example of a simple cash ledger account foreign currency remeasurement run with empty account closing step code
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <CashLedgerAccountForeignCurrencyRemeasurementRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Cash fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <AccountingClosingStepCode></AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID>2015</FiscalYearID> </CashLedgerAccountForeignCurrencyRemeasurementRun> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the _response of similar request
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE216FD5585E1DD0B749E5:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3 </MaximumLogItemSeverityCode> <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item> <Item> <TypeID>024(/FIA_PERIOD_LOCK/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Period 012 in fiscal year 2015 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 001 in fiscal year 2016 closed in set of books 0001 for closing step 000</Note> </Item> </Log> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Both fiscal year and period are mandatory parameters like in foreign currency remeasurment run for cash in the UI. Hence, customer have to provide both the fields in the request message.
Scenario 1:
Here is an example of a simple cash ledger account foreign currency remeasurement run with empty fiscal period
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <CashLedgerAccountForeignCurrencyRemeasurementRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample cash fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID></AccountingPeriodID> <FiscalYearID>2015</FiscalYearID> </CashLedgerAccountForeignCurrencyRemeasurementRun> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the _response of similar request
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE216FD5585E1DD0B749E5:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3 </MaximumLogItemSeverityCode> <Item> <TypeID>001(/FIA_CASH_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Selections missing for fiscal year or period</Note> </Item> <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item> </Log> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Scenario 2:
Here is an example of a simple cash ledger account foreign currency remeasurement run with empty fiscal year
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <CashLedgerAccountForeignCurrencyRemeasurementRun> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Cash fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID></FiscalYearID> </CashLedgerAccountForeignCurrencyRemeasurementRun> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the _response of similar request
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE216FD5585E1DD0B749E5:804" xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <Log> <MaximumLogItemSeverityCode>3 </MaximumLogItemSeverityCode> <Item> <TypeID>001(/FIA_CASH_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Selections missing for fiscal year or period</Note> </Item> <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item> </Log> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Test run indicator decide 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 took abap_false i.e. update run
Here is an example of a simple test cash foreign currency remeasurement run
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<CashLedgerAccountForeignCurrencyRemeasurementRun>
<ObjectNodeSenderTechnicalID/>
<CompanyID></CompanyID>
<!--Optional:-->
<SetOfBooksID>0001</SetOfBooksID>
<!--Optional:-->
<Description languageCode="EN">Sample Cash FCRE Run</Description>
<!--Optional:-->
<TestRunIndicator>true</TestRunIndicator>
<!--Optional:-->
<CurrencyCode>USD</CurrencyCode>
<AccountingClosingStepCode>020</AccountingClosingStepCode>
<AccountingPeriodID>012</AccountingPeriodID>
<FiscalYearID>2015</FiscalYearID>
</CashLedgerAccountForeignCurrencyRemeasurementRun>
</n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Here is an example of a simple update cash foreign currency remeasurement run
Example 1:
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global">
<BasicMessageHeader/>
<CashLedgerAccountForeignCurrencyRemeasurementRun>
<ObjectNodeSenderTechnicalID/>
<CompanyID></CompanyID>
<!--Optional:-->
<SetOfBooksID>0001</SetOfBooksID>
<!--Optional:-->
<Description languageCode="EN">Sample Cash FCRE Run</Description>
<!--Optional:-->
<TestRunIndicator>false</TestRunIndicator>
<!--Optional:-->
<CurrencyCode>USD</CurrencyCode>
<AccountingClosingStepCode>020</AccountingClosingStepCode>
<AccountingPeriodID>012</AccountingPeriodID>
<FiscalYearID>2015</FiscalYearID>
</CashLedgerAccountForeignCurrencyRemeasurementRun>
</n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Example 2:
<n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader/> <CashLedgerAccountForeignCurrencyRemeasurementRun> <ObjectNodeSenderTechnicalID/> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Cash FCRE Run</Description> <!--Optional:--> <TestRunIndicator></TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>012</AccountingPeriodID> <FiscalYearID>2015</FiscalYearID> </CashLedgerAccountForeignCurrencyRemeasurementRun> </n0:CashLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
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 cash ledger account foreign currency remeasurement 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 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 regardless of any particular currency code. Otherwise, the run would be executed only for the particular currency code.
Description | Account receivable payable foreign currency remeasurement run create and start run |
Name | CreateAndStartAccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun |
Synchronous | yes |
Release Status | Released |
To create and start accounts receivable payable ledger account foreign currency remeasurement run
The request message of the operation create_and_start_arp_fcre_run contains a BasicMessageHeader node element as well as an arp_fcre_run message node element contains the selection data that is needed to created accounts receivable payable ledger account foreign currency remeasurement run. The detailed structure of the arp_fcre_run node will be explained in the following sub-chapters. The arp_fcre_run node can occur only once in the request message – this means that user is allowed to create only one either accounts payables or receivable ledger account foreign currency remeasurment run through a single web service request.
The response message type of the operation create_and_start_arp_fcre_run contains log items, processing information and an account-specific node with ReferenceObjectNodeSenderTechnicalID, ChangeStateID, as well as Run ID.
The arp_fcre_run message node element contains all generic attributes that is relevant for accounts receivable payable foreign currency remeasurement run like company id, set of books id, party role category code etc.
There are few manadatory attributes that must be present in the request message to start and execute accounts receivable payable ledger account foreign currency remeasurement run. The following are the attributes:
Company id
Account 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 attribute to process the accounts receivable or payable ledger accounts foreign currency remeasurement run.
Test Run Indicator
Description
Set of books id
Currency code
Business partner ids
It is a mandatory selection parameter in the request message for both accounts receivable and payable ledger account foreign currency remeasurement run.
Here is an example of a simple payable ledger accounts foreign currency remeasurement run with empty company id
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID></CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Payable fcre run wo company id</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7:804"> <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:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
The account closing step code is a mandatory parameter for both accounts receivable or payable ledger account foreign currency remeasurement run. In case empty tag of account closing step is provided in the service request, then web service will default the value '000' as account closing step code.
Here is an example of a simple payable ledger account foreign currency remeasurement run with empty account closing step code
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Payable fcre run wo closing step</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode></AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7:804"> <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>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</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> </Log> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
The party role category code differenciate the run whether it is a payable ledger account foreign currency remeasurement run or receivable ledger account foreign currency remeasurement run.
User Interface | PartyRoleCategoryCode |
---|---|
Payable Foreign Currency Remeasurement Run | 3 |
Receivable Foreign Currency Remeasurement 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 foreign currency remeasurement run with empty party role category code.
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample fcre run wo party role</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode></PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7:804"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>005(/FIA_ARP_FCR_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>006(/FIA_ARP_FCR_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Business partner MC9785 (Silverstar Wholesale Corp) not found</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Here is an example of a simple payable foreign currency remeasurement run
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample Payable fcre run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Here is an example of a simple receivable foreign currency remeasurement run
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable fcre run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Both fiscal year and period are mandatory parameters like in foreign currency remeasurment run for payables and receivables in the UI.
Here is an example of a simple payable foreign currency remeasurement run without fiscal period
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample payable fcre wo fiscal period</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID></AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7: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_FCR_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Selections are missing for fiscal year or period</Note> </Item>- <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Here is an example of a simple payable foreign currency remeasurement run without fiscal year
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample payable fcre wo fiscal year</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID></FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7: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_FCR_BL/)</TypeID> <CategoryCode>INC.COI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Selections are missing for fiscal year or period</Note> </Item> <Item> <TypeID>094(/AP_ESI_COMMON/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Action SCHEDULE_DIRECTLY not possible; action is disabled</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Test run indicator decide 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 took abap_false i.e. update run
Here is an example of a simple test receivable ledger account foreign currency remeasurement run
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable test fcre run</Description> <!--Optional:--> <TestRunIndicator>true</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Here is an example of a simple update receivable foreign currency remeasurement run
Scenario 1:
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable update fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
Scenario 2:
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable update fcre run</Description> <!--Optional:--> <TestRunIndicator></TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>4</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
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 foreign currency remeasurement 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 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 regardless of any particular currency code. Otherwise, the run would be executed only for the particular currency code.
Unlike other parameter, selection by business partner is a zero to many relationship; that means customer can choose to execute the run with or without the business partner as selection parameter. Customer can choose more than one business partner to filter the number of affecting payables or receivable accounts.
Here is an example of a simple update receivable foreign currency remeasurement run
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample receivable update fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC*</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
In the selection of business partner can be achieved using Interval inclusion exclusion code and interval boundary type code. The web service request can contain either of the inclusion or exclusion code in the service, but we allow only Equals and between as boundary type code in the accounts receivables payables ledger account foreign currency remeasurement run.
Here are few cases of incorrect usage of boundary type codein test receivable ledger account foreign currency remeasurement run along with the erroneous response message
Case 1:
if service request contains boundary type code other than 'Equals' or 'Between'
Here is an example of a simple payable foreign currency remeasurement test run
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample payable test fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <!--Zero or more repetitions:--> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>6</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier/> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7:804"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>089(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Interval Boundary Type Code 'Less Than' is not valid. Please use 'Equal To' or 'Between'</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Case 2:
If service request contains 'Equal' as boundary type code and have both lower boundary and upper boundary provided.
Here is an example of a simple payable foreign currency remeasurement test run
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample test payable fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>1</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> <!--Optional:--> <UpperBoundaryIdentifier>MC9786</UpperBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7:804"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>091(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Interval Boundary Type Code 'Equal To' is invalid as upper boundary is provided</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>
Case 3:
If service request contains 'Between' as boundary type code and only lower boundary type code is provided.
Here is an example of a simple payable foreign currency remeasurement test run
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest xmlns:n0="http://sap.com/xi/SAPGlobal20/Global"> <BasicMessageHeader> <!--Optional:--> <ID/> <!--Optional:--> <UUID/> <!--Optional:--> <ReferenceID/> <!--Optional:--> <ReferenceUUID/> </BasicMessageHeader> <AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> <!--Optional:--> <ObjectNodeSenderTechnicalID/> <CompanyID>MC10000</CompanyID> <!--Optional:--> <SetOfBooksID>0001</SetOfBooksID> <!--Optional:--> <Description languageCode="EN">Sample test payable fcre run</Description> <!--Optional:--> <TestRunIndicator>false</TestRunIndicator> <!--Optional:--> <CurrencyCode>USD</CurrencyCode> <PartyRoleCategoryCode>3</PartyRoleCategoryCode> <SelectionByBusinessPartnerID> <!--Optional:--> <InclusionExclusionCode>I</InclusionExclusionCode> <IntervalBoundaryTypeCode>3</IntervalBoundaryTypeCode> <!--Optional:--> <LowerBoundaryIdentifier>MC9785</LowerBoundaryIdentifier> </SelectionByBusinessPartnerID> <AccountingClosingStepCode>020</AccountingClosingStepCode> <AccountingPeriodID>003</AccountingPeriodID> <FiscalYearID>2016</FiscalYearID> </AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRun> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleRequest>
The following would be the response of similar request
<n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation xmlns:n0="http://sap.com/xi/SAPGlobal20/Global" xmlns:prx="urn:sap.com:proxy:ACL:/1SAI/TAE1F07E8BE36965D462DB7:804"> <Log> <MaximumLogItemSeverityCode>3</MaximumLogItemSeverityCode> <Item> <TypeID>090(/FIA_ACC_ADJUSTMENT/)</TypeID> <CategoryCode>INC.BOI</CategoryCode> <SeverityCode>3</SeverityCode> <Note>Interval Boundary Type Code 'Between' is invalid as upper boundary is missing</Note> </Item> </Log> </n0:AccountsReceivablePayableLedgerAccountForeignCurrencyRemeasurementRunCreateAndStartRunMessageBundleConfirmation>