...
| Info |
|---|
Learn more about time tasks: Time efforts If subtasks are not sent to FSM, check if KP26 data is maintained for the activity types, with the technician’s work center’s cost center. |
Type |
Enter order type if order type-dependent filtering is needed for activity types. Entries with order type will be searched for first. If there are no entries with order type, the ones without order type will be used. The filtering is relevant for the following time task generation approach: Time tasks - standard approach. If activity types are determined for time task for technicians (Time tasks - Time task for technician), only entries with blank order type will be selected.
| ||||||
|---|---|---|---|---|---|---|---|
Activity type |
Time tasks will be generated for activity types included in the range |
. Notice how in the example below, two time tasks are generated, each for one activity type in the range (101-102): https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/109969519/Time+tasks+-+Time+task+for+technician#Example |
| Note |
|---|
The 'Between' operator performs comparisons of character-based fields lexically. This can cause issues when comparing strings that represent numerical values, as SAP evaluates each character in the string from left to right. To prevent potential problems, ensure that configuration values have consistent lengths for accurate lexical comparison. For example, pad numeric values with leading zeros to standardize their length:  |