send feedback

❮ Previous Next ❯

Kanban Ad Hoc Card Insertion interface for JD Edwards

About the Kanban Ad Hoc Card Insertion interface

Kanban ad hoc card insertion is meant to be a temporary way to ensure that the in-process inventory will cover the demand.

For a unique combination of supplying branch, consuming branch, supplying location, and consuming location, you can add one, and only one, ad hoc ID. You must have at least one non-ad hoc Kanban ID that exists for the combination of supplying branch, supplying location, consuming location, consuming branch, and item. An ad hoc Kanban ID cannot be the first or only Kanban ID for an item. Ad hoc Kanban information is excluded from the Kanban Size Calculation (R30450) and the Kanban Replenishment Capacity (P3019) programs because the demand is uncertain and not planned. The interface to add an ad hoc Kanban ID in dcLINK is ND3N3016. It calls the ‘C' business function BD3N3001 to retrieve its processing options.

Name	Function name	Description
DD3N3016		dcLINK Interface Kanban Adhoc Card Insertion
ND3N3016	dcLINKInterfaceKanbanAdhocCardIn	dcLINK Interface Kanban Adhoc Card Insertion
DD3N3001		PO Retrieval Kanban Adhoc Card Insertion
BD3N3001	PORetrieveKanbanAdHocCardInsert	PO Retrieval Kanban Adhoc Card Insertion

The full name of this interface is ND3N3016 Kanban Ad Hoc Card Insertion

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 insert an Ad Hoc Kanban card is P3016. Choose revisions and the ad hoc insertion can be found as a form exit. The menu to find P3016 is G30411

Processing options

Processing options for the Kanban Ad Hoc Card Insertion interface.

The dream writer version will default to ZJDE0001 if not otherwise specified in the parameter list on the call. There are only two processing options, and the only one dcLINK cares about is on the process tab.

Process tab

Create an Ad Hoc Card – a ‘1' allows the entry of an ad hoc card. Blank does not.

Processing option data structure for DD3N3001

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

Type	Description	Parameter
String	szVersion_VERS	Input
String	szKanbanSizeCalcVersion_VERS	Output
Char	cCreateAdhocCard_EV01	Output

Processing

This interface is used to create a temporary Kanban ID.

This interface is used for creating a temporary Kanban ID. What needs to be passed in is all the things you would need to pass in to setup a normal Kanban ID. The idea behind an ad hoc Kanban ID is that it is created to supplement an existing Kanban ID. The consuming branch, consuming location, supplying branch, supplying location, and item needs to match the existing Kanban ID. If an ad hoc card already exists, then an error message will be displayed.

Required fields

The following fields are required when adding an Ad Hoc card insertion: the consuming branch, the consuming location, the supplying branch, the supplying location, and the item number. These five fields are used to find the “original” Kanban record (and verify that an Ad Hoc record does not already exist), the Kanban size, the unit of measure, the source type, and the phase.

Best practice

The container size is not a required field, but if it is left blank the default is considered 1. This means that the number of cards will equal the Kanban size. The formula for calculating the number of cards is: Kanban size, divided by container size, equals the number of cards. Since this may not be valid, it is best to include the container size when creating an Ad Hoc card.

Verify the processing

Steps to verify the processing

This interface is performing a purely file maintenance task. There will be no entries in CARDEX, summary availability will not be affected, and no work orders/purchase orders are created as a result of creating the Ad Hoc card. The only place you can see a change is in the Kanban master file (F3016).

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

Open the E1 application used to create Kanban masters.
Scroll the screen to the right to the Ad Hoc Card Exists column.
If the processing was successful, a Y will display in the Ad Hoc Card Exists column.

Input data structure

Input data structure for DD3N3016.

