CALL Function Module RV_CALL_CHANGE_TRANSACTION in a NEW session/window

Hi,
I am modifying report VA14L. When a sales document is clicked on in the ALV grid, I need the sales document to open in a NEW window, not in the same. To determine and open the transaction, function module RV_CALL_CHANGE_TRANSACTION is used. How can I force this FM to open in a new window?
Many Thanks,
Jeroen

Thanks.
I think you mean STARTING NEW TASK instead of IN NEW TASK because the latter does not exist. STARTING NEW TASK '<task>' does not work either, it causes a short dump:
Error analysis
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "CALL_FUNCTION_NOT_REMOTE"
    on the called page.
So any other suggestions?

Similar Messages

Function Module to open a new session displaying a method of a class

Hello All,
I have a method A of class B.
Now, in my current session, I have a button. When the user clicks on this button, what I expect is that a new session be opened and in the new session method A of class B be displayed.
This is similar to the debugger, wherein, in the debugging mode, we can bring up the context menu in the Source Code (Edit Control) tool, and then select "Go To Source Code".
So basically, I am looking for a Function Module which does the same.
I came across Function Module CC_CALL_TRANSACTION_NEW_TASK, however, this will only create a new session.
I could specify the transaction as SE24, but it then opens a new session with this transaction. That is it.
My objective is to display the method of a class in a new session.
Is there any Function Module in this case?
Regards,
Mithun
Edited by: Mithun Kamath on Aug 9, 2011 5:35 PM

Hello Sandra,
Thank you very much. That was exactly what I was looking for.
However, instead of calling EDITOR_PROGRAM directly, what I instea did was the following:
1) Created a RFC enabled Function module.
2) Inside this function module, I wrote the following code:
SUBMIT tpda_editor_start AND RETURN
   WITH prgm = is_alert_det-program_name
   WITH incl = is_alert_det-include_name
   WITH dynp = space
   WITH line = is_alert_det-line_no.
The parameters above were similar to the one proposed by you.
Borrowed the above from the class CL_TPDA_SERVICES_TOOLS, method NAVIGATE_TO_SOURCE.
The above is basically called in the debugger, when we use the context menu in the editor tool and invoke the "Goto Source Code" functionality. This eventually calls the EDITOR_PROGRAM FM.
The reason why I did this is because when I was testing the FM, it did not allow me to specify the include as CL_TEST=====CM01. I do not know why, probably I was doing it wrong. But it gave me a message saying that the object does not exist in table TADIR.
Anyway, I did the above steps and it worked exactly as I wanted it to.
I would like to thank you again.
Best Regards,
Mithun
P.S. Forgot to add, I called the above RFC enabled FM as a new task.
Edited by: Mithun Kamath on Aug 10, 2011 4:19 PM

Call function module in new task

I need to call a function module starting new task but the problem is that it has inporting parameters also. Please help me in doing this. Points will be rewarded.

Look at the ABAP keywords RECEIVE RESULTS FROM FUNCTION. This is where you can get the results from the CALL FUNCTION MODULE... NEW TASK...
It's all in the ABAP help for CALL FUNCTION MODULE.
matt

ABAP Dump when calling Function Module Starting New Task

Hi all. I have a tricky situation now, I am doing a POC on parallel processing.
I am getting an ABAP dump on the following Call Function line which is in class lcl_steer_114numc (See below for full program):
METHOD start.
    CALL FUNCTION 'Z_ZZCLS_STEER_114NUMC'
      STARTING NEW TASK me->id
      CALLING me->finish ON END OF TASK.
ENDMETHOD.                    "start
However I get the following ABAP dump:
Short text
    Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"
The function module only contains a wait statement to simulate parallel processing. It is strange that it dumps here, because when I change the FM call to another call that has been triggered successfully from other classes, it still produces the same ABAP dump.
The background of the Proof Of Concept is to see if I can get an event to trigger the next process that depends on the outcome of the previous process. Parallel processes are run in the start methods by calling RFC.
<Garbled code removed>
Moderator Message: Please post relevant portions of the code only.
Edited by: Suhas Saha on Jul 17, 2011 1:17 PM

