Search Results get_qualifier

Overview

APPS.PAY_GB_P6EDI_PKG is a United Kingdom localization package within Oracle E-Business Suite Payroll. Its principal business function is the ingestion of P6 electronic data interchange (EDI) submissions from HM Revenue & Customs (HMRC), supplied to the employer as flat files. The package parses these inbound P6 files and loads the extracted tax code and related payroll information into the PAY_GB_TAX_CODE_INTERFACE staging table, from which the standard tax code update process can validate and apply the changes to employee assignments. The header comment identifies the source file as pygbp6ei.pkh, with a version dated 2007, reflecting the long-standing nature of the GB statutory filing interface. The package is classified as OTHER in the ETRM repository and is owned by APPS.

Key Procedures and Functions

The package exposes seven documented program units:

• UPLOAD_P6 — The main entry point and concurrent-program driver. It reads the P6 flat file and loads its contents into the tax code interface table. It returns the standard concurrent request OUT parameters (errbuf, retcode) and accepts a request identifier, filename, processing mode, effective date, business group, and a validate-only flag that permits a dry run without committing data.
• GET_QUALIFIER — A parsing function that extracts the qualifier token from a given input line of the P6 file, allowing the upload routine to determine the record type encountered.
• GET_NAME — A parsing function that returns the name element from a supplied line, used principally for employee name components carried within the P6 message.
• PROCESS_ATT — The function that the user searched for. It processes an individual attribute value within the P6 record, taking the raw line and its qualifier and returning the resolved attribute string. It isolates the field-level extraction logic that feeds the subsequent write to the interface table.
• PROCESS_DATE — A conversion function that renders date values from the P6 file into the canonical format expected by the interface table, such as effective and issue dates.
• PROCESS_TAX — A conversion function that interprets tax code content according to a supplied process type, normalising the various tax code representations found in P6 data.
• WRITE_TO_DATABASE — The insert routine that accepts the fully parsed P6 record fields — message date, form type, district number, employer reference, NI number, works number, previous employment pay and tax totals, tax code, week1/month1 indicator, employee name, effective date, issue date, and request ID — and persists them to the interface table. UPLOAD_P6 invokes it once per parsed record.

Tables Accessed

The package writes to PAY_GB_TAX_CODE_INTERFACE, the GB localization interface table that stages inbound tax code changes prior to validation and application. The ETRM metadata additionally lists UTL_FILE, the Oracle supplied file I/O package, which the upload routine uses to read the P6 flat file from a directory location accessible to the database server. No other application tables are referenced.

Usage Notes

PAY_GB_P6EDI_PKG is not referenced by any other package in the ETRM repository, indicating that it is invoked directly as a standalone process rather than as a shared API. In practice it is driven from a concurrent program that submits UPLOAD_P6 with the file name, business group, effective date, and validate-only indicator; the validate-only mode is used to inspect file contents before committing staged tax codes. After loading, the standard GB tax code interface processes read PAY_GB_TAX_CODE_INTERFACE to apply the changes. Support and custom implementations typically call the parsing functions (GET_QUALIFIER, PROCESS_ATT, PROCESS_TAX, PROCESS_DATE) only for diagnostics of malformed P6 files, since their signatures presume the fixed-width layout of the HMRC P6 message format.