Name	Default value	R/O	Alias	Notes
cdcLINKActionCode_EV01		X	EV01
cActionCode_ACTION		X	ACTION
jdDateUpdated_UPMJ	Current Date	X	UPMJ	Retrieved from GetAuditInfo.
mnTimeUpdated_UPMT	Current Time	X	TDAY	Retrieved from GetAuditInfo.
szUserId_USER	Current User	X	USER	Retrieved from GetAuditInfo.
szWorkStationId_JOBN	Current Workstation	X	JOBN	Retrieved from GetAuditInfo.
szMachineKey_MKEY	Current Machine	X	MKEY	Retrieved from GetAuditInfo.
mnJobnumber_JOBS		o	JOBS
szProgramId_PID	ND3N3016	X	PID	Defaulted in program if not passed in.
szVersion_VERS	ZJDE0001	X	VERS	Defaulted in program if not passed in.
cSuppressErrorMsg_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.
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 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 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.
szUnknownItem_UITM		O	UITM	Not used in this NER.
szConsumingBranch_MMCU		R	MMCU	This field is part of the key to look up the “permanent” Kanban master. You cannot add an Ad Hoc record if there is not a “permanent” Kanban master for a given consuming branch, supplying branch, consuming location, and supplying location combination.
szSupplyingBranch_MCU		R	MCU	This field is part of the key to look up the “permanent” Kanban master. You cannot add an Ad Hoc record if there is not a “permanent” Kanban master for a given consuming branch, supplying branch, consuming location, and supplying location combination.
szConsumingLocation_TLOC		R	TLOC	This field is part of the key to look up the “permanent” Kanban master. You cannot add an Ad Hoc record if there is not a “permanent” Kanban master for a given consuming branch, supplying branch, consuming location,n and supplying location combination.
szSupplyingLocation_LOCN		R	LOCN	This field is part of the key to look up the “permanent” Kanban master. You cannot add an Ad Hoc record if there is not a “permanent” Kanban master for a given consuming branch, supplying branch, consuming location, and supplying location combination.
mnKanbanID_KID1		O	KID1	Not used in this NER.
mnKanbanSize_KBQT		R	KBQT	This is the total size of the Kanban.
szUnitOfMeasure_UOM		R	UOM	A value must be passed in this field.
sz2ndItem_LITM		R	LITM	The item number must be passed in one of these fields: 2^nd, short, or 3^rd. An error will be returned if all three fields are blank.
mnShortItem_ITM		R	ITM	The item number must be passed in one of these fields: 2^nd, short, or 3^rd. An error will be returned if all three fields are blank.
sz3rdItem_AITM		R	AITM	The item number must be passed in one of these fields: 2^nd, short, or 3^rd. An error will be returned if all three fields are blank.
cSourceType_REPT		R	REPT	The value entered in this field is validated against the UDC table 31/RS. Valid values are: 0 = DFM Raw and In Process 1 = Work Center 2 = Inventory 3 = Supplier 4 = Outside Assembly 5 = Transfer Order 6 = DFM Dual Card
cPhases_KBTM		R	KBTM	The value entered in this field is validated against the UDC table 31/TM. Valid values are: 1 = One phase transfer 2 = Two phase transfer
mnSupplier_AN8		O, R	AN8	If the Ad Hoc line being created is a type 3 or 4 for supplier, then the supplier number should be passed into this NER.
szLineCellIdentifier_LINE		O	LINE
mnContainerSize_CNTS		O	CNTS	This is the capacity of the container being used to supply the consuming location. This field works in conjunction with the Kanban size. If the size of the Kanban is 50, how many of those 50 will fit in this container.
cOverride_KBOV		O	KBOV
cReceipts_KBRC		O	KBRC	Used when working with purchase orders. Valid values are: 0 = the system does not run the receipt process 1 = the system does run the receipt process
mnNumberOfKanbanCards_KBNC		O	KBNC	This defines the number of cards for the Kanban. Each card represents a container. The Kanban size, divided by the container size, equals the number of cards.
szCalculationMethod_CALCID		O	CALCID
mnRelatedKanbanID_KID2		O	KID2
cAdHocCardExists_EV01		O	EV01	After the successful addition of an Ad Hoc card the system will display a ‘Y' in this field on the Ad Hoc card.

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.

The data structure fields are in the left column, and the corresponding values for each scenario are listed by column.

Field name	Adding ad hoc card
cdcLINKActionCode_EV01
cActionCode_ACTION
jdDateUpdated_UPMJ
mnTimeUpdated_UPMT
szUserId_USER	Elvis
szWorkStationId_JOBN
szMachineKey_MKEY
mnJobnumber_JOBS
szProgramId_PID
szVersion_VERS	ZJDE0001
cSuppressErrorMsg_EV01
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
szGuidUniqueID_GUID
szGuidApprover1_USR1
szGuidFullName1_FULLNAME1
szGuidApprover2_USR2
szGuidFullName2_FULLNAME2
mnGuidReasonCode1_REASON1
szGuidCommentField_COMMENTS
mnGuidReasonCode2_REASON2
szGuidCommentField2_2COMMENTS
szGuidScriptID_FMNMVERS
szGuidTextMessage_TEXTMES
szUnknownItem_UITM
szConsumingBranch_MMCU	M30
szSupplyingBranch_MCU	M30
szConsumingLocation_TLOC	LA.80 .
szSupplyingLocation_LOCN	LC.50 .
mnKanbanID_KID1
mnKanbanSize_KBQT	60
szUnitOfMeasure_UOM	EA
sz2ndItem_LITM	2037
mnShortItem_ITM
sz3rdItem_AITM
cSourceType_REPT	1
cPhases_KBTM	1
mnSupplier_AN8
szLineCellIdentifier_LINE
mnContainerSize_CNTS	60
cOverride_KBOV
cReceipts_KBRC
mnNumberOfKanbanCards_KBNC
szCalculationMethod_CALCID
mnRelatedKanbanID_KID2
cAdHocCardExists_EV01

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
0003	Blanks Invalid. This error message will be returned for any of the following reasons. No value was passed into this NER for the consuming branch (szConsumingBranch_MMCU). No value was passed into this NER for the supplying branch (szSupplyingBranch_MCU). No value was passed into this NER for the Kanban size (mnKanbanSize_KBQT). No value was passed into this NER for the Unit of Measure (szUnitOfMeasure_UOM).
004G	Item Number Invalid. The item number needs to be passed in. It can be in either the 2^nd item number field, the short item number field, or the 3^rd item number field.
018A	Code not found in User Defined Code. This error message is returned if the phase (cPhases_KBTM) was left blank, or the phase passed in is not in the UDC table 31/TM.
116W	Source Type is Blank. This error message is returned if the source type (cSourceType_REPT) was left blank, or the source type is not in the UDC table 31/RS.
128J	Insert Failed. The insert of the Kanban Ad Hoc record into the Kanban Master (F3016) failed.
3016D	AdHoc Cannot Be Created. This error message is returned if the processing options are set to not allow Kanban Ad Hoc cards to be created.
3016E	AdHoc Card exists in Kanban Master. There can only be one Ad Hoc card associated with each Kanban master. This message is returned if the Kanban master already has an Ad Hoc card associated with it.

There was a problem loading this topic

Mobile Enterprise Platform