Automatic remote login at remote function call

Hello,
we have three systems, development, testing and productiv. I want to do a remote function call on the repective other system. But I always get a login window where you have to insert your password for that system. Is there a possibility to do this automatically? Thanks.
Cheers, Lars.

or else in SM59 double click on your destination server and in logon/security tab and give ur username and password and try

Similar Messages

An error occurred when executing a REMOTE FUNCTION CALL.

Dear all,
We have two syetms called DXD and GRD , we have a remote enabled function module in the DXD system , when i am trying to call this Function module from
GRD system it is going for the short dump, and giving the follwing error,
Error analysis
 An error occurred when executing a REMOTE FUNCTION CALL.
 It was logged under the name "RFC_NO_AUTHORITY"
 on the called page.
But i do have the access for the DXD system also, i am really struggling to solve this problem, if any lights are there to help me , i will be thank full for then,
some body suggested for me that we need to maintain the Trusted system tables in the target system.
Thanks & regards
Satya.

first u( user id ) have to get the Authorizations to use RFC ?
object will be like S_RFC or some thing like this.
when u get this kind of error just call /NSU53 then u will come to know which Authorization Object is missing from ur User Profile.
Regards
Prabhu

Data error (invalid data type 17) in a Remote Function Call

Hi,
I am passing 2 select-option tables to RFC.
Tables have structures -
   Table1 SIGN(C1)
               OPTION(C2)
               HIGH(C6)
               LOW(C6)
   Table2 SIGN(C1)
               OPTION(C2)
               HIGH(C20)
               LOW(C20)
At the destination side, I have created two table types which have same structure.
But when I call the RFC , program terminates with error - "Data error (invalid data type 17) in a Remote Function Call"
Not able to understand the reason for this error. Please help.
Thanks,
Sujeet

