IRMIPM 40B: Patch 007 Notes

Transcription

1 IRMIPM 40B: Patch 007 Notes User functions have been added to the pricing sheet. There are now two methods to the existing interface for key fields checks. One is to provide a button on the rule sheet and the other is to execute the button. This allows a button to be added to a rule such as "Members" which will show the active membership list for a rule based on the values submitted in /IRM/GMLM. Another example is to do the same for material group and list the materials in that material group. A Price Book can now be triggered within an agreement. This is available only if Foundation Data is licensed Sales documents such as contracts and quotations can now be triggered from an agreement. Documents can be created that can be used in call-offs. Confirmations can now be recorded for partners. This controls when a partner was notified, when confirmation is expected, reminders, etc. A new field was added for the reason for release status. The lifecycle and phases of an agreement are now able to be tracked within an agreement. The next phases of a typical flow for that agreement type are also listed for reference purposes. A document flow is also available for the lifecycle changes. Multiple notifications per agreement were not allowed. There is a new customizing table to set this up. There is a popup now if multiple output exists to allow the user to select the correct one. If only one is configured, then it will go directly to the desktop document. Win/loss reasons were only tracked in notes in an agreement. There is now a Win/Loss Reason on header of the agreement. The planned duration was shown in the agreement for milestone dates. This is now fixed. There was no control number on an agreement. There is now a 30 character field for the control number on the agreement. Dates were calculated based on the calendar in the date type configuration. Now they are calculated based on the calendar in agreement if one is specified. The "Fixed Value" date, value days are now also included. It is changeable only from mass maintenance. The fixed value date means "Guarantee date". Value days means "Notice before price increase". Vistex, Inc. Page 1 of 12

2 Customizing is now available for allowed payment methods per agreement type. It will only display the payment methods that are customized for the agreement type in the drop down in agreement creation. If none are defined, all allowed for the country of the sales organization will be displayed. Administrative data and other fields that were added in this support pack are also available as selection fields in the agreement search screens. The contract term is now shown in the unit of period maintained in agreement type customizing. The contract term is displayed for reference. There is a new customizing table for information for the Renewal Type for the agreement. Exchange Rate, Conversion Date and Exchange Rate Type are now three separate fields in the terms section in the agreement. In the "Extras" menu, navigation to the Membership and Product List Maintenance transactions are available within the agreement. Basic measures are now available for the Price Summary Sheet in the agreement. This allows users to define their own scripts to calculate scores and return statuses to agreements for workflow. Currently only rules are available for the calculation of measures. Exchange Rate Parameters were added to the Customer Settlement Parameters, Vendor Settlement Parameters, and Agreement Settlement Parameters transactions Scales did not work in create or change mode. Standard scale subscreens are now called at the time of rule entry. The summary sheet was not synchronized with the rules. User fields and formulas on summary sheet were not called due to performance reasons. Now a button is provided for a refresh, the user fields are filled in, and the formulas are called when it is selected. If a condition record was deleted outside of the agreement, the summary sheet would not reduce the number of rules for the condition type/condition table combination. That is now fixed. If data was not entered in all blank rows when selecting a number of rows during rules creation, a hard error would occur until the lines were deleted. Now blank lines can be left in the rule entry screen. Vistex, Inc. Page 2 of 12

3 The unit of measure (UOM), currency, and basis on the rules line was not defaulting in correctly. Now a certain logic is followed for defaulting UOM and currency and basis. UOM is based on condition alias table, then sales unit of measure from the material master, and finally base unit of measure. Currency is defaulted based on the condition alias table and then company code currency. Basis is based is on the alias table only. Additional fields in the KOMG derivation BADI were added to allow users to influence KOMG fields, like date. Also, a call up point in the BADI is now provided. Calls to formulas have also been revised to provide call up points and other parameters. BSPs Enhancement /IRM/IPxxASPM_WS Claim Request Enhancement /IRM/GPXREF Claim Request Enhancement /IRM/GMXREF A lock level for M condition types could not be maintained. The lock level logic has been revised to lock at the field level specified, e.g. 2 or 3, etc. This means that for condition type/table Sales Organization/Distribution Channel/Customer/Material (VKORG/VTWEG/KUNNR/MATNR), if the lock level is 2, the lock is at Sales Organization/Distribution Channel (VKORG/VTWEG) level. If it is lock level 3, we lock at the Sales Organization/Distribution Channel/Customer (VKORG/VTWEG/KUNNR) level. If an agreement was saved and no rules were changed, they were not being sent to the save user exit. Even if no rules are changed on an agreement, the rules are now available in the save user exit. Changes to organizational data after an agreement has been created were not allowed. Now changes can be made after creation. The primary partner was not in the field catalog of the overview screen. Now it is available and there is a name on the worklist for a primary partner and an owner. If a condition type allowed for deletion from the database, it was just being flagged for deletion in the agreement. Now the deletion of a condition record is based on the customizing settings. A new Web transaction has been provided to allow creation and maintenance of an agreement from the Web. Partner cross reference tables are now provided for flexibility. This allows a catalog of mapping of customer numbers to SAP customer numbers. Material cross reference tables are now provided for flexibility. This allows a catalog of mapping of customer material numbers to SAP material numbers. Vistex, Inc. Page 3 of 12

