Replacement for Pooled table: M_VMVME

Hi,
Can anyone suggest what is the replacement for the pooled table M_VMVME in ECC 6.0 version.
Thanks,
Sheetal

Sheetal
The replacement for this pooled table is SHP_IDX_GDRC.
Please check out Note: 570991 & 479457 or look at program ZBEY_COMPLETE_INBOUND_DELIVERY.
You may need to replace your cersion of the program with the new one.
Regards
Carl Cavendish-Davies
SAP Technical Manager

Similar Messages

Pooled table M_VMVME

Hi,
A pooled table 'M_VMVME' doesnot exist in ECC 6.0 version.
Can anyone suggest, what can be used as it's replacement?
Thanks,
Sheetal.

HI sheetal,
I am quite sure that SAP standard tables wont be deleted , when the version is upgraded.
May be the name might be changed.
I too try to find it out.
I don' t think that the table will be missing, it may be there with other name.
be in touch,
i might help you,if i can, b'cos we use 4.7 version.
bye now,

Data Maintenance For Pooled Table

Hi,
I have to make table maintenance for pooled table T052S , Can I make table maintenace , if I have access key, is it feaseable, as I have some requirement , which is to be done. or is there any other method by which user can maintain this table except through SPRO.
thanks
bobby

We're on ECC 5.0 here and this table already has a maintenance transaction defined - OBB9.
This is how SAP sets up maintenance for a lot of the config tables:
     Define a Maintenance View - e.g. V_T052S
     Define a Maintenance Dialog
     Define a transaction variant on SM30
A user can be given maintenance access for only OBB9

Alternative for Pooled table M_VMVLA in ECC 5 version

Hi,
Pooled table M_VMVLA in version 3.1i does not exist
in ECC 5.Can anyone tell me the alternative for this?
Pool/cluster M_VMVL in 3.1i version
Helpful answers will be rewarded
Thanks
Kiran

Hai Kiran
Check the following Code in program 'RVV50L21'.
the following Code is present in ECC 5.0
select * from shp_idx_gdsi where wadat in i_datum "470
 and vstel in i_vstel
 and route in i_route
 and vbeln eq vttp-vbeln.
simillar code in 3.1 version is
select * from m_vmvla where wadat in i_datum
 and vstel in i_vstel
 and route in i_route
 and vbeln eq vttp-vbeln.
Replacent table for m_vmvla is shp_idx_gdsi
Regards
Sreeni

Alternative for Pooled table M_VMVAC in ECC 5 version

Hi,
Pooled table M_VMVAC in version 3.1i does not exist
in ECC 5.Can anyone tell me the alternative for this?
Pool/cluster is M_VMVA in 3.1i version
Helpful answers will be rewarded
Thanks
Kiran

Check data base view V_VMVAC.
Regards
Sridhar

Replacement for "AP_CHECK_FORMATS" table in R12

Hi all,
what is the replacement for ap_check_formats in Oracle apps R12.
Is ap_selected_invoice_checks obsoleted in R12? If yes ,what is the replacement for ap_selected_invoice_checks.
Please suggest.

Hi,
You need to have metalink (my oracle support) credentials and a valid CSI to access this.
Metalink can be accessed from here.
https://support.oracle.com
Thanks

Cluster and pool tables

I make a join with a pool table the compiler writes
Für Pool-Tabellen, Cluster-Tabellen und Projektions-Views ist JOIN
for pool-Tables, Cluster-Tables and Projections-View is no JOIN allowed.
What can I do to read the data from the table a005 in join.
thanks.
Waseem

>
Ahmad Waseem wrote:
> What can I do to read the data from the table a005 in join.
> thanks.
> Waseem
Hello Waseem,
Ans is DONOT use JOIN. You have to use FOR ALL ENTRIES.
You can JOIN only transperant tables. This is where JOIN scores over FOR ALL ENTRIES
BR,
Suhas

About pool table??

what for pooled and cluster table used and how to create it???

