on 03-09-2007 6:22 PM
In the config directory, creating a Receiver Determination asks for the sender system, interface, and namespace, right? If using a business system/service, then once you pull up the list for the interface and namespace, only outbound interfaces are displayed (or IDOCs). Similarly, when creating the receiver agreement, only inbound interfaces are listed. When creating agreements around integration processes, only abstract interfaces are listed.
Now, why is it that you can ignore the lists and use abstract interfaces for system senders and receivers if no mapping is applied going into or coming out of integration processes? That is, the sender agreement uses the same abstract interfaces as the BPM. Or the abstract interface coming out of the BPM is used in the sender agreement. Even though this is allowed, is it discouraged? Is this something that might not work in the future? Working with NW04 (not s).
TIA.
Tim
Hi,
In simpler words
Sender Agreement is used to bind the channel with message interface. So it has direction ie inbound our outbound.
But Abstract Interface does not has direction. It is used only in BPM..
Rgds,
moorthy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is ur post is regrading y the abs interface are also listed in the sender agreement selection?....
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
83 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.