Issues related to sales orders. Notes 20636466 corrects a program. See also the following document for more frequent issues on MD04: http://scn.sap. SAP Transaction and Command Codes Job Aid Prepared by Accenture. Create Investment Program. Usually these errors are found when going through MD04.
You can detect or check this using Transaction MD0. Stock/Requirements List). These inconsistencies may trigger follow- on errors in planning, procurement (production, purchase order) or document processing (availability check). Other terms. Sales document, sales requirements, outbound delivery, delivery, delivery requirement, reconstruction, reorganization, VBBE: Sales Requirements Individual Records; VBBS: Sales Requirement Totals Record, summation SUMBD, individual requirement, total requirement, daily requirement, weekly requirement, customer requirement, sales order requirement, ATP availability, batch input, collective processing, /SAPAPO/CIF. If you cannot correct the error yourself, create a customer message and describe how the error can be reproduced (for further information see Note 5. If errors occur repeatedly in the requirements update that you (still) cannot reproduce, save the log of correction report SDRQCR2. Correcting the Error.
Correct the requirement errors using the SDRQCR2. To improve system performance, make sure that you have implemented Note 8. Release 4. 5. B). If the ATP server is active in your system, update the data in the ATP buffer (see Note 1. If your R/3 system transfers sales and delivery requirements to an APO system (using an active integration model for the . If this does not work, see Note 4. Instructions for Using SDRQCR2.
Material and Plant. If you enter selection criteria for . If you do not enter a selection criterion, the report processes all sales and delivery requirements. By severely restricting the selection criterion . In general, selecting the . For more information, see the section entitled . In this way you can also use SDRQCR2.
Compare. Always select the . If you do not select the parameter, the report completely reconstructs the database (for the materials/plants selected). Planning entry. If you select the . Correspondingly, the log issued by the report is also sorted according to material and plant. No parallel processing with a data transfer! Only execute the SDRQCR2.
EDI- IDoc and so on)! Reason: The report does not read or set blocks. It therefore produces correct results only if no other program updates sales or delivery requirements, or checks availability while the report is running. If you execute the report with a data transfer during production operation, the system may even generate new requirement errors! Additional Information: If you run the SDRQCR2. Material/Plant for the same reason, so that they do not overlap during simultaneous processing. Recommendation. To execute the SDRQCR2.
Header Version / Date 8 / 2010-04-26 Priority Correction with high priority Category Program error Primary Component MM. Note 521164 - MD04: Correction. SAP Note 25444 -SDRQCR21: Recovery of sales and delivery. Recovery of sales and delivery requirements.
The SAP Help Portal navigation has been updated to make it simpler to find what you are looking for. For more information please visit our Community and let us know.
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. For that you have to implement the program ZCORR. 521164 - MD04: Correction EKES-MENGE after reversal of. I'm using version 470, so the note 442831. SAP Logistics Sales and Distribution. Requirements in sales order Error V1427.
If runtime problems or other problems occur, see the following explanations in the sections entitled . Since you can only execute it at specific times (you cannot use parallel processing, that is, you cannot execute the report with a data transfer during normal production operation), bottlenecks may occur.
In this case, attempt the following solutions: Execute the report with a data transfer only for materials with requirement errors. To do this, proceed as follows: Step 1: Execute the report without a data transfer (!) and without the selection criteria 'Material/Plant', but with 'Compare' and with 'Processing for material'. You can also do this during production operation. Step 2: Outside production operation (!), execute the report with a data transfer only for those materials (or material/plant combinations) for which step 1 logged requirement errors. Step 3, only if you use total requirements (Table VBBS, daily/weekly requirement) and not individual requirements (Table VBBE): Outside of production operation (!), repeat step 1 without 'Processing for material' for test purposes. The report should no longer log any errors.
Comment 1: If step 1 logged several materials with requirement errors, repeat it (several times if necessary) with selection(s) according to these materials. By repeating the step in this way, the system may log fewer materials with requirement errors. If data was transferred, the report would then create new errors.) Carry out step 2 only for those materials for which the report has logged permanent requirement errors.
Comment 2: If the time outside production operation is insufficient for step 2, divide the step into several substeps. That is, divide the material list determined in step 1 into sections that do not overlap and execute the report for each corresponding subsection. You can execute these substeps in succession, if necessary over several days, or partially at the same time depending on your system capabilities. Comment 3: If, contrary to expectations, step 3 logs materials with requirement errors, (repeatedly) treat this step as step 1 of a new correction process. Outside production operation, reduce the list of materials with requirement errors as described in comment 1, and so on.
Do not select the 'Planning entry' parameter. The report then does not create any new planning file entries (see above). However, you must be aware of the risks involved in doing this! Archive sales documents and deliveries. We recommend that you archive sales documents and deliveries. Document archiving reduces the database for the SDRQCR2. Optimize database performance.
The tables that the report uses to approximately preselect the relevant document items are the most important: VBUK and VBUP (without a selection according to Material/Plant)VAPMA, VLPMA and VBUP (with a selection according to Material/Plant)The report still reads entries from tables VBAK, VBAP, VBEP, LIKP, LIPS, as well as VBPA, VBUP and VBFA (if necessary). Finally, it reads and updates tables VBBE (requirement individual records) or VBBS (totals records for each day/week). Solving SDRQCR2. 1 Problems.
Document status. The report returns correct results only if the statuses of the documents affected are correct (with regard to reference, delivery, goods movement, reason for rejection). This prerequisite is usually met. Only if you have good reason to suspect that the statuses are inconsistent or that the report has returned incorrect results because of inconsistencies, see Note 2. Item Material Index. If you enter the 'Material' or 'Plant' selection criteria, the report returns correct results only if the document items affected are contained correctly in the relevant material index (VAPMA, VLPMA). This prerequisite is usually met. Only if you have good reason to suspect that the index is inconsistent, that the report has returned incorrect results because of inconsistencies, or that the report terminated with SAPSQL.