ECC 6 Obsolate commands & function modules

Hi,
We are going to upgrade from 4.7 to ECC 6. I am looking for list of obsolate commands and function modules in ECC 6.
Thanks
aRs

Hi,
Please check this link for obsolete ABAP command.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5ac31178-0701-0010-469a-b4d7fa2721ca
Regards,
Ferry Lianto

Similar Messages

Function module in crystal reports using tables as input

We had a function module created with a few import parameters. We successfully linked it in crystal and were able to retrieve the data.
To accommodate the requirement of being able to pick multiple values for some of the parameters, the import parameters were changed to tables. When testing in ECC, we are able to retrieve the data using the function module.
However, when we're using the same approach as before in crystal reports, we are not able to retrieve the data.
Is it possible in crystal to pass the input parameters to tables ?
Any ideas what I might be doing wrong?
Thanks,
Mat

Hi John,
The solution is very simple.
You create a function module in ECC (t-code SE37) that will receive you input parameters, process them, and export a table with your results.
In the function module you define an input parameter using a CHAR120 data type (ex. PERNR).
In the function module source code you add logic to split the input parameter
[SPLIT i_PERNR AT ',' INTO TABLE itab_PERNRS.]
You then create a crystal report against your function module.
In your crystal report you create a parameter using type "string" (ex. I_PERNR).
When you execute the crystal report, you input a comma delimited string in the parameter.
[00001234,00005678,00009123]
The function module will receive the string of values, split the string to an internal table, and process accordingly.
I still have no solution for the 120 character restriction in the CR->ECC interface. In the meantime, I get around this by creating multiple parameters (PERNR1, PERNR2, PERNR3, etc.).
Each parameter is set up to pass a string of 120 characters to ECC.
The function module is set up to concatenate the parameters before splitting.
[CONCATENATE PERNR1 PERNR2 PERNR3 into I_PERNR]
Hope this helps.

Archiving using PBS Function modules

Hi All,
I am converting existing report to archiving reports.
For that I am using PBS Commands FUNCTION MODULES. .
ie function module like '/PBS/SELECT_INTO_TABLE'
Can any one send some documents related PBS and how to use these commands or function modules,and sample programs.
thanks in advance..
srinu.

Hi ,
Thanks for your help and responce.
I already coded one small program using commands . but its not working properly in perticular case.
 Here is the Code.
 From EKKO table the fucntion module fetching the data properly.
SELECT SINGLE * FROM EKKO
 INTO W_EKKO
 WHERE EBELN EQ P_EBELN.
 IF SY-SUBRC NE 0.
 CALL FUNCTION '/PBS/SELECT_INTO_TABLE'
 EXPORTING
 ARCHIV 'CMM'
 OPTION ''
 TABNAME = 'EKKO'
 SCHL1_NAME = 'EBELN'
 SCHL1_VON = P_EBELN
 SCHL1_BIS = P_EBELN
 TABLES
 I_TABELLE = TAB20
 EXCEPTIONS EOF = 4
 OTHERS = 2.
 LOOP AT TAB20 WHERE ( EBELN EQ P_EBELN ).
 MOVE-CORRESPONDING TAB20 TO W_EKKO .
 EXIT.
 ENDLOOP.
 ENDIF.
But when I use the function module to fetch from EKPO, its considering only EBELN , but not considering the EBELP .
Its fetching all the line items related to this EBELN.
SELECT * UP TO 1 ROWS
 INTO CORRESPONDING FIELDS
 OF TABLE TAB23
FROM EKPO
WHERE EBELN EQ W_EKKO-EBELN
AND EBELP EQ P_EBELP.
ENDSELECT.
if sy-subrc ne 0.
CALL FUNCTION '/PBS/SELECT_INTO_TABLE'
 EXPORTING
 ARCHIV = 'CMM'
 OPTION = ''
 TABNAME = 'EKPO'
 SCHL1_NAME = 'EBELN'
 SCHL1_VON = W_EKKO-EBELN
 SCHL1_BIS = W_EKKO-EBELN
 SCHL2_NAME = 'EBELP'
 SCHL2_VON = P_EBELP
 SCHL2_BIS = P_EBELP
 TABLES
 I_TABELLE = TAB23
 EXCEPTIONS EOF = 4
 OTHERS = 2.
 LOOP AT TAB23 WHERE ( EBELN EQ W_EKKO-EBELN AND
 EBELP EQ P_EBELP ).
 MOVE TAB23-ebelp TO W_EKPO-ebelp.
