Results for “customer_site_id”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FTE_SEL_GROUP_ASSIGNMENTS is a Transportation Execution (FTE) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It stores the association between selection groups and the individual business entities that belong to those groups. A selection group is the mechanism used to bundle entities—customers, customer sites, shipping organizations, and locations—so that they can be processed collectively during planning, carrier selection, rating, and other transportation execution activities.
The table belongs to the FTE schema and is classified as VALID in the ETRM data model. Its documented role is to provide the method by which entities such as customer, customer site, and shipping organization are assigned to one or more groups. One notable exception is documented: the shipping enterprise group is not assigned through this table, because the shipping enterprise itself is not defined as a group member in the same manner as other entity types.
The heuristic Data Vault classification mined from the foreign key structure is satellite-leaning. In modeling terms, GROUP_ASSIGNMENT_ID behaves as a unique row identifier equivalent to a satellite key, while the GROUP_ID foreign key anchors each row to its parent group. This suggests the table functions primarily as a descriptive satellite attached to FTE_SEL_GROUPS rather than as a standalone hub or a pure link between two equal-weight hubs.
Key Information Stored
The documented physical schema for 12.2.2 contains eleven columns. The most important columns are:
- GROUP_ASSIGNMENT_ID — the surrogate primary key, uniquely identifying each assignment row. It is the anchor of primary key constraint FTE_SEL_GROUP_ASSIGNMENTS_PK1.
- GROUP_ID — the foreign key to FTE_SEL_GROUPS. It identifies the selection group that the assigned entity belongs to. This is the essential business join column and the most frequently used predicate in queries against this table.
- CUSTOMER_ID — identifies a customer entity assigned to the group.
- CUSTOMER_SITE_ID — identifies a customer site (ship-to or bill-to location) assigned to the group.
- ORGANIZATION_ID — identifies the shipping organization assigned to the group.
- LOCATION_ID — the location identifier associated with the assignment, used where the assigned entity is location-based.
The remaining columns are standard EBS who-columns: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN. These support auditing and concurrent-program tracking but carry no transportation-specific business meaning.
Business-key candidates relate to the combination of GROUP_ID with one of the entity identifier columns (for example, GROUP_ID plus CUSTOMER_ID, or GROUP_ID plus ORGANIZATION_ID), depending on the entity type being assigned. The documented surrogate key remains GROUP_ASSIGNMENT_ID; the entity columns act as the semantic discriminator describing what has been assigned.
Common Use Cases and Queries
Typical reporting use cases include determining which customers or organizations belong to a given selection group, and conversely, finding all groups to which a particular customer, site, or organization has been assigned. A basic listing query:
SELECT group_assignment_id, group_id, customer_id,
customer_site_id, organization_id, location_id
FROM fte.fte_sel_group_assignments
WHERE group_id = :p_group_id;
Resolving group membership for a specific customer or organization:
SELECT g.group_id, g.group_name, a.customer_id, a.organization_id
FROM fte.fte_sel_group_assignments a,
fte.fte_sel_groups g
WHERE a.group_id = g.group_id
AND a.customer_id = :p_customer_id;
These queries support carrier assignment validation, planning group maintenance, and reconciliation of transportation setup during implementations or data migration audits.
Related Objects
The documented foreign key relationship is to FTE_SEL_GROUPS via GROUP_ID. This parent table holds the group definition (such as group name and type) and is the principal dependency for this object. Join columns for reporting are FTE_SEL_GROUP_ASSIGNMENTS.GROUP_ID to FTE_SEL_GROUPS.GROUP_ID.
Beyond this documented relationship, related objects in the FTE transportation execution model include the entity master tables referenced by CUSTOMER_ID, CUSTOMER_SITE_ID, ORGANIZATION_ID, and LOCATION_ID, together with the planning and carrier-selection components that consume selection group membership. Any process that resolves a selection group to its constituent entities reads this table as the authoritative assignment source, excluding shipping enterprise groups, which are handled outside this table per the documented description.
-
this table provides the method to assign entities such as customer, customer site, shipping organization, etc... to a group or groups. The shipping enterprise group is not assigned in this table as the shipping enterprise is not defined as
-
APPS.MRPBV_REPLENISHMENT_DSTNS·↳ HR_ORGANIZATION_INFORMATION·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_SITES_ALL·Explore MRP module →
-
Temporary sub-ledger balances for Receivables
-
View: JG_ZZ_AR_BALANCES_V 12.1.1
Sub-ledger balances for Receivables
APPS.JG_ZZ_AR_BALANCES_V·↳ JG_ZZ_AR_BALANCES·↳ JG_ZZ_AR_TMP_BAL·Explore JG module →
-
Table: MSC_PHUB_CUSTOMERS_MV 12.1.1
-
APPS.MRPBV_REPLENISHMENT_DSTNS·↳ HR_ORGANIZATION_INFORMATION·↳ HZ_CUST_ACCOUNTS·↳ HZ_CUST_ACCT_SITES_ALL·Explore MRP module →
-
This table stores the AR3 forms and the details. This is used in both AR and OM.
-
This table contains the security rules for processing data in Oracle Collaborative planning.
-
This table contains the security rules for processing data in Oracle Collaborative planning.
-
Table: MSC_DEMANDS_F_MV 12.1.1
-
This table is not used.
-
APPS.MSC_SUP_DEM_TRANSACTIONS_V·↳ FND_GLOBAL·↳ MSC_SUP_DEM_ENTRIES_UI_V·↳ MSC_X_UTIL·Explore MSC module →
-
Stores Mass Tax Changes requests with all inputs submitted
-
Table: JG_ZZ_AR_TMP_DETAIL 12.2.2
Used for calculating sub-ledger balances and holding detailed reporting data for Receivables
-
India Localization Receipts Header Table same as RCV_SHIPMENT_HEADERS
-
APPS.MRPFV_REPLENISHMENT_DSTNS·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_ORGANIZATION_INFORMATION·↳ HZ_CUST_ACCOUNTS·Explore MRP module →
-
Table: MSC_DEMANTRA_F 12.1.1
-
Table: MSC_ITEM_SUBSTITUTES 12.2.2
This table stores all the Relationships between Item Substitutes for planning.
-
Sub-ledger balances for Receivables
-
APPS.MSC_SUP_DEM_ENTRIES_VMI_V·↳ MSC_COMPANIES·↳ MSC_COMPANY_RELATIONSHIPS·↳ MSC_COMPANY_SITES·Explore MSC module →
-
APPS.MSC_SUP_DEM_UPDATE_SECURITY_V·↳ FND_GLOBAL·↳ MSC_GROUP_COMPANIES·↳ MSC_SUP_DEM_ENTRIES·Explore MSC module →
-
This table stores the AR3 forms and the details. This is used in both AR and OM.
-
Inter-company relationships
-
Table: MSC_ITEM_CUSTOMERS 12.2.2
Table to hold customer items and cross references.
-
APPS.MSC_SUP_DEM_TRANSACTIONS_V·↳ FND_GLOBAL·↳ MSC_SUP_DEM_ENTRIES_UI_V·↳ MSC_X_UTIL·Explore MSC module →
-
View: ARFV_CUSTOMER_SITES 12.2.2
APPS.ARFV_CUSTOMER_SITES·↳ FND_TERRITORIES_VL·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_GENERAL·Explore AR module →
-
MTL_TRANSACTION_FLOWS_V is a view for Intercompany transaction flows of type shipping and procuring flows.
APPS.MTL_TRANSACTION_FLOWS_V·↳ MTL_INTERCOMPANY_PARAMETERS·↳ MTL_TRANSACTION_FLOW_HEADERS·↳ MTL_TRANSACTION_FLOW_LINES·Explore INV module →
-
View: MSC_SECURITY_RULES_V 12.1.1
APPS.MSC_SECURITY_RULES_V·↳ FND_DATE·↳ FND_GLOBAL·↳ FND_USER_RESP_GROUPS·Explore MSC module →
-
View: MSC_SECURITY_RULES_V 12.2.2
APPS.MSC_SECURITY_RULES_V·↳ FND_DATE·↳ FND_GLOBAL·↳ FND_USER_RESP_GROUPS·Explore MSC module →
-
This table is not used.
-
10SC ONLY - Retrofitted
APPS.RCV_ENTER_RECEIPTS_RMA_V·↳ OE_PO_ENTER_RECEIPTS_V·↳ OE_SYS_PARAMETERS·Explore PO module →
-
View: RCV_ENTER_RECEIPTS_V 12.2.2
10SC ONLY - Retrofitted
APPS.RCV_ENTER_RECEIPTS_V·↳ HR_GENERAL·↳ HR_SECURITY·↳ OE_SYS_PARAMETERS·Explore PO module →
-
View: MSC_SUP_DEM_HZ_UI_V 12.2.2
APPS.MSC_SUP_DEM_HZ_UI_V·↳ FND_GLOBAL·↳ MSC_SUP_DEM_ENTRIES_UI_V·↳ MSC_X_UTIL·Explore MSC module →
-
- Retrofitted
APPS.RCV_SHIPMENT_HEADERS_MRC_V·↳ RCV_MC_SHIPMENT_HEADERS·↳ RCV_SHIPMENT_HEADERS·Explore PO module →
-
View: ARBV_CUSTOMER_SITES 12.1.1
APPS.ARBV_CUSTOMER_SITES·↳ HZ_CUST_SITE_USES_ALL·Explore AR module →
-
APPS.MSC_SUP_DEM_UPDATE_SECURITY_V·↳ FND_GLOBAL·↳ MSC_GROUP_COMPANIES·↳ MSC_SUP_DEM_ENTRIES·Explore MSC module →
-
View: JAI_CMN_RG_23_II_V 12.2.2
APPS.JAI_CMN_RG_23_II_V·↳ HR_ALL_ORGANIZATION_UNITS·↳ HR_LOCATIONS_ALL·↳ JAI_CMN_RG_23AC_II_TRXS·Explore JA module →
-
10SC ONLY
APPS.MTL_INTERCOMPANY_PARAMETERS_V·↳ FND_GLOBAL·↳ HR_GENERAL·↳ HR_ORGANIZATION_UNITS·Explore INV module →
-
APPS.CSF_MAP_ACCESS_HOURS_VL·↳ CSF_MAP_ACCESS_HOURS_B·↳ CSF_MAP_ACCESS_HOURS_TL·Explore CSF module →
-
This table stores threshold values for each exception type. For supplier facing exceptions, the threshold values are obtained in the following order (specific to general):company_id, company_site_id, item, supplier_id, supplier_site_idcom
-
Stores Information of RG23A/C Part II Details. Also known as Amount Register
-
Table: MSC_PHUB_CUSTOMERS_MV 12.2.2
-
Staging table to hold item customers data.
-
Staging table to hold item customers data.