send feedback

❮ Previous Next ❯

Inventory Issues and Adjustments interface for JD Edwards

About the Inventory Issues and Adjustments interface

The Inventory Issues and Adjustments interface is used to issue material from inventory or adjust inventory quantities.

The MEP version is called ND3N4114. This interface was written in NER and calls ‘C' business functions BD3N4105 or BD3N4103 to retrieve processing options for the related interactive program.

Even though the interface is called ND3N4114, depending on how the cIssue_or_AdjFlag_EV01 is set will determine the functionality of the NER. If the field is set to “I” for Issue, the interface will perform an inventory issue and a reduction in inventory. If the field is set to “A” for Adjustment, the interface will perform an inventory adjustment transaction.

Processing an Inventory Issue: When the cIssue_or_AdjFlag_EV01 is set to “I”, the interface will retrieve the processing options from P4112, signifying the transaction will be an inventory issue and a reduction in inventory. When performing the inventory issue, the transaction quantity is entered as a positive number. BD3N4103 is used to retrieve the processing options from the interactive program P4114.

Processing an Inventory Adjustment: When the cIssue_or_AdjFlag_EV01 is set to “A”, the interface will retrieve the processing options from P4112, signifying the transaction will be an inventory issue and a reduction in inventory. When performing the inventory issue, the transaction quantity is entered as a positive number. BD3N4105 is used to retrieve the processing options from the interactive program P4112.

Name	Function name	Description
DD3N4114		dcLINK Interface Inventory Issues and Adjustments
ND3N4114	dcLINKInventoryActivity	dcLINK Interface Inventory Issues and Adjustments
DD3N4105		PO Retrieval Inventory Issues
BD3N4105	PORetrievalInventoryIssues	PO Retrieval Inventory Issues
DD3N4106		PO Retrieval Inventory Adjustments
BD3N4103	PORetrievalInventoryAdjustments	PO Retrieval Inventory Adjustments

The full name of this interface is ND3N4114 Inventory Issues and Adjustments.

This interface guide applies to the following JDE versions.

EnterpriseOne Xe through 9.1

This interface is written to support single-line transactions. A single-line transaction creates an EnterpriseOne batch for each transaction with a separate document number, and performs a Begin Document, Edit Line, End Document, and Clear Cache.

In EnterpriseOne, the application that you would run to perform an inventory issue is P4113 Inventory Issues. This can be accessed from the G4111 menu (Inventory Master/Transactions).

In EnterpriseOne, the application that you would run to perform an inventory adjustment is P4114 Inventory Adjustments. This can be accessed from the G4111 menu (Inventory Master/Transactions).

Processing options

Processing options for Inventory Issues and Adjustments 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 when you run the transaction through the corresponding EnterpriseOne application, utilizing the same version, that you receive the identical result.

Processing options for Inventory Issues

Defaults tab

Document 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.
Location/Lot: If there is a value of 1 in this field, and no lot or location is passed in the interface, it will use the location and lot from the primary location. cPO_DefaultPrimLocation_EV01.

Process tab

Issue Type: Used to specify the fields that are displayed within EnterpriseOne. If set to 2 - Sub ledger information only, or 3 - Equipment and Sub ledger information, the processing option to require an account number becomes active. cPO_DisplayOptions_EV02
Account Number: If the value of 2 or 3 is set in the issue type, this field is used to require the entry of account numbers. Valued values are: 1 - require entry in the account number field; or blank - default the expense account from the inventory default 4124 AAI item. cPO_RequireAcctNum_EV03
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. cPO_ProtectCosts_EV04.
Issue Quantity: Used to specify whether the interface will allow the inventory to be driven to either a negative quantity available, or a negative quantity on hand. Valid values are: blank – disallow negative quantity available; 1 – allow negative quantity available; 2 – disallow negative quantity on hand; Warning – allowing the available quantity to go negative is not compatible with using the weighted average cost function. cPO_EverestEventPoint06_EV06
Lots on Hold: Used to specify whether the interface will allow a transfer if the lot is on hold. Valid values are: 1 – allow transfers from/to lots on hold; and blank – do not allow transfers from/to lots on hold unless the lot status is defined in a lot group. cPO_EverestEventPoint07_EV07

