The interface table that contains data for sublines from Non-Oracle sources is the PSP_DISTRIBUTION_INTERFACE table. Table 1, describes the various fields in this table and their data types.
| NAME | NULL? | DATA TYPE |
|---|---|---|
| DISTRIBUTION_INTERFACE_ID | NOT NULL | NUMBER(10) |
| PAYROLL_ID | NOT NULL | NUMBER(9) |
| TIME_PERIOD_ID | NOT NULL | NUMBER(9) |
| PERSON_ID | NOT NULL | NUMBER(9) |
| ASSIGNMENT_ID | NOT NULL | NUMBER(9) |
| ELEMENT_TYPE_ID | NOT NULL | NUMBER(9) |
| DISTRIBUTION_AMOUNT | NOT NULL | NUMBER |
| DISTRIBUTION_DATE | NOT NULL | DATE |
| SOURCE_CODE | NOT NULL | VARCHAR2(30) |
| GL_CODE_COMBINATION_ID | NUMBER(15) | |
| PROJECT_ID | NUMBER(15) | |
| EXPENDITURE_ORGANIZATION_ID | NUMBER(15) | |
| EXPENDITURE_TYPE | VARCHAR2(30) | |
| TASK_ID | NUMBER(15) | |
| AWARD_ID | NUMBER(15) | |
| DR_CR_FLAG | NOT NULL | VARCHAR2(1) |
| STATUS_CODE | NOT NULL | VARCHAR2(1) |
| BATCH_NAME | NOT NULL | VARCHAR2(30) |
| ERROR_CODE | VARCHAR2(30) | |
| ATTRIBUTE_CATEGORY | VARCHAR2(30) | |
| ATTRIBUTE1 | VARCHAR2(150) | |
| ATTRIBUTE2 | VARCHAR2(150) | |
| ATTRIBUTE15 | VARCHAR2(150) | |
| LAST_UPDATE_DATE | NOT NULL | DATE |
| LAST_UPDATED_BY | NOT NULL | NUMBER(15) |
| LAST_UPDATE_LOGIN | NOT NULL | NUMBER(15) |
| CREATED_BY | NOT NULL | NUMBER(15) |
| CREATION_DATE | NOT NULL | DATE |
| GL_POSTING_OVERRIDE_DATE | DATE | |
| GMS_POSTING_OVERRIDE_DATE | NOT CURRENTLY USED |
This section describes the validation checks that Labor Distribution performs when it validates and imports data from the interface tables. When you write programs to load the interface table, you must ensure that the data you enter complies with the rules. If there is invalid data in the interface table, then Labor Distribution detects traps the errors and enables you to correct the errors using the Maintenance of Pre-Generated Distribution Lines window.
Table 2 describes the validation checks Labor Distribution performs before it imports data.
| Validation Name | Description |
|---|---|
| 1. BATCH_NAME | The application imports pre-generated distribution lines from non-Oracle sources into Labor Distribution based on the batches in which you loaded them into the interface table. Ensure that the batch names in the interface table are unique. Ensure that you do not reuse the batch names even after you load the batches into Labor Distribution and you remove the data you transferred from the interface table. |
| 2. DISTRIBUTION_INTERFACE_ID | The DISTRIBUTION_INTERFACE_ID identifies records within any batch. The loader program uses a sequence that the application creates during the Labor Distribution installation process. The sequence that the loader program uses for this purpose is PSP_PAYROLL_INTERFACE_S. |
| 3. DISTRIBUTION_DATE | The application uses the DISTRIBUTION _DATE field when it posts a transaction to Oracle Grants Accounting, Oracle Projects, or Oracle General Ledger. You can use this date field to check the validity of a number of other fields. |
| 4. PERSON_ID | The PERSON_ID field refers to the person for whom the subline is created. The PERSON_ID must be a valid ID in Oracle Human Resource Management Systems for an active employee for the effective date specified in the record. The person is defined in the PER_PEOPLE_F table. |
| 5. ASSIGNMENT_ID | The ASSIGNMENT_ID field must be a valid assignment for the PERSON_ID specified in the record. The field must also be defined in Human Resource Management Systems. The assignment is defined in the PER_ASSIGNMENTS_F table. |
| 6. PAYROLL_ID | The PAYROLL_ID field must refer to a valid payroll cycle name in Human Resource Management Systems. When there is a complete installation of Human Resource Management Systems, the payroll name referred to by this field must also be a valid payroll for the ASSIGNMENT_ID and EFFECTIVE_DATE specified by the record. The payroll is defined in the PAY_PAYROLLS_F table. |
| 7. TIME_PERIOD_ID | The TIME_PERIOD_ID field must refer to a valid payroll period in Human Resource Management Systems. The payroll period must be linked to the PAYROLL_ID on the effective date selected. The time period is defined in the PER_TIME_PERIODS table. |
| 8. ELEMENT_TYPE_ID | The ELEMENT_TYPE_ID field must refer to a valid element selected in the Elements Imported window in Labor Distribution. The elements selected in the setup window are valid element types in Human Resource Management Systems. The element type is defined in the PAY_ELEMENT_TYPES_F table. |
| 9. DISTRIBUTION_AMOUNT | DISTRIBUTION_AMOUNT is the amount that is to be paid to an employee over the subline date range specified. |
| 12. PAYROLL_SOURCE_CODE | The PAYROLL_SOURCE_CODE field must refer to a valid non-Oracle source as specified in the Payroll Sources window in Labor Distribution. |
| 13. DR_CR_FLAG | The DR_CR_FLAG field must contain either a D for debit amount or C for credit amount. |
| 14. GL_CODE_COMBINATION_ID | The GL_CODE_COMBINATION (GL_CCID) field must refer to a valid General Ledger account in General Ledger. This field can contain a value only if the PROJECT_ID, EXPENDITURE_ORGANIZATION_ID, EXPENDITURE_TYPE, TASK_ID, and AWARD_ID (POETA) fields are NULL. During validation and the import of sublines, Labor Distribution checks to ensure that GL_CCID and the POETA are mutually exclusive. |
| 15. PROJECT_ID | The PROJECT_ID field must refer to a valid project in Grants Accounting and Projects. Labor Distribution ensures that the PROJECT_ID field exists in the Grants Accounting view GMS_PROJECT_EXPEND_V. This field can contain a value only if the GL_CODE_COMBINATION_ID field does not. The PROJECT_ID field and the GL_CODE_COMBINATION_ID fields are mutually exclusive and Projects is implemented. The project is defined in the PA_PROJECTS table. |
| 16. EXPENDITURE_ORGANIZATION_ID | The EXPENDITURE_ORGANIZATION_ID field must refer to a valid Expenditure Organization in the Grants Accounting view PA_ORGANIZATIONS_EXPEND_V. This field can contain a value only if the GL_CODE_COMBINATION_ID field does not contain a value if Projects is implemented. The expenditure organization is define din the PA_ORGANIZATION_EXPEND_V table. |
| 17. GL_POSTING OVERRIDE_DATE | Date is to be specified if required to override this date to the Effective Date in PSP_DISTRIBUTION_LINES which is later transferred to the GL Accounts Interface. General Ledger override date for posting; if defined, this date overrides the distribution date for posting to General Ledger. |
| 18. GMS_POSTING_OVERRIDE_DATE | Not currently used |
| 19. EXPENDITURE_TYPE | The EXPENDITURE_TYPE field must be defined in Projects with an ST or STRAIGHT TIME system linkage function. If award is implemented, it must have an allowability schedule related to an award in Grants Accounting-allowable expenditures. This field can contain a value only if the GL_CODE_COMBINATION_ID field is not entered and Projects is implemented. The expenditure type is defined in the PA_EXPENDITURE_TYPES table. |
| 20. TASK_ID | The TASK_ID field must refer to a valid task in the Oracle Projects view PA_TASKS_EXPEND_V and must be linked to the project identified by the field PROJECT_ID. This field can contain a value only if the GL_CODE_COMBINATION_ID field does not contain a value and Projects is implemented. The task is defined in the PA_TASKS table. |
| 21. AWARD_ID | The AWARD_ID field must refer to a valid award in the Grants Management view GMS_AWARDS_BASIC_V. This field can contain a value only if the GL_CODE_COMBINATION_ID field does not contain a value and awards is implemented. The award is defined in the GMS_AWARDS table. |
| 22. ATTRIBUTE_CATEGORY, ATTRIBUTE1 through ATTRIBUTE15 | The attribute fields are designed for Descriptive Flexfields that are reserved for future use. |
| 23. LEDGER_ID | Ledger identifier |
| 24. BUSINESS_GROUP_ID | Business group identifier |
| 25. LAST_UPDATE_DATE | Standard Who column |
| 26. LAST_UPDATED_BY | Standard Who column |
| 27. LAST_UPDATE_LOGIN | Standard Who column |
| 28. CREATED_BY | Standard Who column |
| 29. CREATION_DATE | Standard Who column |
Caution: Oracle recommends that you do not populate columns in the interface table that this topic does not list. This is because the application uses those columns for internal calculations.