Page Comparison

If there are checklist templates in FSM that do not exist in SAP ECC/S4, checklist template number range must be changed. E.g. when a production system is copied, the related FSM company may already have multiple checklists created and each of them is mapped with an SAP id. If a new checklist template version is created, a generic idoc may end up with status 40 because of a failed attempt to map the new FSM id with an SAP id previously mapped with another FSM id. To avoid the consumption of already used IDs, navigate to transaction SNRO and increase the NR status field for number range /PACG/CLTT.

Determine the relevant NR Status value in one of the following ways:

• If external IDs are enabled on your system (field External Id in transaction https:/PACG/ECM_COMP - Company definition/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/31953211), navigate to query api in the admin module for your FSM company, select ChecklistTemplate objects by externalId in the descending order and find the last used SAP template ID, like below:

The new NR status in SNRO should be higher than the ID above.

• Reach out to SAP support to learn about the latest used SAP code for checklist template (based on internal mapping table between SAP IDs and FSM IDs)

• Assess how many checklist template objects have been created in the FSM company. Check in table NRIV the last used checklist template id.

  

  Enter a significantly higher number in the NR status field in SNRO, e.g. +100 or +1000.

To unblock a failed checklist template version (generic idoc with status 40), please contact the FSM Cloud Connector support team. This requires changing the status of the generic idoc and editing the sap key which should be closely assisted by a technical consultant. It can also be corrected automatically by using https:/PACG/ECM_FIX_CT_GEN - Unblock checklist templates/proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1869840400.