Skip to Content

Cannot limit BOM Usage to convert Production Order

Dear Experts,

In our company, we have 3 kinds of BOMs for Production -

E-BOM

P-BOM

F-BOM

For creating Production Order, especially to convert from MPS Planned Order in MD04, we only allow the F-BOM. In one of our client, i.e. client 138, it was setup previously so the following error message was prompted when it is NOT F-BOM (e.g. P-BOM) to convert Production Order from MD04 -

P BOM exists , it is unable to be converted.

Message no. ZBC001

However, in our another client 118, we had configured the same (e.g. specified F-BOM for BOM Application in OPL8) and used a P-BOM to test but didn't find the above error msg.

The difference between two clients is that no component and exception msg "52" were found for the MPS Planned Orders in MD04 of client 118 while there were components and no exception msg was found for the MPS Planned Order in MD04 of client 138.

Could you advise how to solve our above problem in client 118 ?

Many Thanks,

KH Fong

Add a comment
10|10000 characters needed characters exceeded

Related questions

2 Answers

  • Posted on Jul 06, 2016 at 09:07 AM

    Attached is the relevant screens for your ref. -

    In client 118 , exception msg "52" found in MD04 and cannot block to convert to Production Order -

    In client 138, exception msg is not found and can block (with the above error msg) to convert to Production Order -

    Both of the above FG Materials are belong to P-BOM (not F-BOM).

    Any expert can help to advise solution for our above problem ?

    Tks,

    KH Fong


    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jul 06, 2016 at 09:20 AM

    Kwok,

    Use of acronyms which do not exist in the SAP standard glossary does not make a question any easier to answer.

    Anyhow, let me see if I understand this question, by attempting to restate your situation:.

    1. You have created a custom functionality in one client, which triggers a custom popup message for that client's solution, and also prevents certain standard SAP activity..

    2. You have attempted to create a similar functionality in another client, and this functionality does not work in the same way that it does in the first client.

    3, You are asking us in SCN, none of whom have access to either system, and none of whom have the slightest clue about the design of the custom solution, to tell you why the custom solution does not work as you expect in the second client.

    Is that an accurate summary of your question?

    Best Regards,

    DB49

    Add a comment
    10|10000 characters needed characters exceeded

    • Dear Solomon (& other Experts),

      Refer my above msg on 2016-7-6 6:53am which I had already mentioned our problem in details.

      Refer my above msg on 2016-7-26 11:34am which I had further explained our problem and found solution (by ourselves) in details. Basically, we had solved our above problem (in MD04) by comparing and adjusting transactions OS21 & OS31.

      The rest of questions (by interest) are -

      Q1) Is it possible to block MANUALLY created Planned Orders & Production Orders for if it is NOT F-BOM usage (e.g. P-BOM) ? Our BOM usages were mentioned on the above msg on 2016-7-26 11:34am.

      Q2) If the above Q1 is "Yes", how to enable such blocking to block the MANUALLY created Planned Orders & Production Orders ?

      Tks,

      KH Fong

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.