What is the difference between RT(Result table)& CRT(Cumilative result tabl

what is the difference between RT(Result table)& CRT(Cumilative result table)

Hi,
RT Contains all the results of the payroll of the current
period, i.e, ur current months Basic, HRA, CLA etc. Where as in CRT contains
all the cummulated amount of the Basic, HRA, CLA, i.e, lets us assume that
ur basic per month is 5000/- then in RT table u will have Basic amount for
the month of September will be 5000/- and in CRT for the month of September
u will have Basic amount as 30,000/- ie, 5000 * 7. And also CRT has Yearly
amount and also Current month amount. you can check this with the Tcode
pc00_m40_clsrt
AWARD POINTS IF USEFUL

Similar Messages

What is the difference between payment_method_code,payment_method_lookup_code in ap_checks_all table ?

Hi All,
Could you explain me what is the difference between payment_method_code & payment_method_lookup_code in ap_checks_all table.
Is both the column store same values ?
Regards,
Uva

Hi Prathima,
In tech lingo:
Payment_num is the same as AP_INVOICE_PAYMENTS_ALL.payment num.
Check_number is same as check_number in AP_CHECKS_ALL -> which also has checkrun_name used in payment batch You can get to AP_CHECKS_ALL by using check_id in AP_INVOICE_PAYMENTS_ALL
Raman.

Hi guru's what is the difference between table and temlate in smartforms

hi guru's what is the difference between table and temlate in smartforms

Hi Vasu,
Template is used for proper allignment of data which table is used for displaying multiple data.
We can say Template is for static data and Table is for dynamic data.
Suppose we have a requirement in which we have to allign the customer address in such a way as shown below:-
Name- Vasu Company- WIPRO Location- Chennai
Desig- S/W Native - Mumbai
Then for proper allighnment we can create a template and split that into 3 columns and 2 rows and create text elements for each cell display a proper allighned data at the output.
When we include a template inside a loop it gives the same property as a table.
When we have mutiple data which is to be extended to the next page like when we display all employee details in a company we use table.
Table has 3 sections , HEADER, ITEM ,FOOTER
The header secntion will be executed once and it will loop at the item level. at the end footer will be executed.
Hope this gives u some idea..
<b>Please reward if useful</b>
Regards,
sunil kairam.

What is the difference between infocube and fact table?

hi bw gurus,
what is the difference between infocube and fact table?
thanks in advance
bye

Fact table contains only KeyFigures and foreign keys of dim ids.
Infocube conatin fact table sorrounded by dimension tables.dimension table contain primary keys of dim ids and SIDs which link to master data.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/6ce7b0a4-0b01-0010-52ac-a6e813c35a84

What is the difference between standard,sorted and hash table

<b>can anyone say what is the difference between standard,sorted and hash tabl</b>

Hi,
Standard Tables:
Standard tables have a linear index. You can access them using either the index or the key. If you use the key, the response time is in linear relationship to the number of table entries. The key of a standard table is always non-unique, and you may not include any specification for the uniqueness in the table definition.
This table type is particularly appropriate if you want to address individual table entries using the index. This is the quickest way to access table entries. To fill a standard table, append lines using the (APPEND) statement. You should read, modify and delete lines by referring to the index (INDEX option with the relevant ABAP command). The response time for accessing a standard table is in linear relation to the number of table entries. If you need to use key access, standard tables are appropriate if you can fill and process the table in separate steps. For example, you can fill a standard table by appending records and then sort it. If you then use key access with the binary search option (BINARY), the response time is in logarithmic relation to
the number of table entries.
Sorted Tables:
Sorted tables are always saved correctly sorted by key. They also have a linear key, and, like standard tables, you can access them using either the table index or the key. When you use the key, the response time is in logarithmic relationship to the number of table entries, since the system uses a binary search. The key of a sorted table can be either unique, or non-unique, and you must specify either UNIQUE or NON-UNIQUE in the table definition. Standard tables and sorted tables both belong to the generic group index tables.
This table type is particularly suitable if you want the table to be sorted while you are still adding entries to it. You fill the table using the (INSERT) statement, according to the sort sequence defined in the table key. Table entries that do not fit are recognised before they are inserted. The response time for access using the key is in logarithmic relation to the number of
table entries, since the system automatically uses a binary search. Sorted tables are appropriate for partially sequential processing in a LOOP, as long as the WHERE condition contains the beginning of the table key.
Hashed Tables:
Hashes tables have no internal linear index. You can only access hashed tables by specifying the key. The response time is constant, regardless of the number of table entries, since the search uses a hash algorithm. The key of a hashed table must be unique, and you must specify UNIQUE in the table definition.
This table type is particularly suitable if you want mainly to use key access for table entries. You cannot access hashed tables using the index. When you use key access, the response time remains constant, regardless of the number of table entries. As with database tables, the key of a hashed table is always unique. Hashed tables are therefore a useful way of constructing and
using internal tables that are similar to database tables.
Regards,
Ferry Lianto

What is the difference between Table & Tablespace Fragmentation

What is the difference between Table Fragmentation & Tablespace Fragmentation.
What causes Table Fragmentation and what cause Tablespace Fragmentation.
How can we avoid Table Fragmentation & Tablespace Fragmentation.
How can we fix already Fragmented Tables & Fragmented Tablespaces
Thanks
Naveen

Unless you are using an exceptionally old version of Oracle or are still using dictionary managed tablespaces or are using some interesting definitions of "fragmentation", fragmentation is practically impossible in Oracle.
Justin

What is the difference between straucture & table

what is the difference between straucture & table

Hi,
Tables
Represent the Database Tables where data actually resides.
Tables can be defined independently of the database in the ABAP Dictionary.
The fields of the table are defined with their (database-independent) ABAP/4 data types and lengths.
Structures
Are record declarations that do not correspond to a Database Table.
Just like user-defined data type.
Defined like a table and can then be addressed from ABAP/4 programs.
Structures contain data only during the runtime of a program.
In this link, you can find some useful coding samples.
http://www.sapdevelopment.co.uk/java/jco/jcohome.htm
http://www.henrikfrank.dk/abapexamples/Java/sapjava_getcompanycode_list.htm
Following are the weblogs about JCO
/people/gregor.wolf3/blog/2004/09/23/from-function-module-to-jco-application--part-1-of-3
/people/gregor.wolf3/blog/2004/09/24/from-function-module-to-jco-application--part-2-of-3
/people/gregor.wolf3/blog/2004/09/25/from-function-module-to-jco-application--part-3-of-3
/people/gregor.wolf3/blog/2004/08/26/setup-and-test-sap-java-connector-outbound-connection
For Tables and Structures refer this.
http://help.sap.com/saphelp_40b/helpdata/en/4f/991f82446d11d189700000e8322d00/applet.htm
For RFC related information,check this.
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://www.sap-img.com/abap-function.htm

What is the difference between READ TABLE ITAB WITH KEY and TABLE KEY

Hi Experts,
what is the difference between
READ TABLE <ITAB> WITH KEY <K1> = <C1>
<Kn> = <Cn> .
and
READ TABLE <ITAB> WITH TABLE KEY <K1> = <C1>
<Kn> = <Cn> .
Thanks
Akash.

Hi akashdeep,
Nice question. I also tried to find out, but no much success. My opinion is that for practical purposes there is no difference.
It may have difference in case of searching, especially sorted tables. (binary search or normal linear search).
Case1: If our table is sorted table with defined key fields, and we give WITH TABLE KEY, then faster binary search is used.
Case2 : If our table is sorted table with defined key fields, and we give WITH KEY, (and no field contained in the keys), then normal linear search is used.
regards,
amit m.

What is the differences between Transparent,Pooled and Cluster tables?

Hello all,
What is Pool table?What is the differences between Transparent,Pooled and Cluster tables?
Regards!
Purna

Transparent table:
Tables can be defined independently of the database in the ABAP Dictionary. The fields of the table are defined together with their (database-independent) data types and lengths.
A table definition in the ABAP Dictionary has the following components:
Table fields: The field names and the data types of the fields contained in the table are defined here.
Foreign keys: The foreign keys define the relationships between this table and other tables.
Technical settings: The technical settings define how the table is created on the database.
Indexes: Indexes can be defined for the table to speed up data selection from the table.
There are three categories of database tables in the ABAP Dictionary.
A physical table definition is created in the database for the table definition stored in the ABAP Dictionary for transparent tables when the table is activated. The table definition is translated from the ABAP Dictionary to a definition of the particular database.
On the other hand, pooled tables and cluster tables are not created in the database. The data of these tables is stored in the corresponding table pool or table cluster. It is not necessary to create indexes and technical settings for pooled and cluster tables.
Pooled table
Pooled tables can be used to store control data (e.g. screen sequences, program parameters or temporary data). Several pooled tables can be combined to form a table pool. The table pool corresponds to a physical table on the database in which all the records of the allocated pooled tables are stored.
Cluster table
Cluster tables contain continuous text, for example, documentation. Several cluster tables can be combined to form a table cluster. Several logical lines of different tables are combined to form a physical record in this table type. This permits object-by-object storage or object-by-object access. In order to combine tables in clusters, at least parts of the keys must agree. Several cluster tables are stored in one corresponding table on the database.
Regds,
Manohar

What is the difference between exists and in

hi all
if i have these queries
1- select ename from emp where ename in ( select ename from emp where empno=10)
and
2- select ename from emp where exists ( select ename from emp where empno=10)
what is the difference between exists and in is that only when i use in i have to bring the field name or what.... i mean in a complex SQL queries is it will give the same answer
Thanks

You get two entirely different result sets that may be the same. Haah! What do I mean by that.
SQL> select table_name from user_tables;
TABLE_NAME
BAR
FOO
2 rows selected.
SQL> select table_name from user_tables where table_name in (select table_name from user_tables where table_name = 'FOO');
TABLE_NAME
FOO
1 row selected.
SQL> select table_name from user_tables where exists(select table_name from user_tables where table_name = 'FOO');
TABLE_NAME
BAR
FOO
2 rows selected.So, why is this? the WHERE EXISTS means 'if the next is true', much like where 1=1 being always true and 1=2 being always false. In this case, where exists could be TRUE or FALSE, depending on the subquery.
WHERE EXISTS can be useful for something like testing if we have data, without actually having to return columns.
So, if you want to see if an employee exists you might say
SELECT 1 FROM DUAL WHERE EXISTS( select * from emp where empid = 10);
If there is a row in emp for empid=10, then you get back 1 from dual;
This is what I call an 'optimistic' lookup because the WHERE EXISTS ends as soon as there is a hit. It does not care how many - only that at least one exists. It is optimistic because it will continue processing the table lookup until either it hits or reaches the end of the table - for a non-indexed query.

What is the difference between   nvl(sum (field), 0) & sum(nvl (field,0)) ?

What is the difference between nvl(sum (field), 0) & sum(nvl (field,0)) ?
For the below table data i don't see any different in results
CREATE TABLE FRUITS
TYPE VARCHAR2(10 BYTE),
VARIETY VARCHAR2(10 BYTE),
PRICE NUMBER(18,2)
TYPE     VARIETY          PRICE
apple     gala          2.79
apple     fuji          0.24
apple     limbertwig     2.87
orange     valencia     3.59
orange     navel          9.36
pear     bradford     7.77
pear     bartlett     7.77
cherry     bing          2.55
cherry     chelan          6.33
pear     bradford
     navel          6.39
select variety, nvl(sum(price),0)
from fruits
group by variety;
VARIETY     NVL(SUM(PRICE),0)
limbertwig     2.87
bartlett     7.77
bing     2.55
marathon     0
gala     2.79
fuji     0.24
navel     15.75
bradford     7.77
chelan     6.33
valencia     3.59
select variety, sum(nvl(price,0))
from fruits
group by variety;
VARIETY     SUM(NVL(PRICE,0))
limbertwig     2.87
bartlett     7.77
bing     2.55
marathon     0
gala     2.79
fuji     0.24
navel     15.75
bradford     7.77
chelan     6.33
valencia     3.59
no difference in output.
what is the difference?
Thanks in advance

Do you see the difference now?
PRAZY@11gR1> create table testing(field number);
Table created.
Elapsed: 00:00:00.10
PRAZY@11gR1> insert into testing select null from dual connect by level<=5;
5 rows created.
Elapsed: 00:00:00.00
PRAZY@11gR1> select * from testing;
     FIELD
Elapsed: 00:00:00.01
PRAZY@11gR1> select sum(nvl(field,1)) from testing;
SUM(NVL(FIELD,1))
                5
Elapsed: 00:00:00.00
PRAZY@11gR1> select nvl(sum(field),1) from testing;
NVL(SUM(FIELD),1)
                1
Elapsed: 00:00:00.00In the former, we are substituting 1 to null value and summing-up. hence we got 5. in the later, we are summing-up the null, which is null and substituting 1 if the result is null. so we got 1.
Regards,
Prazy

Hi gurus what is the difference between EDI & ALE.

hi gurus what is the difference between EDI & ALE.

HI,
EDI is a technique used to communicate business and information transactions between computer systems of different companies and organizations. These transactions include such documents as purchase orders, invoices, inquiries, planning, acknowledgements, pricing, order status, scheduling, test results, shipping and receiving, payments, and financial reporting
EDI Introduction
The EDI interface is intended to connect an EDI subsystem with the SAP system. EDI subsystems perform the following tasks related to EDI processing:
1·Conversion of data·
2.Message and Interchange Handling.
3.Communication·
4.Administration of partner profiles·
5.Monitoring of processing
From the SAP side, the EDI interface is based on IDoc technology, which is independent of EDI standards. All data is transferred in files between the R/3 System and the EDI subsystem. Synchronous RFC (Remote Function Call) is implemented to define the time of transfer for a file between the two systems.
EDI u2013 Benefits
Improves data accuracy u2013
With EDI business can eliminate the need to re-enter data from paper documents and thus prevent potential data entry errors. Additionally, the cost of processing an electronic requisition is estimated to be one-tenth the cost of handling its paper equivalent
Lowers personnel costs-
EDI can help companies reduce the need for personnel involved in orders and accounting processing. Speeds up information exchange- EDI systems can shorten the lead time between receipt and fulfillment of orders. When scheduling information is transmitted with ordering data, companies can plan production more accurately and thus reduce stock investments.
Reduces technical complexity related to data interchange u2013
With EDI companies use standardized data formats to exchange documents. EDI allows companies using different business applications and systems to achieve computer-to-computer electronic exchange of business documents.
Application Link Enabling
ALE Objectives u2013 ALE incorporates controlled exchange of data messages ensuring data consistency across loosely coupled applications. ALE comprises of three layers. Application Services Distribution Services Communication Services
Basic principle of ALE is to provide a distributed and fully integrated R/3 system. Each application is self-sufficient. The use of self-sufficient system implies a certain measure of data redundancy.Hence data has to be both distributed and synchronized.
General Steps Involved in Configuring EDI u2013 ALE Interface
- Maintaining the Condition Table
- Maintaining the Access Sequences
- Maintaining the Output types
- Assign output types to the partner functions
- Maintain output determination procedure
- Assign output determination Procedures

What is the difference between tkprof and explainplan

Hi,
what is the difference between tkprof and explainplan.

Execution Plans and the EXPLAIN PLAN Statement
Before the database server can execute a SQL statement, Oracle must first parse the statement and develop an execution plan. The execution plan is a task list of sorts that decomposes a potentially complex SQL operation into a series of basic data access operations. For example, a query against the dept table might have an execution plan that consists of an index lookup on the deptno index, followed by a table access by ROWID.
The EXPLAIN PLAN statement allows you to submit a SQL statement to Oracle and have the database prepare the execution plan for the statement without actually executing it. The execution plan is made available to you in the form of rows inserted into a special table called a plan table. You may query the rows in the plan table using ordinary SELECT statements in order to see the steps of the execution plan for the statement you explained. You may keep multiple execution plans in the plan table by assigning each a unique statement_id. Or you may choose to delete the rows from the plan table after you are finished looking at the execution plan. You can also roll back an EXPLAIN PLAN statement in order to remove the execution plan from the plan table.
The EXPLAIN PLAN statement runs very quickly, even if the statement being explained is a query that might run for hours. This is because the statement is simply parsed and its execution plan saved into the plan table. The actual statement is never executed by EXPLAIN PLAN. Along these same lines, if the statement being explained includes bind variables, the variables never need to actually be bound. The values that would be bound are not relevant since the statement is not actually executed.
You don’t need any special system privileges in order to use the EXPLAIN PLAN statement. However, you do need to have INSERT privileges on the plan table, and you must have sufficient privileges to execute the statement you are trying to explain. The one difference is that in order to explain a statement that involves views, you must have privileges on all of the tables that make up the view. If you don’t, you’ll get an “ORA-01039: insufficient privileges on underlying objects of the view” error.
The columns that make up the plan table are as follows:
Name Null? Type
STATEMENT_ID VARCHAR2(30)
TIMESTAMP DATE
REMARKS VARCHAR2(80)
OPERATION VARCHAR2(30)
OPTIONS VARCHAR2(30)
OBJECT_NODE VARCHAR2(128)
OBJECT_OWNER VARCHAR2(30)
OBJECT_NAME VARCHAR2(30)
OBJECT_INSTANCE NUMBER(38)
OBJECT_TYPE VARCHAR2(30)
OPTIMIZER VARCHAR2(255)
SEARCH_COLUMNS NUMBER
ID NUMBER(38)
PARENT_ID NUMBER(38)
POSITION NUMBER(38)
COST NUMBER(38)
CARDINALITY NUMBER(38)
BYTES NUMBER(38)
OTHER_TAG VARCHAR2(255)
PARTITION_START VARCHAR2(255)
PARTITION_STOP VARCHAR2(255)
PARTITION_ID NUMBER(38)
OTHER LONG
DISTRIBUTION VARCHAR2(30)
There are other ways to view execution plans besides issuing the EXPLAIN PLAN statement and querying the plan table. SQL*Plus can automatically display an execution plan after each statement is executed. Also, there are many GUI tools available that allow you to click on a SQL statement in the shared pool and view its execution plan. In addition, TKPROF can optionally include execution plans in its reports as well.
Trace Files and the TKPROF Utility
TKPROF is a utility that you invoke at the operating system level in order to analyze SQL trace files and generate reports that present the trace information in a readable form. Although the details of how you invoke TKPROF vary from one platform to the next, Oracle Corporation provides TKPROF with all releases of the database and the basic functionality is the same on all platforms.
The term trace file may be a bit confusing. More recent releases of the database offer a product called Oracle Trace Collection Services. Also, Net8 is capable of generating trace files. SQL trace files are entirely different. SQL trace is a facility that you enable or disable for individual database sessions or for the entire instance as a whole. When SQL trace is enabled for a database session, the Oracle server process handling that session writes detailed information about all database calls and operations to a trace file. Special database events may be set in order to cause Oracle to write even more specific information—such as the values of bind variables—into the trace file.
SQL trace files are text files that, strictly speaking, are human readable. However, they are extremely verbose, repetitive, and cryptic. For example, if an application opens a cursor and fetches 1000 rows from the cursor one row at a time, there will be over 1000 separate entries in the trace file.
TKPROF is a program that you invoke at the operating system command prompt in order to reformat the trace file into a format that is much easier to comprehend. Each SQL statement is displayed in the report, along with counts of how many times it was parsed, executed, and fetched. CPU time, elapsed time, logical reads, physical reads, and rows processed are also reported, along with information about recursion level and misses in the library cache. TKPROF can also optionally include the execution plan for each SQL statement in the report, along with counts of how many rows were processed at each step of the execution plan.
The SQL statements can be listed in a TKPROF report in the order of how much resource they used, if desired. Also, recursive SQL statements issued by the SYS user to manage the data dictionary can be included or excluded, and TKPROF can write SQL statements from the traced session into a spool file.
How EXPLAIN PLAN and TKPROF Aid in the Application Tuning Process
EXPLAIN PLAN and TKPROF are valuable tools in the tuning process. Tuning at the application level typically yields the most dramatic results, and these two tools can help with the tuning in many different ways.
EXPLAIN PLAN and TKPROF allow you to proactively tune an application while it is in development. It is relatively easy to enable SQL trace, run an application in a test environment, run TKPROF on the trace file, and review the output to determine if application or schema changes are called for. EXPLAIN PLAN is handy for evaluating individual SQL statements.
By reviewing execution plans, you can also validate the scalability of an application. If the database operations are dependent upon full table scans of tables that could grow quite large, then there may be scalability problems ahead. On the other hand, if large tables are accessed via selective indexes, then scalability may not be a problem.
EXPLAIN PLAN and TKPROF may also be used in an existing production environment in order to zero in on resource intensive operations and get insights into how the code may be optimized. TKPROF can further be used to quantify the resources required by specific database operations or application functions.
EXPLAIN PLAN is also handy for estimating resource requirements in advance. Suppose you have an ad hoc reporting request against a very large database. Running queries through EXPLAIN PLAN will let you determine in advance if the queries are feasible or if they will be resource intensive and will take unacceptably long to run.

What is the difference between the two update statements

Hi Everyone
Along with the emp table in scott kindly insert the to ins statement into emp.
Insert into EMP
(EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO)
Values
(8000, 'JAMES', 'CLERK', 7698, sysdate,
1000, 10, 30);
Insert into EMP
(EMPNO, ENAME, JOB, MGR, HIREDATE, SAL, COMM, DEPTNO)
Values
(8001, 'JAMES', 'CLERK', 7698, sysdate,
1000, 10, 30);
Consider the below two update statements.
1) update emp a
set ename=(select loc
from dept b
where a.deptno=b.deptno)
where exists(select loc
from dept b
where a.deptno=b.deptno)
2) update emp a
set ename=(select loc
from dept b
where a.deptno=b.deptno)
What is the difference between the 1st and 2nd update statement? what is the use of exists clause in the first update statement ? Can u suggest in what case will the two update statements provide different results.
Thanks in advance

