GetPurchaseOrderReceipt

Get Purchase Order Receipt

Major Business Rule

Object Name: B4300370

Parent DLL: CDIST

Location: Client/Server

Language: C

Functional Description

Purpose
To retrieve a complete row in the Purchase Order Receiver file (F43121) given: Order # and Type and
Suffix and Line #, Company, and # of Lines

Technical Specification




Edits:


IF (Index != 2) THEN


 Index = 1





IF (Index  = 1) THEN


 IF Matching Type (MATC) is not specified THEN


  Retrieve first record matching the rest of the keys.


 ENDIF


ELSE


 Retreive F43121 by DOC and DCT and KCO.


ENDIF





Retrievals:


If the record is found, then allocate and copied record into pointer.

Data Structure

D4300370 - Structure for GetPurchaseOrderReceipt

Parameter Name Data Item Data Type Req/Opt I/O/Both

mnOrderNumber DOCO MATH_NUMERIC NONE NONE

A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on.

szOrderType DCTO char NONE NONE

A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and
should not be changed: P Accounts Payable documents   R Accounts Receivable documents   T Payroll documents   I Inventory documents
O Purchase Order Processing documents   J General Accounting/Joint Interest Billing documents   S Sales Order Processing documents

szOrderCompany KCOO char NONE NONE

A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a
sales order, and so on). If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the
order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order
type, the order company lets you locate the desired document. If you use the regular Next Numbers facility, the order company is not used to
assign a next number. In this case, you probably would not use the order company to locate the document.

szOrderSuffix SFXO char NONE NONE

In the A/R and A/P systems, a code that corresponds to the pay item. In the Sales Order and Procurement systems, this code identifies
multiple transactions for an original order. For purchase orders, the code is always 000. For sales orders with multiple partial receipts against an
order, the first receiver used to record receipt has a suffix of 000, the next has a suffix of 001, the next 002, and so on.

mnOrderLineNumber LNID MATH_NUMERIC NONE NONE

A number that identifies multiple occurrences, such as line numbers on a purchase order or other document. Generally, the system assigns
this number,but in some cases you can override it.

cReturnFlag EV01 char NONE NONE

An option that specifies the type of processing for an event.

cErrorCode ERR char NONE NONE

The Data Field Error Code field is simply a generic data field to pass an error condition flag.  This field is one of the fields that make up the
external parameter data structure of the Data Dictionary Server.

cCallType ERR char NONE NONE

The Data Field Error Code field is simply a generic data field to pass an error condition flag.  This field is one of the fields that make up the
external parameter data structure of the Data Dictionary Server.

idPointerToF43121DataStructure GENLNG ID NONE NONE

General purpose ID variable.

cMatchType MATC char NONE NONE

A code, attached to each purchase-order detail record or receipt record, that indicates whether a voucher exists and whether the voucher
or receipt record has been reversed. Valid values are: 1 No voucher exists. 2 A voucher exists. 3 The voucher has been reversed. 4 The receipt
record has been reversed. Note: Record types 3 and 4 are audit records only; you cannot access these record types for the Voucher Match
program (P4314) or the PO Receipts program (P4312).

mnIndex CDL MATH_NUMERIC NONE NONE

The length of the user defined code. It cannot be greater than 10 characters.

szReceiptCompany KCO char NONE NONE

A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher,
or journal entry. If you use the Next Numbers by Company/Fiscal Year feature, the Automatic Next Numbers program (X0010) uses the
document company to retrieve the correct next number for that company. If two or more original documents have the same document number and
document type, you can use the document company to locate the desired document.

mnReceiptNumber DOC MATH_NUMERIC NONE NONE

A number that identifies the original document, such as a voucher, invoice, or journal entry. On entry forms, you can assign the document
number or let the system assign it using the Next Numbers program (P0002). Matching document numbers (DOCM) identify related documents
in the Accounts Receivable and Accounts Payable systems. Examples of original and matching documents are: Accounts Payable     o
Original document - voucher     o Matching document - payment Accounts Receivable     o Original document - invoice     o Matching document -
receipt Note: In the Accounts Receivable system, the following transactions simultaneously generate original and matching documents:
deductions, unapplied receipts, chargebacks, and drafts.

szReceiptType DCT char NONE NONE

A user defined code (00/DT) that identifies the origin and purpose of the transaction.  PeopleSoft reserves several prefixes for document
types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are: P Accounts payable
documents R Accounts receivable documents T Time and Pay documents I Inventory documents O Purchase order documents S Sales order
documents

