MDX cache

HI,
Am working in WEBI where source is SAP Bex query.Since the performance is very slow.
I used Reporting agent (precalculated crystal report queries) for filling MDX cache but still my webi report is running for long time.
Could any one can explain how to make use of MDX cache in BI
Regards,
Kannan

Hi,
Shame you didn't mention your BObj version...
What notes are relevant to you depends entirely on the MDX expression and many other factors.
Try this:
www. service.sap.com/notes
Application area: BW-BEX-OT-MDX
Search terms:
a) performance runtime SAPKW70108
b) performance runtime SAPKW70109
c) performance runtime SAPKW70110
--> you will get a list of about 20 corrections, which include notes such as:
1553927, 1507653 , 1481568 , 1579304 , 1481835 , 1517091 , 1528869 , 1554272 , 1574984 , 1573815
All i have done is checked Note 1142664 - MDX: Composite SAP note about performance improvements
You should bookmark it!
Regards,
Henry

Similar Messages

Mdx cache error

Hi
I tried to fill the mdx cache on a query for a crystal report and I got the following error
Note
The following error text was processed in the system PB1 : Exception condition "NO_PROCESSING" raised.
The error occurred on the application server edmbwp01_PB1_95 and in the work process 4 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: PROCESS_MDX of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS_VARSET of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS_QUERY of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS of program CL_RSRA_ENGINE_MX=============CP
Method: START of program CL_RSRA_ENGINE_MX=============CP
Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP
Method: EXECUTE_SINGLE_RC of program CL_RSRA_JOB===================CP
Method: PRODUCE_MDX of program CL_RSRD_PRODUCER_PRECALC======CP
Method: IF_RSRD_F_PRODUCER_RT~PRODUCE of program CL_RSRD_PRODUCER_PRECALC======CP
Method: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
Has anyone see this error before?
Thanks,
Daniel

Hi Daniel,
how did you try to pre-fill the MDX cache ? Reporting Agent / Broadcasting ?
ingo

Fill MDX Cache Error

Hi Experts,
When I execute fill MDX cache by Information Broadcasting,I met such error messages as follows:
The following error text was processed in the system BGP : Exception condition "NO_PROCESSING" raised.
The error occurred on the application server PEKAX531_BGP_01 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: PROCESS_MDX of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS_VARSET of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS_QUERY of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS of program CL_RSRA_ENGINE_MX=============CP
Method: START of program CL_RSRA_ENGINE_MX=============CP
Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP
Method: EXECUTE_SINGLE_RC of program CL_RSRA_JOB===================CP
Method: PRODUCE_MDX of program CL_RSRD_PRODUCER_PRECALC======CP
Method: IF_RSRD_F_PRODUCER_RT~PRODUCE of program CL_RSRD_PRODUCER_PRECALC======CP
Method: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system BGP in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server PEKAX531_BGP_01 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server PEKAX531_BGP_01 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 001 -u: WANGJINE -l: E -s: BGP -i: PEKAX531_BGP_01 -w: 0 -d: 20100506 -t: 114206 -v: RABAX_STATE -e: RAISE_EXCEPTION
HTTP 500 - Internal Server Error
Your SAP Internet Communication Framework Team
Does anyone have met this issue?
Pls help!
Thanks!

Hi
I encountered the same issue on some of my queries
Note
The following error text was processed in the system PB1 : Exception condition "NO_PROCESSING" raised.
The error occurred on the application server edmbwp01_PB1_95 and in the work process 4 .
The termination type was: RABAX_STATE
The ABAP call stack was:
Method: PROCESS_MDX of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS_VARSET of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS_QUERY of program CL_RSRA_ENGINE_MX=============CP
Method: PROCESS of program CL_RSRA_ENGINE_MX=============CP
Method: START of program CL_RSRA_ENGINE_MX=============CP
Method: EXECUTE_SINGLE of program CL_RSRA_JOB===================CP
Method: EXECUTE_SINGLE_RC of program CL_RSRA_JOB===================CP
Method: PRODUCE_MDX of program CL_RSRD_PRODUCER_PRECALC======CP
Method: IF_RSRD_F_PRODUCER_RT~PRODUCE of program CL_RSRD_PRODUCER_PRECALC======CP
Method: EXECUTE_NODES of program CL_RSRD_SETTING===============CP
I ran my query in mdxtest and was able to run other queries and fill the mdx cache.
Any ideas?

Invalidating the MDX Cache

