Signature Capture interface for JD Edwards

About the dcLINK Signature Capture interface

The dcLINK Media Object Long Text function is used to write the location of an image file to the F00165, so that the file can be viewed through JDE. The ND3N0006 interface was written in NER.

Name	Function Name	Description
ND3N0006	dcLINKSignatureCapture	dcLINK Interface Signature Capture
DD3N0006C		dcLINK Interface Signature Capture

This interface has no processing options.

This guide applies to the newest version of the ERP.

Processing

Depending upon the cdcLINKActionCode used, the interface will write the record to the F00165 table for an image file (JPG, PNG, etc.) or a different kind of file (PDF, DOC, etc.).

Verify the processing

View the media object to verify that it opens within JDE.

Input data structure - DD3N0006C

Name	R/O	Notes
cdcLINKActionCode_EV01	X	‘1' to add an image file, ‘2' to add a different kind of file. Will default to a ‘1' if not passed in.
cActionCode_ACTION		This is not used in this interface.
jdDateUpdated_UPMJ	X	Retrieved from GetAuditInfo.
mnTimeUpdated_TDAY	X	Retrieved from GetAuditInfo.
szUserId_USER	X	Retrieved from GetAuditInfo.
szWorkStationId_JOBN	X	Retrieved from GetAuditInfo.
mnJobNumber_JOBS		This is not used in this interface.
szProgramId_PID		This is not used in this interface.
szVersion_VERS		This is not used in this interface.
cSuppressErrorMessage_EV01		This is not used in this interface.
cErrorCode_ERRC
szErrorMessageKey_EKEY
iDebugLevel_INT01
szMachineKey_MKEY		This is not used in this interface.
szGTObjectName_OBNM	R	This is required. This corresponds to the GDOBNM field in the F00165.
szImageName_GTFILENM	R	This is the name of the image being used.
szQueueName_QUNAM	R	This is the name of the media object queue that the object will be placed in.
szGTItemName_GTITNM	X	This will default to ‘Image' or ‘Document' by the system if it is not passed in. It corresponds to the GDGTITNM in the F00165.
szKey1In_DS50	R	Part one of the key. It corresponds to the GDTXKY field in the F00165.
szKey2In_DS50	O	If any additional key fields are needed, use these fields to add them. The interface will concatenate them together, starting with szKey1In_DS50.
szKey3In_DS50	O
szKey4In_DS50	O
szKey5In_DS50	O
szKeyOut_MOTXKY	R	This is the returned key field. It corresponds to the GDTXKY field in the F00165.
mnSequenceNumber_MOSEQN	O	This will be calculated within the interface.
szMobileOrderNumber_DS50	O	This is used for MOBILEApps processing.
Globally Unique Identifier (GUID) Fields	O	GUID values are all optional unless a business must comply with FDA 21 CFR Part 11 auditing requirements. Refer to the Special Processing Interface Usage Guide for GUID Input Data Structure details.

R = Required (shaded in blue for quick reference)

O = Optional

X = Required, but will default in if not passed

C = Conditional (see explanation for conditions)

Additional information

The following notes apply to the Signature Capture interface.

The user will have to determine the media object data structure (the GTxxxx) which is entered into the GTObjectName field. The user will also have to determine the key for that record. In some instances, it will be a simple key (shipment number or short item number, for instance).
If a line number needs to be formatted in a particular way (if it is part of the key), it needs to be formatted prior to passing it into the Key field. For instance, the sales order detail line number needs to be passed in as 1.000 (as it does when done through JDE). If it is not passed in with the decimal formatting (ie, passing it in as 1), it will not appear on the application, but it will be in the F00165.
We do not validate any of the key data.

There was a problem loading this topic