Example Of Aynchronous and Transactional RFC

hi all
please give me an example for Aynchronous and Transactional RFC.
note: dont give me the definitions. i have the same.please give me the example
regards
ravish

Hi Ravish,
I am using the FM RFC_READ_TABLE for the examples,
In our Examples we are using the following systems.
Description Server Name RFC Destination
Calling System PDC ENT Server NONE
Target System 1 PDC 210 Server PDC210
Target System 2 PDC ISU Server BPD150
Common Code
REPORT yarfc_with_resp_ran_test .
DATA : lit_options TYPE TABLE OF rfc_db_opt.
DATA : wa_options LIKE LINE OF lit_options.
DATA : lit_fields TYPE TABLE OF rfc_db_fld.
DATA : wa_fields LIKE LINE OF lit_fields.
DATA : lit_data TYPE TABLE OF tab512.
DATA : wa_data LIKE LINE OF lit_data.
DATA : lv_count TYPE i.
DATA : flg_check TYPE flag.
DATA : lv_time LIKE sy-uzeit.
CONSTANTS : lc_dbtable TYPE tabname VALUE 'MARA'.
*Refreshing the tables
REFRESH : lit_options,lit_fields,lit_data.
*Populating the Option Table
*Populating the Field Table
CLEAR wa_fields.
wa_fields-fieldname = 'MATNR'.
wa_fields-offset = 000032.
wa_fields-length = 000018.
wa_fields-type = 'C'.
wa_fields-fieldtext = 'Material number'.
APPEND wa_fields TO lit_fields.
aRFC with Response
* aRFC Example With Response
*Refreshing the Data Table
REFRESH : lit_data.
*PDC-ENT to PDC210
CALL FUNCTION 'RFC_READ_TABLE'
STARTING NEW TASK 'taskPDC210'
DESTINATION 'PDC210'
PERFORMING resp_pdc210 ON END OF TASK
EXPORTING
 query_table = 'MARA'
TABLES
 options = lit_options
 fields = lit_fields
 data = lit_data
EXCEPTIONS
 table_not_available = 1
 table_without_data = 2
 option_not_valid = 3
 field_not_valid = 4
 not_authorized = 5
 data_buffer_exceeded = 6
 OTHERS = 7.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CLEAR lv_count.
lv_count = LINES( lit_data ).
WRITE : 'aRFC Example With Response'.
SKIP 1.
*MARA DB Count Before Receiving the result of Function Call
WRITE : 'MARA DB Count(PDC210)' , lv_count , sy-uzeit.
*Waiting for 1 Second to identify the time difference
WAIT UP TO 1 SECONDS.
*Synchronisation Point
WAIT UNTIL flg_check = 'X'.
SKIP 1.
WRITE : 'Time When We Set Flag Check i.e. we are in Receiving FM' , lv_time.
CLEAR lv_count.
lv_count = LINES( lit_data ).
SKIP 1.
*Waiting for 1 Second to identify the time difference
WAIT UP TO 1 SECONDS.
*MARA DB Count After Receiving the result of Function Call
WRITE : 'MARA DB Count(PDC210)' , lv_count , sy-uzeit.
*& Form resp_pdc210
FORM resp_pdc210 USING taskname.
RECEIVE RESULTS FROM FUNCTION 'RFC_READ_TABLE'
TABLES
 options = lit_options
 fields = lit_fields
 data = lit_data
EXCEPTIONS
 table_not_available = 1
 table_without_data = 2
 option_not_valid = 3
 field_not_valid = 4
 not_authorized = 5
 data_buffer_exceeded = 6
 OTHERS = 7
*Flag set for the Synchronisation Check.
flg_check = 'X'.
CLEAR lv_time.
*Time when flag get set.
lv_time = sy-uzeit.
ENDFORM. " resp_pdc210
tRFC
* Transactional RFC Example
*Refreshing the Data Table
REFRESH : lit_data.
*PDC-ENT to PDCISU
CALL FUNCTION 'RFC_READ_TABLE'
IN BACKGROUND TASK
DESTINATION 'PDCISU'
EXPORTING
 query_table = lc_dbtable
