Use
You use this function to configure the layout of the perishables planning list in line with the processes performed in your company and to meet the requirements of the users. You can, for example, add other fields or switch off columns. You can save the settings as a variant or have them appear system-wide.
Prerequisites
Before you can use this function, you must generate a perishables planning list (see
Perishables: Perishables Planning List).Features
You create a screen variant using transaction SHD0 and activate this using user exit EXIT_SAPMWOG1_015. The new screen variant is available system-wide.
See BC – Changing the SAP Standard:
You use transaction SHD0 (for example, for planning for individual stores) to create a variant of WDFR with a new transaction code of your choice. The new transaction is available system-wide under the new transaction code.
See BC – Changing the SAP Standard: Transaction Variants and Screen Variants
All users can change these table settings, save them as a variant and define their own standard settings. The width and position of each column can be configured.
See Getting Started: Creating Table Control Variants
The following describes where user exits are planned and illustrates where these can be used:
You can have the system find vendors on the basis of your own criteria and exclude them from further processing.
The system carries out the following processing steps for each vendor:
You can, for example, exclude articles for further processing that the user is not allowed to order.
You can, for example, remove all vendors except one from the list and make the vendor field ready for input.
You can, for example, change the results of a sales price calculation or transfer the data from an external system.
You can, for example, transfer data from an external system to R/3
You can add indicators such as chemically treated
You can specify a role-based screen layout
Using method TX_XX_FILL from BAdI WDFR_BADI you can find and prepare data for the perishables planning list. Steps 1 and 6 do not run when the BAdI is implemented.
You can, for example, have the system check if the order value is within the maximum limit set.
User exit EXIT_SAPMWOG1_014: change field content
You can, for example, have the system check if the order value of individual items or of the whole purchase order is below a certain limit and, if the limit is exceeded, prevent posting.
You can, for example, prevent posting.
See also:
Changing the SAP Standard (BC)