Shipment Confirmation interface for JD Edwards

About the dcLINK Shipment Confirmation interface

The ship confirmation interface is commonly used as either a ship confirmation that advances the status of a sales order to reflect good being shipped or as a pack confirmation that allows sales order lines to be split when an order is being packed into cartons.

In the enterprise system, the application name is P4205. The dcLINK version is called ND3N4205. This interface was written in NER and calls a “C” business function BD3N4201 to retrieve the processing options.

Name	Function Name	Description
DD3N4205		dcLINK Interface - Shipment Confirmation
ND3N4205	dcLINKShipmentConfirmation	dcLINK Interface - Shipment Confirmation
DD3N4201		PO Retrieval - Shipment Confirmation
BD3N4201	PORetrievalShipmentConfirmation	PO Retrieval - Shipment Confirmation

This guide applies to the newest version of the ERP.

Processing option data structure

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

Type	Description	Parameter
String	szVerison_VERS	Input
String	szStatusNextFrom_NXTR	Output
String	szStatusNextThru_NXT2	Output
String	szDefaultOrderType_DCTO	Output
String	szLineTypeNewLine_LNTY	Output
String	szStatusNextConfirmed_NXTEV1	Output
String	szStatusNextAddLine_NXTEV2	Output
String	szStatusNextBO_NXTEV3	Output
String	szAllowAddLineEntry_VL01	Output
String	szDisplayKitLines_VL02	Output
String	szDisplayTextLines_VL03	Output
String	szErrorItemLoc_VL05	Output
String	szPreloadOption_VL06	Output
String	szCheckAvailabiltiy_VL07	Output
String	szPreventNegativeShip_VL08	Output
String	szPreventOvership_VL09	Output
String	szOverrideLT_VL10	Output
String	szOverrideSHAN_VL11	Output
String	szCallFrieghtProgram_VL13	Output
String	szOverrideFreight_VL14	Output
String	szAutoPrintInvoice_VL15	Output
String	szSOEVersion_VL16	Output
String	szPackConfirm_VL17	Output
String	szR42565Vers_VL18	Output
String	szTestResultsVersion_VER	Output
String	szCertificateAnalyFlag_SVL	Output
String	szCertificateAnalyVersion_VER2	Output
Char	cAgreementBPFlag_EV09	Output
Char	cAgreementSearchFlag_EV08	Output
String	szAgreementDestination_MCU	Output
String	szTypeTransaction_TYTN	Output
Char	cOutboundUBERun_EV10	Output
String	szVersionConsolidated_VER	Output
Char	cBulkTransactionVolFlag_EV01	Output
String	szR4210ICVersion_SVL	Output
Char	cCreateItercompanyOrder_EV01	Output
Char	cAllowReliefOfInventory_EV01	Output
Char	cCertificateOfAnalysisSub_EV01	Output
Char	cReevaluateQualityTests_EV01	Output
Char	cPrepaymentProcessing_EV01	Output
String	szAuthorizedPPayTransVers_VERS	Output
String	szSettlePPayTransVers_VERS	Output
String	szAuthorizeHoldPPayProc_HOLD	Output
String	szSettleHoldPPayProc_HOLD	Output
String	szAuthLinesnextStatus_NXTR	Output
String	szSettledLInesNextStatus_NXTR	Output
Char	cProcessAuthorization_EV02	Output
Char	cProcessSettlement_EV02	Output
Char	cCallR45100Mode_EV01	Output
String	szR45100Version_VL01	Output
Char	cBOorCANRemains_EV01	Output
Char	cR42950SubmitUpdate_EV01	Output
Char	cSADWarningError_EV01	Output
Char	cNewLotsForCO_EV01	Output
Char	cUse_Next_Order_Status_UNOP	Output
String	szR42950Version_VL02	Output
String	szP4620Version_VL01	Output
String	szMinimumCartonStatus_CRSS	Output
Char	cReconcileCartonShipment_RCSD	Output
String	szLotGroup_LOTGRP	Output
Char	cIntransitAccounting_EV01	Output
String	szP4312Version_VERS	Output

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.

Verifying the processing

The desired result of performing a ship confirmation is the advancement of the sales order line to the correct next status. That next status may come from the order activity rules, or it may be overridden from a processing option. Optionally, you may see a sales order line get split if the quantity being confirmed is less than the quantity that was ordered.

If the processing option is set to relieve inventory, then you will also see an entry in CARDEX for the amount that was confirmed, plus the summary availability on hand quantity will decrease by the amount confirmed.

Input data structure

The following table describes the input data structure for DD3N4220.

