IRMIPM 60D SP3: Release Notes - Vistex, Inc · See the Release Notes under the Period Profile area...

Vistex, Inc. Page 1 of 24 Last Modified: 1/17/2013

Area Type of Change Transaction Code Topic ChangesAddress Match New Functionality /IRM/GCRM

/IRM/GMLM/IRM/GPLM

Address Comparison This functionality allows the user to compare the addresses that the system has found for the partner provided and partner determined based on the lookup profile. This is available in the claim workbench, transaction workbench, and the membership workbench. Functionality is only available after creating an address match path and then assigning the match path to the claim type, transaction type, or membership submission type.Address Match Path Configuration:/IRM/IPSPRO > Basic Functions > Address Match > Define Address Match Path

Agreement New Functionality /IRM/GSRCHPM Agreement BSP - More Values Search Profiles now have the option to further define selection criteria with 'More Values.' By using More Values, a single or range of specific values can be included or excluded in search selection criteria. These values will populate the Search Fields based on configuration and available values are specific to the Search Field chosen. The following options are available:

1. Select Single Values2. Select Range3. Exclude Single Values4. Exclude Ranges

Options 1 & 2 will set Parameter to 'is.' Options 3 & 4 will set Parameter to 'is not.' Agreement New Functionality /IRM/GAXREF Agreement Cross Reference This functionality allows the user to create a cross reference for any agreement or sales deal which can be used either

across all sales organizations, distribution channels, and divisions or specific to one partner in one sales organization, distribution channel and division. This cross reference is utilized in the claims workbench and transaction register. No additional configuration is needed to utilize this cross reference.

Agreement New Functionality /IRM/IPxxAGUPL/IRM/IPxxASP

Agreement Upload/Download New agreements can be created , existing can be changed and can download agreements using this upload/download functionality which is now available through the below transactions: /IRM/IPxxAGUPL/IRM/IPxxASP

In order to perform these actions, having the file template is mandatory. File template can be created using the transaction /IRM/IPAGFTM.

For more information, go to the Agreement Upload Download attachment.Agreement New Functionality /IRM/IPxxASP Badi / User Exits A new badi method was provided in the badis/IRM/BADI_IPxx_ASP, CLAIM_CREATE. This badi method can be used to

modify the Claim document to be created at time of Agreement Close-out.Agreement Request

New Functionality /IRM/IPxxARM/IRM/IPxxARUPL

Agreement Request Upload/Download

Using the Upload/Download functionality Agreement Request(s) can now be created, existing request(s) can be changed, or request(s) can be downloaded. Functionality is now available through the following transaction codes: /IRM/IPXXARUPL/IRM/IPXXARM

File Template is mandatory in order to perform these actions. Agreement Request file template can be created in transaction /IRM/IPARFTM.

For more information, go to the Agreement Request Upload Download attachment.

IRMIPM 60D SP3: Release Notes


Area Type of Change Transaction Code Topic Changes


Agreement Request

New Functionality /IRM/IPxxARM Periods TAB Configuration: Maintain Agreement Request into Agreement Type and Assign Agreement Type to the Specific Deployment Code and the Active Version.

/IRM/IPSPRO > Basic Function > Pricing Sales > Pricing Agreements > Maintain IP Agreement type: Maintain Agmt Type with Deployment Code and Active Version.

Note: If the Agreement Request Type is marked for Collective Request in the configuration, Periods TAB cannot be seen in Agreement Request Workbench.

Configuration: Make sure Period Parameters - flexible Periods is assigned to the Deployment code /IRM/IPSPRO >Composite IP > Deployment codes and components > Define Deployment codes: - Click on Period Parameters and select a Deployment Code and click details - Assign Flexible periods for Periodicity.

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: Agreement SpecificThe system allows the user to make changes to the periods and save the agreement.

Agreements New Functionality /IRM/IPxxASP/IRM/IPxxARM

Period Profile Period Profile is integrated into the agreement. Instead of using an IP calendar or an SAP fiscal year, you can define your own period profile and add to an agreement. In order to use this functionality, a deployment code must be maintained in the agreement type configuration.

See the Release Notes under the Period Profile area and Periods TAB topic for more information.




Agreements New Functionality /IRM/IPxxASP Periods TAB When using Period Profile for agreements, in order to display the Periods Tab in Agreement Workbench, user needs to set up the configuration, as outlined below:

Configuration: Assign Deployment Code and the Active Version to the Agreement Type /IRM/IPSPRO > Basic Function > Pricing Sales > Pricing Agreements > Maintain IP Agreement type > Maintain Agmt Type with Deployment Code and Active Version.

Configuration: Make sure Period Parameters - flexible Periods is assigned to the Deployment code /IRM/IPSPRO > Composite IP > Deployment Codes and Components > Define Deployment Codes.- Click on Period Parameters and select a deployment code and click details - Assign Flexible periods for Periodicity.

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: Agreement SpecificThe system allows the user to make changes to the periods and save the agreement.

Business Partner New Functionality n/a Business Partner Inbound IDoc – Create/Change

Business partners can now be created or maintained using inbound IDOCs using the Basic Type /IRM/GBUPARTNER01 and the message type /IRM/BUPARTNER on the IDOC.

Calculation Run New Functionality /IRM/IPxxPCRCMP Calculation Run Mass Creation In the mass creation report for calculation run creation, users can now create individual Calculation Runs for each selected participant by checking the 'Individual Calculation Run' flag.

Calculation Run New Functionality /IRM/IPxxPCRM Copy Button The Copy functionality has been extended to allow the copy of calculation runs from claims and other calculation run. The copy type now has 4 values: 1.Reallocation with Claims 2.Recalculation with Claims 3. Recalculation 4. Direct

Calculation Run New Functionality /IRM/IPxxPCRM Create Button A Create button has been introduced in the Calculation Run Workbench. This button now allows users to create, review, and save a Calculation Run directly from the workbench. Previously, Calculation Runs could only be created from Collective Tracking and Mass Process Workbenches. Using the Create button will simulate Calculation Run, allowing the user to review the Accounting, Allocation values and then save. The simulation functionality has also been integrated into the Mass Process Reports for creating Calculation Run.

Calculation Run New Functionality /IRM/IPxxPCRM Creating Claims for Multiple Partners from Calculation Workbench

Directly from the Calculation Run Workbench, users can create individual Claims for multiple settlement partners. Previously, users could only create one claim at a time. Now, users can select multiple settlement partners for one participant and create Claims.




Claims New Functionality /IRM/GCR37 Claim Validation - Mode on Selection Screen

Claim Validation workbench has been redesigned with new functionality, in claim validation workbench Mode functionality was developed and is available in selection screen which has two options: A “Display” and B “Change”, Display mode lets the user to enter in the workbench in display mode and similarly change mode allow user to enter in change mode. Header and Item grid in claim validation workbench is been introduced as editable and it is available to edit at the header level as well as item level.

Auto correction functionality is also available from claim validation workbench, where users can select and create Auto Correction ID which can be executed at a later point in time. separate workbench is also designed for Auto Correction for claims to perform mass change (Transaction /IRM/GCRACM).

Claims New Functionality /IRM/GCRUPL Upload Source Previously, in the upload transaction the Sources were split into two tabs: Desktop Source and File Server Source. Now, the tabs have been eliminated and placed into the File Source section in the File Location field, which defaults to the Desktop Source.

Claims New Functionality /IRM/GCRM/IRM/GCRFTM/IRM/GCRUPL

Upload/Download Users can now create Claims using the Upload File functionality. Previously, only Claims Download functionality was available.

File Template is mandatory to Download/Upload Claims through transaction /IRM/GCRFTM. Users have to create a file template and determine if the template is to be used for importing files only, exporting files only, or importing and exporting files. The file format determines the type of file the system will use for importing or exporting. The formats include, Microsoft Excel, CSV Format (Comma Separated Variable), Text Format.

For more information, go to the Claims Upload Download attachment.

Claims / Transactions

New Functionality /IRM/GCRM/IRM/GRCAM

Parallel Net Value Claims and Transaction Register Workbench now has Parallel Net Value functionality, which allows users to achieve decimal value up to maximum precision.

Parallel Net Value should be configured for a specific Condition Type in Condition Type Additional Data at the Transaction Register and Claim Type level. Once Parallel Net Value is configured it is available in Claim and Transaction Register Workbench at the line item level and it will show the actual parallel net value at each line item. However, at the Header level it will round off the sum of the two line items with more precise decimal value.





