SAP Knowledge Base Article - Public

3680689 - Copied Situation Type cannot be added to the 'Export Software Collection' app

Symptom

  • Copied situation types, including those based on the standard template FIN_GRIRPROCESSORCHANGED, cannot be added to the 'Export Software Collection' app when utilizing the 'Export Software Collection WE/RE Situation' function. 
  • These copied situation types are not visible in the "Add Items" list within the application. 

Environment

SAP S/4HANA Cloud Public Edition

Cause

  • "FIN_GRIRPROCESSORCHANGED" is a standard situation template that is part of the Standard situation framework.
  • The lifecycle process for exporting to software collections or transport does not apply to standard situation templates.
  • This procedure is exclusively applicable to the Extended situation framework. 

Resolution

For standard situation template, it is not possible to transport the standard situation types from a Development/ Quality system to a Production system.

Instead, the workaround is to create the situation type directly in the target system using the situation template available there.

Refer to the Use Case list in the "Situation Template Type" column for each situation template to confirm whether the situation template is standard or extended.

See Also

SAP Help Portal - Use Case

Keywords

situation type, add items list, export software collection, standard situation template, extended situation  framework, transport situation type, create situation type, software collection management , KBA , CA-SIT-ENG , Situation Handling: Situation Engine , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , Problem

Product

SAP S/4HANA Cloud Public Edition all versions