How-to Guide

SAP NetWeaver 2004s

How To…
Create Monitor
Entries from a
Transformation
routine
Version 1.00 – May 2006

Applicable Releases:
SAP NetWeaver 2004s
(BI Capability)
© Copyright 2006 SAP AG. All rights reserved. contained in this document serves informational
purposes only. National product specifications may vary.
No part of this publication may be reproduced or
transmitted in any form or for any purpose without the These materials are subject to change without notice.
express permission of SAP AG. The information These materials are provided by SAP AG and its affiliated
contained herein may be changed without prior notice. companies ("SAP Group") for informational purposes
only, without representation or warranty of any
Some software products marketed by SAP AG and its kind, and SAP Group shall not be liable for errors or
distributors contain proprietary software components of omissions with respect to the materials. The only
other software vendors. warranties for SAP Group products and services are those
that are set forth in the express warranty statements
Microsoft, Windows, Outlook, and PowerPoint are accompanying such products and services, if any.
registered trademarks of Microsoft Corporation. Nothing herein should be construed as constituting an
additional warranty.
IBM, DB2, DB2 Universal Database, OS/2, Parallel
Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, These materials are provided “as is” without a warranty
iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent of any kind, either express or implied, including but not
Miner, WebSphere, Netfinity, Tivoli, and Informix are limited to, the implied warranties of merchantability,
trademarks or registered trademarks of IBM Corporation fitness for a particular purpose, or non-infringement.
in the United States and/or other countries. SAP shall not be liable for damages of any kind including
without limitation direct, special, indirect, or
Oracle is a registered trademark of Oracle Corporation. consequential damages that may result from the use of
these materials.
UNIX, X/Open, OSF/1, and Motif are registered SAP does not warrant the accuracy or completeness of
trademarks of the Open Group. the information, text, graphics, links or other items
contained within these materials. SAP has no control
Citrix, ICA, Program Neighborhood, MetaFrame, over the information that you may access through the
WinFrame, VideoFrame, and MultiWin are trademarks use of hot links contained in these materials and does not
or registered trademarks of Citrix Systems, Inc. endorse your use of third party web pages nor provide
any warranty whatsoever relating to third party web
HTML, XML, XHTML and W3C are trademarks or pages.
®
registered trademarks of W3C , World Wide Web SAP NetWeaver “How-to” Guides are intended to
Consortium, Massachusetts Institute of Technology. simplify the product implementation. While specific
product features and procedures typically are explained
Java is a registered trademark of Sun Microsystems, Inc. in a practical business context, it is not implied that those
features and procedures are the only approach in solving
JavaScript is a registered trademark of Sun Microsystems, a specific business problem using SAP NetWeaver. Should
Inc., used under license for technology invented and you wish to receive additional information, clarification
implemented by Netscape. or support, please refer to SAP Consulting.
Any software coding and/or code lines / strings (“Code”)
MaxDB is a trademark of MySQL AB, Sweden. included in this documentation are only examples and
are not intended to be used in a productive system
SAP, R/3, mySAP, mySAP.com, xApps, xApp, and other environment. The Code is only intended better explain
SAP products and services mentioned herein as well as and visualize the syntax and phrasing rules of certain
their respective logos are trademarks or registered coding. SAP does not warrant the correctness and
trademarks of SAP AG in Germany and in several other completeness of the Code given herein, and SAP shall
countries all over the world. All other product and not be liable for errors or damages caused by the usage of
service names mentioned are the trademarks of their the Code, except if such damages were caused by SAP
respective companies. Data intentionally or grossly negligent.
1 Business Scenario
On the upload of transactional data, you want to prevent the application of business rules for certain
criteria, e.g. a certain cost centre should be treated differently or the records affecting this cost centre
should not be processed at all (skipped on the transfer population of data targets).
In addition to implementing the criteria in the coding of a transformation routine, you also want to
provide information about what has happened to the administrator.
You can do so by writing messages to the monitor from within the transformation routine. These
messages (standard messages defined with transaction code SE91) are displayed in the Data Transfer
Process (DTP) monitor.

2 The Result
The user can check the monitor entries for this DTP after a data load. In our example we have chosen a
specific cost centre (cost centre ‘1000’) for which the processing of the record should be skipped. The DTP
monitor indicates that messages have been triggered for a certain number or records. Details on the
message can be obtained by further drilling-down on the monitor entry.

-1-
3 The Step By Step Solution

3.1 Create transformation routine

1. Create a transformation. Within the

maintenance of the transformation double-
click on a field, in the example the
characteristic “0COSTCENTER”.
In the ‘Rule details’ dialog choose the rule
type ‘Routine’.

2. Enter the source code (see Appendix for

source code example).
Please note that the field names of the
sample coding are not relevant (and will be
different in your scenario).

-2-
3.2 Load data into your InfoCube

1. Create a Data Transfer Process (DTP) to

update the InfoCube with the data from
the PSA.

Execute the DTP by including it in a process

chain or by direct execution from within
the DTP maintenance.

2. To see potential messages triggered in the

custom routine, please go to the monitor
for the DTP ( ).

Depending on whether you skip the

record, abort the whole DTP, or continue
with the processing without raising an
exception, the monitor entry might be
slightly different, e.g. ‘Error Handling’, etc.
Yet you should find a similar output as
shown on the screen shot.

3. Position on the monitor entry and select

the ‘Display for Error Records’ from the
context menu or press the icon
located in the next to the entry.

-3-
 4. As a result you get a pop-up with all the
single messages displayed.

4 Appendix

Sample source code for the method to compute the characteristic “0COSTCENTER”.

CLASS routine IMPLEMENTATION.

METHOD compute_0COSTCENTER.

* IMPORTING
* request type rsrequest
* datapackid type rsdatapid
* SOURCE_FIELDS-KOSTL TYPE C LENGTH 000010
* EXPORTING
* RESULT type _ty_s_TG_1-COSTCENTER

DATA:
MONITOR_REC TYPE rsmonitor.

*$*$ begin of routine - insert your code only below this line *-*
... "insert your code here
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*- to make monitor entries
... "to cancel the update process
* raise exception type CX_RSROUT_ABORT.
... "to skip a record
* raise exception type CX_RSROUT_SKIP_RECORD.
... "to clear target fields
* raise exception type CX_RSROUT_SKIP_VAL.

IF SOURCE_FIELDS-KOSTL = '0000001000'.
MONITOR_REC-MSGID = 'RSM'.
MONITOR_REC-MSGTY = 'E'.
MONITOR_REC-MSGNO = '799'.
MONITOR_REC-MSGV1 = 'Cost Center '.
MONITOR_REC-MSGV2 = SOURCE_FIELDS-KOSTL.
APPEND MONITOR_REC to MONITOR.
* ... Skip a record
raise exception type CX_RSROUT_SKIP_RECORD.
ENDIF.

*$*$ end of routine - insert your code only before this line *-*
ENDMETHOD. "compute_0COSTC

-4-
www.sdn.sap.com/irj/sdn/howtoguides