send feedback

❮ Previous Next ❯

Work Order Completions interface for JD Edwards

About the Work Order Completions interface

This interface is used to report how many items have been completed.

Each work order is setup with an item that is being built. Work Order Completions is the program used to report how many of the items have been completed. The dcLINK version is called ND3N1114. This interface was written in NER and calls ‘C' business function, BD3N3104, to retrieve the processing options.

Name	Function name	Description
DD3N114A		dcLINK Interface Work Order Completion
ND3N1114	ND3N1114	dcLINK Interface Work Order Completion
DD3N3104		PO Retrieval –Work Order Completion
BD3N3104	PORetrieveWOCompletions	PO Retrieval Work Order Completion

The full name of this interface is ND3N1114 Work Order Completions

This interface guide applies to the following JDE versions.

EnterpriseOne Xe through 9.1

Corresponding EnterpriseOne application

In EnterpriseOne, the application you would run to perform a work order completion is P31114, and can be accessed from the menu G3112.

Processing options

Processing options for Work Order Completions.

The dream writer version will default to ZJDE0001 if not otherwise specified in the parameter list on the call.

Defaults tab

Inventory Completion Document Type: A work order completion will write an entry to the CARDEX file for all completions. The document type in this field is the value that will be used in CARDEX.
Inventory Completion Document Type: A work order scrap will write an entry to the CARDEX file for all scraps. The document type in this field is the value that will be used in CARDEX.

Edits

