3/11/13

Document Display

AutoAccounting Frequently Asked Questions (FAQ's) [ID 552086.1]

Modified: Aug 31, 2012 In this Document Purpose Questions and Answers How does AutoAccounting work? How do you implement AutoAccounting? How does AutoAccounting compare to Workflow Account Generator? I have an AutoAccounting Error - where do I start? I receive the following error when interfacing expense reports to AP. How do I fix the problem? PA_AA_NO_RULE_PARAM|RULE|Employee Company /u06/home/applpa/pa/3.1.39/bin/PATTER APP-00969 Program was terminated by signal 11 How do I diagnose a lookup set error? How do I resolve the following error that occurred when distributing expense report costs? paafui-E: Error calling paacaf APP-01756 Value 40 is not defined Cause: The value 40 is not valid Action: Enter a valid value. paacaf-E: Failed to validate flexfield Warning in Flex Validation for line '1263:ALL:Y:20' Does the Allow Dynamic Inserts have to be enabled for the Accounting Flexfield? I created an autoaccounting rule where the source of intermediate value is a SQL Statement. When attempting to assign the rule to an autoaccounting function the rule can not be found. Why isn't the rule in the LOV? How can I find out which parameters are valid for an AutoAccounting Function? How can I get a list of rule definitions for a particular AutoAccounting Rule How can I get a list of AutoAccounting lookup sets How can I get a list of AutoAccounting rules/flexfield segment pairings Can I create or edit existing AutoAccounting transactions? The parameter I want to use for my intermediate value is not available--where do I go to add it? What do the various AutoAccounting errors mean? What does "Defaulting key segment because profile PA_SELECTIVE_FLEX_SEG is not defined" in my log file mean? In Release 12, I have defined detailed accounting rules in Oracle Subledger Accounting. Do I still need to set up AutoAccounting in Oracle Projects? In Release 12, how does AutoAccounting compare to Oracle Subledger Accounting? References Type: FAQ Status: PUBLISHED Priority: 3

Applies to:
Oracle Project Costing - Version 11.5.2 to 12.1.3 [Release 11.5 to 12.1] Information in this document applies to any platform.

Purpose
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113 1/10

3/11/13

Document Display

This FAQ document identifies the most frequently reported how-to questions relating to Oracle Projects AutoAccounting. The articles below do not include bugs/patches or troubleshooting as these are addressed in great detail in the notes referenced at the bottom of this document.

Questions and Answers How does AutoAccounting work?

For each accounting transaction, you define rules to determine the appropriate account to charge. Each accounting transaction is identified by an AutoAccounting function. AutoAccounting functions are components of programs that you submit to generate accounting entries.

How do you implement AutoAccounting?

The steps are as follows: a). Design your AutoAccounting setup based on your implementation data. b). Define lookup sets. Navigation - Setup/AutoAccounting/Lookup Sets. To define a lookup set, you specify pairs of values. For each intermediate value, you specify a corresponding account segment value. One or more related pairs of intermediate values and segment values form a lookup set. You may need several lookup sets to map organizations to cost centers, expenditure types to account codes, event types to account codes, or for other situations where the segment value depends upon a particular predefined parameter. You can use a lookup set more than once; several AutoAccounting rules can use the same lookup set. You define and modify lookup sets using the AutoAccounting Lookup Sets window. c). Define rules. Navigation - Setup/AutoAccounting/Rules. Each AutoAccounting rule you define supplies one Accounting Flexfield segment value at a time. Thus, you need to specify one AutoAccounting rule for each segment in your Accounting Flexfield for each AutoAccounting transaction you want to use. Some of the AutoAccounting rules you define can be quite simple, such as always supplying a constant company code or natural account. Others can draw upon context information (parameters), such as the revenue category for a particular posting or the organization that owns a particular asset. You can even use multiple parameters to provide a segment value. You can reuse the same AutoAccounting rules for many different functions and their transactions. You define rules based on project information that you enter. You can use these AutoAccounting parameters as input values to your rules. Note: AutoAccounting does not use Flexfield security rules when determining a valid account combination. You must define your AutoAccounting rules to determine the appropriate account based on the rules required by your company. d). Assign rules for each function. Navigation - Setup/AutoAccounting/ Assignments. When you are assigning rules to an AutoAccounting function, you may want to assign different rules to different conditions. For example, you may want to account for indirect projects using one set of rules, and use two different sets of rules for billable items and nonbillable items on contract projects.
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113 2/10

