FA 2nd Ledger ER1

ORACLE APPLICATIONS
White Paper Secondary Ledger Enhancement for Oracle Assets - Setup
Written by Oracle Support Services Author: Date Created: Date Changed: Version: Harriet Reissenberger 21.02.2011 11.03.2011 1.1
Content
Introduction ............................................................................................................................................................................ 4 Goal...................................................................................................................................................................................... 4 Restrictions........................................................................................................................................................................... 5 Definitions ............................................................................................................................................................................... 6 Chart of Accounts (CoA) ................................................................................................................................................. 6 Currency........................................................................................................................................................................... 6 Ledger .............................................................................................................................................................................. 6 Secondary Ledger............................................................................................................................................................. 6 Valuation Method (VM)................................................................................................................................................... 6 General Overview of the setup steps..................................................................................................................................... 7 What are the setup steps that need to be made in GL? ..................................................................................................... 7 Secondary Ledger Enhancement - Setup ........................................................................................................................... 13 Case 1: Same Currency, Different CoA than in Primary................................................................................................ 13 Case 2: Different Currency, Same CoA as in Primary ................................................................................................... 20 Case 3: Different Currency and different CoA than in Primary ..................................................................................... 26 A Technical Perspective....................................................................................................................................................... 35 Troubleshooting.................................................................................................................................................................... 38 Missing exchange rate .................................................................................................................................................... 38 Create Accounting run for the Primary instead of the Secondary Ledger ...................................................................... 39 Create Accounting fails for the tax book using a different CoA .................................................................................... 40 Create Accounting fails without any error message and the output is empty................................................................. 41 Performing an Inter- or IntraCompany transaction, the InterCompany Receivable and Intercompany Payables Accounts are missing in the journal ............................................................................................................................... 42
Subledger Accounting Setup for Oracle Assets FA_2nd_Ledger_ER-1.doc Oracle/Client Confidential - For internal use only
ii
Document Control
Change Record
Date 21-Feb-11 11-Mar-11 11-Mar-11 Author Harriet Reissenberger Harriet Reissenberger Harriet Reissenberger Version A 1.0 1.1 Change Reference First draft First published version Added the Technical Perspective and the Troubleshooting section
Contributors
Name Sunil Chawla Organization Assets Development Title Senior Principal Applications Engineer
Reviewers
Name Bradford Ridgway Sunil Chawla Seamus Moran Louise Gareau Anshu Malhotra Role Title Applications Architect Senior Principal Applications Engineer Director Senior Principal Support Engineer Principal Support Engineer Date Reviewed
Document References
Document Title Oracle Assets User Guide Release 12, Part No. B31177-01 Oracle Applications Flexfields Guide Release 12, Part No. B31456-01 Oracle General Ledger Implementation Guide Release 12, Part No. B31219-03 Oracle General Ledger User Guide Release 12, Part No. B31218-03 Type of Reference Reference Manual Reference Manual Reference Manual Reference Manual Document Location My Oracle Support My Oracle Support My Oracle Support My Oracle Support
iii
Introduction
Goal
THE PURPOSE OF THIS DOCUMENT IS TO PROVIDE AN OVERVIEW on the new Secondary Ledger Enhancement for Oracle Assets in Release 12.1.
What is the new Secondary ledger enhancement for Assets?

