cancel
Showing results for 
Search instead for 
Did you mean: 

RFC Lookup in XSLT Mapping

Former Member
0 Kudos

Hi,

I am trying to do RFC Lookup in XSLT.

I got this excellent mapping tool here at sdn:

RFC Lookup by Thorsten Nordholm Søbirk

But I am having problems when I uses this in a multi-record mapping. (many-to one) with lookup for every element.

Has anyone done IDOC with XSLT and RFC lookup (PI 7.11) ? Can you share the XSLT or experience?

Thx for sharing

Accepted Solutions (0)

Answers (2)

Answers (2)

former_member190389
Active Contributor
0 Kudos

Hi,

Can you post your source and target structure?

holger_stumm2
Active Contributor
0 Kudos

Hi @ Fariah Ali

here is the mapping:

Inbound: IDOC HRMD_A07 (from ALE replication)

We only want to have Infotypes IT0001, IT0002, IT0050

Outbound:

<?xml version="1.0" encoding="utf-8"?>

<mt_I004_Time_Stammdaten>

<Datensatz>

<PersNr>PERSNR</PersNr>

<Name>ENAME</Name>

<Eintrittsdatum>BEGDA</Eintrittsdatum>

Austrittsdatum>ENDDA</Austrittsdatum>

<BeschArt/>

<Gueltigkeitsdatum/>

</Datensatz>

</mt_I004_Time_Stammdaten>

thx holger

rajasekhar_reddy14
Active Contributor
0 Kudos

The code what you have written may be not meeting your requirement,

i wondering why you want do RFC look up through XSLT,in PI7.11 you can do it using mapping function only,they approch what you are following will cause performce issues.

Regards,

Raj

holger_stumm2
Active Contributor
0 Kudos

Hi Raj,

thanks for answering.

I am using XSLT, because it is much more elegant and structured than graphical mapping.

In a larger group of developer and administrators, XSLT also makes maintenance and documentation more easy than a proprietary mapping tool.

If you have to do complex tasks and handles a lot of empty segments, than graphical mapping leads to unreadable structures.

And there is a personal point of view: I am a programmer and don't like to doodle spaghetti-diagrams .

I still doubt the performance considerations: In my cases, XSLT always won hands-down.

thx holger