What is memory idoc , communication idoc

plz tell me about
         memory idoc , communication idoc.

hi kalyan,
Master IDOC : This idoc collects all the required data into
single IDOC and this is temporarily stored in memory.
Communication IDOC: there can be n number of communication
IDOCs generated. This comes into picture after the Master
IDOC is validated from the distribution model . And this
IDOC is stored in database table . you can see this IDOC
from we02 tcode..comm idoc is the physical idoc which is reciever specific
IDOC Programming
There are two processes in IDOC processing one is INBOUND PROCESS( IDOC coming to the system and its handling at various stages)  and the other is OUTBOUND PROCESS( IDOC is send to other system  . Separate ABAP programs are written for these 2 processes and different configuration settings are required for each one .Depending upon the trigeering mechanism different programming approaches are used.OUTBOUND PROGRAMS handle the IDOC creation and INBOUND PROGRAMS handle the inbound IDOC and the data trasfer from the IDOC to the database tables.
NEED FOR ABAP PROGRAMMING arises if
1)New IDOC was created
   Depending upon the triggering mechanism i.e change pointer,message control
   etc the programming technique changes and the type of process.
2)Existing IDOC was extended
   User Exits are used to populate data in new segments added and to read them 
   back.
3)To enhance an exsiting process.
   User Exits are used . 
Basic structure of an OUTBOUND PROGRAM
The basic structure of all outbound programs is same. The CONTROL
record which is of TYPE EDIDC has to be filled. It contains important fields like
IDOCTP      IDOC type
MESTYP    Message Type
RCVPRN    Recieving Partner (Destination)
RCVPRT    Partner Type (it is LS i.e Logical System)
The DATA RECORD internal table which is of TYPE EDIDD has to be filled
in the same order as there are segments in the IDOC definition.
It has 2 important fields which are to be filled ,these are
SEGNAM  Name of the segment
SEGDATA Data in the segment and can be upto 1000 bytes.This field
                is corresponds to each data segment in the IDOC.
e.g.
DATA INT_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA W_SEGDATA LIKE zsegment "custom segment zsegment
       INT_EDIDD-SEGNAM = 'ZSEGMENT'
       W_SEGDATA-field1 = value    "taken from some table
       W_SEGDATA-field2 = value    "taken from some table
       INT_EDIDD-SEGDATA = W_SEGDATA
       APPEND INT_EDIDD
This will fill the data record corresponding to the segment ZSEGMENT . For all
segments the sam steps will be repeated until all the data corresponding to all the
segments in the idoc is filled in the internal table of type EDIDD.
      There is only one control record and can be multile data records in the idoc
structure.
Which data is to be extracted from the tables to be filled in EDIDD type internal table is determined in standalone programs from the objects which are specified in the selection screen and from the object key passed to the function module in case of message control and is taken from BDCP table in case of change pointers using function modules "CHANGE_POINTERS_READ"
      In case of stand alone programs and function modules based on change pointers method the function module "MASTER_IDOC_DISTRIBUTE" is used to send the IDOC to ALE layer for distribution ,in case of message control it is handled automatically by the RSNASTED program invoked by the message control.                     
OUTBOUND PROCESS AND OUTBOUND PROGRAM
Outbound programs are used in outbound process to genearte IDOCs . There
purpose is to extract the data from the tables and to fill the IDOC data records
and the control record in the IDOC and pass ito the ALE layer for distribution to the recieving system .
Depending upon the triggering mechanism (how and when the outbound program will be started different techniques and interface is used for outbound program.
1)Message control
Application like PO(purchase order) creation use this technique , where the output type is linked to the application(Message control is a configurable cross application component which can be set in IMG .Such programs are created in the form of function modules and linked to the output type which is linked to the apllication.These have predefined interfaces.
In outbound programs(function module) that use message control the key of the
application document is passed to the function module whcig will read the data from the table depending upon the key passed(NAST structure) and fill the IDOC segemnts with the application data.The control record is also passed to the function module but is not fully filled, the rmaining fields are filled and the control is passed back to the calling program which is RSNASTED and is invoked by the
message control to process ALE and EDI output types and this program on recieving the IDOC data will create the physical IDOC in the system.
The parameteers passed to the function module are
IMPORTING PARAMETERS
OBJECT LIKE NAST
  It contains documents key.
CONTROL_RECORD_IN  LIKE EDIDC
  It contains the partailly filled control record
EXPORETING PARAMETER
OBJECT_TYPE
CONTROL_RECORD_OUT LIKE EDIDC
TABLES
INT_EDID LIKE EDIDD
The internal table used to fill the data records in the same order as they exists in 
the IDOC.
The important parameters that should be filled in the custom function module are
CONTROL_RECORD_OUT and  INT_EDIDD .The OBJK field of the structue NAST contains the key of the apllication document.
2)Stand alone programs
  Generally used for Master Data transfer and as such depending upon the requirement can have different interfaces.The programs have a selection screen which has select options to select the objects, and parameters for specifying the recipient Logical System and the Message Type.
