By nttcPayday Loans Online

Financial Integration in perspective

This chapter describes the main functions and objectives of Financial Integration. Financial Integration is one of the business objects of the General Ledger module. Information is given about the function of this business object within BAAN IV and how it is related to other modules.

Financial Integration within BAAN IV

The Financial Integration business object deals with setting up the link between the logistics modules of BAAN IV and the finance modules. The posting of transactions generated from the logistics modules to the ledger accounts and dimensions of the finance modules is controlled through the Financial Integration business object. Postings can be done in real time or batch mode, depending on the setting defined for the Transaction Real Time To Finance field in the Maintain Integration Parameters (tfgld4150m000) session.

 


Figure 1-1 The Financial Integration business object within BAAN IV

To use the integration features, the Link With Finance field must be set to yes in the parameters of each of the aforementioned modules. For detailed setup information on the link between each individual logistics module and BAAN IV Finance, see the separate chapters.

Mandatory sessions

 


Figure 1-2 Financial Integration Procedure

Note

This procedure does not include the mandatory sessions which are maintained in the logistics modules. A list of the mandatory sessions of other modules is shown in Section 1.3.

Maintain Integration Parameters (tfgld4150m000)

This session can only be used if a logistics module is set for the integration with BAAN IV Finance. This session controls the timing (real time or batch processing) and level of detail (compressed or uncompressed) for posting integration transactions to BAAN IV Finance.

Maintain Integration Elements (tfgld4120m000)

Integration elements are used to define the rules for posting from logistics transactions to dimension codes in BAAN IV Finance. This is done through key pieces of data from the logistics module, such as warehouse, item, project, country, supplier, customer, or cost price component. Mapping of these elements enables product line reporting, project reporting, and other userdefined reporting within the ledger.

This session only creates the integration element codes. The actual mapping is done in the Maintain Options by Integration Elements (tfgld4121m000) session after which the integration elements are assigned to transaction types for posting in the Maintain Transaction Types by Transaction Origin (tfgld4126m000) session.

Maintain Options by Integration Elements (tfgld4121m000)

Within each integration element, two options are available for mapping the information from logistics transactions to each dimension type. Each integration option can be mapped to dimensions individually or by a range, depending on the setting of the Realization field.

Note

The types of logistics data available for integration options are fixed and not user-defined.

Maintain Integration Relations by Range (tfgld4122s000)

This session is executed if the Realization field in the Maintain Options by Integration Elements (tfgld4121m000) session is set to by ranges. and is used to assign a range of integration options to a dimension for posting the financial transaction generated from logistic modules.

Maintain Integration Relations by Element (tfgld4123s000)

This session is executed if the Realization field in the Maintain Options by Integration Elements (tfgld4121m000) session is set to by elements and is used when a one-to-one relationship exists between the integration option and the dimension for posting the financial transaction.

Maintain Transaction Types by Transaction origin (tfgld4126m000)

Integration elements are assigned to financial transaction types in this session. The dimension is selected for posting to BAAN IV Finance based on the mapping defined for the integration element in the Maintain Integration Relations by Range (tfgld4122s000) or Maintain Integration Relations by Element (tfgld4123s000) sessions.

 

All sessions Heading 1.2 are used for posting to BAAN IV Finance at a dimension level, rather than at a ledger account level.

The following sessions are used to define the ledger accounts for posting of the financial integration transactions. Although these sessions can be maintained in this business object, they are actually part of the logistics modules.

Maintain Inventory and WIP Transactions (tdinv8150m000)

This session can be executed only if the Link with Finance field is set to yes in the Maintain INV Parameters (tdinv0100m000) session. This session identifies the ledger accounts to be debited and credited whenever any transaction related to inventory or production is generated from the logistics modules. The postings can be defined based on financial supplier group, warehouse, item group/item, or cost price component.

Maintain Project Transaction Accounts (tipcs8150m000)

This session can be executed only if the Link with Finance field is set to yes in the Maintain PCS Parameters (tipcs0100m000) session. This session identifies the ledger accounts for posting of projectrelated financial transactions. The postings can be defined based on financial supplier group, financial customer group, project, or cost price component.

Maintain Invoice Analysis Accounts (tdsls6101m000)

This session is used to define the ledger accounts for posting of the late payment surcharges and order discounts related to sales invoices. The ledger accounts can be maintained by country or for all countries depending on the setting of the Account Numbers by Country field in the Maintain Financial Integration Parameters (tdsls6100m000) session.

Maintain Invoice Analysis Accounts by Tax Code (tdsls6103m000)

This session is used to maintain the liability accounts for sales tax on invoices. The ledger account for tax can also be defined in the Maintain Tax Codes by Country (tcmcs0136m000) session.

 

This session is used to maintain the ledger accounts for posting revenue (sales turnover) and cost of goods sold (material cost and operation cost) for sales invoices. The ledger accounts for posting to BAAN IV Finance can be defined by financial customer group, warehouse, item group, item, or a combination of these.

Maintain Accounts for Invoice Analysis (tssma6106m000)

This session is used to maintain the ledger accounts for posting the late payment surcharge related to service invoices. The ledger accounts can be maintained by country or for all countries depending on the setting of the Account Numbers per Country field in the Maintain Parameters for Link with Finance (tssma6100m000) session.

Maintain Accounts for Contract Installments (tssma6103m000)

This session is used to maintain the ledger accounts for posting service contract revenue and forecasted cost for a service contract with a customer.

Maintain Accounts for Service Orders (tssma6102m000)

This session is used to maintain the ledger accounts for posting revenue and cost of service orders. Costs are incurred on a service order are invoiced depending on how the cost analysis type is defined. Cost analysis types are defined in the Maintain Cost Analysis Type (tssma3112m000) session. Cost analysis types which require invoicing must have ledger accounts for revenue defined as well as for cost in this session. If no ledger accounts are assigned to a particular cost type, the financial transaction posting will default to the ledger accounts assigned to the other cost type.

Maintain Accounts for WIP (tssma6101m000)

This session is used to maintain the ledger accounts for posting the cost of service orders which have not yet been closed with the Close Service Orders (tssma3144m000) session. Once service orders are closed, the value in the work in process ledger accounts is reversed and the cost is booked to the ledger accounts defined in the Maintain Accounts for Service Orders (tssma6102m000) session.

Maintain Accounts for Service Orders by Contract Type (tssma6105m000)

This session is used to maintain the ledger accounts for revenue and cost related to service orders. Each contract type can have separate ledger accounts for posting cost and revenue. The cost incurred on service orders is invoiced based on the cost analysis type maintained in the Maintain Cost Analysis Type (tssma3112m000) session. For cost analysis types involving the invoicing of service orders, ledger accounts are maintained for both revenue and cost.

 

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Set your Twitter account name in your settings to use the TwitterBar Section.