Error in flat file mapping

I am using flat file as source ,and when i am trying to validate the mapping i am getting the following error:
No data file specified
I tried to configure the mapping,I did not find any option asking source file name.
Can you please help me...
Kiran

Hi Kiran
As far as I remember...when you configure the map, the map configuration property inspector has a tree in the lhs if you navigate to the flat file operator, and right click on that node you should be able to add a data file. The properties for the data file are shown on the rhs when selected in tree.
Cheers
David

Similar Messages

Validation error using flat files..VLD-2407

Trying to build a simple flat file mapping to test out file locations and permissions at a new client and getting the following error: VLD-2407: SQL*Loader map must have a source file. OWB 10.2.0.3. I've added a filename for everything i could find in the mapping configuration screens. Any thoughts?
Thanks

It can happen if your location for deployment is different than that of development and you have forgotten to make sure the
source directory ane file exist in deployment location.
Regards
azaman

Bdc - errors in flat file

hi,
in BDC,
after uploading data from flat file,
how to find if there are any errors in flat file,
before starting the session.

Hi,
You have to create internal tables for all the mandatory fields. see the following code :
I am giving an example for XK01 Transaction.
TYPES:BEGIN OF TY_XK01,
      LIFNR(10)      TYPE C ,          "VENDOR'S ACCOUNT NUMBER
      BUKRS(4)       TYPE C ,          "COMPANY CODE
      EKORG(4)       TYPE C ,          "PURCHASING ORGANISATION
      KTOKK(4)       TYPE C ,          "VENDOR ACCOUNT GROUP
      NAME1(35)      TYPE C ,                              "NAME1
      SORTL(10)      TYPE C ,          "SORT FIELD
      STRAS(35)      TYPE C ,          "STREET
      PSTLZ(10)      TYPE C ,          "POSTAL CODE
      ORT01(35)      TYPE C ,          "CITY
      LAND1(3)       TYPE C ,          "COUNTRY KEY
      REGIO(3)       TYPE C ,          "REGION
      TIME_ZONE(6)   TYPE C ,          "ADDRESS TIME ZONE
      LANGU(1)       TYPE C ,          "LANGUAGE KEY
      TELF1(16)      TYPE C ,          "TELEPHONE NUMBER
      TELFX(31)      TYPE C ,          "FAX NUMBER
      SMTP_ADDR(241) TYPE C ,          "E-MAIL ADDRESS
      URI_SCREEN(132) TYPE C ,     "UNIFORM RESOURCE LOCATOR
      AKONT(10)      TYPE C ,          "RECONCILITATION ACCOUNT
      ZUAWA(3)       TYPE C ,          "KEY FOR SORTING ACCORDING TO ASSIGNMENT NUMBERS
      MINDK(3)       TYPE C ,          "MINORITY INDICATORS
      ALTKN(10)      TYPE C ,          "PREVIOUS MASTER RECORD NUMBER
      ZTERM(4)       TYPE C ,          "TERMS OF PAYMENT KEY
      ZWELS(10)      TYPE C ,          "LIST OF THE PAYMENT METHODS
      WAERS(5)       TYPE C ,          "PURCHASE ORDER CURRENCY
      END OF TY_XK01,
BEGIN OF TY_LIFNR,
     LIFNR(10) TYPE C ,
     END OF TY_LIFNR,
     BEGIN OF TY_BUKRS,
     BUKRS(4) TYPE C ,
     END OF TY_BUKRS,
     BEGIN OF TY_EKORG,
     EKORG(4) TYPE C ,
     END OF TY_EKORG,
     BEGIN OF TY_KTOKK,
     KTOKK(4) TYPE C ,
     END OF TY_KTOKK,
     BEGIN OF TY_LAND1,
     LAND1(3) TYPE C ,
     END OF TY_LAND1,
     BEGIN OF TY_LANGU,
     LANGU(1) TYPE C ,
     END OF TY_LANGU,
     BEGIN OF TY_AKONT,
     AKONT(10) TYPE C ,
     END OF TY_AKONT,
     BEGIN OF TY_ZUAWA,
     ZUAWA(3) TYPE C ,
     END OF TY_ZUAWA,
     BEGIN OF TY_MINDK,
     MINDK(3) TYPE C ,
     END OF TY_MINDK,
     BEGIN OF TY_WAERS,
     WAERS(5) TYPE C ,
     END OF TY_WAERS.
