Why should the source system config be open for restore?

Good day everyone,
Every time I do source system restore, I have to open the IMG in the source system. Could someone please explain or provide me with an SAP link that explains the necessity for this step. It is causing me a lot of troubles in production systems.
Thanks.

Thanks for your response.
Funny thing though my has not ran that hot.
Wither watching Videos or play a game like Fallout 3 everything on the laptop is always cool to my touch on the top.
Except sometimes by the vent where the fan and exchaust are it maybe lukewarm, I've had other laptops run much hotter.
But Thanks for the input, I think I'll go ahead and turn it back on though.
Better Safe then Sorry....

Similar Messages

Error: Infoobject is not defined in the source system

hi
(I posted this in other forums as well - but wondering, it it should be here in BCT/Extractors - I could use more help).
this is my issue:
I am trying to load master data (attr) for an infoobject.
But, it fails with the following error message (when I click on the "Error message" button on the "monitor" screen.
"Infoobject is not defined in the source system"
"Erros in source system".
(I did rsa3 and find it has some data + i checked on the base table as well, it has data; the datasource is from an SRM system) Why is it complaining like this.
any help on what could be wrong here? Pl let me know,
thanks

Thanks Ricardo,
I have tried that b4. and it says the "source system connection is OK".
any other idea?
Do I have to install the infoobjects on the source system as well? SRM is my source system.. I am not sure on that, but If I have to, how do I do that?
thanks
Message was edited by: Esan

Restoring the source system connection in BW

Hi all,
Ive been trying to upload data for 2 of my infocubes, and the extractions are bouncing. The message in R/3 is told me to check the connection. The RFC are fine. But when I tried to restore the source system connection (RSA1 in BW), it sent me the following error messages:
1.- Basic type ZS 118 does not exist.
2.- The following error in the source system:
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
The description in each error is:
Error #1:
Diagnosis
    IDoc type ZS 118 could not be found.
System response
Procedure
   Please enter an IDoc type that exists.
Error #3:
Diagnosis
    Incorrect IDoc type ZSAB023 in the ALE definition of the source system.
System response
    Error when sending data to BW.
Procedure
    Enter IDoc type ZS 118 .
They told me this IDocs are created automatically by the connection. Is that true?
How can I fix this, so that I can restore my connection and do the data extraction?
Thanks a lot
Regards,
Vic

Hi Victor Tostado
1.- Basic type ZS 118 does not exist.
Type Transaction WE30. Check iDoc types Obj. Name : RSSEND -> press F7
a.) Enter 'RSSEND' in the Obj. Name field. You will see an entry similar to the one below:
          RSSEND                          Data transfer from the source system (template)
                [-] E1RSSH               Data transfer IDoc: Header information
                         [+] E1RSHIE    Data transfer Idoc: Hierarchy header information
                                E1RSTXT   Data transfer IDoc: Texts
     b.) Enter RSREQUST in the Obj. Name field. You will see an entry similar to the one below:
            RSREQUST                    Data request to the source system
                 [-] E1RSRH               Data request IDoc: Header segment
                         [+] E1RSRHI     Data request IDoc: Hierarchy
                         [+] E1RSRTX    Data request IDoc: Texts
                         [+] E1RSRMD   Data request IDoc: Master data
                         [+] E1RSRIS      Data request IDoc: InfoSource
     c.) Enter RSINFO in the Obj. Name field. You will see an entry similar to the one below:
            RSINFO                         Info IDoc
                [-] E1RSHIN             InfoIDoc: Status segment
                        E1RSPIN            InfoIDoc: Data packet segment
                        E1RSEIN            InfoIDoc: Error segment
