Results for “ship_to_flag”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The WSHFV_PICK_LINE_GROUPING_RULE view is a reporting and integration object in the Oracle E-Business Suite Order Entry (OE) module. In the ETRM 12.2.2 metadata it is documented as a retrofitted view owned by the APPS schema. Its purpose is to expose the pick-slip line grouping rules that control how pick slip lines are consolidated when Oracle Warehouse Management or Order Management generates picking documents. Each row in the view represents a single named pick-slip rule, identified by the PICK_SLIP_RULE_ID, together with the flags that determine the grouping criteria applied to that rule.
Because the object is a view rather than a base table, it does not store data itself. It provides a stable, read-oriented interface over the underlying configuration table, allowing reports, concurrent programs, and external integrations to query grouping rules without directly referencing the base table. This is significant for customers upgrading from earlier releases, since the "Retrofitted" description indicates the view was created to preserve backward compatibility for code and reports that previously relied on the older naming conventions.
Underlying Base Objects
The view is defined over a single documented base object: WSH_PICK_SLIP_RULES, accessed through a synonym. No joins to other tables are present in the documented view text. The defining query selects a subset of columns from WSH_PICK_SLIP_RULES and applies column aliases to expose the grouping flags under names that include the GROUP_BY_ prefix. For example, ORDER_NUMBER_FLAG is exposed as GROUP_BY_ORDER_NUMBER_FLAG, and SUBINVENTORY_FLAG becomes GROUP_BY_SUBINVENTORY_FLAG. This aliasing makes the semantic intent of each flag explicit to consuming applications.
The view also carries the standard Oracle EBS "who" columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the concurrent program audit columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID). These are inherited directly from the base table and support auditing and traceability of rule configuration changes.
Key Columns
The most important identifier column is PICK_SLIP_RULE_ID, the primary key of the underlying rule. This is the column most commonly searched for, as it links a rule definition to pick slip documents and to the warehouse configuration that references it. Other notable columns include:
NAMEandDESCRIPTION— the user-defined rule name and its descriptive text.GROUP_BY_ORDER_NUMBER_FLAG— indicates whether pick lines are grouped by order number.GROUP_BY_SUBINVENTORY_FLAG— indicates whether grouping considers the subinventory.GROUP_BY_CUSTOMER_FLAG— indicates grouping by customer.SHIP_TO_FLAG— controls grouping by ship-to location.GROUP_BY_CARRIER_FLAG,GROUP_BY_SHIP_PRIORITY_FLAG,GROUP_DEPARTURE_FLAG, andGROUP_BY_DELIVERY_FLAG— additional grouping dimensions covering carrier, shipment priority, departure, and delivery.START_DATE_ACTIVEandEND_DATE_ACTIVE— the effective date range during which the rule is active.
Common Use Cases and Queries
Typical uses include validating which grouping flags are enabled for a given rule, generating configuration reports, and troubleshooting pick slip consolidation behavior. The following query retrieves the grouping configuration for a specific rule:
SELECT pick_slip_rule_id, name, description, group_by_order_number_flag, group_by_subinventory_flag, start_date_active, end_date_active FROM wshfv_pick_line_grouping_rule WHERE pick_slip_rule_id = :rule_id;
A second common pattern lists all currently active rules:
SELECT pick_slip_rule_id, name, group_by_customer_flag, group_by_carrier_flag FROM wshfv_pick_line_grouping_rule WHERE TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));
These queries are frequently embedded in custom reports and data-extraction routines that audit warehouse picking configuration across operating units and organizations.
-
- Retrofitted
APPS.WSHFV_PICK_LINE_GROUPING_RULE·↳ WSH_PICK_SLIP_RULES·Explore OE module →
-
View: ASO_PVT_ACCT_RELATE_V 12.2.2
APPS.ASO_PVT_ACCT_RELATE_V·↳ HZ_CUST_ACCT_RELATE·Explore ASO module →
-
View: OKX_CUST_ACCT_RELATE_V 12.2.2
APPS.OKX_CUST_ACCT_RELATE_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE_ALL·Explore OKX module →
-
View: OE_RA_ADDRESSES_V 12.2.2
This view is used for validation of addresses.
APPS.OE_RA_ADDRESSES_V·↳ HZ_CUST_ACCT_SITES·Explore ONT module →
-
View: OE_RA_ADDRESSES_V 12.1.1
This view is used for validation of addresses.
APPS.OE_RA_ADDRESSES_V·↳ HZ_CUST_ACCT_SITES·Explore ONT module →
-
View: ASO_PVT_ACCT_RELATE_V 12.1.1
APPS.ASO_PVT_ACCT_RELATE_V·↳ HZ_CUST_ACCT_RELATE·Explore ASO module →
-
Table: CZ_IMP_ADDRESS 12.1.1
Data to be imported (or rejected) into CZ_ADDRESSES
-
Pick Release Grouping Rules
-
- Retrofitted
APPS.WSHBV_PICK_LINE_GROUPING_RULE·↳ WSH_PICK_SLIP_RULES·Explore OE module →
-
View: OKX_CUST_ACCT_RELATE_V 12.1.1
APPS.OKX_CUST_ACCT_RELATE_V·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE_ALL·Explore OKX module →
-
OBSOLETE, MDApp only
-
Location information populated by loader
-
Location information populated by loader
-
Relationships between customer accounts
-
This table is used to store the deleted records for HZ_CUST_ACCT_RELATE_ALL during account merge
-
The HZ_CUST_ACCT_SITES_ALL_M table stores the information of customer profile amounts from HZ_CUST_ACCT_SITES_ALL table before the account merge happens. The primary key for this table is CUST_ACCT_SITE_ID , CUSTOMER_MERGE_HEADER_ID.
-
Stores all customer account sites across all operating units
-
View: AST_CUST_ACCT_SITES_V 12.1.1
APPS.AST_CUST_ACCT_SITES_V·↳ AR_LOOKUPS·↳ FND_TERRITORIES_TL·↳ HZ_CUST_ACCT_SITES·Explore AST module →
-
View: AST_CUST_ACCT_SITES_V 12.2.2
APPS.AST_CUST_ACCT_SITES_V·↳ AR_LOOKUPS·↳ FND_TERRITORIES_TL·↳ HZ_CUST_ACCT_SITES·Explore AST module →
-
View: CSC_CUST_ACCT_SITES_V 12.2.2
APPS.CSC_CUST_ACCT_SITES_V·↳ FND_TERRITORIES_VL·↳ HR_OPERATING_UNITS·↳ HZ_CUST_ACCT_SITES·Explore CSC module →
-
Relationships between customer accounts
-
Pick slip rules
-
Customer address information
-
CSC_ACCT_RELATIONSHIP_V retrieves related accounts for a customer account.
APPS.CSC_ACCT_RELATIONSHIP_V·↳ AR_LOOKUPS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE·Explore CSC module →
-
CSC_ACCT_RELATIONSHIP_V retrieves related accounts for a customer account.
APPS.CSC_ACCT_RELATIONSHIP_V·↳ AR_LOOKUPS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE·Explore CSC module →
-
View: JTF_CUST_ACCT_SITES_V 12.1.1
JTF_CUST_ACCT_SITES retrieves information about customer sites. One customer account can have multiple sites.
APPS.JTF_CUST_ACCT_SITES_V·↳ HZ_CUST_ACCT_SITES_ALL·Explore JTF module →
-
- Retrofitted
APPS.WSHBV_PICK_LINE_GROUPING_RULE·↳ WSH_PICK_SLIP_RULES·Explore OE module →
-
- Retrofitted
APPS.WSHFV_PICK_LINE_GROUPING_RULE·↳ WSH_PICK_SLIP_RULES·Explore OE module →
-
Table: CZ_IMP_ADDRESS 12.2.2
Data to be imported (or rejected) into CZ_ADDRESSES
-
View: CS_INCIDENTS_DIARY_V 12.2.2
This view is not used anymore. This has been obsoleted. Starting 11.5.6 this view will not be supported and will remain just for backward compatability. The view CS_INCIDENTS_LOG_V has some of the functionality from this view but is not a c
APPS.CS_INCIDENTS_DIARY_V·↳ CSICUMPI_PUB·↳ CS_CUSTOMER_PRODUCTS_ALL·↳ CS_INCIDENTS_ALL_B·Explore CS module →
-
OBSOLETE, MDApp only
-
View: JTF_CUST_ACCT_SITES_V 12.2.2
JTF_CUST_ACCT_SITES retrieves information about customer sites. One customer account can have multiple sites.
APPS.JTF_CUST_ACCT_SITES_V·↳ HZ_CUST_ACCT_SITES_ALL·Explore JTF module →
-
This table is used to store the deleted records for HZ_CUST_ACCT_RELATE_ALL during account merge
-
View: CS_INCIDENTS_DIARY_V 12.1.1
This view is not used anymore. This has been obsoleted. Starting 11.5.6 this view will not be supported and will remain just for backward compatability. The view CS_INCIDENTS_LOG_V has some of the functionality from this view but is not a c
APPS.CS_INCIDENTS_DIARY_V·↳ CSICUMPI_PUB·↳ CS_CUSTOMER_PRODUCTS_ALL·↳ CS_INCIDENTS_ALL_B·Explore CS module →
-
Stores all customer account sites across all operating units
-
View: CSC_CUST_ACCT_SITES_V 12.1.1
APPS.CSC_CUST_ACCT_SITES_V·↳ FND_TERRITORIES_VL·↳ HR_OPERATING_UNITS·↳ HZ_CUST_ACCT_SITES·Explore CSC module →
-
Pick slip rules
-
(Release 11.5 Only)
APPS.AR_CUSTOMER_RELATIONSHIPS_V·↳ AR_LOOKUPS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE·Explore AR module →
-
(Release 11.5 Only)
APPS.AR_CUSTOMER_RELATIONSHIPS_V·↳ AR_LOOKUPS·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_RELATE·Explore AR module →
-
Customer address information
-
Pick Release Grouping Rules
-
The HZ_CUST_ACCT_SITES_ALL_M table stores the information of customer profile amounts from HZ_CUST_ACCT_SITES_ALL table before the account merge happens. The primary key for this table is CUST_ACCT_SITE_ID , CUSTOMER_MERGE_HEADER_ID.
-
View: XNC_PVT_ACCT_RELATE_V 12.1.1
This View retrieves the Related Customer Accounts for a given Customer Account and also specifies the Relationship type (Contact of, Employee of , etc)
Not implemented in this database·Explore XNC module →
-
View: XNC_PVT_ACCT_RELATE_V 12.2.2
This View retrieves the Related Customer Accounts for a given Customer Account and also specifies the Relationship type (Contact of, Employee of , etc)
Not implemented in this database·Explore XNC module →
-
VIEW: CZ.CZ_IMP_ADDRESS# 12.2.2
-
Information about customer relationships
Not implemented in this database·Explore AR module →