send feedback

❮ Previous Next ❯

Inventory Reclassification interface for JD Edwards

About the Inventory Reclassification interface

This interface is used to reclass an item into something other than its original form.

For example, a lumber mill gets a 40 foot maple log. They run it through the mill and reclass the log into 120 board feet of FAS, 140 board feet of selects and better, and 240 board feet of No. 1 Common. The dcLINK version is called ND3N4116.This interface was written in NER and calls a ‘C' business function, BD3N4108, to retrieve the processing options from the interactive program P4116.

Name	Function name	Description
DD3N4116		dcLINK Interface Inventory Reclassification
FD3N4116		dcLINK Interface Inventory Reclassification
ND3N4116	dcLINKInventoryReclassificaiton	dcLINK Interface Inventory Reclassification
DD3N4108		PO Retrieval Inventory Reclassification
BD3N4108	PORetrievalInventoryReclass	PO Retrieval Inventory Reclassification

The full name of this interface is ND3N4116 Inventory Reclassification

This interface guide applies to the following JDE versions.

EnterpriseOne Xe through 9.1

Environment considerations

It takes multiple calls to perform one inventory reclassification transaction. Each transaction has at least one “from” side, and one “to” side (they could have multiple “froms” and multiple “tos”). Then there is a transaction with an action code that initiates the Edit Doc/End Doc function. In order to make all this work together, these transactions are first loaded into a work file (FD3N4116) and then a transaction is sent up with an action code that initiates the processing of all the other transactions. So, step one is to make sure the work file has been created in the environment in which you are working. This can easily be done using UTB to see if the file exists.

Corresponding EnterpriseOne application

In EnterpriseOne the application that you would run to perform an inventory reclassification is P4116 Inventory Reclassification. This can be accessed from the G4111 menu (Inventory Master/Transactions).

Processing options

Processing options for Inventory Reclassification interface.

Processing options control certain aspects of how the interface functions, both within EnterpriseOne, and through the interface. It is important, when testing the interface, that you receive an identical result when running the transaction through the corresponding EnterpriseOne application, utilizing the same version.

Defaults tab

Documents Type: This is the document type that will default for the transaction if one is not passed into the interface. This is validated against the UDC 00/DT. Typically you allow the document type to default from this value into the interface and not be manually entered. szPO_DocumentType_DCT
Assign Expiration Dates: If this field is blank, then the lot expiration date becomes a required field for transactions that create a new lot. cAssignExpirationDates_EV01

Process tab

Cost Entry: Used to specify whether the interface will allow changes to the unit cost and extended amount fields. Valid values are: 1 – do not allow entry and use the default values from the Cost Ledger Table F4105, and blank- allows entry into the cost fields. cProtectCost_EV02
Lots on Hold: Used to specify whether the interface will allow a reclassification if the lot is on hold. Valid values are: 1 – allow reclassification to lots on hold, or blank – do not allow reclassification to lots that are on hold. cAllowHeldLots_EV04
Reclassification Quantity: Used to specify whether the interface will allow an amount that is greater than the quantity available to be reclassified. Valid values are: blank - do not allow amounts that are greater than the quantity available to be reclassified, or 1 – allow amounts greater than the quantity available to be reclassified. cAllowQtyOverAvailable_EV05
Quantity Validation: Used to specify if the quantity on the “to” transaction must match the quantity on the “from” transaction. Valid values are: blank – no validation is performed, 1 – validation is done but only a warning is issued that they don't match, or 2 – validation is done and an error message is generated if they don't match.

Processing option data structure for DD3N4108

The interface retrieves these parameters by calling BD3N4108 and is passed back in the following data structure.

Type	Description	Parameter
String	szVersion_VERS	Input
String	szDocumentType_DCT	Output
String	szJournalEntriesVersion_VL01	Output
String	szItemSearchVersion_VL02	Output
String	szItemLedgerVersion_VL03	Output
Char	cProtectCost_EV02	Output
Char	cSummaryMode_EV03	Output
Char	cAllowHeldLots_EV04	Output
Char	cAllowOverQtyAvailable_EV05	Output
Char	cQuantityValidation_EV06	Output
String	szOutInteroperabilityType_TYTN	Output
Char	cAgreementAssignProcess_EV01	Output
Char	cAssignExpirationDates_EV01	Output

Processing

Processing information for Inventory Reclassification interface.

