Running SCOV ( Coverage Analyzer ) on Production System

Hi,
Our organization would like to start using SCOV ( Coverage Analyzer ) on our Production system. From our understanding, when the main switch is turned on, there are several jobs scheduled that compile all programs. This step should be very expensive in terms of system resources and when it is done on Production system - it could be crutual. My question: is there any way to make this step easier in terms of performance overhead? Maybe to run it on each Application Server seperately?
In general I would like to know if anyone has experience running SCOV on production system. Is there any effect on performance except the first compilcation step?
Thanks in advance,
Anna Lifshits-Agmon

Hi,
Please check this link
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/aff89590-0201-0010-5aa1-bc174397594e
Thanks and regards
Durga.K

Similar Messages

Using SCOV ( Coverage Analyzer) in Production

Hi,
Our organization would like to start using SCOV ( Coverage Analyzer ) on our Production system. From owr understanding, when the main switch is turned on, there are several jobs sheduled that compile all programs. This step should be very expensive in terms of system resources and when it is done on Production system - it could be crutual. My question: is there any way to make this step easier in terms of performance overhead? Maybe to run it on each Application Server seperately?
In general I would like to know if anyone has experience running SCOV on production system. Is there any effect on performance except the first compilcation step?
Thanks in advance,
Anna Lifshits-Agmon

you might want to take a look at OSS note 626215. We recently ran this overnight in our development system and it fell over, running out of tablespace in certain areas. Next time we ran it, we used the note, extended the necessary tablespaces and made sure we kept an eye on it. It took a day to run in our development system as it generates every program on the system. We've not yet tried it on Production.

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

Reg: Unicode- Coverage Analyzer- (SCOV)

Hi
Can any one tell me how we can use the Coverage Analyzer (Transaction SCOV)as a tool for Unicode enabling. What are the sequence of steps that are to be followed.
Any Information, Documentation, Links, or examples that elucidates the same are highly solicited.
Thank you in anticipation.
Regards,
Sravan.

Hi,
I haven't used SCOV much.
In SCOV, 'global view' gives you a set of figures and graphical representation of system performance data. One of these graphs show the unicode-percentange of all programs that are unicode-enabled(one axis is time (month) and other axis represents percentage of programs that are unicode enabled). This is just to see how many programs have been unicode-enabled in the system. As long as you are not 100%, there is work to be done.
To force unicode-enabling (there may be programs which are unicode compliant but have not been set to unicode), you can check the profile parameter abap/unicode_check to enforce unicode syntax checks. (This has nothing to do with SCOV per se).
Now, how best to use SCOV when an object is being unicode-enabled and you need to make sure it is working fine?
After unicode-enabling the program you need to test it to make sure it works. But after running one or more tests successfully, how do you know whether all lines of code in the program have been covered in the tests?
SCOV can give you information whether all blocks of the code has been tested or not. If all blocks of a program/object have been tested after unicode-enabling (as reported in SCOV) then you can assume your testing to be complete. If on the other hand some blocks (let us say cetain subroutines in the program) have not been executed, you can see this in the detailed view in SCOV, and accordingly run other tests to ensure that this code is tested.
I am sorry I can not give you a step by step for this, if you post your mail-id, I can probably mail you a document which talks about this in a little (not much) detail.
cheers,

Aggregates in Production System and Change Run Hierarchy

Hi All,
Can anybody tell me, Why should we create Aggregates in Production System nd How?
What is Change Run Hierarchy nd How to perform this?
Reply back me to [email protected]
Regards,
Kiran

Hi Kiran,
Aggregates are nothing but a subset of your Infocube... when a query is executed, it firstl looks for the presence of the data in your aggregates and if found then it fetches the reocrds from there itself.. Else not, it'll search teh entire infocube and then fetch the records which is at a high risk of time consumption and the performance of the Query execution slows down or becomes worse significantly.. for this purpose, you build aggregates.. how do you decide whether you should go for aggregates or not is based on the following criteria...
if the %Data Base time is > 30% and if the KPI ratio (selected to transferred records) is > 10, then you go for the aggregates... you can get these details in the ST03N transaction by choosing Expert mode and selecting BI Workload... you can find all the statistics related to the Query execution starting from the front end time to db time/...
thats all about your aggregates...
Attribute or Hierarchy change run is done so that any changes to your Master data Attributes will have to get effected in terms of your reporting...
say for eg.. ur name is XYZ and loc is in India.. this is how it'll be reflected in your reporting also.. but at a later point in time, if you have changed your location from India to Europe, then for that to be reflected in your reporting, you'll have to perform an Attribute change run for that Characteristic...
Hope it solves your issue..
Regards
Manick

