MRP Exception Description

Dear Gurus,
I am looking for documentation which would provide detailed definition of MRP Exception messages. I found one on http://www.sap-basis-abap.com/index.htm but would greatly appreciate if you could suggest other good sites which provide this type of information (MRP functions and logic).
My experience is with another large ERP and this will help me speed up my learning curve.
Thank you.
Francois P.

Hi.
You can check
http://help.sap.com/saphelp_470/helpdata/en/f4/7d3f9344af11d182b40000e829fbfe/frameset.htm
Or refer to Sap Note --> 178804

Similar Messages

Exception Description: No conversion value provided for the attribute

Hi!,
The following is printed when I try to persist an entity with a an enum attribute in it. It deployted succuessfully and mapped fine a table, my configuration is, Windows2003, SJSAS 9 FCS, Derby DB.
Exception [TOPLINK-115] (Oracle TopLink Essentials - 2006.4 (Build 060412)): ora
cle.toplink.essentials.exceptions.DescriptorException
Exception Description: No conversion value provided for the attribute [NEW].
Mapping: oracle.toplink.essentials.mappings.DirectToFieldMapping[status-->REPORT
.STATUS]
Descriptor: RelationalDescriptor(com.namespace1.reports.persistence.Report --> [
DatabaseTable(REPORT)])
The Entity class is the following:
* Report.java
* Created on 25 �� , 2006, 06:07 �
* To change this template, choose Tools | Template Manager
* and open the template in the editor.
package com.namespace1.reports.persistence;
import java.io.*;
import java.util.*;
import javax.persistence.*;
* @author Administrator
@javax.persistence.Entity(name="Report")//name used in EJB-QL.
public class Report implements Serializable {
public enum ReportStatus{
NEW,
OPEN,
SUBMITTED,
ACCEPTED,
REJECTED
@javax.persistence.Id
@javax.persistence.GeneratedValue(strategy = javax.persistence.GenerationType.AUTO)
private long id;
@Transient
private int currentEntryId;
@Column(length=256)
private String title;
private String ownerName;
@Enumerated(EnumType.ORDINAL)
@Basic
private ReportStatus status;
@OneToMany(mappedBy="report",targetEntity=ReportEntry.class,cascade=CascadeType.ALL)
private Map<Integer,ReportEntry> reportEntries;
/** Creates a new instance of Report */
public Report() {
public long getId() {
return id;
public void setId(long id) {
this.id = id;
public int hashCode() {
int hash = 0;
hash += (int)getId();
return hash;
public boolean equals(Object object) {
// TODO: Warning - this method won't work in the case the id fields are not set
if (!(object instanceof Report)) {
return false;
Report other = (Report)object;
if (this.getId() != other.getId()) return false;
return true;
public String toString() {
return "com.namespace1.reports.persistence.Report[id=" + getId() + "]";
public int getCurrentEntryId() {
return currentEntryId;
public void setCurrentEntryId(int currentEntryId) {
this.currentEntryId = currentEntryId;
public String getTitle() {
return title;
public void setTitle(String title) {
this.title = title;
public String getOwnerName() {
return ownerName;
public void setOwnerName(String ownerName) {
this.ownerName = ownerName;
public ReportStatus getStatus() {
return status;
public void setStatus(ReportStatus status) {
this.status = status;
public Map<Integer, ReportEntry> getReportEntries() {
return reportEntries;
public void setReportEntries(Map<Integer, ReportEntry> reportEntries) {
this.reportEntries = reportEntries;
}

This problem is side effect of issue 193 (https://glassfish.dev.java.net/issues/show_bug.cgi?id=193) and is described in details in issue 634 (https://glassfish.dev.java.net/issues/show_bug.cgi?id=634). Your choices are to use the work around described in the above issue or switch to the GlassFish build with the fix.
regards,
-marina

MRP exception message 64 and planning strategy group 52

Hi Gurus,
I have done extensive search online in the forum to find the route cause why we are getting MRP exception message 64 for a specific material in one of our plants. This exception message does not occur for the same materials which is also produced in another plant.
I was just wondering whether the planning strategy group of 52 in MRP 3 view would have any effect on the frequent occurrence of exception message 64. I know that the 64 message occurs when the routing time is higher than the in house production time. If that's the case where to look for in routing to correct this, apart from this do we need to look at work centers and other details. I'm not a PP person but still was curious to know see if i could take a shot at it.
Also the MRP settings that we follow in the plant where this problem does not occur is NETCH, Create PR - 2, Schedule lines - 3, create MRP list - 1, Planning mode - 3, scheduling -2
in the plant where the 64 message occurs quite often is Netch, Create PR -2, Schedule lines - 3, create MRP list - 1, planning mode - 1, Schdeduliing - 1
I was thinking do MRP settings and planning strategy group would have any impact on why we are getting the 64 wexception message
Because of this 63 exception message, the downstream components are getting wrong signals.
Thanks
Ravi

Hello Ravi
Generallt, exception message "64 - Production finish after order finish" is triggered when the order start date is in the past and system automatically changes to forward scheduling to calculate the finish date.
Note 1913017 explains how the order basic date is calculated and adjusted in case of forward scheduling, however, you are using strategy 52 and this is a very special scenario, whever VP planned orders are generated.
The VP planned orders will always be adjusted to the requirements date even if the requirements date is in the past. This is a special feature in the planning segment, since these orders are only kind of 'virtual' planned orders. These orders only have to provide the demand requirements for the components in time.
Therefore, there is a relationship between strategy 52 (VP planned order) and the exception message observed.
BR
Caetano

[JPA] Exception Description: Missing meta data

I'm getting the following error message trying to compile a simple EE App that
contains a single Entity Class.
Exception Description: Missing meta data for class [java.lang.Integer].
Ensure the class is not being excluded from your persistence unit by a
<exclude-unlisted-classes>true</exclude-unlisted-classes> setting.
If this is the case, you will need to include the class directly by adding a
<class>[java.lang.Integer]</class> entry for your persistence-unit.That class contains a private Map<Long, Integer> list and I'm using SJSAS 9 and NetBeans 5.5.
Thanks in advance,
Stefano

I'm also experiencing this problem.
I'm pretty sure the cause of this is your "Map<Long, Integer>" and my "List<Integer>".
Doesn't GlassFish implement this JPA specification?
I see the post is been unreplied for a month: Please, somebody help us!
Tks,
Raul Oliver

MRP Exception Message 26: Excess stock in individual segment

We would like to modify the logic relating to MRP Exception Message 26: Excess stock in individual segment to allow for a material-specific tolerance threshold, within which no exception would be generated. An alternate approach might be to deactivate message 26 and create a new custom exception that accomplishes the same thing.
The reason is that we fabricate and procure a large number of materials in a Make-To-Order environment, with some planned scrap at multiple levels of sub-assembly. The result is that we often have small residual quantities of components & sub-assemblies in sales order stock when the project is complete. Some of these may be useful on future projects so we want them to remain in stock, but we donu2019t want them to continually generate exception messages that distract our planners from the exceptions that truly need attention.
I have tried setting up a storage location that is excluded from MRP, and this works only if the material is in General Stock, but not if it is in Sales Order Stock.
If anyone knows of a way to either set up an allowed tolerance, or exclude a sales order segment from MRP, please let me know.

DB49,
I have previously suggested just what you have indicated (ie. to move the parts back to unrestricted geneeral use stock). My company's objection is that the materials were either produced or procured for that original sales order and that the costs for these materials are in that sales order as well. Using a 411E transfer posting will not only move the stock, but also the cost (as if we are buying it back from the sales order). Since there is no guarantee that we will be able to sell it again, our accounting department will not allow us to do this.
So the bottom line is:
We do want to retain visibility to these stocks.
We don't want the cost for these stocks back on our books
If the opportunity presents itself, we want to move them to any future sales order for the same material.
We don't want the hundreds of exception messages for "excess stock in individual segment"
However we do want to see this message for actively planning sales orders that may have too much stock
There may be no way to get this, but that is the goal.

MRP Exception message for Excess production quantity

Originally, there is a demand for a common item material A 1500
One work order is opened for this grouped demand
Grouped Demand: 1500
Work Order QTy: 1500
Due to a drop in demand, the demand fall to 1200
At this time, will any MRP exception raise to suggest the order to reduce the scheduled quantity to 1200?
If there is way to do so, what should I set to achieve this requirement?

I just afraid additional demand would raise by setting this coverage.
I tried to define a range of coverage profile in the system with min:0 target:0 and max:1
I set a material to use this profile and run a MRP with my above case.
But still No exception message was suggested for the case.
Is there something I am missing out?
Anyway, thanks you for your suggest.

Working with MRP Exception Message

Hi Team,
In MD04, i am getting exception messages like below.
20 - Cancel the Process
15 - Postpone the process
10 - Bring Process Forward
I have already read the SDN postings and also the below link.
What is rescheduling and how does it work - ERP Manufacturing (PP) - SCN Wiki
But question is, Instead of MRP raises this exception message like "10 - Bring Process forward". This exception message proposes new start date for the planned order.
Q1: Instead of raises this as exception message, during MRP run, the planned order start date can be directly modified by the system know?
Q2: On daily basis, How to act on this MD04 exception messages? How the MRP Controller should act on this exception messages? Should the planner need to modify the planned order dates manually as proposed by the exception message?
Q3: Do w have any mass transaction to act on this exception message?
Thanks

But question is, Instead of MRP raises this exception message like "10 - Bring Process forward". This exception message proposes new start date for the planned order.
Exception message '10' is raised to 'firmed' receipts - not planned receipts. MRP cannot change the firmed receipts (exception - roll-forward periods), hence adjustment in case of this message is out of the question. Rest assured, the planning run does adjust the receipt as much as possible.
Q1: Instead of raises this as exception message, during MRP run, the planned order start date can be directly modified by the system know?
Have you seen exception message '10' to a planned order which is not fixed/firmed? System adjusts when possible.
Q2: On daily basis, How to act on this MD04 exception messages? How the MRP Controller should act on this exception messages? Should the planner need to modify the planned order dates manually as proposed by the exception message?
This may involve many manual decision from the planners and should not be automated. You can help out a planner through reports, but the decision should not be taken automatically.
If you find it interesting you can go through responses from Dogboy 49 and myself in the threads shared below:
Handling of MRP Exception Message
md04 exception
Q3: Do w have any mass transaction to act on this exception message?
No, you may think of developing something using BAPI_MATERIAL_STOCK_REQ_LIST or MD_STOCK_REQUIREMENTS_LIST_API function modules and providing hyperlinks to the users so that they can directly be inside the corresponding change transaction according to the MRP element.
However, 10, 20 and 15 all of these three exception messages come due to rescheduling for the firmed receipt elements. In MD07 you can get a collective overview of number of these messages in the exception group 07 (standard).
Best Regards.
Rajen

MRP Exception Messages - Best practices

Dear colleagues,
I am currently dealing with a large SAP installation where system is already live in 50+ countries and the number of manufacturing plants are in hundreds. MRP generates exception messages but the volume is significantly high. Planners have lost faith in these messages thus the client is not getting the full benefit of reacting to MRP exceptions.
Have any of you dealt with similar business situations? If yes, what best practices and what system design have you put in place to simplify the process of resolving exception messages.
Thanks,
PKV

Hello Pavan,
MD06 should be the planner's best friend as it helps him be on top of all the future expected shortfalls, talk to production schedulers or Vendors to bring material on time for production/deliver to customer.
Best way to handle exception messages in a plant is to divide it by MRP controllers, procurement types external or internal.
Planners have to analyse MD06 after every MRP run if possible. Atleast once a week go through their MD06.
However as per my experience most places the material master planning data is not as clean as the planners would like to have. But MD06 offers them an opportunity to update the material master as per their choice. ie planners can change planned delivery time, mrp lot size, mrp type etc..
You may have to find out why the planners have lost faith in MRP messages. System(MRP) can give you a good result only if master data is good.
Hope this helps.
Thanks,
Ram

MRP Exception messages difference

Hi PP Gurus
I need to understand the exact difference between few exception messages
MRP Exception message 6 - Start date of supply proposal is in past
MRP Exception message 7 - Finish date of supply proposal is in past
Query : Does it means that if start date is in past & finish date is in future , then only EM6 will appear .If both are in past , then EM7 will appear ???
MRP Exception message 10 - This is meant for Rescheduling IN i.e. if the supply proposal finish date is later than reqt date
MRP Exception message 15 - This is meant for Rescheduling OUT in i.e. if the supply proposal finish date is eariler than reqt date
MRP Exception message 30 - Plan process according to schedule i.e. pull or push the supply proposal as per reqd date
It looks to me that
EM30 is same as EM10 & EM15 since the former also suggests to pull or push as the latter two does .Then what is the exact difference between these
rgds
sandeep

1- I'm not sure, but could be.
2- Difference between 10, 15 and 30 is that 10 and 15 are for firmed elements (like production order or purchase order); 30 is for planned order (or other NOT FIRMED element) that cannot be properly planned because of LT problems.

Update MRP Exception Messages...in Oracle Database

Hi All,
I am working on MRP Exception Messages.
I am using the BAPI_MATERIAL_MRP_LIST for my MRP Messages.
For the above BAPI The Inputs are 1.Material Number 2. Plant.
I have the Plant and Material numbers (57,000 i inserted using BAPI_MATERIAL_GETLIST) Tables With Data in my Oracle Database.
I would like to update the MRP Messages Table in in my Oracle Database.
My logic is I took the plant numbers and put into the repeater and the same Material too. I am giving linking the both to BAPI inputs,material and Plant. Is it right what I am going?
Can you give some ideas how to do it.
Thanks
R M

I think this is a duplicate of your other MRP Exception Message. Please close this one since the other one is receiving all the responses.
Thanks,
Mike

MRP exception handling for planning strategy 52

Hi All,
How to handing MRP exception in Mass? For example, header material having two sub assembly and 3 raw materials in it's BOM. As per planning strategy 52, we maintain PIR for finished part, if we run MRP planning will be generated with respect to Planned Independent Requirement(PIR). Now, the problem is the higher/upper level material planing date is lower than low level material, It means Semi finished material(SF2) planning date is for example ( 15 june 2014) at the same time another lower level semi finished material (SF1) planning date is (18 june 2014). In this case without completing SF1, we can't produce SF2 because SF1 is an component of SF2. In the same way, system will propose the planning info for all raw material/semi finished. How we will handle this exception in mass since we using more materials in shop floor.Hence, it's really hard to planner to adjust the planing date for each and every material wise. How to handle/adjust this MRP exception? How to make system to calculate dependent materials availability to calculate next level material's planning date (start,end)? We understand that we have to maintain proper master information like in-house production days, planned delivery date, Gr processing date etc., to get planning information. Apart from that how we handle or to get without this kind of exceptional message? Please suggest
Thanks

AKS,
There is absolutely nothing wrong with having exception messages. Expecting to be able to perform some mass transaction that will magically make all messages "go away" is unreasonable. In any real life business, there will be new exception messages with every MRP run - sometimes thousands of them.
These messages indicate that there is something the matter with the plan; but they don't really tell you what is the best way to fix the plan. There may not be an easy way to fix this plan, it may actually require having your planners examine each PIR, trace down the BOM, and determine what is the best solution for that PIR. Once you have decided what is wrong with your plan, then ask me what mass changes are available to fix THAT problem.
Now, to your question. If you want all the dates to line up, then allow dates in the past. Although this solution doesn't give you results that are any more realistic than your current solution, you will eliminate most of the exception message 10's; and, if all your master data is correct, most of the supply and demand dates should line up. The messages will be replaced with a boatload of "new, and start date in the past" or similar. You can allow MRP to create procurement proposals with start dates in the past by changing the appropriate settings in OPPQ and/or OPPR. Also affected by scheduling parameters found in OPU5 and OPU3.
This is a business decision. Some planners prefer not to allow dates in the past. Others just the opposite. You (or the client, if you are a consultant) have to decide which is best for your company.
Best Regards,
DB49

Exception Description: Entity class [] has no primary key....

Received the following error in jdeveloper - some info on how to fix would be greatly appreciated
[EclipseLink/JPA Client] Adding Java options: -javaagent:C:\oracle\MiddlewareNew\jdeveloper\modules\oracle.toplink_11.1.1\eclipselink.jar
C:\Oracle\MiddlewareNew\jdk160_05\bin\javaw.exe -client -classpath C:\JDeveloper\mywork\APP_CM_AUTONUM_GEN\.adf;C:\JDeveloper\mywork\APP_CM_AUTONUM_GEN\SAM_CM_AUTONUM_GEN\classes;C:\oracle\MiddlewareNew\jdeveloper\modules\oracle.toplink_11.1.1\toplink.jar;C:\oracle\MiddlewareNew\jdeveloper\modules\oracle.toplink_11.1.1\antlr.jar;C:\oracle\MiddlewareNew\modules\com.bea.core.antlr.runtime_2.7.7.jar;C:\oracle\MiddlewareNew\modules\javax.persistence_1.0.0.0_1-0.jar;C:\oracle\MiddlewareNew\jdeveloper\modules\oracle.toplink_11.1.1\eclipselink.jar;C:\oracle\MiddlewareNew\jdeveloper\modules\oracle.xdk_11.1.1\xmlparserv2.jar;C:\oracle\MiddlewareNew\jdeveloper\modules\oracle.xdk_11.1.1\xml.jar;C:\oracle\MiddlewareNew\modules\javax.jsf_1.2.0.0.jar;C:\oracle\MiddlewareNew\modules\javax.ejb_3.0.1.jar;C:\oracle\MiddlewareNew\modules\javax.enterprise.deploy_1.2.jar;C:\oracle\MiddlewareNew\modules\javax.interceptor_1.0.jar;C:\oracle\MiddlewareNew\modules\javax.jms_1.1.1.jar;C:\oracle\MiddlewareNew\modules\javax.jsp_1.1.0.0_2-1.jar;C:\oracle\MiddlewareNew\modules\javax.jws_2.0.jar;C:\oracle\MiddlewareNew\modules\javax.activation_1.1.0.0_1-1.jar;C:\oracle\MiddlewareNew\modules\javax.mail_1.1.0.0_1-1.jar;C:\oracle\MiddlewareNew\modules\javax.xml.soap_1.3.1.0.jar;C:\oracle\MiddlewareNew\modules\javax.xml.rpc_1.2.1.jar;C:\oracle\MiddlewareNew\modules\javax.xml.ws_2.1.1.jar;C:\oracle\MiddlewareNew\modules\javax.management.j2ee_1.0.jar;C:\oracle\MiddlewareNew\modules\javax.resource_1.5.1.jar;C:\oracle\MiddlewareNew\modules\javax.servlet_1.0.0.0_2-5.jar;C:\oracle\MiddlewareNew\modules\javax.transaction_1.0.0.0_1-1.jar;C:\oracle\MiddlewareNew\modules\javax.xml.stream_1.1.1.0.jar;C:\oracle\MiddlewareNew\modules\javax.security.jacc_1.0.0.0_1-1.jar;C:\oracle\MiddlewareNew\modules\javax.xml.registry_1.0.0.0_1-0.jar;C:\oracle\MiddlewareNew\wlserver_10.3\server\lib\weblogic.jar -javaagent:C:\oracle\MiddlewareNew\jdeveloper\modules\oracle.toplink_11.1.1\eclipselink.jar SAM.CMAUTONUMGENClient
java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at sun.instrument.InstrumentationImpl.loadClassAndStartAgent(InstrumentationImpl.java:323)
     at sun.instrument.InstrumentationImpl.loadClassAndCallPremain(InstrumentationImpl.java:338)
Caused by: java.lang.reflect.InvocationTargetException
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:597)
     at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializerAgent.initializeFromAgent(JavaSECMPInitializerAgent.java:45)
     at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializerAgent.premain(JavaSECMPInitializerAgent.java:38)
     ... 6 more
Caused by: javax.persistence.PersistenceException: Exception [EclipseLink-28018] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Predeployment of PersistenceUnit [SAM_CM_AUTONUM_GEN] failed.
Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class oracle.SamCmAutonumGen] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:870)
     at org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.callPredeploy(JPAInitializer.java:101)
     at org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.initPersistenceUnits(JPAInitializer.java:149)
     at org.eclipse.persistence.internal.jpa.deployment.JPAInitializer.initialize(JPAInitializer.java:135)
     at org.eclipse.persistence.internal.jpa.deployment.JavaSECMPInitializer.initializeFromAgent(JavaSECMPInitializer.java:145)
     ... 12 more
Caused by: Exception [EclipseLink-28018] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.EntityManagerSetupException
Exception Description: Predeployment of PersistenceUnit [SAM_CM_AUTONUM_GEN] failed.
Internal Exception: Exception [EclipseLink-7161] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class oracle.SamCmAutonumGen] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
     at org.eclipse.persistence.exceptions.EntityManagerSetupException.predeployFailed(EntityManagerSetupException.java:210)
     ... 17 more
Caused by: Exception [EclipseLink-7161] (Eclipse Persistence Services - 1.0.2 (Build 20081024)): org.eclipse.persistence.exceptions.ValidationException
Exception Description: Entity class [class oracle.SamCmAutonumGen] has no primary key specified. It should define either an @Id, @EmbeddedId or an @IdClass. If you have defined PK using any of these annotations then please make sure that you do not have mixed access-type (both fields and properties annotated) in your entity class hierarchy.
     at org.eclipse.persistence.exceptions.ValidationException.noPrimaryKeyAnnotationsFound(ValidationException.java:1245)
     at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.validatePrimaryKey(EntityAccessor.java:1173)
     at org.eclipse.persistence.internal.jpa.metadata.accessors.classes.EntityAccessor.process(EntityAccessor.java:486)
     at org.eclipse.persistence.internal.jpa.metadata.MetadataProcessor.processORMMetadata(MetadataProcessor.java:443)
FATAL ERROR in native method: processing of -javaagent failed
     at org.eclipse.persistence.internal.jpa.deployment.PersistenceUnitProcessor.processORMetadata(PersistenceUnitProcessor.java:303)
     at org.eclipse.persistence.internal.jpa.EntityManagerSetupImpl.predeploy(EntityManagerSetupImpl.java:830)
     ... 16 more
Exception in thread "main" Process exited with exit code 1.

Hi,
you may want to try the J2EE forum here on OTN in case you don't get a sufficient answer to the problem.
Frank

Exception Description: Unable to process XML tag [driver-class] with value

Hi
I'm newbie with TopLink. I try to write a litle application with TopLink:
- First, I create a session.xml file:
<?xml version="1.0" encoding="UTF-8"?>
<toplink-sessions version="11g Technology Preview 3 (11.1.1.0.0)" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<session xsi:type="database-session">
<name>dbsession</name>
<event-listener-classes/>
<logging xsi:type="toplink-log"/>
<primary-project xsi:type="xml">META-INF/tlMap.xml</primary-project>
<login xsi:type="database-login">
<platform-class>oracle.toplink.platform.database.oracle.Oracle10Platform</platform-class>
<user-name>dev</user-name>
<password>F6A3DA7BA187330D4E11A713C42FF833</password>
<sequencing>
<default-sequence xsi:type="table-sequence">
<name>Default</name>
</default-sequence>
</sequencing>
<driver-class>oracle.jdbc.OracleDriver</driver-class>
<connection-url>jdbc:oracle:thin:@//10.10.10.31:1521/devdb1</connection-url>
<bind-all-parameters>false</bind-all-parameters>
<struct-converters/>
</login>
</session>
</toplink-sessions>
- Second, I create a Java Application ( Application1.java):
package project2;
import java.sql.ResultSet;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.util.Vector;
import oracle.toplink.queryframework.DataModifyQuery;
import oracle.toplink.queryframework.SQLCall;
import oracle.toplink.queryframework.StoredProcedureCall;
import oracle.toplink.sessions.DatabaseSession;
import oracle.toplink.sessions.Session;
import oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader;
import oracle.toplink.tools.sessionmanagement.SessionManager;
import oracle.toplink.util.SessionFactory;
public class Application1 {
public Application1() {
public static void main(String[] args) {
// new Application1();
String statement = "SELECT motdepasse,login FROM bou_courtier";
SessionManager sessionmanager = SessionManager.getManager();
System.out.println("test");
// SessionFactory sessionfactory = new SessionFactory("META-INF/sessions.xml","dbsession");
DatabaseSession session = (DatabaseSession)sessionmanager.getSession(new XMLSessionConfigLoader(),"dbsession",Thread.currentThread().getContextClassLoader());
// Session session = sessionfactory.acquireSession();
System.out.println("test");
SQLCall sqlcall = new SQLCall(statement);
session.executeNonSelectingCall(sqlcall);
ResultSet rs = sqlcall.getResult();
try {
while(rs.next()){
String strPass = rs.getString(1);
String strLogin = rs.getString(2);
System.out.println("Password :"+strPass+"---"+"Login :"+strLogin);
} catch (SQLException e) {
// TODO
- Third, I build and run Application1.java in Jdevelopper 11g preview 3. Sadly, the result is a error:
Exception in thread "main" Local Exception Stack:
Exception [TOPLINK-9003] (Oracle TopLink - 11g Technology Preview 3 (11.1.1.0.0) (Build 071207)): oracle.toplink.exceptions.SessionLoaderException
Exception Description: Unable to process XML tag [driver-class] with value [oracle.jdbc.OracleDriver].
Internal Exception: java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
     at oracle.toplink.exceptions.SessionLoaderException.failedToLoadTag(SessionLoaderException.java:83)
     at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildDatabaseLoginConfig(TopLinkSessionsFactory.java:408)
     at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildLogin(TopLinkSessionsFactory.java:336)
     at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildDatabaseSessionConfig(TopLinkSessionsFactory.java:182)
     at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildSession(TopLinkSessionsFactory.java:168)
     at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildTopLinkSessions(TopLinkSessionsFactory.java:117)
     at oracle.toplink.tools.sessionconfiguration.XMLSessionConfigLoader.load(XMLSessionConfigLoader.java:239)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:448)
     at oracle.toplink.tools.sessionmanagement.SessionManager.getSession(SessionManager.java:311)
     at project2.Application1.main(Application1.java:33)
Caused by: java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver
     at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
     at java.security.AccessController.doPrivileged(Native Method)
     at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
     at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
     at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
     at oracle.toplink.tools.sessionconfiguration.TopLinkSessionsFactory.buildDatabaseLoginConfig(TopLinkSessionsFactory.java:405)
     ... 8 more
Process exited with exit code 1.
Can you help me to debug this error. Many thanks
user615555

The internal error: "java.lang.ClassNotFoundException: oracle.jdbc.OracleDriver"
is stating it can't find your driver jar file on the classpath. You'll need to check that you've included your Database driver in the list of libraries on your classpath.
Best Regards,
Chris

Regrouping of MRP exception messages

Hi Gurus,
Can anybody please help me with this issue. The business has requested to regroup the exception messages arising in MD04/MD06. Currently there are 8 selection groups into which all the MRP exception messages are put in. The business wants to move some messages in to different selection groups. Can anybody please let me know what are the implications of doing this? The reason the business has asked for this is that they feel that there are so many unused selection groups and they want to organize the messages as per the title/name. for example Reschedule in (message no 10) and reschedule out (message no 15), they want to separate these into two groups. Once group called expedite which will contain message 10 and anothet group called deexpedite which will contain message 15. sinmilarly for other messages. Please throw some light on this. Help is greatly appreciated.
Thanks
Anusha

Dear,
There is no the implications of doing this but note that most of exception message functionallity is hard-coded in MRP.
OMD3 and OM0L are the places you can make the possible changes.
Or you need to go for develpment with MD_STOCK_REQUIREMENTS_LIST_API
Use the BAPI_MATERIAL_MRP_LIST where AUSSL Exception message key. You will get all details
Regards,
R.Brahmankar

MRP exception message

Hi,
How to interpret the MRP exception messages in MD06?
1.what is the meaning of Stock days supply field showing 999,9- (meaning of 999,9-)
2.what is the meaning of 1st receipt day supply & 2nd RDS
3.Exception message group 3 showing the value 19 (In message group 3 there is no 19)
Can you please elaborate the each one in detail?
Thanks and Regards,
Vairavan

Hi,
The main difference would be what you consider as available for the calculation. You can configure in OMIL.
Regards,
Vivek
Pasting SAP help, which explains it quite clearly:
The receipt days' supply indicates how many days a material will last. The system takes current plant stock and specific, predefined receipts into account when calculating the receipt days' supply.
You can define two receipt days' supplies.This enables you to instruct the system to take the less binding receipt elements into account for the first receipt days' supply, and to take only the binding receipt elements (such as production orders and shipping notifications) into account for the second days' supply.
Additionally, in Customizing for MRP, you can use the safety stock indicator to define whether the number of days refers to the safety stock or the actual physical stock.
If the number of days is based on the safety stock, which is set in the standard settings, the system calculates the number of days until the stock level falls below the safety stock level. If the number of days is based on the physical stock level, the system calculates the number of days until the stock level falls below 0.
Material with critical ranges of coverage are indicated by red traffic lights in the MRP list and the stock/requirements list. You can define how many days are considered to be critical.

MRP Exception Description

Similar Messages

Maybe you are looking for