ENDLOOP .
endif.
Please check my code and give me some inputs.
Is there any pre-conditions are needed.
Thanks and Regards,
Srinivas Kalva.

Standard Remote-Enabled Function Module to display data.

Good afternoon,
Is there any Standard Remote-Enabled Function Module which can be used to display a list of material, supplier or stocks data?
First time, I was trying to use FM link to BW Extractor as MDEX_MATERIAL_MD for Material Attributes, but these kind of FM are not Remote-Enabled and not released.
My second solution is to find a Standard Remote-Enabled Function Module which can be used to display a list of material, supplier or stocks data, but I haven't it yet.
May someone help me in this?
Thanks in advance for your answers.
Best regards,
Paul d'ORIGNY

Hi,
Suppose you want to read data from the vbrk table in ECC through a function module, then you can define the function module as "remote-enabled"(attribute tab in se37-processing type). You can try the following code out:
FUNCTION Z_EM_INVOICE.
*""Local Interface:*
*" IMPORTING
*" VALUE(I_FKDAT) TYPE FKDAT OPTIONAL
*" TABLES
*" E_VBRK STRUCTURE VBRK
*select * from vbrk into table*
e_vbrk where fkdat = i_fkdat.
ENDFUNCTION.
From BI you can call the function odule as follows:Supposing that you are calling the function module in the start routine of a dso:
data : v_dest_system TYPE char255.
data: l_vbrk type table of vbrk.
v_dest_system = 'DRDCLNT010'
CALL FUNCTION 'Z_EM_INVOICE''
destination v_dest_system
EXPORTING
i_fkdat = <passing variable>
e_vbrk = l_vbrk.
Regards,
Anjana.

Function module Registry_get

Hi All,
We are going for upgrade from 4.6 to ECC 6.0.Function module REGISTRY_GET is obselete in 4.6 instead of this i have used class CL_GUI_FRONTEND_SERVICES method 'registry_get_value' .But the there is a diffrence in number of parameter passed in function module and that class method.Below is the code both in 4.6 and ECC 6.0.
In 4.6 it was as below:
CALL FUNCTION 'REGISTRY_GET'
      EXPORTING
           KEY     = 'protocol\StdFileEditing\server'
           SECTION = 'ExcelWorksheet'
      IMPORTING
           VALUE   = EXCEL_PATH.
Now in ECC 6.0 i replaced as below:
call method cl_gui_frontend_services=>registry_get_value
    exporting
      root                = cl_gui_frontend_services=>hkey_classes_root
      key                 = 'protocol\StdFileEditing\server'
      value               = ''
    importing
      reg_value           = reg_value
    exceptions
      get_regvalue_failed = 1
      cntl_error          = 2
      error_no_gui        = 3
      others              = 4.
If i compair both the code then parameters differ's.But i am not able to undestand what the use of these parameter.Please sugest if i am doing the right thing in ECC6.0 and please also let me know the replacement of function module 'Profile_GET' used as below in 4.6:
call function 'PROFILE_GET'
       exporting
            filename = 'front.ini'
            key      = 'Path'
            section = 'Filetransfer'
       importing
            value    = dir_path
       exceptions
            others   = 1.
Thanks
Mohit

Sample to understand :
Code 46C
*     Test, ob OrgPublisher lokal installiert ist
      CALL FUNCTION 'REGISTRY_GET'
           EXPORTING
                key     = 'CLSID'
                section = 'OrgPublisher.Document.2'
           IMPORTING
                value   = class_id.
      IF class_id IS INITIAL.
Code ECC 6.0
      CALL METHOD cl_gui_frontend_services=>registry_get_value
        EXPORTING
          root         = cl_gui_frontend_services=>hkey_classes_root
          key          = 'OrgPublisher.Document.2\CLSID'
        IMPORTING
          reg_value            = class_id
        EXCEPTIONS
          get_regvalue_failed = 1
          cntl_error           = 2
          error_no_gui         = 3
          not_supported_by_gui = 4
          OTHERS               = 5.
      CALL METHOD cl_gui_cfw=>flush
        EXCEPTIONS
          cntl_system_error = 1
          cntl_error        = 2
          OTHERS            = 3.
      IF class_id IS INITIAL OR sy-subrc NE 0.