I. Transparent tables (BKPF, VBAK, VBAP, KNA1, COEP)
· Allows secondary indexes (SE11->Display Table->Indexes)
· Can be buffered (SE11->Display Table->technical settings) Heavily updated tables should not be buffered.
II. Pool Tables (match codes, look up tables)
· Should be accessed via primary key or
· Should be buffered (SE11->Display Table->technical settings)
· No secondary indexes
· Select * is Ok because all columns retrieved anyway
III. Cluster Tables (BSEG,BSEC)
· Should be accessed via primary key - very fast retrieval otherwise very slow
· No secondary indexes
· Select * is Ok because all columns retrieved anyway. Performing an operation on multiple rows is more efficient than single row operations. Therefore you still want to select into an internal table. If many rows are being selected into the internal table, you might still like to retrieve specific columns to cut down on the memory required.
· Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported
· Can not be buffered
IV. Buffered Tables (includes both Transparent & Pool Tables)
While buffering database tables in program memory (SELECT into internal table) is generally a good idea for performance, it is not always necessary. Some tables are already buffered in memory. These are mostly configuration tables. If a table is already buffered, then a select statement against it is very fast. To determine if a table is buffered, choose the 'technical settings' soft button from the data dictionary display of a table (SE12). Pool tables should all be buffered.
"Major difference betwen Standard tables,Pooled tables and Cluster Tables?
1.A transparent table is a table that stores data directly. You can read these tables directly on the database from outside SAP with for instance an SQL statement.
2.Transparent table is a one to one relation table i.e. when you create one transparent table then exactly same table will create in data base and if is basically used to store transaction data.
3.A clustered and a pooled table cannot be read from outside SAP because certain data are clustered and pooled in one field.
4.One of the possible reasons is for instance that their content can be variable in length and build up. Database manipulations in Abap are limited as well.
5.But pool and cluster table is a many to one relationship table. This means many pool table store in a database table which is know as table pool.
6.All the pool table stored table in table pool does not need to have any foreign key relationship but in the case of cluster table it is must. And pool and cluster table is basically use to store application data.
7.Table pool can contain 10 to 1000 small pool table which has 10 to 100 records. But cluster table can contain very big but few (1 to 10) cluster table.
8.For pool and cluster table you can create secondary index and you can use select distinct, group for pool and cluster table. You can use native SQL statement for pool and cluster table.
9.A structure is a table without data. It is only filled by program logic at the moment it is needed starting from tables.
10.A View is a way of looking at the contents of tables. It only contains the combination of the tables at the basis and the way the data needs to be represented. You actually call directly upon the underlying tables.
'The table which store information about Structures and Tables are as follows:
DD02L - table properties
DD02T - table texts
DD03L - field properties
DD03T - field texts
Creating Pooled Tables/Cluster Tables Locate the document in its SAP Library structure
Procedure
 1. In the initial screen of the ABAP Dictionary select object type Table, enter a table name and choose This graphic is explained in the accompanying text Create.
 The field maintenance screen for the table is displayed. Table type Transparent table is set as default.
 2. Make the necessary entries in the Short description and Delivery class fields on the Attributes tab page. Then define the fields of the table.
 Proceed as when Structure link creating a transparent table. Save your entries.
 3. Choose Extras
 ® Change table category.
 A dialog box appears in which you have to select the table type Pooled table or Cluster table.
 4. Choose This graphic is explained in the accompanying textSelect.
 You return to the field maintenance screen for the table. Field Pool/cluster name is displayed on the Attributes tab page in addition to the standard fields.
 5. Enter the name of the
 table pool or table cluster to which you want to assign the pooled table or cluster table in field Pool/cluster name
 Note that the total key length of a pooled table may not exceed the key length of the associated table pool. The key of a cluster table must correspond to the key of the associated table cluster.
 6. Proceed as when creating a transparent table (see
 Structure link Creating Tables). Remember that you cannot create indexes for pooled or cluster tables.
