HCM: The Regular/Temporary and Full Time/Part Time fields default to Regular and Full Time for all workers

 While migrating the workers we noticed that 'Regular or Temporary' and 'Full Time or Part Time' are getting auto populated with default values 'Regular' and 'Full Time' even though we are not passing the values for these fields.

These values are coming from the Position assigned and the reason is 'Position Synchronization Configuration'. 

Navigation: Setup and Maintenance > Search > Manage Enterprise HCM Information

Now the problem was, we were not even providing these values in the position load and system was still populating these fields with default values. This seems to be a bug.

The workaround is to pass the #null values to FullPartTime & RegularTemporary fileds in the position load file.

So to rectify the assignment records, you need to update the positions first and then run the ''Synchronize Person Assignments from Position". This process would only work if "Allow Override at Assignment' flag is unchecked. If it is also checked unfortunately you have to update the assignment records.

HCM: Default Number, Date & Time Format

 These default formats are controlled by profile options.

Navigation: Setup and Maintenance > Manage Administrator Profile Values

Profile Option Code:

Number: FND_NUMBER_FORMAT

Date     : FND_DATE_FORMAT

Time    : FND_TIME_FORMAT

You can set these options on Site or User level from the list of values available as required.

HCM: Workers Auto Numbering & Duplication Check

 Auto numbering and person duplicate check options are available under enterprise information. You can amend as required 

Navigation: Setup and Maintenance > Search > Manage Enterprise HCM Information

'Enterprise Information' Section

Options are self explanatory for both number generation and duplicate check. 

If you want to start the person number from a specific range you can provide that value in the 'Initial Person Number' filed.

HDL Error ORA-01000: maximum open cursors exceeded

While uploading large volume of data in Cloud/EBS you may encounter this error message. The solution is to increase the value set for open_cursors for the session.

It was easy to amend this value in EBS
ALTER system SET open_cursors = 1000 scope=both;

But in Cloud you do not have access to do so but you can try optimizing the HDL performance.
Increase the size of below parameters in the HCM Data Loader configurator.

Maximum Concurrent Threads for Load
Load Group Size

The recommended value for the number of threads is 8, and for say 50,000 records in a batch, a Chunk size of 500 could be used to give decent throughput.

Navigation> Setup and Maintenance > Configure HCM Data Loader

If it doesn't improve the performance please raise a service request with Oracle and they will increase the value for open_cursors parameter.

Ref: (Doc ID 2066732.1)

Defining New Source System Owner for HDL in Oracle Cloud

For HDL either you can use User Key or Source Key. To go with the source key, a source system owner must be defined. To do so, you need to add a new lookup code in the HRC_SOURCE_SYSTEM_OWNER lookup type.

Roles Required: "Application Implementation Consultant"
                            OR "Human Capital Management Application Administrator"

Use the Manage Common Lookups task in the ''Setup and Maintenance' work area under 'Other' 

Or 'Settings & Actions' window for your user and select  'Setup and Maintenance' under 'Administration

Now if know the functional area, search Task for 'Manage Common Lookups' 

or click on the little window to the right hand side and 'Search' for  'Manage Common Lookups'

> Search for the lookup type HRC_SOURCE_SYSTEM_OWNER. 

> In the Lookup Codes section of the page, click the New icon to add a new lookup-code
> Save & Close

select lookup_code
      ,meaning
      ,description
 from fnd_lookup_values
where upper(lookup_TYPE) ='HRC_SOURCE_SYSTEM_OWNER'
  and enabled_flag = 'Y'

'Java was started but returned exit code 1' Error

Please check the correct java version is installed and java environment is set correctly.

'java -version' in command prompt (cmd) will show you the java version installed
'where java' will show you the java location

Ensure proper version of JDK is installed, you can download JDK from here.

Set the JAVA_HOME environment variable.

Oracle SQL Developer - Increase size of GUI/Font

When you are running SQL Developer on Windows 10, you need to change the compatibility accordingly to get the proper GUI size.

With default compatibility mode 

Change the compatibility mode

1> Right Click on SQL Developer icon and select Properties.

     > Go to the Compatibility tab

     > Compatibility mode change it to windows 7

         > Check the option of Override high DPI scaling behaviour

         > Select "System" in drop down below

6> Apply 

Re-Launch the application