General Ledger - Oracle EBS R12: February 2016

Friday 12 February 2016

How To Enable Management Segment Qualifier on a Running Instance - Oracle EBS R12

https://generalledger-gl.blogspot.com/2016/02/httpgeneralledger-gl.html

I have a question regarding qualifier.Can I Enable Management Segment qualifier in location on running instance?

Solution

This is allowed, please check note How To Enable Management Segment and What Is It's Use? ( Doc ID 558612.1 )

But you need to be aware of the following:

In case Management qualifier is being assigned to an existing Ledger, DO NOT enable it in Chart of Accounts form. Instead run the following two concurrent request in the specified order:
1. Program - Prepare Journal Batches for Management Segment Upgrade
2. Program - Complete Management Segment Upgrade

Once the above two requests complete successfully, the desired segment will automatically be enabled as Management Segment.

-----------------------------------------------------------------------------------------------------------

Request Program - Prepare Journal Batches for Management Segment Upgrade

Error No entries found in the list of values

received in the parameter Chart of accounts

-----------------------------------------------------------------------------------------------------------

The LOV could be empty because of two reasons:

1. Management Qualifier is already assigned to one of the Segments of the Chart of Accounts

2. The issue is caused by the fact that , instead of running the requests, Management Qualifier was enabled directly from the Chart of Accounts definition form. Later on it was removed

Please check and let me know if any of the above is true.

Can we enable "Security Enabled" check box on running Instance - Oracle EBS R12

https://generalledger-gl.blogspot.com/2016/02/enabling-security-enabled-check-box-in.html

Our Financial System has been Implemented since 2009.
Now our requirement is to apply security rules on Location segment.
Our Location segment is using security type as "Non-Hierarchical Security".
But the Issue is we have not checked the "Security enabled" check box at the time of implementation.
We need your help regarding this, If we will check the security Enabled check Box Now.
Is there any issue? Please recommend your suggestion in this regard.
--------------------------------------------------------------------------------------------------------

Q.Does Oracle Support or you suggest the updation of security enabled check box in the running FINANCIAL SYSTEM?because we have to unfreeze key flexfields and after enabling we have to compile key flexfields again.

----------------------------------------------------------------------------------------------------------

Solution

Security can be enabled or disabled at anytime. This is allowed and supported.

Please check note: What Are The Permitted Changes In A Chart Of Accounts ( Doc ID 984572.1 ).

Having security enabled will allow you to use security rules.

Unfreeze , freeze and recompile of the accounting flexfield are steps that need to be done whenever this kind of change is done,

It does not have any negative impact, the change is allowed only when unfreeze is done , while recompiling is done automatically when the change is saved , in order to ensure the change is propagated to entire chart of accounts structure.

In conclusion, security enabled check box can be updated in a running financial system.

Thursday 11 February 2016

Negative Ledger ID Scripts - Oracle EBS R12

http://generalledger-gl.blogspot.com/2016/02/negative-ledger-id-scripts.html

Negative Ledger ID Scripts

Please Download it from the Below URL

https://drive.google.com/open?id=0B30-kT1pIOm_UUFIekgxZWJWdnc

------------------------------------------------------------------------------------------------------------------------

SQL> !ls

1- Negative_ledger_id_dfix.txt

2- IN_SLA_NOT_IN_GL_dfix.txt

SQL> @Negative_ledger_id_dfix.txt ----- Bug_number 16765725

PROVIDE FILE NAME

<br>

Enter value for p_file_name:

Journal Import Error Codes - Oracle EBS R12

http://generalledger-gl.blogspot.com/2016/02/period-error-codes-ep01-date-is-not-in.html

Journal Import Error Codes

Period Error Codes
------------------
EP01 This date is not in any open or future enterable period.
EP03 This date is not within any period in an open encumbrance year.
EP04 This date is not a business day.
EP05 There are no business days in this period.

Unbalanced Journal Error Codes
------------------------------
WU01 Warning: This journal entry is unbalanced. It is accepted because suspense posting is allowed in this ledger.
EU02 This journal entry is unbalanced and suspense posting is not allowed in this ledger.
EU03 This encumbrance journal entry is unbalanced and the Reserve for Encumbrance account is not defined.

Flexfield Error Codes
---------------------
EF01 This Accounting Flexfield is inactive for this accounting date.
EF02 Detail posting not allowed for this Accounting Flexfield.
EF03 Disabled Accounting Flexfield.
EF04 This is an invalid Accounting Flexfield. Check your cross-validation rules and segment values.

Flexfield Error Codes
---------------------
EF05 There is no Accounting Flexfield with this Code Combination ID.
EF06 The alternate account is invalid.
WF01 An alternate account was used instead of the original account.
WF02 A suspense account was used instead of the original account.

Foreign Currency Error Codes
----------------------------
EC01 A conversion rate must be entered when using the User conversion rate type.
EC02 There is no conversion date supplied.
EC03 A conversion rate type or an accounted amount must be supplied when entering foreign currency journal lines.
EC06 There is no conversion rate for this currency, conversion type, and conversion date.
EC08 Invalid currency code.
EC09 No currencies are enabled.
EC10 Encumbrance journals cannot be created in a foreign currency.
EC11 Invalid conversion rate type.
EC12 The entered amount must equal the accounted amount in a ledger or STAT currency journal line.
EC13 Amount is too large.
ECW1 Warning: Converted amounts could not be validated because the conversion rate type is not specified.

