SAPINST Import SAPVIEW.STR Error

[Private_Member_80553]

Hello,

Currently I am doing a sapinst import and facing a following error and don't have a idea how to fix it. Export finnished without any error. Can someone give me a advise please.

(RDI) ERROR: keyword "fld" or "qry" expected at line 4 of DB independent control file "/sapexport/SID/export/ABAP/DATA/SAPVIEW.STR

SAPVIEW.STR:

1 # Versions: 1 - initial format,  2 - row store flags,  3 - CDS views

    2

    3 vie: /1CN/A3DSAP00002

   4 ref: /1CN/C3DSAP00002

    5 fld: CLIENT

    6 fld: BEF_APPL

    7 fld: OBJTYPE

    8 fld: SRC_PROCESS_TYPE

    9 fld: SRC_ITEM_TYPE

   10 fld: KSCHL

   11 fld: OBJECT_ID

   12 fld: TIMESTAMP_TO

   13 fld: RELEASE_STATUS

   14 fld: KOPOS

   15 fld: CREATED_ON

   16 fld: VARNUMH

   17 fld: TIMESTAMP_FROM

   18 fld: KSCHL_SUPP

   19 fld: COND_GROUP_ID

   20 fld: MAINT_STATUS

   21 fld: CREATED_BY

   22 fld: SUPP_EXIST

   23 fld: SCALE_DIM

   24 fld: ITEM_CATEGORY

   25 qry: SELECT T0001."CLIENT", T0001."BEF_APPL", T0001."OBJTYPE", T0001."SRC_PROCESS_TYPE", T0001."SRC_ITEM_TYPE",

   26             T0001."KSCHL", T0001."OBJECT_ID", T0001."TIMESTAMP_TO", T0001."RELEASE_STATUS", T0001."KOPOS",

   27             T0001."CREATED_ON", T0001."VARNUMH", T0001."TIMESTAMP_FROM", T0001."KSCHL_SUPP", T0001."COND_GROUP_ID",

   28             T0001."MAINT_STATUS", T0001."CREATED_BY", T0001."SUPP_EXIST", T0001."SCALE_DIM", T0001."ITEM_CATEGORY"

   29      FROM "/1CN/C3DSAP00002" T0001

   30

   .

   .

   .

Thank you in advance

Matus

[divyanshu_srivastava3 · Accepted solution]

Are you using same level/patch of r3trans for import that you used while taking export?

[divyanshu_srivastava3 · Accepted solution]

At the time of taking export, while splitting tables,  did you have any issue.

Also, can you check controlling file and file system mounted have same contents as should be ?

[Reagan · Accepted solution]

Divyanshu Srivastava wrote:

Are you using same level/patch of r3trans for import that you used while taking export?

R3trans ???

In fact it should R3load.

[divyanshu_srivastava3 · Accepted solution]

I mean the same , R3* should have same versions.

[Private_Member_80553 · Accepted solution]

Hi Divaynshu

of course it was R3load, but in my case I have synchronized all R3* files,

Thx for help

[former_member1015]

We are getting the same error. But we are doing a Unicode conversion and we get this error during import of data in to the unicode system. So our sources system R3* files are non-unicode and target system is unicode. Is there a way I can ignore the error and proceed??