Note
All the attributes of the Structure link technical settings can be maintained for pooled tables and cluster tables. Before you can access these attributes, however, you must convert the table to a transparent table.
Leaving content frame
creating pool/cluster tables
regards,
srinivas
*reward for useful answers*

Replacement for AR_SALES_TAX in R12?

Any one please tell me the replacement for the table AR_SALES _TAX in R12. I am working on
location_id,start_date, end_date, from_postal_code,to_postal_code,sales_tax_id columns .Any one please suggest the proper placement

Yes, it's still available in R12
http://etrm.oracle.com/pls/et1211d9/etrm_pnav.show_object?c_name=AR_SALES_TAX&c_owner=AR&c_type=TABLE
http://etrm.oracle.com/pls/et1211d9/etrm_pnav.show_object?c_name=AR_SALES_TAX&c_owner=APPS&c_type=SYNONYM
http://etrm.oracle.com/pls/et1211d9/etrm_fndnav.show_object?n_appid=222&n_tabid=52548&c_type=TABLE
http://etrm.oracle.com/pls/et1211d9/etrm_fndnav.show_object?n_appid=222&n_tabid=52548&c_type=TABLE
https://blogs.oracle.com/stevenChan/entry/ebs_data_model_1213
https://blogs.oracle.com/stevenChan/entry/ebs_seed_data_comparison_reports
Thanks,
Hussein

Replacement to MSEG table

HI,
The fields RSNUM and RSPOS are from the reservation table RESB. Based on these two fields I am fetching MBLNR MJAHR and ZEILE from MSEG table. But the select query is taking a lot of time. Could anyone please give me a replacement for MSEG Table .
Thanks,
Chinmaye

You should avoid reading MSEG if you don't know the document number (MBLNR). Check if you can get to that number in table EKBE via table EKET. See this site for an illustration of how the tables are connected:
http://www.erpgenie.com/sap/abap/tables_mm.htm#Purchasing%20Tables

Possible for Native SQL to read Pooled Tables?

Hi Experts,
Is it possible to run native SQL against SAP's internal Pool Table, the table that stores the many "Pooled Tables" across SAP? I realize that is much preferred to access the pooled table using Open SQL via ABAP functions, but that is not an option for me. I am writing native SQL against a copy of the SAP ECC underlying tables.
If it is possible, what is the technical name of the table?
Thanks,
Kevin

Hello Kevin,
quite a strange question. As you mentioned it before, the preffered way is to use open sql. The pooled tables are handled by the application server and so, they are not accessible by native sql.
Independently, consider about two things:
1.) The ABAP DDIC uses sometimes different sizes and field-lengths, so you should not read LSTR or LRAW fields with native sql.
2.) You have to be more patient about transaction handling and parameter setting via SQL, because your application server does not get any information about what you have done before.
Kind regards,
Hendrik

Module pool ---Problem in finding the line index for the table control

Hi Friends,
I am working in Module pool programming.
My requirement is when i select any record on the lead selection I need to find out the index of the line on which row i have selected.
Could any one please suggest me the proper solution how to get the line index for the table control in module pool programming.
Thanks
Satish Raju

Hi Raju,
Follow the steps
<li>U should take one variable in your internal table or in structure which is used for table control fields.
 DATA :BEGIN OF itab OCCURS 0 ,
 mark TYPE c ,
 matnr LIKE mara-matnr ,
 matkl LIKE mara-matkl,
 maktx LIKE makt-maktx,
 END OF itab .
 controls: tabc types tableview using screen 100.
<li>This mark variable should be given in Table control properties. follow the path
double click on the table control-->attributes .->select w/SelColumn and in that give itab-mark.
<li>Flow logic of the screen
 process before output.
 MODULE status_0100.
 LOOP AT itab with control tabc
 endloop.
 process after input.
 module cancel at exit-command.
 LOOP AT itab.
 MODULE read_table_control.
 ENDLOOP.
 MODULE user_command_0100.
