Skip to Content
avatar image
Former Member

Error during Production Order creation

Hi All,

Our's is MTO scenario. We have maintiain Account Assigment Category as 'M' in Requirement Type. During creation on production order with ref to sales order system gives error "Account assignment cannot be carried out because of different origin no."

If I create the production order with ref to quotation system does not gives any error. But my requirement is to create the prod order with ref to sales order.

Please guide

Regardsd

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Sep 06, 2008 at 09:02 AM

    Dear Bala,

    For this problem you have to maintain the Account assignment category E in requirement class (OVZG) ,then u will get sale order related plan order and you have to mrp run through MD02 and MD04. Then you can see you plan order against this sale order in MD04.

    Regards

    Suneeshkumar.VR

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Sep 07, 2008 at 07:29 PM

    Hi Bala,

    In SPRO goto>Sales and Distribution> Basic Functions-->

    Availability Check and Transfer of Requirements

    -->

    Transfer of Requirements

    -->

    Define Requirements Classes

    Define Requirements Types

    --> Determination Of Requirement Types Using Transaction

    Determination Of Requirement Types Using Transaction

    In the standard system, requirements types are determined according to a specific search strategy beginning with the material strategy group.

    Strategy for Determining the Requirements Type

    1. First, an attempt is made to find a requirements type using the strategy group in the material master.

    2. If the strategy group has not been maintained, the system will determine it using the MRP group.

    3. If the MRP group has not been defined, the system uses the material type instead of the MRP group when accessing the corresponding control tables.

    4. If no requirements type is found here, the system assumes a special rule and attempts to find a requirements type with the aid of the item category and the MRP type.

    5. If this is not possible, a last attempt is made to find a requirements type with the item category only.

    6. If the last attempt fails, the system declares the transaction as not relevant for the availability check or transfer of requirements.

    Note

    You can select an alternative search strategy in the 'Source' field, for example a transaction-related procedure for determining requirements type (source = 1 or 2).

    Example

    There are business transactions, such as consignment stock processing, in which the material with its planning characteristics is not important, rather the transaction itself. An issue from the customer's consignment stock should not trigger an availability check against planning at the plant as layed down by the planning strategy but rather against special stock.

    Actions

    1. Assign the item categories and MRP type to the requirements types.

    2. Select an alternative search strategy in the 'Source' field if necessary.

    By assigning the 1 or 2 to the Source you can have the requirements in MD04 refered to order instead of the initial source document which is usually quotation. If we don't assign this then the system by default refers to the initail document created i.e. Inquiry or Quotation whichever is the first document.

    Regards,

    Karthik.

    Add comment
    10|10000 characters needed characters exceeded