irmipm 60e sp3: release notes - vistex, inc · can change general data, dates, partners, texts and...

Area Sub‐Area Type of Change Transaction Code Topic ChangesAgreements Agreement Copy New Functionality /IRM/IPxxASP Copy Schedules and Periods New in Release E SP3, a copy function for Schedules and Periods has been introduced. When

users reference the agreement when copying with the same validity date, the system will populate two new options for users to check the copy schedules and copy periods. These are available only when the user is copying with the same validity dates. If the agreement is copied with a new validity, these two options will not be available.For more information, please review the Copy Schedules and Periods Document.

Agreements Awards New Functionality /IRM/IPxxASP Awards Display In Review Sheet of Agreement

New tab "Awards" has been added to the agreement review sheet to display the Awards data.

Agreements Awards New Functionality /IRM/IPxxASPM_WS/IRM/IPxxARM_WS/IRM/GSDLM_WS/IRM/GSDLRM_WS/IRM/IPPQM_WS/IRM/IPSDAM_WS/IRM/IPSDARM_WS

Awards Maintenance from BSP With release E SP3, the system now supports award maintenance from the BSP applications for Agreements, Agreement request, Deals, Deal request, Master request, Direct Agreement, and Direct Agreement request.

Agreements Campaigns New Functionality /IRM/IPCGM Campaign Management A new object, Campaign, has been introduced for trade planning scenarios, to launch a new product. The Campaign node has been added under Pricing Agreements, containing its own number range object. The campaign functionality allows direct analysis, planning, execution, and measures promotional campaign activities through all applications before creating an agreement, deal, etc.

As Campaigns are mostly promotional activities, a new tab, Elements, has been introduced in the workbench. Element types are assigned to the Campaign in the new Elements tab. In the Elements tab, all the information pertaining to Elements in the Campaign, for example, type of campaign, validity of campaign, target market, etc. are contained. The Campaign Element Type is further divided into the element categories Element and Event.

Campaigns do not have condition type groups and it is recommended that Virtual Price Sheets are used. Virtual Price Sheets are assigned to a Campaign type under Assigned Price Sheets in Campaign type configuration.

Agreements Campaigns New Functionality /IRM/IPCGM Campaigns - IDOCs In order to move the campaign data from the legacy system to SAP, a new IDOC type, /IRM/CMPGNS01, and a message type, /IRM/CMPGNS, have been created. The IDOC type supports the movement of the Header, Dates, Texts, Organization and Partner data. For more information, please see the Campaign IDOCs document.

Agreements Campaigns New Functionality /IRM/IPCGM_WS Campaigns in BSP In prior releases campaigns were available only in within the GUI. Now, with Release E Service Pack 3, Campaigns are also available in via the BSP, with all the same features as the GUI transaction. In order to use the Campaigns BSP, block profiles must be created and assigned to the Campaign type in the block profile node.

Configuration for Block Profile:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Campaigns > Web Interface > Define Campaign Block Profiles (Assign Block Profiles to Campaign type)

IRMIPM 60E SP3: Release Notes

Vistex, Inc. of 39 Last Modified: 1/22/2016

Area Sub‐Area Type of Change Transaction Code Topic ChangesIRMIPM 60E SP3: Release Notes

Agreements Campaigns New Functionality /IRM/IPCGM Campaigns Mass Processing Mass change has been introduced in Campaigns to change multiple Campaigns at a time. Users can change General Data, Dates, Partners, Texts and Status of multiple Campaigns at the same time using the Mass Change option. For the mass change to function properly, the desired fields must be configured in the Mass Change node under the campaign type. The fields maintained in this node will show up in the general tab of Mass change Campaigns. In addition, a download option is also available via mass change.

Configuration:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Campaigns > Define Campaign Types

Agreements Deals New Functionality /IRM/GSDLM Deals Measures As of Release ESP3, measures are available in Deals. Measures can be maintained at Deal type level in the configuration.

Configuration :/IRM/GPRSPRO > Deals > Maintain Deal Types > Maintain Deal Types / 1 ‐ Maintain Measures in Measures Node.

Agreements Evaluations New Functionality /IRM/IPCGM Elements Tab in Review Sheet As part of release E Service Pack 3, the Evaluation Elements tab can now be accessed in HTML mode using the agreement review sheet.

Configuration:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Campaigns > Define Campaign Types > (Maintain Element Types for Campaign Type)

Agreements Evaluations New Functionality /IRM/IPxxASP/IRM/IPxDAM/IRM/IPCGM

Evaluation Tab in Review Sheet As part of release E Service Pack 3, the Evaluation tab can now be accessed in HTML mode using the agreement review sheet.

Configuration:Agreement:/IRM/IPSPRO > Basic functions > Pricing ‐ Sales (Purchasing) > Pricing (Purchasing) Agreements > Maintain IP Agreement types‐sales (Purchasing) > Maintain Agreement types for xxx/2 > (Maintain Evaluation types for Agreement Type)

Direct Agreement:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales (Purchasing) > Pricing Agreements (Purchasing)> Direct Agreements > Maintain Direct Agreements > (Maintain Evaluation types for Direct Agreement Type)

Campaign:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Campaigns > Define Campaign Types > (Maintain Evaluation types for Campaign Type)



Agreements File Upload New Functionality /IRM/IPxxARUPL/IRM/IPxxAGUPL/IRM/IPxxPGUPL/IRM/IPxxARUPL/IRM/IPxxAUPL/IRM/IPxxAPGUPL/IRM/IPPQUPL/IRM/IPCGUPL/IRM/GFGUPL

Check Entire File As part of Release E SP3 a new option is available in all the upload transactions. This option, Check Entire File, will allow the system to check the all records of a file being uploaded. Unlike in past releases, when the system would stop the upload process at the first error encountered, this option will report all errors encountered throughout the entire file to the users.

Agreements File Upload New Functionality /IRM/GFSUB/IRM/IPxxARUPL/IRM/IPxxAGUPL/IRM/IPxxPGUPL/IRM/IPxxARUPL/IRM/IPxxAUPL/IRM/IPxxAPGUPL/IRM/IPPQUPL/IRM/IPCGUPL/IRM/GFGUPL

File Submission ‐ File Server The enhanced file submission screen allows the users to upload a file from the Server. Besides uploading file from local desktop, the user now can store the server path for each submission type. In addition to this enhancement, users can use the files stored on the file server during the upload process. This is done through the new File Server option in the File Location drop down menu in each upload transaction.

Agreements File Upload New Functionality /IRM/IPxxARUPL/IRM/IPxxAGUPL/IRM/IPxxPGUPL/IRM/IPxxARUPL/IRM/IPxxAUPL/IRM/IPxxAPGUPL/IRM/IPPQUPL/IRM/IPCGUPL/IRM/GFGUPL

Transfer Errors A new flag called Transfer Errors has been introduced in release ESP3. If an Upload file contains any invalid data, the system can download the errors into a separate file for the user to analyze and correct. The extension for the file is maintained in Transfer File Suffix field, which is only displayed when transfer errors option is selected.

Agreements Milestone New Functionality /IRM/IPxxASP/IRM/IPSPRO

Claim Type Configuration at Milestone Assignment Level

As part of Release E SP3, the functionality of assigning multiple claim types based on each milestone schedule type has been introduced. This allows claims with different claim types can be created from the Agreements Schedule line items for each milestone types. In addition, one of the multiple claim types would be a global assignment. Unlike earlier releases where users had to assign all the claim types to the milestone schedule type, as part of this release, users can specify the claim type to each and every milestone type.

Configuration:/IRM/IPSPRO‐>Basic functions‐>Pricing sales‐>Pricing Agreements‐>Maintain IP Agreement types‐ Sales‐>Maintain Agreement Types For Billbacks/1‐> Schedule types‐> Claim Types.

Agreements Review Sheet New Functionality /IRM/IPCGM Elements Tab In the agreement review sheet, the Elements tab can now be accessed in HTML mode.

Configuration:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Campaigns > Define Campaign Types > (Maintain Element Types for Campaign Type)



Agreements Review Sheet New Functionality /IRM/IPxxASP/IRM/IPxDAM/IRM/IPCGM

Evaluation Tab In the agreement review sheet, the Evaluation tab can now be accessed in HTML mode.

Configuration:Agreement:/IRM/IPSPRO > Basic functions > Pricing ‐ Sales (Purchasing) > Pricing (Purchasing) Agreements > Maintain IP Agreement types‐sales (Purchasing) > Maintain Agreement types for xxx/2 > (Maintain Evaluation types for Agreement Type)

Direct Agreement:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales (Purchasing) > Pricing Agreements (Purchasing)> Direct Agreements > Maintain Direct Agreements > (Maintain Evaluation types for Direct Agreement Type)

Campaign:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Campaigns > Define Campaign Types > (Maintain Evaluation types for Campaign Type)

Agreements Schedules New Functionality /IRM/IPxxASP/IRM/IPSPRO

Item Filter At Agreement Schedules Configuration

In Release E SP3, Item Filters have been introduced to consider line items when creating a claim from a schedule. The Item Filters can be used at claim item level under schedules types in the agreement workbench. Two pre‐defined options are provided for item filter:

1. All Items ‐ In this scenario, if the rule has ten line items, the system will consider all ten lines in the claim during claim creation.2. X ‐ Match Schedule ID ‐ In this scenario, if the rule has ten line items, but only five of the line items have schedule ID maintained, then system will consider those five line items with corresponding schedule ID during the claim creation. In order for this functionality to be utilized, a condition table with the Schedule ID Field, IRM_SCHID, must be created.

Configuration:/IRM/IPSPRO‐>Basic functions‐>Pricing sales‐>Pricing Agreements‐>Maintain IP Agreement types‐ Sales‐>Maintain Agreement Types For Billbacks/1‐> Schedule types‐> Claim Types‐>Item Derivation‐> Item Mapping

For more information, please review the Agreement Schedules ‐ Item Filter Document.

Agreements Status Flow New Functionality /IRM/IPxxAME Status Mass Change New to Release E SP3 is the ability to use the mass change functionality to set status flow outcomes and statuses for agreements. This mass status change functionality has been integrated into the mass change menu for the agreement workbench. Users will have the ability to select the agreements for which the outcomes and status have to be maintained.



Agreements Trade Calendar New Functionality /IRM/GTCM or /IRM/GTCOBM

Trade Calendar The Trade Calendar functionality allows users to view and compare all the Agreements and Agreement requests at once in a web view. In addition, a drag and drop functionality is available, through which the validity of the agreement can be changed on the fly. Different layouts, along with the filter formulas, can be created in the object maintenance workbench for more ease of use and better understanding. These layouts can be configured horizontally or vertically with Hierarchy levels and the fields in the layout can be configured to be editable. For more information, please review the Trade Calendar Document.

Agreements Upload and Download

New Functionality /IRM/IPAGFTM/IRM/IPxxAGUPL/IRM/IPxxAGDNL

Evaluation Documents Users are now able to upload and download evaluation documents from the agreement upload and download transactions. To achieve this, four new sections have been added to the Section Tab in the Agreement File Template Workbench. These sections, Evaluation Grid Item, Evaluation Header, Evaluation Basic Item, and Evaluation Partner, can be used to map the evaluation fields to be uploaded or downloaded in conjunction with the corresponding agreement.

Business Script Enhancements New Functionality /VTA/BMSM Enhancements Previously, the business script functionality was introduced as a way to allow users to create function modules without accessing or requiring knowledge of the coding. New enhancements have been incorporated as part of Release E Service Pack 3 to further aid in the creation of business scripts. These enhancements include: creating parameters that refer to the format of a previously created parameter, copying parameters, inserting functions into the middle of steps, changing functions, deleting functions and a new global message system. In addition, other aesthetic changes have been made to simplify the user experience. For more information, go to the Business Script Editor 6ESP3 attachment.

Claim and Transaction Register

Claim Stage New Functionality /IRM/GCRSTGUPD/IRM/GRCASTGUPD

Updating Claim Stage Report will update claim stage for claims which were locked during subsequent IP document processing. Not only flag at header criteria level to be marked, also IP type and subsequent document partner role configuration at claim type level has to be maintained.


Simple Mode Single Code

New Functionality /IRM/GCRM/IRM/GRCAM/IRM/GCR37/IRM/GRCA37/IRM/IPxxM/IRM/IPxx37/IRM/IPxx34

Simple Mode Single Code The purpose of the Simple Mode Single Code functionality is to avoid the unnecessary processing of multiple values for the action code, adjustment code and rejection reason fields.

In order to specify whether a particular IP, Claim or Transaction Register type is in simple mode, a flag must be maintained at the type level configuration. If the Simple Mode Single Code flag is marked, users will see only one value for each of the codes (adjustment code, action code and rejection reason) at item level of the Claim, Transaction Register or IP documents and the Set Codes option will be hidden from the item toolbar.

Configuration: ‐ IP: IPSPRO ‐> Documents ‐> Define IP Types ‐ Claim: IPSPRO ‐> Documents ‐> Claims ‐> Define Claim Types‐ Transaction Register: IPSPRO ‐> Documents ‐> Transaction Register ‐> Define Sales Transaction Types / Define Purchasing Transaction Types




Special Handling in Grids

New Functionality /IRM/GCRM/IRM/GRCAM/IRM/GCR37/IRM/GRCA37/IRM/IPxxM/IRM/IPxx37/IRM/IPxx34

Special handling at item grid level

The purpose of "Special handling in grids" functionality is to allow users to work upon the IMV fields with greater ease. Previously, the set operation was done by selecting each column and applying the value of the IMV codes, but it was difficult for a user to select particular column since IMV values are spread across multiple columns. Additionally it allows user to perform set operation for only a few selected line items. Hence, a new Set Codes button is introduced in Special handling at item grid level.

The filter option was based on each individual column. This caused user to have to select multiple IMV code columns and search for the desired values. To avoid the complexity, a new Codes filter button is introduced to search for the code values without selecting the each column individually.

For more information, please see the Special Handling at Item Grid Level attachment.


Validation Workbench

New Functionality /IRM/GCR37/IRM/GRCA37

DM Partner Creation from Validation Workbench

Previously, DM and ECC Partner creation was restricted to item level in Claim and Transaction Register workbenches. As of release ESP3, users are allowed to create Partners from Claim and Transaction Register Validation Workbench as well. This new creation functionality from the validation workbenches will help improve performance with Claim Packages.

Configuration: ‐ Claims: /IRM/IPSPRO > Documents > Claims > Define Claim Types ‐ provide the partner for Item Par. Role field under the Partners tab

‐ Transaction Register: /IRM/IPSPRO > Documents > Transaction‐> Define Sales Transaction Types ‐ Provide the partner for Item Par. Role field under the Partners tab

Claims Status Flow New Functionality /IRM/GCRM Status Mass Change New to release E Service Pack 3 is the ability to use the mass change functionality to set status flow outcomes and statuses for claim documents. This status mass change functionality is integrated into the mass change menu in Claim workbench. Users will have the ability to select the claims for which the outcomes and status have to be maintained.

Composite Awards New Functionality /IRM/IPROEAAC Enrollment Auto Award Creation

A new transaction code /IRM/IPROEAAC is introduced, to create auto awards for the enrollments of the Roster. Configuration:/IRM/IPSPRO > Basic Function > Roster > Define Roster type Click on Award Types, and assign the Cumulative Award Type with the validity.

Composite Awards New Functionality /IRM/GAWM/IRM/GAWTM/IRM/GAWCM/IRM/GAWRM/IRM/IPROM/IRM/IPRORM

Logical Databases for Awards Transactions

New logical databases (LDBs) have been created for award, award type, award component, award request, roster and roster request.

Composite Awards New Functionality /IRM/IPROCIP/IRM/IPROCCP

Lookup Tier Redesign Previously, tier determination functions “LOOKUP_TIER” and “LOOKUP_NEXT_TIER” were based on quantity or amount. Now, they are redesigned to handle both quantity and amount.



Composite Awards New Functionality /IRM/GAWRPMP Mass Postings Users can post award request using the mass process functionality in Award Request mass process workbench.

Composite Awards New Functionality /IRM/GAWRM/IRM/GAWRFTM/IRM/GAWRDNL/IRM/GAWRUPL

Mass Upload for creating Award Request

Users can upload and download Award Requests using the upload/download functionality. For more information, please see the document Mass Upload for Award Request.

Composite Awards New Functionality /IRM/GAWRM Redemption of Awards using Redemption Catalog

Awards can now be redeemed using Redemption Catalog. The user needs to enter the redemption catalog, transaction party details, catalog item and quantity in the award request. Then, the system determines the award for redemption.

Configuration:/IRM/IPSPRO > Basic Functions > Awards > Define Award Request Types‐Select the Posting Category as "Redemption"‐Enable the "Redemption using Catalog" flag

Composite Awards New Functionality /IRM/IPxxASP/IRM/IPxxM/IRM/IPxxCIP/IRM/IPxxCCP

Tier Determination in Pricing In this release, eligible awards created in transactional IP and composite are based on the active tier of the enrollment in the roster. To support this functionality, two new fields “Roster” and “Award Indicator” are included in the General tab of the agreement.

Composite Buckets New Functionality /IRM/IPxxCIP/IRM/IPxxCCP

Bucket Item Source Field The new Bucket Item Source field has been introduced in the definition of the source key figure as long as the bucket is the source. The bucket item source has the following three options:• A Condition ‐ The key figure ID will be fetched from the condition item table based on the condition type entered in the condition type field.• B Aggregation ‐ The key figure ID will be fetched from the aggregation table based on the aggregation type entered in the aggregation type field.• Usage ‐ The key figure ID will be fetched from the bucket items table based on the usage assigned to the bucket type.

Composite Calculation Run New Functionality /IRM/IPxxPCRM Calculation Run‐Price Change Document

If the price protection profile is defined for the revaluation type then a price change document can be created while posting the calculation run document. In Release ESP3, the navigation is provided to the created price change document from Calculation run.

Configuration:/IRM/IPSPRO > Composite IP > Define Price Protection Profile/IRM/IPSPRO > Composite IP > Define Calculation Run Types

Composite Calculation Run New Functionality /IRM/IPxxCIP/IRM/IPxxPCRM

Info Record Updating from calculation run

When dealing with the price protection functionality, as of Release E Sp2, the Info Record Update is limited only to the participation validity dates. Due to this, repricing could only be done for the whole participation period. With the introduction of Release E SP3, a user can choose to update the info record either by the agreement dates, the evaluation dates, participation dates or from the agreement rules by using the new BADI method, Info_Records_Post.



Composite Calculation Run New Functionality /IRM/IPxxPCRM/IRM/IPSPRO/IRM/IPMXSGM/IRM/IPMXSM

Matrix Update from calculation run

Now in Release ESP3, synchronous update is now provided. The calculation run data will update the matrix without running the staging report. In addition, when the calculation run document is accrued, settled and interim settled, it will update the matrix directly.

Configuration:/IRM/IPSPRO> Composite IP > Deployment code and Components > Define Deployment codes.

Select a deployment code and a calculation run type under it. Then, in the IP Matrix Update, select Update Category and a matrix group, so that the matrix group will be updated according to the function defined.

Composite Calculation Run New Functionality /IRM/IPxxPCRM/IRM/IPxxPCRPMP/IRM/IPSPRO

Proforma Creation from calculation run

Release ESP3 provides the functionality to create a Proforma in the ways mentioned below: 1) Creating proforma for selective participants from calculation run workbench2) Creating proforma in Background from calculation run workbench3) Creating proforma from calculation run mass processing report4) Creating proforma from calculation run mass processing report during postings

Configuration:/IRM/IPSPRO > Basic functions > Planning > Proforma >Define Proforma Profile

Composite ClaimsTransaction Register

New Functionality /IRM/GCRM/IRM/GRCAM/IRM/GCRDMM/IRM/GCRDOMM/IRM/GRCADMM/IRM/GRCADOMM/IRM/EPCPM

Composition Material Composition has been integrated into claims and transaction register to support royalties. A composition material can be an ECC or DM material that explodes similarly to a BOM material in claims and transaction register.

For more information, go to the Composition_Integration_Claims_TR attachment.

Composite File Upload New Functionality /IRM/IPMXSUPL Check Entire File As part of Release E SP3 a new option is available in all the upload transactions. This option, Check Entire File, will allow the system to check the all records of a file being uploaded. Unlike in past releases, when the system would stop the upload process at the first error encountered, this option will report all errors encountered throughout the entire file to the users.

Composite File Upload New Functionality /IRM/GFSUB/IRM/IPMXSUPL


Composite File Upload New Functionality /IRM/IPMXSUPL Transfer Errors A new flag called Transfer Errors has been introduced in release ESP3. If an Upload file contains any invalid data, the system can download the errors into a separate file for the user to analyze and correct. The extension for the file is maintained in Transfer File Suffix field, which is only displayed when transfer errors option is selected.



Composite Matrix New Functionality /IRM/IPMXSCM/IRM/IPMXSCMBG

Batch Execution of Functions in Matrix Utilities

By using matrix utilities for job periods, the user is now able to execute all matrix utilities functionalities in background job processing. It might be copy, delete, copy + delete, process from source to target matrix combinations.

By using the process functionality, the user can apply the functions on the source matrix. The list of functions will take effect on the data in the sequence maintained. Variable maintained here should take priority.

Composite Matrix New Functionality /IRM/IPMXSM/IRM/IPMXPLAN

Characteristic Display at Subset Workbench

In Subset workbench there is a possibility of setting Characteristic Display drop down list field, for Characteristics display at Planning. Based upon the type of Characteristic Display set for an Individual Layout at Subset workbench, Characteristics are displayed according to it on executing the subset in planning workbench.

The 3 possible types for Char. Display can be set for a layout. They are a. Characteristic Description b. Characteristic Value c. Characteristic Value & Description.

The Default status for Characteristic Display is “Characteristic Description”.

Composite Matrix New Functionality /IRM/IPxxASP/IRM/IPPQM/IRM/GPSM/IRM/GPPM

Dependency of Price Simulation State on Proforma State

This feature provides the feasibility of updating the price simulation state along with the status of proforma delete or post. If the proforma is deleted, then price simulation gets deleted automatically. If the proforma is posted, the user cannot make any changes to the price simulation document.

Composite Matrix New Functionality /IRM/IPMXM Derivation Source Mapping Fields Conversion

In Release E SP2 for the Matrix workbench, at the derivation source mapping, the fields used to be in the order of 'matrix characteristic' first and then 'source' field.

Now in Release E SP3, these two fields are swapped by running the /IRM/IPMX_ESP3_DERV_CONV conversion report in SE38. So the expected order is, 'source' field and then 'field name' which is the 'matrix characteristic'.

For more information, go to the Matrix Conversion Reports attachment.Composite Matrix New Functionality /IRM/IPMXSM Explosion Source Mapping

Fields Conversion In Release E SP2 for the Subset workbench, at the explosions source mapping the fields used to be in the order of 'matrix characteristic' first and then 'source' field.

Now in Release E SP3, these two fields are swapped by running the /IRM/IPMX_ESP3_EXPL_CONV conversion report in SE38. So the expected order is, 'source' field and then 'field name' which is the 'matrix characteristic'.

For more information, go to the Matrix Conversion Reports attachment.Composite Matrix New Functionality /IRM/IPMXM Feasibility of Flagging Can be

Any and Initial flags after Generating the Matrix

Previously, the user was not permitted to enable the "Can be Any" and "Initial" flags after the generation of the matrix.

Now, the user is permitted to enable the "Can be Any" and "Initial" flags for matrix characteristics even for a previously generated matrix. But once those are flagged and the matrix is generated, there no chance to unflag them.



Composite Matrix New Functionality /IRM/IPMXM/IRM/IPMXSM/IRM/IPMXPLAN

Field Descriptions at Usage Details

When the user logs in with a language (language defined at usage level), descriptions for the planning workbench characteristics and key figures will reflect the same description that is defined at the subset usage level. Characteristics and key figures for which descriptions are not maintained at the subset usage level, they will be displayed in the language in which the user has logged into the system with.

Composite Matrix New Functionality /IRM/IPSPRO Fixed Value at Characteristics Condition in Proforma

In this release, the 'Value' field has been introduced at the 'Key figure conditions' to limit the copying of data from the source document to the proforma.

The maintained fixed value's (characteristics') keyfigure value will show up in proforma.

Configuration:/IRM/IPSPRO > Basic functions > Matrix > Proforma >Define Proforma Profile

Composite Matrix New Functionality /IRM/IPSPRO/IRM/IPxxASP/IRM/IPPQM/IRM/GPSM/IRM/GPPM/IRM/IPMXSM

Matrix Update on Saving Proforma without Posting it

In this release, the 'Update Matrix' flag is introduced in the proforma profile configuration. If it is enabled, the changes such as create/change/delete proforma will directly update both the matrix data and members.

Configuration:/IRM/IPSPRO > Basic functions > Matrix > Proforma > Proforma Profile

Composite Matrix New Functionality /IRM/IPMXSCM/IRM/IPMXSCMBGSLG1

Matrix Utilities Job for Periods Along with the 'Batch Execution of Functions in Matrix Utilities' functionality, the variant saved for background processing has a period criteria based on which the batch job schedule can be done. The user can have feasibility of planning matrix utilities for executing them in future with the help of matrix utilities for job periods in background processing.

The user can verify the complete detailed log details for the above background processing job by specifying all the basic job details using the transaction code SLG1.

Composite Matrix New Functionality /IRM/IPMXSM/IRM/IPMXPSUPL/IRM/IPMXSCM

Members Upload from an External Source File and Members Copy into Matrix

The purpose of this functionality is to upload members from an external source file into the matrix subset. This is done by using the members upload functionality in which the user needs to maintain a subset members template that is the same in the source file. When updating one subset usage members into another subset usage is required, then members can be copied from the source matrix subset to the target matrix subset.

Composite Matrix New Functionality /IRM/IPMXSM/IRM/IPMXSCM/IRM/IPMXSCMBG/OSM37/OSLG1

Overwriting the Existing Data in the Matrix by using a Background Job

The purpose of this functionality is to overwrite the existing data in the matrix by using matrix utilities functionalities in background job processing.



Composite Matrix New Functionality /IRM/IPSPRO Proforma Key Figure Condition Fields Conversion

In Release E SP2, the fields used to be in the order of 'matrix characteristic' first and then source field in the proforma profile in the keyfigure conditions at keyfigure mapping.

Now in Release E SP3, these two fields are swapped by running the /IRM/IPMXP_ESP3_KFCOND_CONV conversion report in SE38. So the expected order is, 'source' field and then 'field name' which is the 'matrix characteristic'.

Configuration:/IRM/IPSPRO > Basic functions > Matrix > Proforma >Define Proforma Profile

For more information, go to the Matrix Conversion Reports attachment.

Composite Matrix New Functionality /IRM/IPMXM/IRM/IPMXSM/IRM/IPMXPLAN

Supporting Characteristics in both Row and Column Hierarchies

This functionality allows the feasibility of assigning characteristics in both row and column hierarchy of a layout. Upon executing a planning workbench with characteristics on both hierarchies (row and column hierarchies), characteristics of a matrix data can be displayed on both hierarchies based upon layout fields assignment.

Composite Matrix New Functionality /IRM/IPSPRO/IRM/IPxxASP/IRM/IPPQM/IRM/GPSM/IRM/GPPM

Supporting Source Unit of Measure (UOM)/Currency

In this release, the 'Source Unit' flag is introduced at the keyfigure mapping in the proforma profile configuration. When this checkbox is enabled, the mapped key figures' units will be displayed in proforma according to price sheets units.

Configuration:/IRM/IPSPRO > Basic functions > Matrix > Proforma > Define Proforma Profile

Composite Matrix New Functionality /IRM/GDSTM/IRM/IPMXSM

Update Source Documents Data into Matrix Using Load

This functionality is used to Update Source Documents (IP Documents) Data into Matrix Using Subset "Load”. It is used to Update Matrix whenever there is a change in Source Documents.

In order to pull the data from source documents Data set “Definition” is defined at Data Set Workbench. Then the above Data Set is assigned to a Subset Usage at Subset workbench. When the associated source documents are created (or) changed, then the change in IP documents data will be reflected back only when it is loaded.

In Sp3 , the following source documents are also supported1.Sales Document (Dataset Area ‐ 060) 2.Billing Document (Dataset Area ‐ 061) 3.Delivery Document (Dataset Area ‐ 062) 4.Purchasing Document (Dataset Area ‐ 063)



Composite Matrix New Functionality /IRM/IPMXSM/IRM/IPMXSM/IRM/IPMXPLAN

Waterfall Views Assignment at Scenario Workbench

Since a large amount of matrix data is represented in a graphical manner, waterfall views in the Scenario workbench have now been introduced.

Waterfall views that are defined and assigned in the Subset workbench are customized or reduced in the Scenario workbench, for user feasibility.1. Initially waterfall elements are defined in the Subset workbench and the matrix key figures or key figure groups will be assigned to each of these waterfall elements.2. Each element can be assigned to a waterfall view any number of times with different contributions along with color combinations.3. In the Waterfall Views tab, the user can also assign key figures along with waterfall elements for user feasibility.4. When these waterfall views are used in the Planning workbench, initially the data is represented in the cascade elements. Then, upon navigating to the waterfall views format, data is represented in graphical format.5. Summaries Data can also be represented in waterfall views format based upon the Waterfall Elements & Waterfall Views definitions at Subset usage level.

There exists two cases ‐ 1.If the Scenario comprises with Waterfall Views Assignments at "Waterfall Views" tab, and then the Scenario in planning workbench contains only the Views defined at Scenario workbench. 2. If the Scenario doesn't contain any Waterfall Views assignments at "Waterfall Views" tab, then the Scenario in planning workbench contains all the Waterfall Views assigned to the Subset for that particular Scenario.

Composite Reports New Functionality /IRM/IPRPM Performance Improvements and Supporting Summarization in HTML Result Screen

In this release, the report execution has been optimized; HTML view support for summarization has been introduced, which was not supported in the prior release. Users can now view the result of summarization fields in the HTML view.

Composite Roster New Functionality /IRM/IPROM Additional Attributes for Enrollment in Roster

Customer specific fields can be maintained for roster enrollments.

Configuration:‐ Add the new fields in the append structure /IRM/S_IPROERCA of table /IRM/IPROERLM‐ Assign the new fields to the roster type/IRM/IPSPRO > Basic Functions > Roster > Define Roster TypeSelect Roster Type > Enrollment Additional Attributes

Composite Roster New Functionality /IRM/IPROREU Mass Upload of Enrollments to Create Enrollment Request

This new transaction code, /IRM/IPROREU, has been introduced to upload the enrollments to create an enrollment request. An optional check button is provided in the transaction to post the enrollment request.



Composite Roster New Functionality /IRM/IPROM Review Tab for Enrollment The roster enrollment view can now be displayed in the tree view, by configuring the anchor fields in the roster type configuration. By default, the system displays the enrollments in the ALV grid.

Configuration:/IRM/IPSPRO > Basic Function > Roster > Define Roster type >Click on Enrollment View, and create a view with anchor fields

Composite Subcomponent New Functionality /IRM/IPxxCIP Explosion Of Sets in Tracking In this release, Sets as subcomponent characteristics is introduced where users can explode the sets. This is similar to the flexible groups functionality.

A 'set' Field in the subcomponent characteristics configuration has been introduced. The user needs to maintain a Zfield that holds the set number. By using this, the user can fetch the exploded characteristics of the set. Additional attributes for dimensions should be added in the /IRM/S_GCIDIM_FLDS structure.In order to identify the dimension field attributes, the field name should be in a specific format: ‘DIM_<Dimension Category >’.

Users should include the ‘/IRM/S_GCIDIM_FLDS’ structure in append structure of this ‘/IRM/S_IPxxSCMCHAR’.

Configuration:Maintain the 'set' field in the subcomponent definition./IRM/IPSPRO > Composite IP > Deployment Codes and Components > Define Deployment Subcomponents

Composite Subcomponent New Functionality /IRM/IPxxCIP /IRM/IPxxPCRM

Multiple Internal Documents during Settlement to Partners

Previously, a single document number was generated in the case of internal settlement and the same document number was used for all of the settlement partners. But now if multiple partners accounting is maintained as ‘A ‘(Multiple Accounting Documents) in the deployment code definition, then the system will generate different documents for each settlement partner.

Configuration:/IRM/IPSPRO > Composite IP > Deployment Codes and Components > Define Deployment Codes

Composite Subcomponent New Functionality /IRM/IPSPRO Optimize Script Calling during Subcomponent Calculation

In this release, the 'OptScrpt' flag has been introduced to increase the performance of the subcomponent formula evaluation. An optimized script is defined with a subcomponent table and is evaluated once with all of the subcomponent lines instead of calling the script line by line.

The user needs to enable the 'OptScrpt' flag for the subcomponent in the deployment code definition.Configuration:/IRM/IPSPRO > Composite > Define Deployment CodesSelect the Deployment Code > Allowed Versions > Subcomponent



Composite Subcomponent Characteristics

New Functionality /IRM/IPxxCIP/IRM/IPxxCCP

Condition Record Number Mapping

The condition record number, KNUMH, can now be mapped to the subcomponent tracking characteristic as long as the rule is the source.

Composite Subcomponent Formulas

New Functionality /IRM/IPxxCIP/IRM/IPxxCCP

Valid From Date and Valid To Date Fields Enabled in Subcomponent Formulas

The valid from date (DATAB) and the valid to date (DATBI) of the subcomponent lines are now supported in the subcomponent formulas.

Data Objects Assignment New Functionality /VTA/BDOCM Domain Assignment As part of Release E SP3, domains have been introduced to classify fields, rules, rule profiles, and data models. For any field, rule, or rule profile to be available for use in a data model, the same domain assigned to the data model must be assigned, which is now a required field. To create a domain, the user must execute the Define Domain node in the /VTA/DOSETUP transaction. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Changes New Functionality /VGM/xxxx Mass Change The custom search transactions created by the user provide a dashboard like mass change functionality, wherein the users can search across data objects based on the selection criteria defined in the process area. The users can change the Object data that are pulled up and save the changes either as a validation run or directly into the object. Note: only the sections that are marked as search relevant in data model configuration will be available in Mass Change transaction. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Data Model New Functionality /VTA/BDOCM Cross Reference Mapping As part of the data model configuration workbench in the /VTA/BDOCM transaction, users can create new cross references. These cross references have to be mapped within the data model and can then be accessed when creating subsequent versions, reprocessing objects, or during posting. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Data Model New Functionality /VTA/BDOCM Duplication Coverage When creating a data model in transaction /VTA/BDOCM, users can now review a list of data that has been duplicated within a certain period of time. This is done within the Duplication tab of the data model. Here users will have to create a field group for a specific section of a version within the data model. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Data Model New Functionality /VTA/BDOCM Status Flow During the creation of a data model, a status profile can be assigned to each version. Different status profiles can be assigned to different versions. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Data Model New Functionality /VTA/BDOTVC Subsequent Versions In order to speed up the processing of multiple objects, the /VTA/BDOTVC transaction, Create Target Version, has been created. This transaction will allow users to create subsequent versions from existing version of multiple objects in single execution, rather than going to object instance workbench and individually creating subsequent versions for each object. Users can also schedule background jobs for creating target versions using this transaction. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Data Model New Functionality /VTA/BDOCM Update Relevant Version Version's which will be frequently updated should be marked as 'Update Relevant' this will create the Cluster tables and internally data fetching and processing will be done on these cluster tables to provide best performance.

Data Objects Download New Functionality /VTA/BDODNL Download Objects As part of Release E SP3, the data object functionality now allows offline maintenance of data objects. To accomplish this, the user must enter the /VTA/BDODNL transaction to download objects into a file. Multiple objects can be downloaded into the same file. An object can be downloaded either to the desktop or to a file server. After making changes to the file, the file can be uploaded back into the system.For more information, go to the Data Objects ‐ Enhancements attachment.



Data Objects Enhancements New Functionality /VTA/DOSETUP/VTA/BDOCM/VGM/xxxx/VTA/BDOVRM/VTA/BDOPM /VTA/BDOPRM/VTA/BDOVRPS/VTA/BDOTVC/VTA/BDOIU/VTA/BDODNL/VTA/BDODMI

Data Objects Enhancements Though introduced in Release E SP1, many changes have been made to the Data Objects functionality in Release E SP3. These changes will affect different aspects of the functionality and provide the user with new functionality. Included in these new features are custom transaction codes for each data model, allowance of partial postings of validation runs, and new mass change functionality, as well as others. These changes are intended to improve upon the functionality introduced in the past releases. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Fields New Functionality /VTA/BDOCM Create Field with Reference Users can create new fields using the Create with Reference option which will create a field having the same properties as the field to which it is referred.For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Fields New Functionality /VTA/BDOCM Field Type A new option when creating fields is the field type. A field type defines the datatype and length of characters of a field or the number of decimal places for a numeric datatype. In addition, uppercase and lowercase can be distinguished for the values entered on the screen. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Fields New Functionality /VTA/BDOCM Global Field As stated before, when creating a field, a domain must be assigned for the field to be activated. However, the only exception is when creating a global field. In the field creation popup window, the user has an option to create a global field. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects IDOC New Functionality /VTA/BDODMI Data Model from IDOC New to Release E SP3 is the ability to automate the creation of a data model from an IDOC type. In order to accomplish this, a new transaction has been created, /VTA/BDODMI. In this transaction, the user will need to provide a Data Model, Version, Domain, and an IDOC type.For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Index Tables New Functionality /VTA/BDOIU Index Updating In order to update Index table with the latest changes to the Duplication Field Groups, the /VTA/BDOIU transaction, Index Update has been introduced. The purpose of this functionality is to update the index table whenever changes are made to the existing duplication groups. Updating the index tables every time a duplication change is made is necessary in order to maintain current information in the duplication fields.For more information, go to the Data Objects ‐ Enhancements attachment.



Data Objects IP New Functionality /VTA/BDOCM Integration As of Release E SP3, the data objects functionality has been fully integrated with several IP applications allowing the user to create documents within the following applications: Agreements Agreement RequestsDeal Deal Request Master Request Product List Vendor List Customer List Membership Direct AgreementDirect Agreement Request

Data Objects Postings New Functionality /VTA/BDOCM Partial Postings Partial posting can be utilized when the user wants to send only the valid portion of the data object to create subsequent objects. If partial posting flag is not marked, then entire object will be considered for Posting to Subsequent Object. Introduced as part of the Data Objects functionality in Release E SP2, postings can create such objects as claims, transaction register, agreement, agreement request, membership list, customer list, partner list, vendor list, and master request from a data object instance. One data object instance is able to create multiple subsequent documents. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Profile New Functionality /VTA/BDOPM /VTA/BDOPRM

Data Profiling ‐ Grouping New to Release E SP3, users have the ability create data profiles with groups in order to display different statistics based on the data from selected data objects. These groups are created within the Object Profile, transaction /VTA/BDOPM, or the Object Profile Run, /VTA/BDOPRM. A group can consists of multiple fields from different sections. Users can assign more than one group to a field, as well as, assigning groups to the various code types. As a result, the profile run will show the field statistics based on the values of the group.For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Reprocess New Functionality /VTA/BDOVRPS Reprocess Multiple Object Versions

With the new release, the data objects functionality now allows users to carry out operations such as duplication, matching, and rule checks for multiple objects within a single transaction. In this transaction, /VTA/BDOVRPS, users can reprocess more than one object at a time, provided the objects are from the same data model and same version. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Setup New Functionality /VTA/DOSETUP Custom Transaction Code New to Release E SP3, the data objects functionality requires the creation of separate custom transaction codes for both the Data Object workbench and the Search and Process functionalities for each data model. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Setup New Functionality /VTA/DOSETUP Data Objects Setup One of the changes to the data objects functionality is the new IMG transaction for Data Objects Setup, /VTA/DOSETUP. Here users can configure aspects of the Data Object types. In this IMG transaction, users can maintain number ranges for objects and validation runs, custom transaction codes, validation, correction or correction codes, and other aspects needed in the use of the Data Objects functionality. For more information, go to the Data Objects ‐ Enhancements attachment.



Data Objects Validation Run New Functionality /VTA/BDOVRM Auto Validation Run An auto validation run can be used to create validation runs based on determined search criteria. In the transaction /VTA/BDOAVM, the user will be able to enter an Auto Validation Run name and select a Process Area. It is the Process Area that will determine which fields are available as part of the search criteria. Users can also select data conditionally based on a qualifier and can modify the data before creating a validation run by using corrections. Once an Auto Validation run is executed, any available data objects meeting the criteria will be added to a validation run. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Validation Run New Functionality /VTA/BDOVRM Locking When data has been added to an open validation run, the system now has the ability to lock the corresponding objects preventing any changes from being made. The locking functionality is set at the section level of a data model version in the /VTA/BDOCM transaction. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Validation Run New Functionality /VTA/BDOVRM Subsequent Validation Run Based on the selections made, the system can create a subsequent validation run containing objects still in progress on a current validation run. For more information, go to the Data Objects ‐ Enhancements attachment.

Data Objects Validation Run New Functionality /VTA/BDOVRP Subsequent Validation Run In Release E SP3, users can now release validation runs using a single execution. In the /VTA/BDOVRP transaction, users can release a single validation run or select several validation runs and release them all at the same time. Releasing these validation runs can be done in the foreground or as part of a background job. For more information, go to the Data Objects ‐ Enhancements attachment.

Global Business Script New Functionality /VTA/BSEM Script Review Introduced as part of the Business Script functionality during Release E SP2, the trace option has undergone some changes during Release E SP3. One such change is only allowing the trace functionality to be available after the Business Script has been activated. The trace button will not be an available option if the user is working with a deactivated script. Additionally, when users decide to trace a Business Script, the system will allow users to set a trace at the Step level or the individual operation level. Users will be able to trace a script during the simulation functionality, but can also have a trace window displayed when the system is executing a script in a transaction.

Global Business Script New Functionality /VTA/BSETRC Script Trace As part of Release E SP3, users will have the ability to review all current traces active for all Business Scripts, regardless of the transaction it is located in. This is displayed in the transaction /VTA/BSETRC. From here, users can review which aspects of a script are currently traced. In addition, from this transaction, users can activate or deactivate additional steps of a script already being traced, deactivate the tracing option for entire scripts, or deactivate the tracing option for all scripts within the system.

Global Charts New Functionality /IRM/GCHDL/IRM/IPRPM/IRM/GSPM

Fusion Charts In prior releases, users would have to download the chart templates into a local work directory using the transaction /IRM/GCHDL. However, from Release E SP3 onwards, users will no longer be required to run this transaction. Now, the chart rendering will be done without downloading the templates. This will affect all transactions that rely on the chart display, especially the Report Workbench, /IRM/IPRPM, and the Status Flow Preview, /IRM/GSFM.



Global File Upload New Functionality /IRM/GAXREFUPL/IRM/GMXREFUPL/IRM/GPXREFUPL/IRM/GUXREFUPL


