Unusable Label Number interface for JD Edwards
About the Unusable Label Numbers Interface guide
Maintains entries in the unusable label file.
The unusable label number interface allows users to maintain entries in the unusable label file (F4622). This is done using three action codes. The dcLINK version is called ND3N4620. This interface was written in NER.
Normally, this would have been a “standalone” NER, but due to timing and cutoff constraints, this NER was added as a separate function under the Carton Reorganization NER.
| Name | Function Name | Description |
|---|---|---|
| DD3N4622 | dcLINK Interface DS – Unused Labels | |
| ND3N4620 | dcLINKInterfaceUnusableLabelNumb | dcLINK Interface – Unusable Label Numbers |
Processing options
There are no processing options associated with this NER.
Corresponding EnterpriseOne app
In EnterpriseOne, the application you would run to record unusable labels is P4622 which can be accessed from the menu G4615.
Required field
The required fields are the branch/plant and label serial number. These two fields are the key to the unusable label file.
Verifying the processing
The easiest way to verify the transaction worked is to use the E1 application on menu G4615. The file can be inquired upon, and the record displayed to verify all the entered fields show up.
Processing
The purpose of this interface is to allow the recording of label serial numbers that will not be used.
An EnterpriseOne process will use this information to pass along to a trading partner so they know why they are not receiving consecutive label numbers. Three dcLINKAcitonCodes control how this interface maintains the unusable label number file.
| Action code | Description |
|---|---|
| 0 | Tells the interface to write the information passed up to the file. This would be used to setup an initial unused label record. Reason codes can be supplied to identify why the label could not be used. The label maybe damaged, the carton the label is on maybe damaged, etc. Any value sent up in the reason code field will be validated against the UDC table 46/UL, so only predefined reason codes can be sent. A container code may be sent up as well to identify the type of container the unusable label is on. This field is also validated against a UDC table (46/EQ), so only predefined containers can be used. If an item number is passed up it must be a valid item number from the item master. The shipment number is not validated. |
| 1 | Allows the information on an existing record in the file to be changed. The fields that can be changed are: the reason code, the container code, the shipment number, the customer carton ID, and the container item number. The same editing is done against the same UDC tables. |
| 9 | Removes an entry from the unusable label file. |
Input data structure DD3N4620
Input data for unusable level numbers.
| Name | Default value | Notes | ||
|---|---|---|---|---|
| R/O | Alias | |||
| cdcLINKActionCode_EV01 | 0 | X | EV01 | Valid action codes are as follows. 0 – create an unusable label entry 1 – Update an existing unusable label entry 9 – Delete an existing unusable label entry |
| cActionCode_ACTION | X | ACTION | ||
| 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. If a value is passed into this field that value will be used to update CARDEX and any “last updated by” fields in tables. |
| szWorkStationId_JOBN | Current Workstation | X | JOBN | Retrieved from GetAuditInfo |
| mnJobNumber_JOBS | O | JOBS | ||
| szProgramId_PID | ND3N4620 | X | PID | Defaulted in program if not passed in |
| szVersion_VERS | X | VERS | Not used in this NER | |
| cSuppressErrMsg_EV01 | O | EV01 | ||
| cErrorCode_ERRC | 0 | X | ERRC | Initialized to blanks in program |
| szErrorMessageKey_EKEY | Blanks | X | EKEY | Initialized to blanks in program |
| iDebugLevel_INT01 | O | INT01 | Displays M&D Debug statements if the value is greater than 0 | |
| szBranchPlant_MCU | R | MCU | The branch /plant. | |
| szLabelSerial_LBLSN | R | LBLSN | This is the label serial number. | |
| szszLabelDataId_LDTAI | O | LDTAI | Not used in this NER | |
| szReasonCode_ULBLRC | O | ULBLRC | This is the reason code that identifies why the label can't be used. If entered, it is validated against the UDC table 46/UL. | |
| szContainerCode_EQTY | O | EQTY | This is the container code associated with this label. If this is entered, it is validated against the UDC table 46/EQ | |
| mnShipmentNumber_SHPN | O | SHPN | The shipment number the label was associated with. | |
| szszCustomerCartonId_CEQT | O | CEQT | The customer carton ID. | |
| szContainerItemNumber_UITM | O | UITM | If this field is not blank, then it is validated against the Item Master file. The short item number is returned, and this is what is used in the Unusable Label Number file (F4622). | |
R = Required
X = Required but will default in if not passed
O = Optional
Transaction test scenarios
Transaction test scenarios for unusable level numbers.
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 | Add a label | Update a label | Delete a label |
|---|---|---|---|
| cdcLINKActionCode_EV01 | 0 | 1 | 9 |
| cActionCode_ACTION | |||
| jdDateUpdated_UPMJ | |||
| mnTimeUpdated_TDAY | |||
| szUserId_USER | |||
| szWorkStationId_JOBN | |||
| mnJobNumber_JOBS | |||
| szProgramId_PID | |||
| szVersion_VERS | |||
| cSuppressErrMsg_EV01 | |||
| cErrorCode_ERRC | |||
| szErrorMessageKey_EKEY | |||
| iDebugLevel_INT01 | |||
| szBranchPlant_MCU | 27 | 27 | 27 |
| szLabelSerial_LBLSN | 4235 | 4235 | 4235 |
| szszLabelDataId_LDTAI | A | ||
| szReasonCode_ULBLRC | DMG | ||
| szContainerCode_EQTY | BOX1 | BOX2 | |
| mnShipmentNumber_SHPN | 1533 | ||
| szszCustomerCartonId_CEQT | |||
| szContainerItemNumber_UITM | 2440 | 2440 | 2440 |
Common error messages
Common error messages for unusable level numbers.
The following are common error messages that can be generated by this BF, and what those error messages mean.
| Error message | Meaning |
|---|---|
| 0001 | Action Invalid: This error message is returned if the action code is not equal to a ‘0', ‘1', or ‘9'. |
| 0002 | Record Invalid: The record invalid error message can be returned on either an update or a delete, if the record being updated or deleted does not exists in the unusable label number file (F4622). |
| 013G | Delete Unsuccessful: The action code called for a delete of an unusable label record, but the delete failed. |
| 013H | Update Unsuccessful: The action code called for an update, but an error was returned from the update to the unusable label number file. |
| 017E | Insert Unsuccessful: The action code called for an insert and an insert was attempted but it did not work. |
| 0267 | Item Number Invalid: The item number entered was not found in the Item Master table (F4101). |
| 073P | Duplicate Keys not allowed: The action code called for an insert, but there is already another record in the file with this same branch/plant and label serial number. |
| 4750 | Required Field: This error message returned is either the branch/plant, or the label serial number is left empty. |
Loading...
There was a problem loading this topic