Results for “wait_before_notify_days”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AP_HOLD_CODES is a Payables module reference table in the AP schema that defines the master list of invoice hold and release codes used throughout Oracle E-Business Suite. Each row represents a distinct hold reason or release reason that can be applied to an invoice, expense report, or recurring payment template. Because these codes drive the workflow that suspends payment processing, the table functions as the central control point for which holds are permitted, which ones can be manually released by end users, and which ones trigger notifications or workflow events.

In Data Vault modeling terms, the ETRM relationship metadata classifies AP_HOLD_CODES as hub-leaning. This reflects the fact that HOLD_LOOKUP_CODE acts as a durable business key referenced by multiple downstream fact-like tables (AP_HOLDS_ALL, AP_EXPENSE_REPORT_HEADERS_ALL, and AP_RECURRING_PAYMENTS_ALL), rather than a transaction entity that itself records events. The table is populated largely through seeded lookup values and maintained by the Payables administrator.

Key Information Stored

The surrogate primary key is enforced through AP_HOLD_CODES_PK on HOLD_LOOKUP_CODE. A second unique index, AP_HOLD_CODES_U1, covers HOLD_LOOKUP_CODE and ZD_EDITION_NAME, which supports the editioning model introduced in 12.2.x. The most operationally significant columns include:

• HOLD_LOOKUP_CODE — the business key and primary key value that uniquely identifies each hold or release code.
• HOLD_TYPE — distinguishes whether the code is applied as a hold or used as a release reason, governing how Payables treats the code at runtime.
• DESCRIPTION — the user-facing name of the hold shown on inquiry and entry forms.
• USER_RELEASEABLE_FLAG — indicates whether an end user may manually release the hold without system intervention.
• USER_UPDATEABLE_FLAG — controls whether users may update the hold through the application interface.
• POSTABLE_FLAG — determines whether an invoice carrying this hold can still be posted to the general ledger.
• INACTIVE_DATE — the date from which the code is no longer available for new hold assignments.
• HOLD_INSTRUCTION — free-text guidance explaining how or why the hold should be applied or cleared.
• EXTERNAL_DESCRIPTION — an alternate description intended for external communications or supplier-facing output.
• WAIT_BEFORE_NOTIFY_DAYS and REMINDER_DAYS — control the timing of workflow notifications after a hold is placed.
• INITIATE_WORKFLOW_FLAG — determines whether placing the hold launches an Oracle Workflow process.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) track row history.

Common Use Cases and Queries

Typical usage centers on reporting which holds are active, identifying user-releasable codes, and auditing hold aging. A common query lists all currently active hold codes and their release characteristics:

• SELECT hold_lookup_code, description, hold_type, user_releaseable_flag, postable_flag FROM ap_hold_codes WHERE inactive_date IS NULL;
• Reporting joins AP_HOLD_CODES to AP_HOLDS_ALL on HOLD_LOOKUP_CODE to produce a hold-aging report by vendor or invoice.
• Identifying holds that suppress posting by filtering POSTABLE_FLAG = 'N' for reconciliation with GL activity.
• Reviewing REMINDER_DAYS and WAIT_BEFORE_NOTIFY_DAYS to validate notification configuration against Payables options.

Related Objects

AP_HOLD_CODES is referenced by several key tables through foreign key relationships on HOLD_LOOKUP_CODE:

• AP_HOLDS_ALL — the primary transaction table recording holds applied to invoices; joins on HOLD_LOOKUP_CODE and additionally on RELEASE_LOOKUP_CODE when a hold is released.
• AP_EXPENSE_REPORT_HEADERS_ALL — expense report headers can carry holds resolved against this table via HOLD_LOOKUP_CODE.
• AP_RECURRING_PAYMENTS_ALL — recurring payment templates may carry holds defined by HOLD_LOOKUP_CODE.

These relationships confirm the hub role of AP_HOLD_CODES, serving as the central reference for hold and release definitions consumed across the Payables and Expenses sub-ledgers.