Background Job Running long time in Production system ???

Hi guys,
I have custom report which runs normally in 20 minutes. i am executing this report every day. but when i execute the same report yesterday it took 5 hours.
i did the performance trace ....the sql statements are in acceptable range only. i don't see any major time consumption.
since it's in production system we can't debug the active job....
can u guys, throw light on this issue.
Note : there are many posts related to this already in the forum, but not helps to resolve my issue.
Regards
Girish

Giri,
You can use STAD (or older one SE30) to have a trace of the program if you have that access and will be a great help in finding the problem.
If you can't due to some reason, then next time job runs for long (while in ACTIVE state), check SM50 regularly to see that the is process hanging on a table fetch, check that any of the DB table is not getting frequent locks in SM12.
Also, you should check that if your job does any table update, is there any new index created in prod system for that table.
If you can't find anything, then take the necessary access in Prod from basis temporarily and debug the job to find exact issue.
Regards,
Diwakar

BRTOOLS applications die with Dr Watson exeption [BW productive system]

Our BW system is:
Oracle: 9.2.0.5.1 64Bit Unicode
Sap Kernel Release: 640, Patch 40
Osystem: Windows 2003 Enterprise Edition Service Pack 1 [NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10]
SAPKB64010
SAPKW35010
Problem Description
On 07-May-2006 we upgraded our Database server Operating system with
Microsoft Service pack 1 [Windows 2003, Enterprise edition, Service
Pack 1].
Since then BRARCHIVE, BRCONNECT etc die : process died with exitcode -
1073741819
On the Operating System Event viewer the message is:
Faulting application brarchive.exe, version 6400.121.12.35249, faulting
module orannts9.dll, version 9.2.0.2, fault address 0x000000000000b830.
Dr Watson application creates a log File with :
Microsoft (R) DrWtsn32
Copyright (C) 1985-2002 Microsoft Corp. All rights reserved.
Application exception occurred:
App: E:\usr\sap\BWP\SYS\exe\run\disp+work.EXE (pid=768)
When: 5/6/2006 @ 16:40:28.665
Exception number: c0000005 (access violation)
--> System Information <--
Computer Name: SAPBW
User Name: SAPServiceBWP
Terminal Session Id: 0
Number of Processors: 2
Processor Type: ia64 Family 31 Model 1 Stepping 5
Windows Version: 5.2
Current Build: 3790
Service Pack: 1
Current Type: Multiprocessor Free
Registered Organization: ATTICA
Registered Owner: sysman
.... etc
On our R/3 productive system oly BRCONNECT (for ANALYZE and CHECK) dies
while BRARCHIVE does not have any problems.
I downloaded the last version of BRTOOLS 6.40 <38> but still we have
the same problem.
Do you have any idea about what is going wrong ?
Thanks in Advance

I changed the initSID.sap and some lines kep uncomented and whitout any key word. Then get the error and when put double coloms in those lines the error disappear. I´m affraid ours problem wasn,t the same.
Best regards,
Javier.

Unicode Coverage analyzer

Hi,
Can somebody please help me with how to use coverage analyzer?
Thanks,
Yogita

Hello
The Coverage Analyzer is a tool for entering the number of calls for processing blocks and executable programs separately according to periods, users and functional areas. The processing blocks and executable programs together with their keywords are shown in the following table:
Unit
Keyword
Procedures
form, function, method
Dialog modules
module
Event blocks
at line selection, at pf<xx>, at selection screen, at user command, end of page, end of selection, get, get late, initialization, start-of-selection, top-of-page
Programs
program, report
The Coverage Analyzer is, therefore, a function for monitoring the system-wide execution of ABAP programs. It also
enables the success of test activities to be assessed for quality checks,
provides an overview of the use of programs for development purposes.
The transaction is SCOV.
For help on this check
http://help.sap.com//saphelp_470/helpdata/EN/c7/af9a79061a11d4b3d4080009b43351/frameset.htm
Coverage Analyzer tool.
Bye
Gabriel

RFC users locked after system copy in production system

Hi,
BW_User,MDBTC(RFC users) system users were locked in our BI Production system at the same time system copy activity was running in the Quality system(production to quality) so as per our colleagues concern after system copy they started Quality system with out changing background work-process 0 so some jobs were triggered which were copied from production system.
Is there any cause to lock RFC users in production system for system copy? If there is any other reason where we can check logs
Thanks
Jalandhar Reddy

