What is the table of field *DABMG*

Hi all,
i have made a smart form for GOODS RESERVATION in which i have to print Removed Quantity.When i execute the report of MB25,it shows me the field Removed Quantity with Technical Field Name DABMG.Problem is that i can't find in which table this value is been stored.
Thanks & Regards,
sappk25

Please make where-used for data element DABMG in se11. you can find that. also check table EKET (Iam not sure 100%)
a®

Similar Messages

  • What are  the tables and fields  in fico & sd module

    what are  the tables and fields  in fico & sd module

    Hi,
    <b> Sales and Distribution:</b>
    Customers KNA1 General Data
    KNB1 Customer Master – Co. Code Data (payment method, reconciliation acct)
    KNB4 Customer Payment History
    KNB5 Customer Master – Dunning info
    KNBK Customer Master Bank Data
    KNKA Customer Master Credit Mgmt.
    KNKK Customer Master Credit Control Area Data (credit limits)
    KNVV Sales Area Data (terms, order probability)
    KNVI Customer Master Tax Indicator
    KNVP Partner Function key
    KNVD Output type
    KNVS Customer Master Ship Data
    KLPA Customer/Vendor Link
    Sales Documents VBAKUK VBAK + VBUK
    VBUK Header Status and Administrative Data
    VBAK Sales Document – Header Data
    VBKD Sales Document – Business Data
    VBUP Item Status VBAP Sales Document – Item Data
    VBPA Partners
    VBFA Document Flow
    VBEP Sales Document Schedule Line
    VBBE Sales Requirements: Individual Records
    SD Delivery DocumeLIPS Delivery Document item data, includes referencing PO
    LIKP Delivery Document Header data
    Billing Document VBRK Billing Document Header
    VBRP Billing Document Item
    SD Shipping Unit VEKP Shipping Unit Item (Content)
    VEPO Shipping Unit Header
    <b>Financial Accounting</b>
    FBAS             Financial Accounting “Basis”
    BKPF             Accounting Document Header              BUKRS / BELNR / GJAHR
    BSEG             Accounting Document Segment             BUKRS / BELNR / GJAHR / BUZEI
    BSIP             Index for Vendor Validation of Double   BUKRS / LIFNR / WAERS / BLDAT /
                     Documents                               XBLNR / WRBTR / BELNR / GJAHR / BUZEI
    BVOR             Inter Company Posting Procedure         BVORG / BUKRS / GJAHR / BELNR
    EBKPF            Accounting Document Header (docs from   GLSBK / BELNR / GJHAR / GLEBK
                     External Systems)
    FRUN             Run Date of a Program                   PRGID
    KLPA             Customer / Vendor Linking               NKULI / NBUKR / NKOAR / PNTYP
                                                             / VKULI / VBUKR / VKOAR
    KNB4             Customer Payment History                KUNNR / BUKRS
    KNB5             Customer Master Dunning Data            KUNNR / BUKRS / MABER
    KNBK             Customer Master Bank Details            KUNNR / BANKS / BANKL / BANKN
    KNC1             Customer Master Transaction Figures     KUNNR / BUKRS / GJHAR
    KNC3             Customer Master Special GL Transactions KUNNR / BUKRS / GJAHR / SHBKZ
                     Figures
    LFB5             Vendor Master Dunning Data              LIFNR / BUKRS / MABER
    LFBK             Vendor Master Bank Details              LIFNR / BANKS / BANKL / BANKN
    LFC1             Vendor Master Transaction Figures       LIFNR / BUKRS / GJHAR
    LFC3             Vendor Master Special GL Transactions   LIFNR / BUKRS / GJHAR / SHBKZ
                     Figures
    VBKPF            Document Header for Document Parking    AUSBK / BUKRS / BELNR / GJHAR
    FBASCORE         Financial Accounting General Services “Basis”
    KNB1             Customer Master (Company Code)          KUNNR / BUKRS
    LFA1             Vendor Master (General Section)         LIFNR
    LFB1             Vendor Master (company Code Section)    LIFNR / BUKRS
    SKA1             G/L Account Master (Chart of Accounts)  KTOPL / SAKNR
    SKAT             G/L Account Master (Chart of Accounts – SPRAS / KTOPL / SAKNR
                     Description)
    MAHNS            Accounts Blocked by Dunning Selection   KOART / BUKRS / KONKO / MABER
    MHNK             Dunning Data (Account Entries)          LAUFD / LAUFI / KOART / BUKRS /
                                                             KUNNR / LIFNR / CPDKY / SKNRZE /
                                                             SMABER / SMAHSK / BUSAB
    FI-GL-GL (FBS)   General Ledger Accounting: Basic Functions- G/L Accounts
    SKAS             G/L Account Master (Chart of Accounts – SPRAS / KTOPL / SAKNR / SCHLW
                     Key Word list)
    SKB1             G/L Account Master (Company Code)       BUKRS / SAKNR
    FI-GL-GL (FBSC)  General Ledger Accounting: Basic
                     Functions - R/3 Customizing for G/L Accounts
    FIGLREP          Settings for G/L Posting Reports        MANDT
    TSAKR            Create G/L account with reference       BUKRS / SAKNR
    FI-GL-GL (FFE)   General Ledger Accounting: Basic
                     Functions - Fast Data Entry
    KOMU             Account Assignment Templates for G/L    KMNAM / KMZEI
                     Account items
    FI-AR-AR (FBD)   Accounts Receivable: Basic Functions - Customers
    KNKA             Customer Master Credit Management :     KUNNR
                     Central Data
    KNKK             Customer Master Credit Management :     KUNNR / KKBER
                     Control Area Data
    KNKKF1           Credit Management : FI Status data      LOGSYS / KUNNR / KKBER / REGUL
    RFRR             Accounting Data – A/R and A/P           RELID / SRTFD / SRTF2
                     Information System
    FI-BL-PT         Bank Accounting: Payment (BFIBL_CHECK_D)  Transactions – General Sections
    PAYR             Payment Medium File                     ZBUKR / HBKID / HKTID / RZAWE /
                                                             CHECT
    PCEC             Pre-numbered Check                      ZBUKR / HBKID / HKTID / STAPL
    FI-BL-PT-AP(FMZA)Bank Accounting: Payment Transactions – Automatic Payments
    F111G            Global Settings for Payment Program for MANDT
                     Payment Requests
    FDZA             Cash Management Line Items in Payment   KEYNO
                     Requests
    PAYRQ            Payment Requests                        KEYNO
    Hope this solves your concern...
    Regards,
    Habeeb
    Assign points if helpful

  • What is the Table name & Field Name for Clearing text field in F-53 Transac

    Hi,
    I need prepare a functional specification for Clearing text field in Check Register.I am not able to find the Table name and Field Name for Clearing text field in F 53 transaction code.Kindly provide me the Table and filed name.so that i can proceed.Kindly help me.
    I will assign points.
    Thanks
    Sunitha

    Hi
    From the payment document you have to link to the clearing document (Number BSEG-AUGBL, same Fiscal year and Company Code) in the clearing document the text entered in the transaction can be found on item text (BSEG-TEXT).
    RF05A is a Structure name
    Ranga
    Edited by: Ranga Swamy on Dec 4, 2008 7:55 PM

  • What are the tables and field where Cost Center info. is stored ?

    Hi Experts,
    One of my customer is using the Cost Center / Profit Center and mention the same in all document. Now for particular Incoming Payment customer wants to print the dimention wise details entered in incoming payment as well as out going payment.
    Can anybody tell me from which table / fields I can retrive this information ? Particularly in Crystal Report.
    Thanking in advance,
    Samir Gandhi

    No response ?
    Does anybody monitoring this or not ?
    BR
    Samir Gandhi

  • What is the table name and field name for Street 2, street3 in Vendor mast.

    Hi,
    I have a BDC code for Vendor master. I just need to insert the fields street 2, street3, stree4 and street5 in the code. Can I insert it in the code directly without re-recording? If yes then what would be the table and field names for the fields mentioned above.
    Thanks & Regards,
    Sriram

    Hi Sriram,
       Its a Configuration Setting to bring the Check box ask your SD consultant, else directly insert this try, change your internal table filed here,
      PERFORM bdc_dynpro USING 'SAPMF02K'    '0100'.
      PERFORM: bdc_field USING 'RF02K-BUKRS' indata-bukrs,
               bdc_field USING 'RF02K-EKORG' indata-ekorg,
               bdc_field USING 'RF02K-KTOKK' indata-ktokk,
               bdc_field USING 'USE_ZAV'     'X',------------------------>this part is check box
               bdc_field USING 'BDC_OKCODE'  '/00'.
    for street just try this without re-recording,
    PERFORM bdc_field  USING 'ADDR1_DATA-NAME1'       indata-name1.
      PERFORM bdc_field  USING 'ADDR1_DATA-NAME2'       indata-name2.
      PERFORM bdc_field  USING 'ADDR1_DATA-SORT1'       indata-sortl.
      PERFORM bdc_field  USING 'ADDR1_DATA-STREET'      indata-stras.
      PERFORM bdc_field  USING 'ADDR1_DATA-POST_CODE1'  indata-pstlz.
      PERFORM bdc_field  USING 'ADDR1_DATA-CITY1'       indata-ort01.
      PERFORM bdc_field  USING 'ADDR1_DATA-COUNTRY'     indata-land1.
      PERFORM bdc_field  USING 'ADDR1_DATA-REGION'      V_regio.
      PERFORM bdc_field  USING 'ADDR1_DATA-PO_BOX'      indata-pfach.
      PERFORM bdc_field  USING 'ADDR1_DATA-STR_SUPPL2'  indata-suppl2.
      PERFORM bdc_field  USING 'ADDR1_DATA-TAXJURCODE'  indata-txjcd.

  • How can L identify what are the not null fields of a table in a stored procedure ?

    How can L identify what are the not null fields of a table in a stored procedure ?

    You could query the data dictionary:
    SELECT column_name
    FROM all_tab_columns
    WHERE owner = '...'
    AND table_name = '...'
    AND nullable = 'N'

  • What are the table names for CRM and APO?

    hi friends,
    what are the table names for CRM and APO?
    Regards
    suneel.

    hi Suneel,
    check in crm forum
    Re: SAP-CRM Tables
    BUT051 BP Relationship: Contact Person Relationship
    Similar to BUT050 , additionally contains Contact Person’s Address data
    BUT0BK Business Partner: Bank Data & Details
    BP Number, Bank Key, Bank Country Key, Bank Account Number
    BNKA Bank Master Data
    BUT100 BP: Roles
    ADR2 Telephone Numbers (Business Address Services)
    ADR6 SMTP Numbers (Business Address Services)
    Contains Email – Id of the BP.
    ADRC Addresses (Business Address Services)
    BP’s Complete Address Details- City, Country, Post Code, District, Street, Title No Etc
    TSAD3T Table containing the Title text against a Title No.
    COMM_PRODUCT Master Table for Product
    CRMM_BUAG Master table for Business Agreement
    CRMM_BUAG_H Header Data for Business Agreement such as Tax Category, Tax Characteristic, Form key, Business Agreement Class. Data in this table correspond to ISU CRMD_ORDERADM_H Contains the Header Information for a Business Transaction.
    Note:
    1. It doesn’t store the Business Partner
    responsible for the transaction. To
    get the Partner No, link it with
    CRM_ORDER_INDEX.
    2. This table can be used for search
    based on the Object Id(Business
    Transaction No).
    CRMD_CUSTOMER_H Additional Site Details at the Header Level of a Business Transaction
    CRMC_PROC_TYPE Master table Business Transaction Type
    CRMC_PARTNER_FCT Definition of Partner Functions
    SCPRIOT Priorities for Activities with priority text.
    CRMC_PROC_TYPE_T Text for a transaction type
    CRMC_ACT_OBJ_T Objective Number and Text for Activities
    TJ30T All the status code and text
    CRMC_PR_ASSIGN : Transaction Type and its Transaction Type Object.
    IBIB : Installed Base/Ibase
    IBIN : Installed Base Components
    COMM_PRODUCT : Products
    CRMC_T077D : customer account groups
    CRMD_ORDERADM_H (for header) CRMD_ORDERADM_I (Item data)
    CRMD_ORDERADM_H Business Transactions CRM
    CRMD_ACTIVITY_H Activity
    CRMD_OPPORT_H Opportunity
    BUTOO : Customer details
    BUT001 BP: General data II
    BUT100 BP: Roles
    BUT150 BP relationship: Attribute table (test
    different
    BUT_HIER_TREE Business Partner Group Hierarchy
    CDBC_T_PRODUCTID Mapping: Product Id
    CDBD_ORGMAN Business transaction - organizational unit -
    set
    COMC_PRODUCT General Product Settings
    COMC_R3_FIELDS Assignment of R/3 material master fields to
    CFOP
    COMM_CATEGORY Category
    COMM_CFGMAT Basic Data for Materials
    COMM_HIERARCHY Category Hierarchy
    COMP_TYPES Hierarchy Tool: Comparison Type Check
    Table
    CRMC_CPRICPROC Customer Pricing Procedures
    SMOKVBEZ15 Assignment employees to positions
    CRMMLSGUID: GUID entry (should match GUID in CRMPRLS)
    CRMM_BUT_CUSTNO : Also GUID table (GUID here should match GUID in R/3 table CRMKUNNR)
    SMOFSUBTAB : Mapping & Parameters
    SMOFDSTAT : Download Monitor (R4AM1)
    SMOFFILTAB : Filters (Should match filters in R3AC1 & R/3 Table CRMFILTAB)
    SMOFOBJECT Definition of Objects for Download
    SMOFOBJPAR Parent Objects of an Object in Table
    SMOFPARSFA Middleware Parameter
    SMOFQFIND Queue Finder Table for MW-Queue finder
    SMOFTABLES Definition of Tables for Download

  • What is the table used outgoing payment to vendors?

    What is the table used outgoing payment to vendors?
    And which field in the table records the tax code

    Hi Priyanka,
    We need to make clear that which table is used in different step in purchasing process regarding to tax.
    For example,
    When I post a PO, I can input tax code for each line item. Which table is used to store such information?
    When I post an invoice, I can also input tax code. Which table is used to store such info? As far as I know, it is BKPF, right?
    And in the actual outgoing payment, can I input different tax code from PO or invoice. If so, which table is used to store such info?
    Thanks a lot in advance.
    Best regards
    Eda

  • If we open a transaction i need to find what are the tables used

    hi gurus
    can anyone suggest me
    if we open a transaction  liek va01
    i need to find what are the tables used
    what are the fields used in that transaction
    i need a list .
    thanks&regards
    kals.

    Hi
    you can find all those details in transaction variant,
    go with SHD0 ( numerical 0) and then enter your transaction code and enter transaction variant name and then select that
    Select the program SAPMV45A and go CHANGE WITH PROCESSING (F6),
    there you can find the list of fields and field names.
    reward points if usful.
    thanks and regards,
    muralidhar

  • What is the table for query name

    Hi All,
    I need an urgent requirement for removing duplicate technical query names from the production. Since there are few issues with the SAP given program I am customizing the SAP Program. Can any one tell me what is the table where the QUERY NAME and it's technical name can be found?
    Thanks,
    Alex.

    hi Alex,
    try RSRREPDIR, RSZCOMPDIR.
    there is one oss note all the tables.
    Table containing Work Book and query relation
    Query Detailes
    oss 792779
    Symptom
    Report ANALYZE_RSZ_TABLES is designed as a check-tool for detecting and solving different types of inconsistencies in the main query definition database tables.
    The program is recommended for BW system administrators.
    Other terms
    Query definition, query, reusable, component, variable, missing elements, missing records, missing UID, INCONSISTENCY, RSZELTDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZCALC, RSZSELECT, RSRREPDIR.
    Reason and Prerequisites
    ATTENTION: the described version of the program is delivered with the following Support Packages:
    SP27 for release BW 3.0B
    SP21 for release BW 3.1C
    SP13 for release BW 3.5
    All versions of this report available in systems before those Support Packages are test versions which can be used only for information purposes.
    Check prerequisites
    Checks are possible only for elements in object version 'A' (active) and 'D' (delivered).
    Checks for query elements in 'D' version are possible only in the systems which are set as content.
    Checks description
    Report performs checks in the tables containing the parts of the definitions of queries and query components: RSRREPDIR, RSZCOMPDIR, RSZCOMPIC, RSZGLOBV, RSZELTDIR and RSZELTXREF.
    1. Table RSRREPDIR
    The table RSRREPDIR is a header table of the generated reports. Consistency of query definition in this table allows to select a query in the Open Dialogs of fronted application and to call report generated for this particular query using transaction RSRT.
    The following errors can be found:
    - queries with missing definition;
    - queries with missing GENUNIID;
    - queries with technical names different than in RSZCOMPDIR;
    - non-queries in the table.
    1.1 Queries with missing definition
    The queries are available only in the table RSRREPDIR and not found in the table RSZELTDIR in the corresponding object version. Such queries (in active version) can be accessed only from RSRT transaction. An attempt to execute such query will return the short dump 'Exception condition INCONSISTENCY'. The error also happens during query generation in RSRT or during mass regeneration of the queries using RSR_GEN_DIRECT_ALL_QUERIES report or application menu of transaction RSRT. The inconsistent queries can not be repaired because of missing query definitions. The recommended solution is to delete those records in order to avoid the possible system dumps.
    1.2 Queries with missing GENUNIID
    Queries having empty GENUNIID field in the table RSRREPDIR. Such queries may be available in the frontend and in RSRT transaction. An attempt to execute such query will return the message'GENUNIID not found'. Situation requires additional investigation at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    1.3 Queries with technical names different than in RSZCOMPDIR
    The check outputs the queries which have different technical names in the RSRREPDIR and RSZCOMPDIR tables. Execution of a query using the technical name given in Query Designer and stored in the table RSZCOMPDIR will return the error message 'GENUNIID not found'. The system tries to find the corresponding GENUNIID for the wrong COMPID which does not exist in the system or which belong to another query. The recommended solution is to correct the wrong COMPID in the table RSRREPDIR via corresponding procedure.
    1.4 Non-queries in the table
    The table RSRREPDIR normally contains only reports. Query elements of other types should not exist in this table and can be deleted. In case, when such records exist in the table an attempt to access them in RSRT returns the error message 'GENUNIID not found'. The recommended solution is to delete those records from the table using the corresponding procedure.
    2. Table RSZCOMPIC
    The table RSZCOMPIC contains an InfoProvider assignment for queries and other reusable query components (STR, RKF and CKF).
    The following errors can be found:
    - local elements in RSZCOMPIC;
    - components with inconsistent definition;
    - components based on non-existing InfoProviders;
    - components based on non-active InfoProviders.
    2.1 Local elements in RZSCOMPIC
    The table RSZCOMPIC contains an InfoProvider assignment for the reusable components. The local elements and also variables have no InfoProvider assignment and should not exist in this table. Those elements can be deleted via corresponding procedure.
    2.2 Components with inconsistent definition
    The reusable queries or query components existing in the table RSZCOMPIC, but not found in the table RSZELTDIR. Those reusable components may return 'Exception condition INCONSISTENCY' dump during accessing/execution. The situation may have different outcomes and has to be investigated at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    2.3 Components based on non-existing InfoProviders
    Queries or query components are assigned to the InfoProviders which do not exist anymore in the system. Queries without InfoProvider are not available in Open Dialogs of frontend applications, but can be executed in RSRT. The execution will return the error message'InfoProvider not found'. The recommended solution is to delete the unnecessary components. Deletion of these queries or query components can be done directly from the list using corresponding procedure similar to RSZDELETE transaction.
    2.4 Components based on non-active InfoProviders
    Queries or query components which are assigned to the InfoProviders which do not exist in the system in the active version. Queries without active InfoProvider are not available in Open Dialogs of frontend applications. In case, an affected query is technically consistent, an attempt to execute it in transaction RSRT will return the message 'Activate the XXX InfoCube / InfoProvider again. Message #BRAIN 056'. Quite often this error is combined with other errors like missing GENUNIID in the RSRREPDIR or other inconsistencies. Each case has to be investigated in order to get the current status of this object. If the affected query is useless, it can be deleted from the system using transaction RSZDELETE.
    The check is available only for the query elements in object version 'A' (active).
    3. Table RSZCOMPDIR
    The table RSZCOMPDIR is the directory table containing the main properties of all reusable components.
    The following errors can be found:
    - duplicated technical names (COMPID);
    - components with inconsistent definition;
    - components without InfoProvider assignment;
    - components with missing OWNER.
    3.1 Duplicated technical names (COMPID)
    The check outputs queries or other reusable query components which have duplicated technical names (COMPID).
    The error does not cause any dumps in ABAP or terminations in Query Designer, but may cause several symptoms in different reporting areas:
    different queries are available in BEX Analyzer and RSRT under the same name;
    wrong query is used as Data Source for Web Template (Web Reporting, Reporting Agent, Broadcasting, MDX);
    replacement of variables does not work... etc.
    The recommended solution is to provide a new technical name for the duplicated component using corresponding procedure.
    ATTENTION: in case when there are only 2 components with the duplicated technical name, only one of those 2 components can be renamed using the corresponding procedure.
    The alternative solution for renaming the duplicated technical names is to use the ABAP report RENAME_DUPLICATE_ELEMENTS.
    3.2 Components with inconsistent definition
    Reusable query components which are not found in the element directory table RSZELTDIR are displayed. This situation may cause the short dump 'Exception condition INCONSISTENCY' during accessing the affected component in Query Designer or execution the affected query in RSRT. Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
    3.3 Components without InfoProvider assignment
    All reusable query component (except variables) should be assigned to a particular InfoProvider. This assignment is located in the table RSZCOMPIC. When the record is not found in this table, the affected component may become not available in Query Designer in the corresponding InfoProvider. In some cases the error message "Component XXX.. (version A) has no InfoCube assignment". Further investigations are required at SAP. Create an OSS note for the SAP component BW-BEX-ET-QDEF.
    3.4 Components with empty ONWER field
    Reusable components which have empty OWNER field in the table RSZCOMPDIR are accessible by users having $USER setting in the authorization object S_RS_COMP1 (users which are authorized to their own queries or query components). This leads to authorization concept violation.
    For error solution the field OWNER in the RSZCOMPDIR should be filled with any value. Execute the corresponding edit mode in order to fill the empty field with user 'SAP'. This will prevent the potential authorization violation for users with $USER setting and will take no effect on the users without this setting.
    4. Table RSZELTXREF
    The table RSZELTXREF contains all links and dependencies between the query elements within a query or query component.
    The following errors can be found:
    - missing elements (INCONSISTENCY dump);
    - not supported relations between query elements;
    - extended RSZELTXREF check.
    4.1 Missing elements
    Missing elements are those query elements which exist as the dependant objects (field TELTUID) in the table RSZELTXREF, but not available in the element directory table RSZELTDIR in corresponding object version. In case, when such elements are used in any query or other query components (STR, CKF or RKF), this may lead to ABAP short dump with 'Exception condition INCONSISTENCY' error message in query run-time or design-time. Other known symptoms of this error is, that structures, calculated key figures or restricted key figures are not available in an Info Provider in Query Designer during design-time.
    The missing elements which are in use in other queries or query components, can not be automatically repaired or deleted without components where those elements are used. In most cases the manual repair operations directly in the DB tables are required. Create an OSS message for SAP component BW-BEX-ET-QDEF for further investigations and creation of a repair plan.
    The missing elements which are not in use in any query or query components, can be deleted from the system via corresponding delete procedure. This deletion will not affect any existing query or query component.
    ATTENTION: if missing element is variable, it can be repaired in some cases automatically using the corresponding repair procedure. See table RSZGLOBV check 5.1. 'Variables with inconsistent definition' for details.
    4.2 Not supported relations between query elements
    Some relations between query elements which are not supported and can cause dumps in ABAP or terminations in Query Designer (for example link STR <--> VAR). Such cases have to be additionally investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
    4.3 Extended RSZELTXREF check
    The extended RSZELTXREF check outputs 2 situations which, in combination with other conditions in the system, may be responsible for slow performance of all operations which involve select from the table RSZELTXREF and resolving the relations between query elements (query load, query generation, expanding of a variable list for corresponding InfoObject, expanding of a list of reusable components in Query Designer,... etc.):
    - records with empty INFOCUBE field
    - records which are not used in any query or query component
    Records with empty INFOCUBE field
    The current algorithm of resolving of relations between the query elements uses an optimization which allows to reduce the amount of data selected from the table RSZELTXREF during such operations are query load, query generate, expand a list of reusable components (STR, CKF, RKF) and so on. All relations between query elements within one reusable component based on one InfoProvider 'N' are also located within the same InfoProvider. The system has to select only records where the INFOCUBE field contain the same InfoProvider 'N' and in addition to this all other records where the INFOCUBE field is empty. This is necessary, because in all BW releases below 3.x the INFOCUBE field was not in the RSZELTXREF table and all components created before 3.x release have this field empty. Selection of records with empty INFOCUBE is required in order to ensure the consistency of processed query.
    When the number of records with empty INFOCUBE is quite large (50.000 - 1 mln records), any simple operation which require resolving of the relations may take a long time, because those records are always being selected, loaded to Query Designer and processed in the design-time.
    Records which are not used in any query or query component
    The program makes a virtual attempt to reconstruct the table RSZELTXREF via resolving the relations between all reusable components existing in the system. All records which are not used in any query or query components are considered as non-used records. Usually these are fragments of old queries or other components which are not deleted due to former errors in the query delete algorithm.
    The current version of the program contain only information about those 2 issues. See the OSS note 823804 for additional information.
    ATTENTION: the extended RSZELTXREF check is recommended when all critical problems with reusable components are resolved and the system clean-up is done (no useless records in the tables, no useless non-executable queries or other affected query component available).
    Starting from SP28 for BW 30B, SP22 for BW 31C and SP14 for BW 3.5 the Extended RSZELTXREF check detects and fixes the following situations:
    records used in existing queries or query components with empty INFOCUBE field;
    records used in existing queries or query components with wrong INFOCUBE assignment;
    records with or without INFOCUBE assignment which are not used in any query or query component.
    For further check details read the OSS note 859086.
    5. Table RSZGLOBV
    The table RSZGLOBV contains the definitions and technical properties of the variables.
    The following errors can be found:
    - variables with inconsistent definition;
    - variables with missing or incorrect properties;
    5.1 Variables with inconsistent definition. Variable not found in RSZELTDIR/RSZCOMPDIR tables.
    The variable existing in the table RSZGLOBV, but not existing in the tables RSZELTDIR or RSZCOMPDIR have inconsistent definition. These situation may return 2 different error messages. When a variable is missing in RSZELTDIR table (or in both together), an attempt to expand a list of variable under a corresponding InfoProvider or a list of text/formula variables will return a message 'Inconsistency in loading...'. All variables which are created for corresponding InfoProvider, text/formula variable are not available. When a variable is missing in the RSZCOMPDIR table only the error message is 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded' in Query Designer.
    In both cases the variables can be repaired via the corresponding procedure provided in the program under the technical name (COMPID) corresponding to the name in VNAM field in the table RSZGLOBV with the text 'REPAIRED BY SAP'.
    As an alternative solution, when the affected variables which are not used in any query or query component can be deleted directly from the RSZGLOBV table. Both solutions will fix the reported symptoms.
    ATTENTION: it is recommended to open a repaired variable in Variable Wizard of Query Designer and to adjust the definition of this variable, when it is necessary.
    ATTENTION: deletion of the affected variables missing in the table RSZCOMPDIR is not possible using transaction RSZDELETE. An attempt to delete such variable will return the error message 'Component not found'.
    5.2 Variables with missing or incorrect properties
    Several errors can be found within this check. The variables of different type have their own sets of properties. Missing or incorrect properties may cause different error message during execution of a query where such variables are in use. In the case of the affect variables with processing type 'replacement' , the replacement may not work because of the problem.
    Each case has to be investigated at SAP. Create an OSS message for SAP component BW-BEX-ET-QDEF.
    6. Table RSZELTDIR
    The table RSZELTDIR is the main directory table containing all query elements available in the system.
    ATTENTION: the RSZELTDIR check may take a long running time depending upon the table size.
    The following errors can be found:
    - local elements not in use;
    - reusable elements not in RSZCOMPDIR table;
    - reusable elements not in RSZCOMPIC table;
    - structure (STR) without structure members;
    - selections or RKF without definition in RSZSELECT table;
    - formulas or CKF without definition in RSZCALC table;
    - variables (VAR) without definition in RSZGLOBV table;
    - queries (REP) without entries in RSRREPDIR table.
    6.1 Local elements not in use
    Local elements (field REUSABLE = false) which are not used as dependant objects in the table RSZELTXREF. These elements are useless and not accessible from Query Designer. Usually these are fragments of the definitions of old queries accumulated in system because of different problems with save/delete procedures which are not accessible by the end users. The recommended solution is to delete those elements using the corresponding delete procedure.
    6.2 Reusable elements not in RSZCOMPDIR table
    Reusable elements (field REUSABLE = true) must have a corresponding entry in the table RSZCOMPDIR which contains the definition and properties of this reusable component. An attempt to load such component in Query Designer may cause the error message 'Missing UID XXXXXX... in RSZCOMPDIR! You may continue to work, but this component is not loaded'. Additional investigations are requires at SAP. Create an OSS message for BW-BEX-ET-QDEF.
    ATTENTION: Deletion of such affected components is also not possible using transaction RSZDELETE. An attempt to delete will return the message 'Component not found'.
    6.3 Reusable elements not in RSZCOMPIC table
    Reusable elements (field REUSABLE = true), except variables (DEFTP = 'VAR'), must have a corresponding entry in the table RSZCOMPIC which contains an InfoProvider assignment for reusable components. When a reusable component has no InfoProvider assignment it may be not available in Query Designer during design-time. Additional investigations are required at SAP. Create an OSS message for BW-BEX-ET-QDEF. In case the affected component is useless, it can be also deleted from the system using transaction RSZDELETE.
    6.4 Structures (STR) without structure members
    Reusable and non-reusable structures (DEFTP = 'STR') should have dependant elements (structure members). When these structure members are not found a query containing this structure returns the error message 'Element structure not correct' during generation or execution in RSRT or BEx analyzer. The program outputs a query technical name where such structures are used or the technical name of an InfoProvider if the affected structure is reusable and not used in any query. In this case it can be accessed from any query created in the same InfoProvider in Query Designer. The solution is to open the affected structure in using the latest available version of Query Designer and to create the required structure members in order to avoid the error message.
    In case, when the affecter structure is local (non-reusable) and is not used in any query, this structure is not accessible by frontend users and can be deleted from the system by corresponding procedure provided in the program.
    6.5 Local selection of RKFs without records in RSZSELECT table
    Local selections and reusable Restricted Key Figure (DEFTP = 'SEL') usually should have the corresponding records in the DB table RSZSELECT. The program outputs all selections found in the system which have no corresponding records in the RSZSELECT table.
    Usually this issue has no impact on the existing queries and produces no error messages. There are 3 possible types of selections within a query:
    Normal selection - this selection represents a characteristic in Row, Columns or Free Characteristics area, Conditions or Exceptions. This situation produces no error messages, but the selection is not taken into account by OLAP.
    Dummy structure member - structure member type selection can be defined using Query Designer. Such structure member produces no selection and can be used only as place holder within a query. This situation produces no error messages during generation/execution of a query containing a structure with those dummy structure members.
    Cell selection - this type of selection is usually used as Cell selection and can be defined using Cell Editor in Query Designer. This situation produces no error messages, but the selection is not taken into account by OLAP.
    If it is necessary, the selection definition can adjusted using the latest available version of Query Designer. The affected local selections can be accessed from the queries presented in the WHERE-USED (INFOCUBE/QUERY). The Restricted Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
    In case, when a local selection is not used in any query or query components the recommended solution is to delete this selection using the corresponding delete procedure.
    6.6 Local formulas of CKFs without records in RSZCALC table
    Local formulas (DEFTP = 'FML') or Calculated Key Figures (DEFTP = 'CKF') should contain definition of the calculations in the table RSZCALC. When such definition is not found in the table RSZCALC the queries or query components which include those affected objects can not be generated or executed by OLAP. An attempt to generate such query returns the error message 'The (sub) formula XXX... is not available'.
    The definitions of the affected formulas or Calculated Key Figures can be adjusted using the latest available version of Query Designer. The adjustment of a local formula is possible from the corresponding query listed presented in the program. The Calculated Key Figures are available in Query Designer from any query created on the corresponding InfoProvider.
    In case, when a local formula is not used in any query or query components the recommended solution is to delete this formula using the corresponding delete procedure.
    6.7 Variables without records in RSZGLOBV table
    Variables (DEFTP = 'VAR') should exist in the table RSZGLOBV. The table RSZGLOBV contains all processing properties and definition of the variables. Query where such variables are used can not be executed without problems.
    The repair procedure is not possible, because of missing definition. In case, when such variable is not used in any query, the recommended solution is to delete it from the system in order to avoid potential problems. If the affected variable is already used in other queries or query components, create an OSS message for SAP component BW-BEX-ET-QDEF. Further investigations and possible repair plan have to be created at SAP.
    6.8 Queries without records in RSRREPDIR table
    Queries (DEFTP = 'REP') should exist in the table RSRREPDIR. The table RSRREPDIR is a header table of generated reports and also a part of the database view V_REP_JOIN which provides data for the BEx Open/Save Dialogs.
    A query which does not exist in the table RSRREPDIR is not accessible via RSRT transaction (error message 'GENUNIID not found') and not displayed in the Open/Save Dialogs of fronted applications.
    The recommended solution is to delete such queries using the corresponding procedure provided in the program and similar to RSZDELETE.
    In some cases the repair procedure is also possible. The success of the repair procedure depends upon the consistency of the affected query, the existence of a valid InfoProvider for this query and some other factors. For repair attempt create an OSS message for the SAP component BW-BEX-ET-QDEF.
    hope this helps.

  • What is the table name means to me.

    Hi All,
    Here is the partial technical information for the field found in the SAP screen/GUI.
    Table Name: /SAPSLL/PRODUCT_LLNS_DYNP_S
    Field Name: CCNGN
    Data element: /SAPSLL/CCNGN.
    Here is my questions.
    ================
    1. What is the table name means to me.
        Is it a table name in SAP  repository or the table found in the  backend database  ? 
        Let us say my backend database is oracle.  
       The table name  in the  repository  and the table name in the backend  oracle database  is the same ?
    2.     What is the "Field Name:" means to me ?
    3.  What is the "Data element:" means here. 
    Any help or pointers are appreciated.
    thanks
    siva

    Check with this
    Go to SE84>ABAP Dictionary->Fields->Table fields/structure fields (double click )->Give the description of ur field in ur case (Schedule line date) and Press F8.
    It will show where this field is available in the TABLESStructures.

  • What is the table name for getting Last Receipt  & issue date of material?

    Hi Friends,
    What is the table name for getting Last Receipt  & issue date of material?
    *Case 1:*
    Here, I am running report in May 2008. But, if there is no goods receipt for the respective material since last 13th March 2007.
    Then in this case Last goods receipt date should be 13th March 2007.
    Please guide me.
    Regards
    Siva

    I checked MSEG table. But, I didn't find any field for date.
    Can you tell me field name.
    Regards
    Siva

  • What are the tables  related to Goods receipt details

    Hi,
    Please tell me the GR related data base tables.
    What are the tables  related to Goods receipt details
    Regards,
    Sunil Kumar.T
    Edited by: sunil kumar on Apr 28, 2008 8:49 AM

    Hi,
    If you want to know tables which are related to transaction.
    Use recording through SHDB tcode.
    go to shdb tcode
    after enter name of your zname.
    after for which transaction you are doing recording enter that tcode here migo.
    after press start recording.
    then enter data into fields after at last save and back.
    then it goew to control recording session screen
    after press program for create.
    then enter attributes ,select source code after save your code.
    Using this tables and which fieldsa you are using for perticular requirement.
    this is an easy procedure to know tables and fields.
    or
    USE ST05 tcode by entering single filed into application.
    These two approaches are usefull but go to first one if you knew which data you have to entered.
    Otherwise go to st05.
    *Reward points
    for goods receipt tcode by entering data

  • What are the tables rfpdo and rfpdo1?

    what are the tables rfpdo and rfpdo1?
    wht are these fields?
    rfpdo-allgstid
    rfpdo1-allgfael

    Look at <a href="http://help.sap.com/saphelp_46c/helpdata/en/40/5f3275e24bd111950d0060b03c6b76/frameset.htm">Data Collection Programs for FI-GL, FI-LC, CO-OM and CO-PA</a>
    <i>Data Collection Programs for FI-GL, FI-LC, CO-OM and CO-PA
    Description
    1. Data retrieval from the FI general ledger With the report RFBILA00, data from the balance sheet and the P+L statement can be transferred to SAP-EIS. Detailed information on this is stored with the corresponding parameter of the report RFBILA00 (RFPDO-BILA_EIS).
    2. The interface to FI-LC has been revised and the sender structure enhanced. AS sender field names were changed, it is necessary to adapt transfer rules created in release 2.2. Detailed information on this interface is contained in the online help for transfer program RGCEISS1.
    3. CO-PA data can be transferred into SAP-EIS using a basic report. More information on this can be found in the Implementation Guide of SAP-EIS.
    4. Data from CO-OM can be transferred to SAP-EIS using Report Writer reports. Since reports must fulfill certain conditions for the data transfer, standard reports in the report group '1EI' are delivered for CO-CCA. From the same group, you can define reports which transfer data from CO-OPA to SAP-EIS. You will find more information on this in the implementation guide.</i>
    Regards

  • What are the Table Names

    Hi All,
    What are the table names which Stores the Shopping Cart Data i.e Cart No., created by, approved by, line item details.
    What are the table names which Stores the Shopping Cart approver name.
    What are the table names which Stores the Confirmation data i.e document no. , name of the approver of the confirmation, line item details.
    Please also mention the common used table names in SRM EBP.
    Thanks in advance.
    Regards
    Sridhar

    Hi Sridhar,
    pl. explore the golden txn. BBP_PD in SRM.
    Just Run the txn. choose yr object type i.e. for SC choose BUS2121
    for confn. pl. chk out(i don't have sys)
    put any sample SC or confn no
    execute
    it will give you that BUS object details
    Doubleclick to open all details
    on the relevant field just double click to get the respective table name
    e.g. SC data click on SC no.
    For ready ref following are some tables
    PO no in the tables BBP_PDBEH/BBP_PDBEI from the SC guid
    Tables updated related to Shopping Cart               
    Srno     Tables     Description     H/I
    1     CRMD_ORDERADM_H     Header Table of the Shopping Cart     H
    2     BBP_PDHGP     Business Transaction Purchasing Informatio     H
    3     BBP_PDHSB     Bid Invitation     H
    4     BBP_PDBEH     Backend Specific Header Data     
    6     BBP_PDPSET     Further Procurement Information     
    7     BBP_PDHSC     Header Extension for Customer Fields     H
    8     BBP_PDHSS     Hdr Extension for SAP Internal Enhancement     H
    9     CRMD_ORDERADM_I     Business Transaction Item     I
    10      BBP_PDIGP     Business transaction item-Purchasing infor     I
    11     BBP_PDBEI     Backend Specific Item Data     I
    12     BBP_PDISB     Bid Invitation/Bid-Specific Item Data     I
    13     BBP_PDISC     Item Extension for Customer Fields     I
    14     BBP_PDISS     Item Ext. for SAP Internal Enhancements (IBUs and so on)     I
    15     CRM_JEST     Individual Object Status     
    16     CRMD_PARTNER     Partners     
    17     BBP_PDBGP     Partner Extension Gen. Purchasing Data     
    18     BUT000     BP: General data I     
    19     ADDR3_DATA     Address data     
    20     BBP_PDORG     Purchasing Organizational Unit     
    21     BAPIEKKOL     BAPI -s inofrmation     H/I
    22     BAPIEKPO_ECI     BAPI -s inofrmation     H/I
    23     BBP_BAPIEKKN     BAPI -s inofrmation     H/I
    24     BAPIEBAN     BAPI -s inofrmation     H/I
    25     BAPIEBKN     BAPI -s inofrmation     
    26     BBP_PDACC     Account Assignment     
    27     BBP_PDATT     Document Attachment     
         Additional Tables          
    28     BBP_CATEGORY_FAV     User-Specific Favorites for Product Categories     
    29     STXH     STXD SAPscript text file header     
    30     BBP_PDVIEW_IAP     Item Data: General Purchasing and Purchasing Set     
    31     BBPC_PARTNERFUNC     Definition of Partner Functions
    32     HRP1001     Infotype 1001 DB Table
    33     TSAD3T     Titles (Texts) (Business Address Services)
    34     comm_applcatgrpr     Application Area of a Hierarchy
    35     BBP_FUNCTION_MAP     Function Map for BAPI Dispatcher
    36     SWOTIP     Index Parent Object Types
    37     HRSOBJECT     Index for Standard Objects
    38     usr02     Logon Data (Kernel-Side Use)
    39     usrefus     Reference user for internet applications
    40     spers_obj     Personalization object repository
    41     hrv1222a     View of Attributes
    42     bbpc_partnfunc_t     Description of Partner Functions
    43     CRM_JSTO      Status Object Information
    44     crmc_but_call_fu     Determining FMs for Data Exchange BP
    45     bbpc_actionmap     Assign Method Actions
    46     but000     BP: General data I
    Pl. note I have not checked these all tables myself, you can explore.
    BR
    Dinesh
    <b>Reward if helps</b>

Maybe you are looking for

  • Just got a MacBook.

    My old portable was a 12'' PowerBookG4. I was running Leopard on it, however I did notice that a couple of my programs did not work and as I recall my wireless router did work as well. There are little problems here and there. This MacBook that I hav

  • Work process in complete status

    Hi Gurus , wps are going to complete status and restart after error is set to no , tried to retart wps again same problem they going again to complete status . could some guide on this. thanks va

  • Federated Search for Documentum

    Hi. Has anybody implemented a federated search for Documentum? I think Documentum uses Verity internally for full text indexing, but Verity is tightly integrated with Documentum's own metadata search - does Documentum expose the search functionality

  • Can't find iTunes backup.

    I was removing my backup from my iPod Touch 4 and I had backed it up. So I reset it and then when I went to restore the backup it re-backed it up before I could catch it and now I can't locate my original backup. So I downloaded the free trial of Won

  • I have working Netgear network. Want to add new Time Capsule and run 2nd network for new apple TV and Imac, and keep the netgear network for my PC and Canon printer.

    I have working Netgear N600 dual band router network. The existing network has an XP netbook PC, canon printer, 2 Iphones, Epson Air printer, an Ipad, 3 roku boxes, backup drive. Just bought a new Apple TV box, and time capsule 2T.  I have an IMac on