1. A Capital Project must exist. The type associated to this project must have at least:
   - Class = Capital
   - On the Capitalization Information Tab, grouping method must be ‘CIP grouped by client extension’
2. The user that will be updating the install base instances and running concurrent programs should be allowed by Projects Security to update the project. In practice this means that the resource needs to be listed as a key member on the project
3. No project task asset assignment should be created manually yet
   (R) Projects
   (N) Project
   - find the project and open it
   - double click on the task
   - click on Options -> asset assignments
   - there should be no records displayed (yet)
4. The  ‘Asset Key Flexfield’ should be set up without any required segments, otherwise no new assets can be created in step 6 of the flow below.
   (R) System Administrator
   (N) Application / flexfield / key / segments
   - query the Asset Key Flexfield – there should be (at least) one enabled structure (ASSET_KEY_FLEXFIELD)
   - click on the Segments button for that structure
   - for each segment defined, click on the ‘open’ button
   - make sure the ‘Required’ check box is not enabled
5. Items must be set up. For Normal Items:
   - in the Inventory tab, the item must be an inventory item, stockable and transactable
   - in the Service tab, Install Base tracking must be enabled and Asset Tracking must be blank.
   - in the Purchasing tab, the expense account and asset category must be entered
   - in the Costing tab, the costing enabled is enabled, asset value is enabled and COGS account should be entered
   - in the Receiving tab, the receipt routing should be Direct
6. The appropriate periods must be open for the following modules:
   GL – General Ledger
   AP – Accounts Payable
   AR – Accounts Receivable
   PO – Purchasing
   INV – Inventory
   PA – Projects
   Please refer to the documentation for these modules how to open/close periods
7. The Current Period for the Asset Book must be up to date:
   (R) Assets
   (N) Depreciation -> Run Depreciation.
   - Select the Asset Book from the list of values.
   -  The current period for that book is displayed.  If it is prior to
   the start date of the contract, enable the Close Period check box and
   then press the Run button.
   -  Repeat this until the current period is up to date
   -  Repeat this set of steps for the Asset Tax Book.
8. The Descriptive Flexfield for Expenditure Items must be set up as per instructions in the Enterprise Install Base Implementation guide:
   (R) System Administrator
   (N) Application / Flexfield / Descriptive / Segments
   - Query the flexfield with title ‘Expenditure Items’
   - Set up the following segments under the Global Elements structure as these will be used for grouping
   when creating assets:
   Name:  Item Number
   Window Prompt: Item Number
   Column: ATTRIBUTE6
   Valueset: 50 chars
   Displayed: yes
   Enabled: yes

   Name:  Serial Number
   Window Prompt: Serial Number
   Column: ATTRIBUTE7
   Valueset: 50 chars
   Displayed: yes
   Enabled: yes

   Name:  Category
   Window Prompt: Category
   Column: ATTRIBUTE8
   Valueset: 50 chars
   Displayed: yes
   Enabled: yes

   Name:  Location
   Window Prompt: Location
   Column: ATTRIBUTE9
   Valueset: 50 chars
   Displayed: yes
   Enabled: yes

   Name:  Product
   Window Prompt: Product
   Column: ATTRIBUTE10
   Valueset: 50 chars
   Displayed: yes
   Enabled: yes

9. Profile Options to be set:
   - PA: Default Expenditure Organization
   - PA: Licensed to use CRL Projects (Yes)
   - Service: Inventory Validation Organization
   - MO: Operating Unit
   - CSE: FA Book Type Code
10. Two triggers must be enabled: CSE_MASS_ADDITIONS_ARU and CSE_FA_RETIREMENTS_ARI. On the administration server node, as the owner of the application tier file system, run csetrg03.sql as the APPS schema to enable the triggers.
    $ cd $CSE_TOP/patch/115/sql
    $ sqlplus <APPS username>/<APPS password> @csetrg03.sql

Process Flow Steps to Receive Normal item into Project and create Asset.

1. Create a purchase order
   (R) Purchasing
   (N) Purchase Orders / Purchase Orders
   - type = Standard
   - Enter a supplier, supplier site, ship-to, bill-to and buyer in the Header
   - In the lines, type = Goods. Enter the item, quantity, price and need-by date – do not save yet
   - Click on button ‘Shipments’
   - On the More tab, uncheck the ‘Accrue at Receipt’ flag
   - Click on Distributions
   - Destination type = Expense
   - Click on the Projects subtab enter the project, task, expenditure type, organization and date.
   - Save the Purchase order

   Approve the Purchase order by pressing the Approve button. If the user cannot approve the PO, follow the procedures as implemented in the environment to approve a PO.

   Note: in 11.5.10 Accrue on Receipt is supported with patch 4435139 CSI: 11.5.10: Rollup Patch # 3 for Oracle Installed Base and Asset Tracking products

2. Receive the purchase order into the project
   (R) Purchasing
   (N) Receiving / Receipts
   - Choose the inventory organization where the item will be received
   - Minimize the receipt header that pops up
   - On the receipt line, enter quantity (same as on the PO line), type should default to Expense. Enter location too.
   - If the item is serialized, enter serial number(s) through Button ‘Lot – Serial’
   - save

   Depending on the processing mode for PO Receipts, the receiving transaction is saved online or in the background. If necessary, run the Receiving Transaction Processor concurrent program to process it.

   Verification:
   - An Install Base Instance should be created with Accounting Classification = Project and Usage Code = In Process
   - A record should be inserted in table PA_TRANSACTION_INTERFACE_ALL for the received items. If the item is serialized, the serialnumber is in ATTRIBUTE7. The item name is in ATTRIBUTE6

3. Run Projects transaction import
   (R) Projects
   (N) Other / Requests / Run / Single Request
   Run program PRC: Transaction Import with parameter Transaction Source = ‘CSE_PO_RECEIPT’

   Verification:
   - After running the program, the record in PA_TRANSACTION_INTERFACE_ALL should be removed. if not check the log file and output file of the concurrent request for failures.
   - If successful, there should be an expenditure item created against the project (PA_EXPENDITURE_ITEMS_ALL)

4. Install the Item in the Project
   For 11.5.9 and earlier
   (R) Oracle Enterprise Installed Base
   (N) Workforce Management
   - Organization = the inventory organization where the item was received
   - Item Number = the received item
   - Revision / Lot / Serial number: enter if applicable to the item
   - Transaction Date = <sysdate>
   - Transacted By = <pick from the list of values>
   - Transaction Type = Project Item Installed
   - Project Number = project number
   - Task Number = Task number
   - Location = FA location – pick from lov
   - quantity = the received quantity
   - Apply

   For 11.5.10
   (R) Oracle Install Base User
   (N) Oracle Installed Base
   - Query the instance that was created when receiving the PO (Quick Find by Item Instance number)
   - Check the Select check box in front of the Instance in the result table
   - Select Transaction Type = Project Item Installed
   - Press the Go button
   - Enter a Deployment Order name (free text)
   - Enter Transaction Quantity
   - Enter Location (from lov)
   - Press Submit

   Verification:
   - After SFM has processed the message, the accounting class of the item instance should be Inventory; the usage code must be Installed. In 11.5.10, the update does not go through SFM, as the transaction is done in the HTML User Interface, which updates Install Base directly.

