Help needed in XSLT MAPPING with RFC function module

null
Edited by: Ram Kishore on Sep 25, 2009 1:09 PM
Edited by: Ram Kishore on Sep 25, 2009 1:10 PM

Hi Arunava,
If you dont have any key field in ItemData1 and ItemData2 in the incoming flat file, then you have to insert a keyfield in both the ItemData1 ,ItemData2 .
For this ,you need to use ItemData1.keyFieldValue and ItemData2.keyFieldValue in your FCC parameters.
Also, need to mention the keyFieldName in both ItemData1 ,ItemData2.(ex:ItemData1.fieldNames).
Hope the below blog would help you.
/people/sukumar.natarajan/blog/2007/06/12/content-conversion-in-sender-file-adapter--2-new-useful-parameters
Regards,
Swetha.

Similar Messages

Collection problem with RFC function module WSDL.

Hi.
I have developed an RFC function module in a SAP system version 4.7 (WAS 620). This FM has 2 table parameters. I have no problem when I see the WSDL in the SAP Web Service Browser.
Another team is trying to consume this RFC FM as a web service from a Java application but they say they can't see the table parameters as collections.
Here is the WSDL of the FM, the table parameters are T_MOVIM and T_ERROR:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:s0="urn:sap-com:document:sap:rfc:functions" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" targetNamespace="urn:sap-com:document:sap:rfc:functions">
     <types>
          <xsd:schema targetNamespace="urn:sap-com:document:sap:rfc:functions">
               <xsd:element name="ZMMFUSAPTK_0001">
                    <xsd:complexType>
                         <xsd:all>
                              <xsd:element name="GENIDOC" minOccurs="0">
                                   <xsd:simpleType>
                                        <xsd:restriction base="xsd:string">
                                             <xsd:maxLength value="1" />
                                        </xsd:restriction>
                                   </xsd:simpleType>
                              </xsd:element>
                              <xsd:element name="T_ERROR">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                              <xsd:element name="T_MOVIM">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:all>
                    </xsd:complexType>
               </xsd:element>
               <xsd:element name="ZMMFUSAPTK_0001.Response">
                    <xsd:complexType>
                         <xsd:all>
                              <xsd:element name="CODRET">
                                   <xsd:simpleType>
                                        <xsd:restriction base="xsd:string">
                                             <xsd:maxLength value="1" />
                                        </xsd:restriction>
                                   </xsd:simpleType>
                              </xsd:element>
                              <xsd:element name="T_ERROR">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0012" />
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                              <xsd:element name="T_MOVIM">
                                   <xsd:complexType>
                                        <xsd:sequence>
                                             <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="s0:ZMMTASAPTK_0011" />
                                        </xsd:sequence>
                                   </xsd:complexType>
                              </xsd:element>
                         </xsd:all>
                    </xsd:complexType>
               </xsd:element>
               <xsd:complexType name="ZMMTASAPTK_0011">
                    <xsd:sequence>
                         <xsd:element name="REFERENCIA" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="10" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="FECHACONT" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="8" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="FECHADOC" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="8" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CODMOV" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="2" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="NROPLAN" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="12" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="NROCOMP" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="10" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CLASEMOV" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="3" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CENTRO" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="4" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="ALMACEN" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="4" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MATERIAL" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="5" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="LOTE" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="10" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CANTIDAD" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="15" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MOTIVOMOV" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="4" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CENTROREC" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="4" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="ALMACENREC" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="4" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CENTROCTO" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="10" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="ORDEN" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="12" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="TIPOSTK" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="1" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="NROPEDIDO" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="10" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CODCISTERNA" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="50" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                    </xsd:sequence>
               </xsd:complexType>
               <xsd:complexType name="ZMMTASAPTK_0012">
                    <xsd:sequence>
                         <xsd:element name="REFERENCIA" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="10" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="CODERR" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="3" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                         <xsd:element name="MSJERR" minOccurs="0">
                              <xsd:simpleType>
                                   <xsd:restriction base="xsd:string">
                                        <xsd:maxLength value="100" />
                                   </xsd:restriction>
                              </xsd:simpleType>
                         </xsd:element>
                    </xsd:sequence>
               </xsd:complexType>
          </xsd:schema>
     </types>
     <message name="ZMMFUSAPTK_0001Input">
          <part name="parameters" element="s0:ZMMFUSAPTK_0001" />
     </message>
     <message name="ZMMFUSAPTK_0001Output">
          <part name="parameters" element="s0:ZMMFUSAPTK_0001.Response" />
     </message>
     <portType name="ZMMFUSAPTK_0001PortType">
          <operation name="ZMMFUSAPTK_0001">
               <input message="s0:ZMMFUSAPTK_0001Input" />
               <output message="s0:ZMMFUSAPTK_0001Output" />
          </operation>
     </portType>
     <binding name="ZMMFUSAPTK_0001Binding" type="s0:ZMMFUSAPTK_0001PortType">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
          <operation name="ZMMFUSAPTK_0001">
               <soap:operation soapAction="http://www.sap.com/ZMMFUSAPTK_0001" />
               <input>
                    <soap:body use="literal" />
               </input>
               <output>
                    <soap:body use="literal" />
               </output>
          </operation>
     </binding>
     <service name="ZMMFUSAPTK_0001Service">
          <documentation>SAP Service ZMMFUSAPTK_0001 via SOAP</documentation>
          <port name="ZMMFUSAPTK_0001PortType" binding="s0:ZMMFUSAPTK_0001Binding">
               <soap:address location="http://dbades00.bue.bemberg.com.ar:8002/sap/bc/soap/rfc" />
          </port>
     </service>