Dear all,
We are observing that even if we delete entries in the query cache, queries coming from BOBJ don't fire the corresponding SQL in the BW DB. We want to investigate now the content of the MDX cache, but so far we were not able to find a TX or similiar to manipulate (invalidate, current content, etc).
Any ideas ?
Kind regards, Philipp

Hi Philipp,
Can you share some information on the transaction you used for validating/invalidating the MDX Cache?
It will be very helpful. I couldn't find any info on this.
Thanks in advance.

MDX cache location in BI

Experts--
How can i administer the MDX cache which is used for BI broadcasting in a normal BI system.?
rsrt/rsrcache can be used for OLAP cache...would like to know similiar for MDX cache...
Best Regards,
Vikash

BI 7/0 has new distribution types are Fill Precalculation Store, Precalculate Value Set, Fill OLAP Cache, and Fill MDX Cache. These distribution types allow the BEx Broadcaster to replace the functions of the Reporting Agent. (Old Reporting Agent scenarios still run in SAP NetWeaver 2004s. However, the Reporting Agent will not be developed any further and is removed from the SAP NetWeaver 2004s Data Warehousing Workbench. You can now only reach the Reporting Agent using transaction code REPORTING_AGENT.) The Fill Precalculation Store distribution type allows you to precalculate Web templates, and the Precalculate Value Set option you to fill pre-calculated value set variables with values for characteristic values. The pre-calculated value sets are then available as variable values in BEx queries. With the Fill OLAP Cache, and Fill MDX Cache distribution types, you can warm up the OLAP and MDX cache with BEx queries.
You can check with tcode The new T-code RSRD_ADMIN which allows Administrators easy access to three key sources of information:
Global broadcast settings
Schedules of broadcast settings
Broadcast logs
You can also check with tcode SDMO with text search for required functionality.
Check this link http://csc-studentweb.lrc.edu/swp/Berg/Conferences/SAP_Reporting_analytics_2007/pdf/Track6_session7.pdf
Thank you,
Shyam

BW cache settings and WebI

Hello,
we're trying to tune the BW cache for WebI queries, we'd like to change the default cache settings for a number of queries, including ones used for BO universes.
I'd like to know if this changes will be picked and used by WebI or if it is not sensitive to such changes (Cache Mode and Persistence Mode).
Thanks in advance for your help.

Hello Pablo,
I haven't tried yet but the OLAP cache should be used by WebI when it accesses the queries. You can ensure it does in transaction RSRCACHE by looking at the last access of a cached query. Could also look at the BI stats (if you have installed them and turned then on of course).
Regarding the cache settings, I would personally recommend using the persistent cache (across App Servers if you have more than one app server) into a Cluster table (or Transparent table if the data set is quite large). Can find more details here: http://help.sap.com/saphelp_nw70ehp1/helpdata/en/d9/31363dc992752de10000000a114084/frameset.htm
You could also look into MDX cache instead of OLAP cache, but I haven't played with it yet so I'm not sure it would help with WebI. Anyone else did?
Hope it helps...

MDX strtomember and +

Hi,
Hope I'm in the right forum...
Have a problem running an MDX with MDX test:
SELECT {[0CALMONTH].[200910],
StrtoMember("[0CALMONTH].[20091" + "1]")}
ON 0 FROM [ZPBSD_800/ZPBSD_800_QA_BO_001]
I always get the error message "invalid MDX command with +"
When I write it as
SELECT {[0CALMONTH].[200910],
StrtoMember("[0CALMONTH].[200911]")}
ON 0 FROM [ZPBSD_800/ZPBSD_800_QA_BO_001]
it works. Of course I want to replace the + "1" with something more special, but if not even this thing works I cannot go on.
Anyone have an idea?
We are on SAP 7.0 EnhP 1

Hi,
this looks identical to this entry here:
Re: MDX Cache and WEBI
Ingo

Multicube Performance

Dear All,
I have performance issue in one of my query.
This query is build from MultiProvider, which is contains 2 InfoCube.
What I'm already do:
1. Build aggregate in each infocube and when I check via RSRT, they found it.
2. Check related master data, infocube and query via RSRV and all object are fine.
3. Setting Read Mode and Cache Mode in query properties.
I choose Read Mode = H - Query Read when you navigate or expand
and for Cache Mode = 4 - Persistent Cache Accross Each Application Server, since this query is accessed with many user.
4. Recreate DB Indexes and DB Statistics in tab Performance (InfoCube - Manage) for each infocube.
5. Check via DB20, DB Statistic for related table (fact and dimension) is up to date.
Is there anything else that I can do? I already frustated with user's complaining in this week.
Really appreciated any kind of helps, Thanks.
Regards,
Steph

