Previous  Next          Contents  Index  Navigation  Glossary  Library

Frequently Asked Questions

What Does the CreateRelatedItem Procedure Do?

This procedure does the following:

What Happens if the Source Transaction is Not Costed?

If the source transaction is not costed because it is rejected during cost distribution, the labor transaction extension is not called for that transaction. Therefore, related transactions for rejected source transactions will not be created or costed.

Can I Create Multiple Related Transactions for a Single Item?

Yes, you can create multiple related transactions for a given source transaction based on the logic in your labor transaction extension.

How Do I Identify Related Transactions?

You identify related transactions by referring to the expenditure item id of the source transaction.

In the expenditure inquiry forms and reports within Oracle Projects, you can identify related transactions based on your implementation data used for related transactions, particularly the expenditure type. Oracle Projects displays all related transactions immediately after the source transaction.

What if Some Parameters Are Not Passed to CreateRelatedItem?

All parameters that are not passed to the related transactions procedure are read from the source transaction; except for quantity, billable status, and expenditure type. The quantity is set to 0 for the related transactions. The billable status is derived based on the transaction controls and transaction control extensions that you define. Expenditure type is a required parameter that you provide.

What if a Related Transactions Does Not Pass Validation?

If a related transaction does not pass validation in the CreateRelatedItem procedure, Oracle Projects does not create the related item, and marks the source transaction with a cost distribution rejection reason specifying that an error was encountered in the labor transaction extension procedure. The source item is not marked as cost distributed and is displayed in the exception output report in the Distribute Labor Costs process.

Where Can I Establish the Billable or Capitalizable Status of Related Transactions?

The related transaction's billable or capitalizable status is derived using transaction controls and task billable or capitalizable status like all other transactions. You can further derive the billable or capitalizable status of related transactions by including logic in the transaction control extension procedure to look at related transactions based on certain criteria, and then setting the billable or capitalizable flag. The transaction control package, which establishes the billable or capitalizable status, is called within the CreateRelatedItem procedure.

How Does the Transaction Controls Procedure Identify Related Transactions?

The transaction control procedure, which establishes the billable or capitalizable status and validates transactions, is called within the CreateRelatedItem procedure.

The transaction control extension identifies related transactions by the x_module of the CreateRelatedItem procedure. When the calling procedure (CreateRelatedItems) calls transaction controls, the x_module is set to CreateRelatedItem.

Can I Calculate Raw Cost Amounts of Related Transactions Using Burden Costing?

You can use the Cost Plus API to determine raw cost amounts of related transactions based on your burden costing setup.

See Also

Cost Plus Application Programming Interface (API)


         Previous  Next          Contents  Index  Navigation  Glossary  Library