send feedback

❮ Previous Next ❯

Failure Analysis interface for JD Edwards

About the Failure Analysis interface

The Failure Analysis interface allows the association of failures, analyses, and resolutions with maintenance requests and work orders.

In order to utilize failure analysis, a failure record must be attached to a work order or maintenance request. Afterwards, an analysis and resolution may be attached to that failure.

When you enter the failure analysis database from a work order or maintenance request, the system displays the failure that is associated with the issue. If a standard, reusable failure was used, the failure entry information is disabled. If a non-standard failure was used, the failure fields are enabled.

This interface calls the BD3N1702 business function to retrieve the processing options from the interactive program, P17766.

Name	Function Name	Description
DD3N1767		dcLINK Failure Analysis Data Structure
ND3N1767	dcLINK Interface - Failure Analysis	dcLINK Failure Analysis
DD3N1702		PO Retrieval – Failure Analysis – P17766 Data Structure
BD3N1702	PORetrievalFailureAnalysisP17766	PO Retrieval – Failure Analysis – P17766

This guide applies to the newest version of the ERP.

Corresponding EnterpriseOne application

In EnterpriseOne, the application you would run to launch Speed Time Entry is P17767. The menu to find Failure Analysis > Daily Failure Analysis Processing > Failure Analysis is G1709.

Verifying the process

There are several places a person can look to verify a warehouse confirmation transaction worked. Deep down, a warehouse confirmation transaction is a glorified inventory movement, so, many of the places where you would look to verify an inventory transaction are the exact same places you will look to verify a warehouse confirmation.

Processing options

This interface requires processing options from P17767 program. A version will default to ZJDE0001 if not otherwise specified in the parameter list on the call.

Defaults tab

Failure Analysis Type (cKnowledgeType_KNLT) - This field indicates the default failure analysis type. Valid values are: blank - All types, “1” - Failure, “2” - Analysis, and “3” - Resolution.
Failure Analysis Approval Flag (cKnowlBaseApprovalType_KBAPF) - This field indicates the option to use for failure analysis approval.
Order Type (szOrderType_DCTO) - This field specifies the order type to use.
Product Family (szProductFamily_PRODF) - This field specifies the product family to include.
Product Model (szProductModel_PRODM) - This field specifies the product model to include.
Product Component (szProductComponent_PRODC) - This field specifies the product component to include.
Environment (szEnvironment_ENV) - This field specifies the environment to use.

Process tab

Media Object Display (cMediaObjectDisplay_EV01) – This field indicates how to display media objects. Valid values are: blank - Display first generic text item, “1” - Display first image item, “2” - Display first OLE item, and “3” - Display first URL/File item (FUTURE).
Approvals Access (cApprovalAccess_EV01) - This field indicates whether to allow access to approvals. Valid values are: blank - Do not allow access to approvals, and “1” - Allow access to approvals.

Versions tab

Failure Analysis Revisions (P17767) Version (szP17767Version_VER1) - This field specifies which version of the Failure Analysis Revisions program to use. If blank, the Version will default to “ZJDE0001”.

Processing option data structure

The following processing options are available for data structure DD3N1702. The interface retrieves these parameters by calling BD3N1702.They are passed back in the following data structure.

Type	Description	Parameter
String	szPOVersion_VERS	Input
Char	cDisplayFailureCodes_EV01	Output
Char	cDisplayAnalysis_EV01	Output
Char	cDisplayAnalysisCodes_EV01	Output
Char	cDisplayResolution_EV01	Output
Char	cDisplayResolutionCodes_EV01	Output
Char	cFAModication_EV01	Output
Char	cKnowledgeType_KNLT	Output
Char	cKnowlBaseApprovalType_KBAPF	Output
String	szOrderType_DCTO	Output
String	szProductFamily_PRODF	Output
String	szProductModel_PRODM	Output
String	szProductComponent_PRODC	Output
String	szEnvironment_ENV	Output
Char	cMediaObjectDisplay_EV01	Output
String	szP17767Version_VER1	Output
Char	cApprovalAccess_EV01	Output

Processing

The characteristics of an item determine which processing fields are required by the interface.

Some characteristics are set at the item master level, and some are set at the item/branch level. The item/branch level always takes precedence over the item master. Refer to the Special Processing Interface Usage Guide for more information.

Action Code	Advanced Inventory Action Code	Description
	A	Analysis
	F	Failure
	R	Resolution
A		Add mode
C		Change mode

Required fields for Analysis action

When dcLINKActionCode = 'A': Add Analysis Record, the following fields are required.

BF cdcLINKActionCode
BF cActionCode_ACTION
BF mnOrderNumber_DOCO
BF szOrderType_DCTO
BF cKnowledgeType_KNLT
BF szMediaObjectText_CURRENT
BF szDescription_DS01

Required fields for Failure action

When dcLINKActionCode = 'F': Add Failure Record, the following fields are required.

BF cdcLINKActionCode
BF cActionCode_ACTION
BF mnOrderNumber_DOCO
BF szOrderType_DCTO
BF cKnowledgeType_KNLT
BF szMediaObjectText_CURRENT
BF szDescription_DS01

Expanded fields:

