What is the prupose abap query? configuaration process?

what is the prupose abap query? configuaration process?

Hi Balaji,
Here is the details of ABAP Query
ABAP Query
An ABAP Workbench tool that enables users without knowledge of the ABAP programming language to define and execute their own reports.
In ABAP Query, you enter texts and select fields and options to determine the structure of the reports. Fields are selected from functional areas and can be assigned a sequence by numbering.
ABAP Query offers the following types of reports:
Basic lists
Statistics
Ranked lists
I hope it will clear for you,
Regards,
Murali.

Similar Messages

What is the difference between query & query view in BI 7.0 ?

Hi Experts,
What is the difference between query & query view in BI 7.0 ?
Can anyone suggest me on this.
Thanks & Regards
Sameer Khan

Hi Sameer,
Pls find the below URL for Query&Query View
http://help.sap.com/saphelp_nw04/helpdata/EN/26/6de53cce129749893b008c627ede07/content.htm
http://help.sap.com/saphelp_erp2004/helpdata/en/36/18788b6bca5d02e10000009b38f983/content.htm
Thanks,
John

What is the Current ABAP Kernel version for SAP ERP 6 (ECC6)..?

What is the Current ABAP Kernel version for SAP ERP 6 (ECC6)..?

Hi,
Login to http://service.sap.com/swdc using your S user-id
Serach for kernel
Check for your relevent kernel patch (unicode/non-unicode , NW release etc.)
Regards,
Rajneesh

What is the command to look at process at os level ?

what is the command to look at process at os level ?

Do you want Dispatcher processes or else all sap related processes?
Any ways:
Try with this:
ps -ef/grep XXXX/grep DEV..here XXXX..give process name
If you want for all then just go with ps -ef/grep DEV
If you want to have cpu utilization then just go with
TOPAS cmd ....
Use dpmon for a single dispatcher.
Satish

What is the default time settings in Process chains

Hi,
What is the default time settings in Process chains.
How to set time settings for daily,weekly,monthly loads in Process chains.
What is the time settings that we have to take care when creating meta chains.
Thanks,
Madhu.

Hi Madhu,
The Time settings for any PC is done in the start variant of the PC. There is nothing like default time setting. These settings are totally depended on the requirement and system performance. It is a general rule of thumb to load the data during a time when the user activity is minimum as the loading process is going to occupy many dialog as well as background WPs. So, if you schedule them at a time when there are many users on the system, they might feel that the system is slow. Hence, you decide as to what is the best time for scheduling a PC. The same applies to meta chain also. In case of meta chains, you make sure the dependencies of the local chains is also handled. Hope this helps.
Thanks and Regards
Subray Hegde

What are the phases in requirements gathering process?

Hello
What are the phases in requirements gathering process?
Lets say we start from meeting with business , several workshops , etc
Is business Blueprint the final phase of this process?
Whats the difference between Business Blueprint and functional spec?
Thanks

Hi ,
Blueprint is the starting phase of the project. First there would be requirement gathering according to the client requirements. Then according to these requirements functional specs would be made. Based on these functional specs technical spec would me made and once approved from the client development would start.
This is just an overview. Hope it helps.
Regards,
Rahul.

What is the purpose of using return process sales doc type?

what is the purpose of using return process sales doc type?

hi,
There is the standard process
1)Order type( RE) VA01
2)Delivery( LR)Vl01n with reference to return order
i)if the movement is 651then system will not generate accounting document upon doing Post goods Receipt ,the stock will be in the return location
then you use movement type 453 to get the stock in UN restricted
ii)if the movement type 653 the system generates accounting document and stock posts in unrestricted use
3)With reference to Delivery raise Credit memo (RE) with transaction VF01
CHAN

What is the purpose of using credit process sales doc type?

what is the purpose of using credit process sales doc type?

hi,
A transaction that reduces Amounts Receivable from a customer is a credit memo.
Credit memo request is a sales document used in complaints processing to request a credit memo for a customer. If the price calculated for the customer is too high, for example, because the wrong scale prices were used or a discount was forgotten, you can create a credit memo request. The credit memo request is blocked for further processing so that it can be checked. If the request is approved, you can remove the block. The system uses the credit memo request to create a credit memo.
CHAN

What is the purpose of using debit process sales doc type?

what is the purpose of using debit process sales doc type?

hi,
A debit memo is a transaction that reduces Amounts Payable to a vendor because; you send damaged goods back to your vendor.
Debit memo request is a sales document used in complaints processing to request a debit memo for a customer. If the prices calculated for the customer were too low, for example, calculated with the wrong scaled prices, you can create a debit memo request. The debit memo request can be blocked so that it can be checked. When it has been approved, you can remove the block. It is like a standard order. The system uses the debit memo request to create a debit memo.
CHAN

What is the programming (ABAP) difference between Unicode and non Unicode?

What is the programming(ABAP) difference between Unicode and non Unicode?
Edited by: NIV on Apr 12, 2010 1:29 PM

