Abap mapping - pb on SAP example?

Question

Hi,
I try to use an Abap mapping for flow "IDoc -> XI -> structured file". For that I have modified the 1st example of SAP (by changing line: "direct = 1").
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to convert between idoc and xml in xi 3.0.pdf
But when I send an IDoc from R/3, I have this error in Message Monitoring: <i>"Error in mapping program YCL_AM_DE00109 (type R3_ABAP, kernel error ID UNCAUGHT_EXCEPTION)"</i>.
In fact, it seems that problem is when I get data from field "TABNAM":
* Control data: segment EDI_DC40
  data: el_element type ref to if_ixml_element.
  el_element = idocument->find_from_name( 'TABNAM' ).
  ls_edidc-tabnam = el_element->get_value( ).  "<<<
1. Is there the good example for such a flow?
2. Anybody have an idea to solve that?
Regards.
Mickael

Answer 1

Hello,
@Stefan: I need this lookup e.g. for outbound processes for some conversions / setting dynamic parameters depending on the RCVPRN inside an IDoc. That means I have a unique key (RCVPRN_<messageType>) and some (4-6) additional information (e.g. mail subject, FTP filename,...) to this key whch I would like to access during mapping runtime. Vice versa, for inbound scenarios, inside a EDI -> IDoc mapping, I need at least a simple "FixValues" translation from some kind of EDI partner id into the corresponding SAP customer number.
@all: So from my experience value mapping does not realy fit this "translation" needs? There are some disadvantages, for example if both input values "A" and "B" should be translated into "1", this is not possible, as the keys have to be unique in both directions.
By the way, I have now also implemented the RFC lookup in my mapping as alternative to the JDBC lookup. To me there are at first sight some pros and cons:
- Pro: You just need a "simple" RFC user within the RFC channel. You do not need to use the PI system user / pw which owns the Z table.
- Con: If you select more than one field from the table, the RFC lookup function return all fields of the db entry just separated by a delimiter, which is why you need to implement some "parsing" of the fields in a UDF (minor disadvantage).
Still interesting discussion!
Thanks,
Christoph