Lot Status Update interface for JD Edwards

About the Lot Status Update interface

This function is used to update the Item Location file.

This NER has two functions that perform similar but different functions. Both functions update a lot status code. One updates the lot status in the Item Location file (F41021) and the other updates the lot status code in the Lot Master file (F4108). This usage guide covers the updating of the Item Location file. The dcLINK NER that is called is ND3N4108. This interface was written in NER and calls ‘C' business function, BD3N4109, to retrieve the processing options.

Name	Function name	Description
DD3N4108C		dcLINK Interface Lot Status Update
ND3N4108	dcLINKLotStatusUpdate	dcLINK Interface Lot Master Revisions
DD3N4109		PO Retrieval Lot Master Revisions
BD3N4109	PORetrievalLotMasterRevisions	PO Retrieval Lot Master Revisions

The full name of this interface is ND3N4108 Lot Status Update

This interface guide applies to the following JDE versions.

EnterpriseOne Xe through 9.1

Corresponding EnterpriseOne application

In EnterpriseOne, the application you would run to change the lot status is P4108, lot master revisions. P4108 can be accessed from the menu G4113.

Verify the processing

Both CARDEX and summary availability will reflect a lot status change to the item location file.

Processing

This business function will change the lot status in the Item Location file, F41021.

This business function will only change one item/location/lot entry at a time. That means if the lot number existed in more than one location, this business function would have to be called once for each location in order to change all the entries for that lot number.

Required fields

The branch/plant, item number and lot number are required fields. The location is not required, but will default to blanks if nothing is passed in, which may or may not be desired.

This NER will use item number, branch/plant, location, and lot number to read the item location file for the current lot status, and to check to see if there is any quantity available. If the omit zero quantities flag (cOmitZeroQuantities_OMIT0) is on, and the quantity on hand is equal to a zero, an error is generated. Likewise, if the quantity on hand is less than zero, or the quantity available is less than zero, an error is generated

Processing options

Processing options for Lot Status Update.

The dream writer version will default to ZJDE0001 if not otherwise specified in the parameter list on the call. This interface calls BD3N4109 to get the lot master processing options, but at this time none of the retrieved processing options are used in this business function. Only one of the processing options is used by this NER.

Update lot status: This processing option is a flag that is either on (1) or off (0 or blank). If this is set to a “1”, then no one is allowed to update the lot status. This NER checks this processing option, and if it is set to a ‘1', no updating is performed.

Processing option data structure for DD3N4109

Our interface retrieves these parameters by calling BD3N4109 and is passed back in the following data structure.

Type	Description	Parameter
String	szPOVersion_VERS	Input
Char	cPO_DisableLotStatUpdate_EV02	Output
Char	cPO_DisableLotGradeUpdate_EV03	Output
Char	cPO_DisableLotPotnUpdate_EV04	Output
String	szPO_GradeDocType_DCTO	Output
String	szPO_PotencyDocType_DCT	Output
Char	cDisplayPercentofLife_DSPLY	Output
Char	cDisplayNumberofDays_DSPLY	Output
Date	jdCalculationDate_CLCJ	Output
Char	cMassUpdateOfLotDates_EV01	Output

Input data structure

Input data structure for DD3N4108C.

