Inventory Cycle Count Entry interface for JD Edwards

About the Cycle Count Entry interface

This NER will update the cycle count transaction file (F4141) with cycle count transactions that have been entered through Mobile Enterprise Platform.

Count information can either replace what has already been entered into the cycle count transaction file, or accumulate to the counts already entered. The Mobile Enterprise Platform NER that is called is ND3N4141. This interface was written in NER and calls ‘C' business function, BD3N4102, to retrieve the processing options.

Name	Function Name	Description
DD3N4141	dcLINKCycleCountEntry	dcLINK Interface – Cycle Count Entry
ND3N4141	dcLINKCycleCountEntry	dcLINK Interface – Cycle Count Entry
DD3N4102	PORetrievalCycleCountEntry	PO Retrieval – Cycle Count Entry
BD3N4102	PORetrievalCycleCountEntry	PO Retrieval – Cycle Count Entry

In EnterpriseOne, the application you would run to enter an inventory count is P4141, Cycle Count Entry. P4141 can be accessed from the menu G4121.

In EnterpriseOne, all the items/locations that have been selected to be counted are shown in the grid. In Mobile Enterprise Platform, each grid row would be a different transaction that is scanned/entered and then sent to be updated to E1.

The full name of this interface is ND3N4141 – Cycle Count Entry.

This interface guide applies to the following JDE versions.

EnterpriseOne 9.1
EnterpriseOne 9.2

Processing options

The interactive version will default to ZJDE0001, if not otherwise specified in the parameter list on the call. This interface calls BD3N4102 to get the cycle count processing options. The processing options that are retrieved and used by P4141 are actually stored under the P41240 – Cycle Count Review.

Default tab

From Cycle status – this status is used by ND3N4141 to validate that the cycle count that is being processed is at the correct status to be processed. Any cycle count whose status is less than this From status will error out.

Thru Cycle Status – this status is used by ND3N4141 to validate that the cycle count that is being processed is at the correct status to be processed. Any cycle count whose status is greater than this Thru status will error out.

Processing option data structure - DD3N4102

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

TYPE	DESCRIPTION	PARAMETER
String	szPOVersion_VERS	Input
String	szFromCycleStatus_CYCS	Output
String	szThruCycleStatus2_CYCS2	Output
String	szCycleCountPrintVersion_VL01	Output
String	szCycleCountUpdateVersion_VL02	Output
Char	cManualLicensePlate_EV01	Output

Processing

This business function updates the cycle count transaction file with counts entered through Mobile Enterprise Platform.

Options can be used to accumulate the counts submitted, which is helpful if multiple people are counting an item. Or they can be used to replace any existing counts, which is helpful if an error was made and counting needed to be redone.

The counted by field is not required but can be very helpful for people that review and troubleshoot the entered cycle counts.

Required fields

The branch/plant, item number, cycle count number, and transaction quantity are required fields. If the item being counted exists in more than one location, or in more than one lot, then a best practice would be to also include location and lot in the data collected for this transaction.

Verifying the processing

All Mobile Enterprise Platform does is update the cycle count transaction file to verify that the transaction processed is the file that needs to be reviewed. The best way to review the file is to use the E1 application. The Cycle Count Entry program in E1. Prior to this a transaction was entered via Mobile Enterprise Platform to count 50 of item 210 in the blank ( . . ) location. What we would expect to see when we re-inquire on the entry screen is that it now shows that there is a count for 50.

License plates

In the E1 application, there is a row exit called LPN Detail Entry that allows users to record by license plate the quantity for each item. When that row exit is called, it is calling a different program, P46L42, that actually allows you to enter a count against a specific license plate. Likewise, Mobile Enterprise Platform has a separate NER that allows entry of counts against specific license plates. That NER is ND3N6L42.

dcLINKACTION Code	Description
0	Always defaults to 0. No different action takes place based on this code.

Input data structure - DD3N4141

NAME	DEFAULT VALUE	R/O	ALIAS	Notes
szBranchPlant_MCU	N/A	r	MCU	This is the branch/plant that the item being counted is assigned to.
szItemNoUnknownFormat_UITM	N/A	r	UITM	This is the item that is being counted.
szFormattedLocation_LOCNE1	N/A	o	LOCNE1	This is the location where the item is being counted. Technically it is not a required field, but it is strongly suggested that it be included on each transaction.
szUnitOfMeasure_UOM	N/A	o	UOM
mnCycleCountNumber_CYNO	N/A	r	CYNO	Before an item can be counted, a cycle count has to be created in E1. When a cycle count is generated, it is given a number, and items are assigned to this cycle count. It is that number that needs to be entered into this field.
mnJobNumber_JOBS	N/A	o	JOBS
cActionCode_ACTION	N/A	o	ACTION	This field is not used in this NER.
mnTransactionQty_TRQT	N/A	r	TRQT	This is the quantity of the item that was counted.
szSalesReportingCode1_SRP1	N/A	o	SRP1
szSalesReportingCode2_SRP2	N/A	o	SRP2
szSalesReportingCode3_SRP3	N/A	o	SRP3
szSalesReportingCode4_SRP4	N/A	o	SRP4
szSalesReportingCode5_SRP5	N/A	o	SRP5
szCountedBy_CNTB	N/A	o	CNTB	Enter the name of the person who is reporting the counts.
jdDateCounted_CNTJ	N/A	o	CNTJ	If not entered this will default to today's date.
cCycleCountNumber_CCCD	N/A	o	CCCD
dcLINKActionCode_EV01	0	x	EV01	Always defaults to a 0. No different action takes place based on this code.
cdcLINKReplaceCounts_EV01	N/A	o	EV01	Blank – accumulate the count 'l' - replace the count
jdDateUpdated_UPMJ	Current Date	x	UPMJ	Retrieved from GetAuditInfo
mnTimeOfDay_TDAY	Current Time	x	UPMT	Retrieved from GetAuditInfo
szUserId_USER	Current User	x	USER	Retrieved from GetAuditInfo
szWorkStationId_JOBN	Current Workstation	x	JOBN	Retrieved from GetAuditInfo
szProgramId_PID	ND3N4141	x	PID	Defaulted in program if not passed in
szVersion_VERS	ZJDE0001	x	VERS	Defaulted in program if not passed in
cSuppressErrMsg_EV01	N/A	o	EV01
cErrorCode_ERRC	Blanks	x	ERRC	Defaulted in program
szErrorMessageKey_EKEY	Blanks	x	EKEY	Defaulted in program
iDebugLevel_INT01	N/A	o	INT01	Displays M&D Debug statements if the value is greater than 0
szLot_LOTN	N/A	o	LOTN	If the item being counted is a lot control item, then this becomes a required field, in order to differentiate between this item, and the same item in a different lot.
szGuidUniqueID_GUID	Automatically generated by Mobile Enterprise Platform	o	CFRGUID	If generate unique identifier (GUID) is turned on in the Mobile Enterprise Platform configuration utility, this field will contain a GUID. The GUID is used to tie database changes in PeopleSoft to the transactions that triggered those changes to occur.
szGuidApprover1_USR1	N/A	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 Mobile Enterprise Platform. 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	N/A	o	FULLNAME1	This field is the full name of the GUID Approver 1.
szGuidApprover2_USR2	N/A	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	N/A	o	FULLNAME2	This field is the full name of the GUID Approver 2.
mnGuidReasonCode1_REASON1	N/A	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	N/A	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	N/A	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	N/A	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	N/A	o	FMNMVERS	The screen ID in PeopleSoft where the change was made is captured. MEP captures the script ID.
szGuidTextMessage_TEXTMES	N/A	o	TEXTMES	This is a free form entry field.
mnSecondaryQty_SQOR	N/A	o	SQOR	If the item is a DUAL unit of measure item this is the secondary quantity.
szSecondaryUM_UOM2	N/A	o	UOM2	If this item is a DUAL unit of measure item this is the secondary unit of measure.
szProductionNumber_PMPN	N/A	o	PMPN	Pass value for Production Number

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, as well as the fields that would be passed for each scenario. The data structure fields are in the left column. The corresponding values for each scenario are listed by column.

Field Name	Replace a Count	Accumulate a Count
szBranchPlant_MCU	W30	W30
szItemNoUnknownFormat_UITM	VIT	220
mnCycleCountNumber_CYNO	295	295
mnTransactionQty_TRQT	75	50
szCountedBy_CNTB	Elvis	Elvis
dcLINKActionCode_EV01	0	0
cdcLINKReplaceCounts_EV01	1	N/A
szUserId_USER	Elvis	Elvis
szLot_LOTN	2.006E+11	N/A

Common error messages

The following table describes the common error messages that can be generated by this BF and what those error messages mean.

ERROR MESSAGE	MEANING
0002	Record Invalid This overused error message can be received if any of the following situations are true: 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. The read of the cycle count header file (F4140) fails. The key is the cycle count number. The cycle count status from the cycle count header file is less than the “from” status returned from the processing options, or greater than the “to” status returned from the processing options. The cycle count status from the cycle count header file is equal to 50, 60, or 99. An error was encountered in calling either the Verify and Get Item Master with Short or Unknown Item or the F4101 Get Item Master Information business functions.
006J	Invalid Unit of Measure The unit of measure passed into this business function does not exist in the UDC table 00/UM.
141B	Blanks Invalid This error message will be received if either the item number is not passed in, or the cycle count number is not passed in.
4065	Bulk Inventory Transaction Not Allowed The item number being processed is setup in the Item Master as a bulk pick item, which is not allowed in cycle count entry.
4213	Need Specific Branch/Plant No branch/plant was passed in, and it is a required field.

References

The following table describes any 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
BD3N4102	PO Retrieval – Cycle Count Entry
DD3N4102	PO Retrieval – Cycle Count Entry
ND3NGUID	dcLINK Utility Write Signature Capture
DD3NGUID	dcLINK Utility Write Signature Capture

There was a problem loading this topic