© All rights reserved D'PROS Innovation 2020 November

fvarr

Table of Contents

Support Lifespan

What's New?

System Requirements

Installation Procedure

RainbowSAP 4.11

Release Highlights

2

Support Lifespan Version 4.11 of RainbowSAP suite release date is set to 2020 November.

Support for older versions will be maintained till 2021 April.

Following that date, D'PROS will no longer provide fixes, updates and assistance for older

versions. We highly encourage our customers to perform the version upgrade prior to this

date.

3

What's New? The following table is a summary of new features and bugs fixed added in version 4.11.

Table 1: Cross-Application - New capabilities -

# Feature Description

1 /DCM/JOBREPORT: Variant Field In transaction /DCM/JOBREPORT the ALV output was enhanced with step's report variant and variant text fields.

2 File Viewer: CSV File Viewer (/DCM/FILE_VIEW) now supports also CSV files.

Table 2: Cross-Application - Bug Fixes -

# Bug

1 When a transaction was being executed on SAP GUI for HTML (Web GUI), all the links in the selection screen page (Get variant..., Favorites, etc.) didn't work (didn't do anything).

2 In the file viewer (/DCM/FILE_VIEW), the (default) columns position might have been incorrect: The column position was set according to alphabetic order, which means that column AA arrived before B, for example.

3 In the file viewer, selection of ALV layout in the selection screen didn’t set the ALV layout.

4

Table 3: Publisher - New capabilities -

# Feature Description

1 New Distribution Method: Fiori Notification

A new distribution method was added: Fiori Notification (These are notifications which are displayed in the Fiori launchpad). This feature requires NW 7.51 or above (and FES 3.0 or above) and is delivered in standalone CR. Configuration guide can be found in appendix A.

2 Business Entity Type: Business Partner

A new business entity was introduced: business partner. BP - Address-independent B2 - Address-dependent (Standard address)

3 Business Entity Type: Sales Office

A new business entity was introduced: SO – Sales Office. (Email addresses of sales offices can be maintained in the SAP-standard transaction OVX1).

4 Snapshot: Append During publish to snapshot, write mode was extended with Append option (in addition to Create new and override). This option allows to append records to an existing snapshot (Report fields/metadata must match the ones of the existing snapshot).

5 Split by Record There is a new option of “Record Split” to create a separate publish (email, SMS, etc.) per record.

6 Decimal Format - Optimize Decimals

A new parameter was added File format – Formatting: Optimize (Decimals). This parameter controls whether to optimize decimal values (remove redundant decimals). e.g. 7.00 will be displayed as 7. This option is irrelevant for XLS/XLSX files.

7 Text Symbols Enhancement The email subject and contents (text name) were enhanced with new text-symbols for setting dynamic content: Number of records, date/time and ALV fields (value and value’s text). In the standard text’s dialog, "Program Symbols..." button now displays the list of related symbols. For subject, an Insert variable button was added to allow quick addition of text-symbol. The same functionality was enabled also for SMS contents.

8 E-Mail - Blocklist Recipients Blocklisted email-addresses can now be maintained via transaction /DCM/PUBLISHER_BLIST. E-Mails won’t be sent to blocklisted addresses.

9 E-Mail Distribution Method Validation - BAdI

BAdI /DCM/ADA_DIST_METHOD_BADI was introduced to allow custom validation checks against the email recipients (e-mail addresses).

5

10 Support Logical Transaction Publisher was enhanced to support logical transaction (for reports w/o transaction), in similar to what is done in Rainbow. Direct input of report w/o transaction (for users with authorization object /DCM/PBADM with ACTVT=70 - "Administration") isn’t possible anymore.

11 Security: CSV Injection Safe In order to protect of CSV injection vulnerability in Spreadsheet viewers, Safe parameter was added to the selection screen (Checked by default). When being set, apostrophe (‘) prefix is automatically added in case the cell value starts with: Equals to (“=”), Plus (“+”), Minus (“-“) or At (“@”).

12 Subtotals: Separate Column for Total's Hierarchy Level

For publish of reports with totals/subtotals, the hierarchy level (e.g. *) is being set in a separate column instead of being concatenated into the first column.

13 Snapshot Where-Used In customizing /DCM/PUBLISHER_IMG -> Snapshots -> Define Snapshot Keys a Where-used function was added. It contains a list of:

