Delete an entity

Hello all,
How can I delete an entity from Oracle Data Quality?
Thanks,
Andrea

Hi All,
Even i have the same issue mentioned above.
I need to delete an entity.
I tried by right clicking on the particular entity which i want to delete;
but i didnt see any option for deleting (in that MENU.)
Please advice how to proceed further.
Thanks,
AMR

Similar Messages

Not able to delete any Entity Dimension members

Hi All,
I am trying to delete some Entity Dimension members but its not allowing me to delete. This problem is only for Entity Dimension.
I can edit Entity member name or properties successfully but not able to delete or move the position.
I also tried to check member usage but its not giving me any results, a blank screen comes and planning goes down after some time. Same happens when I try to delete any Entity member.
I have admin rights on Planning and I can delete other dimension member but not for Entity. There is no workflow started for Entity but If it is than also it pop-ups that after member deletion all planning unit will be lost. I have bounced planning DB and also restarted all Hyperion services but still no luck.
Please let me know if anyone has faced this issue or have any solution to resolve.
Regards
Vishal

Hi John,
After uncheck of "enabled for process management" for all Scenario along with Version dimension members , this issue is now resolved. But its a temporary resolution as client has not yet started any workflow so we can uncheck that options ,but when they need to start workflow process then we have to check this options again which will start this issue again.
Do you have any permamant resolution for this issue?
Thanks for your help.
Regards
Vishal

XCode 4.02 data model editor -- How do I delete an entity?

How does one delete an entity from the data model editor in XCode 4.02?
I have searched for the past hour for a little "minus" button hidding somewhere on the screen.

Switch Editor Style to 'Graph' from 'Table' (lower right of the editor window).
Select the entity you want gone...tap once so it shows focus.
Hit the 'Delete' key on your keyboard. 'Undo' if you want it back.

Hibernate: how to null out foreign key references when deleting an entity?

We use Spring/Hibernate3 in our app, and ran into kind of a bummer of a problem. We have a relationship that is many-to-one (e.g. Student -> School). This is represented by a schoolId on the Student table. When we delete the school through the Hibernate layer, we are immediately receiving foreign key constraints because Hibernate does not null out the Students' schoolId columns where applicable.
What we'd like to see happen is something like this:
1. SchoolDAO.delete(id)
Hibernate: UPDATE Student set schoolId = NULL where schoolId = ?
Hibernate: DELETE from School where id = ?
But what we're actually seeing is:
1. SchoolDAO.delete(id)
Hibernate: DELETE from School where id = ?
And hence the foreign key constraints.
Was wondering if someone else here has run into this. Someone on the Hibernate forums suggested using an Interceptor, but the Hibernate3 interceptors don't give us access to the Session to allow us to do a bulk update to null out these references. Apparently the interceptor javadoc says that the interceptor is basically there to change properties on the object in question and should not involve the session at all.
We then looked at implementing an Event, and that worked, but was not called for every cascade deleted event. We have a lot of cascade activity in our database, so that was a little disappointing.
We had briefly considered manually nulling out that FK in the DAO itself, but that would not work with the large amount of Hibernate driven cascade deletion that goes on in our app (Hibernate does not call our DAO every time it cascade deletes an entity).
Would greatly appreciate any pointers on this subject. We're hoping that others have run into this as well.
thanks.

I'm not sure why you'd expect that given that there's
not really an equivalent object oriented operation -
if you want to relinquish the object in the OO scheme
of things you have to null all the references to it;
you can't just say "make everything that points to
this object null".I can field that question. We came from EJB 2.x where in the event that you deleted a School entity bean using ejbRemove() you would see the following queries generated:
UPDATE Student set schoolId = NULL where schoolId = ?
DELETE from School where id = ?
Basically, it would manage the relationship for you. I know it's a completely different system but we were a little surprised to learn that Hibernate did not do this on its own as well.

Deleting CAF-Entity-Tables

Hello!
In a former I already asked how to delete the database tables that are generated by CAF for entity-services.
There are got some answers for maxDB. The problem is, we use Oracle. It version is 10.1.0.4.0, I think, I can see it in db13-transaction in SAP-logon, or is that database a totally different?
Can anyone suggest a oracle-client and give a short hint how to use it?
Thank you in advance for your help.
Jörg