Are you using BW3.5?
In BI7, under distribution type we gets following options:
Broadcast E-Mail (Bursting)
Broadcast by Exception
Broadcast (Multi Channel)
Precalculating Value Sets
Filling the OLAP Cache
Filling the MDX Cache
You have to use "Filling the OLAP Cache" option for Distribution type.

SMD on SP15: no data for E2E Workload Analysis are shown

Hello!
I have successfully run Setup Wizard for the satellite solution "EP Portal on 6.40".
Unfortunately no data for E2E Workload Analysis are shown since more than one month.
I use SAP Solution Manager with SP 15, BI CONT 9
I have implemented the following SAP notes:
1088163, 1107804, 110782, 1119766
The jobs E2E_EXTRACTOR_CONTROLLER are running without errors.
Enclosed one of those for portal solution:
09.04.2008 E2E: Extractor Controller 1
EC: 09.04.2008 13:05:52 UTC Extractor Controller started for SID B11
EC: 09.04.2008 15:05:52 CET Installation Number 0020198811
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component
EC: 13:05:52 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:52 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:52 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:54 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/APPLOG_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/APPLOG_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/APPLOG_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/DUMP_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
09.04.2008 E2E: Extractor Controller 2
ME: 13:05:54 UTC Calling Extractor /SDF/DUMP_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/DUMP_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/SYSLOG_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/SYSLOG_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/SYSLOG_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/UPDATE_EXTRACTOR
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor /SDF/UPDATE_EXTRACTOR ,
Extractor Class:
ME: 13:05:54 UTC Receiving return code 98 from
/SDF/UPDATE_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:54 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: 13:05:54 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
09.04.2008 E2E: Extractor Controller 3
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:54 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:55 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:55 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 13:05:56 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 09.04.2008 0 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 09.04.2008 00 h to 09.04.2008 12 h
ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 13:05:56 UTC Receiving return code 6 from
E2E_JAVA_EXTRACTOR_IF
ME: Error:
DATA_RETRIEVAL_EXCEPTION
EC: 13:05:56 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200006685
EC: 13:05:56 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:56 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:05:57 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:05:57 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_RFC
EC: Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR
09.04.2008 E2E: Extractor Controller 4
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:05:58 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 08.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type b) detected: From 08.04.2008 12 h to 09.04.2008 11 h
RR: Interval (Type c) detected: From 08.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:58 UTC Calling Extractor /SDF/IDOC_THROUGHPUT_EXTRACTOR ,
Extractor Class:
ME: 13:05:58 UTC Receiving return code 98 from
/SDF/IDOC_THROUGHPUT_EXTRACTOR
ME: Error:
ME: Error - No RFC Destination maintained for remote execution.
EC: 13:05:58 UTC Main Extractor raises exception. No Data returned by extractor.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F60_XI_E2E_PROXY_STATS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:05:58 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:05:58 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
ME: No Data Found.
ME: 13:06:00 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_C_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_C_TRANSPORTS
09.04.2008 E2E: Extractor Controller 5
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_NOTES
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_NOTES
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_W_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 1
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:01 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor F90_CA_W_TRANSPORTS
ME: No Data Found.
ME: 13:06:01 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:01 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:01 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF ,
09.04.2008 E2E: Extractor Controller 6
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 13:06:02 UTC Receiving return code 0 from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:06:02 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F55_XI_IDOC_ADAPTER
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:02 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:02 UTC Calling Extractor F55_XI_IDOC_ADAPTER
ME: No Data Found.
ME: 13:06:02 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F60_XI_E2E_PROXY_STATS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F60_XI_E2E_PROXY_STATS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Invalidating MDX Cache.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_C_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_C_TRANSPORTS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
09.04.2008 E2E: Extractor Controller 7
EC: Extractor F90_CA_NOTES
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_NOTES
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_ST_API
EC: Extractor F90_CA_W_TRANSPORTS
EC: Extractorclass
EC: Product 01200314690900000192
EC: Main Instance (1) 9
EC: Main Instance (2) 01200314690800000134
EC: Component 01200615320200005507
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_ST_API Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 02.04.2008 12 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor F90_CA_W_TRANSPORTS
ME: No Data Found.
ME: 13:06:03 UTC E2E_ME_ST_API Main Extractor Run finished.
EC: Main Extractor E2E_ME_RFC
EC: Extractor E2E_SSR_EXTRACTOR_IF
EC: Extractorclass
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component 01200615320200005507
EC: Local Execution of Extractor.
EC: ME called in Multi-Mode.
EC: 13:06:03 UTC Calling ME.
EC: Read Destination
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval: From 09.04.2008 00 h to 09.04.2008 12 h
RR: Interval (Type e) detected: From 09.04.2008 12 h to 09.04.2008 12 h
ME: 13:06:03 UTC Calling Extractor E2E_SSR_EXTRACTOR_IF ,
Extractor Class:
E2E_SSR_EXTRACTOR_0CCMSATPH
ME: 13:06:06 UTC Receiving return code 0 from
E2E_SSR_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 13:06:06 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence: 0
EC: Invalidating MDX Cache.
Any helpful information will be appreciated
regards
Thom