Name	Default value	R/O	Alias	Notes
cdcLINKActionCode_EV01	0	X	EV01	Always defaults to a 0. No different action takes place based on this code.
cActionCode_ACTION	0	X	ACTION
jdDateUpdated_UPMJ	Current Date	X	UPMJ	Retrieved from GetAuditInfo.
mnTimeUpdated_UPMT	Current Time	X	UPMT	Retrieved from GetAuditInfo.
szUserId_USER	Current User	X	USER	Retrieved from GetAuditInfo.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo.
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N4108	X	PID	Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	X	VERS	Defaulted in program if not passed in.
cSuppressErrorMessage_EV01		O	EV01
cErrorCode_ERRC	Blanks	X	ERRC	Defaulted in program.
szErrorMessageKey_EKEY	Blanks	X	EKEY	Defaulted in program.
iDebugLevel_INT01		O	INT01	Displays M&D Debug statements if the value is greater than 0.
szBranchPlant_MCU		R	MCU	The branch/plant is part of the key in reading and updating the Item Location file.
szItemNoUnknownFormat_UITM		R	UITM	This NER needs the short item number to read several files. It derives the short item number from the unknown item number passed in this field.
szLocation_LOCN		O	LOCN	If this is not entered it will default to blanks, which may or may not be the desired action.
szLot_LOTN		R	LOTN	The lot number must be entered in order to read or update the Item Location file.
cNewLotStatusCode_LOTS		R	LOTS	This is the new status that the lot will be updated to.
szStatusChangeReason_STRCD		O	STRCD	This reason code is passed into the business function that will create the Cardex entry.
cOmitZeroQuantities_OMIT0		O	OMIT0	If this field is equal to ‘1', then an error will be generated if the quantity on hand for this branch/plant, item, location, and lot are not unique.
szGuidUniqueID_GUID	Automatically generated by dcLINK	O	CFRGUID	If generate GUIDs is turned on in the dcLINK configuration utility, this field will contain a GUID (guaranteed unique identifier). The GUID is used to tie database changes in PeopleSoft to the transactions that triggered those changes to occur.
szGuidApprover1_USR1		O, R	USR1	An entry in this field or the Approver 2 field will cause a signature capture record to be written. Signature capture records are part of the GUID processing and should not be used unless a GUID is being created by dcLINK. The value of this field is a User ID, not an address book entry. There must be a value passed in to either this field or the approver 2 field, otherwise it is an error.
szGuidFullName1_FULLNAME1		O	FULLNAME1	This field is the full name of the GUID Approver 1.
szGuidApprover2_USR2		O, R	USR2	GUID processing supports up to two approvers. If two approvers are required, this is the User ID of the second approver. There must be a value passed in to either this field, or the approver 1 field, otherwise it is an error.
szGuidFullName2_FULLNAME2		O	FULLNAME2	This field is the full name of the GUID Approver 2.
mnGuidReasonCode1_REASON1		O, R	REASON1	If either of the approver fields contains a value, but no value is entered into one of the reason code fields, then an error will be returned. Reason codes must match the valid reason codes setup for GUID processing, otherwise it is an error.
szGuidCommentField_COMMENTS		O	COMMENTS	This is a free form entry field that is used to further explain the reason code entered into the previous field.
mnGuidReasonCode2_REASON2		O, R	REASON2	If either of the approver fields contains a value, but no value is entered into one of the reason code fields, then an error will be returned. Reason codes must match the valid reason codes setup for GUID processing, otherwise it is an error.
szGuidCommentField2_2COMMENTS		O	2COMMENTS	This is a free form entry field that is used to further explain the reason code entered in the previous field.
szGuidScriptID_FMNMVERS		O	FMNMVERS	In PeopleSoft the screen ID where the change was made is captured. dcLINK captures the script ID.
szGuidTextMessage_TEXTMES		O	TEXTMES	This is a free form entry field.

R = Required

X = Required but will default in if not passed

O = Optional

Transaction test scenarios

The following test scenarios demonstrate a variety of ways in which this interface could be used, and the fields that would be passed for each scenario.

The data structure fields are in the left column, and the corresponding values for each scenario are listed by column.

Field name	Placing a lot on hold	Removing a lot on hold
cdcLINKActionCode_EV01	0	0
cActionCode_ACTION
jdDateUpdated_UPMJ
mnTimeUpdated_UPMT
szUserId_USER
szWorkStationId_JOBN
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS
cSuppressErrorMessage_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
szBranchPlant_MCU	30	30
szItemNoUnknownFormat_UITM	4100	4100
szLocation_LOCN	. .	. .
szLot_LOTN	200572	200572
cNewLotStatusCode_LOTS	D
szStatusChangeReason_STRCD
cOmitZeroQuantities_OMIT0
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES

Common error messages

The following are common error messages that can be generated by this BF, and what those error messages mean.

Error message	Meaning
0002	Record Invalid. This error message can be generated under several different scenarios. One, the item location file is read with the branch/plant, item, location, and lot number as the key. If no record is found this error message is returned. Two, the omit zero quantities flag is on, and the quantity on hand in the item location file is equal to zero. Three, the quantity on hand in the item location file is less than zero. Four, the quantity available in the item location file is less than zero.
022N	Lot does not exist in the Lot Master. The F4108 was read and no record was found that matched this combination of lot number, branch/plant, and item number.
0267	Item Number Invalid. If no item number is passed to this business function, this error message will be returned.
0964	Branch/Plant Invalid. No branch/plant was passed into this business function.
4299	Invalid Processing Option. This is the message returned when this interface is called, but the processing option is set to not allow updating of the lot status.

There was a problem loading this topic

Mobile Enterprise Platform