Here are some of the frequently asked questions  in project costing.

Q1. Why are my Inventory items not being burdened?

Answer:

You can not adjust expenditure items with a Transaction Source of Inventory, Inventory Misc, or Work-In-Process since all accounting for these costs occurs in Oracle Manufacturing.

Q2. When I run PRC: Distribute Labor Costs process (PALDLC) after adding a new organization, I am getting an error that the process can not find a compiled burden multiplier. Why?

Answer:

When a new organization is added to the burdening hierarchy a process must be run to create the burden multipliers for that organization.

  1. Log into the Application with your Projects Responsibility.
  2. Navigate to Other -> Requests -> Run.
  3. Run the PRC: Add New Organization Compiled Burden Multipliers (PACOANOR) process.
  4. Then re-run the PRC: Distribute Labor Costs (PALDLC) process.

The PRC: Distribute Labor Costs (PALDLC) process has to be run after the Burden Schedule has been revised with the new organization and before charging transactions to the new organization.

Q3. While running the PRC: Distribute Labor process (PALDLC), I received the exception of Missing Cost Rate. Why?

Answer:

Insure that cost rates have been properly defined.

  1. Navigate to Setup > Costing > Labor > Organization Labor Costing Rules.
  2. For the expenditure organization, verify which cost rate schedule is assigned.
  3. If there is no assignment for the specific organization, you will have to travel up the expenditure organization hierarchy to the first organization that does have an assignment, and if none are found, then check if the operating unit has an assigned schedule.
  4. If there is no assignment for the organization, any of its parents, or the operating unit, you will need to create one and assign the appropriate cost rate schedules.
  5. Using the rate schedules defined for the organization, verify that there are rates defined for the employee and/or their job.

Q4. What data is displayed for commitment columns in the Project Status Inquiry (PSI) screen?

Answer:

The column used to display commitment amount on the Project Status Inquiry (PAXURVPS) screen is defined in the Project Status Columns screen.

  1. Log into the Application using your Projects Responsibility.
  2. Navigate to Setup > Project Status Columns.

The definition here shows which columns in PA_PROJECT_ACCUM_COMMITMENTS are accessed to display project commitment information in the Project Status Inquiry (PAXURVPS) screen.

 

Q5. How can I create an new a Unit of Measure (UOM) for expenditures and billing?

Answer:
  1. Log into the Application using your Accounts Receivable Responsibility.
  2. Navigate to Setup > System > Units of Measure > Class.
  3. Set up a class for this UOM if required, for example Volume.
  4. Navigate to Setup > System > Units of Measure > UOM.
  5. Create your new unit of measure.
  6. Switch to your Projects Responsibility.
  7. Navigate to Setup > System > Units.
  8. Set up the same unit of measure.
  9. Enter Expenditure Types as needed with expenditure type class of “Usage” and add the cost rates.
  10. Save your work.

 

Q6. In 11i, why does the PRC: Interface Labor Costs to General Ledger (PAGGLT) not create the credit account or generate a journal batch for import?

Answer:

After interfacing costs to the General Ledger (GL), you try to run the Journal Import process (GLLEZL) within GL. However, the List of Values for the Group ID displays no values for the source Projects. Verify the Implementation Options have been set to interface costs to GL. To do this:

  1. Log into the Application using your Projects Responsibility.
  2. Navigate to Setup > System > Implementation Options.
  3. Set the options that control whether you want to interface the costs and revenue to GL as follows:
    • Interface Labor Costs to GL: Y
    • Interface Usage Costs to GL: Y
    • Interface Revenue to GL: Y

    If these options are set to N or are blank, then the PRC: Interface Costs to General Ledger (Labor, Revenue, or Usage) processes will mark the rows as Accepted, but will not create rows in the GL interface table. The GROUP_ID will therefore not display any values when you try to run the Journal Import process in General Ledger.

    These options also control whether costs and revenue are interfaced to GL in Release 12.

 

Note:  You should run the interface to GL processes, even when these options are set to N, so that the rows are marked as processed.

 

Q7. In 11i, why does the PRC: Interface Labor Costs to GL (PAGGLT) process fail with a Signal 11 error?

Answer:

You need to ensure all the parameters that you are using in AutoAccounting (AA) are valid parameters for use by the rules and functions. To do this:

  1. Log into the Application using your Projects Responsibility.
  2. Navigate to Other -> Request -> Run.
  3. Select the IMP: AutoAccounting Functions (PAXAAFTP) process.
  4. Choose the function in question, such as the Labor Cost Clearing Account function, to get a list of the valid parameters for the function.
  5. If you leave the function parameter blank when running this report it will list all the valid parameters for each function that is used in Project Accounting.

For example, if you were to choose the Labor Cost Clearing Account function, and run the report, this would show you that there are seven parameters (copied below) that are valid to use with this AutoAccounting function. You may only use one of these seven in rules that will be assigned to this function. If you were using a parameter that is not included on the list below, you would receive the Signal 11 error message.

Project Organization
Project Organization ID>br> Task Organization
Task Organization ID
Expenditure Organization
Expenditure Organization ID
Expenditure Item ID

When you create a rule, there is no validation of the parameters that you enter. This is because there is no way to know which function a particular user intends to assign to the rule. Therefore, the list of values will always display all parameters, whether or not they are valid for a particular function.

You must consult the output of the IMP: AutoAccounting Functions report when designing AutoAccounting rules for a particular function to insure that you only use parameters valid for that function.

 

Q8. How does Oracle Projects determine PA or GL Date and PA or GL Period for expenditure items?