DATA : I_XK01     TYPE TABLE OF TY_XK01,     "FOR HOLDING DATA FROM FLAT FILE
       I_SUCCMESG TYPE TABLE OF TY_MESG,     "FOR SUCCESS RECORDS DETAILS
       I_ERRMESG TYPE TABLE OF TY_MESG,     "FOR ERROR RECORDS DETAILS
       I_ERROR TYPE TABLE OF TY_ERROR,
I_LIFNR TYPE TABLE OF TY_LIFNR,
I_BUKRS TYPE TABLE OF TY_BUKRS,
I_EKORG TYPE TABLE OF TY_EKORG,
I_KTOKK TYPE TABLE OF TY_KTOKK,
I_LAND1 TYPE TABLE OF TY_LAND1,
I_LANGU TYPE TABLE OF TY_LANGU,
I_AKONT TYPE TABLE OF TY_AKONT,
I_ZUAWA TYPE TABLE OF TY_ZUAWA,
I_MINDK TYPE TABLE OF TY_MINDK,
I_WAERS TYPE TABLE OF TY_WAERS,
I_FINALMESG TYPE TABLE OF TY_ERROR,
I_MESG TYPE TABLE OF TY_MESG.
*& WORK AREA DECLARATION
DATA: WA_XK01     TYPE TY_XK01,               "FOR HOLDING DATA FROM FLAT FILE
       WA_SUCCMESG TYPE TY_MESG,               "FOR SUCCESS RECORDS DETAILS
       WA_ERRMESG TYPE TY_MESG,               "FOR ERROR RECORDS DETAILS
       WA_ERROR TYPE TY_ERROR,
WA_LIFNR TYPE TY_LIFNR,
WA_BUKRS TYPE TY_BUKRS,
WA_EKORG TYPE TY_EKORG,
WA_KTOKK TYPE TY_KTOKK,
WA_LAND1 TYPE TY_LAND1,
WA_LANGU TYPE TY_LANGU,
WA_AKONT TYPE TY_AKONT,
WA_ZUAWA TYPE TY_ZUAWA,
WA_MINDK TYPE TY_MINDK,
WA_WAERS TYPE TY_WAERS,
WA_MESG TYPE TY_MESG,
WA_FINALMESG TYPE TY_ERROR.
INITIALIZATION.
SELECT LIFNR FROM LFA1 INTO TABLE I_LIFNR.
SELECT BUKRS FROM T001 INTO TABLE I_BUKRS .
SELECT EKORG FROM T024E INTO TABLE I_EKORG .
SELECT KTOKK FROM T077K INTO TABLE I_KTOKK .
SELECT LAND1 FROM T005 INTO TABLE I_LAND1.
SELECT SPRAS FROM T002 INTO TABLE I_LANGU.
SELECT SAKNR FROM SKA1 INTO TABLE I_AKONT .
SELECT ZUAWA FROM TZUN INTO TABLE I_ZUAWA .
SELECT MINDK FROM T059M INTO TABLE I_MINDK .
SELECT WAERS FROM TCURC INTO TABLE I_WAERS.
LOOP AT I_XK01 INTO WA_XK01.
      TRANSLATE WA_XK01-LIFNR TO UPPER CASE.
      READ TABLE I_LIFNR INTO WA_LIFNR WITH KEY LIFNR = WA_XK01-LIFNR.
      IF SY-SUBRC = 0 .
        CONCATENATE WA_MESG-MESG TEXT-100 WA_XK01-LIFNR TEXT-101 ' , ' INTO WA_MESG-MESG.
      ENDIF.
      TRANSLATE WA_XK01-BUKRS TO UPPER CASE.
      READ TABLE I_BUKRS INTO WA_BUKRS WITH KEY BUKRS = WA_XK01-BUKRS.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-102 WA_XK01-BUKRS TEXT-103 ' , ' INTO WA_MESG-MESG.
      ENDIF.
      TRANSLATE WA_XK01-EKORG TO UPPER CASE.
      READ TABLE I_EKORG INTO WA_EKORG WITH KEY EKORG = WA_XK01-EKORG.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-104    WA_XK01-EKORG TEXT-103 ',' INTO WA_MESG-MESG.
      ENDIF.
      TRANSLATE WA_XK01-KTOKK TO UPPER CASE.
      READ TABLE I_KTOKK INTO WA_KTOKK WITH KEY KTOKK = WA_XK01-KTOKK.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-105   WA_XK01-KTOKK TEXT-103   ',' INTO WA_MESG-MESG.
      ENDIF.
      TRANSLATE WA_XK01-LAND1 TO UPPER CASE.
      READ TABLE I_LAND1 INTO WA_LAND1 WITH KEY LAND1 = WA_XK01-LAND1.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-106   WA_XK01-LAND1 TEXT-103   ',' INTO WA_MESG-MESG.
      ENDIF.
      TRANSLATE WA_XK01-LANGU TO UPPER CASE.
      READ TABLE I_LANGU INTO WA_LANGU WITH KEY LANGU = WA_XK01-LANGU.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-107 WA_XK01-LANGU TEXT-103   ',' INTO WA_MESG-MESG.
      ENDIF.
      READ TABLE I_AKONT INTO WA_AKONT WITH KEY AKONT = WA_XK01-AKONT.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-108   WA_XK01-AKONT TEXT-103 ',' INTO WA_MESG-MESG.
      ENDIF.
      READ TABLE I_ZUAWA INTO WA_ZUAWA WITH KEY ZUAWA = WA_XK01-ZUAWA.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-109    WA_XK01-ZUAWA TEXT-103   ',' INTO WA_MESG-MESG.
      ENDIF.
      READ TABLE I_MINDK INTO WA_MINDK WITH KEY MINDK = WA_XK01-MINDK.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-110    WA_XK01-MINDK TEXT-103   ',' INTO WA_MESG-MESG.
      ENDIF.
      TRANSLATE WA_XK01-WAERS TO UPPER CASE.
      READ TABLE I_WAERS INTO WA_WAERS WITH KEY WAERS = WA_XK01-WAERS.
      IF SY-SUBRC <> 0 .
        CONCATENATE WA_MESG-MESG TEXT-111   WA_XK01-WAERS TEXT-103   ',' INTO WA_MESG-MESG.
      ENDIF.
