Skip to main content

Appendix A: Loading Additional Customer-Specific Data in SAP S/4HANA

This appendix provides an example of how to map and load the additional data from your source system into SAP S/4HANA.

Using FIN%Tables

The following tables have been updated with additional fields in SAP Central Finance 2021 to support SAP S/4HANA 2021:

FIN_HEADER

  • TRANSACTION_TYPE: Defines whether document creation or change is done. For document creation, this field must be left blank. For document change, enter 'C'.
  • LEDGER_GROUP: Defines the ledger group of an accounting document. By posting in a ledger group, you can post the document in the specific ledgers assigned to that ledger group in the SAP Central Finance system.
  • OBJECT_TYPE: Defines the object type of an accounting document. This field corresponds to the BKPF-AWTYP field. So far, there was only one AWTYP field called CF3P for the third party interface. It was set automatically while replicating a document. Now, the new AWTYPs namely 'CF3PS', 'CF3PM' and 'CF3PG' are introduced to support SAP S/4HANA 2021.
  • GLO_REFERENCE1 to GLO_REFERENCE5: Indicates the country or region specific reference number 1 to 5 in the document. It is used in specific ACR tax reports depending on the country.
  • GLO_DATE1 to GLO_DATE5: Indicates the country or region specific date from 1 to 5 in the document. It is used in specific ACR tax reports depending on the country.
  • GLO_BUSINESS_PARTNER1and GLO_BUSINESS_PARTNER2: Indicates the country or region specific business partner 1 and 2 in the document. It is used in specific ACR tax reports depending on the country.

FIN_ACCT

  • PURCHASING_DOC_NO: Indicates the purchasing document number. If you are using the Central Accruals Management with the Accounting Views of Logistics for Purchase Orders, you need to enter the purchase order number of the source system.

  • PURCHASING_LOGSYS: Indicates the logical system of the purchasing document. If you are using the Central Accruals Management with the Accounting Views of Logistics for Purchase Orders you need to enter the source logical system of the purchase order number.

  • REFERENCE_1 to REFERENCE_3: Indicates the reference key 1 to 3 for the line item.

  • GLO_REFERENCE1: Indicates the country or region specific reference number from1 to 5 in the document. It is used in specific ACR tax reports depending on the country.

FIN_DEBIT

  • PAYMENT_TERMS: Indicates the terms of payment key. The DISCOUNT_FIRST_DAYS, DISCOUNT_FIRST_PERCENT, DISCOUNT_SECOND_DAYS, DISCOUNT_SECOND_PERCENT, and NET_TERMS fields are not derived from this field in SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA. Enter this field only for reporting purpose.
  • FIXED_PAYMENT_TERMS: Indicates the fixed payment terms.
  • PARTNER_BANK_TYPE: Indicates the partner bank type.
  • PURCHASING_DOC_NO: Indicates the purchasing document number.
  • PURCHASING_LOGSYS: Indicates the logical system of purchasing document.
  • GLO_REFERENCE1: Indicates the country or region specific reference number from1 to 5 in the document. It is used in specific ACR tax reports depending on the country.
  • ORG_LINE_NO: Indicates the line number of the original credit or debit line for which the withholding tax is linked.

FIN_CREDIT

The FIN_CREDIT table has the same additional fields as the FIN_DEBIT table.

FIN_PRDTAX

ORG_LINE_NO: Indicates the line number of the original credit or debit line for which the withholding tax is linked.

FIN_WHTAX

  • ORG_LINE_NO: Indicates the line number of the original credit or debit line for which the withholding tax is linked.
  • MANUALLY_AMT_TAX_INDICATOR: Indicates the withholding tax amount. Enter 'X' if the AMT_TAX_DOCUMENT_CURR, AMT_TAX_COMP_CODE_CURR, or AMT_TAX_GROUP_CURR fields contain values other than 0.
  • MANUALLY_AMT_BASE_INDICATOR: Indicates the withholding tax base amount. Enter 'X' if the AMT_TAX_DOCUMENT_CURR, AMT_TAX_COMP_CODE_CURR, or AMT_TAX_GROUP_CURR fields contain values other than 0.

Default Reference Fields for Balances and Journals Jobs

For the Balances and Journals jobs to run accurately, the following reference fields for various source systems must contain the default value provided in the SAP Central Finance Transaction Replication by insightsoftware for SAP S/4HANA.

Important: Overwriting these reference fields during extraction may impact the reconciliation report data.

MAGNITUDE_STG_ONE Table

Source System

 Reference Field

Oracle E-Business Suite, JD Edwards EnterpriseOne, Oracle PeopleSoft, Microsoft Dynamics GP, Microsoft Dynamics 365 Finance and Operations, Microsoft Dynamics 365 Business Central (On-premises and Cloud), Infor LN (On-Premises), Flat File

