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

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

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.

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

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.

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

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

Can i use SWWL to stop a sync send in IP, in production system

hi forum,
in a scenario of mine, theres a BPM and in the BPM there is a sync send to a rfc function module,
after the scenario ran, i can see in the PE, workflow, that the scenario is hanging in the synchronous send step for 3 days 15 hours, and has not yet returned the response....
i could identify the problem ...because in the SXNB_ADM runtime parameter, HTTP_TIMEOUT , the current value is 2700000, which comes out to be some 31 days......
may be due to this the step is still waiting,
how can i stop the process,
can i stop the IP using SWWL, will there be any proble,
coz its in PRODUCTION system......

Hi Sudeep,
if you dont have any correlation: just wait for the 31 days, nothing bad can happen. It is important, to correct the reason, so think about, to reduce the timeout and put an exception branch to the send step, which is stopping the process.
If you have a correlation, other messages can share in the hanging process; in that case you should delete the workitem at SWWL.
Regards,
Udo

Create a Support Message in Production system showing up in Solution Manage

Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
Thanks
Paul

Hi Paul
The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
Make sure your RFC's are trusted and that you have SAP ALL during config.
I hope this will help:
Setup Service Desk
Steps to follow while configuring support desk.
1) Implement the note 903587 .
2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
3) Check all the objects in the table BCOS_CUST using transaction SM30.
Appl : OSS_MSG
+ :W
DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
+ :CUST 620
+ :1.0.
*4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
4.3) Activation of the following components has to be done by replicating the previous steps
3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
3.2) SOLMAN40_SDESK_ACTIONLOG_001
3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
3.4) SOLMAN40_SDESK_TEXTTYPES_001
*Depends upon the number of inactive BC set objects that we have after the upgrade.
4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
Number ranges for ABA notifications
5.1) create an internal and external number range using transaction DNO_NOTIF.
5.2) assign number range intervals to groups internal and external.
5.3) SLF1 is the internal number range group
5.4) SLF2 and SLF3 is the external number range interval
5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
5.51) Go to transaction DNO_CUST01
5.52) From the GOTO menu select the menu item DETAILS
5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
Number ranges for Support Desk notification
5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
5.6) Then assign both the external and internal numbering
5.61) Go to SPRO and then to SAP Solution Manager
5.62) Then select General Settings and then select Transaction types
5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
8.2) Select the item Service Desk and then to general settings.
8.3) Execute the category u2018Define Transaction Typesu2019.
8.4) Select the transaction type as SLFN
8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
9) Activate the partner/ Organization
9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
9.2)Find the entries starting with HRALX
HRALX-HRAC WITH VALUE 'X'.
HRALX-OBPON WITH VALUE 'ON'.
HRALX-PBPON u2018ONu2019.
HRALX-MSGRE u2013 u20180u2019.
9.3) If entries are not found create it.
10) Generate Business partner screens
10.1) Go to transaction BUSP.
10.2) Execute the report with the following parameters
CLIENT - Client in which business partners should be created (solution manager client)
APPLICATION OBJECT-
SCREEN - *
Generate all/ selected screens - All screens.
delete sub screen containers -
11) implement SAP note 450640.
11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
11.2) Execute it with test mode box unchecked.
If a new relationship is to be created then steps 12 and 13 has to be followed
12) To create a relationship category
12.1) Go to transaction BUBA
12.2) Select the entry CRMH00: Undefined relationship
12.3) click on copy
12.4) Rename CRMH00 to ZCRMH00.
12.5) CREATE A RELATIONSHIP CATEGORY.
IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
' FROM BP2 : IS A PART OF ATTUNE
13) Add the relationship category to the support team partner function
13.1)Use SPRO
IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
-> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
13.3) In the field relation ship category, Select the newly created relationship category and save.
14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
15) Create a new access sequence for the support team determination
15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Configuration ->
-> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
->Define Access Sequence
15.2) Click on New Entries
15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
15.4) Create an new Individual Access with the following value:
u2022 Batch Seq: 10
u2022 Dialog Seq : 10
u2022 Source : Business Partner Relationship.
u2022 Detail on the source:
u2022 Partner Function : Reported By (CRM)
u2022 Mapping/restrictions
u2022 Flag Mapping/definition for partner being Searched
u2022 Partner Function in Source: Support Team (CRM).
Save it.
This Access Sequence will give us the Partner which has the relationship assigned
to the Support Team in the Reported By partner data.
16) Adapt the partner determination schema/Function
16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
-> Partner Determination Procedure -> Define Partner Determination Procedure.
16.2) The two options to adapt partner determination schema are
16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
16.22) select the line starting with SLFN0001 or the newly created procedure.
16.23) Double Click on Partner Function in Procedure.
16.24) Select the Partner Function "Support Team", and click Details.
16.25) in the detail view only change the Partner Determination/access Sequence to
the one we've just created. Save your entry.
17) Create a root organizational model.
17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
17.3) enter the organizational unit, the description and save it.
18) Create the support team organization
18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
19) Create the business Partners.
19. 1) Key users- End user (Business Partner General) ,Address should be specified.
19.2) go to the transaction BP.
19.3) create a new Person, Select the role: Business Partner (Gen).
For Identification of the key user
19.31) click on the identification tab
19.32) enter a line in the identification number formatted as follows
IDTYPE : CRM001.
Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
eg: USER NAME : USER1.
CLIENT : 100.
SID : ER1.
INSTALL NUMBER : 123456789.
IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
20) Message Processors- Support Team members .
20.1) they should be created first as the users in the corresponding client of the solution manager.
20.2) As business partners they will have the role 'EMPLOYEE'.
20.3) Go to transaction BP .
20.4) Create New Person with the role employee.
20.5) In the Identification tab you should enter the user name in the employee data/User Name.
eg: username: proc1
enter proc1 in the field User name.
21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
22) Assign the business partners (Message Processors) to the previously created support team.
22.1) Go to transaction PPOMA_CRM.
22.2) Select the support team 1.
22.3) Click on create
22.4) select position
22.5) call it 'MPROC_T1/Message Processors for team 1
22.6) Replicate it for the other support teams.
22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
choose owner/Business Partner find and select the business partner
22.8) Validate and Save it.
22.9) If the assignment of business partner is not possible then implement the note 1008656
Or 997009
23) Create the iBase component
23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
23.2) or use the transaction IB51 to create the installed base.
23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
24)Assign Business Partners to iBase Components
IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
-> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
*--optional--
If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
now to assign the partner Function "System Administrator".
25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
26)Define the transaction variant for the message processors
Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
27) Go to transaction PFCG
27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
27.2) Give a description Message Processor role and save it.
27.3) Go to the menu tab and choose add report
27.4) select the report type : ABAP Report
27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
27.6) Enter the previously created variant.
27.7) flag the skip initial screen box.
27.8) flag the SAPGUI for windows.
27.9) Create a new transaction with tcode starting with Y or Z.
27.10)Display this transaction and check the values at the bottom of the screen
in the subscreen Default Values, you should have the following parameters:
u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
u2022 D_SREPOVARI-NOSELSCRN = X
And also all the user should have the correct role.

Deleting unecessary workitems in production system.

Similar Messages

Maybe you are looking for