<li>read_table_control module code
 MODULE read_table_control INPUT.
 MODIFY itab INDEX tabc-current_line."this will update the itab table
 "mark field with 'X ' whatever we
 "have selected on table control
 ENDMODULE.
<li>If you want to Delete some of the records from Table control follow this code u2026Create one pushbutton and give Fucnction code to that and write below code
 CASE okcode.
 WHEN 'DELETE'.
 LOOP AT itab WHERE mark = 'X'.
 DELETE itab.
 ENDLOOP.
 ENDCASE.
I hope that it helps you.
Thanks
Venkat.O

Why Inner join or Outer join is not used for Pool or Cluster tables ?

Hi SAP-ABAP Experts .
With Due Regards .
May u explain me why Inner join or Outer join is not useful for Pool or Cluster tables ?
because peoples advised not use Joins for Pool and Cluster tables , What harm will take place , If we do this ?
Best Regards to all : Rajneesh

Both Pooled and Cluster Tables are stored as tables within the database. Only the structures of the two table types which represent a single logical view of the data are defined within the ABAP/4 Data Dictionary. The data is actually stored in bulk storage in a different structure. These tables are commonly loaded into memory (i.e., 'buffered') due to the fact they are typically used for storing internal control information and other types of data with little or no external (business) relevance.
Pooled and cluster tables are usually used only by SAP and not used by customers, probably because of the proprietary format of these tables within the database and because of technical restrictions placed upon their use within ABAP/4 programs. On a pooled or cluster table:
Secondary indexes cannot be created.
You cannot use the ABAP/4 constructs select distinct or group by.
You cannot use native SQL.
You cannot specify field names after the order by clause. order by primary key is the only permitted variation.
I hope it helps.
Best Regards,
Vibha
Please mark all the helpful answers

Replacement of i_wrap table in oops for FM 'ALVDG_WORD_WRAP' ?

Replacement of i_wrap table in oops?
**This declaration is not allowed in oops?
how to replace i_wrap declaration, occus 0**
**if i convert into types....i am unable to pass in below function module. **
DATa: BEGIN OF I_WRAP OCCURS 0,
 text(60) type c,
 END OF I_WRAP.
 CALL FUNCTION 'ALVDG_WORD_WRAP'
 EXPORTING
 textline = w_text1
 DELIMITER = ' '
 OUTPUTLEN = 35
* IMPORTING
* OUT_LINE1 =
* OUT_LINE2 =
* OUT_LINE3 =
 TABLES
 OUT_LINES = I_WRAP
* EXCEPTIONS
* OUTPUTLEN_TOO_LARGE = 1
* OTHERS = 2
 BREAK-POINT.
 IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
pls suggest.

Hello Anee
Quite simple:
"DATa: BEGIN OF I_WRAP OCCURS 0,
" text(60) type c,
" END OF I_WRAP.
TYPES: BEGIN OF ty_s_wrap.
TYPES: text(60) TYPE c.
TYPES: END OF ty_s_wrap.
TYPES: ty_t_wrap TYPE STANDARD TABLE OF ty_s_wrap
 WITH DEFAULT KEY.
DATA: lt_wrap TYPE ty_t_wrap.
 CALL FUNCTION 'ALVDG_WORD_WRAP'
 EXPORTING
 textline = w_text1
 DELIMITER = ' '
 OUTPUTLEN = 35
* IMPORTING
* OUT_LINE1 =
* OUT_LINE2 =
* OUT_LINE3 =
 TABLES
 OUT_LINES = lt_wrap
* EXCEPTIONS
* OUTPUTLEN_TOO_LARGE = 1
* OTHERS = 2
Regards
Uwe

Creating view to get first row for each table !!

