SpeedLotUpdate

Speed Lot Update

Major Business Rule

Object Name: B4000850

Parent DLL: COPBASE

Location: Client/Server

Language: C

Functional Description

Purpose
To allow selection of data to be updated in Lot Master Table (F4108). If any changed flags are set
to '1', then the associated data will be used for update.

Technical Specification




Retrievals:


Fetch Lot Master Table (F4108) with ITM, MCU and LOTN for each record passed into this function.  

Update the Lot Master Table (F4108) based on the information passed.   








04/27/95 cdl


If any Changed Flag is set to a '1', use the associated information passed in for updating F4108.





04/27/95  cdl


If the Lot Status Code retrieved from F4108 is blank and the Lot Status Code passed in is not blank 

or Lot Status Code retrieved from F4108 is not blank and the Lot Status Code passed in is blank, call 

GetUDC as


followed:





Fetch to the UserDefinedCode table for 40/LQ and the Document Type passed in. (Use X0005:  GetUDC)


 Look at the first character of the description fields for the UDC (DL01)


 if equals to '1' :  add the transaction quantity to UserDefineQuanitity(UB01)


 if equals to '2' :  add the transaction quantity to UserDefineQuanitity(UB02)


 if equals to '3' :  add the transaction quantity to UserDefineQuanitity(UB03)


 if equals to '4' :  add the transaction quantity to UserDefineQuanitity(UB04)


 if equals to '5' :  add the transaction quantity to UserDefineQuanitity(UB05)


 if equals to '6' :  add the transaction quantity to UserDefineQuanitity(UB06)





 Note: This function will not know if  the  Transaction Quantity is positive or 

negative value.


  Positive and Negative Transaction Quanitity must be determined prior to 

calling this function.





Fetch to the UserDefinedCode table for 40/LD and the Document Type passed in. (Use X0005:  GetUDC)


 Look at the first character of the description fields for the UDC (DL01)


 if equals to '1' :  move transaction date if not NULL  to UserDefineDate(UB01)


 if equals to '2' :  move transaction date if not NULL  to UserDefineDate(UB02)


 if equals to '3' :  move transaction date if not NULL  to UserDefineDate(UB03)


 if equals to '4' :  move transaction date if not NULL  to UserDefineDate(UB04)


 if equals to '5' :  move transaction date if not NULL  to UserDefineDate(UB05)


 if equals to '6' :  move transaction date if not NULL  to UserDefineDate(UB06)

Data Structure

D4000850 - Speed Lot Update

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnShortItemNumber	ITM	MATH_NUMERIC	NONE	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
szBranchPlant	MCU	char	NONE	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.
szLot	LOTN	char	NONE	NONE
A number that identifies a lot or a serial number. A lot is a group of items with similar characteristics.
cLotStatusCode	LOTS	char	NONE	NONE
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.
szLotGrade	LOTG	char	NONE	NONE
A code that indicates the grade of a lot. The grade is used to indicate the quality of the lot. Examples include the following: A1 Premium grade A2 Secondary grade The grade for a lot is stored in the Lot Master table (F4108).
mnLotPotency	LOTP	MATH_NUMERIC	NONE	NONE
A code that indicates the potency of the lot expressed as a percentage of active or useful material (for example, the percentage of alcohol in a solution). The actual potency of a lot is defined in the Lot Master table (F4108).
jdExpirationDate	MMEJ	JDEDATE	NONE	NONE
The date on which a lot of items expires. The system automatically enters this date if you have specified the shelf life days for the item on Item Master Information or Item Branch/Plant Information. The system calculates the expiration date by adding the number of shelf life days to the date that you receive the item. You can commit inventory based on the lot expiration date for items. You choose how the system commits inventory for an item on Item Master Information or Item Branch/Plant Information.
jdReceivedDate	UA01	JDEDATE	NONE	NONE
The last date that a particular activity occurred. You determine the type of activity that the category represents (for example, receipts). This field represents date category 1. You specify the document types that update this category in user defined codes (system 40, type LD).
jdIssuedDate	UA02	JDEDATE	NONE	NONE
The last date that a particular activity occurred. You determine the type of activity that the category represents (for example, issues to work orders). This field represents date category 2. You specify the document types that update this category in user defined codes (system 40, type LD).
jdAdjustedDate	UA03	JDEDATE	NONE	NONE
The last date that a particular activity occurred. You determine the type of activity that the category represents (for example, recalibration dates). This field represents date category 3. You specify the document types that update this category in user defined codes (system 40, type LD).
jdCompletedDate	UA04	JDEDATE	NONE	NONE
The last date that a particular activity occurred. You determine the type of activity that the category represents (for example, inventory completions). This field represents date category 4. You specify the document types that update this category in user defined codes (system 40, type LD).
jdApprovedDate	UA05	JDEDATE	NONE	NONE
The last date that a particular activity occurred. You determine the type of activity that the category represents (for example, lot status approvals). This field represents date category 5. You specify the document types that update this category in user defined codes (system 40, type LD).
jdSoldDate	UA06	JDEDATE	NONE	NONE
The last date that a particular activity occurred. You determine the type of activity that the category represents (for example, sales). This field represents date category 6. You specify the document types that update this category in user defined codes (system 40, type LD).
mnSupplierNumber	VEND	MATH_NUMERIC	NONE	NONE
The address book number of the preferred provider of this item.
szSupplierLotNumber	RLOT	char	NONE	NONE
The supplier's lot number for the item.
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
szStatusChangeReason	STRCD	char	NONE	NONE