Processing option data structure for DD3N4105

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

Type	Description	Parameter
String	szPO_Version_VERS	Input
String	szPO_DocumentType_DCT	Output
Char	cPO_DefaultPrimLocation_EV01	Output
String	szPO_JournalEntriesVers_VL01	Output
String	szPO_ItemLedgerVer_VL03	Output
String	szPO_WarehouseReqVer_VL04	Output
Char	cPO_DisplayOptions_EV02	Output
Char	cPO_RequireAcctNum_EV03	Output
Char	cPO_ProtectCosts_EV04	Output
Char	cPO_SummaryMode_EV05	Output
Char	cPO_AgreeAssignProcess_EV01	Output
Char	cPO_EverestEventPoint06_EV06	Output
Char	cPO_EverestEventPoint07_EV07	Output
Char	cPO_EverestEventPoint08_EV08	Output
String	szPO_OutInteropType_TYTN	Output
String	szLotGroup_LOTGRP	Output
String	szMatrixEntryVersion_VERS	Output
Char	cPOItemSearchSelect_EV01	Output
Char	cPOProdNoConsumption_EV01	Output

Processing options for Inventory Adjustments

Defaults tab

Document 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.
Location/Lot: If there is a value of 1 in this field, and no lot or location is passed in the interface, it will use the location and lot from the primary location. cEntera1todefaultfromprim_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. cProtectCosts_EV02.
Lot and Layering Fields: This field is used to specify whether the interface will allow changes to the Lot Status, Lot Description, Lot Grade, and Lot Potency fields. Valid values are: blank - do not allow changes; and “1” - allow changes. cLotLayering_EV05
Adjustment Quantity: Used to specify whether the interface will allow the inventory to be driven to either a negative quantity available, or a negative quantity on hand. Valid values are: blank – disallow negative quantity available; 1 – allow negative quantity available; 2 – disallow negative quantity on hand. Warning – allowing the available quantity to go negative is not compatible with using the weighted average cost function. cAllowQtyOverAvailable_EV05
Lots on Hold: Used to specify whether the interface will allow a transfer if the lot is on hold. Valid values are: 1 – allow transfers from/to lots on hold; and blank – do not allow transfers from/to lots on hold unless the lot status is defined in a lot group. cAllowHeldLots_EV06

Warehouse tab

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. cLicensePlate_EV01
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. cEntera1todefaultfromprim_EV01
Assign Items to License Plate 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. cAgreementAssignProcess_EV01

Processing Option Data Structure

Type	Description	Parameter
String	szVersion_VERS	Input
String	szDocumentType_DCT	Output
Char	cEntera1todefaultfromprim_EV01	Output
Char	cProtectCosts_EV02	Output
Char	cSummaryMode_EV03	Output
Char	cLotLayering_EV05	Output
Char	cAllowQtyOverAvailable_EV05	Output
Char	cAllowHeldLots_EV06	Output
String	szJournalEntriesVersion_VL01	Output
String	szItemLedgerVersion_VL03	Output
String	szWarehouseVersion_VL04	Output
Char	cAllowHeldLots_EV06	Output
String	szJournalEntriesVersion_VL01	Output
String	szItemLedgerVersion_VL03	Output
String	szWarehouseVersion_VL04	Output
String	szOutInteroperabilityType_TYTN	Output
Char	cAgreementAssignProcess_EV01	Output
Char	cLicensePlate_EV01	Output
String	szLotGroup_LOTG	Output
String	szLPNGenerationMethod_LPNG	Output
Char	cBuildStructure_EV01	Output
Char	cItemSearchAndSelect_EV01	Output
String	szMatrixEntryVersion_VERS	Output
Char	cProductionNoCumsumption_EV01	Output

