Skip to Content
Author's profile photo Narendra Vishwakarma

How to stop Particular Bdoc Type replication between CRM & ECC?

Requirement:

Bdoc Replication from CRM to ECC and vice versa should be stop for particular Bdoc Type. In this scenario BUPA_MAIN Bdoc type should not replicate between ECC and CRM system.

As-is-process:


Presently, there are no restrictions on Bdoc replication between both the system CRM & ECC. Thus, as stated above, replication of particular Bdoc need to be stopped. This requirement generally arise while set-up of new system, in my case we are setting up Quality system and until everything got set-up correctly (Like All the Transport Request import correctly) as Development system, nothing should be replicate between new ECC Quality system and CRM Quality system.

To-be-process:

In the new environment Bdoc replication should be stopped.

Solution:

To achieve this requirement there are set of steps provided in SPRO, by which we can stop replication of any Bdoc types. In this example I have taken Bdoc Type BUPA_MAIN.

Step 1 Go to SPRO =>

/wp-content/uploads/2015/03/1_656646.png

Step 2   Go to => Customer Relationship Management =>

                              CRM Middleware and Related Components =>

                                   Message Flow Setup=> Execute (F8) – BDoc Type Settings.

/wp-content/uploads/2015/03/2_656647.png

Step 3 Create New Entries.

/wp-content/uploads/2015/03/3_656648.png

Step 4-  maintain entry in below fields as mentioned below.

A.    Short Name text Box: give Bdoc name for that particular Adapter Object type for which you want to stop replication.

B.    Use XML: select Default option.

C.    Do Not Send: Make it check.

D.    Save the entries.

/wp-content/uploads/2015/03/4_656649.png

After Completion of all the above  steps the mentioned Bdoc Type replication would be stop. To start again the replication just delete the created entry.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Sanjay Parihar
      Sanjay Parihar

      Very detailed