XML message mapping considering idoc message variant

Dear Experts,
I am very new to PI. I am working on a scenario where I need to map VGON_OUT xml message from SNC system to ORDRSP.ORDERS05 inbound idoc of ECC 6.0 system.
The issue is :
In the inbound partner profile in ECC there are two ordersp message types. one with message variant SMI and another without any message variant.
Both of them are using different process codes for processing.
So my question is how to map the VGON_out xml message in PI?
Please note: the key difference is the idoc message variant.
There is no way to merge both of these message types as their function is serving two different purposes.
I have attached the xml file and the screenshot of the partner profile here.
Any suggestion or reference link or document would be deeply appreciated.
Thanks in advance.
Praty

Hi Pratyusa,
Did you try with different partner profiles for each ORDRSP?
Regards,
Krupa

Similar Messages

Splitting multiple IDoc XML files into single IDoc messages for R/3

Hi all. I have a problem splitting IDoc XML files coming in to XI. I currently have an interface that takes in single store sale IDoc transactions (type WPUBON01) in an IDoc XML file. I then have some complex graphical mapping on the IDoc before sending to R/3 via the IDoc adapter. This works fine. However, we now wish to include multiple sales in one file i.e. many WPUBON01 IDocs. I could use message splitting to do this BUT the mapping is so complex, I do not wish to have to change it to enable the processing of many IDocs in one file instead of just one.
What I want to do: have one mapping splitting a multiple IDoc XML file into single IDoc messages and then another taking these single messages as before and performing the mapping. I cannot find a way to do this in one interface; the main problem I'm having is getting XI to split the multiple IDocs into many single IDoc messages within XI itself. I'd be very grateful for any advice on the best way to do this.
Thankyou.
Stuart Richards (Halfords, UK)

Bhavesh,
Thanks again for a clear explanation... I'm moving forwards but still struggling. I've been on this all afternoon today (after a break on other things) and just cannot get my message to split properly (though the SOAP adapter problem I had earlier is now fixed!). If my initial IDoc XML file contains this format:
<WPUBON01><IDOC>....</IDOC>
<IDOC>....</IDOC>
<IDOC>....</IDOC></WPUBON01>
.. I'm not sure what the cardinaility on the first message mapping and interface mapping should be. I'd have thought the source interface would be 1 and the target would be 0..unbounded but this isn't working. I'm trying different things but I get different errors each time. Currently, I have the above cardinality in my first interface and I'm passing in the following data:
<WPUBON01><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832292</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160633</VORGZEIT><BONNUMMER>1001</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1001</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832293</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1002</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1002</ZUONR></E1WPB06></E1WPB01></IDOC><IDOC><EDI_DC40><TABNAM>EDI_DC40</TABNAM><MANDT /><DOCNUM /><DOCREL>620</DOCREL><DIRECT>2</DIRECT><IDOCTYP>WPUBON01</IDOCTYP><MESTYP>WPUBON</MESTYP><MESCOD>ST6</MESCOD><SNDPOR>WPUX</SNDPOR><SNDPRT>KU</SNDPRT><SNDPRN>0518</SNDPRN><RCVPOR /><RCVPRT>KU</RCVPRT><RCVPRN>0518</RCVPRN><REFINT>00000003832294</REFINT></EDI_DC40><E1WPB01 SEGMENT="1"><POSKREIS>0518</POSKREIS><KASSID>29</KASSID><VORGDATUM>20071029</VORGDATUM><VORGZEIT>160634</VORGZEIT><BONNUMMER>1003</BONNUMMER><KASSIERER>100</KASSIERER><CSHNAME> </CSHNAME><BELEGWAERS>GBP</BELEGWAERS><E1WPB02 SEGMENT="2"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="3"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="4"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="5"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="6"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="7"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="8"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="9"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="10"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="11"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="12"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="13"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB02 SEGMENT="14"><VORGANGART /><QUALARTNR>ARTN</QUALARTNR><ARTNR>000000065601301390</ARTNR><VORZEICHEN>-</VORZEICHEN><MENGE>1</MENGE><AKTIONSNR>0000000000</AKTIONSNR><REFBONNR> </REFBONNR><E1WPB03 SEGMENT="15"><VORZEICHEN /><KONDITION>PN10</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03><E1WPB03 SEGMENT="16"><VORZEICHEN></VORZEICHEN><KONDITION>ZPN1</KONDITION><KONDVALUE>1.00</KONDVALUE><CONDID /><QUALCONDID /></E1WPB03></E1WPB02><E1WPB06 SEGMENT="17"><VORZEICHEN></VORZEICHEN><ZAHLART>PTCS</ZAHLART><SUMME> </SUMME><KARTENNR /><ZUONR>1003</ZUONR></E1WPB06></E1WPB01></IDOC></WPUBON01>
In the message monitor, I get a chequered flag. Great. However, I get the dreaded error 500 in the SOAP receiver comm channel:
SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Internal Server Error
Exception caught by adapter framework: SOAP Error
Delivery of the message to the application using connection AFW failed, due to: SOAP Error.
Any ideas as to what this might be?! I'm getting there.... if I get a solution out of this, I promise to write the blog myself!
Cheers
Stuart

