BI Setup Guide
Short Description
crm bi setup guide...
Description
Setup Guide for SAP NetWeaver Business Intelligence
SAP CRM ondemand solution Wave 5 Target Audience
System administrators
Document version: 1.0 – June 21st, 2008
SAP AG Dietmar-Hopp-Allee 16 69190 Walldorf Germany T +49/18 05/34 34 24 F +49/18 05/34 34 20 www.sap.com
© Copyright 2007 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any
SAP, R/3, mySAP, mySAP.com, SAP NetWeaver, xApps, xApp, and
form or for any purpose without the express permission of SAP AG.
other SAP products and services mentioned herein as well as their
The information contained herein may be changed without prior
respective logos are trademarks or registered trademarks of SAP AG
notice.
in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their
Some software products marketed by SAP AG and its distributors
respective companies. Data contained in this document serves
contain proprietary software components of other software vendors.
information purposes only. National product specifications may vary.
Microsoft, Windows, Outlook, PowerPoint, and SQL Server are
These materials are subject to change without notice. These materials
registered trademarks of Microsoft Corporation.
are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,
any kind, and SAP Group shall not be liable for errors or omissions
MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries,
with respect to the materials. The only warranties for SAP Group
xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity,
products and services are those that are set forth in the express
Tivoli, and Informix are trademarks of IBM Corporation in the United
warranty statements accompanying such products and services, if any.
States and/or other countries.
Nothing herein should be construed as constituting an additional warranty.
ORACLE is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Disclaimer Some components of this product are based on Java™. Any code
Citrix, ICA, Program Neighborhood , MetaFrame, WinFrame,
change in these components may cause unpredictable and severe
VideoFrame, and MultiWin are trademarks of Citrix Systems, Inc.
malfunctions and is therefore expressively prohibited, as is any decompilation of these components.
HTML, XML, XHTML and W3Care trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts
Any Java™ Source Code delivered with this product is only to be used
Institute of Technology.
by SAP’s Support Services and may not be modified or altered in any way.
Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used
Documentation in the SAP Service Marketplace
under license for technology invented and implemented by Netscape.
You can find this documentation at the following address: http://service.sap.com/
Typographic Conventions
Icons
Type Style
Description
Example Text
Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation
Caution
Example text
Emphasized words or phrases in body text, graphic titles, and table titles
Syntax
EXAMPLE TEXT
Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.
Example text
Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.
Example text
Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.
Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.
EXAMPLE TEXT
Keys on the keyboard, for example, F2 or ENTER.
Icon
Meaning
Example Note Recommendation
Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.
Contents 1 Introduction...................................................................................6 1.1 BI / SAP SAP CRM on-demand solution System Landscape and System Administration.............................................................................7 1.1.1 System Landscape...............................................................................................7 1.1.2 SAP BW System Requirements: Support Package Level and Notes to Be Applied...........................................................................................................................8 1.1.3 System Administration..........................................................................................9
2 Business Process Configuration...............................................43 2.1 Business Process Activation........................................................44 2.2 Adjustment of BI Content [BI].......................................................47 2.2.1 Adoption of the Role SAP_BWC_CXP_SALES_MGR “Portal/BW Role for CXP Sales Manager”............................................................................................................47 2.2.2 Adoption of Other Roles......................................................................................51
2.3 Adoption of CRM DataSources [CRM + BI]...................................53 2.4 Text DataSources for Userstatus [CRM + BI]................................58 2.5 Adoption of Transfer Rules for Product Texts [BI]........................61 2.7 Adoption of Update Rules for Quotations [BI]..............................65 2.8 Adoption of Webtemplate [BI]........................................................67 Changes to Mime Repository [BI]........................................................81 Customizing of Product [BI].................................................................82 Important Note on Data Consistency [BI]...........................................85 Opportunities [BI]..................................................................................86 Create / Execute InfoPackages for Opportunity Header 0CRM_OPPT_H [BI]................................................................................87 Create/ Execute InfoPackages for Opportunity Items 0CRM_OPPT_I [BI] ...........................................................................................................94 Create/Execute Process Chain for Opportunity (Header & Items) [BI] ..................................................................................................................95 Activity [BI]............................................................................................96 Create / Execute InfoPackages for Activities [BI]...............................97 Create / Execute Process Chain for Activity [BI]................................98 Business Partner [BI]............................................................................99 Create / Execute InfoPackages for Business Partner Master Data [BI]..........................................................................................................100 Create / Execute Full InfoPackages for Org Unit [BI].......................101 Create / Execute Process Chain for Business Partner Master Data [BI]..........................................................................................................102 Organizational Unit and User Name [BI]...........................................104 Create / Execute Full InfoPackages for Org Unit Master Data [BI]. 105 Create / Execute Full InfoPackages for User Name Master Data [BI] ................................................................................................................106 Create Process Chain for Org Unit [BI].............................................107 Campaign [BI].......................................................................................109
4
Create / Execute InfoPackages for Outbound Customer Contact [BI] .................................................................................................................110 Create /Execute InfoPackages for Inbound Customer Contact 0CRM_CONTACT_IN [BI]......................................................................111 Create/Execute InfoPackages for Marketing Elements 0CRM_MKTELM_TEXT & MKTELM5_ATTR [BI].................................112 Create/Execute Process Chain for Campaign [BI]...........................113 Leads [BI]..............................................................................................114 Create/Execute InfoPackages for Lead Header 0CRM_LEAD_H [BI] .................................................................................................................115 Create/Execute InfoPackage for Lead GUID 0CRM_LEAD_ATTR [BI] .................................................................................................................116 Create/Execute Process Chain for Lead [BI].....................................117 Quotations [BI].....................................................................................118 Create InfoPackage for Quotations [BI].............................................119 Create Process Chain for Quotations [BI].........................................120 Service Tickets [BI]..............................................................................121 Create InfoPackage for Service Ticket Headers [BI]........................122 Create InfoPackage for Service Ticket Items [BI].............................123 Create Process Chain for Service Tickets [BI].................................124 Product [BI]..........................................................................................125 Regular Upload of CRM Master Data [BI]..........................................126 Upload of Master Data and Texts from CRM Customizing or from Fixed Domains [BI]...............................................................................127 Currencies [BI].....................................................................................128 InfoObject “BP Number in External System” (0BP_EXTERN) [BI]. 129
3 Appendix A: Common CRM Business Objects.......................130 4 Appendix B: Relevant Business Objects for CRM Sales......132 5 Appendix C: Relevant Business Objects for CRM Marketing ........................................................................................................134 6 Appendix E: Relevant Business Objects for the product......137 7 Appendix E: Relevant Business Objects for CRM Service. . .138 8 Appendix F: Objects for User Status .......................................139 9 Appendix G: Transactions.........................................................140
5
3 Appendix A: Common CRM Business Objects
1 Introduction This setup guide is aimed to support the members of SAP CRM on-demand solution teams to prepare the Business Intelligence part of SAP CRM on-demand solution. This setup guide is not learning material and profound knowledge of SAP BW is necessary to work with this setup guide.
6
3 Appendix A: Common CRM Business Objects
1.1 BI / SAP SAP CRM on-demand solution System Landscape and System Administration 1.1.1 System Landscape A typical SAP CRM on-demand solution system landscape would always consist of logical pairs of systems, consisting of a SAP CRM on-demand solution system and a BW system. We recommend building productive SAP CRM on-demand solution system landscapes from a preconfigured template landscape. The actual template systems will be validated with the help of a SAP CRM on-demand solution validation landscape.
BW Template System CRM Template System
BW Productive System 1 CRM Productive System 1
BW Validation System CRM Validation System
BW Productive BW Productive BW Productive System 3 System 2 CRM Productive CRM Productive CRM Productive System 2 System 3 System 4
7
3 Appendix A: Common CRM Business Objects
1.1.2 SAP BW System Requirements: Support Package Level and Notes to Be Applied For the SAP BW system used in SAP CRM on-demand solution Wave 5, SAP Net Weaver BI 7.0 Component Support Pack - SAPKW70018 and BI Content SP SAPKIBIIP10 is required. As of now, all Notes which had to be applied as part of COD Wave 4 has been implemented in COD Wave 5. Hence no notes are required to be implemented.
8
3 Appendix A: Common CRM Business Objects
1.1.3 System Administration
1.1.3.1 Check Language Support [BI] In the BW system, in transaction SE38, execute report RSCPINST and check that EN and DE are installed. Remark: if only EN is installed, the BW upload of texts will not transfer German texts (this is specific to German and does not necessarily apply to other languages)
9
3 Appendix A: Common CRM Business Objects
1.1.3.2 ALEREMOTE Configuration [CRM] 1. Log on to the CRM system 2. Call transaction SU01, User ALEREMOTE 3. Logon Data →User Type: DIALOG and User Group: SUPER We assume that user ALEREMOTE is used for the BI Content activation. During BI Content activation the ALEREMOTE should be of User Type “Dialog”. After BI Content activation ALEREMOTE should have User Type “System”.
10
3 Appendix A: Common CRM Business Objects
System: CRM Client must be available
11
3 Appendix A: Common CRM Business Objects
12
3 Appendix A: Common CRM Business Objects
4. In CRM system, call transaction SCC4.
5. Change “Cross Client Object Changes” →“allowed”
13
3 Appendix A: Common CRM Business Objects
14
3 Appendix A: Common CRM Business Objects
6. 7. 8. 9.
For the BW extraction of CRM one order objects, the user ALEREMOTE requires additional authorization. In transaction PFCG, create a new role ZCXP_ALEREMOTE (description: “BW Extraction of one order objects”). On Authorizations, click Change Authorization Data and manually add S_USER_GRP, Activity: 03, 05, User group in user master maint: *. Add CRM_ORD_LP with full authorization. Then generate the profile. Finally, assign the role to user ALEREMOTE (this will only be possible in SU01 after you have clicked Text comparison from child sys under Roles).
•
CRM System: Create RFC CLNT to BI system (User ALEREMOTE)
15
3 Appendix A: Common CRM Business Objects
1.1.3.3 ALEREMOTE Configuration [BI] 1. Log on to BI system 2. Call transaction SU01, User ALEREMOTE 3. Logon Data → User Type: DIALOG and User Group: SUPER ALEREMOTE should have the roles SAP_BC_USR_CUA_CLIENT and SAP_BC_USR_CUA_SETUP_CLIENT assigned. In addition, ALEREMOTE should have the profiles S_BI-WHM_RFC and S_BI-WX_RFC assigned.
16
3 Appendix A: Common CRM Business Objects
17
3 Appendix A: Common CRM Business Objects
4. Call transaction RSCUSTA. The result should appear as in the screenshot:
5. In transaction SE16 for table RSADMINA, check that the entry for the client to be used for BW is correct.
18
3 Appendix A: Common CRM Business Objects
In transaction RSCUSTV3, the entries should appear as in the screenshot.
19
3 Appendix A: Common CRM Business Objects
In transaction RSCUSTV5, the entries should appear as in the screenshot.
1.1.3.4 Activate Application Component Hierarchy in CRM 1. Log on to CRM system 2. In transaction RSA9, confirm creation •
20
3 Appendix A: Common CRM Business Objects
1.1.3.5 Activation of BEx Personalization [BI] 1. Log on to BI system 2. Call transaction RS_PERS_ACTIVATE 3. Execute the report.
21
3 Appendix A: Common CRM Business Objects
1.1.3.6 Create SAP CRM on-demand solution [BI] 1. Log on to BI system 2. Call transaction RSA1 3. Select Modeling → Source System
22
3 Appendix A: Common CRM Business Objects
4. Enter system data, user, ALEREMOTE, and password, then click Enter. (Raise IT/IBC Message in the DEV-BBPCRM-USER Component for the DSS Colleagues to enter the password.
Control RFC Connection
Under MDMP & Unicode, check that the connection is also unicode-enabled.
23
3 Appendix A: Common CRM Business Objects
5. Activate Source Systems...
24
3 Appendix A: Common CRM Business Objects
25
3 Appendix A: Common CRM Business Objects
1.
6. And replicate metadata as well
Several similar popups may appear.
26
3 Appendix A: Common CRM Business Objects
7Select as 3.x Datasource. Several similar popups may appear. 8. Always select the option this and following XX as 3.x Datasource.
27
3 Appendix A: Common CRM Business Objects
1.1.3.7 Replicate Tree Metadata [BI] 1. Log on to BI system. 2. Call transaction RSA1, Modeling, DataSources. 3. Select the CRM system and choose Replicate Tree Metadata.
28
3 Appendix A: Common CRM Business Objects
1.1.3.8 Middleware Configuration [CRM] 1. Log on to CRM system. 2. Call transaction GNRWB.
3. Select generator group BWADP: BW ADAPTER. 4. Select BUS_TRANS_MSG (left-hand side). 5. Select BWA_* (right-hand side), see screenshot.
29
3 Appendix A: Common CRM Business Objects
6. Click Generate (red/white button) The result should appear like this:
30
3 Appendix A: Common CRM Business Objects
7. In the CRM system, call transaction SMW01 and check BDOC type BUS_TRANS_MSG.
31
3 Appendix A: Common CRM Business Objects
At this stage, BDocs (if there are any at this stage) are not processed, all are yellow. The result list may be void.
32
3 Appendix A: Common CRM Business Objects
8. In the CRM system, call transaction SMQR and click Registration.
9. Click Registration and enter CSA* as the queue name.
The result appears like this:
33
3 Appendix A: Common CRM Business Objects
10. Check SMW01 again. If BDocs are available, the result appears like this:
34
3 Appendix A: Common CRM Business Objects
11. Unless all BDocs are green by now, enter transaction SMQ2, Queues CSA*. (This section is only included for troubleshooting.)
12. Select each entry that appears and try to activate the queues manually.
35
3 Appendix A: Common CRM Business Objects
1.1.3.9 BI Content Activation: Generic Web Templates [BI] 1. Log on to BI system. 2. Call transaction RSOR. 3. Click Menu, Edit, and then Source System Administration. Verify that the correct CRM system and client have been selected.
4. On the left-hand side, select Objects in BW. 5. In Grouping, specify Only Necessary Objects. 6. Double-click Select Objects, search for Generic.
36
3 Appendix A: Common CRM Business Objects
7. Select Generic BCT Web Templates and click Transfer Selections. 8. Select Install → Install.
37
3 Appendix A: Common CRM Business Objects
1.1.3.10 Transfer Global Settings, Transfer Exchange Rates [BI] 1. Log on to BI system. 2. Call transaction RSA1. 3. Click Modeling → Source Systems. 4. Select SAP CRM on-demand solution system. 5. Select Transfer Global Settings.
38
3 Appendix A: Common CRM Business Objects
6. Select Currencies, Units of measurement, Fiscal year variants, and Update tables, then run the report. 7. Do the same for exchange rates.
39
3 Appendix A: Common CRM Business Objects
Since power users maintain currencies and currency conversion in SAP CRM on-demand solution, currencies and currency conversion rates need to be uploaded regularly from CRM to BW. This is best done by adding the currency conversion report to one of the process chains.
40
3 Appendix A: Common CRM Business Objects
1.1.3.11 Maintenance of Source System IDs [BI] 1. Log on to BI system 2. Call transaction RSA1 3. Choose Menu → Tools → Asgnmt of Srce Syst to Srce Syst ID 4. Specify CX as the value of the source system ID
41
3 Appendix A: Common CRM Business Objects
1.1.3.12 Authorization Problems You should verify that the Web templates in SAP CRM on-demand solution can be executed without authorization errors. If authorization errors occur, follow note 820183 “New authorization concept in BI” and run function module RSEC_GENERATE_BI_ALL in transaction SE37. Authorization problems may appear after any changes to the business process configuration.
PS: Note is already part of COD W5 System. Hence need not be applied.
42
3 Appendix A: Common CRM Business Objects
2 Business Process Configuration
43
3 Appendix A: Common CRM Business Objects
2.1 Business Process Activation 1. Log on to BI system. 2. Call transaction RSOR (or RSA1, Business Content). 3. Select object types. 4. Under Grouping, specify In Data Flow Before.
5. Select roles SAP_BW_CXP_SALES_MGR, SAP_BW_CXP_SALES_REP, SAP_BW_CXP_SERV_MGR, SAP_BW_CXP_SERV_REP, and InfoObjects 0USERNAME and 0ORGUNIT. Remark: The two InfoObjects are not fully used in the actual reports, but they are processed in SAP Exits within these reports and are therefore required. 6. Transfer the selection, then click Install.
44
3 Appendix A: Common CRM Business Objects
45
3 Appendix A: Common CRM Business Objects
7. Confirm that DataSources in the source system may be transferred from BI Content. This step requires a logon in the CRM system. The user in the CRM system should be authorized for the remote activation of BI Content: Assign the CRM user the role SAP_RO_BCTRA “Remote Content Activation of SAPIDataSources from a BW”. (The screenshot displays the status of a system where the BI Content has already been activated. Otherwise, the system will set hooks for those objects that have not yet been activated.).
8. Save the activated objects as local objects in the source system. When asked by the system if you want to keep an existing Version of InfoObjects, always choose the Content version.
46
3 Appendix A: Common CRM Business Objects
2.2 Adjustment of BI Content [BI] After BI Content activation, some objects have to be adjusted for SAP CRM on-demand solution. This section will describe all steps in detail.
2.2.1 Adoption of the Role SAP_BWC_CXP_SALES_MGR “Portal/BW Role for CXP Sales Manager” Note that this role will only exist after SAP_BW_CXP_SALES_MGR has been activated in transaction RSOR from BI Content. 1. In Role Maintenance (transaction PFCG), enter SAP_BWC_CXP_SALES_MGR and click Change.
47
3 Appendix A: Common CRM Business Objects
2. Generate the profiles for the role SAP_BWC_CXP_SALES_MGR.
48
3 Appendix A: Common CRM Business Objects
3. Under User, perform a complete user comparison. This will turn the User tab green.
49
3 Appendix A: Common CRM Business Objects
50
3 Appendix A: Common CRM Business Objects
4. Under Personalization, enter CRM_ROLE_VARIABLE_SETTING and add a line with value 0CXPMOM as VNAM and value 1 as RES.
2.2.2 Adoption of Other Roles 1. For role SAP_BWC_CXP_SALES_REP “Portal/BW role for CXP Sales Representative”, proceed as in the previous step, with the exception that in Personalization for CRM_ROLE_VARIABLE_SETTING you now add several lines • 0P_USER as VNAM and value 1 as RES • 0CXPUSR as VNAM and value 1 as RES • 0CXPBP as VNAM and value 1 as RES 2. For SAP_BWC_CXP_SERV_MGR, proceed similarly to SAP_BWC_CXP_SALES_MGR and for SAP_BWC_CXP_SERV_REP proceed similarly to SAP_BWC_CXP_SALES_REP. 3. In transaction RSOR, activate all currency translation types from BI Content. (Otherwise queries that use the currency translation types will show errors).
51
3 Appendix A: Common CRM Business Objects
52
3 Appendix A: Common CRM Business Objects
2.3 Adoption of CRM DataSources [CRM + BI] All CRM One Order Data Sources are now enhanced by User Status in COD Wave 5. For convenience, we have included a screenshot of SAP CRM on-demand solution Customizing of User Status, which shows the status object groups used in SAP CRM on-demand solution:
Then edit the DataSource, remove the flags for BWSTONEACTI, and save. In the BW system, replicate again the metadata for DataSource 0CRM_SALES_ACT_1.
53
3 Appendix A: Common CRM Business Objects
open the transfer rules for InfoSource 0CRM_SALES_ACT_1. Include BWSTONEACTI in the Transferstructure and map this field to InfoObject 0STAONEACTI. Afterwards, activate the transfer rules.
54
3 Appendix A: Common CRM Business Objects
55
3 Appendix A: Common CRM Business Objects
In the transfer rules for 0CRM_SALES_ACT_1, check that the private flag has been mapped properly. The screenshot shows the case where the private flag has not been mapped yet.
56
3 Appendix A: Common CRM Business Objects
1. Proceed similarly with the other One Order DataSources used in SAP CRM ondemand solution. Here is a list of them, including the field name to be used in the extract structure, the InfoSource name in BW, and the InfoObject name to be used for the mapping in the transfer rules: DataSource
Field Name
InfoSource
Userstatus InfoObject
0CRM_SALES_ACT_1
BWSTONEACTI
0CRM_SALES_ACT_1
0STAONEACTI
0CRM_QUOTA_ORDER_I
BWSTONEQUOT
0CRM_QUOT_ORDER_I
0STAONEQUOT
0CRM_OPPT_H
BWSTONEOPPT
0CRM_OPPT_H
0STAONEOPPT
0CRM_OPPT_I
BWSTONEOPPT
0CRM_OPPT_I
0STAONEOPPT
0CRM_LEAD_H
BWSTONELEAD
0CRM_LEAD_H
0STAONELEAD
0CRM_SRV_PROCESS_I
BWSTONESVTK
0CRM_SERVICE_PROCESS_I
0STAONESVTK
0CRM_SRV_PROCESS_H
BWSTONESVTK
0CRM_SERVICE_PROCESS_H
0STAONESVTK
57
3 Appendix A: Common CRM Business Objects
2.4 Text DataSources for Userstatus [CRM + BI] All CRM One Order Text Data Sources are now enhanced by User Status in COD Wave 5. 1) In transaction RSO2, theText Data Sources according to the following table for each of the different User Status objects should be assigned correctly (it is important to follow this precisely, since the DataSource name is evaluated in the generic function module for the data extraction.) Status Group Object ACTI OPPT LEAD QUOT SVTK
DataSource
Application Component
0CRM_STAONEACTI_TEXT 0CRM_STAONEOPPT_TEXT 0CRM_STAONELEAD_TEXT 0CRM_STAONEQUOT_TEXT 0CRM_STAONESVTK_TEXT
0CRM_SALES-IO 0CRM_SALES-IO 0CRM_MKT-IO 0CRM_SALES-IO 0CRM_SERVICE-IO
58
3 Appendix A: Common CRM Business Objects
2. On BW side in transaction RSD1 for the following list of InfoObjects maintain in tab “Master data/texts” application component for ”InfoSource with direct update” according to the following table InfoObject
Application Component
0STAONEACTI
CRM-IO
0STANEOPPT
CRM_SALES-IO
0STAONEQUOT
CRM_SALES-IO
0STAONELEAD
CRM_MKT-IO
0STAONESVTK
CRM_SERVICE-IO
3. On the BW side, replicate the metadata for all DataSources in the application components from the table and replicate the new DataSources as 3.x DataSources. Then use transaction RS_ISTD_REMOTE to create transfer rules. To do this, first assign SourceSystem to the User Status InfoObject and then assign the corresponding User Status InfoObject according to the following list: InfoSource
DataSource
0STAONEACTI
0CRM_STAONEACTI_TEXT
0STAONEOPPT
0CRM _STAONEOPPT_TEXT
0STAONELEAD
0CRM _STAONELEAD_TEXT
0STAONEQUOT
0CRM _STAONEQUOT_TEXT
0STAONESVTK
0CRM _STAONESVTK_TEXT
59
3 Appendix A: Common CRM Business Objects
Maintain the transfer rules according to the following screen:
60
3 Appendix A: Common CRM Business Objects
2.5 Adoption of Transfer Rules for Product Texts [BI] The TransferRules for DataSource 0PRODUCT_TEXT does not fill 0PROD_SYST. As a result Product Texts in CRM on Demand are not displayed properly. We need to introduce a routine, which determines 0PROD_SYST out of the LOGSYS field in the transfer structure.
Create a routine with name “Two-Figure Source System”, save and activate. If you have already loaded texts, then you need to reinitialize the upload in order to fill the 0PROD_SYST field for all Products.
61
3 Appendix A: Common CRM Business Objects
62
3 Appendix A: Common CRM Business Objects
63
3 Appendix A: Common CRM Business Objects
Here are the essential parts of the coding for the transfer routine: Data declaration section: *$*$ begin of global - insert your declaration only below this line *-* DATA: l_s_errorlog TYPE rssm_s_errorlog_int, l_text TYPE string. *$*$ end of global - insert your declaration only before this line *-*
Coding from the form routine: *$*$ begin of routine - insert your code only below this line RETURNCODE = 0.
*-*
IF RESULT IS INITIAL. * retrieve source system ID form the source system CALL FUNCTION 'RSDG_ID_GET_FROM_LOGSYS' EXPORTING i_source_system = TRAN_STRUCTURE-logsys IMPORTING e_soursysid = RESULT EXCEPTIONS id_not_found = 1. IF sy-subrc 0.
64
3 Appendix A: Common CRM Business Objects
RETURNCODE = 4. MESSAGE e087(r7) WITH TRAN_STRUCTURE-logsys INTO l_text. MOVE-CORRESPONDING syst TO l_s_errorlog. l_s_errorlog-record = RECORD_NO. APPEND l_s_errorlog TO g_t_errorlog. * ABORT = 1. ENDIF. ENDIF. *$*$ end of routine - insert your code only before this line *-*
2.7 Adoption of Update Rules for Quotations [BI] In BI Content within the Update Rules for InfoCube 0CSAL_C05 (from 0CRM_QUTO) the Fiscal Variant InfoObject is assigned the constant value ‘K4’. Change this in such a way, that the InfoObject is linked to the same field from 0CRM_QUTO:
65
3 Appendix A: Common CRM Business Objects
66
3 Appendix A: Common CRM Business Objects
2.8 Adoption of Webtemplate [BI] In BI Content 7.03 SP10, All the Web Templates are corrected and need not be replaced 0TPLI_0CRM_C04_Q0020_01 0TPLI_0CRM_PRI_Q5001 0TPLI_0CSAL_C05_Q0401 0TPLI_0CSAL_C05_Q0403 0TPLI_0CSRV_C01_Q5001 0TPLI_0CSRV_C01_Q5002 0TPLI_0CSRV_C01_Q5003 0TPLI_0CSRV_C01_Q5004 0TPLI_0MKTG_C01_Q8001_V01 0TPLI_0CSAL_C01_Q0025_01 0TPLI_0CRM_C04_Q0022_01 0TPLI_0CSAL_C01_Q0026_01 0TPLI_0CRM_C04_Q001_01 In transaction SE38, execute program RS_TEMPLATE_MAINTAIN and check if the web templates are executing without displaying any errors.
67
3 Appendix A: Common CRM Business Objects
68
3 Appendix A: Common CRM Business Objects
But we need to shut off the Information Broadcasting functionality in the generic BI web template 0ANALYZER, the functionality to send the report (using information broadcasting) in Webtemplate 0TPL_BAP_BUTMENUBAR_ALL and the functionality to create comments / bookmarks in 0ADHOC_TABLE_ANALYZER and 0ADHOC_CHARTS. In both cases in TA SE38 execute report RS_TEMPLATE_MAINTAIN, open the corresponding web template and replace the content by the content of the corresponding files in the archive W3Ed2_Webtemplates.zip. The BW Query for “Campaign Effectiveness” needs to be adopted (0CRM_MC07_Q7031). Remove CRM Sales Org (0CRM_MKTELM__0CRM_SALORG) from the free characteristics and replace this by Marketing Org (0CRM_MKTELM__0CRM_MKTORG). Restrict to variable 0CXPMOM and save the query. Please check that prior to this activity note 999320 is implemented on CRM side.
In order switch from CRM Sales Org to Marketing Org already existing campaigns need to be corrected. For this you need to create and run a correction report. You would also need to run this report if you initialize the upload of attributes for 0CRM_MKTELM again (because then the assignment or Marketing Org for campaigns created prior to the implementation of note 999320 would loose their Marketing Org reference again): Create a report ZCXP_MARKETING_ORG: *----------------------------------------------------------------------* *& Report ZCXP_MARKETING_ORG *& *&---------------------------------------------------------------------* *&
69
3 Appendix A: Common CRM Business Objects
*& *&---------------------------------------------------------------------* REPORT ZCXP_MARKETING_ORG. type-pools: rsd. data: data: data: data: data:
l_mktelm_tabname type RSCHNTAB. l_bpartner_tabname type RSCHNTAB. l_username_tabname type RSCHNTAB. l_t_atr type RSD_T_ATR. l_viobj type RSD_S_VIOBJ.
data: data: data: data: data: data:
l_mktelm_fieldnm type RSFIELDNM. l_respper_fieldnm type RSFIELDNM. l_bpartner_fieldnm type RSFIELDNM. l_user_name_fieldnm type RSFIELDNM. l_username_fieldnm type RSFIELDNM. l_orgunit_fieldnm type RSFIELDNM.
data: l_type_mktelm type RSD_DTELNM. data: l_type_respper type RSD_DTELNM. data: l_ref_mktelm type ref to data. data: l_ref_respper type ref to data. field-symbols: type any. field-symbols: type any. data: l_type_bpartner type RSD_DTELNM. data: l_type_user_name type RSD_DTELNM. data: l_ref_bpartner type ref to data. data: l_ref_user_name type ref to data. field-symbols: type any. field-symbols: type any. data: l_type_username type RSD_DTELNM. data: l_type_orgunit type RSD_DTELNM. data: l_ref_username type ref to data. data: l_ref_orgunit type ref to data. field-symbols: type any. field-symbols: type any. data: data: data: data:
l_t_columns_mktelm type standard table of string. l_t_columns_bpartner type standard table of string. l_t_columns_username type standard table of string. l_columns type string.
data: data: data: data: data: data: data: data:
l_where_string type string. l_record_no type i. l_subrc type sysubrc. l_t_attributes type standard table of RSD_S_IOBJNM. l_attributes type RSD_S_IOBJNM. l_data type RSNDI_S_CHAVL. l_t_data type standard table of RSNDI_S_CHAVL. l_t_messages type standard table of RSNDI_S_MESSAGE.
CALL FUNCTION 'RSD_CHKTAB_GET_FOR_CHA_BAS' EXPORTING I_CHABASNM = '0CRM_MKTELM' * I_NSPACEGEN = * I_S_VIOBJ = * I_T_ATR = IMPORTING
70
3 Appendix A: Common CRM Business Objects
* E_CHKTAB = E_CHNTAB = l_mktelm_tabname * E_CHTTAB = * E_TXTTAB = * E_SIDTAB = * E_SIDVIEW = * E_ASITAB = * E_ASISTR = * E_ASTTAB = * E_CHKNEW = EXCEPTIONS NAME_ERROR =1 OTHERS = 2. IF SY-SUBRC 0. write: / 'error in retrieving name of master data table for 0CRM_MKTELM.'. exit. ENDIF. CALL FUNCTION 'RSD_IOBJ_GET' EXPORTING I_IOBJNM = '0CRM_MKTELM' * I_OBJVERS = RS_C_OBJVERS-ACTIVE * I_BYPASS_BUFFER = RS_C_FALSE * I_IGNORE_BCTCOMP = RS_C_FALSE * I_WITH_DTEL = RS_C_TRUE IMPORTING E_S_VIOBJ = l_viobj * E_S_IOBJ = * E_S_VCHA = * E_S_KYF = * E_S_TIM = * E_S_UNI = * E_S_DPA = * E_S_COB_PRO = * E_T_IOBJ_CMP = E_T_ATR = l_t_atr * E_T_ATR_NAV = * E_T_ATRNAVT = * E_T_IOBJT = * E_S_AROUT = * E_S_AROUTT = * E_T_AABAP = * E_T_IOBJ_HIE = EXCEPTIONS IOBJ_NOT_FOUND =1 ILLEGAL_INPUT =2 BCT_COMP_INVALID =3 OTHERS = 4. IF SY-SUBRC 0. write: / 'error in retrieving infoobject metadata for 0CRM_MKTELM.'. exit. ENDIF. l_mktelm_fieldnm = l_viobj-fieldnm. read table l_t_atr transporting no fields with key attrinm = '0BPARTNER'. if sy-subrc ne 0. write: / '0BPARTNER is not an attribute to 0CRM_MKTELM.'. exit. endif. read table l_t_atr transporting no fields
71
3 Appendix A: Common CRM Business Objects
with key attrinm = '0CRM_MKTORG'. if sy-subrc ne 0. write: / '0CRM_MKTORG is not an attribute to 0CRM_MKTELM.'. exit. endif. CALL FUNCTION 'RSD_FIELDINFO_GET_FOR_IOBJ' EXPORTING I_IOBJNM = '0CRM_MKTELM' * I_TH_TLOGO = IMPORTING * E_FIELDNM = E_DTELNM = l_type_mktelm * E_DOMANM = * E_CHKTAB = * E_OUTPUTLEN = EXCEPTIONS NAME_ERROR =1 IOBJ_NOT_FOUND =2 OTHERS = 3. IF SY-SUBRC 0. write: / 'data element for 0CRM_MKTELM not found.'. exit. ENDIF. CALL FUNCTION 'RSD_IOBJ_GET' EXPORTING I_IOBJNM = '0BP_RESPPER' * I_OBJVERS = RS_C_OBJVERS-ACTIVE * I_BYPASS_BUFFER = RS_C_FALSE * I_IGNORE_BCTCOMP = RS_C_FALSE * I_WITH_DTEL = RS_C_TRUE IMPORTING E_S_VIOBJ = l_viobj * E_S_IOBJ = * E_S_VCHA = * E_S_KYF = * E_S_TIM = * E_S_UNI = * E_S_DPA = * E_S_COB_PRO = * E_T_IOBJ_CMP = * E_T_ATR = * E_T_ATR_NAV = * E_T_ATRNAVT = * E_T_IOBJT = * E_S_AROUT = * E_S_AROUTT = * E_T_AABAP = * E_T_IOBJ_HIE = EXCEPTIONS IOBJ_NOT_FOUND =1 ILLEGAL_INPUT =2 BCT_COMP_INVALID =3 OTHERS = 4. IF SY-SUBRC 0. write: / 'error in retrieving infoobject metadata for 0BP_RESPPER.'. exit. ENDIF. l_respper_fieldnm = l_viobj-fieldnm.
72
3 Appendix A: Common CRM Business Objects
CALL FUNCTION 'RSD_FIELDINFO_GET_FOR_IOBJ' EXPORTING I_IOBJNM = '0BP_RESPPER' * I_TH_TLOGO = IMPORTING * E_FIELDNM = E_DTELNM = l_type_respper * E_DOMANM = * E_CHKTAB = * E_OUTPUTLEN = EXCEPTIONS NAME_ERROR =1 IOBJ_NOT_FOUND =2 OTHERS = 3. IF SY-SUBRC 0. write: / 'data element for 0BP_RESPPER not found.'. exit. ENDIF. create data l_ref_mktelm type (l_type_mktelm). IF SY-SUBRC 0. write: / 'create data for 0CRM_MKTELM not working.'. exit. ENDIF. create data l_ref_respper type (l_type_respper). IF SY-SUBRC 0. write: / 'create data for 0BP_RESPPER not working.'. exit. ENDIF. assign l_ref_mktelm->* to . IF SY-SUBRC 0. write: / 'assign for 0CRM_MKTELM not working.'. exit. ENDIF. assign l_ref_respper->* to . IF SY-SUBRC 0. write: / 'assign for 0BP_RESPPER not working.'. exit. ENDIF. CALL FUNCTION 'RSD_CHKTAB_GET_FOR_CHA_BAS' EXPORTING I_CHABASNM = '0BPARTNER' * I_NSPACEGEN = * I_S_VIOBJ = * I_T_ATR = IMPORTING * E_CHKTAB = E_CHNTAB = l_bpartner_tabname * E_CHTTAB = * E_TXTTAB = * E_SIDTAB = * E_SIDVIEW = * E_ASITAB = * E_ASISTR = * E_ASTTAB = * E_CHKNEW = EXCEPTIONS NAME_ERROR =1 OTHERS = 2.
73
3 Appendix A: Common CRM Business Objects
IF SY-SUBRC 0. write: / 'error in retrieving name of master data table for 0BPARTNER.'. exit. ENDIF. refresh l_t_atr. CALL FUNCTION 'RSD_IOBJ_GET' EXPORTING I_IOBJNM = '0BPARTNER' * I_OBJVERS = RS_C_OBJVERS-ACTIVE * I_BYPASS_BUFFER = RS_C_FALSE * I_IGNORE_BCTCOMP = RS_C_FALSE * I_WITH_DTEL = RS_C_TRUE IMPORTING E_S_VIOBJ = l_viobj * E_S_IOBJ = * E_S_VCHA = * E_S_KYF = * E_S_TIM = * E_S_UNI = * E_S_DPA = * E_S_COB_PRO = * E_T_IOBJ_CMP = E_T_ATR = l_t_atr * E_T_ATR_NAV = * E_T_ATRNAVT = * E_T_IOBJT = * E_S_AROUT = * E_S_AROUTT = * E_T_AABAP = * E_T_IOBJ_HIE = EXCEPTIONS IOBJ_NOT_FOUND =1 ILLEGAL_INPUT =2 BCT_COMP_INVALID =3 OTHERS = 4. IF SY-SUBRC 0. write: / 'error in retrieving infoobject metadata for 0BPARTNER.'. exit. ENDIF. l_bpartner_fieldnm = l_viobj-fieldnm. CALL FUNCTION 'RSD_FIELDINFO_GET_FOR_IOBJ' EXPORTING I_IOBJNM = '0BPARTNER' * I_TH_TLOGO = IMPORTING * E_FIELDNM = E_DTELNM = l_type_bpartner * E_DOMANM = * E_CHKTAB = * E_OUTPUTLEN = EXCEPTIONS NAME_ERROR =1 IOBJ_NOT_FOUND =2 OTHERS = 3. IF SY-SUBRC 0. write: / 'data element for 0BPARTNER not found.'. exit. ENDIF. read table l_t_atr transporting no fields
74
3 Appendix A: Common CRM Business Objects
with key attrinm = '0USER_NAME'. if sy-subrc ne 0. write: / '0USER_NAME is not an attribute to 0BPARTNER.'. exit. endif. CALL FUNCTION 'RSD_IOBJ_GET' EXPORTING I_IOBJNM = '0USER_NAME' * I_OBJVERS = RS_C_OBJVERS-ACTIVE * I_BYPASS_BUFFER = RS_C_FALSE * I_IGNORE_BCTCOMP = RS_C_FALSE * I_WITH_DTEL = RS_C_TRUE IMPORTING E_S_VIOBJ = l_viobj * E_S_IOBJ = * E_S_VCHA = * E_S_KYF = * E_S_TIM = * E_S_UNI = * E_S_DPA = * E_S_COB_PRO = * E_T_IOBJ_CMP = * E_T_ATR = * E_T_ATR_NAV = * E_T_ATRNAVT = * E_T_IOBJT = * E_S_AROUT = * E_S_AROUTT = * E_T_AABAP = * E_T_IOBJ_HIE = EXCEPTIONS IOBJ_NOT_FOUND =1 ILLEGAL_INPUT =2 BCT_COMP_INVALID =3 OTHERS = 4. IF SY-SUBRC 0. write: / 'error in retrieving infoobject metadata for 0BPARTNER.'. exit. ENDIF. l_user_name_fieldnm = l_viobj-fieldnm. CALL FUNCTION 'RSD_FIELDINFO_GET_FOR_IOBJ' EXPORTING I_IOBJNM = '0USER_NAME' * I_TH_TLOGO = IMPORTING * E_FIELDNM = E_DTELNM = l_type_user_name * E_DOMANM = * E_CHKTAB = * E_OUTPUTLEN = EXCEPTIONS NAME_ERROR =1 IOBJ_NOT_FOUND =2 OTHERS = 3. IF SY-SUBRC 0. write: / 'data element for 0USER_NAME not found.'. exit. ENDIF. create data l_ref_bpartner type (l_type_bpartner).
75
3 Appendix A: Common CRM Business Objects
IF SY-SUBRC 0. write: / 'create data for 0BPARTNER not working.'. exit. ENDIF. create data l_ref_user_name type (l_type_user_name). IF SY-SUBRC 0. write: / 'create data for 0USER_NAME not working.'. exit. ENDIF. assign l_ref_bpartner->* to . IF SY-SUBRC 0. write: / 'assign for 0BPARTNER not working.'. exit. ENDIF. assign l_ref_user_name->* to . IF SY-SUBRC 0. write: / 'assign for 0USER_NAME not working.'. exit. ENDIF. CALL FUNCTION 'RSD_CHKTAB_GET_FOR_CHA_BAS' EXPORTING I_CHABASNM = '0USERNAME' * I_NSPACEGEN = * I_S_VIOBJ = * I_T_ATR = IMPORTING * E_CHKTAB = E_CHNTAB = l_username_tabname * E_CHTTAB = * E_TXTTAB = * E_SIDTAB = * E_SIDVIEW = * E_ASITAB = * E_ASISTR = * E_ASTTAB = * E_CHKNEW = EXCEPTIONS NAME_ERROR =1 OTHERS = 2. IF SY-SUBRC 0. write: / 'error in retrieving name of master data table for 0USERNAME.'. exit. ENDIF. refresh l_t_atr. CALL FUNCTION 'RSD_IOBJ_GET' EXPORTING I_IOBJNM = '0USERNAME' * I_OBJVERS = RS_C_OBJVERS-ACTIVE * I_BYPASS_BUFFER = RS_C_FALSE * I_IGNORE_BCTCOMP = RS_C_FALSE * I_WITH_DTEL = RS_C_TRUE IMPORTING E_S_VIOBJ = l_viobj * E_S_IOBJ = * E_S_VCHA = * E_S_KYF = * E_S_TIM = * E_S_UNI = * E_S_DPA =
76
3 Appendix A: Common CRM Business Objects
* E_S_COB_PRO = * E_T_IOBJ_CMP = E_T_ATR = l_t_atr * E_T_ATR_NAV = * E_T_ATRNAVT = * E_T_IOBJT = * E_S_AROUT = * E_S_AROUTT = * E_T_AABAP = * E_T_IOBJ_HIE = EXCEPTIONS IOBJ_NOT_FOUND =1 ILLEGAL_INPUT =2 BCT_COMP_INVALID =3 OTHERS = 4. IF SY-SUBRC 0. write: / 'error in retrieving infoobject metadata for 0USERNAME.'. exit. ENDIF. l_username_fieldnm = l_viobj-fieldnm. CALL FUNCTION 'RSD_FIELDINFO_GET_FOR_IOBJ' EXPORTING I_IOBJNM = '0USERNAME' * I_TH_TLOGO = IMPORTING * E_FIELDNM = E_DTELNM = l_type_username * E_DOMANM = * E_CHKTAB = * E_OUTPUTLEN = EXCEPTIONS NAME_ERROR =1 IOBJ_NOT_FOUND =2 OTHERS = 3. IF SY-SUBRC 0. write: / 'data element for 0USERNAME not found.'. exit. ENDIF. read table l_t_atr transporting no fields with key attrinm = '0ORGUNIT'. if sy-subrc ne 0. write: / '0ORGUNIT is not an attribute to 0USERNAME.'. exit. endif. CALL FUNCTION 'RSD_IOBJ_GET' EXPORTING I_IOBJNM = '0ORGUNIT' * I_OBJVERS = RS_C_OBJVERS-ACTIVE * I_BYPASS_BUFFER = RS_C_FALSE * I_IGNORE_BCTCOMP = RS_C_FALSE * I_WITH_DTEL = RS_C_TRUE IMPORTING E_S_VIOBJ = l_viobj * E_S_IOBJ = * E_S_VCHA = * E_S_KYF = * E_S_TIM = * E_S_UNI = * E_S_DPA =
77
3 Appendix A: Common CRM Business Objects
* * * * * * * * * *
E_S_COB_PRO = E_T_IOBJ_CMP = E_T_ATR = E_T_ATR_NAV = E_T_ATRNAVT = E_T_IOBJT = E_S_AROUT = E_S_AROUTT = E_T_AABAP = E_T_IOBJ_HIE = EXCEPTIONS IOBJ_NOT_FOUND =1 ILLEGAL_INPUT =2 BCT_COMP_INVALID =3 OTHERS = 4. IF SY-SUBRC 0. write: / 'error in retrieving infoobject metadata for 0ORGUNIT.'. exit. ENDIF. l_orgunit_fieldnm = l_viobj-fieldnm. CALL FUNCTION 'RSD_FIELDINFO_GET_FOR_IOBJ' EXPORTING I_IOBJNM = '0ORGUNIT' * I_TH_TLOGO = IMPORTING * E_FIELDNM = E_DTELNM = l_type_orgunit * E_DOMANM = * E_CHKTAB = * E_OUTPUTLEN = EXCEPTIONS NAME_ERROR =1 IOBJ_NOT_FOUND =2 OTHERS = 3. IF SY-SUBRC 0. write: / 'data element for 0ORGUNIT not found.'. exit. ENDIF. create data l_ref_username type (l_type_username). IF SY-SUBRC 0. write: / 'create data for 0USERNAME not working.'. exit. ENDIF. create data l_ref_orgunit type (l_type_orgunit). IF SY-SUBRC 0. write: / 'create data for 0ORGUNIT not working.'. exit. ENDIF. assign l_ref_username->* to . IF SY-SUBRC 0. write: / 'assign for 0USERNAME not working.'. exit. ENDIF. assign l_ref_orgunit->* to . IF SY-SUBRC 0. write: / 'assign for 0ORGUNIT not working.'. exit. ENDIF.
78
3 Appendix A: Common CRM Business Objects
l_columns = l_mktelm_fieldnm. append l_columns to l_t_columns_mktelm. l_columns = l_respper_fieldnm. append l_columns to l_t_columns_mktelm. l_columns = l_user_name_fieldnm. append l_columns to l_t_columns_bpartner. l_columns = l_orgunit_fieldnm. append l_columns to l_t_columns_username. l_record_no = 0. refresh l_t_data. select (l_t_columns_mktelm) from (l_mktelm_tabname) into (, ) where objvers = 'A'. if is not initial. concatenate l_bpartner_fieldnm ' = ''' ''' and objvers = ''A''' into l_where_string. select single (l_t_columns_bpartner) from (l_bpartner_tabname) into where (l_where_string). if sy-subrc eq 0 and is not initial. concatenate l_username_fieldnm ' = ''' ''' and objvers = ''A''' into l_where_string. select single (l_t_columns_username) from (l_username_tabname) into where (l_where_string). if sy-subrc eq 0 and is not initial. write: / , ' ', , ' ', , ' ', . l_record_no = l_record_no + 1. l_data-record_no = l_record_no. l_data-iobjnm = '0CRM_MKTELM'. l_data-value = . append l_data to l_t_data. l_data-iobjnm = '0CRM_MKTORG'. l_data-value = . append l_data to l_t_data. endif. endif. endif. endselect. l_attributes = '0CRM_MKTORG'. append l_attributes to l_t_attributes. CALL FUNCTION 'RSNDI_MD_ATTRIBUTES_UPDATE' EXPORTING I_IOBJNM = '0CRM_MKTELM' * I_UPDATE_ALL_ATTRIBUTES = * I_CHAVL_ENQUEUE = RS_C_TRUE * I_DB_COMMIT = RS_C_FALSE * I_COMMIT_WORK = RS_C_FALSE IMPORTING E_SUBRC = l_subrc TABLES I_T_ATTRIBUTES = l_t_attributes I_T_DATA = l_t_data E_T_MESSAGES = l_t_messages. if l_subrc is initial and l_t_messages is initial.
79
3 Appendix A: Common CRM Business Objects
CALL FUNCTION 'RSDMD_MD_ACTIVATE' EXPORTING I_CHABASNM = '0CRM_MKTELM'. endif.
80
3 Appendix A: Common CRM Business Objects
Changes to Mime Repository [BI] In order to avoid Java Script errors in BW Webtemplates the file JSBCTBasic.js from Business Content has to be replaced in the Mime repository. In transaction SE80 go to the Mime repository and follow the path SAP -> BW -> BCT -> JavaScript. In the context menu for JSBCTBasic.js go to “change”. Then replace the content of the file with the content of the file JSBCTBasic_NWfix.txt in the archive W3Ed2_Webtemplates.zip. Then save and exit.
81
3 Appendix A: Common CRM Business Objects
Customizing of Product [BI] In the BW system in SPRO specify value 18 for Product Id length as follows:
Similarly in TA OMSL specify the length of Material as 18 and save the result. (If you do not maintain this number you will not be able to view Masterdata for 0CRM_PROD in se16.)
82
3 Appendix A: Common CRM Business Objects
83
3 Appendix A: Common CRM Business Objects
84
3 Appendix A: Common CRM Business Objects
Important Note on Data Consistency [BI] Because Userstatus is now required in all reporting layers, including object types from previous waves (Opportunities, Activities, and Leads), the data upload for them has to be reinitialized. Only then will Userstatus be available for objects created in previous SAP CRM on-demand solution waves.
85
3 Appendix A: Common CRM Business Objects
Opportunities [BI] The following steps are the main steps to configure BI business objects. The configuration steps depend on the CRM business process. For example, creation of an initial InfoPackage is not necessary for texts or org unit because only a full upload is possible for these business objects. All upload processes that have to be scheduled on a regular basis are included in process chains. All other uploads deal with objects that are never changed (for example, texts from domains) or that are specified in customizing (for example, opportunity phases). For these, data only has to be transferred once.
86
3 Appendix A: Common CRM Business Objects
Create / Execute InfoPackages for Opportunity Header 0CRM_OPPT_H [BI] 1. Log on to BI system. 2. Call transaction RSA1. 3. Modeling: InfoProvider. 4. Search for 0CRM_C04. 5. Expand InfoCube 0CRM_C04 to DataSource 0CRM_OPPT_H.
InfoPackage description (should start with the word “INITIAL”), for example, description “Initial Opportunity Header”
87
3 Appendix A: Common CRM Business Objects
88
3 Appendix A: Common CRM Business Objects
6. Check that update mode Initialize Delta Process is active.
7. Check that data target DSO: 0CRM_OPPH is available.
8. Check processing (PSA).
89
3 Appendix A: Common CRM Business Objects
9. Save the InfoPackage.
90
3 Appendix A: Common CRM Business Objects
10. Expand to initial Upload InfoPackage Opportunity header (the object created above “Initial Opportunity Header”). 11. Start initial upload.
91
3 Appendix A: Common CRM Business Objects
Delta mode is necessary to upload data at any time. After successful initial upload, you will be able to create a delta InfoPackage. 1. Log on to BI system. 2. Call transaction RSA1. 3. Select Info Provider. 4. Expand to DataSource 0CRM_OPPT_H. 5. Create InfoPackage.
92
3 Appendix A: Common CRM Business Objects
6. Save Delta InfoPackage Opportunity header, description “Delta Opportunity Header”.
93
3 Appendix A: Common CRM Business Objects
Create/ Execute InfoPackages for Opportunity Items 0CRM_OPPT_I [BI] Perform the same steps as for Opportunity Header, but for 0CRM_OPPT_I.
94
3 Appendix A: Common CRM Business Objects
Create/Execute Process Chain for Opportunity (Header & Items) [BI] Process chains will be necessary for delta upload to start a periodic upload for opportunity
1. Call transaction RSPC. 2. Select process chain. 3. Terminate variant. 4. Activate process chain. 5. Start process chain.
95
3 Appendix A: Common CRM Business Objects
Activity [BI]
96
3 Appendix A: Common CRM Business Objects
Create / Execute InfoPackages for Activities [BI] Perform the same steps as for initial upload of Opportunity Header, but for 0CRM_SALES_ACT_1.
97
3 Appendix A: Common CRM Business Objects
Create / Execute Process Chain for Activity [BI]
1. Call transaction RSPC. 2. Select process chain. 3. Terminate variant. 4. Activate process chain. 5. Start process chain. Important remark: Activity and Contact uploads target the same ODS objects. Therefore the upload of activities should be finished before the upload of contacts is started and vice versa.
98
3 Appendix A: Common CRM Business Objects
Business Partner [BI]
99
3 Appendix A: Common CRM Business Objects
Create / Execute InfoPackages for Business Partner Master Data [BI] 1. Log on to BI system. 2. Call transaction RSA1. 3. Modeling: InfoSources. 4. Search for 0BPARTNER (type Attribute). 5. Expand to DataSource 0BP_ID_ATTR. 6. Create initial InfoPackage. Use description “Initial 0BP_ID_ATTR”. 7. Execute the InfoPackage (Update: Initialize Delta Process). 8. Create InfoPackage for delta upload. Proceed similarly for the following DataSources •
0BP_RELATIONS_ATTR
•
0BP_DEF_ADDRESS_ATTR
•
0BPARTNER_ATTR
100
3 Appendix A: Common CRM Business Objects
Create / Execute Full InfoPackages for Org Unit [BI] 1. Log on to BI system 2. Call transaction RSA1, Modeling → DataSources 3. Search for 0BPARTNER, locate data source 0BP_UNAME_ORGUNIT_ATTR. 4. Create full InfoPackage for DataSource 0BP_UNAME_ORGUNIT_ATTR 5. Select Upload → Full upload 6. Click Schedule and start full upload immediately
101
3 Appendix A: Common CRM Business Objects
Create / Execute Process Chain for Business Partner Master Data [BI]
102
3 Appendix A: Common CRM Business Objects
1. Call transaction RSPC. 2. Select process chain. 3. Terminate variant. 4. Activate process chain. 5. Start process chain.
103
3 Appendix A: Common CRM Business Objects
Organizational Unit and User Name [BI]
104
3 Appendix A: Common CRM Business Objects
ate / Execute Full InfoPackages for Org Unit Master Data [BI] 1. Log on to BI system. 2. Call transaction RSA1. 3. Modeling: InfoSources → DataSource 0CRM_ORGUNIT_HR01_HIER. 4. Create full InfoPackage. 5. Start full upload. Repeat the steps for the following DataSources: •
0CRM_ORGUNIT_SALES_ATTR
•
0CRM_ORGUNIT_TEXT
105
3 Appendix A: Common CRM Business Objects
reate / Execute Full InfoPackages for User Name Master Data [BI] 1. Log on to BI 2. Call transaction RSA1 3. Modeling: InfoSource → InfoObject: 0USERNAME 4. Create full InfoPackage
106
3 Appendix A: Common CRM Business Objects
reate Process Chain for Org Unit [BI]
1. Call transaction RSPC. 2. Select process chain. 3. Terminate variant. 4. Activate process chain.
107
3 Appendix A: Common CRM Business Objects
5. Start process chain.
108
3 Appendix A: Common CRM Business Objects
Campaign [BI]
109
3 Appendix A: Common CRM Business Objects
Create / Execute InfoPackages for Outbound Customer Contact [BI] 1. Log on to BI system. 2. Call transaction RSA1. 3. Modeling: InfoProvider. 4. Search for 0CRM_C06. 5. Expand InfoCube 0CRM_C06 to the DataSource 0CRM_CONTACT_OUT. 6. InfoPackage description (start with the word INITIAL) for example, description Initial Contact out. 7. After creating Initial Contact Out, check the update mode Initialize Delta Process. 8. Check that data target DSO: 0CRM_CT_O is available. 9. Check processing (PSA). 10. Save the InfoPackage. 11. Start the initial upload. To upload data at any time, delta mode is necessary. After successful initial upload, you will be able to create a delta InfoPackage. 1. Log on to BI system. 2. Call transaction RSA1 3. Modeling: InfoProvider. 4. Search for 0CRM_C06. 5. Expand InfoCube 0CRM_C06 to DataSource 0CRM_CONTACT_OUT. 6. Check that data target DSO: 0CRM_CT_O is available. 7. Check processing (PSA). 8. Save the InfoPackage. 9. Start the delta upload (process chain).
110
3 Appendix A: Common CRM Business Objects
Create /Execute InfoPackages for Inbound Customer Contact 0CRM_CONTACT_IN [BI] 1. Create initial and delta InfoPackages as in 3.8.1. 2. Start the delta upload (process chain).
111
3 Appendix A: Common CRM Business Objects
Create/Execute InfoPackages for Marketing Elements 0CRM_MKTELM_TEXT & MKTELM5_ATTR [BI] Create initial and delta InfoPackages for marketing elements 0CRM_MKTELM_TEXT & 0CRM_MKTELM5-ATTR.
112
3 Appendix A: Common CRM Business Objects
Create/Execute Process Chain for Campaign [BI] Perform the same steps as before to create the following process chain:
Important remark: Activity and Contact uploads target the same ODS objects. Therefore the upload of activities should be finished before the upload of contacts is started and vice versa.
113
3 Appendix A: Common CRM Business Objects
Leads [BI]
114
3 Appendix A: Common CRM Business Objects
ate/Execute InfoPackages for Lead Header 0CRM_LEAD_H [BI] Perform the same steps as for initial and delta campaign but for DataSource 0CRM_LEAD_H
115
3 Appendix A: Common CRM Business Objects
Create/Execute InfoPackage for Lead GUID 0CRM_LEAD_ATTR [BI] Perform the same steps as for initial and delta lead, but for DataSource 0CRM_LEAD_ATTR
116
3 Appendix A: Common CRM Business Objects
Create/Execute Process Chain for Lead [BI] Perform the same steps as for a campaign, but one process chain for the following DataSources: 0CRM_LEAD_H 0CRM_LEAD_ATTR
117
3 Appendix A: Common CRM Business Objects
Quotations [BI]
118
3 Appendix A: Common CRM Business Objects
Create InfoPackage for Quotations [BI] DataSource is 0CRM_QUOTA_ORDER_I.
119
3 Appendix A: Common CRM Business Objects
Create Process Chain for Quotations [BI]
120
3 Appendix A: Common CRM Business Objects
Service Tickets [BI]
121
3 Appendix A: Common CRM Business Objects
Create InfoPackage for Service Ticket Headers [BI] DataSource 0CRM_SRV_PROCESS_H.
122
3 Appendix A: Common CRM Business Objects
Create InfoPackage for Service Ticket Items [BI] DataSource 0CRM_SRV_PROCESS_I
123
3 Appendix A: Common CRM Business Objects
Create Process Chain for Service Tickets [BI]
124
3 Appendix A: Common CRM Business Objects
Product [BI] Create InfoPackage for the following DataSources and combine the upload process in one process chain: 0PRODUCT_TEXT 0PRODUCT_ATTR 0CRM_PRODUCT_ATTR 0CRM_PROD_ATTR
125
3 Appendix A: Common CRM Business Objects
Regular Upload of CRM Master Data [BI] In SAP CRM on-demand solution Wave 3, power users may change some CRM master data and even change CRM Customizing. Therefore data should be uploaded regularly from the following CRM DataSources ZCXP_STAONEACTI_TEXT ZCXP_STAONEOPPT_TEXT ZCXP_STAONELEAD_TEXT ZCXP_STAONEQUOT_TEXT ZCXP_STAONESVTK_TEXT 0CRM_PROC_TYPE_TEXT 0CRM_CAT_CATEGORY_TEXT 0CRM_CAT_CATEGORY_ATTR 0CRM_CAT_SCHEME_TEXT
126
3 Appendix A: Common CRM Business Objects
Upload of Master Data and Texts from CRM Customizing or from Fixed Domains [BI] For the following list of CRM DataSources, data only needs be uploaded once (after the CRM system has been customized for SAP CRM on-demand solution): 0COUNTRY_TEXT 0CRM_ACT_GOAL_TEXT 0CRM_CATEGORY_ATTR 0CRM_DIRECT_TXT 0CRM_OBJ_TYPE_TEXT 0CRM_OPPIMPOR_TEXT 0CRM_OPPT_CNTRPHASE_TEXT 0CRM_OPPT_CYCLE_TEXT 0CRM_OPPT_TYPE_TEXT 0CRM_PRIO_TXT 0CRM_SOURCE_TEXT 0CRM_S_BW_CAT_CODE_TEXT 0CRM_S_BW_CAT_GROUP_TEXT 0CRM_S_BW_CAT_TYPE_TEXT 0REGION_TEXT 0STAONESYS0_TEXT 0STAONESYS1_TEXT 0STAONESYS4_TEXT 0STAONESYS8_TEXT 0STAONEUSS0_TEXT 0STATECSYS2_TEXT 0CRM_OPPT_ PHASE_TEXT 0CRM_LEAD_TYPE_TEXT 0CRMCHANNEL_TEXT 0CRM_PLGRP_TEXT 0STAMKTSYS0_TEXT 0STAMKTSYS1_TEXT 0STAMKTSYS2_TEXT 0STAMKTSYS3_TEXT 0CRM_TACTIC_TEXT 0CRM_OBJEC4_TEXT 0CRM_PRIO_TEXT 0CRM_LEAD_QL_TEXT 0CRMCAMPTYP_TEXT Create InfoPackages for the upload and load the data to SAP BW.
127
3 Appendix A: Common CRM Business Objects
Currencies [BI] Since power users maintain currencies and currency conversion in SAP CRM on-demand solution, currencies and currency conversion rates need to be uploaded regularly from CRM to BW.
128
3 Appendix A: Common CRM Business Objects
InfoObject “BP Number in External System” (0BP_EXTERN) [BI] This InfoObject is not used in the BI Content for CRM on Demand, but is has been used several times in value added services. We therefore recommend to also allow lower case characters:
129
3 Appendix A: Common CRM Business Objects
3 Appendix A: Common CRM Business Objects Business Partner (0BPARTNER) Issue
InfoSource
DataSource / Transfer Rule
Upload Method
Partner: ID Number
0BP_ID_NUMBER_ATTR
0BP_ID_ATTR
Delta
BP: Relationships
0BPRELATION_ATTR
0BP_RELATIONS_ATTR
Delta
BP: Standard Address
0BP_DEF_ADDRESS_ATTR
0BP_DEF_ADDRESS_ATTR
Delta
BP: master record
0BPARTNER_ATTR
0BPARTNER_ATTR
Delta
BP: Texts
0BPARTNER_TEXT
0BPARTNER_TEXT
Delta
User/ Name Org. Unit
0BPARTNER
0BP_UNAME_ORGUNIT_ATTR
Delta
Organizational Unit Issue
InfoSource
DataSource
Process Chain
Organ. Hierarchies
0ORGUNIT
0CRM_ORGUNIT_HR01_HIER
Full
Organ. Unit Attr
0ORGUNIT
0CRM_ORGUNIT_SALES_ATTR
Full
Organ Unit: Texts
0ORGUNIT
0CRM_ORGUNIT_TEXT
Full
User Name Issue
InfoSource
DataSource
Process Chain
User Name Attributes
0USERNAME
0CRM_HR_UNAME_ORG
Full
User Name Texts
0USERNAME
0CSM_USER_TEXT
Full
Catalog Issue
InfoSource
DataSource
Upload Mode
Catalog Code
0CAT_CODE
0CRM_S_BW_CAT_CODE_TEXT
Full
Catalog Code group
0CAT_GROUP
0CRM_S_BW_CAT_GROUP_TEXT
Full
Catalog Type
0CAT_TYPE
0CRM_S_BW_CAT_TYPE_TEXT
Full
Category Issue
InfoSource
DataSource
Upload Mode
Category attribute
0CRM_CAT
0CRM_CATEGORY_ATTR
Full
Category (texts)
0CRM_CAT
0CRM_CATEGORY_TEXT
Full
Business Transaction Object Type Issue
InfoSource
DataSource
Upload Mode
Business Transaction Object Type
0CRM_OBJTYP
0CRM_OBJ_TYPE_TEXT
Full
Business Transaction Type
130
3 Appendix A: Common CRM Business Objects
Issue
InfoSource
DataSource
Upload Mode
Business Transaction Type
0CRM_PRCTYP
0CRM_PROC_TYPE_TEXT
Full
CRM Status Life Cycle (One Order) Issue
InfoSource
DataSource
Upload Mode
CRM Status Life Cycle (One Order)
0STAONESYS0
0STAONESYS0_TEXT
Full
CRM Status Planned (One Order) Issue
InfoSource
DataSource
Upload Mode
CRM Status Planned (One Order)
0STAONESYS1
0STAONESYS1_TEXT
Full
CRM Status Opportunity /Lead (One Order) Issue
InfoSource
DataSource
Upload Mode
CRM Status Opportunity/Lead (One Order)
0STAONESYS4
0STAONESYS4_TEXT
Full
CRM Status: Rejected (One Order) Issue
InfoSource
DataSource
Upload Mode
CRM Status: rejected (One Order)
0STAONESYS8
0STAONESYS8_TEXT
Full
Contacts User Status: Life Cycle Status Issue
InfoSource
DataSource
Upload Mode
Contacts User Status: Life Cycle Status
0STAONEUSS0
0STAONEUSS0_TEXT
Full
CRM Status: Incorrect Issue
InfoSource
DataSource
Upload Mode
CRM Status: incorrect
0STATECSYS2
0STATECSYS2_TEXT
Full
Country Issue
InfoSource
DataSource
Upload Mode
Country
0COUNTRY
0COUNTRY_TEXT
Full
Region Issue
InfoSource
DataSource
Upload Mode
0REGION
0REGION_TEXT
0REGION_TEXT
Full
131
3 Appendix A: Common CRM Business Objects
4 Appendix B: Relevant Business Objects for CRM Sales Opportunities Issue
InfoCube
DSO
InfoSource
DataSource
Upload Mode
Header
0CRM_C04
0CRM_OPPH
0CRM_OPPT_H
0CRM_OPPT_H
Delta
Items
0CRM_C04
0CRM_OPPI
0CRM_OPPT_I
0CRM_OPPT_I
Delta
Activities Issue
InfoCube
DSO
InfoSource
DataSource
Upload Mode
Activities
0CSAL_C01
0SAL_DS01
0CRM_SALES_ACT_1
0CRM_SALES_ACT_1
Delta
Analysis Phase Issue
InfoSource
DataSource
Process Chain
Analysis Phase
0CRM_CNTRPH
0CRM_OPPT_CNTRPHASE_TEXT
Upload Mode Full
Current Opportunity Phase Issue
InfoSource
DataSource
Upload Mode
Analysis Phase of an Opportunity
0CRM_CURRPH
0CRM_OPPT_PHASE_TEXT
Full
Direction Issue
InfoSource
DataSource
Upload Mode
Direction (text)
0CRM_DIRECT
0CRM_DIRECT_TXT
Full
Target Issue
InfoSource
DataSource
Upload Mode
Target (text)
0CRM_OBJECT
0CRM_ACT_GOAL_TEXT
Full
Opportunity Priority Issue
InfoSource
DataSource
Upload Mode
Opportunity Priority
0CRM_OPPIMP
0CRM_OPPIMPOR_TEXT
Full
Opportunity Type Issue
InfoSource
DataSource
Upload Mode
Opportunity Type
0CRM_OPPTYP
0CRM_OPPT_TYPE_TEXT
Full
Priority Issue
InfoSource
DataSource
Upload Mode
Priority
0CRM_PRIO
0CRM_PRIO_TEXT
Full
132
3 Appendix A: Common CRM Business Objects
Priority
0CRM_PRIO_A
0CRM_PRIO_TEXT
Full
Sales Cycle Issue
InfoSource
DataSource
Upload Mode
Sales Cycle
0CRM_SLSCYC
0CRM_OPPT_CYCLE_TEXT
Full
Origin Opportunity/ Lead Issue
InfoSource
DataSource
Upload Mode
Origin Opportunity/ Lead
0CRM_SOURCE
0CRM_SOURCE_TEXT
Full
User Status Issue
InfoSource
DataSource
Upload Mode
User Status
0CRM_USSTAT
0CRM_USSTAT_TXT
Full
133
3 Appendix A: Common CRM Business Objects
5 Appendix C: Relevant Business Objects for CRM Marketing Campaign Issue
InfoCube
DSO
InfoSource
DataSource
Upload Mode
Outbound
0CRM_C06
0CRM_CT_O
0CRM_CONTACT_OUT
0CRM_CONTACT_OUT
Delta
Inbounds
0CRM_C07
0CRM_CT_I
0CRM_CONTACT_IN
0CRM_CONTACT_IN
Delta
Lead Issue
InfoCube
DSO
InfoSource
DataSource
Upload Mode
Lead
0MKTG_C01
0MKT_DS01
0CRM_LEAD_H
0CRM_LEAD_H
Delta
Lead Items
0MKTG_C01
0MKT_DS02
0CRM_LEAD_I
0CRM_LEAD_I
Delta
Marketing: Multiple Link Tracking Issue
DSO
InfoSource
DataSource
Upload Mode
CRM Marketing: Multiple Link Tracking
0CRM_MLIT
0CRM_MLI
0CRM_MLI
Delta
Lead GUID (Attribute) Issue
InfoSource
DataSource
Upload Mode
Lead GUID(attribute)
0CRM_LEAGUI
0CRM_LEAD_ATTR
Delta
Lead Type Issue
InfoSource
DataSource
Upload Mode
Lead type
0CRM_LEATYP
0CRM_LEAD_TYPE_TEXT
Full
Issue
InfoSource
DataSource
Upload Mode
Channel
0CRMCHANNEL
0CRMCHANNEL_TEXT
Full
Channel
BW Status (Marketing) Issue
InfoSource
DataSource
Upload Mode
BW Status
0STAMKTSYS0
0STAMKTSYS0_TEXT
Full
BW Status
0STAMKTSYS1
0STAMKTSYS1_TEXT
Full
BW Status
0STAMKTSYS2
0STAMKTSYS2_TEXT
Full
BW Status
0STAMKTSYS3
0STAMKTSYS3_TEXT
Full
Planning Profile Group Issue
InfoSource
DataSource
Upload Mode
Planning Profile Group
0CRM_PLGRP
0CRM_PLGRP_TEXT
Full
134
3 Appendix A: Common CRM Business Objects
135
3 Appendix A: Common CRM Business Objects
Tactic Issue
InfoSource
DataSource
Upload Mode
Tactic
0CRM_TACTIC
0CRM_TACTIC_TEXT
Full
Objective (s) Issue
InfoSource
DataSource
Upload Mode
Objective(s)
0CRM_OBJEC4
0CRM_OBJEC4_TEXT
Full
Priority Issue
InfoSource
DataSource
Upload Mode
Priority
0CRM_PRIO
0CRM_PRIO_TEXT
Full
Marketing Element Issue
InfoSource
DataSource
Upload Mode
Marketing Element Text
0CRM_MKTELM
0CRM_MKTELM_TEXT
Delta
Marketing Element Attributes
0CRM_MKTELM
0CRM_MTTELM5_ATTR
Delta
Lead Qualification Level Issue
InfoSource
DataSource
Upload Mode
Lead Qualification Level
0CRM_QUALEV
0CRM_LEAD_QL_TEXT
Full
Target Group Issue
InfoSource
DataSource
Upload Mode
Target group
0TGGRP_ID
0CRM_TGGRP_TEXT
Full
Mailing Item Guid Issue
InfoSource
DataSource
Upload Mode
CRM Mailing Item Guid
0CRM_MIG
0CRM_MAIL_GUID_ATTR
Full
Campaign Type Issue
InfoSource
DataSource
Upload Mode
Campaign Type
0CRMCAMPTYP
0CRMCAMPTYP_TEXT
Full
136
3 Appendix A: Common CRM Business Objects
6 Appendix E: Relevant Business Objects for the product CRM Product Issue
InfoSource
DataSource
Upload Mode
CRM Product
0PRODUCT
0PRODUCT_TEXT
Delta
0PRODUCT_GENERAL_ATTR
0PRODUCT_ATTR
Delta
0CRM_PROD_ATTR
0CRM_PROD_ATTR
Delta
0CRM_PRODUCT_ATTR
0CRM_PRODUCT_ATTR
Delta
137
3 Appendix A: Common CRM Business Objects
7 Appendix E: Relevant Business Objects for CRM Service Service Tickets Issue
InfoCube
DSO
InfoSource
DataSource
Upload Mode
Service Ticket Headers
0CSRV_C01
0CRM_PROH
0CRM_SERVICE_PROCESS_H
0CRM_SRV_PROCESS_H
Delta
Service Ticket Items
0CRM_PRI
0CRM_PROI
0CRM_SERVICE_PROCESS_I
0CRM_SRV_PROCESS_I
Delta
Multilevel Categorization Issue
InfoSource
DataSource
Upload Mode
Multilevel Categorization Category GUID
0CRMCC_CAT
0CRM_CAT_CATEGORY_ATTR
Delta
Multilevel Categorization Schema
0CRMCCSCHID
0CRM_CAT_SCHEME_TEXT
Delta
Multilevel Categorization Category
0CRMCCCATID
0CRM_CAT_CATEGORY_TEXT CXRCLNT701
Delta
138
3 Appendix A: Common CRM Business Objects
8 Appendix F: Objects for User Status Issue
InfoSource
DataSource
Upload Mode
User Status (Activities)
0STAONEACTI
ZCXP_STAONEACTI_TEXT
Full
User Status (Opportunities)
0STAONEOPPT
ZCXP_STAONEOPPT_TEXT
Full
User Status (Quotations)
0STAONEQUOT
ZCXP_STAONEQUOT_TEXT
Full
User Status (Service Ticket)
0STAONESVTK
ZCXP_STAONESVTK_TEXT
Full
139
3 Appendix A: Common CRM Business Objects
9 Appendix G: Transactions Transaction
Description
System
RSA1
Modeling DW- Workbench
BI
RSA2
DataSource Repository
Source System (BI or CRM)
RSA3
Extractor Checker
SourceSystem (BI or CRM)
RSA5
Install Business Content
SourceSystem (BI or CRM)
RSA6
Postprocess DataSources and Hierarchy
SourceSystem (BI or CRM)
RSA7
BW Delta Queue Monitor
SourceSystem (BI or CRM)
RSOR
Business Content
BI
SE16
Data Browser
All
SPRO
Customizing
All
SBIW
DataSource in BW
SourceSystem (BI or CRM)
SCC4
Client Administration
All
RS12
Overview of Master Data Locks
SourceSystem (BI or CRM)
RSDBC
DB Content
SourceSystem (BI or CRM)
RSMO
Data Load Monitor Start
BI
RSMON
Administrator Workbench (Monitoring)
BI
RSO2
OLTP Meta Data Repository
SourceSystem (BI or CRM)
RSPC
Process Chain Maintenance
BI
RSRT
Start of Report Monitor
BI
140
3 Appendix A: Common CRM Business Objects
141
View more...
Comments
