IDOC / BAPI / RFC

Hi,
I want to know what is the differences between the IDOC/ BAPI/ RFC...????
How we will prefer to choose one of them??
What is asynchronous / synchronous IDOC..???
Can you giude me on these terms and provide me some useful data/information for the same..
Thanx,
Jay

Hi Jaywant,
Please check this link
What is the difference between ALE, IDOC and BAPI
http://www.sap-img.com/abap/ale-bapi.htm
Difference Between BAPI and RFC
http://www.sap-img.com/fu026.htm
http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
Best regards,
raam

Similar Messages

Difference among IDOCS,BAPI,RFC?

what is the difference among IDOCS,BAPI,RFC? and what is the real need to use them and again where exactly these are used in real time applications?

Hi,
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS Customer Master, and WMMBID02 for message type WMMBXY Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALEs ability to redefine it for any message type.
Regards,
Bhaskar

What are idocs, BAPI, RFC?

Hi,
What are idocs, BAPI, RFC?
Regards,
anuj

Hii,
BAPIs and RFCs are the functions exposed by SAP, when it comes to the integration part, you have to know that particular BAPI or RFC. For example, if you want to get table data or want to query to the SAP table then you use RFC_READ_TABLE. Similarly if you want to know whether customer is existing, you need to know which RFC/BAPI has this info. May I know which tool are you using, are you talking about generating a proxy and playing around that.
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
Try this..Hope this will help.
SAP ALE & IDOC<<<<
Steps to configuration(Basis) >>
1. Create Logical System (LS) for each applicable ALE-enabled client
2. Link client to Logical System on the respective servers
3. Create background user, to be used by ALE(with authorizaton for ALE postings)
4. Create RFC Destinations(SM59)
5. Ports in Idoc processing(WE21)
6. Generate partner profiles for sending system
The functional configuration(Tcode: SALE)
Create a Customer Distribution Model (CDM);
Add appropriate message types and filters to the CDM;
Generate outbound partner profiles;
Distribute the CDM to the receiving systems; and
Generate inbound partner profiles on each of the clients.
Steps to customize a new IDoc >>>
1. Define IDoc Segment (WE31)
2. Convert Segments into an IDoc type (WE30)
3. Create a Message Type (WE81)
4. Create valid Combination of Message & IDoc type(WE82)
5. Define Processing Code(WE41 for OUT / WE42 for IN)
6. Define Partner Profile(WE20)
Important Transaction Codes:
SALE - IMG ALE Configuration root
WE20 - Manually maintain partner profiles
BD64 - Maintain customer distribution model
BD71 - Distribute customer distribution model
SM59 - Create RFC Destinations
BDM5 - Consistency check (Transaction scenarios)
BD82 - Generate Partner Profiles
BD61 - Activate Change Pointers - Globally
BD50 - Activate Change Pointer for Msg Type
BD52 - Activate change pointer per change.doc object
BD59 - Allocation object type -> IDOC type
BD56 - Maintain IDOC Segment Filters
BD53 - Reduction of Message Types
BD21 - Select Change Pointer
BD87 - Status Monitor for ALE Messages
BDM5 - Consistency check (Transaction scenarios)
BD62 - Define rules
BD79 - Maintain rules
BD55 - Defining settings for IDoc conversion
WEDI - ALE IDoc Administration
WE21 - Ports in Idoc processing
WE60 - IDoc documentation
SARA - IDoc archiving (Object type IDOC)
WE47 - IDoc status maintenance
WE07 - IDoc statistics
BALE - ALE Distribution Administration
WE05 - IDoc overview
BD87 - Inbound IDoc reprocessing
BD88 - Outbound IDoc reprocessing
BDM2 - IDoc Trace
BDM7 - IDoc Audit Analysis
BD21 - Create IDocs from change pointers
SM58 - Schedule RFC Failures
Basic config for Distributed data:
BD64: Maintain a Distributed Model
BD82: Generate Partner Profile
BD64: Distribute the distribution Model
Programs
RBDMIDOC Creating IDoc Type from Change Pointers
RSEOUT00 Process all selected IDocs (EDI)
RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
RSARFCEX - Execute Calls Not Yet Executed
RBDMOIND - Status Conversion with Successful tRFC Execution
RBDMANIN - Start error handling for non-posted IDocs
RBDSTATE - Send Audit Confirmations
FOr testing you can use WE19.
BAPI
BAPI Programming guide: -
http://help.sap.com/saphelp_nw04/helpdata/en/e0/9eb2370f9cbe68e10000009b38f8cf/frameset.htm
BAPI user guide: -
http://help.sap.com/saphelp_46c/helpdata/en/7e/5e115e4a1611d1894c0000e829fbbd/frameset.htm
BAPI STEP BY STEP PROCEDURE: -
http://www.sap-img.com/abap/bapi-step-by-step-guidance.htm
Example:-
http://www.erpgenie.com/abap/bapi/example.htm
PDF download: -
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/200dd1cc-589e-2910-98a9-bb2c48b78dfa
list of all bapis
http://www.planetsap.com/LIST_ALL_BAPIs.htm
for BAPI's
http://www.sappoint.com/abap/bapiintro.pdf
http://www.sappoint.com/abap/bapiprg.pdf
http://www.sappoint.com/abap/bapiactx.pdf
http://www.sappoint.com/abap/bapilst.pdf
http://www.sappoint.com/abap/bapiexer.pdf
http://service.sap.com/ale
http://service.sap.com/bapi
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDAPII/CABFAAPIINTRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFABAPIREF/CABFABAPIPG.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE8/BCFESDE8.pdf
http://www.planetsap.com/Bapi_main_page.htm
http://www.topxml.com/sap/sap_idoc_xml.asp
http://www.sapdevelopment.co.uk/
http://www.sapdevelopment.co.uk/java/jco/bapi_jco.pdf
Also refer to the following links..
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.planetsap.com/Bapi_main_page.htm
http://www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
BADI
Check these links on BADI
http://www.esnips.com/doc/e06e4171-29df-462f-b857-54fac19a9d8e/ppt-on-badis.ppt
http://www.esnips.com/doc/10016c34-55a7-4b13-8f5f-bf720422d265/BADIs.pdf
http://www.esnips.com/doc/43a58f51-5d92-4213-913a-de05e9faac0d/Business-Addin.doc
http://www.esnips.com/doc/1e10392e-64d8-4181-b2a5-5f04d8f87839/badi.doc
http://www.esnips.com/doc/3b7bbc09-c095-45a0-9e89-91f2f86ee8e9/BADI-Introduction.ppt
Check this link for advantage of BADIs over User exits
http://www.sap-img.com/abap/difference-between-badi-and-user-exits.htm
Reward points if useful.
Regards,
Sushama