Message Mapping of IDOC "MATMAS.MATMAS05"

Hi!
I would like to execute the following message mapping for IDoc
MATMAS05 <--> MATMAS05.
What are the recommended fields to map?
Is the a button to automatically map the fields with the same names?
Thank you very much!
regards
Thom

Hi,
you could use the button "Map Selected Fields and Substructures if Names Are Identical"
it's explained here:
http://help.sap.com/saphelp_nw04/helpdata/en/49/1ebc6111ea2f45a9946c702b685299/frameset.htm
Or if you do it without a mapping:
simple IDoc to IDoc scenario with SAP PI
Regards
Patrick

Get the mapping values from one message mapping into another message mappin

Hi All,
I created two graphical message mappings. In first message mapping i created one user defined function and set one global container parameter and I need to use this parameter in my second message mapping user defined function. But the global container parameters can be used in different user defined functions in same message mapping. So is there any way to use the values which are set in one message mapping into another message mapping. If yes, please help me how to get?

Hi Koteswara rao,
As you said global container parameters from first message mapping are not accessible from second message mapping program.
i haven't faced situation like this.but, if you have some unmapped field in target message in first message mapping,you can put global variables data in that unmapped field.
anyway the output of first message mapping would be input for 2nd messages mapping,so you can access global data(unmapped field filled with global data in 1st MM) from 2nd mapping program..
Cheers,
Jag

Error in message mapping of IDoC Invoic02

Hi,
i have imported the invoic02 idoc into PI system. i have mapped the required field os idoc with standard XSD which is imported through ED. I'm able to most of the fields with idoc and XSD. however, some of the node in xsd are repaeting.
so here the part of xsd with which i'm mapping.
(first_node)ListOfTaxSummary                      0..1
(second_parent_node)TaxSummary                   1..unboubed
(child_node) tax                                 1..1
(element)TaxAmount                                0..1
(element)TaxCategoryCoded                         0..1
here the i have mapped ListOfTaxSummary    with the idoc node E1EDS01
TaxSummary with E1EDS01
tax with E1EDS01.
i tried all possibilities with different mapping. but i'm able to get the tax node under taxsummary with the element. the problem its been repeated as E1EDS01 idoc repeats.
please help us in solving this problem.
Thanks
Kind regards,
Lalitkumar.

Could someone tell me is there any relation for the above error in XML messages and to the message mapping?
The error mentions that you have used an IDOC in your mapping program which is not found in the ESR....you need to check if the IDOC is present in the ESR and is present under the correct SWCV.
Once you have done the check do some dummy change to the mapping and activate it (if in DEV) and then check the CACHE.

CIDX Standard Message Map to IDoc

Hi,
I am looking for CIDX standard message for mapping to SHPMNT05 IDoc. I want to know the standard CIDX standard message and the repository to find such standard messages when Standard IDocs available in SAP are known.
Regards,
Suraj Kumar

