Apps Common Descriptive Flexfields
Purpose
Provide a focused DFF setup-data route without owning CSV transport.
Read DFF setup-task guidance before
acting. Use shared.setup-export.task-level-export only for export and
core.data-loader only for approved FSM CSV import. For DFF metadata
deployment or deployment status, use only core.fusion-api.rest-api-client
as specified in the DFF reference.
Segment and Context Design
For a DFF context or global/context-sensitive segment create or update, read
defaulting rules and resolve only values the
user omitted. Show the supplied, derived, and still-pending values in a
user-visible DFF blueprint before preparing an FSM ZIP. Include ColumnName
(Table Column) for every global and context-sensitive segment, showing the
resolved column or its pending status and reason. Keep ShortPrompt out of the
user-visible blueprint as specified in the defaulting rules. Return the resolved
design and its provenance to the calling task workflow for project-workspace
persistence. A displayed default is a proposal subject to the validation and
approval gates below; it does not authorize a Fusion write.
Read mandatory validations before preparing an FSM ZIP
or handing a supplied ZIP to Data Loader. Validate the requested design against
the exact DFF task context, the current task-scoped export, and the candidate
package. When a segment has a value-set code, invoke
core.fusion-api.apps-common.value-sets for the live definition check described
there. Return each failed or unresolved check to the calling task workflow and
stop before import approval or deployment. These DFF checks supplement, and do
not replace, core.data-loader source validation and Task Hook approval.
DFF Deployment Workflow
Read the REST Deployment and Status section of
DFF setup-task guidance. Deployment
compiles the configured DFF; it is not a CSV import. After the Import DFF
Setup Data workflow has completed successfully, enter this workflow for the
imported DFF. Do not deploy after an incomplete or failed import.
- Preflight the confirmed target environment,
application_id, DFF
flexfield_code, optional force_deployment value ("true" or
"false"), and the caller's required Fusion privilege. When the calling
skill omits it, set forceDeployment to the documented default, "false".
Preserve URL encoding in the flexfield code; do not infer or substitute
identifiers.
- For a live deployment, present the exact target environment, POST endpoint,
and immutable JSON payload, then obtain explicit approval immediately before
invoking the REST client. Submit with
fusion_rest_client.py, using the
default Fusion scope for /fscmUI/applcoreApi.
- Capture
jobId, jobStatus, deploymentStatus, validationStatus,
validationReport, deploymentErrorMessage, and the response links. Do
not retry a POST without explicit approval.
- For status, call the documented
getDeploymentState GET endpoint through
the REST client using the same resolved identifiers. Poll only when asked,
using the bounded interval and timeout in the reference; stop at a terminal
response or timeout.
Preflight and Error Handling
Preflight task identity, catalog eligibility, artifact shape, target
environment, and required approval with the selected workflow. Classify an
unsupported task as catalog_or_metadata_mismatch and an unapproved import as
approval_blocker. Redact credentials, tokens, and sensitive setup data from
diagnostics.
For deployment, classify malformed identifiers or force values as
input_validation; a 401/403 after the REST client's one refresh attempt as
authorization_or_privilege; HTTP failures as fusion_api_error; and a
nonterminal result at the polling limit as process_timeout. Return the last
safe status and job ID to the calling project workflow; never persist OAuth
tokens, secrets, Authorization headers, or sensitive setup data.
1---2skill_id: "core.fusion-api.apps-common.descriptive-flexfields"3name: apps-common-descriptive-flexfields4description: "Resolves and validates Oracle Fusion Descriptive Flexfield context and segment designs, then routes task-level CSV export, approved Data Loader FSM CSV import, and approval-gated REST deployment status workflows."5layer: "core"6pillar: "Core"7type: "orchestration"8execution_mode: "hybrid"9owner_team: "Central platform team"10version: "0.5.0"11inputs: ["fusion_environment_context", "dff_task_context", "dff_segment_or_context_specification", "candidate_fsm_zip", "flexfield_deployment_context", "execution_options"]12outputs: ["resolved_dff_blueprint", "validation_result", "execution_result", "diagnostics", "audit_summary"]13depends_on: ["shared.setup-export.task-level-export", "core.data-loader", "core.fusion-api.rest-api-client", "core.fusion-api.apps-common.value-sets"]14uses_core: ["core.fusion-api.rest-api-client", "core.fusion-api.apps-common.value-sets"]15persists_project_state: false16workspace_outputs: []17applicability:18 industries: ["All"]19 countries: ["All"]20 fusion_releases: ["Current Oracle Fusion Cloud Applications release"]21side_effects: ["May read value-set definitions, export DFF setup data, submit an approved FSM CSV import, or submit an approval-gated DFF deployment request."]22required_privileges: ["Fusion privileges required by the selected setup-task export, Data Loader, and DFF deployment workflows"]23metadata:24 source: https://skillmd.com/skills/oracle/apps-common-descriptive-flexfields25---2627# Apps Common Descriptive Flexfields2829## Purpose3031Provide a focused DFF setup-data route without owning CSV transport.3233Read [DFF setup-task guidance](references/descriptive-flexfields.md) before34acting. Use `shared.setup-export.task-level-export` only for export and35`core.data-loader` only for approved FSM CSV import. For DFF metadata36deployment or deployment status, use only `core.fusion-api.rest-api-client`37as specified in the DFF reference.3839## Segment and Context Design4041For a DFF context or global/context-sensitive segment create or update, read42[defaulting rules](references/defaulting-rules.md) and resolve only values the43user omitted. Show the supplied, derived, and still-pending values in a44user-visible DFF blueprint before preparing an FSM ZIP. Include `ColumnName`45(Table Column) for every global and context-sensitive segment, showing the46resolved column or its pending status and reason. Keep `ShortPrompt` out of the47user-visible blueprint as specified in the defaulting rules. Return the resolved48design and its provenance to the calling task workflow for project-workspace49persistence. A displayed default is a proposal subject to the validation and50approval gates below; it does not authorize a Fusion write.5152Read [mandatory validations](references/validations.md) before preparing an FSM ZIP53or handing a supplied ZIP to Data Loader. Validate the requested design against54the exact DFF task context, the current task-scoped export, and the candidate55package. When a segment has a value-set code, invoke56`core.fusion-api.apps-common.value-sets` for the live definition check described57there. Return each failed or unresolved check to the calling task workflow and58stop before import approval or deployment. These DFF checks supplement, and do59not replace, `core.data-loader` source validation and Task Hook approval.6061## DFF Deployment Workflow6263Read the **REST Deployment and Status** section of64[DFF setup-task guidance](references/descriptive-flexfields.md). Deployment65compiles the configured DFF; it is not a CSV import. After the **Import DFF66Setup Data** workflow has completed successfully, enter this workflow for the67imported DFF. Do not deploy after an incomplete or failed import.68691. Preflight the confirmed target environment, `application_id`, DFF70 `flexfield_code`, optional `force_deployment` value (`"true"` or71 `"false"`), and the caller's required Fusion privilege. When the calling72 skill omits it, set `forceDeployment` to the documented default, `"false"`.73 Preserve URL encoding in the flexfield code; do not infer or substitute74 identifiers.752. For a live deployment, present the exact target environment, POST endpoint,76 and immutable JSON payload, then obtain explicit approval immediately before77 invoking the REST client. Submit with `fusion_rest_client.py`, using the78 default Fusion `scope` for `/fscmUI/applcoreApi`.793. Capture `jobId`, `jobStatus`, `deploymentStatus`, `validationStatus`,80 `validationReport`, `deploymentErrorMessage`, and the response links. Do81 not retry a POST without explicit approval.824. For status, call the documented `getDeploymentState` GET endpoint through83 the REST client using the same resolved identifiers. Poll only when asked,84 using the bounded interval and timeout in the reference; stop at a terminal85 response or timeout.8687## Preflight and Error Handling8889Preflight task identity, catalog eligibility, artifact shape, target90environment, and required approval with the selected workflow. Classify an91unsupported task as `catalog_or_metadata_mismatch` and an unapproved import as92`approval_blocker`. Redact credentials, tokens, and sensitive setup data from93diagnostics.9495For deployment, classify malformed identifiers or force values as96`input_validation`; a 401/403 after the REST client's one refresh attempt as97`authorization_or_privilege`; HTTP failures as `fusion_api_error`; and a98nonterminal result at the polling limit as `process_timeout`. Return the last99safe status and job ID to the calling project workflow; never persist OAuth100tokens, secrets, Authorization headers, or sensitive setup data.