Hi Jorg,
You can download the client from Oracle.
http://www.oracle.com/technology/tech/oci/instantclient/index.html
Best Regards,
Austin.

Problem when trying to delete CMP entity bean

Hi,
When I try to remove a CMP entity bean, I have this error :
re09.projet_ejb.syndic.AdminException: Exception thrown from bean; nested exception is: javax.ejb.EJBException: nested exception is: com.sun.jdo.api.persistence.support.JDOUnsupportedOptionException: JDO76207: Update of a primary key field is not allowed.It's only happening when I try to remove a bean which has a relation with another bean. The relation type is One to Many. I tried to search on this forum to find an answer but I found nothing that could help me.
Message was edited by:
Starship
Sry I just found the mistake, the cascade delete was not on the right place :s
Message was edited by:
Starship

Got it sorted so I thought I would share the solution here: The problem wasnt related to LR 5.2 but was to do with Mac OS X 10.8.5 AKA Mountain Lion. I had also noticed that I was having an issue around deleting anything on my MAC. When I tried to delete a file from anywhere I was asked to submit my password. The message I got was finder wants to make a change please submit password. I checked through the mountain Lion forums and found a solution here; https://discussions.apple.com/message/20499360#20499360%2320499360
I implemented it and the problem has dissappeared.

Deleting parent entity of oneToMany does not delete children first,

