Apps Common Extensible Flexfields
Purpose
Manage EFF setup-data tasks routed from pillar setup-task skills without owning
CSV transport. Read EFF 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 EFF metadata
deployment or deployment status, use only core.fusion-api.rest-api-client
as specified in the EFF reference.
EFF Deployment Workflow
Read the REST Deployment and Status section of
EFF setup-task guidance. It is separate
from CSV import: an EFF deployment compiles the already-configured flexfield;
it does not transport setup data. After the Import EFF Setup Data workflow
has completed successfully, enter this workflow for the imported EFF. Do not
deploy after an incomplete or failed import.
- Preflight the confirmed target environment,
application_id, EFF
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 (for example, %23); 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 the request with
fusion_rest_client.py,
which uses 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.
- Run a caller-supplied
post_deployment_action only after status confirms
DEPLOYED. Follow the Task-Specific Post-Deployment Action section of
the EFF reference. Do not infer, substitute, or run a post-deployment action
for a task that does not explicitly define one.
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.
For a caller-supplied post-deployment action, classify a missing successful
DEPLOYED status as process_failed, an unapproved POST as
approval_blocker, and an unsuccessful job result as process_failed.
Capture the response and any request identifier in post_deployment_result.
Do not retry the POST without a new explicit approval.
1---2skill_id: "core.fusion-api.apps-common.extensible-flexfields"3name: apps-common-extensible-flexfields4description: "Manages Oracle Fusion Extensible 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.1"11inputs: ["fusion_environment_context", "eff_task_context", "flexfield_deployment_context", "post_deployment_action", "execution_options"]12outputs: ["execution_result", "post_deployment_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 EFF setup data, submit an approved FSM CSV import, or submit an approval-gated EFF deployment request."]22required_privileges: ["Fusion privileges required by the selected setup-task export, Data Loader, and EFF deployment workflows"]23metadata:24 source: https://skillmd.com/skills/oracle/apps-common-extensible-flexfields25---2627# Apps Common Extensible Flexfields2829## Purpose3031Manage EFF setup-data tasks routed from pillar setup-task skills without owning32CSV transport. Read [EFF setup-task guidance](references/extensible-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 EFF metadata37deployment or deployment status, use only `core.fusion-api.rest-api-client`38as specified in the EFF reference.3940## EFF Deployment Workflow4142Read the **REST Deployment and Status** section of43[EFF setup-task guidance](references/extensible-flexfields.md). It is separate44from CSV import: an EFF deployment compiles the already-configured flexfield;45it does not transport setup data. After the **Import EFF Setup Data** workflow46has completed successfully, enter this workflow for the imported EFF. Do not47deploy after an incomplete or failed import.48491. Preflight the confirmed target environment, `application_id`, EFF50 `flexfield_code`, optional `force_deployment` value (`"true"` or51 `"false"`), and the caller's required Fusion privilege. When the calling52 skill omits it, set `forceDeployment` to the documented default, `"false"`.53 Preserve URL encoding in the flexfield code (for example, `%23`); do not54 infer or substitute identifiers.552. For a live deployment, present the exact target environment, POST endpoint,56 and immutable JSON payload, then obtain explicit approval immediately before57 invoking the REST client. Submit the request with `fusion_rest_client.py`,58 which uses the default Fusion `scope` for `/fscmUI/applcoreApi`.593. Capture `jobId`, `jobStatus`, `deploymentStatus`, `validationStatus`,60 `validationReport`, `deploymentErrorMessage`, and the response links. Do61 not retry a POST without explicit approval.624. For status, call the documented `getDeploymentState` GET endpoint through63 the REST client using the same resolved identifiers. Poll only when asked,64 using the bounded interval and timeout in the reference; stop at a terminal65 response or timeout.665. Run a caller-supplied `post_deployment_action` only after status confirms67 `DEPLOYED`. Follow the **Task-Specific Post-Deployment Action** section of68 the EFF reference. Do not infer, substitute, or run a post-deployment action69 for a task that does not explicitly define one.7071## Preflight and Error Handling7273Resolve task identity from the calling pillar skill, verify74`ExportImportSupportedFlag`, and preflight the selected workflow's target,75artifact, and approval requirements. Classify an unsupported task as76`catalog_or_metadata_mismatch` and an unapproved import as77`approval_blocker`. Redact credentials, tokens, and sensitive setup data from78diagnostics.7980For deployment, classify malformed identifiers or force values as81`input_validation`; a 401/403 after the REST client's one refresh attempt as82`authorization_or_privilege`; HTTP failures as `fusion_api_error`; and a83nonterminal result at the polling limit as `process_timeout`. Return the last84safe status and job ID to the calling project workflow; never persist OAuth85tokens, secrets, Authorization headers, or sensitive setup data.8687For a caller-supplied post-deployment action, classify a missing successful88`DEPLOYED` status as `process_failed`, an unapproved POST as89`approval_blocker`, and an unsuccessful job result as `process_failed`.90Capture the response and any request identifier in `post_deployment_result`.91Do not retry the POST without a new explicit approval.