Dynamic database items are created by Oracle HRMS processes whenever you define new elements or other related entities.
When you define a new element, Oracle HRMS runs a process to create a number of related database items for it. To ensure easy recognition of these items, the process adds the element name <ENAME> to each one. It also creates further database items for each pay and input value you use <INAME>.
Here is a list of database items created each time you define an element using the Element window:
| Database item | Description |
|---|---|
| <ENAME>_BEN_CLASS | The element's benefit classification |
| <ENAME>_CLASSIFICATION | The element's classification |
| <ENAME>_CLOSED_FOR_ENTRY | Yes/no flag: translated into local language. If Yes, new element entries cannot be created but existing element entries can still be modified. |
| <ENAME>_CLOSED_FOR_ENTRY_CODE | Yes/no flag: If Yes, new element entries cannot be created but existing element entries can still be modified. |
| <ENAME>_COSTABLE_TYPE | The element's costable type (from lookup table) |
| <ENAME>_COSTABLE_TYPE_CODE | The element's costable type (code values) |
| <ENAME>_COUNT | The element entry count |
| <ENAME>_END_DATE | The date to which this element is effective |
| <ENAME>_INPUT_CURRENCY_CODE | The element's input currency code |
| <ENAME>_LENGTH_OF_SERVICE | The element's qualifying length of service |
| <ENAME>_OUTPUT_CURRENCY_CODE | The element's output currency code |
| <ENAME>_PROCESSING_PRIORITY | The element's processing priority |
| <ENAME>_QUALIFYING_AGE | The element's qualifying age |
| <ENAME>_QUALIFYING_UNITS_CODE | The qualifying length of service units (code values) |
| <ENAME>_QUALIFYING_UNITS | The qualifying length of service units (from lookup table) |
| <ENAME>_REPORTING_NAME | The element's reporting name |
| <ENAME>_STANDARD_LINK | Yes/no flag: yes = standard, no = discretionary |
| <ENAME>_STANDARD_LINK_CODE | Yes/no flag: yes = standard, no = discretionary |
| <ENAME>_<INAME>_UNIT_OF_MEASURE | The element's unit of measure (from lookup table) |
| <ENAME>_<INAME>_UNIT_OF_MEASURE_CODE | The element's unit of measure (code values) |
| <ENAME>_<INAME>_DEFAULT | The element's default input value |
| <ENAME>_<INAME>_MIN | The element's minimum input value |
| <ENAME>_<INAME>_MAX | The element's maximum input value |
In addition to the items above, Oracle HRMS creates the following four items for elements defined with multiple entries not allowed:
| Database item | Description |
|---|---|
| <ENAME>_<INAME>_ENTRY_VALUE | The element value |
| <ENAME>_<INAME>_USER_ENTERED_CODE | Whether a value exists at the element entry level (yes/no) |
| <ENAME>_<INAME>_START_DATE | The element's start date |
| <ENAME>_<INAME>_END_DATE | The element's end date |
In addition to the common list above, Oracle HRMS creates the following item for elements defined with multiple entries allowed whose input values are numeric (that is, hours, integer, money or number).
| Database item | Description |
|---|---|
| <ENAME>_<INAME>_ENTRY_VALUE | The summed element values for the multiple entries |
The units for '<ENAME> <INAME> ENTRY VALUE' are generated for both recurring and nonrecurring elements and are user-definable. Oracle HRMS modifies the definition text to retrieve the entry value in the unit of measure as specified in the PAY_INPUT_VALUES_F table.
When you define a grade rate, Oracle HRMS runs a process to create a number of related database items for it. To ensure easy recognition of these items, the process adds the grade rate name <NAME> to each one.
Here is a list of database items created each time you define a grade rate using the Grade Rate window:
| Database item | Description |
|---|---|
| GRADE_<NAME>_VALUE | The grade rate's value |
| GRADE_<NAME>_MINIMUM | The grade rate's minimum value |
| GRADE_<NAME>_MAXIMUM | The grade rate's maximum value |
When you define a pay scale rate, Oracle HRMS runs a process to create the following database item for it. To ensure easy recognition of this item, the process adds the rate name <NAME> to it.
| Database item | Description |
|---|---|
| SPINE_<NAME>_VALUE | The pay scale rates value |
When you define descriptive flexfield segments you make them available for use in QuickPaint by running the Create Descriptive Flexfield DB Items process from the Submit Requests window. This process creates database items for each of the descriptive flexfields listed below.
To ensure easy recognition of these items, the process adds the descriptive flexfield segment name <SEGMENT_NAME> to each one.
| Database item | Description |
|---|---|
| PEOPLE_<SEGMENT_NAME> | People descriptive flexfield database items |
| PAYROLLS_<SEGMENT_NAME> | Payroll descriptive flexfield database items |
| ASSIGNMENTS_<SEGMENT_NAME> | Assignment descriptive flexfield database items |
| GRADES_<SEGMENT_NAME> | Grade descriptive flexfield database items |
| ABSENCES_<SEGMENT_NAME> | Absence descriptive flexfield database items |
| ABSENCE_TYPES_<SEGMENT_NAME> | Absence Type descriptive flexfield database items |
| PERSON_ADDRESSES_<SEGMENT_NAME> | Person Address descriptive flexfield database items |
| EVENTS_<SEGMENT_NAME> | Events descriptive flexfield database items |
| JOBS_<SEGMENT_NAME> | Jobs descriptive flexfield database items |
| CONTACTS_<SEGMENT_NAME> | Contacts descriptive flexfield database items |
| PERIODS_OF_SERVICE_<SEGMENT_NAME> | Periods of Service descriptive flexfield database items |
| RECRUITMENT_ACTIVITIES_<SEGMENT_NAME> | Recruitment Activities descriptive flexfield database items |
| POSITION_<SEGMENT_NAME> | Position descriptive flexfield database items |
| APPLICATIONS_<SEGMENT_NAME | Applications descriptive flexfield database items |
| ORGANIZATION_<SEGMENT_NAME> | Organization descriptive flexfield database items |
When you define key flexfield segments you make them available for use in QuickPaint by running the Create Key Flexfield DB Items process from the Submit Requests window. This process creates database items for each of the key flexfields listed below.
To ensure easy recognition of these items, the process adds the key flexfield segment name <SEGMENT_NAME> to each one.
Run this process for each of your Business Groups. If you define context-dependent key flexfield structures using BUSINESS_GROUP_ID as the reference field, the process creates database items for those flexfield segments as well. BUSINESS_GROUP_ID is the only reference field that the Create Key Flexfield DB Items process supports.
| Database item | Description |
|---|---|
| COMP_KF_<SEGMENT_NAME> | Competence key flexfield database items |
| GRADE_KF_<SEGMENT_NAME> | Grade key flexfield database items |
| GROUP_KF_<SEGMENT_NAME> | Group key flexfield database items |
| JOB_KF_<SEGMENT_NAME> | Job key flexfield database items |
| POS_KF_<SEGMENT_NAME> | Position key flexfield database items |
| SCL_ASG_<LEGISLATION_CODE>_<ENAME> | Assignment soft coded legislative flexfield database items |
| SCL_ORG_<LEGISLATION_CODE>_<ENAME> | Organization soft coded legislative flexfield database items |
| SCL_PAY_<LEGISLATION_CODE>_<ENAME> | Payroll soft coded legislative flexfield database items |
When you define an absence type, Oracle HRMS runs a process to create the following database item for it. To ensure easy recognition of this item, the process adds the absence type name <ABSENCE_NAME> to it.
| Database item | Description |
|---|---|
| <ABSENCE_NAME>_CUM_BALANCE | The cumulative balance for an absence type |