New functions
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | New APP Purchasing (ME) | This NOTE is used to integrate QPPD into the purchasing document. | NOTE-3229 | ||
| synchronization order data (head) | synchronization order data header level | NOTE-3201 | ||
| MM: Plant-dependent QPPD objects | With this NOTE, QPPD objects for a material can now also be created independently of the plant. | NOTE-3195 | ||
| BRF Engine Version 3 | Version 3 of the processing of BRF+ function and its mapping offers the following improvements:
Support of all BRF+ data (units, date, timestamp..) Mapping of multi grids and parameter tables Direct addressing via rule positions, context and object type Support of deep BRF structures Data content for the regulation header (e.g. regulation type or name) can be queried. When using multiple function calls for an object type, the generated data is transferred to the successor. Also included is an example BRF+ application: /SCT/QP_GEN | Activation via parameter BRF_ENGINE = 'V3' or direct call of method BRF_EXECUTE3 of the generation class.
Existing BRF+ rules must be checked Use of appliction log only with Object /SCT/ and subobject BRF non persistence. | NOTE-3193 | |
| ECC documents extended by the object VBEP schedule line for the sales item | The ECC functions are extended by the schedule lines of sales document items.
GET_VBEP and GET_VBEP_TAB are available in the class /SCT/QP_ECC. The selection screen for ECC documents in the standard system has been extended to include the document category VBEP. | NOTE-3155 | ||
| TOE: Context determination from variant configuration | TOE can be used in the variant configuration. The determination of context-dependent characteristics is now supported. | - | NOTE-3054 |
Technical changes
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Synchronisation via VART-Classes for inbound and outbound data can be modified | none | Redefinition of methods in classes
/SCT/QP_IF_SYNC~SYNC_FILL_BUFFER_OUTBOUND /SCT/QP_IF_SYNC~SYNC_PROCESS_BUFFER_INBOUND | NOTE-3276 | |
| SYNC_FDM: call submethod DO_CHANGE_VAL missing | With the method /SCT/QP_CL_SYNC_FDM->DO_CHANGE_VAL, an additional option was created to manipulate a VAL data record before the changes are applied. | NOTE-3272 | ||
| BRF+ processing with mapping of structural elements in individual generation methods | For the generation QPPD provides methods to generate element values via BRF+ functions. Thereby a mapping to the current object type and the structures of the QPPD object takes place.
For the use in customer-invidual programs individual BRF+ calls with transfer of import parameters can be made with this extension. The mapping of the element values is then done analogously. | user of method /SCT/QP_CL_BRF_PROCESS3->/SCT/QP_IF_BRF_PROCESS3~EXECUTE | NOTE-3245 | |
| BRF+ Connection of multiple data Types of BRF+ with QPPD | If extended properties are used, the existing rules in the BRF+ must be adapted. | Definition of the element with corresponding properties.
| NOTE-3187 | |
| TOOLS: Determine ASCII code / delete non-ASCII characters | The new method GET_ASCII_FROM_CHAR enables the determination of the ASCII code of one character.
The new method DO_REMOVE_NON_ASCII deletes all non-ASCII characters from a string. These methods can be used, for example, to filter the content of messages sent to old legacy systems. | NOTE-3166 | ||
| Extension of the synchronisation to include external data. Use for BAPI's or IDOC update to ECC documents | In order to provide QPPD objects with link to ECC documents data additionally with data, these can be announced before the call.passed to the successor.
Also included is an example BRF+ application: /SCT/QP_GEN | Use Methods of classe /SCT/QP_CL_SYNC_ADD_DATA in customer reports | NOTE-3163 | |
| Generation sequence for texts | The generation sequence now follows the lexicographic order of the generation method name | NOTE-3160 | ||
| DATA: QVC-DATA to DB-DATA | The IF_DATA interface previously only had the method MAP_DATA_DB_TO_QVC for converting from the format /SCT/QP_S_DB_DATA to /SCT/QP_T_QVC_DATA or /SCT/QP_TS_QVC_DATA. With the new method /SCT/QP_IF_DATA~MAP_DATA_QVC_TO_DB it is now possible to carry out the reverse transformation.
The GET_DATA method now also returns ET_DB_DATA if this parameter was requested and only ET_QVC_DATA was filled by the service. | NOTE-3139 | ||
| APPBUS available via Factory | The APPBUS class is now available through the FACTORY. | NOTE-3136 | ||
| FACTORY: Determination of instances when changing the scenario | If the scenario is changed, the internal buffer of the factory is retained and incorrect instances are returned. | Instances that are created via the FACTORY must not be buffered in static variables. | NOTE-3135 | |
| MAMBA value fields | Changing fields in MAMBA has been harmonized with the BUS: MAMBA only changes those fields that are contained in /SCT/QP_S_VALUEFIELDS. | If necessary, adapt structure /SCT/QP_S_VALUEFIELDS in order to change customer-specific value fields via BUS->CHANGE. | NOTE-3134 | |
| Global generation | Global generation has been technically revised. Global generation was executed too often or executed when it was suppressed. | NOTE-3130 | ||
| MM : Interface for class CL_MM_GUI | In order to solve the dependencies between QPPD Core and APP MM, an Interface /SCT/QP_IF_MM_GUI will be used. | NOTE-3119 | ||
| Post IDoc as an extension | If the QPPD-IDOC is included as an extension in another basic type, programming had to be laborious in the past so that posting was possible.
The new method /SCT/QP_IF_IDOC->DO_INBOUND_IDOC_BY_DATA enables this. For this, the Z parent segment must be transferred as IS_DATA. | NOTE-3114 | ||
| SYNCMODEL field in / SCT / QP_TVART deleted | The SYNCMODEL field has been removed from the /SCT/QP_TVART table. | NOTE-3093 |
Improvements
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | MAMBA_VIEW/ALV_GRID: too many flush | GUI-Performance optimisation | NOTE-3192 | ||
| Mamba : Performance LOOP ->FILTER | Performance improvement in MAMBA. | NOTE-3190 | ||
| MAMBA: Performance improvement uniqueness check | The performance of the uniqueness check in MAMBA has been improved. | NOTE-3128 | ||
| BUS optimization | Performance optimisation when export parameter "et_items" is not requested | NOTE-3118 |
Bugs
| Type | Schlüssel | Zusammenfassung_EN | Auswirkungen_EN | Implementierungsanweisungen_EN | Key |
|---|---|---|---|---|---|
 | Selection von VARTen in APPBUS and ECC-VART partly with error | When selecting nodes for an ECC GUID, partially wrong VARTs are read out for the ECC document depending on the existing data objects. | NOTE-3283 | ||
