Import SAP IDOC in B1

Is it possible to import SAP IDOCS (e.g. ORDERS05) in B1?  Is extra software needed?

Hi Johan,
Electronic File Format: the Tools is provided, and used to do most of the file transformations and imports.
It is used for all bank statements (import and export), is used to generate specific reports (Intrastat) and by SAP for specific legal requirements (i.e.the one asked by the French Legals to provide an electronic export on a specific format during controls).
Not the easiest thing to master, but a standard tool for file transformation from Inside the client (B1if will run on the server only, as you know).
sthat you are not restricted regarding the source format (you can even use a .rpt file as a source ).
If you search Inside the SCN, you'll find posts explaining how to use it.
Regards,
Eric

Similar Messages

  • SAP IDOC import from XI

    I'm trying to import IDOC from SAP, but i'm getting "login failed (authorization insufficient)" error. But i'm able to login into SAP GUI using the same login info. What authorizations/roles i should have on SAP and XI system for IDOC transfers?
    Thanks,
    Anika

    Hi Anika,
    These roles shud be assigned to the user which you use to login to the SAP R/3 system as from this R/3 system you are trying to import IDoc into SAP-XI after getting connected.
    You may be able to login using the id w/o these roles thru SAP GUI but its not necessary that you have authorization to import the IDoc. Hence you need to add these roles to the user profile.
    Cheers
    JK

  • How we can import an IDOC structure from one SAP system to another w/o ALE

    Hi Gurus,
    How we can import an IDOC structure from one SAP system to another? we're not able to use ALE tech, these two sap systems are isolated.
    Any response will be awarded!
    Thanks a lot.
    Samson

    hi,
    1.One is by change pointer concept i.e by executing the RBDMIDOC.We can generate the idoc and automatically to the inbound System.
    2.By executable program also like bd10 and bd11.
    Regards,
    SHIVA(reward if helpful).

  • How we can import an IDOC structure from one SAP system to another

    Hi Gurus,
    How we can import an IDOC structure from one SAP system to another? If we're using ALE, how can we do that? Please can someone give me the process and necessary t codes.
    Any response will be awarded!
    Thanks a lot.
    Samson

    hi!
    Define the logical system names in both the systems.
    Logical system names :SAP001
    SAP002
    SAP001 FOR 001 CLIENT
    SAP002 FOR 002 CLIENT
    These two logical system definitions should be present in both the systems.
    Assign the logical systems to the client. (in both the systems)
    Assign SAP001 to 001 CLIENT
    Assign SAP002 to 002 CLIENT
    you can See these in transaction SALE.
    After this define the rfc DESTINATION IN sm59. (in both the systems)
    In 001 client create the RFC destination name SAP002
    In the tab log on security, give the user name and password and client of the 002 client and save it.
    Similarly do the reverse in the 002 Client.
    In 001 client create the port.(Transaction WE21)
    Specify the RFC destination name as SAP002.
    Now you can define the ports, (both the systems)
    Create the partner profile for partner(ie gve logical system name of partner) , so give as SAP002.
    partner profile in both the systems.
    Now create the distribution model in BD64 and goto edit>model view>distribute.
    The same model view will be visible n distributed to the partner system also..which in this case is sap002.
    U may trigger the idoc from we19 and chk its status in we05.
    Please let me know if you need further info on this.

  • Problem with import of IDOC fromSAP 3.1i to PI 7.0

    Hi ,
    I have an IDOC as ZXYZ.ORDERS01 in SAP R/3 3.1i System, I am unable to import the IDOC in PI7.0
    Let me know the process to import that idoc.
    ( I am Doing IDOC to File and file to IDOC Scenario )
    Regards,
    Edited by: TomShey on Sep 22, 2010 6:27 PM

    Hi,
    We also had same problem of unable to import IDOC structures automatically from SAP 3.1I to XI/PI, as the support of this feature as mentioned by SAP starts from version >= 4.0.
    Please find the prerequisite as mentioned in help.sap.com
    Prerequisites
    The SAP system from which you want to import the RFCs or IDocs must contain function modules for calling metadata. You can import RFCs and IDocs from SAP Release 4.0 and higher. The table below gives an overview of the required support packages:
    (http://help.sap.com/saphelp_nw04/helpdata/en/14/80243b4a66ae0ce10000000a11402f/frameset.htm)
    So as per my experience, I could identify three options after indepth investigation.
    1. Recreate the IDOC structures in another SAP system which is of latest version >= 4.0 may be IDES, and then import the structure in IR for further developments. This is the option we are using for our developments now.
    2. Get WSDL of the IDOC structure by creating manually the structure using XML Enterprise edition using the complete syntax or xpath and import as external definitions and use it in mapping.
    3. Re-create the IDOC structure in XI system itself and try to use it.
    Let me know if this helped you.
    Regards,
    Bindu

  • How to import the IDOC into Seeburger BIC mapping designer

    Hi All,
    Can u please tell me how to import the IDOC into Seeburger BIC mapping desginer.
    I have scenario My scenario is SAP GTS 7.0.....>Seeburger BIS.....>Atlas customs system for Germany
    Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send
    to Atlas systeam.
    Regards,
    Ramesh.

    Hi Ramesh
    BIC is a tool from Seeburger to transmit the XML data to EDI and EDI to XML.
    Seeburger mapping programs for transferring the XML data to EDI data and EDI data to XML data, but not for the structure changing, in the IR your mapping program is same.
    Receiver side you need AS2 Adapter for converting data to EDI target structure. we have many EDI versions are available, for converting the EDI to XML or vice versa AS2 gives some default mapping programs, xml to EDI or EDI to XML convertion done through this mapping programs.
    Seeburger AS adapter provider provides some mapping programs(for example EDI4010 version or other), if you are using the same EDI version(4010) then you can use that mapping programs, if the version is different then we can manually generate the Seeburger X2E and E2X mappings for the corresponding version and signal(850 or 810 or ..), for this seeburger provides the mapping designer tool (BIC), there we can develope the X2E and E2X mapping programs and configure this in the Seeburger work bench.
    Regards
    Ramesh

  • SAP(IDOC) ---PI---webservice

    Hi
    Is it possible or not to send IDOC to webservice via PI ?
    I need a necessary things and steps to setup in PI (BPM etc) to send the IDOC from SAP to Webservice via PI
    thanks
    manian

    Hi,
    Yes You can send the Idoc to Webservice Very Well through XI
    If you want Response back to SAP means we need to configure BPM else no need of any BPM
    ALE Settings
    Steps
    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.
    In SLD u2013 System Landscape Directory
    TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
    Ts for Third Party (Logical system):-
    BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
    BS for Third Party (Logical system):-Enter the XI logical system name.
    In Transaction SALE
    Define and Assign the logical system name.
    IR
    1)Import the Idoc in IR for Sender Side Structure and use this Idoc itself as DT MT and MI. No need to create
    2) Import the wsdl file given from the webservice team
    3) create MI for this webservice
    4) create Mappping and interface mapping
    ID
    1)No need to create any Sender CC for Idoc, why because Idoc Sits on ABAP Stack and can directly interact with the IS
    2) Create Receiver SOAP CC
    3) Create Receiver Determination and Interface Det
    4) Create Receiver agreement
    5) no need of Sender agreement
    REgards
    Seshagiri
    Edited by: N V Seshagiri on Aug 12, 2008 7:01 AM

  • File to IDOC Scenario: where to import the idoc structure?

    Dear all,
    I have a short organizational question for you all. I have created a scenario where the MDM server places a file in a FTP directory and XI will take it from there for processing to IDOC towards the SAP system.
    During design time I need to import the IDOC structure as the inbound interface for the SAP system.
    My question in this situation is: do I import the IDOC into the namespace of the MDM (in which I keep the outbound interface and the mappings) server or do I place it in the namespace of the SAP system?
    I ask this because in the latter case the IDOC structure will be the only object in the SAP namespace. If I do not do this, I don't have to create this.
    What is the right thing to do from an organizational point of view?
    Thanks in advance for your input.

    Hi Yomesh and Sudheer,
    thanks for your answers. To conclude this topic I will demonstrate how I have understood this all by giving you a short overview of how I will proceed now. Could you please comment???
    Sender system is a SAP MDM system. For which I will create a SWC called <Company name>_MDM_DEV version 1.0.
    For the receiving SAP Enterprise system I will create an additional SWC called <Company name>_SAP_DEV version 1.0.
    And thus I do not put any objects under SWCs from the original installed product components.
    Then I create a SWC for common objects as IDOCs (to what product does that need to be assigned???)
    Then I will put the interface and message types in the corresponding SWCs and put the mappings in the source SWC as our landscape is not that huge.
    How's that???
    So under which product to create the SWC for common objects is my final question...
    I will provide points to you both.
    Cheers,
    Auke
    Message was edited by:
            A. Schotanus

  • How to import Custom idoc into  IR?

    I have a custom idoc and i need to map it with the receiver format after importing into IR . Please let me know the sequence of steps to import custom idoc into  Integration repository?
    I think I need to first import into IDX2 and then import into repository. Am I correct?

    Hi Prateek,
    thanks for the information .The normal standard idocs we import by searching the idoc eg- for importing matmas we type mat and we search it, since it is a standard idoc it will be available in the list (after selecting the chek box "Import of idoc or rfc interfaces from sap system permitted").
    But my question is how we import custom idoc as they wont be present in the list?

  • Read/write operation on SAP IDOC file

    Hi All,
    We are developing an application, which will be used for registering and processing of travel data for a client.One of itu2019s functionality is to get the data from external system in different format(like CSV, Excel, Fixed Flat file, XML, main frame file, DBF and SAP IDOC) and import it into Oracle databases.
    One of the design considerations for it, is to read these files and convert it into predefined XML format
    and then import these data from XML to oracle database.
    Currently we are analyzing the requirement and trying to find out all the Open Source JAVA API which can convert these different format files to predefined XML format, using some mapping file.
    We have found out Open Source JAVA API for all the file format, except SAP IDOC files.
    Any Java API to read/write the SAP IDOC file, Please advise
    Regards,
    Madhu
    Edited by: Madhu Sudhan on Feb 17, 2009 12:06 PM

    Hi All,
    We are developing an application, which will be used for registering and processing of travel data for a client.One of itu2019s functionality is to get the data from external system in different format(like CSV, Excel, Fixed Flat file, XML, main frame file, DBF and SAP IDOC) and import it into Oracle databases.
    One of the design considerations for it, is to read these files and convert it into predefined XML format
    and then import these data from XML to oracle database.
    Currently we are analyzing the requirement and trying to find out all the Open Source JAVA API which can convert these different format files to predefined XML format, using some mapping file.
    We have found out Open Source JAVA API for all the file format, except SAP IDOC files.
    Any Java API to read/write the SAP IDOC file, Please advise
    Regards,
    Madhu
    Edited by: Madhu Sudhan on Feb 17, 2009 12:06 PM

  • How to import a idoc

    hi all,
    please help me for how to import a idoc into the imported objects in INTEGRATION REPOSITORY  (XI)

    Hi Manoj,
    Just follow this sequence :
    integration repository --> software component double click --> select radio button which says “import of RFC and IDOC interfaces from SAP systems Permitted”. --> provide the connection data for import from SAP System --> then under imported objects, you have IDoc --> right click and say import of sap objects --> then give your server details and import the IDoc you want.
    I hope this makes things clear to you.
    Regards,
    abhy

  • SAP(Idoc) = XI = ThirdPart(WebService)

    Hello friends!
    I have a problem with development of acknowledgement system with SAP(Idoc) <=> XI <=> ThirdPart(WebService)  scenario.
      My case:
    Scenario looks like:
    SAP(Idoc) <=>(Idoc adapter) XI (SOAP adapter)<=> ThirdPart(WebService)
      It must work this way:
    SAP system send IDOC, then XI map it and send it via SOAP-adapter to third part webservice. Then webservice answer to XI with structure сontains "TRUE" or "FALSE",
    and then XI must inform SAP ALE/IDOC system if current information from idoc was successfully added to webservice or not.
    But how can I get it? As far as I understand ALE/IDOC system I have to create ALEAUD by myself, put status of idoc depends on webservice return and send ALEAUD idoc to SAP.
    I'am right?

    Hi,
    You can use BPM for this Idoc--Soap Sync Process
    Design objects:
    Data type & Message Type
    1) Import the IDOC and Later you import the Idoc, doble click on it a export it to your driver, next import it as External Definition for reason becouse if not, you wont be able to create a MI type synch with IDOC and genericResponse structure
    2) Create data type for your Response Type of IDOC
    3) Import the WSDL File For Request and the Response Type
    4) Create the Message types according to the Data types which we created
    Messgae Interface:
    1) Outbound synchronous:
        output message will be ur idoc external definition file
        input message will be ur message type that u have created.
    2) Abstract Outbound Synchronous:
        use the same as in Outbound Synchronous
    3) Inbound Synchronous:
        input message will be ur request message of RFC/WebService
        output message will be ur response message of RFC/Webservice
    4)Abstract Inbound Sunchronous:
        input message will be ur request message of RFC/WebService
        output message will be ur response message of RFC/Webservice
    Mapping
    Request Message Mapping:
    b/w ur idoc external definiton and request message of RFC/WS
    response Message Mapping:
    b/w ur Response message of RFC/WS and ur message type
    Interface Mapping
    Import MI(abstract) of IDOC
    Import MI of WS
    select the mapping for request and response Tab
    BPM
    1) In container window define a variable named IDoc_ABS with category abstract interface and   
        type (select the MI of IDOC alone)
       define a variable named GenericRespnse_abs with category abstract interface and type (select         
       MI of genericResponse alone)
    2) Create a Recieve Step --> in property message select the container you define before of idoc.
    3) Define a Send Step--> mode synchronous
        select MI type abstract and sync (idoc and genericResponse)
        for property request message selects container Idoc_ABS
        for property response message selects container GenericRespnse_abs.
    Save your Changes and thats all for BPM
    *Configuration *
    1) Create scenario
        Assign BS and create comunication channels with QoS (quality of service) type BE
    2) Import your BPM
       Create a Receiver Determination
    -->in the target service select the BPM. Save
    -->In overview windown at foot windowns select MI IDoc_abs only. nothing else
    Create a Receiver Determination
    -->here the system who send data is BPM
    -->in the target service select the BS of receiver system.Save
    -->In overview windown at foot windowns select interface mapping and assing communication channel
    what we do here. the flow is next
    1) Receive data from sender system and send it to BPM
    2) BPM call bs of target system (WS). how? because in interface determination you selected    
       before the interface mapping
    Regards
    Seshagiri

  • SAP IDOC

    Hi All,
       I have few questions on SAP IDOC's
      1. If we are using Standard IDOC, then is it only the config or any coding is required to populate the IDOC. Examaple Order03
    2. If we Customize, then only customize fields needs to be populated or all the fields (SAP Standard and Custom fields)
    Thanks & Regards
    SM

    Hi
    1.. If we are using Standard IDOC, then is it only the config or any coding is required to populate the IDOC. Examaple Order03
    Have to do complete configuration in the system.if required very less code in the fun module can be written.
    see the below doc
    2. If we Customize, then only customize fields needs to be populated or all the fields (SAP Standard and Custom fields)
    Only code has to be written for the population of the custome fields in the custom segments of the Idoc extension in the user exit of the idoc.
    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
    Message was edited by:
            Anji Reddy Vangala

  • Imported Objects - IDOC

    Hello,
    I'm trying to find a data type that is used within another data type.
    The first type is an imported object IDOC:  ORDERS.ORDERS02.ZORDERS1
    within this object is a data type called ZORDERS1.Z1EDPA1 and that is the data type I need to edit.  I am unable to locate this type in the imported objects folders or listed as a data type under any namespaces in the Intergration Repository.
    Does anyone know where I might be able to find it and edit it?
    Thanks,
    Matt

    In XI I have an IDOC adapter that takes a PO from SAP R/3 and sends it to our SUS system.  When I look at the POs being sent I see that XI uses the type ORDERS.ORDERS02.ZORDERS1 and the sender namespace is urn:sap-com:document:sap:idoc:messages.  Within that type there is a sub-type (for the segment Z1EDPA1) that I need to edit.
    Currently the XI shows this segment as having two data types defined within it:  segment and ZZECHANGEREQID.  I need this data type to show all the fields within the segment name1, name2, address, etc.
    Where is this namespace urn:sap-com:document:sap:idoc:messages defined?
    Thanks,
    Matt

  • Error in importing an idoc

    hi friends,
    i am new to xi.when importing an idoc say from ecc5 to xi for a file to idoc scenario,I am getting this message-'System ECC is running on the specified application server. However, source system sapecc50 is specified in software component version FILE_TO_IDOC_COMP , 3.0 of sap.com Do you want to disconnect?' - Could anyone help me out.Thanks in advance

    hi karthik,
    this is just a message.. you can say yes and give the necessary details to connect to the system and import the idoc.
    when you double click on your SCV, there is a system that is specified there.. i guess, the idoc you are trying to import is from another. hence, you can give the details of the system you want to import idoc from.

Maybe you are looking for

  • Import Container contains Error

    Hi, when i'm using in QAR, i didnt found any error in PO release strategy. But now, i'm facing the error Import container contains errors (are any obligatory elements missing?). I've checked workflow definition, it doesn't shows any error. And the im

  • IPhone developer site not working.

    Ive been trying to download the SDK for iPhone for two hours now. The site fails at the redirect.html site. And the developer site fails to load images and what not. Is it a bandwidth problem they are having? Is there another site i can download this

  • C project in labview

    Hello, i have one project developped using c code, this project is composed with 4  .c files ( each one with its .h file), in the 5th file i have the main()  function with other functions, before asking here , i have been reading this http://www.ni.c

  • Restore and Permissions Questions

    I'm wondering what my restore options are going alllow me to do. Let me elaborate on my situation and it might reveal why I am posting a new topic. I bought my macbook pro used, and it came with ilife and mac office installed. I used time machine to

  • Dark capture in FCE4; fine in iMovie

    Hi, I captured a clip using iMovie ('11) the other night. I bought FCE4 last night and tried importing the same clip; it looked dark, so I compared the two, and sure enough, the FCE4 capture is darker and loses some detail in areas that detail is pla