Hi Michal and Shabarish,
Thanks for providing the required information. I am stuck up with a issue which is explained below.
Sample xml downloaded from http://www.cidx.org/ is different from the required message.
Sample ShipNotice xml downloaded is as follows....
<?xml version="1.0" encoding="UTF-8" ?>
- <ShipNotice>
- <Header>
- <ThisDocumentIdentifier>
<DocumentIdentifier>12345678</DocumentIdentifier>
</ThisDocumentIdentifier>
- <ThisDocumentDateTime>
<DateTime DateTimeQualifier="On">2002-04-01T20:55:13Z</DateTime>
</ThisDocumentDateTime> ......
But what is required as per the business scenario is as follows
<?xml version="1.0" encoding="UTF-8"?>
<PlannedShipment>
   <PlannedShipmentIdentifier>191919</PlannedShipmentIdentifier>
   <ShipDirection>Outbound</ShipDirection>
   <FreightTerms>Pre-Paid</FreightTerms>
   <CarrierSCAC>SEFL</CarrierSCAC>
   <FreightForwarder/>
   <EquipmentType>ODY CODE HERE</EquipmentType>
   <EquipmentNumber>TRL2096</EquipmentNumber>
   <CarrierTrackingNumber>100283534</CarrierTrackingNumber>
   <LoadList>
      <Load>
         <PlannedLoadIdentifier>125656</PlannedLoadIdentifier>
         <TransportationOrderIdentifier>1230987</TransportationOrderIdentifier>
         <Schedule>
            <ScheduledPickupDate timezone="EST">2004-03-19T15:35:00</ScheduledPickupDate>
            <RequestedDeliveryDate timezone="EST">2004-03-22T15:35:00</RequestedDeliveryDate>
            <ScheduledDeliveryDate timezone="EST">2004-03-22T15:35:00</ScheduledDeliveryDate>
         </Schedule>   ..........
In this case, How should I proceed?
Kindly help me out.
Thanks & Regards,
Suraj Kumar

How to do message mapping in IDoc or RFC to file transfer ?

Hello guys. I have a doubt. I know how to do an IDoc to file or RFC to file scenario. But how to do mapping in an Idoc to file or RFC to file scenario ? As I understand mapping is done in the sender. But IDoc or RFhas no interface as its used for SAP. So where do we need to perform mapping ?

Hi,
You dont need the Data type and message type for IDOC's, RFC's and for external definitions. so u just create one DT,MT for your File structure and you need 2 message interfaces, one for file and one for the Idoc/RFC. You can use them in your mapping program.
Regards,
Kumar.
P.S: Reward Points if Helpful!!!!!!!!!

SWIFTMX message mapping in Financial Message Designer

Hi,
Is it possible to create a mapping between an external message and an internal message in SWIFTMX format like we do in SWIFT MT format? If so can anyone tell me how it can be done.
Thanks in advance!
Deepak

With little knowledge in this field, I think Oracle Payments Adapter may help you in implementing the same.
http://www.oracle.com/us/technologies/soa/service-bus-fsi-ds-066433.pdf
Regards,
Anuj

CIDX Standard Message Map to IDoc -- 2

Hi Michal and Shabarish,
Thanks for providing the required information. I am stuck up with a issue which is explained below.
Sample xml downloaded from http://www.cidx.org/ is different from the required message.
Sample ShipNotice xml downloaded is as follows....
<?xml version="1.0" encoding="UTF-8" ?>
- <ShipNotice>
- <Header>
- <ThisDocumentIdentifier>
<DocumentIdentifier>12345678</DocumentIdentifier>
</ThisDocumentIdentifier>
- <ThisDocumentDateTime>
<DateTime DateTimeQualifier="On">2002-04-01T20:55:13Z</DateTime>
</ThisDocumentDateTime> ......
But what is required as per the business scenario is as follows
<?xml version="1.0" encoding="UTF-8"?>
<PlannedShipment>
<PlannedShipmentIdentifier>191919</PlannedShipmentIdentifier>
<ShipDirection>Outbound</ShipDirection>
<FreightTerms>Pre-Paid</FreightTerms>
<CarrierSCAC>SEFL</CarrierSCAC>
<FreightForwarder/>
<EquipmentType>ODY CODE HERE</EquipmentType>
<EquipmentNumber>TRL2096</EquipmentNumber>
<CarrierTrackingNumber>100283534</CarrierTrackingNumber>
<LoadList>
<Load>
<PlannedLoadIdentifier>125656</PlannedLoadIdentifier>
<TransportationOrderIdentifier>1230987</TransportationOrderIdentifier>
<Schedule>
<ScheduledPickupDate timezone="EST">2004-03-19T15:35:00</ScheduledPickupDate>
<RequestedDeliveryDate timezone="EST">2004-03-22T15:35:00</RequestedDeliveryDate>
<ScheduledDeliveryDate timezone="EST">2004-03-22T15:35:00</ScheduledDeliveryDate>
</Schedule> ..........
In this case, How should I proceed?
Kindly help me out.
Thanks & Regards,
Suraj Kumar