Regards,
Raymond

Function Module RFC_CALL_TRANSACTION not exist in ERP6??

Hi,
Does anyone know if this function module has been replaced in ERP6?? We are still running code that calls this Funciton Module, but we get the following error:
Executing postCommandError with type 'action_log', attribute '10001' and command 'Function module "RFC_CALL_TRANSACTION" not found.'
tks
Christiaan
POINTS WILL BE REWARDED

Hi Christiaan,
Check RFC FM ABAP4_CALL_TRANSACTION
Thanks
Lakshman

Clarification on some reading: Datasource and Function Module extraction

Hi,
I found a link on Help.sap which explains how to create a function module and I have some questions after my review:
It basically uses function module to read some filght data from the table SPFLI
1.
I got into this research since one of the methods for data extraction from R3/ECC to BW is through Function Modules.
Why couldn't that extraction be based on a view of the table SPFLI.
i.e. why is this complication of writing an ABAP code to achieve something which could be done with a DB view or table?
2.
Any example or scenario where you think a datasource could NOT be created based on a table, Database View or Sap Query and that it must be done with a Function Module?
3.
So, once the function module is successfully created; how to do create a Datasource based on this function modeule to take care of the delta's on the source data?
4.
There was a discussion about "remote function call" which I did not get completely. Will extracting data from R3/ECC to BI be regarded as "remote call"
Thanks

1. Why couldn't that extraction be based on a view of the table SPFLI. i.e. why is this complication of writing an ABAP code to achieve something which could be done with a DB view or table?
A DataSource could have been created directly from table SPFLI. It was used as an example in the case of the document is my guess. There are some table types, however, that you cannot create a DataSource directly off of.
2. Any example or scenario where you think a datasource could NOT be created based on a table, Database View or Sap Query and that it must be done with a Function Module?
Pool/Cluster tables cannot be directly read and therefore must use a Function Module for extraction. Another reason for using a Function Module, even against a single table, is in the case that you have more than one field that you want to create a generic delta against. SAP delivers the capability in the application to set a generic delta on only one field within the DataSource. If there is more than one, say created on and changed on dates, a Function Module is require in order to enable that.
3. So, once the function module is successfully created; how to do create a Datasource based on this function modeule to take care of the delta's on the source data?
Go to tocde RSO2, enter the DataSource name, click on the Create button. In the next screen, there are three buttons toward the top to tell what is the source of the DataSource: 1) Extraction from View (default); 2) Extraction from Query; and 3) Extraction from Function Module. When you click on the Extraction from Function Module button, the View/Table field will gray out and the Function Module and Extraction Structure fields will un-gray.
4. There was a discussion about "remote function call" which I did not get completely. Will extracting data from R3/ECC to BI be regarded as "remote call"
I think that this is referring to a process whereby you create a remote-enabled Function Module on the source R3/ECC system and then create an ABAP program in BW that calls that remote-enabled Function Module. Basically, the ABAP program on BW would send some parameters through to the remote-enabled Function Module on R3/ECC. The Function Module would extract data into an internal table and then pass that internal table back through to the ABAP program in BW for further processing.
Edited by: Dennis Scoville on Aug 20, 2009 8:18 AM

Obsolate statement for function module TABLE_COMPRESS

Hi all,
What is the alternate function module for TABLE_COMPRESS?
This is going fine in 4.7 version.
But in ECC 6.0, if we use this function module we r getting SLIN error (Obsolate statements) .
How can we rectify this SLIN error?
So we have to use another funtion module for the same purpose.
Can any one help on this?
Rewards to all.
Thanks & Regards
Anu.

Hello,
This Function Module belongs to the Function Group SYST. I really doubt if this is going to be made obsolete without providing an alternative. In such a case there would almost certainly have been an OSS Note. However, I could not find any OSS note for this.
Moreover, the Function Module doesn't have "obsolete" flag set if you see from SE37. Therefore it must be really safe to use this function module in your program.
Still, I will try to get a confirmation for this.
Regards,
Anand Mandalika.

How to find the Obsolete function module in ECC 6.0

Hi Guys,
How we can find the all obsolete function in ECC 6.0, is any T-code to finding the obsolete function modules, or any other way to find.
Could you please help me.
Thanks,
Gourisankar.

