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.

Similar Messages

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

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

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...

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.

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

To refer logical source in update rules

Hi,
I wanted to find the logical source system using abap into my update rule, is it possible.
Help would be appreciated.
Thanks,
SD

Hi,
you have only to write something like this:
case sy-sysid.
* development system
    when 'dev1'.
        result = 'r3_dev'.
* test system
    when 'test1'
        result = 'r3_test'.
endcase.
dev1 and test 1 are your bi systems. When data comming from one source system you can use this code in each transformation.
Regards
Andreas

Creating Source System in BW

Hi Friends,
We are using BI, i have to create a source system(R3) in BW.
Both sides we have users with enough profiles.
In RSA1 --> Source System --> Create is using to create the sourse system.
I am using automatic function at the time of defining the source system.
It is asking some dialog user from source side, i am giving some dialog user
then i am getting the error user cannot create in source system.
Could you please help me out.. how to create R3 source system in BI.
Thanks in advance
Srinivas

Hi Srini,
                Check u'r partner profiles.if u din't get....
plz follow this....
2.1     SAP R/3
2.1.1     Define Client Administration (SAP R/3)
Use
This activity allows you to change Customizing settings.
Prerequisites
You have logged on to the system in English in order to start with the installation of the Best Practices Scenario.
Procedure
Run the following activity:
SAP R/3 Role Menu     Define Client Administration (SAP R/3)
Transaction Code     SCC4
SAP R/3 Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
Then carry out the following steps:
1.     Choose Display  Change.
2.     Confirm the warning message Caution: The table is cross client.
3.     Select your SAP R/3 client and choose Details.
4.     In the Change View Clients: Details screen, activate the following settings:
     Automatic recording of changes
     Changes to Repository and cross-client Customizing allowed
     eCATT and CATT allowed.
