Hi,

In case of cash basis accounting, payments are directly interfaced to Projects and then they can be directly queried from expenditure inquiry using payment number.

But in case of accrual based accounting, only if there is any discount on payment and it has got interfaced to Projects, then only payment number field can be used to query directly in expenditure inquiry.

A major accounting method that recognizes revenues and expenses at the time physical cash is actually received or paid out.

This contrasts to the other major accounting method, accrual accounting, which requires income to be recognized in a company's books at the time the revenue is earned (but not necessarily received)

and records expenses when liabilities are incurred (but not necessarily paid for).

When transactions are recorded on a cash basis, they affect a company's books only once a completed exchange of value has occurred; therefore,

cash basis accounting is less accurate than accrual accounting in the short term.

On the contrary, Accrual Accounting is:

An accounting method that measures the performance and position of a company by recognizing economic events regardless of when cash transactions occur.

The general idea is that economic events are recognized by matching revenues to expenses (the matching principle) at the time in which the transaction occurs rather than when payment is made (or received).

This method allows the current cash inflows/outflows to be combined with future expected cash inflows/outflows to give a more accurate picture of a company's current financial condition.

When you define a ledger, you can enable an option for the ledger to use cash basis accounting. Otherwise, the ledger uses accrual basis accounting.

You cannot define both for a Ledger. Please review the following note:

Project Costing With Cash Basis Accounting in Release 12 (Doc ID 420988.1)

You can check also the following note:   Advanced Resolution Center : Overview of Procure to Pay Integration With Project (Doc ID 2889264.2).

Thanks and regards,

Anca

Hi Shashank,

Our recommendation is to apply the solution from Doc ID 454258.1.

If you would like an investigation on your particular encountered issue, we recommend you to open an SR in order for an EBS engineer to troubleshoot the issue further determine an alternate solution if that will be the case.

Regards.

Hi,

1) For troubleshooting, you can use Test Workbench from the following note:

How To Run A Real Transaction Test In Approvals Management Test Workbench (Doc ID 2318303.1)

This indicates that the source of these values can change based on the data source/flow.

For General Ledger journal approval the transactionIdIn value is the batch_id from gl_je_batches table.

Reviewing the Approval Management Engine (AME) journal approvals setup, the following is selected to be used and is the same for the API.

Transaction type = GL Journal Approval

Transaction Type id = GLJOURNAL (transactiontypeIn)

You cand check AME Exception Log and use also AME Analyzer from Note 2332426.1 EBS Approvals Management Analyzer

2) You may check also the setup from the following note: Oracle General Ledger (GL) Practical Guide: Approvals Management Engine (AME) Journal Approval (Doc ID 2624906.1)

You can review also the following note: Oracle General Ledger Journal Approvals Integration with Oracle Approvals Management (AME) and Oracle Workflow (Doc ID 2038960.1)

from the section: To configure Oracle Approvals Management (AME) Rules, ensure you use the responsibility “Approvals Management Business Analyst”.

i. If the usage type selected is “Dynamic”, then you must write a SQL Query to derive the approver list.

For more details on how to use the AME Attributes refer Oracle Approvals Management Implementation Guide.

ii. If the usage type selected is “Static”, then the Approver Type will need to be updated.

i. Testing your AME rules for Oracle General Ledger Journals

i. To ensure that the AME rules satisfy the conditions and actions you can create a journal and then test it using the AME Test Workbench before submitting the journal for

approval. It is advisable to test every time AME rules are modified or for debugging of journals.

ii. If the submitted journal satisfies AME rules, it will follow the Approval Hierarchy which is set in the AME setup in the Action Type.

iii. In case the journals do not satisfy any of the AME Rules, and complete in error, then you can use the Test Workbench for further investigation.

3) You can review the related example from the following note:

Approval Management Engine (AME) Setup and Usage Video Series (Doc ID 2612266.2) -- Supervisory Level Hierarchy

Thanks and regards,

Anca

Gotta love an intermittent problem! Is there any more to the error message? Is this sent to SYSADMIN? Initially, I'd say that you need to look at your AME Approver Group and how it selects Approvers, as well as some of the Mandatory Attributes. Have you tried looking at it through the AME Test Workbench? That might tell you something.

Here are some notes which could apply. Some are pre-R12.2, but they might still be useful.

R12: GL AME Journal Approval Is Getting Error "No Approver Was Found To Approve Your Journal Batch". (Doc ID 2395351.1)

