Oracle GL Interview1
Oracle GL Interview1
More
Next Blog
Total Pageviews
9,751
Labels
Database (2)
Desktop Integrator (WebADI) (2)
E-Business Suite (12)
Financial Accounting Hub (FAH) (2)
General Ledger (15)
Interview Questions in R12 (4)
Linux OS (1)
Order Management (4)
Payables (3)
Receivables (8)
System Admin - Script (2)
System Administration (5)
6.Recurring Jv :this one is We define one template, we use Periodically, these are 3 types
1.Standard 2.Skeleton 3.Formula
Blog Archive
7.Mass Allocation Jv :Set of Expenses or Set of Revenue allocate different parts using Formula A*B/C
A is Total Cost Pool..B is Usage Factor...C is Total Usage Factor...
2013 (45)
December (26)
2014 (16)
November (2)
October (6)
September (11)
unable to see item in price list
LOV in r12 order ...
user defined exceptions in
package oe_schedule_uti...
Error while opening r12 sales
order form. EOERR: O...
Unable to See the Legal Entity
List of Value in th...
The difference between an average and standard balance sheet is that balances are expressed as average amounts rather Than actual periodend amounts. An average balance is computed as the sum of the actual daily closing balance for a balance sheet account, divided by the
number of calendar Days in the reporting period .
6) Is there a limit to the number of periods in a budget year or how many years a budget can span?
Ans) One can define budgetary control for n number of years however, one year can have maximum of 60 fiscal periods7)
Viewer
Live Traffic Feed
2. However, access to these Balancing Segment Values could be controlled through Security Rules being assigned to the Value Set and the
Respective Responsibility
3. The Key question is: If Legal Entity having the context to the Operating Unit that shares the common Ledger does not have assignment to it,
what impact it has on the integrity of data when this access is otherwise allowed, except through Security Rules?
converted by Web2PDFConvert.com
converted by Web2PDFConvert.com
converted by Web2PDFConvert.com
AR,AP,CM,FA,PO etc. This program looks after your SLA accounting rules and accordingly generates the entries and transfer them to GL.
If you want to see the journals first before transferring them to GL, you can run the same program in Draft mode before running in final mode.
If you have already run the create accounting but not transferred to GL, it is sufficient to run the "Transfer Journal Entries to General Ledger"
concurrent request.
converted by Web2PDFConvert.com
Segment Qualifiers
converted by Web2PDFConvert.com
Incorrect names will cause the Accounting Flexfield Compilation program to fail with the error:
oracle error 904 invalid identifier
ora-06512 at system.ad_dll, line 165
ora-06512 at line 1 has been detected in afuddl ()[3_xdd]
do_ddl(APPLSYS,.......)
View Name: %_VIEW
Name NULL? TYPE
------------------------------ ----- ----VIEW_HAS_FAILED_CHECK_LOG_FILE CHAR(61)
2. Can any changes be made to the Accounting Flexfield?
Any changes to an Accounting Flexfield that has been in use is NOT supported. This is documented throughout the GL
Users Guide.
This will cause data inconsistencies and data corruption.
Development and Support do not support changes to the accounting flexfield.
Changing your flexfield definition once you have used it to acquire data can cause serious inconsistencies with existing
data, which could cause data corruption.
For more information review the Oracle Applications Flexfields Guide in Defining Key Flexfield Structures:
Warning: Do not modify a frozen flexfield definition if existing data could be invalidated. An alteration of the flexfield
structure once you have any flexfield data can create serious data inconsistencies. Changing your existing structures
may also adversely affect the behavior of any cross-validation rules or shorthand aliases you have for your structures,
so you should be sure to manually disable or redefine any cross-validation rules and shorthand aliases to reflect your
changed structures.
If it is absolutely required to have changes on segments then a NEW ledger or set of books needs to be created with the
desired accounting flexfield.
The GL Consolidation feature can be used to transfer journals or balances from the existing ledger/set of books to the
new ledger/set of books with the new structure.
If Oracle Subledgers are used then they must also point to the new ledger/set of books. This may require Oracle
Consulting services.
3. Can segments be added to or removed from an existing accounting flexfield structure?
No - this will cause data inconsistencies and data corruption.
Development and Support do not support changes to the accounting flexfield.
Changing your flexfield definition once you have used it to acquire data can cause serious inconsistencies with existing
data, which could cause data corruption.
For more information review the Oracle Applications Flexfields Guide in Defining Key Flexfield Structures:
Warning: Do not modify a frozen flexfield definition if existing data could be invalidated. An alteration of the flexfield
structure once you have any flexfield data can create serious data inconsistencies. Changing your existing structures
may also adversely affect the behavior of any cross-validation rules or shorthand aliases you have for your structures,
so you should be sure to manually disable or redefine any cross-validation rules and shorthand aliases to reflect your
changed structures.
4. Can the segments of existing accounting flexfield structure be changed?
No. This will cause data inconsistencies and data corruption.
Development and Support do not support changes to the accounting flexfield.
Changing your flexfield definition once you have used it to acquire data can cause serious inconsistencies with existing
data, which could cause data corruption.
For more information review the Oracle Applications Flexfields Guide in Defining Key Flexfield Structures:
Warning: Do not modify a frozen flexfield definition if existing data could be invalidated. An alteration of the flexfield
structure once you have any flexfield data can create serious data inconsistencies. Changing your existing structures
may also adversely affect the behavior of any cross-validation rules or shorthand aliases you have for your structures,
so you should be sure to manually disable or redefine any cross-validation rules and shorthand aliases to reflect your
changed structures.
5. Do all segments of the accounting flexfield have to be enabled and displayed?
Yes. This is mandatory for all applications versions.
All segments must be enabled, displayed and required. Any other configuration is not supported.
From the Oracle Applications Flexfields Guide:
"If you are defining the Accounting Flexfield, you MUST display ALL segments. Hiding segments will adversely affect your
application features, such as Mass Allocations".
The only supported solution therefore, is to have all segments displayed from the start and for them to remain that way.
Oracle General Ledger does not support non-displayed segments. If you have non-displayed segments, it may be
possible that some functionality will work anyway.
However this is not guaranteed, and just because the functionality works at some point in time does not mean that it will
continue to work as bug fixes are applied and new releases are issued.
6. How to find which accounts are inactive?
Since Release 11i the standard report: Chart of Accounts - Inactive Accounts Listing can show the inactive accounts.
7. Can code combinations be deleted or purged ?
It is not possible to delete or purge the account code combinations and segment values. You can only end date the
combinations and segment values.
The reason why it is not possible is that all applications that interface journals to GL could potentially use the
combinations and you cannot remove a combination if it is used in a transaction.
Currently there is no process to determine if a code combinations is still referenced in any part of the EBS application.
Additionally, programs like translation check all the old values back to the earliest ever transaction in a separate table that
stores the code combinations. Also transactions that used the code combination are stored and still referenceable in the
subledgers, etc.
8. How to set up an Accounting Flexfield structure that has a dependent segment?
Define the accounting flexfield structure in two steps.
1. On the Key Flexfields Segments form, you have to Save the flexfield structure after you define the segment with the
independent segment (for example account). Then leave the form and come back.
converted by Web2PDFConvert.com
2. Now add your dependent segment (for example subaccount). You should see the dependent value set in the list of
values.
9. What is the recommended numbering for the Accounting Flexfield structure and why?
The Accounting Flexfield structure requires consecutive segment numbers beginning with 1, such as 1,2,3.....
Gaps in numbering like 1,10, 20,... are not supported. This could cause errors when compiling and in other General
Ledger functions.
10. Why are some of the segment separators displayed as question marks (?) ?
Check the descriptions of the Segment Values. If the same segment separator value (ie: dash) is used in the segment
value description, the actual segment separator on the chart of accounts will appear at times as a "?".
Posted by Suresh at 2:13 PM
No comments:
Post a Comment
Enter your comment...
Publish
Preview
Newer
Post
Home
converted by Web2PDFConvert.com