Skip to main content

Appendix B: SAP Data Services Jobs, Global Variables

This appendix contains the descriptions of SAP Data Services jobs that are created during the setup of Transaction Replication. It also lists the global variables that you need to update before running these jobs.

SAP Data Services Jobs

During the setup of SAP Data Services objects for loading transaction and balance data, import the .atl file of your source system into the SAP Data Services repository using SAP Data Services Designer. This creates projects and jobs specific to your source system in the repository.

Note: The .atl files for your source system are available at <SetupFolder>\<SourceSystem>\<SourceDatabase>\Mappings.

For information about setting up SAP Data Services objects, see Set Up Data Services Objects in the SAP Central Finance Transaction Replication by insightsoftware Installation and Configuration Guide.

The following sections provide the project and job details for each source system.

Oracle E-Business Suite

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import AVL data, load the SC_AVL.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_AVL project:

  • SC_CI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer invoice information and generates cache.
  • SC_CO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer order information and generates cache.
  • SC_PO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for purchase order information and generates cache.
  • SC_SI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for sales invoice information and generates cache.

Note: For AVL transaction, the TOBEDELETED column flag value has been changed to " ". It implies that the value must not be deleted. However, when this value is X, it must be deleted. The delete functionality is applicable for flat file AVL transactions only.

IFS Applications

To import transaction data, load the IFS_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the IFS_Journals project:

  • IFS_Journals_OT: Performs an initial data load for journal data.
  • IFS_Journals_CDC: Performs an incremental data load for journal data.
  • IFSCDC_Set_Status_On: Enables the incremental data load for the IFS_Journals_CDC job.
  • IFSCDC_Set_Status_Off: Disables the incremental data load for the IFS_Journals_CDC job.
  • IFS_Reprocess_Journals: Processes data for transactions that failed during initial and incremental data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the IFS_Balances.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the IFS_Balances project:

  • IFS_GL_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • IFS_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • IFS_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

JD Edwards EnterpriseOne

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

Oracle PeopleSoft

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import AVL data, load the SC_AVL.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_AVL project:

  • SC_CI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer invoice information and generates cache.
  • SC_CO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer order information and generates cache.
  • SC_PO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for purchase order information and generates cache.
  • SC_SI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for sales invoice information and generates cache.

Microsoft Dynamics AX

To import transaction data, load the msftax_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the MSFTX_Journals project:

  • MSFTAX_Journals_OT: Performs an initial data load for journal data.
  • MSFTAX_Journals_CDC: Performs an incremental data load for journal data.
  • MSFTAXCDC_Set_Status_On: Enables the incremental data load for the MSFTAX_Journals_CDC job.
  • MSFTAXCDC_Set_Status_Off: Disables the incremental data load for the MSFTAX_Journals_CDC job.
  • MSFTAX_Reprocess_Journals: Processes data for transactions that failed during initial and incremental data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the MSFTAX_Balances.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the MSFTAX_Balances project:

  • MSFTAX_GL_ACCOUNT_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • MSFTAX_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • MSFTAX_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

Microsoft Dynamics NAV

To import transaction data, load the MSFTNAV_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the MSFTNAV_Journals project:

  • MSFTNAV_Journals_OT: Performs an initial data load for journal data.
  • MSFTNAV_Journals_CDC: Performs an incremental data load for journal data.
  • MSFTNAVCDC_Set_Status_On: Enables the incremental data load for the MSFTNAV_Journals_CDC job.
  • MSFTNAVCDC_Set_Status_Off: Disables the incremental data load for the MSFTNAV_Journals_CDC job.

To import balances data, load the MSFTNAV_Balances.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the MSFTNAV_Balances project:

  • MSFTNAV_GL_ACCOUNT_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • MSFTNAV_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • MSFTNAV_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

Microsoft Dynamics SL

To import transaction data, load the MSFTSL_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the MSFTNSL_Journals project:

  • MSFTSL_Journals_OT: Performs an initial data load for journal data.
  • MSFTSL_Journals_CDC: Performs an incremental data load for journal data.
  • MSFTSLCDC_Set_Status_On: Enables the incremental data load for the MSFTSL_Journals_CDC job.
  • MSFTSLCDC_Set_Status_Off: Disables the incremental data load for the MSFTSL_Journals_CDC job.
  • MSFTSL_Reprocess_Journals: Processes data for transactions that failed during initial and incremental data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the MSFTSL_Balances.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the MSFTSL_Balances project:

  • MSFTSL_GL_Account_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • MSFTSL_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • MSFTSL_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

Microsoft Dynamics GP

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

Microsoft Dynamics 365 Finance and Operations

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import AVL data, load the SC_AVL.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_AVL project:

  • SC_CI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer invoice information and generates cache.
  • SC_CO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer order information and generates cache.
  • SC_PO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for purchase order information and generates cache.
  • SC_SI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for sales invoice information and generates cache.

Microsoft Dynamics 365 Business Central (On-premises and Cloud)

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.

Epicor iScala

To import transaction data, load the iScala_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the iScala_Journals project:

  • SCA_Journals_OT: Performs an initial data load for journal data.
  • SCA_Journals_CDC: Performs an incremental data load for journal data.
  • SCACDC_Set_Status_On: Enables the incremental data load for the SCA_Journals_CDC job.
  • SCACDC_Set_Status_Off: Disables the incremental data load for the SCA_Journals_CDC job.
  • SCA_Reprocess_Journals: Processes data for transactions that failed during initial and incremental data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the iScala_Balances.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the iScala_Balances project:

  • SCA_GL_Account_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • SCA_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • SCA_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

To import drilldown data, load the iScala_SCD.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the iScala_SCD project:

  • IScala_OT_AP_TRX: Transfers historic and one-time data from the Payables tables in the iScala system to the corresponding mirror tables in the Transaction Replication Stage environment.
  • IScala_OT_AR_TRX: Transfers historic and one-time data from the Receivables tables in the iScala system to the corresponding mirror tables in the Transaction Replication Stage environment.
  • IScala_OT_GL_TRX: Transfers historic and one-time data from the General Ledger tables in the iScala system to the corresponding mirror tables in the Transaction Replication Stage environment.
  • IScala_OT_PO_TRX: Transfers historic and one-time data from the Purchase Orders tables in the iScala system to the corresponding mirror tables in the Transaction Replication Stage environment.
  • IScala_OT_SO_TRX: Transfers historic and one-time data from the Sales Order tables in the iScala system to the corresponding mirror tables in the Transaction Replication Stage environment.
  • IScala_OT_MASTER_DATA: Transfers historic and one-time data from the Entity tables (such as customer, vendor, material, etc.) in the iScala system to the corresponding mirror tables in the Transaction Replication Stage environment.
  • SCD_JOB_ISCALA_CDC: Initiates the incremental data transfer from master and transaction tables in the iScala system to the corresponding mirror tables in the Transaction Replication Stage environment.

