With out Interface mapping

Hi
I have a scenario like from SAP-XI-mainframe..My question is this poosible to send the data with out Interface mapping
venkat

hi,
sure it is
no need for any mapping (interface mapping)
just don't create it in repository and don't use
it in directory and your flow will work without it
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Similar Messages

File to file with out message mapping and using variable substitution

Hi,
Can any one send me a scenario where we can have file to file scenario with out message mapping and where i can use variable substitution.
As of now i am using integrate configurations where i cant use variable substitution as the message does not reflect in integration engine. I need to populate time stamp between <filename><timestamp>.txt.pgp
I am as of now using configuration scenario.
The time stamp always writes before the last file extension.
Let me know your thoughts?
Thanks,
Chandra.

Hi Chandra,
u can use the Variable substitution even without IR contents also(Mapping....).
in the receiver communication channel just specify the path u want to access for a value...
eg: filename payload:mt_name,1,records,1,name,1
and in th file name give it as %filename%.txt... or vt ever ur requirement
Babu

Query reg Variable Substitution with enhanced interface mapping

Hi All,
The scenario is IDoc to file using enhanced interface determination (message split based on some conditions) and the output file name should be based on a field value in the IDoc. So, I've tried using Variable Substitution Option in the receiver file adapter. But it's failing with the error 'com.sap.aii.adapter.file.varsubst.VariableDataSourceException'.
My question is does Variable Substitution works with Enhanced Interface Determination? Bcoz the outcome of interface determination is a main and sub payload.
IDoc Payload
<?xml version="1.0" encoding="utf-8" ?><HR_HRMD_A07><IDOC BEGIN="Constant"><E1PLOGI SEGMENT="Constant">
<E1PITYP SEGMENT="1"><E1P0000 SEGMENT="1"><ENDDA>99991231</ENDDA></E1P0000></E1PITYP></E1PITYP></E1PLOGI></IDOC></HR_HRMD_A07>
Variable Substitution XPATH, which I've mentioned is payload:HR_HRMD_A07,1,IDOC,1,E1PLOGI,1,E1PITYP,1,E1P0000,1,ENDDA,1
Thanks in advance.
Regards,
Joe.

Hi,
It was the problem with the capital letters for the variable field. We changed it to small letters, then the issue is resolved.
Thanks,
Joe.

About interface mapping

what are there case about interface mapping?
i knew that the following:
outbound to inbound
abstract to abstract.
what else the case?

Hi joy zheng ,
These r the details about interface mapping :
Interface Mappings
You can define mappings for an interface pair (source and target interface) by using message interfaces and message types in the Integration Repository.You can also define the corresponding mappings when the source or target interface is an IDoc, an RFC, or another interface connected by an adapter.
When defining mapping programs for request, response, or fault messages, the definition is first separated from the interfaces that reference the corresponding message types. Furthermore, you can reuse a message type for multiple interfaces. This means that the simple definition of a mapping program is not sufficient to establish a connection (that is based on the assignment of outbound and inbound interfaces).
This role is undertaken by the interface mapping:
●     An interface mapping specifies the corresponding mapping programs for request, response, or fault messages for a selected interface pair. You use an interface mapping to register mappings for an interface pair.
●     You can also specify multiple mapping programs to be executed one after the other in the case of requests and responses for an interface mapping.
You can also define multiple interface mappings for the same interface pair, to provide multiple variants in the Integration Repository. At configuration time, the customer can select the appropriate mapping in an interface determination and save it in the Integration Directory
Use :
Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time . The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.
Features
Executing Multiple Mapping Programs for One Direction
By using an interface mapping you can execute multiple mapping programs consecutively for the transformation of a request or response message. In such cases, an interface mapping comprises multiple steps for which the following applies:
●     The steps are executed in the sequence specified (from top to bottom). The result of the mapping program from the previous step is forwarded to the mapping program of the subsequent step.
●     Each step can reference a mapping program that executes a 1:1, 1:n, n:1, or an m:n transformation. In the case of multi-mappings (1:n, n:1, or m:n), the previous step must create the same number of messages that the subsequent step expects.
●     Multi-mappings use one envelope to put all messages in one structure. If one of the steps references a multi-mapping program, all subsequent steps must use the same envelope.
The mapping for a request message comprises two message mapping programs: one 1:1 transformation and one 1:n transformation. Since the latter message mapping uses the multi-mapping envelope for both the target message and the source message, the message mapping for the 1:1 transformation must also create a transformation result with a multi-mapping envelope.
You do not strictly need to divide up one direction of the whole mapping into different steps. However, this enables all the message formats in one system landscape to be mapped to a central message format, for example. This results in less mapping programs being required because you no longer need to be able to map all the different message formats to each other.
Activities
       1.      Create your interface mapping on the design maintenance screen of the Integration Builder (see also: Creating an Object).
