...
Within the FSM App working times are booked on the Worktimetask object and then transferred to SAP. With this customizing you can define the different Worktimetasks which can be selected within the App and with which attributes they are posted either in CATS (see activation in /PACG/ECM_TIMEF – Time Effort ) or as confirmation against service order defined in this transaction.
Each Company has its own Work Time Task Definitions
...
Work Time Task Code | Unique ID of the Work Time Task | ||
|---|---|---|---|
Work Time Task Name | Task name which will be shown in the App. | ||
Activity type | The activity type as used in the SAP for posting CATS / confirmation. Note that activity type determined from settings /PACG/ECM_CTET - Time Effort Type – precisely field ActType PA0315 has higher priority.  | ||
Activity Task Type (TASKTYPE) | This field will be filled in CATS booking if it exists in BAPICATS1. Also CATSDB fields EXTSYSTEM and EXTAPPLICATION will be filled. Fields TASKLEVEL and TASKCOMPONENT should be filled by a customer-specific user exit.  
| ||
No book | The field is only used in classes performing the confirmation of the Service Order. If the "no book" field is checked, no confirmation will be created for the work time task and a message "Work time will be not booked in SAP" will be displayed. | ||
SalesActiveType | Sales Activity type for Sales support: Uniquely identifies the type of sales activity (for example, whether the sales activity is a sales call, a telephone call, and so on). | ||
A/ATT | Attendance- or Absence Type for posting in CATS | ||
Time posting | Selection options: from/to, absolute or fixed value | ||
Posting value | In case of fixed value | ||
Unit of measure | In case of fixed value | ||
Past option | Options for showing days backwards in window | ||
Future option | Options for showing days forward in window | ||
Inbound/Outbound | In- or outbound selectable |
...