Last update: 30/11/2006 Here is a collection of the most frequently asked questions and troubles that a developer has during the uploading of flat file in BW: Common mistake on upload file • Delimeter not given in upload csv or given in wrong way. How to resolve: You must be sure that it will be set as “;” 
Pay attention in some regions and depending of the contents of the file the delimeter of csv is "," (Thanks Vitaliy)!! A good doc on .csv is http://www.ietf.org/rfc/rfc4180.txt • The system can't open the file. Possible Reason: - When the file is on application server can't be it is not accessible from BW because of authorization given on BW user (normally BWADMIN) doesn’t match with the permission on the file. - The file in client workstation is still open from another user. (thanks Vitaliy :)) • When you make at your own the .csv file from an excel file, in the source file you have the last (one or more) line blank. How to resolve: Delete all records “empty” in excel before convert in .csv • Saving a .csv file from .xls --> loose some info or change some data. How to resolve: define the format of all the excel cells as "text". Select all cells and 
Note that if you open a .csv file directly with excel you’ll may lose every formatting option. If you need to re-open the file to add or adjust some data it’s better to open the previous file .xls and not the .csv. • The file contains un-necessary formatting not visible in "NOTEPAD". (Hidden characters) How to resolve: manage the file with another editor. Common mistake on definition and conversion in BW after upload data: • You catch an error on Alpha conversion (or another type of field conversion like PERI7…) You need to take confident with this concept. Documents are in http://help.sap.com/search/highlightContent.jsp or in discussion in forum alpha conversion Take in mind the option in transfer rule to convert the data from external format into internal. 
The type ALPHA, NUMCV and GJAHR are supported by standard. Note, check also the datasource definition 
• Data in the file is in lowercase but the definition of InfoObject in the general tabpage is #147;no lowercase” You have two options. 1 - Change the definition of Infoobject to lowercase, but make it only if is really necessary to distinguish between the values like “MATERIAL”, “Material” or “MaTerial”. Don’t make it if the values means the same like “MATERIAL” 2 - Convert to uppercase the data using the TOUPPER() formula in the transfer rules. • Calendar day should be of the format yyyymmdd (SAP requires this format). • After the upload of data for some currency you have the amount * 100. That could happen for the currency key defined without decimals (see TCURX table). How to resolve: Set the option “Currency conversion for external Syst.” in the Tab External data of Infopackage. • You set the option “Currency conversion for external Syst.” but the problem on currency persists! Hot to resolve: in the Datasource definition every amount must refer to a currency unit. Note that during the definition of the Datasource structure, when you insert the InfoObject of reference, the system ask if you want to overwrite the definition. 
If you say not, the definition (length and type of data) remain what you have defined. 
But also the unit of reference for the structure. To change this reference it’s necessary to say “overwrite”. Only in this way the option “Currency conversion for external Syst.” could be used. 
The Infoobject related to the field of amount must have the Infoobject unit defined also in the datasource structure. When you say "overwrite" the definiton data of IO substitutes the data (length, type, and others) but also the currency of reference. • Special character not admitted during the execution of the update rules. How to resolve: Make it admitted on transaction RSKC. But have a look on the blog linked below to go deeper on the argument. Invalid characters in SAP BW 3.x: Myths and Reality. Part 2. Some Hints: **** EXTERNAL DATA Make always the preview option of file to understand: - if the path specified is correct (if not you receive an error) - if the parameters in tab external data are correct (you'll see a very strange content) - if the content of fields corresponds to the definition made in the infosource (some content are not correct under the right column or a part of the information is splitted into two column). Note that you can see more than the 5 records proposed by default (check almost the first 100-500 records please). I strongly recommend to use the simulation of update during the preview of file. 
****** TAB SELECTION Is open to insert one value, an interval or more value and interval together (in OR). But there aren't selection criteria more fine like exclude or include only initial value. In this case is necessary to insert a little ABAP routine 
Note that the only combinations admitted in the range like variable are: SIGN - OPTION I - BT I - EQ I - CP No Others (ex, E EQ to exclude a value) are available for file source. You can make more options only for infopackage based on generated infosource like ODS. Reference in SDN world At the end I would like to resume some blogs and docs about this specific argument. Blogs - Here the complete list. Binary File in BW: what I can do with control file Invalid characters in SAP BW 3.x: Myths and Reality. Part 2. Debugging data upload in BW (but only with PSA and after upload file) Hierarchy Upload from Flat files Loading Text Files(.TXT) into BW with HEX option How to create ASCII text file for upload to SAP BW (in case of hard problem of performance) Help pages is every time the main reference: NW2004 NW2004s
Pay attention in some regions and depending of the contents of the file the delimeter of csv is "," (Thanks Vitaliy)!! A good doc on .csv is http://www.ietf.org/rfc/rfc4180.txt • The system can't open the file. Possible Reason: - When the file is on application server can't be it is not accessible from BW because of authorization given on BW user (normally BWADMIN) doesn’t match with the permission on the file. - The file in client workstation is still open from another user. (thanks Vitaliy :)) • When you make at your own the .csv file from an excel file, in the source file you have the last (one or more) line blank. How to resolve: Delete all records “empty” in excel before convert in .csv • Saving a .csv file from .xls --> loose some info or change some data. How to resolve: define the format of all the excel cells as "text". Select all cells and Note that if you open a .csv file directly with excel you’ll may lose every formatting option. If you need to re-open the file to add or adjust some data it’s better to open the previous file .xls and not the .csv. • The file contains un-necessary formatting not visible in "NOTEPAD". (Hidden characters) How to resolve: manage the file with another editor. Common mistake on definition and conversion in BW after upload data: • You catch an error on Alpha conversion (or another type of field conversion like PERI7…) You need to take confident with this concept. Documents are in http://help.sap.com/search/highlightContent.jsp or in discussion in forum alpha conversion Take in mind the option in transfer rule to convert the data from external format into internal. The type ALPHA, NUMCV and GJAHR are supported by standard. Note, check also the datasource definition • Data in the file is in lowercase but the definition of InfoObject in the general tabpage is #147;no lowercase” You have two options. 1 - Change the definition of Infoobject to lowercase, but make it only if is really necessary to distinguish between the values like “MATERIAL”, “Material” or “MaTerial”. Don’t make it if the values means the same like “MATERIAL” 2 - Convert to uppercase the data using the TOUPPER() formula in the transfer rules. • Calendar day should be of the format yyyymmdd (SAP requires this format). • After the upload of data for some currency you have the amount * 100. That could happen for the currency key defined without decimals (see TCURX table). How to resolve: Set the option “Currency conversion for external Syst.” in the Tab External data of Infopackage. • You set the option “Currency conversion for external Syst.” but the problem on currency persists! Hot to resolve: in the Datasource definition every amount must refer to a currency unit. Note that during the definition of the Datasource structure, when you insert the InfoObject of reference, the system ask if you want to overwrite the definition. If you say not, the definition (length and type of data) remain what you have defined. But also the unit of reference for the structure. To change this reference it’s necessary to say “overwrite”. Only in this way the option “Currency conversion for external Syst.” could be used. The Infoobject related to the field of amount must have the Infoobject unit defined also in the datasource structure. When you say "overwrite" the definiton data of IO substitutes the data (length, type, and others) but also the currency of reference. • Special character not admitted during the execution of the update rules. How to resolve: Make it admitted on transaction RSKC. But have a look on the blog linked below to go deeper on the argument. Invalid characters in SAP BW 3.x: Myths and Reality. Part 2. Some Hints: **** EXTERNAL DATA Make always the preview option of file to understand: - if the path specified is correct (if not you receive an error) - if the parameters in tab external data are correct (you'll see a very strange content) - if the content of fields corresponds to the definition made in the infosource (some content are not correct under the right column or a part of the information is splitted into two column). Note that you can see more than the 5 records proposed by default (check almost the first 100-500 records please). I strongly recommend to use the simulation of update during the preview of file. ****** TAB SELECTION Is open to insert one value, an interval or more value and interval together (in OR). But there aren't selection criteria more fine like exclude or include only initial value. In this case is necessary to insert a little ABAP routine Note that the only combinations admitted in the range like variable are: SIGN - OPTION I - BT I - EQ I - CP No Others (ex, E EQ to exclude a value) are available for file source. You can make more options only for infopackage based on generated infosource like ODS. Reference in SDN world At the end I would like to resume some blogs and docs about this specific argument. Blogs - Here the complete list. Binary File in BW: what I can do with control file Invalid characters in SAP BW 3.x: Myths and Reality. Part 2. Debugging data upload in BW (but only with PSA and after upload file) Hierarchy Upload from Flat files Loading Text Files(.TXT) into BW with HEX option How to create ASCII text file for upload to SAP BW (in case of hard problem of performance) Help pages is every time the main reference: NW2004 NW2004s
4 Comments
| User | Count |
|---|---|
| 525 | |
| 263 | |
| 238 | |
| 234 | |
| 167 | |
| 157 | |
| 152 |
