Skip to content
JDE Reference

F03B14

transaction

Receipts detail: one row per application of a receipt against an invoice pay item, splitting the cash into payment, discount, write-off, chargeback, and deduction amounts.

Notes

Payment + discount + write-off + chargeback + deduction amounts explain how each invoice pay item was settled; sum RZPAAP by invoice key to reconcile against F03B11 open amounts.

What the badges mean
Superseded
Superseded — a newer table has replaced it, but older scripts still read this one.
Also in JDE World
Also present in JDE World A9.x on the same table name.
master
Data class: what the table holds — master data, transaction documents, control/setup values, history, or a workfile.
Read/write access
Access mode: how the paired program reads or writes this table — R (read), W (write), or R/W (both).
No lifecycle badge means the table is current and not documented in JDE World. In field listings, K marks a primary-key field.

Fields

39 fields · 2 key

39 fields.

Table fields: key flag, field name, DD alias, description, data type, length, and quirk flags (Julian date, implied decimals, padded string, UDC decode). 39 fields.
KeyFieldAliasDescriptionTypeLengthFlags
Primary keyRZPYIDPYIDPayment ID linking back to the F03B13 receipt headerNumeric15
Primary keyRZRC5RC5Line number within the receipt — makes each application row uniqueNumeric5
RZCKNUCKNUReceipt/check number repeated from the header for convenienceString25
RZDOCDOCInvoice document number the cash was applied toNumeric8
RZDCTDCTInvoice document typeString2
RZKCOKCOInvoice document companyString5
RZSFXSFXInvoice pay item the application hitString3
RZAN8AN8Customer address book numberNumeric8
RZDCTMDCTMMatching document type of the receipt (RC)String2
RZDMTJDMTJReceipt dateNumeric (DD type: Date)6
RZDGJDGJG/L date of the applicationNumeric (DD type: Date)6
RZPOSTPOSTG/L posted code for the application rowCharacter1
RZGLCGLCG/L offset class used to resolve the A/R trade accountString4
RZCTRYCTRYCentury of the G/L dateNumeric2
RZFYFYFiscal year of the G/L dateNumeric2
RZPNPNFiscal period of the G/L dateNumeric2
RZCOCOCompany of the applicationString5
RZICUTICUTBatch type (RB)String2
RZICUICUBatch number of the receipt batchNumeric8
RZDICJDICJBatch dateNumeric (DD type: Date)6
RZPAAPPAAPAmount of this receipt applied to the invoice, domestic currencyNumeric15
RZADSCADSCDiscount that was available on the invoice at application timeNumeric15
RZADSAADSADiscount taken as part of the applicationNumeric15
RZAAAJAAAJAmount written off during applicationNumeric15
RZECBAECBAChargeback amount generated — creates a new invoice for the disputed pieceNumeric15
RZDDADDADeduction amount routed to deduction processingNumeric15
RZBCRCBCRCBase (domestic) currencyString3
RZCRRMCRRMCurrency mode — domestic or foreign entryCharacter1
RZCRCDCRCDTransaction currency of the receiptString3
RZCRRCRRExchange rate used for the application; implied decimals vary by setupNumeric15
RZPFAPPFAPApplied amount in the foreign currencyNumeric15
RZAGLAGLRealized gain or loss recognized on the applicationNumeric15
RZRSCORSCOWrite-off reason codeString2
RZECBRECBRChargeback reason codeString2
RZDDEXDDEXDeduction reason codeString2
RZTYINTYINReceipt type code from the headerCharacter1
RZMCUMCUBusiness unit of the applicationString12
RZPDLTPDLTPartial payment flagCharacter1
RZDDJDDJNet due date of the invoice being paid, useful for on-time payment analysisNumeric (DD type: Date)6

Field provenance: hand-curated.

Boilerplate SQL

Starting point for reading F03B14 on Databricks — Julian dates, implied decimals, and padded strings are already converted. Set your Unity Catalog location and filter values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema_data>, <DGJ_FROM>, <DGJ_TO>

