PIR IS NOT REDUCED

Hai Gurus,
1) I had created Requirement(PIR) for a fert material through SOP
2) MRP run is done .
3) planned and pur req.created
4) Material GI is done
5) Planned order is converted to process order and Goods issue done using MB1A
6) process order confirmation and goods receipt agianst process order is done.
7) Finished goods is delivered .
8) Finally order is settled.
My question is
A) After following the above all steps , in MDO4 the requirement created by SOP is not reduced from
the stock requirement list( MDO4) against the delivered qty , so once again the requirement is taken into consideration for MRP run, which should
not happen, i dont know where the settings to be done to correct this error.
waiting for the positive reply
Regards,
sekar chand

>
sekar chand wrote:
> Hai Mr proshob and Mario,
>
> Thanks for your valuable reply.
>
> The strategy which i was using is 40 , with 90 days forward and backward as consumption parameters
>
> And delivery is based on STO.
>
> can i change the strategy from 40 from 11, if so whether it will have any impact
>
> waiting for the positive reply.
>
> Regards
> sekar chand
Sekar,
In standard SAP you cannot consume PIR with STO Deliveries related PGI, so changing the requirment type from VSF to BSF or planning strategy from 40 to 11 would not help.
Please look at the option of using BADI- MD_PIR_FLEX_CONS and Method CHECK_PIR_CONS_REDUC to perform your required consumption.
Regards,
Prasobh

Similar Messages

After delivery aslo PIR are not reduced

Hi
I am using strategy 10.normally in 10 strategy PIRS will be reduced after Delivery.
after delivry also the PIRS are not reduced but the stock is reduced.
why it is happenning.
plz give me the solution immediately.
Regards
Srinivas

