Integration Scenario - Component not visible

Hi all,
I have two s/w components - say main component and sender component. Both belong to the same product version.
I have created an integration scenario in the main component and I want to create a swim lane corresponding to 'actions' that are already created in the sender component.
So, when I choose "Insert application component" in the scenario's swim lane area, and select the product version, it does NOT show the sender component !
Hence I am unable to include the actions of sender component in the integration scenario.
I have also checked from SLD that there are few more components (like the sender component) that are assigned to the same product version, but still not visible while creating a swim lane, as mentioned above.
I have tried the option of clearing SLD data cache, but it didn't help.
What can be done about this ?
Regards,

Hi,
did you make those software components dependet?
just like in my weblog?:
/people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Similar Messages

  • Doubt in Integration Scenario Configurator- Not able to assing sender chane

    Hi All,
    i have imported the integration scenario to the Directory.
    Assigned the relevant business services to both Sender and Receiver.
    I am able to assign a Receiver Communication Channel.
    But for sender system communication system , it shows 'Not Required'. i am not able to do anything. Sender is a Third Party System. I have created a sender JMS channel under it.
    could someone suggest what is to be done?

    If you configured your sender BS and CC correctly it must show..
    one try go and create a dummy sender agrement for the same interface check it is allowing there ,,if yes then u doing something wrong in configuaration scenarion.

  • Development Component not visible in dev config, but visible in DTR,CBS

    Hi,
    we have recently migrated our production track from netweaver 2004 to 2004s. In the Dev Config perspective I am unable to see a DC, but I am able to see the same from the DTR perspective. I am also able to see this DC in CBS.
    I am unable to create a project or work on this DC because of this problem.
    Has anyone else faced the same problem ? What can be done to make the DC visible in the Dev Config ?
    Thanks in advance for your help.
    Warm regards,
    Rashmi

    Hi Dao,
    Thanks again for your reply.
    Here are the findings :
    1)The DC is not available in both the active and inactive tabs in the Dev config perspetive.
    2) I have only NWDS 7.0 on my machine, but Admin has the older version 6.4 and it was not visible on their machine.
    3) I tried Re-Synching the archives, but still no luck, the DC is still invisible.
    4)The DC was last modified during the creation of the new track, the activities making changes to the DC before that are mostly UI changes, no deletes etc.. which could cause the DC to not be visible.
    5) It is a WD DC.
    6) The DC exists in Cons/Dev (both active/inactive) DTR workspaces as well as CBS build spaces (on both versions of the track)
    7)There are no pending activities for this DC in the old track.
    8)There were couple of broken DCs on the new track but this is mainly because of compile time errors due to use of deprecated methods.
    While checking for all these items I noticed that the .dcref file for the DC is missing in the DTR for both active and inactive, could this mean anything ? Is this the reason for the DC not being visible in the Dev Config perspective ?
    Is there any way to recover the DC ?
    Thanks in advance for your help.
    Warm regards,
    Rashmi

  • Integration Repository Objects not visible after Succesfully Import

    Hello everybody,
    I'm importing design objects via File System, the system gives a succesful message after import, but the objects are not imported, I've checked Cache and everything is green, anyone have any suggestions on why could this be happening, we have PI 7.0 SP 17, thanks in advance for your answers.
    Regards,
    Julio Cesar

    Hello guys, thanks for your answers, actually is the correct .tpz file, and we are exporting a hole namespace, the software component version already exists in the target system, the objects are active in the source system, actually there is no change list with inactive objects in any of the systems the source or the target.
    Regards,
    Julio

  • Development Component not visible in the Consolidation Compartment in CBS

    Hi Experts,
    We have created a new development component on the track for which we
    have created an DTR activity. After we checked in, activated & released
    the activity successfully, we went to the consolidation tab in CMS and
    imported the activity. We could successfully imported the activity into
    consolidation system and got the message import finished. But when I checked
    in the Consolidation compartment, I could not found out my newly
    created Development component. I feel that the activities are not going there.
    I also tried restarting the NWDI server but still no luck.
    Kindly assist as without solving this issue we cannot assemble our
    components and cannot move them to Quality environment.
    Also, kindly assist how can we transport the entire SCA (where we have done the custom development) from development
    to Consolidation for the same state?
    Currently, we have lesser number of DCs in the SCA of my cons environment than my dev environment, so how can I exactly have the same state of custom developed SCA in my cons environment?
    Is there any provision of system restore so that we can overcome the above issue or any other means by which we can move the entire SCA from my dev environment to cons environment.
    Please suggest as this is affecting our go live activities.
    Thanks & Regards,
    Anurag

    Hi,
    when you have imported into cons and it said finished succesfully, then clicking on the button "Details..." can you confirm that all the 3 phases were succesful (dtr import, cbs make and deployment) ?
    Do you have any pending activations? You can check it in the CBS webui -- page "Activities".
    Can you see any requests in the TCS deployer as described by Pramod ? (you need to look for numbers in square brackets [ ]. If there are any it means that those requests are still being deployed. If this is the case and the requests are not disappearing from the TCS Deployer, then doublecheck if the RTS settings for CONS are ok. Here a hint for that: http://wiki.sdn.sap.com/wiki/display/TechTSG/%28NWDI%29%28CMS%29Q0002).
    Eventually if all this is fine, can you please trigger an Initialize Compartment (you do this in CBS webui -- select your CONS compartment).
    I hope this helps.
    Thanks and Regards,
    Ervin

  • Z logical component not visible in project administration

    Hi All,
    I have created new product in SMSY named ZLegacy and assigned logical component.
    But when I try to assign this logical component to my project, I dont see the Zproduct. Is there any table which I need to change manually ?
    BR,
    Shyam

    This forum is for the Flex SDK. The Flash Builder (formerly Flex Builder) IDE has its own dedicated forum. Questions specific to the IDE should be directed there.

  • Integration Scenario Configurator

    Hello!
    I want to generate the receiver determination for an integration process on XI 3.0 SP10 with the Integration Scenario Configurator.
    I have created an Integration Scenario in the Integration Repository, there are no errors when checking with F7.
    If I open it in the Integration Directory and go to Integration Scenario Configurator -> Check Configurability I get the following error message:
    "Component View /Role <my Integration Process>: Only connections with interfaces that belong to the integration process interface are permitted"
    What does the error message mean? What do I need to change to eliminate this error message?
    The connections point to interfaces I have defined in the same software component as the integration scenario and process. For the integration process I have created abstract interfaces.
    Regards, Tanja

    Hi Simon!
    I was able to solve this problem some weeks ago but thanks for your hint anyway.
    As you have mentioned the problem was that in the Integration Repository the integration scenario was not consistent with the used integration process as it  contained a wrong interface.
    After I have corrected the integration process in the Integration Repository and updated the changes in the Integration Directory the generation with the Integration Scenario Configurator worked without any problems and the status of the process changed to 0 in SXI_CACHE.
    Regards, Tanja

  • Confusion with PI 7.1 with integration scenario

    Hi, expert,
    I read a lot of documents before I have physically logged on to PI 7.1, I thought I had a very good idea about the new version. However when I am physically in PI 7.1, I found I get a little confused.
    I know ES is a big thing in 7.1, but I will be working on integration (integration scenario), I thought this part is not changed from 7.0 to 7.1. Basically in 7.0, you defined message type and message interface, message mapping and interface mapping, then you go to ID to configure the integration scenario. However in 7.1, you do not have message interface anymore, instead, we have service interface under which you define operations, which is fine from ES perspective. But if I am only interested in integration, what I need is like PI 7.0: outbound interface, mapping, inbound interface, NOT the operation. Now how can I define 7.0 message interface in PI 7.1? (I know operation mapping is 7.0 interface mapping).
    Can I make following understanding?
    1) Operation in 7.1 is like messag interface in 7.0
    2) Service Interface is a tool to group multiple related operations under one roof.
    3) To define integration scenario, I do NOT need the modeling. Modeling is only relevant to model ES, NOT for integration scenario.
    So if I am only interested in integration scenario, what is changed from PI 7.0 to PI 7.1?
    Thanks for advice
    Jayson

    > Can I make following understanding?
    > 1) Operation in 7.1 is like messag interface in 7.0
    Service Interface with one operation whose name is same as the service interface and Xi 3.0 compatible type is same as 7.0 Message Interface
    > 2) Service Interface is a tool to group multiple related operations under one roof.
    Yes.
    > 3) To define integration scenario, I do NOT need the modeling. Modeling is only relevant to model ES, NOT for integration scenario.
    Yes.
    >
    > So if I am only interested in integration scenario, what is changed from PI 7.0 to PI 7.1?
    I did not work much on this area but, as long as you are replacing the interface mapping with operation mapping things must be pretty much same here. For your information, Integration scenario is not a compulsion unless u want to represent the scneario graphically and create the ID objects automatically.
    You can create the ID objects manually whitout creating an integration scenario on ESR.
    VJ

  • Integration scenario and configuration scenario - is it madatory

    Hi,
    Integration Scenarios are not mandatory, the reason for creating them is given in the blog you mentioned:
    The advantages of defining integration scenarios in the Integration Builder (design tool) are as follows:
    · The integration scenario provides you with an overview of the process and the process flow
    · The integration scenario club together all objects like SWVC,Interface objects, mapping objects,integration processes.You can access all of these objects from the integration scenario.
    · The integration scenario gives you the design time information which is required for its configuration.
    The configurtation items are getting created.
    Regards
    Patrick

    Hi Priya,
       There are two things here.
    1) Create the Integration Scenario in the IR.
    2) Use the wizard to configure the integration scenario in ID.
    The Integration scenario created in the IR acts as a template to create the configuration objects in ID.
    The wizard will create the actual configuration objects only (not just documentation).
    But creating integration scenarios is not mandatory.
    YOu can as well create all the configuration objects manually.
    Generally, you will go for Integration scenarios if you are building a general purpose product (Product based ).
    If it is a project that you are building for a particular customer, you can chose to create the configuration objects using the configuration scenario approach.
    Regards,
    Ravi kanth talagana

  • Not able to add a  business component in Integration Scenario

    Hi Experts,
    I have Imported an Integration Scenario from ESR into ID. I am trying to assign a business component but its showing only the business systems in search result and not any business component. What would be the reason?
    Regards,
    Pranil Shinde

    Hi,
    I have created integration scenario in ESR using two actions for IB and OB interface. Then I have imoprted IS into ID.
    Now in model configurator in ID,  while assigning the business component to Inbound interface action, its not showing me the business compnent created in search result.
    Regards,
    Pranil
    Edited by: pranil shinde on Feb 9, 2012 5:41 PM

  • Error in Integration Scenario: No software Component version exists

    Hi Experts,
    We have external product and software component like Product "Project Management" we have imported the CIM content for it
    Now when we create an Application Component for the same in Integration Scenario in ESR (PI7.1)
    while trying to do right click --> Edit Action it gives Error
    "" No imported software component version exists for product"
    Also note that it allows us to Add new Action there
    that is we can right click --> Add action
    Kindly help with your suggestions to resolve this << Moderator message - Everyone's problem is important >>.
    Regards,
    Jagadish
    Edited by: Rob Burbank on Nov 10, 2010 3:56 PM

    Hi Experts,
    Tried the steps given in SAP Note: 768148
    Still it is not resolved.
    I appraiciate if any one suggest some more options to resolve this.
    Regards,
    Jagadish

  • Missing Component View on Integration Scenario

    Hi All,
    I'm having a problem when doing the XI 3.0 Demo Examples.
    The CheckFlightSeatAvailability scenario in my system doesn't have ABAP_Proxy_2_Web_Service component view.
    The Config Guide said that this demo variant is available as of XI SPS 12, while my XI SPS is 14, so I supposed there's no problem.
    But when I checked the Software Component Version SAP BASIS 6.40 in the Integration Repository, the Available Support Packages field's value is 9.
    My questions are :
    1. Does it means that I'm still using SPS 9 for configuring the scenario ? If that so, how can I update it to SPS 14 ?
    2. If that's not the problem, what should I do so that the ABAP_Proxy_2_Web_Service appear in the CheckFlightSeatAvailability scenario ?
    Kindly need your advices in this matter.
    Regards,
    Andy

    Hi Andy,
    you are on patch9 for basis component.
    In patch stack guide it is described how to upgrade this component.
    Import the appropriate content for the SAP XI Support Package release from the archive SAPBASIS<SP>_<PL>.ZIP (XI Content SAP_BASIS 6.40). Proceed as follows:
    1. Unpack the archive using a ZIP tool of your choice.
    2. Copy the export file (with file extension tpz) into the import directory <INSTDIR>/ <SAPSID>/SYS/global/xi/repository_server/import.
    3. Start the Integration Builder for the design time.
    4. Import the XI content by choosing Tools &#8594; Import design objects...
    For more information, see SAP Note 705541.
    This is always an important step, since the component not only contains scenario's but also Adapter MetaData.
    So if this level is not on 14 (and the rest is) you will not be able to make use of SP14 Adapter features or even run into all kind of errors.
    Regards,
    Theo

  • Integration Scenarios vs Process Component Modelling

    Hi Experts,
    Just wanted to know:
    1) How theoritically and technically, is 7.0's Integration Scenarios different from 7.1's Process modelling?
    2) For what kind of cases we go for Integartion Scenarios and for what kind of cases we model a PCM?
    3) What is "Deployment Unit" in PCM?
    Thanks
    Shailesh

    Hi,
    >>>1) How theoritically and technically, is 7.0's Integration Scenarios different from 7.1's Process modelling?
    Process Component modeling is ment for modeling SOA, where you create a Business Object, Service Interfaces, etc and this help to understand the business semantics of enterprise services in the business process platform. And you will not create Receiver Determination, Interfaces Determination out if that. Where as Integration Scenario is meant only for integration where you define Sender system, receiver system etc...
    >>>2) For what kind of cases we go for Integartion Scenarios and for what kind of cases we model a PCM?For normal integration between 2 or more systems you use Integration Scenario. But Process Component Model is for Service Provisioning.
    >>>3) What is "Deployment Unit" in PCM?
    All the related/dependent Process Components are tied together in one unti and this is called Deployment unit. It also describes the logical boundary of the  Process Component. Apart from this deployment units are the only installable units and this shows what types of interactions are needed between process components.
    Thanks,
    Prakash

  • The userexit is not working in integration scenario- inb. delivery creation

    Hi Experts please help,
    We know that vl31n is for inbound delivery creation.
    in one of the userexits of vl31n, I did code ( shifting the batch to vendor batch )...
    So,the user enters batch number under batch field and
    fill all other required information and saves to create inbound delivery.
    Whilw inbound delivery creation my coding in user exit gets executed and shifts the batch number to Vendor batch field.
    This we observed when we check in vl32n or vl33n, the batch entered shifted to Vendor batch field() batch field is space.
    This is working fine with vl31n inb. delivery creation.
    But in integration testing it failed.
    In Integration, what is happening the other system called "ICH" is creating ASN (shipping note) with the batch number, which inturn created the inbound delivery in R/3 via XI as shown like below.
    Integration scenario :
    ICH System (ASN)   --> XI -->  R/3 System (Inb. delivery creation)
    So when "ICH" triggers ASN to R/3 the inbound delivery creation is happening but the batch number is not shifting to vendor batch field.
    when we open the inbound delivery in vl32n, the batch number is under batch field only...it should be under vendor batch field.
    My understanding is my user exit coding of vl31n not getting executed in the integration process.
    Kindly help me what can I do to shift the batch sending from ICH to shift to vendor batch field.
    Please let me know if I could not explain the scenario.
    THANKS IN advance.
    YOUR HELP WILL BE GREATLY APPRECIATED.

    the ASN from ICH, it uses a standard idoc function module IDOC_INPUT_DESADV1 and there is one user exit EXIT_SAPLV55K_012 which calls ZXTRKU07
    need to code there.
    solved by meetings with some other experts.
    THANKS.

  • Multiple component view in integration scenario

    Hi
      I have <b>multiple component views</b> defined in my integration scenario.
      When i try to configure these component view in Integration directory in integration scenarion configurator, if I select the component view i want to apply then the systems give a message " All configuration settings made in the current component view will be lost".
      This means that if i have configured the first component view and then try to configure the second component view then setting of first view get lost.
      i want to have all the configure all the component views in the integration scenario.
    Please provide some pointers for the issue.
    Thanks in advance
    Regards,
    Amit Deshpande

    Amit,
    When you have multiple component views in the Integration scenario, you would ideally want to create separate configuration scenarios for each component view.
    So for eg. if you have four component views, 4 different configuration scenarios can be created using the integration scenario configurator. The only thing is that you would have to repeat the integration scenario configurator steps[Tools->Transfer Integration Scenario from Integration Repository] 4 times, once for each component view. If you notice, you can change the name of the configuration scenario each time you start afresh.
    The message is a warning that if you go back during the integration scenario configuration process[the first step is the selection of the component view for which you want the configuration scenario] and change the component view then all the changes made thus far would be lost.
    For e.g if you are in step 3[Assign Services, I think] and then go back and change the component view, all the changes made for the original component view selected would be lost.
    Hope this helps.
    -Anand

Maybe you are looking for