Complex posting via inbounc IDoc

Hi,
we are implementing functionality to create FI invoices by inbound IDocs using IDoc type ABB_INVOICE_RECEIPT03. We need to have the IDoc import functionality access the complex posting functionality which we are used to access manually from transaction FB60.
Unfortunately it seems to us that this functionality is not available when using this IDoc type. Are we correct about this? We hope not!
Does anyone know how to implement complex posting functionality via IDoc?
We have not found any SAP Notes about this either.
We are running SAP 4.6c
Thanks in advance for all kind assistance!
Regards,
Bernt Evensen

In Complex posting, consultants and experts can have their choice of posting by selecting the posting key and do all the entries as long as the doc type - allows account types.
Only two Tcodes are used by consultants and experts from olden days - F-02 and F-04 - which will take care of most of the transactions. While using the Tcodes , system will take control the settings in PK, GL and display the fields - This will help consults whether the config is OK. In the same screen - the facility of fast entry screen is there - which allows only 40/50 posting keys..- further developed for new screen Enjoy SAP.
In Enjoy SAP posting screens- you need to create separate variant - for entry - but however  while entering the data and saving - system will decide whether it can be entered or not as per GL - FSGrp definitions. Here you have option to select posting keys only 40/50 at the bottom screen- it is development from the fast line entry screen of complex posting -This screen is meant for users who will do only limited transactions. You have editing option for users for this screen separately to avoid mistakes by users and not asking for more informations. You will be able to move from Enjoy SAP to Complex posting and back while doing the transaction.
Hope the above explanation will be of help to you.

