Apps Common Key Flexfields
Purpose
Manage KFF setup-data tasks routed from pillar setup-task skills without owning
CSV transport. Read KFF 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 KFF metadata
deployment or deployment status, use only core.fusion-api.rest-api-client
as specified in the KFF reference.
KFF Deployment Workflow
Read the REST Deployment and Status section of
KFF setup-task guidance. Deployment compiles
the configured KFF; it is not a CSV import. After the Import KFF Setup Data
workflow has completed successfully, enter this workflow for the imported KFF.
Do not deploy after an incomplete or failed import.
- Preflight the confirmed target environment,
application_id, KFF
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".
URL-encode reserved code characters (for example, GL# as GL%23) and do
not infer 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
Resolve task identity from the calling pillar skill, verify
ExportImportSupportedFlag, and preflight the selected workflow's target,
artifact, and approval requirements. 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.key-flexfields"3name: apps-common-key-flexfields4description: "Manages Oracle Fusion Key Flexfield setup data through 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.3.0"11inputs: ["fusion_environment_context", "kff_task_context", "flexfield_deployment_context", "execution_options"]12outputs: ["execution_result", "diagnostics", "audit_summary"]13depends_on: ["shared.setup-export.task-level-export", "core.data-loader", "core.fusion-api.rest-api-client"]14uses_core: ["core.fusion-api.rest-api-client"]15persists_project_state: false16workspace_outputs: []17applicability:18 industries: ["All"]19 countries: ["All"]20 fusion_releases: ["Current Oracle Fusion Cloud Applications release"]21side_effects: ["May export KFF setup data, submit an approved FSM CSV import, or submit an approval-gated KFF deployment request."]22required_privileges: ["Fusion privileges required by the selected setup-task export, Data Loader, and KFF deployment workflows"]23metadata:24 source: https://skillmd.com/skills/oracle/apps-common-key-flexfields25---2627# Apps Common Key Flexfields2829## Purpose3031Manage KFF setup-data tasks routed from pillar setup-task skills without owning32CSV transport. Read [KFF setup-task guidance](references/key-flexfields.md)33before acting.3435Use `shared.setup-export.task-level-export` only for export and36`core.data-loader` only for approved FSM CSV import. For KFF metadata37deployment or deployment status, use only `core.fusion-api.rest-api-client`38as specified in the KFF reference.3940## KFF Deployment Workflow4142Read the **REST Deployment and Status** section of43[KFF setup-task guidance](references/key-flexfields.md). Deployment compiles44the configured KFF; it is not a CSV import. After the **Import KFF Setup Data**45workflow has completed successfully, enter this workflow for the imported KFF.46Do not deploy after an incomplete or failed import.47481. Preflight the confirmed target environment, `application_id`, KFF49 `flexfield_code`, optional `force_deployment` value (`"true"` or50 `"false"`), and the caller's required Fusion privilege. When the calling51 skill omits it, set `forceDeployment` to the documented default, `"false"`.52 URL-encode reserved code characters (for example, `GL#` as `GL%23`) and do53 not infer identifiers.542. For a live deployment, present the exact target environment, POST endpoint,55 and immutable JSON payload, then obtain explicit approval immediately before56 invoking the REST client. Submit with `fusion_rest_client.py`, using the57 default Fusion `scope` for `/fscmUI/applcoreApi`.583. Capture `jobId`, `jobStatus`, `deploymentStatus`, `validationStatus`,59 `validationReport`, `deploymentErrorMessage`, and the response links. Do60 not retry a POST without explicit approval.614. For status, call the documented `getDeploymentState` GET endpoint through62 the REST client using the same resolved identifiers. Poll only when asked,63 using the bounded interval and timeout in the reference; stop at a terminal64 response or timeout.6566## Preflight and Error Handling6768Resolve task identity from the calling pillar skill, verify69`ExportImportSupportedFlag`, and preflight the selected workflow's target,70artifact, and approval requirements. Classify an unsupported task as71`catalog_or_metadata_mismatch` and an unapproved import as72`approval_blocker`. Redact credentials, tokens, and sensitive setup data from73diagnostics.7475For deployment, classify malformed identifiers or force values as76`input_validation`; a 401/403 after the REST client's one refresh attempt as77`authorization_or_privilege`; HTTP failures as `fusion_api_error`; and a78nonterminal result at the polling limit as `process_timeout`. Return the last79safe status and job ID to the calling project workflow; never persist OAuth80tokens, secrets, Authorization headers, or sensitive setup data.