Table Parameters are obsolete in ECC 6.0

hello All,
I have created a function module in ECC6.0 and I need an internal table as a parameter but SAP will not allow it to be created as a tables parameter only as a changing parameter. How do you do this as a changing parameter. I am using structure type MMPUR_TEXTLINES.
Thanks

Use tables tab instead of changing.
then use
MMPUR_TEXTLINES LIKE MMPUR_T_TEXTLINES
a®

Similar Messages

New in NW04s: FL069 TABLES parameters are obsolete (in function modules)

Can somebody explain what is the fundamental reason for this behaviour in NW04s?
In Netweaver 2004s system (like ERP2005 ) you get a warning message in SE37:
FL069 TABLES parameters are obsolete! when defining quite ordinary tables parameter using LIKE and reference to a structure in ddic.
I now speak normal function modules, not RFC enabled.
This example of tables parameter definition will cause the warning message:
return LIKE BAPIRET2
I of course looked the additional help provided by this message FL069. I understood it as following:
you should stop using TABLES parameter and more often use CHANGING parameter by referring a TABLE TYPE defined in dictionary.
if using CHANGING parameter and still want to pass the header line of your internal table you should use a separate parameter (EXPORT or CHANGING parameter)
Developers have too much used TABLES parameters for passing internal tables for reading (by value) rather than to be modified (by reference). As a consequence, fm could have change the header line without caller to know it.
in my opinion the message help is missleadingly telling that header line is no longer passed to function module if TABLES parameter is used. I made a small test program and fm (with TABLES paramerer), and everything worked as before.
The warning message can be ignored by pressing Enter a few times and your fm with TABLES parameter works as it had in older versions of Netweaver.
SAP is still using a lot of TABLES parameters in their own function modules. For example SD_SALES_HEADER_MAINTAIN.
So what is the point of this warning message while everything still works as it used to be and SAP uses this same "OBSOLETE" feature itself? Is there anything more fundamental behind this message? Like TABLES paremeters will no longer work in future versions of ABAP (or header line passing will be ignored in future versions) and therefore developers should switch to CHANGING/EXPORT parameters with TABLE TYPES as soon as possible??
Please understand that I don't need any assistance how to avoid this message, just interested to share your opinions what is the purpose of this warning message.
That is why I did not marked this thread as a question.
Br: Kimmo

Hello,
This is the view under Tables tab in my function builder:
I_T_SELECT     TYPE     SRSC_S_IF_SIMPLE-T_SELECT
I_T_FIELDS     TYPE     SRSC_S_IF_SIMPLE-T_FIELDS
E_T_DATA     LIKE     SFLIGHT (which I change to YBWxxxx)
The moment I change to YBWxxxxx it gives me that error '"TABLES parameters are obsolete! "'
and unfortunately hitting enter several times is not helping either
Thanks!

Tables parameters are obsolete

hi,
      i am trying to create one function module in ecc6.0 version. And after declaration under tables table like "errortable like bapiret2" i am getting the warning "tables parameters are obsolete". please help me to solve this problem.
                                                                    Thanks&Regards,
                                                                     chakradhar.M.

Hi,
It just a warning message..Press enter to continue..
OR
create a table type in the DDIC for the structure and use that table type in the EXPORTING parameter...
Thanks
Naren

How BAPI Tables parameters are passed by reference

