Req Idoc steps in detail for creating Idoc control records(Sender Non SAP)

Hello All,
I have a scenario where a Microsoft biztalk server communicates with SAP ECC through Idoc ORDERS05 . i need to give them the information of the below IDoc control records
SNDPOR
SNDPRT
SNDPFC
SNDPRN
RCVPOR
RCVPRT
RCVPFC
RCVPRN
IDOCtype
Since the sender is Ms Biztalk . kindly let me know the detailed  steps involved in creating the sender side info such as SNDPOR, SNDPRT, SNDPFC and SNDPRN.
Thanks in advance ,
Pavithra

Hi,
The info like (SNDPRN) which has to be providen by Biztalk in the IDoc control of their Idoc are these ones that YOU defined in the ALE config (tx WE20) of your ECC, to accept this IDoc (idoc message / idoc type) from Biztalk.
If your ALE config is not yet created in your ECC, you have to do it. For instance, check in WE20 (partner profile) the ALE config of your other systems, and in WE02 (Idoc log) to see the content of an IDoc Control, by selecting an inbound Idoc.
Do not hesitate to use WE19 to test an idoc integration, as you have to fill the idoc control manually. By this way you will sure be of what info Biztalk has to put inside their IDoc control (EDI_DC40).
Regards
Mickael

