Parameters for Assignment Extensible and Descriptive Flexfields
Flexfield segments have list of values that are dependent on standard attributes. Assignment and work relationship attributes can be used as these objects:
-
Flexfield parameters for assignment and work relationship descriptive flexfields.
-
Input parameters when creating a value set for a flexfield segment.
You can use assignment attributes and descriptive flexfields as parameters when you configure assignment extensible flexfields (EFF) and assignment descriptive flexfields (DFF).
If you have configured the value set or default conditions using parameters for the EFF, these values will be reinitialized only when you navigate to the EFF field.
This table shows the parameters that you can use in the assignment EFF (PER_ASSIGNMENT_EIT_EFF) and assignment DFF (PER_ASG_DF):
Parameter Code |
Parameter Description |
Data Type |
Supported in DFF |
Supported in EFF |
---|---|---|---|---|
ACTION_CODE |
Action |
Varchar2 |
Yes |
Yes |
ASG_INFORMATON_DATE1 to ASG_INFORMATION_DATE15 ASG_INFORMATION_NUMBER1 to ASG_INFORMATION_NUMBER20 ASG_INFORMATION1 to ASG_INFORMATION50 ASG_INFORMATION_CATEGORY |
Legislative flexfields |
Date Number Varchar2 Varchar2 |
Yes |
Yes |
ASS_ATTRIBUTE_DATE1 to ASS_ATTRIBUTE_DATE15 ASS_ATTRIBUTE_NUMBER1 to ASS_ATTRIBUTE_NUMBER20 ASS_ATTRIBUTE1 to ASS_ATTRIBUTE50 ASS_ATTRIBUTE_CATEGORY |
Customer flexfields |
Date Number Varchar2 Varchar2 |
Yes |
Yes |
ASSIGNMENT_ID |
Assignment identifier |
Number |
Yes |
Yes |
ASSIGNMENT_STATUS_TYPE |
Assignment status type |
Varchar2 |
Yes |
Yes |
ASSIGNMENT_STATUS_TYPE_ID |
Assignment status type identifier |
Number |
Yes |
Yes |
ASSIGNMENT_TYPE |
Assignment type |
Varchar2 |
Yes |
Yes |
BARGAINING_UNIT_CODE |
Bargaining unit code |
Varchar2 |
Yes |
Yes |
BUSINESS_UNIT_ID |
Business unit identifier |
Number |
Yes |
Yes |
COLLECTIVE_AGREEMENT_ID |
Collective agreement identifier |
Number |
Yes |
Yes |
CONTRACT_ID |
Contract identifier |
Number |
Yes |
Yes |
EFFECTIVE_END_DATE |
Effective end date |
Date |
Yes |
Yes |
EFFECTIVE_START_DATE |
Effective start date |
Date |
Yes |
Yes |
EMPLOYEE_CATEGORY |
Worker category |
Varchar2 |
Yes |
Yes |
EMPLOYMENT_CATEGORY |
Assignment category |
Varchar2 |
Yes |
Yes |
ESTABLISHMENT_ID |
Reporting establishment |
Varchar2 |
Yes |
Yes |
EXPENSE_CHECK_ADDRESS |
Expense check send-to address |
Varchar2 |
Yes |
Yes |
FULL_PART_TIME |
Full time or part time |
Varchar2 |
Yes |
Yes |
GRADE_ID |
Grade |
Number |
Yes |
Yes |
GRADE_LADDER_PGM_ID |
Grade ladder |
Number |
Yes |
Yes |
GSP_ELIGIBILITY_FLAG |
Include in grade step progression |
Varchar2 |
Yes |
Yes |
HOURLY_SALARIED_CODE |
Hourly paid or salaried |
Varchar2 |
Yes |
Yes |
JOB_ID |
Job |
Number |
Yes |
Yes |
LABOUR_UNION_MEMBER_FLAG |
Union member |
Varchar2 |
Yes |
Yes |
LEGAL_ENTITY_ID |
Legal employer |
Number |
Yes |
Yes |
LEGISLATION_CODE_VALUE |
Legislation code value |
Varchar2 |
Yes |
Yes |
LOCATION_ID |
Location |
Number |
Yes |
Yes |
MANAGER_FLAG |
Working as a manager |
Varchar2 |
Yes |
Yes |
ORGANIZATION_ID |
Organization |
Number |
Yes |
Yes |
PERIOD_OF_SERVICE_ID |
Period of service identifier |
Number |
Yes |
Yes |
PERMANENT_TEMPORARY_FLAG |
Regular or temporary |
Varchar2 |
Yes |
Yes |
PERSON_ID |
Person |
Number |
Yes |
Yes |
PERSON_TYPE_ID |
Person type |
Number |
Yes |
Yes |
POSITION_ID |
Position identifier |
Number |
Yes |
Yes |
POSITION_OVERRIDE_FLAG |
Synchronize from position option |
Varchar2 |
Yes |
Yes |
PRIMARY_ASSIGNMENT_FLAG |
Primary assignment option |
Varchar2 |
Yes |
Yes |
PRIMARY_FLAG |
Primary option |
Varchar2 |
Yes |
Yes |
PRIMARY_WORK_RELATION_FLAG |
Primary work relationship indicator |
Varchar2 |
Yes |
Yes |
PROPOSED_WORKER_TYPE |
Proposed person type |
Varchar2 |
Yes |
Yes |
REASON_CODE |
Action reason |
Varchar2 |
Yes |
Yes |
SENIORITY_BASIS |
Basis for seniority calculation |
Varchar2 |
Yes |
Yes |
SET_OF_BOOKS_ID |
Set of books identifier |
Number |
Yes |
Yes |
SOURCE_ASSIGNMENT_ID |
Source assignment identifier |
Number |
Yes |
Yes |
SYSTEM_EFFECTIVE_DATE |
System effective date |
Date |
Yes |
Yes |
SYSTEM_PERSON_TYPE |
Worker type |
Varchar2 |
Yes |
Yes |
UNION_ID |
Union |
Number |
Yes |
Yes |
WORK_AT_HOME |
Working at home |
Varchar2 |
Yes |
Yes |
You can't use Contract ID as a parameter in Assignment DFF and Assignment EFF in these flows:
- Create flows, such as Hire an Employee, Add a Contingent Worker, Add a Pending Worker, and Add a Nonworker
- Local and Global Transfer (Global Transfer and Global Temporary Assignment)
- Create Work Relationship
- Add Assignment
This table shows the parameters that you can use in the work relationship DFF (PER_PPS_DF):
Parameter Code |
Parameter Description |
Data Type |
---|---|---|
DATE_START |
Start date |
Date |
LEGAL_ENTITY_ID |
Legal entity identifier |
Number |
LEGISLATION_CODE |
Legislation |
Varchar2 |
PERIOD_OF_SERVICE_ID |
Period of service identifier |
Number |
PERIOD_TYPE |
Period type |
Varchar2 |
PERSON_ID |
Person identifier |
Number |
PRIMARY_FLAG |
Primary indicator |
Varchar2 |
Using Attribute Values for Value Sets
You can use the assignment or work relationship attributes as input parameters when you create a value set by selecting the table validation type. The following is the syntax that you can use for the WHERE Clause field:
FIELD NAME = :{PARAMETER.<parameter name>}
For example, JOB_ID = :{PARAMETER.JOB_ID} and COUNTRY_CODE = :{PARAMETER.LEGISLATION_CODE}
You can use the following syntax when using flexfield segments:
Flexfield Segment = :{SEGMENT.<flexfield segment code>}
For example, if PayGroup is a segment code, you can use paam.ASS_ATTRIBUTE6= :{SEGMENT.PayGroup}