Hi Gouri,
If you are looking at determining whether a single FM is obsolete or not is by this method:
Go to FM in SE37 -> Goto Attributes Tab -> General Data section -> look above the Edit Lock field ... where SAP places the release status and date of the FM, if the FM is obsolete, the text Function Obsolete appears
This is one way of finding out one FM @ a time
However if you want to check on a mass scale, I dont have a SAP system here hence cant confirm, however, all FMs are stored in TFDIR database table. Please scroll through the fields of the DB table to check whether any field relates to release status or the like. If it does, then from SE16, you can put the value corresponding to "Obsolete" in the field and run to check all FMs.
Cheers,
Aditya

G_G_IDOC_REC_ZZINCOT function module not found in ECC 5.0

i am getting the dump.
the fuction module is not presend in ECC 5.0
Runtime Errors         CALL_FUNCTION_NOT_FOUND
Exceptn                CX_SY_DYN_CALL_ILLEGAL_FUNC
Date and Time          04/05/2007 07:13:25
ShrtText
Function module "G_G_IDOC_REC_ZZINCOT" not found.
What happened?
The function module "G_G_IDOC_REC_ZZINCOT" was called, but cannot be
    found in the Function Library.
Error in ABAP application program.
The current ABAP program "SAPLGUIF" had to be terminated because one of the
    statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
    and make a note of the actions and input that caused the
    error.
To resolve the problem, contact your SAP system administrator.
    You can use transaction ST22 (ABAP Dump Analysis) to view and administer
     termination messages, especially those beyond their normal deletion
    date.
is especially useful if you want to keep a particular message.
Error analysis
An exception occurred. This exception is dealt with in more detail below
    . The exception, which is assigned to the class 'CX_SY_DYN_CALL_ILLEGAL_FUNC',
     was neither
caught nor passed along using a RAISING clause, in the procedure
     "IDOC_INPUT_GLROLL" "(FUNCTION)"
Since the caller of the procedure could not have expected this exception
     to occur, the running program was terminated.
    The reason for the exception is:
    The program "SAPLGUIF" contains a CALL FUNCTION statement. The name
    of the function module to be called is "G_G_IDOC_REC_ZZINCOT".
No function module exists with the name "G_G_IDOC_REC_ZZINCOT".
    All function modules are stored in the Function Library (SE37).
Possible reasons:
a) Wrong name specified. Particular attention should be paid
       to upper/lower case and underscores ("_")
    b) Transport error
c) If an enqueue/dequeue module has been used, the lock object
       may not have been activated (ABAP Dictionary)
       may not have been activated (ABAP Dictionary).
How to correct the error
Check the last transports to the R/3 System.
    Is the program "SAPLGUIF" currently being changed?
    If an enqueue/dequeue module is involved, is the activation
    of the lock object missing in the ABAP/4 Dictionary?
You may able to find an interim solution to the problem
    in the SAP note system. If you have access to the note system yourself,
    use the following search criteria:
"CALL_FUNCTION_NOT_FOUND" CX_SY_DYN_CALL_ILLEGAL_FUNCC
    "SAPLGUIF" or "LGUIFU05"
    "IDOC_INPUT_GLROLL"
Function modules with names similar to "G_G_IDOC_REC_ZZINCOT":
G_G_IDOC_REC_COFIT
G_G_IDOC_REC_FILCT
G_G_IDOC_REC_ECMCT
G_G_IDOC_REC_GLPCT
G_G_IDOC_REC_GLT0
G_G_IDOC_REC_SECURE
G_POSTING_ZZINCOT
G_G_IDOC_SEND_COFIT
G_G_IDOC_SEND_ECMCT
G_G_IDOC_SEND_SECURE
If you cannot solve the problem yourself and you wish to send
    an error message to SAP, include the following documents:
1. A printout of the problem description (short dump)
       To obtain this, select in the current display "System->List->
       Save->Local File (unconverted)".
2. A suitable printout of the system log
       To obtain this, call the system log through transaction SM21.
       Limit the time interval to 10 minutes before and 5 minutes
       after the short dump. In the display, then select the function
       "System->List->Save->Local File (unconverted)".
3. If the programs are your own programs or modified SAP programs,
       supply the source code.
       To do this, select the Editor function "Further Utilities->
       Upload/Download->Download".
4. Details regarding the conditions under which the error occurred
       or which actions and input led to the error.
    The exception must either be prevented, caught within the procedure
     "IDOC_INPUT_GLROLL"
