1.Can I use Rapid Implementation to add new values at a later point?
Rapid Implementation is
meant for one-time quick setup. We do not support updates from Rapid
Implementation. Hence you need to manually add values.
2.Can I change accounting calendar period frequency or adjusting
frequency on re-upload?
No. Once created the
calendar definition cannot be changed.
3.Can re-upload delete values in the system if I remove values
or LE(s) or BU(s) in the spreadsheet?
No. Once uploaded you
need to navigate to the respective setup UI using FSM task to either delete or
inactive or end-date the respective entity.
4.Do I need to deploy chart of accounts when new values are
manually added?
No.
5.How do I know the names of the entities created?
ESS request output file
contains the names of the entities.
6.How are names derived for the setup entities except Legal
Entity and Business Unit?
All the names for
value set, chart of accounts, accounting calendar, ledger and implicit DAS are
derived from the "Name" attribute provided in the spreadsheet.
Value Set, Tree Code:
"<Segment> <Name>"
Chart of Accounts,
Accounting Calendar (first 15 chars limit): "<Name>"
Ledger, Implicit DAS:
"<Name> <CountryCode>" |
7.What is the primary ledger and default legal entity for each
business unit?
The primary ledger and
the first legal entity are assigned to the BU belonging to the same country.
These can be changed at a later point from "Assign Business Unit Business
Function" task.
8.Can I change the Ledger's calendar, chart of accounts,
existing Ledger-LE assignments (or) LE-BSV assignments on re-upload?
No.You cannot change
ledger's calendar, chart of accounts and existing assignments but can add new
assignments.
9.Can I upload Financial Common entities without providing BU(s)
or LE(s) or both?
Yes.You can upload
without BU(s) or LE(s) or both but the primary ledger may be functionally
incomplete.
10.Is the same value set used for both Primary Balancing Segment
(PBS) and Intercompany segment?
Yes.The same value set
is used for Primary Balancing Segment and Intercompany segment. You may specify
security rules to ensure that specific segment values are never charged for
Primary Balancing Segment.
11.The user does not want to use the same value set for both
Primary Balancing Segment (PBS) and Intercompany segment since user does not
want to specify additional security rules. How do I proceed?
You can still use Rapid
Implementation to create the segments with the same value set and proceed to
perform the below steps
manually before proceeding with deploying chart of accounts and Financial
Common Entities upload.
Create the value set
and values for Intercompany segment
Create the tree
(versions base and current) for Intercompany segment (refer to already created
PBS tree)
Run audit, row and
column flattening
Ensure to associate
correctly tree to Intercompany segment
12.Does RI support creating statistical accounts?
No. RI does not support
creating statistical accounts. Use "Manage Statistical Unit of
Measure" task in FSM to create statistical accounts manually.
13.Does RI create secondary ledgers, ALC and reporting
currencies?
No. RI only creates
primary ledgers.
14.Why are two versions "%Base" and
"%Current" created for each hierarchy (tree)?
Two versions are created
due to essbase restrictions. These restrictions will be addressed in following
bugs:
Bug 17578078 -
allocations: fusion: allocation needs to support memberid for nonunique
outlines.
Bug 14835002 - smart
view : fusion: smart view to support member id field from Essbase cube.
15.What are the size limits for names of various objects?
The combination of Name
and Segment(name) provided in 'COA, Calendar and Ledger' sheet should not
exceed 30 characters.
The length of the parent
or child values in each of the sheets , cannot exceed the 'display width'
provided for the segment corresponding that sheet in 'COA, Calendar and Ledger'
worksheet.
Do not use spaces in the
beginning or at the end since Essbase does not allow member names to start/end
with spaces.
Do not use special
characters- Essbase does not support special characters.
16.Is Primary Balancing Segment must be the first segment?
The first segment should
be the Primary Balancing Segment and the Primary Balancing Segment comes before
the Natural Account Segment.
17.The GL Rapid implementation spreadsheet is not accepting the
word "FUNCTION" as a segment name. What are the restricted reserved
keywords?
The list of reserved
words can be found in the Manual Implementing Enterprise Structures and General
Ledger,
Chapter 6 Financial
Structures found here: http://docs.oracle.com/cd/E51367_01/financialsop_gs/FAI
GL/F1489230AN193E8.htm#F47477AN1ACD9
Go to Section Planning
Key Flexfields: Points to Consider - Essbase Character and Word Limitations -
Other Restrictions
Refer to this following
note as well:
What Are Essbase
Restricted Characters/Keywords Within COA Segment/Values and What Will Be
Impacted Areas? Doc ID 1666824.1
18.How to create multiple ledgers using Rapid implementation
file for General ledger which share the same chart of accounts
A primary ledger is
created for each unique country chosen in the Companies and Legal Entities
sheet. For example, if one of the legal entities is based in the United States
and another in Canada, and the ledger name entered by the user is InFusion
Ledger, then two primary ledgers, InFusion Ledger US and InFusion Ledger CA,
are created. The country code is appended as above, to the primary ledger name
provided by the user for cases where multiple countries are involved.
All the primary ledgers
created use the same chart of accounts, account hierarchies, and accounting
calendar as defined in the Rapid Implementation spreadsheet. The ledger
currency defaults based on the country of the legal entity or entities
associated with the ledger.
If only one country
exists among legal entities on the Companies and Legal Entities sheet or no
legal entities are entered, then only one primary ledger is created based on
user inputs.
19.How can we use a different segment separator (eg:
".") instead of default "-".
In all releases, RI uses
the hyphen as segment separator.
In the RI spreadsheet
for R7 and R8, you need to always use hyphen for retained earnings account (R9
onwards, the retained earnings account gets defaulted automatically without user
input).
To resolve this issue,
after the upload of ChartOfAccounts and before proceeding with deploying COA,
please go the "Manage Chart Of Accounts Structures" task and modify
the segment separator from "-" to whatever you wish to manually and
proceed to deploy the COA. After successful deploy of COA, please proceed to
upload FinancialCommonEntities file.
20.Value Set is created with the name as <Segment>
<Ledger Name>. Is there a way to change this or to specify the value set
name that we would like to see since the Chart of Accounts will be used by
multiple ledgers?
No. This cannot be
changed by the customer. Both value sets and tree code are generated with name
as "<Segment> <Ledger Name>".
21.Is there a way to add values to the Chart of Account segments
without specifying parents?
No
22.The user wishes to create multiple LEs for one country but
wants each LE to be associated to a separate ledger using RI.
This is not supported by
RI solution. If they provide all LEs for a country in Rapid Implementation
spreadsheet then all LEs will be created and associated to one single ledger
that is created for the country. An important point here is that customer will
not be able to use the Ledger or LE(s) to suit his requirement as once LE is
associated to a Ledger it cannot be associated to another Ledger.
Hence advise the user to
create LEs and Ledger manually as per their requirement which is currently not
supported by Rapid Implementation.
23.The user wishes to use an existing calendar and does not want
Rapid Implementation to create the same.
User needs to rename the
calendar exactly to match the Ledger name provided in the Rapid Implementation
spreadsheet. The upload of FinancialCommonEntities.zip will skip calendar if
calendar with the same name exists in the system.
24.How does RI handle upload of existing values?
Update of Existing
Values
Only Description is
updated
No updates are allowed
to summaryFlag, accountType, financialCategory, thirdPartyControlAccount,
reconcile in both RI and Coex flows. Any changes should be done manually from
FSM/Applcore tasks. (The upload process verifies summaryFlag and accountType
for changes wrt DB. If there are any changes the values are skipped skip
changes for the value in both RI and Coex flows. )
Known Issues and
Workarounds
1.User getting "Compile error: Can't find project or
library" upon pressing "Validate data" button.
This is a problem with
your MS Excel setup. Please go to Design mode or press ALT+F11 to switch to the
Visual Basic Editor, then Tools -> References and clear the check box for
the type library or object library marked as "MISSING:".
2.Getting "Enter date in 'MM/DD/YYYY' format only"
validation error , even after formatting the date cell to be MM/DD/YYYY type
and entering the date in MM/DD/YYYY format
Follow the below
solution :
1. Close all Office
applications.
2. Open Control
Panel>Clock, Language, and Region>Region and Language>Change the
date,time, or number format.
3. Under Formats, use
the drop down to select "English (United States)".
4. Then close and open
Excel.
3.Run-time error '13: Type mismatch
A value of '#N/A' was
used - expected values are alphanumeric - simply double click the cell or
manually change the format of cells to text.
4.In Release 8 when we click on Add Segments button in the spreadsheet,
it does not add segment sheets to fill data for segments.
This issue is fixed in
R9. Not backported to R7/R8 since RI is one-time usage and issue happens only
in specific releases of MS excel.
Note: Workaround that
we'd suggested was to click on 'Generate Additional Hierarchy' button in one of
the segment pages and then rename the generated worksheet to match the segment
name.
5.Unable to update Retained Earnings on the ledger Options UI
Make sure that
"GL#" is deployed. Navigation: "Manage Chart of Accounts
Structure Instances" task (Search for "Key Flexfield Code" as
"GL#" and click on "Deploy Flexfield" button).
Note: This manual
deployment step is needed until Rel 9. From R10 we have the automatic flex
deployment happening as part of "ChartOfAccounts.zip" upload.
6.From FSM, unable to upload ChartOfAccounts.zip. On clicking
submit, the browsed file disappears and nothing happens.
Known issue from R9
onwards.Internal bug 19901522. Resolved in tech stack bug 19477200 - file
upload broken in remote regions recently
Workaround: Navigate to
Scheduled Processes and select the "Upload Enterprise Structures and
Hierarchies".
1. Login to ATK Homepage
and navigate to "Scheduled Processes"
2. Schedule new Process:
"Upload Enterprise Structures and Hierarchies"
3. Choose the
"Upload Enterprise Structure" option and upload your
"ChartOfAccounts.zip"
4. Monitor request for
success and repeat 2,3 for "FinancialCommonEntities.zip"
7.RI upload using non-MM/DD/YYYY generates incorrect Calendar
Start Date.
An issue is discovered
in Releases 9/10 with Rapid Implementation pertaining to the incorrect
generation of Calendar Start Date in zip files (ChartOfAccounts.zip and
FinancialCommonEntities.zip).This can result in calendar getting generated with
an incorrect start date.
Who will encounter this
issue? Those who satisfy both conditions below:
All users who do not
have the short date format in their OS Region and Language settings as
"MM/dd/yyyy" or "M/d/yyyy"
All users for whom the
DD and MM values are different (e.g. Jan 1st and Apr 4th are ok) Workaround
(can only be used prior to upload)
Start button Picture
of the Start button > Control Panel > Region and Language
Change the Format to
English (United States). Verify that the short date format is
"MM/dd/yyyy" or "M/d/yyyy" Resolution:
This issue is fixed in
Rel 11, and is being backported through R9.2 bug 20789120, R10 bug 20789116.
8.Unable to insert/delete rows in 'Companies and Legal Entities'
Spreadsheet.(getting some warning pop up stating cells are locked and Sheet
needs to be unprotected.)
Go to Review tab (on top
of the worksheet) , and then click on unprotect.
Background:
Automatically disabling the LE details field in the case on non-child (or
parent) values feature works only when the sheet is protected, hence the
implementation.
9.Create Hierarchies failed with Hierarchies creation failed
java.lang.NullPointerException
Review the exception
details as given below. java.lang.NullPointerException Exception Message:
Hierarchies creation failed java.lang.NullPointerException
Check and remove any
special characters like '.' and '&' that may be present in values provided
for any of the segment sheet.
10.When trying to "Upload Hierarchy" > "Create
New Hierarchy", the value set does not show up for "Value Set"
LOV.
Reason: Value set is
created with some other module other than "General Ledger". This
value set is not created using the RI process as RI always registers the value
set for "General Ledger" module.
Fix: For the value set
to appear in the LOV, please edit the Value Set and change the module to
"General Ledger"
14.How does RI handle upload of existing values?
Update of Existing
Values Only Description is updated No updates are allowed to summaryFlag,
accountType, financialCategory, thirdPartyControlAccount, reconcile in both RI
and Coex flows. Any changes should be done manually from FSM/Applcore tasks.
(The upload process verifies summaryFlag and accountType for changes wrt DB. If
there are any changes the values are skipped skip changes for the value in both
RI and CoexThis can happen when the BUs are already existing in the system and
created prior to RI upload using the "Manage Business Unit" task from
FSM (ie, UI). In this case, the user should remove the BUs from the spreadsheet
and proceed flows. )
15.During FinancialCommonEntities.zip upload, RI process fails
to upload Business Units
This can happen when the
BUs are already existing in the system and created prior to RI upload using the
"Manage Business Unit" task from FSM (ie, UI). In this case, user
should remove the BUs from spreadsheet and proceed
16.During FinancialCommonEntities.zip upload, RI process created
duplicate Legal Entities
For Legal Entities,
LegalEntityIdentifer is the alternate key and not the Legal Entity Name. To
ensure duplicates are not created, please use the same LegalEntityIdentifier.
Ideally, data user is
trying to upload should not exist in the system since can conflict with data
being uploaded.
17.After RI upload, the user finds the account values got
created with the wrong account types and there exist code combinations that
need to be corrected
This can only happen
when the user removed the LOVs for Account type in "Natural Account"
sheet of RI spreadsheet and typed the value incorrectly. RI picks the last
account type (Expense) as it was not able to find the correct value and there
was no validation as LOVs are used for the same.This is a user mistake to
remove LOVs and type incorrect account type and the user can correct the values
from Applcore UIs but if incorrect code combinations due to this issue exist a
data fix may not be supported.
Additional validations
to handle this is added in ER bug 23066412
18. The user wishes to upload non-English data using RI
spreadsheet. While uploading RI process fails to upload in the non-English
language.
This is an expected
behavior and not a bug.
Rapid Implementation
spreadsheet does not support NLS (means shows information only in English and
has seeded information in English like Segment Label in COA, Calendar, and
Ledger, the country in Companies and Legal Entities, Account type in Natural
Accounts etc). The spreadsheet will accept data entered in other language and
the generated zip files should only be uploaded using the English session.
Reference bug 21408690
You can upload values
and their descriptions in multiple languages using "Segment Values and
Hierarchies Import" feature/spreadsheet.
19.User finds incorrect ledger currency assigned to the primary
ledger.
The Rapid Implementation
worksheet upload process uses the country of the legal entity assigned to the
ledger is to derive the ledger currency. If no legal entities are entered, then
the currency field becomes mandatory else it is an optional field.
Reason: If the user has
provided LEs, the currency will be picked up automatically from
FND_TERRITORIES_VL and FND_CURRENCIES_VL, based on the country of the LE.
These data delivered via
TerritorySD.xml and CurrencySD.xml needs to be correct. In case the definition
is incorrect, please can log an Applcore bug (e.g. bug 19451752) to get this
corrected. How to resolve the issue?
The customer should
discard the ledger with incorrect ledger currency and create a new ledger with
the right currency. A data fix is complicated as it involves ledger tables and
Essbase cubes and hence not recommended.
20.Upload fails to process Primary Ledgers with
belowerror:LedgerRelationshipEOJBO-27040: Value "Ledger Name greater than
17" for field TargetLedgerShortName exceeds the maximum length allowed
Use should use ledger
name that is less than 17 chars (we append space + country code making it max
20 chars
which is width of
TargetLedgerShortName in LedgerRelationship). For TEST env,customer should
discard previous upload and re-upload using the restriction above . Not
recommended to use RI directly in PROD
21.HierarchiesOnly.zip upload does not flatten hierarchy on
modifying existing hierarchy
Issue: Upload Hierarchy
> Modify Existing Hierachy option does not flatten the hierarchy.
Resolution/Workaround: To resolve the issue you can run force flattening (in Manage Trees and Tree Versions UI) or run use "Financials Tree Audit and Tree Flatten Process" ESS job from Navigator > Scheduled Process.
No comments:
Post a Comment