InvBalanceRealTimeEventTemplate

Item Balance Real Time Event Notification Template

Minor Business Rule

Object Name: B4101660

Parent DLL: CINV

Location: Client/Server

Language: C

Data Structure

D4101660A - Item Balance Real Time Event Notification Template

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
cActionCode	ACTN	char	REQ	INPUT
A code that specifies the action that is performed. Valid values are: A Add C Change
szLocation	LOCN	char	REQ	INPUT
The storage location from which goods will be moved.
cPrimaryBinPS	PBIN	char	REQ	INPUT
A code that indicates whether this is the primary or secondary location for this item within this stocking location. Valid values are: P Primary storage location S Secondary storage location Note: You can only have one storage area marked as primary within each branch or warehouse. In some cases, the system uses the primary storage area as the default.
cLotStatusCode	LOTS	char	REQ	INPUT
A user defined code (41/L) that indicates the status of the lot. If you leave this field blank, it indicates that the lot is approved. All other codes indicate that the lot is on hold. You can assign a different status code to each location in which a lot resides on Item/Location Information or Location Lot Status Change.
mnQtyBackorderedInPri	PBCK	MATH_NUMERIC	REQ	INPUT
The number of units backordered in primary units of measure.
mnQtyOnPurchaseOrderPr	PREQ	MATH_NUMERIC	REQ	INPUT
The number of units specified on the purchase order in primary units of measure.
mnQuantityOnWoReceipt	QWBO	MATH_NUMERIC	REQ	INPUT
The number of units on work orders in primary units of measure.
mnQty1OtherPrimaryUn	OT1P	MATH_NUMERIC	REQ	INPUT
The first of two quantities that can be specified as additional offsets (subtractions from on-hand) in the determination of quantities available for sale. (Primary unit of measure)
mnQty2OtherPrimaryUn	OT2P	MATH_NUMERIC	REQ	INPUT
The second of two quantities that can be specified as additional offsets (subtractions from on-hand) in the determination of quantities available for sale. (Primary unit of measure)
mnQtyOtherPurchasing1	OT1A	MATH_NUMERIC	REQ	INPUT
The quantity that appears on documents such as bid requests, which are not formal commitments to buy on the part of your organization.
mnQuantitySoftCommitted	PCOM	MATH_NUMERIC	REQ	INPUT
The number of units soft committed to sales orders or work orders in the primary units of measure.
mnQtyOnFutureCommit	FCOM	MATH_NUMERIC	REQ	INPUT
The quantity on sales order whose requested shipment date is beyond the standard commitment period that has been specified in the Inventory Constants for that branch. As an example, if you normally ship most orders within 90 days, then an order for an item with a requested ship date a year from now would have its quantity reflected in this field.
mnQtyHardCommitted	HCOM	MATH_NUMERIC	REQ	INPUT
The number of units committed to a specific location and lot.
mnWorkOrderSoftCommit	FUN1	MATH_NUMERIC	REQ	INPUT
The number of units soft committed to Work Orders in the primary unit of measure.
mnQuantityOnWorkorder	QOWO	MATH_NUMERIC	REQ	INPUT
The number of units hard committed to work orders in the primary unit of measure.
mnQtyInTranPrimaryUn	QTTR	MATH_NUMERIC	REQ	INPUT
The quantity currently in transit from the supplier.
mnQtyInInspPrimaryUn	QTIN	MATH_NUMERIC	REQ	INPUT
The quantity currently being inspected. This quantity has been received, but is not considered on hand.
mnQuantityOnLoanToMa	QONL	MATH_NUMERIC	REQ	INPUT

mnQuantityInboundWareh	QTRI	MATH_NUMERIC	REQ	INPUT
A quantity in the primary unit of measure that you expect to add to the location detail after you confirm a putaway or replenishment suggestion.
mnQuantityOutboundWare	QTRO	MATH_NUMERIC	REQ	INPUT
A quantity in the primary unit of measure that you expect to remove from the location after you confirm a picking or replenishment suggestion.
mnFutureUseQuantity	QTY1	MATH_NUMERIC	REQ	INPUT
Quantity for future use in the Item Location file (F4102).
mnFutureUseQuantity2	QTY2	MATH_NUMERIC	REQ	INPUT
Quantity for future use in the Item Location file (F4102).
mnNetChangeQuantity	TRQT	MATH_NUMERIC	REQ	BOTH
A value that represents the available quantity, which might consist of the on-hand balance minus commitments, reservations, and backorders. You enter this value in the Branch/Plant Constants program (P41001).
szTransactionDocumentType	DCT	char	REQ	INPUT
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
jdDateUpdated	UPMJ	JDEDATE	REQ	OUTPUT
The date that specifies the last update to the file record.
mnTimeUpdated	TDAY	MATH_NUMERIC	REQ	OUTPUT
The computer clock in hours:minutes:seconds.
szPlanningUOM	CMUM	char	OPT	OUTPUT

mnPlanningQuantity	TRQT	MATH_NUMERIC	OPT	OUTPUT
A value that represents the available quantity, which might consist of the on-hand balance minus commitments, reservations, and backorders. You enter this value in the Branch/Plant Constants program (P41001).
cAPSFlag	EV01	char	REQ	OUTPUT
An option that specifies the type of processing for an event.
cAPSSupplyDemandFlag	EV01	char	REQ	OUTPUT
An option that specifies the type of processing for an event.
mnIdentifierShortItem	ITM	MATH_NUMERIC	OPT	NONE
An inventory item number. The system provides three separate item numbers plus an extensive cross-reference capability to other item numbers (see data item XRT) to accommodate substitute item numbers, replacements, bar codes, customer numbers, supplier numbers, and so forth. The item numbers are as follows: o Item Number (short) - An eight-digit, computer-assigned item number o 2nd Item Number - The 25-digit, free-form, user defined alphanumeric item number o 3rd Item Number - Another 25-digit, free-form, user defined alphanumeric item number
szCostCenter	MCU	char	OPT	NONE
An alphanumeric code that identifies a separate entity within a business for which you want to track costs. For example, a business unit might be a warehouse location, job, project, work center, branch, or plant. You can assign a business unit to a document, entity, or person for purposes of responsibility reporting. For example, the system provides reports of open accounts payable and accounts receivable by business unit to track equipment by responsible department. Business unit security might prevent you from viewing information about business units for which you have no authority.
mnQtyOnHandPrimaryUn	PQOH	MATH_NUMERIC	OPT	NONE
The number of units that are physically in stock. The system displays the quantity on-hand in the primary unit of measure.
mnUnitsTransactionQty01	QT01	MATH_NUMERIC	OPT	NONE
Quantity field in the Batch Receiver Destination Quantity table (F4012Z) that is used to process multiple ship to locations. This function is only valid for EDI transactions.
mnUnitsTransactionQty02	QT02	MATH_NUMERIC	OPT	NONE
Quantity field in the Batch Receiver File - Destination Quantity (F4012Z) that is used to process multiple ship to locations. This is only a function valid for EDI transactions.
szLot	LOTN	char	OPT	NONE
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics.
szPlanningLotStatus	DL01	char	OPT	NONE
A user defined name or remark.

Related Functions

None

Related Tables

None