VerifyAndGetF43121ZRecord

Verify and Get F43121Z Record

Major Business Rule

Object Name: B4300510

Parent DLL: CDIST

Location: Client/Server

Language: C

Functional Description

Purpose
To determine if a Purchase Order Receiver Workfile (F43121Z) record exists for the key passed in.
If it does exist then return the pointer for the record if requested.

Setup Notes and Prerequisites
Need to be aware of the standards for returning pointers and setting off errors (ie. CallType,
ReturnFlag, ErrorCode, SuppressErrors, etc.).

Technical Specification




 


IF (NumberOfKeys < 1 OR > 7) THEN


 NumberOfKeys = 7


ENDIF





Fill in the F43121Z key with the parameters.





Set the F43121Z number of keys to NumberOfKeys.





Retreive F43121Z in to F43121ZPointer.





Return F43121Z Pointer if requested otherwise free pointer





Return ErrorCode - 0 if Success else 1

^

Data Structure

D4300510 - Verify and Get F43121Z Record

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

szComputerID CTID char NONE NONE

mnJobNumber JOBS MATH_NUMERIC NONE NONE

The job number (work station ID) which executed the particular job.

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

szOrderKeyCompany 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.

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.

mnReceiptLineNumber 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.

nNumberOfKeys INT01 integer NONE NONE

Special Input Expected
Default = 7ab
^

cReturnPointer EV01 char NONE NONE

Special Input Expected
1 == Return the Pointerab
^

idF43121ZPointer GENLNG ID NONE NONE

General purpose ID variable.

cCallType EV02 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.

cSuppressErrors EV01 char NONE NONE

Special Input Expected
1 == Suppress Errorsab
^

szOrderSuffix SFXO char OPT 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.

Related Functions

None

Related Tables

F43121Z Receiver workfile

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
szComputerID	CTID	char	NONE	NONE

mnJobNumber	JOBS	MATH_NUMERIC	NONE	NONE
The job number (work station ID) which executed the particular job.
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
szOrderKeyCompany	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.
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.
mnReceiptLineNumber	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.
nNumberOfKeys	INT01	integer	NONE	NONE
Special Input Expected Default = 7ab ^
cReturnPointer	EV01	char	NONE	NONE
Special Input Expected 1 == Return the Pointerab ^
idF43121ZPointer	GENLNG	ID	NONE	NONE
General purpose ID variable.
cCallType	EV02	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.
cSuppressErrors	EV01	char	NONE	NONE
Special Input Expected 1 == Suppress Errorsab ^
szOrderSuffix	SFXO	char	OPT	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.