Skip to main content
Question

Transformer Error using unparsed-text

  • June 13, 2024
  • 1 reply
  • 73 views

Forum|alt.badge.img

I’ve to integrate the PDF in Ascii 64 on my XML external invoice - I’m on APP10 UPD17

On my transformer, i use this instruction :

1/ I dump on XP variable the 1st part of the file name, then i use concat to get the correct file name , in a variable named filepdf

<xsl:variable name="XP" select="invoiceId" />
<xsl:variable name="filepdf" select="concat($XP,'.txt')"/>
 

2 / On the XML tag <attachement> : i try to load the contain of the .txt file 

                   <ATTACHMENT>
                        <xsl:value-of select="unparsed-text($filepdf)"/>
                    </ATTACHMENT>
On message i get this error : 

Error while preparing input data. 
Caused by: ifs.fnd.base.SystemException: Transformer error: Error checking type of the expression 'funcall(unparsed-text, [variable-ref(filepdf/string)])'. 
Caused by: javax.xml.transform.TransformerConfigurationException: Error checking type of the expression 'funcall(unparsed-text, [variable-ref(filepdf/string)])'. 
Caused by: com.sun.org.apache.xalan.internal.xsltc.compiler.util.TypeCheckError: Error checking type of the expression 'funcall(unparsed-text, [variable-ref(filepdf/string)])'.

I’ve tried to change version 1 to 2, on the header : but no more result

xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="urn:ifsworld-com:schemas:einvoice_service_receive_einvoice_request" version="2.0" exclude-result-prefixes="xs">

 

1 reply

Forum|alt.badge.img+2
  • Do Gooder (Customer)
  • 5 replies
  • June 24, 2024

Having a similar error message in IFS Apps9 non-production environment when attempting to send E-INVOICE to EDI middleware provider.

“Error while preparing input data. 
Caused by: ifs.fnd.base.SystemException: Exception TransformerConfigurationException for transformer IFS_EINVOICE_TO_FINVOICE 
Caused by: javax.xml.transform.TransformerConfigurationException: line 304: Template 'Limit_Digits' already defined in this stylesheet.”
 

Although we are not receiving the same error in our production environment.

 

Any advice is much appreciated. 

 

Kind regards, 

Sheri Sigworth


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings