Search Results ins_form_res_rule

Overview

PAY_FORMULA_RESULTS is an Oracle EBS Payroll (PAY) package owned by the APPS schema and declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer. Its documented purpose is the programmatic maintenance of the two rule types that bind formulas and processing behaviour to an element type: status processing rules and formula result rules. It is therefore a configuration-time API rather than a payroll run-time calculation engine.

The package is relevant to searches such as "증발률 계산" (evaporation-rate calculation) in the sense that any statutory or company-specific calculation expressed as a payroll formula — including a rate-of-evaporation style computation — must be attached to an element before it can be evaluated during a payroll run and have its result written back to the payroll result tables. PAY_FORMULA_RESULTS provides the API surface for creating those attachments.

Key Procedures and Functions

Two entry points are documented in the metadata (ETRM 12.2.2, API classification OTHER):

• INS_STAT_PROC_RULE — Creates a status processing rule for an element. A status processing rule defines which formula is executed when an assignment's status changes in a particular way, for example on hire, termination, or a leave event. The function returns a numeric identifier for the created rule. It operates against a business group and, optionally, a legislation context, and is effective-dated.
• INS_FORM_RES_RULE — Creates a formula result rule for an element. A formula result rule determines what happens to a value produced by a formula: whether it updates a database item, is treated as an indirect result, stops a recurring element, or updates a recurring element. The header change log notes that this API was updated in version 1.1 to accept an element type identifier that may in fact be an input value identifier, precisely so that Indirect, Stop, and Update Recurring result rules can be created.

Both functions are thin configuration APIs. They validate and insert rule definitions; they do not execute the formulas themselves. No parameter lists are reproduced here, as the documented excerpt exposes only the INS_STAT_PROC_RULE signature.

Tables Accessed

The package reads and writes the following base tables through APPS synonyms:

• PAY_FORMULA_RESULT_RULES_F and PAY_FORMULA_RESULT_RULES_S — the date-tracked (F) and secure (S) rule definitions written by INS_FORM_RES_RULE.
• PAY_STATUS_PROCESSING_RULES_F and PAY_STATUS_PROCESSING_RULES_S — the rule definitions written by INS_STAT_PROC_RULE.
• PAY_INPUT_VALUES_F — read to resolve an element type or input value identifier, validating that the supplied identifier is a legal target for an indirect or update result rule.

The _F/_S pairing reflects the standard Oracle HRMS date-tracked plus secure-version table pattern, so inserts must supply effective start and end dates consistent with that model.

Usage Notes

PAY_FORMULA_RESULTS is not normally called by end users. It is invoked by Oracle Payroll setup forms — the Formula Result Rules and Status Processing Rules windows reached from the Element description — and by concurrent programs or PL/SQL setup scripts that mass-load element configuration during implementation or an upgrade. It is referenced by thirteen other packages, indicating that other Oracle Payroll APIs depend on the rule-creation logic defined here rather than re-implementing it.

For custom development, the package is the supported route when an implementation needs to programmatically attach a formula to an element, for example when generating a large number of element definitions that share a common calculation model. Because the package runs AUTHID CURRENT_USER, custom callers must hold the necessary privileges on the underlying PAY tables. Rule creation should be performed in a controlled setup environment and validated through the element definition forms before being promoted, since duplicate or overlapping effective-dated rules can cause payroll run-time errors rather than immediate insert failures.