NOTE-3287

Enhancement SAP standard field plant

in the QPPD, the Plant field is included at the node.
The following adjustments are implemented:
1. New header screen with consideration of the plant
2. Extension of the authorization objects and check with consideration of the plant
3. Provision of the plant in the BRF+ set of rules and TOE checks
4. Idoc Processing is enhanced by plant

A new object type is created at the node analogous to the header object Header with dynpro 8000. This object type is assigned to the node. The field can be maintained in the header. An extended authorization check is carried out.

NOTE-3284

TOE Extension by min/max and unit

Via TOE/TOEC now additionally the min/max values and the unit can be set by default.

NOTE-3274

SYNC in the background

New function to run the SYNC in the background via FUP.

NOTE-3262

/SCT/QP_TECHM_LONG_TEXTS: Fixed font

Long texts can be displayed using a fixed (monospaced) font.

NOTE-3258

TOOLS: Method to determine if S/4

New TOOLS method IS_S4 to determine if the current system is an S/4 system.

NOTE-3249

Revision interaction GUI with CONTROLLER

The interactions of the GUI with the CONTROLLER have been revised. This concerns the handling of the FCODES/ACTION to the controller. The previous methods have been encapsulated. Explicit methods of the CONTROLLER are used.

NOTE-3242

Missing change documents

New fields are recorded:
Flags in VAL and PMK
actvalreq and TDNAME in VAL

NOTE-3289

save change documents using archived Data

Better performance by saving change documents coming from archived data

NOTE-3240

CUST-Service: Perfomance

Performance improvement when changing values via BUS.

NOTE-3285

SPLITTER: No data transfer

If the TEXT object type is used in the SPLITTER and the SAP LOGON and not the BUSINESS CLIENT is used, the data is not transferred.

NOTE-3281

After duplicating, the new node does not appear in the tree

After duplicating, the new node does not appear in the tree

NOTE-3278

Wrong VART-class for builder

In some cases, the wrong VART-class was used and no builder functionality was executed

NOTE-3275

TOE: Valid entries are ignored in the search-help, and displayed as incorrect

Some valid context-dependent values were sometimes displayed as faulty ( when the value was checked ) and omitted in the search-help

NOTE-3269

4 eye principle bug at changing status

It is not possible anymore to change values and release a specification at the same time. The check now not only checks the last person that changed the specification it also checks on open not yet saved changes.

In customer systems, specifcations which have the 4 eye principle activated aswell as generation classes implemented should be checked. It could be possible that the check on IS_CHANGED could be false positive. Here it could be necessary to implement customer specific coding.

NOTE-3266

Constraints check processed at wrong element

in some cases, constraints-checks were omitted, leaving error messages although the value should have been correct.

NOTE-3261

ELEM: Interface for Customizing

If the element service is not delivered, an import error occurs because the search help /SCT/QP_CL_SX_TS refers to the class of the element customizing service, which is not delivered.

NOTE-3257

VART class: GET_GRID_GROUP method determines incorrect links for single values

When grouping grids using the /SCT/QP_IF_VART~Get_grid_grouped method, linked RowGrp will return incorrect linked RowGrp,under the following conditions:
1. elements to be grouped contain scalar value (value instead of value_min and value_max)
2. there is no record in the data to be grouped

When calling the method, the parameter that should check single values when merging, the call is adjusted:
it_element = value #( ( element = 'XXX' type = /SCT/QP_CL_CONST=>OUTTAB_TYP_NENN ))

NOTE-3254

APP_BUS->CREATE_ECC_LINK generates an exception in the event of an abort error

When a faulty specification is linked with APPBUS, an exception is thrown, even if the link is successfully created, just because the specification is faulty.
An exception should solely be thrown when the linking was not successful.

NOTE-3251

MAMBA ICONs

The ICON was not set correctly when a value was changed manually.

NOTE-3248

MODEL: Initialize BASE entries

If a node was created that created several BASE entries, then not all BASE entries were always correctly initialized.

NOTE-3246

MAMBA does not reset error messages

The LOG messages were not reset before an element was checked for plausibility. This led to erroneous setting/resetting of LOG messages.

NOTE-3238

MODEL: SAVE with SYNC

If SYNC is active when saving and changes an instance that has already been run through, there is a short dump due to DUPLICATE_KEY.

NOTE-3236

TOE check of deleted nodes generates nonsensical error messages

If nodes are deleted, a check of the element values is still performed and may lead to unnecessary errors in loggiin and status.