4 Claim Request Enhancement /IRM/GUXREF Unit of measure cross reference tables are now provided for flexibility. This allows a catalog of mapping of customer unit of measures to SAP unit of measures numbers. You can now enter claim periods for a line item to denote a range of dates instead of just an individual date. If claim request type is marked for "Parallel UOM", a user can enter a parallel quantity and a parallel UOM on the claim item. For example, this is required for food items where you have to track cases and pounds. Two date types were added: Check with planned end date for submission and check with services rendered date for planned end date. These date types come from the agreement and are used to check whether the claim was submitted in the allotted time frame and if the services rendered date was within the allotted time frame. There are now 2 fields in the claim: agreement entered and agreement determined. If a valid agreement is entered in the requested field, it is copied to agreement determined field automatically. If it is invalid, the correct agreement can be entered manually. Reverse postings (un-post) can now be done for a claim request. First, it checks whether subsequent documents exist for claim request. If there are none, the post status is set to space and saved. These can be done from the menu path or as a resolution. A claim cannot be reversed if a billing document exists for a claim request. The Sales Incentives (SI) and Customer Rebate (CR) Workbench was added to Extras menu in the claim request. The transaction date is now available in header mass change in the claim request. The counter in the worklist is updated accordingly based in the header and the item view. Navigation to the Partner display was added to the Extras menu in the claim request. Navigation to the customer creation transaction (XD01) was added to the Extras menu in the claim request. Navigation to the business partner creation transaction (BUG1) was added to the Extras menu in the claim request. Navigation to the Partner Cross Reference transaction (/IRM/GPXREF) was added to the Extras menu in the claim request. Vistex, Inc. Page 4 of 12

5 Navigation to the create material transaction (MM01) was added to the Extras menu in the claim request. Navigation to the customer material info record was added to the Extras menu in the claim request. Navigation to the material determination transaction was added to the Extras menu in the claim request. Navigation to the Material Cross Reference transaction (/IRM/GMXREF) was added to the Extras menu in the claim request. Navigation to the material listing/exclusion transaction was added to the Extras menu in the claim request. Navigation to the Unit of Measure Cross Reference transaction (/IRM/GUXREF) was added to the Extras menu in the claim request. It is now possible to have a claim with 0 quantity. This is required, for example, for claims that are based on advertisement, display fees, etc. There is a new BADI method for authorization checks for a claim. A new field for "skip document checks" has been added. If this field is selected, all checks including document checks will be skipped. Checks on demand will only check items that are marked on the item grid. Activity '39' has to be allowed for skipping checks. A new function module for changing any field of a claim request has been created. This is required if a customer uses their own front end for creating claims and wants to create claims in IP via a BAPI. LIS updates only took place at posting. Now LIS update takes place at all times not just after posting. For example, if a claim is being processed, it will still be taken into account when a new claim is entered when checking purchase history versus claim history. Thousands of line items on a claim make it cumbersome to navigate. Now the line item screen is expanded when the middle section on the claim is condensed. Dynamic upload errors were not being handled correctly. Error lines are now skipped. Formatting errors will cause a stoppage and no lines will be added. Warnings and error lines are skipped and shown in message log. The sold to party and submitted by were not entered in one subscreen. If a sold-to is entered, the submitted by is determined. If a submitted by is entered, the sold-to is defaulted in from the submitted by if sold-to is not entered by user. Vistex, Inc. Page 5 of 12

