New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Change documents Release 2409 | This NOTE can now be used to display the values for OBJECT TYPE, ROWGRP, ELEMENT and LFDNR in the change document display. Performance improvements have also been made. | NOTE-3570 | ||
| MAMBA: Input check against permitted units of measurement | This NOTE is used to check the units of measurement entered against the dimension stored on the element. | NOTE-3563 |
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | SYNC: Additional data for changing objects | The use of additional data from the class /SCT/QP_CL_SYNC_ADD_DATA is supported with this NOTE not only when creating objects, but also when changing objects. | NOTE-3584 | ||
| RFC: Table NUM is distributed | Using the RFC-functions to copy QPPD-objects distributes additionally the /SCT/QP_NUM tables. | NOTE-3579 | ||
| Indexes for /SCT/QP_ALP | The /SCT/QP_ALP table has been provided with the indexes 010 for access via OGUID and 020 for access via GUID. | NOTE-3577 | ||
| MAMBA: Optimizations View | 1) Various small performance improvements
2) It is now possible to display the element name of a vertical column in Mamba. 3) When entering values in the grid that are not applicable, an error message is displayed as a popup. 4) Removed unassigned error messages when initializing the object type. 5) Display error if the object type uses vertical elements but the primary reference does not. 6) Incorrect error messages when using layout variants. | NOTE-3576 | ||
| BUS->ACTIVATE: Change mode | When using the BUS->ACTIVATE function, the object with this NOTE is set to change mode before the function is executed. | NOTE-3572 | ||
| MAMBA: Zugriff mit LFDNR | Internal access to data in MAMBA is only carried out with the LFDNR if there is no vertical element group. | NOTE-3562 | ||
| Program for downloading texts | The program /SCT/QP_DOWNLOAD_TEXT allows you to download texts. | NOTE-3556 | ||
| Transport Order Release 2409 | The auxiliary class TRANSPORT_ORDER has been equipped with an interface and new functionalities have been added. | NOTE-3554 | ||
| Certification Release 2409 | Extensive changes were made to the entire QPPD in order to obtain the certificate. | NOTE-3548 | ||
| Instantiation of PROGRESS | The class /SCT/QP_CL_PROGRESS generates an instance of itself without the FACTORY.
PROGRESS changed to interface. SET_ACTIVE is now a PUBLIC method. PROGRESS is now also available in FACTORY=>GET_INSTANCES. /SCT/QP_CL_GTS changed to IF_PROGRESS. | NOTE-3462 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | ECC documents: memory consumption and performance | When ECC documents are initialised, the detailed data (VAL, PMK, texts, documents) are not created. | NOTE-3581 | ||
| MAMBA: GET_CHECK_ERRORS | Performance improvement in the internal determination of errors for a value. | NOTE-3569 | ||
| GUI: Too many FLUSH | An unnecessary flush is performed when the object type is changed, nodes are expanded in the tree, drag & drop is performed or certain buttons are clicked. | NOTE-3555 | ||
| SYNC: Performance with multiple sync models | If several sync models are active, too many synchronizations are performed. | NOTE-3551 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Action Log Shortump | When displaying the action log, a short dump may occur under certain circumstances. | NOTE-3586 | ||
| BRF: Incorrect mapping | Incorrect mapping when using ITEM, NODE, PARENT or also FIRST, LAST, PREVIOUS or NEXT. | NOTE-3583 | ||
| Recalculate NUM | New functions (BUS, FUP) are provided for the recalculation of NUM entries. The associated report /SCT/QP_FILL_QP_NUM has been converted to FUP | NOTE-3580 | ||
| BUS Release 2409 | BUS->CREATE_REF: Pass through ER_BASE_NEW
BUS->CHANGE: Read the object again after all actions and supply ET_BASE if necessary | NOTE-3578 | ||
| MAMBA: Value fields + notifications | When changing TME and PMK values (VAL, VALT, PMK) or long texts for the element via the BUS, it was not always correctly recognized that the data record had changed.
Affected functions: 1) BADI DO_CHANGE_DATA on the object type was not called correctly 2) Event handler VART->ON_VALUES_CHANGED was not called correctly 3) Management data, ORIGIN, MODEDREF, MANU, STATGEN, STATELM not set correctly 4) Generation of TDNAME for long text when reference is redefined | NOTE-3575 | ||
| Object under ECC-Doc cannot be deleted | An object under an ECC document could not be deleted if at least one object linked under this ECC document has a termination error. | NOTE-3574 | ||
| Fehler | BRF+ functions distributed via DSM (Decision Management System) generate a short dump when a function is called. | NOTE-3573 | ||
| Empty hierarchy in NODE->MT_CHILDS | The hierarchy in the NODE->MT_CHILDS was not set up correctly. | NOTE-3571 | ||
| BUS: Creating nodes | When creating nodes via the BUS, the internal information, e.g. from the TGRUELM, was not transferred to the new data record. As soon as the data record is maintained again, the missing information is added. | NOTE-3568 | ||
| GUI title cut off | The name of the current node is truncated in the GUI if the default name was at least 36 characters long. | NOTE-3567 | ||
| Dump when jumping into the cockpit | Under certain circumstances, a dump occurs when jumping to the QPPD Cockpit. This dump is probably due to a change in the SAP standard and does not behave in the same way on all installations. To counteract the dump, the QPPD offers the two new parameters /SCT/TREE_SELNODE_FLUSH_A and /SCT/TREE_SELNODE_FLUSH_B with this NOTE, which trigger a flush before or after updating the main tree. | NOTE-3566 | ||
| DOC: Data loss when duplicating/saving nodes | Duplicating/saving causes the information for the BDS documents to be lost under certain circumstances. | NOTE-3565 | ||
| CUST-Service Freigabe 2409 | This NOTE contains corrections to the CUST SHMO. | NOTE-3564 | ||
| No updating of the grid after switching to display mode | If objects were reloaded, the display was not updated correctly. | NOTE-3561 | ||
| BUS->CHANGE: Call without changes | If the BUS->CHANGE is called without changes, the | NOTE-3560 | ||
| NOTE-3557 | ||||
| Versioning Release 2409 | 1) Corrections when setting OGUIDs if objects are versioned consistently.
2) If an item is versioned consistently and therefore the ROOT must also be versioned consistently, then the item was not versioned after versioning the ROOT. | NOTE-3553 | ||
| APP PP: Improvements 2409 | The APPBUS was not initialised correctly when the PP service was called up in the background. | NOTE-3552 | ||
| Endless loop during generation | If an exception occurred when executing a generation method, this could lead to an infinite loop during generation. With this NOTE, the affected method is only executed once. The notification has also been adjusted. | NOTE-3550 | ||
| BRF+ v2 executes COMMIT | In the BRF+ v2 application, a COMMIT is sent when the internal buffer is created. This NOTE deactivates the creation of the buffer. The BRF+ applications are therefore built dynamically once. | NOTE-3549 | ||
| BUS: CREATE_REF | An error occurs with BUS->CREATE_REF if the PARENT node is the ROOT. | NOTE-3547 | ||
| Specification comparison Release 2409 | Error correction when comparing long texts. If several objects are compared with each other, a display problem occurs in the GUI. | NOTE-3546 | ||
| TEXT: Endless loop | An endless loop could occur when generating texts. | NOTE-3545 | ||
| MAMBA: LANGTEXT Display problems | If a long text can be maintained in several languages on the GRID in the GUI, then after maintaining a long text in one language, the same text was displayed incorrectly in the other languages. This does not affect the saving, but only the display in the GUI. | NOTE-3544 | ||
| MASS Release 2409 | 1) A dump occurs when the cockpit is exited with F3 after the immediate evaluation.
2) Specifications can be locked en masse, but not unlocked en masse. 3) If a specification is versioned consistently, a dump occurs when it is copied. 4) As soon as a specification is versionable, the status cannot be changed via the cockpit, as a new version is always to be created. 5) A dump occurred after the EXCEL export was used. 6) Versioning of objects did not always work. 7) Dump with long field names for Select. | NOTE-3543 |