AT-Shipment Confirmation interface for JD Edwards

About the AT-Shipment Confirmation Interface guide

AT-Shipment confirmation allows you to perform a transportation shipment confirmation.

The Advanced Transportation Shipment Confirmation interface is used to advance the status of a shipment in the transportation module and advance the sales order lines associated with that shipment. In the enterprise system the application name is P49645 and it is called from P4915. If a version of P49645 is created, there must be a corresponding version of the P4915 with the same name, and the P4915 version must have a value in the Protected Status parameter.

The dcLINK version is called ND3N4945. This interface was written in NER and calls a C business function BD3N4903 to retrieve the processing options.

The Advanced Inventory implementation of the Transportation Management Shipment Confirmation supports updating shipments in transportation, along with associated sales order lines. The enterprise system implementation also supports updating purchase orders, but that functionality is not supported in this release of ND3N4945.

Name	Function name	Description
DD3N49645		dcLINK Interface - Transportation Shipment Confirmation
ND3N4945	dcLINKTransportationShipmentConf	dcLINK Interface - Transportation Shipment Confirmation
DD3N4903		PO Retrieval - Transportation Shipment Confirmation
BD3N4903	TransportationShipmentConf	PO Retrieval - Transportation Shipment Conf.

This interface gives the user the ability to perform a transportation shipment confirmation, which can also perform a ship confirmation on each sales order line that has been added to the shipment. The only required input parameter is the shipment number (mnShipmentNumber_SHPN). The interface will update the shipment from the F4941 file using the shipment number passed in on the call.

This interface can perform what is called a “standalone” shipment confirmation, or a synchronized shipment confirmation. The standalone version only updates the status of the shipment being processed. The synchronized version updates the status of the shipment, and calls the Advanced Inventory Ship Confirmation business function (ND3N4205) to update all the sales order lines for the shipment. All of this is controlled by the processing option for the version number of P4205 (po_szP4205Version_VERS). If no version has been entered into this field, then this interface performs a standalone shipment confirmation. Otherwise, a synchronized version is performed.

When ND3N4205 is called, it will read the F4211 file selecting all records for which the shipment number in the F4211 record (stored in the commodity code field) is equal to the shipment number being processed. The ship confirmation performed here essentially amounts to a “blind” ship confirmation. That means that there is no opportunity to change the location, lot, quantity or anything else about each sales line. Any change to this information would have to have been done prior to this point using the pack confirmation process.

The input capable fields are: Mode of Transport (szModeOfTransport_MOT), Carrier (mnCarrier_CARS), Actual Shipment Date (jdActualShipmentDate_ADDJ), Actual Shipment Time (mnActualShipmentTime_ADTM), Delivery Date (jdDeliveryDate_DLDT), Override Weight (mnOverrideActWeight_WGTS), and Vehicle Registration (szVehicleRegistration_PRLO). These are all used by the master business function to update the shipment record.

Interface processing options

Processing options for the AT-Shipment Confirmation.

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

Process tab

Post Confirmation Form (cDisplayPostConf_EV01): This field is used by the enterprise system to control display of an extra window that allows the actual weight to be overridden after the confirmation has occurred. The Advanced Inventory implementation doesn't use this field for that purpose. The weight is part of the input data structure, and by virtue of mapping a value in that field the weight will be overridden.
Print Delivery Documents (cPrintDeliveryDocuments_EV02): This field is used by the enterprise system and Advanced Inventory to control the printing of delivery documents. Specifically, it is used to condition the call to the business function Initialize Document Print Batch Tables.
Display Delivery Document Selections (cDsplyDeliveryDocSelect_EV03): This field is used in the enterprise system to conditional a call to another application. Advanced Inventory does not support that application so this processing option value is ignored at this time.
Sales Order Status (szConfirmSOStatus_LTTR): This field represents the status code to which the F4211 record will be updated.
Credit Order Status (szCreditOrderStatus_NXTR): This field works the same way as the sales order status except this status code is used exclusively for credit orders.
Override Next Status (szOverrideShipmentStatus_SSTS): This field is used to update the status of the shipment record. The status entered in this field will become the next status of the shipment record.
Process Ship Confirmation (cProcessShipConfirmFlag_EV01): This field determines if the transaction will call dcLINK Shipment Confirmation NER.
UCC128 Shipment Edits (cProcessUCC128Flag_EV01): This field determines if the transaction will call the Edit Shipment for UCC128 function.