REFERENCE_COLUMN_4 = UFF_STG_TEMP.NATURAL_ACCOUNT

REFERENCE_COLUMN_6 = UFF_STG_TEMP.LINE_NUMBER_ORIG

REFERENCE_COLUMN_10 = decode( $G_ERP = 'JDE', UFF_STG_TEMP.DOC_NUMBER, UFF_STG_TEMP.HEADER_ID)

REFERENCE_COLUMN_11 = UFF_STG_TEMP.COMPANY_CODE

REFERENCE_COLUMN_13 = decode( $G_ERP = 'JDE', UFF_STG_TEMP.REFERENCE2, $G_ERP = 'EBS', UFF_STG_TEMP.ORDER_NUMBER, ' ')

Microsoft Dynamics NAV

REFERENCE_COLUMN_9 = ACCOUNT_TYPE

REFERENCE_COLUMN_10 = BELNR

REFERENCE_COLUMN_11 = COMPANY_CODE

REFERENCE_COLUMN_13 = ORDER_NUMBER

FIN% Tables

Source System

 Table Reference Field

Oracle E-Business Suite, JD Edwards EnterpriseOne, Oracle PeopleSoft, Microsoft Dynamics GP, Microsoft Dynamics 365 Finance and Operations, Microsoft Dynamics 365 Business Central (On-premises and Cloud), Infor LN (On-Premises), Flat File

HEADER

REFERENCE_3 = UFF_STG_TEMP.OBJECT_KEY_SOURCE

REFERENCE_4 = UFF_STG_TEMP.OBJECT_KEY_REV_SOURCE

REFERENCE_5 = UFF_STG_TEMP.FI_MODULE

REFERENCE_8 = UFF_STG_TEMP.COMPANY_CODE

REFERENCE_10 = UFF_STG_TEMP.SENDER_SYSTEM_ID
ACCT

REFERENCE_6 = UFF_STG_TEMP.LINE_NUMBER_ORIG

REFERENCE_8 = UFF_STG_TEMP.COMPANY_CODE

REFERENCE_10 = UFF_STG_TEMP.SENDER_SYSTEM_ID
PRDTAX

REFERENCE_6 = UFF_STG_TEMP.LINE_NUMBER_ORIG

REFERENCE_8 = UFF_STG_TEMP.COMPANY_CODE

REFERENCE_10 = UFF_STG_TEMP.SENDER_SYSTEM_ID
CREDIT

REFERENCE_6 = UFF_STG_TEMP.LINE_NUMBER_ORIG

REFERENCE_8 = UFF_STG_TEMP.COMPANY_CODE

REFERENCE_10 = UFF_STG_TEMP.SENDER_SYSTEM_ID
DEBIT

REFERENCE_6 = UFF_STG_TEMP.LINE_NUMBER_ORIG

REFERENCE_8 = UFF_STG_TEMP.COMPANY_CODE

REFERENCE_10 = UFF_STG_TEMP.SENDER_SYSTEM_ID
WHTAX

REFERENCE_6 = UFF_STG_TEMP.LINE_NUMBER_ORIG

REFERENCE_8 = UFF_STG_TEMP.COMPANY_CODE

REFERENCE_10 = UFF_STG_TEMP.SENDER_SYSTEM_ID

Microsoft Dynamics AX

 HEADER

REFERENCE_2 = OBJECT_LOGSYS

REFERENCE_10 = $G_SOURCE_SYSTEM

ACCT

REFERENCE_2 = OBJECT_LOGSYS

REFERENCE_10 = $G_SOURCE_SYSTEM

REFERENCE_1 = NVL(Validation_amount_Pass.TRANS_TYPE,' ')

PRDTAX

REFERENCE_2 = OBJECT_LOGSYS

REFERENCE_10 = $G_SOURCE_SYSTEM

CREDIT

REFERENCE_2 = OBJECT_LOGSYS

REFERENCE_10 = $G_SOURCE_SYSTEM

REFERENCE_3 = nvl(Validation_Lifnr_Pass.PAYMENT_TERMS,'')

DEBIT

REFERENCE_2 = OBJECT_LOGSYS

REFERENCE_10 = $G_SOURCE_SYSTEM

REFERENCE_3 = nvl(Validation_Lifnr_Pass.PAYMENT_TERMS,'')

WHTAX

REFERENCE_2 = OBJECT_LOGSYS

REFERENCE_10 = $G_SOURCE_SYSTEM

Microsoft Dynamics NAV HEADER REFERENCE_10 = $SOURCE_SYSTEM