Well, the thing is I did manage to run 3 other Function Modules asynchronously succeesfully prior to that function call, with the same exact function call syntax. Further more, I have tried editing it with your suggestion but I get the exact same dump.
The complete function group can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZmFhNzcwMTgtYzQ0Mi00NzQ4LTg5YTMtNDNlNWUxYTM2NTg3&hl=en_US
The complete program can be downloaded here (slinkee file):
https://docs.google.com/leaf?id=0B3sua1Bw4XK4YWJmNjU3ODYtODRmMy00Nzg2LThkNTUtZjNkNDRhZGQ3MTUw&hl=en_US
The complete ST22 dump can be found here:
https://docs.google.com/leaf?id=0B3sua1Bw4XK4ZDU1YmFkZDAtOTU5MS00ZTgwLWFlZTktNWZhMDUxMzJlZWNl&hl=en_US
Basically I ST22 gives me the following:
Runtime Errors         RPERF_ILLEGAL_STATEMENT
Date and Time          17.07.2011 05:29:54
|Short text                                                                                |
|    Statement "CALL FUNCTION .. DESTINATION/STARTING NEW TASK/IN BACKGROUND TASK"                 |
|What happened?                                                                                |
|    Error in the ABAP Application Program                                                         |
|                                                                                |
|    The current ABAP program "Z_ZZB1_CLOSE_PERIOD_TEST2" had to be terminated                     |
|     because it has                                                                               |
|    come across a statement that unfortunately cannot be executed.                                |
And it explains it here (but is not helpful / relevant at all) as I ran the program from SE38.
|Error analysis                                                                                |
|    There is probably an error in the program                                                     |
|    "Z_ZZB1_CLOSE_PERIOD_TEST2".                                                                  |
|    The program was probably called in a conversion exit                                          |
|    or in a field exit. These are implemented by                                                  |
|    function modules called CONVERSION_EXIT_xxxxx_INPUT/OUTPUT or                                 |
|    USER_EXIT_xxxxx_INPUT.                                                                        |
|    Conversion exits are triggered during screen field transports or                              |
|    WRITE statements, field exits during field transports from the                                |
|    screen to the ABAP/4 program.                                                                 |
|    In this connection, the following ABAP/4 statements are not allowed:                          |
|                                                                                |
I hope you try to download the slinkee files and you will notice the call function I performed was no different than the other call function RFC calls that really are working.

Calling Function Module in Update Task

Hello Experts,
Can anyone let me know about
Calling Function Module in Update Task.
Why do we use this " In Update Task " ??
How do we Use ??
What is the Use... ??
Kindly let me know....
Thanks and Regards
Pramod

hi,
Why do we use this " In Update Task " ??
The main update technique for bundling database changes in a single database LUW is to use CALL FUNCTION... IN UPDATE TASK.
How do we Use ??
A typical R/3 installation contains dialog work processes and at least one update work process. The update work processes are responsible for updating the database. When an ABAP program reaches a COMMIT WORK statement, any function modules from CALL FUNCTION... IN UPDATE TASK statements are released for processing in an update work process. The dialog process does not wait for the update to finish. This kind of update is called asynchronous update.
What is the Use... ??
Asynchronous update is useful when response time from the transaction is critical, and the database updates themselves are so complex that they justify the extra system load
Real time scenario.
Suppose a user wants to change an entry in a database table, or add a new one. He or she enters the necessary data, and then starts the update process by choosing Save. This starts the following procedure in the ABAP program:
Firstly, the program locks the database entry against other users, using the enqueue work process (or the message server in the case of a distributed system). This generates an entry in the lock table. The user is informed whether the update was successful, or whether the lock could not be set because of other users.
If the lock is set, the program reads the entry that is to be changed and modifies it. If the user has created a new entry, the program checks whether a record with the same key values already exists.
In the current dialog work process, the program calls a function module using CALL FUNCTION... IN UPDATE TASK, and this writes the change details as an entry in table VBLOG.
When the program is finished (maybe after further dialog steps), a COMMIT WORK statement starts the final part of the SAP LUW. The work process that is processing the current dialog step starts an update work process.
Based on the information passed to it from the dialog work process, the update work process reads the log entries belonging to the SAP LUW from table VBLOG.
The update work process passes this data to the database for updating, and analyzes the return message from the database. If the update was successful, the update work process triggers a database commit after the last database change and deletes the log entries from table VBLOG.
If an error occurred, the update work process triggers a database rollback, leaves the log entries in table VBLOG, flags them as containing errors, and sends a SAPoffice message to the user, who should then inform the system administrator.
The corresponding entries in the lock table are reset by the update work process.
Hope this is helpful, Do reward.

Can we call functional module in a subroutine? Any example?

Can we call functional module in a subroutine? Any example?

sample code....
REPORT ZPL_BDC_PA30.
TABLES : PA0022.
DATA : V_PERNR LIKE PA0022-PERNR,
       V_SLABS LIKE PA0022-SLABS.
DATA : FILENAME TYPE STRING.
DATA : BEGIN OF IT_DATA OCCURS 0,
         PERNR LIKE PA0022-PERNR,       "Personnel Number
         SLABS LIKE PA0022-SLABS,       "Certificate code
         SLABS1 LIKE PA0022-SLABS,      "Certificate code new
       END OF IT_DATA.
DATA : IT_BDCDATA LIKE BDCDATA OCCURS 1 WITH HEADER LINE.
DATA : BEGIN OF IT_ERROR OCCURS 0,
         POS LIKE SY-TABIX,
         TEXT(40),
       END OF IT_ERROR.
PARAMETERS : P_FNAME TYPE DXFIELDS-LONGPATH.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR P_FNAME.
CALL FUNCTION 'F4_DXFILENAME_TOPRECURSION'
EXPORTING
I_LOCATION_FLAG       = ' '
I_SERVER              = '?'
I_PATH                = I_PATH
FILEMASK              = '.'
FILEOPERATION         = 'R'
   IMPORTING
O_LOCATION_FLAG       = O_LOCATION_FLAG
O_SERVER              = O_SERVER
     O_PATH                = P_FNAME
ABEND_FLAG            = ABEND_FLAG
   EXCEPTIONS
     RFC_ERROR             = 1
     ERROR_WITH_GUI        = 2
     OTHERS                = 3
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
START-OF-SELECTION.
FILENAME = P_FNAME.
PERFORM UPLOAD.            "Uploading inputfile to internal table.
PERFORM VALIDATE.          "validating the values
PERFORM POPULATE_BDC.      "Populating bdc internal table
PERFORM ERROR_RECORDS
        TABLES IT_ERROR.     "Error records
*&      Form bdc_fdata
FORM BDC_FDATA USING FNAM FVAL.
CLEAR IT_BDCDATA.
IT_BDCDATA-FNAM = FNAM.
IT_BDCDATA-FVAL = FVAL.
APPEND IT_BDCDATA.
ENDFORM.                    " bdc_fdata
*&      Form bdc_hdata
FORM BDC_HDATA USING PROGRAM SCRNO DYNBEGIN.
CLEAR IT_BDCDATA.
IT_BDCDATA-PROGRAM = PROGRAM.
IT_BDCDATA-DYNPRO = SCRNO.
IT_BDCDATA-DYNBEGIN = DYNBEGIN.
APPEND IT_BDCDATA.
ENDFORM.                    " bdc_hdata
*&      Form upload
FORM UPLOAD .
CALL FUNCTION 'GUI_UPLOAD'
    EXPORTING
      FILENAME                      = FILENAME
     FILETYPE                      = 'ASC'
     HAS_FIELD_SEPARATOR           = 'X'
HEADER_LENGTH                 = 0
READ_BY_LINE                  = 'X'
DAT_MODE                      = ' '
CODEPAGE                      = ' '
IGNORE_CERR                   = ABAP_TRUE
REPLACEMENT                   = '#'
CHECK_BOM                     = ' '
VIRUS_SCAN_PROFILE            = VIRUS_SCAN_PROFILE
NO_AUTH_CHECK                 = ' '
IMPORTING
FILELENGTH                    = FILELENGTH
HEADER                        = HEADER
    TABLES
      DATA_TAB                      = IT_DATA
   EXCEPTIONS
     FILE_OPEN_ERROR               = 1
     FILE_READ_ERROR               = 2
     NO_BATCH                      = 3
     GUI_REFUSE_FILETRANSFER       = 4
     INVALID_TYPE                  = 5
     NO_AUTHORITY                  = 6
     UNKNOWN_ERROR                 = 7
     BAD_DATA_FORMAT               = 8
     HEADER_NOT_ALLOWED            = 9
     SEPARATOR_NOT_ALLOWED         = 10
     HEADER_TOO_LONG               = 11
     UNKNOWN_DP_ERROR              = 12
     ACCESS_DENIED                 = 13
     DP_OUT_OF_MEMORY              = 14
     DISK_FULL                     = 15
     DP_TIMEOUT                    = 16
     OTHERS                        = 17
