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.

Similar Messages

Solman 7.1: Who deleted/added system in a specific solution?

Does anybody know, if there is a change/activity log available in solution manager to track changes to solutions, i.e. to see:
- When was system XYZ added/deleted to the solution/logical components ?
- Who added/deleted a system XYZ to a solution/ logical component ?
Edited by: Uta Hedemann on Mar 1, 2012 10:24 PM

Hi Benoit,
Have you try on other workcenter ?
Solution Manager Administration -> Solutions -> Click on Object ID column -> solman_directory will be open trough sapgui.
On your first post, i can saw your need to open a solution, only that you need to maintain it. on the others comments yo told about to add logical components in a Solution. If it's that I think that you can do that on solman_directory transaction.
I think that if you can see a "ghost" popup that is closed immediately, that can be due to a Internet Browser Security options that block you to download the sap shortcut to acces using sapgui to solman_directory transaction.
Hope that can solve your problem,
Regards,
Lluis

SAP Product issue in 'Product System' tcode SMSY

In the process to create the new 'Product system' for SAP Product 'SAP ERP 6.0', system is not accepting any installation number (because of grey mode) but If i choose the SAP Product ' SAP Netweaver', i can assign Installation number for ECC server.
When i'm selecting Product 'SAP ERP 6.0' for new product system, i'm getting the Product version 'SAP ERP 6.0 01' .
as per our license policy, we have to use 'SAP ERP 6.0' as the SAP Product .
any idea about to fix it or if i'm missing something?
We are using SAP EHP1 for SAP Solution Manager 7.0 and SAP ECC 6.0 for ECC server landscape.
Thanks
Amar

using the following link (reply from Miguel section), i'm able to fix this problem
Product Version SAP ERP 6.0 Missing from solman 7.0
Thanks

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

SolMan 7.1 SP10: Managed Systems Configuration: client 000 OK, client 100 error

Hello,
after installing SolMan 7.1 SP10 successfully I also completed the steps "System Preparation" and "Basic Configuration".
Now I'm connecting the managed ABAP systems to the Solution Manager by performing step "Managed Systems Configuration".
After several other ABAP systems I'm now connecting our productive CRM 7.0 EHP1 system "CM3" (SAP_BASIS 702).
I also connected the CRM development and CRM quality assurance system without a problem.
For client 000 everything worked fine, the RFC destinations were created and a green light is shown.
Now the problem is to connect the productive client 100:
The log for Activity RFC Connection says:
The corresponding dev_rfc tracefile says:
**** Trace file opened at 20140326 164911 W. Europe Standard Time, by disp+work
**** Versions SAP-REL 720,0,523 RFC-VER U 3 1468763 MT-SL
======> Name oder Kennwort ist nicht korrekt (Wiederholen Sie die Anmeldung)
ABAP Programm: SAPLSM_SETUP_API (Transaction: )
Called function module: FUNCTION_EXISTS
User: SOLMAN_ADMIN (Client: 001)
Destination: 0050568713C71ED3AD9FC4F78AC9D9EB (Handle: 16, DtConId: 27FEB4E356BCF14F99EB0050568713C7, DtConCnt: 1, ConvId: 64734943,{27FEB4E3-56BC-F14F-99EB-0050568713C7})
EPP RootContextId: 0050568713C71ED3AD9FB7AD4C4859EB, ConnectionId: 0050568713C71ED3AD9FB784232C59EB, ConnectionCnt: 1
EPP TransactionId: BDFDB4E3626AF14899EB0050568713C7
But both users taken to execute this step (SAP Solution Manager Administrator "SOLMAN_ADMIN" and Managed System Configuration User "SM_ADMIN_SM3") exist and have the correct provided password.
Does anyone have a clue?
Kind regards
Rüdiger Höckel

Hello Ranjith,
thanks for your quick response.
The ST-A/PI software component is the same on all systems: 01Q_700 #2.
SolMan system: SM3
CRM systems: CM0 (ok), CM1 (ok), CM3 (problem with client 100, client 000 OK).
I also tried the recommendation found in the SAP Community Network
(http://scn.sap.com/thread/3483642) but this didn't help either:
1.Delete system from LMDB.
2.Delete system from SLD of solman.
3.Re- register the system to SLD of solman(rz70 for AS ABAP)
[the LMDB synchronizes with the SLD every 10 minutes, system CM3 is visible again in the LMDB]
4.Now follow the steps in managed system configuration.
The wizard worked fine for client 000 but throws this error for client 100.
I use all the latest installation and configuration guides.
For this step I'm using the guide "Managed System Configuration" that is available in the SOLMAN_SETUP wiki.
https://websmp206.sap-ag.de/~sapidb/011000358700001120342013E.pdf
Kind regards
Rüdiger
P.S. In total I have already connected eight systems (SAP_BASIS 700 to 731) but this is the first system that gives an error.

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

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.

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.

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

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

Steps to configure BPM report from Solman 7.00 for productive system ECC6.0

Hi all,
Please given me the steps to configure Buisness process Monitoring reports from Solman 7.0 for productive system( ECC6.0, windows & database oracle 10.2),
I wanted to create the Reports of monitoring the buisness.
Regards,
Akash Basis consultant.

Thanks for replying Volker von Gloeden,
This thread is my first one in SDN & I am very glad that someone has given the answer ,
I will take a look for solution you have provided & will inform you.
Thanks again.

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

Something is deleting my distribution list in Production system

Hello masters:
I created a distribution list in order to send emails from a workflow item. It's working fine in dev and qas. However, something is deleting my distribution list in Production system.
And the worst is that my distribution list is deleted as soon as I create it again (well, it lasts a few days).
Does anybody knows what could be happening?
Thank you.

Probably the Distribution list is not getting created at all.
Also check whether there is any program that is deleting the distribution list.
TZW02 User <-> Determine message
Also check for Authorization when you are trying to display existing Distribution list.
Thanks
Arghadip

Solman 7.1 SP10 delete product system in SMSY

Similar Messages

Maybe you are looking for