5. Send a message to place the item in service
   For 11.5.9 and earlier
   (R) Oracle Enterprise Installed Base
   (N) Workforce Management
   - Organization = the inventory organization where the item was received
   - Item Number = the received item
   - Revision / Lot / Serial number: enter if applicable to the item
   - Transaction Date = <sysdate>
   - Transacted By = <pick from the list of values>
   - Transaction Type = Project Item in Service
   - Project Number = project number
   - Task Number = Task number
   - Location = FA location – pick from lov (same as step #4)
   - quantity = the received quantity
   - Apply

   For 11.5.10
   (R) Oracle Install Base User
   (N) Oracle Installed Base
   - Query the instance that was created when receiving the PO (Quick Find by Item Instance number)
   - Check the Select check box in front of the Instance in the result table
   - Select Transaction Type = Project Item In Service
   - Press the Go button
   - Enter a Deployment Order name (free text)
   - Enter Transaction Quantity
   - Press Submit

   Verification:
   - After SFM has processed the message, the accounting class of the item instance should be Inventory; the usage code must be In Service. In 11.5.10, the update does not go through SFM, as the transaction is done in the HTML User Interface, which updates Install Base directly.
   - 2 records should be inserted in PA_TRANSACTION_INTERFACE_ALL.
   ATTRIBUTE6 = itemname
   ATTRIBUTE7 = serialnumber
   ATTRIBUTE8 = asset category
   ATTRIBUTE9 = FA Location
   ATTRIBUTE10 = product classification

6.  Run concurrent request set: eIB Create Assets for Normal Items
   (R) Oracle Enterprise Install Base
   (N) Request / Run / Request Set
   choose request set eIB Create Assets for Normal Items , which contains:
   - Expenditures with 8,9,10 for Normal Item Report
   - PRC: Transaction Import
   - Asset header for Normal Item Report
   For the parameters, enter the project and/or task details against which the PO receipt was done

   Verification:
   - the output files of the concurrent programs will list the number of successfully processed transactions
   - the Expenditures with 8,9,10 for Normal Item Report does not necessarily need to process any records. Theoretically it is possible to receive against a PO (step 2) and put it in service (steps 4 and 5) without running the PA import (step 4). In that scenario putting the instance in service will NOT populate the PA_TRANSACTION_INTERFACE_ALL records, meaning that some updates are not done to the project. The Expenditures with 8,9,10 for Normal Item Report will take care of the updates that would normally be done when putting the item in service so it can be processed to a project asset assignment.
   - after the transaction import, the records from PA_TRANSACTION_INTERFACE_ALL will be removed and new expenditure items will have been created
   - in the Asset Details of the Project task, the items should be visible as project assets

7.  Run concurrent request: eIB Asset Request Set
   (R) Projects
   (N) Other / Requests / Run /  Request Set
   Run eIB Asset Request Set, which contains:
   PRC: Generate Asset Lines for a Single Project
   PRC: Interface Assets to Oracle Assets

   Verification:
   - the output files of the concurrent programs will list the number of successfully processed transactions
   - a record should be inserted in FA_MASS_ADDITIONS with status POST

8.  Run Post Mass Additions from Fixed Assets.
   (R) Assets
   (N) Mass Additions / Post Mass Additions
   The parameters for this request set is the Asset Book; the same value should be entered as is set in the profile option: CSE: FA Book type code. This is the Asset Book used by Enterprise Install Base.

   Verification:
   After the post mass additions programs, the asset should be visible in the Asset Workbench

What descriptive flexfields are available for a particular table?

Use the following SQL:

select table_usage_code, descriptive_flexfield_code, description
from FND_DF_TABLE_USAGES
where table_name = ‘<TableName>’;

What tables and key flexfields are available for a module?

Use the following SQL:

select k.table_name, k.table_usage_code, k.key_flexfield_code, k.description
from FND_KF_TABLE_USAGES k, fnd_application a
where k.application_id = a.application_id
and a.product_code=’<ProductCode>’

What extensible flexfields are available for a particular module?

Use the following SQL:

select k.table_name, k.table_usage_code, k.descriptive_flexfield_code, k.description
from FND_DF_TABLE_USAGES k, fnd_application a
where k.application_id = a.application_id
and a.product_code=’<ProductCode>’
and table_usage_code like ‘%_EFF’

What descriptive  flexfields are with not deployed status in fusion database ?

Use the following SQL:

select descriptive_flexfield_code, deployment_status, deployment_date, deployment_error_message

from FND_DF_FLEXFIELDS_B

where deployment_status <> ‘DEPLOYED’;

What key flexfields are with not deployed status in the fusion database?

Use the following SQL:

select key_flexfield_code, deployment_status, deployment_date, deployment_error_message

from FND_KF_FLEXFIELDS_B

where deployment_status <> ‘DEPLOYED’;

REQUIREMENTS AND LIMITATIONS DEFINING THE ACCOUNTING FLEXFIELD

   1. What are the requirements and limitations defining the Accounting Flexfield?

The Accounting Flexfield has several special requirements and limitations for its definition.
Follow these recommendations carefully, since an incorrectly defined Accounting Flexfield will adversely affect your chart of accounts and application features and in most cases they cannot be corrected.

Plan your key flexfield structures carefully, including segment information such as segment order and field lengths.
Once you define your key flexfields and enter flexfield values, you cannot change your structures. Attempting to do so may create data inconsistencies that impact the behavior of your application or require a complex conversion program. Changing your existing structures may also adversely affect the behavior of items that reference your present flexfield structure, such as financial statements, recurring journal
entries, allocations, consolidations, cross-validation rules and shorthand aliases

Try to build flexibility for future needs into your account structure during setup:
- you may want to add an extra character to the size of each segment to anticipate future needs.
- You can define additional segments for future use.

The following is not a complete list of restrictions and does not excuse the reading of the General Ledger and Flexfields User Guides:
- It is mandatory to designate one segment as the Natural Account segment and another as the Balancing segment.
- The Accounting Flexfield supports only the Char format type. You should not select the Numbers Only check box for the Accounting Flexfield.
- The Accounting Flexfield requires consecutive segment numbers beginning with 1 (such as 1, 2, 3, …).
- The Accounting Flexfield requires that all segments be Displayed and Required. Hiding segments is not supported.
- You can use dependent account segments when you want a “context-sensitive” segment, but avoid it if possible. Use the Cross Validation Segment Rules instead, as some functions may not work properly with dependent segments (for example the AHE in ADI).

SEGMENTS, VALUES AND VALUE SETS

   1. Can different sets of books share the same value set?

If there is a set of books that uses a particular value set and a new book is created, it can use the existing value set.
When the Account Flexfield Structure is created, simply choose the existing value set from the List of Values.
However,if you use an existing value set, the new structure will also inherit the existing values in the value set. It does not create an empty value set to be populated.

   2. Can the Accounting Flexfield Segment name be changed?

Nothing about a flexfield structure should be changed since this could seriously impact your existing data and cause inconsistencies.
The LOV (list of values) prompt and window prompt that appear on the segment form can be changed so the users can see the segment with a different name.

1. Navigate to Setup: Financial: Flexfield: key: segments
2. Query all
3. Unfreeze your flexfield
4. Open the segment summary screen
5. Choose the segment you wish to change
6. Change the LOV and window Prompts and insert the new name.
7. Save your work
8. Freeze the Flexfield which should launch a concurrent request.
9. Check the log and make sure the compile worked OK.

   3. How to add a new value to an existing segment?

On the Segment Values form, insert a new row with your new value.
Make sure the segment qualifiers are set correctly (Allow Posting and Budgeting).
If this is the natural account segment, specify the Account Type also.

   4. How to delete a segment value?

There is no supported way to delete a segment value. Segment values can only be disabled not deleted.

   5. How to enable an existing Future-Use accounting flexfield segment?

Do the following, on the Key Flexfield Segments form:

1. Unfreeze the accounting flexfield
2. Change the Window Prompt name to a valid name (do NOT change the segment name)
3. Update the Default Type and Default Value (if necessary)
4. Freeze the accounting flexfield and recompile

   6. How to re-enable an account value?

In order to re-enable an account value or remove an end date, do the following:

1. Unfreeze the accounting flexfield structure
2. Re-enable the account value or remove the end date of the segment value.
3. Re-freeze the accounting flexfield structure and recompile.
4. Log out of the applications and log back in.

The account value should now be once more available for use.

   7. Is it possible to change the size of a Value Set used in the Accounting Flexfield?

It is possible to increase the size in some cases.
Once the value set is created, you should avoid changes in the size of a value set used in an accounting flexfield.

You should never change:
- from a larger to a smaller maximum size.
- from a smaller to a larger maximum size if your value set is Right-justify Zero-fill (since 001 is not the same as 0000001 and all of your existing values would become invalid).

You will need to test the results thoroughly. All the account ranges may need to be re-entered everywhere (ranges like 00 to 99 will not include the same as 0000 to 9999).

Examples of areas to test (this is not a complete list):
- Summary templates,
- FSGs
- ADI (if you use it)
- Recurring Journals
- Mass Allocations
- Consolidation

   8. Is there a way to load values for a specific segment outside of the form?

iSetup is the Oracle product that provides supported APIs to load values into Oracle Applications flexfields.

To load code combinations ADI may be used. Uploading zero amount journals will create new code combinations.
In this case Dynamic Insertion should be enabled and all account segment values need to exist before the new account code combinations will be dynamically created.
Enhancement Request 2974057 has been logged to provide an API to load account code combinations.

   9. What is the Segment Value Inheritance?

Segment Value Inheritance automatically propagates attributes of individual segment values to the account code combinations which contain that segment value.
This feature eases chart-of-accounts maintenance by automatically replicating changes in segment value attributes to the accounts containing each segment value.

The segment value attributes which can be propagated to the related account code combinations are:
- enabled/disabled flag,
- effective dates,
- allow posting
- allow budgeting

   10. What is the difference between Hierarchical and Non-hierarchical Security Type?

- Hierarchical Security: This feature combines Flex Value Security and Flex Value Hierarchy.
The end result is ‘a flex value is secured if one of it’s parents is secured’, i.e. if a parent value is excluded then all the children are also excluded.

- With non-hierarchical security, the child values do not inherit the parent security.

   11. Which tables store segment values and descriptions?

The tables are:
- FND_FLEX_VALUES_TL
- FND_FLEX_VALUES.

   12. Why can you update the Segment Values form (FNDFFMSV) when the flexfield structure is frozen?

You do NOT need to Unfreeze Flexfields to amend Segment Qualifiers since FNDFFMSV version 11.5.28.

Due to customer requests, Patch 1081772 introduced this change for FNDFFMSV.fmb 115.28, and it is included in R11i FND patchset C onwards.
This is now standard functionality.
Documentation Bug 1377482 has been raised to reflect this change to functionality, since the 11i Users Guide does not advise of the change.

   13. Why is it possible to post to accounts with disabled segment values?

You must disable the segment value and disable every code combination that uses that segment value.
In version 11 and prior, you had to disable each code combination individually.
However, in 11i, you can disable a range of code combinations using the Segment Value Inheritance program.
See the General Ledger Users Guide, Release 11i for more information on this program.

Note: General Ledger does not distinguish between accounts which have transactions outstanding in order to determine if these accounts can or cannot be disabled.

   14. Why is the Field still protected against update, even after unfreezing the structure?

Most probably one of the flexfields that uses this value set is still frozen.
You can find the other flexfields with the following sql which shows the frozen structures containing the valueset:

SEGMENT QUALIFIERS

   1. Can a flexfield qualifier be changed after it has been created?

No.
Once a segment qualifier has been designated for a specific segment and has been saved, it will permanently have the attributes with that qualifier.

For example, you accidentally designate the cost center segment as the natural account segment. Even though you do not compile this, the system saves the changes. And once it has been saved, it will have all the attributes designated for the natural account qualifier, even after it has been changed back, resaved with the correct qualifier and compiled.

This is the inherent functionality of the software.

Unfortunately, there is no real easy solution for this issue. The only option is to create a new chart of accounts and attach a new set of books.
You may be able to just create a new chart of accounts if you have not created the set of books yet.
See Note:107448.1 for more information.

   2. Does the Accounting Flexfield needs one segment flagged with the Intercompany qualifier?

The intercompany segment is an optional Intercompany feature for the Intercompany Segment Balancing.
It is not required in order to do intercompany balancing.

It is just another way to do the intercompany balancing, instead of using different natural accounts to track intercompany balances, you can use the intercompany segment in the Chart of Accounts to record the same detail.

It is more just a matter of preference of how you want to track the intercompany transactions.

Refer to Note:151130.1 to see additional information regarding How Intercompany Journal Lines are Created in General Ledger 11i.
Also see the Oracle General Ledger Users Guide, Chapter 5: Accounting for Multiple Companies Using a Single Set of Books.

   3. How to correct a misclassified account?

Note:1050920.6 contains detailed steps for correcting Misclassified Account Types. The steps must be followed in the exact order if the misclassified account is to be corrected in its entirety.

   4. What is a Reconciliation qualifier and how is it setup?

This Reconciliation flag is a Globalization feature used primarily by European customers.
When the flag is set to YES, the account is set up to be reconciled.

GL Entry Reconciliation is a set of forms and reports that enable the user to selectively cross-reference transactions in the General Ledger.
Once the balance of a group of transactions is zero, the user can mark them as reconciled. This functionality enables the transactions in any account that should balance to zero (for example, an Intercompany suspense account) to be reconciled.

See Note:1041211.6 for more information.

   5. Why are segment Qualifiers or Rollup Groups for an existing value not updatable?

Because one of the structures using that value set is Frozen.
You need to unfreeze all flexfields that use the value set to be able to update the values.

See Note:1015950.6 for detailed steps and scripts to find the flexfields that use a particular value set.

HIERARCHIES, PARENTS AND ROLLUP GROUPS

   1. Can a parent value be changed to a child value and vice versa?

No. An account should never be changed from a child to a parent or vice versa.
This may cause corruption in the chart of accounts and balances at the table level and is not supported by development.

   2. How to identify overlapping child ranges in a Value Set?

Note:143175.1 explains this issue and a script to identify these overlapping ranges.

These can also be found by the Diagnostics script GL Check Setup, described on Note:205198.1

   3. Should Rollup Groups be frozen?

It is recommended that Rollup Groups be frozen unless they are being modified.
However, if they are not frozen, there should not be any effects on General Ledger reports, functions, or other processes.

   4. Which table stores the parent value and its child ranges?

It is the FND_FLEX_VALUE_NORM_HIERARCHY table

ACCOUNTING FLEXFIELD STRUCTURE

   1. Are there any rules for the Names of the segments?

Yes, the names of the segments must follow the same rules as the SQL column names in a table:

- must be from 1 to 30 bytes long
- must begin with an alphabetic character from your database character set.
- can contain only alphanumeric characters from your database character set and the underscore (_), dollar sign ($), and pound sign (#)
- cannot use the SQL reserved words:
ALL,ALTER,AND,ANY,AS,ASC,
BETWEEN,BY,
CHAR,CHECK,CLUSTER,COMMENT,COMPRESS,CONNECT,CREATE,CURRENT,
DATE,DECIMAL,DEFAULT,DELETE,DESC,DISTINCT,DROP,
ELSE,EXCLUSIVE,EXISTS,
FLOAT,FOR,FROM,GROUP,HAVING,
IMMEDIATE,IN,INDEX,INSERT,INTEGER,INTERSECT,INTO,IS,
LEVEL,LIKE,LOCK,LONG,
MINUS,MLSLABEL,MODE,
NOT,NOWAIT,NULL,NUMBER,
OF,ON,OPTION,OR,ORDER,
PCTFREE,PRIOR,PUBLIC,
RAW,ROW,ROWID,ROWNUM,
SELECT,SET,SHARE,SMALLINT,START,SUCCESSFUL,SYNONYM,SYSDATE,
TABLE,THEN,TO,TRIGGER,
UID,UNION,UNIQUE,UPDATE,USER,
VALIDATE,VALUES,VARCHAR,VARCHAR2,VIEW,
WHENEVER,WHERE,WITH.

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:
- Release 11i page 2-19,
- Release 11, page 2-18 .

If it is absolutely required to have changes on segments then a NEW 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 set of books to the new set of books.
If Oracle Subledgers are used then they must also point to the new 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:
- Release 11i, page 2-19
- Release 11, page 2-18

   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:
- Release 11i, page 2-19,
- Release 11, page 2-18.

   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. 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.

2.  Now add your dependent segment (for example subaccount). You should see the dependent value set in the list of values.

   8. 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.

   9. 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 “?”.

Do not use the segment separator in the description and this should resolve the issue.

DESCRIPTIVE FLEXFIELDS IN GL

   1. How to Add the Account Segment Qualifier Reconciliation Flag

The Reconciliation Flag is a qualifier introduced by the European Localizations.
Please review Note:163966.1 for instructions.

   2. How to Disable Enter Journals:Reconciliation Descriptive Flexfield in Enter Journals?

1. Navigate to Setup>Financial>Flexfield>Segments
2. Query Application: Regional Localizations and Title: Enter Journals:Reconciliation
3. Unfreeze the flexfield
4. Under Context Field, ensure Value Required is disabled
5. Under Context Field Values, disable any context values defined except Global Data Elements as it need to be enabled. Simply click on Segments and disable any segments defined for this one.
6. Save your changes
7. Freeze the flexfield definition
8. Compile

   3. How to enable the Journals-Captured Information descriptive flexfield?

Define context values for each of the account values you want to capture information for.
Then define context-sensitive segments that will hold the desired information.

See Note:141887.1 for more information.

   4. Why columns Attribute11 through Attribute20 in Descriptive Flexfield Enter Journals: Lines cannot be used?

These columns are reserved for descriptive flexfield Regional Reconciliation Lines – JG_ZZ_RECON_LINES.

See Note:197562.1 for more information.

Basic Changes

Functional design

1. Set Of Books is replaced by the term Ledger.

2. Accounting entries for transactions happening in all the applications such as Purchasing,Cost Management,Payables will go to General Ledger through a common module called “Subledger Accounting (SLA)” which is introduced in R12 and accounting entries can be viewed at SLA menu.

3. Accounting entries can be created manually at SLA level and can be transferred to General Ledger by running the program ‘Transfer to GL’.

4. SLA architecture gives the flexibility to derive the accounts for all transactions when it comes to SLA using Account Derivation Rules to meet various business needs and the accounting entries using those derived accounts can be transferred to General Ledger. Also it gives the flexibility to modify the accounting line types,balance types,conditions based on which the accounting gets generated for all the event classes.

5. SLA has the option to generate the accounting entries for respective subledgers in Draft mode or Final mode. Accounting entries can be created in Draft mode first in SLA which is a rough or draft entry to see whether the journal needs any modification in terms of account code or journal category. These draft entries will not get transferred to GL at any point of time. If any modification is required, it can be done using the features available in SLA and the accounting entries can be created in Final mode once the user feels that the journals do not need any modification. When the entries get created in Final mode in SLA, it will override the entries already created in Draft mode and these final mode entries alone will get transferred to GL.

5. The concept of Secondary Ledger has been introduced so that you can have two different accounting methods set at ledger level, for eg; Accrual basis accounting method for Primary ledger and Cash basis accounting method for Secondary ledger, and the ledgers can have different chart of accounts/currencies/calenders.  Actual and Encumbrance entries in the Procure to Pay cycle can be generated in secondary ledger also along with the entries in Primary ledger.

Technical design

1. The column set_of_books_id has been replaced with ledger_id in GL Tables

2. As a part of Subledger Accounting, new SLA tables XLA_AE_HEADERS, XLA_AE_LINES and XLA_DISTRIBUTION_LINKS have been introduced through which the accounting entries flow to GL.

3. PO details will not available in reference columns(reference_1,reference_2…) in tables GL_JE_LINES and GL_BC_PACKETS. Hence accounting entries in these tables can be retrieved only using SLA tables and GL_IMPORT_REFERENCES table.

4. Receiving Subledger/Inventory subledger/Payables subledger is not directly linked to table GL_JE_LINES,instead it is linked through the subledger tables XLA_AE_HEADERS, XLA_AE_LINES and XLA_DISTRIBUTION_LINKS.

5. XLA_AE_LINES table is mapped to GL_IMPORT_REFERENCES table with the gl_sl_link_id and gl_sl_link_table columns. The linking columns between GL_IMPORT_REFERENCES and GL_JE_LINES tables are je_header_id and je_line_num.

Setting up of Encumbrance

Defining the Subledger Accounting Method (SLAM) :

Navigation:

General Ledger>Set up>Financials>Accounting Set up Manager>Accounting Set ups
Query the ledger and you can find the option for setting up the Subledger Accounting Method

Subledger Accounting Method is having the option of

a) Standard Accrual
b) Encumbrance Accrual
c) Standard Cash
d) Encumbrance Cash