Infor CloudSuite Industrial (SyteLine)

To import transaction data, load the Syteline_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the Syteline_Journals project:

  • Syteline_Journals_OT: Performs an initial data load for journal data.
  • Syteline_Journals_CDC: Performs an incremental data load for journal data.
  • SytelineCDC_Set_Status_On: Enables the incremental data load for the Syteline_Journals_CDC job.
  • SytelineCDC_Set_Status_Off: Disables the incremental data load for the Syteline_Journals_CDC job.
  • Syteline_Reprocess_Journals: Processes data for transactions that failed during initial and incremental data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the Syteline_Balances.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the Syteline_Balances project:

  • Syteline_GL_Account_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • Syteline_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • Syteline_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

Infor Baan

To import transaction data, load the BAAN_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the BAAN_Journals project:

  • BAAN_Journals_OT: Performs an initial data load for journal data.
  • BAAN_Journals_CDC: Performs an incremental data load for journal data.
  • BAANCDC_Set_Status_On: Enables the incremental data load for the BAAN_Journals_CDC job.
  • BAANCDC_Set_Status_Off: Disables the incremental data load for the BAAN_Journals_CDC job.
  • BAAN_Reprocess_Journals: Processes data for transactions that failed during initial and incremental data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the BAAN_Balances.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the BAAN_Balances project:

  • BAAN_GL_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • BAAN_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • BAAN_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

Infor LN (On-Premises)

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads the general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import AVL data, load the SC_AVL.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_AVL project:

  • SC_CI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer invoice information and generates cache.
  • SC_CO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer order information and generates cache.
  • SC_PO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for purchase order information and generates cache.
  • SC_SI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for sales invoice information and generates cache.

Workday

To import transaction data, load the Workday_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the Workday_Journals project:

  • Workday_Journals: Performs an initial data load for journal data.
  • Workday_Reprocess_Journals: Processes data for transactions that failed during data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the Workday_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the Workday_Balances project:

  • Workday_GL_Account_Balances: Loads general ledger account opening balances into SAP S/4HANA.
  • Workday_Customer_Balances: Loads customer balances into SAP S/4HANA.
  • Workday_Vendor_Balances: Loads vendor balances into SAP S/4HANA.

QAD

To import transaction data, load the QAD_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the QAD_Journals project:

  • QAD_Journals: Performs an initial data load for journal data.
  • QAD_Reprocess_Journals: Processes data for transactions that failed during data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

NetSuite

To import transaction data, load the NetSuite_DataLoad.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the NetSuite_DataLoad project:

  • Netsuite_Account: Loads initial accounting data from your source system.
  • cdc_NetSuite_Account: Loads incremental accounting data from your source system.
  • NetSuite_Accounting_Periods: Loads initial accounting periods data from your source system.
  • cdc_NetSuite_Accounting_Periods: Loads incremental accounting periods data from your source system.
  • NetSuite_Currencies: Loads initial currencies data from your source system.
  • cdc_NetSuite_Currencies: Loads incremental currencies data from your source system.
  • NetSuite_Customers: Loads initial customer data from your source system.
  • cdc_NetSuite_Customers: Loads incremental customer data from your source system.
  • NetSuite_Employees: Loads initial employee data from your source system.
  • cdc_NetSuite_Employees: Loads incremental employee data from your source system.
  • NetSuite_Subsidiaries: Loads initial subsidiary information from your source system.
  • cdc_NetSuite_subsidiary: Loads incremental subsidiary information from your source system.
  • NetSuite_Uom: Loads initial UOM data from your source system.
  • cdc_NetSuite_Uom: Loads incremental UOM data from your source system.
  • NetSuite_Vendors: Loads initial vendor data from your source system.
  • cdc_NetSuite_Vendors: Loads incremental vendor data from your source system.
  • NetSuite_Posting_Account_Activity: Loads initial data for posting account activity from your source system.
  • NetSuite_TransactionLines: Loads initial data for transaction lines from your source system.
  • NetSuite_Transactions: Loads initial transaction data from your source system.
  • NetSuite_trx_CDC: Loads incremental data for transactions, transaction lines, and posting account activity from your source system.
  • NSCDC_Set_Status_Off: Disables the incremental data load process for the NetSuite_trx_CDC job.
  • NSCDC_Set_Status_On: Enables the incremental data load for the NetSuite_trx_CDC job.

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

Deltek Costpoint

To import transaction data, load the CSPT_Journals_hvr.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the CSPT_Journals project:

  • CSPT_Journals_OT: Performs an initial data load for the journal data.
  • CSPT_Journals_CDC: Performs an incremental data load for the journal data.
  • CSPTCDC_Set_Status_on: Enables the incremental data load for the CSPT_Journals_CDC job.
  • CSPTCDC_Set_Status_Off: Disables the incremental data load for the CSPT_Journals_CDC job.
  • CSPT_Reprocess_Journals: Processes data for transactions that failed during initial and incremental data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

1C:Enterprise

To import transaction data, load the 1C_Journals.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the 1C_Journals project:

  • 1C_Journals: Performs an initial data load for the journal data.
  • 1C_Reprocess_Journals: Processes data for transactions that failed during data loads.
  • Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import balances data, load the 1C_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the 1C_Balances project:

  • 1C_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.

To import drilldown data, load the 1C_SCD.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the 1C_SCD project:

  • 1C_SCD_Trx: Transfers data from the 1C system to the corresponding mirror tables in the Transaction Replication Stage environment.

Flat File

