Search Results save_results

Overview

FTE_SEL_GROUPS_PKG is an APPS-owned PL/SQL package in Oracle E-Business Suite Release 12.1.1 and 12.2.2 that supports the Freight and Transportation Execution (FTE) module's selection group functionality. Selection groups are named collections of selection rules and attributes that determine how shipping results are evaluated and generated for outbound shipments. The package provides the validation, copy, assignment, and result-lifecycle logic used when users define, maintain, or reassign selection groups through the FTE user interface or through processing programs.

The package is classified as OTHER within the ETRM metadata, indicating that it is a supplemental backend package rather than a formally published public API. It is not referenced by any other package, so its procedures are invoked directly by FTE forms or by concurrent processing rather than through a layered call stack of dependent PL/SQL objects.

Key Procedures and Functions

• VALIDATE_GROUP — Confirms that a selection group name is unique and that its start and end dates do not overlap with other assigned groups for each assignee. It supports CREATE, COPY, and UPDATE modes, validating one assignee for create/copy operations and one or more assignees for update operations.
• COPY_GROUP — Creates a new selection group by duplicating all entities composing the source group except data residing in FTE_SEL_RESULTS, so that rule and attribute definitions are carried forward without copying prior execution output.
• VALIDATE_SHIPMETHOD — Verifies that a given carrier and service level combination represents a valid ship method before the group definition is committed.
• VALIDATE_ASSIGNMENT — Checks whether a selection group can legitimately be assigned to a specified assignee (by name, type, and identifier), returning the resolved group identifier when validation succeeds.
• DELETE_RESULTS — Removes rows from FTE_SEL_RESULTS for a given selection group during UPDATE operations, clearing previously generated results so that the group can be re-evaluated cleanly.
• SAVE_RESULTS — Persists selection result data for the group, populating the result and result-attribute tables that drive shipment selection output.
• IS_VALID_REGION — Determines whether a supplied region value is valid for use within selection group processing.

Tables Accessed

The package operates across three logical table families. The group definition family comprises FTE_SEL_GROUPS and FTE_SEL_GROUPS_S, together with FTE_SEL_GROUP_ASSIGNMENTS, FTE_SEL_GROUP_ATTRIBUTES, and FTE_SEL_GROUP_ATTRIBUTES_S; these store the group header, its assignees, and the attributes that scope the selection logic. The rules family includes FTE_SEL_RULES, FTE_SEL_RULES_S, FTE_SEL_RULE_RESTRICTIONS, and FTE_SEL_RULE_RESTRICTIONS_S, which capture the rules and their restrictions that a group applies. The results family includes FTE_SEL_RESULTS, FTE_SEL_RESULTS_S, FTE_SEL_RESULT_ASSIGNMENTS, FTE_SEL_RESULT_ASSIGNMENTS_S, FTE_SEL_RESULT_ATTRIBUTES, and FTE_SEL_RESULT_ATTRIBUTES_S. DELETE_RESULTS targets only FTE_SEL_RESULTS, while COPY_GROUP deliberately excludes that table to avoid duplicating execution output. All tables are accessed through APPS synonyms, and the _S tables hold the translated or setup-level shadow rows associated with their base counterparts.

Usage Notes

FTE_SEL_GROUPS_PKG is typically invoked from the FTE selection group maintenance forms when a user creates, copies, updates, or assigns a selection group, and from batch or concurrent processing that regenerates selection results. The DELETE_RESULTS procedure is of particular interest to developers investigating how stale selection results are purged before an UPDATE re-evaluates a group, since it is the documented entry point for clearing FTE_SEL_RESULTS. Because the package is classified as OTHER and is referenced by no other package, custom code should call its procedures cautiously: parameter signatures are not published as a supported API, and the package header in the ETRM documentation shows no version continuity guarantee across point releases. Integrators should validate behavior in the target release, confirm that x_return_status values are checked after each call, and prefer supported FTE APIs or concurrent programs where they exist rather than invoking this package directly.