„Act. Type as TT" unchecked example with E4C activity: In the case of a service order created from backend SAP ERP, there will be a first sending message type /PACG/ECM_SERVICECALL_TASK to FSM upon service order release (other than other message types which is not described here). 
The idoc data in the segment shown here in the example (idoc 917679) will not be the same format if you have set the checkbox for „Act. Type as TT". See example further below.
This first record is stored in DTO TimeTask in FSM with object.objectType = SERVICECALL. This type of record will never appear in the mobile FSM app during creation of effort.
Once the assigment of the activity to the technician is released from FSM workforce management, FSM will send an activity in idoc which will in turn updates the operation level person no.
Once the service order in the backend SAP ERP backend is updated, this will trigger the sending of message type /PACG/ECM_SERVICECALL_TASK back to FSM. Now, there will be two(2) records of object.objectType = SERVICECALL and PERSON. Only the record with object.objectType = PERSON will appear in the mobile FSM app. See further below in „Act. Type as TT" checked example with E4C activity.
„Act. Type as TT" checked example with E4C activity: In the case of a service order created from backend SAP ERP
When a service order is created from backend SAP ERP and released, no message type /PACG/ECM_SERVICECALL_TASK will be sent initially except for service call related message type that is sent to FSM (not described here). Once the service order is released to the technician from FSM and updated in the service order in backend, we see 4 service call task sending as below.
As shown below, out of the four records, only two(2) are shown in the mobile FSM app as this corresponds to the object.objectType = PERSON in FSM. Noticed that there are 4 records (4 idocs – see previous page) required in FSM from SAP ERP backend (one for SERVICECALL and second for PERSON for each activity type), in this example, we have in /pacg/ecm_solaf for the company ID, we have defined that it is to include activity type 101 to 102 (shown directly below here).
In the mobile FSM app, we see two(2) entries for the task it can select (based on object.objectType = PERSON) and the screen next to it shows the API query on the data that is stored in FSM DTO TimeTask.
Note: If you see the below example with list of task that doesn't belong to the service order/call, then please check the DTO TimeTask content for your service call/order and outbound message type /PACG/ECM_SERVICECALL_TASK from SAP ERP to FSM. This can happen if the technician is not registered for the workcenter it belongs to in SAP ERP (see tcode IR03).