Search Results g_lookup_type
Overview
APPS.PER_FI_POSTALCODE_UPLOAD is an Oracle E-Business Suite 12.1.1 / 12.2.2 package body that performs a bulk data load of Finnish postal code reference data into the EBS localization lookup model. The package name prefix "PER_FI" indicates it belongs to the Human Resources (PER) localization layer for Finland. Its business purpose is to allow structured postal code records to be read from a flat file staged on the database server, validated, and then inserted or updated as lookup values alongside the corresponding localization lookup type. Rather than requiring end users to enter each postal code manually through a form, administrators can supply a delimited file and let the package persist the records in a controlled, batch-oriented manner.
Key Procedures and Functions
The package exposes five documented procedures. Their naming and the surrounding declarations reveal the intended processing model:
- READ_FILE — Entry point that opens the file named by the caller from the configured database directory, stores the supplied business group as the package-level g_bg_id, and drives the remaining processing. The header constants c_read_file ('r'), c_max_linesize (400), and c_commit_point (10) show that it opens the file in read mode, constrains line length, and commits in batches of ten records.
- READ_RECORD — Parses each line returned by READ_FILE into individual field values. It is the component responsible for detecting malformed or empty input, which the package tracks through the locally declared exceptions e_invalid_record and e_empty_line.
- IS_NUMBER — A validation helper that tests whether a supplied character value represents a valid numeric literal. This is used to confirm that postal code values, and any numeric qualifiers in the source file, are well formed before they are written to the lookup tables.
- INSERT_ROW — Creates a new lookup value row for a postal code that does not yet exist in FND_LOOKUP_VALUES.
- UPDATE_ROW — Modifies an existing lookup value when a postal code already present in the destination is encountered again, allowing corrections or descriptive changes to be applied.
Tables Accessed
The package references three objects through APPS synonyms:
- FND_LOOKUP_TYPES — Read to resolve the lookup type and its owning view application. The package-level variable g_view_application_id is declared against FND_LOOKUP_TYPES.view_application_id, and g_lookup_type is the constant 'FI_POSTAL_CODE'. Notably, the localized name of the lookup type is restricted to 50 characters (VARCHAR2(50)), which is the identifier that ties each uploaded postal code record to the correct lookup category.
- FND_LOOKUP_VALUES — The primary destination table. INSERT_ROW and UPDATE_ROW write postal code values, meanings, and descriptions into this table under the FI_POSTAL_CODE lookup type.
- UTL_FILE — The Oracle-supplied PL/SQL file I/O package, used to read the staged flat file from the directory designated by the constant c_data_exchange_dir ('PER_DATA_EXCHANGE_DIR').
Usage Notes
The package is an OTHER-classified API rather than a published HRMS business API, and the ETRM record states it is referenced by zero other packages, confirming it is intended for direct invocation rather than being called from the delivered application code. In practice it is driven by a concurrent program registered against the PER_DATA_EXCHANGE_DIR directory, with the file name and business group passed as parameters and errbuf/retcode returned through the standard concurrent manager interface. The commit point of ten records and the warning/error severity constants (c_warning = 1, c_error = 2) indicate the loader is designed to report partial progress rather than abort on the first bad line. Because the mechanism populates FND_LOOKUP_VALUES directly, the loader can be used as a data conversion or initial setup utility when implementing Finnish localization, but lookups loaded in this way must respect the same lookup type context as records maintained through the standard lookup maintenance forms.
-
APPS.PER_FI_POSTALCODE_UPLOAD SQL Statements
12.2.2
-
APPS.PER_SE_POSTALCODE_UPLOAD SQL Statements
12.1.1
-
APPS.PER_FI_POSTALCODE_UPLOAD SQL Statements
12.1.1
-
APPS.PER_SE_POSTALCODE_UPLOAD SQL Statements
12.2.2
-
PACKAGE BODY: APPS.PER_FI_POSTALCODE_UPLOAD
12.1.1
-
PACKAGE BODY: APPS.PER_SE_POSTALCODE_UPLOAD
12.1.1
-
PACKAGE BODY: APPS.PER_SE_POSTALCODE_UPLOAD
12.2.2
-
PACKAGE BODY: APPS.PER_FI_POSTALCODE_UPLOAD
12.2.2
-
PACKAGE: APPS.QP_PTE_UTIL
12.2.2
-
PACKAGE: APPS.QP_PTE_UTIL
12.1.1
-
PACKAGE: APPS.OKL_OVD_PVT
12.2.2
-
APPS.IGS_FI_PRC_DISC_SUA SQL Statements
12.1.1
-
PACKAGE: APPS.OKL_OVD_PVT
12.1.1
-
PACKAGE: APPS.OKL_OPT_RUL_TMP_PVT
12.2.2
-
PACKAGE: APPS.OKL_OPT_RUL_TMP_PVT
12.1.1
-
PACKAGE BODY: APPS.IGS_FI_PRC_DISC_SUA
12.1.1
-
PACKAGE BODY: APPS.QP_PTE_UTIL
12.2.2
-
PACKAGE BODY: APPS.QP_PTE_UTIL
12.1.1
-
APPS.PER_SE_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES_PKG
12.1.1
-
APPS.PER_FI_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES
12.1.1
-
APPS.PER_FI_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES_PKG
12.2.2
-
APPS.PER_SE_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES
12.2.2
-
APPS.PER_FI_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES
12.2.2
-
APPS.PER_SE_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES
12.1.1
-
APPS.PER_SE_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES_PKG
12.2.2
-
APPS.PER_FI_POSTALCODE_UPLOAD dependencies on FND_LOOKUP_VALUES_PKG
12.1.1
-
APPS.IGS_FI_PRC_DISC_SUA dependencies on IGS_FI_GEN_GL
12.1.1
-
APPS.OKL_OVD_PVT dependencies on OKL_ACCOUNTING_UTIL
12.2.2
-
APPS.OKL_OVD_PVT dependencies on OKL_ACCOUNTING_UTIL
12.1.1
-
APPS.IGS_FI_PRC_DISC_SUA dependencies on IGS_LOOKUP_VALUES
12.1.1
-
APPS.IGS_FI_PRC_DISC_SUA dependencies on STANDARD
12.1.1
-
APPS.QP_PTE_UTIL dependencies on QP_PTE_UTIL
12.1.1
-
APPS.IGS_FI_PRC_DISC_SUA dependencies on FND_FILE
12.1.1
-
APPS.QP_PTE_UTIL dependencies on QP_PTE_UTIL
12.2.2
-
PACKAGE BODY: APPS.OKL_OVD_PVT
12.2.2
-
PACKAGE BODY: APPS.OKL_OVD_PVT
12.1.1
-
APPS.OKL_OVD_PVT dependencies on OKC_API
12.2.2
-
APPS.OKL_OVD_PVT dependencies on OKC_API
12.1.1
-
APPS.OKL_OVD_PVT dependencies on OKC_API
12.1.1
-
APPS.OKL_OVD_PVT dependencies on OKC_API
12.2.2
-
APPS.OKL_OPT_RUL_TMP_PVT dependencies on OKC_API
12.1.1
-
APPS.OKL_OPT_RUL_TMP_PVT dependencies on OKC_API
12.2.2