Load Approval interface for JD Edwards

About Load Approval interface guide

The Load Approval interface is used to advance the status of a load from pending to approved.

The Load Approval interface is used to advance the status of a load from a status of “20 - Pending” to “30 - Load Approved”. In the enterprise system the application name is P4960. The dcLINK version is called ND3N4960. The ND3N4960 interface was written in NER and calls a “C” business function BD3N4901 to retrieve the processing options. The EnterpriseOne MBF Load approval is called within the ND3N4960 function and will process the load to update all of the necessary files.

Name	Function name	Description
ND3N4960	dcLINKAdvancedTransMngmnt	Load Approval
DD3N4960		Load Approval
DD3N4901		PO Retrieval - Work with Loads
BD3N4901	PORetrievalWorkWithLoads	PO Retrieval - Work with Loads

The Transportation Management System requires that the sales orders used have an order type of “S4” - a sales order for transportation. The load approval interface requires that a sales order with the Last Status of “520” and Next Status of “527” be used. Shipments that are included on a load should have a status of “10” - pending. Loads that are waiting to be approved should be at a status of “20” - pending.

This dcLINK interface for Load Approval requires the user to enter the Planning Depot and Load Number field values for a created load. The combination of the two fields is what makes each record unique. The status of the load should be “20 - Pending”. When the function gets called, it will validate the load and depot that were entered and return any errors. If the status is greater than “20”, then the function will return an error to the user that the load is protected and is unable to be changed.

If the load is valid, then the status should change to “30 - Load Approved”, the Shipment Status should change from “10 - pending” to “25 - approve”, and the sales Order Next Status should have changed from “527” to “560,” and the Last Status from “520” to “527”. The EnterpriseOne MBF Approve Load (N4901150) that is called in dcLINK Interface Load Approval (ND3N4960) should update all of the necessary files.

Processing options

Processing options for the load approval.

The DreamWriter defaults to ZJDE0001 if not otherwise specified in the parameter list on the call.

Defaults tab

Distance Unit of Measure for Stop Sequence Form (szPO_UOMDistance_UMD1): This field is the unit of measure that the distance traveled should be measured with for the load.

Ship appry tab

Bypass Update of Order Next Status for shipment with sales order (cPO_BypassUpdtOrdrNxtStat_EV01): This should be left blank, so that the Order Next status is not bypassed when a shipment containing a sales order is approved.
Override Order Next Status used for shipment with approved sales orders (szPO_OverrideStatusCodeNxt_NXTR): This should be set at “560” for the Override Order Next Status used for shipments containing approved sales orders.
Warehouse Processing Mode (cPO_WarehousPrcssingMode_EV01): This should be left blank so that there are no picks for warehouse request processing mode for shipments containing outbound sales orders.
Version of Process Pick Request (szPO_WarehousePickVersion_VERS): If version is left blank, then ZJDE0001 will default in as the version.
Protected Shipment Status (szPO_ProtectedShipmntStat_PSPS): This field is left blank and the Approval Status from the Transportation Constants will be used.
Shipment Status Unapproved (szPO_ShipmentStatusUnappr_SSTS): Shipment status of “10” is to be used when a load is unapproved.
Override Order Next Status for unapproved shipments with sales order (szPO_UnapprStatusCodeNext_NXTR): This field overrides Order Next Status for unapproved shipments containing sales orders.
Required Valid RMA (cPO_ReqireValidRMA_EV01): This is a flag set for RMA(Returned Materials Authorization).
Bypass Update of Order Next Status for shipment with purchase order (cPO_BypassUpdtPurchasOrdr_EV01): This flag is set to bypass the update of Order Next Status when a shipment containing a purchase order is approved.
Override Order Next Status used for shipment with approved purchase orders (szPO_OverridePONextStatus_NXTR): The override Order Next Status that is used when a shipment containing purchase orders is approved.
Override Order Next Status for unapproved shipments with purchase order (szPO_UnapprovePONextStat_NXTR): This field overrides the Order Next Status for unapproved shipments containing purchase orders.

Process tab

Initial Load Status (szPO_InitialLoadStatus_ LDLS): This field is used to specify the initial status of a load - it should be set at “10”.
Pending Load Status (szPO_PendingLoadStatus_LDLS: This field is used to specify the current load status - it should be set at “20”.
Protected Load Status (szPO_ProtectedLoadStatus_LDLS: This status is used as the protected status only if this status number is smaller than Approved Load Status in Transportation Constants - it should be set at “28”.
Override Next Status for shippable lines created by a split (szPO_OverridNxtStatShipabl_NXTR: Leave blank, and the next status from the original line will be used to specify the override next status for shippable lines created by a split shipment.
Next Status for backordered lines created by a split (szPO_OverrideNextStatus_NXTR: This field is used to specify the next status code for backordered lines that are created by a split shipment.

Processing option data structure DD3N4901

Processing option data structure for load approval.

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_OverridePONxtStatAppr_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 a load approval.

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

To verify that the approve load actually changed the status of the load use the EnterpriseOne Load Build application (P4960) located on menu G4911.

To verify the load approval, complete the following steps.

From the Work with Loads screen, highlight the row with the planning depot and load number used.

Step Information

Note:The Load Status Number and Description should be “30 - Load Approved”.
At the top of the screen, select the Select button. This opens the Load Detail - Shipments screen.
Highlight the grid row for each shipment.
Select the Shipment Details button from the row exit menu ensure the status of the shipment changed to “25”.
Verify that the Next and Last status for the sales order has been changed, go to the EnterpriseOne app Sales Order Detail (P4210) on menu G4211.
On the Customer Service Inquiry screen, use the filter fields to find and highlight the grid row for the sales order used.
Press the select button at the top of the screen.
Review the Next Status and Last Status in the grid.

Input data structure DD3N4960

The input data structure for load approval.

Name	Default values	Notes
Name	Default values	R/O	Alias
cdcLINKActionCode_EV01	0	X	EV01	Always defaults to a “0”. No different action takes place based on this code.
cActionCode_ACTION	1	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
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N4960	X	PID	Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	X	VERS	Defaulted in program if not passed in.
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”.
szPlanningDepor_VMCU		R	VMCU	Identifies the location of the load.
mnLoadNumber_LDNM		R	LDNM	A number that was assigned using next number to a planning depot when the load is built that makes it unique.
Globally Unique Identifier (GUID) Fields	GUID values are all optional unless a business must comply with FDA 21 CFR Part 11 auditing requirements. Refer to Special Processing Interface Usage Guide for GUID Input Data Structure details.

R = Required

O = Optional

X = Required but will default in if not passed

C = Conditional

There was a problem loading this topic

Mobile Enterprise Platform