1. Get rid of all advertisements and get unlimited access to documents by upgrading to Premium Membership. Upgrade to Premium Now and also get a Premium Badge!

PRC: Transaction Import Errors With INVALID_ETYPE_SYSLINK

Discussion in 'Oracle Projects' started by ajith kumar s, Jun 30, 2014.

  1. ajith kumar s

    ajith kumar s Active Member

    Messages:
    8
    Likes Received:
    0
    Trophy Points:
    75
    Hi,

    While importing transaction trough WEB-ADI 'PRC: Transaction Import' giving error like...

    Rejection Code Meaning
    ------------------------------ ---------------------------------------------------------------------------------------------------
    INVALID_ETYPE_SYSLINK Invalid expenditure type and expenditure type class combination

    INVALID_ETYPE_SYSLINK The expenditure_type/system_linkage for the expenditure item is not a valid/active. Refer
    pa_expend_typ_sys_links table for valid ones

    I have searched in metalink it says "Padded spaces exist in the source file. Remove padded spaces in the source file for the SYSTEM_LINKAGE (expenditure type class) column."


    Can any one help on this how to remove padded spaces.
     
  2. rajenb

    rajenb Forum Expert

    Messages:
    361
    Likes Received:
    114
    Trophy Points:
    655
    Location:
    Mauritius
    Hi Ajith,

    Are you importing through WEB-ADI ?
    As far as I know, the 'PRC: Transaction Import' process is a concurrent request used to import data from external sources into Oracle Projects.

    But, before you submit the process, you must populate the Transaction Interface table (PA_TRANSACTION_ INTERFACE_ALL) with records that you want to import. This is usually achieved by a custom feeder program which can be in C / Pro*C, SQL*Loader or PL/SQL.
    The one most commonly used is SQL*Loader. I don't which one you're using , but you can use the "TRIM" function to remove the spaces.

    Please provide some more information on how you are populating the Interface table.

    Thanks.
     
  3. himanshugosain

    himanshugosain Active Member

    Messages:
    4
    Likes Received:
    0
    Trophy Points:
    150
    Hi Ajith,

    Please find below the root cause and the solution for this issue.

    Regards,
    Himanshu Gosain

    Step 1) Pick up the value of the two fields in the file which has mapped with the fields
    ( EXPENDITURE_TYPE and SYSTEM_LINKAGE) of the interface table PA_TRANSACTION_INTERFACE_ALL.
    Step 2) Verify that an active Expenditure Type Class available/defined.

    select EXPENDITURE_TYPE_ID , EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, START_DATE_ACTIVE, END_DATE_ACTIVE
    from PA_EXPENDITURE_TYPES
    where EXPENDITURE_TYPE = PA_TRANSACTION_INTERFACE_ALL.EXPENDITURE_TYPE

    Step 3) Verify that an active Expenditure Type Class available/defined.
    select EXPENDITURE_CATEGORY, EXPENDITURE_CATEGORY_ID, START_DATE_ACTIVE, END_DATE_ACTIVE
    from PA_EXPENDITURE_CATEGORIES
    where EXPENDITURE_CATEGORY in
    (
    select EXPENDITURE_CATEGORY
    from PA_EXPENDITURE_TYPES
    where EXPENDITURE_TYPE = PA_TRANSACTION_INTERFACE_ALL.EXPENDITURE_TYPE
    )

    Step 4) Verify that an active association available between Expenditure Type and System Linkage.
    select SYSTEM_LINKAGE_FUNCTION, EXPENDITURE_TYPE , START_DATE_ACTIVE, END_DATE_ACTIVE
    from PA_EXPEND_TYP_SYS_LINKS
    where EXPENDITURE_TYPE = Value Picked up from File during Step 1 for the field EXPENDITURE_TYPE
    and SYSTEM_LINKAGE_FUNCTION = Value Picked up from File during Step 1 for the field SYSTEM_LINKAGE

    Solution:
    Either associate the expenditure type class with the expenditure type using the Expenditure Types window
    or
    Either Change the expenditure type or the expenditure type class on the transaction so they form a valid
    combination.
    Step 1) Pick up the value of the two fields in the file which has mapped with the fields
    ( EXPENDITURE_TYPE and SYSTEM_LINKAGE) of the interface table PA_TRANSACTION_INTERFACE_ALL.
    Step 2) Verify that an active Expenditure Type Class available/defined.

    select EXPENDITURE_TYPE_ID , EXPENDITURE_TYPE, EXPENDITURE_CATEGORY, START_DATE_ACTIVE, END_DATE_ACTIVE
    from PA_EXPENDITURE_TYPES
    where EXPENDITURE_TYPE = PA_TRANSACTION_INTERFACE_ALL.EXPENDITURE_TYPE

    Step 3) Verify that an active Expenditure Type Class available/defined.
    select EXPENDITURE_CATEGORY, EXPENDITURE_CATEGORY_ID, START_DATE_ACTIVE, END_DATE_ACTIVE
    from PA_EXPENDITURE_CATEGORIES
    where EXPENDITURE_CATEGORY in
    (
    select EXPENDITURE_CATEGORY
    from PA_EXPENDITURE_TYPES
    where EXPENDITURE_TYPE = PA_TRANSACTION_INTERFACE_ALL.EXPENDITURE_TYPE
    )

    Step 4) Verify that an active association available between Expenditure Type and System Linkage.
    select SYSTEM_LINKAGE_FUNCTION, EXPENDITURE_TYPE , START_DATE_ACTIVE, END_DATE_ACTIVE
    from PA_EXPEND_TYP_SYS_LINKS
    where EXPENDITURE_TYPE = Value Picked up from File during Step 1 for the field EXPENDITURE_TYPE
    and SYSTEM_LINKAGE_FUNCTION = Value Picked up from File during Step 1 for the field SYSTEM_LINKAGE

    Solution:
    Either associate the expenditure type class with the expenditure type using the Expenditure Types window
    or
    Either Change the expenditure type or the expenditure type class on the transaction so they form a valid
    combination.