Backflush: Work order completions will try to backflush component issues if this flag is turned on and the work order has been setup correctly (the issue code for each component on the parts list is setup as a ‘B' for backflush when complete).
Receipt Routing: If you are verifying a completion occurred, but can't find en entry in CARDEX, check this processing option. If receipt routing is on, then look in the Ledger Inquiry (P43252 on menu G43A14).
Override Lot Numbers: A ‘1' in this field allows the user to change the lot number multiple times. A blank locks in the first lot number that was reported, and uses that lot on all completions.

WO Status

Partial Work Order Status Code: For partial work order completions, this is the status code that will be used to update the work order header status.
Completed Status Code: For full completions that would satisfy the quantity being built on the work order, this status code will be used to update the work order.
Work Order Status Limit: The value entered here is the status code beyond which no more completions can be made against this work order.

Process manufacturing

Allow Unplanned Co/By Products: If the item being built has co/by products as the result of manufacturing, then this flag needs to be a ‘1' in order for this interface to call the co/by product business function. All co/by products are completed “blind”.
Issues Ingredients to Co/By Products: Use this processing option to determine if ingredients are issued to the process item, or to each co/by product that the system completes. This processing option is used only if the Backflush option is set to issue component work order issues.

Warehouse management

Putaway Requests: If this processing option is set to a ‘1' then a work order completion will create a putaway request. This happens automatically and there is nothing special that needs to be passed in on the call. It is mentioned here because it affects where you need to look to validate that the transaction worked properly.
License Plate Number Generation Method: Used to specify how a license plate number will be created. Note however, if the branch/plant used in the transaction is not setup for license plating, then the value of this processing options is moot. A license plate will automatically be generated when the value is 00, 02 or 03. A 01 says the license plate will manually be entered, but that cannot be done using this interface (see ND3N6L30), so a 01 effectively turns off license plating for this NER.
Build default UOM structure: Blank says use the default UOM structure defined in Unit of Measure by Item application, using the entire unit of measure structure. A ‘1' still builds the license plates according the UOM structure, but it ignores any levels higher than the transaction UOM. For example, if an item had a structure of boxes, cartons, and pallets, and the adjustment was for 36 cartons, then license plates would be created for the boxes and cartons, but not the pallets.
Assign Items to License Plat Window (P46L30): This option calls the application P46L30, which cannot be done from this NER. If someone wants to utilize this application, they need to be using Advanced Inventory's ND3N6L30 interface.

Cross Docking

Cross Docking: This processing option specifies whether cross docking is to occur or not. If this processing option is greater than blank, then the interface will check to see if a sales order is waiting for this item to be produced.

Processing option data structure for DD3N3104

Our interface retrieves these parameters by calling BD3N3104, and is passed back in the following data structure.

Type	Description	Parameters
String	sz_PO_Version_VERS	Input
String	szPO_CompletionDCT_DCT	Output
String	szPO_ScrapDCT_DCT	Output
String	szPO_StatusCodeWo_SRST	Output
Char	cPO_LotCode1_EV02	Output
Char	cPO_LotCode2_EV03	Output
Char	cPO_LotCode3_EV04	Output
Char	cPO_LotCode4_EV05	Output
Char	cPO_LotCode5_EV06	Output
Char	cPO_CompletionLot_EV07	Output
Char	cPO_SalesDetailUpdate_EV08	Output
String	szPO_NXTROverride_NXTR	Output
Char	cPO_UpdateNextStatus	Output
Char	cPO_DisplayBORelease_EV09	Output
Char	cPO_UnplannedCOBY_EV12	Output
Char	cPO_IssueSeperate_EV13	Output
Char	cPO_PutawayMode_EV14	Output
String	szPO_WarehouseVersion_VER4	Output
Char	cPO_CallWOIssues_EV01	Output
String	szPO_WOIssuesVers_VERS	Output
String	szPO_StatusLimit_SRST	Output
Char	cPO_ReceiptRouting_EV10	Output
Char	cPO_LotOverride_EV11	Output
String	szPO_ShortageVers_VER2	Output
String	szPO_WOEntryVer_VER3	Output
String	szPO_VersionTestResults_VERS	Output
Char	cPO_ReplenishLSN_EV22	Output
String	szPO_IssuesDocumentType_DCTO	Output
String	szPO_TypeTransaction_TYTN	Output
Char	cPO_SubSystemUBE_EV01	Output
Char	cPQOHNegative_EV01	Output
String	szPO_CompletedStatusCode_SRST	Output
Math	mnPO_Threshold_MATH01	Output
Char	cPO_WIPRevaluation_EV01	Output
Char	cPO_LincensePlating_EV01	Output
Char	cPO_CrossDockingFlag_EV01	Output
Char	cPO_CrossDockingPicRequest_EV01	Output
String	szPO_CrossDockPicReqstVer_VERS	Output
String	szPO_CrosDocOvrideNexStat_NXTR	Output
String	szPO_FromSalesOrderStatus_NXTR	Output
String	szPO_ThruSalesOrderStatus_NXTR	Output
Char	cPO_BeforeImagProcessing_BIPROC	Output
String	szPO_BOReleaseVersion_VER1	Output
Char	cPOHoldCodeRequirement_EV01	Output
String	szPOLPNGenerationMethod_LPNG	Output
Char	cPOBuildStructure_EV02	Output
Char	cPOLicensePlateWindow_EV01	Output

Processing

Work Order Completions is a complex program that can do lots of different processing, depending on how the processing is set.

For example, if you complete, and you are using EnterpriseOne's warehouse module, then instead of just putting the item away in stock, a suggestion is automatically created that will ultimately create a warehouse suggestion to put the item away.

There are options that would put the item completed into receipt routing. If the work order is setup appropriately, and a processing option is set, then performing a completion could also kick off the blind issue of the components. If a work order is tied to sales order, and the item being built has a lot number, then there are processing options that control how the lot number is assigned (it could be the sales order number), or whether the sales order should be updated with the new lot and location information.

The good news is, even through there are many processing options, the master business function handles the complexity. The only thing we really need to watch is that a processing option is not set to call an interactive program when we are processing in batch (the component issues could be interactive or blind – we always want that to be blind).

In EnterpriseOne there are two menu entries, one for a partial completion, and one for a full completion. The only difference between these programs is the processing option for the status code. One changes the status to a partial completion status, and the other changes it to a fully complete status. Once a work order status has been updated to complete, many of the operations you were able to do (issues, completions, etc.) are no longer allowed.

At the same time an item is being reported completed, you may also report if an item has been scrapped. While this could happen once in a while, generally it is very unusual to complete an item and then scrap it. Most companies will try to salvage it along the way by scrapping bad components and re-issuing replacements.

If the completed item is a dual unit of measure item, then the transaction will allow the reporting of secondary quantity and unit of measure.

The completion transaction also allows the user to specify the location and lot where the item was putaway. There is only one field in the work order for the location and lot, so multiple completions to different locations and lots are not reflected on the work order, only the last entry will be shown. There is a form exit in the application P31114, which allows users to override the new lot dates. This functionality is not supported from work order completions, but there is a new Advanced Inventory interface (ND3N4109 Lot Date Revisions) that can be called to change these dates.

Cross docking

If the processing option for cross docking is a ‘2' (planned cross docking), or a ‘3'(planned and opportunistic cross docking), then the completion NER will call Advanced Inventory's business function for cross docking, dcLINK Cross Dock Calculation. Several things are passed into this function, including the order number, order type, and item number. What comes back is a cross dock “flag”. This flag will be a ‘1' if there are sales orders that need the item that was just completed. It will be a ‘2' if there are sales orders, and some of those orders are setup for cross docking. It will be a ‘3' if there is a sales order specifically cross docked to this manufacturing order.

Co/By products completions of process items

Process items, stocking type R, are used to manufacture 'Co' products. 'By' products also may be created. Process item completions complete Co and By products to inventory, not the process item number. For example, when producing oils from crude oil, several desired Co products may be produced and additionally some unwanted residues may be created as By products of the process. In order for the co/by products completion to be kicked off the input field, cCoByProductCompletion_EV02 must contain a ‘1'.

Co/By Products are set up in the process item's BOM, including item numbers and quantities (Form Exit to view and revise them). dcLINK does a blind Co/By product completion in the same way that the process item completion in JDE completes the Co and By products to inventory. For each quantity 1 of the process item being completed, the Co and By product item quantities, as setup from the process item's BOM, are completed. If quantity 10 of the process item is completed, then 10X the Co/By product quantity, as setup from the BOM Form exit, is completed.

Interactively in EnterpriseOne, the user additionally has the ability to override the resulting calculated quantity of each Co or By product. Using the dcLINK interface, the calculated quantity of each Co and By product will be completed to inventory or scrapped. If the user enters a scrap quantity of the process item, then the co/by product completion will calculate a scrap quantity for each of the Co and By products.

Co/By products completions with work file FD3N48WF

Co and By products can also be completed as unplanned quantities - that is, quantities not planned in the BOM related setup quantities. In this functionality the user can enter the Co and/or By product item number, completed qty, lot number, location, secondary qty, secondary UOM (for dual UOM items) and memo lot field text into the work file. Multiple item records can be entered into the work file and then processed to JDE, resulting in Co and/or By product completions to inventory or scrap.Use cdcLINKActionCode with “W” to insert data into work file and then to process those records use cdcLINKActionCode with “P”. All records processed successfully will update the work file CBUSP field with “Y”. The records that have been processed can then be deleted by sending a transaction to cdcLINKActionCode with “D”.

License plating

Items being reported complete can automatically be assigned to one or more license plates. The requirements are that the branch/plant where the completion is being reported has license plating turned on, and the processing options under the Warehouse Mgt tab have license plating turned on. What will happen is the system will assign the license plate number(s) when a completion is performed. The challenge is that this NER gets no notification of the license plate number(s) that were used. If the requirement is to print a license plate label after the completion finishes, allowing this NER to assign the license plate number(s) may not be the way to go. Consider using ND3N6L30 to manually create the license plate.

Required fields

The minimum required fields to perform a work order completion is the work order1, the document type, and the quantity being completed. Everything else depends on what you are doing. If you are completing an item with a lot number, then in addition to the lot you may want to pass the expiration date, memo lot 1, memo lot2, lot status, lot potency, lot grade, or the two new lot date fields, the effective date of the lot, and the based on date of the lot.

Verify the processing for Inventory

Instructions to verify the processing for Inventory.

A work order completion that is not going into receipt routing or warehouse should affect inventory by writing an entry to CARDEX and updating summary availability.

To verify the processing for inventory, complete the following steps in JDE.

Open CARDEX to view this.
Then screen will show an item being completed and its effect on CARDEX.

Step Information

Note the value in the document type field. The 'IC" comes from the processing options for the version passed into the interface.
The next two screens show the effect a work order completion has on the summary availability.

Step Information

The first screen is the "before" version.

The second screen shows the change to the summary availability after one item is completed.
If the item being completed is for a specific location or lot, then that information will also be shown in CARDEX.

Step Information
Every time a work completion transaction is processed, the work order itself is affected. The difference between doing a partial work order completion, versus a full completion, is the value of the status field in the processing option. Therefore one of the first places to look to see if a completion processed correctly is to check and see if the status code on the work order (see below) was updated.

Step Information
The completion screen in EnterpriseOne (G3112) can be used to verify that the quantity completed and scrapped was updated. Inquire on the order being processed and look at what was completed to date, and scrapped to date.

Step Information
If the processing option and work order is setup to do issues as part of the completion, then you will need to look at the parts list to see if the issue part of the completion occurred. The following screen prints show a view of the parts list before the completion was run, and after the completion was run. Note that after the completion, the components that make up the completed item have been issued.

Step Information
If there are any co/by products being completed as the result of doing the work order completion, you will check to make sure those completions occurred. They should be reflected in CARDEX, but you can also check them on the work order by clicking on the Co/By Products form exit button. The screen displayed will be similar to the one shown below. Verify that the quantity completed to date, or scrapped to date, reflect the transaction you just processed.

Step Information

Verify the processing for Receipt Routing

Instructions to verify the processing for Receipt Routing.

If the item being completed is setup to go into receipt routing, then there won't be any CARDEX entries until the item is received to stock through receipt routing.

To verify the processing for Receipt Routing, complete the following steps in JDE.

Go to the receipt routing menu G43A14 and call up the movement and disposition application.
Using the work order, perform inquiry.

Step Information

A screen similar to the one shown below will be displayed. You will see an entry equal to the quantity completed on the work order completions.

Verify the processing for License Plating

Instructions to verify the processing for License Plating.

To verify the processing for License Plating, complete the following steps in JDE.

Open the License Plate Workbench program.
To fine which license plate was created, use the QBE fields at the top of the grid to narrow the search.

Step Information

Input data structure

Input Data Structure for DD3N114A.

Name	Default value	R/O	Alias	Notes
szVersion_VERS	ZJDE0001	X	VERS	Defaulted in program if not passed in.
cdcLINKActionCode_EV01	0	X	EV01	Always defaults to a 0. No different action takes place based on this code. W = Used for CoBy production completion with Work File. It will insert data into table FD3N48WF. P = Process records from work file for CoBy product completion. D = Delete record from work file FD3N48WF.
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. If a value is passed into this field, it will be used to update CARDEX and any “last updated by” fields in tables.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo.
mnJobNumber_JOBS		O	JOBS
szProgramId_PID	ND3N1116	X	PID	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.
mnDocumentOrderInvoice_DOCO		R	DOCO	This is a required field. If this field is left blank, error 4635 will be generated. This field, along with the item number (szQBEUnknownItem_UITM), is used to find the correct component on the work order to scrap.
szOrderType_DCTO		R	DCTO	This is a required field. If this field is left blank, error 0503 will be generated. This field, along with the work order (szQBEOrderNumber_DOCO), is used to find the correct component on the work order to scrap.
szUnitOfMeasureAsInput_UOM		O	UOM	This QBE field is not used by the interface. It was added as a convenience for customizing this interface, should a client need to select component records by quantity issued. The selection logic would have to be added.
mnUnitsQuantityCompleted_SOQS		O	SOCS	This value is required if the transaction is performing completion.
mnUnitsQuantityCanceled_SOCN		O	SOCN	This value is required if the transaction is performing scrap/cancel.
szStatusCodeWo_SRST		O	SRST	This QBE field is not used by the interface. It was added as a convenience for customizing this interface, should a client need to select component records by quantity ordered. The selection logic would have to be added.
szCostCenterAlt_MMCU		O	MMCU	If a value is entered into this field, it will be used by the interface to locate the correct component to scrap. The interface loops through the F3111 file reading all components that match the order number (szQBEOrderNumber_DOCO) and item number (szQBEUnknownItem_UITM) entered. If this field is not null, it will be compared to each retrieved record looking for a match.
jdDateCompletion_STRX		O	STRX	If a value is entered into this field it will be used by the interface to locate the correct component to scrap. The interface loops through the F3111 file reading all components that match the order number (szQBEOrderNumber_DOCO) and item number (szQBEUnknownItem_UITM) entered. If this field is not null, it will be compared to each retrieve record looking for a match.
szLot_LOTN		R	LOTN	This is a required field. If this field is left blank, error 0964 (Error: Branch/Plant Invalid) is generated. This is the Branch/Plant Name.
szReasonCode_RCD		O	RCD	This QBE field is not used by the interface. It was added as a convenience for customizing this interface, should a client need to select component records by date requested. The selection logic would have to be added.
jdExpireDate_EXPR		R	EXPR	This is a required field. If this field is left blank, error 3968 is generated. This is the quantity that is being scrapped. The quantity must not be equal to zero.
szMemoLotField1_LOT1		X	LOT1	This optional field will be defaulted from reading the F3111 file. It can be overridden by supplying a value when the interface is called.
szMemoLotField2_LOT2	Processing Options	R	LOT2	If left blank, it will default to the value stored in the processing options (po_szReasonCde_REAC). Any value keyed into this field will be edited against the UDC table 31\|RC.
szLocation_LOCN			LOCN	Any value entered into this field tells the system that the quantity being completed will be put away into this location.
mnLotPotency_LOTP	Processing Options	X	LOTP	This field is optional. If left blank it will default to the value from the processing options. If that value is blank then today's date will be defaulted. This only needs to be overridden if using the current date is unacceptable.
szLotGrade_LOTG		X	LOTG	This field is the description that is associated with the reason code. If this field is left blank, then the description will default from the UDC table 31\|RC.
cCoByProductCompletion_EV02			EV02	Enter a ‘1' in this field if there are co/by products associated with the item being completed. Any co/by products will be completed blindly (can't override the quantity being completed).
cBTNSelectLocation_EV01			EV01	Not used at this time.
szSLIssueBranchPlant_MCU			MCU	Not used at this time.
szSLIssueLocation_LOCN			LOCN	Not used at this time.
szSLIssueLot_LOTN			LOTN	Not used at this time.
mnSLIssueQuantity_SOQS			SOQS	Not used at this time.
szSLIssueMemoLotField1_LOT1			LOT1	Not used at this time.
szSLIssueMemoLotField2_LOT2			LOT2	Not used at this time.
szSLIssueVendorLotNumber_RLOT			RLOT	Not used at this time
jdSLIssueLotExpirationDte_MMEJ			MMEJ	Not used at this time.
cLotStatus_LOTS			LOTS	This field allows the user to update the lot status at the time the completion is run.
szGuidUniqueID_GUID	Automatically generated by dcLINK	O	CFRGUID	If generate GUIDs is turned on in the dcLINK configuration utility, this field will contain a GUID (guaranteed unique identifier). The GUID is used to tie database changes in PeopleSoft to the transactions that triggered those changes to occur.
szGuidApprover1_USR1		O, R	USR1	An entry in this field, or the Approver 2 field, will cause a signature capture record to be written. Signature capture records are part of the GUID processing and should not be used unless a GUID is being created by dcLINK. The value of this field is a User ID, not an address book entry. There must be a value passed in, to either this field or the approver 2 field, otherwise it is an error.
szGuidFullName1_FULLNAME1		O	FULLNAME1	This field is the full name of the GUID Approver 1.
szGuidApprover2_USR2		O, R	USR2	GUID processing supports up to two approvers. If two approvers are required, this is the user ID of the second approver. There must be a value passed in, to either this field or the approver 1 field, otherwise it is an error.
szGuidFullName2_FULLNAME2		O	FULLNAME2	This field is the full name of the GUID Approver 2.
mnGuidReasonCode1_REASON1		O, R	REASON1	If either of the approver fields contain a value, but no value is entered into one of the reason code fields, then an error will be returned. Reason codes must match the valid reason codes setup for GUID processing, otherwise it is an error.
szGuidCommentField_COMMENTS		O	COMMENTS	This is a free form entry field that is used to further explain the reason code entered into the previous field.
mnGuidReasonCode2_REASON2		O, R	REASON2	If either of the approver fields contains a value, but no value is entered into one of the reason code fields, then an error will be returned. Reason codes must match the valid reason codes setup for GUID processing otherwise it is an error.
szGuidCommentField2_2COMMENTS		O	2COMMENTS	This is a free form entry field that is used to further explain the reason code entered in the previous field.
szGuidScriptID_FMNMVERS		O	FMNMVERS	In PeopleSoft the screen ID where the change was made is captured. dcLINK captures the script ID.
szGuidTextMessage_TEXTMES		O	TEXTMES	This is a free form entry field.
mnSecondaryQty_SQOR		O, R	SQOR	If the item is a DUAL unit of measure item, this is the secondary quantity.
szSecondaryUoM_UOM2		O, R	UOM2	If this item is a DUAL unit of measure item, this is the secondary unit of measure.
szUpdateStatusCode_SRST			SRST	This field updates the work order status. Often times this comes from the processing options so nothing needs to be entered into this field.
jdLotEffectiveDate_DLEJ			DLEJ	Lots can now be setup with the dates they become effective. A date entered in this field will be used to update the lot with the first date that this lot is effective.
jdBasedOnDate_BODJ			BODJ	The system will use this date, in conjunction with the shelf life days, to calculate other lot dates to include the expiration date.
mnSLIssueSecondaryQty_DQTY			DQTY	Not used at this time.
mnSLIssueSecondaryUOM_UOM2			UOM2	Not used at this time.
jdSLIssueBasedOnDate_BODJ			BODJ	Not used at this time.
jdSLIssueLotEffectiveDate_DLEJ			DLEJ	Not used at this time.
cSLIssueLotStatusCode_LOTS			LOTS	Not used at this time.
cCrossDockFlag_EV01			EV01	This field will return the following values: 1 = there are sales orders that need the item just competed; 2 = there are sales orders and some of them are looking for cross docking; and 3 = there is a sales order specifically cross docked to this manufacturing order.
szCountryOfOrigin_ORIG			ORIG
szCoByComponentItem_CPIL		C	CPIL	If cdcLINKActionCode has “W”, then it is needed.
mnCoByQuantityTransaction_TRQT		C	TRQT	If cdcLINKActionCode has “W”, then it is needed.
mnCoByQuantityCanceled_SOCN		O	SOCN
szCoByLocation_LOCN		C	LOCN	If cdcLINKActionCode has “W”, then it is needed.
szCoByLot_LOTN		C	LOTN	If cdcLINKActionCode has “W”, then it is needed.
jdCoByDateLot_Expiration_MMEJ		O	MMEJ	This value is required if a new lot number is being introduced.
szCoByMemoLotField1_LOT1		O	LOT1
szCoByMemoLotField2_LOT2		O	LOT2
cCoByLotStatusCode_LOTS		O	LOTS
mnCoBySeqNoOperations_OPSQ		C	OPSQ	If cdcLINKActionCode has “W”, then it is needed.
szCoByUnitOfMeasureAsInput_UOM		C	UOM	If cdcLINKActionCode has “W”, then it is needed.
cCoByCoproductsByproducts_COBY		C	COBY	If cdcLINKActionCode has “W”, then it is needed.
mnCoByResourcePercent_RSCP		O	RSCP