</definitions>
Should I change something in the definition of the parameters of the FM? or the problem is with the parsing process on the other system?
Thanks in advance.
Fabian.

Welcome to SDN.
I am not sure about this particular issue, but i have used WSDL from WAS6.20 system in MS Office infopath to consume webservice where we have had table parameters without any issue.
may be try with office infopath to make sure that the problem is with the WSDL or with the java application.
Regards
Raja

Problem with RFC function module from R/3 to CRM

Hi, i have a RFC function module created in R/3, this is the code:
function Z_CRM_PRODUCTO_INTERLOCUTOR.
""Interfase local
*" IMPORTING
*"     VALUE(GV_VKORG) TYPE VKORG
*"     VALUE(GV_VTWEG) TYPE VTWEG
*"     VALUE(GV_MATNR) TYPE MATNR
*"     VALUE(GV_KUNNR) TYPE KUNNR_V
*" EXPORTING
*"     VALUE(GV_KDMAT) TYPE MATNR_KU
*"     VALUE(GV_POSTX) TYPE KDPTX
*" EXCEPTIONS
*"      NOT_FOUND
UNPACK GV_MATNR TO GV_MATNR.
UNPACK GV_KUNNR TO GV_KUNNR.
select single KDMAT POSTX
          into (GV_KDMAT, GV_POSTX) from KNMT
          where   VKORG = GV_VKORG
                  and VTWEG = GV_VTWEG
                  and KUNNR = GV_KUNNR
                  and MATNR = GV_MATNR.
IF sy-subrc <> 0.
    RAISE NOT_FOUND.
ENDIF.
endfunction.
When i call this function from CRM, i do it like this:
CALL FUNCTION 'Z_CRM_PRODUCTO_INTERLOCUTOR'
DESTINATION LV_RFCDEST
EXPORTING
    GV_VKORG = lv_vkorg
    GV_VTWEG = ORGMAN_H-DIS_CHANNEL
    GV_MATNR = ORDERADM_I_WRK-ORDERED_PROD
    GV_KUNNR = WA_DATOS_PER-N_PAGADOR
IMPORTING
    GV_POSTX = IT_POS_LINE-DESCRIPCION
    GV_KDMAT = IT_POS_LINE-material
EXCEPTIONS
    not_found = 1.
where:
it_pos_line-descripcion type string
it_pos_line-material type string.
Well, my problem is that when debugging, in R/3 the 2 return values have the correct value, but when they are passed to CRM they have only one position.
As i've been told, it was working ok, but it's being wrong since we made a ¿conversion to unicode?. Maybe I should change the type of return ???
Thanks in advance !!!

