CRM Datasource Related SAP Note (Very Important)

4
SAP Note Header Data Symptom There may be problems or issues related to data tranfer from CRM to BW. Other Terms CRM-BW extraction,upload,initial,delta,full upload ,Sales Analytics,BWA1, BWA5, BWA7, authorization, gnrwb, performance, BaDI, CRM_BWA_MFLOW,extraction, RSA1,RSA7, RSA3, BW Status, BUS_TRANS_MSG, Reason and Prerequisites There could be errors in customization or program errors due to which data may not be transferred or incorrectly transferred to BW. Solution Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues) Question 2 : On executing transaction RSA3 I get records but I find 0 records when I load data from BW request.(No Data Available).How can I extract data in this case? Question 3 : The Deltas for my data source are not extracted . What can I do? Question 4: How can I extract the fields, which are not provided in the standard data source extraction ? Question 5: I am unable to extract user status correctly.What should I do? Question 6 : What can I do when the activity/Opportunity/Complaint reasons (Code,CodeGruppe,Katalogart) are not extracted? Question 7: What can I do if the deleted opportunities are not reflected in BW? Question 8: How do I activate the metadata? Question 9: I donot get any records for the delta upload of my attribute datasource(s).What is to be done? Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0 and various other BW status mean ? Question 11: How will I know which datasource to use? Solutions Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues) Suggestion 1: Please implement notes 653645 (Collective note) and 639072(Parallel Processing). The performance could be slow because of the wrong control parameters used for packaging. You can change the package size for the data extraction. Also note that changing the package size in the transaction SBIW would imply a change for all the extractors. Instead, you could follow the path in the bw system. Infopackage (scheduler) > Menu 'Scheduler' > 'DataS. default data transfer' > maintain the value as 1500 or 1000(This value is variable) The package size depends on the Resources available at the customer side(The no of parallel processes that could be assigned = 1.5 times the no of CPU's available approx.) Question 2 : On executing transaction RSA3 I get records but I find 0 records when I load data from BW request.(No Data Available) Suggestion 2: First check if there are any entries in the table CRMD_ORDER_INDEX.Only if there are entries in this table you can extract records. If this is not the case then,It is possible that the user does not have sufficient authorities for extraction of the relevant objects. Additionally, please review and implement the following notes 615670 161570 150315 692195 - FAQ: Sales Analytics and CRM-BW data Extraction Version 5 Validity: 03.09.2013 - active Language English (Master) Released On 03.09.2013 13:30:53 Release Status Released for Customer Component BW-BCT-CRM-SAL BW only - Sales Analytics BW-BCT-CRM BW only - Customer Relationship Management BW-BCT-CRM-BE BW only - Connection CRM - BW CRM-ANA-EXT Extractors CRM-ANA-EXT-API Generic Functions: Data exchange CRM/BW CRM-BTX-ANA-BW BW Data Exchange Priority Recommendations / Additional Info Category FAQ Other Components

description

CRM Datasource Related SAP Note (Very Important)

Transcript of CRM Datasource Related SAP Note (Very Important)

  • SAP Note

    Header Data

    Symptom

    There may be problems or issues related to data tranfer from CRM to BW.

    Other Terms

    CRM-BW extraction,upload,initial,delta,full upload ,Sales Analytics,BWA1, BWA5, BWA7, authorization, gnrwb, performance, BaDI, CRM_BWA_MFLOW,extraction, RSA1,RSA7, RSA3, BW Status, BUS_TRANS_MSG,

    Reason and Prerequisites

    There could be errors in customization or program errors due to which data may not be transferred or incorrectly transferred to BW.

    Solution

    Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues) Question 2 : On executing transaction RSA3 I get records but I find 0 records when I load data from BW request.(No Data Available).How can I extract data in this case? Question 3 : The Deltas for my data source are not extracted . What can I do? Question 4: How can I extract the fields, which are not provided in the standarddata source extraction ? Question 5: I am unable to extractuser status correctly.What should I do? Question 6 : What can Ido when the activity/Opportunity/Complaint reasons(Code,CodeGruppe,Katalogart)are not extracted? Question 7: What can I do if the deleted opportunities are not reflected in BW? Question 8: How do I activate the metadata? Question 9: I donot get any records for the delta upload of my attribute datasource(s).What is to be done? Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0 and various other BW status mean ? Question 11: How will I know which datasource to use? Solutions Question 1 : The Extraction from CRM to BW takes a very long time. What can be done? (Performance Issues) Suggestion 1: Please implement notes653645 (Collective note) and 639072(ParallelProcessing). The performance could be slow because of the wrong control parameters used for packaging. You can change the package size for the data extraction. Also note that changing the package size in the transaction SBIW would imply a change for all the extractors. Instead, you could follow the path in the bw system. Infopackage (scheduler)> Menu 'Scheduler' > 'DataS. default data transfer' > maintain the value as 1500 or 1000(This value is variable) The package size depends on the Resources available at the customer side(The no of parallel processes that could be assigned = 1.5 times the no of CPU's available approx.) Question 2 : On executing transaction RSA3 I get records but I find 0 records when I load data from BW request.(No Data Available) Suggestion 2: First check if there are any entries in the table CRMD_ORDER_INDEX.Only if there are entries in this table you can extract records. If this is not the case then,It is possible that the user does not have sufficient authorities for extraction ofthe relevant objects. Additionally, please review and implement the following notes 615670 161570 150315

    692195 - FAQ: Sales Analytics and CRM-BW data Extraction

    Version 5 Validity: 03.09.2013 - active Language English (Master)

    Released On 03.09.2013 13:30:53 Release Status Released for Customer Component BW-BCT-CRM-SAL BW only - Sales Analytics

    BW-BCT-CRM BW only - Customer Relationship Management

    BW-BCT-CRM-BE BW only - Connection CRM - BW

    CRM-ANA-EXT Extractors

    CRM-ANA-EXT-API Generic Functions: Data exchange CRM/BW

    CRM-BTX-ANA-BW BW Data Exchange

    Priority Recommendations / Additional Info Category FAQ

    Other Components

  • 618953 If you are in the release 4.0 then To do BW extraction with the user please see that the following authorization object exists(display mode is enough): CRM_ACT, CRM_OPP, CRM_LEAD, CRM_SAO, CRM_SEO, CRM_CO_SE, CRM_CO_SC CRM_CO_SA, CRM_CON_SE, CRM_CMP, CRM_ORD_OP, CRM_ORD_LP, CRM_ORD_PR CRM_ORD_OE, CRM_CO_PU, CRM_CO_PD, CRM_ORD_PO (all these objects are linked to transaction crmd_order). Question 3 : The Deltas for my data source are not extracted . What can I do? Suggestion 3: Please check the following. Please Check if the services have been generated in transaction GNRWB. If they are not active(not marked 'X' before their names) then activate the services following the steps here. Go to transaction GNRWB Select BUS_TRANS_MSG Select (on the right, the services) : BWA_DELTA3, BWA_FILL, BWA_queue Press Generate. Also checkfor the following: 1. The delta should have been initialized successfully. 2. Confirm that all Bdocs of type BUS_TRANS_MSG are processed with success in SMW01. 3. If there are queues in SMQ1 with erroneous status then activate these queues. In Transaction SMQ1 if there are Queues existing with names beginning with CRM_BWAn (n is number) then activate these queues in the same transaction. For any more issues in this, please check the notes 1892765 and 1483845. 4.a)If required activate the datasource. Go to transaction BWA5 > select the required datasource and activate. 4 b) The Delta may not be active ,activate the delta in BWA7 by selecting the name of the datsource and pressing the candle icon for 'activate delta'. 5. In BW system, Go to transaction RSA1 > modeling > infosources > select the infosource > right mouse click on the selected infosource > choose option replicate datasource.Activate the infosource. 6. Go to the scheduler for the infosource > select deltain the update>choose the option PSA only (in the Processing tab)> start immediately Check the entry in the RSA7 in the OLTP(CRM system) Question 4: How can I extract the fields, which are not provided in the standarddata source extraction . Suggestion 4: Follow the steps mentioned below. 1. Enhance Extract Structure with the required fields. (Create & include an append structure to the extract structure via transaction RSA6). 2.a) Release the fields of the appendfor usage. (To do this, double click on the Datasource and remove the flags in the column 'Hide Field' for all fields of Append.) 2.b)If the new fields cannot be seen in the extract structure of the transaction BWA1 then change the visibility of the required fields and save the datasource, and then activate it in RSA6. 3. Define your mappings in BADI (CRM_BWA_MFLOW) to fill these fields. Goto SPRO . Follow the path -> SAP Implementation guide ->Implementation with other mySAP components -> Data transfer to the Business Information Warehouse-> Settings for the application specific datasources (CRM)-> Settings for BW adapter-> Badi :BW adapter :Enhancement of datasources in messaging flow. 4. Replicate the new Datasource to BW. 5. Expand the Communication Structure in BW. 6. Maintain transfer Rules for the new Datasource. 7. Activate the trasfer rules and perform the upload. Question 5:I am unable to extractuser status correctly.What should I do? Suggestion 5 :Check the following notes 531875 616062 713458 700714 765281 Question 6 : What can Ido when the activity/Opportunity/Complaint reasons(Code,CodeGruppe,Katalogart)are not extracted. Suggestion 6 :Check the following notes 481686 516820 603609 617411 711146 Question 7:Deleted opportunities are not reflected in BW. Suggestion 7: Check the note 706327. Question 8: How do youactivate the metadata? Suggestion 8:CRM BW adapter meta data has to be activated first before it is available in the system. You can use Transaction BWA5 to copy the meta data for selected DataSources. You can reach the transaction via the IMG maintenance 'SAP Reference IMG -> Settings for SAP Business Information Warehouse -> Activate BW Adapter Meta Data'. For more information, see the documentation on the IMG activity 'Activate BW Adapter Meta Data'.(Note 432485) Question 9: I donot get any records for the delta upload of my attribute datasource(s).What is to be done? Suggestion 9: In case of attribute datasources, it is possible that the entry for the GUID is missing in the table SMOXAFLD. If , for example the datasource 0CRM_OPPT_ATTR is not giving deltas then you can follow the steps: 1)If Delta process is active for the attribute datasource e.g. 0CRM_OPPT_ATTR, then stop the delta process in the BW system 2) In the CRM system, Make the entry in the table SMOXAFLD for the datasource with the Key as

  • 0CRM_OPPT_ATTR GUID 3) Save the entry.Activate the datasource 4) Check that the above entry is replicated in smoxafld_s also after this. 5) Create a transport request manually for the following object. R3TR SMO4 0CRM_OPPT_ATTR Question 10: What do the status BWSTONESYS0 , BWSTONEUSS0,BWSTTECSYS0 and various other BW status mean ? Suggestion 10: The BW status are used to extract system and user defined status. The BW status are defined in the customization settings in SPRO. Check for-> Status Concept for BP/Product/CRM objects.Here goto-> Process user status You will find the documentation attached here for the user status. Going inside the transaction you will find the status groups USS0, ZIOP,ZMOP etc. The names of the various BW status are derived from this For ex. BW + ST+ One + USS0 gives the name of the field BWSTONEUSS0 or BWST + ONE + ZMOP = BWSTONEZMOP (Master opportunity values) (which means BWST + (status group name) + status object group name) Double clicking on any of the object groups will take you to the values that these status can have . For ex. BWSTONEUSS0 in your systemcan have values E001 ,E002,E003,E007 which will be shown in RSA3 as BW status values 1,2,3,7, respectively. Similarly we have Goto -> Process system status (in SPRO). Here you can get the values for the system status in exactly the same way as BWSTONESYS0(Lifecycle status) , BWSTTECSYS2 (Error) etc. In RSA3 you get the names as BW status, To know which corresponds to which status here,Goto the record list in RSA3 . Here goto Settings - Layout -Current . Right click -> Press Show technical field names . You will be able to see the BW status names and will be able to adjust the layout accordingly. Question 11: How will I know which datasource to use? Suggestion 11: To find out the which extractor extracts a particular document, get the BUS object type of that particular document and go to table smoxgsel to get a list of datasources which can be used.

    Validity

    This document is not restricted to a software component or software component version

    References

    This document refers to:

    SAP Notes

    This document is referenced by:

    SAP Notes (19)

    1437392 Enhancing CRM datasources- performance issues 765281 User status for opportunity items returns wrong values. 713458 CRM BW:Incorrect extraction of user status Opportunity Items 711146 CRM-BW data extraction: Complaints reasons are not extracted 706327 Deleted Opportunities are not extracted to BW 700714 Extraction of User Statues for Opportunity items 653645 Composite SAP Note about performance-related topics 639072 CRM/BW parallel proc. for extracting business transactions 618953 Authorization check activated in operational reporting 617411 BW, complaints, reasons are not extracted 616062 BW, user status is not extracted 615670 Authorization check in operational reporting 603609 BW extraction of complaints, reasons not filled 531875 User status is not copied into BW status 516820 BW extractn opportunity,reason for status,incorrect contents 481686 BW extraction complaint does not return reasons 432485 Activation of CRM BW adapter meta data in CRM 3.0 161570 User ALEREMOTE in the BW: Dialog user or system user? 150315 BW-Authorizations for Remote-User in BW and OLTP

    639072 CRM/BW parallel proc. for extracting business transactions 531875 User status is not copied into BW status 618953 Authorization check activated in operational reporting 617411 BW, complaints, reasons are not extracted 616062 BW, user status is not extracted 615670 Authorization check in operational reporting 603609 BW extraction of complaints, reasons not filled 1437392 Enhancing CRM datasources- performance issues 516820 BW extractn opportunity,reason for status,incorrect contents 765281 User status for opportunity items returns wrong values. 713458 CRM BW:Incorrect extraction of user status Opportunity Items 711146 CRM-BW data extraction: Complaints reasons are not extracted 706327 Deleted Opportunities are not extracted to BW

  • 653645 Composite SAP Note about performance-related topics 700714 Extraction of User Statues for Opportunity items 481686 BW extraction complaint does not return reasons 150315 BW-Authorizations for Remote-User in BW and OLTP 432485 Activation of CRM BW adapter meta data in CRM 3.0 161570 User ALEREMOTE in the BW: Dialog user or system user?