Global File Upload New Functionality /IRM/GFSUB/IRM/GAXREFUPL/IRM/GMXREFUPL/IRM/GPXREFUPL/IRM/GUXREFUPL


Global File Upload New Functionality /IRM/GAXREFUPL/IRM/GMXREFUPL/IRM/GPXREFUPL/IRM/GUXREFUPL


Global Launchpad New Functionality /IRM/GLPBM_WS/IRM/LAUNCHPAD/IRM/LAUNCHPAD_WS

Amount Tiles A new option added to the report links is the ability to add a cumulative amount, as well as, summary amounts. After adding a report to a tile in the new generation Launchpad Builder, transaction /IRM/ GLNPBM_WS, a new popup window will be displayed. Here the user can choose how to evaluate summarize the report.For more information, go to the Launchpad ‐ Changes and Enhancements attachment.

Global Launchpad New Functionality /IRM/LAUNCHPAD Contains Value Search Functionality

In order to search the values based on the pattern specified, two new selection values Contains Pattern and Not Contains Pattern have been introduced in Classic Launchpad. Users are able to search for the required data by specifying the pattern in the launchpad fields. When using either of these options, the user must enter an asterisk (*) when entering the desired pattern.

Global Launchpad New Functionality /IRM/LAUNCHPAD Field Validation Functionality To prevent invalid data from being entered into the search fields in the Launchpad, the Field Validation has been introduced. If the user provides invalid data in the search field, instead of displaying a blank transaction screen, the system will provide an error message within the launchpad screen.


Grouping Tiles Users now have the ability to group tiles together within a single column on the new generation Launchpad. To group tiles within a single column, the user must access the Launchpad Profile using the Launchpad Builder transaction, /IRM/GLNPBM_WS.For more information, go to the Launchpad ‐ Changes and Enhancements attachment.

Global Launchpad New Functionality /IRM/GWSM/IRM/LAUNCHPAD

Input Multiple Selections When creating a new link, users have the option to select the Input‐Multiple Selections under the Display At Runtime option menu. This selection provides users the ability to enter the multiple selections as part of the search field using the More Values button in the launchpad.


Launchpad Change and Enhancements

Introduced during Release E SP2, the new generation Launchpad was intended to give the Launchpad a new look by allowing the user to have control over the display settings in a personalized tile view. As part of Release E SP3, new functionality has been added improving upon this by providing users an easier way to personalize the Launchpad profile in terms of the data and display. Now users are able to group tiles, display multiple display documents, control animations, and display cumulative amounts of reports.For more information, go to the Launchpad ‐ Changes and Enhancements attachment.




Launchpad Report Tiles In order to speed up the loading time of the Launchpad Profile, any tile that contains a report chart will be automatically generated in the background after the profile is displayed. Therefore, when displaying the Launchpad profile in the transaction /IRM/LAUNCHPAD_WS, the system will generate the pages, tiles, links, and background first. Then after everything has been generated, the chart tile will be generated and displayed.For more information, go to the Launchpad ‐ Changes and Enhancements attachment.


Launchpad Worklist In Release E SP3, when a user adds a document to the worklist of a workbench, the document can be viewed from the new generation Launchpad.For more information, go to the Launchpad ‐ Changes and Enhancements attachment.


Maximum Number of Hits New to the Workspace Workbench is the Maximum number of hits field. This field has been designed to restrict the number of entries returned by a search from the launchpad. Entering a value into this field will cause the system to display only the specified number of records when a search is conducted. However, though an entry has been added to the workspace link, users can modify or remove the maximum number of hits count in the launchpad.


Required Fields Users now have the ability to specify the required fields when creating links for transactions in the Workspace workbench. A new checkbox, Required has been introduced. Users can select the Required checkbox in the workspace specifying that the field is mandatory when searching the documents in Launchpad. Therefore, if no entry is provided, the system will display an error message.


Tile Animation To allow users to control the display of the new generation Launchpad Profiles, two new options have been added to the Animation tab in the tile settings. These options are set in the new generation Launchpad Builder transaction, /IRM/GLNPBM_WS, at the individual tile level. For more information, go to the Launchpad ‐ Changes and Enhancements attachment.

Global Launchpad New Functionality /IRM/LAUNCHPAD Tile View In Launchpad GUI Introduced during Release E SP2, the new generation launchpad was intended to give the launchpad a new look by allowing the user to have control over the display settings in a personalized tile view. This new view introduced is a tile view display, as well as the Launchpad Builder transaction, /IRM/GLPBM_WS. Originally this display option was only available through the Launchpad Portal transaction, /IRM/LAUNCHPAD_WS. However, as part of Release E SP3, this functionality is now available in the launchpad GUI transaction. Therefore, any launchpad profile using the tile view option can be accessed through the transaction /IRM/LAUNCHPAD, as well as, all the functionality available in the Launchpad Portal.

Master Request Check Functionality

New Functionality /IRM/IPPQM Support Master Request Check Functionality

The purpose of the functionality is to provide feasibility for the user to validate the rules, partners and clauses data all at once. If the user did not a required field in the rules tab, partners tab or clauses tab, the system will display an error message. In the application toolbar, the user can click on the "Check Rules" icon regardless of what tab is being displayed within the master request document. The behavior of "Check Rules" icon is similar to "Check and Complete" icon on the Rules tab.



Master Request Editions New Functionality /IRM/IPPQM Editions Tab in Master Request The purpose of this functionality is to track all the changes done to the master request document like creating postings, adding price records, changing price records, and/or deleting price records. The user can maintain and display editions from the Editions tab; only one edition will be active at a time. If an edition type is assigned to master request type, the status profile assigned in the master request type level will be inactive and the status profile assigned to the edition type will be active.

Configuration:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Set up Agreements > Master Request > Define Edition Types > Define Master Request > Edition Types

For more information, go to the Master Request_Editions attachment.Master Request Evaluation New Functionality /IRM/GEVELM

/IRM/GEVTPM/IRM/GEVTM/IRM/IPPQM

Evaluation Tab in Master Request

The Evaluation tab with the master request allows the user to maintain census or compliance data, or suitability to determine the applicable master request. The evaluation tab functionality can be as simple as a collection tool for data or used to cross check that all the necessary information is entered. If the assigned evaluation type is marked for auto‐creation in the master request configuration, the evaluation entry will automatically be created in the Evaluation tab while a new master request is being created.

For more information, go to the Master Request_Evaluation attachment.

Master Request General New Functionality /IRM/IPPQM/IRM/IPSPRO

Name Change In the master request workbench, the Activities tab has been renamed to the Postings tab.

In the master request type configuration, the Activity Stages and Activity Steps nodes have been renamed to Posting Stages and Posting Steps nodes.

Master Request Mass Change New Functionality /IRM/IPPQ23 Follow-on Functions The Master Request Follow‐On Functions transaction has been introduced, which is the same as the Mass Report functionality. Users can make use of follow‐on functionality with these options: create proforma, recreate proforma, refresh proforma, reprocess and set status for master requests.

The Parallel Execution option is available to decrease the execution time for processing master request documents.



Master Request Mass Change New Functionality /IRM/IPPQACTM Mass Postings The Master Request Mass Posting transaction has been introduced, which is similar to the Mass Report functionality.

Users can make use of mass postings by creating postings and processing scheduled postings.• The Create Postings option allows the user to create single or multiple postings, such as Price Proposal, Agreements, Agreement Requests, Deal and Deal Request. While creating a posting for Agreement Request activity, the system will allow the user to select the agreement request type if multiple agreement request types are assigned in the agreement type configuration. •The Process Scheduled Postings entries are stored in the /IRM/IPPQACTBJ table after processing the scheduled postings for the given master requests selection. The respective master request entries will be removed from the /IRM/IPPQACTBJ table.

The Parallel Execution option is available to decrease the execution time for processing master request documents.

Master Request Mass Change New Functionality /IRM/IPPQM Status Integration for Mass Change in Master Request

A new Status tab has been introduced in the mass change of the master request, which allows users to change the status of multiple master requests at a time. Both status profile and status flow are supported in the mass change of a master request, but users can only select one option from the "Status by" dropdown.

Master Request Mass Extension New Functionality /IRM/IPPQME Mass Extension The Master Request Mass Extension Workbench (GUI) enables users to create, change rules and/or header data for multiple master requests at one time. Using the General, Partners, Dates, Status and Text tabs, data can be changed, deleted, or added for new master requests within the mass extension transaction. If multiple master request types are chosen, certain functions that are not applicable will not apply and the system will give a message.

Master Request Periods New Functionality /IRM/IPPQM/IRM/IPPQM_WS

Periods Functionality in Master Request

The Period tab within the master request allows the user to maintain predefined periods or master request specific periods. Instead of using an IP calendar or SAP fiscal year, the user can define a period profile and assign it to a master request type. Then within the master request GUI or BSP transaction, the period profile can be proposed on the Schedules tab.

Period Selection ‐ Predefined:• The period profile information populates below the period selection area. The system displays the same number of periods that were created in the period profile workbench with same ending days.• In the Review tab, the system generates a list of periods for the time period selected with the proper start and end dates for each period. The number of periods is dependent on the time period selected.

Period Selection ‐ Master Request Specific:• The system allows the user to make changes to the periods and save the master request.



Master Request Postings New Functionality /IRM/IPPQM Postings Change Support for Agreements

Postings change functionality is available to make changes to existing agreement postings based on agreement derivation configuration. Here the system supports both the synchronous and asynchronous modes. Any header or rule changes made in the master request can be updated directly to the agreement by using the postings change functionality and the agreement posting will be created in the same master request document. Agreement change posting needs to be configured in the master request type along with the derivation source. Derivation source can be either posting step or rules. If the derivation source is posting step, the agreements created under the respective posting step will be updated with the new changes made in master request document. If the derivation source is rules, the user needs to manually add the rules along with the agreement numbers that require changes. The agreement number is added to the Sales Deal field of the Price sheet set as derivation source in the configuration.

Configuration Path: /IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Set up Agreements > Master Request > Define Master Request 1. In Posting Step node, select Agreement Derivation Source from the dropdown menu.2. Posting Step > Derivation Source (Postings steps or Application, Condition type, Table).

Master Request Postings New Functionality /IRM/IPPQM Supporting of Direct Agreement Postings from the Master Request

Users can now create and maintain Sales and Purchasing Direct Agreements and Agreement Requests from the Postings tab in the master request. Previously, only Deal, Deal Request, Price Proposal, Billback, Chargeback, Sales Rebate, Purchasing Rebate, Sales Incentives, and Business Registers Agreement and Agreement Requests were the only activities that could be created and maintained from the Postings tab.

For more information, go to the Master Request_Sales‐Purchase Direct Agreement attachment.

Master Request Schedules New Functionality /IRM/IPPQM/IRM/IPPQM_WS/IRM/IPPQFTM

Schedules Functionality in Master Request

New functionality has been introduced as “Master Request Schedules“ within the master request workbench. The purpose of this functionality is to provide flexibility to the business for the time frame of an master request and automatically allocate and distribute corresponding amounts based on schedule validity. The schedules section is available in the master request file template, review sheet and BSP.

For more information, go to the Master Request_Schedules attachment.

Matrix Planning New Functionality /IRM/IPMXM/IRM/IPMXSM/IRM/IPMXPLAN

Adding members while distribution from Any

While using the function DIST_2_Any, if the usage doesn't have an entry for a characteristic, system will create the entry member combination and save the record. In addition, by using the function DIST_ANY, distribution from any, any value will be distributed.



Matrix Planning New Functionality /IRM/IPMXM/IRM/IPMXPLAN

Allowing Layout Functions to Modify Child Level Data Using Script

Release E SP3 now allows business scripts within the layout function to modify child level data. These layout functions are assigned at planning workbench main screen and, based on the assignment level in the layout hierarchy, the associated child data will be modified using the script definitions.

Matrix Planning New Functionality /IRM/IPMXSM/IRM/IPMXPLAN

Authorization Group at Usage level for Function on Demand assignments

In Release ESP3, Authorization Groups for On Demand functions at the usage level has been introduced. This allows only users within the specified authorization group to access the functions assigned to the authorization group.

The Authorization group can be defined using the following configuration path: IPSPRO ‐> Basic functions ‐> Matrix ‐> Define Authorization Groups


Categorization of existing functions along with Implementation types

In Release ESP3, the existing functions of Pre‐Defined, Computation, User‐Defined, and Forecast have been restructured and categorized into Function Type and Implementation Type.

For more information, please see the attached document Matrix Functions Categorization .

Matrix Planning New Functionality /IRM/IPMXSCM/IRM/IPMXSTGU

Collecting Posted Staging Data while Processing IP Documents

As of Release E SP3, a new functionality has been introduced to collect the posted staging data while the data is updated from the IP documents in the Matrix. For this, a check box is provided in the subset workbench at usage level. When this is checked at the Subset Usage, the system will collect the posted Staging Data while processing IP documents into a table for later viewing.

Note: This check will increase the processing time while running the matrix staging data update.


Currency and Quantity as the characteristics in the matrix

Introduced in Release E SP3, the currency and the quantity fields are treated as one of the characteristics. This provides the ability of calculating their respective conversions. The user needs to define the custom currency and quantity fields before the fields become available in the characteristics tab of the matrix workbench. This is achieved in the append structure under the main structure /IRM/S_IPMXCHARCA. Once the characteristic fields are defined in the append structure, they can be assigned at Matrix Workbench and the respective fields can be assigned in the layouts. The Matrix data, with respect to the Currency and Quantity fields, is displayed at planning workbench along with the other characteristics.


Default Distribution Functions The Default Distribution Functions type provides the feasibility of controlling the distribution data to the hidden levels at planning.

For more information, please see the attached document Default Distribution Functions .


Derivations Overwrite at Subset Usage Level

Derivations assigned at subset workbench will overwrite the derivations that are defined at matrix workbench. Derivations that are assigned at subset usage level have the highest priority.




Distribute Matrix Data with Reference to a Key Figure

In Release ESP3, the Matrix data can be distributed with reference data from the planning workbench using Distribution with Reference function type. Using this type, the reference data is considered a Key Figure. Based on the type of Key figure assigned to the function, the corresponding data will be distributed when applied.

For more information, please see the attached document Distribute Matrix Data with Reference to a Key Figure.


Distribution level As part of Release E SP3, a new column, Distribution Level, has been provided. This distribution level column improves the performance during distribution by restricting the distribution to matrix characteristics. In the distribution level, the user needs to provide the characteristic for which the data needs to be distributed in the planning screen.

Example: If the matrix characteristics are defined as Customer, Sales Org, Distribution Channel, Division, and Material and the distribution level is set to Distribution Channel. In the planning functionality, the distribution of data is done through the Distribution Channel, while the further characteristics, such as, Division and Material are not considered in the distribution, since these are at a lower level than the Distribution Channel.

Note: The distribution level will be enabled only when the Distribute From Any indicator is checked. This means, the Distribution Level field must be applicable to the functions DIST_ANY and DIST_ANYK.


Enhancement Class Methods to Lock Time Periods in Planning

The Enhancement Class methods provide feasibility of Locking Time Periods for a particular Time Interval as defined in Enhancement Class method definition. This Enhancement Class is assigned for a subset at subset workbench. Upon executing the planning workbench with a matrix subset usage and, if, the subset usage has been assigned with the enhancement class methods definition, then, the time periods for that matrix can only be displayed, even in change mode, independent of layouts assigned for the matrix.

The Enhancement class methods are defined at SE24 transaction.


Feasibility of Business Script for Derivations at Matrix level & Subset Usage Level

The Business Script for Derivations functionality at the matrix level and the subset usage level allows user to define custom business scripts for deriving data independent of the source mapping. Depending on the script maintained at derivations level, the corresponding derivation returns the value at planning workbench.

The derivation functionality follows a predefined priority level from highest to lowest, as listed below:Business script at Subset Usage‐>Business Script at Matrix workbench‐>Normal Derivations at Subset Usage‐>Normal Derivations at Matrix workbench.




Fixed value at characteristics condition in Derivations/Explosions/Proforma

In Release ESP3, the Value field is introduced in the Source mapping to limit the copying of data from the Source Matrix to the Target matrix. This is applicable for Derivations, Explosions and Proforma.

Within the Derivations functionality, if a value is specified in the Value field, then the Derivation Key Figure will carry the data from the source matrix to the target matrix for the specified member. If the value is not specified, then the data related to the common members will be copied from the source matrix to the target matrix using the derived key figure. In addition the subset usage level of the derivation source will have a higher priority in the planning workbench.

When using the value field in Explosions, if the value is specified, the data will be copied from the source matrix to the Explosion ID in target matrix. This data will be displayed in the planning workbench within the same usage as the Explosion ID. If the value is not specified, the data related to the common members will be copied from the source matrix to the Explosion ID in the target matrix. Again the data will be displayed in the planning workbench within the same usages as the Explosion ID. The Explosion definition, along with the source mapping, will always be executed at the subset/usage level. There is no prioritization within the Explosion functionality.

Matrix Planning New Functionality /IRM/IPMXVARM/IRM/IPMXPLAN

Functions Assignments at Scenario Workbench

The main objective of functions assignments at scenario workbench is to allow the user to limit or filter the number of functions assigned to the subset.

The functions, which are defined at matrix workbench and assigned at subset workbench, are customized or reduced at Scenario workbench for usability. 1. If the Scenario computes with the functions assigned in the Functions Tab, then the Planning Workbench consists of only the functions which are assigned at Scenario. 2. If the Scenario computes with No function assigned in its Functions Tab, then the Planning Workbench consists of all the functions which are assigned to the Subset of that particular Scenario.


Layout Specific Functions Initially, functions which were defined at matrix workbench were allowed to be assigned in the Assignments tab in the. Now in ESP3, these functions can be assigned for individual layouts at usage level. The Layout Specific Functions provides the ability to assign only the specified functions for each of the individual layouts. In addition, the user can restrict functions for individual layouts.

Functions with an Implementation event of On Demand are only allowed to be assigned in layouts. Additionally, functions without any Function Implementation Event are only allowed for assigning in layouts. For example, the functions Dist_Any, Sweep, Forecast, Dist_Anyk, can be used in the layouts.



Matrix Planning New Functionality /IRM/IPMXM/IRM/IPMXSM/IRM/IPMXVARM/IRM/IPMXPLAN

Layout Specific Functions Assignments at Scenario Workbench

The Layout Specific Function allows the assigning of only the specified functions for each of the individual layouts. The user can restrict the number of functions for each individual layout. Allowing these functions to assigned for individual layouts at usage level.

Similarly, in the Scenario workbench, functions assigned at the Functions tab are only allowed for assigning layouts at Layouts tab. If no function assignments exist at functions tab, then the layouts functions, which are assigned at subset usage level, are taken into consideration.

Only the Forecast and On Demand functions can be maintained at Scenario workbench level.


Layouts & Functions Assignments with Explosions Filter at Subset Usage Level

The layout and function assignments for the subsets have been moved to subset usage level, along with explosions filter. Now, the explosions filter can be assigned for individual layouts. In addition, the functions assigned to the usage can be applied all the layouts assigned. At the planning workbench, the user can easily filter explosions for individual layouts based on their assignment at subset usage level. Functions which are assigned for the subset usage will be available independent of layouts.


Layouts Assignments at Scenario Workbench

This functionality allows user to filter or limit the number of layouts assigned to the same subset in the matrix workbench. • The Assignments of layouts in the Layouts tab comprises with two possible cases. 1. If the Scenario comprises with some Layouts Assignments in the Layouts tab, then the Scenario in planning workbench contains only the layouts defined at Scenario workbench. 2. If the Scenario doesn't contain any Layouts assignments in the Layouts" tab, then the Scenario in planning workbench contains all the Layouts assigned to the Subset for that particular Scenario.

•The deletion of the layouts at subset workbench is only possible if there are no layouts assignments for a scenario with that particular subset.The layouts which are assigned at subset workbench can only be customized at Scenario workbench.


Locking Data by Characteristics at Planning

Assigning the Lock Level option at Subset Usage will prevent more than one user from maintaining the same matrix data at the planning level at a time.

Matrix Planning New Functionality /IRM/IPMXSGM Matrix update with Synchronous Update of Matrix Group

When the Update Type is set to Synchronous Update in the matrix group, the IP documents will update the matrix automatically without executing the staging report.




Member locking extended to other areas

When more than one user tries to modify the same set of matrix data during planning, then the matrix data will be locked. This can be achieved by assigning the Lock Level at the Subset Usage.

This functionality has been extended to the below areas:• Proforma posting• Matrix data upload/download• BI data update• APD Data update• Matrix Utilities

Matrix Planning New Functionality /IRM/IPMXSM/IRM/IPMXPLAN

Summaries in subset workbenchIn Release ESP3, new functionality has been provided to view matrix data in a format knows as Summaries in planning workbench. Based upon the definition provided at the subset workbench, Table or Total Summary Types, the data is reflected during planning in summaries format.

For more information, please see the attached document Summaries .


Supporting Decimal Type Variables

Decimal Type variables can be defined in the Variables tab of Matrix workbench, /IRM/IPMXM. This functionality is similar to the definition of other variables, requiring a description, length, decimal places, high and low values. The variable can be assigned to different function types and used for calculations related to data using the decimals in the planning workbench.


Variables Assignments and their Default Values Overwrite at Scenario Workbench

Variables which are defined at Matrix workbench can be customized or reduced at Scenario workbench, for ease of use. Here, variables can be assigned along with their default values which lie between higher and lower values. Variables Assignments and their Default Values defined at scenario workbench take priority over the values defined at Matrix and Subset workbenches.