"(FUNCTION)", or declared in the procedure's RAISING clause.
    To prevent the exception, note the following:
System environment
SAP Release.............. "640"
Application server....... "d48ix100"
    Network address.......... "151.162.153.62"
    Operating system......... "AIX"
    Release.................. "5.3"
    Hardware type............ "00C65EFD4C00"
    Character length......... 8 Bits
    Pointer length........... 64 Bits
    Work process number...... 2
    Short dump setting....... "full"
Database server.......... "d48ix100"
    Database type............ "ORACLE"
    Database name............ "D48"
    Database owner........... "SAPR3"
Character set............ "en_US.ISO8859-1"
SAP kernel............... "640"
    Created on............... "Nov 5 2006 20:46:58"
    Created in............... "AIX 1 5 00538A4A4C00"
    Database version......... "OCI_920 "
Patch level.............. "156"
    Patch text............... " "
Supported environment....
    Database................. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE
     10.2.0.."
SAP database version..... "640"
    Operating system......... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory usage.............
    Roll..................... 16128
    EM....................... 8379856
    Heap..................... 0
    Page..................... 16384
    MM Used.................. 2530176
    MM Free.................. 1657232
    SAP Release.............. "640"
User and Transaction
Client.............. 010
    User................ "OS0730"
    Language key........ "E"
    Transaction......... "YICUPLD "
    Program............. "SAPLGUIF"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6
Information on where terminated
    The termination occurred in the ABAP program "SAPLGUIF" in "IDOC_INPUT_GLROLL".
    The main program was "Y21091IRECON ".
The termination occurred in line 65 of the source code of the (Include)
     program "LGUIFU05"
of the source code of program "LGUIFU05" (when calling the editor 650).
    Processing was terminated because the exception "CX_SY_DYN_CALL_ILLEGAL_FUNC"
     occurred in the
procedure "IDOC_INPUT_GLROLL" "(FUNCTION)" but was not handled locally, not
     declared in the
RAISING clause of the procedure.
    The procedure is in the program "SAPLGUIF ". Its source code starts in line 5
    of the (Include) program "LGUIF$05 ".
Source Code Extract
Line SourceCde
35
36 *Prüfen, ob Customizing richtig eingestellt ist
   37     CHECK EXIT IS INITIAL.
   38     PERFORM CHECK_CUSTOMIZING USING IDOC_NUMBER.
   39
40 *Für Einzelposten neue Belegnummern vergeben
   41     CHECK EXIT IS INITIAL.
   42     PERFORM NEW_DOCUMENT_NUMBER USING IDOC_NUMBER
   43                                       IDOC_CONTRL-MESTYP.
   44
45 *Füllen der Segmentdaten
   46     CHECK EXIT IS INITIAL.
   47     CLEAR IDOC_SEGMENT. REFRESH IDOC_SEGMENT.
   48
49     LOOP AT IDOC_DATA WHERE DOCNUM EQ IDOC_NUMBER.
   50       IDOC_SEGMENT = IDOC_DATA.
   51       APPEND IDOC_SEGMENT.
   52     ENDLOOP.
53
54 *Name des zu rufenden Funktionsbausteines ermitteln
   55     ROL_FUNCNAME = 'G_G_IDOC_REC_$'.
   56     PERFORM BUILD_ROL_FUNCNAME USING IDOC_NUMBER ROL_FUNCNAME.
   57
58 *Funktionsbaustein zum Empfangen des IDOC's aufrufen
   59 *Wenn Sender 4.0 System -> Nimm' TAB30, sonst altes TAB
   60     IF NOT E1GLTTF-TAB30 IS INITIAL.
   61       L_TAB30 = E1GLTTF-TAB30.
   62     ELSE.
63       L_TAB30 = E1GLTTF-TAB.
   64     ENDIF.
>>>>>     CALL FUNCTION ROL_FUNCNAME
   66          EXPORTING
   67               MESTYP             = IDOC_CONTRL-MESTYP
   68               DOCNUM             = IDOC_NUMBER
   69               TAB                = L_TAB30
   70          TABLES
71               IDOC_SEGMENT       = IDOC_SEGMENT
   72               IDOC_STATUS        = IDOC_STATUS
   73               RETURN_VARIABLES   = RETURN_VARIABLES.
   74