Processing

Information about processing Inventory Issues and Adjustments.

Required fields

The MEP Action Code, Issue or Adjustment Flag, branch/plant, and quantity are required fields. These are the minimum requirements. If you are adjusting a specific location and/or lot, these fields would need to be entered. Is you want to enter a zero 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.
2 – Lots are assigned with next 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.
4 – Supplier, memo lot 1 required.
5 – Supplier, 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. Because you are transferring inventory, the lot must already exist for lot controlled items. The only information needed is the combination of item/location, and lot number, and the quantity.

Shelf Life Days, SLD

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

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 characteristic 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. For 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.

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, issue or Adjustment Flag (use “A” for adjustment), and lot number information if required. Typically, the document type is retrieved from the processing options of the version being used.

Action Code usage

The Inventory Activity interface can be used as a single-line transaction.

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

Action code	Description
0	Used to process a single-line transaction. Performs Begin Document, Edit Line, End Document, and Clear Cache.
L, S	Calls the MEP Serial Number Lookup business function to determine the “from” location. After the call is made, the action code is changed to a 0 and processed normally.

Verify the processing

Steps to verify the processing.

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

Open CARDEX.
Verify that there is an entry in the Item Ledger (menu G41112).
Verify that there is a journal entry in Inventory Journal Review (menu G41).

Step Information

Inventory Issues typically decrease inventory, however the transaction quantity is entered as a positive value. Inventory Adjustments typically increase inventory. If you wish to decrease inventory, a negative value must be entered for the transaction quantity. Typically you would use an inventory issue to decrease inventory.
In the details of the CARDEX entry that was created when the transfer ran, you will see a batch number that can be used to look up the journal entry that was created, and a document number that can be used to review the issue using the E1 application, Inventory Issues or the adjustment using the E1 application, Inventory Adjustment.
In the CARDEX entry, verify that there is a journal entry batch.
In Summary Availability, verify the following.
Step Information
For an Issue, there will be a decrease in inventory for the item/location/lot entered.

For an Adjustment, there will be inventory for the item/location/lot entered.
Optional. If the adjustment was made for a branch/plant that has license plating turned on, and the processing options were set to create a license plate, then use the License Plate Workbench (P46L10) to find the results of the transaction. Since the assigning of the license plate number is all done behind the scenes, this will require some investigation to find the license plate created. You can use the QBE fields to narrow the search.

Input data structure

Input data structure for DD3N4114.