3/11/13

Document Display

To make it easy to do this, Oracle Projects provides function transactions to each function, which identifies commonly used conditions in which you may want to assign different rules. You can assign rules to function transactions for each AutoAccounting function. You complete the following steps to assign AutoAccounting rules to AutoAccounting functions and transactions: Enable each transaction you want to use For each transaction you enable, you specify an AutoAccounting rule for each segment of your Accounting Flexfield

How does AutoAccounting compare to Workflow Account Generator?

Both the account generation processes in Oracle Workflow and AutoAccounting in Oracle Projects can create account numbers dynamically, based on transactions in Oracle Projects. This section compares the Account Generator to AutoAccounting, and provides directions for: Assigning a constant or lookup value to a segment Assigning an attribute parameter to a segment Deriving a segment value Learning more about SQL functions to generate account codes

ACCOUNT GENERATOR TERMS OR FUNCTIONALITY Workflow or Item Type Function Process Attribute Assigning a constant to a segment Assigning an attribute parameter to a segment Assigning a lookup set value to a segment

EQUIVALENT IN AUTOACCOUNTING Function Defining and assigning rules to segments Parameter Assigning a constant AutoAccounting rule to a segment Assigning an AutoAccounting rule that uses a parameter, which becomes the value (a lookupset is not used) Assigning an AutoAccounting rule that passes a parameter to a lookup set to determine the segment value Using an AutoAccounting rule that derives the intermediate value or segment value via a SQL statement.

Deriving a segment value by using SQL statements or If conditions

I have an AutoAccounting Error - where do I start?

In most cases, when a user encounters an AutoAccounting error when processing Oracle Projects transactions, you will utilize the debug log file to find the source of the error. Most AutoAccounting errors are specific and will provide you with enough information for troubleshooting purposes. Setting the Profile Option 'PA: Debug Mode' = Yes will provide more detail information in the log file.

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113

3/10

3/11/13

Document Display

I receive the following error when interfacing expense reports to AP. How do I fix the problem? PA_AA_NO_RULE_PARAM|RULE|Employee Company /u06/home/applpa/pa/3.1.39/bin/PATTER APP00969 Program was terminated by signal 11
This is an example of an AutoAccounting error given when a parameter is defined which is not available for the function. In this case the parameter Task Organization was set up to derive the Employee Company in Transfer Expense Report Cost. To troubleshoot the above error: a. Check AutoAccounting Assignments to determine the segment which is using the rule Employee Company. b. Check AutoAccounting Rules form to determine the parameter that is being used for that rule. c. Now check the AutoAccounting Parameters report to see if the parameter can be used for this function. In this case, Task Organization is not a parameter which is available for the function Transfer Expense Report Cost and therefore, caused the above error to occur. d. The selected parameter can not be used in this function, however, you may be able to use a SQL statement in the rule in order to derive the segment value you need.

How do I diagnose a lookup set error?

Warning in Auto Accounting for line '1218:ALL:N:5' xx No segment value lookup in AutoAccounting lookup set 'Organization to Company' Warning in Auto Accounting for line '1263:ALL:Y:20' This is an example of an AutoAccounting error that was caused by an incomplete Lookup Set. In this case, the expenditure was charged to a project that has the organization name of Data Systems. The Lookup Set being called by the rule does not contain Data Systems as a Intermediate Value and no Segment Value is defined. To troubleshoot the above error: a. Find the transaction which is causing the error. The transaction will be listed on the exception section of the report along with the error `Incomplete AutoAccounting Rule.' Note: the above error does not cause the entire process to complete with an error. b. From the error we know the lookup set does not contain an intermediate value and segment value that is needed to process this transaction. We can determine the segment value needed by first knowing the parameter that the rule is passing. Go to the AutoAccounting Assignments form to find the rule being called for organization. Zoom to the AutoAccounting rules form to determine the parameter being passed. In the above case, the parameter Project Organization is being passed. c. Query up the project that was charged on the transaction and get the Organization name. This is the intermediate value that needs to be entered into the Lookup Set, along with the appropriate segment value as determined by the client. d. Now query up the Lookup Set called `Organization to Company' and insert the appropriate intermediate and segment values. e. Re-test the process. Note: In the above case, it is unlikely that the project organization had changed since the time of the expenditure. This applies to Task Organization as well. However, in the case of expenditure organization it is possible that the current
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113 4/10

