Results for “location_code”
4 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AP_SHIP_BILL_TO_LOCATIONS_V is a seeded Oracle E-Business Suite view owned by the APPS schema and classified under the Payables (AP) product family. It presents a consolidated list of ship-to and bill-to locations that are valid for use in Payables transactions at the time of query. The view joins the transactional location table with its translated counterpart to expose a language-specific location code and description alongside the location identifiers and site-type flags that Payables and related modules rely on.
Functionally, the view acts as a lookup and validation source rather than a transactional store. It is commonly referenced by reports, integrations, and concurrent programs that need to resolve a LOCATION_ID into a user-friendly location code and description, or that need to confirm whether a given location is enabled as a ship-to site, a bill-to site, or both. Because the view filters out locations whose INACTIVE_DATE has already passed, consumers are guaranteed to see only currently active locations.
Underlying Base Objects
The documented base objects referenced by the view are HR_LOCATIONS_ALL (synonym), HR_LOCATIONS_ALL_TL (synonym), and the HR_GENERAL package. The primary data source is HR_LOCATIONS_ALL, aliased LOC, which supplies the location identifier, business group, ship-to and bill-to flags, inventory organization reference, and the inactive date used for filtering. The translated table HR_LOCATIONS_ALL_TL, aliased LOT, supplies the LOCATION_CODE and DESCRIPTION values in the user's current language.
The two tables are joined on LOC.LOCATION_ID = LOT.LOCATION_ID, and the translated row is restricted to LOT.LANGUAGE = USERENV('LANG'), ensuring each location appears once in the session language. The HR_GENERAL package is invoked through HR_GENERAL.GET_BUSINESS_GROUP_ID to enforce the current business group context, with a fallback of -99 when no business group is resolvable. The INACTIVE_DATE filter uses SYSDATE so that locations retained historically in the base table but no longer effective are excluded.
Key Columns
LOCATION_ID— The primary surrogate key for the location, used throughout EBS as the foreign key value stored on addresses and site records.LOCATION_CODE— The translated, user-facing short name for the location, sourced fromHR_LOCATIONS_ALL_TL.DESCRIPTION— The translated long description of the location, also from the translated table.SHIP_TO_SITE_FLAG— Indicates whether the location is enabled for use as a ship-to site. This is the column users search for under the term ship_to_site_flag. It governs whether the location can be selected as a receiving or delivery destination.BILL_TO_SITE_FLAG— Indicates whether the location is enabled for use as a bill-to site, controlling its availability as an invoicing address.INVENTORY_ORGANIZATION_ID— Optionally associates the location with a specific inventory organization, relevant where shipping and receiving activity is organization-scoped.
Common Use Cases and Queries
The view is most frequently used to present validated, active location lists in Payables and procurement contexts, and to confirm site flag status before allowing a location to be defaulted onto a transaction.
SELECT location_id, location_code, description,
ship_to_site_flag, bill_to_site_flag
FROM apps.ap_ship_bill_to_locations_v
WHERE ship_to_site_flag = 'Y';
A typical bill-to validation follows the same pattern, substituting BILL_TO_SITE_FLAG. To resolve a single location from a stored identifier:
SELECT location_code, description
FROM apps.ap_ship_bill_to_locations_v
WHERE location_id = :p_location_id;
Because the view already applies the inactive-date and language filters, integrations that consume it avoid duplicating that logic. One caveat: the view does not expose the full address block, so address-level reporting must join back to HR_LOCATIONS_ALL. All results remain scoped to the session business group and language, which should be accounted for in multi-organization reporting.
-
APPS.AP_SHIP_BILL_TO_LOCATIONS_V·↳ HR_GENERAL·↳ HR_LOCATIONS_ALL·↳ HR_LOCATIONS_ALL_TL·Explore AP module →
-
No Longer Used - MOAC
APPS.AP_SHIPPING_NETWORK_LOCATIONS·↳ HR_GENERAL·↳ HR_LOCATIONS_ALL·↳ HR_LOCATIONS_ALL_TL·Explore AP module →
-
APPS.AP_SHIP_BILL_TO_LOCATIONS_V·↳ HR_GENERAL·↳ HR_LOCATIONS_ALL·↳ HR_LOCATIONS_ALL_TL·Explore AP module →
-
No Longer Used - MOAC
APPS.AP_SHIPPING_NETWORK_LOCATIONS·↳ HR_GENERAL·↳ HR_LOCATIONS_ALL·↳ HR_LOCATIONS_ALL_TL·Explore AP module →