Reorganisation of PIR's related

Hi pp legends,
        I am tring to use the Reorganisation of PIR's (MD74) transaction for my requirement. for example, there is a requirement of 3000 nos for june and 2000 nos for july, if i run mrp, one planned order for 3000 and another planed order for 2000 is generated. after converting my planed order, i was able to produce only 2950, the remaining 50 nos is my loss. i cannot produce that odd 50, only this 2950 only will be sent to meet that 3000 nos requirement. next time if i run the mrp, the system is planning for the remaining 50 nos also which i dont want to plan. the requirement of 3000 has to get nullified with my actual output of 2950. for that i tried md74, there only PIR is only getting cancelled and the quantity produced for that requirement is being consumed for next orders.
  If any body can help me in sorting out this problem, it will be of great use for me.
Thank you
regards,
senthil nathan.k

Hi Senthil,
What I understand from your query is : out of 3000 PIR qty in the month of June, MRP has created a planned order for 3000. This planned order was converted into production order with 50 scrap qty. Now in the next MRP run, these additional 50 qtys are planned with a new planned order, which you do not want.
If this is your requirement, you could MD62 transaction to change the PIR qty from 3000 to 2950. And if you run mrp in planning mode 3, delete and recreate mode, the excess planned order, if unfirmed/unfixed will get deleted. Please note that the firmed/fixed  planned order (so also production orders) will not be touched upon by MRP.
hope this helps you to resolve your present situation.
Regards,
Kiran

