CRM_ORDER_MAINTAIN not working as RFC

Hi ,
we need to change the msg partner for a support desk msg from webdynpro application.for that we are creating a custom RFC function module, Contains the below coding ,
CRM_ORDER_MAINTAIN
CRM_ORDER_SAVE
BAPI_TRANSACTION_COMMIT
It is successfully changing the business partner ( msg processor ) in the support desk msg . But if we call this function module from webdynpro it is not creating as such.
what could be the reason .
____________ we checked the following
1. we called the RFC from other SAP system . it is not working .
2. we debugged that RFC from R/3 , we found the difference. For the below functional module is not returning any events from R/3 . whereas if we run the FM from solution manager it is exporting events .
CRM_EVENT_PASS_INFO_EXE_OW

Hi,
Did you solve this issue?? if you do? how you do it?
thanks in advanced.

Similar Messages

Mail - Not working in RFC call

Hi,
I have custom IDoc sending from one box to another , Say for example A to B. My problem is if any error found in the data in box B while updating the application document. I am generating a mail using the following code in Box B
      v_length = strlen( v_string ).
      v_hlength = v_length. .
      send_request = cl_bcs=>create_persistent( ).
      try.
          document = cl_document_bcs=>create_document(
                                        i_type    = 'RAW'
                                        i_text = i_content[]
                                        i_subject = v_subject ).
          call method send_request->set_document( document ).
          sender = cl_sapuser_bcs=>create( v_sender ).
          call method send_request->set_sender
            exporting
              i_sender = sender.
          loop at i_recipient.
            translate i_recipient-smtp_addr to lower case.
            recipient = cl_cam_address_bcs=>create_internet_address(
    i_recipient-smtp_addr ).
            call method send_request->add_recipient
              exporting
                i_recipient = recipient
                i_express    = ' '
                i_copy       = ' '
                i_blind_copy = ' '
                i_no_forward = ' '.
          endloop.
          move : 'E' to v_request_status.
          v_status = v_request_status.
          call method send_request->set_status_attributes
            exporting
              i_requested_status = v_request_status
              i_status_mail      = v_status.
          send_request->set_send_immediately( 'X' ).
          send_request->send( ).
          commit work.
        catch cx_document_bcs into bcs_exception.
      endtry.
But if sending the IDoc from A to B the mails are not generated ie not found in SOST . ( I checked the IDoc it showing as Error)
But If i login in Box B and run the same IDoc in Box B thru WE19 and reprocess it generating the mails.
Any info why ?
a®

Any info ?
a®

CRM_ORDER_MAINTAIN not working

Hi Expert !!!!!!
I am using FM CRM_ORDER_MAINTAIN to create activity. I am not getting any error but activity fails to create.
CALL FUNCTION 'CRM_ORDER_MAINTAIN'
   EXPORTING
     it_activity_h                 = it_activity_h
     it_activity_i                 = it_mat_com
     it_product_i                  = it_product
     it_appointment                = it_appointment
     it_partner                    = it_partner_com
*   IMPORTING
*     ET_EXCEPTION                  = et_exception1
   CHANGING
     ct_orderadm_h                 = it_orderadm_h
     ct_orderadm_i                 = it_orderadm_i
   EXCEPTIONS
     error_occurred                = 1
     document_locked               = 2
     no_change_allowed             = 3
     no_authority                  = 4
     OTHERS                        = 5
ls_objects_to_save = iv_guid.
APPEND ls_objects_to_save TO lt_objects_to_save.
CLEAR ls_objects_to_save.
CALL FUNCTION 'CRM_ORDER_SAVE'
    EXPORTING
      it_objects_to_save = lt_objects_to_save
    IMPORTING
      et_saved_objects   = lt_saved_objects
      et_exception       = et_exception
    EXCEPTIONS
      document_not_saved = 1
      OTHERS             = 2.
IF sy-subrc IS INITIAL.
    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        wait = 'X'.
ENDIF.
both FM's CRM_ORDER_MAINTAIN and CRM_ORDER_SAVE are not throwing any exceptions.
Regards,
Rushikesh

You have forgotten about CT_INPUT_FIELDS, which is used for informing which fields you want to maintain.
Fill it also.
Regards

RFC connections do not work after system restart

Hi PI experts!
We're facing a problem with our PI 7.0 system. After each restart of the system, all RFC sender communication channels do not work. When testing the connection in the sending SAP system, the connection test fails. Currently we workaround the issue by manually restarting the RFC adapter after system restart.
Does anybody has any idea how th fix that problem? <<text removed>>
Cheers,
Matthias
Edited by: Matt on Apr 29, 2009 3:26 PM - don't offer points

Mathias,
Your problem is due to the fact that SAP is not up and running when XI restarts.
there is a parameter in RFC adapter that you can modify in order to fix that
Please, see the following link and let me know: /people/community.user/blog/2006/09/21/xi-rfcadapter-reconnect-issue
best regards,
David

File Attributes from App Server by RFC (GET_FILE_ATTRIBUTES does not work )

Hello,
We have an Objects application that is started through an RFC BAPI call from a Java app. The Java app. passes a file to the BAPI. We want to test, as efficiently as possible, if the file is 0 bytes long. We have tried /epsf/get_file_attributes but there is a problem with it being called remotely. We have Remote Enabled the function module. Local tests work fine (GUI User), but when it is called by the Bapi(Technical User) we receive sy-subrc = 2. I think it is referring to a 'Communication Error'.
I found a nice class, CL_GUI_FRONTEND_SERVICES for the workstation server, but nothing comparable for the application server.
Help is greatly appreciated as I am pulling my hair out.
Best Regards,
Mark Lengel

Hello Andreas,
The GET_FILE_ATTRIBUTES fm is also from the EPS Function Group and provides the file size, it just does not work when called from Rfc/Bapi. Won't the GET_DIRECTORY_LISTING fm just return directory info ?
I am afraid I will have to resort to the OPEN, READ, CLOSE DATASET steps in order to check for a zero length file.
Regards,
Mark

RFC adapter in XI 3.0 not working properly with BAPI in R/3 4.6C

Here is the scenario.
An XML file is received from our customer. This file contains purchase order information that is used to create a sales order in our SAP 4.6C system. Once the sales order is created an acknowledgement is generated and this is returned back to our customer in an XML format. This scenario is working perfectly fine in our XI 2.0 system but is not working properly in our XI 3.0 test environment. Our custom function module in R/3 is a wrapper function that uses a standard SAP BAPI to create the sales order. Part of the function module does use the statement
call function 'BAPI_TRANSACTION_COMMIT'
The last thing the BAPI does is call another function module that using an RFC destination that will return and order acknowledgement.
Here is what happens within XI and our SAP system.
The XML file is received and mapped to our imported RFC. The RFC adapter is called and the information is passed onto SAP where our customer function module executed. The sales order is created within SAP without any problems and the second function module is called which references an RFC destination assigned to our XI 3.0 system. The information is sent back to XI and an appropriate file is created for our customer. All seems to be working properly except that when the original RFC is sent from XI to SAP, SAP creates a short dump stating
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryException:" Then it is put back into the que where 5 minutes later it executes again and trys to recreate the sales order in SAP. (again, this same function module executing from XI 2.0 works fine)
I believe I have everything configured properly because the SAP side is being executed and I am successfully passing information back from SAP to XI. However the original function module in SAP is failing with the above error message. It appears that the original function module cannot communicate back with XI. I have had SAP looking at this issue and they have not been successful yet in solving this problem.
Any ideas.
Thanks,
Jim d'Hulst

Hi,
I think the problem is with the send back of acknowledgement to XI. Does the DeliveryException state something about the sender agreement? I guess you are using a statement like below:
CALL FUNCTION 'ZABCD'
destination <tcp/ip destination>
exporting
input = ack.
In that case, check whether the TCP/IP destination is working fine. Also, to be able to exchange message, the structure of the Function Module ZABCD needs to be identified as the sender in XI Configuration (Integration Directory).
Also, check your config with the blog mentioned below:
<a href="/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit">/people/arpit.seth/blog/2005/06/27/rfc-scenario-using-bpm--starter-kit</a>
Regards,
Amitabha

IGS rfc not working BI 7.0

Hi All,
We have upgraded our BWD system from 3.5 to 7.0, in smicm restart j2ee server option is disabled only Icm restart option is enabled. I have checked the services both the SMTP and HTTP are active and HTTP is activated as External also.
I have checked the Http server ->display data: it's showing that ABAP and J2EE configured true but J2ee server operational = false.
If j2ee server is not working plz suggest me how to start the j2ee server.
If j2ee server is not working does IGS RFC work ? presently we are facing the problem with IGS rfc we have given the paramters according to note 844669 in instance profile still no luck .... please suggest..
Thanks,
Subhash.G
Message was edited by:
subhash gadde

Hi Markus,
We have fixed the IGS problem the RFC IGS pointing is wrong destination.
We have given the program IGS.Pjazzsap6 in the RFC destination.
I do not have any information about Pjazzsap6 exactly what does it mean?
our EP dev server which is connecting to BWD is pointing to Pjazzsap6 in IGS destination . Is Pjazzsap6 is kind of program file ? please suggest...
Thanks,
Subhash.G

RFC to SOAP - Not working

Hi
I am working on RFC to SOAP scenorio and the same is working fine, when i execute from XXX client, when the same is executed from YYY client it is giving dump, even i tried changing the communication channel to client YYY
I am getting the following error "lookup of alternativeServiceIdentifier via CPA-cache failed for channel"
Can you pls help
Regards
Madhan D

hi refre this thread too
lookup of alternativeServiceIdentifier via CPA-cache failed for channel
SAP Note - 730870
This alternativeServiceIdentifier error mostly appeared while changing the information of Business Systems ie.e Client information in communication channel.
As the Business system information from SLD will not be matched for the communication details. You are trying to override the metadata information of Business System maintained in SLD. This creates conflicts while connecting with the sender/receiver system
Refer
/people/danny.deroovere/blog/2008/02/26/change-client-in-scenarios-with-sap-business-system
lookup of alternativeServiceIdentifier via CPA-cache failed for channel
alternativeServiceIdentifier: party/service from channel configuration are.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d0a8949b-098d-2910-2b8e-b5e9b7daeb26 Page No
Regards
Abhishek

RFC Function module is not working in program while Background

Hi All,
we have a one program in BI system which is calling RFC function module. it is executing the program in foreground very well. Same program we have executed in background , it is not working at all. Thiis RFC function module exists in R/3 4.6c system.

Hello Raju,
Transactional call of a remote-capable function module specified in func using the RFC interface. You can use the addition DESTINATION to specify an individual destination in dest. If the destination has not been specified, the destination NONE is used implicitly. Character-type data objects are expected for func and dest.
When the transactional call is made, the name of the called function, together with the destination and the actual parameters given in parameter list, are registered for the current SAP LUW in the database tables ARFCSSTATE and ARFCSDATA of the current SAP system under a unique transaction ID (abbreviated as TID, stored in a structure of type ARFCTID from the ABAP Dictionary, view using transaction SM58). Following this registration, the program making the call is continued by way of the statement CALL FUNCTION.
When executing the COMMIT WORK statement, the function modules registered for the current SAP LUW are started in the sequence in which they were registered. The statement ROLLBACK WORKdeletes all previous registrations of the current SAP LUW.
If the specified destination is not available for COMMIT WORK, an executable called RSARFCSE is started in the background. This attempts to start the functional modules registered for an SAP LUW in their destination, every 15 minutes up to a total of 30 times. You can make changes to these parameters using transaction SM59. If the destination does not become available within the given time, this is noted in the database table ARFCSDATA as a CPICERR entry. By default, this entry in database table ARFCSSTATE is deleted after 8 days.
Thanks and Regards,
SAP Shori

Jdbc to rfc to jdbc scenario is not working

Hi...
We have done the JDBC to RFC to JDBC scenario using BPM, it was working fine in the last month. now we started testing the same scenario, that is not working. In SXMB_MONI it is showing only sender data is successful, it is not showing any RFC Receiver data & Jdbc Receiver data. in the CCM also Jdbc Sender CC is showing successfull and it is showing the successful messages also, but in RFC Receiver CC
& JDBC Receiver CC it is not showing any thing.
please help on this...
Regards,
Pasi.

Hi
Check u r RFC response (put external break point)
and check wether it has data
rgds
srini

RFC destination not working

Hi,
I have created a RFC destination in my XI system to connect to another system. But when i try Remote logon, it is not working. I have specified all the required details. Can anybody tell me what is the problem?
Regards,
Divija.

Hi Divija,
If your RFC user is not a dialog user, then you will not be able to log on to the system in the dialog mode. The remote log on will fail in the dialog mode. However, when you use an RFC call, there will not be any problems.
Have u given the user id and client details...
Press System Information->Target information and check if it is giving u information of ur destination system only.
Also see if u have mentioned the host/port number correctly in SM59
I hope u have connection type set to 3 in technical settings, SAVE AS IP address and enter IP address in the Target host.
Load distribution should be set to NO.
Another option go to ST05 and select RFC trace and execute the RFC and then disply the trace.
Also go through these links...
http://help.sap.com/saphelp_nw2004s/helpdata/en/25/76cd3bae738826e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/33/c6e63b60c25767e10000000a11402f/frameset.htm
I hope it helps.....
Regards,
Abhy

RFC SAPXPG_DBDEST_ DBHOST not working

Dear Experts,
RFC SAPXPG_DBDEST_<DBHOST> not working in our Production system (cluster), due to this I am not able to take backup from DB13.
I have updated latest "sapxpg" in /usr/sap/<SID>/exe/run still it is not working.
Any idea????????
Regards,

Po ssible points of this error:
1) After downloaded this file you have to RUN ./root.sh in kernel.
2) check the environment variable for given path of backup.
3) Also check the RFC connection before schedule the job.

RFC working in foreground but not working thru webdynpro abap

Dear all,
I am passing certain parameters to an RFC it works thru foreground but when I pass the same parameters at the click of a submit button the RFC doesn't work. although the RFC importing parameters are getting passed successfully.
Can anyone tell me the reason for this kind of behaviour or what needs to be done to make it work more specifically?
Thanks and regards,
Sonal

I am not sure about the exact reason behind your problem, but you can try following things. I hope it will help.
1) Set break point after RFC call, and try following things:
     i) Check if correct parameters are passed to the RFC i.e. parameters you are passing in test mode, same are also passed
        while running in WDA application
     ii) Compare the return parameters of RFC in test mode and WDA after setting break point if any
2) use 'COMMIT WORK' after RFC call
Regards,
Saket.

Trusted RFC not working for different user , working for same user

Dear All,
I have two SAP system - One Solman (7.0) and another ECC 6.0 (SR3) on HPUX box with Oracle DB (Unicode).
I want to establish Trust relationship between these system.
I have configured the same, as per the following link:
http://help.sap.com/saphelp_nw04/helpdata/en/8b/0010519daef443ab06d38d7ade26f4/content.htm
and note 128447.
My requirement is one user X in solman client 001,
will execute some test plan (Tcode stwb_2) which will take the control to ECC 6.0 client 200, execute the tcode as user Y and come back in Solman again.
The user X (SAP_ALL) exists in Solman - client 001 and user Y (SAP_ALL) exists in ECC 6.0 - client 200.
In ECC 6.0 client 200, I have created a role ZRFCACL with the following and assigned to the user Y (as per the above help / note):
Role : ZRFCACL
Auth. Obj: S_RFCACL
Value assigned to fields are:
     RFC_SYSID : SOL
     RFC_CLIENT: 001
     RFC_USER : X
     RFC_EQUSER: N
     RFC_TCODE : *
     RFC_INFO : *
     ACTVT     : 16
Whenever the user X is trying to execute the test from solman, he is getting the error : "No authorization to log on as trusted system (RC = 0)"
Each time the user is trying the above, in ECC 6.0, the following dump is occuring:
CALL_FUNCTION_SINGLE_LOGIN_REJ under username SAPSYS
I have assigned the role ZRFCACL to user X in Solman also.
Next, I have performed the following check:
created one user M in both system
created the role ZRFCACL2 in ECC 6.0 client 200 as follows and assigned the role to user M:
     Role : ZRFCACL2
     Auth. Obj: S_RFCACL
     Value assigned to fields are:
          RFC_SYSID : SOL
          RFC_CLIENT: 001
          RFC_USER : ''
          RFC_EQUSER: Y
          RFC_TCODE : *
          RFC_INFO : *
          ACTVT     : 16
Assigned SAP_ALL to user M in both system (So the user M in Solman does not have ZRFCACL2).
This time, the trust relationship worked and no dump got generated.
I have also checked the thread Trusted RFC do not work
but unable to resolve the issue.
Any suggestion where the things are going wrong in this / what else I need to check or this is not possible at all?
Thanks in advance for your help.
Sudip

