COnfiguring IDOCs for Inquiriey/Quotation

Dear Experts,
I have  a requirement to trigger IDOCs when a Quotation is SAVED in SAP CRM.
Can anyone pls provide so configuration steps.......
We are in CRM 4.0.
Or any idea about output configuartions..
Thanks,
reshali.....

Hi experts,
I am new to idocs, Requiremnt is to send the idoc having quotation no to the external sys ( out bound ).
i have tried but i cld only find idoc for sales order which is orders--. somehow i cld not locate the idocs for quotation
if someone has already worked on the idoc for  sales quoatation wld request you to suggest.
I have also tried to search on sdn for the above mentioned requirement but was not successful
your help will be appreciated.
Thanks
Regards
Edited by: sabsvk on Jan 11, 2010 6:29 AM

Similar Messages

  • Configure idocs for User management ack settings?

    1. IDOC config idoc says acknowledgments should not be requested, and run idx_noale ? why should we turn off and how to do this ?
    2. IDOCs sent to IS should not be processed by IDoc adapter, advises insert the relevant idoc types into exception table, execute report idx_select_idoctyp_without_is
    why we need to configure explicitly for each relavant ido types?
    thanks

    Hi Kumar,
    Receiver adapters that run on the Adapter Engine support system acknowledgments if they are requested by the sender. Acknowledgements are triggered when a message is successfully processed by the adapter or if an error occurs while it is being processed. Receiver adapters do not support application acknowledgments. The RNIF and CIDX adapters are exceptions to this rule, since they also support scenario-dependent application acknowledgments. Sender adapters of the Adapter Engine do not request any acknowledgments.
    This means, JDBC adapter does only send system acks, however IDoc adapter is requesting application acks. Therefore as mentioned by the previous poster, you have to disable acks for this scenario using report IDX_NOALE.
    Also go through these documents for any further help:
    http://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/xi/xi-how-to-guides/how to handle acknowledgments for idoc.pdf
    http://help.sap.com/saphelp_nw04/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
    I hope this clears all your doubts.
    Regards,
    abhy
    PS: AWARD POINTS FOR HELPFUL ANSWERS.

  • Triggering an idoc for Quotation

    Dear experts,
    I am beginner to ALE & idocs.I want to see how ALE works by triggering idoc for quotation viewed through VA23.
    I want to transfer a single quotation between y Development logical clients.
    Configuration is done in SALE.
    Basic type is ACC_SALES_QUOTA01
    Messagetype is ACC_SALES_QUOTA
    E1BPACCRSO and E1BPACSQ00 are segment types.
    I can also see the documentation of same in WE62
    Function module in WE57 is BAPI_IDOC_INPUT1 and BAPI_IDOC_INPUTP ie two different for same basic and message type .
    My first question is why so ?.Which will triggger .?
    in WE41/WE42 how will i know for given functionmodule which process code is assigned?.
    How can i know whether this basic type is an inbound idoc or outbound idoc or any idoc basic type can be used as outbound and inbound ?.I am little confused as i am new to ALE & idocs.
    If i assume that any idoc can have any direction ie inbound as well as outbound then i should have process codes in WE41 as well as WE42 ,which is not true here.
    Edited by: aditya  sharma on Jul 14, 2010 8:15 AM

    Hi,
    you can refer below link for ALE-IDOC info.
    http://help.sap.com/saphelp_46c/helpdata/en/d5/edf163dcdc11d1890c0000e8216438/frameset.htm
    WE41 refers to outbound process codes and WE42 refers to inbound process codes.
    for quotation use SD12 process code for outbound.

  • Configurations required for IDOC to File

    Can any body suggest me the configuration required for integrating remote R/3 system with the XI Server.
    I want to know the following.
    1) How and where to configure R/3 with the XI server.
    2) What are the configurations required for Outbound and Inbound IDocs in R/3 and XI Servers.

    Hi Rajeshwar,
    take a look over here:
    https://www.sdn.sap.com/sdn/weblogs.sdn?blog=/weblogs/topic/16
    you'll find at least 5 weblogs that show the idoc configuration
    Regards,
    michal
    XI FAQ - http://www.bcc.com.pl/netweaver/sapxifaq

  • Idocs for  quotation creation

    Hi Experts,
    Have any one of  you worked on idoc meant for sales quotation ?
    could u please tell me whether the idoc meant for creation of sales order and sales quotation are  "orders--"
    only .
    Thanks,
    sabs
    Edited by: sabsvk on Jan 7, 2010 8:21 AM

    Hi experts,
    I am new to idocs, Requiremnt is to send the idoc having quotation no to the external sys ( out bound ).
    i have tried but i cld only find idoc for sales order which is orders--. somehow i cld not locate the idocs for quotation
    if someone has already worked on the idoc for  sales quoatation wld request you to suggest.
    I have also tried to search on sdn for the above mentioned requirement but was not successful
    your help will be appreciated.
    Thanks
    Regards
    Edited by: sabsvk on Jan 11, 2010 6:29 AM

  • Idocs for Purchase RFQ

    Hi Friends,
    Does anybody knows how to configure, an Outbound Idoc to non SAP application for Purchase Request For Quotation? And after inbound a similar Idocr for update Quotation into SAP using estandar Idocs messages?
    Thanks for your help,
    Andres.

    Hi
    Check these links for 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.
    Check 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://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Outbound IDOC for Credit Management

    HI All,
    We need to send the Credit management data from SAP to other system. For that we require Standard IDOC, could you please suggest the standard IDOC available for the same and how to configure it. Please let me know if we have any standard program which generates the IDOC for my requirement.
    Regards,
    Phanindra

    Thanks for the Input, could you please let me know how we trigger this IDOC. Is it through configuration or any standard program which will generate idocs.

  • IDocs for Invioce and Delivery

    Hi all,
    I have to send the customer the Invoice and Delivery confirmation for that order placed by him through an IDoc in background job.
    We are going for a standard IDoc for invoice and Delivery also but how to fill the data into that standard IDoc.
    1.Do we have standard report like (BD12, BD14, BD10 etc.)
    2.Should we develop a report to fill the data into that Idoc.
    Please help me to find standard report or please help me to write code for that standard IDoc.
    Thank you all in advance,
    Regards,
    Shalem.

    Hi Shalem,
    You need to do the following activities.
    - Setup condition record (t/code <b>NACE</b>) for shipping (V2) and billing (V3).
    - Setup output type (t/code <b>NACT</b>) for shipping (V2) and billing (V3) with transmission medium <b>A</b> (ALE).
    - Setup procedures (t/code <b>NACZ</b>) for shipping (V2) and billing (V3) if required.
    - Once the above setup are done, for any creation of billing and shipping will create entries into table <b>NAST</b> (Message Status).
    - Then you can create IDoc using this standard program <b>RSNAST00</b>. Please ensure your ALE and IDoc configuration have been done such as BD64, WE20, WE21 and etc.
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

  • What is the standard inbound idoc for substation management?

    Hello Experts,
    Can anybody help me to find out the standard inbound idoc for substation management?
    The following field are requied to be  filled in idoc.
    1)Power_Produced(STAGR)
    2) Reduction_Power_Consumed(STAGR)
    3)Ancillary_Power_Consumed (STAGR)
    4)Unit (MEINB)
    5) UOM and Date (BUDAT)
    If possible please tell me the standard BAPI for these fileds.
    Thanks in advance for your help.
    Thanks and Regards,
    Suresh.

    Hi Debo,
    What is your exact requirement?
    Are you trying to find the standard configurations available for a webdynpro application? then, use t-code SE15 and open the application name and use the tree structure to find out the available configurations under WD application.
    sample:
    Regards,
    Rama

  • What is the IDOC for Final Approval of PO

    Hi,
    Can any one tell me ..
    1. what is the IDOC for Final Approval of Purchase Order?
    2. Is there any Separate IDOCs for GRN(Goods Receipts
    Note) in Transaction MIGO. Like Creation of GRN,
    Changing of GRN, Cancelling of GRN, Transfering materials to Scrap or Cost center (Changing of Movement types in MIGO).
    regards,
    Khaja.

    Khaja,
    1. There is no separate IDOC for final approval of a PO. IF you have configured a release stratgey for a PO, the PO IDOC will be transmitted only upon the final apporval of the PO.
    2. Yes there should be a IDOC for Goods Receipt.
    Regards,
    Ravi
    Note : Please mark the helpful answers

  • Idoc for customer payment advice

    Hi all,
    We receive Idoc for payment advice from customer. Can some body tell me how can I read this information to match the invoice.I mean how can I map Idoc field to SAP internal tables.
    How do I know which Idoc field will hit which SAP table & which table.
    So please guide me about Idoc mapping & finding appropriate field for inbound idocs.
    Edited by: Nik Wallace on Aug 5, 2008 8:04 AM

    Hello,
    Customer of vendor payment advice is the advice informing the customer that the amount has been paid against which invoices.
    You need to configure the payment advice in FBZP or give them as part of variant in F110.
    When you run the automatic payment program, based on the FBZP settings, a payment advice gets triggered.
    You are able to see your payment advice in SP02. To generate payment advice correctly, please make sure your settings in Variant (F110) are correct. Any invalid entries will result in NO generation of payment advice.
    Hope this is useful to you.
    Regards,
    Ravi

  • Idoc for FI or CO

    Hi,
    i've configured to generate and send idoc for Purchase order, and i realized that someone should create message output (goto -> message), by that time, some batch program try to send idoc.
    my question as below;
    1. regarding FI or CO, FI or CO, is there go->meesage menu on transaction of FI or CO in order to generate IDOC for change pointer? and how to send idoc at the time triggered by transaction?
    2. purchase order, when i output PO for IDOC, i had to set NEU, ALE type, if someone only create PO without goto->message, then PO created will not generate idoc,
    so my questions is how can i make PO which is generated IDOC and send IDOC by automatically when end-user create PO.
    thanks
    venjamin

    Hi,
    what about FI or CO? like general account posting?
    PO in MM,  we have to output message by goto -> message,
    but regarding FI or CO, they do not have message menu or output determination, how can i generate on FI transaction or CO transaction? and send IDOC?
    thanks
    venjamin

  • Message type for generating IDOC  for SUBCONTRACTING PURCHASE ORDER

    Hi All,
    I have to generate IDOC for PO creation or change .
    I am using IDOC_OUTPUT_ORDERS and IDOC_OUTPUT_ORDCHG.
    The messagetype.idoctype  I am using is  ORDERS. ORDERS05  and ORDCHG. ORDERS05.
    Now the confusion is regarding whether  this message type will work in case of SUBCONTRACTING PURCHASE ORDER as well ?
    As I have gone through some websites and came to know that I will have to use PORDCR1.PORDCR102 specially for subcontracting.
    And programs we need to use is BUS2012_ICH_R3 instead of  RSNASTED and Form Routine SEND_PORDCR1 instead of EDI_PROCESSING.
    Purchase Order Collaboration scenario - Not generating IDOC in ECC
    http://www.erpgenie.com/faq/edi_purchasing.htm    on this site question no  8.
    Subcontract PO IDOCs
    I hope your experience will help me .
    Please reply ASAP.
    Edited by: uttam27 on Dec 4, 2011 1:47 PM

    There is a generic function to create change pointers for all message typs - 'CHANGE_POINTERS_CREATE_DIRECT'.  This is triggered only if you configure your message type to create change pointers from BD50.
    Once you activate it do any change to orders you can see change pointer tables BDCPV filled. Then BD21 will read the changes and generated outbound idocs accordingly.

  • Mapping issue: FCC: Idoc for each record in file

    Hi,
    I have file to Idoc scenario.
    I receive csv file with multiple records.
    The requirement is to create an Idoc for each record.
    For eg.
    source file
    A1,B1,C1
    A2,B2,C2
    A3,B3,C3
    After FCC
    <MT>
    <TRANS>
    <ROW>
    <A>A1</A>
    <B>B1</B>
    <C>C1</C>
    </ROW>
    <ROW>
    <A>A2</A>
    <B>B2</B>
    <C>C2</C>
    </ROW>
    <ROW>
    <A>A3</A>
    <B>B3</B>
    <C>C3</C>
    </ROW>
    </TRANS>
    <MT>
    I have first tested it with only 1 record to test end to end connectivity. It works as expected and Idoc is posted to target system.
    Now when I am trying to send multiple records, I am getting some issues.
    Below are the steps that I have taken to process multiple records:
    1. Changed the cardinality of ROW (child of RecordSet) from 1 to Unbounded.
    2. Changed the occurance of Idoc to Unbounded.
    3. Mapped ROW to Idoc root.
    I have tested the mapping in IR and it generates multiple IDOCs.
    When I send the test file, it fails with error Tag found instead of tag IDOC BEGIN=
    I can see the xml message created with multiple ROWs in XI by File adapter in sxmb_moni.
    When I do Test Configuration in ID, with the XML message extracted from sxmbmoni, the result that I got was:_
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
    This means that idoc was not created while mapping.
    But the same sample message works OK in IR!
    Pls help where I have missed.
    Regards,
    Anirudh.

    Sudhir,
    Thanks for your response.
    FCC is working fine. I have taken the XML message in XI created after FCC from csv sample message.
    I have tested this message in IR by placing it between
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
       <ns0:Message1>
    </ns0:Message1>
    </ns0:Message>
    It is working fine and Idocs are created in mapping in IR.
    But the same sample message is creating below output ID!
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
    Regards,
    Anirudh.

  • Help needed in inbound IDoc for ORDERS....

    Hello all,
    I need help in IDoc for ORDERS.. Here is the situation. I have an ORDERS IDoc coming to my SAP system from my customer. When I see the SO it creates.. it says that it has incomplete data.. Information like pricing, inco terms, payment terms. load data, load date etc. is not filled in. How do get those filled automatically.. my customer can not, obviously, give me all the information needed for the SO.. Where do I configure and how?
    Thanks,
    Charles

    Hi,
    You can use user exits available in FM IDOC_INPUT_ORDERS to populate additional information.
    Also you can use form CUSTOMER_FUNCTION_DYNPRO to populate additional information for BDC screens of VA01. This form is available in FM IDOC_INPUT_ORDERS as well.
    Regards,
    Ferry Lianto
    Please reward points if helpful.

Maybe you are looking for

  • Wifi no longer works after update mountain lion

    Ls, I've updated my MacBook Pro to Mountian Lion yesterday. Ever since the update I've lost the ability to use the internet over Wifi. The system shows a check mark on the left of my network list, however there is no outside connection. I have ran th

  • How to Increase the SGA Size.

    Hi Guru's I want to Know How to Increase the SGA Size in Database 8.1.7.4.1 My Ram Size is 6 GB When I query the Below Script select name, value from v$parameter where name in ('shared_pool_size', 'java_pool_size', 'streams_pool_size', 'log_buffer',

  • BAPI s in Visual Composer

    Hi, In Visual Composer, for R/3 systems we use BAPIs. This BAPIs have some mandatory fields for input port and without filling all this fields we cant get data. For sales order BAPI_SALESORDER_GETLIST there are two of them, customer number and sales

  • Dynamic Link Media Server Error On Video Export Photoshop CC 2014

    Dynamic Link Media Server Error On Video Export Photoshop CC 2014

  • Help with static and non static references

    Hi all, I'm new to Java I'm having some difficulties with accessing non static methods. I'm working with Tree data structures and all the interfaces and methods are non-static. I have to write a tester main method to create and modify trees but how d