Manage Account, Contact, and Household Audit Policies
Purpose
Check and enable audit for CX Account, Contact, Household, and child business
objects that the live Audit Setup inventory binds to one of those roots.
Validate requested attribute names and enable those attributes without
disabling existing audited attributes. Delegate every Fusion operation to
core.fusion-api.audit-setup.
Setup Task Identity
- Task:
Manage Audit Policies (FND_MANAGE_AUDIT_POLICIES)
- Pillar:
CX
- Offering:
Sales
- Functional area:
Sales Foundation (ORA_ZBS_SALES_FOUNDATION)
- Parent skill:
cx.sales.sales-foundation
The catalog reports CSV export/import support for the wider setup task. This
dedicated capability does not export or import FSM setup data; route any
separate task-level CSV request through the parent workflow. Audit reads and
writes in this skill always use core.fusion-api.audit-setup.
Required Read Order
- Read
references/audit-object-map.json before resolving an object.
- Read
core/fusion-api/audit-setup/SKILL.md before any Fusion operation.
- For project work, consume the active project context and use the declared
project-management dependencies for durable evidence.
Object Boundary
Treat the exact account, contact, and household entries in the object map
as supported root candidates. Before using any mapped root for status, child
resolution, attribute inventory, preview, or mutation, reconcile its complete
identity against a fresh live get-setup --application sales response.
Support either a validated root itself or one child resolved from that live
inventory.
Use the map's application and application_module together: retain rows with
webApplication=sales and the exact mapped amname before root or child
resolution. The same Account OrganizationDVO also appears under customer
in ActivityAM without the Account audit hierarchy. That occurrence is not an
alternative inventory for this skill. Keep Account's business-object identity
unchanged; application scope and object identity are distinct.
- Resolve
Account only to OrganizationDVO, Contact only to PersonDVO,
and Household only to GroupVO.
- A root is live-validated only when at least one
objectDetails row has the
exact mapped viewObject and its parentObjectList contains the exact mapped
parent_business_object. Multiple rows are acceptable only when they resolve
to the same object and parent identity. Fail closed on no match or conflicting
identities and classify the result as catalog_or_metadata_mismatch.
- Never treat
check-status as proof that a root exists. Fusion can return
auditSwitch: NONE for an unknown object identity; use get-setup for
existence and parent-binding validation before calling check-status.
- Require
audit_object=account|contact|household before resolving a child.
The selected root disambiguates children that are valid beneath multiple
roots.
- Resolve
child_audit_object by exact viewObject or a unique exact
viewObjectDisplayName within the selected root's live hierarchy, using the
procedure below. The child viewObject must differ from the root.
- For a resolved child, use its live immediate parent on the selected root path
as
parentBusinessObject; do not substitute the root for a nested parent.
- The root's
excluded_names reject alternative root identities only. They
are not child exclusions: Sales Account is a valid Account child when its
live parent binding proves membership. Apply only
child_resolution.excluded_display_names to child candidates.
- Permit
audit_object=both (Account and Contact) or audit_object=all
(Account, Contact, and Household) only for read-only root status checks.
Require one root and at most one child for every other operation and every
mutation.
Supported Operations
| Operation |
Support |
Core Audit Setup route |
view-status |
Automated read-only |
check-status |
enable-object |
Approved live mutation |
check-status, then update-status, then check-status |
list-auditable-attributes |
Automated read-only inventory |
get-setup --application sales |
list-child-objects |
Automated read-only inventory |
get-setup --application sales |
get-enabled-attributes |
Unsupported by the API |
No Fusion call; return UNSUPPORTED_API |
enable-attributes |
Approved live mutation |
get-setup, check-status, update-status, then check-status |
Do not expose internal operation names when the user's natural-language intent
is unambiguous.
Core Delegation Boundary
- Use only
core.fusion-api.audit-setup for Audit Setup reads and writes.
- Do not copy its OAuth flow, REST endpoints, request transport, token refresh,
response normalization, or retry implementation into this skill.
- Do not invoke Audit Setup endpoints directly, call a generic REST client as a
substitute, or modify a core skill for Account-, Contact-, or
Household-specific behavior.
- For root and child attribute enablement, this specialized skill owns the
additive semantics: an
attributesList containing only requested
isAuditable: true rows leaves omitted audited attributes unchanged.
- Pass the exact environment, object identity, payload, and execution options
to the core capability and consume its structured result, diagnostics, and
audit summary.
Preflight Checks
Before any Fusion-changing action:
- Resolve exactly one target environment and confirm it is the environment the
user intends to change.
- Resolve exactly one supported root from the object map and reconcile its
exact
business_object and parent_business_object against a fresh live
inventory. When a child is requested, resolve it from the same fresh live
inventory and prove every parent link back to the selected root in the
mapped application module.
- Confirm authentication readiness, required OAuth scope, and Audit Setup
privileges through the core capability.
- Validate the requested operation, required inputs, and mutually exclusive
options before building a payload.
- For attribute enablement, validate every exact attribute against the same
live inventory row used to resolve the root or child object.
- Confirm the operation is live, show its side effects, and require the exact
preview approval defined below.
- Revalidate the environment, object, payload, and fingerprint immediately
before execution; stop if any value changed.
View Object Audit Status
- Resolve
account, contact, household, both, or all from the object
map and reconcile every selected root against a fresh live inventory, or
resolve one requested child beneath exactly one live-validated root. both
means Account and Contact; all means Account, Contact, and Household.
- Invoke core Audit Setup
check-status separately for each live-validated
object.
- Return the exact business object,
auditSwitch, last-update time when
present, environment summary, and core diagnostics.
- Do not interpret
NONE, OFF, or a missing affirmative switch as enabled.
Read-only status checks do not require execution approval.
Enable Object Audit
- Complete the preflight checks for exactly one object.
- Invoke core Audit Setup
check-status after the fresh live-inventory
reconciliation. Do not use this status response as object-existence proof.
- If
auditSwitch is already ON, return NO_CHANGE_REQUIRED; do not invoke
a mutation.
- Otherwise build a preview that contains the environment, display name,
business object, parent business object, current status, requested status,
exact
enable: true payload, impact, and preview fingerprint.
- Stop for explicit approval bound to that exact preview. Approval of another
object, environment, payload, plan, or earlier preview is invalid.
- Immediately before execution, rerun the applicable preflight checks and
ensure the preview fingerprint remains unchanged.
- Invoke core Audit Setup
update-status exactly once. Never retry a live
mutation automatically.
- Verify object status with a separate core
check-status read.
- Return
VERIFIED_SUCCESS, UNVERIFIED_SUCCESS, NO_CHANGE_REQUIRED, or a
classified failure.
Child Object Inventory and Resolution
Use core Audit Setup get-setup --application sales as the source of live
child-object identity and parent membership. Read all objectDetails rows from
the core result, then restrict them to the mapped application and module.
- Resolve and live-validate the selected root from
references/audit-object-map.json in that scoped inventory.
- Build parent-to-child links from each row's
parentObjectList, ignoring
self-parent entries. Each non-self entry is a possible parent binding, not
an ordered ancestor path. Traverse from the selected root to include direct
children and nested descendants. Use visited identities per path to stop
cycles; never cross application-module boundaries or infer a link by name.
- Apply only
child_resolution.excluded_display_names to child candidates.
Keep live-bound Sales Account children; the root's excluded_names do not
apply here. Shared children may belong to several roots; retain only paths
reachable from the user-selected root.
- For
list-child-objects, return viewObject, viewObjectDisplayName, the
full parentObjectList, application, module, depth, and root-to-child paths.
Collapse identical rows, preserving distinct parent bindings. Do not persist
the result as a release-independent catalog.
- For a requested child, require an exact view-object match or one unique exact
display-name match in that hierarchy. Reject zero matches, conflicting rows,
missing parent metadata, and disconnected objects. If several immediate
parents or paths remain, list the choices and require selection before a
status check, attribute lookup, preview, or mutation.
- Record
root_object_key, child_business_object,
child_object_display_name, full parent_object_list, application,
application_module, root_to_child_path, and the live immediate parent as
parent_business_object. For a direct child that parent is the selected
root. For a descendant it is the preceding object on the validated path.
Revalidate every link and this exact parent before any mutation.
An empty child inventory is not proof that Account has no auditable children.
If the mapped module/root is absent or no children are discovered, return
INCOMPLETE_INVENTORY with catalog_or_metadata_mismatch, the queried scope,
and a next action to check metadata exposure and Audit Setup privileges. Do
not silently fall back to customer, report unsupported children, or permit a
mutation against an unresolved identity.
For documented support questions or a discrepancy, consult Oracle's current
Sales audit hierarchy.
Distinguish documented support from live discovery; documentation supplies
business labels, not executable view-object or parent identities. Never use
it to invent a mutation target. The
Audit Setup contract
defines parent identities through application-module view links.
Auditable Attribute Inventory
Use core Audit Setup get-setup --application sales only to obtain the
available/auditable field inventory for the selected root or resolved child.
Filter by the mapped application/module, exact resolved viewObject, and
selected parent binding; do not merge attributes from other occurrences of
the same view object. Return attribute names and display names that the
response identifies as selectable and auditable.
Never describe this inventory as the currently enabled selection.
Enabled Attribute Read Limitation
For get-enabled-attributes, return a structured result with:
{
"status": "UNSUPPORTED_API",
"reason": "Fusion Audit Setup does not expose the current enabled-attribute selection through REST.",
"manual_location": "Setup and Maintenance > Manage Audit Policies > Sales > selected Account, Contact, Household, or child object > Attributes",
"enhancement_request": "ER 34232448"
}
Do not inspect the UI, request UI evidence, accept a manually supplied current
selection, or attempt to verify the current selection. Do not infer it from
get-setup, check-status, audit history, a prior skill run, or an
update-status response.
Enable Attributes
Enabling named attributes is additive. Submit only the attributes the user asks
to enable with isAuditable: true; attributes omitted from the request remain
unchanged. Do not request the current enabled-attribute selection and do not ask
the user for a complete replacement list.
- Require exactly one resolved root or child object, a non-empty unique list
of exact attribute names, and the target environment.
- Complete the preflight checks, including live inventory validation for every
requested attribute. Reject unknown, ambiguous, duplicate, or cross-object
names.
- Invoke core Audit Setup
check-status and record the object audit state.
- Sort the unique attribute names deterministically and build the complete
request payload with
enable: true and one isAuditable: true row per
requested attribute. Do not add negative rows or rows for omitted
attributes.
- Present one immutable preview containing the exact environment, object,
additive semantics, requested attribute list, exact payload, impact, and
SHA-256 fingerprint of the canonical payload.
- For a child, include the selected root, child identity, full live
parentObjectList, application/module, validated root-to-child path, and
chosen immediate parentBusinessObject in the preview.
- State prominently:
This enables only the requested attributes; existing audited attributes that are omitted from this payload remain enabled.
- Stop for separate explicit approval for this one resolved object and exact
fingerprint. Any environment, object, attribute, payload, or fingerprint
change invalidates approval.
- Immediately before execution, rerun the applicable preflight checks,
including every live parent link on the selected path when applicable, and
confirm the preview remains unchanged. Invoke core Audit Setup
update-status exactly once. Never retry the live mutation automatically.
- Verify with core Audit Setup
check-status that the resolved root or child
object auditing is ON.
- Return
FIELD_ENABLEMENT_SUBMITTED_NOT_READ_BACK for field verification.
Treat the successful core response as evidence for the submitted update
only, never as an independent read of the current enabled selection.
Approval Contract
- Require a separate preview and approval for every resolved root or child.
- Bind approval to the exact environment, root context, resolved object,
operation, payload, and fingerprint.
- Require approval immediately before the core mutation step.
- Never retry a live mutation automatically.
- Do not treat approval of a plan, another object, another environment, a
prior payload, or a read-only call as mutation approval.
- Do not combine roots or children into one mutation or continue from one
approved mutation to another without a separate preview and approval.
Machine-Readable Outputs
Return applicable fields in a structured result:
operation
root_object_key, object_scope, object_display_name, business_object,
parent_business_object, parent_object_list, application,
application_module, root_to_child_path, and inventory_status
child_object_inventory and resolved_audit_object
environment
object_audit_status
auditable_attribute_inventory
enabled_attribute_result
requested_attributes
attribute_update_semantics
preview_fingerprint
execution_result
verification_result
diagnostics
errors
Redact tokens, authorization headers, client secrets, token-cache contents, and
sensitive environment configuration.
Error and Recovery Contract
Classify failures as input_validation, catalog_or_metadata_mismatch,
auth_expired_or_invalid, authorization_or_privilege,
transport_or_environment, fusion_api_error, artifact_persistence, or
approval_blocker.
- Fail before side effects for an unsupported root, unbound or ambiguous child,
missing live
parentObjectList, unsupported operation, empty attribute list,
ambiguous or invalid attribute, stale preview, or missing approval.
- Permit the core capability to refresh a cache-managed token once after a
rejected cached token. Do not replace an explicit token silently.
- Retry only bounded read-only transport failures through the core capability.
- Never retry
update-status without a new preview and explicit approval.
- On an indeterminate mutation response, stop and report the environment,
object, operation, payload fingerprint, known response details, and manual
reconciliation path. Do not resubmit automatically.
- Do not attempt rollback by reconstructing a prior attribute selection; the
API cannot retrieve that selection authoritatively. If a requested attribute
must later be disabled, handle it as a separate explicit operation and
approval rather than as compensation for this additive enablement.
Persistence
When project context is supplied, persist the redacted preview, validation
result, execution result, verification result, diagnostics, and append-only
skill-run record under the declared workspace paths. Record the core skill run
reference and payload fingerprint. Do not persist attribute selections as an
authoritative baseline because later changes can occur outside this skill.
Append token usage using the manifest policy. Never persist OAuth tokens,
authorization headers, token-cache contents, client secrets, or raw sensitive
environment properties.
Hierarchy Review Evidence
Review the synthetic hierarchy scenarios
when changing resolution rules. The linked inventories and structured expected
outcomes cover direct, nested, shared, cyclic, ambiguous, disconnected,
module-isolated, and incomplete hierarchies. This is reviewed evidence for the
declarative workflow; text-contract tests do not execute a resolver.
Natural Prompts
Is audit enabled for Account?
Check audit for Account and Contact.
Check audit for Account, Contact, and Household.
Enable audit for Contact.
Enable audit for Household.
Show attributes available for Account auditing.
Which Contact attributes are currently enabled for audit?
Enable audit for Account CEO Name.
Enable DUNSNumberC and StockSymbol auditing for Account.
List child objects available for Account auditing.
Enable audit for Email Address on the Email child object of Contact.
List child objects available for Household auditing.
Ownership and Review
- Owner: CX Sales pillar team.
- Functional reviewer: CX Sales Pillar Lead or Accounts, Contacts, and
Households SME.
- Framework reviewer: FDOS A-Team/core reviewer.
- QA reviewer: required for root and child resolution, status, approval,
attribute enablement, failure, and persistence behavior.
1---2skill_id: "cx.sales.sales-foundation.manage-audit-policies"3name: manage-account-contact-and-household-audit-policies4description: "Checks and enables Oracle Fusion audit for CX Account, Contact, Household, and their live-resolved child business objects, and additively enables named audit attributes through the shared Audit Setup core capability. Use for parent or child object audit-status checks, object-level audit enablement, audit-attribute inventory validation, requests to identify currently enabled audit attributes, and approved enablement of one or more named attributes without disabling omitted attributes."5layer: "pillar"6pillar: "CX"7offering: "Sales"8functional_area: "Sales Foundation"9functional_area_code: "ORA_ZBS_SALES_FOUNDATION"10task_code: "FND_MANAGE_AUDIT_POLICIES"11task_name: "Manage Audit Policies"12parent_skill_id: "cx.sales.sales-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: "import"20execution_mode: "hybrid"21owner_team: "CX sales pillar team"22version: "0.5.1"23inputs:24 - "project_context"25 - "fusion_environment_context"26 - "audit_object"27 - "child_audit_object"28 - "audit_operation"29 - "requested_attributes"30 - "execution_approval"31outputs:32 - "object_audit_status"33 - "child_object_inventory"34 - "resolved_audit_object"35 - "auditable_attribute_inventory"36 - "enabled_attribute_result"37 - "immutable_audit_preview"38 - "execution_result"39 - "verification_result"40 - "diagnostics"41 - "skill_run_record"42 - "token_usage_record"43depends_on:44 - "cx.sales.sales-foundation"45 - "core.fusion-api.audit-setup"46uses_core:47 - "core.fusion-api.audit-setup"48 - "core.project-mgmt.artifact-version-manager"49 - "core.project-mgmt.artifact-registry-manager"50 - "core.project-mgmt.project-state-manager"51persists_project_state: true52token_usage_tracking:53 enabled: true54 granularity: "per_skill_run"55 artifact_type: "token_usage_record"56 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"57 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"58 required_fields:59 - "activity_start_time"60 - "skill_id"61 - "task"62 - "trigger"63 - "artifacts_written"64 - "files_read"65 - "estimated_input_tokens"66 - "estimated_output_tokens"67 - "estimated_total_tokens"68 - "estimation_method"69 - "notes"70state_updates:71 - "validation_results"72 - "reports"73 - "token_usage_records"74workspace_outputs:75 - artifact_type: "validation_result"76 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-foundation/manage-audit-policies/current/"77 versioning_policy: "major-new-version-minor-confirm-update"78 - artifact_type: "report"79 default_location: "project/{project_id}/artifacts/pillars/cx/sales/sales-foundation/manage-audit-policies/current/"80 versioning_policy: "major-new-version-minor-confirm-update"81 - artifact_type: "skill_run"82 default_location: "project/{project_id}/state/runs/"83 versioning_policy: "append-only"84 - artifact_type: "token_usage_record"85 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"86 versioning_policy: "append-only"87applicability:88 industries:89 - "All"90 countries:91 - "All"92 fusion_releases:93 - "Oracle Fusion Cloud Applications 26B or newer"94side_effects:95 - "Reads Account, Contact, Household, or a live-resolved child object's audit setup through core.fusion-api.audit-setup."96 - "May enable audit for exactly one Account, Contact, Household, or validated child business object after explicit approval."97 - "May additively enable named audit attributes for exactly one Account, Contact, Household, or validated child business object after explicit approval."98 - "May persist redacted validation, execution, and skill-run evidence in the active project workspace."99required_privileges:100 - "Access to the exact target Oracle Fusion environment and required OAuth scope."101 - "Fusion privileges appropriate to view and manage audit setup."102metadata:103 source: https://skillmd.com/skills/oracle/manage-account-contact-and-household-audit-policies104---105106# Manage Account, Contact, and Household Audit Policies107108## Purpose109110Check and enable audit for CX Account, Contact, Household, and child business111objects that the live Audit Setup inventory binds to one of those roots.112Validate requested attribute names and enable those attributes without113disabling existing audited attributes. Delegate every Fusion operation to114`core.fusion-api.audit-setup`.115116## Setup Task Identity117118- Task: `Manage Audit Policies` (`FND_MANAGE_AUDIT_POLICIES`)119- Pillar: `CX`120- Offering: `Sales`121- Functional area: `Sales Foundation` (`ORA_ZBS_SALES_FOUNDATION`)122- Parent skill: `cx.sales.sales-foundation`123124The catalog reports CSV export/import support for the wider setup task. This125dedicated capability does not export or import FSM setup data; route any126separate task-level CSV request through the parent workflow. Audit reads and127writes in this skill always use `core.fusion-api.audit-setup`.128129## Required Read Order1301311. Read `references/audit-object-map.json` before resolving an object.1322. Read `core/fusion-api/audit-setup/SKILL.md` before any Fusion operation.1333. For project work, consume the active project context and use the declared134 project-management dependencies for durable evidence.135136## Object Boundary137138Treat the exact `account`, `contact`, and `household` entries in the object map139as supported root candidates. Before using any mapped root for status, child140resolution, attribute inventory, preview, or mutation, reconcile its complete141identity against a fresh live `get-setup --application sales` response.142Support either a validated root itself or one child resolved from that live143inventory.144145Use the map's `application` and `application_module` together: retain rows with146`webApplication=sales` and the exact mapped `amname` before root or child147resolution. The same Account `OrganizationDVO` also appears under `customer`148in ActivityAM without the Account audit hierarchy. That occurrence is not an149alternative inventory for this skill. Keep Account's business-object identity150unchanged; application scope and object identity are distinct.151152- Resolve `Account` only to `OrganizationDVO`, `Contact` only to `PersonDVO`,153 and `Household` only to `GroupVO`.154- A root is live-validated only when at least one `objectDetails` row has the155 exact mapped `viewObject` and its `parentObjectList` contains the exact mapped156 `parent_business_object`. Multiple rows are acceptable only when they resolve157 to the same object and parent identity. Fail closed on no match or conflicting158 identities and classify the result as `catalog_or_metadata_mismatch`.159- Never treat `check-status` as proof that a root exists. Fusion can return160 `auditSwitch: NONE` for an unknown object identity; use `get-setup` for161 existence and parent-binding validation before calling `check-status`.162- Require `audit_object=account|contact|household` before resolving a child.163 The selected root disambiguates children that are valid beneath multiple164 roots.165- Resolve `child_audit_object` by exact `viewObject` or a unique exact166 `viewObjectDisplayName` within the selected root's live hierarchy, using the167 procedure below. The child `viewObject` must differ from the root.168- For a resolved child, use its live immediate parent on the selected root path169 as `parentBusinessObject`; do not substitute the root for a nested parent.170- The root's `excluded_names` reject alternative root identities only. They171 are not child exclusions: Sales Account is a valid Account child when its172 live parent binding proves membership. Apply only173 `child_resolution.excluded_display_names` to child candidates.174- Permit `audit_object=both` (Account and Contact) or `audit_object=all`175 (Account, Contact, and Household) only for read-only root status checks.176 Require one root and at most one child for every other operation and every177 mutation.178179## Supported Operations180181| Operation | Support | Core Audit Setup route |182| --- | --- | --- |183| `view-status` | Automated read-only | `check-status` |184| `enable-object` | Approved live mutation | `check-status`, then `update-status`, then `check-status` |185| `list-auditable-attributes` | Automated read-only inventory | `get-setup --application sales` |186| `list-child-objects` | Automated read-only inventory | `get-setup --application sales` |187| `get-enabled-attributes` | Unsupported by the API | No Fusion call; return `UNSUPPORTED_API` |188| `enable-attributes` | Approved live mutation | `get-setup`, `check-status`, `update-status`, then `check-status` |189190Do not expose internal operation names when the user's natural-language intent191is unambiguous.192193## Core Delegation Boundary194195- Use only `core.fusion-api.audit-setup` for Audit Setup reads and writes.196- Do not copy its OAuth flow, REST endpoints, request transport, token refresh,197 response normalization, or retry implementation into this skill.198- Do not invoke Audit Setup endpoints directly, call a generic REST client as a199 substitute, or modify a core skill for Account-, Contact-, or200 Household-specific behavior.201- For root and child attribute enablement, this specialized skill owns the202 additive semantics: an `attributesList` containing only requested203 `isAuditable: true` rows leaves omitted audited attributes unchanged.204- Pass the exact environment, object identity, payload, and execution options205 to the core capability and consume its structured result, diagnostics, and206 audit summary.207208## Preflight Checks209210Before any Fusion-changing action:2112121. Resolve exactly one target environment and confirm it is the environment the213 user intends to change.2142. Resolve exactly one supported root from the object map and reconcile its215 exact `business_object` and `parent_business_object` against a fresh live216 inventory. When a child is requested, resolve it from the same fresh live217 inventory and prove every parent link back to the selected root in the218 mapped application module.2193. Confirm authentication readiness, required OAuth scope, and Audit Setup220 privileges through the core capability.2214. Validate the requested operation, required inputs, and mutually exclusive222 options before building a payload.2235. For attribute enablement, validate every exact attribute against the same224 live inventory row used to resolve the root or child object.2256. Confirm the operation is live, show its side effects, and require the exact226 preview approval defined below.2277. Revalidate the environment, object, payload, and fingerprint immediately228 before execution; stop if any value changed.229230## View Object Audit Status2312321. Resolve `account`, `contact`, `household`, `both`, or `all` from the object233 map and reconcile every selected root against a fresh live inventory, or234 resolve one requested child beneath exactly one live-validated root. `both`235 means Account and Contact; `all` means Account, Contact, and Household.2362. Invoke core Audit Setup `check-status` separately for each live-validated237 object.2383. Return the exact business object, `auditSwitch`, last-update time when239 present, environment summary, and core diagnostics.2404. Do not interpret `NONE`, `OFF`, or a missing affirmative switch as enabled.241242Read-only status checks do not require execution approval.243244## Enable Object Audit2452461. Complete the preflight checks for exactly one object.2472. Invoke core Audit Setup `check-status` after the fresh live-inventory248 reconciliation. Do not use this status response as object-existence proof.2493. If `auditSwitch` is already `ON`, return `NO_CHANGE_REQUIRED`; do not invoke250 a mutation.2514. Otherwise build a preview that contains the environment, display name,252 business object, parent business object, current status, requested status,253 exact `enable: true` payload, impact, and preview fingerprint.2545. Stop for explicit approval bound to that exact preview. Approval of another255 object, environment, payload, plan, or earlier preview is invalid.2566. Immediately before execution, rerun the applicable preflight checks and257 ensure the preview fingerprint remains unchanged.2587. Invoke core Audit Setup `update-status` exactly once. Never retry a live259 mutation automatically.2608. Verify object status with a separate core `check-status` read.2619. Return `VERIFIED_SUCCESS`, `UNVERIFIED_SUCCESS`, `NO_CHANGE_REQUIRED`, or a262 classified failure.263264## Child Object Inventory and Resolution265266Use core Audit Setup `get-setup --application sales` as the source of live267child-object identity and parent membership. Read all `objectDetails` rows from268the core result, then restrict them to the mapped application and module.2692701. Resolve and live-validate the selected root from271 `references/audit-object-map.json` in that scoped inventory.2722. Build parent-to-child links from each row's `parentObjectList`, ignoring273 self-parent entries. Each non-self entry is a possible parent binding, not274 an ordered ancestor path. Traverse from the selected root to include direct275 children and nested descendants. Use visited identities per path to stop276 cycles; never cross application-module boundaries or infer a link by name.2773. Apply only `child_resolution.excluded_display_names` to child candidates.278 Keep live-bound Sales Account children; the root's `excluded_names` do not279 apply here. Shared children may belong to several roots; retain only paths280 reachable from the user-selected root.2814. For `list-child-objects`, return `viewObject`, `viewObjectDisplayName`, the282 full `parentObjectList`, application, module, depth, and root-to-child paths.283 Collapse identical rows, preserving distinct parent bindings. Do not persist284 the result as a release-independent catalog.2855. For a requested child, require an exact view-object match or one unique exact286 display-name match in that hierarchy. Reject zero matches, conflicting rows,287 missing parent metadata, and disconnected objects. If several immediate288 parents or paths remain, list the choices and require selection before a289 status check, attribute lookup, preview, or mutation.2906. Record `root_object_key`, `child_business_object`,291 `child_object_display_name`, full `parent_object_list`, `application`,292 `application_module`, `root_to_child_path`, and the live immediate parent as293 `parent_business_object`. For a direct child that parent is the selected294 root. For a descendant it is the preceding object on the validated path.295 Revalidate every link and this exact parent before any mutation.296297An empty child inventory is not proof that Account has no auditable children.298If the mapped module/root is absent or no children are discovered, return299`INCOMPLETE_INVENTORY` with `catalog_or_metadata_mismatch`, the queried scope,300and a next action to check metadata exposure and Audit Setup privileges. Do301not silently fall back to `customer`, report unsupported children, or permit a302mutation against an unresolved identity.303304For documented support questions or a discrepancy, consult Oracle's current305[Sales audit hierarchy](https://docs.oracle.com/en/cloud/saas/sales/oasal/use-auditing-to-monitor-sales-application-changes.html).306Distinguish documented support from live discovery; documentation supplies307business labels, not executable view-object or parent identities. Never use308it to invent a mutation target. The309[Audit Setup contract](https://docs.oracle.com/en/cloud/saas/applications-common/26b/farca/op-fscmrestapi-fndauditrestservice-audittrail-get-auditsetup-post.html)310defines parent identities through application-module view links.311312## Auditable Attribute Inventory313314Use core Audit Setup `get-setup --application sales` only to obtain the315available/auditable field inventory for the selected root or resolved child.316Filter by the mapped application/module, exact resolved `viewObject`, and317selected parent binding; do not merge attributes from other occurrences of318the same view object. Return attribute names and display names that the319response identifies as selectable and auditable.320321Never describe this inventory as the currently enabled selection.322323## Enabled Attribute Read Limitation324325For `get-enabled-attributes`, return a structured result with:326327```json328{329 "status": "UNSUPPORTED_API",330 "reason": "Fusion Audit Setup does not expose the current enabled-attribute selection through REST.",331 "manual_location": "Setup and Maintenance > Manage Audit Policies > Sales > selected Account, Contact, Household, or child object > Attributes",332 "enhancement_request": "ER 34232448"333}334```335336Do not inspect the UI, request UI evidence, accept a manually supplied current337selection, or attempt to verify the current selection. Do not infer it from338`get-setup`, `check-status`, audit history, a prior skill run, or an339`update-status` response.340341## Enable Attributes342343Enabling named attributes is additive. Submit only the attributes the user asks344to enable with `isAuditable: true`; attributes omitted from the request remain345unchanged. Do not request the current enabled-attribute selection and do not ask346the user for a complete replacement list.3473481. Require exactly one resolved root or child object, a non-empty unique list349 of exact attribute names, and the target environment.3502. Complete the preflight checks, including live inventory validation for every351 requested attribute. Reject unknown, ambiguous, duplicate, or cross-object352 names.3533. Invoke core Audit Setup `check-status` and record the object audit state.3544. Sort the unique attribute names deterministically and build the complete355 request payload with `enable: true` and one `isAuditable: true` row per356 requested attribute. Do not add negative rows or rows for omitted357 attributes.3585. Present one immutable preview containing the exact environment, object,359 additive semantics, requested attribute list, exact payload, impact, and360 SHA-256 fingerprint of the canonical payload.3616. For a child, include the selected root, child identity, full live362 `parentObjectList`, application/module, validated root-to-child path, and363 chosen immediate `parentBusinessObject` in the preview.3647. State prominently: `This enables only the requested attributes; existing365 audited attributes that are omitted from this payload remain enabled.`3668. Stop for separate explicit approval for this one resolved object and exact367 fingerprint. Any environment, object, attribute, payload, or fingerprint368 change invalidates approval.3699. Immediately before execution, rerun the applicable preflight checks,370 including every live parent link on the selected path when applicable, and371 confirm the preview remains unchanged. Invoke core Audit Setup372 `update-status` exactly once. Never retry the live mutation automatically.37310. Verify with core Audit Setup `check-status` that the resolved root or child374 object auditing is `ON`.37511. Return `FIELD_ENABLEMENT_SUBMITTED_NOT_READ_BACK` for field verification.376 Treat the successful core response as evidence for the submitted update377 only, never as an independent read of the current enabled selection.378379## Approval Contract380381- Require a separate preview and approval for every resolved root or child.382- Bind approval to the exact environment, root context, resolved object,383 operation, payload, and fingerprint.384- Require approval immediately before the core mutation step.385- Never retry a live mutation automatically.386- Do not treat approval of a plan, another object, another environment, a387 prior payload, or a read-only call as mutation approval.388- Do not combine roots or children into one mutation or continue from one389 approved mutation to another without a separate preview and approval.390391## Machine-Readable Outputs392393Return applicable fields in a structured result:394395- `operation`396- `root_object_key`, `object_scope`, `object_display_name`, `business_object`,397 `parent_business_object`, `parent_object_list`, `application`,398 `application_module`, `root_to_child_path`, and `inventory_status`399- `child_object_inventory` and `resolved_audit_object`400- `environment`401- `object_audit_status`402- `auditable_attribute_inventory`403- `enabled_attribute_result`404- `requested_attributes`405- `attribute_update_semantics`406- `preview_fingerprint`407- `execution_result`408- `verification_result`409- `diagnostics`410- `errors`411412Redact tokens, authorization headers, client secrets, token-cache contents, and413sensitive environment configuration.414415## Error and Recovery Contract416417Classify failures as `input_validation`, `catalog_or_metadata_mismatch`,418`auth_expired_or_invalid`, `authorization_or_privilege`,419`transport_or_environment`, `fusion_api_error`, `artifact_persistence`, or420`approval_blocker`.421422- Fail before side effects for an unsupported root, unbound or ambiguous child,423 missing live `parentObjectList`, unsupported operation, empty attribute list,424 ambiguous or invalid attribute, stale preview, or missing approval.425- Permit the core capability to refresh a cache-managed token once after a426 rejected cached token. Do not replace an explicit token silently.427- Retry only bounded read-only transport failures through the core capability.428- Never retry `update-status` without a new preview and explicit approval.429- On an indeterminate mutation response, stop and report the environment,430 object, operation, payload fingerprint, known response details, and manual431 reconciliation path. Do not resubmit automatically.432- Do not attempt rollback by reconstructing a prior attribute selection; the433 API cannot retrieve that selection authoritatively. If a requested attribute434 must later be disabled, handle it as a separate explicit operation and435 approval rather than as compensation for this additive enablement.436437## Persistence438439When project context is supplied, persist the redacted preview, validation440result, execution result, verification result, diagnostics, and append-only441skill-run record under the declared workspace paths. Record the core skill run442reference and payload fingerprint. Do not persist attribute selections as an443authoritative baseline because later changes can occur outside this skill.444445Append token usage using the manifest policy. Never persist OAuth tokens,446authorization headers, token-cache contents, client secrets, or raw sensitive447environment properties.448449## Hierarchy Review Evidence450451Review [the synthetic hierarchy scenarios](references/hierarchy-resolution-review.md)452when changing resolution rules. The linked inventories and structured expected453outcomes cover direct, nested, shared, cyclic, ambiguous, disconnected,454module-isolated, and incomplete hierarchies. This is reviewed evidence for the455declarative workflow; text-contract tests do not execute a resolver.456457## Natural Prompts458459- `Is audit enabled for Account?`460- `Check audit for Account and Contact.`461- `Check audit for Account, Contact, and Household.`462- `Enable audit for Contact.`463- `Enable audit for Household.`464- `Show attributes available for Account auditing.`465- `Which Contact attributes are currently enabled for audit?`466- `Enable audit for Account CEO Name.`467- `Enable DUNSNumberC and StockSymbol auditing for Account.`468- `List child objects available for Account auditing.`469- `Enable audit for Email Address on the Email child object of Contact.`470- `List child objects available for Household auditing.`471472## Ownership and Review473474- Owner: CX Sales pillar team.475- Functional reviewer: CX Sales Pillar Lead or Accounts, Contacts, and476 Households SME.477- Framework reviewer: FDOS A-Team/core reviewer.478- QA reviewer: required for root and child resolution, status, approval,479 attribute enablement, failure, and persistence behavior.