IDOC/BAPI/RFC... to create/modify BoM??

Hello,
I need to found the best way to create or modify a BoM in SAP from an external system (throught SAP PI).
My SAP version is 4.7. I've searched and I've found the following, IDOCs, BAPIs and RFCs, but I'm not sure about the functionallity of each one, and if they solve my problem:
IDOCS:
BOMMAT.BOMMAT04
MATERIALBOM_CREATEBOMGROUP01
BAPIS:
BAPI_MATERIAL_BOM_GROUP_CREATE
RFCS:
CSAP_BOM_ITEM_MAINTAIN (CSAP_MAT_BOM_OPEN and CSAP_MAT_BOM_CLOSE are necessary with that)
Can you give me some option?

Hi,
Please try BAPI BAPI_PRICES_CONDITIONS.
Check this links for more information.
BAPI_PRICES_CONDITIONS
Problem with BAPI_PRICES_CONDITIONS
Regards,
Ferry Lianto

ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

Hi,
we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
My question is:
We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
Best regards,
Steven

Hi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi.

Difference between idoc and rfc

what is the difference between idoc and rfc? when and where it is used? when there is idoc, why rfc vice versa?

IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
IDocs are used for asynchronous transactions: Each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database.
Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
A large enterprise's networked computing environment is likely to connect many geographically distributed computers to the main database. These computers are likely to use different hardware and/or operating system platforms. An IDoc encapsulates data so that it can be exchanged between different systems without conversion from one format to another.
IDoc types define different categories of data, such as purchase orders or invoices, which may then be broken down into more specific categories called message types. Greater specificity means that an IDoc type is capable of storing only the data required for a particular transaction, which increases efficiency and decreases resource demands.
An IDoc can be generated at any point in a transaction process. For example, during a shipping transaction process, an IDoc may be generated that includes the data fields required to print a shipping manifest. After a user performs an SAP transaction, one or more IDocs are generated in the sending database and passed to the ALE communication layer. The communication
layer performs a Remote Function Call (RFC), using the port definition and RFC destination specified by the customer model.
The IDoc is transmitted to the receiver, which may be an R/3, R/2, or some external system
RFC
Remote Function Calls (RFC) and data exchange through IDoc message documents. RFC makes direct and synchronous calls of a program in the remote system. If the caller is an external program it will call an RFC-enabled function in R/3 and if the calling program is the R/3 system it will call an RFC-function in another R/3-system or it will call a non-R/3 program through a gateway-proxy (usually rfcexec.exe). BAPIs are a subset of the RFC-enabled function modules, especially designed as Application Programming Interface (API) to the SAP business object, or in other words: are function modules officially released by SAP to be called from external programs.
note:reward points if solution found helpfull.....
regards
chandrakanth.k