d.) If any of the above do not exist, contact your BASIS Team.
2.- The following error in the source system:
Type Transaction SM59. Maintain RFC destinations
a.)     Open the RFC Destinations. b.) Find your Source System and double click on it. c.) Technical setting should contain information regarding your source system d.) Logon Information should contain source system client and name & password for you remote logon.
3.- Incorrect IDoc type ZSAB023 in the ALE definition of the source system
Type Transaction WE21. iDoc Processing Ports.
receivers port is not available go to WE21 -> create port
a.) Select 'Ports' and then 'Transactional RFC'. b.) Click on the Port # for you source system. c.) Verify description & SAP R/3 versiond. RFC Destination should be one created in SM59. If non-existent then create one.
I) Type Transaction SE16. Data browser (for R/3 -> BW Connections)
Enter RSBASIDOC Print out copy of all entries in table.
II) Type Transaction SM30. Msg Types & Assignment to iDocs
Enter 'EDIMSG' in the Table/View field. Click on the 'Enter Conditions' option for Restrict Data Range. Click 'Maintain'. Select Message Type. Then enter 'RSSEND' in "From' field. Verify that the Basic Type matches what is in your RSBASIDOC table for each of your connections. If any are missing any entries you must create them as follows: Create another session and type Transaction WE30. Enter IDoc Type (ZSBAXXX) in Obj. Name field (Suggestion: Start new type with 'ZS' + Transfer Structure Prefix + (3)#'s) Select Create. Select "Create from Copy'. Enter 'RSSEND" in 'Copy From' field Enter Description (i.e. IDoc Type for BW Development) Execute (Green Check). Repeat for other missing entries.
Regards
Sangram Sutar

Error message from the source system

Hi,
I'm trying to load 0SD_O03 & 0SD_C03 using fullupload.
I have data in source system which I checked in RSA3.
I deleted the init request from the Infopackage.
Diagnosis
An error occurred in the source system.
System response
Caller 09 contains an error message.
Further analysis:
The error occurred in Service API .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request.
Please help!
Thanks,
Vish

I see a shortdump in BW system with runtime error
MESSAGE_TYPE_X
The current application program detected a situation which
should not occur. Therefore, a termination with a short du
triggered on purpose by the key word MESSAGE (type X).
Hi A.H.P,
It didn't happen to other extractions. I just started with this one. I set up the table in SAP R/3 system and when I tried to do the initial full load in SAP BW, it comes up with the above error.
Thanks,
Vish

RFC destination BW could not be created in the source system R3073

I'm creating a source system for our BW (version 7.0) dev client.I'm linking it to our R/3 4.7 QA client. From RSA1 I select create source system, I enter the system information and in the next screen I'm prompted to log on as system administrator. I'm in QA now and the system automatically crated the RFC connection. I test the connection and it runs ok. I log on to the BW client from QA and it logs on just fine. When I exit the screen I get the following message:
RFC destination BW could not be created in the source system message number R3073
Why is this happening? The connection tests just fine.
I'm using RFCREMOTE user in BW and ALEREMOTE in QA with the same password
Any ideas?
thanks

