We have added search box. Key in SAP issue keyword to search
TopBottom

Announcement: wanna exchange links? contact me at sapchatroom@gmail.com.

RE:[sap-log-mm] PR Deleted when the next MRP Run

Posted by Admin at
Share this post:
Ma.gnolia DiggIt! Del.icio.us Yahoo Furl Technorati Reddit

Reply from ha_tran on May 30 at 11:19 PM
Hi Buffy,

Question 1: This is the standard SAP functionality which is logical as SAP will verify again in your next MRP run if there is still a material shortage. If not, then SAP will automatically remove the existing un-processed PR which was generated from the previous run.
Question 2: There are two alternative solutions you can choose - 1) Either build it via the setting of your release indicator (if you are using release strategy for your PR); or 2) Firm it in MD04 transaction. Another option you can consider is to convert your PR into RFQ as soon as it is generated.
Question 3: There is not any customisable message.

Cheers,
HT

---------------Original Message---------------
From: Buffy Anything
Sent: Wednesday, May 30, 2012 9:51 PM
Subject: PR Deleted when the next MRP Run

Dear Expert,

May I your help about PR which created from Planned Order?

Our scenario of process:
1. MRP generated the Planned Orders
2. User converted to PR and awaiting to release PR
3. The next MRP run and PR deleted

Questions:
1. Why PR deleted when the next MRP run? Is it the business practice?
2. How to prevent PR deleted from the next MRP run?
3. Any rules from the customizing manange this scenario ?

Thank you in advance.

Regards,
Buffy

 
Reply to this email to post your response.
 
__.____._
Manage Settings | Unsubscribe | Create FAQ | Send Feedback
  
Copyright © 2012 Toolbox.com and message author.
Toolbox.com 4343 N. Scottsdale Road Suite 280, Scottsdale, AZ 85251
 
ha_tran  
Senior SAP Supply Chain Business Analyst
achievements
 
Mark as helpful
View this online
Ask a new question
 
In the Spotlight
Toolbox.com for iPhone & Android: Ask Questions & Get Answers Anywhere. Download the Free App

_.____.__

0 comments:

Post a Comment

T r a n s l a t e to your language