Process Statistics for Billing: Non-Clarification 

Technical name: BIW_ISU_KPI_BI_NCL

Technical Data

Type of DataSource	Transactional data (movement data)
Application Component	Utilities Industry 0IS_UC
Available from OLTP Release	IS-U/CCS 4.72
RemoteCube Compatibility	No

Prerequisites

You use the enhanced message management tool (EMMA) and have activated the business process area Billing (EBI) for message and BW process management. You can find these settings in the IMG for the utilities industry, under Information System ® Business Information Warehouse ®Settings for Application-Specific DataSources (PL) ®Utilities Industry ® Process Statistics.

Use

This DataSource extracts information on processes in the billing area to BW. This includes processing time, user and messages that have occurred within the processing.

The processes that contribute information for this DataSource are determined by their business process code. These are:

EBI00001	Automatic billing
EBI00002	Manual billing
EBI00003	Complete reversal
EBI00004	Adjustment reversal

Processes that you defined using the IMG activity Define Customer Business Processes for Message Management, and that you allocated to the Billing business process area, are also logged.

Logging

The processes are logged, regardless of whether they:

·        Are called from the Customer Interaction Center (CIC), from the IS-U, or remotely from a CRM system

·        Are called directly using transactions

·        Are called via a workflow.

Calls from the CRM Interaction Center WebClient, from E-Services (Biller Direct), or from Internet Self Services (via IST) are not logged. Process calls at the time of the migration to IS-U also do not generate any messages in the application log of the process statistics.

Messages

You can define the scope of the messages to be extracted. The success messages, information messages and warning messages are taken from a positive list, which you form from the SAP success messages – IMG activity Define Success Messages for Extraction (SAP) – and the success messages that you defined. This DataSource generally forwards error messages to BW, as long as they are contained in the application log and are not excluded by the IMG activity Suppression of  Messages for Log Preparation, or as long as they are defined as triggering messages for clarification case generation.

In addition to the messages stored in this way, the special message EMMA 011 (Start process <Business Process Code> for <Object Type> <Object Key> in process area <Business Process Area>) is extracted for each process and processed object. This message is given the error category Error ('E') if no message from the aforementioned positive list of success messages was written in the application log for the corresponding process. Otherwise, the message is given the message category Success (‘S’).

Nested Processes

As a general rule, processes can be logged as nested.

For detailed information on these nested main processes and subprocesses, see the documentation for the DataSource Process Statistics for Move-In, Move-Out and Move-In/Out: Non-Clarification (0UC_CM_NCL_CS01).

Customer-Specific Processes

Processes that you defined using the IMG activity Define Customer Business Processes for Message Management, and that you allocated to the Customer Service business process area, are also logged. To do this, you must meet two prerequisites:

·        You operate the methods EmmaLogProcessStart, EmmaLogProcessMsgWrite andEmmaLogProcessEnd from the BOR object type EMMA: Process (EMMAPROC), in order to write messages within a process in an application log.

·        You implement the BAdI Enhancement of the Document Structure for KPI Process (ISU_INV_KPI_PROCESS) in order to accumulate data records that the system writes in the delta queue.

Front-Office Processes

For detailed information on these front-office processes, see the documentation for the DataSource Process Statistics for Move-In, Move-Out and Move-In/Out: Non-Clarification (0UC_CM_NCL_CS01).

Delta Update

No data is transferred when initializing the delta update.

The processes do not directly update the delta queue, but first save the data in an application log. The delta update itself takes place within Log Analysis, Preparation and Case Generation (transaction EMMA). You can use this transaction to prepare (in the background) all jobs (processes) from the Billing business process area that have not yet been prepared. Each process and object is analyzed here to see whether a clarification case must be generated. If this is not the case, the delta queue for this DataSource is directly updated during this action. Otherwise, no data is written in the delta queue, but an extract is generated, which is further processed in the case generation, and whose processing also fills the delta queue.

The messages with information from the billing document are accumulated during the update in the delta queue.

Note that the message regarding the end of a process - EMMA-012 - is never forwarded to BW. The information contained therein, regarding the end time stamp is supplied in the data record from the start message – EMMA-011.

