Reports for Scheduling Background
Jobs 
Use
You can schedule the following reports using background jobs on the server:
Asynchronous Processing of Inbound Data Containers:
Report Name |
WAF_MW_MAPPING |
Purpose |
SAP MI offers synchronous and asynchronous processing of data containers transferred from the mobile device to the server. The type of processing depends on the type of data container defined by the application developer. This report processes the data containers that were defined for asynchronous processing. |
Recommended Frequency of Repetition |
Daily or more frequently to ensure that data coming from a mobile device is processed as soon as possible. In test phases you should increase the frequency of repetition, for example, to every two minutes. |
Synchronization of Role Contents with the Contents of the Deployment Console:
Report Name |
WAF_DEPLOYMENT_FROM_ROLES |
Purpose |
The report extracts the applications assigned to the users of a role (in transaction PFCG). The report then transfers the extracted applications to the tables used by the SAP MI Web Console. If you stored RFC destinations in the table MEMAPPDEST, the report also evaluates the roles edited in the associated back-end systems. In this case, the applications that were assigned to a user in the back-end system are transferred to the tables used by the SAP MI Web Console. If you created a user group with the name MESYNC (see Creating a User Group for Synchronization), the users determined in the back end are automatically generated on the SAP Web AS and assigned to this user group. These users initially do not have any authorizations and must be assigned authorizations. This is done by assigning a suitable role (see Role Editing for Mobile Applications). To enable the data to be transferred, you require the authorization S_TABU_RFC in the back end. |
Recommended Frequency of Repetition |
Daily or depending on how often the contents of the roles are changed. In test phases you should start the report manually after a role modification or, for example, schedule it to be run on an hourly basis. |
Activities
...
1. Schedule the above reports in background jobs (see Scheduling Background Jobs).
Start transaction SE38 to execute reports manually.
To schedule background jobs you need authorization for the back-end system. If this is not the case, the background jobs cannot be executed correctly. Make sure that you have all the necessary authorizations. For more information, see the corresponding R/3 documentation.