PurchaseOrderRealTimeWrapper4

Purchase Order Real Time Event Notification Function 4

Major Business Rule

Object Name: B4302154

Parent DLL: CDIST

Location: Client/Server

Language: C

Data Structure

D4302154A - Purchase Order Real Time Event Notification

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cEventAction	EV01	char	REQ	INPUT
An option that specifies the type of processing for an event.
szErrorID	EV01	char	OPT	OUTPUT
An option that specifies the type of processing for an event.
idEventID	GENLNG	ID	OPT	BOTH
General purpose ID variable.
cHeaderDetailFlag	EV01	char	REQ	INPUT
An option that specifies the type of processing for an event.
cErrorStatus	EV01	char	OPT	OUTPUT
An option that specifies the type of processing for an event.
idHeaderPointer	GENLNG	ID	OPT	INPUT
General purpose ID variable.
idDetailPointer	GENLNG	ID	OPT	INPUT
General purpose ID variable.
cErrorAPIEventReturn	EV01	char	OPT	OUTPUT
An option that specifies the type of processing for an event.
mnOrderNumber	DOCO	MATH_NUMERIC	REQ	INPUT
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	REQ	INPUT
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	REQ	INPUT
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	REQ	INPUT
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	REQ	INPUT
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.
cOrderAction	ACTN	char	REQ	INPUT
A code that specifies the action that is performed. Valid values are: A Add C Change
szEventName	VC10A	char	REQ	INPUT
This is a generic field used as a work field in Everest.
szEventScope	VC30A	char	REQ	INPUT
This is a generic field used as a work field in Everest.
szCallingFunctionName	VC30A	char	REQ	INPUT
This is a generic field used as a work field in Everest.
cFutureUseFlag	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
nFutureUseInteger	INT01	integer	OPT	INPUT
Number of Days in Future to Query for Responses Due.
mnFutureUseMathNumeric	MATH01	MATH_NUMERIC	OPT	NONE
- - - Good Performance Low Value.
szFutureUseString	VC30A	char	OPT	NONE
This is a generic field used as a work field in Everest.

Related Functions

None

Related Tables

None