To import transaction data, load the SC_Journals.atl file from\\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Journals project:

  • SC_Journals: Handles both initial (OT) and incremental (CDC) journal data loads, automatically generates cache, and includes an option to concurrently run L1-L3 reconciliation reports.
  • SC_CDC_Set_Status_On: Enables the incremental data load for the SC_Journals job.
  • SC_CDC_Set_Status_Off: Disables the incremental data load for the SC_Journals job.
  • SC_Reprocess: Processes data for transactions that failed during initial and incremental data loads.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.
  • SC_Level1_Refresh: Verifies missing source records, updates corresponding tables, and adjusts L1 reconciliation reports accordingly.

To import balances data, load the SC_Balances.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_Balances project:

  • SC_Balances: Loads general ledger account opening balances, customer balances, and vendor balances into SAP S/4HANA.
  • SC_Master_Lookup_Load: Loads master data from MSC_Lookup_Data.xlsx into the MSC_MASTER_LOOKUP table and creates a persistent cache for lookup data.

To import AVL data, load the SC_AVL.atl file from \\Mappings into your SAP Data Services repository. This creates the following jobs within the SC_AVL project:

  • SC_CI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer invoice information and generates cache.
  • SC_CO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for customer order information and generates cache.
  • SC_PO_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for purchase order information and generates cache.
  • SC_SI_STAGE_LOAD: Performs an initial (OT) and incremental (CDC) data load for sales invoice information and generates cache.

Reconciliation

To import reconciliation data, load the <SourceSystem>_RECON_L1_L5.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the <SourceSystem>_RECON_L1_L5 project:

  • <SourceSystem>_Account_Recon: Loads initial account balances from the source system and SAP S/4HANA into the LEVEL5_RECON_GLBAL_STG table in the staging schema.
  • <SourceSystem>_Period_Balances_CDC: Loads incremental account balances from the source system's balances table into the <SourceSystem>_SOURCE_BALANCES tables in the staging schema.
  • <SourceSystem>_Period_Balances_OT: Loads initial account balances from the source system's balances table into the <SourceSystem>_SOURCE_BALANCES tables in the staging schema.
  • <SourceSystem>_Period_Balances: (for GP) Loads the initial and incremental reconciliation for account balances.
  • <SourceSystem>_Source_Doc_Info: Loads initial journal information from the source table in the source schema into the SOURCE_DOC_INFO table in the staging schema.
  • <SourceSystem>_Source_Doc_Info_CDC: Loads incremental journal information from the source table in the source schema into the SOURCE_DOC_INFO table in the staging schema.
  • <SourceSystem>_SRCDOC_Set_Status_Off: Disables the incremental data load for the <SourceSystem>_Source_Doc_Info_CDC job.
  • <SourceSystem>_SRCDOC_Set_Status_On: Enables the incremental data load for the <SourceSystem>_Source_Doc_Info_CDC job.
  • <SourceSystem>CDC_PERIOD_Bal_Set_Status_Off: Disables the incremental data load for the <SourceSystem>_Period_Balances_CDC job.
  • <SourceSystem>CDC_PERIOD_Bal_Set_Status_On: Enables the incremental data load for the <SourceSystem>_Period_Balances_CDC job.

To import reconciliation data, load the RECON_STG.atl file from \\Mappings into the SAP Data Services repository. This creates the following jobs within the RECON_STG project:

  • S4_MASTER_LOAD: Loads reference tables (T100 for error messages and TCURX for currency data) from Target to Staging. Required once before recon load for SQL Server environments only (not needed for HANA). Re-run when currency configurations are updated to refresh the staging table.
  • SC_RECON: Performs an initial and incremental data load into the LEVEL<1|2|3|4|5>_RECON%_STG tables in the staging schema, supporting both HANA and SQL Server environments.
  • RECON_DEL_HIST: Deletes historical data in the LEVEL<1|2|3|4|5>_RECON_STG tables based on the values provided for the Company, Fiscal Year and/or Fiscal Period parameters during the job run.
  • RECON_L1_L3: Refreshes L1-L3 reconciliation reports.
  • RECON_L4_L5: Refreshes L0, L4, and L5 reconciliation reports.

Cleanup

The following job is common for all source systems.

  • SCT_CLEANUP: Performs data cleanup according to specified parameters.

Global Variables

Before executing the jobs to load data from the source system into the SLT Replication Server, ensure you update the relevant global variables. Some variables are specific to only certain source systems. For more information on running the jobs, refer toLoading Data and Reprocessing Documents.

Note: The capitalization of the variables may differ across source systems.

GL Balances Job

The list of variables that you need to specify before running the <SourceSystem>_GL%Balances job in the <SourceSystem>_Balances project is as follows:

  • $set_of_book_id/$Ledger_id: Optional; it indicates the set of books/ledger identifier using which the general ledger balance is extracted.
  • $Company_Code: Indicates the company code (balancing segment) using which the general ledger account balances are extracted for a company.
  • $Year_to_Extract/$Fiscal_Year_To_Extract: Indicates the year in which the balances are extracted from the source system.
  • $Period_Name_to_extract: (Only for NetSuite) Indicates the period name using which the balances are extracted from the source system. For example, specify "Dec 2018".
  • $Period_Num_to_Extract: Indicates the period number using which the balances are extracted.
  • $Natural_Account: Indicates the account number for which the balances are extracted from the source system.
  • $Year_to_Post/$Fiscal_Year_To_Post: Indicates the year in which the balances are posted to SAP S/4HANA.
  • $GL_Date: Indicates the general ledger date on which the balance is posted to SAP S/4HANA.
  • $GL_Clearing_Account/$clearing_account: Indicates the general ledger account number to which the clearing amount is posted to balance the journal.

GL Open Item Balances Job

The list of variables that you need to specify before running the <SourceSystem>_GL%OPEN_ITEM job in the <SourceSystem>_GL_OPEN_ITEM project is as follows:

  • $G_GL: Indicates whether the journals pertaining to general ledger can be loaded into SAP S/4HANA; set to 1 to enable the load for general ledger.
  • $G_SLT: Indicates whether the documents can be loaded into SLT Replication Server; set to 1 to enable SLT for the data load.
  • $G_FROM_DATE: Indicates the date from which the journals are processed in the DD-MON-YYYY format. For example, 29-MAR-2022.
  • $G_TO_DATE: Indicates the date up to which the journals are processed in the DD-MON-YYYY format. For example, 29-MAR-2022.
  • $G_COMP_CODE/$COMP_CODE: For Oracle E-Business Suite, use $G_COMP_CODE and for Oracle PeopleSoft, use $COMP_CODE , to enter the company code for which you want to load the general ledger open items.
  • $G_GL_CLEARING_ACCOUNT: Enter the general ledger account to which any offset amounts are posted.

