Skip to Content
author's profile photo Former Member
Former Member

How to delete the BP

Hi experts,

I am new to Basis. I want to delete the duplicate BP's in my system in solution manager i have searched the related post in same forum the links are http://scn.sap.com/thread/309504

In one discussion the guy mentioned this in comment which works perfectly for that problem

"The error points that the BP you are trying to delete is already used in an order ,etc that is still valid.

If you aren't sure where the BP is used, follow these steps :

Put breakpoints in CRM_BUPA_ORDER_EVENT_ARCH1 and CRM_BUPA_READ_ORDER_OBJECTS and debug till you see the error CRM_BUPA 205. These modules determine the dependencies of the BP when you try to delete it.This will help you see which dependency is preventing the deletion and then maybe you can manually delete / invalidate the dependency and then try to delete the BP again."


But i didn't get what exactly he is trying to suggest...

I have tried BUPA_DEL tcode but it says the message that "Deletion is not allowed BP still used in business transactions...." Then i tried tcode BUPA_PRE_DA to set the deletion flag then i got the following error

"BP still used in business transactions...."

"No partners found for stated selection"


Guys please help me out on this issue whether with above solution that i am not getting or with some other solution...

Early reply should be appreciated.

Thanks and Regards

Prasad Deshpande


Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jan 05, 2014 at 07:11 AM

    I found that Archiving is also an option for this can anyone guide me how to archive the BP's using the transaction SARA... Is we need to follow some prerequisite for this....

    Add a comment
    10|10000 characters needed characters exceeded

    • Hi Prasad,

      How to use the SARA transaction for delete the archival data... this are step to used

      Introduction

      Usage of SAP for our Day to Day Business Activities Results in Huge Amount of Enterprise Data.

      It consequences are Data Overflow, Transactions running for long time and Performance Degradation. By

      using Data Archiving Methodology we can clean up the Out of date data or any unused data and store it

      offline. This leads to Performance improvement, Maximized System availability, Reduction of costs.

      SAP provides us a solution for this Data Archiving process using which we can archive the data in a secure

      and consistent manner. Archiving program uses certain checks and follows certain rules which ensure

      consistency of data. By using this method we can archive master data such as Material Master, Batch

      Master Records, HR master data and transactional data such as Sales Documents, Financial Documents,

      Purchase orders etc.

      Archiving process comprises of two mandatory steps

      · Archive File Creation

      · Deletion of files from the Database

      These steps are discussed in detail for Batch Records and Consignment Materials

      Archiving Configuration Setup

      The first step of Configuration of Archiving Object starts from transaction AOBJ. Batches and Consignment

      materials are archived via the object MM_SPTOCK

      You can also see the list of tables from which data is going to be archived. The Transaction DB15 can be

      used for this purpose

      The Write and Delete Programs which are involved in this Object

      Note: For Performing theWrite Step You should have required authorizations for executing SARA Transaction

      How to Choose Data which is Eligible for Archiving

      Generally in any SAP System Transaction Data forms the major part and it occupies huge space. Master

      Data is changed rarely and it occupies lesser space compared to transactional data.

      Data Archiving is used for both transactional and master data

      In this case the data is Batch Master Records. Whenever your customer no longer needs the data you can

      archive and delete that. For this to happen you have to flag that particular batch master which customer no

      longer needs so that the archiving and deletion program will delete it.

      When a batch master record is created, the deletion flag is hidden if the material master record is not flagged

      for deletion at plant level or storage location level. If the material master record is flagged for deletion, the

      system issues a warning on the initial screen. The Deletion flag field is then displayed, but the deletion flag

      cannot be set. You can set the deletion flag at plant level for a Batch master Record using Transaction

      MSC2N.

      Archiving File Creation- Write Step

      Open the Transaction SARA and Specify MM_SPSTOCK as the Archiving Object

      Click on the Write Button.

      Give the Variant name and Select Maintain Button

      We can Run the Write Program of Archiving Object in Either Test Mode or Production Mode.

      1) Test Mode Mean’s that no archive files are created

      2) In Production Mode the archive file is created depending on the selection criteria and rules

      defined for that archiving object

      Initial Selection Screen for Write Program of MM_SPSTOCK object. You can give the list of material

      number’s, Plant Data and respective Batch No’s which are no longer needed.

      Various Check Boxes provided on the selection screen serves a different purpose

      1) Consider batch record without deletion flag - Mean’s the record’s which are not having the deletion

      flag set are taken into consideration while archiving

      2) Check expiration data of batch – If the batch is expired it will be considered for archiving

      3) Only Consider Batch record’s without stock - Only select’s the record for which the stock is NULL

      and the rest of all are ignored

      Select Complete option listed in the drop down box which will give you the complete output log in the spool.

      Save the Variant and come back to the initial screen. Maintain the Start Date and Spool Parameters .Once

      you maintain them traffic light will turn onto green. Now Press the execute button and it displays a status

      message at the bottom “New Archiving Job was Scheduled.

      You can check the job log and spool using SM37 once the job is completed successfully

      Spool


      Click on the spool and you will get the complete processing log for the write step

      The log consists of details like No. of Written Data Objects, Size of archive file , Database space occupied

      in MegaBytes and list of Batch Master records that have been written to the archive file

      Delete Step

      After successful completion of the write step next comes the delete step where the data being written on the

      file is deleted using the delete program

      Now press the Delete button. Once you click on it you will be redirected to screen shown below

      Press the archive selection button and you will get a Pop-up display which shows you the completed write

      Session

      Select the check boxes and click on OK button. Maintain start date and Spool parameters which is the same

      as the one you maintained for the Write Step

      You can see all the traffic lights converted to green once you’re done.Now click on the execute button.You

      will get a status message “New Deletion jobs were scheduled”

      You can check the job log in SM37.If you observe carefully ,can see two jobs completed successfully .one

      job is the submit job which lasts for few seconds (ranging from 0 to 3 seconds) and the other one is the

      actual job which does the deletion process.

      Check the spool of the delete job. You will find some information related to the number of deleted data

      objects and deleted database space in MB etc.

      You can see the list of batch records in the spool which got archived successfully

      Verify the results from the database tables MCHA whether the records are successfully deleted or not.

      You can also check the same using MSC3N transaction.

      Archive Administration –Management

      Using the management option shown below in the initial screen we can view the technical settings and

      Logical file path names

      Click on the Technical settings .Observe the Logical file name maintained for this Archiving object

      The logical file name details can be seen using the transaction code FILE. Open this transaction and you can

      find the list of file names under Logical file name Definitions folder. Search your logical file and double

      clicking on it will take you to the Details screen.

      Conclusion:

      Batch Master Records are Archived and Deleted from the database successfully.

      Related Content

      Visit the following web pages

      http://www.help.sap.com

      http://www.sdn.sap.com/irj/sdn/nw-mdm?rid=/webcontent/uuid/f062dd92-302d-2a10-fe81-ca1be331303c

      http://help.sap.com/saphelp_dimp50/helpdata/en/8d/3e59fd462a11d189000000e8323d3a/frameset.htm

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.