IDoc to IDoc Mapping

Hi ,
I am new to SAP PI. We are using B2B scenario in office. We are getting ALE idoc from one system and generating idoc to receiver system inbetween we need to map the fields by using PI. Please help me on this, How to Map the idoc fields in PI?
Thanks in advance.

Hi,
Can you explain what type of IDOCs you are using. And also you specified that its a B2B scenario, but you are having 2 R/3 systems on both sides right?
Specify the type of business scenario.
Thanks,
Anudeep.

Similar Messages

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

IDoc to IDOC, Message Mapping settings

Hi!
I am going to implement IDoc to IDOC scenario.
The IDOC should be send from SAP ECC 6.0 system, client 100 to the same system in client 200 via SAP XI.
I have chosen the message type MATMAS05.
Questions
- What is the minimal message scenario (MATMAS:MATMAS05 to MATMAS.MATMAS05) in message mapping?
- when I change some mapping attributes do I need to activate the other related objects (e.g. Interface Mapping, etc.)?
My problem is that the IDOC will be received in SAP XI, but has the following error:
Error: must node 'E1MARAM' failed in structue MATMAS05
How can i correct this error?
Thank you very much!
regards
Holger

Hi Holger,
> * What is the minimal message scenario (MATMAS:MATMAS05 to MATMAS.MATMAS05) in message >mapping?
No Mapping at all or a direct 1:1 connection of all corresponding fields.
> * when I change some mapping attributes do I need to activate the other related objects (e.g. Interface >Mapping, etc.)?
You only have to activate objects that you changed - so no.
From the error I guess that a node in the target structure is not created although the idoc-definition states it as mandatory.
Do you really need the mapping? Does the incoming IDoc also miss the Node?

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

>so i cant use apply control rec values from payload.........
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

PI EDI help: What is the source of ISA13 in a IDOC to EDI mapping

Hello Experts,
It would be of great help if you can provide the field mapping for ISA 13 in outbound from IDOC sceanrio:
IDOC: INVOIC02 - to - EDI 810 mapping.
Is it the best practice to have ECC send the value in a particular IDOC field ( like RFINT) or PI has to use a custom function to populate the ISA13 field.?
Thank you,
Patrick.

Hi,
ISA13 is for Interchange Control Number. It is a control number assigned by the interchange sender.
Normally its Sequential number starting with 000000001 and incremented by 1 for each subsequent ISA between sender and receiver.
This is a very useful value to include. It creates an explicit link between the IDoc and the EDI transmission. This number eases Production Support greatly. When there's an issue with a Partner EDI transmission, the Partner's EDI support people want to know the Interchange Control Number
The IDoc interface does not process or check this field.
regards
Ganga

Mapping IDOC to IDOC

We are receiving The CREMDM idoc from one XI system to another XI system and are required to pass this IDOC to SAP R/3. Is there a simple method to map all fields from one IDOC message to the same IDOC and pass into SAP R/3. We are creating a function module on R/3 to process the inbound CREMDM idoc

Hi Robert,
As Amir said if you have same idoc(1:1 mapping) you do not need a mapping.
Also in addition to this in case if you want to mapped only few segment which is having same field name, there is a button "Map selected fields and substructure if names are identical" in mapping. You need to select a segment from source and target and click on this button. It will auto-map all fields from source to target which having same name.
Hope this will help.
Nilesh

Idoc - to - JDBC mapping..

Can any one help me on step-by-step Idoc to JDBC mapping ..

Check this link for jdbc receiver adapter. and follow the instructions. If you need more assistance let us know with your requirement
For configuring JDBC adapter
http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
For creating jdbc structure on the inbound side
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

Retreive IDOC number and map it to a field in Target XML

Hi Experts,
IDOC to file scenario
I have a requirement where I have to retreive the number of the IDOC generated and map it to a field ID in the target XML.
Do i have to use a UDF for this? can ne one pls explain?
Regards,
Teja

Hi Ravi,
You dont need use a UDF for this.
this is a very simple requiremen.
You can get the IDOC number from source IDOc
under EDI_DC40 node field name DOCNUM.
This DOCNUM fielsd will contain the IDOC number
Map this DOCNUM field from source IDOC to target XML structure.

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>

XI IDoc ASC X12 mapping

Hi
I would like to know more abt your IDoc and X12 implementation. I am in the beginning stage of IDoc - X12 implementation using XI. We don't have the adapter yet. Which adpater is good Seeburger or some thing else. I would like to know deatils abt imlementing in seburger.

Hi ram .
R U looking for EDI or IDOC ...?
See burger is for EDI (the only XI support as of now as per my knoweldge)not for IDOC.
and IDOC adapter is inbulit in XI.
It will be nice if u tell the scenaro looking for.
thanx & regards
Vinod Ahir

