# Manage Legal Reporting Unit Registrations Setup Task Guidance

> Provides task-specific setup guidance for Manage Legal Reporting Unit Registrations under the Legal Structures functional area.

- Skill: `oracle/manage-legal-reporting-unit-registrations-setup-task-guidanc` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx get-skill add oracle/manage-legal-reporting-unit-registrations-setup-task-guidanc`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/manage-legal-reporting-unit-registrations-setup-task-guidanc/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/manage-legal-reporting-unit-registrations-setup-task-guidanc

---


# Manage Legal Reporting Unit Registrations Setup Task Guidance

## Purpose

Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Legal Reporting Unit Registrations` under `Legal Structures`.

## Setup Task Skill Contract

- task_code: `XLE_MANAGE_LEGAL_REPORTING_UNIT_REGISTRATIONS`
- task_name: `Manage Legal Reporting Unit Registrations`
- 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 Reporting Unit Registrations` under `Legal Structures`.

## Setup Task Metadata

- Task name: `Manage Legal Reporting Unit Registrations`
- Task code: `XLE_MANAGE_LEGAL_REPORTING_UNIT_REGISTRATIONS`
- 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:

1. Export setup task data with `shared.setup-export.task-level-export`.
2. Validate setup task data with `shared.validation.setup-data-validator`.
3. Validate reference data with `shared.validation.reference-data-validator`.
4. 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.
5. Prepare the FSM archive locally using the contract below.
6. 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 Reporting Unit Registrations`
- Setup task code: `XLE_MANAGE_LEGAL_REPORTING_UNIT_REGISTRATIONS`

### Local-Only FSM Package Preparation

This assisted workflow prepares a package locally and stops before upload or any Fusion mutation.

1. 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.
2. 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 parent/child rule is missing or ambiguous; do not invent a package contract.
3. Build the smallest supported LRU-registration delta from the task resources. Preserve the exact unchanged legal-entity and legal-reporting-unit parent rows; author only the supported registration delta in `ORA_XLE_LEGAL_REPORTING_UNIT_REGISTRATION.csv`; keep `ORA_XLE_LEGAL_REPORTING_UNIT_REGISTRATION_FUNCTION.csv` header-only with zero candidate rows; and preserve every unrelated row and untouched archive member.
4. 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.
5. Produce a ZIP-valid immutable FSM archive, its SHA-256 digest, a member inventory, a row/member semantic diff against the baseline, and a sanitized package-preparation receipt containing no secrets or sensitive payload values.
6. 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.
7. 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.


## 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.

