E2E Change Analysis

I am unable to see E2E change analysis tab in SMD. I can see E2E exeption,trace and workload analysis but not Change analysis....Can anyone of you please let me know if i need to do any configuration for this....
REWARD POINTS FOR ALL USEFUL ANSWERS...
Thanks,
Ajay Kande

Thnx  a lot Frederic.
Can you tell me regarding the following error:
type com.sap.sup.admin.e2e.trace.wd.model.types.Syuzeit could not be loaded: com.sap.dictionary.runtime.DdException: TypeBroker failed to access SLD: Error while obtaining JCO connection.
I am getting this error when i try to execute E2E Trace Analysis....

Similar Messages

  • E2E Change Analysis Function

    Hi All,
    Is E2E Change Analysis functionality of SolMan 7.1 able to track changes made in configuration object of Solar02-config tab? How do I know who has changed what configuration object and what changes has been done?
    Any response is helpful!
    Thanks,
    Shaun

    Hi Shaun,
    Do you know transaction solar_eval? It is used to report many data from the project/solutions/test workbench area. It currently has no option to report the history of changes of the objects, but when the SP05 for solman 7.1 comes out, it'll enhance this functionality adding the option to report the history of changes of the tabs or the history of changes of the documents.
    kind regards, Fabricius

  • Error while accessing E2E Change Analysis via SMD

    Hi All,
    I am having below mentioned error while accessing E2E Change Analysis via SMD.
    Error loading template 0TPL_0SMD_CA01_Q0001 
    Notification Number BRAIN 276 
    Let me know if you are aware about the solution.
    Regards,
    Vinit Pagaria

    Is the Queries and templates activated completely in BI-content/Client?
    Please check the same and if needed activate the queries again by running report :CCMSBI_SETUP_E2E
    Also refer to the SAP Note 1342231 - ST: Manual actvtn. of BI Content for E2E diagnostics SP18-22.
    Revert for any issues pls.
    Thanks,
    Jagan

  • 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

  • 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 doesn’t solve the issue, try to do Manual activation of BI Content for E2E Diagnostics.  (note 1110013)
    Hope this helps.
    Thanks,
    Labinot

  • Work Ceters error in change analysis: "No config stores found"

    Hello,
    I have configured E2E diagnostics succesfully, but when i try to view change analysis (Root cause analysis) for my ECC development system, an error appears:
    "No config stores found for 'EC1 0020256704 ABAP or no changes found"
    Any of you have any idea about this problem?
    Thanks and regards
    Carlos

    Hi  Guys
    In order to solve this issue , please refer to this SAP Note  below
    1392544 : E2E Change Analysis - Wrong "No store or no changes
    If this above doesnt solve the issue then please follow these steps belo
    w.
    1.) Make sure the JAVA and ABAP stack are relevent as per this note belo
    w
    1274287 : End-to-End Diagnostics SP18(EHP1)- SP19 - SP20 -
    2.) Please make sure that you have applied the central note
          1334252 SAP Solution Manager - Basic functions (SP20/21)
    and check if you are able to activate the following objects in
    SE80 via the context menu.
    Classes: CL_WD_COMPONENT_ASSISTANCE
    3.)  Make sure the user SOLMAN_ADMIN has profile S_SMDIAG_E2E
    3.) Afterwards, for system ID in subject . make sure the main Instance is been sele
      cted as per this document 
    https://websmp204.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000703907
    &_SCENARIO=01100035870000000112&_OBJECT=011000358700000074392009E
    4.)
    Run the Managed Setup wizard from SOLMAN_SETUP -> Managed System
    Configuration, step 4. Configure Diagnostics.i.e the Main Instances that should be selected in
    the wizard step.Ensure the wizard runs with no errors.
    I am sure this will fix the issue
    Best Regards
    Jai Wardhan

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

  • RCA error in change analysis "No config stores found "

    Hi,
    I have configured E2E RCA in solman.
    In solman_workcenter t.code. RCA -> E2E ->select system->if i click change analysis it  is showing errror "No config stores found for 'GRD 0020251123 ABAP or no changes found' '' .
    but if i click trace, exeception and workload i get graph.
    i checked [Work Ceters error in change analysis: "No config stores found"] , but still i get the error.
    Plz help to solve the issue.
    Regards,
    Karthik

    hi
    why dont you check all the lists given by JAI in the thread
    [Work Ceters error in change analysis: "No config stores found"|Work Ceters error in change analysis: "No config stores found"]
    jansi

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

  • The Filter "Time Frame" in Sales Pipeline Change Analysis

    Dear support.
    In Sales Pipeline Change Analysis,
    The Filter "Time Frame" can select only
    "Last 7 Days","Last 30 Days","Last 90 Days".
    I want to select other days(10days,60days...etc)
    Is it possible to define it by customization?
    Regards.

    Dear experts
    I don't have good solution and I am troubled.
    Is not there the good wisdom?
    Regards.

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

  • 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

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

  • E2E trace analysis in Solman

    Dear all,
    I have some question about the E2E trace analysis on solman. Hope you can help me!~
    1. We are using Solman 7.1 SP6 and we will upgrade to SP10 or SP11 in recent months. We want to use solman RCA trace analysis to trace ERP ABAP program. Could anyone can told me how to do this? I can do the HTTP trace in solman with RCA trace analysis but I don't know whether we can also nalysis the ABAP trace in solman.
    2. We have many printers in our PRD systems and all printers connected to a SPRINTER server. Now we need some suggestion on how we can monitoring these printers with solman. Also we hope to use the RCA tools to nalaysis the problem on printer such as the printer are offline/dead halt/printing very slowly and so on.
    Is this possible?

    Hi Yushuai,
    1. Using E2E in SolMan you can capture the movement of request and response to any JAVA and ABAP system. It will show you that what ABAP program has been called but It will not tell you what happening inside ABAP program.
    Regards,
    Ravi Maheshwari

  • E2E Exception Analysis

    Hi All,
    I have configured SMD (Solution Manager Diagnostics) on SM 4.0 SP12 and I also have setup IntroScope agent and EP agent succesfully.
    When trying to run the program E2E Exception Analysis I get the next message:
    "This application is not yet configured. Please refer to the E2E post-installation steps". Unfortunately I cannot find any documentation about these post installation steps.
    Can you please help me out?
    Regards,
    Koen

    Hi Koen,
    E2E functionalities are very difficult to setup manualy.
    In SPS12, you should order a E2E Diagnotics starter pack.
    General availability of E2E tools is SPS13 (automatic setup).
    Regards,
    Xavier Picquart

Maybe you are looking for