Migrating reuse code to lvlib files... namespace conversion leading to inability to find VIs?

I am attempting to migrate my reuse code from llb files to directories, and in the process grouping code within lvlib files. All of the reuse code resides within my user.lib directory (which is in the search path). After this conversion process, which has resulted in VIs being in different physical locations and having their namespaces altered, my other code is unable to automatically find them? Is there an automated method for telling my programs how to find the new reuse code. If not, does anyone have any suggestions for where to start writing a program that could help with the conversion process? Note, none of the VI names have changed, but of course their logical namespaces have.

You can also manually change the VI search paths.
http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/adding_dir_vi_srch_path/
Maybe you can temporarily add the new locations and go back to the defaults once you have saved all the VIs with the new paths.
LabVIEW Champion . Do more with less code and in less time .

Similar Messages

ERR: EXCEPTION_DURING_EXECUTE while using FILE CONTENT CONVERSION

Hi,
I'm trying a file to file scenario with File Content Conversion for Sender communication channel. But am getting the following error in SXMB_MONI
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code> 
<SAP:P1>com/sap/xi/tf/_MM_ContentBased_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>During the application mapping com/sap/xi/tf/_MM_ContentBased_ a com.sap.aii.utilxi.misc.api.BaseRuntimeException was thrown: RuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
I tried the same message mapping for normal file to file scenario without using File Content Conversion. It went through fine.
Our file structure follows
 <Header>
 <Sysnum>01</Sysnum>
 </Header>
 <Body>
 <Name>ABCDE</Name>
 <Age>25</Age>
 <Stream>XYZ</Stream>
 </Body>
The Sender Communication Channel Parameters follows:

Recordset Str: Header,1,Body,1
Header.fieldFixedLengths : 2
Header.fieldNames : Sysnum
Body.fieldFixedLengths : 5,2,3
Body.fieldNames : Name,Age,Stream
ignoreRecordsetName : true
Looking for a solution
Thanks,
Ajay.

Hi Ajay,
your message mapping failed.
Copy the XML message from monitoring and exectute the mapping in Integration Builder with maximal trace to get the reason.
Regards,
Udo

FIle Content Conversion Problem in IDOC-XI-File Scenario

Dear All,
I am doing IDOC-XI-FILE scenario.
I am facing one problem related to File Content Coversion.My requirement was to generate a dynamic file like %store_code%_%current_date%_sitemaster.xml , I have completed the dynamic generation successfully .
Now there is slight change in the requirement ,we have to suppress the current_date node of the xml content . i have tried to suppress the current_date using these DATE.fieldFixedLengths 0 , Date.fixedLengthTooShortHandling Cut , But I am unable to suppress it Can some body provide me the details on this .
The output xml version generated by Reciever file adapter is as below :
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
</ns0:MT_SITE_MASTER>
Plz provide me the code I have to write in the file content conversion .
Thanks in advance
Regards
Prabhat

If u see my earlier reply, I mentioned that u can not suppress the field from the one node.i.e Form SITE_DATA data type u can not suppress the field called CURRENT_DATE.
My suggestion is that , modify the Data type in such a way that you will be having two nodes as I have mentioned earlier. Then use the Suppress Logic for the Current Date.
So it will look like this-
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_SITE_MASTER xmlns:ns0="http://sample-xitest.com/sitemaster">
- <SITE_DATA>
<STORE_CODE>N002</STORE_CODE>
<TITLE_MEDI>Company</TITLE_MEDI>
<STORE_NAME>Mount Road</STORE_NAME>
<STREET>Chennai</STREET>
<COUNTRY>IN</COUNTRY>
<SALES_TAX_NO>12345678910</SALES_TAX_NO>
</SITE_DATA>
<CURR_DATE>
<CURRENT_DATE>20051105</CURRENT_DATE>
</CURR_DATE>
</ns0:MT_SITE_MASTER>
So ur SITE_DATA is not having a field called CURRENT_DATE. This field is in separate node (segment ) called CURR_DATE. Now u can use the Suppress Logic for the same like this.
CURR_DATE.fieldFixedLengths - 0
CURR_DATE.fixedLengthTooShortHanling - Cut
And in your Variable Substitution you can use the date from the other segment called CURR_DATE.
Hope this solves ur problem.
Regards,
Moorthy

How to get the source code in PAR file

Hi All,
I used the PAR migration tool to migrate from PAR to EAR file. When I imported the EAR into NWDS 7.3, I was just able to see the structure and jsp files and could not find the java source code files. I would requires the java source code to make modifications so that deprecated APIs can be replaced and to also make the code compatible with JDK 1.6.
I think the original 7.0 PAR file itself does not contain the source code. I decided to use the "Include source code" option when exporting the 7.0 PAR.
I have the portal application DC project in my NWDS 7.0. However, when I try to export the PAR file using Export --> PAR File -- > Next... I am unable to select any project from the list. The list appears blank with disabled Next & Finish buttons.
I also noticed that in the portal DC application structure, there is a .sda file under /gen/default/deploy. Also there is no PAR folder under /gen/default/public.
How do I include the source in the PAR file so that I can edit the same after migrating to EAR format ?
Regards,
Melwyn