I am having tables(more than 10) which are related using foreign key and primary key relationship.
Example:
Table1:
T1Prim T1Col1 T1Col2
Table2
T2For T2Prim T2Col1 T2Col2 T2Col3
(here T2For will have value same as T1Prim and in my design it has same column name i.e. T1Prim)
Table3
T3For T3Prim T3Col1 T3Col2 T3Col3
(here T3For will have value same as T2Prim)
and so on.
The data in the tables is like For table1 there will be one record, for table2 there will be one record and for table 3 there are more than one records.
Can i view either the first record for each of them or all records from each of them by writing the following view.
I have written a view like this:
Create or replace view test (T1Prim,T1Col1, T1Col2,T2Prim,T2Col1 T2Col2, T2Col3, T3Prim,T3Col1, T3Col2, T3Col3)
As
Select
Table1.T1Prim,
Table1.T1Col1,
Table1.T1Col2,
Table2.T2Prim,
Table2.T2Col1,
Table2.T2Col2,
Table2.T2Col3,
Table3.T3Prim,
Table3.T3Col1,
Table3.T3Col2,
Table3.T3Col3
From
Table1,
Table2,
Table3
where
Table1.Prim = Table2.For
and Table2.Prim = Table3.For
When i ran the select statement on the view I am not getting any data. Whereas there is data when select is ran on individual table.
Can someone please tell me where i am goofing.
Thanks in the anticipation that i will get some hint to solve this.
Eagerly waiting for reply.
Thanks !!

