Convert the logic source system

Hi all,
I have a question related to the transportation.
We have 3 client for DEV(001) QA(002) & PRD(003).
I have packaged a transport request for my cube and related transformation. I also mantained the Conversion(DEV001 -> QA002). I released the transport request and import it into QA. It works fine because the source was changed from DEV001 to QA002.
My question is what the system behavior is if I want to import the same transport request into PRD. can the system automaticly change the source from DEV001 to PRD003? If can't, what should I do?

Hi,
Conversion of system has to be maintained in production system as well .
Once conversion of QA to PRD is maintained , same requests can be transported to PRoduction and system will change ref. of transfer rule from Qa system to PRD system.
Hope that helps.
Regards
Mr Kapadia

Similar Messages

Start Routine to populate the Logical Source System

Hi Friends please help me with the below
1. Requirement : to Populate The system Date , Source System
in BI for Each load request.

1 Solution: I thought of writing the Start Routine for this but it is giving me error
syntax Error: END METHOD MISSING?????
2. Also I have requirement to populate 0sourcsys source system id, can any body help how to populate that.
Thanks
Poonam Roy
ABAP Code.
I have the End Method. what more to do.
METHOD start_routine.
*=== Segments ===
 FIELD-SYMBOLS:
 <SOURCE_FIELDS> TYPE tys_SC_1.
 DATA:
 MONITOR_REC TYPE rstmonitor.

$$ begin of routine - insert your code only below this line -
... "insert your code here

FORM STARTROUTINE
USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TRANSTRU
ABORT LIKE SY-SUBRC.
DATA: ZLOAD_DAT LIKE SY-DATUM
ZZSOURSYS TYPE RSLOGSYS
IF G_S_MINFO-DATAPAKID=1
SOURCE_FIELDS-ZLOAD_DAT = SY-DATE.
SOURCE_FIELDS-ZZSOURSYS = G_S_MINFO-LOGSYS.
ENDIF.
ABORT = 0.
ENDFORM.
ENDMETHOD.
ENDCLASS.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*- to make monitor entries
... "to cancel the update process
 raise exception type CX_RSROUT_ABORT.
$$ end of routine - insert your code only before this line -
ENDMETHOD.

Hi,
Check whether the formula is useful here than Routine. Because you can see the Sy-datum , source system( I Guess) fields as avaialable formula elements .
With rgds,
Anil Kumar Sharma .P

ABAP logical source system

dear all,
how can i get the logical source system using abap into my update rule?

Hello,
I believe is SY-SYSID.
Diogo.

How to retreive logical name for the OLAP source system

dear all, i am writing an extractor for a data source and need to fetch the OLAP SOURCE SYSTEM (r3 backend) for it.
obviously in RSA1, you can see the source system of the data source, however, i have debugged this and could not find the function or class that puts the source system in the field.
in short i have the data source, and i know i want it to be the active version, so how can i get the olap source system of this ?
thanks
glen
Edited by: gingle on Dec 2, 2008 10:22 PM

Try tcode SM59. I am locked out of the transaction at this client, so I can't give you any more details.
You can also look at the source system in RSA1 ... go to the source systems tab and change it.
Both of these steps are typically basis steps, so i would advise you to be cautious when doing anything in either of those screens.
Brian

BDLS for conversion of logical source system name

Hello All,
I am trying to reassign a new source system NEW1 by replacing old source system OLD1 using BDLS in the source system.
But the NEW source system logical system name already exists as I created it . Can I delete the new source system and then use BDLS?
How do I make sure that the reassignment happens correctly?
And what precautions should be taken to avoid further consequences?
Regards,
NIKEKAB

BDLS does a pretty good job... Never had issues with it when using it... Always execute a test run, look for warnings or errors...
Yes, you can delete the source system before doing BDLS... I assume, since it is new, nothing is connected to it...
You always will have to check RFC connections, datasources replicas, rules, etc, once the conversion is done...
Make sure you take a look at note 886102, it has very good information and make reference to other relevant notes specific for BDLS, like 121163, 369759, etc... Read the notes carefully, follow the steps and you'll be fine...
Once everything is done and in place, you shouldn't have any surprises in the future... It's just normal maintenance...
Good luck...

Unable to 'set the default source system' to Install Business Content