TABLES
 options = lit_options
 fields = lit_fields
 data = lit_data
EXCEPTIONS
 table_not_available = 1
 table_without_data = 2
 option_not_valid = 3
 field_not_valid = 4
 not_authorized = 5
 data_buffer_exceeded = 6
 OTHERS = 7.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
*Refreshing the Data Table
REFRESH : lit_data,lit_fields.
*Populating the Field Table
CLEAR wa_fields.
wa_fields-fieldname = 'INT_UI'.
wa_fields-offset = 000032.
wa_fields-length = 000022.
wa_fields-type = 'C'.
wa_fields-fieldtext = 'Internal key for point of delivery'.
APPEND wa_fields TO lit_fields.
*PDC-ENT to PDCISU
CALL FUNCTION 'RFC_READ_TABLE'
IN BACKGROUND TASK
DESTINATION 'PDCISU'
EXPORTING
 query_table = 'EUIHEAD1'
TABLES
 options = lit_options
 fields = lit_fields
 data = lit_data
EXCEPTIONS
 table_not_available = 1
 table_without_data = 2
 option_not_valid = 3
 field_not_valid = 4
 not_authorized = 5
 data_buffer_exceeded = 6
 OTHERS = 7.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION 'RFC_PING'
IN BACKGROUND TASK
DESTINATION 'PDCISU'.
*Commit Work
COMMIT WORK.
Do reply for any further help.
Regards,
Ranjit Thakur.
Please Mark The Helpful Answer.

Similar Messages

Monitoring of remote system's Transactional RFC and Queued RFC

Hello,
In our production system, in rz20- CCMS monitor templates- Communication-Transactional RFC and Queued RFc- outbound queues- Queues otherwise not monitored we can see blocked queues for each client.
System is connected to solution manager and we wish the central auto reaction is implemented in solution manager
However i am unable to find Transactional RFC and Queued RFC for the remote system, they exist only for solution manager itself
Tell me how can i do the central monitoring

Hello,
First you need to check with your Landscape in solman in order to monitor any kind of activities to do so pls follow these steps.
Go to SMSY in solman under Landscape components>Product systemsselect you satellite system example SAP ECC.
On the main screen you will find client for which you have generated RFC connection. Please check though connection are working fine, Go to edit mode and try to click on generate button there will be a pop-up, which gives a clear picture of RFC connection which already exists, and you can also re-generate this RFC connection by clean it up when you re-generate pls select under Actions after generation assign RFC dest for system monitoring.
But make sure there is no project impact on this RFC, like they are not using any logical components and already have some projects running on this RFC connection.
I would advise you to first you the option of assign and check RFC button which is next to generate icon.
Regards
JUDE

CCMS qRFC Monitoring: Missing Transactional and Queued RFC Monitoring Nodes

Hi ,
We are trying to create a Queued RFC monitoring for VERTEX Queued , but we are missing CCMS Monitor Templates,in monitor Communications -->Transactional RFC and Queued RFC in Dev and PROD ,but its present in QA System .
I have checked all system are at same level for support packs , kernel version .
I have refered following Notes - 441269,437187,455431, 485826
Can we create manually new one , but we are missing MTE class also ?
Can we create new monitoring template ?
We are running 4.6c with basis support pack level :
SAP_BASIS 46C 0054 SAPKB46C54
SAP_ABA 46C 0054 SAPKA46C54
Thanks
Hamendra

Hamendra,
Please make sure background dispatching is activated in your system. Go to tcode RZ21 and menu Technical Infrastructure --> Method execution --> Active background dispatching.
This should schedule a job called SAP_CCMS_MONI_BATCH_DP. This is the job that will run the function for building the ALE/EDI monitoring segment.
After scheduling the job check back in a few hours, if the ALE/EDI monitor is still not there try the following.
1. Go to tcode RZ21
2. In the topology section choose radio button "Segment overview" and click display
3. Go into change mode and delete the monitoring segments
This will force the system to recreate all the monitoring contexts.
Check back in a few hours and see if the monitor is working.
Tarkesh

