- Correction Program For Md04 Sap Login
- Correction Program For Md04 Sap Jobs
- Correction Program For Md04 Sap Portal
- Correction Program For Md04 Sap Office
- Correction Program For Md04 Sap Portal
Mar 23, 2014. Update from: Note 1992885 was created based on the information from this document.Issues related to sales orders are very frequently observed on transaction MD04. This document provides a brief explanation and the solution for the most commonof these issues:1 - A sales order/delivery is already completed or deleted but it still appears on MD04. What is the use of SDRQCR21 (SAP note 1166713) standard SAP program? I have got a issue with this program. The issue (problem) stated is as follows: Program SDRQCR21 was ran on material XYZ for plant ABC. It did not work. The item is still on MD04. Unable to use material as it is being held on the MD04. Mar 31, 2016 This WIKI has been moved to the ERP Manufacturing space. You can find on the link Inconsistencies for planning elements and display problems on transaction MD04.
Take note to test in always in your Test environment first.
Sales Document Status Update
Sometimes a Sales Document may be updated incorrectly and the status may be out of sync with the attributes in the document.
For example the sales order has been fully delivered then also status is showing open or In-processing.
Solution is to Run SA38 or SE38 with report SDVBUK00 which will determine the status again for the document.
Billing Document Update - VF04
If a document is not displayed at all or incorrectly in the billing-due list, check the following points one after the other:
The relevance for billing (table TVAP) of the document: if this was changed, consider Note 127514.
The billing status of the document (tables VBUK or VBUP). If you can neither bill a document with Transaction VF01 or VF21 nor with Transaction VF04 or VF24, check whether the billing status of the document to be billed is correct.If required, run report SDVBUK00 for sales orders (Note 67742, 88511, 207875) or report ZZDELSTA for deliveries (Note 137011).
For billing documents, you can achieve a redetermination of the status by means of a change of a header field in the billing document (Note 142368).
Billing Index (table VKDFS)
If a document is not displayed in the billing-due list, but you can still bill it in Transaction VF01/VF21, the statuses of the document to be billed are correct. However, incorrectly, the system did not create an entry in the billing index. For the resetup of the index table, call up report RVV05IVB for the affected documents. This report is described in Note 128947.
Remarks:
The index update (VKDFS) occurs during the update of the statuses in program SAPLV05I that is, during a possible debugging, the update debugging has to be active. Function group V05I ('Index update') is maintained by component LE-SHP.
- You can find an analysis report for the billing-due list in the related Note 386370.
The statuses (VBUK, VBUP) are determined in programs SAPLV45P or SAPLV50P.
Correcting Incorrect SD Document Indexes
Report RVV05IVB is available in your system for reorganizing or correcting incorrect SD document indexes. The report can correct the following index tables:
Select only what is appropriate as the running time can be quite long.
For example, I fill in the Sales document number with issue and only Tick Billing index (Sales Documents)Table | Contents | Usage |
VEPVG | Delivery Due Index | Delivery Due List (VL04) |
VKDFS | Billing Initiator | Billing Due List (VF04, VF24) |
VTRDI | Shipment Planning Index | Shipment processing (VT01/VT04) |
VRSLI | Receipt of Material from Deliveries | SC Stock Monitoring (ME2O) |
VAKGU | Sales Index: Quotation Validity | List of Quotations (VA25) |
VAKPA | Orders by Partner Function | List of Sales Orders (VA05) |
VAPMA | Order Items by Material | List of Sales Orders (VA05) |
VLPKM | Sched. Agrmnts by Cust Mat. | List of Scheduling Agreements (VA25) |
VLKPA | Delivery by Partner Function | List of Deliveries (VL05/VL06) |
VLPMA | Delivery Items by Material | List of Deliveries (VL05/VL06) |
VRKPA | Bills by Partner Functions | List of Billing Docs (VF05) |
VRPMA | Billing Items per Material | List of Billing Docs (VF05) |
If you use the RVV05IVB report to obtain a correct result for the SDRQCR21 correction report (Requirements), select 'Material index' in the 'Sales documents' area and in the 'Deliveries' area. If you do not have much time to run the report, restrict the document numbers further (for example, the documents corrected in the last run of the SDRQCR21 correction report). If you have enough time, you do not need to restrict the documents any further.
The SDRQCR21 report works incorrectly if the material indexes of VAPMA (Sales and distribution documents) or VLPMA (Deliveries) are incorrect.
See also; MD04 - Inconsistencies after PGI - SDRQCR21
Skip to end of metadataGo to start of metadataIssue:
One or more of the following commonly occurring symptom(s) affecting purchase order(s) and/or scheduling agreement(s) or their follow-on documents in your system, due to inconsistency in EKES, EKET or EKBE table(s):
- More than one line appears for a purchasing document in MD04
- Confirmation's MRP relevant quantity was not reduced, hence MRP still calculates with it
- Not correct values appearing at reporting, in purchase order history or at schedule lines overview
- MRP element ’POitem’ still visible in MD04 after posting Inbound Delivery
- MRP element ’ShpgNt’ still visible in MD04 after posting GR
- Negative quantity in MD04 even after goods receipt is posted
- The receipt quantity in MD04 is inconsistent from PO History
- Editing (Inbound or Outbound) Delivery is not possible, also may dump happens
- Incorrect stock in transit quantity in MB5T based on PO history
- Reversing/cancelling of a GR (goods receipt) or a GI (goods issue) or a delivery is not possible, error message M7 328 (Deficit of Delivered quantity..) also may raised
Solution:
- Check if there is a real inconsistency in the involved tables
- according to the symptom search for a correction report from the below list.
- make sure the correction reports are available in the system.
- start the report(s) in Test mode first, then in update mode to correct false entries.
Symptoms and correction reports to solve them:
Inconsistency in 'MRP reduced' values in confirmation and schedule lines:
Symptom | Correction Report | from Note | Additional info |
Incorrect DABMG (MRP reduced quantity) values in tables EKET, EKES | ZCORRDABMG | 202875 | This is the most commonly helpful and used report |
EKES-MENGE <> EKES-DABMG | ZZ_COMPLETE_ASN ZZ_CORR_EKES_DABMG ZZ_CORR_EKES_EKBE | 636853 | In case if update within EKES table was incorrect |
EKES-DABMG updated incorrectly for inbound delivery | ZCORR_EKES_PO | 1247578 | Inbound delivery is posted and has movement status 'C'. |
Incorrect EKET-DABMG and / or EKES-DABMG entry (with 'GR assignment' confirmation) | ZCORREKESGRRTV | 536190 | Usually this inconsistency (or below) cause M7 328 error also (for example by document reversing, MIGO, VL09). You cannot use it if you switched between 'No GR assignment' and 'GR assignment'. Use it if return deliveries for inbound deliveries are handled via delivery. Make sure EKES/EKBE-ETENS numbering are correct, if not go down to 'Incorrect EKES-ETENS numbering' entry and use correction report. The report won't work for confirmation controls in which the corresponding confirmation category is not have the 'GR assignment' (WEZUO) checkbox in customizing |
ZCORREKESBYGR | 215072 | You cannot use it if you switched between 'No GR assignment' and 'GR assignment' Make sure EKES/EKBE-ETENS numbering are correct, if not go down to 'Incorrect EKES-ETENS numbering' entry and use correction report. |
Correction Program For Md04 Sap Login
Above reports work only if the EKPO-ELIKZ (delivery completed) indicator is NOT ticked, and if the 'GR-assignment' checkbox is ticked for the used confirmation type in the used confirmation control customizing!
Inconsistency between or within scheduling lines and PO History:
Symptom | Correction Report | from Note | Additional symptom which solvable with the report |
EKBE-MENGE <> EKET-GLMNG (incorrect EKET-GLMNG) | ZKOGLMNG | 100690 | Cannot delete delivery, mainly for STO / SA problems. Used in case when the delivered quantity at the schedule line level is not equal to the actual quantity delivered (in history tables) it is created to handle issues with STO’s having old scheduling logic! (not the one described in Note 885177) |
EKET-WEMNG > EKET-WAMNG (incorrect EKET-WEMNG) | ZKOWEMNG | ||
EKET-MENGE < EKET-WAMNG or EKET-MENGE < EKET-GLMNG (incorrect EKET-MENGE) | ZKOMENGE | SAPSQL_ARRAY_INSERT_DUPREC dump at insert to EKPO, EKET usable when scheduled quantity is not equal to GI/GR quantity | |
EKET-WEMNG <> EKBE-MENGE (incorrect EKET-WEMNG) | ZKORWEM2 | The report was changed to include the new schedule line processing also (see Note 885177)! | |
EKET-WAMNG <> EKBE-MENGE (incorrect EKET-WAMNG) | ZKOWAMNG | Could solve MESSAGE_TYPE_X, TABLE_INVALID_INDEX dumps | |
EKET-WEMNG <> EKBE-MENGE (incorrect EKET-WEMNG) | ZKORWEMN3 | Problems with delivery also | |
EKET-WEMNG <> EKBE-MENGE (incorrect EKET-WEMNG for RETURN ITEMS) | ZKORWEMN4 | Reverse, or return not possible | |
Inconsistency in EKET-GLMNG, EKET-WEMNG and in EKET-WAMNG together | ZZ_CORR_EKET_WEMNG_WAMNG_GLMNG | Tip: run this also, if none of the above (from note 100690) helps |
If the report doesn't correct the document, or you would like to know more about the application logic of the reports, refer to the debugging guides in the following Wiki page: Debugging Guides for correction reports.
Additionally helpful reports for missing or incorrect table entries:
Symptom | Correction Report (3) | from Note | Additional info |
History for the delivery contains incorrect quantity | ZKOEKBEPO | ||
Order history for delivery does not exist | ZCREA_EKBE | ||
EKES-MENGE after reversal of goods is incorrect | ZCORR_EKESMENGE | ||
EKES entry exists but delivery (item) already deleted | ZDELEKES | If the inbound delivery exists but individual delivery items do not exist see the note’s solution part for action to do | |
Death satellite program. Missing EKES entry for the inbound delivery | ZCREATE_EKES | ||
Incorrect ETENS numbering in EKBE | ZCORR_EKBE_ETENS | Ensure that ETENS numbering is passing to EKES entries | |
The outbound delivery already deleted (from table LIKP) but still remained in the PO History (table EKBE) | Z_ARCHIVE_STO | it can correct cases where the entire delivery, is deleted, not just its item(s) | |
Correction report for completing open inbound deliveries in case the GR already exists | Z_COMPLETE_INBOUND_DELIVERY | ||
Incorrect EKES-ETENS numbering | ZHIGETENS (correct from entered ETENS value) | In case of overflow in EKES-ETENS field or SAPSQL_ARRAY_INSERT_DUPREC dump, or BIT_OFFSET_NOT_POSITIVE dump, see this Troubleshooting guide. | |
ZCORETENS (Correction for '0000' value records) |
If you observe further problems with Deliveries probably due to inconsistency, checkout KBA 2006809 - Composite SAP note: How to fix delivery-related inconsistencies
If the correction report not solved the observed problem, contact SAP Support, by describing the steps you did, and explaining the observed inconsistency. Watch naruto shippuden dubbed free.
Please keep the correction reports also available in your system after own checking.
Please keep the correction reports also available in your system after own checking.
Correction Program For Md04 Sap Jobs
Additional symptoms and resolution:
Dump MESSAGE_TYPE_X LIS_VERTEILUNG_LF while editing delivery (deleting, canceling, etc.):
- Firstly please try to run the correction report ZZ_CORR_EKET_WEMNG_WAMNG_GLMNG from SAP Note 100690 for this dump. If that not helps, please continue with belows:
- The dump is possibly caused by inconsistency, please see the solution of note 431145:
'Use correction report ZKOEKBE to get an overview of the number of incorrect updates. and to have a consistent status for the replenishment delivery again.
Then use report ZKOGLMNG from note 100690 in order also to correct the quantity delivered of the purchase order delivery schedule line.' - If these reports not helped, please read note 167242 and use the two mentioned 2 correction reports:
- The first report (ZKOEKB1) checks for inconsistencies on table EKBE and fixes them.
- The second report (ZKORWEMN3) fixes inconsistencies between tables EKBE and EKET.
Dump BIT_OFFSET_NOT_POSITIVE could be caused by incorrect EKES-ETENS numbering or SAPSQL_ARRAY_INSERT_DUPREC dump due to that an EKES record with the value '0000' in the field ETENS is created or other specific system problem occurs related to incorrect numbering of schedule lines:
- Check out this TSG for solution suggestion.
See also
BIT_OFFSET_NOT_POSITIVE in Schedule Agreement BAPI's due to EKET-ETENR overflow (06 859)
Correction Program For Md04 Sap Portal
If you observe further problems with deliveries, probably due to an inconsistency, checkout note 2006809 - Composite SAP note: How to fix delivery-related inconsistencies
Additional Info:
Correction Program For Md04 Sap Office
![Correction Correction](https://wiki.scn.sap.com/wiki/download/attachments/198969974/mrp1.jpg?version=1&modificationDate=1282266802000&api=v2)
The root cause of the above inconsistencies are not known. According to SAP-Support knowledge, from SAPKH60610 SAP-APPL Support Package level with also implemented notes: 1860803, 1911909, 1941146, 1960756, 1967549, 1979068, (2086182 also in case you use IS-AFS - Apparel and Footwear) the system is more reliable and less inconsistencies occur.
Please be aware that the above stated reports are not in the standard SAP system by default. You need to open the corresponding note and copy the reports' program code manually from the note's correction instructions - then you need to create the report in SAP System with SE38 transaction and activate them - or implement it via SNOTE.
Correction Program For Md04 Sap Portal
All of the mentioned reports can be run in all of the currently supported SAP ERP and SAP S/4Hana systems.