C programming used in defining Basic type of IDOCS

Wow , when I go in WE60 and see the basic sturcture for IDOC for ex: MATMAS05, I find its using C programming language ?
Example:
#define E2CUCO
typedef struct{

SAP just provides multiple ways to view the definition of the IDoc.  These are used to assist external applications to import IDoc structures.  The IDoc itself actually exists as numerous table entries within SAP.

Similar Messages

  • On an pci_mio 16e4 programming using nidaq & visual basic, after using AI_Setup analog sequential data accusition stops.To restart I use Init_DA_Brds This takes a long time, What must I reset to restore the analog sequential function?

    on an pci_mio 16e4 programming using nidaq & visual basic, after using AI_Setup analog sequential data accusition stops.To restart I use Init_DA_Brds This takes a long time, What must I reset to restore the analog sequential function?
    I belive that the trigger is being changed on the io board, but cannot manage to reset it.
    The reset process takes in the order of 0.1 sec, and since this is a time critical application, i want to get the scanning function working again faster

    Dear Ian. Thank you for your reply. The problem appears to be that the scan trigger(s) are stopped, or something, by the use of the AI_setup instruction. The sytstem works perfectly until this instruction is used. My problem is in understanding what has happened since the help seems to give no detail on any interconnection between the scan system and the external analog trigger system. I have tried to reconnect the triggers, but so far unsucessfuly

  • What is Basic type in IDoc?

    Hi all,
    What is Basic type in IDoc? Please explain me in layman terms. How to see the details of basic type ALEREQ01? Please point me to related files or threads.
    Thanks,
    Charles.

    Hi,
    <b>IDOC Basic type means, IDOC type delivered by SAP</b>. When you want to modify the IDOC provided by SAP, you create an Extension IDOC of Basic type.
    <b>This is what SAP says about "Basic Type".</b>
    IDoc type supplied by SAP (standard format for data communication). Basic types can be modified by customers to create a new, upward-compatible IDoc type. Basic types can also be defined by customers and modified at a later date. Basic types and subsequent modifications created by customers are not necessarily upward-compatible.
    <b>To check detail of any IDOC, user transaction <u>WE60</u>.</b>
    Check area Menu <b>WEDI</b>. Its a Area menu for all IDOC related transaction. Enter command WEDI ( where you enter transaction code - Top left of screen ). Also, this command only works from very first screen of SAP. This is SAP eacy access screen you see when you logon into SAP. Since WEDI is area menu, you can only execute from very first screen.
    Here is the list of other area menu.
    WEDI - IDOC and EDI Basis
    BALE - ALE Administration
    Let me know if you need any other information.
    Regards,
    RS

  • Functiopn module associated with basic type of idoc without process code

    can i know the function module assciated with basic type of idoc if i do not know the process code for the same

    hi saurabh,
    download.oracle.com/docs/cd/B10464_05/integrate.904/b10299/intro.htm
        CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
          EXPORTING
            master_idoc_control                  = wa_edidc
          TABLES
            communication_idoc_control           = it_edidc
            master_idoc_data                     = it_edidd
      EXCEPTIONS
        ERROR_IN_IDOC_CONTROL                = 1
        ERROR_WRITING_IDOC_STATUS            = 2
        ERROR_IN_IDOC_DATA                   = 3
        SENDING_LOGICAL_SYSTEM_UNKNOWN       = 4
        OTHERS                               = 5
        IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
        ENDIF.
      ENDIF.
    ENDIF.
    ENDMETHOD.
    i think this will help u
    regards,
    sindhu.

  • Two print programs using the same output type in t-code v/40

    Hi,
    I am trying to use the same Output type RD00 to print diferent forms.
    In t-code v/40 we can fill a second Processing but how this work?
    Can someone tell me more about this?
    The final goal is to print diferent forms according to different companies.
               Thank you and best regards
                         João Fernandes

    Hi,
    It is not possible to have 2 different routines to be assigned to one output type in the procedure. I think when you say 2 routines, you are saying 2 logics or you are saying the subroutines KOBED and KOBEV of the routine.
    In all reqmt routines, which is in discussion now, only one of the subroutines will be always called, though I dont know unfortunately which one is this. As you said, that only one of your processing logic works, that is the right subroutine area where the second logic should also be coded. So please move your code from the inactive subroutine area to the active subroutine area. Now you should be able to see both the validations being active.
    Hope this helps. If the case is different, please let us know.

  • Enter a valid basic type - BW IDoc type RSSEND is not same as the SS IDOC

    Hi,
    I am connecting the ERP system to BW system, and am getting error:
    CHECK(context menu source system):
    @5C@     BW unknown in source system     RSAR     8     
    @5C@     The BW IDoc type RSSEND is not the same as the source system IDoc type     RSAR     371     
    RESTORE(context menu source system):
    Information: Enter a valid basic type
    Information help:
    Enter a valid basic type
        Message no. E0434
    Diagnosis
        An entry with the key /BD2CLNT100/LS//RSSEND//// is to be inserted in
        table
        EDP13.
        The value 'RSBEND' is not valid for field IDOCTYP.
    Procedure
        Check whether basic type RSBEND exists.
    help required

    Hi,
    Please find the below link may useful.
    http://wiki.ittoolbox.com/index.php/Re-Connect_R/3_and_BW
    Reg,
    Venkat

  • Basic type and idoc type

    hi iam having z-basic type how to find what is the standard idoc type(for ex MATMAS,Creamas) for that

    Step1. Go to WE30 and give the extended IDoc name
    Step2. Check the extension button and click on display
    Step3. Click on header button (Top 3rd left button)
    Step4. In Technical Attributes, you will get the name under "Linked Basic Type"
    Hope it solves your query...
    Regards,
    Prasoon Sahay
    Edited by: Prasoon Sahay on Sep 2, 2009 2:18 PM

  • Using user-defined data types in Forms 6i

    When I use the following code in Oracle Forms 6i
    PROCEDURE test IS
    prcl prcl_ty;
    BEGIN
    prcl := prcl.setParcel('xxx-xx-xxxx');
    END;
    I get 'Error 801'. However the above does work in SQL editor. The online help says PL/SQL8 client-side program units cannot support Oracle 8 object-related functionality and I suspect this is the reason I get the error from Forms. Is there a work-around for this.
    The TYPE is defined as:
    CREATE OR REPLACE
    TYPE PRCL_TY AS OBJECT
    (parcel VARCHAR2(11),
    MEMBER FUNCTION getBook RETURN VARCHAR2,
    MEMBER FUNCTION getMap RETURN VARCHAR2,
    MEMBER FUNCTION getItem RETURN VARCHAR2,
    MEMBER FUNCTION getItem_NS RETURN VARCHAR2,
    MEMBER FUNCTION getSplit      RETURN VARCHAR2,
    MEMBER FUNCTION find RETURN VARCHAR2,
    MEMBER FUNCTION find (yr in VARCHAR2) RETURN VARCHAR2,
    MEMBER FUNCTION isValid RETURN BOOLEAN,
    MEMBER FUNCTION toString                     RETURN VARCHAR2,
    MEMBER FUNCTION toString (par IN VARCHAR2) RETURN VARCHAR2,
    STATIC FUNCTION setParcel (istr IN VARCHAR2 DEFAULT '000-00-000A') RETURN prcl_ty) -- to be used as a constructor
    NOT FINAL
    CREATE OR REPLACE
    TYPE BODY PRCL_TY AS
    MEMBER FUNCTION getBook RETURN VARCHAR2 IS
    BEGIN
    return substr(self.parcel,1,3);
    END;
    MEMBER FUNCTION getMap RETURN VARCHAR2 IS
    BEGIN
    return substr(self.parcel,4,2);
    END;
    MEMBER FUNCTION getItem RETURN VARCHAR2 IS
    BEGIN
    return substr(self.parcel,6);
    END;
    MEMBER FUNCTION getItem_NS RETURN VARCHAR2 IS
    BEGIN
    return substr(self.parcel,6,3);
    END;
    MEMBER FUNCTION getSplit RETURN VARCHAR2 IS
    BEGIN
    return substr(self.parcel,9,1);
    END;
    MEMBER FUNCTION find RETURN VARCHAR2 IS
    found varchar2(1);
    BEGIN
    begin
    select 'x'
         into found
         from casrp
         where cp_book_num = self.getBook
         and cp_map_num = self.getMap
         and cp_item_num = self.getItem
              and rownum = 1;
         return 'CASRP';
         exception
         when NO_DATA_FOUND then
         begin
    select 'x'
         into found
         from pro_prop
         where pp_book_num = self.getBook
         and pp_map_num = self.getMap
         and pp_item_num = self.getItem
              and rownum = 1
              and NOT EXISTS (select 'x'
                                  from cncl_prcl
                                  where cr_book_num = self.getBook
                                  and cr_book_num = self.getMap
                                       and cr_book_num = self.getItem
                                       and rownum = 1);
         return 'PRO_PROP';
         exception
         when NO_DATA_FOUND then
              return '';
         end;
    end;
    END;
    MEMBER FUNCTION find (yr IN VARCHAR2) RETURN VARCHAR2 IS
    found varchar2(1);
    BEGIN
    begin
    select 'x'
         into found
         from casrp
         where cp_book_num = self.getBook
         and cp_map_num = self.getMap
         and cp_item_num = self.getItem
              and cp_tax_yr = yr
              and rownum = 1;
         return 'CASRP';
         exception
         when NO_DATA_FOUND then
         begin
    select 'x'
         into found
         from pro_prop
         where pp_book_num = self.getBook
         and pp_map_num = self.getMap
         and pp_item_num = self.getItem
              and pp_tax_yr = yr
              and rownum = 1
              and NOT EXISTS (select 'x'
                                  from cncl_prcl
                                  where cr_book_num = self.getBook
                                  and cr_book_num = self.getMap
                                       and cr_book_num = self.getItem
                                       and cr_tax_yr = yr
                                       and rownum = 1);
         return 'PRO_PROP';
         exception
         when NO_DATA_FOUND then
              return '';
         end;
    end;
    END;
    MEMBER FUNCTION isValid RETURN BOOLEAN IS
    i number;
    BEGIN
    for i in 1..8 loop
         if substr(parcel,i,1) not between '0' and '9' then
         return FALSE;
         end if;
         end loop;
         if nvl(substr(parcel,9,1),'#') not between 'A' and 'Z' and
         nvl(substr(parcel,9,1),'#') != '#' then
         return FALSE;
         end if;
         return TRUE;
    END;
    MEMBER FUNCTION toString RETURN VARCHAR2 IS
    BEGIN
    return self.toString('-');
    END;
    MEMBER FUNCTION toString (par IN VARCHAR2) RETURN VARCHAR2 IS
    BEGIN
    return self.getBook||par|| self.getMap||par|| self.getItem;
    END;
    STATIC FUNCTION setParcel (istr IN VARCHAR2 DEFAULT '000-00-000A') RETURN prcl_ty IS
    len number;
    pos number;
         lastch varchar2(1);
    temp varchar2(30);
    invalid_format exception;
         pragma exception_init(invalid_format,-9001);
    BEGIN
    temp := upper(istr);
    -- Find 1st occurance of '-'. If not in correct postion, pad book num with zeros.
         pos := instr(temp,'-',1,1);
    if pos > 0 then
         if pos != 4 then
    temp := lpad(substr(temp,1,pos-1),3,'0')||substr(temp,pos);
         end if;
    -- Find 2nd occurance of '-'. If not in correct postion, pad map num with zeros.
         pos := instr(temp,'-',1,2);
         if pos != 7 then
    temp := substr(temp,1,4)||lpad(substr(temp,5,1),2,'0')||substr(temp,pos);
         end if;
         -- Pad item num
         len := length(temp);
         lastch := substr(temp,len);
         temp := substr(temp,1,7)||lpad(substr(temp,8,len-1),3,'0');
         if lastch between 'A' and 'Z' then
              temp := temp||lastch;
         end if;
    end if;
    temp := replace(temp,'-','');
         if prcl_ty(temp).isValid then
    return (prcl_ty(temp));
         else
         raise invalid_format;
         end if;
    END;
    END;
    Rich Hall
    [email protected]

    You are correct in your assumptions. Client side PLSQL does not support user defined types like the one you are trying to use.
    There are no workarounds I am afraid.

  • Prob wth Extending HRMD_A06 basic type

    Hi All,
    I have some custom fields in PA0002 table. So i extended HRMD_A06 and in user-exits i am populating custom fields. Out bound side everything is OK. But it is giving 51 error in inbound side. Probelm with read_namtb subroutine. it is chking the custom segment in T777D table...
    I am unable to solve the problem. Can anyone hlp me in this regard.

    May be this helps you !!
    <b>
    FYI</b>
    <b>Symptom</b>The standard scenario for the distribution of HR master data and organizational data via message type HRMD_A only covers a limited number of infotypes.
    Additional standard infotypes should be distributed using a customer enhancement.
    Other terms
    PFAL, RHALEINI, HRMD_A
    Reason and Prerequisites
    In the standard scenario, only infotypes are distributed, which are required for a distributed HR in a non HR-system.
    Solution
    The following activities are required if standard infotype Pnnnn (with nnnn = infotype number) is to be distributed in addition.
    Consider the restrictions at the end of this note in particular!
    Release 3.1
    1. Source code corrections:
    According to the attachment (programs not contained in the standard system), repairs are necessary in the Includes LRHA2U06 and UP50RU01.
    You only have to change Include UP50RU01 if it is a PA infotype.
    If you also want to distribute infotypes starting with 2nnn or 9nnn, an additional repair in Include LRHALF01 is necessary. Remember that in this case the Infotype 2011 is stored differently than the other infotypes and cannot therefore be distributed.
    Note that these changes are not contained in the standard system.
    2. Customizing:
    Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system):
    For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number).
    Transaction SM30 for table T777D only for PD infotypes (in the sending system and the receiving system):
    For the entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
    Transaction WE30 for ZRMD_A01 (in the sending system and the receiving system):
    With Transaction WE30, create extension ZRMD_A01.
    Create E1PITYP as a reference segment type, as child segments of this, the extension segment types Z1Pnnnn. As an IDoc type, create ZRMD_A01 for the basic IDoc type HRMD_A01 and extension ZRMD_A01.
    Transaction WE82 (in the sending system and the receiving system):
    The entry for message type HRMD_A and basic IDoc type HRMD_A01 is copied to a new entry with the extension ZRMD_A01.
    Transaction WE20 (in the sending system):
    In the sending system, for the partner number of the receiving system in the outbound parameters, enter ZRMD_A01 as idoc type in the line for entry message type HRMD_A.
    Transaction WE57 (in the receiving system):
    Copy the entry for function module name IDOC_INPUT_HRMD, basic IDoc type HRMD_A01 and message type HRMD_A, and enter ZRMD_A01 in the field extension.
    As of Release 4.0B
    1. Source code corrections:
    Implement the attached advance corrections or:
    Apply Hot Package for 4.0B:   SAPKH40B02 or
    Legal Change Patch for 4.0B:  SAPKE40B02
    The Include UP50RU01 must only be changed if it is a PA infotype.
    Include UP50RU01 is not contained in the Hot Package and must be changed in accordance with the advance correction if the Legal Change Patch is not applied.
    After applying the Hot Package (and manually repairing the UP50RU01) or the Legal Change Patch, only the Customizing activities are necessary.
    2. Customizing
    Transaction WE31 for Z1Pnnnn (in the sending system and the receiving system) :
    For each additional infotype, create a new segment type Z1Pnnnn (with nnnn = infotype number). The function "Create by copying" can be used to reduce the work load.
    Transaction SM30 for table T777D (in the sending system and the receiving system):
    For entry infotype nnnn, enter Z1Pnnnn in field IDOC segment.
    Transaction WE30 for ZRMD_A02 (in the sending system and the receiving system):
    With Transaction WE30, recreate extension ZRMD_A02.
    The linked basic type is HRMD_A02. Insert the new Z1Pnnnn segments as child segments of E1PITYP.
    Transaction WE82 (in the sending system and the receiving system):
    Copy the entry for message type HRMD_A and basic type HRMD_A02 to a new entry with extension type ZRMD_A02.
    Transaction WE20 (in the sending system):
    In the sending system enter ZRMD_A02 as an 'Extension' for the partner number of the receiving system in the outbound parameters in the entry message type HRMD_A with basic type HRMD_A02.
    Transaction WE57 (in the receiving system):
    Copy the entry for the FM name IDOC_INPUT_HRMD, basic type HRMD_A02 and message type HRMD_A, and in field 'Extension' enter ZRMD_A02.
    As of Release 4.5A
    Here, the Customizing activities described in Release 4.0B are to be carried out.
    As of Release 4.5A, HRMD_A03 is used as the basic type and ZRMD_A03 is used as the extension type.
    As of Release 4.6A, HRMD_A04 is used as a basic type and ZRMD_A04 is used as an extension type.
    As of Release 4.6C, HRMD_A05 is used as a basic type and ZRMD_A05 is used as an extension type.
    As of Release 4.70, HRMD_A06 is used as a basic type and ZRMD_A06 is used as an extension type.
    Restrictions:
    SAP cannot offer any support concerning compatibility with different releases for the additional infotypes of the enhancement in the standard system. For release specific changes to the infotypes of the enhancement a client-specific solution must be found (project solution).
    Other known restrictions:
    Known restrictions are listed here with possible solution approaches. If you should discover a restriction that is not yet documented, you can inform us of this via the R/3 SAPNet Frontend with a low priority problem message.
    01/25/1999: PA infotypes with subtypes are not found in T591A
    For infotypes in personnel administration, whose subtypes are stored in a different table than T591A according to table T582A, distribution works in the transfer mode 'Insert' and using the change pointers. Distribution in the transfer mode 'Update' does not work. The approach to solve the problem is a customer-specific extension of the routine HR_INFTY_GET in program RHALEINI by the corresponding infotype/subtype combinations.
    02/01/1999: Workflow infotypes
    Workflow infotypes, thus in the area 12xx, are not supported since the object type workflow is not supported in the standard ALE scenario. The approach to solve the problem is the use of the manual transport connection (RHMOVE30).
    05/17/1999: Infotype 2011
    The Infotype 2011 is stored differently than the other infotypes and therefore cannot be distributed.
    11/09/2000: Segment for infotypes with a width of more than 1000 characters
    The maximum width of a segment is 1000 characters. For this reason it cannot be generated automatically for infotypes with a width of more than 1000 characters.
    A possible solution is to create the segment manually and to only insert the key fields and the application fields that are really needed in the segment in order to avoid exceeding the 1000 characters. The values of the fields are transported from infotype into the segment and vice versa in the case of infotypes that are distributed additionally. The reason is that the fields have the same names in segment and infotype.
    07/17/2002: In ALE inbound processing, only the data records of the infotypes are posted - similar to the infotypes to be distributed in the standard. No additional functions regarding possibly dependent or derived data in other (database) tables are executed. A solution approach is to distribute the dependent or derived data in a separate (customer) scenario or implement a customer exit (RHALE001) or a BADI (HRALE00INBOUND_IDOC) with the desired functionality.
    <b></b>

  • User defined table types sometimes show up a unknown data type in Profiler

    A couple of our users have a problem when using user defined table types. Calls are made using UDTT as variables and these are then passed to a stored procedure as parameters. Sometimes the application returns a timeout. In such situations a Profiler-Trace
    shows the following:
    declare @p4 unknown
    whereas the correct trace (that is sometimes displayed) should be:
    declare @p4 dbo.ReportFilterTableType
    ReportFilterTableType is a UDTT. The users do have correct permissions for the UDTT (otherwise they would never be usable for the user). What could be the reason that the data types for the variable
    @p4 in the example are sometimes returned as unknown and at other times are returned correctly as
    ReportFilterTableType? Could this possibly be a network related issue?
    Thank you.
    Graham Goodwin Email: [email protected]

    I know this is a old post, but i am also facing the same issue that too in my production server. Did you find any workarround for this issue. Please do reply. Critical problem we are facing.
    Alka, Is your problem timeouts when passing TVP parameters, or is it that a Profiler Trace shows type "unknown" for the TVP data type name?
    If your problem is timeouts, be aware that TVPs do not have statistics so the optimizer might not be able to generate an optimal plan for non-trivial queries. Declaring a primary key or unique constraint on the table type may help since that will provide
    useful cardinality information.  You may need to resort to hints in some cases.
    I suggest you start a new thread with details of your specific situation if the information in this thread doesn't help.
    Dan Guzman, SQL Server MVP, http://www.dbdelta.com

  • Use of around a type

    I am not familiar with the following convention, specifically the use of the < >.
    private ArrayList<ActionListener> actionListenerList;1) Looking for the meaning of the usage of < >.
    TIA

    It is used to define the type that the collection can hold. Follow the link to the tutorial on generics.
    http://java.sun.com/j2se/1.5/pdf/generics-tutorial.pdf
    Hope this helps,
    PS.

  • WHICH basic type for doing inbound PO closing (to tick delv complete ind)?

    Dear SAP Gurus,
    The IDoc should tick the delivery complete indicator of a PO, that's it.
    I think this should be very simple but I already tried using basic type PORDCH02 but not yet successful.
    Need your advise:whether i used the correct basic type? etc.
    Regards,
    WILL.

    nobody answers.

  • Shipment IDOC basic type TPSSHT01 Message type SHIPPL

    Hi,
    I tried changing the shipment to add a delivery to the shipment using a bapi. I have successfully added the delivery but  INbound IDOC but finally i ended up in error in the idoc stating "Transportation planning point has no partner for transportatn. planning"
    please let me know where am goin wrong.
    Thanks,
    Prem.

    Hi Sravan ,
    WE82  is used for - Assigning Message type to IDOC . Here only we assigned this WMTORD message type to IDOC  (DELVRY03).
    We have warehouse , we need to send the WMTORD ( Transport order ) to Warehouse . Then they can process the picking , packing , shipping and loading  and send the materials to customers . After completion of all process , they(WMS team) will send the WMTOCO ( Transport confirmation )  to us  .Then  We will generate the Invoice based on TO and purchase Order .
    My requirement  : Now , The warehouse team needs the delivery date also should include in WMTORD message .
    But i looked in all segments in DELVRY03 idoc , i didn't find any element belongs the delivery date .
    Please advice me and help on this same

  • Message type and IDoc type to update a sales order

    I can create sales order at WE19 by the message type SALESORDER_CREATEFROMDAT2 and IDoc type SALESORDER_CREATEFROMDAT202 . Can I use the same message type and IDoc type to update a sales document (sales order) and also how can I do (I mean, which structures should I use; at E1BPSDHD1X - UPDATEFLAG what should I enter? Put an X to update a document or etsc?)? I enter the "E1BPSDHD1X - UPDATEFLAG" as X, "E1BP_SENDER - LOG_SYSTEM", "E1BPSDITM - ITM_NUMBER", " E1BPSDITM - MATERIAL", "E1BPPARNR - PARTN_ROLE", "E1BPPARNR - PARTN_NUMB" and "E1BPSCHDL - REQ_QTY". The sales order quantity is at "E1BPSCHDL - REQ_QTY" and it is the field that I want to update. When I look at the transaction code BD87, I see the status text as "Enter a document number between 0005000000 and 0005999999". I cannot update the order. How can I update it? Canybody explain me in a detailed manner?
    Thanks in advance....
    Edited by: Hikmet Akcali on Oct 21, 2009 4:00 PM

    At the IDoc type pop-up selection, there are 3 types. These are: ORD_ID01, ORDERS05 and /NFM/ORDERS05. SAP system component version is SAP ECC 6.0 . I choose ORD_ID01. There are structures EDI_Z1, EDI_Z3, EDI_Z5, EDI_Z9 and EDI_Z53. Where should I enter the number of the sales document to be updated? Also, which function module should I choose?
    Edited by: Hikmet Akcali on Oct 21, 2009 5:34 PM

  • Using variables defined in an include or another program

    Hi,
    i'm trying to use some declarations in my program which are defined in an include or another program.
    1. I need to create a class whose definition is in an include
    2. i need to declare a variable like this
        v_temp TYPE l_temp ,  l_temp is a structure defined in an include .
    I'm trying to use the declarations in another program or an include in  my program. however, i dont want to use 'include' statement
    your help would be appreciated.
    Thanks,
    Kranthi.

    Hi Kranti,
    If u write the declarationin some other include or program n use it in other program, without using INCLUDE.. how would the complier understand where the declaration has come from?? U need to specify to the compiler the path of declaration and hence the include is included..
    If u dont intend to use INCLUDE, declare a data element in ABAP dictionary and use it in ur program..
    I dont think its possible to do it the way u have suggested..
    BTW, why arent u in favour of using the INCLUDE.. is it because it has a lot of declarations..
    Regards,
    Tanveer.
    Please mark helpful answers

Maybe you are looking for