You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: apps/docs/content/docs/integrations/oracle_fusion_hcm.mdx
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,8 @@ Salary creation and correction support **user-entered salary bases only**. Creat
47
47
48
48
Payroll run-result values, balance slots, and goal completion percentages remain their documented strings. Balance `value1`–`value10`, definition IDs, and context/dimension labels are preserved without inventing net-pay or year-to-date meanings.
49
49
50
+
When updating an element input value, supply its text value or explicitly enable `clearScreenEntryValue`. Clearing writes Oracle's documented null value; a missing value alone never clears it. Direct execution also accepts an explicit null. The clear flag follows the established integration pattern for model interfaces that cannot express nullable scalar parameters.
51
+
50
52
Operation contracts: [assigned payroll creation](https://docs.oracle.com/en/cloud/saas/human-resources/farws/op-payrollrelationships-payrollrelationshipsuniqid-child-payrollassignments-payrollassignmentsuniqid-child-assignedpayrolls-post.html), [element entry creation](https://docs.oracle.com/en/cloud/saas/human-resources/farws/op-elemententries-post.html), [salary creation](https://docs.oracle.com/en/cloud/saas/human-resources/farws/op-salaries-post.html), [salary correction](https://docs.oracle.com/en/cloud/saas/human-resources/farws/op-salaries-salaryid-patch.html), and [salary bases](https://docs.oracle.com/en/cloud/saas/human-resources/farws/op-salarybasislov-get.html). Required fields follow the formal operation schemas even where abbreviated examples omit them.
51
53
52
54
## Talent and performance
@@ -670,7 +672,8 @@ Update Element Entry Value using documented Oracle fields. Requires administrati
670
672
|`elementEntryValueId`| string | Yes | Element entry value ID, as a positive decimal string |
671
673
|`effectiveDate`| string | Yes | Effective date in YYYY-MM-DD format |
672
674
|`rangeMode`| string | Yes | CORRECTION changes the historical row; UPDATE starts an effective-dated change |
673
-
|`screenEntryValue`| string | No | Element input value as text, preserving decimal precision; null clears a nullable value |
675
+
|`screenEntryValue`| string | No | Element input value as text, preserving decimal precision. To clear it, use clearScreenEntryValue. Direct execution also accepts explicit null. |
676
+
|`clearScreenEntryValue`| boolean | No | Explicitly clear the element input value; omit screenEntryValue when true |
entryType: {type: 'string',description: 'Oracle element-entry type code supported by the tenant'},
1846
1926
entryValues: {type: 'json',description: 'Up to 100 typed objects: inputValueId (positive decimal string) and screenEntryValue (string up to 60 characters or null). Input IDs serialize exactly as JSON integers'},
1847
1927
elementEntryValueId: {type: 'string',description: 'Element entry value ID, as a positive decimal string'},
1848
-
screenEntryValue: {type: 'string',description: 'Element input value as text, preserving decimal precision; null clears a nullable value'},
1928
+
screenEntryValue: {
1929
+
type: 'string',
1930
+
description: 'Element input value as text; use clearScreenEntryValue to explicitly clear it',
1931
+
},
1932
+
clearScreenEntryValue: {type: 'boolean',description: 'Explicitly clear the element input value'},
1849
1933
objectActionId: {type: 'string',description: 'Object action ID, as a positive decimal string'},
1850
1934
salaryId: {type: 'string',description: 'Salary ID, as a positive decimal string'},
1851
1935
salaryBasisId: {type: 'string',description: 'Salary basis ID, as a positive decimal string'},
0 commit comments