Hi,
check out this example
[LINK|http://abap.googlar.eu/viewtopic.php?f=5&t=28]
You have several ranges that you can use like RANGE_AUF.
Function example:
FUNCTION zexemple.
*"*"Interface local:
*" IMPORTING
*"     REFERENCE(R_HORA) TYPE FLAG
*"     REFERENCE(R_DIA_1) TYPE FLAG
*"     REFERENCE(P_IDOC) TYPE FLAG
*" EXPORTING
*"     REFERENCE(MSG) TYPE CHAR255
*" TABLES
*"      T_OIFSPBL STRUCTURE OIFSPBL
*"      SL_PBLNR STRUCTURE RANGE_PBLNR
*"      SL_MATNR STRUCTURE RANGE_MATNR
*"      SL_HORA STRUCTURE RANGE_UZEIT
*"      T_ERROS STRUCTURE ZARSTRING
ENDFUNCTION.
Report:
SELECT-OPTIONS: sl_pblnr FOR oirbpblb-pblnr,
                              sl_matnr FOR a361-matnr.
~
Final question:
You are passing the values using TABLES and not IMPORTING right?

CATCHABLE EXCEPTIONS in the remote function call (RFC)

Please tell me what are the CATCHABLE EXCEPTIONS in the remote function call (RFC) and to which exception class do they belong????
Thanks in advance.
Dinesh Dhiman

HI,
With external function calls, the EXCEPTIONS addition of the CALL FUNCTION command can be used to assign return values to the exceptions defined in the interface of the called function module. Class-based exceptions cannot be propagated to the caller from a remotely-called function module, and have the effect of an exception that cannot be handled.
As well as the exceptions defined in the interface of the called function module, an external function call can also have the following predefined exceptions:
The SYSTEM_FAILURE exception is the response to a runtime error that occurs when the remotely-called function module is executed.
The COMMUNICATION_FAILURE exception occurs when the connection to the partner system cannot be established or if the connection is lost during communication.
Note
We strongly recommend that you assign a return value to both these exceptions for every RFC, and that you handle this return value, as otherwise a runtime error will occur in the exception situations in question.
Regards,
Sesh

Remote Function Call

Hi,
I am very much new to RFC, Can anyone help me to suggest some ideas for the following scenario.
1. For the created PA30 screen using webdynpro, i have to create RFC.
2. BAsed on the input from the system and the screen i have to write RFC.
3. Through the RFC i have to update the Tables.
Thanks ,
Vijay
Moderator message : Spec dumping is not allowed, search for available information. Thread locked.
Edited by: Vinod Kumar on Aug 9, 2011 10:28 AM

Hi..,
CALL FUNCTION - RFC
Syntax Forms
Synchroner RFC
1. CALL FUNCTION func DESTINATION dest
 parameter_list.
Asynchroner RFC
2. CALL FUNCTION func STARTING NEW TASK task
 [DESTINATION {dest|{IN GROUP {group|DEFAULT}}}]
 parameter_list
 [{PERFORMING subr}|{CALLING meth} ON END OF TASK].
Transaktionaler RFC
3. CALL FUNCTION func IN BACKGROUND TASK
 [DESTINATION dest]
 parameter_list
 [AS SEPARATE UNIT].
The destination contains the connection parameters for remote function calls. It contains the connection type, the target system and the partner program. Connections that affect SAP systems exclusively can be agreed as trustedsystems. RFC destinations are managed using transaction code SM59. 
regards,
sai ramesh

CALL_FUNCTION_REMOTE_ERROR when calling a remote function call through PI

Hello. Thanks in advance for your perspective on this.
We are developing an interface that runs in an R/3 system and is suppossed to perform a lookup in another R/3 system via a PI 7.0 system.
Here's what we are trying to do, let's call these systems "A", "B", "C" respectively.
R/3 -> PI   -> R/3
The R/3 system (A) executes code, which calls this function module like this:
      CALL FUNCTION 'Z_CHK_MAT' DESTINATION 'XI_RFCADAPTER'
        EXPORTING
          iv_region           = lv_region
          iv_matnr            = ls_matnr-matnr
        IMPORTING
          ev_flg_is_purchased = e_flg_is_purchased.
This code, is set via the "DESTINATION" parameter to use the RFC destination 'XI_RFCADAPTER'. This destination, points to the PI (B) system above.
Anyhow, we're getting a short dump in the R/3 (A) system, which is like this:
CALL_FUNCTION_REMOTE_ERROR
"JCO.Server could not find server function 'Z_CHK_MAT'"
From my analysis, I believe this is because the remote function module Z_CHK_MAT does not exist, in the PI (B) system.
Our developer, believes this should just "pass through" the PI (B) system, and call the function module in the R/3 (C) system.
Any insight on this? In this scenario, does this Function Module need to exist in the PI abap side? Can you give perspective / guidance on this?
Thanks a lot
Steve

No need to exist in PI ABAP side.
Just make sure that:
1. as Michal said, you import it in Integration Repository (and use it in your configurations);
2. the RFC Destination type that points to XI is of type T, not 3;
3. both the RFC Destination & the Sender RFC Adapter (and only them) are using the same Program Id.
Regards,
Henrique.

Refresh a report list after remote function call

Hi,
My customer has a report listing invoices. A non-SAP program calls a remote function creating an invoice with BAPI. My customer wants the list to be refreshed after the invoice is created via RFC or to refresh the list in specified time intervals.
Is there any way to accomplish that task?
thanks,

... or OO, integrate like this
DATA:      ok_code LIKE sy-ucomm.
*       CLASS lcl_event_handler DEFINITION
CLASS lcl_event_handler DEFINITION.
PUBLIC SECTION.
    CLASS-METHODS: on_finished FOR EVENT finished OF cl_gui_timer.
ENDCLASS.                    "lcl_event_handler DEFINITION
CLASS lcl_event_handler IMPLEMENTATION.
METHOD on_finished.
* Start Timer again
    gr_gui_timer->interval = pa_autow.
    CALL METHOD gr_gui_timer->run.
* cause PAI
    CALL METHOD cl_gui_cfw=>set_new_ok_code
      EXPORTING
        new_code = gc_cmd_refresh.
ENDMETHOD.                    "on_finished
DATA:
gr_gui_timer               TYPE REF TO cl_gui_timer,
gr_event_handler           TYPE REF TO lcl_event_handler,
gs_vtyp                    like ts_vtyp.
*======================================================================*
*= Selection screen                          =*
*======================================================================*
PARAMETERS:
pa_autow TYPE flag DEFAULT 'X'.
SELECTION-SCREEN END OF BLOCK date.
*&      Form init_autorefresh
*       Timer starten oder stoppen
FORM init_autorefresh .
IF pa_autow IS NOT INITIAL.
    CREATE OBJECT gr_gui_timer.
    SET HANDLER gr_event_handler->on_finished FOR gr_gui_timer.
    gr_gui_timer->interval = pa_autow.
    CALL METHOD gr_gui_timer->run.
ELSEIF gr_gui_timer IS BOUND.
    gr_gui_timer->cancel( ).
ENDIF.
ENDFORM.                    " init_autorefresh
Regards,
Clemens

AS3/BlazeDS remote function calls

We have a pure as3 - no flex - project which connects to server-side Java. The actionscript will, upon interaction from the user, invoke a Java function on the server side, which will then broadcast out a message to all users. This works when testing locally, but when we put the project onto a remote server, the actionscript code will no longer invoke the Java function.
We are unsure as to why this is: the service xml files are the same, and the files are in the correct locations. In the BlazeDS admin console, whenever we try to call that Java function, it is incrementing the InvocationFaultCount variable for the specified destination. Any suggestions why it won't work online, but will on the local machine?
thanks

Hello Case,
The approach in NCo for this purpose is to use RfcCustomDestination, as already recognized by you. Thus you can challenge the user for his personal password and set those credentials for the logon. Best variant is to provide a repository user and password in the configured destination so that metadata is then read with a user that is restricted to metadata lookup permissions only.
In case the infrastructure would issue a token for the logged on user, one could imagine that with such a token and trust between the ABAP system and the NCo application could do some kind of SSO. However, NCo runtime is not prepared so far to allow such a setup.
Best regards,
Markus

Remote Function Call (RFC) within a BAdI in ECC to CRM

I've a remote enabled FM in a CRM system which I want to call within a BAdI implementation of a ECC system. As a result, the CRM system is the RFC server and the ECC system is the RFC client.
The FM in CRM simply gets the relevant rows of a Z table which, of course, only exists in CRM and passes these rows to the calling program as per parameter supplied by the calling program.
Now the BAdI in ECC is for changing 'Contracts' data in SAP (transactional data) before posting the contracts in the ECC database. The business uses a transaction where a large number of contracts are processed and documents posted in the system - and when this happens the system runs through (calls) the BAdI one contract at a time.
If I call the RFC enabled FM anywhere within this BAdI, it gets the data for one contract only so it reduces a great deal of performance in regards to memory consumption, network load etc. So I want to avoid this and call the RFC FM once instead, if possible.
Is it possible to call this RFC FM once only (to load the CRM Z table data for all contracts) and store it in a global table/area within the instantiated BAdI class (visibility public) so that when the BAdI is called the second time onwards it can read the global table/area by READ TABLE WITH KEY statement and avoid the RFC call for each BAdI call?
I was also thinking about may be using ABAP Shared Memory if this is a possibility in order to avoid the repeated RFC call? But this table on the RFC server changes frequently....so it might not be a good idea? or....??
I would greatly appreciate your inputs and thoughts regarding this; it would be great to hear if someone had had a similar experience.
Cheers,
Sougata.

As the Z table is only updated via a particular program in CRM - we developed and called a RFC enabled FM in that report when its updating the Z table to update the Z table in ECC to keep it in sync.
Short term benefit but might be long term pain if the Z table in CRM is updated by another program/process/application in the future! Not to mention any table field changes in CRM has to be also made in ECC everytime which is again a pain.
This is a workaround and definitely not a full-proof solution - but I guess these days one has to shut up and deliver whatever the customer wants!

Remote function call (RFC) for WS_DELIVERY_UPDATE fails w/o error message

Dear Experts,
Iu2019m using WS_DELIVERY_UPDATE to post goods issue against outgoing delivery. SE37 works fine.
RFC call from external program with the same parameters fails without returning any message.
It aborts during call and after that it becomes invalid.
Also calling BAPI_TRANSACTION_COMMIT does not help.
Any idea why SE37 works fine but RFC fails?
Anything I am missing?
Many thanks
Regards
JW

There could be many reasons, I'd suggest to get your Basis admin involved. Take a look at the ABAP dump (ST22), update termination (SM13) or RFC errors (SM58). Although I doubt you'll find something inside SAP, since it seems that RFC call itself fails.
This function is not a BAPI, so BAPI_TRANSACTION_COMMIT won't do any good. All it does is COMMIT WORK actually.

Generate Idoc from Remote function call

Hi,
Earlier i have done RFC which is been called with JCO and and sends datastream as well xml.
Now my doubt, is it possiible to generate the idoc for external application through RFC call from JCO?
if so, can anyone send me appropriate links or advice on the subject!
My main concern is i can generate the idoc through RFC call basing on the calling parameters,,, but how to pass the idoc structure for them?
for XML i used Export: E_XML TYPE STRING
for data stream: ITAB LIKE ZSTR_ITAB.
Any inputs will be of great helpfull...

Assigned resultant idoc structure to the Table parameter of type EDIDD in created BAPI.

Characters getting lost while calling a remote function

Hi there,
I've got a problem concerning a remote function call.
Situation: System A has a function module ZFM_X with one importing parameter ("text" type string).
System B calls this function module ZFM_X through a remote function call.
It passes a string (containing 521 characters) variable to the importing parameter "text".
Unfortunately, only fragments of the imported text arrive in System A.
The text arriving in System A has the following pattern: The first 256 are correct, following 256 white spaces(blanks) following the last 9 characters of the imported text.
Example:
This is sent by System B to System A through a String variable.
http://xxx.xx.xx.xx:xxxx/servlet/ContentServer?get&pVersion=0046&contRep=PG&docId=4BB4C36F5A0200B9E1008000AC101219&accessMode=r&authId=CN%3DP60&expiration=20100420112054&secKey=MIH3BgkqhkiG9w0BBwKggekwgeYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGBxjCBwwIBATAZMA4xDDAKBgNVBAMTA1A2MAIHIAgIKARFNDAJBgUrDgMCGgUAoF0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTAwNDIwMDkyMDU0WjAjBgkqhkiG9w0BCQQxFgQUItgHQiYkW9BkScWnoMPkZiuCGSMwCQYHKoZIzjgEAwQuMCwCFGPGseHQSPV2%2F75OVMF2yMFzwfTLAhQgPRMvivyuii4gZ%2BJSKonPRsF1XA%3D%3D
At System A the following text arrives
http://xxx.xx.xx.xx:xxxx/servlet/ContentServer?get&pVersion=0046&contRep=PG&docId=4BB4C36F5A0200B9E1008000AC101219&accessMode=r&authId=CN%3DP60&expiration=20100420112054&secKey=MIH3BgkqhkiG9w0BBwKggekwgeYCAQExCzAJBgUrDgMCGgUAMAsGCSqGSIb3DQEHATGBxjCBwwIBATA 1XA%3D%3D
It definitely looks like a unicode problem. Oddly, we have another system constellation which is exactly the same as System A/B where we are doing this, and its working perfectly fine.
I hope you are not stunned by this wall of text, but any help is totally appreciated!
Edited by: Erik Nagler on Apr 20, 2010 11:54 AM

Hi,
I tried it with String type and Character type (CHAR1024).
Both dont work.
As far as the unicode test is concerned:
Sysem A is a unicode System whereas System B is a non-unicode system.
I tried to change the Radiobutton to "unicode" in sm59, but I can't.
It is uneditable, even though I am in change mode.
[>>Picture<<|http://img90.imageshack.us/img90/2006/unicode.png]

Regarding the Remote Function Module

hi,
Can any body can provide the brief information regarding the Remote Function Module.
1)How to create the remote function module
2)how it differ from the normal function module
3)any special features about this.
Thanks in advance

