MCOD system  -  Isolation of components

Dear all,
I am having a query in isolating the components in MCOD database. Let me clearly explain the scenario.
Existing Landscape : Sql 2000 , ECC 5 , BW 3.5 and XI 3.0 -- 32 bit
New landscape       : Sql 2005  , ECC 5, Bw 3.5   and XI3.0 -- 64 bit
In One database we have installaed the 3 instances like ECC , BW  and  XI. Now we are going to isolate the components from mcod and going to install seprate instances with seprate databases.
My question is that.  1. Is that posssible to isolate the component individually from Mcod.? is
                                    possible how it can be done?
                               2. what are the steps we need to consider?
                               3. Is that possible to attach the exported from mcod?
        Note: this is the production server so we have down time very less,
Please suggest me with your valuble points
Regadrs
Vijay

Hi markus,
I am trying to export the component in test  and then in production server.
In test server the empty screen is displaying like
*This is r3trans version 6.13 (Release 6.40 -12.12.05 - 14:24:12 )
Unicode enabled version*
In production server its displaying the below
*This is r3trans version 6.13 (Release 6.40 -12.12.05 - 14:24:12 )
Unicode enabled version
2EETW169 no connect possible: u201C connect failed with DBLI_RC_LOAD_LIB_FAILEDu201D*
In test server I have applied the recent patches of  all the below ones,
dbmsslib.dll
r3ldctl.exe
r3szchk.exe
r3load.exe
*In production trans.log contanins
4 ETW000 r3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 23.12.2008 - 10:29:04
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans -d
4 ETW000  trace at level 2 opened for a given file pointer
4 ETW000  [dev trc     ,00000]  Tue Dec 23 10:29:04 2008                                  0.000000
4 ETW000  [dev trc     ,00000]  db_con_init called                                        0.000000
4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                                 0.000000
4 ETW000  [dbcon.c     ,00000]  *** ERROR => Invalid profile parameter dbms/type (or environment variable dbms_type) = <undef>, cannot load DB library
4 ETW000                                                                                0.000000
2EETW169 no connect possible: "connect failed with DBLI_RC_LOAD_LIB_FAILED."
In default profile,, we are maintaing the following variables and i hope you can understand what i am trying to do from my earlier post.
dbms/type = mss
dbs/mss/server = Careview-db
dbs/mss/schema = bwp
dbs/mss/dbname = PRD
In test trans.log
4 ETW000 r3trans version 6.13 (release 640 - 12.12.05 - 14:24:42).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 23.12.2008 - 11:29:16
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans -d
4 ETW000  trace at level 2 opened for a given file pointer
4 ETW000  [dev trc     ,00000]  Tue Dec 23 11:29:18 2008                                  0.000000
4 ETW000  [dev trc     ,00000]  db_con_init called                                        0.000000
4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                                 0.000000
4 ETW000  [dev trc     ,00000]  Loading DB library 'dbmssslib.dll' ...                48  0.000048
4 ETW000  [dev trc     ,00000]  load shared library (dbmssslib.dll), hdl 0          8512  0.008560
4 ETW000  [dev trc     ,00000]      using "E:\usr\sap\BWA\SYS\exe\run\dbmssslib.dll"
4 ETW000                                                                              85  0.008645
4 ETW000  [dev trc     ,00000]  Library 'dbmssslib.dll' loaded                        29  0.008674
4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library dbmssslib.dll
4 ETW000                                                                              25  0.008699
4 ETW000  [dev trc     ,00000]  Version of 'dbmssslib.dll' is "640.00", patchlevel (0.100)
4 ETW000                                                                            1254  0.009953
4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library dbmssslib.dll
4 ETW000                                                                              40  0.009993
4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library dbmssslib.dll
4 ETW000                                                                                0.009993
4 ETW000  [dev trc     ,00000]  New connection 0 created                             228  0.010221
4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              39  0.010260
4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                         37  0.010297
4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:
4 ETW000                                                                              24  0.010321
4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              32  0.010353
4 ETW000  [dev trc     ,00000]  Thank You for using the SLOLEDB-interface           7392  0.017745
4 ETW000  [dev trc     ,00000]  Using dynamic link library 'E:\usr\sap\BWA\SYS\exe\run\dbmssslib.dll'
4 ETW000                                                                               7  0.017752
4 ETW000  [dev trc     ,00000]  dbmssslib.dll patch info                               6  0.017758
4 ETW000  [dev trc     ,00000]    patchlevel   0                                       6  0.017764
4 ETW000  [dev trc     ,00000]    patchno      103                                     5  0.017769
4 ETW000  [dev trc     ,00000]    patchcomment MSSQL: Error in explain with run time (903705)
4 ETW000                                                                               4  0.017773
4 ETW000  [dev trc     ,00000]  np:(local) connection used on CARETEST-DB            423  0.018196
4 ETW000  [dev trc     ,00000]  CopyLocalParameters: dbuser is 'acc'                  22  0.018218
4 ETW000  [dev trc     ,00000]  Tue Dec 23 11:29:19 2008                           30554  0.048772
4 ETW000  [dev trc     ,00000]  Provider SQLNCLI could not be initialized. See note #734034 for more information.
4 ETW000                                                                              51  0.048823
4 ETW000  [dev trc     ,00000]  Using provider SQLOLEDB instead.                     163  0.048986
4 ETW000  [dev trc     ,00000]  OpenOledbConnection: MARS property was not set.      349  0.049335
4 ETW000  [dev trc     ,00000]  Provider Release:08.10.1830                        34245  0.083580
4 ETW000  [dev trc     ,00000]  Provider SQLNCLI could not be initialized. See note #734034 for more information.
4 ETW000                                                                            1086  0.084666
4 ETW000  [dev trc     ,00000]  Using provider SQLOLEDB instead.                      16  0.084682
4 ETW000  [dev trc     ,00000]  Cache sizes: header 68 bytes, 100 names (157600 bytes), 100 dynamic statements (567200 bytes), total 724868 bytes
4 ETW000                                                                           19476  0.104158
4 ETW000  [dev trc     ,00000]  Initializing private procedure name cache.            17  0.104175
4 ETW000  [dev trc     ,00000]  procedure cache created/attached                      43  0.104218
4 ETW000  [dev trc     ,00000]  Connected to db server : [CARETEST-DB] server_used : [np:(local)], dbname: ACC, dbuser: acc
4 ETW000                                                                              38  0.104256
4 ETW000  [dev trc     ,00000]  pn_id:CARETEST-DB_ACCACC                              11  0.104267
4 ETW000  [dev trc     ,00000]  Not using MARS (on sql 8.0)                           15  0.104282
4 ETW000  [dev trc     ,00000]  Connection 0 opened (DBSL handle 0)                  418  0.104700
4 ETW000  [dev trc     ,00000]  The IRow interface is supported by this OLEDB provider
4 ETW000                                                                           76280  0.180980
4 ETW000  [dev trc     ,00000]  Provider SQLNCLI could not be initialized. See note #734034 for more information.
4 ETW000                                                                            1681  0.182661
4 ETW000  [dev trc     ,00000]  Using provider SQLOLEDB instead.                      16  0.182677
4 ETW000  [dev trc     ,00000]  DbSlBegRead[2]: ##Y3CARETESTacc00000063320000000002112919
4 ETW000                                                                           22170  0.204847
4 ETW000  [dev trc     ,00000]  Tue Dec 23 11:29:22 2008                         2853361  3.058208
4 ETW000  [dev trc     ,00000]  NTAB: Structure of NTAB on DB is VERS_B              433  3.058641
4 ETW000  [dev trc     ,00000]  NTAB: standalone processing                           87  3.058728
4 ETW000  [dev trc     ,00000]  NTAB: read profile                                    22  3.058750
4 ETW000  [dev trc     ,00000]  NTAB: rsdb/ntab/entrycount 1000.                      16  3.058766
4 ETW000  [dev trc     ,00000]  NTAB: rsdb/ntab/ftabsize 500.                         15  3.058781
4 ETW000  [dev trc     ,00000]  NTAB: rsdb/ntab/irbdsize 100.                         15  3.058796
4 ETW000  [dev trc     ,00000]  NTAB: rsdb/ntab/sntabsize 100.                        20  3.058816
4 ETW000  [dev trc     ,00000]  NTAB: compute_hash_card: 2003.                        48  3.058864
4 ETW000  [dev trc     ,00000]  NTAB: maxcnt 1000.                                    26  3.058890
4 ETW000  [dev trc     ,00000]  NTAB: hfactor 2003.                                   13  3.058903
4 ETW000  [dev trc     ,00000]  NTAB: mem_protocol_size 104                           14  3.058917
4 ETW000  [dev trc     ,00000]  NTAB: hdr_backpack_offset 0                           14  3.058931
4 ETW000  [dev trc     ,00000]  NTAB: hdr_backpack_size 0                             13  3.058944
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: header_size 44.                           14  3.058958
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: item_size 36.                             14  3.058972
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: item_cnt 1000.                            14  3.058986
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: unit_size 4                               14  3.059000
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: unit_cnt 128000.                          48  3.059048
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: data_size 512000.                         15  3.059063
4 ETW000  [dev trc     ,00000]  NTAB: IREC: header_size 44.                           14  3.059077
4 ETW000  [dev trc     ,00000]  NTAB: IREC: item_size 36.                             14  3.059091
4 ETW000  [dev trc     ,00000]  NTAB: IREC: item_cnt 250.                             14  3.059105
4 ETW000  [dev trc     ,00000]  NTAB: IREC: unit_size 8                               13  3.059118
4 ETW000  [dev trc     ,00000]  NTAB: IREC: unit_cnt 12800.                           14  3.059132
4 ETW000  [dev trc     ,00000]  NTAB: IREC: data_size 102400.                         14  3.059146
4 ETW000  [dev trc     ,00000]  NTAB: STAB: header_size 44.                           14  3.059160
4 ETW000  [dev trc     ,00000]  NTAB: STAB: item_size 36.                             14  3.059174
4 ETW000  [dev trc     ,00000]  NTAB: STAB: item_cnt 250.                             14  3.059188
4 ETW000  [dev trc     ,00000]  NTAB: STAB: unit_size 4                               13  3.059201
4 ETW000  [dev trc     ,00000]  NTAB: STAB: unit_cnt 25600.                           14  3.059215
4 ETW000  [dev trc     ,00000]  NTAB: STAB: data_size 102400.                         15  3.059230
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: header_size 148.                          14  3.059244
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: item_size 24.                             14  3.059258
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: item_cnt 1000.                            14  3.059272
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: unit_size 256                             14  3.059286
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: unit_cnt 1000.                            13  3.059299
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: data_size 256000.                         15  3.059314
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: hh_p 2347eb8, hh_len 44                 3816  3.063130
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: aa_p 251c590, aa_len 8012                 39  3.063169
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: ia_p 251e4e8, ia_len 36000                15  3.063184
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: dat_p 252a008, dat_len 512000             14  3.063198
4 ETW000  [dev trc     ,00000]  NTAB: IREC: hh_p 2346b58, hh_len 44                   14  3.063212
4 ETW000  [dev trc     ,00000]  NTAB: IREC: aa_p 2527190, aa_len 8012                 13  3.063225
4 ETW000  [dev trc     ,00000]  NTAB: IREC: ia_p 25a7010, ia_len 9000                 13  3.063238
4 ETW000  [dev trc     ,00000]  NTAB: IREC: dat_p 25a9340, dat_len 102400             14  3.063252
4 ETW000  [dev trc     ,00000]  NTAB: STAB: hh_p 2346b90, hh_len 44                   13  3.063265
4 ETW000  [dev trc     ,00000]  NTAB: STAB: aa_p 25c2348, aa_len 8012                 13  3.063278
4 ETW000  [dev trc     ,00000]  NTAB: STAB: ia_p 25c42a0, ia_len 9000                 14  3.063292
4 ETW000  [dev trc     ,00000]  NTAB: STAB: dat_p 2a90048, dat_len 102400                 3.063292
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: hh_p 2344718, hh_len 148                   1  3.063293
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: aa_p 2aa9050, aa_len 8012                     3.063293
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: ia_p 25c65d0, ia_len 24000                    3.063293
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: dat_p 2aaafa8, dat_len 256000                 3.063293
4 ETW000  [dev trc     ,00000]  NTAB: ntab_mem_protocol 2344718, ntab_mp_p 2344718, ntab_proc_id 0
4 ETW000                                                                               1  3.063294
4 ETW000  [dev trc     ,00000]  NTAB: FTAB: hh_p 2347eb8, ha_list 251c590, hi_list 251e4e8, buffer 252a008
4 ETW000                                                                             196  3.063490
4 ETW000  [dev trc     ,00000]  NTAB: IREC: hh_p 2346b58, ha_list 2527190, hi_list 25a7010, buffer 25a9340
4 ETW000                                                                              50  3.063540
4 ETW000  [dev trc     ,00000]  NTAB: STAB: hh_p 2346b90, ha_list 25c2348, hi_list 25c42a0, buffer 2a90048
4 ETW000                                                                              27  3.063567
4 ETW000  [dev trc     ,00000]  NTAB: TTAB: hh_p 2344780, ha_list 2aa9050, hi_list 25c65d0, buffer 2aaafa8
4 ETW000                                                                              25  3.063592
4 ETW000  [dev trc     ,00000]  NTAB: mem_handler: alloc for 500 elems, task 0, art 0
4 ETW000                                                                               8  3.063600
4 ETW000  [dev trc     ,00000]  NTAB: mem_handler: alloc for 500 elems, task 0, art 1
4 ETW000                                                                             139  3.063739
4 ETW000  [dev trc     ,00000]  NTAB: mem_handler: alloc for 500 elems, task 0, art 2
4 ETW000                                                                              95  3.063834
4 ETW000  [dev trc     ,00000]  NTAB: mem_handler: alloc for 500 elems, task 0, art 3
4 ETW000                                                                              72  3.063906
4 ETW000  [dev trc     ,00000]  Found proc Y3I000003A7G1FK0612DDNTFi1o4ns on db - doesn't exist in cache
4 ETW000                                                                           19102  3.083008
4 ETW000  [dev trc     ,00000]  DbSlBegRead[0]: Y3I000003A7G1FK0612DDNTFi1o4ns        52  3.083060
Regadrs
Vijay