append wa_mesg to err_mesg.
endloop.
I am populating the error messages into workarea using concatenate statement.
Hope this solves the problem.
Reward points if helpful.
Thanks and Regards,
Narayana.

Flat File mapping issue

Hello All,
I am trying to an extract using flat file method in BI 7.0. I have some 150 fields in my CSV file but i wanted is just about 10 which are scattered around in the CSV file.When i Read Preview Data in the Preview tab i see incorrect data in there.And that too all under one tab, basically all under one field , though in the extraction tab for Data Seperator i have been using ; and also tried checking the HEX box, for escape i have the ", tried HEX for this aswell.For rows to ignore i have 1.
One thing i would like to know is how will the BI infoobject know where is the position of the flat file field in the CSV file and where will it be mapped.i know it can be mapped in the Transformations but that is from the flat file datasource, i am asking about the CSV file.
Please help me out and tell me what am i doing incorrectly.
Thanks for your help.Points will be assigned.

hi,
use ,and ; as the escape signs.
system takes care of it when u speicfy the path and name of the file and format as CSV.
always the system checks the one to one mapping of the falt file fields with the infoobject in the datasource.
options for u
1. arrange the neccessary fields in the flat file that exactly maps with infoobjects for mapping. then start loading.
2. keep as such and load with scattered field and in transformation map the required fields alone.
second option consumes more memory space unneccessarily.
For BI 7.0 basic step to laod data from flat (excel files) files for this follow the beloww step-by step directions ....
Uploading of master data
Log on to your SAP
Transaction code RSA1LEAD YOU TO MODELLING
1. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
2. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( master data attributes, text, hierarchies)
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
3. Creation of data targets
In left panel select info provider
Select created info area and right click to select Insert Characteristics as info provider
Select required info object ( Ex : Employee ID)
Under that info object select attributes
Right click on attributes and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.
4. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. Alternatively monitor icon can be used.
BW 7.0
Uploading of Transaction data
Log on to your SAP
Transaction code RSA1LEAD YOU TO MODELLING
5. Creation of Info Objects
In left panel select info object
Create info area
Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
Create new characteristics and key figures under respective catalogs according to the project requirement
Create required info objects and Activate.
6. Creation of Data Source
In the left panel select data sources
Create application component(AC)
Right click AC and create datasource
Specify data source name, source system, and data type ( Transaction data )
In general tab give short, medium, and long description.
In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
In proposal tab load example data and verify it.
In field tab you can you can give the technical name of info objects in the template and you not have to map during the transformation the server will automatically map accordingly. If you are not mapping in this field tab you have to manually map during the transformation in Info providers.
Activate data source and read preview data under preview tab.
Create info package by right clicking data source and in schedule tab click star to load data to PSA.( make sure to close the flat file during loading )
7. Creation of data targets
In left panel select info provider
Select created info area and right click to create ODS( Data store object ) or Cube.
Specify name fro the ODS or cube and click create
From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
Click Activate.
Right click on ODS or Cube and select create transformation.
In source of transformation , select object type( data source) and specify its name and source system Note: Source system will be a temporary folder or package into which data is getting stored
Activate created transformation
Create Data transfer process (DTP) by right clicking the master data attributes
In extraction tab specify extraction mode ( full)
In update tab specify error handling ( request green)
Activate DTP and in execute tab click execute button to load data in data targets.
8. Monitor
Right Click data targets and select manage and in contents tab select contents to view the loaded data. There are two tables in ODS new table and active table to load data from new table to active table you have to activate after selecting the loaded data . Alternatively monitor icon can be used
Ramesh

