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

Similar Messages

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 on SP15: no data for E2E Workload Analysis is visible

Hello,
I use SAP Solution Manager 4.0 with (ABAP SP15, BI CONT 703 Patch 9, LM-Service 14 Patch 4) and would set up the SMD functionality for SAP EP 6.40 SP19.
The Set up Wizards runs without any errors but I could see the data in the tabs (E2E Workload, E2E Change Analysis)
The E2E_EXTRACTOR_CONTROLLER job runs without errors.
Which actions should be done to solve the problem?
Thank you!
regards
Thom

Tom,
Make sure that when you ran SMD setup wizard, job CCMSBISETUP completed successfully. Check this in SM37.
Check ABAP runtime errors in ST22.
If you are getting RAISE_EXCEPTION error, apply note 1119766.
Make sure that MultiProvider 0SMD_MPIH is activated. In BI client run transaction RSA1, Modeling, InfoProvider- check if 0SMD_MPIH is active.
If above doesnt solve the issue, try to do Manual activation of BI Content for E2E Diagnostics. (note 1110013)
Hope this helps.
Thanks,
Labinot

E2E Workload Analysis for BI

Hi All,
Currently we are searching for BI - IP workload analysis tools. I come to know that SolMan Diagnostic tool E2E Workload Analysis for BI useful somewhat to measure the work load. Kindly anybody can tell me
1. Is this tool works for JAVA environment or not
2. How it is useful for BI-IP workload analysis
3. Is there any tools like SolMan diagnostic tool.
4. If we install this tool in SolMan what is the impact.
Thxs,
KVA

This is what I get from Application log (slg1) when I try to drill down on system BIJ (java system) and the page under Workload Analysis do not display (WA-Overview) is ok:
SELECT { [Measures].[0SMD_AVG], [Measures].[0SMD_MAX], [Measures].[0SMD_EXS
] } ON 0, NON EMPTY [0SMD_METY].MEMBERS ON 1 FROM [0SMD_MPEH/0SMD_MPEH_WA_Q
0008_H] SAP VARIABLES [0SMD_V_SID] INCLUDING "BIJ_2" [0SMD_V_TIHMFROM] INCL
UDING >= "201008270000" [0SMD_V_TIHMTO] INCLUDING <= "201008272359" [0SMD_V
INFOPR] INCLUDING "0SMDPERH" [0SMD_V_INFOPR] INCLUDING "0SMD_PE2H" [0SMD_
V_MTYPEM] INCLUDING "IVIEWS" [0SMD_V_MTYPEM] INCLUDING "BI RUNTIME SERVICE"
Value "BIJ_2" for variable "E2E SID Variable" is invalid
Type:E, Id:BRAIN, Number:643, System:SMDCLNT001
I applied the note Note 1301656 even if we are already sp23. I also regenerated the query 0SMD* in bi client.
What does Value "BIJ_2" for variable "E2E SID Variable" is invalid mean and how to correct this?

After BI 4.1 configuration in SOLMAN - error message "The systems you selected do not contain any software components currently supported by E2E Workload Analysis"

Hi All,
I'm trying configure E2E monitoring. I configured all necessary steps, I can see my BI 4.1 system in SLD, also in SOLMAN, all “lights” are green. But if I start Root Cause Analysis>> Ent-to End Analysis>> My system>> Workload Analysis, I see this error "The systems you selected do not contain any software components currently supported by E2E Workload Analysis".

It would be better if you can raise the question at Remote Supportability and Monitoring Tools
and or comment in the blog post How to generate and consume an E2E trace with BI4.x (for non-SolMan landscapes)
created by Toby Johnston
Do go through the note 1871260 - The systems you selected do not contain any software
components currently supported by E2E Workload analysis for SAP HANA
Hope they help.

No data in RunSAP workload analysis

Hi Experts,
I've installed solution manager 7.0 EHP1 and configured to execute End-to-End Analysis.
And I can use Wily Introscope Workstation to display realtime data and history data.
But in solution manager workcenter, I can't get any data from workload analysis.
I've used t-code CCMSBISETUP to setup BI and everything looks fine.
What other things should I check?
Thanks!

