Manage Transaction Types Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Transaction Types under Customer Billing.
Setup Task Skill Contract
- task_code:
AR_MANAGE_TRANSACTION_TYPES - task_name:
Manage Transaction Types - parent_skill_id:
erp.financials.customer-billing - pillar:
ERP - offering:
Financials - functional_area:
Customer Billing - functional_area_code:
ORA_FIN_CUST_BILL - 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 Transaction Types under Customer Billing.
Setup Task Metadata
- Task name:
Manage Transaction Types - Task code:
AR_MANAGE_TRANSACTION_TYPES - 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:
Customer Billing - Setup task name:
Manage Transaction Types - Setup task code:
AR_MANAGE_TRANSACTION_TYPES
Source-Backed Task Behavior
- Treat
AR_TRANSACTION_TYPEas the parent entity andAR_REF_ACCT_TRX_TYPEas its reference-account child; preserve the exact parentSetCodeandNamein every emitted child row. Evidence:SRC-FSM-PACKAGE,SRC-CODE-AM-DEF,SRC-CODE-REF-VO. - Use
SetCodeplusNameas the parent transaction-type business identity; never identify a transaction type byNamealone. Evidence:SRC-CODE-BO-META,SRC-CODE-PRIMARY-VO,SRC-EDM-RA-CUST-26B. - Support source-backed create and existing-row update preparation. Match updates only by
SetCodeplusName. The exact supported update fields areDescription,Status, andEndDate; every other field remains blocked unless later operation-specific evidence promotes it. Physical delete remains unsupported, andStatusorEndDatechanges are retirement updates rather than delete. Evidence:SRC-HELP-TRXTYPE-26C,SRC-CODE-CREATE-VO,SRC-CODE-AM-IMPL,SRC-CODE-PRIMARY-VO,SRC-CODE-PRIMARY-EO,SRC-E2E-MTT-DESCRIPTION-UPDATE-20260905,SRC-E2E-MTT-DESCRIPTION-ROLLBACK-20260905. - Treat developer-test fixtures, campaign policies, and test approvals as test-only controls. They never limit ordinary implementor create or update row counts and never override the source-backed task behavior in this skill and its active
ora-resource/files. - Require explicit create values for
SetCode,Name,PostToGl,AccountingAffectFlag,Status,Type,DefaultPrintingOption,DefaultStatus,AllowFreightFlag,AllowOverapplicationFlag,CreationSign,StartDate,TaxCalculationFlag, andNaturalApplicationOnlyFlag; do not invent defaults for these fields. Evidence:SRC-FSM-PACKAGE,SRC-CODE-CREATE-VO,SRC-CODE-PRIMARY-EO,SRC-BO-TRXTYPE-26C. - Require
AR_TRANSACTION_TYPE.Nameto be no more than 20 characters and an explicitly suppliedAR_TRANSACTION_TYPE.Descriptionto be no more than 80 characters. Enforce these source-backed limits before immutable preview or candidate generation for every requested row, report the actual and maximum character counts, and never silently truncate, abbreviate, or rewrite business text. Evidence:SRC-EDM-RA-CUST-26B,SRC-E2E-MTT-FIELD-LENGTH-20260909. - Accept only
YorNfor source-backed Boolean option fields, and reject a row whenNaturalApplicationOnlyFlagandAllowOverapplicationFlagare bothY. Evidence:SRC-BO-TRXTYPE-26C,SRC-CODE-PRIMARY-EO,SRC-CODE-PRIMARY-VO. - Validate fixed domains before package generation: transaction class
ADJ,BR,CB,CM,DEP,DM,GUAR, orINV; record statusA,D, orI; printing optionN,NOT, orPRI; completion controlALL,NEGATIVE_LINE_AMT, orNONE. Evidence:SRC-BO-TRXTYPE-26C,SRC-CODE-CREATE-VO,SRC-EDM-RA-CUST-26B. - Omit the five Fusion who/audit fields from generated parent and child rows and preserve them only as baseline comparison evidence. Evidence:
SRC-CODE-AM-IMPL,SRC-CODE-PRIMARY-EO,SRC-CODE-PRIMARY-VO,SRC-CODE-REF-VO. - Require ISO date values and reject
EndDateearlier thanStartDate; malformed date and date-time values must not be stringified into a package. Evidence:SRC-BO-TRXTYPE-26C,SRC-CODE-PRIMARY-EO,SRC-EDM-RA-CUST-26B. - During reconciliation, apply strict separator canonicalization to every package field whose exact
ASM_SETUP_CSV_METADATA.xmltype isdate: requested and candidate values must be identical strictYYYY-MM-DD, and a persisted strictYYYY/MM/DDvalue is equivalent only when all values parse to the same valid Gregorian calendar date. Retain all raw values, the canonical ISO date, declared type, generic rule ID, and metadata-contract evidence. Do not extend this rule to date-time/timestamp fields, strings whose names merely containDate, blanks, malformed or locale-ambiguous values, unequal dates, or candidate drift. Evidence:SRC-E2E-MTT-STARTDATE-CANON-20260905,SRC-E2E-MTT-ENDDATE-CANON-20260909,SRC-FSM-PACKAGE. - For a reference-account child row, require exact
BuNameandLedgerName, setSourceRefTabletoRA_CUST_TRX_TYPES_ALL, and never accept a caller override for that constant. Evidence:SRC-CODE-REF-VO,SRC-CODE-AM-IMPL,SRC-EDM-AR-REF-26A. - Treat every account-segment field as an ordered, ledger-specific programmatic reference. Never invent, pad, reorder, truncate, or reuse combinations across ledgers; live use remains blocked until explicit nonproduction validation. Evidence:
SRC-CODE-AM-IMPL,SRC-CODE-GL-BULK,SRC-CODE-ARPT-VALIDATE,SRC-CODE-REF-VO. - For
CreationSign, accept only verified codePor the case-insensitive business labelPositive Signand normalize it toP. ForDefaultStatus, accept only verified codeOPor the case-insensitive business labelOpenand normalize it toOP. Their general resolvers remain Partial, so block or clarify every other value. KeepUsageCategoryCodeandTrxSubclassCodeblocked unless their exact environment-supported codes are verified; omit an optional unresolved field instead of inferring a code from a label. Evidence:SRC-CODE-CREATE-VO,SRC-BO-TRXTYPE-26C,SRC-E2E-MTT-CREATE-IMPORT-VALUES-20260905,SRC-E2E-MTT-CREATE-RECONCILIATION-20260905. - Serialize descriptive-flexfield values only with their matching context code and source-backed datatype; never fabricate contexts or coerce values across contexts. Evidence:
SRC-CODE-PRIMARY-EO,SRC-CODE-PRIMARY-VO,SRC-EDM-RA-CUST-26B. - Build from a fresh same-task template/current export pair, preserve
ASM_SETUP_CSV_METADATA.xmlunchanged from the current-data baseline, preserve ordered headers and explicit trailing blanks, and reject every short or long CSV row. Evidence:SRC-FSM-PACKAGE. - If every requested update already matches the fresh current-data baseline exactly, complete source, field, ownership, and requirement validation and return
NO_OPwithout creating an import ZIP. The result retains input/design hashes and the business summary;candidateSha256is null, the member inventory is empty, and no candidate may be submitted to Data Loader. Record the no-change outcome. The same rule applies to an already-restored update rollback. Do not treat approximate text or date formatting differences as exact equality; ordinary typed-date reconciliation remains unchanged. A batch containing any real change follows the normal package, validation, preview, and approval workflow. - Route every import through
core.data-loaderinFSMmode with an emptybusinessObject; use metadataObjectShortNameAR_MANAGE_TRANSACTION_TYPESas task identity, require the validation, immutable preview, and approval prescribed by core.data-loader and Task Hook, and never retry a failed or uncertain submission automatically. Evidence: current repository contracts andSRC-FSM-PACKAGE.
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.customer-billing for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.