irmipm 60c: release notes - vistex, inc · 2015-01-13 · example of a change: you change material...

Area Type of Change Transaction Code Topic Changes

ADM New Functionality /IRM/IPGADM Authorization A new authority object V_GB_AUTDM is delivered which is used to

control ADM processing by Function and Action. The input to the

authority object is the Function to be performed and the triggering

Action.

ADM New Functionality /IRM/IPGADM Customer Hierarchy SAP Customer hierarchy changes can be tracked with this feature,

and IP documents can then be created or re-priced based on the

Customer Hierarchy changes.

ADM New Functionality /IRM/IPGADM Index Profile Index Profile is basically a combination of one or more condition

index tables. It provides dynamic selection of condition records

(rules) which were changed.

Index profile can be used to track agreement rules. Select Index

Profile in ADM for repricing IP Documents for any changes in

Agreement Rules. Index Profile can also be used to 'adjust'

agreement rules.

ADM New Functionality /IRM/IPGADM IP Hierarchy IP Hierarchy changes can be tracked by adding 'Save Changes' in IP

Hierarchy type configuration. All changes will be stored in table

/IRM/IPHIERCL. ADM takes data from this table to prepare Source

records that can used to find target IP documents for repricing.

ADM New Functionality /IRM/IPGADM Master Data Track Master data changes (Customer/Vendor/Material) and re-price

IP documents with this feature based on the attribute and the

changed-on date entered by the user. Changes are tracked based by

maintaining characteristics (Table AUSP).

Example of a change: You change Material A from Material Group X

to Material Group Y, so you now need to reprice the IP documents

with Material A on them, because your agreement has Material

Group X pricing on it which material A is no longer eligible for and

now is eligible for Material Group Y pricing. An agreement cannot be

"repriced" , but an agreement rule can be adjusted using ADM. The

characteristic which needs to be tracked needs to be present in

customizing table /IRM/TGADCHAR.

IRMIPM 60C: Release Notes

Vistex, Inc. of 43 Last Modified: 8/25/2010



ADM New Functionality /IRM/IPGADM Membership Now the changes on the Membership can be captured on the

agreement for that GPO. A new condition record is created for the

GPO rule on the agreement is created by delimiting the record on the

membership release date. This will be commonly used to trigger

output for the change to a membership list when that membership

list is present on an agreement in the form of a GPO eligibility rule.

GPO A --> 1/1/09 - 12/31/09 (original record - before change)

------------------------

GPO A --> 1/1/09 - 11/14//09 (old record w/ delimited date)

GPO A --> 11/15/09 - 12/31/09 (new record because member was

added)

At this point, can trigger notification to the wholesaler with the

change to the membership list

ADM New Functionality /IRM/IPGADM Price Types In some cases, resubmissions will be triggered internally, without

being prompted by a distributor (e.g. a Medicaid Claim). When a

price type is changed, there is an obligation to send a resubmission

back to the submitter. This can be done through Automated Data

Maintenance (ADM) as many claims may need to be resubmitted

simultaneously. When a price type changes, the user has to identify

the claims that need to be resubmitted and initiate a claim

resubmission creation from ADM. This can be a collective or

individual resubmission.

As of now you can only create one to one or one to many

resubmissions using ADM but many to one resubmission is not yet

provided.

ADM New Functionality /IRM/IPGADM Vendor Hierarchy Vendor Hierarchy changes cannot be tracked with standard ADM tool

but this can be achieved by user exit in Vendor processing

Agreement Fix /IRM/IPxxASP Agreement Postings Previously, IP Items were not being fetched in case of Agreement

Posting Amounts to be fetched from LIS tables according to

configuration settings for the purpose of Claim creation from

agreements; this has been fixed.




Agreement Fix /IRM/IPxxASP Participation Previously, if a deployment code was locked by the Participant

transaction and you attempted to create an agreement which was

tied to the deployment code, the rules may no longer be displayed if

a lock issue was encountered. Now the rules will always appear

despite the deployment code being locked.

Agreement Fix /IRM/IPxxASP IDOC Various issues were corrected in the Inbound Agreement Idoc.

Agreement Fix /IRM/IPxxASP Rules Previously, the Set Values function in the Agreement was not working

correctly; this has been fixed.

Agreement New Functionality /IRM/IPxxASP Close Out After the expected accrual and actual accrual have been posted, you

can close out at the spend type level or you can close out at the

agreement level. This means you want to take the difference

between the expected and actual accruals and zero it out. It creates

a claim for the difference; it is an accounting entry. When you

choose to close it out, it will give you a pop-up and ask you what

claim type you want to use. If you close out at the agreement level,

it changes the agreement status. Closeout process requires that claim

types are configured at the agreement type level and a condition

type is assigned for calculation of amounts.

Agreement New Functionality /IRM/IPxxASP Communication of

Changes - Change Package

View and Document View

The changes that are made in the agreement are stored in logs and

in the logs the changes for agreement or rules all will be tracked.

Logs are stored in 2 ways:

1.Change Package View

2.Document View

- Change Package View - Each Change(Each Save) becomes change

packages. it show all the changes in that package.

- Document View - Overall what is changed in an agreement.




Agreement New Functionality /IRM/IPxxASP Configurable Tabs Tabs for Agreements and Agreement Requests can now be

configured to change the sequence of how they appear on the GUI.

If tabs are selected on the configuration, only the tabs that are

selected display on the GUI. if nothing is selected on the

configuration, then all tabs appear on the GUI. User can also change

the tab Title by typing their own title in the Description column of

the configuration. User can also associate an icon to each tab by

selecting an icon from the icon name column of the configuration.

Agreement New Functionality /IRM/IPxxASP Field List The General Tab and the Settlement Tab can now be configured to

display only defined fields. You can configure an agreement type to

only display selected fields. If one field is selected, only that field will

appear on either the General or the settlement tab. If nothing is

selected in configuration, all fields will appear. Some fields are

comprised of more then one labels on the general or settlement tab.

E.g. If you select the field Settlement Type in configuration, it is

actually comprised of 4 labels(Settlement Method, Settlement Type,

Settlement Frequency and Settlement Calendar) on the Settlement

tab. All four fields will appear on the Settlement tab in the GUI but at

the same time, the General Tab will have no fields appearing. So care

needs to be taken to make sure all fields needed on each tab are

selected in the configuration, as if you configure fields for one tab

then the other tab needs to be configured also.




Agreement New Functionality /IRM/IPxxASP IDOC : Membership and

Product list explode

scenario

When creating the agreement IDOC, if it encounters a condition type

that is marked as “Membership” or "Grouping", the program will

explode the membership and include the individual customers in the

IDOC. It explodes them under the customers and product section of

the IDOC. Examples of grouping are customer groupings (again based

on membership) and product grouping (based on product list).

Condition record number is the link between the parent and child

node. All the exploded Child segments will have Parent condition

record number in KNUMA _SQ and $$xxxxxxx in KNUMH.

Agreement New Functionality /IRM/IPPRASP Authorization A new authority objects V_GB_PBPTY is delivered which is used

during price book processing for purchasing rebates.

Agreement New Functionality /IRM/IPxxASP Enhancement In function groups XIPCB, XIPBB, XIPSI, XIPCR, and XIPPR, a new user

exit has been delivered. EXIT_SAPLXIPxx_053 - Agreement - General

Data Display (PBO)

This exit can be used to export data to customer screen which is

replacing "General" Data tab of agreements.

Agreement New Functionality /IRM/IPPRASP Enhancement In function groups XIPCB, XIPBB, XIPSI, XIPCR, and XIPPR, a new user

exit has been delivered. EXIT_SAPLXIPxx_054 - Agreement - General

Data Display (PAI)

This exit can be used to import data from customer screen which is

replacing "General' tab of agreements.

Agreement New Functionality /IRM/IPxxASP Enhancement In the BADI /IRM/BADI_IPxx_ASP, the following new methods have

been added to influence Agreements:

BEFORE_COPY - used during copy of one agreement to another

ITEMS_FILL - used to enhance item view entries.

Agreement New Functionality /IRM/IPxxASPM_WS BSP Redesign The Agreement BSP has been redesigned using the CRM UI paradigm.

Agreement

Request

Fix /IRM/IPxxARM Measures Previously, there were errors that were occurring while executing

measures from an Agreement Request; this has been fixed.




Agreement

Request

New Functionality /IRM/IPxxARM Configurable Tabs For Agreement Request, the configurable tabs is driven by the

configuration defined for the corresponding agreement type. E.g. If

an Agreement Type is configured to display only five (5) tabs, then

the corresponding Agreement Request Type will also only display

those five (5) tabs.

Agreement

Request

New Functionality /IRM/IPxxARM Field List For Agreement Request, the Field List configuration is driven by the

configuration defined for the corresponding agreement type. E.g. If

an Agreement Type is configured to display only five (5) fields, then

the corresponding Agreement Request Type will also only display

those five (5) fields.

Agreement

Request

New Functionality /IRM/IPxxARM IDOC : Communication of

Changes

The Agreement request can trigger IDOC output that captures the

difference of the state of the agreement before the request and after

the change on the request. When triggering IDOC output it triggers

function module (/IRM/IP_IDOC_OUTPUT_AGRQST_CHN) for the

IDOC output capturing the changes only. This IDoc is intended to

track the changes on request which is created for an existing

agreement. Then this IDoc pulls up rules which were changed on

request with comparison to rules on agreement at the time of

creation.

Agreement

Request

New Functionality /IRM/IPxxARM_WS BSP Redesign The Agreement Request BSP has been redesigned using the CRM UI

paradigm.

All Applications Fix n/a Accessibility Many user interface changes have been made to be 100%

Accessibility compliant. Examples of accessibility are having help text

for each icon and not using the same icon twice on a screen. You

may notice small changes in the transaction screens.

Claim Fix /IRM/GCR23 Performance Performance enhancement changes have been included.

Claim Fix n/a Performance Performance enhancement changes have been made in the inbound

Idoc processing program.

Claim Fix /IRM/GCRM Resolution When resolution contains two IP actions, the first action is executed

successfully and the second one results in an error.




Claim New Functionality /IRM/GCRM Checks If there are checks carried out and you want to get into the claim to

view any errors, it sometimes could take a while to pull up as the

items will have to be processed again. So now there is now an option

to view the last claim's check log for the items of the claim while in

display mode. You do not have to re-execute the checks to see the

errors. The check message log is created when saving the claim and

is stored so that is can be pulled back up without re-executing the

checks. There is a button available on the items grid now to view the

last messages for items when it was saved.

Claim New functionality /IRM/GCR37 Claim Validation This new transaction is similar to /IRM/IPBB37 though only provides

claim specific data; no IP related data is shown. The items grid here

is similar to items grid in claim WB. All the claim operations provided

in /IRM/IPBB37 are available from /IRM/GCR37 also.

