|
|
|
|
|
|
|
|
|
| Previous | Next | Contents | Index | Navigation | Glossary | Library |
Do not import your data into columns marked System Assigned in the Comments column of the following table. Columns marked OPTIONAL are for optional transaction information that you can track if you want. VARCHAR2 columns are case sensitive. You can either load the table directly from your external system, or you can fill in some values using SQL*Plus.
Enter an implementation-defined transaction source code that classifies the transaction. This transaction source, along with the original transaction reference, identifies the source of transactions loaded into Oracle Projects from an external system. If a transaction source is defined as Costed, then a raw cost amount must exist for the transaction. If the transaction source is defined as Purgeable, the transaction will be purged from the table when the import process has completed. See: Transaction Sources.
Note: This column is for internal use only; you cannot view values stored in this column from any Oracle Projects windows. You must enter this internal code or a value in USER_TRANSACTION_SOURCE to specify the transaction source.
| Validation: | The transaction source you enter must be a valid transaction source. You can obtain a list of valid transaction sources from PA_TRANSACTION_ SOURCES.TRANSACTION_SOURCE. |
| Destination: | PA_EXPENDITURE_GROUPS_ALL. TRANSACTION_SOURCE and PA_EXPENDITURE_ITEMS.TRANSACTION_ SOURCE. The transaction source information is denormalized for performance optimization. |
| Validation: | The transaction source you enter must be a valid transaction source. You can obtain a list of valid transaction sources from PA_TRANSACTION_ USER.USER_TRANSACTION_SOURCE. Oracle Projects uses values from this table to derive the transaction source if you do not specify a value for the transaction source. |
| Destination: | None |
Enter a reference to the original item loaded into Oracle Projects from an external system via the Transaction Import program. Unless the transaction source allows duplicate references, this unique reference, along with the transaction source, identifies the source of the original transaction loaded into Oracle Projects from an external system.
| Validation: | An expenditure item must not already exist with the same identifier values as the transaction if the transaction source does not allow duplicate system reference values. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.ORIG_ TRANSACTION_REFERENCE |
The expenditure batch name within Oracle Projects is created as a concatenation of the batch name and expenditure type class entered in the transaction interface table and the interface ID. An expenditure batch is a group of expenditures loaded into the interface table; all transactions in this batch must have the same transaction source. The batch name is used to derive part of the expenditure batch name in Oracle Projects expenditure tables after import.
| Validation: | None |
| Destination: | PA_EXPENDITURE_GROUPS_ALL. EXPENDITURE_GROUP |
Enter the date of the last day of the expenditure week for this transaction. All transactions in an expenditure must be on or before the expenditure ending date. In addition, all timecard items must be within the expenditure week date range. The maximum expenditure ending date of all expenditure items processed in a batch becomes the expenditure batch ending date.
| Validation: | Valid week ending date based on the expenditure cycle start day defined in Implementation Options. |
| Destination: | PA_EXPENDITURES_ALL.EXPENDITURE_ ENDING_DATE |
Enter the number of the employee who incurred the charge for this transaction. This column must be populated for labor and expense report items, but is optional for other expenditure type classes.
| Validation: | Must be a valid employee number in PER_PEOPLE_F.EMPLOYEE_NUMBER |
| Destination: | PA_EXPENDITURES_ALL.INCURRED_BY_ PERSON_ID |
Enter the name of the organization that incurred the charge for this transaction. If employee number is provided, then this column can be null, in which case Transaction Import derives this value from the employee organization. If you provide both an employee and an organization, Oracle Projects uses the employee information to derive the organization. Transaction Import uses the last employee assignment in the expenditure period to derive the employee organization.
| Validation: | Must be a valid organization in PER_ORGANIZATION_UNITS.NAME |
| Destination: | PA_EXPENDITURES_ALL.INCURRED_BY_ ORGANIZATION_ID |
Enter the date on which this transaction occurred.
| Validation: | The expenditure item date must be on or before the expenditure ending date. Also, the expenditure item date of timecard items must fall within the expenditure week as defined by the expenditure ending date. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL. EXPENDITURE_ITEM_DATE |
Enter the number of the project this transaction is charged to.
| Validation: | Must be a valid project number in PA_PROJECTS.SEGMENT1 and PA_PROJECTS_EXPEND_V; project must have a project status that allows new transactions; project must not be a project template; and project must allow charges from your operating unit (if multiple organization support is enabled). |
| Destination: | None |
Enter the number of the task this transaction is charged to.
| Validation: | Must be a valid task number in PA_TASKS.TASK_NUMBER for the project number specified; and task must be a lowest task that allows charges. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.TASK_ID |
Enter the expenditure type that classifies the type of charge for this transaction.
| Validation: | This expenditure type must be a valid expenditure type in PA_EXPENDITURE_ TYPES.EXPENDITURE_TYPE. The expenditure type and expenditure type class combination must exist as an active combination in the PA_EXPEND_TYP_SYS_LINKS table. You cannot import expenditure items with a expenditure type class of Supplier Invoices. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL. EXPENDITURE_TYPE |
Enter the non-labor resource utilized for this transaction. This column is populated only for usage items.
| Validation: | This non-labor resource must be a valid non-labor resource in PA_NON_LABOR_ RESOURCES.NON_LABOR_RESOURCE and must be a resource classified by the specified expenditure type. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.NON_LABOR_ RESOURCE |
Enter the name of the organization owning the non-labor resource utilized for the transaction. This column is populated only for usage items.
| Validation: | Must be a valid non-labor resource owning organization in PA_NON_LABOR_RESOURCE_ ORGS.ORGANIZATION_ID for the specified non-labor resource. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL. ORGANIZATION_ID |
Enter the number of units for the transaction based on the unit of measure defined for the expenditure type.
| Validation: | None |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.QUANTITY |
Enter the total raw cost of the transaction.
| Validation: | If the transaction source is defined as Costed, a raw cost amount must exist. If transaction source is not Costed, this column value is ignored. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.RAW_COST |
Enter the raw cost rate for the costed transaction. Oracle Projects uses this information for reporting purposes only.
| Validation: | None |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.RAW_COST_ RATE |
Enter the burdened cost for transactions that meet either of the following criteria:
| Validation: | None |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.BURDEN_COST |
Enter the burdened cost multiplier for the burden transaction. Oracle Projects uses this information for reporting purposes only.
| Validation: | None |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.BURDEN_ COST_RATE |
If you are importing a transaction that has already been accounted for and interfaced to GL, enter the ID of the GL debit account. If you allow adjustments to these transactions, Oracle Projects uses this value to account for reversing, adjusting costs.
| Validation: | Must be a valid GL account in GL_CODE_COMBINATIONS |
| Destination: | PA_COST_DISTRIBUTION_LINES_ALL.DR_ CODE_COMBINATION_ID |
If you are importing a transaction that has already been accounted for and interfaced to GL, enter the ID of the GL credit account.
| Validation: | Must be a valid GL account in GL_CODE_COMBINATIONS |
| Destination: | PA_COST_DISTRIBUTION_LINES_ALL.CR_ CODE_COMBINATION_ID |
Enter the reference to the record in the external system if it has already been accounted for and interfaced to Oracle General Ledger. This information enables you to drill down to the transaction in the originating system.
| Validation: | None |
| Destination: | PA_COST_DISTRIBUTION_LINES_ALL.SYSTEM_REFERENCE1 |
Enter the reference to the record in the external system if it has already been accounted for and interfaced to Oracle General Ledger. This information enables you to drill down to the transaction in the originating system.
| Validation: | None |
| Destination: | PA_COST_DISTRIBUTION_LINES_ALL.SYSTEM_REFERENCE2 |
Enter the reference to the record in the external system if it has already been accounted for and interfaced to Oracle General Ledger. This information enables you to drill down to the transaction in the originating system.
| Validation: | None |
| Destination: | PA_COST_DISTRIBUTION_LINES_ALL.SYSTEM_REFERENCE3 |
Enter the GL date of the transaction if it has already been accounted for and interfaced to Oracle General Ledger. Oracle Projects uses this information for reporting purposes only.
| Validation: | If this column is null for an accounted transaction, then Transaction Import will reject the transaction. |
| Destination: | PA_COST_DISTRIBUTION_LINES_ALL.GL_ DATE |
Enter the expenditure type class of the given transaction. If the transaction has no expenditure type class, the default expenditure type class defined for the transaction source will be used. Oracle Projects stores this information at the expenditure item level and uses it to determine how to process the expenditure item.
| Validation: | Must be defined for the expenditure type. If this value is NULL, then the default system linkage (or expenditure type class) defined for the transaction source is used. |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.SYSTEM_ LINKAGE_FUNCTION |
Enter the description that you want to assign to the expenditure item created from this transaction.
| Validation: | None |
| Destination: | PA_EXPENDITURE_COMMENTS. EXPENDITURE_COMMENT |
You must set this value to P (pending) for transactions you want to import. Oracle Projects will set the value to A (accepted) after a transaction is successfully imported, or R (rejected) when an item is rejected during import.
If TRANSACTION_STATUS_CODE is set to A after Transaction Import completes, this indicates that the TRANSACTION_SOURCE entered is not defined as Purgeable, and you will need to delete the item manually. See: Transaction Sources.
If an item is rejected, the rejection reason code will be generated in the TRANSACTION_REJECTION_CODE column.
| Validation: | Lookup codes for this column are stored in the PA_LOOKUPS table under the lookup type of TRANSACTION STATUS. |
| Destination: | None |
This column is populated by a system-defined code indicating why the transaction was rejected by the Transaction Import program. For a list of codes, see: Resolving Import Exceptions.
| Validation: | This column is system assigned. Lookup codes for this column are stored in the PA_LOOKUPS table under the lookup type of TRANSACTION REJECTION REASON. |
| Destination: | None |
Enter the descriptive flexfield category for the descriptive flexfield information you want to import.
| Validation: | None |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.ATTRIBUTE_ CATEGORY |
Enter the descriptive flexfield information that you want to import for a transaction (expenditure item). The structure of the information you enter in these columns (datatypes, value sets) should match the structure of the descriptive flexfield segments you have defined for your transaction or you will experience validation problems when you try to access the information in the expenditure entry forms.
| Validation: | None |
| Destination: | PA_EXPENDITURE_ITEMS_ALL. ATTRIBUTE [1-10] |
Enter Y or N so that Transaction Import can identify summary-level adjustments (negative amounts) for which there is no single matching item to adjust. If this column is set to Y, Transaction Import will bypass the matching validation logic that is usually executed for adjustments (negative transactions). If this column is set to N, Oracle Projects finds the matching item and populates PA_EXPENDITURE_ITEMS_ALL.ADJUSTED.
| Validation: | None |
| Destination: | PA_EXPENDITURE_ITEMS_ALL.ADJUSTED (if column is set to N) |
| Validation: | Must be a valid organization ID defined in the following tables: PA_EXPENDITURE_GROUP_ALL.ORG_ID, PA_EXPENDITURES_ALL.ORG_ID, PA_EXPENDITURE_ITEMS_ALL.ORG_ID, and PA_COST_DISTRIBUTION_LINES_ALL.ORG_ID. |
| Destination: | None |
| Validation: | None |
| Destination: | None |
| Validation: | None |
| Destination: | None |
| Validation: | None |
| Destination: | None |
| Validation: | None |
| Destination: | None |
| Validation: | This column is system assigned. |
| Destination: | PA_EXPENDITURES_ALL.EXPENDITURE_ID |
| Validation: | This column is system assigned. |
| Destination: | PA_EXPENDITURES_ALL.EXPENDITURE_ ITEM_ID |
| Validation: | This column is system assigned. |
| Destination: | None |
| Validation: | This column is system assigned. |
| Destination: | None |
| Previous | Next | Contents | Index | Navigation | Glossary | Library |
