Import Trading Community Data
Purpose
Prepare and execute one governed CX Import Management activity for one exact Trading Community object. Support CSV generation and validation, immutable preview, approved submission, bounded monitoring, diagnosis, and post-import verification. Asset, Asset Contact, and the UI-labeled Asset Team Member object are supported; their exact target codes are Assets, AssetContact, and AssetResource.
Required reading
- Read
references/object-profiles.json only to resolve the exact Import Management object code and post-import verification strategy.
- Read all six
ora-resource files and compile/use ora_rule_registry.json through Task Hook.
- Read
core/data-loader/SKILL.md; it owns source transport review, the canonical immutable digest, Task Hook validation, and approval authorization before any import adapter runs.
- Read
core/fusion-api/rest-api-client/SKILL.md and its routed Fusion REST reference before resolving live object metadata or verifying records.
- Read
core/fusion-api/cx-import-export-management/SKILL.md and its required reference before mode-aware execution or monitoring.
- Only when the user asks to generate a CSV or explicitly validate its data, also read
references/column-contracts.json, references/field-contracts.json, and the matching template under assets/templates/.
Selection gates
- For every supplied or generated CSV, select exactly one Import Management
object code and one exact job-level
ImportMode without inspecting supplied
data rows. ImportMode is routing metadata, not a CSV field-validation result.
Do not infer it from the supplied filename, columns, or values.
- The remaining selection gates apply only to generation or an explicit
data-validation request. Never infer
Account from Organization, or
Contact from Person; ask the user to choose because their generated import
contracts are functionally different.
- Select exactly one allowed parent for a child object.
Household is a parent identity only and is not a top-level object supported by this skill.
- Reject missing, ambiguous, or unsupported operations. Treat
update,
create-or-update, or create and update as CREATE_RECORD, create as
CREATE_ONLY, and
literal delete as DELETE_RECORD. Bind the exact code into the immutable
preview and the live Import Management activity.
- Enforce
fixed-high for Classification Code, Hierarchy, and Hierarchy Member. Enforce fixed-low for Resolution Link and Resolution Link Member. Other profiles may use low or high volume; use the profile default unless the user chooses otherwise.
- Hierarchy and Hierarchy Member generation or explicit data validation support
create, update, and delete. Their update route uses
CREATE_RECORD; their
delete route uses DELETE_RECORD, identifier-only rows, exact-target checks,
destructive approval, and optional post-generation absence reconciliation.
For an unchanged supplied CSV, do not apply those row-level checks: require
exact-object ImportSupport=Y, bind DELETE_RECORD in the approved preview,
and let Fusion Import Management accept or reject the rows.
- Additional Identifier generation/validation supports create, update, and
delete. Delete uses the exact
PartyIdentifierId as its only CSV field and
routes the activity as DELETE_RECORD. Require one exact parent-scoped
pre-delete match, destructive approval, and zero exact post-import matches.
- Treat Resolution Link
LinkStatus=I and Resolution Link Member MemberStatus=I as semantic destructive actions performed with CREATE_RECORD. Treat Source System Reference DELETE_RECORD as semantic inactivation rather than physical removal.
- Treat Asset
DeleteFlag=Y as semantic soft deletion performed with CREATE_RECORD; it requires destructive approval independently of literal DELETE_RECORD.
- For Asset Contact and Asset Team Member, require the explicit
Asset parent. Submit the exact target codes Assets for Asset and AssetResource for Asset Team Member; do not derive either code from its display name.
Prepare and validate CSV
Supplied CSV pass-through import
When the user supplies a CSV and asks to import it, treat every data CSV as an
opaque payload. Do not invoke prepare_tca_import_csv.py; do not parse, inspect,
normalize, validate, repair, or rewrite its header or row data. Do not compare
its columns with bundled samples, downloaded templates, column contracts, field
contracts, or live attributes. Accept any column count, names, order, and data,
including more columns than a sample, fewer columns, or no overlap with a
sample. Preserve the exact bytes through approval and upload.
For this pass-through branch, check only transport and routing facts: the path
exists, the file is a nonempty .csv, group basenames are unique
case-insensitively, at most one file is an authoritative CX mapping CSV, at
least one file is a data CSV, and an exact Import Management object code can be
resolved. Also require the exact job-level ImportMode from explicit user
intent or an already reviewed workflow artifact. If the object code is not
explicit and no mapping CSV supplies it, ask for the CX Business Object code.
If the mode is missing or ambiguous, ask whether the job is CREATE_ONLY,
CREATE_RECORD, or DELETE_RECORD. These are routing inputs, not CSV data
validation. Do not ask for a validation waiver. Fusion Import Management is the
authority that accepts or rejects the supplied data after submission.
Generation or explicit data validation
Only when the user asks this skill to generate a CSV or explicitly asks to
validate its data, use scripts/prepare_tca_import_csv.py; do not hand-build the
generated file. The following contracts and examples apply only to that branch
and must never block import of a supplied CSV.
The stored contracts deliberately distinguish three concepts:
required_for_create_by_skill is the minimum requirement enforced for a create operation, supplemented by conditional object rules.
identity_set_membership shows alternative keys used by create-or-update or delete; one complete supported set is required.
metadata_required is Oracle REST/import metadata and is descriptive. Do not blindly require every such field because Fusion can generate some fields or satisfy identity requirements through alternatives.
List the supported profile matrix:
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py profiles
Inspect all fields, types, lengths, and requiredness for one object:
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py fields \
--object "Contact"
Inspect only the skill-required create fields or one exact column:
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py fields \
--object "Hierarchy" --required-only
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py fields \
--object "Account" --column PartyNumber
Generate a minimal child-object template:
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py template \
--object "Address" --parent-object Organization --operation create-or-update \
--volume high --output /secure/work/address.csv
Prepare a validated file from synthetic-shaped JSON records:
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py prepare \
--object Organization --operation create --records-json /secure/input/organizations.json \
--output /secure/work/organization.csv --report /secure/work/organization.report.json
Use --full only when every downloaded-template column is needed. For prepare, include optional exact-header fields in the source records; for template, use --column ExactHeader. The redacted report contains no row values; it records object, parent, operation, derived import flags, file metadata, headers, SHA-256, destructive status, verification strategy, and warnings.
For LinkedParty, resolve the exact target-active LinkType codes before preparing or validating rows and pass them through --target-values-json. The file must remain outside project/ and use this redacted contract:
{
"objectCode": "LinkedParty",
"source": "fusion-runtime",
"fields": {"LinkType": ["target-active-code"]}
}
Do not translate a business label into a code from memory or preserve a previously observed environment's value as a universal default. The validator rejects a LinkedParty file when runtime LinkType evidence is absent or the row value is not in the supplied target-active set. Its report records only the validated field names, not the allowed-value payload.
Preflight
For a supplied CSV pass-through import, preflight only the exact environment,
OAuth session and upload privileges, explicit object and ImportMode routing,
current UCM account, authoritative ImportSupport=Y, immutable ordered
CSV-group SHA-256, mode-aware adapter readiness, and approval freshness. Do not
inspect or validate headers, fields, row values, lookups, identities, parents,
duplicate risk, or volume. Selecting the job-level mode does not authorize
inspection of the supplied CSV.
In particular, never require, inspect, or request a waiver for
PartyUsageCode. A field that is absent from the CSV is not a local blocker.
Present that the data content was not inspected and will be evaluated by Fusion.
For an explicit supplied Hierarchy or HierarchyNode delete, do not inspect
the CSV for PartyId, PartyNumber, parent identity, AsOfDate, identifier-only
rows, or a pre-delete match. The exact object, DELETE_RECORD mode, immutable
file group, environment, UCM account, activity, and destructive approval define
the authorized scope. Fusion Import Management evaluates the row data.
For generated CSVs or an explicit data-validation request, apply the remaining
object-specific checks in this section before execution.
If the user reports that their login, roles, or privileges changed, force one fresh OAuth login before interpreting a successful-but-empty Import Management object lookup. Retry only that read-only lookup once. Treat a still-empty result as a catalog or authorization blocker; do not substitute a neighboring object code. Access to CRM object metadata or the Import Management object picker does not prove authorization to upload through ERP Integration Service to the resolved UCM account.
For LinkedParty create, verify the main party has SALES_PROSPECT or SALES_ACCOUNT usage and the related party has the distinct financial CUSTOMER usage. Resolve LinkType from the exact target and validate it through --target-values-json; a user-facing label is not submission evidence. Do not treat Account type ZCA_CUSTOMER or usage SALES_ACCOUNT as evidence of financial CUSTOMER usage. If the financial usage is absent, stop and route creation of the financial customer account through its owning workflow before preparing or submitting the link.
For Account create/update, pass active lookup codes such as ZCA_PROSPECT and ZCA_CUSTOMER, never display meanings such as PROSPECT or CUSTOMER. Permit an existing Account identified by PartyNumber or source-system keys to change type without repeating an unchanged address. If any address field is being changed, require the complete address bundle. Explain that ZCA_CUSTOMER results in sales SALES_ACCOUNT usage and does not establish financial CUSTOMER usage.
For Source System Reference create/update, omit Status; the target import contract rejected a populated Status even though the downloaded template exposed the column. Use the selected profile's DELETE_RECORD path for semantic inactivation. Before retrying any source-system reference create, query the exact party, source system, and reference value because an earlier submission may already have succeeded.
For Asset create, require AssetNumber plus an existing asset-owner identity: CustomerId, CustomerPartyNumber, or AccountSourceSystem with AccountSourceSystemReference. Also require either ProdGroupId or the complete InventoryItemId plus InventoryOrgId pair; resolve the chosen product identity from the exact target. Validate all supplied source-system pairs together. For Asset Contact create, require AssetId or AssetNumber plus a contact identified by ContactPartyId, ContactPartyNumber, or the complete contact source-system pair. For Asset Team Member create, require AssetId or AssetNumber plus ResourceId or ResourcePartyNumber. Resolve asset, contact, resource, product, product-group, business-unit, currency, UOM, status, and function codes against the exact target when supplied.
Core-service boundary
Keep Trading Community object selection, optional CSV generation/validation,
metadata interpretation, approval orchestration, verification rules, and result
redaction in this skill. Supplied data CSVs cross this boundary unchanged and
receive no pillar data validation. Use core.fusion-api.rest-api-client for
authenticated read-only metadata and verification calls. Use
core.data-loader for mandatory source review, canonical digest, Task Hook
validation, and approval authorization. After those gates pass, use
core.fusion-api.cx-import-export-management as the mode-aware execution and
monitoring adapter; it must create the activity with the exact approved
ImportMode.
This skill uses core.data-loader as the governing preview and approval
workflow, not as the generic live initiateDataLoad adapter. Trading Community
templates and field catalogs remain local and are consulted only for generation
or an explicit data-validation request.
Core Data Loader resolves the CX UCM account from the exact target object's live metadata. Retain scripts/resolve_tca_ucm_account.py only for read-only reconciliation or diagnostics that must compare slash and dollar forms. Store raw service responses only in a secure temporary location and never display or persist encoded document content.
Preview and execution workflow
Resolve the exact environment, Import Management object code, exact
ImportMode, supplied CSV group, import activity name, and privileges. Do
not parse supplied data CSVs to infer these values. Refuse a missing or
ambiguous mode.
For supplied CSVs, freeze the exact bytes without data inspection or transformation. For generation or explicit validation, run the applicable helper and then freeze the result. Any byte, source order, mapping, object, mode, or environment change invalidates approval.
Resolve current object metadata and UcmAccount with the core REST client from GET /crmRestApi/resources/11.13.18.05/objectMetadata/{ObjectCode}?fields=UcmAccount&onlyData=true. Separately confirm the same exact code through the importExportObjectMetadata objectRowFinder and require ImportSupport=Y; do not substitute a neighboring code when it is absent. Normalize the metadata UCM account's slash form to UCM $ form with the skill-local resolver. Do not ask the user to supply or override it.
Skip data-dependent lookup, parent, mapping, and volume checks for supplied
CSVs. Select and validate only the job-level ImportMode; do not inspect CSV
data to infer or confirm it. Apply object dependencies only when generating
data or when the user explicitly requests data validation. Do not add a
hierarchy member target-resolution exception for supplied CSV deletes.
For a new Resolution Link campaign, create and verify DedupLink first, capture its generated LinkNumber, then prepare a separately approved LinkMember activity. Require exactly one master across the new link's requested members. Use Y/N in the import CSV and verify the REST MasterFlag as boolean true/false.
Enter core.data-loader and run upload_and_initiate.py <csv> --cx-import --cx-import-object-code <ObjectCode> --preflight-envelope-output <secure-temp>/preflight.json, omitting
--task-routed, --approve-upload, and --task-validation-envelope.
Core owns source transport review and may persist its reviewed ZIP outside
project/. Its archiveSha256 identifies that ZIP, not the ordered CSV
group. Preserve source basenames and bytes; do not upload this ZIP or use its
digest as the CX execution digest. Mapping CSVs remain unsupported by the
protected adapter: record the gap and stop before approval.
Run the Core CX adapter's prepare-import with the exact ordered local CSVs
and settings shown below, saving its review output outside project/.
Reconcile the two Core review artifacts with the skill-local helper:
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/reconcile_tca_import_preview.py \
--preflight <secure-temp>/preflight.json \
--adapter-preview <secure-temp>/adapter-preview.json \
--object-code <ObjectCode> --import-mode <CREATE_ONLY|CREATE_RECORD|DELETE_RECORD>
The helper checks the Data Loader envelope and ZIP digest, exact ordered
filenames and file bytes against the protected adapter manifest, and target,
object, mode, and UCM account. It never parses data CSV headers or rows,
extracts a ZIP, computes a replacement group digest, or grants approval.
Treat a failed reconciliation as an approval_blocker; rerun the applicable
Core previews after correcting the mismatch. Different ZIP and group digests
are expected because they identify different representations.
After reconciliation, use only the adapter-returned manifest.groupSha256
in Task Hook's compatibility finalData.archiveSha256 field. Retain the
Data Loader ZIP digest separately as finalData.dataLoaderArchiveSha256.
finalData must also bind the exact environment, object code, ImportMode,
import activity name, ordered filenames, UCM account, activation, schedule,
and core.fusion-api.cx-import-export-management execution adapter. Include
the protected manifest, approvalId, and reviewSha256 in the review.
Present the ordered filenames, group digest, target, object, mode, and
activity. For supplied CSVs, state that data content was not inspected.
Never invoke the physical-archive verifier for the CSV group, independently
reconstruct its digest, or submit through generic initiateDataLoad.
Stop once for exact-artifact execution approval, showing destructive effects
for DELETE_RECORD or semantic inactivation/removal. This approval authorizes
both the matching Task Validation envelope and the protected Core adapter
approval; do not ask again for the same execution.
Record that explicit approval using
cx_import_export_job.py approve-import --approval-id <id> --review-sha256 <reviewed-digest>.
The authority is the owner-private store outside the project, not mutable
finalData, a self-hash, or an editable Task Validation envelope. Approvals
expire after 15 minutes by default and cannot be reused or renewed.
Invoke the supported Core CX adapter; do not call or wrap its Python
implementation. Use the exact approved ordered data CSVs, object, mode,
activity name, UCM account, activation, and schedule; --import-mode is required.
Never call the generic Core Data Loader initiateDataLoad route because it
does not bind the Import Management ImportMode.
Bare create-import --execute and upload-ucm --execute
are disabled. Core owns OAuth, UCM transport, diagnostics, and returned IDs.
python3 core/fusion-api/cx-import-export-management/scripts/cx_import_export_job.py execute-approved-import \
--approval-id <approved-id> \
--name <approved-activity-name> \
--object-code <ObjectCode> \
--import-mode <CREATE_ONLY|CREATE_RECORD|DELETE_RECORD> \
--upload-file <approved.csv> \
--ucm-document-account '<resolved-account>' \
--activate YES \
--schedule ONE_TIME_IMMEDIATE \
--token-cache auto
Use prepare-import with these same arguments (without --approval-id)
for the step-6 preview. Repeat --upload-file in the approved order for
multiple data CSVs. Mapping CSVs remain unsupported: record the workflow gap
and stop, without substituting another upload route. Execution opens each
source once, compares bytes/order/settings against the protected approval,
consumes that approval atomically, confirms the current fixed environment
and exact object account, and uploads only the verified in-memory bytes.
Any byte, membership, order, object, mode, activity name, environment, UCM
account, activation, or schedule change invalidates approval.
Capture the redacted receipt in the project workspace. A failed attempt
spends the approval; reconcile partial uploads and activity status before
seeking new authorization, and never replay an uncertain write.
Capture the returned UCM document name and ImportActivityId, then stop after
accepted activity creation/activation. Return a compact import receipt with
activity ID and name, exact object and mode, activation, schedule, filename,
UCM document name, and current data-file status. Persist that receipt under
the project workspace so the user can say check status later without
repeating an ID. Never display the adapter's raw upload response, encoded
source content, UCM search metadata, or null-filled REST payload.
When the user subsequently requests status, resolve the latest applicable
activity ID from project state when the request omits it. Run the CX
adapter's get-import --import-activity-id route and require its parent
activity response to report the same exact ObjectCode and ImportMode.
Then run
scripts/get_tca_import_status.py with the approved object code and
ImportMode. This task-local helper uses the existing core REST client to
fetch both the parent activity and its child/DataFiles collection. The
parent must report the same exact ObjectCode and ImportMode; a missing or
mismatched value is not successful evidence of the requested operation.
For a supplied CSV, report Fusion's activity mode, status, and counts without
parsing the CSV to discover verification keys. Report the child data-file
Status, ReadFromFile, LoadedSuccessfully, ErrorsReported, Warnings,
and Unprocessed values, plus start/end timestamps. Include available error,
exception, and success report content IDs for terminal outcomes. Never infer
status from a parent-only response that omits these fields. When errors are
nonzero and ErrorReportContentId is available, immediately run
scripts/get_tca_import_report.py --content-id <ErrorReportContentId> and
include every distinct Fusion business diagnostic in the same status
response. The report helper returns only error type, message, and diagnostic
comment; it does not expose or persist source rows.
ImportMode=DELETE_RECORD
plus a successful activity proves that Fusion processed the job in delete
mode; it does not by itself prove that a specific target record is absent.
Perform record-level verification only when the user supplied the needed
identities separately. For generated or explicitly validated records,
verify by the profile strategy and exact identities. Do not equate a loaded count,
generic Data Loader success, or UI-search visibility with target
verification, and do not resubmit without exact reconciliation.
Build the request-instance ledger only when request identities were supplied independently or the skill generated the records. Never inspect an opaque supplied CSV to manufacture that manifest. Every manifest entry must end as completed_and_verified, failed_no_record_created, deferred, not_submitted, or unknown_requires_reconciliation.
Build and validate the ledger from redacted request and outcome files:
{
"environment": "nonproduction-environment-alias",
"requests": [
{
"request_id": "address-account-1",
"object_code": "Address",
"intended_mutation": "created",
"parent_ref": "account-request-1",
"source_reference_supplied": true,
"expected_match_count": 1
}
]
}
Each outcome uses the same request_id and exact object_code. A completed_and_verified outcome supplies mutation, import_activity_id, ucm_content_id, process_counts, and verification with exact_match_count, target_record_ids, state, plus parent_identity or source_reference when the request requires them. Non-completed outcomes require a reason. The utility rejects duplicate outcomes and outcomes for unknown or semantically different requests; a request with no outcome becomes unknown_requires_reconciliation.
python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/build_tca_verification_ledger.py \
--request-manifest /secure/work/requests.json \
--outcome /secure/work/outcomes.json \
--output /secure/work/verification-ledger.json
The ledger distinguishes created, updated, deleted, inactivated, and
none. Never count an update as a create or a physical deletion as an
inactivation. Never use a Relationship or Account Contact outcome to satisfy a
Linked Party request, and never use an Account-to-Contact association to
satisfy an Account-to-Account link. Account/Organization and Contact/Person
remain distinct functional objects. Account type ZCA_CUSTOMER or usage
SALES_ACCOUNT remains distinct from financial CUSTOMER usage.
Verification branches
sales-account: confirm exact party identity plus active sales profile, PromotedFlag, owner, and address state.
sales-contact: confirm exact party identity, sales-contact state, and intended Account/Household association.
party-usage: confirm exact party identity and intended Organization/Person usage without treating it as Account/Contact.
child-with-parent or relationship: confirm the child/relationship and its exact parent, subject, and object identities.
- For an Additional Identifier delete, query the selected party's
AdditionalIdentifier child by the approved PartyIdentifierId and require
zero exact matches. A completed activity or loaded row is not deletion proof.
asset: confirm the exact AssetId/AssetNumber, owner identity, product or product-group identity when supplied, status, and DeleteFlag state.
asset-child: confirm the exact Asset parent plus the Asset Contact or Asset Team Member record ID, referenced contact/resource identity, function, and primary/owner flag.
hierarchy-post-process: when separately requested and the necessary
identities are supplied, run and verify Party Hierarchy Generation after a
successful Hierarchy or Hierarchy Member import, then reconcile
tree/version/member state. For delete, zero exact target matches provide
record-level absence evidence; loaded-row counts alone do not.
- Treat Party Hierarchy Generation as a separate ESS mutation routed through
core.fusion-api.ess-job-submitter. Resolve and preview the exact job definition and parameters after the hierarchy import succeeds, and obtain a fresh approval; approval of the CSV import does not authorize an as-yet-unresolved ESS request.
resolution-link and resolution-link-member: confirm link status, membership, and master/member semantics, including inactive status after a semantic removal. Verify Link Members through REST-supported fields LinkNumber, PartyId, PartyNumber, MasterFlag, and MemberStatus; DedupLinkMemberId is an import/update identity and must not be requested from the Link Member REST collection.
exact-identity: query the exact imported identifier and verify the intended field state.
Apply the exact locator and identity requirements in references/object-profiles.json for every branch. A terminal import activity with loaded rows is process evidence only. Completion requires the exact expected target match count, generated target identifier evidence, and the intended created, updated, or inactivated state. If exact target reconciliation is ambiguous, use unknown_requires_reconciliation; do not claim completion or submit another mutation.
For LinkedParty, resolve the parent from hubOrganizations by PartyNumber and use that returned item key in /hubOrganizations/{PartyNumber}/child/LinkedParty. Do not substitute the numeric PartyId in that item-key position. Verify the related party, target-resolved LinkType, MainLink, status, and active dates before changing the ledger entry to completed_and_verified.
Diagnostics and persistence
Classify failures as input_validation, catalog_or_metadata_mismatch, auth_expired_or_invalid, authorization_or_privilege, transport_or_environment, fusion_api_error, process_timeout, process_failed, artifact_persistence, or approval_blocker. Treat an uncertain Core adapter result as an approval blocker, not as permission to replay a write. On timeout, report environment, object, activity ID, last status, and elapsed wait; use the Core adapter's read-only status route rather than resubmitting.
Keep source rows, generated CSVs, downloaded reports containing row data, credentials, and tokens outside project/. When a project exists, persist only redacted validation reports, immutable-preview metadata, run status, external IDs, diagnostics, verification evidence, and token usage at the declared workspace paths.
Maintain the field catalog
When Oracle changes the Import Management templates, download all 25 supported object ZIPs from the exact target-family environment and regenerate the local assets and contracts with scripts/build_tca_field_contracts.py. Supply the current CRM REST describe plus current Account and Contact object-metadata attribute payloads. For objects whose REST describe doesn't cover every import field, supply UI metadata captured from Import Objects with --ui-metadata-dir. Use repeatable --object arguments for a scoped incremental refresh. The generator validates every ZIP, preserves each Oracle two-row CSV under assets/templates/, records SHA-256 values, and fails if any template column has no authoritative data type. Review generated diffs and rerun all skill tests before handoff.
1---2skill_id: "cx.customer-data-management.trading-community-foundation.import-trading-community-data"3name: import-trading-community-data4description: "Imports user-supplied Trading Community CSV files unchanged through Oracle CX Import Management, without validating their columns or row data. Also generates or validates CSVs when explicitly requested. Supplied CSVs may contain any number and names of columns, including columns absent from the bundled samples."5layer: "pillar"6pillar: "CX"7offering: "Customer Data Management"8functional_area: "Trading Community Foundation"9functional_area_code: "ORA_HZ_CDM_FOUNDATION"10task_code: "CUSTOM_IMPORT_TRADING_COMMUNITY_DATA"11task_name: "Import Trading Community Data"12dataloader_import_mode: "CXIMPORT"13businessObject: ""14type: "import"15execution_mode: "hybrid"16owner_team: "CX Customer Data Management pillar team"17version: "2.5.5"18inputs:19 - "project_context"20 - "target_fusion_environment"21 - "exact_import_object"22 - "exact_import_mode"23 - "optional_parent_object_for_generation_or_explicit_validation"24 - "optional_volume_mode_for_generation_or_explicit_validation"25 - "source_records_or_csv"26 - "requested_record_manifest"27 - "import_activity_name"28 - "execution_approval"29outputs:30 - "unchanged_supplied_csv_or_generated_csv"31 - "optional_redacted_csv_validation_report"32 - "immutable_import_preview"33 - "ucm_upload_summary"34 - "cx_import_activity_result"35 - "import_status_and_diagnostics"36 - "post_import_verification"37 - "request_instance_verification_ledger"38 - "campaign_completion_summary"39 - "skill_run_record"40 - "token_usage_record"41depends_on:42 - "cx.customer-data-management.trading-community-foundation"43 - "core.data-loader"44 - "core.fusion-api.cx-import-export-management"45 - "core.fusion-api.ess-job-submitter"46uses_core:47 - "core.data-loader"48 - "core.auth.fusion-oauth-authentication"49 - "core.fusion-api.rest-api-client"50 - "core.fusion-api.ucm-rest-client"51 - "core.fusion-api.cx-import-export-management"52 - "core.fusion-api.ess-job-submitter"53 - "core.project-mgmt.artifact-version-manager"54 - "core.project-mgmt.artifact-registry-manager"55 - "core.project-mgmt.project-state-manager"56persists_project_state: true57token_usage_tracking:58 enabled: true59 granularity: "per_skill_run"60 artifact_type: "token_usage_record"61 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"62 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"63 required_fields:64 - "activity_start_time"65 - "skill_id"66 - "task"67 - "trigger"68 - "artifacts_written"69 - "files_read"70 - "estimated_input_tokens"71 - "estimated_output_tokens"72 - "estimated_total_tokens"73 - "estimation_method"74 - "notes"75state_updates:76 - "validation_results"77 - "reports"78 - "token_usage_records"79workspace_outputs:80 - artifact_type: "validation_result"81 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/current/"82 versioning_policy: "major-new-version-minor-confirm-update"83 - artifact_type: "report"84 default_location: "project/{project_id}/artifacts/pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/current/"85 versioning_policy: "major-new-version-minor-confirm-update"86 - artifact_type: "skill_run"87 default_location: "project/{project_id}/state/runs/"88 versioning_policy: "append-only"89 - artifact_type: "token_usage_record"90 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"91 versioning_policy: "append-only"92oracle_supplied_guidance_files:93 - purpose: "Input and CSV contract checks"94 location: "ora-resource/ora_input_validation.md"95 - purpose: "Import dependency readiness"96 location: "ora-resource/ora_dependency_readiness.md"97 - purpose: "Object, operation, parent, and volume rules"98 location: "ora-resource/ora_reference_lookups.md"99 - purpose: "Safe import defaults"100 location: "ora-resource/ora_defaulting_rules.md"101 - purpose: "Preview, deletion, and live-execution gates"102 location: "ora-resource/ora_design_enforcement.md"103 - purpose: "Failure classification and recovery"104 location: "ora-resource/ora_error_handling.md"105applicability:106 industries:107 - "All"108 countries:109 - "All"110 fusion_releases:111 - "Current Oracle Fusion Cloud release"112side_effects:113 - "Creates local CSV files outside the tracked project workspace and may persist redacted validation and run metadata."114 - "Uses the core CX adapter to upload an explicitly approved immutable CSV group and create or activate one Import Management activity."115 - "Creates and may activate one explicitly approved CX Import Management activity with the exact selected ImportMode."116 - "Literal deletion and semantic inactivation/removal require separate destructive approval."117required_privileges:118 - "Access to the exact target Oracle Fusion environment and required OAuth scope."119 - "Privileges to upload to the target-metadata-resolved UCM document account."120 - "CX Import Management privileges for the selected object and operation."121 - "Object-specific delete or update privileges for destructive operations."122metadata:123 source: https://skillmd.com/skills/oracle/import-trading-community-data124---125126# Import Trading Community Data127128## Purpose129130Prepare and execute one governed CX Import Management activity for one exact Trading Community object. Support CSV generation and validation, immutable preview, approved submission, bounded monitoring, diagnosis, and post-import verification. Asset, Asset Contact, and the UI-labeled Asset Team Member object are supported; their exact target codes are `Assets`, `AssetContact`, and `AssetResource`.131132## Required reading1331341. Read `references/object-profiles.json` only to resolve the exact Import Management object code and post-import verification strategy.1352. Read all six `ora-resource` files and compile/use `ora_rule_registry.json` through Task Hook.1363. Read `core/data-loader/SKILL.md`; it owns source transport review, the canonical immutable digest, Task Hook validation, and approval authorization before any import adapter runs.1374. Read `core/fusion-api/rest-api-client/SKILL.md` and its routed Fusion REST reference before resolving live object metadata or verifying records.1385. Read `core/fusion-api/cx-import-export-management/SKILL.md` and its required reference before mode-aware execution or monitoring.1396. Only when the user asks to generate a CSV or explicitly validate its data, also read `references/column-contracts.json`, `references/field-contracts.json`, and the matching template under `assets/templates/`.140141## Selection gates142143- For every supplied or generated CSV, select exactly one Import Management144 object code and one exact job-level `ImportMode` without inspecting supplied145 data rows. `ImportMode` is routing metadata, not a CSV field-validation result.146 Do not infer it from the supplied filename, columns, or values.147- The remaining selection gates apply only to generation or an explicit148 data-validation request. Never infer `Account` from `Organization`, or149 `Contact` from `Person`; ask the user to choose because their generated import150 contracts are functionally different.151- Select exactly one allowed parent for a child object. `Household` is a parent identity only and is not a top-level object supported by this skill.152- Reject missing, ambiguous, or unsupported operations. Treat `update`,153 `create-or-update`, or `create and update` as `CREATE_RECORD`, `create` as154 `CREATE_ONLY`, and155 literal `delete` as `DELETE_RECORD`. Bind the exact code into the immutable156 preview and the live Import Management activity.157- Enforce `fixed-high` for Classification Code, Hierarchy, and Hierarchy Member. Enforce `fixed-low` for Resolution Link and Resolution Link Member. Other profiles may use low or high volume; use the profile default unless the user chooses otherwise.158- Hierarchy and Hierarchy Member generation or explicit data validation support159 create, update, and delete. Their update route uses `CREATE_RECORD`; their160 delete route uses `DELETE_RECORD`, identifier-only rows, exact-target checks,161 destructive approval, and optional post-generation absence reconciliation.162 For an unchanged supplied CSV, do not apply those row-level checks: require163 exact-object `ImportSupport=Y`, bind `DELETE_RECORD` in the approved preview,164 and let Fusion Import Management accept or reject the rows.165- Additional Identifier generation/validation supports create, update, and166 delete. Delete uses the exact `PartyIdentifierId` as its only CSV field and167 routes the activity as `DELETE_RECORD`. Require one exact parent-scoped168 pre-delete match, destructive approval, and zero exact post-import matches.169- Treat Resolution Link `LinkStatus=I` and Resolution Link Member `MemberStatus=I` as semantic destructive actions performed with `CREATE_RECORD`. Treat Source System Reference `DELETE_RECORD` as semantic inactivation rather than physical removal.170- Treat Asset `DeleteFlag=Y` as semantic soft deletion performed with `CREATE_RECORD`; it requires destructive approval independently of literal `DELETE_RECORD`.171- For Asset Contact and Asset Team Member, require the explicit `Asset` parent. Submit the exact target codes `Assets` for Asset and `AssetResource` for Asset Team Member; do not derive either code from its display name.172173## Prepare and validate CSV174175### Supplied CSV pass-through import176177When the user supplies a CSV and asks to import it, treat every data CSV as an178opaque payload. Do not invoke `prepare_tca_import_csv.py`; do not parse, inspect,179normalize, validate, repair, or rewrite its header or row data. Do not compare180its columns with bundled samples, downloaded templates, column contracts, field181contracts, or live attributes. Accept any column count, names, order, and data,182including more columns than a sample, fewer columns, or no overlap with a183sample. Preserve the exact bytes through approval and upload.184185For this pass-through branch, check only transport and routing facts: the path186exists, the file is a nonempty `.csv`, group basenames are unique187case-insensitively, at most one file is an authoritative CX mapping CSV, at188least one file is a data CSV, and an exact Import Management object code can be189resolved. Also require the exact job-level `ImportMode` from explicit user190intent or an already reviewed workflow artifact. If the object code is not191explicit and no mapping CSV supplies it, ask for the CX Business Object code.192If the mode is missing or ambiguous, ask whether the job is `CREATE_ONLY`,193`CREATE_RECORD`, or `DELETE_RECORD`. These are routing inputs, not CSV data194validation. Do not ask for a validation waiver. Fusion Import Management is the195authority that accepts or rejects the supplied data after submission.196197### Generation or explicit data validation198199Only when the user asks this skill to generate a CSV or explicitly asks to200validate its data, use `scripts/prepare_tca_import_csv.py`; do not hand-build the201generated file. The following contracts and examples apply only to that branch202and must never block import of a supplied CSV.203204The stored contracts deliberately distinguish three concepts:205206- `required_for_create_by_skill` is the minimum requirement enforced for a create operation, supplemented by conditional object rules.207- `identity_set_membership` shows alternative keys used by create-or-update or delete; one complete supported set is required.208- `metadata_required` is Oracle REST/import metadata and is descriptive. Do not blindly require every such field because Fusion can generate some fields or satisfy identity requirements through alternatives.209210List the supported profile matrix:211212```bash213python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py profiles214```215216Inspect all fields, types, lengths, and requiredness for one object:217218```bash219python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py fields \220 --object "Contact"221```222223Inspect only the skill-required create fields or one exact column:224225```bash226python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py fields \227 --object "Hierarchy" --required-only228229python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py fields \230 --object "Account" --column PartyNumber231```232233Generate a minimal child-object template:234235```bash236python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py template \237 --object "Address" --parent-object Organization --operation create-or-update \238 --volume high --output /secure/work/address.csv239```240241Prepare a validated file from synthetic-shaped JSON records:242243```bash244python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/prepare_tca_import_csv.py prepare \245 --object Organization --operation create --records-json /secure/input/organizations.json \246 --output /secure/work/organization.csv --report /secure/work/organization.report.json247```248249Use `--full` only when every downloaded-template column is needed. For `prepare`, include optional exact-header fields in the source records; for `template`, use `--column ExactHeader`. The redacted report contains no row values; it records object, parent, operation, derived import flags, file metadata, headers, SHA-256, destructive status, verification strategy, and warnings.250251For `LinkedParty`, resolve the exact target-active `LinkType` codes before preparing or validating rows and pass them through `--target-values-json`. The file must remain outside `project/` and use this redacted contract:252253```json254{255 "objectCode": "LinkedParty",256 "source": "fusion-runtime",257 "fields": {"LinkType": ["target-active-code"]}258}259```260261Do not translate a business label into a code from memory or preserve a previously observed environment's value as a universal default. The validator rejects a `LinkedParty` file when runtime `LinkType` evidence is absent or the row value is not in the supplied target-active set. Its report records only the validated field names, not the allowed-value payload.262263## Preflight264265For a supplied CSV pass-through import, preflight only the exact environment,266OAuth session and upload privileges, explicit object and `ImportMode` routing,267current UCM account, authoritative `ImportSupport=Y`, immutable ordered268CSV-group SHA-256, mode-aware adapter readiness, and approval freshness. Do not269inspect or validate headers, fields, row values, lookups, identities, parents,270duplicate risk, or volume. Selecting the job-level mode does not authorize271inspection of the supplied CSV.272In particular, never require, inspect, or request a waiver for273`PartyUsageCode`. A field that is absent from the CSV is not a local blocker.274Present that the data content was not inspected and will be evaluated by Fusion.275276For an explicit supplied `Hierarchy` or `HierarchyNode` delete, do not inspect277the CSV for PartyId, PartyNumber, parent identity, AsOfDate, identifier-only278rows, or a pre-delete match. The exact object, `DELETE_RECORD` mode, immutable279file group, environment, UCM account, activity, and destructive approval define280the authorized scope. Fusion Import Management evaluates the row data.281282For generated CSVs or an explicit data-validation request, apply the remaining283object-specific checks in this section before execution.284285If the user reports that their login, roles, or privileges changed, force one fresh OAuth login before interpreting a successful-but-empty Import Management object lookup. Retry only that read-only lookup once. Treat a still-empty result as a catalog or authorization blocker; do not substitute a neighboring object code. Access to CRM object metadata or the Import Management object picker does not prove authorization to upload through ERP Integration Service to the resolved UCM account.286287For `LinkedParty` create, verify the main party has `SALES_PROSPECT` or `SALES_ACCOUNT` usage and the related party has the distinct financial `CUSTOMER` usage. Resolve `LinkType` from the exact target and validate it through `--target-values-json`; a user-facing label is not submission evidence. Do not treat Account type `ZCA_CUSTOMER` or usage `SALES_ACCOUNT` as evidence of financial `CUSTOMER` usage. If the financial usage is absent, stop and route creation of the financial customer account through its owning workflow before preparing or submitting the link.288289For Account create/update, pass active lookup codes such as `ZCA_PROSPECT` and `ZCA_CUSTOMER`, never display meanings such as `PROSPECT` or `CUSTOMER`. Permit an existing Account identified by PartyNumber or source-system keys to change type without repeating an unchanged address. If any address field is being changed, require the complete address bundle. Explain that `ZCA_CUSTOMER` results in sales `SALES_ACCOUNT` usage and does not establish financial `CUSTOMER` usage.290291For Source System Reference create/update, omit `Status`; the target import contract rejected a populated `Status` even though the downloaded template exposed the column. Use the selected profile's `DELETE_RECORD` path for semantic inactivation. Before retrying any source-system reference create, query the exact party, source system, and reference value because an earlier submission may already have succeeded.292293For Asset create, require `AssetNumber` plus an existing asset-owner identity: `CustomerId`, `CustomerPartyNumber`, or `AccountSourceSystem` with `AccountSourceSystemReference`. Also require either `ProdGroupId` or the complete `InventoryItemId` plus `InventoryOrgId` pair; resolve the chosen product identity from the exact target. Validate all supplied source-system pairs together. For Asset Contact create, require `AssetId` or `AssetNumber` plus a contact identified by `ContactPartyId`, `ContactPartyNumber`, or the complete contact source-system pair. For Asset Team Member create, require `AssetId` or `AssetNumber` plus `ResourceId` or `ResourcePartyNumber`. Resolve asset, contact, resource, product, product-group, business-unit, currency, UOM, status, and function codes against the exact target when supplied.294295## Core-service boundary296297Keep Trading Community object selection, optional CSV generation/validation,298metadata interpretation, approval orchestration, verification rules, and result299redaction in this skill. Supplied data CSVs cross this boundary unchanged and300receive no pillar data validation. Use `core.fusion-api.rest-api-client` for301authenticated read-only metadata and verification calls. Use302`core.data-loader` for mandatory source review, canonical digest, Task Hook303validation, and approval authorization. After those gates pass, use304`core.fusion-api.cx-import-export-management` as the mode-aware execution and305monitoring adapter; it must create the activity with the exact approved306`ImportMode`.307308This skill uses `core.data-loader` as the governing preview and approval309workflow, not as the generic live `initiateDataLoad` adapter. Trading Community310templates and field catalogs remain local and are consulted only for generation311or an explicit data-validation request.312313Core Data Loader resolves the CX UCM account from the exact target object's live metadata. Retain `scripts/resolve_tca_ucm_account.py` only for read-only reconciliation or diagnostics that must compare slash and dollar forms. Store raw service responses only in a secure temporary location and never display or persist encoded document content.314315## Preview and execution workflow3163171. Resolve the exact environment, Import Management object code, exact318 `ImportMode`, supplied CSV group, import activity name, and privileges. Do319 not parse supplied data CSVs to infer these values. Refuse a missing or320 ambiguous mode.3212. For supplied CSVs, freeze the exact bytes without data inspection or transformation. For generation or explicit validation, run the applicable helper and then freeze the result. Any byte, source order, mapping, object, mode, or environment change invalidates approval.3223. Resolve current object metadata and `UcmAccount` with the core REST client from `GET /crmRestApi/resources/11.13.18.05/objectMetadata/{ObjectCode}?fields=UcmAccount&onlyData=true`. Separately confirm the same exact code through the `importExportObjectMetadata` `objectRowFinder` and require `ImportSupport=Y`; do not substitute a neighboring code when it is absent. Normalize the metadata UCM account's slash form to UCM `$` form with the skill-local resolver. Do not ask the user to supply or override it.3234. Skip data-dependent lookup, parent, mapping, and volume checks for supplied324 CSVs. Select and validate only the job-level `ImportMode`; do not inspect CSV325 data to infer or confirm it. Apply object dependencies only when generating326 data or when the user explicitly requests data validation. Do not add a327 hierarchy member target-resolution exception for supplied CSV deletes.328 For a new Resolution Link campaign, create and verify `DedupLink` first, capture its generated `LinkNumber`, then prepare a separately approved `LinkMember` activity. Require exactly one master across the new link's requested members. Use `Y`/`N` in the import CSV and verify the REST `MasterFlag` as boolean `true`/`false`.3295. Enter `core.data-loader` and run `upload_and_initiate.py <csv>330 --cx-import --cx-import-object-code <ObjectCode>331 --preflight-envelope-output <secure-temp>/preflight.json`, omitting332 `--task-routed`, `--approve-upload`, and `--task-validation-envelope`.333 Core owns source transport review and may persist its reviewed ZIP outside334 `project/`. Its `archiveSha256` identifies that ZIP, not the ordered CSV335 group. Preserve source basenames and bytes; do not upload this ZIP or use its336 digest as the CX execution digest. Mapping CSVs remain unsupported by the337 protected adapter: record the gap and stop before approval.3386. Run the Core CX adapter's `prepare-import` with the exact ordered local CSVs339 and settings shown below, saving its review output outside `project/`.340 Reconcile the two Core review artifacts with the skill-local helper:341342 ```bash343 python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/reconcile_tca_import_preview.py \344 --preflight <secure-temp>/preflight.json \345 --adapter-preview <secure-temp>/adapter-preview.json \346 --object-code <ObjectCode> --import-mode <CREATE_ONLY|CREATE_RECORD|DELETE_RECORD>347 ```348349 The helper checks the Data Loader envelope and ZIP digest, exact ordered350 filenames and file bytes against the protected adapter manifest, and target,351 object, mode, and UCM account. It never parses data CSV headers or rows,352 extracts a ZIP, computes a replacement group digest, or grants approval.353 Treat a failed reconciliation as an `approval_blocker`; rerun the applicable354 Core previews after correcting the mismatch. Different ZIP and group digests355 are expected because they identify different representations.356 After reconciliation, use only the adapter-returned `manifest.groupSha256`357 in Task Hook's compatibility `finalData.archiveSha256` field. Retain the358 Data Loader ZIP digest separately as `finalData.dataLoaderArchiveSha256`.359 `finalData` must also bind the exact environment, object code, `ImportMode`,360 import activity name, ordered filenames, UCM account, activation, schedule,361 and `core.fusion-api.cx-import-export-management` execution adapter. Include362 the protected manifest, `approvalId`, and `reviewSha256` in the review.363 Present the ordered filenames, group digest, target, object, mode, and364 activity. For supplied CSVs, state that data content was not inspected.365 Never invoke the physical-archive verifier for the CSV group, independently366 reconstruct its digest, or submit through generic `initiateDataLoad`.367 Stop once for exact-artifact execution approval, showing destructive effects368 for `DELETE_RECORD` or semantic inactivation/removal. This approval authorizes369 both the matching Task Validation envelope and the protected Core adapter370 approval; do not ask again for the same execution.3717. Record that explicit approval using372 `cx_import_export_job.py approve-import --approval-id <id> --review-sha256 <reviewed-digest>`.373 The authority is the owner-private store outside the project, not mutable374 `finalData`, a self-hash, or an editable Task Validation envelope. Approvals375 expire after 15 minutes by default and cannot be reused or renewed.3768. Invoke the supported Core CX adapter; do not call or wrap its Python377 implementation. Use the exact approved ordered data CSVs, object, mode,378 activity name, UCM account, activation, and schedule; `--import-mode` is required.379 Never call the generic Core Data Loader `initiateDataLoad` route because it380 does not bind the Import Management `ImportMode`.381 Bare `create-import --execute` and `upload-ucm --execute`382 are disabled. Core owns OAuth, UCM transport, diagnostics, and returned IDs.383384 ```bash385 python3 core/fusion-api/cx-import-export-management/scripts/cx_import_export_job.py execute-approved-import \386 --approval-id <approved-id> \387 --name <approved-activity-name> \388 --object-code <ObjectCode> \389 --import-mode <CREATE_ONLY|CREATE_RECORD|DELETE_RECORD> \390 --upload-file <approved.csv> \391 --ucm-document-account '<resolved-account>' \392 --activate YES \393 --schedule ONE_TIME_IMMEDIATE \394 --token-cache auto395 ```396397 Use `prepare-import` with these same arguments (without `--approval-id`)398 for the step-6 preview. Repeat `--upload-file` in the approved order for399 multiple data CSVs. Mapping CSVs remain unsupported: record the workflow gap400 and stop, without substituting another upload route. Execution opens each401 source once, compares bytes/order/settings against the protected approval,402 consumes that approval atomically, confirms the current fixed environment403 and exact object account, and uploads only the verified in-memory bytes.404 Any byte, membership, order, object, mode, activity name, environment, UCM405 account, activation, or schedule change invalidates approval.406 Capture the redacted receipt in the project workspace. A failed attempt407 spends the approval; reconcile partial uploads and activity status before408 seeking new authorization, and never replay an uncertain write.4099. Capture the returned UCM document name and `ImportActivityId`, then stop after410 accepted activity creation/activation. Return a compact import receipt with411 activity ID and name, exact object and mode, activation, schedule, filename,412 UCM document name, and current data-file status. Persist that receipt under413 the project workspace so the user can say `check status` later without414 repeating an ID. Never display the adapter's raw upload response, encoded415 source content, UCM search metadata, or null-filled REST payload.416417 When the user subsequently requests status, resolve the latest applicable418 activity ID from project state when the request omits it. Run the CX419 adapter's `get-import --import-activity-id` route and require its parent420 activity response to report the same exact `ObjectCode` and `ImportMode`.421 Then run422 `scripts/get_tca_import_status.py` with the approved object code and423 `ImportMode`. This task-local helper uses the existing core REST client to424 fetch both the parent activity and its `child/DataFiles` collection. The425 parent must report the same exact `ObjectCode` and `ImportMode`; a missing or426 mismatched value is not successful evidence of the requested operation.42710. For a supplied CSV, report Fusion's activity mode, status, and counts without428 parsing the CSV to discover verification keys. Report the child data-file429 `Status`, `ReadFromFile`, `LoadedSuccessfully`, `ErrorsReported`, `Warnings`,430 and `Unprocessed` values, plus start/end timestamps. Include available error,431 exception, and success report content IDs for terminal outcomes. Never infer432 status from a parent-only response that omits these fields. When errors are433 nonzero and `ErrorReportContentId` is available, immediately run434 `scripts/get_tca_import_report.py --content-id <ErrorReportContentId>` and435 include every distinct Fusion business diagnostic in the same status436 response. The report helper returns only error type, message, and diagnostic437 comment; it does not expose or persist source rows.438 `ImportMode=DELETE_RECORD`439 plus a successful activity proves that Fusion processed the job in delete440 mode; it does not by itself prove that a specific target record is absent.441 Perform record-level verification only when the user supplied the needed442 identities separately. For generated or explicitly validated records,443 verify by the profile strategy and exact identities. Do not equate a loaded count,444 generic Data Loader success, or UI-search visibility with target445 verification, and do not resubmit without exact reconciliation.44611. Build the request-instance ledger only when request identities were supplied independently or the skill generated the records. Never inspect an opaque supplied CSV to manufacture that manifest. Every manifest entry must end as `completed_and_verified`, `failed_no_record_created`, `deferred`, `not_submitted`, or `unknown_requires_reconciliation`.447448Build and validate the ledger from redacted request and outcome files:449450```json451{452 "environment": "nonproduction-environment-alias",453 "requests": [454 {455 "request_id": "address-account-1",456 "object_code": "Address",457 "intended_mutation": "created",458 "parent_ref": "account-request-1",459 "source_reference_supplied": true,460 "expected_match_count": 1461 }462 ]463}464```465466Each outcome uses the same `request_id` and exact `object_code`. A `completed_and_verified` outcome supplies `mutation`, `import_activity_id`, `ucm_content_id`, `process_counts`, and `verification` with `exact_match_count`, `target_record_ids`, `state`, plus `parent_identity` or `source_reference` when the request requires them. Non-completed outcomes require a reason. The utility rejects duplicate outcomes and outcomes for unknown or semantically different requests; a request with no outcome becomes `unknown_requires_reconciliation`.467468```bash469python3 pillars/cx/customer-data-management/trading-community-foundation/import-trading-community-data/scripts/build_tca_verification_ledger.py \470 --request-manifest /secure/work/requests.json \471 --outcome /secure/work/outcomes.json \472 --output /secure/work/verification-ledger.json473```474475The ledger distinguishes `created`, `updated`, `deleted`, `inactivated`, and476`none`. Never count an update as a create or a physical deletion as an477inactivation. Never use a Relationship or Account Contact outcome to satisfy a478Linked Party request, and never use an Account-to-Contact association to479satisfy an Account-to-Account link. Account/Organization and Contact/Person480remain distinct functional objects. Account type `ZCA_CUSTOMER` or usage481`SALES_ACCOUNT` remains distinct from financial `CUSTOMER` usage.482483## Verification branches484485- `sales-account`: confirm exact party identity plus active sales profile, `PromotedFlag`, owner, and address state.486- `sales-contact`: confirm exact party identity, sales-contact state, and intended Account/Household association.487- `party-usage`: confirm exact party identity and intended Organization/Person usage without treating it as Account/Contact.488- `child-with-parent` or `relationship`: confirm the child/relationship and its exact parent, subject, and object identities.489- For an Additional Identifier delete, query the selected party's490 `AdditionalIdentifier` child by the approved `PartyIdentifierId` and require491 zero exact matches. A completed activity or loaded row is not deletion proof.492- `asset`: confirm the exact `AssetId`/`AssetNumber`, owner identity, product or product-group identity when supplied, status, and `DeleteFlag` state.493- `asset-child`: confirm the exact Asset parent plus the Asset Contact or Asset Team Member record ID, referenced contact/resource identity, function, and primary/owner flag.494- `hierarchy-post-process`: when separately requested and the necessary495 identities are supplied, run and verify Party Hierarchy Generation after a496 successful Hierarchy or Hierarchy Member import, then reconcile497 tree/version/member state. For delete, zero exact target matches provide498 record-level absence evidence; loaded-row counts alone do not.499- Treat Party Hierarchy Generation as a separate ESS mutation routed through `core.fusion-api.ess-job-submitter`. Resolve and preview the exact job definition and parameters after the hierarchy import succeeds, and obtain a fresh approval; approval of the CSV import does not authorize an as-yet-unresolved ESS request.500- `resolution-link` and `resolution-link-member`: confirm link status, membership, and master/member semantics, including inactive status after a semantic removal. Verify Link Members through REST-supported fields `LinkNumber`, `PartyId`, `PartyNumber`, `MasterFlag`, and `MemberStatus`; `DedupLinkMemberId` is an import/update identity and must not be requested from the Link Member REST collection.501- `exact-identity`: query the exact imported identifier and verify the intended field state.502503Apply the exact locator and identity requirements in `references/object-profiles.json` for every branch. A terminal import activity with loaded rows is process evidence only. Completion requires the exact expected target match count, generated target identifier evidence, and the intended created, updated, or inactivated state. If exact target reconciliation is ambiguous, use `unknown_requires_reconciliation`; do not claim completion or submit another mutation.504505For `LinkedParty`, resolve the parent from `hubOrganizations` by `PartyNumber` and use that returned item key in `/hubOrganizations/{PartyNumber}/child/LinkedParty`. Do not substitute the numeric `PartyId` in that item-key position. Verify the related party, target-resolved `LinkType`, `MainLink`, status, and active dates before changing the ledger entry to `completed_and_verified`.506507## Diagnostics and persistence508509Classify failures as `input_validation`, `catalog_or_metadata_mismatch`, `auth_expired_or_invalid`, `authorization_or_privilege`, `transport_or_environment`, `fusion_api_error`, `process_timeout`, `process_failed`, `artifact_persistence`, or `approval_blocker`. Treat an uncertain Core adapter result as an approval blocker, not as permission to replay a write. On timeout, report environment, object, activity ID, last status, and elapsed wait; use the Core adapter's read-only status route rather than resubmitting.510511Keep source rows, generated CSVs, downloaded reports containing row data, credentials, and tokens outside `project/`. When a project exists, persist only redacted validation reports, immutable-preview metadata, run status, external IDs, diagnostics, verification evidence, and token usage at the declared workspace paths.512513## Maintain the field catalog514515When Oracle changes the Import Management templates, download all 25 supported object ZIPs from the exact target-family environment and regenerate the local assets and contracts with `scripts/build_tca_field_contracts.py`. Supply the current CRM REST describe plus current Account and Contact object-metadata attribute payloads. For objects whose REST describe doesn't cover every import field, supply UI metadata captured from Import Objects with `--ui-metadata-dir`. Use repeatable `--object` arguments for a scoped incremental refresh. The generator validates every ZIP, preserves each Oracle two-row CSV under `assets/templates/`, records SHA-256 values, and fails if any template column has no authoritative data type. Review generated diffs and rerun all skill tests before handoff.