Data is selected based on the specified objects from the tables . and control record of type EDIDC is created and filled with important values like DIRECTION ,IDOCTP,RCVPRT,RCVPRN and MESTYP .
Data is filled in an internal table of TYPE EDIDD according to segment definitions
and in same order and the function module MASTER_IDOC_DISTRIBUTE is called passing the control record and the internal table containg IDOC data and importing an internal table consisting of control records for each communication IDOCS created.
3)Change pointer
Change Pointer table is read and checked if changes were made to important fields , if so the outbound program will be triggered automatically , these have predefined interfaces
thanks
abdul
reward me if usefull

Similar Messages

  • Creation of communication IDOC's from BD12

    Hi All,
    I am triggering BD12 transaction for few customers.
    For some set of customers i am able to create both Master IDOC & Communication IDOC.
    Ex: For the customers whose Account Group is : 0001
    For other set of customers i am able to create Master IDOC but Communication IDOC i am not able to create.
    Ex: For the customers whose Account Group is: ZCRD
    Customer in account group ZCRD do not have sales area data maintained, where in there is no information maintained for sales, billing, shipping & Partner functions.
    Where as customers in account group 0001 have the sales area data maintained.
    This is the functional analysis of both the Account Groups.
    Can anybody tell the reason why Communication IDOC's are not created for Account Group-ZCRD customers & For Account Group-0001 communication IDOC's are created!
    Can anybody solve this issue!
    I have debugged this issue step-by-step for both Account Group's [ZCRD, 0001] related customers, There is no check in code for Account Group-ZCRD so that communication IDOC's does not get created.
    Also both Account Group's customers went through same piece of code, Only at in F.M call to MASTERIDOC_CREATE_REQ_DEBMAS
    the returned parameter CREATED_COMM_IDOCS is 0 for Account group-ZCRD related customer where as it is 1 for ACcount Group-0001 related customer.
    Can anybody resolve this issue so that Communication IDOC's will also be created for Account Group-ZCRD related customers!
    Thanks in advance.
    Thanks,
    Deep.

    Hi Naveen,
    Thank you for the reply.
    In BD64 i have checked the details.
    There is no checks/filteration against Account Groups-ZCRD/0001.
    One more thing is the customers for Account Group-ZCRD are
    Credit Master accounts.
    Is there any way i can find the resolution for the same!
    Thanks for the reply.
    Thanks,
    Deep.

  • Difference b/w Master & Communication IDocs

    Hi All,
    What is the difference b/w Master & Communication IDocs.
    Akshitha.

    The master Idoc is the Temporary Idoc & kept in memory buffers until communication IDocs are generated. These recipient-specific IDocs are called Communication IDocs and are Stored in the Database.
    But the master Idoc is not.
    The Communication IDocs are transferable IDocs not the Master Idoc. For every Receiver, each separate communication Idocs will be created from master Idoc.
    more info on idocs....
    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.
    Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    Regards
    vasu

  • Regarding generating Master/Communication IDOCS's from BD12 forfewcustomers

    Hi All,
    I have one issue when i am using BD12.
    I am inputting some customers and output type/message type and executing the transaction for some customers it is generating both Master & Communication IDOCs, But for some customers it is generating only Master IDOC's but not Communication IDOC's.
    These kind of cases are coming for particular Account Group [Ex: ZCRD etc..],
    Can anybody tell me what is the relation between Account Grooup & Customer & why it is stopping generation of Communication IDOC's for particular Account group related customers.
    How can i solve this issue!
    Can anybody solve this issue!
    Thanks in advance.
    Thanks,
    Deep.

    Hi All,
    Any inputs/Solution for the above posted issue!
    Resolution in this regard will be appreciated.
    Thanks,
    Deep.

  • Sender Communication Channel for Integration Scenario IDoc - XI - IDoc?

    Hello All,
    One general question. I have to configure an IDoc - XI - IDoc Scenario. For this Scenario I have to configure an Receiver Communication Channel (IDoc Adapter) to the Backend System but what about Sending Communication Channel for the Sending R/3 system.
    Is the (IDoc) Communication Channel from Sending system to XI required to configured?
    Many thanks in advanced!
    Jochen

    Hi Jochen,
    for sending IDOCs from SAP to XI, sender IDOC adapter is not required. when XI will send the IDOC to a SAP system, then receiver IDOC adapter is needed.
    Thanks,
    Rajeev Gupta

  • Doubt on IDOC TO  IDOC communication

    Hi Experts,
    I have a doubt on IDOC to IDOC communication:
    Plz clarify it
    1. what is the need of passing same IDOC from one system to other system through XI while communicating between two systems,it can be done by using ABAP also ?
    2.what is the advantage of passing like this through XI compared to ABAP?
                           Plz clarify good answers will be rewarded .
                                                                                    Regards,
                                                                                    Vinod.

    Hi,
    See when you are dealing with Only IDOC to IDOC Communication means there is no need of XI here.
    You can go with ALE also here.
    Situations to go to XI.
    1) when you have the Different field mappings
    2) When you are having the multiple receivers
    3) when you are dealing with Bundling & Transformations
    Reward Ponts If Helpful
    Regards
    Giri

  • Doubt on IDOC communication

    Hi Experts,
                      I have a doubt on IDOC to IDOC communication:
    Plz clarify  it
                        1. what is the need of passing same IDOC from one system to other system    through XI  while communicating between two systems,it can be done by using ABAP also ?
                         2.what is the advantage of passing like this through XI compared to ABAP?
                   Plz clarify good answers will be rewarded .
                                                                                    Regards,
                                                                                    Vinod.

    The need for an XI to transfer IDOC from one system to another sytem : the answer for this comes from the basic of using XI as a middle ware.
    1. When you connect IDOC directly to another system without using XI....you are going for P2P connections then this leds to problem in monitoring if the data breaks, you have to login to both systems to check......
    2. we have a central monitoring tool for check this iterface..
    3. You can build a message orchestration using the BPM if required for this IDOC...
    4. You can have full control in the IDOC processing...i mean do you want to send ot not and so on.
    Beofre XI or typical connection between 2 SAP Systems were using IDOC directly but they are P2P connectinons,,,no control, no monitoring....NO orcheatreation...etc.....

  • What is Basic type in IDoc?

    Hi all,
    What is Basic type in IDoc? Please explain me in layman terms. How to see the details of basic type ALEREQ01? Please point me to related files or threads.
    Thanks,
    Charles.

    Hi,
    <b>IDOC Basic type means, IDOC type delivered by SAP</b>. When you want to modify the IDOC provided by SAP, you create an Extension IDOC of Basic type.
    <b>This is what SAP says about "Basic Type".</b>
    IDoc type supplied by SAP (standard format for data communication). Basic types can be modified by customers to create a new, upward-compatible IDoc type. Basic types can also be defined by customers and modified at a later date. Basic types and subsequent modifications created by customers are not necessarily upward-compatible.
    <b>To check detail of any IDOC, user transaction <u>WE60</u>.</b>
    Check area Menu <b>WEDI</b>. Its a Area menu for all IDOC related transaction. Enter command WEDI ( where you enter transaction code - Top left of screen ). Also, this command only works from very first screen of SAP. This is SAP eacy access screen you see when you logon into SAP. Since WEDI is area menu, you can only execute from very first screen.
    Here is the list of other area menu.
    WEDI - IDOC and EDI Basis
    BALE - ALE Administration
    Let me know if you need any other information.
    Regards,
    RS

  • No Communication IDOC generating for MATMAS --- Urgent

    Hi,
    I have two systems in the Landscape; one is DA1 and other is DA3. Both systems are exactly identical.
    When I am triggering idoc of message type MATMAS from bd10 in DA1 systems, it successfully generating MATMAS idoc and I am able to see that idoc in we02 but when I am triggering MATMAS idoc in DA3 system; it is generating Master IDOC but it is not generating Communication idoc for Message type MATMAS and in we02 as well I am not able to see any such idoc.
    Both the Systems are exactly same and I have checked ALE configurations in both the systems, they are same.
    Can anyone suggest, what could be the problem.
    Regards,
    Varun

    hi,
    As Bineah mentioned check the distribution model, distribute it and generate partner profile.  verify all the configurations once again i hope it will do.
    if any queries let me know .
    ~linganna

  • Master IDOC but not the communication IDOC

    Hi
    what is master IDOC and the communication IDOC
    what is the diff?
    i have installed sap gui in my system and how to connect the sapserver through internet?

    HI SAPABAP,
    1>Master idoc is only created but it won't be stored in database,where as communication idoc is stored in database.
    2>Data is transferred via communication idoc not by master idoc.
    Regards,
    Nagaraj

  • Difference between Master Idoc and Communication Idoc.

    Can anyone list out the difference between Master Idoc and Communication 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.
    Form and content: IDoc terminology
    As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
    A message refers to the contents of a specific implementation of an IDoc; it’s a logical reference. This differs from a reference to the IDoc itself, which specifies the message’s physical representation. Think of it this way: If you’re watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayor’s limousine (which is specific to the mayor) is the IDoc. You’re building a logical object, and the IDoc is both its container and the vehicle that moves it.
    The IDoc control record
    Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDoc’s functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
    Layout of an IDoc control record
    This “cover slip” format informs the receiving system of the IDoc’s purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
    Data records
    The data records following the control record are structured alike, including two sections: a segment information section and a data section.
    In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner company’s Oracle system, which has no such data dictionary.
    The second part of the record is the data itself, a storage area of 1,000 characters.
    Status records
    If you’ve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, you’re familiar with the list of stops and transfer points through which a package passes on its way to you.
    This collection of records is exactly what you’ll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
    Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
    IDoc Base
    IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
    This “IDoc Base” gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
    Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
    Multiple messages
    One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
    IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, it’s no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
    A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

  • 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.

  • Problem in the formation of communication idoc

    Transfering master data from our system to the client system.
    After doin all the outbound configurations from BD10 im sending the materials.
    ALL the master idoc are created but only 0 communication idoc is created. how can i solve the problem.

    Hi,
    Since you are transferring the data through ALE, you need to make settings in BD64 (distribution model) and also WE20 paretner profile.
    How to maintain:
    BD64:
    Go to Edit mode and click on button 'Create model view' and fill the popup inputs 'Short text, Technical name, start date and enddate'.
    Now click on button 'Add message type' and give 'Model view, Sendor, Receiver and message type'.
    These should be same as that of WE20.
    Save it and then try once again. now issue will be resolved.
    Please reward if useful.
    Regards,
    Ramesh

  • O Communication Idocs

    Hi
    I have an error. In QAS, I have an Idoc to File scenario. I triggered an idoc from WE19 by adding data manually and it reached XI. I went to BD10 and then tried to trigger from there. I got an error like this
    1 Master Idoc set up for message type
    0 communication IDoc(s) generated for message type
    Any clue why I get this error ?
    Midhun

    Sandeep
    I created a Model View. Now, I don't see nodes under that as I see under other scenarios. I only see the Model View that I created ECC_XI_File. How do I get nodes? I just have one line there. I saved it. Should I add more details ?
    I have only entered the four fields
    Where do I enter the Logical System Names of both Source and Target ?
    Midhun

  • Monitoring receiver idoc communication channel

    Hi All
    I have an idoc to idoc scenario.
    I am unable to see my receiving idoc communication channel in communication channel monitoring of RWB. It is not available in the dropdown list.
    I want to have a look at the audit log to see if the idoc is delivered to the receiving system.
    How can i monitor receiver idoc communication channel?
    How can i ensure that the idoc is delivered to the receiving system?
    In sxmb_moni, status is checkered flag.
    Many Thanks
    Chandra Sekhar

    Hi,
    IDOC is on ABAP stack hence u can not monitor IDOC.
    For testing purpose
    1) GO to SXMB_MONI check the status of message.
    2) Go to R3 and enter Tcode WE02 and check the IDOC which is send from XI. enter the idoc name and see the status of IDOC it should be in green status if it is posted successful or else see the status record for checking the error message.
    chirag

Maybe you are looking for

  • How to compare date and time together

    Hi, How to compare Date and Time together? For example in a database table there are two fields rundate and runtime.  I want to compare these two with perticular date and time in the program.  Like, I want to pull all the records where the records's

  • Smart sync error detection

    Hi, I am developing a Smart Sync application and I am trying to read the ErrorConflict inbox. There is a special class for it called surprisingly ErrorConflictInbox. I have at the backend a call transaction logic, and I am simulating an error in this

  • How to tell JSP for encoding Format??

    Hi all, I have following requirements 1. The user enters data in local language say kannada(indian langauage). The data should be stored in ms-access only in the form of local langauge. Customer dosnt want see some junk values or entity values. His r

  • Oracle 10g Express Edition - number of simultaneous connections

    Goodmorning, I'm goingo to test Oracle 10g Express Edition but I ned to know the max numbers of simultaneous connections it supports. Many thanks to all.

  • One keynote file opens another

    We use Keynote to display messages in various buildings on plasma TV's. Currently we have no way to display building specific slides in only one building. We would like to be able to have a standard keynote file that would be displayed in all buildin