Hi,
I have gone through different sites to find the suitable CIDX standard message. I understood that there are message standards supported from order to invoice. They are all in sync with either seller or buyer. But my scenario is entirely different. In between order to invoice there is one step where logistics is involved, where in we need to send the transportation order. Logistics will place the tenders to different freight agencies and carry out the business.
So, here in my scenario I need to send SHPMNT05 IDoc(Outbound shipment) to logistics using cidx standards. So, it is not Ship Notice (Buyer or Seller) and it should be different message dealing with logistics or freight agent.
I have two questions here:
1. Find suitable CIDX message for SHPMNT05.
2. If I do not find the suitable one, then 'How should I proceed?'.
XI Experts, kindly help me out.
Thanks & Regards,
Suraj Kumar

Problem in message mapping (outbound IDOC ORDERS05 from SAP R/3)

Hi to all,
I have an outbound interface from sap r3
sap r3 --> XI --> ftp server
idoc --> XI --> text file
Using IDOC orders05
The problem is in segment E1EDP01/E1EDP19
Segment E1EDP01 is unbounded and i map it well. If it contains E1EDP19, works fine. But in some cases, E1EDP19 not appears at E1EDP01segments. So then XI fails at mapping:
IDOC OUTPUT (OK)
1-E1EDP01/E1EDP19
2-E1EDP01
3-E1EDP01/E1EDP19
4-E1EDP01
XI WRITES (FAILURE)
1-E1EDP01/E1EDP19
2-E1EDP01/E1EDP19 (INFORMATION FROM LINE 3)
3-E1EDP01 (WRONG)
4-E1EDP01 (WRONG)
You can take a look of Mapping mode here:
<a href="http://img505.imageshack.us/my.php?image=orders05mappingcj8.jpg">[IMG]http://img505.imageshack.us/img505/1536/orders05mappingcj8.th.jpg[/IMG]</a>
We don't use BPM and wanna use a solution without it.
Pls ask me for more information if necessary.
Thanks a lot for your help; Regards

Hi all,
The mapping function includes an exists and a mapwithdefault.
Now the creation of the segment is handled ok, but not as well its fields. Its unable to determine the write of the second E1EDP19 segment and it does:
1- OK
2- OK
3- Writes E1EDP20 but not the 19
4- OK
Thanks for your interesting

PI 7.11: IDoc Message mapping

Hi there,
I'm currently working on a graphical message mapping using IDoc HRMD_A06 as source structure (HR master data transferred via PFAL).
In my result structure I have to fill a field CostCenter with the following logic:
If field KOSTL (cost center) is filled in node E1P0315, map this field to CostCenter in result structure, otherwise take KOSTL of node E1P0001.
The end date (ENDDA) has to be '99991231' in each case.
This is how the result structure looks like:
<e>                       [1...1]
<CostCenter>            [1...1]
</e>
This is the simplified source structure:
<E1PLOGI SEGMENT="1">
<E1PITYP SEGMENT="1">                        [0...n]
     <E1P0001 SEGMENT="1">                     [0...n]
       <INFTY>0001</INFTY>                     [0...1]
       <ENDDA>99991231</ENDDA>                 [0...1]
       <KOSTL>0000012345</KOSTL>               [0...1]
    </E1P0001>