Name	Default value	R/O	Alias	Notes
jdTransactionDate_TRDJ	Today's Date	X	TRDJ
szTransactionDocType_DCT	Processing Options	X, R	DCT	Required field. If the version does not have a default value, then the transaction must include the document type.
mnDocNumber_DOC		O	DOC	This field normally should be blank. EnterpriseOne will return this field.
mnBatchNumber_ICU		O	ICU	This field normally should be blank. EnterpriseOne will return this field.
szBranchPlant_MCU		R	MCU
szPrimaryItemNumber_UITM		R	UITM
szDisplayLocation_LOCNE1		O	LOCNE1	Can be unformatted but must have separators. If the processing option is set to default from primary, and no location is entered, the primary location will default into the transaction.
szLotNumber_LOTN		O, R	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.
szTransactionUOM_TRUM		O	TRUM	If no value is passed, the primary unit of measure will be used.
mnTransactionQty_TRQT		R	TRQT
mnTransactionUnitCost_UNCS		O	UNCS
mnTransactionExtendedCost_PAID		O	PAID
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.
cLotStatusCode_LOTS		O	LOTS
szReasonCode_RCD		O	RCD
jdExpirationDate_MMEJ		O, R	MMEJ	If the item is lot controlled, and there is no value in the shelf life days, this becomes a required field.
szLotDescription_LDSC		O	LDSC
jdGLDate_DGL	Today's Date	X	DGL
szMemoLot1_LOT1		O, R	LOT1	If the item is lot controlled, and set to require Memo Lot 1, this becomes a required field.
szMemoLot2_LOT2		O, R	LOT2	If the item is lot controlled, and set to require Memo Lot 2, this becomes a required field.
cdcLINKActionCode_EV01		R	EV01	0 = Single-line Transaction.
cActionCode_ACTION	C	X
jdDateUpated_UPMJ	Current Date	X		Retrieved from GetAuditInfo.
mnTimeUpdated_TDAY	Current Time	X		Retrieved from GetAuditInfo.
szUserId_USER	Current User	X		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.)
szWorkStationId_JOBN	Current Workstation	X		Retrieved from GetAuditInfo.
mnJobNumber_JOBS		O		This field normally should be blank. EnterpriseOne will return this field.
szProgramId_PID	ND3N4114	X		Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	X		If not passed in the ZJDE0001 version will be used. The processing options of this version will be used for error checking.
cSuppressErrMsg_EV01		O
szLotDescription_LDSC		O	LDSC
szLotDescription_LDSC		O	LDSC
jdGLDate_DGL	Today's Date	X	DGL
szMemoLot1_LOT1		O, R	LOT1	If the item is lot controlled, and set to require Memo Lot 1, this becomes a required field.
szMemoLot2_LOT2		O, R	LOT2	If the item is lot controlled, and set to require Memo Lot 2, this becomes a required field.
cdcLINKActionCode_EV01		R	EV01	0 = Single-line Transaction.
cActionCode_ACTION	C	X
jdDateUpated_UPMJ	Current Date	X		Retrieved from GetAuditInfo.
mnTimeUpdated_TDAY	Current Time	X		Retrieved from GetAuditInfo.
szUserId_USER	Current User	X		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.)
szWorkStationId_JOBN	Current Workstation	X		Retrieved from GetAuditInfo.
mnJobNumber_JOBS		O		This field normally should be blank. EnterpriseOne will return this field.
szProgramId_PID	ND3N4114	X		Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	X		If not passed in the ZJDE0001 version will be used. The processing options of this version will be used for error checking.
cSuppressErrMsg_EV01		O
cErrorCode_ERRC	Blank	X		This is a return value. 1 = warning 2 = error
szErrorMessageKey_EKEY	Blanks	X		This value is returned and will contain the alias of the error message.
iDebugLevel_INT01		O		Displays M&D Debus statements if the value is greater than zero.
szExplanationTransaction_TREX		O
szAcctNoInputMode_ANI		O
szSubledger_SBL		O
cSubledgerType_SBLT		O
szPhase_WR01		O
szAssetNumberInput_ASII		O
mn0911JobNumber_JOBS		O		This field normally should be blank. EnterpriseOne will return this field.
cZeroCostEntered_EV09		O		Normally blank. If you are trying to manually enter a zero cost, this must be set to 1.
cIssue_or_AdjFlag_EV01		R	EV01	A = Inventory Adjustment I = Inventory Issue
szDocumentKeyCompany_KC0		O	KCO	This field normally should be blank. EnterpriseOne will return this field.
cBatchStatus_EV01		O	EV01	This field normally should be blank. EnterpriseOne will return this field.
mnPreviousLineNumber_LNID		O	LNID	This field normally should be blank. EnterpriseOne will return this field.
mnLastJELine_JELN		O	JELN	This field normally should be blank. EnterpriseOne will return this field.
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.
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.
jdLotEffectivityDate_DLEJ		O	DLEJ
szLicensePlateNumber_LPNU		O	LPNU	The value in this field indicates the license plate that contains the item to be issued. This field is not used with inventory adjustments. If a license plate(s) is created, it is done automatically using system defaults. If a user wants control over the license plate number that is created, then they need to use ND3N6L30 not inventory adjustments.

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.