Membership File Upload New Functionality /IRM/IPGTAUPL/IRM/IPGTUPL/IRM/GMLUPL


Membership File Upload New Functionality /IRM/GFSUB/IRM/IPGTAUPL/IRM/IPGTUPL/IRM/GMLUPL


Membership File Upload New Functionality /IRM/IPGTAUPL/IRM/IPGTUPL/IRM/GMLUPL




Pricing Agreement New Functionality /IRM/0IPAGR21/IRM/IPxxASPSE38

Archiving ‐Archiving of agreement scales, awards, sheet extension tables and sets are available. In order to archive an agreement, the agreement archiving control must be maintained via /IRM/0IPAGR21. Here the agreement type, sales organization and residence time in days must be maintained. There is also a "Document Pricing Check" flag that was introduced at this level. In order to alleviate performance issues, this flag verifies if the agreement was used in sales conditions (/IRM/GCOND and KONV tables). ‐Once the archiving control is setup, the completion status must be set via the agreement workbench menu: Mass Process > Header Data, input an “X” in the Completed field. The user can pull up the agreement(s) in the agreement workbench but cannot edit the agreement anymore. In order to edit the agreement(s), the user has to reset the completion status via the agreement workbench menu: Mass Process> Header Data, check the Reset flag for the Completed Field. ‐After setting the completion status, the user can complete the first step of archiving the agreement via the /IRM/IPxxAGR_ARCH_WRITE report. When reviewing the results in the Log Summary, if the user processes more than one agreement, the report will show the agreement count but not all of the agreement numbers. As an example, instead of displaying every agreement number, the report will show the first agreement number. The Detail Log displays all of the agreement numbers. ‐When the delete report has been executed, the user can complete the final step of archiving by deleting the archived agreement via the /IRM/IPxxAGR_ARCH_DELETE report. Once executed, the data will no longer be accessible in the tables (scales, awards, sheet extension tables and sets).



Pricing Agreement Request

New Functionality /IRM/0IPAR21/IRM/IPxxARMSE38

Archiving ‐Archiving of agreement request scales, awards, sheet extension tables and sets are available. In order to archive an agreement request, the agreement request archiving control must be maintained via /IRM/0IPAR21. Here the agreement request type, sales organization and residence time in days must be maintained. ‐Once the archiving control is setup, the completion status must be set via the agreement request workbench menu: Mass Process > Header Data, input an “X” in the Completed field. ‐The user can pull up the agreement request(s) in the agreement agreement workbench but cannot edit the agreement request anymore. In order to edit the agreement request(s), the user has to reset the completion status via the agreement request workbench menu: Mass Process > Header Data, check the Reset flag for the Completed Field. ‐After setting the completion status, the user can complete the first step of archiving the agreement request via the /IRM/IPxxAR_ARCH_WRITE report. When reviewing the results in the Log Summary, if the user processes more than one agreement request, the report will show the agreement request count, but not all of the agreement request numbers. As an example, the report will show the first agreement request number. The Detail Log displays all of the agreement request numbers. ‐When the delete report has been executed, the user can complete the final step of archiving by deleting the archived agreement request via the /IRM/IPxxAR_ARCH_DELETE report. Once executed, the data will no longer be accessible in the tables (scales, awards, sheet extension tables and sets).

Pricing General New Functionality /IRM/GPR01/IRM/GPR02/IRM/GPR04/IRM/GPR06/IRM/GPR26/IRM/IPxxASP/IRM/IPxDAM/IRM/GxDLM

Auto Adjusting Dates The purpose of the functionality is to save more than one overlapping record, which was previously not allowed. When a user tries to maintain overlapping records, the dates will be adjusted automatically by considering the old and new record validities.

To enable this functionality, the "Date Check" flag needs to be marked in the price sheet configuration which allows to maintain overlapping records.

Configuration: /IRM/GPRSPRO > General Maintenance > Price Sheets > Define Price Sheets > Enable Date Check Checkbox

For more information, go to the Pricing_Auto Adjusting Dates attachment.



Pricing Master Request New Functionality /IRM/0IPPQ21/IRM/IPPQMSE38

Archiving ‐Archiving of master request scales, awards, sheet extension tables and sets are available. In order to archive a master request, the master request archiving control must be maintained via /IRM/0IPPQ21. Here the master request type, sales organization and residence time in days must be maintained. ‐Once the archiving control is setup, the user can complete the first step of archiving the master request via the /IRM/IPPQ_ARCH_WRITE report. When reviewing the results in the Log Summary, if the user processes more than one master request, the report will show the master request count, but not all of the master request numbers. As an example, the report will show the first master request number as an example. The Detail Log displays all of the master request numbers. ‐When the write report has been executed, the user can complete the final step of archiving by deleting the archived master request via the /IRM/IPPQ_ARCH_DELETE report. Once executed, the data will no longer be accessible in the tables (scales, awards, sheet extension tables and sets).

Pricing Performance New Functionality /IRM/IPxxASP/IRM/IPxxARM/IRM/IPxxPGM/IRM/IPSDAM/IRM/IPSDARM/IRM/IPSDPGM/IRM/IPPDAM/IRM/IPPDARM/IRM/IPPDPGM/IRM/IPPQM

User Controlled Performance Changes

There are user controlled performance changes that can be done through any BADI to be used during rules maintenance. The BEFORE_SAVE method in the interface has two new parameters, C_SKIP_FORMULAS, C_SKIP_USER_FIELDS and C_SKIP_POLICY.

Configuration path: /IRM/IPSPRO > Basic Functions > Pricing ‐ Sales (Pricing ‐ Purchasing) > Pricing Agreements (Purchasing Agreements) > Setup Agreements > Agreement Rules > Price Sheets > Define Price Sheets > Additional Attributes for Key Fields > Skip ChecksSkip Check Possible Values:‐ SPACE – Foreign checks and key value checks will be performed‐ X – Foreign checks will be skipped and key value checks will be performed‐ Y – Foreign checks will be skipped and key value checks will be skipped

Pricing Structural Pricing New Functionality /IRM/IPPQM Duplicate Root Materials In structural pricing for a master request, the system allows duplicate root materials by default and duplicate child materials depending upon the configuration.

Configuration:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Setup Agreements > Master Request > Define Master Request > Assign Explosion Profile > Agreement Rules > Define Explosion Profiles Explosion Source = BOM > Assign Price Sheets to Material Type > Material Assignment field.

Material assignment can be defined in the following three (3) ways:1. Unique across BOMs – if we maintain duplicate materials across all BOMs, then the backend sheet will consider as it as a single record for all BOMs.2. Unique within a BOM – if we maintain duplicate material with in a BOM, then the backend sheet will consider it as a single record only.3. Non‐unique – if we maintain duplicate materials across all BOMs, then the backend sheet will consider them as individual records for each material.



Pricing Structural Pricing New Functionality /IRM/IPPQM Duplicate Root Materials ‐ Qualifier Field

A new 'Qualifier' field in the Explosion Profile configuration has been introduced It will allow the user to determine the price sheet. This field has the following two options:1) Material type: The user can use standard material types here, create qualifier material type with material type (standard), application, condition type, condition table and field name values.2) User defined: The user can assign a user specific material type and fill the price sheet in the “assigned_price_sheet_fill” BADI method.

Configuration:/IRM/GPRSPRO > Basic Functions > Define Explosion Profiles > Assign Price Sheets to Material Type > Qualifier

Pricing Structural Pricing New Functionality /IRM/IPPQMCT04CL01MM01CU41 CS01

New Explosion Source Types There are two additional explosion sources in the explosion profile, they are: Manual BOM and Variant Configured. The purpose of this functionality is to maintain multilevel records for manual and variant configured BOMs in the structural price sheet within the master request.Manual BOM: When this source is chosen, the user can manually build the hierarchy "on‐the‐fly" within the structural pricing sheet. The user can explode or re‐explode the BOMs using this source.‐Reexplode Manual BOM: A new reexplode manual button has been added in the structural price sheet under the Rules tab. This is used to change existing materials rate, quantity values, and to add new materials.Variant Configured: When this source is chosen, the user can explode only configurable materials within the structural pricing sheet. In Variant Configured, creating a Manual BOM and reexplode to change existing materials rate and quantity values.‐In addition to the standard BOM prerequisites, the user must: 1) Create material flagged as configurable on the Basic Data 2 tab and the class assigned on the Classification tab in MM01.2) Create a configuration profile for the material in CU41.Configuration:/IRM/IPSPRO > Basic Functions > Pricing ‐ Sales > Pricing Agreements > Setup Agreements > Agreement Rules > Define Explosion Profiles > Explosion Sources

Pricing Structural Pricing New Functionality /IRM/IPPQM Quantity and Unit Fields The quantity and unit fields are new in the master requests structural pricing sheet Explosions popup.

Pricing Structural Pricing New Functionality /IRM/IPPQM/IRM/IPPQFTM/IRM/IPPQUPL

Upload, Import and Download Upload, import and download are now available to create, change or review a structural pricing data in a master request.For more information, go to the Pricing_Structural Pricing Upload Download attachment.

Rights Management (Dimensions)

Agreement Request

New Functionality /IRM/IPARFTM/IRM/IPxxARM/IRM/IPxxARUPL/IRM/IPxxARDNL

Dimension Sets Upload and Download

Users now have an option to easily upload and download dimension sets data into a file. This data can be used to add and/or delete dimension values.For more information, go to the Pricing_Agreement Request File Template with Dimensions attachment.




AgreementAgreement Request

New Functionality /IRM/IPxxASP/IRM/IPxxARM

Mass Change Dimension Sets Users have the ability to mass change sets through the Mass Process Header option within the agreement workbench. This functionality allows the user to maintain individual and collective sets by adding and/or deleting dimensions on multiple agreements at once.The two available actions are to add or delete dimensions. The adding action would check the node of the dimension in the respective category, while deleting would uncheck the node of the dimension in the respective category. There are two available sources when adding or deleting dimensions:1. Inclusion – The action on respective dimension has to be performed in inclusion dimensions.2. Exclusion – The action on respective dimension has to be performed in exclusion dimensions.


AgreementAgreement RequestDirect Agreement Master Request

New Functionality /IRM/IPxxASP/IRM/IPxxASPM_WS/IRM/IPxxARM/IRM/IPxxARM_WS/IRM/IPSDAM/IRM/IPSDAM_WS/IRM/IPPDAM/IRM/IPPDAM_WS/IRM/IPPQM/IRM/IPPQM_WS

Dimension Sets The dimensions functionality has been revamped since it was introduced in Release E SP1. Now, a new "Sets" tab has been introduced in agreements, agreement requests, direct agreements and master requests, which only appears if a dimension profile has been assigned to the agreement type, direct agreement type and/or master request type. For more information, go to the Pricing_Dimension Sets attachment.


AgreementDirect Agreement

New Functionality /IRM/IPAGFTM/IRM/IPxxASP/IRM/IPxxAGUPL/IRM/IPxxAGDNL/IRM/IPDAFTM/IRM/IPSDAM/IRM/IPSDAUPL/IRM/IPSDADNL /IRM/IPPDAM/IRM/IPPDAUPL/IRM/IPPDADNL


Users now have an option to easily upload and download dimension sets data into a file. This data can be used to add and/or delete dimension values.For more information, please see the Pricing_Agreement File Template with Dimensions attachment.


Data Maintenance Material

Change to Functionality

/IRM/EPPDM Dimensions Maintaining dimensions for a DM material is obsolete.


Dimension Cross Reference

New Functionality /IRM/GDMXREF /IRM/GDMXRFFTM/IRM/GDMXREFUPL/IRM/GDMXREFDNL

Dimension Cross Reference Upload and Download

Upload and download functionality is available to create, change, or review change to a dimension cross reference record. For more information, go to the Pricing_Dimension Cross Reference Upload Download attachment.


Dimension Cross Reference ‐ File Upload

New Functionality /IRM/GDMXREFUPL Check Entire File As part of Release E SP3 a new option is available in all the upload transactions. This option, Check Entire File, will allow the system to check the all records of a file being uploaded. Unlike in past releases, when the system would stop the upload process at the first error encountered, this option will report all errors encountered throughout the entire file to the users.





New Functionality /IRM/GFSUB/IRM/GDMXREFUPL




New Functionality /IRM/GDMXREFUPL Transfer Errors A new flag called Transfer Errors has been introduced in release ESP3. If an Upload file contains any invalid data, the system can download the errors into a separate file for the user to analyze and correct. The extension for the file is maintained in Transfer File Suffix field, which is only displayed when transfer errors option is selected.


Master Request New Functionality /IRM/IPPQFTM/IRM/IPPQM/IRM/IPPQUPL/IRM/IPPQDNL


Users now have an option to easily upload and download dimension sets data into a file. This data can be used to add and/or delete dimension values.For more information, go to the Pricing_Master Request File Template with Dimensions attachment.


Rights and Royalties

New Functionality /IRM/GCRM/IRM/GRCAM/IRM/IPxxASP/IRM/IPSDAM/IRM/IPxxM

Dimensions Evaluation in Claims, Sales Transaction Register and IP documents

The dimensions functionality has been revamped since it was introduced in Release E SP1. Now, a new "Sets" tab has been introduced in agreements. A set is a collection of dimensions assigned as key fields in the price records of agreements. The dimension price records are evaluated in pricing in Claims, Sales Transaction Register and IP documents For more information on dimensions, go to the Pricing_Dimension Sets attachment.

Configuration:Assign Dimension Profile in General tab of Claim Type configurationIPSPRO > Documents > Claims > Define Claim Types

Assign Dimension Profile in General tab of Sales Transaction Register Type IPSPRO > Documents > Transaction Register > Define Sales Transaction Register


Rights and Royalties

New Functionality /IRM/GCRM/IRM/GRCAM

Supporting DM materials in Claims/IP/TR

Earlier in claims, only posted DM Materials were supported. As of Release ESP3, non‐posted DM Materials are supported as well in Claims, IP and TR. In order to support the DM BOM materials, an Alternate BOM field has been added at the Item Category level.

The Source Document Type (Claim/TR) with DM materials will be carried over in IP as well. In order to support the DM BOM materials in IP, an Alternate BOM and Usage field has been added at the Item Control.

Configuration:

Claim Type ‐ /IRM/IPSPRO > Documents > Claims > Define Claim Types ‐In ‘Material Source’ field, select SAP or DM material.

Transaction Register Type ‐ /IRM/IPSPRO > Documents > Transaction Register > Define Sales/Purchasing Transaction Types ‐ In ‘Material Source’ field, select SAP or DM material.



Status Flow Delegation New Functionality /IRM/GDGUA /IRM/GDGM

Status Flow ‐ Delegation Rules Assignment to SAP Users

In Release E SP3, activities designated for an SAP user can be delegated to others. A new transaction code /IRM/GDGUA has been provided to accomplish this. To delegate activities to others, a delegation rule must be defined in the transaction /IRM/GDGM. Then, the SAP user whose activities have to be delegated has to be added to the new transaction code along with the corresponding delegation rule and the validity period for the delegation. The CC Original flag has been provided to send a copy of the original processor on all delegation emails.

Status Flow Steps New Functionality /IRM/GSFM End Flag In addition to the Start flag, an End flag has also been introduced. This will indicate to the system when the end of the status flow has been reached. Unlike the Start flag, this is an optional flag, as the system, by default, will otherwise use the last step of the status flow as the end step. When the status flow reaches the step with the End flag marked, the status flow, step, and the activities will be set as completed and no further processing will be allowed.

Status Flow Steps New Functionality /IRM/GSFM Start Flag Prior to Release E SP3, the user did not have an option to select the default start step for the status flow. Instead only a default flag was provided in the status flow workbench, /IRM/GSFM. However, introduced in Release E SP3, any status flow will contain a Start column, which is replacing the Default column. Here the user will be able to set any step in the status flow as the first step. Once a start step is identified, the status flow will follow the subsequent steps as defined in the outcome section.

Transaction IP Agreement Status Update

New Functionality /IRM/IPxxASP/IRM/IPxxM

Agreement Status update from IP document

As of Release E Service Pack 3, users can determine whether the agreement status field is update with the IP document settlement status. This control can be useful only if the settle by agreement flag is marked in the agreement/partner settlement parameter. This can be achieved by using the Turn off Agreement Status Update flag at the settlement profile level. If the flag is checked, the agreement status update is disabled and the agreement header will not be updated during settlement of the IP document. For more information, please see the attached document Agreement Status update from IP document .

Transaction IP Buckets New Functionality /IRM/IPxxBXKM Agreements fetched by the condition in Buckets

This is an inbuilt functionality provided in Release E SP3. Earlier the agreements were determined by each condition record, while updating the line item in the buckets was not considered. Instead, the buckets were updated with the agreement at the IP line item level and not with the agreements determined by the conditions. Now, with this new functionality, if the buckets are created for multiple agreements, then the IP document items update each of the respective buckets. This will help the user to track IP document efficiently.

For more information, please review the Updating Multiple Agreement Buckets Document.



Transaction IP Buckets New Functionality /IRM/IPSPRO Bucket Aggregation Revamp The Bucket Aggregation functionality has been enhanced to support the new Royalties Business Scenarios. Users are now restricted to only fields that are part of the buckets item criteria. In addition, the Aggregation Type functionality has been extended in the Bucket Type configuration. Multiple aggregation types can be created and their respective aggregation tables can be generated in the Bucket type configuration. As of this release, multiple value fields are allowed for the aggregation types. Also, the aggregation as per the conditions can be configured.

Configuration: /IRM/IPSPRO ‐> Basic Functions ‐> Buckets ‐> Define Bucket Types. For more information, please review the Bucket Aggregation Revamp Document.

Transaction IP Buckets New Functionality /IRM/IPxxBXCKM Performance improvement As of Release E SP3, the data type SSTRING is used for the field VAKEY instead of CHAR100. This change has been made to improve the memory utilization and, thereby, improving the performance. Also, to improve performance, the dynamic table is used to prepare VAKEY before the component of the structure is assigned.

Transaction IP Buckets New Functionality /IRM/IPxxBXCKM Update Only Active conditions flag in Bucket Type Configuration

In previous releases, buckets would update with both active and inactive conditions from the IP. With Release ESP3, users have an option to update the conditions based on the selection at the configuration. A flag is provided in configuration at the condition level of the bucket type. If the Update Active Condition flag is marked, only active conditions will be updated in Buckets. Otherwise, both active and inactive conditions will be updated in the bucket

Configuration:/IRM/IPSPRO > Basic Functions > Buckets > Define Bucket Types ‐ Mark the flag in Conditions node.

Transaction IP Dimensions New Functionality /IRM/IPxxBCKM Supporting Dimensions in Buckets

Dimensions are now supported in buckets. The dimension fields need to be appended to the bucket fields structure, /IRM/S_IPBCKFD, using the naming convention DIM_<Dimension Name> and having component type /IRM/GDIMDT. The user can use the dimension fields in criteria, item criteria and aggregation criteria of the bucket.

Configuration:/IRM/IPSPRO > Basic Functions > Define Bucket Types



Transaction IP DM Materials New Functionality /IRM/GCRM/IRM/GRCAM

Supporting DM Materials in Claims, Transaction Register and IP Documents

Previously, only posted DM Materials were supported in claims. Now, non‐posted DM materials are supported in claims, transaction registers (TR) and IP. In order to support DM BOM materials, the alternate BOM field has been added to the item category level.

The source document type (Claim/TR) with DM materials will be carried over to IP documents as well. In order to support the DM BOM materials in IP, the alternate BOM and usage field has been added to the item control.

Configuration:

Claim Type ‐ /IRM/IPSPRO > Documents > Claims > Define Claim Types ‐In ‘Material Source’ field, select SAP or DM material.

Transaction Register Type ‐ /IRM/IPSPRO > Documents > Transaction Register > Define Sales/Purchasing Transaction Types ‐ In ‘Material Source’ field, select SAP or DM material.

Transaction IP Document Parking New Functionality /IRM/IPSPRO Allow TAX postings during park In release ESP3, a new flag is available at the settlement profile level to record tax postings. If the flag is checked, tax posting will be recorded when the IP document is parked.

Configuration:IPSPRO‐‐>Documents‐‐> Accruals & Settlement ‐‐> Select Settlement Profile ‐‐> Check the box ' Tax Postings During Park'

Transaction IP File Upload New Functionality /IRM/GCULUPL/IRM/GPLUPL/IRM/GVNLUPL/IRM/GAWRUPL/IRM/GRCADMUPL/IRM/GCRDMUPL/IRM/GCRUPL/IRM/GRCAUPL


Transaction IP File Upload New Functionality /IRM/GFSUB/IRM/GCULUPL/IRM/GPLUPL/IRM/GVNLUPL/IRM/GAWRUPL/IRM/GRCADMUPL/IRM/GCRDMUPL/IRM/GCRUPL/IRM/GRCAUPL/IRM/IPPCUPL




Transaction IP File Upload New Functionality /IRM/GCULUPL/IRM/GPLUPL/IRM/GVNLUPL/IRM/GAWRUPL/IRM/GRCADMUPL/IRM/GCRDMUPL/IRM/GCRUPL/IRM/GRCAUPL/IRM/IPPCUPL


Transaction IP Payment Schedule

New Functionality /IRM/IPxxM Payment Schedule history mode rewrite

The Payment Schedule History Mode report has been re‐written in release ESP3. Previously, the system improperly updated the IP document after transfer with posting. With this correction, the system supports many different scenarios, previously not supported.

Transaction IP Status Flow New Functionality /IRM/IPxx34 Status Mass Change New to release E Service Pack 3 is the ability to use the m ass change functionality to set status flow outcomes and statuses for IP document reconciliations. This status mass change functionality is integrated into the mass change menu in the IP document reconciliation workbench. Users will have the ability to select the IP document reconciliations for which the outcomes and status have to be maintained.

