Main topics
Simplification and new version
As part of this simplification, parts of the customizing have been restructured or deleted. On the other hand, a new version of the QPPD is available with the release, which no longer supports certain features of the product. This new version can be installed optionally. Further information can be found here: Simplification and new version (R).TOE: New object for buffered database tables
STATUS: Enhancements to 18 statuses and 36 processes
Number range assignment in the hierarchy
APP SD
Synchronization of versioned rules
Button bar with standard SD functions
Various text adaptations/translation corrections in the languages German, English and French
New functions
S  | 
            Schlüssel  | 
            Zusammenfassung_en  | 
            Auswirkungen_en  | 
            Implementierungsanweisungen_en  | 
           
|---|---|---|---|---|
BRF+ version 1 and 2 disabled  | 
            With this NOTE, BRF+ versions 1 and 2 are no longer generally available.  | 
            The following adjustments are necessary to reactivate BRF+ v1/v2:   | 
           ||
Number range assignment in the hierarchy  | 
            It is now possible to define number ranges in the hierarchy.  | 
            |||
SD tab: Standard SD functions for items  | 
            The standard SAP SD button bar, which is displayed on the standard overview screen, is also available on the QPPD tab.  | 
            |||
Change documents Release 2309  | 
            Adjustments to the change documents:   | 
            |||
Extension of statuses and processes  | 
            The QPPD has been expanded to include customer statuses and customer transactions. A total of 18 customer statuses and 36 customer transactions are now possible.  | 
            |||
Simplification  | 
            As part of this simplification, parts of the customizing have been restructured or deleted. The documentation can be found in the DOC.  | 
            1. Execute Report /SCT/QP_RELEASE_2309_CUST.   | 
           
Technical changes
S  | 
            Schlüssel  | 
            Zusammenfassung_en  | 
            Auswirkungen_en  | 
            Implementierungsanweisungen_en  | 
           
|---|---|---|---|---|
Translating and cleaning up action codes  | 
            Translating and cleaning up action codes  | 
            |||
MAMBA: Ease of use  | 
            If a new line has been created in the GUI, it is then displayed and selected.  | 
            |||
Proof of use: Improvement of use  | 
            In the where-used list dialog box, the user selects the entire ALV row to determine which objects are to be displayed when the "Select" button is clicked. This NOTE also makes it possible to specify the objects to be displayed by selecting just one cell in the ALV tree.  | 
            |||
Authorithy group /SCT/ADM for admin-reports  | 
            The administration programs are now provided with the authorization group /SCT/ADM.  | 
            |||
SD fast entry screen to detail with filtering of current version extended  | 
            With the new optional import parameter in the SD_GUI->DO_START_QPPD method, only the latest versions are displayed when jumping from the FDM to the cockpit and not all linked versions.  | 
            |||
SD: Save ECC documents with handle if VBELN is empty  | 
            If a sales order is saved without VBELN, the ECC documents are saved to the new DOC types VBAKH/VBAPH/VBEPH instead of the DOC types VBAK/VBAP/VBEP. In this case, the data key is extended with the SD handle. In this way, the object data is not lost even though there is no order number yet. The data can then be corrected again using a further program /SCT/QP_EMPTY_VBELN.  | 
            |||
Collective version: Deactivation of checks  | 
            If elements are edited on an FDM, complex TOE checks may no longer work, as the elements are not used on the original object. This can result in incorrect error messages. The checks of the element values can be deactivated via the new flag SKIP_CHECK in MAMBA with a customer-specific redefinition.  | 
            |||
INFO writing Release 2309  | 
            In the class for writing the info records, the GET_FUP method can be used to return the name of an FUP with which the info records are to be updated. The report /SCT/QP_INFOWRITE can update the info records completely asynchronously or as if the objects had been saved (usually synchronously). The architecture of the INFO update has been revised and simplified.  | 
            The follow-up processes SCT_INFO_WRITE, SCT_INFO_WRITE_BG, SCT_INFO_MARK, SCT_INFO_REWORK must be set in customising.  | 
           ||
MAMBA: Administrative data for manual changes  | 
            If new lines were inserted, administrative data was written. However, this is not always correct. This NOTE corrects the behavior and allows rows to be added internally even without administrative data. For example, when creating empty rows.  | 
            |||
Class for generating transport request entries  | 
            The new class /SCT/QP_CL_TRANSPORT_ORDER makes it possible to add entries to transport requests.  | 
            |||
CDS Views  | 
            Standard views are provided for the QPPD for the use of ODATA services. These views are similar to the existing standard QPPD views.  | 
            |||
MAMBA: Recognition of changes  | 
            Change detection was encapsulated in a sub-method. This also makes the logic easier to redefine.  | 
            |||
BRF+ Mapping Default element values  | 
            A mapping to the hierarchy of the rule is defined via the definition of the input structures. The mapping searches for the corresponding node and finds the element values at this node. If this node does not exist, the entire structure is searched for. However, this is not always desired.  | 
            When calling the generation method brf_execute, the parameter IV_MAP_ELEMENT_DEFAULT = ABAP_FALSE must be set so that the parameters are not filled based on their name.  | 
           ||
Global generation Release 2309  | 
            When the objects are loaded indirectly by the BUS, the initial GG is executed even though this was suppressed by the caller. The parameter IV_SUPPRESS_GLOBGEN can now be used to specify externally whether the initial generation is executed.  | 
            |||
TOE Technical object for buffered database tables  | 
            The /SCT/QP_CL_TOE_TABLE object was previously only used to read in valid entries for the TOE values based on a table individually. Further use in the TOE context with BRF+ was therefore only possible to a limited extent.  | 
            |||
SD: Synchronization versioned specifications  | 
            With this NOTE, the fast data entry screen in the sales order only takes into account the latest version of the assigned objects: As soon as a new version is created for an assigned object, only the latest version is taken into account in FDM.  | 
            |||
