ORACLE - FUSION : Common Lookup DFF Configuration.

 Following steps will let you know how to configure DFF's for common lookups and use them while configuring common lookups. 

Normal common lookups will let you configure lookup code and corresponding meaning.  If you want to configure additional values for a lookup code then you can use DFF's to configure context and use them in lookups. 

MANAGE DFF

• Login into Fusion. 
• Go to Manage and Setup 
• Search for Manage Descriptive Flexfields
• Search for Lookup values descriptive flexfield (Name)
• Edit - Lookup values descriptive flexfield
• Manage Contexts
• Search for existing contexts or Create a new one. 
• Create
• Give a display name  - XXSCM_SHOP_ORG_MAP_LOOKUP
• API Name - XxscmShopOrgMapLookup
• Save
• Under Context Sensitive Segments add segments - ( additional lookup values )
• Give a Name - Ex: Inventory_Organization
• Data Type as Character
• Table Column will auto populated - Attribute1
• Under Value Set : Either select an existing one or create new
• Create a New Value Set
• Value Set Code - XXSCM_INV_ORG_NAME
• Module - Inventory Management
• Validation Type : Table   -- This will allow us to define table, column and where clause. 
•  Under Definition 
• From Clause - Provide Table Name - INV_ORGANIZATION_DEFINITIONS_V
• Value Column Name - Provide Column Name - ORGANIZATION_CODE
• ID Column Name :  ORGANIZATION_ID
• WHERE Clause :  INVENTORY_ENABLED_FLAG = 'Y'
• Save 
• This will validate TABLE and Column Values. 
• Save and Close the value set
• Save and Close the Segment
• Follow the above steps to create a new segment for inventory.
• Save and Close the Context

MANAGE COMMON LOOKUP:

• Go to Manage and Setup 
• Search for Manage Common Lookups
• Add Common Lookup +
• Lookup Type : XXSCM_SHOP_ORG_LOOKUP
• Meaning : Give some valid meaning 
• Description : Give some value Description
• Module : Common
• REST Access Secured :  Authenticated. 
• Lookup Code
• Add 
• Lookup Code : Shop1
• Meaning : Give a Name
• Enable
• Expand the lookup code
• Select the context created earlier
• Select the Org 
• Select the Inventory

Oracle Fusion - User Creation or Migration and Role Provisioning

Oracle Fusion Users can be originated in Fusion Application where in users are created in Fusion (Security Console) or can be provisioned from identity providers like IDCS to Fusion Application. 

In case users are originating at IDCS and then provisioned or synced with Fusion Application then it is required  to setup SSO application in IDCS and enable User Sync from IDCS to FA. 

It is required to configure Auto Role Provisioning to all the users and assign Employee role or Contingent worker role to User.  It will assign a default role to user when an User account is created in Fusion. 

In case users are not assigned with any role and by chance if you run a seeded job - "Send Pending LDAP Request"  or if it gets kicked off due to some other sync job like Role Assignment then it will remove the users which are not assigned with any roles.  

"Send Pending LDAP Request" job will perform following tasks. 

• Create , Suspend and Reactivate User Accounts. 
• User create will be triggered when Person record is created for a Worker. 
• User will be suspended when roles are removed from a User. 
• User will be Reactivated when a User will be rehired. 

Note: These jobs will triggered when automatic user creation and management is enabled in Fusion. 

It is not required to run this Job if the user is created manually or synced from IDCS.  It is required only if we need to create user automatically using Employee records. 

Enable Auto Creation and Management :  FA > Setup and Maintenance > Manager Enterprise HCM Information > Edit and Set > User Account Creation as - Both Person and Party User. 

Automatic Role Provisioning >  FA > Setup and Maintenance > Manager Enterprise HCM Information > Edit and Set > User Account Role Provisioning as - Both Person and Party User. 

Provision Roles to  Users Automatically. 

• Login into FA
• Setup and Maintenance
• Tasks
• Search > Manage Role Provisioning Rules / Manager Role Mapping
• + Create
• Give a Mapping Name - Employee Prov
• Update Following Fields.  This will assign the roles to Active Employee
• System Person Type =  Employee
• HR Assignment Status = Active.
• Under Associated role
• + Add Row
• Role Name >  Search for a Role - Employee Role
• Add
• Select Auto Provision Option. 
• Save and Close. 
• Follow Above Steps for Contingent Worker.
• Add Mapping Name - Contingent Work
• System Person Type = Contingent Worker
• HR Assignment Status = Active
• Add Role 
• Select Contingent Worker Role
• Select Auto Provision Option. 
• Save and Close. 

When you schedule "Send Pending LDAP Request" it will perform Auto Role Provisioning. 

Simple Steps to Create an HCM Extract.

Steps to Create an HCM  Extract :

1. Login to HCM
2. Go to data exchange. 
3. In Tasks (Right menu), select Manage Extract Definition. 
4. Select create ( + )
5. Give a name to Extract.
6. Give Start Date value. 01-Jan-2000  
7. The Start date is an effective start date that applies to all date-effective interactions in the current session.
8. Select extract type
• HR Archive is for getting assignment and person details. 
• Payroll interface is for getting payroll related details.
9. Create Data Group
• Give Group Name. 
• Give Display  Name. 
• Select User Entity based on the data you want to extract.  
•  Example :
•  PER_EXT_SEC_ASSIGNMENT_UE     PER_EXT_EMAIL_ADDRESSES_UE
• set Threading Action Type = Object Action
• Select Threading Database Item - It will be the unique value of the Main table that will be used to join or get the values.
•   Example : Extract Assignment ID
10. Create a Record
• Give a Record Name.
• Give a Tag name - This value will be a XML tag (Parent Tag) value under which the attribute values will be coming.
• Select Type as Detail Record.
• Process Type as Fast Formula .
11. Create Attributes - Individual data elements. 
• Give a Name Value
• Give a XML tag value. 
• Short code 
• Output label value -- All these four values can be same. 
• Select type as DBI group. 
• Select the value 
•   Example :  Extract Assignment ID , Person Number , Person Name , etc. 
• Set KEy attribute for primary unique value. 
• Save. 
12. We can add the conditions at DG level to filter the data. 
13. Create Data group relationship under Data Groups.
•   Select the child DG.
•   select create option under connect DG.
•   Select the parent DG.
•   Select the Parent DBI Item  - Parent joining value.
•     Example - Extract Assignment Person ID
•   Select chile DBI - Child Joining element value
•     Example - Extract E-Mail Person ID
• We can add the filter at the group level or attribute level. 
14. Go to extract delivery
• Select add
• Provide a name for delivery option.
• Select an output type 
•   Ex : Text for a CSV and we need to attach a template. 
•    Data for XML out put and we dont need to attach a template. 
• Give an output file name. 
• Select delivery type as None.
• Save the changes. 
15. Go to extract execution tree Compile all formulas.
• Refreh and make sure all formulas are compiled. 
16. Submit Extract to run the extract.