Claim New Functionality /IRM/GCRM Configurable Tabs Tabs in Claim Documents can now be configured for a user defined

specific sequence. There is a View column in configuration with

Header and Item as selections. If Header level tabs are selected in

configuration, only tabs that are selected are displayed. If no tabs are

selected, then all tabs are displayed on the GUI. Tabs at Item level

can also be selected in configuration to be displayed in a user defined

sequence. If no tabs are selected at the item level, then all tabs are

displayed. The item level configuration drives the item level tabs on

the GUI when the user highlights the items and click on the Item

Details icon. If tabs are selected in configuration for the Item Details

then only the selected tabs appear in the drop down of the Item

detail button of the GUI. If no tabs are selected at the item level then

all tabs are displayed.




Claim New Functionality /IRM/IPBB37 Customer addition fields We have provided customer addition structures in header structure(

/IRM/S_GCRHDR_VLDCA and /IRM/S_IPBBHDR_VLDCA) and

customer addition item structure( /IRM/S_GCRITM_VLDCA and

/IRM/S_IPBBITM_VLDCA ). Customer can add new fields other than

what we already deliver to these structures and they will be available

in the transaction. The data for these customer addition fields can be

enhanced using new BADI /IRM/BADI_IPBB_VLD methods header_fill

and item_fill.

Claim New Functionality /IRM/GCR25 Mass Processing Claim at

Item Level

There is a new transaction known as Mass Processing Claim at Item

Level. The transaction code is /IRM/GCR25. This enables you to

process line items only in batch and can decide what lines to process

or reprocess.

Claim New Functionality /IRM/GCRM_WS More Button to add to

Worklist

On Claims BSP, you can add claims to a worklist by using the More

Button and retrieve the Worklist from the Saved Search Dropdown.

Claim New Functionality /IRM/GCRM_WS BSP Redesign The Claim BSP has been redesigned using the CRM UI paradigm.




Claim New Functionality /IRM/GCRM Packages There is a new tab in the Claim Workbench called Packages; there is

configuration for packages in the Claim Type. If you don't want to

see this tab, you can turn it off in configuration.

The concept of the Package arose because there sometimes would

be a lengthy processing time of a claim if there were a lot of lines on

the claim. So when Packages are enabled on a Claim Type in

configuration, a parent claim is created without any line items on it

in, but has multiple child claims, also known as Packages. The

Packages are created with line items. Within configuration you can

specify the package size which drives how many line items will

appear in each package. For example, a claim with 50,000 lines on it

can be broken up into packages containing 5,000 lines on each. So

you can look at one package at a time via the Parent claim; the

Parent claim is the Source document that is used to create the IP

document. When in the Claim Workbench, Packages never show up

in a search only the Parent Claim shows up. Packages can accrue

separately and can settle separately.

- For additional information, go to the Package Processing

attachment.

Claim New Functionality /IRM/GCRM Packages Configuration:

1. Activate packages and set package size in claim type configuration

Settlement Parameters:

1. Select "Settle by Source Document" flag in settlement parameters

to ensure all packages are settled on same settlement document.

Note: Settlement transaction selection must select all child claims.

Claim Creation Process:

1. Packages can be created only from claim upload (GCRUPL)




Claim New Functionality /IRM/GCRM Packages Processing Packages:

1. A new tab called "Package" gets created in the header of the

parent claim. This lists all the packages (child claims) created for the

parent claim. When one package is selected, the lines for that

package are displayed in the item grid.

2. Whenever claims are searched by either the parent claim or the

child claims, only the parent claim is returned in the worklist. The

child claims are show in the Packages tab of the parent claim in focus.

3. Packages Tab displays when a Claim is detected as a Parent Claim.

Package Screen contains the total number of lines with adjustment

code, rejection reason, invalid material, etc. by package. Click on a

Package in the Package Screen to display items in the line item grid.

Details from only one Package at a time will display in the Claim line

item grid.

4. Posting is done at Parent Claim level

Claim New Functionality /IRM/IPxx37 Packages Validation/Posting

1. Select package and click "Navigation" icon . This navigates to the

claim validation (IPBB37) transaction.

2. Subsequent claim processing such as Posting and Resolution must

be triggered from the Claim mass processing program. or claim

validation transaction. These functions will not be possible from the

workbench.




Claim New Functionality /IRM/IPxxM Packages IP Documents

1. One IP document is created for each child claim.

2. Each IP document is accrued individually.

3. Care needs to be taken to ensure that all IP documents are

selected for settlement together, so that they are settled collectively

on a single settlement document (further dependent on settlement

parameters). To select all IP documents for settlement, you can also

enter parent claim number in the source document field of selection.

4. System will permit individual settlements from the billback

workbench; if this is to be prevented systemically, custom checks

need to be written.

Claim New Functionality /IRM/GCRM Resubmission There are two new options in the Claim Workbench: Transfer and

Resubmission. A Transfer copies line items from one claim to a new

one. Resubmission creates a new claim from the selected items of

the source claim and calculates the delta line item value. It

references the original document and determines the already settled

amount on the line item. There is a predelivered formula to calculate

the delta. A new claim header "Category" field indicates if a claim

results from a transfer or a resubmission; a reference document field

stores the source document number.

- For additional information, go to the Claim_Claim Resubmission

attachment.




Claim New Functionality /IRM/IPxx35 Resubmission of the IP

Document

In previous releases, a re-transmission of the parked document was

possible but a resubmission of select lines was not provided as

standard. In this release, a true resubmission process is available

using transaction code /IRM/IPxx35. There are two new functions: a

Resubmit button on the ALV line item grid and Resubmission History

Display menu pull-down option. With the Resubmit button you can

select lines for resubmission and the system will generate output for

only the selected lines. A pop-up displays the list of selected IP

document lines being resubmitted. The Display Resubmission menu

option shows the history of the resubmitted items. It stores a

version of each output; it displays which lines were attached to each

resubmission.

Claim New Functionality /IRM/IPBB37 Enhancement In the BADI /IRM/BADI_IPBB_VLD, the following new methods have

been added to enhance header and item data In claim validation :

HEADER_FILL

ITEM_FILL

Clauses and

Templates

New Functionality /IRM/GCLM BTF Editor The Vistex approach to contract authoring is considered to be an

'inside-out' approach; it is fully integrated with SAP and is there to

actually generate the document, not use a separate tool to do

contract authoring and then integrate it with SAP ('outside-in'

approach). There is only one text editor as of this Enhancement

Pack, it is known as the BTF Editor (Business Text Framework Editor).

This Editor is standard to SAP. The HTML editor no longer exists.

Clauses and

Templates

New Functionality /IRM/IPxxASP Checkout Versions Have the ability to check out a clause version on the agreement in

change mode only. Then while in change mode, only the user who

checked it out should be able to check the version back in. However,

if the user who checked it out is in display mode or has left the

agreement entirely, other user's given the proper authorizations

would be permitted to check it back in via display mode.




Clauses and

Templates

New Functionality /IRM/GCLM

/IRM/GTPM

/IRM/IPxxASP

Comparison The split screen comparison has been eliminated. Now when

choosing compare (clauses and templates), it will use the native

version of Microsoft Word to compare using Word's basic compare

function (Review --> Compare). Before launching into Word, the user

must make their selections as to how they would like to view the

items to be compared:

(1) Target and Result it shows the Compared document and the

Revised document and it defaults the Word Source document to

"Show Revised".

(2) Source and Result it shows the Compared document and the

Original document and it defaults the Word Source document to

"Show Original".

(3) Result it shows the Compared document and it defaults the Word

Source document to "Hide Source Document".

(4) "_" Display Source, Target and Result documents it shows the

compared document, the Original document and the Revised

document and it defaults the Word Source document to "Show

Both".

Clauses and

Templates

New Functionality /IRM/GTPM Hierarchical View The hierarchical view of the template structure now enables the user

to reorder clauses simply by dragging and dropping them within the

structure. There are three different drag and drop options: UNDER,

ABOVE and BELOW. The UNDER option will place the clause under

another as a child. For example, Clause A (Level 1) is dropped under

Clause B (Level 2), so Clause B will now be placed at Level 1 and

Clause A will now be placed at Level 1.1.

Clauses and

Templates


/IRM/GTPM

New Columns on Clause

Tab in an Agreement

There are two new columns on the clause tab in the agreement: Risk

Factor and Negotiation Status. These are informational fields only

and have their own IMG nodes in /IRM/IPSPRO. The Risk Factor pulls

into an agreement from the Template Workbench for each

clause/template that has a risk factor. Negotiation status is editable

in agreements only it is by design; this field is not present in the

Template Workbench.




Clauses and

Templates


/IRM/GTPM

/IRM/IPxxASP

Notes Notes can be created and maintained for each clause. The notes can

be entered on each clause in the Clause Workbench or notes can be

entered on each clause once pulled into an agreement. Clause notes

will not carry forward to the clause notes column in the agreement;

notes maintained in Clauses/Templates Workbench are specific to

Clause/Templates Workbench. When notes are added to the Notes

Comment column (field: COMNT) in the agreement, it will add the

notes to each clause and they can all be displayed by clicking on the

Notes icon for each clause. The Notes Comment column (field:

COMNT) in the grid displays the most recent note.




Clauses and

Templates

New Functionality /IRM/GCLM Price Sheets Anchor Price Sheets can be tied to other price sheets. The purpose of

this is so the rules dynamically pull into the clause structure display

within the Agreement Workbench; this happens when it has a clause

with Price Sheets assigned to it and there are those corresponding

rules on the agreement.

The Anchor Price Sheet and the Additional Price Sheets are assigned

on the clause itself (Price Sheet tab in the Clause Workbench).

Assigned Price Sheet fields can be configured at the Clause Type Level

in configuration. If this configuration is not maintained, Rate is

shown as the default field, which appears to the right of the Key

Field(s). The Key Field (ex. Partner) appears as the far left column,

then the Anchor Sheet followed by all additional price sheets from

left to right. In general, all Key fields are displayed first and then

configured fields if any.

For instance, say the Anchor price sheet has Sales Organization,

Distribution Channel and Material on it and the user wants to add

Rebates as an additional field it gets added as an additional sheet in

the form of a column. Anchors key in price sheet so all data will show

up in one line when referencing additional price sheets within a

clause (i.e. tier pricing on one line).

Clauses and

Templates

New Functionality /IRM/GTPM Template Versions The Versions tab is no longer present in the Template Workbench

transaction; the version information is now incorporated onto the

General tab in the Template Workbench transaction. If trying to save

a new version from not the latest version in the series, it will not

allow the user to save changes from an outdated version. For

example, if the user has Version 1 and Version 2 and are trying to

create Version 3 from Version 1, it will not allow the user to and

should tell the user to create it from Version 2.




Clauses and

Templates

