Search Results iem_intent_docs_pvt

Overview

The APPS.IEM_INTENT_DOCS_PVT package body is a private (PVT-classified) PL/SQL API within the Oracle E-Business Suite E-Tax/Receivables (formerly ETRM) product family. Its role is to encapsulate the low-level database operations that maintain records in the IEM_ACCOUNT_INTENT_DOCS table, which stores "intent documents" — formal documentary declarations by which a company signals its intent to conduct cross-border transactions under a specific trade or tax regime. Such intent documents are fundamental to tax determination, particularly for VAT/GST recovery and customs treatment, because entitlement to preferential rates or refunds depends on a valid, on-file intent declaration.

The package is classified as private, meaning it is not intended as a public integration point for external consumers; instead it is invoked internally by other EBS components, most likely a public-facing wrapper package, a Forms-based user interface, or a concurrent program that manages intent document maintenance. The metadata notes that the package is VALID in the APPS schema and is not referenced by any other database object, confirming its position as a leaf-level implementation unit that reads and writes directly to the underlying table.

Key Procedures and Functions

Two procedures/functions are documented in the ETRM metadata for this package body:

• CREATE_ITEM — Inserts a new intent document record into the underlying IEM_ACCOUNT_INTENT_DOCS table. This is the primary maintenance routine used when a new documentary declaration is registered against a customer account or transaction regime. It is the entry point through which callers supply the attributes of the intent document (account association, document type, effective dates, and status) for persistence.
• DELETE_ITEM — Removes an existing intent document record. This supports lifecycle management, allowing documents that have expired, been superseded, or been entered in error to be purged from the active data set so they no longer influence subsequent tax or customs determination.

No parameter lists are exposed in the ETRM documentation, and no additional logic should be assumed beyond the create/delete semantics implied by the procedure names. Any public API (such as IEM_ACCOUNT_INTENT_DOCS_PUB or similar) that fronts these operations would supply the arguments at runtime.

Tables Accessed

The dependency listing confirms that IEM_INTENT_DOCS_PVT references the following objects via APPS synonyms:

• IEM_ACCOUNT_INTENT_DOCS — the primary base table. CREATE_ITEM inserts into it and DELETE_ITEM deletes from it. This table holds the persistent record of each intent document associated with an account.
• IEM_ACCOUNT_INTENT_DOCS_S1 — a secondary object referenced by the package, appearing directly beneath the base table in the dependency tree. The _S1 suffix and the user's original search string ("iem_account_intent_docs_s1") indicate this is an index or supporting database segment on the base table, used to enforce uniqueness and accelerate lookups (for example, by account and document type) during duplicate checks or retrieval within CREATE_ITEM and DELETE_ITEM.
• DUAL — referenced indirectly for scalar evaluation, consistent with PL/SQL constructs that select from DUAL for defaulting or CURSOR-based checks.

The package relies on the STANDARD package supplied by SYS, as is typical of all PL/SQL units.

Usage Notes

Because the package is private, it is not called directly by external customizations in the normal supported pattern. It is invoked indirectly when an EBS user or process creates or removes an account intent document — typically through an Oracle Forms-based maintenance screen or an internal service routine that delegates persistence to this package. The presence of the IEM_ACCOUNT_INTENT_DOCS_S1 reference strongly suggests that duplicate validation is enforced at insert time, so callers should expect that CREATE_ITEM may raise exceptions when a conflicting document already exists. DELETE_ITEM similarly operates at row level and is intended for controlled cleanup rather than bulk purging. For release 12.1.1 and 12.2.2, the package remains VALID and is unchanged in its documented behavior; however, custom developers seeking to add intent documents programmatically should target the corresponding public API rather than calling IEM_INTENT_DOCS_PVT directly, to preserve upgrade safety and integrity of the intent document data.