Question:
Hi,
I have an Oracle table in an external database. I created a DataSource
and and InfoSource for it.
To create the InfoSource, I have defined InfoObject with the same
type and length as database table fields.
When I load data, InfoPackage ends with error mentioned in title.
In PSA, I can see:
Diagnosis
The system checked whether the loaded InfoObject value conforms to the
conversion exit.The check failed.
For example:
The value '1' was loaded into an InfoObject with alpha exit, even thoug
the value '0000000001' was expected.
System response
The load process has failed or the erroneous records are displayed in
the monitor. This does not depend on how error handling is set up.
Procedure
Find out why the data does not conform to the conversion exit, and, if
possible, correct the cause. Possible causes are errors in Business
Content or an error in a customer exit in the source system.
If you cannot correct the problem, you have the option of removing the
conversion exit on the InfoObject. However, since the system has already
been converted, duplicates appear in the system again.
************!!!!!!!!
None of the InfoObjects has conversion routine assigned (I have tried
to put conversion routine and the error is the same, so, now I have
deleted conversion routine ALPHA for all InfoObjects).
As an example, in database, I have field EMPLOYEE NUMBER, type
VARCHAR2 and length 10.
In BW, I have created InfoObject ORA_EMPL, type CHAR, length 10 without
conversion exit.
I have assigned them in transfer rules.
In database, a value stored for this field is '100'. I don't know if
system waits for '00000000100' still I have deleted conversion exit.
Thanks.
Answer:
you can always fill the leading zero's in a transfer rule
Answer:
No, that's not possible. The error arised again, but listen what was the problem, I have already solved.
Hi have several InfoObjects in Communication Structure, that was in the following way:
0CALDAY
EMPL_NBR
PROJ_NBR
...
The database table has fields:
ENTRY_DATE, varchar2(, format YYYYMMDD (as in SAP BW)
EMPLO_NBR, varchar2(10)
PROJE_NBR, varchar2(10).
I mapped them in transfer rules. Well, the problem was in 0CALDAY!!! (still system informs about the error in the InfoObject EMPL_NBR.
And what was the problem???
If I map the InfoObject 0CALDAY directly to the source field ENTRY_DATE, the error arises, but if I create a transfer routine for InfoObject 0CALDAY, with source code:
result = tran_structure-entry_date
It works OK!!!
As you can see, the transfer routine does not perform any action, it makes a direct mapping, but it solves the problem.
I hope this solution can help other people with the same problem.
Regards.
Answer:
This problem can be solved, by using the Conversion Check Box in the Transfer Rules.
This check box is ready for Input for Info objects having 'Conversio Routines'. For example 0CALDAY has conversion routine other than 'Alpha'.
By checking the check box in the Transfer rules, the system performs the Conversion. This problem doesn't appear in 2.OB but appears after performing Alpha conversion, which is necessary before the upgrade to 3.0B.
Hope this helps
KBK