Transaction Register

Deals New Functionality /IRM/GRCAM Deals in Transaction Register Prior to Release E SP 3, Deals were available only in Claims. However, now as part of release ESP3, Deals are also available in the Transaction Register.

Transaction Register

Status Flow New Functionality /IRM/GRCAM/IRM/GRCA37

Status Mass Change New to release E Service Pack 3 is the ability to use the mass change functionality to set status flow outcomes and statuses for transaction register documents. This status mass change functionality is integrated into the mass change menu in transaction register workbench. Users will have the ability to select the transaction register documents for which the outcomes and status have to be maintained.


Area Sub‐Area Conversion Program Topic Purpose Prerequisite Tips & TricksGlobal Text Engine /IRM/GTEXT_60E_SP2_SP3_CONV Texts Configuration

ConversionVistex has new text tables to be in synch with SAP text configuration. This program moves the existing Vistex text data to the new tables.

Global Business Script /VTA/BSE_60E_SP2_SP3_CONV Messages Handling In script

Script message handling changed, this program converts the existing message data to the new format.

Note 2235427 must be applied first.

Global Business Script /VTA/BSE_60E_SP2_SP3_ACTIVATE Reactivating All the Existing Active Scripts

The technique for Business Script code generation is changed. This program adjusts all existing active scripts to be in synch with the new technique.

Matrix Functions/Layouts

/IRM/IPMX_ESP3_ASSIGN_CONV Subset Workbench This report is to convert the functions and layouts currently assigned at subset level to usage level, since those items are now handled at the usage level.

Matrix Counter /IRM/IPMX_ESP3_CNTR_FILL Matrix counter A new counter technique was introduced in the Matrix to allow for correct updating when using parallel processing this program fills in the new field.

You do not need to execute this program is you have either of these notes applied, because the conversion program was already executed during the installation of these notes:2111996 ‐ 60E‐ Matrix update fails during parallel processing of IP documents 2139595 ‐ 60E ‐ Matrix update changes for parallel processing of IP documents

Matrix Derivations /IRM/IPMX_ESP3_DERV_CONV Matrix Workbench The change of a key field in the Matrix Derivations Source Mapping table to a non‐key field requires conversion of the data.

Matrix Explosion /IRM/IPMX_ESP3_EXPL_CONV Subset Workbench The change of a key field in the Explosions Characteristic Mapping table to a non‐key field requires conversion of the data.

Matrix Functions /IRM/IPMX_ESP3_FNTYPES_REVAMP Matrix Workbench Restructuring Matrix Function Types into two categories, Function type and Implementation type, requires conversion of all matrix functions.

Matrix Comments /IRM/IPMX_ESP3_GEN_CMNT_TABLES Matrix Workbench Generating Comments tables /IRM/IPMX****C, /IRM/IPMX****CA, /IRM/IPMX****CT, and /IRM/IPMX****H to support comments functionality for existing matrices

Matrix Proforma /IRM/IPMXP_ESP3_KFCOND_CONV Proforma Profile Configuration

The change of a key field in the Proforma Profile Key Figure Conditions table to a non‐key field requires conversion of the data.

Agreement Schedules /IRM/IPAGSC_DESCR_ESP3_CONVERT Agreements/ Agr. Requests

In the previous release you could not maintain language specific schedule descriptions; SP3 introduces this ability. This report will convert existing schedules descriptions into the new format to support descriptions in multiple languages.

IRMIPM 60E SP3: Post‐Upgrade Conversion Reports


Area Sub‐Area Authorization Object Defined in Transaction ActionsMatrix Subset V_IP_MXFAG /IRM/IPMXSM While assigning functions to Subset (transaction /IRM/IPMXSM), the user (configurator)

can enter the authorization group. Based on this authorization group a check will be performed on the function during execution.The authorization group would need to be assigned to the users via authorization object V_IP_MXFAG who are authorized to perform the function.

Matrix Subset V_IP_MXLAGMatrix Planning Scenario V_IP_MXPAG

Matrix Planning Object V_IP_MXPOB

IRMIPM 60E SP3: New Authorization Objects


Campaign IDOC’s

Page 1 of 1

In order to move the campaign data from the legacy system to SAP, a new IDOC type, /IRM/CMPGNS01, and a message type, /IRM/CMPGNS, have been created. The IDOC type supports the movement of the Header, Dates, Texts, Organization and Partner data. The following the segments are used for the each section:

Header information: /IRM/CMPGNK01

Additional Identifiers: /IRM/AGMTK02

Document Dates: /IRM/DATES01

Header Text Identification: E1EDKT1

Document Header Texts: E1EDKT2

Organizational data: E1EDK14

Header Partner: E1EDKA1

The two API’s are as follows:

1) Inbound (create a campaign with IDOC information): /IRM/IPCGIDOC_INPUT_CMPGNS

2) Outbound (create IDOC with campaign information): /IRM/IPCGIDOC_OUTPUT_CMPGNS

Updating Multiple Agreement Buckets

Page 1 of 3

This is an inbuilt functionality provided in Release E SP3. Earlier the agreements were determined by each condition record, while updating the line item in the buckets was not considered. Instead, the buckets were updated with the agreement at the IP line item level and not with the agreements determined by the conditions. Now, with this new functionality, if the buckets are created for multiple agreements, then the IP document items update each of the respective buckets. This will help the user to track IP document efficiently. For example, consider the IP document pricing example below.

The condition type ZSDP and the condition records are determined two agreements, 5991 and 5992.


Page 2 of 3

When the IP document is created the line items will update the buckets for each of the agreements.


Page 3 of 3

Structural Pricing - Upload/Download

Page 1 of 4

Overview

Upload, import and download are now available to create, change or review a structural pricing data in a master request.

File Template

In order to upload or download a structural pricing data, a file template is required. This can be created through transaction /IRM/IPPQFTM.

On the Section tab, the user must maintain the Structural Pricing section if they want to upload and/or download structural pricing data in/from a master request. Here, a user can specify the position of the section in Excel sheet by specifying the section indicator(s) or the start row value(s). However, both the section indicator and start row should not be entered. If the user specifies the section indicator(s) here, then each row in Excel should start with the corresponding section indicator. The start row and end row position are used only for single document upload. For mass upload, section indicators should be specified.

On the Mapping tab, the section needs to have the below fields, at a minimum, to upload/download successfully: • STUFE – Level • MATNR – Material • WERKS – Plant • MTART – Material Type • MENGE – Component Quantity • KBETR – Rate Mapping Tab Example


Page 2 of 4

Upload

The upload functionality is available from /IRM/IPPQUPL and /IRM/IPPQM.

• From both of these transactions, users can upload a file to: o Create a master request with one or multiple BOMs on it.

In the below example, level 0 in column B represents the highest level in each BOM.

Spreadsheet Example

o Change a master request(s) structural pricing data. • The /IRM/IPPQUPL transaction is split into three sections: Desktop Source, File Source and Action.

o In the File Source section, the File Location field defaults to the Desktop Source.

Import

The import functionality is available from /IRM/IPPQM.

• From this transaction, users can import a file to create a single or multiple BOMs on a master request. o On the structural pricing sheet in a master request, a new ‘Import BOM Materials’ icon has been

added in the ‘Create Explosion’ window.

o After clicking this icon, the ‘Import Items from File’ window is displayed. Here the field positions and/or field values must be maintained.


Page 3 of 4

o After maintaining the field positions or field values, the user clicks the Continue icon. At this point, the corresponding values will be added to the ‘Explosion’ window.

o Upon clicking the Continue icon in the ‘Explosion’ window, price records are added to the structural pricing sheet.


Page 4 of 4

Download

The download functionality is available from /IRM/IPPQM.

• From this transaction users can download master request(s) with structural pricing data. This is done by going to the Menu and clicking on Extras, then Upload/Download. Here a new window is displayed and the ‘Download’ Action must be chosen. Popup Window Example

Bucket Aggregation Revamp

Page 1 of 4

The Bucket Aggregation functionality has been enhanced to support the new Royalties Business Scenarios. Users are now restricted to only fields that are part of the buckets item criteria. In addition, the Aggregation Type functionality has been extended in the Bucket Type configuration. Multiple aggregation types can be created and their respective aggregation tables can be generated in the Bucket type configuration. As of this release, multiple value fields are allowed for the aggregation types. Also, the aggregation as per the conditions can be configured. The configuration is done at the Bucket type configuration: /IRM/IPSPRO Basic Functions Buckets Define Bucket Types. In the Aggregation type configuration, while defining the Aggregation type criteria, only those fields which are used for item criteria of a particular Bucket type are available.

In Aggregation Types user can create and assign multiple Aggregation Types to a particular bucket type.


Page 2 of 4

When maintaining value fields, multiple value fields can be maintained. Value fields can be a

combination of currency fields, weight fields, volume fields, or quantity fields, provided the fields share

a single unit of measure. For example, the Net Weight and Gross Weight can be used together as they

have one unit of measure GEWEI, Weight Unit.

When selecting the condition aggregation option, the user can maintain the value field and specify all

the conditions for which aggregation will be done.


Page 3 of 4

If only active conditions are to be considered during aggregation, then the Update Only Active

Conditions flag must be selected.

Once the aggregation configuration is completed, the user can generate the aggregation table by

clicking the generate button .

Once the table is generated, the user can review the name of the table by selecting the Technical Details

button.


Page 4 of 4

Copy Schedules and Periods

Copy Schedules and Periods Below screenshot gives an option to Copy Schedules and Periods, this copy functionality is available only when user copies the agreement with Same Validity period. This functionality is made available across all modules of Vistex.

And when the user chooses for a New Validity period during agreement copy, Copy Schedules and Copy Periods options is disappeared as it is logical when the new validity period for the agreement is considered.

Dimension Sets

Page 1 of 4

Overview The dimensions functionality has been revamped since it was introduced in Release E SP1. Now, a new "Sets" tab has been introduced in agreements, agreement requests, direct agreements and master requests. This tab only appears if a dimension profile has been assigned to the agreement type, direct agreement type or master request type. A set is a collection of dimensions assigned as key fields in the price records of agreements, agreement requests, direct agreements and master requests. These price records are validated in claims based on the sets assigned to it.

Sets Tab

Sets on the Sets tab in agreements, agreement requests, direct agreements and master requests can be defined in two ways:

1. Individual Set – maintain multiple dimensions with at least one dimension from each category in the inclusion. (A dimension profile is required for an individual set)

2. Collective Set – maintain a group of sets with at least one set in the inclusion.

Review Tab The Review tab within each set displays the dimensions of inclusion and exclusion that are separated by “Except” as a keyword.

Dimension Sets

Page 2 of 4

Rules – Set as Key Field The new sets field, IRM_DMSET, needs to be assigned to the condition table from the price sheet on the agreement, agreement request, direct agreement or master request. Sets can be created, maintained and displayed from the price record or on the Sets tab.

Creating a Price Record with a Set Two ways to create a price record with a set include:

1. Assigning an existing set o If the set already exists on the Sets tab, when creating the new record,

the user can select one of the existent sets in the set field. o Sets can be assigned in the GUI transactions and the Web Interface

transactions. In order to maintain or display sets in the Web Interface

transactions, the new Sets block needs to be included in the Block Profile assigned to the agreement, agreement request, direct agreement or master request type in configuration.

2. Creating a new set directly from the price record o If creating a set from the price record, when entering values on the new

record, the user can right-click on the set field and choose the Create Set option.

o This functionality is not available in the Web Interface transactions.

Maintaining a Set

The two ways to maintain a set are as follows: 1. From the Sets tab

Dimension Sets

Page 3 of 4

o Available in the GUI transactions and the Web Interface transactions. 2. From the price record

o In order to change a set from the price record, the user can right-click on the set field and choose the Change Set option.

o This is not available in the Web Interface transactions.

Displaying a Set

The user can display sets in the following ways: 1. From the Sets tab

o Available in the GUI transactions and the Web Interface transactions. 2. From the price record

o In order to display it from the price record, the user can right-click on the set field and choose the Display Set option.

o This method is not available in the Web Interface transactions.

Copying a Set

When copying agreements, agreement requests, direct agreements and master requests, there is a ‘Copy Sets’ checkbox that is available to copy sets from the source document(s) to the new target document(s). This checkbox will also appear when creating agreements, agreement requests and direct agreements from the Postings tab in a master request.

Searching for a Document with a Set

When on the search screen within the agreement, agreement request, direct agreement and master request workbench, the user now has the option to search data by sets. The

Dimension Sets

Page 4 of 4

options to search include Sets Description, Dimension Profile, Dimension Category and/or Dimension values.

Review Sheet

Sets can be displayed on the Review Sheet ( ) within the agreement, agreement request, direct agreement and master request workbench.

Transactions

/IRM/IPxxASP – Agreement Workbench /IRM/IPxxARM – Agreement Request Workbench /IRM/IPSDAM – Direct Agreement Workbench /IRM/IPPDAM – Direct Agreement Workbench /IRM/IPPQM – Master Request Workbench

Evaluations in Master Request The Evaluation tab with the master request allows the user to maintain census or compliance data, or suitability to determine the applicable master request. The evaluation tab functionality can be as simple as a collection tool for data or used to cross check that all the necessary information is entered. If the assigned evaluation type is marked for auto-creation in the master request configuration, the evaluation entry will automatically be created in the Evaluation tab while a new master request is being created. Required Setup Steps:

• Evaluation Elements • Evaluation Template • Evaluation Type • Assign Evaluation Type to Master Request Type

1. Evaluation Elements: Evaluation elements are created using transaction code /IRM/GEVELM.

Element type, data type, length, and topic are required. Depending on the element type/data type maintained on the evaluation element, the system provides different value source options.

2. Evaluation Template: Using the evaluation elements already existing in the system, a

template is created. This template will determine format of the fields/values that will be displayed. Evaluation templates are created using transaction code /IRM/GEVTPM.

3. Evaluation Type: Upon creation of the Evaluation Template, Evaluation type is created. During

the creation of the evaluation type, the object type is selected/assigned. Evaluation types are created using transaction code /IRM/GEVTM.

4. Assign Evaluation Type to Master Request Type: Select an existing master request or the user

can create a master request type along with description, internal number range and validity dates. Select the Evaluation node and assign evaluation type; assigned evaluation types can be marked for auto creation.

a. Configuration Path: /IRM/IPSPRO Basic Functions Pricing Sales Pricing Agreements Setup Agreements Master Request Define Master Request Evaluation Types

Page 1 of 1

Composition in Claim and Transaction Register

Page 1 of 3

Composition has been integrated into claims and transaction register (TR) to support royalties. A composition material can be an ECC or DM material that explodes similarly to a BOM material in claims and transaction register.

Configuration in claims and TR to support composition functionality: /IRM/IPSPRO > Documents >

> Claims > Define Claim Types > Transaction Register > Define Sales/Purchasing Transaction Types

1. Maintain the composition relevant fields in the item category definition of the claim/TR

type

Lower Level Item Category – The assigned item category will be used for

exploded materials. Composition Type – Materials with the assigned composition type are

considered in the claim/TR. Percentage Conditions – Percentages assigned in the compositions for materials

and partners are passed to the assigned conditions in pricing. Split by Partners - When the “Split by Partners” flag is enabled, exploded items

are split by the partners. The percentage assigned to the partner in the composition material will carry forward to the pricing. When this flag is not enabled, the related percentage will be saved in the:

o /IRM/GCRPTR table (Claim Partners) for claims o /IRM/GRCAPTR table (Transaction Partners) for TRs

2. Configure the Bill of Material numbering for the claim/TR type


Page 2 of 3

Composition functionality is supported in Claim and TR domains:


Page 3 of 3

Example of composite explosion in claims:

Master Request File Template with Dimensions

Page 1 of 1

Overview Users now have an option to easily upload and download dimension sets data into a file. This data can be used to add and/or delete dimension values.

Details

In order to upload and download sets data into a file, two new sections have been introduced in the file template, Dimension Set Header and Dimension Set Item. Each of these new sections need to have the below mandatory fields mapped, at a minimum, to upload/download successfully. Section Field Name Field Description Mandatory or Optional? DH Dimension Set Header PQNUM Master Request Mandatory DH Dimension Set Header SETID Set Mandatory DH Dimension Set Header DESCR Description Optional DH Dimension Set Header SETTY Dimension set type Optional DH Dimension Set Header DMPFL Dimension Profile Optional DI Dimension Set Item PQNUM Master Request Mandatory DI Dimension Set Item SETID Set Mandatory DI Dimension Set Item SETNO Include/Exclude Set Optional DI Dimension Set Item EXCLS Exclusion Optional DI Dimension Set Item DIMEN1 Dimension Determined Optional DI Dimension Set Item DIMEN2 Dimension Determined Optional DI Dimension Set Item DIMEN3 Dimension Determined Optional DI Dimension Set Item DIMEN4 Dimension Determined Optional

Transactions /IRM/IPPQFTM – Master Request File Template /IRM/IPPQM – Master Request Workbench /IRM/IPPQUPL – Upload Master Request /IRM/IPPQDNL – Download Master Request

Master Request – Sales and Purchasing Direct Agreements

Page 1 of 1

New functionality is available in Master Request Workbench where users can create and maintain Direct Agreement and Agreement Requests from the Postings tab. Prior configuration settings are needed in order to use this functionality. The following steps are needed in customization in order to use this new functionality. It is not necessary to follow the steps in the order mentioned below except creating Master Request Type which is a base step; however, some of the steps are dependent on others. For example, Activity Stages are needed to maintain Activity Steps, whereas maintaining Condition Map IDs are a completely independent step, but are required to assign Condition Map IDs to Activity Steps.

• Create Master Request Type • Assign Price Sheets to Master Request • Maintain Posting Stages • Maintain Posting Steps • Maintain Condition Map • Assign Condition Map IDs to Posting Steps

Configuration: /IRM/IPSPRO Basic Functions Pricing Sales Pricing Agreements Setup Agreements Master Request

Define Master Request Define Condition Map

1. Create Master Request Type:

Users can create a master request type along with description, internal number range and validity dates. All other fields and options can be added or modified anytime, except for the master request type itself.

2. Assign Price Sheets to Master Request Type: Users can assign price sheets to the master request. All of the fields are mandatory and need to be populated in order to complete this step. Multiple applications and price sheets can be assigned here. Only the sheets assigned here are available in the master request workbench for this type.

3. Maintain Posting Stages: Users need to set up stages in this tab. Multiple stages can be maintained within each master request type. Users have to maintain the stage, position and description fields.

Example stages: Master Request, Price Proposal, Agreements, Agreement Request, Deal, Deal Request, etc.

4. Maintain Posting Steps: Users need to maintain the activities needed for the master request type. Multiple posting steps can be maintained within each master request type. Postings have to be linked to the stages created. Users will also have to maintain related document types for those postings.

Example steps: Create Master Request, Create Price Proposal, Create Billback Agreements, Create Chargeback Agreements, etc.

5. Maintain Condition Map: Users have to create a Condition Map IDs. Within it the user specifies the price sheets with target application, condition type, and condition table. Then each price sheet needs to be setup with price record mapping that maps the target application, condition type, condition table and field(s) to the source condition type(s), condition table(s) and field(s).

6. Assign Condition Map IDs to Posting Steps: Condition Map IDs need to be assigned to the posting steps in the master request type.

Mass upload of award Request

Page 1 of 3

Mass of Award Request New to Release E Service Pack 3, users can create and download Award requests using the upload/download functionality using the transactions codes /IRM/GAWRUPL and /IRM/GAWRDNL. While downloading award requests, if a group of award requests are selected, the corresponding information is download to a local file.

The document dowloaded will display corresponding header and item fields according to the award request file template selected.


Page 2 of 3

In the upload workbench, the user must select the file template, path and location corresponding to the desired document. After the selections are made and the transaction is executd, the award request will be created in accordance to the data from the file. In addition, the award requests can be posted simultaneously by selecting the “Post” flag.


Page 3 of 3

• File template for the award request consist of the header and item fields which are to be mapped from the document data as shown below

Auto Adjusting Dates on Price Records

Page 1 of 5

The purpose of the functionality is to save more than one overlapping record, which was previously not allowed. When a user tries to maintain overlapping records, the dates will be adjusted automatically by overlapping, splitting or overlaying them with the existing condition records based on the validity dates. To enable this functionality, the "Date Check" flag needs to be marked in the price sheet configuration. Configuration: - /IRM/GPRSPRO > General Maintenance > Price Sheets > Define Price Sheets > Enable Date Check Checkbox

1. Create new records with auto-adjusting dates in price records: System is now allowing splitting, overlapping, overlaying of price records by auto-adjusting dates on them.

1.1 Overlapping case: Two price records with same key fields can be added with overlapping dates

Example: In /IRM/GPR01, a user can add two price records with the same key fields like Sales Organization, Distribution Channel and Material and different validity dates.

1st record valid dates: from Jan 2015 to Dec 2020 (new record)

2nd record valid dates: from May 2015 to Dec 2020 (new record)

In the above example system will create two new records based on the validity dates as below.

1.2 Splitting case: Two price records with same key fields but different validity dates can be added,

whereas the validity dates of the second record will fall in between the validity date of the first record.


Page 2 of 5

Example: /IRM/GPR01, a user can create two same new records with validity dates that fall in between the 1st record

1st record valid dates: from Jun 2015 to Dec 2020 (new record)

2nd record valid dates: from Aug 2015 to Oct 2016 (new record)

In the above example, the system will create three new records based on the validity dates as below.