Second one updates all records in emp. If there is no record in dept then ename will be updated to null.
The first one only updates records in emp where a record in dept exists. It does not matter whether loc is non-null in dept or not. In an EXISTS query it doesn't matter if you do SELECT *, SELECT LOC, SELECT 1, SELECT NULL - Oracle just checks for existence.
So most often an update like the first one is meant to improve performance by only updating those emp records that are needed. Usually that is a good idea.
For this very specific case where all employees do belong to a department, all records in emp will be updated anyway, so for this specific case it actually makes worse performance because it does work to make an unnecessary check.
Normally the EXISTS query is good for performance, but always figure out if they are needed first ;-)

What is the difference between Execute SQL Task and OLE DB Command

Besides the obvious, Execute SQL Task being used in Control Flow, and
OLE DB Command being used in Data Flow what is the difference between the two? Is one supposed to use
Execute SQL Task to produce a result set that then gets handed over to
Data Flow and OLE DB Command ? Everything that I have seen on
OLE DB Command is pretty much execution of a Stored Procedure with ? parameters. It seems as though I got to a point where I had to perform my data edits pretty much entirely in a Stored Procedure executed by
OLE DB Command rather than trying to use the SSIS GUI for everything. I didn't really see in any of my Google searches out there that simply used
OLE DB Command as a straight parameterized SQL against tables for editing and cleansing purposes and handling returns back from SQL Server for COUNT(*), etc..
I know I have posted multiple forums out there regarding this issue but I cannot seem to get a straight answer and some solid direction. So for now, my
Execute SQL Task gives me my editable result set and then control is handed off to
Data Flow and ultimately to my Stored Procedure executed by an
OLE DB Command which pretty much does the chunking for me and performs my data edits and handles my record anomalies through SQL Server Table data stores accordingly or sets flags accordingly if the data passes.
I welcome your thoughts and Thanks for your review and Thanks in advance for any replies and direction that anyone might provide.

Hi ITBobbyP,
OLE DB Command will always process data row by row, whereas Execute SQL task if you call a Stored Procedure it can process data in bulk. As you said, the biggest difference is that Execute SQL Task being used in Control Flow, and OLE DB Command being
used in Data Flow. They are used in different places.
Using Execute SQL Task, we can save the rowset returned from a query into a variable. The Execute SQL task can be used in combination with the Foreach Loop and For Loop containers to run multiple SQL statements. These containers implement repeating control
flows in a package and they can run the Execute SQL task repeatedly. For example, using the Foreach Loop container, a package can enumerate files in a folder and run an Execute SQL task repeatedly to execute the SQL statement stored in each file. I think this
is a big advantage for Execute SQL Task.
As to OLE DB Command, we can easily run an SQL statement for each row transformation in a data flow, then directly insert the outputs to a destination.
To sum up, there are many difference between those two components. We should make better choice based on our actual requirement.
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

What is the difference between RT(Result table)& CRT(Cumilative result tabl

Similar Messages

Maybe you are looking for