Use of Enhanced option in Interface Determination

Hello All,
I am stuck up with a problem, where I need your expertised help.
The scenario is IDOC --> Files
what I mean by files is: I have one sender (ecc system) and two receivers (ftp destinations using file adapters). I created multi mappings (1:n); based on the content of the IDOC field, either Message Type1 or MessageType2 are populated in the message mapping. Each MessageType belongs to separate receivers. Message mapping working good when tested in the test tab.
Now, coming to configuration side; I have created one interfaced determination with enhanced mode and gave the Message interface information, which populated both Message Interfaces below automatically. Interface is failing with "No receiver Agreement for the sender receiver combinatio". I checked all the cache refresh and also the receiver agreements. I have both receiver agreeements defined, one of each receiver. I guess something to do with Interface Determination definition.
Questions:
1) In the interface determination, what receiver system we need to specify. I have two receivers here; I don't see space to specify both when selected enhanced option.
2) How do I specify receiver determination for this?
Thanks for your help..RP

I just looked into the error message deeply. This is why it is errroring out. any idea is a great help.
In the Interface determination, I have * for the receiver.
In the Receiver determination, I have both receivers defined.
In the bottom section of the Receiver Determination, It is showing both message interfaces for each receiver like below
Receiver1
   MessageInterface1 -- Interface Mapping -- Receiver Agreement
   MessageInterface2 -- Interface Mapping -- Does Not Exist
Receiver2
   MessageInterface1 -- Interface Mapping -- Does Not Exist
   MessageInterface2 -- Interface Mapping -- Receiver Agreement
In the Moni, I see two child messages as they are supposed to, one for each receiver and and both failed.
Both messages failed with the similar message statinng that 'No receiver agreement found for sender xx and receiver combination'. This error is for the other message interface which does not beloing to that receiver (MI information also shown in the message).
Thanks for your help..

Similar Messages

Using the RB_Split feature in Interface Determination

hi,
I have a 1:N file to IDOC Scenario where I need to do multi-mapping using RB_Split in Interface Determination instead of using CCBPM.
I had done the repository part, but during interface determination, after I select the RB_SPLIT feature, I get "no objects found" when I try to select FIELD_LABEL_SPLTMAP.
Please help!
regards,
Prashanth

Hi Prashanth,
Pls check this from SAP help & verify..
<i>Activities
To execute a mapping-based message split, perform the following steps:
Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
       1.      Integration Directory: Define the interface determination.
Note the following:
     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
     The interface determination type must be set to Enhanced.
     Select the multi-mapping you defined previously from the Integration Repository.</i>
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
Thanks,
Renjith

Enhanced and conditional interface determination, :

Experts ,
can you giv me some link/ examples of Conditional interface determination and Enhanced Interface determination.
Pls dont send me teh below link!
http://help.sap.com/saphelp_nw04s/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
many Thanks
Arnab Mondal

HI,
U can refer this threads of same discussion:
Re: Condition In Receiver Determination Not Working
purpose of Enhanced Receiver Determination
Then refer this blogs:
Illustration of Enhanced Receiver Determination - SP16
SAP NetWeaver Process Integration: Enhanced Receiver Determination for Synchronous Scenarios

Extended receiver and enhanced interface determination

Hi,
Can somebody list me the business cases when we use the extended receiver and enhanced interface determination.In which scenarios we have to use them?
Where we can use these features and whom they can replace?
Regards,
Anoop

Hi Anoop
have alook at thses URl's also
http://help.sap.com/saphelp_nw04/helpdata/en/43/01322a7af25285e10000000a1553f7/frameset.htm
:Dynamic file and variable substitution
Similarly Extended Receiver determination is used to determine the receiver at runtime.
Refer my reply:Re: Condition In Receiver Determination Not Working
enhancement in ID
Enhanced Receiver Determination:
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead 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.
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Enhanced (Mapping-Based) Interface Determination
In an enhanced interface determination you do not enter the inbound interfaces manually, but instead 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.
http://help.sap.com/saphelp_nw04/helpdata/en/42/ed364cf8593eebe10000000a1553f7/frameset.htm
<b>enhanced interface determination</b>
/people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
List of receivers can be dyamically determined and assigned at runtime using enhanced receiver determination .
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Thanks
Pls reward if useful

