Shipments Excess Charges interface for JD Edwards
About the Shipment Excess Charges interface guide
The excess charges interface allows the user to enter/edit the three excess transportation charge codes.
The excess charges interface allows the user to enter/edit the three excess transportation charge codes that can be associated with a shipment. Those charges codes are Reason Code, Responsibility Code, and Authorization Code. The dcLINK version is called ND3N9640. 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 Confirm Loads NER. It shares the data structure for confirm loads.
| Name | Function name | Description |
|---|---|---|
| DD3N9640 | dcLINK Interface – Confirm Loads | |
| ND3N9640 | dcLINKInterfaceExcessCharges | dcLINK Interface – Excess Charges |
Processing options
There are no processing options associated with this NER.
Corresponding EnterpriseOne application
In EnterpriseOne, the application you would run to record excess charges is P49642 which is a row exit from the confirm load application. The confirm load application can be accessed from the menu G4911.
Verify the process
Use the universal table browser to verify that the fields were changed in the F4215 file, or they can be verified online by using the load confirmation program, and inquiring on the excess charges by clicking on the row exit.
Processing
The purpose of this interface is to allow the recording of the three excess charges reason codes. These codes are used to justify additional charges on the shipment. For example, in the automotive industry a manufacturer may call a supplier and tell them the shipment needs to be expedited. The supplier can enter a reason code and authorization code to reflect the request.
All three of these reason codes can have a blank value. To allow the blanking out of a field that might have a value already in it, the percent sign (%) can be sent up in the field as a special character. The interface will interpret this as the field that should be blanked out. The percent sign needs to be left justified in the field.
The file being updated is the F4215, shipment header file.
To Map or not to Map? As a script builder, do you let the NER default in values or do you map those values in the API call in the script? The answer to that question really cuts to the heart of the readability and maintainability of the scripts.
It is very tempting to let the NER default as much as it needs to and to keep the script “clean”. The only problem with that approach is it hides from the user items that may need to be changed. For example, some interfaces may require a different action code depending on what is being done. By allowing the NER to default the action code it is not as observable to the person who has to edit the script that the action code needs to be changed.Required fields
Required fields for shipment numbers.
The required fields for this NER are the shipment number, and one of the following codes. Reason code, responsibility code, or authorization code. The reason code will be verified against the UDC table 49/ES. The responsibility code will be verified against the UDC table 49/EC.
Input data structure
Input data structure for DD3N9640.
| Name | Default values | Notes | ||
|---|---|---|---|---|
| R/O | Alias | |||
| cdcLINKActionCode_EV01 | 0 | X | EV01 | Always defaults to a 0. No different action takes place based on this code. |
| cActionCode_ACTION | 0 | X | ACTION | |
| jdDateUpdated_UPMJ | Current Date | X | UPMJ | Retrieved from GetAuditInfo |
| mnTimeOfDay_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 | ND3N9642 | X | PID | Defaulted in program if not passed in |
| szVersion_VERS | X | VERS | Not used in this NER | |
| cSuppressErrMsg_EV01 | O | EV01 | ||
| cErrorCode_ERRC | Blanks | 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 | |
| mnLoadNumber_LDNM | O | LDNM | Not used in this NER | |
| szPlanningDepot_LMCU | O | LMCU | Not used in this NER | |
| mnLoadLeg_LNMB | O | LNMB | Not used in this NER | |
| jdActualShipDate_DTE | O | DTE | Not used in this NER | |
| jdActualDeliveryDate_DTE | O | DTE | Not used in this NER | |
| jdLoadConfirmDate_DTE | O | DTE | Not used in this NER | |
| mnActualConfirmTime_TMEO | O | TMEO | Not used in this NER | |
| mnActualShipTime_TMEO | O | TMCO | Not used in this NER | |
| mnActualDeliveryTime_TMEO | O | TMEO | Not used in this NER | |
| szTransShipConfirmVers_VERS | O | VERS | Not used in this NER | |
| szRegistrationLicenseNo_RLNO | O | RLNO | Not used in this NER | |
| 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. | |
| szExcessReasonCode_ETRSC | R | ETRSC | One of these three fields is required. If the NER is called, and nothing is passed in all three fields, an error will be displayed. | |
| szExcessResponseCode_ETRC | R | ETRC | One of these three fields is required. If the NER is called, and nothing is passed in all three fields, an error will be displayed. | |
| szExcessAuthorizationCode_AETC | R | AETC | One of these three fields is required. If the NER is called, and nothing is passed in all three fields, an error will be displayed. | |
| mnShipmentNumber_SHPN | R | SHPN | Required in order to find the shipment to update. | |
| mnOrigin_ORGN | O | ORGN | Not used in this NER | |
| szPrimaryVehicleId_PVEH | O | PVEH | Not used in this NER | |
| mnFromSealNumber_SLN | O | SLN | Not used in this NER | |
| mnToSealNumber_SLN | O | SLN | Not used in this NER | |
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.
The data structure fields are in the left column, and the corresponding values for each scenario are listed by column.
| Field name | Add charges | Blank out a charge |
|---|---|---|
| cdcLINKActionCode_EV01 | 0 | 0 |
| cActionCode_ACTION | ||
| jdDateUpdated_UPMJ | ||
| mnTimeOfDay_TDAY | ||
| szUserId_USER | ||
| szWorkStationId_JOBN | ||
| mnJobNumber_JOBS | ||
| szProgramId_PID | ||
| szVersion_VERS | ||
| cSuppressErrMsg_EV01 | ||
| cErrorCode_ERRC | ||
| szErrorMessageKey_EKEY | ||
| iDebugLevel_INT01 | ||
| mnLoadNumber_LDNM | ||
| szPlanningDepot_LMCU | ||
| mnLoadLeg_LNMB | ||
| jdActualShipDate_DTE | ||
| jdActualDeliveryDate_DTE | ||
| jdLoadConfirmDate_DTE | ||
| mnActualConfirmTime_TMEO | ||
| mnActualShipTime_TMEO | ||
| mnActualDeliveryTime_TMEO | ||
| szTransShipConfirmVers_VERS | ||
| szRegistrationLicenseNo_RLNO | ||
| szGuidUniqueID_GUID | ||
| szGuidApprover1_USR1 | ||
| szGuidFullName1_FULLNAME1 | ||
| szGuidApprover2_USR2 | ||
| szGuidFullName2_FULLNAME2 | ||
| mnGuidReasonCode1_REASON1 | ||
| szGuidCommentField_COMMENTS | ||
| mnGuidReasonCode2_REASON2 | ||
| szGuidCommentField2_2COMMENTS | ||
| szGuidScriptID_FMNMVERS | ||
| szGuidTextMessage_TEXTMES | ||
| szExcessReasonCode_ETRSC | B | % |
| szExcessResponseCode_ETRC | X | |
| szExcessAuthorizationCode_AETC | George | |
| mnShipmentNumber_SHPN | 107502 | 107502 |
| mnOrigin_ORGN | ||
| szPrimaryVehicleId_PVEH | ||
| mnFromSealNumber_SLN | ||
| mnToSealNumber_SLN |
Common error messages
Common error messages for ND3N9640.
The following are common error messages that can be generated by this BF, and what those error messages mean.
| Error message | Meaning |
|---|---|
| 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. |
Loading...
There was a problem loading this topic