Inactive DataSource in Production System

Hi Experts,
I have a situation where DataSource inactive once I initialise infoPackage.we transported from Development to Production and it was active (green) in Production System.I tried to initialise infoPackage then I got the message
DataSource 2LIS_13_VDITM must be activated.How can I resolve the issue.Please throw some light on this issue.I am in a position like golive soon.your help will be appreciated and awarde

Hi,
1. Replicate the datasource at Application component Level. i.e. If your datasource is in an application component say, BW then right click on the application component "BW" and select "Replicate Metadata".
2. If you have transfer rules then activate them with program "RS_TRANSTRU_ACTIVATE_ALL".
SE38 -> RS_TRANSTRU_ACTIVATE_ALL, if you are not able to do it, ask help from your basis to do it, they will have option to do changes directly in prodution itself.
Also chk Note 1056060 - DataSource: Reactivation in the production system
Hope this helps,
Regards
CSM Reddy

Similar Messages

Inactive Transformations and DataSources in Production System.

Hi Experts
We are working on BI 7.0 engine within Solution Manager.
We had some issues with DataSources initially while transporting BI Objects from Devp to Prod. We logged it into OSS and followed their procedure to redo the transports.
In the process, the issue was resolved but 2 New Transformations are created one for each Data Model (since I have only 2 InfoCubes) automatically and is the working model now.
Actual Transformations from Devp became Inactive in Prod and also there are 2 Inactive DataSources which are also from Devp. 2 New DataSources are again from Devp.
When I tried to Delete these unwanted Objects from Prod (I asked the Basis to Open Prod for me though this is not the best practice), it is asking for a Request ID. Also, since the Project has Gone Live already, I am scared if I might disturb the Production System.
Kindly, advise what best could and needs to be done.
Thanks,
Chandu

Initially, we implemented BI-HR module with standard content, which 3.x content (transfer / update rules)... in parallel we also did transformations & DTPs (BI 7.0 model).
Since, client wasn't sure with conversation of transfer rules (has lots of routines) to transformations & DTPs . So we transported both the models to prod sys... We created daily load process chains with transformations & DTPs... The actual plan was, if PC loads fails, then to go for manual loads of 3.x model...Fortunately 7.0 models was successful...
Then one month later, we deleted those transfer / update rules and 3.x datasources from prod sys, on the weekend (process chains runs only week days) without any issues...
We captured those deletion requests and deleted them from SE09 by unlocking them in SE03.

Inactive infoobjects in Production system

Hi All,
I have started the transportation from BI dev to BI production and I am facing a problem all the objects are inactive in BI production while as those objects are active in BI dev.
I cannot use infoobject activation program in production and niether I can do it manually.
I will appreciate your replies.
Let me tell you this is fresh transport and only first unassigned infoobjects were transported.
Regards
Rahul Bindroo

Hi Rahul,
Any message after transport?
Did you replicate your R/3 data sources first before transporting anything. I think you need to replicate r/3 datasources first and than try others. Replicate datasources going to your BW server RSA1->Source Systems and replicate.
Here are the sequence I maintain for transporting but different people do differently. I find it very helpful transporting staffs piece by piece so that if there are any errors, I can solve the problem easily.
BW Transport Sequence:
Info Object Transport only infoobject.
Info Area
Info Catalog
Cube & ODS togather
Multi-Provider/Multicube -
Infoset
Transfer /Update Rules
Role and Authorization
Report
Workbook
Hope it helps..

Transfer rules are inactive in BW Production system

The transfer rules are inactive in BW(Production) for the datasource 0FI_GL_4. I tried to activate by executing a program "RS_TRASNSTRU_ACTIVATE_ALL" and another option by moving transport request from Quality to production( I have done the replicate datasource as well). In the quality system the data flow is ok to ODS(0FIGL_O02). but in Production not able to activate the transfer rules. please suggest me the best practice.
Regards,
Leo.

Hi,
Whenever we get such an error, we first need to check the Transfer Rules (TR) in the Administrator Workbench.
Check each rule if they are inactive. If so then Activate the same.
You need to first replicate the relevant data source, by right click on the source system of D/s ->Replicate Datasources.
Now execute the following ABAP Report Program u201CRS_TRANSTRU_ACTIVATE_ALLu201D.
It asks for Source System Name, InfoSource Name, and 2check boxes. For activating only those TR/TS which are set by some lock, we can check the option for u201CLOCKu201D. For activating only those TR/TS which are Inactive, we check for the option for u201COnly
Inactiveu201D.
Once executed it will activate the TR/TS again within that particular InfoSource even though they are already active.
Regards,
Suman

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

