Idoc and Bdoc

Hi Gurus,
1) I would like to know about Idoc and Bdoc,
what I feel is Idoc triggers in ECC and Bdoc triggers in CRM
2) How difference does displaying a customer in CRM (txn : BP) and ECC (txn: XD03) makes?
Thanks and regards,
Manu

Hi,
Please check these links:
IDOC
Bboc: Business Documents (BDocs). You use this to define and maintain Bdocs.BDocs enable communication between the SAP CRM components and the CRM Server. Data is encapsulated in a BDoc and transferred to the server. Features BDoc Modeler offers the following features:
u2022     Model a new class of BDoc called Messaging BDocs.
u2022     Assign Synchronization BDocs (formerly write BDocs) to a Messaging BDoc.
u2022     Assign site types to Messaging and Synchronization BDocs.
u2022     Documentation facility for every BDoc.
u2022     Removal of SFADDIC and full-integration with DDIC.
u2022     Generate R/3 structure name for a segment automatically.
u2022     Check a BDoc for data consistency.
u2022     Filter BDocs based on criteria.
u2022     Generate R/3 services for a BDoc.
u2022     Release BDocs for correct upgrades.
u2022     The BDoc is locked when it is being used in edit mode by a particular user. Hence, not more than one user can model a BDoc at any given point of time.
u2022     Traffic Lights display mechanism for error tracking.
u2022     Track the occurrence of an object using Where-Used list.
u2022     Specify access rights for users using the authorization concept.
u2022
BDocs used in the CRM scenario can be categorized as follows: -
u2022     Synchronization BDocs (sBDocs):- These BDocs are processed in the CRM Server as well as in the Mobile Client, and contain mappings to tables. They were previously called as Write BDocs in the Client-based BDoc Modeler. Synchronization BDocs are used to exchange data between the CRM server and the Mobile Clients.
u2022     Mobile Application BDocs:- These BDocs are used by CRM Mobile Applications and are processed outside the CRM Server. They contain mappings to tables. They were formerly called Read BDocs or Query BDocs.
u2022     Messaging BDocs (mBDocs): - Messaging BDocs are used by CRM Server applications. These BDocs are processed in the CRM Server and do not contain table mappings. Hence these BDocs will not have parameter information. Nor will they have joins and where clauses.
Could you please be more specific on your second question?
Thanks,
Karuna.

Similar Messages

What is the diffrence btween IDOC and BDOC?

what is the diffrence btween IDOC and BDOC?

Hi,
In short Idoc is an Intermediate Document and Bdoc is an Business Document.
Data can Be Transferd from Sap to Non Sap using Idoc where as we can transfer
data between sap to sap in Bdoc.
IDoc
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
BDOC
BDoc is a business document which is technically similar to an IDoc. BDocs are used to communicate data between two systems.
BDocs come in two types. One is the message BDoc (MBDoc) and the second is the Synchronizing BDoc (SBDoc).
MBDoc is used for replicating the data between SAP CRM and SAP R/3
SBDoc is used for replication and realignment between SAP CRM and mobile clients
som times SAP will be integrated with som other third party systems
ex SAP with BAAN here we should comunicate one to other systems
here we can integrate using EDI technology in this the formate of data will be in I DOCS EX :EDI is a bridge between 2 systems .I doc is a container to transfer data from one sys to other
this Idocs we can use in ALE technology also
BDoc is called Business Document,
BDoc represents data in a structural format. This sturctural architecture is use to either input data to system or send data to other system.
BDocs are data carrier that can either collected in system(Inbound) or can be send out of system(Outbound)
Please refer following link:
http://help.sap.com/saphelp_crm40sr1/helpdata/en/ec/8d7e3a7e760b55e10000000a114084/content.htm
Thanks,
Medha.

Idocs and Bdocs

hi all,
can anybody tell me waht are idocs and bdocs and what is der functionality.
points will b rewarded
thanks
raj

Hi Raj,
IDOC is an intermidate document which acts as a data container to exchange data (messages) between any two business systems
The document represented in an IDoc is independent of the complex structure used in SAP to store application data. This feature enables SAP to rearrange its internal structure without affecting the existing interfaces.
The word IDoc is used very loosely in the IDoc interface. An IDoc represents an IDoc type and IDoc data, depending on the context in which the word IDoc is used. An IDoc type defines the structure and format of the data being exchanged. For example, the IDoc type INVOIC01 defines the format of an invoice document. IDoc data can be seen as an instance of an IDoc type. For example, an actual invoice received from a vendor in electronic form is converted into an IDoc.
An IDoc is an instance of an IDoc type. Each IDoc is assigned a unique number for tracking and future reference. An IDoc serves as a focal object for tracking the state of the process that generated it.
The internal structure of an IDoc, showing the control record, data records, and status records
 One control record
 One or many data records
 One or many status records
 Control record. There is only one control record per IDoc. The control record contains all the control information about an IDoc, including the IDoc number, sender and receiver information, and other control information such as the message type it represents and IDoc type. The structure of the control record is the same for all IDocs and is defined by SAP. The field values, of course, can be different.
 Data record. An IDoc can contain multiple data records, as defined by the IDoc structure. Segments translate into data records. Data records store application data such as purchase order header information, purchase order details lines, and other relevant information.
 Status record. Multiple status records are usually attached to an IDoc. Status records are attached to an IDoc throughout the process as the IDoc achieves different milestones. A status code, date, and time are assigned at every milestone.
