send feedback

❮ Previous Next ❯

LPN Workbench interface for JD Edwards

About the LPN Workbench interface

The LPN Workbench interface allows Advanced Inventory to issue entire license plates, transfer entire license plates, or delete empty license plates.

This functionality exists in EnterpriseOne in the application License Plate Workbench.

Name	Function name	Description
DD3N6L10		dcLINK Interface: LPN Workbench
ND3N6L10	dcLINKInterfaceIssueTransfer	dcLINK Interface: LPN Workbench
DD3N6L01		PO Retrieval: LPN Workbench
BD3N6L01	PORetrieveLPNWorkbench	PO Retrieval: LPN Workbench

The full name of this interface is ND3N6L10 LPN Workbench

This interface guide applies to the following JDE versions.

EnterpriseOne Xe through 9.1

Corresponding EnterpriseOne application

In EnterpriseOne, the application to run to issue an entire license plate, transfer an entire license plate or delete an empty license plate is P46L10 and can be accessed from the menu G46L10.

The license plate workbench is also the main inquiry tool available to review license plates and their contents. Throughout the license plate usage guides the user is directed back to the license plate workbench to verify that the license plate was created properly, the item was added to the license plate, etc.

Processing options

The dream writer version will default to ZJDE0001 if not otherwise specified in the parameter list on the call. This interface will also retrieve processing options for inventory issues and inventory transfers, depending on the action code used with this program.

In each case the interface retrieves the document type that is defined in the processing options for these two transactions. If the document type is not passed in on the call to this interface, it will default to one of the document types retrieved from either the issues processing options, or the transfers processing options.

Security tab

Status and Reason Code Security: In terms of LPN Issues, Transfers, or deleting a LPN, this processing option does not apply. None of these transactions allow for changing status codes.
Inventory Issue: This processing option doesn't apply to dcLINK. In the EnterpriseOne application the ability to issue the full license plate can be turned off, which makes sense because there are other uses for the application. Since the business function would only be used to issue (we don't have the inquiry part that the E1 application does) full license plates, there would be no reason to even call this function if this processing option is disabled. Inventory Transfer: This processing option doesn't apply to dcLINK. In the EnterpriseOne application the ability to transfer the full license plate can be turned off, which makes sense because there are other uses for the application. Since the business function would only be used to transfer (we don't have the inquiry part that the E1 application does) full license plates, there would be no reason to even call this function if this processing option is disabled.

Version tab

Inventory Issue (P4112): This is the version number of the processing options for inventory issues that will be used by ND3N6L10 to get the document type that is used when this business function issues material.
Inventory Transfer (P4113): This is the version number of the processing options for inventory transfers that will be used by ND3N6L10 to get the document type that is used when this business function transfers material.

Processing option data structure: DD3N46L01

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

Type	Description	Parameter
String	szPOVersion_VERS	Input
Char	cStatusSecurity_EV01	Output
Char	cFullInvIssue_EV01	Output
Char	cFullInvTransfer_EV01	Output
String	szInvIssuesVersion_VERS	Output
String	szInvTransferVersion_VERS	Output

Processing

This interface can be used to issue and entire license plate, transfer an entire license plate, or delete a license plate..

Three different action code (cActionCode_ACTION) values are used to control processing. A value of ‘I' tells this interface to issue the entire license plate. A value of ‘T' tells the interface to transfer the entire license plate. A value of ‘D' tells the interface to delete the license plate.

Required fields

The action code will default to an ‘I' if nothing is entered, but for all intents and purposes this field should be treated as a required field. If the action code is equal to a ‘T' (transfer), then the “to” branch/plant is required. The “to” location isn't required, assuming a blank location is valid (the default if left blank). The action code is required for both transactions (remember it can default from the processing options), as is the license plate number.

Optional fields

The reason code, if entered, will be validated against the UDC table 42/RC so if a reason code is passed up it must be a valid reason code. It is valid to have a blank reason code. If the intention is truly to have blanks for the reason code, then pass up the special characters of %#%. This NER will translate that into blanks and pass them into the appropriate business function. Transaction date and G/L date will default to today's date if not entered. The explanation is also an optional field.

