SAP Enhancements are used to go to customer-specific program sections from the standard SAP System, thereby enhancing the standard function with customer-specific requirements.

Customer-specific coding is managed as isolated objects in the customer namespace.

Enhancements are available for planning the following functions:

• WISPL004 Change function for promotions
• WISPL005 Calling function after creating a promotion: This functional enhancement can be called when a promotion was created in manual planning. Information about the promotions header, the interface to be generated, the planning layout to be generated and the data that is selected in the planning layout, is all sent to the customer enhancement. All the data is then made available to the user, in a structure. A table containing the relevant structural information is also sent to the customer enhancement.
• WISPL006 Calling function after creating a promotion in planning

• Menu functions

• WISPL007 Running a customer-specific menu function in manual planning:
  Prerequisites: (1) A specific menu was assigned to a planning layout in Customizing for planning. The menu contains the new function codes. (2) The new function code is also displayed for the relevant layout in Customizing for planning. For more information, see the documentation in Customizing).

To fill the relevant user exit, create an enhancement project using ABAP Workbench ® Utilities ® Enhancements ® Project management, transaction CMOD. Then assign the enhancements to the project. Maintain this in Customizing for Merchandise and Assortment Planning using Function enhancements - Planning.

Use the customer exist to import data from different SAP applications, and then make these available in manual planning.

For example, data from CO-PA (for example, costs, revenues, data from conditions tables prices, rebates) is imported and then used in the planning layout as additional key figures.

In this example, the values in the Price reduction field for CO-PA should be imported from results area S001 (table CE1S001) and placed in the field for the customer-specific additional key figures in planning layout PLMNI02.

The coding for this example may be as follows:

************************************************************************************

* INCLUDE ZXWXPU03 *

************************************************************************************

* The following exit imports data from the results area in CO-PA *

* to Merchandise and Assortment Planning (MAP) *

* for information purposes. In the example, the data contained in the Price reduction value *

* field in CO-PA is imported from results area S001 (table *

* CE1S001) and placed in the field for the customer-specific additional key figure. *

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

* Scenario: Importing Data from CO-PA: *

* To import data from CO-PA, ensure that the characteristic for data from CO-PA *

* is defined in the results area as a characteristic *

* or that it is defined using another characteristic *

* (for example, article => merchandise category). *

*************************************************************************************

* Data declaration (result area table) *

TABLE: ce1s001.

* Internal structure for combining the date fields *

* Fiscal year and 3-character calendar month. *

DATA: BEGIN OF itab,

* Fiscal year and + 3-character calendar month. *

DATA: str3(7) TYPE n.

* Type conversion *

FIELD SYMBOLS: <praba>.

DATA: praba TYPE P DECIMALS 2.

* Planning layout query as additional key figures do not *

* have to be used in all planning layouts. *

CASE i_form.

* Read internal table "t_itsel_max" that contains the selection characteristics

* for manual planning and enter the data in table ITAB.

* Link fiscal year and period

* Read the CO-PA table using the selection characteristic key for

* manual planning and copying data to the export parameters.

* Additional planning layout names can be queried

* if they contain different additional key figures.

ENDCASE.

********************************END-OF-CODING******************************

Planning layout PLMNI02 is structured as follows:

You can use information about characteristics (calendar month, fiscal year, article number) to read the table for the results. The data transferred to the key is then prepared in manual planning.

When programming the customer exits, ensure that all characteristics are selected if they guarantee clear access to the table (CO-PA) that is to be read.