5.     Save.
6.     Go back to the SAP Easy Access menu.
2.1.2     Defining a Logical System for SAP R/3 (SAP R/3)
Use
The purpose of this activity is to create a logical system for your SAP R/3 System. To enable communication between systems within your system landscape, you must
1.     Define the systems as logical systems.
2.     Assign the logical system for the SAP R/3 System to a client.
This enables the systems to recognize the target system as an RFC destination. If the logical system has already been created, skip this activity.
Logical systems are defined cross-client.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Defining a Logical System for SAP R/3 (SAP R/3)
Transaction Code     SPRO
SAP R/3
IMG Menu     Basis Components (for R/3 Enterprisse: SAP Web Application Server)  Application Link Enabling (ALE)  Sending and Receiving Systems  Logical systems  Define Logical System
2.     Choose New entries.
3.     In the column Log System, enter a name for the logical system that you want to create.
4.     In the column Name, enter a description of the logical system.
Log. System     Name
where      XXX is the system name
and      NNN is the client.
5.     Save your entries.
A transport request for Workbench appears.
6.     Select an existing request or create a new request, if necessary.
A transport request for Customizing appears.
7.     Select an existing request or create a new request, if necessary.
2.1.3     Assigning Logical System to Client
Use
The purpose of this activity is to make an assignment for the logical system. Skip this activity if a logical system is already assigned to your client.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Assign Logical System to Client
Transaction Code     SCC4
SAP R/3 Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
2.     Choose Display ® Change.
3.     Confirm the warning message The table is cross client.
4.     Select your R/3 client and choose Details.
5.     Enter the name of the logical system of your SAP R/3 client.
6.     Save and confirm the warning message Be careful when changing the logical system.
7.     Choose Back twice.
2.1.4     Creating an RFC User (SAP R/3)
Use
To enable communication between the SAP R/3 back-end system and the SAP SCM System, you have to create an RFC user in the SAP R/3 System.
The RFC user in the application client enables multiple RFC connections. Skip this activity if an RFC User has already been created.
Procedure
Carry out the following steps:
1.     Access the transaction using:
SAP R/3 Role Menu     Creating an RFC User (SAP R/3)
Transaction Code     SU01
SAP R/3 Menu     Tools  Administration  User Maintenance  Users
2.     In the User field, enter RFCUSER.
3.     Choose Create.
4.     On the Maintain User screen, enter the following data on the Tab entry screens:
Address
Last Name
Function
Logon data
User type     System
Password     LOGIN
Profile
Profiles     SAP_ALL
SAP_NEW
S_BI-WX_RFC
Defaults
Logon Language     EN
5.     Save your entries.
2.3     SAP BW
2.3.1     Define Client Administration
Use
This activity defines changes and transports of the client-dependent and client-independent objects.
Procedure
1.     To perform this activity, choose one of the following navigation options:
SAP BW Role Menu     Local Settings ® Define Client Administration
Transaction Code     SCC4
SAP BW Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
2.     Switch to change mode.
3.     Select your client.
4.     Choose details.
5.     In field Currency enter the ISO-code of the local currency, e.g. USD or EUR.
6.     In field Client Role enter Customizing
7.     Check the settings for changes and transport of client-specific objects and client-independent object changes
If you want to use the settings made by BC-Sets or manually in other systems (other than BW), Automatic recording of changes and Changes to Repository object and cross-client Customizing allowed is required.
Result
Client administration has been defined to support the installation using Best Practices.
2.3.2     Defining a Logical System for SAP BW (SAP BW)
Use
In this step, you define the logical systems in your distributed system.
Prerequisites
Logical systems are defined cross-client. Therefore cross-client customizing must be allowed in your client (this can be checked in transaction SCC4).
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu     Defining a Logical System for SAP BW (SAP BW)
Transaction Code     SPRO
IMG Menu     SAP Reference IMG  SAP Customizing Implementation Guide  SAP NetWeaver  Business Information Warehouse  Links to other Systems  General Connection Settings  Define Logical System
1.     A dialog box informs you that the table is cross-client. Choose Continue.
2.     On the Change View Logical Systems: Overview screen, choose New entries.
3.     On the New Entries: Overview of Added Entries screen enter the following data:
Field name     Description     R/O/C     User action and values     Note
Log. System     Technical Name of the Logical System          Enter a name for the logical BW system that you want to create
Name     Textual Description of the Logical System          Enter a clear description for the logical BW system
4.     Choose Save.
If a transport request for workbench and customizing is displayed choose existing requests or create new requests.
If you want to continue with the next activity, do not leave the transaction.
Result
You have created a Logical System Name for your SAP BW client.
2.3.3     Assigning Logical System to Client (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW
Role Menu     Assigning Logical System to Client (SAP BW)
Transaction Code     SCC4
SAP BW Menu     Tools  Administration  Administration  Client Administration  Client Maintenance
1.     In the view Display View "Clients": Overview, choose Display.  Change
2.     Confirm the message.
3.     Select your BW client.
4.     Choose Details.
5.     In the view Change View "Clients": Details, insert your BW system in the Logical system field, for example, BS7CLNT100.
6.     Save the entries and go back.
2.3.4     Opening Administrator Workbench
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW     Modeling  Administrator Workbench: Modeling
Transaction Code     RSA1
1.     In the Replicate Metadata dialog box, choose Only Activate.
2.     If a message appears that you are only authorized to work in client ... (Brain 009) refer to SAP Note 316923 (do not import the support package, but use the description under section Workaround).
2.3.5     Creating an RFC-User (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options:
SAP BW Role Menu     Creating RFC User
Transaction Code     SU01
SAP BW Menu     Tools  Administration  User Maintenance  Users
Then carry out the following steps:
1.     On the User Maintenance: Initial Screen screen:
a.     Enter the following data:
Field      Entry
User     RFCUSER
b.     Choose Create.
2.     On the Maintain User screen:
a.     Choose the Address tab.
b.     Enter the following data:
Field     Entry
Last Name     RFCUSER
Function     Default-User for RFC connection
c.     Choose the Logon data tab.
d.     Enter the following data:
Field     Entry
Password     LOGIN
User type     System
e.     Choose the Profiles tab.
f.     Enter the following data:
Field     Entry
Profiles     SAP_ALL , SAP_NEW and S_BI-WHM_RFC
g.     Choose Save.
Do not change the password of this user as it is used in RFC connections.
2.3.6     Define RFC-USER as default (SAP BW)
Procedure
To carry out the activity, choose one of the following navigation options
SAP BW Role Menu     Define RFC-USER as default (SAP BW)
Transaction Code     RSA1
SAP BW Menu     Modeling  Administrator Workbench: Modeling
1.     On the Administrator Workbench: Modeling screen choose Settings  Global Settings.
2.     In the Global Settings/Customizing dialog box choose Glob. Settings.
3.     On the Display View RSADMINA Maintenance View: Details screen:
a.     Choose Display  Change.
b.     Enter RFCUSER in the BW User ALE field.
c.     Choose Save.
Leave the transaction in order to activate the entries you have made.
3.3.2     Creating the Source System in the Administrator Workbench
Procedure
1.     From the SAP Menu in the BW system, choose:
SAP BW Role Menu     Creating the Source System in the Administrator Workbench
Transaction code     RSA1
SAP BW Menu     Modeling  Administrator Workbench: Modeling
2.     Choose Modeling.
3.     Choose Source Systems.
4.     In the right-hand window mark Source Systems.
5.     Choose the context menu (right mouse click).
6.     Choose Create.
Field name     User action and values
File System, Manual Meta Data, Data Using File...     X
7.     Choose Enter.
Field name     User action and values
Logical source system      FILE
Source system name     File system
8.     Choose Enter.
9.     Choose Back.

Problem Activating Source system RSAR 374, RSAR 375

Hi all,
Hoping you can help me with this issue. I have two
systems,one R/3 4.7 system and another BW 3.0B system.Both are recently installed. created user in client 800 on R/3. created user in client 100 on BW. i established RFC destination between both, Logical source system assignments and definitions of logical source systems on both. They are working correctly, But i couldnot succeed in creation of the source system. it gets created but it is not activated and ends with the following errors.
Message and the id next to it
1) The following errors occured in the source system. RSAR 374.
2) Result of the destination check: timeout . RSAR 375 .
when i try to activate it by right clicking on it , it does give these errors and activation gets terminated.
Can anyone pleaseeeeeeeeeeee with this. Thanks a lottttttt........
kishore karnati

