List of Journeys
Most Journeys are used in the field mapping process to assist in determining for which business process what fields should be used for taxability determination. Some Journeys are used internally for unique treatment of a process, like Freight and Plants Abroad for example, these are mostly likely not used in the field mapping.
Journey | Description |
/IDT/JOURNEY_HEADER_REQUEST | This Journey manages header data going from SAP to Determination. In field mappings this Journey passes data to link specific header SAP fields to corresponding invoice level XML elements of Determination. |
/IDT/JOURNEY_HEADER_REQUEST_GM | This Journey manages header data going from SAP to Determination for the Goods Movement product transactions. In field mappings this Journey passes data to link specific header SAP fields to corresponding invoice level XML elements of Determination for materials movement transactions in MM. |
/IDT/JOURNEY_HEADER_REQ_BR_GM | This Journey manages the header data going from SAP to Determination for the Brazil material transaction MBOA for receiving inbound transaction on Intra Co STO process. |
/IDT/JOURNEY_GET_CONDITION_DTL | This journey is used internally and gets the relevant tax data from the KONV table and uses that for getting the taxes on the NF document when a PGI is done on the delivery document. Brazil functions only. |
/IDT/JOURNEY_ITEM_REQUEST | This Journey manages header and item data going from SAP to Determination. In field mappings this Journey passes data to link specific header and item SAP fields to corresponding line level XML elements of Determination. |
/IDT/JOURNEY_ITEM_REQ_BR_GM | This Journey manages the item data going from SAP to Determination for the Brazil material transaction MBOA for receiving inbound transaction on Intra Co STO process. |
/IDT/JOURNEY_ITEM_REQUEST_GM | This Journey manages header and item data going from SAP to Determination for the Goods Movement product transactions. In field mappings this Journey passes data to link specific header and item SAP fields to corresponding line level XML elements of Determination for materials movement transactions in MM. |
/IDT/JOURNEY_NG_ITEM_REQUEST | This Journey manages header and item data going from non-group transactions of SAP to Determination. In field mappings this Journey passes data to link specific header and item SAP fields to corresponding line level XML elements of Determination. |
/IDT/JOURNEY_NG_ITEM_SERV_ENTR | This Journey manages item level data going from SAP to Determination for the specific data in Service Entry Sheets within MM PO process. In field mappings this Journey passes data to line specific line-item SAP fields to corresponding line level XML elements of Determination for Service Entry Sheet charges. |
/IDT/JOURNEY_MULTI_ACC_SERVICE | This journey manages the multi account assignment as it is used on a service entry sheet line-item. |
/IDT/JOURNEY_TAX_TAB_RESPONSE | This Journey manages data coming from Determination to SAP. It collects the tax calculation results from the XML and will use the configurable field mappings to link specific Determination fields to corresponding fields in table /IDT/D_TAX_DATA for later use in downstream processes such as invoice printing and reporting. |
/IDT/JOURNEY_STANDARD_RESPONSE | This Journey manages data coming from Determination to SAP. It collects the tax calculation results from the XML and distributes them in condition value formulas where needed. It will use the configurable field mappings to link specific Determination fields to corresponding SAP fields in table KONV. NOTE: This mapping is provided for backwards compatibility and should not be used. |
/IDT/JOURNEY_AUDIT_UPD_DB_BILL | This Journey manages the update to the Determination audit database for Billing documents. At time of SAP finishing posting to the General Ledger account a call will be made to Determination for persisting the tax liability in audit. The process will use the latest calculation done and sets the IS_AUDITED flag to TRUE, the FISCAL_DATE to the posting date of the Billing document, the INVOICE_NUMBER and UNIQUE_INVOICE_NUMBER and the GROSS_AMOUNT in company code currency. It also may set the IS_CREDIT flag to TRUE/FALSE to negate amounts and make the audit reports add up correctly. NOTE: In some cases, a certain value isn’t known till the document has been posted to the G/L, i.e. the legal document number required in some countries. This Journey can be used to write the value to audit, but it would not be recommended to use such a value for taxability rules as the value would not be available during calculations. |
/IDT/JOURNEY_AUDIT_UPD_DB_SETL | This Journey manages the update to the Determination audit database for both Settlement Management sales and purchase billing documents. This journey is identical to /IDT/JOURNEY_AUDIT_UPD_DB_BILL for Settlement Management Audit documents. (New Journey from Release 6.6.0.0 ) |
/IDT/JOURNEY_AUDIT_UPD_DB_GL | This Journey manages the update to the Determination audit update database for G/L documents when there is no billing document. It is using the route /IDT/ROUTE_UPDATE_AUDIT_DB and is used to add information to the update to audit table and report for noting that status of an entry that may not have been posted yet to the audit database. |
/IDT/JOURNEY_AUDIT_SAVE_FRM_GL | This Journey manages the update to the Determination audit database for G/L (LIV/FI) documents. At time of SAP finishing posting to the General Ledger account a call will be made to Determination for persisting the tax liability in audit. The process will use the latest calculation done and sets the IS_AUDITED flag to TRUE, the FISCAL_DATE to the posting date of the G/L document, the INVOICE_NUMBER and UNIQUE_INVOICE_NUMBER and the GROSS_AMOUNT in company code currency. It also may set the IS_CREDIT flag to TRUE/FALSE to negate amounts and make the audit reports add up correctly. NOTE: In some cases, a certain value isn’t known till the document has been posted to the G/L, i.e. the legal document number required in some countries. This Journey can be used to write the value to audit, but it would not be recommended to use such a value for taxability rules as the value would not be available during calculations. |
/IDT/JOURNEY_AUDIT_SAVE_TAX_UP | This journey manages the update to the audit database and will be used for all manual tax scenarios (calculate tax = “ “) and down payments. To update the audit database, this will use the last tax calculation make changes to a few fields like override amount and then send that to audit. |
/IDT/JOURNEY_AUDIT_RESPONSE | This Journey manages the response of the update to the Audit Database. It determines if an update to the Audit Database is successful from the response message and passes a flag with that information to be stored in table /IDT/D_AUDIT_STA. |
/IDT/JOURNEY_AUDIT_SAVE | This Journey saves the data of the last tax calculation call at the time of saving the invoice document in table /IDT/D_AUDIT_REC for later use in the audit update call, cancellations, and other processes. This journey assumes calculate tax = X |
/IDT/JOURNEY_BRAZIL_SD_ADJUST | This Journey adjusts the Brazil SD document and process when use to set the application area from TX to V. This was done to allow the system to utilize the standard Nota Fiscal mapping logic in SD for Brazil |
/IDT/JOURNEY_CHECK_AUDIT_MESS | This Journey checks the audit message and adjusts the call to audit. It does a double check to make sure the call is for a final invoice. |
/IDT/JOURNEY_GM_RESPONSE | This Journey manages the response of the update to the Audit Database for Goods Movement transactions in the Goods Movement product. |
/IDT/JOURNEY_US_SPECIAL_LOGIC2 | This Journey manages the AP logic for countries like US, and PR by switching the company role for the Vendor Charged Tax and offsetting the tax lines for Self-Accrual taxes. NOTE: Customers most likely will not use this in the field mappings; the default is delivered by Thomson Reuters. |
/IDT/JOURNEY_FREIGHT | This Journey manages the Freight logic based on the configurable Freight condition sub-total. It will create a shadow line as a related line to the product line. See the Configuration Guide for more details. NOTE: This journey is not used in the field mappings. |
/IDT/JOURNEY_FREIGHT_LIV | This Journey manages the Freight logic based on the configurable Freight condition sub-total specifically for functions that are different within the MIRO transaction. It will create a shadow line as a related line to the product line. |
/IDT/JOURNEY_PLANTS_ABROAD | This Journey manages the logic for Plants Abroad based on the billing types maintained in table /IDT/D_PLNTS_ABD. For these billing types a Seller and Buyer call is made for the one SD Invoice. Billing type WIA has been added as a default. NOTE: This journey is not used in the field mappings. |
/IDT/JOURNEY_FB05_RESPONSE | This Journey is to handle the complexity of the transactions that can have cash discounts. |
/IDT/JOURNEY_NG_ITEM_FB05 | This Journey manages header and item data going from non-group cash discount transactions of SAP to Determination. In field mappings this Journey passes data to link specific header and item SAP fields to corresponding line level XML elements of Determination. |
/IDT/JOURNEY_FB05_COMPANY_ROLE | This Journey manages the company role for the FB05 transaction logic. |
/IDT/JOURNEY_NG_ITEM_DOWN_PAYM | This Journey is to handle the complexity of the down payment transactions. |
/IDT/JOURNEY_NG_ITEM_SERV_ENTR | This Journey is to handle the complexity of the transactions with service entry sheets. |
/IDT/JOURNEY_SELF_ASSESSMENT | This Journey is used to handle the special fields needed in tandem with the table transaction /IDT/OFFSET_CONFIG to handle the offsetting side entry needed for self-assessment transactions. |
/IDT/JOURNEY_UTILITY_RESPONSE | A Journey that allows a user-exit to read tax result data before the tax data table has been updated. This is not used in any standard function but can be used by a customer for custom user exit data that needs to be retrieved from the response prior to posting to the tax data table. |
/IDT/JOURNEY_MULTI_ACC_ASSIGN | This journey is used to handle the complexity of the logic needed for multiple account assignment within a single PO line-item. |
/IDT/JOURNEY_INDIA_STO_INB | This journey is used to handle the complexity of the logic needed for the J_1IG_INV inbound invoice for STO transaction. |
/IDT/JOURNEY_ADDRESSES | This journey is used to handle the complexity of the logic needed for collecting address data. |
/IDT/JOURNEY_ITEM_REQ_DT_RC | This Journey manages item data going from SAP to Determination for Deferred taxes Reverse charge scenarios. (New Journey from Release 6.6.0.0) |