• Publisher jobs which create a snapshot.

• Rainbow variants for snapshots: Where snapshot is being used as data-source and/or in Table lookup column.

14 SMS: Remove Restriction of 60 Characters

In SMS, content isn’t restricted to 60 characters anymore.

15 Export Report Variant/ALV Layout (of Original Report)

Export of Publisher job now support also export/import of the report variant and the ALV layout of the original report.

16 Export Sub-Variants Sub-variants are now being exported (and imported) as part of Publisher job export.

17 Split by Selection Screen Parameter: Support Empty Value

In case of split by selection screen parameters (in multiple selection), in the sub-variants screen, setting an empty value for parameter is now supported: In case an empty value is set for Select-options a single equal empty value would be set (instead of an empty range (all values)).

18 Handle Exception and Box Columns

Report which include box (selection) and/or exception (lights) columns are now being handled and the value is being omitted instead of being concatenated to the first column.

19 Monitor: Rainbow Snapshot ID A new column was added to the monitor to display the snapshot key in case of Publisher job of Rainbow which is based on snapshot.

20 Monitor: Refresh Active Jobs A new submenu button “Refresh Active Jobs” was added to the monitor toolbar, to allow refresh only of active jobs, in similar to the available option in auto refresh.

21 Monitor: Execute Original Report

In the publisher monitor, Execute original report function was added for quick execution of the original report via selection screen/directly.

6

22 Navigate to Rainbow Variant Publisher monitor and selection screen were enhanced with a hotspot/button for quick navigation to the Rainbow variant in case of Rainbow-based jobs.

23 Export Filename Suffix During export of Publisher job, the suggested filename includes suffix pb.XML to better distinguish between Publisher and Rainbow export files.

24 XLSX: Column Width - Default: Optimized

The default value of column width for XLSX was changed to O - "Optimized to content" instead of A - "Automatic".

25 Selection Screen: New Buttons The selection screen of Publisher was enhanced with new buttons:

• E-Mail - Graphics file – Navigate to maintenance of graphics files (transaction SE78).

• E-Mail – Standard text – Display text (in addition to the existing Create/Change button).

• Snapshot – Navigate to snapshot list (transaction /DCM/PUBLISHER_SNAP).

Table 4: Publisher - Bug Fixes -

# Bug

4 For distribution method File Directory, the max length of the complete filename (path + filename + extension) was restricted to 128 characters and longer filenames were truncated. It may have led to unexpected files, like files w/o extension.

5 In case of report variant whose parameter was set with "Save Field Without Values" (NO_IMPORT), for some data types (date, time, etc.), an empty value was sent and overrode the internal value set by the called report although value shouldn’t been set.

6 During output of an ALV with subtotals, the generated file was incorrect in case at least one of the subtotal columns is hidden (not displayed): The position of the (total) columns in the subtotal/total rows was incorrect (before the actual column position).