Hi Kishore and Edwin,
I have exactly the same problem described here, except I am creating an ECC 6 source system in BI 7.
Therefore, I am wondering if you guys can elaborate on your experience.
I get the same error message RSAR 374 and RSAR 375.
I did both connection and authorization tests for the RFC in SM59 and it's OK.
What do you mean by the "basic concept of BWREMOTE AND ALEREMOTE background users."???
Please advise.
Cheers,
SJ

Source system in Production doesnt exists Error RC- 8

Hello experts!
We connected a second source system to our 7.0 BW. We transported from development to quality system and everything is fine. Now we want to transport to production and we got RC=8 and the message that our "source system does not exist"
First we checked our source system. It is ok. we can replicate datasources, load units and currencies. But when we want to transport something what is directly connected to the source system we got everytime a RC=8 because of source system. For sure, we checked our "Conversion of logical source systems names". We checked if the mapping from development to productive is correct many times but we can find no error.
Is there something I can not see?
I tried to transport Transformations, DataSource Migration, other things connected to 7.0 and 3.x DataSources. Nothing works. I transported a transformation got a little different error like no rules exist because missing infoobjects in source or target or they are not activated. But target seems to be ok and source also have the fields.
Also I have searched the previous threads I have got what I have done but for sure some thing I am missing !!
Any Ideas???
Best regards,
Yash

Thanks Murali for your prompt reply,
I have manged to do the conversion settings again and now the source system client problem subsides !!!
But when I import the requests again from QA to PRD it says that some DS cannot be activated due to inconsistency in CRM production system. Actual message is.
Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
Mapping between data source 0CRM_SRV_CONTRACT_H and source system PC4CLNT400 is inconsistent
Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Activation Mode)
InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active, total of 4 inactive InfoObjects
InfoObject Exchange Rate Date ( 0CRM_EXCDAT ) is not active
InfoObject Exchange Rate Type ( 0CRM_EXCTYP ) is not active
InfoObject Quotation GUID ( 0CRM_QUOGUI ) is not active
InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
is that due to the DS .. some are in BI 7 cannot be mapped with 3.X ?
I will be importing a new request all the way from DEV to QA and Then in PRD as of now to see the inconsistency once again.
Cheers
Yash

Conversion of source system names after transport

Hi gurus,
Please someone can tell me how to configure the "conversion of source system names after transport" in the BI system as my transport is not working on a new BI System ?
Thx in advance

