NOTE-3059

Certificate Template created new

Template certificate writing for metal industry is available. The functions are:

Certificate monitor for monitoring and worklist of pending certificates.

NOTE-3046

CUSTRPT: Selection screen extended

A selection option for the element has been added to the selection screen of the customizing analysis.

NOTE-2532

Plausibility check and searchhelps of element values for the DDIC fixed values domain

With the new class /SCT/QP_CL_TOE_DDIC_DOMAIN it is now possible to assign a SAP domain with fixed values to a QPPD element.
The pausiblity check and value help is then performed using the SAP domain values.

NOTE-2522

TOOLS: Splitting Range Interval

NOTE-2518

Plausibility checks and searchhelp of elements with QPPD-Systemelements

The system fields Spec.-type, Itemtype, Spec.-group, Hierarchy and Spec.-block of the current Specification can be used for plausibility checks and search helps for elements.
Elements /SCT/VART, /SCT/VGRP, /SCT/VTYP, /SCT/VBLOCK, /SCT/HIERA within Objecttype SPACE will be created. In the application (VART-class) these elements can be accessed.

The elements /SCT/VART, /SCT/VGRP, /SCT/VTYP, /SCT/VBLOCK, /SCT/HIERA must be created, which then can be accessed in the application (VART class). These are already included in the current standard delivery.

NOTE-2499

Progress bar: show speed

Display of processing speed can be optionally added. No effect on existing uses.

NOTE-2483

Extend element to 20 digits

NOTE-2477

VC : Pass numbers as number

In the VC-Sync module there are now 2 variants for synchronizing numbers:
Either the VC characteristic is synchronized as text: Then the output format of the characteristics incl. unit is transferred into the QPPD field. E.g. "13 000,000 kg". Or only the pure number is synchronized in a QPPD-DB compatible format without unit, without 1000 separator, with dot as decimal separator. E.G. "13000.000".

To implement the 2nd option (new variant), the method CHECK_SYNTAX_CABN must be called with the additional parameter IV_NUMONLY = abap_true.

NOTE-2472

TOE: Trace for BRFplus functions

BRF+ is called directly from the QPPD generation and from the QPPD TOE. Thereby with this NOTE the existing user settings for the BRF+ call (Active + Mode) are now taken into account to use the BRF+ own tracing functionality. This BRF+ tracing function is not the QPPD action log. Additionally, with this NOTE all BRF+ calls from the QPPD have been centralized in a single class (/SCT/QP_CL_FDT).

NOTE-2467

NOTE-2463

Enhancement QPPD Datastructures

The introduction of table /SCT/QP_NUM simplifies several evaluations, especially within CDS-Views for numerical values. Numerical values from tables /SCT/QP_VAL and /SCT/QP_PMK are being displayed in the FLTP and DEC format. In addition, the values are also stored in SI. MIN and Max are adjusted by the range type. Comparisons with >= and <= are now possible. Additionally it became necessary to adjust the QPPD Standard IDOC as the adjustment of the lengths to 20 digits for Spec.types, Itemtypes and Objecttypes as well as the extension of the /SCT/QP_VAL, /SCT/QP_PMK and /SCT/QP_STX table have been done. Also the /SCT/QP_VAL and /SCT/QP_PMK table were extended by 10 flags, which can be used customer-specific.

Translated with www.DeepL.com/Translator (free version)

The /SCT/QP_FILL_QP_NUM report allows to regenerate the /SCT/QP_NUM table.

NOTE-2459

TOE: Plausibility check and search help for element values

New TOE version 2.0 with additional features:
- Context related definition of valid values
    - in the form of lists and placeholders (*) on the tabs for V-type
      or domain
    - Use of BRF+ rule with predefined BRF+ functions.
      Support of input of element values by search help exit of
      TOE values.
    - Defaults and mandatory field control
    - Individual error message
    - Individual control of errors and warnings
- Display of contexts to the element. Marked and callable
  by hotspots to the element and element name in the grid.
- Customizing TOE contexts. Individual control of ABAP classes with
  parameters analogous to TOE control