Same problem being observed in our Solman system (SP15). Below are the errors observed in the spool output of E2E framework jobs,
1] ME: Data Loader Error occurred.
   EC: 21:05:44 UTC Main Extractor raises exception. No Data returned by extractor.
2] No action - TSL parameter detected.
   This extractor is not allowed to run outside time frame
3] ME: 21:05:45 UTC Receiving return code    98   from
   /SDF/UPDATE_EXTRACTOR
   ME: Error:
   ME: Error - No RFC Destination maintained for remote execution.
   EC: 21:05:45 UTC Main Extractor raises exception. No Data returned by extractor.
4] ME: Error:
   DATA_RETRIEVAL_EXCEPTION
   EC: 21:05:46 UTC Main Extractor raises exception. No Data returned by extractor.
Tried referring E2E workload analysis guide...no use..the issues have not been covered in that.

SMD: no data for E2E Workload Analysis are shown

Hello,
I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 3) and would set up the SMD functionality for SAP EP 6.40 SP19.
The Set up Wizards runs without any errors and I could see the data in all the steps (E2E Workload, E2E Change Analysis).
Unfortunately since 2 months I can see any data in (E2E Workload, E2E Change Analysis, E2E Exception Analysis).
The E2E_EXTRACTOR_CONTROLLER job runs and is enclosed here
16.04.2008                  E2E: Extractor Controller                          1
EC: 16.04.2008 14:05:11 UTC    Extractor Controller started for SID E11
EC: 16.04.2008 16:05:11 CET    Installation Number                   0020198811
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component
EC: 14:05:11 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:11 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:12 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:14 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component           01200615320200006685
EC: 14:05:14 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:14 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:16 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:16 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component           01200615320200006685
EC: 14:05:16 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
16.04.2008                  E2E: Extractor Controller                          2
RR: Scanned Interval:            From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:16 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:18 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:18 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: 14:05:18 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:18 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:20 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:20 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: 14:05:20 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:20 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
16.04.2008                  E2E: Extractor Controller                          3
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:21 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:21 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
Can some one help to solve this problem.
Thank you very much
regards
Thom

Hello,
I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 3) and would set up the SMD functionality for SAP EP 6.40 SP19.
The Set up Wizards runs without any errors and I could see the data in all the steps (E2E Workload, E2E Change Analysis).
Unfortunately since 2 months I can see any data in (E2E Workload, E2E Change Analysis, E2E Exception Analysis).
The E2E_EXTRACTOR_CONTROLLER job runs and is enclosed here
16.04.2008                  E2E: Extractor Controller                          1
EC: 16.04.2008 14:05:11 UTC    Extractor Controller started for SID E11
EC: 16.04.2008 16:05:11 CET    Installation Number                   0020198811
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component
EC: 14:05:11 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:11 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:12 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:14 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component           01200615320200006685
EC: 14:05:14 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:14 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:16 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:16 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product
EC: Main Instance (1)
EC: Main Instance (2)
EC: Component           01200615320200006685
EC: 14:05:16 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
16.04.2008                  E2E: Extractor Controller                          2
RR: Scanned Interval:            From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:16 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:18 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:18 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: 14:05:18 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 16.04.2008 01 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:18 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 14:05:20 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:20 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: 14:05:20 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 09.04.2008 13 h to 16.04.2008 13 h
RR: Interval (Type e) detected: From 16.04.2008 13 h to 16.04.2008 13 h
ME: 14:05:20 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
16.04.2008                  E2E: Extractor Controller                          3
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 14:05:21 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 14:05:21 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
Can some one help to solve this problem.
Thank you very much
regards
Thom