Similar Messages

  • Queries regarding reorganisation of PIRs

    Hi PP Gurus,
    I have some queries related to re-organization of PIRs using MD76.
    1.In order to execute MD76,we first need to execute MD74 and MD75.Execution of MD74 has two parts.
    a)  Adjustment (reduction) of all planned independent requirements scheduled quantities to the amount of
        (customer) requirements assigned. If no requirements are assigned, the planned quantities are set to 
        zero.
           1) what does planned quantities being set to zero mean?
           2) what is the amount of requirements assigned, where can we find it in table
    b) For all inactive requirements (these have no requirements assigned), the schedule line records are deleted from table PBED if the 'Delete inactive requirements' flag is set on the selection screen.
           1) What makes a requirement inactive?
           2) When do you actually Plan PIR?
           3) When will they be inactive?
    2.When we say planned qty in PBED, is it PLNMG, or FIXMG field.
    3.Which field in PBED is for schedule lines?
    4.I found that in PBHI under history field,some entries have data as 00000000, what is the significance 
       of 'history' being zero.
    Kindly clarify my doubts.

    Hi Mary Joy,
    1) what does planned quantities being set to zero mean?
    The planned quantity set to zero mean the adjustment of an PIR. ie this function is used to adjust the qty of a PIR by reducing the open quantity to zero.  The open quantity is the original planned quantity that has not been consumed by orders of other categories, usually sales orders. Alternatively you can delete such an order completely.
    2) What makes a requirement inactive?
    Requirements are made inactive via many factors like change in demand, change in pegging conditions, change in sourcing, change in forecast, changes in sales orders, scheduled line, inconsistency of data, changes in customer demand, Fresh release of plan etc., 
    3) When do you actually Plan PIR?
    PIR's are demand or requirements that are generated from a firm customer orders like sales order, forecast, scheduling agreement etc.,  PIR can be either entered manually in system or transferred from other sources
    4)  When will they be inactive?
    As and when if a customer demand changes, or if a PIR is deleted or a fresh PIR is overwritten, then the previous PIR will become inactive
    Regards
    R. Senthil Mareeswaran.

  • Why are old PIR's not deleted even after doing MD74 & MD75??

    Hi All,
    In few materials; i am not able to delete old PIR's??
    Even though i have performed MD74 & MD75 (which covers 2 days) i.e. whenever i do this; PIR's which are old than this limit are deleted, but there are few materials of 6-8 months still showing in MD04. Because of which there are major issues in MRP calculations..
    I think in this case PIR's are seemed to be partly consumed...but i am not able to relate this.......please clarify and how can this problem be solved permanantly
    Rgds

    Hi Vicky Khabrani,
    You can check with t code MD73 to see how the PIRs are related with sales orders. In the case of strategies like 40, 50 & 60 when SO is entered the SO consume the PIRs.
    Subsequently if any of these SO are canceled or If the SO qty reduced, still the PIR will have  the link with the SOs.
    With the re-organisation function we can  delete only those PIRs which are not linked with any SOs....
    Regards,
    Ramasamy

  • MD74-Inconsisteny

    we are trying to use the md74 to reorganise the PIR.
    we have run the md74 with same key date on different days.
    Eample on March01 and on march05
    The key date for both case was march01..
    we get less no of materilas on march 01 and new set of materials for march05..
    like to understand better why we have such inconsistency..
    reg
    Dsk

    Hi,
    For Reorganization below are the Useful OSS-Notes.
    OSS Note 135807 - Reorganization of planned independent requirements.
    OSS Note 88492 - Reorganization of planned independent reqs; MD74
    Hope this helps..
    Regards,
    Siva

  • PIR reorganisation

    Dear gurus,
    Can some one tell me what is the use of PIR reorganisation run with tcodes MD74, 75, 76?
    Under what circumstances can I use these?
    Thanks and Regards,
    Raghu

    Dear,
    MD74 - deletes only the PIR
    MD75 - deletes only the history created against each PIR
    Md76- mass deletion with history
    Please refer this thread,
    Deleting PIR using MD74 / MD75 or by any other means.
    Difference between MD74 & MD75
    Regards,
    R.Brahmankar

  • How to Block Planning for PIR related Dependend Requirements of a BOM Comp?

    Hi All,
    We have a scenario which has a FERT Material "XY" has a BOM with ROH Materials "C1", "C2" & "C3".
    Material "XY" has a PIR for 100 pc and on MRP Run it generates Dep Reqmnt for C1, C2 & C3. When MRP Runs, we want to BLOCK generation of Purchase Requisition for C1 only (because of its high Value, the Buyer does not want to buy it for the PIR Planning).
    At the same time there is a Sales Order for "XY" for 50 pc and on MRP Run it creates Dep Reqmnt for C1, C2 & C3 and also Purchase Requisitions.
    This time, Buyer wants to have the Purchase Requistion for C1 as a result of Planning Run.
    Both "XY" & C1, C2 & C3 are all in Planning Strategy 40 and MRP Type PD
    I tried to BLOCK the Pur Req generation by putting the MRP Dep Reqmnts as "1" but it is blocking all the PRs.
    Requirement is to block Pur Req generation for PIR Dep Reqmnts and Not-Blocking generation of PR based on Dep Reqmnts from Sales Orders.
    How can this be achieved?
    Any suggestion is most welcome!
    Thanks!
    Edited by: Jing Tulio on Apr 23, 2009 2:45 AM

    Hi,
    A Suggestion:
    Create an additional alternative BOM for your "XY".
    In this remove the Component C1. Only C2 and C3 will exist.
    Create 2 Production Versions.
    The 1st PV will have the BOM alternative with all the components.
    The 2nd PV will have the BOM alternative with the Components with C2 & C3 only.
    Now in MD62/61 for "XY", specify the Production as PV2, so that every time for PIR, system will consider PV2 and in this the component C1 is not included.
    For all the other purposes (sales order --> Pl. Order --> dependent req.), System will pick the PV1 by default.
    Pl. create the PVs for the same date and same lot size.
    in MRP4 view, BOM selection method, select - 2 Selection by production version.
    Try this and revert for further discussion..
    Regards,
    Siva

  • Tables related to PIR

    Hi,
    I would like to know the tables related to the planned independent requirements ?
    Regards,
    PSS

    PBIM          Independent requirements for material
    PBED          Independent requirement data
    PBHI          Independent requirement history
    PBIV          Independent requirement index
    PBIC          Independent requirement index for customer

  • Distinguishing PIR related planned orders from Customer related.

    Dear all, what could be the best way how to distinguish planned orders generated basing on PIR from ones generated from real Customer Orders. The main idea behind is to make sure that orders generated for real customer orders are processed with first priority and orders from PIR with second. Thank you. Regards,Andrey.

    Hi ,
    System will not always create one plan order for one demand. If lot sizing procedure is WB-Weekly lot size , it wll generate one plan order for customer orde r& PIR falling in same week. Hence , there is no flag or field which will help identify which Plan order is feeding what demand /how much qty of demand.
    You should look at altering Planning strategy. If you implement Make-To-order strategy(20, 50, 59 ) , system will create Planning segment(Blue color seperator in MD04 screen)
    System will ignore lot sizing procedure & always create one plan order for one demand.
    Alternatively , you can implement SAP-SCM which has pegging reports & priority based processing.
    Hope it helps,
    Jatin

  • Reorganizing PIRs -related quires-reg

    Hi friends,
    In our system we have found one back ground job scheduled daily with teh following details .
    Job name : SYS_PIR_DELETION
    Programme : RM60RR20
    out put is showing how many PIRs are selected and how many are adjusted
    its for reorganizing independant requirements -Adjusting Req (PIR)
    request you to provide inputs to understand what this job will be doing regularly ?
    what for its meant ?
    what calculations it will do to adjust PIRs
    please provide valid inputs
    regards
    Madhu Kiran.

    issue analysed by self

  • PO creation date and info record validy price relation.

    Dear Gurus,
    While creating a PO, when I change the PO creation date, price in the PO will change according to the validity start date based on the PIR.I believe thats the logic right? I have a scenario, I'm facing a problem that when I change the PO creation date between 2011 and 2012 period,  the price of the PO at times will not change according to the PIR validity start date. Is there any OSS note related to this issue or I'm missing out any logic?
    Validity periods
    Validity on        Validity to         Deletion Flag.   
    04.11.2011       31.12.2011              x
    01.01.2012       31.12.9999

    HI,
    By default, the pricing conditions are dependant on PO document date.
    But there are different options like, whether you want your pricing to be dependant on Delivery date of PO item or current date (sy-datum) or GR date etc.
    This filed is available in 2 places: 1. Vendor master>purchasing data> Pricing Date Control
    2. Info record>Purchasing data> Pr.Date Cat.
    Check in these 2 places and then simulate pricing by changing the corresponding date.

  • PIR Consumption - Sales Order & Service Order

    All -
    I've come across an issue in our system as it relates to PIR consumption.  We create a PIR forecast which is designed to be consumed by orders.  (MM strategy group 40, PIR consumption indicator 1).  PIR is successfully consumed upon sales order creation.
    In the same area of our business (aftermarket service and repair), we also require PIR consumption when component requirements are added to our repair service orders.
    With the current setup (strat 40, CI 1), the PIR is not consumed after service order component addition.  It adds to the total material requirements.
    I've altered our settings across the board to account for both order types, however, i am hitting a wall as to if my new settings are a help or a hinderance.
    New settings are (MM strat 40, MM mixed MRP mode 3, PIR CI 3).
    Visually, i can see that my total PIR count is actively reduced via MD04 monitoring, however, when looking at the PIR directly, I see that the PIRs have not been consumed.  Instead they are still active and the reqs are hidden.
    I don't know if consumption of PIR is allowed for multiple order types.  I know that strat 40 directly relates to sales order requirement planning.  I do not know if there is a strategy that works similarly for both sales order AND service order types.  I'm also very skeptical of using mixed MRP mode 3 to accomplish the PIR consumption.
    Could anyone enlighten me on this?  I can't find any information on this sort of order types with consumption.  If it's not possible to combine order types with PIR consumption, so be it.  I'd just like some info.
    Thank you in advance,
    Ehren

    Sure thing. I'm running in our test client for the results, but my settings are identical:
    Image 1 = MD04 result of addition of PIR using VSF with consumption indicator 3:
    Image 2 = Addition of sales order requirement for the same part, VQTEST1.  Successfully consumes qty 1 of PIR material:
    Image 3 = Modification of service order to add qty 1 of component VQTEST1. Rather than consuming one of the remaining PIRs, the order created a new requirement above the PIR forecast:

  • Job for alert data reorganisation is not release or running -ERROR BPM

    Hi
    I am trying to set up BPM in solution manager EHP1 .
    I ahve created a business process and also added teh required job,When i try to generate and activate the BPM i get an error as
    "Job for alert data reorganisation is not release or running"
    kindly suggest what i need to do to resolve this issue, which job to be scheduled and also all details and also any relevant document for the same
    i have a project dead line to be met kindly help me ASAP
    Thanks
    Michael

    Hi Michael
    Was it show red alert ?
    Do you still get same alert if you generate and activate
    the BPMon session ?
    If yes, there seems some problem on job "BPM_ALERT_REORG".
    Maybe it is scheduled but not released.
    (do you see scheduled job in SM37 ?)
    1st, according to your description, you use ehp1.
    In that case, as described in note 521820, do you already have
    required note. Especially related to ST-SER like following.
    1273127
    1275225
    1298310
    1319473
    1332197
    1355132
    1390111
    I quickly checked description of each note, but could not find out
    correction related to alert reorganization job. But it is better to
    implement above notes if you do not have yet.
    And if you still have problem (try generation and activation again)
    even with above note, I recommend you to create SAP customer message
    for component "SV-SMG-MON-BPM".
    Best Regards
    Keiji

  • What is the use of t-code MD74 - Reorganising independant requirements

    what is the use of t-code MD74 - Reorganising independant requirements

    basically it to delete the unwanted PIR for the last period.
    Let us say you planned PIR for 100.
    At the end of Period the total salae order were 90, PIR shows 10 excess, this has to be deleted. We can do it manually, but this can be done collectively
    pl go through the link below
    http://help.sap.com/saphelp_47x200/helpdata/en/cb/7f9b7043b711d189410000e829fbbd/frameset.htm
    With the reorganization function, you can delete planned independent requirements for which there are no sales orders in the database. You can delete the planned independent requirements history.
    A key date is required to carry out reorganization which is calculated as follows: the system checks whether a reorganizing interval is maintained in Customizing for the plant that you want to reorganize. If an interval is maintained for this plant, the system uses this information to calculate the key date. If no interval is maintained for this plant, the system checks whether intervals are maintained for any other plants, and selects the largest interval to calculate the key date. You can change the key date proposed in the initial screen for reorganization.
    You can change the proposed key date when deleting the history. You can set a shorter interval for deleting histories than for deleting the requirements records.

  • Different Pricing Schema in PO and PIR for same vendor and material

    Dear Experts,
    I am facing an issue related to MM.
    I have a vendor and a material under a plant, purchase Org, purchase group.
    When we are creating a Purchase Info Record (PIR), it is picking one pricing schema, while when creating PO for same vendor and material, it is picking another different pricing schema.
    As per my knowledge, pricing schema in PO is picked as per pricing schema group of Vendor and I believe same applies for PIR as well. I have only one vendor pricing schema group.
    Because of this issue, I have to manually key-in condition values in PO for all condition types even though I have maintained a purchase info record.
    Please suggest, what can be reason.
    Regards,
    Praveen

    Hi,
    Thanks for clearing my doubts.
    However, I stuck-up in another issue.
    Problem is that condition type- PB00 is linked with almost all pricing schemas.
    Hence, I can't change pricing procedure  in condition type- PB00.
    Also, I can't include all J* related condition types in RM0002 as well.
    Hence, if PB00 remains as RM0002 and I maintain my pricing procedure- ZJIMPO to all J* condition types, still I am not able to create PIR for all J* conditions. Error "Condition type J1CV is not in procedure A M RM0002".
    How to handle this issue? Please suggest.
    Thanks
    Praveen

  • Returnable packaging - vendor related

    Hello SAP Gurus,
    In my current project, I meet following situations regarding vendor related returnable packaging:
    1. Packaging belongs to vendor;
    2. Packaging belongs to us (purchaser);
    3. Packaging is rent by us (purchaser).
    Our current solution is to use "Transport Equipment" - 501/M to receive such packaging when do GR of materials. But the constrains here is that warehouse stuff needs to know which material requires returnable packaging when do MIGO. And they have to manage this manually in an excel file: what material requires returnable packaging.
    Now my question is: how could we link this returnable packaging with the materials + material vendor.
    1. Possible to manage in PIR then flows to PO? (If not considerring development).
    2. If consider to generate 2nd line in PO:
    1) Again, how could Purchase Order creator know this material is required to generate 2nd line for returnable packaging?
    2) For packaging belongs to vendor, which is non-valuated and account assignment will be required;
    Many thanks in advance for your precious input and with best regards-
    Mengyu

    > 1. Packaging belongs to vendor;
    > 2. Packaging belongs to us (purchaser);
    > 3. Packaging is rent by us (purchaser).
    >
    > Our current solution is to use "Transport Equipment" - 501/M to receive such packaging when do GR of materials. But the constrains here is that warehouse stuff needs to know which material requires returnable packaging when do MIGO. And they have to manage this manually in an excel file: what material requires returnable packaging.
    >
    > Now my question is: how could we link this returnable packaging with the materials + material vendor.
    > 1. Possible to manage in PIR then flows to PO? (If not considerring development).
    > 2. If consider to generate 2nd line in PO:
    > 1) Again, how could Purchase Order creator know this material is required to generate 2nd line for returnable packaging?
    > 2) For packaging belongs to vendor, which is non-valuated and account assignment will be required;
    Hi,
    In the 1st case, Packaging belongs to Vendor:
    This is Non-valuated but stock update material type (you can maintain this exclusively for Vendor ownership & Rented since these are not your company owned)
    501-M is fine with this type. To track this in WM to identify for returns you can give a code description to be easily identifiable to trace it for the return. You/user dont have to add a second line item in the PO, but can directly enter in 501M
    In the 2nd case, packaging belongs to your own company, you can define a material type with value and qty update which can also be managed in MIGO. For this I presume you must have issued the materials to vendor before MIGO which can be received in MIGO as company's own stocks.
    Hope this helps
    Shiva

Maybe you are looking for

  • White Macbook has folder with a question mark inside when powered on.

    My brother has a white macbook given to him from a friend and when it is powered on it shows a folder icon with a question mark in the inside flashing and it doesn't boot. He has sent me on a quest to get a power adapter and a new hard drive, He thin

  • Data Commit throwing an error.

    This is the way I commit data:             protected function btnCommit_clickHandler(event:MouseEvent):void                 baa_data_svc.updt_SBJ(bAA_SBJ);                 data_chngd = false; When I try to re-open the form after a commit (shown above

  • Multiple operating system crashes- the computer has rebooted from a bugcheck

    For last couple of months I have been facing multiple crashes every day. Looking for help diagnose it. The memory dump file is 797 MB. Is there an option wherein I can make any sense out of it under guidance from community here- or should i simply tr

  • Multiple Submit / Applychanges  - Issues

    Dear All, I am having form with 3 submit buttons. 1. Submit (create) 2. submit (Approved) -> sequence ->30 3. Submit (Rejected ) -> sequence ->40 I have created 2 processes like 'submit-app' & 'submit-rej'. I have written the conditional for 2 ,3 sub

  • HOW TO CALL  RFC....

    hi...     how to call a  function module using rfc from non sap program( java, vb.net)....