NOTE-3570

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-3584

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-3577

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-3572

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-3556

Program for downloading texts

The program /SCT/QP_DOWNLOAD_TEXT allows you to download texts.

NOTE-3548

Certification Release 2409

Extensive changes were made to the entire QPPD in order to obtain the certificate.

NOTE-3581

ECC documents: memory consumption and performance

When ECC documents are initialised, the detailed data (VAL, PMK, texts, documents) are not created.

NOTE-3555

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-3586

Action Log Shortump

When displaying the action log, a short dump may occur under certain circumstances.

NOTE-3580

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-3575

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-3573

Fehler

BRF+ functions distributed via DSM (Decision Management System) generate a short dump when a function is called.

NOTE-3568

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-3566

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-3564

CUST-Service Freigabe 2409

This NOTE contains corrections to the CUST SHMO.

NOTE-3560

BUS->CHANGE: Call without changes

If the BUS->CHANGE is called without changes, the NOTE-3329 prevents any changes from being made to the object. However, it is intended that the resolution date can be set or the BUILDER can be started at the root node.

NOTE-3553

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-3550

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-3547

BUS: CREATE_REF

An error occurs with BUS->CREATE_REF if the PARENT node is the ROOT.

NOTE-3545

TEXT: Endless loop

An endless loop could occur when generating texts.

NOTE-3543

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.