New Functionality /IRM/IPxxASP Workflow for Clauses Clause workflow for legal approval is separate from the agreement

workflow for approving the agreement, which is controlled by the

Life Cycle Profile. The Phases and Phase Steps allow for as many

workflows as desired. The Phase and Phase Step are found in the

Agreement configuration for Clause Types. The Phase Step can

trigger a step within a phase which triggers workflow; it will trigger

workflow every time the clause on the agreement is modified. It will

populate the phase and phase step fields on the clause and it will

update the current phase and phase step on the General tab on the

agreement. The Lifecycle Flow will show the phase. For example, if

you want to trigger workflow for a particular agreement type, clause

type A, you would assign a phase and phase step to it in the

Agreement configuration so that any time clause type A is modified,

it triggers workflow on that particular agreement type.

Composite IP Fix /IRM/IPxxCIP

/IRM/IPxxCCP

Enhancement Previously, user functions were not displayed during tracking. Even if

a user function was displayed, a run time error occurred upon

execution of the function; this has been fixed.

Composite IP Fix /IRM/IPxxPA Participation Previously, when using Agreements as the participant type, when you

select all the entries in the participation workbench including the

parent node and go for Mass maintenance, the selected entries are

shown ‘twice’ in the popup. After saving the changes made in the

popup, the field ‘KNUMA_AG’ of table /IRM/IPxxPART was incorrectly

updated without leading zeros. Both of these issues were corrected.

Composite IP Fix /IRM/IPxxPA Participation Previously, in the participant transaction, selection screen values

were not retained when switching to change mode; this has been

fixed.




Composite IP Fix /IRM/IPxxCIP Subcomponent Previously, there were issues in subcomponent characteristics

assignment in composite. For example, when multiple versions were

maintained for a deployment code, the system fetched the

characteristics for only the first version; this has been fixed.

Composite IP Fix /IRM/IPxxCIP Subcomponent The Composite tracking screen stopped showing sub-component

values; this has been fixed.

Composite IP New Functionality /IRM/IPPCRM Calculation Log Table -

Deployment Code

Generation

Must use the Deployment Code table to support the Calculation Run

Workbench. This will enable the following: can extract composite

data to BI and can fetch data from postings for prior time period

without recalculating. Also, this will resolve the standard SAP table

limitation of ~4,000 bytes as the data will now be stored in separate

Deployment Code tables.

Will generate transports upon creation. As the deployment code

tables are activated and generated, the common tables become

obsolete. As they are activated, tables for each deployment code will

include the following: Component Table, Supplementary Table,

Subcomponent Table, Calculation Run Table, Calculation Run

Supplementary Table, Calculation Run Subcomponent Table. You can

backup and restore data which is extremely beneficial when deleting

fields from a deployment code. When you add a field to a

deployment code, it will automatically update the table with that

field.


OSS Note

OSS note 1398584 is provided for instructions on moving data from

the Calculation Run tables to the new Calculation Log tables. It is

extremely important to follow the instructions so that the existing

data is not lost.





Postings Allow

There is optional configuration for version postings once the

deployment code exists. This configuration is located in Define

Deployment Code --> Allowed Versions. The options for postings

allowed are as follows: Posting Allowed only if Dep. Code Table

Exists, Posting Allowed and Data will be Frozen, Posting Allowed

(Dep. Code Table is Optional) or Posting not Allowed.

Composite IP New Functionality /IRM/IPPCRCMP Calculation Run Creation -

Mass Processing

Able to create calculation run number through mass processing

through /IRM/IPPCRCMP transaction.

Composite IP New Functionality /IRM/IPPCRPMP Calculation Run Posting -

Mass Processing

Able to process the calculation run postings through /IRM/IPPCRPMP

mass process transaction.

Composite IP New Functionality /IRM/IPPCRM Calculation Run

Workbench - Accounting

Tab

It shows how the accounting will take place (accounting done ahead

of time). Will show accounting at the Accrual, Interim Settlement

and/or Settlement levels for each participant (where applicable).


Workbench - Allocation

Tab

Can see all IP Documents with Participants that have assigned values

(Accrual, Interim Settlement and Settlement).


Workbench - Configurable

Tabs

Can now define the sequence of tabs for a specific calculation run

type in configuration and see how they appear on that calculation

run type in the WB.


Workbench - General Tab

The column layout adjusts when relevant for settlement or accrual.


Workbench - New

Transaction Code

A new Calculation Run Workbench transaction code is being

introduced, /IRM/IPPCRM. The calculation run is the result of what

was done in composite over a period in time. Calculation runs are

scheduled and run automatically, the user would go into the

Workbench to see what was done over a period in time.


Workbench - Posting

Able to process Accrual, Reverse accrual, Interim settlement, Reverse

interim settlement and settlement postings through calculation run

workbench transaction /IRM/IPPCRM.





Workbench - Results Tab

The results pull from the Collective Processing transaction

(/IRM/IPxxCCP). The screen is identical as it pulls from the Collective

Processing configuration.


Workbench - Status Tab

Able to set status in a calculation run workbench.

Composite IP New Functionality /IRM/IPxxCCP

/IRM/IPPCRPMP

Company Code Fill from

Accounting Level

The company code will fill from the accounting level, either

Subcomponent Deployment Code level or IP Document Level. There

are three options to do accounting: Deployment Code level,

Subcomponent Deployment Code level and IP Document Level.


/IRM/IPxxCIP

Component Group There is a screen for component group including a userexit. It

promotes reusability of components, allowing the same component

to be used in multiple deployment codes.


/IRM/IPxxCIP

Enhancement In function groups XIPCB, XIPBB, XIPSI, XIPCR, and XIPPR, a new user

exit has been delivered. EXIT_SAPLXIPxx_056 - Period to Date -

Mapping Where Clause Enhance

This exit can be used to modify the mapping where clause in

participant tracking transactions. Users can also stop the selection

process by marking C_STOP_MAPPING as 'X'.


/IRM/IPxxCIP


exit has been delivered. EXIT_SAPLXIPxx_057 - Current Period -

Mapping Where Clause Enhance

This exit can be used to modify the mapping where clause in

participant tracking transactions. Users can also stop the selection

process by marking C_STOP_MAPPING as 'X'.


/IRM/IPxxCIP


exit has been delivered. EXIT_SAPLXIPxx_058 - Calculation Run

Additional Data PBO

This exit can be used to export data to the customer screen in

calculation run workbench.





/IRM/IPxxCIP


exit has been delivered. EXIT_SAPLXIPxx_059 - Calculation Run

Additional Data PAI

This exit can be used to import data from the customer screen in

calculation run workbench.


/IRM/IPxxCIP


exit has been delivered. EXIT_SAPLXIPxx_060 - Period to Date -

Modify Claim Document

This exit can be used to modify the claim document before the claim

creation dialog from collective tracking and calc. run workbench for

period to date.


/IRM/IPxxCIP


exit has been delivered. EXIT_SAPLXIPxx_061 - Current Period -

Modify Claim Document

This exit can be used to modify the claim document before the claim

creation dialog from collective tracking and calculation run

workbench for current period.


/IRM/IPxxCIP

Enhancement In function groups XIPCB, XIPBB, XIPSI, XIPCR, and XIPPR, you will find

a new user exit EXIT_SAPLXIPxx_062- Multiple Partners Settlement

Adjustment - PTD, however this user exit is not yet released for use.

Do not use as it is not supported.


/IRM/IPxxCIP

Enhancement In function groups XIPCB, XIPBB, XIPSI, XIPCR, and XIPPR, you will find

a new user exit EXIT_SAPLXIPxx_063- Multiple Partners Settlement

Adjustment - CPD, however this user exit is not yet released for use.

Do not use as it is not supported.





/IRM/IPxxCIP


exit has been delivered. EXIT_SAPLXIPxx_064 - Reverse Interim

Settlement - Period To Date

This exit can be used to determine the posting date for reverse

interim settlement. Users can also stop the posting and return back

messages.


/IRM/IPxxCIP


exit has been delivered. EXIT_SAPLXIPxx_065 - Reverse Interim

Settlement - Current Period

This exit can be used to determine the posting date for reverse

interim settlement. Users can also stop the posting and return back

messages.

Composite IP New Functionality /IRM/GMXFM Flexible Maintenance

Workbench - Anchor

There are two available Anchors: Key Figure and Time Period. These

Anchors allow you to maintain the data with that one specified key

figure or time period. When the Anchor is selected it should appear

in the header data above the grid - it should not be a column.


Workbench -

Expand/Collapse

Aggregation Levels

Flexible Maintenance now has its own transaction, /IRM/GMXFM,

and will now appear in a Workbench format. Flexible Maintenance is

truly a planning tool allowing for multiple ways to maintain complex

scenarios.

The results can now expand and collapse. For example, the results

for a material group may be able to be expanded to show sub-

material group.





Workbench -

Expand/Collapse Columns

In the Flexible Maintenance Workbench, the results can now expand

and collapse. For example, the results may be configured to show

the past quarters numbers in a single column and then every month

since has its own column. By selecting the 'Quarter' column, you are

able to expand the results to show each month within that quarter in

its own column.

We can select Key Figures with Versions and Time Periods. There we

can find the “ Define KF Group” grid button, where we can group the

Key figures and in the result grid, you can see columns for these

groups. You can expand group columns by selecting button and

collapse them by selecting the button.

These group columns value is the sum of the all KF columns it belongs

to. This enables you to group the KF columns to show the sum and

can expand/collapse them.


/IRM/IPxxCIP

Formula Builder Pass / Take Back Structures in Formula Builder. Use S_SCCHAR_ARG-

ARG1, S_SCCHAR_ARG-ARG2, etc to fill the subcomponent

characteristics value for LOOKUP_SCOMP_TRACKING_AMT and

LOOKUP_SCOMP_TRACKING_QTY


/IRM/IPxxCIP

Hierarchy Evaluating Hierarchy at component mapping level. May want to

map hierarchies to specific key figures not to the entire version as

seen in deployment code configuration. Mapping Maintenance -->

Deployment Code to Matrix Map.

Composite IP New Functionality /IRM/IPPCRM Log Document The Composite Log Document allows for a snapshot of the IP

transactional data that essentially was used to post any Financial

Entries. This functionality will be available via the Calculation Run

functionality and is known as Composite Logs.

- For additional information, go to the Composite_Log Document

attachment.





/IRM/IPxxCIP

Lookup Table In /IRM/IPSPRO, when defining formulas in a Composite transaction,

there is now the ability to lookup any table. First declare

S_FIELD_RANGE-FNAME1, S_FIELD_RANGE-OPT1, S_FIELD_RANGE-

LVAL1, then in next step write lookup table formula for example

LOOKUP_TABLE( 'MARA', 'MTPOS_MARA', S_FIELD_RANGE ). Table