</E1PITYP>
<E1PITYP SEGMENT="1">                        [0...n]
    <E1P0315 SEGMENT="1">                      [0...n]
      <INFTY>0315</INFTY>                      [0...1]
      <ENDDA>99991231</ENDDA>                  [0...1]
      <KOSTL>0000024001</KOSTL>                [0...1]
    </E1P0315>
</E1PITYP>
</E1PLOGI>
How can I do the check if field KOSTL of node E1P0315 is null?
I've tried an existence check for the whole node (E1P0315->exists), but then it fails, because all E1PITYP nodes are processed.
I hope my problem is clear to you.
Would it be better to use another mapping type?
As I'm an ABAP developer, I would of course prefer some lines of code to this graphical drag&drop thing.
Thanks in advance!

Cheers, guys!
I did it now like that:
http://www.abload.de/image.php?img=mappingflknz.jpg
Click on the image to enlarge it!
The logic is as following (ABAP Pseudo-code ):
IF 0315_KOSTL and 0315_ENDDA are populated.
IF 0315_ENDDA equals '99991231'.
    map 0315_KOSTL to Cost_Center.
ENDIF.
ELSE.
IF 0001_KOSTL and 0001_ENDDA are populated.
    IF 0001_ENDDA equals '99991231'.
      map 0001_KOSTL to Cost_Center.
    ENDIF.
ENDIF.
ENDIF.
Is that a good way to do that mapping?
Do I also have to use the removeContexts function or is it ok like that?
Could I also do that with an ABAP mapping program?
Thanks in advance!

Message Mapping - IDOC to http

Hi ,
I am creating Message mapping for IDOC to Http scenario.
In which i have the following requirement. For a partner Role in segment E1BPDLVPARTNER we need to get the Address_No value
and then with that we need to get the address from segment E1BPADR1
<E1BPDLVPARTNER>
      <PARTN_ROLE>AG</PARTN_ROLE>
     <PARTNER_NO>0007745359</PARTNER_NO>
</E1BPDLVPARTNER>
<E1BPDLVPARTNER SEGMENT="1">
    <PARTNER_NO>0007745359</PARTNER_NO>
    <ADDRESS_NO>0000267775</ADDRESS_NO>
</E1BPDLVPARTNER>
   <E1BPDLVPARTNER SEGMENT="1">
     <PARTNER_NO>0007759123</PARTNER_NO>
     <ADDRESS_NO>9000001048</ADDRESS_NO>
</E1BPDLVPARTNER>
<E1BPADR1 SEGMENT="1">
     <ADDR_NO>000075</ADDR_NO>
     <NAME>BRIDT HOSPITAL INC</NAME>
   </E1BPADR1>
   <E1BPADR1 SEGMENT="1">
     <ADDR_NO>00775</ADDR_NO>
      <NAME>BRIDGA</NAME>
   </E1BPADR1>
   <E1BPADR1 SEGMENT="1">
    <ADDR_NO>05</ADDR_NO>
    <NAME>BRIDL INC</NAME>
   </E1BPADR1>
Can you provide inputs on this.
Thanks,
Vishal

For the Address No 0007745359 in E1BPDLVPARTNER we need to go to the E1BPADR1 segment and get the address from
it and populate the target. Also the data above is test one
Me a bit confused about your requirement!
In your structure Partner_Number is having the value 0007745359
What i get is you have to check for PartnerNo in E1BPDLVPARTNER and if that value matches then go to E1BPADR1 segment and get the Address......but to go to a particular E1BPADR1 you need to check for some field within it.....
Your mapping logic will be something like:
PartNum/ AddrNum -->
                              --->equalS --->
Constant(0007745359)
                                                          ----> And ----> IfWithoutElse --->    Target