New Functionality /IRM/GCRACM/IRM/GRCAACM

Auto Correction Auto Correction is a new functionality that allows processing mass changes in claim and transaction documents in dialog. User has to create an Auto Correction ID and then maintain different combinations of qualifier and correction criteria which tell the system 1) what documents to use and 2) what changes are to be made.

The Auto Correction workbench for claims is /IRM/GCRACM, the Auto Correction workbench for transactions is /IRM/GRCAACM). This functionality is also accessible from Claim Validation workbench (/IRM/GCR37), where users can create an Auto Correction ID which can be executed at a later point in time.

Auto Correction also lets user to change field values for selected documents if it meets specific criteria, setup corrections first and then execute it, or set the values for some fields irrespective to the values of others. Auto correction interface has four following sections:1. Selection – contains the documents in which changes can be applied.2. Qualifier – User can list specific fields and field values that system will use a criteria that has to be met before processing the correction.3. Correction – Actual changes to be made to the fields or actions to be carried out on the claim if the above qualification is met4. Execute – Is used to process the correction.

The following authorization objects are required in order to use the Auto Correction functionality: V_GB_CRAC Authorization for Claim Auto Correction Definition V_GB_RCAAC Authorization for Transaction Auto Correction Definition


New Functionality /IRM/GCRACRM/IRM/GRCAACRM

Auto Correction Run Maintenance

An auto correction run mass maintenance program is available for claims / transaction to process an auto correction in batch. The claim transaction is /IRM/GCRACRM, for transactions it is /IRM/GRCAACRM. This transaction will list a log of the objects that were processed in that particular auto-correction and provide any messages that were triggered for the auto correction run.


New Functionality /IRM/GCR37/IRM/GRCA37

Badi / User Exits Badis are now provided to influence the field catalog of the claim/transaction validation report: /IRM/BADI_GCR_VLD (Claim) and /IRM/BADI_GRCA_VLD (Transaction):

HEADER_DATA_PREPARE Header fields catalog prepareITEM_FCAT_MODIFY Items fields catalog modifyITEM_DATA_PREPARE Items fields catalog prepare


New Functionality /IRM/GCRACM/IRM/GRCAACM

Badi / User Exits Badis are provided to influence Auto Correction behavior: /IRM/BADI_GCRAC_ALL (Claim) and /IRM/BADI_GRCAAC_ALL (Transaction). The following methods are included:

BEFORE_CORRECTION_SAVE Before saving the correction changesAFTER_CORRECTION_SAVE After saving the correction changesBACKGROUND_JOB_PROCESS Process auto correction background jobHEADER_CORR_BEFORE_QUAL_EXEC Before executing the qualifier for header correctionITEM_CORR_BEFORE_QUAL_EXEC Before executing the qualifier for item correctionHEADER_CORR_AFTER_QUAL_EXEC After executing the qualifier for header correctionITEM_CORR_AFTER_QUAL_EXEC After executing the qualifier for item correction





New Functionality /IRM/GCRM/IRM/GCR27/IRM/GCR29/IRM/GCR37/IRM/GRCAM/IRM/GRCA27/IRM/GRCA37

Badi / User Exits A new badi method is provided in the badis /IRM/BADI_GCR_ALL (Claim) and /IRM/BADI_GRCA_ALL (Transaction):

BEFORE_ITEM_COPY_CHECK --> this badi method can be used to determine whether to copy source claim/transaction item to target, and also to modify any item related parameters; this method is called whenever claims/transactions are created with reference, resubmitted, transferred or transferred with deletion (Claims - /IRM/GCRM, /IRM/GCR27, /IRM/GCR29, /IRM/GCR37, Transactions - /IRM/GRCAM, /IRM/GRCA27, /IRM/GRCA37)


New Functionality /IRM/GSRCHPM Claims / Transactions BSP - Search Profile - More Values

Search Profiles now have the option to further define selection criteria with 'More Values.' By using More Values, a single or range of specific values can be included or excluded in search selection criteria. These values will populate the Search Fields based on configuration and available values are specific to the Search Field chosen. The following options are available:


Options 1 & 2 will set Parameter to 'is.' Options 3 & 4 will set Parameter to 'is not.'


New Functionality /IRM/GCRDIU/IRM/GRCADIU

Duplication Check Duplication profile checks were rewritten for performance. The underlying duplication data has changed in format, and so the transactions /IRM/GCRIDU (update claim duplication index) and /IRM/GRCADIU (update transaction duplication index) needs to be run to convert your current duplication check data into the new format. This is listed in the conversion report section of the 60D Support Pack installation note, however please note that this transaction can be run at any point in time, not just as part of the installation.

Composite New Functionality /IRM/IPxxCCP/IRM/IPxxPCRM

Delta Accruals Functionality has been provided to only perform 'delta' accruals for all but the first period accrual. Normally in a period to date plan, an accrual is done for the first period, and the accrual for the next period will reverse the accrual from the first period and then do a completely new accrual for the second period. With delta accrual functionality, the accrual for the first period takes place as usual, but the accrual for the second period is for only the delta amount in the second period. The delta being the difference between the period to date accrual value for the second period minus the accrual value of the first period. Reversing one of the subsequent period delta accruals only reverses the delta amount.

For a delta accrual posting, the delta amount is distributed back to all the IP document line items or just the line items that have contributed to the change in accrual value. You can only use this functionality if you have IP types assigned to your allowed version(s). Turn on this functionality through configuration.

Prerequisites: IP types assigned to your allowed version(s) Accounting Level of Allowed Version must be at the IP Document Level

Configuration: - /IRM/IPSPRO > Composite IP > Deployment Codes and Components > Define Deployment Codes > Deployment Code Allowed Version Level > choose one of the 'Delta Accruals' option




Composite New Functionality /IRM/IPRPM Deployment Code for Reporting There is now the option to run reports that includes multiple Deployment Codes. Deployment Codes for Reporting groups specific Deployment Codes for reporting use only. A Deployment Code for Reporting allows user to assign multiple Deployment Codes, assign Participant Types, and define Periods for reporting. Users can then run reports based on specific Key Figures and Time Periods for the configured Deployment Code for Reporting.

Note that Deployment Code for Reporting is only for reporting purposes and available in the Report Workbench. It will not be available for use in Collective Tracking, Individual Tracking, and Mass Process Workbenches.

For more information, go to the Report Workbench attachment.

Composite New Functionality /IRM/IPxxCCP Evaluation Anchor Functionality is available in Collective Tracking and Mass reports. Evaluation Anchor will allow tracking of multiple participants which have multiple period profiles assigned. Tracking will occur based on an Evaluation Date, which is entered by user. The evaluation anchor has 3 options: 1. Provide Period then Participant This is the standard method. In tracking, you choose the period first, and then choose the participant. 2. Provide Participant then PeriodThis is used when the period is determined based on the participant (participant contains period profile). In collective tracking, if multiple participants have different periods, only the ones with common periods can be tracked together - the other participants cannot be tracked at the same time. 3. Provide Evaluation Date and then Participant Instead of having a period selection field in tracking, you will have an evaluation date field. You must provide the evaluation date field which then determines which participants from your selections will show up on the tracking screen.

Configuration for Evaluation Anchor is set in the Period Parameters section at the Deployment Code level. The evaluation anchor for all existing deployment codes is by default set to option 1, Provide Period then Participant. The evaluation anchor field is only open for input in configuration if the periodicity of the plan is set to Flexible Period.

Composite New Functionality /IRM/IPxxCCP/IRM/IPxxPCRM

FI Accrual Summarization You can now summarize your accrual items by IP document line item attributes, for example by material group. All the line items will sum up until there is only one line for each material group, decreasing the number of line items on the accrual document. Once the lines are condensed by the attributes, only then is account determination called for the summarized lines. Turn on this functionality through configuration.

Prerequisites: Accounting Level of Allowed Version must be at the IP Document Level

Configuration: 1. Create a summarization profile (choose your attributes, your collection of fields, used to sum by) - /IRM/IPSPRO > Composite IP > Deployment Codes and Components > Define Summarization Profile2. Associate the summarization profile to a deployment code - /IRM/IPSPRO > Composite IP > Deployment Codes and Components > Define Deployment Codes > Deployment Code Allowed Version Level > Summarization Profile