You can also create multiple interface mappings for the same interface pair.
       2.      Enter the source and target interfaces that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. The following restrictions apply:
○     If you want to use the interface mapping in a transformation step in an integration process, you must only specify abstract message interfaces. Furthermore, all objects (integration process, interface mapping, and all objects referenced by the interface mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help) (see also: Underlying Software Component Versions).
○     If you want to map multiple messages to each other by using a multi-mapping, you can only specify asynchronous interfaces (for further restrictions, see: Multi-Mappings). If any message interfaces are missing, you can also create them by using the functionCreate New Object ().
If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name in this case.
       3.      To import the properties of the interfaces, choose Read Interfaces. The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).
       4.      To develop an external mapping program, export the XSD schema of the respective request or response message as a zip file after you have imported the interfaces. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema.
       5.      To reference a mapping program for the respective message, you have the following options:
○     Select an existing mapping program from the Integration Repository by using the input help (). If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the Integration Repository (in multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.
○     You can create message mappings directly from the interface mapping. To do this, select the mapping type Message Mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping () in the Mapping Program frame. The Integration Builder copies the specifications of the messages and their occurrence directly from the interface mapping.
An interface mapping can only reference mapping programs that belong to the same or an underlying software component version of the interface mapping. This ensures that the mapping program can be shipped together with the interface mapping (see: Software Logistics).
       6.      If you are not using a mapping for a fault message, you can execute multiple mapping programs in succession for request and response messages:
○     To insert an additional line for a mapping program, choose .
○     To delete the registration for a mapping program, choose .
At runtime, the mapping programs are executed from top to bottom.
       7.      Save the interface mapping.
The following web-site gives complete details about interface mapping :
http://help.sap.com/saphelp_nw2004s/helpdata/en/12/05731a10264057badc32d3d3957015/content.htm
**********Please reward points if u find this useful
cheers,
gyanaraj

Interface mapping test successful, throws exception in BPM

Hi.
We are having a problem with an Interface mapping which works when
tested in Integration Builder, but throws an Exception when it is part
of the Transformation in a BPM.
The scenarion is such:
1. The sender calls the outbound interface using a web service.
2. XI uses the input and passes to the Integration Process
3. In the BPM, a LOGON message is built to call the web service as
specified by an external web service . The input and
output messages are just a single string, in which the other XML is
embedded.
4. XI receives a response from the web service call
5. XI Extracts the sessionId from the response and combines it with the
initial input (Step 1) to create the query for the query message in
the web service.
It is in Step 5 where the transformation fails, with an Exception in
the DefaultTrace.trc as
Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
Thrown:
MESSAGE ID: com.sap.aii.ibrun.server.mapping.rb_MappingRuntimeException.EXCEPTION_DURING_EXECUTE
com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_LogonResponse_PropertySearchRequest_to_ExternalRequestSOAP_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:Messages/ns0:Message1/ns1:EXTERNAL/REQUEST. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd
I have extracted the data from the initial request (step 1) and the
logon response (step 4) and using these I have tested the Interface
Mapping. There is no problem with this and the tests are successful.
From what I can see, because the Response field in the LOGONResponse
contains more XML tags, XI must be parsing it and assuming the tags are
tags in the message, and not just the string, thus it is complaining
that the XSD types do not match. This extra XML Parsing does not take
place in the Interface Mapping Test.
I have put the response into a User Defined Function which just has one
line "return new String("Hello")" and that fails. However, if this UDF
does not have the Response as the input, it does not complain.
Please advise.
--Reenal

hi
You will have to use specific replacements for you xml tags if it is coming as a paramter
replace '<' with <
replace '>' with >
for eg: I want to pass <TakeIt>200</TakeIt> as value to Element <A>
Mapping won't work if it is passed like
a) <A><TakeIt>200</TakeIt></A> - Wrong
Instead the replace the angle brackets
b) <A><TakeIt>200</TakeIt></A> - Correct
While testing the mapping in IR (a) will work bcoz the test tool will convert it to (b) format. Check the xml source in test tool.
So ensure the web response is like (b)
rgds,
Arun

Interface Mapping

