irmipm 40b: patch 008 notes/irm/badi_gpr_all methods to the new class methods. in addition, you must...
TRANSCRIPT
AreaType of
ChangeTransaction Code Topic Changes
Agreement Fix /IRM/IPxxASP Additional DataThe Additional Data 2 screen on the agreement workbench used to
be just display only. It now has update capability.
Agreement Fix /IRM/IPxxASP Agreement Request
Agreement Request functionality has been enhanced to allow for
update to the agreement. As agreement requests are posted, the
agreement can update revision numbers if configured to do so.
Agreement Fix /IRM/IPxxASP Agreement Request
Agreement requests can now can be created directly within the
agreement. Controls have been added to restrict the number of
agreement requests allowed for an agreement type. Controls are in
place to allow for one or more per agreement/agreement request
type. Controls have also been added to lock the agreement from
being changed while a request is open.
Agreement Fix /IRM/IPxxASP Agreement RequestIf the approval status at the item level is marked as rejected, it will
not copy over to the agreement.
Agreement New Functionality /IRM/IPxxASP Authoring
Templates can be added to agreements during agreement creation
and change. Default template types can be assigned to the
agreement type in customizing. Once a template is assigned to the
agreement, clauses can be added or deleted as necessary.
Dynamic displays are available for output based on the template
structure. Rules can also be added as a clause to dynamically
display the active rules for the specified rule sheet.
Agreement New Functionality /IRM/IPxxASP BADI
The BADI /IRM/BADI_GPR_ALL is now obsolete. It has been
replaced with a "Enhancement" Interface
/IRM/IF_GPR_CONDITIONS. You must use transaction SE24 to
create a class for the interface, and must transfer any code from
/IRM/BADI_GPR_ALL methods to the new class methods. In
addition, you must associate the new class to individual price sheets
in agreement rule configuration by entering the class name in the
"Enhancement Class" field.
In the past, the BADI /IRM/BADI_GPR_ALL was used for price
sheet, maintenance profile and index profile. This is no longer the
case. Two new Interfaces are being delivered for the maintenance
profile and the index profile - /IRM/IF_GPR_PRICE_PROFILE and
/IRM/IF_GPR_INDEX_PROFILE. To use these, you must also
create classes for the interfaces. There is a method called
'SELECTIONS_DERIVE' in both of the new interfaces. This is the
replacement method for PROFILE_SELECTION_ENHANCE from
the obsolete BADI.
IRMIPM 40B: Patch 008 Notes
Page 1 of 12
AreaType of
ChangeTransaction Code Topic Changes
Agreement Fix /IRM/IPxxASP Copy Agreement
Copy controls from agreement to agreement have been enhanced.
Agreements can now copy within agreement types or to a different
agreement type. Selection of rules to be copied has also been
enhanced to limit select rules within a rule sheet from being copied.
Agreement Fix /IRM/IPxxASP Field Catalog
If fields are not in new field catalog list and they are in an existing
variant, they will not show. They need to be added to the list. After
adding to the list, the will be displayed.
Agreement Fix /IRM/IPxxASP Funds
The funds tab in the agreement has been modified to include spend
type, territories, and search capabilities. Spend types tie a rule
sheet in the agreement to a particular fund. This allows for multiple
funds to be assigned to an agreement. Searching is also available
to determine which funds are assigned to the applicable territories
for the agreement as well as what balances are left on the funds.
Fund usage can also be reviewed within the agreement now.
Agreement New Functionality /IRM/IPxxASP Measures
Measures used to only be calculated based on rule attributes. Now,
measures can be calculated using partner, agreement, and
additional data attributes. With this addition, all existing measures
will need to be modified to add "RULE_" in front of the rule
attributes. The LOOP statements will also need to have "AT RULE"
added.
Agreement New Functionality /IRM/IPxxASP Min/max Profile
A min/max profile has been added to the agreement. This is done
by mapping from an agreement to a matrix as well as updating from
the matrix to the agreement. Applications of this functionality will
allow agreements to stop being applied once a maximum quantity or
dollar has been reached or will not apply agreements until a
threshold has been met.
Agreement New Functionality /IRM/IPxxASP Payment Terms
Configuration has been added to restrict allowed payment terms per
agreement type. If configured, only a select list of payment terms
will be displayed when entering payment terms on the agreement.
The entire list will no longer be displayed.
Agreement New Functionality /IRM/IPxxASP Performance
A new tab has been added to the agreement called Performance.
This allows a deployment code to be mapped to the agreement to
track performance and compliance against a plan/agreement. The
agreement will automatically assign participants to the deployment
code. Participants can be agreements or partners or a combination
of the two. In the tab, the deployment code, participants, and any
alerts created during precalucation runs will be displayed. There is
a hot key available to display the current view of the deployment
code for the participants within the agreement.
Page 2 of 12
AreaType of
ChangeTransaction Code Topic Changes
Agreement Enhancement /IRM/IPxxASP PPF Actions
SAP Standard Post Processing Framework (PPF) has been
integrated into the agreement in the form of Actions. This allows for
proactive notification based on date types and output processing.
More details on PPF can be obtained from help.sap.com
Agreement New Functionality /IRM/IPxxASP Price Book
Price Book creation from the agreement has been enhanced to
automatically include AA (Sold-to parties for contract) and AW (Ship-
to parties for contract) as relevant partners. As always, the partners
must exist on the Partner Tab of the agreement. This functionality
will only work if Foundation Data is licensed.
Agreement New Functionality /IRM/IPxxASP Release Status
The release status can now be set based on user status. For
example, if an agreement is set to blocked status and the user
status is changed to allow for release status, the agreement will
automatically be released. Reason codes can also override release
statuses.
Agreement New Functionality /IRM/IPxxASP Release Status
The release status can now be changed at a header level within the
agreement. It is not necessary to use mass change to change
agreement statuses.
Agreement Fix /IRM/IPxxASP Release Status
There is now a flag at the header of the agreement to close an
agreement. If this is set, the agreement will not be taken into
account during agreement search.
Agreement New Functionality /IRM/IPxxASP Sales Order
Sales Order creation from the agreement has been enhanced to
automatically include AA (Sold-to parties for contract) and AW (Ship-
to parties for contract) as relevant partners. As always, the partners
must exist on the Partner Tab of the agreement.
Agreement New Functionality /IRM/IPxxASP Territory Search
Condition search is now called within the agreement to derive
territories. The territory will be determined based on partner,
header, and rule attributes. The territory will be used to search for
eligible fund center documents.
Agreements Fix /IRM/IPxxASP BADI
The BADI /IRM/BADI_GPR_ALL is now obsolete. It has been
replaced with Class Enhancement /IRM/IF_GPR_CONDITIONS.
You must use transaction SE24 to create an interface for the class,
and must transfer any code from /IRM/BADI_GPR_ALL methods to
the new interface.
Basis New Functionality /IRM/GPSPRO Configuration
This "IMG" transaction can no longer be accessed if Foundation
Data is not licensed. The configuration tasks from this transaction
that are pertinent for IP have been added to the /IRM/IPSPRO IMG
under Agreements. The path is /IRM/IPSPRO --> Basic Functions --
> Pricing --> Set up Agreements --> Agreement Rules.
Page 3 of 12
AreaType of
ChangeTransaction Code Topic Changes
BSP New Functionality /IRM/IPxxASPM_WS Agreement
Defaults within the agreement BSP are now available. Sales
organization, distribution channel, division, sales office, sales group,
and currency can be defaulted into the agreement creation web
screen so they do not have to be manually entered. This is
configured within the agreement block profiles.
BSP Fix /IRM/IPxxASP_WS Agreement
A second row of menu buttons have been provided within the
agreement display BSP for various functions including buttons to
create an agreement and an agreement request. When in the
detail screen, there is now a button to copy an agreement. In the
Advanced Search screen, another selection screen field has been
provided to search by Primary Partner Role/Partner Number.
BSP Fix /IRM/IPxxASPM_WS Agreement
Whithin the agreement maintenance BSP, additional fields have
been added to the tabs. Rule sheet hyperlink functionality has been
added to the Rules Overview screen and importing price records
from an excel file into the rule sheet is now supported.
BSP New Functionality /IRM/IPxxARD_WS Agreement RequestA display agreement request BSP has been created. Agreement
requests can now be displayed on the web.
BSP New Functionality /IRM/IPxxARM_WS Agreement RequestA maintain agreement request BSP has been created. Agreement
requests can now be created and changed on the web.
BSP Fix /IRM/GCRM_WS Claim RequestAdditional fields are available in the item grid of the claim request of
the Claim Request BSP.
BSP New Functionality /IRM/GFSUB_WS File Submission
A new BSP has been added for global file submission. Now
external parties can submit data files through the web to be
processed in SAP at a later time. These files can be used for
claims, membership, or partner communication documents.
Claim Request New Functionality /IRM/GCRM Agreement
There are now three "Agreement" fields for the claim line item. The
first is the Agreement Requested, where the submitted agreement
or text would be entered. This entry stays as entered. The system
then uses this value to determine the agreement in the SAP system.
For example, if the external description was the ID that the
submitter uses to identify the requested agreement, the system will
take this value and convert it to the corresponding agreement
number. This is stored in the Agreement Determined field
(KNUMA_DET). During pricing, whatever agreement number is
passed back to the claim as the active agreement is then store in
the Agreement Used field (KNUMA_AG).
Page 4 of 12
AreaType of
ChangeTransaction Code Topic Changes
Claim Request Fix /IRM/GCRM Document Flow
Extended document flow was added in order to view all the IP
documents that may have been created from the claim request.
Also, if a claim request document was created with reference from
another claim request document or line items were transferred from
one claim request document to a new document, these document
numbers will also appear in the extended document flow screen.
Claim Request New Functionality /IRM/GCRM File Submission
A program (/IRM/GFSUB) has been provided to upload a file from a
local directory to a server location. An additional program
(/IRM/GCRUPL) has been provided to upload the files from a server
location and create claim request documents. The second program
can also use the files that were uploaded with the BSP.
Claim Request Fix /IRM/GCRM Mass Change
It is now possible to perform mass changes on the claim request
document for select header fields, line Item fields, and pricing
conditions in the claim requests. The pricing conditions that are
eligible for mass change must be specified in the claim request
customizing section.
Claim Request New Functionality /IRM/GCRM Mass Change
When creating or updating a claim request, the header fields now
include a From and To Date, a From and To Period, and a Spend
Type. These are considered mass processing fields. If a value is
entered for these fields, they will automatically populate the same
fields at the item level when new items are entered. The values in
these fields at the header level will have no impact on already
existing lines, just newly added lines. In addition, the header level
values are not saved, only the line item level values.
Claim Request Fix /IRM/GCRM Performance
Line item changes can now lead to line item processing only. For
example, if an customer is added to a cross reference file or
membership group, it allows for processing of just the one line, not
the whole claim. This was done to improve performance.
Claim Request Fix /IRM/GCRM Performance
The claim request line item grid has been pared down to 40+ fields
for performance purposes. To add more custom fields, add append
structure to /IRM/S_GCRITMCA (Claim Request Items - User
Fields) and then add the custom fields to the new append structure.
To add more standard fields to the item grid display, add append
structure to /irm/s_gcritm_fcat (Claim Request - Items - Field
Catalog) and then add the standard fields into the new append
structure.
Page 5 of 12
AreaType of
ChangeTransaction Code Topic Changes
Claim Request Fix /IRM/GCRM Performance
When searching for claim requests, the system will now default to
not reading line item data. When the claim requests returned from
the search are displayed in the search result grid, the view cannot
be expanded to view line item detail as the line item detail was not
read. In order to have line item detail be available on the search
result grid, the selection screen "Read All Items" checkbox must be
checked. This was done to improve performance. A restriction on
the number of records returned was also added.
Claim Request Fix /IRM/GCRM Performance
In the claim request, the domain of the originating document is 20
characters. Once an originating document number was entered, a
conversion routine was adding leading zeros to the number. Now,
the number will remain exactly as entered.
Claim Request Fix /IRM/GCRM Performance
In the claim request line item upload from excel function, the
originating document number for the upload function was less than
20 characters. Now it is 20 characters.
Claim Request Fix /IRM/GCRM Performance
Search and Replace functionality has been added to the item grid
within the claim request. This will allow for ease of use for mass
changes.
Claim Request New Functionality /IRM/GCRM Pricing
The "pricing complete" function can now be skipped for the Claim
Request document. This functionality is useful if externally fed
prices are the only price conditions in the claim request pricing
procedure. If the checkbox for "skipping complete pricing" is set in
the Claim Request Document configuration, then pricing complete
will be skipped, saving processing time.
Claim Request New Functionality /IRM/GCRM Sell in/Sell through
A quantity check can now be performed by the system on a claim
line item material using pricing conditions established in claim
request header configuration, a quantity check profile, and an IP
Matrix. This allows the sell in/sell through dates to be automatically
calculated.
Claim Request Fix /IRM/GCRM Status
The claim line item status and rejection status can now be
automatically set by the system for an invalid material, invalid unit of
measure, or invalid line item partners from configuration. Also,
replacement values (e.g. DUMMY) can be established in case of the
entered ID being invalid.
Claim Request Fix /IRM/GCRM SummaryThe claim summary now is now an ALV grid instead of an HTML
screen. This allows for more personalization of the screen.
Page 6 of 12
AreaType of
ChangeTransaction Code Topic Changes
Claim Request Fix /IRM/GCRM Tolerances
The system can automatically adjust the net price of a claim line
item by using the Value Adjust section of configuration in the claim
request header configuration. It works exactly as the adjustment
pricing condition found in the IP document header configuration.
Claim Request New Functionality /IRM/GCRM Validations
It is now possible to skip all user checks when processing a claim
request. A "Skip All Checks" reason code must be configured and
added to the Claim Request Document configuration. If the claims
processor chooses the Skip All Checks reason code in the claim
request document, the document will bypass any user checks
established in the User Checks user exit. A "Skip All Check" reason
code must be available in the claim request document customizing
in order to use the new transaction /IRM/IPBB37.
Claim Request Fix /IRM/GCRM Validations
A zero value quantity is now allowable in the claim request
document. If a quantity is required, it must now be handled during
user checks.
Composite IP Fix /IRM/GMXM BADI
The BADI /IRM/BADI_GMXM_ALL is now obsolete. It has been
replaced with "Class Enhancement" Interface
/IRM/IF_GMXM_ENHANCEMENT. You must use transaction SE24
to create a class for the interface, and must transfer any code from
/IRM/BADI_GMXM_ALL methods to the new class methods.
Composite IP Fix /IRM/IPXXCIP Currency
Company code and settlement currency can now be defined at the
participant level. A payment currency was also added. This allows
for more flexibility in postings where multiple currencies can exists
within one deployment code.
Composite IP New Functionality /IRM/GMXM Matrix
A flexible maintenance tool was created to allow for matrix data
entry. This will allow for ease of use in planning and quota
management. Roll ups, proportions, and prior years can be used to
create and maintain data within the matrix. User defined functions
such as prior year plus 10% can be added as well.
Composite IP Fix /IRM/GMXM Matrix
A new member creation screen has been added. This can be
accessed outside of the matrix. It allows for an easier entry of
members as well as the ability to enter members without adding
matrix data.
Page 7 of 12
AreaType of
ChangeTransaction Code Topic Changes
Composite IP Fix /IRM/IPXXCIP Participants
Lower level participants can now have different validity periods than
their higher level participant. This allows for members to be added
to a deployment code for time periods shorter than their parent. For
example, if a member is added mid way through the year, their
results from the past periods will not be taken into account.
Composite IP New Functionality /IRM/IPCPB Plan Builder
A more user friendly HTML based tool was developed to create
composite plans. This is available to all composite applications
from plan inception to creation to maintenance to execution.
Composite IP New Functionality /IRM/IPCPE Plan Explorer
A more user friendly HTML based tool was developed to display
composite plans. This is to be used by a standard user to review
how a plan was created.
Composite IP Fix /IRM/IPXXCIP Postings
Accruals can now be done within a shorter period within the larger
period defined for the deployment code. For example, a quarterly
plan can now have three postings (one for each month) instead of
one posting that is reversed each month.
Composite IP Enhancement /IRM/IPXXCIP Postings
Settlement to multiple partners is now available. For example, if
performance tracking is done based on total sales at a corporate
level, the individual stores can be paid not instead of just payouts to
the corporate level.
Composite IP Fix /IRM/IPXXCIP Postings
Finite postings check is now set at the deployment code and version
level. Since a participant can now exist multiple times in a
deployment code, all checks for assigning, unassigning, and editing
have to be controlled at the participation and not the participant
level.
Composite IP Fix /IRM/IPXXCIP Status
The precalculation run now has a status object tied to it. This allows
for user statuses to be defined as well as work flow to be triggered
from it.
Composite IP Fix /IRM/IPXXCIP Tracking
A fiscal year variant mapping table is now available. This allows
flexible mapping between otherwise incompatible fiscal year
variants.
Composite IP Enhancement /IRM/IPXXCIP Tracking
Deployment code variants are now available. If the participant wants
to follow a fiscal year that is different from the deployment code
fiscal year, it is not necessary to create a new deployment code with
a different period structure to accomodate this. A new deployment
code variant with the participant's fiscal year can be created and
assigned to the primary deployment code. All calculations and
postings logic is the taken from the primary deployment code.
Page 8 of 12
AreaType of
ChangeTransaction Code Topic Changes
Contract Authoring New Functionality /IRM/GTPM Authoring
Template creation is now supported. A new template workbench
has been added to manage the creation, maintenance, copying, and
approval of templates necessary for contract authoring. Template
types are available to make clause types optional, required,
preferred, or negotiable. During template creation, structures and
replacements are defined. Dynamic HTML and MS Word creation
of a template is available.
Contract Authoring New Functionality /IRM/GCLM Clauses
Clause creation is now supported. A new clause workbench has
been added to manage the creation, maintenance, copying, and
approval of clauses necessary for contract authoring. Clause
controls are set up by unique clause types. Dynamic HTML and MS
Word creation of the clauses is available.
Funds Management Fix /IRM/GFMxxx Funds
Territories have been added to the fund assignment to allow for
searching of suitable fund based on territories. This will allow for
ease of use when assigning funds to agreements.
Funds Management Fix /IRM/GFMxxx Funds
New Vistex workbenches have been created for the standard SAP
fund management processes. This allows for ease of use and a
more user friendly interface. They have been created for funds,
fund centers, commitment items, structure maintenance, budgeting
releasing, reservations, and usage.
IP Hierarchies New Functionality /IRM/IPHIM Participants
The IP hierarchy display will now show the entire participation
hierarchy. A where used funciton is also now available to determine
where a member is assigned as well as to whom it is assigned
within an IP hierarchy.
IP Hierarchies New Functionality /IRM/IPHIM Participants
Organizational units and positions can now be entered as
participants. The HR values can be used within a hierarchy or as
participants within a deployment code. For example, the
organization unit can be the participant and the settlement can be
done to the people assigned to that organizational unit.
Membership Fix /IRM/GMLM DisplaySearch help for membership has been added. It is now easier to
find a membership list.
Membership New Functionality /IRM/GCMA Display
Transaction /IRM/GCMA has been created to show which
membership groups a member has been assigned to. It is a where
used function for members. It shows full top down/bottom up
hierarchy in the where used list for a member.
Membership Fix /IRM/GCMD Display
A membership list can now be invoked from a current member
display transaction. There is a hot key within the display screen. It
will also show when the member was added to the list.
Page 9 of 12
AreaType of
ChangeTransaction Code Topic Changes
Membership New Functionality /IRM/GMLM Submission
A membership type is now required for each submission. The
membership type controls which fields are required for the
submission. It will also control which fields can be entered within
the submission. Member master data can also be validated before
a submission can be posted. A report will need to be run to put a
membership type on the existing submissions for them to be
displayed. No validations will be done when this report is run.
Miscellaneous Fix VA0x, VF0x Document FlowIP document details can now be viewed again within sales order and
invoice document flow.
Price Book New Functionality /IRM/IPxxASP BADI
A BADI has been provided to influence Price Book processing, such
as determining material to include in Price Book. The BADI is
/IRM/BADI_GPB_ALL. Price Book is available only if component
Foundation Data is installed.
Product List Fix /IRM/GPLM Product list
If Primary Partner is changed in a product list, follow up checks are
now done. Changes can be controlled more systematically now and
validated.
Product List Fix /IRM/GPLM Product listItem status is now available for product lists. Approvals and
workflows can be triggered at an item level within the product list.
Product List Fix /IRM/GPLM Product listNavigation to category definition can now be called from within the
product list transaction. A second screen is not needed.
Product List New Functionality /IRM/GPLM Submission Product List can be created from a file submission
Transaction IP Fix /IRM/IPxxM Agreement Resolution
Agreement resolution has been added as an option within the
agreement selection within the pricing procedure. It allows for rules
to be set based on an access sequence to determine which
agreement should be selected. Options include oldest agreement,
newest agreement, best price, worst price, agreement specified,
highest priority, etc.
Transaction IP Fix /IRM/IPxxM Agreement Search
If multiple agreements are to be applied to one source document for
one IP type, the system will now automatically create multiple IP
documents for that combination based on the agreement search
profile. This will allow for ease of use during reconciliation to better
control which agreement has been authorized and which hasn't.
Page 10 of 12
AreaType of
ChangeTransaction Code Topic Changes
Transaction IP New Functionality /IRM/IPxxM BADI
It is now possible for the system to create multiple IP documents
based on splitting criteria related to the source document. The
"SOURCE DOCUMENT" BADI methods from the BADI
/IRM/BADI_IPG_ALL must be utilized. Add additional partners in
the partner table, and enter the split criteria in the Header structure
'ZUKRI' field for sales related documents. For purchasing, enter the
split criteria in the partner records in the contact person field
(PARNR), and set the value of the PRFRE field to 'X'. For
example, to create one purchasing IP document for each goods
receipt of a PO, add one partner record for every good receipt
material document existing to the parnter table, entering the goods
receipt document number in the contact person field. An IP
document requirement routine must be used at the item level to
restrict the line items from a PO to just those from the particular
goods receipt document being processed.
Transaction IP Fix /IRM/IPxxM Condition Search
Territories derived in the condition search within the IP document
can now be used to update the matrix. This is necessary for sales
incentive plans where a sales rep isn't assigned at an order level.
Just the territory is assigned and then the rep is assigned to the
territory at the participant level of the deployment code.
Transaction IP Enhancement /IRM/IPxxM Condition Search
When condition search is invoked during IP document creation, the
specification of key fields of condition tables can now be added as
partners or additional fields. These values will also be available for
further processing within the document.
Transaction IP Fix /IRM/IPxxM Funds
Postings to the correct funds are done through spend types defined
at the agreement level. This is done during accrual of the IP
document. Controls are in place to ensure the fund is not
overspent. Reversals of the accrual will remove value from the
funds.
Transaction IP New Functionality /IRM/IPxxM Min/max profile
Application of the min/max profile set on the agreement is done in
the IP document. Agreements will not be applied if the minimum or
maximums are not met.
Page 11 of 12
AreaType of
ChangeTransaction Code Topic Changes
Transaction IP Fix /IRM/IPxxM Performance
When searching for IP documents, the system has an option to not
read line item data. When the IP documents returned from the
search are displayed in the search result grid, the view cannot be
expanded to view line item detail as the line item detail as the line
item detail was not read. In order to have line item detail be
available on the search result grid, the selection screen "Read All
Items" checkbox must be checked. This was done to improve
performance. A restriction on the number of records returned was
also added.
Transaction IP Enhancement /IRM/IPxxM SettlementAgreement based settlement is now allowed in transactional and
composite IP. If it is set up, the agreement status will be updated.
Transaction IP New Functionality /IRM/IPxxM Tolerances
A tolerance condition type has been added at the item level. It
also allows for flexible calculation of tolerances based on an access
sequence instead of a flat value.
Transaction IP Enhancement /IRM/IPxxM Workbench
When in the transactional IP workbenches, if the middle section is
collapsed, the item detail display will be expanded. More fields
within the layout will be able to be seen.
Page 12 of 12