Lot Date Revisions interface for JD Edwards

About the Lot Date Revisions interface

This interface allows updates to several lot date fields.

The lot date revisions interface allows updates to the new lot date fields that were introduced in the 8.9 release of EnterpriseOne. Specifically those lot dates are: lot expiration date, lot best before date, lot sell by date, lot effectivity date, user lot date 1, user lot date 2, user lot date 3, user lot date 4, and user lot date 5. In EnterpriseOne, these dates can be changed using P4108, lot master. The dcLINK version is called ND3N4109. This interface was written in NER and calls ‘C' business function, BD3N4109, to retrieve the processing options.

Name	Function name	Description
DD3N4109A		dcLINK Interface Lot Date Revisions
ND3N4109	dcLINKLotDateRevisions	dcLINK Interface Lot Date Revisions
DD3N4109		PO Retrieval Lot Master Revisions
BD3N4109	PORetrievalLotMasterRevisions	PO Retrieval Lot Master Revisions

The full name of this interface is ND3N4109 Lot Date Revisions

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 dates is P4108, lot master revisions, and then select the lot dates tab. P4108 can be accessed from the menu G4113.

Processing options

Processing options for Lot Date Revisions interface.

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.

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

Processing

The purpose of this interface is to change one or more of the dates associated with a lot.

The lot must be an existing lot in the lot master file (F4108). The dates that can be changed are the user lot dates 1 through 5, the lot expiration date, the lot effective date, the lot best before date, and the lot sell by date.

Required fields

The branch/plant, item number and lot number are required fields. The item number maybe passed in as either the short item number, or the second item number – either one will work.

This NER will use item number, branch/plant, and lot number, to read the lot master for the current lot date values. This interface calls a JDE business function to verify any changed dates are still in a valid range relative to the other lot dates. If there are no errors, then the lot master is updated.

Verify the processing

Use the lot master revision program in EnterpriseOne (P4108) to inquire on the lot number. Select the lot and then click on the lot dates tab. Check to make sure the date that was changed has the new value.

Input data structure

Input data structure for DD3N42040.

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.
szMachineKey_MKEY		X	MKEY
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N4109	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.
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 contain 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.
szBranchPlant_MCU		R	MCU	The branch/plant is part of the key in reading and updating the Lot Master file.
sz2ndItem_LITM		R	LITM	Either the second item number or the short item number must be entered. If the second item number is entered, it will be used to lookup the short item number.
mnShortItem_ITM		R	ITM	The short item number is used to read the Lot Master file. If this field is not entered, then the second item number must be entered.
szLot_LOTN		R	LOTN	The lot number must be entered in order to read or update the Lot Master file.
jdLotExpirationDate_MMEJ		O	MMEJ	All the date fields are listed as optional because you may change one or more of them.
jdBestBeforeDate_BBDJ		O	BBDJ	All the date fields are listed as optional because you may change one or more of them.
jdSellByDate_SBDJ		O	SBDJ	All the date fields are listed as optional because you may change one or more of them.
jdLotEffectivityDate_DLEJ		O	DLEJ	All the date fields are listed as optional because you may change one or more of them.
jdUserLotDate1_U1DJ		O	U1DJ	All the date fields are listed as optional because you may change one or more of them.
jdUserLotDate2_U2DJ		O	U2DJ	All the date fields are listed as optional because you may change one or more of them.
jdUserLotDate3_U3DJ		O	U3DJ	All the date fields are listed as optional because you may change one or more of them.
jdUserLotDate4_U4DJ		O	U4DJ	All the date fields are listed as optional because you may change one or more of them.
jdUserLotDate5_U5DJ		O	U5DJ	All the date fields are listed as optional because you may change one or more of them.

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	Update sell by date using short item #	Update best before date using 2nd item #
cdcLINKActionCode_EV01	0	0
cActionCode_ACTION
jdDateUpdated_UPMJ
mnTimeUpdated_UPMT
szUserId_USER
szWorkStationId_JOBN
szMachineKey_MKEY
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS
cSuppressErrorMessage_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES
szBranchPlant_MCU	30	30
sz2ndItem_LITM		4100
mnShortItem_ITM	60661
szLot_LOTN	20599	20600
jdLotExpirationDate_MMEJ
jdBestBeforeDate_BBDJ		10/14/06
jdSellByDate_SBDJ	09/25/06
jdLotEffectivityDate_DLEJ
jdUserLotDate1_U1DJ
jdUserLotDate2_U2DJ
jdUserLotDate3_U3DJ
jdUserLotDate4_U4DJ
jdUserLotDate5_U5DJ

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. In the context of this BF, this error is returned when an error has been detected from one of these three business functions: dcLINK Set User ID, dcLINK Utility Set Audit Info, or dcLINK Utility Write Signature Capture Record. This message is also generated if the read of the lot master fails. The lot master is read using the branch/plant, lot number, and short item number.
004G	Item Number Invalid. This error message can be generated for any of the following reasons: Neither a short item nor a second item number was passed into this business function. A short item number as passed in but it failed validation. A second item number was passed in but it failed validation. Both item numbers were passed in but they are for two different items.
0964	Branch/Plant Invalid. No branch/plant was passed into this business function.
2745	Lot/Serial Number Must be Entered. No lot number was passed into this business function.

There was a problem loading this topic

Mobile Enterprise Platform