Transactional RFC Monitoring

hi all,
   Can anyone explain to me how transactional RFC works? As what i've understand it, the first transaction to get in is the first to be executed right?
   Here's my scenario. I always monitors the transactional RFC,and from time to time, I observe irregularities. For example, at arround 9:00 am, bunch of transactions are displayed and the status are "status recorded". By 11:00 am, transactions are added again but this time one of the status of transactions timed 11:00am is "status executing" even if there are still remaining transactions that are recorded by 9:00 am. The way i understand it, the "first in" "first out" here was not applied.
   Could anyone clear this? am i right about the "first-in first-out" scenario? if yes, how can i correct tmy problem? If not, can you explain??
Your response is highly appreciated.
cheers,
Jay

Hi Jay,
As given in the RFC adapter help
Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
The tRFC in SAP sense means:
This scenario is suitable if the data being sent is not interrelated. A calling application (or client) in system 1 uses a tRFC connection to a called application (or server) in system 2. In this scenario, the data is transferred using tRFC. This means that each function module sent to the target system is guaranteed to be processed once. The order in which the function modules are executed, and the time they are executed, cannot be determined. If a transfer error occurs, a background job is scheduled that resends the function module after a defined period of time.
What you are talking abt is EOIO. As per the RFc adapter help, it supports:
Transactional RFC calls (tRFCs) in messages with quality of service Exactly Once (EO)
The receiver RFC adapter can also process messages with quality of service Exactly Once In Order (EOIO). They are mapped to transactional RFC calls (tRFC).
Hope this is of some help.
Regards
Vijaya

Diff B/W master data and transaction data

Hi all,
What is the main Diff B/W master data and transaction data. give me some example ?
Thanks in Advance
Krish...

hi krish,
MASTER Data is the data that exists in the organization like employee details, material master, customer master, vendor master etc. These are generally created once.
Master data are distributed throughout the company, they are often not standardised and often redundant. As a result it is very costly to offer efficient customer service, keep track of supply chains and make strategic decisions. With SAP Master Data Management (SAP MDM) these important business data from across the company can be brought together, harmonised and made accessible to all staff and business partners. As a key component of SAP NetWeaver, SAP MDM ensures data integrity via all IT systems.
Regardless of the industry, companies often work with different ERP and Legacy systems. The result: the business processes are based on information about customers, partners and products which is displayed in different ways in the systems. If the data are recorded manually, there are more inconsistencies: some data sets are entered several times, others cannot be retrieved by all divisions of the company.
As corporate applications are becoming increasingly complex and produce ever greater amounts of data, the problem is intensified further. Nevertheless, your employees must work with the inconsistent data and make decisions on this basis. The lack of standardised master data easily leads to wrong decisions, which restrict efficiency and threaten customer satisfaction and profitability.
In a word: in order to save costs and ensure your companys success it is necessary to consolidate master data about customers, partners and products, make them available to all employees beyond system boundaries and use attributes valid company-wide for the purpose of description.
TRASNACTION Data - These are the business documents that you create using the master data - Purchase orders, sales orders etc
http://help.sap.com/saphelp_nw2004s/helpdata/en/9d/193e4045796913e10000000a1550b0/content.htm
Regards,
GNK.

Remote and Transactional Cube

Dear Friends,
How a Basic Cube differs from a Transactional and Remote Cube ?
A Small Example- Cube Carries the Transaction data of Customer ,Material, Sales details ( characteristics) and price, Quantity and Revenue (keyfigures) .
When do we Really have to Change or to Create the Other Cubes to hold those Data ?
What is the Exact Purpose that a Scenario Needs the Remote and Transactional Cube ?
I hope Remote Cube Can be created with "Infoservices" and "Source system" . What is the demand for both these options?
Thanks well in advance ,
Ramesh