Versions tab

Delivery Print Version (szP49590Version_VERS): This field is used to specify the version number to be used when this program is called.
Ship Confirmation Version (szP4205Version_VERS: This field is used to specify the version number to be used when this program is called.
UCC128 Shipment Edits (szR42071Version_VERS: This field is used to specify the version number to be used when this program is called.

Interface processing option data structure DD3N4903

Process the option data structure of the AT-Shipment confirmation.

The interface retrieves these parameters by calling BD3N4903. They are passed back in the following data structure.

Type	Description	Parameter
String	szPOVersion_VERS	Input
Char	cDisplayPostConf_EV01	Output
Char	cPrintDeliveryDocuments_EV02	Output
Char	cDsplyDeliveryDocSelect_EV03	Output
String	szConfirmSOStatus_LTTR	Output
String	szCreditOrderStatus_NXTR	Output
String	szPurchaseOrderStatus_NXTR	Output
String	szOverrideShipmentStatus_SSTS	Output
Char	cFreightUpdateOption_EV01	Output
String	szP49590Version_VERS	Output
String	szP4205Version_VERS	Output
String	szP4312Version_VERS	Output
String	szR42071Version_VERS	Output
String	szR4981Version_VERS	Output
Char	cLaunchAdvShippingNotice_RASN	Output
String	szCartonNextStatus_CRSS	Output
Char	cCreateSalesOrderCharge_CSOC	Output
String	szVersionR47032_VERS	Output
String	szVersionP4210CartonQty_VERS	Output
String	szVersionP4210InvRelief_VERS	Output
String	szVersionP4210ItemQty_VERS	Output
Char	cProcessShipConfirmFlag_EV01	Output
Char	cProcessPOReceiptsFlag_EV01	Output
Char	cProcessUCC128Flag_EV01	Output
String	szR42500Version_VERS	Output

Processing

Processing AT-Shipment confirmation.

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 processong

Verification process for AT-Shipment confirmation.

Use the Confirm Shipments application (P4915) on the G4911 menu to inquire on the shipment number being processed. The values for the fields in the shipment record should reflect any changes made by you. The status code for the shipment should have been updated to the status code from the processing options.

Individual sales order lines can be reviewed using the sales order entry program (P4210) found on menu G4211. What you will be verifying is that the status of the sales order lines reflect the fact that they have been ship confirmed. Alternatively, using the Confirm Shipments application, highlighting a row and selecting the Details button should also give the sales order detail information.

Input data structure

The following table describes the input data structure for DD3N4945.

Name	Default values	Nnotes
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	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.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo.
mnJobnumber_JOBS		O	JOBS
szProgramId_PID	ND3N4945	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”.
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.
mnShipmentNumber_SHPN		R	SHPN	Used to retrieve the shipment that is being processed.
szModeOfTransport_MOT		O	MOT	This field can be used to override the mode of transport. If nothing is entered into this field, then the mode setup in the file is used.
mnCarrier_CARS		O	CARS	This field is used to override the carrier number. If nothing is entered, then the carrier number from the file will be used.
jdActualShipmentDate_ADDJ	Current Date	O	ADDJ	This field is used to override the actual shipment date.
mnActualShipmentTime_ADTM	Current Time	O	ADTM	This field is used to override the actual shipment time.
jdDeliveryDate_DLDT		O	DLDT	Delivery date is used to update the actual deliver date of the shipment.
mnOverrideActWeight_WGTS		O	WGTS	The actual weight field can be used to override the weight of the shipment. Note – even if this weight is overridden, it still must be in the tolerances setup in EnterpriseOne, or an error will be generated.
szVehicleRegistration_PRLO		O	PRLO	Not currently being used.
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

Additional information

Additional information for the AT-Shipment Confirmation interface.

There was a problem loading this topic

Mobile Enterprise Platform