Time efforts can be posted to the first found WBS element set as ‘billing element’ (searching down-top, starting from the activity WBS). If the activity WBS and superior WBSs are not set as ‘billing element’, the time effort will be posted to the activity WBS.
| Table of Contents |
|---|
Time efforts can be posted as CATS entries. It is not possible to post time efforts as confirmations.
CATS
Activity type for time efforts posted as CATS entries can be determined from technician’s infotype 0315 or based on the used time task (the so-called technician’s time task, as opposed to service call time task).
Scenario with activity type from technician’s infotype 0315
Prerequisites
For this scenario, the following customizing is required in transaction /PACG/ECM_CTET - Time Effort Type:
Field ‘CATS active' enabled
Field ‘ActType PA0315’ enabled
Additionally, for the technician creating the time effort, infotype 0315 should be maintained in transaction PA30:
Example
Create a new time effort for a WBS activity on the FSM mobile app and approve it in Time and Material Journal.
An inbound time effort idoc can be found:
A new CATS entry, with reference to the activity WBS element, can be found for the technician in transaction CAT2:
Scenario with activity type from technician’s time task
Prerequisites
For this scenario, the following customizing is required in transaction /PACG/ECM_CTET - Time Effort Type:
Field ‘CATS active' enabled
Field ‘ActType PA0315’ disabled
Additionally, a time task for the technician should exist in SAP FSM. Use instructions from the following page: Time tasks - Time task for technician. They include:
Transaction /PACG/ECM_SCG - Service call general settings
Transaction /PACG/ECM_SOLAF - Subtasks - Filter:
Example
Create a new time effort for a WBS activity on the FSM mobile app. Make sure to select the technician’s time task. Approve it in Time and Material Journal.
An inbound time effort idoc can be found:
A new CATS entry, with reference to the activity WBS element, can be found for the technician in transaction CAT2:
Additional time effort customizing options
Field ‘SCC src TE’ in transaction /PACG/ECM_CTET
Source of sending cost center derived from service order had to be adjusted for WBS integration. For sending cost center set as ‘From service order operation/header’, request cost center from activity WBS will be used (if no value found, request cost center from service call WBS). If the customizing is set to ‘From service order header’, request cost center from service call WBS will be used. Other setting options do not differ from service order integration.
Field ‘RCC src TE’ in transaction /PACG/ECM_CTET
For receiving cost center set as ‘From service order operation/header’, responsible cost center from activity WBS will be used (if no value found, responsible cost center from service call WBS). If the customizing is set to ‘From service order header’, responsible cost center from service call WBS will be used. Other setting options do not differ from service order integration.
Transaction /PACG/ECM_SCBW2 - WBS (Service call) - Accounting Indicator
Transaction /PACG/ECM_SCBW2 - WBS (Service call) - Accounting Indicator has been adjusted to support WBS types:
See the original transaction: /PACG/ECM_SCBM2 - Acc. Indicator in Time Effort determ
Transaction /PACG/ECM_ANABW - WBS (Service call) - Attendance or Absence Type
Transaction /PACG/ECM_ANABW - WBS (Service call) - Attendance or Absence Type has been adjusted to support WBS types:
See the original transaction: /PACG/ECM_CANAB - Attendance or Absence Type