Table for Documents Name List

Hello Everyone!
I have a simple question:
Does exists any table in B1 who gives  the document name according to its Object Type?
Thx in advance,
Juan Jimenez

Hi,
You can check this document regarding the issue reported by you:
[Transaction Type Abbreviations|http://help.sap.com/saphelp_sbo88/helpdata/en/45/114a3129fc4805e10000000a1553f6/frameset.htm]
Kind Regards,
Jitin
SAP Business One Forum Team

Similar Messages

  • What are the tables for documents in PP Orders

    Hi all,
    What are the tables for Document Items (type D) in PP orders ?
    Regards,
    Magda

    Welcome to SCN, please refer to the rules of engagement, link at the top of every forum, please search before asking basic questions.
    Thread locked.
    Thomas

  • Tables for Documents&doc. type assigned to Equipment master

    Hi
    I need a table for Documents&d oc. type assigned to Equipment master .I have tried in ITOB, EQUI, DRAW. i could not find this
    Thanks
    Seenu

    hi
    yes you can use object key, it  is the one which relates with the equipment ( object key <b>EQUI</b>)
    regards
    thyagarajan

  • Translation table for Program name/screen number for ECC 6.0

    Hello Experts,
    Do you know if there is a translation table and/or document that would list the Program Name / Screen Number for the transactions in SAP 5.0 and the equivalent Program Name / Screen Number for those same transactions in SAP 6.0?
    The reason that I ask is that we our encountering errors within the TxShuttle macros we are testing that are telling us that the current screen name listed in the macro in no longer valid in the 6.0 environment.
    Regards,
    Atul

    I thnk we dont have any such program .Try searching for a SAP Note if its a standard program.
    Can u tell me the program name and screen number which is not available in ur system.

  • Table for Document assigned to WBS

    In which table Document and WBS assignment is captured?
    Thx

    Hello,
    PRPS is separate table for WBS element. If you want to see it in DMS then check in object link field name in DRAW.
    Hope you are aware about the standard objects in SAP and their respective tables.
    Regards,
    Ravindra

  • Table for document type Number Range interval

    Hi,
    I want to know the number range interval for document type in the production system but I do not have authorisation for SPRO in the prd system.
    Kindly let me know the table name to check this number range interval for the document type.
    Table T003 stores only the number range and not the interval.
    Thanks
    Suresh

    Hi,
    The table which has document types is T003 but the number ranges are stored in a Structure IRDP. The number ranges are maintained directly in the production system.
    regards,
    radhika
    Edited by: kolipara radhika on Aug 25, 2008 6:01 AM

  • Table for Stock Requirement List related information

    Dear Sir,
    We have make-to-order scenario , on receiving the Order from Customer  we first create a Sale-Order for the Ordered Item . Subsequently in MD04 , we find a requirement getting reflected  for the Customer Order .
    For example say the Sale-Order number is S-101 and the Line Item is 10 for the FERT material say FERT-101 having the Order quantity as 1 number .  In MD04 , we find a requirement getting reflected with the following information :
    MRP Element  --> CustOrd
    MRP element data --> S-101 / 00010 / 0001
    Recd/Reqd Qty  -->  1-
    Available Qty  --> 1-
    We need to write a Z program for getting the list of  the requirements against the Customer Order (as shown in MD04) .
    Kindly guide us as which Tables we need to refer for getting the above information pl .
    We assure to award full points for the suggested solution .
    Rgds
    B Mittal

    Hi,
    Pls use below function module, same as you will get Stock Requirement List related information
    MD_STOCK_REQUIREMENTS_LIST_API
    For test, goto SE37 and test it
    Regards,
    Sankaran

  • Tables for Qurey names and cube

    hi,
    I want to know the list cubes against each query.
    can any one tell me what are tables for the folllowing
    1) to get list generic queries avalible .?
    2) cube against each of that query?
    3) Data source against each cube?
    4) generic web templates against each query?
    regards
    Laxman

    Hi Olin,
    RSZELTDIR: filter by: OBJVERS = 'A', DEFTP: REP - query, CKF - Calculated key figureReporting component elements, query, variable, structure, formula, etc
    RSZELTTXT: Similar to RSZELTDIR.
    Texts of reporting component elementsTo get a list of query elements built on that cube:RSZELTXREF:
    filter by: OBJVERS = 'A', INFOCUBE= [cubename]
    To get all queries of a cube:RSRREPDIR: filter by: OBJVERS = 'A', INFOCUBE= [cubename]To get query change status (version, last changed by, owner) of a cube:RSZCOMPDIR: OBJVERS = 'A' .
    Web templates      
    RSZWOBJ - Storage of the Web Objects
    RSZWOBJTXT - Texts for Templates/Items/Views
    RSZWOBJXREF - Structure of the BW Objects in a Template
    RSZWTEMPLATE - Header Table for BW HTML Templates
    Regards
    KP

  • Table for documents

    hi experts
    iam doing report, i want to no in which table all sap documents are stored( iam talking about all modules not for one module))

    get specific.
    SAP has hundred of different documents and at least as much tables for them.

  • Joining vbak to cdhdr table for document changes

    Hi Expert
    I am hanging for a week in this project please need some advice
    I want to join vbak table with cdhdr and select
    vbak.vkbur (plant) and want to show that vkbur in the internal table of it_cdhdr
    so as to select only those plant belong to vkbur so how can I join base on the below coding................
    REPORT ZCHGDOC
    NO STANDARD PAGE HEADING LINE-SIZE 120.
    WRITE: sy-title, 40 'Page', sy-pagno.
    ULINE.
    TABLES: CDHDR,
             CDPOS,
             t001w,
             "VKBUR,
             "VBELN,
             VBAK,
             VBAP.
    SELECTION-SCREEN BEGIN OF BLOCK DOCUMENT WITH FRAME TITLE TEXT-701.
    SELECTION-SCREEN END OF BLOCK DOCUMENT.
    SELECT-OPTIONS:
                     V1 FOR VBAK-VKBUR,
                     S_WERKS for T001W-werks,
                     objectid for  cdhdr-objectid,
                     udate for cdhdr-udate.
    PARAMETER: USERNAME LIKE CDHDR-USERNAME.
    DATA: BEGIN OF IT_VBAP OCCURS 0,
             OBJECTCLAS LIKE CDHDR-OBJECTCLAS,
             OBJECTID LIKE CDHDR-OBJECTID,
             VBELN LIKE VBAP-VBELN,
              END OF IT_VBAP.
    DATA: BEGIN OF IT_CDHDR OCCURS 0,
             OBJECTCLAS LIKE CDHDR-OBJECTCLAS,
             OBJECTID LIKE CDHDR-OBJECTID,
             CHANGENR LIKE CDHDR-CHANGENR,
             USERNAME LIKE CDHDR-USERNAME,
             UDATE LIKE CDHDR-UDATE,
             UTIME LIKE CDHDR-UTIME,
             FNAME LIKE CDPOS-FNAME,
             TABNAME LIKE CDPOS-TABNAME,
             TABKEY LIKE CDPOS-TABKEY,
             VALUE_NEW LIKE CDPOS-VALUE_NEW,
             VALUE_OLD LIKE CDPOS-VALUE_OLD,
    END OF IT_CDHDR.
    DATA: WA LIKE LINE OF IT_CDHDR.
    DATA: WA LIKE LINE OF IT_CDPOS.
    DATA: BEGIN OF IT_CDPOS OCCURS 0,
             OBJECTCLAS LIKE CDHDR-OBJECTCLAS,
             OBJECTID LIKE CDHDR-OBJECTID,
             CHANGENR LIKE CDHDR-CHANGENR,
             TABNAME LIKE CDPOS-TABNAME,
             TABKEY LIKE CDPOS-TABKEY,
             FNAME LIKE CDPOS-FNAME,
             VALUE_NEW LIKE CDPOS-VALUE_NEW,
             VALUE_OLD LIKE CDPOS-VALUE_OLD,
    END OF IT_CDPOS.
    Move-corresponding it_cdhdr to wa.
    Move-corresponding it_cdpos to wa.
    SELECT OBJECTCLAS
            OBJECTID
            CHANGENR
            USERNAME
            UDATE
            UTIME FROM CDHDR
            INTO CORRESPONDING FIELDS OF TABLE IT_CDHDR
    WHERE OBJECTCLAS = 'VERKBELEG' or
          objectclas = 'BETRIEB'
          ORDER BY UDATE.
    WHERE OBJECTCLAS = 'VERKBELEG'
    OR OBJECTCLAS = 'BETRIEB' ORDER BY UDATE.
    Filter data based upon Plant selection criteria.
    IF NOT S_WERKS[] IS INITIAL.
    DELETE IT_CDHDR WHERE NOT OBJECTID IN S_WERKS.
    ENDIF.
    IF IT_CDHDR[] IS NOT INITIAL.
       SELECT OBJECTCLAS
              OBJECTID
              CHANGENR
              VALUE_NEW
              VALUE_OLD
              FNAME
              TABNAME
              TABKEY
              FROM CDPOS
              INTO CORRESPONDING FIELDS OF TABLE IT_CDPOS
              FOR ALL ENTRIES IN IT_CDHDR
              WHERE
              OBJECTCLAS = IT_CDHDR-OBJECTCLAS
              AND OBJECTID = IT_CDHDR-OBJECTID
              AND CHANGENR = IT_CDHDR-CHANGENR.
              "or tabname = 'VBAP'.
       SORT IT_CDPOS BY OBJECTCLAS OBJECTID CHANGENR.
    ENDIF.
    Add tables CDPOS DATA TO CDHDR.
    DATA: INDEX TYPE i.
    LOOP AT IT_CDHDR.
       INDEX = SY-TABIX.
       READ TABLE IT_CDPOS WITH KEY OBJECTCLAS = IT_CDHDR-OBJECTCLAS
       OBJECTID = IT_CDHDR-OBJECTID
       CHANGENR = IT_CDHDR-CHANGENR BINARY SEARCH.
       IF SY-SUBRC = 0.
         IT_CDHDR-VALUE_NEW = IT_CDPOS-VALUE_NEW.
         IT_CDHDR-VALUE_OLD = IT_CDPOS-VALUE_OLD.
         MODIFY IT_CDHDR INDEX index TRANSPORTING value_new value_old.
       ENDIF.
       WRITE:/ SY-DATUM,SY-UZEIT,
              50 'DOCUMENT CHANGE REPORT',
             80 'Page', SY-PAGNO,
    "  WRITE: / SY-REPID
              50 'DETAIL REPORT BY PLANT '.
       SKIP.
       ULINE.
    *& T O P - O F - P A G E *
    WRITE:/ 'UDATE:' ,SY-DATUM.
    FORMAT COLOR 4 INTENSIFIED on.
    Write: /35                           ' DOCUMENT CHANGES REPORT '.
       WRITE: /5 'DOCUMENT-NO'.
    20 'TABNAME', 30 'TEXT_CASE', 50 'FNAME'.
       WRITE: /5 'DATE',  20 'FNAME', 45 'CHANGE-NO',65 'OLD-VALUE',80 'NEW-VALUE',95 'USER-NAME'.
       ULINE.
       LOOP AT IT_CDHDR INTO WA.
       on change of wa-objectid.
       Write: / wa-objectid UNDER'DOCUMENT-NO' ."color col_key.
       ENDON.
    ULINE.
         " CDPOS-tabname UNDER'TABNAME', CDPOS-TEXT_CASE UNDER'TEXT_CASE',CDPOS-fname UNDER'FNAME'. "color col_key ,
         write: / wa-udate dd/mm/yyyy under'DATE' NO-GAP,wa-fname under'FNAME' NO-GAP,wa-changenr under 'CHANGE-NO',
         wa-value_old under'OLD-VALUE' LEFT-JUSTIFIED NO-GAP,
         wa-value_new under'NEW-VALUE' LEFT-JUSTIFIED NO-GAP ,wa-username under'USER-NAME' NO-GAP.
    ENDON.
    Move-corresponding it_cdhdr to wa.
    *Write: / wa-objectid UNDER'DOCUMENT-NO' "color col_key.
    *" CDPOS-tabname UNDER'TABNAME', CDPOS-TEXT_CASE UNDER'TEXT_CASE',CDPOS-fname UNDER'FNAME'. "color col_key ,
    *write: / wa-udate dd/mm/yyyy under'DATE' NO-GAP,wa-utime under'TIME' NO-GAP,wa-changenr under 'CHANGE-NO',
    ltrim(wa-value_old) under'OLD-VALUE' NO-GAP,
    *wa-value_new under'NEW-VALUE' NO-GAP ,wa-username under'USER-NAME' NO-GAP.
       ENDLOOP.
    ENDLOOP.

    Hai everybody.
    I am new to this forum. i got a job in abap recently. The below is my requirement.I want solution for this one. Anybody plz help me.
    The change logs were captured in DBTABLOG for table ZWPRFRUND (in transaction ZWPG).
    The only report which is currently used to get the change logs is RSVTPROT
    Now my requirement is,
    we need to display the change logs in the form of ALV.
    We should divert the changes to CDHDR table instead of DBTABLOG, then we can use the RSSCD100 to display change logs.
    The Important items for the change LOG needed in case of changes to table in “ZWPG” are,DATE ,TIME,USER,FIRST NAME,FILED NAME,OLD VALUE,NEW VALUE
    The above fields need to be displayed in the grid. In the above list “FIELD NAME” denotes any field of the table in the transaction in “ZWPG”
    Thanks & Regards,
    Sujatha.T.

  • 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.

  • Script for document name labels

    How hard would this be?
    A script that would type the file name into the document. I searched for similar threads but no luck. Here are the details...
    1. If the document was named TEST.pdf the script would type TEST in the document.
    2. The font color, size, and type would be Black, Arial Bold,  0.4 in.
    3. The font would be converted to outlines.
    4. A rectangle 0.05" larger than text would be placed around the text.
    5. The rectangle would have no fill and a 100% magenta spot color named "CC" stroke.
    6. The rectangle stroke would be moved to the CC layer (pre-existing layer).
    7. The text "TEST" would be moved to the Artwork layer  (pre-existing layer).
    Thanks for any input or help.
    Anton

    Anton, this should be pretty close for a guide… I don't know what your exact font name would be… so this uses my closest match. Also you don't mention text positioning on the artboard/doc… The stroke is default 1pt as is. The height of the outlined text would be dependent on your font and you may have to tinker with the size where shown…
    #target illustrator
    function docNameToText() {
         if (app.documents.length = 0) {
              return;
         } else {
              var docRef = app.activeDocument;
              var docName = docRef.name;
              var text = docName.replace(/\.(ai|eps|pdf)$/i,'');
              var arialFont = app.textFonts.getByName('ArialMT-Bold'); // Add font name here…
              var nameText = docRef.textFrames.add();
              nameText.contents = text;
              var nameChar = nameText.lines[0].characters;
              for (var i = 0; i < nameChar.length; i++) {
                   nameChar[i].characterAttributes.textFont = arialFont;
                   nameChar[i].characterAttributes.size = 40; // Adjust font size here…
              var textGroup = nameText.createOutline();
              textGroup.position = [36,-36]; // Half Inch down/across from top/left
              var groupBounds = textGroup.visibleBounds;
              var ccLayer = docRef.layers.getByName('CC');
              textGroup.move(ccLayer, ElementPlacement.INSIDE);
              var artLayer = docRef.layers.getByName('Artwork');
              // This can't be the right way to do this now can it?
              var boxTop = groupBounds[1] + 4;
              var boxLeft = groupBounds[0] - 4;
              var boxWidth = (groupBounds[2] - groupBounds[0]) + 8;
              var boxHeight = (-groupBounds[3] - -groupBounds[1]) + 8;
              var spotBox = docRef.pathItems.rectangle(boxTop,boxLeft,boxWidth,boxHeight);
              spotBox.filled = false;
              spotBox.stroked = true;
              //spotBox.strokeWidth = 1; // Default is 1pt
              var ccSpot = docRef.swatches.getByName('CC');
              spotBox.strokeColor = ccSpot.color;
              textGroup.move(artLayer, ElementPlacement.INSIDE);
    docNameToText();

  • PS Tables for Documents, Acitivity Relationships

    Hi Frinds
    We are looking for proper talbes for the following. Can any one help us which are tables to be referred for
    <b>1.   Documents (this icon we can see in overview screen of WBS elements)
    2.  Network Relationship Activity Relationships (Besides - AFAB)
    3. Hirarchy levels of WBS elements (besdes PRHI)</b>- "Hirerchy Graphic -Icon" which enalbe users to view hierarchy levels of elements.
    4.  "system status" and "user status"
    would appreciate help in this front and suitably rewarded with points for solution.
    Look forward to hear and thanks in advance...
    Thanks
    Sudhakar
    Message was edited by: Sudhakar Pappu Rao

    Hi Pranav
    Thanks for yr information. we can select the object WBS, and shall be able to view PS texts in overview and create PS Texts.
    My requirement rather, question is, can we attach any documents without having DMS. ie., can we assign any of the Windows document which are available in hard disc?
    please thorough some light on this and thanks in advance and belated happy diwali wishes to you.
    Thanks
    Sudhakar

  • Table for customer name

    Dear all
    pl give me the table & field where the customer name is saved
    Regards
    Kiran

    Customer Master Tables:
    Description - Table
    General Data in Customer Master - KNA1
    Customer Master (Company Code) - KNB1
    Assign customer-credit card - VCKUN
    Customer Master Contact Partner - MASSKNVK
    Customer master record sales request form - MASSKNVD
    Customer Master Sales Data - KNVV
    Customer Master Partner Functions - KNVP
    Customer Master Licenses - KNVL
    Customer Master Tax Indicator - KNVI
    Customer Master Unloading Points - KNVA
    Customer master credit management: Control area data - KNKK
    Customer master credit management: Central data - KNKA
    Customer Master: Legal Control - Sanctioned Party List - KNEX
    Customer Master (Bank Details) - KNBK
    Customer master (dunning data) - KNB5
    Customer master (VAT registration numbers general section) - KNAS
    Regards,
    Rajesh Banka

  • Table for Document flow

    Hi,
    I have a Sales Order. For this Sales Order i Created a Puchase Order.I made a Goods Reciept and an Account Document is created. Can any one tell the table where i can see the Document flow for this Order? I tried VBFA...but i can see only Purchase Order against the Sales Order.Thanks in Advance.
    Challa.

    VBFA is document flow for SD.
    To find receipt for purchase order, look at EKBE with key purchase order Nr and event type VGABE = '1' Goods receipt
    Then to find accounting document, you need to look to BKPF header table with keys AWTYP Reference procedure 'MKPF' and AWKEY Object key (Nr + year)
    Regards

Maybe you are looking for

  • How can I detect when a hibernate mode accures during my program?

    hello everyone I 'm trying to find some way to let my program know the moment when the user tries to get the computer into hibernate mode ? is this possible in any way under java?

  • Problems with Apache Commons Validator

    Hello there, I got a quiet big problem using the a.m. validation framework. When defining a validation rule for a property like this: <formset> <form name="testForm"> <field property="firstName" depends="isEmail"> <arg0 key="testForm.firstname"/> </f

  • BPM - BPE_ADAPTER : Unknown message Type

    Hello Experts, I am developing a simple BPM scenario with just one receive and one send step. I have configured bothl the BPM steps along with the container elements and verified the objects in IR and ID. In SXI_CACHE the status of teh Integartion Pr

  • How do you copy photo's from elements to an i-padmini

    How do you copy photo's from elements 10 to an i-padmini

  • CMT with non-weblogic JMS in a session bean

    I am writing a session bean which sends a JMS message using a non-weblogic JMS provider. This bean is marked for CMT and I want the JMS send to participate in this CMT as well. My understanding is that I should be able to do this by defining a <resou