Hi Gurus,
I have a genuine doubt regarding BAPI parameters. I would like to point out the genreal rules of bapi like,
1. BAPI parameters should be passed by value. (Because they are rfc fm's. So both systems will be in different servers. This is the normal scenario.)
2. But the tables parameters in BAPI can't be passed by value. Instead they are passed by reference.
3. I know they use some kind of delta mechanism to transfer tables parameters to remote servers.
So gurus I would like to know what exactly happens when a tables parameter is passed. And also I didn't understand the delta mechanism. Kindly guide me.
Thanks in advance,
Jerry Jerome

You'll see in [SAP Library - RFC - Parameter Handling in Remote Calls|http://help.sap.com/saphelp_nw04s/helpdata/en/22/042551488911d189490000e829fbbd/frameset.htm] that tables are not passed by reference when you use RFC. It also explains the delta.
When you make a remote function call, the system handles parameter transfer differently than it does with local calls.
TABLES parameters
The actual table is transferred, but not the table header. If a table parameter is not specified, an empty table is used in the called function.
The RFC uses a delta managing mechanism to minimize network load during parameter and result passing. Internal ABAP tables can be used as parameters for function module calls. When a function module is called locally, a parameter tables is transferred u201Cby reference". This means that you do not have to create a new local copy. RFC does not support transfer u201Cby referenceu201D. Therefore, the entire table must be transferred back and forth between the RFC client and the RFC server. When the RFC server receives the table entries, it creates a local copy of the internal table. Then only delta information is returned to the RFC client. This information is not returned to the RFC client every time a table operation occurs, however; instead, all collected delta information is passed on at once when the function returns to the client.
The first time a table is passed, it is given an object-ID and registered as a "virtual global table" in the calling system. This registration is kept alive as long as call-backs are possible between calling and called systems. Thus, if multiple call-backs occur, the change-log can be passed back and forth to update the local copy, but the table itself need only be copied once (the first time).

Are Business Areas obsolete with ECC 6.0 and the new GL?

I have long heard that SAP is not planning on supporting Business Areas long term. Howver in the help documenation they still have them listed.
One solution offered to remove them is: With the advent of new GL in ECC; the field profit center and the PCA ledger is now an integral part of new gl (FAGLFLEX). profit center and other custom fields can now easily be defined as a zero balance entity - which means it works exactly in similar fashion as BA use to work. In addition, you can mantain a PCA hierarchy and it is an attribute that appears on key objects in SAP i.e. material master, production order, purchase order etc.
However, for customers that are using both BA's and PC's already (for example using BA's to represent plant groupings and PC's along product lines) is there a real need to make a change and remove the BA's from the current system to avoid future problems?

Hi,
The answer is most probably Yes. However, those who are having business area and those who like the concept can continue. New GL has revolutionised the segmental concept which is very much needed for the day to day running of business and to meet the accounting standards which are becoming more rigid due to the prevalance of fraud across the world.
Trust this helps much!
Cheers!

Function moudule error - table parameters obsolete

Subject changed by moderator. Please use a meaningful subject in future
Hi SAP-ABAP experts,
can i get get the information for the following error.
when i was giving *structure* name in tables parameter and gave the 'TYPE' as type in function module screen i was getting the error like this,
TABLES parameters are obsolete.
in 4.7e the function module got activated but in ecc 6.0 i am getting the error like that. can u please clarify the issue
will the type declaration be chaged according to versions of SAP ABAP.
Thanks,
Kavitha.P
Edited by: Matt on Nov 26, 2008 8:09 AM

1. Create a structure in SE11, this will include all the fields you want.
2. Create a Table type in SE11, referring the above structure as the row type.
3. Now, when you use this table type you would need to have a work area to process the data of the table. So, in the program declare a variable with ref to the structure created in Step 1.
Then you can use
LOOP AT T_ITAB INTO WA_ITAB.
ENDLOOP.
where T_ITAB is referring to table type and WA_ITAB is referring to structure.
Thanks
Saurabh

Tables parameters obsolete

Hi all,
In ecc6.0 i have been trying to use tables parameters while designing function modules and it says tables parameters are obsolete, what should be used here and how?
Regards,
C.A

Hi,
Create a table type in Se11 of the type internal table.
Now when you are decalring the internal table in Changing parameter give the reference of that table type.
Create another work area in the source code of function module.
now loop the Internal table sa usual.
regards,
Sujit

RFC Lookup Table Parameters Reusability

Dear All
My Requirement is to Map fields in IDoc from the File data ,there are some fields in idoc for which i need to fetch data from SAP.
For this i am using RFC Look up. i am retrieving values from table parameters for RFC.
and this Table parameters are being used muliple times in Mapping.
Right now i have to execute the same RFC for set of input data atleast 5 r 6 times.
This is effective Performance of the Interface
Is there any concept of Reusuability in RFC Lookup while Mapping in PI.?
Can we use Java Initialization section in mapping for executing the RFC once and using the output data in table parameters while mapping various target fields.
Hoping for a Positive Reply
Regards
Bhasker

Hi,
1) If it is PI 7.1 there are mapping enhancements, such as
a) Variables for storing intermediate mapping value,
b) for RFC lookup etc.
you can find the 7.1 pdfs from SDN
2) you can have a two stage mapping, putting them sequentially in Interface mapping object.
First step : Source to Target (orignal target structure)
here you can do all the mapping and also One time RFC lookup, but leaving the other fields where you need the lookup values again
Second step : Target to Target
here already mapped target becomes your input & you know the fields which have the value & the fields that you need to map again and all other fields are one to one mapping.
Regards
Vishnu

