OracleAppsBlog

A day in the life of an Oracle Applications Consultant

General Ledger

Sunday, November 29, 2020

Setting up Control Accounts and Restricting GL Manual Journal Posting

One of the options to consider when setting up the nominal segment within your Chart of Accounts is what your Third Party Control Account values should be. Before doing this its critical to understand what options are available and the impact of selecting these. Hence, I thought I’d put together a brief post explaining these.

The image below depicts where within the value set you would select the appropriate option and is followed by an explanation of the resultant impact.

Third Party Control Account Options

General Ledger journals can be entered directly in that module or be received from a Subledger. Since control accounts should accurately reflect the movements in a related Subledger its ideal that we only allow postings to these that are sourced from the Subledger. Hence, minimising the number of manual postings to a control account is recommended and makes Subledger to General Ledger Control Account reconciliation a lot simpler.

Whichever option is chosen below will determine the allowed journal source for a GL nominal account and the level of restriction to be applied:

1. Customer Control Account - only journal postings sourced from Accounts Receivable can be posted to this nominal.
2. No - either this is not a control account or you want to allow any type of journal to be posted to this account.
3. Restrict GL Manual Journals - journals with a source of Manual which are those entered directly into General Ledger will not be allowed. This provides more flexibility in that any Subledger can post to this account.
4. Supplier Control Account - only allow journal postings sourced from Accounts Payable can be posted to this nominal.
5. Third Party Control Account - only allow journal postings sourced from Accounts Receivable or Payables can be posted to this nominal.

Inherit Segment Values

Following any updates to a value set its important to point out that you should run the Inherit Segment Value Attributes program. This will propagate the attributes of a segment value to all account combinations that contain that segment value. Note that selecting the Create Execution Report option when running this program produces a report which lists each updated account for comparison including original and current attributes. Download an example of the Segment Value Inheritance Execution Report

Friday, February 03, 2006

Oracle Navigation and ADI Tip Sheets

Last year I worked with Nici Aldridge on an IMSCAN document management and scanning solution for an Oracle E-Business Suite implementation. Nici is an Oracle Applications Consultant who does quite a substantial amount of Oracle Training - read her profile here. She shared with me some “tip sheets” she has produced for Oracle Applications Navigation and Oracle’s Application Desktop Integrator (ADI). These tips sheets are very short documents which are aimed at providing users with the basic information they need to get started with.

Other tip sheets are available for:

• Office 2000 - Generic Information for Office 2000
• Word 2000 - For those converting to Word 2000
• Outlook 2000 - For those converting to Outlook 2000
• PowerPoint 2000 - For those converting to PowerPoint 2000
• PowerPoint for Presenters - Suggestions for using PowerPoint effectively in PC-based presentations
• Visual Aids - Suggestions for choosing and using visual aids, including PC slides

Thursday, April 07, 2005

FSG YTD-Actual Problem and Resolution

This post contains the solution for a small problem we encountered when trying to produce an FSG report.

When trying to produce an FSG report in ADI the other day we noticed a problem with the YTD-Actual column in the report. We wanted to print the report as at December 2005 (i.e. the last month of the year) so that we could see what the budget figures looked like. When trying to print the report in this fashion the YTD-Actual column for Dec 2005 was displaying zero values even though we knew there should be data in the report. We tried printing the report from within General Ledger but still the same result, zero values in the YTD-Actual Column. We knew that there should be values in this column as January and February had already been closed and most of the entries for March had been processed. Even when performing a drill down to the detail in the General Ledger we could see that there were values present.

The problem was a simple one which we found the resolution for buried in point 30 of Metalink Note:108236.1 entitled FSG Functional FAQ. The solution suggested that in order for the YTD-Actual data to display in the report you should ensure that the GL periods upon which you were reporting should be open or closed. In our instance the periods from April to December were still Future Enterable and hence we resolved the problem by opening these periods and immediately closing them so that they now had a status of closed. Once this simple task had been performed we were able to see data in our report.

Tuesday, February 15, 2005

Journal AutoReverse Profile Option

This post highlights a profile option you need to be aware of when setting up AutoReversing journals.

Oracle Apps gives you the ability to manually or automatically reverse posted journals into subsequent accounting periods. We set up AutoReversing journals at a client site the other day so that the journal would automatically reverse in the next non adjusting accounting period i.e. if you were in period 12 of a year it would not reverse the entry in period 13 (an adjustment period) but rather into the first period of the next year. A typical example of where you might want to do this is in the case of an accrual that you raise at the end of month which you now want to reverse in a subsequent month - see the diagram below.

Having completed the setup our expectation was that the journal would reverse when opening the next month (which is the trigger that runs the Automatic Reversal Programme). To our surprise the journals didn’t automatically reverse in the next month, however, the solution was a simple one. By setting the Profile option GL: Launch AutoReverse After Open Period to Yes we now found that when opening the next accounting period two concurrent requests were spawned, one to reverse the journal and another to post it (as enabled by selecting the AutoReverse and AutoPost Reversal options shown in the above diagram) . If you do forget to turn on this profile option as we did, you can still go and manually reverse the journal by choosing the following navigation path in General Ledger: Journals > Generate > Reversal. The result will be a list of journals which you can manually choose to reverse as shown in diagram below.

Further Information

Also refer to these two processes documented using Oracle Tutor at the Enterprise Services Center Helpdesk

• Defining AutoReversal Criteria
• Monthly AutoReverse Journals

Friday, February 04, 2005

ADI Journal Upload Problem Resolution

I received an interesting error message when trying to perform a journal upload in ADI at a client site yesterday, here’s the solution to the problem.

The error message received was “Segment is not defined, is a parent, or is disabled.”

According to Metalink Note:160622.1 the cause is as follows: -

The validation that ADI uses for client side validation cannot dynamically create a new flexfield, only the server-side validation has been designed to dynamically create valid flex code-combinations - Bug:1924015.

The simple solution to the problem is to set the Profile Option profile Flexfields: Validate on Server to Yes. It’s also important to note that Cross-validation checking is only performed if you have this option set to Yes.

Another Metalink Note 251463.1 provides the same solution for the system allowing the upload of Disabled Accounting Flexfield segments to General Ledger via ADI.