Manage Transaction Sources Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Transaction Sources under Customer Billing.
Setup Task Skill Contract
- task_code:
AR_MANAGE_TRANSACTION_SOURCES
- task_name:
Manage Transaction Sources
- 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 Sources under Customer Billing.
Setup Task Metadata
- Task name:
Manage Transaction Sources
- Task code:
AR_MANAGE_TRANSACTION_SOURCES
- 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 Sources
- Setup task code:
AR_MANAGE_TRANSACTION_SOURCES
Source-Backed Task Behavior
- Treat
Name plus SetCode as the portable business key for both AR_BATCH_SOURCE and ORA_AR_TXN_BATCH_SOURCE; do not use environment-specific numeric identifiers as input identity.
- Support only the evidence-backed
create and update lifecycle operations, and keep all package generation, validation, determinism, rollback, and reconciliation work offline until a separately approved Data Loader import.
- Apply the evidence-backed relationship-partition ownership matrix: create targets
ORA_AR_TXN_BATCH_SOURCE and reconciles through AR_BATCH_SOURCE. For update, first require the exact Name plus SetCode key to occur once across the fresh package and in exactly one entity; target and reconcile through that export-owning entity. Stop when the key is absent, duplicated, or present in both entities, and never move an existing row between package projections.
- Preserve the exact two-entity CSV schemas, header order, metadata node paths, every unspecified row, and every unspecified non-audit value; fail closed when a supplied template or baseline disagrees with the adapter contract.
- Keep Manual and Imported transaction-source semantics separate:
BatchSourceType=INV is the Manual branch, while fields evidenced only for Imported sources apply only when BatchSourceType=FOREIGN; InvalidLinesRule=Reject is also evidenced for the Manual create path.
- On create, require
Name, SetCode, Description, BatchSourceType, and StartDate; also require an integer LastBatchNum of at least 1 when AutoTrxNumberingFlag=Y, including a defaulted Y. The new numbering sequence uses this value directly as its start; do not invent or substitute a number.
- On create, default omitted fields to
Status=A, BatchSourceType=INV, AutoTrxNumberingFlag=Y, and InvalidLinesRule=Reject; preserve any explicit value that is valid under the fixed value contract.
- Resolve grouping rule, reference-data set, document type, credit transaction source, legal entity, and transaction type from portable names, codes, sets, or identifiers; never invent a numeric identifier.
- Preserve the ordered self-reference contract: resolve
BatchSourceName with CmBatchSrcSetCode after the credit-source entity is available, and block ambiguous or missing matches.
- Exclude Fusion who columns and the derived display fields
DefaultInvTrxType and LegalEntityName from developer-supplied serialization.
- Treat
Description as the only source-backed supported update field. Do not add evidence-unresolved fields to the fscr-update-fields allowlist or describe them as supported.
- For a non-key, non-audit field on the exact export-owning update entity whose update contract remains explicitly unresolved, first run every known deterministic type, value, length, resolver, identity, and package validation. If those checks pass, disclose the evidence gap and offer the governed application-validation path only with explicit implementor approval bound to the exact update operation, entity, fields, environment, and immutable candidate. Approval to try a value does not prove Fusion supports it.
- Keep
SalesTerritoryRule, ControlTrxCompletionFlag, and UsageCategoryCode unresolved for update. Preserve their Partial resolver/value evidence: reject a known invalid value or a natural-language value that cannot be deterministically mapped, but do not turn incomplete evidence into an absolute unsupported-product conclusion for an exact package value that passes all deterministic checks.
- Never offer an unresolved-field override for
Name, SetCode, audit or identity controls, source-proven unsupported fields, package-integrity requirements, authorization controls, or a field on an entity that does not own the exact fresh-export key. AR_BATCH_SOURCE remains non-targetable for create; it is eligible for update only when it uniquely owns that key, and none of its fields becomes source-backed supported merely because the entity is targetable.
- Treat physical deletion as evidence-unresolved. Never describe Status or EndDate retirement as delete or soft delete, and block deletion until an exact source-backed mechanism, owner, key, child/cascade, irreversibility, and recovery contract exists.
- After every existing source, field, ownership, and requirement check passes, an update whose requested values exactly equal the fresh baseline for one unique Name-plus-SetCode export owner returns
NO_OP without an import ZIP. The result retains input/design hashes and business summary, with null candidate hash and empty inventory; never submit it to Data Loader. Already-restored update rollback follows the same rule. Any real change or create keeps the normal package and approval workflow.
- Keep Fusion writes outside this skill: Run Book owns normalized task intent and orchestration, Data Loader owns immutable preview and approved import, and no import, retry, or cleanup is authorized by static readiness.
Inputs
implementation_objective
project_context
setup_task_scope
setup_data_artifacts
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
skill_run_record
token_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.
For direct task entry containing another active setup-task request, return to the Customer Billing parent scope-confirmation gate before preparing an MTS package. Explicitly excluded document context does not expand the selected task scope.
1---2skill_id: "erp.financials.customer-billing.manage-transaction-sources"3name: manage-transaction-sources-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Transaction Sources under the Customer Billing functional area."5layer: "pillar"6pillar: "ERP"7offering: "Financials"8functional_area: "Customer Billing"9functional_area_code: "ORA_FIN_CUST_BILL"10task_code: "AR_MANAGE_TRANSACTION_SOURCES"11task_name: "Manage Transaction Sources"12parent_skill_id: "erp.financials.customer-billing"13available_flag: "Y"14export_import_supported_flag: "Y"15csv_export_import_supported_flag: "Y"16dataloader_import_mode: "FSM"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "planning"20execution_mode: "assisted"21owner_team: "ERP financials pillar team"22version: "0.1.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28outputs:29 - "setup_task_plan"30 - "setup_data_routing"31 - "validation_checkpoints"32 - "skill_run_record"33 - "token_usage_record"34depends_on:35 - "shared.setup-export.task-level-export"36 - "shared.validation.setup-data-validator"37 - "shared.validation.reference-data-validator"38 - "core.data-loader"39uses_core:40 - "core.project-mgmt.artifact-version-manager"41 - "core.project-mgmt.artifact-registry-manager"42 - "core.project-mgmt.project-state-manager"43persists_project_state: true44token_usage_tracking:45 enabled: true46 granularity: "per_skill_run"47 artifact_type: "token_usage_record"48 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"49 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"50 required_fields:51 - "activity_start_time"52 - "skill_id"53 - "task"54 - "trigger"55 - "artifacts_written"56 - "files_read"57 - "estimated_input_tokens"58 - "estimated_output_tokens"59 - "estimated_total_tokens"60 - "estimation_method"61 - "notes"62state_updates:63 - "setup_task_sequence"64 - "configuration_blueprints"65 - "validation_results"66 - "token_usage_records"67workspace_outputs:68 - artifact_type: "configuration_blueprint"69 default_location: "project/{project_id}/artifacts/pillars/erp/financials/customer-billing/manage-transaction-sources/current/"70 versioning_policy: "major-new-version-minor-confirm-update"71 - artifact_type: "validation_result"72 default_location: "project/{project_id}/artifacts/pillars/erp/financials/customer-billing/manage-transaction-sources/current/"73 versioning_policy: "major-new-version-minor-confirm-update"74 - artifact_type: "skill_run"75 default_location: "project/{project_id}/state/runs/"76 versioning_policy: "append-only"77 - artifact_type: "token_usage_record"78 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"79 versioning_policy: "append-only"80applicability:81 industries:82 - "All"83 countries:84 - "All"85 fusion_releases:86 - "Current Oracle Fusion Cloud release"87side_effects: []88required_privileges: []89metadata:90 source: https://skillmd.com/skills/oracle/manage-transaction-sources-setup-task-guidance91---9293<!-- fscr-supported-operations: create, update -->9495# Manage Transaction Sources Setup Task Guidance9697## Purpose9899Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Transaction Sources` under `Customer Billing`.100101## Setup Task Skill Contract102103- task_code: `AR_MANAGE_TRANSACTION_SOURCES`104- task_name: `Manage Transaction Sources`105- parent_skill_id: `erp.financials.customer-billing`106- pillar: `ERP`107- offering: `Financials`108- functional_area: `Customer Billing`109- functional_area_code: `ORA_FIN_CUST_BILL`110- available_flag: `Y`111- export_import_supported_flag: `Y`112- csv_export_import_supported_flag: `Y`113- dataloader_import_mode: `FSM`114- businessObject: ``115- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`116117## Usage118119Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Transaction Sources` under `Customer Billing`.120121## Setup Task Metadata122123- Task name: `Manage Transaction Sources`124- Task code: `AR_MANAGE_TRANSACTION_SOURCES`125- Available: `Y`126- Export/import supported: `Y`127- CSV export/import supported: `Y`128- CSV export/import routing: `supported`129- Data Loader import mode: `FSM`130- Business Object: ``131132## CSV Export, Import, and Validation Workflow133134`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:1351361. Export setup task data with `shared.setup-export.task-level-export`.1372. Validate setup task data with `shared.validation.setup-data-validator`.1383. Validate reference data with `shared.validation.reference-data-validator`.1394. Import setup task data with `core.data-loader`.140141Use this task metadata when invoking those skills:142143- Offering: `Financials`144- Functional area / Setup Object: `Customer Billing`145- Setup task name: `Manage Transaction Sources`146- Setup task code: `AR_MANAGE_TRANSACTION_SOURCES`147148## Source-Backed Task Behavior149150<!-- fscr-supported-operations: create, update -->151<!-- fscr-create-fields: ORA_AR_TXN_BATCH_SOURCE::AutoTrxNumberingFlag, ORA_AR_TXN_BATCH_SOURCE::BatchSourceType, ORA_AR_TXN_BATCH_SOURCE::Description, ORA_AR_TXN_BATCH_SOURCE::InvalidLinesRule, ORA_AR_TXN_BATCH_SOURCE::LastBatchNum, ORA_AR_TXN_BATCH_SOURCE::Name, ORA_AR_TXN_BATCH_SOURCE::SetCode, ORA_AR_TXN_BATCH_SOURCE::StartDate, ORA_AR_TXN_BATCH_SOURCE::Status -->152<!-- fscr-update-fields: ORA_AR_TXN_BATCH_SOURCE::Description -->153154- Treat `Name` plus `SetCode` as the portable business key for both `AR_BATCH_SOURCE` and `ORA_AR_TXN_BATCH_SOURCE`; do not use environment-specific numeric identifiers as input identity.155- Support only the evidence-backed `create` and `update` lifecycle operations, and keep all package generation, validation, determinism, rollback, and reconciliation work offline until a separately approved Data Loader import.156- Apply the evidence-backed relationship-partition ownership matrix: create targets `ORA_AR_TXN_BATCH_SOURCE` and reconciles through `AR_BATCH_SOURCE`. For update, first require the exact `Name` plus `SetCode` key to occur once across the fresh package and in exactly one entity; target and reconcile through that export-owning entity. Stop when the key is absent, duplicated, or present in both entities, and never move an existing row between package projections.157- Preserve the exact two-entity CSV schemas, header order, metadata node paths, every unspecified row, and every unspecified non-audit value; fail closed when a supplied template or baseline disagrees with the adapter contract.158- Keep Manual and Imported transaction-source semantics separate: `BatchSourceType=INV` is the Manual branch, while fields evidenced only for Imported sources apply only when `BatchSourceType=FOREIGN`; `InvalidLinesRule=Reject` is also evidenced for the Manual create path.159- On create, require `Name`, `SetCode`, `Description`, `BatchSourceType`, and `StartDate`; also require an integer `LastBatchNum` of at least 1 when `AutoTrxNumberingFlag=Y`, including a defaulted Y. The new numbering sequence uses this value directly as its start; do not invent or substitute a number.160- On create, default omitted fields to `Status=A`, `BatchSourceType=INV`, `AutoTrxNumberingFlag=Y`, and `InvalidLinesRule=Reject`; preserve any explicit value that is valid under the fixed value contract.161- Resolve grouping rule, reference-data set, document type, credit transaction source, legal entity, and transaction type from portable names, codes, sets, or identifiers; never invent a numeric identifier.162- Preserve the ordered self-reference contract: resolve `BatchSourceName` with `CmBatchSrcSetCode` after the credit-source entity is available, and block ambiguous or missing matches.163- Exclude Fusion who columns and the derived display fields `DefaultInvTrxType` and `LegalEntityName` from developer-supplied serialization.164- Treat `Description` as the only source-backed supported update field. Do not add evidence-unresolved fields to the `fscr-update-fields` allowlist or describe them as supported.165- For a non-key, non-audit field on the exact export-owning update entity whose update contract remains explicitly unresolved, first run every known deterministic type, value, length, resolver, identity, and package validation. If those checks pass, disclose the evidence gap and offer the governed application-validation path only with explicit implementor approval bound to the exact update operation, entity, fields, environment, and immutable candidate. Approval to try a value does not prove Fusion supports it.166- Keep `SalesTerritoryRule`, `ControlTrxCompletionFlag`, and `UsageCategoryCode` unresolved for update. Preserve their Partial resolver/value evidence: reject a known invalid value or a natural-language value that cannot be deterministically mapped, but do not turn incomplete evidence into an absolute unsupported-product conclusion for an exact package value that passes all deterministic checks.167- Never offer an unresolved-field override for `Name`, `SetCode`, audit or identity controls, source-proven unsupported fields, package-integrity requirements, authorization controls, or a field on an entity that does not own the exact fresh-export key. `AR_BATCH_SOURCE` remains non-targetable for create; it is eligible for update only when it uniquely owns that key, and none of its fields becomes source-backed supported merely because the entity is targetable.168- Treat physical deletion as evidence-unresolved. Never describe Status or EndDate retirement as delete or soft delete, and block deletion until an exact source-backed mechanism, owner, key, child/cascade, irreversibility, and recovery contract exists.169- After every existing source, field, ownership, and requirement check passes, an update whose requested values exactly equal the fresh baseline for one unique Name-plus-SetCode export owner returns `NO_OP` without an import ZIP. The result retains input/design hashes and business summary, with null candidate hash and empty inventory; never submit it to Data Loader. Already-restored update rollback follows the same rule. Any real change or create keeps the normal package and approval workflow.170- Keep Fusion writes outside this skill: Run Book owns normalized task intent and orchestration, Data Loader owns immutable preview and approved import, and no import, retry, or cleanup is authorized by static readiness.171172173174175## Inputs176177- `implementation_objective`178- `project_context`179- `setup_task_scope`180- `setup_data_artifacts`181182## Outputs183184- `setup_task_plan`185- `setup_data_routing`186- `validation_checkpoints`187- `skill_run_record`188- `token_usage_record`189190## Implementation Notes191192Use 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.193194For direct task entry containing another active setup-task request, return to the Customer Billing parent scope-confirmation gate before preparing an MTS package. Explicitly excluded document context does not expand the selected task scope.