Delete/Archive Plant in production system

Hello All,
As per the Client Bussiness requirement, could anyone explain me how can i delete the plant code in production system.
as far as i know, i need to:
close down all purchasing documents
check the inventory
deassign the Pur Org, storage locations ETC.
it would be great if i get all the Standard steps suggest by SAP.
regards
prasad

Hello Venkat,
As per the standard business functionality it is not advisable to delete the plant completely in database system.
Because you had lot of master data under plant creation ( E.g. - Material master , Physical inventory data, material document (GR/GI data) etc ) ..
So, If you are delete the plant code completely there is no past records for that existing master records.
So, It is advisable to do change the plant code name as " DO NOT USE - NAME (OR) BLOCKED - NAME ) in beginning plant name (SPRO settings) ..
For these plant code changes to Do Not use -prerequisite checking are
1. There is Nill stock in MB52 -Stock Avl.
2. MB5L Valuated inventory on GL  ( Nill inventory valuated )
3. "MB5T In-transit inventory " There is no stock in transit movement and stocks
After checking these above pre-requisite please following this below step for plant deletion..
1.  "OX10 Add ""DO NOT USE"" at the beginning of the plant name."
2.  "OX17 Delete plant assignment to purchasing org"
3.  "OVX6 Delete plant assignment to sales org"
4.  "OMS2 Remove Qty/value updating by material type "
Hereafter your plant is completely deleted in your database..Without affecting any existing functionality in business process.
Hope it would be useful..
With Regards,
Thiru