Budget Error Codes
------------------
EB01 A budget version is required for budget lines.
EB02 Journals cannot be created for a frozen budget.
EB03 The budget year is not open.
EB04 This budget does not exist for this ledger.
EB05 The encumbrance_type_id column must be null for budget journals.
EB06 A period name is required for budget journals.
EB07 This period name is not valid. Check calendar for valid periods.
EB08 Average journals cannot be created for budgets.
EB09 Originating company information cannot be specified for budgets.

Encumbrance Error Codes
-----------------------
EE01 An encumbrance type is required for encumbrance lines.
EE02 Invalid or disabled encumbrance type.
EE03 Encumbrance journals cannot be created in the STAT currency.
EE04 The BUDGET_VERSION_ID column must be null for encumbrance lines.
EE05 Average journals cannot be created for encumbrances.
EE06 Originating company information cannot be specified for encumbrances.

Reversal Error Codes
--------------------
ER01 A reversal period name must be provided.
ER02 This reversal period name is invalid. Check your calendar for valid periods.
ER03 A reversal date must be provided
ER04 This reversal date is not in a valid period.
ER05 This reversal date is not in your database date format.
ER06 Your reversal date must be the same as or after your effective date.
ER07 This reversal date is not a business day.
ER08 There are no business days in your reversal period.

Reversal Error Codes
--------------------
ER09 Default reversal information could not be determined.

Descriptive Flexfield Error Codes
---------------------------------
ED01 The context and attribute values do not form a valid descriptive flexfield for Journals - Journal Entry Lines.
ED02 The context and attribute values do not form a valid descriptive flexfield for Journals - Captured Information.
ED03 The context and attribute values do not form a valid descriptive flexfield for Value Added Tax.

Miscellaneous Error Codes
-------------------------
EM01 Invalid journal entry category.
EM02 There are no journal entry categories defined.
EM04 The value in the ACTUAL_FLAG must be "A" (actuals), "B" (budgets), or "E" (encumbrances).
EM05 The encumbrance_type_id column must be null for actual journals.
EM06 The budget_version_id column must be null for actual journals.
EM07 A statistical amount belongs in the entered_dr(cr) column when entering a STAT currency journal line.
EM09 There is no Transaction Code defined.
EM10 Invalid Transaction Code.
EM12 An Oracle error occurred when generating sequential numbering.
EM13 The assigned sequence is inactive.
EM14 There is a sequential numbering setup error resulting from a missing grant or synonym.
EM17 Sequential numbering is always used and there is no assignment for this ledger and journal entry category.
EM18 Manual document sequences cannot be used with Journal Import.
EM19 Value Added Tax data is only valid in conjunction with actual journals.
EM24 Average journals can only be imported into consolidation ledgers.
EM25 Invalid average journal flag. Valid values are "Y", "N", and null.
EM26 Invalid originating company.
EM27 Originating company information can only be specified when intercompany balancing is enabled.
EM29 You do not have access to this ledger and account combination.
EM30 This balancing segment value is not valid for this ledger.
EM31 This management segment value is not valid for this ledger

** Batches listed under "Unbalanced Batches**" have not been imported.

Tuesday 9 February 2016

Consolidation Setup General Ledger - Oracle EBS R12

http://generalledger-gl.blogspot.com/2016/02/consolidation-setup-general-ledger.html

Consolidation Setup General Ledger

Please Download the file from the below URL

https://drive.google.com/open?id=0B30-kT1pIOm_VUt1UTMyN1o2N3c

Error on WEBADI " "Enter a valid Line Description." - Oracle EBS R12

http://generalledger-gl.blogspot.com/2016/02/error-on-webadi-enter-valid-line.html

Error on WEBADI " "Enter a valid Line Description."

"Enter a valid Line Description."

Error is due to the space in Line Description which is in Count as a Character

Formula to Count Characters of Line Description =LEN( )

Monday 8 February 2016

WEBADI Error "This document has already created - please contact support representative" - Oracle EBS R12

http://generalledger-gl.blogspot.com/2016/02/webadi-error-this-document-has-already.html

After downloading the WebADI.xls template from create document step, the template doesn't open up for uploading the data. Instead it gives the message: "This document has already created - please contact support representative"

### Steps to Reproduce ###

Desktop Integration resp.
Create Document
Integrator = General Ledger - Journals
Excel 2000
Layout Functional Actuals - Single
Saved doc to desktop.

The WebADI.xls opened ok the first attempt but then got the message on additional attempts to open it: 'This document has already been created. Please contact your support representative

------------------------------------------------------------

Solution

This is the expected behavior.
A User can generate the layout / document using WebADI.xls only once for security reasons, although the Book1.xls can be used for multiple uploads.

There are two ways to create a Document/ Excel Spreadsheet. When first Creating the Document there is the option to either:
Open Save Cancel.

If you Open the Document and then save if from Excel, it is generated as a Book1.xls.
If you Save the Document, then it is saved as a WebADI.xls.

The user can use the WebADI.xls only once and then they get the "This document has already created" message.
The user can upload Book1.xls multiple times.