name, field name and S_FIELD_RANGE.

Composite IP New Functionality /IRM/GMXDM Matrix Document

Workbench - Propose

Changes to the Matrix

The Matrix Document Workbench is used to capture proposed

changes and send them through an approval process before the

changes are officially saved in the Matrix. This is independent of the

change log and shows the old value and the new value.

If the “Document Assn.” flag is selected in Matrix Type Customizing,

then those Matrix Types are eligible for creating Matrix Documents.

Then when Matrix data is changed in /IRM/GMXM and /IRM/GMXFM

transactions, upon saving a new Matrix Document is created. It is

similar to Change Documents. Each matrix document captures the

changes done at that point of time in the workbench. The Matrix

Document Workbench (/IRM/GMXDM) is to view all the documents

that are created for all matrices. There is no create mode in the

Document Workbench as they can be created only during the other

matrix workbenches.

A concept called Version Transition with approval process(status) has

been introduced, wherein, you can update this new value into the

matrix, but into different version, which will be specified in

customizing.

This process is done when a document is posted. You can select the

Post button and there you need to select the Version to which you

can save these changes.

After the document is posted, you cannot change the current values

and you can see the posted version in the header screen.




Composite IP New Functionality /IRM/GMXM Matrix Workbench -

Members Maintenance

In the /IRM/GMXM transaction, to enter into Members Maintenance,

go to Edit --> Members, it will no longer appear in the Matrix View

dropdown. Once within the maintenance screen, the Existing

Members now appear on the left side of the screen, the Search for

Members now appear on the top right side of the screen and the

Search Results now appear on the bottom right side of the screen.

So members can be added from the results by selecting a member(s)

and clicking on the add members button.

Composite IP New Functionality /IRM/GMXM Matrix Workbench -

Mode/View

The Matrix will now appear in a Workbench format using the same

transaction, /IRM/GMXM, it will no longer appear with the initial pop-

up selection window. Should not have the ability to switch into

Change mode in the main menu bar; should be able to choose

Change or Display mode within the main matrix search screen.

Transaction /IRM/GMXD is now obsolete.

Composite IP New Functionality /IRM/IPxxCIP Navigate to documents

from Subcomponent IP

documents/Source

documents

Navigation to documents from Subcomponent IP documents/Source

documents is now enabled for IP processing.


/IRM/IPxxCIP

Participation -

Components

Now have the option to Skip processing of a component and to Hide

a component for individual participants. If the component needs to

be hidden for all the participants, mark the 'Hide Component' flag in

the component assignment configuration. If component is skipped

for processing for the participant, the mapping, calculation formula

and the use exit is not evaluated.

Composite IP New Functionality /IRM/IPxxPA Participation -

Participation Validity

Rules Validity equals Participation Validity. You can now see

participation on the Performance tab for both auto-assigned and

manually assigned participants (as long as configuration is there).

Auto-assigns the validity for the Participation based on the Rules

Validity. As the Rule Validity changes, the Participation Validity

changes too. There is a user exit now is available to split the

participation auto assignment.





/IRM/IPxxCIP

Reusable Component In this release, the Template Deployment Code is being introduced.

For instance, a parent company has pre-defined components that

cannot be changed at local company levels. Then the local

companies can have components specific to them. Calculations can

be defined on the Template Deployment Code; they are defined once

globally and can be fetched. The template will also pull in the layout,

subcomponents and the mapping maintained. You have to make sure

that the template deployment code has been defined for the same

application as the one using it. In component assignment

configuration, you specify the template deployment code and

version.


/IRM/IPxxCIP

Settlement Adjustment You can now define the subcomponent settlement adjustment

formula when settlement is set to 'Settlement via Subcomponents'. A

user exit has also been provided for the same.


/IRM/IPxxCIP

Subcomponent

Characteristics

Subcomponent Characteristics can now pull in from LIS. Also, can

chose to exclude fields that you don't want to display.


/IRM/IPxxCIP

Tax Posting The tax posting is only relevant during settlement. The formula for

settlement now returns the settlement amount, GL account, tax code

and tax amount .

Composite IP New Functionality /IRM/IPxxCCP Tracking Dynamic selection for participant in tracking screen allows the user to

select only what is in the participation screen (if desired). Selections

can be based on additional fields too.


/IRM/IPxxCIP

User Exit for Where

Clause

A user exit has been provided to modify the where clause prepared

during component and subcomponent mapping. You can mark the

'C_STOP_MAPPING' flag if you do not wish to proceed with the

selection.

Composite IP New Functionality /IRM/IPCISHM Variants Ability to now create a variant with both regular and participant data

in it.




Document

Repository

New Functionality /IRM/IPxxASP

/IRM/IPxxARM

/IRM/GCRM

Active Document The Document Repository is a global application that stores external

documents and allows you to organize them based on your

requirements. There is now a Documents tab that appears in all of

the Agreement, Agreement Request and Claim Workbenches. The

Document Repository is configurable and can be turned off/on in

configuration. There are two storage options: Active and Stored.

The storage option is decided on at the time of upload. The Active

option keeps the document(s) open for changes as long as it is in an

editable format. For instance, a document uploaded in PDF format

will be uneditable even if stored as an Active version. The Stored

option keeps the document(s) closed and uneditable.

-For additional information, go to the Document

Repository_Configuration for Stored and Active Documents

attachment.

Document

Repository


/IRM/IPxxARM

/IRM/GCRM

Attributes Two of the main benefits of having documents in the repository are:

(1) the document is created and uploaded into the Agreement,

Agreement Request and/or Claim; therefore, it always remains with

the Agreement, Agreement Request and/or Claim; and (2) ease of

searching for documents because every document is assigned

attributes that can be manually assigned at the time of upload or can

be defaulted in by configuration.

Document

Repository


/IRM/IPxxARM

/IRM/GCRM

Stored Document There are two storage options in the Document Repository: Active

and Stored. The storage option is decided on at the time of upload.

The Stored document option keeps the document(s) closed and

uneditable.




GPR - IP New Functionality /IRM/GPRSPRO Extension Profile An extension profile is similar to view profiles but different because

the data from the extension profiles are stored on our tables (not the

SAP tables). You can include standard fields and extension fields in a

View Profile. Extension fields are the same concept as 'additional

fields' but they have a different append structure

(/IRM/S_GPRCR_EATR: Price Condition Extended Attributes.).

To add fields to the extension profile the following steps should be

done.

1) Add the required fields to /IRM/S_GPRCR_EATR structure through

an append structure.

2) Create an extension profile in the configuration under basic

functions -> pricing sales -> agreements

3) Assign the extension profile to the price sheet.

To use the extension profile fields in the formula , extension profile

fields should be added to view profile. It is not required to add these

fields to the view profile structure. When the fields are added to

/IRM/S_GPRCR_EATR, they are made available in the view profile.

Extension Profiles are defined here: /IRM/GPRSPRO --> Basic

Functions --> Define Extension Profile




GPR - IP New Functionality /IRM/GPR26 Index Profile For agreement index searching, the BSP agreement transactions now

use the same configuration as the GUI agreement transaction, which

is found under Pricing Agreements --> Set up Agreements -->

Agreement Rules --> Index based pricing

Index searching allows to search agreements based on common

characteristics like customer number, materials. Ex : Search all the

agreements where cust1 is present.

To enable this functionality the following steps should be done.

1) Create index table using OMA6 transaction.

2) Activate index table update.

3) Activate price sheets for index update. (Basic functions -> pricing ->

agreement rules ->index based pricing).

4) Create index profiles (Basic functions -> pricing -> agreement rules -

> index based pricing).

GPR - IP New Functionality /IRM/IPxxASP Language Specific in Alias

(Rules)

This functionality enables to assign language specific aliases to price

sheets. Price sheet alias will be displayed in the agreement rules

overview and rules tab.

GPR - IP New Functionality /IRM/IPxxASP New Scales Button When scales are enabled for a rule on the agreement, a new Scale

button is visible in the menu bar which allows you to

Expand/Collapse the scales in the main grid and on the review sheet.

This means scales can be viewed from the main grid for all rules in a

price sheet at one time instead of going into the scales screen for an

individual rule.




GPR - IP New Functionality /IRM/GPRPLM Policy Workbench -

Calculation

In the Policy Workbench, you can apply policies to condition records.

Currently when a policy is in violation, the policy itself can't do any

mathematical calculations. Now you can dynamically add fields to

condition records for the purpose of policy evaluation. You derive

the dynamic fields with the formula builder, and these field(s) are

only used in the policy. The dynamic field is assigned to the policy

not the condition record.

This release enables the use of temporary working fields in the price

policy definition. To use temporary fields in the policy workbench

formula builder, assign them on the calculation tab.

GPR - IP New Functionality /IRM/IPxxARM Proposal Profile Additional fields that are just for proposals and requests, but not

agreements and condition types. Allows you to keep certain fields

specific to the proposal on the proposal. Fields need to be part of the

extension profile.

Proposal profiles adds the fields to agreement request. TO add new

fields to proposal profile add fields to /IRM/S_GKONPCA structure

through an append structure. The following are configuration steps.

1) Create a proposal profile and add the required fields .

2) Assign the proposal profile to price sheet.

Proposal profile fields are only visible in the agreement request.

These fields will not be transferred to agreement. Extension profile,

view profile fields are visible on both agreement request and

agreement.

GPR - IP New Functionality /IRM/IPxxASP Upload Scales Scales now can be uploaded. A start and end column position must

be provided and scales must be loaded horizontally into the upload

file (i.e. start column = 10; end = 20).

Membership Fix /IRM/GMLM Checks The organization check was not working in spite of configuration

setting set to carry out the check; this has been fixed.




Membership Fix /IRM/GCMD Navigation Previously, you were unable to navigate to Sales Rebate agreements

from the Membership transaction although navigation to all other

application's agreements was possible. Now, there is the ability to

navigate to Sales Rebate agreements from the Membership

transaction.

Transaction IP Fix /IRM/IPxx21

/IRM/IPxx22

/IRM/IPxx23

Accrual/Settlement Previously, the update terminated during accrue and create in mass

processing because the field IPNUM was passed incorrectly to the

/IRM/IPBKPF table; this has been fixed.


/IRM/IPxx22

/IRM/IPxx23

Accrual/Settlement Previously, splitting the FI documents after every 999 lines of IP

documents only worked for Billbacks; now it works for all

applications.

Transaction IP Fix n/a Archiving Archiving programs were changed to improve performance.

Transaction IP Fix /IRM/IPxxM Checks Previously, an erroneous error message was received that the

component business register is not installed. Now, this error

message will no longer occur.

Transaction IP Fix /IRM/GVOFM Enhancement Previously, you were unable to create routines through

/IRM/GVOFM. Now, you can create routines through /IRM/GVOFM.

