Error in flat file loading : Important

Hi !
I am using BW 3.5 . I am loading data from flat file which has a KF VOLUME and UOM as USG but it is giving error as Conversion exit error.(CONVERSION_EXIT_CUNIT_INPUT).
Please tell me what should i do ?

Dear Rajib Goon
Its won't be a much problem.
Open your info source, in the Key Figures Transfer View, you can see a one column name called "Fixed Unit Of Measurement". Here enter "USG" for the Keyfigure VOLUME & Reschedule your info package.
Hope this will help you lot.
Regards
Saravanan.ar

Similar Messages

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

Error in Flat file loading with different units

Hi Gurus,
I have Quantity and its unit (say CS, DZ and KG etc...) fields in source system. when i transfered into psa using infopackage the error was shown as The error in unit CS is not mentioned in English.
Could you please tell me what have to do for solving the problem.
Thanks
Shrinu

Hi,
Sorry, I couldn't understand your answer. I have problem with transaction data not the masterdata. could you please expand your answer as iam bit new to these problems.
Points will be awarded for your reply.
Thanks
Shrinu

What are the settings for datasource and infopackage for flat file loading

hI
Im trying to load the data from flat file to DSO . can anyone tel me what are the settings for datasource and infopackage for flat file loading .
pls let me know
regards
kumar

Loading of transaction data in BI 7.0:step by step guide on how to load data from a flatfile into the BI 7 system
Uploading of Transaction 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 ( 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 )
3. 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.
4. 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.
Loading of master data in BI 7.0:
For Uploading of master data in BI 7.0
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.

Best practise around handling time dependency for flat file loads

Hi folks,
This is a fairly common situation - handling time dependency for flat file loads. Please can anyone share their experience around handling this. One common approach is to handle the time validity changes within the flat file where it is easily changeable by the user but then again is prone to input errors by the user. Another would be to handle this via a DSO. Possibly, also have this data entered directly in BI using IP planning layouts. There is a IP planning function that allows for loading flat file data but then again, it only works without the time dependency factor.
It would be great to hear thoughts or if anyone can point to a best practise document for such a scenario.
Thanks.

Bump!

Unit Code, Commercial Code - Flat File loading vs BPS Loading

Hi SDN Community,
Recently, we have moved our flat file loading to be performed by BPS interfaces.
During flat file loads, the Commercial code of all units of measures, are verified.
eg.DAY
But when loaded by BPS, the UNIT code is verified.
eg. TAG.
In the display of the BPS upload, it displays DAY which is the commercial code.
The only thing, is the customer is forced to use TAG in the BPS upload files.
They wish to create another record in the transaction
CUNI to be
Unit code = DAY
Commercial code = DAY.
However, i have found that we cannot allocate the same commercial code to another unit code.
Is this a design constraint, or a process error that i am doing.
Thank you.
Simon

04.01.2010 - 02:22:53 CET - Reply by SAP
Dear customer,
As i do not fully understand how this works, but the base table T006A
has 2 entries, 1 for english, 1 for German, should it not be that the
English EN entry field be working rather that the German DE, hence DAY
should be used? Can you please confirm my understanding on this?
>>> If you check my attachment "SE16.xls", you can see that it's for
language >>English<<, and the internal format is TAG while the external
format is DAY.
- Are there any plans to modify the BPS functionality in newer SAP BW
versions to allow the customer to indicate the same UOM as per flat
file laods? Or is an upgraded Support Pack that allows this?
- If not, would it be possible to make any customer enhancements to
allow this to take place depending on customer requirements.
>>> There is no plan at this moment to change this BPS functionality
in newer SAP BW versions or support packages.
We really recommend you to use internal format TAG in the upload file
in BPS which I think should be acceptable and feasible to you. All
other ways trying to use external format is risky and we cannot assure
you that it will work well as it's not SAP standard function. (I think
it's not worth the risk as the standard function which requires
internal format should not be too unacceptable)
Thanks for your understanding.
I also don't think my BC-SRV-ASF-UOM colleague would be able to help
you a lot regarding this.
Best Regards,
Patricia Yang
Support Consultant - Netweaver BW
Global Support Center China
SAP Active Global Support

Flat File loading Initialize with out Data transfer is disabled in BI 7.0

