Manage AutoAccounting Rules Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage AutoAccounting Rules under Customer Billing.
Setup Task Skill Contract
- task_code:
AR_MANAGE_AUTOACCOUNTING_RULES
- task_name:
Manage AutoAccounting Rules
- 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 AutoAccounting Rules under Customer Billing.
Business-language requests are sufficient. Do not ask customers to name the FSM task, CSV members, database tables, or loader APIs. Accept requests such as "For Vision Operations, derive Receivable from transaction type and use constant 000 for Department" or "Change the Revenue Product segment from a constant to Standard Lines and leave everything else unchanged."
Customer Interaction and Lifecycle Contract
Resolve the exact business unit, account type, and every accounting segment from fresh task evidence. A create requires the complete segment design for one BuName plus Type. An update requires one exact existing parent and one or more exact child Segment values; preserve every unrequested field, segment, DFF value, and unrelated rule.
Ask one consolidated business question when a required value is missing or ambiguous. Never infer a business unit, account type, segment, source, constant value, chart of accounts, DFF context, or accounting value from conversation history or another environment. One unresolved operation blocks the entire mixed or bulk candidate.
Supported operations are create and update. Physical delete, identity rename, business-unit or account-type movement, and segment identity changes are unsupported. Suppress no-op updates.
BuName, Type, Segment, and SegmentNum are identity values. The five audit columns on each entity are Fusion-owned and must be blank in candidates. Each segment rule must contain exactly one derivation: a compatible TableName, or a value-set-valid Constant, never both and never neither.
Account Types and Sources
Normalize only unambiguous account-type labels to the seeded codes evidenced for this task: BR_FACTOR, BR_REC, BR_REMITTANCE, BR_UNPAID_REC, CHARGES, DEFERRED_TAX, FREIGHT, ORA_PREPAYMENT, REC, REV, SUSPENSE, TAX, UNBILL, and UNEARN.
Normalize supported source labels to canonical package values only when compatible with the selected account type: Transaction Types to RA_CUST_TRX_TYPES, Salesperson to RA_SALESREPS, Bill-to Site to RA_SITE_USES, Standard Lines to RA_STD_TRX_LINES, and Tax to RA_TAXES. A constant derivation uses blank TableName and the confirmed value in Constant.
Source-Backed Task Behavior
- Treat
BuName plus Type as the parent rule identity and require fresh target-environment evidence for the business unit.
- Treat
Segment and SegmentNum as child identity evidence beneath the exact parent; never infer a missing or ambiguous segment from another rule.
- Support create and update only; reject physical delete, identity rename, business-unit or account-type movement, and segment identity changes.
- Require exactly one derivation for each segment row: a compatible
TableName or a validated Constant, never both and never neither.
- Normalize account types and table sources only from the closed, source-backed code sets stated above; ask a follow-up question for an unsupported or ambiguous business label.
- Leave Fusion-owned audit columns blank in candidates and retain their exported values only as read-only baseline evidence.
- Keep DFF columns blank on create and preserve them on update unless the exact deployed context, segment mapping, and value-set evidence are available.
- Preserve all unrequested fields and unrelated rows, suppress no-op updates, and fail closed when any mixed or bulk operation remains unresolved.
- Do not claim a requested target is live-ready unless its complete portable key resolves to exactly one row in the fresh exact-task export. Block a duplicated or conflicting requested target before package generation; preserve byte-identical duplicate rows outside the requested scope without treating them as target evidence.
Preview, Handoff, and Verification
Show a complete normalized preview with action, business unit, account type, every segment name/number, source or constant, DFF changes, preserved values, applied normalization, warnings, and operation counts. Route design confirmation to the active Run Book. Route deterministic package creation, immutable candidate hashing, import approval, submission, monitoring, and result collection exclusively to core.data-loader.
After terminal import success, obtain a fresh exact-task export and reconcile every submitted identity and requested value. Fail verification when a requested row is absent, duplicated, or different, or when a confirmed baseline row changed unexpectedly. Allow unrelated rows created concurrently after the baseline unless they duplicate or alter a requested target.
Customer-configured business units, segment structures, constants, and DFF deployments require fresh target-environment evidence. Public documentation and CodeSearch establish behavior and seeded contracts, not customer-specific contents. DFF values require the exact deployed context, segment-to-AttributeN mapping, and value-set evidence; otherwise keep them blank on create and preserve them on update.
Setup Task Metadata
- Task name:
Manage AutoAccounting Rules
- Task code:
AR_MANAGE_AUTOACCOUNTING_RULES
- 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 AutoAccounting Rules
- Setup task code:
AR_MANAGE_AUTOACCOUNTING_RULES
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.
1---2skill_id: "erp.financials.customer-billing.manage-autoaccounting-rules"3name: manage-autoaccounting-rules-setup-task-guidance4description: "Handles natural-language AutoAccounting requests for exact Receivables business units and account types, including create and update of segment derivation rules, deterministic FSM CSV preparation, governed Data Loader import, and persisted-state verification."5layer: "pillar"6pillar: "ERP"7offering: "Financials"8functional_area: "Customer Billing"9functional_area_code: "ORA_FIN_CUST_BILL"10task_code: "AR_MANAGE_AUTOACCOUNTING_RULES"11task_name: "Manage AutoAccounting Rules"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.2.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-autoaccounting-rules/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-autoaccounting-rules/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:88 - "After the active Run Book and Core Data Loader complete their required preview and approval gates, the authorized FSM adapter may create or update AutoAccounting setup in the approved Fusion environment."89required_privileges:90 - "AR_SET_UP_RECEIVABLES_DEFAULT_DISTRIBUTION_RULE_PRIV or an equivalent privilege inherited through ORA_AR_RECEIVABLES_ADMINISTRATION_DUTY."91 - "ORA_ASM_FUNCTIONAL_SETUPS_USER_ABSTRACT plus task-specific access for FSM CSV export and import."92metadata:93 source: https://skillmd.com/skills/oracle/manage-autoaccounting-rules-setup-task-guidance94---9596<!-- fscr-supported-operations: create, update -->97<!-- fscr-create-fields: AR_AUTO_ACCOUNTING::Attribute1, AR_AUTO_ACCOUNTING::Attribute10, AR_AUTO_ACCOUNTING::Attribute11, AR_AUTO_ACCOUNTING::Attribute12, AR_AUTO_ACCOUNTING::Attribute13, AR_AUTO_ACCOUNTING::Attribute14, AR_AUTO_ACCOUNTING::Attribute15, AR_AUTO_ACCOUNTING::Attribute2, AR_AUTO_ACCOUNTING::Attribute3, AR_AUTO_ACCOUNTING::Attribute4, AR_AUTO_ACCOUNTING::Attribute5, AR_AUTO_ACCOUNTING::Attribute6, AR_AUTO_ACCOUNTING::Attribute7, AR_AUTO_ACCOUNTING::Attribute8, AR_AUTO_ACCOUNTING::Attribute9, AR_AUTO_ACCOUNTING::AttributeCategory, AR_AUTO_ACCOUNTING::BuName, AR_AUTO_ACCOUNTING::Type, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute1, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute10, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute11, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute12, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute13, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute14, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute15, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute2, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute3, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute4, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute5, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute6, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute7, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute8, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute9, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::AttributeCategory, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Constant, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Segment, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::SegmentNum, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::TableName -->98<!-- fscr-update-fields: AR_AUTO_ACCOUNTING::Attribute1, AR_AUTO_ACCOUNTING::Attribute10, AR_AUTO_ACCOUNTING::Attribute11, AR_AUTO_ACCOUNTING::Attribute12, AR_AUTO_ACCOUNTING::Attribute13, AR_AUTO_ACCOUNTING::Attribute14, AR_AUTO_ACCOUNTING::Attribute15, AR_AUTO_ACCOUNTING::Attribute2, AR_AUTO_ACCOUNTING::Attribute3, AR_AUTO_ACCOUNTING::Attribute4, AR_AUTO_ACCOUNTING::Attribute5, AR_AUTO_ACCOUNTING::Attribute6, AR_AUTO_ACCOUNTING::Attribute7, AR_AUTO_ACCOUNTING::Attribute8, AR_AUTO_ACCOUNTING::Attribute9, AR_AUTO_ACCOUNTING::AttributeCategory, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute1, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute10, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute11, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute12, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute13, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute14, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute15, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute2, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute3, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute4, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute5, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute6, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute7, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute8, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Attribute9, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::AttributeCategory, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::Constant, ORA_LE_AR_AUTO_ACCOUNTING_SEGMENT::TableName -->99100# Manage AutoAccounting Rules Setup Task Guidance101102## Purpose103104Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage AutoAccounting Rules` under `Customer Billing`.105106## Setup Task Skill Contract107108- task_code: `AR_MANAGE_AUTOACCOUNTING_RULES`109- task_name: `Manage AutoAccounting Rules`110- parent_skill_id: `erp.financials.customer-billing`111- pillar: `ERP`112- offering: `Financials`113- functional_area: `Customer Billing`114- functional_area_code: `ORA_FIN_CUST_BILL`115- available_flag: `Y`116- export_import_supported_flag: `Y`117- csv_export_import_supported_flag: `Y`118- dataloader_import_mode: `FSM`119- businessObject: ``120- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`121122## Usage123124Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage AutoAccounting Rules` under `Customer Billing`.125126Business-language requests are sufficient. Do not ask customers to name the FSM task, CSV members, database tables, or loader APIs. Accept requests such as "For Vision Operations, derive Receivable from transaction type and use constant 000 for Department" or "Change the Revenue Product segment from a constant to Standard Lines and leave everything else unchanged."127128## Customer Interaction and Lifecycle Contract129130Resolve the exact business unit, account type, and every accounting segment from fresh task evidence. A create requires the complete segment design for one `BuName` plus `Type`. An update requires one exact existing parent and one or more exact child `Segment` values; preserve every unrequested field, segment, DFF value, and unrelated rule.131132Ask one consolidated business question when a required value is missing or ambiguous. Never infer a business unit, account type, segment, source, constant value, chart of accounts, DFF context, or accounting value from conversation history or another environment. One unresolved operation blocks the entire mixed or bulk candidate.133134Supported operations are create and update. Physical delete, identity rename, business-unit or account-type movement, and segment identity changes are unsupported. Suppress no-op updates.135136`BuName`, `Type`, `Segment`, and `SegmentNum` are identity values. The five audit columns on each entity are Fusion-owned and must be blank in candidates. Each segment rule must contain exactly one derivation: a compatible `TableName`, or a value-set-valid `Constant`, never both and never neither.137138## Account Types and Sources139140Normalize only unambiguous account-type labels to the seeded codes evidenced for this task: `BR_FACTOR`, `BR_REC`, `BR_REMITTANCE`, `BR_UNPAID_REC`, `CHARGES`, `DEFERRED_TAX`, `FREIGHT`, `ORA_PREPAYMENT`, `REC`, `REV`, `SUSPENSE`, `TAX`, `UNBILL`, and `UNEARN`.141142Normalize supported source labels to canonical package values only when compatible with the selected account type: Transaction Types to `RA_CUST_TRX_TYPES`, Salesperson to `RA_SALESREPS`, Bill-to Site to `RA_SITE_USES`, Standard Lines to `RA_STD_TRX_LINES`, and Tax to `RA_TAXES`. A constant derivation uses blank `TableName` and the confirmed value in `Constant`.143144## Source-Backed Task Behavior145146- Treat `BuName` plus `Type` as the parent rule identity and require fresh target-environment evidence for the business unit.147- Treat `Segment` and `SegmentNum` as child identity evidence beneath the exact parent; never infer a missing or ambiguous segment from another rule.148- Support create and update only; reject physical delete, identity rename, business-unit or account-type movement, and segment identity changes.149- Require exactly one derivation for each segment row: a compatible `TableName` or a validated `Constant`, never both and never neither.150- Normalize account types and table sources only from the closed, source-backed code sets stated above; ask a follow-up question for an unsupported or ambiguous business label.151- Leave Fusion-owned audit columns blank in candidates and retain their exported values only as read-only baseline evidence.152- Keep DFF columns blank on create and preserve them on update unless the exact deployed context, segment mapping, and value-set evidence are available.153- Preserve all unrequested fields and unrelated rows, suppress no-op updates, and fail closed when any mixed or bulk operation remains unresolved.154- Do not claim a requested target is live-ready unless its complete portable key resolves to exactly one row in the fresh exact-task export. Block a duplicated or conflicting requested target before package generation; preserve byte-identical duplicate rows outside the requested scope without treating them as target evidence.155156## Preview, Handoff, and Verification157158Show a complete normalized preview with action, business unit, account type, every segment name/number, source or constant, DFF changes, preserved values, applied normalization, warnings, and operation counts. Route design confirmation to the active Run Book. Route deterministic package creation, immutable candidate hashing, import approval, submission, monitoring, and result collection exclusively to `core.data-loader`.159160After terminal import success, obtain a fresh exact-task export and reconcile every submitted identity and requested value. Fail verification when a requested row is absent, duplicated, or different, or when a confirmed baseline row changed unexpectedly. Allow unrelated rows created concurrently after the baseline unless they duplicate or alter a requested target.161162Customer-configured business units, segment structures, constants, and DFF deployments require fresh target-environment evidence. Public documentation and CodeSearch establish behavior and seeded contracts, not customer-specific contents. DFF values require the exact deployed context, segment-to-`AttributeN` mapping, and value-set evidence; otherwise keep them blank on create and preserve them on update.163164## Setup Task Metadata165166- Task name: `Manage AutoAccounting Rules`167- Task code: `AR_MANAGE_AUTOACCOUNTING_RULES`168- Available: `Y`169- Export/import supported: `Y`170- CSV export/import supported: `Y`171- CSV export/import routing: `supported`172- Data Loader import mode: `FSM`173- Business Object: ``174175## CSV Export, Import, and Validation Workflow176177`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:1781791. Export setup task data with `shared.setup-export.task-level-export`.1802. Validate setup task data with `shared.validation.setup-data-validator`.1813. Validate reference data with `shared.validation.reference-data-validator`.1824. Import setup task data with `core.data-loader`.183184Use this task metadata when invoking those skills:185186- Offering: `Financials`187- Functional area / Setup Object: `Customer Billing`188- Setup task name: `Manage AutoAccounting Rules`189- Setup task code: `AR_MANAGE_AUTOACCOUNTING_RULES`190191192193194## Inputs195196- `implementation_objective`197- `project_context`198- `setup_task_scope`199- `setup_data_artifacts`200201## Outputs202203- `setup_task_plan`204- `setup_data_routing`205- `validation_checkpoints`206- `skill_run_record`207- `token_usage_record`208209## Implementation Notes210211Use 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.