I mean use a collection :
Collection Methods
A collection method is a built-in function or procedure that operates on collections and is called using dot notation. The methods EXISTS, COUNT, LIMIT, FIRST, LAST, PRIOR, NEXT, EXTEND, TRIM, and DELETE help generalize code, make collections easier to use, and make your applications easier to maintain.
EXISTS, COUNT, LIMIT, FIRST, LAST, PRIOR, and NEXT are functions, which appear as part of an expression. EXTEND, TRIM, and DELETE are procedures, which appear as a statement. EXISTS, PRIOR, NEXT, TRIM, EXTEND, and DELETE take integer parameters. EXISTS, PRIOR, NEXT, and DELETE can also take VARCHAR2 parameters for associative arrays with string keys. EXTEND and TRIM cannot be used with index-by tables.
For more information, see "Using Collection Methods".
Syntax
Text description of the illustration collection_method_call.gif
Keyword and Parameter Description
collection_name
This identifies an index-by table, nested table, or varray previously declared within the current scope.
COUNT
COUNT returns the number of elements that a collection currently contains, which is useful because the current size of a collection is not always known. You can use COUNT wherever an integer expression is allowed.
For varrays, COUNT always equals LAST. For nested tables, normally, COUNT equals LAST. But, if you delete elements from the middle of a nested table, COUNT is smaller than LAST.
DELETE
This procedure has three forms. DELETE removes all elements from a collection. DELETE(n) removes the nth element from an index-by table or nested table. If n is null, DELETE(n) does nothing. DELETE(m,n) removes all elements in the range m..n from an index-by table or nested table. If m is larger than n or if m or n is null, DELETE(m,n) does nothing.
EXISTS
EXISTS(n) returns TRUE if the nth element in a collection exists. Otherwise, EXISTS(n) returns FALSE. Mainly, you use EXISTS with DELETE to maintain sparse nested tables. You can also use EXISTS to avoid raising an exception when you reference a nonexistent element. When passed an out-of-range subscript, EXISTS returns FALSE instead of raising SUBSCRIPT_OUTSIDE_LIMIT.
EXTEND
This procedure has three forms. EXTEND appends one null element to a collection. EXTEND(n) appends n null elements to a collection. EXTEND(n,i) appends n copies of the ith element to a collection. EXTEND operates on the internal size of a collection. So, if EXTEND encounters deleted elements, it includes them in its tally. You cannot use EXTEND with index-by tables.
FIRST, LAST
FIRST and LAST return the first and last (smallest and largest) subscript values in a collection. The subscript values are usually integers, but can also be strings for associative arrays. If the collection is empty, FIRST and LAST return NULL. If the collection contains only one element, FIRST and LAST return the same subscript value.
For varrays, FIRST always returns 1 and LAST always equals COUNT. For nested tables, normally, LAST equals COUNT. But, if you delete elements from the middle of a nested table, LAST is larger than COUNT.
index
This is an expression that must yield (or convert implicitly to) an integer in most cases, or a string for an associative array declared with string keys.
LIMIT
For nested tables, which have no maximum size, LIMIT returns NULL. For varrays, LIMIT returns the maximum number of elements that a varray can contain (which you must specify in its type definition).
NEXT, PRIOR
PRIOR(n) returns the subscript that precedes index n in a collection. NEXT(n) returns the subscript that succeeds index n. If n has no predecessor, PRIOR(n) returns NULL. Likewise, if n has no successor, NEXT(n) returns NULL.
TRIM
This procedure has two forms. TRIM removes one element from the end of a collection. TRIM(n) removes n elements from the end of a collection. If n is greater than COUNT, TRIM(n) raises SUBSCRIPT_BEYOND_COUNT. You cannot use TRIM with index-by tables.
TRIM operates on the internal size of a collection. So, if TRIM encounters deleted elements, it includes them in its tally.
Usage Notes
You cannot use collection methods in a SQL statement. If you try, you get a compilation error.
Only EXISTS can be applied to atomically null collections. If you apply another method to such collections, PL/SQL raises COLLECTION_IS_NULL.
You can use PRIOR or NEXT to traverse collections indexed by any series of subscripts. For example, you can use PRIOR or NEXT to traverse a nested table from which some elements have been deleted.
EXTEND operates on the internal size of a collection, which includes deleted elements. You cannot use EXTEND to initialize an atomically null collection. Also, if you impose the NOT NULL constraint on a TABLE or VARRAY type, you cannot apply the first two forms of EXTEND to collections of that type.
If an element to be deleted does not exist, DELETE simply skips it; no exception is raised. Varrays are dense, so you cannot delete their individual elements.
PL/SQL keeps placeholders for deleted elements. So, you can replace a deleted element simply by assigning it a new value. However, PL/SQL does not keep placeholders for trimmed elements.
The amount of memory allocated to a nested table can increase or decrease dynamically. As you delete elements, memory is freed page by page. If you delete the entire table, all the memory is freed.
In general, do not depend on the interaction between TRIM and DELETE. It is better to treat nested tables like fixed-size arrays and use only DELETE, or to treat them like stacks and use only TRIM and EXTEND.
Within a subprogram, a collection parameter assumes the properties of the argument bound to it. So, you can apply methods FIRST, LAST, COUNT, and so on to such parameters. For varray parameters, the value of LIMIT is always derived from the parameter type definition, regardless of the parameter mode.
Examples
In the following example, you use NEXT to traverse a nested table from which some elements have been deleted:
i := courses.FIRST; -- get subscript of first element
WHILE i IS NOT NULL LOOP
-- do something with courses(i)
i := courses.NEXT(i); -- get subscript of next element
END LOOP;
In the following example, PL/SQL executes the assignment statement only if element i exists:
IF courses.EXISTS(i) THEN
courses(i) := new_course;
END IF;
The next example shows that you can use FIRST and LAST to specify the lower and upper bounds of a loop range provided each element in that range exists:
FOR i IN courses.FIRST..courses.LAST LOOP ...
In the following example, you delete elements 2 through 5 from a nested table:
courses.DELETE(2, 5);
In the final example, you use LIMIT to determine if you can add 20 more elements to varray projects:
IF (projects.COUNT + 20) < projects.LIMIT THEN
-- add 20 more elements
Related Topics
Collections, Functions, Procedures
http://download-west.oracle.com/docs/cd/B10501_01/appdev.920/a96624/13_elems7.htm#33054
Joel P�rez

Replacement for Pooled table: M_VMVME

Similar Messages

Maybe you are looking for