Creating Checklists in SAP

In the typical scenario the checklists are created in the Cloud and sent back to SAP. In the SAP they can be mainly read, some additional activities could be performed as well once the checklist is created in SAP.
However, the opposite scenario is possible as well:

1. The checklist is created in SAP.

2. The checklist is sent to the Cloud.

3. The checklist appears on the user's screen (in the FSM Client).

4. The user fills some data and closes the checklist.

5. The checklist is sent to the SAP back.

6. It is recognized in SAP, that this checklist already exists in SAP: instead of creation, the checklist is updated.

There is no customizing supporting creation of the checklists in SAP: it is assumed that the checklist is created based on some transactional data of SAP (sales order, delivery, inventory, purchase order etc), thereby a custom logic in ABAP needs always to be implemented anyway. Thereby, instead of customizing tables, the API (classes / methods) is provided with E4C, which could be used in the custom programs at the customer side (not in /PACG namespace provided by proaxia, but in Z or Y namespace, created in the scope of E4C custom implementation). The logic of these programs depends on the customer requirements, which are different in every case. Thereby the provision of one or even several programs with the E4C itself is not possible.

The typical approach should be:

1. Create a checklist template at the customer side.

2. Write a custom program (not in /PACG namespace, but in in the Z or Y namespace) creating the checklist instances. These checklist instances will refer to the checklist template. You always write the program creating the checklist instance for the given checklist template.