Bapi wrapper- MODIFY Wrapper For SyncBo

Question

Modify Wrapper :ZGET_AM_P2P For SyncBO
I have read the requirement :
-replace entire item data with entries of table parameters
pls tell me the code will work or not if i put in syncBo
someone pls help me.....
FUNCTION ZGET_AM_P2P.
""Local interface:
*"  IMPORTING
*"     VALUE(V_ANLN) LIKE  ANLA-ANLN1 OPTIONAL
*"     VALUE(V_STORT) LIKE  ANLZ-STORT OPTIONAL
*"  EXPORTING
*"     VALUE(V_MSG) TYPE  STRING
  TABLES : anla, anlz, anlh.
  DATA : v_date LIKE sy-datum,
         var1 like  BALM-MSGV1,
         var2 like  BALM-MSGV2.
  refresh : bdcdata, messtab.
  clear : bdcdata, messtab, v_msg, v_date.
  SELECT SINGLE * FROM anla WHERE anln1 = v_anln
                              AND bukrs = '1000'.
  SELECT SINGLE * FROM anlz WHERE anln1 = v_anln
                              AND bukrs = '1000'.
  SELECT SINGLE * FROM anlh WHERE anln1 = v_anln
                              AND bukrs = '1000'.
  CONCATENATE   anla-aktiv6(02)  anla-aktiv4(02) anla-aktiv(04) INTO v_date.
  CALL FUNCTION 'ZBAPI_AM_P2P'
   EXPORTING
     V_ANLN          = ANLA-ANLN1
     V_STORT         = v_STORT
     V_TXT50         = ANLA-TXT50
     V_ANLHTXT       = ANLH-ANLHTXT
     V_KOSTL         = ANLZ-KOSTL
     V_WERKS         = ANLZ-WERKS
     V_DATE          = v_date
   IMPORTING
     V_MSG           = v_msg
ENDFUNCTION.
FUNCTION zbapi_am_p2p.
""Local interface:
*"  IMPORTING
*"     VALUE(V_ANLN) LIKE  ANLA-ANLN1 OPTIONAL
*"     VALUE(V_STORT) LIKE  ANLZ-STORT OPTIONAL
*"     VALUE(V_TXT50) LIKE  ANLA-TXT50 OPTIONAL
*"     VALUE(V_ANLHTXT) LIKE  ANLH-ANLHTXT OPTIONAL
*"     VALUE(V_KOSTL) LIKE  ANLZ-KOSTL OPTIONAL
*"     VALUE(V_WERKS) LIKE  ANLZ-WERKS OPTIONAL
*"     VALUE(V_DATE) LIKE  SY-DATUM OPTIONAL
*"  EXPORTING
*"     VALUE(V_MSG) TYPE  STRING
  DATA :  var1 LIKE  balm-msgv1,
          var2 LIKE  balm-msgv2.
  PERFORM open_group.
  PERFORM bdc_dynpro      USING 'SAPLAIST' '0100'.
  PERFORM bdc_field       USING 'BDC_OKCODE' '=MAST'.
  PERFORM bdc_field       USING 'ANLA-ANLN1' v_anln.
  PERFORM bdc_field       USING 'ANLA-ANLN2' '0'.
  PERFORM bdc_field       USING 'ANLA-BUKRS' '1000'.
  PERFORM bdc_dynpro      USING 'SAPLAIST' '1000'.
  PERFORM bdc_field       USING 'BDC_OKCODE' '=TAB02'.
  PERFORM bdc_field       USING 'ANLA-TXT50' v_txt50.
  PERFORM bdc_field       USING 'ANLH-ANLHTXT' v_anlhtxt.
  PERFORM bdc_field       USING 'ANLA-AKTIV' v_date.
  PERFORM bdc_dynpro      USING 'SAPLAIST' '1000'.
  PERFORM bdc_field       USING 'BDC_OKCODE' '=BUCH'.
  PERFORM bdc_field       USING 'ANLZ-KOSTL' v_kostl.
  PERFORM bdc_field       USING 'ANLZ-WERKS' v_werks.
  PERFORM bdc_field       USING 'ANLZ-STORT' v_stort.
  PERFORM bdc_dynpro      USING 'SAPLAIST' '3020'.
  PERFORM bdc_field       USING 'BDC_OKCODE' '=YES'.
  CALL TRANSACTION 'AS02' USING bdcdata MODE 'N'
                                        UPDATE 'S'
                                        MESSAGES INTO messtab.
  PERFORM close_group.
  READ TABLE messtab INDEX 1.
  MOVE messtab-msgv1 TO var1.
  MOVE messtab-msgv2 TO var2.
  CLEAR v_msg.
  CALL FUNCTION 'MESSAGE_PREPARE'
       EXPORTING
           language               = 'E'
            msg_id                 = messtab-msgid
            msg_no                 = messtab-msgnr
            msg_var1               = var1
            msg_var2               = var2
        MSG_VAR3               = ' '
        MSG_VAR4               = ' '
      IMPORTING
           msg_text               = v_msg
       EXCEPTIONS
            function_not_completed = 1
            message_not_found      = 2
            OTHERS                 = 3.
ENDFUNCTION.
Message was edited by:
        yzme yzme

Answer 1

Hi Saptak,
Good to see that you had gone through earlier posts & SAP notes.
Record not on device errors occurs when a mobile user tries to modify a record which currently doesn't belongs to him anymore. Since you have an S01 syncBO, the object he is trying to modify now is deleted from MI. ( This doesn't mean the object is deleted from backend. Basically the Getlist bapi is now not returning this object)
This occurs only if the sync mode is "async". There is nothing to be worried about. This is just an expected behaviour. If you feel the update is important and needs to be sent to the backend, set the parameter REPROCESS_ON_NO_DATA to 'X' and reprocess the worklist.
When you reprocess, the Getdetail bapi will be called and the user changes are merged to the latest backend data. No conflict check done and hence there is a chance of backend changes getting overwritten. If the particular record is only updated by mobile user, then there is nothing to worry..
Let me know if you need more clarifications...
Regards
Ajith