Maintain Seal Number interface for JD Edwards

About the Maintain Seal Numbers interface guide

The maintain seal numbers interface allows the user to enter/delete seal numbers put on a trailer.

The seal numbers can be recorded against either a load or a shipment. The dcLINK version is called ND3N9640. This interface was written in NER.

Normally, this would have been a “standalone” NER, but due to timing and cutoff constraints, this NER was added as a separate function under the Confirm Loads NER. It shares the data structure for confirm loads.

Name	Function name	Description
DD3N9640		dcLINK Interface – Confirm Loads
ND3N9640	dcLINKInterfaceMaintainSealNbrs	dcLINK Interface – Maintain Seal Numbers

Corresponding EnterpriseOne application

In EnterpriseOne, the application you would run to enter seal numbers is P49380, which is a form exit from both the confirm load application and the confirm shipment application. Both confirmation programs can be found on the menu G4911.

Processing options

There are no processing options associated with this NER.

Processing

This interface is used to record the seal number affixed to the trailer when it leaves the shipping dock.

The seal number can be recorded against a load or a shipment. A range of seal numbers can be issued for a single trailer. It is anticipated that while that trailer is in transit it will have to be opened and resealed.

If a single seal number is being recorded, then that value is passed into this interface. If a range of seal numbers are being used, then the “from” seal number and “to” seal number is passed in. This interface will start with the “from” number and loop, adding one to the seal number, and stopping when the seal number value is greater than the “to” seal number. Obviously in this case, the actual seal numbers used must be consecutive numbers between the “from” and “to” seal numbers.

This interface can be used to add seal numbers and delete seal numbers.

Required fields

The required fields for this NER depend on what action is being performed.

The action code field (cActionCode_ACTION) can be either an “A” for adding seals, or a “D” for deleting seals. The dcLINK action code can be “0” if a single seal number is being added to a load, a “1” if a seal range is being added to a load, a “2” if a single seal is being added to a shipment, or a “3” if a seal range is being added to a shipment.

If the seal number is being added to a load, then, in addition to the action codes, the load number, the planning depot, the load leg, the origin, and of course, the seal number(s) are all needed.

If the seal number is being added to a shipment, then, in addition to the action codes the planning depot, the shipment number, the origin, and the seal number(s) are required.

Verify the seal for loads

Verify seals were added to a load .

To verify that a seal was added to a load , complete the following steps in JDE.

Run the load confirmation program.
Select the form exit Seals.
In the EnterpriseOne app, review the seal numbers associated with the load.

Verify the seal for shipments

Verify seals were added to a shipment.

To verify a seal was added to a shipment, complete the following steps in JDE.

Run the shipment confirmation program.
Select the form exit Seals.
In the EnterpriseOne app, review the seal numbers associated with the shipment.

Input data structure

Input data structure for DD3N9640.