2. Create new price record and change existent record with auto-adjusting date in price records: The system is now allowing splitting, overlapping and deleting records by auto-adjusting dates in price records.

2.1 Overlapping case: A new price record needs to be added with the same key fields as an existing record, where validity dates given on the new record will overlap with the validity dates of existing record.

Example: /IRM/GPR01 (or) 02, Create price sheet with one new record and change existent record.

1st record valid dates: from Jul 2015 to Dec 2025 (existent record)

2nd record valid dates: from May 2016 to Dec 2025 (new record)


Page 3 of 5

In the above example, the system will create one new record and change the validity of the existing record based on the validity dates as below.

2.2 Splitting case: A new price record needs to be added with the same key fields of an existing record, where the validity dates given on the new record will fall in between the validity dates of an existing record.

Example: /IRM/GPR01 (or) 02, Create price sheet with one existent record and new record.

1st record valid dates: from Feb 2015 to Dec 2050 (existent record)

2nd record valid dates: from May 2016 to Dec 2016(new record)


Page 4 of 5

In the above example system will create two new records and change the validity of the existing record based on the validity dates as below.

2.3 Deleting case: A new price record needs to be added with the same key fields of an existing record, where the validity dates given on the new record will overlay with the validity dates of an existing record.

Example: /IRM/GPR01 (or) 02, Create price sheet with one existent record and new record.

1st record valid dates: from May 2015 to Dec 2020 (existent record)

2nd record valid dates: from Mar 2015 to Dec 2020(new record)

In the above example, the system will create one new record and deletes the existing record based on the validity dates as below.


Page 5 of 5

The changes in the functionality of price records are applicable in following workbenches.

• Transaction Codes

o /IRM/GPR01/02 – Classic maintenance

o /IRM/GPR04/06 – Profile-based maintenance

o /IRM/GPR26 – Index-based maintenance

o /IRM/IPxxASP – Agreement workbench

o /IRM/GxDLM – Deals workbench

o /IRM/IPxDAM – Direct agreement workbench

Launchpad Plus - Changes and Enhancements

Page 1 of 9

Contents Introduction ............................................................................................................................................ 2

Grouping Tiles ..................................................................................................................................... 2

Launchpad Work List ........................................................................................................................... 4

Launchpad Report Tiles ....................................................................................................................... 6

Amount Tiles ................................................................................................................................... 6

Tile Animation ..................................................................................................................................... 7


Page 2 of 9

Introduction Introduced during Release E SP2, the new generation Launchpad was intended to give the Launchpad a new look by allowing the user to have control over the display settings in a personalized tile view. As part of Release E SP3, new functionality has been added improving upon this by providing users an easier way to personalize the Launchpad profile in terms of the data and display. Now users are able to group tiles, display multiple display documents, control animations, and display cumulative amounts of reports.

Grouping Tiles Users now have the ability to group tiles together within a single column on the new generation Launchpad. To group tiles within a single column, the user must access the Launchpad Profile using the Launchpad Builder transaction, /IRM/GLNPBM_WS. Selecting the corresponding column and clicking

the settings button , the user will be able to provide a description, font size, and color.

After the entries are made and the user clicks continue, the description entered would be displayed at the top of the corresponding column.


Page 3 of 9

Then in the Launchpad BSP transaction, /IRM/LAUNCHPAD_WS, each column containing a description will have an outline grouping the tiles associated with it. In addition, when the user scrolls the cursor within the column, the outline will be highlighted.


Page 4 of 9

Launchpad Worklist In Release E SP3, when a user adds a document to the work list of a workbench, the document can be viewed from the new generation Launchpad. The documents added will be stored under the worklist link at the top of the Launchpad screen and will be segmented by the document type.

From there, the user can review the document by clicking the Show button corresponding with the desired document. If the user wants to review several documents, the user must select which documents to review by checking the box next to each document and then click the Show button

at the top of the document section. Please note, the system will only display multiple documents of the same type at one time. In either case, clicking the show button will open a new tab displaying the corresponding BSP transaction.

In the case of a single document, the system will display the document chosen.


Page 5 of 9

However, in the case of multiple documents selected, the system will display the list of documents.

If the user wants to review the information related to a document, but does not want to open a

different BSP transaction, the More button will display a popup window with selected information regarding the document.


Page 6 of 9

Unlike the Show option, this option can only be used for a single document at a time.

Launchpad Report Tiles As part of the new release changes have been made to the tiles that contain reports to reduce load times and improve usability. The first improvement, in order to speed up the loading time of the Launchpad Profile, any tile that contains a report chart will be automatically generated in the background after the profile is displayed. Therefore, when displaying the Launchpad profile in the transaction /IRM/LAUNCHPAD_WS, the system will generate the pages, tiles, links, and background first. Then after everything has been generated, the chart tile will be generated and displayed. This allows users to access the links to the other tiles in a timelier manner, instead of waiting for the chart to be generated. In addition, this allows the user to see more up to date charts.

Amount Tiles A new option added to the report links is the ability to add a cumulative amount, as well as, summary amounts. After adding a report to a tile in the new generation Launchpad Builder, transaction /IRM/ GLNPBM_WS, a new popup window will be displayed. Here the user can choose how to evaluate summarize the report.


Page 7 of 9

If no selections are made, the tile will display any available charts within the tile. However, if the user selects an evaluation field, the system will display the total amount of the chosen field in the tile.

If a Summarize By option is chosen, the system will display the amounts based on the field chosen when the user scrolls the cursor over the tile.

Every user has their own set of tasks to perform or information to see and, as such, the user needs the ability to control over what the profile displays and the manner in which it is displayed.

Tile Animation To allow users to control the display of the new generation Launchpad Profiles, two new options have been added to the Animation tab in the tile settings. These options are set in the new generation Launchpad Builder transaction, /IRM/GLNPBM_WS, at the individual tile level. The first option, on click, will cause the system to display details only when the user clicks on the tile. When choosing this option from the Detailed Scroll dropdown, the links in the tile will be scroll up to the top after the user clicked on the tile.


Page 8 of 9

The second option added to the Animation tab is the Delay option. This option is available when selecting the top, bottom, right, or left option from the Details Scroll option menu. The user will have the option to enter an amount of time into the Delay field. Then when reviewing the Launchpad profile using transaction /IRM/LAUNCHPAD_WS, the system will wait the specified amount of time after the user places the cursor over the tile before displaying the tile details.


Page 9 of 9

Please note the entry made in the Delay field is in milliseconds. Therefore, if a user enters the value 4000, the system will wait 4 seconds before displaying the tile details.

Editions in Master Request

Page 1 of 8

The purpose of this functionality is to track all the changes done to the master request document like creating postings, adding price records, changing price records, and/or deleting price records. The user can maintain and display editions from the Editions tab; only one edition will be active at a time. If an edition type is assigned to master request type, the status profile assigned in the master request type level will be inactive and the status profile assigned to the edition type will be active. Required Setup Steps:

• Create Edition Types • Assign Edition Types to Master Request

1. Create Edition Type: Users can create an edition type along with its description in /IRM/IPSPRO.

a. Configuration Path: /IRM/IPSPRO Pricing Sales Pricing Agreements Setup Agreements Master Request Define Edition Types

2. Assign Edition Types to Master Request Type: Users can assign multiple editions types to a

master request type in the edition types node. If only one edition type is assigned that will be selected as the default edition, if multiple edition types are assigned, the system will allow for choosing the default edition. A status profile can be assigned to each edition type. By enabling the Allow Multiple checkbox in an edition type, the system will allow the creation of the same edition multiple times in the master request document.

a. Configuration Path: /IRM/IPSPRO Basic functions Pricing Sales Pricing Agreements Setup Agreements Master Request Define Master Request Edition Types

2.1 Allowed Postings: In the edition types assigned to the master request type, the user needs to assign the postings steps for which postings should be created. This enables the user to restrict the creation of postings.


Page 2 of 8

2.2 Automatic Postings: The user can assign posting steps for automatic creation of postings like agreement, agreement request, deal, deal request or master request based on the user status of the master request.

The user has the option to select the posting steps for which automatic posting should be created based on the user status of the master request.


Page 3 of 8

Master Request Document:

• Edition Fields: In a master request document that has the above edition types setup, the current user status and current edition will be derived from the edition type. On the Postings tab, the Edition dropdown is displayed, which is not available in the master request documents that do not have the edition types configuration. The status profile maintained on the edition type will be displayed on the Status tab of the master request document.

• Edition Tab: On the Editions tab in a master request, one edition will be created as the default that is selected as the default in the edition type. The edition description field is mandatory that needs to be populated by the user.


Page 4 of 8

• Rules Tab: In the Rules tab on a master request, when the user adds a new price record, the

edition field on the price sheet will be auto populated with the current edition number. This enables the user to track changes made to the master request under the active edition.

• Status Update from Editions Tab: Users can update the status of the master request document

from the Editions tab. In the Editions tab, the user can select the active edition and then click on the status button, which will open the status popup screen. The status can be updated in the status popup tab, which behaves the same as the Status tab on the master request.

Upon updating the status, the status on the header will be updated based on the status profile configuration.


Page 5 of 8

If the status of the master request document is updated and automatic postings are configured, postings will be automatically created in background at the time of save.

• Closing/Creation of Active Edition: To close the active edition, the user needs to click on the close icon. Upon closing the edition, the edition specific data can be viewed only in display mode. No postings will be allowed from the closed edition. However, the user can still change


Page 6 of 8

the header data like General, Organization, Additional Data1 tabs etc. Whereas if the user needs to add a new edition in the Editions tab to create postings and for adding new rules.

The create edition icon will only be enabled if all of the editions are closed.

If an edition is marked for multiple creation, the user will be able create the same edition multiple times.


Page 7 of 8

• Edition Specific Data View: Edition specific postings can be viewed in both the Postings tab and the Editions tab. To view edition specific postings data in the Postings tab, the user needs to select the edition from the dropdown.

To view edition specific postings data In the Editions tab, the user needs to select the edition and click on the Posting Documents icon.

The created edition specific postings will be displayed in a popup.


Page 8 of 8

• Copy Edition Specific Rules Data: While creating a copy of a master request to the same master request type or different master request type, the “Copy Open Edition Rules” checkbox is provided to restrict the copy all unwanted rules data. If the user marks flag for “Copy Open Edition rules”, the rules that are created under the current active edition will be updated to the copied master request document. If the user does not mark the flag for “Copy Open Edition Rules”, all of the rules data will be updated to the copied master request document.

Agreement Request File Template with Dimensions

Page 1 of 1


Details

In order to upload and download sets data into a file, two new sections have been introduced in the file template, Dimension Set Header and Dimension Set Item. Each of these new sections need to have the below mandatory fields mapped, at a minimum, to upload/download successfully. Section Field Name Field Description Mandatory or Optional? DH Dimension Set Header ARNUM Agreement Request Mandatory DH Dimension Set Header SETID Set Mandatory DH Dimension Set Header DESCR Description Optional DH Dimension Set Header SETTY Dimension set type Optional DH Dimension Set Header DMPFL Dimension Profile Optional DI Dimension Set Item ARNUM Agreement Request Mandatory DI Dimension Set Item SETID Set Mandatory DI Dimension Set Item SETNO Include/Exclude Set Optional DI Dimension Set Item EXCLS Exclusion Optional DI Dimension Set Item DIMEN1 Dimension Determined Optional DI Dimension Set Item DIMEN2 Dimension Determined Optional DI Dimension Set Item DIMEN3 Dimension Determined Optional DI Dimension Set Item DIMEN4 Dimension Determined Optional

Transactions /IRM/IPARFTM – Agreement Request File Template /IRM/IPxxARM – Agreement Request Workbench /IRM/IPxxARUPL – Upload Agreement Request /IRM/IPxxARDNL – Download Agreement Request

Summaries

Page 1 of 10

Using the Summaries functionality, the Matrix data is represented in a grid format based on the Key figures, Characteristics, and Variables combinations assigned for a particular summary type in the subset workbench. The user can also view the summaries data in the waterfall views. Additionally, summaries can be assigned at subset workbench to represent the matrix data in a grid format in the planning workbench for better comprehension and flexibility. Summaries are usage dependent, meaning the user can plan a different set of summaries for different usages of a single subset. Summaries consist of two types, Table type and Total Type.

Table Type Summary: Here the user can have the ability to assign Characteristics, Key figures, Variables, and the Total Summary for an individual Table type summary. The summary represents the data according to the combinations selected at the subset level and presents the data in a grid format in the planning workbench. Here, the user defines a custom set of functions for each Table specific summary type using script/measure.

Total Type Summary: Table type summaries are useful for representing the total summary value for the available key figures. Here user has the feasibility of assigning only the key figures (including Derivation key figures). These Total summary types can also be assigned for the above Table type summaries for representing whole set of key figures data.

The below example illustrates the sequence of steps involved in defining the Summaries at the subset workbench. As shown in the screen shot, the Summaries functionality is listed as part of the usage details for the matrix and subset.

Summaries

Page 2 of 10

For this example, the Planning Summary type, SUM1, and the Summary Type, Table, with the description Material Summary, have been set. The Functions button has been provided to allow users to define the corresponding Script/Measure. In addition, the Planning Summary fields have been assigned to the Material Summary are a combination of Characteristic Key Figures. These key figures have the Entry Check option selected, allowing the values to be edited in the planning workbench.

In the below screen shot, utilizing the script/measure functionality, the user defined two functions, ZFUN1 and ZFUN3, as a place holder for an Increase in net price and summation respectively. The function ZFUN1 has been marked as Function Load, which indicates that the system executes this when loading the summary data. While the ZFUN3 function has been marked as Function Demand, this allows the user to control by selecting the function from the Tool Tip menu.

Summaries

Page 3 of 10

Similarly, as the screen shot below displays, the summary of the table type, SUM2, has been defined for the same subset and usage as the previous table. In addition, the table, SUM2, contains the associating planning fields, including a Total Summary field, SUM3.

In the following screen shot, the Customer Summary has been defined by the user with two functions, ZFUN1, Increase in Delta in ADQTY, and ZFUN2, Increase in Net Price, through the script/measure functionality. The function ZFUN1 has the Function Load option selected, while the ZFUN2 function has the Function Demand option selected.

The next screen shot displays the definition for the Total Summary type function, SUM3, along with the Planning Summary Fields. For this type of summary, Total, the user is unable to define the functions. Instead, the user can assign the Derivation Key Figure ZYAMT, Sales History Accepted Amount.

Summaries

Page 4 of 10

Waterfall Elements and Waterfall Views for Representing Summary Data:

To present the summary data in the waterfall view, the list of waterfall elements must be defined for the subset and usage, as shown in the screen shot below.

Similarly, the waterfall views are to be defined, for which the above waterfall elements are assigned. An example of this definition and assignment is shown in the screen shot below.

Summaries

Page 5 of 10

Summaries at Planning Workbench

In the planning, the user will select the corresponding matrix, subset, usage and the time period desired. After the selections are made and the planning workbench is executed, the system will display to the data related to the selections made, similar to the screen shot below.

From here, the user can navigate to the summaries associated with the matrix and subset combination. To access the summaries, the user can click the arrow next to the Summary header to display the Summary field. Then, as shown in the screen shot below, the user can select from the list of defined summaries.

Summaries

Page 6 of 10

Once the summary is selected, the matrix data related to the combination of Characteristics, Key Figures, and Variables with the selected summary will be displayed. In the screen shot below, the Material Summary has been selected and the summary data represented as per the combination assigned at the subset workbench, including the order of the assignments.

Summaries

Page 7 of 10

Similarly, in the screen shot below, the Customer Summary has been selected from the summary options. As in the previous example, the data below represents the combination of the Characteristics and Key Figure assignments made in the subset workbench.

In the same way, the screen show below displays the data related to the Total Summary selection. Here the Key Figure assignments are listed along with a slider.

Summaries

Page 8 of 10

Summary Functions at Planning:

On the navigating planning grid, the user can apply summary functions for the matrix data. The summary functions, those marked as Function Load, are applied during the loading of the summary data. The functions marked as Function Demand will be displayed in the Tool Tip. The default will provide the Distribute with Difference function, when no user defined function has been marked as Function Check on the Assignment tab. However, no functions will be provided for any Total Type Summaries. These cases can be seen in the screen show below.

Similarly, in the screen shot below, the Customer Summary has been selected and the functions associated with it are displayed.

Summaries

Page 9 of 10

Waterfall Representation for Summaries:

As per the definition for the waterfall elements at the Subset workbench, the summaries data will be represented in the waterfall views. The waterfall views can only be planned for the Table type summary, not for the Total summaries. In addition, the waterfall view is represented only when the user selects a single entry or record from the list of summary records. In the screen shot below, the Waterfall views is represented for a single record from the summary grid, along with its cascade elements view for the Overall view.

Summaries

Page 10 of 10

In addition, the screen show below represents the waterfall view for the multiple records selections from the summary grid for the Overall view.

Schedules Item Filter

Page 1 of 1

Item Filter Item Filter is the configuration setting available during claim creation under schedules functionality of Vistex Agreements. This is the new functionality introduced from E SP3 with the predefined values as “All Items” and “X – Match Schedule ID”. Configuration Menu Path: IP Implementation Guide Incentives and Paybacks Module Basic Functions Pricing Sales Pricing Agreements Maintain IP Agreement Types – Sales.

Along with the above configuration the condition table for the condition type should have the Schedule ID field IRM_SCHID configured. Screenshot below of table A913 have the field Schedule ID. Schedule ID field is a numeric field with length 3 characters. This field is a free field and can be used as per the business requirement. For Ex: An agreement rule (Condition type ZHCR) has 10 materials out of which 5 materials have schedule ID as 1, if the configuration is made with the item filter as X – Match Schedule ID, during claim creation system will consider only 5 materials with Schedule ID and rest 5 materials are ignored.


Page 1 of 4

Special handling at item grid level The Purpose of the Set Codes button:

• line items can be selected to set/reset the IMV codes using Set Codes

button. When ‘Set Codes’ button is selected, a pop up will appear to

maintain IMV codes.


Page 2 of 4

• System successfully set the IMV codes for the selected items.


Page 3 of 4

The purpose of Codes Filter button:

• Items with selected action code/adjustment code/rejection reason code can

be filtered out using Codes Filter button. When Codes Filter button is

selected, a pop up will appear to mention the codes.

• System will successfully retrieve all the line item with the selected codes


Page 4 of 4

• Filter can be delted by selecting ‘Delete Filter’ option in Codes Filter button.

• Delete Filter successfully deleted the above filter

Trade Calendar

Page 1 of 7

The Trade Calendar functionality allows users to view and compare all the Agreements and Agreement requests at once in a web view. In addition, a drag and drop functionality is available, through which the validity of the agreement can be changed on the fly. Different layouts, along with the filter formulas, can be created in the object maintenance workbench for more ease of use and better understanding. These layouts can be configured horizontally or vertically with Hierarchy levels and the fields in the layout can be configured to be editable.

The following transactions can be used setting up the Trade calendar:

/IRM/GTCM- Trade Calendar Maintenance Workbench.

/IRM/GTCOBM- Trade Calendar Object Maintenance Workbench.

/IRM/GTCM_WS- Trade Calendar in BCA.

To create a trade calendar, the following steps must be followed:

• The calendar used to view the Trade calendar BCA search is maintained in the transaction

/IRM/GTCM.

The Calender name and View ID are defined in this worbench to be selected and used in the

trade calender BCA as shown below.

Trade Calendar

Page 2 of 7

• The Objects used in the maintainance workbench can be configured in the transaction

/IRM/GTCOBM.

• The formula button navigates to a business script window where the formula is created. Here

the script formula will remain deactivated until the user activates it.

Trade Calendar

Page 3 of 7

• The fields tab contains the fields to be displayed and used in formula.

• In the steps tab, the formula script can be written.

• After the step is created, it can be activated by returning to the step tab and clicking on the

Activate button. Only then, will the script step be activated and displayed at the side of the tab.

Trade Calendar

Page 4 of 7

• In the messages tab, the Local and Global messages are created.

• In the review tab, the entire formula script written created can be reviewed

Trade Calendar

Page 5 of 7

• After completing all of the above steps, the formula is activated by clicking on

activate/deactivate button on the tool bar.

Below are configuration examples of different types of layout models with the corresponding calendar

display.

• Layout-1 – Horizontal

Trade Calendar

Page 6 of 7

• Layout-2: Vertical

• Hierarchy level

Trade Calendar

Page 7 of 7

Agreement and Direct Agreement File Template with Dimensions

Page 1 of 1


Details

In order to upload and download sets data into a file, two new sections have been introduced in the file template, Dimension Set Header and Dimension Set Item. Each of these new sections need to have the below mandatory fields mapped, at a minimum, to upload/download successfully. Section Field Name Field Description Mandatory or Optional? DH Dimension Set Header KNUMA_AG Sales deal Mandatory DH Dimension Set Header SETID Set Mandatory DH Dimension Set Header DESCR Description Optional DH Dimension Set Header SETTY Dimension set type Optional DH Dimension Set Header DMPFL Dimension Profile Optional DI Dimension Set Item KNUMA_AG Sales deal Mandatory DI Dimension Set Item SETID Set Mandatory DI Dimension Set Item SETNO Include/Exclude Set Optional DI Dimension Set Item EXCLS Exclusion Optional DI Dimension Set Item DIMEN1 Dimension Determined Optional DI Dimension Set Item DIMEN2 Dimension Determined Optional DI Dimension Set Item DIMEN3 Dimension Determined Optional DI Dimension Set Item DIMEN4 Dimension Determined Optional