IF SY-SUBRC <> 0.
    MESSAGE I000(BCTRAIN) WITH 'FILE NOT UPLOADED'.
ELSE.
   MESSAGE I000(BCTRAIN) WITH 'FILE UPLOADED'.
ENDIF.
ENDFORM.                    " upload
*&      Form populate_bdc
FORM POPULATE_BDC .
LOOP AT IT_DATA .
    PERFORM BDC_HDATA USING 'SAPMP50A'
                                '1000'
                                'X'.
    PERFORM BDC_FDATA USING 'RP50G-PERNR'
                             IT_DATA-PERNR.
    PERFORM BDC_FDATA USING 'RP50G-CHOIC'
                             '0022'.
    PERFORM BDC_FDATA USING 'BDC_OKCODE'
                             '=MOD'.
    PERFORM BDC_HDATA USING 'MP002200'
                                 '2000'
                                 'X'.
    PERFORM BDC_FDATA USING 'P0022-SLABS'
                             IT_DATA-SLABS1.
    PERFORM BDC_FDATA USING 'BDC_OKCODE'
                             '=UPD'.
    CALL TRANSACTION 'PA30' USING IT_BDCDATA.
    REFRESH IT_BDCDATA.
ENDLOOP.
ENDFORM.                    " populate_bdc
*&      Form validate
FORM VALIDATE .
    data : num like sy-tabix,
           num1 like sy-tabix.
LOOP AT IT_DATA.
   num = num + 1.
num1 = sy-tabix.
    SELECT PERNR
         FROM PA0022
         INTO V_PERNR WHERE
         PERNR EQ IT_DATA-PERNR.
    ENDSELECT.
    IF SY-SUBRC <> 0.
      MOVE num TO IT_ERROR-POS.
      MOVE 'Invalid Pernr' TO IT_ERROR-TEXT.
      APPEND IT_ERROR.
      DELETE IT_DATA .
    ELSE.
      IF IT_DATA-SLABS IS INITIAL.
        MOVE num TO IT_ERROR-POS.
        MOVE 'Certificate code is initial' TO IT_ERROR-TEXT.
        APPEND IT_ERROR.
        DELETE IT_DATA.
      ENDIF.
    ENDIF.
ENDLOOP.
ENDFORM.                    " validate
*&      Form error_records
FORM ERROR_RECORDS TABLES IT_ERRORS.
FORMAT COLOR COL_GROUP.
WRITE : / 'Error in the following records : ' .
FORMAT COLOR COL_NEGATIVE.
LOOP AT IT_ERROR.
    WRITE : / IT_ERROR-POS,
               IT_ERROR-TEXT.
ENDLOOP.
ENDFORM.                    " error_records

Can we call Function Module from Process Chain?

Hello experts,
I have a small question.
Can we call Function Module(SE37) from Process Chain?
If yes can you please provide some example link?
I m new to BI world.
regards

Hi,
Create one ABAP program and call the function module from that program. Check the link to know how to call a function module from an ABAP program.
http://help.sap.com/saphelp_wp/helpdata/en/d1/801edb454211d189710000e8322d00/content.htm
http://help.sap.com/saphelp_wp/helpdata/en/9f/db98ef35c111d1829f0000e829fbfe/content.htm
Then use process type "ABAP Program" in your process chain and add the program you have created. So then this program will be executed via process chain and this program will call the function module.
Indrashis

Uncatchable exception: BSP calling Function Module

Hi all,
currently i'm facing a very weird problem. My application class calls function module
HR_INFOTYPE_OPERATION. Normally, in case of an error, the function module gives you back a return parameter. But if i call it from my BSP, the processing doesn't leave the function module. It directly throws an exception ERROR_MESSAGE_STATE instead of writing the message into parameter return.
If i call the function module with the same parameters from a report, it works fine and the error message is written to return parameter without throwing an exception.
What am i doing wrong? I don't want that exception and need to go on with filled parameter result.
Regards
Mark-André

