-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Groups
- Interest Groups
- Application Development and Automation
- Discussions
- why tRFC is stated as asynchronous processing type
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
why tRFC is stated as asynchronous processing type
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2006 Dec 15 12:20 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2006 Dec 15 1:42 PM
- SAP Managed Tags
- ABAP Development
Hi max,
1. The concept and architecture of rTFC
is such that,
even if the other server is DOWN, at the time of making the call,
the r/3 system will ensure,
that wehenver the other system is UP,
it will connect and do the rfc call.
2. This processing happens INDEPENDENTLY
of the calling program.
The callling program, can CONTINUE after the tRFC call is made.
It NEED NOT WAIT, after calling the FM.
Hence, it is asynchrous.
regards,
amit m.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2006 Dec 15 1:23 PM
- SAP Managed Tags
- ABAP Development
hi,
While with synchronous and asynchronous RFC each call makes a single logical unit of work (LUW) in the remote system,you can group several RFCs into one LUW for transactional RFCs.
you can use the addition IN BACKGROUND TASK which you must specify before the DESTINATION entry.if you write a COMMIT WORK statement all the previous RFCs are bundled into one LUW and transmitted through tRFC
Thus it is asynchronous
Regards,
Sourabh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎2006 Dec 15 1:42 PM
- SAP Managed Tags
- ABAP Development
Hi max,
1. The concept and architecture of rTFC
is such that,
even if the other server is DOWN, at the time of making the call,
the r/3 system will ensure,
that wehenver the other system is UP,
it will connect and do the rfc call.
2. This processing happens INDEPENDENTLY
of the calling program.
The callling program, can CONTINUE after the tRFC call is made.
It NEED NOT WAIT, after calling the FM.
Hence, it is asynchrous.
regards,
amit m.
Bluesky