Checks on Status Change

Setting an object status, the ProConfiguration performs several checks. If the check results in one or more errors, ProConfiguration will always issue a corresponding message or log.

Status Not Valid/Not Available

On objects (material, document etc.) it is possible to check whether a certain status cannot be set, because the status is not allowed or selectable for the current status net.

Example: the material status, set with transaction MM02 cannot be set.

Open

Status Cannot be Set Manually

On objects (material, document, etc.) it can be checked that certain statuses cannot be set manually by the user because they are set by ProConfiguration via object dependencies, for example.

Example: Document status cannot be set manually.

Open

Part Family Status

After starting a processing scenario in a part family, it will be checked, whether the status change on the family member is possible for all materials in the part family.

Example: Status change not possible because of status in part family.

Error Object Handling

Errors during object handling (create, new version, link…) will be listed in a log.

Example: Object could not be created, because the change number was locked by user CG. After the change number was released, the line in the upper part of the dialog can be marked (1) and the action can be repeated (2).

In case the user has no permission to repeat the last action, he must address the ProConfiguration administrator, who is able to control the administrator user interface of ProConfiguration and to repeat the last action.

Check Object Dependencies

Setting an object status, ProConfiguration will run several checks on other objects (documents, material, components in BOM etc.). If one or more checks are negative, the user will be informed with a message / protocol.

Example: The new/next document status is checked on all existing documents in the data package:

Before executing depending actions, e.g. setting another status on another object, ProConfiguration counts the number of internal sessions (see also below). If the number of internal sessions is too small, the following message will appear:

What are internal sessions?

A session is an open SAP window where you can process a certain task. You can open several sessions and work on a different system task in each session, just as you can work with multiple open windows in other software applications. If a program starts another transaction or another program (e.g. double-click on the object), an internal session will be started. SAP limits the number of internal sessions down to 10. Internal sessions are independent of the number of open windows within a terminal session; they only count within one window.
After starting SAP (which opens a window), the main program to display the main menu (easy access) will use already one session. After starting the first transaction, the second session will become active. In the following a possible scenario of internal sessions of actions with objects dependencies is explained.

Normally this causes no problems. But because of the navigation it may be possible, that on the moment of the status change an internal session is already active, which does not allow more depending actions.

Example: Start SAP (1) > PCL (2) > MM03 (3) > Link objects / CV03 (4) > Document structure (5) > Document display and change to edit (6) > status change.

This way the first object dependency will already start in the 7th internal session. If nested actions are necessary, it may be possible, that the number of still available sessions is not sufficient. If not enough actions are available for the required actions, it is necessary to quit the nested transactions and the initial action must be executed in the first session.

Check BOM (Structures)

While setting an object status the ProConfiguration can run checks on the BOMs. If one or more checks are negative, the user will be informed with a message/protocol.

Example: A new material status checks the status of the components in a BOM.