3/11/13

Document Display

expenditure organization is not the same as the organization on the expenditure item in error. Don't assume that the employees current organization is the organization on the expenditure. It is a good place to start however you may need to look at the expenditure organization on the expenditure item and then assure that organization exists in the Lookup Set.

How do I resolve the following error that occurred when distributing expense report costs? paafui-E: Error calling paacaf APP-01756 Value 40 is not defined Cause: The value 40 is not valid Action: Enter a valid value. paacaf-E: Failed to validate flexfield Warning in Flex Validation for line '1263:ALL:Y:20'
This is an example of an invalid segment value set up in either a rule which passes a constant value or a lookup set which derives an invalid segment value. In this case the function Distribute Expense Report cost, company segment, used a rule which contained the constant value of 40. 40 is not defined in G/L as a valid segment for Company. To troubleshoot the above error: a. Start off in the Assignment form for this function. Page down to the transaction zone and then to the assignment zone for the enable transactions. For each segment, zoom to the Rule form until you find the rule which is passing on the value in error. You may need to further zoom to the Lookup Set to determine this. b. Change the invalid value to the correct value as determined by the client. c. Retest the process. Note: If you have reason to believe that the value is valid, a good test is to change responsibilities to General Ledger and enter a journal entry using that segment value. If the entry fails then the value is invalid. If it passes, you may need to look at additional transactions and rules that are passing this value to find the cause of the error.

Does the Allow Dynamic Inserts have to be enabled for the Accounting Flexfield?
In 11i.PJ_PF.M and higher, dynamic insertion is no longer required. Users can define the Accounting Flexfield with or without the Allow Dynamic Inserts options enabled. Note 444351.1 For patchset levels prior to 11i.PJ_PF.M, dynamic insert is used to create new code combinations in the gl_code_combinations table. Therefore, enabling dynamic inserts is a requirement when running Project Accounting in patchset levels prior to 11i.PJ_PF.M.

I created an autoaccounting rule where the source of intermediate value is a SQL Statement. When attempting to assign the rule to an autoaccounting function the rule can not be found. Why isn't the rule in the LOV?
Not all parameters are available for all autoaccounting functions. If a rule is using an invalid parameter for the function, the rule will not be included in the LOV.

How can I find out which parameters are valid for an AutoAccounting Function?
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113 5/10

3/11/13

Document Display

Run the IMP: AutoAccounting Functions report. The IMP: AutoAccounting Functions report (PAXAAFTP) provides a complete list of the parameters and transactions associated with a particular AA function. All possible parameters used by the AutoAccounting rules to derive key fexfield segment values are listed. The transactions associated with the AA function are also displayed, as well as an indication of whether each transaction is enabled or not.

How can I get a list of rule definitions for a particular AutoAccounting Rule
Run the IMP: AutoAccounting Rule Definitions (PAXAARUL) report. This report shows the definition of a particular AutoAccounting rule, including the type of its intermediate source (Constant, Parameter, or SQL Statement) and the corresponding value for that source. The report will display the text of a SQL statement if that is the intermediate value source. Segment value sources will also be listed, along with the name of the lookup set where appropriate.

How can I get a list of AutoAccounting lookup sets

Run the IMP: AutoAccounting Lookup Sets (PAXAASVL) report. This report lists all the AA lookup sets along with each intermediate value and its corresponding segment value.

How can I get a list of AutoAccounting rules/flexfield segment pairings

Run the IMP: AutoAccounting Segment Rule Pairings (PAXAASRP) report. This report provides a review of all pairings of AutoAccounting rules with key flexfield segments. The report also displays each of the function's transactions for the selected function as well as function transactions without paired segments and rules.

Can I create or edit existing AutoAccounting transactions?

Oracle Projects predefines AutoAccounting transactions; you cannot modify them, or define additional transactions.

The parameter I want to use for my intermediate value is not available--where do I go to add it?
Parameters are seeded by Oracle Projects and can not be added to. However you may be able to use a SQL statement in the rule in order to derive the segment value they need.

What do the various AutoAccounting errors mean?

