Payments Implementation Guidance
Purpose
Apply the core Data Loader execution contract
to tasks with a supported FSM route. Route setup creates and changes through
core.data-loader; UI inspection remains read-only. Missing prerequisites block
execution, and Data Loader's approval workflow must not be duplicated.
Provides ERP Financials implementation guidance for the Payments functional area.
When to Use
Use this functional-area skill after Financials scope is confirmed and the project needs payments setup planning, baseline export, import sequencing, or validation checkpoints.
Catalog Metadata
- Pillar:
ERP - Offering:
Financials(XLE_FINANCIALS_JUR) - Functional area / Setup Object:
Payments(ORA_FIN_PAYMENTS)
Setup Tasks
- Manage Formats (
IBY_MANAGE_FORMATS) - Manage Payment Systems (
IBY_MANAGE_PAYMENT_SYSTEMS) - Manage Payment Codes (
IBY_MANAGE_PAYMENT_CODES) - Manage Disbursement System Options (
IBY_MANAGE_DISBURSEMENT_SYSTEM_OPTIONS)
Inputs
implementation_objectiveproject_contextpayments_scopepayments_requirements
Outputs
functional_area_setup_planconfiguration_guidancevalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the generated nested setup-task skills for task-level planning, sequencing, setup-data routing, and validation. Track token usage for any generated project artifact or skill-run record using the manifest policy.
Task Selection
Resolve the exact requested FSM task through the effective catalog and the project-objective classifier before choosing a nested task workflow. The authored child-skill list above is an implementation inventory, not a complete Payments task catalog or a default task selection. For a vague request such as "configure Payments setup using standard values", ask which exact setup task is intended; keep task selection pending until the user resolves that scope. Resolve offering ambiguity under the classifier's existing offering-scope rules as well.
When several tasks are explicitly requested, retain their separate identities and route each through its owning guidance. An MPS package contains only the exact MPS task; missing guidance for another task is a separate readiness gap.