Paramenters to be given in RFC as a sender
Hi,
Pl Let me know the parameters to be given in RFc as sender.
Also Pl Explain TCP/Ip,ABAP ,HTTP.. ..connections in detail
Thanks
Srini
HI,
Pl Let me know the parameters to be given in RFc as sender.
- First create the TCP/IP connection at SAP R/3 end
tcode : sm59 , enter the any destnation name , type of connection : T
Enter the description and select the Register server Program radiobutton.
Enter the any program id.
Getway host of R/3 server and Gateway service is : sapgw<instance number>
Next create Sender RFC communcation channel in ID.
select adapter type : IDOC.
application server : r/3 server name
Program id : which is created above (R/3 tcp/ip program id)
Gateway service, username & pwd also.
save and activate..then monitor the status of sender rfc in adapter monitoring whether sender rfc created up and running.
Regards,V
Venu.
Similar Messages
-
RFC error when sending logon data
Hi;
We cannot configure the STMS of our development system. When we try to
configure it, system gives an error message: Errors during distribution
of tp configuration; TMS Alert Viewers tells us
RFC_COMMUNICATION_FAILURE: RFC communications error with
system/destination TMSADM-FKT.DOMAIN_FKT RFC error when sending logon
data and READ_PROFILE_FAILED:File
erptest\sapmnt\trans\bin\TPPARAM
could not be opened for reading (No such file or directory).
Is there any advise for solution?
Best regards
Noyan
PS: Please find the profiles below:
START:
#.* Start profile START_DVEBMGS00_erptest *
#.* Version = 000006 *
#.* Generated by user = BASIS *
#.* Generated on = 30.12.2010 , 15:40:55 *
generated by R3SETUP
SAPSYSTEMNAME = FKT
INSTANCE_NAME = DVEBMGS00
SAPSYSTEM = 00
SAPGLOBALHOST = erptest
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
start database
#_DB = strdbs.cmd
#Start_Program_02 = immediate $(DIR_EXECUTABLE)\$(_DB) FKT
start message server
#_MS = msg_server.exe
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start IGS
Start_Program_05 = local $(DIR_EXECUTABLE)$(DIR_SEP)igswd$(FT_EXE) -mode=profile pf=$(DIR_PROFILE)$(DIR_SEP)FKT_DVEBMGS00_erptest
start application server
#_DW = disp+work.exe
#Start_Program_04 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS
General parameters for starting the system
#parameter created by: BASIS 24.12.2007 23:53:27
#SAPSYSTEM = 00
#parameter created by: BASIS 24.12.2007 23:53:27
#SAPSYSTEMNAME = FKT
#parameter created by: BASIS 24.12.2007 23:53:27
#INSTANCE_NAME = DVEBMGS00
#parameter created by: BASIS 24.12.2007 23:53:27
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
#parameter created by: BASIS 24.12.2007 23:53:27
#SAPGLOBALHOST = erptest
Start database
#parameter created by: BASIS 24.12.2007 23:53:27
_DB = strdbs.cmd
#parameter created by: BASIS 24.12.2007 23:53:27
Start_Program_01 = immediate $(DIR_EXECUTABLE)\$(_DB) $(SAPSYSTEMNAME)
Start message server
#parameter created by: BASIS 24.12.2007 23:53:27
MS = msgserver.exe
#parameter created by: BASIS 24.12.2007 23:53:27
Start_Program_02 = local $(DIR_EXECUTABLE)\$(_MS) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
Start applications server
#parameter created by: BASIS 24.12.2007 23:53:27
_DW = disp+work.exe
#parameter created by: BASIS 24.12.2007 23:53:27
Start_Program_03 = local $(DIR_EXECUTABLE)\$(_DW) pf=$(DIR_PROFILE)\FKT_DVEBMGS00_erptest
DEFAULT:
SAPDBHOST = ERPTEST
dbms/type = mss
dbs/mss/server = ERPTEST
dbs/mss/dbname = FKT
dbs/mss/schema = fkt
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPFQDN = tr.delta.is
SAPLOCALHOSTFULL = $(SAPLOCALHOST).$(SAPFQDN)
SAPDBHOST = erptest
SAPTRANSHOST = erptest
DIR_TRANS =
$(SAPTRANSHOST)\sapmnt\trans
#DIR_TRANS = D:\usr\sap\trans
DIR_PROFILE = D:\usr\sap\FKT\SYS\profile
SAP Message Server for ABAP
rdisp/mshost = erptest
rdisp/sna_gateway = erptest
rdisp/sna_gw_service = sapgw00
rdisp/vbname = erptest_FKT_00
rdisp/enqname = erptest_FKT_00
rdisp/btcname = erptest_FKT_00
rdisp/msserv = sapmsFKT
rdisp/msserv_internal = 3900
rdisp/bufrefmode = sendoff,exeauto
login/system_client = 200
#GUVENLIK PARAMETRELERI
login/password_expiration_time = 90
login/min_password_lng = 6
#parameter created by: BASIS 25.03.2004 08:41:25
rdisp/gui_auto_logout = 10800
#parameter created by: BASIS 25.03.2004 08:37:47
#old_value: 3 changed: BASIS 25.03.2004 08:42:38
login/fails_to_user_lock = 6
#validasyon geregi, g#venligi artirma ama#i - check active but no check for SRF
#parameter created by: BASIS 16.06.2007 17:35:41
#old_value: 2
#changed: BASIS 14.05.2008 15:24:55
auth/rfc_authority_check = 1
#otomatik unlocki iptal eder
#parameter created by: BASIS 10.11.2006 17:47:15
login/failed_user_auto_unlock = 0
#AUDIT PARAMETRELER?
#old_value: changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_day = 1996800000
#old_value: 1000000000 changed: BASIS 20.04.2005 17:17:01
#old_value: 0 changed: BASIS 20.04.2005 17:19:12
rsau/max_diskspace/local = 2048000000
#old_value: 2000000000 changed: BASIS 28.03.2005 23:17:11
#old_value: 2 changed: BASIS 29.03.2005 12:09:14
#old_value: 0 changed: BASIS 20.04.2005 17:13:37
rsau/max_diskspace/per_file = 665600000
rsau/enable = 1
rsau/local/file = D:\usr\sap\FKT\DVEBMGS00\log\++++++++######..AUD
rsau/selection_slots = 12
#rec/client = ALL
DIR_AUDIT = D:\usr\sap\FKT\DVEBMGS00\log
FN_AUDIT = ++++++++######..AUD
#DIL PARAMETRELERI
#Turkish codepage settings
abap/import_char_conversion = 0
install/codepage/db/non_transp = 1610
install/codepage/db/transp = 1610
zcsa/installed_languages = DET
#zcsa/system_language = E
zcsa/system_language = T
zcsa/second_language = E
install/codepage/appl_server = 1610
#OS dependent
abap/locale_ctype = Turkish_turkey.28599
#DIR_PUT = D:\usr\sap\FKQ\upg\abap
*** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/msserv_internal = 3900
#system/type = ABAP
INSTANCE:
SAPSYSTEMNAME = FKT
SAPGLOBALHOST = erptest
SAPSYSTEM = 00
INSTANCE_NAME = DVEBMGS00
DIR_CT_RUN = $(DIR_EXE_ROOT)\$(OS_UNICODE)\NTAMD64
DIR_EXECUTABLE = $(DIR_INSTANCE)\exe
icm/server_port_0 = PROT=HTTP,PORT=80$$
SAP Message Server parameters are set in the DEFAULT.PFL
ms/server_port_0 = PROT=HTTP,PORT=81$$
#rdisp/wp_no_dia = 10
#rdisp/wp_no_btc = 3
#rdisp/wp_no_enq = 1
#rdisp/wp_no_vb = 1
#rdisp/wp_no_vb2 = 1
#disp/wp_no_spo = 1
rdisp/wp_no_dia = 12
rdisp/wp_no_vb = 3
rdisp/wp_no_vb2 = 0
rdisp/wp_no_enq = 1
rdisp/wp_no_btc = 3
rdisp/wp_no_spo = 1
#PERFORMANS PARAMETRELERI
#parameter created by: SAP* 08.08.2001 10:30:18
abap/fieldexit = yes
#parameter created by: ALPER 13.10.2000 18:24:16
install/collate/active = 1
rdisp/max_wprun_time = 25000
MEMORY_NO_MORE_PAGING dump nedeniyle
#parameter created by: BASIS 27.12.2006 17:00:22
rdisp/PG_MAXFS = 262144
abap/heap_area_nondia = 2000000000
rdisp/PG_SHM = 16384
rdisp/ROLL_SHM = 32768
#'STORAGE_PARAMETERS_WRONG_SET' or 'TSV_TNEW_PAGE_ALLOC_FAILED'
#Note 552209 - Maximum memory utilization for processes on NT/Win2000
#parameter created by: BASIS 30.10.2007 10:57:24
#abap/heap_area_nondia = 50000
#parameter created by: BASIS 30.10.2007 10:58:54
#rdisp/PG_SHM = 0
#parameter created by: BASIS 30.10.2007 10:58:27
#rdisp/ROLL_SHM = 625
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:49:57
dbs/mss/stats_on = 1
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:49:33
dbs/oledb/stats_on = 1
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:48:23
dbs/oledb/add_procs = 8
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:47:29
rsdb/esm/max_objects = 2000
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:47:03
rsdb/otr/buffersize_kb = 4096
#EWA report 12.2007
#parameter created by: BASIS 03.01.2008 19:46:21
rsdb/esm/buffersize_kb = 4096
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:18:14
ztta/parameter_area = 16000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:16:43
enque/table_size = 10000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:16:20
gw/max_sys = 2000
#Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:16:01
gw/max_overflow_size = 25000000
#Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:15:19
rdisp/max_comm_entries = 2000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:14:48
rdisp/tm_max_no = 2000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:14:20
gw/max_conn = 2000
Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:13:42
rdisp/max_arq = 2000
#Eyl#l 2006 EWA raporu
#parameter created by: BASIS 24.11.2006 13:12:57
ztta/roll_area = 3500000
#parameter created by: BASIS 18.05.2005 09:20:25
#old_value: 90 changed: BASIS 18.05.2005 09:22:25
rdisp/max_hold_time = 300
#parameter created by: BASIS 20.08.2003 12:10:20
#old_value: 6144
#changed: BASIS 03.01.2008 19:42:10
rsdb/obj/buffersize = 20000
#parameter created by: BASIS 20.08.2003 12:09:48
#old_value: 6000
#changed: BASIS 03.01.2008 19:42:59
rsdb/obj/max_objects = 20000
note 103747
#parameter created by: BASIS 08.07.2003 20:42:11
#old_value: 250000
#changed: BASIS 30.10.2007 10:56:17
#abap/buffersize = 100000
#changed: BASIS 03.01.2008 19:40:36
#abap/buffersize = 300000
#by: BASIS 12.06.2008
abap/buffersize = 400000
note 103747
#parameter created by: BASIS 08.07.2003 20:41:32
#zcsa/presentation_buffer_area = 20000000
#64 bite gectikten sonra by: BASIS 10.06.2008
zcsa/presentation_buffer_area = 30000768
note 103747
#parameter created by: BASIS 08.07.2003 20:40:55
rsdb/ntab/ftabsize = 30000
note 103747
#parameter created by: BASIS 08.07.2003 20:40:12
rtbb/max_tables = 500
note 103747
#parameter created by: BASIS 08.07.2003 20:39:15
#old_value: 20000
#changed: BASIS 03.01.2008 19:41:29
#rtbb/buffer_length = 30000
#64 bite gectikten sonra by: BASIS 10.06.2008
rtbb/buffer_length = 50000
note 103747
#parameter created by: BASIS 08.07.2003 20:38:26
zcsa/db_max_buftab = 10000
note 103747
#parameter created by: BASIS 08.07.2003 20:37:37
#zcsa/table_buffer_area = 50000000
#64 bite gectikten sonra by: BASIS 10.06.2008
#zcsa/table_buffer_area = 89000000
by: BASIS 12.06.08
zcsa/table_buffer_area = 99000000
note 103747
#parameter created by: BASIS 08.07.2003 20:36:54
sap/bufdir_entries = 10000
note 103747
#parameter created by: BASIS 08.07.2003 20:36:12
rsdb/cua/buffersize = 8000
#note 103747
#parameter created by: BASIS 08.07.2003 20:34:46
#old_value: 5000 changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/sntabsize = 5500
#parameter created by: BASIS 08.07.2003 20:33:56
#note 103747
#old_value: 10607 changed: BASIS 08.07.2003 20:34:58
#old_value: 10000 changed: BASIS 08.07.2003 20:35:39
rsdb/ntab/irbdsize = 11000
#note 103747
#parameter created by: BASIS 08.07.2003 20:32:18
rsdb/ntab/entrycount = 40000
#old_value: 2076 changed: BASIS 28.06.2005 19:36:21
#old_value: 5735 changed: BASIS 28.06.2005 19:40:01
PHYS_MEMSIZE = 4096
#64 bite gectikten sonra by: BASIS 10.06.2008
abap/heaplimit = 40894464
abap/heap_area_total = 2000683008
ztta/roll_extension = 2000683008
em/blocksize_KB = 4096
*** UPGRADE EXTENSIONS (RELEASE "701") ***
#rdisp/elem_per_queue = 2000
#auth/auth_number_in_userbuffer = 9000
#snc/enable = 0Hi Srikishan;
You are right. The problem was releated with secstore. I found a SAP note ( Note 1532825 - Deleting SECSTORE entries during system export/system copy). I created the program which ise mentioned in the note and than run it. After that everything seems ok now.
Thanks for your help and interest
Best regards
Noyan -
Hi Experts,
We have a business scenario wherein I have to execute the RFC function(async) from an ABAP in R/3 and update the data in DB2 tables(async).
I am using RFC as sender(async) and JDBC as receiver(async). I configured/registered the RFC connection in SM59 and used the same program id in RFC sender adapter. I tested the connection in standalone mode, it is working.
The RFC function when I imported will have a request and a response. The data that I require to send to JDBC adapter is in the response. So I tried to use RFC response and created a message interface. Then I used that in my interface mapping and in the sender & receiver agreements. In the message mapping I used response that was imported.
I get an error message saying sender agreement not found. The as per OSS note 730870 I changed the sender agreement to use RFC function as sender interface, I cannot use this function module for my mapping, as it does not contain the response.
Am I doing something wrong. Can somebody show me some direction.Hi Srinivas ,
If you want to capture the response of an RFC execution in XI and then map this response to another structure(In ur case a JDBC structure) inside XI message mapping , then you will have to use the RFC reciever adapter of XI and NOT the RFC sender adapter.If you use the RFC sender adapter, it means that your SAP system is acting as an RFC CLIENT, what happens is the REQUEST structure in your RFC destination will be converted to RFC-XML by the RFC sender adapter of XI and is available for furthur processing.
But then, If you want to send the RESPONSE structure of an RFC to XI , one way is to execute the RFC in SAP(without passing this thru XI), now you have to pass the result of this RFC execution to XI by assigning it to a request structure of another RFC in your ABAP code and pass it to XI using RFC sender adapter.
If not , you can use a dummy RFC in SAP to send a trigger to XI , execute the actual RFC in XI using RFC reciever adapter , capture the response , map it to ur JDBC structure and you are done.
May be you can give a try on these lines. As for the error , you can chk these threads and see if it helps
com.sap.aii.af.ra.ms.api.DeliveryException
"call to messaging system failed: com.sap.aii.af.ra.ms.api.DeliveryExceptio
RFC Sender Adapter error " Call to messaging failed"
Thanks
Saravana -
hi
can any one provide me with some scenarios having
idoc and rfc as senders.Hi
To Configure the RFC to FILE scenario ,Proceed as Follows
a. Create an RFC Destination to XI in transaction code (SM59)
b. Create new destination of type T (TCP/IP)
c. Make sure you select Registered Server Program option before writing your program ID
d. Write you program ID (remember it's case-sensitive)
e. In the gateway host and gateway service write the values of your Application system - business system (not the XI server)
Step2:Repository
1) From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2) Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
From the list of Software Component Versions, Choose your own software component version .Click Import.
3) On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
The namespace is ur:rfctofile
4) Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
After this specify the connection parameters to the R/3 system:
4.1) System IS :sapfox
4.2) Client IS :800
Then Save it. The new namespace will be visible under software component version node in the left frame.
Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3) Application server:172.25.5.7
4.4) System number: 00
4.5) User name:developer
4.6) Password: Password of Sap R/3 system.
Then click continue .You will find IDOC and RFC node. Click on this node and select the Idoc or Rfc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the Rfc and Idoc will be available into XI as Message types. So no need to create any Rfc or Idoc Structure. We need to create a structure for file only.
5). Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6) Create new data types.
6.1) Right click on Data types and select New.
Your Data Type is. dt_file
In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
Save the object.
6.2) The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
no need to create Data types. They are imported directly as Message types.
6.3) To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
Select the following.
6.3.1) Category: XSD.
6.3.2) Messages: From All Available Global Elements.
6.3.3) File:
Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7). Create a new Message Type.
7.1) In the left hand frame under Interface objects, right click on the Message types and select new.
7.2) Give a suitable name to the Message type.(MT_ messagetype).
7.3) For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
Save it.
8). Create a Message interface
8.1) In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2). The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
Save it.
9) . Create a graphical mapping between the target document and the sender .
9.1) In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2) As Source message select your own Message type.You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- > Namespace->Imported Objects.
9.3) As Target Message you can choose your Rfc .Choose Search for Integration Object.
9.4) Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5) Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the Source fields to the respective Target Fields.
Save It.
9.6) You can also Test your Mapping by selecting the 'Test Tab'.
9.7) Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10). Create an Interface Mapping.
10.1) In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2) Source interface : Your Outbound Interface (The Source document(Rfc) interface).You can Choose Search for Integration Object.
10.3) Target interface: Your Inbound Interface( The Target document interface).
Then Select 'Read Interface' and Assign your 'Mapping Program' .
Mapping Program: Your Message mapping.
Then Save it.
11.) Finally , in the left hand frame ,go to your change list and Activate it
STEP 3: Directory
1) From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
Create a Scenario Object
2). The First Step is to create a Scenario Object
This will serve as container for all your configuration work. Create and save a scenario object
3) In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) . Create a Communication Channel.
6). Expand your service and right click on Communication Channel. Name your Communication Channel
Here we need to configure the adapter.
Since the Sender is 'RFC', Specify the following Parameters
For the adapter type , use the F4 help and select RFC.
Specify Sender since the adapter will be sending messages to XI
Specify the following parameters.
Transport Protocol: RFC
Message Protocol: RFC(RFC XML )
Adapter Engine: Integration Server
Adapter status: Active
RFC Server Parameter:
Application Server(Gateway):172.25.5.7
Application Server Service(Gateway Service): sapgw00
Program Id: Id of Registered server program ( it is case sensititve)
And the adapter is configured. Save it
Since the Receiver is File , Specify the following Parameters
6.1 For the adapter type , use the F4 help and select FILE.
6.2 Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3 Specify the following parameters.
Transport Protocol: File Transport Protocol.(FTP)
Message Protocol: File Content Conversion(since the xml files produce by XI need to be converted to text files)
Adapter Engine: Integration Server
For the File system access Parameters, enter the following
Source Directory:Test
File Name: Input.txt
6.4 For the FTP Connection Parameters, Specify the Following
Server:172.25.5.240
Port: 21(by default)
Data Connection: Passive
Connection security: None
Connection Mode: Permanently
Transfer Mode: Binary
6.5 For Processing Parameters, Specify the following
File construction mode: Add Time Stamp
File Type: Binary
6.6 For Content Conversion Parameters, Specify the Following
RecordSet Structure:
Adapter Status: Active
The receiver file adapter is now configured. Save your Communication Channel.
Create an Receiver Determination.
7). From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1) Select your sender service and interface.
Sender:
Party: blank
Service: Sender service(Business system)
Interface : Sender interface
7.2) In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
Create an Interface Determination.
7.3) Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1) In the Receiver Determination you just created, have a look at the area Configuration Overview for Receiver Determination at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2) In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3) You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4) A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5) When you are done , Save the Interface determination object.
8.) Create a Sender Agreement.
In the left hand frame , right click on Sender Agreement ->New
8.1) Specify the following:
Party: blank
Service: Select your own Business system
Interface: Outbound Interface
8.2) In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.) Create a Receiver Agreement.
Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1) Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2) In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
Specify the following:
Party: blank
Service: Select your own Business system
Interface: Inbound Interface
9.3) In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
Your Configuration is complete. Activate the objects.
To Configure the IDOC TO FILE SCENARIO,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC OUT OF SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Sending System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in SAP R/3 towards other system
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Outbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Outbound Parameters.So click on ADD TO Create Outbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Receiving port, Pack size=1 and Basic type
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
5) Create Customer Distribution model in the transaction code BD64
1) Click on the Create modal View button and enter the short text, Technical name etc as shown below
2) Now select the created model view and click on Add message type button .A pop up box appears, enter Sending system, receiving system and message type
3) Save the Distribution model
Generate Partner Profiles
Click on Menu Item Generate Partner Profiles
It leads to the next transaction where in the selection screen you have to provide Model view name, Partner System logical system and execute
Then, you will be intimated about the partners, port creation, and outbound parameters creation
4) Distribute Customer Distribution Model
In the menu item GO to Edit->Modal View-> Distribute to the destination client
Popup window appears ,press Enter
You will be intimated about the the Modal View Distributed
Step2:Repository
1) From the Integration Builder page, select Integration Repository. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server
2) Choose Tools->Transfer from System Landscape Directory->Import Software Component Versions
From the list of Software Component Versions, Choose your own software component version .Click Import.
3) On the left hand side frame ,software components will appear .Select your own software component. Open your own software component. Double click on this software component. A screen will appear .Switch to display mode. After doing this first add a namespace under Namespaces.
Your NameSpace is urn:idoctofile
4) Then choose the Radio Button ->Import of RFC AND IDOC interfaces from SAP systems permitted
After this specify the connection parameters to the R/3 system:
4.1) System :sapfox
4.2) Client :800
Then Save it. The new namespace will be visible under software component version node in the left frame.
Under the namespace node, you will find the section Imported Objects. Right click on it and choose Import of sap objects. A wizard will display. In the wizard provide the following details.
4.3) Application server:172.25.5.7
4.4) System number:00
4.5) User name: developer
4.6) Password: Password of Sap R/3 system.
Then click continue .You will find IDOC node. Click on this node and select the Idoc which is to be imported from R/3. Click Finish to start the Import. Close the wizard. After doing this the Idoc will be available into XI as Message types. So no need to create any Idoc Structure. We need to create a structure for file only.
5). Under your namespace in the left frame, expand the node Interface objects. You will find a node DATA TYPES
6) Create new data types.
6.1) Right click on Data types and select New.
Your Data Type is :dt_file
In the data type Editor ,Create a structure having Elements of type String , integer, Boolean , Float etc as per the requirement.
Save the object.
6.2) The Import function for XSD files enables you to upload message definitions from external sources. The object type External Definition is a container to make external definitions available in the Integration Repository.. While Importing the XSD files from External Definition
no need to create Data types. They are imported directly as Message types.
6.3) To do so, In the left hand frame Under Interface objects Create a new object of type External Definition and give name to it.
Select the following.
6.3.1) Category: XSD.
6.3.2) Messages: From All Available Global Elements.
6.3.3) File:
Once the XSD is imported, click on Message tab , You should be able to see 2 messages(Request and Response)
7). Create a new Message Type.
7.1) In the left hand frame under Interface objects, right click on the Message types and select new.
7.2) Give a suitable name to the Message type.(MT_ messagetype).
7.3) For the section Data type used you can go to input help (F4) or Search help provided and choose your data type (DT_datatype) from there.
Save it.
8). Create a Message interface
8.1) In the left hand frame under Interface objects, right click on the Message Interface and select new and name(MI_ messageinterface) it
8.2). The interface Should be Inbound and mode should be Asynchronous .It should reference your Message type(Use F4 or Search help).
Save it.
9) . Create a graphical mapping between the target document and the sender .
9.1) In the left hand frame ,expand Mapping objects. Right click on Message mapping and name it.You are now in a graphical editor.The Source message is on left, the Target message is on right.
9.2) As Source message select your own Idoc .You can choose Search for Integration Object.As a reminder you can find your Idoc or Rfc under Software Component- > Namespace->Imported Objects.
9.3) As Target Message you can choose your Message type .Choose Search for Integration Object.
9.4) Now that we have defined the Source and Target message, we can start defining the Mapping rules.
9.5) Map the fields of Source document to the equivalent fields in Target document .This can be achieved easily by locating the field in Target document and then Drag and Drop the Source fields to the respective Target Fields.
Save It.
9.6) You can also Test your Mapping by selecting the 'Test Tab'.
9.7) Fill in the values in the Idoc fields and click 'Start Transformation'. On the right hand side you will see Target Document populated with the appropriate Values.
10). Create an Interface Mapping.
10.1) In the left hand Frame expand Mapping objects. Right Click on Interface Mapping and Name it. You are in a Interface Mapping Editor .Assign the following References.
10.2) Source interface : Your Outbound Interface (The Source document(Idoc) interface).You can Choose Search for Integration Object.
10.3) Target interface: Your Inbound Interface( The Target document interface).
Then Select 'Read Interface' and Assign your 'Mapping Program' .
Mapping Program: Your Message mapping.
Then Save it.
11.) Finally , in the left hand frame ,go to your change list and Activate it
STEP 3: Directory
1) From the Integration Builder page, select Integration Directory. This will launch the Java Web Start Application. Log with the User id and password from the Integration Server.
Create a Scenario Object
2). The First Step is to create a Scenario Object
This will serve as container for all your configuration work. Create and save a scenario object
3) In the left hand frame you can see the created scenario object. Under that Object Expand the node Service without Party and right click on Business System->Assign Business System
4) In the wizard , leave the party name blank and then select your own Business System. Uncheck the box Create Communication Channel Automatically.This service (business system) represents the legacy system and Sap R/3 which will be exchanging the data.
5) . Create a Communication Channel.
6). Expand your service and right click on Communication Channel. Name your Communication Channel
Here we need to configure the adapter.
Since The Sender is IDOC , then there is no need of Sender communication channel and Sender Agreement.
For the Receiver, Specify the following Parameters
6.1 For the adapter type , use the F4 help and select FILE.
6.2 Specify Receiver since the adapter will be sending XML files from XI to the FTP server.
6.3 Specify the following parameters.
Transport Protocol: File Transport Protocol.(FTP)
Message Protocol: File Content Conversion(since the xml file produce by XI need to be converted to text file)
Adapter Engine: Integration Server
For the File system access Parameters, enter the following
Source Directory:Test
File Name: Input.txt
6.4 For the FTP Connection Parameters, Specify the Following
Server: 172.25.5.240
Port: 21(by default)
Data Connection: Passive
Connection security: None
Connection Mode: Permanently
Transfer Mode: Binary
6.5 For Processing Parameters, Specify the following
File construction mode: Add Time Stamp
File Type: Binary
6.6 For Content Conversion Parameters, Specify the Following
RecordSet Structure:
Adapter Status: Active
The receiver file adapter is now configured. Save your Communication Channel.
Create an Receiver Determination.
7). From the left frame Create a new Receiver Determination object. This is the main part of routing process, where you assign a receiver for your message.
7.1) Select your sender service and interface.
Sender:
Party: blank
Service: Sender service(Business system)
Interface : Sender interface
7.2) In the Configured Receivers area , choose the Service for the Target System.. Save your Receiver Determination
Create an Interface Determination.
7.3) Next create an Interface Determination object. Now that we have defined a receiver of message ,we need to assign an Inbound interface and an Interface mapping
7.3.1) In the Receiver Determination you just created, have a look at the area Configuration Overview for Receiver Determination at bottom of your screen and press Refresh for that the Business system you assigned is displayed in that area as well.
7.3.2) In the column Receiver(Partner/Service) open the details by clicking the node .The Entry Not defined shows you that there is no interface determination present.
Right click on the Entry Not defined and select New specific, in order to create a new interface determination object
7.3.3) You are now in the screen Edit Interface Determination. In the section Configured Inbound Interfaces select the Inbound Interface using F4 help Provided. You might need to choose ALL button for the interface to be shown.
After choosing the Inbound Interface, It is shown in the Interface Determination
7.3.4) A mapping has to be specified .Use the F4 help next to Inbound Interface to select your Interface Mapping.
7.3.5) When you are done , Save the Interface determination object.
8.) Create a Sender Agreement.
In the left hand frame , right click on Sender Agreement ->New
8.1) Specify the following:
Party: blank
Service: Select your own Business system
Interface: Outbound Interface
8.2) In the screen Edit Service Agreement use F4 help for the Sender Communication channel field .Select your Communication channel .Save and close
9.) Create a Receiver Agreement.
Finally you will create a 'Receiver Agreement' .This will allow you to assign a Receiver Communication Channel to the receiver service/Interface you have chosen.
9.1) Go back to the main screen for your receiver determination. In the area Configuration Overview for Receiver Determination at the bottom of your screen click Refresh.
9.2) In the Column Receiver Agreement(Communication Channel) right click and select New Specific.
Specify the following:
Party: blank
Service: Select your own Business system
Interface: Inbound Interface
9.3) In the screen Edit Receiver Agreement for the field Receiver Communication Channel use the input help F4 and select your communication channel. Save and Close it
Your Configuration is complete. Activate the objects.
plz rewards points
vikas -
Using remote enabled rfcs can we send data from one system to other..
or do can we do this only b/w twp sap systems.
why do we use bapis then.
wat is its difference b/w rfc and bapi.Hi Jaya Krishna,
RFC's can be accessed from non SAP systems also.
Technically BAPIs are RFcs Function modules only.
The only differenece is the business utility of them. The BAPIs have a standard Business functionality attached to them, like creation of an Order, Changing a Purchase document etc, Where as normal RFC function modules may or may not have a specific business functionality attached to them.
Regards,
Ravi -
RFC destination for Sender System in R/3 4.6c
Hi All,
I am trying create a RFC destination in R/3 4.6 system which will be used as sender RFC communication channel in Xi scenario. However i dont seem to have all the options such as activation type,gateway host and service which used to be there in SAP Enterprise or mySAP ERP systems. Can some one guide me to create an RFC destination in 4.6 system that will be used as a sender RFC system?Hi Arul,
One more important point u have missed.
Program ID,
When ur configuring sender service from RFC,The most important point is Program ID.
Use some name and create it.Use the same name in SM59.
s such its very crucial .Activate them .make sure the destination for that programID is what u expect.
Reghards
chandra shekar -
RFC to XML-RFC Parsing issue in RFC Adapter as Sender
Hi all,
I tried to use RFC adapter as a sender. The scenario I am trying to achieve is R3 -> RFC Adapter Sender --> BPM --> RFC Adapter Receiver --> SAP Auto-ID system.
The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails. Everything works as expected, except the RFC Adapter Sender.
The RFC I am calling has an input table. The input data I use works fine if I call it via SE37 or remotely from another SAP system. However, if I call it via RFC adapter, when XI parses the data into RFC-XML format, the input data is all messed up.
DATA: BEGIN OF ID_STR,
ID_VERSION(8) TYPE C,
ID(96) TYPE C,
ELEMENT_NAME(50) TYPE C,
ELEMENT_VALUE(128) TYPE C,
END OF ID_STR.
DATA: it_id LIKE TABLE OF ID_STR,
ls_id LIKE ID_STR.
ls_id-ID_VERSION = 'EPC_1.30'.
ls_id-ID = '30340242206DC3C00000000A'.
ls_id-element_name = 'BATCH_ID'.
ls_id-element_value = 'BATCH001'.
APPEND ls_id TO it_id.
CALL FUNCTION '/AIN/UI_MOBILE_MSG_SEND'
IN BACKGROUND TASK
DESTINATION 'RFC_UPDATEAII'
EXPORTING
IV_BUSINESS_PROCESS = '09'
IV_COMMAND = 'DO'
IV_ACTION_TYPE = 'APL2'
IV_PRT_ID = '31140242200000000F000000'
IV_DEVGRP_EXTID = 'MOBILE'
TABLES
IT_ID = it_id
commit work.
And the parsed RFC-XML message is:
<?xml version="1.0" encoding="UTF-8" ?>
<rfc:_-AIN_-UI_MOBILE_MSG_SEND
xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
<IV_ACTION_TYPE>APL2</IV_ACTION_TYPE>
<IV_BTD_EXTID />
<IV_BTD_TYPE />
<IV_BUSINESS_PROCESS>09</IV_BUSINESS_PROCESS>
<IV_COMMAND>DO</IV_COMMAND>
<IV_DEVGRP_EXTID>MOBILE</IV_DEVGRP_EXTID>
<IV_LOC_EXTID />
<IV_LOC_TYPE />
<IV_PRT_ID>31140242200000000F000000</IV_PRT_ID>
<IV_PRT_ID_VERSION />
<IV_REASON_CODE />
<IV_UNAME/>
<ET_RETURN />
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>206DC3C00000000A BATCH_ID</ID>
<ELEMENT_NAME />
<ELEMENT_VALUE />
</item>
</IT_ID>
</rfc:_-AIN_-UI_MOBILE_MSG_SEND>
You can see the data in the table is all wrong, it should be:
<IT_ID>
<item>
<ID_VERSION>EPC_1.30</ID_VERSION>
<ID>30340242206DC3C00000000A</ID>
<ELEMENT_NAME>BATCH_ID</ELEMENT_NAME>
<ELEMENT_VALUE>BATCH001</ELEMENT_VALUE>
</item>
</IT_ID>
The calling system is a 4.6C non-unicode system, and the destination system is a unicode system (this does not matter since the first part of the integration is between R3 and XI). There is no config found on R3 side to specify non-unicode because it is a rather old system. In XI RFC Adapter config, I checked non-unicode checkbox (I also tested it with this unchecked, but still the same issue).
Have any of you seen this problem and how you resolve it?
Thanks a lot for your help!
Regards,
HartHi Hart
long time no seen - hope you remember me
>The reason to use two RFC adapter and BPM is to log the request message if the RFC call fails
there is an easy way (guess max 3-4 hours) to solve all of your issues
and get rid of a BPM
use IDOC - XI - ABAP Proxy
then you will have IDOC and ABAP Proxy that always log the message on both ends (and you can restart ABAP proxies easily in AII - and every AII supports ABAP proxies) + you get rid of a BPM as it's not necessary as far as I understand (as it's asyn communication right?)
maybe you can go this way and IDOCs always work...
good luck,
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ -
Adapter engine field blank in RFC Comm channel (Sender)
Hi Friends,
I am not getting any value in drop-down list of adapter engine in RFC adapter sender communication channel.System is allowing me to save the comm channel , system is giving me following error
No adapter engine specified
I m getting values of adapter engine when I select some other adpter like XI.
Thanx
AnandHi,
The RfcAdapter is implemented as a J2EE Service and thus this service has to be started and stopped. This will affect the whole RfcAdapter and can be done from the J2EE Engines Visual Administrator. When you are connected to the J2EE Engine choose the tab 'Cluster' and open the appropriate server node in the tree. Then open the 'Services' node. There you can see the entry 'SAP XI Adapter: RFC'. When you open the context menu on this entry you can start and stop the service
Regards
Chilla... -
RFC Data not sending to Destination ( com.sap.aii.af.rfc.afcommunication.Rf
Hi Experts,
i have created a TCP/IP connection in sm59 as ID4 with R/3 details. now i am calling a function module like this.
call function 'Z_CBT_RFC_SALESPERSON'
exporting
p_sdate = p_sdate
p_edate = p_edate
tables
isalesperson = i_salesperson
exceptions
no_data_found = 1
others = 2.
if sy-subrc <> 0.
message e111(zi) with text-101.
endif.
if not i_salesperson[] is initial.
call function 'Z_CBT_RFC_SALESPERSON' in background task destination
'ID4'
exporting
p_sdate = p_sdate
p_edate = p_edate
tables
isalesperson = i_salesperson.
write: text-103.
else.
message e111(zi) with text-101.
exit.
endif.
commit work .
i am getting a problem that some times the data is exported to XI system but some times not.
and in sm58 i am getting an error message for this execution as
KOMMP2 Z_CBT_RFC_SALESPERSON ID4 05/28/2007 02:30:10 <b>Commit fault: com.sap.aii.af.rfc.afcommunication.R</b> 95B7F6ADB04C465A8502002E brcpfd04 SE38 ZSIOPSP 105 0000
Commit fault:
com.sap.aii.af.rfc.afcommunication.RfcChannelMismatchExcept
For all execution iam getting this error. Anyone call tell me how to resolve this issue.
Please suggest me, do i need any modification in the program and in connection settings.please do the needful as soon as possible.points will be awarded for all answers.
Thanks in advance.
Thanks & Regards,
PoornaHi Sergio,
Actually we are using the same connections for all the interfaces the we are developing in development system, and XI guys are using the same Program-ID in all their interfaces to configure.
So when we are triggering the interface, some times the messages are going to XI, but sometimes no data is going.
and let me know, if any more settings are required in sm59.
Thanks & Regards,
Poorna. -
Handle submit program for background jobs in RFC FM to send email in ITS
Hi all
I am facing a problem in ITS, i.e. I have called a RFC Function Module on the page load event of one of the HTML template. In that FM I have used <b>submit program</b>. This RFC FM is working fine in background i.e. it is sending pdf as email to a particular email address
but in the frontend it is not responding.
I wanted to ask whether we can handle submit <program-name> in background job from ITS
<b>If you are unable to understand the problem i can share with you my code as well.</b>
Thanks
Ekta TuliHi Tobias
The Function Module <b>ZV_FUNC_CCK_EMAIL_PDF</b> is used to generate the email with pdf as attachement. it is generating email at backend but not in frontend.
thanks
ekta
please find the code below for the FM
FUNCTION zv_func_cck_email_pdf.
*"*"Local interface:
*" IMPORTING
*" VALUE(CONTRACT) LIKE VBAP-VBELN
*" VALUE(EMAIL) LIKE ADR6-SMTP_ADDR
*" EXPORTING
*" VALUE(RETURN) TYPE CHAR4
data: i_vbak like vbak .
DATA: v_cont(10) TYPE c.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
EXPORTING
input = contract
IMPORTING
output = v_cont.
DATA: z_element(30) TYPE c.
DATA: gv_fb_addr_get_selection LIKE addr1_sel.
DATA: BEGIN OF mtab_contract OCCURS 0, "sap field
ordno(10), "vbeln (10)
terr(6),
vkorg LIKE vbak-vkorg,
vkgrp LIKE knvv-vkgrp,
repname(35),
repmailbox(10),
gueen(10), "expires dated -same as valid to
kunnr(10),
name1(35), "name1(35)
stras(35), "stras(35)
pstlz(10), "pstlz(10)
ort01(35), "ort01(35) city
regio(3), "regio(3)
kunnr2(10),
name2(35), "NUM?(35)
stras2(35), "stras(35)
pstlz2(10), "pstlz(10)
ort012(35), "ort01(35) city
regio2(3), "regio(3)
kit1 LIKE vbap-matnr, " currently 41315
kit1-qty(6), " like vbap-zmeng,
kit2 LIKE vbap-matnr, " currently 41316
kit2-qty(6), " like vbap-zmeng,
kit3 LIKE vbap-matnr, " currently 41317
kit3-qty(6), " like vbap-zmeng,
kit4 LIKE vbap-matnr, " currently 91869US
kit4-qty(6), " like vbap-zmeng,
med1 LIKE vbap-matnr, " currently 7408cp
med1-qty(6), " like vbap-zmeng,
med2 LIKE vbap-matnr, " currently 0211CP
med2-qty(6), " like vbap-zmeng,
med3 LIKE vbap-matnr, " currently 0578CP
med3-qty(6), " like vbap-zmeng,
med4 LIKE vbap-matnr, " currently 0068CP
med4-qty(6), " like vbap-zmeng,
med5 LIKE vbap-matnr, " currently 0069CP
med5-qty(6), " like vbap-zmeng,
med6 LIKE vbap-matnr, " currently other
dis6 LIKE makt-maktx, " currently other
med6-qty(6), " like vbap-zmeng,
med7 LIKE vbap-matnr, " currently other
dis7 LIKE makt-maktx, " currently other
med7-qty(6), " like vbap-zmeng,
med8 LIKE vbap-matnr, " currently other
dis8 LIKE makt-maktx, " currently other
med8-qty(6), " like vbap-zmeng,
med9 LIKE vbap-matnr, " currently other
dis9 LIKE makt-maktx, " currently other
med9-qty(6), " like vbap-zmeng,
med10 LIKE vbap-matnr, " currently other
dis10 LIKE makt-maktx, " currently other
med10-qty(6), " like vbap-zmeng,
END OF mtab_contract.
DATA: BEGIN OF mtab_material OCCURS 0,
ordno(10),
matnr LIKE vbap-matnr,
qty LIKE vbap-zmeng,
END OF mtab_material.
DATA: w-mm(4) VALUE ' MM '.
*SELECT-OPTIONS: s_vkorg FOR vbak-vkorg,
* s_vkgrp FOR knvv-vkgrp, "Sales Group
* s_terr FOR knvp-kunn2. "Territory Code
*PARAMETERS: p_parvw LIKE vbpa-parvw MEMORY ID par OBLIGATORY, "Partner ID
** DEFAULT 'Z1'.
* p_vbeln LIKE vbak-vbeln MEMORY ID aun,
* p_email LIKE adr6-smtp_addr MEMORY ID email. "Sales Document #
*SELECT-OPTIONS: "s_vbeln FOR vbak-vbeln MEMORY ID aun, "Sales Document #
* s_guebg FOR vbak-guebg, "Valid-From Date
* s_gueen FOR vbak-gueen, "Valid-To Date
* s_ship FOR vbpa-kunnr, "Ship-to customer
* s_bstzd FOR vbak-bstzd MEMORY ID bst ."DEFAULT 'CCK'. "P.O. # Supplement
DATA: i_otf TYPE STANDARD TABLE OF itcoo,
i_content_txt TYPE table of solisti1, "Content
i_content_bin TYPE solix_tab, "Content
i_content_bin1 TYPE solix_tab, "Content
i_objhead TYPE soli_tab,
w_pdf TYPE solisti1, "For PDF
w_res TYPE itcpp, "SAPscript output
w_otf TYPE itcoo, "For OTF
w_transfer_bin TYPE sx_boolean, "Content
prog(60).
data : t_obj_bin type standard table of solisti1.
DATA: w_arc_params LIKE arc_params,
w_pri_params LIKE pri_params.
*DATA: lcl_cls TYPE REF TO cl_gui_frontend_services.
CONSTANTS : c_x TYPE c VALUE 'X', "X
c_locl(4) TYPE c VALUE 'LOCL', "Local Printer
c_otf TYPE sx_format VALUE 'OTF', "OTF
c_pdf TYPE sx_format VALUE 'PDF', "PDF
c_printer TYPE sx_devtype VALUE 'PRINTER', "PRINTER
c_bin TYPE char10 VALUE 'BIN'. "BIN
DATA: v_name TYPE string ."Downloading File Name
DATA: v_len_in TYPE so_obj_len,
v_tempdir(50) TYPE c,
v_size TYPE i.
DATA : x_pdf_bag_tline TYPE rcl_bag_tline,
v_pdf_fsize TYPE i,
objpack LIKE sopcklsti1 OCCURS 2 WITH HEADER LINE,
objhead LIKE solisti1 OCCURS 1 WITH HEADER LINE,
objbin LIKE solisti1 OCCURS 10 WITH HEADER LINE,
objtxt LIKE solisti1 OCCURS 10 WITH HEADER LINE,
reclist LIKE somlreci1 OCCURS 5 WITH HEADER LINE,
doc_chng LIKE sodocchgi1,
tab_lines LIKE sy-tabix.
DATA : v_pnum LIKE usr21-persnumber,
v_anum LIKE usr21-addrnumber,
smtp_addr LIKE adr6-smtp_addr.
DATA: v_path TYPE string,
v_code TYPE i.
DATA : wa_obj_txt TYPE solisti1.
DATA : t_obj_txt TYPE STANDARD TABLE OF solisti1.
DATA : t_rec_list TYPE STANDARD TABLE OF somlreci1.
DATA : t_obj_pack TYPE STANDARD TABLE OF sopcklsti1.
DATA : wa_document_data TYPE sodocchgi1. "Mail data
DATA : wa_rec_list TYPE somlreci1.
DATA: reciever TYPE sadrud. "Email address of the receiver
DATA : wa_obj_pack TYPE sopcklsti1.
DATA: v_lines(10) TYPE n.
DATA: binfilesize TYPE i.
DATA : wa_obj_header TYPE solisti1.
DATA : t_obj_header TYPE STANDARD TABLE OF solisti1.
DATA : obj_id TYPE sofolenti1-object_id. "To send a file as attatchment
data: pdftab type table of tline with header line.
data : flag_sent_to_all type sonv-flag.
*START-OF-SELECTION.
* IF lcl_cls IS INITIAL.
* CREATE OBJECT lcl_cls.
* ENDIF.
CLEAR i_vbak.
SELECT * FROM vbak into i_vbak
WHERE
* guebg IN s_guebg AND "Valid-From Date
* gueen IN s_gueen AND "Valid-To Date
* vkorg IN s_vkorg AND
vbeln = v_cont AND
* AUART = 'LP ' AND "Converts to 'CO ' Scheduling A
auart = 'KM ' AND "Converts to 'CQ ' Qty contract
* VBTYP = 'E' AND "sales doc cat? JM
vbtyp = 'G' ."AND "sales doc cat "JM
* bstzd IN s_bstzd.
mtab_contract-kunnr = i_vbak-kunnr.
mtab_contract-ordno = i_vbak-vbeln.
mtab_contract-vkorg = i_vbak-vkorg.
WRITE i_vbak-gueen TO mtab_contract-gueen. "CHG014419
APPEND mtab_contract.
ENDSELECT.
LOOP AT mtab_contract.
* PERFORM get_contract. "CO sales orders line items
******Get Contract*********
* SELECT SINGLE kunnr "partner
* INTO vbpa-kunnr
* FROM vbpa
* WHERE vbeln EQ mtab_contract-ordno
* AND posnr EQ '000000'
* AND parvw EQ 'WE' "Ship-To's
* AND kunnr IN s_ship. "Ship-To ID added 04/01/99
* IF sy-subrc EQ 0 .
* MOVE vbpa-kunnr TO mtab_contract-kunnr2.
* MODIFY mtab_contract.
* ELSE.
* EXIT.
* ENDIF.
CLEAR knvp.
SELECT SINGLE kunn2 "territory
INTO knvp-kunn2
FROM knvp
WHERE kunnr EQ mtab_contract-kunnr2
AND vkorg EQ mtab_contract-vkorg
AND parvw EQ 'Z6'.
* AND kunn2 IN s_terr .
IF sy-subrc EQ 0 .
MOVE knvp-kunn2 TO mtab_contract-terr.
MODIFY mtab_contract.
ELSE.
EXIT.
ENDIF.
CLEAR kna1. "get rep name and mail box
SELECT SINGLE name2 FROM kna1 INTO (kna1-name2)
WHERE kunnr = knvp-kunn2.
IF sy-subrc EQ 0 .
SPLIT kna1-name2 AT w-mm INTO mtab_contract-repname
mtab_contract-repmailbox.
mtab_contract-repmailbox+3 = mtab_contract-repmailbox.
mtab_contract-repmailbox(3) = 'MM'.
MODIFY mtab_contract.
ENDIF.
CLEAR knvv.
SELECT SINGLE vkgrp
INTO knvv-vkgrp
FROM knvv
WHERE kunnr EQ knvp-kunn2
AND vkorg EQ mtab_contract-vkorg.
* AND vkgrp IN s_vkgrp.
IF sy-subrc EQ 0 .
MOVE knvv-vkgrp TO mtab_contract-vkgrp.
MODIFY mtab_contract.
ELSE.
EXIT.
ENDIF.
mtab_contract-med1-qty = '_______'.
mtab_contract-med2-qty = '_______'.
mtab_contract-med3-qty = '_______'.
mtab_contract-med4-qty = '_______'.
mtab_contract-med5-qty = '_______'.
mtab_contract-med6-qty = '_______'.
mtab_contract-med7-qty = '_______'.
mtab_contract-med8-qty = '_______'.
mtab_contract-med9-qty = '_______'.
mtab_contract-med10-qty = '_______'. "JM
mtab_contract-kit1-qty = '____'.
mtab_contract-kit2-qty = '____'.
mtab_contract-kit3-qty = '____'.
mtab_contract-kit4-qty = '____'.
mtab_contract-dis6 = 'OTHER _____________________'. "JM
mtab_contract-dis7 = 'OTHER _____________________'. "JM
mtab_contract-dis8 = 'OTHER _____________________'. "JM
mtab_contract-dis9 = 'OTHER _____________________'. "JM
mtab_contract-dis10 = 'OTHER _____________________'. "JM
* SELECT * FROM VBAP WHERE VBELN = MTAB_CONTRACT-ORDNO.
* IF VBAP-MATNR = '7408CP'.
* MTAB_CONTRACT-MED1 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '0211CP'.
* MTAB_CONTRACT-MED2 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '91865US'.
* MTAB_CONTRACT-MED3 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '0578CP'.
* MTAB_CONTRACT-MED4 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '0068CP'.
* MTAB_CONTRACT-MED5 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '0069CP'.
* MTAB_CONTRACT-MED6 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '92055CP'. "JM
* MTAB_CONTRACT-MED7 = VBAP-MATNR. "JM
* ELSEIF VBAP-MATNR = '90799CP'. "JM
* MTAB_CONTRACT-MED8 = VBAP-MATNR. "JM
* ELSEIF VBAP-MATNR = '41315'.
* MTAB_CONTRACT-KIT1 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '41316'.
* MTAB_CONTRACT-KIT2 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '41317'.
* MTAB_CONTRACT-KIT3 = VBAP-MATNR.
* ELSEIF VBAP-MATNR = '91869US'.
* MTAB_CONTRACT-KIT4 = VBAP-MATNR.
* ELSE.
* SELECT SINGLE MAKTX INTO MAKT-MAKTX
* FROM MAKT WHERE MATNR = VBAP-MATNR.
* ENDIF.
* MODIFY MTAB_CONTRACT.
* ENDSELECT.
MODIFY mtab_contract.
* IF.
** mtab_contract-terr IN s_terr AND
** mtab_contract-kunnr2 IN s_ship AND
** mtab_contract-vkgrp IN s_vkgrp.
** PERFORM get_address.
* ELSE.
* DELETE mtab_contract INDEX sy-tabix.
* ENDIF.
ENDLOOP.
SORT mtab_contract BY terr.
* PERFORM set_print_option.
* Print defaults should be immed and delete after print...
itcpo-tdimmed = ' '.
itcpo-tddelete = 'X'.
itcpo-tdnewid = 'X'.
itcpo-tdcopies = 1.
itcpo-tdnoprev = 'X'.
itcpo-tdgetotf = 'X'.
itcpo-tddest = 'LOCL'.
CALL FUNCTION 'GET_PRINT_PARAMETERS'
EXPORTING
destination = 'LOCL'
no_dialog = 'X'
IMPORTING
out_archive_parameters = w_arc_params
out_parameters = w_pri_params.
*exit if cancel chosen*
IF sy-subrc NE 0.
EXIT.
ENDIF.
sadr-regio = 'CA'.
sadr-pstlz = '92620'.
LOOP AT mtab_contract.
* PERFORM check-for-values.
IF mtab_contract-ordno = space.
mtab_contract-ordno = '___________'.
ENDIF.
IF mtab_contract-terr = space.
mtab_contract-terr = '______'.
ENDIF.
IF mtab_contract-repname = space.
mtab_contract-repname = '___________________________________'.
ENDIF.
IF mtab_contract-repmailbox = space.
mtab_contract-repmailbox = '__________'.
ENDIF.
IF mtab_contract-kunnr = space.
mtab_contract-kunnr = '__________'.
ENDIF.
IF mtab_contract-name1 = space.
mtab_contract-name1 = '___________________________________'.
ENDIF.
IF mtab_contract-stras = space.
mtab_contract-stras = '___________________________________'.
ENDIF.
IF mtab_contract-pstlz = space.
mtab_contract-pstlz = '__________'.
ENDIF.
IF mtab_contract-ort01 = space.
mtab_contract-ort01 = '___________________________________'.
ENDIF.
IF mtab_contract-regio = space.
mtab_contract-regio = '___'.
ENDIF.
IF mtab_contract-kunnr2 = space.
mtab_contract-kunnr2 = '__________'.
ENDIF.
IF mtab_contract-name2 = space.
mtab_contract-name2 = '___________________________________'.
ENDIF.
IF mtab_contract-stras2 = space.
mtab_contract-stras2 = '___________________________________'.
ENDIF.
IF mtab_contract-pstlz2 = space.
mtab_contract-pstlz2 = '__________'.
ENDIF.
IF mtab_contract-ort012 = space.
mtab_contract-ort012 = '___________________________________'.
ENDIF.
IF mtab_contract-regio2 = space.
mtab_contract-regio2 = '___'.
ENDIF.
* PERFORM open_form.
CALL FUNCTION 'OPEN_FORM'
EXPORTING
dialog = ' '
form = 'ZREV_CCK_AGREMT'
language = sy-langu
OPTIONS = itcpo
EXCEPTIONS
canceled = 1
device = 2
form = 3
OPTIONS = 4
unclosed = 5
OTHERS = 6.
IF sy-subrc <> 0.
MESSAGE e000(zz) WITH 'Open Form Error. ' sy-subrc.
ENDIF.
z_element = 'MAIN'.
* PERFORM write_form.
CALL FUNCTION 'WRITE_FORM'
EXPORTING
element = z_element
EXCEPTIONS
element = 1
function = 2
type = 3
unopened = 4
unstarted = 5
window = 6
OTHERS = 7.
* PERFORM close_form.
CALL FUNCTION 'CLOSE_FORM'
IMPORTING
RESULT = w_res
TABLES
otfdata = i_otf
EXCEPTIONS
unopened = 1
OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE e000(zz) WITH 'Close Form Error. ' sy-subrc.
ENDIF.
*&---Convert OTF data to PDF data.
call function 'CONVERT_OTF'
exporting
format = 'PDF'
importing
bin_filesize = binfilesize
tables
otf = i_otf
lines = pdftab[].
data : name LIKE RLGRAP-FILENAME.
CONCATENATE 'C:Temp' mtab_contract-ordno '.pdf' INTO v_name.
*CALL FUNCTION 'DOWNLOAD'
* EXPORTING
* bin_filesize = v_size
* filename = name
* filetype = 'BIN'
* TABLES
* data_tab = pdftab[].
CALL FUNCTION 'GUI_DOWNLOAD'
EXPORTING
* BIN_FILESIZE =
filename = v_name
FILETYPE = 'BIN'
tables
data_tab = pdftab[].
* Downloading the PDF File
* CALL METHOD lcl_cls->gui_download
* EXPORTING
* bin_filesize = v_size
* filename = v_name
* filetype = c_bin
* CHANGING
* data_tab = pdftab[].
CALL METHOD cl_gui_cfw=>flush.
**Send PDF as Email.
* wa_obj_txt-line = 'CCK Contract Agreement'.
APPEND wa_obj_txt TO t_obj_txt.
CLEAR wa_obj_txt.
wa_obj_txt-line = 'Please find attatched PDF document for Contract'.
APPEND wa_obj_txt TO t_obj_txt.
CLEAR wa_obj_txt.
DESCRIBE TABLE t_obj_txt LINES tab_lines.
**Prepare document data
wa_document_data-obj_name = 'CCK Contract Agreement'.
wa_document_data-obj_descr = 'CCK Contract Agreement'.
wa_document_data-obj_langu = sy-langu.
wa_document_data-proc_type = 'R'.
wa_document_data-proc_name = 'CCK'.
wa_document_data-priority = c_x.
wa_document_data-obj_prio = c_x.
**Receiving list
wa_rec_list-receiver = sy-uname.
wa_rec_list-rec_type = 'B'.
wa_rec_list-com_type = 'INT'.
wa_rec_list-notif_del = c_x.
APPEND wa_rec_list TO t_rec_list.
CLEAR wa_rec_list.
wa_rec_list-receiver = '[email protected]'."p_email.
reciever = wa_rec_list-receiver.
wa_rec_list-rec_type = 'U'.
wa_rec_list-com_type = 'INT'.
wa_rec_list-notif_del = c_x.
APPEND wa_rec_list TO t_rec_list.
CLEAR wa_rec_list.
*Object packet
CALL FUNCTION 'SX_TABLE_LINE_WIDTH_CHANGE'
EXPORTING
line_width_src = 134
line_width_dst = 255
TABLES
content_in = pdftab[]
content_out = t_obj_bin
EXCEPTIONS
err_line_width_src_too_long = 1
err_line_width_dst_too_long = 2
err_conv_failed = 3
OTHERS = 4
IF sy-subrc <> 0.
ENDIF.
DESCRIBE TABLE t_obj_bin LINES v_lines.
CLEAR wa_obj_pack-transf_bin .
wa_obj_pack-head_start = 1.
wa_obj_pack-head_num = 0.
wa_obj_pack-body_start = 1.
wa_obj_pack-body_num = tab_lines.
wa_obj_pack-doc_type = 'RAW'.
wa_obj_pack-doc_size = tab_lines * 255.
APPEND wa_obj_pack TO t_obj_pack.
CLEAR wa_obj_pack.
wa_obj_pack-transf_bin = 'X'.
wa_obj_pack-head_start = 1.
wa_obj_pack-head_num = 0.
wa_obj_pack-body_start = 1.
wa_obj_pack-body_num = v_lines.
wa_obj_pack-doc_type = 'PDF'.
wa_obj_pack-obj_name = 'ATTATCHMENT'.
wa_obj_pack-obj_descr = mtab_contract-ordno.
wa_obj_pack-doc_size = binfilesize.
APPEND wa_obj_pack TO t_obj_pack .
CLEAR wa_obj_pack.
**Object header
wa_obj_header-line = 'PDF'.
APPEND wa_obj_header TO t_obj_header.
CALL FUNCTION 'SO_NEW_DOCUMENT_ATT_SEND_API1'
EXPORTING
document_data = wa_document_data
put_in_outbox = c_x
commit_work = c_x
IMPORTING
sent_to_all = flag_sent_to_all
new_object_id = obj_id
TABLES
packing_list = t_obj_pack
object_header = t_obj_header
contents_bin = t_obj_bin
contents_txt = t_obj_txt
receivers = t_rec_list
EXCEPTIONS
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
OTHERS = 8.
IF sy-subrc <> 0.
else.
return = 'true'.
ENDIF.
ENDFUNCTION.
<b> Flow Editor</b>
<flow>
<state name="Start">
<module name="<b>ZV_FUNC_CCK_EMAIL_PDF</b>" type="RFC" stateful="1">
<inputmapping source="Contract" target="CONTRACT"/>
<inputmapping source="email" target="EMAIL"/>
</module>
<module name="ZV_FUNC_CCK_VALIDATE_SHIPTO" type="RFC" stateful="1">
<inputmapping source="SHIP_TO" target="KUNNR"/>
<inputmapping source="USERNAME" target="USER"/>
<outputmapping source="CITY" target="CITY"/>
<outputmapping source="NAME" target="NAME"/>
<outputmapping source="POSTAL" target="POSTAL"/>
<outputmapping source="REGION" target="REGION"/>
<outputmapping source="RETURN" target="RETURN"/>
<outputmapping source="SD_CITY" target="SD_CITY"/>
<outputmapping source="SD_NAME" target="SD_NAME"/>
<outputmapping source="SD_POSTAL" target="SD_POSTAL"/>
<outputmapping source="SD_REGION" target="SD_REGION"/>
<outputmapping source="SD_STREET" target="SD_STREET"/>
<outputmapping source="SOLDTO" target="SOLDTO"/>
<outputmapping source="STREET" target="STREET"/>
</module>
</state>
<event name="onLoad" next_state="Start"/>
<event name="Check2" next_template="ZV_CCO_CONFIRMED_ORDER"/>
</flow> -
RFC -programing to send table from one SAP box to other
can some one share info on how to communicate data between two SAP boxes through RFC
Hi,
Goto SE 37. Create a RFC by selecting RFC in the Attributes. Enter the IMPORT/EXPORT/TABLES parameters.
Build the logic and activate it.
Now in the another system.
Logon to the same system/client. Call the RFC with the data. Import the return data.
If you want more details, please let us know your requirement in detail.
Best regards,
Prashant -
Transaction RFC fails to send data and no errors
I am using a function module in background task to enable TRFC call. I don't get any error and the data does not go to the external Remote system.
I don't see any data in SM58 or ARFC* tables.
Any help is appreciated.
Thanks,
VijayHI,
- Verify connection test
- Verify user locked
- Verify user authorization
For begin
Rgds -
How to configure SCOT/RFC destination to send email to external addresses
Hi,
I have an ABAP program which sends out an email to email addresses such as [email protected], i configured SCOT and entered our company exchange server address in the SMTP node, and it works just fine. Problem is the program also needs to send emails to internet mail id's such as [email protected] or [email protected], and here it doesnt work, the email request shows up in SOST as failed saying that the address is unrecognized, we are able to send receive emails from internet id's as well using our email client (outlook), i just have no idea how to get the same to work from my ABAP program, i guess i am missing some BASIS configuration, can anybody help please?Please see the following example. Make sure you are setting the recipient type correctly.
report zrich_0003 .
data: maildata type sodocchgi1.
data: mailtxt type table of solisti1 with header line.
data: mailrec type table of somlrec90 with header line.
start-of-selection.
clear: maildata, mailtxt, mailrec.
refresh: mailtxt, mailrec.
maildata-obj_name = 'TEST'.
maildata-obj_descr = 'Test'.
maildata-obj_langu = sy-langu.
mailtxt-line = 'This is a test'.
append mailtxt.
mailrec-receiver = '[email protected]'.
<b> mailrec-rec_type = 'U'.</b>
append mailrec.
call function 'SO_NEW_DOCUMENT_SEND_API1'
exporting
document_data = maildata
document_type = 'RAW'
put_in_outbox = 'X'
tables
object_header = mailtxt
object_content = mailtxt
receivers = mailrec
exceptions
too_many_receivers = 1
document_not_sent = 2
document_type_not_exist = 3
operation_no_authorization = 4
parameter_error = 5
x_error = 6
enqueue_error = 7
others = 8.
if sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
endif.
Regards,
Rich Heilman -
How to call a RFC of a remote system from an ABAP webdynpro component
Dear Experts,
I am a newbie in ABAP Webdynpro.
I am working on a requirement where I have a webdynpro component on ECC system.I need to call a RFC located on CRM system from my webdynpro component on the ECC system.
How do I do that ?? Please help.
Regards,
Mamai.Calling RFC from some other system is same as local except the difference is that you have to give destination name while calling.
And the regarding the method of calling it depends on your FM.
if it is big RFC with complex structure, you can create the service call for it with destination given as RFC desitination.
if it is simple straight forward RFC you can directly call it.
for creating RFC service call call use this method
1. Starting the Wizard
To start the wizard, position the cursor on the Web Dynpro component to be edited in the object list at the left margin of the
workbench window. Open its context menu and choose the entry Create->Service Call. The wizard is started and leads you
through the creation process.
Press Continue.
2. Choice of Controller
On the second dialog window of the wizard, you can choose whether the service call is to be embedded in an existing
controller or whether a new controller is to be created for this purpose. Service calls can only always be embedded in
global controllers u2013 that is, in the component controller or in additionally created custom controllers. It is not possible, to
embed service calls in view controllers.
a. Select radio button Use Existent Controller
b. Do not change the default entry for component: <CC name>
c. Enter for controller COMPONENTCONTROLLER
d. Press Continue.
3. Service Type and Service Selection
a. You now select, which service type should be used for this service call. Select radio button Function Module. Fill the
destination here. Press Continue.
b. Select the service: for Function Module enter <RFC name>. Press Continue.
4. The Required Methods and Context Elements
On the two subsequent dialog windows, default values are listed for giving names to the context nodes and attributes
required by the service call as well as to the required methods. The proposed names are based on the names of the
embedded service, but you can change them as required. However, heed the respective notes in the corresponding dialog
box.
a. Adapt Context: Select from Nodes/Attributes . Press Continue.
b. Specify Method Name: leave all entries as provided: Component: Controller: COMPONENTCONTROLLER Method: EXCUTE_ Press Continue.
5. Completing the Choice
When you have confirmed the last dialog box, the generation is triggered. Afterwards you now have the required methods
and contexts at your disposal for using them within your Web Dynpro component.
or if you want to call directly the use the call statement with destination -
XML pay load for RFC call in java mapping
Hi,
I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
Say i have 2 import parameters(input1,input2) and one output(output1)......
Thanks in advance,
H.L.Babu>
hlbabu123 wrote:
> Hi,
> I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
>
> Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
>
> Say i have 2 import parameters(input1,input2) and one output(output1)......
>
> Thanks in advance,
> H.L.Babu
have a look at this document - https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439&overridelayout=true
in case u still have issues do get back
Maybe you are looking for
-
How do I find where my larger files are all at Once
Like all I am getting close to having a full HD. Is there a way to tell where all my large files are all at the same time without having to go to each folder, file, application Thx Much
-
GUY'S I am facing a strange problem. i am working on server on which they created my user-id with developer access, user told me to change the form and to add signature in form, i have uploaded this signature using se78 tcode,put when i go for print
-
Importing Audio for ppt files in Captivate
How do you import audio and sync over multiple powerpoint slides? I'm using Captivate 6
-
The emails get sent but the to address should list in the email
If I do something like this <cfmail type="html" query="q" to="#q.email# The emails get sent but the to address should list in the email, but they don't get listed.
-
How to get DVD's into Final Cut 5
I have been given raw footage of my son's wedding shot in HD and put on 5 DVD's. It is in standard definition on the DVD. How can I get it into Final Cut 5 to edit? I have always worked from miniDV tapes and am at a loss as to how to make this work.