Hi,
I cannot tell you surely the settings for SCC4 now (I can't connect to my sys).
Nevertheless, create your R3QA RFCDEST manually in your BWDEV with SM59.
Create your BWDEV RFCDEST manually in your BWQA .
Perform test and authorization test within SM59 from both sys.
When creating the source system in BW the system will detect the RFC and ask you if you want to use it; accept an proceed the the rest of the procedure.
hope this helps...
Olivier.

How to change the source system for just a datasource

Hi,
Our test/development BI system ( BI 7.0 Unicode ) is connected to our development system and to our test system, 1 BI system connected to 2 R/3 systems.
During some time, the test system won't be available so all datasources that point to the test system must be connected to the development system. In RSA1 is not possible to change the source system in a datasource: RSDS 057
'Creation of DataSources for SAP source system D30CLNT007 is not permitted' , same error trying to copy the datasource,.
Any idea about how to proceed ?
Regards,
Joan

Hi,
If I try to repliclate metadata in the datasource, message RSAR 051 appears: 'error when opening an RFC connection'. This error is expected because the logical system pointed in the datasource does not exist.
Is not possible to change the source system in datasource ( in RSA1 ) because the field is always greyed, also if I try to copy the datasource the message RSDS 057 appears.
Any idea about how to proceed ?
Regards,
Joan

Infosource 8ZISCMS10 is not defined in the source system

Hi Gurus,
I got an issue when loading the data with in SAP BW (Info source is ODS),It threw an error message stating "Infosource 8ZISCMS10 is not defined in the source system",
Could any one of you help me in this regrad plz,
N:B: I have activated the transfer structure through RS_TRANSTRU_ACTIVATE_ALL and replicated the data sources before loading...

When u activate DSO/ODS (say ZISCMS10) it creates datasource (8ZISCMS10) & Infosource (8ZISCMS10)
U can check these at ...... Modeling --> Datasources -> BI -> BI source system name. If it is missing .. reactivate DSO/ODS.
If the load is failing in QA, u should rereactivate DSO/ODS in DEV and transport that to QA.. After transport.. make sure datasource (8ZISCMS10) & Infosource (8ZISCMS10) appears in QA (Modeling --> Datasources -> BI -> BI source system name)

CLIENT of the source system in the Transfer Rules

Hi,
Can I get the CLIENT of the source system dynamically in the Transfer Rules (and assign it to an InfoObject)?
I have a generic extractor from a R/3 source system. The table in the source system & the extract structure the DataSource both contain MANDT, but its not coming in the RSO2 screen (which, if I'm not wrong, is how it should be).
I need the CLIENT info. in my BW data targets. I do not want to hardcode this value in Trans Rules as the client in Dev & Prod is different for my R/3 sys.
If I can't get it directly from the DataSource, is there any way I can get it from any system field using routine?
If I'm not wrong - SYST-MANDT in the Formulas will give me only my BW CLIENT.
Thanks in advance for your help.
Regards,
Melwyn

hi,
i think if your bw dev and prod client is different you can try in transfer rules
if sy-mandt = xxx. ( bw dev client number)
result = 'yyy'. (source system dev)
else.
result = 'zzz'. (source system prod)
endif.
or enhance the extract structure/ append structure with zz field for mandt and field in user exit zxrsau01 with sy-mandt
or if use infoobject 0LOGSYS, populate in transfer rules with result = g_s_minfo-logsys.
hope this helps.

Job terminated in the source system

Hi BW ens,
when i try to load data i am getting error as below.
Error message when processing in the Business Warehouse
Diagnosis
An error occurred in the SAP BW when processing the data. The error is documented in an error message.
System response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Second step in the update
**when i tried to see in the source system it is showing like :Extrapolation cannot be carried out because no inst. has been allocated"and "ABAP/4 processor: CONVT_NO_NUMBER:**
**pls let me know how to overcome this problem in loading.**
regards
Ravi

Hi Ravi,
U can check the Job logs in SM37 !!!!!
Apart from that i think there is a lock that has occured ,goto SM12 and unlock the objects.
Reload the data at the point where the error has occured ,It should be fine.
Rgds
SVU123

An error occured in the source system

My process chain has been doing FULL load for COPA data in a ODS. It failed today saying
Diagnosis
An error occurred in the source system.
System response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
When I click on indiv. Message tab I get "Job in source system terminated - Requests is set to red"
What should I do to resolve the problem.

For Source system R3 :
This particular problem "Job terminated in the source System" occurs when there are long running jobs in the backend.
In the monitor tab,
Environment --> Job Overview --> In the source system.
After logging into the source system, click execute
Check the status of the job i.e. active or failed.
Check the job log for the same.
If its " DBIF_SQL_..... " sort of error, then in this case, delete the request from the data target and reload again.
The load would be successful
Caller 09 error normally occurs when the source from which the datasource is picking up data may be in use on the R3 side.
Hope this helps!!!!!!!

Error occured in the Source system while loading mater data

hi all
While loadng the master data info package.The request is getting failed with error occured in the source system.
error message says "<b>if the source system is a Client Workstation, then it is possible that the file that was to be loaded was being edited at the time of the data request. Make sure that the file is in the specified directory and is not being edited, and restart the request</b>".
   I had tried repeating the Request but again It is getting failed.
   please help me resolving the issue.
Thanks(=Points)
      Priya

Hello Priya
If u r loading thru flat file
1. Check the correct path in infopackage
2. Check if it is opened,if it is then close it and run package again
If loading thru R/3
1. Check DS is not opened in change mode
2. Check if RSA3 is able to extract data...if it is then check in RSA7 and chk IDOC status...
3. Are you running init..then make sure no document is posted in R/3 side...
Thanks
Tripple k

Language field is not maintained in the source system

hi,
I had problem with 0ehs_actn_text data source. when i'm trying to pull data to BW it's saying language field is not maintained in the source system.
I check the datasource there is no language field in the extract structure. and No fileds are checked for slection. I found one field REFOBJ checked in the data selection tab of datasource. But the data not coming to BW side.
could anyone help.
regards
kumar

hi kumar,
Check in rsa6 TXTLG field should be there and it should not be checked in HideField Tab.. then only the data will populate to BW..
So make the things properly and once again replicate the data source in Bw side.. load the data..
other wise if u dont wanto the language field in Bw side goto infoobject maintanance uncheck the "TExt Language dependent" option in masterdata/texts Tab.. save and activate it.. load the data..
i hope this will help you..
Thanks..
ravi.p

Inbound idoc error in the source system

HI,experts
I manually configurate the idoc type ,message type ,etc between the BW system and r/3 source system when the automatic program encouters errors. And the communication between BW and source sysyem seems ok since the source system is activated successfully in BW side.
But when I check the inbound the idoc in source system after i triggerred a full load for the datasource 0FI_GL_4,an error occurs in the inbound process in R/3. There is no control information in the idoc which message type is RSRQST.
how can i figure this issue out ?could anyone help me ?

HI,ALL
Thanks for your replies and documents.
Now I find the problems lies in the error connection between R/3 and BW. IF the autoconfiguration is completelly correct , the table RSBASIDOC in both system should be added one record.But now when the source system is activated successfully ,the table in R/3 side has no entry while the BW side has one entry .juding from this ,there is no BW system connected to the R/3 ,which is proved when I fill the setup table for LO datasource an error message shows that there's no BW system is connected to the OLTP system.
How can i figure this issue out ?If I want to do an automatic configuration ,what shall I do ?

Transfer method 'TRFC with PSA' is not supported by the source system.

Hi guys
We are getting the following error when we try to open the transfer rules:
Transfer method 'TRFC with PSA' is not supported by the source system.
And when we run the load we are getting this error message:
An RFC call-up triggered the exception
Our source system check is ok. RFC test is ok from both sides.
Please advice what else can be the solution.
Edited by: sam on Nov 6, 2008 4:51 PM

Did you do Right click on Source system and 'Check' option in RSA1-> Source Systems?
Is this problem after upgrade or something like that?
-Abhijit

No Hierarchies for this InfoSource in the Source System

Hello All,
I want to find out how to get my hierarchy back in Bex (Query Designer). We just got a new BW system. The hierarchy was loading fine in the old system but unable to see it in the new system. I have done the following and still no luck:
Replicated the Datasource
Replicated the Source System
Maintain Hierarchies shows no hierarchies and when I click on create hierarchy (No values when you click on Hierarchy Name). Whereas I get hierarchy values in the old system.
In the Infopackage, click on Hierarchy Selection => Available Hierarchies from OLTP, I get "There are no Hierarchies for this InfoSource in the Source System".
Is there anything am missing? My suspicion is may be the Hierarchies need to be maintained in ECC first and then I should replicate again and then load the hierarchy.
Any suggestion would be appreciated.
Thanks,
Recca

Thanks Sai and RDS.
@ Sai: Yes, the Datasource is present in BW as 3.x version which I assume is ok. It is also present in active version in ECC in RSA6. There is nothing to load for the hierarchy because when you click on the InfoPackage the "Hierarchy Selection" and then "Available Hierarchies from OLTP", in other to refresh the list, I get "There are no Hierarchies for this InfoSource in the Source System".
@ RDS: Yes, the connection of BW to the ECC Source System is good....checked out ok. There is nothing to load for the hierarchy because when you click on "Hierarchy Selection" and then "Available Hierarchies from OLTP", in other to refresh the list, I get "There are no Hierarchies for this InfoSource in the Source System".
Besides RSA6 to check the datasource in active version in ECC, do you have a T-Code to check where these following Hierarchies are maintained in ECC? I need to compare it from the old system with the new system.
1. Fund
2. Fund Center
3. Commitment Item
Thanks,
Recca

Why should the source system config be open for restore?

Similar Messages

Maybe you are looking for