Dear SAP Friends,
Please tell the exact meaning , use & effect of Exception Message.
What they indicate & how they will generated?
Plzz reply.
Thanks & regards,
chandra.
Request clarification before answering.
Hi,
Exception messages depend on the transaction being carried out and are meant to inform you of an important or critical event (for example, start date lies in the past, safety stock has been exceeded).
By means of the exception messages, you can easily sort out any materials that you need to reprocess manually.
Exception Messages are assigned to the Exception Groups.
System will suggest the Exception messages and depending upon the requiremen t the MRP Controller can manually intervene and act upon the MRP Element.
Hope this helps..
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear,
exception messages are generated by system to indicate the process exceptions...while running MRP, as per the customization settings you may get planned orders whose date is in past. Hence system will issue a EM for this so that planned can take appropriate action.
This is basically to inform planner that what are the issues associated after planning and needs his attention, and action by him will reduce the problem in future.
Someof the simillar EM are grouped under a EM group
There are reports like MD06, MDLD which will give gthe list of materials accoding to EM groups so that planned can take action
Example is givenn below
Group -
Message -
Description
69 Recursive BOM components possible
1 02 New, and opening date in the past
05 Opening date in the past
2 03 New, and start date in the past
06 Start date in the past
63 Production start before order start
3 04 New, and finish date in the past
07 Finish date in the past
64 Production finish after order finish
4 01 Newly created order proposal
42 Order proposal has been changed
44 Order proposal re-exploded
46 Order proposal has been manually changed
61 Scheduling: Customizing inconsistent
62 Scheduling: Master data inconsistent
80 Reference to retail promotion
82 Item is blocked
5 50 No BOM exists
52 No BOM selected
53 No BOM explosion due to missing config.
54 No valid run schedule header
55 Phantom assembly not exploded
6 25 Excess stock
26 Excess in individual segment
40 Coverage not provided by master plan
50 Shortage in the planning time fence
57 Disc. matl partly replaced by follow-up
58 Uncovered reqmt after effective-out date
59 Receipt after effective-out date
70 Max. release qty - quota exceeded
96 Stock fallen below safety stock level
7 10 Bring process forward
15 Postpone process
20 Cancel process
30 Plan process according to schedule
8 98 Abnormal end of requirements planning
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 13 | |
| 12 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 2 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.