COMM_SRTUCTURE is uknown when migrating data flow bw 3.x to 7.4

Question

Dear ALL,
2LIS_13_VDHDR data flow migrating 3.x to 7.x , ABAP syntax error COMM_STRUCTURE is unknown infosoure transformation level, present we are using 7.4 sp5 . after migration ABAP code
TYPES:
      BEGIN OF _ty_s_TG_1_full,
*      InfoObject: 0CHNGID Change Run ID.
        CHNGID           TYPE /BI0/OICHNGID,
*      InfoObject: 0RECORDTP Record type.
        RECORDTP           TYPE /BI0/OIRECORDTP,
*      InfoObject: 0REQUID Request ID.
        REQUID           TYPE /BI0/OIREQUID,
*      InfoObject: 0CALDAY Calendar Day.
        CALDAY           TYPE /BI0/OICALDAY,
*      InfoObject: 0CALMONTH Calendar Year/Month.
        CALMONTH           TYPE /BI0/OICALMONTH,
*      InfoObject: 0CALWEEK Calendar year / week.
        CALWEEK           TYPE /BI0/OICALWEEK,
*      InfoObject: 0FISCPER Fiscal year / period.
        FISCPER           TYPE /BI0/OIFISCPER,
*      InfoObject: 0FISCVARNT Fiscal year variant.
        FISCVARNT           TYPE /BI0/OIFISCVARNT,
*      InfoObject: 0BILLTOPRTY Bill-to party.
        BILLTOPRTY           TYPE /BI0/OIBILLTOPRTY,
*      InfoObject: 0COMP_CODE Company code.
        COMP_CODE           TYPE /BI0/OICOMP_CODE,
*      InfoObject: 0DISTR_CHAN Distribution Channel.
        DISTR_CHAN           TYPE /BI0/OIDISTR_CHAN,
*      InfoObject: 0DOC_CATEG Sales Document Category.
        DOC_CATEG           TYPE /BI0/OIDOC_CATEG,
*      InfoObject: 0PLANT Plant.
        PLANT           TYPE /BI0/OIPLANT,
*      InfoObject: 0SALESORG Sales Organization.
        SALESORG           TYPE /BI0/OISALESORG,
*      InfoObject: 0SALES_GRP Sales group.
        SALES_GRP           TYPE /BI0/OISALES_GRP,
*      InfoObject: 0SALES_OFF Sales Office.
        SALES_OFF           TYPE /BI0/OISALES_OFF,
*      InfoObject: 0SHIP_TO Ship-To Party.
        SHIP_TO           TYPE /BI0/OISHIP_TO,
*      InfoObject: 0SOLD_TO Sold-to party.
        SOLD_TO           TYPE /BI0/OISOLD_TO,
*      InfoObject: 0VERSION Version.
        VERSION           TYPE /BI0/OIVERSION,
*      InfoObject: 0VTYPE Value Type for Reporting.
        VTYPE           TYPE /BI0/OIVTYPE,
*      InfoObject: 0DIVISION Division.
        DIVISION           TYPE /BI0/OIDIVISION,
*      InfoObject: 0MATERIAL Material.
        MATERIAL           TYPE /BI0/OIMATERIAL,
*      InfoObject: 0SHIP_POINT Shipping point.
        SHIP_POINT           TYPE /BI0/OISHIP_POINT,
*      InfoObject: 0PAYER Payer.
        PAYER           TYPE /BI0/OIPAYER,
*      InfoObject: 0DOC_CLASS Document category /Quotation/Order/Deliver
*y/Invoice.
        DOC_CLASS           TYPE /BI0/OIDOC_CLASS,
*      InfoObject: 0DEB_CRED Credit/debit posting (C/D).
        DEB_CRED           TYPE /BI0/OIDEB_CRED,
*      InfoObject: 0SALESEMPLY Sales Representative.
        SALESEMPLY           TYPE /BI0/OISALESEMPLY,
*      InfoObject: 0SUBTOT_1S Subtotal 1 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_1S           TYPE /BI0/OISUBTOT_1S,
*      InfoObject: 0SUBTOT_2S Subtotal 2 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_2S           TYPE /BI0/OISUBTOT_2S,
*      InfoObject: 0SUBTOT_3S Subtotal 3 from pricing proced.for conditi
*on in stat. curr..
        SUBTOT_3S           TYPE /BI0/OISUBTOT_3S,