Sending IDocs via RFC Adapter

Hello!
In an itegration scenario, we need to send (non XML) IDocs via RFC to a remote R/3 system (4.6C). As we don't want to get these IDocs persisted on the target system, it's intended to address the remote functions directly.
Now the problem:
- RFC Adapter only works with XML IDocs (so we cannot transfrom back to native IDoc)
- IDoc-Adapter sends native IDocs, but only to IDOC_INBOUND_ASYNCHRONOUS on target system (and the Idocs will be persisted)
In a next step, we also tried to implement a workaround with a local ABAP proxy on the XI system. But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
Has anybody any idea to solve this problem? Maybe I'm thinking too complicated Help is highly appreciated!
Cheers,
Matthias

Hi,
what kind of document you want to post?
most (many) IDOCs use BAPIs so you can
just call the BAPI (RFC) from XI
>>>But it seems, that it's not allowed to call a abap proxy locally on the integration engine.
you can call it on another client on the XI
(which is set as application system in SXMB_ADM)
Regards,
michal

Idoc or RFC

Dear Guys
Will some body explain the relationship between IDOC BAPIS and RFCs. I have developed a interface between SAP 4.6C and ASP.NET using .NET Connectors. When I am getting data by just using RFC then why should I go for IDOCs.
My same is question is related to BAPIs when RFCs Function using BAPI are providing me data through BAPIs then why is IDOC technology there.
When I have to use RFC and when we can use IDOC or RFCs.
Basically I am trying to develop an ASP application by using which our customer can crreate Sale Order on SAP.

hi,
>>>How does it work in real life scenarios? Will there be a batch job to trigger the IDOCS to XI?
yes but you can set IDOC creation from PO
in a few minutes (in standard) and you
have to do a lot a development to send
them with RFC... so not few minutes
+ you can archive idocs and delete them
just like any message in the XI
>>>>2) How can i create an IDOC?
you have to maintain the partner profile and
set the output type and that's all...
5 minutes in standard
3) What is the RFC involved to get the purchase orders?
none you have to fill the RFC yourself...
you can use BAPI for PO creation as a template
but you still have to fill it youself
Regards,
michal

BAPI/RFC for WIP values

