Error when importing ProNovia products

Errors occasionally occur when importing ProNovia products. These can be roughly divided into four categories:

The dependencies and/or the instructions for import were not taken into account.
One or more objects delivered by ProNovia are not compatible with the system
So-called deadlocks occur
A general error occurs in the transport system

In case of an error (but ideally also in case of warnings) the import logs must be checked to narrow down the error.

Dependencies and/or import instructions not taken into account

For the installation of products it is necessary that all dependencies are fulfilled. ProNovia provides a specially developed tool for the installation of products, which checks all product kits for their dependencies before the transports are added to the import queue. Due to the strong dependencies between objects, importing a single job will cause objects outside the job to be regenerated as well. This can also lead to problems, which is why all transports must always be imported at the same time during a product upgrade.

The entire installation and upgrade process is described here and must be followed.

Incompatible objects

During the internal release process, all ProNovia products go through a series of checks. These include dependency checks to ensure that products do not reference other products that may not be available to customers. Likewise, each reference to an SAP standard element is checked to exclude the use of non-core objects.

Nevertheless, due to different release statuses (EhP, SP) it can happen in individual cases that objects used by ProNovia are not available on a customer system. Furthermore, it happens in rare cases that incompatible changes are (have to be) made to the base products (ProBasicLib, ProObjectLib, ProFramework) and thus other installed products become faulty when updating such a product. This occurs however only in absolute exceptional cases, since most changes can be made downward compatible. In addition, such incompatible changes are described in the knowledge base in each case.

In such cases, the log describes in detail which objects are faulty and why. Check whether these are objects from ProNovia. This can be recognized by the namespace /PRONOVIA/ or /PCH/. Create a ticket in the ProNovia Support Center so that specialists can take a closer look at the issue if it is a ProNovia object.

Deadlocks

So-called deadlocks can occur during import. In this case several processes try to change the same data. Such errors can never be completely excluded and cannot be influenced by ProNovia. In the SAP knowledge base article 1454536 describes the problem and also a possible parameter to reduce the occurrence.

Some ProNovia products contain several hundred or even several thousand objects (e.g. ProFramework contains about 12'000 single objects). In addition, the technical dependency between objects due to the object-oriented architecture leads to the additional generation of a large number of objects that were not part of the actual transport. This behavior can also not be influenced by ProNovia. These two factors lead to the fact that the import lasts under circumstances very long and the susceptibility for Deadlocks increases. If the import is carried out during operation, the problem is also dramatically increased, since objects are also continuously generated by users. ProNovia product updates are not comparable with normal transports but much more with SAP upgrade processes due to their sometimes very large volume.

It is strongly recommended to perform a product upgrade at a marginal time or in a locked upgrade window.

Details about imports into running systems are documented in the following SAP Notes:

Errors in the transport system

Occasionally, errors occur during import caused by technical problems in the transport system. ProNovia has no influence on such errors. Such errors can have a wide variety of causes. They can be errors of SAP programs but also of the components R3trans or tp, which are necessary for the import. In a first step it is recommended to restart the import again. If the same error occurs again, check the SAP knowledge base to see if there is a solution.

Previous version not matching when importing ProNovia products

When importing ProNovia product transports, they may appear in the import queue with the status Does not match component version. This status indicates that the installed SAP components (and versions) on the ProNovia origin system do not match their system. However, this check can be ignored for the import of ProNovia products, since ProNovia products are delivered in their own namespace and ProNovia ensures compatibility with SAP components.

To import the transports, the option Ignore non-matching component version must be activated during the import.