Transactions /IRM/IPAGFTM – Agreement File Template /IRM/IPxxASP – Agreement Workbench /IRM/IPxxAGUPL – Upload Agreement /IRM/IPxxAGDNL – Download Agreement /IRM/IPDAFTM – Direct Agreement File Template /IRM/IPSDAM – Direct Agreement Workbench /IRM/IPSDAUPL – Upload Direct Agreement /IRM/IPSDADNL – Download Direct Agreement /IRM/IPPDAM – Direct Agreement Workbench /IRM/IPPDAUPL – Upload Direct Agreement /IRM/IPPDADNL – Download Direct Agreement

Schedules in Master Request New functionality has been introduced as “Master Request Schedules “within the Master Request workbench. The purpose of this new functionality is to provide flexibility to business for time frame of Master Request and automatically allocates and distributes corresponding amount based on schedule validity. The total allocated amount under the Schedules tab will be maintained as schedule dates period payments. Users will be able to maintain schedules with different schedule types in a master request and will also be able to allocate amounts by payment period dates using Master Request parameters. The created schedules on a master request document can be copied to the agreement, agreement request or master request by marking flag for “Copy Schedules” check in the Postings popup screen. In order to maintain a schedule, schedule types with a schedule category must be assigned to the master request type. Schedule Type: Schedule type should be assigned to the master request type. In schedules, the allocation of the amount gets derived through the schedule categories (specific date, periodic and milestone).

1. Specific Date: Allocate the amount as per specific dates. Period profile and proposed tabs will be greyed out when the user selects the specific date as schedule type.

2. Periodic: Master request pays the allocated amount, equally distributed within the periods. If the schedule type was chosen as periodic, then the period profile and propose button will both be activated. For period profile, the user can choose the pre-defined periods and for the propose button, the user can maintain the desired dates.

3. Milestone: Allocate the amount by using milestone type, but not by specific dates. Milestone type should be maintained in configuration and should be assigned under Schedule type. When the user selects the milestone schedule type, the period profile and proposed button will be greyed out. For schedule dates, the amount under the milestone schedule type should always be less than the header total amount of the milestone schedule type and the milestone dates are optional for user. However, if desired, the user can assign dates for milestone. The user can also allocate the header total amount value type either as ‘amount ‘or ‘percent’.

Schedule Value Type: This value type specifies the amount field as amount or percent. Page 1 of 2

Schedules in Master Request Schedule Usage: Only one schedule at a time will be defaulted in the Master Request. Users can only select one default check within all of the schedule types and make that default selection defaulted in the Master Request. This schedule usage helps in the composite application, when a user needs to call the selected schedule type into the composite applications. Schedule Type Dates: The scheduled dates will be adjusted as per the changes in the header schedule type start and end dates. At the schedule date level, the user can set the value through the set value button in order to set the amount. Period Profile and Period Proposal Button: For period profile, the user can select the available standard period profiles for amount allocation. The total amount is equally distributed among the periods. Once the user selects the available period profile, all of the periods will be defaulted under dates for schedule. Under the propose button, the user can define the period profile as a Master Request level or as a Predefined level. The user can use the period propose button in order to maintain the proposal dates under the Master Request level period. The user can choose the period profile and period proposal button for periods instead of entering the periods manually. The purpose of the period profile and proposal tabs is to propose the dates automatically. Configuration:

- /IRM/IPSPRO Basic Function Pricing Sales Pricing Agreements Define Schedule Type Define Milestone Type Define Schedule Usage Setup Agreements Master Request Define Master Requests Schedule Types

Page 2 of 2

Dimension Cross Reference - Upload/Download

Page 1 of 2

Overview

Upload and download is available to create, change or review a dimension cross reference record.

File Template

In order to upload or download a dimension cross reference record(s), a File Template is required. This can be created through transaction /IRM/GDMXRFFTM.

On the Section tab, there is only one section available, Dimension Cross Reference. In this tab, a user can specify the position of the section in Excel sheet by specifying the section indicator(s) or the start row value(s). However, both the section indicator and start row should not be entered. If the user specifies the section indicator(s) here, then each row in Excel should start with the corresponding section indicator. The start row and end row position are used only for single document upload. For mass upload, section indicators should be specified.

On the Mapping tab, the section needs to have the below fields, at a minimum, to upload/download successfully: • NRART – Partner Type • KTONR – Partner • DIMID – Dimension Entered • DMCAT – Dimension Category • DIMEN – Dimension

The Field Mask column in the Mapping tab is enabled for fields that may require value conversion. To avoid conversion errors, the field mask can be used as per the screenshot below. In this example, the system date format is MM/DD/YYYY, but during upload/download the user wants the date format in DD/MM/YYYY, so DD/MM/YYYY is specified as the Field Mask for the date fields.

Dimension Cross Reference - Upload/Download

Page 2 of 2

Mapping Tab Example

Upload

The upload functionality is available from /IRM/GDMXREFUPL.

• From this transaction: o Users can upload a file to create single or multiple dimension cross reference record(s).

To upload multiple records can be uploaded at a time. In the file template, the section indicator should be mentioned in the first colum to indicate to which section the data corresponds.

o Users can upload a file to change existing dimension cross reference record(s), provided the upload file contains the required file template field(s).

• This transaction is split into three sections: File Source, File Info and Dimension Cross Reference Fields. o In the File Source section, the File Location field defaults to the Desktop Source.

Download

The download functionality is available from /IRM/GDMXREFDNL.

• From this transaction: o Users can download dimension cross reference record(s) using the download transaction

workbench. o File template is mandatory to download; users can use a file template to tell the system the field

mappings in the spreadsheet. • This transaction is split into three sections: General Data, Admin Data and Download.

Default Distribution Functions

Page 1 of 15

Instead of Distributing matrix data to the hidden levels equally, now the user has the control over distributing to the hidden levels based on the type of function implemented in matrix data. A newly generated Matrix will be populated with eight Predefined functions out of which five are Distribution Function types and the other three are Distribution with Reference Function Types. Each of the eight pre-defined functions is categorized under the Pre-Delivered Implementation type, as shown in the screen shot below.

