Error in File to Custom IDoc

Hi All,
I am getting following error while doing File to Custom IDoc Scenario
No authorization to send IDocs with message type Z
Can any one tell how to resolve this error?
Regards,
Sai

Hi Krishna,
The RFC destination that you have put in IDoc communication channel must be present in your SAP XI system, transaction SM59 also.
Please check if the user id/Password that you have given has all the authorization.
Also check the User ID and passwrord in SM59 in R3 and see if a Remote Login is possible.
There is also some configuration by which the clients are allowed / blocked from receiving Idocs from XI. Basis guys can do it for you. Please approach your basis consultant. Hopefully that helps..
Regards,
Abhy
Message was edited by: Abhy Thomas

Similar Messages

  • File to custom IDOC  or File to abap proxy

    Hi there,
    I would like to know best approach for the following scenario.
    1) i have file coming from legacy system
    2) On target side SAP , I have BAPI's available  (Create, Save, Commit )(No standard IDOC available)
    I can create Custom IDOC and call those BAPI's in Custom Function Module
    or
    I can use ABAP proxy and call BAPI's
    What is the best way of doing this? and Is there any other way?
    Thanks
    Kumar

    hi,
    Abap Proxy is better than RFC in terms of performance.
    proxy is that it always by passes the Adapter Engine and will directly interact with the application system and Integration engine - so it will and should give us a better performance.
    In your case , if there want to crate idoc from scratch level then we go for proxy  and proxy support large volume of data (more than 5 mb).
    One more  reason is RFC , the data is converted between RFC and XML in RFC adapter. In proxy XI communicates with the R/3 in native XI language (SOAP XML).

  • File to multiple IDOCs error

    Dear All,
            I am trying to create customer master using FILE-To-Multiple IDocs.Idoc generated with 2 errors.
    1.First one is status 51...Specify the Account Group.
    2.Second one is it's generating only single idoc(not multiple).
    I have mapped Account Group source field to KTOKD(Idoc).is this mapping problem?I have given IDOC occurence unbounded but not generating multiple idocs.below is my message mapping structure.
    mt_customer                                                   Debmas01
      customer  (1...1)                                
        customer_master(1..unbounded)----
    >IDOC (1..unbounded)
    below is my input xml file with data.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:mt_customer xmlns:ns0="urn://fenestacustmast">
       <Customer>
          <Customer_master>
             <AccountGroup>0004</AccountGroup>
             <CustomerNumber/>
             <CompanyCode>1000</CompanyCode>
             <SalesOrg>DBPM</SalesOrg>
             <DistributionChannel>PS</DistributionChannel>
             <Division>WD</Division>
             <Title>Mr</Title>
             <Name>Preethi</Name>
             <SearchTerm>Mat</SearchTerm>
             <SearchTerm2>V6CUSTNO</SearchTerm2>
             <StreetNumber>Street 6</StreetNumber>
             <City>Bangalore</City>
             <Country>IN</Country>
             <Region>KAR</Region>
             <TransporationZone>ASCHTS01</TransporationZone>
             <Fax>251662546</Fax>
             <Telephone>9658965236</Telephone>
             <VATRegNo>ABCG1254</VATRegNo>
             <LegalStatus>01</LegalStatus>
             <ReconAccount>36023901</ReconAccount>
             <SortKey>001</SortKey>
             <TermsOfPayment>S028</TermsOfPayment>
             <ToleranceGroup>1000</ToleranceGroup>
             <PaymentHistRecord>TRUE</PaymentHistRecord>
             <SalesDistrict>A1KAKA</SalesDistrict>
             <SalesOffice>BPBL</SalesOffice>
             <SalesGroup>SEN</SalesGroup>
             <Currency>INR</Currency>
             <CustPricingProc>1</CustPricingProc>
             <CustStatsGroup>1</CustStatsGroup>
             <DeliveringPriority>01</DeliveringPriority>
             <ShippingConditions>01</ShippingConditions>
             <Plant>DBBG</Plant>
             <AccountAssGroup>01</AccountAssGroup>
             <TaxClassification>1</TaxClassification>
             <InvoicingDate>IN</InvoicingDate>
             <InvoicingListDate>IN</InvoicingListDate>
             <IncoTerms>FCA</IncoTerms>
             <IncotermsPart2>Bangalore</IncotermsPart2>
             <CreditControlArea>FENE</CreditControlArea>
          </Customer_master>
       </Customer>
    </ns0:mt_customer>
    I did very simple mapping one to one without any functions.All are string types.I couldn't find what is the error?any help would be appreciated.
    Thanks in advance.
    Vinay

    Hi,
        I would like to know whether you have mapped your customer_master(1..unbounded) node to IDOC(1..unbounded) node???Please check it once.Depending on that only the multiple IDOCs will be generated. I think it is mapping problem only. Have you changed the occurrence of IDOC to unbounded by exporting & then reimporting it to external definitions???? I've already done it & i got multiple IDOcs generated. Please check it and let me know the response so that I can help.
    Please follow th below links
    http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c
    /people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
    Thanks & Regards
    Priyanka Anagani

  • Error with Custom Idoc

    Hi All,
    I have created a custom idoc for creation of master data in the system. This custom idoc is using a custom function module to process the idocs. In the FM i have used Call transaction method to upload the master data in the sap system. Everything seems to be working fine.
    But the problem is that whenever any external system creates more than one idoc, first idoc is posted successfully while others fail with an error message "No status record was passed to ALE by the application.". Please let us know how we can resolve it.
    Correct Answers will be rewarded.
    Regards,
    Sridhar.

    Hello
    Refer to following thread:
    The specified item was not found.
    Thanks
    Amol Lohade

  • Error Handling in File to Multiple IDOC Scenario?

    Hello Experts,
    My scenario is file with Multiple records and I want to send it to SAP system.If there will be 10 Records in my file I need to create 10 IDOC in Target system.
    I can use below of the two options.
    1) File to Multiple Idoc (1.N Mapping)
    2) Using BPM
    3)Directly place the file in SAP application server and process it via ABAP Program.
    However I am not clear in which option error handling will be more effective.Please suggest.
    Basically I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
    Also I will be doing this scenrio for transaction data with huge size (1 Million Records).Which approach will be more effective in this case.
    Thanks,
    Pushkar

    Hi Patel,
    I want to handle If out of 10 records 9 are correct and 1 record is not correct then I should be able to report within PI without affecting 9 correct records.Is it possible 9 records will be sent to SAP system and PI will only show error for 1 incorrect record.
    when working on graphical mapping, the target structure is created when there are no errors in all records of source structure.
    suppose if we have validation error in 9th and 10th record, then we can not process the first eight records and inturn we can not store the two error records in XI for further.
    i suggest you the third option, you can directly place the file in SAP application server and process it via ABAP Program.
    this is far better because you can do more customizations as you have to deal with millions of records.
    Regards,
    Pradeep A.

  • ATTRIBUTE_IDOC_RUNTIME error in File-IDOC Scenario

    Hi,
    I got this error in FIle-IDOC scenario.
    ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
      <SAP:P1>Transaction IDX1: Port SAPMMX, client , RFC destination contain errors
    There are many threads on same issue. Almost in all threads, the suggestion given was, we need to check the Channel Definition(Port should be SAP<SYSID> and not SAP<SYSID>_<CLIENT>)
    I have given the proper values for RFC desitnation and port. Even then, I m getting this error.
    Is there any other suggestions?

    Hi aarthi,
    I suggest u chk all d settings dat u hav done..
    Steps for ALE settings:-
    Steps for XI
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the R3 system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto IDX1.
         Create a new port.
         Give the port name.
         Give the client number for the R3 system.
         Select the created Rfc Destination.
    Step 3)
         Goto IDX2
         Create a new Meta data.
         Give the Idoc type.
         Select the created port.
    Steps for R3.
    Step 1)
         Goto SM59.
         Create new RFC destination of type 3(Abap connection).
         Give a suitable name and description.
         Give the Ip address of the XI system.
         Give the system number.
         Give the gateway host name and gateway service (3300 + system number).
         Go to the logon security tab.
         Give the lang, client, username and password.
         Test connection and remote logon.
    Step 2)
         Goto WE21.
         Create a port under transactional RFC.(R3->XI)
         Designate the RFC destination created in prev step.
    Step 3)
         Goto SALE.
         Basic settings->Logical Systems->Define logical system.
         Create two logical systems(one for XI and the other for R3)
         Basic settings->Logical Systems->Assign logical system.
         Assign the R3 logical system to respective client.
    Step 4)
         Goto WE20.
         Partner type LS.
         Create two partner profile(one for XI the other for R3).
         Give the outbound or inbound message type based on the direction.
    Step 5)
         Not mandatory.
         Goto BD64.
         Click on Create model view.
         Add message type.
    Step 6)
         Goto WE19
         Give the basic type and execute.
         fill in the required fields.
         Goto IDOC->edit control records.
         Give the following values.(Receiver port,partner no.,part type and sender Partner no. and type)
         Click outbound processing.
    Step 7)
         Go to SM58
         if there are any messages then there is some error in execution.
         Goto WE02.
         Check the status of the IDOC.
         Goto WE47.
         TO decode the status code.
    BD87 to check the status of IDOC.
    In case if not authorized then go to the target system and check in SU53, see for the missing object
    and assign it to the user.
    SAP r3
    sm59(status check)(no message)
    WE02(status check)
    WE05(status check)
    BD87(status check)
    Xi
    IDx5(Idoc check)
    SU53(authorization check)
    reward points if helpful...
    MenoN

  • File to Multiple Idocs, Error: Tag MESSAGE1 found instead of tag IDOC BEGIN

    Hi,
    I have configured my file to multiple idocs scenario using the following blog -
    /people/claus.wallacher/blog/2006/06/29/message-splitting-using-the-graphical-mapping-tool
    Now when i try to execute this scenario it is scenario it is giving me the following error at "Call Adapter" Stage in runtime-
    "Tag MESSAGE1 found instead of tag IDOC BEGIN="
    My message looks like this at "Request Message Mapping" Stage in runtime -
      <?xml version="1.0" encoding="UTF-8" ?>
    - <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
    - <ns0:Message1>
    - <ZDR009>
    - <IDOC BEGIN="1">
    - <Z100901 SEGMENT="1">
      <RUNDATE>20080220</RUNDATE>
      <RUNTIME>0037</RUNTIME>
      <CONSTANT1>PYRLINCST</CONSTANT1>
      <CONSTANT2>CSC</CONSTANT2>
    - <Z100902 SEGMENT="1">
      <RECTYP>2</RECTYP>
      <SSN>641381239</SSN>
    Kindly assist me in solving this error, Thanks in Advance!!
    Regards.
    Sudheer

    Hi Sudheer,
    Just the check the message mapping. Check the parant node mappings to create two different messages.
    It seems that the mapping done on IDOC Node to create the IDOCs is getting failed.
    Copy the content from inbound payload and test it in message mapping.
    Remember, when you load the test data into your test tab you will get the error of structure mismatch coz in your mapping you have additional message.
    Do the change with original data as shown below befor testing.
    <?xml version="1.0" encoding="UTF-8" ?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>
    Original message will be here.
    </ns0:Message1>
    </ns0:Messages>
    Regards,
    Sarvesh

  • Custom IDOC to create XML file

    Hi,
    We are on 4.7 release.
    A custom outbound IDOC type is developed to creates a text file at the location entered in FILE type port.
    Now we want to create XML file intead of text file. Is it possible by simply changing the port to XML FILE port? Or do we need to do any modifications inside the FMs for the IDOC?
    Similarly for Inbound scenario (using custom IDOC type), do we need any chagnes in FMs to handle IDOCS in XML file format?
    Thanks.

    You can even do that conversion of idoc to xml by simple method
    create a xml port and use the standard fm there
    and it wud handle that.
    u may like to refer this blog...
    Collecting IDocs without using BPM
    Thanks
    Kiran
    Edited by: kiran dasari on Dec 12, 2008 10:38 AM

  • Error in Inbound Customer IDOC (WE19)

    Hi All
    I am creating Inbound Customer IDOC
    Message Type : DEBMAS
    & FM : IDOC_INPUT_DEBITOR.
    But getting error(51) : "No batch input data for screen SAPMF02D 0340".
    According to previous threads, I have seen this screen for Mandatory fields but I didnt found any.
    Could anyone tell me what mandatory fields to enter in DEBMAS or  the Solution for this Error.
    Regards.

    Hi Nikhil I am getting this error which you got it before but this time I am getting it in LSMW when creating customer master screen."No batch input data for screen SAPMF02D 0340"
    what am i supposed to check?
    Can u plz send me ur mail ID.

  • Error While Creating Custom IDOC Segment using WE31

    Could anyone please help me resolve this issue.
    I am getting following error when trying to create a custom IDOC segment type using WE31.
    "Name range violation: Name Z1WOHDR not permitted in SAP system"
    Segment type trying to create: Z1WOHDR
    Regards
    Venu

    Try changing the name , But i am not getting any such error with the name you are using.
    Just Try with some onther name

  • Im getting the following Installer was unable to access a critical file/directory. Please try installing again.(Error code: 43) Contact Customer Support

    I'M GETTING THE FOLLOWING ERROR
    Installer was unable to access a critical file/directory. Please try installing again.(Error code: 43) Contact Customer Support

    Error downloading Creative Cloud applications

  • Hi...  I just attempted to update CC.  Download itself appears to have happened, but when then I got this message...  Installer was unable to access a critical file/directory. Please try installing again.(Error code: 43) Contact Customer Support .... can

    Installer was unable to access a critical file/directory. Please try installing again.(Error code: 43) Contact Customer Support
    Any ideas?

    Hi  Serpent,
    Try the following Steps:
    open activity monitor and close all Adobe related applications
    navigate to: /Library/Application support/Adobe
    In that directory you will see a folder named OOBE - Rename that folder to OOBEold
    Navigate to: MAC HD /Application/Utilities directory
    In there you will see a folder called "Adobe Application Manager" - delete it
    Download the Adobe Cleaner Tool from here: http://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems/_jcr_conte nt/main-pars/accordion_container_1/accordion-par/accordion-item-1/accordion-item-par/proc e dure/proc_par/step_3/step_par/download/file.res/AdobeCreativeCloudCleanerTool.zip
    Open the Cleaner Tool and choose to clean "Creative Cloud" only.
    Download and install Creative Cloud again - https://ccmdls.adobe.com/AdobeProducts/KCCC/1/osx10/CreativeCloudInstaller.dmg
    Regards,
    Rave

  • Error when trying to extend custom idoc

    Hi ladies and gentlemen,
    I am experiencing problems when I try to extand a custom idoc segment.
    I created a custom idoc (ZBEVINBDEL) with 3 segments, generated it and have tested it successfully.  Now the users have come back and requested additional fields.  When I tried to modify the custom segment (after cancelling the segment and idoc status' from released status, I got the message 'Segment type Zxxxxx.. cannot be changed'  (this is because the idoc segment type has been flagged as generated).
    So I thought I'll create an extension to the corresponding segment.  I've created the extension segment in WE31, but when I try to create the extension (ZBEVINBDELX02), and try to create as new to the linked type ZBEVINBDEL, I get another error message 'Action is not possible for generated idoctypes'.
    Has anybody experienced this problem before, and could you give me an explanation on how to get around these problems, either for changing the segment or extending one.  If the answer lies within BDBG, please explain in detail.
    Cheers,
    Steve

    Reuben,
    In the end, I didn't need to touch the extension.  I was able to achieve my goal by adding the new fields in  my custom structure in SE11, and the new fields came into the idoc automatically.  Then I just had to add code to handle the new fields in my Function module.
    Good Luck,
    Steve

  • Error in creation of  PurOrd IDoc

    Hi All,
    I have set up the output type for PO and created patner profiles and also add the message types ORDER and ORDCHG  but  when I save the PO and check the messages, I get an error: " No recipient found for message type ORDERS in the ALE Model ".
    What could be the possible problem?
    Highly appreciate any kind of help.
    Thanks in advance,
    Shweta
    PS: <b><REMOVED BY MODERATOR></b>
    Message was edited by:
            Alvaro Tejada Galindo

    Hi
    Check the Partner Profile in WE20 correctly
    also see the steps for it as per 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.
    Regards
    Anji

  • Development of custom IDOC's

    Hi All,
    Can we go for approach of developing custom IDOC's? where in our scenarios are getting files from thrid party and updating data in file  into ECC.
    Approach towards Custom IDOC's is for error monitoring and recprocessing.
    Would request your inputs and suggesions in this regard.
    Is that good approach for going to custom idocs? if not why?
    Thanks,
    chandra.

    Hi,
    SAP R/3 systems send out data through IDoc (Intermediate Document), which in internally has segments and fields containing the data. But sometimes, these fields are not sufficient for a specific end-to-end business scenario as far as data transfer is concerned. So in such scenario, either few fields are to be added or subtracted, or completely new structure- IDoc needs to be created.
    At times because of the business scenario we do have to create Custom idocs .
    Regards,
    Bhanu

Maybe you are looking for

  • How to execute custom code only when a specific node is selected in infoset

    Hi, We have written a piece of custom code under a node (P1045). Not all users will have access to this Infotype as it is related to Appraisals. So, when users (w/no access to 1045) try to run a Query for other info types data, they are getting error

  • How do I locate multiple files at one time?

    I've moved a few songs around in my computer's files, and each time I'd go back to locate the files, it asked me if I would like to locate the original files for other songs. Today I tried to do the exact same thing, but it doesn't give me the same o

  • Revoke in Oracle 8i

    Hi , Can anyone tell the following query in 8i is correct ? revoke execute on <procedure name> from public; if it is not please tell me how to revoke a execute permission on a procedure from public in oracle 8i?

  • TS1424 Can't get Genius Suggestions to work in new version of ITunes

    Genius Suggestions used to come up automatically in previous versions.  Miss that a lot!!  Help menu says select Genius Playlist (where is that), select song & choose Genius Suggestions from action menu (where is that) and then click create genius pl

  • Can i run applications on ipad from icloud?

    I have a piece of interaction software (project management training) and I wonder if anybody knows if I can store this application on iCloud and run it from the iPad?