Required fields

The dcLINK Action Code, transaction number, from/to flag, branch/plant, item, and quantity are required fields. These are the minimal requirements. If you are adjusting a specific location and/or lot, these fields would need to be entered. If you want to enter a zero cost for the transaction, you must put a value of “1” in the cZeroCostEntered_EV09 field.

The characteristics of an item determine which fields are required by the interface. Some characteristics are set at the item level, and some are set at the item/branch level. The item/branch level always takes precedence over the item master.

Lot/Serial Control

Determined at the branch level. The Lot Process Type SRCE determines if a lot or serial number is required and how it is assigned. Valid values are:

Blank, 0 - Lots are optional.
1 - Lots are assigned using the date (the API will populate the lot number).
2 - Lots are assigned with next number (the API will populate the lot number).
3 - Lots must be assigned manually.
4 - Serial number is optional.
5 - Serial number assigned using date.
6 - Serial number assigned manually.

The Serial Number Required NR works in conjunction with the lot process type to determine whether a serial number is required, or if additional lot fields are required. Valid values are:

Blank - Serial number not required.
3 - Supplier lot required (entry of this field is not supported by the Inventory Adjustment interface or by EnterpriseOne, the user must maintain the lot master after the record is added).
4 - Supplier lot (entry of this field is not supported by the Inventory Adjustment interface or by EnterpriseOne, the user must maintain the lot master after the record is added), memo lot 1 required.
5 - Supplier lot (entry of this field is not supported by the Inventory Adjustment interface or by EnterpriseOne, the user must maintain the lot master after the record is added), memo lot 1 and memo lot 2 are required.
6 - CSMS Non-serialized item.
N - Serial number not required.
Y - Serial number required (if the item is serialized the quantity must be 1). This is dependent on the lot process type flag having a value of 5, 6 or 7.

Shelf Life Days SLD

This will determine if the expiration date can be assigned automatically based on the transaction date. The Lot Status Code LOTS will default in from the item/branch record. If you are passing a value into this field, the processing options must be set to allow for processing lots on hold. The lot status code is validated against the UDC 41/L. The Lot Grade LOTG determines whether grade is used for this item. The item can be either grade or potency controlled but not both. If the item is grade controlled, the value is validated against the UDC 40/LG. The Lot Potency LOTP determines whether potency is required for this item. When using lot controlled items, if the item/lot combination already exists, you will not be able to change the existing lot number information, you will only be affecting the quantity. If the item is set to have the next number automatically assigned, you do not have to pass the lot number. If a lot number is entered it will take that value and not use the next number. Example: Item L1001, Lot number 12345 currently has a quantity on hand of 100 with an expiration date of 12/10/2010. If an adjustment is made for 10 and an expiration date of 12/15/2010 is entered, the system will ignore the new date, no error is returned, but the expiration date of the lot will not change. The prompting of the expiration date should be tailored to fit the specific needs of the script, whether to always prompt for the date, always default from the Shelf life days, or to check if the lot exists and then act appropriately.

Dual Unit of Measure

This is determined at the item master level. When this is turned on for an item, a primary and a secondary quantity are required. All inventory transactions must be entered with primary and secondary quantities. The dual unit of measure process uses principals based upon catch weight. The primary characteristics of these items are that there is a variable quantity for the unit of measure conversion, not a static conversion factor. Examples are food and roll goods. Example: If you were dealing with chickens, the weight per chicken varies, so a standard unit of measure conversion will not work because it is not consistent. The item setup could be Primary Unit of Measure Each, secondary unit of measure LB; a unit of measure conversion needs to exist with a baseline conversion of LB to each. The weight in lbs of an individual chicken will vary and needs to be input for all transactions. The Dual Unit of Measure Item DUAL controls whether the item is a dual unit of measure item and whether tolerance checking is used. The valid values are: Blank – the item does not utilize dual unit of measure functionality; 1 – the item utilizes the dual unit of measure functionality without tolerance checking; 2 – the item utilizes the dual unit of measure functionality with tolerance checking for all transactions except for inventory issues and adjustments. If you do not pass the secondary quantity in this transaction it will not default to the standard unit of measure conversion it will pass a 0 into the secondary quantity.

Best practice

The minimum fields that you should be passing in are the Item number, Branch/Plant, Quantity, Location, from/to flag, transaction number, and lot number information, if required. Typically the document type is retrieved from the processing options of the version being used.