hi,
Remotecbue will have only structure and It does't hold any data.
and it is used to bring live data to BW ..At the time of reporting only the data fetches from the source system. So it takes more time to execute.
it will not hav update rules...
Transactional InfoCubes are used only in conjunction with SEM. The data from this kind of InfoCube is accessed transactionally, meaning data is written to the InfoCube (possibly by several users at the same time) and reread as soon as possible. Basic InfoCubes are not suitable for this. You should use Basic InfoCubes for read-only access (for example, when reading reference data).
Rfer
http://help.sap.com/saphelp_bw33/helpdata/en/39/100c38e15711d4b2d90050da4c74dc/frameset.htm
thanks
(Assign points if useful..)

Transactional RFC

hi experts,
In SM58(Transactional RFCs) Status text showing "document is being distributed changes are not possible".
why this error comming.
Any one can help me out in this.
Regards,
Babu

Hi Babu,
In general, when you create any BP or Material or Order in R/3, it will move to CRM.
Now if you try to edit that document in CRM, it will give the error message "document is being distributed changes are not possible".
This can happen vice versa too, I mean if you create data in CRM and if it moves to R/3.
If you have not done any settings regarding changing data after moving one system to another, this error message gets triggered.
Check the below link to have a clear picture.
Document is being distributed - changes are not possible
Hope this helps.
Thanks.
Best Regards,
Arun Sankar.

Many queues in Transactional RFC (SM58)

Hello,
There are many queues under transactional RFC(SM58) what should i do?
Can i delete the Queue's or execute that?
What is the mean of Execute LUW's and Debug LUW's ,when we wil use it?
Highly appriciate your immediate replies.
Thanks in advance.
Cheers,
Chinna.

Hi Chinna
You have all the details mentioned in this link
http://help.sap.com/saphelp_nw04/helpdata/en/22/042585488911d189490000e829fbbd/content.htm
Cheers
Shaji

SM58 (transactional RFC)

Hi,
In our source system in SM58 (transactional RFC) i am getting the Status Text:
User is locked. Please notify the person responsib
Please advise how to proceed
Thanks
Please search the forum before posting a thread
Edited by: Pravender on Aug 12, 2011 4:09 PM

Hi
Thanks for the update.
I can execute the TCode SM58 and there i can see all the RFC queus are failed becaus of User Locked

Transactional RFC material (urgent)

Hi gurus,
i need some good matrial on Transactional Remote Function Call. Please provide me the same,
any help will be highly appreciated
Regards
vj

hi vj,
Transactional RFC
1 This type of RFC was renamed from asynchronous to transactional RFC, because asynchronous RFC has another meaning in R/3 Systems.
2 The called function module is executed exactly once in the RFC server system. Each function call is seen as a transaction in the target system.
3 Transactional RFCs use the suffix IN BACKGROUND TASK. The remote system need not be available at the time when the RFC client program is executing a tRFC.
4 The tRFC component stores the called RFC function together with the corresponding data in the R/3 database, including a unique transaction identifier (TID).
5 If a call is sent, and the receiving system is down, the call remains in the local queue until a later time.
6 The calling dialog program can proceed without waiting to see whether or not the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
7 The system logs the remote call request in the database tables ARFCSSTATE and ARFCSDATA with all of its parameter values. You can display the log file using transaction SM58.
8 When the calling program reaches a COMMIT WORK, the remote call is forwarded to the requested system for execution.
9 Transactional RFC requests are transferred, with parameter data in byte-stream form, using TCP/IP or X400.
10 LUW's are identified by transaction ID's that are unique world-wide. The transaction ID can be determined from an ABAP program by calling function module ID_OF_BACKGROUNDTASK. (You must call this function after the first asynchronous CALL, and before the related COMMIT WORK.)
11 The system function module ARFC_DEST_SHIP transports the data to the target system and the function module ARFC_EXECUTE executes the stored function calls. If an error or an exception occurs during one of the calls, all the database operations started by the preceding calls are rolled back and an appropriate error message is written to the file ARFCSSTATE.
12 Once you have identified the ID of the LUW, you can use the function module STATUS_OF_BACKGROUNDTASK to determine the status of the transactional RFC.
13 Call transaction SM58 (Tools _ Administration _ Monitoring _ Transactional RFC). This tool lists only those transactonal RFCs that could not be carried out successfully or that had to be planned as batch jobs. The list includes the LUW ID and an error message. Error messages displayed in SM58 are taken from the target system. To display the text of the message, double-click on the message.
14 If a LUW runs successfully in the target system, the function module ARFC_DEST_CONFIRM is triggered and confirms the successful execution in the target system. Finally, the entries in the Tables ARFCSSTATE and ARFCSDATA are deleted.
DISADVANTAGES
1 These can reduce performance significantly in both the send and the target
systems.
2 In addition, the sequence of LUWs defined in the application cannot be kept. Therefore, there is no guarantee that the transactions are executed in the sequence dictated by the application. The only guarantee is that all LUWs are transferred sooner or later.
SYNTAX
Eg : CALL FUNCTION remotefunction IN BACKGROUND TASK
CALL FUNCTION func IN BACKGROUND UNIT
parameter_list. The field dest can be either a literal or a variable. Logical destinations are defined in the RFCDES table via transaction SM59 or via the menu path: Tools ->Administration,Administration->Network->RFC destinations.
SAMPLE PROGRAM
RSTRFCT0
regards
gaurav
plz award pts if helpfull

