Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Scribd
Upload
1K views

Loading GL Code Combinations Into Oracle

Oracle Applications allow for automatic generation of account code combinations when dynamic insert is enabled, but GLDI can be used to load multiple combinations in a single batch update. GLDI facilitates creating combinations in Excel and importing them through the GL_INTERFACE table without custom code. Alternatively, SQL*Loader can perform a similar loading of combinations, though with more setup and knowledge required.

Uploaded by

floatingbrain
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
1K views

Loading GL Code Combinations Into Oracle

Oracle Applications allow for automatic generation of account code combinations when dynamic insert is enabled, but GLDI can be used to load multiple combinations in a single batch update. GLDI facilitates creating combinations in Excel and importing them through the GL_INTERFACE table without custom code. Alternatively, SQL*Loader can perform a similar loading of combinations, though with more setup and knowledge required.

Uploaded by

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

Loading GL Code Combinations into Oracle

One of the best features about Oracle Applications is that you can let
the applications naturally generate account code combinations over
time providing "dynamic insert" is set to "on" (plus, you should have
also implemented cross-validation rules!). However, in some cases,
you may want to generate the GL code combinations yourself in a
single mass-update. The easiest way to do this without creating a
custom process is to use Desktop Integrator (GLDI).

Firstly, turn "dynamic insert" to on. Then use GLDI to create a journal
entry in Excel of all of your desired combinations. Next, load the
journal into the GL_INTERFACE table and import it. Once the journal is
imported, you can safely delete in within General Ledger. It will have
automatically created your combinations.

If you are not using GLDI, you can use SQL*Loader in a similar way (it
just takes a little bit more time and knowledge).

You might also like