Broadcaster Distribution Types

Hi All,
I want to precalculate the 7.0 web template so that it won't hit the queries improving performance. I am looking for functionality similar to 3.5 reporting agent settings for web templates (precalculating only data and accessing via DATA_MODE=STORED). I'm on BI 7.0 SP10 with FPN.
When I create a setting in broadcaster for a web template I see only following distribution types:
Broadcast email
Broadcast to portal
Broadcast to printer
Broadcast email Bursting
Broadcast multi channel
When I create a setting for QUERY i see following additional distribution types
Broadcast according to exception
Precalculate value set
Fill OLAP cache
Fill MDX cache
But i don't see the distribution type "FILL PRECALCULATION STORE" which is mentioned on help.
http://help.sap.com/saphelp_nw04s/helpdata/en/54/6e6f422f91c153e10000000a1550b0/frameset.htm
Also, if i refer to documentation for creating broadcast setting it doesn't mention about this distribution type:
http://help.sap.com/saphelp_nw04s/helpdata/en/4a/337f42fb623150e10000000a1550b0/frameset.htm
Kindly help.
Thanks.
Abhijeet
Points will b awarded for every answer..

Please see the message from BI development team I got after creating an OSS for this same issue.
"A "broadcasting into the precalcualtion store" is not possible.
By mistake it was in the documentation and some rollout material for
a while but this has been corrected.
There are alternative scenarios: e.g. precalculation of webtemplates
followed by sending them to users per e-Mail or put them on a file
share via "Export to KM".

E2E Workload: No data/graphic is available

Hi!
I have succcessfully set up SMD.
Unfortunately I can see any data under the E2E Workload tabs.
The job E2E_EXTRACTOR_CONTROLLER runs and retrieves the data for the solution.
Has some one exprerience how to proceed?
P.S. I have SAP Solution Manager 4.0 SP 13
Thank you very much
regards
Thom

Hi Frederic,
I miss the data as well in Overview (empty graph) as also in in system tab.
Enclosed you will find the E2E_EXTRACTOR_CONTROLLER of portal solution
07.02.2008                  E2E: Extractor Controller
        1
EC: 07.02.2008 09:05:57 UTC    Extractor Controller started for SID
E11
EC: 07.02.2008 10:05:57 CET    Installation Number
0020198811
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_CA_CS_EXTRACTOR
EC: Extractorclass
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: No action - TSL parameter detected.
EC: This extractor is not allowed to run outside time frame:
EC: From 03 h to 05 h CET
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eEAExtractor
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: 09:05:57 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 06.02.2008 20 h to 07.02.2008
08 h
RR: Interval (Type e) detected: From 07.02.2008 08 h to 07.02.2008
08 h
ME: 09:05:57 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eEAExtractor
ME: 09:06:06 UTC Receiving return code     0   from
E2E_JAVA_EXTRACTOR_IF
ME: No Data returned by Extractor with no Error detected.
ME: 09:06:06 UTC E2E_ME_RFC Main Extractor Run finished.
ME: Number of records written to persistence:           0
EC: Invalidating MDX Cache.
EC: Main Extractor      E2E_ME_RFC
EC: Extractor           E2E_JAVA_EXTRACTOR_IF
EC: Extractorclass
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
EC: Product             01200314690900000192
EC: Main Instance (1)   7
EC: Main Instance (2)   01200314690800000134
EC: Component
EC: 09:06:06 UTC Calling ME.
EC: Read Destination SOLMANDIAG
ME: E2E_ME_RFC Main Extractor Run started.
RR: Calculating Required Records.
RR: Scanned Interval:            From 31.01.2008 08 h to 07.02.2008
08 h
RR: Interval (Type b) detected: From 05.02.2008 11 h to 07.02.2008
07 h
RR: Interval (Type c) detected: From 05.02.2008 11 h to 07.02.2008
08 h
ME: 09:06:06 UTC Calling Extractor E2E_JAVA_EXTRACTOR_IF          ,
Extractor Class:
com.sap.sup.admin.bwextract.E2eWAIntroscopeExtractor
ME: 09:06:07 UTC Receiving return code     1   from
E2E_JAVA_EXTRACTOR_IF
ME: Error:
INTROSCOPE_SQL_EXCEPTION
EC: 09:06:06 UTC Main Extractor raises exception. No Data returned by
extractor.
What do you think: make it perhaps sence to patch SOLMAN to SP 14?
Thank you!
regards
Thom

