Search Results returns_processing

Overview

MTL_STAT_TYPE_USAGES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered under the INV (Inventory) product module. It exposes the statistical type usage configuration maintained in the Oracle Inventory and Oracle Landed Cost / physical accounting domain. In practical terms, the view answers the question: which legal entity, economic zone, category set, and period setup is authorized to use a given statistical quantity type for a given usage context?

The view is a denormalized join rather than a base table. It flattens the raw MTL_STAT_TYPE_USAGES rows and replaces foreign-key identifiers with human-readable descriptions, such as legal entity name, zone display name, category set name, tax office location code, and user period type. This makes it directly suitable for BI Publisher reports, custom concurrent programs, and integration extracts that must present statutory inventory and physical-inventory setups without embedding multiple decode joins. It is also referenced as a supporting object during the resolution of related TCA/XLE first-party information queries; the user search for "xle_firstparty_information_v" points to exactly this dependency, since XLE_FIRSTPARTY_INFORMATION_V is one of the view's joined sources.

Underlying Base Objects

The ETRM metadata records the following referenced objects: MTL_STAT_TYPE_USAGES (synonym over the base table), XLE_FIRSTPARTY_INFORMATION_V (view), GL_PERIOD_TYPES (synonym), MTL_CATEGORY_SETS (synonym), MTL_ECONOMIC_ZONES_VL (view), HR_LOCATIONS (view), HZ_LOCATIONS (synonym), and the HR_GENERAL package.

• MTL_STAT_TYPE_USAGES is the driving table; each row carries the legal entity, zone code, stat type, usage type, period settings, conversion options, tax office, and rule-set attributes.
• XLE_FIRSTPARTY_INFORMATION_V supplies the legal entity NAME via the join on LEGAL_ENTITY_ID.
• GL_PERIOD_TYPES provides USER_PERIOD_TYPE for the configured accounting period type.
• MTL_CATEGORY_SETS supplies CATEGORY_SET_NAME.
• MTL_ECONOMIC_ZONES_VL supplies ZONE_DISPLAY_NAME from the zone code.
• HR_LOCATIONS supplies the tax office LOCATION_CODE through the location ID.

The view definition is a UNION of two near-identical SELECT lists, typically separating rows where the tax office location is populated from those where it is null, so that the inner join to HR_LOCATIONS does not drop unassigned tax offices.

Key Columns

• LEGAL_ENTITY_ID / NAME — the first-party legal entity and its resolved name from XLE_FIRSTPARTY_INFORMATION_V.
• ZONE_CODE / ZONE_DISPLAY_NAME — the economic zone and its display label.
• STAT_TYPE — the statistical quantity type being configured.
• USAGE_TYPE — the context in which the stat type is consumed (for example physical inventory or cycle count usage).
• PERIOD_SET_NAME / PERIOD_TYPE / USER_PERIOD_TYPE — the accounting calendar and period granularity.
• START_PERIOD_NAME / END_PERIOD_NAME — the effective period range for the usage.
• CATEGORY_SET_ID / CATEGORY_SET_NAME — the item category set scoping the usage.
• TAX_OFFICE_CODE, TAX_OFFICE_NAME, TAX_OFFICE_LOCATION_ID, TAX_OFFICE_LOCATION_CODE — tax office identification and its HR location code.
• WEIGHT_UOM_CODE, WEIGHT_PRECISION, REPORTING_ROUNDING — weight and rounding controls.
• CONVERSION_TYPE, CONVERSION_OPTION, TRIANGULATION_MODE — currency and unit conversion behavior.
• ATTRIBUTE_RULE_SET_CODE, ALT_UOM_RULE_SET_CODE, REFERENCE_PERIOD_RULE — rule-set and valuation rule identifiers.
• PENDING_INVOICE_DAYS, PRIOR_INVOICE_DAYS, RETURNS_PROCESSING, KIT_METHOD, INCLUDE_ESTABLISHMENTS — operational accounting flags.

Common Use Cases and Queries

Typical uses include auditing which legal entities have statistical type usages configured, exporting calendar and category-set mappings for reconciliation, and validating tax office assignments before period close.

List all usages for a legal entity:

SELECT legal_entity_id, name, zone_code, zone_display_name, stat_type, usage_type
FROM apps.mtl_stat_type_usages_v
WHERE legal_entity_id = :p_legal_entity_id
ORDER BY stat_type, usage_type;

Find usages missing a tax office location:

SELECT legal_entity_id, name, stat_type, usage_type
FROM apps.mtl_stat_type_usages_v
WHERE tax_office_location_id IS NULL;

Because the view is not partitioned and performs multiple joins with a UNION, restrict queries with indexed predicates such as LEGAL_ENTITY_ID or ZONE_CODE, and avoid unfiltered full scans on large production instances.