Main topics
User menu
The QPPD and its transactions are now available in SAP Menu → Logistics → Central Functions.
Change document profile
The writing of change documents has been revised. It is now possible to specify via customzing for which fields change documents should be written. Furthermore, CDS-view are provided to read the change documents.
New status "Technical Error"
The nodes of an object get the status "Technical Error (IZQTD)" if an exception occurs during the initialization of an object. For example, by a used hierarchy, which no longer exists in Customizing.
New fast entry Direct
New collective entry mask outside the standard synchronization.
Rework of global generation
A pending GG no longer generates an error message after a BUS call or a GUI action, which causes a status change.
If a global generation is pending when saving, the user will be presented with a popup to decide whether to re-run the global generation.
If an object has a non-unique name when saved, the rule name is changed to the GUID in the BUS case. In the GUI case, the user is asked to make a decision accordingly beforehand via a popup.
Copy nodes
When dragging a node in the GUI to copy it using drag&drop functionality, and that copying is allowed, then the user is offered two options with/without child nodes for copying.
Miscellaneous text adjustments/translation corrections in DE, EN, FR
APPS
SD
The FDM in sales order integration can alternatively be displayed as an additional tab on the items overview screen.
New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | User menu | Added user menu to SAP Menu:
SAP Menu -> Logistics -> Central Functions -> Quality, Product and Production Definition | NOTE-3367 | ||
| SD TAB | The FDM in sales order integration can alternatively be displayed as an additional tab on the overview screen of the items. | NOTE-3366 | ||
| New fast data Maintenace direct | On the one hand, the class enables a collective entry on the regulation group for the visible objects on item type level. On the other hand, collective entries can also be created within an object for the subordinate nodes.
This associated class does not work with standard synchronization, but becomes active only when the tab is selected in the GUI. The element group data of the associated nodes are displayed in rows. Only system fields and element values are displayed. Inspection characteristics are not supported. If complex and non-unique element values are to be selected in the rules type, relations can be stored in the syncmodel (name of the object type ) in the mapping. The synchronization is done by the button "Sync manual". This class requires the view of the class /SCT/QP_CL_FDM_DIRECT_VIEW. | Create an objectyp containing the classes /SCT/QP_CL_FDM_DIRECT and /SCT/QP_CL_FDM_DIRECT_VIEW. Link the objekttyp to specification Group or a specification. Maintain mapping in synchronisation if element definition is not unique | NOTE-3365 | |
| MAMBA Expander | EXPANDERS not used on a node are no longer available in the LAYOUT. | NOTE-3359 | ||
| BRF+: Additional structure and tables definition for positions in the hierarchy | In BRF+ functions data can be obtained from positions with the relative positioning to the current node by using the following structure prefixes: FIRST, LAST, PREVIOUS, NEXT. | Use of structure and table prefix
FIRST LAST PRIEVIOUS NEXT | NOTE-3355 | |
| PP: Costing of the sales order and confirmation of results | The PP-Service class is extended by further 4 functions:
1) Costing of sales order can be started inside and outside the sales order in "light" mode (with display of costing results) as well as in "dark" mode (without display). 2) Display of the costing of the sales order 3) Cost calculation for a costing number 4) Cost of assemblies for an order or order item | use methods in class /SCT/QP_CL_PP_SERVICE
/sct/qp_if_pp_service~calculate_sd_process /sct/qp_if_pp_service~calculate_sd_display /sct/qp_if_pp_service~calculate_sd_result /sct/qp_if_pp_service~calculate_result | NOTE-3348 | |
| GUI: Copy nodes | If a node is dragged to a node in the GUI to copy it using drag and drop functionality,and that copying is allowed, then the user is offered two options with/without child nodes for copying. | NOTE-3345 | ||
| New authorization object /SCT/QPPD2 with "Plant" field | In addition to the previous authorization object /SCT/QPPD with the fields VART, VTYP, AG, ACTVT, another authorization object /SCT/QPPD2 with the fields VART, VTYP, AG, WERKS, ACTVT is provided, which enables a check with the new field Plant. | NOTE-3324 | ||
| Change documents Release 2303: Change document profile | The writing of change documents has been revised. It is now possible to specify via customzing for which fields change documents are to be written. In addition, CDS-view is provided to read out the change documents. | The change document profile "X" must be entered.
For S/4 systems: The class /SCT/QP_CL_CHGDOC_S4 must be entered as class for the interface /SCT/QP_IF_CHGDOC. For the FBD "SCT_CHGD" must be set: DB data "Individual". For the migration to the new settings the program /SCT/QP_MIGRATE_CDP can be used. | NOTE-3295 | |
| New status "Technical error | The nodes of an object get the status "Technical error (IZQTD)" if an exception occurs during the initialization of an object. For example, due to a hierarchy used, which no longer exists in Customizing. | NOTE-2009 |
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | CDS-views: Splitting into consumer/interface views | The provided CDS-views /SCT/QP_C_DOMAIN_01, /SCT/QP_C_NODE, /SCT/QP_C_PP_PLPO are split into consumer/interface views. | All customer views that refer to the views /SCT/QP_C_DOMAIN_01, /SCT/QP_C_NODE, /SCT/QP_C_PP_PLPO must be adjusted. | NOTE-3399 | |
| ECC: GET_ECC_KEYS extension for APPs | Extension of the ECC->GET_ECC_KEYS method with the other APPs. | NOTE-3398 | ||
| BADI GUI->DO_MT_CTEXT_SEL | With | NOTE-3396 | ||
| Old objects | Various objects will be moved to the OLD package and will not be delivered for new customers. | NOTE-3391 | ||
| Authorization check for system regulation types deactivated | Authorization check for system regulation types deactivated | NOTE-3389 | ||
| Value fields: Extension | The field SOLLINTEINH has been added to the structure /SCT/QP_S_VALUEFIELDS_PMK. The field ORIGIN of type /SCT/QP_ORIGIN (SSTRING) has been added to the structure /SCT/QP_S_VALUEFIELDS_VAL_PMK. Since the /SCT/QP_S_VALUEFIELDS_VAL_PMK is included in the structures /SCT/QP_S_GENER and /SCT/QP_S_GENER_PMK, the ORIGIN field must be deleted there. Extension category /SCT/QP_S_VALUEFIELDS_VAL_PMK changed to "arbitrarily extendable". Fields deleted from VALUEFIELDS_VAL_PMK: MODEREF, MANU, ORIGIN New structure VALUEFIELDS_VPS created with the fields: MODEREF, MANU, ORIGIN. Fields deleted from VALUEFIELDS_VAL: TDOBJEKT, TDID, TDNAME, TDSPRAS. New structure VALUEFIELDS_VAL_STX with the fields: TDOBJECT, TDID, TDNAME, TDSPRAS. In S_GENER and S_GENER_PMK and VALUEFIELDS the structure VALUEFIELDS_VPS included. In VALUEFIELDS the structure VALUEFIELDS_VAL_STX is included. In S_GENER the structure VALUEFIELDS_VAL_STX is included. | NOTE-3386 | ||
| Report TADIR_UPDATE: Changing the transport layer | The report /SCT/QP_TADIR_UPDATE is extended by the function that also the transport layer can be changed. | NOTE-3384 | ||
| Save | 1) In MODEL->DO_SAVE the export parameter ET_SAVED_ROOT was not always passed correctly.
2) Performance optimization: In MODEL->DO_MERGE_SAVE_DATA the existing data are deleted only if these already exist. 3) In CONTROLLER->DO_SAVE the FT as well as the AL was stored only after the COMMIT and thus only with the termination of the session. The FT is now stored by the MODEL, the AL by the CONTROLLER. 4) With BUS->SAVE and CONTROLLER->DO_SAVE the stored ROOTs are made available in the new export parameter ET_SAVED_ROOT. Since BUS->SAVE has an export parameter BASE, the known parameter EV_NO_AUTHORITY is also made available. 5) The no longer used parameter IV_FORCE_GENERATE in BUS->SAVE has been removed. 6) In VART->SAVE the export parameter from BUS was passed through. | NOTE-3383 | ||
| Deleting VART nodes with ECC docs | 1) There was sometimes an unauthorized error message when deleting an object that was used in the ECC document.
2) The work mode was not set correctly when loading data that was already partially loaded in the MODEL. 3) GUI->ON_MT_NODE_KEYPRESS: Change to the method GUI->DO_PROCESS_FCODE from 4) GUI->ON_ACTION_DELETE now calls GUI->ON_ACTION_DELETE_REL if the relation type is set accordingly. Thus, the deletion correctly distinguishes between the deletion of a node and a relation. | NOTE-3377 | ||
| VART class: event handler for error inheritance | A new method ON_NODE_OWN_CHILDREN_ERROR is provided in the VART class to override the inheritance of the error from child nodes. | NOTE-3375 | ||
| SD Release 2303 | A filter on VARTen, which are involved in the Syncmodell, was inserted. Changes made on the VBPA header are now also distributed to all positions. SYNC does not have to be reactivated after SAVE_DOCUMENT. | NOTE-3373 | ||
| Refresh of lastupdate | The precision of LASTUPDATE has been increased from DEC15 to DEC21(7). With this, time is recorded exactly to 10^-6 seconds. Thus, there is no longer a need to wait for the next second to start while saving. This increases the performance when saving. | NOTE-3372 | ||
| MAMBA Column Optimization | In MAMBA_VIEW the methods SET_COLOPT_MODEL and SET_FCAT_LAYOUT_COLCWIDTH_OPT are provided to change the internal flags COL_OPT in MAMBA-Model and COL_OPT / CWIDTH_OPT in the field catalog layout according to customer requirements. | NOTE-3371 | ||
| VART/BUS: Change of POSNR | The two new methods SWITCH_NODE_POSITION and SET_BASE_POSNR in the VART/BUS class can now be used to change the POSNR of those BASE entries for which sorting is activated. | NOTE-3370 | ||
| Restructure access to system elements | For accessing system element the following methods have been provided in TOOLS class: IS_SYSTEM_ELEMENT, GET_SYSTEM_ELEMENT_VALUE, GET_SYSTEM_ELEMENT_PRAEFIX. | If the $SYSTEM$ element was used, the element and its uses in object types must be renamed to /QPPD/STATUS. | NOTE-3364 | |
| Trigger for object type change | The object type in the GUI, which is now switched to from another node, from another object type or from the selection screen, is notified of a switch to itself via the new interface method ON_OBJTYP_CHANGE. | NOTE-3363 | ||
| Delete MAMBA lines with MODEREF=X | If a line is to be deleted by generation with MODEREF=X and no dynamic elements are present, then the line will not be deleted from the display. | NOTE-3358 | ||
| CUST->GET_NODE_HIERA_ELEMENTS: Filtering by object type | In the method CUST->GET_NODE_HIERA_ELEMENTS the TGRUELM entries are now fit by object type if parameter IV_OBJEKTTYP was specified. | NOTE-3357 | ||
| BUS: Support BDS | The BUS now supports the modification of BDS information. | NOTE-3356 | ||
| Factory: Redefinition of log class | The class for the log /SCT/QP_CL_LOG can be redefined via the factory. | NOTE-3352 | ||
| Redesign of the get_base_tab method | General revision of the GET_BASE_TAB and GET_BASE method to CL_VART. | NOTE-3341 | ||
| SYNC: Wrong entry found in mapping | If a differentiated mapping is stored in the mapping, the default entry is found first and not correctly the differentiated entry. The order of the mapping is now taken into account: Depending on the setting, other mappings can now be found. The order now wins before the default entries. | If necessary, adjust the mapping table in the synchronization, with adjustment of the sequences. | NOTE-3337 | |
| SYNC: Extension of the key number | The key field "Key number" has been extended from 2 to 4 fields. Old customizing entries for the /SCT/QP_TSYMAP table can no longer be used. | Old customizing entries for the /SCT/QP_TSYMAP table can no longer be used. | NOTE-3336 | |
| BUS: Changeover to single-level call | If a new object is created via BUS->CREATE/CHANGE/CREATE_CHILD/CREATE_REF, two internal CONTROLLER calls were used so far. This NOTE improves the logic so that only one call is used. | NOTE-3329 | ||
| BADIs: Reused instantiation | Performance improvement by using the same instance for BADIs.
Extension spot /SCT/QP_BADI with the following BADI definitions: /SCT/QP_BADI_CONTROLLER /SCT/QP_BADI_GUI /SCT/QP_BADI_LOG_VIEW /SCT/QP_BADI_MODEL /SCT/QP_BADI_NODE /SCT/QP_BADI_OBJTYP /SCT/QP_BADI_SEARCHHELP APPS: The following extension spots with BADI definition of the same name: /SCT/QP_BADI_PP /SCT/QP_BADI_SD /SCT/QP_BADI_VC | NOTE-3328 | ||
| APPBUS/SYNC: only consider the latest version of a QPPD object | When versioned QPPD objects are used, the /SCT/QP_CL_APPBUS~GET_ECC_LINKS_FOR_DOCS method now has a new parameter IV_ONLY_LAST_VERSION to get the rule with the highest version number (VVS). | NOTE-3326 | ||
| Indexes on database tables | Indexes were previously excluded for HDB. This NOTE enables all indexes for all types of databases. | NOTE-3321 | ||
| APP PP: Improvements 2303 | PP-APP can now be activated at plant/order type level.
Mapping is now done according to the sync model (no more static mapping). The /SCT/QP_GENSYNC utility generates the mapping entries automatically. Bug fixing in generation of DOCKEYS. When a production order is saved, now only the data linked to APPBUS is saved (and not all data loaded into the model as before). | NOTE-3316 | ||
| Global Generation: Messages&Performance | The functions around the global generation (GG) have been revised.
1) A pending GG no longer generates an error message after a BUS call or a GUI action, which causes a status change. Rather, when saved via the BUS, a new GG is triggered as needed. In the GUI, the user is shown a popup to decide whether a GG should be executed again. For this purpose, the methods around saving in the BUS/GUI/CONTROLLER have been revised. 2) If an object has a non-unique name when it is saved, the rule name is changed to the GUID in the BUS case. In the GUI case, the user is asked for a decision accordingly beforehand via a popup. 3) In MAMBA a new function was implemented, which triggers a notification because of a change only if the data or the messages have actually changed by the generation. To do this, the data and messages are compared before and after generation. 4) The way the GG processes the pending nodes has been performance optimized by first generating a node as long as it has a pending generation. This usually saves several passes of the generation. 5) The internal flag GEN_PENDING_DELAYED is now only set if GEN_PENDING is not set. | NOTE-3315 | ||
| VART: Creating an object with DOCTYPE/DOCKEY | When creating an object via VART->CREATE, it is now possible to include the DOCTYPE and DOCKEY. | NOTE-3311 | ||
| VART class: New event handler ON_DELETE_BEFORE | When checking whether a BASE entry can be deleted, the VART method /SCT/QP_IF_VART~ON_DELETE_BEFORE is also called with the BASE entry to be checked. | NOTE-3309 | ||
| Generation of short dump for generation methods | If the parameter GENERATION_METHOD_DUMP = 'X' is set, no message is generated in case of errors in the generation methods, but the program terminates with a short dump. | NOTE-3307 | ||
| FBD Functional Enhancements Release 2303 | New functions in FUP:
1) Data transfer to FBD with two additional options "Differences" and "Individual". The latter option calls the interface method /SCT/QP_IF_FUP~DO_FILTER_DATA. The individual data filter also allows to cancel the processing. 2) The data filter is now also applied when explicitly calling an FUP via /SCT/QP_IF_FUP~DO_PROCESS_FUP( ). 3) Only the data of an object is passed to the FBD. This also prevents a dump due to too much data. | NOTE-3306 | ||
| MM : Improvements 2303 | /SCT/QP_CL_MM_SERVICE: NEW service class for buffered reading of mara, marc, mkal, plpo, stpo.
Extension of the structure /sct/qp_s_mm_handle by WERKS and PSTAT, in order to be able to recognize better whether the view is cross-plant or not Various submethods created in /SCT/QP_CL_MM_GUI to simplify the redefinitions. | NOTE-3300 | ||
| Searchhelp status | The search help for the status /SCT/QP_SH_TJ02 is extended by the field ICON. The ISTAT field in the /SCT/QP_STATUS table is changed to use this search help so that CDS views or similar also benefit from this change. The DTEL /SCT/QP_ISTAT uses the SH /SCT/QP_SH_TJ02. | NOTE-3296 | ||
| MAMBA: Update net data | The updating of the internal fields MANU, MODEREF, MANDATORY in the structures VAL/PMK from the MAMA line is only done with this NOTE when saving and no longer when determining the original data. | NOTE-3294 | ||
| APP PP: Release 2303 | The entire APP PP has been refactored. | All implementations of the APP PP must be adapted. | NOTE-3291 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | BUS->READ Performance | Reading with BUS->READ has been accelerated by filling the parameter ET_ITEMS only if it is also SUPPLIED. | NOTE-3388 | ||
| MAMBA VIEW: Grid Refresh | The ALV is only updated when ALV-relevant changes occur. | NOTE-3344 | ||
| CUST-Service Performance | The construction of elements for each hierarchy level has been accelerated. | NOTE-3313 | ||
| BRF+ mapping inperformant access to customizing | Slightly increased memory usage. | NOTE-3303 | ||
| BRF+ Read application and function of DB | It can happen that applications have to be entered in Customizing on a system that do not exist in BRF+ on this system. This leads to the fact that when using the old BRF+ method /SCT/QP_CL_BRF_COM->GET_AP_FU_INFO_FROM_DB the selection from the DB is executed too often because the negative results are not buffered. | NOTE-3302 | ||
| Performance CL_VART->GET_DATA_BASE_FROM_ORIGIN | Better performance for the method CL_VART->GET_DATA_BASE_FROM_ORIGIN | NOTE-3299 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | TECHM: Reset M_RANGETYPE | The M_RANGETYPE field was not reset correctly. | NOTE-3400 | ||
| Determine node data of objects | The | NOTE-3397 | ||
| ARC: Deletion indicator of the archived node is not removed in the archive | The status marked for deletion is now correctly removed if data is written into the archive. Because of this the automatic deletion report is working aswell. | If archiving is already in use, consider aligning with Z-Coding to prevent possible conflicts. | NOTE-3394 | |
| TOE short dump when comparing constraints with arbitrary valid values | -If a value has an arbitrary validity, range type = ~~, then a short dump occurred in TOE when comparing CONSTRAINTS. | NOTE-3390 | ||
| Node checks on nodes that are not changeable | The node check by the methods NODE->CHECK_DATA is only executed if the node is also changeable. This is ensured by the method MODEL->IS_BASE_CHANGEABLE. E.g. with the deletion of the node this was checked again by CHECK_DATA, which led possibly to a status change on another node of the same object. | NOTE-3387 | ||
| SHMO: Deleted nodes | The SHMO returned an object that was still buffered, even if it had already been completely deleted from the database. The error did not occur if only parts of the object were deleted. | NOTE-3385 | ||
| BUS: Guessing logic | Errors occurred in the guessing logic in the BUS under the following conditions:
If a new object is created with the BUS and at the same time elements are included in the IT_ITEMS parameter without specifying identifying information (no GUID, VNR, etc.), which are only available on the header, then errors occur when processing VAL/PMK entries. The rate logic for STX entries has been adapted to the logic for VAL/PMK entries so that the identifying information is also correctly taken into account. | NOTE-3382 | ||
| HEADER: Processing changes | When BUS->CHANGE to the header data, the request is not processed correctly: #INITIAL# does not lead to the deletion of a value. An empty value in the request must not lead to any change in the object type. | NOTE-3381 | ||
| MAMBA: Takeover ROWGRP | If the | NOTE-3380 | ||
| CUST->GET_NODE_HIERA_ELEMENTS: Filtering ROOT | The filter on ROOTS at the method CUST->GET_NORE_HIERA_ELEMENTS was not applied to the export parameter ES_ELEMENT_USAGE.
Further performance optimization of the method by building the internal buffer only on VART level. | NOTE-3379 | ||
| BUILDER dump | If the BUILDER deletes the BASE entries in the MT_BASE by the MERGE used, then the references in the MODEL, CONTROLLER; GUI, BUS are lost as a result. | NOTE-3378 | ||
| CONV: Wrong text ID | When converting numbers and violating the rule on maximum decimal places, an incorrect text was used for the exception. | NOTE-3369 | ||
| Delete relations | If an object with a BOM relation is copied in the GUI in global workmode and the copied BOM relation is to be deleted in the resulting object, an error occurs. | NOTE-3362 | ||
| MAMBA: Search help with wildcard produces conversion error | An input with special characters before a search help is called can sometimes lead to superfluous conversion errors. These conversion errors are based on the initial input with special characters and not on the results of the search help. | NOTE-3361 | ||
| TOE: Clear the memory after deleting a node | The internal TOE memory was not properly freed from node data that has already been deleted. | NOTE-3360 | ||
| Vart method /sct/qp_if_vart~get_grid_grouped returns wrong results | Incorrect assignments of rows (RowGrp) to the elements of the condition. | NOTE-3354 | ||
| MAMBA-VIEW: Hide/show elements | Setting the property "Visible"/"Not visible" did not work properly when only these properties and no value was changed. | NOTE-3353 | ||
| BUS->CHANGE called always notify_changed() of Header object type | A call to BUS->CHANGE, even without changes to the header, had always triggered the change notification. The notification is now triggered only when there were actual changes. | NOTE-3351 | ||
| FDM: Delete nodes | The display in FDM was not updated when nodes within the object were deleted. | NOTE-3350 | ||
| Drag&Drop: Too many objects displayed/loaded | If nodes with non-original relations are created by drag&drop, which refer to other objects that are not loaded and/or not displayed, these objects are loaded or displayed after drag&drop. | NOTE-3347 | ||
| BRF+ v1 Error | 1) The interface of the /SCT/QP_CL_BRF_MAIN class, /SCT/QP_IF_BRF_MAIN, was not consistently used to instantiate the variables. This resulted in dumps.
2) When displaying the results from the DOG, dumps occurred because the different variables used to hold the view classes were incompatible with each other. | NOTE-3346 | ||
| TEXT: Check in display mode | The checks were performed during initialization in display mode. | NOTE-3342 | ||
| MAMBA: No data update in display mode | If the MAMBA MODEL changes, e.g. by a generation or by logic in another node, and the object or the node is in display mode, then the display is not updated. | NOTE-3339 | ||
| LOG: Initialization of the message texts | When initializing an existing object with messages, the message texts were not built at the node data. | NOTE-3338 | ||
| TOE: Superfluous checks | TOE performs checks for elements that are not TOE-relevant. | NOTE-3335 | ||
| FDM_VART : Changes are applied to an incorrect target | SYNC-Changes were under certain circumstances applied to the wrong target object | NOTE-3334 | ||
| IDOC: INFO writting | If after posting the IDOC the INFO records are written with a user who has set the global workmode, the update of the IDOC records fails because of a missing workmode at the BASE entries. | NOTE-3333 | ||
| Dump at FREE | If several objects are loaded, which are linked to each other, and are to be deleted from memory at the same time, a dump can occur randomly when objects are deleted from memory that still have dependencies loaded. | NOTE-3332 | ||
| SD: Dump in case of missing permissions | If the permissions are not set correctly, a dump will occur when creating the sales order. | NOTE-3331 | ||
| Tools: Converting Timestamp | Conversion from date/time/time stamp/time zone to date/time/time stamp/time zone does not work properly. | NOTE-3330 | ||
| APP MM - Copy from reference doesn't work | While creating a new material master using a reference, specifications were not always created when the Sync-action COPY was customized. | NOTE-3327 | ||
| Versioning Release 2303 | Node sequences are not transferred when creating a new version.
Dissolution date can now optionally be passed when creating versions. Further performance optimizations. Dump during substitution fixed. | NOTE-3322 | ||
| TECHM: Duplicate data | If an object type of the type TECH_ABSTRAKT has a vertical element group, then the method GET_ORIGINAL_DATA of the object type also erroneously returns the data of the primary reference. This can possibly lead to duplicate data if this node is used to create a new node. | NOTE-3320 | ||
| Dump on change of VART group node | When the group node for specification types was set to change mode, a short dump occurred. | NOTE-3319 | ||
| Mamba: Conversion of certificate unit | An incorrect conversion has been carried out on the element "certificate unit" (field altzeugeinh ). | NOTE-3318 | ||
| SD: Selection of incorrect objects at VBAK level | After a sales order was created and saved, the wrong QPPD objects were selected at VBAK level. | NOTE-3317 | ||
| Numeric default values in BRF+ with wrong format | Error messages occur if default values are used although the value is correct. | NOTE-3314 | ||
| BUS->LOAD doesn't always load | Under some circumstances, the specifications selected by VNAME/VART may not always be loaded | NOTE-3312 | ||
| Translation corrections release 2303 | Texts and translations were adapted. | NOTE-3310 | ||
| VART class: resetting the buffer | When deleting nodes, the buffer of the VART class was not reset. Therefore, values of already deleted nodes were returned. Due to the central use of the VART class, this can lead to inconsistent behavior, e.g. with BRF+, generations, customer programs.
| NOTE-3308 | ||
| SD/PP/ME: "Ghost objects" | If ME or PP documents are stored with reference to SD documents, deleting data from the memory too early will result in "ghost data", i.e. objects without correct reference to ECC documents (empty DOCKEY/VNAME). | NOTE-3305 | ||
| Jump to QPPD objects | The jump to QPPD objects did not work properly anymore. | NOTE-3304 | ||
| PP: Wrong costing number for duplicate materials | If a material occurs more than once in the BOM explosions, the first costing number is returned in the second call. | NOTE-3301 | ||
| NOTE-3298 | ||||
| BRF+ Mapping System Fields | Incorrect assignment of system fields from header parent nodes and especially the WERK field. | - | NOTE-3297 | |
| TECHM_DUO: Long text change | After changing a long text using the button in the GRID, the node data was not updated correctly with the data from the object type. | NOTE-3293 | ||
| GUI-TYP "GUI" vs "BUS" | Although the QPPD Cockpit was started via the BUS, the internal GUI type indicator is still set to "BUS" and not to "GUI". Possibly the wrong activity profile was applied as a result. | NOTE-3292 | ||
| BRF+ Error during transfer of LFDNR to BRF+. | When mapping to the QPPD, the values are not mapped correctly. | NOTE-3290 | ||
| MAMBA: TDNAME is not taken over externally | The TDNAME on the element is not taken over in case of external change. | NOTE-3044 |