Skip to Content
author's profile photo Former Member
Former Member

Can't dispatch planned order (LA), but can dispatch production order

Hello,

I'm new to capacity planning and all of the related configuration screens. I'm probably missing something simple. We've configured our work centers and routings. We've configured our production order types (tcode OPU3, type US01) and planned order types (tcode OPU5, type LA) so that all create capacity requirements and are relevant to 'detailed scheduling'. Requirements are being generated for production orders and planned orders. We can see correct setup and production times in the graphical planning table CM21.

Here's the problem: When we try to dispatch a planned order, nothing happens. There is no error, but the order is not dispatched. If we convert the planned order into a production order, accepting all SAP proposed defaults, and then try to dispatch the production order, it works fine.

What configuration are we missing? My first thought was to look in OPU5 for order type LA. In the detailed scheduling section, scheduling horizon is zero (is this Ok?), SelID: Detailed is 01, 'scheduled' and 'generate capacity reqs' are checked.

Thanks,

Randy

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Apr 03, 2008 at 03:57 AM

    Hi,

    Please check below points,

    Lead time scheduling for Planned order.

    Select suitable Strategy Profile at capacity Planning table (For EX SAP___T001)

    After dispatching the planned order check with Log Message - This will give some idea.

    Please try with CM25.

    Regards

    Pradeep

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Randy -

      In your config settings in transaction OPPQ - you maintain default setting for different transactions by plant.

      Execute this transaction and type in the plant you are using to try to dispatch planned orders.

      Click on Maintain

      Click on the Conversion button under the Planned orders section.

      Click on the Planned Order --> Production Order button.

      Make sure you have a default order type filled in for the Production order field.

      An OSS note explains that the the system, when dispatching planned production orders, temporarliy converts the planned order to a production order to determine dates/times. For some reason it bypasses the material master production scheduling profile which would determine an order type and looks here instead. When it doesn't find a setting here it does nothing. They really should consider putting an error message in but .. they have not yet.

      Hope this works!

      Rachael

  • Posted on Apr 02, 2008 at 09:11 PM

    Randy ,

    Please analyse the below note related to your issue.Hope this will help you to sort out the problem.I have cheked the configuration area.I hope u are correct .In fact , it may related to your production version if you do automatic dipatch.Please reade the note and come back.

    If an error arises when automatically dispatching planned orders (for example, a capacity overload at a work center) then the system schedules the affected planned orders to another production line.This function is available in both types of planning table. It is of interest for all areas that use planned orders, for example in repetitive manufacturing or in MRP/MPS. It can also be used in production control when later converting planned orders to production orders.

    this function the following conditions must be met:

    The dispatching function Change production version on error must be set in the strategy profile.

    The original work center

    must be entered in the production version of the material as the production line (not necessarily in the current production version).

    can only be assigned to one operation in the routing for this production version

    The alternative work center can only be assigned to one operation in the routing for the alternative production version

    If an error arises the system copies the production version with the version key that is next alphanumerically into the planned order. The planned order is rescheduled with this production version. However, it is not dispatched to the new production line but remains in the pool. In this way you can dispatch the rescheduled planned orders together with other planned orders in the pool to the new production line.

    To give you a better overview and to improve handling you should choose a sort key with which the planned orders in the pool are sorted according to work center and, for example, latest start date. All orders that are to be dispatched to a production line are then placed next to one another in the pool. If an error arises during automatic dispatching to the new line every planned order affected is rescheduled with the next production version

    . If the conditions are not met then the following occurs depending on your settings in the strategy profile:

    Dispatching is terminated

    Dispatching to the same work center is continued and error messages are written to the planning log

    You can only dispatch main operations with this function, but not sub-operations. Operations are always dispatched with the full quantity to the new work center

    Reward point if useful

    Regards

    Jia

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.