Similar Messages

  • IDoc status 51 - LSMW for Creating Purchasing Info Records

    Dear All,
    My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
    In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
    Request you guys to resolve the issue....
    Solution will b rewarded.. Thanks in advance....

    I shouldnot use basic type INFREC01 instead of NFRECMASS01.
    'coz Within the FM there is a check for basic type like:
    check idoc type
    if f_idoc_control-idoctp c_idoctp_infrec01. " INFREC01
    raise wrong_function_called.
    endif.
    Even one can go to WE57 and see the basic Type INFREC01 assigned to the FM IDOC_INPUT_INFREC, hence one shud use this basic type...

  • IDoc status 51 - LSMW for Creating Purchasing Info Records using IDoc meth

    Dear All,
    My req is to create a Conversion for Purchasing Info Records. LSMW's IDoc method is used to develop this conversion wherein Message Type "INFREC" and Basic Type "INFRECMASS01" are being used.
    In the 14th step (Start IDoc Processing), I 'am getting the IDoc status "51" and Status Text "Application document not posted". If I double click on respective IDoc number, I got its Control record, Data records, and Status records; in the status records I can see "51" in Red color with the message "Function module not allowed: IDOC_INPUT_INFREC". If I double click on this it asks me to check the process code...
    Request you guys to resolve the issue....
    Solution will b rewarded.. Thanks in advance....

    U should use basic type INFREC01 instead of NFRECMASS01.
    Within the FM there is a check for basic type like:
    check idoc type
        if f_idoc_control-idoctp <> c_idoctp_infrec01. " INFREC01
          raise wrong_function_called.
        endif.
    Edited by: Joyjit Ghosh on Sep 15, 2008 4:57 PM

  • FM FOR CREATING NEW CONDITION RECORDS FROM INPUT FILE

    Hello vikas,
    I need to develop a interface program FOR CREATING NEW CONDITION RECORDS FROM INPUT FILE.
    Is there ay function module to update or create the condtion records,
    if u have any example interface program to update conditions records please send me.
    regards
    ram.

    This must be your compiler output.
    Basically, it is telling you two things that are wrong - in syntax.
    1. On line number 11 of the file RationalCollection1.java, the compiler expects a type identifier - that would be the object or return type such as int, String, boolean, etc.
    The reason it is doing this is probably due to your not ending a previous statement - like the "expected ';'" error statement. Check your code, make sure that methods (brackets) are closed correctly and there are no open statements (i.e. missing the semi-colen at the end).
    2. On line number 33 of the file RationalCollection1.java, the compiler expected the closing bracket. Thus, you didn't put the bracket where the compiler wants it.
    It appears that you have skipped some lines of code. Those lines are the problem, post them - post lines 30-36 and 9-15 so we can see what is happening around those error lines.

  • Reg : class for creating table control

    hi everyone,
                 is there any class for creating table control?my requirement is
                  created 2 custom containers,one for alv display and other for table control display.
    For alv i used cl_gui_alv->set_table_first_display,likewise any class for creaitng table control?????????
    pleas find me a solution......
                      thanks in advance......

    Hi,
    You can use the class CL_TABLECONTROL for creating table control and the method SET_VALUES shall be used to fill values for tha tabcntrl.
    Else, you can use the Table Control Wizard to create the tabcntrl easily.
    Regards,
    Renjith Michael.

  • 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

  • FM to get partner profile details for ALE-IDOCs?

    hi
    is there any function module to get partner profile details in current system?
    extremly sorry my mistake......
    for ALE-IDOCs
    Message was edited by:
            ashwinee mali

    BAPI_BUSINESS_PARTNER_MODIFY   CBP: BAPI for Modifying (Creating/Changing) Business Partner             
    BAPI_BUSINESS_PARTN_GET_DETAIL CBP: Business Partner Detailed Information                               
    regards,
    srinivas
    <b>*reward for useful answers*</b>

  • Port details for particular IDOC

    Hi All,
    I want to find PORT details for a particular IDOC.
    Will you please let me know how to find PORT details for a specific IDOC?
    Thanks in Advance,
    Ramana

    Also Kcr, pls check this.
    Assumin your instance number is 00
    ABAP Port : 8000
    JAVA Port: 50000
    What is to be undwerstand here is the role of your port here, if you want to acess any Xi component residing on the Java stacj you will use 50000, since SLD and rwd are on the java stack you cannot have different port to acess them.
    similary for ABAP Stack 8000 is used.....
    inaddition to this you will also have the trfc Port for IDOC communication port,
    you can check the abap port by SMICMgotoservices......
    kindly reward if found helpful.
    cheers,
    Hema.

  • FICA -IDOC for posting the billing data from NON-SAP ISU system

    Hi,
    Kindly note we are implementing NON-SAP ISU with SAP FICA for the finance implementation. In this context, we ahve identified BAPI for BP and CA. We have decided to go for transaction posting through the transaction FPE1. For this, we are looking for the transaction data IDOC which is CTRACDOCUMENT_ACCOUNT (FICA Posting)  in the WEDI. But it seems that it is not yet released. Can anybody help me out for this to either identify the equivalent IDOC or other method to post the data from Banner system (NON-SAP ISU ) system. We are presently not implmenting billing system in SAP ISU, but only FI system

    Hi,
    you can create the same...
    but normal practice what we do is create swc for each system so that it is easy to maintain and easy to extend in the future..
    or else follow some conventions if you are just starting the things..
    HTH
    Rajesh

  • FM or BAPI for creating purchase info records and purchase conditions

    Hi all,
    i need create purchase info records and purchase conditions from txt-file,
    What FM or BAPI i can used for this?
    Thanks and Regards,
    Andrei

    You can use trasaction SXDA_TOOLS.....
    object type BUS3003
    program type BINP
    program/method RM06IBI0
    but the fields must be sequentially written in the txt, with every space inclusive....

  • Details regarding Create customer master record

    Hi,
    Can anyone gv info regarding Creating customer master record.
    I need Existing Bapi's for the same.
    Thanks in advance.
    Purna

    Check out the bapi:BAPI_CUSTOMER_CREATEFROMDATA1.
    To know of how to use it, check its documentation, it is very well documented.
    hi karthik, shaik can not reward points as he did not mark this as a question.
    Regards
    Gopi

  • FM or BAPI for creating/deleting condition records for an output type

    Hi all,
               what is the FM or BAPI for creating and deleting the condition records for a Z(custom) output type.

    You can use trasaction SXDA_TOOLS.....
    object type BUS3003
    program type BINP
    program/method RM06IBI0
    but the fields must be sequentially written in the txt, with every space inclusive....

  • Error during creating a control record

    Hi Experts,
    we are using  EEC6.03 version.
    system error..
    Change before earliest retro. date 01.03.2010 acc. to control rec. to py area CO
    Error-
    While creating Control Record, system takes advance period.
    example-
    We have given present payroll period as 12.2009, and  earliest retro active accounting peroid  as 10.2009,
    then system takes the date 01.03.2010.
    Actually System should take present payroll period as 01.12.2009, But is shows as 01.03.2010. I am unable to understand.
    Please Help me out Guys.

    Hi,
    It seems that your payroll periods are screwed up. To check that please check table V_T549Q (SM30) and see if period corresponds to dates. Period parameter is assigned to payroll area in table V_T549A.
    Then if it is wrong you can regenerate them using transaction OG00. Please read report help thoroughly.
    Cheers

  • Looking for "Creating IDocs from Outbound Deliveries 101" guide

    Please forgive what is probably a very stupid question as I am very new to the subtleties of SAP interface configuration. I am looking for a guide to as to how to set up SAP4.7 to create an IDoc from the creation (or update) of an outbound delivery. I'm think I'm looking for a SHPORD IDoc, and I thought I'd set up all the necessary stages, but I create a delivery and no idoc appears.
    If anyone knows of a "basic configuration guide" to get a SHPORD idoc from a delivery then please point me in that direction.
    Thanks!

    check here https://www.sdn.sap.com/irj/sdn/wiki
    SAP R/3(Idocs) to XI - Steps Summarized

  • Enhancement for creating IDOC.

    Hi All,
    I have a requirement in which I have to generate a IDOC of type INSPECTIONPLAN_CREATE01 everytime Inspection Plan is created(QP01), changed(QP02) or deleted.
    Can anyone suggest me the appropriate enhancement or BADI for the same.
    Regards,
    Monica

    Pl see if you can use any of the following three exits.
    EXIT_SAPLCQBM_001
    EXIT_SAPLCQBM_002
    EXIT_SAPLCQBM_003
    2 BADIs being called -
    IMRM_TL_WORKFLOWS
    CP_DIG_SIGNATURE
    <b>Reward points</b>
    Regards

Maybe you are looking for

  • ADF RC on Tomcat

    Has anyone gotten ADF RC to work on Tomcat (or JBoss or Glassfish). I know an updated ADF RC installer is not out, but I wanted to know if someone got something working. Here are the following links I have found... [unanswered question on a blog|http

  • Computer Shuts Down With FireWire Attached

    Just picked up my 13" MacBook Pro - Made mid 2009. I picked up a FireWire adapter to go from the FW800 to FW400. Just tried it out for the first time and as soon as I plug the adapter into the computer it shutdown. I don't have anything with FW800 to

  • Problem with fill-in-blank questions

    I'm using powerpoint 2003 and Adobe presenter 7. When I create fill-in-blank questions in quiz, more detail: I have 5 textboxes in 5 sentences; after each sentence, I pushed "enter" to make a new line (of course, there is 1 textbox in each one). It s

  • Advantages of buying MSI products

    Hi people. I just wanna seek some help here for my Social subject project. I hope someone can list down 5 good advantages of buying MSI products. Thank you!

  • How to handle ORA-00001: unique constraint in EXCEPTION block?

    Hi, Is there a specific exception thats raised when ORA-00001: unique constraint error occurs?