Add Remove Items to LPN interface for JD Edwards

About the Add Remove Items to an LPN interface

The Add Remove Item to an LPN business function allows dcLINK to add or remove items from a license plate.

There are several action codes that control the processing of this NER. Depending on which action code is used, this NER can:

Create a new license plate that has no items associated with it
Create a new license plate and add an item to it
Add an item to an existing license plate
Remove an item from an existing license plate

Many of the “normal” dcLINK transactions like Inventory Adjustments and PO Receipts will automatically create license plates if their processing options are set accordingly. Use this function to override the “automatic” actions. This function allows the dcLINK user to pass in the name of the license plate, which overrides the automatic creation of LPN.

Name	Function name	Description
DD3N6L30		dcLINK Interface: Add/Remove Item to License Plate
ND3N6L30	dcLINKInterfaceAddRemoveLPN	dcLINK Interface: Add/Remove Item to License Plate

The full name of this interface is ND3N6L30 Add Remove Items to an LPN

This interface guide applies to the following JDE versions.

EnterpriseOne Xe and higher versions

Corresponding EnterpriseOne application

In EnterpriseOne, the application to run to assign/remove items to LPNs is P46L30 and can be accessed from menu G46L10.

Processing options

There are no processing options that are used to control the processing of this NER.

Input data structure

Input data structure for DD3N6L30 Add Remove Items to LPN.

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.
cActionType_ACTION		X	ACTION	Valid values are: 1 = Create an empty LPN only. 2 = Create LPN and add an item to it. 3 = Add item to an existing LPN. 4 = Remove item from LPN.
jdDateUpdated_UPMJ	Current Date	X	UPMJ	Retrieved from GetAuditInfo.
mnTimeUpdated_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	ND3N6L30	X	PID	Defaulted in program if not passed in.
szVersion_VERS		X	VERS	This program has no processing options.
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 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, than 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 in which the change was made is captured. dcLINK captures the script ID.
cCreateOrUseLP_EV01		R	EV01	Valid values are ‘N' for create and ‘E' for existing.
szBranchPlant_MCU		R	MCU	Valid branch/plant that is setup with license plating on must be passed in.
szUnknownItemNo_UITM		R	UITM	Item number of item being added to the LPN.
szLocation_LOCN		O, R	LOCN	The location is optional, but the location of the item must match the location of the license plate. When BF cActionType_ACTION = 1 for creating an Empty LPN, the location is required and cannot be blank.
szLot_LOTN		O	LOTN	If the item being added to the LPN is lot/serial number controlled, then this is the lot/serial number of that item.
mnPrimaryQuantity_PQOH		R	PQOH	There must be a quantity associated with the item being added.
mnDualQuantity_DQTY		O	DQTY	If the item being added to the LPN is a dual unit of measure item, then enter the dual quantity in this field.
szGuidTextMessage_TEXTMES		O	TEXTMES	This is a free form entry field.
szLicensePlateNumber_LPNU		R	LPNU	Child license plate number must always be passed in unless action code 1 is being used.
szLPContainerCode_EQTY		O	EQTY	Only used when adding a new parent LPN.
szLPStatusCode_LPSC		O	LPSC	Only used when adding a new parent LPN.
szLPReasonCode_LPNRC		O	LPNRC	Only used when adding a new parent LPN.
szLPXRefType_CRLPT		O	CRLPT	Only used when adding a new parent LPN.
szLPCrossReferenced_CRLPN		O	CRLPN	Only used when adding a new parent LPN.
mnLPGrossWidth_GWID		O	GWID	Can be used when adding a new parent or adding a child to an existing parent.
mnLPGrossDepth_GDEP		O	GDEP	Can be used when adding a new parent or adding a child to an existing parent.
mnLPGrossHeight_GHET		O	GHET	Can be used when adding a new parent or adding a child to an existing parent.
mnLPOverrideWeight_OVWER		O	OVWER	Can be used when adding a new parent or adding a child to an existing parent.

R = Required

X = Required but will default in if not passed

O = Optional

Verify the processing

Use the EnterpriseOne License Plate Workbench application on menu G46L10 to verify that the item/LPN transaction worked correctly.

To verify items were added to or removed from the LPN, complete the following steps in JDE.

On the G46L10 menu, open the License Plate Workbench menu.
Use this application to verify that the item/LPN transaction worked correctly.
Step Information
The license plate number shown should be what was generated by the system, or what you passed into the NER.

The location in which the LPN was created must match the location in which the item is found.

The container code will default in, but may be overridden.