This enhancement was created to meet global requirements around tax book and Secondary ledger accounting. Up to this enhancement, the ledger list of values (LOV) for tax books in Assets restricts to the same Primary ledger as the corporate book or an associated Secondary ledger which meets all three of the following conditions: 1) Valuation Method Enabled (use Primary amounts = no) 2) Same Chart of Accounts (CoA) 3) Same Currency These restrictions are now lifted and the following cases are allowed for tax books with the enhancement:
Book Class`
Corporate Tax Tax Tax Tax Tax
Main Ledger
Primary Primary Secondary Secondary Primary Primary
MC Classification
ALC ALC ALC ALC Secondary Secondary
COA
Currency
VM Enabled Required
N/A N/A N/A N/A Y Y
N/A Same as Corp Same As Corp Different Same as Corp Different
N/A Same as Corp Same as Corp Same as Corp Different Different
- Currently allowed Configurations - Additional allowed Configurations after the Enhancement
So, with this enhancement one can now set up three different configurations for tax books in Assets: 1. A Secondary ledger with the same currency as the Primary ledger, but a different chart of accounts 2. A Secondary ledger with the same chart of accounts, but a different currency then in the Primary ledger 3. A Secondary ledger with a different chart of accounts and a different currency then in the Primary ledger
In this document, we will describe how the setup for all three new cases is performed.
Restrictions
Please note that the following restrictions apply to this enhancement: Deferred Depreciation for Secondary Ledger is not supported Drill Down from SLA to Subledger is not supported for Secondary Ledger Standard Reports, including Variable Format (RXI) Reports, are not supported for Secondary Ledgers. This means that custom reports are necessary to report on and reconcile the asset books Only one Secondary Ledger can be attached to a Tax Book. The Accounting Calendar and Period Type of the Secondary Ledger(s) need to be the same as in the Primary Ledger. Therefore, the Fiscal Year for the tax books in Assets needs to be the same as for the corporate book, which in turn needs to match the fiscal year start and end date in the ledger and the period names also need to be the same as those in the Accounting Calendar of the ledger.
Definitions Chart of Accounts (CoA)

The Oracle General Ledger application provides different Accounting Flexfield (Chart of Accounts) structures for users of different sets of books. The Oracle General Ledger application determines which flexfield structure to use based on the value of the GL Ledger Name - formerly GL Set of Books Name - user profile option.
Currency
Every Ledger is kept in one Accounting currency, sometimes also referred to as functional currency within Oracle.
Ledger
The Ledger is what used to be called the General Ledger Set of Books. It consists of the currency, chart of accounts, accounting calendar, ledger processing options and subledger accounting method.
Secondary Ledger
It is a Secondary representation of the Primary ledger, but with a different set of rules as required.
Valuation Method (VM)

The Subledger Accounting setup determines whether a ledger is classified as valuation method driven as it correlates to the "Use Primary Amounts" flag in the SLA options for a ledger. In the case of Assets, the valuation method is the depreciation book.
General Overview of the setup steps What are the setup steps that need to be made in GL?
The very first step is to design the setup. The naming convention is quite important as it should be clear which CoA, ledger and tax book the user has in front of him. Just like with any ledger, the value sets need to be set up, which are then used in the Accounting Flexfield(s). The Accounting flexfield(s), calendar and currencies need to be set up. Then a rate type needs to be set up with the conversion rates for the cases where the Primary and Secondary ledger currencies are different. Note: if not using a daily rate, but a monthly or quarterly rate, then a conversion rate must be set up for the Date Placed In Service (DPIS) for every asset. One needs to define a mapping set for those cases, where the Primary and the Secondary ledger use a different Chart of Accounts. The easier way to map the Chart of Accounts is via Segment Rules rather than Account Rules as else one would have to map EVERY account combination in the Target Secondary ledger with the corresponding account combination in the Source Primary ledger. When these steps are performed, one can create the Primary and the Secondary ledger(s) via the Accounting Setup Manager. The Application Accounting Definition is then linked with the Subledger Accounting Method (SLAM), which in turn is then assigned to the Ledger. Note: The Subledger Accounting setup is valid for ALL depreciation books belonging to the ledger that is linked. When the Ledgers are set up, then a Ledger responsibility needs to be created for each ledger and at least one for Assets. For each responsibility, profile option GL Ledger Name needs to be filled with the correct ledger. For Assets, the Primary ledger needs to be chosen as the profile option GL Ledger Name value. The setup of the depreciation books will be discussed for each case as they differ depending on the case. We will now see how the Primary Ledger has been set up: Accounting Flexfield: HIR Primary CoA EUR consists of 4 segments. Segment 1 is the balancing segment. Segment 2 is the natural account segment. Segment 3 is the cost center segment and segment 4 is an unqualified segment called Product. The natural account segment is 4 characters wide.
The Accounting currency of the Primary ledger is Euro, ISO code EUR and a Subledger Accounting Method called HIR Primary EUR is used.
The following subledger accounting options were chosen in the Accounting Setup Manager:
10
And this Intracompany Balancing rule:
When setting up an Assets Book, there is no Ledgers tab. Only after having saved the book and then requerying it, will the Ledgers tab appear. We will discuss this tab in more detail when we are setting up the tax books.
The corporate book HIR CORP EUR is linked to Primary ledger HIR Primary Ledger EUR:
11
12
Secondary Ledger Enhancement - Setup
We will now go into the detailed setup for all three cases
Case 1: Same Currency, Different CoA than in Primary
In our first case, the Secondary Ledger uses a different Chart of Accounts but the same Accounting currency then the Primary ledger. So the Chart of Account (CoA) needs to be set up first. Then we define the Subledger Accounting method and the Chart of Accounts mapping before we can set up the Secondary ledger. In Assets, a tax book is set up that is linked directly to the Secondary ledger.
13
The Accounting flexfield also consists of 4 segments. Segment 1 is the balancing segment and has the same value set as the Primary ledger. Segment 2 is the natural account segment. Segment 3 is the cost center segment and has the same value set as the Primary ledger. Segment 4 is an unqualified segment called Project. The natural account segment is 6 characters wide and uses a different value set then the Primary ledger.
14
Note that the Chart of Accounts fields for the Secondary ledger need to be filled as follows: Transaction: CoA of the Primary Ledger, Accounting: CoA of the Secondary ledger
To make it a little easier, Segment Rules and not Account Rules were used for the Chart of Accounts Mapping. As the value sets for the balancing segment and the cost center segment are the same, the rule Copy Value From could be used. For the natural account, each target account has to be mapped to a source account as we are using a different account in our Secondary ledger. As segment Project does not exist in our source CoA, we used rule Assign Single Value with a default value of 000 for the Project segment.
15
We can now set up our Secondary ledger: Note that the Accounting Calendar and Period Type is the same as for the Primary Ledger.
We choose the Mapping set we have defined earlier. It is very important that the Journal Conversion Rule Post Journals Automatically from Source Ledger is set to No!
And for the Subledger Accounting Options, the option Use Primary Ledger Amounts also has to be set to No!
16
If Inter- or Intracompany Balancing has been set up in the Primary Ledger, then there must also be the same rule for the Secondary ledger.
Once the Secondary ledger setup is completed, the tax book can be set up in Assets in the Book Controls form. Note that this is the one case out of the three new enhancements, where the Secondary Ledger is chosen directly in the Ledger field of the Calendar tab.
17
The Ledgers tab will remain empty for this setup case.
Once the tax book is set up, one can continue setting up the asset categories for the tax book, basically continue with the regular tax book setup. When the setup is complete and assets are copied or added to the tax book and one is ready to run Create Accounting, then the Secondary ledger is defaulted as the ledger when choosing the tax book.
18
And here we have an example output of Create Accounting for this setup case:
And this is the Create Accounting output for the same transaction/event in the Primary Ledger:
19
Case 2: Different Currency, Same CoA as in Primary

In our second case, our Secondary Ledger uses a different Currency but the same Chart of Accounts then the Primary ledger. So there is no need to set up a different Chart of Account for this ledger. The Subledger Accounting Method needs to be defined, but no CoA mapping is necessary before we can set up the Secondary ledger. In Assets, a tax book is set up that is linked to the Primary ledger. After saving the tax book, it is requeried and a new tab appears in the Book Controls form where the Secondary ledger is assigned.
As we are now using a different currency, a rate type and rates need to be defined. We are using a rate type called Period End1 for our setup.
One can also use the Corporate rate type or any other type as long as rates are set up. Note: if not using a daily rate, but a monthly or quarterly rate, then a conversion rate must be set up for the Date Placed In Service (DPIS) for every asset.
Subledger Accounting Setup for Oracle Assets FA_2nd_Ledger_ER-1.doc Oracle/Client Confidential - For internal use only 20
Even though this is a Secondary ledger and not an Alternate Ledger Currency (ALC, formerly MRC), the behavior is the same. The exchange rate used is that of the DPIS and with every cost adjustment a weighted average is used to convert the Primary ledger amounts into the Secondary ledger currency. As the Chart of Accounts is the same as for the Primary ledger, we can now set up our Secondary ledger:
21
With these Currency Conversion options and Journal Conversion Rules:
Note that Post Journals Automatically from Source Ledger needs to be set to No! Equally important, Use Primary Ledger Amounts under Accounting Options is also set to No!
And again we have set up Intracompany Balancing Rules:
22
After we have completed our ledger setup, we can now set up our tax book in Assets. We link it to the Primary Ledger and save it once we have completed the normal set up. Note: The Ledgers tab does not appear when doing the normal setup. Note also: The Allow GL Posting check box is unchecked
Then we requery our new book and the Ledgers tab appears. We pick our Secondary Ledger and check Allow GL Posting and Enabled. Note: we can only chose 1 Secondary ledger and we cannot update it once saved! Also, once unchecking Allow GL Posting and/or Enabled, this also cannot be changed anymore!
23
When submitting Create Accounting for the tax book, the Ledger ID of the Secondary Ledger needs to be chosen:
And this is an example of what the output will look like. It is the same adjustment event we have looked at in the Primary and other tax book:
24
25
Case 3: Different Currency and different CoA than in Primary
As we are now using a different currency, a rate type and rates need to be defined. We are using a rate type called Period End1 for our setup.
One can also use the Corporate rate type or any other type as long as rates are set up. Note: if not using a daily rate, but a monthly or quarterly rate, then a conversion rate must be set up for the Date Placed In Service (DPIS) for every asset.
26
For this case we are using a Chart of Account that consists of only 3 segments, a balancing segment with the same value set as the Primary ledger, and account segment which is different than in the Primary ledger. It is the same account value set that was is used in case 1.
27
Therefore we will also have to create a mapping set with the Secondary CoA as the Target and the Primary CoA as the Source. Again we are using Segment Rules. As the value sets for the balancing segment and the cost center segment are the same, the rule Copy Value From could be used. For the natural account, each target account has to be mapped to a source account as we are using a different account in our Secondary ledger.
28
Setting up our Subledger Accounting Method, the Transaction Chart of Accounts is that of the Primary Ledger and the Accounting CoA is that of the Secondary Ledger.
We have set up rules to use the balancing segment value from the Default Account in the Book Controls form:
Note: When always using the balancing segment value from the default account in the Book Controls, Inter- and IntraCompany transactions will not work as when performing e.g. a transfer in the corporate book the tax book will always use the same balancing segment value and therefore a regular transfer will get created in that tax book.
29
We are now ready to define our Secondary ledger. Different Currency and CoA as in the Primary ledger, same calendar as required and different Subledger Accounting Method.
30
We choose the Mapping set we have defined earlier. As we are again using a different currency then in our Primary Ledger, we have to determine the Currency Conversion Rules with the Error Handling. It is very important that the Journal Conversion Rule Post Journals Automatically from Source Ledger is set to No !
31
Note that for the Accounting Options, Use Primary Ledger Amounts correctly defaults to No and it also cannot be updated anymore:
And again we are setting up an Intracompany Balancing rule:
Now that we are done with our Secondary Ledger setup, we can set up our tax book in Assets and link it to our new Secondary Ledger. We set up our book normally and link it to the Primary Ledger.
32
Once the Book is saved, the Ledgers tab appears and we can link the book to the Secondary Ledger:
33
We pick our Secondary Ledger and check Allow GL Posting and Enabled. Note: we can only chose 1 Secondary ledger and we cannot update it once saved! Also, once unchecking Allow GL Posting and/or Enabled, this also cannot be changed anymore! We now continue with the normal setup including Asset Categories. Once we have copied assets into the book and are ready to run Create Accounting we again have to make sure that we pick the Secondary Ledger for parameter Ledger ID as the Primary Ledger defaults:
And here is again the Create Accounting output for the same adjustment as we have seen previously for the Primary and also the other Secondary Ledgers:
34
A Technical Perspective
Behind the scenes the scenario is as follows:
Case 1: Same Currency, Different CoA than in Primary

A row will be inserted into table FA_BOOK_CONTROLS with the Secondary Ledger ID.
Case 2: Different Currency, Same CoA as in Primary

A row will be inserted into table FA_BOOK_CONTROLS with the Primary Ledger ID.
A row will be inserted into table FA_MC_BOOK_CONTROLS with the Secondary Ledger ID.
35
Case 3: Different Currency and different CoA than in Primary

A row will be inserted into table FA_BOOK_CONTROLS with the Primary Ledger ID.
A row will be inserted into table FA_MC_BOOK_CONTROLS with the Secondary Ledger ID.
For the second and third case: as there is a different Accounting currency then in the Primary ledger, the currency conversion takes place as if the Secondary Ledger were actually an Alternate Ledger Currency (ALC) Ledger. This means that addition and cost adjustment transactions get converted with the appropriate rate from GL Daily Rates with the rate type set up for the Secondary Ledger. Other transactions and depreciation use the weighted average that gets inserted into table FA_MC_BOOKS_RATES.
The Asset SLA trace has been modified to handle events for the Secondary Ledger. For the first case, one will not notice any difference, except that the ledger_id is that of the Secondary Ledger:
36
For the second and third case: Upon successful transaction/depreciation, one event is created for the Primary Ledger and another event gets created for the Secondary Ledger. As Create Accounting is to be run only for the Secondary Ledger, the events created for the Primary Ledger will always remain Unprocessed(!)
On Depreciation Rollback, the event will get deleted if the status is Unprocessed and a reversal event will get created if the event is processed. If event is processed in the Secondary Ledger and Unprocessed in the Primary Ledger then on rollback, the event will be deleted for the Primary Ledger and a reversal event will get created for the Secondary Ledger.
37
Troubleshooting
A few cases to help with troubleshooting potential issues have been put together here.
Missing exchange rate

After completing the setup for the required tax book(s), Initial Mass Copy is run. It fails with the following messages in the Log and the output file: Initial Mass Copy Execution Report Book: HIRTAX USD COA2 Request ID: 6007183
Asset number HIRAT1 Transaction header id 364300 Mass Copy failed on this asset and transaction. Please review log file for more information. Asset number HIRAT2 Transaction header id 364302 Mass Copy failed on this asset and transaction. Please review log file for more information. Etc. Periodic Mass Copy may fail as well with the same message. Attempting to add an asset manually to the tax book fails with: APP-OFA-48392 Unknown Serverside Error. When a DB or Forms trace with Binds is run, the output will display this query: SELECT CONVERSION_RATE FROM GL_DAILY_RATES WHERE FROM_CURRENCY = :B4 AND TO_CURRENCY = :B3 AND CONVERSION_DATE = TRUNC(:B2 ) AND CONVERSION_TYPE = :B1 END OF STMT BINDS #65: Bind#0 oacdty=01 mxl=32(15) mxlc=00 mal=00 scl=00 pre=00 oacflg=13 fl2=206001 frm=01 csi=873 siz=32 off=0 kxsbbbfp=2b20970b5a08 bln=32 avl=03 flg=09 value="EUR" Bind#1 oacdty=01 mxl=32(15) mxlc=00 mal=00 scl=00 pre=00 oacflg=13 fl2=206001 frm=01 csi=873 siz=32 off=0 kxsbbbfp=2b20970b5a40 bln=32 avl=03 flg=09 value="USD" Bind#2 oacdty=12 mxl=07(07) mxlc=00 mal=00 scl=00 pre=00 oacflg=13 fl2=206001 frm=00 csi=00 siz=8 off=0 kxsbbbfp=2b20970b5ab0 bln=07 avl=07 flg=09 value="1/1/2005 0:0:0"
38
Bind#3 oacdty=01 mxl=32(30) mxlc=00 mal=00 scl=00 pre=00 oacflg=03 fl2=1206001 frm=01 csi=873 siz=32 off=0 kxsbbbfp=2b209702de30 bln=32 avl=11 flg=05 value="Period End1" This indicates that no exchange rate for EUR to USD exists on 01-JAN-2005 for rate type Period End1. The conversion rate was entered for 31-JAN-2005 and not the first of the month for rate type Period End1. This Error Handling for the has been set up for the Secondary Ledgers with a different currency under Subledgers: Missing Conversion Rate Report Error: Use Last Rate * Number of Days to Find the Last Rate: 31 However, since this was the first period and the Period End rate was set up for the 31st, there is nothing to fall back on. This is why even for a rate type Period End, an exchange rate must exist for Dates Placed In Service (DPIS) for the assets to be copied to the tax book(s). After all the necessary rates are set up Mass Copy will complete successfully.
Create Accounting run for the Primary instead of the Secondary Ledger
For case 2 and 3 Create Accounting may fail with the following message: Message Number 95937 Message There are either non-accountable events existing in the system, or events which could not be processed because no data could be found on transaction objects. Please enable the profile option SLA: Enable Diagnostics, create accounting again, and run the report Transaction Objects Diagnostics to identify the problem. If one encounters this error message, then one should check the parameters with which Create Accounting was run. It is very likely that it was run for the Primary Ledger and not the Secondary Ledger. For case 1 this would not be an issue as the Secondary Ledger defaults for parameter Ledger ID when the case 1 tax book is chosen.
39
Create Accounting fails for the tax book using a different CoA
For case 1 and 3 the Create Accounting output may display the following errors and the Account fields are empty:
The error message at the bottom indicates that there is an issue with a specific Code Combination ID. Running the following query will display: select code_combination_id, segment1||'.'||segment2||'.'||segment3||'.' ||segment4 from gl_code_combinations where code_combination_id in (447067) ;
This is the default code combination set up in the Book Controls form for the tax book. Checking the CoA Mapping one may notice that the account 9999 from the source ledger is not mapped to the target ledger account. Correcting this oversight and rerunning Create Accounting will let the program complete successfully:
To avoid issues with the CoA Mapping it is best practise to map all account and not only those used for Assets.
40
Create Accounting fails without any error message and the output is empty
To diagnose this problem perform the following steps: 1. Please set the following profile options at user level: FND: Debug Log Enabled Yes FND: Debug Log Module - % FND: Debug Log Level - Statement 2. Then please rerun Create Accounting in Draft mode with "Errors Only" parameter at Yes. 3. Please run the following query with the request ID of the Accounting Program request: spool errmsgnic1 set pagesize 0 set linesize 300 SELECT MESSAGE_TEXT, substr(module,1,70) FROM fnd_log_messages msg, fnd_log_transaction_context tcon WHERE msg.TRANSACTION_CONTEXT_ID = tcon.TRANSACTION_CONTEXT_ID AND tcon.TrANSACTION_ID = <Accounting Program request ID> ORDER BY LOG_SEQUENCE ; spool off Or run the query in the Oracle SQL Developer or Toad. The output may look similar to this: BEGIN of BuildCcids xla.plsql.xla_ae_code_combination_pkg.BuildCcids BEGIN of map_transaction_accounts xla.plsql.xla_ae_code_combination_pkg.map_transaction_accounts coa_sla_mapping_name = HIR Primary to Secondary EUR, coa_sla_mapping_id = 1121 xla.plsql.xla_ae_code_combination_pkg.map_transaction_accounts BEGIN of map_ccid xla.plsql.xla_ae_code_combination_pkg.map_ccid # rows inserted into gl_accts_map_int_gt(ccid) = 9 xla.plsql.xla_ae_code_combination_pkg.map_ccid -> CALL gl_accounts_map_grp API xla.plsql.xla_ae_code_combination_pkg.map_ccid Error. = User-Defined Exception xla.plsql.xla_ae_code_combination_pkg.map_ccid -: XLA-95103: An internal error occurred. Please inform your system administrator or support representative that:
41
An internal error has occurred in the program xla_ae_code_combination_pkg.map_ccid. User-Defined Exception. fnd.plsql.APP_EXCEPTION.RAISE_EXCEPTION.dict_auto_log This indicates that there is an issue with the CoA mapping between the Secondary and the Primary Ledger. The CoA mapping needs to be checked. In the case above, the CoA of the Secondary Ledger has a segment which does not exist in the Primary Ledger. This segment was mapped wrongly. The CoA Mapping was changed to Action Assign Single Value for the segment and a default value was given. After that Create Accounting completed successfully and produced the expected output.
Performing an Inter- or IntraCompany transaction, the InterCompany Receivable and Intercompany Payables Accounts are missing in the journal
When performing an Inter- or IntraCompany transaction, the InterCompany Receivable and Intercompany Payables Accounts are missing in the journal. The Create Accounting output displays this error:
The individual segment values as well as the complete code combinations used for the Inter- or IntraCompany Balancing Rules in the both the Primary and the Secondary Ledger exist and are active and allowed. The FND Logging output displays well how the Cost and Reserve accounts are created but for the InterCompany Accounts the following is found in the log: BEGIN of procedure STACK_ERROR p_appli_s_name = XLA p_msg_name = XLA_INTRA_CC_NOT_ACTIVE p_entity_id = 3672308 p_event_id = 3742769 p_ledger_id = 1621 p_ae_header_id = 5200014 p_ae_line_num = p_accounting_batch_id = l_msg_number = 0 END of procedure STACK_ERROR END of procedure BUILD_MESSAGE END LOOP - fun_bal_errors_gt End of procedure create_intercompany_errors
42
Check the accounts again, especially the attribute values for the two accounts. Make sure they are not parent accounts and that posting is allowed. Verify that the Inter- IntraCompany Receivables and Payables accounts are also mapped to the Primary Ledger Accounts. Then submit Create Accounting again.
43

FA 2nd Ledger ER1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FA 2nd Ledger ER1

Uploaded by

Copyright:

Available Formats

ORACLE APPLICATIONS

White Paper Secondary Ledger Enhancement for Oracle Assets - Setup

What is the new Secondary ledger enhancement for Assets?

N/A Same as Corp Same As Corp Different Same as Corp Different

N/A Same as Corp Same as Corp Same as Corp Different Different

- Currently allowed Configurations - Additional allowed Configurations after the Enhancement

Definitions Chart of Accounts (CoA)

Valuation Method (VM)

And this Intracompany Balancing rule:

Secondary Ledger Enhancement - Setup

Case 1: Same Currency, Different CoA than in Primary

Case 2: Different Currency, Same CoA as in Primary

With these Currency Conversion options and Journal Conversion Rules:

And again we have set up Intracompany Balancing Rules:

Case 3: Different Currency and different CoA than in Primary

And again we are setting up an Intracompany Balancing rule:

Behind the scenes the scenario is as follows:

Case 1: Same Currency, Different CoA than in Primary

Case 2: Different Currency, Same CoA as in Primary

Case 3: Different Currency and different CoA than in Primary

Missing exchange rate

You might also like