Hello Maria,
Make sure you define your parameters in CRM exactly the same way as in R3, do not use type string here.
So:
it_pos_line-descripcion type C char 40,
it_pos_line-material type C length 35.
Kind regards,
John.

Facing Problem with RFC Function Module

Hi,
I have created an RFC function module to get some data in table format.
I have run the RFC in original system: It is giving the data.
However, when I run this in target system, It is not giving any values.
Could you please let me know, why it happens? I am not sure where I missed out.
Thanks,
Sandeep

HI,
i hope you are calling the RFC function module in the target system like this
CALL FUNCTION <FUNC NAME> DESTINATION <DESTINATION NAME> . The destination should be logical system name of the source Logical system .
Regards,
Nagaraj

Problem with RFC Function module

Hello All,
I have created one RFC with importing parameters as material and material description.when I pass some value in material desc it always convert into the uppercase.I have one option of checkbox for upper/lower case but i have to do it manually evrytime.Is there any solution for making the material desc as case sensitive or we can make the checkbocxticked permanently?
Regards
Lalit

Hi Lalit,
There is no option for making the input case sensitive .
One alternate can be using "test data directory " but that will not be of much help if you are changing the materail number each and very time.
Better convert the materail number to upper/lower case inside FM using convert to -
Rgds,
Sandeep

RFC Function module-With Only Request message

Hi
i need a RFC with only Request message and Response message is not required.
please help me, how to create a RFC function module with out Response message, and it should contain only Request message.
i have created RFC in this way:
RFC doesn't contain neither import nor export parameters. and i have defined one table in TABLE tab which refers to a ztable created already.
when i imported RFC into XI i came to know that RFC has both Request and Response messages, but i don't need Response message.
Thanks in advance..help would be appreciated
Regards,
Rajesh

Thankx Michal,
I have written ZRFC this way:
insert ZMM_AUTO_GR from INPUT_TABLE .
if sy-subrc = 0.
commit work.
else.
rollback work.
im not using neither import nor export parameters..but using only tables parameters. but when imported in XI im getting same table structure in both request an response.
please suggest what changes required in above code to invoke my ZRFC in async way.
you will not get any response in XI- what chages required in my code to dnt get .reponse in XI.
appreciate your help.
Regards,
Rajesh.

Call RFC Function Module in R/3 via XI during Mapping

Hi,
I have an XI scenario where I have to fill the IDoc ADRMAS03 in XI and send it to R/3. Unfortunately the sender system does not provide the required address number (ADRNR) for the Business Partner, only the Business Partner number. Therefore I want to call a Function Module in R/3 during the mapping in order to get the ADRNR.
Does anybody know which RFC-Function Module I can call in R/3 4.6c providing the Busness Partner number in order to get the ADRNR?
Thanks.
Alex

Hi,
no need for RFC lookup it's better to do as he wants
(inside an exit in R3) - just my point of view
BTW
don't use a FM just find a table with both values
and create a select statement youself
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

A little help needed in message mapping

a little help needed in message mapping
I have to map one of the idoc header segments as many times as it occurs to each Idoc when using the split message funcionality
let us say we have the segment seg1 and there is a QUALF in it
<seg1>
<qualf>001</qualf>
</seg1>
<seg1>
<qualf>002</qualf>
</seg1>
then we use the vbeln to split the idoc into 2.
so if we have
<vbeln> 1 </vbeln>
and
<vbeln>2 </vbeln>
then 2 Idocs should be created like this
<Idoc>
<vbeln> 1 </vbeln>
<seg1>
<qualf>001</qualf>
</seg1>
<seg1>
<qualf>002</qualf>
</seg1>
</Idoc>
<Idoc>
<vbeln> 2 </vbeln>
<seg1>
<qualf>001</qualf>
</seg1>
<seg1>
<qualf>002</qualf>
</seg1>
</Idoc>
it is easy to create the segment by using createif with the QUALF field but my problem how to map the qualf twice for each idoc
Thanks.

UseOneAsMany is the function you need to use.
It takes three parameters:
1 --- The node you want to duplicated
2 --- How many times you want to duplicated
3 --- The context you want to place for it.
Regards
Liang

XSLT Mapping with Java Enhancement

