General purpose | Define Work Time tasks for Work Time reporting in FSM and customize how Work Time reported with a given task in FSM should be stored in SAP ECC/S4.
From FSM perspective, Work Time and Absences are the same object, therefore this transaction also defines the Absence Types relevant for FSM, when creating a reservation on the planning board. See also: Differences between Reservations and Absences | ||||
|---|---|---|---|---|---|
Sending transaction (?) | https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/38174833
| ||||
Object assignment (?) | Object WORKTIMETASK must be added to https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31952609 for a given company |
Table of contents
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
Work Time Task Definition
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 https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137696 ) or as confirmation against service order defined in this transaction.
Each Company has its own Work Time Task Definitions
In the Work Time Task Definitions you can define:
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.  | ||||
FSM Activity Type | If entered, the reported work time will be posted with reference to the technician’s on-going activities' order(s). The orders relevant for CATS/confirmation posting are retrieved for each activity found based on the following criteria:
In case multiple activities are retrieved and they belong to more than 1 order, the time posting will be split equally - each posting (with a different time slot) will have reference to another order. If orders are retrieved, the ones from tab ‘Receiver order/WBS element’ are not considered. | ||||
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 |
| ||||
Att/Absence Type | Attendance- or Absence Type for posting in CATS | ||||
CATS Act. Type (previously Task Type) | 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.
| ||||
Time posting | Determine how start/end datetime should be calculated for time confirmation/CATS. Selection options:
| ||||
Posting value | Fixed work value for time confirmation. Used when ‘Fixed value’ is set in field ‘Time posting' | ||||
Unit of measure | Fixed work unit for time confirmation. Used when ‘Fixed value’ is set in field ‘Time posting' | ||||
Past option | Options for showing days backwards in window | ||||
Future option | Options for showing days forward in window | ||||
Inbound/Outbound | In- or outbound selectable | ||||
Color
| Absence types can be sent to FSM with the color parameter, specified in SAP ECC/S4. Please note that FSM allows usage of colors in the HEX format, e.g. #6e6858 or #17bd8b. To ensure that only the relevant colors are sent, users must select one of the 20 predefined colors. Use the ‘Color’ field’s search help to quickly select a color code.  ExampleIn transaction /PACG/ECM_VWRKTC - Work Time Task Definition, enter a color for a given work time task code (absence type).  Send the worktime task type to FSM with transaction /PACG/ECM_WRKTTSND - Work Time Task. 
Notice that the color property can be found in the outbound idoc. 
Navigate to FSM Settings and Configuration, tab ‘Planning and Dispatching’ -> ‘Time slot types’. Notice that the absence type’s color reflects the customizing in SAP ECC/S4. 
Create an absence on the Planning and Dispatching Board. The reservation is of the selected color.   |
Continue learning with:
| Table of Contents |
|---|
Time frames
| Note |
|---|
When maintaining entries here, please keep in mind the following:
|
Per Work Time Task Definition Time Frames can be assigned per day of the week, start and end time to identify different activity type or Attendance -/ Absence type. An option enables worktime to be posted with an activity type depending on a schedule and already posted time. E.g.: Mo-Fr. first 8h 100%, over 8h to 10h 150%, over 10h 200%; Saturday first 4h 150%, then 200%; Sunday and holiday 200%, day change since 0:00h
Source activity type | Activity type assigned to the work time task in node ‘Work time task definition’ or optionally in the reporting technician’s infotype 0315.
| ||||
|---|---|---|---|---|---|
DuratSOpt | The dependency for posting the surcharges for the worktime posting is set by either selecting person or order. Leaving the field empty will not activate the dependency. | ||||
Actual start/finish | While trying to create a new time frame for a given work time task in /PACG/ECM_VWRKTC - Work Time Task Definition, the user is obliged to fill the actual start and actual finish time fields. If the fields are left empty, an error message is displayed.  |
| Status | ||
|---|---|---|
|
Use the button ‘Consistency check’ to verify if your split customizing is correct.
The consistency checks will verify the following:
the entire day (24h) is covered by ‘Actual start time’ and ‘Actual finish’ dates (no gaps left)
Actual start/finish does not overlap with other time slot entries for the same key
For each entry where “duration to” is not initial (00:00:00), any non-initial actual finish is entered
Duration time fits between start and end time.
All Activity Types provided in Time Confirmation Split was maintained accordingly in https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/37137814
Receiver order/WBS element
Work times can be posted on a collective service order if the order is entered in this customizing and CATS is disabled in transaction /PACG/ECM_TIMEF – Time Effort. If CATS is active, the order or WBS element [available since Service Pack 5 for add-on 200] entered in this customizing will be used as the receiver order/receiver WBS element in the CATS entries.
| Info |
|---|
Please note that if both an order and WBS element are filled in one entry, then the order will be used. Maintain either an order or a WBS element in one entry. |
An example resulting CATS entry, with the WBS as WBS receiver:
An example resulting CATS entry with a service order as the order receiver:
An example resulting confirmation if CATS is disabled:
Posting to internal orders
| Status | ||
|---|---|---|
|
Worktime entries can be posted as direct activity allocations, with an internal order as the receiver order. Other properties such as sending/receiver cost center are determined the same way (using the same customizing transactions) as for CATS/confirmations posted to service orders.
Selected customizing fields considered
Transaction, field | Document property |
/PACG/ECM_CTET, 'Time in H' | Total quantity |
/PACG/ECM_CTET, ‘Fill send cctr’, ‘Fill rec cctr’, ‘Send. CostCtr src WT’, ‘Rec. CostCtr src WT’ | Sending/Receiver cost center |
Preconditions
In transaction /PACG/ECM_VWRKTC - Work Time Task Definition, tab ‘Receiver order/WBS element’ an internal order is added
In transaction /PACG/ECM_CTET posting to CATS is disabled
Limitations
Worktime remarks are posted as header doc. text and item text but the text will be cut to 50 characters (system limitation).
Please note that it is currently not possible to post CATS with reference to internal orders, therefore the field ‘CATS active’ in transaction /PACG/ECM_CTET must be disabled, or the customized receiver order should not be internal.
Worktime Out: CATS status to IDOC Action
Define which CATS statuses are relevant for work time transfer. Work times with statuses not maintained will not be transferred (neither automatically after changes in CATS, nor with the sending transaction).
Additionally, the transaction types of outbound idocs can be defined: change or delete (the object will be deleted from SAP FSM).
Example of automatic transfer of a work time object after changes of status in CATS
The customizing can be tested using transaction CATS_APPR_LITE - Approve Working Times. Reset approval of a CATS entry:
Observe that an outbound work time idoc is generated. Based on the customizing, its transaction type is 'D':
Make sure to check the following customizing beforehand:
· A WORKTIME object entry should be maintained for a given company in transaction /PACG/ECM_PAAS - Personnel Area assignments.
· Work time tasks should be maintained for relevant attendance/absence types and set as ‘Outbound’ in transaction /PACG/ECM_VWRKTC - Work Time Task Definition.