Hi,
Maars here. This is my first post hoping that in future ones I'll also be lending a helping hand.
I am trying to 'Install Business Content' under the BUSINESS CONTENT section in txn RSA1. I am doing this after 'Transfer Data Sources' in R/3 and I can now see all the data sources (under the application component hierarchy) for the source system. But I am not able to see the Info Objects in the Business Content.
When I try to set R/3 as the default source system (got this screen after clicking a icon in the standard tool bar), BW is not saving the settings ie., I set the R/3 as the default and then click on OK. If I go back to the same screen again, I find that my settings were NOT saved.
Could you please help me out?
Thank you.

Hi,
It seems to be a bug in version 3.5.
Do like this:
After you open the screen to choose the dafault source system
Clcik on 3rd button(F6) available in the bottom of the scrreen.
And then select teh tick mark for required system.
And then click on Continue button
You have do this step before you drop the cube to right side of the cube.
Ok, even after all these steps , if you reopen the screen you would not see Tick mark u have done just before. DONOT WORRY ABT it.
Drag and drop required cube with dat flow before.
Now you can see the Transfer rules with selected Source system only in the collected Objects.
With rgds,
Anil Kumar Sharma .P

How do I register as a developer in the Online Source System?

Im trying to add an ABAP program to SAP BW, and I get this message:
You are not registered as a developer.
Please register in the Online Source System (OSS).
In the OSS you will receive an access key.
I have no idea what this means. How do access the OSS and do this? I have done various searches on SAP's site and I've not found anything useful.
Is there any shortcut I can use to get this access key and proceed with work? I'm on a tight deadline?

> Well , you should speak to your Team Lead and request for ABAP Developer Access Key.
> Your Tem Lead will request BASIS guys to generate an Access Key for you.
> Once you receive your access key, try to create a program in SE38 > It will prompt you to enter Access Key. > enter the generated access key and continue.
Cheers
Praveen

G/L account picked for the "wrong" source system entry

Dear Experts,
in SRM 7.0, Classic Scenario, i am facing the following issue with respect to G/L account determination in the SC:
We have three R/3 systems connected to SRM. All these R/3 systems use the same Material Groups, but the G/L accounts are different in each R/3 system.
In the Table "Determination of G/L Account using product categories", i have maintained the repsective combinations. For each combination of product category and account assignment category, the respective G/L account is defaultet for the respective source system.
But in the shopping cart, the determination of the correct G/L does not always work. When a user enters the shopping cart initially with a line item that is accounted to his default account assignment category, than the correct G/L account for his source system is derived. But if he changes the account assignment category of the line item, than a G/L account from a "wrong" source system is getting picked up from the table.
I have checked the GUIDs of the product categories between "Comm_category" and "bbp_det_account" and they are correct.
What can be the reason for the picking of the G/L account from the wrong source system?
Can the note 1357871 bring the correction?
Thank you very much!

Hello Dima,
I think your problem comes from your source system for product category management.
Could you clarify one point: if you change account assignment category, does new G/L account have to be determined for same backend system too or not ?
If yes, correct new G/L account will be determined using your customizing (IMG: SAP Implementation Guide > SAP Supplier Relationship Management > SRM Server > Cross-Application Basic Settings > Account Assignment > Define G/L Account for Product Category and Account Assignment Category ).
If it does not work, log an OSS message.
If no, you need to switch value for each SC item field BBP_PDIGP-LOGSYS_FI from old backend source system to the new one. For this, use BBP_DOC_CHANGE_BADI.
Then, your customized G/L account definition for product category and account assignment category should be OK.
Regards.
Laurent.

Not converting the logical system through BDLS

Hi Experts,
I did the system copy of BI system from production to developemnt
To change the logical system in RSA1 --> Source systems
I have choose client role as test in scc4 and in tcode BDLS i have given the old logical system name new logical system name
after completing the job RBDLSMAP i checked in the RSA1 there is no change in logical sytem
i got the following message
SM37 log
Job started
Step 001 started (program RBDLSMAP, variant &0000000000005, user ID ABCD)
Logical system name ABC500-1 does not match SAP's recommendation
Job RBDLSMAP no longer exists
Converted table: 'RSSTATMANSTATUS'; number of changes: ''
Converted table: 'RSSTATMANSTATDEL'; number of changes: ''
Converted table: 'RSSTATMANREQMAP'; number of changes: ''
Converted table: 'RSSTATMANREQMDEL'; number of changes: ''
Converted table: 'RSSTATMANPSA'; number of changes: ''
Converted table: 'RSMDATASTATE_EXT'; number of changes: ''
Job finished
Spool log
Table Name                Field Name       Number of Relevant Entries    Number of Converted Entries
/BI0/ABP_CUST00*          LOGSYS                              0                              0
/BI0/ABP_CUST40*          LOGSYS                              0                              0
/BI0/ABP_VEND00*          LOGSYS                              0                              0
/BI0/ABP_VEND40*          LOGSYS                              0                              0
/BI0/ACDS_DS0400*         LOGSYS                              0                              0
/BI0/ACDS_DS0440*         LOGSYS                              0                              0
/BI0/ACDS_DS0500*         LOGSYS                              0                              0
/BI0/ACDS_DS0540*         LOGSYS                              0                              0
/BI0/ACLM_DS0300*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0340*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0600*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACLM_DS0640*         CLM_FISY                            0                              0
                          LOGSYS                              0                              0
