Versions Compared

Old Version 10

changes.mady.by.user proaxia

Saved on

compared with

New Version Current

changes.mady.by.user Alicja

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

  •        Update the FSM account and company details. The company name should be the same while created in the cloud. Transaction /PACG/ECM_CACC

...

  •       Path to maintain the Warehouse /PACG/ECM_WRHOUSEWRHSE

...

  •        If warehouse is missed, it is necessary to make new entry:

...

1.5. Number ranges

Before system copy, note all number range statuses on the test system for number ranges starting with /PACG* (use transaction SNRO, table NRIV or FSM Cloud Connector cockpit).

...

After copy, these statuses must be re-entered on the system, to avoid using the same SAP key in FSM twice. Otherwise, outbound idocs will end in status 40 and ‘ID mapping mismatch error’.

If the statuses were not noted before copy, after system copy increase the number ranges by a value reasonable for a given object type (for instance by 1000 for checklist templates, 10000 for checklist instances). This should fix the issue for all upcoming objects, the ones already received require update of the key in the dedicated tables and manual update in the idoc - this should not be performed without proaxia’s support.

Expand
titleLearn more about number ranges for checklist templates

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:/

...

Image Modified

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.

    Image Modified

    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://proaxia-prod-doc.atlassian.net/wiki/spaces/PFCC/pages/1869840400.

Info

Next steps: Configurations of Message Broker and FSM Cloud Company available here Message Broker and FSM Cloud Company Configuration