If Encumbrance needs to be enabled, then the Subledger Accounting Method has to be set as  “Encumbrance Accrual” in case of Accrual basis accounting method or “Encumbrance Cash” in case of cash basis accounting method for the ledger.
If Encumbrance is not used, then the Subledger Accounting Method has to be set as “Standard Accrual” or “Standard Cash” for the ledger.

Difference in Behavior between 11i and R12:

1. In 11i, Encumbrance related set ups include enabling the Budgetary control flag for the set of books, defining the Reserve for Encumbrance a/c, enabling the encumbrance for REQ,PO and INVOICE in Financial Options.
Where as in R12, Subledger Accounting Method has to be set for the ledger in addition to other set ups done in 11i. If it is set to “Standard Accrual”, Encumbrance cannot be used for that ledger even though the Encumbrance is enabled for the REQ,PO and INVOICE in Financial Options.

2. In 11i, there is an option to choose different encumbrance types for REQ,PO and INVOICE in Financial options but in R12, Financial options does not have the LOV to choose the encumbrance type. By default, Requisition encumbrance will be “Commitment”, PO encumbrance will be “Obligation” and invoice encumbrance will be “INVOICE”. If any of these 3 encumbrance types is not enabled in GL > Set up > Journal > Encumbrance, then the respective document REQ/PO/Invoice will throw budgetary control exception and will fail funds check.

