Error in flat file uploading

Hi
II upload a flat file with datas like "Order No" whitch is stored as De/12/Ce/1435, and "Date" stored as 1999-02-12. But when I look a preview I see "Order No" converted to number something like 000000001000000234 and "Date" is cut to only 1999-02-
The file is a .csv separated with comas.
After uploading it is in DSO and DAtaCube that way. How to solve that?

Hi,
The problem may be with the flat file. Just have only one record in the flat file. Open the CSV flat file in Notepad see what is the data displayed. If mappings are done correctly, the data displayed in notepad output will be loaded exactly into data target.
Just try with one record.
Regards
Akhan

Similar Messages

  • Error in flat file upload

    Dear All,
    I am uploading from a flat file source system and it give me an error saying IDOC type for sourcesystem is not available is this purely an basis problem or is there anything I can do about it.
    Thanks &Regards,
    Vinay.

    Hello,
    Check the Log in sm21 (for all servers). Did any short dumps reported for the failure (st22).
    what exactly is the error reported in RSMO?
    Please give us error in detail.
    Thanks and Regards,
    Harish

  • Does any one know how to resolve the error while flat file upload

    Hey guys, I am so struck with this problem, please do let me know if anyone has any suggestions and ideas.
    1. I created three InfoObjects, Material Number, Name and Price,which is  a keyfigure and has data type DEC and fixed currency USD.
    Material Number is "With Master Data ", "With Text" and i added Name and Price as attributes to that.
    2.
    After that i created an Application component, and therafter a data source for Master data Attibutes.
    Now i select my flat file which is .csv file, in this data source. When I click "Load Example Data", i get all the fields from flat file, but the data type for PRICE changes to FLTP with length 16 instead of remaining DEC.
    Does anyone have any idea why on earth is this change of Data type taking place ?
    Please do me a favour by answering if you know about this problem. Thanks, appreciate it . Byee. And yeah, m just starting off in SAP so I am a total amateur unlike most of the people here.

    Am workin on BI 7.0.
    Let me put it in another way :
    Created Infoobjects:      1) Material No , 2) Material Name  3 ) Price which is the Key Figure
    Material No -
    has attributes Material Name and Price and " WIth Master Data", With ' Text"
    Price: -
    data type DEC, fixed currency - USD
    After doing things.
    Created Application Component:
    then, Right Click - Create Data Source,
    Selected -- Master Data Attributes
    After that from "EXTRACTIO' tab , selected the flat file, which is *.csv
    and then in DATA FORMAT - " SEPERATED WITH SEPERATOR"
    Then from "PROPOSAL" tab, when i click Load example data, the data from flat file shows up here, but the field PRICE now has Data Type -- " FLTP" and lenght "16"
    I hope i was clear enough. thanks

  • Error in Flat files upload

    I have a week of history data and I am trying to upload it but I got this error;
    Error in conversion exit
    CONVERSION_EXIT_CUNIT_INPUT
    when I diagonis this error the detail tell me that:
    An error occurred in record                                                   1 during execution ofconversion exit CONVERSION_EXIT_CUNIT_INPUT for field ME_UN_ADSP.
    The actual field I am using is '0ME_UN_ADSP' in my Infosource. I have no idea. what's wrong. could anyone please explain me. Thank you.

    Hello everybody I have another error while loading Transactional Data CSV and ASCII in a transactional Info Cube. I get either Error 1, 4, or Error 8 after in the Schedule Tab the Start button is hit. I have BW 3.5, and well, this is the complete text for Error 1, yes I have checked that everything matches of what have been defined in the info catalogs and transfer rules, update rules, and communication structure.
    Again this is not a problem of format of data, since i have used the same file in other uploads, but not in BW 3.5, is there any patch that i need to apply?
    Error 1 when loading external data
    Message no. RSAR234
    Diagnosis
    Error number 1 occurred when loading external data:
    1. Error when reading the file (access rights, file name, ...)
    2. File size or number of records does not correspond to the data in the control file
    3. Error when generating the IDoc
    4. File contains invalid data (errors with an arithmetic operation or data conversion)
    Procedure
    Check whether you have the required access rights and whether the data in the control file is correct (file names, record length, number of records, ...). Correct the data in the control file if necessary and check the data file for invalid data (values of the wrong type, values in the wrong format for conversion exit,...). Check whether the file has headers that have not been specified.

  • BPS  Flat File Upload Error Messages

    Hi,
    I am using the BPS flat file upload and am getting error messages. These error messages are coming from the user exit in the characteristics relationships. Unfortunately the message does not indicate which line on the upload file the error is for. In the user exit it does not pass the line no of  the flat file that is being processed.
    Does anyone have any ideas how the message could be enhanced to indicate the line in error or if there is another exit I could perform the validation in?
    regards
    Paul Cairncross

    Hi Sai,
    The issue is not the particular message. The message is in fact my message in the user exit in the characteristic relationships. The issue is when using the flat file upload the message does not indicate which line in the file the message apply's to. Looking at the userexit no line number is passed. This is not a problem in the web as the specific line is highlighted when the user is keying in the data.
    Regards,
    Paul Cairncross

  • Flat file upload error message

    Hi Friends
    I have designed an infocube and when i try to load data after selecting the option of flat file upload, i get the following error message," You have no authorization for basic types(activity 03)". Please clarify what it means.
    regards
    kris

    hi Kris,
    it may due to lack of authorization, please run transaction su53 and capture the info to your basis team to add you the needeed authorization.
    hope this helps.

  • 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 Upload BSP page

    Hi Marc,
    I am following the July version of how-to. When generating the BSP page, I am told checkbrowser.htm and js.htm are not available. When I create a checkbrowser.htm and point the include to js3.htm, which is one of the page fragment available, there are a few other errors coming out. What am I missing?

    Do you already know if the flat file upload is possible from a multi planning area? Because I get the error message that my multi planning area does not exist when executing the function.
    Thnx.

  • Problem in Flat File Uploading

    Hi everyone
    During a flat file uploading, I get a message for each record of my SKU (Stock Keeping Unit), for eg for SKU 1017023, I got a message
    <b>Value '1017023 ' for characteristic PISKU is in external format     RRSV     9</b>
    PISKU is the field name.
    The whole extraction is failing.
    Kindly provide me some suggestions as soon as poosible!!
    If possible mail me at
    [email protected]
    Regards
    Gajendra Singh

    Hi,
    It seems there is a space in the value '1017023 '.You have to edit in PSA and then send it again else delete the request and change the flat file entry and reload the data.
    Hope this helps
    Assign points if useful
    Regards,
    venkat

  • How To guide...for Flat File upload for User-Defined variables

    Has anyone got link to the guide that describes how to do a flat file upload for populating User-Defined Variables ?
    Any assistance will be appreciated.
    Uche

    SAP BW Business Planning and Simulation "How To" Guides
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/ab9fd590-0201-0010-2590-be78eb70015c
    How to Upload User-Specific Variable Selections in BW-BPS
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/documents/a1-8-4/how to upload user-specific variable selections in bw-bps.pdf
    this is what you are looking for ?
    Message was edited by: Murali

  • Create a flat-file upload for a BO XAI Inbound Service?

    Hello all,
    If we don't have a schema defined for a BO XAI Inbound Service, how can we create the XSL and the flat-file upload schema file for it.
    Any advice?
    Regards,
    Kerr

    I don't have problem to create the XSLT mapping.
    But because it is to create a flat-file upload for a Business Object XAI Inbound Service, it doesn't have a schema on the server as to the thread Create Schema for Business Object to use for XAI Inbound Service?
    And I can't create that flat-file upload without a schema on the server.
    Or I can use the BO XAI Inbound Service WSDL instead to create the mapping for the flat-file upload.
    Regards,
    Kerr

  • FLAT FILE UPLOAD INTO BI

    Hi,
    What kind of questions are needed to be asked (from client) for requirements gathering for a flat file upload (from legacy system) to BI? Basically what are all the questions that i need to ask them to make sure I have all information for designing a flat file extractor?
    Thanks

    I would ask them what do they want to report on from the legacy system and is data already in R/3?  I would also ask what kind of data is stored in the legacy system .... inventory, financial data, sales, etc ... Once I knew that, I would ask what do they want to report on .... stock quantities/costs, gl account data, revenue, deliveries, etc....
    Then I would ask, do you want this to be seperated from the R/3 datastream?  More than likely this will be yes, if not, fight to keep it seperated and possible in it's own cube/ODS and combine in a multiprovider (you need to use the same 0material, 0customer, 0vendor, 0gl_account info objects if you want to combine nicely on a multiprovider).
    If the database the legacy system is on is either SQL Server or Informix or Oracle, you may want to consider DBConnect and connect directly to their tables.
    In all cases, I try to avoid bringing everything in "just because we may need it".  If the system is legacy and it's been a legacy for 2 years, see what people keep going back for and grab that data only.  If someone claims to need data, but have not sought it out for 2 years, then the probably don't need it.
    Also, check the granularity of the data.  Do they need individual documents for legal reasons?  Can you summarize the data?  What are they going to use the data for?
    Brian

  • BPC delta flat file upload possible?

    Hi experts,
    Ive been trying to find an answer of whether or not it is possible to retain member data on manual flat file upload into a dimension. We have created a dimension (employee) and have created some dummy nodes member data and would like to determine if it is possible to then keep this manual member data while manually loading further member data through flat file load. Is this sort of manual flatfile delta load possible? If so how? What is best practice here?
    Also, is it possible to load data into a dimension using two methods IE manual upload file and then another form (IE BW load) without overwriting data? Im assuming this is where the merge data option comes in to play.
    Any guidance would be much appreciated.
    Regards,
    Danielle

    Hi Danielle,
    While uploading data, if you have added dimension members manually, then, it never gets deleted untill and unless you specify for it.
    In your scenario, you have created dummy members and want to upload data thru flat file. Then, the data will be uploaded only for those members for which you want to upload data, rest of the members will display the old data.
    As you rightly said earlier, while running data manager package, you need to select MERGE option instead of REPLACE & CLEAR data values. This keeps the old data intact and adds the new ones as well.
    Hope this clarifies further.
    Rgds,
    Poonam

  • Beginner - Flat file upload error Help Please

    Hi Everyone,
    I am trying to upload a flat file [.csv] for the first time.
    I created Info objects  Material Id, Material Name , Price as keyfigure.
    Material Id holds Material Name and Price as attributes and is With Text and With Master Data.
    For the Keyfigure, Price, I have selected Amount and defined as USD.
    In the flat file, i have Material id, Material Name, Price, Description for Text, its something like this
    Mid         M-Name   Price      DESCRIPTION
    10001     A              99.99     AA
    When I create an Application Component and thereafter create a data source for master data attributes for Material
    and select the flat file and upload it, then the data types for Keyfigure PRICE changes to FLTP Length 16, its no longer as DEC and i get some werid data for Price field, something like
    "99.990000000001E+02" instead of 99.99.   Why am I having this problem and how could this be resolved ?
    I thought i would start off with my best foot forward but it didnt work. Any kind of help would be highly appreciated. Thanks guys..Byee

    hi,
    these are the BI.7 steps
    BW 7.0
    Uploading of master data
    Log on to your SAP
    Transaction code RSA1u2014LEAD YOU TO MODELLING
    1. Creation of Info Objects
    u2022 In left panel select info object
    u2022 Create info area
    u2022 Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
    u2022 Create new characteristics and key figures under respective catalogs according to the project requirement
    u2022 Create required info objects and Activate.
    2. Creation of Data Source
    u2022 In the left panel select data sources
    u2022 Create application component(AC)
    u2022 Right click AC and create datasource
    u2022 Specify data source name, source system, and data type ( master data attributes, text, hierarchies)
    u2022 In general tab give short, medium, and long description.
    u2022 In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
    u2022 In proposal tab load example data and verify it.
    u2022 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.
    u2022 Activate data source and read preview data under preview tab.
    u2022 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
    u2022 In left panel select info provider
    u2022 Select created info area and right click to select Insert Characteristics as info provider
    u2022 Select required info object ( Ex : Employee ID)
    u2022 Under that info object select attributes
    u2022 Right click on attributes and select create transformation.
    u2022 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
    u2022 Activate created transformation
    u2022 Create Data transfer process (DTP) by right clicking the master data attributes
    u2022 In extraction tab specify extraction mode ( full)
    u2022 In update tab specify error handling ( request green)
    u2022 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 RSA1u2014LEAD YOU TO MODELLING
    5. Creation of Info Objects
    u2022 In left panel select info object
    u2022 Create info area
    u2022 Create info object catalog ( characteristics & Key figures ) by right clicking the created info area
    u2022 Create new characteristics and key figures under respective catalogs according to the project requirement
    u2022 Create required info objects and Activate.
    6. Creation of Data Source
    u2022 In the left panel select data sources
    u2022 Create application component(AC)
    u2022 Right click AC and create datasource
    u2022 Specify data source name, source system, and data type ( Transaction data )
    u2022 In general tab give short, medium, and long description.
    u2022 In extraction tab specify file path, header rows to be ignored, data format(csv) and data separator( , )
    u2022 In proposal tab load example data and verify it.
    u2022 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.
    u2022 Activate data source and read preview data under preview tab.
    u2022 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
    u2022 In left panel select info provider
    u2022 Select created info area and right click to create ODS( Data store object ) or Cube.
    u2022 Specify name fro the ODS or cube and click create
    u2022 From the template window select the required characteristics and key figures and drag and drop it into the DATA FIELD and KEY FIELDS
    u2022 Click Activate.
    u2022 Right click on ODS or Cube and select create transformation.
    u2022 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
    u2022 Activate created transformation
    u2022 Create Data transfer process (DTP) by right clicking the master data attributes
    u2022 In extraction tab specify extraction mode ( full)
    u2022 In update tab specify error handling ( request green)
    u2022 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
    if it is helpful assign points
    cheers
    sivaRaju

  • 'File is not open' error when running DTP for flat file upload in BI

    Dear Sir,
    We are trying to upload master data from flat file for which we have
    created respective DTPs. When we are running the DTPs we are getting an
    error saying 'The file '&&filepath&&' is not open'. We also checked
    that the file is not open, but still we are getting this error. Could
    anyone please suggest what we have to do to solve this problem.
    Many Thanks
    Narendra

    Hi,
    I am currently facing the same error "Error in Source system".  "The file 'path' is not open".
    Could you please let me know how you resolved this issue.
    many thanks.
    Regards,
    Madhusudhan

Maybe you are looking for