RSA7 - no records in the source system

Hello,
RSA7 in the source system shows the following record :
2LIS_03_BF DB1CLNT300 21
But 'Display data entries' shows no data. No data in bw aswell. Delta init has restriction by plant.
Is it a normail situation?

Hi,
Which update method you are using.
If its direct delta then it directly come RSA7.If its Queued delta or Unserilized V3 update you have to see in LBWQ and SM13 respctively.
For more info find this.
http://www.sdn.sap.com/irj/sdn/nw-bi?rid=/library/uuid/f03da665-bb6f-2c10-7da7-9e8a6684f2f9
Regards,
Shiva.
Edited by: Shivu Kumar on Oct 14, 2009 2:45 PM

Similar Messages

Customized delta data source for deleting data record in the source system.

Hello Gurus,
there is a customized delta data source, how to implement delta function for deleting data record in the source system?
I mean if there is record deleted in the source sytem, how to notify SAP BW system for this deleting change by this customized delta
data source?
Many thanks.

Hi,
when ever record deleted we need to write the code to insert the record in Z table load this records into BW in a cube with similar structure.while loading into this cube multiply the Keyfigure by -1.
add this cube in the Multi Provider.The union of the records in the orginal cube and the cube having deleted records will result in zero vale and will not be displayed in report .
Regards,

Changing the source system in QA

Hello All,
I just wanted a quick opinion from your experience on the following issue:
We have a ECC Dev client 20 connected to BI Dev client 20
Similarly we have ECC QA 120 connected to BI QA 120
But due to some reason we now want to connect a new ECC QA client 150 to BI QA 120 and take out ECC QA 120 totally(120 is wiped off).
I already have a lot of development transported to BI QA where the source system is ECC 120. Now if 120 dies and we pull the data from 150, what are the pitfalls to watch for?
Like all my Master data objects , DSO and Cubes still point to ECC QA client 120 but now the "actual" source system is going to be ECC QA 150.
Points,
Gaurav

You need to replicate all the data sources in BI from QA 150 and change the source system assignment to 150 instead of 120.
Also, you need to reinitilase delta for delta enabled extractors.
Two things to watch out:
1. If you dont have source system identifier, then if you happen to get records with same key, then it will overwrite. This applies to both master and transaction data.
2. For transaction data that is not delta enables, there may be a possibiltiy with which the records will get duplicated. So, better to delete the old requests before reload the data from QA150.
Ravi Thothadri

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

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 ?

R/3 connection to BIW - No Idocs arrived from the source system

Question,
Hi Team,
I have issues during loading attribute data from R/3 source system to BI,
I go to the path
Data Warehousing Workbench - Modeling window. In the DataSources view, my application component Group ##. On my DataSource i Create Info Package and save it,
Later I select the following options
Full Update = select
On the Processing tab page, select only PSA.
On the Schedule tab page, choose Start Data Load Immediately and start the data load.
Till here everything is in active version and saved, and connection to the source system is active and working fine.
However when I do loading I received following messages, what I observed in Monitor window,
Data was requested OK
Request still running
Diagnosis
No errors found. The current process has probably not finished yet.
System Response
The ALE inbox of BI is identical to the ALE outbox of the source system
or
the maximum wait time for this request has not yet been exceeded
or
the background job has not yet finished in the source system.
Current status
No Idocs arrived from the source system.
When I go to detail tab, under transfer section, I receive the following message
Data Package 1 : arrived in BW ; Processing : Selected number does not agree with transferred n
But when I actually go to PSA maintain section and select data and no of records, I can see the that data is loaded into PSA section,
But when I chose to run the transformation I donu2019t get data here,
Kindly help me to resolve this issue,
Regards,
BluSKy

Hi,
the BIW i am using , its compact BIW, which is in EXI, and i execute transaction /nrsa1 to go biw development workbench,
i am not sure about transactions settings about r/3 side,
could you plz throw some light on this issue,
regards
blusky

We would like to test old deltas from the source system( copied to new)

