Error Project Information On The Distribution Is Not Valid
Contents |
items against predefined criteria and any transaction controls and transaction control client extensions that you set up during the implementation of Oracle Projects. The standard validation process performs the following checks: the expenditure organization is not active oracle Project Expenditure item falls within project dates Project status allows transactions Transaction controls and
A Project-level Expenditure Transaction Control Has Been Violated
transaction control extensions allow charges of this type Project allows cross-charges from the user's operating unit in a multi-organization environment Task system linkage function oracle projects Expenditure item falls within task dates Task is a lowest task Task is chargeable Transaction controls and transaction control extensions allow charges of this type Expenditure type Expenditure type is active Employee Employee is active the expenditure item date is not within the active dates of the project Existing expenditure item (for adjustments only) Matching expenditure item exists (unless you enter an unmatched, negative transaction) Oracle Projects may reject expenditure items for the predefined reasons listed below, whether the expenditure was created in Oracle Projects, Oracle Personal Time and Expense, other Oracle Applications, or an external cost collection system. If you receive a rejection reason not included in the list below, check with your implementation team for
The Expenditure Organization Is Not Active Otl
any rejection reasons specific to your company that were defined in transaction control extensions. Note: Oracle Projects validates pre-approved expenditure batches as you enter expenditure item details. Expenditures created using Oracle Personal Time and Expense and external cost collection systems are validated during the Submit and Transaction Import processes, but before Oracle Projects creates an expenditure. Rejection Reason (Error Lookup Code) Troubleshooting Tips Expenditure (timecards, expense reports, usage logs, etc.) You may receive the following rejection reasons when you use Transaction Import to import an expenditure. Burdened cost is not valid for the given system linkage (INVALID_BURDENED_AMOUNT) A transaction with an expenditure type class of Burden Transactions should have a burden cost of NULL. For other expenditure type classes, if the transaction source or project does not allow burdening, then they burden cost should equal zero. all CCID for credit is NULL (INVALID_CR_CCID) The code combination ID for the credit account cannot be NULL for transactions that have already been accounted for in an external system. GL accounted transactions CCID for debit is NULL (INVALID_DR_CCID) The code combination ID for the debit account cannot be NULL for transactions that have already been accounted for in an external system. GL accounted transactions Cannot lock original item for re
Costing - Version 12.1.1 to 12.1.3 [Release 12.1]Oracle Grants Accounting - Version 12.1.1 to 12.1.3 [Release 12.1]Oracle Project Management - Version 12.1.1 to 12.1.3 [Release 12.1]Information in this document applies to any invalid expenditure type and expenditure type class combination platform. Purpose In Release 12 new functionality was added to allow users the expenditure organization information is invalid various options in terms of how the expenditure item date is derived when matching an invoice to a project-related
Oracle Projects Technical Reference Manual
purchase order. This feature is controlled by the profile option "PA: Default expenditure Item date for supplier cost" (PA_AP_EI_DATE_DEFAULT). The possible settings are: SettingLookup Code Source Document Exp Item Date POTRNSDT Transaction https://docs.oracle.com/cd/A60725_05/html/comnls/us/pa/exp03.htm Date INVTRNSDT Transaction GL Date INVGLDT Transaction System Date INVSYSDT Two primary issues with the implentation of the feature have been: When the profile option is not set, or is set to an invalid value, supplier invoices created in Payables by matching to a project-related PO are created with a NULL expenditure item date (EXPENDITURE_ITEM_DATE). The original profile option definition created from pa120pc.ldt incorrectly http://oraclzfreesupport.blogspot.com/2013/12/troubleshooting-issues-resulting-from.html defined the List of Values (LOV) for the profile option. As a result, when the profile option was set by the user, the value being saved on the back end was the lookup meaning rather than the actual lookup code (e.g., the profile option value was stored as 'Transaction Date' rather than 'INVTRNSDT'). This naturally has resulted in many cases where the profile has been set to an invalid value, even though the correct user-visible value (e.g., 'Transaction Date') is displayed in the profile options form. When the value of the profile option is something other than "Source Document Exp Item Date", this can result in a change to the expenditure item date that was entered and validated on the PO. These validations were not being carried out on the new expenditure item date at the point of matching the invoice to the PO, which could result in invalid expenditure item dates being assigned on the invoice. These two issues result in missing or invalid expenditure item dates on project-related supplier invoices, and this condition can produce a wide array of symptoms, issues, and problems in both Payables an
Oracle Projects- Accounts Paya ... May 9, 2013 Sathish Oracle Projects - Accounts Payables/ Oracle Projects Integration 6 Comments PA - AP Flow: http://projectsaccounting.com/oracle-projects-accounts-payables/oracle-projects-accounts-payables-integration.html Payables to Project Costing video from our Oracle Projects Training http://life.us.sogeti.com/FAQ4.html Here iam considering the AP invoice integration with Oracle Projects. I will explain about the Expense Reports flow in another topic. This integration involves 2 sub processes given below: Interfacing Supplier Invoice From Oracle Payables To Oracle Projects Interfacing Supplier Invoice Adjustments is not From Oracle Projects To Oracle Payables - Only for 11i Interfacing Supplier Invoice From Oracle Payables To Oracle Projects: This process involves : Creating the invoice. Approve the invoice. Account for the invoice in payables. Run the ‘Interface Supplier Costs' process in Oracle Projects which interfaces the invoices from AP to PA. Interfacing the expenditure organization Supplier Invoice Adjustments From Oracle Projects To Oracle Payables: This process involves: Adjust the supplier invoice interfaced to Oracle Projects by either splitting the quantity or transferring an invoice from one project/task to another. Execute the PRC: Distribute Supplier Invoice Adjustment Costs process in Oracle Projects. Run the PRC: Interface Supplier Invoice Adjustment Costs to Payables process in Oracle Projects. Important Project Related Fields in AP: Project Name - Project Name to which the Invoice is accounted in Payables. Task Number - Task Number of the Project to which the invoice is accounted. Note: If the Task is not chargeable, the system displays the following error message: APP-PA-19270 The Task is Not Chargeable. The same error will be received if the Chargeable Flag is not checked while defining Tasks in Projects Setup or if the task is a Parent Task. Expenditures cannot be created at the Parent Task level. Expenditure Types - Expenditure Type of
Projects Pull up the required project Open the Tasks page (select tasks and click detail) Make sure that Tasks do not have Trans Finish Date.