Pricing Implementation Guidance
Purpose
Provides CX Configure Price Quote implementation guidance for the Pricing functional area.
When to Use
Use this functional-area skill after Configure Price Quote scope is confirmed and the project needs pricing setup planning, baseline export, import sequencing, or validation checkpoints.
Catalog Metadata
- Pillar:
CX - Offering:
Configure Price Quote(ORA_CONFIGURE_PRICE_QUOTE) - Functional area / Setup Object:
Pricing(CUSTOM_PRICING)
Setup Tasks
- Fusion Pricing Sync (
CUSTOM_FUSION_PRICING_SYNC)
Inputs
implementation_objectiveproject_contextpricing_scopepricing_requirementssync_direction_from_prompt: source and target stated or inferred from the user's request; the child task validates the supported direction.
Outputs
functional_area_setup_planconfiguration_guidancevalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
The only executable CPQ Pricing task skill here is
fusion-pricing-sync/SKILL.md. Route CPQ Pricing requests to set up pricing,
run or submit Fusion Pricing Sync, or sync pricing between Fusion and CPQ to
that skill. Detect source and target from the user's prompt before any live
workflow step, then apply the child skill's direction validation. The supported
direction is Fusion as source and CPQ as target. If the prompt omits direction,
recommend Fusion to CPQ. If it requests CPQ to Fusion, explain the mismatch
and offer Fusion to CPQ for the user's confirmation; do not silently reverse
the request. Users do not need to request DAT generation or Data Loader
initiation explicitly.
For a fresh implementation request, route project initialization and initial
Run Book creation through the implementation router and the core initializer /
Run Book workflow before invoking the child task's live loader steps. Include
CUSTOM_FUSION_PRICING_SYNC in the canonical task mapping, deliver the created
Run Book dashboard, then continue to DAT generation and validation. Reuse an
existing active Run Book with the exact sequenced task. The child task obtains
one Data Loader approval before upload; Run Book preparation does not replace it.
Track token usage for any generated project artifact or skill-run record using
the manifest policy.
The Pricing functional area routes setup wording to its runtime sync task. Keep existing request phrases, including "Sync Fusion to CPQ" and "Setup Fusion Pricing," as triggers for that task. The user-facing wording below changes the response, not which prompts select the workflow.
This task does not call CPQ REST or poll a CPQ task status. Its only setup-data
execution route is the approved CpqChargeSetSync Data Loader import. It is a
trigger-only sync, so the workflow must not ask users for charge-set rows or
mapping data.
The registered pricing operation is POST with no business payload. The DAT
contains a loader trigger, with optional integer chargeId when generated, rather
than charge-set input rows. Keep REST routing for CpqChargeSetSync and use the
child task's explicit create-mode DAT workflow.
In user-facing progress and result messages, describe the work as "syncing Fusion
pricing reference data." Keep the supported Fusion-to-CPQ direction available
when it is needed to resolve or explain a source/target choice. Treat charge-set
terminology and CpqChargeSetSync as internal workflow details.