Refer the below links,
idoc information
http://help.sap.com/saphelp_nw2004s/helpdata/en/78/21785851ce11d189570000e829fbbd/frameset.htm
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&
/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

DIFFERENCE BETWEEN iDOC MESSAGING AND bDOC MESSAGING

hI
gurus what is the diffrence between idoc messaging and bdoc messaging?
K. Mangalum

Hi Kumara,
BDOC:
Container of business data that belongs together, for example customer, contact person, order or activity. This means that it contains all required information for a business process. The technical representation of a BDoc type is completely independent. There are many possible representations for a BDoc type.
For example, a BDoc type can be represented as follows:
as a collection of internal ABAP table structures (on the CRM Server),
by ADO record sets (on mobile clients),
as an XML form (for non-SAP systems), or,
as an IDoc.
Therefore a BDoc type is a semantic collection of business data and not a syntactical description.
There are three classes of BDoc types:
BDoc types exclusively used for mobile applications
They consist of a hierarchical data segment structure with assignment to database tables.
BDoc types for synchronization between the consolidated database in the CRM Server and mobile applications
They consist of a hierarchical segment structure with assignment to database tables.
BDoc types exclusively used for non-mobile applications
They consist of:
a hierarchical segment structure with no assignment to database tables,
additional data (complex data type modeled in the ABAP Dictionary)
Standard BDoc types are provided by SAP. Additional BDoc types can be modeled by customers.
Idoc:
IDOC: An intermediate document, container for exchanging data between R/3 and other SAP and non-SAP applications. Structured collection of segments. Segments are structured collection of data elements.
General Structure
IDocs contain administration information for technical processing, as well as the actual application data, which is stored in segments. A segment comprises segment fields as the smallest unit of the IDoc - comparable with the data elements from the EDIFACT standard.
In the SAP System, the processing status ("what has happened to the IDoc before now?") is stored in the IDoc status information. The status information also contains details about errors and indicates the data in which the error occurred. This status information is not forwarded as part of the IDoc but separately using "status processing".
IDoc types (special structure)
An IDoc type is defined through its permitted segments. Segments can be dependent on each other (parent and child segments). For example, segment E1EDPT1 (document item text identification) is a child segment of segment E1EDP01 (document item data, general) in IDoc type EXPINV01 (export billing) and a child segment of E1EDP07 (order data shipping notification) in IDoc type DESADV01 (shipping notification). The segment, therefore, is used in several contexts and is the "child" of several "parents".
CRM Bdoc and IDoc are both persisted data structures.
Idoc works on a particular technology called ALE and is used for data exchange between two R/3 systems
Regards,
Satish Mathala

Idoc and message type not getting replicated in the receiver system

Hi
i have created a Z Idoc and didtributed the mode from system A ....I can see the distribution model in system B
However i cannot see the custom zidoc / message type in sys B.. Do i need to create the zidoc again in sys B

Hi Tarang,
at least ou need the required partner agreements and you should have a processing function for inbound IDoc. To implement this, the full definition of IDoc including Segment definition should be present in receiving system.
Just look at standard IDocs and do as they do.
Regards,
Clemens

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

How to trigger automatically an IDOC and RFC from SAP R/3 system?

Hi ,
lets say if we are implementing IDOC to FILE &RFC to FILE scenario ,how can we trigger on timely basis(schedules)
1)standard IDOCs and BAPIs?
2)customized Idocs and Customized Bapis?
3)Master Idocs and transactiona Idocs?I think we need to use change pointers for master Idocs and donno about Transactional Idocs.
please explain ,
thank you very much for your help.
regards,
Babu

sorryfor the late reply, I was busy with my work.thank you for your posts.
so all of you say just run the RSEOUT00 no matter what interface we use in XI like Master ,transactional Idocs,standard or customized BAPIs?
And I think we use RSNASTED if we have on recieving side right?
<b>then when we would use a report of format below to trigger an RFC,is this format for Asunc RFC ?</b>
REPORT Z_SEND_DATA_TO_XI.
parameters: dest like rfcdes-rfcdest default '(RFC Destination you defined in SM59)'.
<<your other variable declaration and ABAP Code here>>
call function 'ZXI_SEND_DATA'
in background task
destination dest
exporting
Name = John
City = Smith. (The values to pass to XI)
commit work.
<<Any Write statements or sy-subrc statements here>>
6) Save and Activate your ABAP program.
6) After all these steps, execute your ABAP Program to send the data to file via XI.

IDoc and creation of sales order!!

