Status for IDOC

Hello Everyone,
after inbound processing through test tool (we19) the idoc is in error (rather warning) state. The error being
"No status has been passed to/by ale layer".
What exactly is the problem which gives this type of error.
regards
Rahul.

Hi Kesi,
Incase of the inbound, we must update the idoc status. Please refer a sample code that is updating the idoc status,
FM to create the notification items
  CALL FUNCTION 'ALM_PM_NOTIFICATION_ADD_DATA'
    EXPORTING
      number                  = v_notification
IMPORTING
  NOTIFHEADER             =
  NOTIFHDTEXT             =
   TABLES
  NOTFULLTXT              =
     notitem                 = i_noitem
  NOTIFCAUS               =
  NOTIFACTV               =
  NOTIFTASK               =
  NOTIFPARTNR             =
  KEY_RELATIONSHIPS       =
     return                  =   i_return_add.
  READ TABLE i_return_add WITH KEY type = 'E'.
  IF sy-subrc EQ 0.
    v_noti_error = 'X'.
    idoc_status-docnum = v_docnum.
    idoc_status-status = '51'.
    idoc_status-msgid  = 'IM'.
    idoc_status-msgno  = '147'.
    APPEND  idoc_status.
  ELSE.
    LOOP AT i_noitem.
      idoc_status-docnum = v_docnum.
      idoc_status-status = '53'.
      idoc_status-msgid  = 'IM'.
      idoc_status-msgno  = '654'.
      idoc_status-msgv1  = i_noitem-item_key.
      APPEND  idoc_status.
    ENDLOOP.
  ENDIF.
Hope this will solve your problem.
Thanks
Kathirvel

