A day in the life of an Oracle Applications Consultant

Saturday, July 10, 2004

Automating the creation of account code combinations (CCID’s) in Oracle General Ledger

This post outlines two methods one can use to automate the creation of account code combinations in General Ledger

In certain instances it may be necessary to manually create account code combinations (CCID’s) in Oracle General Ledger. To some extent this is determined by whether your organization has decided to use dynamic insert or not. Dynamic insert is an option you can turn on or off when creating your accounting flexfield. If the option is turned on it will allow account code combinations to be automatically generated. If dynamic insert is turned off then it will certainly be necessary for a General Ledger Super User to go and create an approved set of combinations for use within your organization. Even if dynamic insert is turned on you may find that at the beginning of an implementation that there are not enough active account combinations. This means you will more than likely have to manually add account code combinations as presently Oracle has no automated facility to perform this. To manually add account code combinations one should login under General Ledger Super User and on the navigation menu go to Setup > Account > Combinations. Having navigated to the form displayed in Fig. 1 you can then insert the needed lines.

Figure 1: The Account Code Combinations Form Maintain General Ledger Account Code Combinations (CCID's) using this Oracle Form As manually adding account code combinations can be a rather tiresome job I investigated potential ways to automate the process and have come up with the following means of doing so: -

1. Journal Load via ADI

Using this option entails creating an excel spreadsheet journal via ADI with the account code combinations that you would like insert. The account code combinations should contain zero values. After uploading the spreadsheet journal from ADI an unposted journal will be created in General Ledger. The unposted journal can be deleted and the account code combinations that you created will remain behind. The reason for using the spreadsheet journal as opposed to using a journal in General Ledger is that the spreadsheet makes it easier to create the account code combinations you want to load as you can use the copy and paste features.

2. Use of DataLoad

A dataload template can be created and the account code combinations can be loaded directly into General Ledger.

Another tip

Personally I prefer to use the first method mentioned as it is much faster than using Dataload. Another word of advice when creating these combinations. One should ensure that you have correctly filled in the flexfield qualifiers (displayed in Fig. 2) when capturing your segment values as the account code combinations will use this information to determine how a CCID is created.

Figure 2: The Flexfield Segment Qualifiers

The Flexfield Segment Qualifiers should be correctly chosen to ensure proper creation of a CCID

For example, if for any of the accounts in the combination of segment values, you have allow budgeting and allow posting set to “no”, then the account code combinations as displayed in Figure 1 will be created with allow budgeting and allow posting set to “no”. If you create an account code combination with the incorrect value for allow budgeting and allow posting, you can go and manually change the value. However, if you have a large number of lines that have the incorrect values you cannot merely go and upload another blank journal after having corrected the mistake in the flexfield segment qualifiers. You will still have to manually make the amendments as once an account code combination has been created you cannot “overwrite” it.

Lastly, if anyone has come up with any other better method or an automated procedure for performing this activity then please add your comments.