Cross Dock Calculation interface for JD Edwards

About the Cross Dock Calculation interface

This interface is used to send alerts to users performing PO Receipts or WO Completions that an item being processed should be cross docked to the shipping dock.

Cross docking is the expression used to indicate that goods coming into a warehouse need to immediately be shipped out to fulfill a sales order. This speeds up order fulfillment by not putting the item being processed into storage.

This interface isn't executed automatically; it must be called from an application, and all it does is alert the application via the cross docking flag (cCrossDockFlag_EV01) that the line being received should be cross docked (taken to the shipping dock). It is up to the application to display sufficient information to the person processing the item so he/she knows what to do.

Name	Function name	Description
DD3N4312C		dcLINK Interface Cross Docking Calculations
ND3N4312	dcLINKCrossDockCalculation	dcLINK Interface Cross Docking Calculation

The full name of this interface is ND3N4312 Cross Dock Calculation

This interface guide applies to the following JDE versions.

EnterpriseOne Xe through 9.1

Corresponding EnterpriseOne applicaton

There is no corresponding E1 application that works exactly like this function. E1 has a Planned Cross Docking Workbench (P4611) that can be used to see sales orders that have the item being processed on it, but it requires someone reviewing the workbench and making a determination if the item needs to be cross docked.

In order for this function to work as expected, a user does have to do some setup in JDE. Specifically, when a sales order is entered for each line, there is a row exit that allows users to tie that sales order line to a purchase order/work order that will fulfill the quantity needed on the sales order. To get to this input screen, go into your sales order, select a line that has been entered, and then click row exits choosing the exit that says SOE – Additional.

Processing options

There are no processing options associated with this cross docking function.

Processing

Processing information for Cross Dock Calculation interface.

At a minimum, what needs to be supplied to is the short item number and branch plant. If you only supply these two items, then you can expect to get back as a cross dock flag value 0.

If you add the status range (the from and thru), then what is returned for a cross dock flag could be 0, 1 or 2.

In addition to the item number, branch plant, and statuses, if you also supply the order number (purchase order or work order depending on what you are doing), document type, company number, order suffix, and line number then you may, in addition to the 0, 1, or 2, receive a cross dock flag of 3.

Cross dock flag meanings

Flag	Meaning
0	Even though the item is setup for cross docking, there were no sales orders found that needed this item.
1	At least one sales order was found for the item being processed, but the sales order was not flagged for cross docking. In this case a company may do “opportunistic” cross docking (I was not planning on cross docking this item but I found an order that needs this item so I'm doing it anyway).
2	Sales orders were found that needed the item being processed, and at least one order is setup for cross docking.
3	A sales order was found that was specifically tied to this the purchase order/work order passed in.

Required fields

The minimum required fields are the short item number and branch plant. However, just passing those fields will only get you a 0 returned for the cross dock flag.

Including the from status (szFromStatusCode_LTTR) and the thru status code (szThruStatusCode_NXTR) gives the interface more to work with, and increases the possible return codes for the cross dock flag to 0, 1 or 2.

If you want to check if the item being processed is tied to a specific sales order, then pass in the order number (mnCDOrderNumber_DOCO), the order type (szCDOrderType_DCTO), the company number (szCDOrderCompNo_KCOO), the order suffix (szCDOrderSuffix_SFXO), and the order line number (mnCDOrderLineNo_LNID). If an order is setup for the purchase order/work order, a value of 3 will be returned in the cross dock flag.

Input data structure

Input data structure for DD3N4312C

Name	Default value	R/O	Alias	Notes
cdcLINKActionCode_EV01	Not used	X	EV01
cActionCode_ACTION	Not used	X	ACTION
jdDateUpdated_UPMJ	Not used	X	UPMJ
mnTimeUpdated_UPMT	Not used	X	UPMT
szUserId_USER	Not used	X	USER
szWorkStationId_JOBN	Not used	X	JOBN
mnJobNumber_JOBS	Not used	O	JOBS
szProgramId_PID	Not used	X	PID
szVersion_VERS	Not used	X	VERS
cSuppressErrorMessage_EV01	Not used	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.
szBranchPlant_MCU		R	MCU	This is a required field and the interface will return an error if nothing is passed in.
mnShortItemNumber_ITM		R	ITM	This is a required field and the interface will return an error if nothing is passed in.
szUnitOfMeasureAsInput_UOM	Not used	O	UOM
mnTotDemandQty_TRQT		O	TRQT	This is returned on the call, and is an accumulation of the F4211 transaction quantity.
cCrossDockFlag_EV01	0	O	EV01	0 = No sales orders were found that had an open quantity for this item. 1 = Sales order(s) were found for the item being processed, and are at the right status for cross docking, but the order(s) was not flagged for cross docking. 2 = Sales order(s) were found for the item being processed, and at least one order was setup for cross docking. 3 = Sales order(s) were found for the item being processed, and the sales order(s) is specifically tied to this purchase order/work order to refill the sales order.
mnCDOrderNumber_DOCO		O	DOCO	This needs to be passed in if you trying to specifically match the item being processed to a specific sales order. This is the purchase/work order number.
szCDOrderType_DCTO		O	DCTO	This needs to be passed in if you are trying to specifically match the item being processed to a specific sales order. This is the purchase/work order document type.
szCDOrderCompNo_KCOO		O	KCOO	This needs to be passed in if you are trying to specifically match the item being processed to a specific sales order. This is the purchase/work order company number.
szCDOrderSuffix_SFXO		O	SFXO	This needs to be passed in if you are trying to specifically match the item being processed to a specific sales order. This is the purchase/work order suffix.
mnCDOrderLineNo_LNID		O	LNID	This needs to be passed in if you are trying to specifically match the item being processed to a specific sales order. This is the purchase/work order line number.
szFromStatusCode_LTTR		O	LTTR	The sales order next status must be greater than, or equal to, this status for the line to be selected.
szThruStatusCode_NXTR		O	NXTR	The sales order next status must be less than, or equal to, this status for the line to be selected.

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	Just item and branch/plant	Looking for a specific order	Looking for sales orders in a status range
cdcLINKActionCode_EV01
cdcLINKActionCode_EV01
cActionCode_ACTION
jdDateUpdated_UPMJ
mnTimeUpdated_UPMT
szUserId_USER
szWorkStationId_JOBN
mnJobNumber_JOBS
szProgramId_PID
szVersion_VERS
cSuppressErrorMessage_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
szBranchPlant_MCU	30	30	30
mnShortItemNumber_ITM	60011	60011	6011
szUnitOfMeasureAsInput_UOM
mnTotDemandQty_TRQT
cCrossDockFlag_EV01
mnCDOrderNumber_DOCO		5931
szCDOrderType_DCTO		OP
szCDOrderCompNo_KCOO		00001
szCDOrderSuffix_SFXO		000
mnCDOrderLineNo_LNID		1.000
szFromStatusCode_LTTR		520	520
szThruStatusCode_NXTR		560	560

Common error messages

The following are common error messages that can be generated by this BF, and what those error messages mean.

Error message	Meaning
023C	Short Item Number Invalid. The short item number is a required input into this function. If this field is empty, this error will be returned.
0964	Branch Plant Invalid. The branch plant is a required input into this function. If this field is empty, this error will be returned.

There was a problem loading this topic

Mobile Enterprise Platform