Error in flat file reconciliation in oim11g on linux.

Hi all,
i am getting following exception in flat file reconciliation of oim 11g on linux machine. Any one please help me out from this error .
*<Apr 19, 2011 12:29:26 PM EDT> <Error> <XELLERATE.WEBAPP> <BEA-000000> <Class/Method: CreateConnectorAction/imageScreen encounter some problems: >*
java.lang.NumberFormatException: null
at java.lang.Long.parseLong(Long.java:375)
at java.lang.Long.parseLong(Long.java:468)
at com.thortech.xl.ejb.beansimpl.tcFormDefinitionOperationsBean.getFormFieldsData(tcFormDefinitionOperationsBean.java:2135)
at com.thortech.xl.ejb.beansimpl.tcFormDefinitionOperationsBean.getFormFields(tcFormDefinitionOperationsBean.java:1694)
at Thor.API.Operations.tcFormDefinitionOperationsIntfEJB.getFormFieldsx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
at $Proxy312.getFormFieldsx(Unknown Source)
at Thor.API.Operations.tcFormDefinitionOperationsIntfEJB_r9z3jf_tcFormDefinitionOperationsIntfRemoteImpl.getFormFieldsx(tcFormDefinitionOperationsIntfEJB_r9z3jf_tcFormDefinitionOperationsIntfRemoteImpl.java:2665)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:84)
at $Proxy188.getFormFieldsx(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:307)
at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:198)
at $Proxy311.getFormFieldsx(Unknown Source)
at Thor.API.Operations.tcFormDefinitionOperationsIntfDelegate.getFormFields(Unknown Source)
at com.thortech.xl.webclient.actions.CreateConnectorAction.imageScreen(CreateConnectorAction.java:1176)
at com.thortech.xl.webclient.actions.CreateConnectorAction.goNext(CreateConnectorAction.java:521)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.apache.struts.actions.DispatchAction.dispatchMethod(DispatchAction.java:269)
at com.thortech.xl.webclient.actions.tcLookupDispatchAction.execute(tcLookupDispatchAction.java:133)
at com.thortech.xl.webclient.actions.tcActionBase.execute(tcActionBase.java:894)
at com.thortech.xl.webclient.actions.tcAction.execute(tcAction.java:213)
at com.thortech.xl.webclient.actions.CreateConnectorAction.execute(CreateConnectorAction.java:135)
at org.apache.struts.chain.commands.servlet.ExecuteAction.execute(ExecuteAction.java:58)
at org.apache.struts.chain.commands.AbstractExecuteAction.execute(AbstractExecuteAction.java:67)
at org.apache.struts.chain.commands.ActionCommandBase.execute(ActionCommandBase.java:51)
at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
at org.apache.commons.chain.generic.LookupCommand.execute(LookupCommand.java:305)
at org.apache.commons.chain.impl.ChainBase.execute(ChainBase.java:191)
at org.apache.struts.chain.ComposableRequestProcessor.process(ComposableRequestProcessor.java:283)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1913)
at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:462)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.XSSFilter.doFilter(XSSFilter.java:103)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.thortech.xl.webclient.security.CSRFFilter.doFilter(CSRFFilter.java:61)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.platform.auth.web.PwdMgmtNavigationFilter.doFilter(PwdMgmtNavigationFilter.java:115)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.iam.platform.auth.web.OIMAuthContextFilter.doFilter(OIMAuthContextFilter.java:100)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:330)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Thank u & regards,
Praveen.

