Scribd
Upload
100 views

Oracle Additional Interfaces - 2

This document discusses two ways to specify accounts in the GL_INTERFACE table in Oracle General Ledger: segment specification or code combination ID specification. For segment specification, valid segment values from enabled segments are loaded into the corresponding columns in GL_INTERFACE. Alternatively, a code combination ID can be entered to identify the account segments instead of specifying individual segment values. The document provides examples and recommendations for using each method of account specification.

Uploaded by

annu-agi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
100 views

Oracle Additional Interfaces - 2

This document discusses two ways to specify accounts in the GL_INTERFACE table in Oracle General Ledger: segment specification or code combination ID specification. For segment specification, valid segment values from enabled segments are loaded into the corresponding columns in GL_INTERFACE. Alternatively, a code combination ID can be entered to identify the account segments instead of specifying individual segment values. The document provides examples and recommendations for using each method of account specification.

Uploaded by

annu-agi
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Assigning Values for Accounts (Oracle General Ledger Users' Guide) Page 1 of 2

Previous Next Contents Index Navigation Glossary Library

Assigning Values for Accounts


You can specify your accounts in the GL_INTERFACE table in one of two ways: segment specification
or code combination ID specification.

Segment Specification

Assign an account value for each segment that you enabled in your General Ledger application. For
example, if you enabled four account segments, you need to first determine into which columns of the
GL_INTERFACE table you should enter data. This can be done by looking at the Column field of each
segment in the Key Flexfield Segments window. In this example we find that:

 Segment 1 corresponds to the column SEGMENT1

 Segment 2 corresponds to the column SEGMENT2

 Segment 3 corresponds to the column SEGMENT4

 Segment 4 corresponds to the column SEGMENT5

Note: The column named SEGMENT3 is not used.

Given the above information above, you should load the data as follows:

Data for Flexfield Load Into:


Segment 1 GL_INTERFACE.SEGMENT1
Segment 2 GL_INTERFACE.SEGMENT2
Segment 3 GL_INTERFACE.SEGMENT4
Segment 4 GL_INTERFACE.SEGMENT5

Load valid enabled segment values for your enabled segments into the GL_INTERFACE table. The
segment values must already be defined in your General Ledger application.

For example, value 01 is not the same as value 1. You can specify Maximum Size and Right-justify
Zero-fill Numbers when you define your value sets in the Value Sets form. Maximum Size indicates the
maximum width of each segment value that Journal Import expects. Right-justify Zero-fill Numbers
indicates whether your account should right justify and zero-fill numbers when you enter values for a
particular value set. If you have the Right-justify Zero-fill Numbers option enabled, and your Maximum
Size is three, then your segment value would be 001. However, if your Maximum Size is four, then your
segment value would be 0001. Journal Import does not allow null values in enabled segments.

Code Combination ID Specification

http://download-uk.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/gloiji04.htm 9/8/2008
Assigning Values for Accounts (Oracle General Ledger Users' Guide) Page 2 of 2

Alternatively, you can enter a code combination ID to identify your account segments. You can find a
list of valid account code combinations and their corresponding code combination IDs in the
GL_CODE_COMBINATIONS table. If you want Journal Import to use the code combination ID to
create your journal entries, enter the appropriate code combination ID in the
CODE_COMBINATION_ID column of the GL_INTERFACE table and do not enter values in the
SEGMENT1 through SEGMENT30 columns.

If you enter values for your account segments in the SEGMENT1 through SEGMENT30 columns and
enter a value in the CODE_COMBINATION_ID column, Journal Import uses the Segment column
values to create your journal entries.

If you enter segment values for an invalid account in the GL_INTERFACE table, General Ledger prints
the invalid account in your Journal Import Execution Report. If you enter a code combination ID and if
suspense posting is disabled, General Ledger prints the invalid code combination ID in your Journal
Import Execution Report. If you enter a code combination ID and if suspense posting is enabled,
General Ledger prints only the segment value separators in your Journal Import Execution Report.
Therefore, we recommend that you disable suspense posting if entering code combination IDs.

See Also

Overview of Setting Up

Defining Accounts

Understanding the GL_INTERFACE Table

Assigning Values for Additional Required and Conditionally Required Columns

Assigning Values for Currency Conversion

Assigning Values to Optional Columns

Required NULL Columns in the GL_INTERFACE Table

Importing Specialized Data

About Journal Import Validation

Previous Next Contents Index Navigation Glossary Library

http://download-uk.oracle.com/docs/cd/A60725_05/html/comnls/us/gl/gloiji04.htm 9/8/2008

You might also like