mnNumberOfLines NLIN MATH_NUMERIC NONE NONE

A number representing the number of lines on either a purchase or sales order. or The number of receivers recorded during the receipts
process.  This field will be used in Voucher Matching.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnOrderNumber	DOCO	MATH_NUMERIC	NONE	NONE
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry, and so on.
szOrderType	DCTO	char	NONE	NONE
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and should not be changed: P Accounts Payable documents R Accounts Receivable documents T Payroll documents I Inventory documents O Purchase Order Processing documents J General Accounting/Joint Interest Billing documents S Sales Order Processing documents
szOrderCompany	KCOO	char	NONE	NONE
A number that, along with order number and order type, uniquely identifies an order document (such as a purchase order, a contract, a sales order, and so on). If you use the Next Numbers by Company/Fiscal Year facility, the Automatic Next Numbers program (X0010) uses the order company to retrieve the correct next number for that company. If two or more order documents have the same order number and order type, the order company lets you locate the desired document. If you use the regular Next Numbers facility, the order company is not used to assign a next number. In this case, you probably would not use the order company to locate the document.
szOrderSuffix	SFXO	char	NONE	NONE
In the A/R and A/P systems, a code that corresponds to the pay item. In the Sales Order and Procurement systems, this code identifies multiple transactions for an original order. For purchase orders, the code is always 000. For sales orders with multiple partial receipts against an order, the first receiver used to record receipt has a suffix of 000, the next has a suffix of 001, the next 002, and so on.
mnOrderLineNumber	LNID	MATH_NUMERIC	NONE	NONE
A number that identifies multiple occurrences, such as line numbers on a purchase order or other document. Generally, the system assigns this number,but in some cases you can override it.
cReturnFlag	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cErrorCode	ERR	char	NONE	NONE
The Data Field Error Code field is simply a generic data field to pass an error condition flag. This field is one of the fields that make up the external parameter data structure of the Data Dictionary Server.
cCallType	ERR	char	NONE	NONE
The Data Field Error Code field is simply a generic data field to pass an error condition flag. This field is one of the fields that make up the external parameter data structure of the Data Dictionary Server.
idPointerToF43121DataStructure	GENLNG	ID	NONE	NONE
General purpose ID variable.
cMatchType	MATC	char	NONE	NONE
A code, attached to each purchase-order detail record or receipt record, that indicates whether a voucher exists and whether the voucher or receipt record has been reversed. Valid values are: 1 No voucher exists. 2 A voucher exists. 3 The voucher has been reversed. 4 The receipt record has been reversed. Note: Record types 3 and 4 are audit records only; you cannot access these record types for the Voucher Match program (P4314) or the PO Receipts program (P4312).
mnIndex	CDL	MATH_NUMERIC	NONE	NONE
The length of the user defined code. It cannot be greater than 10 characters.
szReceiptCompany	KCO	char	NONE	NONE
A number that, with the document number, document type and G/L date, uniquely identifies an original document, such as invoice, voucher, or journal entry. If you use the Next Numbers by Company/Fiscal Year feature, the Automatic Next Numbers program (X0010) uses the document company to retrieve the correct next number for that company. If two or more original documents have the same document number and document type, you can use the document company to locate the desired document.
mnReceiptNumber	DOC	MATH_NUMERIC	NONE	NONE
A number that identifies the original document, such as a voucher, invoice, or journal entry. On entry forms, you can assign the document number or let the system assign it using the Next Numbers program (P0002). Matching document numbers (DOCM) identify related documents in the Accounts Receivable and Accounts Payable systems. Examples of original and matching documents are: Accounts Payable o Original document - voucher o Matching document - payment Accounts Receivable o Original document - invoice o Matching document - receipt Note: In the Accounts Receivable system, the following transactions simultaneously generate original and matching documents: deductions, unapplied receipts, chargebacks, and drafts.
szReceiptType	DCT	char	NONE	NONE
A user defined code (00/DT) that identifies the origin and purpose of the transaction. PeopleSoft reserves several prefixes for document types, such as, vouchers, invoices, receipts, and timesheets. The reserved document type prefixes for codes are: P Accounts payable documents R Accounts receivable documents T Time and Pay documents I Inventory documents O Purchase order documents S Sales order documents
mnNumberOfLines	NLIN	MATH_NUMERIC	NONE	NONE
A number representing the number of lines on either a purchase or sales order. or The number of receivers recorded during the receipts process. This field will be used in Voucher Matching.