First- and second-level obligations of FSM Partners

Partners are contractually obliged to provide first and second level support services. In case our support team has to perform the analysis described below, these efforts will be chargeable.

Please note that the following analysis must be performed BEFORE opening a ticket to avoid billable efforts.

Configuration issues and consulting services are always billable.

1. Superuser settings available in the Admin portal

1.1 User Group
e.g.

• Check if the user is active, a plannable resource
• Change user's password
• Change user's user group

1.2 Group Permission
e.g.

• Check the Permission read, create, update, delete

1.3 Company Settings
e.g.

• Mapping of the Service Call

1.4 Business Rules
e.g.

• Check execution logs
• Validate BR with failed Object

1.5 Screen Configurations
e.g.

• Check if they are enabled

1.6 Query API
e.g.

• Check the ERP Error table
• Check the objects in question (Service Call, Activity, ServiceAssignment): status? Syncstatus?
• Check the Person / UnifiedPerson

1.7 ERP Connector
e.g.

• Check the connector version

1.8 Audit Logs
e.g.

• Check the history on an Object

 

2. Troubleshooting Mobile Apps

2.1 Delete Database on Mobile App

2.2 Managing Sync Performance

 

3. Available shell settings

3.1 Planning board
e.g.

• Block diagnosis tool

3.2 System Monitoring
e.g.

• Check if any object is blocked
• Check the error message

 

4. SAP B1 & SAP FSM Cloud Connector

Check the following files:

• SAP FSM Cloud Connector logs
• COR_CLOUD_SEND/RECEIVED/CONFIRMED tables
• SWA_CT_CLOUD_ERR

 

5. How to open a ticket for FSM

Before opening a ticket, make sure that the issue has been properly tested and/or reproduced.

5.1 Include a detailed issue description

1. System details:
   • Cloud Account name:
   • Database/Company name:
   • Affected user(s):
   • *Mobile app version and Operating System:
   • *SAP FSM Cloud Connector Version:
   • *ERP version and PL:
2. Issue description:
   • Analysis performed so far:
   • *Examples (service call/activity/sales order -number):
   • *Include attachments (screenshots, connector logs, short video).
3. Is this behavior reproducible in both test and productive environment?
   • Steps of reproduction:
   • Expected behavior:

(*) If applicable