Manage Legal Addresses Setup Task Guidance
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Legal Addresses under Legal Structures.
Setup Task Skill Contract
- task_code:
XLE_MANAGE_LEGAL_ADDRESSES
- task_name:
Manage Legal Addresses
- parent_skill_id:
erp.financials.legal-structures
- pillar:
ERP
- offering:
Financials
- functional_area:
Legal Structures
- functional_area_code:
ORA_ASK_LEGAL_STRUCTURES
- available_flag:
Y
- export_import_supported_flag:
Y
- csv_export_import_supported_flag:
Y
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when planning, sequencing, exporting, importing, or validating setup data for Manage Legal Addresses under Legal Structures.
Setup Task Metadata
- Task name:
Manage Legal Addresses
- Task code:
XLE_MANAGE_LEGAL_ADDRESSES
- Available:
Y
- Export/import supported:
Y
- CSV export/import supported:
Y
- CSV export/import routing:
supported
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.
- Load the task-local
ora-resource/ora_rule_registry.json and run its referenced input, lookup, dependency, defaulting, design, error-handling, and final-package-readiness checks. The ora-resource graph validates the candidate; it does not create a Fusion mutation.
- Prepare the FSM archive locally using the contract below.
- Hand the exact final archive to
core.data-loader only after the local workflow returns READY_FOR_DATA_LOADER_PREVIEW.
Use this task metadata when invoking those skills:
- Offering:
Financials
- Functional area / Setup Object:
Legal Structures
- Setup task name:
Manage Legal Addresses
- Setup task code:
XLE_MANAGE_LEGAL_ADDRESSES
Local-Only FSM Package Preparation
This assisted workflow prepares a package locally and stops before upload or any Fusion mutation.
- Require a fresh, same-target, same-release, successful same-task FSM export as the immutable baseline. Bind the exact environment and task identity, current
ASM_SETUP_CSV_METADATA.xml, exact CSV member hierarchy, exact header spelling and order, and the exported encoding.
- Re-run the complete task ora-resource graph against the reviewed inputs and baseline. Fail closed with a task-specific package-contract gap if any source, mapping, value, member hierarchy, header, encoding, carrier, or system-blank rule is missing or ambiguous; do not invent a package contract.
- Build a new-rows-only upload archive; the immutable export is reference evidence for metadata, headers, and duplicate checks, never the upload payload. Preserve
ASM_SETUP_CSV_METADATA.xml byte-for-byte and retain the exact exported CSV member hierarchy, header bytes/order, and encoding. In XLE_LE_LEGAL_ADDRESS.csv, include only the reviewed new addresses that passed complete-scope duplicate checks. Keep every companion CSV header-only with zero data rows. Exclude every existing baseline row, including existing addresses, legal entities, establishments, registrations, and functions. Omitting rows from this create package does not request deletion in Fusion. Do not submit an unfiltered export or append new rows to a populated baseline for upload.
- Every new address row must have nonblank
LeFormattedAddress, CreatedByModule set to XLE_CREATE_LE, and a new collision-checked OrigSystemReference. Apply the deterministic formatting contract in ora-resource/ora_defaulting_rules.md: replace every comma in a supplied complete single-line address with /, preserving the other characters and spaces. For component-only input, derive a nonblank value from the reviewed components and resolved country layout; block if the source or mapping is ambiguous. Validate the final CSV value, not just the input or preview.
- Do not copy physical IDs, audit fields, object-version fields, ESS fields, or service-owned values from the baseline or another row. Copy a value only when the task resources explicitly authorize it as a carrier. Keep Fusion-generated
FormattedAddress and FormattedMultilineAddress blank; this blank treatment never applies to LeFormattedAddress.
- Reparse every CSV in the final ZIP. Require its address data-row count and identities to equal exactly the reviewed unique new candidate set, all
LeFormattedAddress values to be populated and normalized, existing data rows included to equal zero, and every companion data-row count to equal zero. Require at least one new row; if all requested addresses already exist, return Existing Match without submitting an empty import. Block a mismatch before Data Loader preview. Produce the immutable archive, SHA-256, per-member baseline/upload row counts, header/metadata fingerprints, and a semantic diff explicitly showing excluded baseline rows and newly authored rows. Record a sanitized package-preparation receipt.
- Any source, mapping, value, package byte, member inventory, or hash change invalidates this preview state and requires the full validation and package-preparation workflow to run again.
- On success, return
READY_FOR_DATA_LOADER_PREVIEW. Do not claim READY_FOR_IMPORT or approval. Stop before upload or mutation and hand the exact immutable archive to core.data-loader, which owns Task Hook validation, preview, explicit approval, archive-hash verification, upload, and initiation. A standalone new-rows-only package is the normal contract for this task, not an exception requiring a baseline-preservation waiver.
Outcome Reporting and Verification
Keep the central Data Loader approval, initiation, monitoring, and report contracts unchanged. Accepted initiation means submitted, not created; return its initiation report without automatic status polling. When the user requests status, results, errors, or verification, use the central monitoring workflow and apply ora-resource/ora_error_handling.md before making a task-level success or failure claim.
Inspect the current, correctly correlated FSM ProcessLog, underlying process completion state, and relevant object counters alongside Data Loader status/errors. A Data Loader error with a still-running FSM process is a status discrepancy, not proof that address creation failed. Missing or incomplete logs leave the task outcome unverified. Confirm exact new-row persistence through a fresh same-target export before claiming the address or a particular field value is present in Fusion. Distinguish the authored LeFormattedAddress from the returned value and Fusion-generated display fields; do not promise the submitted slash string will be displayed verbatim.
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.legal-structures 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.legal-structures.manage-legal-addresses"3name: manage-legal-addresses-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Legal Addresses under the Legal Structures functional area."5layer: "pillar"6pillar: "ERP"7offering: "Financials"8functional_area: "Legal Structures"9functional_area_code: "ORA_ASK_LEGAL_STRUCTURES"10task_code: "XLE_MANAGE_LEGAL_ADDRESSES"11task_name: "Manage Legal Addresses"12parent_skill_id: "erp.financials.legal-structures"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/legal-structures/manage-legal-addresses/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/legal-structures/manage-legal-addresses/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-legal-addresses-setup-task-guidance91---9293# Manage Legal Addresses Setup Task Guidance9495## Purpose9697Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Legal Addresses` under `Legal Structures`.9899## Setup Task Skill Contract100101- task_code: `XLE_MANAGE_LEGAL_ADDRESSES`102- task_name: `Manage Legal Addresses`103- parent_skill_id: `erp.financials.legal-structures`104- pillar: `ERP`105- offering: `Financials`106- functional_area: `Legal Structures`107- functional_area_code: `ORA_ASK_LEGAL_STRUCTURES`108- available_flag: `Y`109- export_import_supported_flag: `Y`110- csv_export_import_supported_flag: `Y`111- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`112113## Usage114115Use this skill when planning, sequencing, exporting, importing, or validating setup data for `Manage Legal Addresses` under `Legal Structures`.116117## Setup Task Metadata118119- Task name: `Manage Legal Addresses`120- Task code: `XLE_MANAGE_LEGAL_ADDRESSES`121- Available: `Y`122- Export/import supported: `Y`123- CSV export/import supported: `Y`124- CSV export/import routing: `supported`125126## CSV Export, Import, and Validation Workflow127128`CSVExportImportSupportedFlag` is `Y` for this task, so route task setup data work through the relevant skills:1291301. Export setup task data with `shared.setup-export.task-level-export`.1312. Validate setup task data with `shared.validation.setup-data-validator`.1323. Validate reference data with `shared.validation.reference-data-validator`.1334. Load the task-local `ora-resource/ora_rule_registry.json` and run its referenced input, lookup, dependency, defaulting, design, error-handling, and final-package-readiness checks. The ora-resource graph validates the candidate; it does not create a Fusion mutation.1345. Prepare the FSM archive locally using the contract below.1356. Hand the exact final archive to `core.data-loader` only after the local workflow returns `READY_FOR_DATA_LOADER_PREVIEW`.136137Use this task metadata when invoking those skills:138139- Offering: `Financials`140- Functional area / Setup Object: `Legal Structures`141- Setup task name: `Manage Legal Addresses`142- Setup task code: `XLE_MANAGE_LEGAL_ADDRESSES`143144### Local-Only FSM Package Preparation145146This assisted workflow prepares a package locally and stops before upload or any Fusion mutation.1471481. Require a fresh, same-target, same-release, successful same-task FSM export as the immutable baseline. Bind the exact environment and task identity, current `ASM_SETUP_CSV_METADATA.xml`, exact CSV member hierarchy, exact header spelling and order, and the exported encoding.1492. Re-run the complete task ora-resource graph against the reviewed inputs and baseline. Fail closed with a task-specific package-contract gap if any source, mapping, value, member hierarchy, header, encoding, carrier, or system-blank rule is missing or ambiguous; do not invent a package contract.1503. Build a new-rows-only upload archive; the immutable export is reference evidence for metadata, headers, and duplicate checks, never the upload payload. Preserve `ASM_SETUP_CSV_METADATA.xml` byte-for-byte and retain the exact exported CSV member hierarchy, header bytes/order, and encoding. In `XLE_LE_LEGAL_ADDRESS.csv`, include only the reviewed new addresses that passed complete-scope duplicate checks. Keep every companion CSV header-only with zero data rows. Exclude every existing baseline row, including existing addresses, legal entities, establishments, registrations, and functions. Omitting rows from this create package does not request deletion in Fusion. Do not submit an unfiltered export or append new rows to a populated baseline for upload.1514. Every new address row must have nonblank `LeFormattedAddress`, `CreatedByModule` set to `XLE_CREATE_LE`, and a new collision-checked `OrigSystemReference`. Apply the deterministic formatting contract in `ora-resource/ora_defaulting_rules.md`: replace every comma in a supplied complete single-line address with `/`, preserving the other characters and spaces. For component-only input, derive a nonblank value from the reviewed components and resolved country layout; block if the source or mapping is ambiguous. Validate the final CSV value, not just the input or preview.1525. Do not copy physical IDs, audit fields, object-version fields, ESS fields, or service-owned values from the baseline or another row. Copy a value only when the task resources explicitly authorize it as a carrier. Keep Fusion-generated `FormattedAddress` and `FormattedMultilineAddress` blank; this blank treatment never applies to `LeFormattedAddress`.1536. Reparse every CSV in the final ZIP. Require its address data-row count and identities to equal exactly the reviewed unique new candidate set, all `LeFormattedAddress` values to be populated and normalized, existing data rows included to equal zero, and every companion data-row count to equal zero. Require at least one new row; if all requested addresses already exist, return Existing Match without submitting an empty import. Block a mismatch before Data Loader preview. Produce the immutable archive, SHA-256, per-member baseline/upload row counts, header/metadata fingerprints, and a semantic diff explicitly showing excluded baseline rows and newly authored rows. Record a sanitized package-preparation receipt.1547. Any source, mapping, value, package byte, member inventory, or hash change invalidates this preview state and requires the full validation and package-preparation workflow to run again.1558. On success, return `READY_FOR_DATA_LOADER_PREVIEW`. Do not claim `READY_FOR_IMPORT` or approval. Stop before upload or mutation and hand the exact immutable archive to `core.data-loader`, which owns Task Hook validation, preview, explicit approval, archive-hash verification, upload, and initiation. A standalone new-rows-only package is the normal contract for this task, not an exception requiring a baseline-preservation waiver.156157### Outcome Reporting and Verification158159Keep the central Data Loader approval, initiation, monitoring, and report contracts unchanged. Accepted initiation means submitted, not created; return its initiation report without automatic status polling. When the user requests status, results, errors, or verification, use the central monitoring workflow and apply `ora-resource/ora_error_handling.md` before making a task-level success or failure claim.160161Inspect the current, correctly correlated FSM ProcessLog, underlying process completion state, and relevant object counters alongside Data Loader status/errors. A Data Loader error with a still-running FSM process is a status discrepancy, not proof that address creation failed. Missing or incomplete logs leave the task outcome unverified. Confirm exact new-row persistence through a fresh same-target export before claiming the address or a particular field value is present in Fusion. Distinguish the authored `LeFormattedAddress` from the returned value and Fusion-generated display fields; do not promise the submitted slash string will be displayed verbatim.162163164## Inputs165166- `implementation_objective`167- `project_context`168- `setup_task_scope`169- `setup_data_artifacts`170171## Outputs172173- `setup_task_plan`174- `setup_data_routing`175- `validation_checkpoints`176- `skill_run_record`177- `token_usage_record`178179## Implementation Notes180181Use the parent functional-area skill `erp.financials.legal-structures` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.