Transaction IP Fix /IRM/IPPCM Partner Communication Previously, you were not able to process a post-settlement

adjustment against an interim settlement document, but now this

has been fixed and you are able to do this activity.


/IRM/IPxx22

/IRM/IPxx23

Performance Performance enhancement changes have been included.

Transaction IP Fix /IRM/IPxxM

/IRM/IPxx23

/IRM/IPxx31

Settlement The balance in the transaction currency error message appeared on

final settlement; this has been fixed.

Transaction IP Fix /IRM/IPxxCSP

/IRM/IPxxVSP

Settlement Parameters Previously, the DELETE function code in Settlement Parameters was

missing; this has been fixed.




Transaction IP New Functionality /IRM/IPBBM

/IRM/IPCBM

Agency Business

Integration

The Agency Business Vendor Billing Document (VBD) and Customer

Billing Document (CBD) have been integrated into the Payback and

Chargeback applications.

- If Agency Business is used, the integration of VBD/CBD provides a

logistically equivalent document in form and function of the financial

document from the Vistex application. Financial documents are no

longer created directly from the Payback and Chargeback application,

but rather through the VBD/CBD documents which are instead

created.

- Integration points for VBD/CBD:

Accrual

Parking/Settlement

- For additional information, go to the Transaction IP_Agency

Business Integration attachment.

Transaction IP New Functionality /IRM/IPxx35 Log Document The Transaction IP Log Document allows for a snapshot of the IP

transactional data that essentially was used to post any Financial

Entries. In the transactional IP model this functionality will be

viewable via the /IRM/IPxx35 (replace xx with IP module i.e. SI, CB,

etc.) transactions provided in each IP module.

- For additional information, go to the Transaction IP_Log Document

attachment.




Transaction IP New Functionality /IRM/IPxx20

/IRM/IPxx21

/IRM/IPxx22

/IRM/IPxx23

/IRM/IPxx29

Parallel Processing All of the batch job transactions now have parallel processing

available (/IRM/IPxx21, /IRM/IPxx22 and /IRM/IPxx23). There are

two ways to mass process a large number of items: (1) Either select

'Dialog Task' so that dialog work-processes are used. (2) Or select

'Background Job' so that background work-processes are used. In any

case, following fields should be specified: Packet size: Selected data is

divided into packets, and each packet is given to each parallel

session. Number of documents in a packet is equal to 'Packet-size'.

Maximum-sessions: Parallel sessions not more than 'Maximum-

sessions' will be initiated. Server-group: Group of servers on which

parallel sessions get executed. If this is not specified, then default

server-group in the system gets used.

Transaction IP New Functionality /IRM/IPPCM Partner Communication -

Add and Delete lines

manually

One can add or delete lines manually in the PC document. This

functionality did exist but has been enhanced in this release. Earlier

one could not add a line item to the PC document if it came as a part

of the vendor’s response was not a part of the original submitted

claim and was not a valid SD billing document in the system.

However, now one can add a line item with an invalid SD Billing

document and line item and the system will accept it but will give it

an appropriate line color to signify that this is invalid.


Copy functionality

One will be able to create a copy of a PC document by clicking on the

copy button.





Final Settlement

Final Settlement is carried out when the vendor response of all line

items are either same as submitted or within tolerance. In the

current system, in the PC document if the vendors response of all line

items are either same as submitted and/or within tolerance , and you

try to do Interim Settlement then the system will not let you do so

since there is no item outside tolerance. Thus one has to carry out

final settlement on those IP documents as a separate step.

However in the new version, if the vendor’s response for all the line

items are same or within tolerance and the user clicks on the Interim

Settlement button then system will automatically carry out Final

Settlement. If the response for some of those line item is within

tolerance and the system automatically adjusts the net value of the

line item, then before Final Settlement takes place , the accrual

amount must be reversed and then re-accrued. The system now also

takes care of this and will reverse accrue and re-accrue before

carrying out final Settlement.


Line Item colors

Going forward, colors will be assigned to the lines in the Partner

Communication document to denote their status. The colors act as a

visual aid to the user. There is a color wheel at line item level which

displays the different colors and their significance.

- For additional information, go to the Transaction IP_PC_Line Item

Color attachment.





Park with Interim Settle

There is now an option to Park with Interim Settle such that you can

Park the IP documents to create a claim and at the same time debit

the vendor for the amount that you are claiming. However when the

vendor responds, you will record the response in another PC

document and Settle the actual amount that he has responded with

and reverse the settlement that you had performed while parking.

- For additional information, go to the Transaction IP_PC_Park with

Interim Settle attachment.


Postings Tab

On the Partner Communication document header, you will now have

a tab called ‘Postings’. This tab is used to display the numbers of all

the Partner Communication documents which share the same Parked

Document (Claim). All the Interim Settlement and Reverse Interim

Settlement documents linked to the respective Partner

Communication document are also shown. The purpose of this tab is

to provide visibility into the various postings carried out for the

Parked Document (Claim) and also to see Partner Responses which

were recorded in various Partner Communication Documents which

may or may not have been Interim Settled.

All the Interim Settlement and Reverse Interim Settlement

documents are hot links so that when you click on them they will

take you to the respective Accounting documents.

The lines in this tab have colors to indicate different cases. There is a

color wheel present to denote what the different colors mean.


Proposed Interim

Settlement Amount (PISA)

Going forward, at line item level, the system will propose a

Settlement amount based on what has been previously settled for

the line item and the new adjusted amount.

- For additional information, go to the Transaction IP_PC_PISA

attachment.





Re-determine Proposed

Interim Settlement

Amount

There is now a new button in the application toolbar for PC

document. This button is used to re-determine the Proposed Interim

Settlement Amount. The button looks like a calculator. In the earlier

version, this button was used to calculate the header level Adjusted

Amount but is no longer used for that purpose.

Consider this example where you recorded the vendor’s first

response and performed interim settlement. The vendor provides a

second response but this PC document was put on hold and wasn’t

updated to the IP documents. Suppose that the third response comes

in, PC document is created and Interim Settled. If after a while the

vendor comes back and asserts that the second response was the

correct one then one must go into the PC document created for the

second response and re-determine the Proposed Interim Settlement

Amount as the already Settled Amount has now changed. When you

click on the Calculator button, the system will re-determine the

Proposed Interim Settlement Amount and then one can carry out

Interim Settlement.


Requested Interim

Settlement Amount field

There is now a field at the header level called Requested Interim

Settlement Amount which is used when the vendor does not provide

line item detail while responding and only gives a header amount.

You can put the Header Amount in this field and the system will

distribute this amount to the line items based on the proportion of

the submitted amount of that line item compared to the total

submitted amount.





Requested Interim

Settlement Amount field

There is now a field at the header level called Requested Interim

Settlement Amount (RISA) which is used when the vendor does not

provide line item detail while responding and only gives a header

amount. You can put the Header Amount in this field and the system

will distribute this amount to the line items based on the proportion

of the submitted amount of that line item compared to the total

submitted amount.

- For additional information, go to the Transaction IP_PC_RISA field

attachment.


Reverse Interim

Settlement

After Interim Settlement is carried out, if required, you now have the

ability to reverse the Interim Settlement. A button for Reverse

Interim Settlement will appear in the header after Interim Settlement

is carried out. Also the link to the Reverse Interim Settlement

document appears in the Postings Tab of the PC document.


Settled Amount for the

line item

It is a common process in Chargebacks for the vendor to come back

more than once with a response to a line item. Also, it is common for

the distributor to resubmit the claim in order to be reimbursed with

the accurate amount of money. Also, you can carry out interim

settlements multiple times for a submitted claim. Considering all

these scenarios, it would be highly beneficial to know the total

amount of money settled for a particular line item so far.

Now, a new column in the line item level grid has been introduced

which displays the “Settled Amount” for the line item. For a

particular claim, when one creates the Partner Communication

document, it shows the amount which has been settled for that line

item due to previous Interim Settlements. Thus, one has the

information of the amount submitted and settled so far readily

available to them.

- For additional information, go to the Transaction IP_PC_Settled

Amount for the line item attachment.




Transaction IP New Functionality /IRM/IPPCUPL Partner Communication -

Upload an entire PC

document

One can now upload the entire PC document i.e. both header and

line item information from a spreadsheet. This upload program has

the same format as all other Vistex upload programs where you can

specify the positions of the various columns in the spreadsheet and

also specify a constant value if it applies to all the rows of the

spreadsheet.


Upload PC document line

items from a spreadsheet.

One can now upload PC document line items from a spreadsheet

once the header information is filled in. This upload program has the

same format as all other Vistex upload programs where you can

specify the positions of the various columns in the spreadsheet and

also specify a constant value if it applies to all the rows of the

spreadsheet.

Transaction IP New Functionality /IRM/GCRM Resubmission There are two new options in the Claim Workbench: Transfer and

Resubmission. A Transfer copies line items from one claim to a new

one. Resubmission creates a new claim from the selected items of

the source claim and calculates the delta line item value. It

references the original document and determines the already settled

amount on the line item. There is a predelivered formula to calculate

the delta. A new claim header "Category" field indicates if a claim

results from a transfer or a resubmission; a reference document field

stores the source document number.

- For additional information, go to the Claim_Claim Resubmission

attachment.




Transaction IP New Functionality /IRM/IPxx35 Resubmission of the IP

Document

In previous releases, a re-transmission of the parked document was

possible but a resubmission of select lines was not provided as

standard. In this release, a true resubmission process is available

using transaction code /IRM/IPxx35. There are two new functions: a

Resubmit button on the ALV line item grid and Resubmission History

Display menu pull-down option. With the Resubmit button you can

select lines for resubmission and the system will generate output for

only the selected lines. A pop-up displays the list of selected IP

document lines being resubmitted. The Display Resubmission menu

option shows the history of the resubmitted items. It stores a

version of each output; it displays which lines were attached to each

resubmission.

Transaction IP New Functionality /IRM/IPxxLIS Update LIS Version Based

on IP Type

Standard logic for infostructure updates from transactional IP

documents is to update the '000' active version. This remains the

default in the new release. In addition, configuration now allows the

update of an LIS version other than '000'. This is set in IP type

configuration with a "version" field. This allows for select IP

document types to update versions other than actual such as goal

data, planned data or what-if scenarios.

Transaction IP New Functionality /IRM/IPxxM Update Tracking Item There is now a field called Tracking Item. At the time of settlement,

the item is automatically assigned a number and this is what is

communicated externally as the item number. This is done because

there could be multiple documents that exist with each of them

having multiple line items, so by assigned a sequential number to

each line item it makes communication easier.




Transaction IP New Functionality /IRM/IPxxM

/IRM/IPxx21

/IRM/IPxx22

/IRM/IPxx23

/IRM/IPxx29

Enhancement In the BADI /IRM/BADI_IPXX_ALL, the following new methods have