Name	Default values	Notes
Name	Default values	R/O	ALIAS
cdcLINKActionCode_EV01	0	X	EV01	‘0' if working with a single load number ‘1' if working with a range of seals for a load ‘2' if working with a single shipment number ‘3' if working with a range of seals for a shipment
cActionCode_ACTION	jNone	X	ACTION	‘A' if adding a seal number ‘D' if deleting a seal number
jdDateUpdated_UPMJ	Current Date	X	UPMJ	Retrieved from GetAuditInfo
mnTimeOfDay_TDAY	Current Time	X	TDAY	Retrieved from GetAuditInfo
szUserId_USER	Current User	X	USER	Retrieved from GetAuditInfo. If a value is passed into this field, it will be used to update CARDEX and any “last updated by” fields in tables.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N9642	X	PID	Defaulted in program if not passed in
szVersion_VERS		X	VERS	Not used in this NER
cSuppressErrMsg_EV01		O	EV01
cErrorCode_ERRC	Blanks	X	ERRC	Initialized to blanks in program
szErrorMessageKey_EKEY	Blanks	X	EKEY	Initialized to blanks in program
iDebugLevel_INT01		O	INT01	Displays M&D Debug statements if the value is greater than 0
mnLoadNumber_LDNM		F	LDNM	Identifies the load that the seal numbers are recorded against.
szPlanningDepot_LMCU		O	LMCU	Not used in this NER
mnLoadLeg_LNMB		O	LNMB	Identifies which leg of the load the seal number is used on.
jdActualShipDate_DTE		O	DTE	Not used in this NER
jdActualDeliveryDate_DTE		O	DTE	Not used in this NER
jdLoadConfirmDate_DTE		O	DTE	Not used in this NER
mnActualConfirmTime_TMEO		O	TMEO	Not used in this NER
mnActualShipTime_TMEO		O	TMCO	Not used in this NER
mnActualDeliveryTime_TMEO		O	TMEO	Not used in this NER
szTransShipConfirmVers_VERS		O	VERS	Not used in this NER
szRegistrationLicenseNo_RLNO		O	RLNO	Not used in this NER
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.
szExcessReasonCode_ETRSC		O	ETRSC	Not used in this NER.
szExcessResponseCode_ETRC		O	ETRC	Not used in this NER.
szExcessAuthorizationCode_AETC		O	AETC	Not used in this NER.
mnShipmentNumber_SHPN		R	SHPN	Required in order to find the shipment to update.
mnOrigin_ORGN		O	ORGN	Not used in this NER
szPrimaryVehicleId_PVEH		O	PVEH	Not used in this NER
mnFromSealNumber_SLN		O	SLN	Beginning seal number assigned to the trailer. If only one seal number is being assigned, use this field to report the seal number.
mnToSealNumber_SLN		O	SLN	Ending seal number assigned to the trailer.

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	Add a single seal to a load	Add a range of seals to a load	Add a single seal to a shipment	Add a range of seals to a shipment	Delete a seal from a shipment
cdcLINKActionCode_EV01	0	1	2	3	2
cActionCode_ACTION	A	A	A	A	D
jdDateUpdated_UPMJ
mnTimeOfDay_TDAY
szUserId_USER
szWorkStationId_JOBN
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS
cSuppressErrMsg_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
mnLoadNumber_LDNM	4	4
szPlanningDepot_LMCU	30	30	30	30	30
mnLoadLeg_LNMB	1	1
jdActualShipDate_DTE
jdActualDeliveryDate_DTE
jdLoadConfirmDate_DTE
mnActualConfirmTime_TMEO
mnActualShipTime_TMEO
mnActualDeliveryTime_TMEO
szTransShipConfirmVers_VERS
szRegistrationLicenseNo_RLNO
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES
szExcessReasonCode_ETRSC
szExcessResponseCode_ETRC
szExcessAuthorizationCode_AETC
mnShipmentNumber_SHPN			112	112	112
mnOrigin_ORGN	6031	6031	6031	6031	6031
szPrimaryVehicleId_PVEH
mnFromSealNumber_SLN	2	4	8	9	15
mnToSealNumber_SLN		6		11

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.
112Q	Seal Number not correct This error message is received if 1) the from seal number (mnFromSealNumber_SLN) was not passed in, or 2) the dcLINK action code is equal to “1” or “3” and the to seal number (mnToSealNumber_SLN) was not passed in.
112T	Seal Number not correct If the dcLINK action code is equal to “1” or “3”, and the “to” seal number is less than the “from” seal number.
113A	Load point invalid If the dcLINK action code is equal to “0” or “1”, and the load leg number (mnLoadLeg_LNMB) was not passed in.
138T	Action Code Invalid Two things can cause this error message. One, the action code (szActionCode_ACTION) is not equal to “A” or “D”. Two, the dcLINK action code (cdcLINKActionCode_EV01) is not equal to “0”, “1”, “2”, or “3”.
181B	Invalid Load/Shipment Number There are two causes for this error message. One, the dcLINK action code is equal to “0” or “1” and the load number (mnLoadNumber_LDNM) was not passed in. Two, the dcLINK action code is equal to “2” or “3” and the shipment number (mnShipmentNumber_SHPN) was not passed in.
4247	Invalid Depot The planning depot (szPlanningDepot_LMCU) does not contain a value.

There was a problem loading this topic

Mobile Enterprise Platform