Solution manager 3.2 Test

Dear sap developers,
I am currently using ecatt to record business scenarios in different satellite systems from solution manager 3.2, and when I record MM , FI or PP transactions by using ECATT from solman in R/3 system a popup appears with "transaction not found in the target system" but when I try to record technical transaction it works., (RFC connection works in both sides, Solman and SAP R/3 4.6, authorization problems).
1st I choose the target system and I select the recorder type TCD, finally I enter the transaction, it works only for technical tcodes like su01, se80, also spro but not for mm01, va01 etc.
At the beginning of the recording when I try to display the whole transactions by using the match code the SAP menu contain only Solman menu not Logistics, Accounting of my target R/3 menu.
How can I record Logistic transactions in the target system from solman?
And in eCATT editor when I click the Pattern button I have only limited commands, how can I have the whole list of commands? The insert statement menu starts with command instead of Group.
Thank you very much for your help,
Aklilu

Hi Prakhar,
go there:
http://help.sap.com/saphelp_sm32/helpdata/en/index.htm
and click on Test Organization, there you are
Regards,
Pascal

Similar Messages

  • Solution Manager for Deploy, Test, Trace....

    Hi All,
    We have developed some custom java based components.
    I want to know how can we use the <b>Solution Manager</b> to do the following;
    <b>Deploy, Test, Trace, Performance tuning and trouble shooting..</b>
    Where can i find Solution Manager documents related to the above.
    Any help would be highly appreciated.
    Thanks in Advance.
    Thanks..

    Hi,
    Please refer these notes:
    1258458 - WD ABAP ALV incorrect aggregation values or short dump
    2047023 - 500 SAP Internal Server Error. ERROR Access via 'NULL' object reference not possible (termination: RABAX_STATE) when viewing a product system in LMDB (SOlution Manager 7.1)
    1757238 - Getting short dump SINGLE_EXIT_MULTIPLY_ACTIVE in transaction CRM_DNO_MONITOR
    1801284 - SOLMAN_WORKCENTER abends
    Divyanshu

  • Error opening a Test Script inUFT from Solution Manager

    This error is the subject of a call with SAP and HP but I wondered if anyone else has come across this problem.
    We work with Solution Manager 7.1 (SP11) and HP's UFT 11.53 to create automated testing. We ustilise the two free seat licences for UFT that are provided via enterprise support. We do not use HP's Quality Centre.
    On some occasions when trying to open a test script for editing UFT tries to open and then closes again. The error message below is displayed in solution manager.
    “External Test Tool Quick Test Professional Is Busy and Cannot Create a New Test Script”
    When this happens the local cache files are wiped. We have managed to salvage some of these scripts by pasting in copies of the cache file from another PC but some we had to recreate from scratch.

    If you don't have one already create a gateway instance on your Content Server.
    Change or create the RFC destination :  SAPKPROTP   type = T
    Check the radio button to start on Expicit Host 
    Enter the program = c:\winnt\sapkprotp.exe
    Enter target  host - use the hostname of the server for your Content Server
    Enter the Gateway information
    Regards,
    Brian

  • Solution Manager Test Management Process

    Hi,
    I have been assigned for a solution manager task for test process,I have used for uploading and downloading the documents ,the transaction used solar01 and solar02.
    The process includes right from for eg.FS ,TS till CR,in future if anyone access can see the complete tree of the CR(Change Request.
    How to provide the link between if anyone access CR to see the entire tree.
    I have given the requirements below.
    Description: There is no standard framework for test management , specifically the application support domain. Presently, all test efforts (unit test, integration test, non-regression test, stress test, acceptance test) are managed and executed on project or change level, i.e subject to discretion and goodwill of the individual project manager / change owner. In order to strengthen both the test process and tool support, the global Solman is to be prepared for that. Proposed phased approach is:
    a.       Familiarize and explore standard Solman functions and features for test management in global Solman (test client); hands-on tests to be started after completed IBM migration
    b.      Setup sample test plan and cases, load sample content (test script). Select appropriate test use case independently and in close communication with local contact or project mgr.
    c.       Document and showcase sample to SAP COE and representatives.
    d.      Offer and decide on deployment options.
    e.       Provide ongoing support and coaching; documentation; break-fix support as needed (expected: minimal)
    Test automation and non-SAP test mgmt are not in scope .
    Guide me,since the target date is fixed
    Regards,
    Anu

    Hi,
    As far as I know the only solution for this would be to split it in two test cases, so you can assign the two testers in sequence.
    You can assign the same test case for multiple testers but you can't split half of it for each tester.
    Kind regards,
    Fabricius

  • Solution Manager and HP Quick Test Connection.

    Hello Gurus,
    We want to use Solution Manager to make test for our developments, but our corporate tool for this is HP Quick Test.
    As far as I know it's possible to connect Solution Manager to HP Quick Test. Does anybody know about it?
    Thanks in advance.

    Hi,
    Are u mentoning about HQ Quality Center? If yes, these documents might help:
    SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario-Specific Settings -> Third Party Integration -> SAP Quality Center by HP -> Integration Test Management ...
    Also check SAP Note 1059350 - Installing SAP Adapter for SAP Quality Center by HP.
    Rajeev

  • Connection between Solution Manager Testing und Test Workbench

    Hello,
    I have Problems understanding the connection between the test organization in the solution manager and the test workbench in the corresponding sap system.
    The documentation says that the Solution Manager reuses the test workbench functionality. It is not clear for me how this connection works. In the solution manager you define test cases in the configuration of the project. When you create a test plan in the solution manager you can use the testcases of the project. But when you execute the testcases you do it in the corresponding sap system where the transaction of the test case is. Does this mean that the test cases und test plans that you create in the solution manager are transported to the target sap system? If this is true, when is the transport taking place?
    Thanks a lot!
    Regards, Lars.

    Hi Lars,
    I think you are confused with solution manager and tools like QTP.
    The difference between solution manager and QTP/ECATTT is the eCATT or QTP are used for creating the test scripts or the test cases but solution manager is used for storing all types scripts centrally.
    It means say you have manual test scripts eCATT and Ext QTP scripts lying on the R/3 servers but from solution manager you can create a project comprises of all the scenario and linked test cases of various type.
    Now at a later time when you start testing a manager login to solution manager enter the test plan project name etc and can check what is the current status of the test
    1. how much testing is completed
    2. Who is the tester what is the test script where or on which testing took place etc
    you can check my weblog to knw how to manage and perform testing via solution manager.
    /people/community.user/blog/2006/12/07/organize-and-perform-testing-using-solution-manager
    Please reward points for the same.

  • Upload of Test Cases in SAP Solution Manager.

    Hello,
    I am trying to create a project and its component in SAP Solution Manager with 12 Test Plans. The Test Plans have different number of test cases. I do not have the Test cases now, but I shall have them in future. I currently have the following data.
    Test Plan ID
    Module
    Business Process
    Business Area
    Sub Business Area
    Test Case Description
    Test Case Details
    Transaction Codes
    Priority of Test Cases
    Can I create a structure of a project in the development system in which I have 12 Test Plans and n number of Test Cases under every Test Plan? The structure would have place holder for each test case in which I can upload the Test Cases later. Is that possible?
    Regards,
    Namrata.

    Hi Namrata,
    Yes, you can create project structure before using solar01 tcode. later once your test cases (either manual or automatic) are ready then you can upload them using solar02 on test cases tab,
    refer Link Test Case to Transactions/Reports - Configuration - SAP Library
    Assignments - SAP Solution Manager - SAP Library
    Thanks
    Jansi

  • User Manual for Solution Manager

    Friends,
    For a first time user of Solution Manager, is there documentation available to guide one through the rigour? Maybe a user manual on how to effectively harness Solution Manager during the project implementation cycle.
    Thanks and Regards,
    Sameer Aroskar

    you can also check this
    <a href="/people/community.user/blog/2006/12/07/organize-and-perform-testing-using-solution-manager and Perform Testing using Solution Manager</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ce0b74e3-0601-0010-29a0-f2a6af98ef06">How SAP Solution Manager Can Smooth Your Next Upgrade Project</a>
    <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2a92c290-0201-0010-4b8f-a2aaaa3b822e">SAP Solution Manager - Test Drive SAP Solution Manager in an Implementation Project</a>
    I hope these will be fine for now
    Regards
    Milton

  • ALL SAP Solution Manager Transaction Code

    Dear experts,
    is there any document or transaction code listing all existing transactions code related to Solution Manager?
    Especially for aministrator profil.
    Thank you very much.
    Best regards,
    Pascal.

    Hi,
    I have searched for documents but couldnt find it.
    I can though provide you with a gud no of t-codes:
    RMMAIN - Roadmap
    SOLAR_PROJECT_ADMIN - Project Administration
    SOLAR01 - Business Blueprint
    SOLAR02 - Configuration
    STWB_2 - Test Plan Management
    STWB_WORK - Testing
    SOLAR_EVAL - Reporting
    SMSY - System Landscape
    SOLUTION_MANAGER - Solution Manager Operations
    DNOTIFWL - Basic Notifications Worklist
    CRM_DNO_MONITOR - Transaction Monitor
    CRMD_ORDER - Transaction Processing
    SBWP - SAP Business Workplace
    SOLAR01C - SAP Solution Manager: Configuration
    STWB_INFO - Test Workbench Information System
    STWB_WORK - Testing
    SCDT_SETUP - Customizing Distribution
    SCOUT - Customizing Scout
    SDCCN- configuring earlywatch alerts
    SMSY_SETUP
    SOLMAN_DIRECTORY-solution directory config.
    DSWP- Solution Overview
    BUSP- generate business partners
    SOLMAN_ISSUE_MGMT - Issue Management
    SLDCHECK - Connection test SLD
    SLDAPIUSER - Customizing SLD API
    AISUSER - SAP Support Portal User Maintenance
    You can also take the list of T-Codes by executing SE16 and checking the contents of Table TSTCT?
    Let me know if this helps
    Rohit

  • Excellent material for SAP TAO with SAP Solution Manager

    Dear All,
    I found SAP TAO material and slides and it is superb for SAP TAO learners, Please go through this link [http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/00e9a828-ad24-2d10-3183-9eec5f5b1c4e|http://www.sdn.sap.com/irj/sdn/index?rid=/library/uuid/00e9a828-ad24-2d10-3183-9eec5f5b1c4e]
    Regards,
    Dasaratha

    hi i was looking for carrier in sap testing..can you provide me some information about the difference between sap solution manager and sap testing
    and i would like to know list of topics that cover SAP testing and software's used for the course.... and i want to know if anyone can provide training on it as you are sap tester...i was looking for institutes on sap testing in Hyderabad..i hardly find any ....
    i hope you get me back as soon as possible

  • Archiving/Deleting Test Messages in SAP Solution manager

    Hi,
    We have configured Service Desk in our solution manager 7.0 with EHP1 system.
    We have created test messages to test the configuration.
    We need to delete these test messages which are appearing in T Code CRM_DNO_MONITOR.
    We run the report "CRM_ORDER_DELETE" but the output is
    Deletion of CRM Documents
    The following document could not be deleted:                 8000000259
    Not possible to delete, a reference exists to a subsequent document
    Number of documents deleted:                                          0
    Number of documents not deleted:                                      1
    So
    We have followed the "Note 1329247 - Archiving Solution Manager Service Desk messages".
    1)
    a)Call transaction DNOTIFWL and set the deletion flag for the Service Desk message. The deletion flag corresponds to the system status I1076 (deletion flag).
    b) Execute the report Z_DELETE_BASIC_NOTIFICATIONS
    The above step we have executed successfully.
    2)
    In CRM
    You cannot delete a service process in CRM. The service process must be archived.
    Call transaction SARA and select the archiving object CRM_SERORD. Archiving involves three steps:
    a) Initial run     Report CRM_ARC_SERORD_CHECK
    b) Write run       Report CRM_ARC_SERORD_SAVE
    c) Delete run     Report CRM_ARC_SERORD_DELETE
    in SARA T Code we have typed  archiving object CRM_SERORD.
    After this what to do??? How to proceed further.
    Can any body suggest us the step by step procedure to archive these test messages.
    Regards,
    Raj

    > In CRM
    > You cannot delete a service process in CRM. The service process must be archived.
    > Call transaction SARA and select the archiving object CRM_SERORD. Archiving involves three steps:
    > a) Initial run     Report CRM_ARC_SERORD_CHECK
    > b) Write run       Report CRM_ARC_SERORD_SAVE
    > c) Delete run     Report CRM_ARC_SERORD_DELETE
    >
    > in SARA T Code we have typed  archiving object CRM_SERORD.
    > After this what to do??? How to proceed further.
    You need to schedule a BGD job to execute this. You can do this from the SARA screen itself, clicking on the 'Job' button. Please refer:
    http://help.sap.com/saphelp_crm50/helpdata/en/e6/c66f3b6c980c3be10000000a11402f/content.htm
    Rajeev

  • Solution Manager 7.0 Installation Error on Import ABAP  -Test DB connection

    Hi, SDN fellows.
    I am installing Solution Manager 7.0. In Step 16 of 44 - Import ABAP, I encountered an error when the installer was testing the database connection. It failed at this command:
    R3load.exe -testconnect
    Below is the error I copied from the log viewer. Thanks for all possible advices/suggestions to fix this issue. 
    =================
    WARNING 2011-07-12 03:51:49.188
    Execution of the command "C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect" finished with return code 2. Output:
    sapparam: sapargv( argc, argv) has not been called.
    sapparam(1c): No Profile used.
    sapparam: SAPSYSTEMNAME neither in Profile nor in Commandline
    C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110712035148
    (DB) ERROR: db_connect rc = 256
    (DB) ERROR: DbSlErrorMsg rc = 99
    WARNING[E] 2011-07-12 03:51:49.188
    CJS-30023  Process call 'C:\usr\sap\SM1\SYS\exe\uc\NTAMD64\R3load.exe -testconnect' exits with error code 2. For details see log file(s) R3load.exe.log.
    ERROR 2011-07-12 03:51:49.204
    FCO-00011  The step testDatabaseConnection with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|testDatabaseConnection was executed with status ERROR .
    =============
    KC

    cont....
    4 ETW000                                                                              33  1.576524
    4 ETW000  [dev trc     ,00000]  Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum: 1112312
    4 ETW000                                                                              24  1.576548
    4 ETW000  [dev trc     ,00000]  DbSlRead - Error 103 (dbcode 208) on open             19  1.576567
    4 ETW000  [dev trc     ,00000]  DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
    4 ETW000                                                                              19  1.576586
    4 ETW000  [dev trc     ,00000]  DbSlRead - Error 103 (dbcode 208) on fetch            13  1.576599
    4 ETW000  [dev trc     ,00000]  DbSlRead - <##Y4ISBDCAPPsm100000045960000000001234118>
    4 ETW000                                                                              18  1.576617
    4 ETW000  [dblink      ,01299]  ***LOG BZA=>table SVERS      does not exist on database            [dblink#5 @ 1299]
    4 ETW000                                                                            8060  1.584677
    4 ETW000  [dev trc     ,00000]  Wed Jul 13 23:41:19 2011                           41342  1.626019
    4 ETW000  [dev trc     ,00000]  DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000002234118
    4 ETW000                                                                              25  1.626044
    4 ETW000  [dev trc     ,00000]  ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
    4 ETW000                                                                            3649  1.629693
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
    4 ETW000                                                                              33  1.629726
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
    4 ETW000                                                                              19  1.629745
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
    4 ETW000                                                                              27  1.629772
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000002234118]
    4 ETW000                                                                              19  1.629791
    4 ETW000  [dev trc     ,00000]  ParamStmtExec failed.  HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP      1 COMPCNT FROM "DDNTT" ]
    4 ETW000                                                                              28  1.629819
    4 ETW000  [dev trc     ,00000]  Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
    4 ETW000                                                                              20  1.629839
    4 ETW000  [dev trc     ,00000]  NTAB: SELECT COMPCNT FROM DDNTT FAILED               277  1.630116
    4 ETW000  [dev trc     ,00000]  DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000003234118
    4 ETW000                                                                              44  1.630160
    4 ETW000  [dev trc     ,00000]  ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
    4 ETW000                                                                             459  1.630619
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
    4 ETW000                                                                              33  1.630652
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
    4 ETW000                                                                              18  1.630670
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
    4 ETW000                                                                              29  1.630699
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000003234118]
    4 ETW000                                                                              23  1.630722
    4 ETW000  [dev trc     ,00000]  ParamStmtExec failed.  HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP      1 VERSION FROM "DDNTT" ]
    4 ETW000                                                                              29  1.630751
    4 ETW000  [dev trc     ,00000]  Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
    4 ETW000                                                                              20  1.630771
    4 ETW000  [dev trc     ,00000]  NTAB: SELECT VERSION FROM DDNTT FAILED               267  1.631038
    4 ETW000  [dev trc     ,00000]  DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000004234118
    4 ETW000                                                                              43  1.631081
    4 ETW000  [dev trc     ,00000]  ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
    4 ETW000                                                                             436  1.631517
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
    4 ETW000                                                                              32  1.631549
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
    4 ETW000                                                                              18  1.631567
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'DDNTT'.
    4 ETW000                                                                              58  1.631625
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000004234118]
    4 ETW000                                                                              19  1.631644
    4 ETW000  [dev trc     ,00000]  ParamStmtExec failed.  HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP      1 DBASE FROM "DDNTT" ]
    4 ETW000                                                                              28  1.631672
    4 ETW000  [dev trc     ,00000]  Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
    4 ETW000                                                                              21  1.631693
    4 ETW000  [dbntab.c    ,00000]  *** ERROR => NTAB: SELECT VERSION/DBASE FROM DDNTT FAILED
    4 ETW000                                                                             284  1.631977
    4 ETW000  [dbntab      ,01276]  ***LOG BZY=>unexpected return code 103        calling NTAB       [dbntab#4 @ 12761]
    4 ETW000                                                                              31  1.632008
    4 ETW000  [twdydbacc.c ,00568]  i:0                                                 8690  1.640698
    4 ETW000  [twdydbacc.c ,00569]  db_fd_p<i>.fname:       PGMID                         20  1.640718
    4 ETW000  [twdydbacc.c ,00570]  db_fd_p<i>.is_key:      0                             11  1.640729
    4 ETW000  [twdydbacc.c ,00571]  db_fd_p<i>.offset:      0                             10  1.640739
    4 ETW000  [twdydbacc.c ,00572]  db_fd_p<i>.db_length:   0                             10  1.640749
    4 ETW000  [twdydbacc.c ,00573]  db_fd_p<i>.fixed_length:4                             10  1.640759
    4 ETW000  [dev trc     ,00000]  DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000005234118
    4 ETW000                                                                              40  1.640799
    4 ETW000  [dev trc     ,00000]  ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
    4 ETW000                                                                             434  1.641233
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
    4 ETW000                                                                              32  1.641265
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
    4 ETW000                                                                              75  1.641340
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
    4 ETW000                                                                              31  1.641371
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000005234118]
    4 ETW000                                                                              18  1.641389
    4 ETW000  [dev trc     ,00000]  ParamStmtExec failed.  HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP      1 COMPCNT FROM "XXXXT" ]
    4 ETW000                                                                              28  1.641417
    4 ETW000  [dev trc     ,00000]  Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
    4 ETW000                                                                              21  1.641438
    4 ETW000  [dev trc     ,00000]  NTAB: SELECT COMPCNT FROM XXXXT FAILED               269  1.641707
    4 ETW000  [dev trc     ,00000]  DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000006234118
    4 ETW000                                                                              44  1.641751
    4 ETW000  [dev trc     ,00000]  ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
    4 ETW000                                                                             437  1.642188
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
    4 ETW000                                                                              32  1.642220
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
    4 ETW000                                                                              18  1.642238
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
    4 ETW000                                                                              28  1.642266
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000006234118]
    4 ETW000                                                                              19  1.642285
    4 ETW000  [dev trc     ,00000]  ParamStmtExec failed.  HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP      1 VERSION FROM "XXXXT" ]
    4 ETW000                                                                              27  1.642312
    4 ETW000  [dev trc     ,00000]  Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
    4 ETW000                                                                              70  1.642382
    4 ETW000  [dev trc     ,00000]  NTAB: SELECT VERSION FROM XXXXT FAILED               273  1.642655
    4 ETW000  [dev trc     ,00000]  DbSlBegRead[1]: ##Y4ISBDCAPPsm100000045960000000007234118
    4 ETW000                                                                              44  1.642699
    4 ETW000  [dev trc     ,00000]  ParamStmtExec: line 13165. hr: 0x80040e14 Statement(s) could not be prepared.
    4 ETW000                                                                             435  1.643134
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 8180, sev 0), Statement(s) could not be prepared.
    4 ETW000                                                                              32  1.643166
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
    4 ETW000                                                                              19  1.643185
    4 ETW000  [dev trc     ,00000]  sloledb.cpp [ParamStmtExec,line 13165]: Error/Message: (err 208, sev 16), Invalid object name 'XXXXT'.
    4 ETW000                                                                              28  1.643213
    4 ETW000  [dev trc     ,00000]  Procname: [##Y4ISBDCAPPsm100000045960000000007234118]
    4 ETW000                                                                              20  1.643233
    4 ETW000  [dev trc     ,00000]  ParamStmtExec failed.  HR 80040e14 DBSL retcode 103. stmt: [SELECT TOP      1 DBASE FROM "XXXXT" ]
    4 ETW000                                                                              30  1.643263
    4 ETW000  [dev trc     ,00000]  Conn_i:1 selection:1 singleton:0 flag_fupd:0 use_cursor:0 chksum: 1122000
    4 ETW000                                                                              21  1.643284
    4 ETW000  [dbntab.c    ,00000]  *** ERROR => NTAB: SELECT VERSION/DBASE FROM XXXXT FAILED
    4 ETW000                                                                             324  1.643608
    4 ETW000  [dbntab      ,01276]  ***LOG BZY=>unexpected return code 103        calling NTAB       [dbntab#4 @ 12761]
    4 ETW000                                                                              27  1.643635
    2EETW000 sap_dext called with msgnr "2":
    2EETW000 -
    db call info -
    2EETW000 function:   db_ntab
    2EETW000 fcode:      NT_RDTDESCR
    2EETW000 tabname:    TADIR
    2EETW000 len (char): 5
    2EETW000 key:        TADIR
    2EETW000 retcode:    2
    4 ETW000  [dev trc     ,00000]  db_con_rollback (con_da={R/3,0,0},th_rollback=1,tx=0)
    4 ETW000                                                                            9946  1.653581
    4 ETW000  [dev trc     ,00000]  Rollback: TestConnection(1) successful             36526  1.690107

  • Solution Manager Testing Procedure

    hi everyone,
    i have configured solution manager for HR Reporting with the following t.codes
    solar_project_admin
    solar01
    stwb_2- where i am not able to find the test cases so i am not able to assign test packages to users and
    in t.code stwb_work when i test the report id doesnot see anything
    pl help me out
    Regards
    Utkarsh

    Hello. You have to create them by using NEW button.
    Bye

  • Can we create a workflow in Solution Manager for Tester Worklist ?

    Hi Friends,
    Actually I have a requirement to create a workflow in solution manager.
    The requirement is to create a workflow for issue log(tester worklist). As soon as a new issue (support message) is created then the wf should get triggered and send out a mail to the resp. person. It just a sending a mail between issue creater and responsible person.
    Can anyone please let me know if we create a wf in Solman or not ? If so please provide me some related buss. obj for that. thanks
    Is there any standard workflow (or similar to that) to make it automatic ? Once the message is created then a mail to the responsible person should go.
    Grateful to your help.
    Srithan

    Sorry Raguraman,
       I am unable to check those tcodes as I havenot got the authorizations for those. after several mails I got some basic wf developer tcode access. I am not sure whether I have to create a new workflow for this or I can go with some built-in technology to send mail when a new message (tcode: stwb_work) is created.
    can raguraman or anyone please help me on doing this ?
    if the solman has provided the standard for sending mails when a new message is created/changed to the responsible person.
    grateful for your help
    Regards,
    srithan

  • Solution manager, PI and ERP incl FICA (IS-U) test systems on same HANA DB server Appliance

    Hello
    I wander is it possible to have Solution manager, PI and ERP incl FICA (IS-U). All for test/system purposes:
    I am sure we need separate application servers for Solution manager, PI and ERP incl FICA (IS-U),
    I would have question regarding Appliance i.e Hana DB server. can Solution manager, PI and ERP incl FICA (IS-U) products reside on same Appliance i.e Hana DB server in MCOS or MCOD? (I am sure that for production use this is no-go option)
    What is the case when renting cloud solution?
    Thank you a lot in advance
    Jan

    Check the java part, most of the Solman Web Based thing use the java, check the management console to ensure message server and dispatcher proper work, normally is: http://hostname:50113.
    If central note give you problems deimplement all the not complete implemented notes and use SUM
    and MOPZ to update your system with the last SP, then apply the central note acording to your SP level.
    We found that have the system in the last level prevents a lot of problems because of not complete implemented notes.

Maybe you are looking for