Fusion Pricing Sync Setup Task Guidance
Purpose
After the Run Book is prepared and active, run the Fusion Data Loader workflow
for CpqChargeSetSync through an approved immutable archive for a supported
Fusion-to-CPQ request. A general business-outcome request selects this workflow; the user
does not need to request Generate DAT or initiateDataLoad separately.
CpqChargeSetSync is a trigger-only sync task. Never ask the
user for charge-set rows, mapping data, or a source DAT. The DAT/ZIP and the
initiateDataLoad request fields are internal workflow artifacts, not user
inputs. Use the generic core Data Loader DAT generator. The generated DAT is an
internal workflow artifact rather than a user-requested sample.
core.data-loader resolves the live template, validates and packages the DAT,
and owns approval, upload, and initiation. Task rules validate the POST trigger
contract against the immutable source. Do not define task-local exceptions
to core validation.
Pricing Trigger Contract
The pillar developer confirms that pricing sync is a POST operation with no
business request payload. The registered Data Loader adapter executes that
operation from a trigger DAT; the DAT row and the generic initiateDataLoad
request are loader transport artifacts, not charge-set business data.
dataloader_import_mode: REST selects this registered REST-backed Data Loader
business object. It does not mean direct REST execution and does not conflict
with using DAT as the loader source. Keep this route; do not change it to HDL
or require an additional direct-REST execution document.
Use the generic generator's explicit --operation create --format dat path so
RestAction, when present in the live template, is POST, never PATCH or
DELETE. Do not use update-mode sample enrichment or look up existing charges.
chargeId is a non-mandatory integer surrogate field. If the generator includes
it, its metadata-valid integer placeholder is acceptable: the particular value
has no business meaning and needs no existence, uniqueness, or mapping lookup.
Its omission is also acceptable when the live source schema permits it. Do not
ask the user for it or reject a generated integer merely because it is a sample
value. This contract does not waive core schema or datatype checks.
If live metadata requires business inputs, contradicts the optional integer contract, or cannot provide a usable registered template, report the exact metadata mismatch. Do not invent a REST/DAT conflict or substitute a direct POST. A failed lookup is a blocker; a successful metadata-backed loader route does not need an independently callable business endpoint.
Run Book Handoff
For a normal request such as "Fusion Pricing Sync" or "Setup Fusion Pricing",
start with router.implementation-router and select the project and this exact
task. If a new project is needed, delegate to
core.project-mgmt.project-workspace-initializer: create the canonical local
Run Book plan and task context, then let core.runbook create the initial Run
Book under its own authorization rules. Deliver the returned Run Book dashboard
before DAT generation. Reuse an existing active Run Book and exact sequenced
task; do not create a duplicate on resume. Missing task membership or an
unbound, failed, or unknown Run Book requires the declared core workflow to
resolve it before proceeding. A deferred creation is handled by that workflow.
The intended flow is Run Book preparation, DAT generation and validation, Data Loader approval, then upload and initiation. Run Book creation or activation never approves the pricing upload. This skill delegates Run Book operations; it does not construct Run Book payloads or mutate its control state.
For user-facing narration, say "syncing Fusion pricing reference data." Use
Fusion-to-CPQ wording only when direction needs to be confirmed or explained.
Keep charge-set terminology and the business-object name in the internal
workflow; preserve any verbatim approval or initiation report required by
core.data-loader.
Preflight
Before the first live Data Loader step, infer the requested source and target
from the user's prompt and apply the direction rules in
ora-resource/ora_input_validation.md. Only Fusion as source and CPQ as target
may proceed. Then read and apply the task-local input
validation, dependency-readiness, reference-lookup, and error-handling
guidance. Require an exact live CpqChargeSetSync metadata match, a validated
immutable archive, completed Task Hook validation, and a current approval bound
to that exact archive. Delegate environment identity, privilege, artifact, and
approval-envelope checks to core.data-loader and core.data-loader.task-hook.
Stop before upload or initiateDataLoad when any preflight check fails,
is ambiguous, or no longer matches the approved archive.
Required Workflow
Read the task-local ora-resource/ files in this order: defaulting rules,
input validation, dependency readiness, reference lookups, error handling,
then the rule registry.
Complete the Run Book handoff above before the first Data Loader step. Use its canonical task-context.json and the positive sequence for Fusion Pricing Sync.
- Resolve
CpqChargeSetSyncfrom livedataLoaderBusinessObjectsmetadata and download its DAT template/schema throughcore.data-loader. - Generate an internal
CpqChargeSetSyncDAT through the generic core Data Loader generator, using a fresh artifact-directory ID and--operation create --format dat. Save it underproject/{project_id}/artifacts/pillars/cx/configure-price-quote/pricing/fusion-pricing-sync/runs/{run_id}. Use only this one generated DAT as the source; its generated record is the sync trigger, not user-supplied charge-set data. Keep the Run Book's configured runID; the fresh artifact-directory ID must not replace it. Validate POST and the optional integer chargeId contract from ora-resource/ora_input_validation.md. Pass the DAT tocore.data-loaderfor live source/schema validation, immutable ZIP preparation, preflight, and Task Hook validation. Reject any generated value that does not pass those core gates. Do not collect charge-set data from the user. - After the one Data Loader approval, upload only that approved archive to UCM
and call
initiateDataLoadwithIMPORT_AND_LOAD. Do not retry either POST.
Routing and Approval
core.data-loader owns live business-object metadata, DAT schema and source
validation, deterministic ZIP preparation, immutable-artifact checks, UCM
upload, and the fixed generic initiateDataLoad action. This skill must not
implement those Data Loader functions.
The one Data Loader initiation requires a current approval for the exact
immutable CpqChargeSetSync archive. An active Run Book is a prerequisite, not
a substitute for the Data Loader approval.
Ask the user only for an approval at the core.data-loader approval gate. Do
not expose internal workflow verbs as required user prompts.
Recovery and Persistence
Persist redacted validation and failure diagnostics under the project workspace.
Do not persist credentials, tokens, authorization headers, or archive contents.
Do not retry a UCM upload or initiateDataLoad after dispatch without explicit
approval or idempotency evidence.
Download Fusion Data Loader Sample
This generated sample-download section applies to a separate explicit workbook
sample request. The normal Fusion Pricing Sync workflow above generates DAT
with --operation create --format dat; it does not require a user-supplied
workbook or a second sample-generation prompt.
Use this workflow when dataloader_import_mode: "REST" and a Fusion Data Loader sample is needed for the task’s business object.
Confirm that
CpqChargeSetSyncis the exact registered Data Loader business object.Generate the default editable XLSX sample through
core.data-loader:python3 core/data-loader/scripts/generate_sample_dat.py \ "CpqChargeSetSync" \ --operation create \ --output-dir "<project-artifact-directory>"Keep the generated workbooks together:
- editable sample
- attribute-details workbook
- key-fields workbook
Review the generated headers and key fields before preparing source data. The operation uses read-only Fusion metadata and does not upload or import data.
Use the generated editable workbook as the starting point for the later Data Loader preparation and approval workflow.