Similar Messages

  • System status for IDOC creation and processing for production orders

    All
    I am creating IDOCs for production orders to send requirements to an external WM system for kitting execution.
    I need to know whether there are any system statuses to notify me when an IDOC has been created,failed and processed. If not, how do I go about creating user defined statuses for these statuses.
    Second question, which idocs should I use to confirm, teco and cancel the production orders from an external system?
    Thanks
    Evan

    HI Evan
    u can use the standard program - RBDMOIND scheduled in back ground to update the Idoc staus ,
    this helps to update the IDoc Status from
    '03     Data passed to port OK  '  to
    '12     Dispatch OK'
    status 03 indicates the IDoc is successfully transmitted to Communication Layer and the Status 12 helps to confirm the data dispatch to the receiving port.

  • System status or user status for IDOC creation and processing for prod ord

    All
    I am creating IDOCs for production orders to send requirements to an external WM system for kitting execution.
    I need to know whether there are any system statuses to notify me when an IDOC has been created,failed and processed. If not, how do I go about creating user defined statuses for these statuses.
    Second question, which idocs should I use  to confirm, teco and cancel the production orders from an external system?
    Thanks
    Evan

    For the first part of your query refer to the technical forums.
    For the second part - refer to Idoc - LOIPRO01, it has a segment for Order status, that should be of interest.
    Attn Moderators
    I think it would be better to move this thread to a technical forum, so the requester can get the most relevant information.

  • Status for idoc to edit and reprocess it

    Hi ,
    I have a senario in which i need to hold the idocs for invoice coming as inbound in SAP .
    Then once the PO is created editing the Invoice idocs to add PO by editing the IDOC and reprocess the same idoc and post invoice corresponding to PO in SAP and then change the status of that idoc to 53.
    Can someone help me,with the status that i need to set to only have the idocs in SAP  .
    And then use those idocs to edit anf add PO and save it for status 32 (idoc edited).
    And run some standard program to change the status to 53 with invoice created.
    Thanks,
    Richa

    Richa,
    You can set the idoc status to '51' in the customer exit of inbound idoc processing function module . Check the TABLES/CHANGING/EXPORT parameter of FM for something like EX_PROTT .. here you can pass the error message after checking the PO number ..
    I'm not sure how are you linking Accounting document to PO.. you can use your logic to update the PO/set the idoc in error status in customer exit .
    -Tushar Shukla

  • Did anyone know how to update status for Idoc Finsta01

    Hi ,
    Did anybody did updating idoc status and message for idoc type FINSTA01.
    In Lockbox idoc_input_lockbx.
    If any BADI avilibale fr this to update.
    Thanks,
    Madhu

    Option 1:
    See SAP Help as below you will get the idea-
    Certain IDoc statuses are classified as archivable in the standard system, while others are not. You can display or change this classification.
    The current status of an IDoc must be archivable before the IDoc can be archived.
    Procedure
    Choose SAP Menu -> Tools -> Business Communications -> IDoc Basis -> Control -> Status -> Maintain Status Value.
    To change entries, choose .
    Select the required status. By double-clicking you can call a detail screen, in which you can display or change the archivability.
    By using or you can display or change all statuses one after another.
    Option2: I think it might be possible using generate status file for the outbound IDOC and then change the status in the file further process it. But I am not sure, I just had a look at the Xns in WEDI and made this story
    Thanks,
    Naren

  • Missing data status for Idocs : HR ORG Upload in SRM

    Hi All,
        We are using ALE Idocs for uploading HR ORG in SRM system.We are getting some IDocs errors. 51 status is 'Missing data'.
    Details description like below:
    Missing data
    Message no. HRALX00_ORG315
    Diagnosis
    It has been determined that the employee 00036837 has been received for the first time. However, not all the data that is needed to create a business partner has been received. In this case, the infotype 1001 and the subtype A209 have not been entered for the employee.
    Procedure
    Maintain the filter of the appropriate distribution model. To do this, call transaction BD64 in the source system. Add a new filter group to the data filter. Assign the following values for the filter group: infotype: 1001, object type: P, subtype: A209. After you have generated the partner profile again and distributed the distribution model, you can redistribute the relevant IDoc.
    Please help me How to resolve this issue.Please let us know if you need any more information.

    Hi Ramchandra,
    it s the best solution to your query to load the IDOCs manually using the context menu of the datapackage or IDOC --> manual update and then refresh the load as it is not throwing any error
    check do you have enough number of process running in your system
    check for TRFC logs
    Thank you

  • Batch job for IDOC processing in 64 status

    Hi experts ,
    i want to know the name of Batch job for IDOC processing in 64 status.
    I have configured the partner profiles as 'process immediatly'.
    So with this configuration whenever an idoc comes in production it gets processed immediatly and automatically.
    i want to know how they are getting processed automatically.
    is there any job which looks for these idocs(in 64 status and process immediatly flag) and process it.
    What is the trigger for thiese idocs processing???
    Please guide me
    thanks in advance
    Anit gautam

    Hi Thanks for ur reply.
    =====Upon arrival, "process immediately" should fire that process =====
    how it is getting fire?
    means is there any batch job running which looks for idoc in 64 status or is there any event which get triggered when an idoc
    comes in 64 status.
    why we use OYEB transaction???
    Regards

  • 51 status for inbound IDOC

    Hello All,
    while importing an idoc am getting following error with 51 status
    No import record for IDoc available.
    anyone please tell me  where to maintain the import record and how.
    thx in advance
    Sippy.

    Hi..
    Test your IDoc and check whether input file is available or not.
    using Tcode : we19.

  • What is the internal  processing for idocs

    Dear friends this is subbu working as a abap consultant.
    can any body explain the how idocs are transfered (inbound process and outbound process)

    1.Here out bound means sender.Inbound mens --receiver.
    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.
    There are two filtering in IDoc.
    Segment Filtering:
    Segment filtering can be achieved using T/Code BD56. Here you can suppress a whole segment irrespective of data inside it . You have to give Message Type / Sender Prrtner / Receiver Partner.
    Data Filtering:
    Data filtering can be done in dustribution model (BD64) where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
    Please check this link for more information.
    http://help.sap.com//saphelp_470/helpdata/EN/0b/2a611c507d11d18ee90000e8366fc2/frameset.htm
    Reward points..

  • Pls send material for idocs in ECC 6.0

    Pls send material for idocs in ECC6.0

    Hi sitaram s ,
    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.
    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.
    Archiving Processed IDocs
    IDoc archiving is a two-step process:
    1. Archive the IDoc.
    2. After that another job will be generated. You can see in your SARA for your trigger to delete those archived IDocs.
    Have a look at transaction WE47, set "Archiving - Possible" for all statuses to be archived. Use transaction SARA with object IDoc to archive. If the above is set then all IDocs are archived the same way.
    Transaction SARA works in the following way:
    On the main screen enter IDoc as the object. Click on Customising -> Technical settings. This shows the logical filename (configured via transaction FILE & SF01) that will be used to get a filename when writing the archive files. It also shows the document type (that links to an archive via transaction 0AC0) or the archive, depending on SAP version. You can also set the size of the archive files and whether the deletion and storage jobs should execute automatically or not.
    On the main screen there are, amongst others, buttons for ARCHIVE, DELETE and MANAGEMENT. When you click on ARCHIVE you will go to a screen where you can create variants, and set the parameters for the archiving job. The EXECUTE button will schedule this job. If the "start automatic" tic for the deletion program was not set in customising, you will need to go to the DELETE button on the main screen to schedule the deletion jobs, after the archive job has finished. This schedules a job per archive file. In MANAGEMENT you will be able to see the statuses of each archive run.
    SAP Integration Using ALE(Application Linking and Enabling)
    - IDOCS -
    http://www.thespot4sap.com/Articles/SAP_ALE_IDOCS.asp
    Updating IDoc data in segments,Changing a control record of an IDoc,Getting IDocs linked to Application documents,
    Displaying and IDoc in a report,Read IDoc from Database,Creating and sending an IDoc,Update IDoc status on the database
    ALE Inbound Pre-Processing
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    cheers!
    gyanaraj
    reward points if u find this helpful

  • R3 settings for IDOC-IDOC scenario

    Hi,
    For IDOC to IDOC scenario what are the settings we have to in R3 System other than XI configuration settings.
    What are setting for both sender and receiver side.
    Thanks,
    Kishore

    Hi Kishore,
    http://help.sap.com/saphelp_nw04/helpdata/en/18/22b800773211d396b20004ac96334b/content.htm
    http://www.erpgenie.com/index.php?option=com_content&task=view&id=346&Itemid=57
    http://searchsap.techtarget.com/loginMembersOnly/1,289498,sid21_gci994575,00.html?NextURL=http%3A//searchsap.techtarget.com/expert/KnowledgebaseAnswer/0%2C289625%2Csid21_gci994575%2C00.html
    http://www.thespot4sap.com/Articles/SAP_ALE_Other_Concepts_Conclusion.asp
    Refer this material..
    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.
    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.
    You can directly create an iDoc using some transaction like...
    Use TCODE bd10 - to Send Data
    and TCODE bd11 - to Get Data
    and you can check the IDoc List using TCODE we02.
    As you want step by step procedure.
    1. Define Logical System and Assign Logical System
    TCODE sale
    2. Define RFC
    TCODE sm59
    3. Define Port
    TCODE we21
    4. Define Partner Profile
    TCODE we20
    5. Define Distribution Model
    TCODE bd64
    6. Send Data
    TCODE bd10
    7. Get Data
    TCODE bd11
    8. IDoc List
    TCODE we02
    There are basically two types of IDOCs.
    Basic IDOCs
    Extended IDOCs
    Idoc Components
    Basic Idoc
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extension Idoc
    Extending the functionality by adding more segments to existing Basic IDOCs.
    Creation of IDoc
    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.
    Create IDOC Type
    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
    u can also check all these links related to idocs
    http://www.allsaplinks.com/idoc_sample.html
    http://www.allsaplinks.com/
    http://www.sap-img.com/
    http://www.sappoint.com/abap.html
    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
    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://expertanswercenter.techtarget.com/eac/knowledgebaseCategory/0,295197,sid63_tax296858_idx0_off50,00.html
    http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
    http://help.sap.com/saphelp_47x200/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm
    Reward points if this helps
    Regards
    Pragathi.

  • Problem with WE19 Test tool for idoc process

    Hi,
    I have a idoc in 51 status. This idoc is used for order creation and its an inbound idoc.
    This idoc has around 2000 line items. On checking the status for this idoc, i find that in a particular line item(223) error is showing.
    So in WE19, I entered this idoc no. and deleted all the line items below the error line item. Now when I click on 'Standard Inbound', I am getting error mssg 'Receipient port invalid', 'idoc was saved but cannot/ should not be processed'.
    How to correct this. After this idoc is processed and generates a sales order, I want to insert the error line item and find the issue.
    Please help.
    Thanks & Regards,
    Hari Om

    Hi,
    Receipient port invalid You must have taken the IDOC from Production and put it in the development or quality I guess.That is why system gives this error.
    To solve this issue Click on edit control record fields that is first line. Change the port for the reciepient for example change it from SAPproduction to SAP development /SAP quality
    Incase of further queries please reply
    Regards
    Mano

  • Materials for idoc

    Hi am interested to learn about idocs can you provide me some useful links

    Hi saranya srithar  ,
    IDoc is an Intermediate document that holds application data.
    A container used to exchange data
    It is independent of the complex SAP structure to store data.
    It serves as the vehicle for data transfer.
    IDoc Type defines the structure and format in which the data is exchanged.
    It is similar to a structure in SAP
    IDoc data is an instance of IDoc Type
    IDoc  acts as a standard SAP interface to exchange business data through ALE.
    From an SAP system, an IDoc can be sent to and received from
    An SAP R/3 system
    An SAP R/2 system
    An EDI subsystem
    Any third-party application software
    Segments . Idoc data is arranged in Rows, The rows make up segments of an idoc. Each segment consists of fields/segments. Fields can contain data.
    These r all the t/codes which we will come across in IDocs:
    TCODE     TTEXT
    BD10     Send Material
    BD100     IDoc display object channel view
    BD101     Consistency check
    BD102     Outbound registry
    BD103     Inbound registry
    BD104     maintain tbd53
    BD105     Maintain Supported Business Objects
    BD11     Get Material
    BD12     Send customer
    BD13     Get customer
    BD14     Send vendor
    BD15     Open vendor
    BD16     Send Cost Center
    BD17     Get Cost Center
    BD18     Send General Ledger Account
    BD19     Get General Ledger Account
    BD20     IDoc passed to application
    BD21     Select change pointer
    BD22     Delete change pointers
    BD23     Delete serialization data
    BD24     Send Cost Elements
    BD25     Send Activity Type
    BD26     Get Activity Type
    BD27     Send cost center activity prices
    BD28     Send obj/cost element control data
    BD30     Distribute material object list
    BD31     Distribute document object list
    BD32     Distribute plant allocations(matBOM)
    BD33     Distribute material variants (ALE)
    BD34     Distribute order BOM
    BD35     Send Business Process Groups
    BD36     Send Business Processes
    BD37     Send Business Process Price
    BD40     Read change pointer for group
    BD41     Dispatch IDocs for group
    BD42     Check IDocs for group
    BD43     Post IDocs for group
    BD44     Assign Message Types to Serlz. Group
    BD47     Dependencies between methods
    BD48     Dependency method - message
    BD50     Activate Change Ptrs for Mess. Type
    BD51     Maintain function modules (inbound)
    BD52     Activ.change pointer per chng.doc.it
    BD53     Reduction of Message Types
    BD54     Maintaining Logical Systems
    BD55     Maintain IDoc Conversion
    BD55OLD     Maintain IDoc Conversion
    BD56     Maintain IDoc Segment Filters
    BD57     Maintain link and serialization ty.
    BD58     Convert organizational units
    BD59     Allocation object type -> IDoc type
    BD60     Additional data for message type
    BD61     Activate Change Pointers - Generally
    BD62     Define Segment Conversion Rule
    BD62OLD     Define Segment Conversion Rule
    BD63     Transport ALE Tables of Message Type
    BD64     Maintenance of Distribution Model
    BD65     Maintain IDoc type required fields
    BD66     IDoc type field -> change doc.field
    BD67     Maintain methods (inbound)
    BD68     Maintain Lists
    BD68OLD     Maintain Lists
    BD69     Assignment of Message Type to IDoc
    BD70     Synchronize Number Ranges
    BD71     Define FM for dependent bus. object
    BD72     Activate Events
    BD73     Reposting of IDocs (ALE)
    BD75     Convert IDoc Status
    BD77     Distribution of control data
    BD78     Monitoring control data distribution
    BD79     Maintain IDoc Conversion Rules
    BD79OLD     Maintain IDoc Conversion Rules
    BD81     Filter objects parameter filtering
    BD82     Generate Partner Profiles
    BD83     Send IDocs after an ALE error
    BD84     Post IDocs after ALE error
    BD85     Consistency check for transfer
    BD86     Consistency check for sales
    BD87     Status Monitor for ALE Messages
    BD89     Control data model. - initial screen
    BD91     Send Characteristic
    BD92     Send Class
    BD93     Send Classification
    BD95     Specify ALE object types
    BD96     filter objects of receiver determin.
    BD97     Assign RFC dest. to Logical Systems
    BD98     Consistency Check Workflow Connectn.
    BD99     Message type dependencies
    WE02     Display IDoc
    WE05     IDoc Lists
    WE06     Active IDoc monitoring
    WE07     IDoc statistics
    WE08     Status File Interface
    WE09     Search for IDocs by Content
    WE10     Search for IDoc in Archive
    WE11     Delete IDocs
    WE12     Test Modified Inbound File
    WE14     Test Outbound Processing
    WE15     Test Outbound Processing from MC
    WE16     Test Inbound File
    WE17     Test Status File
    WE18     Generate Status File
    WE19     Test tool
    WE20     Partner Profiles
    WE21     Port definition
    WE23     Verification of IDoc processing
    WE24     DefaultValuesForOutboundParameters
    WE27     DefaultValues for Inbound Parameters
    WE30     IDoc Type Development
    WE31     Development IDoc Segment
    WE32     Development IDoc View
    WE34     Object for Display of XML IDocs
    WE40     IDoc Administration
    WE41     Process codes, outbound
    WE42     Process codes, inbound
    WE43     Funct.module: Status record display
    WE44     Partner Types and Checks
    WE45     Forward (inbound) (V3, EDILOGADR)
    WE46     Error and Status Processing
    WE47     Status Maintenance
    WE50     System process codes: Texts
    WE51     System process codes: Change texts
    WE54     FMs for changing file names
    WE55     Function Module for Path Names
    WE56     IDoc Administration
    WE57     Assignment Messages for Appl. Objs
    WE58     Status process codes: Texts
    WE59     Change status process codes
    WE60     Documentation for IDoc types
    WE61     Documentation for IDoc record types
    WE62     Documentation for segments
    WE63     Documentation
    WE64     Documentation message types
    WE70     Conversion: Basic types
    WE71     Conversion: Extensions
    WE72     Conversion: IDoc types
    WE73     Conversion: Logical messages
    WE81     Logical message types
    WE82     Assign Messages for IDoc Type
    WE84     Assignment of IDoc and appl. fields
    WE85     Create Rule Names
    WEBU     Printing Labels via Assortment List
    WEDI     EDI Basis
    WEINBQUEUE     IDoc Inbound Queue
    WEKF     Purchase order SAP Retail
    WEL0     Forward (inbound) (EDILOGADR)
    WEL1     EDI: Interface Invoice for EDILOGADR
    WELI     Maintain Status Groups
    cheers!
    gyanaraj

  • Configuartion for IDOC

    Hi Experts,
    If XI is sending an IDOC to R/3. wht are the configurations steps are required at XI and R/3 side. plz list down all the TCODES that are used at both sides?
    Thanks
    Faisal

    Hi Abdhul...
    Config for IDOC ...
    Do these configurations in R/3 and in XI...
    Step for Configuration fo IDOC in R/3
    SM59-rfc destination
    IDX1-port
    IDX2-load metadata
    we05-IDoc status records
    BD54-Create Partner Number
    We20-Create Partner Profile
    WE19-Testing IDoc Processing
    SAP XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2)
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    SAP R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    Reward points if it is useful..
    Thanks,
    Satya Kumar
    Edited by: SATYA KUMAR AKKARABOYANA on Mar 19, 2008 4:13 PM

  • Requirements for IDOC

    Hi friends,
                    Could you please tell me the details required for doign a IDOC scenario.
                     I want the details seperately when IDOC is a sender and also when IDOC is a receiver.
    Note: High reward points for the reply

    HI
    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.
    Idoc creation
    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.
    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.
    You can get the all description from below tcodes
    WE60-> Documentation for IDoc types
    WE09-> Search for IDocs by Content
    BD87-> Status Monitor for ALE Messages
    WE63 -- information about Standard IDOC in R/3
    WE64 - Details about process codes
    WE82, WE30, WE31 -- IDOC Types.
    SAP R/3
    R/3 to XI
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (We21)
    a) First Select Transactional RFC and then click create button
    b) Enter the destination port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Create Partner Profile (WE20)
    a) Create New
    b) Create the Partner no. name as same the logical system name of the destination system.
    c) Select Partner type LS
    d) Enter details for Type: US/USER, Agent, and Lang.
    e) Click on the + button to select the message type.
    f) Select Partner no. and LS which ever create above.
    g) Select Message type
    h) Select Process code related to the Message type.
    I) save.
    XI to R/3
    1) RFC Destination (SM59)
    a) Choose create.
    b) Specify the name of the RFC destination
    c) Select connection type as 3 and save
    d) In the technical settings tab enter the details SAP SID/URL and system number#.
    e) Enter the Gateway host as same details above SID/URL.
    f) Gateway service is 3300+system number#.
    g) In the Logon /Security tab, enter the client user & Password details of Destination system.
    h) Test the connection and remote logon.
    2) Create Port (IDX1) ( Create port to get IDOC Meta data from sender system)
    a) Select create new button
    b) Enter the port name as SAP+SID (The starting char should be SAP)
    c) Enter the destination client.
    d) Enter the RFC Destination created in SAP R/3 towards other system.
    e) Save
    3) Load Meta Data for IDOC (IDX2) (To maintain IDOC Metadata, it is needed by XI because XI needs to construct IDOC-XML from IDOC. It is not needed by any sap system).
    a) Create new
    b) IDOC Message Type
    c) Enter port created in IDX1.
    Details ABT IDOC??????
    1)Use WE60 transaction.
    2)you need list of basic type idocs then use t.code WE60.
    To display IDOC list in particular time intervel use we02 or we05.
    where u can find the outbound and inbound processing idoc's.
    use t.code 'wedi' to get more information on idoc's.
    3)You can use the WE60 for Idoc Documentation
    & we can use WE30 for Idocs list
    Refer the below links for furtehr assistance
    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
    cheers

Maybe you are looking for