been added to influence the header, item and partner data from the

source document:

BILLING_HEADER_FILL / BILLING_ITEM_FILL

CLAIM_HEADER_FILL / CLAIM_ITEM_FILL

SALES_HEADER_FILL / SALES_ITEM_FILL

RCA_HEADER_FILL / RCA_ITEM_FILL


/IRM/IPxx23

Enhancement In the BADI /IRM/BADI_IPG_ALL, the following new methods have

been added to influence the PPF processing for Accounting

Documents:

AFTER_IPBKPF_SAVE

ACTIONS_DISPLAY


/IRM/IPPCM

Enhancement In the BADI /IRM/BADI_IPPC_ALL, the following new methods have

been added to enhance the PC document:

HEADER_FILL - Enhance Partner Communication Header

ITEM_CHECK - Check Partner Communication Item

ITEM_FILL - Enhance Partner Communication Item

PARTNER_COMM_CHECK - Check Partner Communication

BEFORE_SAVE - Enhance Partner Communication before saving to

database

AFTER_SAVE - After saving a Partner Communication

ITEM_DISPLAY_PREPARE - Determine whether a particular field of an

Item is Editable

COPY_CHECK - Check and modify Document Copied

EXCEL_ITEMS_IMPORT - Enhance item data imported from Excel

AUTHORITY_CHECK - Check Authorizations (Create/Change

/Display/Post)

Transaction

Register

New Functionality /IRM/GRCAM Authorization A new authority object V_GB_RCPTY is delivered which is used during

processing of transaction register for purchasing documents.

Transaction

Register

New Functionality /IRM/GRCAM Inbound IDOC for

Transaction Register

Use inbound IDOC type /IRM/SALESRPT01 to create Transaction

Register document .




Transaction

Register

New Functionality /IRM/GRCAM Transaction Register

Workbench

The Transaction Register transaction is /IRM/GRCAM. The

Transaction Register is used to bring external transactions into the

system. Anything that does not fit anywhere else goes into the

Transaction Register. Looks and feels like a claim except it can be

used for all transactions, including Purchasing. Entering material is

optional based on customizing setting at Transaction type level.

Vistex Portal New Functionality /IRM/GWSM

/IRM/GWSUA

Assignment - In order for a user to see workspaces in the portal, the workspace(s)

must be assigned to each user. You can manage the assignment

directly through /IRM/GWSUA or through /IRM/GWSM --> Extras -->

User Assignment.

- Users can be assigned to workspaces for a particular time frame.

Super-users can create workspaces in Production and they can be

transported directly from the Workspace transaction.

- For composite-type workspaces, a user only needs to be assigned to

the composite-type workspace, not each of the individual-type

workspaces within it.

Vistex Portal New Functionality /IRM/PORTAL Portal - Notifications The Notifications tab on the Portal contains Workflow and Alerts

from the user's SAP Business Workplace.

Vistex Portal New Functionality /IRM/PORTAL Portal - Recent Items The Recent Items tab on the Portal contains the most recent items

viewed while in the Portal session.

Vistex Portal New Functionality /IRM/PORTAL Portal - Worklist The Worklist tab on the Portal contains all of the user's worklist

favorites. For example, if the user has a Billback Agreement saved as

a favorite and has a Chargeback Document saved as a favorite, both

would appear in the Portal Worklist section.

Vistex Portal New Functionality /IRM/PORTAL Portal - Workspace(s) The Workspace tab on the Portal contains all of the workspaces

assigned to the user.




Vistex Portal New Functionality /IRM/PORTAL Portal Profile In the Portal Profile, the Portal header page image and session

timeout are maintained in this one table. This table is what triggers

the Portal Profile selection popup at the time the Portal transaction is

launched. If you select one Portal Profile, then press continue, you

are shown the header image that is stored in that record and the

session timeout that is stored in that record is applied. In case you

do not select a Portal Profile row, the default shown is the Vistex

image in the header and default session time out is 90 minutes. If

you select all rows and if you click on continue button at that time we

are considering first record only.

The Portal Profile is defined in IPSPRO --> Global Settings --> Define

Portal Profile. New images are loaded via SE80 (MIME Repository >

Right-click on the destination folder (make sure you have

authorizations to that folder)) > Import MIME Objects) and then that

path goes into the MIME Path field in the configuration of a profile.

Vistex Portal New Functionality /IRM/PORTAL Vistex Portal The Vistex Portal is a central point where you can access all Vistex

transactions, SAP transactions and URLs. The main view in the Portal

is essentially the Portal view of your Easy Access screen. When a link

is launches from the Portal, it will navigate you to an already open

SAP session.




Vistex Portal New Functionality /IRM/GWSM Workspace Creation - A Workspace contains groupings of links (i.e. transactions and/or

URLs) for users; these can also be considered Roles. You can create

your own Workspaces using transaction /IRM/GWSM. Using

transaction /IRM/GWSM you can create GUI,BSP and URL links that

can be accessed from the Portal. Transaction /IRM/PORTAL is used to

login to the Vistex Portal.

- Workspaces can be created manually or by importing from a role

menu. There are two types of Workspaces: Individual and

Composite. A user can have many roles, if there are many individuals

with a few of the same roles, a composite workspace can be created

which is a collection of individual workspaces.

Vistex Portal New Functionality /IRM/GWSM Workspace Sections Within each workspace, you can assign links to an unlimited number

of sections. There is a two column limitation and the columns are

independent of one another. There is no row limitation. As you

create links, you can assign them to a section at that time or you can

assign them later if the desired sections are not set up at that time.

You have the ability to nest sections in a hierarchical order; you have

to decide the appropriate parent link.




Vistex Portal New Functionality /IRM/GWSM Workspace Types - A Workspace has three different node types: Transaction, Web

Application and URL. Transaction types are comprised of GUI Vistex

transactions (Workbench and Other) and GUI Other transactions (ex.

VA01, etc.). Web Application types are comprised of BSP Vistex

transactions and BSP Other transactions. URL types are comprised of

any other links (ex. www.vistex.com).

- Within GUI Vistex Workbench types, you can specify different

processing types and context (i.e. attributes). The processing types

are Create, Change, Change with ID, Display and Display with ID. The

context enables you to set up the defaults that you want to set. For

example, you can specify that you want the Sales Organization to

default every time you launch that particular link from the Portal.

Currently, context is only available for Agreements, Agreement

Requests, Claims and Composite. Also, certain links can have saved

searches/variants to help narrow the desired search results.


Document Repository

Page 1 of 13

Configuration for Stored and Active Documents

Stored Documents

1 . Define Content Repository (Giving Storage Logical Name)

Transaction: OAC0

Creation and Maintenance of Content Repository

Document Repository

Page 2 of 13

To check the created repository, click on CSADMIN button.

Transaction: CSADMIN

Document Repository

Page 3 of 13

2 . Defining Document Classes

Customizing Object: V_TOADD

Transaction: SM30

Document Repository

Page 4 of 13

Double-click on the Document Class

Here we can change the application for Document class. It indicates using which tool you want

to open this type of Document.

Example: we changed the application of JPG Document class to EAIWEB.WEBVIEWER2D.

Here we want to open this document in ECL Viewer.

Document Repository

Page 5 of 13

Defining Document Types

Here we had standard ones if we want to create any new one we should start its name with the

letter ‘X…’ in the below we created with ‘Z…’

Transaction: OAC2

Customizing Object: TOAVE

Transaction: SM30

Document Repository

Page 6 of 13

Providing Links of Content Repository to Document type and Object type

Transaction: OAC3

Active Documents

1 . Assignment of Application Classes to Object Types

Transaction: SBDSV1

Document Repository

Page 7 of 13

Creating link between BDS to Content Server

Transaction: SBDSV2

Document Repository

Page 8 of 13

Configuration for Document Repository

Transaction: /IRM/GDRMDLM

Defining Folder Types

Document Repository

Page 9 of 13

Defining Model

Assigning Folder Types to Model

Document Repository

Page 10 of 13

Create and Maintain Attribute Set

Create and Maintain Attributes for selected Attribute Set

Document Repository

Page 11 of 13

Assignment of Model and Attribute Set to Object Type and Qualifier

Maintaining Documents for Specified Application

Document Repository

Page 12 of 13

Example: Claims

Transaction: /IRM/GCRM

Searching Documents Across Object Types

Transaction: /IRM/GDRM

Search Screen

Document Repository

Page 13 of 13

General Documents Maintenance

Transaction: /IRM/GDRGM

Partner Communication – Settled Amount for the Line Item

Page 1 of 1

Please see this example below. For line item 1, the original submitted amount was $1000. Before this Partner Communication document was created, there were previous Interim Settlements carried out and thus far $994.56 has been settled. Similarly, for the other two line items.

Partner Communication - Park with Interim Settle

Page 1 of 1

These are the series of events which would take place:

a) IP documents are Parked and in the background a PC document of type A is created and Interim Settlement (#1) is carried out for $X.

b) Next the vendor provides his amounts and we create a PC document of type B. The total of his response comes up to $Y. We Interim Settle for amount $Y and in the background the system will reverse the #1 Interim Settlement for $X.

c) Continue the rest of the process as is.

Configuration and other settings required for this to work:

a) Create two separate PC document types, one which will be created when the Parked Document is created. The other one for recording the vendor’s actual response.

b) The PC document used during Parking must be assigned in the Settlement Profile which is used for that IP type

c) In the Vendor Settlement Parameters or Agreement Settlement Parameters, for Settlement Type select “Park and Interim Settle” option

Composite Log Document

Page 1 of 7

The Composite Log Document allows for a snapshot of the IP transactional data that essentially was

used to post any Financial Entries. This functionality will be available via the Calculation Run

functionality and is known as Composite Logs.

Configuration Necessary: A new configuration Point has been delivered in IPSPRO (Define Header Copy Control for Composite

Postings)

In this configuration area the following entries are a must have, highlighted are important elements to

point out the other are non-trivial but may vary depending on the existing Composite design based on

the implementation.

Composite Posting Category: Please use CR for Calculation Run, other categories will be used along the

Business Register functionality

Company Code/Partner Type

IP Type: Please ensure that the Number Range for Transactional Logs has been assigned to the IP

document Configuration

Partner Function/Sales Organization/Distribution Channel/Division/Partner Determination Procedure

*Manual Override Condition Type : This condition type is where the distributed amounts will be placed

at the line item level. This topic will be discussed further in the next section.

* Pricing Procedure: The pricing procedure to be used within the log. If this pricing procedure is the

same as in the IP documents to which the distribution will occur to, all condition types will be copied

exactly the way they are in the source document to the Log. If the pricing procedure is different it can


Page 2 of 7

be used along with the values of ‘’ or ‘A’ in the Condition Copy option in order to only copy certain

condition types.

* Copy Source Document Pricing: If this indicator is set it takes precedence over the Condition Copy

