Detail LPN Count Entry interface for JD Edwards
About the Detail LPN Count Entry interface
The Detail LPN Count Entry business function allows dcLINK to update the LPN detail count, which is the row exit in Cycle Count and Tag Count that allows the user to allocate the cycle/tag count amount to the various license plates that make up that count.
| Name | Function name | Description |
|---|---|---|
| DD3N6L42 | dcLINK Interface Detail LPN Count Entry | |
| ND3N6L42 | dcLINKInterfaceDetailLPNCount | dcLINK Interface: Detail LPN Count Entry |
The full name of this interface is ND3N6L42 Detail LPN Count Entry
This interface guide applies to the following JDE versions.
-
EnterpriseOne Xe through 9.1
Corresponding EnterpriseOne application
In EnterpriseOne, the application you can run to spread a cycle/tag count across license plates is P46L42.This application can only be called from the cycle count application (P4141), or the tag count entry application (P41604).
In each of these applications the LPN Detail Entry is a row exit option. The row exit is grayed out unless the item selected has license plates to be counted. The license plates that are displayed when P46L42 is run are preloaded when the Select Items for Cycle /Tag Count UBEs are run.
Processing options
There are no processing options that are used to control the processing of this NER.
Processing
This business function allows dcLINK to update the LPN detail count.
Required Fields
-
The branch/plant must be supplied. It does not need to be right justified.
-
The item number that is being counted must be supplied.
-
The location and lot number must be supplied if the location being counted is not a blank location.
-
If the item number is under lot/serial number control, then the lot/serial number must be entered.
-
The cycle count number must be entered if the dcLINKActionCode is equal to ‘0'.
-
The tag count number must be supplied if the the dcLINKActionCode is equal to ‘1'.
-
The license plate is a required field.
-
The total quantity that will be used to build the license plate(s) must be entered.
Optional fields
The lot and location are optional assuming a blank location is a valid location, and not a lot or serial number controlled item.
Action codes
The dcLINKActionCode is used to tell this interface which other interface (Cycle Count Entry or Tag Count Entry) this NER is being used in conjunction with.
-
A value of ‘0' tells it cycle count entry is being used and the field CycleCountNumber_CYNO becomes a required field.
-
A value of ‘1' says tag count entry is being processed and it makes the field TagCountNumber_TGG required.
The field cActionCode_ACTION is used to control how the quantity counted is processed.
-
An ‘A' in this field tells this interface to accumulate, add the value reported on the transaction to the amount already in the F46L42 file.
-
A value of ‘R' tells this interface to replace the value that is in the F46L42 file with the transaction value.
Verify the processing
Use the EnterpriseOne cycle count entry program (P4141) or the tag count entry program (P41604) to verify.
To verify the processing, use one of the following options in JDE.
-
Use the cycle count entry program (P4141), or the tag count entry program (P41604) and inquire on the item being counted.
-
Optional. As this interface (ND3N6L42) updates the License Plate Cycle and Tag Count file (F46L42), you can use UBE to verify that file was updated.
Input data structure
Input data structure for DD3N6L42 Detail LPN Count Entry.
| Name | Default value | R/O | Alias | Notes |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 |
0 |
X |
EV01 |
0 = A cycle count transaction is being processed. 1 = A tag count transaction is being processed. |
| cActionCode_ACTION |
A |
X |
ACTION |
A = Accumulate the quantity entered to whatever value is already in the F46L42 file. R = Replace the quantity in the F46L42 file with the value on this transaction. |
| 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 |
ND3N6L42 |
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 captured. dcLINK captures the script ID. |
|
| szGuidTextMessage_TEXTMES |
O |
TEXTMES |
This is a free form entry field. |
|
| szBranchPlant_MCU |
R |
MCU |
Valid branch/plant that is setup with license plating on must be passed in. |
|
| szUnknownItemNo_UITM |
R |
UITM |
The item number must be entered. |
|
| szLocation_LOCNE1 |
O |
LOCNE1 |
The location is optional but if it is not entered it will default to blank – which may or may not be a valid default. |
|
| szLot_LOTN |
O |
LOTN |
The lot is optional unless the item is a lot controlled item, in which case the lot needs to be supplied. |
|
| mnCycleCountNumber_CYNO |
O |
CYNO |
This field is required if the dcLINKActionCode is equal to ‘0'. |
|
| mnTagCountNumber_TGG |
O |
TGG |
This field is required if the dcLINKActionCode is equal to ‘1'. |
|
| szLicnesePlateNumber_LPNU |
R |
LPNU |
This field not used by the interface. |
|
| mnQtyCounted_TQCT |
R |
TQCT |
This field is the amount of the item on the license plate being counted. |
|
| mnDualQtyCounted_SQOR |
O |
SQOR |
This field is only used on dual unit of measure items and is the amount of the item on the license plate being counted. |
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 | Cycle count replace count | Cycle count accum. count | Tag count accum. count | Tag count replace count |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 |
0 |
0 |
1 |
1 |
| cActionCode_ACTION |
R |
A |
A |
R |
| 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 |
||||
| szGuidTextMessage_TEXTMES |
||||
| szBranchPlant_MCU |
W30 |
W30 |
W30 |
W30 |
| szUnknownItemNo_UITM |
VIT |
VIT |
VIT |
VIT |
| szLocation_LOCNE1 |
. . . |
. . . |
. . . |
. . . |
| szLot_LOTN |
200602210006 |
200602210006 |
200602210006 |
200602210006 |
| mnCycleCountNumber_CYNO |
926 |
926 |
||
| mnTagCountNumber_TGG |
11 |
10 |
||
| szLicnesePlateNumber_LPNU |
W30011845 |
W30011845 |
W30011845 |
W30011845 |
| mnQtyCounted_TQCT |
30 |
27 |
30 |
27 |
| mnDualQtyCounted_SQOR |
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 |
|---|---|
| 424B |
Enter Item Number and Transaction Qty. In this NER this means the item number is blank or null. |
| 4750 |
Required Field. This error will be generated if the dcLINKActionCode is ‘0' and the cycle count number is blank/null, or the dcLINKActionCode is ‘1' and the tag count number is blank/null. |
| 101LPN |
License Plate Number: Blank. The license plate number is blank or null. |
| 104LPN |
Branch Plant required. The branch/plant cannot be blank on any transaction. |
| 46L8 |
LPN Detail Entry Quantity Invalid. The quantity counted is blank or null. |
| 096N |
Record not found. The fetch to the F46L42 file using cycle count/tag count, item number, branch/plant, location, lot, and license plate number resulted in no records found. |
| 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. |
| 132LPN |
Location Error. If this error is returned from this NER it means a null location was trying to be processed. The location cannot be null. |
| 144LPN |
Branch Plant: Error The branch/plant does not have license plating turned on. |
Loading...
There was a problem loading this topic