Hi
RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;
and you will be passing an Import parameter DESTINATION to it.
Other code and usage will be similar to any fun module;
Have a look at any fun module in SE37 to understand better about the different components of Fun modules;
Refer this link:
http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm
check out the following link it might help you
http://help.sap.com/printdocu/core/Print46c/de/data/pdf/BCFESDE2/BCFESDE2.pdf
Function Modules;
Check this matter.
Function Modules are Global ABAP programs created by SAP for reusable purpose.they have IMPORT,EXPORT and TABLE parameters, and EXCEPTIONS to through when error occurs.
You can create them from TCode SE37.
Go through the following doc:
Function modules are cross-program, reusable procedures that are organized into function groups, and whose functions are implemented between the statements FUNCTION and ENDFUNCTION. Function modules and their interfaces are created in the Function Builder.
Function Module Interfaces
The parameter interface of a function module is defined in the Function Builder. It includes the definition of interface parameters and the specification of exceptions that can be triggered by a function module. The Function Builder automatically generates comment lines below the FUNCTION statement in the source code of the function module, which represent the interface of the function module with the following syntax:
Syntax
... [IMPORTING parameters]
[EXPORTING parameters]
[CHANGING parameters]
[TABLES table_parameters]
[{RAISING|EXCEPTIONS} exc1 exc2 ...]
The syntax and semantics of IMPORTING, EXPORTING, CHANGING, RAISING, and EXCEPTIONS mainly correspond to the definition of method interfaces with [CLASS-]METHODS. The additional option of defining table parameters using TABLES is obsolete.
Interface parameters
The interface parameters are defined on the relevant tab pages in the Function Builder.
IMPORTING parameters are input parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input parameter. The content of the actual parameter is passed to the input parameter when the call is made. The content of an input parameter for which 'pass by reference' is defined cannot be changed in the function module.
EXPORTING parameters are output parameters. When the function module is called, a suitable actual parameter can be specified for every output parameter. The content of an output parameter that is defined for 'pass by value' is transferred to the actual parameter if the function module is completed without errors. An output parameter that is defined for pass by reference is not initialized when the function module is called.
CHANGING parameters are input and output parameters. When the function module is called, a suitable actual parameter must be specified for every non-optional input or output parameter. When the function module is called, the content of the actual parameter is passed to the input/output parameter, and when the function module is completed, the content of the input/output parameter is passed to the actual parameter.
TABLES parameters are table parameters. Table parameters are obsolete CHANGING parameters that are typed as standard tables with a header line. If an internal table without a header line or a table body is passed as an actual parameter to a formal parameter of this type, an empty local header line is generated in the function module. If an internal table with a header line is used as an actual parameter, both the table body and the header line are passed to the function module. Pass by value is not possible in formal parameters defined using TABLES. Formal parameters defined with TABLES can be replaced by formal parameters defined with CHANGING. A local work area can be created for the internal table in the function module by using the addition LIKE LINE OF itab of the DATA statement.
Exceptions
The exception of a function module are defined on the Exceptions tab page in the Function Builder. Here you can select exception classes to define whether class-based exceptions are declared or non-class-based exception are defined. Class-based exceptions are represented in the above syntax by RAISING, and non-class-based exceptions are represented by EXCEPTIONS.
The addition RAISING is used to declare class-based exceptions that can be propagated from the function module to the caller. Exceptions in the categories CX_STATIC_CHECK and CX_DYNAMIC_CHECK must be explicitly declared, otherwise a propagation can lead to an interface violation. A violation of the interface leads to the treatable exception CX_SY_NO_HANDLER. Exceptions of the category CX_NO_CHECK are implicitly always declared. The declaration of exceptions of the category CX_STATIC_CHECK is statically checked in the syntax check. For exceptions of the category CX_DYNAMIC_CHECK, the check is not performed until runtime. In a function module in which class-based exceptions are declared with the RAISING addition, the statement CATCH SYSTEM-EXCEPTIONS cannot be used. Instead, the relevant treatable exceptions should be handled in a TRY control structure.
The addition EXCEPTIONS is used to define a list of non-class-based exceptions that can be triggered in the function module using the statements RAISE or MESSAGE RAISING. Exceptions defined in this way - as with formal parameters - are bound to the function module and cannot be propagated. If an exception of this type is triggered in a function module, and no return value has been assigned to it with the homonymous addition EXCEPTIONS of the CALL FUNCTION statement when the call was made, this leads to a runtime error.
Note
For new developments after release 6.10, SAP recommends that you work with class-based exceptions that are independent of the function module.
RFC is a technology which is used to access a functions (Modules) from
the remote systems.
If a function module is set as remote enabled which can be access from
the remote system via RFC.Eg: U can access the Remote enabled function modules in ur VB,Webdynpro,Java,Visual composer program.
A function module can be set as remote enabled by SE37->Go to ur FM->click the option Button "remote enabled".
But Normal function modules can not accessd from the remote system.
Good Example for RFC enabled function module is : BAPI(Business Application Programming Interface)
Note: All BAPIs are Remote enabled but not all remote enabled function modules are BAPI.
CALLING A FUNCTION MODULE:
1)In U ABAP Editor --> Click "Patter" ---> Selection Option Button "Call Function"
--> Write the Corresponding FM name --> Hit Enter
2)The appropriate import ,export Parameters will be displayed in ur editor
3)Pass the Values Here.
Also check these links.
http://www.geocities.com/victorav15/sapr3/abapfun.html
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
Check this link:
http://help.sap.com/saphelp_erp2004/helpdata/en/9f/db988735c111d1829f0000e829fbfe/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/43/41341147041806e10000000a1553f6/frameset.htm
See the following links:
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_erp2005vp/helpdata/en/9f/db970e35c111d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/26/64f623fa8911d386e70000e82011b8/content.htm
Reward points for useful Answers
Regards
Anji