Extended Receiver & Extended Interface Determination

Hi Experts,
Can any tell me what is Extended Receiver & Extended Interface Determination.
And the Difference between Standard Receiver & Standard Interface Determination.
were to use Extended Receiver & Extended Interface Determination.
Thanks in advance
Shakif

Hi,
Standard Receiver Determination Features
Specifying Receivers
You can specify receiver parties and receiver services. To specify the receiver in more detail, you have the following options:
●     Select the receiver from the Integration Directory
●     Specify a constant value for the receiver
●     Determine the receiver dynamically from the message content
To enter the necessary details, use the following:
●     The party editor for specifying the receiver party
●     The service editor for specifying the receiver service
To call the relevant editor, in the Display/Edit Receiver Determination editor in the Configured Receivers frame, call the Input Help ( ) in either the Party or Service column.
Defining Conditions
You 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).
●     If you want to specify a new condition for forwarding the message to a receiver, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert New Condition () and call the condition editor by using the input help ().
●     If you want to specify a new condition for forwarding the message to multiple receivers, in the table in the Display/Edit Receiver Determination editor in the Configured Receivers frame, choose Insert Line After Selection ( ) and call the condition editor by using the input help ().
In the condition editor, you can select an element from the message payload and specify a value with which the value of this element is to be compared at runtime.
Enhanced Receiver Determination
Use
You use an enhanced receiver determination to have a mapping program determine the receivers of the message dynamically at runtime. Instead 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.
You can of course formulate conditions in a standard receiver determination that relate to the content of the message. However, you have to specify the names of the receivers (to which the message is sent under the formulated condition) explicitly in the receiver determination. If you create an enhanced receiver determination, you do not have to specify receiver names at this stage.
Integration
During the definition of the interface mapping, you assign the abstract message interface ReceiverDetermination as the target interface. The message interface ReceiverDetermination is in the Integration Repository in the software component SAP BASIS (namespace http://sap.com/xi/XI/System).
The message interface uses the message type Receivers and the data type Receivers. The data type Receivers describes a list of receivers and has the following structure:
The following instance of the data type Receivers contains two receivers. The first receiver comprises a party and service and is identified by a DUNS number; the second receiver comprises a service without a party.
<Receivers>
<Receiver>
    <Party agency=016 scheme=DUNS>123456789</Party>
    <Service>MyService</Service>
</Receiver>
<Receiver>
    <Party agency=http://sap.com/xi/XI scheme=XIParty></Party>
    <Service>ABC_200</Service>
</Receiver>
</Receivers>
You can specify party and service for each receiver.
Activities
       1.      Integration Repository: Define the interface mapping. Assign the message interface ReceiverDetermination as the target interface (see above).
       2.      Integration Repository: Define the message mapping or mapping program that is to determine the receivers at runtime. Assign the message mapping or mapping program to the interface mapping.
       3.      Integration Directory: Define an (enhanced) receiver determination.
○     Enter the outbound interface of the interface mapping from step 1 in the key of the receiver determination as the outbound interface.
○     Assign the interface mapping created in step 1 to the receiver determination.
Standard Interface Determination
Use
You can specify to which inbound interfaces 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.
Note the following fundamental cases when assigning multiple inbound interfaces:
Multiple Different Inbound Interfaces
Imagine you enter the following interface assignment.
Inbound Interface
Condition
Interface Mapping
IF_1
M_1
IF_2
M_2
After the interface determination is evaluated, this results in two messages with the same payload at runtime. A different mapping (either M1 or M_2) is executed for both messages and then they are forwarded to the two interfaces (either IF_1 or IF_2) at the receiver.
Multiple Identical Inbound Interfaces with Conditions
Imagine you enter the following interface assignment.
Inbound Interface
Condition
Interface Mapping
IF_1
B_1
M_1
IF_1
B_2
M_2
In this case, the conditions are evaluated during the interface determination step. If condition B_1 is true, then mapping M_1 is executed; if condition B_2 is true, then mapping M_2 is executed. The message is forwarded to the same inbound interface at the receiver in both cases. Unlike in the case described above, this does not result in multiple messages with the same payload because only one condition can ever be true at runtime.
Features
You enter the assignment between the outbound interface and the inbound interface(s) in a table. Each table line represents exactly one assignment between the outbound interface and an inbound interface. To insert or delete lines, choose Insert One Line After Selection () or Delete Selected Line ().
Enhanced (Mapping-Based) Interface Determination
Use
In an enhanced interface determination you do not enter the inbound interfaces manually, but instead 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 example, you want to split an overall booking for a trip comprising connecting flights into individual booking orders (for each leg of the trip).
You cannot realize this usage case with a standard interface determination (without using an integration process). A standard interface determination does allow you to specify multiple (N) inbound interfaces (with different mapping). In this case, N messages with the same payload and different receiver interfaces are generated from the source message before the mapping step; these are then transformed differently depending on the receiver interface. Therefore it is conceivable to write the mappings in such a way that the first mapping from the source message generates a message that only contains the first item, the second mapping generates a messages that only contains the second item, and so on. However, this no longer works if the number of items can vary with each new source message.
You can use an enhanced interface determination to configure a mapping-based message split for this usage case. You assign the interface determination a multi-mapping that has a target interface with an element with occurrence 0...unbounded. At runtime, the individual messages (for the individual items) are calculated in the mapping step. First, the individual messages are grouped into a bulk message. Then, the bulk message is transferred to the Adapter Engine. The Adapter Engine then splits the bulk message up into the individual messages (see figure).
Procedure at Runtime During Message Split
Note that both the bulk message and all individual messages each have a message header with a receiver interface (see figure).
Receiver Interfaces of Bulk Messages and Individual Messages
The header of the individual messages contains the relevant receiver interface. It is based on the definition of the multi-mapping. Note that the receiver interfaces of the individual messages may be different. The receiver interface of the bulk message is always InterfaceCollection (namespace http://sap.com/xi/XI/System).
If the message split only results in one message, the original message structure remains the same. In this case, a bulk message containing just one individual message is not created.
You can also assign a multi-mapping with multiple different target interfaces to an enhanced interface determination (1:n transformation). Each target interface can contain elements with occurrence 0 ... unbounded.
Messages cannot be sent by using different Adapter Engines in a mapping-based message split. This affects configuration thus: All receiver agreements that have a receiver interface from the mapping entered in the key must only be assigned communication channels with the following adapter types:
-          RFC Adapter
-          SAP Business Connector Adapter
-          File/FTP Adapter
-          JDBC Adapter
-          JMS Adapter
-          SOAP adapter
-          Marketplace adapter
-          Mail Adapter
-          RNIF adapter
-          CIDX Adapter
The adapters also have to all run on the same Adapter Engine.
Adapters developed by partners also support a mapping-based message split if they run on the same Adapter Engine.
Attachments from the original message are not appended to the messages resulting from the message split.
Activities
To execute a mapping-based message split, perform the following steps:
       1.      Integration Repository: Define the multi-mapping (see Developing Multi-Mappings for Message Splits).
       2.      Integration Directory: Define the interface determination.
Note the following:
○     The outbound interface of the multi-mapping must be entered as the sender interface in the key of the interface determination.
○     The interface determination type must be set to Enhanced.
○     Select the multi-mapping you defined previously from the Integration Repository.
To do so, call input help ().
The target interfaces of the interface mapping are displayed in the Inbound Interfaces frame.
The number of messages (for an inbound interface) created in the mapping step is displayed in the Occurrence column.
Regards,
Phani
Reward points if Helpful

Interface Determination doubt

Hi guys,
I have a file with the following example source:
80
80
56
25
32
80
56
The target is an R/3 and the interface is IDoc. All lines with value 80 should map to RPLMAS02 and the others values to ARTMAS 05. So, is two different mappings based on content field for the same target service R/3.
I already have two different mappings for each IDoc type, and Im using the function createIf to exclude the lines that I dont want to add in each IDoc. But, I cant do it using XPath conditions in the Interface Determination, because both mappings are always performed
Which is the best way to achieve this issue?
Thanks in advance,
Ricardo.

Hi folks,
Thanks a lot for your prompt answers.
Aamir: Take my source code as an example, I have several lines with different key field values. Based on these key field values I want to route both contents to different mappings. The lines with 80 value to RPLMAS mapping and the rest (different from 80) to ARTMAS mapping. But, from my understanding, at Interface Determination level, one message is considered and the XPath conditions only checks where 80 value exists or not. As I've a message with both values 80 and !=80), both mappings are performed and the last one is generated empty with error.
Saravana: I didn't understood where this "workaround" solve my issue above?
Resuming: I want to route lines for two different mappings and not an entire message. I mean, I want to put lines 80 in one mapping and the rest in another every thing at the same execution time.
Thanks in advance,
Ricardo.

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.

Enhanced Interface Determination in PI 7.1

Hi All,
My scenerio will work as follows
The changes in the process order will triggered by the client system .I will get the already converted XML file.I have used the file adapter in the sender side to pick the file.At the receiver side I am using the 3 custom BAPIs.I have used 3 message interface instead of multi-mapping as the inbound interfaces.
The Logic is like that:
If the Process order status is = 1 then call BAPI 1,if it 2 then call BAPI 2 & call BAPI 3.
Please tell me the following
1.Is there Enhanced Interface Detrmination option available in PI 7.1?If so then can I mention or call 2 BAPIs in one condition over there?Do I need to write ABAP condition?
2.Is Enhanced interface Determination possible when I have used 3 inbound interfaces instead of multi-mapping?
3.From my point of view I need the following in my scenerio
- 3 message mappings(Graphical Mappings),
- 3 interface mappings,
- 1 sender agreement,
- 1 receiver determination,
-1 interface determination(with 2 conditions in it),
-3 receiver agreements.
Am I right?
4.How many sender and receiver agreements do I need?
5.Do I need to go for Enhanced receiver determination?
Thanks in advance.

the same status node in the source file on which I will impose check will call the selective inbound interface based on the
status node.Is it?If so,then do I need to mention anything other than the check condition in XPATH e.g.do I need to mention any
mapping program or inbound interface (though I dont thing so but I am still confused) ?
Yes, apart from specifying the condition in the Condition Editor you also should mention the corresponding Inbound Service Interface and Interface Mapping (if any).
Condition will only cause the execution of that particular line and wont automatically call the mapping/ interface (unless these are specified in the Interface Determination).
Is XPATH the alternative option in condition editor which can be skipped though I would surely like to go through it as
much as possible?
XPATH is the easiest option to specify a condition....other option includes the use of a Context Object.
So as of now think that you cannot skip XPATH (for this particular requirement).
Once you become an expert in using a XPATH (which you can in a days period) you can try out for Context Objects.
Regarding Test Case:
There is no standard template for this.....i would suggest check with peers in your company.....many a times companies have their own templates for test cases alongwith the possible cases....then referring to those test cases you can build the cases for your scenario. Avoid a direct copy of the test cases.....many wont be relevant for your case.
Regards,
Abhishek.

Enhanced Interface Determination - does not work!

Hi guys,
well i have a scenario where i have done a multi mapping where MT_TYPSCH is generated for each new value which occurs in one special source field.
<NO>1</NO>
<NO>2</NO>
<NO>3</NO>
..so three MT will be generated.
Now i would like these messages devided to different Business Services where each one has on FTP-CC to write a file with a certain filename, e.g. File1.txt, File2.txt, File3.txt.
Therefore i thought i use different receivers in Receiver Determination with using Conditions and pointing to a value in field with XPATH. So depending on field <NO> the message should be routed to the given receiver targets.
I surely use the enhanced Interface Determination because i use multi mapping.
But when i run test, i receive 3 files with different names but same content. For me the receiver determination is not working that good.
Can someone help me on this?!
source:
<ZBC0>
<IDOC BEGIN="">
<EDI_DC40 SEGMENT="">
<ZBC0 SEGMENT=""> 0...9999
<NO>1</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</ZBC0>
<ZBC0 SEGMENT="1">
<NO>2</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</IDOC>
</ZBC0>
target:
<?xml version="1.0" encoding="UTF-8"?>
<MT_TYPSCH> 1..1
<TYPSCHRecordSet> 1..1
<TYPSCHDetailsStruc> 1..unbounded
<FELD1/> {represents content of <No>}
<FELD2/>
<FELD3/>
</TYPSCHDetailsStruc>
</TYPSCHRecordSet>
</MT_TYPSCH>

Hi Mario,
ok here is my requirement.
We get ONE IDoc in which several items are listed. These have one field <NO> which can have the values 1,2 and 3. Depending on this value the items should be collected and written to different files on FTP.
My approach is that i divide all the items in mapping in different Message Types. This MT should be routet to different business services which has one CC to write on FTP.
To get the items with e.g. <NO>1</NO> i took condition in reciever determination using xpath. ((/ZBC21/IDOC/ZBC21/NO = 1).
So depending on the mapping everything runs - in my point of view but the different messages are not routed to the different services to write them to different files.
Source
<ZBC0>
<IDOC BEGIN="">
<EDI_DC40 SEGMENT="">
<ZBC0 SEGMENT=""> 0...9999
<NO>1</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</ZBC0>
<ZBC0 SEGMENT="1">
<NO>2</NO>
<TYPE>1B20-6</TYPE>
<SPEC>152J</SPEC>
</IDOC>
</ZBC0>
target:
<?xml version="1.0" encoding="UTF-8"?>
<MT_TYPSCH> 1..1
<TYPSCHRecordSet> 1..1
<TYPSCHDetailsStruc> 1..unbounded
<FELD1/> {represents content of <NO>}
<FELD2/>
<FELD3/>
</TYPSCHDetailsStruc>
</TYPSCHRecordSet>
</MT_TYPSCH>
The output should be files with content of items depending on field <NO>.
file1.txt (all items with <NO>1</NO>)
file2.txt
file3.txt
I hope i made it clearer!
br

Enhanced Interface Determination?

Hi All,
I have a scenario where i need to do a header validation . if validation succeeds i have to map source to target data and sent to SAP system. if validation fails i need to map source to error data and sent it to MQ system.
I am using enhanced receiver determination for selecting proper receiver based on the header validation. but in this case inspite of failed header validation there is no error message in SXMB_MONI...
what i wanted is that when header validation fails , error message should be displaced in moni and also a error message (xml ) should be sent to MQ system.
for implemention the above mentioned feature , i took another message mapping and interface mapping where i am explicitly throwing error -- Repository work.
In configuration , i just create one more receiver determination with new message type and in existing interface determination , i added the additional interface mapping ( throwing error ).
due to above changes , i am getting three message in Moni.. if header validation fails.
1. which indicated that there is message splitting.
2. one successful message ( source to error xml file ) to be sent to MQ system.
3. error message where i am explicitly throwing error .
can we have a situation where we have only one error message in moni and also the error is sent to MQ system?..
i guess there is some feature in interface determination.. what is enhaced interface determination..
I hope i am clear with my requirement..
Ranjeet Singh...

Have a look
/people/robin.schroeder/blog/2006/11/15/using-dynamic-receiver-determination-with-sync-interface
/people/venkataramanan.parameswaran/blog/2006/03/17/illustration-of-enhanced-receiver-determination--sp16
List of receivers can be dyamically determined and assigned at runtime using enhanced receiver determination .
http://help.sap.com/saphelp_nw04/helpdata/en/43/a5f2066340332de10000000a11466f/content.htm
Thanks

Enhanced Interface Determination for IDOCs

Hi All,
I've a query on the usage of Enhanced Interface Determination for IDocs.
I've to create IDocs based on the condition in the Message Mapping i.e. say if recordtype in the source is A then IDoc1 should be created and if recordtype is B then IDoc2 should be created.
Is it possible to use Enhanced Interface Determination to achieve this??.. Because I was told by someone that Enhanced Interface Determination can't be used for IDoc based scenarios though am using External Definitions for the mapping purpose. Please clarify.
Thanks in advance
Regards,
Joe.

Hi Sridhar/ Bhavesh,
Thanks for your prompt reply. I think I wasn't clear in my previous post.
The scenario is the input file has three different record types (3 different structures) and the IDocs should be created based on the record type. I don't think I can use the condition based scenario as the record types are totally different. Please suggest.
Thanks,
Joe.

Interface Determination under Enhanced Receiver Determination Scenario

Hi,
One of the very basic assumption for Enhanced Receiver Determination is that Receivers are found at run time, and one of the such requirement is that we don't know about Receiver Business System at the time of configuration.
Now for such scenarios, how do we configure "Interface Determination". For Interface Determination one of the input filed is "Receiver Service/Party", in addition to "Sender Service/Party" plus "Sender Interface"
Since we don't know Receivers at config, what value(s) should come in "Receiver Service/Party" in Interface Determination at config time.
Thanking all of you in advance

Hi Rajan,
You have to do the following things:-
First, maintain Database Table in SAP XI. Which contains several keys like Sender, Receiver system and then according to that key combination we perform a JCO call and fetch the values which gives us the correct receiver and interface.
Create a Data Type which will be having Two elements Service And Interface.
Now careate a message type and message interface for this data type. This will be for your receiver.
Then use source payload and perform a message mapping between Sender Payload & this Message Type.
Use UDF and make a JCO call and fetch table entries for service and interface.
Then in Directory perform extended determination and use this mapping into it. The result will be Service & Interface.
Thanqs
Biplab

Abap proxy with attachments in enhanced interface determination/mapping

Hi guys.
We were receiving a abap proxy from ECC with a pdf attached in the header.
This was the scenario PROXY ---> FILE
We used the PayloadSwapBean Module in a Receiver File Adapter to get this document and put it in a FTP Server.
Now we have to make and improvement in the scenario and we have to generate two receiver interfaces so the scenario looks like this:
PROXY ---> FILE and JDBC.
So we have to use an enhanced interface mapping and an enhanced interface determination.
The problem is that with this enhanced interface determination/mapping the attached document is lost.
Any solution?
Thanks a lot.
Regards.

> The problem is that with this enhanced interface determination/mapping the attached document is lost.
I know there was an issue in early PI 7.1 SP versions. maybe you find a bug fix for this?
Otherwise report to SAP.

Enhanced Interface Determination gives Empty Payload

Hi,
I am using Enhanced Interface Determination in my scenario.
1:3 Message Types(Interfaces).
The thing is that split occurs, but after Message Mapping I get empty Payloads..
I am using External Definitions instead of Message types.
Another question: Can there be multiple dynamic confgiurations during splits. i.e one Dynamic Configuration for each message split.
Note: testing the Interface mapping from IR with payload from MONI gives proper output.
Regards,
Sundar.

Hi All,
I copied the entire XML which i used for testing in Interface Mapping which i should not have....
I gave as
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
   <ns0:Message1>
      <ns1:SAP_HR_MT xmlns:ns1="http://com.cognizant/sapr3/all">
         <Participant>....
                     </Participant>
         <Dependent>
            ....         </Dependent>
         <Coverage>
            ....         </Coverage>
      </ns1:SAP_HR_MT>
   </ns0:Message1>
</ns0:Messages>
But the input should have been
<?xml version="1.0" encoding="UTF-8"?>
      <ns1:SAP_HR_MT xmlns:ns1="http://com.cognizant/sapr3/all">
         <Participant>....
                     </Participant>
         <Dependent>
            ....         </Dependent>
         <Coverage>
            ....         </Coverage>
      </ns1:SAP_HR_MT>
now the output is perfectly coming....:-)
Regards,
Sundar )

Enhanced interface determination IN BPM

Hello experts,
Question is in the title.
I'm in PI 7.0 and i think it's not possible. Can you confirm it ?
Thank you for your responses.
Regards.

Yes ! ;o)
But, i have a scenario with BPM : file -> synchronous call bapi -> 2 split mapping (using enhanced interface determination) -> possibility 4 files.
It's not a problem for me, because i will 'stop' BPM afterthe Bapi call, but i have to create most CC.
It was just an quastion for me.
Thanks.

Use of Enhanced option in Interface Determination

Similar Messages

Maybe you are looking for