Manage Party Usage Lookups
Purpose
Provides task-specific setup planning, routing, export, import, and validation guidance for Manage Party Usage Lookups under Trading Community Foundation.
Setup Task Skill Contract
- task_code:
HZ_MANAGE_PARTY_USAGE_LOOKUPS
- task_name:
Manage Party Usage Lookups
- parent_skill_id:
cx.customer-data-management.trading-community-foundation
- pillar:
CX
- offering:
Customer Data Management
- functional_area:
Trading Community Foundation
- functional_area_code:
ORA_HZ_CDM_FOUNDATION
- 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 Party Usage Lookups under Trading Community Foundation.
Setup Task Metadata
- Task name:
Manage Party Usage Lookups
- Task code:
HZ_MANAGE_PARTY_USAGE_LOOKUPS
- 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.
- 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.
- Route every import exclusively through
core.data-loader.
- For an FSM ZIP, preserve the archive unchanged, require the exact case-sensitive member basename
ASM_SETUP_CSV_METADATA.xml, and require exactly one metadata task identity equal to HZ_MANAGE_PARTY_USAGE_LOOKUPS.
- Let Core Data Loader prepare the final immutable upload artifact, then invoke its
data-load Task Hook immediately before approval and upload. Require the Task Hook validation envelope to remain bound to that archive's SHA-256.
- Require the user's separate explicit approval of the exact immutable preview. Any source, archive, environment, task identity, validation result, or approval change restarts the Core Data Loader and Task Hook lifecycle.
- Core Data Loader owns UCM upload, initiation payload construction, endpoint and FSM routing selection, accepted-request reporting, and later status diagnostics. This pillar skill must not select an adapter, endpoint, loader routing field, or retry policy.
Use this task metadata:
- Offering:
Customer Data Management
- Functional area / Setup Object:
Trading Community Foundation
- Setup task name:
Manage Party Usage Lookups
- Setup task code:
HZ_MANAGE_PARTY_USAGE_LOOKUPS
Inputs
natural_language_request
fusion_environment_context
lookup_type_or_meaning
lookup_code_and_named_changes
setup_data_artifact
project_id
Outputs
lookup_result
setup_data_result
diagnostics
skill_run_record
token_usage_record
Implementation Notes
Use the parent functional-area skill cx.customer-data-management.trading-community-foundation for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.
Ownership and review
- Owner: CX Customer Data Management pillar team.
- Functional reviewer: CX Customer Data Management Pillar Lead or a Trading Community Foundation SME.
- Framework reviewer: FSCR A-Team/core reviewer.
- QA reviewer: required when lookup read, mutation, validation, export, or import behavior changes.
Reviewer guidance is in the body because the current manifest schema has owner_team but no reviewer field.
Task-specific lookup baseline
| Lookup type |
Meaning or scope |
Configuration level |
Evidence and restriction |
HZ_PARTY_USAGE_RULE_TYPE |
Party Usage Rule Type |
System (S) |
Fixed OOTB task member; Standard lookup. |
HZ_PARTY_USAGE_TYPE |
Party Usage Type |
System (S) |
Fixed OOTB task member; Standard lookup. |
HZ_PARTY_USG_FR_MEMBER_TYPE |
Party Usage Filter Rule Member Type |
System (S) |
Fixed OOTB task member; Standard lookup. |
HZ_PARTY_USG_SELECT_CRITERIA |
Party Usage Selection Criteria |
System (S) |
Fixed OOTB task member; Standard lookup. |
This is a closed four-type OOTB inventory established by the exact-task Fusion UI and reconfirmed by read-only GETs from the configured environment. The task does not provide an operation for adding a lookup type. All four types resolve through /fscmRestApi/resources/11.13.18.05/standardLookups/{LookupType} and currently contain only seeded-origin codes. A current GET must reconfirm the category and configuration level before a live operation. Missing or changed evidence is catalog_or_metadata_mismatch; never add a type based on prefix, module, or meaning. See ora_reference_lookups.md.
Supported and unsupported operations
| Request |
Support |
| List lookup types belonging to this task |
Return the closed four-type baseline and current read results; never add a task member. |
| Show codes and values or retrieve one exact code |
Read-only, no approval, after exact task membership and lookup-category resolution. |
| Create or delete a lookup type or lookup code |
Unsupported because all four types are System. |
| Update a lookup type or code |
Only Meaning, because all four types are System and both current Oracle configuration rules and REST describe must permit the field. |
| Export task setup data |
Supported through shared.setup-export.task-level-export because the exact catalog CSV flag is Y. |
| Validate and import task setup data |
Supported through core.data-loader only after shared validation, Task Hook validation of the exact immutable archive, and separate explicit approval. |
| Update description, display sequence, enabled state, dates, tag, module, REST security, configuration level, category, seeded identity, lookup type, or lookup code |
Unsupported for these System types; refuse before preview. |
Never silently upsert. Treat CreatedBy == SEED_DATA_FROM_APPLICATION as seeded-origin evidence. LastUpdatedBy identifies only the most recent updater and must never convert a seeded code into a custom code.
Configuration-level and manual mutation contract
- All four task members are System. Do not create or delete types or codes.
- Permit only lookup-type or lookup-code
Meaning after both current Oracle configuration rules and REST describe confirm it.
- Category is
standardLookups for all four confirmed members. If a current exact GET no longer resolves there, stop; do not fall through to another category.
- A manual PATCH payload must contain only
Meaning. Never include Description, DisplaySequence, EnabledFlag, StartDateActive, EndDateActive, Tag, ModuleId, RestAccessSecured, CustomizationLevel, LookupType, or LookupCode.
Every manual mutation must:
- Resolve exactly one configured Fusion environment.
- GET the exact lookup type and exact code when applicable.
- Retrieve or use current cached describe metadata for the resolved resource family.
- Validate task membership, Standard category, System level,
CreatedBy seeded origin, and current REST describe support for Meaning.
- Show one exact redacted preview containing environment, method, endpoint, before/after values, payload, impact, and preview fingerprint.
- Require explicit approval bound to that environment, target, method, payload, and fingerprint.
- Send exactly one POST, PATCH, or DELETE through
core.fusion-api.apps-common and core.fusion-api.rest-api-client.
- Never automatically retry a mutation and never enable upsert.
- Verify with a separate GET.
- Report verified success, unverified success, refusal, or classified failure distinctly.
Read-only listing and retrieval require no approval.
Task CSV export contract
Route export to shared.setup-export.task-level-export with exact TaskCode: HZ_MANAGE_PARTY_USAGE_LOOKUPS. The owning exporter must create one task CSV export, capture and monitor its ProcessId, download immutable FileContent only after success, retrieve ProcessLog after failure, and save the ZIP or diagnostic under the supplied project workspace. Do not implement export HTTP, polling, or ZIP processing here.
FSM ZIP validation and import contract
- Run
shared.validation.setup-data-validator and shared.validation.reference-data-validator for task-local setup and reference checks.
- Route the import only to
core.data-loader; this pillar skill supplies the exact task context and rules but never selects or invokes an import adapter or endpoint.
- Detect an FSM ZIP only when a member has the exact case-sensitive basename
ASM_SETUP_CSV_METADATA.xml.
- Reject missing, duplicate, unreadable, encrypted, unsafe-path, or ambiguous metadata.
- Parse metadata without rewriting the archive and require exactly one task identity equal to
HZ_MANAGE_PARTY_USAGE_LOOKUPS.
- Preserve the archive bytes and SHA-256 through validation, Task Hook preview, approval, and execution.
- After Core Data Loader prepares the final immutable upload artifact, require its
data-load Task Hook to evaluate this task's compiled ora-resource rules and issue the validation envelope bound to the exact archive SHA-256.
- Require a later standalone explicit approval of that exact immutable preview. A changed source, archive, environment, task identity, rule result, or approval invalidates the envelope and restarts validation.
- Let Core Data Loader own UCM upload, FSM initiation routing and payload construction, accepted-request reporting, and any later status or ProcessLog retrieval. Do not reconstruct its envelope or locally choose an endpoint, adapter, routing field, or retry behavior.
- Submit only once under the current Core Data Loader contract. If Task Hook validation or approval is missing, stale, or mismatched, stop with
approval_blocker before any POST.
- Treat a later Run Book or Journey
updateProgress failure as a separate synchronization result. Do not change an accepted FSM import to failed, and never retry or resubmit the import because progress synchronization failed.
Natural prompts
Show the Party Usage Lookups in the configured environment.
Show the values for <lookup meaning or exact lookup type>.
Change the meaning of <code> in <lookup type>.
Export Manage Party Usage Lookups setup data.
Validate and import this Manage Party Usage Lookups export.
Resolve an unambiguous request directly; do not ask the user to choose an internal operation name.
Error and diagnostic contract
| Failure class |
Use |
input_validation |
Missing environment, invalid Meaning, non-Meaning manual field, changed artifact, or unsafe ZIP. |
catalog_or_metadata_mismatch |
Task membership, category, level, describe, exact TaskCode, CSV flag, or adapter contract cannot be proven. |
auth_expired_or_invalid |
Cached authentication rejected; refresh once only under repository cache policy. |
authorization_or_privilege |
Access remains denied or the task/resource privilege is missing. |
transport_or_environment |
Environment, VPN, DNS, or connection failure. Retry only bounded reads. |
fusion_api_error |
Fusion rejects the one approved request; report status and ECID when available. |
process_timeout |
Export/import polling window expires; preserve TaskCode, ProcessId, last status, and next-check path. |
process_failed |
Export/import completes with errors; preserve ProcessLog/status and partial results. |
artifact_persistence |
A required ZIP, diagnostic, result, run record, or token log cannot be saved. |
approval_blocker |
Preview is missing, stale, changed, or declined. |
Durable diagnostics include status, stage, failure class, message, recommended action, environment, redacted endpoint, artifact references, ProcessId/ECID, completed checks, and verified side effects. Never persist credentials, tokens, authorization headers, customer data, signed URLs, or sensitive payloads.
Synthetic behavior checks
| Scenario |
Expected result |
| General task read |
Return exactly the closed four-type baseline and current read results; do not infer additions. |
| Create, delete, or System field other than Meaning |
Refuse before preview even if generic REST describe marks it updatable. |
| Meaning update |
Exact GET, Standard/System/seed/describe validation, one preview, approval, one PATCH, and separate GET verification. |
| Wrong-task FSM ZIP |
Refuse before import because metadata does not equal HZ_MANAGE_PARTY_USAGE_LOOKUPS. |
| Task-local import route selection |
Refuse before POST; Core Data Loader owns endpoint, adapter, routing-field, and retry selection. |
| Missing or stale Task Hook validation envelope |
Fail closed with approval_blocker; do not upload, initiate, or reconstruct an envelope. |
| Valid exact-task FSM archive |
Preserve bytes and hash, pass exact task context to Core Data Loader, complete Task Hook validation and separate approval, then let Core Data Loader execute once. |
Persistence
When project_id is supplied, persist artifacts under the manifest paths, append a run record under project/{project_id}/state/runs, and append token usage under the shared token log. Repository-only authoring does not create a project workspace. Fail closed when required authority, membership, category, metadata, privilege, adapter, approval, or safe destination evidence is absent.
1---2skill_id: "cx.customer-data-management.trading-community-foundation.manage-party-usage-lookups"3name: manage-party-usage-lookups-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Party Usage Lookups under the Trading Community Foundation functional area."5layer: "pillar"6pillar: "CX"7offering: "Customer Data Management"8functional_area: "Trading Community Foundation"9functional_area_code: "ORA_HZ_CDM_FOUNDATION"10task_code: "HZ_MANAGE_PARTY_USAGE_LOOKUPS"11task_name: "Manage Party Usage Lookups"12parent_skill_id: "cx.customer-data-management.trading-community-foundation"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: "CX customer data management 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/cx/customer-data-management/trading-community-foundation/manage-party-usage-lookups/current/"70 versioning_policy: "major-new-version-minor-confirm-update"71 - artifact_type: "validation_result"72 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/manage-party-usage-lookups/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-party-usage-lookups-setup-task-guidance91---9293# Manage Party Usage Lookups9495## Purpose9697Provides task-specific setup planning, routing, export, import, and validation guidance for `Manage Party Usage Lookups` under `Trading Community Foundation`.9899## Setup Task Skill Contract100101- task_code: `HZ_MANAGE_PARTY_USAGE_LOOKUPS`102- task_name: `Manage Party Usage Lookups`103- parent_skill_id: `cx.customer-data-management.trading-community-foundation`104- pillar: `CX`105- offering: `Customer Data Management`106- functional_area: `Trading Community Foundation`107- functional_area_code: `ORA_HZ_CDM_FOUNDATION`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 Party Usage Lookups` under `Trading Community Foundation`.116117## Setup Task Metadata118119- Task name: `Manage Party Usage Lookups`120- Task code: `HZ_MANAGE_PARTY_USAGE_LOOKUPS`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.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. Route every import exclusively through `core.data-loader`.1345. For an FSM ZIP, preserve the archive unchanged, require the exact case-sensitive member basename `ASM_SETUP_CSV_METADATA.xml`, and require exactly one metadata task identity equal to `HZ_MANAGE_PARTY_USAGE_LOOKUPS`.1356. Let Core Data Loader prepare the final immutable upload artifact, then invoke its `data-load` Task Hook immediately before approval and upload. Require the Task Hook validation envelope to remain bound to that archive's SHA-256.1367. Require the user's separate explicit approval of the exact immutable preview. Any source, archive, environment, task identity, validation result, or approval change restarts the Core Data Loader and Task Hook lifecycle.1378. Core Data Loader owns UCM upload, initiation payload construction, endpoint and FSM routing selection, accepted-request reporting, and later status diagnostics. This pillar skill must not select an adapter, endpoint, loader routing field, or retry policy.138139Use this task metadata:140141- Offering: `Customer Data Management`142- Functional area / Setup Object: `Trading Community Foundation`143- Setup task name: `Manage Party Usage Lookups`144- Setup task code: `HZ_MANAGE_PARTY_USAGE_LOOKUPS`145146## Inputs147148- `natural_language_request`149- `fusion_environment_context`150- `lookup_type_or_meaning`151- `lookup_code_and_named_changes`152- `setup_data_artifact`153- `project_id`154155## Outputs156157- `lookup_result`158- `setup_data_result`159- `diagnostics`160- `skill_run_record`161- `token_usage_record`162163## Implementation Notes164165Use the parent functional-area skill `cx.customer-data-management.trading-community-foundation` for functional-area sequencing and scope decisions. Track token usage for any generated project artifact or skill-run record using the manifest policy.166167## Ownership and review168169- Owner: CX Customer Data Management pillar team.170- Functional reviewer: CX Customer Data Management Pillar Lead or a Trading Community Foundation SME.171- Framework reviewer: FSCR A-Team/core reviewer.172- QA reviewer: required when lookup read, mutation, validation, export, or import behavior changes.173174Reviewer guidance is in the body because the current manifest schema has `owner_team` but no reviewer field.175176## Task-specific lookup baseline177178| Lookup type | Meaning or scope | Configuration level | Evidence and restriction |179|---|---|---|---|180| `HZ_PARTY_USAGE_RULE_TYPE` | Party Usage Rule Type | System (`S`) | Fixed OOTB task member; Standard lookup. |181| `HZ_PARTY_USAGE_TYPE` | Party Usage Type | System (`S`) | Fixed OOTB task member; Standard lookup. |182| `HZ_PARTY_USG_FR_MEMBER_TYPE` | Party Usage Filter Rule Member Type | System (`S`) | Fixed OOTB task member; Standard lookup. |183| `HZ_PARTY_USG_SELECT_CRITERIA` | Party Usage Selection Criteria | System (`S`) | Fixed OOTB task member; Standard lookup. |184185This is a closed four-type OOTB inventory established by the exact-task Fusion UI and reconfirmed by read-only GETs from the configured environment. The task does not provide an operation for adding a lookup type. All four types resolve through `/fscmRestApi/resources/11.13.18.05/standardLookups/{LookupType}` and currently contain only seeded-origin codes. A current GET must reconfirm the category and configuration level before a live operation. Missing or changed evidence is `catalog_or_metadata_mismatch`; never add a type based on prefix, module, or meaning. See [ora_reference_lookups.md](ora-resource/ora_reference_lookups.md).186187## Supported and unsupported operations188189| Request | Support |190|---|---|191| List lookup types belonging to this task | Return the closed four-type baseline and current read results; never add a task member. |192| Show codes and values or retrieve one exact code | Read-only, no approval, after exact task membership and lookup-category resolution. |193| Create or delete a lookup type or lookup code | Unsupported because all four types are System. |194| Update a lookup type or code | Only `Meaning`, because all four types are System and both current Oracle configuration rules and REST describe must permit the field. |195| Export task setup data | Supported through `shared.setup-export.task-level-export` because the exact catalog CSV flag is `Y`. |196| Validate and import task setup data | Supported through `core.data-loader` only after shared validation, Task Hook validation of the exact immutable archive, and separate explicit approval. |197| Update description, display sequence, enabled state, dates, tag, module, REST security, configuration level, category, seeded identity, lookup type, or lookup code | Unsupported for these System types; refuse before preview. |198199Never silently upsert. Treat `CreatedBy == SEED_DATA_FROM_APPLICATION` as seeded-origin evidence. `LastUpdatedBy` identifies only the most recent updater and must never convert a seeded code into a custom code.200201## Configuration-level and manual mutation contract202203- All four task members are System. Do not create or delete types or codes.204- Permit only lookup-type or lookup-code `Meaning` after both current Oracle configuration rules and REST describe confirm it.205- Category is `standardLookups` for all four confirmed members. If a current exact GET no longer resolves there, stop; do not fall through to another category.206- A manual PATCH payload must contain only `Meaning`. Never include `Description`, `DisplaySequence`, `EnabledFlag`, `StartDateActive`, `EndDateActive`, `Tag`, `ModuleId`, `RestAccessSecured`, `CustomizationLevel`, `LookupType`, or `LookupCode`.207208Every manual mutation must:2092101. Resolve exactly one configured Fusion environment.2112. GET the exact lookup type and exact code when applicable.2123. Retrieve or use current cached describe metadata for the resolved resource family.2134. Validate task membership, Standard category, System level, `CreatedBy` seeded origin, and current REST describe support for `Meaning`.2145. Show one exact redacted preview containing environment, method, endpoint, before/after values, payload, impact, and preview fingerprint.2156. Require explicit approval bound to that environment, target, method, payload, and fingerprint.2167. Send exactly one POST, PATCH, or DELETE through `core.fusion-api.apps-common` and `core.fusion-api.rest-api-client`.2178. Never automatically retry a mutation and never enable upsert.2189. Verify with a separate GET.21910. Report verified success, unverified success, refusal, or classified failure distinctly.220221Read-only listing and retrieval require no approval.222223## Task CSV export contract224225Route export to `shared.setup-export.task-level-export` with exact `TaskCode: HZ_MANAGE_PARTY_USAGE_LOOKUPS`. The owning exporter must create one task CSV export, capture and monitor its `ProcessId`, download immutable `FileContent` only after success, retrieve `ProcessLog` after failure, and save the ZIP or diagnostic under the supplied project workspace. Do not implement export HTTP, polling, or ZIP processing here.226227## FSM ZIP validation and import contract2282291. Run `shared.validation.setup-data-validator` and `shared.validation.reference-data-validator` for task-local setup and reference checks.2302. Route the import only to `core.data-loader`; this pillar skill supplies the exact task context and rules but never selects or invokes an import adapter or endpoint.2313. Detect an FSM ZIP only when a member has the exact case-sensitive basename `ASM_SETUP_CSV_METADATA.xml`.2324. Reject missing, duplicate, unreadable, encrypted, unsafe-path, or ambiguous metadata.2335. Parse metadata without rewriting the archive and require exactly one task identity equal to `HZ_MANAGE_PARTY_USAGE_LOOKUPS`.2346. Preserve the archive bytes and SHA-256 through validation, Task Hook preview, approval, and execution.2357. After Core Data Loader prepares the final immutable upload artifact, require its `data-load` Task Hook to evaluate this task's compiled `ora-resource` rules and issue the validation envelope bound to the exact archive SHA-256.2368. Require a later standalone explicit approval of that exact immutable preview. A changed source, archive, environment, task identity, rule result, or approval invalidates the envelope and restarts validation.2379. Let Core Data Loader own UCM upload, FSM initiation routing and payload construction, accepted-request reporting, and any later status or ProcessLog retrieval. Do not reconstruct its envelope or locally choose an endpoint, adapter, routing field, or retry behavior.23810. Submit only once under the current Core Data Loader contract. If Task Hook validation or approval is missing, stale, or mismatched, stop with `approval_blocker` before any POST.23911. Treat a later Run Book or Journey `updateProgress` failure as a separate synchronization result. Do not change an accepted FSM import to failed, and never retry or resubmit the import because progress synchronization failed.240241## Natural prompts242243- `Show the Party Usage Lookups in the configured environment.`244- `Show the values for <lookup meaning or exact lookup type>.`245- `Change the meaning of <code> in <lookup type>.`246- `Export Manage Party Usage Lookups setup data.`247- `Validate and import this Manage Party Usage Lookups export.`248249Resolve an unambiguous request directly; do not ask the user to choose an internal operation name.250251## Error and diagnostic contract252253| Failure class | Use |254|---|---|255| `input_validation` | Missing environment, invalid Meaning, non-Meaning manual field, changed artifact, or unsafe ZIP. |256| `catalog_or_metadata_mismatch` | Task membership, category, level, describe, exact TaskCode, CSV flag, or adapter contract cannot be proven. |257| `auth_expired_or_invalid` | Cached authentication rejected; refresh once only under repository cache policy. |258| `authorization_or_privilege` | Access remains denied or the task/resource privilege is missing. |259| `transport_or_environment` | Environment, VPN, DNS, or connection failure. Retry only bounded reads. |260| `fusion_api_error` | Fusion rejects the one approved request; report status and ECID when available. |261| `process_timeout` | Export/import polling window expires; preserve TaskCode, ProcessId, last status, and next-check path. |262| `process_failed` | Export/import completes with errors; preserve ProcessLog/status and partial results. |263| `artifact_persistence` | A required ZIP, diagnostic, result, run record, or token log cannot be saved. |264| `approval_blocker` | Preview is missing, stale, changed, or declined. |265266Durable diagnostics include status, stage, failure class, message, recommended action, environment, redacted endpoint, artifact references, ProcessId/ECID, completed checks, and verified side effects. Never persist credentials, tokens, authorization headers, customer data, signed URLs, or sensitive payloads.267268## Synthetic behavior checks269270| Scenario | Expected result |271|---|---|272| General task read | Return exactly the closed four-type baseline and current read results; do not infer additions. |273| Create, delete, or System field other than Meaning | Refuse before preview even if generic REST describe marks it updatable. |274| Meaning update | Exact GET, Standard/System/seed/describe validation, one preview, approval, one PATCH, and separate GET verification. |275| Wrong-task FSM ZIP | Refuse before import because metadata does not equal `HZ_MANAGE_PARTY_USAGE_LOOKUPS`. |276| Task-local import route selection | Refuse before POST; Core Data Loader owns endpoint, adapter, routing-field, and retry selection. |277| Missing or stale Task Hook validation envelope | Fail closed with `approval_blocker`; do not upload, initiate, or reconstruct an envelope. |278| Valid exact-task FSM archive | Preserve bytes and hash, pass exact task context to Core Data Loader, complete Task Hook validation and separate approval, then let Core Data Loader execute once. |279280## Persistence281282When `project_id` is supplied, persist artifacts under the manifest paths, append a run record under `project/{project_id}/state/runs`, and append token usage under the shared token log. Repository-only authoring does not create a project workspace. Fail closed when required authority, membership, category, metadata, privilege, adapter, approval, or safe destination evidence is absent.