7 In an extreme case in which subtotals are defined, but no totals (Totals isn't defined for any of the columns and/or a column with totals is hidden), setting split by selection screen parameter raised error message /DCM/ADA 117 - "Field is not contained in the data stream for totals records" although there aren't any real subtotals.

8 During publish in HTML the following color inconsistencies might occur in case of a report with subtotals: 1. In subtotal/total lines, the key columns (cells of key columns) were colored in the color of Key (Blue) instead of subtotal/total row color. 2. In total line, the subtotal columns (cells of subtotal columns) were colored in subtotal Yellow (Light Yellow) instead of total Yellow.

9 During publish, the contents of the first field had leading (redundant) spaces.

7

# Bug

10 In case of multiple job with split by dynamic selection field, invalid dynamic selection value (e.g. value too long) may have led to runtime error in subroutine /DCM/ADA_PUBLISHER TEXPR_PARAM_SET (e.g. CONV_EXIT_FIELD_TOO_SHORT).

11 In case of multiple job (with sub-variants) with split by a dynamic selection field, In case the report variant includes dynamic selection values, the dynamic selection values weren't being selected at all (not the ones defined in the variant nor the split value).

12 In some reports (e.g. FBL5N), a special control break is set, which split the spool into separate blocks. This may have led to unexpected parsing: e.g. the block header was concatenated to the next line, instead of being ignored.

13 In case of copy of a multiple job with sub-variants, after the sub-variants dialog was displayed and save is pressed, popup "The variants does not exist" appeared for every sub-variant to be copied. After confirming these popups, the program continued as expected and the sub-variants were copied.

14 When SMS distribution method is being used, in case no phone number is maintained for business partner, warning message /DCM/ADA 109 - "No telephone numbers maintained for partner Business Partner" was issued. However, job status was Finished instead of Partially completed.

15 When the distribution method block was collapsed, the active distribution methods weren’t listed in some cases for e-mail, SMS and snapshot.

16 In the Publisher monitor, it is possible to mass update background jobs (background user and/or server) by selecting multiple (scheduled) jobs and pressing on Update Job Attributes. Due to bug, the corresponding 'Set' checkbox of server was displayed even when Server input wasn't enabled (Whether input of background user was enabled or not).

17 In the Publisher monitor ALV, the value of transaction code for Rainbow-based jobs was empty.

18 In multiple job with sub-variants, in case there are recipients for the first record, no further checks were done and no error messages were raised for other records even when no recipients were set.

19 In case of split by multiple selection, in the sub-variants screen is a dropdown input field for Sender Type (in case sender wasn't explicitly set in the main variant). Dropdown contained empty values instead of E (Email) and U (User).

20 When setting a transaction code/report, filename is set automatically with the report name. In case the report name contained slash ("/"), like in case of ABAP query, error message SWF_EXP_001 025 - "Syntax error at pos. 4: Symbol '/' cannot be used here" was raised.

21 In "Read in local memory" mode, in case a column heading included "|" character, the file was being corrupted. * When “Read in local memory” isn’t set, the file is still being corrupted.

22 Changes of SMS Text weren't saved in change documents.

23 Text of dynamic parameter ($P$) wasn’t set when BAdI /DCM/ADA_BADI isn't Implemented.

24 The value of parameter "Multi spec descr." Hasn’t been validated, what may lead to runtime error in method /DCM/CL_CA_DD_ELEM_TYPE=>ELEMDESCR_GET (Called by /DCM/CL_CA_DISTRIBUTOR=>USER_DEFINED_TEXT) due to uncaught exception /DCM/CX_CA_DDIC_FIELD_INVALID.

8

# Bug

25 When "Read in local memory only" option is set, in case no data was returned (ALV wasn't displayed at all), runtime error GETWA_NOT_ASSIGNED occurred in subroutine /DCM/ADA_PUBLISHER_PRC data_from_table_ref.

26 In the selection screen the SMS content button was enabled for input even when variant is called in display mode.

27 In File Directory, the search help for physical file name allowed to list all the files in application server even if the user isn’t authorized. This functionality was restricted by adding an authorization check against authorization object S_ADMI_FCD with S_ADMI_FCD = ST0R (Authorization to analyze traces), in similar to what is done in transaction AL11 (note 2940881).

9

Table 5: Rainbow - New capabilities

# Feature Description

1 Grouping - KPI Groping was enhanced with KPIs. A KPI can be defined (aggregated value of column) and assigned to group. The KPIs are displayed both in SAP GUI grouping tree and in the SAPUI5 app.

2 Send - Share Link (Permalink)

Send via Outlook was enhanced with new option “Content link”. When being set a (perma)link to the report (via ITS) will be generated. The link will navigate directly to the Rainbow variant with the selected report variant, ALV layout and the selected rows. Generated links should be periodically deleted by scheduling a background job of report /DPS/RET_LINK_DEL (It’s recommended to delete links older than one month).

3 Comment Collaboration As part of creation of a new comment it’s now possible to assign collaborators (recipients). These collaborators would receive automatically an e-mail with the comment contents, including a permalink to the report.

4 Applied Painting Rules It’s now possible to apply painting rules locally (Instead of activating them for the whole Rainbow variant). Applied rules are saved as part of the ALV layout.

5 Grouping - Display As ALV

A new button was added to Grouping tree: Display table. It allows to display the grouping as ALV table instead of tree. This view is also available for direct execution via Publisher (i.e. publish the grouping values).

6 Direct Execution of Detailed List (Non-Aggregated)

For Rainbow variants with aggregation mode, an option to directly execute the report in Detailed (non-aggregated) view. This option is available both in Publisher and in API call (method /DPS/CL_RET_RAINBOW_API->CALL_TRANSACTION).

7 Grouping Tree: Intersection

New function Intersection was added to grouping tree. It controls whether to display intersection or union of record during selection of multiple groups.

10

8 Variables Input/Output Authorization

Variables were extended with authorization group attribute. This allow to grant user authorizations to display and/or update variable value. Authorizations are being checked only when an authorization group is set. These authorizations are in addition to the standard maintenance authorization in authorization object /DPS/RET for Rainbow makers. A new authorization object was introduced: /DPS/RETV with the following values for ACTVT:

• 35 (Output) – Display variable.

• 34 (Write) – Update value of variable.

• 78 (Assign) - Set value of authorization group. If user has no authorization, he won't be able to set this value of authorization group.

• 02 (Change) - Change variable. If user has no authorization, he won't be able to change the variable (attributes).

9 Long Text Column: Use Alternative Language

In Long text column, “Use alternative language” attribute was added. It controls whether to select text in alternative language if no text was found for the input language.

10 Aggregation Function: Existence Check

New aggregation function EXIST (Existence Check) was added to the list of available aggregation functions of DB Lookup/Table Lookup columns and graphs. The function returns a boolean (XFELD) whether a record was selected or not. In case of graphs, the function is interrupted as 0/1 (If record exist - Value is 1).

11 DB Lookup: Aggregation Function Median

In DB Lookup column, aggregation function Median was added (only for numeric fields).

12 SAPUI5: Period (YYYYMM) Format

Period data elements (SPMON, /DCM/MONTH_YYYYMM) are now supported in the SAPUI5 app to display a period value (month/year) instead of a simple text. This is relevant for both Table and Charts.

13 SAPUI5: Currency and Unit Columns

For amount/quantity columns with reference currency/unit of measure, the values are displayed with the reference currency/unit (e.g. 30.00 USD). This feature can be switched off by setting parameter rainbow-unit=false.

14 SAPUI5: Charts - Time Axis

For charts with X axis of date/time, standard charts were replaced with Time axis charts which better present the time dimension. Relevant for char types: Columns, Stacked Columns, Line.

15 SAPUI5: Graphics - Handle "Display Initial Values"

Graphs with "Display Initial Values" is now handled in the SAPUI5 app.

11

16 SAPUI5: Charts - Count Unique - Handle Initial Values

In the SAPUI5 app, charts with count unique now handles initial values to display consistent results like in SAP GUI charts.

17 SAPUI5: Indicate Navigated Item

When navigating to a group the navigated group is highlighted.

18 SAPUI5: Charts - Formatting of X/Y Axis

In SAPUI5 Charts, the values are formatted for better readability: X Axis – Formatted according to column datatype. Y axis – Formatted with short formatting.

19 SAPUI5: Remove Empty List Groups

When an ALV filter is applied, For List groups, empty (w/o any filtered records) groups aren’t displayed. Empty static (standard) groups are still displayed.

20 SAPUI5: Filter Infobar Filter infobar was added.

21 SAPUI5: Alignment of Numeric Columns

Numeric columns are now right-aligned for better readiness.

22 Key Suggestion During initial setting of key, in case the original report contains a key, the key may be auto-suggested.

23 Links Navigation The following navigation have been implemented: /DCM/FILE – Open (local) file /DCM/URL – Open URL in web browser /DCM/EMAIL – Open email with email address (send to) /DCM/TELF – Open dialer with telephone number (call to) Corresponding data elements (with an automatic assignment to navigation) were added to the Recommended data elements search help. * Values are restricted to 70 characters length due to system limitation.

24 Call Rainbow Transaction (API) - Filter

API method /DPS/CL_RET_RAINBOW_API->CALL_TRANSACTION was extended with an option to add a filter (in ALV level) on top of ALV layout. This may allow, for example, display Rainbow for a specific document. Parameter IV_FILTER was added. The expected format is: <ALV_FIELDNAME1>=<VALUE1>$<VALUE2>;<ALV_FIELDNAME2>... (e.g. LIFNR=1000$2000) (It supports only list of EQ values) In addition, simple parameter IT_ROWKEY was added to filter by record key.

25 Variables: Order New attribute sequence number was added to variables. It controls on the order of the variables in the variables view.

26 Variables View: Value Description

The variables view was enhanced with the description of the value (e.g. Name of company code).

12

27 Variables View Visible By Default

In case of Rainbow variant with input/output variables the variables view should be visbile by default (This can be manually changed later by saving a default ALV layout).

28 New Aggregation Functions: Standard Deviation, Variance

Aggregation functions Standard deviation and Variance were added to the following objects: Aggregate context-menu, List count with aggregationn, Aggregation column, DB Lookup column, Table Lookup column

29 Formula Function: COALESCE

The following formula function was added: COALESCE - Returns the value of the first argument which is not initial.

30 Copy Column: Column Position

In case of copy column, the position of the new column is now set after the copied column (instead of at the end of columns).

31 New Column: Scroll to Column

After adding a new column (via Create/Copy column), the ALV is automatically scrolled to the new column.

32 Remove Setting of Default ALV Layout

During execution of Rainbow variant, the ALV layout of the original report was set temporarily as the default layout for all users. This may have led to inconsistent behaviour in extreme cases in which the report was executed multiple times in parallel. ALV layout isn’t being set as default anymore.

33 Paint Rule: Display / Copy

Functions Display/Copy were added to paint rules.

34 Context-Menu: Columns The context-menu of column was extended with sub menu Columns which contains list of functions relevant for column: Overview, Create and Display, Change, Copy when a single column is selected. Function Create Reference Column was also added for quick creation of columns (Aggregation, Text, Comment, Input info) based on the selected column.

35 Table Lookup Context-Menu: Snapshot Timestamp

For table lookup columns, the context-menu was extended with function (Column → Snapshot) to display the timestamp of the snapshot.

36 Change Documents Context-Menu

For input columns, the context-menu was extended with function Input Change Documents to display change documents for the selected column/records.

37 Context menu: Color All color-related functions in context menu were reorganized under one sub-menu: Color.

38 Create Variant - Translation

Translation function is now available directly during creation of Rainbow variant (not only on update).

39 Toolbar Function - Refresh Attribute

The configuration of Rainbow toolbar functions (for a specific Rainbow variant) was extended with attribute Refresh. This may allow to override the default refresh definition in the customizing.

40 Export Filename Suffix During export of Publisher job, the suggested filename includes suffix rb.XML to better distinguish between Rainbow and Publisher export files.

13

41 Formula Function / Toolbar Function Where-Used: Print Preview

In Customizing /DPS/RAINBOW_IMG -> Define Toolbar Functions and Define Formula Functions, Where-used popup now supports print preview.

42 Formula Functions - Help

Help (documentation) was added to customizing /DPS/RAINBOW_IMG -> Define Formula Functions

43 Function Where-Used: Navigation to Rainbow

In the customizing of Define Toolbar Functions / Define Formula Functions there is a Where-used function which lists the Rainbow variants where the object is being used. Hotspot for quick navigation to the Rainbow variant was added.

Table 6: Rainbow - Bug Fixes -

# Bug

1 After deletion of a column from report (custom column or standard column which was removed from the original report), in case the ALV layout contained filter on the deleted column, runtime error ASSERTION_FAILED might occur in method CL_SALV_BS_FILTER->DO_STRATEGY_DYNAMIC_WHERE.

2 In case of Rainbow-based variant, it was still possible to set checkbox "Variants for Sel." (VARI_SEL) in the variant attributes (in tab Transaction). It could lead to inconsistencies, especially in Publisher.

3 In Change column, in case a standard column is defined not from dictionary (w/o data element / reference field), error message 00 055 - "Fill in all required entry fields" was raised and changes couldn’t be saved. Hence, column heading and/or authorization couldn’t be changed.

4 In formula column and/or group, in case the formula includes a column w/o display authorization (for this specific end-user), the column wasn't evaluated and error was written to log (/DCM/CA 253 - "The syntax in the formula is incorrect", SFB 532 - "Formula element is not allowed here") although it should be supported.

5 The column heading of standard columns (of the original report) always shown the long text, instead of a dynamic text according the width of the column.

6 In case of multiple aggregation columns for the same grouping, the calculation might have been incorrect: Values were empty or multiplied.

7 In cases of standard/DB Lookup columns, a reference table field might be available internally. When a foreign key is defined in the table/structure level and not in the data element itself (values table), text column couldn’t be set.

8 After change of the key columns, the key attribute of added/removed key fields wasn’t updated immediately in the ALV output.

9 In case of aggregation function median, the calculation returned incorrect results in case of even number of values: Instead of the average of the two median values, it returns the values of the median and following value.

10 In case of an input column with referenced aggregation column (which aggregates this input column), any update of value updated the aggregated values and refreshed the ALV table. Due to bug, this distorted the sorting/filter of the ALV.

14

# Bug

11 For DB Lookup columns, in case the criteria is non-unique and contains mapping to fields with : 1. At least one EQ mapping to field. 2. At least one not EQ mapping to field. The results might be incorrect : Data was set only for the first record and value remained empty for other records.

12 In case a DB Lookup is defined with an invalid (deleted) DB table, runtime error might occur due to uncaught exception /DCM/CX_CA_DDIC_TABLE_INVALID in method /DCM/CL_CA_DD_UTIL->DDIF_TABL_GET (Called by /DPS/CL_RET_COLUMN_DB_LOOKUP->DB_FIELD_VALIDATE).

13 For DB Lookup/Table Lookup columns with aggregation function, the aggregation wasn't calculated in case both conditions occur: 1. The value of the field in the first record is initial. 2. No Key fields are specified or all key fields have an initial value.

14 In DB Lookup/Table Lookup columns, changing the selected field may lead to update of the checkbox attribute (in case old field was checkbox and new one or vice versa). The change wasn’t reflected immediately in the ALV output. Moreover, in case a checkbox column was changed into numeric column, runtime error UC_OBJECTS_NOT_CHARLIKE occurred in subroutine LSLVCF05 DATA_TABLE_GET.

15 In Table lookup column, aggregation function median was available also for non-numeric columns, although it isn't supported.

16 On maintenance of Long text column, the search help of language (TDSPRAS) didn't set the selected.

17 In aggregation mode, when column which is set as a key column was deleted, runtime error OBJECTS_OBJREF_NOT_ASSIGNED (exception CX_SY_REF_IS_INITIAL) occurred in /DPS/RET_RAINBOW subroutine NEW_COLUMN_IN_USE.

18 In Rainbow navigation, the navigation was restricted to 30 characters instead of 70 (longer values were being truncated into 30 characters).

19 Execution and/or export of original report variant which include a selection screen parameter of type structure/table led to runtime error UNCAUGHT_EXCEPTION due to uncaught exception CX_PARAMETER_INVALID_RANGE in method CL_ABAP_ELEMDESCR=>GET_C (called by /DCM/CL_CA_SELSCREEN_UTIL=>IS_PARAM_VAL_INITIAL).

20 During copy of graph, in case the graph is with aggregation function CNT_U and Y axis is non-numeric, error message /DPS/RET 105 - "is not numerical" was raised and graph couldn’t be copied.

21 In case of graph with value in percentage, SAP GUI charts displayed negative values as positive ones (e.g. -100% is displayed as 100%, while the value label was correct: -100%).

22 In graphs, initial value of data type Time was displayed as NA instead of 00:00:00 (12 AM).

23 When graph title included Hebrew characters with numeric digits w/o spaces (e.g. 12345 678901345ג ), the title was displayed incorrectly: The Hebrew letters always moved to the first/last position.

24 In the SAPUI5 app, in case the x axis column is of type date/time, the displayed values were incorrect: Only the first value was displayed instead of aggregated value.

25 In the SAPUI5 app, column headings and columns with links were truncated instead of being wrapped.

26 In Rainbow variants based on ABAP Query, in case the ALV layout included a filter, the filter hasn’t been applied.

15

# Bug

27 When setting a comment, multiple spaces were condensed (e.g. "first second" was converted into "first second").

28 During copy of column there was no authorization check for copy of the selected column kind (Authorization object /DPS/RET: /DPS/RETOB='C', /DPS/RETSB=Column Kind, ACTVT=90).

29 On the graphs overview, deletion of graph might have led to runtime error OBJECTS_OBJREF_NOT_ASSIGNED (exception CX_SY_REF_IS_INITIAL) in /DPS/RET_RAINBOW subroutine GRAPH_DELETE.

30 In case of error in graphs due to invalid graph (column doesn't exist, etc.), no errors were displayed in the log (although the graph wasn’t displayed).

31 In case of secondary update of formula of variable, the value of the variable hasn't been updated immediately (But only on the next execution of the Rainbow variant)

32 After creation of a new variable, the Log button wasn't available in the ALV toolbar even in case the variable was invalid and errors/warning are available in the log.

33 In case a variable was deleted, its corresponding records weren't removed from the log (in case of an invalid variable. e.g. empty formula). A subsequent display of log might have led to runtime error due to uncaught exception /DPS/CX_RET_VARIABLE in method /DPS/CL_RET_VARIABLES=>VARIABLE_GET (Called by /DPS/CL_RET_LOG=>DISPLAY).

34 During creation/update of aggregation column, it was possible to define an aggregation for column w/o authorizations (technically hidden). This allowed to bypass the column authorization and reveal the values behind it.

35 No change documents were created in the followed cases:

• Update of the display option of variable.

• Deletion of column.

36 In the Rainbow monitor, Execute original of logical transaction always led to error 5A 484 - "You are not authorized to use transaction" even if the user has authorizations.

37 In the variant attributes screen, the search help for transaction code passed the report name to the search help and restricted the search although it’s irrelevant.

38 In the variant attributes screen, when an invalid report (non-existing/imported from other system) is set, runtime error might occur due to uncaught exception /DCM/CX_REPORT in method /DCM/CL_CA_SELSCREEN_UTIL->IS_REPORT_WITH_SELSCREEN.

39 In some extreme cases import of Rainbow variant could lead to runtime error due to uncaught exception CX_SY_STRUCT_COMP_NAME in method CL_ABAP_STRUCTDESC->CHECK_COMPONENT_TAB (called by /DCM/CL_CA_ALV_UTIL->LAYOUT_IMPORT).

40 It is possible to import a variant with invalid/unsupported column type (When variant is exported from a system with newer release to older one). This led to runtime errors (e.g. uncaught exception CX_SY_CREATE_OBJECT_ERROR in method /DPS/CL_RET_COLUMN_CUSTOM->COLUMN_FACTORY).

41 In SAP GUI, in case of average calculation for Integer, the value is rounded to integer (e.g. average of 6, 7 will return 6). In the SAPUI5 app, on contrary, the average was rounded always to 2 decimals places. This led to inconsistencies between the charts in the UI5 app and in the SAP GUI.

42 In some extreme cases in which the default method for Display which is defined in business object is different from Display (e.g. BUS2097), the navigation to the object didn’t work.

16

# Bug

43 In customizing “Define formula function”, the description couldn’t be set. It was overridden with the value of status (e.g. @08\QImplemented@).

44 In customizing "Define Objects Navigation", in case a value was entered in Authorization Transaction field during new entry, it was automatically cleared on Enter.

17

Table 7: Changer - New capabilities

# Feature Description

1 Timeline - Multiple Records

Timeline view now supports selection of multiple records (of the same table). This view is also available directly in the selection screen (i.e. the report can be executed in timeline view instead of standard changes mode).

2 Timeline - Save Layout It’s now possible to save ALV layouts in Timeline view (the layouts are in change document object/table level).

Table 8: Changer - Bug Fixes -

# Bug

1 In case the primary table of the change document object is a structure (and not DB table/view), selection by object criteria might led to runtime error SAPSQL_NO_DBTAB_OR_VIEW (exception CX_SY_DYNAMIC_OSQL_SEMANTICS) in subroutine /DCM/CLRL_OBJECT_CHANGES_PRC DB_TABLE_OBJKEY_SELECT.

2 During the import of Changer CR to new S/4HANA releases, error "No component exists with the name 'VAKEY'" might occur in class /DCM/CLR_DATASOURCE_COND .

18

Table 9: IDoc - Bug Fixes -

# Bug

1 In case of different IDoc types with the same prefix (16 characters long), the ALV layouts was shared instead of being separate. e.g. SHP_OBDLV_SAVE_REPLICA01 SHP_OBDLV_SAVE_REPLICA02 shared the same ALV layouts (since both have the same prefix SHP_OBDLV_SAVE_R).