Information Broadcating problem

Hi All,
                   When we are trying to configure the Information Broadcasting from Bex analyzer it is throwing " error : 0BROADCASTING_TEMPLATE " . We have installed this from Business Content but no luck . We are on NW 2004s .Do we need Java stack for Information Broadcasting .

Hi Ajay,
I got some document where I can see in New Distribution Type (Information Broadcasting Settings) options like
1.     Fill OLAP Cache,
2.     Fill MDX Cache,
3.     Fill Precalculation Store
4.     Send E-Mail etc.
Out of these I am only seeing Send-Email option and not the others. Is this because we are not using Java Stack. Further I think in Output Option we wont get PDF type as we are not using Java Stack. Please let me know if my understanding is correct

Passing date range parameters in MDX Query

Following is my mdx query
SELECT NON EMPTY
    [Measures].[Cache Attendees Count]
ON COLUMNS,
NON EMPTY
    ([Cache Attendees].[Visit Id].[Visit Id].ALLMEMBERS *
    [Cache Attendees].[User Id].[User Id].ALLMEMBERS *
    [Cache Attendees].[Screen Name].[Screen Name].ALLMEMBERS *
    [Cache Attendees].[User Type Id].[User Type Id].ALLMEMBERS *
    [Cache Attendees].[User Type Name].[User Type Name].ALLMEMBERS *
    [Cache Attendees].[Group Date Count].[Group Date Count].ALLMEMBERS *
    [Cache Attendees].[Insert Time Stamp].[Insert Time Stamp].ALLMEMBERS )
    DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS FROM
    SELECT
            STRTOMEMBER(@FromCacheAttendeesInsertTimeStamp) : STRTOMEMBER(@ToCacheAttendeesInsertTimeStamp)
        ) ON COLUMNS FROM (
        SELECT
            STRTOSET(@CacheAttendeesConferenceId) ) ON COLUMNS FROM [Cube_Attendee])
        WHERE ( IIF( STRTOSET(@CacheAttendeesConferenceId).Count = 1, STRTOSET(@CacheAttendeesConferenceId), [Cache Attendees].[Conference Id].currentmember ) )
CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS
I want to filter my cube with three parameters
1. @CacheAttendeesConferenceId
2. @FromCacheAttendeesInsertTimeStamp
3. @ToCacheAttendeesInsertTimeStamp
When i pass following parameters
ConferenceId = 1, StartDate='2010-01-28T00:00:00', EndDate='2010-02-03T00:00:00'
Then it show records
But When i pass following parameters
ConferenceId = 1, StartDate='2010-01-27T00:00:00', EndDate='2010-02-03T00:00:00'
Then it display message No Data Available
PLease help me on this issue why not FromDate & ToDate range works properly.

Step1:- First i create a SSAS datasource. Then i create a cube for my table CacheAttendees.
It has following columns:-
[Cache Attendees].[Conference Id]
[Cache Attendees].[Group Date Count]
[Cache Attendees].[Insert Time Stamp]
[Cache Attendees].[Screen Name]
[Cache Attendees].[User Id]
[Cache Attendees].[User Type Id]
[Cache Attendees].[User Type Name]
[Cache Attendees].[Visit Id]
Step2:- Then i create a dimension with this cube with all columns.
Step3:- Then i deploy my SSAS project.
Step4:- Use SSAS datasource in my SSRS datasource.
Step5:- Create a report with chart control. Add a parameter ConferenceId. Set default to 1. When i preview my report then it show Cache Attendees].[Conference Id].[1] in header of report instead of that, When i pass the parameter value as 1 then report cannot show & throw an error. I want to pass this parameter at runtime.
Step6:- Please help me how is it possible to pass parameter at runtime.

Problem with Displaying MDX in RSCRM_REPORT

I have read forum messages that the RSCRM_REPORT or RSCRM_BAPI can display a query's MDX statement.
I'd tried to enable the "Display MDX Statement" menu option in both transactions. All I can see is an empty MDX pane at the bottom of screen with menu icons, but no actual MDX statement text. I am able to run "Execute Report" and get the results, but still don't see any MDX statement.
What am I missing here? Are there steps needed to enable this feature?
Thanks for any help.
Linda

Hi Immanuel,
Have you tried clearing the cache? My guess is, it is probably a defect.
Regards,
Vikram

MDX cache

Similar Messages

Maybe you are looking for