Dump problem while remote FM call

Hello Experts,
In R3 system there is a RFC Fm Z_SALESORDER_CREATE which is wrapper of standard FM SD_SALESDOCUMENT_CREATE. When we do remote call from CRM system for Z_SALESORDER_CREATE. Its given dump as follows:
Short text
    "Unable to interpret 2,00 as a number."
What happened?
    Error in the ABAP Application Program
The current ABAP program "Z_CREATE_ORDER_WITH_JOB_VRNT" had to be terminated
     because it has
    come across a statement that unfortunately cannot be executed.
The error occurred during an RFC call to another system.
    In the target system, a short dump has been written as well.
    More detailed information on the error cause can be found there.
Error analysis
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name "CONVT_NO_NUMBER"
    on the called page.
We are not using 2,00 anymore...it is something changed format while compiling..
It cause dump in R3 also..dump desc in r3 as follows
Unable to interpret " 2,00" as a number.
What happened?
Error in ABAP application program.
The current ABAP program "SAPLSTS4" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
Error analysis
An exception occurred. This exception is dealt with in more detail bel
. The exception, which is assigned to the class 'CX_SY_CONVERSION_NO_NUMBER
was neither
caught nor passed along using a RAISING clause, in the procedure
"CONVERSION_EXIT_TSTRG_OUTPUT" "(FUNCTION)"
Since the caller of the procedure could not have expected this excepti
to occur, the running program was terminated.
The reason for the exception is:
The program attempted to interpret the value " 2,00" as a number, but
since the value contravenes the rules for correct number formats,
this was not possible.
How to correct the error
The exception must either be prevented, caught within the procedure
"CONVERSION_EXIT_TSTRG_OUTPUT"
"(FUNCTION)", or declared in the procedure's RAISING clause.
To prevent the exception, note the following:
Integers are represented in ABAP using a sequence of digits and, in so
cases, a preceding sign.
The system offers the following options for displaying floating point
numbers:
[sign][mantissa]E[sign][exponent]
[sign][whole number part].[fractional part]
e.g. -12E+34, +12E-34, 12E34, 12.34
If the error occurred in one of your own programs or in an SAP program
that you modified, try to correct it yourself.
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:
"CONVT_NO_NUMBER" CX_SY_CONVERSION_NO_NUMBERC
"SAPLSTS4" or "LSTS4U01"
"CONVERSION_EXIT_TSTRG_OUTPUT"
Please help me to solve ths problem as soon as possible..
thanks in advance for you quick response.
Anutosh

Hi
Check your defined data types which you are passing to FM and exact FM data types.
I hope that's the problem .
Regards,
Sree

Function called IN BACKGROUND TASK goes to work process DIA, not BGD

I'm calling a function IN BACKGROUND TASK
In SM50, I see it running in a DIA work process.
I want it to run in a BGD work process.
Can this be done? If so, how? If not, why not?

Hi...
It looks like, it will always run in DIA process and not Background process...I am not sure that we can change the work process
Check the below link..
http://help.sap.com/saphelp_40b/helpdata/pt/69/c24f864ba111d189750000e8322d00/content.htm
What is written in the link is...
"Background updates (CALL FUNCTION IN BACKGROUND TASK) represent a variant of remote function call that is synchronous with the end of a transaction (COMMIT WORK). In background updating, an update is run in another dialog work process that may be in the same or in another application server and R/3 System. Because such updates run in their own LUWs, they may start only after all critical updates have been completed. Otherwise, it would not be possible to roll back background changes in the event of an error in another update component. "
IF you get the answer of whether we can change the work process then please let us know...

Automatic remote login at remote function call

Similar Messages

Maybe you are looking for