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

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

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

Similar Messages

What are the tables to be used for these reports

hello everybody,
i am a new user. it is only recently that i have started learning ABAP. i was given a rask by my faculty to develop the following reports. can anyone help me find out the tables that are used for them.
1. Report for Sales Orders due for delivery.
2. Revenue Reports based on Order Types.
3. Report for list of Pending Purchase Orders, Cancel Purchase orders.

Hi,
This depends on which fields you are supposed to show in output.Ask the person about layout requirement. How they want output of the report and which fields.
Normally Functional person will give table name also.
Here are few tables which can be useful in your requirement.
Sales Header table : VBAK
Sales Item table : VBAP
Delivery Header : LIKP
Delivery Item : LIPS
Purchase order header : EKKO
Purchase order item : EKPO
Better to concern this with u r requester and u ll get definite answer.
*MARK if this helps

Instance name and Var for Input Text fields

I have several Input Text fields, as a form, linked to a PHP
script for which I require Var's for each field.
But I also need Instance names for each field, so I can fix
the tabIndex.
Yet, everytime I test my movie, the text fields have their
Paths (_level0.fName) written in them.
They are normally blank, and I've tried putting in some text
of my own, but the Var name is still displayed in the text fields.
Is there any way I can stop that from happening, and keep
both the Instance names and Var's in-place.
As far as I know, I need both the Instance name (for the
tabIndex) and the Var (for the PHP script) or is there a way that
the tabIndex and PHP script will work with either of the two?
Thanks
Chaz.

Can you use a different name for ‘instance name’
and ‘var’? That seems to solve the problem but I
don’t know if that helps you in your situation.
For an example;
Instance name: test_txt
Var: test

How to define the same font size,color for a text field label

hi all,
In my project i need to define the same font size & color for all the text field lables in the application.how do we can achieve this?
Thanks & regards,

...or you could use declarative components....
Not sure if skinning would prevent developers from overriding a look and feel??? hmmm not sure..
Grant

What are the table names for CRM and APO?

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

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

What is the table for query name

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

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

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

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

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

What is the table name for Workload analysis?

Hi All TechGurus,
We need to create an ABAP program in which it displays some information of Transaction (STO3n), Report for the same (SAPWL_ST03N)
We want to create an ABAP program to get the output in excel format?
What is the table name for Workload analysis?
Many thanks in advance!!

Hi Keshav,
Thank you for your reply.
As per my requirement, i want to create an ABAP program in which it displays some information of Transaction (STO3n) and want to send the output in excel format. however I don't understand how to start with it.
Below are the conditions -
1. display data for today's date
2 .In transaction profile, task should be Dialogue.
from where should i fetch data which is getting displyed after executing t.code ST03n?
Please help me with your suggessions...
Thanks

What is the table name means to me.

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

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

What are the Table Names

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

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

What is the table name to get master_organization_id...???

Dear All,
Please help me for the below question if any one knows...
In which table, we get master_organization_id ....?
or
what is the table name to get master organization id..?
or
Master Organization id belongs to which table in oracle apps...?

For the organizations you can write this
select * from org_organization_definitions
It will return all defined organizations along with their organization_id,organization_code,organization_name and set_of_books_id etc
If my response or the response of another was helpful, please mark it accordingly
Thanks
Naveed

What is the benefit in using OID for names resolution?

I have been wondering about this for awhile. I have been working on getting this to work in Iplanet along with Pat Lehane ([email protected]), and it works now.
What are the benefits in using OID for names resolution when you can just use the static tnsnames.ora. Database and database names are not created dynamically and they don't change that often. Would creates a new database every day and has to worry about changing the static tnsnames.ora file. In my environment, we run Oracle applications from a server, so there is only one tnsnames.ora file, on the file server.
It would appear that using OID would cause extra traffic (LDAP lookups) on your network.
I would like some opinions from both Oracle and Oracle users. Thanks

hi,
A benefit of using OID for names resolution is that it allows you to centralize net8 naming (i.e., tnsnames) information in the same place (OID) where other types of administrative information (about users, enterprise groups, enterprise roles, etc) gets stored. If you are more comfortable using tnsnames.ora files for net8 naming, that is perfectly fine!
An important reason that Oracle had for providing Net8 naming functionality in OID is that the legacy 'Oracle Names' functionality of Oracle 7 will eventually be desupported. This is discussed in metalink Note #135696.1 on http://metalink.oracle.com .
Hope this helps.

What is the table contains Function module include program name

Hi,
What is the table contains Function module include program name
Regards,
Raja

Try this FUNCTION_INCLUDE_INFO to get the include number to which function module belongs to.From this u ll get only the particular include name.
or
if u need the all the includes used in the function group u have use INNER JOIN on TFDIR and D010INC table
<b>Select binclude into itab from trdir as a inner join d010inc as b on apname = bmaster where apname = fmodname.</b>
I hope this will help u.
Thanks & Regards
Santhosh
Message was edited by:
santhosh ds

What are the tables name in database belongs to AGIS?

Dear all:
I want to know what are the tables in database belongs to AGIS , such as transactions,AGIS "Intercompany Organization Assignments"?
My environment is : Oracle R12.1.3
Regards
Terry

Terry,
Please see these docs/links.
Advanced Global Intercompany Systems FAQ [ID 975235.1]
Troubleshooting AGIS Accounting [ID 813397.1]
How to Determine Data Populated in the Reference Columns in GL,AR,AP Interface tables for AGIS Invoices [ID 853296.1]
Oracle E-Business Suite Release 12.1 Release Content Documents [ID 561580.1]
eTRM Version 12.1.1
http://etrm.oracle.com/pls/et1211d9/etrm_search.search
Thanks,
Hussein

What r the tables used for this report.

hi all..
i am a fresher for ABAP. i need the help.
what r the tables used for this report.
Reports provide pending order details according to Material wise and customer wise for particular month.
thanks in advance
RK.Ashokkumar.

Hi Ashok,
this is easy to do.
Open Two SAP Screen with same user ID.
Run SQL trace using ST05 transaction.Open ST05 transaction in One and make
Trace on ,Run the report in another screen.
Once report run is over.End the trace process and click on display trace in same ST05 transaction.There is a click button on ST05 Transaction screen to start trace
process,End trace process and Display track process.
The SQL trace will give you all the table details which is used in that particular report.
You have not mentioned about the report name so I have suggested this way.
regards,nishant
Please reward if this helps

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

Similar Messages

Maybe you are looking for