Hi Gurus,
The scenario is
They will make a DB copy of the Prod system onto a QA system, the Copied system will have
its system ID changed(SID) to a new one.
There will be deltas available in the RSA7, as this is a copy of the 3 weeks old prod
system. Now the delta's will be available on the Copied system pointing to the BW Prod system.
We would like to test these delta's to BW Dev. why we would like to do the delta's to the
BW dev system is to check whether we can do system copies without clearing the delta's on
the source system.
After the system copy we will do all the activities necessary to reflect the system changes
a. Like BDLS, We20, we21,ALE checks, RFCDES, RSLOGSYSDEST, RSBASIDOC, etc on the source system to
reflect the changes of the BW Prod system to BW Dev system.
b. Likewise, we will perform all the above activities on the BW dev system by changing the
existing source system to the new source system( performing BDLS,we0, we21, etc)to reflect
the new Source system with the new (SID).
c. We will check the source system connection
d. Replicate the datasources on the new source system
e. Activate the Transfer rules for the new source system.
Now for us to do delta's from the new source system to the Bw dev system we need to change
underlying tables in source system to point the delta's, arfc TID's etc to the BW dev system.
We can change the entries in the TRFCQOUT, ARFCCSTATE, ARFCDATA tables to point the LUW's and
destination to the BW dev system.
What I presume is if we run the BDLS on the Copied system to change the BW prod system to BW
and also the underlying Tables for the LUW's and etc will still be pointing to BW Dev. I would
like to know if this is the case .
Lastly, appreciate if anyone can say if this is possible to do without having to clear the
BW delta queue on the source system.

Hi Ramesh,
Appreciate a lot for your response, but i would like to know if we can reflect the entries in table RSSDLINIT(Last Valid Initializations to an OLTP Source) and RSSDLINITSEL(Last Valid Initializations to an OLTP Source) in the BW system on the copied source system
tables ROOSPRMSC(Control Parameter Per DataSource Channel), ROOSPRMSF(Control Parameter Per DataSource Channel) by executing the ABAP program RSSM_OLTP_INIT_DELTA_UPDATE after we do the BDLS conversion on the new copied source system.
After the BDLS conversion I reckon the entries in the RSA7 queue, ARFCCSTATE, TRFCQOUT tables willl reflect the BW Development system instead of the BW Production system isnt it.
response much appreciated.
Kalyan

Select the language field in the source system ?

Hi,
when I schedule the load for 0cust_sales_text there popups the message 'Select the language field in the source system -> Long text'.
Long text says: 'Either no language field is selected as a selection field in the source system KC1CL005 in DataSource 0CUST_SALES_TEXT, or the language field is not assigned to InfoObject 0LANGU in BW.'
In the DataSource there is not an object for language? I don't know what to do.
Tobias

Hello,
texts of 0cust_sales are not marked as language-dependent.
the psa tells me, which records are marked as error, but i don't understand it.
green     1     1     0009     03     MB     L605930     cust a
green     1     2     0009     03     XX     L605930     cust a
red     1     3     0009     04     MB     0000013081     cust b
red     1     4     0009     04     XX     0000013081     cust b
green     1     5     0020     01     MB     0000001570     cust c
green     1     6     0020     01     XX     0000001570     cust c
red     1     7     0020     01     MB     0000001571     cust c
red     1     8     0020     01     XX     0000001571     cust c
red     1     9     0020     01     MB     0000001572     cust c
red     1     10     0020     01     XX     0000001572     cust c
green     1     11     0020     01     MB     0000001578     cust d
The error messages say there were double records
Tobias

Steps in BW after the upgrade of the source system R3 in netweaver 2004s???

Hi,
1. Who can tell me which are the steps to execute in BW after the upgrade of the source system R/3 4.6 to Netweaver 2004s (ECC6) ?
2. Do the delta loads continue to run or must be re-initialized?
Thanks for your help
Dominique

hi Dominique,
you should take care not after upgrade, but also before upgrade
or your upgrade has been done ?
also stated, before upgrade
If you use Logistic Cockpit, please make sure that you know notes 328181, 396647, 380078.
These are absolutely prerequisit notes for using Logistic Cockpit.
Never change the extract structure (communication structure) when there is data in SM13 or in the DeltaQueue!
Never upgrade your PlugIn System when you have data in SM13 or in the DeltaQueue!
SM13 and RSA7 have ALWAYS to be EMPTY BEFORE you apply any changes to communication structures, extract structures or any referenced Data Dictionary object or BEFORE you upgrade your PlugIn system!!!
SM13 and RSA7 have to be EMPTY also when you apply PlugIn Support Packages!
458305-OLTP system upgrade: What should I be aware of afterwards?
Note 458305 - OLTP: System upgrade or SP - What should I be aware of after
Note 301192 - Procedure after upgrading an R/3 source system
Note 359412, there may be some others
hope this helps.

DW Side Work When the Sourcing System Gets Refreshed

Dear colleagues,
We currently have an ECC 6 Client as the sourcing system feeding data into our QAS BW 3.5 environment (basically Master data and very little transaction data at the moment). Due to the Master Data inconsistency of the sourcing client, it is decided to rebuild the ECC client plus complete Master Data reloading.
So, as a Basis person with limited BW knowledge, I am a little bit nervous from the BW side in terms of the procedure how to rebuild our QAS BW system. Here I have following questions for your experts:
1. Is there any standard procedure out there that I can follow in such a circumstance that I dont think is unique to us.
2. I believe I have to reload all the Master data once this has been done from the ECC side, do I have to delete all the Master data that have already been loaded into the BW and how should I do that?
3. With the very limited transaction data, will they be gone if I rerun the INIT process or I have to do things differently?
Thanks and regards,
Joshua Z.

