F48166DecrementKnowledgeBasePare

F48166 Decrement Failure Analysis Pareto

Minor Business Rule

Object Name: N1700700

Parent DLL: CCRIN

Location: Client/Server

Language: NER

1.1Purpose
This NER is used to decrement the frequencey count in F48166 - Knowledge Base Pareto for a combination of Knowledge Bases (Symptom,
Analysis, Resolution). It is executed from P17765 - Call / Order Knowledge Base whenever that application detects that a Knowledge Base Symptom,
Analysis or Resolution is being detached from a Call or Service Order. What this business function does is take the Analysis or Resolution that is being
detached from the Call/Service Order and pairs it with existing Symptoms and Analyses that exist for the Call/Service Order and then decrements the
frequency count in F48166 for that pair. Then the Analysis or Resolution record is deleted from the Call / Order Knowledge Base Table (F48165). The
function can also handle when a Symptom is being detached from the Call / Order. When this happens, the only database update that occurs is to delete
the Symptom from F48165, since the Knowledge Base Pareto Table (F48166) would not have any entries for a solitary Symptom.

1.2Setup Notes and Prerequisites.

Data Item Data Structure DescriptionI/ORequiredNotes
DOCODocument NumberIY
DCTODocument TypeIY
RCK5Sequence NumberIY
KNLTKnowledge TypeIY
UKIDKnowledge Base IDIY
EV01SuccessON

1.3Special Logic

Data Structure

D1700700 - F48166 Decrement Failure Analysis Pareto

Parameter Name Data Item Data Type Req/Opt I/O/Both

mnDocumentNumber DOCO MATH_NUMERIC REQ INPUT

A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry,
and so on.

szDocumentType DCTO char REQ INPUT

A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has
reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post
program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and
should not be changed: P Accounts Payable documents   R Accounts Receivable documents   T Payroll documents   I Inventory documents
O Purchase Order Processing documents   J General Accounting/Joint Interest Billing documents   S Sales Order Processing documents

mnSequenceNumber RCK5 MATH_NUMERIC REQ INPUT

This field is used to create a unique key within a file.  If you are using a program which will allow you to resequence the records, we
recommend you use one of the following data dictionary items:  DSS5, DSS7, DSS9.

cKnowledgeType KNLT char REQ INPUT

A code that associates a type of action with the Failure Analysis record. Valid values are: Failure Analysis Resolution All

mnKnowledgeBaseID UKID MATH_NUMERIC REQ INPUT

This field is a unique number used to identify a record in a file.

cSuccess EV01 char OPT OUTPUT

An option that specifies the type of processing for an event.

Related Functions

None

Related Tables

None

Parameter Name	Data Item	Data Type	Req/Opt	I/O/Both
mnDocumentNumber	DOCO	MATH_NUMERIC	REQ	INPUT
A number that identifies an original document. This document can be a voucher, a sales order, an invoice, unapplied cash, a journal entry, and so on.
szDocumentType	DCTO	char	REQ	INPUT
A user defined code (00/DT) that identifies the type of document. This code also indicates the origin of the transaction. J.D. Edwards has reserved document type codes for vouchers, invoices, receipts, and time sheets, which create automatic offset entries during the post program. (These entries are not self-balancing when you originally enter them.) The following document types are defined by J.D. Edwards and should not be changed: P Accounts Payable documents R Accounts Receivable documents T Payroll documents I Inventory documents O Purchase Order Processing documents J General Accounting/Joint Interest Billing documents S Sales Order Processing documents
mnSequenceNumber	RCK5	MATH_NUMERIC	REQ	INPUT
This field is used to create a unique key within a file. If you are using a program which will allow you to resequence the records, we recommend you use one of the following data dictionary items: DSS5, DSS7, DSS9.
cKnowledgeType	KNLT	char	REQ	INPUT
A code that associates a type of action with the Failure Analysis record. Valid values are: Failure Analysis Resolution All
mnKnowledgeBaseID	UKID	MATH_NUMERIC	REQ	INPUT
This field is a unique number used to identify a record in a file.
cSuccess	EV01	char	OPT	OUTPUT
An option that specifies the type of processing for an event.