R = Required

X = Required but will default if passed in

O = Optional

C = Conditional (See notes for condition)

Name	Default value	R/O	Alias	Notes
szVersion_VERS	ZJDE0001	X	VERS	Defaulted in program if not passed in.
cdcLINKActionCode_EV01	0	X	EV01	Always defaults to a 0. No different action takes place based on this code. W = Used for CoBy production completion with Work File. It will insert data into table FD3N48WF. P = Process records from work file for CoBy product completion. D = Delete record from work file FD3N48WF.
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. If a value is passed into this field, it will be used to update CARDEX and any “last updated by” fields in tables.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo.

R = Required

X = Required but will default if passed in

O = Optional

C = Conditional (See notes for condition)

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	Completion	Completion with Backflush	Completion with Scrap	Completion with CO/BY Products
szVersion_VERS	ZJDE0001	ZJDE0002	ZJDE0002	ZJDE0001
cdcLINKActionCode_EV01	0	0	0	0
mnDocumentOrderInvoice_DOCO	10941	10962	10962	10972
szOrderType_DCTO	WO	WO	WO	WO
zUnitOfMeasureAsInput_UOM
mnUnitsQuantityCompleted_SOQS	1	1		2
mnUnitsQuantityCanceled_SOCN			1
szLot_LOTN
szLocation_LOCN
mnLotPotency_LOTP
szLotGrade_LOTG
cCoByProductCompletion_EV02				1
cBTNSelectLocation_EV01
mnSecondaryQty_SQOR
szSecondaryUoM_UOM2
szCountryOfOrigin_ORIG
szCoByComponentItem_CPIL
mnCoByQuantityTransaction_TRQT
szCoByLocation_LOCN
szCoByLot_LOTN
jdCoByDateLot_Expiration_MMEJ
szCoByMemoLotField1_LOT1
mnCoBySeqNoOperations_OPSQ
szCoByUnitOfMeasureAsInput_UOM
cCoByCoproductsByproducts_COBY
mnCoByResourcePercent_RSCP
mnCoByUniqueKeyIDInternal_UKID
mnCoByComponentNumberBOM_CPNB

