Manage Opportunity Revenue Categories Setup Task Guidance
FSM Task Identity Policy
Require exact task code/name, selected task SKILL.md, target environment, and
immutable archive SHA-256 throughout review, export, package preparation, and
validation.
- Review, export, and package preparation do not require Data Loader task context.
- Every Core Data Loader mutation handoff requires a persisted project
TaskContextPath, exact TaskName, and positive TaskSequence.
- The selected context entry must resolve to this task's exact skill path,
TaskCode, TaskName, offering, and functional area.
The persisted context may be generated from the project's resolved setup-task
plan without creating an Oracle Run Book. Never hand-author, infer, or
synthesize a context entry merely to satisfy Data Loader.
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Opportunity Revenue Categories under Opportunities.
Setup Task Skill Contract
- task_code:
MOO_MANAGE_REVENUE_CATEGORIES
- task_name:
Manage Opportunity Revenue Categories
- parent_skill_id:
cx.sales.opportunities
- pillar:
CX
- offering:
Sales
- functional_area:
Opportunities
- functional_area_code:
ORA_MOO_OPPORTUNITIES
- available_flag:
Y
- export_import_supported_flag:
Y
- csv_export_import_supported_flag:
Y
- dataloader_import_mode:
FSM
- businessObject: ``
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Opportunity Revenue Categories under Opportunities.
Supported Operations and Routes
| Operation |
Route |
Required behavior |
| Read |
Core Apps Common Standard Lookups REST |
Resolve exactly one code under MOO_REVN_CATEGORY and return sanitized current state without mutation approval. |
| Create |
Task-level export and Core Data Loader FSM only |
Require an absent exact code, a fresh exact-target/release completed export, exactly one reviewed package row, and complete package readiness before handoff. |
| Update |
Task-level export and Core Data Loader FSM only |
Require one existing exact code, a reviewed mutable delta, fresh state lock, impact evidence, and complete immutable package readiness before handoff. |
| Disable |
Default: task-level export and Core Data Loader FSM |
Set EnabledFlag to N in the package only; do not translate disablement to DELETE. |
| Export |
Shared task-level export |
Export and validate the complete MOO_MANAGE_REVENUE_CATEGORIES task for the exact target and release; do not require a LookupCode. |
| Import |
Core Data Loader FSM only |
Validate every changed MOO_REVN_CATEGORY row, preserve every unrelated member and row, and hand the unchanged final ZIP to Data Loader. |
Delete is unsupported by this task contract. Do not create or rename the parent
lookup type, substitute MOO_SETID_REVN_CATEGORY, or add reference-set context.
Read-only discovery delegates transport and authentication to
core.fusion-api.apps-common. Direct REST mutation is unsupported even though
the core adapter documents generic standard-lookup writes. Refuse POST, PATCH,
PUT, and DELETE for this task and use the exact FSM package route for Create,
Update, Disable, or Import.
Setup Task Metadata
- Task name:
Manage Opportunity Revenue Categories
- Task code:
MOO_MANAGE_REVENUE_CATEGORIES
- Available:
Y
- Export/import supported:
Y
- CSV export/import supported:
Y
- CSV export/import routing:
supported
- Data Loader import mode:
FSM
- Business Object: ``
CSV Export, Import, and Validation Workflow
CSVExportImportSupportedFlag is Y for this task, so route task setup data work through the relevant skills:
- Export setup task data with
shared.setup-export.task-level-export.
- Validate setup task data with
shared.validation.setup-data-validator.
- Validate reference data with
shared.validation.reference-data-validator.
- Import setup task data with
core.data-loader.
Use this task metadata when invoking those skills:
- Offering:
Sales
- Functional area / Setup Object:
Opportunities
- Setup task name:
Manage Opportunity Revenue Categories
- Setup task code:
MOO_MANAGE_REVENUE_CATEGORIES
Default FSM Package Workflow
- Load
core/fusion-api/apps-common/SKILL.md and its standard-lookups
reference contract for read-only parent and code discovery.
- Select
SingleLookup for Read or one-code Create, Update, or Disable, and
Package for full-task Export or Import.
- Resolve the exact
MOO_REVN_CATEGORY parent. Resolve one exact code for
SingleLookup; for Package Import, validate every changed row independently.
- Obtain a fresh completed export for the exact target, release, and
MOO_MANAGE_REVENUE_CATEGORIES task. Preserve it as the baseline and build
a separate final ZIP for a mutation or Import.
- Before design gating, validate exact task identity/name/code, one ASM
identity, metadata-derived members and headers,
reviewed row deltas, fresh current-state locks, impact, unrelated-content
preservation, and the SHA-256 of the reopened final ZIP.
- For a mutation or Import handoff, resolve persisted
TaskContextPath, exact
TaskName, and positive TaskSequence to this exact skill path, TaskCode,
offering, and functional area. Hand that context with the exact environment,
immutable package path, SHA-256, member summary, proposed rows, current
state, impact evidence, and verification read to core.data-loader.
- Let Data Loader validate the unchanged package, invoke Task Hook, and build
its immutable approval preview. Stop until the user later replies exactly
approve; no other approval text authorizes the FSM upload.
- After that approval, let Data Loader revalidate and submit once. Accepted
initiation is terminal for that request; do not monitor, retrieve ProcessLog,
or re-read the lookup automatically.
- On a later explicit status or results request, use Data Loader status
handling and then re-read the exact item to compare it with the approved
result. On a failed or uncertain result, preserve sanitized diagnostics and
reconcile before proposing another package.
For the FSM route, Data Loader owns the approval preview and later standalone
approve. This child hands off package evidence without requiring, creating,
or interpreting Data Loader-owned approval evidence.
Execution Safety Contract
Before any external read, export, package handoff, supported direct REST
preview, or mutation, run a preflight that validates the exact environment,
task identity, request mode and route, privileges, selectors, current-state
evidence, package or endpoint shape, destination paths, and route-owned
approval state. Stop before side effects when evidence is missing, stale,
ambiguous, cross-environment, or inconsistent with the task-local resources
and compiled rule plan.
For error handling and failure behavior, load
ora-resource/ora_error_handling.md, classify the failure under the governed
taxonomy, preserve sanitized diagnostics and external identifiers, and follow
only the documented recovery path. Retry cached-token authentication at most
once through the owning core client and retry only bounded read-only transport
failures. Never retry a live REST mutation, Data Loader import, upload, or
uncertain result without a fresh immutable preview and explicit approval. On a
timeout or accepted Data Loader initiation, return the current status and safe
next-check path instead of polling or resubmitting automatically.
Redact credentials, bearer tokens, authorization headers, OAuth state,
token-cache contents, cookies, private keys, and sensitive payload values.
Never print or persist those secrets in previews, diagnostics, project
artifacts, skill-run records, or user responses.
Oracle Resource Read Order
- ora_input_validation.md
- ora_reference_lookups.md
- ora_defaulting_rules.md
- ora_dependency_readiness.md
- ora_design_enforcement.md
- ora_error_handling.md
- ora_rule_registry.json for the compiled task-node graph
Inputs
implementation_objective
project_context
setup_task_scope
setup_data_artifacts
fusion_environment_context
request_mode
lookup_operation
lookup_code
lookup_attributes
expected_current_state
reference_export_optional
task_context_path
task_sequence
package_path_optional
package_sha256_optional
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
current_revenue_category_state
immutable_change_preview
fsm_package_validation
data_loader_task_validation_result_optional
data_loader_approval_preview_optional
task_validation_envelope_optional
data_load_initiation_result_optional
accepted_initiation_result_optional
lookup_execution_result
post_change_verification
diagnostics
skill_run_record
token_usage_record
Implementation Notes
Use the parent functional-area skill cx.sales.opportunities for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
1---2skill_id: "cx.sales.opportunities.manage-opportunity-revenue-categories"3name: manage-opportunity-revenue-categories-setup-task-guidance4description: "Manages Opportunity revenue-category codes under standard lookup MOO_REVN_CATEGORY through guarded read-only discovery and validated export-derived FSM packages handed to Core Data Loader; direct REST mutation is unsupported."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Opportunities"9functional_area_code: "ORA_MOO_OPPORTUNITIES"10task_code: "MOO_MANAGE_REVENUE_CATEGORIES"11task_name: "Manage Opportunity Revenue Categories"12parent_skill_id: "cx.sales.opportunities"13available_flag: "Y"14export_import_supported_flag: "Y"15csv_export_import_supported_flag: "Y"16dataloader_import_mode: "FSM"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "orchestration"20execution_mode: "hybrid"21owner_team: "CX sales pillar team"22version: "0.3.5"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28 - "fusion_environment_context"29 - "request_mode"30 - "lookup_operation"31 - "lookup_code"32 - "lookup_attributes"33 - "expected_current_state"34 - "reference_export_optional"35 - "task_context_path"36 - "task_sequence"37 - "package_path_optional"38 - "package_sha256_optional"39outputs:40 - "setup_task_plan"41 - "setup_data_routing"42 - "validation_checkpoints"43 - "current_revenue_category_state"44 - "immutable_change_preview"45 - "fsm_package_validation"46 - "data_loader_task_validation_result_optional"47 - "data_loader_approval_preview_optional"48 - "task_validation_envelope_optional"49 - "data_load_initiation_result_optional"50 - "accepted_initiation_result_optional"51 - "lookup_execution_result"52 - "post_change_verification"53 - "diagnostics"54 - "skill_run_record"55 - "token_usage_record"56depends_on:57 - "core.fusion-api.apps-common"58 - "shared.setup-export.task-level-export"59 - "shared.validation.setup-data-validator"60 - "shared.validation.reference-data-validator"61 - "core.data-loader"62uses_core:63 - "core.fusion-api.apps-common"64 - "core.data-loader"65 - "core.project-mgmt.artifact-version-manager"66 - "core.project-mgmt.artifact-registry-manager"67 - "core.project-mgmt.project-state-manager"68persists_project_state: true69token_usage_tracking:70 enabled: true71 granularity: "per_skill_run"72 artifact_type: "token_usage_record"73 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"74 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"75 required_fields:76 - "activity_start_time"77 - "skill_id"78 - "task"79 - "trigger"80 - "artifacts_written"81 - "files_read"82 - "estimated_input_tokens"83 - "estimated_output_tokens"84 - "estimated_total_tokens"85 - "estimation_method"86 - "notes"87state_updates:88 - "setup_task_sequence"89 - "configuration_blueprints"90 - "validation_results"91 - "token_usage_records"92workspace_outputs:93 - artifact_type: "configuration_blueprint"94 default_location: "project/{project_id}/artifacts/pillars/cx/sales/opportunities/manage-opportunity-revenue-categories/current/"95 versioning_policy: "major-new-version-minor-confirm-update"96 - artifact_type: "validation_result"97 default_location: "project/{project_id}/artifacts/pillars/cx/sales/opportunities/manage-opportunity-revenue-categories/current/"98 versioning_policy: "major-new-version-minor-confirm-update"99 - artifact_type: "skill_run"100 default_location: "project/{project_id}/state/runs/"101 versioning_policy: "append-only"102 - artifact_type: "token_usage_record"103 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"104 versioning_policy: "append-only"105applicability:106 industries:107 - "All"108 countries:109 - "All"110 fusion_releases:111 - "Current Oracle Fusion Cloud release"112side_effects:113 - "Reads standard lookup MOO_REVN_CATEGORY through core.fusion-api.apps-common."114 - "May hand an exact immutable MOO_MANAGE_REVENUE_CATEGORIES FSM package to core.data-loader, which owns Task Hook validation, its approval preview, the later standalone approval, upload, and accepted initiation result."115 - "On a later explicit status or results request, may read Data Loader process evidence and verify MOO_REVN_CATEGORY through Apps Common."116 - "Persists preview, execution, verification, diagnostic, and token-usage artifacts in the implementation project workspace."117required_privileges:118 - "Fusion privileges to view or manage standard lookup MOO_REVN_CATEGORY."119 - "Privileges to export or import MOO_MANAGE_REVENUE_CATEGORIES when the approved FSM route is selected."120metadata:121 source: https://skillmd.com/skills/oracle/manage-opportunity-revenue-categories-setup-task-guidance122---123124# Manage Opportunity Revenue Categories Setup Task Guidance125126## FSM Task Identity Policy127128Require exact task code/name, selected task `SKILL.md`, target environment, and129immutable archive SHA-256 throughout review, export, package preparation, and130validation.131132- Review, export, and package preparation do not require Data Loader task context.133- Every Core Data Loader mutation handoff requires a persisted project134 `TaskContextPath`, exact `TaskName`, and positive `TaskSequence`.135- The selected context entry must resolve to this task's exact skill path,136 `TaskCode`, `TaskName`, offering, and functional area.137138The persisted context may be generated from the project's resolved setup-task139plan without creating an Oracle Run Book. Never hand-author, infer, or140synthesize a context entry merely to satisfy Data Loader.141142## Purpose143144Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Opportunity Revenue Categories` under `Opportunities`.145146## Setup Task Skill Contract147148- task_code: `MOO_MANAGE_REVENUE_CATEGORIES`149- task_name: `Manage Opportunity Revenue Categories`150- parent_skill_id: `cx.sales.opportunities`151- pillar: `CX`152- offering: `Sales`153- functional_area: `Opportunities`154- functional_area_code: `ORA_MOO_OPPORTUNITIES`155- available_flag: `Y`156- export_import_supported_flag: `Y`157- csv_export_import_supported_flag: `Y`158- dataloader_import_mode: `FSM`159- businessObject: ``160- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`161162## Usage163164Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Opportunity Revenue Categories` under `Opportunities`.165166## Supported Operations and Routes167168| Operation | Route | Required behavior |169|---|---|---|170| Read | Core Apps Common Standard Lookups REST | Resolve exactly one code under MOO_REVN_CATEGORY and return sanitized current state without mutation approval. |171| Create | Task-level export and Core Data Loader FSM only | Require an absent exact code, a fresh exact-target/release completed export, exactly one reviewed package row, and complete package readiness before handoff. |172| Update | Task-level export and Core Data Loader FSM only | Require one existing exact code, a reviewed mutable delta, fresh state lock, impact evidence, and complete immutable package readiness before handoff. |173| Disable | Default: task-level export and Core Data Loader FSM | Set EnabledFlag to N in the package only; do not translate disablement to DELETE. |174| Export | Shared task-level export | Export and validate the complete MOO_MANAGE_REVENUE_CATEGORIES task for the exact target and release; do not require a LookupCode. |175| Import | Core Data Loader FSM only | Validate every changed MOO_REVN_CATEGORY row, preserve every unrelated member and row, and hand the unchanged final ZIP to Data Loader. |176177Delete is unsupported by this task contract. Do not create or rename the parent178lookup type, substitute `MOO_SETID_REVN_CATEGORY`, or add reference-set context.179Read-only discovery delegates transport and authentication to180`core.fusion-api.apps-common`. Direct REST mutation is unsupported even though181the core adapter documents generic standard-lookup writes. Refuse POST, PATCH,182PUT, and DELETE for this task and use the exact FSM package route for Create,183Update, Disable, or Import.184185## Setup Task Metadata186187- Task name: `Manage Opportunity Revenue Categories`188- Task code: `MOO_MANAGE_REVENUE_CATEGORIES`189- Available: `Y`190- Export/import supported: `Y`191- CSV export/import supported: `Y`192- CSV export/import routing: `supported`193- Data Loader import mode: `FSM`194- Business Object: ``195196## CSV Export, Import, and Validation Workflow197198`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:1992001. Export setup task data with `shared.setup-export.task-level-export`.2012. Validate setup task data with `shared.validation.setup-data-validator`.2023. Validate reference data with `shared.validation.reference-data-validator`.2034. Import setup task data with `core.data-loader`.204205Use this task metadata when invoking those skills:206207- Offering: `Sales`208- Functional area / Setup Object: `Opportunities`209- Setup task name: `Manage Opportunity Revenue Categories`210- Setup task code: `MOO_MANAGE_REVENUE_CATEGORIES`211212## Default FSM Package Workflow2132141. Load `core/fusion-api/apps-common/SKILL.md` and its standard-lookups215 reference contract for read-only parent and code discovery.2162. Select `SingleLookup` for Read or one-code Create, Update, or Disable, and217 `Package` for full-task Export or Import.2183. Resolve the exact `MOO_REVN_CATEGORY` parent. Resolve one exact code for219 SingleLookup; for Package Import, validate every changed row independently.2204. Obtain a fresh completed export for the exact target, release, and221 `MOO_MANAGE_REVENUE_CATEGORIES` task. Preserve it as the baseline and build222 a separate final ZIP for a mutation or Import.2235. Before design gating, validate exact task identity/name/code, one ASM224 identity, metadata-derived members and headers,225 reviewed row deltas, fresh current-state locks, impact, unrelated-content226 preservation, and the SHA-256 of the reopened final ZIP.2276. For a mutation or Import handoff, resolve persisted `TaskContextPath`, exact228 `TaskName`, and positive `TaskSequence` to this exact skill path, `TaskCode`,229 offering, and functional area. Hand that context with the exact environment,230 immutable package path, SHA-256, member summary, proposed rows, current231 state, impact evidence, and verification read to `core.data-loader`.2327. Let Data Loader validate the unchanged package, invoke Task Hook, and build233 its immutable approval preview. Stop until the user later replies exactly234 `approve`; no other approval text authorizes the FSM upload.2358. After that approval, let Data Loader revalidate and submit once. Accepted236 initiation is terminal for that request; do not monitor, retrieve ProcessLog,237 or re-read the lookup automatically.2389. On a later explicit status or results request, use Data Loader status239 handling and then re-read the exact item to compare it with the approved240 result. On a failed or uncertain result, preserve sanitized diagnostics and241 reconcile before proposing another package.242243For the FSM route, Data Loader owns the approval preview and later standalone244`approve`. This child hands off package evidence without requiring, creating,245or interpreting Data Loader-owned approval evidence.246247## Execution Safety Contract248249Before any external read, export, package handoff, supported direct REST250preview, or mutation, run a preflight that validates the exact environment,251task identity, request mode and route, privileges, selectors, current-state252evidence, package or endpoint shape, destination paths, and route-owned253approval state. Stop before side effects when evidence is missing, stale,254ambiguous, cross-environment, or inconsistent with the task-local resources255and compiled rule plan.256257For error handling and failure behavior, load258`ora-resource/ora_error_handling.md`, classify the failure under the governed259taxonomy, preserve sanitized diagnostics and external identifiers, and follow260only the documented recovery path. Retry cached-token authentication at most261once through the owning core client and retry only bounded read-only transport262failures. Never retry a live REST mutation, Data Loader import, upload, or263uncertain result without a fresh immutable preview and explicit approval. On a264timeout or accepted Data Loader initiation, return the current status and safe265next-check path instead of polling or resubmitting automatically.266267Redact credentials, bearer tokens, authorization headers, OAuth state,268token-cache contents, cookies, private keys, and sensitive payload values.269Never print or persist those secrets in previews, diagnostics, project270artifacts, skill-run records, or user responses.271272273274275## Oracle Resource Read Order2762771. [ora_input_validation.md](ora-resource/ora_input_validation.md)2782. [ora_reference_lookups.md](ora-resource/ora_reference_lookups.md)2793. [ora_defaulting_rules.md](ora-resource/ora_defaulting_rules.md)2804. [ora_dependency_readiness.md](ora-resource/ora_dependency_readiness.md)2815. [ora_design_enforcement.md](ora-resource/ora_design_enforcement.md)2826. [ora_error_handling.md](ora-resource/ora_error_handling.md)2837. [ora_rule_registry.json](ora-resource/ora_rule_registry.json) for the compiled task-node graph284285## Inputs286287- `implementation_objective`288- `project_context`289- `setup_task_scope`290- `setup_data_artifacts`291- `fusion_environment_context`292- `request_mode`293- `lookup_operation`294- `lookup_code`295- `lookup_attributes`296- `expected_current_state`297- `reference_export_optional`298- `task_context_path`299- `task_sequence`300- `package_path_optional`301- `package_sha256_optional`302303## Outputs304305- `setup_task_plan`306- `setup_data_routing`307- `validation_checkpoints`308- `current_revenue_category_state`309- `immutable_change_preview`310- `fsm_package_validation`311- `data_loader_task_validation_result_optional`312- `data_loader_approval_preview_optional`313- `task_validation_envelope_optional`314- `data_load_initiation_result_optional`315- `accepted_initiation_result_optional`316- `lookup_execution_result`317- `post_change_verification`318- `diagnostics`319- `skill_run_record`320- `token_usage_record`321322## Implementation Notes323324Use the parent functional-area skill `cx.sales.opportunities` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.