Hi,
I need to create sales order using IDoc and the file will have multiple line items for sales order and it has to be dynamic, so whats the best way to do this?
Regards
Gunjan

Hi
Check for the related IDOC types in EDBAS table and for related Message Types
in table EDMSG. take relavent one for your requirement and use.
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
Reward points if useful
Regards
Anji

Tax with the help of idoc and EDI

Dear gurus,
how can we process tax data that is used between two systems through the help of IDOC and EdI? It would be great for ur kind support.

Hi Amit,
I do not understand how a non-sap system having an idoc adapte?
Do you mean the non-sap system has the ability to understand the IDOC files?
If yes, then your scenario is typically a IDOC-to File scenario.
Read this:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
If you do not intend to use XI in between, then you can just configure the outbound IDOCs in your SAP system and configure a file port in we21 transaction and create the partner profile in we20 transaction.
Regards,
Ravi

PI 7.1 scenario -- File to File , File to IDOC and IDoc to File Scenario

Hi All,
*I have PI 7.0 . I have in that File to File , File to IDOC and IDoc to File Scenarios*
File to File -- This scenario is working fine.
File to IDOC -- Setting done in PI 7.0 like SM59, IDXI, IDX2 and in R/3 like SALE (logical system)--- This scenario is working fine.
IDoc to File -- Seeting done in R/3 like SALE (Logical system, Distrubtion Model (Port, Partner Profile)) -- This scenario is working fine.
Now I need to move to PI 7.1 -- for File to File , File to IDOC and IDoc to File Scenarios.
Please let me know do I require to make any changes in Design and Configuration and settings in PI 7.1 and R/3 for above scenarios or it will work fine as it is already working for PI 7.0
If changes are required please let me know what changes to do for each scaenario and pls also send blogs for that.
Regards

>
Rickkk wrote:
> Hi,
>
> Idoc metadeta is updated through idx2?
>
> Regards
If there is no metadata maintained for an idoc type, the metadata for that idoc type gets loaded when an idoc of that type is received by PI for the first time. If you are looking at loading metadata of all idoc types before the first run, its really not required. Just make sure that the port is configured properly. Although, there is no harm in preloading the metadata using IDX2.
You need to use IDX2 mandatorily when the the metadata changes and the metadata in ECC and PI is different. In that case, you need to delete metadata for the changed IDoc type and then either you can update the metada through IDX2 or let the system take care of.

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.

Pass through scenario in SAP PI with no mapping for File to IDoc and Idoc to file scenarios

Hi Experts,
Can i have step by step process in SAP PI for pass through scenario with no mapping in case of file to Idoc and Idoc to file both cases please.
What objects i can skip.
My PI system is 7.3 dual stack.
I have seen below blogs, still its confusing to me.
When and how to create an scenario in SAP PI without mapping objects.
Pass Through Scenario with no Mapping in PI 7.1
Appreciate your help on this.
Regards,
Mohan.

Hi Mohan
In pass thru interface you don't need to create any ESR objects, only ID objects are required.
Just Create a Receiver Determination and Receiver Agreement for your scenario (no need for Interface Det. and Sender Agreement).
Specify the IDOC in the Sender Interface and namespace as urn:sap-com:document:sap:idoc:messages
Or instead of creating objects manually, Run the wizard with Idoc name/namespace in sender/receiver interface
Regards
Osman

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

How to encode XML to Idoc and decode Idoc to XML in business connector?

Hi all,
first of all: thanks for all, who are reading and perhaps responding this question!
Here some facts and my question(s):
The facts:
- I have the business connector version 4.6!
- I'm not working with any SAP Netviewer!
- I have XML files on an FTP-server and Idoc-files on an FTP-server --> so no connection between SAP and business connector, meaning: the files are just on the ftp-server!
What am i doing and what is working properly:
- Business connector logs in into the FTP-server (with FTP-service: pub.client.ftp:login)
- gets the file (with FTP-service: pub.client.ftp:get) (the idoc-file, when i want to convert it into XML or the XML-file, when i want to convert it into idoc-format)
- puts the file into another place in the server (with service wm.PartnerMgr.gateway.transport.FTPTransport:OutboundProcess)
!!!So far only getting and putting of the file works!!!
What is missing between getting the file in one format - for example idoc-format - and putting the file into the server in the other format - for example XML-format is:
CONVERSION FROM XML INTO IDOC AND VICE VERSA
My question:
- which services i have to use between getting and putting the files?
Thanks to all,
Tamer

Hi,
I have the same problem. I do fix it?
Thanks
Wilson Xavier
Brazil

Idoc and http adapter

Idoc and http adapter resides in ABAP stack. So how do we monitor these two adapters ? It wont be visible in RWB ?

Hi,
To know the difference i suggest u try to do it by ur self only.
Login in to Runtime Work bench- component monitoring-Adapter engine-communication channel monitoring- Filter the communication channel with name.
and click on message id of that channel, it will show u the steps by step log for that channel.
MONI is used for message monitoring.
chirag

Idoc and Bdoc

Similar Messages

Maybe you are looking for