Hello,
Please make sure that your system fulfills all the pre-requisites. The following note will point you to the right one depending on the release level of your system:
    1274287 End-to-End Diagnostics
Make sure your systems are well defined, as of EHP1 is mandatory the use of SLD. Please check the following document:
   http://service.sap.com/diagnostics
     Media Library...
         SAP Solution Manager Landscape Setup Guide
Further information can be found ate SAP Note 1435043.
   1435043 E2E Workload Analysis - No applicable data found
Regards,
Allam Drebes

E2E Workload analysis-Conditions tab

Hello,
While cheking the E2E workload analysis, I could see three expandable (drill down) tabs in the workload analysis section. 1. Conditions 2. Navigation 3.Metric Data Display. Here I am not abe to understand the functionality of 'Conditions'. Could you please tell me the use of this and how we can use this?
Regards,
Rajeev

duplicate post

Define shipping data for plants / multiple sales areas should be assigned f

Dear All ,
Appreciate of you helped me in this:
I am trying to configure the intercompany STO process, when I reached the step of u201CDefine shipping data for plants u201C I found that the issuing plant is already assigned to sales Area ( 2000 , 60 , 10 ) which represent local sales , but I need to assign the sales area ( 2001 , 60 , 10 ) which represent foreign sales.
Both sales areas should be used because we are doing STOs with a local company here in jordan and another one in Algeria , so Is there any way to have both sales areas assigned for the same issuing plant?
Thanks ,
Malik

Hi Malik,
I am afraid this is impossible in SAP standard. For this purpose you have the BAdI ME_PROCESS_PO_CUST. The method PROCESS_ITEM of this BAdI gets one single parameter, IM_ITEM, which is the pointer to the PO item object. This object has a lot of useful methods, among them:
- GET_SHIPPING_DATA gives you the Shipping tab of the PO item derived by SAP, among them the ship-to number
- SET_SHIPPING_DATA allows you to amend the data on the Shipping tab
Let your ABAPer implement the BAdI and program its method PROCESS_ITEM.
BR
Raf

Reset SMD-Configuration data for the solution

Hello!
I would like to know how to reset the configuration data for the solution in SMD wizard.
The solution has already the status "green" --> "This solution is ready for Diagnostics".
The problem is that I cannot change the settings for the server ("Setup parameters").
The instance number there (98) cannot be changed.
Further question:
how to install the introscope agent via SMD Wizard?
If I choose the solution and press "Setup Introscope Agent" I get the warning:
The landscape definition of the selected system is empty. Operation has been aborted
Furthermore I cannot see any parameters:
neigther for Server Node Details nor for Current VM Parameters. Here I get the warning:
There is no detail available for this server node. Check the Last Operation Result pane for more information.
Any helpful information wil be appreciated.
Thank you very much!
regards
Thom

Hi Thom,
To reset configuration there is possibility to remove Landscape Info using
Diagnostics Administration -> Diagnostics System -> Landscape management.
For your issue with Wily, you must have a solution correctly define. this setup will not work until you have it.
Frederic

Crystal Reports Template : Data for Cash-Flow Analysis

Dear Experts,
We are working on cash flow forecasting model, i.e going forward 12 months, which in written in MS Excel. We update it with actual data recorded in SAP B1 (Ver 8.8 PL18) A manual process.
Was wondering if we can get a crystal report template which contain the following data:
Sales, Purchases, Collections and Payments by BP in a given time (user specified)
BP Code
BP Name
Sales Invoice #
Sales Invoice Date
Sales Invoice Value (total)
Sales Credit Memo #
Sales Credit Memo Date
Sales Credit Value (total)
Purchase Invoice #
Purchase Invoice Date
Purchase Invoice Value (total)
Purchase Credit Memo #
Purchase Credit Memo Date
Purchase Credit Value (total)
BP Receipt #
BP Receipt Date
BP Receipt Value
BP Payment #
BP Payment Date
BP Payment Value
Thank you to all who have answered this question posted earlier under queries, I am hoping we can get a combined report using CR, a feat not possible using SAP B1 Query function. I look forward to your advice.
Regards
Raj

Hi,
I am not familiar with crystal report. But using queries (that already answered) you can create crystal report.
You can also refer how to guide for creating crystal report in sap b1.
Thanks & Regards,
Nagarajan

