Work Order Inventory Issues interface for JD Edwards

About the Work Order Inventory Issues interface

This interface is used to manually issue components of a work order.

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

Name	Function Name	Description
DD3N113A		dcLINK Interface - Work Order Issues
ND3N1113	dcLINKWOInventoryIssues	dcLINK Interface - Work Order Issues
DD3N3103		PO Retrieval - Work Order Issues
BD3N3103	PORetrievalWOIssues	PO Retrieval - Speed Status Update

This guide applies to the newest version of the ERP.

This interface gives the user the ability to issue components of a work order. Each item on the work order must be issued separately.

Processing options

The following processing options are available for this interface.

To process a transaction, the Document Number (mnDocumentOrderInvoiceE_DOCO), Item Number (szItemNoUnknownFormat_UITM), Operation Sequence (mnSequenceNoOperations_OPSQ), and Component Branch/Plant fields (szBranchComponent_CMCU) must contain valid data.

This transaction uses the szItemNoUnknownFormat_UITM field for the submission of the component's item number. This allows the most flexibility when sending a transaction, since different types of item numbers may be sent from the reader without requiring TranBuilder script changes.

The data structure DD3N113A contains the parameter cLocationControl_EV01. This field, in conjunction with the processing option Unplanned Issues, determines how issues could be applied to the work order parts list. The cLocationControl_EV01 field defaults to a “0” (zero), which signifies that location is not a determining factor when locating an item on the work order parts list. cLocationControl_EV01 is largely used for a component part that is on a parts list multiple times with the same operation sequence number.

The processing option Unplanned Issues has precedence over cLocationControl_EV01 and as such, even if the component item with the location specified in the transaction is not found, it will be added as an unplanned issue.

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

Edits Tab

Document Type (szPO_Issues_DCT) - This field is used to define the default document type when performing issues. The document type is used to determine the origin and purpose of the document.
Work Order Status Code (szPO_StatusCodeWo_SRST) - This field is used as the default status code on the header record for issued materials. If left blank, the system does not update the status code on the header record.
Material Status Code (szPO_MaterialStatusCodeWo_MTST) - This field defaults the status of the material issue, if one has not been sent with the transaction. If left blank, the status will not be updated by the system.
Work Order Status Code Limit (szPO_IssueLimit_SRST) - This field specifies the status beyond which material may not be issued for a work order.
Unplanned Issues (cPO_UnplannedIssue_EV12) - This field determines whether or not the transaction may create an unplanned issue. If this field is a “1” then the users may perform unplanned issues.

Display Tab

Issue Type Code (cPO_ITCValidate_EV01) – This field will validate whenset to a “1”, as long as the material being issued has a valid issue type code. If a component being issued is not of the correct type, the NER will issue an “Invalid Record” error. When this processing option is left blank, this validation is not performed.
Operation Sequence (cPO_EqualOPSQ_EV03) - This field will allow issues against any operation sequence when this value is blank. If the value is a “1”, then the component being issued must be at the operation sequence sent with the transaction in parameter mnSequenceNoOperations_OPSQ.
Requested Date (cPO_EqualDRQJ_EV04) - This field, when set with a “1”, will allow issues of components with the same date DateRequestedJulian (F3111 file) as specified in parameter jdDateRequestedJulian1_DRQ2 of the transaction. A blank value does not perform this check.
Lot Number (cPO_ProtectLotNumber_EV17) - No special processing is done by this NER.
Issue Material For (cPO_RecommendedIssueQty_EV01) - This field will reset the value of parameter mnCompletionIssueQty_QNTOW to “0” if this processing option field is blank. When this field contains a “1”, component issue quantity will be calculated by the value in parameter mnCompletionIssueQty_QNTOW.

Processing option data structure

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

