Order Management - EBS (MOSC)

MOSC Banner

order.png

Nilesh Pardakhe
Nilesh Pardakhe Posts: 14 Blue Ribbon
edited Sep 11, 2014 12:59PM in Order Management - EBS (MOSC) 5 comments

Comments

  • Tanzeel Mirza
    Tanzeel Mirza Posts: 840 Gold Badge

    Hi @Nilesh Pardakhe

    Do you have the Customer PO Number, Salesrep and Unit Selling Price populated?

    Please provide the screenshot showing the Order on the Quick Sales Order Screen.

    Generally this error comes if the above information is not existing on the Order.

    Thanks

  • Nilesh Pardakhe
    Nilesh Pardakhe Posts: 14 Blue Ribbon

    Hi @Nilesh Pardakhe

    Do you have the Customer PO Number, Salesrep and Unit Selling Price populated?

    Please provide the screenshot showing the Order on the Quick Sales Order Screen.

    Generally this error comes if the above information is not existing on the Order.

    Thanks

    @Tanzeel Mirza,

    The order was a standard order and all the suggested field were populated on the order. We have tired to book the order into another Org for the same BU and were successful. But caused the error while booking on one specific Org.

  • Tanzeel Mirza
    Tanzeel Mirza Posts: 840 Gold Badge

    @Tanzeel Mirza,

    The order was a standard order and all the suggested field were populated on the order. We have tired to book the order into another Org for the same BU and were successful. But caused the error while booking on one specific Org.

    Hi @Nilesh Pardakhe

    You can try the below option. Hope this should resolve the issue. If not please confirm the version of your application.

    1) Run the “Workflow background process” from “System Administrator” with parameters as 

    1. Item type – OM Order Line

    1.2. Process Deferred - Yes

    1.3. Process Time out - Yes

    This will book all the deferred orders.

    If this doesn't resolve the issue then try option 2.

    2) This issue can also be caused if no workflow is associated with the corresponding order header. The ultimate root-cause is unknown and is suspected as a corrupted (header) transaction type.   The below solution can be used to verify the solution.

    a) Recreate the offending transaction type in duplicate.

    b) Retest using this newly generated transaction type.

    c) Migrate, and end-date the old transaction type, if testing successful.

    Please let me know if this resolves the issue or not. I will try to find other solutions and let you know.

    Thanks

    Mirza Tanzeel

  • Tanzeel Mirza
    Tanzeel Mirza Posts: 840 Gold Badge

    @Tanzeel Mirza,

    The order was a standard order and all the suggested field were populated on the order. We have tired to book the order into another Org for the same BU and were successful. But caused the error while booking on one specific Org.

    One more thing which you need to check if there is any Form Personalization on the form which is restricting the order from getting booked.

    As far as I remember the event on the Book Button is OM_PRE_BOOK_EVENT and may be some message of ERROR type is being shown and restricting you from booking the order.

    If you change the type of message from ERROR to WARN or SHOW or any other, I think it should allow you to book the order after you click OK the message being popped up.

    Please let me know.


    Thanks

  • This usually occurs when the SO LINE TYPE does not have an appropriate workflow at the line level.

    Whatever your workflow assigned to the LINE TYPE may not have a booking step in it.

    Check the wflow assigned to the LINE TYPE, if you are using  custom workflow switch to standard (Seeded) flow and try again.

    If the error disappears it will confirm that customer wflow has an issue.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center