Why to replicate the data for GTS? (we are on the same client)

Hi Folks,
We have a GTS installed on the same machine as ERP, so GTS and SAP ERP are on the same client.
As I understand the implementation guide we have to transfer all the master data like vendor/clients to GTS.
That would mean we replicate all the vendors and clients.
What is the sense of that? Why do we have to replicate all the data, We are on the same client?
Does GTS cannot use the normal vendor master?
Thx for help
Dieter

Hi,
GTS has its own Database for Business Partners and Material Master, that is why you have to transfer it, even if its on the same client.
For Developpement you can have both on one machine, but for Testing and aspecially for Production SAP recommends to have 2 seperate machines. This for 2 Reasons:
1. GTS Runs some jobs (depending on what you implemented) that are very CPU consuming and you take the risk of putting your CPU to 100%
2. But more important, you will have to patch up GTS many times to cope with new legal regulations, if you have it on the Same machine you have to touch the ERP, wich most companies do not want...
Regards,
Marc

I did some file maintenance and now my itunes icon on my computer cannot find the songs. I have to show were all the data for the individul songs are located in the computer. How do I remap the location of the actual songs, so the computer list can find

did file maint on computer, not ipod list in computer not linked with actual place of songs in computer. What can I do to remap the itunes list in the computer to find actual songs.

You didn't move the library or rename the folder or drive it was in? Are your songs IN the library or are did the library point to them elsewhere on your drive? Obviously something happened, any idea what?

When using "Database diff" selecting other schemas only for compare own objects are shown too!

Hi!
For comparing lot of objects I use a priviliged account z, which can read Schema a and b.
In the compare dialog I set different from the Defaults following Options:
- step 1
- option "Maintain"
- step 3
- button "More"
- select schema a
- button "Lookup"
- mark all objects and shuttle to the right
- repeat for schema b
After the diff report is finished, schema object of account z are listed too, despite I have not selected this.
Best regards
Torsten

Ah, you're using user Z to select objects from A & B?
On step 2, do you have anything selected that you have not picked an object type for using the 'shuttle' in Step 3?
For example, if you picked, 'procedures' and then in the wizard, didn't pick ANY procedures in A or B, it will by default use ALL of the procedures in Z for the compare.

SMD E2E: Configuration Analysis

Hi!
I can already see the data for E2E Workload Analysis.
Unfortunately I cannot see the data under the tab "E2E Configuration".
Can some one tel me how to proceed with with errors/warnings?
No SID found for value 'E11 0020198811012003146909000001927' of characteristic 0SMD_FSRC
Invalid filter on 0SMD_FSRC: Filter changed
Characteristic 0SMD_CSAL was changed in InfoCube 0SMD_CA01. Adjust the query
What I have already done
tcode RSRT --> Gen. query directly --> "0SMD*"
tcode CCMSBISETUP --> Sceanrio "E2E"
Any helpful information will be appreciated
regards
Thom

Hi,
I'm trying to setup E2E. Diagnostics server (BI client in solman) & Managed system setup was done.
I don't see any graphs(at least plain) in solman. I observed that extractor jobs are failing, also i dont see any info objects under solman diagnostics in TC - RSA1.
Please guide.
Thanks in advance.

No data in Workload Analysis overview in E2E Analysis for TREX

Hi,
I'm not getting any data in E2e Workload analysis Overview screen for TREX system. Data is available in all other screens and extractors are running fine. I'm using Solution Manager 7.1 SP10. Kindly help me.
Regards,
Pragadees

Hi Pragadeesh,
Your system landscape definition in SMSY seems to be wrong. The products selected at the Setup Wizard for the managed system must exist in SMSY in order to run the extractos correctly.
Please refer to the Root Cause Analysis Landscape Guide available
at http://service.sap.com/diagnostics -> media library for additional information.
1) Upgrade CIM model according to note 669669.
2) Download the latest version of note 1468591 and apply it using SNOTE
3) Check note 1259109, download the latest configuration file and apply it
Additionally, it is highly recommended to patch your LM-SERVICE SP09
with the latest patch (1) according to note 1599627.
Thanks
Vikram

SMD: no data for E2E Workload Analysis are shown

Similar Messages

Maybe you are looking for