Skip to main content
insightsoftware Documentation insightsoftware Documentation
{%article.title%}
Published:
Was this article helpful?
0 out of 0 found this helpful

ERP Ledger Transactions to Bizview Datastore

This topic describes the process for enabling integration of ledger transactions from the ERP system to Bizview Datastore database.

This topic contains the following sections:

Map Dimensions to Ledger Transaction Columns

Access this setting by following the path: System Administration > Data Services > CONFIGURATION > ERP Adapter Configuration.

See examples below for Jeeves configuration:

IntegrationConfiguration

 

IntegrationConfiguration3

Possible values for ERP Tag Id are listed in .

 

Adjust the Starting Point for Ledger Transactions

The integration job has a predefined parameter named @FROM_ISOMONTH.

This parameter has two objectives:

  • To limit the transactions (based on ISOMONTH) that are loaded from the ERP system to the staging table in Bizview.

  • Existing transactions with ISOMONTH >= @FROM_ISOMONTH in the Datastore will be deleted and fully replaced by the validated transactions from the staging table

To set the parameter value for @FROM_ISOMONTH:

Open Template Job (e.g. ADP_JV).

Change the job parameter value for @FROM_ISOMONTH to the preferred value:

Job_param

 

job_param_value

 

Test: Update Transactions to Datastore

The next step is to test the integration data flow for ledger transactions.

Run Integration Job

Select steps 50 through 80:

job_steps2

Check for Errors

The steps for checking errors are similar to those in Object Integration.

Analyse Validation Errors

  • Use SQL Server Management Studio

  • Connect to the Bizview datastore DB

  • Execute statement

 

selectdistincterror_code,error_value,error_descr

from stgerr.v_fin_ledgertranswherejob_id='5721'

 

The query result will be all rows (with all columns) of the loaded transactions in the staging table (st.fin_ledgertrans), that failed the validation process with error code 301.

Next step:Scheduling the Integration Job

Published:

ERP Ledger Transactions to Bizview Datastore

This topic describes the process for enabling integration of ledger transactions from the ERP system to Bizview Datastore database.

This topic contains the following sections:

Map Dimensions to Ledger Transaction Columns

Access this setting by following the path: System Administration > Data Services > CONFIGURATION > ERP Adapter Configuration.

See examples below for Jeeves configuration:

IntegrationConfiguration

 

IntegrationConfiguration3

Possible values for ERP Tag Id are listed in .

 

Adjust the Starting Point for Ledger Transactions

The integration job has a predefined parameter named @FROM_ISOMONTH.

This parameter has two objectives:

  • To limit the transactions (based on ISOMONTH) that are loaded from the ERP system to the staging table in Bizview.

  • Existing transactions with ISOMONTH >= @FROM_ISOMONTH in the Datastore will be deleted and fully replaced by the validated transactions from the staging table

To set the parameter value for @FROM_ISOMONTH:

Open Template Job (e.g. ADP_JV).

Change the job parameter value for @FROM_ISOMONTH to the preferred value:

Job_param

 

job_param_value

 

Test: Update Transactions to Datastore

The next step is to test the integration data flow for ledger transactions.

Run Integration Job

Select steps 50 through 80:

job_steps2

Check for Errors

The steps for checking errors are similar to those in Object Integration.

Analyse Validation Errors

  • Use SQL Server Management Studio

  • Connect to the Bizview datastore DB

  • Execute statement

 

selectdistincterror_code,error_value,error_descr

from stgerr.v_fin_ledgertranswherejob_id='5721'

 

The query result will be all rows (with all columns) of the loaded transactions in the staging table (st.fin_ledgertrans), that failed the validation process with error code 301.

Next step:Scheduling the Integration Job

For an optimal Community experience, Please view on Desktop
Powered by Zendesk