FUP Release 2309  | 
            Under certain circumstances, using the queue buffer leads to errors when creating bgRFC queues. This NOTE deactivates the buffer. This NOTE also restructures the logic for creating the queue names and IDOC processing.  | 
            |||
Reload  | 
            Short dumps are generated when objects are reloaded under various circumstances. The reloading function has been technically revised.  | 
            |||
SYNC : Automatic determination of member's name in kemapping  | 
            The attributes mv_syobj_fdm, mv_syobj_qppd, mv_syobj_me, mv_syobj_mm, mv_syobj_sd, mv_syobj_vc, mv_syobj_info are now determined automatically.  | 
            Filling the attributes mv_syobj... in the constructor from the Z-Keymapping class ist not requierd anymore and should be deleted.   | 
           
Improvements
S  | 
            Schlüssel  | 
            Zusammenfassung_en  | 
            Auswirkungen_en  | 
            Implementierungsanweisungen_en  | 
           
|---|---|---|---|---|
Avoid unnecessary class instantiations  | 
            When the SD, PP or MM applications are started, many QPPD instances are created to check whether QPPD is active. This NOTE improves the behavior and reduces the number of instances.  | 
            |||
TOOLS->DO_SPLIT_RANGE: Too many comparisons  | 
            Diese Methode hat zu viele Vergleiche ausgeführt.  | 
            
Bugs
S  | 
            Schlüssel  | 
            Zusammenfassung_en  | 
            Auswirkungen_en  | 
            Implementierungsanweisungen_en  | 
           
|---|---|---|---|---|
MAMBA-VIEW: Update filter/expander  | 
            If only the filters have been updated in the grid, the display has not been updated.  | 
            |||
ECC->GET_LINK_INSTANCE returns the wrong VART instance  | 
            The ECC->GET_LINK_INSTANCE method returns the wrong VART instance.  | 
            |||
Translation corrections Release 2309  | 
            Correction of the English translations.  | 
            |||
MASS Excel Export Dump  | 
            In some cases during the excel export a dump happend, because MO_TOOLS gets incorrectly initialized. Now MO_TOOLS gets initialized correctly and the dump wont happen anymore.  | 
            |||
Copy  | 
            If a node is copied with its sub-nodes using drag & drop in the GUI and the target is a node where the item type matches but the hierarchy does not, copying is not possible.  | 
            |||
Log will not be aktualized, wenn no message are available  | 
            With the setting "Show log automatically = empty", the log messages were not always updated correctly when the node was changed.  | 
            |||
AUTH: Error during authorization check of the plant for /SCT/QPPD2  | 
            The authorization check for the plant returns incorrect results under certain conditions.  | 
            |||
SD: Error when processing additional data  | 
            The buffer table for the additional data was set up incorrectly.  | 
            |||
TOE: Incorrect conversion in the search help  | 
            When displaying the values in a TOE search help, the output was carried out with the wrong conversion routine.  | 
            |||
SYNC : Data is not always synchronized correctly  | 
            If 2 sync objects have returned a different value for the same element, e.g. generated value vs. manual value, or if this value is returned to the sync object that is currently sending it by synchronizing a value, then the data that has just been processed could not be reset correctly.  | 
            |||
BRF+: Search help for element values incorrect  | 
            The search help for element values in BRF+ did not work correctly if the name of the parameter did not correspond to the element name, e.g. because prefixes were used.  | 
            |||
CL_DATA->GET_DATA sometimes give 00000-Guid back  | 
            Under some circumstances, empty entries were given back.  | 
            |||
NODE: Initialize  | 
            A generation is carried out for a node. This creates a new node with a primary reference to this node. This results in a short dump TABLE_FREE_IN_LOOP.  | 
            |||
MASS changing values doesn't work  | 
            Changing values in the masschange-tool didn't work.  | 
            |||
MAMBA: Long text and icon are not always updated  | 
            Under certain circumstances, the long text (displayed as STX_TEXT) and the corresponding icon were not always updated correctly.  | 
            |||
Read BAPI READ objects  | 
            Error correction of   | 
            |||
IDOC Segment Header  | 
            The data in the IDOC segment HEADER was not transferred correctly.  | 
            |||
BRF+ Mapping conversion error using numerical values  | 
            Sometimes BRF+ returns numerical values in scientific format. This leads to aborts if the value is to be written to the QPPD.  | 
            |||
Workmode global does not work properly  | 
            Due to an error in   | 
            |||
SHMM: dump cx_shm_out_of_memory avoid  | 
            If no shared memory is available, an exception can be thrown after the attach_for_update when additional records are added. As this exception was not caught, this led to a short dump.  | 
            |||
BRF+ Elements with type time are used incorrectly  | 
            Bei Verwendung des BRF+-Typs "TIMEPOINT" wurde der Typ (Datum, Uhrzeit oder Zeitstempel) nicht festgelegt.  | 
            |||
Where-used list for element values: Search help  | 
            In the "Where-used list element values" popup, a shortdump is generated when the search helps are executed.  | 
            |||
MAMBA: Dump for non-numeric inputs  | 
            When a non-numeric value was entered into a numeric field in GRID, a short dump occurred.  | 
            |||
No translations for "Functions"  | 
            In the context menu, the language-dependent designations of the functions for the regulation type were not displayed correctly.  | 
            |||
SD GUI log container no longer closes  | 
            If the QPPD is integrated in the customer order in the docking container, it was not possible to close the display of the sync log or error log.  | 
            |||
MAMBA: Column optimization not always applied  | 
            Column optimization was not always performed.  | 
            |||
MAMBA: Wrong column group  | 
            The wrong column group was used for the display in the GRID.  |