Vendor Balances Job

The list of variables that you need to specify before running the <SourceSystem>%Vendor_Balances job in the <SourceSystem>_Balances project is as follows:

  • $Ledger_id: Indicates the ledger identifier using which the vendor balance is extracted.
  • $As_of_date: Indicates the date up to which the balance is calculated and extracted.
  • $vendor_id/$Vendor_number: Optional; it indicates whether the job is run for a specific vendor or for all vendors; specify the vendor number to run the job for a single vendor or leave it blank to run the job for all vendors.
  • $Vendor_Clearing_Account: Indicates the vendor account number to which the clearing amount is posted to balance the journal.
  • $AP_Clearing_Account: Indicates the Accounts Payable account to which any offset amounts are posted.
  • $gl_date: Indicates the general ledger date on which the balance is posted to SAP S/4HANA.
  • $Year_to_Post/$Fiscal_Year_To_Post: Indicates the year in which the balances are posted to SAP S/4HANA.
  • $Period_Num_to_post: Indicates the period number using which the balances are posted.
  • $Summary_Mode: Y indicates that the balances are posted as transaction for each vendor. N indicates that the balances are posted as transaction for each invoice.
  • $G_SLT: Indicates whether the documents can be loaded into SLT Replication Server; set to 1 to enable SLT for the data load.
  • $<SourceSystem>_Company/$Company_Code: Indicates the company code (balancing segment) using which the vendor balances for a company are extracted.
  • $G_DB_TYPE: Indicates the staging database type.
  • $RUN_ID: Indicates the unique job run identifier used by different source systems for the same job.

Customer Balances Job

The list of variables that you need to specify before running the <SourceSystem>%Customer_Balances job in the <SourceSystem>_Balances project is as follows:

  • $Ledger_id: Indicates the ledger identifier using which the customer balance is extracted.
  • $<SourceSystem>_Company: Indicates the company code (balancing segment) using which the customer balances for a company are extracted.
  • $As_of_date: Specifies the date up to which the balance is calculated and extracted.
  • $Customer_Number: Optional; it indicates whether the job is run for a single customer or for all customers; specify the customer number to run the job for a single customer or leave it blank to run the job for all customers.
  • $Customer_clearing_account: Indicates the general ledger account number to which the clearing amount is posted to balance the journal.
  • $GL_Date: Indicates the general ledger date on which the balance is posted to SAP S/4HANA.
  • $Year_to_post: Indicates the year in which the balance is posted to SAP S/4HANA.

1C_Balances Job

  • $1C_FILEPATH: Indicates the path in which the .csv file containing the source data is available.
  • $v_email: Indicates the email address of the point of contact. The error messages or notifications are sent to the specified email address.
  • $POSTING_DATE: Indicates the date up to which the balances gets posted into SAP S/4HANA.
  • $CLEARING_ACCOUNT: Indicates the account number to which the clearing amount is posted to balance the journal.
  • $SOURCE_SYSTEM: Indicates the source system for which the balance is extracted.

1C_SCD_Trx Job

  • $UFF_FILEPATH_SRC1: Indicates the folder path where the flat files are available.
  • $UFF_ARCHIVE_SRC1: Indicates the archive folder path where the processed files are moved.
  • $UFF_SRC1_EXCEPTION: Indicates the folder path where the exception files are created.
  • $G_SOURCE_SYSTEM: Indicates the source system name.
  • $G_USER: Indicates the Created By username.

Stage Load Job

The list of variables that you must provide before running the AVL-related jobs is as follows:

  • $FILE_PATH: Indicates the location of the Master lookup file.
  • $STAGE_DB: Indicates the Staging database, such as SQL Server, HANA.
  • $<SourceSystem>_CO_OT: Indicates intial load if set to '1'.
  • $<SourceSystem>_CI_OT: Indicates intial load if set to '1'.
  • $<SourceSystem>_CI_CDC: Indicates incremental load if set to '1'.
  • $<SourceSystem>_CO_CDC: Indicates incremental load if set to '1'.
  • $<SourceSystem>_PO_OT: Indicates intial load if set to '1'.
  • $<SourceSystem>_PO_CDC: Indicates incremental load if set to '1'.
  • $<SourceSystem>_SI_OT: Indicates intial load if set to '1'.
  • $<SourceSystem>_SI_CDC: Indicates incremental load if set to '1'.
  • $G_DB_TYPE: Indicates the staging database type.
  • $G_ERP: Indicates the ERP type. PSFT, UC, EBS, D365FNO, MSFTBC, InforLN
  • $SCT_VERSION: Indicates the product version.
  • $G_JOB_NAME: Indicates the job name that is run.

SC Balances Job

