New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | 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-3059 | ||
| Translation QPPD application in French | The QPPD application is available in French. | NOTE-3058 | ||
| CUSTRPT: Selection screen extended | A selection option for the element has been added to the selection screen of the customizing analysis. | NOTE-3046 | ||
| Use of BRF+ rules for context-related plausibility check of element values | The context check in TOE is extended by the BRF+ rule. The following functions can be mapped in the BRF+ rules:
-Plausibility check of element values based on TOEC contexts -Default values for elements -mandatory field control -Different messages for the log. Warnings, information, or error messages can be output. | NOTE-3015 | ||
| 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-2532 | ||
| BRFplus: Simplified data object generation (DOG v2) | New DOG generation version 2: Compared to DOG v1, transaction /SCT/QP_POOL can now be used to generate greatly simplified data structures and elements in BRFplus based on existing QPPD customizing. In DOG v2, generation is only VART-dependent and no longer context-dependent. The DOG v2 is based on the new BRF+ Engine v2. | NOTE-2528 | ||
| TOOLS: Splitting Range Interval | NOTE-2522 | |||
| GRID: Editabitilty of fields based on element customizing | In the grid based on elementsettings, such as nominal, and MIN, or Max values, controls exist that cause certain fields to no longer be editable.
This control is extended by the target value fields for inspection characteristics. | The maintenance type of PMK elements now determines the editability of columns. PMK elements may have to be updated. | NOTE-2520 | |
| 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-2518 | |
| SPLIT DIMS | NOTE-2500 | |||
| Progress bar: show speed | Display of processing speed can be optionally added. No effect on existing uses. | NOTE-2499 | ||
| SYNC_SD : Viewing the VKORG in the C71 | The settings for the SYNC in the SD in the C71 have been extended by the VKORG. This allows the settings to be made in dependence on the VKORG. | NOTE-2490 | ||
| Extend element to 20 digits | NOTE-2483 | |||
| Archiving: Archive change documents | The APP Archive in QPPD has been extended by the function that change documents can also be archived. In addition, the central database service has been extended by corresponding read functions. If certain indicators are set, the service now also returns the change documents for a QPPD object. | NOTE-2479 | ||
| 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-2477 | ||
| VC : Generic mapping | With this note it is now possible to work with patterns in the element name in the mapping for the synchronization between VC/rapid capture and VC/QPPD. For example "VC_ELEM*". Thus one does not necessarily have to list all elements individually. | NOTE-2476 | ||
| 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-2472 | ||
| MAMBA/ FCAT : Search help for unit and dimension(s) | It is now possible to define Mamba object types that have several different unit fields with different dimensions, e.g. meter and kilogram, on one line. | NOTE-2470 | ||
| NOTE-2467 | ||||
| VART: possibility to copy/reference recursively | This function allows to use a VART as a copy/reference template to another VART. It is possible to select the children of the source VART and decide whether they must be referenced or copied (assuming the VTYP is defined in the target hierarchy). | NOTE-2464 | ||
| 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-2463 | |
| QPPD CDS Views 1.0 | Standard QPPD CDS views are provided for the creation of customer-specific CDS views. These views provide all dependent data for a node in a structured way. Included are STATUS, NODET, VAL, VAL, PMK, STX as well as domains. Selections by text are supported either in the logon language as well as for all maintained texts. | NOTE-2461 | ||
| 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-2459 | ||
| FAVORITES TREE: Folder texts empty when changing logon language | The texts of the favorite folders are always displayed in the logon language. If the text is not filled, the text from another language is displayed. In this way, the favorites folder also receives a text if it should be filled in the logon language. | NOTE-2455 | ||
| Create VART as primary reference | A VART can now be used as a primary reference | NOTE-2449 | ||
| NOTE-2448 | ||||
| Additional functions on VART | New function "Additional function on the VART".
Shortening of field ACTION from 70 to 40 characters. | NOTE-2447 | ||
| Selection mask: variants and other toolbar buttons | Selection variants can be stored/called up for the selection screen. This applies to Z-selection screens as soon as the subscreens are defined as "selection screen".
The customizing setting "Delete tree for new selection" has been deleted. The arrangement of the pushbuttons has been changed: A new pushbutton "New selection" leads back to the selection screen. The new pushbutton "Delete selection" is only available on the selection screen. | NOTE-2444 | ||
| 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-2441 | ||
| SYNC : Support PMK from QPPD to FDM. | This note enables inspection characteristics (from the /sct/qp_pmk table) to be displayed in fast capture - and not only elements from the /SCT/QP_VAL table).
Synchronization from fast recording to QPPD for these inspection characteristics is not supported. | NOTE-2438 | ||
| 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-2434 | ||
| NOTE-2433 | ||||
| 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-2429 | ||
| MAMBA: Method for custom double-click handling | Improved extensibility. If the double click in MAMBA_VIEW is to be redefined or equipped with customer functions, this NOTE helps by providing the method MAMBA_VIEW->ON_DOUBLE_CLICK_CUSTOM. This can be redefined customer-specific and is already supplied with the necessary, resolved import parameters from the standard QPPD event handler. | NOTE-2428 | ||
| MAMBA: Detailed action log messages for generated values | Improved analysis options with the action log. | NOTE-2426 | ||
| CUST: Receive result of GET_TCONVERT as reference | The setting for the conversion routine (/SCT/QP_TCONVERT) can additionally be obtained as a reference from the CUST service. | NOTE-2425 | ||
| 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-2423 | ||
| Constant: Deletion of OBJEKTTYP_STATUS | The constant OBJECTTYPE_STATUS has been deleted because this object type is customizable and therefore could have a different names. | Check all usages of OBJECTTYPE_STATUS and replace them with Z constants if necessary. | NOTE-2414 | |
| MAMBA- TOE : Allow also positive news | TOE check methods can also generate positive messages (e.g. warnings) | NOTE-2413 | ||
| VART: Adjustments to DO_COPY_NODE | Developers get more options when copying nodes within builder functions on a VART class. | NOTE-2411 | ||
| 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-2410 | |
| TOOLS: Advanced unit conversion methods | New helper methods provide the ability to easily convert units in QPPD value fields during generation/builder. | NOTE-2408 | ||
| Logging of BRFplus messages | New possibilities for logging BRFplus messages in QPPD logics and during function execution. | NOTE-2402 | ||
| Enhancement of /SCT/QP_VAL and -PMK with MANDATORY flag | The MANDATORY flag now will be stored in tables /SCT/QP_VAL and /SCT/QP_PMK. It can no longer be generated via the SCREEN methods. | Z-generations and their methods must be checked for correct update of MANDATORY flag. | NOTE-2398 | |
| 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-2397 | ||
| Moderef: Domain incomplete / duplicates in DDIC | Consistency of development objects.
DTEL /SCT/QP_MODEREF changed to DTEL /SCT/QP_MODUS. Old DTEL and domain /SCT/QP_MODEREF have been deleted. | All usages of DTEL/DOMA /SCT/QP_MODEREF need to be switched to DTEL/DOMA /SCT/QP_MODUS. | NOTE-2392 | |
| 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-2391 | ||
| Customizing service: GET_TGRUELM extended by selection only via element | Customizing service: GET_TGRUELM extended by selection only via element | NOTE-2390 | ||
| 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-2386 | ||
| TOE: Context Analysis | It is now possible to double-click on a TOE error message in the log to display the appropriate context. | NOTE-2380 | ||
| 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-2372 | ||
| TOE Context: Dynamization of TOE context determination | In transaction C21 in the TOE sub-dialog a new field "Class TOE Context" has been created, which can optionally be filled. If the field is filled, the TOE engine will not use the class entered in the "Class TOE" field to determine the context, but the class in the "Class TOE context" field. | NOTE-2371 | ||
| 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-2370 | ||
| CL_VART: Enable value selection with LFDNR | Data can be selected with the LFDNR in addition to the ROWGRP. | NOTE-2361 | ||
| 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-2356 | ||
| BUS/VART class: Execute generation on object only for nodes with pending generation | In the interface to the BUS the new optional parameter IV_ONLY_PENDING to the method BUS->GENERATE as well as to the wrapper method GENERATE of the VART class was implemented. This makes it possible to execute the generation on an object only for nodes that have pending generations. Existing calls of BUS->GENERATE continue to work and do not need to be adapted. | NOTE-2345 | ||
| NOTE-2340 | ||||
| DOMAIN new functionality for domains for conversion methods checks with contexts | Domain: new functionality for domains for conversion methods checks with contexts | NOTE-2335 | ||
| NOTE-2325 | ||||
| NOTE-2317 | ||||
| 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-2303 | |
| NOTE-2302 | ||||
| NOTE-2292 | ||||
| NOTE-2289 | ||||
| NOTE-2287 | ||||
| NOTE-2286 | ||||
| NOTE-2280 | ||||
| NOTE-2278 | ||||
| NOTE-2275 | ||||
| NOTE-2274 | ||||
| NOTE-2267 | ||||
| NOTE-2266 | ||||
| TOE domain: Consideration of status and validity period at the domain | The validity period of the domain header has not been considered within the associated element until now. Also, domains with deletion indicators or locked domains could be used as valid domains.
With this correction the validity period of the elements is synchronized with the validity date of the header. If the status is not OK or released, the validity date is set to 0000000000. | NOTE-2264 | ||
| 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-2262 | |
| Class for Spec-Types extension /SCT/QP_CL_VART | Various new methods are provided. | NOTE-2260 | ||
| Extension class ECC documents /SCT/QP_CL_ECC | The class is extended by various methods | NOTE-2259 | ||
| BUS: Syntax check for element values | According to the MVC model, it is mandatory that the QPPD behaves in the background in the same way as in the foreground. Therefore, when the BUS is executed and element values are passed, these are checked for syntactical correctness. All customer implementations must be adapted if necessary. | All customer implementations must be adapted if necessary. | NOTE-2241 | |
| 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-2213 | |
| NOTE-2095 | ||||
| NOTE-1864 | ||||
| NOTE-1701 | ||||
| NOTE-1246 | ||||
| GENER structure: Duplicates / Wrong extension category | The /SCT/QP_S_TAB_GENER structure has been deleted and replaced by the existing, identical /SCT/QP_S_GENER structure. Customer-specific generation methods may have to be adapted in the signature. | Customer-specific generation methods may have to be adapted in the signature. | NOTE-1206 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | 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-2484 | ||
| NOTE-2462 | ||||
| NOTE-2396 | ||||
| FCAT: When building the dynamic columns, references are set to the column group fields | When building the field catalog, references are stored in the catalog for the dynamic columns from the column group. The identification of columns from the column group is simplified in the field catalog. | NOTE-2315 | ||
| NOTE-2268 | ||||
| NOTE-2261 | ||||
| NOTE-2257 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Drag&Drop: Create node via template | Create via drag & drop no longer works. Follow-up error NOTE 2530 | NOTE-3002 | ||
| SD : No sync between FDM and QPPD. | The synchronization between FDM and QPPD did not work properly. | NOTE-2534 | ||
| 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-2533 | ||
| CONTROLLER->DO_CREATE_MOD_NODE: Correction transfer VART/VTYP from IS_NODE_KEYS_NEW | NOTE-2531 | |||
| 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-2530 | ||
| BRFplus: Optimized data transfer | Signatures of functions can now be used to define data objects for input and output. | NOTE-2529 | ||
| 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-2524 | ||
| SPLITTER: Wrong display | When switching between two nodes in the GUI using the same splitter variant, a dangerous error can occur. This occurs when one node assigns an object type to a cell of its splitter, and the other node that will be switched to in the GUI does not assign an object type to the same cell of the same splitter. Since the processing of the containers in the splitter is based only on a positive list, the cell that is not used is not processed. Therefore, a wrong grid is then seen on this cell.
| NOTE-2523 | ||
| 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-2521 | ||
| Mamba : Field editability based on element-customizing | For VAL elements, it is now only possible to edit the VALUE_EIH field if the element has a dimension or standard unit. The fields of PMK elements are now controlled by the inspection characteristic type. The fields CATALGART1, AUSWMENGE1, AUSWMGWRK1 and AUSWVERS1 are ready for input for the inspection characteristic type Quantitative, but the other fields are not. For the inspection characteristic type qualitative, it is reversed and the fields SOLLINTUNTMIN, SOLLINTUNT, SOLLINTNENNWERT,SOLLINTOBE, SOLLINTOBEMAX, SOLLINTRANGET, SOLLINTPLRANGET, SOLLINTEINH, SOLLEXTUNTMIN, SOLLEXTUNT, SOLLEXTNENNWERT, SOLLEXTOBE, SOLLEXTOBEMAX, SOLLEXTRANGET, SOLLEXTPLRANGET, ALTSOLLZEUGUNT, ALTSOLLNENNWERT, ALTSOLLZEUGOBE, ALTZEUGEINH and NKOM are ready for input. If no inspection characteristic type is available, all fields are ready for input.
| the customizing for elements should be double-checked so that no fields become unintentionally not editable or editable. | NOTE-2519 | |
| 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-2517 | ||
| Mamba->DO_SET_VALUES : Conversion to TOE-F4 | After one or more entries have been selected from a TOE search help, the values have not always been converted to QPPD database format. This could lead to unwanted plausicheck errors. | NOTE-2516 | ||
| BRFplus: Formulas | BRFplus: Formulas | NOTE-2515 | ||
| Creation of an original node below a VBLOCK in the GUI not possible | The submenu for "Creation"/"Creation with template" was not built correctly on group nodes. | NOTE-2514 | ||
| Adjustments DDIC | The domains /SCT/QP_GENCLASS and /SCT/QP_ICON are deleted. | NOTE-2513 | ||
| NODE: DATA_GENERATE consideration STATUS | The generation at the node was executed although the node did not have the fit state. | NOTE-2510 | ||
| BUS->CREATE_VERSION from multiple positions | Versioning of multiple positions via BUS->CREATE_VERSION does not work. | NOTE-2509 | ||
| BUS: Deletion of nodes | NOTE-2507 | |||
| 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-2506 | ||
| Text elements and messages | Unification of the use of text elements and messages. | NOTE-2503 | ||
| 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-2502 | ||
| Uniqueness check with long texts | The uniqueness check did not consider the long texts correctly. Duplicate long texts were not recognized correctly. | NOTE-2501 | ||
| APPBUS: Jump to ECC-linked original instructions | Ability to jump by means of single method call. | NOTE-2498 | ||
| CONV: NUMC conversion | If the conversion method is NUMC and no length is specified, then no length restrictions may apply. However, errors are generated even if the maximum allowed length is not specified and the input is longer than no character. Furthermore, in the case when no maximum allowed length is specified, the leading zeros are added incorrectly if they are set. | NOTE-2497 | ||
| Archiving: Transfer/ Takeover of adaptations from VA | Correction of the formatting of NODET entries when writing archives. | NOTE-2496 | ||
| MAMBA: Update SCREEN properties | If the generation method is a CONRULE: Only MODEREF properties may be written back.
If the generation method is a SCREEN method: Only FILLTYP and VISIBLE may be written back. If the generation method is a GEN method: Everything may be written back: MODEREF, FILLTYP, VISIBLE, MANDATORY and VALUES. | NOTE-2494 | ||
| 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-2492 | ||
| Uniqueness check of the regulation name not correct. | This note corrects a problem in checking the uniqueness of a prescriptive name. | NOTE-2491 | ||
| 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-2489 | ||
| VART class is instantiated 2 times | The VART class has been instantiated a second time for an object when it is loaded. This happens under the condition when object 2 was used as LINK or BOM in object 1 and then object 2 is loaded separately. This can lead to unintended behavior on object 2 when a new VART instance is used. | NOTE-2488 | ||
| 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-2487 | ||
| Extension categories corrected | NOTE-2486 | |||
| BRFplus: Runtime optimization when referencing context data objects during function call | Runtime optimization for function calls. | NOTE-2485 | ||
| CDPOS_UID not deleted | When deleting change documents, SAP standard change document table entries (Tables CDHDR, CDPOS and CDPOS_UID) have not been deleted correctly. | The report for deleting the redundant QPPD change documents, /SCT/QP_CORRECT_DEL_CHGDOCS, must be run on each client QPPD has been installed. The program /SCT/QP_CHGDOCS_STATS gives an overview of the number of change documents affected. | NOTE-2482 | |
| 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-2481 | |
| Create node with referencing does not consider the position number | If a node is created with referencing and the position number is specified, it is not taken into account. This leads to unintended behavior with the new node. | NOTE-2480 | ||
| 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-2478 | ||
| SYNC_VC: VC data not loaded within VA03 | On a SAP HANA system, the data in QPPD FDM from VC is not loaded immediately when using transaction VA03. | NOTE-2475 | ||
| 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-2474 | ||
| Mamba : Value fields not recognized correctly | An internal error has caused that value fields have not always been recognized correctly. As a consequence, the search helps have not been displayed correctly or conversion errors have not always been deleted after the input has been corrected. | NOTE-2473 | ||
| NODE_TEXT: FCAT | The FCAT was not displayed correctly when switching from display to change mode. | NOTE-2469 | ||
| TOE : Error messages incorrectly formatted (key3) | This note corrects a problem during the plausibility check of elements. Under certain circumstances, the error messages have been formatted incorrectly. This has resulted in the messages no longer being automatically cleared when the error was corrected. | NOTE-2468 | ||
| NOTE-2466 | ||||
| GUI, MT: "Error getting the event parameter" | Error message "Error getting the event parameter" when clicking the expander at the node. | NOTE-2460 | ||
| 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-2458 | ||
| CL_TEXTELEMENT : Non-existent translation leads to short dump | If a text is to be determined via CL_TEXTELEMENT for a language which is not maintained, a dump occurs. | NOTE-2457 | ||
| 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-2456 | ||
| Change documents at midnight ("burn the midnight oil") | When change documents are written at exactly 0 UTC, a short dump occurs. | NOTE-2454 | ||
| 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-2453 | ||
| SYNC_QPPD : Sync object not activated (FDM) if no data available | The note corrects a display problem on the fast data maintenance (FDM) screen. Under certain circumstances, the FDM has not always been updated. | NOTE-2452 | ||
| TECHM_DUO: Changes are not always saved | Corrects the possible loss of data when saving domains after the selected languages have been changed. | NOTE-2450 | ||
| MAMBA/MAMBA_VIEW: Grid is not rebuilt | NOTE-2446 | |||
| NODE/HEADER: Origin is not saved | Original origin will be written to nodes. | NOTE-2445 | ||
| Context menu shows incomplete elements. | This note corrects the structure of the context menu in QPPD: Sometimes the technical function was displayed instead of its description. | NOTE-2443 | ||
| SYNC : QPPD changes are not always saved when 2 sync models are active | Improved detection of changes when multiple sync models are active. | NOTE-2442 | ||
| MAMBA: Write back search help results only for input-ready elements | Element values that could normally not be changed manually were able to be overwritten under certain circumstances by selecting a search help value. | NOTE-2439 | ||
| NOTE-2437 | ||||
| MAMBA: Copying error with rows with longtext | While copying rows with existing longtext also TDNAME will be copied. As a consequence the text is referenced and both rows have exactly the SAME textobject | NOTE-2436 | ||
| Conversion errors disappear during copying | Values are syntactically checked when nodes are copied/versioned. | NOTE-2435 | ||
| Selection screen: Shortdump (head status + Vtype) | This note corrects a dump on the selection screen: If only certain criteria were filled, the JOIN conditions were built incorrectly and a SQL DUMP occurred. | NOTE-2432 | ||
| MAMBA: Dump when resetting error messages | Dump when resetting error messages within MAMBA | NOTE-2431 | ||
| MAMBA: Optimized recognition of element and field name on double click | The handling of a double-click in the object type did not work or only to a limited extent for the ELEMENTTEXT field (text for the element). A double-click here can e.g. bring the TOE context analysis to the display, if configured accordingly. | NOTE-2427 | ||
| 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-2422 | ||
| TOE: Global generation must not be triggered during TOE check (constraints/workload) | TOE calls MAMBA to check values during the context check. Via this additional ACTION the Global Generation (GG) is suppressed. | NOTE-2421 | ||
| 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-2420 | ||
| DOG: Element profile not always correctly assigned | Elements with specific element profile (/SCT/QP_C18) may not have been displayed with corresponding characteristic in transaction /SCT/QP_DOG. | NOTE-2419 | ||
| MAMBA: Generation of initial data does not execute a check | NOTE-2416 | |||
| MAMBA insert_line : Determine TECHTYP automatically | If the TECHTYP was forgotten in the elementcustomizing, subsequent functions in MAMBA were not executed correctly. Now the object type determines the TECHTYP itself. | NOTE-2415 | ||
| 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-2412 | ||
| CL_VART->GET_DATA_BASE returns the nodes in the wrong order Under certain circumstances, long texts are duplicated to an element when the referencing is removed. | This note ensures that the return table of the CL_VART->GET_DATA_BASE method is sorted in ascending order by hierarchy. | NOTE-2409 | ||
| 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-2407 | ||
| TEXT: Empty texts are stored on the database | STX entries with empty content will no longer be stored, unless the text is based on a reference! | NOTE-2406 | ||
| 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-2405 | ||
| MAMBA: Doubling VAL-LTXT at resolution primary reference | Under certain circumstances, long texts were duplicated to an element when the referencing is removed. | NOTE-2404 | ||
| 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-2400 | ||
| NOTE-2395 | ||||
| NOTE-2394 | ||||
| NOTE-2393 | ||||
| NOTE-2389 | ||||
| NOTE-2388 | ||||
| NOTE-2387 | ||||
| NOTE-2385 | ||||
| NOTE-2383 | ||||
| MODEL: GG when creating the node | The call of the GG when creating the node has been revised. | NOTE-2382 | ||
| 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-2381 | ||
| Shortdump when nodes displayed from the BUILDER are deleted | After deleting nodes with the Builder (in the background), a dump can be generated when the deleted node is displayed in the GUI. | NOTE-2379 | ||
| NOTE-2378 | ||||
| NOTE-2377 | ||||
| NOTE-2376 | ||||
| NOTE-2375 | ||||
| NOTE-2374 | ||||
| NOTE-2373 | ||||
| NOTE-2366 | ||||
| NOTE-2364 | ||||
| NOTE-2362 | ||||
| SYNC : Reference to the source dataset added | Normally none. The new field is not yet used in SCT-Std. | NOTE-2360 | ||
| NOTE-2359 | ||||
| NOTE-2358 | ||||
| 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-2357 | ||
| NOTE-2355 | ||||
| NOTE-2354 | ||||
| Subnodecan be versioned despite CHILD workmode | Under certain circumstances it was possible to version a subnode, although this was not allowed in customizing (because the header is not changeable). | NOTE-2353 | ||
| 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-2352 | ||
| NOTE-2350 | ||||
| NOTE-2349 | ||||
| NOTE-2348 | ||||
| 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-2347 | |
| NOTE-2346 | ||||
| NOTE-2343 | ||||
| MAMBA: Shortdump when initializing data with validity check on date | NOTE-2341 | |||
| 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-2339 | ||
| Error versioning: edit 2 versions at the same time | When changing from CHANGE to DISPLAY and the current object can be versioned, all higher versions of the current object are additionally reloaded in object-oriented change mode. | NOTE-2338 | ||
| NOTE-2337 | ||||
| NOTE-2336 | ||||
| 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-2333 | ||
| NOTE-2331 | ||||
| NOTE-2330 | ||||
| NOTE-2329 | ||||
| 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-2328 | |
| TECHM_DUO: Shortdump | If TECHM_DUO is used in a domain and this domain is loaded independently as well as under an element, a short dump may occur. | NOTE-2327 | ||
| Longtext incompletely read | Sometimes the first line of the long text was not returned by the data service. | NOTE-2326 | ||
| NOTE-2324 | ||||
| NOTE-2323 | ||||
| MAMBA: Dump in case of wrong assignment of TechType of an element to the object type | If the object type is e.g. TME and the element itself is of the TechType PMK, a shortdump occurs. | NOTE-2322 | ||
| NOTE-2320 | ||||
| NOTE-2319 | ||||
| NOTE-2318 | ||||
| NOTE-2316 | ||||
| NOTE-2313 | ||||
| NOTE-2311 | ||||
| NOTE-2309 | ||||
| NOTE-2308 | ||||
| NOTE-2307 | ||||
| NOTE-2306 | ||||
| NOTE-2305 | ||||
| NOTE-2304 | ||||
| NOTE-2301 | ||||
| NOTE-2299 | ||||
| NOTE-2298 | ||||
| NOTE-2297 | ||||
| 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-2296 | ||
| NOTE-2295 | ||||
| BRF+ V1: Dumps due to lost node reference | Fixing dumps after deleting nodes for complex constellations of rules in memory. | NOTE-2293 | ||
| NOTE-2291 | ||||
| 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-2284 | ||
| NOTE-2282 | ||||
| NOTE-2281 | ||||
| NOTE-2279 | ||||
| NOTE-2273 | ||||
| TECHM DUO: Longtexts TDNAME | Deleting the long texts in TECHM_DUO does not work correctly. The TDNAME was not generated correctly. | NOTE-2272 | ||
| NOTE-2271 | ||||
| Generation: TDNAME while copying | When versioning/duplicating/creating new nodes, a TDNAME was generated for the /SCT/QP_VAL entries under certain circumstances, although no long text was available. | Correctionreport /SCT/QP_CORRECT_TDNAME must be executed to clean up the /SCT/QP_VAL entries. | NOTE-2270 | |
| NOTE-2265 | ||||
| Objecttypes at referenced nodes | If the element group was redefined at the hierarchy, a data loss as well as a display error may occur when saving if the redefined element group contains elements which are not defined in the position type. In addition, an object with a node containing the original element group must be loaded first. Then an object must be loaded which contains a node of the same position type but with the redefined element group.
| NOTE-2263 | ||
| NOTE-2256 | ||||
| MAMBA : Saving mandatory elements without values . | Error messages for non-valued mandatory elements were not reset correctly when they were evaluated after reloading the object.
Non-valued mandatory elements will be saved in the future so that the reference to the error message is not lost. | NOTE-2243 | ||
| 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-2137 | ||
| MAMBA: Generation of object types with elementgroups of different types (horizontal/vertical) are faulty | If both VAL entries and PMK entries were generated (or newly created) from a generation method, the VAL entries were processed first and then the PMK entries (or vice versa). This resulted in incorrect generation of these new values if the horizontal elements (from VAL or PMK) happened not to be processed first. With this NOTE, all horizontal elements are processed first and then the vertical elements, regardless of their TECHTYP. | NOTE-1903 | ||
| 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. | NOTE-1719 | ||
| NOTE-1163 |