Hi Valdecir,
Thanks for the reply. I am providing the detail of the generated dump below:
Please check in case any clue is there.
Runtime Errors         CALL_FUNCTION_SINGLE_LOGIN_REJ
Date and Time          12.08.2008 18:59:32
Short text
No authorization to logon as trusted system (Trusted RC=0).
What happened?
Error in the ABAP Application Program
The current ABAP program "SAPMSSY1" had to be terminated because it has
come across a statement that unfortunately cannot be executed.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An RFC call (Remote Function Call) was sent with the invalid user ID "98819 "
. Or the calling system is not registered as trusted system in the
target system.
How to correct the error
The error code of the trusted system was 0.
Meaning:
0    Correct logon as trusted system mode
1 No trusted system entry for the calling system "SOL " or the
security key entry for the system "SOL " is invalid
2 User "98819 " does not have RFC authorization (authorization object
(S_RFCACL) for user "98819 " witl client 001.
3    The timestamp of the logon data is invalid
The error code of the SAP logon procedure was 1.
Meaning:
0    Login was correct
1    Wrong password or invalid user ID
2    Locked user
3    Too many attempted logons
5    Error in the authorization buffer (internal error)
6    No external user check
7    Invalid user type
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 16192
EM...... 4189840
Heap.... 0
Page.... 0
MM Used. 1194640
MM Free. 2992576
User and Transaction
Client.............. 000
User................ "SAPSYS"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "489F2BD6C36D0F12E10000000A0A049E"
Program............. "SAPMSSY1"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "SOL"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 001
User................ 98819
Transaction......... "SMSY"
Call Program........."SAPLSRTT"
Function Module..... "SCCR_GET_RELEASE_NR"
Call Destination.... "SM_RD3CLNT200_TRUSTED"
Source Server....... "gcbsolm_SOL_00"
Source IP Address... "10.10.4.206"
Additional information on RFC logon:
Trusted Relationship "X"
Logon Return Code... 1
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPMSSY1" - in
"REMOTE_FUNCTION_CALL".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 67
of the (Include) program "SAPMSSY1".
Source Code Extract
Line
SourceCde
37
endmodule.
38
39
module %_rfcdia_call output.
40
"Do not display screen !
41
call 'DY_INVISIBLE_SCREEN'.
42
perform remote_function_diacall.
43
endmodule.
44
45
module %_cpic_start.
46
if sy-xprog(4) = '%RFC'.
47
perform remote_function_call using rfctype_external_cpic.
48
else.
49
call 'APPC_HD' id 'HEADER' field header id 'CONVID' field convid.
50
perform cpic_call using convid.
51
endif.
52
endmodule.
53
54
55
form cpic_call using convid type c.
56
communication send id convid buffer header.
57
if sy-subrc eq 0.
58
perform (sy-xform) in program (sy-xprog).
59
else.
60
message a800.
61
endif.
62
endform.
63
64
form remote_function_call using value(type).
65
data rc type i value 0.
66
do.
>>>>>
call 'RfcImport' id 'Type' field type.
68
if sy-xprog = 'JAVA'.
69
system-call plugin
70
id 'JAVA' value 'FORW_JAVA'
71
id 'RC'   value rc.
72
if there is no rollout on the JAVA side which
73
rolls both, JAVA and ABAP, we return to the
74
C-Stack and reach this point
75
76
in case there was an rollout, the ABAP-C stack is lost
77
and we jump direkt to this point
78
79
here we trigger the rollout on this Abap side with
80
the following statement
81
system-call plugin
82
id 'JAVA' value 'ROLL_OUT'
83
id 'RC'   value rc.
84
else.
85
perform (sy-xform) in program (sy-xprog).
86
rsyn >scont sysc 00011111 0.
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
1
SY-TABIX
0
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
CPIC and RFC Control
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080812
SY-UZEIT
185932
SY-XPROG
SAPRFCSL
SY-XFORM
READ_SINGLE_LOGIN_DATA
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         SAPMSSY1                            SAPMSSY1                               67
REMOTE_FUNCTION_CALL
1 MODULE (PBO) SAPMSSY1                            SAPMSSY1                               30
%_RFC_START
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name REMOTE_FUNCTION_CALL
%_DUMMY$$
0000
0000
2222
0000
SY-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
SYST-REPID
SAPMSSY1
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
HEADER
000000000000
000000000000
TYPE
3
0000
0003
SY-XPROG
SAPRFCSL
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5455445422222222222222222222222222222222
3102633C00000000000000000000000000000000
%_ARCHIVE
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RC
0
0000
0000
SY-XFORM
READ_SINGLE_LOGIN_DATA
000000000000000000000000000000
000000000000000000000000000000
544455444445444445445422222222
2514F39E7C5FCF79EF414100000000
%_SPACE
0
0
2
0
No.       1 Ty.          MODULE (PBO)
Name %_RFC_START
%_PRINT
000                                                                                0###
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222333222222222222222222222222222222222222222222222222222222222222222222222222222222222223000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
RFCTYPE_INTERNAL
3
0000
0003
Internal notes
The termination was triggered in function "ab_xsignon"
of the SAP kernel, in line 2491 of the module
"//bas/700_REL/src/krn/rfc/absignon.c#9".
The internal operation just processed is "CALY".
Internal mode was started at 20080812185932.
Calling system.....: "SOL "
Caller.............: "98819 "
Calling client.....: 001
RFC user ID........: "98819 "
RFC client.........: 200
Trusted return code: 0
Logon return code..: 1
Transaction code...: "SMSY "
Active state.......: "-782823270"
Note: At releases < 4.0, the information for the caller is not
available.
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x4000000002b43cb0 SignOnDumpInfo + 0x280 at absignon.c:2491 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000002b3f2f0 ab_xsignon + 0xb30 at absignon.c:876 [dw.sapRD3_DVEBMGS00]
(5) 0x4000000002aa4cb0 ab_rfcimport + 0x1ad0 at abrfcfun.c:3599 [dw.sapRD3_DVEBMGS00]
(6) 0x40000000040f4a80 Z8abjcalyv + 0x500 [dw.sapRD3_DVEBMGS00]
(7) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003f538b0 Z9abxeventPKt + 0xb0 at abrunt1.c:281 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003f360a0 ab_dstep + 0x280 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001cb4600 dynpmcal + 0x900 at dymainstp.c:2399 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cab0e0 dynppbo0 + 0x280 at dymainstp.c:540 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fb4de0 TskhLoop + 0x4e20 at thxxhead.c:4518 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(20) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
SAPMSSY1
0
11.04.2005
09:27:15
22528
E
1
Prg
SAPLSCCA
1
05.07.2005
13:10:18
52224
E
2
Prg
SAPRFCSL
0
13.02.2005
17:31:45
17408
E
3
Typ
RFCSYSACL
0
13.02.2005
17:31:45
7168
4
Typ
SYST
0
09.09.2004
14:18:12
31744
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program SAPMSSY1
SYST                                       . .       : :     00004612
\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x0001\0\0\0
Program SAPRFCSL
RFCSYSACL                                  . .       : :     00001760
SOL                             RD3
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
116
CLEA
00
0035
SAPMSSY1
60
117
CLEA
00
0036
SAPMSSY1
60
118
CLEA
00
0037
SAPMSSY1
60
119
MESS
00
001C
SAPMSSY1
60
120
ENDF
00
0000
SAPMSSY1
62
121
00
0000
SAPMSSY1
62
122
PERP
00
0001
SAPMSSY1
64
123
PERP
02
0000
SAPMSSY1
64
124
WHIL
00
0002
0000
0000
0000
0000
0000
0000
SAPMSSY1
66
128
WHIL
00
0003
0000
0000
0000
0000
0000
0000
SAPMSSY1
66
132
BRAN
05
001E
SAPMSSY1
66
133
CALY
00
0003
0038
002A
0005
002B
0000
0000
SAPMSSY1
67
>>>>>
CALY
02
0000
0039
8000
0000
0000
0000
0000
SAPMSSY1
67
141
COMP
00
0002
0010
003A
SAPMSSY1
68
143
BRAF
02
000E
SAPMSSY1
68
144
SRFC
01
0000
003A
003B
SAPMSSY1
69
146
SRFC
01
0000
003C
C000
SAPMSSY1
69
148
SRFC
02
0000
0000
0000
SAPMSSY1
69
150
SRFC
01
0000
003A
003D
SAPMSSY1
81
152
SRFC
01
0000
003C
C000
SAPMSSY1
81
Thanks & Regards
Sudip

Sender RFC is not working

Hi
I am working on RFC to SOAP Scenorio
I configured Sender RFC Communication Channel.
Using the same program id, i created RFC destination.
The RFC Destination is working fine.
When i test it using program, i am getting the
error alternativeServiceIdentifier via CPA-cache
Can you pls help
Regards
Madhan D

hi,
did you configure as per my blog:
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
regards,
Michal Krawczyk

CRM_ORDER_MAINTAIN not working as RFC

Similar Messages

Maybe you are looking for