Manage Payment Terms Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Payment Terms under Payables.
Supported Operations
This task supports creating and updating Payment Terms setup records. It does not support delete or end-date operations. Only the operation-specific fields documented in Input Validation and Design Enforcement are permitted; all other fields remain blocked.
Task Behavior
- Take every
AP_TERM_*CSV header and its order from the exact FSM template for this task. Reject short or long rows, and keep explicit trailing blank fields. Seeora-resource/ora_input_validation.mdandora-resource/ora_rule_registry.json. - Build the package with these keys:
AP_TERM_HEADER.Name;AP_TERM_LINE.AP_TERM_HEADER.Name + SequenceNum;AP_TERM_SUBSCRIPTION.AP_TERM_HEADER.Name + SetCode; andAP_TERM_HEADER_TRANSLATION.AP_TERM_HEADER.Name + Language. Fusion resolves the root alternate key and derives internal parent keys. Never put an internal ID in the CSV. Seeora-resource/ora_design_enforcement.md. - For every create or update of an
AP_TERM_LINE,AP_TERM_SUBSCRIPTION, orAP_TERM_HEADER_TRANSLATIONrow, include the matchingAP_TERM_HEADERrow in the same FSM archive. Unless an explicit header operation supplies it, copy the parent unchanged from the fresh current-data export and blank all audit fields. Include each parent only once. Block generation if the parent is absent from both the explicit operations and the fresh baseline; validation must reject missing or changed supporting parents. Fusion can mark a child-only archive as successfully imported while skipping its update. The non-productionAP_TERM_LINEtest proved this behavior: a child-onlyDueDayschange remained unpersisted after a successful import. - A new
AP_TERM_HEADERmust include at least one explicitly requestedAP_TERM_LINEinstallment for that same header in the package. This applies to enabled and disabled new terms. A set assignment or translation does not replace an installment. Stop before preview or ZIP generation withAP_AT_LEAST_ONE_CHILDand ask for installment details; never invent a line. For an existing term, a header update or child create/update does not require adding another installment. Keep its existing installments unchanged unless the user requests a change. - For a create with
AP_TERM_HEADER_TRANSLATIONrows, use the header key as the logical target. Fusion may display and export the explicit US translation name instead of that key. Derive this alias only from the candidate's US translation row, use it for reconciliation and UI proof, and record the header-key-to-display-name mapping. A KO row is translation evidence, not another payment-term header. - For a new payment-term header, default an omitted or blank
EnabledFlagtoY,TypetoSTD, andStartDateActiveto the package-builder system date inYYYY/MM/DD; record each applied value as an explicit default and serialize it into the CSV. A suppliedTypemust be exactlySTD; reject every other Type before package generation. Other explicit request values override their corresponding defaults. Seeora-resource/ora_defaulting_rules.md. - When preparing an import ZIP, use the date format shown in the fresh export for new or changed dates. Keep unchanged dates exactly as exported.
- Validate header dates and Rank before package generation. Dates must use the supported calendar-date format, and
EndDateActivecannot precedeStartDateActive. Rank is compared globally across Payment Terms, must be a whole numeric value of at most 18 digits, and must not duplicate another header's numeric Rank; do not invent a positive or minimum Rank rule. Seeora-resource/ora_input_validation.md. - Validate every effective payment-term line before package generation. Require exactly one due basis (
DuePercentorDueAmount) and exactly one complete due-date method (DueDays,DueDayOfMonthwithDueMonthsForward,FixedDate, orCalendar). Percentage lines for a term must total exactly 100; amount lines must include a zero-amount line; and one term cannot mix percentage and amount bases. Enforce the documented day/month ranges, nonnegative due values, complete discount pairs, and ordered discount dates and percentages. Seeora-resource/ora_input_validation.mdandora-resource/ora_design_enforcement.md. - Accept a set code, a set name, or an unspecified "set" in the user's request.
Keep an explicit code unchanged. For a name, look up
SetNameand get itsSetCode. For an unspecified set, search both fields and count distinct SetCodes. One distinct code allows processing; multiple codes require the user to choose; no matches stop ZIP/import. Never guess a code, change its case, or substitute a different set. Show any name-to-code mapping in the preview. See Reference Lookups. - Run
scripts/resolve_reference_prerequisites.pybefore normalization. It acceptssetReferenceinput and fills the subscription'sSetCodeonly after a complete, clear lookup. A supplied code or Calendar is checked by a read-only GET: a readable result allows processing, no rows stop it, and malformed responses stop it. The calendar query joins its name and type filters withand. - For an uploaded ZIP containing set assignments or installment Calendars, run the same reference helper
with
--packagebeforevalidate-upload. Pass its saved results using--reference-evidence. These results must cover every SetCode and nonblank installment Calendar in that exact ZIP. Missing results, no matches, or malformed responses stop validation. An unavailable API follows the supplied-value warning rule below. - If a check for an explicit code or Calendar is unavailable, record
validation_skippedand keep the supplied value for the separately approved import. HTTP 400 also records aresolver_contract_issuefor maintenance. If a name or unspecified set cannot be fully looked up, stop and ask for the Set Code; do not use the skipped-check rule to invent a required value. - Keep template-required audit columns as technical package behavior. Do not ask an implementation user to invent audit values; preserve non-requested values and rows from the fresh current export. See
ora-resource/ora_defaulting_rules.mdandora-resource/ora_input_validation.md. - Keep all adapter package construction and validation offline. Live export, preview, import, monitoring, persisted-state verification, commit, push, merge, and publication require their separate approvals. See
e2e-adapter.jsonandora-resource/ora_design_enforcement.md.
Setup Task Skill Contract
- task_code:
AP_MANAGE_PAYMENT_TERMS - task_name:
Manage Payment Terms - parent_skill_id:
erp.financials.payables - pillar:
ERP - offering:
Financials - functional_area:
Payables - functional_area_code:
FIN_PAYABLES_DEPLOYED - 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 Payment Terms under Payables.
Setup Task Metadata
- Task name:
Manage Payment Terms - Task code:
AP_MANAGE_PAYMENT_TERMS - 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:
Financials - Functional area / Setup Object:
Payables - Setup task name:
Manage Payment Terms - Setup task code:
AP_MANAGE_PAYMENT_TERMS
Inputs
implementation_objectiveproject_contextsetup_task_scopesetup_data_artifacts
Outputs
setup_task_plansetup_data_routingvalidation_checkpointsskill_run_recordtoken_usage_record
Implementation Notes
Use the parent functional-area skill erp.financials.payables for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
Verifying Changes After Import
reconcile can report PASS only after the workflow has observed a successful
import and a later completed export from the same task and environment. Supply
--verification-evidence <observations.json> --environment <selected-environment> --base-url <selected-https-origin> --import-request-id <completed-import-request>
along with the baseline, approved candidate, blueprint, requirements and export.
Missing, stale or mismatched evidence leaves verification PENDING; say that
saved changes have not yet been verified.
For an offline file comparison, use reconcile --compare-only. Its result is
MATCH or DIFFERENT, with persistenceVerification=NOT_PERFORMED. A file match
does not prove that an import occurred. Package building and import approval
are unchanged. See Error Handling
for the required observations.
Reference Lookup Evidence
When a design or uploaded ZIP uses lookup receipts, follow Reference evidence provenance. Keep the selected target separate from evidence, require matching environment and HTTPS origin, and rerun preflight for missing, malformed, future, or more-than-24-hour-old observations. The same provenance checks apply to unavailable lookup warnings. An offline receipt does not authorize a live call or prove that Fusion imported the ZIP.
Uploaded Package Compatibility
Before reporting an uploaded ZIP as valid, supply validate-upload with
--target-context <selected-target.json> from the independently selected
workflow target. Both baseline and uploaded metadata must match its environment
and release. Read Uploaded package compatibility
for the contract and migration boundary. Matching schemas alone do not establish
source/target compatibility.
Source Manifest Labels and Origins
When producing a source manifest or verifying post-import observations, follow Manifest labels and HTTPS origins. A source manifest's environment must match its ZIP metadata; keep migration destination information separate. Use a credential-free HTTPS origin without an API path, query or fragment. A template-only label requires an empty package.