Similar Messages

  • How to find who has deleted the query in Production system

    I Experts,
    I have an issue. Someone has deleted one query in Production system.
    How can i find who has deleted the query??
    I searched the ans for the same i the below threads :-
    Query deleted in production
    How to find out who has deleted the production Query
    But it didn't help me as i couldn't understand how to use the transaction SLG1.. Can Someone please explain me how can i find out who has deleted the Query..
    Regards,
    Pavan Raj

    Hello,
    Please, remember the date on which date the query has seen last time  in the production server. You can use the last date in the From date and To date would be current  date and execute the SLG1 tcode. It would list you all the logs in the Object text you can search for BEX Query designer and sub object text column you can check for delete logs options.
    Double click on the object will list you the query and name. From the user column you can find who has deleted the query.
    Might be this can help you for analysis.
    Thanks
    Geeta Sharma

  • Creation of new Plant in productive system

    Dear All,
               I have to create 3 new plants. the system is already productive from the last one year.
    can anybody guide what will be the effects if i create new plants and send the transport to the production system.
    what need to be looked for side effects if any?
    pl give your valuable suggestions.
    Thanks and regards
    Ajay

    If you create new plants - there is no adverse effect but you have to make sure that the plant you create is copying by the existing.
    other things if you have any custom reports based on the plant then the new plant should be included, authorization needs to be consider if any basd on the plant,
    etc

  • Is it possible to Delete BP's from production system

    Hi All,
    Is it possible to delete old BP numbers from production system?
    if yes please let me know the procedure and impact on the system.
    if no please let me know ,how to prevent user from entering old BP number into order.
    Thanks in advance for your help.
    Regards,
    Shaik

    Hi Shaik,
    You can delete the BP using transaction BUPA_DEL.
    Just enter the number of the BP you want to delete and then execute.
    Make sure that all the checkboxes on the selecton screen are clear.
    In case the BP has dependencies and deletion is not alowed, you will get an error message informing you of the same.
    Best Regards,
    Rishu.

  • How to start Archiving process in production system.

    Dear Experts,
    As i was new to archiving process need help regarding this.as our client as 1.3 Tb of data with them,as they want to clean the unwanted data from the database.as they are using windows 2003 as server, oracle as database and using sapr/3 4.6 c.i want to know from where i have to start the process.i have read so many threads regarding this.they are helpful for me.i have some queries that i have to clarify.
    1) I have found which table increasing more in database.,i have checked (DB15 ,SAARA).how to find this has to archive.
    2) Data which is not important who has to delete that data.i heard data deletion is not basis work.
    3) After deleting data in datbase without reorganising space will not be empty is this may be the cause??
    4) is there any data loss in  reoraganising??
    5) is there any way to do reorganising with brtools in oracle.??
    Please clarify me.
    Regards,
    Naveen  N

    Dear Naveen,
    Data archiving is an inter-departmental activity.
    The person responsible for each application (which he/she is using in SAP Solution to carry out the business process) should be involved in SAP Data Archiving Process/Activities.
    The team should be grouped with the persons responsible for each application.
    After the planned Analysis, The team grouped for executing the Data Archiving process produce the checklist for Archive Data (based on your business process and other dependent factors). They will provide the inputs (archiving objects) for Data Archiving requirements.
    Moreover, As a part of Data Archiving process, you will have to delete the planned archive data from the actual Database. So, some spaces will become free in Database but all will be scattered in its respected Tablespace(s) in random manner. You will have to perform Database Reorganization to regain the free space.Because, The Data is stored in Database in form of Fragmented database objects (Tables/Indexes) in its respective Tablespace (s).Reorganization is generally performed to defragment these database objects. By doing so, one can improve performance and regain the space within tablespaces that was being unused due to fragmentation.
    I hope this information will be helpful.
    Regards,
    Bhavik G. Shroff

  • Deleting unecessary workitems in production system.

    Hello Friends,
    There are so many workitems avaable in user  inbox. Earlier there was some problem in the workflow, when user manually released the PR( Purchase Requisition or PO ( Purchase Order), the workitem wasnot disappeared from user inbox. We fixed it but those workitem processing the older version of workflow.
    And worktiem related document was released already.
    So, User dont want them. Please how to clean the user inbox. I Know about SWWL.but SAP advices not to use in PRD environment.
    It is very urgent. Please give urs valuable solutions.
    Regards,
    Manoj

    Yes, well, of course I will disagree... even though I've done it myself.
    The point about deletion is that not only can you corrupt things (even with top-level) if you don't know exactly what you're doing; but this is also supposed to be an auditable process. Transactions and reports are logged on a statistical basis (i.e. number of executions over time), and evidence that <b>something</b> relating to PO release has been deleted with <i>no trace of what and by whom</i> is a very bad thing if spotted by an auditor having a bad day.
    Kjetil's suggestion will do the job if there are a lot of items, however the question sounds like it might just be one item. Go into the technical view of the top-level item, Edit->Change and logically delete it. This way the item is gone and the log shows who cancelled it.
    Cheers,
    Mike

  • Deleting Variable in production system vis Transport request

    Hello,
    I need to delete a variable in production system via Transport request how can we do this?
    Thanks,

    Hi,
    Open the query in BEx in Development system, delete the variable form the query. The pop-up will arise for a new transport request. Capture the query in new request and then transport the same to Production.
    Regards,
    Yogesh.

  • Identification Test- and Production-System in Mapping

    Hi,
    we have a Java-function in a mapping step.
    There we need an identification if it runs in our Test- or Production-system.
    Currently we use a property file in the Java-Package for realizing this.
    But this is not a very good solution. The last time we transport the archive to our production system somebody forgot to change this property file and therefore we had some trouble in our production.
    Does anybody have an idea how we can identify the system name of the XI-system in a Java-Mapping?
    Is there perhaps any constant we can use of the Map input-parameter?
    In the documentation I didn't found anything about this.
    Best Regards,
    Thorsten

    Thorsten,
    Try using System.getProperty("SAPSYSTEMNAME") in your Java function.
    Regards,
    Jaishankar

  • Unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

    Hi,
    For SU01 role removal, you do not need S_USER_AGR with 02, and as you mentioned both authorizations available in production, if so trace should not show you the S_USER_AGR with 02 with RC=04.
    I would recommend to do role comparison for the user performing the activity. and then check if you have the S_USER_AGR with 02 in user buffer SU56.
    But ideally it should not ask you S_USER_AGR for 02 through SU01, so please take help of abaper to debug it.
    Also put trace in non-prd to see if S_USER_AGR is getting checked with 02 for removal through SU01.
    BR,
    Mangesh

  • Delete COPA value fields in a productive system

    Does anyone have practical experience with deleting COPA value fields in a productive system?
    The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
    An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
    I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
    Cheers, Peter

    To delete characteristics or value fields, you should perform the following       
    activities:                                                                               
    1. Delete the corresponding characteristics and value fields from      
    Customizing in all clients (this includes forms, reports, planning     
    layouts, and so forth). To locate characteristics and value fields, use
    the appropriate where-used list in the Customizing Monitor. You can    
    access it by choosing Tools -> Analysis -> Check Customizing Settings  
    (TA KECM).                                                             
    You can jump directly from the where-used list to the relevant         
    Customizing transaction and then delete the appropriate field there.   
    2. Switch to the screen for maintaining the data structure of an       
    operating concern (Maintain operating concern).                                                                               
    3. If you need to effect other changes to the datastucture for the     
    operating concern before making any deletions, effect those changes and
    save the data structure.                                                                               
    4. In order to be able to select the fields of the data structure,     
    choose Extras -> Characteristics (or Value fields) -> Unlock.                                                                               
    5. Select the characteristics and value fields to be deleted and remove
    them from the data structure with the "Reset fields" function.                                                                               
    6. Reactivate the operating concern. The system starts by checking
    whether the operating concern contains any data and whether the fields   
    to be deleted are still being used in any Customizing settings.                                                                               
    7. If none of the fields are still in use, the system then starts the    
    re-activation. If the operating concern does not contain any data or     
    does not require the database system to be converted, the tables are     
    activated. You are then able to activate the environment for the         
    operating concern. In this case, the following activities no longer      
    apply.                                                                   
    If the operating concern already contains data, a system message tells   
    you that the database needs to be converted. If you proceed, an          
    activation log appears (at the top of the list).                                                                               
    8. Analyze the activation log. If it only contains error messages        
    telling you to convert the tables, proceed with the next activity.       
    You must otherwise remove the cause of the errors before the tables can  
    be converted. In this case, you should answer "No" to the next prompt,   
    which asks whether the conversion transaction should start.                                                                               
    9. If you still only receive error messages telling you to convert the   
    tables, choose "Back" and start the conversion.                                                                               
    10. Plan a job for the conversion. A list of the tables to be converted  
    is shown for this. If the tables only contain a small amount of data     
    (less than 10 000 records), then all the tables can be converted in one  
    job. In that case, you can select all the tables.                        
    For larger tables, conversion should take place in several jobs.                  
    However, you should ensure that table CE4xxxx (where xxxx = operating             
    concern) is the last table to be converted.                                       
    Warning. No other changes can be made to the operating concern during             
    the conversion.                                                                   
    A copy of the table is generated during the conversion. The database              
    system should have sufficient memory available for this copy.                     
    To schedule conversion as a job, use the "Schedule selections" function.          
    You can display the current status of the conversion by selecting the             
    "Refresh" icon. Tables disappear from the list once they have been                
    converted sucessfully. If a conversion is taking a while, it is also              
    possible to leave the transaction. You can then continue the conversion           
    using DB requests -> Mass processing in one of the following ways:                
    With the job overview. You access this by choosing System -> Services ->          
    Jobs.                                                                             
    Using the database utility transaction. You access this by choosing               
    Utilities -> Database Utility in the ABAP Dictionary menu.                        
    You can use the status function to call up the status of the operating            
    concern during operating concern maintenance. You need to activate all            
    tables after conversion.                                                                               
    11. To analyze errors that have occurred during the conversion, you can           
    use the database utility transaction by choosing Extras -> Logs. The log          
    has the same name as the conversion job: TBATG-date. You can also                 
    restart the conversion with this transaction.                                     
    For more information on the database utility, choose Help -> Application          
    help while still in the above transaction.                                                                               
    12. Once you have activated all the tables in the operating concern,    
    generate the operating concern environment from within operating concern
    maintenance.                                                            
    You can then use the operating concern again.                           
    Please, refer to the IMG documentation under Controlling ->             
    Profitability Analysis -> Structures -> Define operating concern        
    -> Maintain operating concern, for further details.                     
    Hope it helps

  • Solman 7.1 SP10 delete product system in SMSY

    Hi,
    Somehow in my Solman 7.1 sp10 a product system is in SMSY and not in LMDB but in this SP I´m unable to delete it using SMSY and as the product system is not in LMDB, I don´t find how to do it.
    Anyone knows how to delete it.
    Regards,

    Hi Vevek,
    If it's not associated with LMDB and the data source is SLD or TMS/RFC and the date and time stamp is out-dated, then you can delete the product system in SMSY by switching to Edit mode. If the data source is LMDB, then it needs to be done via LMDB. I hope that helps to address the issue. If not please open a message with SV-SMG-SYS.
    Regards,
    Jay Soma.

  • Sap* deletion in Production System

    Hi experts,
      I wanted to do TMS configuration which require to login to my Production System from 000 client. I am newly joined here. And i dont now any of user password (DDIC,SAP,BASIS)* for client 000. I have tried reseting it from my MSSQL Database, But it requires Server Restart which i can not take because of High volume of users. I am taking help of my ABAPER in the same. But is there any other way to reset there password.i have tried Update and Delete command for unlocking and deleting the sap* user from database level. Command completed successfully but no use. I will be thankfull if anybdy can provide me the programme.
    Regards,
    Vaibhav Gore

    Hai,
    After deleting the user SAP* in client 000 did you try to login into the client with SAP* and password PASS.
    Also check parameter login/no_automatic_user_sapstar value in Instance profile or default profile, this should be set to '0' in order to login with SAP* and PASS password. If the above said parameter is set to '1' then you have to set it to '0' and then bounce back the SAP system in order to make the changes effective. After this you can login with SAP* and password PASS.
    Regards,
    Yoganand.V

  • Deleting Queries in Production system

    Hello,
    I transports few queries into production system but I would like to delete those queries
    Can i just delete in production or is there any procedure?
    These queries are just brand new queries.
    Thanks,

    What is the difference between "Create Transport Requests for BEx "  and "Transport object"
    When do we use "Create Transport Requests for BEx "?
    When do we use "Transport object"?
    Correct answer = points
    Thanks,
    Edited by: Moderator on Jan 30, 2008 3:41 PM
    *Everyone on the forum knows that points will be assigned for correct and useful replies. There is really no need to keep mentioning this on each post you create. Thanks!

  • PERNR deletion in Production System

    Is it possible to delete PERNR in production system after Posting is done and bank transfers are also made.

    Dear Samrudhi,
    Before trying to delete the personnel number please ensure you have completed the following steps.
    1. Identify the posting run number in which the payroll result for this employee is posted to accounting.
    2 .Reverse this posting run from PCP0 transaction.
    3. Delete the payroll result using the transaction PU01.
    4. Clear the fields in infotype 0003 using PU03 transaction.
    5. Use PU00 to delete the personnel number, if any time evaluation results are there for this employee choose B2 cluster first in PU00 transaction then deleting the personnel number.
    Please let us know if you still have problem with this. Also do not forget to remove this personnel number from the DME file generated and repost the reversed posting run which include other employees result.
    Regards
    Raviiiiiiiiiiii

  • Physical Inventory Document deletion in Production system

    Hi Friends,
    There is an physical inventory document # xxxxxxxxx from 2003, which has
    also posting block, which is likely to cause that couple of materials
    can not be maintained.
    Now This document needs to be simply deleted in tx
    MI02. I tried this in Test system and did not have any trouble.
    However I am not sure can i do the deletion in Production system..??
    Pleae guide me is there any problem in production to cancel this Document.
    What type of precations i  need to take care in Production system.
    Brgds,
    RK

    Hi there
    You can delete it directly, it is not an issue, if you want to cross check ( if the material with CC), you can run in MICn for those materials and generate session page you can see for avail for the generate session to create the new PI/CC (based on the Last count date as the older one, not the recently counted and deleted,,)
    Hope it helps
    Senthil

Maybe you are looking for