The second screen shows the item information entered on the transaction: item number, location, lot, and quantity.

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	Create an Empty LPN	Create LPN and add an Item to it	Add item number to existing LPN	Remove item number from LPN
cdcLINKActionCode_EV01	0	0	0	0
cActionType_ACTION	1	2	3	4
jdDateUpdated_UPMJ
mnTimeUpdated_TDAY
szUserId_USER	Elvis	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
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
cCreateOrUseLP_EV01	N	N	E	E
szBranchPlant_MCU	W30	W30	W30	W30
szUnknownItemNo_UITM		VIT	VIT	VIT
szLocation_LOCN	R	. . .	. . .	. . .
szLot_LOTN		200603270001	200603270002	200603270002
mnPrimaryQuantity_PQOH		5	24	12
mnDualQuantity_DQTY
szGuidTextMessage_TEXTMES
szLicnesePlateNumber_LPNU	W3001405	W3001410	W3001405	W3001405
szLPContainerCode_EQTY
szLPStatusCode_LPSC
szLPReasonCode_LPNRC
szLPXRefType_CRLPT
szLPCrossReferenced_CRLPN
mnLPGrossWidth_GWID
mnLPGrossDepth_GDEP
mnLPGrossHeight_GHET
mnLPOverrideWeight_OVWER

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 entered 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.
424B	Enter Item Number and Transaction Qty. This error message can be generated if 1) the item number is null, or 2) the transaction quantity is null.
139LPN	Invalid Stocking Type for License Plates This message will be generated if the item number being put on the license plate has a stocking type of B (bulk) or X (outside process).
104LPN	Branch Plant required. The branch/plant cannot be blank on any transaction.
138T	Action Code Invalid. The action code used is not a valid action code for this BF.
031Q	Field Invalid. The create or use field is blank.
402B	Invalid License Plate Status Code. The status code used in the transaction was not found in 46L/SC.
402C	Invalid License Plate Reason Code. The reason code used in the transaction was not found in 46L/RC.
402D	Invalid Cross Referenced LPN Type. The cross referenced LPN type used in this transaction was not found in 46L/CR.
402G	Weight Exceeds Max. LP Weight. The weight of the license plate plus all its contents exceeds the max weight.
0002	Record Invalid. 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, dcLINK Utility Write Signature Capture Record, or anytime when another specific error message id has not been assigned to the EKEY value.
401T	License Plate Number does not exist. This error is returned when the child license plate is validated and no entry was found, or the parent license plate number is validated and it does not exist.
401S	License Plate Number Exists. The transaction is trying to create a new parent license plate, but the license plate number passed in on the transaction already exists.
0855	Quantity Invalid. This quantity error is returned if the quantity available in the Item Location (F41021) file is less than the quantity from the License Plate Detail (F46L11) file.
027Z	Item Location Record Not Found. No record exists in the F41021 file for the item number entered.
141LPN	License Plate Number – Location Error. This error is returned when Creating an Empty LPN (cActionType_ACTION = 1) and the szLocation_LOCN value is blank. A location value other than blank is required.
0003	Blanks Invalid. This error is returned when Creating an Empty LPN (cActionType_ACTION = 1) and the szLocation_LOCN value is blank. A location value other than blank is required.
3098	Invalid Location Format. This error is returned if an invalid location was entered as input.

Processing

This business function utilizes the action code (cActionType_ACTION and cdcLINKActionCode_EV01) to control processing.

A dcLINKAction code of 2 supports an update to the F46L10.LMCTUOM and LMEQTY, as a part of the build structure process. When there is a need to create an LPN, and there is no setup for the container code, the user will need to pass the value ‘2' in the dcLINKActionCode parameter, along with setting cActionType to equal ‘2'.

This business function utilizes the action code (cActionType_ACTION) to control processing.

Action code	Description
1	An action code of 1 creates a new empty LPN. It creates only one LPN at a time. The LPN will default most of it's setup, however it is possible to override values like the container code, cross-reference number, cross-reference type, status code, reason code, width, height, depth, and the override weight. The license plate number, if being supplied, needs to be passed in using the license plate field. It is valid to have the license plate system setup so that the LPN is auto generated, in which case nothing need be passed for a license plate number. Upon successful completion using this action code, a new license plate has been created in the location specified. No association between an item and a license plate takes place with this action code.
2	This action code will create a new LPN and add an item to it. The LPN must not exist prior to the first call. The item must exist. This action code would only be called once for each new LPN. Once this action is run the LPN is created and is no longer new, so action code 3 would be used to add additional items to the LPN. The same result could be accomplished by calling this NER twice, once with an action code of 1, and again with an action code of 3.
3	This action code will add an item to an LPN. Both the item and the LPN must already exist and be in the same location.
4	This action code will remove an item from an LPN. Both the item and LPN must have been previously setup in an item/LPN relationship.

Required fields

Branch/Plant: The BF will check to see if the branch/plant is setup for license plating. Valid values are branch/plants where license plating is turned on.
Action code: One of the valid action codes listed above (1, 2, 3 or 4) must be passed in. No value is defaulted.
Create or use license plate: This field tells the BF if you are creating a new license plate, or using an existing license plate. Valid values are ‘N' or ‘E'.
Item number: Unless the action code is equal to ‘1', an item number must be provided.
License plate: Every transaction this BF can perform requires a license plate. However, because the system can generate the license plate, it is not checked as a required field if the action code is equal to 1 or 2. Bear in mind though that if a client's system is not setup to generate a license plate number, and one is not sent up with an action code 1 or 2, the transaction will not work as expected.
Location: The location is required and must not be blank when an Empty LPN is created (cActionType_ACTION = 1). This validation was added to align the interface with the Standard JDE application process. Even when blank is a valid location on the EnterpriseOne system, this is not allowed. However, location is not required for the other action types: 2 - Create an LPN and add an item to it, 3 - Add an item to an LPN, 4 – Remove item from an LPN.

Optional fields

Container code: If a value is entered in the container code, then the value entered must be a valid container code for that branch/plant.
Status code: If a value is entered for status code, then that status code must exist in the UDC table 46L/SC.
Reason code: If a value for reason code is entered, then that reason code must exist in the UDC table 46L/RC.
Cross reference type: If a value for cross reference type is entered, then it must be a valid cross reference type that exists in the UDC table 46L/CR.

There was a problem loading this topic

Mobile Enterprise Platform