Switching R/3 source systems

Hi SDN gurus,
We have a scenario where we sould like to change a test R/3 source system in our BI7 box. Currently there are lots of flows from QA1 (old style datasources/transfer rules etc), if a new R/3 system QA2 is created and connected, is there a way to convert the transfer rules/InfoPackages etc to  pick up the new system. I'm trying to avoid retransporting all the objects from dev again with a new system mapping from/to value as there are projects currently starting in dev which complicates things.
Is there a program or function module that can help ?
Cheers,
Rob.

Hi Rob,
If you go into the transport connection, under "Grouping" you have an option called "Save for System Copy".   This option allows you to move all of your datasources/assignments/transfer rules from one system to another just like when you transport from Dev to QA.  
You need to build this transport out with all of the datasources you are using.  Then release the transport.  After you create the new source system, you need to map your original source system to the new source system (RSA1=>tools=>Mapping of the Source System Names).
Then you can import (apply the transport to your dev system and your datasources/transfer rules/assignments will be copied over.
I would test this out before deleting my original source system.
Brian

Similar Messages

  • How to change a source system

    Hello,
    we have just copied our BW productive system on the consolidation system. With this copy on the consolidation system now exist the source system to our productive R/3 system.
    I would like to connect the bw consolidation systen with the R/3 consolidation system.
    Does anybody now a possibility to switch the existing source system "R/3 productive" to "R/3 consolidation".
    All source system related objects (infopackages and so on) should be switched to the new source system too.
    Thanks
    Frank

    Hi,
    Roberto's answer is correct but it is making the assumption that all the DataSources in R/3 production are the same in R/3 QA.
    Once you have done the BDLS in BW for the source system technical name, you will have to do a source system check and restore. This will check the idoc and low level communication settings.
    As Roberto states, SAP note 325525 is the best source of information.
    Finally, you will have to deal with the data differences. Your data in R/3 QA will not be the same in R/3 PRD. This is a manual process.
    Cheers,
    Mike.

  • Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

    I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
    ErrorCode: -17600,
    Failed to load a required step's associated module.
    LabVIEW Run-Time Engine version 9.0.1f3.
    When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
    My TestStand Engine Version is 2012 f1 (5.0.0.262).
    I'd appreciate any help on this issue.
    Roman

    Hi Roman,
    There are a couple of things you can try:
    1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
    Check if the simple VI is loadable and runs without errors in TestStand.
    If the step generates the same error, you should try a re-install of the LabVIEW development system.
    If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
    1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
    Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
    Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
    2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
        Right-click "Build Specifications" and choose "New->Application(EXE)".
        In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
        Save the properties.
        Right-click on the newly created build specification and choose Build.
    Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
    You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
    Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
    If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
    Regards,
    TRJ

  • Key Figure data type/length differs in BI and source system

    Hi all.
    It is a strange question, but we need an explanation to our "strange" client. Why many fields which are DEC 13 in source system became CURR 09 in BI? DEC->CURR type switch seems reasonable, but not the length. I guess the shorter numeric field is the less precise it can keep...
    Does SAP give any explanation for that?

    Hi,
         If you are expecting the data to be aggregated in the cube and if the data is loaded by different requests, then in that case the data wouldnot be aggregated.
    EX:  CHAR1   CHAR2    CHAR3   CHAR4     CHAR5    CHAR6    CHAR7    KF1   KF2   KF3
             A               B              C            D        E              F             G          10     20    30
              A               B              C            D        E              F             G          10     20    30
    sUPPOSE IF THE ABOVE 2 ROWS OF DATA ARE GETTING LOADED IN THE SAME REQUEST, then you can expect the data to be aggregated and the o/p of the KFs will be 20, 40 and 60 respectively.
    In case the loading is done with separate requests, then your data will not be aggregated.
    This is becuse in the cube, Request ID (under the Data Package Dimension)    is one of the dimension and this differs when the requests are different.
    Regards
    Sunil

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

  • No username of Source system is avbl after livecache system copy

    Hi Experts
    I have done a livecache system copy from the source system to target system. Here the steps are
    Assume my Source SYstem Livecache is RP1 and Target System livecache is RS1.
    1. Taken Source system livecache DATA and LOG Area backup RP1.
    2. Defined the same source system backup medium name in Target System (RS1 and moving the Source system Liveacache backuped files to Target system and defined the medium name as per that)
    3. put the livecache db_admin mode
    4. db_activate RECOVER <medium_name>.
    5. recover_start <log_medium_name> LOG <nnn>
    6. db_online.
    Here we faced that
    ERR
    -24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
    -24907,ERR_DBAWRONG: Wrong database system administrator
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    So we activated the SUPERDBA as " db_activate SUPERDBA,<password>
    then it came to online. and afterwards we have used the load_systab command to load the tables.
    BUT we could not find any Source System name like "RP1ADM" in the tables of the livecache database. Only there are CONTROL,SUPERDBA username availbale. Usually there will be also the source admin name . I dont know why it is missing
    Before a month we have done livecahe restore same as now in that time we got the source system name admin also. ( RP1ADM) and also tables which owned by RP1ADM. alos i could find APPSYSPARAM table and the instance also registered.
    But now in this restore we could not find the above.
    We followed the same procedure and there is no change in the steps also.
    Could anyone help me...
    Regards
    bala

    Hello Bala,
    1. As I wrote you already, the notes:
    886103 System Landscape Copy for SAP SCM
    877203     Post steps after the Homogenous liveCache copy using backup/
    457425     Homogenous liveCache copy using backup/restore
    has all recommended steps to do, when you will run the u201CSystem Landscape Copy for SAP SCMu201D
    2. If you run the u201CHomogenous liveCache copy using backup/restoreu201D you should pay attention to the note 457425. After you imported the complete data backup < step 2. > you need to update the system tables.
    To update the system tables you need to know the correct database SYSDBA user & password.
    After you restored the databackup of the source database, start the database online & run u201Cselect * from usersu201D SQL command to see the SYSDBA user. Then check that you know the DBA user ( DataBase Administrator ) & password of the source database instance => Open the SQL session with this
    user & password.
    Example:
    after db_activate recover <medium_name>
    login as control,password
    db_online
    sql_execute select * from users
    sql_connect  superdba,<password of source system>
    If you didnu2019t get error with the last command, then you could update the system tables with the superdba,<password of source system> using load_systab command.
    The system tables will be updated & the correct SYSDBA user & password will be updated in *.UPC file.
    3.     
    user_sysdba:
    You make the database system administrator known to Database Manager. It is only necessary to use this DBM command if the database administrator is not known or is incorrectly known to Database Manager.
    u201CI have tried like this
    after db_activate recover <medium_name>
    login as control,password
    db_admin
    user_sysdba superdba,<password of source system>
    db_onlineu201D
    You could update the .upc files with the wrong SYSDBA user password u2026
    You was lucky, that you knew the correct SYSDBA user and password of the source database.
    Example  < NLK is my local database >:
    A.     I could update the .upc file with wrong password of SYSDBA user:
    dbmcli -d NLK -u control,control
    dbmcli on NLK>user_sysdba superdba,test
    OK
    dbmcli on NLK>db_online
    OK
    dbmcli on NLK>load_systab
    ERR
    -24909,ERR_DBAUNKNOWN: SYSDBA unknown
    dbmcli on NLK>exit
    B.  I could update the .upc file with wrong SYSDBA user:
    dbmcli -d NLK -u control,control
    dbmcli on NLK>user_sysdba test,test
    OK
    dbmcli on NLK> user_get test
    OK
    u2026
    dbmcli on NLK>sql_connect test,test
    ERR
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    dbmcli on NLK> dbmcli on NLK>sql_connect superdba,admin
    OK
    I could connect as test,test; but the test user is NOT SYSDBA user u2026
    dbmcli -d NLK -u test,test
    dbmcli on NLK>
    Itu2019s recommended to user the load_systab command, so the .upc files will be updated with the correct SYSDBA user/password or
    you will get error.
    4. http://maxdb.sap.com/doc/7_7/86/68627a1bc642e6a6f73d3bc7a55fe1/content.htm
    You got error:
    ERR
    -24622,ERR_AUTOLOADSYSTAB: Automatic loading of the System Tables failed
    -24907,ERR_DBAWRONG: Wrong database system administrator
    -24988,ERR_SQL: SQL error
    -4008,Unknown user name/password combination
    The automatically updating the system tables, according to the default value, is switched on.
    After you will run the update system tables with the correct SYSDBA user & password the *.UPC file will be updated,
    and with the next liveCache restart you will not get this error.
    5. See more information in the MAXDB library:
    http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
    Thank you and best regards, Natalia Khlopina
    Edited by: Natalia Khlopina on May 19, 2010 2:58 PM

  • How to replace a source system with another in BW

    Hello experts,
    I've read many topics dealing with my customer's need, but I still can't find the solution.
    My landscape is the following one :
    ECC6 with DEV, QUAL and PROD
    BW with DEV and PROD
    BW DEV source system is ECC6 DEV, I need to change it to ECC6 QUAL
    A lot of work has already been done, and I'd like not to lose it changing the source system.
    Datasources are the same in ECC6 DEV and QUAL.
    This is not a system or a client copy, it is really a source system switch.
    The new source system is already created (both DEV and QUAL ECC6 are available in "source systems" in RSA1), and I tried to use BDLS tcode
    In the "old logical system name" I choose my current source system and in "new logical system name" I choose the one I now need to use.
    System answer is : "The logical system name ECC6 QUAL already exists"
    Obviously I did something wrong, but can't figure what.
    Is there any action to perform before BDLS ?
    Any help is appreciated, and points will be given.
    Guillaume P.

    Thanks for your answer,
    "relevant object" means for you datasources, transfer rules and transformations ?
    With the grouping option "Save for system copy" I can't take easily all datasources, and others objects
    Will I have to pick all object one by one ?
    What would be the adjustement in table RSLOGSYSMAP ? For the moment it's empty.
    Regards
    Guillaume P.

  • Unable to Create Source system in RSA1

    I have installed a BI Server(Netweaver 2004s). When i try to add source system in RSA1, it gives an error "No entry for BW_USER in table RSADMIN available"
    Let me tell what all i tried.
    1) i clicked on settings>global settings- it gives a blank page. when i switch it to change mode, there is a button called "Position" and then "Entry1 of 2". I cant enter any value there and when i click on "Position" button, it says "Table RSADMINAV has no relevant fields"
    2) In se16 tried to maintain RSADMINA table and for BW User field, i gave BW_USER, but there is no "execute" Button. all i see is "Reset" button. i tried pressing F8 key, it wont do anything. I clicked on save but it says "the entry is already exist"
    Regarding RFC - i created a user BW_USER in ERP Sytem and ERP_USER in BI server and both the user type are System user.
    From both the server i tried to do Connection test and i am not getting any error. but if i try clicking Remote Connection, it wont connect and wont do anything and no Errors.
    Please help me Resolving this Issue, Since it became a very critical issue.

    Hi,
    Can you check  if there is any other user ID specified in "BW user for ALE".
    To check, Go to transaction RSA1 --> Settings --> Global Settings.
    If you find a different user id there, then specify the correct BW user id there.
    Please refer to OSS Note 410952 for details.
    Hope this solves your problem!!
    Regards,
    Raj.
    Edited by: Raj on Aug 14, 2009 8:15 PM
    Edited by: Raj on Aug 14, 2009 8:16 PM

  • Error when activating Datasource in Source System

    Dear All,
    I am gettting this error when activating data source in source system(RSA5).
    1)DataSource 0NETWORK_CUST_ATTR; switch to package PS_IS_EHP3_SFWS_SC is off.
    2) The extract structure DTTV_REC_53 of the DataSource 0TV_REC_531 is invalid
    Message no. R8444
    Diagnosis
    An invalid extract structure has been assigned to the DataSource. An extract structure has to be active in the DDIC. It cannot be a view, since the customer is not able to add append fields for filling in the customer exits to a view.

    Hi
    To use this datasource, you need to install EHP3 package.
    http://help.sap.com/saphelp_nw70/helpdata/EN/b0/7b6c759c494ffcbf821d2442687888/frameset.htm
    Chandu.

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

  • RSA1 Source System DBConnect problem with 8i DB

    I have just upgraded my BI instance to Oracle 11G.  After this, a source system connection to an Oracle 8i database configured using DBConnect does not work.  I have read that a connection between 11g instant client and an 8i database is not possible. 
    After switching back to the Oracle 10G instant client, the source system connection works fine.
    I'm just wondering if anybody has encountered this, and if there is any way to have the 11G instant client in place for SAP as a whole but have DBConnect use the 10G client to connect to the 8i DB.  Any insight is appreciated.  Thanks!

    Hello,
    Please check your RFC destination whether the source system already exists.
    In the source system creation you assign the IP address instead of source system name. Please go through the screens (SM59).
    If you have not used IP address you can ignore it.
    Thanks
    Chandran
    Edited by: Chandran Ganesan on Nov 13, 2008 2:30 PM

  • Copy Transferrules from one source system to another

    Hi everybody,
    we're uploading data from nearly 25 sourcesystems (including separate systems and systems with more than one client to extract from) via flat-file. The source-system exports data to a shared file directory and the bw-system reads it from there. Though this results in only <b>one</b> transferrule for all source-systems, it keeps generating problems every time upload is due.
    Somebody had the idea to switch to 'standard' R/3->BW method of data staging, using generic extractors and so on. But this will result in <b>25</b> transferrules which, I'm afraid, have to be set up and maintained seperately. As there's quite some coding in the rules (the transfertructure in fact has 241 fields), flaws are for sure!
    We know the trick of exporting a transferrule, changing the source-system-mapping and re-importing the same transport-request. That can be used to copy to one or two other systems, but not for 25.
    Does anybody know another way to copy a transferrule from one source system to multiple other source systems?
    Looking forward to your answers
    Thanks and Regards
    Robert

    Hi Ralph,
    I don't like that methode. Importing the same transport 15 times, each time changing the source-system mapping and making sure, that source-system gets the changes seems to be a huge source of errors, which will be hard to find.
    What do you think of the following idea to solve the issue a totally different way:
    All transfer-rules directly connected to the source-systems are stripped of all Coding, so there is a plain 1 by 1 transformation including 0logsys.
    The InfoSources attached all lead to one ODS-Object, which has the only purpose to collect the data from the source-system without any transformation. So some fields a filled by a system and other fields maybe not.
    The coding specific for source-systems is moved to transfer- / update-rules from that ODS-Object to the original ODS-Objects / Cubes and the "collecting" ODS-Object is emptied after every loading process.
    This will result in a single point of change. It will be quite a huge program (maybe in startroutine) but it's the one and only point, where changes and corrections have to be made.
    Regards
    Robert

  • Source System and RFC cnx

    Hi Friends!
    We have BI connected to ECC and working ok.
    Now, the business will create a new instance in ECC, in the same server.
    We only need use the second (newest) instance, but we dont want create e new source system.
    We are thinking about change the RFC  cnx of the source system, and put this pointed to the new instance.
    With this solution, we hope that not changes must be take place in BI.
    a) is this a good solution? any experience on this?
    b) the RFC cnx, can identify each of this ECC instance, if both of them are in the same server?
    c) doed I need any aditional change in BI?
    Thanks a lot for your suggest!

    This will work in case you will set up a new instance of ECC with same logical name, same RFC connection as 1st ECC instance has. Basically all the basis settings should be same.
    Also consider that you have to switch off 1st ECC instance before connecting other ECC to your BW with same RFC connection etc...
    BR
    m./

  • How to delete source system in BI system

    Dear Experts ,
    recently we finished client copy in BI production system to quality system,
    now we are facing problem with source system connections in bI system
    in RSA1 APO production system's source system is comes to BI quality system now i need to delete that APO source system in BI quality system ..please let me the process how can i delete source in BI quality
    can i delete it as below
    log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
    or we have any other process to delete it.
    Regards

    Hi Swathimatta,
    Apart from the two ways to delete the source system:
    1.- log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
    2.- Execcuting the FM 'RSAP_BIW_DISCONNECT.
    If you cannot delete the source system:
    Use fuction module RSAR_LOGICAL_SYSTEM_DELETE to delete
    the source system:
    1 - Go to SE37.
    2 - Run fuction module RSAR_LOGICAL_SYSTEM_DELETE.
    3 - Fill with the parameters as mentioned below:
          I_LOGSYS          = FUENTE
          I_FORCE_DELETE    = X
          I_NO_TRANSPORT    =
          I_NO_AUTHORITY    =
    Or follow the recommendations from note 140276, Solution 2:
    "You cannot delete the source system. Two cases have to be distinguished:
        o  The source system still exists.
           Switch to Transaction SM59. Find the destination which has the
           same name as the logical system of the source system from field
           SLOGSYS in table RSBASIDOC (see above).
           -  Such a destination does not exist in Transaction SM59. In this
              case, you have to create the destination to the source system.
              Name the destination equal the entry in SLOGSYS from above.
              Then return to the Administrator Workbench and repeat the
              deletion.
           -  The entry exists but a remote login is not possible. Correct
              the communication parameters.
           -  Everything works. Change to Transaction SE37, function module
              RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS =
              <log. name of the source system>, I_FORCE_DELETE = 'X'.
        o  The source system no longer exists or was replaced with another
           source system with the same IP address.
           Proceed as described in the first case but make sure, that the
           field 'Target host' contains a not existing server in the
           maintenance screen of the destination (Transaction SM59). If
           necessary, change an existing entry. Later when you delete, the
           system asks you whether you want to delete, although the source
           system is not available. Select 'Ignore'. "
    I hope it can help you.
    Regards,
    Fran.

  • Job Termination in source system-Dataload failure

    Hello Forum,
    We are on BW 3.1 and our source is SAP R/3 Enterprise.
    We have been facing a recurring problem for a dataload, that is JOB TERMINATION IN SOURCE SYSTEM.
    Details of the load:
    Target:Master Data
    Full load
    Processing:      PSA and InfoObject table in se

    Sorry, it got posted before I completed it.
    Please find the full details here:
    Hello Forum,
    We are on BW 3.1 and our source is SAP R/3 Enterprise.
    We have been facing a recurring problem for a dataload, that is JOB TERMINATION IN SOURCE SYSTEM.
    Details of the load:
    Target:Master Data
    Update Mode: Full load
    Processing: PSA and InfoObject table in series
    Selections: None
    Records Check:Terminate if errors occur; Aggregation    permitted
    Character Check: Switched off
    This has been delaying the loads for a long long time.
    Could you please suggest us the ways to fix this problem?
    Thanks is advance,
    Raj

Maybe you are looking for

  • Sematic group for a write optimized DSO

    Hello, I am loading from a datasource to a write optmized DSO. While doing so, I am not able to set semtantic key/group for the DTP.  I have turned error handling on using the setting 'Valid records update, No reporting(request RED)'. Is this setting

  • How can I connect my printer without air print

    How can I connect my printer without air print to my ipad mini?

  • ITunes won't update

    When I try to update through iTunes and after it downloads it says an error has occurred try and download again. Then I went on apple.com and tried that way and the installer downloaded. Then when it tried to download after a while it says an error o

  • 6680-Voda live streaming-Not enough Bandwidth

    Got a Nokia 6680 yesterday and could get the streaming Sky on Voda live no problem. I have tried today, it is saying not enough bandwidth and to check my network settings. Not sure what to do at this point. Any help would be appreciated please.

  • How do I create a check box?

    Hey there, I want to create a check box beside a text, like "keep me logged in". Anyone who can explain me how to do that? Thanks, alewei