I have two entities related with a bi-rdirectional OneToMany relationship. When I delete the parent, I want eclipseLink to automatically delete the child entities first before deleting the parent entity. I have implemented what I understand all the documents are telling me I should implement, but I can not get it working.
When I try and delete the parent I get an SQLException as the foreign key constraint has been violated as there are child records for the parent I am trying to delete. It was my understanding, that if you have all the annotations correct on my Entities, then all i have to do is delete the parent and eclipseLink will delete the children first and therefore i should never get the SQL exception.
Here is some snippets of my code.
Entities
@Entity(name = "PARENTS")
public class ParentEntity {
     @Id
     @Column(name = "PARENT_ID", nullable = false)
     private String parentID;
     @Column(name = "DISPLAY_NAME", nullable = false)
     private String displayName;
     @OneToMany(mappedBy="parent", orphanRemoval=true, cascade=CascadeType.ALL)
     private Collection<ChildEntity> childEntities;
@Entity(name = "CHILDREN")
@IdClass(ChildIdentifier.class)
public class ChildEntity {
     @Id
     @Column(name="ITEM_ID", nullable=false)
     private String itemID;
     @Id
     @ManyToOne()
     @JoinColumn(name="PARENT_ID", nullable=false)
     private ParentEntity parent;
public class ChildIdentifier implements Serializable {
     private String itemID;
private String parent;
Tables created from these entities
PARENTS
Name Null? Type
PARENT_ID NOT NULL VARCHAR2(36)
DISPLAY_NAME NOT NULL VARCHAR2(255)
PrimaryKey = PARENT_ID
CHILDREN
Name Null? Type
ITEM_ID NOT NULL VARCHAR2(36)
PARENT_ID NOT NULL VARCHAR2(255)
PrimaryKey = ITEM_ID,PARENT_ID
ForeignKey = PARENTID = PARENTS.PARENT_ID
Code to delete a parent
     public void deleteParent(String id)
          ParentEntity e= em.find(ParentEntity .class, id);
          if (e!= null)
               em.remove(e);
Exception seen
javax.persistence.RollbackException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.4.0.v20120119-r10715): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLIntegrityConstraintViolationException: ORA-02292: integrity constraint (MYSCHEMA.CHILDREN_FK_P_PARENTS) violated - child record found
Error Code: 2292
Call: DELETE FROM PARENTS WHERE (PARENT_ID = ?)
I have added eclipse logging entries in my persistence.xml to try and see what is going on
<property name="eclipselink.logging.level" value="FINE"/>
<property name="eclipselink.logging.parameters" value="true"/>
And in my jdev console when running my test, i do not see any queries of CHILDREN before it tries to delete from PARENTS.
Am I missing something really obvious?
Thanks in advance.
Edited by: smaslin on Feb 20, 2012 9:20 AM
Edited by: smaslin on Feb 21, 2012 5:26 AM

"optional=false" only affects DDL generation, not runtime JPA behavior. PrivateOwned is similar to orphanRemoval in that it should cause the removal of child entities when they are dereferenced from the parent (ie remove them from the parent's collection). Cascade remove or cascade all should be all you need, but PrivateOwned+orphanRemoval should still cause the collection to be removed, as long as there are entities within the Parent's list of children to remove.
The only case where I can see this not occuring is if you have not been maintaining the bidirectional relationship. That is, if you have added Child entities and set a parent, but not updated the Parent's collection of children to reflect that change. A simple test is to refresh the parent before removal - call em.refresh(e); right before the em.remove(e);. If this works, then you will need to change your application so that when you add parents to a child you also add the child to the parent's list of children - JPA does not maintain relationships for you and not doing so will keep the cache inconsistent with what is in the database.
Best Regards,
Chris

JPA OneToMany bidirectional -- Entity deletion

I am having trouble deleting an entity part of a part-whole hierarchy and mapped as a OneToMany bidirectional relationship. For example:
public class A {
    @OneToMany(mappedBy="parent", cascade={CascadeType.MERGE, CascadeType.PERSIST})
    private Collection<A> children;
    @ManyToOne(cascade={CascadeType.MERGE, CascadeType.PERSIST})
    @JoinColumn(name="PARENT_ID")
    private A parent;
}Instances of 'A' can, but do not HAVE to participate in this relationship. Therefore, a cascade on remove is not appropriate, because for any given instance of 'A', a parent and/or any of the children can exist independent of that instance.
So basically I want to remove an instance of 'A', and at the same time have it's child relationships updated -- basically pointing to a null parent.
What's the proper way to do this?
The first and most obvious way to me is:
    entityManager.remove(instanceOfA);But that results in the cryptic error: "deleted entity passed to persist".
The only way I've gotten this to work so far is to use two transactions. In the first, I simply break the relationships and merge the objects:
    Collection<A> children = instanceOfA.getChildren();
    instanceOfA.setChildren(null);
    for(A child : children) {
        child.setParent(null);
        entityManager.merge(child);
    entityManager.merge(instanceOfA);And in the second transaction:
    instanceOfA = entityManager.find(A.class, instanceOfA.getId());
    entityManager.remove(instanceOfA);This works, but feels very clunky.
What is the proper way to do this?
Thanks,
Justin

I am having trouble deleting an entity part of a part-whole hierarchy and mapped as a OneToMany bidirectional relationship. For example:
public class A {
    @OneToMany(mappedBy="parent", cascade={CascadeType.MERGE, CascadeType.PERSIST})
    private Collection<A> children;
    @ManyToOne(cascade={CascadeType.MERGE, CascadeType.PERSIST})
    @JoinColumn(name="PARENT_ID")
    private A parent;
}Instances of 'A' can, but do not HAVE to participate in this relationship. Therefore, a cascade on remove is not appropriate, because for any given instance of 'A', a parent and/or any of the children can exist independent of that instance.
So basically I want to remove an instance of 'A', and at the same time have it's child relationships updated -- basically pointing to a null parent.
What's the proper way to do this?
The first and most obvious way to me is:
    entityManager.remove(instanceOfA);But that results in the cryptic error: "deleted entity passed to persist".
The only way I've gotten this to work so far is to use two transactions. In the first, I simply break the relationships and merge the objects:
    Collection<A> children = instanceOfA.getChildren();
    instanceOfA.setChildren(null);
    for(A child : children) {
        child.setParent(null);
        entityManager.merge(child);
    entityManager.merge(instanceOfA);And in the second transaction:
    instanceOfA = entityManager.find(A.class, instanceOfA.getId());
    entityManager.remove(instanceOfA);This works, but feels very clunky.
What is the proper way to do this?
Thanks,
Justin

LIGHTSWITCH HTML ENTITY SOFT DELETION

Hello all,
I am working on LightSwitch HTML client application. I have an issue regarding entity soft deletion.
For your kind information, I have also referred Beth Messi's link:
http://blogs.msdn.com/b/bethmassi/archive/2011/11/18/using-the-save-and-query-pipeline-to-archive-deleted-records.aspx
My Scenario:
I have an Accounts table which is related to other tables.
In Accounts edit screen, I have a delete button. On deleting account from edit screen Account should be marked as deleted in database(i.e. soft delete) if it has no reference in any other table, otherwise show client side an error message
myapp.EditAccount.DeleteAccount_Tap_execute = function (screen) {
// Write code here.
screen.Account.deleteEntity();
myapp.applyChanges().then(function success() {
// Delete successful message.
}, function error(e) {
// Delete failure message.
According to Beth Messi's example: On deletion, the entity will discard changes and mark the entity as soft deleted.
So, If data is discarded then I do not get the server side exception " Could not delete. entity is in use." and my code inside function error() could not execute.
Any different way to accomplish this is also appreciated.
Thanks,
Ravi Patel

HI Ravi,
As Beth’s blog said, it marks records for deletion without actually deleting them from the database. It discards the changes, this reverts the deletion.
As I know, myapp.applyChanges(), calling apply will save all the changes of the current changeset. If only one changeset exists, it will save them to the database. If the current changeset is a nested scope, it will commit the changes to
the parent changeset. I don’t think you can use myapp.applyChanges()
method in this scenario.
Best regards,
Angie
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Deleting Entity Services

Hi All:
I deleted an entity service call Status_Obj, but after Generate all Project Code, appears the following error:
Error Status_ObjServiceLocal cannot be resolved (or is not a valid return type) for the method create Status_ObjServiceLocalHome.java NWD_agiletrk_Dpmg_env_orgejbmodule~agile.com/ejbModule/com/agile/pmg_env_org/besrv/status_obj
Someone have an idea about how can resolve this.

Hi,
It seems that the you are returning same structure in one of your operations that you have used to create the Entity Service. Now that service is deleted .. its structure might as well not be there .. and thats why the project gives build error.
Hope this helps,
Ashutosh

Entity beans - cascade delete doesn't work

Hi,
Could anyone show me a working example where cascade delete implemented with EJB3 entity beans?
If the database not created with cascade delete I can't do it..
I use JDeveloper 10.1.3.0 and it's embedded OC4J and Oracle 8i database.
My session bean doesn't catch any exception during remove an entity that has child entity. The exception will be thrown only at the end of the transaction, when the container calls the concrete SQL. And my client receives SQL exception: child record found.
Why can I define: cascade={CascadeType.REMOVE} if the container doesn't check it and doesn't throw exception when I want to delete an entity that has childs?
Thanks
Kati

Kati,
The EJB3 support in 10.13.0 JDeveloper is a preview implementation released prior to the completion of the EJB3 specification. I do not believe the cascade functionality was complete for that preview. I would recommend either switching to the 10.1.3.1 preview or downloading and using TopLink Essentials, which is the compliant implementation of EJB3 Java Persistence API (JPA).
http://otn.oracle.com/jpa
Doug

Need help getting around the following error: JBO-27101: Attempt to access dead entity in EO.

Hi everyone,
My logic in prepareForDML() updates some attributes (shown in the snippet below) based on whether an insert or update is taking place. But, when I delete a line, I get the following error: JBO-27101: Attempt to access dead entity in EO. So far, I have not been able to catch this error.
        if (operation == DML_INSERT) {
            setLineId((new SequenceImpl("eo_s",
                                        getDBTransaction()).getSequenceNumber()));
            setCreatedBy(createdBy);
            setCreationDate(currentDateAndTime);
            setLastUpdatedBy(lastUpdatedBy);
            setLastUpdateDate(currentDateAndTime);
        } else if (operation == DML_UPDATE) {
            setLastUpdatedBy(lastUpdatedBy);
            setLastUpdateDate(currentDateAndTime);
Any advice would be appreciated. Thanks!
James

Hi Timo,
Thanks for responding. Whenever I delete a line and commit, I get the error. And, since inserts and updates are all that I am interested in, I did not think that I needed deletion logic. The VO contains several EOs, but all are reference EOs that cannot be updated except for the main EO.
Here is the entire prepareForDML() method:
    protected void prepareForDML(int operation, TransactionEvent e) {
        // BEGIN Initial Version
        // Using prepareForDML is a best practice (versus doDML).
        ApplicationModule am;
        boolean lineIsValid;
        byte entityState;
        byte postState;
        Date currentDateAndTime;
        Date weekEndingDate;
        Number createdBy;
        Number lastUpdatedBy;
        String amConfiguration;
        String amDefinition;
        String entityStateText;
        String operationText;
        String postStateText;
        ServicesAMImpl servicesAMImpl;
        Timestamp timeStamp;
        // amDefinition = "com.model.services.ServicesAM";
        // amConfiguration = "ServicesAMLocal";
        // am = Configuration.createRootApplicationModule(amDefinition, amConfiguration);
        createdBy = new Number(-1); // TODO fnd_profile.value('USERNAME')
        entityState = getEntityState();
        entityStateText = null;
        operationText = null;
        postState = getPostState();
        postStateText = null;
        lastUpdatedBy =
                new Number(-1); // TODO fnd_profile.value('USERNAME'); is there a last login id?
        // servicesAMImpl = (ServicesAMImpl)am;
        // lineIsValid = servicesAMImpl.callValidateLineProcedure(getBillable());
        timeStamp = new Timestamp(System.currentTimeMillis());
        currentDateAndTime = new Date(timeStamp);
        // TODO Should weekEndingDate be in the callValidateLineProcedure()?
        weekEndingDate =
                commonCode.nextDay(getActivityDate(), Calendar.THURSDAY);
        setWeekEndingDate(weekEndingDate);
        // TODO See https://community.oracle.com/message/9542286?tstart=14.
        // if (entityState != Entity.STATUS_DELETED & entityState != Entity.STATUS_DEAD)...
        System.err.println("prepareForDML - getLineId: " + getLineId());
        switch (operation) {
        case DML_DELETE:
            operationText = "Delete";
            break;
        case DML_INSERT:
            operationText = "Insert";
            break;
        case DML_UPDATE:
            operationText = "Update";
            break;
        System.err.println("prepareForDML - operationText: " +
                           operationText); // TODO
        // System.out.println("prepareForDML - operationText: " + operationText); // TODO
        switch (entityState) {
        case Entity.STATUS_INITIALIZED:
            entityStateText = "Initialized";
            break;
            // Don't do anything.
        case Entity.STATUS_UNMODIFIED:
            entityStateText = "Un-Modified";
            break;
            // Don't do anything.
        case Entity.STATUS_DEAD:
            entityStateText = "Dead";
            break;
            // Don't do anything.
        case Entity.STATUS_DELETED:
            entityStateText = "Deleted";
            break;
            // entity.revert();
            // entity.refresh(Entity.REFRESH_CONTAINEES);
        case Entity.STATUS_MODIFIED:
            entityStateText = "Modified";
            break;
            // entity.refresh(Entity.REFRESH_UNDO_CHANGES);
        case Entity.STATUS_NEW:
            entityStateText = "New";
            break;
            // entity.refresh(Entity.REFRESH_FORGET_NEW_ROWS);
            // entity.refresh(Entity.REFRESH_REMOVE_NEW_ROWS);
        default:
            entityStateText = String.valueOf(entityState);
        System.err.println("prepareForDML - entityStateText: " +
                           entityStateText);
        switch (postState) {
        case Entity.STATUS_INITIALIZED:
            postStateText = "Initialized";
            break;
            // Don't do anything.
        case Entity.STATUS_UNMODIFIED:
            postStateText = "Un-Modified";
            break;
            // Don't do anything.
        case Entity.STATUS_DEAD:
            postStateText = "Dead";
            break;
            // Don't do anything.
        case Entity.STATUS_DELETED:
            postStateText = "Deleted";
            break;
            // entity.revert();
            // entity.refresh(Entity.REFRESH_CONTAINEES);
        case Entity.STATUS_MODIFIED:
            postStateText = "Modified";
            break;
            // entity.refresh(Entity.REFRESH_UNDO_CHANGES);
        case Entity.STATUS_NEW:
            postStateText = "New";
            break;
            // entity.refresh(Entity.REFRESH_FORGET_NEW_ROWS);
            // entity.refresh(Entity.REFRESH_REMOVE_NEW_ROWS);
        default:
            postStateText = String.valueOf(postState);
        System.err.println("prepareForDML - postStateText: " + postStateText);
        // DeadEntityAccessException
        if (operation == DML_INSERT) {
            setLineId((new SequenceImpl("eo_s",
                                        getDBTransaction()).getSequenceNumber()));
            setCreatedBy(createdBy);
            setCreationDate(currentDateAndTime);
            setLastUpdatedBy(lastUpdatedBy);
            setLastUpdateDate(currentDateAndTime);
        } else if (operation == DML_UPDATE) {
            setLastUpdatedBy(lastUpdatedBy);
            setLastUpdateDate(currentDateAndTime);
        // Configuration.releaseRootApplicationModule(am, true);
        // END Initial Version
        super.prepareForDML(operation, e);
Here is the entire doDML() method:
    protected void doDML(int operation, TransactionEvent e) {
        // BEGIN Initial Version
        // This logic is for troubleshooting only.
        String operationText;
        operationText = null;
        switch (operation) {
        case DML_DELETE:
            operationText = "Delete";
            break;
        case DML_INSERT:
            operationText = "Insert";
            break;
        case DML_UPDATE:
            operationText = "Update";
            break;
        System.err.println("doDML - operationText: " + operationText); // TODO
        // System.out.println("doDML - operationText: " + operationText); // TODO
        // END Initial Version
        super.doDML(operation, e);
James

Deleting CMR OC4J 9.04.0 - 9.0.4.1 - 10.1.2.0 - 10.1.3.0 - 10.1.3.1

I've a simple code that work correctly on Oracle iAS 10g Release 1
but not on Release 2 or Release 3.
We have already received a patch from Oracle for the Release 2
Today we are requesting a patch for the Release 3 as the bug remains on the NEW Release.
Unfortunately, Oracle Support didn't want to identify our problem as a bug of their J2EE container because this behaviour is considered as normal.
So I need our help to find the J2EE 1.3 (we use only EJB 2.0) documentation speaking about deletion of Entity behind a CMR.

Below I will explain the bug we have found at the beginning :
We noticed changes between iAS 9.0.4.0.0 and 9.0.4.1.0 in CMP-CMR behavior.
When we remove an element from a CMR collection (child part of a relationship) the 9
.0.4.1.0 version of OC4J generate an exception. Perhaps the OC4J attempt to upda
te the chield property which reference the parent key to NULL. So we have an OR
A-01407 SQL Exception because this field is mandatory. This problem did not app
ears with the first release of OC4J 10g.
A simple testcase to test this problem
two tables :
create table a
id number(11,0) NOT NULL,
lib varchar2(500) NOT NULL
ALTER TABLE A ADD ( CONSTRAINT A_PK PRIMARY KEY (ID)
create table b
id number(11,0) NOT NULL,
idJoinA number(11,0) NOT NULL,
lib varchar2(500) NOT NULL
ALTER TABLE B ADD ( CONSTRAINT B_PK PRIMARY KEY (ID)
ALTER TABLE B ADD ( CONSTRAINT BJOINA FOREIGN KEY (idJoinA) REFERENCES A (ID);
We create two entity : one for table a and one for table b with one cmr 1 - N
When we execute this part of code :
ALocal entityA = getALocalHome().findByPrimaryKey(45);
for(Iterator iter = entityA.getCollectionB.iterator();iter.hasNext();)
BLocal entityB = (BLocal)iter.next();
entityB.remove();
we catch :
javax.ejb.EJBException: Error saving state: ORA-01407: cannot update ("A"."IDJOINA") to NULL

Data deletion on primary index and secondary index

Hello, I have a question regarding data deletion in BDB-JE.
Suppose I have an Entity class which has a primary index and a secondary index, the secondary key does not have outer related entity. So when I want to delete this entity, is it correct we only need to remove the entity from primary index? or I also need to do it for secondary index or just remove it from secondary index and internally BDB_JE will remove it from primary index?
Thanks
Anfernee

You can delete an Entity using the delete method for primary index or the secondary index. When an entity is deleted, secondary index records are automatically deleted. The primary and secondary indices are always kept in sync.
--mark

MRP requirements (material = "no dispo", storage location deleted)

Good morning,
I have two different problems and hopefully, you can help me.
- I see stock information in MMBE for a storage location I deleted
- MD04 shows requirements for this storage location after it was deleted and the material was set to "no dispo"
How can this be?
I remember a report from SAP, which clear all wrong requirements for a material, but I did not find it. Anyone remeber the report??
Thanks
Nicole

If by saying "I deleted the S/L" you mean that you deleted that entity in customization, this is a NONO practice. By deleting it from customization you are not deleting all the database references that exist in many objects (tables) as well, and this leads to inconsistencies that in some cases are not manageable.
I suggest that you you recreate the S/L, name it something like "DELETED-DO NOT USE", and gradually make sure that all references (like in your example stock, requirements, etc.) are gone.

Delete an entity

Similar Messages

Maybe you are looking for