*      InfoObject: 0SUBTOT_4S Subtotal 4 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_4S           TYPE /BI0/OISUBTOT_4S,
*      InfoObject: 0SUBTOT_5S Subtotal 5 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_5S           TYPE /BI0/OISUBTOT_5S,
*      InfoObject: 0SUBTOT_6S Subtotal 6 from pricing proced. for condit
*ion in stat. curr..
        SUBTOT_6S           TYPE /BI0/OISUBTOT_6S,
*      InfoObject: 0OPORDQTYBM Open orders quantity in base unit of meas
*ure.
        OPORDQTYBM           TYPE /BI0/OIOPORDQTYBM,
*      InfoObject: 0OPORDVALSC Net value of open orders in statistics cu
*rrency.
        OPORDVALSC           TYPE /BI0/OIOPORDVALSC,
*      InfoObject: 0QUANT_B Quantity in base units of measure.
        QUANT_B           TYPE /BI0/OIQUANT_B,
*      InfoObject: 0DOCUMENTS No. of docs.
        DOCUMENTS           TYPE /BI0/OIDOCUMENTS,
*      InfoObject: 0DOC_ITEMS Number of Document Items.
        DOC_ITEMS           TYPE /BI0/OIDOC_ITEMS,
*      InfoObject: 0NET_VAL_S Net value in statistics currency.
        NET_VAL_S           TYPE /BI0/OINET_VAL_S,
*      InfoObject: 0COST_VAL_S Cost in statistics currency.
        COST_VAL_S           TYPE /BI0/OICOST_VAL_S,
*      InfoObject: 0GR_WT_KG Gross weight in kilograms.
        GR_WT_KG           TYPE /BI0/OIGR_WT_KG,
*      InfoObject: 0NT_WT_KG Net weight in kilograms.
        NT_WT_KG           TYPE /BI0/OINT_WT_KG,
*      InfoObject: 0VOLUME_CDM Volume in cubic decimeters.
        VOLUME_CDM           TYPE /BI0/OIVOLUME_CDM,
*      InfoObject: 0HDCNT_LAST Number of Employees.
        HDCNT_LAST           TYPE /BI0/OIHDCNT_LAST,
*      InfoObject: 0CRM_PROD Product.
        CRM_PROD           TYPE /BI0/OICRM_PROD,
*      InfoObject: 0CP_CATEG Category.
        CP_CATEG           TYPE /BI0/OICP_CATEG,
*      InfoObject: 0FISCYEAR Fiscal year.
        FISCYEAR           TYPE /BI0/OIFISCYEAR,
*      InfoObject: 0BP_GRP BP: Business Partner Group (from Hierarchy).
        BP_GRP           TYPE /BI0/OIBP_GRP,
*      InfoObject: 0STAT_CURR Statistics Currency.
        STAT_CURR           TYPE /BI0/OISTAT_CURR,
*      InfoObject: 0BASE_UOM Base Unit of Measure.
        BASE_UOM           TYPE /BI0/OIBASE_UOM,
*      InfoObject: 0PROD_CATEG Product Category.
        PROD_CATEG           TYPE /BI0/OIPROD_CATEG,
*      InfoObject: 0VOLUME Volume.
        VOLUME           TYPE /BI0/OIVOLUME,
*      InfoObject: 0VOLUMEUNIT Volume unit.
        VOLUMEUNIT           TYPE /BI0/OIVOLUMEUNIT,
*      InfoObject: 0FISCPER3 Posting period.
        FISCPER3           TYPE /BI0/OIFISCPER3,
*      InfoObject: 0SALES_DIST Sales District.
        SALES_DIST           TYPE /BI0/OISALES_DIST,
*      InfoObject: 0BILL_TYPE Billing type.
        BILL_TYPE           TYPE /BI0/OIBILL_TYPE,
*      InfoObject: 0MOVE_PLANT Receiving Plant/Issuing Plant.
        MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
*      InfoObject: 0SHIP_COND Shipping conditions.
        SHIP_COND           TYPE /BI0/OISHIP_COND,
*      InfoObject: 0AB_RFBSK Status for Transfer to Accounting.
        AB_RFBSK           TYPE /BI0/OIAB_RFBSK,
*      InfoObject: 0AB_FKSTO Indicator: Document Is Cancelled.
        AB_FKSTO           TYPE /BI0/OIAB_FKSTO,
*      InfoObject: 0CUST_GRP5 Customer Group 5.
        CUST_GRP5           TYPE /BI0/OICUST_GRP5,
*      InfoObject: ZCU_COND1 Constomer Condition Group 1.
        /BIC/ZCU_COND1           TYPE /BIC/OIZCU_COND1,
