New functions
| Type | Issuekey | Customfield_10052 | Customfield_10053 | Customfield_10054 | Key |
|---|
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Conversion from BRF+ version 1/2 to version 3 | With the release of 2509, BRF+ version 1/2 will no longer be supported and will be replaced by version 3. | Two possible solutions: 1. Upgrade the BRF+ applications to version 3. 2. Workaround the BRF+ functionality with a customer-specific Z class. - The customizing table contents for calling the application/functions are stored in the object types. See (also Migration Release 2503). - The static classes /SCT/QP_CL_BRF_BUFFER and /SCT/QP_CL_BRF_ACCESS_GLO remain unchanged. The functionality is processed in a Z class, e.g., ZCL_BRF_MAP3. This class inherits from the class /SCT/QP_CL_BRF_MAP3. An example is included in this note. - In the factory, the Z class must be entered for the interfaces/SCT/QP_IF_BRF_MAP3. - In the Z class, the mapping must be reprogrammed in the coding according to the old Customizing. - The generation of elements and structures in Brf+ is only available in version. | NOTE-3660 | |
| Synchronization of VBKD fields and general SYNC-SD problems | With BAPI_SALESORDER_SIMULATE, the QPPD data is now not automatically discarded so that the QPPD data can be accessed after the simulation. After the call, a BUS->FREE must be called explicitly, otherwise the QPPD data remains in the memory until the session is closed. When using the function modules BAPI_SALESORDER_CHANGE or BAPI_SALESORDER_CREATE_FROM_DAT*, the QPPD data is automatically released after saving. | NOTE-3650 | ||
| VART: Assign POSNR when creating relations | The new optional import parameter IV_POSNR can be used to specify the position of the new relation when it is created. | NOTE-3648 | ||
| VART: New method SET_GENER_PENDING_FLAG | This NOTE makes the SET_GENER_PENDING_FLAG method available in the VART interface. This means that not only the GENER flag but also the GENER_PENDING flag can be set for the individual notification. | NOTE-3639 | ||
| Switch to new version for deleting objects, nodes, relations, loading, reloading | The methods for deleting objects, nodes and relations and loading/reloading objects have been changed to the new version. The logic for substitution and the so-called DEFAULT node have also been removed. | NOTE-3634 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Too much data stored | If nodes were loaded several times in different uses, the internal storage routine was run through too often. | NOTE-3640 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Dump on specification blocks for objects | The specification blocks above the objects were not initialized correctly, which led to short dumps in FDMs on these folders. | NOTE-3659 | ||
| Search help: Adjustments for UI | 1) The default values of the selection options were not always correctly taken into account. 2) The conversion of the output values was previously carried out in STEP 3 SELECT. This is sufficient for the GUI, but not for the UI. Therefore, the logic for converting the values was moved from STEP 3 to STEP 4 before mapping the values to the fields. 3) The search help user exit can be used to specify that a possibly existing selection method is not executed. In this case, there was an error in the UI because the wrong subsequent step was executed. | NOTE-3658 | ||
| APPBUS : Mixing memory and DB data | Due to an incorrect merge in the APPBUS->GET_ECC_LINKS_FOR_DOCS method, objects that have already been deleted are incorrectly returned. | NOTE-3657 | ||
| TEXT: Incorrect detection of changes | Although no changes have been made, the TEXT object type has incorrectly recognized changes and consequently triggered subsequent actions, such as generation. | NOTE-3656 | ||
| MAMBA: Editability of fields | If an object type has horizontal and vertical elements, where the vertical elements are set with different maintenance types, then the editability of the horizontal element was calculated incorrectly. | NOTE-3655 | ||
| Origin is not set/reset correctly with subsequent changes | If values with/without the specification of ORIGIN are created or changed via the BUS, ORIGIN is not processed correctly internally under certain circumstances. | NOTE-3653 | ||
| SD: Deleting order items with multiple objects | If several objects are linked to an SD document item and the document item is deleted, a dump takes place. | NOTE-3652 | ||
| Specification Comparison Release 2509 | If an object or part of an object that is used in the rule comparison is deleted, a short dump occurs. | NOTE-3651 | ||
| GUI: Display of nodes after drag & drop | After dragging and dropping nodes, the display was not updated correctly. | NOTE-3649 | ||
| Versioning Release 2509 | 1) PREVOGUID was set incorrectly 2) DUMP in the GUI after versioning 3) Optimization: Under certain circumstances, it is not necessary to set the source object to change mode and check it 4) The versioning of the item type after the versioning of the root node is now carried out in a separate step at the end | NOTE-3647 | ||
| ADD_DATA is not taken into account if there are no SYNC changes. | ADD_DATA is not taken into account if there are no SYNC changes. | NOTE-3646 | ||
| MAMBA: Checkbox is not displayed correctly | When using checkboxes in dynamic columns, the content was not always updated correctly. | NOTE-3645 | ||
| Incomplete release of the node data memory | If the data of a node was released from the memory, its further uses as sub-nodes in other nodes were not released correctly. | NOTE-3644 | ||
| Conversion error with ZAHL | If a conversion method of the number type is used and only the characters "+", "-", ",", ",,", ",,," or spaces are entered, a short dump occurs. | NOTE-3643 | ||
| S/4 adjustments | Adjustments to the coding due to conversion to S/4. | NOTE-3642 | ||
| Translation corrections Release 2509 | Correction of translations. | NOTE-3641 | ||
| Duplicate check | The duplicate check of objects was not carried out correctly under certain circumstances. | NOTE-3638 | ||
| Program /SCT/QP_TABLE transfers larger tables | With this correction the program /SCT/QP_TABLE is able to transfer tables up to a size of 32000 characters. | NOTE-3637 | ||
| Mamba: Column layout not always correct | If a new column is added to an existing layout, moved, and the layout is saved, the column will be displayed in the wrong position the next time it is opened. | NOTE-3636 | ||
| MASS Release 2509 | 1) Elements that are defined as min or max value are now also displayed in the mass update 2) If an activity was carried out on the object, the generation had to be started manually so that the new status was also saved. Now, once the activity has been executed, the generation is automatically executed and the object is saved. 3) If the exclusion operators were used when selecting objects, these were not taken into account correctly. 4) When executing the transaction /SCT/QP_MASS it was possible to enter a non-valid VART and start the program. | NOTE-3635 | ||
| MAMBA: Error message is not always reset | If an incorrect value was entered in the FDM and then corrected in the GUI, the error messages were not reset correctly. | NOTE-3632 |