Generation of Encumbrance Entries

Functional design

On Reserving and Approving the Requisition(PR)/Purchase Order(PO), Encumbrance amount gets reflected in Funds Inquiry screen and the encumbrance entries can be viewed in SLA menu in Purchasing module.

Navigation:
Purchasing>Accounting>SLA:User Main Menu>Accounting events
Query by transaction dates,ledger name and transaction number which is the PR/PO number

Following Accounting entries will be available in the HTML page

Budget a/c DR
Reserve For Encumbrance CR

There is an option to do funds check before taking the RESERVE and APPROVE action on the PR/PO by navigating to Tools > Check funds in Requisitions and Purchase Order forms to see the funds check behavior before approving the PR/PO. This funds check activity will create a draft entry in SLA and once the document is reserved, encumbrance entry will get created in Final mode overriding the draft entry already created for the “Check funds” action. If the funds check fails due to insufficient funds on taking the RESERVE action, entries will get created with Invalid status in SLA.

If Secondary ledger is associated to the primary ledger with the conversion level as ‘Subledger’ and if the secondary ledger is using encumbrance based SLAM, then encumbrance entries will get created in both primary subledger and secondary subledger on doing the RESERVE action on the PO.

The Concurrent Request “Transfer Journal Entries to GL” has to be submitted from Purchasing Responsibility to create the encumbrance entries in GL. On running this request, encumbrance entries created in Final mode alone will get transferred to GL.

Difference in Behavior between 11i and R12:

1. In 11i, encumbrance entries will get transferred to GL by running the concurrent program “Program-Create Journals” from GL responsibility. But in R12, “Transfer Journal Entries to GL” has to be submitted from Purchasing Responsibility to create the encumbrance entries in GL.

2. In 11i, it is not possible to view the encumbrance entries in Purchasing module, where as in R12, the entries can be viewed from SLA menu in Purchasing.

3. In 11i, a credit against the Reserve For Encumbrance a/c (RFE) can be seen only at the time of posting the Encumbrance debit entry in GL. But in R12, RFE a/c gets credited along with the budget a/c debit entry which can be viewed from SLA menu in Purchasing.

Technical design

On reserving and approving the PR/PO, encumbrance entries get generated in table GL_BC_PACKETS with column source_distribution_type as ‘PO_REQ_DISTRIBUTIONS_ALL’ for PR and ‘PO_DISTRIBUTIONS_ALL’ for PO and column source_distribution_id_num_1 as req distribution id for PR and po distribution id for PO.

Encumbrance entries will also get generated in the table PO_BC_DISTRIBUTIONS which has been newly introduced in R12. This table has the columns ‘reference4′ and ‘reference3′ columns where the PO/PR number and distribution id gets populated.
These accounting entries are also populated in the table XLA_AE_LINES. The table XLA_AE_HEADERS will show whether the encumbrance entry is created in Draft mode or Final mode or Invalid mode indicated by the column accounting_entry_status_code and it will also show whether the entry is transferred to GL or not indicated by the column gl_transfer_status_code.

The tables PO_BC_DISTRIBUTIONS and XLA_AE_HEADERS are linked with the column ‘event_id’.
The tables XLA_AE_HEADERS and GL_BC_PACKETS are linked with the column ‘ae_header_id’.
The tables XLA_AE_HEADERS and XLA_AE_LINES are linked with the column ‘ae_header_id’.

Once the entries are populated in GL and those entries are posted, records from the table GL_BC_PACKETS will get deleted but the entries in table PO_BC_DISTRIBUTIONS will remain always.

Difference in Behavior between 11i and R12:

In 11i, Encumbrance entries created in GL_BC_PACKETS will be directly moved to GL_JE_LINES by running the CJE program, whereas in R12, Encumbrance entries gets generated in a new table PO_BC_DISTRIBUTIONS and also in XLA tables in addition to GL_BC_PACKETS.

Receipt Accounting

As mentioned earlier, accounting entries for transactions happening in Receiving subledger and inventory subledger will flow to GL only through SLA which involves a new process called “Create Accounting process”.

Create Accounting process for Online Accruals

When purchase order is set to accrue at receipt, accounting entries get created in Receiving subledger once the receiving transactions are done. Then the Create Accounting process should take place to create journals in SLA accompanied by Transfer to GL process and posting which are optional. Users can choose whether they want the journal import and posting also to happen at the same time when the create accounting process is done or the Transfer to GL/Posting can be done explicitly. But if encumbrance is enabled, it is always preferred to do the Transfer to GL and Posting along with the create accounting process by having the values for parameters ‘Transfer to GL’ and ‘Posting in GL’ as YES while submitting the create accounting program. For more details on this, please refer to Note.728064.1. Another main implication of this model of doing the GL transfer and posting along with create accounting process is that, on failure of Journal Import, the data will be rolled back to SLA tables and hence there will not be any data in GL interface.

This Create Accounting Process involves two concurrent programs Create Accounting-Receiving which can be submitted from Purchasing>View Requests or from Cost Management Responsibility > SLA menu > Create Accounting and Create Accounting-Cost Management which can be submitted from Cost Management Responsibility > SLA menu. ”Create Accounting – Receiving” only accounts for Expense destination PO Receipt. “Create Accounting – Cost Management” accounts for all transactions mentioned below.

- Expense destination PO Receipt
- All Inventory transactions including inventory destination POs
- WIP transactions
- Accrual Write Off transactions

Parameters used while submitting the Create Accounting concurrent program:

• Ledger – Ledger (SOB) name to be given
• End date – Accounting entries to be created for all receipts  TO DATE
  a) Draft – Draft mode creates the SLA journals as Draft which can be modified. Hence these entries will not get transferred to General Ledger and it will be available only in SLA. Once the entries created in Draft mode are verified and confirmed, Create Accounting program has to be run in Final mode and the entries getting created now will override the draft entries in SLA and will get transferred to General Ledger.
  b) Final – Final mode creates SLA journals which can not be modified and can be transferred to General Ledger.
• Report – Options available are Detail or Summary
• Transfer to General Ledger – Yes or No – If the mode is set to Final and the value for this parameter is set to No, then the accounting entries will get created only in SLA table and it will not be available in gl_interface or GL. You need to submit the program “Transfer to Gl” in Cost Management Responsibility > SLA to transfer the entries created in Final mode from SLA to General Ledger.
• Post in General Ledger – Yes or No

  a) Online Accruals with Expense destination

Functional design

When the PO which is set to accrue at receipt is received and delivered to expense destination, Receipt Accounting happens in Receiving subledger. Then the Create Accounting process has to be submitted to generate the receipt accounting in SLA and GL.
This receipt accounting includes encumbrance reversal entries if the PO is encumbered, otherwise it just includes the actual entries. These entries can be viewed in SLA menu in Cost Management module.

Navigation:
Cost Management,SLA > SLA >SLA: Inquiry > Accounting event
Query by transaction dates and ledger name

Following Accounting entries will be available in the HTML page

AP Accrual a/c CR
Receiving Inspection a/c DR

Charge a/c DR
Receiving Inspection a/c CR

If encumbrance is enabled, encumbrance reversal also can be viewed as follows

Budget a/c CR
Reserve For Encumbrance DR

These entries can also be viewed from Receiving Transaction Summary > View Accounting.

In encumbrance enabled environment, once the receiving process is done, Create Accounting process and posting in GL has to be completed in order to get the encumbrance reversal and actuals to hit the GL funds inquiry simultaneously as the funds availability calculation in Funds Inquiry screen will consider the encumbrance reversal and actuals only when they are posted in GL.

Technical design

