Defining account detail requirements for Oracle General Ledger

Define your organization's account detail (code combination) requirements for interface transactions. ERP applications typically provide a flexible accounting structure that enables you to customize general ledger account codes.

For both Flex SQL configuration and the General Ledger Feed process, each segment on the ERP General Ledger must have a corresponding segment value defined in Infor EAM. These definitions are determined during the Financial Interface Scope Task. Infor suggests that a qualified Infor technical services consultant assist in this process.

To define account detail requirements for Oracle General Ledger:

Define your organization's chart of accounts structure in the ERP application. Your chart of accounts structure outlines the account code segments required for conducting your business transactions.
Review the Infor EAM business transactions that have a financial effect on your organization.
Define accounting requirements for each business transaction identified during the previous step. When defining these requirements, consider the number of account code segments required by your organization. Additionally, consider what values are allowed for account code segments, as well as the expected and default values for each account code segment. Identify routine cases, special cases, and validation requirements for each account code segment.
Determine your organization's method for collecting information required to create actual account code segments. When determining this method, try to achieve a balance among the effort required to set up the account code segments, the effort of entering and maintaining the segments in the system, the accuracy of the segments, and the amount the segments conform with your organization's fiscal policies. Consider who will be entering transaction information, what decisions must be made for each transaction, and what information is and should be available to the responsible party as they make decisions for each business transaction.

Note: Infor strongly recommends that you derive values for account code segments from entities within Infor EAM. For example, most charts of accounts include an organizational component, such as departments or cost centers. Map departments in Infor EAM to account code segments for your departments or cost centers, or define an object structure in Infor EAM that corresponds to your organizational department and cost center structure.
If your chart of accounts contains a project segment as a cost center, use Infor EAM project/budget codes to supply project segments by creating custom attributes for the PROJ (R5PROJECTS) entity in Infor EAM to store the account code segment values for one or all project account code segments.

You should also consider creating user attributes in Infor EAM that will store the account segment values. Creating these attributes allows you to enter the segment values without hard coding them into the fixed Infor EAM tables.