PriceMarkdownPlan

The Business Objekt Markdown plan is a specification of planned
price reductions (amd, if required, price increases) for sales materials within a certain period of time.

The markdown plan can also contain the planned sales quantities and values.

Structure

A markdown plan can consist of several items that each contain the
planned sales quantity and the planned sales value of a sales material.


Items can be structured hierarchically. In this way, generic materials can be divided up according to their variants.


An item can comprise several price phases. A price phase contains the
sales price planned for a period of time as well as, if required, the sales quantity and the sales value.


To the markdown plan are assigned the plants to which the planned price reductions are to apply.

Comment

The markdowns can be determined from a markdown rule.
Through sales pricing valid conditions can be generated from the
planned prices.

Example
With a markdown plan you can control the selling-off of material
stocks. In the case of seasonal materials, e.g. fashionable articles,
in particular, you can ensure, through well-timed markdowns, that at the end of the planning period all the stocks have been sold.

Available Methods

• ChangeRoughPlanning : Process Markdown Plan (Rough-Cut Planning) [ BAPI_PRICEMARKDOWNPLAN_CH_R_PL ]
  
• CreateFromData : Create [ BAPI_PRICEMARKDOWNPLAN_CREATE ]
  
• GetDetail : Detailed Data for a Markdown Plan [ BAPI_PRICEMARKDOWNPLAN_GETDETA ]
  
• GetList : List of Markdown Plans [ BAPI_PRICEMARKDOWNPLAN_GETLIST ]
  

ChangeRoughPlanning

You can use this method to process an existing markdown plan.

The method allows you to process data at header, item and distributionchain/plant level (rough-cut planning). It is not possible to process price phases.

The document number of the markdown plan, and tables containing the old
data (determined with method "PriceMarkdownPlan.GetDetail") and new (changed) data is transferred to the method.

The system first checks whether the data that was transferred as "old"is the same as that on the database. If it is not, processing iscancelled and a message is returned. Only if the data is consistent is
the old and new data compared and the markdown plan is updated with the new data.

Processing options

Changes to name, start date and number of periods.

Changes to start date of first price phase, markdown rule, final price,
price point indicator, planned initial stock, and planned sales quantity.

Adding and deleting of items.

Adding and deleting of plants.

Notes

The header data must always be transferred in full.

To keep the transferred dataset as small as possible, not all old and
new data has to be transferred at item, phase and plant level. It issufficient to transfer the data that needs to be changed. The methodthen returns a warning. However, note that processing of the markdownplan is then not necessarily based on the current data on the database.

The authorization object checked is "S_TCODE" (authorization for transaction "WMF2").

No Commit Work is triggered in this method. As a result, after themethod is called, BAPI "BAPI_TRANSACTION_COMMIT" must be called to trigger the update.

CreateFromData

You use this method to create a markdown plan.

For each material, you have to enter the distribution chain via whichthe material is to be sold. If prices are to be activated later at plant level, you can enter the plants in a separate plant table.

It is also possible to enter the starting times and the quantities(planned sales quantities and initial stocks), as well as the salesprices. If a sales price is not entered, the system suggests one. Inaddition, you can enter a markdown rule for each material. This
markdown rule defines the price phases. If you do not enter a markdownrule for a material, the system uses the default markdown rule from the markdown type.

The method carries out all the necessary consistency checks and returnsall messages as a return table. The return values and their meanings are listed in the parameter documentation.

Notes

The entry of a markdown type is mandatory so that the system can determine the price phases.

Authorization object checked: S_TCODE (authorization for transaction WMF1)

A Commit Work is not triggered in this method. As a result, after the
method has been called, a general BAPI "BAPI_TRANSACTION_COMMIT" must be called to triggered the posting.

GetDetail

This method provides the detailed information for a particular markdownplan needed for processing. This relates to header, item, phase, and DC/plant data.

Notes

Authorization object checked: S_TCODE (authorization for transaction WMF3).

GetList

This method provides you with a list of markdown plans that match the transferred selection options.

You can limit the selection of markdown plans by entering the following criteria:

You can limit the number of hits by using the optional

"MAXROWS" parameter.

As a result, you receive a list of markdown plans containing the following data:

Notes

Authorization object checked: S_TCODE (authorization for transaction WMF3).