DC and PAR/EAR stuff are different formats, SC/DC is an archive type used by NWDI, if I got it right.
How do I go about generating the PAR file (with source) ?
In fact through including the seources while creating the PAR/EAR in NWDS, but: no need to do that, you can also depack SDA (rename it to zip). If you wanna just see the Java sources you will find them there, otherwise decompile as Vijay already sad.
cheers

File Content Conversion Problem

Hi
I have a flat file having 10 fileds with fixed length of field 7 characters
abc bcd dce cef ecf fgi
123 234 343 233 434 343
322 222 222 222 222 222
+++++++++++++++++++++++++++++++
XML CODE FOLLOWS
+++++++++++++++++++++++++++++++
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_send xmlns:ns0="http://OTO-Continue.com">
-<SEND>
 <abc>343</abc>
 <bcd>343</bcd>
 <dce>434</dce>
 <cef>3434</cef>
 <ecf>343</ecf>
 <fgi>434</fgi>
</SEND>
</ns0:MT_send
As per the client req I'm going with FCC. The file is picking fine with the FILE. But not picking with the FCC.
The parameters which I gave are as follows.
SOURCE I feel it is fine since file is picking fine and keeping the same for FCC also.
PROCESSING
QOS -- Exactly Once
Poll Interval -- 10
Processing Mode -- Delete
Empty-File Handling -- Process empty files
CONTENT CONVERSION Parameters
Document Name -- (am giving sender data type name) DT_send
Document NSpace -- http://OTO-Continue.com
Recordset Name -- SEND
Recordset Structure -- SEND,*
Recordset Sequence -- Ascending
Recordset per Message -- 0
And in the table the parameters am settings are
SEND.fieldNames abc,bcd,cde,def,efg,ghk
SEND.fieldFixedLengths 7,7,7,7,7,7 (because each and every field has 7 characters)
SEND.keepIncompleteFields No
SEND.fieldFixedLengthType char
SEND.fieldContentFormatting trim
SEND.fieldEndSeparator 'nl'
This was the configuration. But this is not working I monitored the Communication Channel and file is not reading and not getting deleting.
What actually went wrong in above configuration. Why it is not working.
Thanks.

