Configuring message flow in CRM MW/Queue finder/

Configuring message flow in CRM MW

 

§Next the flow tables have to be maintained-tables, SMW3BDOCIF & SMW3FDCUST

§Standard flow control table SMW3FDSTD is maintained by SAP already & should not be changed

§Maintain table SMW3BDOCIF with separate entries for

-Mbdoc type-validation module-mobile bridge module

-Sbdoc type-validation module

§

§Activate the mobile bridge in table SMW3FDCUST

§Maintain the table SMW3FDCUST with following entries

-Mbdoc Flow context entries (mbdoc notification additional calls, mbdoc notification multiple additional calls , mbdoc intial load additional calls )

-The additional flow contexts MOA, MOB, MOC (above) are added after the MO1 (notification), MO2(notification multiple), MO3 (intial load) calls respectively

-Maintain the mobile bridge function module created earlier in the above entries

-Mark the active flag (mobile bridge)

§Check transaction SM08FD for the flow services of the mbdoc

-The mobile bridge function module is called at the end of the standard function module calls(maintained in table SMW3FDSTD )

-

  

 

 

Queue finder

 

§In an actual scenario CRM MW maintains the queue finder so that the flow control framework uses qRFC queues to enable asynchronous outbound processing of the mBDoc messages. This is to improve response times for dialog users

§The queue finder writes some of the update tasks to queues which are processed asynchronously

§The queue names for a business object can be configured in table CRMQNAMES

-Eg: Usually queue name is on an instance level for business object (1 queue per object instance), but several instances can share the same queue because queue names are determined using a hash algorithm (prefix + first/last n characters of the business partner number).

-

§To make this example simpler the queue determination can be  excluded by setting of the parameter __synchmode when calling CL_SMW_MFLOW- PROCESS_OUTBOUND 

 

Table CRMQNAMES

 

 

 

§Final steps would be to setup a mobile client & subscribe it to the replication object (sbdoc) using replication rules in admin console

§This will complete the end to end middleware flow

§If in this process R/3 had to be included in the data exchange then suitable download objects should be created in the CRM adapter, & an application similar to R/3 plug in has to be created for this business object