Hi Firmin,
You can do this in RSA1 in tools under conversion of logical source system names.
Here you maintain the development system or the system used for development as the source system.
You will have to mention the logical name of the development system.
In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
Check the folllowing link for more informationn on this.
[Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
Hope it helps you ,
Best regards,
Sunmit.

Assign Source System to Source System ID

Hello Experts,
I am loading master data from flat file (which is an export from another BI system Info Object) in which one of the attribute is SourceSytem ID (0SOURSYSTEM). But in the flat file some of the records for this particular attribute are blank and some are with R3. So the records which are without any sourcesystem ID are not getting loaded.
Error is as follows: No source system ID exists for source system (logical system) FLAT_FILE.
Detail Error: Procdure: Assign source system ID to logical source system FLAT FILE. To do this go to TOOLS--> Assign source system to source system ID from main menu of DWB.
Can anyone tell me what exactly I need to give at this place. Any two digit char or do I need to contact basis to follow any specification?
Thanks for your time.
Experts please let me know how I can proceed loading flatfile data which i got from another BI system.
Edited by: saptrain on Apr 5, 2010 7:52 PM
Edited by: saptrain on Apr 5, 2010 7:53 PM
Edited by: saptrain on Apr 5, 2010 7:53 PM
Edited by: saptrain on Apr 5, 2010 11:07 PM

Hi,
What exactly does this attribute does while reporting?
Usually if you have 2 source system then this attribute is used to differentiate between to source systems. You have to use this is report to restrict to particular source system
I am assuming it will just differentiates the data that we loaded either from R/3 or FF or something else. Is that right?
Yes, You are right
Apart from that is there anything useful in reporting point of view?
Everything is based on reporting. Mostly you will use this when you are having two source systems. Ex: ECC and CRM for 0BPARTNER info object
It doesnt matter if I give any two chars(as u said) right?
No it doenst matter. You have button called something "Suggest ..." you can use that. Other wise you can give your own name
thanks
Srikanth

Test System (BQ1) Objects showing up wrong Source System after Transport.

Hi Experts,
We are working on IS-U BI7.0 Project. We have finished with our Development and have transported the DataSources, Transformations and DTPs from Development (BD1) into Test (BQ1) Systems.
We have entered values in the Conversion of Logical Source Systems correctly.
When we select the DataSource and Click Object Directory Entry from the Extras Menu, we found that the Original Source System is defined as BQ1 instead of BD1 (Development System), which is where the Object is getting Transported from.
We have implemented an SAP Note:1008633 (Incorrect Source System after Transport (RSTRAN 514) but couldn't resolve the issue.
We basically want all the Objects in the BQ1 (Test System) showing the Original Source System as BD1 (Development System) but only the DataSources and it's connected Transformations and DTPs are originating from the BQ1 (Test) System itself (The Transformations when Transported from BD1 to BQ1 are Transported with a different Technical Name which is very strange).
Had anyone faced similar problem and if so, what was the effective solution implemented.
Any help in this regard is very much appreciated.
Thanks in Advance.
Best Regards,
Chandu.

It is resolved by our Basis.
Thanks,
Chandu

Change Source system Tech.Name

Production : PRE -
> PRB
PRE-Production : PPE -
> PRE
We make a copy of our production BI to Preproduction BI (PPB) we follow note # 886102. We want to connect this system to our pre production ERP (PPE).We already run BDLS change the logical system name we created new RFC created which is pointed to new R3 system .Problem is when we are going to run Tcode RSA1 in source system it shows old Tech name PRE600. We are unable to activate the source system.
We can create new source system (PPE),but All our BI objects mapped with old source System (PRE600). I am afraid to change thousands of BI objects ( change source system from PRE600 to PPE600).
Is there any work around we can change the Logical Source system Tech.Name? or some batch job which change the source system name for all BI objects.
Appreciate your earliest reply.
Nawab

Hi
Can you please check the Tcode BDLS
Check the document it will be helpful
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
Regards

Source System conversion for several production SAP

Hello all,
What kind of customizing in table RSLOGSYSMAP i have to do ?
We have 1 DEV and 9 production system P01, P02, .... P09.
In the table i must insert 9 lines, one for each production system ?
DEV -> P01
DEV -> P02
DEV -> P09
Or i insert only one line
DEV -> P0X
and i change the table before each of the nine transport ???
I have to transport the same order 9 times ?
Thanks for your precious help.
Christophe

Cristophe,
I think this must be done on the target system where you will mention the source and target fields .
You do not have to manually enter the values into the table - you can find this under source system conversion defined in the transport connection .
I think the source system just gives it current logical systems and then the target system will do the conversion and hence it will not be 9 entries in your DEV environment but 1 entry each in your productive environment.
Also you cannot have two entries for the same logical source system in this table.
Arun

ABAP logical source system

Similar Messages

Maybe you are looking for