New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Validation for regulation types without regard to the validity date | The following new class can now be selected in the customizing settings for the technical element: /SCT/QP_CL_TOE_VART_NO_VALID The validity date is not taken into account in this class. Otherwise, the validity check functions the same. | NOTE-3689 |
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | GUI: Context menu entries without text | If a regulation type or item type lacked a description in the logon language, it was not displayed in the context menu. With this Note, the technical description is used instead if a text is missing. | NOTE-3701 | ||
| Global generation: Extended log | An extended log for global generation can be activated using the QPPD parameter "/SCT/QP_GLOBGENLOG" and the value "X". | NOTE-3694 | ||
| Adding links below multiple specification blocks | It was not possible to add links below multiple specification blocks. | NOTE-3691 | ||
| Updating values in /SCT/QP_NUM | With this NOTE, only values that are error-free and have not been deleted are written to table /SCT/QP_NUM. | NOTE-3685 | ||
| HEADER: Consideration of lowercase letters | With this NOTE, the input fields for the specification name in the various HEADER screens also allow lowercase letters. | NOTE-3680 | ||
| BUS: Guessing logic extended | The CUST->GET_NODE_HIERA_ELEMENTS method now only returns entries with the element from IV_ELEMENT in the ET_ELEMENT_USAGE table, provided that IV_ELEMENT is filled. BUS->DO_LINK_DETAILS__NODETARGET: If an element group has been specified in the VAL data records, an attempt is made to find the element at the target with this element group. If no element with this element group is found, the element is determined using the previous logic by taking the element that matches the current node from any element group of the object type. | NOTE-3677 | ||
| TOOLS: JUMP outsourced | The JUMP logic from FM/SCT/QP_DO_JUMP_NODE has been moved to TOOLS->GET_NODEKEY_FOR_JUMP. | NOTE-3676 | ||
| NOTE-3675 | ||||
| BRF+: Additional EXIT after generation | This NOTE provides an additional exit following the receipt and conversion of the generation values from BRF+. | NOTE-3674 | ||
| Mandatory node inspection | With this NOTE, the mandatory node check is no longer performed when saving, but whenever the object is modified with respect to the number of its position types. A new event handler method, VART->ON_CHECK_CHILDS_MANDATORY, is provided, which can be used to modify the mandatory nodes. | NOTE-3668 | ||
| BRF+ v1/v2 and DOG deleted | The BRF+ v1/v2 and DOG applications have been deleted. | NOTE-3664 | ||
| Foreign keys in text tables | The tables /SCT/QP_NODET and /SCT/QP_VALT, or the structures they contain, each receive a foreign key to the table TJ02-SPRAS for the SPRAS field. | NOTE-3663 | ||
| New BADI NODE->ON_ACTIVITY_AFTER | When an action is executed at a node, the new BADI NODE->ON_ACTIVITY_AFTER provides new opportunities for customer-specific extensions after the standard coding has been executed. This NOTE also resolves the issue of checks being executed twice. | NOTE-2290 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Free up memory Release 2603 | If objects have BOM relations, not all memory was released when the memory was freed. If attempts were made to reload objects, they were not reloaded, or not fully reloaded, under certain circumstances if parts of the object were already loaded in other objects. Nodes that were reloaded but are used in other objects (in non-original relations) that were not reloaded will also not be updated. | NOTE-3686 | ||
| NOTE-3683 | ||||
| BUS->ACTIVITY Performance | When executing BUS->ACTIVITY, too much data was read from the affected object too frequently. In addition, this NOTE resolves an issue with this performance improvement where processing would terminate if follow-up processes were already involved during the read operation. | NOTE-3662 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | NOTE-3704 | ||||
| Global Generation Release 2603 | 1) An error occurred when re-executing global generation on an object for which global generation was already running; consequently, global generation remained technically suppressed after execution. 2) If global generation has been executed for an object and a collective TOE check for the entire object subsequently runs, nodes of the object may be marked for generation again. Therefore, global generation is executed once more for the marked nodes of the object. 3) Due to an error in the "NOTE" object type, global generation was executed prior to the notification. 4) Global generation can optionally be suppressed when switching the WORKMODE. | NOTE-3703 | ||
| GUI: JUMP objects not displayed | This NOTE fixes a GUI error where QPPD objects were not displayed after navigating away and returning. | NOTE-3702 | ||
| During generation, QPPD's own method CHECK_DATA was executed erroneously. | NOTE-3699 | |||
| NOTE-3697 | ||||
| VART->GET_NODE_OBJECT returns an incorrect result | The VART->GET_NODE_OBJECT method did not return the correct object type when the object type was not specified. | NOTE-3696 | ||
| Mamba: Column optimization on first call | Column optimization in MAMBA did not work on the first call under certain circumstances. | NOTE-3695 | ||
| GUI: Dump after deleting the node | If a node in the tree has been deleted, a dump may occur under certain circumstances because an attempt was made to process the node that no longer exists. | NOTE-3693 | ||
| GUI: Short dump after saving | If the deleted items folder was expanded and there were still other items in the tree, a short dump occurred after saving. | NOTE-3690 | ||
| Lock conflict | When switching to edit mode, an incorrect lock conflict occurred if the object in question had a BOM relationship to another object that another user had locked exclusively in another session. | NOTE-3688 | ||
| VART class: Deleting relations | Deleting relations via the VART class using the DELETE_NODE method was not always possible. | NOTE-3687 | ||
| IDOC Segment NUM | When transferring data from the NUM table, the values of elements were truncated after 15 characters. | NOTE-3684 | ||
| Global working mode | Various bug fixes for the global work mode. | NOTE-3682 | ||
| Extended dialogue window for creating and maintaining objects Release 2603 | This NOTE fixes an error that occurs when creating BOM relationships via the extended dialog box for object creation and maintenance. | NOTE-3679 | ||
| TOOLS: Short dump with GET_STRING_FROM_STRUCTURE | The TOOLS->GET_STRING_FROM_STRUCTURE method generates a short dump if a reference of the transferred structure is not bound. | NOTE-3678 | ||
| APP PP: Update the display | A short dump occurred, or the display in the production order for the QPPD object type was not updated if that object type was also included in the object representing the production order. | NOTE-3673 | ||
| Error during license verification | This NOTE corrects an error in the license validation process. An incorrect error message was generated. | NOTE-3672 | ||
| MAMBA: MODEREF during restoration of referencing | If an element is marked as deleted (MODEREF = D) and is inherited by another node, when the reference to this element is restored, the MODEREF is incorrectly set to I (manually changed) and does not adopt the original value for MODEREF. | NOTE-3671 | ||
| Return of BASE entries | If an object containing BOMs was read via BUS->READ and only a specific number of BOM levels were to be returned, the correct number of BASE entries was not always returned. | NOTE-3670 | ||
| APPBUS stores too much data | If the import parameter IV_GUID is not specified, APPBUS saves all open changes made by the QPPD—possibly multiple times—instead of saving only the ECC documents. | NOTE-3669 | ||
| Versioning Release 2603 | For versioning, it is generally necessary to have a specification number. With this NOTE, it is now possible to version an object if item types do not have specification numbers. However, this only applies if the specification type uses the versioning types “Weak versioning,” “Versioning as copy” or “Versioning as copy, consistent validity area.” Specification numbers are still required for versioning item types. | NOTE-3666 | ||
| The “Get Variant” button was not visible when the cockpit was first launched. | NOTE-3665 |