I have an issue with my interface mapping
I have an interface mapping between an Outbound Interface and an Abstract Interface.... Obviously this is for a mapping between the sender and BPM.
Anyway Everything activates sucessfully in the Repository.
However when I try to select it in the Interface Mapping in the Integration Directory I can't see anything...
Anyone have any ideas as to where this could be? Where I am going wrong

hi Mendez,
this case happens mostly when your SCV (under which the interface is) is not installed on the particular business system.
goto SLD and verify if the SC is installed on that particular Technical system/business system.
The other reason may be the update of cache. u can also verify that in the transaction sxi_cache

Value mapping, interface mapping, standard funtions and user defined functi

I like have more information abt live scenario's use of value mapping, interface mapping, standard funtions and user defined functions.
How to create user defined funtions and how to use it in XI?
thanks in advance
shiva

Hi,
Interface mappings register your mapping program for an interface pair in the Integration Repository. If you require a mapping at runtime, it is sufficient to select the interface mapping for the interface pair at configuration time .The Integration Server uses the interface mapping to identify associated mapping programs for request messages, response messages, fault messages, or all three.
Features
Executing Multiple Mapping Programs for One DirectionBy using an interface mapping you can execute multiple mapping programs consecutively for the transformation of a request or response message. In such cases, an interface mapping comprises multiple steps for which the following applies:
●     The steps are executed in the sequence specified (from top to bottom). The result of the mapping program from the previous step is forwarded to the mapping program of the subsequent step.
●     Each step can reference a mapping program that executes a 1:1, 1:n, n:1, or an m:n transformation. In the case of multi-mappings (1:n, n:1, or m:n), the previous step must create the same number of messages that the subsequent step expects.
●     Multi-mappings use one envelope to put all messages in one structure. If one of the steps references a multi-mapping program, all subsequent steps must use the same envelope.
The mapping for a request message comprises two message mapping programs: one 1:1 transformation and one 1:n transformation. Since the latter message mapping uses the multi-mapping envelope for both the target message and the source message, the message mapping for the 1:1 transformation must also create a transformation result with a multi-mapping envelope.
You do not strictly need to divide up one direction of the whole mapping into different steps. However, this enables all the message formats in one system landscape to be mapped to a central message format, for example. This results in less mapping programs being required because you no longer need to be able to map all the different message formats to each other
Activities
       1.      Create a message mapping on the design maintenance screen of the Integration Builder (see also: Creating an Object).
You can also create multiple interface mappings for the same interface pair.
       2.      Enter the source and target interfaces that require a mapping of the request message, the response message, the fault message, or all three, in the table of the same name. The following restrictions apply:
○     If you want to use the interface mapping in a transformation step in an integration process, you must only specify abstract message interfaces. Furthermore, all objects (integration process, interface mapping, and all objects that reference the interface mapping) must be in the same software component version. If you want to reference objects from underlying software component versions, you must access the objects from the Basis Objects branch (in the navigation tree or using an input help).
○     If you want to map multiple messages to each other by using a multi-mapping, you can only specify asynchronous interfaces (for further restrictions, see: Multi-Mappings). If any message interfaces are missing, you can also create them by using the function Create New Object ().
If the interface cannot be imported or cannot be created in the Integration Repository (in the case of an external adapter, for example), you must enter the interface names manually. However, it is not possible to check the technical name in this case.
       3.      To import the properties of the interfaces, choose Read Interfaces. The table in the lower area displays tab pages for the request message, response message, and if available, for the fault message, for each mode of the interfaces (either synchronous or asynchronous).
       4.      To develop an external mapping program, export the XSD schema of the respective request or response message as a zip file after you have imported the interfaces. The zip file can contain multiple schema files that reference each other, for example in a multi-mapping. In this case, the schema with the global message element has the name MainSchema.
       5.      To reference a mapping program for the respective message, you have the following options:
○     Select an existing mapping program from the Integration Repository by using the input help (). If this is a message mapping, the default setting of the input help only displays those message mappings that are found using the source and target message in the Integration Repository (in multi-mappings, the first source and target messages are used as the search criteria). However, you can also display any number of message mappings, for example, because you are constructing a mapping from several mapping programs with intermediate instances which have no message types.
○     You can create message mappings directly from the interface mapping. To do this, select the mapping type Message Mapping in the Type column. Position the cursor in the Name column and choose the function Create New Message Mapping () in the Mapping Program frame. The Integration Builder copies the specifications of the messages and their occurrence directly from the interface mapping.
An interface mapping can only reference mapping programs that belong to the same or an underlying software component version of the interface mapping. This ensures that the mapping program can be shipped together with the interface mapping (see: Software Logistics).
       6.      If it is not a mapping for a fault message, you can execute multiple mapping programs in succession for request and response messages:
○     To insert an additional line for a mapping program, choose .
○     To delete the registration for a mapping program, choose .
At runtime, the mapping programs are executed from top to bottom.
       7.      Save the interface mapping.
Regards
Aashish Sinha
PS : reward points if helpful

Interface Mapping with out SWCV ?

HI Guys,
is it possible to create an interface mapping in the XI Repository even without a software component version and a message interface.
Actually i have developed a Proxy-Soap synch scenario and now we got the need to change our namespace name and the interface name. Is there nay way that i can change the namespace and the interface name wiht the existing mappings
any help would be appreciated
Thanks,
srini

Hi Srini,
>>>is it possible to create an interface mapping in the XI Repository even without a software component version and a message interface
Neither nor.
>>>Actually i have developed a Proxy-Soap synch scenario and now we got the need to change our namespace name and the interface name. Is there nay way that i can change the namespace and the interface name wiht the existing mappings
You can copy single objects and all of one namespace to the other. The linked objects have to be changed manually.
Regards,
Udo

Multi mapping with out BPM

HI ALL ,
I am trying to do multi mapping with out using BPM .I will get message from the sender and i need to send that to two different target system. I have defined the mapping in the IR . In ID i have created the configuration scenario and i have created the receiver determination .In receiver determination i have selected "EXTENDED" and when i select input help for mapping name it says "NO Object found". What else should i do get the mapping program here .
Regards,
Tarun.

Bhavesh,
I'm sorry but if he needs 2 different receivers, then it's not the case of using Enhanced Interface Determination.
sapuser,
if you scenario is asynchronous, then it's easily implemented.
But it won't be achieved with multimapping.
You'll have 2 receivers in receiver determination (normal RD, not enhanced). For each of those, you'll have to create a separate simple mapping (that will generate the message expected at each receiver system) and refer that mapping in the interface determination of each receiver.
For example, you have input_message containing data1 and data 2. You'll have 2 simple mappings (not a multimapping), 1 generating output_message_1 containing data1 and the other generating output_message_2 containing data2. Then refer those mappings in the proper interface determinations.
Regards,
Henrique.

Defining input message Type for webservice interface with out input

Hi all,
I am configuring a scenario RFC -> XI -> Webservice. My sync webservice doesnot need any input. it genrates a random number which needs to be sent back to the RFC. How can i define an input message data type with out any data? As the interface requires both input and output data types in XI?
I tried a dummy data type with a single string input and didn't map it. but its not working because of name space issues. i specified a seperate XML name space in Message Type but i get a Target URL as the name space in the request which i provided in the SOAP reciever adapter.
Any help will be appriciated
Thanks and best regards,
Kulwant Singh

Hi
Can u chk the webservice request using test tools like stylus studio or xml spy and ensure that the same request is going out of XI .
make sure that you have changed the default xml namesapce in the target MT.
rgds
Arun

Is it possible to map the cmp fields of the entity bean with out dictionary

Dear sirs,
I have created the EJB project module and WEB Module. Now i have to map the CMP fields of the entity bean to the underlying table. Is it possible to map the cmp fields of the entity bean with out java dictionary? If yes how can we do that.
I have got some error while mapping an EJB's CMP fields to the table through dictionary. I was actually intended to map 79 fields but it gives an error that more than 64 fields are not allowed while building the dictionary.
1. Can you tell me what could be the possible reason?
2. Is it possible to map the cmp fields of the entity bean with out java dictionary? If yes how can we do that.
Kindly helo me,
Sudheesh K S

Hi,
Sudheesh please check up if the below link helps,there are other ways of writing the persistent.xml for container managed entity bean.
http://help.sap.com/saphelp_nw04s/helpdata/en/9b/f695f0c84acf46a4e0b31f69d8a9b7/frameset.htm, probably in the studio you cannot browse through tables not in the java dictionary,but manually editing it may still solve the problem.
Also here is another link that specifies the databases supported by J2EE Engine.
http://help.sap.com/saphelp_nw04s/helpdata/en/66/a5283eeb47b40be10000000a114084/frameset.htm
The below link shows how to specify the database vendor and datasource
http://help.sap.com/saphelp_nw04s/helpdata/en/e1/67fc3ee241ba28e10000000a114084/frameset.htm
Hope you are able to solve the problem.
Do let us know if you come up with the solution.
Regards,
Harish
Message was edited by: HARISH SUBRAMANIAN

Define Inbound Interface for Interface Mapping with Java functions