Using Withholding Tax Clearing Table for Flat File Source

The FIN_CLRWHT table is added to enable the clearing of withholding tax open items for the Flat File source system. The table has the following fields:

  • UNIQUE_ID: Indicates the unique identifier. It is required to ensure the uniqueness of the data entered across multiple data sources (systems and organizational units). It is used as key field building the relation between header and item information.
  • LINE_NUMBER: Indicates the line number.
  • OPEN_ITEM_DOCUMENT_NO: Indicates the open item document number in the sender system.
  • OPEN_ITEM_FISCAL_YEAR: Indicates the fiscal year of the open item document in the sender system.
  • OPEN_ITEM_ITEMNO_ACC: Indicates the item number in the open item document.
  • OPEN_ITEM_DOC_LINE_NO: Indicates the line item number in the open item document in the sender system.
  • WITHHOLDING_TAX_TYPE: Indicates the indicator for withholding tax type.
  • WITHHOLDING_TAX_CODE: Indicates the Withholding Tax Code. If it is blank, it means that withholding tax must not be calculated.
  • DOCUMENT_CURR_ISO: Indicates the ISO code of the document currency. A value must be entered if the AMT_TAX_DOCUMENT_CURR of AMT_BASE_DOCUMENT_CURR field contains amount other than 0.
  • AMT_TAX_DOCUMENT_CURR: Indicates the tax amount in document currency. If the withholding tax amount is provided, the document currency value must be entered.
  • COMP_CODE_CURR_ISO: Indicates the ISO code of the company code currency. A value must be entered if the AMT_TAX_COMP_CODE_CURR of AMT_BASE_COMP_CODE_CURR field contains amount other than 0.
  • AMT_TAX_COMP_CODE_CURR: Indicates the withholding tax base amount in the document currency. It is an optional field and if left blank, it is calculated automatically from the AMT_TAX_DOCUMENT_CURR field.
  • AMT_BASE_DOCUMENT_CURR: Indicates the withholding tax base amount in the company currency. If the withholding tax amount is provided, the document currency value must be entered.
  • AMT_BASE_COMP_CODE_CURR: Indicates the withholding tax base amount in the company currency. It is an optional field and if left blank, it is calculated automatically from the AMT_BASE_DOCUMENT_CURR field.
  • MANUALLY_AMT_TAX_INDICATOR: Indicates the withholding tax amount. It is set to 'X' if the AMT_TAX_DOCUMENT_CURR, AMT_TAX_COMP_CODE_CURR, or AMT_TAX_GROUP_CURR fields contain values other than 0.
  • MANUALLY_AMT_BASE_INDICATOR: Indicates the withholding tax base amount. It is set to 'X' if the AMT_TAX_DOCUMENT_CURR, AMT_TAX_COMP_CODE_CURR, or AMT_TAX_GROUP_CURR fields contain values other than 0.
  • GROUP_CURR_ISO: Indicates the ISO code of the group currency. A value must be entered if the AMT_TAX_GROUP_CURR of AMT_BASE_GROUP_CURR field contains amount other than 0.
  • AMT_TAX_GROUP_CURR: Indicates the withholding tax amount in group currency.
  • AMT_BASE_GROUP_CURR: Indicates the withholding base amount in group currency.

Using Customer Extensibility Tables

In addition to the header information that is loaded into the SLT Replication Server through the /1LT/CF_E_HEADER staging table and the line information through the /1LT/ CF_E_ACCT, /1LT/CF_E_DEBIT, /1LT/CF_E_CREDIT, /1LT/CF_E_PRDTAX, /1LT/CF_E_CLRITM, and /1LT/CF_E_WHTAX staging tables, you may have custom data that you want to load into SAP S/4HANA.

In such cases, you can use the customer extensibility staging tables /1LT/CF_E_EXTENT and /1LT/CF_E_EXT_IT to load the additional header and line-level details from your source system into SAP S/4HANA. The tables contain the following fields:

/1LT/CF_E_EXTENT

  • UNIQUE_ID: Is used to join to the Accounting Document Header entry in the /1LT/CF_E_HEADER table
  • CUST_EXTENSION: Stores the additional data of data types, such as CLOB, in the Oracle Database

/1LT/CF_E_EXT_IT

  • UNIQUE_ID: Is used to join to the Accounting Document Header entry in the /1LT/CF_E_HEADER table
  • ITEM_NUMBER: Is used to join to Accounting Document Item with ITEMNO_ACC column in the /1LT/CF_E_ACCT, /1LT/CF_E_DEBIT, /1LT/CF_E_CREDIT, /1LT/CF_E_PRDTAX, or /1LT/CF_E_WHTAX table containing line-level details.
  • CUST_EXTENSION: Stores a large amount of data of data types, such as CLOB, in the Oracle Database