When purchase order has Accrue on Receipt set to YES, Receiving Transaction Processor generates the accounting entries in RCV_RECEIVING_SUB_LEDGER upon Receipt and Deliver of the PO. Then the Create Accounting process should take place to create SLA journals which will insert records in XLA_AE_HEADERS, XLA_AE_LINES and XLA_DISTRIBUTION_LINKS. These accounting entries will be available in the table XLA_AE_LINES. The event type code in XLA_AE_HEADERS for this Encumbrance Reversal entry is DELIVER_EXPENSE and the event type code in XLA_AE_HEADERS for these actual entries will be RECEIVE for receipt accounting and DELIVER_EXPENSE for delivery accounting.
The tables RCV_RECEIVING_SUB_LEDGER and XLA_DISTRIBUTION_LINKS can be linked using the column source_distribution_id_num_1. The value of rcv_sub_ledger_id has to be given as source_distribution_id_num_1 for the source_distribution_type “RCV_RECEIVING_SUB_LEDGER” in XLA_DISTRIBUTION_LINKS table.

  b) Online Accruals with Inventory destination

Functional design

When the PO is received and delivered to inventory destination, Receipt Accounting happens in Receiving subledger and Deliver Accounting happens in inventory subledger. Then the Create Accounting process has to be submitted to generate the receipt accounting and deliver accounting in SLA and GL. This deliver accounting includes encumbrance reversal entries if the PO is encumbered, otherwise it just includes the actual entries.

View Accounting from Receiving Transaction Summary will show the accounting entries for RECEIVE transaction. To view the actual entries for DELIVER transaction, navigate to Material Distributions form which will show the accounting entries once the deliver transaction is costed. To view these actual entries and Encumbrance Reversal entries in SLA after create accounting process is done, navigate to

Cost Management Resp>SLA>Inquiry>Accounting event
Query by transaction dates and ledger name

Following Accounting entries will be available in the HTML page

AP Accrual a/c CR
Receiving Inspection a/c DR

Material Valuation a/c DR
Receiving Inspection a/c CR

If encumbrance is enabled, encumbrance reversal also can be viewed as follows provided the flag “Reverse encumbrance” is checked in organization parameters > Costing tab.

Budget a/c CR
Reserve For Encumbrance DR

In encumbrance enabled environment, once the receiving process is done, Create Accounting process and posting in GL has to be completed in order to get the encumbrance reversal and actuals to hit the GL funds inquiry simultaneously as the funds availability calculation in Funds Inquiry screen will consider the encumbrance reversal and actuals only when they are posted in GL.

 Technical design

When purchase order has Accrue on Receipt set to YES and destination_type_code is set to Inventory, Receiving Transaction Processor generates the accounting entries in RCV_RECEIVING_SUB_LEDGER upon Receipt and Cost manager generates the accounting entries in MTL_TRANSACTION_ACCOUNTS upon Deliver of the PO. Then the Create Accounting process should take place to create SLA journals which will insert records in XLA_AE_HEADERS, XLA_AE_LINES and XLA_DISTRIBUTION_LINKS. These accounting entries will be available in the table XLA_AE_LINES. The event type code in XLA_AE_HEADERS for this Encumbrance Reversal entry is PO_DEL_INV and the event type code in XLA_AE_HEADERS for these actual entries will be RECEIVE for receipt accounting and PO_DEL_INV for delivery accounting.

The tables MTL_TRANSACTION_ACCOUNTS and XLA_DISTRIBUTION_LINKS can be linked using the column source_distribution_id_num_1. The value of  inv_sub_ledger_id has to be given as source_distribution_id_num_1 for the source_distribution_type “MTL_TRANSACTION_ACCOUNTS”.

Difference in Behavior between 11i and R12:

1. In 11i, Receiving Transaction Processor creates the Receipt Accounting entries in Receiving Subledger as well as in GL_INTERFACE. Journal Import will be done to transfer the entries to GL_JE_LINES where as in R12, Receiving Transaction Processor will create the entries only in Receiving Subledger. Create Accounting Program has to be run to create SLA journals which in turn will trigger the journal import.

2. In 11i, if encumbrance is enabled, encumbrance reversal and actuals will undergo funds check when these entries are populated in gl_interface and GL funds inquiry will reflect the encumbrance reversal and actuals even before posting the entries in GL. But in R12, encumbrance reversal and actuals will hit the GL funds inquiry only when these entries are posted in GL even though funds check happens in SLA itself.

  c) Create Accounting process for Period End Accruals

Functional design

When the PO which is set to accrue at period end is received and delivered to expense destination and Receipt Accruals Period End program is submitted, accounting entries get created in Receiving subledger during period end for the PO shipments which has the received quantity greater than billed quantity. Then the Create Accounting process has to be submitted to generate the receipt accounting in SLA and GL.

This create accounting process is accompanied by Subledger Multiperiod Accounting program which gets spawned automatically to generate the reversal for the accrual entries for the next period in SLA. Depending on the value for  the parameter “Transfer to GL” given while submitting the create accounting program, Journal import will happen and the accrual entries for the current period and next period will get transferred to GL.

During this create accounting process, it has to be ensured that the end date given while submitting the Create Accounting program is greater than or equal to the first date of the next period in which accrual reversal is supposed to happen. If the end date of Create Accounting program is less than the first date of the next period, accrual entries for the current period alone will get created in Final mode and will get transferred to GL, where as  the reversal entries will get created in SLA with status as ‘Incomplete’ and it is not eligible to get transferred to GL . To transfer the accrual reversal entries which got created with INCOMPLETE status from SLA to GL, it has to be final accounted in SLA first which can be done by running the program ‘Complete Multiperiod Accounting’ with end date which includes the first date of next period and then it can be transferred to GL. If the GL period is closed for the current period or for the next period, period end accrual entries and reversal entries will get created only in SLA. To transfer these entries to GL, the concurrent request “Transfer Journal entries to GL-Receiving” needs to be submitted after opening the GL period.

This receipt accounting includes encumbrance reversal entries if the PO is encumbered, otherwise it just includes the actual entries. These entries can be viewed in SLA menu in Cost Management module and it cannot be viewed from Receiving Transactions Summary > Tools > View Accounting.

Navigation:
Cost Management>SLA Resp>SLA>Inquiry>Journal entries
Query by transaction dates and ledger name

Following Accounting entries will be available in the HTML page

AP Accrual a/c CR
Charge a/c DR

If encumbrance is enabled, encumbrance reversal also can be viewed as follows

Budget a/c CR
Reserve For Encumbrance DR

for the period in which Receiving is done and for the next period,you can see the reversal entry as

AP Accrual a/c DR
Charge a/c CR

If encumbrance is enabled, encumbrance reversal also can be viewed as follows

Budget a/c DR
Reserve For Encumbrance CR

As mentioned for online accruals with Expense destination, in encumbrance enabled environment, once the receiving process is done, Create Accounting process and posting in GL has to be completed in order to get the encumbrance reversal and actuals to hit the GL funds inquiry simultaneously as the funds availability calculation in Funds Inquiry screen will consider the encumbrance reversal and actuals only when they are posted in GL.

Encumbrance will get reversed from the PO once the invoice is validated.Encumbrance on the PO will get converted to Invoice encumbrance. On doing Create Accounting for the invoice, Encumbrance on the invoice will also get reversed. But this invoice encumbrance reversal and Actuals will get reflected in Funds Inquiry screen only when these entries are posted in GL.

Technical design

When Purchase Order has Accrue on Receipt flag set to NO, Receipt Accruals Period End program generates the accounting entries only in RCV_RECEIVING_SUB_LEDGER. Then the Create Accounting process should take place to create SLA journals which will insert records in XLA_AE_HEADERS, XLA_AE_LINES and XLA_DISTRIBUTION_LINKS. These accounting entries will be available in the table XLA_AE_LINES. The event type code in XLA_AE_HEADERS for this Encumbrance Reversal entry is PERIOD_END_ACCRUAL and the event type code in XLA_AE_HEADERS for these actual entries will be RECEIVE for receipt accounting and PERIOD_END_ACCRUAL for delivery accounting.
The tables RCV_RECEIVING_SUB_LEDGER and XLA_DISTRIBUTION_LINKS can be linked using the column source_distribution_id_num_1. The value of rcv_sub_ledger_id has to be given as source_distribution_id_num_1 for the source_distribution_type “RCV_RECEIVING_SUB_LEDGER” in XLA_DISTRIBUTION_LINKS table.

Difference in Behavior between 11i and R12:

1. In 11i, Receipt Accruals Period End program creates the Receipt Accounting entries in Receiving Subledger as well as in GL_INTERFACE. Journal Import will be done to transfer the entries to GL_JE_LINES where as in R12, Receipt Accruals Period End program will create the entries only in Receiving Subledger. Create Accounting Program will create SLA journals and ‘Transfer Journal entries to Gl’ program will move the entries to GL from SLA.

2. In 11i, Accrual entries need to be reversed manually in the next period whereas in R12, reversal of accrual entries for the next period will happen automatically

3. In 11i, if encumbrance is enabled, encumbrance reversal and actuals will undergo funds check when these entries are populated in gl_interface and GL funds inquiry will reflect the encumbrance reversal and actuals even before posting the entries in GL. But in R12, encumbrance reversal and actuals will hit the GL funds inquiry only when these entries are posted in GL even though funds check happens in SLA itself.

Impact of Secondary ledger on Create Accounting process (applicable for both Online accruals and Period end accruals)

