Estimation of production system client size

Dear all,
we have planned to do client refresh from BI production to development system for only customization data (sap_cust)
for that i need to check in target systems space availability (in development system)
but how can we estimate and how much space it consumes in development system (file system ) and
which file system we required to increase and how much ,
and i tried to refresh in existing client in development system for this i need to take any pre - requisits
please i requested from your help on this
Regards

This questions have been asked multiple times in the forums before. There is info in both SAP Notes and Help.sap.com about it.
You should search before posting, Read the "Rules of Engagement"
Juan

Similar Messages

List of modifiable programs & reports in a productive system

Hi everyone,
I am trying to determine what objects are modifiable in a system set as productive. I have identified about 50 users who are assigned authorization object S_DEVELOP (activity=02 & auth group=DEBUG) in the production system. However the SAP consultant says that this is not an issue because program modification is not allowed in a system which is set as productive. This makes sense but is it true?
Is there a report or a table which can list system objects that are currently modifiable? From another forum a user suggested I check table OBJH. This was an excellent tip, however OBJH does not list ABAP programs or reports - just tables, views, etc. Any help will be greatly appreciated.
Thanks,
Martin

Hi Martin,
These settings are done at client level. Each client can be configured with below options
We can also view client details from SALE->sending and receiving systems->logical systems->assign client to logical system.
Client Role
Customizing
Test
Production
Demo etc..
Changes and Transport for client-specific objects
options are :
Changes without automatic recording
Automatic recording of changes
No changes allowed
Changes w/o automatic recording, no transport allowed
Cross-Client Objects changes
Options are :
Changes to repository and cross-client customizing allowed.
No changes to cross-client customizing objects
No changes to repository objects
No changes to repository and cross-client customzing objs.
And I don't think production system/client is allowed to do any changes to reports or dictionary objects. These must have to come from development system via quality system to production.
Regards
Manohar

Minimum Trusted RFC's for productive system

Hi!
We have very strict requirements dealing with set up of Trusted RFC for productive system for ChaRM approach in SOLMAN.
Can some one tell me which Trusted RFC's and users for the productive system do I need?
a) Trusted RFC is not mandatory for the productive system
b) Trusted RFC only in productive system, client: 000, users: 1 communication user and 1Dialog user
c) Trusted RFC in productive system for each client with users...
Thank you very much!
H. Thomasson

Create the function modules in SE37 and set the remote-enabled flag in the attributes section. Then import them into XI.
Create a custom Z table through SE11 on each system to store any data, and the code in each function module would reference it. (Either that or just hard-code everything)
In short yes it can be done through SE37, no you don't need SE38.
I think you're talking about function groups which is a container for the function module. You can do everything through SE37 if you use the Goto->Function Groups-> Create Group option and give it the same name as your Function Module.

Replicate data from one client to another in a production system

Hello,
I have two client in production system. Whenever a equipment is created in one client it should be replicated in another client and whenever a equipment is changed in one client the changes should be replicated to another client.
Data should be immediatly replicated to the another client.
Can basis do some setting so that the two client will always have the same data for equipments.
or i have to get the data from one system and send it to another system through idoc and update that data in another system. This will take a lot of time.
or is there any easy way

Hi Sachin,
You need custom program to achieve this requirement. Either you can use ALE+IDoc or direct BAPI function module call.
This should happen within seconds if designed properly.
Regards,
Avinash

Transformation pointing to Quality Client in Production System Repeatedly

Hi,
I need to understand one issue which is explained in detail below step by step.
1. I created one Customized Data Source(Full Load) and replicated in BW.
2. Also created Info Objects, DSO, Info Package, Transformation, DTP.
3. While transporting this modelling to Production(first time), i unknowingly/mistakenly missed capturing the datasource in Transport Request.Sequence of transport was -
Data Source
Info Area
Info Object Catalogue
Info Object
DSO
Cube & MP
Data Source
Transformation
Info Package & DTP
Now, the moment TR for transformation was transported it threw an error - "Data Source does not exist in Quality client". Then I transported the Data Source TR and after that re-transported the transformation TR production and this error was removed.
But, there were 2 transformations in production - 1) Pointing to Production, 2) Pointing to quality.
4. I request the basis team to delete the second transformation(pointing to quality) from BW production system.
5. After that we captured Data Source and transformation in same TR and transport was successful.
6. Now, after few days we transported a change to production for same object and the system again threw the same error mentioned in point no.3 above and created two transformations again.
How to resolve this issue permanently and I also want to know the reason of this type of system behavior.

