PI 7.1 Sender Interface and Receiver Interface  gets interchanged

Hi All,
I m facing a strange problem in PI 7.1
For many of my scenarios, the Sender Interface, sender namespace and receiver Interface, receiver namespace  information gets interchanged and displayed incorrectly.
But sometimes its working fine.
When we analysed the Log messages, found that, after xml validation step, the sender and reciever interface gets interchanged.
Any idea why this happens?
How to rectify this error?

Aarthi,
Please check your message interfaces once again. Sender is outbound and Receiver is inbound.
Also please check your receiver determination.
Regards,
---Satish

Similar Messages

  • Code to retrive the sender and receiver interface names using custome adapter module

    Hello Team,
    I want to develop an custom adapter module which could retrieve the names of the sender and receiver interfaces of the scenario and for that i am trying to use com.sap.aii.af.service.administration.api.monitoring.ProcessContextFactory.ParamSet but i don't know whether this API will support or not and also i don't know how to develop the code using this API so please suggest me some code for it so that i could retrieve the names.
    Thanks you all in advance.
    Regards,
    Avinash.   

    Hi,
    Just ASMA setting will do the needful. Are you planning to rename your target file name. If yes then only you will require UDF.
    Update: Since your directory name will be taken from source file name then you have to use mapping for this, else it will not be possible.
    I don't know if creating a new module for this will help you solve the issue, but in that case rather creating adapter module, mapping will be easier.
    Regards,
    Sarvesh
    Edited by: Sarvesh Singh on Dec 7, 2009 3:04 PM

  • The difference between IEEE802.1Q Native VLAN sub-interface and Physical interface?

    Hello
    I think the following topologies are supported for Cisco Routers
    And the Physical interface also can be using as Native VLAN interface right? 
    Topology 1.
     R1 Gi0.1 ------ IEEE802.1Q Tunneling  L2SW ------ Gi0 R2
    R1 - configuration
    interface GigabitEthernet0.1
     encapsulation dot1Q 1 native
     ip address 10.0.0.1 255.255.255.0
    Topology 2.
    R1 Gi0 ------ IEEE802.1Q Tunneling L2SW ------ Gi0 R2
    interface GigabitEthernet0
    ip address 10.0.0.1 255.255.255.0
     And is it ok to use the physical interface and sub-interface with dynamic routing such as EIGRP or OSPF etc?
    R1 Gi 0 ---- Point to Multipoint EIGRP or OSPF ---- Gi0 R2 / R3 
          Gi 0.20--- Point to Point EIGRP or OSPF --- Gi0.10 R4  (same VLAN-ID) 
    R1 - configuration
    interface GigabitEthernet0
     ip address 10.0.0.1 255.255.255.0
    interface GigabitEthernet8.20
     encapsulation dot1Q 20
     ip address 20.0.0.1 255.255.255.0
    Any information is very appreciated. but if there is any CCO document please let me know.
    Thank you very much and regards,
    Masanobu Hiyoshi

    Hello,
    The diagram is helpful.
    If I am getting you correctly, you have three routers interconnected by a switch, and you want them to operate in a hub-and-spoke fashion even though the switch is capable of allowing direct communication between any of these routers.
    Your first scenario is concerned with all three routers being in the same VLAN, and by using neighbor commands, you force these routers to establish targeted EIGRP adjacencies R1-R2 and R1-R3, with R1 being the hub.
    Your second scenario is concerned with creating one VLAN per spoke, having subinterfaces for each spoke VLAN created on R1 as the router, and putting each spoke just in its own VLAN.
    Your scenarios are not really concerned with the concept of native VLAN or the way it is configured, to be honest. Whether you use a native VLAN in either of your scenarios, or whether you configure the native VLAN on a subinterface or on the physical interface makes no difference. There is simply no difference to using or not using a native VLAN in any of your scenarios, and there is no difference to the native VLAN configuration being placed on a physical interface or a subinterface. It's as plain as that. Both your scenarios will work.
    My personal opinion, though, is that forcing routers on a broadcast multi-access segment such as Ethernet to operate in a hub-and-spoke fashion is somewhat artificial. Why would you want to do this? Both scenarios have drawbacks: in the first scenario, you need to add a neighbor statement for each spoke to the hub, limiting the scalability. In the second scenario, you waste VLANs and IP subnets if there are many spokes. The primary question is, though: why would you want an Ethernet segment to operate as a hub-and-spoke network? Sure, these things are done but they are motivated by specific needs so I would like to know if you have any.
    Even if you needed your network to operate in a hub-and-spoke mode, there are more efficient means of achieving that: Cisco switches support so-called protected ports that are prevented from talking to each other. By configuring the switch ports to spokes as protected, you will prevent the spokes from seeing each other. You would not need, then, to configure static neighbors in EIGRP, or to waste VLANs for individual spokes. What you would need to do would be deactivating the split horizon on R1's interface, and using the ip next-hop-self eigrp command on R1 to tweak the next hop information to point to R1 so that the spokes do not attempt to route packets to each other directly but rather route them over R1.
    I do not believe I have seen any special CCO documents regarding the use of physical interfaces or subinterfaces for native VLAN or for your scenarios.
    Best regards,
    Peter

  • Difference between abstract interface and normal interface

    Hello Friends,
    What is the Difference between abstract interface and normal interface?....

    What is the Difference between abstract interface and
    normal interface?....The difference is that you didn't follow convention in the first case. All interfaces are implicitly abstract so you don't have to declare them as such.

  • Difference between PI/XI interface and ABAP interface

    Hello Experts,
    We are in the process of identifying interfaces for our current client. I am looking for some documentation or any specific information that will help me to differentiate between SAP PI interface and ABAP Interface. Basically I want to know what are the advantages of PI interface over ABAP interface. What is better? and why?
    Any information would be of great help. Thanks.

    PI (versus point to point ABAP) advantages are:
    1)     Centralized control over data security
    2)     More effective (centralized) interface failure monitoring and resolution
    3)     Elimination of redundant development and maintenance costs

  • Sender DEBIT and receiver DEBIT

    Dear all,
    I notice in settlement, there are 2 button : sender and receiver. Now, what confused me is why both also called sender debit and receiver debit?
    Why both also DEBIT?
    Please advise me.
    Thanks

    Dear All,
    I see mostly it is like that where sender debit and receiver debit. If you go into KO88 previous settlement, you will get this.
    I read in forum also it is explaining in debit.
    You assign the debit cost element groups to a settlement cost element.
    You settle by cost element - that is, the debit cost element is the settlement cost element.
    so i would like to know why the title is sender debit and receiver debit. why both debit.
    thanks

  • Regarding Sender query and receiver query

    Hi Masters
          I have one sender query and receiver query. Both queries contain G/L account.
    First I got sender query report, in this report I drill down one free charactteristics field to get correponding field sales document in receiver report.
    Is it mandatory which field i drill down in sender report should be in receiver report?
    Could you please help ?
    Thanks in Advance
    Raja.S

    I would rewrite the first one to:
    Select t.id_entity,t.id_trade_ref,p.am_stock
    from trade t,posting p
    where t.id_trade_ref = '5V973781B'
    and p.id_trade_ref = t.id_trade_ref
    This way, you really make the join between the table.
    I think the join is better because it uses less code. I do not think you will notice much performance win between one or the other, especially because it concerns only a few rows.

  • Send Task and Receive Task

    In our beta test, we came upon several issues, one of them is when we create a BPMN process that consists of the following simple flow: Start -> User Task 1 -> Send Task -> User Task 2 -> Receive Task -> User Task 3 -> End
    When we deploy and run the flow, it always stops at the Receive Task. But when we remove User Task 2 from the flow and redeploy and run, the process runs fine all the way to the end. I am wondering if this is a bug in BPM 11g where if you put an activity between Send Task and Receive Task, it does not work, but when you do not have a task between Send Task and Receive Task, it works fine. Can someone confirm this scenario please?
    Within the Send Task and Receive Task, we are invoking a BPEL process that has a simple asynchronous service. The Send Task invokes the BPEL process, and the Receive Task has the callback to the BPEL process.
    Makes sense?
    Thanks.

    What does the bpel process do? Does it work with a synchronous bpel process?
    I think you should submit an SR for this since it works when there is no activity between the send/receive.
    Heidi.

  • Could I configure local switching between sub-interface and global interface on ASR9k?

    Could I configure local switching between sub-interface and global interface on ASR9k?

    For 2 interfaces it is probably best to use an xconnect. It is faster and saves system resources (eg mac learning doesnt apply to xconnect).
    Config example:
    l2vpn
     xconnect group link
      p2p link
       interface Bundle-Ether100.4321
       interface Bundle-Ether500.4321
    EFP config:
    interface Bundle-Ether100.4321 l2transport
     encapsulation dot1q 4000
     rewrite ingress tag pop 1 symmetric
    interface Bundle-Ether500.4321 l2transport
     encapsulation dot1q 2000
     rewrite ingress tag pop 1 symmetric
    This example shows that you can link 2 EFP's with different vlan's together if you'd pop the tags.
    If the EFP's are of the same vlan, then popping the tag can be done but not a must. In general it is recommended to always pop vlan tags so there is a standard EFP design, but not for any technical reasons.
    When you use a bridge domain and using a BVI, you MUST pop the tags as the BVI has no notion of a vlan tag and wants to see "plain ethernet".
    regards
    xander

  • I need an application that will enable my ipad to receive calls, make calls , send sms and receive sms. line2 is not available in south africa

    i need an application that will enable my ipad to receive calls, make calls send sms and receive sms. line2 is not available in south africa

    Skype would be a possibility for phone calls, though I don't know if it's available in SA. Search the iTunes Store for "SMS" and you'll quickly see if there are any SMS apps you can try.
    Regards.

  • Display sender and receiver interfaces in CCMS

    Hello CCMS Specialists,
    I've a question regarding CCMS and SNMP TRAPS.
    In my case I'm sending the alerts to a Third Party application via SNMP TRAPS. In CCMS I don't get the information about a specific Interface and therefore I can't send it to a third party application.
    My question is: is it possibile or how to send the information from an interface (sender and receiver information) via CCMS to our Third Party application?
    For example, if there has been an Internal HTTP error. We don't get the details about the interface. Hoe could we display those information as well?
    Kind Regards,
    Kamran

    hi,
    And also check   spro -
    > financial accounting -
    > financial accounting global settings -
    > correspondence -
    > define correspondance  check the variant bcause all are standard variants so the one which we require need 2 make changes......... create our variant..
    if useful assign points....
    regards,
    santosh kumar

  • Interface and Receiver determination steps

    Dear Experts,
    I have list of queries which I am facing issue in ID. I am working on SOAP<->SAP-PI<->PROXY scenario.
    1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
    My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the  node Communication Component without party). I created this Business System ABAP from the entries of SLD.
    2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
    3. In the Receiver Determination, I can see in the "Configuration Overview" tab
    that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
    but it shows SI_SOAP_OB.
    4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
    and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
    5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
    I need urgent suggestions from experts , kindly help.
    Regards
    Alice Rebecca

    1. Created 2 Service Interface i.e. SI_SOAP_OB and SI_PROXY_IB in ESR.
    My question is that in the sender and receiver tab what should be the entries in Business System of SOAP and PROXY systems ( i.e. BS system created under the node Communication Component without party). I created this Business System ABAP from the entries of SLD.
    ANS -
    For SOAP, anything like Legacy_filer can be created & used.
    For PROXY, use the business system of R/3 system maintained in SLD.
    2. What is the sequence of steps in the ID i.e. Cc,ID,RD,SA,RA.
    ANS-
    Sender CC
    Sender Agreement
    Rec Determination
    Int Determination
    Rec CC
    Rec Agreement.
    Create the steps in COnfiguration Scenario directly.
    3. In the Receiver Determination, I can see in the "Configuration Overview" tab
    that the PROXY business system has red entries. I think that this system should show SI_PROXY_IB
    but it shows SI_SOAP_OB.
    4. When trying to create Interface Determination, I receive "JAVA.lang stack overflow error"
    and INTERNAL ERROR.I made sure that there is no inactivated objects under my user.
    ANS
    its cache error. Go for full cache refresh in IB>AdministrationData cahce--cache refresh.
    5. I am sure that the step till creating SI in ESR and sender agreement in ID is correct. Can I create proxy as well as WSDL with end point at this stage.
    ANS
    Nope. create the structure in ESR & generate proxy for the same in ECC system. that's it. No need of WSDL here.
    -santosh.

  • SOAP sender adapter and several interfaces

    I have several interfaces and want to connect them via SOAP sender adapter. How can I use 1 communication channel for this interfaces? or do i need to create communicaton channel for each interface?

    Hi,
    you can't use one communication channel, cause you got different WS.
    As you have a WS individual parameter (
    SOAP action) in the communication channel you need individual communication channels.
    A workaround would be to develop a >wrapper WebService< and deploy it on the backend. This Wrapper is able to call the different other WSs.In this case you need only one CC. Additionaly you need a parameter, which tells the wrapper-WS which individual WS he has to call.
    Regards Mario
    Message was edited by:
            Mario Müller

  • ENHANCED INTERFACE AND RECEIVER DETERMINATION

    1)what is the use of enhanced interface determination and enhanced receiver determination and in scenarios we will use them and in what conditions ,and what differentiates it from standard interface/reciever determination?

    1. <b>Standard receiver determination</b> to specify the receivers of the message (and optionally routing conditions) manually.You can specify receiver parties and receiver services. To specify the receiver in more detail, you have the following options:
    &#9679;     Select the receiver from the Integration Directory
    &#9679;     Specify a constant value for the receiver
    1.2You also have the option of specifying the conditions to be applied when forwarding a message to the receiver(s) in a receiver determination.
    Generally, a condition relates to the contents of a message; if a specified condition is fulfilled for a particular payload element (the corresponding element has a certain value, for example), then the message is forwarded to the specified receiver(s).
    <b>Enhanced receiver determination</b> to have a mapping program determine the receivers of the message dynamically at runtimeInstead of creating the receivers in the receiver determination manually, you assign a mapping to the receiver determination and this returns a list of receivers at runtime.
    A typical usage case is if you do not yet know the names of the receivers at configuration time. In this case, you can define a mapping program, for example, which reads a list of receivers from a table or from the payload of the message at runtime.
    2.<b>Standard Interface Determination</b> :You can specify to which inbound interface at the receiver the message is to be sent at runtime. You also have the option of specifying a mapping and (when multiple inbound interfaces are defined) a condition for each inbound interface.
    2.1 n an enhanced interface determination, you do not enter the inbound interfaces manually, but first select a multi-mapping. You get the inbound interfaces from the target interfaces of the multi-mapping. The inbound interfaces are determined at runtime during the mapping step.
    You typically use an enhanced interface determination if the source message has an element with occurrence 0 ... unbounded (for multiple items of a data record) and you want multiple messages (for the individual items) to be generated at runtime.
    for receiver determination try this link also
    http://help.sap.com/saphelp_nw70/helpdata/en/43/a5f2066340332de10000000a11466f/frameset.htm
    Regards,
    Mandeep Virk
    *Reward if Helpful*

  • (RFC vs files), where Sender SAP and receiver multiple system

    Publish and Subscribe using  BPM or Without BPM (RFC vs files), where Sender SAP and receivers multiple system,.
    This is my 1st BPM scenario in sandbox system
    For this scenario
    I Created 2 Data types
    2 MT,
    Service interface:
    Request interface Mode:Asynchronous
    Abstract Req interface,Mode:Asynchronous
    Response Interface,Mode:Asynchronous
    Abstract Respomse Interface ,Mode:Aysnchronous
    Synchronous Interface ,Mode:Synchronous
    2 Message mapping for Req and Resp
    1 Operation Mapping
    BPM design: Plz find the attatchement
    Can anyone please help me how many Interface determinations,receiver determinations ,sender agreements,receiver agreements need to create for this.......
    It will be good if anyone send the BPM design flow for this.........
    can we do this scenario without BPM?
    Regards
    A.Muni kumar
    Edited by: Muni 1234 on Jan 31, 2012 10:24 AM

    Hi
    Receiver is FTP only.....
    SAP side is RFC.........
    RFC sender will be initiating the scenario, and there is receiver is File, PI should go to file directory and take the file then send it back to RFC as response.
    Sender: RFC
    Receiver: File
    1. is this scenario with condition based routing.. so that each time outof many receiver systems it will trigger any specific system.
    if above is the case then you can achive this without BPM also..
    Yes...its condition based routing...
    I Used async in this scenario.....sender side configurations also done....
    But when when I am triggering BAPI from SE37 I am getting an error
    Exception SYSTEM_FAILURE
    Message ID: 00 Message number: 341
    Message:
    Runtime error CALL_FUNCTION_NOT_FOUND has occurred
    How to Solve this????
    I checked the RFC destination which i created in TCP/IP..a nd i mentioned the same in se37 RFC target system..
    Connection is Ok
    Or we need to create proxy for MI and report for this?
    Edited by: Muni 1234 on Feb 1, 2012 8:38 AM

Maybe you are looking for