If Secondary ledger is associated to the primary ledger with the conversion level as ‘Subledger’ and if the secondary ledger is using Accrual based SLAM (e.g Encumbrance Accrual/Standard Accrual), then encumbrance entries will get created in both primary subledger and secondary subledger on doing the Create Accounting process. On the other hand, if the Secondary ledger associated to the primary ledger is using Cash based SLAM (e.g Encumbrance Cash/Standard Cash) with the conversion level as ‘Subledger’, then the setup mentioned below is mandatory. Otherwise, Create Accounting process will error out or complete with warning and will not generate the receipt accounting entries neither in Primary ledger nor in Secondary ledger.

Setup to be done for Secondary ledger using Cash based SLAM:

When the Primary ledger itself is using Cash basis accounting, Accrual based accounting entries should not get generated for Receiving transactions for the Primary ledger. In such case, it is not required to run the programs ‘Create Accounting-Receiving’ or ‘Create Accounting-Cost Management’ as no accounting entries will be created by these programs.

 Impact of Periodic Average Costing on Create Accounting process (applicable for both Online accruals and Period end accruals) 

R12 SLA design has no impact when Periodic Average Costing (PAC) is used as it follows the same 11i approach. Accounting entries created in PAC will not go to SLA and it will not undergo the create accounting process. Instead it will get transferred to GL via gl_interface from PAC distributions . But the perpetual accounting entries will also happen along with PAC entries where the perpetual accounting will follow the SLA design. But those entries should not get imported from SLA to GL as PAC accounting will be transferred to GL. To restrict the GL import of perpetual accounting entries, “Transfer to GL” option in organization parameters should be set to None for organizations which use PAC so that xla_ae_headers for perpetual accounting will have the gl_transfer_status_code as “NT” and it will not be picked by the journal import process.

Accrual Reconciliation Process

a) Accrual Reconciliation Reports:
After completing  the Receipt transactions and Invoice matching, Create Accounting program has to be run in Final mode along with the  subsequent transfer of entries to General Ledger after which the  Accrual Reconciliation Process has to be started.

“Accrual Reconciliation Load Run” program has to be submitted with transaction date as the parameter which will populate the data in tables CST_RECONCILIATION_SUMMARY, CST_AP_PO_RECONCILIATION and CST_MISC_RECONCILIATION. Now run the Accrual Reconciliation Report for the operating unit and do the reconciliation. There are 3 different types of Accrual Reconciliation Report

1. AP and PO Accrual Reconciliation Report – This report shows the transaction details based on each accrual account for each PO distribution with the Receiving transaction amount and invoice transaction amount with a net balance greater than zero.

Parameters used while submitting the program:

Operating Unit – Select the Operating Unit for the report
Title – Enter your title for the report
Sort by – Parameter to specify how to sort the data at the distribution level – Valid Values – Age in days,Total Balance,Vendor,PO number (default)
Aging Period Days – The number of days by which to group transactions sorted in descending order
Item From and Item To – Range of items to consider for this report
Vendor From and Vendor To – Range of Vendors to consider for this report
Min Outstanding Balance and Max Outstanding Balance – Limits of distribution balance to dispaly
Balancing Segment From and Balancing Segment To – Range of balancing segment to consider for this report

2. Summary Accrual Reconciliation Report – This report shows the total balances for each accrual account without any distribution details and individual transaction amount and also shows whether that summarized accrual balance is related to AP PO transaction or AP no PO transaction or Miscellaneous Inventory transaction.
Parameters used while submitting the program:

Operating Unit – Select the Operating Unit for the report
Title – Enter your title for the report
Balancing Segment From and Balancing Segment To – Range of balancing segment to consider for this report

3. Miscellaneous Accrual Reconciliation Report – This report shows the transaction details based on each accrual account which got hit because of Miscellaneous Inventory transactions and AP NO PO transactions.Accrual amount will be displayed for each transaction along with the source whether it is INV or AP. This report picks data from CST_MISC_RECONCILIATION which gets populated during the load run process.

Parameters used while submitting the program:

Operating Unit – Select the Operating Unit for the report
Title – Enter your title for the report
Sort by – Parameter to specify how to sort the data at the distribution level – Valid Values – Item,Transaction Date (default) , Amount
Date From – Starting date of time period to display for this report
End Date – Ending date of time period to display for this report
Item From and Item To – Range of items to consider for this report
Min Amount and Max Amount – Limits of transaction amount to display
Balancing Segment From and Balancing Segment To – Range of balancing segment to consider for this report

Difference in Behavior between 11i and R12:

1. In 11i, the Accrual Rebuild Reconciliation Report  which was  required  to be run  to populate the accrual reconciliation table is now replaced by “Accrual Reconciliation Load Run” program in R12. The table PO_ACCRUAL_RECONCILE_TEMP_ALL has been replaced by the tables  CST_RECONCILIATION_SUMMARY and  CST_AP_PO_RECONCILIATION in R12.

2. 11i has only one Accrual Reconciliation Report which will show all the transactions for the accrual account irrespective of whether it is Miscellaneous INV transaction or AP NO PO transaction. But in R12 there are 3 different reports, one for AP-PO individual transactions, one for Miscellaneous transactions showing the individual transaction details for source INV and AP and one for showing the summarized accrual balance for all transaction types.

3. 11i has the option of running the Accrual Reconciliation Report with net accrual balance as 0 as well as net accrual balance greater than 0. But in R12, Accrual Reconciliation Report will show only the transactions having net accrual balance greater than zero.

4. In 11i, Accrual Reconciliation Report can be run for a specific data range and accrual balances can be checked for a specific period. But in R12, Accrual Reconciliation Report always shows the ‘as on date’ accrual balance and the report cannot be run for a specific date range.

b) Accrual Write-off Process:
Once the accrual entries for the PO or invoice are shown in Accrual Reconciliation Report, Accrual Write-off can be done using Cost Management or Purchasing responsibility>Accounting>Accrual write offs>AP and PO. This will delete the accrual entry from CST_AP_PO_RECONCILIATION table and populate the write off transaction in CST_WRITE_OFFS table. This write off transaction can also be viewed in the form View Write offs.
Accounting entries have to be created in SLA and GL for these write off transactions by submitting the Create Accounting program.This can be viewed in SLA menu by navigating to Tools > View Accounting in the View Write offs form.

Following Accounting entries will be available in the HTML page for a RECEIVE transaction

Accrual a/c DR
Offset a/c CR

Similarly for an AP PO MATCH transaction

Accrual a/c CR
Offset a/c DR

This Offset a/c will always be the Invoice Price Variance account.

Accounting events for this write off transaction will show the Event status as “Final Accounted” once the Create Accounting program is submitted and the entries are transferred to GL.

Difference in Behavior between 11i and R12:

1. The table PO_ACCRUAL_WRITE_OFFS_ALL has been replaced by the table CST_WRITE_OFFS in R12.

2. In 11i, accounting will not get created for the write off transaction and accrual entry has to be manually adjusted in GL whereas in R12, Create Accounting program will create the accrual entry for the write off transaction in SLA as well as in GL and hence manual adjustment of accrual entry is not required.

Accounting Flow

for

Purchase Orders, Receipts and Matched Invoices in an Encumbrance Environment

An Oracle White Paper

This document details the accounting entries that are expected for purchase orders with Expense or Inventory destinations, receipts and matched invoices. It also considers the two choices of accrual available for Expense items in an encumbrance-enabled environment.

Expense items can be accrued at

a)     Period-end

b)    On Receipt

Inventory Items can ONLY be accrued at

a)     Receipt

This document consists of the following case studies/scenarios.

Accrue on receipt: (APO)

Case 1: Expense Destination/Create, Approve, Reserve/Receive/Invoice

Case 2: Expense Destination/Create, Approve, Reserve/Invoice/Receive

Case 3: Expense Destination/Create, Approve, Reserve/Receive/Invoice at a price greater than PO price

Case 4: Expense Destination/Create, Approve, Reserve/Receive/Invoice at a quantity greater than PO quantity

Case 5: Inventory Destination/ Create, Approve, Reserve/Receive/Invoice

Case 6: Inventory Destination/ Create, Approve, Reserve/Invoice/Receive

Accrue at Period-end: (APE)

Case 1: Create PO /Receive PO /Deliver PO /Invoice/Run the period end program

Case 2: Create PO /Invoice/Receive PO/Deliver PO/Run the period end program

Case 3: Create PO/Receive PO/Deliver PO/Run the period end program/Invoice

Case 4: Create PO/Receive PO/Run the Period end program/Deliver PO/Run the

period end program/Invoice

Case 5: Create PO /Receive PO /Deliver PO /Invoice at a price greater than PO

Price/Run the period end program

Case 6: Create PO /Receive PO /Deliver PO /Invoice at a quantity greater than PO

Quantity/Run the period end Program

The following Pages will explain each case in detail:

LEGEND: AOR= Accrue On Receipt, APE= Accrue at Period-End

Note:

• Corresponding offsetting accounts have same symbols.
• PO base price refers to received quantity * unit Price in PO line
• NR tax refers to Non Recoverable Tax calculated for the (received quantity * po line unit price)

• REC tax refers to Recoverable Tax calculated for the (received quantity * po line unit price)

Important Notes:

1. Accrual entries will be generated /created ONLY when the Received quantity > Billed quantity at the time of running Receipt Accruals-Period end program.