-- ============================================================
-- Table  : F03B14 Receipts detail: one row per application of a receipt against an invoice pay item, splitting the cash into payment, discount, write-off, chargeback, and deduction amounts.
-- Purpose: Column-selected read of F03B14 — auto-generated from field metadata
-- Grain  : One row per RZPYID + RZRC5
-- Notes  : Auto-generated skeleton. Julian dates (CYYDDD) are converted to DATE and implied-decimal amounts are scaled (verify decimals in F9210); padded business-unit/UDC keys are TRIMmed. Audit columns (…USER/…PID/…UPMJ) are omitted — see the quirks guide. Set catalog/schema to your Unity Catalog location; fill remaining placeholders (<...>) for your tenant.
-- ============================================================
SELECT
  f.RZPYID AS "Payment ID linking back to the F03B13 receipt header",
  f.RZRC5 AS "Line number within the receipt — makes each application row unique",
  f.RZCKNU AS "Receipt/check number repeated from the header for convenience",
  f.RZDOC AS "Invoice document number the cash was applied to",
  f.RZDCT AS "Invoice document type",
  f.RZKCO AS "Invoice document company",
  f.RZSFX AS "Invoice pay item the application hit",
  f.RZAN8 AS "Customer address book number",
  f.RZDCTM AS "Matching document type of the receipt (RC)",
  CASE WHEN f.RZDMTJ IS NULL OR f.RZDMTJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.RZDMTJ AS INT) DIV 1000, 1, 1), CAST(f.RZDMTJ AS INT) % 1000 - 1) END AS "Receipt date",  -- CYYDDD Julian → DATE
  CASE WHEN f.RZDGJ IS NULL OR f.RZDGJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.RZDGJ AS INT) DIV 1000, 1, 1), CAST(f.RZDGJ AS INT) % 1000 - 1) END AS "G/L date of the application",  -- CYYDDD Julian → DATE
  f.RZPOST AS "G/L posted code for the application row",
  f.RZGLC AS "G/L offset class used to resolve the A/R trade account",
  f.RZCTRY AS "Century of the G/L date",
  f.RZFY AS "Fiscal year of the G/L date",
  f.RZPN AS "Fiscal period of the G/L date",
  f.RZCO AS "Company of the application",
  f.RZICUT AS "Batch type (RB)",
  f.RZICU AS "Batch number of the receipt batch",
  CASE WHEN f.RZDICJ IS NULL OR f.RZDICJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.RZDICJ AS INT) DIV 1000, 1, 1), CAST(f.RZDICJ AS INT) % 1000 - 1) END AS "Batch date",  -- CYYDDD Julian → DATE
  f.RZPAAP / POWER(10, 2) AS "Amount of this receipt applied to the invoice, domestic currency",  -- implied decimals: 2 (verify in F9210)
  f.RZADSC / POWER(10, 2) AS "Discount that was available on the invoice at application time",  -- implied decimals: 2 (verify in F9210)
  f.RZADSA / POWER(10, 2) AS "Discount taken as part of the application",  -- implied decimals: 2 (verify in F9210)
  f.RZAAAJ / POWER(10, 2) AS "Amount written off during application",  -- implied decimals: 2 (verify in F9210)
  f.RZECBA / POWER(10, 2) AS "Chargeback amount generated — creates a new invoice for the disputed piece",  -- implied decimals: 2 (verify in F9210)
  f.RZDDA / POWER(10, 2) AS "Deduction amount routed to deduction processing",  -- implied decimals: 2 (verify in F9210)
  f.RZBCRC AS "Base (domestic) currency",
  f.RZCRRM AS "Currency mode — domestic or foreign entry",
  f.RZCRCD AS "Transaction currency of the receipt",
  f.RZCRR AS "Exchange rate used for the application; implied decimals vary by setup",
  f.RZPFAP / POWER(10, 2) AS "Applied amount in the foreign currency",  -- implied decimals: 2 (verify in F9210)
  f.RZAGL / POWER(10, 2) AS "Realized gain or loss recognized on the application",  -- implied decimals: 2 (verify in F9210)
  f.RZRSCO AS "Write-off reason code",
  f.RZECBR AS "Chargeback reason code",
  f.RZDDEX AS "Deduction reason code",
  f.RZTYIN AS "Receipt type code from the header",
  TRIM(f.RZMCU) AS "Business unit of the application",
  f.RZPDLT AS "Partial payment flag",
  CASE WHEN f.RZDDJ IS NULL OR f.RZDDJ = 0 THEN NULL ELSE DATE_ADD(MAKE_DATE(1900 + CAST(f.RZDDJ AS INT) DIV 1000, 1, 1), CAST(f.RZDDJ AS INT) % 1000 - 1) END AS "Net due date of the invoice being paid, useful for on-time payment analysis"  -- CYYDDD Julian → DATE
FROM <catalog>.<schema_data>.f03b14 f
WHERE
  f.RZDGJ >= <DGJ_FROM>  -- Julian CYYDDD, e.g. 126001
  -- AND f.RZDGJ <= <DGJ_TO>  -- Julian CYYDDD, e.g. 126365
ORDER BY f.RZPYID;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. UDC decode edges point coded fields at their F0005 lookup.

Join details

  • F03B13F03B14header detail · 1:N
    ON f03b13.RYPYID = f03b14.RZPYID
  • F03B14F03B11foreign key · N:1
    ON f03b14.RZDOC = f03b11.RPDOC

Programs That Use This Table

R read · W write · R/W read + write

Secondary programs

More Accounts Receivable tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle, JD Edwards, and EnterpriseOne are registered trademarks of Oracle and/or its affiliates.