What all are the fields you are bringing from Flat File to OIM ?
It says NumberFormatException which generally comes when you try to convert String (that does not represent a number) into Number. Check your fields and their mapping once again.

Error in flat file

hai...........
If there is a error in 5 th record of flat file.
what happens if we upload that data through session method, whether it stops at 4 th record or except 4 th record all r updated........
and what happens with call transaction .
plz any body give me clear explanation.....?

Dear Satheesh,
If there is error in 4th record,....in (1) Session method:- it skips that records, and all remaining records get uploaded into the system...and u have to go the log thr' SM35, then either u can see error to what screen and to what field by Analyze ro Statistics or Log options from Application Tool bar buttons...and do correction and process them again.......While as in (2) Call Transaction method:- screen gets stucks immediately at the point of error. In this situation, u have to do corrections manually to process that screen ( means u have to filled data for those fields,where error occurs)....I think that this info. will sufficient for you.
Sanjay Bhalerao

Error in Flat File to XML conversion

Hi all,
I am trying to convert a flat file to XML using the Sender File Adapter and I am getting the following error message.
2006-01-23 17:23:00 EST: Error: Conversion of complete file content to XML format failed around position 0: Exception: ERROR converting document line no. 2 according to structure 'GL_FileUpload_SAPECC_Header_DT1':java.lang.Exception: ERROR in configuration: more elements in file csv structure than field names specified!
My flat file looks like this,
--Start
GL,GLI,1,RefTest,4011,Test,1234567890,12032005,12032005,GL,RK
GL,GLI,4011,3011,,,,,,AU,600,7000,8000,9000,5000,RK,,,,,,,,,,,,,,,,,,,,
---End
The adapter configuration is like this:
Document Name: GL_FileUpload_SAPECC_Item_MT1
Document Namespace: urn:corptech.qld.gov.au:sss_std_offering:gl
RecordSet Name: GL_FileUpload_SAPECC_Record_DT1
RecordSet Namespace: urn:corptech.qld.gov.au:sss_std_offering:gl
RecordSet Structure: GL_FileUpload_SAPECC_Header_DT1,1,GL_FileUpload_SAPECC_Item_DT1,*
RecordSet Sequence: Ascending
Key FieldName: TransType
On the Adapter Properties, I have got:
--Start
GL_FileUpload_SAPECC_Header_DT1.fieldNames: TransType,RowType,SequenceNo,ReferenceKey,SenderSystem,HeaderText,CompanyCode,DocumentDate,PostingDate,DocumentType,ReferenceNo
GL_FileUpload_SAPECC_Header_DT1.fieldSeparator: ,
GL_FileUpload_SAPECC_Item_DT1.fieldNames: TransType,RowType,SequenceNo,GLAccount,CostCentre,ProfitCentre,InternalOrder,WBSElement,TaxCode,Currency,GLAmount,VendorAmount,CustomerAmount,AssetAmount,DRCR,ItemText,VendorNo,CustomerNo,Name,Street,City,PostCode,PoBox,State,Country,BankKey,BankAccount,BankCountry,CalcTax,PaymentTerms,BaseDate,PaymentBlock,PaymentMethod,Assignment,AssetNo,AssetSubNo,AssetTransaction
GL_FileUpload_SAPECC_Item_DT1.fieldSeparator: ,
ignoreRecordsetName: true
GL_FileUpload_SAPECC_Header_DT1.keyFieldValue: GL
GL_FileUpload_SAPECC_Item_DT1.keyFieldValue: GL
---End
The structure defined on the data type looks like this,
--Start
GL_FileUpload_SAPECC_Record_DT1   Complex Type
   GL_FileUpload_SAPECC_Header_DT1 Element
      TransType                     Element
      RowType                       Element
      Sequence Number               Element
    GL_FileUpload_SAPECC_Item_DT1   Element
      TransType                     Element
      RowType                       Element
      Sequence Number               Element
      GLAccount                     Element
