Steps to archive idocs

hi
can anyone send me step by step documents for archiving idocs using tcode SARA using the archiving object IDOC.
or if there is any other option for archiving idocs.
we are on sap 4.6c version.
<i>points will be rewarded accordingly</i>
thanks

Check out links
http://sap.ittoolbox.com/documents/popular-q-and-a/archiving-processed-idocs-2884
http://www.sap-img.com/basis/delete-remove-of-idocs-from-r3.htm
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b81ed43d711d1893e0000e8323c4f/content.htm
http://www.topxml.com/biztalkutilities/walkthroughs/SAP%20IDoc%20Configuration.pdf
Hope this’ll give you idea!!
<b>P.S award the points.!!! DOn`t forget :)!!!!</b>
Good luck
Thanks
Saquib Khan
"Knowledge comes but wisdom lingers!!"
"Some are wise and some are otherwise"

Similar Messages

  • STEPS for creating IDOC .

    I need to creat IDOC for whenever  delivery is created .

    Hi
    Take the correct Idoc type and Message Type and process code from EDBAS and EDMSG tables and use
    see the doc
    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.
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • How to view archived IDoc's

    Hi experts,
      i need to view the archived content of the archived idocs.  i tried with SARI(Infostructure SAP_IDOC_001),
    but i cant view the content of the archived IDOC's. the scenario is like,
    > IDoc's are archived using SARA
    > Delete that IDOC using SARA
    > SAP_IDOC_001 infostructure got activated using SARI
    after that i tried to view the content in WE10, but i cant. Is thr any other steps i missed here?
    Plz help on this.
    Thanks,
    murugan.

    Hi,
    After activating Infostructure, Did you build the Info structure? If not then build it.
    Path > SARI > Customizing > Status > Build structure > Select the Archive file and run it.
    Note: After successfull execution the archive file will have green signle.
    Then you can display the archived IDOC's
    Hope this will help you.
    -Thanks,
    Ajay

  • Retriving Archived IDocs

    Hi,
    1) Is it possible to retrieve an archived Idoc? If yes how?
    2) Assume that an archived IDoc is in status 68. Please help confirm
    3) Is it possible to retrieve an Idoc in status 68? If yes how.
    Would greatly appreciate any help.
    Regards,
    Mick

    To chekc if Idoc is reloadable from arhive use
    EDI_IDOC_RELOADABLE
    To read an idoc from archive use
    EDI_IDOC_GET_FROM_ARCHIVE

  • Display archived IDOCs in transaction WE10 - click on IDOC number

    Hi experts,
    If you run transaction WE10 and display IDOCs not archived (from the database), from the list of IDOCs you can click on the IDOC number and then go to the screen that displays the IDOC information (Control, Data and Status records).
    However, if you run WE10 with archived IDOCs (Data Source is archive), you get to see the list of IDOCs but when you click on the IDOC number it doesn't go to another screen showing you the IDOC information but it stays on the same screen.
    Is this expected behaviour? I have had a looked at the OSS and Internet Search and there is no reference to this behaviour.
    Many thanks for your help in advanced.

    Hi Jurgen,
    Thanks for moving my post to the correct space.
    Our Auth team is very confident that this is not a user auth issue. This could possibly be true because the idoc data resides on the following tables when in the database (before archive) - EDIDC, EDID4 & EDIDS. The idoc could then be viewed via transaction WE02 or the Data Browser (SE16). There is no EDIDD table in our ERP system so obviously no authorization object to assign to.
    Once the idoc is archived, the data is removed from the ERP tables and moved to our archive database/server for storage. So when trying to view the archived record, the system does not access the ERP tables but rather the archive directory (that it's mapped to in settings). I assume the SARA transaction merely displays the data in the same segments/grouping with these table names (mentioned above in my first post) but instead of EDID4 it displays EDIDD.
    According to the error longtext, "The check performed when data is read from the archive is the same as that of the Data Browser (transaction SE16)". So I was not involved with setting up our archiving procedure but could it be that table EDID4 was incorrectly mapped to table EDIDD in archives?
    Regards,
    Fawaaz

  • Steps for ale idoc creation?

    Hi,
    I want the complete process of ale idoc generation.
    my maild id is [email protected]
    Thank You.
    From:
    Mohammed Moid Ahmed

    Hi
    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
    Outbound:
    Step 1.  Application document is created when transaction is saved.
             2.  Message control is invoked.
             3.  Messages are processed by system.
             4.  Messages are Edited (if desired).
             5.  Output (ALE /  EDI) is checked
             6.  Validate against Message control record from Partner Profile
             7.  Application Document is saved.
             8.  Entry NAST table is created for every selected output program
                  along with Medium & Timing.
             9.  Check for Process Immediately .
                     If (yes)
                       Determine Processing Program from TNAPR Table.
                     ELSE
                       Execute RSNASTED Program.
           10.  Read Partner Profile to determine Process Code.
           11.  Process Code points to the Function Module & Invoked.
           12.  IDoc is generated. 
           13.  Check for ALE Request.
                        if (Yes)
                            Perform Filters, Conversions, Version Changes etc.
                        Else.
                            IDoc is stored in DATABASE.
    INBOUND:
    Step 1.  EDI Subsystem creates an IDoc file from EDI Messages
            2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
             3.  Data in Control Record is validate against the Partner                       Profile.
            4. IDoc is generated in Database and syntax check is                      carried out.
            5. IDoc file is deleted once file read.
            6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow. 
                       7.  Check for Process Immediately.
                   If NO
                     Execute RBDAPP01 Program
                   Else
                      Read Process Code from Partner Profile        
                           Process Code Points to  Function Module
                     Application Document Posted.     
    further help:
    check url
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/ale/configuration.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapdevelopment.co.uk/training
    And also u can get lots of inof from the below link.
    http://www.sapgenie.com/ale/why_ale.htm
    Reward points if useful
    Regards
    Anji

  • Store archiving IDoc's to an HTTp content server

    Hi Guru's,
       I want to store the archived IDoc's to an HTTP content server. 
    i have created an content server on OAC2 and i dont know how to link the archived IDocs to an HTTp content server.
    I searched many forums, but i cant get the exact solution for this.
    Could anyone help me on this..  pls...
    Thanks in advance,
    murugan..

    Hello,
    I will take a final call on this - As i understand all the configuration is correct but not updating in link tables.
    I also understand system Id is ok as PO and IDoC are working.
    In Content repository creation for PO & IDoC you will be taking document area as Data Archiving but for Printlist content repo you have to select ArchiveLink.
    If you have done above then check connectivity and send the certificate
    In your Archive server (IXOS, EASY, DOCUMENTUM or so on ) Check same content repository is properly configured.. if possible refresh it. Check for certification from SAP.
    You are facing connectivity issue so cross check carefull all archive server level.
    Lastly check oss note
    Let us hope for the best.
    -Thanks,
    Ajay.

  • Steps to configure idoc adapters

    hi All can anyone tell me
    what the configuration steps need for idoc adapter (sender).
    thank you
    swari.

    Hi,
    See Wiki :
    " SAP R3 (Idocs) To XI -- Steps Summarized"
    Link:
    [https://wiki.sdn.sap.com/wiki/display/XI/SAPR3(Idocs)ToXI--Steps+Summarized]
    And...
    File To IDOC
    https://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
    Troubleshooting File-to-IDOC Scenario in XI.
    Troubleshooting  File-to-IDOC Scenario in XI.
    Edited by: Pedro Baroni on Nov 7, 2008 6:14 PM

  • Archiving IDOC

    Hi all,
    During Archiving IDOC , WRITE program displays number of archived Data records(EDID4) , Control records (EDIDC) , and Status records(EDIDS) for each archived file in spool.
    Can anyone tell me the names of tables from where these values i.e number of archived documents per archived file for that particular session, can be obtained.

    Hi Deepti,
    Statistics information for every Archiving session is stored in table ADMI_STATS and ADMI_FILES.
    ADMI_STATS will give you the no of objects archived in a particular session. Information on no of objects per archive file can be found in table ADMI_FILES.
    Hope this helps
    Cheers!
    Samanjay

  • Get Archived IDocs based on IDoc creation date

    Save Our Environment. Save Yourself.
    Hi Experts!!!
    We need to get the archived idocs based on the idoc creation date. If I give some date, then I should get all the idocs that are archived in that period. How can this be possible?
    One more doubt is - I checked the logical path in FILE for archived idocs. But when I go to that in AL11, I can not see any data in that. Where can I find the details of all the archived idocs?
    I serached in SCN for the same but in vain.
    Please help me out. Thanks.
    - I'm not an environmentalist.  I'm an Earth warrior.

    Please find the code to read archeived idocs
    FORM read_datarecord.
      STATICS ls_open TYPE boolean VALUE false.
      DATA: ld_tabix TYPE sytabix,
            lt_edidc TYPE STANDARD TABLE OF edidc,
            ld_edidc TYPE edidc.
      MOVE syst-tabix TO ld_tabix.          
      IF int_edidc-mandt IS NOT INITIAL.
      ELSE.
        IF gd_use_as IS INITIAL.
          IF ls_open = false.
            CALL FUNCTION 'ARCHIVE_OPEN_FOR_READ'
              EXPORTING
                object         = 'IDOC'
              IMPORTING
                archive_handle = gd_archive_handle
              TABLES
                archive_files  = gt_arch_sel.
            MOVE true TO ls_open.
          ENDIF.
          CLEAR ld_edidc.
          WHILE ld_edidc-docnum <> int_edidc-docnum.
            CALL FUNCTION 'ARCHIVE_GET_NEXT_OBJECT'
              EXPORTING
                archive_handle = gd_archive_handle
              EXCEPTIONS
                end_of_file    = 1.
            IF syst-subrc IS INITIAL.
              REFRESH lt_edidc.
              CALL FUNCTION 'IDOC_ARCHIVE_GET_TABLE'
                EXPORTING
                  archive_handle   = gd_archive_handle
                  record_structure = 'EDIDC'
                TABLES
                  t_data           = lt_edidc.
              READ TABLE lt_edidc INTO ld_edidc INDEX 1.
              IF ld_edidc-docnum = int_edidc-docnum.
                CALL FUNCTION 'IDOC_ARCHIVE_GET_TABLE'
                  EXPORTING
                    archive_handle   = gd_archive_handle
                    record_structure = 'EDIDD'
                  TABLES
                    t_data           = int_edidd.
              ENDIF.
            ELSE.
              EXIT.
            ENDIF.
          ENDWHILE.
        ELSE.
          CALL FUNCTION 'EDI_IDOC_GET_FROM_ARCHIVE'
            EXPORTING
              docnum                       = int_edidc-docnum
            TABLES
              int_edidd                    = int_edidd
            EXCEPTIONS
              idoc_not_in_infostructures   = 1
              idoc_read_error_from_archive = 2
              archive_close_error          = 3
              others                       = 4.
          IF sy-subrc <> 0.
          ENDIF.
        ENDIF.
      ENDIF.
      IF ls_open = true AND ld_tabix = anz_int_edidc.
        CALL FUNCTION 'ARCHIVE_CLOSE_FILE'
          EXPORTING
            archive_handle = gd_archive_handle.
      ENDIF.
    ENDFORM.                               " READ_DATARECORD
    PS if you don't have auth to SARA then get auth . you need to talk to your business owner or talk to basis to get auth

  • Archiving idocs using RSEXARCB

    HI
    I am using the program RSEXARCB to archive IDOCS.I want to know is there a way whether I can check if all the IDOCs have been archived or not? I don’t have the IDOC numbers. This program just archives the idocs which fall in a certain time period(say last 6 months). The IDOC numbers are not provided explicitly. What are the statuses for archived IDOCS?
    Please help. Its very urgent.
    Regards,
    Ram

    Hello,
      You can use table content display (SE16) of IDOC status table EDIDS based on creation date CREDAT.
    Thanks,
    Venu

  • Archive IDOC's

    I would like to archive IDOC's object. I've executed the write phase, but after that some physical files have been deleted. Then when I execute the delete phase I received the message :
    Archive file 000028-003IDOC is being verified
    Data stream in archive file 000028-003IDOC is shorter than expected
    Error during verification when accessing archive file 000028-003IDOC
    1 archive file(s) were not successfully verified
    Job cancelled after system exception ERROR_MESSAGE
    How can I do to avoid this error ?
    Thank's in advanced

    Hi,
    You could try this.
    If the arhive file was stored in a storage server, then go to SARA-->Customizing -> Archiving Object-Specific Customizing-> Technical Settings. Here in the section "Place file in Storage  System" check the checkbox against Delete program reads from Storage System . Now try to run the delete program. It should work..
    ~Asish

  • Archiving IDOCs...

    Hi
    As per my requirement, I need to archive unwanted IDOC in my system. Could you please put down the way for this?
    Thanks in Advance.
    Siva Kumar

    sometimes i wish people would care to describe the whole process ...
    first think what IDOCs you want to archive. you can customize this using tx. WE40 where you decide per status whether an IDOC is archivable or not.
    second go to your basis guys and ask them how they want the thing set up. have a look at the technical settings section in transaction SARA, object IDOC to see what i mean. you basis guys have to configure logical/physical path and filenames using transaction FILE.
    third check whether your company is using an external archiving system where archive files are to be stored (like IXOS, EASY, SAPERION ...). if so, you might want to store your archived IDOCs on the same system. you would have to set up the content management for your IDOCs using tx. OAM1 (and following) -> this is a bit difficult -> refer to help.sap.com on the details.

  • View Archived Idocs

    HI Gurus,
    Can you help me with reading archived IDocs by IDoc number. I tried SARA but that didnt help me.
    Please help.

    Hi Vinod,
    You can use transaction WE09 to read an archived IDOC.  After entering the IDOC number, click on the Data Source button and select the checkbox by Archive.
    Hope this helps.
    Best Regards,
    Karin Tillotson

  • Cannot display archived idoc data records in SARA

    Hello,
    In our ERP system, we regularly archive idocs older than 6 months. To view these archived idocs I use transaction SARA (with archive object IDOC and infostructure SAP_IDOC_001) to search for the relevant idoc that has been archived. Once the idoc is displayed, I drill down further by clicking the magnify glass button which then displays the idoc levels:
    EDIDC               Control record (IDoc)
    EDIDD               Data record (IDoc)
    EDIDS               Status Record (IDoc)
    SRL_ARLNK      SREL: Archive Structure for Links
    When I try to view the Data Records, I get a message saying "You are not authorized to display table EDIDD". According to our Authorizations department, this is not an Auth issue but rather config setup or program issue.
    Why can't I view the archived idoc data records? Is there another way to view archived idoc data?
    Regards,
    Fawaaz

    Hi Jurgen,
    Thanks for moving my post to the correct space.
    Our Auth team is very confident that this is not a user auth issue. This could possibly be true because the idoc data resides on the following tables when in the database (before archive) - EDIDC, EDID4 & EDIDS. The idoc could then be viewed via transaction WE02 or the Data Browser (SE16). There is no EDIDD table in our ERP system so obviously no authorization object to assign to.
    Once the idoc is archived, the data is removed from the ERP tables and moved to our archive database/server for storage. So when trying to view the archived record, the system does not access the ERP tables but rather the archive directory (that it's mapped to in settings). I assume the SARA transaction merely displays the data in the same segments/grouping with these table names (mentioned above in my first post) but instead of EDID4 it displays EDIDD.
    According to the error longtext, "The check performed when data is read from the archive is the same as that of the Data Browser (transaction SE16)". So I was not involved with setting up our archiving procedure but could it be that table EDID4 was incorrectly mapped to table EDIDD in archives?
    Regards,
    Fawaaz

Maybe you are looking for

  • HP officejet 6100 eprinter not recognizing networks

    I have tried resetting and factory reset on the printer, plugging and unplugging in all possible combinations, updating firmware and .  The printer will work on the MacBook when connected to the Airport Express.  The Ipad Air will not see it at all.

  • File to IDOC scenario: Create customer master and then return customer no

    Hi all. I have a scenario to pass xml file to sap XI to generate IDOC to create customer master in SAP. My problem is that I need to return customer no. created in SAP from IDOC. Is there any solution to do this? Someone told me that BPM could be use

  • Problem with special characteres

    Hi. I have a problem with java. I�m making an application that works with special characters and displays correctly on my local machine, as I use escape characters such as ì for �. The problem is when I deploy the application on a unix machine. All o

  • Iwl3945 and dhcpcd workaround - bash script

    I got tired of typing every command by hand all the time, so i made this simple bash script to do this for me... edit the script with your preferences and settings and run it as root. The script sets a static ip, and all the shizzle thats needed to h

  • "not the right kind of document" -- eps & ps

    This seems to be quite an issue with photoshop, as I see. The weird thing is that Photoshop CS2 could open EPS and PS files, which was handy for generating hi-res tiff from InDesign layouts. Now suddenly it cannot open neither postscript file - and r