Hi experts,
When loading through flat file in BI 7.0 for Info Package Level Initialization Delta Process with data Transfer is coming by default,but when i want to select Initialization Delta Process without Data transfer is disabled. (in the creation of Data Source (flat file) in the Extraction Tab Delta Process is changed to FIL1 Delta Data (Delta Images).
please provide me Solution.
regards
Subba reddy.

Hi Shubha,
For flat file load please go throught he following link:
http://help.sap.com/saphelp_nw70/helpdata/EN/43/03450525ee517be10000000a1553f6/frameset.htm
This will help.
Regards,
Mahesh

Flat-File Loading problem

Hi Friends,
I am struggling with flat-file loading problem. I am trying to load a .csv file into data target. I took all pre-cautions while loading data. I look into preview and simulate the data. Everything is ok, but when i schedule the data, i found 0 records in the monitor. The following is the STATUS message of the above problem:
   No data available
Diagnosis
The data request was a full update.
In this case, the corresponding table in the source system does not
contain any data.
System response
Info IDoc received with status 8.
Procedure
Check the data basis in the source system.
         Can anybody help me what is the problem and procdure to resolve it?
Regards,
Mahesh

Hi Eugene,
Thanks for the quick reply. The following screen-shot tells you the messages of detail tab;
OVER ALL STATUS MISSING WITH MESSAGES OR WARNINGS
REQUEST: MISSING MESSAGES
EXTRACTION
EVERYTHING IS OK
DATA REQUEST RECEIVED
NO DATA AVAILABLE DATA ELECTION ENDED.
PROCESSING
NO DATA
           The above message was shown in details tab. Pls guide me to locate the problem.
Regards,
Mahesh

Transformation not generating-Flat file loading

Hello guys, I hope you can help me with this little confusion I have on BI7 Flat file loading.
I got a File (CSV) on my workstation. I am trying to load Master Data. Here is the example of my file and issues:
Lets say, I have CSV file named "CarModel.CSV" on my PC.
This excel file has 10 Records and No atributes for this Field.
So the records should show like this and it is showing correctly in PSA level, DS level.
A
B
C
D
E
F
My goal is to load Flat file data to InfoObject (inserted in Infoprovider)
I created Source system, DS, all thats stuffs.
I am now on Display DS screen under Proposal Tab. I am putting 10 Records to show and hitting Load example data....it works fine by showing all 10 records. However in the bottom part of this screen, what should show as a Field ?In my case , First it was showing the First Record ("A")...i didnt think it was correct but i prceeded anyways. Transformation could not be generated.
I tried by deleting "1" from the field "No. of header rows to be ignored" and its the same result ..No transformations.. I mean i know its very simple to load this data but i am not sure what i am doing wrong..My question is:
1) What should show under Field/propasal tab in my case?am i supposed to create this Field?
2) Should the system to propse the field which is from my flat file header ?in my case i dont have any header..should i have include header in my csv file like "car model"? i am confused please give me some info thanks
dk

Hi,
In filed tab, u have to enter ur infoobject names in an order...and press enter it'll automatically give the description and its other factors...
i guess u shuld have some header in the sense eg: customer,cust ID like this..this only u have to enter as fields...in proposal tab...try that
rgds,

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 load error

Hi.
I am getting the following error when loading .csv file from "Client Workstation" but the same file is loading fine from "Application server".
Value '10/1/206 ' of characteristic 0DATE is not a number with 000008 spaces
I look for your suggestions to solve and understand this.
Thanks
Kumar

Hi Dinesh,
I solved the problem by using SDATE in transfer rules as per the SAP note 161506. I am giving the note below for others who might land with similar problem.
Thanks
Kumar
SAP Note Number: 161506
Summary
Symptom
You want to transfer data from a source system into BW from a file (flat file) that also includes date entries (for example, for the 0CALDAY InfoObject). However, when you load the data, the data disappears.
Other terms
Time characteristic, transfer structure, transfer rules, InfoPackage Scheduler, InfoSource
Reason and Prerequisites
In the flatfile of the source system, a date exists which is not stored in the internal format YYYYMMDD but in the external (user-specific) format. In the transfer structure maintenance, no routine is specified for the conversion exit for the corresponding date field. An incorrect data type and an incorrect length can be assigned additionally. The missing conversion exit causes an incorrect processing of the date during the conversion to the internal format of the type DATS and length 8.
Solution
In the maintenance of the transfer structure, standard values that expect the date while the data is being stored in the internal format of the YYYYMMDD system are entered for the 0CALDAY InfoObject (calendar day):
InfoObject Field name Type Length Conversion exit   0CALDAY       CALDAY      CHAR      8
The problem described above is corrected with the conversion of the date fields into the internal format in the flatfile.
If you want to maintain the external format of the date in the source file, implement the following changes in the transfer structure maintenance for the 0CALDAY field:
InfoObject Field name Type Length Conversion exit   0CALDAY       CALDAY      CHAR    10   SDATE
Note that the type must always be CHAR (not DATS). The predefined field length is changed from 8 to 10, and additionally the conversion routine SDATE is entered.
IMPORTANT: The external format for the date in the flat file must match the standard settings of the user in the system (System -> User profiles -> Own data -> Fixed values) such as DD.MM.YYYY MM/DD/YYYY and so on.
Each time you make a change in the maintenance of the transfer structure, you must
a) save the new entries,
b) activate the transfer rules again (InfoSource -> maintain transfer rules),
c) exit and access the Administrator Workbench again (see related notes below) before the next set of data is loaded.
Header Data
Release Status:     Released for Customer
Released on:     03.09.2004 08:27:34
Priority:     Recommendations/additional info
Category:     Consulting
Primary Component:     BW-WHM-DST Data Staging
Releases
Release Independant
Related Notes
157643 - Format 0CALMONTH, 0CALWEEK and 0FISCPER incorrect
155706 - Changes to transfer rules are ignored

