my BDOCs in CRM are all waiting with yellow status

[Former Member]

I don't know why my BDOCs(transaction smw01) are all waiting with yellow status. Shouldn't they be automatically transfering data to my data source. If i manually process the BDOC then data goes to the datasource which can be seen via transaction RSA3. Help?

Message was edited by: Prakash Singh

[edwin_harpino]

hi Prakash,

i think bdocs should be something automatically,

never have bdocs problem, once transfer datasource rsa5,

activate in bwa5, (bwa7 if necessary), replicate to bw,

create infopackage for delta-init, and create another infopackge for delta and scheduled periodic.

the delta will go to delta queue (rsa7).

ask basis guy to check bdocs ?

hope this helps.

[Former Member]

I don't have problems in BW. It's the BDOCs that is sitting in CRM (SMW01). If i manually process the BDOCs then my infopackage loads the data without any problems in BW. If i don't then the infopackage doesn't find any records. In CRM the BDOCs are not populating the delta queue.

[edwin_harpino]

yes, i know you have no problem with bw

and the problem is in crm side.

when i said run transaction bwa5

and bwa7, it's in crm side. and i try to share you

the general steps we performed when extract crm data.

what datasource are you using ? make sure it's marked

in bwa5, if not so, you need to choose it and click

the light icon. and bwa7 also.

hope this helps.

[Former Member]

i already knew that bwa5 and bwa7 transaction are on CRM side. My datasource is activated. i am using 0CRM_SRV_PROCESS_H and 0CRM_SRV_PROCESS_I datasource.

[Former Member]

that doesn't solve my problem. The above notes is all about manually processing bdocs. i need something to setup automatic processing of bdocs.

[edwin_harpino]

hi Prakash,

again oss note 692195-FAQ: Sales Analytics and CRM-BW data Extraction ?

bwa5 and bwa7, delta is activated ?

and initialization performed in bw ?

626214 619122

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.

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'.

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,

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 ?

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

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 check for 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.

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 delta in 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 standard data 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 append for 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 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 extract user status correctly.What should I

do?

Suggestion 5 :Check the following notes

531875

616062

713458

700714

765281

Question 6 : What can I do 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 you activate 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 system can 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.