If I am right, you have done a PGI and still able to see the sale order/purchase order alive in MD04.
If this is your problem area,
Use SDRQCR21
Instructions for Using SDRQCR21
Material and Plant
If you enter selection criteria for "Material" or "Plant," the report processes the requirements according to this selection only. If you do not enter a selection criterion, the report processes all sales and delivery requirements.
By severely restricting the selection criterion "Material," you may be able to reduce the runtime of the report. In general, selecting the "Plant" criterion only does not shorten the runtime period. For more information, see the section entitled "Performance of SDRQCR21".
Data transfer
Select the "Data transfer" parameter so that the report updates the requirements on the database.
If you execute the report without selecting the data transfer parameter, the report simulates the update only (that is, it checks the requirements and issues a log, but it does not make any changes). In this way you can also use SDRQCR21 as a pure check report for sales and delivery requirements.
Compare
Always select the "Compare" parameter to improve the performance (runtime) and to restrict the scope of the log.
The report then corrects, deletes and creates only the requirements affected by the correction. If you do not select the parameter, the report completely reconstructs the database (for the materials/plants selected).
Planning entry
If you select the "Planning entry" parameter, the report creates planning file entries (entries for the planning run) for the materials/plants affected (and relevant according to the MRP type).
Processing for material
If you select the "Processing for material" parameter, the report saves the requirements (database commit) one after the other for each material/plant, instead of saving all the requirements in one step. 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 SDRQCR21 report with a data transfer once you have made sure that no-one will process sales documents or deliveries (for the materials/plants according to the selection) whilst the report is running, either in the foreground (dialog) or in the background (rescheduling, collective run for creating deliveries, 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 SDRQCR21 report twice at the same time, enter the relevant selection criteria Material/Plant for the same reason, so that they do not overlap during simultaneous processing.
 Recommendation
To execute the SDRQCR21 correction report easily, securely and completely, do not enter any selection criteria for "Material" or "Plant," select all four checkboxes and make sure that the report is not running during production operation. If runtime problems or other problems occur, see the following explanations in the sections entitled "Performance of SDRQCR21" and "Solving SDRQCR21 Problems."
 Comments
o Even if you execute the report without a data transfer, you should still select the "Compare" parameter.
However, it is irrelevant whether you select the "Planning entry" parameter in this case, since the report without a data transfer does not create any planning file entries.
o The "Compare," "Planning entry" and "Processing for material" parameters are available as of R/3 Release 3.1I only.
Performance of SDRQCR21
The report may require a long runtime. 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:
o 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.
o 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.
o 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.
o 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. (During production operation, the report usually logs more requirement errors than actually exist. 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.
o 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.
o 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 SDRQCR21 report and for other programs, and therefore significantly improves performance.
 Optimize database performance.
The tables that the report uses to approximately preselect the relevant document items are the most important:
o VBUK and VBUP (without a selection according to Material/Plant)
o 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 SDRQCR21 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 207875 and/or 506510, to check and, if necessary, correct the statuses of sales documents and/or deliveries.
 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_ARRAY_INSERT_DUPREC because of inconsistencies, check the TVIND Customizing table and see Note 128947 and/or 33267 for information about correctly reconstructing the material index.
 ATP server: After the run of SDRQCR21 (if you use the ATP server), you must load the requirements for the combinations from material and plant for which SDRQCR21 was started to the ATP server.

Problem with gross requirement planning pir is not getting reduced

Dear Gurus
I am trying to use strategy 11 for a particular finished product.(having bom and routing)
In the material master I have set mrp type pd lot size ex .strategy group 11, mixed mrp 2,item category group norm, availabilty checking group 02 .
Then I made manually pir for that material in md61 with BSF requirement type .
Then ran the mrp for that material in md02.
Planned orders came .(In md04 screen that gross requirement line text also came as usual )Converted them to prodn order and then did the gr in mb31 with 101 mvt type. After doing the gr the pir should get reduced in md04 screen which is not happening . Where I am going wrong
Regards
Sandip Sarkar

Dear Sandip Sarkar,
                                  It usually happens run MRP and ckeck.
Strategy 11 in summary :-
1. Sales Order creation - no impact.
2. Goods Receipt - minus the quantity for the oldest planned independent in demand management.
   For e.g. if PIR is 100 and delivery 90, PIR becomes 10 (withdrawal 90).
3. Delivery - no impact as delivery is issue from sales order.
This strategy is particularly useful if you need to produce, regardless of whether you have stock or not. For instance, steel or cement producers might want to use this strategy because they cannot shut down production; a blast furnace or a cement factory must continue to produce, even if this means having to produce to stock.
You need to maintain the following master data for the finished product:
Maintain strategy group 11 on the MRP screen.
Set the Mixed MRP indicator to 2 on the MRP screen.
Maintain the item category group (for example, NORM) on the Sales Organization screen.
Maintain the Availability check field so that you perform an availability check without the replenishment lead time (checking group 02 in the standard system).
Strategy                                                        10
Stock is taken into account                           Yes
reduction of planned independent
requirements takes place during u2026   u2026 goods issue for                                                                                delivery                                  order (discrete production),
11
Stock is taken into account                          No
Reduction of planned independent
requirements takes place during u2026            ... goods receipt for a production
                                                                        order (discrete production),
for a planned order (repetitive
                                                                         manufacturing), or for a purchase
                                                                         order (trading goods).
Edited by: Vachanala Rajasekhar on May 7, 2010 11:55 AM

Planned ind.requirement is not reduced during processing of the goods issue

Hello to all,
I am facing a problem.
We are using make to stock production with strategy 10 (LSF).
On 1.12.2006 the ind.requirement (LSF) is entered for week 4.2007 (I see that from schedule line history) for the material A.
In the system at that time there were a sales order which needed that material A in exact quantity the LSF was. The GI of the delivery were on 13.01.2007.
The LSF still exist in the system and it can be seen in MD04.
Before running every MRP, a planning scenario is being created and run. From MS04 I can see that the LSF exists since then in all scenarios except from 3.
The schedule line history of the LSF has only its creation (1.12.2006).
Can you please explain to me the following:
1. why in the first place the LSF did not reduce after the GI of delivery?
2. the LSF does not exist in olny 3 scenarios. how it could disappear (delete) and appear (create) again without history displays that changes?
3. If I delete the LSF I think I will not have a problem. Correct?
Thank you in advance for your help.
IX

Hi Ismini,
For the first question, there could be several reasons, like for example, 13.1 is not week 4. So if the consumption parameters did not allow forward for at least around 7-10 days (to get to the date of the first day in week 4), then consumtion didn't take place. Another reason could be that you defined planning strategy 10 for the material AFTER the sales order was already created.
Point 2: I really don't know he details of these LTP scenarios that you mention.
Point 3: if it really is from 2007 I think that you can delete the PIR without fear.
Regards,
Mario

WM-production order supply quantity is not reduced after confirmation,GRN

Dear Gurus
               i am configured the WM-PP , in the production order after material staging and TR-TO process , i did confirmed the
               production order and GRN. Raw material stock is not reduced from the storage type 100....
               kindly, suggest me where i missed the configuration.
BR
DEVA

Hi Ismini,
For the first question, there could be several reasons, like for example, 13.1 is not week 4. So if the consumption parameters did not allow forward for at least around 7-10 days (to get to the date of the first day in week 4), then consumtion didn't take place. Another reason could be that you defined planning strategy 10 for the material AFTER the sales order was already created.
Point 2: I really don't know he details of these LTP scenarios that you mention.
Point 3: if it really is from 2007 I think that you can delete the PIR without fear.
Regards,
Mario

Table space not reduce after delete in oracle 11G

Hi Team,
I have a DB 11.1.0.7 on unix.
I have execute delete tables on tablespace, but this not reduce.
Thanks

935299 wrote:
What segment space management type is defined for the tablespace in question?
MANUAL
Then you should check out the documentation some more.
But even if you shrink the table segement what is that going to do for the data file size?
I don't undertand you.
ThanksYour thread is titled "Table space not reduce after delete in oracle 11G" which implies to me that you are interested in reducing the size of a tablespace (which really means reducing the size of the underlying datafile(s)).
So, if you shrink the size of the sys.aud$ table, will that cause the datafile(s) to become smaller? Will it accomplish your goal? What else, if anything, needs to happen?

Table space not reduce after delete in oracle 10g

Hi..
Based on my system, i have found that my oracle table space did not reduce after the deletion query. Why ?.. Could somebody help me. As your info, I am using oracle 10g.
Thank you,
Baharin

After Delete the table space will not be set free. high water mark will not be reset. to regain the space you need to recognize the objects from which you deleted the data. This can be done in many ways.
1) Move the objects.
Alter table temp move --> optionally tablespace clause can be used. After this you need to rebuild table indexes.
2) With 10g table can be shrinked or reorganize to free the space.
alter table mytable enable row movement;
alter table mytable shrink space;
3) Export/Import
export the objects and drop and recreate with import.

