Transportation Load Build interface for JD Edwards
About the Transportation Load Build interface
You can use this interface to group a collection of shipments into a load.
Transportation Load Build is an interface used to group a collection of shipments into a load for the purpose of reducing costs and optimizing delivery routes. You may build a load using a common carrier or a private fleet.
In the enterprise system the application name is P4960. The dcLINK version is called ND3N496A. This interface was written in NER and calls a “C” business function BD3N4901 to retrieve the processing options.
| Name | Function name | Description |
|---|---|---|
| DD3N4960A |
dcLINK Interface Transportation Load Build |
|
| ND3N496A |
dcLINKLoadBuild |
dcLINK Interface Transportation Load Build |
| DD3N4901 |
PO Retrieval Work With Loads |
|
| BD3N4901 |
PORetrievalWorkWithLoads |
PO Retrieval Work With Loads |
The full name of this interface is ND3N0496A Transportation Load Build
This interface guide applies to the following JDE versions.
-
EnterpriseOne 8.10
Processing options
The DreamWriter defaults to ZJDE0001 if not otherwise specified in the parameter list on the call.
Defaults tab
-
Distance Unit of Measure (szPO_UOMDistance_UMD1): This processing option is used to specify the unit of measure for the distance that the load travels.
Shipment Apprv tab
-
Bypass the update of Order Next Status (cPO_BypassUpdtOrdrNxtStat_EV01): This processing option is used to specify whether the system bypasses the status update of an order. If the update order next status is bypassed, the system does not update the order to the next status code.
-
Override Order Next Status (szPO_OvrrideStatusCodeNxt_NXTR): This processing option is used to specify the value for an override next order status that the system uses when a shipment with sales orders is approved. This status must be a valid next status or other allowed next status. Valid values are order activity rules defined in the Order Activity Rules Program (P40204) for the document type being used. If you leave this option blank, the system determines the next status using order activity rules.
-
Warehouse request processing mode (cPO_WarehousPrcssingMode_EV01: This processing option is used for shipments with outbound sales orders. This processing option determines if the system needs to generate a pick request from the Warehouse system. Valid values are: blank = Do not generate, 1 = Generate requests only, 2 = Generate requests and process with the subsystem.
-
Version of Process Pick Request program (szPO_WarehousePickVersion_VERS): This processing option is used to generate warehouse management pick requests through the subsystem. You must specify the version, Print Pick Request (P46171), that is set up for subsystem processing.
-
Override Approved Shipment Status (szPO_ProtectedShipmntStat_PSPS): This processing option is used to specify the override approved shipment status to be used when a shipment is approved. Valid values are status codes in the transportation constants. If you leave this option blank, the system uses the approval status from the transportation constants.
-
Shipment status to be used when a load is unapproved (szPO_ShipmentStatusUnappr_SSTS): This processing option is used to specify the shipment status for an unapproved load.
-
Override Order Next Status for unapproved shipments containing sales orders (szPO_UnapprStatusCodeNext_NXTR): This processing option is used to enter the override Order Next Status to be used when a shipment containing sales orders is approved.
Processing option data structure DD3N4901
The interface retrieves these parameters by calling BD3N4901. They are passed back in the following data structure.
| Type | Description | Parameter |
|---|---|---|
| String |
szPO_Version_VERS |
Input |
| String |
szPO_CostCenterTrip_VMCU |
Output |
| Date |
jdPO_PromisedDeliveryDate_PDDJ |
Output |
| String |
szPO_ModeOfTransport_MOT |
Output |
| String |
szPO_FromLoadStatus_LDLS |
Output |
| String |
szPO_ToLoadStatus_LDLS |
Output |
| Char |
cPO_ShiftCode_SHFT |
Output |
| Char |
cPO_DispositionCodeBCS_DSCD |
Output |
| String |
szPO_LoadType_LDTY |
Output |
| String |
szPO_UOMDistance_UMD1 |
Output |
| Char |
cPO_BypassUpdtOrdrNxtStat_EV01 |
Output |
| String |
szPO_OvrrideStatusCodeNxt_NXTR |
Output |
| Char |
cPO_WarehousPrcssingMode_EV01 |
Output |
| String |
szPO_WarehousePickVersion_VERS |
Output |
| String |
szPO_ProtectedShipmntStat_PSPS |
Output |
| String |
szPO_ShipmentStatusUnappr_SSTS |
Output |
| String |
szPO_UnapprStatusCodeNext_NXTR |
Output |
| Char |
cPO_ReqireValidRMA_EV01 |
Output |
| Char |
cPO_BypassUpdtPurchasOrdr_EV01 |
Output |
| String |
szPO_OvrridePONxtStatAppr_NXTR |
Output |
| String |
szPO_UnapprovePONxtStatus_NXTR |
Output |
| String |
szPO_VersnWorkWithShpmnts_VERS |
Output |
| String |
szPO_VersionSelectShpmnts_VERS |
Output |
| String |
szPO_VersionDocumentPrint_VERS |
Output |
| String |
szPO_VersionLoadConfirm_VERS |
Output |
| String |
szPO_VersionDelivrConfirm_VERS |
Output |
| String |
szPO_VersionDisposition_VERS |
Output |
| String |
szPO_LoadTender_VERS |
Output |
| String |
szPO_LoadingNote_VERS |
Output |
| String |
szPO_PreferenceVersion_VERS |
Output |
| String |
szPO_InitialLoadStatus_LDLS |
Output |
| String |
szPO_PendingLoadStatus_LDLS |
Output |
| String |
szPO_ProtectedLoadStatus_LDLS |
Output |
| String |
szPO_OvrridNxtStatShipabl_NXTR |
Output |
| String |
szPO_OverrideNextStatus_NXTR |
Output |
| Char |
cPO_ShoppingCartMode_CART |
Output |
Processing
Processing information for the Transportation Load Build interface.
Processing
The characteristics of an item determine which fields are required by the interface. Some characteristics are set at the item master level, and some are set at the item/branch level. The item/branch level always takes precedence over the item master. Refer to the Special Processing Interface Usage Guide for more information.
Verify the processing
Transactions may be verified by confirming that the shipment(s) have an entry (entries) for the correct load (menu G4911).
Additional information
Additional information for Transportation Load Build interface.
Additional information
This interfaces gives the user functionality for adding shipments to loads through dcLINK® transactions instead of using the EnterpriseOne application. To process a Transportation Load Build transaction, the Planning Depot (szPlanningDepot_VMCU), the Shipment Number (mnOrderNumber_DOCO), and the Load Number (mnLoadNumber_LDNM) are required. It is important to note that the Load Number must have been created in EnterpriseOne prior to attempting to assign shipments to it. This interface will not create a load.
Besides the standard dcLINK parameters, the user may enter the Intermediate Destination (mnIntermediateDestination_ANID) parameter in addition to the above mentioned parameters.
The two parameters for weight and volume unit of measure are not used at this time.
Loading...
There was a problem loading this topic