Search Results per_data_exchange_dir

Overview

PAY_GB_P6EDI_PKG is a United Kingdom localizations package in Oracle E-Business Suite that implements the P6 end-of-year expenses and benefits electronic data interchange (EDI) process. The package body parses flat-file submissions in the Inland Revenue P6 format and loads the parsed records into the PAY_GB_TAX_CODE_INTERFACE table for subsequent validation and processing by the payroll application. The header comment in the source confirms this purpose: the code "uploads p6 information from flat file into pay_gb_tax_code_interface table."

The package is not classified as a public API; ETRM records it with an API classification of OTHER, and it is referenced by no other packages. It is an internal processing component invoked through a concurrent program that outbound or inbound EDI processing drives. The source header shows version 120.4 dated 2007/11/02, consistent with the code lineage carried forward into EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

• UPLOAD_P6 — The principal entry point. It reads the P6 flat file, parses each record into fixed-position and qualifier-delimited fields (form type, form number, district number, employer reference, NI number, works number, tax code, employee name, dates, and week1/month1 indicator), and writes the extracted rows to the interface table. It accepts a request ID, filename, processing mode, effective date, business group, and a validate-only flag. On error it populates the standard concurrent program OUT parameters errbuf and retcode.
• GET_QUALIFIER — Extracts the three-character qualifier that identifies the type of data element within a P6 record, governing how the remaining positions of the line are interpreted.
• GET_NAME — Resolves and formats the employee name component from the incoming record so it can be stored against the interface row.
• PROCESS_ATT — Handles the processing of attendance or related attribute data within the P6 record structure.
• PROCESS_DATE — Converts and validates date values encountered in the P6 message, such as the date of message, effective date, and issue date.
• PROCESS_TAX — Processes the tax code and tax-related monetary fields (for example total pay and total tax from a previous employer) for insertion into the interface table.
• WRITE_TO_DATABASE — Performs the actual DML insert into PAY_GB_TAX_CODE_INTERFACE, committing the parsed record set produced by the preceding procedures.

Tables Accessed

• PAY_GB_TAX_CODE_INTERFACE — The staging table that receives the parsed P6 records. Rows inserted here are subsequently read by further payroll processing that applies the tax code information to employee assignments.
• UTL_FILE — The Oracle-supplied file I/O package used to open and read the P6 flat file. UTL_FILE is referenced through its database package rather than an APPS synonym.

Usage Notes

The package is normally invoked by a concurrent program that submits the P6 upload, passing the file name and business group as parameters. The routine obtains the source file location by calling FND_PROFILE.GET for the PER_DATA_EXCHANGE_DIR profile option, which is the standard EBS profile controlling the directory used for data exchange files. This is directly relevant to searches for "per_data_exchange_dir," since the profile must be set correctly for UPLOAD_P6 to locate the flat file.

The p_validate_only parameter allows a run to parse and report the file contents without committing interface rows, which supports pre-production verification. UPLOAD_P6 also accepts an explicit request ID, allowing the package to be called from custom code that must propagate a concurrent request identifier for traceability. Because no other packages reference PAY_GB_P6EDI_PKG, it should be treated as an internal component rather than a supported integration API.