75   ENDLOOP.
76
77 *Keine IDOC's empfangen
   78   IF SY-SUBRC NE 0.
   79     RAISE WF_ERROR_PROCESS.
   80   ELSE.
81 *Prüfen, ob Fehler bei der Verarbeitung der IDOCs aufgetreten sind
   82     LOOP AT IDOC_STATUS WHERE MSGTY = 'A'
   83                            OR MSGTY = 'E'.
   84       EXIT.
Contents of system fields
Name     Val.
SY-SUBRC 0
SY-INDEX 0
SY-TABIX 2
SY-DBCNT 1
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY                                                                           &

I think that the FM is a customized one. Correct me if I am wrong. It is quite possible that certain FM's might have been missed out while the new system is built. Here I am assuming that the you are doing an upgrade.
If whatever, I've mentioned above is correct, you can copy the FM and its other components from the old system into the new one, to rectify the error

Debugging RFC function module from ECC to CRM

Hi All,
My requirement is to debug an RFC function module present in CRM(7.0) system from ECC(6.0) system. A report program in ECC will call CRM custom FM. I found many posts in SDN with the same issue and tried to implement suggestions provided there. But I couldn't succeed. The approach I followed is:
I logged in to ECC report program and kept an external breakpoint just before the function module call.
I logged in to CRM system, opened the function module and kept an external breakpoint there.
In both the systems I provided the dialogue userid( id through which I log in to SAPGUI) in the system->settings->debugging option.
In CRM I activated the external break point in transaction SRDEBUG.
Now when I execute the report program in ECC, control stops at the breakpoint. If I press F5 at the function call, control is not going to the external break point set in the CRM FM. I am getting output of FM directly.
I tried with different settings like turning on the check box for IP matching and session breakpoint active immediate, switching to classic debugger etc. I also tried to provide the RFC user id instead of dialogue user but system throws exception saying only dialogue userids are allowed. I found that by inserting an infinite loop statement, control goes inside the RFC CRM FM but I prefer not to change the code.
Please let me know if I missed anything.
Thanks and Regards,
Naren

Hi,
Debug RFC calls
When an RFC function module is called it is usually not possible to debug the call, using the below techniques we can achieve the same. For this example we are calling an RFC enabled FM in ECC system from CRM system.
Scenario 1: Calling a custom RFC FM
STEP 1: Add an infinite loop in the remote custom Function Module (adding a u201CDO. ENDDO.u201D statement at the start of the FM would be enough).
STEP 2: Execute your program in the CRM system. The execution stops at the RFC call, because of the infinite loop.
STEP 3: Now login to the ECC system and go to transaction SM51 select the process which is executing the RFC and navigate to the menu: u201CProgram/Session->Program->Debuggingu201D this triggers the debugger session in a separate window.
Scenario 2: Calling a Standard RFC FM
When we are debugging a standard program we cannot add the infinite loop, hence we cannot go to SM51 and debug the work process. The RFC destination for the ECC system has a User specified, the RFC function module gets executed using this users credentials. Usually the basis team set up the RFC user as non Dialog user, this does not allow debugging. Contact your Basis team and get this changed to a dialog user enabling you to debug RFC function calls via the normal debugger.
Note: User name configured in the RFC destination (transaction SM59)
Note: User type for the RFC User (transaction SU01D)
Hope this will be helpful..

Error while creating webservice from function module in ECC

Hi
while creating a web service out of a function module in ECC, in the configure service section we get a message saying ' Remember that the service does not have any runtime configuration and therefore cannot be used. Create the Web service configuration in the NetWeaver Admninistrator (transaction WSADMIN2).'
instead of check box 'release for runtime'.
Our ECC at release 7 patch level 22.
Checked in SCICM, SICF teh service and the folder are active.
Please suggest if we are missing on anything
Regards
Kumar

In new version on ECC, the runtime configurations needs to be performed in transaction SOAMANGER.
On executing the transaction, it opens a browser. The important configurations to be performed are:
1. Configure J2EE server and host. You can choose to provide the ECC server and host
2. Administration of the service in "Single Service Administration". The navigation path may differ depending of the ECC versions. But it is related to administration of the services.
Once done, check the WSDL generated.
Use this WSDL in the NWDS.
Regards,
Sharath

Replaced version of Function Module PFL_COPY_OS_FILE in ECC 6.0