MESSAGE NAME PA_AA_AA_ERROR PA_AA_ABORTING PA_AA_BAD_APPLICATION PA_AA_ENTER_CONSTANT_VALUE PA_AA_ENTER_FF_STRUCTURE PA_AA_ENTER_PARAMETER_NAME PA_AA_ENTER_SQL_STATEMENT PA_AA_ERROR PA_AA_FIELD_NOT_COPIED MESSAGE TEXT Error occurred during AutoAccounting Process &PROCESS terminating with error Bad application id passed to AutoAccounting Please enter a constant value Please enter a flexfield structure Please enter a parameter name Please enter a SQL Select Statement Error in AutoAccounting Set Processing error function Function '&FUNCTION' could not update the field
6/10

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113

3/11/13

Document Display

'&FIELD' PA_AA_FIRING_RULE PA_AA_FUNC_UNINIT PA_AA_FV_ERROR PA_AA_INVALID_MODE PA_AA_INVLD_KEY_SRC PA_AA_INVLD_RULE_TYP PA_AA_INVLD_SQL_PARAM PA_AA_LESS_PARAMS PA_AA_LOOKUP_SET_INTEGRITY PA_AA_MISSING_TOKEN PA_AA_MULT_ROWS PA_AA_NOT_ENF_ARGS PA_AA_NO_DB_CNCT PA_AA_NO_DESCRP PA_AA_NO_DETAIL_POST PA_AA_NO_LOOKUP PA_AA_NO_MEMORY PA_AA_NO_PARAMS PA_AA_NO_ROWS Firing rule '&RULE' ... Function '&FUNCTION' is not initialized Error occurred during flexfield validation You have called '&FUNCTION' with an invalid mode Key source for rule '&RULE' is invalid Rule type for rule '&RULE' is invalid AutoAccounting rule '&RULE' refers to a nonexistent SQL parameter Not enough parameters passed into function '&FUNCTION' This lookup set is already in use by another rule The '&TOKEN' token is missing Rule '&RULE' selects multiple rows which is not currently supported &MODULE: Not enough arguments Unable to connect to database Unable to allocate a descriptor Detail posting disabled for code combination &CCID No segment value lookup in AutoAccounting lookup set '&LOOKUPSET' &MODULE is out of memory No parameters exist for function '&FUNCTION' SQL Select Statement for rule '&RULE' did not return any rows Rule 'RULE' refers to a parameter not connected to its parent function AutoAccounting function '&FUNCTION' does not exist The token '&TOKEN' does not exist The function transaction code &FTCODE does not exist No transactions exist for function '&FUNCTION'. SQL Statement for rule '&RULE' has selected a row with a NULL value Memory could not be allocated for '&OBJECT' in '&FUNCTION'.

PA_AA_NO_RULE_PARAM PA_AA_NO_SUCH_FNCT PA_AA_NO_SUCH_TKN PA_AA_NO_SUCH_TRANS PA_AA_NO_TRANS PA_AA_NULL_SELECTED PA_AA_OUT_OF_MEMORY

PA_AA_PAXTAU_ARG_PROTOPA_AA_PAXTAU_ARG_PROTO Usage: PAXTAU Account/password 0 Y ApplicationName AA-Function Function-Transaction Structure-ID Parameter1 Parameter2 ...
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113 7/10

3/11/13

Document Display

PA_AA_READING PA_AA_RULE_INTEGRITY PA_AA_SEG_ORDER_LBL PA_AA_SUMMARY_ALLOWED PA_AA_TOO_MANY_PARMS PA_AA_TOO_MANY_QULFRS PA_AA_TOO_MANY_ROWS PA_AA_TOO_MANY_RULES PA_AA_TOO_MANY_SQL_PARAMS PA_AA_TOO_MANY_TOKNS PA_AA_TOO_MANY_TRANS PA_AA_TOO_MANY_TRIGS PA_AA_TRANS_UNKNOWN PA_AA_VALUE_MATCH_NOT_UNIQUE PA_AA_VALUE_TOO_LARGE PA_AA_WARNING PA_AA_WRONG_FF PA_AA_WRONG_KEY_SRC_TYPE PA_AA_WRONG_N_CLMS PA_AA_WRONG_PARAM PA_AA_WRONG_RULE_TYPE