Issue in IDOC-XI-IDOC scenario

Hi,
We are facing a strange issue in an IDOC-XI-IDOC scenario. We are using a SAX parser to parse the code here.
The error we are getting in 'sxmb_moni' is
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS</SAP:P1>
<SAP:P2>java.lang.RuntimeException</SAP:P2>
<SAP:P3>For input string: ""</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/abc/def/dev/sapxi/clfmas/Idoc2IdocMapperCLFMAS a java.lang.RuntimeException was thrown: For input string: ""</SAP:Stack>
The strange thing is, when I restart the message, it gets processed successfully. Also, when I copy the payload, and test the same on a different environment, it gets processed successfully.
Would really appreciate some pointers here!
cheers,
Prashanth

Hi,
This related to mapping error check it once again.Check in Interface mapping Test tab.see the result.check the sxmb_moni and get the source of mapping come back to interfcae mapping and test .
See the below links
Hi I got EXCEPTION_DURING_EXECUTE in RWB->Message Monitoring
I am getting MAPPING EXCEPTION_DURING_EXECUTE
EXCEPTION_DURING_EXECUTE- Error in Mapping. Doubt about IE and AE
EXCEPTION_DURING_EXECUTE
Mapping problem - EXCEPTION_DURING_EXECUTE
ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION
Regards
Chilla..

Sender port is not picking in PI for idoc to idoc scenario