Action code usage

Inventory reclassification is made up of multiple lines written to a work file that are then processed together as one transaction. The transaction number (mnTransactionNbr_TRNO) is the common element that combines multiple lines together to form this single transaction. A single transaction will be at least four lines - a “from” line (dcLINK Action Code = 2); a “to” line (dcLINK Action Code = 3); an edit doc/end doc line (dcLINK Action Code = 7); and a transaction “trigger” (dcLINK action code = 8), which tells the interface all the lines have been loaded and to process the group as one transaction. In practice there maybe multiple “from” lines or multiple “to” lines. Each of these lines must have the same transaction number and the transaction number must be different from anyone else that might also be performing inventory reclassification transactions.

The valid action codes (cdcLINKActionCode_EV01) for this interface are:

Action code	Description
0	Use to process a single-line transaction, performs Begin Document, Edit Line, End Document and Clear Cache.
2	Used with multi-line transactions. Begin Document and Edit Line. Open batch and enter the first line item.
3	Used with multi-line transactions. Edit Line, used to continue to add lines to the same batch.
7	Used with multi-line transactions. Edit Document and End Document.
8	Used with multi-line transactions. Transaction trigger to process all the lines loaded to the work file and/or clear the work file. If an error occurs during a multi-line transaction set and you wish to abandon the transactions you must use this action code to clear the work file.

Verify the processing

Verify the processing of the Inventory Reclassification interface.

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

Open CARDEX.
Verify the entry in the Item Ledger (menu G41112).
Verify the journal entry in Inventory Journal Review (menu G41).
Use the E1 application to view transactions done in dcLINK.
Use the QBE fields to find the batch created in dcLINK and select the entry.

Input data structure

Input data structure for DD3N4116.