Composite New Functionality /IRM/IPxxCIP Layout, HTML, Grid Views Displayed Subcomponents for Individual Tracking introduces many new layout options. There is now an option to toggle between Grid view and HTML table view. HTML table display columns consisting of all the characteristics and key figures which have authorization, which also serves the purpose to integrate standard grid functionalities. There are also four more individual options to further customize and manage layouts:

1. Select Layout - User can select the desired layout from the list of layouts he had defined in the system for specific Deployment Code and Version.

2. Change Layout - User can select desired option from popup window as: 2a. Displayed Column : It is used to select the columns, which needs to be displayed in the grid on screen, user can mark the fields which should be summarized. 2b. Sort Order : It is used to define the sort order by which table data should be displayed on the screen, the same field if required can be marked for subtotals to get the summarized info, grouped together based on subtotal fields. 2c. Filter : In displayed table data, if user is interested only in some specific line of data, then filter option is useful where users can give condition on which they want to see data in subcomponent data displayed on the screen.

3. Default Layout - User can reverse all layouts changed to the previously configured layout specified in the Configuration at Deployment Code level.

4. Manage Layout - User can make particular layout as default layout or delete specific layout from list of layouts.

There is an option to select the default view for the subcomponent. 1. HTML view or 2. Grid view. This option is available in Screen Layout Parameters under Assigned Subcomponents

Composite New Functionality /IRM/IPxxPA/IRM/IPxxCIP/IRM/IPxxCCP/IRM/IPCMP

Lookup Profile Lookup Profiles have been integrated with the Composite Process. Lookup Profile functionality can be used to perform partner determination based on identification types.

In order to use partner determination, the Lookup Profile must be configured and associated with a Partner Identification Type. The Partner Identification Type is then assigned to the deployment code participation type configuration. In tracking for that deployment code, the collective search help for the participant field is dynamically adjusted based on the Lookup Profile. Also, if a non-SAP partner value is entered in the participant field, a technique called 'reverse lookup' is triggered which goes through the search options of the Lookup Profile, and the corresponding SAP value is then determined.

See the Release Notes for Partner Lookup Profile (in this same document) for more information on Lookup Profiles.




Composite New Functionality /IRM/IPxxPA/IRM/IPxxCIP/IRM/IPxxCCP

Period Profile Period Profiles1 can be used to drive the period of the tracking transaction. This is useful participants are tracked on different evaluation periods. Period Profiles can be assigned to Participants, which allow users to set defined fiscal periods for the Participants.

Configuration for this functionality is set in Period Parameters in Deployment Code level configuration. Periodicity should be set to 'F Flexible Periods.' Evaluation Anchor2 should also be maintained.

This functionality is available in Participation Workbench, Individual Tracking, and Collective Tracking.

1. See Release Notes Year Dependent Period Profile, Calendar Period Profile, Year Dependent Period Profile, and Period Profile - Year Shift for more information on Period Profiles. 2. See Release Note Evaluation Anchor for more information on Evaluation Anchors.

Composite New Functionality /IRM/IPxxVM Search Variants Search Help Variant workbench has been modified to allow the creation of Search Variants (earlier called search help variants) and Participation Variants which are used to define virtual participations in composite tracking. These variants are assigned as participants in the participation workbench.

Composite New Functionality /IRM/IPxxVM Virtual Participation With the use of Search Variants (see 'Search Variants' release note), it is now possible to create virtual participant lists to be used throughout the composite process. Virtual Participation allows users to track participants without manually storing each participant record. Fetching participant list at runtime provides a significant performance enhancement to the system.

To use Virtual Participation, a Participation Variant must be assigned to a Deployment Code. The Participation Variant must be of Category Type '1 Participation.' Also, 'Virtual Participation' checkbox must be flagged in Deployment Code Configuration.

Since Virtual Participation is tied to the Deployment Code, it can be used in the following areas: Individual Tracking, Collective Tracking, Calculation Run, Mass Calculation Run, and Mass Postings.

Composite New Functionality /IRM/IPxxCIP/IRM/IPxxCCP/IRM/IPxxCPP/IRM/IPxxPCRM

Badi / User Exits Multiple new composite user exits are provided in the function group XIPxx:

EXIT_SAPLXIPxx_072 --> This user exit can be used to reapportion IP documents before updating document flow - Period to Date. Used when IP document flow is being updated from composite accruals/settlement, etc. In case of multiple accounting documents, this user exit can be used to reallocate the amounts at the IP line item level.

EXIT_SAPLXIPxx_073 --> This user exit can be used to reapportion IP documents before updating document flow - Current Period. Used when IP document flow is being updated from composite accruals/settlement, etc. In case of multiple accounting documents, this user exit can be used to reallocate the amounts at the IP line item level.

EXIT_SAPLXIPxx_074 --> This user exit can be used to influence the period to date GET_RANGE or GET_VALUE data when IP documents or claims are fetched using dataset. If the dataset definition has GET_RANGE or GET_VALUE, the system will perform a call to this user exit which will have the composite PTD/CPD and subcomponent data available.

EXIT_SAPLXIPxx_075 --> This user exit can be used to influence the current period GET_RANGE or GET_VALUE data when IP documents or claims are fetched using dataset. If the dataset definition has GET_RANGE or GET_VALUE, the system will perform a call to this user exit which will have the composite PTD/CPD and subcomponent data available.




Composite New Functionality /IRM/GSRCHPM Composite BSP - More Values Search Profiles now have the option to further define selection criteria with 'More Values.' By using More Values, a single or range of specific values can be included or excluded in search selection criteria. These values will populate the Search Fields based on configuration and available values are specific to the Search Field chosen. The following options are available:


Options 1 & 2 will set Parameter to 'is.' Options 3 & 4 will set Parameter to 'is not.' File Template New Functionality /IRM/*FTM Badi / User Exits New badi methods are provided in the File Template badi /IRM/BADI_GDCT_ALL:

CONVERSION_DISPLAY_PREPARE --> This method can be used to influence the display of conversion data in the File Template Workbenches

BEFORE_SAVE --> This method can be used to influence the file template data before it is saved to the database

AFTER_SAVE --> This method can be used to trigger an action after file template data has been saved

Launchpad New Functionality /IRM/GWSM Workspace Workbench - More Values

The workspace workbench now has the functionality to save search information for GUI links that are included in the Launchpad.

The user can define either include single values or ranges, or exclude single values or ranges by clicking on the "More Values" button when adding a GUI link to workspace workbench; then saving and transporting the workspace profile and assigning the workspace to a Launchpad Profile.

Material Cross Reference

Informational /IRM/IPSPRO Material Identification Type The material identification type determines which material lookup profile the system will use to determine the lookup profile that is used to identify the correct material in the cross reference table. The Material Identification types then are assigned to Claim Types, Transaction Types, and Composite Deployment Code, and Product List types under the Material Identification field.Creating Material Identification Type:/IRM/IPSPRO > Basic Functions > Material Determination > Define Material Identification Types

For even more information, go to the IRMIPM 60D SP1 Release Notes --> Lookup Engine for Material and Partner topic.


Informational /IRM/IPSPRO Material Lookup Profile Lookup profile will determine the process the system uses to determine the correct SAP material when using the material cross reference functionality. The user can establish the sequence in which the system will search the various system tables. Then, the lookup profile can be assigned to a Material Identification Type.Creating Lookup Profile and Lookup Sequence:/IRM/IPSPRO > Basic Functions > Material Determination > Define Material Lookup Profile > Material Lookup Sequence






Informational /IRM/GMXREF Material Lookup Universal Lookup

This functionality allows the user to create a universal cross reference for a material that can be used across all sales organizations, distribution channels, and divisions. This cross reference can be utilized in the claims workbench, transaction register workbench, price maintenance, price type, and price book. Before using the cross reference, a Lookup profile and lookup must be created and assigned to a Claim type or Transaction type.Creating Lookup Profile and Lookup Sequence:IRM/IPSPRO > Basic Functions > Partner Determination > Define Partner Lookup Profile > Partner Lookup SequenceAssigning Lookup Profile to Claim Type:IRM/IPSPRO > Documents > Claims > Define Claim Type > Select Claim Type >Partner Identification Type 1 & 2 > Assign Lookup ProfileAssigning Lookup Profile to Transaction Type:IRM/IPSPRO > Documents > Transaction Register > Define Sales/Purchasing Transaction Type > Material ID Types


Membership New Functionality /IRM/GMLM Address Maintenance This functionality allows the user to make changes to partner addresses in the membership workbench. The changes that have been made to the addresses are only reflected in the membership workbench and not in the customer master. The system will now store the changes made to partners with valid and not valid numbers.

Membership New Functionality /IRM/GMLFTM Membership File Templates In order to utilize the Membership upload/download functionality, the user must first create a template which the system will use to identify the membership information. To create a template, the user will have to create a name and description, as well as determine if the template is to be used for importing files only, exporting files only, or importing and exporting files. The file format determines the type of file the system will use for importing or exporting. The formats include, Excel, CSV (Comma Separated Variable), Text, Tab Delimited (Text file with values separated by tabs), or Fixed File format (Text file in which the values are always at the same position in the line). After entering the template name, description, type, and file format, the user must then determine the start row, an end row (if necessary), and if the file should display the field titles for both the header section and the members section of the membership. In the mapping tab, the user will select the desired fields from both the header and the member for the upload and download process. To determine the order in which the information is presented, the user will have to enter a position value for each field. Please note that a numeric value will have to be entered into the position column. If there is a field that must always be the same, the user can set that field to a fixed entry by entering a value into the Field value Column. Once the user has completed the creation process, the file template must be saved and transported to be used in the upload or download process.

Membership New Functionality /IRM/GMLIDOC Membership List - Outbound IDoc Creation Report

Using transaction /IRM/GMLIDOC, which calls program /IRM/GML_IDOC_CREATE, users can now generate outbound IDOCs displaying all the membership information for a particular trade organization. The IDOC will include all information on members as of a specified date, including the membership information of other trade organization listed as members (sublist). These IDOCS then could be sent to the corresponding partners.




Membership New Functionality /IRM/GMLUPL/IRM/GMLM

Upload/Download Membership List

Users can now create new membership structures, maintain existing ones, or download membership submission information through the upload/download functionality. Membership submission downloads are done through the Membership workbench, /IRM/GMLM - Membership Workbench. Membership uploads are prepared by using transaction /IRM/GMLUPL - Upload Membership List.In order to either upload or download a membership, a template will first have to be created. Once a template has been created a membership submission can be downloaded through the membership workbench by selecting the submission number, then clicking on Extras and Export to file. A new window will pop up requiring the file template name and a file path.After creating a file template to upload a membership from transaction /IRM/GMLM, the user only needs to enter the template name and the file name, using the whole file path, in the file info section. Previously, in the upload transaction the Sources were split into two tabs: Desktop Source and File Server Source. Now, the tabs have been eliminated and placed into the File Source section in the File Location field, which defaults to the Desktop Source. When the template is entered the rest of the corresponding information is completed by the system. Lastly, user has to click the execute button and the membership information will be uploaded.

Partner Cross Reference

Informational /IRM/IPSPRO Partner Identification Type The material identification type determines which partner lookup profile the system will use to determine the lookup profile that is used to identify the correct partner in the cross reference table. The Partner Identification types then are assigned to Claim Types, Transaction Types, and Composite Deployment Code, and Membership Submission types under the Partner Identification field.Creating Partner Identification Type:/IRM/IPSPRO > Basic Functions > Partner Determination > Define Partner Identification Types



Informational /IRM/IPSPRO Partner Lookup Profile Lookup profile will determine the process the system uses to determine the correct partner number when using the material cross reference functionality. The user can establish the sequence in which the system will search the various system tables. Then, the lookup profile can be assigned to a Partner Identification Type.

Creating Lookup Profile and Lookup Sequence:/IRM/IPSPRO > Basic Functions > Partner Determination > Define Partner Lookup Profile >Partner Lookup Sequence






Informational /IRM/GPXREF Universal Customer Cross Reference

This functionality allows the user to create a universal cross reference for a customer that can be used across all sales organizations, distribution channels, and divisions. This cross reference can be utilized in the claims workbench, membership workbench, transaction register, price types, and price books . Before using the cross reference, a Lookup profile and lookup must be created and assigned the corresponding area, e.g. claim type or membership submission type.Creating Lookup Profile and Lookup Sequence:/IRM/IPSPRO > Basic Functions > Partner Determination > Define Partner Lookup Profile >Partner Lookup SequenceAssigning Lookup Profile to Claim Type:/IRM/IPSPRO > Documents > Claims > Define Claim Type > Select Claim Type >Partner Identification Type 1 & 2 > Assign Lookup ProfileAssigning Lookup Profile to Membership Type:/IRM/IPSPRO > Basic Functions > Membership > Define Submission Type > Partner ID Type


Period Profile New Functionality /IRM/GFPM Calendar Period Profile This functionality allows the user create a period profile that is based on the calendar year. The calendar year profile will create twelve monthly periods that are the same as the twelve calendar months.

Period Profile New Functionality /IRM/GFPM Period Profile - Year Shift This functionality allows the user create a period profile in which the start of the fiscal period is in the middle of the calendar year. This is done by entering either a “+1” or a “-1” in the year shift column for the periods that fall into either the next fiscal period or the prior fiscal period.

Period Profile New Functionality /IRM/GFPM Period Profile Workbench A Period Profile workbench has been introduced. Period Profiles are similar to SAP fiscal year variants. When setting up a period profile, you specify whether it is based on a calendar year, or other date ranges that can be year dependent or independent. The period profile created can be utilized in the agreement workbench, participant workbench, individual tracking, and collective tracking.

Period Profile New Functionality /IRM/GFPM Year Dependent Period Profile This functionality allows the user create a period profile that is dependent on the year. This allows users to create as many periods as are needed, with any end dates that the user specifies. However, the user can specify different end dates for the same period in each of the years that is created. The system will determine the correct period based on the current year and the dates that were entered by the user. The year dependent period profile can employ the year shift functionality if the start of the fiscal period is in the middle of the year.

Period Profile New Functionality /IRM/GFPM Year Independent Period Profile This functionality allows the user create a period profile that is independent of the year. It makes it possible to create as many periods as are needed, with any end dates that the user specifies. The year independent period profiles will maintain the same start dates and end dates for each period as specified regardless of the current year. The year independent period profile can employ the year shift functionality if the start of the fiscal period is in the middle of the year.

Price Request New Functionality /IRM/IPPQM Change Log Users can see the changes made to the Price request in the change log. Currently any changes made to the objects like Dates, Spend Types, Header, Territories or Partner will reflect in the change log. Change Log is also available at the rule level.

Price Request New Functionality /IRM/IPPQM/IRM/IPPQCD

Change Log Users are now able to see the changes made to the Price Request in the change log. Any changes made to the objects, such as: Dates, Spend Types, Header, Territories or Partner will reflect in the change log.

This functionality is also available for Mass Change via transaction /IRM/IPPQCD and at the rule level. Price Request New Functionality /IRM/IPSPRO Hide Organization and Basic

TabCan hide Organization and Basic tabs in BSP as per configuration in Block Profile. Previously it was set up as default to show both tabs.




Price Request New Functionality /IRM/IPSPRO Quick Information Block Configuration

Quick Information block displays fields configured in Deal Block Profiles configuration. The Quick Information fields will then override the standard fixed fields of Deal Type, Deal Number, and Description.

Price Request New Functionality /IRM/IPPQM_WS Save Button A Save button is now available for use within all blocks (on all screens of the web transaction), not just the Review and Save block.

Price Request New Functionality /IRM/IPPQUPL /IRM/IPPQM/IRM/IPPQFTM

Upload/Download Upload/Download is now available to create or change existing Price Requests. Users can use Upload transaction, /IRM/IPPQUPL, to create or change existing Price Requests. Both Upload/Download can be done via 'Extras' and 'Goto' menu options from Price Request Workbench, /IRM/IPPQM. In addition, multiple Price Requests can be uploaded/downloaded at a time.

A File Template is mandatory to Upload/Download a Price Request. Users can create and/or maintain file templates through transaction /IRM/IPPQFTM.

For more information, go to the Price Request Upload Download attachment.Price Request New Functionality /IRM/IPSPRO Value Property A new configuration item called Value Property is available in Block Profile to assign different value properties to block

profile fields. Users can show just the value, show just the description, or show the value and description for fields.

Pricing New Functionality /IRM/GPRTWM Time Window Time Window is new functionality which allows for pricing conditions to be valid for only certain date/time intervals. User's will create a Time Window and will maintain different time frames under this using the workbench transaction /IRM/GPRTWM. More than one time window can be associated with a Time Window type. The system only checks if the start time > the end time during the entry of a time window record; there are no overlap checks on the time window dates. Once the Time Window type is created, it is then associated with a price sheet so that it is considered during rule creation.-For more information, go to the Pricing_Time Window attachment.

Product List New Functionality /IRM/GPLFTM Product List File Templates In order to utilize the Product list upload/download functionality, the user must first create a template which the system will use to identify the product list information. To create a template, the user will have to create a name and description, as well as determine if the template is to be used for importing files only, exporting files only, or importing and exporting files. The file format determines the type of file the system will use for importing or exporting. The formats include, Excel, CSV (Comma Separated Variable), Text, Tab Delimited (Text file with values separated by tabs), or Fixed File format (Text file in which the values are always at the same position in the line). After entering the template name, description, type, and file format, the user must then determine the start row, an end row (if necessary), and if the file should display the field titles for both the header section and the product section of the product list. In the mapping tab, the user will select the desired fields from both the header and the products for the upload and download process. To determine the order in which the information is presented, the user will have to enter a position value for each field. Please note that a numeric value will have to be entered into the position column. If there is a field that must always be the same, the user can set that field to a fixed entry by entering a value into the Field value Column. Once the user has completed the creation process, the file template must be saved and transported to be used in the upload or download process.




Product List New Functionality /IRM/GPLUPL/IRM/GPLM

Upload Product List Users can now create new product lists, maintain existing product lists, or download product lists information through the upload/download functionality. Product lists downloads are done through the Product List workbench, /IRM/GPLM – Product List Workbench. Product list uploads are prepared by using transaction /IRM/GPLUPL - Upload Product List.In order to either upload or download a product list, a template will first have to be created. Once a template has been created a product list can be downloaded through the product list workbench by selecting the product list number then clicking on Extras and Export to file. A new window will pop up requiring the file template name and a file path.After creating a file template, to upload a product list from transaction /IRM/GPLM, the user only needs to enter the template name and the file name, using the whole file path, in the file info section. Previously, in the upload transaction the Sources were split into two tabs: Desktop Source and File Server Source. Now, the tabs have been eliminated and placed into the File Source section in the File Location field, which defaults to the Desktop Source. When the template is entered the rest of the corresponding information is completed by the system. Lastly, user has to click the execute button and the membership information will be uploaded.

Reporting New Functionality /IRM/IPBRRPM Business Register Report Workbench

Similar to the report workbench, there is an additional workbench for creating reports in the Business Register module. This workbench will report on Claims, Business Register, Business Register Agreements, Business Register Agreement Requests, Transactions, and Price Type. Users are able to create reports by selecting categories such as Metric, Activity, Composite Adhoc, or Turnaround.

For more information, go to the Report Workbench attachment.Reporting New Functionality /IRM/IPRPM Reports Workbench A new Report Workbench is now available for reporting purpose for Billback, Chargeback, Sales Incentive, Purchase

Rebates, Sales Rebates, Claims, Transactions, Agreements, Agreement Requests, and Billing Documents. In the Report Workbench users can create reports by selecting categories such as Core, Metrics, Activity, Composite Adhoc, Matrix Adhoc, Turnaround, or Merged. For more information, go to the Report Workbench attachment.

Territories New Functionality /IRM/IPGTM Badi / User Exits A new badi was delivered to be used with Territories - /IRM/BADI_IPGTR_ALL :

BEFORE_SAVE --> used to influence the territory data before saving it to database

AFTER_SAVE --> used to trigger an action after the territory data has been saved

TERRITORY_CHECK --> used to perform checks on territory data before saving

AUTHORITY_CHECK --> used to perform an authority check for various activities such as display, change and create




Territories New Functionality /IRM/IPGTPM Badi / User Exits A new badi was delivered to be used with Territory Proposals - /IRM/BADI_IPGTP_ALL :

BEFORE_SAVE --> used to influence the territory proposal data before saving it to database

AFTER_SAVE --> used to trigger an action after the territory proposal data has been saved

BEFORE_POST --> used to influence the territory proposal data before posting

AFTER_POST --> used to trigger an action after the territory proposal data has been posted

PROPOSAL_CHECK --> used to perform checks on territory proposal data before saving

AUTHORITY_CHECK --> used to perform an authority check for various activities such as display, change and create

Territories New Functionality /IRM/IPGTPM Collective Territory Proposals This functionality works in conjunction with the determination mass creation/change functionality. When condition records are either created or changed, the user has the option to save the changes as a proposal. The collective proposals allow all the created or changed condition records to be saved into one proposal, which allows them to be reviewed at one time. Before using this functionality, the proposal type must be configured to handle collective proposals.

Configuration:/IRM/IPSPRO > Basic Functions > Territory Management > Define Territory Proposal Type

Territories New Functionality /IRM/IPGTM Determination Mass Creation/Changes

This functionality allows the user create or change the condition records assigned to many territories at one time. The condition records that are created or changed can be either saved directly into the territories or can be saved as a collective proposal and posted at after approvals.

Territories New Functionality /IRM/IPGTA Mass Territory Assignment Territory structure can be changed for multiple territories under an assignment type. It can either be saved directly or as proposal for approval.

Territories New Functionality /IRM/IPGTM Territories There is a new interface in the territory workbench which is similar to the interface that is used in other areas. Instead of displaying the territory structure on the left hand side of the screen and having buttons for the definition and determination, the list of territories is displayed on the left hand side and the general information, structure, determination are all part of the main screen but displayed in separate tabs. In addition, the user can create different assignment types and create different structures and determinations based on the assignment type. The territory workbench also allows for two search terms in which the user is able to use in the search territories screen.

A conversion report /IRM/IPGT_60D_SP2_SP3_CONVERT is delivered to convert the old territory values to the new territory structure, however the new territory configuration must be complete before running the conversion report.

The authority object V_IP_TRTYP (Authorization for Territory) must be associated with the user in order for the Territory transactions to be used.

Territory related configuration:/IRM/IPSPRO > Basic Functions > Territory Management > Define Territory Type/IRM/IPSPRO > Basic Functions > Territory Management > Define Territory Level/IRM/IPSPRO > Basic Functions > Territory Management > Define Territory Proposal Type/IRM/IPSPRO > Basic Functions > Territory Management > Define Territory Assignment Type




Territories New Functionality /IRM/IPGTM Territory Determination Territory determination condition tables and records are accessed through the territories that are created and not through a condition search. The condition tables are assigned to territory types through the configuration of the territory type. Creating condition records is similar to creating rules in agreement transactions.

Territories New Functionality /IRM/IPGTM/IRM/IPGTA

Territory Level Assignment This function allows users to assign levels to each member of the territory hierarchy. The territory level is not a mandatory field unless assigning a parent territory. In this case, the territory level of the child territory must be greater than that of the parent territory. Currently four territory levels are delivered with the option to create additional levels and maintain the current levels. To create additional territory levels, enter the IMG, /IRM/IPSPRO, under Basic Functions > Territory Management > Define Territory Level. When creating a new territory level the user must enter a numeric value in the Territory Level field, but it does not have to be sequential, allowing for additional levels to be added in between at a later date.

Territories New Functionality /IRM/IPGTPM Territory Proposals In addition to the new territory workbench, the new functionality allows any creation or changes of territories to be saved as a proposal. These proposals can be displayed and posted in this transaction.

The authority object V_IP_TPTYP (Authorization for Territory Proposal) must be associated with the user in order for the Territory transactions to be used.

Configuration:/IRM/IPSPRO > Basic Functions > Territory Management > Define Territory Proposal Type

Transaction IP New Functionality /IRM/GFMBM /IRM/GFMRLM

Badi / User Exits Multiple new badi methods were provided in the Funds Management badi /IRM/BADI_GFM_ALL :

BUDGET_FIELD_STYLES_PREPARE --> used to prevent certain field to be edited in budgeting/releasing whenever budget/release data is displayed (/IRM/GFMBM, /IRM/GFMRLM)

PER_OVW_FIELD_STYLES_PREPARE --> used to prevent certain field to be edited in budgeting/releasing whenever budget/release data is displayed in period-level pop-up (/IRM/GFMBM, /IRM/GFMRLM)




Transaction IP New Functionality /IRM/IPBRM/IRM/IPBR10/IRM/IPBR11/IRM/IPBR12/IRM/IPBR13/IRM/IPBR16

Badi / User Exits Multiple new badi methods were provided in the badi /IRM/BADI_IPBR_ALL :

LIS_PURCHASING_HEADER_PREPARE --> used to fill purchasing header level LIS fields whenever Business Registers being created or updated (/IRM/IPBRM, /IRM/IPBR23)LIS_PURCHASING_ITEM_PREPARE --> used to fill purchasing item level LIS fields whenever Business Registers being created or updated (/IRM/IPBRM, /IRM/IPBR23)CP_HEADER_FILL --> used to fill header and header level partners of Business Registers being created from composite postings; this method is called whenever Business Register documents are created (/IRM/IPBRM, /IRM/IPBR16)CP_ITEM_FILL --> used to fill item and item level partners of Business Registers being created from composite postings; this method is called whenever Business Register documents are created (/IRM/IPBRM, /IRM/IPBR16)BB_HEADER_FILL --> used to fill header and header level partners of Business Registers being created from Billback documents (/IRM/IPBRM, /IRM/IPBR10)BB_ITEM_FILL --> used to fill item and item level partners of Business Registers being created from Billback documents (/IRM/IPBRM, /IRM/IPBR10)CB_HEADER_FILL --> used to fill header and header level partners of Business Registers being created from Chargeback documents (/IRM/IPBRM, /IRM/IPBR11)CB_ITEM_FILL --> used to fill item and item level partners of Business Registers being created from Chargeback documents (/IRM/IPBRM, /IRM/IPBR11)CR_HEADER_FILL --> used to fill header and header level partners of Business Registers being created from Sales Rebate documents (/IRM/IPBRM, /IRM/IPBR13)CR_ITEM_FILL --> used to fill item and item level partners of Business Registers being created from Sales Rebate documents (/IRM/IPBRM, /IRM/IPBR13)SI_HEADER_FILL --> used to fill header and header level partners of Business Registers being created from Sales Incentive documents (/IRM/IPBRM, /IRM/IPBR12)SI_ITEM_FILL --> used to fill item and item level partners of Business Registers being created from Sales Incentive documents (/IRM/IPBRM, /IRM/IPBR12)

Transaction IP New Functionality /IRM/IPBRM/IRM/IPBR14

Badi / User Exits Multiple new badi methods were provided in the badi /IRM/BADI_IPBR_ALL :

PR_HEADER_FILL --> used to fill header and header level partners of Business Registers being created from Purchasing Rebate documents (/IRM/IPBRM, /IRM/IPBR14)PR_ITEM_FILL --> used to fill item and item level partners of Business Registers being created from Purchasing Rebate documents (/IRM/IPBRM, /IRM/IPBR14)

Transaction IP New Functionality /IRM/IPPCM/IRM/IPPCUPL

Badi / User Exits Multiple new badi methods were provided in the Partner Communication badi /IRM/BADI_IPPC_ALL :

SOURCE_DOC_DETERMINE --> used to influence source document determination based on the new entry fields 'Document-Entered' and 'Item-Entered' for a Partner Communication item, used whenever Partner Communication items are created or updated (/IRM/IPPCM, /IRM/IPPCUPL)

PROFILE_SET --> used to influence the Display Profile to be used for the Partner Communication workbench, used whenever a Partner Communication document is getting created, updated or displayed in the workbench (/IRM/IPPCM). The Display Profile maintained at the Partner Communication (PC) Type level can be over-ridden using this Badi method.

Transaction IP New Functionality /IRM/IPxx05 Badi / User Exits A new badi method was provided in the badis /IRM/BADI_IPxx_ALL, LIST_DATA_POPULATE. This badi method can be used to change or populate list-data in the List Display reports.

Transaction IP New Functionality /IRM/IPxxM Badi / User Exits A new badi method was provided in the badis /IRM/BADI_IPxx_ALL, DELETION_CHECK. This badi method can be used to check whether an IP document is eligible for deletion.




Transaction IP New Functionality /IRM/IPxxM/IRM/IPxx21/IRM/IPxx23

Cancellation of IP document Previously there was no option to cancel an IP document, only delete the IP document. A new processing option is now available to cancel an IP document. During the cancellation process, the system creates a new cancellation IP document with opposite Dr/Cr indicator of the original IP document, and links this cancellation document with the cancelled(original) IP document; both IP documents are marked as completed.

The main purpose behind introducing Cancellation Document is BW reporting. This functionality will improve the quality of the results the users will get from the BW reporting, because now all the Cancelled IP documents will be saved in the system instead of completely deleting the IP documents.

After cancelling of an IP Document, user should be able to see a Cancellation icon near Dr/Cr indicator. Also, on Admin Data tab, there should be Cancellation Document number and user can also navigate to the Cancellation Document from there and come back to the original IP document. After the IP document has been cancelled, users will not be able to process it further and it will not be eligible to have any postings. If the IP document has any open postings in process (e.g., the document is accrued, parked or settled), system will not allow the user to cancel it.


Cancel During Recreate Previously, when user used 'Recreate' functionality for the IP document, system would delete the previous IP Document and create a new IP Document. A new feature exists whereby the IP document being recreated will not be deleted, but cancelled instead. With the new "cancellation" functionality, if the flag for 'Cancel During Recreate' for a specific IP type is marked, system will not delete the old IP document, but cancel it by creating a matching cancellation document, then create a new IP document for that IP Type. This way the original (cancelled) document and corresponding cancellation document will remain in the system to be helpful for auditing purposes and BW Reporting.

Configuration: /IRM/IPSPRO > Docs > Define IP types > Flag – Cancel during Recreate


Delete IP Documents in Mass Processing

Previously, deletion of an IP document was only performed through the IP document workbench. The mass processing jobs now contain an additional processing option to delete IP documents. When IP documents are deleted through the mass processing programs, all IP documents being deleted will be soft deleted (marked for deletion, not physically deleted) no matter what IP Type config setting exists for the "No physical delete" flag.


Delta Accruals Previously, for an accrued IP document, if the user had to make any changes which would affect the net value of the IP document, the IP document's accrual status was no longer considered as completely processed and was considered as needing to be accrued again. The user had to reverse accrue the IP Document and re-accrue in order to accrue the new amounts and to set the accrual status as completely processed.

With the new functionality of Delta Accruals, user will not have to reverse accrue and re-accrue the IP document. Rather, whenever any changes are made to an accrued IP document, user will just need to accrue the IP document again and the system will create a brand new accrual document for the differential amount, meaning the positive/negative difference in the amounts before change and after change on the IP document. Two configuration steps are necessary in order to use this functionality.

Configuration: - /IRM/IPSPRO > Documents > Define Header Criteria - Sales Document > Go into IP Type, and check the box 'Delta Accruals'- /IRM/IPSPRO > Documents > Define IP Types > Go into IP Type and set the flag for "Log Accruals"





Internal Accruals With the new functionality of Internal Accruals, if accrual postings to FI are not desired, user will be able to post the accruals internally as Internal Posting by keeping the flag checked for "Internal Accrual" in Accrual Profiles configuration. System will post to Funds during internal accruals.

If the user wants a specific number range depending upon the document type for Internal Accruals, user can specify "Internal Document Type" in the Accrual Profile configuration.

Configuration: /IRM/IPSPRO > Accrual and Settlement > Define Accrual Profile > Select Accrual profile and click Details > Flag the field "Internal AccrualAssign the same Accrual Profile to the IP Type for each user that needs to post accrual document as 'Internal Posting.'

Transaction IP New Functionality /IRM/IPxx2* IP Document Creation during Repricing Mass Processing

The IP document 'Reprice' function will detect any line items in the source documents which now became eligible for an IP document. The line items that change in value and the newly eligible lines get picked up while doing Mass Processing of IP documents via 'Reprice', and previously, any such newly eligible line items were only added to the existing IP documents; a brand new IP document was never triggered.

New functionality exists whereby new IP documents can be created for newly eligible line items during the repricing function of the mass processing jobs. To trigger this functionality, users will have to set flag 'Creation During Reprice' on mass-processing report selection-screens. Now, users will not have to initiate the 'Recreate' job again. Instead, the 'Reprice' job will perform that action. It will help the users to save time because they will not have to schedule separate jobs for 'Reprice' and 'Recreate' tasks.

Please note that this function does not work when repricing an IP document using the workbench.


OSS Note #17057661705063170499317049031704805170468117044721703858170375717032261703055170254617022661702233170198717016071700881170074017003611700351170017016990421698305169769316976221697596169753016973721696595169629816962971696007169589916956021695241169498216936281693614169356716934591693425169341416929581691207168983716878441686122

Agreement Grouping Fields Not Filtered in Agreement RulesError updating Agreement group during agreement mass change

Agreement Copy to an Agr request copies Revision reasonDeletion of a Claim not allowedReconciliation account error from value rule of attributeItem Partner Not Validated Against Sales AreaValid Owner Error in Agreement Header dataTerms of Payment validation error in Agreement

Incorrect error message in /IRM/GPR26 on selection criteriaIncorrect Agreement Log Display when making changes in rulesMember Type is not defaulted during Membership ListFirst column mapping issue in File Template UploadContext is not avilable for /IRM/IPCRASP in workspacesetl amt wrong when one of the company code accrual is -VE

Multiple currencies in Period overview of Agr summary reportVistex structure '/IRM/ESIPARHDR_TEXT0001' is missingShort dump in Product List Workbench in French/IRM/GML_TRADE_ORG_MEMBERS_GET not considering validity datePerformance and rules update issue during IP doc repriceKUNNR field value passed to Sales Order via Agr Workbench

Badi changes are not reflectingShort dump in French when running /IRM/IPPRAMEMaterial freely enterable in Transaction RegisterInterim settlement from the calculation run not workingBW Vistex IP Log KON extractors fail due to memory dumpsLong runtimes during mass process of claims and TR

Incorrect status display on calendar viewPrice Proposal Authorization Checks results in short dumpTree display issues in /IRM/GCMDSearch term not getting filled in condition header tableIncorrect error msg displays on Agr WB when entering priceIncorrect Settlement Status and final amount in PR IP docs

Primary partner refresh issue on items grid in claimsError Segments not passed in Agreement Request IDOCMembership Submission KONH-KOSRT not populated with MSNUMParticipant tracking - Inconsistent resultsClaim requests not displayed in calculation runIncorrect currency conversion while processing a claim

Fields missing in Worklist Search for Agr and Agr RequestEligible/Interim Settelment Blank in collective trackingShort dump when saving in Transaction Register / ClaimIssue with report /IRM/EPAT_ADDL_DESCR_DSP3_FILLDynamic Pricing Table Fields stored with empty Date elementsAgreement getting created without validity dates

IRMIPM 60D SP3: Release NotesThe following OSS notes have been included in Support Pack 3 of Release 60D

OSS Note DescriptionTransaction /IRM/IPARLOG does not work as expected/IRM/GCMD Membership List Time Limit ExceededDelete common tables from Composite


OSS Note #


OSS Note Description 1686173

1686505168555716856031685716168489516845171684532168380616839211683981168376516828021681974168114416799301679991167902216790421679291167876116785361678311167726416772731677400167749616767381676948167627516757661675767167595716760271674826167491616742251673675167352216731191673226167331216726691672855167286016721341672371 IP document created without line items for return orders

Incorrect entry in KWERT_n leads to short dumpAgreement changes on saveMass creation of BR docs from claims causes duplicate IP docClaim upload program performance issuesRules not updated when agr. terminated using agr. requestIssue with product hierarchy drop down list in price sheets

Tax base amount not filled in accounting documentsAttribute rules not being taken into account during creationParticipant deleted even if postings existPerform Authorization Checks before entering the transactionItem Pricing called twice in ClaimsDump when saving multiple agr. changes as collective request

Agreement not displayed when clicked on agr in Hierarchy TabVolume field (VOLUM) not determined when creating PricebookAgreement Req/Agreement first tab displays blankAll price sheets not copied when copying Agreement RequestBlank Screen when clicked on rules in the change logUpdate error when posting agreement request to agreement

Session times out when accessing change log on Agr Workbench/IRM/IP_AGR_REQUEST_READ is nt reading rules fr Coll Req.Agr Block profile customizing not recognizing valid fieldsIssue with key field groups in composite tracking screenIncorrect period description on the tracking screenPerformance issue in pricing complete for Claims

F4 help issue with Commision group in transaction registerInconsistent number of participation records on AgreementIssue with Agreement Request BSP Block ProfileIssues with message log in IP WorkbenchSAPSQL_ARRAY_INSERT_DUPREC error during Agreement workflowPerformance issue with Claim Update Call Function

Short dump in calculation run create mass programSettlement Calendar value incorrect on Participation recordAgreement request output idoc may result in errorsPrice record overlap message displayed for Agr. RequestClaim stage is not updated on settlement clearingCalculation run simulation issues

Issues during Unit of measure conversionDeleted Agreement allowed at itemBalance in transaction currency error whil performing stlmntNo Message Passed to IDOC when Partner Not FoundAccount Determination error in Purchasing RebatesMoving from Agreement Transaction to other Transaction-Dump

Currency and Reference Agr number field labels are missingBadi to modify claim data before agreement close outError in Plant validation in Material Cross referenceClaim Documents missing user statuses entries


OSS Note #



1671691167177816720731671429167114016711481670710167072816708401669476166821516677111667720166779816667601666915166691716669631667033166714016671441665533166363716625671661559166076716602151659775165997316600131659221165925616593311658943165896116582321658327165674016568631655960165609816561171655689165512716541351654137

Error when configuring deductions and credits field mappingScroll bar not available in agreement workbench general tabGCMA/GCMD Timeout ErrorsSwitching periods results in invalid participation messageTransfer issues with claim and Transaction RegisterUpdate termination during claim or TR transfer/resubmission

Submitted currency issue during claim uploadIncorrect reconciliation status is setAgreement BSP issue with release statusAuthorization check issues in IP document transactionsUnable to Release Membeship ListIssue with F4 help in composite mass process transactions

Incorrect values fetched in dropdown of Product ListShort dump when clicking 'Review Sheet' button in agreementField BUZEI_DM is missing in Deductions Field MappingClaim/Transaction Register Save goes into infinte timeAlv grid reduces with header compressedIssue with material determination in claim workbench

Membership History Loading IssuesClaim archive function not capturing partner informationDynamic Dates Issue in ADMPayer being determined even if it is passed from uploadCannot navigate to the agreement from agreement group WBClaim/TR - Change in behaviour of item pricing date over SP2

Agreement Texts not updated while mass processingUpdate termination when uploading a PC documentRuntime Error when updating a claimCannot update Partner field (KTONR) in Claim workbenchMaterial UOM is incorrectly determined in claim workbenchShort dump when populating IP CR doucment list

Screen Resize issue for Item details in ClaimsDocument Flow does not display all docs with SD BillingIncorrect price derived in FM /IRM/G_PRICING_COND_SCALE_GETRules tab is hidden but the rules processing still occursPerformance issue during price book creationDisplay profile leads to missing line item fields in claim

Agreement Request is not determining the agreementAccrual creation error due to FI number range conflictF4 value in items grid gets overwritten on different itemEHP6.0 compatibility checks- Generation errors - GlobalEHP6.0 compatibility checks- Generation errors - IPExtension profile fields missing in /IRM/GPR_RECORDS_POST

Update Termination when updating Claim / TR IMV dataIssue with copying an agreement to an agreement requestDUMMY14 field is showing up in Agr Request Search AdditionalIssue when deleting the setup table in vistex BWIncorrect entries in LIS during IP document recreation


OSS Note #



1653091165342416522611652655165183316511921649726164977116497781644055

Incorrect reverse accrual amount in document flowIncorrect header amount after changing item condition valueCancellation Document pricing should match cancelled docIssue in Navigation to Agreement from Membership for BRCalculation run can be created for all depcode code versions

Duplication check performance issue for header fields onlyCannot settle IP Documents with more than 999 itemsFlexible groups cause runtime errors in sales order/IP docsIssues when uploading price records with scalesIssues in participant close out in composite IPMissing additional attributes in matrix mapping

Rls Notes-FINALOSS Notes


Page 1 of 6

Agreement Request Upload/Download Functionality:

Agreement Request Upload/Download functionality is currently available in:

• Billbacks: /IRM/IPBBARUPL, /IRM/IPBBARM • Chargebacks: /IRM/IPCBARUPL, /IRM/IPCBARM • Sales Incentives: /IRM/IPSIARUPL, /IRM/IPSIARM • Sales Rebates: /IRM/IPCRARUPL, /IRM/IPCRARM • Purchasing Rebates: /IRM/IPPRARUPL, /IRM/IPPRARM • Business Register: /IRM/IPBRARUPL, /IRM/IPBRARM

Path to Upload/Download Functionality from Transactions

/IRM/IPXXARUPL & /IRM/IPXXARM: GoTo > Upload Agreement Request(s)). Using these transactions,

• Users can upload a file to create a completely new Agreement Request. • Users can upload a file to create multiple Agreement Requests at a time. • Users can upload a file to change any existing Agreement Request(s) as long as that upload file contains

specific Agreement Request number(s).

/IRM/IPXXARM: Extras > Upload/Download. Using this transaction,

• In order to enable Upload/Download option an Agreement Request should be in focus. • Users can download the focused Agreement Request only. • Users can upload a file to make the changes on the focused Agreement Request only.

/IRM/IPXXARM: Mass Process > Download. Using this transaction,

• Multiple Agreement Requests can be downloaded at a time.

Defining File Template:

In order to perform the upload and download actions, user needs to build a file template using transaction /N/IRM/IPARFTM. File template is mandatory to upload/download Agreement Requests.

Upload /Download are possible for following sections of Agreement Request data.

• Header • Partners • Dates • Rules • Scales

We can configure these sections using file template workbench.


Page 2 of 6

In the Section tab within File Template Workbench, user can specify the position of the section in Excel sheet by specifying either section indicator or start row value. Both section indicator and start row should not be entered.

If user specifies section indicators here, then each row in Excel should start with corresponding section indicator.

Start Row and End Row position can be used only for single document upload/download. For mass upload/download user should specify section indicators.

Field mask column in Mapping tab of File Template Workbench is enabled for few fields that require value conversion. To avoid conversion errors user should fill this field mask as shown in the screenshot below.

Each parent section (Header, Rules) can have multiple child sections (Partners, Dates, Rules). If user wants to add a new section to file template, user should add keys field of current section and its

parent section.

Parent Section (Keys) Child Section Header (KNUMA_AG, ARNUM, PQNUM, DRNUM) Dates, Partners, Rules

Rules (KNUMH, KOPOS) Scales


Page 3 of 6

For example, if user wants to add a Rules section then user has to add key fields of rules (KNUMH + KOPOS ) + its parent section (Header) key KNUMA_AG to the file template.

In create case, key fields of every section should be empty except KNUMA_AG – header key field. User can

fill this value from number range object. If user is specifying number range value for KNUMA_AG in header section then user should fill same value for all child section (Every child section has its parent section keys - KNUMA_AG). Alternatively, KNUMA_AG can be left empty to allow the system to assign the Agreement Request number.

Upload file format:

Please consider below points when doing change to an existing agreement request.

Change:

In change case, parent section (Header/Rules) key fields should be filled. Otherwise user considers this as create case.

In change case, user can create new child sections, such as adding new rules, dates, partners, or scales. In this case, for new row we should fill corresponding parent section keys. For example, if user wants to add a new partner to existing Agreement 1, then user should fill KNUMA_AG value of new partner row with 1. Similarly, if user wants to add new scale to existing rule, then user should fill KNUMH and KOPOS (parent section keys) in scales section.

When the user tries to change an agreement request and if the entire agreement request is downloaded as

it is, make changes and upload it. This is called offline maintenance.

Delete:

Users have deletion indicators for each section. To delete a row users need to include deletion indicator field in File Template Workbench for each section, then set the corresponding row deletion indicator value to ‘X’ and upload.

Multiple Agreement Requests:

Section title should be mentioned in first column for multiple agreement requests to understand the data for which section it corresponds to.

Note: The key fields must remain unchanged so that the target rule can be found when uploading. A limitation exists that the key fields are unable to be locked from change in Excel after downloading. Do not change the key fields as this will result in undesired results when uploading.


Page 4 of 6

File Template (IPARFTM) - Screenshots of Mapping section:

Header

Dates


Page 5 of 6

Partners

Rules


Page 6 of 6

Scales

Sample Files

See attached.

Sheet1

External descriptionAgreement RequestAgreement Request TypeAgreement typeAgreement StatusDescription of agreementValidity periodValidity periodRelease statusAgreementReference AgreementOwner RoleReason CodeDivisionStatusSales OrganizationDistribution ChannelCurrency

HeaderUPLOAD AGRZSP8ZBBZEnd User Contract01/31/201201/31/203000300010USD

Agreement RequestDate TypePlanned Start DatePlanned End DatePlanned DurationUnitActual Start DateActual End DateActual DurationUnitDelete

DatesCLRB03/31/20301.00DAY1.00DAY

DatesCRCT04/09/201205/08/201230.00DAYDAY

Agreement RequestPartner functionCustomerPerson numberUnloading PointDeleteHierarchy Assignment

PartnersAA101566

PartnersPY101573

Agreement RequestApplicationCondition TypeTableCondition TableValid FromValid ToCondition record no.Sequent.no. of cond.AgreementSales OrganizationDistribution ChannelMaterialRateCustomerPayerCustomerDeletion Indicator

RulesVZSDD96401/31/201201/31/2030101566

RulesVZSDD89001/31/201201/31/2030300010101885

RulesVZBEA89201/31/201201/31/2030300010VE-10120,000.00

RulesVZSDP89201/31/201201/31/2030300010VE-10130.00






DatesRENW01/02/203001/31/203030.00DAYDAY


PartnersAA101566

PartnersSP101089

PartnersPY101573

PartnersSH101563


RulesVZSDD96401/31/201201/31/2030101566

RulesVZSDD89001/31/201201/31/2030300010101885

RulesVZBEA89201/31/201201/31/2030300010VE-1012,000.00

RulesVZSDP89201/31/201201/31/2030300010VE-10130.00

Sheet2

Sheet3

Sheet1






DatesRENW01/02/203001/31/203030.00DAYDAY


PartnersAA101566

PartnersSP101089

PartnersPY101573

PartnersSH101563


RulesVZSDD96401/31/201201/31/2030101566

RulesVZSDD89001/31/201201/31/2030300010101885

RulesVZBEA89201/31/201201/31/2030300010VE-10120,000.00

RulesVZSDP89201/31/201201/31/2030300010VE-10130.00

Sheet2

Sheet3

Agreement Upload/Download

Page 1 of 5

Agreement Upload/Download Functionality:

The Agreement upload/download functionality that is currently available in:

• Billbacks: /IRM/IPBBAGUPL, /IRM/IPBBASP • Chargebacks: /IRM/IPCBAGUPL, /IRM/IPCBASP • Sales Incentives: /IRM/IPSIAGUPL, /IRM/IPSIASP • Sales Rebates: /IRM/IPCRAGUPL, /IRM/IPCRASP • Purchasing Rebates: /IRM/IPPRAGUPL, /IRM/IPPRASP • Business Register: /IRM/IPBRAGUPL, /IRM/IPBRASP

Agreement upload/download paths from each transaction:

IPXXAGUPL & IPXXASP (GoTo -> Upload Agreement(s)): Using these transactions

• Users can upload a file to create a completely new agreement • Users can upload a file to create multiple agreements at a time • Users can upload a file to change any existing agreement(s) as long as that upload file contains specific

agreement number (s)

IPXXASP-> Extras -> Upload/Download: Using this transaction,

• In order to get this Upload/Download option enabled, an agreement should be in focus • Users can download the focused agreement only • Users can upload a file to make the changes on the focused agreement only

IPXXASP-> Mass Process -> Download: Using this transaction

• Multiple agreements can be downloaded at a time using this download option

Defining File template:

In order to perform this upload and download actions, user needs to build a file template using the T-Code /N/IRM/IPAGFTM. So File template is mandatory to upload/download agreements.

Upload /Download is possible for following sections of agreement data.

• Header • Partners • Dates • Rules • Scales

User can configure these sections using file templa

IRMIPM 60D SP3: Release Notes - Vistex, Inc · See the Release Notes under the Period Profile area...

Documents

Transcript of IRMIPM 60D SP3: Release Notes - Vistex, Inc · See the Release Notes under the Period Profile area...