Field name	Assigning Lots and Locations	Completion with CO/BY Products with Work File FD3N48WF	CO/BY Product Final Processing with Work File
szVersion_VERS	ZJDE0001	ZJDE0001	ZJDE0001
cdcLINKActionCode_EV01	0	W	P
mnDocumentOrderInvoice_DOCO	10941	459727	459727
szOrderType_DCTO	WO	WO	WO
zUnitOfMeasureAsInput_UOM
mnUnitsQuantityCompleted_SOQS	1	1	1
mnUnitsQuantityCanceled_SOCN
szLot_LOTN	10963
szLocation_LOCN	1.A.1
mnLotPotency_LOTP		5
szLotGrade_LOTG		A
cCoByProductCompletion_EV02		1	1
cBTNSelectLocation_EV01
mnSecondaryQty_SQOR		2
szSecondaryUoM_UOM2		GA
szCountryOfOrigin_ORIG		US
szCoByComponentItem_CPIL		2001
mnCoByQuantityTransaction_TRQT		2
szCoByLocation_LOCN		1 A 1
szCoByLot_LOTN		TEST
jdCoByDateLot_Expiration_MMEJ
szCoByMemoLotField1_LOT1		MEMO 555
mnCoBySeqNoOperations_OPSQ		10
szCoByUnitOfMeasureAsInput_UOM		EA
cCoByCoproductsByproducts_COBY		C
mnCoByResourcePercent_RSCP		10
mnCoByUniqueKeyIDInternal_UKID		3783
mnCoByComponentNumberBOM_CPNB		18