Hi Guru's,
i am doing idoc to idoc scenario passing through sap pi ,while executing this idoc from client1 is successfully coming to PI, but while going from PI to client2 , i am getting error 51 (company code is defined for LS(logical system) for 1000 (vendor),i checked the configurations for sender idoc from pi ,it is taking a port value which is not present neither in xi nor in r/3 it is MDM interface port value i tried makking the port value constant in PI mapping ,but still same error is comming.
idoc created with partner type LI in source system.i am posting it as LS in receiver system.
Please help me in resolving this error.
Regards,
reddy

Hi,
The error mentioned by you is not related to the port..but its related to the Application ...
IDoc 51 means idoc has been received in R/3 client and when it tries to process it ended in error..
Check with the functional consultant for the error you have received..
HTH
Rajesh

Adapter module in PI 7.1 EhP1 for Falt File Idoc to Idoc xml transformation

Hi Experts,
In PI 7.1 (EhP1) there is a java adapter module that can be added to the file adapter that automatically transforms Flat File representation of IDoc to IDoc XML. Can anyone provide the link to this particular module? Tried searching but could not get the specific module name or parameters.
The same conversion can be achieved using a standard SAP provided ABAP mapping but we need to use the module in this case.
Thanks and regards,
Shiladitya

/people/william.li/blog/2009/04/01/how-to-use-user-module-for-conversion-of-idoc-messages-between-flat-and-xml-formats
FYI~~~

IDoc Packaging in IDoc 2 IDoc Scenario

Hi every one,
Can anyone please throw some light on the following:
Use of Idoc packaging in an Idoc2Idoc scenario. I dont have any clue about this.
Reg,

This should be rather straight forward, if you are using XI to pass IDocs from system to system then you actually don't really have to do any mapping. There are some other good discussions on this topic:
idoc to idoc
IDOC packaging
Re: IDOC to IDOC Scenario
This is a good document on the topic:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cdded790-0201-0010-6db8-beb9bb2b2660
You can import the IDoc data types and go about creating the rest of your scenario, usnig the IDoc adapters and ALE
I would definitely also check out this document on configuring the IDoc adapter:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e098

IDOC - XI - IDOC with strange Config , Still working . Please comment !

I am having an running IDOC interface in Production ...
whose SAP XI Config looks strange to me ...
This Interface is IDOC - XI - IDOC
On receiver IDOC adapter ... following Options are checked...
1. APPLY CONTROL VALUE FROM PAYLOAD
2. TAKE SENDER FROM PAYLOAD
3. TAKE RECEIVER FROM PAYLOAD.
So all three Options are checked , But Now the strange thing is in Mapping ...
When I look into the Mapping ...
Sender IDOC to Receiver IDOC
Sender IDOC is different from Receiver IDOC ..
In Control Record ( EDIDC_40)
TABNAME IS MAPPED WITH TABNAME
DIRECT IS MAPPED WITH DIRECT
IDOCTYPE IS MAPPED WITH IDOCTYPPE
MESTYPE IS MAPPED WITH MESTYPE
SNDPRN IS MAPPED WITH CONSTANT HAVING SAP XI SYSTEM RELATED VALUES
SNDPOR IS MAPPED WITH CONSTANT HAVING SAP XI SYSTEM RELATED VALUES
SNDPRT IS MAPPED WITH CONSTANT HAVING SAP XI SYSTEM RELATED VALUES
RCVPOR IS DISABLED
RCVPRN IS DISABLED
So now my Query are :-
1. IF RCVPRN/ RCVPRN is disables ... How interface is still working as TAKE RECEIVER FROM PAYLOAD Option are checked , still that interface is working ... ??????????
2. IF Receiver DOCTYPE / MESTYPE IS MAPPED WITH Sender DOCTYPE / MESTYPE, How it is getting Correct values .. if both Sender and receiver IDOC are Different????
Please make Comments !
Regards
PS

Hi,
IDoc control record will get generated by the XI runtime and there are certain fields which cannot be controlled using mapping for e.g. in your case disabling of RCVPRN ..if you disable this field stil the value will be generated and passed to the receiver system...
To check what exactly idoc values are passing then go to MONI and check there under Response ->IDoc Outbound which displays the control record values passed exactly...
HTH
Rajesh

IDOC to IDOC Error

Hi ,
I am doing an IDOC to IDOC scenario. Idoc from source system is successfully sent to xi and xi is able to delivery the idoc to the target system. When the idoc is posted to target system the status is 64 IDoc ready to be transferred to application. When I run the RBDAPP01 report it is giving me dump. Find below the dump
Can any one throw some light on it please?
Runtime Errors GETWA_NOT_ASSIGNED
Date and Time 28.09.2007 09:28:27
 Short text
 Field symbol has not yet been assigned.
 What happened?
 Error in the ABAP Application Program
 The current ABAP program "SAPLHRALX00_INTEGRATION_PERSON" had to be terminated
 because it has
 come across a statement that unfortunately cannot be executed.
 Error analysis
 You attempted to access an unassigned field symbol
 (data segment 32785).
 This error may occur if
 - You address a typed field symbol before it has been set with
 ASSIGN
 - You address a field symbol that pointed to the line of an
 internal table that was deleted
 - You address a field symbol that was previously reset using
 UNASSIGN or that pointed to a local field that no
 longer exists
 - You address a global function interface, although the
 respective function module is not active - that is, is
 not in the list of active calls. The list of active calls
 can be taken from this short dump.
 Trigger Location of Runtime Error
 Program SAPLHRALX00_INTEGRATION_PERSON
 Include LHRALX00_INTEGRATION_PERSONF52
 Row 486
 Module type (FORM)
 Module Name IDOC_CONVERT
 Source Code Extract
 Line SourceCde
 456 add_idoc_msg ct_idoc_errors <ls_segment>-docnum <ls_segment>-segnum gc_idoc_warn
 457 'RH_ALEOX_INTG_CP_IDOC_1' 'IDOC_CONVERT/MAPPING'.
 458 CLEAR <ls_segment>-segnam.
 459 CONTINUE.
 460 ENDIF. "mapping
 461
 462 ELSEIF <ls_e1pad31>-sclas = gc_quali AND
 463 <ls_e1pad31>-otype = gc_pernr AND
 464 <ls_e1pad31>-relat = gc_q_cp_subty+1.
 465
 466 <ls_e1pad31>-otype = gc_cpers.
 467 <ls_e1pad31>-objid = <ls_mapping>-objid.
 468
 469 PERFORM idoc_convert_1001_q USING <ls_segment>
 470 CHANGING et_e1p1001_q
 471 et_refobj_q.
 472 PERFORM idoc_convert_5586 CHANGING <ls_segment>.
 473
 474 ENDIF.
 475 * -
 476 WHEN gc_e1p0000.
 477 * -
 478 PERFORM idoc_convert_pa_infty USING gc_cpers
 479 <ls_mapping>-objid
 480 '5580'
 481 space
 482 <ls_mapping>-begda
 483 'E1P5580'
 484 CHANGING <ls_segment>.
 485 * -
 >>>>> WHEN gc_e1p0001.
 487 * -
 488 APPEND <ls_segment>-sdata TO lt_segment_0001.
 489 PERFORM idoc_convert_pa_infty USING gc_cpers
 490 <ls_mapping>-objid
 491 '5581'
 492 space
 493 <ls_mapping>-begda
 494 'E1P5581'
 495 CHANGING <ls_segment>.
 496 * -
 497 WHEN gc_e1p0002.
 498 * -
 499 APPEND <ls_segment> TO lt_segment_0002.
 500 PERFORM idoc_convert_pa_infty USING gc_cpers
 501 <ls_mapping>-objid
 502 '5582'
 503 space
 504 <ls_mapping>-begda
 505 'E1P5582'
Thanks
Mohammad

Hi Mohammad
you should post in the ABAP forum, there is a quick, good answer expectable.
Regards,
Udo

IDoc to IDoc Mapping

Similar Messages

Maybe you are looking for