Problem in Middleware

Question

Hi Experts,
     I am doing one object in middleware replication of delivery plant from R/3 to CRM. As you know there is relationship for ship_to and default delivery plant in R/3 but this is not present in CRM. For solving that problem we have created relationship category  'ZPLANT' in CRM and replicate the delivery plants in CRM as BP. So we are able to create the relationship manually in CRM.
But our client wants delta load for replication means whenever default delivery plant enters in ship_to in R/3 then that should create relationship in CRM between ship_to and delivery plant with relationship category 'ZPLANT'.
To solve this, I have created New MBDOC and all other function module like mapping fm, validation fm etc. required for MW steps R/3 as well as CRM. To initiate the delta load, I have used user exit DE_EIOUT (process event) for running my download fm to create BAPIMTCS structure and call mBDOC.
Now problem for me is that this download is working perfectly when I am adding, changing or deleting delivery plant in ship_to.
But it is giving problem when delivery plant is being added while creation of ship_to. Means my BDOC runs before BUPA_MAIN creation of ship_to in CRM and show error 'BP (ship_to) does not exists in system'.
Please help me what should I do so that my BDOC will run after BUPA_MAIN.
Is there any functionality of delaying the BDOC for few seconds?
Though it is a very long story and I feel sorry for that. I will appreciate your effort for helping me
Regards,
Paramjit

Answer 1

Hi Michael,
The code that I am using in smoutil3 as follows
(  Zmbdoc_ddp is my bdoc structure and zddp_ext is extension part )
   DATA message TYPE zmbdoc_ddp000 VALUE IS INITIAL.
  FIELD-SYMBOLS <bdoc> TYPE zmbdoc_ddp000.
DDIC type part
  DATA message_ext TYPE zddp_ext VALUE IS INITIAL.
  FIELD-SYMBOLS <ddic> TYPE zddp_ext.
segment data
  DATA segment_line TYPE LINE OF zmbdoc_ddp000-zddp_root.
  DATA ext_line TYPE LINE OF zddp_ext-zddp_root.
  DATA transfer_structure TYPE transfer_structure_t.
  DATA lv_task TYPE c.
  DATA itab LIKE transfer_structure OCCURS 0 WITH HEADER LINE.
  DATA ls_zddp              TYPE zddp.
  DATA: lv_header        TYPE smw3_bdoc,
       lt_header        TYPE SMW3_FHD.
CODING -
CREATE REFERENCES
Create a reference for all
BDoc part, regardless if they are filled or not!
  CREATE DATA ref_message LIKE message.
  ASSIGN ref_message->* TO <bdoc>.
<bdoc> = message.
  CREATE DATA ref_message_ext LIKE message_ext.
  ASSIGN ref_message_ext->* TO <ddic>.
Moving all data container of bapmatics into mBDoc
  LOOP AT ti_bapimtcs WHERE tabname = 'ZDDP'.
fill classical mBDoc part
    MOVE ti_bapimtcs-data TO ls_zddp.
    MOVE ls_zddp-kunnr TO transfer_structure-p1.
    MOVE ls_zddp-vwerk_new TO transfer_structure-p2.
    MOVE ls_zddp-vwerk_old TO transfer_structure-p3.
Handle TASK value
    CASE e_bapicrmdh2-dwnloadtyp.
      WHEN 'I'.
        lv_task = 'I'.
      WHEN 'D'.
        lv_task = e_bapicrmdh2-delta_op.
    ENDCASE.
Fill the extension of the mBDoc
    ext_line-data-kunnr     = transfer_structure-p1.
    ext_line-data-vwerk_new = transfer_structure-p2.
    ext_line-data-vwerk_old = transfer_structure-p3.
    IF lv_task <> c_insert.
      ext_line-datax-kunnr = 'X'.
      ext_line-datax-vwerk_new = 'X'.
      ext_line-datax-vwerk_old = 'X'.
    ENDIF.
    ext_line-control-task = lv_task. " e_bapicrmdh2-delta_op.
    APPEND ext_line TO <ddic>-zddp_root.
  ENDLOOP.
  CALL METHOD cl_smw_mflow=>set_header_fields
    EXPORTING
      in_bdoc_type = 'ZMBDOC_DDP'
    IMPORTING
      out_header   = header.
Regards,
Paramjit