Search Results jtf_api_all_invalid_argument

Overview

APPS.IEC_RLCTRL_UTIL_PVT is a private utility package within the Oracle EBS Interaction Center (IEC) module, historically part of the CRM/Telephony toolset delivered under the JTF (Java Tools Framework) message namespace. The package body provides shared, internal helper logic used by other IEC release-control and runtime packages to standardize error handling and to validate the standard "Who" audit columns before a database operation is attempted. It is classified as a PVT (private) API, meaning it is intended for internal consumption by the IEC product code rather than for direct invocation by customers or third-party integrators.

The central design principle is consistent, translatable error reporting through the Oracle Application Object Library message stack (FND_MESSAGE / FND_MSG_PUB). Rather than hard-coding text, the package raises seeded messages by name and populates tokens, allowing messages to be localized and surfaced correctly in the EBS Forms or OAF user interface.

Key Procedures and Functions

The package exposes three documented procedures:

• ADD_INVALID_ARGUMENT_MSG — Registers a standard "invalid argument" error against the FND message stack. It sets the IEC message JTF_API_ALL_INVALID_ARGUMENT and fills the API_NAME, VALUE, and PARAMETER tokens before publishing the message. It is used when a caller supplies a syntactically or semantically unacceptable value.
• ADD_NULL_PARAMETER_MSG — Registers the standard "null parameter" error. This is the procedure associated with the user's search term "add_null_parameter_msg." It sets the IEC message JTF_API_ALL_NULL_PARAMETER and populates the API_NAME and NULL_PARAM tokens, reporting that a mandatory parameter was passed as NULL. Both message helpers are gated by FND_MSG_PUB.CHECK_MSG_LEVEL against the error level, so they only publish when the stack is configured to accept error-severity messages.
• VALIDATE_WHO_INFO — Validates the "Who" audit information supplied by the calling API, accepting the API name, user-facing and logical parameter names, and the USER_ID, LOGIN_ID, RESP_ID, and RESP_APPL_ID identifiers, and returning a status through an IN OUT NOCOPY parameter. It provides a reusable check that mandatory audit context exists before insert or update processing proceeds.

Tables Accessed

According to the documented metadata, the package references two tables through APPS synonyms:

• FND_USER — Read to confirm that the supplied USER_ID corresponds to a valid, enabled application user during Who-column validation.
• FND_LOGINS — Read to validate the LOGIN_ID passed by the caller, ensuring the session/login context is genuine.

No DML is documented against these tables; access is read-only validation. All error output is written to the in-memory FND message stack rather than to a database table.

Usage Notes

IEC_RLCTRL_UTIL_PVT is referenced by two other packages, which invoke its message helpers and Who-validation routine from their own public APIs. Typical invocation patterns include:

• At the top of a public IEC API, before business logic runs, to assert that required parameters are non-null and who-columns are populated.
• Inside exception or validation branches, to push a properly tokenized error onto the FND stack so the client can display it.
• From concurrent programs or forms-based code driven by the IEC runtime, where consistent message behavior is required.

Because it is a PVT package, custom code should call the public IEC APIs rather than this utility directly. Support considerations: the body header indicates version 115.5 (2003), so behavior is stable across 12.1.1 and 12.2.2, though message text resides in the IEC/JTF message dictionary and may require language-specific translations. When diagnosing the "add_null_parameter_msg" behavior, verify that FND message JTF_API_ALL_NULL_PARAMETER exists and is enabled, and that the calling API is passing the offending logical parameter name correctly.