Technical system for idoc

i am doing a file2idoc scenario.i want to crete a technical system as web-as-abap.but we are having ecc6.0.here  we are having both abap & xi .here those are having  different host name.here in this scenario i am using idoc as receiver system.so will i use hostnbame of abap or xi in  technical system(web-as-abap)??

Hi Michal,
Thanks for reply.
Regd Logical System, i did like this.
T-Code: SALE
Copied 'Logical System' name which is assigned for Client 800.
and While creating SLD,
Technical System: ( for Receiver IDOC)
1.Web As ABAP
2.Web AS ABAP Name (SID): FIC ( i don't know where to find SID , somebody asked me to give my R/3 System name.
Note:Other guy told me like this to find SID, T-Code:SM51
There will be name Seperated by 2 Underscores, the part next to 2nd underscore is SID. So, in my R/3 System, its like FIC_FIC_00, but when i tried to give 00 as SID, its not accepting, so i gave FIC)
Installtion Number:    (i gave)
Database hostname: FIC
3. In next page Instance Number:00
4. In next page Host Name: FIC and clicked Add
5. Client: 800
Logical System: T90CLNT090 ( which is from T-Code Sale)
Business System:
1. New_BS_IDOC
2. Selected the Technical System created above.
Still cannot find in "Adapter Specific Identifiers"
<i>>>>you need to have logical system for your r3 business system (which you put in header mapping - sender service of the receiver agreement)</i>
do i need to provide, receiver Buss System for Sender Service of Receiver Agreement?
and i looked at weblog given, i am unable to find anything under T-Code IDX2, its empty..
Any Sugg?