The list of variables for the SC_Balances job:

  • $G_ERP: Indicates the ERP name, such as InforLN, EBS, JDE, PSFT, D365FNO, MSFTBC, MSFTGP, or UC.
  • $G_SOURCE_SYSTEM: Indicates the source system name.
  • $G_UC_FOLDER_LOCATION: (for UC) Indicates the folder path from which the utility should retrieve files. If left blank, the utility will default to the folder path defined in the SourceConnect Management Console Connection tab during UC datasource configuration.
  • $G_UC_File_Wildcard: (for UC) Indicates the file name pattern (wildcard) that the utility should use to identify relevant files. The default value is *.CSV. Some examples include UC_*.CSV, EBS_*.CSV.

  • $G_UC_Skipped_Rows: (for UC) Indicates the number of initial data rows to skip during file extraction. The default value is 0. Only positive integers are allowed. 

    Note: Do not include empty lines in this count. Only count rows that contain data and need to be skipped. For example, if rows 1–3 contain data and rows 4–5 are empty, enter 3 as the value. The empty rows will be skipped automatically.

     

  • $G_DB_TYPE: Indicates the database type (HANA, Microsoft_SQL_Server).
  • $G_CUSTOMER: Indicates whether to load the customer journals into SAP S/4HANA. Set to 1 if yes.
  • $G_VENDOR: Indicates whether to load the vendor journals into SAP S/4HANA. Set to 1 if yes.
  • $G_GL: Indicates whether the journals pertaining to general ledger can be loaded into SAP S/4HANA; set to 1 to enable the load for general ledger.
  • $G_SLT: Indicates whether the documents can be loaded into SLT Replication Server; set to 1 to enable SLT for the data load.
  • $G_FISCAL_YEAR: Indicates the year for which the data should be deleted in the LEVEL<1|2|3|4|5>_RECON%_STG tables in the staging schema.
  • $G_GL_DATE: Indicates the posting date, which can be either the current date or a specified date to run the job.
  • $G_LEDGER_ID: Indicates the ledger identifier using which the customer balance is extracted.
  • $G_AS_OF_DATE: Specifies the date up to which the balance is calculated and extracted.
  • $G_TRANSACTION_ID: Indicates a combination of Header ID and Doc type separated with a colon (:). Example: ‘20240001:ARC’ or ‘20240001'.
  • $G_PERIOD_NUM_TO_EXTRACT: Indicates the month up to which the data should be loaded (example, January = 01).
  • $G_COMPANY_CODE: Indicates the company code (balancing segment) using which the general ledger account balances are extracted for a company.
  • $G_GL_CURRENCY_CODE: Filters records based on currency.
  • $G_AP_CLEARING_ACCT: Indicates the AP Clearing Account to be loaded for the clearing lines.
  • $G_AR_CLEARING_ACCT: Indicates the AR Clearing Account to be loaded for the clearing lines.
  • $G_GL_CLEARING_ACCT: Indicates the GL Clearing Account to be loaded for the clearing lines.
  • $G_CLEARING_ACCOUNT_FOR_POPACCTPROC: Indicates the clearing account value.
  • $G_UC_LOG_FILEPATH: Indicates the location of the log file to be loaded for error records.
  • $G_EMAIL: Indicates the email for job notifications.
  • $G_LOOKUP_CHANGES: Indicates whether to refresh the master lookup cache during the journals job (1 = yes, 0 = no).

SC Journals Job

The list of variables for the SC_Journals and SC_Reprocess jobs:

  • SC_Journals
    • $G_ERP: Indicates the ERP name, such as InforLN, EBS, JDE, PSFT, D365FNO, MSFTBC, MSFTGP, or UC.
    • $G_SOURCE_SYSTEM: Indicates the source system name.
    • $G_UID: Indicates that it is automatically triggered from Management console.
    • $G_COMMIT_SIZE: (for UC) Indicates the commit size. Default is 100000.
    • $G_UC_FOLDER_LOCATION: (for UC) Indicates the folder path from which the utility should retrieve files. If left blank, the utility will default to the folder path defined in the SourceConnect Management Console Connection tab during UC datasource configuration.
    • $G_UC_File_Wildcard: (for UC) Indicates the file name pattern (wildcard) that the utility should use to identify relevant files. The default value is *.CSV. Some examples include UC_*.CSV, EBS_*.CSV.

    • $G_UC_Skipped_Rows: (for UC) Indicates the number of initial data rows to skip during file extraction. The default value is 0. Only positive integers are allowed. 

      Note: Do not include empty lines in this count. Only count rows that contain data and need to be skipped. For example, if rows 1–3 contain data and rows 4–5 are empty, enter 3 as the value. The empty rows will be skipped automatically.

       

    • $G_DB_TYPE: Indicates the database type (HANA, Microsoft_SQL_Server).
    • $G_RUN_OT: Indicates whether to run OT (1 to run, 0 otherwise).
    • $G_AP: (for JDE and EBS) Indicates whether to run the AP module (1 to run, 0 otherwise).
    • $G_AR: (for JDE and EBS) Indicates whether to run the AR module (1 to run, 0 otherwise).
    • $G_GL: (for JDE and EBS) Indicates whether to run the GL module (1 to run, 0 otherwise).
    • $G_SLT: Indicates whether to run SLT (1 to run, 0 otherwise).
    • $G_HEADER_ID:
      • (for JDE) Indicates a combination of Company code, Doc batch, and Doc number/Doc number join separated with a colon (:). Example: ‘00001:1893:1083’ or ‘00001::’.
      • (for EBS, PSFT, D365FNO, MSFTBC, MSFTGP) Indicates the JE_HEADER_ID value.
      • (for InforLN) Indicates a combination of Company code, Doc type, and Header ID separated with a colon (:). Example: ‘121:ARC:20240001’ or ‘121:ARC’ or '121'.
    • $G_FROM_DATE: Indicates the start date from which data should be fetched and loaded.
    • $G_TO_DATE: Indicates the end date until which data should be fetched and loaded.
    • $G_AP_CLEARING_ACCT: Indicates the AP Clearing Account to be loaded for the clearing lines.
    • $G_AR_CLEARING_ACCT: Indicates the AR Clearing Account to be loaded for the clearing lines.
    • $G_GL_CLEARING_ACCT: Indicates the GL Clearing Account to be loaded for the clearing lines.
    • $IF_COPA: (for EBS, GP, UC) Indicates if there are copa fields (1 to load copa fields for a document, 0 otherwise).
    • $IF_EXTENT: Indicates if there are any extension fields (1 to load extension fields for a document, 0 otherwise).
    • $G_RUN_CDC: Indicates whether to run CDC (1 to run, 0 otherwise).
    • $G_SUBSCRIPTION: Indicates the subscription name to be provided when the job is triggered for CDC load.
    • $RE_INITIALIZE_TAB: Indicates the status of the CDC records when loaded for the first time (set to ‘N’).
    • $G_RUN_RECON: Indicates whether to run reconciliation reports (1 to run, 0 otherwise).
    • $G_LOGICAL_SYSTEM: Indicates the logical system for which the account balances data is loaded into the staging schema from the source system and SAP S/4HANA.
    • $G_SELECT_RECON_REPORT: Indicates the reconciliation report to be run. Default is L1, L2, L3.
    • $G_LOCATION: Indicates the location of the recon records to load. Default is ‘ALL’.
    • $CDC_HIST_DEL_DAYS: Indicates the required days to refresh CDC history.
    • $G_VALIDATE_AIF: Indicates whether to validate AIF errors ('Y' to validate).
    • $G_UC_LOG_FILEPATH: Indicates the location of the log file to be loaded for error records.
    • $G_EMAIL: Indicates the email for job notifications.
    • $G_LOOKUP_CHANGES: Indicates whether to refresh the master lookup cache during the journals job (1 = yes, 0 = no).
  • SC_Reprocess
    • $G_ERP: Indicates the ERP name, such as InforLN, EBS, JDE, PSFT, D365FNO, MSFTBC, MSFTGP, or UC.
    • $G_SOURCE_SYSTEM: Indicates the source system name.
    • $G_UID: Indicates that it is automatically triggered from Management console.
    • $G_DB_TYPE: Indicates the database type (HANA, Microsoft_SQL_Server).
    • $G_COMMIT_SIZE: (for UC) Indicates the commit size. Default is 100000.
    • $G_UC_FOLDER_LOCATION: (for UC) Indicates the folder path from which the utility should retrieve files. If left blank, the utility will default to the folder path defined in the SourceConnect Management Console Connection tab during UC datasource configuration.
    • $G_UC_File_Wildcard: (for UC) Indicates the file name pattern (wildcard) that the utility should use to identify relevant files. The default value is *.CSV. Some examples include UC_*.CSV, EBS_*.CSV.

    • $G_UC_Skipped_Rows: (for UC) Indicates the number of initial data rows to skip during file extraction. The default value is 0. Only positive integers are allowed. 

      Note: Do not include empty lines in this count. Only count rows that contain data and need to be skipped. For example, if rows 1–3 contain data and rows 4–5 are empty, enter 3 as the value. The empty rows will be skipped automatically.

       

    • $G_SLT: Indicates whether to run SLT (1 to run, 0 otherwise).
    • $IF_COPA: (for EBS, GP, UC) Indicates if there are copa fields (1 to load copa fields for a document, 0 otherwise).
    • $IF_EXTENT: Indicates if there are any extension fields (1 to load extension fields for a document, 0 otherwise).
    • $G_USE_AUTO_INPUT: Indicates whether records are picked in an automated process. Set to ‘Y’ to run, else ‘N’.
    • $G_USE_MANUAL_INPUT: Indicates whether records are picked in a manual process. Set to ‘Y’ to run, else ‘N’.
    • $G_PROCESS_MISSING_DOCS: Indicates whether to check for source missing records. Set to ‘Y’ to run, else ‘N’.
    • $G_Process_Validation_Errors: Indicates whether to check for stage error records. Set to ‘Y’ to run, else ‘N’.
    • $G_Process_AIF_UIDs: Indicates whether to check for AIF error records. Set to ‘Y’ to run, else ‘N’.
    • $G_UC_LOG_FILEPATH: Indicates the location of the log file to be loaded for error records.
    • $G_UC_REPROCESS_FILEPATH: Indicates the location of the reprocess file to be loaded for error records.
    • $G_FROM_DATE: Indicates the start date from which data should be fetched and loaded.
    • $G_TO_DATE: Indicates the end date from which data should be fetched and loaded.
    • $G_AP_CLEARING_ACCT: Indicates the AP Clearing Account to be loaded for the clearing lines.
    • $G_AR_CLEARING_ACCT: Indicates the AR Clearing Account to be loaded for the clearing lines.
    • $G_GL_CLEARING_ACCT: Indicates the GL Clearing Account to be loaded for the clearing lines.
    • $G_CLEARING_ACCOUNT_FOR_POPACCTPROC: Indicates the clearing account value.
    • $G_RUN_RECON: Indicates whether to run reconciliation reports (1 to run, 0 otherwise).
    • $G_LOGICAL_SYSTEM: Indicates the logical system for which the account balances data is loaded into the staging schema from the source system and SAP S/4HANA.
    • $G_SELECT_RECON_REPORT: Indicates the reconciliation report to be run. Default is L1, L2, L3.
    • $G_LOCATION: Indicates the location of the recon records to load. Default is ALL.
    • $CDC_HIST_DEL_DAYS: Indicates the required days to refresh CDC history.
    • $G_LOOKUP_CHANGES: Indicates whether to refresh the master lookup cache during the journals job (1 = yes, 0 = no).

