New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Follow-up processes | New framework follow-up processes | Any existing settings for creating queues using the TOOLS method must be converted to the new technology.
Entry in Factory / SCT / QP_IF_IDOC implemented by / SCT / QP_CL_QV_IDOC_SERVICE Make settings in C10-> Follow-up processes for QPPD standard follow-up processes: SCT_CHGD change documents => / SCT / QP_CL_FUP_CHGD_OUT SCT_CHGP change pointer => / SCT / QP_CL_FUP_CHGP_OUT SCT_IDOC_IN IDOC input => / SCT / QP_CL_FUP_IDOC_IN SCT_IDOC_OUT IDOC output => / SCT / QP_CL_FUP_IDOC_OUT SCT_INFO_MARK INFO Dependent data records mark => / SCT / QP_CL_FUP_INFO_MARK SCT_INFO_REWORK INFO Dependent data records proz => / SCT / QP_CL_FUP_INFO_REWORK SCT_RFC_OUT copy data via RFC => / SCT / QP_CL_FUP_RFC_OUT | NOTE-3108 | |
| CONV: Conversion depending on unit | This note enables further conversion specifications for numeric values.
With this note, it is possible to specify the format (e.g. number of digits before/after the decimal ) differently for each conversion method and for each specified unit of measurement. (e.g. mm with 2 decimals/ inches with 3 decimals) If the unit is not found in the customizing for the conversion method, the entry without a unit is valid. | NOTE-3105 | ||
| Selection of Spec´s with connection to ECC-Documents | Until now, there was no option available to select a specification for a sales document ( or material master or production order) in QPPD. This note solves this problem.
- When creating an ECC spec, the key fields will be additionally stored as single values in table /sct/qp_val. - Creation of a CDS view (DB-VIEW) for the selection of ECC documents - New selection report for selection via ECC documents (key fields e.g. MATNR/ VBELN) as new selection tab | NOTE-3066 | ||
| GRID: Convenience. Copy rows and display them in order | By copying lines, the new lines will now be added immediately after their own source, according to the current sorting, and not always on top of the grid as it was before. | NOTE-3060 | ||
| Sync-MM: Customizing depending on the KMAT | With this NOTE it is possible to make customising settings for the material master connection, which are dependent on the KMAT. | NOTE-3023 | ||
| Main tree: Display of new information | New information is visible in the columns of the main tree: area of responsibility, user, authorisation group, original rule type, hierarchy and context. | NOTE-3022 | ||
| Update INFO records with bgRFC | The processing of INFO records has been technically revised and converted to bgRFC. | NOTE-3021 | ||
| Specificationtype Filter via authorization | The search helps for the Specificationtype and the itemtype now only display entries the user has read permissions for. This gives more clarity and helps to avoid errors. | NOTE-3014 | ||
| Additional functions on VART | New function "Additional function on the VART".
Shortening of field ACTION from 70 to 40 characters. | NOTE-2447 | ||
| Process outgoing IDOCs with bgRFC | The processing of outgoing IDOCs has been technically revised and converted to bgRFC. | NOTE-1374 | ||
| CHGDOC: Automatic processing of change pointers with bgRFC | The processing of change pointers has been technically revised and converted to bgRFC. | NOTE-1288 |
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | BUS-> CHANGE Do not abort processing in the case of resumable exceptions | If exceptions that can be resumed occur when processing changes via the BUS, the BUS no longer aborts processing. Instead, the exception message is written to ET_RETURN and processing continues. | NOTE-3103 | ||
| CL_SYNC2 is obsolete | It is no longer necessary to specify CL_SYNC2 in the factory setting (C10). | NOTE-3089 | ||
| CL_VART: Method DO_COPY_NODE deleted | Less complexity in SCT-VART class. More flexibility through implementation in Z-VART class. | Uses of the SCT method must be replaced with the copied Z method. | NOTE-3080 | |
| BRFplus DOG v2: Refactoring | The Data Object Generation (DOG) v2 transaction /SCT/QP_POOL is renamed to /SCT/QP_DOG_VART.
In addition, internal classes have been renamed. | Customer implementations for the APP BRF+/DOG may have to be adapted due to the changed classes.
| NOTE-3079 | |
| BUS: export parameters for missing read permissions | Several new parameters | NOTE-3078 | ||
| RFC-Service | With the new class /SCT/QP_CL_RFC and the corresponding interface /SCT/QP_IF_RFC, data can be read in from an RFC source and saved in another RFC target. It is recommended to only use this service for RFC accesses and to avoid direct FM calls. | It is recommended to only use this service / SCT / QP_CL_RFC for RFC access and to avoid direct Functionmodule calls. | NOTE-3074 | |
| CUST: Resolution of reference itemtypes | Reference itemtype resolution is now supported for arbitrary depth | NOTE-3073 | ||
| CONCEPT GAP: References | The QPPD lock concept has been changed: Previously, only an exclusive lock was generated for the ROOT of the own object. With this NOTE, a read lock is now additionally generated for every other, different object, of which at least one node is used as a reference (other relation type than "original").
This prevents the deletion of a node in exactly the case, if this is used as reference in an object, which was not stored yet. It is still possible to change the content of a node if it is used as a primary and/or secondary reference in an object that is currently being edited by another user. | NOTE-3072 | ||
| TOE: Extension of plausibility check for inspection characteristics with the field SELECTED SET | The field "selected set" has been added to the plausibility check for inspection characteristics. If the SAP standard selected sets are to be used, the technical object /SCT/QP_CL_TOE_TABLE can be used with reference to the standard tables. | If the selected set is used for inspection characteristics and a plausibility check and search help functions are to be performed, then a technical object must be added in Customizing. If the SAP standard selected sets are to be used, the technical object /SCT/QP_CL_TOE_TABLE can be used with reference to the standard tables. | NOTE-3070 | |
| Workmode CREATE | The QPPD now uses the "WORKMODE CREATE" for newly created nodes.
This workmode remains until the node is saved for the first time or until the node is changed to a status in which the node is not ready for input (WORKMODE N). It allows a finer definition of the authorization in the case of creation. | If necessary, maintain settings for WORKMODE CREATE in activity profile C15.
If necessary, check authorizations for creating objects and related nodes. | NOTE-3068 | |
| TOE: Determination of context values for line elements extended to object types | When determining context element values, the search via hierarchy indicator is interpreted differently. Up to now for Multi-grid, only elements of the row have been found. The search now has been extended. Elements related to the object type will also be found. | NOTE-3064 | ||
| Mass Change: Improvements | Optimization of functionality and integration as APP. | NOTE-3063 | ||
| PP: Production order change with BADI WORKORDER_UPDATE instead of userexits | NOTE-3056 | |||
| TOE conversion FuBa exit characteristics from VC to ABAP class | Conversion of plausi, text determination and search help from Function to Class /SCT/QP_IF_CAWN and /SCT/QP_CL_CAWN
Overdefinitions now possible. The function modules are retained. | NOTE-3052 | ||
| TOE conversion method GET_TOE_STRUCTURE to interface method | The method is also required externally for access from classification. | NOTE-3051 | ||
| SYNC MM : Read all ECC relations | Up to now, only QPPD objects were read in to DOCTYPE MARA,
Now the QPPD objects that are connected to the MARC are also displayed. | NOTE-3050 | ||
| CDS VIEW /SCT/QP_C_VAL Flag01 - Flag10 added | CDS view now with additional fields | NOTE-3047 | ||
| BRF+: MODEL uses against MVC | The QPPD model was used outside the controller. This is against the MVC architecture. | All customer implementations that use the QPPD MODEL directly must use the CONTROLLER instead. | NOTE-3043 | |
| TOE: Delete field TOE context type (TOEC_TYPE) | Improvement in TOE by automatic determination of flow logic. Therefore an adjustment of Z-TOE classes will be necessary because a field was removed. | In Z classes with TOE context, the setting of the field must be deleted. | NOTE-3041 | |
| TOE Access from external applications | Access from external applications now will be supported. The methods for
-Plausibility check of values -value list, -call of search helps -determination of multilingual texts are provided. Context values can also be set. The functionality is shown in the example report /SCT/QP_TOE_EXTERNAL_CALL. | NOTE-3038 | ||
| TOEC: Validity Element values without RowGroup are multiplied out. | New function:
If the Validity tab does not contain any other column elements, it is assumed that the single values of the elements are valid in combination and form a combined context. | NOTE-3037 | ||
| TOE: Restructuring of the methods for system variables for better overdefinition | System variables can be queried in TOEC. Methods have been extracted for better encapsulation for overdefinitions. | user of elements wioth name praefix /QPPD/ | NOTE-3036 | |
| TOEC Change of logic for validity values at the VART | On the Validity tab of the register for validity, elements can be filled with values that are queried during the context check. If the element is listed and the content is space, the validity was also queried on blank for the element. This logic is changed. A space is now interpreted as '*'. This reduces the maintenance effort. If nevertheless a space is needed '= ' should be entered. | NOTE-3035 | ||
| DATA: New selektiontype VART | There is now the option of using the DATA Service to select only with the regulation type (VART). All objects for which the VART matches are returned. | All calls should be checked, which load data in QPPD, whether they only use the specificaiton type (VART). If necessary, these calls have to be adapted if a selection with the VART alone is not desired. | NOTE-3033 | |
| CUST: GET_NODE_HIERA_ELEMENTS | The new optional import parameter allows to get the CUST settings only for the ROOT and not for the whole object. | NOTE-3032 | ||
| MODEL usage against MVC | The QPPD-Model was used outside of the controller. This is against the MVC-architecture. | All customer implementations, which use the QPPD-MODEL directly have to use the CONTROLLER instead. | NOTE-3031 | |
| VART class against MVC | The QPPD model was used outside the controller. That's against the MVC architecture. | All customer implementations that use the QPPD-MODEL directly must use the CONTROLLER/BUS instead. | NOTE-3030 | |
| TOOLS: Analysis program for number ranges | NOTE-3020 | |||
| XML service against MVC | Violation of MVC architecture led to inconsistent data processing. | NOTE-3019 | ||
| BRFplus v2: Sampler for enhancements | NOTE-3008 | |||
| Programme /SCT/QP_QV_UPDATE deleted | The /SCT/QP_QV_UPDATE report was deleted.
| NOTE-3007 | ||
| VART class: collector for extensions / adaptations | The VART class was supplemented by helper methods for creating / changing / deleting nodes. | NOTE-3000 | ||
| Versioning revision | The versioning in the standard has been completely technically revised. | All customer implementations for versioning must be adapted. All redefinitions of deleted methods must be recreated. | NOTE-2535 | |
| BUS: CREATE/CHANGE: Value fields and rate logic | The logic to guess which node is meant by the request (in the BUS), as well as the processing of the value fields was fundamentally revised or corrected. All customer implementations must be adapted if necessary. | All customer implementations must be adapted if necessary. | NOTE-2527 | |
| Wrong definition of database tables as text table | QPPD database tables were defined as text tables. | NOTE-2512 | ||
| GUI: Restructuring context menu FCODE/ACTION | Handling of FCODE by the event handler has been restructured as well as the internal QPPD-ACTION. Many internal methods and signatures have been changed to better separate FCODE and ACTION. FCODE is used in the SAP standard to control buttons and context menus. QPPD internally works with ACTIONs. | Customer redefinitions and implementations of GUI, CONTROLLER, MODEL and BADI must be checked. | NOTE-2505 | |
| ECC: Separation of SD logics (app-specific) from CORE | Improper separation of CORE-ECC and APP-SD. Correction in this note. | NOTE-2471 | ||
| XML service: Obsolete source code | Obsolete source code was removed. | NOTE-2465 | ||
| Classes for XML processing adapted | Technical adaptation coding | NOTE-2368 | ||
| VART->CHANGE: parameter-simplification | Actually the IS_CHANGE parameter has some complex possibilities. However, these are hardly used, since the use is not self-explanatory. Therefore, the method is rewritten to use BUS types. | After importing the actual release, usages must be changed from /SCT/QP_CL_VART->CHANGE_DATA to ZQP_CL_VART->CHANGE_DATA. | NOTE-2332 | |
| Instantiation of classes in the SE16N | Number of class instances will be reduced. | NOTE-1878 | ||
| Checkpoints | Revision of the checkpoint groups. | NOTE-1367 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | TOE performance optimization when using constraints in element value checking | If an element has dependent values, these are checked too often. The correction reduces the number of checks depending on the application up to 30%. | NOTE-3104 | ||
| Generalization of method for TOEC and domains | TOEC methods are queried in parts on values belonging to the TOE and not assigned to the context. These methods are adjusted so that the old definition still works.
The generation methods at the domain, which provide the basic data for the TOEC methodology are also controlled with fixed parameters and also do not use the constant class. This adaptation is necessary for the creation of the documentation and demo examples in the ECP system. | NOTE-3088 | ||
| Performance problem while deletion of subnodes | A performance problem was corrected when deleting subnodes under a complex hierarchy. | NOTE-3009 | ||
| BUS->READ reads to much data | The logic works correctly again. Less memory will be consumed. | none | NOTE-2036 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | TOE-conversions are not standardized | Some TOE-objects return F4-values in database format, some others in display format (using conversion-exit). To avoid inconsistencies and double conversion, the display format should be used overall. | NOTE-3152 | ||
| /SCT/QP_CL_PP_COLLECTOR uses the non existent GET_INSTANCE method of the Tools class | NOTE-3138 | |||
| Upwards notification | If a value was changed for an original node below a VBLOCK through generation and a notification is to be carried out for all parent nodes, then this was only carried out until the next VBLOCK. | NOTE-3113 | ||
| BUS: No exceptions | Generating exceptions in the BUS has never been supported. An error caused an exception to be generated by mistake. | NOTE-3112 | ||
| Creating multiple long texts creates a short dump | duplikat | NOTE-3111 | ||
| Wrong determination of VART_INSTANCE | The note corrects the fact that, under certain circumstances, the VART instance for child nodes was wrong determined. | NOTE-3110 | ||
| Endless loop when splitting intervals | If intervals are specified incorrectly, e.g. max-value is smaller than min-value, the splitting of unique intervals runs into an endless loop. | NOTE-3109 | ||
| Set mandatory-flag using generation | Using generation-methods to set the mandatory flag won't always work as expected. | NOTE-3107 | ||
| Sync SD : Price conditions not transferred | This note remediates this problem: Under certain circumstances, the price conditions that were generated in QPPD were not synchronized into the sales order. | NOTE-3106 | ||
| NOTE-3102 | ||||
| NOTE-3099 | ||||
| TOOLS Determination of screen-componentstructures creates a short dump | With method TOOLS->GET_STRUCT_COMP for the selected component (from DDIC) further structure information to the data element/DDIC will be read. If no DDIC object but a dynamic type assignment (in a class or type definition) is available, a short dump is produced. | NOTE-3098 | ||
| Error/Problem while deleting nodes | When deleting a node, a shortdump can happen under very special circumstances. | NOTE-3097 | ||
| Writing info sets deletes too many nodes when using VTYPEN filter | When nodes are filtered using VBlocks or VTypes, nodes that are assigned SPACE are also deleted. | NOTE-3092 | ||
| TOE Context determination in search helps for effectivity values = Initial faulty | The validity check in search helps is performed against element values on the tab for regulation types. If no contents are specified, a blank should be interpreted as '*'. The error is corrected | Note: For implementations via CDS views, non-filled element values (content = NULL) should be set to blank.
Example: (CASE when element.value is null then ' ' else element.value end) as value | NOTE-3091 | |
| NOTE-3090 | ||||
| /SCT/QP_IF_TOOLS~DO_FILL_MANDT_QVCDATA Client is not filled in | The client in the /sct/qp_s_qvc_data structure was not populated as expected. | NOTE-3086 | ||
| CORE: Wrong prompt for saving at "Back | The prompt to save was shown too early (in the case where the user clicked "Back" to get to the selection screen). This note corrects the problem | NOTE-3084 | ||
| Customizing: Search helps in hierarchy | The search helps for status profile and VBLOCK used the wrong search helps.
It was only possible to enter values manually. | NOTE-3083 | ||
| LOG not saved | If only LOG entries that do not trigger a status change are changed via the node check, these changes in the LOG are not taken into account when the object is saved. | NOTE-3077 | ||
| GUI: error after deleting "Object type not set". | If the currently selected node in the tree is deleted via the MT TOOLBAR and there is no other node or the parent node has no object types, the error "Object type is not set the GUI" appears and the transaction is terminated. | NOTE-3076 | ||
| MAMBA / TEXT: Data from references are saved | Error 1) Data from references is incorrectly saved as original data.
(Precondition: The node where references are used must be changed and saved twice). Error 2) During versioning, data is duplicated when references and vertical elements are present. | NOTE-3071 | ||
| GRID: The method for grouped determination of the table does not return any results if condition elements are missing | The method /SCT/QP_CL_VART->get_grid_grouped returns no results if there is no entry in the condition column. | NOTE-3069 | ||
| TOE: system fields are not reset during context determination | If system fields such as regulation type are used as context and a change of context is done then the previous context value is kept | NOTE-3067 | ||
| BRFplus (old engine): Incorrect mapping if element exists on different tabs of a node | Possibility of wrong results when running BRFplus ruleset using old BRFplus engine. | NOTE-3062 | ||
| NOTE-3061 | ||||
| NOTE-3057 | ||||
| TOE Selection method for search help values not called up | When using the rule type class to select data for F4 finders, the method was not called. | NOTE-3055 | ||
| No authorization check while Copying | When copying, there was no authorization check and thus it was possible to create nodes although it is not allowed. | NOTE-3053 | ||
| TOE: Interface method Get_Value_Text does not return texts when called externally | When calling up text determination from external applications such as search help and text determination in classification, no texts are determined. The correction has been made | NOTE-3048 | ||
| GET_BASE_ROOT_DELETE and GET_BASE_ROOT not in sync | If a node in the BUS was not addressed with GUID (but with e.g. VNAME, VNR), it could happen that the wrong hierarchy was processed. | NOTE-3040 | ||
| NOTE-3039 | ||||
| BRF+: Screen generation deletes log messages | Related to BRF+ v1: When opening tabs with BRFplus screen generation, log messages are deleted from BRFplus in display mode. | NOTE-3034 | ||
| BRF+ rules selected incorrectly with multiple clients on one system | If several clients are active on one system, the functions are read for each client. This leads to a dump during the later assignment to internal tables. | NOTE-3029 | ||
| ARC: Writing the archive with different client | In case the target system has a different client than the source system, while transferring data into the archive, the data was stored with the wrong client. | NOTE-3027 | ||
| ARC: Write Version: Memory overflow during mass data processing | The program /SCT/QP_ARC_WRITE_VERSION dumps if it is executed for a lot of data. | NOTE-3026 | ||
| Object type NODE_TEXT: Data storage error after button initialization | Entries that were deleted or created via the "Initialize texts" button were not saved or transferred until now. Saving the object type NODE_TEXT now works correctly. | NOTE-3024 | ||
| Error during the uniqueness check. Spec.-name not accepted. | Under very special circumstances, an error has been erroneously generated during the uniqueness check of regulations.
The error can be recreated as follows: Create object, save, delete and create a new object with the same name again. | NOTE-3017 | ||
| NOTE-3011 | ||||
| Grid: Catalog column not editable for qualitative inspection characteristics | After the adjustment, the catalog is now editable at PMKTYP QUAL and no longer at QUAN. | NOTE-3010 | ||
| SYNC_VC : Shortdump during formatting of numbers | If VC features are configured as numbers, a short dump may occur depending on how many decimal places are entered. This note corrects the problem. | NOTE-3005 | ||
| VC : Generic mapping, correction | The generic mapping to VC was not displayed in the FDM. | NOTE-3004 | ||
| TREE : Subnodes under group nodes are not displayed | Under certain circumstances, (folders for VTYP's should not be displayed) it can happen that subnodes in the tree are not displayed properly. This note corrects the misbehavior. | NOTE-3003 | ||
| Drag&Drop: Create node via template | Create via drag & drop no longer works. Follow-up error NOTE 2530 | NOTE-3002 | ||
| MAMBA: Deletion of VAL long texts | Empty VAL records only with TDNAME without TDID and without TDOBJEKT were saved mistakenly. | NOTE-2538 | ||
| Shortdump with VBLOCK status schema | Short dump when generating data if VBLOCK has no status scheme. | NOTE-2537 | ||
| DOCUMENTS Cancel popup creates documents anyway | Despite cancellation in the popup, documents were stored in the BDS! | NOTE-2536 | ||
| DO_CHECK_NEW_DATA_REF : Incorrect error message. | Copying grid lines consisting of PMK and VAL values did not work properly. | NOTE-2508 | ||
| DOCUMENTS: incorrect adoption of the language | Correction includes the conversion of the language from LAISO to SPRAS, the documents are no longer saved with the wrong language key. | NOTE-2430 | ||
| NOTE-2418 | ||||
| BUS->CHANGE: Usage of VNAME in DELETE statement deletes data | While using BUS->CHANGE. If in the Parameter table IT_DELETE the VNAME was used to identify the right node, to delete a /SCT_QP_VAL/_PMK/_ANA entry, the method CL_HEADER->DO_CHANGE_DATA also has been called. In this case the Specification-Name (VNAME) was deleted mistakenly. This note corrects the error. | NOTE-2401 | ||
| XML service: Authorization error / Incomplete data | There have been several problems with authorization checks and data selection due to redundant logic. Now the BUS will be properly used instead. | NOTE-1967 |