Field_of_E1BPADR1 (validation logic) -->             Then(Field_of_E1BPADR1)
Context of PartNum/ AddrNum to be raised and also that of Field_of_E1BPADR1 (the one on which validation is imposed.
If possible get some more details from your technical lead on how to select the E1BPADR1 ...
Regards,
Abhishek.

Filtering of records in Message Mapping

I am facing problem during filtering record in message mapping. My message comes from R3 and should be sent to one business service in entirety and should also be sent to another business service in part. To resolve this I created a message map for selecting record based on some conditions but this creates empty XML nodes wherever condition is not satisfied. Everything works fine but the scenario fails at the end while trying to convert XML to text using file adapter. The error is Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)

Hi Rajesh,
This scenario you are trying can be done using CONDITIONAL RECEIVER DETERMINATION and RB SPLIT, where you can basically have one sender and two receivers.
To do this without using a BPM.
1. Create your mapping program that will map the information from the source file
into the destination idoc. This has to be a 1:N split. Just make sure that the destination message type and message interface are are of occurrence N.
2. Also, you will have 2 destination interfaces and 2 interface mapping, one for the IDOC and one for the mail.
Now, there are a few essential steps in your configuration,
1. In the receiver determination, specify the 2 receiver systems, one for your IDOC and the other for your MAIL.
2. Now, you will have a condition window. Just type the condition on the basis of which the receiver has to be determined for the mail and the idoc business system. Just remember that the condition can be specified only for the source message.
3. In the Interface Determination, you have an option called RB CLASSIC and RB SPLIT. To do a 1:N split, you will have to do a RB_SPLIT.
And since you wanted to covert the XML format to text format you require content conversion at the receiver adapter end, for that please go through these links below. It clearly explains your requirement.
/people/arpit.seth/blog/2005/06/02/file-receiver-with-content-conversion
http://help.sap.com/saphelp_nw04/helpdata/en/d2/bab440c97f3716e10000000a155106/frameset.htm
I hope I have answered your query.
Regards,
Abhy
note: do reward points for the helpful answers.

How to get the segment detials of IDoc message type.

Dear Friends,
I want to write function module , which takes the IDOC message type as an input and returns all the segment fields in response.
Basically I want to get the XML schema of a IDOC message type and need to expose these details toa 3rd party application to use.
Dear experts ,Please do give me some ideas how to achieve this .
like tables from where i can get these details or u feel any other goos way of doing the same.
thx,
jeevan

Hello experts,
Please participate .........
To redefine my objective I will say:--
I am trying to do some thing very similar that is there in XI .
You might have seen the way IDOCs are shown while mapping an idoc structure.
Its like you select a message type and u get all the list of Idoc Structure shown .
I am really relying on you people.
thx ,
jeevan

PI 7.1 Operation mapping - Multiple message mapping - one to many issue

Dear Experts,
I am facing this issue in PI 7.1 and I beleive i did similar one in PI 7.0 successfully.
I have an operation mapping with two message mappings.
The occurence of source message of operation mapping is 1
The occurence of target message of operation mapping is 0..unbounded
Corresponding i configured two message mappings
For message mapping-1
Source message occurence = 1 and Target message occurence = 1
For message mapping-2
Source message occurence = 1 and Target message occurence = 0...unbounded
When i test message mappings individually they are working good. But when i test it in operation mapping, the operation mapping is not working..as it is not able to convert single occurence output of message mapping -1 to the second message mapping-2.
Any suggestions?
Thanks.

The message that i get when testing in operation mapping:
Runtime Exception when executing application mapping program com/sap/xi/tf/_MM_MessageMapping_1_; Details: com.sap.aii.mappingtool.tf7.IllegalInstanceException; Cannot create target element /ns0:MT_MessageMapping_1_TargetMessageType/RECORDSET. Values missing in queue context. Target XSD requires a value for this element, but the target-field mapping does not create one. Check whether the XML instance is valid for the source XSD, and whether the target-field mapping fulfils the requirement of the target XSD
My question is, has somebody mapped similar scenario in your environment? If yes, can you please provide details.
Operation mapping : 1 to 0..unbounded
Message Mapping1: 1 to 1
Message Mapping2: 1 to 0...unbounded

XML message mapping considering idoc message variant

Similar Messages

Maybe you are looking for