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 optionsAt header level:
Changes to name, start date and number of periods.At item level:
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.At plant level:
Adding and deleting of plants.
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.