Element adaptor dump

Hi,
We are facing a weird problem in the portal for a webdynpro ABAP application. When the user clicks on the applcation link in portal multiple times there is timeout error or a short dump for assert condition failed. This dump is triggered from the below class. The assert statement is highlighted in the below code extract.
Class: CL_NW7_VIEW_ELEMENT_ADAPTER
Method: DISPATCH_NW7_EVENT
METHOD dispatch_nw7_event.
DATA: l_event_handler TYPE REF TO if_wdr_nw7_event_handler.
l_event_handler = get_nw7_event_handler( i_event_handler_id ).
assert l_event_handler is not initial.
" View-based Delta Rendering: tracking of client events
raise event on_nw7_handle_event
    exporting
      event_handler = l_event_handler
      event_name    = i_event_name.
l_event_handler->handle_event(
      i_event_name       = i_event_name
      i_event_parameters = i_event_parameters
      i_update_data      = i_update_data
      i_event_queue      = i_event_queue ).
ENDMETHOD.
Please share your views in getting rid of this bug.
Thanks in Advance.
Kiran.

Hi Kiran,
This can be a timeout problem. However it is happening only in Portal environment ? Are you able to execute this application from SAP GUI. You can create a simple test wda with LinkTo URL ui.
What does this application do ? Is there any specific Special UI like OfficeControl,Acf etc?
See the [https://service.sap.com/sap/support/notes/1411434|https://service.sap.com/sap/support/notes/1411434]
[https://service.sap.com/sap/support/notes/1470327|https://service.sap.com/sap/support/notes/1470327]

Similar Messages

Compiler bug in 10.1.3 EA1? get "Internal compilation error" with EnumSet

The code sample below generates "Error: Internal compilation error, terminated with a fatal exception" when doing make. It's a very simple example, it creates an EnumSet with one element and dumps it via the "toString()" method.
If I change the line:
"EnumSet set = EnumSet.of(Buttons.ONE);"
To:
"EnumSet set = EnumSet.allOf(c);"
It works fine. For some reason the "of" method of "EnumSet" crashes the compiler.
Any ideas?
========================================
package mypackage;
import java.util.EnumSet;
public class EnumDemo
enum Buttons { ONE, TWO, THREE }
public EnumDemo()
public void dump()
          Class c = Buttons.class;
          EnumSet set = EnumSet.of(Buttons.ONE);
          System.out.println(set.toString());
public static void main(String[] args)
EnumDemo cls = new EnumDemo();
cls.dump();
==============================

package com.esp.main;
import java.awt.Dimension;
import java.awt.event.MouseAdapter;
import java.awt.event.MouseEvent;
import javax.swing.JTree;
import javax.swing.event.TreeModelEvent;
import javax.swing.event.TreeModelListener;
import javax.swing.event.TreeSelectionEvent;
import javax.swing.event.TreeSelectionListener;
import javax.swing.tree.DefaultTreeModel;
import javax.swing.tree.TreePath;
public class TreeNavigator extends JTree {
private FormMain fm;
public TreeNavigatorNode selectedTreeNode;
public TreePath selectedTreePath;
public JTree thisTree;
public TreeNavigator(FormMain pFM) {
fm = pFM;
thisTree = this;
addTreeSelectionListener(new TreeSelectionListener() {
public void valueChanged(TreeSelectionEvent e) {
selectedTreeNode = (TreeNavigatorNode)thisTree.getLastSelectedPathComponent();
if (selectedTreeNode == null) {
return;
selectedTreePath = e.getPath();
addMouseListener(new MouseAdapter() {
public void mouseReleased(MouseEvent e) {
if (e.getClickCount() == 1) {
doPopup(e.getX(), e.getY());
String nodeInternalFrameClassName = selectedTreeNode.getInternalFrameClassName();
String nodeNodeTypeDesc = selectedTreeNode.getNodeTypeDesc();
if ((selectedTreeNode != null) && (nodeNodeTypeDesc.equals("FORM") || nodeNodeTypeDesc.equals("GRAPH"))) {
fm.showInternalFrame(nodeInternalFrameClassName, fm, null);
} else if (e.getClickCount() == 1) {
TreePath path = thisTree.getClosestPathForLocation(e.getX(), e.getY());
thisTree.setSelectionPath(path);
public void doPopup(int x, int y) {
if ((selectedTreeNode != null) && selectedTreeNode.nodeTypeDesc.equals("MODULE")) {
fm.cm.sendString("Do Nothing");
} else {
fm.cm.sendString("Launch form");
setEditable(false);
setMaximumSize(new java.awt.Dimension(3200, 3200));
setPreferredSize(new java.awt.Dimension(800, 100));
setShowsRootHandles(false);
setLargeModel(false);
setRootVisible(false);
setDragEnabled(false);
DefaultTreeModel treeNavigatorModel = new DefaultTreeModel(fm.treeNavigatorNodeArray[fm.rootNode], true);
treeModel.addTreeModelListener(new NavigatorTreeModelListener());
setModel(treeNavigatorModel);
expandAll(this);
try {
jbInit();
} catch (Exception e) {
e.printStackTrace();
public void expandAll(JTree tree) {
int row = 0;
while (row < tree.getRowCount()) {
tree.expandRow(row);
row++;
private void jbInit() throws Exception {
this.setSize(new Dimension(286, 383));
TreeNavigatorCellRenderer renderer = new TreeNavigatorCellRenderer(fm);
this.setCellRenderer(renderer);
class NavigatorTreeModelListener implements TreeModelListener {
public void treeNodesChanged(TreeModelEvent e) {
TreeNavigatorNode node;
node = (TreeNavigatorNode)(e.getTreePath().getLastPathComponent());
* If the event lists children, then the changed
* node is the child of the node we've already
* gotten. Otherwise, the changed node and the
* specified node are the same.
try {
int index = e.getChildIndices()[0];
node = (TreeNavigatorNode)(node.getChildAt(index));
} catch (NullPointerException exc) {
public void treeNodesInserted(TreeModelEvent e) {
public void treeNodesRemoved(TreeModelEvent e) {
public void treeStructureChanged(TreeModelEvent e) {
}

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.

Dynamic properties problem

Dear friends,
I am trying to create an application form, where i have a
tabNavigator, which being rendered based on number of items set in
textInput:
private function addCars(event:Event):void{
var car_number:int=int(number_of_cars.text);
for(var i:int = 1; i <= car_number; i++){
var new_car:car_details=new car_details();
new_car._car_id=i;
car_navigator.addChild(new_car);
where car_details is class defined in MXML, and sets some
properties for car:
<mx:HBox width="100%">
<mx:Label text="Date of creation"/>
<mx:DateField id="car_creation_date"/>
<mx:Label text="Model"/>
<mx:TextInput id="car_model"/>
</mx:HBox>
It works fine. Now i want to be able to set id's for this
properties in a run-time so i can later get an information from
fields and pass it to ColdFusion.
Can you explain how to do this? We've try many things - none
works.
Thanks,
Mika

I'm not exactly sure what you mean, so what I'm going to say next might have nothing to do with what you want.
Since you are obviously dynamically generating the JSP, couldn't you also generate some javascript code that before you submit loops through al the form elements and dumps all the data in a single hidden input field? I always use a structure like this:
1|2|3|4|5
This would mean that there were 5 form elements with the selected values '1' to '5'. And then when I need to parse the data (fx. in a bean), I split the string on the pipe (|) character. According to what you need to know you might need to encode more information into the string, but for me this has always worked just fine.

Network line noise and BT broadband

It's worth a mention, a pal fo mine recently "expanded" his home network, using the proprietry mains network adapters that you can buy, to use your house wiring to expand your network. His caused him a lot of problems with noise, and once disconnected problems went away. Just a heads up, if you're using them.

Powerline adaptors are controversial devices. Your friend has just discovered the reason for the controversy. They work basically by sending relatively powerful radio signals through the house wiring. It is the unwanted radiation of these signals that caused his noise problems.
The problem with these devices is that, under strictly controlled laboratory test conditions, they comply with the relevant radio interference standards, and are awarded the appropriate accreditations (CE mark, etc.). When they are installed in the average house, it is often a very different story. The wiring in every house is different, and will have different effects, sometimes drastic, in terms of radiating radio interference.
PLC (Power Line Communication) for the transport of high speed data is a technology that's pushing its luck - it works fine for low speed applications like remote meter reading, but it has a whole host of interference-related problems when used for computer networking. This is well known to the manufacturers of Powerline Adaptors, but they sell them anyway on the basis that they work in "Most" cases. Manufacturers interpretation of "Most" may differ significantly from ours, however.
If Powerline Adaptors work for you, and don't cause any problems for you or your neighbours, then OK. On the other hand, if your house wiring radiates any perceptible interference from these adaptors, dump them, and use the better alternatives - WiFi or ethernet cabling. (BT Vision decided to supply these devices as part of their package. They may have since come to regret this, given the potential for service problems and unhappy customers).

Kodo.rar and WebLogic 7

Hi,
I__m trying to deploy the kodo.rar file in Web Logic 7 and I__m running into
the problem described in this
(http://www.solarmetric.com/Support/Newsgroups/article.php?id=2553&group=solarmetric.kodo.developer)
inquiry.
That is, I__m getting a bunch of error message stating that the application
server cannot find __set__ methods for the ra.xml configured properties.
Example output:
<Feb 10, 2003 1:40:55 PM CST> <Notice> <WebLogicServer> <000327> <Starting
WebLogic Admin Server "myserver" for domain "mydomain">
<Feb 10, 2003 1:41:36 PM CST> <Error> <Connector> <190070> << KodoJDO_kodo
Cannot find a "set" method in the ManagedConnectionFactory for theconfiguration property "UseBatchedStatements". Ensure that the MCF
contains "get" and "set" methods for each of the ra.xml configuration
properties. Ensure that the data types
associated with these methods match the data type specified in the
<config-prope
rty-type> element.>
Can you tell me if this issue was ever resolved? Or is there a work
around for it?
Thanks.

Marc,
I downloaded 2.4.1 this morning un-jard the kodo.rar file, updated the
ra.xml file, created a kodo1.rar file and deployed it to WebLogic with
similiar results. (See below.)
Yesterday (2.4.0) I dumped the methods in the
com.solarmetric.kodo.impl.jdbc.ee.ManagedConnectionFactoryImpl class and
found a lot of the "set" methods that web logic was complaining about.
(Method dump is attached below the Similiar Results.)
Any advice you can give would be appreciated.
-Tim S.
*===Similiar results:
Starting WebLogic Server...
<Feb 11, 2003 11:03:56 AM CST> <Notice> <Management> <140005> <Loading
configura
tion D:\tapps\bea\user_projects\mydomain\.\config.xml>
<Feb 11, 2003 11:04:04 AM CST> <Notice> <Security> <090082> <Security
initializi
ng using realm myrealm.>
<Feb 11, 2003 11:04:04 AM CST> <Notice> <WebLogicServer> <000327>
<Starting WebL
ogic Admin Server "myserver" for domain "mydomain">
<Feb 11, 2003 11:04:24 AM CST> <Error> <Connector> <190070> <<
KodoJDO_kodo > Ca
nnot find a "set" method in the ManagedConnectionFactory for the
configuration p
roperty "UseBatchedStatements". Ensure that the MCF contains "get" and
"set" met
hods for each of the ra.xml configuration properties. Ensure that the data
types
associated with these methods match the data type specified in the
<config-prop
erty-type> element.>
<Feb 11, 2003 11:04:24 AM CST> <Error> <Connector> <190070> <<
KodoJDO_kodo > Ca
nnot find a "set" method in the ManagedConnectionFactory for the
configuration p
roperty "MaxPool". Ensure that the MCF contains "get" and "set" methods
for each
of the ra.xml configuration properties. Ensure that the data types
associated w
ith these methods match the data type specified in the
<config-property-type> el
ement.>
<Feb 11, 2003 11:04:24 AM CST> <Error> <Connector> <190070> <<
KodoJDO_kodo > Ca
nnot find a "set" method in the ManagedConnectionFactory for the
configuration p
roperty "ConnectionTestTimeout". Ensure that the MCF contains "get" and
"set" me
thods for each of the ra.xml configuration properties. Ensure that the
data type
s associated with these methods match the data type specified in the
<config-pro
perty-type> element.>
*====
Dumped Methods
*====
D:\apps\kodo-jdo-2.4.0\com\edsplm\sca\basicactions\persistent>java
ShowMethods com.solarmetric.kodo.impl.jdbc.ee.Managed
ConnectionFactoryImpl
==== Methods =====
--- edits here ---
com.solarmetric.kodo.conf.SimpleConfiguration.getDefaultFetchThreshold()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setDefaultFetchThreshold(int)
public int
com.solarmetric.kodo.conf.SimpleConfiguration.getDefaultFetchBatchSize()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setDefaultFetchBatchSize(int)
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setQueryFilterListeners(java.l
ang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getQueryFilterListeners()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setEnableQueryExtensions(boole
an)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getEnableQueryExtensions()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setPersistenceManagerClass(jav
a.lang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getPersistenceManagerClass()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setPersistenceManagerPropertie
s(java.lang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getPersistenceManagerPropertie
s()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setDataCacheClass(java.lang.St
ring)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getDataCacheClass()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setDataCacheProperties(java.la
ng.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getDataCacheProperties()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setDataCache(com.solarmetric.k
odo.runtime.datacache.DataCache)
public synchronized com.solarmetric.kodo.runtime.datacache.DataCache
com.solarmetric.kodo.conf.SimpleConfiguration.getDa
taCache()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setProxyManagerClass(java.lang
String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getProxyManagerClass()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setProxyManagerProperties(java
lang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getProxyManagerProperties()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setProxyManager(co
m.solarmetric.kodo.util.ProxyManager)
public synchronized com.solarmetric.kodo.util.ProxyManager
com.solarmetric.kodo.conf.SimpleConfiguration.getProxyManager
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setCacheReferenceSize(int)
public int
com.solarmetric.kodo.conf.SimpleConfiguration.getCacheReferenceSize()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setUseSoftTransactionCache(boo
lean)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getUseSoftTransactionCache()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setOptimistic(boolean)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getOptimistic()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setRetainValues(boolean)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getRetainValues()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setRestoreValues(boolean)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getRestoreValues()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setIgnoreCache(boolean)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getIgnoreCache()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setNontransactionalRead(boolea
n)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getNontransactionalRead()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setNontransactionalWrite(boole
an)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getNontransactionalWrite()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setMultithreaded(boolean)
public boolean
com.solarmetric.kodo.conf.SimpleConfiguration.getMultithreaded()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionUserName(java.lan
g.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionUserName()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionPassword(java.lan
g.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionPassword()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionURL(java.lang.Str
ing)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionURL()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setPersistenceManagerFactoryCl
ass(java.lang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getPersistenceManagerFactoryCl
ass()
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionDriverName()
public void com.solarmetric.kodo.conf.SimpleConfiguration.setMaxPool(int)
public int com.solarmetric.kodo.conf.SimpleConfiguration.getMaxPool()
public void com.solarmetric.kodo.conf.SimpleConfiguration.setMinPool(int)
public int com.solarmetric.kodo.conf.SimpleConfiguration.getMinPool()
public void com.solarmetric.kodo.conf.SimpleConfiguration.setMsWait(int)
public int com.solarmetric.kodo.conf.SimpleConfiguration.getMsWait()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionFactoryName(java.
lang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionFactoryName()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionFactory(java.lang
Object)
public synchronized java.lang.Object
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionFactory()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionFactory2Name(java
lang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionFactory2Name()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionFactory2(java.lan
g.Object)
public synchronized java.lang.Object
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionFactory2()
public java.util.Properties
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionPropertiesProps()
public void
com.solarmetric.kodo.conf.SimpleConfiguration.setConnectionProperties(java.l
ang.String)
public java.lang.String
com.solarmetric.kodo.conf.SimpleConfiguration.getConnectionProperties()
public java.beans.BeanInfo[]
com.solarmetric.kodo.conf.SimpleConfiguration.getAdditionalBeanInfo()
public java.beans.BeanDescriptor
com.solarmetric.kodo.conf.SimpleConfiguration.getBeanDescriptor()
public int
com.solarmetric.kodo.conf.SimpleConfiguration.getDefaultEventIndex()
public int
com.solarmetric.kodo.conf.SimpleConfiguration.getDefaultPropertyIndex()
public java.beans.EventSetDescriptor[]
com.solarmetric.kodo.conf.SimpleConfiguration.getEventSetDescriptors()
public java.awt.Image
com.solarmetric.kodo.conf.SimpleConfiguration.getIcon(int)
public java.beans.MethodDescriptor[]
com.solarmetric.kodo.conf.SimpleConfiguration.getMethodDescriptors()
public java.beans.PropertyDescriptor[]
com.solarmetric.kodo.conf.SimpleConfiguration.getPropertyDescriptors()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setProperties(java.la
ng.String) throws java.io.IOExce
ption
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setDictionary(com.sol
armetric.kodo.impl.jdbc.schema.D
BDictionary)
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setConnectionDriverNa
me(java.lang.String)
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setAutoReturnTimeout(
int)
public int
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getAutoReturnTimeout(
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setConnectionTestTime
out(int)
public int
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getConnectionTestTime
out()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setDictionaryClass(ja
va.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionaryClass()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setDictionaryProperti
es(java.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDictionaryProperti
es()
public com.solarmetric.kodo.impl.jdbc.schema.DBDictionary
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDict
ionary(com.solarmetric.kodo.impl.jdbc.runtime.Connector)
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setSQLExecutionManage
r(com.solarmetric.kodo.impl.jdbc
SQLExecutionManager)
public com.solarmetric.kodo.impl.jdbc.SQLExecutionManager
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getSQLE
xecutionManager()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setSQLExecutionManage
rClass(java.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getSQLExecutionManage
rClass()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setSequenceFactoryCla
ss(java.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getSequenceFactoryCla
ss()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setSequenceFactoryPro
perties(java.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getSequenceFactoryPro
perties()
public com.solarmetric.kodo.impl.jdbc.SequenceFactory
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getSequence
Factory(com.solarmetric.kodo.impl.jdbc.runtime.Connector)
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setSequenceFactory(co
m.solarmetric.kodo.impl.jdbc.Seq
uenceFactory)
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setSQLExecutionListen
erClass(java.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getSQLExecutionListen
erClass()
public com.solarmetric.kodo.impl.jdbc.SQLExecutionListener
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getSQL
ExecutionListener()
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDefaultPersistence
ManagerFactoryClass(
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setDefaultSubclassPro
viderClass(java.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDefaultSubclassPro
viderClass()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setDefaultSubclassPro
viderProperties(java.lang.String
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDefaultSubclassPro
viderProperties()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setDefaultClassMappin
gClass(java.lang.String)
public java.lang.String
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getDefaultClassMappin
gClass()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setWarnOnPersistentTy
peFailure(boolean)
public boolean
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getWarnOnPersistentTy
peFailure()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setFlatInheritanceMap
ping(boolean)
public boolean
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getFlatInheritanceMap
ping()
public void
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.setUseBatchedStatemen
ts(boolean)
public boolean
com.solarmetric.kodo.impl.jdbc.JDBCSimpleConfiguration.getUseBatchedStatemen
ts()
public void
--- Edits here ---
Marc Prud'hommeaux wrote:
Tim-
Are you using Kodo 2.4.1? The issue (if it is the same one I am thinking
of) should be resolved in 2.4.1's kodo.rar file.
Let us know if this does not help.
In article <[email protected]>, Tim Slechta wrote:
Hi,
I__m trying to deploy the kodo.rar file in Web Logic 7 and I__m running into
the problem described in this
(http://www.solarmetric.com/Support/Newsgroups/article.php?id=2553&group=solarmetric.kodo.developer)
inquiry.
That is, I__m getting a bunch of error message stating that the application
server cannot find __set__ methods for the ra.xml configured properties.
Example output:
<Feb 10, 2003 1:40:55 PM CST> <Notice> <WebLogicServer> <000327> <Starting
WebLogic Admin Server "myserver" for domain "mydomain">
<Feb 10, 2003 1:41:36 PM CST> <Error> <Connector> <190070> << KodoJDO_kodo
Cannot find a "set" method in the ManagedConnectionFactory for theconfiguration property "UseBatchedStatements". Ensure that the MCF
contains "get" and "set" methods for each of the ra.xml configuration
properties. Ensure that the data types
associated with these methods match the data type specified in the
<config-prope
rty-type> element.>
Can you tell me if this issue was ever resolved? Or is there a work
around for it?
Thanks.
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

MKT_ELEMENT_CREATE gives Dump during creation of Campaign Element

Hi,
I am trying to create campaign element through code and I am getting dump in the following class method.
Class : CL_CRM_MKTPL_OL_MKTPROJECT
Method : SET_ATTRIBUTES
Line No : 15 ->> lr_header_item->get_attributes( EXPORTING iv_get_external_attributes = abap_true
                                  IMPORTING es_attributes              = ls_header_attr ).
In above statement LR_HEADER_ITEM comes as Initial.
Below is the code for creating campaign element.
DATA: LR_TASK          TYPE REF TO CL_CGPL_TASK,
        LR_TASKS         TYPE REF TO CL_CGPL_TASKS,
        LR_PROJECT       TYPE REF TO CL_CGPL_PROJECT.
DATA: WA_PROJECT TYPE CGPL_PROJECT.
DATA: WA_TASK     TYPE CGPL_TASK.
DATA: LIT_TASKS   TYPE CGPLD_ITAB_TASK.
DATA: WA_MESSAGE TYPE BAPIRET2.
DATA: LIT_RETURN TYPE TABLE OF BAPIRETURN1.
DATA: WA_CAMPAIGN TYPE CRM_MKTPL_CAMPAIGN,
        WA_ATTRIBUTES TYPE CRM_MKTPL_MKTELEMENT.
DATA: LV_GUID TYPE SYSUUID-X."BAPI_MARKETINGELEMENT_GUID-MKTELEMENT_GUID.
DATA: LV_CAMP_GUID TYPE BAPI_MARKETINGELEMENT_GUID-MKTELEMENT_GUID.
CALL FUNCTION 'MKT_ELEMENT_READ'
    EXPORTING
      MARKETINGELEMENT = IV_SOURCE_GUID - THIS IS A IMPORT PARAMETER OF FUNCTION MODULE ( CAMPAIGN GUID ).
    IMPORTING
      EX_CAMPAIGN      = WA_CAMPAIGN
      EX_ATTRIBUTES    = WA_ATTRIBUTES.
CONCATENATE WA_ATTRIBUTES-EXTERNAL_ID '_' SY-DATUM '_' SY-UZEIT INTO WA_ATTRIBUTES-EXTERNAL_ID.
WA_ATTRIBUTES-OBJECT_TYPE = 'CPT'.
CALL FUNCTION 'SYSTEM_UUID_CREATE'
    IMPORTING
      UUID = WA_ATTRIBUTES-GUID.
LV_CAMP_GUID = WA_ATTRIBUTES-GUID.
WA_ATTRIBUTES-PROJECT_GUID = IV_SOURCE_GUID.
WA_ATTRIBUTES-PARENT_GUID = IV_SOURCE_GUID.
CALL FUNCTION 'MKT_ELEMENT_CREATE'
    EXPORTING
      IM_MARKETINGELEMENT = LV_CAMP_GUID
      IM_ATTRIBUTES       = WA_ATTRIBUTES
    TABLES
      RETURN              = LIT_RETURN.
IF LIT_RETURN[] IS INITIAL.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT = 'X'.
ENDIF.

This would happen if you are not passing the right guid to the program or Function Module. Please check that the guid is available in cgpl_project table.
Ajay Gupta

Dump error when clicked on text elements in SAP Script window

Hi All,
There is an inclusion in SAP Script. I have written the code in driver program. I need to pass the value to SAP Script in the requested position. But when I go to SE71 > Form Name > Change or Display > MAIN Window > Text Elements > I get a dump error.
Category               ABAP Programming Error
Runtime Errors         DATA_LENGTH_TOO_LARGE
Except.                CX_SY_RANGE_OUT_OF_BOUNDS
ABAP Program           SAPLSTXK
Application Component BC-SRV-SCR
Date and Time          30.04.2014 20:00:08
Short text
     Invalid partial field access: Length is too large
What happened?
     Error in the ABAP Application Program
     The current ABAP program "SAPLSTXK" had to be terminated because it has
     come across a statement that unfortunately cannot be executed.
What can you do?
     Note down which actions and inputs caused the error.
     To process the problem further, contact you SAP system
     administrator.
     Using Transaction ST22 for ABAP Dump Analysis, you can look
     at and manage termination messages, and you can also
     keep them for a long time.
Error analysis
     An exception occurred that is explained in detail below.
     The exception, which is assigned to class 'CX_SY_RANGE_OUT_OF_BOUNDS', was not
      caught in
     procedure "TOKEN_COMMENT" "(FORM)", nor was it propagated by a RAISING clause.
     Since the caller of the procedure could not have anticipated that the
     exception would occur, the current program is terminated.
    The reason for the exception is:
    In the executed program "SAPLSTXK", the system attempted to access the field
    "ITF_TOKEN" of the type "C" and with the length 255 using the length 272.
    However, a partial field access with a length specification that is
    larger than the field length is not allowed.
How to correct the error
    Reduce the length used to access the field.
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DATA_LENGTH_TOO_LARGE" "CX_SY_RANGE_OUT_OF_BOUNDS"
    "SAPLSTXK" or "LSTXKFRN"
    "TOKEN_COMMENT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
2937 * todo empty comment ???
2938       if g_tm_open    eq true or     " Section
2939          g_tm_b_close eq true.
2940         l_token = '\chcbpat0'.
2941         l_len = strlen( l_token ).
2942         token_control = true.
2943         assign l_token to <itf1>.
2944         perform put_itf1_new using l_len.
2945         perform token_line_begin changing l_next_token.
2946       else.                          " without section
2947         concatenate '\chcbpat0\line' g_cf_string l_cbpat_token into l_token.
2948         l_len = strlen( l_token ).
2949         token_control = true.
2950         assign l_token to <itf1>.
2951         perform put_itf1_new using l_len.
2952       endif.
2953     elseif l_next_token-code eq ')L'.         " \par
2954       l_token = '\par'.
2955       l_len = strlen( l_token ).
2956       token_control = true.
2957       assign l_token to <itf1>.
2958       perform put_itf1_new using l_len.
2959     elseif l_next_token-code eq '(C' or       " \par + format
2960            l_next_token-code eq ')C' or
2961            l_next_token-code eq '(&' or
2962            l_next_token-code eq 'TA' or
2963            l_next_token-code eq 'SC' or
2964            l_next_token-code eq 'ST'.
2965       concatenate '\chcbpat0\par' g_pf_string g_cf_string l_cbpat_token into l_token.
2966       l_len = strlen( l_token ).
>>>>>       itf_token(l_len) = l_token.
2968       token_control = true.
2969       assign l_token to <itf1>.
2970       perform put_itf1_new using l_len.
2971     endif.
2972
2973 * Step 7: (L to disarm
2974   if g_compose eq true and
2975      l_next_token-code eq '(L'.
2976     perform read_next_itf_token(rstxscan) using p_token.
2977   endif.
2978
2979 ENDFORM.                    " token_comment
2980 *&---------------------------------------------------------------------*
2981 *&      Form create_lang_info
2982 *&---------------------------------------------------------------------*
2983 *       add default language to rtf
2984 *----------------------------------------------------------------------*
2985 *      -->P_HEADER text
2986 *      <--P_RESULT text
How do I open the text elements? I need to pass the variable inside SAP Script.
Please Help. The requirement is pending from very long. Not able to rectify this issue.
Regards,
Rekha

Hi,
There is a SAP Note about this problem
566794 - Runtime error: STRING_OFFSET_TOO_LARGE during conversion
Correction Instructions
Correction Instructions
Software Component
Valid from
Valid to
Number
SAP_BASIS
46B
46D
473267
SAP_BASIS
610
620
473185
Support Packages & Patches
Support Packages
Software Component
Release
Support Package
SAP_BASIS
46B
SAPKB46B48
46C
SAPKB46C39
46D
SAPKB46D28
610
SAPKB61027
620
SAPKB62014
Regards
Miguel

Dump in adding a ui element to group dynamically

hi all,
I have a group which has a dropdown ,my requirement is when i click a button
a dropdown should be created dynamically below the dropdown created at design time.
My code in wddomodifyview()
cl_wd_dropdown_by_idx=>new_dropdown_by_idx(
   EXPORTING
       bind_texts                 = 'CN_RULEBUILDER.CA_CONDITION'
         RECEIVING
        control    = lr_input ).
   lr_group ?= view->get_element( 'GRP_BUILDER' ).
lr_group->add_child( lr_input ).
when i run this i get dump
Adapter error in MATRIX_LAYOUT "_03" of view "ZMCPTS_RULES_SCREEN.V_MAIN": No LayoutData exists for child element "_10" of the UIElementContainer
Can someone please help me with this

This is because you need to set the Layout for the new element added as below:
data LR_FLOW_DATA type ref to CL_WD_FLOW_DATA.
LR_FLOW_DATA = CL_WD_FLOW_DATA=>NEW_FLOW_DATA( element = lr_input ).
Thanks,

Each time that I go into edit with Photoshop Elements 8 it causes a physical dump and shuts down

Each time that I go into my Photoshop Elements 8 it causes a physical dump and shuts down. I have only used this program a few times although I have had it a few years. The first couple of times it worked fine; but now, it shuts me down each time. I have already tried unistall and reinstall. Help!

Well, can you try opening just the Photoshop Elements 8 (from the Start menu) and see if it opens Editor from Welcome Screen or not?
It it still crashes, please try couple of probable solutions as mentioned below:
Solution 1:
Close Elements.
Launch the Photoshop Elements Welcome Screen and hold down ctrl + alt + shift as you click Editor.
Continue to hold the keys until you see a message box asking if you want to delete Photoshop Elements settings file; click Yes. Elements will open with default preferences.
Solution 2: In case any network printer is attached try to launch without network or printer uninstall or make different printer as default.
Solution 3: Try launching with anti-virus off or removing PSE from conflicting list.
Solution 4:
On the drive on which you have installed PSE,on my machine it is on C:
Go to C:\Program Files\Adobe\Photoshop Elements 10\Locales\<locale>\Plug-Ins\Import-Exportand you will find twain plug-in. Remove that plug-in from that location and copy it somewhere else.
Now launch PSE and check if it works.

Premiere Elements 4.0 - dump of physical memory

Hey Everyone,
I was in the process of burning some videos(AVI format) and when i went to the green "SHARE" tab and would select DISK(to burn DVD), it would freeze up, then immediately go to a blue screen and come up with a error message of 'BEGINNING DUMP OF PHYSICAL MEMORY'. Windows recovery indicated a problem with the PX Engine and an update was available. I went to the website and downloaded the update, rebooted the PC, and tried again but still got the memory dump message.
i have burned many pictures on DVD creating slideshows and such but this is my first time burning actual video onto a DVD. I figured the process for burning video is the same as burning pics. i created a picture slide show afterwards and it burned it just fine - no errors.
Am i doing something wrong?

A BSOD is a major problem, and is very often a sign of hardware issues. The main causes are:
Heat buildup - in the CPU, or the HDD's
RAM - bad, or going bad
PSU - going bad, or improperly connected
MoBo - going bad
This ARTICLE will link to tools that will help you track those elements, and possibly show the bad element, or potentially bad element.
I would also change Reboot on Error, to OFF, so that you can write down the report on the BSOD. There might be something in that load of "abstract code" that will be helpful, but maybe not. Also, when one reboots after a BSOD, Windows will usually yield an error message to the effect of "Windows has recovered from a serious problem... " and will often help you trace the issue. Also, this ARTICLE will give you tips for finding clues as to what was happening, just before the BSOD.
If nothing else works, see this ARTICLE.
Before doing anything else, I would solve the BSOD issue.
Good luck,
Hunt

Backend dump CX_WD_GENERAL when using the UI element ' 'ThresholdSlider'.

Hi Guys
I am using the UI element 'ThresholdSlider' in my application and its working fine from front end. However it gives a Runtime Error: UNCAUGHT_EXCEPTION with exception CX_WD_GENERAL when ever the user tries to drags the slider to chaneg the value. This does not happen if the user clicks on the slider to change the value.
As I said, the user do not face any issues in using the UI element/application. However, it gives a backend dump every time he drags the slider.
Can you please help me resolve this issue?
Highly appreciate your help.
Thanks and Regards
Pramod Ch

>Can you please tell me why there are so many dependenices for a simple basic scroll bar error, that notes got multiple corrections.
The Corrections for unified rendering rendering notes are large because they are collective notes that correct all known issues in the rendering. When you load these notes they replace all the Unified Rendering files (all CSS and JavaScript) for all UI elements. Although you may be looking to only fix one relatively small error, it necessitates that the entire JavaScript library be kept in sync.
>Did SAP rewrite this functionality on enhanement package 4.
Actually this particluar UI element was new in ERP Enhancement Package 4 (NetWeaver 7.01). But as explained above, the size and complexity of the note in question isn't related to this one particluar issue alone, but becuase the fix is a collective one.

Short dump when trying to see the text elements of main window

Hi ,
The form is running properly in 4.7 c . But when the same is copied in ECC5.0 (unicode) , i 'm getting short dump while trying to see the TEXT ELEMENTS .
The message is like ' trying to create a field with zero length'.
Regards,
Jytoi.

hi
I've never worked on ECC 5.0 version..however, I can only tell u that this could be the issue that code written in 4.7 may not be supported in 5.0..so try to get a good idea of ECC 5.0 before u start coding in this..
regards,
shamim

SC--- Dump when I use wrong WBS element

Hi SRM gurus,
Can You plase give is there any OSS note for the following dump or solution if any.
I have maintained by mistake wrong WBS element
Example : Correct WBS is E-PTHK.CK.01
Entered as E-PTHKC.CK.01 in this case getting Dump.
Entered as E-PTHK.CK.02 in this case getting std Error as " No WBS element Exist"
Thanks in advance

Thank you both,
Actually User has be maintaing in the personal settings before creating the SC.
By mistake he has typed wrong in settings so Dump occured
To avoid this is there any solution.
Thank you
Edited by: CK on Apr 2, 2009 5:44 PM

Dump showing that table does not contain any elements.

Hi All,
I have a table, with lead select.Based on the row selected, corresponding values of the row are filled in the input fields.
I filter the table and only those rows are displayed which has status "waiting". Now the problem is when there is only one row with status "waiting", and process it, its status changes to "done", as a result of which there is no row in the table, and i get following error:
Adapter error in INPUT_FIELD "IF_STATUS" of view "ZPWB.DISTRIBUTE_VIEW": Context binding for property VALUE cannot be resolved: The DISTRIBUTE_VIEW.1.PD_ITEMS_TAB node does not contain any elements
Can you please help out:)

I have now the same problem.
somebody found out what the solution is for that issue?
if i have an empty context i get a dump due to the context binding. what is the work around?

Element adaptor dump

Similar Messages

Maybe you are looking for