---End
Any help or suggestion please.
Thank you.
Warm Regards,
Ranjan

Hi, Ranjan.
First of all, let's look at the meaning of the error.
> ...Exception: ERROR converting document line no. 2 according to
> structure 'GL_FileUpload_SAPECC_Header_DT1':java.lang.Exception:
> ERROR in configuration: more elements in file csv structure than
> field names specified!
It seems that XI interpreted 2nd line as
Header_DT1 not as Item_DT1 that you meant.
> GL,GLI,4011,3011,,,,,,AU,600,7000,8000,9000,5000,RK,,,,,,,,,,,,,,,,,,,,
That's why it says this line has more elements than the structure
defined(Header_DT1)
And the reason why XI misinterpreted the above as Header is that
you used keyFieldValue with the same value.
> ...Header_DT1.keyFieldValue: GL
> ...Item_DT1.keyFieldValue: GL
According to the following help,
http://help.sap.com/saphelp_nw04/helpdata/en/2c/181077dd7d6b4ea6a8029b20bf7e55/content.htm
it says like the following.
Key Field Name
If you specified a variable number of substructures for Recordset
Structure, in other words, at least one substructure has the value
*, then the substructures must be identified by the parser from
their content. This means that a key field must be set with different
constants for the substructures. In this case, you must specify a key
field and the field name must occur in all substructures.
How about using different constants for header and item if possible?
Good luck.

Reg : Error in flat file in BDC

hi friends...
let consider 10 records in my flat file...
suppose 5th record is error means
In BDC Session method, what happen records before and after the error record, its get update or not ? like
In BDC Call Transaction method, what happen records before and after the error record, its get update or not ?
please give me some detail...
Regards
Selva

Hi,
In call transaction method you will have an option of Displaying No screens, all screens and Error screens,
If you select No screens all other records except error records will be process and messages will be collected by an internal table of type bdcmsgcoll.
In all screens you need to process each screen manually yourself by selecting the OK code. It is kinda like debugging. So when you encounter the error screen you can change the error data and proceed.
When you select error screens it will stop when the error occurs. So you need to correct the error and continue with the further processing.
Regards,
Pramod

Reg error in flat file to flat file scenario

Hi techies,
Iam just starting working with XI scenarios.
In base flat file to flat file scenario which is mentioned in wiki.sdn
http://wiki.sdn.sap.com/wiki/display/XI/FLATFILETOFLATFILE
I had completed entire scenario. After generating sender file. Iam getting this error in runtime work bench.
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'CONTACTS.EMP.fieldFixedLengths' or 'CONTACTS.EMP.fieldSeparator' is missing
Please suggest how to resolve this error.
Thanks in advance,
Regards,
Kiran

Hi,
From your error description,
Conversion initialization failed: java.lang.Exception: java.lang.Exception: Error(s) in XML conversion parameters found: Parameter 'CONTACTS.EMP.fieldFixedLengths' or 'CONTACTS.EMP.fieldSeparator' is missing
it is clear that you have missed out either or both the 2 parameters in receiver file adapter content conversion, namely EMP.fieldFixedLengths and EMP.fieldSeparator.
From the example that you followed, use the following values for the 2 parameteres is the output file is a comma separated file:
EMP.fieldFixedLengths: 8,10,10
EMP.fieldSeparator: ,
I have assumed that the lengths of the fields NAME,ADD,MOBILE are 8,10 and 10 respectively. Change them according to your requirement.
Use any other value in place of comma(,) in EMP.fieldSeparator according to the requirement.
Hope it helps you buddy!!!
Thanks
Biswajit
Edited by: 007biswa on Feb 22, 2011 9:25 AM
Edited by: 007biswa on Feb 22, 2011 9:28 AM