NOTE-2449

Create VART as primary reference

A VART can now be used as a primary reference

NOTE-2447

Additional functions on VART

New function "Additional function on the VART".
Shortening of field ACTION from 70 to 40 characters.

NOTE-2441

Reorganisation item number

the /SCT/QP_REORG_VNR report allows you to move the VNR for regulation types and categories to a different number range. The new number range can be specified in the report. The existing number range counters will not be taken into account. In the specified number range, the highest value is determined and increased by 1. The value is not adjusted in the number range counter. This must be done manually afterwards. The last assigned number is output.
All affected tables are corrected.
In addition, element values that refer to a VNR or VVS are also corrected.

NOTE-2434

Allow nodes without specification no.

It is now possible to create nodes without VNR. For this purpose, the number range number is to be left blank in Customizing.

NOTE-2429

TOE: Context Analysis

Improved TOE analysis options: In Mamba, clicking on a hotspot at ELEMENT or ELEMENTTEXT now invokes TOE context analysis if it has been used.

NOTE-2426

MAMBA: Detailed action log messages for generated values

Improved analysis options with the action log.

NOTE-2423

BUS/CONTROLLER: Optionally do not execute garbage collector

By default, the garbage collector is still executed in BUS->FREE. This can be deactivated via a new optional import parameter.

NOTE-2413

MAMBA- TOE : Allow also positive news

TOE check methods can also generate positive messages (e.g. warnings)

NOTE-2410

MAMBA: Control of "mandatory" property within SCREEN methods

Changing field property "mandatory" within customer-specific generation has been adapted. For technical reasons, it is no longer possible to change the mandatory field property using a SCREEN method (methods with a special prefix, set in C10).

In case (customer-)implementations exist, they must be adapted and changed to normal generation methods without the special prefix.

NOTE-2402

Logging of BRFplus messages

New possibilities for logging BRFplus messages in QPPD logics and during function execution.

NOTE-2397

Deletion of non-changeable items allowed

Subnodes that are not ready for input may now also be deleted. Customer implementations may have to be adapted to prevent deletions of nodes that are not ready for input.

NOTE-2391

GUI: SAVE Button

Changed objects can be saved via the SAVE button in the TOOLBAR as well as via the statement of the same name in the context menu for the object. Up to now, the SAVE action was used in both places. For technical reasons, the context menu will now use the SAVE_OBJECT action instead of the SAVE action in the future. Therefore the profiles/activities must be checked in the C15. The background is that the action SAVE_OBJECT is offered in the context menu in the future only if the object concerned was also changed. The SAVE button in the TOOLBAR, on the other hand, is always available, since changes could exist to objects that are not currently visible in the tree. For the EXTERNAL profile, which is used in FDMs outside the QPPD Cockpit, both SAVE and SAVE_OBJECT actions must be excluded, because saving is triggered from the external application.

NOTE-2386

SD: BUS profile redefinable

The GUI class for SD now contains a separate method for profile determination.
This method can be redefined and allows the BUS functions that are called as part of the QPPD-SD connection to be controlled with a customer-specific profile.

NOTE-2372

MAMBA: MANU indicator for new lines

Currently, when creating a new row in the GRID (with element, without value), the indicator (MANU) is always set that the row was changed manually (MANU = X). This prevents the generation from determining a value/default value. In the future, this indicator will no longer be set when a row is created manually in Mamba (MANU = SPACE). The indicator will only be set (MANU = X) as soon as the user maintains a value. If the user does not maintain a value, the flag does not remain set (MANU = SPACE) and the element may not be saved if the SAVE_EMPTY setting is not set accordingly.Customer redefinitions and implementations must be checked to determine whether this flag (MANU) controls functionality in customer-specific generation methods. These must be adapted if necessary.

NOTE-2370

SYNC MM : Connection QPPD material master

Enables QPPD specifications to be linked to the SAP material master ( analogous to the link in SD ). Display of the link on a customer-specific tab with fast entry in the material master.

NOTE-2356

ECC DOC: Creation of ECC document rules without direct linking

