Record appending problem in the flat file

Hi everybody,
I am using this code I have to append records one by one(in next line) in a text file, But the records are getting appended side by side how to solve this problem.
code is like this
<%
String varValue="042204ccc";
String loginID="xxxx";
String str= varValue+"="+loginID;
FileWriter fw = new FileWriter(new File("details.txt"),true);
fw.write(str);
fw.close();
%>
thanks in advance.

Better yet, append System.getProperty("line.separator"). That's platform independent.
MOD

Similar Messages

Modifying the number of records to skip after importing the flat file

I imported a flat file and the first row was the column header. I also created an external table for that flat file. The sqlldr is skipping the first record during the load. Is there a way to change this in the flat file module or External table?

If you marked this row as the header in the sample wizard then you will see the following in the External Table:
ACCESS PARAMETERS (
RECORDS DELIMITED BY NEWLINE
CHARACTERSET WE8MSWIN1252
STRING SIZES ARE IN BYTES
NOBADFILE
NODISCARDFILE
NOLOGFILE
SKIP 1
So the external table is skipping this.
Now the issue with changing it is interesting because you cannot change this after the sampling... I think this is a bug which I will file.
Let me know if this answers the question,
Jean-Pierre

Problem Experts OWB 10gR2 - Mapping with OMB - Give a name to the flat file

I'm trying to create a mapping in OWB by using the Experts (OMB),
where the data source is a database table and the target is a flat file (to transform a table to a flat file).
The tasks of my Experts :
This task create a mapping, and add a existing table on it.
     OMBCC '$thepath'
     catch {OMBDROP MAPPING 'M1'}
     OMBCREATE MAPPING 'M1'
     OMBALTER MAPPING 'M1' \
     ADD $INITIAL_LAUNCH_CONTEXT_TYPE OPERATOR '$thetable' \
     BOUND TO $INITIAL_LAUNCH_CONTEXT_TYPE \ '$INITIAL_LAUNCH_CONTEXT' \
This task change the context and create a flat file
     OMBCC '/PRJ_LABO_PHARMA/SRC_FILE'
     catch {OMBDROP FLAT_FILE 'NEW_FILE'}
     OMBCREATE FLAT_FILE 'NEW_FILE' \
     SET PROPERTIES (DATA_FILE_NAME) VALUES('fichier_genere.txt')
This task add the flat file to the mapping, and create a connection between the source (table) and the target (flat file)
     OMBCC '/PRJ_LABO_PHARMA/MOD_SRC_LABO'
     OMBALTER MAPPING 'M1' \
     ADD FLAT_FILE OPERATOR 'NEW_FILE'\
     BOUND TO FLAT_FILE '/PRJ_LABO_PHARMA/SRC_FILE/NEW_FILE' \
     OMBALTER MAPPING 'M1' \
     ADD CONNECTION FROM GROUP 'INOUTGRP1' OF OPERATOR '$thetable' \
     TO GROUP 'NEW_FILE' OF OPERATOR 'NEW_FILE' COPY ALL
This task update the flat file structure
     OMBRECONCILE MAPPING 'M1' OPERATOR 'NEW_FILE' \
     TO FLAT_FILE '/PRJ_LABO_PHARMA/SRC_FILE/NEW_FILE' \
     USE (RECONCILE_STRATEGY 'REPLACE', MATCHING_STRATEGY 'MATCH_BY_OBJECT_ID')
Then I have a task which execute this mapping.
Everything is good, but during the execution I have a error VLD-2357 : The target file's name is not indicated for the file NEW_FILE.
I don't know how to give a name to the flat file in OMB.
Help me please.
Best regards
Samy

Just like if you built this in the UI where you would have to configure the flat file operator and define a target data file name and possibly the location these properties should be set in scripting.
Set the property TARGET_DATA_FILE_NAME to the name of the data file.
Something like....
OMBALTER MAPPING 'M1' \
MODIFY FLAT_FILE OPERATOR 'NEW_FILE' SET PROPERTIES (TARGET_DATA_FILE_NAME) VALUES ('my_datafile.csv')
Cheers
David

Structure of the flat file that uses bapi_po_create1 ?

Hi People,
I am going to create a purchase order using bapi_po_create1 .... to upload the file from legacy to r3 , .what will the stucture of the flat file .......what wil be the key to diffrentiate diiferent purchase orders. ( for eg : IN vendor master ........vendor number will be the key to diffrentiate the records , as we all know the purchase order will be created only at the end of the transaction..so what will be the key to diffrentitate each po record )

Hi Siva,
Check the Code below. You can refer the fields to prepare the input File .
*& Report YDM_PO_CREATE1                                               *
REPORT ydm_po_create1.
*-- Input File Declaration
TYPES: BEGIN OF ty_input_file,
       column1 TYPE char50,
       column2 TYPE char50,
       column3 TYPE char50,
       column4 TYPE char50,
       column5 TYPE char50,
       column6 TYPE char50,
       column7 TYPE char50,
       column8 TYPE char50,
       column9 TYPE char50,
       column10 TYPE char50,
       column11 TYPE char50,
       column12 TYPE char50,
       column13 TYPE char50,
       column14 TYPE char50,
       column15 TYPE char50,
       column16 TYPE char50,
       column17 TYPE char50,
       column18 TYPE char50,
END OF ty_input_file.
DATA: i_input_file TYPE STANDARD TABLE OF ty_input_file,
      wa_input_file TYPE ty_input_file.
CONSTANTS: c_path     TYPE char20 VALUE 'C:\',
           c_mask     TYPE char9 VALUE ',*.*,*.*.',
           c_mode     TYPE char1 VALUE 'O',
           c_filetype TYPE char10 VALUE 'ASC',
           c_x        TYPE char01 VALUE 'X'.
PARAMETERS : p_fname   LIKE rlgrap-filename.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
*-- Browse Presentation Server
PERFORM f4_presentation_file.
START-OF-SELECTION..
*-- Read presentation server file
PERFORM f1003_upload_file.
IF NOT i_input_file[] IS INITIAL.
    PERFORM split_data.
ENDIF.
*&                  Form f4_presentation_file
*&                F4 Help for presentation server
FORM f4_presentation_file .
CALL FUNCTION 'WS_FILENAME_GET'
    EXPORTING
      def_path         = c_path
      mask             = c_mask
      mode             = c_mode
      title            = text-001
    IMPORTING
      filename         = p_fname
    EXCEPTIONS
      inv_winsys       = 1
      no_batch         = 2
      selection_cancel = 3
      selection_error = 4
      OTHERS           = 5.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
ENDFORM.                    " f4_presentation_file
*&                      Form f1003_upload_file
*&                         Upload File
FORM f1003_upload_file .
DATA: lcl_filename TYPE string.
lcl_filename = p_fname.
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      filename                = lcl_filename
      filetype                = c_filetype
      has_field_separator     = c_x
    TABLES
      data_tab                = i_input_file
    EXCEPTIONS
      file_open_error         = 1
      file_read_error         = 2
      no_batch                = 3
      gui_refuse_filetransfer = 4
      invalid_type            = 5
      no_authority            = 6
      unknown_error           = 7
      bad_data_format         = 8
      header_not_allowed      = 9
      separator_not_allowed   = 10
      header_too_long         = 11
      unknown_dp_error        = 12
      access_denied           = 13
      dp_out_of_memory        = 14
      disk_full               = 15
      dp_timeout              = 16
      OTHERS                  = 17.
IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
            WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    EXIT.
ENDIF.
ENDFORM.                    " f1003_upload_file
*&      Form split_data
      Collect data for creating Purchase Order
FORM split_data .
DATA: i_poitem        TYPE STANDARD TABLE OF bapimepoitem,
        i_poitemx       TYPE STANDARD TABLE OF bapimepoitemx,
        i_poitem_sch    TYPE STANDARD TABLE OF bapimeposchedule,
        i_poitem_schx   TYPE STANDARD TABLE OF bapimeposchedulx,
        i_acct_***      TYPE STANDARD TABLE OF bapimepoaccount,
        i_acct_assx     TYPE STANDARD TABLE OF bapimepoaccountx,
        i_services      TYPE STANDARD TABLE OF bapiesllc ,
        i_srvacc        TYPE STANDARD TABLE OF bapiesklc,
        i_return        TYPE STANDARD TABLE OF bapiret2,
        wa_header       TYPE bapimepoheader,
        wa_headerx      TYPE bapimepoheaderx,
        wa_poitem       TYPE bapimepoitem,
        wa_poitemx      TYPE bapimepoitemx,
        wa_poitem_sch   TYPE bapimeposchedule,
        wa_poitem_schx TYPE bapimeposchedulx,
        wa_acct_***     TYPE bapimepoaccount,
        wa_acct_assx    TYPE bapimepoaccountx,
        wa_services     TYPE bapiesllc,
        wa_srvacc       TYPE bapiesklc,
        wa_return       TYPE bapiret2,
        ws_po           TYPE bapimepoheader-po_number.
wa_services-pckg_no = 10.
wa_services-line_no = 1.
wa_services-outl_no = '0'.
wa_services-outl_ind = c_x.
wa_services-subpckg_no = 20.
APPEND wa_services TO i_services.
wa_srvacc-pckg_no = 10.
wa_srvacc-line_no = 1.
wa_srvacc-serno_line = 01.
wa_srvacc-serial_no = 01.
wa_srvacc-percentage = 100.
APPEND wa_srvacc TO i_srvacc.
LOOP AT i_input_file INTO wa_input_file.
    IF wa_input_file-column2 EQ 'HD'.
      wa_header-doc_type = wa_input_file-column3.
      wa_header-creat_date = sy-datum.
      wa_header-created_by = sy-uname.
      wa_header-vendor = wa_input_file-column4.
      PERFORM conversion_output USING wa_header-vendor
                                CHANGING wa_header-vendor.
      wa_header-comp_code = 'DE03'.
      wa_header-purch_org = 'DE03'.
      wa_header-pur_group = 'DE1'.
      wa_header-vper_start = wa_input_file-column9.
      wa_header-vper_end = wa_input_file-column10.
      wa_headerx-comp_code = c_x.
      wa_headerx-doc_type = c_x.
      wa_headerx-creat_date = c_x.
      wa_headerx-created_by = c_x.
      wa_headerx-vendor = c_x.
      wa_headerx-purch_org = c_x.
      wa_headerx-pur_group = c_x.
      wa_headerx-vper_start = c_x.
      wa_headerx-vper_end = c_x.
    ENDIF.
    IF wa_input_file-column2 EQ 'IT'.
      wa_poitem-po_item = wa_input_file-column3.
      wa_poitem-short_text = wa_input_file-column6.
      wa_poitem-plant = wa_input_file-column8.
      wa_poitem-quantity = '1'.
      wa_poitem-tax_code = 'V0'.
      wa_poitem-item_cat = 'D'.
      wa_poitem-acctasscat = 'K'.
      wa_poitem-matl_group = wa_input_file-column7.
      wa_poitem-pckg_no = '10'.
      APPEND wa_poitem TO i_poitem .
      wa_poitemx-po_item = wa_input_file-column3.
      wa_poitemx-po_itemx = c_x.
      wa_poitemx-short_text = c_x.
      wa_poitemx-plant = c_x.
      wa_poitemx-quantity = c_x.
      wa_poitemx-tax_code = c_x.
      wa_poitemx-item_cat = c_x.
      wa_poitemx-acctasscat = c_x.
      wa_poitemx-matl_group = c_x.
      wa_poitemx-pckg_no = c_x.
      APPEND wa_poitemx TO i_poitemx.
      wa_poitem_sch-po_item = wa_input_file-column3.
      wa_poitem_sch-delivery_date = sy-datum.
      APPEND wa_poitem_sch TO i_poitem_sch.
      wa_poitem_schx-po_item = wa_input_file-column3.
      wa_poitem_schx-po_itemx = c_x.
      wa_poitem_schx-delivery_date = c_x.
      APPEND wa_poitem_schx TO i_poitem_schx.
      wa_acct_***-po_item = 10.
      wa_acct_***-serial_no = 01.
      wa_acct_***-gl_account = '0006360100'.
      wa_acct_***-co_area = '1000'.
      wa_acct_***-costcenter = 'KC010000'.
      APPEND wa_acct_*** TO i_acct_***.
      wa_acct_***-po_item = 10.
      wa_acct_***-serial_no = 02.
      wa_acct_***-gl_account = '0006360100'.
      wa_acct_***-co_area = '1000'.
      wa_acct_***-costcenter = 'KC010000'.
      APPEND wa_acct_*** TO i_acct_***.
      wa_acct_assx-po_item = 10.
      wa_acct_assx-serial_no = 01.
      wa_acct_assx-po_itemx = c_x.
      wa_acct_assx-serial_nox = c_x.
      wa_acct_assx-gl_account = c_x.
      wa_acct_assx-co_area = c_x.
      wa_acct_assx-costcenter = c_x.
      APPEND wa_acct_assx TO i_acct_assx.
      wa_acct_assx-po_item = 10.
      wa_acct_assx-serial_no = 02.
      wa_acct_assx-po_itemx = c_x.
      wa_acct_assx-serial_nox = c_x.
      wa_acct_assx-gl_account = c_x.
      wa_acct_assx-co_area = c_x.
      wa_acct_assx-costcenter = c_x.
      APPEND wa_acct_assx TO i_acct_assx.
      wa_services-pckg_no = 20.
      wa_services-line_no = 2.
      wa_services-service = wa_input_file-column9.
      wa_services-quantity = '100'.
      wa_services-gr_price = '100'.
      wa_services-userf1_txt = wa_input_file-column13.
      APPEND wa_services TO i_services.
      wa_srvacc-pckg_no = 20.
      wa_srvacc-line_no = 1.
      wa_srvacc-serno_line = 02.
      wa_srvacc-serial_no = 02.
      wa_srvacc-percentage = 100.
      APPEND wa_srvacc TO i_srvacc.
    ENDIF.
ENDLOOP.
CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
      poheader                     = wa_header
      poheaderx                    = wa_headerx
POADDRVENDOR                 =
TESTRUN                      =
MEMORY_UNCOMPLETE            =
MEMORY_COMPLETE              =
POEXPIMPHEADER               =
POEXPIMPHEADERX              =
VERSIONS                     =
NO_MESSAGING                 =
NO_MESSAGE_REQ               =
NO_AUTHORITY                 =
NO_PRICE_FROM_PO             =
   IMPORTING
     exppurchaseorder             = ws_po
EXPHEADER                    =
EXPPOEXPIMPHEADER            =
   TABLES
     return                       = i_return
     poitem                       = i_poitem
     poitemx                      = i_poitemx
POADDRDELIVERY               =
     poschedule                   = i_poitem_sch
     poschedulex                  = i_poitem_schx
     poaccount                    = i_acct_***
POACCOUNTPROFITSEGMENT       =
     poaccountx                   = i_acct_assx
POCONDHEADER                 =
POCONDHEADERX                =
POCOND                       =
POCONDX                      =
POLIMITS                     =
POCONTRACTLIMITS             =
     poservices                   = i_services
     posrvaccessvalues            = i_srvacc
POSERVICESTEXT               =
EXTENSIONIN                  =
EXTENSIONOUT                 =
POEXPIMPITEM                 =
POEXPIMPITEMX                =
POTEXTHEADER                 =
POTEXTITEM                   =
ALLVERSIONS                  =
POPARTNER                    =
break gbpra8.
LOOP AT i_return INTO wa_return.
ENDLOOP.
ENDFORM.                    " split_data
*&      Form conversion_output
      Conversion exit input
FORM conversion_output USING    p_ip
                        CHANGING p_op.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
    EXPORTING
      input = p_ip
    IMPORTING
      output = p_op.
ENDFORM.                    " conversion_output
Also suggest you to search in SDN with key - BAPI_PO_CREATE1. Will get more useful links.
Hope this helps.
Manish

Error while loading data into External table from the flat files

HI ,
We have a data load in our project which feeds the oracle external tables with the data from the Flat Files(.bcp files) in unix.
While loading the data, we are encountering the following error.
Error occured (Error Code : -29913 and Error Message : ORA-29913: error in executing ODCIEXTTABLEOPEN callout
ORA-29400: data cartridge error
KUP-04063: un) while loading data into table_ext
Please let us know what needs to be done in this case to solve this problem.
Thanks,
Kartheek

Kartheek,
I used Google (mine still works).... please check those links:
http://oraclequirks.blogspot.com/2008/07/ora-29400-data-cartridge-error.html
http://jonathanlewis.wordpress.com/2011/02/15/ora-29913/
HTH,
Thierry

BAPI_PO_CREATE1 not able to create PO's for multiple rows from the flat fil

Hi
i am uploading PO's from a flat file into SAP using the BAPI_PO_CREATE1. Everything works fine if the flat file hast only one record.
if the flat file has more than one record then while loading the second record the BAPI returns a error message. I am calling the BAPI in a loop.
The strange thing is that if i load the second record individually the program is able to create the PO. So only when i have multiple records in the flat file i am unable to load the PO into SAP. I debugged and checked all the internal tables passed to the BAPI. All seems to have the data correctly but still the BAPI fails.
any idea where i am going wrong?
the code looks something like this.
LOOP AT HEADER_ITAB.
   PERFORM FILL_HEADER_RECORDS.
LOOP AT ITEM_ITAB WHERE EBELN eq HEADER_ITAB-EBELN.
     PERFORM FILL_ITEM_RECORDS.
ENDLOOP.
PERFORM CERATE_PO_VIA_BAPI.
ENDLOOP.

What is the error message. Are you trying something like this:
    LOOP AT T_DATA1.
      AT NEW LIFNR.
        READ TABLE T_DATA1 INDEX SY-TABIX.
        PERFORM INIT_TABLES.
        PERFORM FILL_DATA.
--Call the BAPI to create PO
        PERFORM CREATE_PO.
      ENDAT.
    ENDLOOP.
FORM CREATE_PO .
CALL FUNCTION 'BAPI_PO_CREATE1'
    EXPORTING
      POHEADER                     =   POHEADER
      POHEADERX                    =   POHEADERX
    POADDRVENDOR                 =
    TESTRUN                      =
    MEMORY_UNCOMPLETE            =
    MEMORY_COMPLETE              =
    POEXPIMPHEADER               =
    POEXPIMPHEADERX              =
    VERSIONS                     =
    NO_MESSAGING                 =
    NO_MESSAGE_REQ               =
    NO_AUTHORITY                 =
    NO_PRICE_FROM_PO             =
   IMPORTING
     EXPPURCHASEORDER             = EXPPURCHASEORDER
     EXPHEADER                    = EXPHEADER
     EXPPOEXPIMPHEADER            = EXPPOEXPIMPHEADER
   TABLES
     RETURN                       = RETURN
     POITEM                       = POITEM
     POITEMX                      = POITEMX
    POADDRDELIVERY               =
     POSCHEDULE                   = POSCHEDULE
     POSCHEDULEX                  = POSCHEDULEX
     POACCOUNT                    = POACCOUNT
    POACCOUNTPROFITSEGMENT       =
     POACCOUNTX                   = POACCOUNTX
    POCONDHEADER                 =
    POCONDHEADERX                =
     POCOND                       = POCOND
     POCONDX                      = POCONDX
    POLIMITS                     =
    POCONTRACTLIMITS             =
    POSERVICES                   =
    POSRVACCESSVALUES            =
    POSERVICESTEXT               =
    EXTENSIONIN                  =
    EXTENSIONOUT                 =
    POEXPIMPITEM                 =
    POEXPIMPITEMX                =
    POTEXTHEADER                 =
      POTEXTITEM                   = POTEXTITEM
    ALLVERSIONS                  =
     POPARTNER                    = POPARTNER
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    EXPORTING
      WAIT   = 'X'
    IMPORTING
      RETURN = RETURN1.
DATA: L_NAME TYPE LFA1-NAME1.
CLEAR L_NAME.
SELECT SINGLE NAME1
           FROM LFA1
           INTO L_NAME
           WHERE LIFNR = POHEADER-VENDOR.
LOOP AT RETURN.
    WRITE : / RETURN-TYPE,
              RETURN-ID,
              RETURN-MESSAGE.
    WRITE : '--> For vendor:',
             POHEADER-VENDOR,
             L_NAME.
ENDLOOP.
ENDFORM.                    " CREATE_PO

Urgent: Problem to load Flat file using DTP.

Hi Experts,
I try to load a flat file PSA->DSO->INFOCUBE using DTP.
I my flatfile in the application server in csv format.
in the My data source I opted Adapter as Load Text -Type file from Application Server.
Data Format : I test with both the potions : Fixed length & Separated with Separator( For example CSV) .
If I check the preview: I cant find any data and get the message: Inbound processing of data package 000001 finished
when I try to Load the data thorough PC the load was successfull but only 0 records are transfered and added to PSA:; DSO and Info Cube.
The test file contains around 20 records.
Any suggestions please.
Thanks & Regards

Hi Sailekha..
in the My data source I opted Adapter as Load Text -Type file from Application Server.
Data Format : I test with both the potions : Fixed length & Separated with Separator( For example CSV) .
Note: As per ur info:
In the Flat file Data source :
1. You have to maintain the Adapter as:
Load Text -Type file from Application Server
Data Format : Separated with Separator
Then Use the "Proposal" Tab to generate the field proposals.
(Only in BI 7.0 this option is available).
After that check the Preview in "Preview" Tab.
Hope it works...
Cheers,...
Varma

Unable to load the flat file from client work station

Hi,
I am trying load a flat file (.CSV file)from my desktop (Client work station) and getting the following error.
An upload from the client workstation in the background is not possible
Message no. RSM860
Diagnosis
You cannot load data from the client workstation in the background.
Procedure
Transfer your data to the application server and load it from there.
I have recd a .XLS file and then I have converted to .CSV file , which I saved in my desktop and trying to load the same.
Please help me how to go about this?...
Thanks in advance.
Christy.

Hi All,
Again, I have tried to load the flat file from clint work station with direct loading..I have got the following errors..
Errors : 1
Record 990: Contents '50,000' from Field /BIC/ZPLQTY_B Not Convertible in Type QUAN -> Long Tex
like this i recd so many errors.
ERROR : 2
Error in an arithmetic operation in record 259
Please help me how to load the flat file successfully.
If I hv to save the flat file in Appl server..how to do that..Please provide step by step instruction..
Thanks
Christy

Getting a error when loading the flat file

Hi,
I have created a infoobject called ID and i have a attribute name.I have assigned a data source and done the update rules.When i try to upload the flat file i get a error.
Error 8 when compiling the upload program: row 227, message: A newer version of data type /BIC/CCDHIO_SRPID_ATT
I have faced this problem earlier but now i am not able to rectify it .Can someone suggest me what to do.I am working on 3.5 version.
Thanks
Regards
Harish

Hi,
Check the Flatfile Infoobjects and in datasource structure ,It should be same order and check whther you you are ignoring header rows or not in infopackage
Regards,
Marasa.

Conversion_Exit_Cunit_error occured while loading the Flat file data

Hi
Iam tryign to load Flat file data into an ODS, i am getting error like Error Conversion Cunit.
Also we are using 0unit in the ODS for which CUNIT is a conversion rule
Can you please suggest me why iam getting this error

Hi Sunil
Hope you can check whether you are loadig the flat file data from application server or Client workstation.
May be if you are loading from Client work station you will face problem of this type.
Try to check if any change in format in the file.
at the end of the file delete the spaces.

Error message while uploading the flat file

Hi Experts,
I am getting the error message while uploading the flat file.
Message class: MG
Number: 147
The message is: Several descriptions exist for the language JA.
Please guide me why this error is occuring.
Regards
Akshay

hi,
how are you uploading the file and where ?
u can use open dataset , read dataset or gui_upload
check this link
http://help.sap.com/saphelp_nw04/helpdata/en/c8/e92637c2cbf357e10000009b38f936/frameset.htm

Different formats of the flat file for the same target

In our deployment, we use plugin code to extract the csv files in the required format. The customers are on same version of datamart, but they are on different versions of source database - from 3.x to 4.5 depending on which version of application they are using. In 4.0, we introduced a new column email in the user table in the source database. Accordingly, plugin will add the field in the csv file. But not all the customers will get the upgraded version of plugin at the same time. So ETL code needs to decide which data flow to process depending on the format of the csv file to load data to the same target table. I made the email field in the target table nullable but it still expects the same format of the csv file with delimiter for null value.
Need help to achieve this. Can I read the structure of the flat file in DS or get the count of delimiters so that I can use a conditional to use different data flow based on the format of the flat files.
Can I make the email column in the flat file optional?
Thanks much in advance.

You can add an email column that maps to null in a query transform for the source that does not contain this column.
Or else you can define two different file formats that map to the same file. One with the column and one without

Date and Time in the flat file

Hi All,
I am trying to design a flow which will get data from a flat file. The file has a field which contains both the time and date. How can I handle this in BW? Do I need to creat 2 infoobjects and split the flat file field in start routine or transfer rule? Or is there any stadard infoobject which can hold both the data and time?
Also, the client asked me if I want a .CSV file or .XLS file. Which one is better for uploading into BW? Any PROS and CONS?
Best Regards,

Hi,
There is no single Data Type which accepts the Date and Time. Other way is to look the data as CHAR. Else the Update Routine/Formula is the Best
In the Update Rule or Transfer Rule use the Formula
Let the Info Objects be
0date
0Time
The Transfer Rule/ Update Rule Formulas Be
0Date --> LEFT( 8, 'DateTime' )
0Time --> RIGHT(6, 'DateTime')
Then CSV is the best Option to accept the Data as it is ready for Upload
Regards
Happy Tony

How to store the flat file data into custom table?

Hi,
Iam working on inbound interface.Can any one tell me how to store the flat file data into custom table?what is the procedure?
Regards,
Sujan

Hie
u can use function
F4_FILENAME
to pick the file from front-end or location.
then use function
WS_UPLOAD
to upload into
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
CALL FUNCTION 'F4_FILENAME'   "Function to pick file
    EXPORTING
      field_name = 'p_file'     "file
    IMPORTING
      file_name = p_file.     "file
CALL FUNCTION 'WS_UPLOAD'
   EXPORTING
     filename                       = p_file1
    TABLES
      data_tab                      = it_line
*then loop at it_line splitting it into the fields of your custom table.
loop at it_line.
          split itline at ',' into
          itab-name
          itab-surname.
endloop.
then u can insert the values into yo table from the itab work area.
regards
Isaac Prince

Convert the flat file to xml format.

hi,
I need to write a interface program in the R/3 to pull the flat file data from the unix application server and do some manipulation and place back into the unix application server in XML format, From the unix box XML file taken by the XI server.
pls give me some idea to convert the flat file to XML format, through any function module or any other logic is there...
with regards,
Thambee.

Hi Thambe
in addition to the above posts
Program to convert flat file to XML file.
please download tool from this link:
http://www.download.com/Stylus-Studio-2008-XML-Enterprise-Suite/3000-7241_4-10399885.html?part=dl-StylusStu&subj=dl&tag=button&cdlpid=10399885
how to use:
http://www.stylusstudio.com/learn_convert_to_xml.html
http://www.sap-img.com/abap/sample-xml-source-code-for-sap.htm
Flat file to XML
CONVERTION OF FLAT FILE TO XML : NO OUT PUT FOUND
Converting Idoc flat file representation to XML
how to convert flat file into IDOC-XML
Thanks
sandeep sharma
PS ; if helpful kindly reward points

Record appending problem in the flat file

Similar Messages

Maybe you are looking for