The updates don't pass from server to DOE

[Former Member]

Hello,

We are using Mobile 7.1. In our configuration we have an SAP ECC 5.0 server, a DOE middleware server and several mobile devices. When we perform some changes from the client side (mobile devices) the changes pass successfully to the server side. But when we perform the changes on the ECC server (server side) they don't pass to the client side. When we checked the tables on the DOE, we found that the changes didn't pass to the DOE server at all.

we also checked the BAPI wrappers - the GETLIST and GETDETAILS functions show the changes without any problem. What can be the possible reason for the problem?

Thanks in advance,

Sergey Kozyrev

[Former Member · Accepted solution]

Hi Sergey,

The changes you are referring to , is it change in data or change in metadata?

If it is change in data, meaning some more data has been created in R/3 which needs to be reflected in the middleware and client, then you should check the Data Object used for this data. Check the Backend Adapter for it. If Synchronization type mentioned out there is DOE TRIGGERED, then you will not get the data automatically in middleware even if it is added in R/3. You will have to manually trigger the delta load using the transaction SDOE_LOAD. If the Synchronization type is BACKEND TRIGGERED, then in R/3 BTE should be maitained, which will trigger events and updates all the data changes. In either case some action has to be performed to push the data.

Check if this helps.

Regards,

Priya

[Former Member]

Hi Sergey,

Since you have chosen BE TRIGGERED option, you need to either implement key push or instance push methods in Backend.

you would have given a Backend BO name while creating the BE adapter for the data object in DOE.

key Push can be implemented by calling function module SMMW_BE_CALL_DELTABO present in the DOE server by passing the Backend BO name and the keys.This implementation need to be done at Backend. sample code follows

Data : lt_notif like standard table of smmw_ber3keys,
       notif type smmw_ber3keys.

 notif-r3key = order-ORDER_ID.
 append notif to lt_notif.

CALL FUNCTION 'SMMW_BE_CALL_DELTABO'
IN background task
destination 'RFC_DEST'
  EXPORTING
    BEBO_NAME              = 'BEBO_NAME'
*   IV_GATEWAY_ID          =
*   IV_GATEWAY_ALIAS       =
  TABLES
    R3KEYS                 = lt_notif
*   ET_RETURN              =
          .

If you have opted for Instance Push , then invoke Instance Push function module in the DOE server that was specified in the adapter by passing complete instance

These Function modules needs to be invoked using RFC destination created in BE for DOE sever.

Once either of these are in-place, then with every update/delete/insert in BE, keys/instances will be pushed to DOE automatically.

Regards,

Liji

[Former Member]

Hello Priya,

In our case the Synchronization type is BACKEND TRIGGERED but and the object that we work on is PM Notification. So under "BO Object" field we wrote NOTIFICATION. When you wrote that n R/3 BTE should be maitained, what exactly did you mean? Do we need to perform any additional customization in R3 besides BAPI wrappers' definition?

Thanks in advance,

sergey Kozyrev

[Former Member]

Hi,

If you are pushing keys with proper BO name, then check for logs in monitoring portal. Go to logs and traces link in netweaver mobile portal. Choose backend integration search mode. Give your SWCV name and data object name and search. Check whether there are any logs for the push that you have done. If there are any then check for errors.

If you are not able to see any logs check whether you have enabled backend push job for this business object in SDOE_BG_JOB_MONITOR. If you could not see then instance was not pushed to middleware from backend at all.

Regards,

Dhana