Hi,
Not very sure about Refresh.
But this is what we follow when you go for an SP upgrade or maintenance on source.
As a standard procedure its better to drain all the deltas before going ahead. As a first step I think you will stop all transactions in ECC. Once done Start pulling delta loads repeatedly till it fetches zero records. then reschedule your V3 Jobs to a future date.
Then perform all this activities.
I dont think you have to delete MD as its overwritten the next time you load.
Is there a need for init if the previous init is still there?
Even in case you do I dont think you will lose any data. You always have an option of full repair to load any data from R3.
Refer.
Activity to be performed after client copy :
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
BW system Copy :
System Copy BW
Re: bw system copy
BDLS :
Re: After R/3 Refresh
BDLS on BW Q/A
Check following OSS notes.
Note 543715 - Projects for BW Migrations and System Copies
Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
Note 325525 - Copying and renaming systems in a BW environment
Note 184754 - Procedure after BW database copy
client copy
http://help.sap.com/saphelp_nw04/helpdata/en/c2/17e73a86e99c77e10000000a114084/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/69/c24cc34ba111d189750000e8322d00/frameset.htm
Client Copy
http://help.sap.com/saphelp_nw04/helpdata/en/ff/9be1817d811c41985662da25061f98/frameset.htm
Thanks,
JituK

Error: Qeue 2LIS_03_BF is not available in the source system

Dear Experts,
While scheduling 2LIS_03_BF. It displyed following error.
Error : Queue 2LIS_03_BF is not available in the source system
What could be the problem,
Please help me to resolve this issue.
Regards,
Khader,

Hi Mansi & Sujatha,
I am also facing the same problem, in RSA7 status of 2LIS_03_BF is in red.
Please suggest how could I proceed further.
Regards,
Venkat.

Application log in the source system.

Hi,
I am trying to do the initialisation with data selection from R3 Source system into BW. Data was loaded but still the status showing Yellow and its giving the following messages.
Information was stored in the source system.
Diagnosis
The system has written an <b>application log</b> in the source system.
System response
No errors occurred.
Procedure
Check the log.
Procedure for System Administration
Can any body help me how to look the Application Log & the solution for the above problem.
Note : My PSA have all green records and it loaded 1176080 From 1176080 Records.
Points will be awarded.
Thanks,
Abhi.

Hi Abhi,
If BW tells you that no errors occurred it makes no sense to look into the application log. What helps however is to check if processes are still active for your load, e.g. ODS activation. You can check using tcode SM50 (in R/3 for e.g. user ALEREMOTE, in BW e.g. user BWREMOTE...can differ in your system).
Also check the Details tab in the monitor to see if all is green there (expand all nodes). Something might still be yellow so that's the step which is 'hanging'.
Hope it helps...
Grtx
Marco

No code page has been assigned for the language b in the source system

Hi Gurus,
I have triggered a full infopackage to load data from a non-unicode R/3 system (4.6) to a Unicode SAP BI (7.0) system.
But the load failed with the error " Invalid language "b" for structure alignment of record "3685"
But when i trigger a delta infopackage the IP status ends in green but no data is pulled.
This looks like a typical issue.
Please help me to resolve the issue.
Thanks a lot in advance.
Warm Regards,
Anirban

Hi Prasanth,
I have done all the BW configurations possible,but data is not at all loaded in the BW system.
The BW System is an Unicode one,where as the R/3 system is not an unicode one.
Data is not even loaded until PSA.
How can i maintain the language B in the source system? By running the RSCPINST and adding B to the corresponding table?
Thanks Much!
Anirban

Data Source Z*** is not defined in the source system

Hello All,
I am facing a well known problem extracting data from R3 to the BI side. On both sides I've got SAP ALL.
I created data source on R3 DEV side, tested it and it extracts data. I've replicated metadata on BI side and activated the data source. The problem starts once I create the info package as no data is availble in PSA.
I went to extractor checker and tried to start the extraction and I could see the message: data source Z**** not defined in the source system.
I tried to locate the data source through RSA5 and I cannot see that it is availble there.
Can you please help and advise where the problem is?

Hi Neb,
It can be related to many issues, one of them can be RFC connection issue. Please check the link below :-
Datasource xxx is not defined in the source system
It might give you some of ideas. Also if possible can you tell what Datasource are you having problem with.
Regards
Sunny

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

RSA7 - no records in the source system

Similar Messages

Maybe you are looking for