Journals Job

The list of variables that must specify before running the <SourceSystem>_Journals job in the <SourceSystem>_Journals project is as follows:

  • $<SourceSystem>_FILEPATH: Indicates the path in which the .csv file containing the source data is available.
  • $DOC_SPLIT_CLEARING_ACCOUNT: Indicates the general ledger account to which any offset amounts are posted.
  • $v_<SourceSystem>_email: Indicates the email address of the point of contact. The error messages are sent to the specified email address.
  • $FileName: Indicates the name of the .csv file containing the source data.
  • $SOURCE_SYSTEM: Indicates the source system for which the journal information is loaded from the source system into the staging schema.

Journals CDC Job

The list of variables that you must specify before running the <SourceSystem>_Journals_CDC job in the <SourceSystem>_Journals project is as follows:

  • $G_GL_CLEARING_ACCOUNT: Indicates the general ledger account to which any offset amounts are posted.
  • $G_AR_CLEARING_ACCOUNT: Indicates the receivables account to which any offset amounts are posted.
  • $G_AP_CLEARING_ACCOUNT: Indicates the Accounts Payable account to which any offset amounts are posted.

Journals OT, Reprocess Journals Jobs

The list of variables that you must specify before running the <SourceSystem>_Journals_OT or <SourceSystem>_Reprocess_Journals job in the <SourceSystem>_Journals project is as follows:

  • $G_AP: Indicates whether the journals/documents pertaining to Accounts Payable can be loaded into SLT Replication Server; set to 1 to enable the load for Accounts Payable.
  • $G_AR: Indicates whether the journals/documents pertaining to Accounts Receivable can be loaded into SLT Replication Server; set to 1 to enable the load for Accounts Receivable.
  • $G_GL: Indicates whether the journals/documents pertaining to General Ledger can be loaded into SLT Replication Server; set to 1 to enable the load for General Ledger.
  • $G_SLT: Indicates whether the documents can be loaded into SLT Replication Server; set to 1 to enable SLT for the data load.
  • $G_FROM_DATE: Indicates the date from which the journals are processed.
  • $G_TO_DATE: Indicates the date up to which the journals are processed.
  • $G_GL_CLEARING_ACCOUNT: Indicates the general ledger account to which any offset amounts are posted.
  • $G_AR_CLEARING_ACCOUNT: Indicates the receivables account to which any offset amounts are posted.
  • $G_AP_CLEARING_ACCOUNT: Indicates the Accounts Payable account to which any offset amounts are posted.
  • $<SourceSystem>_FILEPATH: Indicates the path in which the .csv file containing the source data is available.
  • $DOC_SPLIT_CLEARING_ACCOUNT: Indicates the general ledger account to which any offset amounts are posted.
  • $v_<SourceSystem>_email: Indicates the email address of the point of contact. The error messages are sent to the specified email address.