Name	Default Values	R/O	Alias	Notes
cdcLINKActionCode_EV01	0	X	EV01	“0” = Edit Line, End Doc, Clear Cache. “3” = Edit Line. “4” = Edit Line and End Doc. “5” = End Doc. “A” = Process all lines for an order number. “B” = Process all lines for a pick slip number. “C” = Process all lines for a Shipment number. “D” = Process configured item line and components. “Z” = process multiple items to multi locations using work file FD3N2053. “M” = process all items stored in FD3N2053 for the shipment.
cActionCode_ACTION	C	X	ACTION	Defaults to a “C” if not sent in on the call.
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	ND3N4240	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"
mnOrderNo_DOCO		C	DOCO	This is a key field and is required if the dcLINK action code is less than “A”. This is a key field and is required if the dcLINK action code is “Z” or “M”.
szOrderType_DCTO	Processing Options	X	DCTO	If this field is not sent up, it will be defaulted from the processing options. This field is used to read the F4211 file when the dcLINK Action Code is less than or equal to “A”. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
mnLineNo_LNID		O	LNID	This field can be used to identify the F4211 record to be selected for processing. This is the surest way of identifying the correct line and will be used over the Unknown Item Number (szItemNoUnknownFormat_UITM), even if both are sent up. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
mnShipQty_SOQS		O	SOQS	The quantity entered into this field will be the quantity that this NER tries to ship confirm.
mnCancelQty_SOCN		O	SOCN	The quantity entered into this field will be the quantity that this NER uses to cancel from the original line.
mnBackOrderQty_SOBK		O	SOBK	The quantity entered into this field will be the quantity that this NER uses to back order from the original line.
szOrderCo_KCOO		O	KCOO
szBranchPlant_MCU		O	MCU	This is a key field and is required if the dcLINK action codes is “Z” or “M”.
szLocation_LOCN		O	LOCN	Send in the location only if you want to override the value setup on the sales detail line. Note: If you want to change the Commitment, then you must use multi-location. Simply overriding the location will not relieve the commitment.
szLotNo_LOTN		O	LOTN	Send in the lot only if you want to override the value setup on the sales detail line. Note: If you want to change the Commitment, then you must use multi-location. Simply overriding the lot will not relieve the commitment.
szDescription_DSC1		O	DSC1
szLineType_LNTY		O	LNTY
mnCarrier_CARS		O	CARS	Send in the carrier number only if you want to override the value setup on the sales order.
szContainerID_CNID		O	CNID	Send in the container ID only if you want to override the value setup on the sales order.
jdActualShipDate_ADDJ	Today's Date	X	ADDJ	Defaults to current date if not sent up.
szItemNoUnknownFormat_UITM		O	UITM	This field can be used to identify the F4211 record to be selected for processing. This business function will only look at this field if the Line Number (mnLineNo_LNID) is blank or null. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
cCMRecordWrittenToCache_EV04		O	EV04
cWriteRecordIfWarning_EV08		O	EV08
cModeProcessing_MODE			MODE
mnPickSlipNumber_PSN		O	PSN	If the dcLINK Action Code is equal to a “B”, then this field must hold the value of the pick slip number to be processed.
cSyncEndDoc_EV01		O	EV01	If called from Advanced Transportation, this field will contain a “1”. Otherwise it should always be blank.
mnTransJobnmumber_JOBS		O	JOBS	Gets passed in if called from Advanced Transportation.
cBTNSelectLocation_EV01	Blank or “1”	O	EV01	This field replaces the button click that occurs in EnterpriseOne. To kick off Multi-Location processing, set this field to a “1”. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
szSLIssueBranchPlant_MCU		M	MCU	If doing Multi-location processing, this is the override Branch/Plant. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
szSLIssueLocation_LOCN		M	LOCN	If doing Multi-location processing, this is the override Location. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
szSLIssueLot_LOTN		M	LOTN	If doing Multi-location processing, this is the override Lot Number. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
mnSLIssueQuantity_SOQS		M	SOQS	If doing Multi-location processing, this is the quantity that will be reported to the new Location/Lot. This is a key field and is required if the dcLINK action codes is “Z” or “M”.
szSLIssueMemoLotField1_LOT1		M	LOT1	If doing Multi-location processing, this is the Override Lot 1 Number.
szSLIssueMemoLotField2_LOT2		M	LOT2	If doing Multi-location processing, this is the Override Lot 2 Number.
szSLIssueVendorLotNumber_RLOT		M	RLOT	If doing Multi-location processing, this is the Override Supplier Lot Number.
jdSLIssueLotExpirationDte_MMEJ		M	MMEJ	If doing Multi-location processing, this is the Override Lot Expiration Date for the issuing Lot Number.
mnContractSupplementDistri		O	DMCS
szContractNumberDistributi		O	DMCT
cKitOverrride_EV01		O	EV01
mnSLIssueSecondaryQTY_DQTY		M	DQTY
szSLIssueSecondaryUOM_UOM2		M	UOM2
jdSLIssueBasedOnDate_BODJ		M	BODJ
jdSLIssueLotEffectiveDate_DLEJ		M	DLEJ
cSLIssueLotStatusCode_LOTS		M	LOTS
mnShipmentNumber_SHPN		O	SHPN
mnActualShipmentTime_ADTM		O	ADTM	Used for Load Confirmations.
jdDeliveryDate_DLDT		O	DLOT	Used for Load Confirmations.
cInventoryAffectFlag_EV01		O	EV01	Used for Load Confirmations.
szOverrideDocType_DCT		O	DCT	Used for Load Confirmations.
szPrimaryVehicleId_PVEH		O	PVEH	Used for Load Confirmations.
szRegistrationLicNbr_RLNO		O	RLNO	Used for Load Confirmations.
szOverrideNextStatus_NXTR		O	NXTR	Used for Load Confirmations.
mnOverrideDocNumber_DOCO		O	DOCO	Used for Load Confirmations.
jdLoadConfirmDate_LDDT		O	LDDT	Used for Load Confirmations.
mnLoadConfirmTime_TDAY		O	TDAY	Used for Load Confirmations.
szOverrideCompKey_KCOO		O	KCOO	Used for Load Confirmations.
idXAPIWorkflowErrorID_GENLNG		O	GENLNG	Used for Load Confirmations.
szCartonNextStatus_CRSS		O	CRSS	Used for Load Confirmations.
cCalledByTransportation_EV01		O	EV01	Used for Load Confirmations.
cReconcileCartonDetail_EV01		O	EV01	Used for Load Confirmations.
mnLoadNumber_LDNM		O	LDNM	Used for Load Confirmations.
szP4210VersCartonQty_VERS		O	VERS	Used for Load Confirmations.
szP4210VersInvRelief_VERS		O	VERS	Used for Load Confirmations.
szP4210VersItemQty_VERS		O	VERS	Used for Load Confirmations.
cCreateSOCharge_EV01		O	EV01	Used for Load Confirmations.
szPortOfEntryExit_POE		O	POE	Used for Load Confirmations.
jdLotExpirationDate_MMEJ		O	MMEJ	Used for Load Confirmations.