Hi All
I am working on XSLT Mapping with Java Enhancement.
To do this scenario i have followed the following link.
http://help.sap.com/saphelp_nw04/helpdata/en/55/7ef3003fc411d6b1f700508b5d5211/frameset.htm
As per the above link I have created Source and Target Data Types , Message Types , Mesage Interfaces, XSLT Mapping (using the transaction XSLT_TOOL) and Interface Mapping part and configred a simple file to file scenario in the ID part.
Apart from this I have wirte the java code, compile the java code, create the jar file using .java and .class file and after creating the jar file import the .jar file in the imported archive of the IR..
when I am trying to execute the scenario I am getting the successful message in SXMB_MONI but the target file is having the payload as given below.
<?xml version ="1.0" encoding="UTF-8"?>
<name xmlns:javamap="java:com.company.group.MappingClass"/>
And as per the XSLT mapping the payload should be as below
<?xml version ="1.0" encoding="UTF-8"?>
<person>
<name>Rinku Gangwani</name>
</person>
I have also followed the following blog link but still i am getting the same issue
/people/pooja.pandey/blog/2005/06/27/xslt-mapping-with-java-enhancement-for-beginners
could you please tell me what can be the reason that i am getting the blank targt field values in the payload.
Thanks
Rinku Gangwani

Hi,
The Transaction code XSLT_TOOL for ABAP xslt mapping.But the Java Enhancement is used for normal xslt mapping which we created using Stylus Studio.You can not access the Java Enhancement in ABAP xslt mapping.
If you want to use Java Enhancement in xslt mapping then create a xslt mapping using Stylus Studio and save the file as .xsl and zip the .xsl and import to import archive.
Regards,
Prakasu.M
Edited by: prakasu on May 28, 2009 1:46 PM

RFC function module always creating BPs with the same user name (RFC user )

Hi All
I posted the below question in a different area before. But thought it would be more suitable here.
Moderators - Please let me know if am doing any mistake.
Question:
I have a RFC function module in CRM that creates Business Partners in ECC (XD01 tcode).
I am using a dialog RFC destination configured in SM59 in CRM.
But my RFC function module in CRM is always creating the Business Partners in ECC with the RFC user id (the user that we maintain for the RFC destination in SM59).
This is a problem for the users because they are not able to track the actual person responsible for creating these Business Partners.
Can somebody please let me know how to solve this problem?
Thanks
Raj

Hi.
You may use the trust relationship between CRM and R/3 and in SM59 instead of set a specific username, you set the flag "current user".
With this flag, the system will access R/3 system with the user logged in CRM system. The Trust relationship must be created between CRM and R/3 in order to the system doesn't ask for a password to login in R/3.
If you need more details please reply.
Kind regards,
Susana Messias

Need a File Parameter with Browse Functionality in ABAP

Hi
I Need a File Parameter with Browse Functionality in ABAP.
Can anyone help me with logic.
Regards,
Sree

Check below code:
PARAMETERS: p_file TYPE localfile.
DATA: l_path TYPE string,
      l_fpath TYPE string,
      l_fname TYPE string.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL METHOD cl_gui_frontend_services=>file_save_dialog
    EXPORTING
      window_title         = 'Save to...'
      default_extension    = '.txt'
      initial_directory    = 'C:\'
    CHANGING
      filename             = l_fname
      path                 = l_path
      fullpath             = l_fpath
    EXCEPTIONS
      cntl_error           = 1
      error_no_gui         = 2
      not_supported_by_gui = 3
      OTHERS               = 4.
IF sy-subrc EQ 0.
    MOVE l_fpath TO p_file.
ENDIF.

Problem while importing RFC function module in XI. Please Help!

Hi Experts,
           When I try to import RFC function module in XI I get the following error:
             **Ready for import**
Import started...
YCOP_VALIDATE_GR:
+ com.sap.aii.ibrep.sbeans.upload.RemoteUploadException: connection closed without message (CM_NO_DATA_RECEIVED)
Import failed with 1 error
Any idea why is this error? How to resolve this?
Thanks
Gopal

Hi
   The problem still persists.
   This is what I have done:
    1. My FM is RFC enabled. In the "Attribute" tab of the FM I have selected "Remote-enabled module" and "Start immed".