Name	Default value	R/O	Alias	Notes
cdcLINKActionCode_EV01		R	EV01	0 = Single-line Transaction. 2 = Multi-line Transaction – Begin Doc, Edit Line. 3 = Multi-line Transaction – Edit Line. 7 = Multi-line Transaction – Edit Doc, End Doc. 8 = Multi-line Transaction – Process a multi-line transaction, Clear Cache.
mnPreviousLineNumber_LNID		O	LNID	If not doing Multi-line transactions, this field normally should be blank. EnterpriseOne will return this field. In multi-line transactions, all transactions after the initial one must return the previous line number from the previous transaction.
cBatchStatus_EV01		O	EV01	Required field. If the version does not have a default value, then the transaction must include the document type.
mn0911JobNumber_JOBS		O	JOBS	If not doing Multi-line transactions, this field normally should be blank. EnterpriseOne will return this field. In multi-line transactions, all transactions after the initial one must return the 0911 job number from the initial transaction.
mnLastJELine_JELN		O	JELN	If not doing Multi-line transactions, this field normally should be blank. EnterpriseOne will return this field. In multi-line transactions, all transactions after the initial one must return the previous line number from the previous transaction.
szDocumentKeyCompany_KCO		O	KCO	If not doing Multi-line transactions, this field normally should be blank. EnterpriseOne will return this field. In multi-line transactions, all transactions after the initial one must return the document key company from the initial transaction.
mnBatchNumber_ICU		X, R	ICU	If not doing Multi-line transactions, this field normally should be blank. EnterpriseOne will return this field. In multi-line transactions, all transactions after the initial one must return the batch number from the initial transaction.
szLotDescription_LDSC		O	LDSC
jdExpirationDate_MMEJ		O	MMEJ	If the item is lot controlled and there is no value in the shelf life days, this becomes a required field.
cLotStatusCode_LOTS		O	LOTS
szMemoLot2_LOT2		O, R	LOT2	If the item is lot controlled and set to require Memo Lot 2, this becomes a required field.
szMemoLot1_LOT1		O, R	LOT1	If the item is lot controlled and set to require Memo Lot 1, this becomes a required field.
mnLotPotency_LOTP		O, R	LOTP	If the item has Potency control turned on, this is a required field.
szLotGrade_LOTG		O, R	LOTG	If the item has Grade control turned on, this is a required field.
szReasonCode_RCD		O	RCD
mnTransactionExtendedCost_PAID		O	PAID
mnTransactionUnitCost_UNCS		O	UNCS
szLotNumber_LOTN		O	LOTN	If the item is lot controlled, and the lot number is assigned manually, this becomes a required field. If the lot is assigned using next numbers, EnterpriseOne will assign the appropriate next number. If the processing option is set to default from primary, and no location is entered, the primary location will default into the transaction.
szDisplayLocation_LOCNE1		O	LOCNE1	Can be unformatted. If the processing option is set to default from primary, and no location is entered, the primary location will default into the transaction.
szTransactionUOM_TRUM		O	TRUM	If no value is passed, the primary unit of measure will be used.
mnTransactionQty_TRQT		R	TRQT	For “from” lines, this represents the amount that is going to be reclassified. For “to” lines, this represents the amount that after the item has been reclassified.
szPrimaryItemNumber_UITM		R	UITM	Used to look up the short item number. On “from” transactions, this is the item that is being used up. On “to” transactions, this is the item that is being created.
mnTransactionNbr_TRNO		R	TRNO	This is the glue that holds the four transactions together. Each part of the transaction needs to use the same transaction number.
cFromTo_FRTO		R	FRTO	For the “from” lines, the value in this field needs to be “F”. For the “to” lines, the value in this field needs to be a “T”.
szBranchPlantTo_MCU	*	O	MCU	Branch/Plant associated with the “To” transaction.
szBranchPlantFrom_MCUF	szBranchPlantTo_MCU	O	MCUF	Branch/Plant associated with the “From” transaction.
jdTransactionDate_TRDJ		O	TRDJ
szExplanationTransaction_TREX		O	TREX
jdGLDate_DGL		O	DGL
szTransactionDocType_DCT		X	DCT
mnDocNumber_DOC		O	DOC
iDebugLevel_INT01		O	INT01	Displays M&D Debug statements if the value is greater than zero.
szErrorMessageKey_EKEY		O	EKEY	If this NER detected an error while running the transaction, the error message key is returned in this field.
cErrorCode_ERRC		O	ERRC	If an error occurred in the execution of the transaction, the value returned in this field will be a ‘2'. If no error occurred then a ‘0' is returned.
cSuppressErrMsg_EV01		O	EV01	This field is not used.
szVersion_VERS	ZJDE0001	x	VERS	If not passed in the ZJDE0001, version will be used. The processing options of this version will be used for error checking.
szProgramId_PID	ND3N4116	X	PID	Defaulted in program if not passed in
mnJobNumber_JOBS		O, R	JOBS	If not doing Multi-line transactions, this field normally should be blank. EnterpriseOne will return this field. In multi-line transactions, all transactions after the initial one must return the job number from the initial transaction.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo.
szUserId_USER	Current User	X	USER	If not passed in, a value will be retrieved from GetAuditInfo. The value of this field will be used for typical user related updates (user ID of who updated a database record, user ID in CARDEX, user ID for GL batches, etc.)
mnTimeUpdated_TDAY	Current Time	X	TDAY	Retrieved from GetAuditInfo.
jdDateUpdated_UPMJ	Current Date	X	UPMJ	Retrieved from GetAuditInfo.
cActionCode_ACTION	C	O	Action
cZeroCostEntered_EV09		O	EV09	Normally blank, if you are trying to manually enter a zero cost, this must be set to 1.
mnShortItemNumber_ITM		O	ITM	No entry is required. The NER will look up this value using the Primary Item Number.
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 EnterpriseOne 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 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.
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 EnterpriseOne, 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.
mnTransactionGroupNumber_TGN		O	TGN
mnRelatedFromLineNumber_RFLN		O	RFLN
mnSecondaryQuantity_SQOR		O	SQOR	If the item is a DUAL unit of measure item this is the secondary quantity.
szSecondaryUoM_UOM2		O	UOM2	If this item is a DUAL unit of measure item this is the secondary unit of measure.
jdLotEffectivityDate_DLEJ		O	DLEJ

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 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	Enter "From" data	Enter "To" data	Enter end doc	Process trigger
cdcLINKActionCode_EV01	2	3	7	8
mnPreviousLineNumber_LNID
cBatchStatus_EV01
mn0911JobNumber_JOBS
mnLastJELine_JELN
szDocumentKeyCompany_KCO
mnBatchNumber_ICU
szLotDescription_LDSC
jdExpirationDate_MMEJ		12/25/2008
cLotStatusCode_LOTS
szMemoLot2_LOT2
szMemoLot1_LOT1
mnLotPotency_LOTP
szLotGrade_LOTG
szReasonCode_RCD
mnTransactionExtendedCost_PAID
mnTransactionUnitCost_UNCS
szLotNumber_LOTN	200607060001
szDisplayLocation_LOCNE1
szTransactionUOM_TRUM
mnTransactionQty_TRQT	100	25	25	25
szPrimaryItemNumber_UITM	9010	9011	9011	9011
mnTransactionNbr_TRNO	545	545	545	545
cFromTo_FRTO	F	T	T	T
szBranchPlantTo_MCU	30	30	30	30
szBranchPlantFrom_MCUF	30	30	30	30
jdTransactionDate_TRDJ
szExplanationTransaction_TREX	Test of Reclass	Test of Reclass	Test of Reclass	Test of Reclass
jdGLDate_DGL		06/15/2005	06/25/2005	06/25/2005
szTransactionDocType_DCT
mnDocNumber_DOC
iDebugLevel_INT01
szErrorMessageKey_EKEY
cErrorCode_ERRC
cSuppressErrMsg_EV01
szVersion_VERS	ZDBK0001	ZDBK0001	ZDBK0001	ZDBK0001
szProgramId_PID
mnJobNumber_JOBS
szWorkStationId_JOBN
szUserId_USER
mnTimeUpdated_TDAY
jdDateUpdated_UPMJ
cActionCode_ACTION
cZeroCostEntered_EV09
mnShortItemNumber_ITM
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES
mnTransactionGroupNumber_TGN
mnRelatedFromLineNumber_RFLN
mnSecondaryQuantity_SQOR
szSecondaryUoM_UOM2
jdLotEffectivityDate_DLEJ

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
0001	Action Invalid. The dcLINK action code must be one of the following: 0, 2, 3, 7, or 8. This error will also be generated if the dcLINK action code is equal to 0, 2, 3, or 7, and the from/to flag (cFromTo_FRTO) is not equal to a “F” or a “T”.
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.
0003	Blanks Invalid. This message is returned if either the transaction quantity (mnTransactionQty_TRQT), or the transaction number (mnTransactionNbr_TRNO), is left blank.
0004	Date Invalid or Missing. If a lot number is passed in on a “to” transaction, the expiration date (jdExpirationDate_MMEJ) is compared to the transaction date (jdTransactionDate_TRDJ). An error returns this message.
0013	Entry Invalid. This is the error returned if an error was found in the Begin Doc MBF, the Edit Line MBF, the End Doc MBF, or the Clear Detail Stack
039F	Transaction Quantities Do Not Balance. This error is returned after the Edit Doc, if the edit document error code returned from the call is equal to “2”, and the processing option to validate quantities (po_cQuantityValidatio_EV06) is equal to a “2”.
052B	Insert Invalid. The insert into the FD3N4116 work table failed.
056P	Order quantity cannot be zero. The dual unit of measure item flag from the item master indicates the item is a dual unit of measure item, yet the secondary quantity (mnSecondaryQuantity_SQOR) was not populated.
085D	UOM Conversion Unsuccessful. The conversion between the transaction unit of measure and the secondary unit of measure failed.
097X	Delete failed. At end of job, after the work file has been processed successfully, all the entries for the transaction line number that was processed are deleted. This error is returned if the delete failed.
010U	Invalid Item Number. The item number passed in is either blank, or the data item returned when the Verify and Get Item Master is called is blank.
170D	Unit of Measure is related to Secondary. The transaction unit of measure (szTransactionUOM_TRUM) that is passed in does not match the primary unit of measure for this item.
170E	Transaction Exceeds Dual Tolerance. The secondary quantity passed in exceeds the dual of measure tolerance test.
4718	Supplier and Memo Lot 1 Must be Entered. This message is received if the lot is not found in the lot master, and the serial number required field is equal to a 4 or 5, plus the memo lot 1 field passed in is blank.
4773	Supplier, Memo Lot 1 & 2 must be entered. This error is generated when the lot/serial number is not found in the lot master, the serial number required field is equal to a 5, and the memo lot 2 field passed in is blank.
492F	Effective Date less than On Hand Date. The effective date passed in (jdLotEffectivityDate_DLEJ) is less than the transaction date passed in (jdTransactionDate_TRDJ).

There was a problem loading this topic

Mobile Enterprise Platform