Hi,
Well maybe i am wrong to analyze your problem .
Anyway I faced this issue to in our system before and we found that one background job was running in a system that has basically prompting an RFC connection to another system. In the t.code SM59 and there was wrong password was put in.We just reset the password and it was worked fine.
You can try for this..
Regards
Bhuban
RKFL

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.

Not able to change the data of test data containers in production system

Dear All,
We have created eCATT scripts in Development SolMan System and moved the transports to Production SolMan System. Customer wants to change the data at Test data containers and run the scripts in production system but we are not able to edit the data.
May be the reason is SCC4 transaction code has set the below option.
Changes and transports for client-specific Objects
u2022 No changes allowed
Customer doesnu2019t want to change the above option and wanted to change the test data containers to give different datau2019s and run the eCATT scripts.
Could you please let me know the solution for this?
Your help is really appreciated.
Thanks,
Mahendra

eCatt has the feature where you don't need to transport the scripts or test configuration to our target system. We can keep all our scripts and test data in Solman and run this script any other system in your landscape using the System data container and target system.
Maintain the production as one of the target system in System container in Solman and point that system while running the script. Change the test data in Solman to run this script.
Let me know if you need more information
thanks
Venkat

Fetch data from a table present in production system

Hello Gurus,
I want to get data from a table which is present on production system. And i cannot create RFC. Can anybody tell me any other way of getting the data?
Thanks in advance!!
Regards,
Kumail

Hi,
if it's just a one time requirement to get the data from the table into an excel sheet e.g. for some error analysis or for making a development decision, why bothering with development? Just run se11 or se16 display the whole content and save it as excel sheet via the menu. This would be the fastest solution in my opinion.
If you do not have the permissions to see the table in production ask a admin or super user. Creating a program to dump data from the system you are not really allowed to see usually brings you in a lot of trouble :o).
Kind Regards
Roman

Support message and change requests only for production system

Hi guys,
I would like to connect the solman helpesk with CHARM ( CHARM is still running ).
In CHARM I have to create a CR only for production system. ( don't know why - but works as designed).
In SAP helpdesk I can create support messages for every kind of system type but if I want to connect both (HD and CR) , the source system (ibase component) of the issue will copied to the CR and runs in error because of the rule (only p-system) of CHARM.
Of course I can change the ibase to production system manually in SDCR but it seems a very error-prone method.
Now my question: is it possible to change the ibase component due to the creation of CR by copy rule or something like this?
Kind regards
Rayko

Hi Rayko,
We do not have this option.
Once in ChaRM, we assume that the changes will always correct an issue in the PROD system.
I would recommend to open the tickets directly with the PROD system IBase, once the issue is also happening there.
Best Regards,
Fernando

Problem during import of 121 transport requests to productive system

Hello
We have problem during import of transport requests to productive system. Import of 121 transport requests stopped very soon in phase "N" (in TRBAT I have only one entry and in TRJOB as well).
In sm50 there is an BGD running under user DDIC in client 000 now for 14453 seconds (program SAPLSDB2). This should be import.
In SM37 I can see it as job "RDDGEN0L" with repport"RDDGENBB". Based on some literature it should perform "Converting all structure changes generated by the import and recorded in table TBATG, other than the structure changes to matchcode objects." Very interesting that TBATG has only four entries related to 2 indexes in table "DFKKOPK" , one in table "DFKKREP06" and one" ENQU" for EFKKEXC". (only this last one has not status error)
For fist two indexes I know they are not present as objects "LIMU""INDX" in any transport request beeing imported.
Also on productive system there is no"VOL" and "ZOL"indexes for table "DFKKOPK"(instead they are created on test system ie. not transported from development to test system)
Last command for that process is "CREATE INDEX "DFKKOPK~HKO" ON "DFKKOPK" ("MANDT", "HKONT", "OPBEL") PCTFREE 10 INITRANS 002 TABLESPACE PSA
PTR3 STORAGE (INITIAL 0000000016 K NEXT 0000000016 K MINEXTENTS 0000000001 MAXEXTENTS UNLIMITED PCTINCREAS"
There is enaught space on disk and in tablespaces (it is an oracle/HPux server).
Does anyone knows workaroun to solve production

are you importing these transport requests simultaneously into production?
I would suggest you try doing in smaller groups of 5 or 10 and then see whether you are able to import the requests
Rohit

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

Running SCOV ( Coverage Analyzer ) on Production System

Similar Messages

Maybe you are looking for