R = Required (shaded blue for quick reference)

O = Optional

X = Required, but will default in if not passed

C = Conditional (see explanation for conditions)

M = Multi-location

Modes to process a ship confirmation

This interface offers a variety of methods for processing a ship confirmation.

Mode Name	Action	Description
Process a single line	Send up a dcLINK action code (cdcLINKActionCode_EV01) numeric value (typically a “0”), the Order Number (szOrderNo_DOCO), Order Type (szOrderType_DCTO), and either the Line Number (mnLineNo_LNID), or Unknown Item Number (szItemNoUnkownFormat_UITM) field values.	The order type is usually defaulted from the processing options. In this mode, the order, order type, and line number fields provide the closest match (no two lines on the same sales order can have the same line number). If processing is being done by order, order type, and unknown item number, then the first item number for that order that matches the item number being sent in will be used. If the order has multiple lines with the same item number, then this method is less exact, because the first “available” line with a matching item number will always be selected. There are several reasons a sales order line may not be “available”, but the principle reason is that its status codes are not in the valid range to be selected.
Confirm an entire order	Send up a dcLINK Action Code value of "A," an Order Number, and an Order Type (from the processing optinons).	You can perform this mode from a device. Do not send an unknown item number or line number. This interface reads all the lines for the order and ship confirms each line that is at the correct status to be processed. Lines at an incorrect status will be skipped. The quantity used to confirm each line will come from the F4211 detail file. When this option is used, the quantity cannot be overridden.
Confirm an entire pick list	Send up a dcLINK Action Code value of “B” and a pick list number.	You can perform this mode from a device. Do not send an order number, item number, or line number. This interface will read all the lines for the pick list and confirm each line that is at the correct status to be processed. Lines at an incorrect status will be skipped. The quantity used to confirm each line will come from the F4211 detail file. When this option is used, the quantity cannot be overridden.
Confirm an entire shipment	Send up a dcLINK Action Code value of “C” and a shipment number.	Confirming an entire shipment is only done when ship confirmation is called from the transportation shipment confirmation interface. This must not be done from a device.
Confirm a configured item	Send up a dcLINK Action Code of “D”, an Order Number, an Order Type (this may come from the processing options), and a Line Number (of the configured item).	This interface will read the configured item line and ship confirm the configured item line, and the component lines for that item on the order that are at the correct status to be processed. Lines at an incorrect status will be skipped. The quantity used to confirm each line will come from the F4211 detail file. This option will allow for the confirmation of the entire quantity or a partial quantity. Multi-location is not supported with this action code. Also, there are a few fields that cannot be overridden when using this option: Lot, Location, Carrier, and Container ID fields are a few examples.
Confirm multiple items using multi-location processing	First, for each item or line, send up a dcLINK Action Code of “Z” , Order Number, Order Type, Line Number, Branch Plant, Item Number, BTN Select Location “1”, SL Issue Branch Plant, SL Issue Location, SL Issue Lot, and SL Issue Quantity. The data will be stored in a temporary work table (FD3N2053) until the next step. Then, for the final transaction to process al locations entered and stored in the table, fill out the following fields: dcLINK Action Code “M”, Order Number, Order Type, Line Number, Branch Plant, Item Number, and BTN Select Location “1”.	If there is an error anywhere in the transaction, the NER will bail out and not process any of the lines. If this occurs, all lines for the transaction will be deleted from the work file.

As a result of processing the sales order lines, other processes in EnterpriseOne (Pack Confirmation and Advanced Warehouse) be changed. Ship confirmation at this point can be done by order or pick list, because all the changes have been previously submitted and saved.

There was a problem loading this topic

Mobile Enterprise Platform