Main topics
FUP - Function extension.
Switch "MULTI": Customizing switch, whether multiple entries are allowed in a bgRFC queue or not
An exception is generated in the event of an error
Lock entries
Read locks are set on objects if they are used by other objects.
BADIs for APPs deactivated by default
The standard QPPD implementations are deactivated by default and sample implementations are made available.
IDOC
Adaptation MATNR to 40 digits
APPS
PP
Various improvements. Including determination/handling of the production version. Restructuring of methods so that customer-specific logic can be implemented more easily.
MM
Plant-dependent and plant-independent views are now possible.
New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | QPPD Selection Screen Clear | Clear and Clear All Buttons are now available on the ECC Selection Screen.
Clear All from other Selection Subscreens also clear the ECC Selection Screen. | NOTE-3231 | ||
| APP MM Release 2203 | New functions:
Plant-dependent and plant-independent views are now possible. Consideration of a plant-independent before the plant-dependent KMAT for the material for the selection of customizing. Differentiation classification to material via CUOBJ/CUOBF. Corrections: Jump MM GUI to QPPD Cockpit corrected. Deletion of all QPPD objects for material corrected. | NOTE-3210 |
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | VART class: Methods for changing the working mode | The BUS methods for changing the operating mode are provided in the VART class. A repeat sequence can optionally be specified for FBD processing. | used workmode_change and Workmode_display in individual logic of spezification class | NOTE-3374 | |
| Central authorisation check Grid variant | The authorisation check for the grid variant is now carried out centrally via the AUTHORITY class. | NOTE-3288 | ||
| FBD: switch for data | Immense data is sometimes made available to the associated FBDs when they are generated during storage. It is about:
the current data (DB_DATA), the old data (DB_DATA_OLD), the differences (DB_DATA_DEL, DB_DATA_ADD, DB_DATA_MOD). The size of the data delays saving. Also, not all data is always required for each FBD. Therefore, with this NOTE, a new customizing switch USE_DB_DATA is introduced in table /SCT/QP_TFUP. This has the following values: blank = no DB data (default value), K = current DB data: DB_DATA is filled, O = Current and old DB data: DB_DATA and DB_DATA_OLD are filled, A = Current, old and difference DB data: DB_DATA, DB_DATA_OLD as well as DB_DATA_DEL, DB_DATA_ADD, DB_DATA_MOD are filled. | NOTE-3235 | ||
| QPPD APP BADIs disabled by default | With this NOTE, the QPPD implementations in the /SCT/ namespace of the APP-specific BADIs are disabled by default. In addition, these are marked as example implementations. This is intended to ensure that the QPPD initially has no effect on the standard processes after installation. It is therefore necessary to create a Z implementation of the QPPD BADIs in order to activate an APP. This can be inherited from the standard /SCT/ implementation. | NOTE-3230 | ||
| BUS: return of the last exception | The BUS now returns the last exception in the new export parameter EO_ERROR. | NOTE-3228 | ||
| BRF+ changed Default Engine now V3 | when using the standard, the memory consumption is reduced. All BRF+ types are supported. The existing set of rules from version 2 is upward compatible with version 3.
If mapping classes have been redefined. This coding is not functional. | none
If version 2 should continue to be used as the default, this can be changed via the parameter setting: Parameter: BRF_ENGINE Value: V2 | NOTE-3224 | |
| Global generation: Individual setting of generation indicators | Global generation is often used for complex objects. Due to dependencies of the elements among each other, the level settings for notifications of nodes lead to extensive repetitions of the generation methods.
In Customizing, the option Individual can now be specified when sending the hierarchy. The method SET_INDIVIDUAL_GENER_FLAG of the VART class is called. The current node and object type as well as the references to the base entries are passed. The generation flag can then be set individually. | Redefinition of the method /SCT/QP_IF_VART->SET_GENER_FLAG in the respective VART class | NOTE-3220 | |
| APP PP Release 2203 | Various improvements in the APP PP. Among others: Determination/handling of the production version. Restructuring of the methods so that customer-specific logic can be implemented more easily. | NOTE-3217 | ||
| BRF+ copy of applications to other systems | with report /SCT/QP_BRF_COPY BRF applications can be copied to other systems and clients via RFC connections. | authorithy role for BRF+ XML export and Import and RFC function calls | NOTE-3215 | |
| Enhancement of ECC document determination with additional fields VNR, VVS, VNAME and STATUS | NOTE-3208 | |||
| APP PP Release 2203: Improvements BADI | Adaptations for APO/PPDS, selection of production version | NOTE-3207 | ||
| PP: Production version selection | A new method allows you to select an SAP-standard production version using QPPD data. | NOTE-3205 | ||
| IDOC: HEADER extension | With the conversion to S/4, the standard SAP field MATNR was extended from 18 to 40 digits. This NOTE adjusts the QPPD segments. | NOTE-3204 | ||
| Create nodes | When creating nodes with a BASE template, the status is incorrectly filled under certain circumstances. | NOTE-3131 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | CL_DATA_DB : Optimized reading from Long texts | during database access, the long texts are now accessed in an optimized way. | NOTE-3221 | ||
| Performance improvement accessing VART-instances | Performance improvement accessing VART-instances | NOTE-3219 | ||
| CUST-Service: Perfomance | The CUST service builds its buffer tables differentially. First of all, this means that a buffer table is only set up if the content is required directly or indirectly. If necessary, the relevant table is built up completely. With this NOTE it is also possible to partially build up the table. In the case of very large buffer tables, this results in a performance gain. | NOTE-3218 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | NOTE-3239 | ||||
| TECHM_DUO: Duplicate | If an object type is duplicated, which is represented by TECHM_DUO, the long texts are not copied. | NOTE-3233 | ||
| Lock entries | If multiple users use a node from one object as a non-original node in another object, lock entries may be generated incorrectly. This in turn can prevent legitimate deletion of nodes. | NOTE-3232 | ||
| DATA_DB: Reading with hierarchy "Original" | Reading QPPD data via the DB only with the specification GUID and Hierarchy = Original, i.e. without OGUID, did not work properly. | NOTE-3227 | ||
| TOOLS->GET_STRUCT_COMP does not return any fields from IDOC segments | The TOOLS->GET_STRUCT_COMP method does not return any components if the specified DDIC structure represents an IDOC segment. | NOTE-3226 | ||
| SD: Shortdump when called by IDOC processing | If a standard ORDERS IDOC is posted, a short dump occurs. | NOTE-3225 | ||
| TOOLS->DO_SPLIT_RANGES Values are converted into different units, but the unit isnt changed | If now values are converted the unit will be changed aswell. | NOTE-3216 | ||
| VART class does not return references to BASE entries when selecting for context | BASE entries are not returned | NOTE-3214 | ||
| MAMBA: Conversion error for vertical elements | 1. If syntactically incorrect values are set for dynamic elements via the BUS, the cells in the grid are not colored or not colored correctly.
2. If initial, vertical elements are evaluated with a syntactically incorrect value, incorrect error messages are generated. 3. If syntax errors are corrected via the BUS, the error messages were not updated. | NOTE-3213 | ||
| Long-text-button anf stx_text for dyn-columns | Sometimes the system displayed the wrong icon on the long-text button, on the long-text was not properly shown | NOTE-3212 | ||
| TOE Mandatory field control faulty | If the mandatory field control is called for an element for which no context check is stored, the MANDATORY field is reset. Customizing setting for the element will be overwritten.
In addition, the mandatory control is not executed when the element is created. | NOTE-3211 | ||
| SYNC_VC: Korrekturen | The changes from the VC to its sync partners were processed even if the sync partners were not active. | NOTE-3209 | ||
| BUS->CHANGEs makes changes when the hierarchy is not editable | the builder was started, even if the root node was not editable (locked by another user ) | NOTE-3206 | ||
| TOE Defaults: Resetting generated values | If the generation of default values was implemented via TOE and the VALUE_TYPE is not one of the fields VALUE, VALUE_MIN and VALUE_MAX, the possibly generated value was reset if the method contained the name TOE. | NOTE-3199 | ||
| CL_VART->GET_OR_CREATE_NODE incorrect | The method CL_VART->GET_OR_CREATE_NODE did not work correctly. | NOTE-3194 |