SQL08 Need example of creating AND using a Fact (degenerate) dimension

Can someone post a link to some examples of setting up and using a Fact (degenerate) dimension. Ive got the SSAS 2008R2 Adventureworks DW project setup and I see a few Fact dimensions in there, but id like some descriptions to go along with this or
something similar.
My scenario:
Orders - attributes include : Order#, OrderStartDate, SalesPerson, BusinessType, MarketType
OrderTransactions - attributes include: OrderKey , TransactionAmount, TransactionType, TransactionDate, AccountKey
Description:
Its more or less the typical Order > Order Detail type scenario, with the addition of Orders have some additional attributes.
So I want to be able to measure on for example:
Order counts - broken down by BusinessType and MarketType , and then within a date range
Revenue - which will be totals of transaction amounts, again grouped by BusinessType and MarketType, but also be able to drill down to see the related Order#

Hi Shiftbit,
According to your description, you need some examples about create and use degenerate dimensions, right?
Degenerate dimensions, also called fact dimensions, are standard dimensions that are constructed from attribute columns in fact tables instead of from attribute columns in dimension tables. Here is document that describes how to create and use degenerate
dimensions step by step, please refer to the links below.
https://msdn.microsoft.com/en-us/library/ms167409(v=sql.100).aspx
http://www.jamesserra.com/archive/2011/11/degenerate-dimensions/
Regards,
Charlie Liao
TechNet Community Support

Transact RFC error

Hi Gurus,
I am getting one issue while loading the data thru infopackage.
While loading the data in 3.5 flow for some souce system it is taking long time
and givig me transact RFC error. I have checked the source system connectivity and it is fine.Although the status is yellow during the load but at the end of the load it turns to red and it gives me below mentioned error:
Missing data packages for No selection information arrived from the source s
Diagnosis
Data packets are missing from No selection information arrived from the source s. BI processing does not return any errors. The data transport from the source system to BI was probably incorrect.
Procedure
Check the tRFC overview in the source system.
You access this log using the wizard or following the menu path "Environment -> Transact. RFC -> Source System".
Error handling:
If the tRFC is incorrect, resolve the errors listed there.
Check that the source system is connected properly to BI. In particular, check the remote user authorizations in BI.
Kindly let me know your suggestion in this issue.
Thanks in advance.
Amit