/BI0/ACRM_CMGL00*         LOGSYS                              0                              0
/BI0/ACRM_CMGL40*         LOGSYS                              0                              0
/BI0/ACSM_LINK00*         LOGSYS                              0                              0
/BI0/ACSM_LINK40*         LOGSYS                              0                              0
/BI0/AGN_BP00*            GN_PAR_LSY                          0                              0
/BI0/AGN_BP40*            GN_PAR_LSY                          0                              0
/BI0/AGN_CONV00*          LOGSYS                              0                              0
/BI0/AGN_CONV40*          LOGSYS                              0                              0
Could any body help me in this
Thanks & Regards,
Arun

Hi experts,
I have done the system copy form Production to Developement.
Transfermations and DTP(Data transfer process) are still connected from Produciton R3 which should be from developemnt R3.
I have tryied to change the logical sytem name through BDLS. But the logical system name is not changed
i got the job log which is in above conversation in my thread.
Please let me know how to change the logical system name in Transfermations and DTP in RSA1
Thanks & Regards,
Arun

How to change the ECC Source system in SAP BI

Dear Experts,
In my BI development system instead of showing ECC development system as a source system it is showing ECC production system.
Now in my BI system I want to change the source system from ECC Production to ECC development.
Kindly explain me step by step to change the source system from ECC Production to ECC development.
Regards,
Suresh.

Hi,
Ask your basis team to change source system entries.
They knows how to assign logical mappings.
Tx - BDLS.
Tables - RSLOGSYSMAP.
Try this way.
Bw, Tx - RSA1-->source system, Menu Tools - Conversion of logical system name and Assignment of source system to source system ID.
Thanks

ABAP CODE TO POPULATE LOGICAL SOURCE SYSTEM

Hi Friends please help me with the below
1. Requirement : to Populate The system Date , Source System
in BI for Each load request.
1 Solution: I thought of writing the Start Routine for this but it is giving me error
syntax Error: END METHOD MISSING?????
2. Also I have requirement to populate 0sourcsys source system id, can any body help how to populate that.
Thanks
Poonam Roy
ABAP Code.
I have the End Method. what more to do.
METHOD start_routine.
*=== Segments ===
FIELD-SYMBOLS:
<SOURCE_FIELDS> TYPE tys_SC_1.
DATA:
MONITOR_REC TYPE rstmonitor.
$$ begin of routine - insert your code only below this line -
... "insert your code here
FORM STARTROUTINE
USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TRANSTRU
ABORT LIKE SY-SUBRC.
DATA: ZLOAD_DAT LIKE SY-DATUM
ZZSOURSYS TYPE RSLOGSYS
IF G_S_MINFO-DATAPAKID=1
SOURCE_FIELDS-ZLOAD_DAT = SY-DATE.
SOURCE_FIELDS-ZZSOURSYS = G_S_MINFO-LOGSYS.
ENDIF.
ABORT = 0.
ENDFORM.
ENDMETHOD.
ENDCLASS.
*-- fill table "MONITOR" with values of structure "MONITOR_REC"
*- to make monitor entries
... "to cancel the update process
raise exception type CX_RSROUT_ABORT.
$$ end of routine - insert your code only before this line -
ENDMETHOD.

You have to write the code (in BI/BW) in the transfer rule (between Datasource transfer structure and infosource/info object)
There the FORM begin with
[code]USING RECORD_NO LIKE SY-TABIX
 TRAN_STRUCTURE TYPE TRANSFER_STRUCTURE
 G_S_MINFO TYPE RSSM_S_MINFO
