Results for “g_rlm_installed_flag”

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

Overview

OE_VALIDATE is a core Order Management validation package in Oracle E-Business Suite, delivered under the APPS schema. Its principal business function is to centralize attribute-level validation logic for the Order Management schema so that validations are applied consistently whether an order is entered through the Order Management forms, loaded through the Order Import concurrent program, or processed through public APIs such as OE_ORDER_PUB. The package body carries the header comment for OEXSVATB.pls (120.11) and declares the global constant G_PKG_NAME as "OE_Validate" together with G_RLM_INSTALLED_FLAG, which controls behavior contingent on whether Release Management functionality is installed.

The user search term "fptval-21779" is a known EBS error reference associated with order validation failures surfaced by OE_VALIDATE-based logic; errors of this class are raised when an attribute fails a mandatory, reference, or business-rule check during order booking or import. The package is documented in the ETRM repository for both 12.1.1 and 12.2.2 with an API classification of OTHER, and it is referenced by 22 other packages, confirming its role as a widely reused validation utility.

Key Procedures and Functions

The ETRM metadata documents 354 procedures and functions in this package body. Notable examples include:

• GET_ATTR_TBL – Initializes FND_API.g_attr_tbl with the ordered list of attribute names validated by this package. The generator appends new attributes before the end-generate marker; the source header instructs "DO NOT REMOVE," because the table drives dynamic validation dispatch.
• Attribute validators such as ACCOUNTING_RULE, ACCOUNTING_RULE_DURATION, AGREEMENT, BLANKET_NUMBER, BOOKED, CANCELLED, CANCELLED_QUANTITY, AUTO_SELECTED_QUANTITY, ACTUAL_ARRIVAL_DATE, and ACTUAL_SHIPMENT_DATE – each validates a specific order header or line attribute against configured reference data and business rules.
• Configuration validators such as ATO_LINE, COMPONENT, COMPONENT_NUMBER, COMPONENT_SEQUENCE, and CONFIG_HEADER – these enforce rules for configured (ATO/PTO) items and their component lines.
• Service and subscription validators such as SERVICE_COV_TEMPLATE_ID, SERVICE_BILLING_PROFILE, SERVICE_BILL_OPTION, and SERVICE_SUBS_TEMPLATE_ID – these validate service contracts, billing profiles, and subscription templates.

Tables Accessed

OE_VALIDATE reads reference and setup data through APPS synonyms, including:

• OE_ORDER_SOURCES and OE_AGREEMENTS_B – order source and agreement validation.
• OE_SALES_CREDIT_TYPES – sales credit type validation for order lines.
• MTL_GRADES_B – grade code validation for inventory items.
• AR_RECEIPT_CLASSES, AR_RECEIPT_METHODS, and IBY_FNDCPT_TX_EXTENSIONS – receipt class, receipt method, and payment transaction extension lookups used in order and return validation.
• HZ_CUST_ACCOUNT_ROLES, HZ_CUST_SITE_USES, HZ_CONTACT_POINTS, and HZ_ROLE_RESPONSIBILITY – customer, site use, contact, and role validation.
• JTF_RS_SALESREPS and JTF_RS_RESOURCE_EXTNS – salesperson and resource validation.
• PLITBLM – a PL/SQL table used for temporary storage during validation.

Usage Notes

OE_VALIDATE is not typically called directly by end users. It is invoked indirectly by Order Management forms, the Order Import concurrent program, and public APIs such as OE_ORDER_PUB during order entry, booking, and import. The package relies on FND_API.g_attr_tbl to map attribute names to validation routines, so customizations should extend this table rather than alter existing entries. Because it is referenced by 22 other packages, changes to OE_VALIDATE signatures or validation rules can have broad impact across Order Management. When diagnosing errors such as "fptval-21779," the failing attribute name can be used to locate the corresponding validator in this package for troubleshooting.