Problem with SP with table parameters

Hello, I have problem with stored procedure with paramater which is table type.
I have defined my own type
CREATE OR REPLACE TYPE STRING_LST AS TABLE OF VARCHAR2(80);
and i have stored procedure like this
PROCEDURE probe(outList OUT STRING_LST) IS BEGIN outList := STRING_LST(); outList.EXTEND(); outList(outList.LAST) := 'ONE'; outList.EXTEND(); outList(outList.LAST) := 'TWO'; outList.EXTEND(); outList(outList.LAST) := 'THREE'; END probe;
I have java class which connects to the database and calls this procedure
package mypackage; import java.sql.CallableStatement; import java.sql.Connection; import java.sql.DriverManager; import java.sql.SQLException; import java.sql.Types; import java.sql.Array; public class DAO_Test { public static String toNormalString (String aa) { if (aa != null && aa.startsWith("0x")) { StringBuffer str = new StringBuffer(64); for (int i = 2; i < aa.length(); i += 2) { str.append((char) Integer.parseInt(aa.substring(i, i + 2), 16)); } return str.toString(); } else { return aa; } } public void probe ( ) { try { DriverManager.registerDriver(new oracle.jdbc.driver.OracleDriver()); Connection conn = DriverManager.getConnection("dbc:oracle:thin:@server_ip:database_name", "sa", "blahblah"); String sql = "{ CALL PROBE(?) }"; String sqlType = "STRING_LST"; CallableStatement cs = conn.prepareCall(sql); cs.registerOutParameter(1, Types.ARRAY, sqlType); cs.execute(); Array arr = cs.getArray(1); String[] values = (String[]) arr.getArray(); for (int i = 0; i < values.length; i++) { System.out.println("" + i + ": '" + toNormalString(values) + "'");
cs.close();
conn.close();
} catch (SQLException e) {
logger.error("SQLException", e);
} catch (Exception e) {
logger.error("Exception", e);
public static void main (String args[]) throws SQLException {
DAO_Test test = new DAO_Test();
test.probe();
Now...
When I run this class on my local machine the result is OK nad looks like
1: 'ONE'
2: 'TWO'
3: 'THREE'
But when I copy this class on the server and run it, the result is wrong
1: '???'
2: '???'
3: '???'
Here is my environment:
on local machine
eclipse 3.3.1
java 1.5 (java version compiler in eclipse is 1.4)
on server
oracle 9.2.0.6.0
java 1.4.2_08
Result from table parameters are always 3 question marks :|
What is the problem?
Rafał

HI,
I think i found the solution: nls_charset12.jar from page
http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/htdocs/jdbc9201.html
I have copied this jar to server lib directory and it works fine :)

In BAPI's why the structures are used in table parameters?

Hello sir,
what is BAPI sir? In BAPI's why the structures are used in table parameters? table parameters they are using structures but not using any customized tables ?
regards
rachu.

Hello Rachu
BAPIs provide RFC-enabled interfaces to SAP business objects (e.g. like customer, sales order, purchase order, etc.).
A BAPI does basically the same like you would need to do calling the corresponding transaction (e.g. BAPI_SALESORDER_CREATE -> VA01).
Since they are RFC-enabled they can be called from external systems.
BAPIs represent an external interface for the outside world. Very often you will find within the BAPI that there is a mapping done to the (SAP-)internal structures at the beginning of the coding and vice versa at the end of the coding. Thus, you will (almost) never find any DB table name used as type of a BAPI TABLES parameter.
Regards
Uwe

How to know on what tables the standard bw datasource are built in ECC

Hi Guys,
How do we know on what tables the BW DataSource are built in ECC.
Thanks & Regards
Jagannadha Raju

Hi Raju,
check in below link which will give details of the datasources and associated tables.
http://help.sap.com/saphelp_nw70/helpdata/en/3d/5fb13cd0500255e10000000a114084/frameset.htm
Hope this helps.
Regards,
Reddy

Using tables parameters for RFC

Hi All
I am trying to use tables parameter for a Remote Function Call.
It says it is obsolete and not working, we are using ECC6.0 version of SAP.
Any help??

Instead, you should use a table type in a IMPORTING or EXPORTING parameter. Create the table type in SE11 and then reference this table type in your parameter in the IMPORTING/EXPORTING tab. The use of TABLES parameters section is obselete.
Regards,
Rich HEilman

LIKE as typing for parameters is obsolete!

Hi,
I am creating a function module in ECC6 for custom Inbound IDoc. I am creating in the Import tab as
INPUT_METHOD LIKE BDWFAP_PAR-INPUTMETHD
While saving system giving information message that
<i>
LIKE as typing for parameters is obsolete!
</i>
I press f4 in the Type field there i can able find only TYPE and TYPE REF TO entries
Please correct me what i am doing wrong
Sa_R

Hi AR,
In ECC 6, SAP suggests us to use LIKE to reference data objects in the memory (for example, a variable, structure, or internal table).
We should use TYPE to reference build-in types (for example, i, p, f, etc.) and ABAP dictionary types (for example, MARA, MARD or any other object in the ABAP dictionary).
We can still use LIKE to reference an ABAP dictionary type (for example, BDWFAP_PAR in your program); however, SAP suggests us NOT to do so and sends us a warning message.
PS. TYPE/LIKE has no relationship to header/internal table. You can use TYPE to declare internal table and you can use LIKE to declare header, too.
For example, the following statement declares it_bkpf as an internal table.
DATA: it_bkpf TYPE bkpf_t.
B.R.

How to add the rows formatted as table headings, Tables headings are repeated when a table spans more than one page.

Hi all,
i am facing problem while generating Test Result word document after successful execution of TestStand.
The Problem is :
i want to add rows Formatted as table headings, table headings are repeated when a table spans more than one page(marked as Red).
Example:
Page No. 1
|     Test case Number | Test Step number      |
|      100                         |            100                   |
Page No. 2
|     Test case Number | Test Step number      |
|      200                         |            300                   |
Test Result word document should generate with Table headings(marked as Red) in every pages of the document, but i am not getting as per above example.
Please through light on this.
Regards,
Susa.

Hi Santiago,
Thank you very much for your valuable reply.
i want to generate MS-word report for TestStand after successful testing using MS-word2000.
Test report contains Actual values, Expected values and Pass/Fail status.
In my program i have customized all fields i can able to generate test report which contains Verification engineer name , test mode, test date, start time, end time Actual values, Expected values and Pass/Fail status.etc....
To put all values of test case number, Test step number, Actual values, Expected values and Pass/Fail status in to table for each time, i will
insert a row into table every time values arrives, once the table exceedes its page size it moves to the next page, next page should start with table row header but it start with values of above said parameters.
so i'm not able to repeat table row header for each page.
Please find the attached file for your reference.
Attched file expected.doc :   This file contains what i wanted to generate MS-word report. Here table row header "Test Case Number and Test Step Number " is repeated in second page.
Attached file Actual output from source code.doc   : This report generated from the source code. Here table row header "Test Case Number and Test Step Number" is not repeated in second page.
Do you know any property to set "repeat as header row at the top of each page" using MS-word ActiveX in CVI/Labwindows.
i think this information is sufficient for you,
Still if you need some information please ask me.
Thanks
Susa.
Attachments:
Actual output from source code.doc ‏25 KB
expected.doc ‏26 KB

How to declare Dynamic table in Tables Parameters of a Function Module...

Hi Gurus,
I would like to Know how to declare a Dynamic table in Tables parameters of a Function Module.
so that it should be able to hold any table data ....
I have tried all possible ways of trying to assign fields-symbol like declarations which doesnt allow here ...
plz Dont reply with the basics of creating dynamic internal tables, coz my case is not an Internal table it is FM table parameter declaration.....

Hi,
If you are requirement is to create a function module with tables parameter having a generic line type i.e. no specific line type
just declare it with a name under Parameter name with out specifying the type.
A reference function module with such parameter, i would quote is the standard GUI_UPLOAD/ GUI_DOWNLOAD where the parameters specified under TABLES are generic.
If you want to process the values passed to these parameters in the source code of function module, field symbols would be a preferable option.
Regards,
Sharath Panuganti

Table Parameters are obsolete in ECC 6.0

Similar Messages

Maybe you are looking for