Error in rules while updating from PSA to ODS

Question

Hi Experts,
I am trying to load data from PSA to ODS using DTP. For about 101 records I get the following error:
"Runtime error while executing rule -> see long text     RSTRAN     301"
On further looking at the long text:
Diagnosis
    An error occurred while executing a transformation rule:
    The exact error message is:
    Overflow converting from ''
    The error was triggered at the following point in the program:
    GP4808B5A4QZRB6KTPVU57SZ98Z 3542
System Response
    Processing the data record has been terminated.
Procedure
      The following additional information is included in the higher-level
     node of the monitor:
     o   Transformation ID
     o   Data record number of the source record
     o   Number and name of the rule which produced the error
Procedure for System Administration
When looking at the detail:
Error Location: Object Type    TRFN
Error Location: Object Name    06BOK6W69BGQJR41BXXPE8EMPP00G6HF
Error Location: Operation Type DIRECT
Error Location: Operation Name
Error Location: Operation ID   00177 0000
Error Severity                 100
Original Record: Segment       0001
Original Record: Number        2
Pls can anyone help in deducing and pointing this error to the exact spot in the transformation rule
Thanks & Regards,
Raj

Answer 1

Hi Kazmi:
Runtime Errors         CONNE_IMPORT_WRONG_COMP_TYPE
Exception              CX_SY_IMPORT_MISMATCH_ERROR
Short text
    Error when attempting to IMPORT object "HIST2".
What happened?
    Error in the ABAP Application Program
    The current ABAP program "RSORAT4M" had to be terminated because it has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_IMPORT_MISMATCH_ERROR', was
     not caught in
    procedure "AKT_DAY_HIST2" "(FORM)", nor was it propagated by a RAISING clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    When importing the object "HIST2", the component no. 8 in the
    dataset has a different type from the corresponding component
    of the target object in the program "RSORAT4M".
    The data type is "I" in the dataset, but "P" in the program.
How to correct the error
    Try to find out why the type of the object should be different.
    There are various possible options:
    1. The type of the imported field has changed in the Data Dictionary.
       Make sure that the type of the imported field matches the type
       of the field in the Data Dictionary.
       If the data cannot be restored from another source, the data must be
       read by the 'old' structure, converted und again eported with the new
       structure, so that future IMPORTs will always function with the new
       structure.
    2. A new program version is active, which no longer fits the dataset.
       Try to solve the error generating the program "RSORAT4M" again. This
       works as follows: Select transaction SE38 in the SAP system. Enter
       the program name "RSORAT4M". Then activate the function 'Generate'.
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"CONNE_IMPORT_WRONG_COMP_TYPE" "CX_SY_IMPORT_MISMATCH_ERROR"
"RSORAT4M" or "RSORAT4M"
"AKT_DAY_HIST2"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
    To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
    Display the system log by calling transaction SM21.
    Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
    In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught wit
"AKT_DAY_HIST2" "(FORM)", or its possible occurren
RAISING clause of the procedure.
Hope this helps.
Thanks to you and all
Raj