- You want to import a collection in Productive system.
- You are using the Import Collection app in Productive system.
- The software collection you want to import is categorized as Business Interruption: High Risk.
- The software collection you want to import contains custom fields.
The publishing and the deletion of custom fields technically requires an ABAP dictionary activation. Depending on the application or business context, there can be a lot of objects involved, which can cause long runtimes.
The importing process implies publishing the custom fields in the Productive system and, therefore, the ABAP dictionary activation process.
Importing items can lead to business interruptions, when users are working in the system while the items are being changed by the import. The business interruption risk persists until an import is finished. In case of a business interruption, users might face data loss or batch jobs and external services might be interrupted. The Business Interruption column indicates if the interruption risk is high or low.
If you are importing a collection that contains custom fields, you need to take into account that this kind of software collections are usually categorized as high business interruption risk and you need to plan the importing activity accordingly. It is recommended to import collections with a high business interruption risk after working hours.
You can use the Transport Automation feature to schedule the automatic import of software collections outside of business hours.
importing, software collection, high risk, custom field, business interruption, import collection , KBA , BC-SRV-APS-EXT-FLD , Custom Fields , BC-SRV-APS-EXT-SL , Manage and Import Software Collections , BC-DWB-DIC-AC , ABAP Dictionary Activation and Conversion , Problem