The custom information is stored as XML tags in the CUST_EXTENSION column of the tables.

xmlgen_proc

The xmlgen_proc procedure is available as a template at the staging database level to populate the FIN% extension tables and load the custom fields.

xml_data_tables

The tables in xml_data_tables.sql file are used in xmlgen_proc procedure and must be installed before creating the procedure.

Using Profitability Analysis Tables

The FIN_COPA table is added to include the profitability analysis functionality in SAP Central Finance 2021. The table has the following fields:

  • UNIQUE_ID: Indicates the unique identifier. It is required to ensure the uniqueness of the data entered across multiple data sources (systems and organizational units). It is used as key field building the relation between header and item information.
  • ITEM_NUMBER: Indicates the item number.
  • FIELDNAME: Indicates the field name for the CO-PA criteria.
  • VALUE: Indicates the value of the CO-PA criteria.
  • MATERIAL_NO: Indicates the value of the CO-PA criteria material.

Migration of GL Open Items

For Oracle E-Business Suite and Oracle PeopleSoft, perform the following procedures to extract the GL open items and load them into the SAP S/4HANA system:

To extract and load GL open items

  1. In SAP Data Services Designer, import the EBS_GL_OPEN_ITEM.atl or PSFT_GL_OPEN_ITEM.atl file located at <SetupFolder>\<StagingDatabase>\Mappings into your SAP Data Services repository. The following jobs are created under EBS_GL_OPEN_ITEM and PSFT_GL_OPEN_ITEM projects:

    • Master_Lookup_Load
    • JOB_EBS_GL_ACCT/ JOB_PSFT_GL_ACCT
    • JOB_EBS_GL_DOC/ JOB_PSFT_GL_DOC
    • JOB_EBS_GL_OPEN_ITEM_OT/ JOB_OT_GL_OPEN_ITEMS
  2. For both Oracle E-Business Suite and Oracle PeopleSoft, create the two tables, namely GL_OPEN_ITEM_ACCTS and GL_OPEN_ITEM_DOCS, by using the scripts located in the <SetupFolder>\<StagingDatabase>\Scripts\Parallel_scripts folder.
  3. Run the Master_Lookup_Load job to load the lookup table.
  4. Run the JOB_EBS_GL_ACCT and JOB_EBS_GL_DOC jobs to load the data from the respective spreadsheets to the tables in the Oracle E-Business Suite and Oracle PeopleSoft sources.
  5. Update the values of the applicable global variables for your source system before running the final job pertaining to GL open items. For information about the list of applicable global variables, see Global Variables in Appendix B.
  6. Run the JOB_EBS_GL_OPEN_ITEM_OT /JOB_OT_GL_OPEN_ITEMS job. The open items are extracted and loaded into the SAP S/4HANA system.

Loading Additional Data into SAP S/4HANA

This section explains how to load the additional data from your source system into SAP S/4HANA.

The high-level process is as follows:

  1. Locate the Business Add-in (BAdI), BADI_FINS_CFIN_EX_INTF, at the following path in SAP GUI: Financial Accounting > Central Finance > BAdIs: Central Finance > BAdI: Enhance Processing of Posting Data from Third-Party Systems.
  2. Go to the BAdI Builder: Initial Screen for Definitions window.
  3. View the details of the BAdI, BADI_FINS_CFIN_EX_INTF.
  4. Create an implementation, such as Z_BADI_CFIN_EXT_INTERFACE.
  5. Create an implementation class, such as CL_IM_FINS_CFIN_EX_INTF.
  6. Implement the Interface methods MAP_TO_BAPI and FILL_BAPI_MISSING_FIELDS.
  7. Place the required code in the methods to map the additional data in the /1LT/CF_E_EXTENT and /1LT/CF_E_EXT_IT tables with the data in SAP S/4HANA and load it into SAP S/4HANA. For assistance, contact insightsoftware Support.

Custom Report Generation for Mapping Extension Fields

The /MAGSW/DYNAMIC_EXT_MAP is a customized ABAP List Viewer (ALV) report that allows you to maintain the mappings of the extension fields that are read when you run the FILL_ BAPI_MISSING_FIELDS method for implementing the extension fields dynamically.

The /MAGSW/DYN_EXT table stores the source or third-party field names, and the respective target or SAP S/4HANA fields entered in the custom report.

The transaction code is /MAGSW/DYN_MAP_EXT.

Note: The MDG and mapping entity fields are applicable for MDG validations only.

For the steps to configure BAdI and interface custom fields, refer to Appendix E: Extensibility Guidelines

Was this article helpful?

We're sorry to hear that.