Hi Swarna,
CONTENT CONVERSION Parameters
Document Name -- ?
DocumentNSpace -- ?
Recordset Name -- ?
Recordset Structure -- ?
Recordset Sequence -- Ascending
Recordset per Message -- ?
Document Name - <Message Type> eg:- (MT_ABC)
DocumentNSpace - Name space of your MT
Recordset Name - The root node( Which has one occurence)
Recordset Structure - The parent node of the fields(can have multiple occurences)
Recordset Sequence -- Ascending
Recordset per Message -- 1/* (No.of records per each record set)
In your structure
+++++++++++++++++++++++++++++++
XML CODE FOLLOWS
+++++++++++++++++++++++++++++++
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT_send xmlns:ns0="http://OTO-Continue.com">
-<SEND>
<abc>343</abc>
<bcd>343</bcd>
<dce>434</dce>
<cef>3434</cef>
<ecf>343</ecf>
<fgi>434</fgi>
</SEND>
</ns0:MT_send
There is no root node, so in your FCC you need to mention your RecordsetName and you can ignoreRecordSetName in result structure. Check the following blog simulates your requirement.
/people/anish.abraham2/blog/2005/06/08/content-conversion-patternrandom-content-in-input-file
Regards,
Prasanna

Error while generating java client code from wsdl file

I am trying to generate a java client code from WSDL file um_workflowSaveCreateProfile.wsdl which includes um_workflowSaveCreateProfile_interface.wsdl file, so I am keeping both the files in the same folder and trying to generate the client code but it is showing me the below error highlighted .
um_workflowSaveCreateProfile.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="E:/DIPPWF/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:obinterface="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile">
 <import namespace="D:/DIPP/WSDL/um_workflowSaveCreateProfile_interface" location="um_workflowSaveCreateProfile_interface.wsdl"/>
 <service name="OblixIDXML_um_workflowSaveCreateProfile_Service">
 <port name="OblixIDXML_um_workflowSaveCreateProfile_Port" binding="obinterface:OblixIDXML_um_workflowSaveCreateProfile_Binding">
 <soap:address location="http://localhost:7777/identity/oblix/apps/userservcenter/bin/userservcenter.cgi"/>
 </port>
 </service>
</definitions>
um_workflowSaveCreateProfile_interface.wsdl
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:oblix="http://www.oblix.com/" xmlns:oblixxmllocalschema="http://www.oblix.com/OblixXMLLocalSchema" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface" targetNamespace="http://www.oblix.com/wsdl/um_workflowSaveCreateProfile_interface">
 <types>
 <xsd:schema targetNamespace="http://www.oblix.com/" elementFormDefault="qualified"
 xmlns="http://www.oblix.com/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:include schemaLocation="../XMLSchema/common_parameters.xsd" />
 <xsd:include schemaLocation="../XMLSchema/common_authentication.xsd" />
 <xsd:include schemaLocation="../XMLSchema/workflowSaveCreateProfile.xsd" />
 </xsd:schema>
 <xsd:schema targetNamespace="http://www.oblix.com/OblixXMLLocalSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <xsd:element name="request">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element name="params">
 <xsd:complexType>
 <xsd:sequence>
 <xsd:element ref="oblix:ObWorkflowName"/>
 <xsd:element ref="oblix:ObDomainName"/>
 <xsd:element ref="oblix:ObWfComment" minOccurs="0"/>
 <xsd:element ref="oblix:noOfFields"/>
 <xsd:element ref="oblix:AttributeParams"/>
 </xsd:sequence>
 </xsd:complexType>
 </xsd:element>
 </xsd:sequence>
 <xsd:attribute name="version" type="xsd:string" use="optional"/>
 <xsd:attribute name="application" type="xsd:string" use="required" />
 <xsd:attribute name="function" type="xsd:string" use="required" />
 <xsd:attribute name="mode" type="xsd:string" use="optional"/>
 </xsd:complexType>
 </xsd:element>
 </xsd:schema>
 </types>
 <message name="OblixIDXMLInput">
 <part name="authentication" element="oblix:authentication"/>
 <part name="request" element="oblixxmllocalschema:request"/>
 </message>
 <message name="OblixIDXMLOutput">
 <part name="body" element="oblix:Oblix"/>
 </message>
 <portType name="OblixIDXMLPortType">
 <operation name="OblixIDXML_um_workflowSaveCreateProfile">
 <input message="tns:OblixIDXMLInput"/>
 <output message="tns:OblixIDXMLOutput"/>
 </operation>
 </portType>
 <binding name="OblixIDXML_um_workflowSaveCreateProfile_Binding" type="tns:OblixIDXMLPortType">
 <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
 <operation name="OblixIDXML_um_workflowSaveCreateProfile">
 <soap:operation soapAction="http://www.oblix.com/"/>
 <input>
 <soap:body use="literal"/>
 </input>
 <output>
 <soap:body use="literal"/>
 </output>
 </operation>
 </binding>
</definitions>
I am using WSDL2 Java for generating the client code .
Please suggest where am I wrong .
E:\axis2-1.4\bin>WSDL2Java -uri E:\DIPPWF\um_workflowSaveCreateProfile.wsdl -p R
ND -d adb -s -o build\client--http-proxy-host 10.74.93.35 --http-proxy-port 80
Using AXIS2_HOME: E:\axis2-1.4
Using JAVA_HOME: C:\Program Files\Java\jdk1.6.0_02
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
Retrieving document at 'E:\DIPPWF\um_workflowSaveCreateProfile.wsdl'.
Retrieving document at 'um_workflowSaveCreateProfile_interface.wsdl', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_parameters.xsd', relative to 'f
ile:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/common_authentication.xsd', relative t
o 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'E:/DIPPWF/XMLSchema/workflowSaveCreateProfile.xsd', relati
ve to 'file:/E:/DIPPWF/um_workflowSaveCreateProfile_interface.wsdl'.
Retrieving schema at 'navbar.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/workfl
owSaveCreateProfile.xsd'.
Retrieving schema at 'searchform.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/wo
rkflowSaveCreateProfile.xsd'.
Retrieving schema at 'component_basic.xsd', relative to 'file:/E:/DIPPWF/XMLSche
ma/workflowSaveCreateProfile.xsd'.
Retrieving schema at 'displaytype.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/c
omponent_basic.xsd'.
Retrieving schema at 'error.xsd', relative to 'file:/E:/DIPPWF/XMLSchema/compone
nt_basic.xsd'.
Retrieving schema at 'component_workflowTicket.xsd', relative to 'file:/E:/DIPPW
F/XMLSchema/workflowSaveCreateProfile.xsd'.
*[ERROR] More than one part for message OblixIDXMLInput*
org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessingException:
More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Exception in thread "main" org.apache.axis2.wsdl.codegen.CodeGenerationException
: Error parsing WSDL
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:153)
at org.apache.axis2.wsdl.WSDL2Code.main(WSDL2Code.java:35)
at org.apache.axis2.wsdl.WSDL2Java.main(WSDL2Java.java:24)
Caused by: org.apache.axis2.AxisFault: More than one part for message OblixIDXML
Input
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:397)
at org.apache.axis2.description.WSDL11ToAllAxisServicesBuilder.populateA
llServices(WSDL11ToAllAxisServicesBuilder.java:107)
at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.<init>(CodeGenerat
ionEngine.java:147)
... 2 more
Caused by: org.apache.axis2.description.WSDL11ToAxisServiceBuilder$WSDLProcessin
gException: More than one part for message OblixIDXMLInput
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1162)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.addQNameRefer
ence(WSDL11ToAxisServiceBuilder.java:1085)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateBindi
ng(WSDL11ToAxisServiceBuilder.java:686)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
int(WSDL11ToAxisServiceBuilder.java:538)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateEndpo
ints(WSDL11ToAxisServiceBuilder.java:489)
at org.apache.axis2.description.WSDL11ToAxisServiceBuilder.populateServi
ce(WSDL11ToAxisServiceBuilder.java:363).
Thanks in advance.
akshay

Hello,
Were you able to resolve this issue ?
I am seeing the same issue and at my wits end.
regards
Amit

File Content Conversion Error in PI 7.1 (file to Proxy)

Hi
I am working on File to Proxy Scenario and I gave the File content conversion as below, File is picking up by the PI Server when I look at Communication Channel Monitoring, However when I open the Message ID in the CC monitoring it says as
404 Not Found
The requested resource does not exist.
and I do not see any message SXMB_MONI(Because the content is not converted), Can anyone give an idea how to debug this
Thanks
PR
Please find the details below which I gave in the content Conversion
Document Name : MT_TW_AK
Document NameSpace : http://aiwcd.com/Claims_Management(CM)_Rel2.0
RecordSet Name : FROISROIAcknowledgement
RecordSet Structure : Header,1,Record,*,Trailer,1
Recordset Sequence : Ascending
KeyField Name :TransactionSetID
Key Field Type : String (Case Sensitive)
IgnoreRecordsetName : true
Header.fieldNames :TransactionSetID,SenderID,ReceiverID,DateTransmissionsent,TimeTransmissionsent,OriginalTransmissionDate,OriginalTransmissionTime,TestProductionCode,InterchangeVersionID
Header.fieldFixedLengths: 3,25,25,8,6,8,6,1,5
Header.keyFieldValue : H
Record.fieldSeparator :
Record.fieldNames : TransactionSetID,RecordSequenceNumber,DateProcessed,TimeProcessed,InsurerFEIN,ClaimAdministratorPostalCode,ClaimAdministratorFein,AcknowledgementTransactionSetID,ApplicationAcknowledgmentCode,InsuredReportNumber,ClaimAdministratorClaimNumber,JuridictionClaimNumber,MaintenanceTypeCode,MaintenanceTypeCodeDate,RequestCode,FreeFormText,NumberofErrors,MaintenanceTypeCorrectionCode,MaintenanceTypeCorrectionCodeDate,JurisdictionBranchOfficeCode,ClaimAdministratorAlternatePostalCode,NumOfErrors
Record.fieldFixedLengths: 3,9,8,6,9,9,9,3,2,25,25,25,2,8,3,60,2,2,8,2,9,19
Record.keyFieldValue : A
Trailer.fieldNames:TransactionSetID,DetailRecordCount,TransactionCount
Trailer.fieldFixedLengths: 3,9,9
Trailer.keyFieldValue : T
ignoreRecordsetName: true

PR,
Can you check the error in sender communication channel?
Go to RWB ---> Component Monitoring ---> Adapter Engine ---> Communication cahnnel monitoring --> it displays new page. Then give your file sender communication cahnnel name. There you will definitely see some error.
The error what you are getting is a different to this one. Can you please check the error what I have given above path.
Regards,
---Satish

Supress Column Heading - File Content Conversion in Sender Adapter

Hi,
Let me give a more clear picture about my scenario. I need to convert CSV File to XML output:-
My source file has column heading and values. The sample data is mentioned hereunder:-
PERNR;KID;PNALT;NACHN;NAME2;VORNA
;1200;1200;Angus
I have created a data type as under:-
DT_LegacyEmployee (Category - Complex Type)
     Employees (Category - Element, Occurence - 1)
          Header (Category - Element, Occurence - 0...1)
               PERNR_H
               KID_H
               PNALT_H
               NACHN_H
               NAME2_H
               VORNA_H
          Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
               PERNR
               KID
               PNALT
               NACHN
               NAME2
               VORNA
The file conversion parameters in the file sender adapter are mentioned hereunder:-
Document Name - MT_LegacyEmployee
Document Namespace - http://abc.com/xi
Recordset Name - Employees
Rescordset Structure - Header,1,Employee,*
Recordsets per Message - 1
Key Field Type - String (Case Sensitive)
Employee.fieldSeparator - ;
Employee.endSeparator - 'nl'
Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
I dont' have a key field value. How do we remove the header and show only the values in the xml output. I have searched the forum topics as well checked many blogs related to file content conversion, but nothing helped. Kindly advice how to fix this issue. Thanks in advance.
Regards.
Praveen

Hi Praveen,
Change your File Adapter as below
Document Name - MT_LegacyEmployee
Document Namespace - http://abc.com/xi
Recordset Name - Employees
Rescordset Structure - Employee,*
Recordsets per Message - 1
Key Field Type - String (Case Sensitive)
Employee.fieldSeparator - ;
Employee.endSeparator - 'nl'
Employee.fieldNames - PERNR,KID,PNALT,NACHN,NAME2,VORNA
There is no need for the Header required in the data type.
DT_LegacyEmployee (Category - Complex Type)
Employees (Category - Element, Occurence - 1)
Employee (Categroy - Element, Type - DT_LegacyEmployee_Row, Occurence - 0...unbounded)
PERNR
KID
PNALT
NACHN
NAME2
VORNA
Now the trick is in the mapping program
Lets assume your mapping looks like
MT_LegacyEmployee ---> MT_TargetEmployee
- Employees ---> Records
   - Employee ---> Record
     - PERNR ---> TargetPERNR
     - .. so on
When you do a mapping from Employee ---> Record apply the following logic.
(PERNR)--->
             (TestEquals =) --->(NOT)--->
(Constant) --->                                (IF)
(PERNR)                       (IF Without Else) ---> (Record)
                                               (THEN)
                            (Employee)--->
When doing this make sure RightClick on PERNR and Select Context ---> Employees.
By default context would be from Employee and it will give you an error of XSD format. So make sure you are changing the context.

J2SE XML to Flat File Content Conversion

Hi
I've currently got a scenario which sends a flat file to the integration server, it gets mapped and sent to a receiver adapter on a deployed j2se engine.
I'm now trying to convert the xi-xml structured file to a flat file again on the j2se side (the same flat file format it originally had).
My original flat file looks like this -
477
477=AA1
My xml file looks like this -
<?xml version="1.0" encoding="UTF-8"?>
<ns0:ResultMessage xmlns:ns0="urn:xxxx-com:a_test_j2se_filetofile">
<Item>
 <field1>477</field1>
</Item>
<Item>
 <field1>477</field1>
 <field2>AA1</field2>
</Item>
</ns0:ResultMessage>
I am using these content conversion parameters:
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
I get this error on the integration engine (sxmb_moni):
Error while sending by HTTP (error code: 500, error text: Internal Server Error:java.lang.NullPointerException) (See attachment HTMLError for details)
and the j2se adpater log says this:
17:16:32 (4120): Message "13b9d644-54c9-4ffb-0c40-db4c14458d77" of type "application/xml", kind "B" received
17:16:32 (4124): Parsing XML message
17:16:32 (4131): ERROR: Message processing failed with "java.lang.NullPointerException"
What am i missing?

So, now... I did a test configuration in XI and sent your test-payload...it worked.
The J2SE adapter configuration:
File adapter java class
classname=com.sap.aii.messaging.adapter.ModuleXMB2File
version=30
mode=XMB2FILEWITHCONVERSION
#Adress for XMB endpoint -
XI.httpPort=8111
XI.httpService=/file/receiver
#File Adapter specific parameters -
file.createDir=1
file.targetDir=c:/transfer/inbound
file.targetFilename=xmboutput.txt
#file.writeMode=append
#file.writeMode=overwrite
file.writeMode=addCounter
file.counterMode=immediately
#file.counterMode=afterFirst
file.counterSeparator=_
file.counterFormat=00000
file.counterStep=1
#File Content Conversion specific parameters -
xml.addHeaderLine=0
xml.fieldSeparator==
xml.endSeparator='nl'
And here the configuration of the receiver communication channel in the integration directory:
Adapter Type: XI
Receiver
Transport-Protocol: HTTP 1.0
Message-Protocol: XI 3.0
Adapter-Engine: Integration Server
Adressing-Type: URL Address
Target Host: <yourJ2SEip>
Service Number: 8111
Path Prefix:http://<yourJ2SEip>:8111/file/receiver
Authentication Data
Logon data for non-SAP systems
User
Password
That's it... sent your payload and got the wished result:
477
477=AA1
Regards,
Heinrich

File Content Conversion in EDI to File without Seeburger

Hello Friends,
I am using just 2 fields Name and Address in 864 Transaction code.Can anybody help me how to do File Content Conversion from EDI to Xml.as i am using only 2 levels of hierarchy..Please explain me the step by step process 

Dear Kayanth,
My advice to you is if your implementing organization has more then one EDI scenario today or plan to add more EDI scenario to the business is to use the Item Field Content master with the XI.
This tool is powered by NetWeaver and allows to translate all standard EDI messages from txt file to XML.
The tool is represented today by Informatica and is used as a java file deployed in the file adapter.
This will sit-well with the XI development methodology of getting the whole EDI message into the XI in an XML format because in the future you might need more then two fields in the message so modifying the interface will take less time.
Try to look to the future of the implementing organization when it comes to interfaces.
"Quick & Dirty" is not always the best way....usually in the long run - its the worst...
Good luck.
Nimrod.G

** File Content Conversion Error in Receiver CC - How to solve this?

Hi friends,
My target structure looks like below.
EmployeeJobDetails --> Message Type
 JobCode --> Node
 EmployeeNumber xsd:string
 Domain xsd:string
 JobTrack --> Node
 Department xsd: string
 Position xsd: string
I use the FCC parameters in the receiver CC as below:
Recordset Structure: JobCode,JobTrack
JobCode.fieldSeparator = |
JobCode.endSeparator = 'nl'
JobTrack.fieldSeparator = |
JobTrack.endSepartor = 'nl'.
Because, we want the output like below
1099|Raja
Accts|JuniorAccountant
1100|Ram
HR|Recruiter
like this.
In this scenario Source is XML and target is txt file.
I am using XSLT Mapping. The FCC works fine, if my source input file contains some records. But, when we send empty source XML file as below
<?xml version="1.0" encoding="UTF-8"?>
<EMPLOYEE_DATA/>
Mapping works fine. Message is processed successfully in SXMB_MONI. The payload in response also comes with Message Type name like below
<EmployeeJobDetails namespace >
</EmployeeJobDetails>
While convert this, the system throws below error.
Error Message:
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure '' found in document', probably configuration error in file adapter (XML parser error)'
Friend, how to convert this when source XML is empty.
But, if we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the same empty XML file FCC is working fine and we get the target text file 0 KB. (Amazing !!)
But, in the first case, how to solve the issue?
Kind Regards,
Jegathees P.

Hi friends,
If we remove JobTrack node in target strucutre and remove the JobTrack parameters in CC, then if we send the same empty XML file FCC is working fine and we get the target text file 0 KB. (Amazing !!)
But, if we give parameters like JobCode,JobTrack then send pass the same empty file, we face the problem 'File Content Conversion' Error.
Searching solution for this problem ...

Regarding file content conversion

Re: regarding file content conversion
Posted: Sep 25, 2008 11:30 AM in response to: kummari Edit E-mail this message Reply
i tried.but m getting this error
Message processing failed. Cause: com.sap.aii.af.ra.ms.api.RecoverableException: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns1:MT_HyperionReport' found in document', probably configuration error in file adapter (XML parser error)': java.lang.Exception: Exception in XML Parser (format problem?):'java.lang.Exception: Message processing failed in XML parser: 'Conversion configuration error: Unknown structure 'ns1:MT_HyperionReport' found in document', probably configuration error in file adapter (XML parser error)'
Actually my input structure is:
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_ECCReport xmlns:ns0="urn:syngenta.com:i_ecc_erp:se:global:fi_reports:common">
<ACTFiscalyear>siva</ACTFiscalyear>
<StartPeriod>44</StartPeriod>
<EndPeriod>55</EndPeriod>
<LineItems>
<ReportingUnit>rama</ReportingUnit>
<ProfitCentre>844</ProfitCentre>
<Amount>855</Amount>
</LineItems>
</ns0:MT_ECCReport>
and in FCC i wrote below these three lines:
LineItems.fieldSeparator 'nl'
MT_HyperionReport.fieldSeparator 'nl'
LineItems.fieldSeparator 'nl'
So please tell me what is wrong in this

MT_HyperionReport is your message type and this represents the top level node of your message. Below this you have your records. You have MT_HyperionReport as a record type which is clearly not going to work.
In the content conversion parameters section the following fields should be filled, you dont need to specify Recordset if your XML structure does not include this node see SAPhelp example:
Document Name: MT_HyperionReport
Document Namespace: <look at your message type in the designer>
Recordset Structure: Record_type1,<occurrence 1..>, Record_type2,<occurrence 1..>
In the parameter box:
Record_type1.fieldSeparator
Record_type1.fieldNames
ignoreRecordsetName value true
Record_type2...
The SAP help on this is pretty clear and comprehensive...
http://help.sap.com/saphelp_nw04/helpdata/en/0f/80243b4a66ae0ce10000000a11402f/frameset.htm

File content conversion sender adapter

Hi Friends,
I am doing File to IDoc scenario.
I am using File Content Conversion for File Adapter.
My structure look like this
MT_File
HEADER1 1..1
--header1
-- header2
HEADER2 1..1
--header3
DETAILS 1..unbounded
--details1
--details2
--details3
TRAILER1 1..1
-- trailer1
TRAILER2 1..1
-- trailer2
----trailer3
In File Content conversion parameeters..
Document Name :MT_File
Document Namespace :urn:test:FileFcctoIdoc
RecordSet name :
RecordsetStructure :HEADER1,1,HEADER2,1,DETAILS,*,TRAILER1,1,TRAILER2,1
RecordSet Structure: Ascending
RecordSet Per message : *
Key Field Name :header1,header3,details1,trailer1,trailer3
ignoreRecordsetName     : true
HEADER1.fieldNames      :header1,header2
HEADER1.keyFieldValue      : H1
HEADER1.fieldFixedLengths :5,10
HEADER1.endSeparator   :'nl'
HEADER2.fieldNames             :header3
HEADER2.keyFieldValue         : *D
HEADER2.fieldFixedLengths     :5
HEADER2.endSeparator         :'nl'
DETAILS.fieldNames               :details1,details2,details3
DETAILS.keyFieldValue         : 3
DETAILS.fieldFixedLengths     :5,5,5
DETAILS.endSeparator         :'nl'
TRAILER1.fieldNames               :trailer1
TRAILER1.keyFieldValue         : *S
TRAILER1.fieldFixedLengths     :5
TRAILER1.endSeparator         :'nl'
TRAILER2.fieldNames               :trailer2,trailer3
TRAILER2.keyFieldValue         :SE    TRAILER2.fieldFixedLengths    :5,5
TRAILER2.endSeparator         :'nl'
File is :
H1hh1hhhhhhhhh2
*Ddd*
Xddd1dddd2dddd3
Xddd4dddd5dddd6
Xddd7dddd8dddd9
*Sss*
SEKss2
in RWB, Channel CC_FILE_Sender_FccDemo: Empty document found. Proceed without sending message
I think the problem is in FCC paramters..
Could please have a look and correct me
Regards
Ram

Ram,
The problem which i can see is your key field values in your test file. Remember you should have the key field value in each new line at the same place.
For example you have given your text file as shown below...
File Given By You is :
>H1hh1hhhhhhhhh2
>*Ddd *
>Xddd1dddd2dddd3
>Xddd4dddd5dddd6
>Xddd7dddd8dddd9
>*Sss *
>SEKss2
Compair the above file with the below one..
>H1hh1hhhhhhhhh2
>*Ddd *
>Xddd1dddd2dddd3
>Xddd4dddd5dddd3
>Xddd7dddd8dddd3
> *Sss *
>SEKss2
If you notice, for details I have given key field value 3 in each line & at same place.
One more thing just use the KeyFieldName only one ( just follow the same blog which I have given, to understand how to use the KeyFieldName )
e.g.
Document Name :MT_File
Document Namespace :urn:test:FileFcctoIdoc
RecordSet name :
RecordsetStructure :HEADER1,1,HEADER2,1,DETAILS,*,TRAILER1,1,TRAILER2,1
RecordSet Structure: Ascending
RecordSet Per message : *
Key Field Name : KF
Regards,
Sarvesh

Problems in File Content Conversion

Hello,
 I am trying to convert a text file to an XML using File Content Conversion in XI 3.0.
 The incoming text file gets picked up but no message is sent and hence no message is received in the monitor.I get the following log-
Success Channel FILE_SENDER_XML_1: Entire file content converted to XML format
Warning Channel FILE_SENDER_XML_1: Empty document found. Proceed without sending message
Success File "C:\xi_public\i033066\dme_in.txt" deleted after processing
Can somebody help me on this
Thanks
Sandeep

Hello,
 I am not sure of why the empty Payload is created.
I have the following TXT file -
LINE 1 01 22 Sandeep ASKDJKLASD HDFC Bank 12342 asdasd 123569
LINE 2 02 22 Sagar 23123 ICICI 4234 ASDASD 254636 12304 ASDAsdqwe
LIME 3 03 22 1 12304
Ignore 'Lines' above.They are not part of the file.
I have given the following parameters -
Document Name - SampleMessageType
Document Namespace - http://sandeep/xi/bpm_example
Recordset Name - Header,Item,Trailer
Recordset Namespace - http://sandeep/xi/bpm_example
Record Structure - Header,,Item,,Trailer,*
Recordset Sequence - Ascending
Key Field Name - Record Type
Key Field Type - String(Case Sensitive)
Header.fieldFixedLengths 3,4,15,20,15,15,20,10
Header.fieldNames RecordType,RecordLength,CompanyName,CompanyAddress,BankName,BankCode,BankAddress,AccountNumber
Header.processFieldNames fromConfiguration
Header.keyFieldValue 01
Header.lastFieldsOptional YES
Item.fieldFixedLengths 3,4,15,20,15,15,15,10,6,10
Item.fieldNames RecordType,RecordLength,BeneficiaryName,BeneficiaryAddress,BankName,BankCode,BankAddress,AccountNumber,Amount,NoteToPayee
Item.processFieldNames fromConfiguration
Item.keyFieldValue 02
Item.lastFieldsOptional YES
Trailer.fieldFixedLengths 3,4,6,6
Trailer.fieldNames RecordType,RecordLength,TotalRecords,TotalAmount
Trailer.processFieldNames fromConfiguration
Trailer.keyFieldValue 03
Trailer.lastFieldsOptional YES
If I don't give these parameters then channel will give me errors.I don't know what other parameter to give to create a file.
I had tried the same thing with the following and it worked
Document Name - SampleMessageType
Document Namespace - http://sandeep/xi/bpm_example
Record Structure - Substr,*
Recordset Sequence - Ascending
Key Field Name - Record Type
Key Field Type - String(Case Sensitive)
Substr.fieldFixedLengths 3,4,15,20,15,15,20,10,3,4,15,20,15,15,15,10,6,10,3,4,6,6
Substr.fieldNames RecordType,RecordLength,CompanyName,CompanyAddress,BankName,BankCode,BankAddress,AccountNumber,RecordType,RecordLength,BeneficiaryName,BeneficiaryAddress,BankName,BankCode,BankAddress,AccountNumber,Amount,NoteToPayee,RecordType,RecordLength,TotalRecords,TotalAmount
Substr.processFieldNames fromConfiguration
Substr.keyFieldValue 01
Substr.lastFieldsOptional YES
But the problem here is my mapping has the Header,Item and Trailer as the structure names but he XML created here will be like
<?xml version="1.0" encoding="utf-8" ?>
- <ns:SampleMessageType xmlns:ns="http://sandeep/xi/bpm_example">
- <Recordset>
- <Substr>
<RecordType>21</RecordType>
<RecordLength>22</RecordLength>
<CompanyName>Sandeep</CompanyName>
<CompanyAddress>ASKDJKLASD</CompanyAddress>
<BankName>HDFC Bank</BankName>
<BankCode>12342</BankCode>
<BankAddress>asdasd</BankAddress>
<AccountNumber>123569</AccountNumber>
</Substr>
- <Substr>
<RecordType>02</RecordType>
<RecordLength>22</RecordLength>
<CompanyName>Sagar</CompanyName>
<CompanyAddress>23123</CompanyAddress>
<BankName>ICICI</BankName>
<BankCode>4234</BankCode>
<BankAddress>ASDASD 25463</BankAddress>
<AccountNumber>6 12304</AccountNumber>
<RecordType>AS</RecordType>
<RecordLength>DAsd</RecordLength>
</Substr>
- <Substr>
<RecordType>03</RecordType>
<RecordLength>22 1</RecordLength>
</Substr>
</Recordset>
</ns:SampleMessageType>
In this case my mapping fails
Thanks,
Sandeep

File content conversion query

hi,
i have sender and received side -file content conversion.
in sender communication channel -
Recordset structure is -> Header,1,Detail,*
Message type structure is
MT1 has 2 subnodes Header and Detail.
In my message type,there is no field identical in Header and Details. All fields are different.
(1) Is Key Field Name mandatory in this case ? If I am not giving Key field name,sender channel gives error. How to resolve it ?
(2) Input file comes from customer and in the input file there is no specific data to identify header and detail. 1st line shud be header and other lines shud be Detail ,they say. If no identification coming in incoming data,how can we set the key field name ?
rgds

Hi SAP PI,
 For this moment try this.
Let the file content is like this
03456451 TESTDATABC 7645649 8746464
12344 60042
45678 60043
You try reading the file like this
<MT_S>
 <RECORDSET>
 <ROW>
 <field1>03456451</field1>
 <field2>TESTDATABC 7645649 8746464</field1>
 </ROW>
 <ROW>
 <field1>03456451</field1>
 <field2>TESTDATABC 7645649 8746464</field1>
 </ROW>
 <ROW>
 <field1>03456451</field1>
 <field2>TESTDATABC 7645649 8746464</field1>
 </ROW>
</RECORDSET>
</MT_S>
FCC is like this
Document Name : MT_S
Document Namespace: "put name space here"
Recordset Name: RECORDSET
Recordset Structure: ROW,*
ROW.fieldNames field1,field2
ROW.endSeparator 'nl'
ROW.fieldSeparator 0x20
Once you get this in mapping use a simple UDF to ignore the first ROW values and read the rest.
Populate the target structure from the output of UDF for each field value.
Please let me know if you need the uDF and further mapping for this.
Regards
Anupam

Migrating reuse code to lvlib files... namespace conversion leading to inability to find VIs?

Similar Messages

Maybe you are looking for