Hi all,
I would like to show production order WIP values in an external system dashboard.
Is any BAPI/RFC/IDoc available to fetch the data from SAP? If not, please let me know corresponding table to view the data in SAP?
Thanks
Guru

In view COVPB you should find WIP and variance information.

Idocs Vs RFC's

Which is used when and why?Where are Idocs preferred and where are RFC's preferred?

Hi,
Normally while dealing with the amount of data and the way of communication will be the deciding factors to either go for IDOC or RFCs
It also depends on the business requirement and inbound/outbound.
IDOC if we are using any standard document and if you want to use function module then we have to go for RFC. If you extract some data and want to sent then we can go for proxies. IDOC can be triggered immediately and also by background job, Proxies can be triggered like that . It all depends upon the requirement.
IDOC are basically are the best way to go for asynchronous communication.
IDOCs come with rich logging, error handling and workflow integration in the back end R/3 system.
Best thing, all BAPIs could be converted to IDOC interface using the BAPI/ALE generator.
RFC is with synchronous communication. You could even use the proxy communication also.
Please refer
/people/ravikumar.allampallam/blog/2005/08/14/choose-the-right-adapter-to-integrate-with-sap-systems
Thanks
Swarup

Scenario - IDoc - XI - RFC - IDoc

Hi Experts,
I am new to BPM.
We have 2 sap systems...SAP1, SAP2.
The BPM scenario is,
When Material changes made in MM02 of SAP1, changepointers creates an IDoc1. IDoc1 is first sent to XI. Now in SAP2, it is to be checked whether that particular changed in SAP1 exists in SAP2 or not. For this, from XI an RFC call is made to SAP2, depending on the return values, the IDoc message that has been reached to XI (from SAP1) is sent to SAP2.
How to achieve this.
Any docs, links would help me. I am very new to BPM.
-Naveen.

Hi,
Can any one give me some direction.
>>>Are you talking about BPM steps ? if so I have given that.
For Message Interfaces-
1) Abs, Async, Message Interface of type Idoc
2) Abs, Sync, Message Interface of type RFC
3) Abs, Async Message Interface of type Idoc , which is sending to SAP2 system. If you have mapping changes.
Mapping is outside the BPM, Create a dummy message type for RFC response. To check the response in the BPM
i.e Idoc to RFC Req Mapping
RFC Response to Dummy RFC response
Hope this helps,
Regards,
Moorthy

DIFFERENCE B/W IDOC AND RFC   ADAPTERS

HI FRIENDS,
WHAT IS THE DIFFERENCE B/W   IDOC AND RFC   ADAPTERS..? AND WHICH ONE IS
PREFERABLE TO USE    IN TRANSFERING DATA FROM THIRD-PARTY SYSTEM TO SAP.?
REGARDS,
RAMAKRISHNA.

Hi
These links will help you to understand :
http://help.sap.com/saphelp_nw04/helpdata/en/11/028417f9f8b24cbe1b0b398e1cb76a/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/ab/bdb13b00ae793be10000000a11402f/frameset.htm
Please dont forget to reward with points.
Edited by: Dheeraj Kumar on Mar 3, 2008 2:59 PM

BAPI/RFC for Service Complaints Creation in CRM 5.0

Hi,
We are working on the Complaints and Returns module in CRM 5.0. We have found the Transaction Code for the same. (CRMD_BUS2000120).
Not able to find the BAPI/RFC for the same.Let us know if any. Appreciate your comments on the same.
Thanks,
Moorthy

Hi,
Thanks for the response
I am not talking about Service Order. I have requirement to create a Service Complaint. For that the transaction is CRMD_BUS2000120. Now I need to find the function modules/RFC available for this requirement.
Hope it clarifies .
Even I have found function module called -CRM_COMPLAINT_API_CREATE but not sure right one
Thanks,
Moorthy

Idoc-xi-rfc scenario random fails to be processed

