LPN Status Update interface for JD Edwards
About the LPN Status Update interface
The LPN Status Update business function allows dcLINK to change the status of a license plate after it has been created.
This allows companies to use the status code to attach some significance to the license plate. For example, 10 might be the status code for a newly created license plate. 80 might be used to designate that the license plate is empty.
Keep in mind that this is a visual help for users. Changing a status code does not imply that the system has any edits built in to “honor” the status code.
For example, if a client used status 30 to designate the license plate was in quarantine, the license plate system doesn't do anything with status codes, so that has no meaning to the software.
There are several action codes that control the processing of this NER.
| Name | Function name | Description |
|---|---|---|
| DD3N6L70 |
dcLINK Interface: LPN Status Update |
|
| ND3N6L70 |
dcLINKInterfaceLPNStatusUpdate |
dcLINK Interface: LPN Status Update |
The full name of this interface is ND3N6L70 LPN Status Update
This interface guide applies to the following JDE versions.
-
EnterpriseOne Xe through 9.1
Corresponding EnterpriseOne application
EnterpriseOne has no corresponding application. When a license plate is created, the user can specify the status code. This is validated against the UDC table 46L/SC. As long as the status code is found in the table it is considered valid.
Processing options
There are no processing options that are used to control the processing of this NER.
Processing
The dcLINK action code can have four different values. If nothing is passed into the dcLINK action code then ‘0' is defaulted.
The action codes and their meanings are as follows.
| Action code | Description |
|---|---|
| 0 |
An action code of ‘0' tells this interface to update the license plate's status with the value passed in the field szLPStatusCode_LPSC. This field is validated against the UDC table 46L/SC, so the value being passed in must be a valid value or an error will be generated. |
| 1 |
This action code is exactly like action code ‘0' except, in addition to the status code being changed, it will also write a history record to the F46L99 history file. If you want to write a history record you must supply a transaction type (szLPTransactionType_LPTT). This is a predefined value that is stored in the UDC table 46L/TT. EnterpriseOne has a supplied value of ‘LPMNT' (license plate maintenance) that was used in testing, but you can easily setup one like ‘LPSTS' for license plate status if you prefer. |
| 2 |
This action code expects the license plate number passed in is a parent license plate number. It will change the parent LPN to the new status and change all of its direct children. It will not change its children's children. That would require a separate call. This action code does not write the history file. |
| 3 |
This action code works exactly like action code ‘2' but in addition to changing the status code it also writes a history record (like action code ‘1'). |
| 2 |
Dispose of a quantity. |
Required fields
The following fields are required.
-
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.
-
dcLINK Action Code: One of the valid action codes listed above (0, 1, 2, or 3) must be passed in. A ‘0' will default if nothing is passed.
-
License Plate: The license plate cannot be empty. The value entered will be validated against the license plate master file (F46L10).
-
Status Code: The status code must be entered and will be validated against 46L/SC.
-
Transaction Type: If the dcLINK action code is equal to ‘1' or ‘3' then this field must be supplied.
-
Sending Blanks: The valid values for status code and transaction type both include blanks. dcLINK has trouble distinguishing blanks from nulls. To get around this problem send the special characters %#% in either the status code or the transaction type. This tells this interface use blanks. However, blanks must still be setup in the UDC tables as valid values otherwise the interface will still generate an error when it validates.
Verify the processing
You can use EnterpriseOne applications to verify that the transaction worked correctly.
To verify the processing, complete the following steps in JDE.
-
Use the license plate workbench (P46L10) application to view the status number of individual license plates.
-
Inquire upon the license plate processed to display the status code. This will show the value passed through if the transaction was successful.
-
Use the license plate history application to view the history transactions for each license plate. The transaction will display the license plate number, the transaction type sent with the transaction, and the new license plate status.
Input data structure
Input data structure for DD3N6L70 LPN Status Update.
| Name | Default value | R/O | Alias | Notes |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 |
0 |
R |
EV01 |
Valid values are: 0 = Change status code on LPN. 1 = Change status code on LPN and write history. 2 = Change status on parent and direct children. 3 =Change status on parent and direct children plus write history. |
| cActionType_ACTION |
X |
ACTION |
Not used in this NER. |
|
| 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 |
ND3N6L70 |
X |
PID |
Defaulted in program if not passed in. |
| szVersion_VERS |
X |
VERS |
Not used. |
|
| 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. |
|
| szLicnesePlateNumber_LPNU |
R |
LPNU |
The license plate number must always be passed in. If the dcLINK action code is a ‘2' or ‘3' then this is a parent license plate number. |
|
| szLPStatusCode_LPSC |
R |
LPSC |
Must be supplied and must be a valid value in the UDC table 46L/SC. |
|
| szLPTransactionType_LPTT |
O |
LPTT |
Must be a valid value in the UDC table 46L/TT. |
X = Required but will default in
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 | Change status code | Change status code plus write history | Change parent & children status | Change parent & children status plus write to history |
|---|---|---|---|---|
| cdcLINKActionCode_EV01 |
0 |
1 |
2 |
3 |
| cActionType_ACTION |
||||
| 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 |
| szLicnesePlateNumber_LPNU |
W30012060 |
W30012060 |
W30012050 |
W30012050 |
| szLPStatusCode_LPSC |
20 |
10 |
20 |
10 |
| szLPTransactionType_LPTT |
LPMNT |
LPMNT |
Common error messages
The following are common error messages that can be generated by this BF, and what those error messages mean.
| 104LPN |
Branch Plant required. The branch/plant cannot be blank on any transaction. |
| 144LPN |
Branch Plant: Error. The branch/plant entered does not have license plating turned on. |
| 101LPN |
License Plate Number: Blank The license plate number is blank or null. |
| 402B |
Invalid License Plate Status Code The status code used in the transaction was not found in 46L/SC. |
| 0159 |
Blank Field Invalid. This error is generated when the transaction type is blank and the dcLINK action code is equal to a ‘1' or a ‘3'. |
| 0621 |
Value Invalid. This error is returned when the program tries to validate the transaction type that is passed in and no entry is found in the UDC table 46L/TT. |
| 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. |
| 118LPN |
LP Master F46L10: Read Failed. The license plate number passed in was not found in the license plate master file (F46L10). |
| 119LPN |
LP Master F46L10: Update Failed. The update of the license plate master file with the new status code failed. |
| 159U |
Write Failed. The write to the history file (F46L99) failed. |
Loading...
There was a problem loading this topic