option and it will copy all condition types exactly as in the source document.

* Condition Copy: If the pricing procedure assigned in this customizing point is not the same as in the

documents to which the distribution will occur to the values of ‘’ and ‘A’ can be used to selectively copy

condition types into the Composite Log.

Sample of completed Configuration:

Besides the new configuration point an existing configuration point has been added new options that

will work along with the Composite Logs functionality. These new options are in the Deployment Code

configuration and are highlighted below.


Page 3 of 7

Below is a brief description of what these new options are for.

Update Document Flow: With this Flag on every IP document which contributed to the Deployment

Code Financial Posting will have visibility the Composite Posting via the Document Flow of the

transactional document itself (i.e. /IRM/IPSIM). Below is a screen shot of how this looks like:


Page 4 of 7

Notice that every line item has an accrual entry, as opposed to transactional Accruals where the Accrual

is at the header level whenever an accrual happens from a Deployment Code and the Accounting level is

performed at the IP document level every line item will be apportioned an amount based on internal

logic which is explained below under the “Accounting Level and Distributed By Options” below.

Accounting Level & *Distributed By: The way in how the Financial Posting will be distributed across the

selected option. The financial document can be distributed by IP document, Subcomponent or

Deployment Code and using different criteria such as the line item net value or prices/values stored in

subtotals in each line item.

Quick Explanation of the Logic behind this functionality – Refer to the Technical Documentation for

Release C for a more broad explanation of the logic flow:

The following assumes the configuration is as in the screen shot above where the Net Value is used to

apportion or distribute the accounting posting:

Amount Allocated to Line item (what you see in the Document Flow above for each line item): Line Item

Net Value / Sum of all Line Items Net Values * Accrual Amount

The same way the Net Value is used many other attributes can be used to distribute the Financial

Posting Amounts across the line items, some other options are:

Quantity, Parallel Quantity, Subtotal 1,Subtotal 2,Subtotal 3,Subtotal 4,Subtotal 5, etc.

In the event that a different factor must be used to distribute the postings by a user exit has been

delivered under the XIPxx (i..e XIPSI for Sales Incentives function group), these exits are 40 and 41 and


Page 5 of 7

are called Filter IP Documents PTD and CPD. For sample logic to be used in these user exits one can

always refer to the standard code, sample code can be found under include /IRM/LIPCIMF0E Form

Routine Eligible_Posting_Amount_Split. In addition to this the Distribute by Value must be set

accordingly in customizing to call the user exit instead of standard logic in this way.

It is important to point out that the standard functionality only supports one Currency, all IP

documents will be in the same Currency as the Accrual and Settlement amounts relevant for Logs

Posting. In the event that the IP documents to which the distribution will be applied to currency

conversions should take place by the means of an enhancement with the already mentioned user exits.

Transaction Flow and Table Updates Since the nature of this functionality is behind a Calculation Run the first thing we need to create is a

Calculation Run.

When a Calculation Run is created the Composite Logs will be saved. Composite Logs for Composite as

opposed to Transactional Logs consist of a single IP document, the type of the IP document is the type

assigned in the configuration done previously under Documents-> Define Header Copy Control for

Composite Postings.

In order to view the log one must navigate to the General tab of the Calculation Run and click on the

Logs icon which is highlighted below:


Page 6 of 7

The icon has multiple options depending on the type of Financial Posting allowed within the Calculation

Run Configuration (i.e. Accrual, Settlement, etc). Selecting Accruals in this example will bring present us

with the Composite Logs for this Calculation Run:

Notice how a single IP document-like is displayed. This IP document-like entry is stored in the following

tables:

/IRM/IPCPHDRL Header Table for Composites Logs

/IRM/IPCPITML Line item Table for Composite Logs

/IRM/IPCKL Conditions Table

/IRM/IPCPPTRL Partners

/IRM/IPCPITMPL Purchasing Item Logs

The tables above are shared across all applications (with the exception of /IRM/IPCPITMPL which is used

for the Purchasing Rebates application) such as Sales Incentives, Customer Rebates, etc.


Page 7 of 7

When navigating to each line item and reviewing it’s pricing one can’t help but notice the manual

Condition Type (ZMAN) which had previously been assigned in configuration under Documents-> Define

Header Copy Control for Composite Postings.

To understand how the amount populated for ZMAN is calculate please revisit the Distribute By and

Accounting Level configuration points discussed in this document. Also notice that Condition Type PR00

copied over from the original IP document, if more conditions need to be copied to the log from the

original IP document please configure the Pricing Procedure assigned under Documents-> Define Header

Copy Control for Composite Postings accordingly

Partner Communication

Page 1 of 1

Consider the following case where one is recording the vendor’s first response (adjusted amount) to a claim. In this case, since nothing has been settled before, the PISA amount is same as Adjusted Amount. Also, suppose that the adjusted amounts are now Interim Settled.

Submitted Amount

Adjusted Amount Proposed Interim Settlement Amount

Settled Amount

100 100 100 0

80 82 82 0

120 98 98 0

When the vendor sends in a subsequent response, this is what the PC Document will look like.

Submitted Amount

Adjusted Amount Proposed Interim Settlement Amount

Settled Amount

100 100 0 100

80 79 -3 82

120 102 4 98

For line item 2, we have already Interim Settled $82 because of the previous response and thus with

the new response, we owe the vendor $3 and thus the system proposes -3. For line item 3, we had

previously settled 98 but now the new vendor response is 102 and thus the system proposes 4 since

the vendor owes us an additional $4.

Transaction IP Log Document

Page 1 of 4

The Transaction IP Log Document allows for a snapshot of the IP transactional data that essentially was

used to post any Financial Entries. In the transactional IP model this functionality will be viewable via

the /IRM/IPxx35 (replace xx with IP module i.e. SI, CB, etc.) transactions provided in each IP module.

Configuration Necessary: The existing configuration point to define IP documents has been extended to include the following

fields (Documents->Define IP Types)

*Log Accruals: IP Logs will be created when performing Accruals and Reverse Accruals.

Log Parking: IP Logs will be created when creating a Parked Settlement and Park Document Deletion.


Page 2 of 4

Log Settlement: IP Logs will be created when performing Settlements and Reverse Settlements,

including Settlements via Payment Schedule which occur at the header level of the IP document.

Interim Settlement: IP Logs will be when performing Interim Settlements as well as Reverse Interim

Settlements.

Log Range Interval: The range that will be used to create the logs documents, this number range must

be maintained the same way any other number range for an IP document would (i.e. under Global

Settings)

It is important to point out that that Reverses Accrual logs will point to the figures displayed at the

time of Accruals. This is due to the fact that pricing conditions can be changed after an Accrual (but not

after a settlement). If pricing changes in between an Accrual and a Reverse Accrual activity figures

stored under Net Price, Net Value, Accrual Amount, Subtotals 1-6, etc. can potentially change;

therefore, the data logged under the Reverse Settlement is obtained from the original transaction which

is what is being reversed in the end in all cases.

Transaction Flow and Table Updates In order to view the log one must navigate to the Accounting Document posting via transaction code

/IRM/IPxx35 (replace xx with IP module i.e. SI, CB, etc.) in the case of accruals.

The accrual document number can be obtained from the Doc Flow:


Page 3 of 4

In the case of Sales Incentives, the accrual can be viewed via transaction code /IRM/IPSI35

When pressing the Logs icon the transactional log can be displayed:


Page 4 of 4

The data available in the Log will be header, line item, condition record, partner and Payment Schedule

information.

Tables used to store the Transactional IP Log information:

/IRM/IPxxHDRL Header Table for Logs

/IRM/IPxxITML Line item Table for Logs

/IRM/IPTKL Conditions Table (shared across all modules)

/IRM/IPxxPTRL Partners

/IRM/IPxxPSCL Payment Schedule Data

xx = replace xx with IP module i.e. SI, CB, etc.

Parent ClaimFILE

Package (Child Claim)



/IRM/IPxx37 (Validation)

IP Doc for Child Claim 3

IP Doc for Child Claim 2

IP Document for Child Claim 1

Claim WorkbenchCreate / Upload

/IRM/GCRUPL Upload

Multiple Claim

Package Size (i.e. 4,000 items)

Claim Type Config Parent Claim No line items

Child Claim (Package 1) 4,000 items

10,000 items



Selections Search with Parent Claim Search with Child Claim finds Parent

Selected Claim (In focus)Package Screen displays when Claim is detected as a Parent Claim Package Screen contains total number of lines with adjustment code, rejection reason, invalid material, etc. by packageClick on a Package in the Package Screen to display items in the line item gridDetails from only one Package at a time will display in the Claim line item grid Posting is done at Parent Claim level

WorkllistOnly Parent displays in result list

Validation / Posting IP Documents

Navigation from Package ScreenSelect row(s) (i..e Packages) and click NAVIGATION iconSelect column and click NAVIGATION icon (assumes all rows (Packages) are selected) Select column, select row or rows and click NAVIGATION icon (will only display those lines for the Packages (rows) selected

Navigation from Summary View Double click on selected column & row cell Can only do this from the claim level view (hot link while in package level view brings package in focus in the line item grid)

Summary View Choose between Claim level view and the Package level view

IP Document Creation One IP document per Child ClaimNo IP document for the Parent ClaimParent claim is the source document of all IP documents Selection by Parent Claim will select all IP documents for all Child Claims for processing

Settle by Source Document flagVSP / CSP

IP Document Settlement Selection of IP document for settlement should include all the Child Claims & the Parent Claim (system does not inherently enforce this)Child Claims can possibly be settled individuallyIf “Settle by Source Document” flag is set in config, system will ensure that all Child Claims will be settled on 1 settlement document (with caveat that selections must pull Parent Claim and all Child Claims)

/IRM/GCR23 (Posting)

Subsequent claim processing such as Posting and Resolution must be triggered from the Claim mass processing program. These functions will not be possible from the workbench.

Partner Communication - Requested Interim Settlement Amount field

Page 1 of 1

There are two scenarios where this Requested Interim Settlement Amount field can be used: a. When no line item detail is provided – In this case when you create the PC document, you

enter the Parked document details and you will see that submitted amount field will get populated both at item level and header level. The user must then simply enter the header value that the vendor provides in the Requested Interim Settlement field. Once this is done the system will automatically distributes that amount to the line item level and thus populates the Adjusted Amount and Proposed Interim Settlement Amount at line item level.

b. When Line item detail is provided – In this case, suppose that you have entered the line item detail provided by the vendor and you want to deduct an admin fee from the adjusted amount total. You can put the new total in the Requested Interim Settlement field and the system will distribute the difference between the new total and old total amongst the line items. When you change the value of RISA the system gives you a pop-up to chose the option whether you want to distribute this to all lines or only lines where a response is recorded (in the scenario when no response is received for some line items).

Claim Resubmission

Page 1 of 7

Overview

This document proposes to describe Claim Resubmission features including:

1) Creating a Resubmission from the Claim Workbench 2) Creating a Resubmission from a file with line detail 3) Creating a Resubmission from a file with header and line detail 4) Creating a Resubmission from an IDOC 5) Creating Resubmissions using Automated Data Maintenance