Cash Discount at header is not reducing line item price

Hi Experts,
While putting cash discount at header, it is not reducing price of the my total line item. I am having total line item price = 100 USD (10 USD * 10 Qty). I am entering 10 USD as cash discount at header. It is not reducing total line item price to 90. Also in my accounting document 10 USD (cash discount) is going to my tax account.
Please advise.
Regards,
Kamal

Hi,
The cash discount case will only be applicable in connection with terms of payment. You will have to define your customized discount condition type in M/06 and assign it to your PO pricing schema via M/08 transaction. Make sure it shall not be set as 'Statistics' condition type.
Cheers,
HT

Save as Reduced Size PDF and Save as Optimized PDF do not reduce the file size. What gives?

Save as Reduced Size PDF and Save as Optimized PDF do not reduce the file size. What gives? I used Acrobat 9 to do this for a long time. I recently received new laptop loaded with with Acrobat 10 and it does not work the same. I typically scan 8-10 pages of receipts, combine the files in Acrobat, and then optimize to reduce the size so I can upload with my expense report. Typically, my files were reduced to 200-400 KB. I have a 2 MB file that will not reduce at all.

Bernd, thank you for your attempt to help but the option dialog windows do not contain the same options. There are numerous other posts on this forum about this issue and there is no answer. Clearly, there is an issue. I have submitted this issue to our internal help desk.

Table size not reducing after delete

The table size in dba_segments is not reducing after we delete the data from the table. How can i regain the space after deleting the data from a table.
Regards,
Natesh

