Here we would like to draw your attention to MD04 transaction code in SAP. As we know it is being used in the SAP PP-MRP (Material Requirements Planning – PP) component which is coming under PP module (Production Planning).MD04 is a transaction code used for Display Stock/Requirements Situation in SAP.
It comes under the package MD.When we execute this transaction code, SAPMM61R is the normal standard SAP program that is being executed in background.
Aug 13, 2014 A correction program should only be executed after you’ve gone through the following 4 point checklist. If you get specific instructions from SAP via the help portal. A correction program should only be executed after thoroughly testing in a quality/test system. This can be difficult because the unusual nature of these problems is such that.
SAP MD04 menu path
See the possible menu paths to access the same report by avoiding entering the transaction code. Path 1 Logistics → Logistics Execution → Information System → Goods receipt → Lists for Material Stock → Current Requirements and Stock List
Once you delete the delivery, the sales order will become open and the schedule line category throws the requirement which can be seen in MD04. To refresh the requirement in MD04, assign Reason for Rejection in sale order and save. Also run the correction report SDRQCR21.
Sep 28, 2016 It is a correction program.plz refer to following SAP note. Complete Report Documentation From /BEV/ up to A. Print Program: Advance Return for. Upgrade report for SCM Optimizer customizing for Releases SAP SCM 7.0+. Inbound Delivery No Goods Movement In MD04.
79210 Correction program: Delivery item poss. 521164 MD04: Correction EKES-MENGE after reversal of goods. 214031 Composite SAP note: Correction.
This is contained in note 359469, to initialize some EINE fields with the help of SAP development support. It is from note 208976, and to archive the purchasing organization data/plant data (EINE). ZZCOMPLETEASN, ZZCORREKESDABMG and ZZCORREKESEKBE. They are from note 636853, to do correction of MRP relevance of inbound.
Free 3d female model creator. Path 2 Logistics → Logistics Execution → Information System → Shipping → Lists for Material Stock → Current Requirements and Stock List
Path 3 Information Systems → General Report Selection → Materials Management → Consumption-Based Planning → Display Stock/Requirements Situation
Path 4 Information Systems → General Report Selection → Production Planning → Material Requirements Planning → Display Stock/Requirements Situation
Path 26 Logistics → Production → KANBAN → Environment → Inventory Management → Environment → Stock → Stock/Requirements List
Path 27 Logistics → Production – Process → Production Planning → Demand Management → Environment → Stock/Requirements List
Path 28 Logistics → Production – Process → Production Planning → MPS → Evaluations → Stock/Reqmts List
Path 29 Logistics → Production – Process → MRP → Evaluations → Stock/Requirements List
Path 30 Logistics → Production – Process → Process Order → Environment → Process Planning → Environment → Stock/requirements list
Path 31 Logistics → Production – Process → Process Order → Environment → Stock/Requirements List
Path 32 Logistics → Production – Process → Process Planning → Requirements → Process order → Environment → Stock/Requirements List
Path 33 Logistics → Production – Process → Process Planning → Environment → Process management → Environment → Process Orders → Environment → Stock/Requirements List
Path 34 Logistics → Production – Process → Process Planning → Environment → Stock/requirements list
Path 35 Logistics → Production – Process → Process Management → Environment → Process Orders → Environment → Stock/Requirements List
Path 36 Logistics → Production – Process → Process Management → Environment → Process Planning → Requirements → Process order → Environment → Stock/Requirements List
Path 37 Logistics → Production – Process → Process Management → Environment → Process Planning → Environment → Stock/requirements list
Path 38 Logistics → Project System → Resources → Capacity Requirements Planning → Requirements → Production Order → Control → Stock/Requirements List
Path 39 Logistics → Project System → Material → Planning → Stock/Requirements List
Path 55 Accounting → Project System → Information System → Material → Stock/Requirements
Path 56 Information Systems → Project System → Material → Stock/Requirements
Path 57 Information Systems → General Report Selection → Project System → Material → Stock/Requirements
Transaction MD04 technical data table
Tcode
MD04
Purpose
Display Stock/Requirements Situation
Module
PP
Component
PP-MRP
SAP Package
MD
Program running
SAPMM61R
Screen No
300
Type
T
MD04 related transaction codes under SAP package MD
MD14 : Individual Conversion of Plnned Ord.
MS04 : Planning Scenario: Stock/Reqmts List
OMDF : C RM-MAT MD StgeCosts Lot Size T439L
OMDB : Marking Material for MRP Termination
MD03 : MRP-Individual Planning-Single Level
MP11 : Create message for direct production
OMDP : Check Consistency for Planning File
MD05 : Individual Display Of MRP List
MD06 : Collective Display Of MRP List
OMDK : C RM-MAT MD Error Allocation
OMD1 : C RM-MAT MD Mat.type/MRP procedure
OMDH : C RM-MAT MD Plnned Order Types T460D
MDRE : Checking Plnng File In BCKGRND Mode
MDLD : Print MRP List
MD90 : Maintain Number Range for MRP
OMIJ : C MRP Rounding Profiles
OMDN : C MM-MRP No.RangeInterval – PurReq.
MD11 : Create Planned Order
MD92 : Maint.No.Range for Reserv/Dep.Reqmt
OMDG : C RM-MAT MD Ord.ForecastRequmt T439P
MD04 related tables
T449B : Period split: language-dependent description
T458B : Description of exception messages
T457S : Block table for MRP and forecast run
T440F : Exception messages for the forecast
T460C : Order/Purchase order types for planned order
T460B : Special Procurement Key Conversion
PBVPV : Material index for consumption of planning
T450 : MRP transaction control
T438S : Text describing the range of coverage profile
PLAF : Planned Order
T461S : Planning strategies
T439L : Warehouse costs for MRP lot size
T438X : MRP group text
T457C : Transaction calls control
T024D : MRP controllers
T436A : Floats for scheduling
T438A : MRP Type
MDKP : Header Data for MRP Document
T439F : Handling of planning flag at abnormal termination
T457T : Description of MRP elements
Related References
Some Basic Questions & Answers
Which SAP Program will run when we enter tcode MD04? Program named SAPMM61R will run when we enter transaction code MD04.
What is the transaction code type of MD04? MD04 is a Dialog Transaction code type which is shortly represented as T.
31. ZCORR_EKETEINDT_CD
Sap Md04 In Detail
It is from note 1707638, to put a given date into scheduling dates that are initial and need to be corrected.
32. Z_A016_KONH_EVRTN
It is contained in note 1102280, and in order to correct the inconsistencies in table A016.
33. ZZ_CORR_MATCAT
It is in note 1839366, to reset several fields in table EKPO which contains unexpected value when publishing a contract with a material group line item (item category W/8) from SAP Sourcing.
34. Z_MM_QUANTITY_CHECK
You can use this report from note 1370784 to detect inconsistency when an inbound delivery is displayed in transaction MD04 despite goods receipt, or goods receipts are assigned incorrectly.
35. ZZGRREDI
It is from note 164004, and subjects the relevant items to a GR reassignment over the schedule line quantities.
36. ZCREEKUB
You can find it in note 369732 and use it to generate the missing entries in index table EKUB again.
37. ZZMRPAREA
You can run it from note 383042, to update the change in the SA when there are changes in the material master assignment of MRP areas.
38. ZKORR_EKEK_LWEMG
Adobe activation blocker. You can run it from note 1059195 to solve the termination DYNPRO_FIELD_CONVERSION “FLAB_HEAD-LWEMG” When you display or change the scheduling agreement release (SAR).
39. Z_KORR_RSDB_PUR
This is from note 953281 and used to correct the entries for purchase orders which are missing from table RSDB or for deleted purchase orders or enquiries.
40. Z_SET_ELIKZ2
You can use it from note 160525 to set EKPO-ELIKZ for PO so that “Issued quantity”, “Goods receipt quantity” and “Quantity delivered (stock transfer)” are the same.
41. ZKOREKKI, ZZEKKI01 and ZKOREKKI2
It is from note 304671, 92083 and 444557, to find the items which lead to update termination on table EKKI. Then the unnecessary entries in table EKKI are deleted from the database using test = ”.
42. ZCORRECTBEDAT1
It is from note 951328, to fill EKET-BEDAT fields which are missing from purchase orders.
43. ZKOGLMNG, ZKOWEMNG, ZKOMENGE, ZKORWEM2, ZKOWAMNG, ZKORWEMN3,ZKORWEMN4 and ZZ_CORR_EKET_WEMNG_WAMNG_GLMNG
They are from note 100690, to correct inconsistencies with EKET-GLMNG, EKET-WAMNG, and EKET-WEMNG.
44. ZEKPO_UMREZ_UMREN_EQ_0
It is contained in note 339267, to correct the redetermination of the conversion factors (EKPO-UMREZ and EKPO-UMREN) between the base unit of measure (EKPO-LMEIN) and the order unit (EKPO-MEINS).
45. ZELIMDBS
You can find it in note 104475, to subsequently set the “delivery completed” indicator in purchase order that have already been fully delivered, in order to prevent performance problems during ATP check or running MD04.
46. ZKOEKB1
You can find it in note 167242. It shows you which records of the purchase order history are linked incorrectly, and corrects the purchase order history.
47. ZKORVETV and ZZ_CLEANUP_VETVG
You can find them in note 61148, to set up or delete the table VETVG (Delivery Due Intex) for an individual purchase order.
48. ZDELESDUS
It is from note 197012, to delete the entire settings of a user to solve termination TSV_TNEW_PAGE_ALLOC_FAILED in ME21N.
49. Z_RSDBS
It is from note 670262, to insert in RSDBS all missing entries for a selected network.
50. ZCORREKAB2
It is contained in note 864839, to clean up the EKAB table and solve the update termination because of a duplicate table entry in the EKAB table.
51. ZKSTAPO1
You can run it from note 527995, to correct existing purchase orders that haven’t indicator EKPO-STAPO set, although the deletion indicator is set.
52. RM06HL04
You can find it in note 171331, when the quantity ordered in PR is not correspond to the quantity of the purchase order to which it belongs.
53. ZCORLOGS
It is from note 769394, to change the logical system in the “old” source list records after you transfer the source list maintenance into a central system.
54. ZCOREINA and ZDLEINAE
You can find them in note 836917, when there are info records with different info record numbers but with the same material number etc.
55. ZCORR_EINA_URZDT
You can find it in note 451114, to set the initial value of EINA-URZDT to ‘00000000’, if the value is ‘ ‘.
56. ZKORR_EINE_INITIAL
This is contained in note 359469, to initialize some EINE fields with the help of SAP development support.
57. ZKOREINA
It is from note 208976, and to archive the purchasing organization data/plant data (EINE).
58. Serial number pempro. ZZ_COMPLETE_ASN, ZZ_CORR_EKES_DABMG and ZZ_CORR_EKES_EKBE
They are from note 636853, to do correction of MRP relevance of inbound deliveries.
59. ZKOEKBEPO
You can find it in Note 431145, to reestablish consistency between the purchase order history (table EKBE) and the replenishment delivery.
60. ZCREA_EKBE_2
You can use if from note 433505, to reinsert the missing EKBE records.