Idoc ACCONF configuration

Hi friends,
We have inbound INVOIC message type configured in our system to post vendor invoices for both MM ( process code INVL ) and FI ( process code INVF ).
Upon the idoc posting is complete the requirement is to send a ACCONF idoc back to the sender with the status on the invoice idoc posting.  I'm having trouble finding any information on what needs to be set-up to trigger this ACCONF Idoc type ACCONF01I.
Can anyone help with this?
Thanks in advance for your time.

Hi,
I am not sure if this is the best way how to create your IDoc but you can try to use Business transaction event. There is event for posting FI documents. You can try to use this event to call FM which will generate your IDoc. Another possibly better way might be to define your IDoc as output message for FI document. Hence SAP will generate it automatically after creating FI document. You can find some examples of setting IDoc as output message in transaction NACE. Look for output types with word EDI in description. I would try the second option first.
Cheers

Similar Messages

  • Idoc adapter configuration

    while idoc adapter configuration we uncheck the option " apply control record values from payload" why and when it will be usefull?

    Hi Sudhakar,
    When you want to map control record values from the Target payload .....
    Then you choose the option apply control record from payload.
    Follow the link below to understand the concept better....
    (Configuring the Receiver IDoc Adapter --> Fields of the IDoc Control Record)
    http://help.sap.com/saphelp_nw04/helpdata/en/b9/c5b13bbeb0cb37e10000000a11402f/frameset.htm
    Regards,
    Sushil.

  • IDoc Adapter configuration for very high volumes

    Hi PI Expert,
    I'd like to have some tips about Idoc Adapter configuration in case of very very hudge volumes in "file to Idoc scenario" (adressing ECC) : How to optimize Idoc transmission time PI -> ECC ?
    => parallelization PI -> ECC by using differents comm channel IDocs with differents RFC destinations ?.
    => some other technical parameters in adapter IDoc
    => ...
    Thanks a lot
    Best regard.
    Etienne

    Hi,
    for sure idoc bundling will greatly increase performance: https://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken]
    If you are in 7.1 you can also leverage message packaging: http://help.sap.com/saphelp_nwpi71/helpdata/en/46/79e8e13872275ae10000000a11466f/frameset.htm
    Regards,
    Sergio

  • Idoc ACCONF trigger point

    Hi friends,
    We have inbound INVOIC message type configured in our system to post vendor invoices for both MM ( process code INVL ) and FI ( process code INVF ).
    Upon the idoc posting is complete the requirement is to send a ACCONF idoc back to the sender with the status on the invoice idoc posting.  I'm having trouble finding any information on what needs to be set-up to trigger this ACCONF Idoc type ACCONF01I.
    Can anyone help with this?
    Thanks in advance for your time,
    Hitaishi

    Check BTEs 00001025 or 00001030
    Regards
    Vinod

  • Idoc Sender Configurations

    Hi,
    Our requirement is to do Idoc to File scenario in which what are all the configurations that are to be done in R/3 and as well as in XI server.
    regards,
    Kishore

    Hi Kishore,
    Please go through /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters
    also i give a quick checklist, chk it out.
    1)Create an RFC destination to XI in the sender SAP system using SM59
    2)Create a transactional port to XI using the RFC destination created in the above step
    3)Create a Partner agreement usign transaction we20 and port using we21 in the sender SAP system
    4)Create a logical system using transaction bd54 for the partner agreement created in the above step
    5)Select an IDOC using transaction we19 and change the EDIDC header recepient port & LS name
    6)Create an RFC destination to the Sender SAP system using SM59
    7)Create port to sender system using idx1 in the XI system for the RFC destination created in the above step
    8)Create SLD entries(technical and business system) for the sender SAP system.
    In IR , import IDOC metadata, create ur target XSD , create ur Message Mapping , Interface Mapping, thats it.
    In ID, import ur sender R/3 system & receiver systems, U dont need a IDOC sender CC , so only File receiver CC is reqd. Now create a receiver determination, interface determination & receiver agreement ,activate & ur done.
    Use WE19 , select an IDOC and do an outbound processing and u shud see the IDOC in XI.
    Rgds
    joel
    Edited by: joel trinidade on Feb 23, 2009 2:44 PM

  • Idoc Adapter Configuration Issues

    Dear Collegues,
    I have given up almost all hope on configuring my Idoc adapter as I have an error message that I am not sure of how to fix; I have read just about everything I can get my hands on....any help would be so much appreciated:
    Scenario: Demonstrate a simple 'proof of concept' to send MATMAS from R3 ->XI -> R3
    Sending system: [R3 4.6b] CL0510
    Rec'g system:  [R3 4.6b] EL0510
    XI system 3.0:  NXL220
    Current error message in outbound RFC layer of CLO: 
    No service for system SAPCL0, client 510 in Integration Directory
    <u><b>Per the documentation I have done the following:</b></u>
    - RFC connections are all complete
    - Port and Partner Profiles complete
    - ALE model from sender for MATMAS
    - IDX1 in nxl for ports
    - IDX2 - matmas metadata
    - Integration Builder [config]: 
       *Technical and Biz systems set up
       *CL0510 is set up as 'services w/o party' and there is
       a generated idoc channel. 
       *The Adapter Specific Identifier is the CL0510 log 
        syst.
       *Receiver Determination is created w/ 
       idoc_inbound_asychronous as interface; not sure 
       what "namespace" is so I threw the word Idoc in there
       *Interface Determination is created w/ above 
        parameters except the receiver party and service have
        asterisks in them I can't seem to remove
       *Sender and Rec'r Agreements set up [again what goes
         in that namespace field?]
    I think that identifies all of the configuration I have attempted to enter.  I have been only able to read documentation and weblogs as XI training won't be happening for me and my collegues until another several weeks.
    Thanks so much,
    Jennifer Edmondson
    Intel Corp, AZ

    Hi Jennifer,
    for the inbound to XI, e.g. CL0510 you don't have a sender agreement since when you setup up the WE21 trfc Port on CL0510 it points to the XI system as a regular type T SM59 connection. On the connection you can enable the TRACE flag and see in the trace what payload got sent and any errors. I had a problem with that as my user / password to the XI machine was wrong.
    The other part I'm missing from your message is, did you do all the Repository stuff beforehand, e.g. import the IDOCs for each Software Components(defined in the SLD, Tech and Buiz System), then when you use the dropdown in the Directory the Namespaces will default as the urn:sap-com:document:sap:idoc:message. Again once you have done the repository there is no need to write namespaces by hand at all. Do not put an IDOC into a Message Interface, may be into an action if you like to put a scenario into the IR (not necessary).
    On the Receiving IDOC Adapter you will specify all the RFC stuff for the EL0510 system and this one goes into an receiver agreement.
    I'm sending MATMAS from R/3 to XI to File Adapter or SOAP and no issues at all.
    On CLN510 in BD87 does the IDOC has a status of send? Does it look ok?
    I hope this helps. I can make some screenshots of my config if that helps. Send me an e-mail to [email protected]
    Cheers
    Stefan

  • Idoc Communication Configurations and Proxy Runtime Configurations for PI

    We have a fresh PI 7.1 system, fresh ECC6 system, and an existing 4.6C system.
    is there any blog/doc with step-by-step instructioins/screenshots for following tasks:
    1. Configuring Abap proxy runtime between ECC6 and PI 7.1 Systems, for using sproxy from ECC6.
    2. Configuring for IDOC communication between ECC6 and PI 7.1
    3. Configuring for IDOC communication between 4.6C system and PI 7.1
    It involves creating of sm59 rfc destination creations, usage of idoc related transactions on PI system and the other system.. I searched on sdn/forum, but it seems to be addressing specific issues faced.
    Pls suggest any step-by-step instructions docs/blogs available.
    thanks in advance.
    Madhu.

    Madhu,
    Refer the links below:
    1. /people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies
    2& 3 :
    https://wiki.sdn.sap.com/wiki/display/XI/SAPR3%28Idocs%29ToXI--Steps+Summarized
    http://www.riyaz.net/blog/xipi-settings-in-r3-partner-system-to-receive-idocs/
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/877c0d53-0801-0010-3bb0-e38d5ecd352c&overridelayout=true
    http://www.riyaz.net/blog/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
    Also, I  think u hv just started learning XI ..so following link might help:
    http://wiki.sdn.sap.com/wiki/display/NWTech/QAforPI-Onestopforall%28Part-1%29

  • Can anybody explain all the details about idoc like configuration settings etc..

    Hi all can anybody explain the idoc configuration settings, communication channels sender and receiver settings

    Hi,
    Common steps in both Sender and Receiver:
    Create logical system and assign to client
    Create RFC Destinations in SM59
    Create RFC Ports in WE21
    Steps in Sender
    Create table in SE11 and insert data
    Create Segments in Tcode WE31.Define the table fields in segment
    Create basic IDOC type in WE30.Specify the above created segment name,save and release the IDOC
    Create message type in WE81
    Assign message type to IDOC type in WE82 and release
    Create partner profile in BD64,add the message type ,specify sender,receiver,message type and  generate partner profile and execute.Distribute the model view
    Check the partner profile in WE20
    Develop a report in SE38 with code that transfers the data from source to destination
    Execute the report and specify the fields to be transferred
    Check the control records in WE02
    Steps in Receiver:
    Create an update function module in SE37
    Assign the function module to logical message
    Define input method in Tcode BD51
    Create process code in WE42
    Generate partner profile in BD64
    After executing the report in sender system check in the destination system table wheather the fields are transferred
    In this case a custom table has been created in sender and receiver with same structure.We can even transfer the standard table fields by using idocs
    Thanks & Regards,
    Sravanthi Polu

  • BAPI's , BADI ,BDC & IDOC's configuration in sap

    Hi Experts,
    can any one explain how to configure BAPI's , BADI ,BDC & IDOC's in SAP step by step, right answer will get reward points. if u have any noted pls forward to my email id pls....................................
    amar
    [email protected]

    Hi,
    how to configure?
    BAPI are remote functions that can be called by another system or same system...you can use standard BAPI or create your own BAPI. (transaction BAPI and SE37)
    BADI are methods that you can re-define in order to change SAP standard logic for some functionalities...(transaction SE18 and SE19)
    IDOC are structured files in a SAP format that can be customized and used to send or receive data instead of xml or txt or ....files. IDOC can be monitored and checked with a set of transactions.
    Regards.

  • IDoc ORDERS05 - Configuring IDoc Segments

    Hi All,
    Needed some help on understanding how to configure a new idoc using an extended SAP standard idoc type.
    I'm using the ORDERS05 idoc type and extending it to add a single segment (example extended idoc type: ZORDEXT).  We're creating a new condition type to trigger the idoc after sales order create/change.  I'm planning to use the standard FM IDOC_OUTPUT_ORDRSP to create the idoc.
    I noticed that only 1 segment in the ORDERS05 is set to mandatory (E1EDK01).  We have identified at least 10 other required segments in the standard idoc which we need to populate with data.  How do I configure the idoc to populate those segments?  Do I need to set them as mandatory in a customer exit?
    Thanks in advance.
    Cal

    I would have thought that the easiest place to strip out all the unwanted segments would be in your Middleware. Otherwise, you should be able to strip the segments out by creating an include in one of the Customer Functions in IDOC_OUTPUT_ORDRSP, i.e.
    CALL CUSTOMER-FUNCTION '004'
    CALL CUSTOMER-FUNCTION '001'
    CALL CUSTOMER-FUNCTION '003'
    Cheers, Paul.

  • IDoc intreface configuration

    Hi Everyone,
    I need to configure the environment for an inbound idoc. I'm workin in an environment(EN1 Client 100) where I've created all the Function Modules for processing. Now there's a Partner Profile P1 in client 200 that needs the new idoc type be added to its inbound parameter list, which requires a Process Code. To create a process code I require FM in the same client.
    Is it possible to configure the client 200 for inbound parameters while all the FMs are yet in client 100?

    Hi,
    It didnt ask for a TR while I created a new entry.
    I've checked the Transport Organizer too. There is'nt any customizing request.
    Are there any settings to be done, so tht it creates a TR while creating new entries?? the transaction surely has options in the menu for transporting the changes but right now all are deactivated (greyed out).
    Regards,
    Munish

  • IDOC Header Configuration

    hi experts,
    tell me about the IDOC Fields and its Creation.
    (Where to define
    Reciever Port, Partnernumber
    Sender Port, Partnernumber
    actually i created one and for all the fields, but when i tried with those it shows status message as 37 ( Sender port)
    <i>help me to resolve this</i>
    tell me how the entire system <b>( of outbound idoc) </b>works
    thanks in advance
    nikhilbos

    Hi,
    This is expalined both the scenarios:
    Please follow the below process for configuration:
    Pre-requisites for Inbound IDoc to R/3 from PI:
    Configuration required at Xi side:
    Go to IDX1: configure the port.
    Go to IDX2: load the DOC metadata.
    Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
    Configiration required at R3 side:
    Maintain Logical System for PI (SALE transaction):
    Maintain Partner Profile for XI system(WE20):
    Pre-requisites for Outbound IDoc from R/3 to PI:
    Configurations required in R/3:
    Maintain Logical System (SALE)
    Define RFC Destination (SM59) which points to PI system
    Maintain Port (WE21)
    Maintain partner profile. (WE20):
    Maintain Distribution Model (BD64):
    Also refer ALE configuration for pushing idocs from SAP to XI
    /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
    Thnx
    Chirag Gohil

  • XI 2.0 - IDOC Adapter configuration

    Hi,
    I currently have an integration scenario whereby an external system sends IDOC-XML to our integration server which then forwards this via an IDOC adapter to an R/3 620 system. 
    When I send the XML to one client I keep getting the following message :-
      <SAP:Context />
      <SAP:Code p1="Requested parameter does not exist" p2="RQ1CLNT302" p3="" p4="">IDOC_ADAPTER.RECEIVER_BSI_INCORRECT</SAP:Code>
      <SAP:Text language="EN">Unable to convert partner to IDoc receiver partner</SAP:Text>
    After my initial investigation I believed that the above error was due to the client within the SLD had been set-up without a logical system name and the receiving business system had been set-up without an ALE name.  In order to resolve this I deleted and re-created the client and the business system within the SLD.  Having done all this the error still occurs. 
    Does anyone know what causes this problem?
    The systems involved have been set-up in the SLD as follows :-
    a) Sending system PKMS_SAPTEST Alename: PKMS_TEST
    b) Receiving system RQ1CLNT302 Alename RQ1CLNT302
    I have checked the ports in IDX1 and the partner profile in the receiving system but still cannot work out what is causing this problem.
    I know I am missing something really obvious as these messages work when I send them to other clients but I am at a loss to explain the difference
    Regards
    Ian

    Hi All,
    I have now resolved this problem and thought I should spend some time sharing this with you. 
    I decided to look at the code that was issuing the error which was calling a function module called SAI_LOGICAL_SYSTEM_GET to return the logical system for my business system.  When I ran the function module in test mode it returned a blank logical system.  The logical system is stores in table sailcrbsc.  I re-ran the function module with the bypass buffer field set to 'X' - now when the function module is called it returns the correct logical system.
    Anyone out there have any more info on this?  How should I have re-built this table?
    Regards
    Ian

  • IDOC Listeners Configuration

    Hi,
    We are trying to send IDOC from ECC to xMII 11.5 through IDOC Listeners data services.
    We are already sent some IDOCs, itu2019s processed successfully in ECC.
    These are the clarifications are required:
    1)     How to check and view the IDOC status in xMII (the routing rules are already in place).
    2)     Is mandatory to create the transaction for this scenario?
    Thanks for your suggestion in advance!!!
    Regards,
    Boopathi

    Hi Boopathi,
    If you have routing rules in place and a transaction, the main method of testing success would be from within the transaction via event logger or file save or any of a number of different methods.  You could even have the transaction send you an email. 
    If you are just testing for IDoc transmission, I would not attach a transaction or build routing rules.  Without a transaction, the IDoc will be saved in the folder assigned.
    Good luck,
    Mike

  • IDOC configuration in 46C for BI 7

    Dear Experts
    Is there a set of  steps to create the idoc configurations in R/3 for data transfer between R/3 46C  and BI 7?
    After refresh, the idoc related configurations are lost and BI is unable to load from Source System R/3.
    Thanks for reading and hope you can advise on the above.
    Best regards
    Pascal

    Hello Pascal,
    Maybe a thread in the PI forum would help you better:
    Process Integration (PI) & SOA Middleware
    Check the following thread:
    Re: interface help
    Regards,
    Eduardo Rezende

Maybe you are looking for