The following variables indicate whether the job is run for a specific journal or for all journals:

  • $Doc_Number: For JD Edwards EnterpriseOne, specify the gldoc column value of the F0911 table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $Doc_Batch: For JD Edwards EnterpriseOne, specify the glicu column value of the F0911 table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $Company: For JD Edwards EnterpriseOne, specify the glco column value of the F0911 table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $JE_HEADER_ID: For PeopleSoft, specify the JOURNAL_ID column value of the PS_JRNL_HEADER table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $Company_Code: For PeopleSoft, specify the BUSINESS_UNIT column value of the PS_VOUCHER table in the source database to run the job for the vouchers created in the required business unit or leave it blank to run the job for the vouchers created in all business units.
  • $JE_HEADER_ID: For Oracle E-Business Suite, specify the je_header_id column value of the GL_JE_HEADRES table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $JE_HEADER_ID: For IFS Applications, specify the VOUCHER_NO column value of the GEN_LED_VOUCHER_TAB table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $REC_ID: For Microsoft Dynamics AX, specify the RECID column value of the GENERALJOURNALENTRY table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $REC_ID: For Microsoft Dynamics NAV, specify the NO_ column value of the %G_L Register table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $BATCH_NO: For Microsoft Dynamics SL, specify the BATNBR column value of the BATCH table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $JE_HEADER_ID: For Microsoft Dynamics GP, specify the JRNENTRY column value of the GL20000 table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $TRX_NO: For Epicor iScala, specify the GL06002 column value of the GL06 table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $JOURNAL_NO: For Epicor iScala, specify the GL06023 column value of the GL06 table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $Batch_id: For Infor CloudSuite Industrial (SyteLine), specify the journal_batch_id column value of the LEDGER_MST table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $REF_NO: For Infor CloudSuite Industrial (SyteLine), specify the check_num column value of the LEDGER_MST table in the source database for payment documents or the voucher column value in the table for other documents to run the job for the required journal or leave it blank to run the job for all journals.
  • $T_ODOC: For Infor Baan, specify the T_ODOC column value of the TTFGLD106<CompanyCode> table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $G_TRANSACTION_ID: For NetSuite, specify the TRANSACTION_ID column value of the NS_TRANSACTIONS table in the source database to run the job for the required journal or leave it blank to run the job for all journals.
  • $G_HEADER_KEY: For Deltek Costpoint, specify the LVL1_KEY column value of the GL_POST_SUM table in the source database to run the job for the required journal or leave it blank to run the job for all journals.

SC AVL Jobs

The list of variables for the SC_CI_STAGE_LOAD, SC_CO_STAGE_LOAD, SC_PO_STAGE_LOAD, SC_SI_STAGE_LOAD jobs.

  • $FILE_PATH: (for UC) Indicates the location of the file.
  • $G_RUN_OT: Indicates whether to execute the job once (1 to run, 0 otherwise).
  • $G_RUN_CDC: Indicates whether to execute incremental runs (1 to run, 0 otherwise).
  • $G_SLT: Indicates whether the documents can be loaded into the SLT Replication Server (1 to enable SLT for the data load, 0 otherwise).
  • $G_DB_TYPE: Indicates the database type (HANA, Microsoft_SQL_Server).
  • $G_MANDT: Indicates the client that is used for SAP Central Finance.
  • $G_DB_VERSION: Indicates the database version.
  • $G_ERP: Indicates the ERP name, such as InforLN, EBS, PSFT, D365FNO, or UC.
  • $G_FROM_DATE: Indicates the start date for processing journals in the DD-MON-YYYY format. For example, 29-MAR-2022.
  • $G_TO_DATE: Indicates the end date for processing journals in the DD-MON-YYYY format. For example, 29-MAR-2022.
  • $G_CI_IDor$G_CO_IDor$G_PO_IDor$G_SI_ID: Indicates the customer invoice, customer order, purchase order, or sales order ID respectively.
  • $IF_RECON: Indicates whether reconciliation should be executed. Always set to 1.
  • $G_SLEEP: Indicates the delay between each run of a job in milliseconds; modify the value based on the size of the data load with a minimum of 900000 and a maximum of 3600000, which is the default value.
  • $G_SOURCE_SYSTEM: Indicates the source system name.
  • $G_SOURCE_COMPANYCODE: Indicates the company code value in the source.
  • $G_TARGET_COMPANYCODE: Indicates the company code value in the target.
  • $G_LOGICALSYSTEM: Indicates the logical system for which the account balances data is loaded into the staging schema from the source system and SAP S/4HANA.
  • $ARCHIVE_FILE_PATH: (for UC) Indicates the location of the archived file.
  • $G_LOOKUP_CHANGES: Indicates whether to refresh the master lookup cache during the journals job (1 = yes, 0 = no).

Reconciliation Jobs