SOAP Receiver Channel 2 nodes inactive in Production system

Hi All,
We are facing an issue with the SOAP receiver channels in production system. There are 4 nodes which can be seen in the communication channel monitoring and out of which 2 have the status as inactive and the short log says "inactive or never used".
But the same nodes are active on the sender SOAP channel and all other channels.We have also checked the Status of the SOAP service that is also set to active.
Now when the server (App server5 in our case) is switched off, which has the 2 active nodes, the messages are not processed since the nodes on the other server are inactive.
Request you to please help us out in finding out why the nodes are in inactive status only for SOAP receiver channels. Do we need to change any settings at the adapter engine level.
Thank you.
Regards,
Sarvesh Desai
Edited by: Sarvesh Nispat Desai on Aug 25, 2010 5:25 PM

There is an error in reporting the status of SOAP channels. This error has already been fixed by SAP and is available as a fix in higher releases (PI 7.10 and above, latest SPs) .
The status "inactive or never used" is shown in channel monitoring at the following two times:
1. After creating a new SOAP channel (sender/receiver) till this channel processes any new message.
2. After the PI system is restarted, all the SOAP channels show this status, though they are ready to handle any incoming/outgoing messages. The channels continue to display this status till they process any new message.
In both these situations, the SOAP Channel can handle/process messages successfully. So, kindly ignore this channel status ("inactive or never used") reporting error in channel monitoring. This will not at all hamper the normal functioning of the SOAP channels.
Hope this answers your query.

How to make inactive ABAP Program in production system

Dear Expert,
I have a lot abap program in production system which are not used anymore and my company plan to upgarde our SAP system, therefore to reduce the effort for the SAP upgarde I will deactivate the unused ABAP program.
My question how to change the active abap to inactive in production system ?
Thank you in advance.
Best regrads,
Tjandiagung

Program details are stored in the table REPOSRC.
Primaray keys are PROGNAME and R3STATE.
Suppose if the program zxy is in active state, then enry will be
ZXY A
Suppose if we made some changes to it and saved, so the program is in inactive state. so one more entry will be there in the table
ZXY A
ZXY I
So if you add like this for the program which you want in the table REPOSRC, then that programs will be in inactive state.
Regards,
Nikhil

To find the list of Inactive objects in the Production system.

Hi Experts,
Need a help. I want to find the List of inactive objects in the Production system. Do we have any standard program or any transcation code to find.
Appreciate your help.
Thanks,
Venkata.A

Check below threads -
Check Inactive Objects in System
Need program to find the inactive objects
Tcode for finding out the inactive BI Objects

Display Datasource in Source System -- connects to Production ERP

Hello,
We have performed a System Copy of BI Prod. In the copied system on one of the Generic DataSource (ZBIP_VKDFSEXT) when I right click and say "Display Datasource in Source System", it is connecting to Production ERP, supposedly it must be connecting to Dev ERP.
I have tested RFC COnnections and Logical System Settings in WE20 and 21, but they are pointing to DEV ERP.
Correct replies appreciated.
Thanks
SM
Edited by: SM on Jul 9, 2011 5:32 AM

Dear SM,
I guess we have faced same kind of issue earlier,
at that time we just removed RFC connection between production system because we are not using Production system connection any more.
and then just clicked on connection parameter of source-system, there we defined new RFC destination.
Hope it will solve your issue.
Regards,
Ashish

Error while transporting Datasources in Production

Dear All,
I have facing a problem while transporting objects pertaining to BI Cockpit in Production.
Earlier I had transported all the obects (in more than one transports) in Quality (from Development). After testing the objects, I had imported the same number of transports (and in the same order) to Production and now some of the requests have ended in errors like:
DataSource 0TCTWHMTFM_TEXT does not exist in source system PW1CLNT003 of version A
Such errors have occured for most of the Datasources.
Can anyone let me know
1) Why the transports have failed while importing in Production when similar requests have been transported successfully to Quality.
2) The possible solution to correct the error.
Request your kind help to overcome this problem.
Regards
Shalabh