Purpose

Resubmissions occur when a previously denied or short-paid claim is returned (usually with justifying documentation) from the distributor back to the manufacturer. The latter may then choose to amend an earlier decision and to payout additional amounts while referencing the original claim. In a resubmission, the distributor is expected to identify the transmission as being a resubmission, to provide a reference to the original claim identifier, to include only the resubmitted items and provide line item references to the original claim line items.

1) Creating a Resubmission for the Workbench

Using transaction code /IRM/GCRM, locate the original claim and, in change mode, highlight the lines that are the targets for resubmission. Click the Resubmit Claim in the header toolbar and a new claim referencing the original one is created. Only the highlighted lines are carried over. Original Claim:

Claim Resubmission

Page 2 of 7

Resubmitted Claim:

The new claim retains the Reference no from the original and includes the original claim number as Reference doc. The claim category is shown on the header as „C Resubmission‟.

Claim Resubmission

Page 3 of 7

Pricing for the claim should include a condition type that represents the original claim document line item value. This is supported using a formula with the include /IRM/GCR_ITEM_SETTLED_VALUE. When the distributor resubmits for the original claimed amount, the net value of the resubmission claim is calculated as distributor requested amount minus the (already paid) original claim item settled amount.

2) Creating a Resubmission from a file with line detail

When the distributor provides line detail of the resubmission in a file form, one available upload option is to do so from the Claim Workbench. This requires the user to locate the original claim header being referenced. To start the process, the user will click the „create resubmission‟ button which prompts a dialog that allows the original claim number to be entered. You would find this „create resubmission‟ button after starting the claim workbench transaction and immediately switching to change mode.

Claim Resubmission

Page 4 of 7

The „Create Resubmission‟ dialog is shown below. Enter the claim to be referenced and then click on the „Propose items‟ icon which will list the document lines and allow the user to select which line items to carry over onto the new document. In this example, we do not want to propose the items from the original claim, but instead upload a file of line items. Hence for this example we will not click on the propose items icon and just continue on without any line items.

Claim Resubmission

Page 5 of 7

Result screen:

The result screen copies the original claim header data into the resubmission claim. Just like the dialog process in the prior section, the new claim retains the Reference no from the original and includes the original claim number as Reference doc. The claim category is shown on the header as „C Resubmission‟. No line data is copied over. On the line item ALV, the „Import from file‟ button allows line item data upload. The resubmission claim will have its reference document number (/IRM/GCRITM-TRDOC) set to the original claim number identified in the above dialog. The resubmission claim line number (/IRM/GCRITM-TRITM) is determined by a lookup of the original claim line numbers: when upload file includes values for VBELV and POSNV, then TRITM is the line number from the original claim where VBELV and POSNV from the file = the original claim VBELV and POSNV. If no match occurs or if VBELV and POSNV are blank, then attempt to match on TRACKITM: if TRACKITM from the file matches a TRACKITM from a line from the original claim then use the original claim POSNR value to populate the resubmission claim TRITM. If no match occurs or more than one line matches or no TRACKITM value is provided, assign POSNR as if creating a standard (original) claim, leave TRITM as initial and insert into the message log a notification such as „Unable to determine line item from original claim‟.

Claim Resubmission

Page 6 of 7

3) Creating a Resubmission from a file with header and line detail

When the distributor provides header and line detail of the resubmission in a file form, one of the options available is to use transaction Upload Claim document (/IRM/GCRUPL). In order to recognize that a resubmission claim is being created, the header fields available to upload will include „Claim Category‟ (/IRM/GCRHDR-CRCTG). When claim category from the uploaded file is = „C‟, upload program logic will:

a) use the uploaded value of XBLNR to locate the original claim b) create a resubmission claim that populates the original claim as Reference doc c) map the remaining header and line values from the file into the claim document

If no reference (XBLNR) value is provided or if the reference does not match an existing claim or if more than one claim with original claim type exists for the provided reference, the header and line data for the resubmitted claim will not be uploaded and an error message describing which condition was encountered will be inserted into the message log. E.g.: “Resubmission claim with sold-to &KUNAG and bill date &FKDAT is missing a reference” “Resubmission claim with reference &XBLNR did not match any existing claims” “Resubmission claim with reference &XBLNR matched more than one original claim” Determination of resubmission claim number and line number (/IRM/GCRITM-TRDOC and TRITM) is as described in section above.

4) Creating a Resubmission from an IDOC

When the distributor provides a resubmission via EDI, the standard 849 processing function module will recognize that a resubmission claim is being created using the submission type field. When segment value /IRM/IPCBK01-SUBMS is = „2‟, program logic will:

a) use the IDOC value of /irm/ipcbk01-assignnum to locate the original claim b) create a resubmission claim that populates the original claim as Reference doc c) map the remaining header and line values from the IDOC into the claim document

If no reference (assignnum) value is provided or if the reference does not match an existing claim or if more than one claim with original claim type exists for the provided reference, the header and line data for the resubmitted claim will not be processed and a status error describing which condition was encountered will be provided. E.g.: “Resubmission claim with sold-to &KUNAG and bill date &FKDAT is missing a reference” “Resubmission claim with reference &XBLNR did not match any existing claims” “Resubmission claim with reference &XBLNR matched more than one original claim” Determination of resubmission claim number and line number (/IRM/GCRITM-TRDOC and TRITM) is as described in section above.

Claim Resubmission

Page 7 of 7

5) Creating Resubmissions using Automated Data Maintenance

In some cases, resubmissions will be triggered internally, without being prompted by a distributor (e.g. a Medicaid Claim). When a price type is changed, there is an obligation to send a resubmission back to the submitter. This can be done through Automated Data Maintenance (ADM) as many claims may need to be resubmitted simultaneously. When a price type changes, the user has to identify the claims that need to be resubmitted and initiate a claim resubmission creation from ADM. This can be a collective or individual resubmission.

Partner Communication – Line Item Color

Page 1 of 1

Gray – When you create a PC document the initial color of the line items will be gray until Interim Settlement or IP Document update takes place.

Yellow – When you perform Interim Settlement or Click on IP document update, the system updates the IP documents. If there is any error in doing so then the color of the line items becomes yellow. For example, this could happen when the user is trying to update the IP documents but the IP document is locked, then the line becomes yellow.

Green – When Interim Settlement or IP document update is successfully carried out the line items turn green.

Blue – If one line item is a duplicate of another on that same PC document then the second line will be indicated by a blue color.

Pink - If the line item does have not have a valid SD Billing document and line item number then the system still lets you create and save the PC document but will assign a pink color to the line item.

Peach – If the line item has a valid SD Billing document and line item number but it does not belong to this claim, then the system will assign it a Peach color.

SAP Paybacks & Chargebacks by Vistex

Vistex

Agency Business: Vendor/Customer

Billing Document Integration

Chargeback Process

IP

Documents are settled

Parked

/bundledIP documents(send to

creditor)

Outgoing

AB Customer Proforma Invoice

Step 1 – IP Documents are accrued

• Each IP document accrues separately

• Creation of AB documents (accruals) are created

Step 2 – IP Documents are parked

• IP documents are bundled and parked (settlement is simulated)

• Creation of AB customer proforma invoice (credit memo request)

• Used to communicate request for rebate; no financial impact

IP –

Document(accrual) c

1:1

IP –

Document(accrual) c

IP –

Document(accruals)

AB

documentaccrual

AB

documentaccrual

AB

Document (accruals)

1 2

Partner

Communication document created

Incoming

AB Supplier Proforma Invoice (with suggested

invoice amount)

AB Supplier

Invoice (new)

4 53

IP Documents

of bundle are updated w/ suggested

invoice amt

Chargeback Process - Response

IP


Parked


creditor)

Outgoing


Step 3 – IP Partner Communication Document is created

• Creation of an AB supplier proforma invoice with reference to customer proforma invoice

• Used to communicate response to rebate (suggested invoice amt); no financial impact

• AB supplier proforma invoice is used to create the Partner Communication document

Step 4 – IP Documents are updated with suggested invoice amount

• IP documents are updated based on the Partner Communication document

• The suggested invoice amount is logged for each line item, compared to requested rebate

amount and reconciled if necessary

IP –

Document(accrual) c

1:1

IP –

Document(accrual) c

IP –

Document(accruals)

AB

documentaccrual

AB

documentaccrual

AB

Document (accruals)

1 2

Partner


Incoming


invoice amount)

AB Supplier

Invoice (new)

4 53

IP Documents


invoice amt

Chargeback Process - Settlement

IP


Parked


creditor)

Outgoing


Step 5 – IP Documents are settled

• Creation of a new AB supplier invoice

IP –

Document(accrual) c

1:1

IP –

Document(accrual) c

IP –

Document(accruals)

AB

documentaccrual

AB

documentaccrual

AB

Document (accruals)

1 2

Partner


Incoming


invoice amount)

AB Supplier

Invoice (new)

4 53

IP Documents


invoice amt

Chargeback Process - Accruals

Step 1 – IP Documents are accrued

income account + 50 US $

income account +150 US $

accrual clearing account -200 US $

Account key concept - account determination using account key

Step 4 – IP Documents are settled

A/P vendor account - 200 US $

accrual clearing account +200 US $

Same account key must be used for Step 1 & Step 4

Chargeback Process with Discrepancy

IP


Parked


creditor)

Outgoing


Step 1 – IP Documents are accrued for total of $200

Step 2 – IP Documents are parked, outgoing AB Proforma Invoice totals $200

Step 3a – Incoming response creates incoming AB Proforma Invoice which totals $170

Step 3b – Incoming AB Proforma Invoice used to create PC doc to record response

Step 4 – PC doc used to update suggested amounts onto IP documents; IP documents are reconciled to “agree“ with the

suggested amounts (total value lowers to $170)

*** Now accrual docs ($200) do not match proposed settlement amount ($170) ; settlement not possible ***

Step 5 – Original accrual documents reversed, new accruals totaling $170 are created

Step 6 – Settlement now possible – IP documents are settled, and AB Supplier Invoice created for $170

IP –

Document(accrual) c

1:1

IP –

Document(accrual) c

IP –

Document(accruals)

AB

documentaccrual

AB

documentaccrual

AB

Document (accruals)

1 2

Partner


Incoming


invoice amount)

AB Supplier

Invoice (new)

4 53

IP Documents


invoice amt

The original flow assumed that the response matched the request. Here is an example of an exception situation.

$200$200

$200

$170

$170 $170 $170$200