| Status | ||
|---|---|---|
|
The system copy guide includes information about the need to adjust checklist templates’ number ranges after system copy. If there are checklist templates in FSM that do not exist in SAP ECC/S4, checklist template’s 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, the administrator user can perform manual steps described on the following page: https://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/804093999/SAP+GUI#1.5.-Number-ranges-for-checklist-templates. If it was omitted, generic IDocs must be fixed manually by a developer by changing the status of the generic IDoc and editing the sap key.
...
/PACG/ECM_CLTTI - Checklist Template - Icons
/PACG/ECM_CLTTM - Checklist template mapping /PACG/ECM_CLTTP - Checklist Template - Position
/PACG/ECM_CLTTPT - Checklist Template - Position (Description
/PACG/ECM_CLTTS - Checklist Template - Series
...
If the checkbox “Adjust NR status using the highest new key” is enabled, the highest “new SAPKEY” value calculated above (out of all the processed idocs) will overwrite number range status for number range /PACG/CLTT, but only if it’s bigger than the current value found there.
Authorizations
The transaction requires authorization object /PACG/E016 - Unblock checklist templates