Dear All,
Thanks for your kind reply.
There are no R/3 Datasources involved. Our BI Cockpit landscape is based upon only BI system. No data transfer to take place between R/3 and BI.
Secondly, you mean to say that I need to replicate my Source system in Production and then proceed with the transporting of the requests from Dev to Prod.
But I never did the same in Quality while transporting from Dev. Is it that it might have been done in Quality beforehand by someone ?
Also, when the Datasources have not been transported to Production (resulting in error) then how can i replicate these datasources in Production ???
Let me know if I have not understood correctly.
Many thanks again for your efforts.
/Shalabh

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.

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.

Need help with enhanced data source in Production system

Hello Gurus,
1. I enhanced a datasource in BW and populated the field using customer exit using CMOD function. In Dev system, i dont have much data, so I deleted the whole data and did full load.
what shud I do in Production side, so that Delta wudnt be affected??since in production, we have millions of records, we wont do full load., what is the best way to populate the field in production after transporting the datasource to production without disturbing delta's, to reflect the new field for previous years data???
2. can we put 0customer and 0material in the same dimension?? how its going to affect the performance?
Thanks in advance.,
Best Regards,
Pavan

Hi,
Please see this
1.
see this thread
populated the new field with historic data
2. can we put 0customer and 0material in the same dimension?? how its going to affect the performance?
Its better not to use them in a single dimension because one customer and take more than one material so if you have 100 customer and 1000 materials this combination will generate a large number of records. Its always better to keep characteristic which are having 1:N relation ship in one dimensional in you case customer and material will have an M:N type of relationship.which will result in slow performance.
Regards,
Ravi

Re: LOCOCKPIT DATASOURCES IN DEVELOPEMENT SYSTEM

HI
<b>KINDLY READ FULL QUESTION AND CLARIFY.
</b>IN A SYSTEM LAND SCAPE OF DEVELOPMENT-QA-PRODUCTION
EG: IF I AM USING LO COCKPIT -
IF I WANT TO INSTALL A DATA SOURCE FROM R/3 WILL I BE ACTIVATING DATASOURCE IN R/3 DEVELOPMENT SYSTEM R ELSE ON PRODUCTION SYSTEM.
IF I AM DOING THE ACTIVATION ON DEVELOPMENT SYSTEM THEN WHEN WE GO TO PRODUCTION DO I AGAIN NEED TO DO THE DELTA SETTINGS AND SETUP ON PRODUCTION SYSTEM R/3--????
IF I AM EXTRACTING DATA INTO BW DEVELOPMENT SYSTEM, WHEN I TRANSPORT IT TO QA R PRODUCTION DO I AGAIN NEED TO DO SET UP LIKE REPLICATION OF DATASOURCES FROM R/3 TO PRODUCTION SYSTEM BWWHAT IS THE METHODOLOGYKINDLY EXPLAIN IN DETAIL.
SO I AM VERY MUCH CONFUSED. ABOUT WHAT R THE ACTIVITIES I NEED TO DO ON DEVELOPMENT SYSTEM R ELSE PRODUCTION SYSTEM.
KINDLY CLARIFY MY DOUBTS
THANKS AND REGARDS
NEELKAMAL

Hi Neel,
when you install (transaction RSA5) a datasource in DEV you have to put this activation in a change request. The same for Logistic Cockpit delta activation (LBWE).
So, to have the same situation (activated datasource and delta) in QA and PRD.
On the other hand, QA and PRD are not open for any modification, therefore a direct activation is not allowed.
Clearly, when you import your change request (with the related activation), THEN you have to do a replication of the source system in BW (in order to let BW see the updated situation).
Step by step for LO:
activate the datasource in RSA5.
adjust it in RSA6.
activate delta (green light in LBWE)
transport CRs in the other environment (and take care of everything in this case...)
replicate datasource in BW
(remember that setup job and delta init and collective job have to be executed in every environment
Bye,
Roberto

IDOCs error in Production System

Hi Gurus,
In Production system, there is a CRM oppertunities process chain is running on hourly basis, the data was updated to DSO successfully, but for the past one week it was not updating to further processing InfoCube, there is an error.
error: Idoc Ready to be transferred to application.
Please update me step by step procedure.
Thanks

Hi,
Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then checl the Mappings and any routines in BW for that DS, if this is also fine then check the below options.
See Dumps in ST22, SM21 also.
Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.
You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.
S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC
And also check the following things.
1.Connections from BW to ECC and ECC to BW in SM59
2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.
3.Check Dumps in ST22, and SM21.
4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.
5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.
See in SDN
Re: Loading error in the production system
Thanks
Reddy

Inactive DataSource in Production System

Similar Messages

Maybe you are looking for