6 Milestone dates should not have a duration. Now no duration is shown for milestone dates. Partner roles were coming from header procedure. Now they are coming from item category partner determination procedure. Plant, profit center, and business area determination was incorrect for a claim item. It is now fixed. The "No Submitted by" flag was deleted from the database and screen. When determining which partner is being entered in a claim request, the system will follow a set sequence of checks. 1. Look if it is a valid customer/vendor in SAP. 2. Look for IDs in the order for the ID types (which is based on characteristics) customized in the new Partner Search Sequence. 3.Look in the new cross reference table using the submitted by customer first and then the sold to customer and finally the cross partner. If the "ID Type" is specified, different checks are done. 1. Look for the IDs on the customer/vendor master directly. (In the case of a business partner role, go to the ID table.) 2. Look in the new cross reference table with ID type using the submitted by customer first and then the sold to customer. If nothing is found in any of the steps, it is considered an invalid partner. When determining which material is being entered in a claim request, the system will follow a set sequence of checks. 1. Look if it is a valid material in SAP. 2. Look for a customer/material info record using the submitted by customer first and then the sold to customer. 3. Look for a material substitution. 4. Look for alternate ids on the material master. 5. Look in the new cross reference table using the submitted by customer first and then the sold to customer and finally the cross partner. 6.Finally, the product listing/exclusion is checked. If the "ID Type" is specified, different checks are done. 1. Look for the IDs on the material master directly. 2. Look in the new cross reference table with ID type using the submitted by customer first and then the sold to customer. 3. Product Listing/Exclusion is performed even if the ID type is entered. If nothing is found in any of the steps, it is considered an invalid material. When determining which Unit of Measure (UOM) is being entered on a claim request, the system will follow a set sequence of checks. 1. Check if it is a valid unit in table T Look in the new cross reference table using the submitted by customer first and then the sold to customer. If nothing is found in any of the steps, it is considered an invalid UOM. Vistex, Inc. Page 6 of 12

7 Claim Request Performance /IRM/GCRM Composite IP Enhancement /IRM/IPxxCWB Composite IP Enhancement /IRM/IPxxCWB Composite IP Enhancement /IRM/IPxxCWB Composite IP Enhancement /IRM/IPxxCWB Composite IP Enhancement /IRM/IPxxCWB Composite IP Enhancement /IRM/IPxxCIP Several performance enhancements have been applied to speed up pricing, checks and saving a claim request. Settlement and Alert Formulas are now at the version level instead of deployment code level in composite. Additional LOOKUP formulas have also been provided: LOOKUP next scale, next scale base and LOOKUP AND CALCULATE. It is now possible to define user methods. In the Composite Workbench, formulas can be copied from one deployment code version to another. Subcomponent characteristics and key figures can be defined and tracked for a component. Subcomponent key figures can also be transferred to component key figures The screen layout for a deployment code component can now be created without using the screen builder or ABAP. The following is supported: define tracking key figures group, define column group, define column sub-group within column group, define columns, and define remarks for tracking key figures. It is now possible to rank participants based on any tracking key figure. Ranking formulas are provided for granting additional amounts based on the rank attained. Ranking can only be invoked from collective processing and mass processing Lower-level participants can now come from IP Hierarchies. Instead of defining lower level participants in the participant tracking screen, they are defined in the hierarchy and pulled from it during composite IP runtime. IP Hierarchies, SD Hierarchies, MM Hierarchies, Member Types, and Channel Partner Types can be used. The additional and derived fields are also copied into participation fields. Composite IP Fix /IRM/IPxxCIP Composite IP Fix /IRM/IPxxCIP Composite IP Fix /IRM/IPxxCWB The system creates /IRM/Ipxxx tables for audit ability of Composite IP postings. These tables now have date and time stamps for transferring data to BW. Posting in a composite plan was being done at the customer/vendor/employee level independent of the participant. Posting is now checked for the participant and not for the customer/vendor/employee. This is especially the case if the participant is an agreement or material. Parameters on a participant such as attribute, territory, agreement, company code, etc. were added to the mapping customizing transactions. Vistex, Inc. Page 7 of 12