Mohammed,
I did that also - please read my step no.4.
We are able to delete the transformation which was referring to quality client and then captured D.S & transformation in a single TR and transport as successful.
Now, after few days I did one change in the same transformation and transported to production.
System Behavior:
Error - " No source exist (i.e.,system referred to quality in production)".
Also again transformation was visible in production which was referring to quality client(which we already deleted with the help of BASIS).
Now since again the transformation needs to be deleted from production, our basis team is telling us to they cannot delete objects every time in production.Thus,
1. Is there any option to solve this issue permanently?
2. Also is it necessary to transport data source along with the transformation which is directly linked to data source?
Please Note: We have Dev+Quality as one client and Production.

Setting client role in non-production systems

In our QA test systems of R/3 and BW, the client role in SCC4 was set to 'Production'. The reason I was given is that by setting the client role to 'Production', will enable some settings in FI such as period closing,and customizing settings remain open without transportable requests. I totally disagree with this. I worked on numerous projects, but this is first time I am hearing this. I always set client role to Test in non-production systems, without any problems. Do any one have any idea about this?
Thanks
Santosh

SAP have a concept of "current settings". These include things like exchange rates and other items which really appear to be configuration settings. In a non-modifiable system these cannot be changed because the transport management system tries to get involved. If the client is set to productive, this restriction is overridden.
I would always suggest that the QA system should be set to productive and non-modifiable to ensure that the behaviour of the transactions affecting such objects can be tested in a production-like environment. If you need to have your QA system open for any sort of changes you are exposed to having changes introduced in QA to leading to the impression that new/modified functionality or config works but when the transport takes the unmodified version to production you'll be in trouble.

How to check client size in SAP

Hi All,
I would like to check the size of production client so i can do system refresh to QA. I need to know how to check client size only not database size.
Regards
Atul-

Hi
Yes, there is a report called YSTABSIZ which can calculate the size of the client.
1. Login to the target client ( for which the client size to be calculated)
2. Run SE38 , execute YSTABSIZ by selecting the table *
3. Execute the report in background
Once the client is deleted, the space which is free can be used to fill in with newly added data
but if you want to see the actual space reduction in DB02,it can be acheived only with DB reorganization
OSS notes 118823 and for this purpose
Hope ths helps
Please reward points
Sunil

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.

Best practice to reduce downtime for fulllaod in Production system

Hi Guys ,
we have options like "Initialize without data transfer ", Initialization with data transfer"
To reduce downtime of production system for load setup tables , first I will trigger info package for Initialization without data transfer so that pointer will be set on table , from that point onwards any record added as delta record , I will trigger Info package for Delta , to get delta records in BW , once delta successful, I will trigger info package for the repair full request to get all historical data into setup tables , so that downtime of production system will be reduced.
Please let me know your thoughts and correct me if I am wrong .
Please let me know about "Early delta Initialization" option .
Kind regards.
hari

Hi,
You got some wrong information.
Info pack - just loads data from setup tables to PSA only.
Setup tables - need to fill by manual by using related t codes.
Assuming as your using LO Data source.
In this case source system lock is mandatory. other wise you need to go with early delta init option.
Early delta init - its useful to load data into bw without down time at source.
Means at same time it set delta pointer and will load into as your settings(init with or without).
if source system not able lock as per client needs then better to go with early delta init options.
Thanks

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

Activating Update Rules in BW Production Systems? How

Hi all...
How do we activate Update rules in Production systems?
As we dont have the activate button high lighted in update rules.
Urgent.
Thansk in Advance.

