Part 2: What’s New for Sales functions in EHP1 for SAP CRM 7.0?


By Srini Katta

Share |

SAP updates

Learn about Practicality and Performance Improvement!

Continuing on from yesterday, I want to share some of the additional benefits that EHP1 for SAP CRM 7.0 offers for sales.

Tax Exemption: Maintaining tax exemptions based on exemption certificates issued by local, state and federal government was a challenge prior to EHP1. I know some companies that paid hefty penalties when they permitted tax exemptions without proper verification. There is a clear ROI of EHP1 if your company deals with customers that seek tax exemptions, as the tax exemption application supports exemption certificates. The tax exemption certificate feature is available as part of the SAP CRM billing and Tax Transaction Engine (TTE). The system allows period-based, amount-based and onetime tax exemption certificate functionality. You can maintain exemption reasons and reason codes in the application. You can also set up the validity of tax exemptions for certain products or services. It gives the user the capacity to assign the tax exemption certificate in the sold-to party account and the system automatically picks up the tax exemption status based on the preset criteria when an order is created. If necessary, you can setup a manual application of tax exemption after verification. The billing run picks up the tax exemptions, if there are any, from the orders and no redetermination occurs. All invalid tax exemption certificates will be removed from the billing document. The billing checks the type of tax exemption and process accordingly. For example, the billing engine ignores the tax exemption certificate in the subsequent billing document if it is only a one-time tax exemption only. The billing engine accumulates the exempt amount and links the billing documents with exemption for an audit trail.

Enhanced Data Retention Tool (DARTX): It’s great that your customers received tax exemption based on exemption certificates, which are duly verified. However, the tax audits are random and tax authorities can potentially audit taxes that are filed in the past based on agency laws. The timeframe could date back three years or more. This requires companies to be ready for a possible tax audit. SAP has built a tool similar to the tools that auditors use to extract, create, retain and store data that pertains to an audit at a later date. This tool was originally developed for ERP, but they have enhanced the tool to be used with SAP CRM and GTS systems called DARTX.

Performance Improvements in One Order Object: Prior to EHP1, the total value on the header was calculated whenever an order or contract was opened. During that process, all the item values were called and cumulated, which was a major hit on the performance. SAP made fundamental changes that have led to significant improvements in performance. With EHP1, a table holds the total values and no calculation happens when you display an order or contract. The same was true with the order status, which was derived based on the sum statuses of the line items upon an order or contract being opened. Now, the derived header status is stored in a table, avoiding the hassle of redetermination.

Asynchronous Save: Prior to EHP1, the save function was synchronous and the user had to wait until the save was complete. The system took considerable time to save large orders or contracts with hundreds of line items. Now, the update or save is done asynchronously. Users are no longer required to wait until the save is completed. You may be wondering what happens in the event that there is an error during the save process. In that scenario, an instant email is triggered to the user who called the update or save process in and was on order or contract when the error occurred). The email is sent to the user’s email ID.

Item Search in Large Orders and Contracts: In some industries, the sales order and service contract could have thousands of line items. Imagine the challenge of locating a particular line item for an update or review. This is no longer a challenge with the item search functionality delivered with EHP1. The search is similar to the advanced search. There is BADI available to enhance the item search further.

Large Transaction Mode: Prior to EHP1, all the line items were loaded and displayed in pages when a contract or order was opened in the WebClient UI. This required considerable time to display the order or contract. With large transaction mode, only the items on the first page are loaded and the remaining pages get loaded as the user navigates to those line items, resulting in the overall order or contract being loaded much faster. A user handling large orders and contracts will experience a decent amount of performance improvement with this mode. Through customization, you can set up the threshold of the line items to designate an order or contract as a large transaction.

Date Rules and their Calculation: Previously, the logic behind date rules was defined using XML rules parsing. In EHP1, direct ABAP processing replacing the XML parsing made the calculation faster and therefore improved the performance of an order or contract.

Kernel BADI’s: The most frequently called BADI’s are switched to the Kernel BADI’s. The code from existing BAdI’s should be moved to kernel BADI’s. This paved the way for a huge performance improvement.

BDOC Generation: Have you ever read schedule lines in an order? If yes, I don’t need to tell you how painfully slow it was. That is history now. EHP1 improved the reading with a secondary index.

Buffering of Middleware Parameters: You will notice significant performance improvement if your company is using SAP CRM for order generation and SAP ERP for order fulfillment. Remember the “the transaction is locked“ message you used to get while replicating the order from SAP CRM to ERP? Sometimes it seemed as if the order was locked forever. The process was slow as the CRM system read the middleware parameters from the database each time a replication was done. In EHP1, the middleware parameters (Table SMOFPARSFA) is buffered. There are significant performance improvements after you install the EHP1 in an integrated scenario.

I will stop here and will continue with Part III to highlight the pricing of performance improvements with IPC.

If you are interested in learning about how to take advantage of all the new features and functions of SAP Enhancement Pack 1 for SAP CRM 7.0, you can purchase the SAP Online Knowledge Product for your users. Click below for details:

Share |