Extended possibilities for handling ECC VART objects: Sometimes it makes sense to create an ECC document in the QPPD already before a first link. For this purpose there is now a CREATE method at the corresponding VART class in the interface IF_ECC with suitable parameters IV_DOCTYPE and IV_DOCKEY.

NOTE-2340

NOTE-2325

NOTE-2303

Extend element text from 40 to 80 characters

The data element /SCT/QP_ELEMENTTEXT has been extended from 40 to 80 characters.

Data element /SCT/QP_ELEMENTTEXT

NOTE-2292

NOTE-2289

NOTE-2286

NOTE-2278

NOTE-2274

NOTE-2266

NOTE-2262

Enhancement of Specification-Comparision

Bug fixes and function enhancements in the Specification-comparison. No negative effects for the customer.

Check all redefinitions within the Specification comparision.

NOTE-2259

Extension class ECC documents /SCT/QP_CL_ECC

The class is extended by various methods

NOTE-2213

TOOLS static methods

The /SCT/QP_CL_TOOLS class has been changed to the interface (IF) /SCT/QP_IF_TOOLS. ALL customer implementations may need to be adjusted.

All variables which are typed with /SCT/QP_CL_TOOLS must be changed to /SCT/QP_IF_TOOLS. All static calls must be changed to instance calls.

NOTE-1864

NOTE-1246

NOTE-2484

TOE: Extension of the check to min and max (/SCT/QP_VAL table and setpoints of /SCT/QP_PMK table)

Extension of the plausibility logic to the VALUE_MIN and VALUE_MAX fields. Additional possibility to check setpoints of the PMK table (example class /SCT/QP_CL_TOE_PMK).

NOTE-2396

NOTE-2268

NOTE-2257

NOTE-3002

Drag&Drop: Create node via template

Create via drag & drop no longer works. Follow-up error NOTE 2530

NOTE-2533

LINKS with primary/secondary references are not built correctly

Links to item types with primary references out of the hierarchy are not built correctly. The primary reference has not been loaded in Base, the data of the link is incomplete.

NOTE-2530

MODEL: Create node via template

If a new node is created as a copy of another node, then the data of this copy template was not always taken into account.

NOTE-2524

Customizing columns to column group no longer works

This note corrects a customizing problem where the specification of the language was mandatory in the column group definition.
When saving, the message appeared: " " is not a valid language".
This is now no longer the case. If the language is not maintained, then the logon language applies.

NOTE-2521

SYNC: Data does not always appear in the fast data entry : Multiple Models

When displaying the fast data entry, not all data was always displayed correctly if the affected sync objects and multiple sync models were involved.This corrects the misbehavior.

NOTE-2517

Status: Deleting old entries from status management in SAP standard tables

During a release upgrade, when the changeover from the old status to the new status management takes place these SAP system status entries are still retained. After changeovers, they can be deleted via this transport request.

NOTE-2515

BRFplus: Formulas

BRFplus: Formulas

NOTE-2513

Adjustments DDIC

The domains /SCT/QP_GENCLASS and /SCT/QP_ICON are deleted.

NOTE-2509

BUS->CREATE_VERSION from multiple positions

Versioning of multiple positions via BUS->CREATE_VERSION does not work.

NOTE-2506

MAMBA Copy master data by transaction data

If master data is copied to transaction data and the dependencies to dimensions (vertical elements with ROWGRP) are resolved, then the transaction data was incorrectly created with ROWGRP. This has negative effects on subsequent actions in the GRID. E.g. copying rows, creating new data sets as well as later processing by other applications.

NOTE-2502

TEXT: Copying nodes with references

If a new position is to be created in an object with the BUS method DO_CREATE_COPY, but this object was not loaded before, the creation of the position is not executed correctly.

NOTE-2498

APPBUS: Jump to ECC-linked original instructions

Ability to jump by means of single method call.

NOTE-2496

Archiving: Transfer/ Takeover of adaptations from VA

Correction of the formatting of NODET entries when writing archives.

NOTE-2492