8 Composite IP Fix /IRM/IPxxCIP Composite IP Fix /IRM/IPxxCIP Matrix Processing Fix /IRM/GMXM Membership Enhancement /IRM/GMLM Membership Enhancement /IRM/GMLM Membership Enhancement /IRM/GMLM Membership Enhancement /IRM/GMLM Membership Enhancement /IRM/GMLM Membership Fix /IRM/GMLM Membership Fix /IRM/GMLM Membership Fix /IRM/GMLM Navigation to IP documents and agreement from individual tracking did not work if the IP class of the document or agreement was not the same as the composite IP class. Standard navigation is only possible to IP documents and agreements based on IP Class of the deployment code. There is now a function module for navigating to the agreement based on which type it is set up as when it is customized. If multiple classes are found, an error is given. Navigation within a deployment code to an agreement that has the new pricing flag set displayed the agreement using the old pricing format. Now the navigation is to the agreement workbench and displays the new pricing format with the rules tab. The "freeze" width was not set appropriately in Excel maintenance when the value and description are shown. It is now fixed. In addition to customers and vendors, Business Partners (transaction code BUG1/2/3) can now be included as members. When the membership list is posted, it now also sends across the member type and channel partner type to the condition record if applicable. Members can either be copied from another trade organization or transferred from another trade organization now. In a transfer, the validity of the member in the source trade organization is terminated as of the date of the transfer. If customer/vendor/business partner does not exist, they can be created directly from the membership list now. Notification can now be created for a membership list, for example, to notify a trade organization which members were accepted, rejected, etc. There was no way to know if a member was already present in the membership list when they were being proposed. Now members that are already present in the membership list are highlighted. There was no way to upload addresses of the members. Now a field catalog is provided for address upload. It can be shown in an excel upload. All member addresses will be saved if provided on the excel sheet regardless of whether they are valid or invalid. When the header screen in the membership list is collapsed, the members screen was not expanded. Now the member screen is expanded. Vistex, Inc. Page 8 of 12

9 Membership Fix /IRM/GMLM Membership Fix /IRM/GMLM Membership Fix Additional fields for a membership list are were not available during a load from Excel. They are automatically available now. If multiple members are found during a search, the system didn't know which one to pick. Now a popup is provided in online processing and an error code is set if it is created in background mode. When determining which partner is being entered in a membership submission, the system will follow a set sequence of checks. 1. Look if it is a valid customer/vendor in SAP. 2. Look for IDs in the order for the ID types (which is based on characteristics) customized in the new Partner Search Sequence. 3.Look in the new cross reference table using the submitted by customer. If the "ID Type" is specified, different checks are done. 1. Look for the IDs on the customer/vendor master directly. (In the case of a business partner role, go to the ID table.) 2. Look in the new cross reference table with ID type using the submitted by customer first and then the sold to customer. If nothing is found in any of the steps, it is considered an invalid partner. The new functionality is similar to the confirmations within an agreement. There is now a way to track the participant responses as they confirm their participation. /Attributes Enhancement /IRM/IPxxPA /Attributes Enhancement /IRM/IPxxPA A BADI is now provided for notification to check participation. /Attributes Enhancement /IRM/IPxxPA More than one type of notification is possible within a composite plan. /Attributes Enhancement /IRM/IPxxPA /Attributes Fix /IRM/IPxxPA /Attributes Fix /IRM/IPxxPA /Attributes Fix /IRM/IPxxPA /Attributes Fix /IRM/IPxxPA Vistex, Inc. Page 9 of 12 A new transaction is available to create hierarchies independent of SD or MM. Hierarchies are created once and can be used in multiple deployment codes which reduces maintenance efforts. If a material was a participant in composite processing, they could not have an agreement assigned to them. Now a material can have an agreement assigned in participation tracking. If a participant was initially created as a root level and now is moved to a lower level, the formulas and fields that are not eligible at lower levels were not removed. Now they are initialized upon save. Reassignment of lower level participants was not allowed if postings were done at the root level. Now reassignment of lower level participants is allowed regardless of postings for the root level. The BOR object by deployment code/version was not published. It is now published.

