Priority in Planned order

Can we define priorities to Planned order?? if so where should we define the same..
Helpful answer will be rewarded.
HT

Dear HT,
I have not understood "no concept of production order"
Any planned order has to be converted to production order/process order or you have to use REM.
Except in REM we use Co41 and COR8 for converting planned order to production order/process order.
In case of REM system will take the planned order on the start date-fiirst *** first serve basis.
Now in COR8 or CO41 there is a check box-Firm planned orders.
You can firm the planned orders with high priority and select this check button and convert the planned orders.
Please come back if you looking for some thing totally different

Similar Messages

  • Order type selection when converting from planned order to prod order

    Hello friends,
    I have one doubt.That when i am converting the planned order to the production order than from which default settings it takes the order type.
    As we can maintain the default order type in OPPQ , under conversion and in production scheduling profile also we maintain order type for make to stock, make to order, etc.
    So my question is to which setting the system gives the priority.
    Or they both are for different purpose.
    Thanking you guys in advance.

    Hi ,
       You can maintain the order type for conversion of planned order to production order in the T Code OPPE.
    Hope it will be clear.
    Regards,

  • Plan Order Conversation in to Process Order and Plan Order in Back Dates

    HII
    we are working in a process industries with three plants each of them have three order type. we have define MRP group in "OPPR" then assign each MRP group to Orde types in "OPPE". Now the problem is whn i convert plan order in process order for any material systme automaticaly pick the order type PIi01.
    2nd Problem is system system is not creating plan order for prrevios dates. say i enter PIR for month of november from first november to 30th november and run MRP on 29th the sytem create plan order on 30th of november with exception message 30.
    Regards
    Ahmed

    Dear
    Problem No 1 : we are working in a process industries with three plants each of them have three order type. we have define MRP group in "OPPR" then assign each MRP group to Orde types in "OPPE". Now the problem is whn i convert plan order in process order for any material systme automaticaly pick the order type PIi01.
    Answer :
    1.Please check the OPPR -Plant and MRP group -Select Order Type Button -Check what Order Type you have assinged here ( PI01( May be the default Process Order Type )
    2.If you are maintaing MRP group ( 0001 or 0002) , did you asisng the same in MRP1 view ?? because
    3.Did you maintain the similar Order type in OPKP -Define Production Scheduling Profile ? -This has highest priority .
    4.Did you maintain correct order type in OPJH-Maintain Order Type ??
    Refer the expert comments on the same issue : Strategy group to define production order type
    Problem No 2: 2nd Problem is system system is not creating plan order for prrevios dates. say i enter PIR for month of november from first november to 30th november and run MRP on 29th the sytem create plan order on 30th of november with exception message 30.
    Answer : You can plan the order in back dated , if you maitain Satrt date in the Past optiuon in OPU3/OPU5-Define Scheduling parameters .Goto OPU3 -Select the Order Type -Double click -Maintain 90-60 days in the Start Date in the past in Scheduling Control and Details scheduling tab .
    Hope it helps
    regards
    JH

  • Set Availability Check to Exclude Planned Order

    Hi All,
    anyone know how to set the availability check so it will not include the planned order in the calculation ?
    I find one setting in SPRO, the path is :
    Sales & distribution ==>  Basic functions ==> availability check and Transfer of Requirements ==> Availability Check  ==> Availability Check with ATP Logic or Against Planning ==> Carry Out Control for Availability Check
    select one of the record, and update filed "Incl. Planned Orders".
    I've uncheck that field, but I can't get the appropriate result. When I create a new sales order, the availability check still take the planned order I created before into account.
    The problem is, my user want to prevent creating delivery before the goods are already put in the stock. So the planned order should not be considered in the availblity check.
    Thank you in advance
    Rudy

    Hi Rudy,
    Concept of availability check is to verify if the stock is available at the time of creation of sales order. If available, when it can be ready for delivery (as Packing, arranging for transportation, etc may have lead time) & if not available, when it would be available considering Packing, arranging for transportation, etc lead time.
    Availability check whether material is available on required delivery date (backward scheduling) or not. If not available on required delivery date, system will propose next available date (forward scheduling)
    1.     Define Checking Groups
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups
    You define checking groups with which you specify the type of requirements records the system is to create when processing sales orders or deliveries
    2. Define Material Block for Other Users
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Material Block for Other Users.
    3 .Define Checking Groups Default Value
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Checking Groups Default Value.
    4. Carry out Control for Availability Check
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Carry Out Control for Availability Check.
    5. Define Procedure by Requirements Class
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure by Requirements Class.
    6. Define Procedure for Each Schedule Line Category
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Procedure for Each Schedule Line Category.
    7. Determine Procedure for Each Delivery Item Category
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Determine Procedure for Each Delivery Item Category.
    8. Checking Rule for Updating Backorders
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Checking Rule for Updating Backorders.
    9. Define Default Settings
    Menu Path: SPRO>SD>Basic Functions>Availability Check and Transfer of Requirements> Availability Check with ATP Logic or Against Planning>Define Default Settings.
    Availability checks
    1. Availability check is an integral part of the business process that determines if the required delivery quantity can be met on a required delivery date. For this purpose the system takes into account pre-delivery activities such as scheduling for picking or packing times and the time taken to produce or obtain the material. It also performs several background functions such as Backorder processing, rescheduling and ATP quantities.
    2. Backorder processing: processing of a sales order that has not been fully confirmed or not confirmed at a certain delivery date.
    3. Rescheduling: is a proposal of how – confirmed quantities already assigned to a sales order can be reassigned to other sales orders that have a higher priority.
    4. Available to promise (ATP): is a process of checking the available quantities of a material. The ATP quantity consists of warehouse stock + planned receipts (incoming stock) – planned issues (outgoing stock). to examine stock on hand (CO09) proceed to logistics – sales & distribution – sales – environment – availability overview.
    5. Replenishment lead time (RLT): is the time taken for the material to become available either internally (in house production) or externally (from a vendor). The most important things to consider during an external procurement are purchasing and MRP 2 (procurement) views of MMR where the processing time for purchasing, planned delivery time and goods receipt processing time are taken into account. On the other hand internal procurement is based on in house production time (MRP 2 view) goods receipt processing time or alternatively RLT time, which is found on MRP 3 view.
    6. RLT (Replenishment Lead Time) is the time taken for the material to become available. RLT is only used when doing an ATP check (Available To Promise). The value of RLT for a material is specified on material master record.
    7. There are three types of availability checks –
    Check on basis of ATP quantities.
    Check against product allocation.
    Check against planning.
    Configuring Availability check through Checking Groups –
    1. The checking group + checking rule determine how the availability check is to be performed.
    2. The checking group determines whether and how the system checks the stock availability and generates requirements for material planning. The checking group defines what type of requirements will be passed on i.e. summarized requirements (daily/weekly) or individual requirements for each sales order.
    3. The checking rule applies to how the availability check is to be carried out at the transaction level. Note that you must define checking rules for each individual application such as for production orders for example. In Sales and Distribution, the checking rule is specified internally within the system and cannot be changed.
    4. The checking rule, in conjunction with the checking group, determines the scope of the availability check for every business operation; that is, which stocks, receipts and issues are to be included in the availability check and whether the check is to be carried out with or without the replenishment lead time.
    5. Briefly explaining the above – checking group determines which type of requirement to be passed on to MRP whether it be individual or summarized and checking rule which is at the transaction level and can be configured independently for each application module, determines which stocks, receipts and issues to be taken into account. For performing an availability check checking group has to work in conjunction with checking rule.
    6. Advantages of individual processing over summarized processing –
    Backorder processing is possible.
    You can access (MD04) order, line and schedule line individually which gives a greater control on available stock and requirements placed on stock.
    The system automatically uses individual requirements in case of special stock items.
    7. Required data for the Availability check to be carried out –
    The Availability check must be switched on at the requirement class level.
    The Availability check must be set at the schedule line level.
    A requirements type must exist by which the requirements class can be found.
    A plant must be defined in the sales order for each schedule line item (in other words plant must be defined for every material in MMR).
    A checking group must be defined in the material master record in the MRP3 screen in the availability check field.
    8. Configuring Availability check and defining Checking Groups –
    Checking groups are introduced into the sales order based on the setting in the material master record.
    SAP standard checking groups are 01 – summarized requirements and 02 – individual requirements or you can create your own by copying the standard ones.
    Total sales and total deliveries columns are there to configure a checking rule to sum up requirements to post to MRP either individually or by day or week.
    Block quantity required can be set if you want several users to be able to process the material simultaneously in different transactions without blocking each other.
    The no check indicator is CHECKED when you DO NOT want the system to carry out ATP check.
    9. Defining material block for other users – the block check box is an indicator that enables you to block material master records of a particular material during the availability check and restrict other users from accessing same master record and reserve the material. If the block is not set, two users can confirm the same material at the same time for two different orders, not knowing if the stock is available or not. If you select this field, the material is blocked during the availability check and other users cannot: a) Make changes in the material master record. b) Create purchase orders for the material. C) Create orders for the material.
    10. Defining default values for checking groups - Checking groups are introduced into the sales order based on the setting in the material master record.
    However if there is no entry present in the material master record for the checking group, a default value can be set here, depending on material type and plant.
    This default value will be used by the system depending on the material type mentioned in MMR and plant in sales order.
    If an entry exists, this default value is over written by MMR.
    11. Controlling Availability Check – in this section, you tell the system what stock on hand and what inward and outward movements of stock it must take into account when performing the availability check in addition to whether or not to consider the replenishment lead time.
    12. These settings are based on the checking group that is assigned to the material master record and the checking rule that is predefined and assigned to the sales and distribution transaction.
    13. These settings carry out control both for sales order and delivery as well. This is due to the fact that you may want to include specific stock or incoming stock for the sales order, yet at the time of the delivery only include physical stock on hand waiting to be shipped.
    14. It is possible to indicate to the system that you would like the availability check NOT TO CHECK the stock at the storage location level. This indicator is used to set the scope of the availability check.
    15. It is used to switch off the check at storage location level. You create a reservation for a particular storage location. However, the scope of the availability check is set in such a way as to exclude the storage location. In this case, the system carries out the check at plant level only and does not take the storage location into account that is specified in the reservation.
    16. Should you not want the system to automatically check RLT, you may indicate so here. RLT is the time taken for a material to become available. It is only used when doing an ATP check and is taken from MMR.
    17. Defining the elements in the availability check entirely depends on the business needs, but a few tips are given under –
    When controlling the Availability check at the time of the sales order, a purchase requisition does not necessarily indicate by it is going to come into the plant.
    A shipping notification on the other hand - a confirmed purchase order – is a good indicator of receiving stock on a specified date.
    It is always recommended not to select the shipping notifications for the delivery requirements type as you may not actually receive the stock into plant or warehouse for which you are creating a delivery.
    Please Reward If Helpful,
    Thanks and Regards,
    Sateesh.Kandula

  • Conversion Planned Order to Production Order

    I am trying to convert planned order to production oder with the transaction code: MD04
    I am getting this error when I try to convert planned order to production oder:
    Scheduling parameters are not defined for production orders
    Message no. CT604
    Diagnosis
    No scheduling levels have been defined for production orders  in Customizing for plant T024, order type PP01 and production scheduler * . You cannot conduct any scheduling until a selection ID for detailed planning, rough-cut planning or production rate planning has been entered. The selection ID determines the priority for the selection of the routing according to the criteria task list usage, type and status.
    Moreover the scheduling type must be maintained.
    Procedure
    Maintain the scheduling parameters by entering a selection ID for detailled planning, rough-cut planning or production rate planning and select the scheduling type.
    I have retraced my steps and checked all the configuration for scheduling parameters and they all seem accurate. I am lost as to how to keep going and where to look to correct my mistake. Can someone please guide me further so that I can convert planned orders to production order. Thank you for your time.

    Dar,
    ????  Now I am wondering how you were able to 
         ...checked in the following places:
    Define Production Scheduling Profile
    Define Production Scheduler
    Define Scheduling Parameters for Operations
    At any rate, basic questions by students are best addressed in one of the 'Community Discussion' forums, such ast Test and Playgound  Try SCN Features
    As always, in the T&P forum, like this one, it is expected that the questioner will first perform their own basic research, before posting a question, according to the rules of engagement.
    Best Regards,
    DB49

  • Priority to production order

    Dear all,
        I want to assign the priority to production order in the priority field. But I was not able to find the customization for the same. Pl help me in that regards.

    Hi Mangesh,
    The Priority field is useful at the production level. In the header table of creation of production order,we can assign the priority of that particular order like 1,2,3,4.if we have two or more production orders using same workcenters based on the priority, we can use this priority field.It is only for information purpose.
    It reflects on the execution of capacity planning(CM01).This is for manual verification at the shop floor control for completing the production order.
    Regards,
    srivas

  • 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

  • Error while creating a Planned Order

    Hi SAP Experts,
    I have an error encountered while creating a Planned Order which is "Mode linkage problem with mode number".
    Diagnosis:
        An application program called an LCA routine and the following error occurred:
        An order has at least one condition with mode linkage with the same mode number. The activities of this condition must have compatible modes. The modes are compatible when each mode of one activity has a mode for the other activity with the same mode number. The first activity that violates the condition is given in the return code table in ABAP.
    Please enlighthen me what is this error and what should be done to this error.
    Thanks in advance,
    Raymond

    Check the PPM or PDS being used in the Planned Order.
    Most likely you have a Setup Activity followed by Produce Activity. However the Mode (i.e. Resource) used in the two activities are different. The same Mode needs to be used both in Setup and corresponding Produce activity.
    Hope this helps,
    somnath

  • Creation of SNP planned order based on PDS

    Hi,
    I'm a APO developer and I have the following problem:
    I would like to create a SNP planned order based on a PDS (like e. g. in the planning book when you input a number into a cell in the "Production (Planned)" line).
    Up to now I've only managed to create such an order without using the PDS.
    Can you name me a function module which allowes me to do that?
    Thanks in advance.

    Hi,
    I've now managed to create this kind of order.
    I set a breakpoint at the function module /SAPAPO/DM_PROD_ORDER_CHANGE and checked how it was filled in the planning book.
    For those who want to know:
      INCLUDE /sapapo/constants_om.
      CONSTANTS:
        lc_order_type_1f        TYPE /sapapo/om_order_type VALUE '1F'.
      DATA:
        ls_prod               TYPE /sapapo/msnp_prod,
        lt_prod               TYPE /sapapo/msnp_prod_tab,
        ls_sources            TYPE /sapapo/sources,
        lt_sources            TYPE /sapapo/sources_tab,
        lv_matid              TYPE /sapapo/matid,
        lv_locid              TYPE /sapapo/locid,
        lv_vrsioid            TYPE /sapapo/vrsioid,
        lv_tstfr              TYPE /sapapo/timestamp,
        lv_tstto              TYPE /sapapo/timestamp,
        lv_simsession         TYPE /sapapo/om_simsession.
    lv_vrsioid = '000'.
    * Create SimSession
    CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
        EXPORTING
          iv_simversion              = lv_vrsioid
          iv_simsession             = lv_simsession
          iv_simsession_method = 'N'
          iv_perform_commit       = space
        EXCEPTIONS
          lc_connect_failed        = 1
          lc_com_error             = 2
          lc_appl_error            = 3
          multi_tasim_registration = 4.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    * Get PDS
      CALL FUNCTION '/SAPAPO/MSDP_SNP_PPM_VALIDITY'
        EXPORTING
          iv_vrsioid      = lv_vrsioid
          iv_matid        = lv_matid
          iv_locid        = lv_locid
          iv_tstfr        = lv_tstfr
          iv_tstto        = lv_tstto
          iv_planstart    = lv_tstfr
          iv_planend      = lv_tstto
        CHANGING
          ct_sources      = lt_sources
        EXCEPTIONS
          wrong_interface = 1
          error_occured   = 2
          OTHERS          = 3.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
      READ TABLE lt_sources INTO ls_sources INDEX 1.
      ls_prod-version       = lv_vrsioid.
      ls_prod-matid         = lv_matid.
      ls_prod-locid         = lv_locid.
      ls_prod-plobid        = '9AMALO'.
      ls_prod-tstmp         = lv_tstfr.
      ls_prod-catgr         = 'PP1'.
      ls_prod-categ         = 'EE'.
      ls_prod-categ_prku    = 'EE'.
      ls_prod-categ_prse    = 'EL'.
      ls_prod-kz_prod       = '9APPROD'.
      ls_prod-kz_prku       = '9APPROD'.
      ls_prod-kz_prse       = '9ADMDSE'.
      ls_prod-produ         = '1000'.
      ls_prod-proid         = ls_sources-trpid.
      ls_prod-mosta         = gc_new.
      ls_prod-order_type    = lc_order_type_1f.
      ls_prod-is_fixed      = 'X'.
      ls_prod-snp_is_header = 'X'.
      APPEND ls_prod TO lt_prod.
      CALL FUNCTION '/SAPAPO/DM_PROD_ORDER_CHANGE'
        EXPORTING
          ic_database           = 'LC'
          ic_application        = '4'
          iv_simsession         = lv_simsession
          it_prod               = lt_prod
          iv_netch              = 'X'
        EXCEPTIONS
          material_not_supplied = 1
          location_not_supplied = 2
          OTHERS                = 3.
    * Merge simulation version (to commit order changes)
      CALL FUNCTION '/SAPAPO/TSIM_SIMULATION_CONTRL'
        EXPORTING
          iv_simversion                = lv_vrsioid
          iv_simsession                = lv_simsession
          iv_simsession_method         = 'M'
        EXCEPTIONS
          lc_connect_failed            = 1
          lc_com_error                 = 2
          lc_appl_error                = 3
          multi_tasim_registration     = 4
          target_deleted_saveas_failed = 5
          OTHERS                       = 6.
      IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.

  • Issue in creation of Planned Order

    Hi all,
    There is a customer requirement on 08.02.2010 and there is shortage quantity as we don't have enough stock in the warehouse to cover the cust req. So when I run the MRP, planned orders are not getting created on 8th. Can you please tell me what could be the reason?
    Regards,
    Brijesh

    Hi,
    Are you saying that the planned order is not getting created at all or is it being created for an earlier date?
    If it is not being created at all, check in your sales order, whether the schedule line category is CP i.e. MRP relevant & in MD04 you notice the demand. Also check if the material is MRP planned & has a planning file entry (check using MD21, if no entry, make an entry via MD20).
    If it is being created, but at an earlier date, then check the lot sizing procedure. It could be that the lot sizing procedure is weekly or monthly & system has combined the needs & put a supply proposal at an earlier date.
    Check the above & revert with additional info if it does not resolve the issue.
    Regards,
    Vivek

  • User exit/ badi needed for planned order create/change,collective ATP check

    Dear All,
    I'm looking for a user exit/ badi which can be used for planned orders at the stage of
    mass collective availability check (COMAC tcode) update; or at some other relevant stages of mass update of planned orders.
    I need after collective availability check to perform the following:
    1) to copy date from "total comitment" field on header tab of planned order and paste it (replace old date) to order finish date on header screen
    then
    2) to start a scheduling.
    Very appreciate your help.
    Best Regards,
    Andrey
    Edited by: Andrey Kruglov on Apr 15, 2010 3:06 PM
    Edited by: Andrey Kruglov on Apr 15, 2010 3:07 PM

    Dear,
    Use the BAPI : BAPI_PLANNEDORDER_CHANGE
    Or use the function module MD_SET_ACTION_PLAF for Schedule planned order.
    and the transaction MDAC Execute action for planned order
    This function module includes the following actions:
    Explode BOM
    Explode BOM, check availability
    Check availability, only explode BOM in the case of a requirement
    Check availability, do not explode BOM
    Reset availability
    Change planned order data
    Schedule planned order
    Delete planned order
    Assign the key for the respective action control to the materials in the material master (MRP 4 view).
    Please refer this thread,
    Re: MDVP for collective orders
    Regards,
    R.Brahmankar

  • MD06  Issue - Planned orders not getting displayed

    Hello,
    Planned order with the exception "Newly created order proposal" does not get displayed in MD06 with the option "Only Unprocessed MRP Lists" in the processing indicator.
    I am running MD06 report with the following parameters:
    Plant
    MRP Controller
    Exeception Group - All exception selected except 8-Terminations
    Processing indicator - Only unprocessed MRP LIsts, Only with new exceptions
    My material which has a newly created planned order thorugh MRP run with exception "1 - Newly created order proposal" does not get displayed.
    Only when I specify Only processed MRP lists or All MRP LIst in the processing indicator, this material gets displayed. The planned order is for a Stock Transfer order to this plant (receiving plant). How is the MRP LIst processed?
    Please help me out with this issue.
    Sincerely,
    Ketan

    Hi Ketan,
    When you execute the MD06 report, you would find a column with the heading CI, if am right it would be just after the MRP cntlr, here you would find a Pencil & a tick mark. If you find them both, it means the row is unprocessed, but if you find only a tick mark it means that the row is processed.
    So now check for the planned order, it would be just a tick mark & hence would be showing only for the processed MRP list or all MRP lists.
    To process a row or unprocess, just click on the icon & it changes.
    Check & revert if it answers your query.
    Regards,
    Vivek

  • Restrict Product Allocation if Planned order is not getting created

    Hello All,
    We have a scenario that when ever a Sales Order is getting created, Product allocation assignment will be done automatically and planned orders will be created for that requirement in APO.
    There are some cases where in because of wrong Variant Configuration, Planned orders wont be created. Our requirement is to delete the Product Allocation automatically or to stop the product allocation assignment if the planned orders are not created.
    Do we have any standard setting for doing so or Kindly suggest me some BADI's which can be used for it.
    Thanks in advance.
    Best Regards,
    Srinivas.D

    Srinivas,
    A rather odd requirement.
    Have you tried in SCM APO 'Maintain check instructions' to perform the product check first, then allocation?  I would think that if the product check failed, then allocation would not be consulted, and no allocation therefore assigned.
    IMG > APO > GATP > General Settings > Maintain check instructions
    Best Regards,
    DB49

  • Planned Order to Purchase Order report in SAP

    Dear All
    The Business process is Planned Order - Converted to Purchase Requsition - Converted to purchase order .
    Is there any report in SAP , which shhows the direct link between Planned order to Purchase Order ?
    Regards
    Shyam

    I have never seen a standard report, build a query based on tables PLAF, EBAN and EKET should be involved

  • Production order and planned order qty should not consider in MRP

    Dear All,
    i do not want to consider the previous month production order qty and plenned order qty (Nothing but WIP qty) in the current momth MRP, but the stock has to consider in MRP.
    Example,
    Before MRP,
    material : XYZ
    Stock : 1000
    Prod Qty : 500 for 02.04.2008
    PIR Qty : 2000 for 02.05.2008
    After MRP, the requirement should be as below said,
    material : XYZ
    Stock : 1000
    Prod Qty : 500 for 02.04.2008
    PIR Qty : 2000 for 02.05.2008
    Pld OrdQty : 1000 for 02.05.2008
    For the above requirement ,i have done settings in the availabilty check like , for include planned order and include production order are "DO NOT TAKE IN ACCOUNT".
    Even then also the planned order qty is generating for the "500" only.
    please give the solution for the above said requirement.
    thanx in advance
    Regards
    Srinivas

    hi
    MRP will always consider the prod order qty while doing nert req calculation.One thing u can do is TECo the prod orders and un MRP then it wont consider prod order qty.
    The Availability check will check whether the components r avalaible or not based on ur scope of check
    Reward points if useful
    Amit

Maybe you are looking for