Hi MA,
try using ERROR_MESSAGE in the exceptions list, like this.
CALL FUNCTION 'func_name'
     EXPORTING
          string            = text
          pos               = position
     IMPORTING
          string1           = text1
          string2           = text2
     EXCEPTIONS
          string1_too_small = 1
          string2_too_small = 2
          ERROR_MESSAGE     = 3
          OTHERS            = 4.
Cheers
Graham Robbo

What is the use of CALL FUNCTION MODULE - AT BACKGROUND TASK?

Hi experts,
I found Call functional module in background task will make the FM run at the next commit work as some people said. So I have some questions:
1 if we use COMMIT WORK commend, the pending FM will be called? If there are several FMs called at background task, what is the sequence of them? How many conditions will trigger the running of these FMs?
2 Where can I find the log of this pending FMs? In SAP library, it says there are 2 tables. But I checked these tables and can only find the FM name and user of it. And I can not understand content of these tables. It seems one is for the main information of FM, and the other is for the data of the FM, maybe the parameters.
3 If I call a FM in this way, Can I canncel it before the next commit work in some way?
Finally, thanks for reading and help.

HI,
When the COMMIT WORK statement is executed, the function modules registered for the current SAP-LUW are started in the order in which they were registered. ROLLBACK WORK deletes all previous registrations for the current SAP-LUW.
If the specified destination is not available when COMMIT WORK is executed, an executable program called RSARFCSE is started in background processing. By default, this tries to start the function modules registered for a SAP-LUW in their destination every 15 minutes and up to 30 times. These parameters can be changed in the transaction SM59. If the destination does not become available within the defined time, it is recorded in the database table ARFCSDATA as the entry "CPICERR". The entry in the database table ARFCSSTATE is deleted after a standard period of eight days

Third party system call function module/BAPI through RFC to update Z table

Dear Friends,
We have a third party system which directly inserts a Z table in SAP through its programming, which is an auditing issue.
We want the third party system should call function module/BAPI through RFC so that the Z table gets updated.
waiting for inputs..
Thanks,
Kumar

if third party system is capable of making Remote Function call, then writing a Function module & making it remote enable is not difficult task in ABAP.
You may have to prepare specifications first to decide if third party system is going to Read, insert, update, delete records from Zee table.

Why Service Call and why not call Function module Directly in WD ABAP

Hi,
I have created a Webdynpro applications and the logic requires calling avrious Function modules.
Do I need to create Service Call for each Function module or call them directly.
It would be great if you can suggest me under what cases I need to opt for Service call
For example, if I use 'RP_CALC_DATE_IN_INTERVAL', do I need to use Service call or call function module directly.
Note: I have searched forums but could not get the correct answer which I want
Thanks!

The Service Call is really meant to be a wizard/time saver. It has the advantage that it can generate matching context nodes/attributes for the interface of the Function Module you are calling. However everything that the service call does can also be created by hand.
Personally I'm not a fan of what the service call wizard generates. Its good as a time saver or for beginners, but I find I prefer to touch up the code it generates anyway. I much prefer to create a nice reusable model class with its own unit test and then consume this model class (with the service call wizard) from WD. This model class might contain one or more function module calls depending upon what logic I need to access.

Setting to prevent "Function will be started in new session"

Hi all,
I'm focusing following problem / request.
User A is doubleclicking on a Inforecord number inside a puchase order position (ME23N). Now SAP is showing message MEPO014 (Function will be started in new session) and displaying master data of this inforecord in a new "window" (ME13). If the user has already 6 sessions open, he will get a error message "max. sessions ...!". So far so well.
Now the problem:
User B is doing the same, having already 6 sessions open and ME13 will be displayed in same session (window) where he doubleclicked the inforrecord (ME23N).
question:
is there a setting where i can influence the "new session" behaviour of SAP Gui?
plea:
do not post hints like "have you checked User parameters" etc. --- of course i have
If you can simulate what i described on your system you're my "expert"
kind regards
Jörg
26/01/2011
help? anyone ?
Edited by: Jörg Sauterleute on Jan 26, 2011 10:53 PM

Hi Jorg,
Have you checked the following setting?
ME23N-Personal SettingsBasic settings Tab-Envir.info in new session.
Please remove the check mark and save.
Hope it helps.

Call function module in backgrouns task and in update task

Hi Gurus,Pls crear me on the " <b>Call function module in backgrouns task and in update task</b>".
how it works and waht is the link with LUW releated to these .
also heard that commit work statement aslo linked with this.
Pls clarfiy me with expalnation of code.

