Search Results hrdpp_create_payment_detail




Overview
Explore in AI Chat

Overview

APPS.HRDPP_CREATE_PAYMENT_DETAIL is a generated PL/SQL wrapper package that exposes the business logic of the Oracle Human Resources payment detail API, PER_BF_PAYMENT_DETAILS_API.CREATE_PAYMENT_DETAIL, to the Oracle E-Business Suite data pump framework. The package is part of the HRDPP (HR Data Pump) family of generated packages, and its generator header identifies it as the output of hr_pump_meta_mapper, produced in January 2007 against PER_BF_PAYMENT_DETAILS_API. In Oracle EBS 12.1.1 and 12.2.2, this package is significant to payroll and disbursement integrations because it is the programmatic entry point through which externally supplied payment instruction data — check number, payment date, amount, currency, and a set of descriptive flexfield attributes — is validated and inserted into the HR data pump batch tables for downstream processing by Oracle Payroll and Oracle Payments.

From the perspective of a host-to-host bank integration, such as an HDFC host-to-host payment file format requirement, this package represents the inbound leg of the pipeline. The bank file format (fixed-width or delimited, containing beneficiary, amount, currency, and reference fields) is parsed by a custom loader or a SQL*Loader/External Table process, and the resulting rows are passed into the procedures of HRDPP_CREATE_PAYMENT_DETAIL to create standard, framework-compliant payment detail records rather than ad hoc inserts into base tables.

Key Procedures and Functions

  • INSERT_BATCH_LINES — the core public procedure. It accepts a batch identifier, data pump batch line identifier, business group name, user sequence, and link value, together with payment-level inputs including effective date, check number, payment date, amount, check type, currency code, and fifteen BPD descriptive flexfield attribute segments. It maps these values onto PER_BF_PAYMENT_DETAILS_API.CREATE_PAYMENT_DETAIL and writes the resulting payment detail lines into the data pump batch structures.
  • CALL — a documented wrapper procedure in the package interface, used to invoke the underlying API logic in a controlled manner consistent with the generated mapper pattern, including handling of error/exception propagation.
  • DC, D, N, DD, ND — conversion helper functions declared with PRAGMA RESTRICT_REQUIRES(WNDS). DC converts a DATE to VARCHAR2, D converts VARCHAR2 to DATE, N converts VARCHAR2 to NUMBER, DD converts DATE to VARCHAR2 with a supplied format indicator, and ND converts NUMBER to VARCHAR2 with a supplied indicator. These support NLS-independent parsing and formatting of values coming from flat bank files.

Tables Accessed

The package operates against the HR data pump batch model. HR_PUMP_BATCH_LINES and its synonym/translation view HR_PUMP_BATCH_LINES_S store the individual payment detail rows, including amount, check number, payment date, and currency code. HR_PUMP_BATCH_LINE_USER_KEYS and HR_PUMP_BATCH_LINE_USER_KEYS_S hold the user key values that uniquely identify each line for the external source system, typically the bank reference or transaction identifier. HR_PUMP_BATCH_EXCEPTIONS captures row-level validation failures so rejected payment lines from a bank file can be reported and corrected without aborting the entire batch.

Usage Notes

HRDPP_CREATE_PAYMENT_DETAIL is not normally invoked by end users. It is called by concurrent programs, by the HR data pump loader, or by custom PL/SQL and SQL*Loader-based integrations that have already staged bank payment data. In an HDFC host-to-host scenario, the typical invocation is a custom concurrent program that reads the HDFC file, splits records, and calls INSERT_BATCH_LINES once per payment line within a batch. Because the package writes to the data pump tables rather than to PAY_PAYMENT_DETAILS directly, callers must still run the corresponding data pump business group/loader step to promote the lines into the permanent payment detail tables. Error handling should always check HR_PUMP_BATCH_EXCEPTIONS after the call, and the date/number conversion functions should be used consistently to avoid NLS-related data corruption when parsing the bank file.