Problem with mBDoc

[Former Member]

Hello.

We have issues in integration of SAP SM and SAP BI in our company.

The SAP CRM components are the base for SAP SM in part of orders. The extractors have CRM prefix in their names, example 0CRM_SRV_PROCESS_H.

We have explored a lot of documentation about CRM and BI integration, but couldnu2019t find a solution to the issues: mBDocs doesnu2019t work correctly. With any modification of crm orders an mBDoc (class BUS_TRANS_MSG) should be created, which is not happening in our system.

Can you suggest any solution to this issue? What should we modify in CRM to make mBDoc work correctly.

Edited by: Dmitry Kryuchkov on Oct 31, 2011 8:57 AM

[rohit_sharma2 · Accepted solution]

Hello,

You need to make sure that the Total generation (txn. SMOGTOTAL) in CRM was performed.Also check if the subscriptions have been assigned properly in CRM (Txn. SMOEAC) so that the data flows from CRM to external connected systems.

[Former Member · Accepted solution]

Thank you for your answer.

I repeat the total generation. There are some errors in generation status (txn. GENSTATUS). The names of false generation objects are

ATTACHMNT_WR

CAMPAIGN_WRITE

CRITERIA

CUST_KPIPRSET

The subscriptions in txn.SMOEAC are empty. What subcription are needed for external bi system? May it be important, that SAP CRM ( SM) and SAP BI are installed jointly on one server.

[rohit_sharma2 · Accepted solution]

You'd first need to resolve all the errors that appear in GENSTATUS.

Then run the transactions MW_MODE and MW_CHECK to verify if middleeware is operational.

[Former Member · Accepted solution]

I did't find the solution for error "Memo conversion is not complete" in sdn community.

Do you have any idea how to resolve the errors?

[rohit_sharma2 · Accepted solution]

Generally Complete generation solves the errors of memo conversion. But you can run the report CMW_LOB_MIGRATION as mentioned in the note 1080862.Once the report is run, try regenerating the errors in transaction GENSTATUS. This should resolve the issue.

[Former Member · Accepted solution]

Thank you for your answer.

Previous errors has been removed. But we have one error yet:

Generation Object Name: SADCRC CG

Generator group: REPLI

Text:

/1CRMGC/CGSADCRC_DTC:The data object "<FS_DTC>" does not have a component called "GROUPNO".

Could you tell us what need to do with like this error?

Edited by: Dmitry Kryuchkov on Nov 7, 2011 2:15 PM

[rohit_sharma2 · Accepted solution]

Hello Dmitry,

This error occurs because the generated data collector table /1CRMGC/CGDTC001 did not contain a field with name GROUPNO. Normally such field will be generated as part of the table structure whenever there are more than one segments in the BDoc at root level. This can only be the case for BULK repl. objects.

To fix this issue : In transaction SE11, delete the structure /1CRMGC/CGDTC001 and from transaction GNRWB generate the data collector table again by selecting the generator group as DCSRV: data collection service and the generator as DATA_COLLECTOR_TABLE and select all the objects on the Left side.

Let me know if that fixes your problem.

Regards,

Rohit

[Former Member · Accepted solution]

We had executed recommended steps.

All repository object with the DATA_COLLECTOR_TABLE generator have been generated succesfully. But the error still.

May be I create manually this field (GROUPNO) in /1CRMGC/CGDTC001?

[rohit_sharma2 · Accepted solution]

You may try that. But this is a generated structure so may not allow changes. Anyway let me know

[Former Member · Accepted solution]

We have solved the problem.

Basic our mistake is in the bdoc type settings. Following the some article about the crm middleware, in transaction smw3_00 we created the line with short name: "BUS_TRANS_MSG" and checked combo box "Do Not Send". After I unchecked the combo box, bdoc have started work.

Main our task is the set up delta queue for bw. After business content activation and delta initialisation from bw (special infopackage) queue didn't work.

We had bdocs (BUS_TRANS_MESSAGE) with state 'Written to qRFC Queue (intermediate state)' in transaction SMW01. For set up bw delta queue it need to change the bdoc to "Confirmed fully processed" state.

I have performed next steps:

Checked cdb site in SMOEAC. (If cdb site no exist, enable data synchroniztion in CMWC_SMW).

Enabled message processing in MW_MODE. (Even through enabled).

Repeated the CSA* queue registration and scheduler activation in SMQR.

Started the initial load (in R3AS) with bus_trans_msg as load object, crm as sender and cdb as recevier.