Reading &ENTITY ... This rue has been assigned to a segment. Delete assignment first AutoAccounting qualifiers by segment order Summary allowed for code combination &CCID AutoAccounting function '&FUNCTION' has exceeded the maximum number of parameters allowed SQL statement for rule '&RULE' selects more than the maximum number of qualifiers allowed SQL Select Statement for Rule '&RULE' has selected more rows than the maximum number allowed AutoAccounting function '&FUNCTION' uses more than the maximum number of rules allowed AutoAccounting rule '&RULE' uses more than the maximum number of SQL parameters allowed SQL Select Statement for rule '&RULE' selects more than the maximum number of tokens allowed Too many transactions exist for function '&FUNCTION' AutoAccounting transaction '&TRANSACTION' has more than the maximum number of triggers allowed Transaction '&TRANSACTION' is not defined Intermediate Values must be unique Value '&VALUE' is too large for its segment Warning in Auto Accounting for line '&LINE' The passed template uses a different flexfield structure from the one used by function '&FUNCTION' Reference to a non-existent key source type in rule '&RULE' SQL Select Statement for rule '&RULE' does not select the correct number of columns SQL Statement for rule '&RULE' uses incorrect number of parameters Rule '&RULE' uses an invalid rule type

What does "Defaulting key segment because profile PA_SELECTIVE_FLEX_SEG is not defined" in my log file mean?
The profile option PA: Selective Flexfield Segment for AutoAccounting has not been defined.
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113 8/10

3/11/13

Document Display

System Administration Responsibility NAVIGATE: Profile -> System -> Select Application = Oracle Projects Profile = PA% Click find Selective Flexfield Segment for AutoAccounting The value to be used maps to the Segment Rule Pairings Region of Form PAXAAASR. The numbers in this region start with zero as given in the following example: NUMBER 0 1 2 SEGMENT NAME Company Cost Center Account RULE NAME Project Company Project Cost Center Expense Report Revenue

The profile option should normally be set to correspond to the natural account segment position since typically it is the most selective value--that is, the segment with the most distinct values. You count down the rows BEGINNING WITH ONE, not zero. The segment number for account in the above example would be 3 not 2. The actual value used to set the profile option should begin with a '0'. So for example, if the account is the most selective segment in the example above, you would set the profile option to '03'. This profile value is for enhancing performance.

In Release 12, I have defined detailed accounting rules in Oracle Subledger Accounting. Do I still need to set up AutoAccounting in Oracle Projects?
Oracle Projects uses AutoAccounting to create default accounts for project transactions that it sends to Oracle Subledger Accounting. Oracle Projects predefines setup in Oracle Subledger Accounting to enable the create accounting process to accept default accounts from Oracle Projects without change. You can optionally define your own detailed accounting rules in Oracle Subledger Accounting. If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting. If you define your own detailed accounting rules in Oracle Subledger Accounting, you must still set up basic rules in AutoAccounting. Oracle Projects cost distribution, revenue generation, and accounting event generation processes require AutoAccounting to create default accounts during processing.

In Release 12, how does AutoAccounting compare to Oracle Subledger Accounting?

Oracle Projects AutoAccounting and Oracle Subledger Accounting both create accounting information based on transactions in Oracle Projects. The accounts that Oracle Projects AutoAccounting creates are default values. If you define your own detailed accounting rules in Oracle Subledger Accounting, then Oracle Subledger Accounting overwrites default accounts, or individual segments of accounts, that Oracle Projects derives using AutoAccounting. The following table lists Oracle Projects AutoAccounting functionality and the equivalent functionality in Oracle Subledger Accounting.
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113 9/10

3/11/13

Document Display

Oracle Projects AutoAccounting Functionality Lookup sets Intermediate value AutoAccounting rules Parameter AutoAccounting function transactions AutoAccounting functions AutoAccounting rule assignment

Equivalent in Oracle Subledger Accounting Mapping sets Input value Account derivation rules Source Conditions on account derivation rules Journal line types Journal lines definitions: Assign account derivation rules to journal line types

References
NOTE:222953.1 NOTE:226265.1 NOTE:267963.1 NOTE:444351.1 Current Issues for AutoAccounting Troubleshooting Guide for AutoAccounting Project Costing Knowledge Browser Product Page Is Dynamic Insertion Required When Using Oracle Projects?

https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=57edzcy2h_113

10/10