cancel
Showing results for 
Search instead for 
Did you mean: 

MDBT and "Special procurement" (MRP 2 view) issue

Former Member
0 Kudos

Hi PP Gurus

I hope you'll can help me out with this issue:

I'm running the MRP using the background function (MDBT), I'm running it for Plant 8000 (in this plant I make Customer Orders), but I'm using the a Special procurement Key (40 - Stock transfer - proc.from alter.plant) so this order can be manufactured in another plant, say plant 2000.

When running the MRP using t.code MD02 in plant 8000 the system is generating next planning elements:

Plant 8000 (MRP run using T.cod MD02):

03.04.2009 CustSt 1000000076/000010

03.04.2009 CusOrd 1000000076/000010/0001

06.05.2009 PldOrd 0000022865/STPO

Plant 2000: (No need to run MRP, the system generates next elements automatically in plant 2000)

03.04.2009 CustSt 1000000076/000010

05.05.2009 PlORel 0000022865/STPO

06.05.2009 PldOrd 0000022866/SO

Using T.code MDBT I'm getting these results:

Plant 8000:

03.04.2009 CustSt 1000000076/000010

03.04.2009 CusOrd 1000000076/000010/0001

06.05.2009 PldOrd 0000022937/STPO

Plant 2000:

03.04.2009 CustSt 1000000076/000010

05.05.2009 PlORel 0000022937/STPO

As you can see, the system is not generating a PldOrd in plant 200 when using t.code MDBT. Hope you can help me out with this issue

Thanks!!

Elías

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi,

Go to OM0E & check the sequence of scope of planning. It should be plant 8000 first followed by plant 2000. Check & revert.

Regards,

Vivek

Former Member
0 Kudos

hi Vivek

Thanks for your help.. it works!!! but know I have a problem.. after making the parameters you told me It worked well, but one doing it again it didn't work... any idea??

Thanks again

Elías

Former Member
0 Kudos

Hi,

Your posting says it worked & also dint work, can you please clarify whether it is working or not?

Regards,

Vivek

Former Member
0 Kudos

Hi again

Yes, in fact the issue is solved, after making the changes you suggested me it worked out... know the problem is regarding performance issues; when running the MRP it takes about 30 seconds to show me the results, may be, I'm over reacting about the duration... 30 secons is nothing, but the issue is that I have only made 1 sales order and there are few components in the BOM, and there are no ussers logged to the server... any idea???

Thanks

Elías

Former Member
0 Kudos

Elias,

Any idea.....about what? I didn't really see a question, but I am assuming you are asking "what will be the impact to the length of time of the MRP run when I add additional users and additional Sales orders".

The answer is, 'It will take longer'.

Question: "How much longer?"

Answer: "It depends on a number of factors"

MRP typically performs millions of calculations in a large production environment. These calculations take processing time. MRP also reads and writes tremendous amounts of data to and from the underlying database manager (eg, Oracle, etc). The DBM in turn consumes storage space and storage array R/W resources. All of these activities consume time.

As you move from blueprinting to testing, you will gain more insights about how long it will take MRP to run in YOUR production system.

Duration can be shortened by using net change MRP. Duration can further be shortened by limiting the scope of each planning run (eg, just certain plants). It is also possible to use the standard MRP userexits to further refine a subset of parts to run. Parallel processing can sometimes reduce the duration.

That being said, there is only so much you can do from the application side. In large shops, MRP usually runs in background, during periods of least activity. I have seen MRP runs take longer than 8 hours. Once you have done your best job in the app to reduce your MRP duration, you then have to think about implementing a hardware solution. Adding additional CPU to SAP app servers will almost always give duration improvements to calculation intensive processes such as MRP.

[Here|http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000071611&] are some generic SAP sizing guidelines - and, before you ask, no, I am not an expert in this area and I do not understand much of this techy stuff. I tend to use the practical approach: Try it. If it works, great. If it doesn't work, then fix it.

If you are worried, you should set up larger scale test scenarios, and perform stress testing. This is a good practice anytime you are implementing completely new processes that will use large sets of data.

I assume you are currently making these changes in your sandbox or development instance. These instances are typically smaller than the production instance, so MRP durations will be longer. There may not be any problem once you migrate to production.

Regards,

DB49

Former Member
0 Kudos

Hi DB49

I really want to thank you for your answer, it is really useful...and please let me explain my self a little bit more:

Actually I have customized the "Scope of Planning" just to considert 7 plants; when using MDBT I get the "Finished" status of the run about 1 second later after pressign the "Stat Inmediately" push button, but its about 1 minute later that I'm able to see a planning element in the Stock Requirement List. At the beginning I thought that there might be an error but then I realized that although having a Finised status in both MDBT and SM37 I had to wait some seconds (or even minutes) to see planning elements already created.

As you mentioned in your reply right know I'm in a testing phase using the QA server; that's why some times I prefer to run indivual MRP runs for finished products insted of using the background function.

After reading your reply I will focus on doing some test to the system and see what happens with more elements to plan.

When I was asking for some ideas of what might be happeging I was refering to the fact that there is a time frame (betwen the time I have the "Finished" status in MDBT and SM37 and the time I see planning elements in MD04... from 30 seconds to 1 minute) where I don't know if the MRP has already run....

Thanks again

Elías

But when using

Answers (0)