Error while creating process chain for flat file loading

Hi All,
I had Created a process Chain to load Transactiion data(Full load) form flat file which is in my computer.
start>Load>DTP>DeleteIndex>DTP loading CUBE--> Create Index
but the system is throwing an error as "An upload from the client workstation in the background is not possible."
I dont know why this error is coming?
Can some one help me
Regards
Mamta

Hi Mamta,
Basically if you want to load the DS through FF using process chain, the FF has to be placed in Application server. We cant load the FF when it is located in the client local workstation(FF On your PC).
So better you remove the Infopackage step from the PC. Load the IP manually. Once it is completed you can start the process chain with the following steps:
start>DTP>DeleteIndex>DTP loading CUBE> Create Index
Hope it is clear & helpful!
Regards,
Pavan

Error in flat file data loading

Hi All,
I have a flat file which has 20000 records, when I tried to do Read Preivew data in Data source creation Iam getting the following error.
I have the field name GROSSMARGIN in flat file I have given the properties of Grossmargin as a keyfigure and
Data Type :FLTP-Floating point number,
Unit/Currency: 0CURRENCY.
I am not getting any error while loading the value like '22134'.But when ever the records which are having the value of 5 digits, and starts with 3 like above one.After words I have replaces the value with some 5 digit number like(24432),It has worked fine.I do not understand the error cause.
Please help me.
Regards,
G S Ramanjaneyulu.

Hi Raman,
You are using data type INT2 for this and there is a restriction for this data type.
INT2: 2-byte integer between -32767 and 32767. Fields of this type should only be used for length fields. These long fields are positioned immediately in front of a long field (type LCHR, LRAW). With INSERT or UPDATE on the long field, the database interface enters the length which was actually used in the length field. The length is set to 5 places for this data type.
So this accepts the max no. till 32767 and if you put any no. more than that it will give you error of Overflow.
Please let me know if there are any questions.
Thanks
Amit

Hierarchy from flat file loading with errors - duplicate node names

Hello experts,
I am loading a product hierarchy from a flat file into a custom hierarchy
object. The issue is that it errors out saying I am loading
duplicates within nodes, however all node IDs within a level are unique.
It seems to be looking at the node name to determine uniqueness and I know
we have some duplication within the text there especially when you factor
in the 32 character limitation for the node name. Does anyone have an idea
as to whether it is possible to have it only consider the node ID instead
of the node name to determine uniqueness?
A colleague suggested using the link ID to fix this problem but I don't know how that field works or how to populate it.
I'm working in a BI 7.0 environment (I don't know if that makes a difference since you still have to use the 3.x objects to extract the hierarchy).
Any help would be appreciated.
Nancy

Hi Nancy,
You may wish to check this OSS Note 1026749 - Hierarchies: Consistency check for duplicate nodes and 912115 (old one)
Symptom -
When you load or activate a hierarchy it terminates with error message RH 109 or RH 211. The hierarchy contains duplicate nodes and this is not allowed. The long texts of messages RH 109 or RH 211 do not describe the reason for the problem sufficiently or they are partially incorrect.
There is uncertainty about in which cases duplicate nodes exist in a hierarchy and in which cases duplicate nodes are allowed.
Hope this helps,
Bye...
Naga Timmaraju

Error in flat file loading : Important

Similar Messages

Maybe you are looking for