SYNC_SD : References to SD tables not bound

If the sales order is changed by several calls of BAPI_SALESORDER_CHANGE (assumption), then internal reference in CL_SYNC_SD may not be bound anymore. This leads to a short dump.

NOTE-2489

SYNC_SD : dynamic detection if S4 or ECC

When using the standard SYNC SD class on a SAP S4 system, a shortdump occurs because the SAP internal structure IVBAP in SAPMV45A has changed (the HANDLE type GUID_32 field has been added).

NOTE-2487

SYNC_QPPD : Deregister objects on deletion

SYNC in sales order: If an Item is deleted and recreated again in a second step, for which a SYNC existed, a shortdump may occur, because the internal memory in the SYNC was not reset correctly.

NOTE-2485

BRFplus: Runtime optimization when referencing context data objects during function call

Runtime optimization for function calls.

NOTE-2481

CUST: Userindependent settings

The settings for activating the action log have been moved to transaction C15 "Activity profile". This contributes to a better overview and improved performance.

The settings from the /SCT/QP_TUSRI table for activating the action log must be moved to transaction C15.

NOTE-2478

CL_SD_GUI : Instantiate FDM View with the Factory

This note allows you to redefine the view class of the fast entry in SD by means of customizing (Basic Settings, Classes Factory) depending on the customer.

NOTE-2474

LOG saves temporary ROWGRP

When saving the data, temporary ROWGRP are replaced within Mamba by real ROWGRP from the number range. However, the logic does not work on the LOG object type if the "KEY3" field contains a temporary ROWGRP. The replacement is not performed correctly and the error message cannot be assigned when loading the object.

NOTE-2469

NODE_TEXT: FCAT

The FCAT was not displayed correctly when switching from display to change mode.

NOTE-2466

NOTE-2458

MAMBA: Wrong deletion of data

If elements are added, deleted and saved via the BUS in MAMBA and then the user sees this object type for the first time in the GUI, entries are mistakenly deleted from the object type.

NOTE-2456

QPPD Settings : Search Help Default Tab

The search help for selecting the default tab in the user settings was incorrect. A search help with the numbers 1 to 8 is now offered.

NOTE-2453

MAMBA : Conversion error for dyn-columns not always deleted

The syntax check for values on vertical elements was not performed correctly. This concerns e.g. migrations via BUS->CHANGE. Furthermore syntax errors (conversion errors) on vertical columns were not reset correctly when the values were deleted.

NOTE-2450

TECHM_DUO: Changes are not always saved

Corrects the possible loss of data when saving domains after the selected languages have been changed.

NOTE-2445

NODE/HEADER: Origin is not saved

Original origin will be written to nodes.

NOTE-2442

SYNC : QPPD changes are not always saved when 2 sync models are active

Improved detection of changes when multiple sync models are active.

NOTE-2437

NOTE-2435

Conversion errors disappear during copying

Values are syntactically checked when nodes are copied/versioned.

NOTE-2431

MAMBA: Dump when resetting error messages

Dump when resetting error messages within MAMBA

NOTE-2422

NODE: Messages from node check not reset

Errors during node checking incorrectly persist and are not reset. This error affects the error message that is generated when the method could not be executed on the specified class and results in a class-based exception. It does not affect the error messages from the customer implementations.

NOTE-2420

DOG: Avoiding endless loop in recursive contexts

With increasingly complex, more deeply nested context structures, an infinite loop could occur in the transaction /SCT/QP_DOG.

NOTE-2416

MAMBA: Generation of initial data does not execute a check

NOTE-2412

MAMBA: Assignment of ROWGRP for PMK references

If PMK data is initially displayed and this node is used as reference in another node and the same elements should also be initially displayed, they were erroneously displayed twice.

NOTE-2407

SYNC: Unification of the SYNC implementation

The main key for detecting sync objects was ROOT_GUID-GUID-OBJEKTTYP, it is now changed to OGUID-GUID-OBJEKTTYP. Safer detection when VART are linked (in this case OGUID <> ROOT_GUID).

NOTE-2405