2.Activated and tested the FM.
3.Released the FM. In se37, Function Module -> Release ->Release.
4.Tried to import this FM in XI under "RFC". Get the same error.
I have some questions:
1. After releasing the FM do I have to activate it?
2. In release there is "Internal Release" Do I have to use that?
3.Do I have to do "Internal Release" first then "Release"?
4.The FM i am trying to import makes a call to another FM. Both the FMs are in the same system. Both are remote enabled. The second FM updates data in custom table. the first FM which I am importing validates the data and then calls the second FM for update. Do I have to import both FMs?
Please help me!
Thanks
Gopal

I need to create RFC function module which creates the IDOC

Hi-
Any idea how to create RFC function module which creates the outbound IDOC. If you have any sample code please forward to me.
Thanks,
Sony

My Problem is
Whenever they create Invoice using T-code's like FV65(Parked Document), automatically should create IDOC's...
I have used message type FIDCC1 but this message type is usefull only for Posting documents.
1. Whenever they create parked document, entries will be stored in BKPF(Parked Document-Filed-BKPF-BSTAT = 'V') and Bseg....
2. I have to read entries from those tables and should create IDOC...
3. I checked FM's(FI_IDOC_CREATE_FIDCC1, FI_IDOC_PREPARE) but are not useful...
4. Now I need to write one RFC function module and that FM should create the IDOC's....
Can anyone please help me out?
Thanks,
Sony

XSLT Maps with Java enhancements - JCO_SYSTEM_FAILURE

Hi,
I have reviewed several postings regarding XSLT Maps with Java enhancements. I followed instructions and build a jar file and the XSLT document. I built one imported archive with the .jar and .xsl. For the class, The path get loaded properly.
However, I still have a problem when and execute the interface.
My xslt has the following information
<xsl:transform version="1.0"
    xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
    xmlns:ns="http://xyz.abc.sap.def.com"
    xmlns:javamap="java:xyz.Date_Time">
<xsl:param name="inputparam" />
    <xsl:template match="/">
        <test><xsl:value-of select="javamap:getDateValue($inputparam)"/></test>
    </xsl:template>
</xsl:transform>
In SXMB_Moni I get the following error...
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>Exception in method processFunction.</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>"SYSTEM FAILURE" during JCo call. Exception in method processFunction.</SAP:Stack>
<SAP:Retry>A</SAP:Retry>
</SAP:Error>
If i remove the line
<test><xsl:value-of select="javamap:getDateValue($inputparam)"/></test>
The map ends successfuly.
Comments would be appreciated.
Regards,
Sergio

Stefan,
Find the class and method definition below. The method is static and it returns the string.
==========
package xyz;
import java.util.Map;
import com.sap.aii.mapping.api.AbstractTrace;
import com.sap.aii.mapping.api.StreamTransformationConstants;
import java.util.*;
import java.text.*;
public class Date_Time {
    private static AbstractTrace trace = null;
    public static String getDateValue(Map inputparam)
            trace = (AbstractTrace)inputparam.get(
                     StreamTransformationConstants.MAPPING_TRACE );
            Date now1 = new Date();
            SimpleDateFormat formatter = new SimpleDateFormat ("yyyyMMd");
            String dateString = formatter.format(now1);
            return dateString;

RFC function module without RETURN parameter thows error in XI. Please help

Hi Experts,
I have a File to RFC scenario in XI. The RFC function module that I am using at the receiving end does not have "RETURN" parameter. So when I test my scenario I get "RETURN" parameter not found error on SXMB_MONI.
So is it mandatory that RFC function module must have RETURN parameter when used in XI?
Is there any work around to avoid the error without changing the RFC function module?
Please help!
Thanks
Gopal

In my senario the QOS is best effort because it is a Sync.
But the function module is sync in nature as it is returning a parameter called SO_Docs and Ret_Msg. The Ret_Msg contains the error info but it not of BAPIRET2 type.
So is there any way to avoid this error when my QOS is best effort?
Please help!
Gopal

Help needed in XSLT MAPPING with RFC function module

Similar Messages

Maybe you are looking for