Ansicht
Dokumentation

RTST_PSWT_REASNRJ - Map Task Categories to Reason Codes

CL_GUI_FRONTEND_SERVICES - Frontend Services   ABAP Short Reference  
This documentation is copyright by SAP AG.

You use this Customizing activity to link task categories to defined reason codes that are attached to each task item in a task category that a store associate processes, whether they confirm or reject an item. This is relevant for manually-created tasks.

You can set a default reason code to attach to task items that store associates have confirmed. This identifies the completed item as having been processed through the app without any exception. The default code is automatically attached to the item without any further intervention required by the store associate when they choose the 'Confirm' button in the app.

For any task item that the store associate rejects, they must provide a reason to explain why the task item could not be processed while they were performing the task. These reason codes are displayed in a pop-up dialog when they choose the 'Reject'button in the app if more than one reason code is defined. When only one reason is defined it is applied by default.

For optimal results, define at least two reasons for each category as follows:

• Mark one reason as a default that the system will automatically assign to items that store associates confirm.

Do not set more than one reason as the default in the same category or the system will randomly assign any reason to the confirmed item.

• Provide a second, unmarked reason for the system to automatically assign to items that store associates reject.

You can define additional reasons if you would like to know specific reasons why items were rejected. When several reasons are defined, store associates will get a selection list from which to choose the reason that best describes why they rejected an item.

If no reasons are defined for either the confirmation or rejection of items in a category, no reason will be stored in the database along with the processed item and no analytical insights into operational trends in the store will be collected.

You can also define the sort order in which the reasons codes are displayed in the UI for each task.

You must have already defined task categories and their related texts in the following Customizing activities:

• Define Main Settings for Task List Categories

• Maintain Text for Task List Categories

• Define Reason Codes for Tasks That Cannot Be Carried Out

• Maintain Text For Reasons Why Tasks Cannot Be Carried Out

CPI1466 during Backup   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

Length: 3034 Date: 20240523 Time: 193805     sap01-206 ( 63 ms )