In order to implement these functions on Matrix data, the user must assign them to the Subset Usage level, along with a function event type, Function Check or Function Demand. If the Matrix Data is comprised with the Any Value characteristic, a characteristic using the number sign or hash symbol (#), then the distribution of data depends on the type of Function Implemented along with its Function Event type.

Distribute with Overwrite (DIST_OVR) :

This is a new type of Pre-Defined function introduced in Release SP3 with the Function Type Distribution and the Implementation Type Pre-Delivered. The Distribute with Overwrite function will distribute the data equally to all child levels associated with the Layout. In order to use this function, the user must select the Function Check or Function Demand events in the Assignment Tab of the Subset Usage. In the below screen shot, the assignment of the Distribute with Overwrite function is displayed using the Function Check event.


Page 2 of 15

The following examples will better illustrate the Distribute with Overwrite function type. For example, in the planning workbench, the corresponding Matrix, Subset, and Usage combination associated with the Dist_Ovr function type has been executed. As the screen shot shows, the characteristic Amazing Sales Division contains a value of $500 USD, which is divided among three Materials Any Value, $200, test, $100, and Laptop SSHD-ST1000LM015, $200.

Next the Material Characteristic Field is removed from the Layout and the Amazing Sales Division value is changed from 500 to 1000.


Page 3 of 15

As shown in the screen shot below, once the Material field is added back to the matrix characteristics the new value is distributed equally to all three materials.

Distribute with Difference (DIST_DIFF) :

This is a new type of Pre-Defined function introduced in this release with a Function Type of Distribution and an Implementation Type Pre-Delivered. The Distribute with Difference


Page 4 of 15

function will distribute the Difference Data Equally to each of the child levels associated with the Layout. In order to use this function, the user must select the Function Check or Function Demand event in the Assignment Tab of the Subset Usage. In the below screen shot, the assignment of Distribute with Difference is displayed with the Function Check event function.

The following examples will better illustrate the Distribute with Difference function type. For example, in the planning workbench, the corresponding Matrix, Subset, and Usage combination associated with the Dist_DIFF function type has been executed. As the screen shot shows, the characteristic Amazing Sales Division contains a value of $500 USD, which is divided among the three materials of Any Value, $200, test, $100, and Laptop SSHD-ST1000LM015, $200.


Page 5 of 15

Then the Material Characteristic Field is removed from the Layout, the Amazing Sales Division value has been changed from 500 to 600, and the entries saved, as shown in the screen shot below.

As shown below, once the Material field was added back to the characteristic, the difference of $100 ($600-$500=$100) is equally distributed among the three materials. Therefore, $33.33 has been added to each of the previous values.


Page 6 of 15

Distribute with Overwrite Using Reference (DIST_OVRK) :

This is a new type of Pre-Defined function introduced in Release E SP3 with the Function Type of Distribution with Reference and the Implementation Type Pre-Delivered. The Distribute with Overwrite Using Reference function has the ability of overwriting the data based on the Reference Key Figure provided. The key figure may be of the Same Key Figure (Self Key Figure) or Other Key Figure. When using Distribute with Overwrite Using Reference, the system distributes the Data with respect to the Reference Key Figure percentage contributions associated with function assignment. In the below screen shot, the Distribute with Overwrite Using Reference has been assigned with the Adjusted Amount as the Reference Key Figure.


Page 7 of 15

The following examples will better illustrate the Distribute with Overwrite Using Reference function type. For example, in the planning workbench, the corresponding Matrix, Subset, and Usage combination associated with the Dist_OVRK function type has been executed. As the screen shot shows, the characteristic Amazing Sales Division contains an Accepted Amount value of $500 USD, which is divided among three Materials Any Value, $200, test, $100, and Laptop SSHD-ST1000LM015, $200. Similarly, the Adjusted Amount Key Figure value is $100 for the Amazing Sales Division, which is divided among the three materials in the amounts of $15, $80, and $5, respectively.


Page 8 of 15

In the next screen shot, the Material Characteristic Field is removed from the Layout and the Amazing Sales Division value is changed from 500 to 1000.

As shown below, once the Material field was added back to the characteristic, the $1000 has been distributed according to the material’s percentage of the key figure, the Adjusted Amount. For example, the material Any Value was allocated $150, since it accounts to 15% of total Adjusted Amount. Since the material Test accounts for 80% of the Adjusted Amount, this


Page 9 of 15

material was allocated $800 from the new Accepted Amount. Finally, the material Laptop-SSHD was allocated only 5%, $50 of the new value.

Distribute with Difference Using Reference Key Figure:

This is a new type of Pre-Defined function introduced in the current release with a Function Type of Distribution with Reference and an Implementation Type of Pre-Delivered. The Distribute with Overwrite Using Reference function has the ability of overwriting the data based on the Reference Key Figure provided. The key figure may be of the Same Key Figure (Self Key Figure) or Other Key Figure. When Using Distribute with Overwrite Using Reference function, the system distributes the difference Data with respect to the Reference Key Figure percentage contributions associated with function assignment. In the below screen shot the Distribute with Difference Using Reference function has been assigned with the Same Key Figure as the Reference Key Figure.


Page 10 of 15

The following examples will better illustrate the Distribute with Overwrite Using Reference function type. For example, in the planning workbench, the corresponding Matrix, Subset, and Usage combination associated with the Dist_DIFFK function type has been executed. As the screen shot shows, the characteristic Amazing Sales Division contains an Accepted Amount value of $500 USD, which is divided among the three materials of Any Value, $200, test, $100, and Laptop SSHD-ST1000LM015, $200.


Page 11 of 15


As shown below, once the Material field was added back to the characteristic, the difference of $500 ($1000-$500=$500) has been distributed according to the material’s percentage of the key figure, the Accepted Amount. For example, the material Any Value was changed to $400. Since this material accounts for 40% of total Accepted Amount, then the system added an additional $200 (200/500=40%, $500 x 40% = $200). Each of the amounts for the materials was adjusted similarly. The material Test accounts for 20%, and therefore was allocated an additional $100. Finally, the material Laptop-SSHD was allocated 40%, $200 to its existing value.


Page 12 of 15

Distribute to Any (DIST_2_Any):

This is a new type of Pre-Defined function introduced in Release SP3 with the Function Type as Distribution with Reference and the Implementation Type as Pre-Delivered. When using Distribute to Any function, the system distributes the difference value with respect to the Reference Key Figure percentage contributions associated with function assignment. In order to use this function, the user needs to check the Function Check or Function Demand event in the Assignment Tab of the Subset Usage. In the below screen shot, the assignment of the Distribute with Any function is displayed using the Function Check event.


Page 13 of 15

The following examples will better illustrate the Distribute Any function type. For example, in the planning workbench, the corresponding Matrix, Subset, and Usage combination associated with the Dist_Any function type has been executed. As the screen shot displays, the characteristic Amazing Sales Division contains an Accepted Amount value of $500 USD, which is divided among the three materials of Any Value, $200, test, $100, and Laptop SSHD-ST1000LM015, $200.


Page 14 of 15


As shown below, an additional $500 has been distributed only to the Any Value Entry, which represents the difference between the original value of $500 and the new $1000 entry. Since the Distribute to Any function has been used, the additional amount has been added to the Any Value characteristic, raising the allocated amount to $700.


Page 15 of 15

Conversion Reports

Page 1 of 7

Matrix conversion reports for Release E SP3: Below is the list of conversion reports that needs to be run for existing matrix. Conversion Report Name What activity it performs Effective on what data

/IRM/IPMX_ESP3_ASSIGN_CONV Functions and Layouts Assignments from Subset to Usage Conversion

Moves configuration data

/IRM/IPMX_ESP3_CNTR_FILL Matrix Counter Fill Updates transactional data

/IRM/IPMX_ESP3_DERV_CONV Matrix Derivations Source Mapping Conversion


/IRM/IPMX_ESP3_EXPL_CONV Explosions Characteristic Mapping Conversion


/IRM/IPMX_ESP3_FNTYPES_REVAMP Restructuring Matrix Functions


/IRM/IPMX_ESP3_GEN_CMNT_TABLES Generating Matrix Comments Tables

Creates new tables based on generated matrix tables

/IRM/IPMXP_ESP3_KFCOND_CONV Proforma Profile Key Figure Conditions Conversion


1. Conversion Report: /IRM/IPMX_ESP3_ASSIGN_CONV Please check the below screenshots before and after running the conversion report. Notice in the below screenshot, there are no layouts or functions assigned. This matrix was generated in Release E SP2.

Conversion Reports

Page 2 of 7

Now go to SE38 and input program /IRM/IPMX_ESP3_ASSIGN_CONV; see the below screenshot.

Clicking Execute in the above screen takes the user to the below screen where it needs the input of matrix and subset information.

Conversion Reports

Page 3 of 7

After executing the above information, it assigns back the layouts and functions to the matrix as shown in below screenshot.

2. Conversion Report: /IRM/IPMX_ESP3_DERV_CONV

In Release E SP2 for the Matrix workbench, at the derivation source mapping, the fields used to be in the order of 'matrix characteristic' first and then 'source' field. Now in Release E SP3, these two fields are swapped by running the conversion report in SE38. So the expected order is, 'source' field and then 'field name' which is the 'matrix characteristic'.

Conversion Reports

Page 4 of 7

Before running the conversion report:

After running the conversion report:

3. Conversion Report: /IRM/IPMX_ESP3_EXPL_CONV In Release E SP2 for the Matrix workbench, at the derivation source mapping, the fields used to be in the order of 'matrix characteristic' first and then 'source' field. Now in Release E SP3, these two fields are swapped by running the conversion report in SE38. So

Conversion Reports

Page 5 of 7

the expected order is, 'source' field and then 'field name' which is the 'matrix characteristic'. But this happening is in Subset workbench (/IRM/IPMXSM) where the Explosions are defined. Below is the screenshot after running the conversion report.

4. Conversion Report: /IRM/IPMX_ESP3_KFCOND_CONV In Release E SP2, the fields used to be in the order of 'Matrix characteristic' first and then source field in the proforma profile in the keyfigure conditions at keyfigure mapping. By running this conversion report, these two fields are swapped in ESP3. So the expected order is, 'source field which is Field name and Matrix Characheristic. Configuration: /IRM/IPSPRO > Basic functions > Matrix > Proforma >Define Proforma Profile Before running the conversion report:

Conversion Reports

Page 6 of 7


5. Conversion Report: /IRM/IPMX_ESP3_FNTYPES_REVAMP This restructures the Matrix Functions for existing an matrix that were generated in previous releases. Before running the conversion report:

Conversion Reports

Page 7 of 7


6. Conversion Report /IRM/IPMX_ESP3_GEN_CMNT_TABLES In Release E SP3, four new tables are getting created while generating the matrix. As shown in the below screenshot, IPMXxxxC, IPMXxxxCA, IPMXxxxCT, and IPMXxxxH are the new tables. C, CA and CT are comment tables and H is for hierarchy data. So for existing matrixes up until Release E SP2, the user needs to run this conversion report to generate these new tables for them.

Table of Contents Introduction ................................................................................................................................ 2

Variable Definition .................................................................................................................. 2

Editor Mode ............................................................................................................................ 3

Expert Mode........................................................................................................................ 3

Normal Mode ...................................................................................................................... 3

Comments ............................................................................................................................... 6

Field creation from function maintenance pop-up ................................................................... 7

Titled Function Variables ......................................................................................................... 7

SORT table function ................................................................................................................. 8

Messaging ............................................................................................................................... 8

Changes ......................................................................................... Error! Bookmark not defined.

Reorganized Business Script Functions .................................................................................. 10

DO MATH FUNCTION ............................................................................................................. 11

DELETION ICON ..................................................................................................................... 11

DECISION TABLE MAINTENANCE............................................................................................ 12

Removals ....................................................................................... Error! Bookmark not defined.

Fixes ........................................................................................... Error! Bookmark not defined.

Business Script Editor

Page 2 of 12

Introduction Previously, the Business Script functionality was introduced as a way to allow users to create function modules without accessing or requiring knowledge of the coding. New enhancements have been incorporated as part of Release E Service Pack 3 to further aid in the creation of business scripts. These enhancements include: creating parameters that refer to the format of a previously created parameter, copying parameters, inserting functions into the middle of steps, changing functions, deleting functions and a new global message system. In addition, other aesthetic changes have been made to simplify the user experience.

Variable Definition A new option, Like, has been introduced as part of the Refer options when creating a parameter. This option is similar to the field option, except the field being referred to must be of the same type. Also, instead of referring specifically to the existing parameter, the new parameter will only inherit the technical properties of the existing parameter.

For example, when creating a new variable, VAR2, using the Like option to refer to VAR1, the new variable will be created with the same Data Type, Length, and Decimal values as the original parameter.


Page 3 of 12

Please note, the parameter that is being referred to must be an incoming or outgoing parameter in the script and should not refer to an ABAP dictionary object.

Editor Mode In this release, the business script editor provides two editing modes, Expert Mode and Normal Mode. It is possible to toggle between the two modes by clicking on toggle buttons provided in the editor workbench.

Expert Mode In this mode, the script steps are shown as ABAP like statements. In Expert Mode, the system will allow the user to directly edit the script or add more logic. This will help speed up the script maintenance, but the user is completely responsible for the syntax of the script.

Normal Mode Introduced as part of Release 60 E SP3, the normal mode will render the script in an HTML screen. In this mode, users will not be able to directly edit the script text. Rather, a user would


Page 4 of 12

make use of the various predefined options offered in the business script editor workbench by clicking the respective function buttons or choosing an option from a list.

Script Modification Using NORMAL Mode Though the script cannot be edited as freely in NORMAL mode as compared to EXPERT mode, script can be modified using the following options.

Add This button will allow the addition of a function to the very beginning of the script.

Upon clicking the add function button, a drop down field will be provided from which the user can choose a business script function to add.


Page 5 of 12

Change The change button allows users to change an existing function. Upon clicking the change function button, the function will be loaded into function maintenance pop-up wherein the function can be changed.

Delete Clicking the delete function button will cause the function will be deleted from the script.

Insert


Page 6 of 12

Also available are the insert buttons. These buttons allow the user to add a new function above or below an existing function.

The functionality of these buttons works similarly to add function, by providing the user a dropdown to select the function to insert.

Comments Comments are lines of text that descript the function. These lines are for the users’ understanding only and are ignored by the system when executing the script. A comment can

be added by the user to any function by clicking the comment button . Once the user has clicked the button, a new section will be displayed in the function maintenance pop up window. Here the user will provide the desired text.

Once the comments are entered and the user clicks continue, the comment will appear above the corresponding function, as shown in the screen shot below.


Page 7 of 12

To remove a comment, the user will have to edit the function and remove all the text from the comment section.

Field Creation from Function Maintenance Pop Up In this release, new fields can be created from within the function maintenance pop up. The created field will be immediately available for use.

Titled Function Variables In this release, function operands, operators, parameters, fields, etc. are all titled to make them more understandable to users.


Page 8 of 12

Sort Table The Sort function has been introduced to enable sorting of table records. When defining a Sort operation, the user can specify the fields, Sort Key, by which the sorting will take place and the order, ascending or descending, in which the records have to be sorted. As shown in the example below, table ITAB_KNA1 is being sorted in the ascending order by KUNNR, the customer number field, and then in the descending order by KUKLA, the customer classification field.

Messaging As part of this release, changes to the messaging functionality have been made. The message tab will still allow the creation of script specific messages, no called local messages. However, the message tab will no longer call system messages. Instead, a new Global Message Workbench, transaction /VTA/BMSM, has been created specifically for the business script


Page 9 of 12

functionality. Within this workbench, users will be able to create custom global messages. These messages will contain their own numbering, separate from the system messages.

Users can create a global message from the script workbench by clicking the create button in the message tab.

This directs the user to the global message table from the transaction /VTA/BMSM. Once a global message has been created, it can be added to the script by providing the corresponding number from the global message table and clicking the continue button.

This will add the message to the script with a corresponding message number.


Page 10 of 12

After messages have been added to the message tab, they can be called during the script execution using the Give Message function.

Please note, any business scripts using the old System and Script Message options, the conversion program /VTA/BSE_60E_SP2_SP3_CONV will need to be executed to convert the old messages to the new system. Once that conversion program is executed, the conversion program /VTA/BSE_60E_SP2_SP3_ACTIVATE will need to be executed as well to reactivate all of the existing business scripts. If not, the script will not execute, due to “Error in script definition.”

Reorganized Business Script Functions As part of this release, the business script functions have been reorganized and the categories have been renamed into function categories that better reflect the type of operations the functions provide. The new categories are Conditional, Table, Aggregate, Fetch, Formula, Other, Date, String, and Mathematical.

For example, conditional statements, such as “IF….ENDIF” and “DO…ENDDO,” are grouped under the Conditional function category in 60E SP3 whereas these statements were shown under the path Operations-Fields in Release E SP2.


Page 11 of 12

60 E SP3 60 E SP2

DO MATH FUNCTION In addition to changing the grouping of the operations, the Arithmetic operations, add, subtract, multiply, etc., have been replaced by a new function called Do Math. This can be found under function group Formula.

DELETION ICON In prior releases, when removing a function operation line, the user would use the trashcan

icon. However, as of this release, the icon has been replaced with a minus icon.


Page 12 of 12

DECISION TABLE MAINTENANCE In this release, decision table definition/maintenance will be done on an HTML background instead of GUI maintenance. As shown below, the user enters the fields that have to be compared in the Settings tab.

Then, the user will specify the instances and corresponding values in the Content tab.

Data Objects - Enhancements

Page 1 of 23

Contents Introduction ............................................................................................................................................ 2

Data Objects Setup .............................................................................................................................. 2

Custom Object and Search Transaction Codes ..................................................................................... 2

Domain Assignment ............................................................................................................................. 3

Field Type ............................................................................................................................................ 5

Fields Create Field with Reference ....................................................................................................... 6

Global Field ......................................................................................................................................... 7

Status Flow .......................................................................................................................................... 8

Duplication Coverage........................................................................................................................... 9

Mass Change ..................................................................................................................................... 11

Auto Validation Runs ......................................................................................................................... 12

Subsequent Validation Run ................................................................................................................ 13

Multiple Validation Run ..................................................................................................................... 14

Locking .............................................................................................................................................. 15

Cross Reference Mapping .................................................................................................................. 15

Data Profiling - Grouping ................................................................................................................... 16

Reprocess Multiple Object Versions ................................................................................................... 17

Create Subsequent Version................................................................................................................ 18

Index Updating .................................................................................................................................. 19

Download Objects ............................................................................................................................. 20

Data Model from IDOC ...................................................................................................................... 21

Partial Postings .................................................................................................................................. 23


Page 2 of 23

Introduction Though introduced in Release E SP1, many changes have been made to the Data Objects functionality in Release E SP3. These changes will affect different aspects of the functionality and provide the user with new functionality. Included in these new features are custom transaction codes for each data model, allowance of partial postings of validation runs, and new mass change functionality, as well as others. These changes are intended to improve upon the functionality introduced in the past releases.

Data Objects Setup One of the new changes to the data objects functionality is the new IMG transaction for Data Objects Setup, /VTA/DOSETUP. Here a user can configure aspects of the Data Object types. In this IMG transaction the user can maintain number ranges for objects and validation runs, custom transaction codes, validation, correction or correction codes, and other aspects needed in the use of the Data Objects functionality.

Custom Object and Search Transaction Codes New to Release E SP3, the data objects functionality requires the creation of separate custom transaction codes for both the Data Object workbench and the Search and Process functionalities for each data model.


Page 3 of 23

These new custom transaction codes will replace the transactions /VTA/BDOM and /VTA/BDO10 and will be created in the “/VGM/” namespace. To create a new transaction code, the user must enter a value into the Object Transaction Code and Search and Process Transaction Codes fields. The value entered into each field must be different. Upon saving and transporting the entries, the system will automatically add the transaction code using “/VGM/” as the prefix to the entry. The new transaction codes are required for all new implementations and upgrades to 6.0 E SP3.

Domain Assignment

As part of Release E SP3, domains have been introduced to classify fields, rules, rules profiles, and data models. For any field, rule, or rule profile to be available for use in a data model the same domain assigned to the data model must be assigned, which is now a required field. To create a domain, the user must execute the Define Domain node in the transaction /VTA/DOSETUP.


Page 4 of 23

In the table within the node, the user must enter a domain and description.

Once the domain information has been saved and transported, the domain will be available in a drop down menu. The user must select the appropriate domain for the object because the only objects assigned to the domain will be available for selection. In addition, once a domain is selected, it cannot be changed.

Please note, any fields or domains created prior to Release E SP3, a selection in the domain field must be made to continue using the object.


Page 5 of 23

Field Type

A new option when creating fields is the field type. A field type defines the datatype and length of characters of a field or the number of decimal places for a numeric datatype. In addition, Upper case and Lower case can be distinguished for the values entered on the screen.

Finally, in the Fixed Values tab of the field type, the user can assign fixed values, specifying single values to be used in any field with the field type assigned. Description of fixed values can be maintained in different languages which will be displayed in the input help.

The type is assigned to a field and can be assigned to multiple fields. For example, Sold-to-party and Customer fields can have same field type. Here, the type is assigned to a field during the creation of the field. In the Field Type tab, the user must select “No” as the option for the Specified Field Type.


Page 6 of 23

Then the user will click the Select Existing Field Type button to select from the activated field types.

Once selected, the field properties will be entered, matching those of the field type.

Fields Create Field with Reference

One new option when creating fields is the Create with Reference option .


Page 7 of 23

Here the user will be able to enter a new field name, domain, and the reference field. The new field will contain the same field properties and labels as the field used in the reference field.

Global Field

As stated before, when creating a field, a domain must be assigned for the field to be activated. However, the only exception is when creating a global field. In the field creation popup window, the user has an option to create a global field.

When this field is checked, the domain is no longer available for selection. The rest of the field creation is the same as the creation of other fields.


Page 8 of 23

Once the global field is saved and activated, it will be available for use in all data models, regardless of the domain assigned.

Status Flow During the creation of a data model, a status profile can be assigned to each version. Different status profiles can be assigned to different versions.

Once a status profile is assigned to a version, the corresponding status flow steps will be assigned to any new object created. To access the object status flow, the user will have to select a version and click the

Version Status button. This will display a new popup window containing the status information for the current version.


Page 9 of 23

From here, the user can review the status information, set the status for the current step, and change the trigger for the active status.

Duplication Coverage When creating a data model in transaction /VTA/BDOCM, the users can now review a list of data that has been duplicated within a certain period of time. This is done within the duplication tab of the data model. Here the user will have to create a field group for a specific section of a version within the data model.


Page 10 of 23

When defining the Field Group, the user will be able to assign a validation code for each group. This validation code will be displayed in the error code field in each object instance, as well as the dashboard. This will provide the user with an indication of which lines are duplicated.

Once the Field Group is defined, the user must select the area in which duplicates may occur, by clicking

the Coverage button . A new window will be displayed on the right hand side where the user can create a coverage using two data area, Object Header and Version.

After selecting the data area and a field, the user has the option to set the selection type. The options for the user are Dynamic Date Calculations and Fixed Values.

The Dynamic Date Calculation option is used only for Date fields and can be yearly, monthly, weekly, or daily. In addition, the Dynamic Date Calculation can search a set number of past and/or future periods. However, if no number of periods is provided, the system will only consider the current data object.


Page 11 of 23

The fixed value will allow the user to select specific values for the system to search for duplicate records.

Mass Change As previously mentioned, users can create a custom search transaction. This search transaction provides users with a dashboard with mass change functionality, wherein the users can search across data objects based on the selection criteria defined in the Process Area. The users can change the Object data that are pulled up and save the changes either as a validation run or directly into the object. Please note, only the sections that are marked as search relevant in data model configuration will be available in Mass Change transaction.

The dashboard provides the reprocess functionality, which will check the rules associated with the data model. The rules can also be triggered when saving the changes within the dashboard.


Page 12 of 23

Additionally, the match and duplication buttons are provided to carry out the corresponding functionalities. Validation Code and Correction Code fields are always in display mode.

Auto Validation Runs An Auto Validation run can be used to create validation runs based on determined search criteria. In the transaction /VTA/BDOAVM, the user will be able to enter an Auto Validation Run name and select a Process Area. It is the Process Area that will determine which fields are available as part of the search criteria. Users can also select data conditionally based on a qualifier and can modify the data before creating a validation run by using corrections. Once an Auto Validation run is executed, any available data objects meeting the criteria will be added to a validation run.

In addition the user can set qualifiers for the Auto Validation run. Qualifiers are the criteria which consist of fields with values on which corrections will be carried out. Qualifiers are not mandatory to create an Auto Validation Run.


Page 13 of 23

The last tab in the Auto Validation Run is the Corrections tab. Here the user can assign fields and the changes needed to be made to the data from the Qualifier tab. If a Qualifier is added to the Corrections tab, the corresponding correction will only be executed if the qualifying criteria are met. A script can be created to execute the correction steps or fixed values can be added to the right hand side in the Corrections for step section.

Subsequent Validation Run

Based on the selections made, the system can create a Subsequent Validation Run containing objects still in progress on a current Validation Run. When working with Validation Runs in the transaction /VTA/BDOVRM, users will be able to classify objects as Ready for Release, Rejected, or In Process. This is

done by selecting the corresponding lines and clicking on the Set Release Status button .

If an object is marked as Ready for Release, the system will release the object from the validation run. An object marked as Rejected will be removed from the validation run. However, if the user marks an


Page 14 of 23

object as In Process, the system will remove the object from the current validation run, in order to release those objects ready for release, and create a new subsequent validation run containing the in process objects.

From here, the system will release the objects, remove, or, in the case of the In Process option, create a new validation run containing only those objects with the corresponding setting when selectin the Save and release button.

Multiple Validation Run In Release E SP3 users can now release validation runs using a single execution. In the transaction /VTA/BDOVRP, users can release a single validation run or select several validation runs and release them all at the same time. Releasing these validation runs can be done in the foreground or as part of a background job.


Page 15 of 23

Locking

When data has been added to an open validation run, the system now has the ability to lock the corresponding objects preventing any changes from being made. The Locking functionality s set at the section level of a data model version in the transaction /VTA/BDOCM.

This functionality will prevent any data object from being changed when the object is included in a validation run.

Please note that the locking option is valid for the section in which the Lock flag is selected, unless there a parent section has been established. In this case, if the Lock flag was selected at the parent level, then both the parent and child levels will be locked if the object is included on a validation run. However, if the lock option is selected at the child level, then only the child section will be locked and any manipulation to the data will not be allowed. In this case, though the object may be included on a validation run, the parent section will allow changes to be made, but the child section will not.

Cross Reference Mapping As part of the data model configuration workbench in transaction /VTA/BDOCM, users can create new cross references. Theses cross references has to be mapped within model. These cross references can then be accessed when creating subsequent versions, reprocessing objects, or during posting. Each cross reference rule will be assigned to a section and a version within the data model. In addition, users will have to maintain the cross reference type, validation code, incoming fields, and outgoing fields as part of the cross reference setup.


Page 16 of 23

Incoming fields are the ones sent to cross reference engine and outgoing fields will be returned back as a part of result from the engine. Fields can come from either current section, parent section or the Object Header. Validation code is set if value is not determined using the cross reference and Multiple determination validation code is set if more than one value is determined for a combination. Exclusion flag is used to stop the process of determination if value is found in any step. We also allow cross reference maintenance from Object Workbench. For this cross reference types should be maintained at the action code in Codes tab.

Data Profiling - Grouping

New to Release E SP3, users have the ability create data profiles with groups in order to display different statistics based on the data from selected data objects. These groups are created within the Object Profile, transaction /VTA/BDOPM, or the Object Profile Run, /VTA/BDOPRM. A group can consists of multiple fields from different sections. Users can assign more than one group to a field, as well as, assigning groups to the various code types. As a result, the profile run will show the field statistics based on the values of the group.

To utilize the grouping functionality, the user has to create the group in the group tab. Here the user will have to provide a Group ID, Description, and Path. Once that has been completed, the user will have to provide the fields associate to with the grouping.


Page 17 of 23

Then in the Fields tab, a Group By button will be available for each field. Clicking on the button will open a new window where the Group ID can be assigned.

In addition to the Fields Tab, the Codes tab provides users with a Group by Button to assign groups to the codes.

When executing the Profile Run, a Group by menu button is provided in the Results section. Here the user can toggle between viewing the using the Overview view or the Grouping View.

Reprocess Multiple Object Versions With the new release, the Data Objects functionality now allows users to carry out operations such as duplication, matching, and rule checks and cross reference for multiple objects within a single


Page 18 of 23

transaction. In this transaction, /VTA/BDOVRPS, user can reprocess more than one object in at a time, provided the objects are from the same data model and same version.

Using this report, the user can carry out four different operations, Duplication, Matching, Check Rules, and Check Cross Reference. The Duplication option will be used to update the duplication records. The Matching option will carry out the matching functions. Selecting the Check Rules operation will have the system trigger the check rules created for the data model. Finally, the Cross Reference Operation will initiate the cross reference type and mapping for the data model. Multiple operations can be selected when executing the Reprocess Object Version Report.

Create Subsequent Version In order to speed up the processing of multiple objects, the transaction /VTA/BDOTVC, Create Target Version, has been created. This transaction will allow users to create subsequent versions from existing version of multiple objects in single execution, rather than going to object instance workbench and individually creating subsequent versions for each object. User can also schedule background jobs for creating target versions using this transaction.


Page 19 of 23

Index Updating In order to maintain the index tables are up to date with the latest changes to the Duplication Field Groups, the transaction /VTA/BDOIU, Index Update has been introduced. The purpose of this functionality is to update the index table whenever changes are made to the existing duplication groups. Updating the index tables every time a duplication change is made is necessary in order to maintain current information in the duplication fields. The user can update index by using multiple selections, as determined by the assigned Process Area. In addition, users can create variants and schedule the update as a background job.


Page 20 of 23

Download Objects As part of Release E SP3, the Data Object functionality now allows offline maintenance of data objects. To accomplish this, the user must enter the transaction /VTA/BDODNL to download objects into a file. Multiple objects can be downloaded into the same file. An object can be downloaded either to the desktop or to a file server. After making changes to the file, the file can be uploaded back into the system.

Before downloading a data object, the user must create a file template. This is done in the transaction /VTA/BDOFTPM. Here the user must set the template type as “Import & Export” to be able to download and upload the data. Users will also maintain the attributes, e.g. the applicable data model and version, the section, and field mapping for the template.


Page 21 of 23

Once the template has been created, the data objects can be downloaded using the transaction /VTA/BDODNL. In this transaction, the user will specify the data model, version, file template, and file location of the download.

Data Model from IDOC New to Release E SP3 is the ability to automate the creation of a Data Model from an IDOC type. In order to accomplish this, a new transaction has been created, /VTA/BDODMI. In this transaction the user will need to provide a Data Model, Version, Domain, and an IDOC type.

Once the information is provided and the transaction is executed, a new data model is created, activated, and the version is released.


Page 22 of 23

When the data model is created from an IDOC type, segment of the type will be converted into sections. In addition, the new fields are automatically created and linked with the domain name. Each data model will consist of a Control Record Section as a default section. This section will also be listed as a parent section to the first section from the IDOC type. The system will set the IDOC number, Parent Segment Number, and Segment Number as key fields in the newly created data model.


Page 23 of 23

Partial Postings Partial posting can be utilized when the user wants to send only the valid portion of the data object to create subsequent objects. If partial posting flag is not marked, then entire object will be considered for Posting to Subsequent Object. Introduced as part of the Data Objects functionality in Release E SP2, postings can create such objects as claims, transaction register, agreement, agreement request, membership list, customer list, partner list, vendor list, and master request from a data object instance. One data object instance is able to create multiple subsequent documents. For more information on the configuration for Postings, please see the Release E SP2 release notes entitled Data Model Objects.

Added as part of Release E SP3 is the concept of Partial Posting. In the past, users could only post to a subsequent object when all the data has been cleaned. However, using the posting statuses, partial postings can be created. For example, if there are five headers with its respective items in an object instance, but two of those headers have clean data which can be carried forward for creating subsequent objects such as claim, membership, etc. The user can post only those two headers through partial posting to create the subsequent documents. The three remaining headers will be saved and can be processed further before posting.

In order to utilize the partial posting functionality, in the transaction /VTA/BDOCM, the version in the Data Model must have the partial posting option checked.

In addition to the settings in the data model, the user needs to create a sub list. Once a sub list is created for an object, there are five posting statuses that are used for partial posting.

• Not Yet Posted – Data which is not posted • Ready for Posting – Only the data marked as Ready for Posting will be posted • Blocked for Posting – Data will be permanently blocked for Posting • Partially Posted – Only a portion of the data has been posted • Posted – Entire data has been posted

These statuses can be assigned manually or through the rules.

Matrix Functions Categorization

Page 1 of 2

The existing functions have been categorized with the implementation types based on the type of function associated with it. The existing functions Pre-Defined, Computation, User-Defined, and Forecast, have been restructured and categorized into new Function Types and Implementation Types. Based on the type of Function defined, the user will assign the corresponding Implementation type for the function. For a newly generated matrix, the predefined functions will be assigned automatically. The user can define customer functions with its corresponding implementation types. These functions can be assigned at Subset Usage level under the Assignments tab to manipulate the matrix data at planning workbench. As shown below, the list of functions are created for a newly generated matrix.

List of Categorized Functions with corresponding Implementation Type Combinations:

Function Type Implementation Type

Distribution Pre-Delivered Script/Measure Enhancement

Computation Script/Measure Enhancement

Forecast Pre-Delivered

Distribution with Reference

Pre-Deliverd

Matrix Functions Categorization

Page 2 of 2

In prior releases the system provided the Computation function as part of the matrix. Now this function can be accomplished with the combination of the function type Computation and the Implementation type Script/Measure. To replicate the User Defined functions, the user will have to select the combination of the Computation function type and the Enhancement implementation type. To utilize the Forecast Function, a selection of the function type Forecast and Pre-Delivered must be made. When replicating the User Distribution function from prior releases, users will select the Distribution function type, and, as opposed to prior releases, either the Enhancement implementation type or the Script/Measure implementation type.


Page 1 of 4

At planning workbench, the matrix data can be distributed using the Distribution with Reference function. When this function is applied during planning, the matrix data will be distributed according to the Reference Key Figure assigned at subset workbench. Initially, the Distribute with Reference fields are defined at the matrix workbench and are assigned at subset workbench. While assigning the function at the subset workbench, the user can specify the Reference Key Figure according to which the data will be distributed. The Reference Key Figure can be the Same Key Figure or the Other Matrix Key Figure. After execution in the planning workbench, this function can be applied by right clicking on a value in the planning grid. For example, in the below screen shot the Matrix /IRM/IPMXM0355 and its associated function DIST_OVRK has been created using the Function Type Distribution with Reference and implementation Type Pre-Delivered. This combination is necessary to use the Distribute Matrix Data with Reference function.

Once the function is created for the matrix, it must be added as an assignment to the matrix and subset through the usage tab. Using the above example, the function has been assigned to the Subset TEST_SUB2 and the Usage 001, as shown in the screen shot below.


Page 2 of 4

After the function is assigned to the assignments tab, a Reference Key Figure must be provided according to which the matrix amount is to be distributed. In the screen shot below, the Adjusted Amount field has been assigned as the Reference Key Figure for the function DIST_OVRK.

With the selections and setup completed, the Distribute with Reference function is ready for use in the matrix planning screen. When the planning selection screen is displayed, selections for the Matrix, Subset, Usage, and Period must be made. As shown in the below screen shot, the user selected the Matrix /IRM/IPMX0362, the Subset TEST_SUB2, the Usage 001, and the Month 2015.01.


Page 3 of 4

After the selections are made and the planning screen is executed, the corresponding data related to the selections will be displayed, as shown below.

With the data displayed the user is able to overwrite the amount provided. Once this is done, the amount can be distributed based on the previously established Reference Key Figure. For example, in the screen shot below, the user changed the Sales Org 0001 value to 200 from the previous value of 15. To distribute this among th characteristics, the user will right click on the new value and select the option Distribute with Overwrite using Reference, which was the option create as part of the matrix functions and assigned to the subset. Then the data in the two characteristic fields will be replaced with new values based on the ratio established from the Reference Key Figure, the Adjusted Amount field.


Page 4 of 4

Based on the previous example, the 200 will be split with 60% of the value attributed to the American Dollar and 40% allocated to the Indian Rupee.

Agreement Status Update

Page 1 of 1

Agreement Status update from IP document

As of Release E Service Pack 3, users can determine whether the agreement status field is

update with the IP document settlement status. This control can be maintained regardless if

the settle by agreement flag is marked in the agreement settlement tab. This can be

achieved by using the Turn off Agreement Status Update flag at the settlement profile level.

In order to mark the Turn off Agreement Status Update flag, the user must execute the

configuration transaction /IRM/IPSPRO and follow the path Accrual and Settlement > Define

Settlement Profiles.

Once the flag is set, when the system preforms the settlement of an IP document, the

respective agreement status is not updated.