*      InfoObject: ZCU_COND2 Customer Condition Group 2.
        /BIC/ZCU_COND2           TYPE /BIC/OIZCU_COND2,
*      InfoObject: ZBATCHCD Batch Code.
        /BIC/ZBATCHCD           TYPE /BIC/OIZBATCHCD,
*      InfoObject: 0BATCH Batch number.
        BATCH           TYPE /BI0/OIBATCH,
*      InfoObject: ZBATCH Batch number.
        /BIC/ZBATCH           TYPE /BIC/OIZBATCH,
*      Field: RECORD Data record number.
        RECORD           TYPE RSARECORD,
      END   OF _ty_s_TG_1_full.
* Additional declaration for update rule interface
  DATA:
    MONITOR       type standard table of rsmonitor  WITH HEADER LINE,
    MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
    RECORD_NO     LIKE SY-TABIX,
    RECORD_ALL    LIKE SY-TABIX,
    SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
* global definitions from update rules
* TABLES: ...
DATA: IN    TYPE F,
      OUT   TYPE F,
      DENOM TYPE F,
      NUMER TYPE F.
* Def. of 'credit-documents': following doc.categ. are 'credit docs'
*   reversal invoice (N)
*   credit memo  (O)
*   internal credit memo (6)
* Credit-documents are delivered with negative sign. Sign is switched
* to positive to provide positive key-figures in the cube.
* The combination of characteristics DE_CRED and DOC-CLASS provides
* a comfortable way to distinguisch e.g. positive incoming orders or
* order returns.
* Def. der 'Soll-Dokumente': folgende Belegtypen sind 'Soll-Belege'
*   Storno Rechnung (N)
*   Gutschrift (O)
*   Interne Verrechn. Gutschr. (6)
* Soll-Dokumente werden mit negativem Vorzeichen geliefert. Um die Kenn-
* zahlen positiv in den Cube zu schreiben, wird das Vorzeich. gedreht
* Die Kombination der Merkmale DEB_CRED und DOC-CLASS gibt Ihnen die
* Möglichkeit schnell z.B. zwischen Auftrags-Eingang oder Retouren zu
* unterscheiden.
DATA: DEB_CRED(3) TYPE C VALUE 'NO6'.
FORM routine_0002
  TABLES
   P_MONITOR         structure rsmonitor
  CHANGING
    RESULT         TYPE _ty_s_TG_1_full-DOCUMENTS
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
  RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
* init variables
* fill the internal table "MONITOR", to make monitor entries
CLEAR RESULT.
RESULT = COMM_STRUCTURE-NO_INV.
IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
   RESULT = RESULT * ( -1 ).
ENDIF.
RETURNCODE = 0.
  p_monitor[] = MONITOR[].
  CLEAR:
    MONITOR[].
ENDFORM.                    "routine_0002
FORM routine_0003
  TABLES
   P_MONITOR         structure rsmonitor
  CHANGING
    RESULT         TYPE _ty_s_TG_1_full-DEB_CRED
    RETURNCODE     LIKE sy-subrc
    ABORT          LIKE sy-subrc
  RAISING
    cx_sy_arithmetic_error
    cx_sy_conversion_error.
* init variables
* fill the internal table "MONITOR", to make monitor entries
  IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
    RESULT = 'C'.
  ELSE.
    RESULT = 'D'.
  ENDIF.
  RETURNCODE = 0.
  p_monitor[] = MONITOR[].
  CLEAR:
    MONITOR[].
ENDFORM.   
Error:
E:Field "COMM_STRUCTURE-NO_INV" is unknown. It is neither in one of the
specified tables nor defined by a "DATA" statement. "DATA" statement.
communication structure chaged to sours fields but no uses , please suggest how can i proceed , Thanks in Advance immediate replay
Thanks & Regards
Ramesh G

Answer 1

Hi Gareth,
You have two options:
1. Transport from BW 3.1 to BI 7.0. You'll need to create a transport route between both systems. This may cause you some troubles in the future when you want to modify the objects you transported.
2. As there are few objects, you can use XML export utility from Transport connection. There, you make an XML file with the objects you need to transport. One thing that you may take care of, in this option, is that the business content objects you are exporting need to be activated in the destination system. Another problem is that querys are not exported.
Since it's only a cube, maybe you can create the objects manually. Look that in BI 7.0 there are several new functionalities, i don't know how transport or xml export would work.
Hope this helps.
Regards,
Diego