IDoc to IDoc Scenario - Correct Interface Mapping configuration

Hello All,
i have to configure an Interface Mapping for an IDoc to IDoc scenario.
IDoc Type for sending and receiving already imported and located under Imported Objectes\IDocs in respective Software Component Version.
Now, how is the correct configuration? Add the sending respectively receiving IDoc Type directly to Source Interface/Target Interface under Display Interface Mapping or create first a sending Message Interface and a receiving Message Interface and add the IDoc type under configuration Message Types. Then add the Message Interface to the Interface Mapping.
The selection for direct import of the IDoc structure under the Interface Mapping (Source Interface/Target Interface) is possible.
Many Thanks in advanced!
Jochen

hi,
for IDOCs (if you don't use a BPM)
you don't need any message interface
so if you have already created a message mapping
you can put the IDOCs directly to your interface mapping
then click on read interfaces
and select your message mapping program
if you want to learn more about IDOCs and XI
have a look at my book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi">Mastering IDoc Business Scenarios with SAP XI</a>
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

PI : Idoc to JDBC scenario : repeating segments mapping issue

Experts
Please help.
Question reg. mapping for ECC idoc to JDBC scenario.
I am using the ORDRSP idoc which has multiple segments as below.
IDOC -> multiple E1EDK14 segments with 2 fields (QUALF and ORGID)
Depending on the value of the QUALF field i need to populate the column in my target structure.
QUALF 001 => Colmn a
QUALF 002 => Colmn b
For now my graphical mapping is very simple - QUALF => column a (done just to find out how PI mapping works)
What happens in my case, is the PI Payload shows all the E1EDK14 segments however only the value 006 present in the first occurence goes into the target column.
How do I repeat a mapping between QUALF and target col. for multiple occurences of the same segment?
Please can you guide me reg. use of context, loop over segment, UDF = which will be the best solution to achieve this?

Hi
My mapping is as below. I will take an example of a sales order that has 2 line items 00010, 00020. The payload is as follows
I see this payload in the SXMB_MONI transaction => Receiver grouping => Payloads
- <ZORDRES>
- <IDOC BEGIN="1">
+ <EDI_DC40 SEGMENT="1">
+ <E1EDK01 SEGMENT="1">
+ <E1EDK14 SEGMENT="1">
<QUALF>006</QUALF>
<ORGID>01</ORGID>
</E1EDK14>
+ <E1EDK14 SEGMENT="1">
<QUALF>007</QUALF>
<ORGID>01</ORGID>
</E1EDK14>+ <E1EDK03 SEGMENT="1">
+ <E1EDK03 SEGMENT="1">
+ <E1EDK03 SEGMENT="1">
+ <E1EDK03 SEGMENT="1">
+ <E1EDKA1 SEGMENT="1">
+ <E1EDKA1 SEGMENT="1">
+ <E1EDKA1 SEGMENT="1">
+ <E1EDKA1 SEGMENT="1">
+ <E1EDKA1 SEGMENT="1">
+ <E1EDK02 SEGMENT="1">
+ <E1EDK02 SEGMENT="1">
+ <E1EDK17 SEGMENT="1">
+ <E1EDK18 SEGMENT="1">
+ <E1EDK18 SEGMENT="1">
+ <E1EDP01 SEGMENT="1">
<POSEX>000010</POSEX>
+ <E1EDP01 SEGMENT="1">
<POSEX>000020</POSEX>
</E1EDP01>+ <E1EDS01 SEGMENT="1">
<SUMID>001</SUMID>
<SUMME>2</SUMME>
</E1EDS01>
+ <E1EDS01 SEGMENT="1">
<SUMID>002</SUMID>
<SUMME>1100.00</SUMME>
<SUNIT>GBP</SUNIT>
</E1EDS01>
</IDOC>
</ZORDRES>
There are 2 problems. First one which I discovered after posting the query. I can see only the line item 10 in the query that gets contructed in PI to insert the data into the target jdbc table. Please see jdbc receiver communication channel log below
If you see above there are 2 E1EDP01 segments for line 00010, 00020.
INSERT INTO tblOItem (IDocDate, IDocTime, SalesOrderNo, ItemNo, Plant, ItemCategory, UnitSellPrice, QuantityOrdered, QuantityAllocated, ScheduledDeliveryDate) VALUES (20111206, 135530, 0015002085, 000010, 0086, ZTAN, 0.00, 1.000, 1.000, 20111201)
My source and target mappings are as below.
ZSALORD
 IDOC
 BEGIN
 E1EDK01
 E1EDP01
 POSEX =============> SalOrdItm table column itemno
My target side structure (idoc to jdbc scenario is as follows)
I have mapped the E1EDP01 to Statement - I thought this will build one query per line item (per occurence of E1EDP01) but this is not working.
MT_OITEM
Statement
 dbtablename ============> SalOrdItm
 action =================> Insert
 table
 access
 Itemno (this is one of the columns from the table)
The occurence of E1EDP01 is 0..9999999 while the occurence of Statement node is 1...unbounded.
Please is there any email address where I can send you screen shots if the above is not clear.
I need to get this interface delivered as soon as possible but am STUCK.
Edited by: gary jojo on Dec 6, 2011 3:06 PM

IDOC to File Scenario - Configuration steps need to be done in R3 and XI

Hi Experts,
I am working with IDoc to File scenario. Can someone please explain, what are the steps or configuration things need to be done in R3 and as well as in XI too.
Thanks in advance.
Regards,
Sree

Hi Sree,
I thought i will just share a few basic thoughts that you need to take care while doing an IDOC to File Scenario. Just see if it helps you in anyways.
While doing an IDOC -> XI -> File scenario, The Points to noted are:
1. You dont need a DT, MT or a message interface for the IDOC as it itself acts as the Message Interface.
2. You import the IDOC and use the same in your mapping.
3. In this configuration note that you dont have a sender agreement as you dont have a sender IDOC adapter.
If it is that you wanted to send an IDOC from XI (File to IDOC) , then in this case:
points 1 and 2 will remain, but the 3 will not. You will need a sender agreement for the file and a receiver agreement for the IDOC.
IDOC -> File scenario ref:
<a href="/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters scenario</a>
File -> IDOC ref:
<a href="/people/anish.abraham2/blog/2005/12/22/file-to-multiple-idocs-xslt-mapping to IDOC</a>
To be able to trigger your IDOC from the SAP ISU system, you will have to set the partner profile in we20. Select your Business System (mostly under Logical system) and then create Outbound entries for whichever IDOC you want to trigger.
You define your basic type also in your partner profile settings, Please go thru the following links to get a better idea about partner profile:
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b833243d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b7cd343d711d1893e0000e8323c4f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/32/692037b1f10709e10000009b38f839/content.htm
http://help.sap.com/saphelp_nw04/helpdata/en/5e/b8f8bf356dc84096e4fedc2cd71426/frameset.htm
Also, I would suggest that you go through this blog by michal if any issue arises,
/people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions
Also have a look at these forum threads...
IDOC TO FILE SCENARIO
idoc to file scenario
I hope this answers your query.
Regards,
Abhy Thomas

How To Test Idoc To File Scenario in ID From Tools- Test Configuration

Hi All,
Can any body help me in step by step process including screenshots for testing Idoc to file scenario in integration directory from tools->test configuration.
My scenario is passing the PO Idoc data from R/3 into a file using XI.
i have processed the idoc from R/3 and now i went to sxmb_moni in XI system and took the payload xml data.
In ID I have navigated to test configuration from tools then i have provided the following information.
Sender Service : Business system of R/3 b'coz here R/3 is the sender.
Sender Interface : ORDERS.ORDERS6
Receiver Service : Business system of XI b'coz here XI receives the data and places it into a file
In payload text box i have copied the xml code which i have taken from sxmb_moni and clicked the run button. then i got the following error:
Sender Agreement
Internal Error
 HTTP connection to ABAP Runtime failed.
 Error: 403 Forbidden
 URL: http://bxdci.boewe.custservice.de:8093/sap/xi/simulation?sap-client=100
 User: PIDIRUSER
Kindly look into it and correct me if iam wrong or is there any other way to test this scenario in ID please suggest.
Thanks & Regards,
Venkat

Hi Venkat,
Specify the test confisuration as follows.
Sender
Service : Business System of SAP R/3 System
Interface : The outbound message interface name of type the IDOC.
Namespace : will automatically loaded when u select the Interface. Check if it the correct namespace.
Receiver:
Service : Business System name for the Fle system.
Paste the payload that u copied from the sxmb_moni.
Now click on Run and test ur Scenario.
Was the scenario sucessfull in the Message Monitor.
Regards
Santhosh

Configuring IDOC to file Scenario in PI 7

Hello All,
I am doing an IDOC to file scenario, all the configuration is done. When i trigger the outbound IDOC, I can see in SXMB_MONI the sender component, sender Namespace, sender interface and reciever component are coming up correctly as configured.
1. But the reciever namespace and Reciever Interface are having the same values as the sender namespace and sender interface interface respectively. I am sure they have to be as per the config in ID.
2. Also on further going into the error message
SAP:Code area="OUTBINDING">CO_TXT_OUTBINDING_ERROR</SAP:Code
SAP:AdditionalText>No standard agreement found for , DEV400, ANZ, BC_RECV_PAYM_ORD, urn:sap-com:document:sap:idoc:messages, PAYEXT.PEXR2002</SAP:AdditionalText>
Can anyone please suggest , what is it that I am doing wrong.
---Prashanth

Hi,
Please delete the Receiver determination and try creating again. refresh cache.
Can you please have a look at the sap notes if of any use .. i think its a different case altogether , but pls have a look.
SAP Notes 1278244- https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1278244
SAP Note 1284103 -https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1284103
Regards,
Srinivas

Use of Orders05 Interface mapping & XSLT mapping file for Orders03 IDOC

Hello Experts,
In a scenario we are sending Purchase orders and Purhase Order change from SAP to SNC through XI.
Currently Orders03 IDoc is used and standard mapping for Orders03 XSLT is used.
Now the requirement is to use the same IDOC (Orders03) but
- XSLT mapping (OrdersOrders05_ReplenishmentOrderNotification) and
- Interface Mapping (OrdersOrders05_ReplenishmentOrderNotification_01) of Orders05.
What changes would be necessary
- On SAP side,
- in the XSLT mapping, and
- On XI side.
Thanks in advance,
Suraj

Hi Suraj,
First compare ORDERS03 IDOC and ORDERS05 IDoc structures,if both structures are same then u no ned to chnage the XSL it will work fine.
If any chnages in ORDERS05 Idoc then u have to adjust XSLT as per ORDERS05 IDOC.
test interface mapping first and let me know if any error.
Regards,
Raj

Sender Namespace and Sender Interface in the IDOC to IDOC scenario

My question maybe very basic...
It is SAP IDOC to SAP IDOC scenario.
Lets assume that I have done config in XI for:
 Sender = A,
 Interface = B,
 Namespace = C.
My question is:
Is there a place in the source system or somewhere to point that
when an IDOC e.g. DEBMAS is triggered in the source system,
then the Interface should be B and Namespace should be C in the xml file ?
Cheers
Agnie

Hi Agnieszka,
 Check these threads/blogs from you may get some help:
/people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
Idoc-to-idoc scenario
IDoc to IDoc scenario necessary configuration steps
For A-Z help on IDOC, you can refer Michal's book:
<a href="/people/michal.krawczyk2/blog/2006/10/11/xi-new-book-mastering-idoc-business-scenarios-with-sap-xi IDoc Business Scenarios with SAP XI</a>
Regards,
Subhasha Ranjan

Error in Operation Mapping for Idoc to File Scenario

Hi Experts,
I am doing Idoc to File Scenario for Timesheet IDoc "HRSM_C" and following step are through,
Sender agreement --> Receiver Determination --> Interface Determination
got stuck in Operation mapping, it sahows error
"Unable to find resource 193c0e01-bd37-11dd-850c-d879ac131b1f in the following software component versions: http://clarityPOCcom/sap/xi/tf/_MM_Timesheets_iDocToFile_.class-1"
Also not all the fields of IDoc HRSM_C are transferred to the XI server as I am unable to see all the fields in xml file using transaction idx5, as I suppose the reason behind may be there are no values in those fields.
Please suggest how to resove the issue and transfer all the fields from R3 to XI in Idoc eventhough it doesn't contain any value.

Hi
Refresh CPA cache using user PIDIRUSER.
Look Note 951318 for Mapping Cache Refresh.

Pass through scenario in SAP PI with no mapping for File to IDoc and Idoc to file scenarios

Hi Experts,
Can i have step by step process in SAP PI for pass through scenario with no mapping in case of file to Idoc and Idoc to file both cases please.
What objects i can skip.
My PI system is 7.3 dual stack.
I have seen below blogs, still its confusing to me.
When and how to create an scenario in SAP PI without mapping objects.
Pass Through Scenario with no Mapping in PI 7.1
Appreciate your help on this.
Regards,
Mohan.

Hi Mohan
In pass thru interface you don't need to create any ESR objects, only ID objects are required.
Just Create a Receiver Determination and Receiver Agreement for your scenario (no need for Interface Det. and Sender Agreement).
Specify the IDOC in the Sender Interface and namespace as urn:sap-com:document:sap:idoc:messages
Or instead of creating objects manually, Run the wizard with Idoc name/namespace in sender/receiver interface
Regards
Osman

** Interface Mapping - No Objects Found - IDoc is receiver

Hi Friends,
In our scenario, sender is File & receiver is IDoc. For each record in file, we need to created one IDoc. IDoc is CREMAS.CREMAS05. For this as usual we exported XSD and changed the occurrence of IDOC node as minOccurs="0" maxOccurs="unbounded" (as explained in Michael Blog - 2762) and did the message mapping successfully.
While create Interface Mapping, (Message interface (OB) for File, no message interface for IDoc, we directly use CREMAS.CREMAS05 in the target interface) and 'Read Interfaces' and select the Message Mapping option' it shows 'No Objects Found'. What could be the problem ?
Note that earlier it was working fine (Some times ago), now it is showing this error 'No Objects Found". I am very confused why this error is coming.
Kindly help me friends, to solve this.
Kind regards,
Jegathees P.

Friends,
Thanks for all your reply. When we click Read messages button automaticlly our source message (type) and target message (type) will be selected. Then, we select Mapping Program which is suitable for the Source & Target Message. When we do like this, it is showing the error 'No Objects Found'.
I want to check with you Is this due to what reason ? (Because, earlier it was working fine)
Eventhough we select 'Any' to 'Any' and select the mapping, save. After that If we do consistency check , it will show an warning message about the namespace issue.

Mapping issue in idoc to JDBC scenario

mapping issue in idoc to JDBC scenario
source structure
E1KNB1M
BUKRS = 1000
E1KNB1M
BUKRS= 9000
E1KNB1M
BUKRS= 2000
THE NODE E1KNB1M is repeated many times and the field BUKRS is also repeated with E1KNB1M as above
TARGET field : ISFRANCHISE
if any where value of BUKRS =9000 we have to pass Y to the target filed, else N
if BUKRS = 9000   THEN ISFRANCHISE= Y
               ELSE
            ISFRANCHISE=N
I've done the mapping as below
BUKRS = 9000--> IF THEN Y ELSE N--
> ISFRANCHISE
BUT everry time the target value is N only
pl suggest
rgds
mojib

mapped like this
BUKRS--->SORT---->
                                             EQUALS --------IF---THEN    Y
9000------------------------>                                               ----------------->ISFRANCHISE
                                                              ELSE   N
context of BUKRS set to parent node
its worked
thanks to all for valuable suggestions
rgds
mojib

Mapping Error- In IDoc to File scenario

Hi Experts,
Got the Mapping error for one interface (IDoc to file). After comparing with successful message found that the field value (TDLINE) is not availbale in first segment (E1EDT10) in idoc for this failed one.
Mapping is :
TDLINE -- Exists --- Creatif --- Receiver field(in the file)
But here due to the the empty value in first segment the message is failed in XI system, next segment values is not trasmitted to the recever end(maping is the same above). To overcome this issue please suggest the suitable mapping design in IR.
Regards
Mahesh

Hi,
After your CreateIf, use a "IfWithoutElse" by selecting the properties "Keep SUPPRESS Values". To do that, do a right click on IfWithoutElse, choose "Properties".
With this option, you will keep the fact that you have nothing in the source, and so the target context will have a "SUPPRESS" line. I have not THE solution, so do your own test.
If it's not enough, see also about the "mapWithDefault" (but that depends of your real rule).
Regards.
Mickael

Questions to a Mapping for IDOC-to-File Scenario

Hi all,
I want do develop a Message-Mapping for an IDOC-to-File Scenario. A SAP System sends an IDOC to the XI-System and the XI-System should make a mapping an send a XML-File to a FTP-Server. The Strukture of the target message is very easy:
<xdoc>
 <Invoice>
 @purno
 <HeaderInfo>
 <invno/>
 <shipdate/>
 <extvalue/>
 </HeaderInfo>
 <DetailInfo>
 <LineItem>
 @lineno
 <vpartno/>
 <descrip/>
 <qtyord/>
 <cost/>
 <vendmemo/>
 </LineItem>
 </DetailInfo>
 </Invoice>
</xdoc>
The source message is an IDOC. This IDOC can contain one or more positions (E1EDP01). Those different positions should be mapped into different LineItem's (see target structure) -> so in the target file one or more LineItems can appear.
Is it possible to implement this process with a common message-mapping or have I to implement a business process?
Thanks
with best regards
Christopher

Hi Christopher,
Is it possible to implement this process with a common message-mapping or have I to implement a business process? - This thing is possible with common message mapping......you dont need business proces for it.......in msg mapping after taking the source IDOC and target xml struc, map the E1EDP01 field to LineItem field.......just check the occurance of these nodes.....it should be 0..unbounded.........so as many E1EDP01 nodes will be there in idoc, that many LineItem nodes in target will be created.......
Thanks,
Rajeev Gupta

Context handling in message mapping for an IDoc to File Scenario

Hi,
Can somebody help me with this issue. I have an Idoc to file scenario. heres my idoc structure. Its a custom Idoc
Header (1..1)
Detail (0..Unbounded)
         DependentDetail (0...Unbounded)              Note: This dependentdetail is a subelement of Detail
Trailer(1...1)
I created my target structrure the same way as the Idoc structure.
My output is a simple text file. I need the output in this format
Header
Detail1
   Dependentdetail1
   DependentDetail2
   DependentDetail3
Detail2
   DependentDetail1
   Dependentdetail2
Detail3
Detail4
Trailer
Since the Detail and Dependent Detail records are unbounded .
But right now i m getting my output like this:
Header
Detail1
Detail2
Detail3
Detail4
Trailer
But the DependentDetail record in not showing up in the output file. I didnot do any context change in my mapping. So do I need to do any context handling??...If so can somebody explain me with this.
Thanks,
Adam
Edited by: hymanroth on Apr 29, 2011 11:11 PM

Thanks Kenneth foryour quick reply,
Yes, I see the payload for Dependent detail in SXMB_MONI. So as you said earlier there's a problem with my content conversion.
my content conversion is as follows:
Header.fieldNames
Header.fieldFixedLengths
Header.endSeparator
Detail.fieldNames
Detail.fieldFixedLengths
Detail.endSeparator
DependentDetail.fieldNames
DependentDetail.fieldFixedLengths
DependentDetail.endSeparator
Trailer.fieldNames
Trailer.fieldFixedLengths
Trailer.endSeparator
So As I told earlier. With the above content conversion. I am not able to get the Dependent detail record in my output file. So If there is a change in my content conversion can u check it and tell me where I went wrong.
Thanks,
Harsh
Edited by: hymanroth on May 2, 2011 7:03 PM

Idoc to edi scenarios (mapping help is required)

hi expects ,
    i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
INPUT IDOC :
                    Name                         M/C     Min Use      Max Use        Description
INPUT*                                              M               1           1
Record EDI_DC40*                                 C               0           1                       Control Record
Record E2EDK01*                                  C               0           1                       Document Header General Data
     Record E2EDK14*                                  C               0          12                       Header Organizational Data
     Record E2EDK03*                                  C               0          10                       Header Date Segment
Record TEMP_DATE*                                C               0           1                       Temporary Date Segment
     Record DEL_DATE*                                 C               0           1                       Temporary Date Segment
     Record E2EDK04*                                  C               0          10                       Header Taxes
Record E2EDK05*                                  C               0          16                       Header Conditions
Record E2EDKA1*                                  C               0       99999                       Header Partner Info
Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info
Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info
Record TEMP_PAYER*                               C               0           1                       Payer Info
Record TEMP_CARRIER*                             C               0           1                       Carrier Info
Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info
     Record TEMP_NOTIFY*                              C               0           1                       Notify Info
Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info
Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info
Record TEMP_CONSIGNEE*                           C               0           1                       Consignee
Record TEMP_SHIPPER_INFO*                        C               0           1
Record E2EDK02*                                  C               0          10                       Header Reference Data
     Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02
Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING
Record E2EDK17*                                  C               0         999                       Header Terms of Delivery
     Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms
     Record E2EDK18*                                  C               0          99                       Header Terms of Payment
     Record TEMP_TERMS*                               C               0           1
Record E2EDK35*                                  C               0          10                       Additional Data
Group E2EDKT1:2*
OUTPUT FIELD:
Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION
     Segment B2A*                                     C               0           1                       SET PURPOSE
Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment CUR*                                     C               0           1                       CURRENCY
Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE
     Group DTM_GROUP*                                 C               0           1
Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE
Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE
Segment DTM:3*

Hi,
To do the mapping,,,,even you can go for graphical mapping....
But some of the context handling issues you need to deal with,
like....
1.Never map set context of source fields to element level but Segment level.
2. Always you need to check for qualifiers while mapping it to Traget field.
Thanks & Regards
Akshay.
Dont Forget TO Give Points.

IDoc to IDoc Scenario - Correct Interface Mapping configuration

Similar Messages

Maybe you are looking for