Oracle R12 GL : Enhanced Third Party Control Account Validations ( Restrict Manual Journals )


The Third Party Control Account feature in the Oracle E-Business Suite enables organizations to maintain detailed balances by third party for an account code combination. Subledger Accounting checks that valid third party information is associated with the journal line if the account code combination is a Third Party Control Account. If it is not, then Subledger Accounting rejects the journal line.
For example, when the unidentified receipts account code in the Oracle Receivables is defined as a Third Party Control Account, accounting for the unidentified receipts will fail because no third party information is available for such receipts. Similar issues are observed with the rounding account and intercompany accounts.

General Ledger prevents manual journal entries from posting to the Third Party Control Accounts. This ensures that journal lines that post to the control account codes such as Supplier Liability Account, Customer Receivables Account are associated with the valid third party information in the respective subledger modules.

The users might sometimes define an account code as a Third Party Control Account to prevent the GL manual journal entries from posting to these accounts. When such accounts are used in the subledger transaction without the third party information, Subledger Accounting prevents the accounting for such transaction with an error that the third party information is missing.

The described solution helps overcome these issues.
A new Third Party Control Account validation is provided that allows accounting to complete successfully without the third party information in the subledgers but to restrict that account code while entering in the GL manual journal entries.
A new value- ‘Restrict Manual Journals’- is added to the List of values of the Third Party Control Account segment qualifier.
Users can assign ‘Restrict Manual Journals’ value in the list of values of the Third Party Control Account segment qualifier to natural account segment values and prevent the GL manual journal entries from posting to these account code combinations containing the respective natural account segment values.

User procedures:
1. When the need is to define an account code as a Third Party Control Account for the sole purpose of preventing the GL manual journal entries from posting to these accounts then the user needs to select the value ‘Restrict Manual Journals’ in the list of values for the Third Party Control Account segment qualifier in the accounting flexfield segment value definition form, as shown in the attached screenshot.
Navigation path:

Setup> Financials>Flexfields>Key>Values

Query for your structure
Account segment>Segment Qualifiers> Select Third Party Control Account qualifier
Save.
At this point the user will not be able to select this particular account code while creating a manual journal entry in the GL. But the user can still select these account codes without the third party information in the respective subledgers because the system treats this third party control account for the purpose of restricting the usage in the GL manual journal entries only.

2. After the setting up an account code as ‘Restrict Manual Journals’ Third Party Control Account as shown in the attachment, the user needs to run the concurrent program ‘Inherit Segment Value Attributes’ to reflect the Third Party Control Account qualifier changes in the account code combinations.

Note: it is advised not to change the qualifier from ‘Supplier’/’Customer’ to ‘Restrict Manual Journals’ for existing accounts, but rather to define new accounts that will be set up as restricted for GL usage from the beginning.
Such a change, if performed, would affect the subledger reports that consider these qualifiers(e.g. ‘Third Party Balances Report’ -which would still show data from the past, before the change was made) .

Oracle R12 – Time Zone Support : Enabling Multi Time Zone Features


Release 12 of Oracle E-Business Suite includes as standard a feature called User-Preferred Time Zone Support

Conceptually, there are two types of date fields:

  • Dates with a time component – used to indicate a specific point in time within a particular day
  • Dates without a time component – used to denote a particular day, but not a specific point in time within that day

Date fields with a time component can be represented in any time zone, and thus displayed in whichever time zone is most meaningful to the end user. Generally, users prefer to view dates in their own (local) time zone. With the user-preferred time zone feature enabled, date with time fields will be converted to the user’s preferred time zone for display.

As per “Oracle E-Business Suite System Administrator’s Guide – Configuration” guide , For user-preferred time zone support to operate correctly, all of the following must be true:

  • The operating system time zone setting for the database server must be set to the standard corporate time zone.
  • The database must be configured to use the time zone file timezlrg.dat rather than the timezone.dat file.
  • The database must be started in the standard corporate time zone.
  • Every application tier JVM (Java Virtual Machine) must be started in the standard corporate time zone. This can be achieved by setting the application tier operating system time zone to match the standard corporate time zone.
  • Profile ‘Server Timezone’ (SERVER_TIMEZONE_ID) must be set at site level, and must be set to the same standard corporate time zone as the database.
  • Profile ‘Client Timezone’ (CLIENT_TIMEZONE_ID) must be set at user level. This is applicable to Oracle Forms based UIs.
  • Preference ‘Timezone’ must be set at user level. This is applicable to HTML based UIs.
  • Profile ‘Enable Timezone Conversions’ (ENABLE_TIMEZONE_CONVERSIONS) must be set to ‘Yes’ (or ‘Y’) at site level.
  • Profile ‘Concurrent: Multiple Time Zones’ (CONC_MULTI_TZ) must be set to ‘No’ (or ‘N’) at the site level.
  • Environment variable FORMS_APPSLIBS must be set in the Forms tier
  • Forms must be launched through the Personal Home Page or Navigator portlet.

image

image

Fusion Applications – Overview Educational Webinar- 19-Dec-2012 : 12:00 Noon India time


Dear All

Oracle Fusion Applications were designed, from the ground, up using the latest technology advances and incorporating the best practices gathered from Oracle’s thousands of customers. They are 100 percent open-standards-based business applications that set a new standard for the way we innovate, work, and adopt technology. Oracle is conducting a webinar on Fusion Applications for the India OAUG user community
Webinar from Oracle is scheduled on 19-Dec-2012 at 12:00 noon (IST).   This is India Standard time.

Please register now to attend this webinar. Registration link is given below:

http://secure.meetingexpectations.com/oaug/Groups/GroupConferenceRegistration.aspx?grpGCID=1598

You may like to join OAUG if you are not member alreay.
All registered participants will be provided Webex and Audio Information