Similar Messages

  • Error While Creating Technical System for SNC

    Hi There,
    I am trying to create technical system for SNC in SLD, I am not able to seee SNC as a s/w component/product in the list.
    when I checked the list of components in SLD, I found SNC is there under product "SCMSNC" but this product is not in the list of products.
    Please help me how I can get "SCMSNC" product in the product list.
    Thanks,
    Nishant

    Can you please explain it little bit clearly?
    I think you first create product, then SWC and then try to create Technical system.
    While you will create the Technical system, in the last step it will ask you for installed products.
    There you can specify ur product.
    Thanks,
    Hetal

  • MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER

    Hi Experts,
    How the  MATERIAL LINK TO ONE SAP SYSTEM TO ANOTHER SAP SYSTEM FOR IDOC TRANSFER?
    Scenario : when 2nd system create the invoice,it will create a po in the 1st system.
    51 error msg we are getting material does not exists.but the material is available in the receiving plant.
    Please suggest

    If you say the material master is available in the 1st system (where you create the order), then the material number in the IDOC  may not match with the material number in your database.
    leading zeros. material number stored as alphanumeris instead of numeric.

  • Technical system for integration server

    hi all
    what are the steps involved in creating a technical system for integration server?what is the role of RZ70 in creating technical system for integration server?
    regards
    bhasker.

    Hi
    Technical systems should be registered by calling transaction RZ70 in technical system. Activate the profile & excute the job.
    Make sure that you have provided correct SLD Host name & Gateway (Either central or local on XI).
    Once you execute this function a default background job will be scheduled which will run after every 12 Hrs.
    Cheers
    Rakesh

  • Two entries for every technical system for XI in SLD

    Hi,
    Last weekend we had a patch upgrade in our Production env for SAP PI system.
    After that we got the Cache error (Cache notification from Integration Directory failedError when accessing the System Landscape Directory) in RWB -- "Cache Connectivity Test -> IR -> ID -> Adapter Engines".
    And
    In SLD->Technical Systems->all (Adapter Engine, Integration Directory, Integration Repository, RWB).
    e.g.:There are two Adapter Engines:
    Adapter Engine on p80.p80xxxxx
    and
    Adapter Engine on p80.p80xxxxx\p80
    Our Basis team contacted SAP for help & SAP has suggested as below.
    "We compared the SLD->Technical Systems for QA (Q80) and PROD (P80), and found that for the production box (P80), each XI component is registered Twice.
    Now as per the note 764176, we have to delete the entries in the SLD -> Technical Systems. And these will be re-created after a restart.
    Could you please let us know whether these have been maintained for any special reason or we can go ahead and delete them."
    If you have any idea if those two should be maintained or not, please suggest how to proceed.
    Thank you & Best regards,
    Farooq.

    Hi Farooq,
       I have faced the same issue and got resolved by 764176.
    you can go ahead and implement the note 764176 which will resolve your issue.
    Regards,
    naveen

  • Technical system for Oracle in SLD

    Hi All,
    I know the steps to create a technical system for a SAPR/3 system in SLD.
    Can any one tell me the steps to create a technical system for accessing Oracle Database in SLD.
    Thanks in advance,
    Bhavyasri.M

    Hi Shilpa,
    Can u plz provide me the steps in more detail to add the Oracle system in SLD....
    Thanks in advance,
    Bhavyasri.M.

  • Business  system for idoc reciver communication channel.

    hi gurus,
    iam doing one file to idoc scenerio.
    for defining reciver idoc adapter ,which type of businees system i required that is configured in SLD.
    pls guide me .
    warm regards.

    Hi
    You can use th Buiness system as a receiver for IDOC.
    Making sure
    1. the LS of the system(R/3) is same in the SLD and it is also reflecting in the adapter specific attributes in the ID.
    2. Use the same LS name for the BS pointng to FIle in the SLD.
    Complete the IDOC configuration from XI
    1. Create the RFC dest from XI to ECC
    2. Create the Trfc port and call this RFC dest created..
    3. Use this Trfc port in the IDOC receiver
    On ECC:
    Make sure the Partner Profiles is created properly.
    it is suggested to use always the business systems when you deal with IDOC and Proxies.
    Edited by: Nisar Khan on Feb 27, 2008 1:31 PM

  • Creation of business and technical systems for sld

    hi
    can any one help me out, to creation of technical and business system for system landscape directory ....give me detailed instructions.
    this is urgent requirement
    regds
    venky

    Hi pervalli,
    plz look to
    http://help.sap.com/saphelp_nw04/helpdata/de/31/f0ff69551e4f259fdad799a229363e/frameset.htm
    Regards,
    Udo

  • Logical system for IDoc acknowledgment?

    Hi,
    HTTP --> XI --> IDOC (with acknowledgment) is my scenario
    whether the inbound and outbound parameters should be configured in the same logical system or in a different one (in transaction we20)
    Thanks,
    RPN

    For IDOC acknowledgement ,go thru this and do the settings :
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe
    This will help u :
    Configuration Tips for a Business Service/Integration Process to send back ALE audit IDOC

  • Regarding technical system  for Portal

    Hi all:
         When Define Server for Resources for ESS on backend, it asks the technical name of Portal, can you please tell me where to
    find it ?
    Thank you very much .

    Hi,
    FQDN means fully qualified name 
    http://hostname :port/irj/portal  ..your host name will become FQDN if it is name instead of ipaddress.
    put hostname of portal as technical name.

  • How To Create A Technical And Business Systems For Web AS ABAP ???

    Hi Experts,
    How To Create A Technical And Business Systems For Web AS ABAP ???
    Please Let me Know All the Step-By-Step Process to Create ????
    Points Will be Given
    Regards
    Khanna

    Hi Sumit,
    When U Told the thing that first time to execute the RZ70 and All i Did this in XI System
    So I got An Entry for the Technical System for XI System.
    Now i Deleted that and Executed RZ70 in R/3.
    When I Executed RZ70, I got this Error.
    <b> "RFC Call failed: Error Opening an RFC Connection "</b>.
    Now I am Unable to see Any Technical System  Under Web As ABAP. It's Showing Empty Now.
    Please Let me know
    Regards
    Khanna

  • System type for technical system.

    Hi All,
    I want to create a new technical system for my receiver sys. The receiver is the PI .
    so its SAP->XI->XI Interface.
    Can anybady explain what will be the System Type for receiver PI.(web as abap or ...etc)
    Also pls explain the diffrent system types.

    Hi,
    Technical system for PI is of type Web As ABAP (because PI is also a product of SAP)
    Other technical system types:
    Web as ABAP -
    > For SAP applications.
    Web as JAVA -
    > Web AS Java systems consist of one or more instances and each instance is installed
                       on a separate host. An instance itself consists of cluster nodes that can
                       communicate with each other.For Enterprise java applications on J2EE stack.
    Third party -
    > For People soft, BAAN, JDEdwords, ...........
    Regards
    Ramesh

  • SLD configuration for DXI / PXI technical systems

    Hello,
    we have a problem when transporting XI configuration objects from XI dev to XI prod. The transport objects arrive in XI prod, but the name of the business system (for the SAP backend system) is not converted from dev business system (T01CLNT010) to prod business system (P01CLNT01) although the transport target for T01CLNT010 business system was set correctly (we are using business system groups Dev and Prod). And the "related integration server" for T01CLNT010 was also set correctly to DXICLNT010.
    But then I noticed that the technical system for the DXI (XI Dev) is configured as follows:
    TMS Domain ("DOMAIN_PXI") and TMS Transport Group Name GROUP_PXI ("GROUP_PXI") have the same values as PXI. Is that correct ?? We are using file transport, not CMS.
    Another strange effect is that when I set the group in business system DXICLNT010 to Dev, that is also applied to business system PXICLNT010 ! Which is of course not what I want.
    I assume I have to associate DXICLNT010 to Dev and PXICLNT010 to Prod, same as for T01CLNT010 / P01CLNT010. Correct ? Or does the group in the XI business systems not matter ?
    Can anyone post an example of a working SLD configuration with two XI system dev and prod ? What values do I have to use in the XI technical and business systems, so that the transport will work ?
    CSY

    There's obviously something wrong in the SLD configuration for the exchange infrastructure systems. The error you're describing (one system pointing to another) usually occurs when one system is generated through homogeneous system copy of another system (was that your case?). I've seen that behaviour once and they corrected it by manually deleting the exchange infrastructure systems from SLD and creating them again from scratch.
    Anyway, I highly recommend you to get an expert NW Basis consultant to realize a check in it before you proceed any further.
    Aside of that, you're correct in your assumptions.
    Your config in SLD should be like:
    DEV_GROUP:
    - DXI
    - T01
    PRD_GROUP:
    - PXI
    - P01
    It's always 1 XI BS per group.
    Also, if you use separate SLDs for XI Dev and XI Prd, you have to make sure that this configuration is reflected in both SLDs. So, if you make it one SLD instance, you must generate a delta export zip file from the SLD where you did the configuration and import this zip file in the other SLD instance.
    If you use a central SLD, then it's not necessary.
    Regards,
    Henrique.

  • When I can reuse Business and Technical Systems in IR and ID

    Assuming the case(1 scenario) when I already created All SLD object Business System , technical system, SWC and product for interface scenario when file is send from R/3 MM module(Outbound) to XI through File adapter and than mapped and send to 3 party partner via firewall ftp server... All SLD object exists and are created.
    In a different scenario(2 Scenario) the 3 party partner will have to send via XI some MM related data and XI will have to feed this data into R/3 via different type adapter &#8211; this time Idoc adapter(Inbound)
    My questions are:
    1)In 2 scenario - Can I use same already created 2 Business systems for both R/3 and 3 party partner or I need to create new ones?
    Or at lease can use one of the business systems. With words &#8211; is the Business system dependable on type of adapter, inbound/outbound ?What is the criteria for reusing business system for second scenario?
    2)In 2 scenario -Can I use same already created Technical systems for both R/3 and 3 party partner or I need to create new ones?
    Same questions here...for technical system  -  can I reuse it  and when I need newone...
    Thanks all
    Regards
    Jon

    1. If u r posting data to the same R/3 with same client then u can use same WebAS ABAP Business System. U can use same third party business system for this.
    The criteria for reuse is just that if the systems are same (in case of R/3 - the clients should be same), then u should reuse it.
    2.Only 1 Technical system is created for one R3 system. This will be of type WebAS ABAP. So u will have to use same Technical system for both the scenario
    For 3rd party case, u can use different technical system, but that would be redundant. So better to use one.
    Regards,
    Prateek

  • Error while creating Technical System

    Hi
    i am creating Technical system in SLD. I gave all inputs for host name, Instance, License correctly.
    When i press next, It is throwing this error. Do anyone have any idea about this.
    500   Internal Server Error
      Web Dynpro Container/SAP J2EE Engine/6.40 
    Failed to process request. Please contact your system administrator.
    [Hide]
    Error Summary
    While processing the current request, an exception occured which could not be handled by the application or the framework.
    If the information contained on this page doesn't help you to find and correct the cause of the problem, please contact your system administrator. To facilitate analysis of the problem, keep a copy of this error page. Hint: Most browsers allow to select all content, copy it and then paste it into an empty document (e.g. email or simple text file).
    Root Cause
    The initial exception that caused the request to fail, was:
       java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
        at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
        at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
        at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
        at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
        at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
        ... 27 more
    See full exception chain for details.
    System Environment
    Client
    Web Dynpro Client Type HTML Client
    User agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; InfoPath.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
    Version null
    DOM version null
    Client Type msie6
    Client Type Profile ie6
    ActiveX enabled
    Cookies enabled
    Frames enabled
    Java Applets enabled
    JavaScript enabled
    Tables enabled
    VB Script enabled
    Server
    Web Dynpro Runtime Vendor: SAP, build ID: 7.0006.20060302084208.0000 (release=NW04S_06_REL, buildtime=2006-03-04:17:33:21[UTC], changelist=10570, host=pwdfm114), build date: Sat Oct 14 19:38:14 GMT+05:30 2006
    J2EE Engine 7.00 patchlevel
    Java VM Java HotSpot(TM) Server VM, version:1.4.2_12-b03, vendor: Sun Microsystems Inc.
    Operating system Windows 2003, version: 5.2, architecture: x86
    Session & Other
    Session Locale en
    Time of Failure Sat Nov 11 14:04:06 GMT+05:30 2006 (Java Time: 1163234046750)
    Web Dynpro Code Generation Infos
    sap.com/tcsldwd~main
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~landscape
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwddispwda
    No information available null
    sap.com/tcsldwd~businesssystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~technicalsystem
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcwdcorecomp
    No information available null
    sap.com/tcsldwd~softwarecatalog
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    sap.com/tcsldwd~namereservation
    SapDictionaryGenerationCore 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:18[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapDictionaryGenerationTemplates 7.0006.20051128142640.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:17:25[UTC], changelist=378068, host=PWDFM101.wdf.sap.corp)
    SapGenerationFrameworkCore 7.0006.20050713144242.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:06[UTC], changelist=357697, host=PWDFM101.wdf.sap.corp)
    SapIdeWebDynproCheckLayer 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:22:50[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCommon 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:45[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelCore 7.0006.20050929162929.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:07:38[UTC], changelist=369752, host=PWDFM101.wdf.sap.corp)
    SapMetamodelDictionary 7.0006.20051128142655.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:15:16[UTC], changelist=378069, host=PWDFM101.wdf.sap.corp)
    SapMetamodelWebDynpro 7.0006.20051128151854.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:19:38[UTC], changelist=378109, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationCTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    SapWebDynproGenerationCore 7.0006.20051128151834.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:23:00[UTC], changelist=378108, host=PWDFM101.wdf.sap.corp)
    SapWebDynproGenerationTemplates 7.0006.20060118164839.0000 (release=645_VAL_REL, buildtime=2006-01-18:19:44:56[UTC], changelist=385420, host=pwdfm101)
    Detailed Error Information
    Detailed Exception Chain
    java.lang.IllegalArgumentException: The node, node element, and attribute info MUST NOT be null
         at com.sap.tc.webdynpro.progmodel.controller.MessageManager.reportContextAttributeMessage(MessageManager.java:940)
         at com.sap.sld.wd.technicalsystem.NewABAPSystem2.onActionNext(NewABAPSystem2.java:369)
         at com.sap.sld.wd.technicalsystem.wdp.InternalNewABAPSystem2.wdInvokeEventHandler(InternalNewABAPSystem2.java:344)
         at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
         at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at java.security.AccessController.doPrivileged(Native Method)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
    Thanks in Advance
    Vijay Raheja

    HI Michal Krawczyk,
    Thanks for your response. i am working on XI 7.0 and when i go to SLD-> Adminitsrtion-> SLD Data Supplier. There i tried to add SLD CLient.
    It is asking me for :
    -URL of target SLD system, e.g. http://host:port/
    -User
    -Password.
    What should i give here. WHat will be port for R/3 system to which i want to connect.
    Just to add: I have already created Technical system for R/3(CLient 600). I added this through SLD only. But now it is giving error for Technical SYstem for same R/3(Clinet 812).
    Thanks,
    Vijay Raheja

Maybe you are looking for

  • Photosmart 7510

    we have a photosmart 7510,  it has print issues. have followed all the tips tricks and troubleshooting. we decided to buy a new print head. the  printhead arrived today.  it is the wrong part.  the  printhead we need has 5 ink cartridge slots,  (3 co

  • App Error 602 & "Uncaught exception: Application net_rim_bb_messaging_app(144) is not responding; process terminated"

    Hi, I have spent a whole and very frustrating day trying to solve the following problem and in exasperation I resort to a posting here. Note no changes had been made to the phone prior to the start of the problem. My Blackberry 9800 Torch freezes on

  • Is Apple TV going to get Amazon Prime?

    Is Apple TV going to get Amazon Prime?

  • Copy cost center planning to profit center

    Hi dear,i did cost center planning with KP06,then i try 1KE0 to copy cost center planning data to profit center,but seems it does not work,because there is no relevant planning data when i use KE5Z to check planning data can someboyd kindly tell me w

  • Games on intel imac

    having just received my new intel iMac, it would appear there is no Nanosaur 2 - which is very disappointing for my 4 year old son! Could somebody tell me if this is either; hiding somewhere on the hard drive and I'm just too stupid to find it (if so