Verify the processing

You can verify the processing using the license plate workbench using two different methods.

To verify processing, complete the following steps in JDE.

There are two main places to go to verify processing. Select one of the following options.
Step Information
Use the license plate workbench in EnterpriseOne to verify that the license plate was transferred to a different location and/or branch/plant. In the case of issues, use the same program to verify that the license plate no longer has any items on it. In the case of a deletion, use the license plate workbench to verify the license plate is no longer in the system.

Use CARDEX to verify the processing of transactions that are performing transfers and issues. What displays in CARDEX are the standard entries for an item that is being transferred or issued. The document type will most likely be the IT for transfers, or the II for the issues. If anything was passed in for the explanation or reason code it should show up on the ‘explanation' screen in CARDEX.

Input data structure

Input data structure for LPN Workbench DD3N6L10.

Name	Default value	R/O	Alias	Notes
cdcLINKActionCode_EV01	0	x	EV01	Not used.
cActionCode_ACTION	I	x	ACTION	I: Issue an entire license plate. T: Transfer an entire license plate. D: Delete a license plate.
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.
szWorkStationId_JOBN	Current Workstation	x	JOBN	Retrieved from GetAuditInfo.
mnJobNumber_JOBS		o	JOBS
szProgramId_PID	ND3N6L10	x	PID	Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	x	VERS	Defaulted in program if not passed in.
cSuppressErrMsg_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 as a user ID, not an address book entry. There must be a value passed in to either this field, or to 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.
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.
szLicensePlateNumber_LPNU		r	LPNU	This is the license plate number that is to be issued, transferred, or deleted.
szToBranchPlant_MCU		o	MCU	If a license plate is being transferred, this indicates the branch/plant to which the license plate is being transferred.
szToLocation_LOCN		o	LOCN	If a license plate is being transferred, this represents the location to which the license plate is being transferred.
szDocumentType_DCT		r	DCT	The document type is required for issues and transfers. It may come from processing option, so it doesn't have to be entered. But if the processing option doesn't have it defined, then this NER will generate an error.
jdTransactionDate_TRDJ		o	TRDJ	If nothing is entered, the transaction date will default to today's date. This is used only for issues and transfers.
jdGLDate_DGL		o	DGL	If nothing is entered here, the G/L date will default to today's date. This is used only for issues and transfers.
szExplanation_TREX		o	TREX	The explanation is used for issues and transfers. If nothing is entered, each transaction has a default explanation supplied by the MBF.
szReasonCode_RCD		o	RCD	The reason code is used for issues and transfers.
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.

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	Transfer a license plate	Issue a license plate	Delete a license plate
cdcLINKActionCode_EV01
cActionCode_ACTION	T	I	D
jdDateUpdated_UPMJ
mnTimeOfDay_TDAY
szUserId_USER	Elvis	Elvis	Elvis
szWorkStationId_JOBN
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS
cSuppressErrMsg_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES
szLicensePlateNumber_LPNU	014505	200601090001	20060109001
szToBranchPlant_MCU	W30
szToLocation_LOCN	2.A.2
szDocumentType_DCT
jdTransactionDate_TRDJ
jdGLDate_DGL
szExplanation_TREX
szReasonCode_RCD		OVR
mnGuidReasonCode2_REASON2

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
144LPN	Branch Plant: Error. The branch /plant does not have license plating turned on.
460U	Invalid license plate number. A blank child license plate was sent up on a transaction other than action code 1.
104LPN	Branch Plant: Required. The branch/plant is equal to blanks or nulls.
143LPN	License Plate: Transfer Error. The license plate being transferred has commitments, or one of its children has commitments.
104LPN	Branch Plant required. The branch/plant cannot be blank on any transaction.
4641	Document Type is required. The document type was not entered, and a document type was not retrieved from the processing options.
402C	Invalid License Plate Reason Code. The reason code used in the transaction was not found in 46L/RC.
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.

There was a problem loading this topic

Mobile Enterprise Platform