# Apps Common Lookups

> Access Oracle Fusion common, standard, generic, and set-enabled lookups through the appropriate Application Common Features REST resource.

- Skill: `oracle/apps-common-lookups` (Agent Skill, multi-file: 5 files)
- Install (CLI): `npx get-skill add oracle/apps-common-lookups`
- Raw SKILL.md: https://api.skillmd.com/api/skills/oracle/apps-common-lookups/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: Oracle (https://skillmd.com/u/oracle)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/oracle/apps-common-lookups

---


# Apps Common Lookups

## Purpose

Provide a focused, safely routed Application Common Features lookup workflow.

Use the shared `core/fusion-api/rest-api-client/scripts/fusion_rest_client.py`
with relative `/fscmRestApi` endpoints. Route by the caller's named lookup
view:

| Lookup view | Guidance |
| --- | --- |
| Common lookup | [common-lookups.md](references/common-lookups.md) |
| Standard lookup | [standard-lookups.md](references/standard-lookups.md) |
| Generic lookup | [generic-lookups.md](references/generic-lookups.md) |
| Set-enabled lookup | [set-enabled-lookups.md](references/set-enabled-lookups.md) |

For an ambiguous lookup request, make read-only discovery attempts in this
order: Common, Standard, Generic, then Set-Enabled. Stop on the first exact
resource match. A `401` or `403` is an authentication or privilege failure,
not evidence that the lookup is absent; stop and report it. Do not mutate while
identifying the lookup category.

Validate the target, resource key, and body before every request. Read the
current resource and obtain explicit approval before a create, update, or
delete. Do not retry a mutating request automatically; redact credentials,
tokens, and sensitive values from results.

## Preflight and Error Handling

Preflight the lookup view, target environment, privileges, returned resource
identity, body, and approval gate. Classify failures under
`governance/error-handling-guidelines.md`; report the endpoint and safe next
action while redacting credentials, bearer tokens, headers, and sensitive
lookup values.