OWB FLAT FILE MAPPING NOT ABLE TO DEPLOY

Hi,
I've recently started studying data warehousing and exploring the Datawarehouse builder version 3i.
I've created a simple mapping from a csv file to database table ie my source is a flat file and target is a database table. The mapping gets validated successfully and the ctl scrip also gets generated. But the 'Deploy' and "Run' buttons on the "Transformations" tab of the "Generation Results" window are displabled(greyed out) and hence I cannot deploy the generated script.
Please do suggest the cause and solution for the same.
Regards,
Barkha

Many Thanks to Winfred Deering from Oracle who replied:
"This is the expected behavior for flat file mappings. You can register the tcl script with Oracle Enterprise Manager and run it from there. Also you can save the control file and execute via sql loader. "
Thanks and Regards,
Barkha

Flat file mapping problem.

Hi,
I've just created a file mapping, and i'm trying to split a flat file field into 3 subfields for a xml record, but i have the following message:
Before the process run, i've tested the message mapping and the interface mapping, and the log result said that the mapping has been successfully ended, so, Have you ever seen this problem before?
I appreciate your help, thanks.
Marzolla.

Hi Jorge,
Check your XML input. Try to put the same xml instance in the message mapping transformation and test it out.
Regards,
Dhana

Idoc to flat file mapping using XSLT

Hi,
i am using XSLT mapping. my requirement is mapping between idoc and flat file(xml to text). as i do not want to use FCC, i have opted for xslt mapping. please let me know any article which would be helpful for this.
regards,
Meenakshi

Hi Meenakshi,
Two things:
1. Achieving this functionality using XSLT is very difficult.
2. Secondly you may not be able to find a direct document to convert IDoc-XML to flat file using XSLT in sdn. Try google.
I found one link like that may be you can get some idea from there
http://www.stylusstudio.com/SSDN/default.asp?action=9&read=6453&fid=48
Also if you have a XSLT editor like XMLSPY or stylus studio then creating your specific XSLT will b much more simpler
Regards
Suraj

Error in flat file loading in data targets

Hi,
when im loading the data from flat file
"information missing for currency translation into internal format" this error is coming when doing schedule.
can anyone pls help me,im new to SAP BW.
Thanks,
sita

Hi Guptha,
I took 0AMOUNT so 0CURRENCY is assigned automatically.
0currency I kept GBP, INR.
If any solution pls help.
Thanks,
sita
Message was edited by: sita yerram

Error in Flat file loading....

Hi All,
I tried to load data from a flat file, I got the following error :
u201CError in conversion exit CONVERSION_EXIT_CUNIT_INPUTu201D
What does that mean?
Actually when i used ; as the separator it loaded few data fieds, rest all were blank.
and when i used , as separator it was showing the above error.
So i think the problem is in the format of the file.
Can anyone tell me how can i format to overcome this error.?
Thanks in Advance.
Regards,
Chitra.

hi,
check this threads,
Hi, See below link
https://www.sdn.sap.com/irj/sdn/directforumsearch?threadid=&q=conversion_exit_cunit_input&objid=c4&daterange=all&numresults=15&rankby=10001
hope this helps you ..
reagrds,
shikha

Errors in flat file records? how can i handle them?

Hi All,
I am new for BDC. I am uploading customer(XD01) records using BDC caltransaction method.my problem is when i am running the program, some times my program is not updating the records because of my flat file errors. after i correcting the error records and if i run the same program already updated records not processing. my program not running. what i need to do? how can i handle the flat file for reprocessing the error records?
i have around 50,000 records in my flat file.

your program accepts a flat file say the structure of it is structure_load and you create another structure similar to structure_load and name it structure_error.
loop at itab_load.
call transactions...
if success..
commit work and wait X sec.
else.
move-corresponding field to structure_error
append structure_error.
endif.
endloop.
write the file stru_error to PC or app server and make the changes to the data and use the str_error as input to your code again..

Error in flat file mapping

Similar Messages

Maybe you are looking for