CHANGING RESULT TYPE /BI0/OIPERSON
 G_T_ERRORLOG TYPE rssm_t_errorlog_int
 RETURNCODE LIKE SY-SUBRC
 ABORT LIKE SY-SUBRC. set ABORT <> 0 to cancel datapackag[/code]
GS_MIN_INFO structure RSSM_S_MINFO contains information on the request being processed.
G_S_MINFO. This passes technical information about the data load request,
such as requesting user, request date and time, update mode, the handling of
duplicate records, error handling flags, parallel processing flags, and what data
targets to update.
If tou want to use start-routine for optimization reasons and fill an empty field in transfer structure, the structure G_S_MINFO is available too.
[code]USING G_S_MINFO TYPE RSSM_S_MINFO
CHANGING DATAPAK type TAB_TRANSTRU
 G_T_ERRORLOG TYPE rssm_t_errorlog_int
 ABORT LIKE SY-SUBRC. set ABORT <> 0 to cancel datapackage[/code]
And stay in FORM between limits :
[code]$$ begin of routine
$$ end of routine[/code]
Update RESULT in first case, and field(s) of DATAPAK in second case.
[code]RESULT = G_S_MINFO-LOGSYS.[/code] or
[code]LOOP AT DATAPAK INTO l_s_datapak_line.
l_s_datapak_line-zzsourcsys = G_S_MINFO-LOGSYS.
MODIFY DATAPAK FROM l_s_datapak_line.
ENDLOOP.[/code]
Regards

Datasources . problem with the new Source System

Hi friends!
The ECC client were copy and now I have a new source system for this.
If I select source system / verify, the msg is: ok
In can read some data from the new ECC (ie: exchange rates updated), but I can not read any records using the datasources.
The replication in Bi were done, and the data in source system is ok.
-> What is wrong?
Thanks!

Check the profile parameters in WE20,We21... and also check scc4

Transport of Infopackages didn't change logical source system

Hi
I have transported a good number of process chains to test. However the infopackages are not visible in out test system. I looked in table RSLDPIO using options 'Active' and logical system 'testERP111' and they wern't there.
However, when i try the selection 'Active' and 'devERP111' they are there.
SO this means that the logical system name conversion hasn't worked. EVen though we have have the conversion devERP111 > testERP111 set up in the conversion of logical system names.
We have many clients (111, 112 113) on our system so the conversion is something wheich is always checked as part of transporting.
Any ideas why and how to solve it??

Along with that process chains, U should also transport infopackages / DTPs existing in that process chains.
In test system, u can check table RSPAKPOS for the infopackages. If the infopackage is does not exist in that table, u should transport the same to test system.

Transfer rules to the new source system not visible in Transport connection

Dear All,
Recently our source system has been changed from R3 4.7 to ECC 6.O. Corresponding to that all the activities in BI have finished successfully. All my datasources in 4.7 have been replicated in ECC 6 in BI and transfer rules re-assigned. I have also collected them in a Transport request.
Now when I am checking the entire flow in Transport connection, it shows me the transfer rules pointing to the old system only. That is, in RSA1 it shows the new system assignment. But in Transport connection not.
What I have to do so that I can crosscheck in Transport connection all my objects having transfer rules to new system ?
Regards,
Srinivas

I think you should check the source system assignment in the transport connection. It might have directed to the old sytem.
Cheers
Chanda

How to handle the online source system in ETL

Hi gurus,
I have a source table which changes very dynamically
For ex :
Lets say source Table A has 10 million records set which I am trying to insert/update via OWB in staging table(takes fifteen minutes to insert/update them).
During these fifteen minutes of processing ,the existing source table records gets updated and some new records get inserted
How do i identify/ handle such a situation of loading the data on to staging with an online source.
Could you please guide me on this
BR
Sridha
Edited by: sridha on Sep 5, 2010 11:53 PM
Edited by: sridha on Sep 5, 2010 11:54 PM

Hi Sridha,
If your source database is on Oracle, maybe the best way is to use Oracle Streams (Change Data Capture implementation on Oracle):
http://download.oracle.com/docs/cd/E11882_01/server.112/e17069/strms_over.htm#i1006135
For non-Oracle source database and if you use OWB10g R2 you can try to use CDC code templates:
http://download.oracle.com/docs/cd/E11882_01/owb.112/e10582/code_templates.htm#CHDHGGGI
Regards,
Oleg
Edited by: Oleg2 on - corrected link to Oracle Streams overview

Convert the logic source system

Similar Messages

Maybe you are looking for