References

The following table provides the related D3N objects used to support this NER.

Object Name	Description
BD3N0009	dcLINK Utility – Turn Debug On and Off
DD3N0009	dcLINK Utility – Turn Debug On and Off
BD3NSETU	dcLINK Set User ID
DD3NSETUSR	dcLINK Set User ID
BD3N3104	PO Retrieval – Work Order Completions
DD3N3104	PO Retrieval – Work Order Completions
ND3NGUID	dcLINK Utility Write Signature Capture
DD3NGUID	dcLINK Utility Write Signature Capture

Assumptions

The following assumptions should be made when implementing this NER.

JDE 9.0 – We now have a new NER ND3N3105 that can be called from inside the ND3N1114.

ND3N3105 called using cActionCode_ACTION = “A”
Processing Options required or will be defaulted.
- P31114 Processing Option for P48013 Version (default ZJDE0001).
- P48013 Processing Option for P3105 Version (default ZJDE0001).
- P3105 Processing Option for Selection Value (Blank to allow duplicates/”1” no duplicates).
If ND3N3105 ends in error, WO Completion transaction is not processed.

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
0002	Record Invalid. In the context of this BF this error is returned when an error has been detected from one of these three business functions: dcLINK Set User ID, dcLINK Utility Set Audit Info, or dcLINK Utility Write Signature Capture Record. This message is also generated if the item number on the work order is not found in the item master file.
014O	Quantity Creates Overcompletion. If the quantity shipped to date is greater than the quantity ordered this warning message is displayed. The warning can be ignored by passing 014O into the NER in the error message key field.
085D	UOM Conversion Unsuccessful. This message is received if the program cannot convert the primary quantity into a dual quantity for a dual unit of measure item.
113C	Reserved by. The work order being processed is being processed by someone else.
0115	Work Order Number Invalid. The work order number passed in does not exist in the F4801 file.
124E	Processing Option Error. The processing option is set to call WO Inventory Issues. dcLINK only performs blind WO Issues.
141B	Blanks Invalid. The document number is blank or null.
155U	Lot or Location Invalid This message is displayed if the processing option is set to not allow the lot to be overridden, and the lot number passed in does not equal the lot number on the work order.
170E	Transaction Exceeds Dual Tolerance. The program converted the primary quantity into a dual quantity and then applied the tolerance minimum and maximum as defined in the item master. The dual amount passed in on the transaction was outside this calculated range.
492F	Effective Date less than On Hand Date. The lot effective date is not greater than the completion date.
2501	Lot Already Exists for a Different Item. The lot number entered already exists.
2633	Status Invalid for Change. The status code limit as defined in the processing options is less than or equal the status on the work order.
3138	Invalid Location. The location passed in does not exist in the F4100 file.
4117	Process Order has no Co/By Products. The Co/By Product flag is set telling the interface to do a completion, but there is no item in the parts list setup to co/by product completions.
4859	LSN Generation failed for Work Order. This message is displayed if the lot process type for the item is 4, 5, 6, or 7 and the quantity shipped to date is greater than the quantity ordered.
4898	Serial number and quantity requirements. If the item is setup to have a serial number the quantity reported as complete cannot be greater than 1.

There was a problem loading this topic

Mobile Enterprise Platform

Work Order Completions interface for JD Edwards

About the Work Order Completions interface

Corresponding EnterpriseOne application

Processing options

Defaults tab

Edits

WO Status

Process manufacturing

Warehouse management

Cross Docking

Processing option data structure for DD3N3104

Processing

Cross docking

Co/By products completions of process items

Co/By products completions with work file FD3N48WF

License plating

Required fields

Verify the processing for Inventory

Verify the processing for Receipt Routing

Verify the processing for License Plating

Input data structure

Transaction test scenarios

References

Assumptions

Common error messages