Similar Messages

  • BTE for complex posting in FB60

    Hi all,
    I implemented BTE 1030 and 1050 to capture the posting event via FB60 transaction. It works fine if I complete the document with the 'usual' post action.
    The problem occurs when I try to post with the funcion 'Complex Posting'.
    (FB60 --> Enviroment --> Complex Posting). In this case when i complete the document and post it the BTE don't works!! It looks SAP doesn't pass in the custom function implementation (1030 and 1050 interface). Can someone indicates me if exists some others BTE that I can use?
    Thanks!
    Lucio

    Transaction Code - FB60                     Enter Incoming Invoices
    Exit Name           Description
    RFAVIS01            Customer Exit for Changing Payment Advice Segment Text
    RFEPOS00            Line item display: Checking of selection conditions
    RFKORIEX            Automatic correspondence
    SAPLF051            Workflow for FI (pre-capture, release for payment)
    F050S001            FIDCMT, FIDCC1, FIDCC2: Edit user-defined IDoc segment
    F050S002            FIDCC1: Change IDoc/do not send
    F050S003            FIDCC2: Change IDoc/do not send
    F050S004            FIDCMT, FIDCC1, FIDCC2: Change outbound IDoc/do not send
    F050S005            FIDCMT, FIDCC1, FIDCC2 Inbound IDoc: Change FI document
    F050S006            FI Outgoing IDoc: Reset Clearing in FI Document
    F050S007            FIDCCH Outbound: Influence on IDoc for Document Change
    F180A001            Balance Sheet Adjustment
    FARC0002            Additional Checks for Archiving MM Vendor Master Data
    FEDI0001            Function Exits for EDI in FI
    No of Exits:         14
    USER EXIT
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sapgenie.com/abap/code/abap26.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
    http://www.easymarketplace.de/userexit.php
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sappoint.com/abap/userexit.pdfUser-Exit
    http://www.sap-img.com/ab038.htm
    http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
    http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
    http://www.sap-img.com/abap/what-is-user-exits.htm
    http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
    Rewards if useful.........
    Minal

  • XML Forms on the Portal posting to an IDOC

    Scenario
    Goals
    1. Portal Based XML form being used by users to enter information
    2. Posting to an IDOC in R3
    Current Solution
    1. The XML form outputs a file to local file system through the EP
    2. XI then takes this file transforms
    3. XI Posts IDOC
    Question .
    Is there more elegant solution, making use of the file system to transfer files between system strikes me as "ugly". How would I configure the XML form to post directly to XI via a webservice call etc..., I understand how to make the service available in XI, Im just not sure how to make the EP post the XML XI so It can then post the IDOC ?
    Notes.
    1. The XML form has been developed using the Form builder in the Portal
    2. Both the Portal and XI are on NW6 at this stage.
    thanks

    Since researching a little I have discovered the idea of posting an XML form to an IDOC is flawed. So the desired archiecture is now, a form of some sort that can be visually appealing like an XML form that can post directly to an RFC in ECC.
    Enterprise Portal Form -
    > ECC (RFC)
    I have protyped this interaction with Guided Procedures in NW7 and it seems to work but the form presentation is still a mystery.
    How can I have complete control over the presentation of a form in GP to send the data into SAP, or is the visual composer a better solution ?

  • 070302ex603 Formatting errors when posting via BD87 transaction

    Hi experts,
    When posting idocs manually via transaction BD87 all users receive "Formatting error in the field BSEG-WRBTR..." or "Formating error in the field BKPF-BUDAT..." regardless of personal user settings. When the same idoc is posted via scheduler it posts without any error. Can anybody help me out in this issue.
    Points will be rewarded.
    With thanks in advance
    Saravanan

    Hi
    Go to T code ST22. here for the user id in which the dump is generated, click on how to rectify. The system will give you a probable resolution for the problem.  In many cases, there would be some key words, on which you need to serach for a suitable note of SAP to resolve the dump. Take the hlp of your ABAPER also
    Thanks & Best Regards
    Sanil K Bhandari

  • Changing internal order's via Inbound IDOC

    Hi,
          We are having Inbound interface set for creating internal order's using message type 'INTERNAL_ORDER_CREATE01'.
           But when any existing internal order is changed it is giving status 51 with error 'Order already exists'.
          I am wondering how can we handle the changed order situation via inbound IDOC . Is it possible to do it via message type 'INTERNAL_ORDER_CREATE01'.
    Regards,
    ganesh

    Hi ganesh,
    The idoc Status 51 for indound idoc is....
    51 Application document not posted
    the possible solution is checkthe Partner profile for the Idoc and Port number..
    and go to T_code we20 and check the Partner.and check the Syntax in the application tool bar...
    then you will come to know the problem..
    and if you wan to changed order situation via inbound IDOC , yes it is possibel.
    go to t-code we57 and check the Function module attached to the message type .
    and go to FM and find hte customer exit and read the segment which contains order situation and modify the segment..
    i hope this will solve the problem..
    Regards,
    Prabhudas

  • Complex Posting

    Hi experts,
    Complex Posting meny greyed out in FV60 (Park Vendor Invoice) screen but this menu is available via FB60 (Vendor Invoice).
    Can any one explain what is complex posting why it is used in FB60 and why it is greyed out in FV60.
    Thanks in advance
    G. Bhaskaran
    SAP FICO

    In Complex posting, consultants and experts can have their choice of posting by selecting the posting key and do all the entries as long as the doc type - allows account types.
    Only two Tcodes are used by consultants and experts from olden days - F-02 and F-04 - which will take care of most of the transactions. While using the Tcodes , system will take control the settings in PK, GL and display the fields - This will help consults whether the config is OK. In the same screen - the facility of fast entry screen is there - which allows only 40/50 posting keys..- further developed for new screen Enjoy SAP.
    In Enjoy SAP posting screens- you need to create separate variant - for entry - but however  while entering the data and saving - system will decide whether it can be entered or not as per GL - FSGrp definitions. Here you have option to select posting keys only 40/50 at the bottom screen- it is development from the fast line entry screen of complex posting -This screen is meant for users who will do only limited transactions. You have editing option for users for this screen separately to avoid mistakes by users and not asking for more informations. You will be able to move from Enjoy SAP to Complex posting and back while doing the transaction.
    Hope the above explanation will be of help to you.

  • Error 'No tax code found for difference' in Posting Vendor Invoice IDOC

    Hi All,
    I am getting error message 'No tax code found for difference' while posting Vendor Invoice IDOC into SAP. IDOC type is INVOIC02. There is no difference in PO price, Invoice price and even Standard price. then why this  error message? Other Vendor EDI settings are done ( OBCA, OBCD, OBCE etc). Is there any thing specific to be done in the config for this error?
    IDOC has PO  as reference document.
    I looked into several threads in SDN forum but could not find proper solution
    Can any ine help me with this issue?
    Thanks in advance
    Hari

    Hi
    You might be  missing the tax code for uploding through IDOC
    so you can use the t.code we02 and give the doc and find the error
    go to the WE19 to edit the tax  code
    and USE the t.code  BD87  to select the doc and process it
    thanks
    Madhu

  • Invoice Posting using INVOIC02 Idoc for PO and Non-Po based invoices

    Hi All,
      We have a problem regarding posting Invoices using Idocs.
    We have po and non-po invoices coming frm thirdparty in the form of idoc files.
    We need a clarification whether Invoic02 idoc can handle both Po and Non Po Based invoices or threre are seperate idoc types or message types for Po and Non Po Invoices.
    Could any one give some inputs on Partner Profiles also for this senario.
    Please kindly reply as early as possible.
    Regards
    Anil Kumar K

    Hi
      I Got your name from this site.I would be very thankful if you can help me here.I am designing a EDI based invoice LIV.Is it possible to post some charges which are without PO reference but are coming in Vendor Invoices.Is it possible to post these kind of charges with EDI message INOIC01 or we have to post through FI posting.If possible through EDI in which segment of IDOC we will enter these charges with amt.Also is it possible to post credit memo also with EDI
    Thanks
    Sanjeev

  • When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code".

    Hi Experts,
    When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code". As checked, we have configured OBCD and OBCA for the vendor and we are passing the Tax Jurisdiction code in E1EDP04 SAL segment. Can anybody give us some idea to resolve this issue.
    Regards,
    Sameek

    Hi Sameek,
    Please refer the below link. Hope it helps.
    http://scn.sap.com/thread/1435286
    Regards,
    Chandan.

  • Payroll Payment via ALE/IDOC

    Hello Everyone,
    We currently run payroll and process ACH payment information via RFFOUS_T.  The information is sent directly to the bank.  We have a new request which will require HR Payroll payment information to be sent from our SAP system to another SAP system via ALE/IDOC.  Does anyone have any documentation which offers an explanation as to how Payroll processes payment information ALE/IDOC.
    I have found a few references to PC00_M08_CDTA, RFFOEDI1, type PEXR2002/PEXR2003 etc, but nothing that brings it all together.  The process seems to be fairly standard and should be easy to implement (RFC, partner profile, etc). I am ultimately looking for a best practices or some other document which brings everything together and indicates which transactions the user must execute. 
    Thank you for your help.
    Scott

    Hi,
    Please use SAP help link below which gives you idea about ALE connection set-up and IDOC segment usage.
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/CABFAIS/CABFAIS.pdf
    Thanks,
    Ameet

  • BADI for post processing of IDOC BOMORD

    Hi experts ,
    I want a BADI for post processing of IDOC BOMORD. Actually after IDOC processing BOM got updated in system and i want to schedule the explosion of BOM in process order after it. Please update me with the solution.
    Thanks
    Nitin kapoor

    Roberto, thanks for your prompt reply (as always). 
    Actually, it seems that the deletion of the prior infopackage request is performed before executing the infopackage again (not after), I apologize.  I will try your suggestion, though.  If this is actually the correct FM, then I will award you full points!
    I must admit, though, understanding the parameters of the FM are difficult.  Can you aor anyone else provide more details?

  • Send Purchase Order via ALE/IDOCS

    hi,
          How can i send one PO from one client to another via ALE/IDOCS?
          Pls provide few important steps.
    Thanks and Regards,
    Gaurav

    For sending IDOC for Purchase order you will use idoc
    Message type : ORDERS
    Basic Type : ORDERS05
    Create one RFC Destination in SM59 and give that entry in Port in WE21.
    Create Partner profile in WE20 and Port for receiver system in WE21.
    Use your port in Partner profile in WE20.
    In Partner Profile create one entry for Message type ORDERS as Outbound.
    In your tcode when you are creating Purchase order set output message in your header condition for Outbound to send that purchase order to that Partner Profile.
    Check link :
    http://www.****************/Tutorials/ALE/AutoIDOCGen/AutomaticIDocGeneration1.htm
    Regards,
    Sandeep Kaushik

  • Flat-Idocs via the IDOC-adapter

    Hi All,
    I want to send a flat-IDOC via the IDOC Adapter to a SAP R/3 system. The IDOC adapter does not accept flat-IDOC, but wants xml-IDOC. Does anyone know how to send this flat-IDOC to the SAP R/3 via ALE, but without XML-lizing the IDOC?
    I am looking in to the principle of tunneling, but that will involve some ABAP coding.
    Cheers,
    Frank

    Hi Bhavesh,
    I tried, but the IDOC adapter wants XML. The receiver IDOC adapter checks the type of the payload and determines if IDOC tunneling is used or not. I don't know yet how to change the type of the payload:
    <i>method CL_IDX_IDOC_SERVICE-GET_PAYLOAD, part of package SIDOC_ADAPTER
    test if idoc is in tunnel-payload-format
        l_content_type = l_payload->getcontenttype( ).
        IF l_content_type = if_xms_resource=>mimetype_idoc.
          l_idoc_resource ?= l_payload->getdata( ).
          l_tunnel_flag    = 'X'.
        ELSE.</i>
    and with tunneling the idoc must be stored in certain tables where the receiver idoc adapter will get the IDOC instead of the payload. And our flat-idoc is in the actual payload. So the direction I am looking into is an abap mapping, which will change the payload type and stores the flat idoc in these tables, so the idoc adapter is "fooled" to believe it is IDOC tunneling.
    Cheers,
    Frank

  • Posting in Enjoy Screen and Complex Posting Screens

    Hi,
    I want to know the difference of posting in FB60/FB70 enjoy screens and the F-02 complex posting screens. Can someone tell me in what cases i have to use the F-02 screen by explaining a sample business transaction which cannot be posted in FB60 or FB70 but can be posted in F-02.
    Thanks.

    Hi,
    Both F-02 and the enjoy transactions FB60/70 serve the same purpose.  However, enjoy transaction make the entry look more simple and encourage a non functional user to enter correctly without any conflict as to debit/credit.
    In case of F-02, you need to select the posting keys.  These posting keys will define either the transaction needs to be debited or credited.  Though all the tcodes serve the same purpose, the following are the key differences
    1.  F-02 is used for different document types (AB, SA, RE etc.,).  It will be used for accounting as well as AP/AR entries if required.
    2.  In F-02, the posting keys define the document type.  For eg., if you use KN as the document type, you need to use posting key 21 or 31 to allow the system to enter the vendor code.  However, in case of FB60/70, you just need to select if the entry is a invoice or a credit memo and the credit and debit is already identified in the screen.
    3.  FB60/70 is more easier and exhaustive for the accountants to enter the data.  F-02 may not be useful in day to day entry of invoices.

  • Regarding Posting Date in IDOC for Intercompany Invoice

    Hi,
    We have priority issue regarding posting date in IDOC. When we create Intercompany invoice, billing date in intercompany is Actual GI date of delivery document and also Invoice posted with Actual GI date only. But, in IDOC, Posting date is appearing as Planned GI date of delivery document.
    Actual GI date and Billing date and Posting date in IDOC should be same., but, posting date in IDOC is appearing as Planned GI date of delivery doc.
    Kindly help in finding out the root cause of, why posting date in IDOC is not appearing as Billing date and appearing as Planned GI date of Delivery document. This issue is happening from past one month for Intercompany invoice, previously posting date in IDOC used to appear as Billing date only.
    Thanks & Regards,
    Jai Prabhu.

    Hi Jai,
    Are you using standard message type INVOIC ?
    If so check SEGMENT E1EDK02 for date field
    and also check if there is no code put to overwrite the date
    you can check the code in Function module  "IDOC_OUTPUT_INVOIC"
    thanks
    santosh

Maybe you are looking for