Search Results update_case_folder_submitted

Overview

AR_CMGT_WF_ENGINE is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that provides the workflow engine plumbing for the Credit Management (CMGT) module, part of Oracle Receivables. Its procedures serve as Workflow Background Engine callback handlers, invoked by the Oracle Workflow runtime whenever the Credit Management workflow process advances through its activity graph. The package name itself reflects this role: it bridges the declarative workflow definition of the credit request lifecycle with the procedural logic needed to evaluate credit policies, run scoring models, apply automated rules, manage case folders, and route credit requests for analyst assignment and approval.

The source header, $Header: ARCMGWFS.pls 120.6 2005/12/23 19:39:04 bsarkar noship $, indicates the package has been stable since the 11i era and carried forward unchanged into 12.1.1 and 12.2.2, where it remains classified as API classification OTHER in the ETRM repository. The package exposes approximately 40 documented procedures and is referenced by three other packages, confirming it occupies a central position in the credit-to-cash workflow chain rather than functioning as a leaf utility.

Key Procedures and Functions

The documented procedures fall into several functional groups. Workflow entry and status management is handled by START_WORKFLOW, which initiates the credit request flow, and by CHECK_APPLICATION_STATUS, which evaluates the current application state as a workflow condition. Assignment logic is covered by ASSIGN_CREDIT_ANALYST and POST_CREDIT_ANALYST_ASSIGNMENT, which together determine and record which credit analyst owns a request.

Credit evaluation is performed by CHECK_CREDIT_POLICY, CHECK_SCORING_MODEL, GATHER_DATA_POINTS, CHECK_REQUIRED_DATA_POINTS, CHECK_SCORING_DATA_POINTS, and CALCULATE_SCORE, forming the analytic core of the engine. Decision automation is handled by CHECK_AUTO_RULES and GENERATE_RECOMMENDATION, while human review steps are supported by OVERRIDE_CHECKLIST, SKIP_APPROVAL, and APPROVAL_PROCESS.

State transition procedures manage the lifecycle of the underlying entities: UPDATE_CREDIT_REQ_TO_PROCESS, UPDATE_CREDIT_REQ_TO_SUBMIT, UPDATE_CASE_FOLDER_SUBMITTED, UNDO_CASE_FOLDER, and CREATE_PARTY_PROFILE. Nearly all of these functions conform to the Oracle Workflow PL/SQL callback signature, accepting itemtype, itemkey, actid, and funcmode, and returning a resultout value such as COMPLETE, WAITING, or a branch label. The exception is START_WORKFLOW, which accepts a credit request identifier and an application status defaulting to 'SUBMIT'.

Tables Accessed

The package reads and writes the core Credit Management schema tables through APPS synonyms. Credit request and case management data resides in AR_CMGT_CREDIT_REQUESTS, AR_CMGT_CASE_FOLDERS, AR_CMGT_CF_DTLS, and AR_CMGT_CF_RECOMMENDS. Scoring and data point collection depend on AR_CMGT_DATA_POINTS_B, AR_CMGT_SCORES, AR_CMGT_DNB_MAPPINGS, AR_CMGT_CF_DNB_DTLS, and AR_CMGT_BANK_REF_DATA, reflecting integration with Dun & Bradstreet credit data.

Automation and checklist processing use AR_CMGT_AUTO_RULES, AR_CMGT_AUTO_RULE_DTLS, and AR_CMGT_AUTO_RECOMMENDS for rule evaluation and recommendation generation, alongside AR_CMGT_CHECK_LISTS and AR_CMGT_CHECK_LIST_DTLS for manual verification tasks. Guarantor information is held in AR_CMGT_GUARANTOR_DATA. All access is performed as the APPS schema, so no direct grants to the underlying tables are required by callers.

Usage Notes

AR_CMGT_WF_ENGINE is not intended for direct invocation by end users. Its procedures are registered as workflow activity function calls within the Credit Management item type and are executed by the Workflow Background Engine, normally scheduled as a concurrent program. In 12.1.1 and 12.2.2, the engine may also be driven by the Credit Management HTML pages when a credit request is submitted, and by the Credit Management worklist through the standard Oracle Workflow notification framework.

Customizations should avoid modifying this package, as it is a seeded, non-shippable object and patches will overwrite changes. Extensions to credit decisioning should instead be implemented through user-defined auto rules and checklist configurations, which the package evaluates dynamically. The search term "generateauthcfg zenworks" is unrelated to this database object and refers to Novell ZENworks configuration file generation, so no EBS documentation addresses it in this context.