Type	Description	Parameter
String	szPO_Version_VERS	Input
String	szPO_Issues_DCT	Output
String	szPO_StatusCodeWo_SRST	Output
String	szPO_MaterialStatusCodeWo_MTST	Output
String	szPO_IssueLimit_SRST	Output
Char	cPO_PQOHNegative_EV05	Output
Char	cPO_AffectSalesHistory_EV06	Output
Char	cPO_UnplannedIssue_EV12	Output
String	szPO_PODocumentType_DCTO	Output
Char	cPO_ITCValidate_EV01	Output
Char	cPO_ProtectLotNumber_EV17	Output
Char	cPO_RecommendedIssueQty_EV01	Output
Char	cPO_ApplyShrink_APSK	Output
Char	cPO_ApplyYield_APYD	Output
String	szPO_VersionShortageMaint_VERS	Output
String	szPO_OpenPOVersion_V001	Output
String	szPO_POReceiptsVersion_V002	Output
String	szPO_MoveandDispVer_V003	Output
Char	cPO_DefaultWOToSubledger_EV16	Output
String	szPO_IssueTypeTransaction_TYTN	Output
Char	cPO_SelectAllForIssue_EV01	Output
Char	cPO_DisplayOnlyOpenLines_EV02	Output
String	szPO_WOTypeTransaction_TYTN	Output
Char	cPO_WOBeforImagProcesng_BIPROC	Output
String	szPO_LotGroup_LOTGRP	Output

Processing

The characteristics of an item determine which processing 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

To verify that the work order issue actually issued quantity for the work order component, look in EnterpriseOne item ledger (CARDEX) for an issue of the component, with the transaction's document number and quantity. The issue should show up as a negative quantity in the CARDEX for the item.

Input data structure

The following table describes the input data structure for DD3N113A

In the following table, r indicates Required, o indicates Optional, c indicates Conditional, m indicates Multi-location, and x indicates that the item is Required but will default in if not passed.

