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

Similar Messages

  • 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

  • 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

  • Error in Importing standard SAP DCs to Production system

    Hi All
    I am trying to do a transport from QA to Production system. 3 of the standard components
    sap.com_GP-CORE
    sap.com_CAF-MF
    sap.com_CAF
    are not getting imported  to Prod. It gives an error
    caused by Exception:com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'cedeploy' could not be connected to the specified host 'bhbc1ce01.ent.bhicorp.com'and port '50004'.:The user 'cedeploy' could not be connected to the specified host 'bhbc1ce01.ent.bhicorp.com'and port '50004'.
    com.sap.cms.tcs.beans.exception.TCSDeployException_Communication: The user 'cedeploy' could not be connected to the specified host 'bhbc1ce01.ent.bhicorp.com'and port '50004'.
    The user is not locked. I managed to import the rest of the components to Prod with the same user ID.
    Only thing i am able to notice is that, the Owner for these 3 components are "jointadm"  and the rest of the other components had owner as "Make".
    Please give me your suggestion.
    regards
    Deepu

    HI,
    Under the runtime systems tab in CMS lanscape configurator,
    check  the username and password details given for thr production runtime system .
    also once save the configuration.
    Regards,
    Satya.

  • Pernr delete from productive system

    i have run payroll for a pernr - 12 -- 2008 and now want to delete, but system is not detleting the no.
    suggest the step  asap
    rgrds
    rs

    PU00  for deletion fo PERNR
    is the tcode check this one and double confrim once again

  • 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.

  • How to remove Production System from Solution manager.

    Hi All,
    We have Three system landscape and solution manager installed.
    All the system are managed by Solution manager.
    here we are looking to remove the Production System from Solution manager.
    as in case if is there any problem in solution manager then we are not dependent on it.
    things will work directly on Production system.
    Could you please let us know the procedure to remove the system from solution manager.
    Please let us know if is there any document provided by SAP.

    Hi,
    Have you implemented charm,ccms monitoring or any other functionalities?
    if yes,.Delete the sytem from tms domain. and TR route needs to be adjusted, if you are using ccms, remove the agent details from RZ21 also.
    Does your production system data coming from SLD?
    if yes, Delete the entry from SLD
    if both the answer is no.
    1.delete  RFC from SOLMAN to the production systems.
    2. delete the production system using SMT2 transaction.
    3. Remove system rom SMSY from SOLMAN.
    Thanks,
    Jansi

  • Product system not in LMDB only in SMSY

    Hi Solman experts,
    I have a question regarding Solman products in LMDB and SMSY.
    After updating Solman 7.1 from SP08 to SP10, in Managed Systems Configuration, Assign Product step I get the following errors:
    (I am using ABC as SID)
    ABC00001~JAVA: part of product system ABC, which is not in LMDB but only in SMSY
    ABC~ABAP: part of product system ABC, which is not in LMDB but only in SMSY
    In SMSY i see that under ABC there is both ABAP and JAVA whereas under ABC00001 there is only Java (in Products system).
    The Diagnosis of Solman for this error is:
    Diagnosis
    The technical system ABC00001~JAVA is assigned to product system ABC, which was created in transaction SMSY and has not yet been migrated into the Landscape Management Database (LMDB).
    The technical system ABC~ABAP is assigned to product system ABC, which was created in transaction SMSY and has not yet been migrated into the Landscape Management Database (LMDB).
    System Response
    Procedure
    If the product system information in transaction SMSY is still required for your system landscape maintenance, migrate it to LMDB. You can do this in the SAP Solution Manager: Configuration work center under System Preparation -> Prepare Landscape Description -> Migrate SMSY Data into LMDB -> Migrate Product Systems. (For more information, refer to the help text in the UI.)
    If the product system information in transaction SMSY is no longer required for your system landscape maintenance, delete the product system information in SMSY.
    Could anybody who had the same experience share their opinion on this case. This LMDB<>SMSY change is very confusing at this step. Would be more meaningful to execute the optional migrate from SMSY step or delete the product. the second seems a little bit meaningless in this case.
    Thanks in advance.
    Regards

    Hi Shkëlzen,
    then that could be the reason why you have some system(s) in SMSY and LMDB.
    As far as I understood you need to migrate all your Landscape from SMSY to LMDB by using the step "2.4 migrate smsy to lmdb" as mentioned by Jansi Rani Murugesan at http://scn.sap.com/message/15079962#15079962
    It might happen that this transformation creates double system entries in LMDB by adding the 0000x to the SID. But this is only an visual "defect".
    Once you have done the conversion from SMSY to LMDB you should get this issue resolved.
    The conversion report took me more than 48 hours to complete. This is totally normal. You can execute some database statistics updates and/or check/optimize the profile parameters and hope the conversion runs faster.
    Hope this helps,
    Niklas

  • Performing SPAU in Production System

    Dear Team,
    We are in the process of upgrading our Production system from EHP3 to EHP7.
    We upgraded our Quality system with SPDD and SPAU transport requests from Development system and it finished successfully.
    But after upgrading our Kernel in Production system and before performing the EHP7 upgrade, we applied two SAP notes in Production system, these notes were transported from our temporary development(un-upgraded) system(parallel landscape).
    While performing the EHP upgrade in Production system,  SUM has prompted us the below message
    “Decide about Incomplete Modification Transport”
    CAUTION: The program has found the transport "MEDK906662"(our SPAU transport) for SPAU but it does not contain all objects which need adjustment.
    When we checked the log file it show that two objects are missing in the SPAU transport.We suspect these are the SAP Notes which we applied after kernel upgrade and are missing in SPAU transport request.
    Please let me know how we can correct this issue in Production system. I know that SPAU will appear in Production system, but will the system allow me to re-apply/reset the SAP note in SPAU as this system will be un-modifiable.
    Regards
    Imran

    SE06.
    System Change. Global setting "modifiable". Componenents "modifiable". Namespaces "modifiable".
    Client setting-> select client -> Automatic recording of changes, changes to repository and cross-client customising allowed, protection level 0.
    If that doesn't work, give yourself SAPALL and try again.
    If that doesn't work, contact SAP because something is messed up. I've successfully applied notes in P systems during upgrade. Including ones that modify SAP_APPL.

  • Help on applying Workflow Relevant SAP Notes in Production

    Hello,
    Can you please provide your input whether we should apply below mentioned SAP Notes in Production system.
    1.SAP Note-0001925195
    Symptom-
    In the context of event generation for system and user status, the system no longer generates the event)
    2. SAP Note-0001946643
    Sympton-
    The following runtime error occurs in your system:
    Category ABAP Programming Error
    Runtime Errors OBJECTS_OBJREF_NOT_ASSIGNED_NO
    Except. CX_SY_REF_IS_INITIAL
    ABAP Program CL_SWF_RUN_WIM_LOCAL==========CP
    Application Component  BC-BMT-WFM
    The problem occurs only if you use an API to start a new work item within the execution of another work item. Additionally, you use an ABAP OO methods in the work item task.
    3. SAP Note-0001935328
    Symptom-
    A runtime error occurs when you call the workflow outbox or a corresponding API.
    Runtime error EXPORT_NO_SHARED_MEMORY
    Exception CX_SY_EXPORT_NO_SHARED_MEMORY
    The short text of the runtime error tells you that the EXPORT data cluster is too large for the SHARED MEMORY. The termination occurs in the class CL_SWF_RUN_OUTBOX_PERSISTENCE
    I would appreciate quick response with reasons on same.
    Regards,
    Sudeesh Soni

    Hi Abdullah,
    We are not applying given SAP Notes directly into Production.
    Basis team is applying the Support Package stack(SPS) and further, they would like to know the impact of applying above mentioned SAP Notes.
    Regards,
    Sudeesh Soni

  • Data cleanup for customtables in production system.

    Hai,
    My requirement is  a list of custom tables data should be deleted in production system based on some selection-criteria.
    Any one can suggest how we can achive this.
    Shall I write any Zprogram or any other way.
    I have written code for one table .
    Reprot ZTesdel.
    Tables :  YDCS_COMP_CR.
    DATA itab1 type STANDARD TABLE OF YDCS_COMP_CR.
    SELECT * FROM YDCS_COMP_CR INTO TABLE ITAB1.
    DELETE YDCS_COMP_CR from table ITAB1.
    Please any one can tell the same code will work for deleting records from YDCS_COMP_CR or any other piece of needs to added?
    Regards,
    Krishna

    Depending on the nature of the data, there might be a legal retention period to be observed.
    Also check for dependencies to other tables, foreign keys, so you don't end up with a corrupt database.
    If it is data in the GB range, don't delete in one chunk, or the redo buffers might overflow. Instead fetch packages of x records, delete them and do a commit work before reading the next package. Use OPEN CURSOR WITH HOLD and function DB_COMMIT for this purpose.
    Thomas
    Edit: just saw this is a continuation of
    custom tables data deletion (data cleanup)
    zprogram to custom table data deletion
    Please now work with the information provided so far before coming back with more questions.

  • 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/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

  • 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

  • Two SAP production systems in a single physical server

    Dear All,
    Is SAP support installing two SAP production systems like SAP ECC 6.0 of one customer and ECC 6.0 with a different SID and instance no. for another customer in a single physical server? Would like to know from the experts is this possible? If yes ,  what are the things to take care of this design if any?
    Thanks
    Hany

    Hi ,
    check below blog
    You can check the following blog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/5124. [original link is broken]
    It helps you to understand different logon pages for portal
    Koti Reddy

Maybe you are looking for