SLD Registration in SRM

Hi All,
While installing our SRM server we chose "no SLD". We planned to register the SLD in SOLMAN later on. Currently SRM SLD is
up and running, but there are no data supplier in AS ABAP. We tried to run RZ70 by pointing to SRM Host And Gateways. It fails.
While RZ70 runs fine if we point to SOLMAN.
We want to understand how to register SLD of SRM in SOLMAN or if not needed can we have a local SLD in SRM configured now?
As we will be using EP 7.0; SLD is an integral part to make the things happen.
Some technical help or suggestions will be ueful for us.
Thanks & Regards,
Ishan

Dear Ishan,
First of all you need to check your landscape design blueprint. If you are going to have a central SLD which is not going to be on your SRM system itself then you can configure your SRM data suppliers to the central system's SLD itself.
However, if you want to configure the data suppliers to your SRM system itself then first check what is the result on the page http://<hostname>:<port>/sld
As SLD should be installed by default so you would just need to do the SLD configuration as per the post-installation guide available at System Landscape Directory (SLD)
This should help you out.
Regards,
Abhishek

Similar Messages

  • SLD registration for TREX not working...

    SDN Members,
    I am unable to register TREX in SLD. I have put in an OSS message; however, I have yet to receive a response back from SAP... So any help would be much appreciated.
    Thanks,
    -Patrick
    Steps for the Reconstruction 
    1. Generate SLD Configuration file:
    sldreg -configure /usr/sap/TXD/TRX85/slddest.cfg
    2. Copy the SLD Config. File to the Global SLD Directory and run
    command (to transfer data to SLD):
    saposcol -b | sldreg -connectfile slddest.cfg -stdin -oldtransferdtd
    Receive the following:
    (hostnames, ip's, and ports altered to protect the innocent)
    prtdiag can only be run in the global zone
    Thu Dec 27 10:33:04 2007 SLD Registration Program [2.0]  (May  8 2006) [None Unicode]
    Thu Dec 27 10:33:04 2007 No XML data input file set. Will read input data from standard input.
    Thu Dec 27 10:33:04 2007 Supplier Name: ComputerSystem / Supplier Version: 1.0 / Supplier Vendor:  / CIM Model Version: 1.3.21
    Thu Dec 27 10:33:04 2007 Group:
    Thu Dec 27 10:33:04 2007 Group name system1
    Thu Dec 27 10:33:04 2007 validateAttributes OK
    Thu Dec 27 10:33:04 2007 Property Status
    Thu Dec 27 10:33:04 2007 Value OK
    Thu Dec 27 10:33:04 2007 Property NameFormat
    Thu Dec 27 10:33:04 2007 Value IP
    Thu Dec 27 10:33:04 2007 Property Caption
    Thu Dec 27 10:33:04 2007 Value hostname01
    Thu Dec 27 10:33:04 2007 Property Name
    Thu Dec 27 10:33:04 2007 Value usahstxutxd01
    Thu Dec 27 10:33:04 2007 Property IPAddress
    Thu Dec 27 10:33:04 2007 Value X.X.X.X
    Thu Dec 27 10:33:04 2007 Property OpSysReleaseName
    Thu Dec 27 10:33:04 2007 Value SunOS
    Thu Dec 27 10:33:04 2007 Property OpSysCategory
    Thu Dec 27 10:33:04 2007 Value Solaris
    Thu Dec 27 10:33:04 2007 Property VendorRelease
    Thu Dec 27 10:33:04 2007 Value SunOS 5.10
    Thu Dec 27 10:33:04 2007 Property CPUType
    Thu Dec 27 10:33:04 2007 Value sun4v
    Thu Dec 27 10:33:04 2007 Property MachineCategory
    Thu Dec 27 10:33:04 2007 Value SPARC
    Thu Dec 27 10:33:04 2007 Property OpSysBits
    Thu Dec 27 10:33:04 2007 Value 64
    Thu Dec 27 10:33:04 2007 Property NumberOfCPUs
    Thu Dec 27 10:33:04 2007 Value 32
    Thu Dec 27 10:33:04 2007 Property CPURate
    Thu Dec 27 10:33:04 2007 Value 1200
    Thu Dec 27 10:33:04 2007 Property PhysicalRAMInMB
    Thu Dec 27 10:33:04 2007 Value 65528
    Thu Dec 27 10:33:04 2007 Property VirtualRAMInMB
    Thu Dec 27 10:33:04 2007 Value 87224
    Thu Dec 27 10:33:04 2007 Using connect file 'slddest.cfg'.
    Thu Dec 27 10:33:04 2007 No key file 'slddest.cfg.key' used.
    Thu Dec 27 10:33:04 2007 HTTP trace: false
    Thu Dec 27 10:33:04 2007 Data trace: false
    Thu Dec 27 10:33:04 2007 Using connect file 'slddest.cfg'.
    Thu Dec 27 10:33:04 2007 No key file 'slddest.cfg.key' used.
    Thu Dec 27 10:33:04 2007 *** Start SLD Registration ***
    Thu Dec 27 10:33:04 2007 Used URL: http://hostname01:50000/sld/ds
    Thu Dec 27 10:33:04 2007 HTTP open status: true - NI RC=1
    Thu Dec 27 10:33:04 2007 HTTP send successful.
    Thu Dec 27 10:33:04 2007 Return code: 401 --- Return message: (Unauthorized)
    Thu Dec 27 10:33:04 2007 HTTP response: Failure. HTTP status code: 401
    Thu Dec 27 10:33:04 2007 *** End SLD Registration ***
    Thu Dec 27 10:33:04 2007 Data send status: false
    Consequently SLD is not updated with TREX information. Using IE I can go to
    the url http://hostname01:50000/sld/ds , get popup asking for
    credentials (we log in using SLDDSUSER account - w/ Basis Admin level
    auth.), and we receive: Page Cannot be displayed (HTTP 400 - Bad Request
    Internet Explorer ).
    If we go to http://hostname01:50000/sld and login with the same
    account (SLDDSUSER) we see the full SLD Toolset.
    Edited by: Patrick Riggins on Dec 27, 2007 6:06 PM

    UPDATE:
    We were able to work through and
    resolve the error we initially posted in this Thread. Now we run sldreg
    and all looks good; however, we are seeing nothing in SLD (on our XI
    System) even after stop/restart of SLD Server:
    Steps for the Reconstruction 
    1. Generate SLD Configuration Files:
    sldreg -usekeyfile -configure /usr/sap/TXD/TRX00/slddest.cfg
    2. Copied files to Global SLD
    /sapmnt/TXD/global
    3. Run command to transfer data to SLD:
    saposcol -b | sldreg -user <user acct> -pass <password> -host
    <hostname> -port <port #> -datatrace -httptrace -
    logfile /usr/sap/TXD/TRX00/sld_reg.log -stdin
    Looks successful:
    Thu Dec 27 20:31:06 2007 HTTP body length: 0 --- HTTP body: empty
    Thu Dec 27 20:31:06 2007 Return code: 200 --- Return message: (OK)
    Thu Dec 27 20:31:06 2007 HTTP response: Success. HTTP status code: 200
    Thu Dec 27 20:31:06 2007 *** End SLD Registration ***
    Thu Dec 27 20:31:06 2007 Data send status: true
    However in SLD , under content maintenance selecting "All With
    Instances" in the dropdown list and "Class" , no TREX Services showing.
    And no technical system showing for TXD (TREX System)

  • Initial Setup Problem - Starting the SLD Registration process

    Hi,
    we are installing our PI development system. During initial configuration with "NWA --> Configuration Management --> Scenarios --> Configuration Wizard --> Netweaver initial setup" the wizard stands still at Step 68 (of 561) "Starting the SLD Registration process".
    We have restarted the system but after starting again the wizard it stands still again.
    Same problem on our PI quality assurance system.
    PI 7.11 on Windows 2008 R2 with MSSQL 2008 R2.
    Steps of installation:
    1) Installation of PI 7.11
    2) Postworks ABAP (License, TMS, Profiles, rz04, ...)
    3) Kernelupdate to 106
    4) Updates SPS7 ABAP
    5) Updates SPS7 JAVA
    6) Run NWA Initial Setup with J2EE_ADMIN
    Could someone help?
    Thanks
    Regards
    Thomas Mühl

    Then possibly the password was set wrong somewhere (since the "-" character is not blocked). Its advisable to check all service users passwords, to prevent other issues like this one to occur. Please check the OSS note "999962 - PI 7.10: Change passwords of PI service users" for more information on this.

  • Sld registration

    Hi all,
    after running note 764176 I can now only see my DEV and QA objects in my master SLD.
    My PROD components (adapter engine, integration server etc.) are not self registrering in the Master SLD.
    How could I make this happen? (I would like my master to have ALL the components, and then trasnport the PROD components to the my slave SLD)
    Thanks!

    UPDATE:
    We were able to work through and
    resolve the error we initially posted in this Thread. Now we run sldreg
    and all looks good; however, we are seeing nothing in SLD (on our XI
    System) even after stop/restart of SLD Server:
    Steps for the Reconstruction 
    1. Generate SLD Configuration Files:
    sldreg -usekeyfile -configure /usr/sap/TXD/TRX00/slddest.cfg
    2. Copied files to Global SLD
    /sapmnt/TXD/global
    3. Run command to transfer data to SLD:
    saposcol -b | sldreg -user <user acct> -pass <password> -host
    <hostname> -port <port #> -datatrace -httptrace -
    logfile /usr/sap/TXD/TRX00/sld_reg.log -stdin
    Looks successful:
    Thu Dec 27 20:31:06 2007 HTTP body length: 0 --- HTTP body: empty
    Thu Dec 27 20:31:06 2007 Return code: 200 --- Return message: (OK)
    Thu Dec 27 20:31:06 2007 HTTP response: Success. HTTP status code: 200
    Thu Dec 27 20:31:06 2007 *** End SLD Registration ***
    Thu Dec 27 20:31:06 2007 Data send status: true
    However in SLD , under content maintenance selecting "All With
    Instances" in the dropdown list and "Class" , no TREX Services showing.
    And no technical system showing for TXD (TREX System)

  • RWB / SLD Registration / MsgUrl is null?!?

    Hi there,
    i have a Problem. when i go to the SLD Registration in the RWB to Register
    Runtime Workbench
    Repository
    I Become the Message:
    Runtime Workbench reports registration status: completely registered
    XIDomain.IntegrationServer.MsgUrl: MsgUrl of Integration Server is.00.server1 is null.
    XIDomain.IntegrationServer.SecureMsgUrl: SecureMsgUrl of Integration Server is.00.server1 is null.
    XIDomain.IntegrationServer.BusinessSystem: BusinessSystem is null. No BusinessSystem associated to the Integration Server is.00.server1.
    also on the Adapter Engine
    Messaging URL of Integration Server: URL currently used by Adapter Engine is null!
    Messaging URL of Integration Server: URL stored in SLD is null!
    Messaging URL of Integration Server: URL currently used by Adapter Engine and URL stored in SLD are the same
    XIDomain.IntegrationServer.MsgUrl: MsgUrl of Integration Server is.00.server1 is null.
    XIDomain.IntegrationServer.BusinessSystem: BusinessSystem is null. No BusinessSystem associated to the Integration Server is.00.server1.
    The directory is another message:
    Directory: Unable to get directory instance and read data from SLD; details: Unable to create an object that represents the SLD entry for the XI component
    Can someone help here?
    Regards
    Edited by: Bjoern Bayerschmidt on Jun 2, 2010 8:55 AM
    Edited by: Bjoern Bayerschmidt on Jun 2, 2010 8:56 AM

    and you looked at both notes?
    all of this was provided in the two notes in my first post.....  if this did not work.....
    Solution
    Checking completeness and consistency of SLD
    First check whether the PI structures in SLD are incorrect. Start the SLD user interface (http:<host name>:<port>/sld), navigate to Technical Systems --> Process Integration
    For a correct PI registration, the tabular display of the PI structure must contain the following entries:
    - One entry for the domain of the Integration Server
    - One entry for each PI component: Integration Server, Adapter Engine, Directory, Repository and Runtime Workbench (RWB). Each must be assigned to the domain above, i.e. the domain name must appear in column "Domain".
    If some of the PI components Adapter Engine, Directory, Repository or Runtime Workbench are missing in the table, you need to explicitly register those as described below. If they appear in the table, but are not assigned to a domain, you have to delete them and register them explicitly.
    Deleting PI components
    Navigate to
    Technical Systems --> Process Integration
    Select the components you want to delete, push "remove" button.
    Beware: Do not accidentally delete the XIIntegrationServer.
    Triggering SLD Registration of PI components
    You can trigger registration of a PI component by restarting the associated application. Navigate to the start/stop UI in the Netweaver Administrator:
    http:<host name>:<port> --> SAP Netweaver Administrator --> Configuration Management --> infrastructure --> application modules
    Here you restart the applications for the missing PI components:
    com.sap.xi.directory (Integration Builder/Configuration)
    com.sap.aii.af.app (Adapter Engine)
    com.sap.xi.rwb (Runtime Workbench)
    com.sap.xi.repository (Integration Builder/Design)
    this is why i gave both notes as the information you provided was far from complete...
    what version are you using?  is it a new install?  or a restore?  or did it just go like this???

  • PIRWBUSER / not enough Permissions / SLD Registration / Adapter Engine / PI

    Hi Community,
    i have a Problem. I go to the SLD Registration in the RWB
    When i click on Adapter Engine and Register i become the Message
    Adapter Engine P11 (HOST): Unable to get Adapter Engine instance and read the data from SLD; details: Cannot connect to component Adapter Engine P11 (HOST); user PIRWBUSER does not have sufficient authorization to call servlet at URL http://HOST:50000/AdapterFramework/regtest.
    My PIRWBUSER has the following Roles:
    SAP_SLD_CONFIGURATOR
    SAP_XI_RWB_SERV_USER
    SAP_XI_RWB_SERV_USER_MAIN
    Can someone help here?
    Regards
    Bjoern

    Hello!
    Apply the note below according to your system version:
    999962 - PI 7.10: Change passwords of PI service users
    936093 - XI 7.0: Changing the passwords of XI service users
    721548 - XI 3.0: Changing the passwords of the XI service users
    If not worked, try working with the SAP_ALL and check if works.
    Regards,
    Caio Cagnani

  • Delete SLD Registration in RWB

    Hi,
          I would like to delete the component Name (Adapter Engine) listed in Non-central components, as the host name/system doesn't exists anymore. The reason I would like to delete is, whenever we make the changes to any IB objects, save and activate and error messge pops up with this host name.
    Thank you

    Go to SLD -> Technical Systems -> Technical System Type (process integration) ->
    If you find the relavent adapter engine.. remove it and try..
    http://wiki.scn.sap.com/wiki/display/XI/How+to+Manually+Correct+the+Registration+of+XI+Components+Within+the+SLD

  • J2EE SLD registration

    I want to register a J2EE instance into a SLD that runs on a separate XI instance. The registration of the XI J2EE instance itself into the SLD works fine but when i register the other J2EE instance with exactly the same parameters in the SLD the following error is reported: 'Invalid HTTP connect data'.
    Any help is appreciated,
    Jack

    Hi Pascal,
    I did that, now when I run dtr.bat I receive this message:
    dtr is DTR's client tool for the command line.
    It can be used in 2 modes
    - As a simple command line client
    - As a shell
    The shell can be started using dtrshell
    In both these modes the user will require to logon through a popup unless the co
    mmands being used do not connect to the DTR server(Exa: help command).
    If it is required that the login popup does not appear then one of the following
    should be true.
    1. The vfs config folder should have a user.xml file.
    2. The username & password should be specified using the following commandline o
    ptions:
        a. --username/-un <username>
        b. --password/-pwd <pwd>
    Note that if only the user name is specified as commandline argument even then t
    he user will be asked for the password via a popup.
    using the -def option the client to be used can be specified
    Once in the shell all commands can be used without using dtr before them
    Try:
    dtr help simple         list most common commands
    dtr help commands       list all commands
    dtr help command        help on a specific command
    dtr help usage          generic command line arguments
    dtr help configure      lists properties to cinfigure commands/options
    Commandline client Version : 1.60
    And When I run dtrshell.bat I receive login screen and when I enter valid credentials I receive this exception:
    >Initializing...
    >This may take a few seconds. Please wait...
    >Connecting to client ""
    Exception in thread "main" java.lang.IllegalStateException: The client specified
    is not correct or there is no active client present
            at com.tssap.dtr.client.commandline.Cache.getContext(Cache.java:143)
            at com.tssap.dtr.client.commandline.Cache.initialize(Cache.java:49)
            at com.tssap.dtr.client.commandline.Cache.getCache(Cache.java:63)
            at com.tssap.dtr.client.commandline.DTRShell.main(DTRShell.java:79)

  • Supplier Self-Registration in SRM

    In SRM 5.0, I am NOT able to see the 'Supplier Directory' from Prescreen. Full points assured. Thx.
    Raja

    Hi ,
    Chk the link in SPRO where you have to maintain the ROS_PRESCREEN BSP application as your Supplier directory.
    Supplier Relationship Management> SRM Server>
      Master Data-->Define External Web Services (Catalogs, Vendor Lists etc.)
    Rgds,
    Gautam

  • Problem during installation. sld registration

    Hello,
    I'm installing a SAP ERP 2005 system. The installation is stopped when sapinst try to register the system in the SLD. (SLD on solution manager 4.0).
    Here is the errors from the log:
    FRF-0007 (Unable to open RFC connection)
    MUT-03025 (Name or password is incorrect).
    Connection to http://hostname:50000/sld/admin with user J2EE_ADMIN is ok.
    Any ideas?
    Does problem come from a bad password entered in sapinst at the beginning?
    Could anyone tell me how to force sapinst to enter new sld informations again without restarting all the installation? Note that I've exactly the same problem with another similar installation which also use the same SLD.
    Many thanks for your support!
    Vanderperre Olivier

    My problem is solved!
    Sapinst tried to execute the RFC connexion with DDIC on client 300 witch was empty at this moment. I changed to use 001 and the installation finished successfully.
    Best Regards,
    Vanderperre Olivier

  • Business System not reflecting the XI Content for SRM

    Hi,
    We are currently working on the SUS-MM scenario.
    The landscape includes PI 7.11, SRM 7.0 and R/3 4.6C. SLD Communication is working fine between these systems.
    Integration Builder has SRM Server 7.0 and SRM Server IC 7.0 imported.
    The current status:
    We can successfully transfer vendors from SAP R/3 to SUS
    We cannot transfer transaction data from SAP R/3 to SUS, e.g. purchase orders etc
    Our Main Issue:
    The Business System INTEGRATION_SERVER_<SID> is imported into the Integration Builder from the SLD.
    On the Display communication component screen, the receiver and Sender tabs are not showing any of the SRM Server or IC components that have been imported into the ESR. However is displaying only the BASIS components that was imported during inital install.
    Because of this, we are not able to proceed with the configuration though the interfaces being available in the ESR. We are not sure what is that we are missing that is preventing the XI content for SRM from being displayed. Also, the PI business system in the SLD has the SRM Content listed under the installed products list.
    Any help would be appreciated.
    Thanks
    Venkat.

    Hello,
    do you have a solution? I'm facing the same issue.
    Regards,
    Sven

  • SLD Data Supplier Configuration in AS Java System

    Hi All,
    I am trying to configure my SLD manually in SAP Netweaver CE 7.1
    1. Both SLD_DataSupplier and SLD_Client Destinations are created and are successfully.
    2. All the security roles and groups are created and mapped in Identity Management (SAP NWA).
    3. Also SLD is running.
    4. CR_Content is imported from Browser.
    When i click SLD_DATAsupplier_configuration in SAP NWA- configuration management - infrasturcture
    Target_Url - undefined. 
    Both the Destionations are successfully when i ping those destinations.
    Also when i click "collect and send data". I am getting this error.
    Collect and Send Data Failed. Data transfer failed. Destination SLD_DataSupplier is undefined.
    When i see the trace file in \usr\sap\CE1\j00\j2ee\cluster\server0\log\default.trace
    i get the error
    SLD#sld#02004C4F4F50009C0000000300000A6C#2915050000000004#sap.com/tclmitsamuimainframe~wd#com.sap.sldserv.itsam.SAP_ITSAMJ2eeSLDDataSupplier_Impl#Administrator#1##F27A6B20FBAC11DFA34902004C4F4F50#5adebd80fbba11dfa57102004c4f4f50#5adebd80fbba11dfa57102004c4f4f50#0#Thread[HTTP Worker [@33483362],5,Dedicated_Application_Thread]#Plain##
    Data collection for SLD registration failed: Data transfer failed. Destination SLD_DataSupplier is undefined.
    [EXCEPTION]
    java.lang.RuntimeException: Data transfer failed. Destination SLD_DataSupplier is undefined.
    at com.sap.sldserv.itsam.SAP_ITSAMJ2eeSLDDataSupplier_Impl.CollectAndSendData(SAP_ITSAMJ2eeSLDDataSupplier_Impl.java:80)
    at com.sap.sldserv.itsam.SAP_ITSAMJ2eeSLDDataSupplierWrapper.invoke(SAP_ITSAMJ2eeSLDDataSupplierWrapper.java:156)
    How can i resolve this error. What other configurations has to be done for this.
    Thanks and Regards,
    Divya

    Hi Mark,
    SLD Configuration works fine with wizard based configurations. But manually when i try I fail in this automatic collect and send data.
    Also while creating destinations, i tried using
    http://localhost:50000
    http://localhost:50000/sld
    Ping is successful.
    But During Destination creation when i give
    http://localhost:50000/sld/ds. It says "bad Request. Parse error".
    Also i am referring this pdf.
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/20b1adee-ce37-2c10-16a3-ef3e1ca948da?quicklink=index&overridelayout=true
    Here at the picture where the target url is "Undefined". The automatic send property holds a value of true. In my case,
    target url is undefined. But
    automatic send = false.
    Can i change this parameter value.
    What other configuration is required.
    Divya
    Edited by: Divya V on Nov 29, 2010 5:09 PM

  • Facing Problem in SLD(getting 500 INTERNAL SERVER ERROR IN PORTAL)

    Dear All,
    we had ESS application just few days back it went to Go live , very frequently we are facing the issue
    Regards JCO 's , we are getting "500 Internal Server Error" in production Portal
    After getting the error ,the " Maintained JCO's" and "Created JCO'S " are both are disabled
    uder contenten administraton->webdynpro.
    But the SDL is in active , we can able to open SLD url every thing is also fine
    Technical system and every thing coming fine
    we checked SLD User also in SLD User Administration , the SLD user is also there it is not unlocked
    The problem is : if the problem is happend after restarting the server again it is coming properly
    Again after some time it is getting same error ,whith out doing any thing also some times the problem is resolving automatically
    we are not getting Root cause of this behaviour
    In our client side SLD is centralized ,they are not maintain locally
    If the SLD is Proble , the error has to come in Quality and Production also why bcz it is centralized
    But Some times 500 ERROR IN Prodution and some times in Quality.
    And some times the Portal is very slowly opening especially ESS application ,after restart happening it is some better
    again it is getting down after some time
    If it is NETWORK Iuuse or any firewall ect...in which way we can can with them and where
    Guru's share your knowledge it's a very critical for me what are he possible ways...
    Regards,
    Giri

    Here I am giving the LOG details which is available in SLD (J2EE) server
    #2.0 #2012 03 03 14:24:57:513#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201A70000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [17]#Plain##
    SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
    #2.0 #2012 03 03 14:26:06:739#+0530#Error#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector#
    #BC-AC-7XX#sap.com/tc~lm~aci~engine~baselib~05#005056BB552201AB0000000100000DF0#151402750000008310#sap.com/tc~lm~aci~monitor~app#com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(String)#Administrator#0#SAP J2EE Engine JTA Transaction : [9638fffffffe00fffffff85]#1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Thread[Managed_Application_Thread_29,5,Managed_Application_Thread]#Java##
    Unable to obtain Computer Systems, associated to NW Admin NWA_FOR_FirstLandScpSrvcName, from SLD. CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName" [this message was repeated 9 times]
    [EXCEPTION]
    {0}#1#com.sap.sld.api.wbem.exception.CIMException: CIM_ERR_FAILED: No such instance: SAP_NWAdministrator.CreationClassName="SAP_NWAdministrator",Name="NWA_FOR_FirstLandScpSrvcName"
         at com.sap.sld.api.wbem.client.WBEMRequestSender.convertErrorResponse(WBEMRequestSender.java:127)
         at com.sap.sld.api.wbem.client.WBEMRequestSender.convertErrorResponse(WBEMRequestSender.java:48)
         at com.sap.sld.api.wbem.client.WBEMRequestSender.send(WBEMRequestSender.java:272)
         at com.sap.sld.api.wbem.client.WBEMRemoteClient.sendAndCast(WBEMRemoteClient.java:936)
         at com.sap.sld.api.wbem.client.WBEMRemoteClient.associatorNamesImpl(WBEMRemoteClient.java:507)
         at com.sap.sld.api.wbem.client.WBEMAbstractClient.associatorNames(WBEMAbstractClient.java:544)
         at com.sap.nw.lm.aci.engine.base.sld.connection.AccSldConnector.getSldComputerSystemsForMonitoring(AccSldConnector.java:3731)
         at com.sap.nw.lm.aci.monitor.fetch.util.MonitoringSldAdapter.getAllHostnames(MonitoringSldAdapter.java:277)
         at com.sap.nw.lm.aci.monitor.fetch.manager.PrefetchPackageUtil.repackageCs(PrefetchPackageUtil.java:71)
         at com.sap.nw.lm.aci.monitor.fetch.manager.PrefetchPackageUtil.repackageAll(PrefetchPackageUtil.java:58)
         at com.sap.nw.lm.aci.monitor.fetch.manager.FetchManager.repackageIfRequired(FetchManager.java:1046)
         at com.sap.nw.lm.aci.monitor.fetch.manager.FetchManager.run(FetchManager.java:435)
         at com.sap.nw.lm.aci.monitor.fetch.job.FetchJobBean.onJob(FetchJobBean.java:67)
         at com.sap.engine.services.scheduler.runtime.mdb.MDBJobDelegateImpl$2.run(MDBJobDelegateImpl.java:233)
         at java.security.AccessController.doPrivileged(Native Method)
         at javax.security.auth.Subject.doAs(Subject.java:396)
         at com.sap.engine.services.scheduler.runtime.mdb.MDBJobDelegateImpl.onMessage(MDBJobDelegateImpl.java:267)
         at com.sap.scheduler.runtime.mdb.MDBJobImplementation.onMessage(MDBJobImplementation.java:60)
         at sun.reflect.GeneratedMethodAccessor284.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
         at java.lang.reflect.Method.invoke(Method.java:585)
         at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
         at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
         at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
         at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
         at $Proxy1058.onMessage(Unknown Source)
         at com.sap.jms.resourceadapter.RaServerSession.internalOnMessage(RaServerSession.java:188)
         at com.sap.jms.resourceadapter.RaServerSession.onMessage(RaServerSession.java:330)
         at com.sap.jms.client.session.JMSSession.deliverMessage(JMSSession.java:805)
         at com.sap.jms.client.session.JMSSession.run(JMSSession.java:709)
         at com.sap.jms.resourceadapter.RaServerSession.run(RaServerSession.java:379)
         at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:420)
         at com.sap.engine.core.thread.execution.Executable.run(Executable.java:109)
         at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
    #2.0 #2012 03 03 14:26:57:526#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201B00000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [6]#Plain##
    SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
    #2.0 #2012 03 03 14:28:57:522#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201B70000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [5]#Plain##
    SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
    #2.0 #2012 03 03 14:30:57:519#+0530#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
    #BC-XI-CON-AFW#com.sap.aii.af.lib#005056BB552201BE0000000000000DF0#151402750000001894##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#Guest#0##1014F5C2650011E1B811005056BB5522#1014f5c2650011e1b811005056bb5522#1014f5c2650011e1b811005056bb5522#0#Application [20]#Plain##
    SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
    Edited by: giriep on Mar 3, 2012 11:38 AM

  • Supplier Registration Questionnaire

    Hi everybody,
    I am setting up supplier registration in SRM 5.0. I have couple of questions:
    - How is the auto sending of the questionnaire triggerred (SO50 has been setup accordingly)? I got couple of questionnaires auto sent to my mailbox with couple of hours delay yesterday. Today I have not recd any questionnaires for the registration that was done early this morning.
    - I want to send the questionnaire only as attachement since we are using Outlook and Send button has not been working since Outlook 2000 (as per note 840661). After reading the note I still cannot find the '/URL/' that the note refers me to.
    - Finally when I try to attach a document to a supplier profile in "screen suppliers", nothing seems to happen.
    Any help you provide will be much appreciated.
    Thanks
    Venkat

    Ramki -
    Thanks for your prompt response! Really appreciate your help.
    1) Everytime I have a new registration I can see the survey questionnaire email is created but it is in waiting status (the count seems to go up). I cannot see the emails in SOST. All other emails (including manual sending of surveys) seem to be processed ok. Any ideas?
    2) Resolved.
    3) SICF settings have been done. Essentially when I click on the Browse button (in Documents tab) and then click Add button, the screen seems to do something but no attachments show up (in EBP server the attachment shows up at this point). I have ROS and EBP running in 2 different clients. Attachments seem to be working fine in EBP. Is there any Java configuration that needs to be done for the new ROS client for attachments?
    Any other ideas will be most welcome.
    Thanks in advance for your help.
    Venkat

  • Supplier Registration Process

    Hi,
    I am trying to configure Supplier Registration and preselection process in EBP.
    1. Supplier is filling Registration form and sending the same.
    2. This data is appearing in preselect supplier screen with option to accept and reject or set to NEW.
    3. Manager is accepting the same in preselect screen but he is not getting any indication or message that action is complete. There is no acceptance indication is coming.
    4. Further in preselect screen on clicking supplier link supplier data should appear that is also not happening
    5. While I am going to Manage business partner to convert new  registered to bidder or Vendor than also it is not appearing.
    I have activated all relevent services and all customization is done as per configuration guide.
    What is missing?
    Thanks
    Sanjay 
    Thanks

    Hello Sanjay,
    3. There is no return message when accepting the supplier: its BP status is set to "Accepted" so it disappears from the refreshed list if you have default search criteria 'New'.
    You should find the corresponding Prospect with BP transaction, with 'not released' flag unchecked in status tab.
    By accepting this prospect, you only change its status via function ROS_BUPA_CHANGE_STATUS.
    If there is a supplier directory activated in CCM, then this accepted vendor is sent to CCM, where it becomes selectable via OPI.
    I think this is the only XI message related to this acceptance.
    Otherwise, this accepted prospect is available in SRM/SUS Supplier directory, via OPI --> your step 5
    There is no workflow at the moment.
    4- In supplier prescreening, no additional data is supposed to be displayed (you just changed the prospect status)
    5- if Self registration on SRM client: In SRM transaction Manage Business Partner, enter the new BP ID (got it from prescreening list) or search it and convert it to vendor. Then add all purchasing data, vendor org ID and so on.
    Self registration & SUS are supposed to work on the same client/server, and SRM on another one.
    I guess you are trying to make it work on a all-in-one installation. If not, the prospect remains in SUS and that's why you don't find it in SRM.
    Then see next step:
    You can also access directly to the accepted prospect from all sourcing activities (SOCO, VL, BID), via OPI "catalog". In that case you need purchaser autorisations to create a vendor in SRM automatically from retrive OPI data.
    If SUS activated, an XI message is created to send the vendor to SUS.
    You need to define a new web service in SRM, with type "List of vendors" where you define the vendor root node, and the calling URL:
    http://<server>:<port>/sap/bc/bsp/sap/ros_prescreen/main.do
    The same BSP is used for Supplier Directory, but the display is different.
    Assign this web service ID in org attribute "Catalog ID".
    Rgds
    Christophe

Maybe you are looking for