The list of variables that you must provide before running the Reconciliation data-related jobs are as follows:

  • RECON_DEL_HIST Job:
    • $g_comp_code: Optional; indicates the code of the source company for which the data should be deleted in the LEVEL<1|2|3|4|5>_RECON%_STG tables in the staging schema.
    • $g_fiscal_year: Indicates the year for which the data should be deleted in the LEVEL<1|2|3|4|5>_RECON%_STG tables in the staging schema.
    • $g_fiscal_period: Indicates the period of the year for which the data should be deleted in the LEVEL<1|2|3|4|5>_RECON%_STG tables in the staging schema.
  • <SourceSystem>_Account_Recon Job
    • $G_LOGICAL_SYSTEM: Indicates the logical system for which the account balances data is loaded into the staging schema from the source system and SAP S/4HANA.
    • $G_Source_System: Indicates the source system.
    • $G_Fiscal_Year: Indicates the fiscal year to load balances.
    • $G_Fiscal_Period: Indicates the fiscal period to load balances.
  • <SourceSystem>_Source_Doc_Info, <SourceSystem>_Source_Doc_Info_CDC, <SourceSystem>_SRCDOC_Set_Status_Off, <SourceSystem>_SRCDOC_Set_Status_On Jobs
    • $SOURCE_SYSTEM: Indicates the unique number of the source system for which the journal information is loaded into the staging schema during the incremental data load.
  • SC_RECON Job
    • $G_Operation: Indicates the operation type - OT (one-time) or CDC (change data capture).
    • $G_MSSQL_SLT: Indicates whether to execute the SLT load for Microsoft SQL Server stage (1 = yes, 0 = no/HANA).
    • $G_MSSQL_S4: Indicates whether to execute the S4 load for Microsoft SQL Server stage (1 = yes, 0 = no/HANA).
    • $G_Source_System: Indicates the source system for the reconciliation.
    • $G_CLIENT: Indicates the client for fetching reconciliation data from S4 (not required for HANA).
    • $G_LOGICAL_SYSTEM: Indicates the logical system for the reconciliation.
    • $G_Postingdate_Start_Date: Indicates the start date for loading data. For OT operations, uses this specified date; for CDC operations, calculates as current date minus $G_NO_OF_DAYS.
    • $G_Postingdate_End_Date: Indicates the end date for loading data. For OT operations, uses this specified date; for CDC operations, defaults to current date.
    • $G_NO_OF_DAYS: Indicates the number of days prior to the current date to include in the data refresh.
    • $G_Recon_Report: Indicates which reconciliation levels to refresh. Default is all levels: 'L1,L2,L3,L4,L5,L0'.
    • $G_Location: Indicates the location to refresh for reconciliation data. Default is 'ALL'.
    • $G_SOURCE_TYPE: Indicates the source type being loaded.
  • RECON_L1_L3 Job
    • $G_Source_ID: Indicates the source system.
    • $G_RECON_REPORT: Indicates the reports that will be refreshed. Default is L1, L2, L3
    • $G_START_DATE: Indicates the reconciliation start date in YYYYMMDD format.
    • $G_END_DATE: Indicates the reconciliation end date in YYYYMMDD format.
    • $G_Operation: Indicates if the load is one-time or CDC.
    • $G_LOCATION: Indicates the location of the recon records to load. Default is ‘ALL’.
    • $G_LOGICAL_SYSTEM: Indicates the logical system for which the account balances data is loaded into the staging schema from the source system and SAP S/4HANA.
  • RECON_L4_L5 Job
    • $G_SUBSCRIPTION: Indicates the subscription name to be provided when the job is triggered for CDC load.
    • $G_MSSQL_SLT: Indicates whether to execute the SLT load for Microsoft SQL Server stage (1 = yes, 0 = no/HANA).
    • $G_MSSQL_S4: Indicates whether to execute the S4 load for Microsoft SQL Server stage (1 = yes, 0 = no/HANA).
    • $G_Source_System: Indicates the source system for the reconciliation.
    • $G_RECON_REPORT: Indicates the reports that will be refreshed. Default is L4,L5.
    • $G_LOCATION: Indicates the location of the recon records to load. Default is ‘ALL’.
    • $G_Operation: Indicates if the load is one-time or CDC.
    • $G_LOGICAL_SYSTEM: Indicates the logical system for which the account balances data is loaded into the staging schema from the source system and SAP S/4HANA.
    • $G_CLIENT: Indicates the client for fetching reconciliation data from S4 (not required for HANA).
    • $G_Postingdate_Start_Date: Indicates the start date for loading data. For OT operations, uses this specified date; for CDC operations, calculates as current date minus $G_NO_OF_DAYS.
    • $G_Postingdate_End_Date: Indicates the end date for loading data. For OT operations, uses this specified date; for CDC operations, defaults to current date.
    • $G_SOURCE_TYPE: Indicates the source type being loaded.
    • $CDC_HIST_DEL_DAYS: Indicates the required days to refresh CDC history.
    • $G_SLEEP: Indicates the delay between each run of a job in milliseconds; modify the value based on the size of the data load with a minimum of 900000 and a maximum of 3600000, which is the default value.
    • $G_MAIL: Indicates the email for job notifications.
  • SC_Level1_Refresh Job
    • $REAL_TIME_LOAD: If set to 1, initiates a refresh for the specified number of days. If set to 0, provides dates for the refresh activity.
    • $G_SOURCE_SYSTEM: Indicates the source system name.
    • $No_of_Refresh_days: Indicates the duration of the refresh in days.
    • $G_FROM_DATE: Indicates the start date for processing journals in the DD-MON-YYYY format. For example, 29-MAR-2022.
    • $G_TO_DATE: Indicates the end date for processing journals in the DD-MON-YYYY format. For example, 29-MAR-2022.

Cleanup Job

The list of variables for the SCT_CLEANUP job.

  • $SCT_FILEPATH: Indicates the location of the cleanup file when using a CSV input.
  • $ARCHIVE_CLEANUP_FILEPATH: Indicates the location of the archived CSV cleanup file.
  • $ARCHIVE_FILEPATH: Indicates the location of the archived file containing records of the deleted data.
  • $G_ERP: Indicates the ERP name.
  • $G_SOURCE_SYSTEM: Indicates the source system name.
  • $G_IF_CSV_INPUT: Indicates whether filters are loaded manually using a CSV file (Y) or updated automatically (N). The filters for automatic cleanup include: $G_FISCAL_YEAR, $G_COMPANY_CODE, $G_DOC_TYPE, $G_FROM_POSTING_DATE, $G_TO_POSTING_DATE, and $G_RUN_ID.
  • $G_IF_FIN: Indicates whether to delete FIN% data (Y).
  • $G_IF_STGONE: Indicates whether to delete MAGNITUDE_STG_ONE data (Y).
  • $G_IF_SLT: Indicates whether to delete SLT data (Y).
  • $G_RUN_ID: Indicates the run IDs to delete.
  • $G_FISCAL_YEAR: Indicates the fiscal year to delete.
  • $G_COMPANY_CODE: Indicates the company code to delete.
  • $G_DOC_TYPE: Indicates the SAP Central Finance document types to delete.
  • $G_FROM_POSTING_DATE: Indicates the start date for deleting data.
  • $G_TO_POSTING_DATE: Indicates the end date for deleting data.

 

 

Was this article helpful?

We're sorry to hear that.