Hi,
Since the production system is not chnagable you will will not get the activate button. you can only see the updaterules in display mode.
You should activate the update rule in the Dev environment and capture the same in a transportable request and transport the same to Production environment.
If it is very urgent and the transport from Dev would take time. You can as the basis to open the productyion client from tcode scc4, once the procuction client is open you will be able to activate the update rules in production system itself.
assign points if useful
regards
Venkata Devaraj

Process Order tables and Production System Performance

Hi All,
What are the different tables of Process order? Also how do i know which table affects the system performance of Production system and to what extent if Change Logging is made active ?
The issue is in our clients place we would like to set the Change Logging ( Records changes made for any transaction ) for Process orders and we would like to know to which tables change logging should be made active so that Production system performance is not affected.
Please help me regarding this.
Thanks in Advance,
Neetha Avani.

All the changes done in any transaction are saved in CDPOS table.
when there is any report developed based on this table then the performance will be very slow.
Tables used for process orders are
AFKO            Order header data PP orders
AFPO            Order item
AFRU            Order Confirmations
AFRUHR        Order Confirmations for HR
AFRV             Confirmation pool
AFVC             Operation within an order
Hope the above helps.

Error while transporting ADDRESS to production system

Hi all,
We are in the process of a new rollout and we have created new plants and company codes. the same have been transported to quality and pre-production systems without any issues. however when we transport the same to Production, we face an error
The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
The object
R3TR TDAT ADDRESS_4.6*
has not yet been imported into client 100 without error.
the objects are getting transported with same address number as in development which in production points to a different address.
as far as i know the system should generate a new address number and assign it to the object during transport.
Any suggestion wud be great

the log is
 Post-import methods for change/transport request: MEDK909182
 on the application server: ITMISAPGW2
 Post-import method AFTER_IMP_CUST_ADDRESS started for ADDRESS_4.6 T, date and time: 20090714144548
 Post-processing taking place in client 100
 The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
 The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
 The object TDAT ADDRESS_4.6 has not yet been imported successfully into client 100
 Post-import method AFTER_IMP_CUST_ADDRESS completed for ADDRESS_4.6 T, date and time: 20090714144548
 Post-import methods of change/transport request MEDK909182 completed
 Start of subsequent processing ... 20090714144547
 End of subsequent processing... 20090714144548
 Execute reports for change/transport request: MEDK909182
 on the application server: ITMISAPGW2
 Reports for change/transport request MEDK909182 have been executed
 Start of................ 20090714144548
 End of.................. 20090714144548
 Execution of programs after import (XPRA)
 End date and time : 20090714144548
 Ended with return code: ===> 8 <===
regards,
Tarun
Edited by: Tarun Bahal on Jul 16, 2009 9:41 PM

Generate Export DataSource from InfoCube In Production System

Software component : BI release 7.0 SP 18
Dear Gurus,
we have a strange situation in our production system from a month till now.
We want to generate an export data source from an infocube to load data into another one but now when we try to generate in prod ( right click on infocube and select "Generate Export DataSource" ) we can't create anymore.
Following message appears :
no changes to repository and cross client customizing object allowed
and the generation is stopped.
We always did it in production system in the same way as in the other system and then transported the update rule or transformation, but now it seems that is no more possible.
No setting has been changhed in SCC4 and in object changeability. Maybe is an authorization problem or is due to any other setting?
Does anybody has a way to solve this problem?
<removed by moderator>!
Kind Regards
Stefano
Edited by: Siegfried Szameitat on Nov 24, 2008 4:18 PM

Hi Stefano,
If you want to generate an export datasource you ask your basis team to open the system so that you can do.
As per the Sap Best Practise you can do the export datasoorce in your development system and move it to the quality and after testing you transport to Production.
Generallly if you can look in to production authorizations you may have only some operation like to display only.SOme times basis may give authorizations like creation of DTP and Infopacks like that.
Regards

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

Estimation of production system client size

Similar Messages

Maybe you are looking for