Field name	Adjustment non-lot controlled item	Adjustment dual/lot controlled	Adjustment forcing a zero cost	Adjustment passing in document type and doing a negative adjustment	Adjustment utilitzing auditing with a lot controlled item with no default in shelf life days	Adjustment utilizing auditing and signature capture
szTransactionDocType_DCT				IS
szBranchPlant_MCU	W10	W10	W10	W10	W10
szPrimaryItemNumber_UITM	A1001	DL1001	A1001	A1001	L2001
szDisplayLocation_LOCNE1	02AAA01	03AAA01	04AAA01	05AAA01	01AAA01
szLotNumber_LOTN		LOTXYZ			LOTABC
szTransactionUOM_TRUM	CA	RL	EA	EA	EA
mnTransactionQty_TRQT	2	1	1	-2	100
mnTransactionUnitCost_UNCS			0
jdExpirationDate_MMEJ					12/10/2010
cdcLINKActionCode_EV01	0	0	0	0	0	0
szUserId_USER	MEP01	MEP01	MEP01	MEP01	MEP01	MEP01
szVersion_VERS	ZJDE0001	ZJDE0001	ZJDE0001	ZJDE0001	ZJDE0001	ZJDE0001
cZeroCostEntered_EV09			1
cIssue_or_AdjFlag_EV01	A	A	A	A	A	A
szGuidApprover1_USR1						MEPUSER
szGuidFullName1_FULLNAME1						MEP User
mnGuidReasonCode1_REASON1					01	01
szGuidScriptID_FMNMVERS						IA
mnSecondaryQty_SQOR		103
szSecondaryUoM_UOM2		LF
szTransactionDocType_DCT				IS
szBranchPlant_MCU	W10	W10	W10	W10	W10
szPrimaryItemNumber_UITM	A1001	DL1001	A1001	A1001	L2001
szDisplayLocation_LOCNE1	02AAA01	03AAA01	04AAA01	05AAA01	01AAA01
szLotNumber_LOTN		LOTXYZ			LOTABC
szTransactionUOM_TRUM	CA	RL	EA	EA	EA
mnTransactionQty_TRQT	2	1	1	2	100
mnTransactionUnitCost_UNCS			0
jdGLDate_DGL
cdcLINKActionCode_EV01	0	0	0	0	0	0
szUserId_USER	MEP01	MEP01	MEP01	MEP01	MEP01	MEP01
szVersion_VERS	ZJDE0001	ZJDE0001	ZJDE0001	ZJDE0001	ZJDE0001	ZJDE0001
cZeroCostEntered_EV09			1
cIssue_or_AdjFlag_EV01	I	I	I	I	I	I
szGuidApprover1_USR1						MEPUSER
szGuidFullName1_FULLNAME1						MEP User
mnGuidReasonCode1_REASON1					01	01
szGuidScriptID_FMNMVERS						II
mnSecondaryQty_SQOR		101
szSecondaryUoM_UOM2		LF
jdLotEffectivityDate_DLEJ
szLIcensePlateNumber_LPNU

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. cdcLINKActionCode only valid with values 0,2,3,4,5, and 8.
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 the issue/adjustment flag (cIssue_or_AdjFlag_EV01) is not equal to ‘I' or ‘A'. This same message can be generated if the secondary quantity is null/blank/zero, and the primary quantity is null/blank/zero.
0013	Entry Invalid. JDE master business function failed.
010U	Invalid Item Number. The item number cannot be left blank.
4718	Supplier and Memo Lot 1 Must be Entered. Memo Lot 1 cannot be blank when the serial number is a required field.
4773	Supplier, Memo Lot 1 & 2 must be entered. Memo Lot 2 cannot be blank when the serial number is a required field.
460U	Invalid License Plate Number. This error is returned if the transaction being processed is an adjustment, and the license plate number is greater than blanks.

There was a problem loading this topic

Mobile Enterprise Platform