Hi everybody,
                      Can anybody tell me what is the replaced name of function module PFL_COPY_OS_FILE in ECC 6.0. This function module was used in 4.6C version and become obsolete in ECC 6.0. It is basically used for copying OS files.

check CL_GUI_FRONTEND_SERVICES=>FILE_COPY
new_file = P_FILE.
    app_full_name = R_FILE.
    CALL METHOD cl_gui_frontend_services=>file_copy
      EXPORTING
        SOURCE             = new_file
        DESTINATION        = app_full_name
        overwrite          = 'X'
      EXCEPTIONS
        cntl_error         = 1
        error_no_gui       = 2
        wrong_parameter    = 3
        disk_full          = 4
        file_not_found     = 5
        destination_exists = 6
        unknown_error      = 7
        path_not_found     = 8
        disk_write_protect = 9.
    IF sy-subrc NE 0.
      EXIT.
    ENDIF.

Replacement of Function module in ECC 6.0

Hello All,
The Function module 'NAMETAB_GET' is shown to be obsolete in ECC 6.0 .
Please suggest which of the function modules among 'DDIF_FIELDINFO_GET' and 'DDIF_NAMETAB_GET' can be used as a replacement for the same.
Also ,it would be helpful if the use of these function modules is mentioned.
Best Regards,
Lavanya.

use 'DDIF_NAMETAB_GET'
Functionality
This function module reads the runtime information (nametab) of a table or in general of any type of the ABAP Dictionary. However, the runtime information does not contain any text. You should use the function module DDIF_FIELDINFO_GET to read the runtime information including text (or to determine the domain for table fields).
The types of the ABAP Dictionary are divided into data elements, structured types and table types.
A structured type consists of a sequence of components that are each identified by a unique name. A type is defined for each of these components. In addition to the types of the ABAP Dictionary, you can also use the built-in types of the R/3 System (CHAR, NUMC,...) to define the types of the components.
All its components as well as the fields of its structured components are called the fields of a structured type. The name of a field no longer uniquely identifies it within a structured type. For example, a structured type S could have a structured component F, which itself has a component called F. In this case S would have two fields with the name F. For this reason, its long field name is used to identify a field within a structured type. The long field name is the same as the name of the components for the components of the structured type itself. For the fields of a structured component, the long field name is a concatenation of the name of this structured component, the separator '-' and the long field name of the field in the structured component.
A field whose type is defined by a data element or a built-in type is also called an elementary type. A structured type whose components are all defined as elementary types is called flat. All other structured types are called deep.
This module gets the runtime information for the type whose name is defined in the IMPORT parameter TABNAME. If there is no such type, the exception NOT_FOUND is triggered.
Caution: If the IMPORT parameter ALL_TYPES is not set, only flat structured types are taken into consideration. In this case the exception is also triggered if the specified type is a data element, deep structure or a table type.
If the IMPORT parameter LFIELDNAME is not initial, only structured types having a field with the long name defined by LFIELDNAME are taken into consideration. The exception NOT_FOUND is triggered for all other types.
The internal representation of the runtime object is returned in parameters X030L_WA and X031L_TAB. Depending on the type category, this information is then edited in the corresponding parameters (see documentation about the parameters).
Notes
1. If parameter LFIELDNAME is not initial, X031L_TAB nevertheless contains the description of all fields of the structured type. The decoded form is only determined for the specified field, and the result is copied to DFIES_WA instead of DFIES_TAB. Since decoding for all the fields often takes up most of the runtime for this module, you should set parameter LFIELDNAME if you only need information about one field of the structured type.
This module gets the runtime information about a type. This means that only the currently active version of the type is taken into consideration. If none exists, the exception NOT_FOUND is triggered.
The corresponding function module DDIF_<object type>_GET is used to read the actual definition of a type of the ABAP Dictionary.
Caution: These read modules are much less efficient than the modules for defining the runtime information. You should therefore only use them if the runtime information is not sufficient.
2. The documentation for IMPORT parameter GROUP_NAMES describes how to handle named includes.

Replacement of Function Module 'www_get_mime_object' in ECC 6.0

HI,
I need an exact replacement for the Function Module 'www_get_mime_object' in ECC 6.0.
Please help it out.
Regards,
Ashok.

hey

ECC 6 Obsolate commands & function modules

Similar Messages

Maybe you are looking for