Name	Default Values	R/O	Alias	Notes
cdcLINKActionCode_EV01	0	X	EV01	dcLINK Action Codes: Value “0” is the only code used in this NER.
cActionCode_ACTION		O	ACTION	“1” = allow overissue, but ignore all errors in MBF. Blank = disallow overissue, and perform DUOM tolerance checking. Will throw MBF errors and warnings as errors.
jdDateUpdated_UPMJ	(today)	X	upmj	Returned from GetAuditInfo if not passed in.
mnTimeUpdated_TDAY	(now)	X	tday	Returned from GetAuditInfo if not passed in.
szUserId_USER	(current user id)	X	user	Returned from GetAuditInfo if not passed in.
szWorkStationId_JOBN	(current workstation id)	X	jobn	Returned from GetAuditInfo if not passed in.
mnJobNumber_JOBS		O	jobs	Generated within NER.
szProgramId_PID	ND3N1113	X	pid	Generally leave this blank and let it default in.
szVersion_VERS	ZJDE0001	X	vers	This is used by the function to look up the appropriate set of processing options.
cSuppressErrMsg_EV01		O	ev01
cErrorCode_ERRC		X	errc	Indicates an error condition. Set by program.
szErrorMessageKey_EKEY		X	ekey	Holds EnterpriseOne error message number.
iDebugLevel_INT01		O	int01	Leave blank except for debugging and testing purposes only. Higher numbers will show more debug dialog boxes. Leaving this blank or setting to “0” suppresses all debug dialog boxes. Do not leave a value greater than “0” in this field after initial setup and testing, as it will cause synchronous dialogs on the computer to pop up when the function is called.
mnDocumentOrderInvoiceE_DOCO		R	doco	Document number of work order.
szItemNoUnknownFormat_UITM		R	UITM	Item number of component.
mnQuantityToIssue_QNTOW		C	QNTOW	This field or nCompletionIssueQty_QNTOW must contain a quantity, but not both. Must be blank when cBTNSelectLocation_EV01 contains a “1”.
szUnitOfMeasureAsInput_UOM	(primary uom from F4101 file)	X	UOM	If this field is left blank and is an unplanned issued, the UOM will be defaulted from the F4101. For planned issues, this comes from F3111.
szLocation_LOCN		O	LOCN	Location of component issued.
szLot_LOTN		O	LOTN	Lot of issued component.
jdDateTransactionJulian_TRDJ	(today)	X	TRDJ	Transaction date.
jdDateRequestedJulian1_DRQ2		C	DRQ2	Required if Requested Date processing option is a “1”.
mnSequenceNoOperations_OPSQ		R	OPSQ	Operation sequence to issue for.
szMaterialStatusCodeWo_MTST	(from processing options)	X	MTST	Can be overridden.
szBranchComponent_CMCU		R	CMCU	Branch/Plant for component issue.
szStatusCodeWo_SRST	(from processing options)	X	SRST	Cannot be overridden. Defaults from processing options.
mnCompletionIssueQty_QNTOW		C	QNTOW	This field or mnQuantityToIssue_QNTOW must contain a quantity, but not both. This field is used by NER to calculate recommended issue quantity. Must be blank when cBTNSelectLocation_EV01 contains a “1”.
jdGeneralLedgerDate_DGL	(today)	X	DGL
cLocationControl_EV01	0	X	EV01	Used in conjunction with Unplanned Issues processing option to allow multiple locations within the same operations sequence.
cBTNSelectLocation_EV01		O	EV01	To perform a Multi-Location transaction, this parameter must contain a “1”.
szSLIssueBranchPlan_MCU		M	MCU	Branch/Plan of the alternate receiving location. Required when cBTNSelectLocation_EV01 contains a “1”.
szSLIssueLocation_LOCN		M	LOCN	Alternate location issued.
szSLIssueLot_LOTN		M	LOTN	Lot number of the alternate location. For multi-location processing.
mnSLIssueQuantity_SOQS		M	SOQS	Quantity to issue from alternate location. A quantity greater than ‘0' is required when cBTNSelectLocation_EV01 contains a “1”.
szSLIssueMemoLotField1_LOT1		M	LOT1	Memo Lot 1 for multi-location processing.
szSLIssueMemoLotField2_LOT2		M	LOT2	Memo Lot 2 for multi-location processing.
szSLIssueVendorLotNumber_RLOT		M	RLOT	Supplier lot number for multi-location processing.
jdSLIssueLotExpirationDte_MMEJ		M	MMEJ	Lot expiration date for multi-location processing.
Globally Unique Identifier (GUID) Fields		C		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.
mnComponentNumber_CPNT		O	CPNT	Note that the former CPNT parameter maps seamlessly into the new CPNB parameter. No action is necessary to integrate this change.
szMemoLot1_LOT1		O	LOT1
szMemoLot2_LOT2		O	LOT2
jdExpiredDate_EXPR		O	EXPR
jdLotEffectiveDate_DLEJ		O	DLEJ
szAccountNumber_ANI		O	ANI
mnSLIssueSecondaryQty_DQTY		M	DQTY
szSLIssueSecondaryUOM_UOM2		M	UOM2
jdSLIssueBasedOnDate_BODJ		M	BODJ
jdSLIssueLotEffectiveDate_DLEJ		M	DLEJ
cSLIssueLotStatusCode_LOTS		M	LOTS
cBTNCloseLine_EV01		O	EV01	If a ‘1' is passed into this field, it tells the interface to close the line.
DUAL Unit of Measure Parameters				Refer to Special Processing Interface Usage Guide for DUAL Unit of Measure parameter details.
Lot/Serial Control				Refer to Special Processing Interface Usage Guide for additional information on Lot/Serial Control.

Data required for receiving items to multiple locations

With the addition of the available call to dcLINK^® Multiple Location Selection (MLS) NER, the user can now receive items to two separate locations with one transaction.

To perform this action, first set up the transaction as you would for a regular receiving. Original information (data created with the work order parts list) is input into the parameters listed above and the data required for the MLS section is placed in the following parameters.

szSLIssueBranchPlant_MCU is to hold the Branch/Plant.
szSLIssueLocation_LOCN must contain a valid location.
szSLIssueLot_LOTN may contain the lot number for the second location.
mnSLIssueQuantity_SOQS should contain a value greater than “0”. No error will be generated if “0” is sent, but then ask yourself “Why did I used MLS?” The parameter must contain a value when the cBTNSelectLocation_EV01 contains a “1”.
szSLIssueMemoLotField1_LOT1 memo lot 1 for MLS entry.
szSLIssueMemoLotField2_LOT2 memo lot 2 for MLS entry.
szSLIssueVendorLotNumber_RLOT supplier lot number for MLS entry.
jdSLIssueLotExpirationDte_MMEJ lot expiration date for MLS entry.
The szBranchComponent_CMCU parameter must contain the proper branch/plant for the work order even when sending a transaction through multi-location processing.

There was a problem loading this topic

Mobile Enterprise Platform