Hi
The difference between programming in Unicode or not Unicode is that you should consider some adjustments to make on the Program "Z" to comply with the judgments Unicode Standard.
In the past, developments in SAP using multiple systems to encode the characters of different alphabets. For example: ASCII, EBCDI, or double-byte code pages.
These coding systems mostly use 1 byte per character, which can encode up to 256 characters. However, other alphabets such as Japanese or Chinese use a larger number of characters in their alphabets. That's why the system using double-byte code page, which uses 2 bytes per character.
In order to unify the different alphabets, it was decided to implement a single coding system that uses 2 bytes per character regardless of what language is concerned. That system is called Unicode.
Unicode is also the official way to implement ISO/IEC 10646 and is supported in many operating systems and all modern browsers.
The way of verifying whether a program was adjusted or not, is through the execution of the UCCHECK transaction. Additionally, you can check by controlling syntax (making sure that this asset verification check Unicode).
The main decisions to adjust / replace are (examples):
ASSIGN H-SY-INDEX TEXT TO ASSIGN <F1> by
H-SY-INDEX TEXT (*) TO <F1>.
DATA INIT (50) VALUE '/'. by
DATA INIT (1) VALUE '/'.
DESCRIBE FIELD text LENGTH lengh2 by
DESCRIBE FIELD text LENGTH lengh2 in character mode.
T_ZSMY_DEMREG_V1 = record_tab by
record_tab TO MOVE-Corresponding t_zsmy_demreg_v1.
escape_trick = hot3. by
escape_trick-x1 = hot3.
itab_txt TYPE wt by
ITAB_TXT TYPE TABLE OF TEXTPOOL
DATA: string3 (3) TYPE X VALUE B2023 '3 'by
DATA: string3 (6) B2023 TYPE c VALUE '3 '.
OPEN DATASET file_name IN TEXT MODE by
OPEN DATASET file_name FOR INPUT IN TEXT MODE ENCODING NON-UNICODE.
or
OPEN DATASET file_name FOR INPUT IN TEXT MODE ENCODING DEFAULT.
CODE FROM PAGE TRANSLATE a_codepage record by
record TRANSLATE USING a_codepage.
CALL FUNCTION 'DOWNLOAD' by
CALL METHOD cl_gui_frontend_services => gui_download
CALL FUNCTION 'WS_DOWNLOAD' by
CALL METHOD cl_gui_frontend_services => gui_download
CALL FUNCTION 'UPLOAD' by
CALL METHOD cl_gui_frontend_services => gui_upload
CALL FUNCTION 'WS_UPLOAD' by
CALL METHOD cl_gui_frontend_services => gui_upload
PERFORM USING HEAD APPEND_XFEBRE +2. by
PERFORM USING HEAD APPEND_XFEBRE +2 (98).
Best Regars
Fabio Rodriguez

What is the best app for word processing on the i pad

What is the best app for word processing using an i pad

Have a look at the following:
http://itunes.apple.com/sg/app/quickoffice-pro-hd-edit-office/id376212724?mt=8&l s=1
http://itunes.apple.com/sg/app/office2-hd/id364361728?mt=8&ls=1
http://itunes.apple.com/sg/app/documents-to-go-premium-office/id317107309?mt=8&l s=1
http://itunes.apple.com/sg/app/polaris-office/id513188658?mt=8&ls=1

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 are the areas impact query to run for ever/long?

Hi All,
When I have to talk about long running scripts or procedures I focus on DTA which suggests on Indexing and infact I think this is the main cause. What are the other areas which we need to consider for Long running queries and troubleshooting tools we need
to use do you think?
Ofcourse blocking impacts but am purely thinking at query perspective.
Thanks
Swapna

What are the other areas which we need to consider for Long running queries and troubleshooting tools we need to use do you think?
One of the reasons is blocking. Please take a look at these links:
INF: Understanding and resolving SQL Server blocking problems
Troubleshoot Slow-Running Queries In SQL Server
T-SQL Articles
T-SQL e-book by TechNet Wiki Community
T-SQL blog

What's the best network for distributed processing?

Hey guys,
I have a network of three computers... I have distributed processing all set up on Compressor, and it runs really fast through the ethernet connection I have set up.
What's the absolute best way to set up this network?
The macbooks both have a firewire input, but that's not being used to transfer the data in this case... it's all ethernet.
The mac pro has 2 firewire ports... leaving one potentially open for a network.
Do you think it would be beneficial to set up a firewire network for these three computers, or is there any reason why a simple ethernet network is preferable?
Thanks in advance for all of your help...
Oh! One more question!
If I was going to set up a firewire network, how would I do it?
---Trav