| BUS-error missing wenn processing a locked object | The BUS did not always generate an error message when the processed object was locked from another user. | NOTE-3273 | ||
| VART-Instance should be cleared when reloading nodes | When changes are rejected ( back to display mode without saving), the corresponding VART-Instance must be rebuilt. | NOTE-3267 | ||
| BRF+ Function call without return value generates error messages and aborts processing. | For example, if a decision table has no return value then the generation for the object type was aborted.
The note converts the abort message into an information message. No error is generated. The subsequent functions are executed. | NOTE-3244 | ||
| Update of LASTUPDATE | If due to very fast processing, a node is saved in the same second in which it was created or the current LASTUPDATE of the node corresponds to the current time, no new/different LASTUPDATE is set on the node when saving. This can lead to errors when reloading or when working with SHMO or other applications. | NOTE-3203 | ||
| TOE Default values are not generated | NOTE-3200 | |||
| SD translations | Texts in the SD GUI were not translated correctly | NOTE-3198 | ||
| Versioning: Checking for successor versions when deleting | When deleting nodes that could not be versioned, a check was carried out to determine whether they have successor versions. This improvement avoids these queries. | NOTE-3191 | ||
| BRF+ Return Elements without the VALUE addition, do not return any values | missing values | Implementation Note-3187 | NOTE-3189 | |
| BRF* Dump using elements with unit | BRF+ Dump when using elements with units | Implementation Note 3187 | NOTE-3188 | |
| A generated value is not transferred to Mamba | When generating values in MAMBA, no values were written back if MODEREF and values were specified at the same time. | NOTE-3185 | ||
| RFC Service faulty data transmission | When connecting via RFC, instances of classes are only created once via the systems. For singleton instances, the constructor is therefore only called once. If different system settings are available, only data from the source system is used. This can lead to different incorrect data transmissions. | NOTE-3184 | ||
| TOE Text determination | The short text associated with the value was always in logon-language, even if another language was requested | NOTE-3183 | ||
| Splitter data transfer | If data was entered on an object type but not explicitly confirmed with ENTER and then another item type was selected in the tree, the data was not transferred to the object type. | NOTE-3182 | ||
| MAMBA: Sort numeric, horizontal fields | Sorting numeric fields from the horizontal element was not possible. | NOTE-3181 | ||
| Changes in view /sct/qp_mm_tcoppf can not be saved in S4/HANA | Affects S4 / HANA and the APP MM. A short dump occurs when data is maintained in the C72 (data for copy control). | NOTE-3180 | ||
| F2 function "edit values" | When editing field contents (value fields for elements) the F2 key can now be used to select the field and to position the cursor at the end of the value. | NOTE-3179 | ||
| Deletion of info records does not take into account the deletion of position nodes | nfo record deletion based on position data has not been called yet. Info records for position nodes are retained even though they are no longer valid. | NOTE-3178 | ||
| Converting value 0 from MM into INCH | An error occurred converting values when the value is 0. | NOTE-3177 | ||
| BUS: Syntax check for element values | Internal fields were not saved correctly when creating elements via the BUS. | NOTE-3176 | ||
| When sorting the data to be saved, the TYPE field is missing for cs_db_data-num. | No duplicate keys when saving the data if "NUM" is active | NOTE-3175 | ||
| TOE buffer for global generation | If the TOE is used in an object and the GG is executed, the TOE collects MAMBA lines to be checked. These are processed according to the GG. However, if nodes have been deleted during the GG for which the TOE has noted MAMBA lines to be checked, a shortdump occurs. | NOTE-3174 | ||
| SHMO: deleted nodes | If the SHMO is used for an object and nodes are deleted, the SHMO data service has incorrectly returned the node that has already been deleted from the database. | NOTE-3173 | ||
| Name generation: Only capitalization for constant values | The name generation only worked with capital letters when working with constants. | NOTE-3172 | ||
| TECHM: Structure / SCT / QP_SV_TECHM_GRID uses obsolete search help | Affects S/4 HANA and the object type TECHM. The structure /SCT/QP_SV_TECHM_GRID creates a short dump because of the search help used. | NOTE-3171 | ||
| Objects marked as "changed" unnecessarily | Objects are unnecessarily marked as "changed" when they are loaded. | NOTE-3170 | ||
| TOE: Short dump if the domain does not exist | If an element uses a domain as a search help and this domain does not exist, a short dump is created. | NOTE-3169 | ||
| SYNC of VBAK-fields on QPPD-position Object | Header data that was maintained on the VBAK-level was not always copied on QPPD-Objekt attached to VBAP | NOTE-3168 | ||
| IDOC PMK segment | QPPD distribution via IDOC: Adjustment of the /SCT/QP_QVC_PMK_2V332 segment. Segment /SCT/QP_QVC_PMK_3_V332 deleted. | Z-IDOC extensions that include the QPPD standard IDOC must be adapted. Z-IDOC extensions of the QPPD standard IDOC are not affected. | NOTE-3167 | |
| Status change via dropdown menu on the STATUS object type | If the status was changed via the drop-down menu on the STATUS object type, QPPD internal functions according to MVC were bypassed. | NOTE-3165 | ||
| Catch exceptions when starting QPPD | Exceptions were not correctly caught by the QPPD when it started and caused a short dump. | NOTE-3164 | ||
| MAMBA: Items were not deleted | When, on the same object type, data is simultaneously changed and deleted, the deletion may be omitted. | NOTE-3162 | ||
| Instantiation of VART classes | Instances for VART classes were not determined in the event of an error. | NOTE-3161 | ||
| Wrong error message for external lock | If an object is locked, the text of the error message was sometimes generated incorrectly. | NOTE-3159 | ||
| MAMBA_VIEW: Search-help on not editable fields | It was possible to use the search help to enter a value in a non-editable field. | NOTE-3158 | ||
| MAMBA STATELM = R for column elements | If a conversion error has occurred, the status (STATELEM) for dynamic elements has not always been set correctly. | NOTE-3157 | ||
| TOE Conversion of specification to search help regulation types | The search help for specification types represents VNR numbers with leading zeros. | NOTE-3154 | ||
| Programs for reorganising and updating VNR faulty | The programmes /SCT/QP_UPDATE_VNR and /SCT/QP_REORG_VNR have not always updated all tables. | NOTE-3153 | ||
| Catching exceptions during global generation | Under certain circumstances some error messages will be lost during global generation | NOTE-3151 | ||
| PP: missing BOM in plan order and MRP run | The QPPD BOM explosion is not called. Missing material and component quantity | NOTE-3150 | ||
| Deletion from BOM-Nodes | If original nodes are deleted, all BOM usages must also be deleted. | NOTE-3149 | ||
| GUI drag & drop with multiple nodes | If several nodes are dropped using drag & drop and at least 2 nodes use the same reference, a DUMP happens. | NOTE-3148 | ||
| Search help for TVBOCK not available | Search help for TVBOCK not available | NOTE-3147 | ||
| APPBUS->GET_LINKS_FOR_DOCS: missing results | If not all QPPD objects for an ECC document have been loaded in the memory, then not all relations to an ECC document have always been returned | NOTE-3146 | ||
| When transferring data via RFC, child nodes are truncated | When transferring data via RFC, child nodes are truncated in target system | NOTE-3145 | ||
| Workmode changed too often | These unwanted workmode changes have a negative impact on performance and can even generate incorrect results in the TOE context check. | NOTE-3144 | ||
| Field ALTZEUGEINH not completely supported | The new field ALTZEUGEINH was not 100% supported | NOTE-3143 | ||
| the VART instance should be freed when the VART will be freed | Under some circumstances, the VART instance delivers wrong data when the VART has been unloaded from memory and reloaded afterwards | NOTE-3142 | ||
| Deletion of sales order position causes dump. | Wenn several sync models are active, deleting a sales order position can lead to dump because some objects are already deleted while the 2nd sync model is processed, | NOTE-3141 | ||
| TOE : Select VC-values | NOTE-3140 | |||
| ROWGRP is not always properly set | While copying Objecttypes with different element groups ( for example, the source data has no dyn. columns, the target data base some ), then temporary ROWGRP have to be created.
the new ROWGRP was however not copied in all other internal structures. | NOTE-3133 | ||
| Context menu during multiple selection in main-tree | Context menu for multiple selection in the tree | NOTE-3132 | ||
| Loss of data when deleting nodes with primary references | If a node with a primary reference is deleted and the primary reference is a node from its own object, then this node is erroneously deleted as well. | NOTE-3129 | ||
| SYNC_SD correction for Note 1834 : unwanted lines in FDM | Under certain circumstances, unwanted lines appear in the fast data maintenance screen for the sales order. | NOTE-3127 | ||
| Info table creation with fields from sales documents missing | When using the class /SCT/QP_CL_INFO for updating the info tables and using the key fields VBELN and POSNR from the sales and distribution document, the assignment is made via the VERT-VNANME = CUOBJ number of the sales and distribution document. With this enhancement, this assignment is created using the document link class $ECC. Additionally, schedule lines of the sales document can be used. | Only relevant when using the /SCT/QP_CL_INFO class and info tables with VBELN and POSNR fields. Overdefinition do_map_val_to_structure in the Z info class and and production of the commented out program parts with the note from release 3.20 | NOTE-3126 | |
| TOE _ON_VART no consideration of ROWGRP for multigrid | NOTE-3125 | |||
| Synchronisation transfers no units | When the sales order item of the sales unit is synchronized, the unit is not transferred to the requirement specification. | NOTE-3124 | ||
| Detection of nodes in the model with duplicate name returns wrong node | Wrong search of nodes in case of duplicate name assignment. The case occurs when ECC-Link is used to link multiple documents that have the same name. | NOTE-3123 | ||
| CONV: Negative FLOAT values | If the conversion method is of the "number" type and a negative value is to be converted, then the additionally calculated FLOAT value was incorrectly returned as positive during the conversion DB_TO_OUT. | NOTE-3122 | ||
| CHGDOC: Read VAL values from change documents | Reading the VAL values from the change documents did not work properly. | NOTE-3121 | ||
| Action Log: Reorganise | The reorganization of the Action Log using the Report Log /SCT/QP_DEL_AL does not work correctly if the deletion is done using
a) TRUNCATE or b) via selection options left empty should be executed. | Existing jobs for reorganizing the action log must be revised. | NOTE-3120 | |
| TOE: Endless loop within context-check for elements with blank values | If an element contains a context check and the content is empty, QPPD in an endless loop tries to find the value. | NOTE-3117 | ||
| Flags in VAL/PMK are not transfered if changed by BUS | Flag fields in VAL and PMK now get correctly transfered by using BUS methods if other valuefields are initial. | NOTE-3116 |