Hi sridhar,
the explanation already given is correct and good. Small add-on:
All functions called during one LUW with addition IN UPDATE TASK are stored together with their actual parameters in a temporary memory area. The moment a COMMIT WORK is issued, the functions are released to be executed by a so-called update task which is running in the background. This explains why functions called in update task never return anything, no SY-SUBRC and no export or table parameters If a function called in update task raises an exception or runs into an error the calling user will get an express message informing about this. Also, all database updates done by this update process are rolled back to keep consistency.
This proceeding helps to keep database tables consistent and allows the user to keep on doing his work before all database updates are complete. You may have seen messages like "material will be changed" after saving. If you open the same material immediately, you'll get a message "object locked by...<yourself>". This means the update task is still running.
Regards,
Clemens

Error BT616 when calling function module SXPG_COMMAND_EXECUTE in background

Hi All,
We use function module SXPG_COMMAND_EXECUTE with a custom command we defined in SM69 to move files in unix (mv command).
The function module call has worked fine for almost a year and recently we have been seeing an error (BT616) in our job lob (SM37) when the program is run in background. We have not been able to reproduce the error in foreground mode and it seems to be occuring only periodically in the background. (The appropriate SAP authorization objects where assigned to the batch job ID and the steps on the batch job.) We are in the process of setting up the trace flag and performing analysis on the trace log via ST11 to help identify the issue.
After perform analysis on SXPG_COMMAND_EXECUTE, the error is occurring when calling function module SAPXPG_END_XPG for exception 2, system failure, yet function module SAPXPG_END_XPG does not exist. I assume this is a program at the operating system level and is just a signature of the parameters to be passed to the operating system program.
Below is part of the SAP function module SXPG_COMMAND_EXECUTE that is failing.
* Now we have to wait for the termination of the external
* command if the caller wants us to.
    IF TERMINATIONWAIT = 'X'.
      CALL FUNCTION 'SAPXPG_END_XPG'
        DESTINATION DESTINATION
        IMPORTING   EXITSTAT = STATUS
                    EXITCODE = EXITCODE
        TABLES      LOG      = LOG
        EXCEPTIONS COMMUNICATION_FAILURE = 1 MESSAGE MSG
                    SYSTEM_FAILURE        = 2 MESSAGE MSG.
I performed a where used on function module SXPG_COMMAND_EXECUTE, and most of SAP programs call the function module with the parameter TERMINATIONWAIT = 'X', so I assume we should pass X as well.
Any ideas on what could be causing this issue?
Mike Vondran

I also remember I have this kind of issue, as I have some UNIX script at OS( UNIX) level . The problem was with the ID , as it dont have proper authorization at OS level ( UNIX ) . Please check this ID authorization. This could be the one of reasons if youre sure from SAP standpoint.
Hope thisll give you some guide line..
Thanks
Bye

Type error while calling function module with in FOX formula

Hi,
I am getting following error while calling function module from FOX Formula:
"Types of parameter DAY_IN () and variable J_CALDAY(D) are inconsistent"
Following is the code:
DATA    I_CALDAY       TYPE 0CALDAY.
DATA    N_CALDAY       TYPE 0CALDAY.
DATA    KYF              TYPE KEYFIGURE_NAME.
FOREACH   I_CALDAY, KYF.
   CALL FUNCTION SLS_MISC_GET_LAST_DAY_OF_MONTH
      EXPORTING
         DAY_IN = I_CALDAY
      IMPORTING
         LAST_DAY_OF_MONTH = N_CALDAY.
    {KYF, N_CALDAY} = {KYF, L_CALDAY}.
ENDFOR.
Import parameter DAY_IN is of type sy-datum (that inturn is data element SYDATUM of data type DATS - same as 0CALDAY). Not sure why error is being thrown. Any idea? Thanks.
Edited by: SAP_BOY on Dec 4, 2009 5:26 PM

Hi,
I think It will not identify ,though you have (data element SYDATUM of data type DATS - same as 0CALDAY).Check it out by assigning it through a variable of type D.
Data I_CALDAY TYPE D.
Hope it may work out.
Regards,
Indu

CALL Function Module RV_CALL_CHANGE_TRANSACTION in a NEW session/window

Similar Messages

Maybe you are looking for