Hi MrWizard.. do you have Compressor.app V4.1? (Dec 2013) installed or the older ones.? According to you sign you're on older OSX 10.7.5.
The idea you post is sound HOWEVER... it's somewhat fickle and troubesome.. I'm assuming old V3.4 Compressor/Qmaster later ....
Hardware:
You can CERTAINLY use the Firewire ports as NETWORKS NIC using IP over FW.. It certain works between TWO macs as Ive used it yeas back..
Assume you have a FW hub or use the single FW HUB in the MACPRO ... or scout around for a fw switch 800 (if they exist!) or just use a FW800 to 400 cables and an cheap legacy FW400 hub... I saw one once in Taipei!
Simply on each configure the Firewrie INTERFACEs in the System Preferences / Network .... (+ add interface etc etc), apply
Either
hard code (manual) an IP address (1.1.1.x) for each,
Install and deploy OSX SERVER on your MACPRO (IP - 1.1.1.1) and set up a simple DNS and domain "mrwizards.cool_network" for that FW subnet (1.1.1.1x) then DHCP server for that subnet so that when the two MACBOOM PROS connect tey get a an IP address such as 1.1.1.2-253 and assign machine names. Set the dsn serahc on each machine to add 1.1.1.1 (your macpro to resolve machine names0. More work however easier to manage.
test your local DNS between the machines or TRACEROUTE / PING the machines from each other and verify the IP path over the FW NICs works ok.
as long as you can ascertain the IP traffic around your 1.1.1.x subnet the better.
Once you configure these as a separate NETWORK, you will need some way to provide FireWire however... this is only the start of your headaches. Im assuming you are on an olde Compressor/Qmaster V3.5 with legacy FCS 3 suite... true/false?
The configurations takes patience and trial and error and some clear understanding of what you are trying ot acheive if its really worth the effort.
TRANSCODING over nodal cluster: AKA DISTRIBUTED SEGMENTED MULTIPASS TRANSCODING!
ON paper you'd imaging the throughput would be worth it. Sadly the converse is true!.. it often takes LONGER to use a bunch of nodes rather than submission on a SINGLE machine using a CLUSTER on a single machine....
the elapsed time for the submission relies on the processing speed of the slowest machine and its network connection
final assembly of the quicktime peices for the object
hmmmm often quickier just to use a single CLUSTER on the MACPRO!.
You MAY want to consider this option assuming the hardware you have mentioned:
what about this instead of FireWre NICS?
USE Gbit ETHERNET allaround.
Steps:
Set the WIFI on the host to use the WIFI only network for you usual internal activities and bonjour (.local) etc.. assume low IP traffic. - all works oK
OPTION: on the MACPRO dedicate EN0 (first ethernet NIC to WIFI router). Turn off WIFI on MACPRO.
Utilise the ETHERNET (EN0 - builit in ethernet) on the MACBOOKs (older ones? .. will be very slow BTW)
connect the MACPRO Second ETHERNET, and the MACBOOk (pros?) ethenets to a cheap 8 x port Ethernet HUB switch ($HK150 / €15) they are all switches these days). This gives you an isolated subnet... no router needed. Plug in the hub/switch and power on!
look at step 3. above .. QUICK START: just hard code IP addresses as follows in each SYSTEM PREF/network):
MAC PRO ip 1.1.1.1
MACBOOK (Pro) #2 : ip address 1.1.1.2
MACBOOK (Pro) #2 : ip address 1.1.1.3
test the 1.1.1.1-1.1.1.3 network... (ping or traceroute)
V3.5 Compressor and Qmaster for ye old FCS - dig in to QMASTER PREFS as:
MACPRO - set servces and ALSO MAKE CONTROLLER., set NETWORK INTERFACE to the interface on the ETHERNET 2 (not all). set instances to more than 1 one instance but NOT max! Tick MANAGED SERVICES
MACBOO (pro)'s set servces only, set NETWORK INTERFACE to the interface on the ETHERNET (not all). set instances to more than 1 one instance but NOT max! Tick MANAGED SERVICES
launch APPLE QADMINISTRATOR.app and make a managed cluster - easy (DONT waste your time with Quickcluster!.. just dont)
IMPORTANT: make sure teh SOURCE and TARGETS of ALL the pbjects tha the transcodes will use are AVAILALBE (mounted and access) on ALL the machines that you want to participate.
set up batch and make sure SEGMENTED is ticked in the inspector..... submit the job
See how you go.
However if you have Compressor V4.1 (dec 2013) then just set your network up and it should just work with out all teh voodoo in the previous steps.
Post your results for others to see.
Warwick
Hong Kong

What are the configuration steps for cheque process

hi,
sap gurus,
what are the steps for cheque process if our customer wanted to pay by the mode of cheque.
regards,
balaji.t
09990019711.

Hi,
Kindly go to OVFD where in you will have to create a new payment procedure if it's not there in standard SAP. Then, you will have to assign this new payment guarantee procedure in customer in sales area data>billing document screen. As far as standard SAP is concerned you will be able to assign the payement by cards in customer master, but for DD process I think you will have to create it.
Hrishikesh

What is the prupose abap query? configuaration process?

Similar Messages

Maybe you are looking for