7 Replies Latest reply: May 22, 2013 12:11 PM by Sandeep Jain RSS

Error during import of tables into DS4.1 from ECC

Arunkumar Jayabalan
Currently Being Moderated

Hi,

 

We use DS 4.1, RFC transport method to extract data from ECC. RFC destination is all setup and is working fine. A user id has been created in ECC and has all authorization assigned to it. Connection is getting established successfully between DS and ECC.

 

When I try to import the table, I get an error message saying...

 

========

 

Error: Cannot import the metadata table <name=table_name>.

 

RFC CallReceive error <Function /BODS/RFC_ABAP_INSTALL_AND_RUN: RFC_ABAP_MESSAGE, Changes to Repository objects are not permitted in this client) - Changes to Repository objects are not permitted in this client[SAP NWRFC 720][SAP Partner 702 ][client#][server_name][user_id][4102]>. (BODI-1112339)

 

========

 

We were able to import the table earlier sometime, but not now. We came to know that the ECC client was locked down.

 

My question is - do we need to have the ECC client open/unlocked when DS is trying to import the table for extraction? And is it advised to have the client unlocked all the time?

 

Or we are missing something?

 

Your input is much appreciated.

 

Thanks, Arun J

  • Re: Error during import of tables into DS4.1 from ECC
    Wiqvist Johan
    Currently Being Moderated

    Hi,

     

    We are facing the exact same problem. Did you find a solution?

     

    For us things are fine in BODS 3.2 and 4.0 but not 4.1. The only way around it seems to be to enable client changes in SAP, which is not something we can allow for any longer period of time.

     

    Thanks

    Johan

  • Re: Error during import of tables into DS4.1 from ECC
    Matteo Stocco
    Currently Being Moderated

    Hello everyone,

    have you solved the problem?

    We have the same issue, but we can't find a solution...

    Thanks

  • Re: Error during import of tables into DS4.1 from ECC
    shiva sahu
    Currently Being Moderated

    Hi Arun,

     

    As per my knowledge ,you should have enabled connection to ECC while extracting the tables.

     

    If you can not have open connection always ,then you may try one alternative that extract all table once and save them in some staging database and then you can use those tables directly and you will not be required to have always opened connection.

     

     

    Regards,

    Shiva

  • Re: Error during import of tables into DS4.1 from ECC
    Yusuf Bepari
    Currently Being Moderated

    Hello Arun,

     

    In the ECC box data is client dependent. If you have created a data store with some xxx client then you will be able to access the data that belongs to same client. So check with your basis team if the user defined for the client number xxx still has the same roles assigned. To test on the ECC system, try running TCODE SE11(Data dictionary) by logging on to the ECC system with the credentials you have  and client number for the host to which you have created a SAP data store. Check if you are able to access the tables which you are trying to import in to the repository. If everything is fine ask basis team or administrator to check the roles assigned or permissions for that particular user are correct.

     

    Thanks,

    Yusuf.

  • Re: Error during import of tables into DS4.1 from ECC
    Sandeep Jain
    Currently Being Moderated

    Hi,

     

    We use DS 4.1, RFC transport method to extract data from ECC. RFC destination is all setup and is working fine. A user id has been created in ECC and has all authorization assigned to it. Connection is getting established successfully between DS and ECC.

     

    Which environment you are referring too?? Dev ?? then this should not happen.

     

    Check the client Status, client may be closed.

     

    As you have mentioned that all authorizations are already assigned to user (client specific) then it should work fine.

     

    if it is not Dev then you do not need to do any import work (means any development in non-dev env).

     

    All the development related work should be in dev and Abap must be transported to other respective env.

     

    But here it is just import, not the execution of ABAP dataflow.

     

    second suggestion,  try import by Name utility in BODS. it also works in restricted env.

     

    Thanks.

     

    Message was edited by: sandeep jain

Actions