Results for “get_application_number”
8 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The APPS.AR_CMGT_CREDIT_REQUEST_API package is a public Oracle Credit Management (OCM) API that supports the creation and evaluation of credit requests within Oracle E-Business Suite. Its primary business function is to initiate a credit review for a party, an account, or an account site. The package accepts a credit request payload with minimal upfront validation and then launches an asynchronous workflow that performs the detailed credit review processing in the background. This design allows callers to submit a credit request quickly and decouple the request creation from the longer-running evaluation logic handled by Oracle Workflow.
The package is classified as an API and is owned by the APPS schema, with the source declaring AUTHID CURRENT_USER. It is documented under the OCM product and is associated with the business entity AR_CREDIT_REQUEST. The header references the Credit Management API User Notes and the Oracle Credit Management User Guide (document 120ocmug.pdf) as the authoritative documentation sources. The source version carries a header string indicating maintenance through 2009 (version 120.18.12010000.2), consistent with the 12.1.1 lineage, while the package remains documented in the 12.2.2 metadata set.
Key Procedures and Functions
ETRM documents four callable units within this package:
- CREATE_CREDIT_REQUEST — Creates a credit request to initiate a credit review for a party, account, or account site. It accepts the request details, performs minimal validations, and triggers an asynchronous workflow that processes the credit request. This is the central procedure of the package and its documented display name is "Create Credit Request." A later revision added support for a parent credit request identifier and a credit request type, enabling related and hierarchical credit requests.
- IS_CREDIT_MANAGEMENT_INSTALLED — Reports whether Oracle Credit Management is installed, allowing calling code to determine whether credit management functionality is available before attempting to create or process credit requests.
- GET_APPLICATION_NUMBER — Retrieves an application number, used to identify and track credit requests generated through the API. This supports the package's use of the application number sequence and application number storage.
- Additional internal type — The source declares a
hold_reason_rec_typecollection type based onFND_NEW_MESSAGES.MESSAGE_NAME, used in conjunction with hold reason handling during credit request processing.
Tables Accessed
The package accesses its data through APPS synonyms. The principal credit management tables are AR_CMGT_CREDIT_REQUESTS and AR_CMGT_CREDIT_REQUESTS_S, which store the credit request records and their descriptive/translated attributes. AR_CMGT_APPLICATION_NUM_S supplies application number values for identifying requests. Associated credit review artifacts are held in AR_CMGT_CASE_FOLDERS, AR_CMGT_CF_RECOMMENDS, AR_CMGT_CHECK_LISTS, and AR_CMGT_SCORES, reflecting the case folder, recommendation, check list, and scoring outputs of the review process. Hold-related data is stored in AR_CMGT_HOLD_DETAILS and AR_CMGT_HOLD_DTL_S, consistent with the hold reason collection type declared in the source. Configuration and setup values are read from AR_CMGT_SETUP_OPTIONS. Supporting Oracle entities include FND_NEW_MESSAGES for message lookups, FND_USER and PER_ALL_PEOPLE_F for requestor and user identity resolution, and DUAL and PLITBLM for standard PL/SQL utility operations.
Usage Notes
AR_CMGT_CREDIT_REQUEST_API is intended to be invoked from Oracle Forms, concurrent programs, Oracle Workflow processes, and custom PL/SQL code that needs to submit credit reviews programmatically. The package is referenced by twelve other packages, indicating it is a foundational dependency within the OCM integration layer. Callers invoke CREATE_CREDIT_REQUEST with the request attributes and the standard API parameters (p_api_version, p_init_msg_list, p_commit, p_validation_level) and inspect the standard return status, message count, and message data outputs. Because validation at creation time is minimal, callers should not expect full business validation during the API call; the asynchronous workflow performs the substantive processing. Before calling the create procedure, integration code should use IS_CREDIT_MANAGEMENT_INSTALLED to confirm availability and GET_APPLICATION_NUMBER where an application number reference is required. Note that the user search term referencing an external portal URL is unrelated to this package's documented behavior and does not appear in the ETRM metadata.