The initial screen and the output list of transaction MD4C have a new layout after the release upgrade to ERP2004 (as of Support Package 4 for ECC 5.00). Some functions are missing, others have been added.
- The interface of the order progress report (transaction CO46) from the production order area has not been changed. To enable the enhanced usability, you can use the related order report (transaction MD4C). The basic functions of the order progress report have been included in this report.
The interface is changed to enhance usability. Furthermore, SAP intends to design all interfaces of the standard system in such a way that blind persons or persons suffering from vision impairment can use the transaction (accessibility) after installing the suitable additional software. Up to now, the interface layout of the order report (transaction MD4C) and of the order progress report (transaction CO46) does not allow for this option, or only under very restricted conditions.
Redesign and enhancement of transaction MD4C taking new technologies into account
Detailed descriptions of the changes
- 1. Switching to the "old" display of transaction MD4C
You can still use the old display and interface. To do so, set the user parameter MTOLD in the user defaults to "X". You can call the user defaults under System -> User Defaults -> Own Data or using transaction SU3.
- 2. Entry screen of transaction MD4C
You can now select a profile on the entry screen that contains the existing settings for the availability calculation. Furthermore, you can use a profile to control further functions. Further information is available under point 4. If you do not select a layout on the entry screen, the availability calculation is executed using the receipt due date/time (planning day). This means that receipt elements are assorted using the MRP-relevant availability date/time. The requirement is then covered by the first receipt, independent of whether this is a planned or a fixed receipt. This logic is in accordance with the calculation of the available quantity in the stock/requirements list. In addition, the safety stock is included in the availability calculation.
- 3. Output list MD4C
In contrast to the existing display for a selected order or requirement, the system now displays the related component requirements as a multi-level tree structure (ALV tree). The way receipts and requirements are assigned remains unchanged. This means that the structure of the order tree is dependent on the current planning situation, on the stocks and order quantities.
To call further, more detailed information about the structure of the order tree, choose the information button above the output list, choose Goto -> Info for Order Tree or choose F7.
- 4. Create a profile.
To create a profile, choose Production -> Material Requirements Planning -> Evaluation -> Define Profile for Order Report or call transaction OPPF.
You can use a profile to determine the type of the availability calculation
-
- a) by receipt due date/time or
-
- b) by ATP logic and
-
- c) with safety stock or
-
- d) without safety stock .
Furthermore, you can define which type of exceptions is to be determined and issued:
-
- a) MRP exceptions: the same exceptions as in the "old" transaction MD4C.
-
- b) Quantity variance exceptions: The determination of quantity variances was transferred from the order progress report (transaction CO46). An exception message is issued for production orders only if the operation quantity variance between the planned yield and the yield of the last finally confirmed operation exceeds the defined percentage value.
-
- c) Schedule variance exceptions: In addition to the exceptions that are in accordance with the MRP logic, schedule variances can be determined as in the order progress report:
Production order: The actual or the expected delay exceeds the limit value set in the profile.
Planned order: The basic start date or basic finish date is in the past.
Purchase requisition: The date or the requested delivery date is in the past.
Sales order item: The requested delivery date of the earliest delivery-relevant request schedule line is in the past.
- 5. New functions in transaction MD4C
The use of the ALV tree enables a hierarchical display. The order report becomes less confusing. Furthermore, the ALV tree provides standard functions, for example, the creation oo user-specific layouts.
- 6. There is a function missing in transaction MD4C that was provided by transaction CO46.
-
- a) Selection screen
-
- You cannot select several sales orders or sales order items.
-
- The plant and the material are not available as selection criteria.
-
- Elements outside of the product structure are not selected.
-
- Elements assigned to a production order are not selected.
-
- b) The following elements are not taken into account for performance reasons.
-
- Reorder point material
-
- Bulk material
-
- Non-material items
-
- By-product, co-product
-
- Phantom assemblies
-
- c) Output list
-
- The output list provides less fields for selection than transaction CO46.
-
- d) Other missing functions as compared to transaction CO46
-
- Lists cannot be refreshed. Instead, you must exit the transaction and call it again.
-
- You cannot release a production order directly from the output list. Instead, you can branch directly to the change mode of an order and release the order there.
-
- You cannot branch to the sales and distribution document overview.
-
- You cannot branch to the pegged requirement overview.
-
- You cannot branch to the purchase order history overview.
-
- You cannot branch to the material document of a material
- 7. Additional documentation
Further information is available in the SAP Library under the subject production planning and control (PP). Related 777192 contains the relevant path. Remark
This does not represent any promise or obligation on SAP's part to make all elements of the software accessible, nor any warranty that the software becomes accessible after the application of patches or the development using the procedures mentioned in the note.