"No approver was found to approve your journal batch XXX " ,In Journal Approval Integrated With AME (Doc ID 2184018.1)

Journal Approval Workflow with Error Message 3120 'No Approver Found' (Doc ID 268635.1)

Journals Not Getting Approved Through AME: No Approver Found / ORA-20001: Possible Loop in A Chain of Authority (Doc ID 2426150.1)

I hope these help answer your question.

Hi,

You may review the following note : Posting Journals to Prior Periods (Doc ID 1010243.7)

When posting to a prior period, Oracle General Ledger automatically updates the beginning balances of all the following periods. For prior year adjustments this will roll forward the P&L balances to the retained earnings when it reaches the year end. Make sure retained earnings account has not subsequently been disabled.

Thanks and regards,

Anca

Hi,

A) General Ledger automatically posts the net balance of all Revenue and Expense accounts from the prior year to the Retained Earnings Account (REA) when you open the first period of a fiscal year.

GL will automatically update the Retained Earnings Accounts balances as needed, when you enter and post new journal entries to the prior year.

The Retained Earning Account balance for a new year is cumulative and is the result of:

the current balance of Retained Earning Account + net balance of all Revenue and Expense accounts

You can check the following note: General Ledger FAQ for Retained Earnings (REA) (Doc ID 136510.1)

B) As you are saying that you are using glbalfix script and asking about the account type of REA.

I would recommend to review the following note:

Wrong Balance For Retained Earnings Account After Glbalfix (Doc ID 1435136.1)

C) You can review also the following notes:

How to Correct Misclassified Account After Having Run The Year End Closing Journal (Doc ID 295033.1)

What is the Behavior of the General Ledger Year End Closing Process (Doc ID 149999.1)

R12: Scripts to Check Year-End Carry Forward of Actual Balances and Retained Earnings (Doc ID 1365597.1)

Scripts To Check the Impact of a Specific Balancing Segment Value into Retained Earnings Account over Year-End (Doc ID 2684510.1)

Thanks and regards,

Anca

Hi,

In addition with Chandra response, you  can review the following notes:

EBS General Ledger:Security Features (Doc ID 2734537.1)

General Ledger Security Features Video Series (Doc ID 2440781.2)

You can check also the following note:

Data Access Set for Multiple Ledgers With Different Calendars - Is This Possible? (Doc ID 2590469.1)

Thanks and regards,

Anca

Hi Krishna,

Data Access Set is a Security feature and Ledger Set is a feature to facilitate easy use maintenance of multiple ledgers.

When you create a Ledger in R12, a default data access set with the name of the Ledger created would be automatically created. 

You can also create Data Access set and assign ledgers or Ledger Set under the Data accesss set.

You need to assign the data access set to the responsibility by setting GL : Data Access Set profile option to enable the responsibility to access the Ledger. 

You can also use the Data Access Set to restrict access to a particular balancing segment or management segment so that you restrict access only to those segments.

Unless you set the profile GL: Data Access Set, you will not be able to access the ledger. As such Data Access Set is mandatory.

On the other other hand, when a number of ledger have the same COA and Caledar, you can create a Ledger Set. The idea of ledger set is to enable management of multiple ledgers. For example, when you want to open period, you can use ledger set to open period for multiple ledgers. You can also use Ledger Sets in FSG so that you will be able to generate financial statements from multiple ledgers. Creating and using Ledger set is optional depending on your requirement regarding management of multiple ledgers.

Definition Access Set:

• It helps in managing and restricting user access to critical configuration and setup information.
• It controls user access to specific definitions within Oracle EBS, such as accounting flexfield structures, calendars, and currencies.

Hello @User_WGL1S

Basically if the calendar needs to be changed from calendar to fiscal.This can be fixed as long as the periods concerned have not been used in practice it usually means it is fixed in the following year (for 11i see Note:102460.1 a similar note does not yet exist for r12 at this point.

See also What Are The Year Types 'Fiscal' And 'Calendar' Used For ? (Doc ID 1013624.102)

R12: Calendar Changes that can be Supported in General Ledger (GL) (Doc ID 1061798.1)

Please find more details in below note:

General Ledger FAQ for Calendar (Doc ID 134362.1)

Regards.

Marx R.

Hi,

If the GL posting process is canceled midway using front end application, the system typically rolls back the incomplete transaction to maintain data consistency.

• This rollback ensures that the financial data in the General Ledger remains accurate and reflects only completed transactions.
• In case the session is killed from the back end, then You can run General Ledger Analyzer to check if the cancellation has caused any balance corruptions.