If the information on the end time stamp for the process is missing, no information on the process is transferred to BW. This can, for example, be the case if the user cancels the process without the system being able to log the end of the process.

Fields of Origin in the Extraction Structure

Field in Extraction Structure	Description of Field in the Extraction Structure	Table of Origin	Field in Table of Origin
BPGUID_BW	Business process GUID for BW (32 character)	EMMA_HDR	BPGUID
SEQNR	Sequential number for a message, by process.	The number is issued during the delta update, and makes the key unique. The numbering must be sequential.
BPAREA	Business process area	EMMA_BPC	BPAREA
BPCODE	Business process code	EMMA_HDR	BPCODE
SYTCODE	Transaction code	EMMA_HDR	LOGTCODE
UNAME	User name	EMMA_HDR	LOGUSER
BATCH	Ind.: Background processing	BALMP	PARVALUE
TIMEDIFF	Numeric value of processing time	BALMP	PARVALUE
TIMEDIFF_UNIT	Processing time unit: Seconds	BALMP	PARVALUE
SYST_BEG	Time stamp in short form: Start of processing	BALMP	PARVALUE
SYST_END	Time stamp in short form: End of processing	BALMP	PARVALUE
TZONE	Time zone of user	BALMP	PARVALUE
MSG_POS	Ind.: Message record	All messages except EMMA-011 receive this indicator during the delta update.
MSGID	Message identification	BALM	MSGID
MSGNO	Number of system message	BALM	MSGNO
MSGTY	Message type	BALM	MSGTY
MAIN_PROC	Ind.: Main process	BALMP	PARVALUE
ERNAM	Name of clerk who added the object	EEIN	ERNAM
ERDAT	Date on which the record was added	EEIN	ERDAT
USER_CANC	Cancellation of transaction by user (F3, F12, F15)	During the delta update, setting this indicator is one of the options for handling a process in which no data has been changed.
NO_TIME_MEAS	No time measurement	BALMP	PARVALUE
ANZPO	Number of document item messages	If the message is a document item message, this field has the value 1. If not then the field has the value 0. If no differentiation is made between document header messages and document item messages, this field has the value 0.
ANZHEAD	Number of document header messages	If the message is a document header message, this field has the value 1. If not then the field has the value 0. If no differentiation is made between document header messages and document item messages, this field has the value 1.
QROWCOUN	Number of aggregated document item messages	If this field deals with a document header message, the field contains the number of corresponding document item messages. If no differentiation is made between document header messages and document item messages, this field contains the value 0.
BELNR	Billing document number	ERCH	E_BELNR
SPARTE	Division for document	ERCH	SPARTE
GPARTNER	Business partner	ERCH	BU_PARTNER
VKONT	Contract account	ERCH	VKONT_KK
VERTRAG	Contract	ERCH	VERTRAG
BEGABRPE	Start of billing period	ERCH	BEGABRPE
ENDABRPE	End of billing period	ERCH	ENDABRPE
ABRDATS	Billing date	ERCH	ABRDATS
BELEGDAT	Document date	ERCH	BELEGDAT
STORNODAT	Reversal date	ERCH	STORNODAT
PORTION	Portion	ERCH	PORTION
TOBERELEASD	Document is released	ERCH	TOBERELEASD
ABLEINH	Meter reading unit	ERCH	ABLEINHEIT
ABRVORG	Billing transaction	ERCH	ABRVORG
BCREASON	Cancellation reason	ERCH	BCREASON
ORIGDOC	Original of document	ERCH	ORIGDOC
FREI_AM	Date of document release	ERCH	FREI_AM

Features of the Extractor

These data records can also be updated in the delta queue for this DataSource at the time of the clarification case generation within the Log Analysis, Preparation and Case Generation (EMMA)transaction. This always happens when a clarification case is to be generated for a process and an object, but other messages, which are not triggering messages for a clarification case, are logged for a message type. These messages are then treated as non-clarification information.

Note that, in such a case, the start message EMMA-011 is not written in the delta queue for the non-clarification DataSource, but is only written in the delta queue for the clarification DataSource, in order to avoid the duplication of processes in BW.