Reference table of structure LBBIL_INVOICE ?

Hi Expert,
I want to create smartform based on standard SAP program.
Printing Program : RLB_INVOICE
Smartforms : SF_LB_INVOICE
I have problem during change smartform. The interface of smartform is IS_BIL_INVOICE TYPE LBBIL_INVOICE. This structure contain of other table type or other structure. I think this structure have complete data. But functional design always create design using database table that I must fetch the data.
Is there any body can tell me what is reference table of each element of structure LBBIL_INVOICE ?
Thanks beforehand.

Hi ,
These structures are deep structures and you  will have  the table  entered  as a field of this structure .
All the values are populated in these structures . Else copy the standard driver program  and  the key field is always populated in nast table get the keyfield from nast table ( nast  structure gets populated  autmatically  check in the std driver program )
eg   (   move nast-objky(10) to g_ebeln   )
based on this key field fetch all the other values you require in the driver program and pass it to your smart form .But i must say this is  not a smart  thing to do if you already have all the data available in the  standard structure .
give your  driver program and smartform name in NACE txn. also define the output type.  all the other data  retrival  can also be done in the code editor of smart form  in case you need some other values at a later stage.here is the sample code
FORM GET_DATA .
check not nast-objky is initial.
  move nast-objky(10) to g_ebeln.
ENDFORM.                    " GET_DATA
*&      Form  GET_FORMNAME
      text
-->  p1        text
<--  p2        text
FORM GET_FORMNAME .
select single sform
    from tnapr
    into tnapr-sform
   where kschl = nast-kschl " Output Type
     and nacha = nast-nacha " Message transmission
     and kappl = nast-kappl." Application
  if sy-subrc = 0.
    g_formname = tnapr-sform.
endif.
ENDFORM.                    " GET_FORMNAME
*&      Form  ZCALLFORM
      text
-->  p1        text
<--  p2        text
FORM ZCALLFORM .
call function 'SSF_FUNCTION_MODULE_NAME'
  exporting
    formname                 = g_formname
  VARIANT                  = ' '
  DIRECT_CALL              = ' '
importing
   fm_name                  = g_fmname
EXCEPTIONS
   NO_FORM                  = 1
   NO_FUNCTION_MODULE       = 2
   OTHERS                   = 3
if sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
call function g_fmname
  exporting
  ARCHIVE_INDEX              =
  ARCHIVE_INDEX_TAB          =
  ARCHIVE_PARAMETERS         =
  CONTROL_PARAMETERS         =
  MAIL_APPL_OBJ              =
  MAIL_RECIPIENT             =
  MAIL_SENDER                =
  OUTPUT_OPTIONS             =
  USER_SETTINGS              = 'X'
    im_ebeln                   = g_ebeln
IMPORTING
  DOCUMENT_OUTPUT_INFO       =
  JOB_OUTPUT_INFO            =
  JOB_OUTPUT_OPTIONS         =
exceptions
   formatting_error           = 1
   internal_error             = 2
   send_error                 = 3
   user_canceled              = 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.
ENDFORM.                    " ZCALLFORM
*&      Form  ZUPDATENAKT
      text
-->  p1        text
<--  p2        text
FORM ZUPDATENAKT .
nast-vstat = 1.
  nast-usnam = sy-uname.
  nast-datvr = sy-datum.
  nast-uhrvr = sy-uzeit.
  call function 'RV_MESSAGE_UPDATE_SINGLE'
    exporting
      msg_nast = nast.
ENDFORM.                    " ZUPDATENAKT

Similar Messages

  • Key Figure Reference table and fields

    I am getting the following error:
    /BIC/CSSMMIMI1-/BIC/KFMI_LCHF (specify reference table AND reference field)
    I am aware that it is asking me to put a reference table and field for the field in the structure.
    However, what I am not sure about is should I do this action from SE11 or is there a program or other method which would be more suitable (this is not business content)?
    Thanks

    Hi Edwin,
    Thanks for that, the currency type and quantity type are hard coded in the key figure for most of the key figures apart from one, i.e for the quanity I hard code PCS
    From RSD2 I just check the repair option is that correct

  • Reference table and field

    Hi Experts,
    When I am adding a new field NETWR in the structure to enhance the datasource and checking it, I am getting the following error:
         SPECIFY REFERENCE TABLE AND REFERENCE FIELD.
    How to over come this error?
    Kindly help me,
    Thanks in advance,
    Kannan

    Kannan,
    there will be reference fields specified in the table for this field - specifically currency / unit fields - you need to have these in your view to be able to activate the datasource.
    search the forums on the same also....
    Within the view - check the currency / units tab available in SE11.
    Edited by: Arun Varadarajan on Jun 9, 2009 1:18 AM

  • Internal Table and Structures

    Hi,
    I am a beginer. I know how to create a structure and how to create an internal table using ABAP/4. My problem is, i don't understand where to use internal table and structure, also i find myself very confused about the explicit work areas.
    Plese someone show me a program by explaining all of this clearly.

    Hi
    Internal tables are the core of ABAP. They are like soul of a body. For any program we use
    internal tables extensively. We can use Internal tables like normal data base tables only, but the
    basic difference is the memory allocated for internal tables is temporary. Once the program is
    closed the memory allocated for internal tables will also be out of memory.
    But while using the internal tables, there are many performance issues to be considered. i.e which
    type of internal table to be used for the program..like standard internal table, hashed internal
    table or sorted internal table etc..
    Internal tables
    Internal tables provide a means of taking data from a fixed structure and storing it in working memory in ABAP. The data is stored line by
    line in memory, and each line has the same structure. In ABAP, internal tables fulfill the function of arrays. Since they are dynamic data
    objects, they save the programmer the task of dynamic memory management in his or her programs. You should use internal tables
    whenever you want to process a dataset with a fixed structure within a program. A particularly important use for internal tables is for
    storing and formatting data from a database table within a program. They are also a good way of including very complicated data
    structures in an ABAP program.
    Like all elements in the ABAP type concept, internal tables can exist both as data types and as data objects A data type is the abstract
    description of an internal table, either in a program or centrally in the ABAP Dictionary, that you use to create a concrete data object. The
    data type is also an attribute of an existing data object.
    Internal Tables as Data Types
    Internal tables and structures are the two structured data types in ABAP. The data type of an internal table is fully specified by its line type,
    key, and table type.
    Line type
    The line type of an internal table can be any data type. The data type of an internal table is normally a structure. Each component of the
    structure is a column in the internal table. However, the line type may also be elementary or another internal table.
    Key
    The key identifies table rows. There are two kinds of key for internal tables - the standard key and a user-defined key. You can specify
    whether the key should be UNIQUE or NON-UNIQUE. Internal tables with a unique key cannot contain duplicate entries. The uniqueness
    depends on the table access method.
    If a table has a structured line type, its default key consists of all of its non-numerical columns that are not references or themselves
    internal tables. If a table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type
    is an internal table, the default key is empty.
    The user-defined key can contain any columns of the internal table that are not references or themselves internal tables. Internal tables
    with a user-defined key are called key tables. When you define the key, the sequence of the key fields is significant. You should remember
    this, for example, if you intend to sort the table according to the key.
    Table type
    The table type determines how ABAP will access individual table entries. Internal tables can be divided into three types:
    Standard tables have an internal linear index. From a particular size upwards, the indexes of internal tables are administered as trees. In
    this case, the index administration overhead increases in logarithmic and not linear relation to the number of lines. The system can access
    records either by using the table index or the key. The response time for key access is proportional to the number of entries in the table.
    The key of a standard table is always non-unique. You cannot specify a unique key. This means that standard tables can always be filled
    very quickly, since the system does not have to check whether there are already existing entries.
    Sorted tables are always saved sorted by the key. They also have an internal index. The system can access records either by using the
    table index or the key. The response time for key access is logarithmically proportional to the number of table entries, since the system
    uses a binary search. The key of a sorted table can be either unique or non-unique. When you define the table, you must specify whether
    the key is to be unique or not. Standard tables and sorted tables are known generically as index tables.
    Hashed tables have no linear index. You can only access a hashed table using its key. The response time is independent of the number of
    table entries, and is constant, since the system access the table entries using a hash algorithm. The key of a hashed table must be unique.
    When you define the table, you must specify the key as UNIQUE.
    Generic Internal Tables
    Unlike other local data types in programs, you do not have to specify the data type of an internal table fully. Instead, you can specify a
    generic construction, that is, the key or key and line type of an internal table data type may remain unspecified. You can use generic
    internal tables to specify the types of field symbols and the interface parameters of procedures . You cannot use them to declare data
    objects.
    Internal Tables as Dynamic Data Objects
    Data objects that are defined either with the data type of an internal table, or directly as an internal table, are always fully defined in
    respect of their line type, key and access method. However, the number of lines is not fixed. Thus internal tables are dynamic data objects,
    since they can contain any number of lines of a particular type. The only restriction on the number of lines an internal table may contain are
    the limits of your system installation. The maximum memory that can be occupied by an internal table (including its internal administration)
    is 2 gigabytes. A more realistic figure is up to 500 megabytes. An additional restriction for hashed tables is that they may not contain more
    than 2 million entries. The line types of internal tables can be any ABAP data types - elementary, structured, or internal tables. The
    individual lines of an internal table are called table lines or table entries. Each component of a structured line is called a column in the
    internal table.
    Choosing a Table Type
    The table type (and particularly the access method) that you will use depends on how the typical internal table operations will be most
    frequently executed.
    Standard tables
    This is the most appropriate type if you are going to address the individual table entries using the index. Index access is the quickest
    possible access. You should fill a standard table by appending lines (ABAP APPEND statement), and read, modify and delete entries by
    specifying the index (INDEX option with the relevant ABAP command). The access time for a standard table increases in a linear relationship
    with the number of table entries. If you need key access, standard tables are particularly useful if you can fill and process the table in
    separate steps. For example, you could fill the table by appending entries, and then sort it. If you use the binary search option with key
    access, the response time is logarithmically proportional to the number of table entries.
    Sorted tables
    This is the most appropriate type if you need a table which is sorted as you fill it. You fill sorted tables using the INSERT statement. Entries
    are inserted according to the sort sequence defined through the table key. Any illegal entries are recognized as soon as you try to add
    them to the table. The response time for key access is logarithmically proportional to the number of table entries, since the system always
    uses a binary search. Sorted tables are particularly useful for partially sequential processing in a LOOP if you specify the beginning of the
    table key in the WHERE condition.
    Hashed tables
    This is the most appropriate type for any table where the main operation is key access. You cannot access a hashed table using its index.
    The response time for key access remains constant, regardless of the number of table entries. Like database tables, hashed tables always
    have a unique key. Hashed tables are useful if you want to construct and use an internal table which resembles a database table or for
    processing large amounts of data.
    Creating Internal Tables
    Like other elements in the ABAP type concept, you can declare internal tables as abstract data
    types in programs or in the ABAP Dictionary, and then use them to define data objects.
    Alternatively, you can define them directly as data objects. When you create an internal table as a
    data object, you should ensure that only the administration entry which belongs to an internal
    table is declared statically. The minimum size of an internal table is 256 bytes. This is important if an
    internal table occurs as a component of an aggregated data object, since even empty internal
    tables within tables can lead to high memory usage. (In the next functional release, the size of the
    table header for an initial table will be reduced to 8 bytes). Unlike all other ABAP data objects, you
    do not have to specify the memory required for an internal table. Table rows are added to and
    deleted from the table dynamically at runtime by the various statements for adding and deleting
    records.
    You can create internal tables in different types.
    You can create standard internal table and then make it sort in side the program.
    The same way you can change to hashed internal tables also.
    There will be some performance issues with regard to standard internal tables/ hashed internal
    tables/ sorted internal tables.
    Internal table types
    This section describes how to define internal tables locally in a program. You can also define internal tables globally as data types in the
    ABAP Dictionary.
    Like all local data types in programs , you define internal tables using the TYPES statement. If you do not refer to an existing table type
    using the TYPE or LIKE addition, you can use the TYPES statement to construct a new local internal table in your program.
    TYPES <t> TYPE|LIKE <tabkind> OF <linetype> [WITH <key>]
    [INITIAL SIZE <n>].
    After TYPE or LIKE, there is no reference to an existing data type. Instead, the type constructor occurs:
    <tabkind> OF <linetype> [WITH <key>]
    The type constructor defines the table type <tabkind>, the line type <linetype>, and the key <key> of the internal table <t>.
    You can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
    Table type
    You can specify the table type <tabkind> as follows:
    Generic table types
    INDEX TABLE
    For creating a generic table type with index access.
    ANY TABLE
    For creating a fully-generic table type.
    Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic
    type INDEX TABLE includes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot
    pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You
    can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and
    parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
    Fully-Specified Table Types
    STANDARD TABLE or TABLE
    For creating standard tables.
    SORTED TABLE
    For creating sorted tables.
    HASHED TABLE
    For creating hashed tables.
    Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for
    standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
    Line type
    For the line type <linetype>, you can specify:
    Any data type if you are using the TYPE addition. This can be a predefined ABAP type, a local type in the program, or a data type from the
    ABAP Dictionary. If you specify any of the generic elementary types C, N, P, or X, any attributes that you fail to specify (field length, number
    of decimal places) are automatically filled with the default values. You cannot specify any other generic types.
    Any data object recognized within the program at that point if you are using the LIKE addition. The line type adopts the fully-specified data
    type of the data object to which you refer. Except for within classes, you can still use the LIKE addition to refer to database tables and
    structures in the ABAP Dictionary (for compatibility reasons).
    All of the lines in the internal table have the fully-specified technical attributes of the specified data type.
    Key
    You can specify the key <key> of an internal table as follows:
    [UNIQUE|NON-UNIQUE] KEY <col1> ... <col n>
    In tables with a structured line type, all of the components <coli> belong to the key as long as they are not internal tables or references,
    and do not contain internal tables or references. Key fields can be nested structures. The substructures are expanded component by
    component when you access the table using the key. The system follows the sequence of the key fields.
    [UNIQUE|NON-UNIQUE] KEY TABLE LINE
    If a table has an elementary line type (C, D, F, I, N, P, T, X), you can define the entire line as the key. If you try this for a table whose line
    type is itself a table, a syntax error occurs. If a table has a structured line type, it is possible to specify the entire line as the key. However,
    you should remember that this is often not suitable.
    [UNIQUE|NON-UNIQUE] DEFAULT KEY
    This declares the fields of the default key as the key fields. If the table has a structured line type, the default key contains all non-numeric
    columns of the internal table that are not and do not contain references or internal tables. If the table has an elementary line type, the
    default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
    Specifying a key is optional. If you do not specify a key, the system defines a table type with an arbitrary key. You can only use this to
    define the types of field symbols and the interface parameters of procedures . For exceptions, refer to Special Features of Standard Tables.
    The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can
    accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can
    only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions:
    You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically.
    You must always specify the UNIQUE option when you create a hashed table.
    Initial Memory Requirement
    You can specify the initial amount of main memory assigned to an internal table object when you define the data type using the following
    addition:
    INITIAL SIZE <n>
    This size does not belong to the data type of the internal table, and does not affect the type check. You can use the above addition to
    reserve memory space for <n> table lines when you declare the table object.
    When this initial area is full, the system makes twice as much extra space available up to a limit of 8KB. Further memory areas of 12KB each
    are then allocated.
    You can usually leave it to the system to work out the initial memory requirement. The first time you fill the table, little memory is used. The
    space occupied, depending on the line width, is 16 <= <n> <= 100.
    It only makes sense to specify a concrete value of <n> if you can specify a precise number of table entries when you create the table and
    need to allocate exactly that amount of memory (exception: Appending table lines to ranked lists). This can be particularly important for
    deep-structured internal tables where the inner table only has a few entries (less than 5, for example).
    To avoid excessive requests for memory, large values of <n> are treated as follows: The largest possible value of <n> is 8KB divided by the
    length of the line. If you specify a larger value of <n>, the system calculates a new value so that n times the line width is around 12KB.
    Examples
    TYPES: BEGIN OF LINE,
    COLUMN1 TYPE I,
    COLUMN2 TYPE I,
    COLUMN3 TYPE I,
    END OF LINE.
    TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
    The program defines a table type ITAB. It is a sorted table, with line type of the structure LINE and a unique key of the component
    COLUMN1.
    TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
    TYPES: BEGIN OF LINE,
    COLUMN1 TYPE I,
    COLUMN2 TYPE I,
    COLUMN3 TYPE I,
    END OF LINE.
    TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
    TYPES: BEGIN OF DEEPLINE,
    FIELD TYPE C,
    TABLE1 TYPE VECTOR,
    TABLE2 TYPE ITAB,
    END OF DEEPLINE.
    TYPES DEEPTABLE TYPE STANDARD TABLE OF DEEPLINE
    WITH DEFAULT KEY.
    The program defines a table type VECTOR with type hashed table, the elementary line type I and a unique key of the entire table line. The
    second table type is the same as in the previous example. The structure DEEPLINE contains the internal table as a component. The table
    type DEEPTABLE has the line type DEEPLINE. Therefore, the elements of this internal table are themselves internal tables. The key is the
    default key - in this case the column FIELD. The key is non-unique, since the table is a standard table.
    Internal table objects
    Internal tables are dynamic variable data objects. Like all variables, you declare them using the DATA statement. You can also declare static
    internal tables in procedures using the STATICS statement, and static internal tables in classes using the CLASS-DATA statement. This
    description is restricted to the DATA statement. However, it applies equally to the STATICS and CLASS-DATA statements.
    Reference to Declared Internal Table Types
    Like all other data objects, you can declare internal table objects using the LIKE or TYPE addition of the DATA statement.
    DATA <itab> TYPE <type>|LIKE <obj> [WITH HEADER LINE].
    Here, the LIKE addition refers to an existing table object in the same program. The TYPE addition can refer to an internal type in the
    program declared using the TYPES statement, or a table type in the ABAP Dictionary.
    You must ensure that you only refer to tables that are fully typed. Referring to generic table types (ANY TABLE, INDEX TABLE) or not
    specifying the key fully is not allowed (for exceptions, refer to Special Features of Standard Tables).
    The optional addition WITH HEADER line declares an extra data object with the same name and line type as the internal table. This data
    object is known as the header line of the internal table. You use it as a work area when working with the internal table (see Using the
    Header Line as a Work Area). When you use internal tables with header lines, you must remember that the header line and the body of the
    table have the same name. If you have an internal table with header line and you want to address the body of the table, you must indicate
    this by placing brackets after the table name (<itab>[]). Otherwise, ABAP interprets the name as the name of the header line and not of the
    body of the table. You can avoid this potential confusion by using internal tables without header lines. In particular, internal tables nested
    in structures or other internal tables must not have a header line, since this can lead to ambiguous expressions.
    TYPES VECTOR TYPE SORTED TABLE OF I WITH UNIQUE KEY TABLE LINE.
    DATA: ITAB TYPE VECTOR,
    JTAB LIKE ITAB WITH HEADER LINE.
    MOVE ITAB TO JTAB. <- Syntax error!
    MOVE ITAB TO JTAB[].
    The table object ITAB is created with reference to the table type VECTOR. The table object JTAB has the same data type as ITAB. JTAB also
    has a header line. In the first MOVE statement, JTAB addresses the header line. Since this has the data type I, and the table type of ITAB
    cannot be converted into an elementary type, the MOVE statement causes a syntax error. The second MOVE statement is correct, since
    both operands are table objects.
    Declaring New Internal Tables
    You can use the DATA statement to construct new internal tables as well as using the LIKE or TYPE addition to refer to existing types or
    objects. The table type that you construct does not exist in its own right; instead, it is only an attribute of the table object. You can refer to
    it using the LIKE addition, but not using TYPE. The syntax for constructing a table object in the DATA statement is similar to that for defining
    a table type in the TYPES statement.
    DATA <itab> TYPE|LIKE <tabkind> OF <linetype> WITH <key>
    [INITIAL SIZE <n>]
    [WITH HEADER LINE].
    As when you define a table type , the type constructor
    <tabkind> OF <linetype> WITH <key>
    defines the table type <tabkind>, the line type <linekind>, and the key <key> of the internal table <itab>. Since the technical attributes of
    data objects are always fully specified, the table must be fully specified in the DATA statement. You cannot create generic table types (ANY
    TABLE, INDEX TABLE), only fully-typed tables (STANDARD TABLE, SORTED TABLE, HASHED TABLE). You must also specify the key and whether
    it is to be unique (for exceptions, refer to Special Features of Standard Tables).
    As in the TYPES statement, you can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
    You can create an internal table with a header line using the WITH HEADER LINE addition. The header line is created under the same
    conditions as apply when you refer to an existing table type.
    DATA ITAB TYPE HASHED TABLE OF SPFLI
    WITH UNIQUE KEY CARRID CONNID.
    The table object ITAB has the type hashed table, a line type corresponding to the flat structure SPFLI from the ABAP Dictionary, and a
    unique key with the key fields CARRID and CONNID. The internal table ITAB can be regarded as an internal template for the database table
    SPFLI. It is therefore particularly suitable for working with data from this database table as long as you only access it using the key.

  • Caching system for loading reference table data

    Hi,
    I want to load the small reference table data into memory and later i want to query the data in the memory. That table wont be updated frequenctly.I dont want to to load the query results in the memory. As i know i can do it by IBatis or Hibernate. I want to load the reference table data into memory once and want to use the data in memory for querying. Suppose i have a Department table with 100 rows with columns as DeptNO, DeptName and NoOfEmployees. I want to load all the records in to memory and later i want to run queries like getDepartmes where NoEmployees >50. queries can be dynamic.Is it possible with any Java caching systems.

    They allow you to manipulate collections (duh) of objects. Typically, but not exclusively, using a comparator or somesuch. The sort of operation you're describing can be carried out reasonably swiftly by merely iterating over the items - unlikely to be as slow as a database round-trip.
    If you need something particularly sophisticated then you can either craft a suitable data structure to contain it, or go for the generic solution of an embedded database (and if you go for this option, you might want to apologise for biting my head off).
    Or, indeed, you can use a query cache if you need no dynamic capabilities whatsoever (i.e. query with a <50 constraint twice and the second one is fast, but do it again with a <49 constraint and it takes just as long as the first one).

  • How to ADD reference table and make a field as currency field in dictionary

    pls render some info on how to add refernce table and ref field if i want to make an added field as a currency or quantity field...

    Hi Kiran,
    It sounds like you are creating a "Z" table or structure and have defined a quantity (eg MENGE). But when you run the syntax check, the system is saying you need to define a reference table / field.
    Well when you are in SE11, click on the "Currency / Quantity Fields" tab. You will see 2 columns called "Reference Table" and "Reference Field". These 2 columns define the unit of measure for the currency / qty.
    If you have defined in your table MENGE and MEINS and the MEINS field is the unit of measure for the MENGE field you should define your fields as such (inthe Currency/Quantity Fields" tab:
    Table - ZVBAP
    MENGE MENGE_D QUAN ZVBAP MEINS
    MEINS MEINS   UNIT
    Hope this makes sense.
    Cheers,
    Pat.
    PS. Kindly assign Reward Points to the posts you find helpful.

  • Error while creating Cross-reference table using Xreftool (PIP Ins)

    Error while running xref.sh script unable to create cross reference table.
    **Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool**
    Could not find xref directory within tip folder (/OracleAS_1/bpel/docs/workflow/oracle/tip)
    searched for similar issue in OTN it says issue fixed by upgrading Oracle AS, we are using 10.1.3.4 MLR#8
    http://kr.forums.oracle.com/forums/thread.jspa?threadID=835446
    steps followed.
    Creating Cross-Reference Tables
    Complete the following procedure to create cross-reference tables.
    To create cross-reference tables
    1 Navigate to the following directory:
    %SOAHOME%/SiebelODOPPIP/scripts/
    2 Open the following file for editing:
    xref.sh
    3 Set the userid and passwd for logging into BPEL console on the appropriate lines.
    4 Set the correct SOA_HOME location on the appropriate line.
    5 Save and close the file.
    6 Make the file executeable:
    chmod +x xref.sh
    dos2unix xref.sh
    7 Change directory (cd) to integration/esb/bin under %SOAHOME%.
    8 Execute ../../../SiebelODOPPIP/scripts/xref.sh.
    I am using SOA suite 10.1.3.3 and getting same error
    Error: Exception in thread "main" java.lang.NoClassDefFoundError: oracle/tip/xref/tool/AdminTool

    Hi Abhijeet,
    please check in transaction FI01, about your data consistencies. You can use this wiki help in terms of Address, it it found any useful facts for you
    Address Checks - Business Address Services (BC-SRV-ADR) - SAP Library

  • Tables and structures are used in a standard scripts

    how to find which tables and structures are used in a standard scripts?
    pls explain step by step process...
    Edited by: abap on Jun 21, 2008 4:36 PM

    Go to Transaction SE80, Select Program and paste that program name below..
    Then drop down the tree of that program...then you will find option " Dict. Structures"..
    Here you can find the tables which has been you for that transaction / program.
    Regards,
    Santosh

  • For output display report is final_internal table or structure in wd ABAP?

    Hi all,
    for output display report is final_internal table or structure in wd ABAP?
    in wd java output display report -.> CALLING rfc and that RFC OUTPUT table
    finally in internal table is assigned to STRUCTURE .Same procdure?
    Thanks,
    RAMA

    Dear Madhu,
    thanks for guidence!
    its showing popup tht this BADI ( ME_CHANGE_OUTTAB_CUS ) is only use for "SAP Internal  use".
    Regards,
    Praphull

  • Difference btw table and structure???

    Hi all guru's
    What is the difference between table and structure??
    culd you explain me???
    regards
    ss

    hi Supriya,
    structure is one single line, while a table can have as many lines as you wish.
    hope this helps
    ec

  • How to create a table less structure with dynamic menu module

    Hi guys,
    I am using dynamic menu module for creating a main menu for http://firstsite08.businesscatalyst.com/
    but it is generating table structure. What changes to do i had to make to generate a table less structure from dynamic menu module.

    Hi Andy,
    When you create a Menu, the option dropdown for the menu has Default, but under that you will see HTML CSS Only option which creates a ul li structure.
    For the Menu Module options you can find more information from the knowledgebase: http://kb.worldsecuresystems.com/134/bc_1345.html?bc-partner#main_Menu_Modules
    If you would like to use the version 2 menu module you can find a bit of a guide I wrote here: http://forums.adobe.com/docs/DOC-1903

  • Reference Table

    Hi,
      I am creating a purchase header and item table(With same fields as in the standard table) in SE11. But when iam creating the Purchase item, it is giving error that
    ZPURI-MENGE (specify reference table AND reference field)
    ZPURI-NETPR (specify reference table AND reference field)
    ZPURI-NETWR (specify reference table AND reference field)
    Table ZPURI must be created in the database
    Check on table ZPURI resulted in errors.
    Why Iam getting the error when iam creating the purchase item table only?

    Hi ram,
    1. Since menge, netpr , netwr are quantity/currency fields,
       they need the UNIT field also.
    2. ie, if u observe, there must be one more field 
       MEINS or WAERS
       for which some REFERENCE has to be given
       in se11,
        <b>in the 5th TAB</b> (Currency Quantity Fields)
    3. For each such field,
       u will see the table name and field name.
    4. Just give that and it will be ok.
    regards,
    amit m.

  • Reference Table and Fields for Units and Currency

    Can anyone advise on what the reference tables and fields are for currency and quantity key figures? Thanks
    I think for currency the table is TCURC and field is WAERS, does this make sense, not sure for the quantity though
    Message was edited by:
            Niten Shah

    Hi try these -
    TCURC          (Currency codes)
    TCURF          (Translation factors)
    TCURN          (Notations)
    TCURS          (Exchange Rate Spreads)
    TCURT          (Description of the Currency Code)
    TCURV          (Exchange rate types for currency translation)
    TCURW     (Use of exchange rate types)
    TCURX          (Decimal places of the currencies)
    Regards
    Vikash

  • Identify reference Table and filed for...

    Hi
    How to identify the Reference table and field for the particular Currency and quantity field.
    Regards
    Raghav

    Hi there,
    if you want to find out the reference table and field for the particular currency or date field follow the steps given below.
    1. tcode SE11  and give the table name,
    2. double click on the dataelement for which you would like to findout the details.
    3. Place the cursor on the dataelement name and click on the Whereused button
       Utilities --> Where-Used list.
    4. Uncheck all the checkboxes and check Table Fields.
    5. Hit Enter, that should give you all the tables and fields where this dataelement is being used.
    6. You can mention any of the tables as a reference table or fields.
    Hope you found this useful.
    Thanks-
    Rahul.

  • To which table the structure plknzea belongs

    i need to find out the table to which this sturcture(plknzea) belongs.
    how the table fplt is related to table aufk

    This structure is only used in two programs to hold certain data from screen fields.  Depending on certain values of these fields, it sets a value to view V_T350_P, which is a view over T350.
    Code from L0I04I10.
      IF PLKNZEA-SOFT EQ YAUSW.
        V_T350_P-PLKNZ = YAUFT_SOFT.
      ELSE.
        IF PLKNZEA-GEPL EQ YAUSW.
          V_T350_P-PLKNZ = YAUFT_GEPL.
        ELSE.
          IF PLKNZEA-UNGP EQ YAUSW.
            V_T350_P-PLKNZ = YAUFT_UNGP.
          ENDIF.
        ENDIF.
      ENDIF.
    It does something simular in the other program.
    Code from LCOIHI06.
      CLEAR CAUFVD-PLKNZ.
      IF  PLKNZEA-UNGP = YX.
        CAUFVD-PLKNZ = SPACE.
      ELSEIF PLKNZEA-GEPL = YX.
        CAUFVD-PLKNZ = 1.
      ELSEIF PLKNZEA-SOFT = YX.
        CAUFVD-PLKNZ = 2.
      ENDIF.
    Does this answer your question?
    Regards,
    Rich Heilman

Maybe you are looking for