Similar Messages

  • MCOD system copy - need help with plan

    Hi all,
    I got to do export-import for my customer and am facing an issue with their CRM system.
    the source
    MCOD with crm 7.0 abap lets say <sid>=abc and crm 7.0 java <sid>=xyz.
    (netweaver ehp1, hence the split stack)
    DB is Oracle and OS windows.
    target
    i have currently installed crm 7.0 abap on oracle and linux.
    now, here is my plan...  please do let me know your thoughts.
    1.) i will install CRM 7.0 java in target as mcod
    2.) export AS ABAP from source
    3.) export AS JAVA from source
    4.) import AS ABAP into target
    5.) import AS JAVA into target with option mcod.
    well, my question here is during the export will i be able to get 2 exports? i mean will inst export the 2 schemas seperately or there is just option for 1 export and thats the whole database?
    awating your opinions
    Regards,

    hi Shanser,
    if its a dual stack installation you can just run one time SAPINST to get the single export dumps,but if you have done a  add-on Java installation for your CRM system you have to execute two times the SAPINST to get the separate exports for ABAP and JAVA ,but even if you have done  the add-on installation or simple dual stack installation from DB point of view JAVA always goes to SAP<SID>DB and ABAP goes to SAP<SID> DB schema
    hope I have answered your Question
    thanks
    George

  • Separating the MCOD system

    If anyone have any experience in separating MCOD database which is on version DB2 V8.1 fp10, please guide me on how to proceed.
    Best regards,
    AL

    "Separating" an MCOD installation can be (easily) done using a homogeneous system copy using R3load:
    http://service.sap.com/systemcopy
    After you have copied one of the systems you can delete that schema on database level.
    Markus

  • Error  while Installing Java on MCOD system

    Please Find the error attached Below.
    Abap system has been installed and up and running.SID(EB1)
    while installing Java System i am getting the following error SID(EBB).
    WARNING[E] 2009-06-09 01:18:05.920
    CJS-30226  Host: 'sapbl009' or port: 'undefined' or dbSid: 'EB1' is in an inconsistent state or undefined.
    ERROR 2009-06-09 01:18:06.310
    FCO-00011  The step createSecureStore 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_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR .
    ERROR 2009-06-09 01:18:06.310
    FCO-00011  The step createSecureStore 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_SecureStore|ind|ind|ind|ind|8|0|createSecureStore was executed with status ERROR .
    Thanks
    Rishi Abrol

    Hi,
    Have a look at
    Error on: step createSecureStore - NW700 AS Java
    Re: Failed on CreateSecureStore step
    error at "Create Secure Store" phase of Solution Manager 4.0 installation
    narsi

  • Maintenance Optimizer - Systems and Logical Components are not displayed

    Hi Experts,
    When I use the Maintenance Optimizer and select a product version, I do not get any Systems and the relevant Logical Component so that I can select one of those that are displayed. Did I miss any configuration settings or is there anything else that I need to do. Please give me the checklist that I need to look into before selecting a product version in the maintenance optimizer. Please help me out of this.
    Thanks in advance,
    Sagar.K

    Hi,
    Check this link... it has complete step by step configuration of Maintenance Optimizer...
    https://websmp105.sap-ag.de/~sapidb/011000358700000235502007E
    https://websmp208.sap-ag.de/solman-mopz --> SAP Tutor on Maintenance Optimizer
    Award points if found useful

  • DISCOVERY System and its Components

    Hello,
    Do you know what all the SAP componets are combined in the SAP Discovery System??
    Like ERP2005, NW2004s, EP, CAF, BI, MDM...anything else????
    Is this list correct??? Please update me with the complete list...
    Thank you,
    Nikee

    Hi,
    that is going to be a long list:
    <b>SAP NetWeaver 04s</b>
    Portal (SAP NW Portal)
    Application Server (SAP NW AS)
    Process Integration (SAP NW XI)
    Master Data Management (SAP NW MDM)
    Business Intelligence (SAP BW)
    Visual Composer with BI toolkit
    SAP Enterprise Core Component - <b>ECC 6.0</b> (configured with SAP Best Practices tool suite)
    Detailed guidance: how to re-deploy scenarios or key content in your own environment
    Fully documented prototype and development environment (with a working example to evaluate)
    Complete composite application code
    <b>xApps for personal productivity</b>
    Production Order Rescheduling
    Store-Specific Consumer Price
    Request for New Supplier Master Data
    Request for Quotation Approval
    Strategic Investment Buy Simulation
    SAP RFID Solution
    SAP GRC Access Control
    Composite Toolbox
    <b>SAP xApp Analytics</b>
    Travel Expense Exception
    Investment Approval
    <b>Other</b>
    Microsoft Windows 2003
    Microsoft SQL Server 2005
    Hope that I did not forget anything.
    In short: It covers technology and content.
    Best Regards,
       rAimund

  • Isolation of components in PDS while ciffing

    Hi,
    What is the feasible way to isolate certain components in PDS while ciffing from ECC?
    To be more precise, there are 10 componets in BOM in ECC and require only 5 components out of these in PDS while ciffing.
    Thanks,
    Prash

    Hi,
    I assume your requirement as out of 10 components in BOM, you want to plan only 5 components in APO. In that case, you should set the MRP type of your header and only the 5 components as X0. Other 5 components may have different MRP type.
    Also, make sure that you transfer only those 5 APO relevant components material masters. not all.
    Then, while transferring PDS, this will automatically transfer only those 5 APO relevant components to APO.
    If this requirement is not correct, please elaborate your requirement.
    Regards,
    Manimaran M.

  • Error getting system isolation info. Code 8027000C

    Hi, I'm getting this error on a few machines during the Task Sequence. Followed by this other error:Remediation failed with error code 8027000C and also ReleaseRequest failed with error code 0x80004005. Any advice would be appreciated!!
    log file
    ==============================[ OSDSetupHook.exe ]==============================    OSDSetupHook    22/03/2013 4:36:57 PM    976 (0x03D0)
    Executing task sequence    OSDSetupHook    22/03/2013 4:37:01 PM    976 (0x03D0)
    Loading the Task Sequencing Environment from "C:\_SMSTaskSequence\TSEnv.dat".    OSDSetupHook    22/03/2013 4:37:01 PM    976 (0x03D0)
    Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created    OSDSetupHook    22/03/2013 4:37:01 PM    976 (0x03D0)
    Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created    OSDSetupHook    22/03/2013 4:37:01 PM    976 (0x03D0)
    Debug shell is enabled    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Successfully enabled debug command shell support.    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Configuring local administrator account    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Installing SMS client    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Client already installed.    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Moving logs to SMS client directory    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Successfully moved logs to SMS client log directory: C:\Windows\CCM\Logs\SMSTSLog    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Executing task sequence manager bootstrap    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    Executing command line: "C:\Windows\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:5    OSDSetupHook    22/03/2013 4:37:06 PM    976 (0x03D0)
    ==============================[ TSMBootStrap.exe ]==============================    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Command line: "C:\Windows\CCM\TSMBootstrap.exe" /env:Gina /configpath:C:\_SMSTaskSequence /bootcount:5    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Logging successfully initialized.    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Resuming Task Sequence in Full OS    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    We are going in GINA and potentially need to set the authenticator    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    setting the authenticator    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Executing command line: "C:\Windows\CCM\TsProgressUI.exe" /Register:WinPE    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    ==========[ TsProgressUI started in process 1964 ]==========    TsProgressUI    22/03/2013 4:37:06 PM    1968 (0x07B0)
    Command line: "C:\Windows\CCM\TsProgressUI.exe" /Register:WinPE    TsProgressUI    22/03/2013 4:37:06 PM    1968 (0x07B0)
    Registering COM classes    TsProgressUI    22/03/2013 4:37:06 PM    1968 (0x07B0)
    sbModulePath = C:\Windows\CCM\TsProgressUI.exe    TsProgressUI    22/03/2013 4:37:06 PM    1968 (0x07B0)
    Unregistering class objects    TsProgressUI    22/03/2013 4:37:06 PM    1968 (0x07B0)
    Shutdown complete.    TsProgressUI    22/03/2013 4:37:06 PM    1968 (0x07B0)
    Process completed with exit code 0    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Successfully registered TS Progress UI.    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Found network adapter "Intel(R) 82578DM Gigabit Network Connection" with IP Address 10.67.67.146.    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Starting Task Sequence Manager.    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    executing TS Manager not in full media    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    executing TS Manager in c:\windows\ccm    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Executing command line: "TsManager.exe"    TSMBootstrap    22/03/2013 4:37:06 PM    1956 (0x07A4)
    Successfully intialized Logging for TS Manager.    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Commandline: "TsManager.exe"    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    /service parameter found at index: -1    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    /standalone parameter found at index: -1    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    /noclient parameter found at index: -1    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Successfully registered Task Sequencing COM Interface.    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Executing as a standalone exe    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Initializing TS Environment    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Opening Task Sequencing Environment    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,254)    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,254)    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,254)    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    pwszPath && *pwszPath, HRESULT=80070057 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,254)    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    NOT executing in WinPE    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Compiling Config policy    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Compiling config policies...    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Compiling SysHealthConfig policy...    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Retrieving value from TSEnv for '_SMSTSSysHealthClientConfig'    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    ::DecompressBuffer(65536)    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Decompression (zlib) succeeded: original size 688, uncompressed size 4652.    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Instance path = 'CCM_SystemHealthClientConfig.SiteSettingsKey="1"'    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:06 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Compiling SoftUpdConfig policy...    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Retrieving value from TSEnv for '_SMSTSSWUpdateClientConfig'    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    ::DecompressBuffer(65536)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Decompression (zlib) succeeded: original size 2019, uncompressed size 35054.    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Instance path = 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"'    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Instance path = 'CCM_SoftwareUpdatesClientConfig.SiteSettingsKey="1"'    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    (__hrMethodRetVal == ((HRESULT)0L)) || (bFailIfMissing == false), HRESULT=80070002 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,582)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy compilation    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Compiling SoftDistClientConfig policy...    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Retrieving value from TSEnv for '_SMSTSSoftDistClientConfig'    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    ::DecompressBuffer(65536)    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Decompression (zlib) succeeded: original size 1335, uncompressed size 13744.    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Instance path = 'CCM_SoftwareDistributionClientConfig.SiteSettingsKey="1"'    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Start to compile TS policy    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Converting input value from 19 to 3    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace    TSManager    22/03/2013 4:37:07 PM    1980 (0x07BC)
    End TS policy

    I believe that error has to do with NAP (Network Access Protection). If you are not using NAP in your environment you can ignore that error. My logs have those entries, too.

  • Help needed to DELETE a System created with Logical Components assigned.

    Hi,
    I created a system in SMSY in my Solution Manager system. I unknowingly assigned the system to Logical Components. Now on finding that it was a worng way of configuration I need to DELETE the system and recreate it using the option "Create new system with assistant."
    Please help me in resolving the issue. I am not getting an option from the were used list to delete the assignment of the system.
    Expecting a reply at the earliest.
    Regards,
    Vineeth

    Dear friend
    You can remove the system from the logical component by clicking on display/change and removing the SID from the system assignments,
    just select the blank field from F4 help.
    Once you have removed the system from the logical component, you will be able to delete the system.
    shailesh Tiwari

  • ERP Hub Portal SUM EhP7 Components List in Phase Target System Config.

    Dear Colleagues,
    during a EHP/ Update of a J2ee HUB Portal in SUM Phase Configuration/Target Systems Configuration/Confirm Components
    the Component List pop's up with a list of Components slected for removal.
    My Question is, is this valid, I don´t found usefull informations regarding some of the Components, or is there a misconfiguration on Solman for the components of the ERP HUP Portal.
    OSS-NOTE: 1395514 - Löschen von Softwarekomponenten in NW CE 7.20 und höher
    br
    Julius

    Hi,
    I have checked the link before to open my question, but I can't or don't follow the instructions:
    1. Ensure Namespace /RPM is modifiable in SE06
    2. Call transaction SE37
    3.Enter /RPM/RELATION_MODIFY
    4.Select Function module-> Other functions-> Rename
    5.Rename it to /RPM/RELATION_MODIFY_OLD
    6.Release the request if one was created in the process
    7.Restart the phase
    The Function Module and the Function Group  does not exist in our system. And when I can to create the Function Gorup, I have the follow error in the SE80: "Namespace /RMP/ does not exist", and when I try to create the namespace /RPM/ I don't have the "repair license".
    I'm using the EHPI Upgrade tools for the EHP4.
    Regards, Alberto

  • MCOD Installation

    Hello,
    In MCOD we can install multileple SAP components in one DB. It means multiple comoments have only one single DB Instance or each component has its unique DB Instance?
    Thanks for your help
    Kris

    Hi Kris,
    >
    > In MCOD we can install multileple SAP components in one DB. It means multiple comoments have only one single DB Instance
    or each component has its unique DB Instance?
    In MCOD system, DB instance will be single but every system will have their own database schema. For more information check below link:
    https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/80bf0979-8e07-2a10-e486-d72e3aa81f80?overridelayout=true
    SAP note 443925
    Thanks
    Sunny

  • Create a Support Message in Production system showing up in Solution Manage

    Has anyone setup the link between creating a support message (under help) in a production system (like ECC) and SAP's Solution Manager.
    I understand that it uses BADI SBCOS001 with the interface method PREPARE_FEEDBACK_BO, but when I try to run it, it tells me that Customizing for feedback functionality missing. What functionality is missing? And how to I correct this? And how do I ensure it shows in SAP Solution Manager under a solution or project?
    Thanks
    Paul

    Hi Paul
    The only way is to use the IMG. I have just completed this via the IMG info. BUT, it is not that simple.
    Make sure your RFC's are trusted and that you have SAP ALL during config.
    I hope this will help:
    Setup Service Desk
    Steps to follow while configuring support desk.
    1) Implement the note 903587 .
    2) Create all the relevant RFC objects in the satellite system and add the appropriate logical components using transaction SMSY.
    3) Check all the objects in the table BCOS_CUST using transaction SM30.
    Appl : OSS_MSG
    + :W
    DEST :BACK RFC NAME (for solution manager system keep this field as 'NONE')
    + :CUST 620
    + :1.0.
    *4) Check whether the BC sets are activated or not using the transaction SCPR20.If the BC sets are not activated then implement the note 898614.The steps to activate the BC sets are described below
    4.1) Activate SOLMAN40_SDESK_BASICFUNC_000 BC Set.
    4.2) Activate this in expert mode with option u201COverwrite everythingu201D.
    4.3) Activation of the following components has to be done by replicating the previous steps
    3.1) SOLMAN40_SDESK_TPI_ACT_AST_001
    3.2) SOLMAN40_SDESK_ACTIONLOG_001
    3.3) SOLMAN40_SDESK_ACT_ADVCLOSE_001
    3.4) SOLMAN40_SDESK_TEXTTYPES_001
    *Depends upon the number of inactive BC set objects that we have after the upgrade.
    4.4) if the actions mentioned in 4.3 are not listed while executing the transaction SCPR20, then implement the note 898614.In the source client 000 of the solution manager system create a transport request using transaction SE09, unpack the file 'PIECELIST_SERVICE_DESK_INIT.ZIP' from the attachment of the note. Copy the contents of the file 'PIECELIST_SERVICE_DESK_INITIAL.TXT' to the transport request. And activate the actions. Use transaction SCC1 to import the transport request to the solution manager client. If any short dump occurs during the activation, implement the note 939116.
    5) Check whether the number range is set correctly. If not set the number ranges of basic notification (ABA) and the support desk message (Service transaction SLFN).To be able to use the same number ranges for both message types, the internal number range for basic notification (ABA) must correspond to the external number range for the support desk message.
    Number ranges for ABA notifications
    5.1) create an internal and external number range using transaction DNO_NOTIF.
    5.2) assign number range intervals to groups internal and external.
    5.3) SLF1 is the internal number range group
    5.4) SLF2 and SLF3 is the external number range interval
    5.5) Use transaction DNO_CUST01 to assign message categories to the number range.
    5.51) Go to transaction DNO_CUST01
    5.52) From the GOTO menu select the menu item DETAILS
    5.53) Now you can assign the number range of basis notification (ABA) into the notification type.
    The number range for ABA notification is 12 characters in length and to make it compatible with the CRM service transaction insert 2 ZEROES at the beginning.
    Number ranges for Support Desk notification
    5.54) Use transaction CRMC_NR_RA_SERVICE, and define the internal and external number ranges. Intervals must correspond to the intervals of the basic notifications (ABA notification).
    5.6) Then assign both the external and internal numbering
    5.61) Go to SPRO and then to SAP Solution Manager
    5.62) Then select General Settings and then select Transaction types
    5.63) Select the transaction type SLFN and then select the menu item DETAILS from the GOTO menu.
    5.64) In the Transaction Numbering block, assign the internal and external number range. The Number Range object should be CRM_SERVIC.
    5.7) To view the priorities use transaction DNO_CUST01 and select the notification type as SLF1 and then select priorities from the left pane of the screen. The priorities of the first four cannot be deleted, but new priorities can be added.
    6) Check the Action profiles for ABA Notifications (Action profiles are used for synchronization of ABA notification with the CRM Service transaction).
    6.1) To check the action profiles use the transaction SPPFCADM and select the application type DNO_NOTIF then select u2018DEFINE ACTION PROFILE AND ACTIONSu2019.
    6.2) Select the item u2018SLFN0001_STANDARD_DNOu2019 and then from the menu GOTO, select the menu item DETAILS.
    7) The Action profile u2018SLFN0001_STANDARD_DNOu2019 has to be assigned to the message category SLF1 (ABA notifications) using the transaction DNO_CUST01.
    8) The action profile for the support desk message can be set to u2018SLFN0001_ADVANCEDu2019.
    8.1) From SPRO select SAP Solution Manager then Scenario Specific Settings.
    8.2) Select the item Service Desk and then to general settings.
    8.3) Execute the category u2018Define Transaction Typesu2019.
    8.4) Select the transaction type as SLFN
    8.5) From the GOTO menu select the menu item u2018DETAILSu2019 and assign the action profile as SLFN0001_ADVANCED .
    9) Activate the partner/ Organization
    9.1) Go to CRM->MASTER DATA->BUSINESS PARTNER->INTEGRATION BUSINESS PARTNER ORGANIZATION MANAGEMENT->SET UP INTEGRATION WITH ORGANIZATIONAL MANAGEMENT.
    9.2)Find the entries starting with HRALX
    HRALX-HRAC WITH VALUE 'X'.
    HRALX-OBPON WITH VALUE 'ON'.
    HRALX-PBPON u2018ONu2019.
    HRALX-MSGRE u2013 u20180u2019.
    9.3) If entries are not found create it.
    10) Generate Business partner screens
    10.1) Go to transaction BUSP.
    10.2) Execute the report with the following parameters
    CLIENT - Client in which business partners should be created (solution manager client)
    APPLICATION OBJECT-
    SCREEN - *
    Generate all/ selected screens - All screens.
    delete sub screen containers -
    11) implement SAP note 450640.
    11.1) Go to transaction SA38 and select the report CRM_MKTBP_ZCACL_UPDATE_30.
    11.2) Execute it with test mode box unchecked.
    If a new relationship is to be created then steps 12 and 13 has to be followed
    12) To create a relationship category
    12.1) Go to transaction BUBA
    12.2) Select the entry CRMH00: Undefined relationship
    12.3) click on copy
    12.4) Rename CRMH00 to ZCRMH00.
    12.5) CREATE A RELATIONSHIP CATEGORY.
    IN GENERAL DATA FILL LIKE ' FROM BP1 : HAS THE ACTIVITY GROUP '.
    ' FROM BP2 : IS A PART OF ATTUNE
    13) Add the relationship category to the support team partner function
    13.1)Use SPRO
    IMG GUIDE->SAP SOLUTION MANAGER->SCENARIO SPECIFIC SETTINGS->
    -> SERVICE DESK->PARTNER DETERMINATION PROCEDURE->DEFINE PARTNER FUNCTION.
    13.2) FIND THE PARTNER FUNCTION SLFN0003 (SUPPORT TEAM).
    13.3) In the field relation ship category, Select the newly created relationship category and save.
    14) Steps 12 and 13 should be repeated for various business partner types like sold-to-party, message processors if new relationship is to be created for the respective business partner types.
    15) Create a new access sequence for the support team determination
    15.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Configuration ->
    -> Scenario Specific Settings ->Service Desk -> Partner Determination Procedure ->
    ->Define Access Sequence
    15.2) Click on New Entries
    15.3) Define a new access sequence with sequence name as u2018Z001u2019 and description u2018NEW BP RELATIONSHIP ACTIVITY GROUPu2019
    15.4) Create an new Individual Access with the following value:
    u2022 Batch Seq: 10
    u2022 Dialog Seq : 10
    u2022 Source : Business Partner Relationship.
    u2022 Detail on the source:
    u2022 Partner Function : Reported By (CRM)
    u2022 Mapping/restrictions
    u2022 Flag Mapping/definition for partner being Searched
    u2022 Partner Function in Source: Support Team (CRM).
    Save it.
    This Access Sequence will give us the Partner which has the relationship assigned
    to the Support Team in the Reported By partner data.
    16) Adapt the partner determination schema/Function
    16.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide ->
    SAP Solution Manager -> Scenario Specific Settings ->Service Desk ->
    -> Partner Determination Procedure -> Define Partner Determination Procedure.
    16.2) The two options to adapt partner determination schema are
    16.21) Adapt the standard Procedure (SLFN0001) or to create a new one by copying the standard one.
    16.22) select the line starting with SLFN0001 or the newly created procedure.
    16.23) Double Click on Partner Function in Procedure.
    16.24) Select the Partner Function "Support Team", and click Details.
    16.25) in the detail view only change the Partner Determination/access Sequence to
    the one we've just created. Save your entry.
    17) Create a root organizational model.
    17.1) Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration-> Scenario Specific Settings ->Service Desk -> Organizational Model ->Create a Root Unit for Your Organizational Structure.
    17.2) creating an organizational unit by entering the data in the BASIC DATA tab.
    17.3) enter the organizational unit, the description and save it.
    18) Create the support team organization
    18.1) go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Scenario Specific Settings ->Service Desk -> Create Organizational Objects in the Organizational Structure. Or use transaction (PPOMA_CRM).
    19) Create the business Partners.
    19. 1) Key users- End user (Business Partner General) ,Address should be specified.
    19.2) go to the transaction BP.
    19.3) create a new Person, Select the role: Business Partner (Gen).
    For Identification of the key user
    19.31) click on the identification tab
    19.32) enter a line in the identification number formatted as follows
    IDTYPE : CRM001.
    Identification number : <SID><INSTALL NUMBERS><CLIENT><USERNAME>
    eg: USER NAME : USER1.
    CLIENT : 100.
    SID : ER1.
    INSTALL NUMBER : 123456789.
    IDENTIFICATION NUMBER : ER1 123456789 100 USER1.
    20) Message Processors- Support Team members .
    20.1) they should be created first as the users in the corresponding client of the solution manager.
    20.2) As business partners they will have the role 'EMPLOYEE'.
    20.3) Go to transaction BP .
    20.4) Create New Person with the role employee.
    20.5) In the Identification tab you should enter the user name in the employee data/User Name.
    eg: username: proc1
    enter proc1 in the field User name.
    21) Organizational Business Partner- Organizational BPS have the same country in there main address tab. They should be created through the organizational model. Business partner corresponding to the root organization have the role 'SOLD TO PARTY'.
    22) Assign the business partners (Message Processors) to the previously created support team.
    22.1) Go to transaction PPOMA_CRM.
    22.2) Select the support team 1.
    22.3) Click on create
    22.4) select position
    22.5) call it 'MPROC_T1/Message Processors for team 1
    22.6) Replicate it for the other support teams.
    22.7) Select the position MPROC_T1/Message Processors for team1 and click assign,
    choose owner/Business Partner find and select the business partner
    22.8) Validate and Save it.
    22.9) If the assignment of business partner is not possible then implement the note 1008656
    Or 997009
    23) Create the iBase component
    23.1) IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings -> Standard Configuration of Basic Settings -> Solution Manager -> iBase -> Initially Create and Assign the Component Systems as iBase Components.
    23.2) or use the transaction IB51 to create the installed base.
    23.3) it is also possible to create the SOLUTION_MANAGER, select the solution and go to menu Edit -> Initial Data Transfer for iBase.
    24)Assign Business Partners to iBase Components
    IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Basic Settings
    -> SAP Solution Manager System ->ServiceDesk-> iBase -> Assign Business Partners to iBase Components.
    *--optional--
    If you want to be able to assign the System Administrator: Go to the IMG: SAP Solution Manager Implementation Guide -> Customer Relationship Management -> Basic Function -> Partner Processing -> Define Partner Determination Procedure.
    Select the entry "00000032 Installed Base/IBase" and double click on Partner Functions in Procedure.
    Then copy the Entry "Contact Person (CRM)" to a new entry with the partner Function "System Administrator (CRM)" , save it.
    Go back to transaction IB52, select a component, and Goto -> Partner, you should be able
    now to assign the partner Function "System Administrator".
    25) Assign the SAP Standard Role to the user. Message Creator should have the role : SAP_SUPPDESK_PROCESS.
    26)Define the transaction variant for the message processors
    Go to the following IMG Path: SAP Solution Manager Implementation Guide -> SAP Solution Manager -> Configuration -> Scenario Specific Settings ->Service Desk -> General Settings -> Specify User Selection Variant.
    Here we will create variants for the central message processing transaction CRM_DNO_MONITOR.so that the user will have direct access to there dedicated message.
    27) Go to transaction PFCG
    27.1) Enter the role name as Z_MSG_PROCESSORS and choose single role.
    27.2) Give a description Message Processor role and save it.
    27.3) Go to the menu tab and choose add report
    27.4) select the report type : ABAP Report
    27.5) And in the report enter the report name as 'CRM_DNO_SERVICE_MONITOR'.
    27.6) Enter the previously created variant.
    27.7) flag the skip initial screen box.
    27.8) flag the SAPGUI for windows.
    27.9) Create a new transaction with tcode starting with Y or Z.
    27.10)Display this transaction and check the values at the bottom of the screen
    in the subscreen Default Values, you should have the following parameters:
    u2022 D_SREPOVARI-REPORT = CRM_DNO_SERVICE_MONITOR
    u2022 D_SREPOVARI-VARIANT = MY_TEAM_MSG
    u2022 D_SREPOVARI-NOSELSCRN = X
    And also all the user should have the correct role.

  • Logical Components and Solution Landscapes - 2 PRD ECC Servers

    When I assign my PRD ECC5 server to Logical Components > SAP ECC > SAP ECC Server > SAP ECC, I select the Product Version as SAP ECC5.
    From the drop down list on Production System, I can see both my ECC 5 PRD's clients listed. I select one client, all OK. Problem is I have 2 Production ECC5's, both to be used in seperate solutions. So I can only select ONE of these,
    How can I use 2 ECC5 Production systems in Logical Components, or does it need to be configured differently?
    Thanks,
    Derek

    hi Derek,
    you can create more than one logical component under ECC. Just name it something like ZECC2 and the define the systems for this logical component. You can then use the logical component in your project system landscapes.
    To add a new one just right click on the text SAP ECC Server and select Create Logical Component.
    regards,
    Jason

  • SAP Source System showing up as BI Source System in RSA1

    I have 2 BW systems and 2 CRM Systems.  In one BW system, when I create a SAP Source system in RSA1, It gets listed as a SAP Sources system along with ECC and all the rest.
    The Logicial Systems and RFC Connections all appear to be the same between each pair.
    In the other system, using identical procedure, it the source system gets listed as a BI Source System.  The 2 CRM systems have identical components and version levels as do the 2 BW systems.
    Any idea why and if this would make any difference and how to correct.

    Hi,
    To fix this, you need to do a restore (& not a delete) of the source system in BW, having deleted the RSBASIDOC entry in the source OLTP system.
    This will force the BW system to interrogate the RSBASIDOC table entry in the source system again and it should then realise that it is an R/3 system (not a BW system) and move the entry to the SAP folder.
    Rgds,
    Colum

  • Deleting components in scheduling agreement

    Hello all,
    I have a scheduling agreement. It has material X which has components Y1,Y2,Y3.
    I want to delete component Y1 as it not required. So I select the schedule delivery in ME38, ItemComponentNew BOM explosion to see the BOM components. I find Y1,Y2,Y3. When I right click at Y1 and press delete, the component gets deleted.
    I save. But when I come back in the scheduling agreement, the component will remain there.
    Any idea?
    reg
    Sunny

    When you select new Bom explosion, system  explodes  the Components  again w.r.t the BOM maintained in CS01. Instead of new BOM explosion , you should select  "Components"  icon.

Maybe you are looking for