Hi
This error would normally occur, if at the time of processing, the data packets get stuck
To check for stuck trfc follow the path
Environment -> Transact. RFC -> Source System
there, check if trfc recorded, then it means, it is stuck, slecect that particular record and press F6 to execute the LUW.
If this is not the case, check the job overview in the source system.
IF you find ARFCSTATE = loading/sysfail, it means the trfc is stuck ..
you can check the datapacket number from there, and try mannual update for those partiular data packets.
Or else, sometimes, the packet itself doesnt arrive in BW, because of connection problem during the processing of few packets, ands later when you check, it seems fine.
In such cases simply repeat the load
Hope this helps
Regards
Shilpa

Examples for Synchronous and asynchronous

Hi all,
Please can any body give me the real time example for Synchronous and asynchronus
Ranjith

Let us take example of calling a transaction for update:
Call Transaction
Synchronous calls are slower but should be used for transactions that are updating the database because control is not passed back to the program until a successful database commit (or rollback) has been executed. Note this the real SQL commit at the database level not the ABAP command COMMIT WORK. Synchronous calls will set the return code (sy-subrc) if an error is encountered. There are actually two synchrounous update modes:
'S', Synchronous update mode makes database entries describing the updates to be done and an update task (potentially running on a different computer) reads those database entries, does the update, and then deletes the entries describing the update task.
'L', Local update mode describes the updates to be done in the memory of the current process. No entries are made in and then deleted from the database describing the update task.
Asynchronous calls are the default if the UPDATE parameter is not specified. Asynchronous calls do not effect the return code (sy-subrc).
Note - This is opposite of how synchronous/asynchronous workflow tasks behave, in the sense that control is returned to the workflow in a synchronous step even if there is no commit or rollback encountered!
Prakash.
Message was edited by: Prakash Ramu

Import master and transaction data

Hallo,
I need the information, how I can import master and transaction data.
I fellow the introductions from SAP.Help (see Link), but the Programm UPB_DATA_IMPORT
is failed. (See point 3 in Link):
http://help.sap.com/saphelp_nw04/helpdata/en/7a/6d313f8815d036e10000000a114084/frameset.htm
If I want to try point 3. The error massage.
Program UPB_DATA_IMPORT does not exist Message no. DS017
will result.
What I can do? Who can me say why I havent the Programm UPB_DATA_IMPORT?
What is wrong?
Please help me.I need Data to make a demo planning
thanks

Hi,
There is a set of objects in business content (check under SAP DEMO in business content). You can activate some or all of these demo objects (for example demo cubes).
There are programs which you can then execute to create the datafiles which can then be loaded to these demo cubes.
" Start report RSO_BC_FILES_IN_BDS (Transaction SE 38), specify the required (Demo) InfoObject/InfoCube and choose the "Start BDN" button. The system will display all (generally one) CSV files which were supplied with the InfoObject/InfoCube. You can either export this CSV file into a local directory or you can write it directly onto the application server. For loading, proceed as described under section 1. " --- from OSS note 370397

TRFC and Asynchronous RFC

Is there any diff between TRFC and ARFC ?
Is TRFC another name for ARFC?

Hi,
Transactional RFC (tRFC) they are previously known as ARFC
Transactional RFC (tRFC, previously known as asynchronous RFC) is an asynchronous communication method that executes the called function module just once in the RFC server. The remote system need not be available at the time when the RFC client program is executing a tRFC. The tRFC component stores the called RFC function, together with the corresponding data, in the SAP database under a unique transaction ID (TID).
If a call is sent, and the receiving system is down, the call remains in the local queue. The calling dialog program can proceed without waiting to see whether the remote call was successful. If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch.
tRFC is always used if a function is executed as a Logical Unit of Work (LUW). Within a LUW, all calls
·         are executed in the order in which they are called
·         are executed in the same program context in the target system
·         run as a single transaction: they are either committed or rolled back as a unit.
Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.
Disadvantages of tRFC
·       tRFC processes all LUWs independently of one another. Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems.
·       In addition, the sequence of LUWs defined in the application cannot be kept. It is therefore impossible to guarantee that the transactions will be executed in the sequence dictated by the application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later.
regards
prasanth

Example Of Aynchronous and Transactional RFC

Similar Messages

Maybe you are looking for