Hallo all .
Let me first describe our scenario.
Generally it is an IDOC - > XI -> RFC case.
Idocs are created after an order creation .
In XI there are two different mappings, depending on the idoc structure (the IDOC type is the same, but the segments created are different) and two different receivers, each one with an individual communication channel. Each channel is allowed to have up to 200 multiple simultaneous connections .
Then, each functions decides whether the inbound data is appropriate for it and processes it or not .
Our problem is this :
If we send a bunch of orders (eg 100), all of them are processed successfully except of some of them, (eg 4 ).
In the SXMB__MONI, they are all marked as "waiting for acknowledgment" .
Yet, there is no obvious reason for their failure.
If we send again the failed orders, then 3 of them may be processed.
And finally if we send them again even the last one will be processed.
So, from what I can see, this problem cannot exist due to the data we send, or the XI configuration, or the functions that are finally called. Actually, it seems to be absolutely random.
Any suggestions would be highly appreciated .
Edited by: John Syrigos on Dec 30, 2008 6:08 PM
Some clarifications : The business scenario is to handle the ORDER idocs that created in the SAP ERP system from SD (Outbound Deliveries) or the Stock Transport Orders (Outbound Deliveries). The problem for the created IDocs is that if the outbound delivery is coming from SD then for each line item of the sd document fills the segment A for example and if the outbound delivery is coming from the Stock Transport Order then fills another IDOC segment for example B. For this reason we decide to create two separate interface mappings in order to send each IDOC in both of the Function Module that handle which of them will be executed. In the daily order processing the user every afternoon use a standard SAP ERP transaction and collect all the outbound deliveries and create for the collectively the appropriate IDOCs. We suppose the mass processing will create some problems.
Thanks in advance

hi,
one simple advice (less then one day) would be to change
>Generally it is an IDOC - > XI -> RFC case.
either to:
Generally it is an IDOC - > XI -> ABAP proxy case.
or if this is not abap proxy enabled receiver system to:
Generally it is an IDOC - > XI -> IDOC case.
if you already have a working RFC then changing it to and IDOC
and changing a mapping is less then one day and in both cases
abap proxy and IDOC you will have a clear status and LOG!
(as both IDOCs and ABAP proxies are persistent in receiver system)
this is the best possible option I believe and nothing will get lost for sure
Regards,
Michal Krawczyk
http://mypigenie.com XI/PI FAQ

IDoc - XI - RFC Issues

Trying to set up an IDoc->XI->RFC Scenario. Am able to receive the IDoc into XI but are having issues getting this to the other system via RFC.
Status in Monitor for Processed XML Messages (SXMB_MONI) is "Recorded for Outbound Processing". When I "display" the specifics I see the Inbound Message was processed fine but the Receiver Grouping is set to "Recorded for Outbound Processing".
I check SMQ2 and I can see my data in the status "Transaction Recorded". I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".
Also in SMQR the scheduler status is "Inactive". Not sure if that is relevant or not.
Hoping someone has seen this and can help me get whatever I'm missing set up!
Thanks!

Hi,
Also in SMQR the scheduler status is "Inactive". Not sure if that is relevant or not.
This status is OK.
I check SMQ2 and I can see my data in the status "Transaction Recorded". I try to <F6> the message in SMQ2 and get the message "the queue is registered and therefore cannot be activated".
>> in SMQ2 what is the status ? Is it running/sysfail etc ?
If it is SYSFAIL, then double click on that and check the exact error.
Else, you can go to SMQR or SXMB_ADM->Manage Queues->QRFC monitor-> .. then go to specified Queue name(whatever having the problem) and deregister it. Then go to SMQ2 and execute/activate the Queue . This time you will not get the info "Queue is registered...." Then go again SMQR and Re-reigister it.
For more ~
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Re: Recorded for Outbound Processing
Hope this helps,
Regards,
Moorthy

IDOC / BAPI / RFC

Similar Messages

Maybe you are looking for