2. Under the cases mentioned above under the Period-end Section, manual reversal of journal entries are not required except for Case 3 and Case 4 since there are NO accrual entries created /generated.

3. For all these cases the account records from receiving will also be inserted into GL_BC_PACKETS, along with the other subledger tables mentioned above. These records in GL_BC_PACKETS can be viewed by querying the  max(packet_id), as there are no REFERENCE fields populated for receiving records.

4. Liability a/c  which is recorded at invoice price will also include the recoverable and non-recoverable tax rates.

Accounting Flow against Purchase Orders, Receipts and Matched Invoices.

Oracle Financial Forums

Hello All,

My new forum now is ready, so we can support each other by posting our concerns or just sharing knowledge with our friends.

Please just register and share with your connections.

Regards,

Mahmoud Elemam

Treasury Stocks or Equities FAQ

CONTENTS

——–

1.  Is it possible to record the mutual funds investments using XTR?

2.  How does the system manage loan stock?

3.  Regarding a workaround for resale stock using weighted average cost, how do you address these new problems?

Buy Stock Deal

1. Date=05-JAN-2003, Shares=2000, Price=10 –>CpartyA

2. Date=10-JAN-2003, Shares=3000, Price=11 –>CpartyB

Total Average cost per shares is 10.6=[(2000*10)+-(3000*11)/5000]

Sell Stock Deal

1. Date=11-JAN-2003, Shares=2000, Price=12 number of shares to match to buy1: 2000 * (2000/5000) = 800, remaining shares=1200 number of shares to match to buy2: 2000 * (3000/5000) = 1200, remaining shares=1800

P/L : 800 * (12-10) +- 1200 * (11-10) = 2800

The problem is one Stock issue code could buy from different Cparty, and when selling out 2000 shares, that deal is between company and CpartyA, nothing about CpartyB, after resale deal, both remaining shares should be CpartyA=0 shares                        CpartyB=3000 shares

So if you can not allocate selling out shares based on hand total shares, the P/L amount will not use weighted average cost to calculate.

Counterparty is the custodian, for particular Counterparty total selling out number of shares must be equal to total buying number of shares.

QUESTIONS & ANSWERS

——————-

1. Is it possible to record the mutual funds investments using XTR?

Answer

——

You can definitely try using the STOCK deal type in Treasury to record mutual fund investments. For example, the following features of the STOCK deal type are useful in modeling most mutual funds:

1. Price per Share.  You can use this to record the unit price of the fund, be it exchange-quoted or NAV-based.

2. Number of Shares.  This would be the number of units that you purchase or sell.

3. Cash dividends.  You can use this to model income that’s distributed by the fund.

4. Brokerage & Tax.  Useful if you need to record fees and taxes on your deals.

5. Revaluation. Useful to calculate and journalize the holding profit/loss and realized profit/loss of your deals. Market prices are either the exchange-quoted prices or the published NAV figures released by the funds.

There may be certain types of mutual funds that can’t be easily modeled by STOCK, since “mutual funds” is such a broad term itself. It is for this reason that documentation doesn’t explicitly mention it. On the other hand, deal types such as ONC in Treasury may also be suitable for certain funds (such as certain type of money market fund whose unit price is always 1).

2.How does the system manage loan stock?

Answer

——

Stock loans or securities lending is common between financial institutions, and is generally connected to short-selling. Brokerage houses often borrow stocks from other institutions for short-sellers to use (short-sellers sell stocks they don’t own and make money by “sell high, buy low”). The lending party receives money from the borrowing brokerage. When the brokerage returns the stocks later, it gets its cash collateral back.

Oracle Treasury and its Equities module are primarily designed for corporate treasury type users’ investment activities. Therefore, there’s no explicit support for stock loans/securities lending. Having said this, there ARE functionalities that may be sufficient for that prospect, depending on its specific requirements. For example, Oracle

Treasury allows you to enter and update loan securities between companies and counterparties. This is done in the Counterparty Profiles form. You can specify and update information such as estimated dollar value, valuer, valuing schedule, and related deal numbers. There is also the Loan Securities Report that report on such information by

companies. Separately, depending on the role of the company, you can use the existing functionality in the STOCK deal type to model much of the stock loan transaction, by using BUY/SELL subtypes as a workaround.

3.  Regarding a workaround for resale stock using weighted average cost, how do you address these new problems?

Buy Stock Deal

1. Date=05-JAN-2003, Shares=2000, Price=10 –>CpartyA

2. Date=10-JAN-2003, Shares=3000, Price=11 –>CpartyB

Total Average cost per shares is 10.6=[(2000*10)+-(3000*11)/5000]

Sell Stock Deal

1. Date=11-JAN-2003, Shares=2000, Price=12 number of shares to match to buy1: 2000 * (2000/5000) = 800, remaining shares=1200 number of shares to match to buy2: 2000 * (3000/5000) = 1200, remaining shares=1800

P/L : 800 * (12-10) +- 1200 * (11-10) = 2800

The problem is one Stock issue code could buy from different Cparty, and when selling out 2000 shares, that deal is between company and CpartyA, nothing about CpartyB, after resale deal, both remaining shares should be CpartyA=0 shares                        CpartyB=3000 shares

So if you can not allocate selling out shares based on hand total shares, the P/L amount will not use weighted average cost to calculate.

Counterparty is the custodian, for particular Counterparty total selling out number of shares must be equal to total buying number of shares.

Answer

——

Let’s go over this example.

Initially, you own 5000 shares in total:

2000 @10 (purchased from cparty A)

3000 @11 (purchased from cparty B)

Next, you:

sell 800 shares originally acquired @10 and 1200 shares originally acquired @11, all at once to cparty A.

After the resell, you still own 3000 shares in total:

1200 @10

1800 @11.

Your average cost basis remains 10.6/share. The “Shares Remaining” field for the BUY deal in Treasury lets you know how many shares out of that particular BUY deal (with a particular acquisition price) is available for future sale. Don’t think of it as a tally of how many shares you still have with the particular counterparty. If you think from the perspective of the Company, hopefully your confusion is gone.  I agree that the following two scenarios are not exactly identical, for the reason that you’ve mentioned – from the perspective of remaining shares with the particular cparty.

(1)   BUY 2000 shares, cparty A –> SELL 2000 shares, cparty A.

BUY 3000 shares, cparty B

(2)  BUY 2000 shares, cparty A –> SELL 800 shares, both in 1 deal with cparty A.

BUY 3000 shares, cparty B –> 1200 shares,

In (1), after resell, cparty A has 0 remaining and cparty B has 3000 remaining.  In (2), after resell, cparty A has 1200 remaining and cparty B has 800 remaining.

IF all buying and selling is done with the same cparty, then the specific identification method can replicate the weighted average cost method.

In the example, if cparty A has to be the custodian, for (2) to replicate (1), the assumption is that 1200 shares need to be transferred to cparty A prior to the resell deal. This transfer is outside of Treasury.

Being able to resell to ANY counterparty is common in Treasury. The cparty used in the resell deal doesn’t need to have any BUY history. For example, you may have bought securities with cparty A and cparty B only, but you can use cparty C in the resell deal. Treasury doesn’t track the quantity of securities at the cparty level; the remaining quantity notion is from the perspective of individual BUY deal.

Our suggested workaround (for average cost method) is based on this premise. It is not the same as having the real average cost method – for example, the manual allocation becomes difficult to manage if your volumn gets bigger.

Treasury does not directly support average cost basis method in all security modules (equities, bond, discounted securities). What is offered in these deal types is the specific identification method; this is more flexible and can be used (with manual allocation) to mimic other cost methods such as average cost, FIFO, LIFO, etc, and achieve the same valuation results.

Also, common in all security modules in Treasury, the “remaining” quantity concept is within the context of the original BUY deal and is not intended to be used to reconcile the on-hand quantity with your custodian.

In this specific example, the workaround will satisfy your valuation requirement, but will make reconciliation with your custodian difficult. IF ONLY all your purchase and resell is with a single counterparty, then even reconciliation is a non-issue.

Solution Explanation:
=====================
The formula used to calculate DSO is : 

ROUND( ( (SUM( DECODE(ps.class,'INV',1,'DM',1,'CB',1,'DEP',1,0
                      ) * ps.acctd_amount_due_remaining
             ) * MAX(sp.cer_dso_days
                     )
          )
/* Pick amount_due_original only when the gl_date lies between sysdate and dso_days */
/* The Denominator would be 1 when no records are found meeting the decode criteria */
          / DECODE( SUM( DECODE(ps.class,'INV',1,'DM',1,'CB',1,'DEP',1,0
                                )* DECODE(SIGN (trunc(sysdate
                                                      ) - ps.gl_date - sp.cer_dso_days
                                                )  ,-1,
                                                (ps.amount_due_original + nvl
                                                      (ps.amount_adjusted,0
                                                      )
                                                 ) * NVL(ps.exchange_rate,1
                                          ),0
                         )
                   ) , 0,1, SUM( DECODE(ps.class,'INV',1,'DM',1,
                                                 'CB',1,'DEP',1,0
                                        ) * DECODE(SIGN (trunc(sysdate
                                                               )- ps.gl_date
                                                                - sp.cer_dso_days
                                                         ), -1,
                                                               (ps.amount_due_original
                                                                   + nvl
                                                                   (ps.amount_adjusted,0
                                                                    )
                                                                ) * NVL
                                                                    (ps.exchange_rate,1
                                                                     ),0
                                                    )
                                )
                                 )
                                 ),0
                                 ),/* dso */ 