szGradeChangeReason	GRRCD	char	NONE	NONE

szPotencyChangeReason	PTRCD	char	NONE	NONE

cUpdateLotStatus	EV01	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateLotGrade	EV02	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateLotPotency	EV03	char	NONE	NONE
A radio button that specifies the level at which trace/track result is to be displayed. Select the Detail to display all transactions except IB, IX, and IZ types. Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.
cUpdateReceivedDate	EV04	char	NONE	NONE
PeopleSoft event point processing flag 04.
cUpdateIssuedDate	EV05	char	NONE	NONE
A flag that indicates whether automatic spell check is turned on.
cUpdateAdjustedDate	EV06	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateCompletedDate	EV07	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateApprovedDate	EV08	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateSoldDate	EV09	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateExpirationDate	EV10	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateSupplier	EV11	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateSupplierLotNumber	EV12	char	NONE	NONE
An option that specifies the type of processing for an event.
cUpdateOrderNumber	EV13	char	NONE	NONE
An option that specifies the type of processing for an event.
szKeyCompany	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.
szDocumentType	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
mnTransactionQuantity	TRQT	MATH_NUMERIC	NONE	NONE
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).
jdTransactionDate	TRDJ	JDEDATE	NONE	NONE
The date that an order was entered into the system. This date determines which effective level the system uses for inventory pricing.
szProgramID	PID	char	NONE	NONE
The number that identifies the batch or interactive program (batch or interactive object). For example, the number of the Sales Order Entry interactive program is P4210, and the number of the Print Invoices batch process report is R42565. The program ID is a variable length value. It is assigned according to a structured syntax in the form TSSXXX, where: T The first character of the number is alphabetic and identifies the type, such as P for Program, R for Report, and so on. For example, the value P in the number P4210 indicates that the object is a program. SS The second and third characters of the number are numeric and identify the system code. For example, the value 42 in the number P4210 indicates that this program belongs to system 42, which is the Sales Order Processing system. XXX The remaining characters of the numer are numeric and identify a unique program or report. For example, the value 10 in the number P4210 indicates that this is the Sales Order Entry program.
jdLotEffectivityDate	DLEJ	JDEDATE	OPT	NONE
The date on which a lot becomes available. The system uses this date for availability and commitment processing to indicate that the lot is available on or after the date that you specify. You must complete this field when inventory first becomes an on-hand quantity for the lot. If you leave this field blank, the system calculates the effective date of the lot by using the value for Effective Days in the Item Branch File table (F4102) or the current date if the value for Effective Days is zero.
jdBestBeforeDate	BBDJ	JDEDATE	OPT	NONE
The last date on which the products in a lot should be consumed. The system calculates the date by retrieving the value from the Best Before Days field in the Item Master program (P4101). You can also use this date as a "through" date for commitment processing. You can commit a lot by this date by using the Commitment Date Method field in the Item Branch program (P41026).
jdSellByDate	SBDJ	JDEDATE	OPT	NONE
The date by which a lot should be completely sold. The system uses this date as a "through" date for commitment processing. The system calculates the sell by date using the value in the Sell By Days field, which is contained in the Item Branch File table (F4102), when inventory becomes available on-hand.
jdUserLotDate1	U1DJ	JDEDATE	OPT	NONE
A date that the system can use as a through date for commitment processing. The system stores this date in the Lot Master table (F4108). If you leave this field blank, the system can calculate the date by using the value for the User Lot Date 1 Default Days field, which is stored in the Item Branch File table (F4102).
jdUserLotDate2	U2DJ	JDEDATE	OPT	NONE
A user-defined date that can be used for commitment purposes and is stored in the Lot Master table (F4108). Similar to the Lot Expiration Date, User Lot Date 2 is a through date for commitment processing. The User Lot Date 2 commitment option is available in the Commitment Date Method in the Item Branch table (F4102). The system uses the User Lot Date 2 Default Days from the Item Branch table (F4102) to calculate User Lot Date 2 when inventory first goes on hand.
jdUserLotDate3	U3DJ	JDEDATE	OPT	NONE
A user-defined date that can be used for commitment purposes and is stored in the Lot Master table (F4108). Similar to Lot Expiration Date, User Lot Date 3 is a through date for commitment processing. The User Lot Date commitment option is available in the Commitment Date Method in the Item Branch table (F4102). The system uses the User Lot Date 3 Default Days from the Item Branch table (F4102) to calculate User Lot Date 3 when inventory first goes on hand.
jdUserLotDate4	U4DJ	JDEDATE	OPT	NONE
A user-defined date that can be used for commitment purposes and is stored in the Lot Master table (F4108). Similar to Lot Expiration Date, User Lot Date 4 is a through date for commitment processing. The User Lot Date commitment option is available in the Commitment Date Method in the Item Branch table (F4102). The system uses the User Lot Date 4 Default Days from the Item Branch table (F4102) to calculate User Lot Date 4 when inventory first goes on hand.
jdUserLotDate5	U5DJ	JDEDATE	OPT	NONE
A user-defined date that can be used for commitment purposes and is stored in the Lot Master table (F4108). Similar to Lot Expiration Date, User Lot Date 5 is a through date for commitment processing. The User Lot Date 5 commitment option is available in the Commitment Date Method in the Item Branch table (F4102). The system uses the User Lot Date 5 Default Days from the Item Branch table (F4102) to calculate User Lot Date 5 when inventory first goes on hand.
cUpdateEffectivityDate	EV01	char	OPT	NONE
An option that specifies the type of processing for an event.
cUpdateBestBeforeDate	EV02	char	OPT	NONE
An option that specifies the type of processing for an event.
cUpdateSellByDate	EV03	char	OPT	NONE
A radio button that specifies the level at which trace/track result is to be displayed. Select the Detail to display all transactions except IB, IX, and IZ types. Or, select Derivative Lots Only to display only those transactions that may have created new derivative lot.
cUpdateUserLotDate1	EV04	char	OPT	NONE
PeopleSoft event point processing flag 04.
cUpdateUserLotDate2	EV05	char	OPT	NONE
A flag that indicates whether automatic spell check is turned on.
cUpdateUserLotDate3	EV06	char	OPT	NONE
An option that specifies the type of processing for an event.
cUpdateUserLotDate4	EV07	char	OPT	NONE
An option that specifies the type of processing for an event.
cUpdateUserLotDate5	EV08	char	OPT	NONE
An option that specifies the type of processing for an event.

Related Functions

B9800100 Get Audit Information
X0005 Get User Defined Codes

Related Tables

F4108 Lot Master