GUI->DO_SYNC_ACTIVE Shortdumps on external calls

See also NOTE 2154: If the ACTIVE BASE was changed by the controller, this will also correctly be displayed (with NOTE 2154 implemented). However, BASE entries were also displayed that were not intended for being displayed (DISPLAY = ABAP_FALSE).

NOTE-2400

Consistent versioning: 2 released versions simultaneously

Correction of the problem that if the current version is released via ACTIVATE and the previous version has not been loaded, the previous version remained in the RELEASED status.

NOTE-2394

NOTE-2389

NOTE-2387

NOTE-2383

NOTE-2381

The status in the tree changes if there are faulty boms

If an object was loaded both as a stand-alone item and as a BOM, an inadvertent status update can sometimes occur when the user switches between the two nodes.

NOTE-2378

NOTE-2376

NOTE-2374

NOTE-2366

NOTE-2362

NOTE-2359

NOTE-2357

MAMBA: Dump for long text on element

If the long text was set on an element, a dump occurred in MAMBA GRID, the long text was not evaluated.

NOTE-2354

NOTE-2352

MAMBA : Save filter criteria in layout

Saving the filter criteria in the GRID did not work properly. With this NOTE the GRID gets a new functionality: If a layout variant is used, the name of the variant is displayed above the GRID. This makes it easier for the user to see if certain columns and/or values are not displayed or are displayed differently.

NOTE-2349

NOTE-2347

TOE Default: Default values with alternative context name can not be determined

When using the default values via the GET_DEFAULT_ON_CONTEXT method of the generation class with alternative context, no values were returned. The generation method had assumed that a technical object existed for the context, but this was not necessarily the case. The combination of the same name in element and context caused problems.

Check any existing customer-specific default generation methods.

NOTE-2343

NOTE-2339

Inforecords: Short dump SQL-DB deadlock

Short dumps can occur due to a deadlock situation if info records are written. This happens if the objects are used in other objects via referencing or BOM.

NOTE-2337

NOTE-2333

JUMP: Call of /SCT/QP_DO_JUMP_TCODE faulty

Extension of the PARAM structure (used in within calls of other QPPD objects and/or transactions)

NOTE-2330

NOTE-2328

Global generation: Endless loop

This note corrects an infinite loop during generation.
After successful generation, the STATELM flag is changed. Subsequently, the check methods detect an error (the generated value is not correct), causing STATELEM to be changed again. Because generation on this tab is constantly restarted by global generation, constantly changing STATELM causes an infinite loop.
This note corrects the problem so that STATELM will no longer be changed by the generation.
The generation only is able to change STATGEN, the checks only change STATELM.

Since the logic for changing the STATELM field has been changed, it must be checked in customer implementations for Mamba whether adjustments are necessary. This is necessary as the status of this field may be different after generation.

NOTE-2326

Longtext incompletely read

Sometimes the first line of the long text was not returned by the data service.

NOTE-2323

NOTE-2320

NOTE-2318

NOTE-2313

NOTE-2309

NOTE-2307

NOTE-2305

NOTE-2301

NOTE-2298

NOTE-2296

QPPD data is lost when a KDAUF pos is deleted and created again

When an item is created, deleted and created again from the sales order, the data of this item was not saved correctly. A data loss occurred.

NOTE-2293

BRF+ V1: Dumps due to lost node reference

Fixing dumps after deleting nodes for complex constellations of rules in memory.

NOTE-2284

The "Collective-release" keeps the subnodes as changeable (despite CHILD-workmode)

After the action "Collective release" the workmode on the subordinate nodes of an object was not always set correctly. This means that nodes were incorrectly changeable.

NOTE-2281

NOTE-2273

NOTE-2271

NOTE-2265

NOTE-2256

NOTE-2137

BRFplus: Logging in log incomplete

After generating messages in a BRF+ rule, they were not always correctly displayed in the QPPD log at the node.

NOTE-1719

MAMBA: Wrong GRUELM references in COL table if several object types use the same column group

Certain customizing constellations could lead to incorrect display of columns in the object type.