Total outstanding receivables (open)/total sales for prior dso days) * dso days 

Currently if total sales for prior dso days is zero, we substitute a 1, which
could result in a high DSO. (You can't divide by zero). 

To get the total sales it uses the
   (amount_due_original + amount_adjusted )* exchange rate
       from ar_payment_schedules_all.
To get the total open, you use the
   (amount_due_remaining + amount_adjusted )* exchange rate
       from ar_payment_schedules_all. 

You use the amount_due_original instead of amount_due_remaining, if the gldate
lies between the sysdate and the dso days. 

You select dso days in the systems options. 

Note: credit memos are not taken into consideration. 

You can't compare the total net Receivable reported in the form with the
reports, as the date cutoff is different. The forms use todays date.
The reports use as of date.

1. Confirm additional product installation:

Confirm that you have the appropriate products installed to allow Collections to work properly. The following files will need to be compiled on your instance resulting in .plx files. Without these files compiled, Collections will not work properly.

CUSTOM.pll, GLOBE.pll, FNDSQF.pll, JE.pll, JA.pll, JL.pll,
JTF_GRID.pll, JTFDEBUG.pll, JTF_UTIL.pll ,ASOCORE.pll
ASTTMLIB.pll, ASTBOMAN.pll, IEUPUWQ.pll
CSUTILS.pll, CSQKMENU.pll, (ASTCORE.pll in Release 11i only)

2. Setup your Collections User:

Refer to Note: 230346.1 How To Setup a Collections User Account.

A. To create an account:

In System Administrator Responsibility> Security>User>Define

Enter a Username and Password

Assign the following responsibilities:

• System Administrator
• Application Developer
• Receivables Manager
• Collections Agent
• Collections Forms Administrator
• CRM Resource Manager
• Collections HTML Admin
• Telesales Agent
• Human Resources Manager
• CRM Administrator

B. In your HR Responsibility :

• Setup employee
• People>Enter & Maintain
• Enter name, birthday, gender, SSN and Save
• Note the employee number

C. In System Administrator Responsibility:

• Security>User>Define
• Query your Username
• Enter the Full Name as it appeared in the HR setup screen above
• Save

D. Using the CRM Resource Manager Responsibility

• Menu: Maintain Resource
• Create a Group
  • -Name/Start Date (you can use anything)
  • -Assign Usages
    • Collections Application
  • • Sales & Telesales Application
  • -Roles
  • Collections Agent
  • Telesales Agent
• Import Resource
  • Resource Cat = Employee
  • Enter Employee # that was noted previously
  • Click search/select employee
  • Click create resource
• Default Value window
  • select start date of the resource
• Close the window
• Select Resources click Save
• Click Details
• From the Resource Management Form, enter the Username
• Click on Roles Tab (Security & Access)
  • Add the following roles:
  • Collections Role Type
  • Collections Agent Role
  • Telesales Role Type
  • Telesales Agent Role
• Click on the Group Tab
• Query Group you created previously
• Add as an employee to the Group
• Close the form.

3. Decide what level you want the Dunning and Strategies to work.

For Release 11i:    Customer, Account, Bill-To, Delinquency
Use the responsibility – Collections HTML Administrator>Setup

For Release 12: Customer, Account, Bill-To, Delinquency
Use the responsibility – Collections Administrator>Setup Checklist

Please be sure to read the Oracle Advanced Collections User and Implementation Guides for details on the setup of the application for your instance.

4. Setup the UOM for the Strategy processing to use:

There are 2 mandatory setups:

1-  For the UOM to appear under Work Item Template, the UOM must be created under class Time class (not TIME)

2- Please ensure the UOM has a conversion attached to it. The UOM will only appear if there has a conversion attached to it.

3- After this information has been save, please bounce the apache server, clear the _oa__html_pages directory and the browser cache

A. To create a UOM and UOM class:

Defining Unit of Measure Classes
Responsibility Inventory
Menu: Setup > Units of Measure > Classes.
Steps
1. In the Units of Measure Classes window, select File > New.
2. Enter a unique name for the unit of measure class.
3. Enter a description for the UOM class.
4. Define the base unit of measure for this class.
5. Enter a unique abbreviation for the unit of measure with a maximum length of three characters.
6. Select the “inactive on” date from the date picker.
7. Save your work.

B. Click on Conversion and define the conversion for the UOM you just created.

C. The profile option : Time unit of Measure Class (JTF_TIME_UOM_CLASS) needs to be set for Collections HTML administration to determine the UOM class needed to be used.

1- Please set the profile Time unit of Measure Class (JTF_TIME_UOM_CLASS)
2- Save
3- Clear the browser cache
4- Bounce the apache server and clear the _pages directory:
- log onto UNIX
- dir comn/admin/scripts
- stop apache
adapcctl.sh stop
- navigate back to _oa__html pages directory
comn/html/_pages
- run command to delete all pages
rm -rf *
- navigate back to scripts directory
- start apache
adapcctl.sh start

5. Setup Credit Management with Credit Management Super User responsibility

Oracle Collections is designed to read data from the AR_TRX_BAL_SUMMARY table for use in the customer balances of the UWQ and the last payment information in the Collections Header. For this reason, you MUST install Credit Management and the latest patchset to have these functions working in Collections. Credit Management concurrent processes populate and update the data in the AR_TRX_BAL_SUMMARY table.

Collections also uses the Exchange Rate from Credit Management, so you must setup:

-Using Credit Management SuperUser responsibility
-Policy Management>System Options
-Make sure that these settings are set including Exchange Rate
-You can tell if they are set because when you first look at the screen, if you can select an aging bucket, then it’s not set. When the system options are set, you should not be able to select an aging bucket.

For specific information on setting up Credit Management, please review the Credit Management User Guide.

For information on the new UWQ Summary Table in Release 11i.IEX.H RUP 4 and R12, see Note 405933.1.

6. Collections prior to 11i.IEX.H uses the Territory setup to differentiate what customer belongs to what resource.

Use the CRM Administrator responsibility>Territory Administration to setup Territories. You must use the Sales & Telesales usage; the Collections Usage is not working at this time.

Oracle Collections is designed to read the AS_ACCESSES_ALL table for the assignment of resources to the work in Collections. You must use the Telesales and Sales Usage in Territory Manager to setup your Territories. Then run the Generate Territories and Assign Territories in that product to load the AS_ACCESSES_ALL table. None of these steps are considered to be part of Oracle Collections. You will need to discuss issues with Territories with the Oracle Territories team via an SR and issues with Sales Teams with the Telesales group via an SR. Until this is setup, you will need to keep the profile OS: Customer Access Level at Full in order to see your customers. If you set the profile to Sales Team, it will require the setup of territories and sales teams.

Note:

Once you setup your resources and create strategies to have the work items assigned;

If you decide to change the resources/territories in a major way, the strategy work items will still be assigned to the original resources/territories. Once a work item is created and assigned it will not be reassigned based on the new resource/territory strategy. There is an option in the Collections HTML Administrator responsibility that allows you to change the owner of the work item for that work item only. Future work items will be created with the new resource/territories in place.

For instruction on how all this changes in Release 11i.IEX.H and R12, please see Note 367373.1.

7. Next, you’ll need to create delinquencies:

• Collections Forms Administrator>Submit Request
• Run the following jobs:
  • IEX: Promise Reconciliation
  • IEX: Scoring Harness
    • One line per parameter in this order 2,1,6
    • Engine 2 to create the delinquency
    • Engine 1 to score the Party
    • Run engines 6 or 7 depending on setup of strategies.
    • 6 is for Account
    • 7 is for Bill To
  • IEX: Strategy Management

The aging of delinquencies occurs in the Delinquency Management process, which automatically runs with the Scoring Harness jobs. To confirm that you have created delinquencies, you can do a query on the iex_delinquencies_all table.

Select count(*) from iex_delinquencies_all;

If you choose to create custom scoring engines, and you have multiple concurrent processes spawning, you may need to run the scoring engines separately or you will run into FND Bug 2576919.

8. You will need to setup the Strategies at this point.

Strategies are the work items that your collectors will use to determine the course of action to closing the delinquency and receiving the money from the customer. The steps are too lengthy to explain here, please review the User Guide and White Papers for more information. (see below for white paper location)

9. Schedule Processes

In order for Work Items to be advanced in Collections you’ll need to schedule the following processes to run on a regular basis automatically:

Collections Forms Administrator responsibility – Menu>Submit Request>Single Request

Workflow Background Process

Item: Strategy Fulfillment Mailer

This will move work items waiting to go to Fulfillment.

Item: Collection Strategy Work Flow

This will keep the work items moving once they are created.

To confirm that you have created strategies and work items you can query the tables as follows:

Select count(*) from iex_strategies

Select count(*) from iex_strategy_work_items

For more information on Scoring Engines and Strategy Work, please review the White Paper that has been written by development and is available on Metalink.

11. Validate setup correct

If you have followed all the steps correctly, you will see the data in the Universal Work Queue.

If you created delinquencies, you will see the delinquencies in the appropriate node on UWQ. If you ran the Strategy Management process you will see Work Items in the Work Item node waiting to be completed.