Solman 7.1 LVSM Product system has no technical system assigned

Hi All,
As reference of blog #sapadmin:: How to assign Product System in SOLMAN 7.1 & How LMDB, SLD, SMSY and Landscape Verification work in SOLMAN7.1SAPNetworkWeblogs%2528SAPNetworkWeblogs%2529
I have created product instance from LSVM and now I have problem to add "product system" for Enterprise portal (using NW 7.3) to the landscape, as its throw me an error "Product system has no technical system assigned".
From the display help its mentioned:
*Diagnosis*
Product system is not assigned a technical system in the system landscape of the Solution Manager.
*System Response*
Since the system landscape of the Solution Manager forms the basis for working with SAP Solution Manager, if your product systems are incorrectly assigned, many important functions are not available to you, or are only available on a restricted basis.
*Procedure*
Assign one or more technical systems to your product system . SAP recommends that you use the corresponding wizard of the Landscape Verification Tool. To start the wizard, choose the button Change Technical System Assignments next to the message. The user interface of the wizard contains detailed information about its usage.
I'm not sure with sentence of Assign one or more technical systems to your product system and which wizard are this referring to ?
I have also checked from the wiki:
http://wiki.sdn.sap.com/wiki/display/SMSETUP/MaintenanceofProductintheSystemLandscape#MaintenanceofProductintheSystemLandscape-EnterprisePortal
And its only supported for NW 7.0 not 7.3.
Is there anyone had this issues ?
It's feels like I'm the only one stuck in this.
Thanks in advanced.
Raff

Hi Sunny,
Many thanks for your reply.
I have followed the guide you mentioned, now I can see 2 EPD Error from LVSM.
1. Product system EPD has no technical system assigned (new)
2. Technical system EPD is not assigned to a product system
For number 1. if I clicked on Change Technical System Assignments I can see EPD there, but when I want to add the EPD by clicking > I've got this error message " Newly linked technical system EPD has already been locked by user" I've tried to remove the lock from sm12 but nothing happen.
For number 2. if I clicked on Change Product System Assignments, there is an error messages "Technical system EPD was updated in parallel session"
I believe the number 1. coming because I create it from SMSY, but the number 2. is still there in the first place.
Cheers,
Raff

Similar Messages

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

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

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

SOLMAN 7.1 Assigning Hana database Technical system to product system

Hi All,
I am trying to assign a HANA database technical system to Product system.
I am trying to do it in conventional way (i.e in LMDB TCODE--> Selected Product system-->Assign Technical system--> ).
But I am getting below error.
No local proposals; search remotely in SAP SMP (time-consuming).
So wanted to know whether there is any other way for assigning Prodcut system to HANA DB Technical system.
Please find the screen shot for the error message.
Thanks & Regards,
Solman Starter

You can either use a product system that already exists for the ABAP system (if the ABAP system was already connected to Solution Manager) or create a new one. After all you should use the same product system for ABAP and HANA.
Check this for further reference -
Managed System Setup of HANA in Solution Manager 7.1 - SAP Solution Manager Setup - SCN Wiki

Unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

unable to delete Role from User ID in SAP SOLMAN production system but able to from DEV with the same authorization, pls suggest

Hi,
For SU01 role removal, you do not need S_USER_AGR with 02, and as you mentioned both authorizations available in production, if so trace should not show you the S_USER_AGR with 02 with RC=04.
I would recommend to do role comparison for the user performing the activity. and then check if you have the S_USER_AGR with 02 in user buffer SU56.
But ideally it should not ask you S_USER_AGR for 02 through SU01, so please take help of abaper to debug it.
Also put trace in non-prd to see if S_USER_AGR is getting checked with 02 for removal through SU01.
BR,
Mangesh

Solman 7.1 SP10 delete product system in SMSY

Hi,
Somehow in my Solman 7.1 sp10 a product system is in SMSY and not in LMDB but in this SP I´m unable to delete it using SMSY and as the product system is not in LMDB, I don´t find how to do it.
Anyone knows how to delete it.
Regards,

Hi Vevek,
If it's not associated with LMDB and the data source is SLD or TMS/RFC and the date and time stamp is out-dated, then you can delete the product system in SMSY by switching to Edit mode. If the data source is LMDB, then it needs to be done via LMDB. I hope that helps to address the issue. If not please open a message with SV-SMG-SYS.
Regards,
Jay Soma.

How to 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

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

Product system not in LMDB only in SMSY

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

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

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.

Error while extracting the data in R/3 production system,

Hi Team,
We got the following error while extracting the data in R/3 production system,
Error 7 When Sending an IDoc R3 3
No Storage space available for extending the inter 44 R3 299
No storage space available for extending the inter R3 299
Error in Source System RSM 340
Please guide us to fix the issue

It´s very difficult to help you without knowing
- what is going to be transferred
- where you get this error
- system configuration
- actual memory usage
- operating system
- database and configuration etc. etc.etc. etc.
I suggest you open an OSS call and let the support have a look on your system. It´s much easier if one has system access to find out the cause for that problem.
Markus

Error message while transporting SapScript to productive system

Hi,
I have tried to transport an order sapscript form (modified Medruck) into the productive system. But I got errors in transaction stms.
The error message is displayed like this:
R3TRFORMZMEDRUCKN was repaired in this system
Message no. TW 104
Diagnosis
Object R3TRFORMZMEDRUCKN is in repair status. Therefore, it cannot be imported.
System Response
The object is not imported.
Procedure
If you still want to import the object, release the relevant repair andrepeat the import.
Does anybody know something about that problem?
Cheers

Hi,
maybe somebody has already create your form in the productive system. Now you would like to create something already created.
Maybe, you have to check in the TADIR table (key R3TR / FORM / name of the form) if the form already exist. What is the system source for the form. (in the PROD)
And finaly, you can go to the SE03, select the first line and execute (to find object R3TR FORM ..) in all the request order. That will show you who has play with this form, and if a request was lost between DEV & PROD. (in the DEV)
Rgd
Frédric
Message was edited by: Frédéric Girod

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

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

Solman 7.1 LVSM Product system has no technical system assigned

Similar Messages

Maybe you are looking for