Hi,
we are developing an R/3-XI-ITK-SBO system. We realized our SOAP component as custom java functions and we installed it on ITK.
We need to import and configure these functionality in XI because we need to reference to it when we define the Message Interface and the Interface Mapping in Integration Builder Design.
Someone is able to tell us how we can import and configure these java function or definition in XI?
Thanks in advance.
Best regards.

Hi,
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training

Mapping with out bpm

hi...guys
how we will do 1:n multi mapping with out using bpm , pls explain..
with regards,
Prasad.

Hi Prasad
Go thru the forums given below.. which will discuss the same...
1:N mapping without using BPM
Re: 1:N mapping without using BPM --> IDOC to multiple files
Cheers..
Vasu
** Reward Points if found useful **

Interface-Mapping with a Fault Message Type

Hi,
we have an abap-proxy and some messages generated errors. The errors can be displayed via sxmb_moni. The proxy raises an "Application Error (Restart possible)".
Now I wanna transform the generated fault message (of the proxy) with a message mapping and send the output to a file.
My problem is, that it is not possible to define an interface mapping with the fault message as well as it is not possible to define a receiver determination.
Any ideas?
Thanks a lot
Regards
Wolfgang Hummel

Hello
As far as I know you can propogate the application error back to the calling application only in case of a Synch Interface? Are you making a Synch call where the proxy triggers a fault message, if yes then all you need to do is to make the change in XI to have the fault message for both the outbound and inbound message interfaces and then a corresponding fault message mapping and select this in the Interface Mapping and then the fault message will be sent to the source / calling application.
In the case of Asynch calls I don't think this is possible until you use a BPM. Have not tried this myself though.
Regards,
Bhavesh

Interface Mapping with Multiple Message Mappings

Hi My Scenario is
File to Idoc.( Multiple records to Multiple idocs )
Due to Complexity of Mapping I split the Mapping step into 2.
My Source System does not provide Namspace when they are sending XML Data.
When I try 2 mappings individually both Mappings works fine.
However when I try test using Interface Mapping target messages are not generated.
Since 2nd Mapping invoves Mapping Split its expecting extra tags as shown here in the Targert Message generated from Message Mapping 1.
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <ns0:Message1>
How can I solve this problem ?

When I do Message Mapping:
From message Mapping 1 target Produced is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:CostMaintenanceXI xmlns:ns0="http://test.xxx.com">
<CostMaintenanceXI>
<CostMaintenanceXI>
<Product>000000000000000023</Product>
<Plant>1401</Plant>
<Supplier>0000000001</Supplier>
<ValidityFrom>20021212</ValidityFrom>
<DIIndicator>ZFOB</DIIndicator>
<COGAmount></COGAmount>
<COGCurrency></COGCurrency>
<FreightAmount></FreightAmount>
<FreightCurrency></FreightCurrency>
<MISCAmount></MISCAmount>
<MISCCurrency></MISCCurrency>
<SPAAmount></SPAAmount>
<SPACurrency></SPACurrency>
<LandedCaseCost></LandedCaseCost>
<LandedCaseCurrency></LandedCaseCurrency>
<FrontLinePrice></FrontLinePrice>
<FrontLinePriceCurrency></FrontLinePriceCurrency>
</CostMaintenanceXI>
</CostMaintenanceXI>
</ns0:CostMaintenanceXI>
in 2nd Mapping I entered some details in the test tab and the generated source is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
 <ns0:Message1>
 <ns1:CostMaintenanceXI xmlns:ns1="http://test.xxx.com">
 <CostMaintenanceXI>
 <CostMaintenanceXI>
 <Product>1</Product>
 <Plant>1</Plant>
 <Supplier>2</Supplier>
 <ValidityFrom>12212122</ValidityFrom>
 <FOBIndicator/>
 <DIIndicator>ZFOD</DIIndicator>
 <COGAmount>10</COGAmount>
 <COGCurrency/>
 <FreightAmount>10</FreightAmount>
 <FreightCurrency/>
 <MISCAmount>10</MISCAmount>
 <MISCCurrency/>
 <SPAAmount>10</SPAAmount>
 <SPACurrency/>
 <LandedCaseCost/>
 <LandedCaseCurrency/>
 <FrontLinePrice/>
 <FrontLinePriceCurrency/>
 </CostMaintenanceXI>
 </CostMaintenanceXI>
 </ns1:CostMaintenanceXI>
 </ns0:Message1>
</ns0:Messages>
As you can see both of the above structures differs in xmlns. I dont see anything else weird.

With out Interface mapping

Similar Messages

Maybe you are looking for