Search Results get_period_date
Overview
GMICCAL is a PL/SQL package body owned by APPS that provides the core inventory calendar validation and period-balance maintenance logic for Oracle Process Manufacturing (OPM) within Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal purpose is to determine whether a given transaction date falls within a valid, open inventory calendar period for a specific organization and warehouse, and to maintain period-level inventory balances such as usage and yield figures. The package is classified as OTHER in the ETRM repository and is referenced by ten other packages, indicating its role as a foundational utility invoked broadly across OPM transaction processing and inventory control flows.
A user searching for "get_period_date" is typically seeking the routine that returns the calendar period associated with a transaction date. GMICCAL fulfills this requirement indirectly through TRANS_DATE_VALIDATE, which resolves the fiscal year, period, and period end date for a given organization and warehouse before validating the date against the inventory calendar.
Key Procedures and Functions
- TRANS_DATE_VALIDATE — Validates that a supplied transaction date falls within a valid inventory calendar period for a given organization code and warehouse code. It returns a numeric status code: 0 for success, and defined negative values for specific failures including missing warehouse code (-28), missing organization code (-27), missing transaction date (-26), closed warehouse period (-25), company code not found (-24), date in a closed calendar period (-23), period end date/close indicator not found (-22), fiscal year/begining date not found (-21), and warehouse code not found (-29). The header history notes that the organization code passed in should be that of the organization owning the warehouse, not necessarily the document organization code, reflecting Bug 1579270.
- DELETE_IC_PERD_BAL — Removes period balance records from the inventory period balance table.
- INSERT_IC_PERD_BAL — Inserts period balance records, likely drawing sequence values from GMI_PERD_BAL_ID_S.
- CALC_USAGE_YIELD — Computes usage and yield metrics for inventory period balances.
- WHSE_STATUS_UPDATE — Updates warehouse status, interacting with IC_WHSE_STS.
- PERIOD_STATUS_UPDATE — Updates the open/close status of an inventory calendar period.
- DETERMINE_COMPANY — Resolves the company code associated with a given organization, supporting the fiscal year and period determination logic referenced in TRANS_DATE_VALIDATE.
Tables Accessed
The package reads and writes the following tables through APPS synonyms:
- IC_CLDR_HDR / IC_CLDR_DTL — Inventory calendar header and detail; source of fiscal year, period, and period close indicator data.
- IC_WHSE_MST / IC_WHSE_STS — Warehouse master and status; warehouse validity and closed-period determination.
- IC_PERD_BAL / GMI_PERD_BAL_ID_S — Inventory period balance and its sequence; target of insert and delete operations.
- IC_ITEM_MST, IC_LOCT_MST, IC_LOCT_INV, IC_LOTS_MST, IC_TRAN_PND, IC_TRAN_CMP — Item, location, lot, and transaction staging/completion tables supporting balance and usage/yield calculations.
- SY_ORGN_MST, SY_REAS_CDS — Organization master and reason codes, supporting company and status determination.
Usage Notes
GMICCAL is invoked wherever OPM inventory transactions require calendar validation, including inventory transaction entry forms, inventory period close concurrent programs, and period balance recalculation processes. Because it is referenced by ten other packages, custom extensions and integrations that post OPM inventory movements should call TRANS_DATE_VALIDATE rather than re-implementing calendar checks, and must honor its return codes by rejecting or holding transactions when a negative value is returned. The package assumes the calling context supplies an organization code matching the warehouse owner, per the documented defect history. Developers searching for "get_period_date" functionality should note that GMICCAL does not expose a procedure by that exact name; the equivalent capability resides in the period-resolution logic inside TRANS_DATE_VALIDATE and DETERMINE_COMPANY.
-
PACKAGE BODY: APPS.GMICCAL
12.2.2
-
PACKAGE BODY: APPS.GMICCAL
12.1.1
-
PACKAGE: APPS.JGRX_FAREG
12.1.1
-
PACKAGE: APPS.JGRX_FAREG
12.2.2
-
PACKAGE: APPS.JG_RX_FAREG
12.1.1
-
PACKAGE: APPS.JG_RX_FAREG
12.2.2
-
PACKAGE: APPS.PA_RESOURCE_UTILS
12.1.1
-
PACKAGE BODY: APPS.JGRX_FAREG
12.2.2
-
PACKAGE: APPS.PA_RESOURCE_UTILS
12.2.2
-
PACKAGE BODY: APPS.JGRX_FAREG
12.1.1
-
PACKAGE BODY: APPS.JG_RX_FAREG
12.2.2
-
PACKAGE BODY: APPS.JG_RX_FAREG
12.1.1
-
APPS.PA_RESOURCE_UTILS dependencies on PER_ORG_STRUCTURE_ELEMENTS
12.2.2
-
APPS.JG_RX_FAREG dependencies on FND_GLOBAL
12.1.1
-
APPS.JGRX_FAREG dependencies on FND_GLOBAL
12.2.2
-
APPS.JG_RX_FAREG dependencies on FND_GLOBAL
12.2.2
-
APPS.JGRX_FAREG dependencies on FND_GLOBAL
12.1.1
-
APPS.PA_RESOURCE_UTILS dependencies on PER_ORG_STRUCTURE_ELEMENTS
12.1.1
-
APPS.PA_RESOURCE_UTILS dependencies on PA_EMPLOYEES
12.2.2
-
APPS.PA_RESOURCE_UTILS dependencies on PA_EMPLOYEES
12.1.1
-
APPS.GMICCAL dependencies on IC_CLDR_DTL
12.2.2
-
APPS.GMICCAL dependencies on IC_CLDR_DTL
12.1.1
-
PACKAGE BODY: APPS.PA_RESOURCE_UTILS
12.1.1
-
PACKAGE BODY: APPS.PA_RESOURCE_UTILS
12.2.2
-
APPS.JGRX_FAREG dependencies on FA_RX_UTIL_PKG
12.1.1
-
APPS.JGRX_FAREG dependencies on FA_RX_UTIL_PKG
12.2.2
-
APPS.JG_RX_FAREG dependencies on FA_RX_UTIL_PKG
12.2.2
-
APPS.JG_RX_FAREG dependencies on FA_RX_UTIL_PKG
12.1.1
-
APPS.JGRX_FAREG dependencies on JGRX_FAREG
12.1.1
-
APPS.JGRX_FAREG dependencies on JGRX_FAREG
12.2.2
-
APPS.JG_RX_FAREG dependencies on JG_RX_FAREG
12.1.1
-
APPS.JG_RX_FAREG dependencies on JG_RX_FAREG
12.2.2