Answer:

These dates are derived differently depending on how you have configured your system.  You should review the section “Financial Periods and Date Processing for Financial Accounting” in the Oracle Projects Fundamentals guide for full details of how these dates are derived in each case. You may be using any one of the three options below:

  • Period-end date accounting:  PA: Enable Enhanced Period Processing profile option is set to “No”.  In this case for all types of costs except supplier invoices, the PA Date is the end date of the first open or future period which includes or follows the expenditure item date, and the GL date is the end date of the first open or future GL period which includes or follows the GL date.
  • Expenditure item date accounting: PA: Enable Enhanced Period Processing profile option is set to “Yes”, but the Maintain Common PA and GL Periods implementation option is disabled.  In this case the PA date for all but supplier invoice costs will be the expenditure item date, if that falls in an open PA period, or if not, the first date of the next open or future PA period.  The GL date, similarly, will be the expenditure item date if that falls in an open GL period, otherwise it will be the first date of the next open or future GL period.
  • Expenditure item date accounting with common accounting periods: PA: Enable Enhanced Period Processing profile is set to “Yes” and Maintain Common PA and GL Periods implementation option is enabled.  In this case expenditure item date accounting logic above is used to determine the GL date, and the PA date is copied from the GL Date.

 

Q9. When should you run the tieback process for costs?

Answer:

In 11i, after you interface cost and revenue information to the General Ledger interface table and run the Journal Import program, you tieback cost and revenue items to Oracle Projects to ensure that all items are successfully loaded into Oracle General Ledger. If any items are rejected, you can correct them in Oracle Projects and interface them again to Oracle General Ledger.

In Release 12, with the update of Subledger Accounting (SLA) these processes have changed.  In Release 12, you first generate accounting events, and then run PRC: Create Accounting.  The create accounting program allows you to specify if your data should be interfaced to GL and posted in GL as well.  There is no longer a separate tieback program that needs to be run.

 

Q10. Why are journal entries not created in GL when costs are successfully interfaced to GL?

Answer:

In 11i, after interfacing costs to GL, Journal Import has to be run to create the journal entries.  In Release 12 you need to make sure that the “Transfer to General Ledger” parameter is set to “Yes” when running PRC: Create Accounting.

 

Q11. In 11i, why do the Projects General Ledger Interface Audit Reports produce no data?

Answer:

Ensure that journal import in General Ledger is done in detail and not in summarized journals. It is required when importing PA data to General Ledger that the “Create Summary Journals” option not be selected.  If this option is selected, the link between the journal entries and the detail information in Projects will be lost.  Only PA transactions imported in detail to the GL will show on these reports.

 

Q12. How do you correct APP-00969 errors in costing processes?

Answer:

In the debug log file, you’ll see the following errors:

APP-00969; Program was terminated by signal 11
PA_AA_INVLD_SQL_PARAM|RULE|user defined rule name

or

PA_AA_NO_RULE_PARAM_|RULE|user defined rule name

When you create an AutoAccounting rule, there is no validation of the parameters that you enter. You need to make sure that all the parameters that you are using in AutoAccouting are valid for the assigned functions as defined in the report IMP: AutoAccounting Functions. Run the report IMP: AutoAccounting Functions, and choose the function that you are having trouble with (eg “Labor Cost Clearing Account” function). When running this report, you may leave the function parameter blank. This will show you valid parameters for all the functions that are used in Projects.

 

Q13. Does dynamic insertion have to be ‘on’ for the accounting flexfield when distributing or interfacing costs to GL?

Answer:

Up until 11i.PJ_PF.M RUP 4, Oracle Projects required that Dynamic Insertion to be turned on so that non-existent code combination ID’s could be created as needed.  This requirement has since been removed.  In the following versions the requirement is no longer required:

  • Release 11i:  PJ_PF.M RUP 4 or above
  • Release 12.0: 12.0.3 or above
  • Release 12.1.X

 

Q14. How does the streamline process work?

Answer:

You can interface costs and revenue to Oracle General Ledger using Oracle Projects streamline processes. When you use a streamline process, you submit ONE request that optionally distributes then interfaces costs or revenue to Oracle General Ledger.  Like a request set the streamline process will sequentially submit all of the processes required to complete the interface flow.  In 11i it will transfer, import, and tieback the transactions.  In Release 12 it will  generate accounting events, create accounting, import and post the transactions to GL, and update subledger accounting balances.

 

Q15. Why are summarized burden transaction are not transferred to GL after running the PRC: Interface Total Burdened Costs to General Ledger?

Answer:

PRC: Interface Total Burdened Costs to GL will only pick up burdened transactions created by running PRC: Distribute Total Burdened Costs. Summarized burden transactions can be interfaced to GL by running the process PRC: Interface Usages and Miscellaneous Costs to GL.

 

Q16.  How do you correct “profile PA_SELECTIVE_FLEXFIELD_SEGMENT is not defined” or “APP-00606 Cannot read value for profile option PA_SELECTIVE_FLEX_SEG” messages?

Answer:

The profile option PA:Selective Flexfield Segment for Autoaccounting should be set at the application level. This should be set to one of the segments from the General Ledger Accounting Flexfields.  It should be set to the two digit number of the segment which contains the most distinct values (normally the natural account segment).

For example, if your account flexfield is set up as follows:

Company-Cost Center-Account

and there are 4 companies, 22 cost centers, and 370 accounts, then the third (account) segment is the most selective and the value “03” should be placed in the field for the profile option.

Leave a Reply