10 Product List Enhancement /IRM/GPLM It is possible to copy nodes from a product list to another product list from the Review tab. Product List Fix /IRM/GPLM Product List Fix /IRM/GPLM Transaction IP Enhancement /IRM/IPxxM Transaction IP Enhancement /IRM/IPGINDX Transaction IP Enhancement /IRM/IPxxM Transaction IP Enhancement /IRM/0IPG8C When determining which material is being entered in a product list submission, the system will follow a set sequence of checks. 1. Look if it is a valid material in SAP. 2. Look for a customer/material info record using the submitted by customer. 3. Look for a material substitution. 4. Look for alternate ids on the material master. 5. Look in the new cross reference table using the submitted by customer. If the "ID Type" is specified, different checks are done. 1. Look for the IDs on the material master directly. 2. Look in the new cross reference table with ID type using the submitted by customer. If nothing is found in any of the steps, it is considered an invalid material. If a material is marked for deletion and it is added to a product list or in a product list, the system did not flag anything. Now an error code is set for the line item. Parallel Qty and UOM (Catch Weight) is now supported in the IP document. It uses the same logic that was already available for the claim request. There were several issues with the Source Document Index. The selection screen has been revised to have 4 tabs and to show 3 selections from the index table itself separately. If the net value for a document is zero, internal accrual/settlement only is available for contra postings. Contra postings can be configured per IP type to transact a contra posting only or to transact the contra posting only if the net value is 0. Company code has been added as a limiting filed to the IP correspondence trigger table Transaction IP Enhancement /IRM/IPxxM After the pricing BADI, two new BADI methods were created to park or settle. Transaction IP Enhancement /IRM/IPxxM Claim requests can now be a source document for a customer rebate (CR) IP document. Transaction IP Enhancement /IRM/IPxxM Item partners are now available in IP document. It takes the partner procedure from item category control customizing transaction. Transaction IP Enhancement /IRM/IPxxM The wrong date was being used for accrual reversals. Now the posting date of accrual for is used first and if that fails due to a closed period, the posting date is used instead of the system date. Vistex, Inc. Page 10 of 12

11 Items within an IP document that had any accounting document tied to it were being hard deleted. Now they can only be soft deleted after the relevant accounting documents are reversed. A deletion flag was added to the fields in the ALE grid field selection. Transaction IP Fix /IRM/IPxx34 The statistics date was not being stored in the IP document item tables. Now this date is transferred from the source document. It is also being filled it from item table into MC tables for LIS updates. This date is not available in Purchasing, so it is not available in the Purchasing Rebate (PR) application. The Accrual and Park Status was not provided in the reconciliation transactions. It is now provided. Conditions were not getting deleted if all the items from the IP document were deleted. This is now fixed. SAP has a limitation of 999 lines per accounting document and claims and IP documents do not have that limitation. Now during accrual and settlement, multiple accounting documents are created if accounting lines exceed 999. This is done internally by the program. When copying condition records from a source document, the statistical indicator was also being copied. Now it is based on destination pricing procedure. Condition records with a value of "Tax" (D) and "Customer expected price" (J) in the condition class are not copied over. Authorization checks are now being done during search and worklist processing. Errors were occurring when we added documents from bottom screen to worklist within the IP document workbench. They are now fixed. When the Corrected Agreement field (KOMP-AKTNR) changes in the IP document, the document is repriced. Currently navigation to the agreement workbench within an IP document is only to the one in the same IP application. For example, you can only navigate to /IRM/IPBBASP from /IRM/IPBBM. Now you can navigate to the correct agreement workbench from the IP workbench based on the configuration of the agreement type in the IP agreement configuration. Vistex, Inc. Page 11 of 12

12 Transaction IP Internal /IRM/IPxxM Transaction IP Internal /IRM/IPxxM Transaction IP Internal /IRM/IPxxM Transaction IP Internal /IRM/IPxxM Transaction IP Performance /IRM/IPxxM Transaction IP Performance /IRM/IPxxM Transaction IP Performance /IRM/IPxxM Transaction IP Performance /IRM/IPxxM A sales line item may have lower level components that are not explicitly listed on the sales order. In some cases, these items are needed to calculate incentives or chargebacks. Those details can now be stored in a source document staging table. The dependence from the source document item during IP document processing has been removed. This allows the IP document line item creation process to look at the staging table first then the line on the source document if nothing exists so the calculations can be done at the correct level. VBKLT in KOMK is now filled during IP pricing preparation as it is required in the agreement log and agreement resolution. A new 10 character field called "Corrected Agr Number" is created (KOMP- AKTNR). A new field called "User Event for Payment Schedule" was added. It is an information field that the user can populate during online entry or during a user exit. There is a customizing table for this as well. The locking logic was changed to lock at recipient level instead of each individual IP doc to improve performance during mass processing. To improve performance, a flag was provided to avoid reading addresses of each partner during the reading of source documents. The entire IP document was being repriced when we process individual items from workbench. Now the system will only reprice the line being changed instead of the complete document. This was a big performance improvement for IP documents. The entire IP document was being repriced when we process individual items from workbench. Now, the system will only reprice the line being changed instead of the complete document. This was a big performance improvement for IP documents. Vistex, Inc. Page 12 of 12