I think when you do DELETE it removes the data but
it's not releasing any used space and it's still
marked as used space. I think reorganizing would help
to compress and pack all block and relase any unused
space in blocks. Why do you think that? Deleting data will create space that can be reused by subsequent insert/ update operations. It is not going to release space back to the tablespace to make it available for inserts into other tables in the tablespace, but that's not generally an issue unless you are permanently decreasing the size of a table, which is pretty rare.
Would you also please explain about different about
LOB and LONG ? or point me to any link which explain
baout it.From the Oracle Concepts manual's section on the LONG data type
"Note:
Do not create tables with LONG columns. Use LOB columns (CLOB, NCLOB) instead. LONG columns are supported only for backward compatibility.
Oracle also recommends that you convert existing LONG columns to LOB columns. LOB columns are subject to far fewer restrictions than LONG columns. Further, LOB functionality is enhanced in every release, whereas LONG functionality has been static for several releases."
LONG was a very badly implemented solution to storing large amounts of data. LOBs are a much, much better designed solution-- you should always be using LOBs.
Justin

Percentage of used table space not reduce after deletion

Hi..
This is my query to delete data from database:-
delete from $tb_data where to_char(partition_dt,'MON') = '$mm';
The $tb_data and $mm is variable and the $tb_data will be read input table name (as example backup_nx160, backup_ngn and etc) and the $mm will be capture the input month.
My question is why the percentage of used table space is not reduce after delete query was executed. Could somebody help me..
Please help me..
Thank you,
Baharin

baharin wrote:
Hi..
Is it the deleted space will be reused by the system ?Yes.
.. How could i check the real free tablespace or real usage table space ?If you have gathered statistics on the schema recently, then sum (avg_row_len*num_rows) should give you the exact number of bytes that are being consumed - assuming all tables are in a single tablespace under consideration. You can subtract this value from sum (dba_data_files.bytes) figure for the tablespace, to know exact free space.

WM-PP Production supply quantity is not reduce after Confirmation and GRN

HI
Iam configured the WM-PP, Against production i did material staging, TR-TO Process and Grn . But the raw material stock is not
reduced from the Storage type 100. kindly suggest me where i missed the configuration...
with regards
dinesh

Hi experts,
Please provide your expert comments

Rebuild Database did not reduce the database size

I just completed a rebuild database. The rebuild completed much quicker than anticipated and in the end the did not reduce in size.
This is my first rebuild and since original installation I have deleted a number of masters. From my understanding thumbnails and previews are not deleted when the master is deleted. In order to delete the thumbnails and previews the db must be rebuilt. Is this correct?
The db is over 31.1gb. The rebuild took approx 10 minutes and when completed the db size was still 31.1gb. There was a message during the rebuild that read "Recovering projects". I was expecting to see stats showing previews and thumbnails being generated in the activity window but don't see it. Has the db been rebuilt?
Thanks for any assistance.

