Creating interface determination error

Hi Experts,
I upgrade the our PI system to
XI TOOLS 7.10 SP006 11
XI PCK 7.10 SP006 11
After that, i cant create interface determination with wizard. When i finish the wizard, interface determination isnt created and there is a lock in the integration builder.
I tried to make manual interface determination but i cant select the operation mapping..
im waiting ur answers
thanks

Hi,Arvind:
  Did you upgrade to SPS06 with the whole SP stack or just upgrade several components of PI?
  If you just upgrade several components of PI,it is not recommended by SAP.
  If you upgrade the whole components with SPS06,try to upgrade to SPS07 and take a look at NOTES:1259837&1263112, or the java component "ESPFRAMEWORK07_0-20001918" can not be deployed successfully.
regards
yu ming

Similar Messages

  • BPM interface determination error

    Hi All,
    i have BPM scenario. scenario like three files coming from the sender  once picking the all file i have to merge these file based on the common filed in three files.
    for this i used correlation in BPM
    i followed the below steps:
    1)  i creatd three out bound service interfaces for the sender three files
    2)  one inbound  service interface for the  receiver.
    3)  four abstract service interfaces for the BPM.
    5)  Operation mapping between the abstract interfaces.
    ID objects creation :
    imported the integration process in ID from IR.
    communication componets created for the sender & receiver
    4 receiver determinations created 3 RD between Sender bussiness component & BPM ,1 RD between BPM & receiver business component
    4 Interfaces determinastion created as per as RD
    3 sender agreements
    1 receiver agreement
    while testing i got this error in SXMB_MONI
    RCVR_DETERMINATION">CX_RD_PLSRV</SAP:Code>
      <SAP:P1>Problem while determining receivers using interface mapping: No operation with XML root tag
    i got confusion while creatin the Interfaces Determination i.e weather do we need mention Operation mapping between outbound service interface & abstract service interface
    please correct what is the correct process to create the Interface determination in BPM like this scenario.
    thanks in advance

    Are you doing any content conversion in Sender file Adapter then check whether the Flat file properly converted to XML file or not?
    You need to create Interface determination but if source and target interface message type is same then no need to specify operation mappinhg in Interface determiination.
    So interface determination should be there without any operation mapping

  • Bposting document not created(acccount determination error)

    Dear All
    when i am creating invoice in vf01, the system is unable to create accounting document
    i have checked acc assignment of customer and material its their, but still its giveing erro
    error in acc determination
    this is the message iam geting 
    Bposting document not created(acccount determination error)
    how to resolve this issue
    Thanks
    jahangir

    Hi Jahangir,
    Go to VF02 --> Enter --> In change overview screen --> Click at "Enviroment" (Menu) --> Click at "Acc. Determination Analysis" --> Click at "Revenue Accounts"
    You can see the condition types there ---> Open the tree one by one --> see the details on right side --> check for which combination the G/L account is missing
    Maintain the entry in VKOA.
    After that come back to VF02 and release the document.
    If the error still there then check the analysis, whether the required record determined or not.
    Hope this helps.
    Regards,
    MT

  • SOAP Sender with additional header: Interface determination error

    Hello Experts,
    I need to implement a scenario where in sender will add custom header fields and in PI, the values needs to captured. Second step: Based on the custom header value, the receiver needs to be determined.
    Scenario: SOAP Sender -> PI -> SOAP Receiver
    Request Message:
    <RequestMsg>
         <request>
              <Field 1>...</Field 1>
              <Field 2>...</Field 2>
              <Field 3>...</Field 3>
         </request>
    </RequestMsg>
    Without any custom SOAP header, I have created Request / Response Message, Message Mapping, Service Interfaces (Inbound & Outbound) and Operation Mapping and tested the scenario by triggering call through SOAP UI, it works fine. SOAP Request XML looks like below:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:v1="http://www.test.abc.com/v1">
        <soapenv:Header />
        <soapenv:Body>
          <v1:RequestMsg>
             <request>
                  <Field 1>1</Field 1> 
                   <Field 2>2</Field 2>
                   <Field 3>3</Field 3>
             </request>
          </v1:RequestMsg>
       </soapenv:Body>
    </soapenv:Envelope>
    To use customer fields in SOAP Header, I have checked the option "Do Not Use SOAP Envelope" in the SOAP Sender CC and added "&nosoap=true" to url. SOAP Request XML looks like below:
    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:v1="http://www.test.abc.com/v1">
        <soapenv:Header >
              <id>REC1</id>
         </soapenv:Header >
        <soapenv:Body>
          <v1:RequestMsg>
             <request>
                  <Field 1>1</Field 1> 
                   <Field 2>2</Field 2>
                   <Field 3>3</Field 3>
             </request>
          </v1:RequestMsg>
       </soapenv:Body>
    </soapenv:Envelope>
    Now, when I invoke the url, I see that the message reaches PI but it throws error: RoutingException: InterfaceDetermination did not yield any actual interface
    Please note that I have added a Java Mapping before main message mapping to read the soap header and pass only the request message to the next message mapping.
    I am sure, I am missing important steps in the configuration. Please help me in reolving the issue.
    Thanks & Regards,
    Ankit Srivastava

    Hello Hareesh,
    Bingo! The second option suggested by Nicolas worked like a charm. I am just copying the same here:
    -----In ESR, you set the attribute "Interface Pattern" of the outbound service interface as "Stateless (XI30-compatible)", which does not use operations.----
    Thanks a lot. Now, I will be able to concentrate on the next steps.
    Regards,
    Ankit Srivastava

  • Need of creating receiver determination and interface determination

    what is the need of creating interface determination where as providing all the details in Receiver determination?

    Hi,
    The loose coupling between the Interface mapping and receiver determination have provided the compatibility for reusability.
    The Interface determination maintained and just linked to receiver determination so you could have multiple receiver determinations with common interface determination or vice-versa.
    If you provide all the information in receiver determination then, it would be very dfficult to have the various mappins for multiple receivers maintained in receiver determination.
    Interface determination is applied at runtime to all messages to be processed. Thus from security point of view of transaction of data. its preferable.
    Thanks
    Swarup

  • Q? Receiver determination error ????

    Hi all.
    I wana transfer from R3 IDOC to XML with FTP service.
    Although I think configuration completely was finished, happens error.
    How can i correct?
    It's results from test configuration.
        Receiver Determination  <Not found>
           Internal Error
           HTTP connection to ABAP Runtime failed.
           Error: 403 Forbidden
           URL: http://R3:8000/sap/xi/simulation?sap-client=
           User: XIDIRUSER Check
    =======================================================
    Scenario : R3 IDOC -> FTP XML (import Ext Definition DTD)
    1) create Business Service System     : R3, FTP
    2) create Message Interface about FTP : MI_FTP_in
    3) create Interface Mapping R3 & FTP  : IM_R3_to_FTP
    4) import business system about FTP server : FTP
    5) create Receiver Determination : |R3|IDOC_inf
         sender : R3
               - interface : IDOC interface
         configured Receivers
               - Service   : FTP
               - Receiver  : FTP
               - interface : MI_FTP_in
               - Mapping   : IM_R3_to_FTP
               - Receiver Agreement: FTP_file_adapter
    6) create Interface Determination: |R3|IDOC_inf||FTP
         Sender   : R3
               - interface : IDOC interface
         receiver : FTP
         Configured Inbound Interface
               - Inbound interface  : MI_FTP_in
               - interface Mapping  : IM_R3_to_FTP
    7) create Receiver  Agreement : |R3|IDOC_inf|MI_FTP_in
         Sender   : R3
         Receiver : FTP
               - interface : MI_FTP_in
               - Receiver Channel : FTP_File_Adapter
    ========================================================

    Hi,
      Please can you check you Cache is updated or not.If cache is succesfull then check the Port & RFC Destination and Partner profiles  R/3 side and XI side.
    R u testing this scenario using WE19.
    If using we 19 then check the your sender information and receiver information (I mean to say Port,Parner...with outbound parameters )
    Regards,
    Venu.

  • Interface mapping not visible in interface determination

    Hi,
    when i create Interface determination in ID i could see Message interface and i could not my Interface mapping in that.
    It is saying no objects found.
    when i select enhanced instead of standard i could see my Interface mapping
    plz give some idea reg. this
    Thanks

    Hi,
    Check if there is any Interface mapping available between the Outbound Message Interface name and Inbound Message Interface name which you are using in your Interface Determination. Check carefully.
    Thanks
    aMit

  • Question related to enhanced interface determination option in ID

    HI All,
    I am trying to create a 1:N message mapping and here are the steps which I have done.
    1. Created a Source Data type, Message type , Message Interface and activated
    2. Created 3 Target Data types, 3 Message types and 3 Message interfaces and activated.
    3. Created a Message mapping and Interface Mappings in Message interface and activated.
    While creating the configuration(ID) i have to use the enhanced interface determination but my interface mapping is not getting reflected in the popup.
    All of the above objects are created in a Customer Specific software components but however if i create the Message Mapping and Interface Mapping in SCV SAP_BASIS and Namespace http://sap.com/xi/XI/System then i am able to select the interface mapping through enhanced interface determination option during configuration.
    What i wanted to know is do I need to create the Interface mapping in SCV SAP_BASIS instead of Customer Specific SCV.
    Regards,
    Swaroop

    Which version of PI are you working on?We develop objects in customer SWC not SAP Basis.
    Create Interface determination and add 3 operation mappings by using + button , write a condition if you required.I hope you created one Bussiness compoenent for Target.

  • Error while opening the Interface determination

    Hi,
    I am working on PI system(unix platform) which is a system copy(from a windows platform).
    When i tried opening few interface determinations which are already present in ID,  it gives me following Error.
    ====================================================================
    = Root Exception ===================================================
    ====================================================================
    Thrown:
    com.sap.aii.utilxi.swing.toolkit.ServerCallCancelledException: Unexpected exception.
         at com.sap.aii.ib.clsif.gen.BeanAccessHandler.handleRuntimeExInBusinessMethod(BeanAccessHandler.java:87)
         at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:112)
         at com.sap.aii.ib.client.oa.ObjectHandler.read(ObjectHandler.java:119)
         at com.sap.aii.ib.gui.editor.DefaultPersistenceHandler.load(DefaultPersistenceHandler.java:94)
         at com.sap.aii.ib.gui.editor.XiDocument.load(XiDocument.java:249)
         at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.load(OpenCommand.java:353)
         at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.localOpen(OpenCommand.java:273)
         at com.sap.aii.utilxi.swing.framework.cmd.OpenCommand.execute(OpenCommand.java:211)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.execute(ExecutionContext.java:198)
         at com.sap.aii.utilxi.swing.framework.ExecutionContext.executeSafe(ExecutionContext.java:154)
         at com.sap.aii.ib.gui.operations.OperationsServiceProvider.executeDefaultOperation(OperationsServiceProvider.java:295)
         at com.sap.aii.ib.gui.nav.HierarchyNode.executeDefaultOperation(HierarchyNode.java:59)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.DefaultTreeCard.handleHierarchyEvent(DefaultTreeCard.java:198)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.fireHierarchyActionEvent(ThreadedTree.java:542)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree.executeStandardOperation(ThreadedTree.java:2264)
         at com.sap.aii.utilxi.swing.framework.navigation.tree.ThreadedTree$DblClickHandler.mouseReleased(ThreadedTree.java:2196)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.AWTEventMulticaster.mouseReleased(Unknown Source)
         at java.awt.Component.processMouseEvent(Unknown Source)
         at javax.swing.JComponent.processMouseEvent(Unknown Source)
         at java.awt.Component.processEvent(Unknown Source)
         at java.awt.Container.processEvent(Unknown Source)
         at java.awt.Component.dispatchEventImpl(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
         at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
         at java.awt.Container.dispatchEventImpl(Unknown Source)
         at java.awt.Window.dispatchEventImpl(Unknown Source)
         at java.awt.Component.dispatchEvent(Unknown Source)
         at java.awt.EventQueue.dispatchEvent(Unknown Source)
         at com.sap.aii.utilxi.swing.toolkit.Guitilities$EventProcessor.dispatchEvent(Guitilities.java:319)
         at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
         at java.awt.EventDispatchThread.run(Unknown Source)
    Caused by: com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:643)
         at com.sap.engine.services.rmi_p4.P4ObjectBrokerClientImpl.getException(P4ObjectBrokerClientImpl.java:612)
         at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:160)
         at com.sap.engine.services.rmi_p4.reflect.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:52)
         at $Proxy26.read(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at com.sap.engine.services.ejb3.runtime.impl.StatelessRemoteStubInvocationHandler.invoke(StatelessRemoteStubInvocationHandler.java:89)
         at $Proxy27.read(Unknown Source)
         at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at com.sap.aii.ib.clsif.login.BeanProxy.invoke(BeanProxy.java:114)
         at $Proxy27.read(Unknown Source)
         at com.sap.aii.ib.clsif.oa.ObjectAccess.read(ObjectAccess.java:101)
         ... 39 more
    Caused by: java.io.InvalidClassException: com.sap.aii.ib.bom.gen.container.ContainerElementState$XsdSimpleState; local class incompatible: stream classdesc serialVersionUID = 42, local class serialVersionUID = -6470496719860432109
         at java.io.ObjectStreamClass.initNonProxy(Unknown Source)
         at java.io.ObjectInputStream.readNonProxyDesc(Unknown Source)
         at java.io.ObjectInputStream.readClassDesc(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at java.util.Hashtable.readObject(Unknown Source)
         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
         at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
         at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
         at java.lang.reflect.Method.invoke(Unknown Source)
         at java.io.ObjectStreamClass.invokeReadObject(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readArray(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.defaultReadFields(Unknown Source)
         at java.io.ObjectInputStream.readSerialData(Unknown Source)
         at java.io.ObjectInputStream.readOrdinaryObject(Unknown Source)
         at java.io.ObjectInputStream.readObject0(Unknown Source)
         at java.io.ObjectInputStream.readObject(Unknown Source)
         at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.readResult(P4InvocationHandler.java:303)
         at com.sap.engine.services.rmi_p4.reflect.P4InvocationHandler.invokeInternal(P4InvocationHandler.java:138)
         ... 52 more

    Hi,
    This is the problem with the XI system. You have to add some patches.
    For that check this link same problem solved here.
    PI 7.1 : Java exception creating new "Integration process"
    Thanks.

  • Error when trying multiple inbound interface determination for IDOC

    Hi !
    I have this scenario: File -> XI -> IDOC. 
    For each source file, I need to send multiple idoc packages, all to the same business system, but each package should be the result of different interface mappings.
    All mappings have same source and target message types...e.g. source: MT_MyFile, target: CREMAS04.
    To avoid creating a generic mapping program, we need to duplicate the current mapping program, make it handle the new case, and then add it as second interface mapping in Interface Determination, with same inbound interface, but different interface mapping, without conditions. All interface mapping should execute.
    We are receving this error:
      <SAP:Code area="IF_DETERMINATION">CX_ID_PLSRV</SAP:Code>
      <SAP:P1>Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:P1>
      <SAP:Stack>Error when determining the inbound interface: Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx Inbound interface was found more than once (for same sender and receiver) for outbound interface urn:xxxxx/xxxx:.MI_xx_xxxxxxxx_xxx_xx</SAP:Stack>
    Any clues?
    Regards,
    Matias.

    Hi Satish !
    Thanks.
    I need to send different IDOCs to SAME business system.
    In Interface determination I need this:
    Inbound Interface -
    Condition -
    Interface Mapping
    <b>IF_1</b>                     no condition                   <b>M_1</b>
    <b>IF_1</b>                     no condition                   <b>M_2</b>
    I need to send BOTH IDOC packages to same business system.
    But it keeps throwing the posted error.
    Regards,
    Matias.

  • ERROR occured at Interface Determination

    Hi all,
         Ths is  satya our senario is RFC to FILE but the problem is sender RFC is already configuerd to another interface.How can i assign that sender RFC to my interface.Hear i am using Sender service instead of sender system for testing purpose.
    But  when i am testng the test configuration an error is getting triggered in interface determination  in bound interface not found at test configuration tools.  Give me solution
    Thanks & Regards,
    satya.T

    Hi Satya,
    -->You are dealing with the Scenario RFC to FILE.
    -->So it is not mandatory to create the Message interface for Sender (in your case for RFC)because RFC it self is an interface.
    -->so create Message Interface for File.
    -->Coming to ID:
                    You are using the Business Service so,for that you need to maintain the Logical system and Details of the R/3 system.
                    Double click on your Business service and from Menu-->Click on Adapter Specific Identifiers and check the details if not maintain the details as said above.
    Thanks

  • Error with Enhanced Interface determination

    Hi Experts,
    In enhanced interface determination for message splitting w/o BPM, i have given the interface mapping.
    But while testing the configuration.......... i am getiing an error at Interface Determination & Mapping which is not showing any processing log.
    My mapping program works fine.
    could anyone tell me where the problem is....

    Hi,
    Can you post the error message that you are getting....it will help experts solve your problem accurately.
    Regards,
    Abhishek.

  • Interface Determination/BPM Error

    Hi,
    i have a idoc to file scenario,i am using a BPM.
    In ID when configuring the Interface determination, i am not able to select any interface mapping? is this b`se i am using a BPM and since the trnsformation step in the BPM already refers a interface mapping??
    Also i have 6 steps in my BPM :
    1.receive -idoc
    2.transformtaion
    3.send
    4.switch
    5.transformation
    6.send
    which are in a block and i am throwing an alert for this block in case of exception.
    when i try to execute the scenario, when i view PE in  moni, the start of the process itself shows error, but then my 3rd and 4th step gets execeuted succesfully,
    I am not sure why does the start of the process shows
    error status? is it b`se of my alert in the exception handler??

    Hi Harsha,
    Use the document below to get the exact error message from mapping trace.
    https://websmp104.sap-ag.de/~sapdownload/011000358700003141152005E/HowTo_Monitor_ccBPM.pdf
    Also test your mapping in IR test tab using actual payload from the message in BPM(you can download the message from the failed step to test).
    Regards
    Anand

  • Reg: Error at Interface Determination

    hi friends
    i have designed a scenario for MS SQL to R3 i.,e JDBC to RFC adapters. i have designed and activated but while monitoring communication channels it was showing error at sender as INTERFACE DETERMINATION have not been configured, but i have checked it , it was configured correctly .so, what might be the problem .
    with regards
    suman

    Hi,
    check in bottom of receiver determination screen under receiver business system wheather interface determination inbound message interface and interface mappings are visible.
    also try making some dummy changes and activate it again.
    also check in sxi_cache ur interface determination.
    thanks.

  • Error while specifying condition in  Interface Determination

    Hi all,
    I am facing a typical problem
    It's a proxy to file scenario with mutiple receivers.
    In the interface determination when we are trying to specify the condition, it gives the following error.
    "Message interface does not exist in any software components installed on this business system".
    Detailed solution would be highy helpful.
    regards.
    younus

    Hi Yonus,
    It seems that u have made changes in SWCV after doing the configuration.
    Try out thess:
    STEP1->In ID
    Go to menu :--> Enviorment->clear SLD cache
    Step2->In IR
    Go to menu :-->Tools->Transfer from SLD->Update application component and then step 1
    Step3->IN SLD
    Check the the SWCV u r using is associated with the Business system u are using. Check for the checkbox for SWCV in Business System.
    Sachin
    Message was edited by:
            Sachin Dhingra

Maybe you are looking for