New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Specification comparison Release 2503 | The specification comparison now also returns a result if no partner node was found for a node or if there is a disjoint intersection with regard to the object types for a pair. These results are also visualised in the GUI. | NOTE-3628 | ||
| QPPD Licensing | With this NOTE it is necessary to enter a licence key in order to use QPPD. | NOTE-3625 | ||
| New object type Application log and logger functions | This new object type can be used to display messages from the standard SAP Business Application Log (BAL) that have been saved for the node. In addition, the new class /SCT/QP_CL_LOGGER can be used as a wrapper to maintain (add, delete) messages in the BAL for a node at runtime. The new object type also saves the messages from the BAL to the node when the object is saved. | NOTE-3617 | ||
| TEXT: New functions | Generation with overwriting can now be carried out in the GUI. Only the generation class needs to be specified in customising. The generation methods are executed in a similar way to MAMBA. In addition, there is new functionality for transferring values in the generation methods. | NOTE-3376 |
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Removal of exceptions | Superfluous exceptions and coding have been removed. | NOTE-3630 | ||
| GUI: Processing of function codes | The processing of some function codes in the GUI/CONTROLLER has been revised according to the MVC model. | NOTE-3629 | ||
| Transport Order: Functional enhancement | The class /SCT/QP_CL_TRANSPORT_ORDER has been extended with functions to add TADIR entries to a transport request. In addition, the method for determining the deleted objects has been revised. | NOTE-3626 | ||
| Refactored implementation for work mode | Refactored according to MVC architecture: 1) Determination of unauthorised function codes after status changes at the node. This also leads to an improvement in performance. 2) The various methods for changing the working mode have been extensively refactored. 3) The logic for taking the global working mode into account has been moved from the CONTROLLER to the GUI. | NOTE-3624 | ||
| FUP Release 2503 | All data from deleted nodes is provided to the FUP and the change documents. The method DO_CHANGE_QUEUE_NAME can now be used to overwrite customer-specific settings for the FUP that have been predefined in Customizing. | NOTE-3622 | ||
| BRF+ Execute method returns result data | The method BRF_PROCESS3->EXECUTE is enabled with this NOTE to return the results from the SAP standard BRF+. | NOTE-3620 | ||
| BGRFC Retry units | This NOTE provides a new method in the FUP_MAIN to restart a bgRFC unit if it had to be cancelled during processing. | NOTE-3615 | ||
| MAMBA: Synchronisation of deletions of complete rows | This NOTE enables MAMBA to synchronise the deletion of entire rows from the grid, which may consist of several elements. | NOTE-3611 | ||
| Release / Mass release | If an object is released or a mass release is carried out and the object uses consistent versioning, then an unnecessary number of previous versions are loaded. The release/mass release has been completely revised technically. | NOTE-3610 | ||
| SD : Technical improvement | Technical improvement to process SD data. | NOTE-3606 | ||
| Linking of BDS documents | With this NOTE it is not only possible to create new BDS data records via the BUS, but also to create links to existing BDS data records. | NOTE-3597 | ||
| GUI main tree: optimisations and bug fixes | The structure of the main tree has been completely revised technically. Among other things, the nodes are now only created when required. This leads to an improvement in performance. | NOTE-3595 | ||
| Extended dialogue window for creating and maintaining objects Release 2503 | The functions relating to the extended dialogue window for creating and maintaining objects have been completely revised. In addition, error corrections have been implemented. | NOTE-3594 | ||
| Name generation | This NOTE implements the automatic conversion to the output format for values from the object types for name generation, which can be set in customising. | NOTE-3593 | ||
| BDS: Method enhanced | The BDS_GET_CONTENT method now also returns the information on MIMETYP. | NOTE-3589 | ||
| GUI: Favourites tree and worklist | The functions relating to the "Specifications to be checked" area have been deleted from the QPPD standard. New methods are provided in the BADI GUI to implement this area on a customised basis. | NOTE-3588 | ||
| Determination of the BASE sorting criterion | The sorting criterion at the BASE (SORTKR field) is determined with this NOTE when the BASE is created. | NOTE-3585 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Performance improvement when deleting nodes | Performance has been improved when deleting nodes. | NOTE-3608 | ||
| TOOLS/CONV performance improvements | The methods CONV->DO_CONVERT_TSTM_TO_OUT_SUB, CONV->DO_CONVERT_UTC_TO_TZONE, TOOLS->IS_STRING_CONTAIN_CRLF, TOOLS->IS_STRING_CONTAIN_SPACE have been optimized in terms of performance. | NOTE-3604 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | ME Release 2503 | Under certain circumstances, the error message "No data has been changed" was displayed when processing the purchasing document. | NOTE-3621 | ||
| BRF+ External ID for trace | When BRF+ was called from QPPD, the so-called external ID for the standard SAP BRF+ trace was not always saved correctly. | NOTE-3619 | ||
| VART instance at the node | If node instances were also used in a non-original context, the MS_BASE attribute on the node was not always updated correctly. This resulted in incorrect VART instances being used. The attribute is no longer supported. With this NOTE, new methods are made available on the node in order to obtain the correct VART instance or data of the node. | NOTE-3614 | ||
| Copying non-original BASE entries | If a node is to be created as a copy below another node using drag & drop, an error occurred if the hierarchy was not suitable. | NOTE-3613 | ||
| GUI: Drag&Drop | If an attempt was made to load an object via drag & drop by dragging a non-original node from the main tree onto the empty area below the main tree, an error occurred. Too many objects were also loaded and displayed in the main tree if an object with non-original relations was dragged and dropped onto the empty area below the tree. | NOTE-3612 | ||
| BDS: Drag & Drop | When dragging and dropping files into the object types, a short dump occurred if SAP GUI for HTML was used, as drag and drop is generally not supported by SAP GUI for HTML. | NOTE-3605 | ||
| CUST: Language-dependent descriptions | If the customising shared memory is used simultaneously with different logon languages, individual descriptions from the customising are not returned with the correct language. | NOTE-3603 | ||
| If an element is not editable, the mandatory field control via BRF+ has not worked. | NOTE-3602 | |||
| MAMBA View: Settings for layout variants are not always saved | The settings for the layout variants of the grid regarding column optimisation and sorting were not always saved correctly. | NOTE-3601 | ||
| MASS Release 2503 | The error with the counter that shows how many objects have already been processed when saving has been corrected. The selection with ranges did not work correctly. The selection of objects with brackets in rule names caused problems. Texts of the buttons "Calculate amount" and "Delete valuation" are no longer interchanged. | NOTE-3600 | ||
| Preselection | The "Show complete objects" indicator was not correctly taken into account when using the preselection dialogue if the results were to be displayed in the cockpit. | NOTE-3599 | ||
| Processing by bgRFC is not recognised correctly | The TOOLS->IS_DIALOGUE method does not correctly recognise that processing with bgRFC is currently running. | NOTE-3598 | ||
| MAMBA: Search help | When calling a non-TOE search help, a field that is not a field but a structure or a table can be found when the search help parameters are supplied dynamically. If TOE and non-TOE search helps are used simultaneously on the object type, an error occurs because TOE is still incorrectly initialised. | NOTE-3596 | ||
| Free up memory Release 2503 | When freeing up the memory, not all contained objects were always freed up if they were loaded as original and non-original at the same time. In addition, the freeing of memory for TOE and INFO objects has been improved. | NOTE-3591 | ||
| If the object uses a global generation or contains specification blocks, errors could occur. During consistent versioning, the PREVOGUID was not always set and only the first level of the subordinate nodes was taken along when the item types were moved. When versioning item types, the export parameter was supplied with the new root node and not with the new item type. When versioning objects, an attempt was mistakenly made to version item type that had already been marked as deleted. The version replacement function has been removed from the QPPD standard. | NOTE-3590 | |||
| Mamba: Display error columns | An error in | NOTE-3587 | ||
| MAMBA: Generated values for flags | The generated values for the flags FLAG01, ..., FLAG10 were not processed correctly by the object type. | NOTE-3559 |