Rebuilding the database is for disaster-recovery, not file maintenance. I certainly wouldn't do it unless something was fundamentally broken and the application didn't run.
"rebuilding" the database seems to do the following:
(1) remove the database file completely (not even to the trash, it destroys the database utterly)
(2) run through the plist files and reconstruct a brand-new database from them all
I checked this (on an empty library) using hard-links from the commandline, and step (1) above scared me sufficiently that I'd only rebuild the database as an absolute last resort.
Now, 31GB seems a lot for a database that only took 10 minutes to rebuild - are you sure you're not telling us the size of the library (to find the database size, right-click on the library and select view-package-contents, then open the 'Aperture.aplib' folder and find the size of the 'Library.apdb' file. That's the file you're changing when you 'rebuild database'.)
If you're telling us the size of the entire aperture library instead, then that size will be completely dominated by the master RAW files you've imported. I'd guess your library will be less than 10MB.
My understanding is that previews are deleted (since they're stored as separate files alongside the master image, if you look in the folder hierarchy), but thumbnails aren't. The thumbnails are aggregated together into one-file-per-project (presumably for speed of access), and I'd guess the space is reclaimed for future use, but the file doesn't get any smaller. That's a classic trade-off for speed-of-access, and users like us are normally very keen on things being fast
-=C=-

Unrestricted quantity not reducing in MMBE

When we are reserving materials through maintenance order (IW31),
we can see the reserved quantity through MMBE.
but the unrestricted quantity remains the same and does not reduce.
This is not correct. If we are reserving a material in the maintenance
order, then its unrestricted quantity should reduce and the reserved
quantity should increase.
This is not happening in our current scenario.
For e.g
if there is a material A and it has unrestricted quantity as 2.
If i reserve 1 quantity through maintenance order.
Then its unrestricted quantity should reduce to 1 and reserved quantity should increase to 1.
but when we view the MMBE transaction, it shows quantity 2 in unrestricted and 1 in reserved.
Shouldn't the unrestricted quantity reduce to 1??
Please advise.

Hi,
I have done further investigation and found something further wrong with this.
E.g, Material A has unrestricted stock as 5.
I createa a reservation for 1 through maintenance order.
So, effectively, unrestricted stock = 4 and reserved stock = 1 (total = 5)
But SAP (MMBE) is showing unrestricted stock = 5 an reserved stock = 1 (That means I have quantity 6 in total !!!!!!!!!! which is wrong)
Now, I do an unplanned goods withdrawal agains cost center for quantity 5. SAP lets me do it. Ideally, it should give me altleast a warning that quantity 1 is reserved.
Now when i do my planned goods issue for the maintenance order, it gives error 'deficit stock'.
This is wrong business process!! If i have reserved quantity 1, how can somebody else issue it??
Please advise,
Many thanks.

ORA-19510: failed to set size with ORA-27059: could not reduce file size

Hi,
I have RMAN backup implemented and getting below error.
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 01/12/2014 04:28:37
ORA-19510: failed to set size of 12839996 blocks for file "/home/oracle/DBBACKUP/Oracle10g1/Full_Backup/DB_Backup_201401128366598241" (blocksize=16384)
ORA-27059: could not reduce file size
Linux Error: 28: no space left on device
Additional information: 2
I have checked with following scenarios:
1. taking backup by setting the MAXSETSIZE parameter value greater than the maximum size of tablespace.
2. taking compressed incremental backup with maxsetsize as unlimited.
3. taking compressed incremental backup with maxpiecesize value as 20G/40G/80G/120G and maxsetsize as unlimited.
Following is the RMAN backup script:
RMAN> run
2> {
3> allocate channel c1 device type disk maxpiecesize 120G
4> format '/home/oracle/DBBACKUP/Oracle10g1/Full_Backup/DB_Backup_%Y%M%D%t%p';
5> backup incremental level 0 as compressed backupset database plus archivelog delete input;
6> crosscheck backup of database;
7> crosscheck backup of controlfile;
8> crosscheck archivelog all;
9> delete noprompt expired backup of database;
10> delete noprompt expired backup of controlfile;
11> delete noprompt obsolete recovery window of 15 days;
12> release channel c1;
13> }
14> exit;
Oracle database version is 10.2.0.1.
The database is on Linux system and we are taking the RMAN backup on mounted Windows NTFS disk.
The remaining space on NTFS system 1.7TB and the total database size 850GB. Used size by database is 500GB.
Regards,
Yogesh.

Hi,
First get the backup piece size its trying to allocate for file "/home/oracle/DBBACKUP/Oracle10g1/Full_Backup/DB_Backup_201401128366598241"
= 12839996*16384
= 210370494464/1024/1024/1024
=195.9GB
Its trying to allocate ~196GB for the file.
1. Make sure the RMAN backup piece won’t exceed the O/S permitted filesize limit.
2. But we can restrict the RMAN backup piece using the MAXPIECESIZE option.
You restricted it to 120GB but actual requirement to allocate backup piece file is ~196GB.
I think you need to change the MAXPIECESIZE and give it a try.
Please update if it succeeded or failed.
Thanks & Regards,
Gayu

PIR IS NOT REDUCED

Similar Messages

Maybe you are looking for