szKBTreeName_KBTNM
szKnowledgeCode1_KBCO
szKnowledgeCode2_KBCO
szKnowledgeCode3_KBCO

Required fields for Resolution action

When dcLINKActionCode = 'R': Add Resolution Record, the following fields are required.

BF cdcLINKActionCode
BF cActionCode_ACTION
BF mnOrderNumber_DOCO
BF szOrderType_DCTO
BF cKnowledgeType_KNLT
BF szMediaObjectText_CURRENT
BF szDescription_DS01
BF szEquipmentNumber_ASII
BF szUnkownItemNumber_UITM

Verify the processing

Steps to verify the Failure Analysis process.

To verify that the processing completed successfully, complete the following steps in JDE.

On the Maintenance Request menu (G1709), select Maintenance Request Entry.
In the Work with Maintenance Requests dialog box, locate a specific maintenance request, select the request, and then click Select.
In the Maintenance Request Entry dialog box, in the Form menu, select Failure Analysis.
Select Add/Revise FA to display the record.

Step Information

Input data structure

The following table describes the input data structure for DD3N1767.

In the following table, r indicates Required, o indicates Optional, c indicates Conditional, and x indicates that the item is Required but will default in if not passed.

Name	Default Value	R/O	Alias	Notes
cdcLINKActionCode_EV01		R	EV01	See Notes – dcLINK Action Code Usage section below
cActionCode_ACTION		O	ACTION
jdDateUpdated_UPMJ	Current Date	X	UPMJ	This field is retrieved from GetAuditInfo.
mnTimeUpdated_UPMT	Current Time	X	UPMT	This field is retrieved from GetAuditInfo.
szUserId_USER	Current User	X	USER	If this field is not passed in, a value is retrieved from GetAuditInfo.
szWorkStationId_JOBN	Current Workstation	X	JOBN	This field is retrieved from GetAuditInfo.
mnJobnumber_JOBS		O	JOBS
szProgramId_PID	ND3N1767	X	PID	This field defaults in the program if not passed in.
szVersion_VERS	ZJDE0001	X	VERS	If not passed in, the ZJDE0001 version is used.
cSuppressErrorMessage_EV01		O	EV01
cErrorCode_ERRC		X	ERRC	This is a returned value. “1” = warning, “2” = error.
szErrorMessageKey_EKEY		X	EKEY	This value is returned and contains the alias of the error message.
iDebugLevel_INT01		O	INT01	If this field value is greater than zero, the M&D Debug statements are displayed.
szComputerID_CTID		X	CTID	If this field is not passed in, a value is retrieved from GetAuditInfo.
szEquipmentNumber_ASII		C	ASII	Either Equipment Number or Order Number is required. Both parameters cannot be blank.
szUnkownItemNumber_UITM		O	UITM
szProductModel_PRODM		O	PRODM
szProductFamily_PRODF		O	PRODF
szProductComponent_PRODC		O	PRODC
szEnvironment_ENV		O	ENV
szDescription_FDESC		R	FDESC
szMediaObjectText_CURRENT		O	CURRENT
szKnowledgeCode1_KBCO		O	KBCO
szKnowledgeCode2_KBCO		O	KBCO
szKnowledgeCode3_KBCO		O	KBCO
szKnowledgeCode4_KBCO		O	KBCO
szKnowledgeCode5_KBCO		O	KBCO
szKnowledgeCode6_KBCO		O	KBCO
szKnowledgeCode7_KBCO		O	KBCO
mnOrderNumber_DOCO		C	DOCO	Either Equipment Number or Order Number is required. Both parameters cannot be blank.
szOrderType_DCTO		C	DCTO	If the Order Number is sent in, this field is required.
szP17766Version_VERS		O	VERS
Globally Unique Identifier (GUID) Fields		C		GUID fields are all optional unless a business must comply with FDA 21 CFR Part 11 auditing requirements. Refer to Special Processing Interface Usage Guide for GUID Input Data Structure details.

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.

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

Field Name	Create Analysis Record	Create Failure Record	Create Resolution Record
BF cdcLINKActionCode	A	F	R
BF cActionCode_ACTION	A	A	A
BF mnOrderNumber_DOCO	456197	456198	456198
BF szOrderType_DCTO	SV	SV	SV
BF cKnowledgeType_KNLT
BF szMediaObjectText_CURRENT	Test1	Test1	Test1
BF szDescription_DS01	ABCD	ABCD	ABCD
szKBTreeName_KBTNM
szKnowledgeCode1_KBCO	HARD	HARD	CONNECT
szKnowledgeCode2_KBCO	MON	MON
szKnowledgeCode3_KBCO
BF szEquipmentNumber_ASII			1001
BF szUnkownItemNumber_UITM			1001

Common error messages

The following common error messages can be generated by this BF. These messages are described in the following table.

Error Message	Description
2	Record invalid 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.
2737	Action invalid This is set when the dcLINKActionCode is not equal to “A,F,R”.
4641	Document type is required This is set if the order type is blank or zero.
480A	Work order does not exist
2238	Search type value invalid
626	Asset number invalid
078I	Fetch from table failed

There was a problem loading this topic

Mobile Enterprise Platform