Adding a New Push Scenario

In order to create a new push scenario, the following need to be defined:

  • Source attributes
  • Distribution settings
  • Subscriber list
  1. Generate the MDO class handler for the work order push:
    1. Create a new class interface by inheriting all the properties from the base class /SYCLO/CL_CORE_DO_HANDLER_BASE.
    2. Activate the push by redefining the method CHECK_PUSH_SUPPORTED to determine whether the push service is supported by this handler.
    3. Redefine the method DETERMINE_PUSH_RECIPIENTS to identify valid users for the emergency work order push.
    4. Based on the work order assignment type, determine valid partner information and obtain the recipients from the middleware user registry table /<namespace>/MDW00.
    5. Redefine the method BUILD_PUSH_DATA to prepare user-dependent data to be pushed to the recipients. Each recipient will have a separate set of data collection images (push instance) and moved to the outbound queue.
    6. Redefine the method GET_DATA_FILTER_LIST to enable the data filter function for the class handler.
    7. List the filters supported by this class handler method along with the table name and filter name and pass it to the output table ET_DATA_FILTERS.
  2. Redefine the GET method to enable the fetch process for the class handler:
    1. Convert the RFC parameter list into OO parameter format.
    2. Build filter rules from the data object filter service and BAPI input parameters.
    3. Get the outbound message queue data from the push registry cache tables for the MDW user GUID range supplied through the BAPI parameter interface.
    4. Build the output data in OO parameter format.
    5. Cache the exceptions, if any, to the output return table.
    6. In the Agentry SAP Framework Configuration portal, navigate to the Mobile Data Object panel and assign the GET class handler to the appropriate mobile data object.
  3. Create the BAPI wrapper for the push work order fetch (GET):
    1. Create a new RFC.
    2. Assign the input parameter IS_BAPI_INPUT Type: /SYCLO/CORE_BAPI_INPUT_STR, which is the Syclo BAPI wrapper standard input setting. This structure contains the mobile object data such as the mobile user name, device ID, timestamp from the mobile, mobile data object ID, staging information, session and user GUIDs, etc.
    3. Assign the export parameter ES_BAPI_OUTPUT Type: /SYCLO/CORE_BAPI_OUTPUT_STR, which is the Syclo BAPI wrapper standard output structure. This structure contains the timestamp from SAP to the mobile device, package information, etc.
    4. Assign the appropriate tables parameters. This tab contains all the filter ranges and output data structures.
  4. Implement the exchange process for the work order push:
    1. Create a new configuration entry for the exchange process that is utilizing the push.
    2. Enable the push settings and additional filter conditions relevant to the push instance.
    3. Configure the exchange push settings to identify whether the push is active or not, as well as additional filter criteria used to maintain push conditions.
Parent topic: Working with Push Scenarios