Add Remove Parent Child LPNs interface for JD Edwards

About the Add Remove Parent Child LPNs interface

The Add Remove Parent Child LPNs business function allows dcLINK to add child license plates to parent license plates.

This interface also allows the removal of child license plates from parent license plates.

Name	Function name	Description
DD3N6L31		dcLINK Interface: Add Remove Parent/Child LPN
ND3N6L31	dcLINKInterfaceParentChildLPN	dcLINK Interface: Maintain Parent/Child LPNs

The full name of this interface is ND3N6L31 Add Remove Parent Child LPNs

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 add/remove child LPNs from a parent LPN is P46L31, and can be accessed from the menu G46L10.

Processing options

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

Processing

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

Action code	Description
1	An action code of 1 creates a new LPN. It creates only one LPN at a time. The LPN will default most of its setup, however you can override values such as 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 parent license plate field. It is valid to have the license plate system set up so 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 is created in the location specified. No association between child and parent takes place with this action code.
2	This action code will create a new parent LPN and then add a child LPN to the parent. The parent LPN must not exist prior to the first call. The child LPN must exist. This action code would only be called once for each new parent. Once this action is run, the parent is created and it is no longer new, so action code 3 would be used to add additional children to the parent. 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 a child LPN to a parent LPN. Both child and parent must be existing license plates.
4	This action code will remove a child LPN from a parent LPN. Both child and parent must be existing license plates that have been previously setup in a parent/child 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'.
Child license plate:

Unless the action code is equal to ‘1' a child license plate must be provided.
Parent license plate: Every transaction this BF can perform requires a parent 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. However, 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 may not work as expected.
Location: The location is not required assuming a blank location is valid on the EnterpriseOne system that you are working on. Note that this BF will allow the location to be blank. Most clients do not allow a blank location (where is a blank location when you are standing in a warehouse?). What it will not allow is for the location of the child license plate to be different from the location of the parent license plate. They must be the same.

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.

Verify the processing

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

To verify that the parent/child transaction worked correctly, complete the following steps in JDE.

On the G46L10 menu, open the License Plate Workbench menu.
Use this application to verify that the parent/child transaction worked correctly.
Step Information
Enter the parent LPN or the child LPN to find the license plate.

Use the Find Child LP button or Find Parent LP button to find the parent/child that is missing.

Input data structure

Input data structure for DDeN6L31, Add Remove Parent Child LPNs

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		X	ACTION	Valid values are: 1 = Create parent LPN only. 2 = Create parent LPN and add child LPN. 3 = Add child LPN to an existing parent LPN. 4 = Remove child LPN from parent 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	ND3N6L31	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, 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 capture. 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.
szLocation_LOCN		O	LOCN	The location is optional, but the location of the parent license plate must match the location of the child license plate.
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.
szParentLN_PLPNU		X	PLPNU	Parent license plate number. Every transaction requires a parent number – depending on how the EnterpriseOne system is setup, it may auto generate on adds.
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

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.

Field name	Add parent LPN only	Add child LPN to new parent LPN	Add child LPN to existing LPN	Remove child LPN from parent LPN
cdcLINKActionCode_EV01	0	0	0	0
cActionCode_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	E	E	E
szBranchPlant_MCU	W30	W30	W30	W30
szLocation_LOCN	. . .	. . .	. . .	. . .
szGuidTextMessage_TEXTMES
szLicnesePlateNumber_LPNU		010055	010060	010065
szParentLN_PLPNU	P0001		P0001	P0001
szLPContainerCode_EQTY	PAL1	PAL1
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.


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.
103LPN	Parent License Plant Number: Invalid A blank parent license plate number was sent in on a transaction with an action code of 3 or 4. Or, the parent license plate location is not the same as the child license plate location.
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.
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.
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.
402F	Invalid Child License Plate. If the parent license plate number that is passed in is the same number as the child license plate number passed in, this message will be displayed.
402G	Weight Exceeds Max. LP Weight. The cumulative weight of all the items on the LP exceeds the maximum weight limit.

There was a problem loading this topic

Mobile Enterprise Platform