Is it possible to generate outbound idocs for FI invoices? How?

Is it possible to generate Outbound idocs for FI invoices? How? or else i have to write program to get data in file and pass it to translator. Please help.

Dear Gabriel
Before letting you know the possibility, can you please let me know why you want such a requirement, since standard has not provided such copy control, to my knowledge.
As you would know order type KB is for consignment fillup where you are just transferring the goods from FG unrestricted to your own warehouse and that is why in standard you can see the copy control KB --> F8 which means you can raise proforma against delivery and not against fillup order.
So think of whether really you wanted to raise proforma against fillup order which is NOT recommended by SAP.  However, still if you feel that the requirement is so to have, you can make the settings in VTFA.
thanks
G. Lakshmipathi

Similar Messages

  • Generate outbound idoc for Customer Master

    Hi Developers,
    I have requirement to generate outbound IDOC for Customer Master Data. I need to send customer master data through an Outbound IDOC. Can we generate an outbound DEBMAS06 idoc? Can someone help me finding a solution to this problem?
    Thanks in advance for helping.
    Regards,
    Gajendra

    Hi,
    If you have done all the required settings (logical system, partner profiles, distribution model), then either transaction BD10 / BD14 will help you generate the IDOC.
    If you want to send the idocs automatically, then you will to configure some program.
    Unlike transaction data, Master data IDOCS are not triggered immediately, you will have to do the required configuration in SPRO.
    Transaction SPRO
    SAP Customizing Implementation Guide -->
    SAP Web application Server --> Application Link Enabling --> Modeling and Implementing Business Processes -->
    Master Data distribution --> Replication of Modified Data --> Creating IDOCS from Change Pointers
    Take a look at this thread.
    Re: automatic Idoc outbound
    Regards,
    Ravi
    Note : Please mark the helpful answers
    Message was edited by: Ravikumar Allampallam

  • Function Module to Generate Outbound IDOC for Sales Documents

    Hello Experts,
    Can someone please help me, I need to know which function module to use in order to generate the outbound IDOC for sales documents.  Some of the fm's I have come across are the following:
    IDOC_OUTPUT_ORDERS, but actually for Purchase Orders
    IDOC_OUTPUT_ORDRSP, but did not generate any IDocs for my sample Sales Order.
    Points will be given for any help provided.
    Thanks in advance.

    Hi Nagaraj,
    I tried using the IDOC_OUTPUT_ORDERS but I keep getting an error that the Purchase Order <xxx> does not exist, even though the document I tried is a sales order.  For everyone's reference here is the code:
    form process_data.
      DATA v_idoc       TYPE edidc-docnum.
      DATA i_edidd      TYPE TABLE OF edidd.
      DATA wa_idoc_ctrl TYPE edidc.
      LOOP AT i_nast INTO wa_nast.
        CLEAR i_msgs[].
        CALL FUNCTION 'WFMC_PROTOCOL_GET'
          EXPORTING
            cps_nast        = wa_nast
          tables
            messages        = i_msgs
         EXCEPTIONS
           NOT_FOUND       = 1
           OTHERS          = 2.
        LOOP AT i_msgs INTO wa_msgs WHERE arbgb EQ 'E0'.
    *--- Check first if there is an IDOC
          IF wa_msgs-msgv1 IS INITIAL.
            CONTINUE.
          ENDIF.
          v_idoc = wa_msgs-msgv1.
          CLEAR i_edidd[].
          CLEAR wa_idoc_ctrl.
          CALL FUNCTION 'IDOC_READ_COMPLETELY'
            EXPORTING
              document_number                = v_idoc
            IMPORTING
              IDOC_CONTROL                   = wa_idoc_ctrl
    *         NUMBER_OF_DATA_RECORDS         =
    *         NUMBER_OF_STATUS_RECORDS       =
            TABLES
    *         INT_EDIDS                      =
              INT_EDIDD                      = i_edidd
            EXCEPTIONS
    *         DOCUMENT_NOT_EXIST             = 1
    *         DOCUMENT_NUMBER_INVALID        = 2
              OTHERS                         = 3.
          CALL FUNCTION 'IDOC_OUTPUT_ORDERS'
            EXPORTING
              object                              = wa_nast
              control_record_in                   = wa_idoc_ctrl
    *       IMPORTING
    *         OBJECT_TYPE                         =
    *         CONTROL_RECORD_OUT                  =
            tables
              int_edidd                           = i_edidd
    *       EXCEPTIONS
    *         ERROR_MESSAGE_RECEIVED              = 1
    *         DATA_NOT_RELEVANT_FOR_SENDING       = 2
    *         OTHERS                              = 3
          IF sy-subrc <> 0.
    * MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    *         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
          ENDIF.
          COMMIT WORK.
        ENDLOOP.
      ENDLOOP.

  • Help required on OutBound IDoc for FI Invoices

    Hi All,
    I had a requirement to create a custom idoc for FI invoices via a user exit and these idocs will be routed (via RFC) to a JAVA server/processor. Pls suggest how can i acheive this.
    Is there any user exit for acheiveing this or can we proceed further without user exit also.
    If so how to acheive this.
    Thanks & Regards,
    Anil.

    One option that immediately pops up is
    Using Output Types: like for example transaction V/40
    Application: V3 Billing
    You can define a unique output type : ZINV
    Transmission Medium : 6
    Processing Routine
    Program:         RSNASTED
    Form Routine:    EDI_PROCESSING
    You can then use WE20, and define a unique customer / and map message control (ZINV) information in outbound parameters.

  • How to generate Outbound idoc for Material Reservation

    Hi Experts,
    I want to send outbound IDoc when a material reservation is created with tcode MB21.
    I have been working on this issue and finding the solution in SCN for a week...
    I found some messages similar to this but I could not find out the correct way how to do that.
    At this moment, I configured BD64/WE20 referring the following topic which seems to be feasible solution but could not find any outbound IDocs created, unfortunately.
    Implement ALE_RESERVATION_CREATE
    I appreciate if someone can help me how to create outbound IDoc with MB21 or advice some possibility of missing configuration or steps.
    Best Regards,
    Kenji

    Hi;
    Have been able to find the solution to create the IDoc MRESCR after entering a reservation? 
    I am in the same situation and I do not see the IDoc output in the BD87. 
    It would be nice if you share the solution.
    Thanks in advance

  • How to generate an outbound IDOC for customer Invoice

    Hi
    I want to configure that if I create a invoice using TCODE FB70 it should automatically create a outbound IDOC ACC_BILLING( for customer).How I can achieve this. Can any one give me complete step by step help.
    thanks in advance.
    karunb

    You should be able to use it using 'change pointers'.
    For this you will first need to activate change pointer for this message type (check SALE > modelling..>Master data distribution). Next, you will need to setup your ALE config for this IDOC/message type.
    In ALE, you will be able to either run a standard SAP report adhoc, or schedule it such that all changes recorded using change pointer (changes including new customerr records) are collected as IDOCs and sent.
    This is a standard SAP scenario, you only need to do the config/setup to get there. You may wish to read more on change pointers to understand this.
    cheers,

  • If output type is missing in PO, can system create a Outbound IDOC for that

    Hi
    Scenario: sales order should get generated in anoter system once PO is saved in first system. But this is not happening for a new vendor. I checked & found that output type is missing in PO. Asked user to provide  another PO for which SO was created. I checked that PO, here also output type is missing.
    I am surprised that if output type is missing in PO, can system create a Outbound IDOC for that PO? If yes then I am not aware of this process.
    Please help me in analyzing this problem.
    Regards
    Sapmm12

    Hi Sridhar,
    Thanks for your replay.
    I checked for other vendor also. condition records does not exist in NACE  for any of them. But user is claiming that sales aorder is getting created for those PO. Though I have asked them to provide the sales order number & possibly outbound IDOC number for at least one vendor.
    I tried to search IDOC number with reference to PO number but system is taking too much time & ending with run ime error. Because I do not have details of partner, receiver not even message type. Neither I have any process document which can explain how this process works?
    any other approach which may work here?
    Regards
    sapmm12

  • Outbound IDOC for Article Master in WPMA without Price

    Hi,
    How to Generate an Outbound IDOC for  Article Master in WPMA Tcode without maintaing Price for the Article. Please suggest Is it Possible in IS-Retail. If so, what needs to be Done.
    Regards,
    Selvakumar. M

    Hi Selvan
    In patner profile of outbound, Assign WP_PLU01 instead WP_PLU03..
    This will solve ur problem
    Regards
    Vijai Jain

  • Generating an IDOC for Message type PROJECT in Change pointer?

    Hi,
    I am trying to generate an IDOC. for the Message Type PROJECT(Actually this msg. type PROJECT is for BAPI method) in CHANGE POINTERS but it is possible Error is coming, is there any other method to use the message type in change pointer technic.
    Thanks,
    Vinayak,
    Message was edited by: vinayaga sundaram

    Hi Vinay,
    Had a similar requirement few days back..
    What we did was to do a multimapping of 1:N where N = N1 and N2, N1 is the Idocs which you are doing today, N2 is the set of invalid records...
    Now we have written this as a file and then created another interface which will pick the file and based on the name of file we decided the To address. We have used mail package and this interface (file to mail ) was made as a generic one so that it can be used across many interfaces...
    filename and To address relationship was maintained as a value mapping in ID... You can have a thought of this approach and try to send the invalid records as a mail rather than alert.
    Regards
    Suraj

  • Regarding Outbound IDOC for Goods Receipt with MBGMCR03

    Hi Experts,
    Please let me know ,how to handle TYPE QUANT fields when i am generating an Outbound IDOC for Goods receipt for message type MBGMCR with the IDOC type MBGMCR03.
    At item level when passing the value for quantity received field ,the QUAN value into NUMC or CHAR before MASTER_IDOC_DISTRIBUTE to pass it to data record it is showing correctly in my BADI .
    after generating the idoc , the field value is appended with next field value passed.
    before generating IDOC
    erfmg( 60.000) - ENTRY_QTY(060)
    efrme (EA)       - ENTRY-UOM(EA)
    after generating IDOC
    IN WE02
    ENTRY_QTY-060EA
    later field values are mismatching .
    Please let me know the resolution.
    Thanks & regards
    Vishnu

    Hi,
         Standard Idoc types for invoice is  INVOIC01 and INVOIC02.
    - Use WE30 for seeing Idoc types with segment.
    Or otherwise go for Custom Idoc
               Create Custom Idoc type with required fields,custom output type and assign it to partner profiles.(If there is no std idoc type or output type)
              Use Funtion module MASTER_IDOC_DISTRIBUTE to generate Idocs while saving MIRO, for this you need to find exit or implement implicit enhancement while saving MIRO.
    http://wiki.sdn.sap.com/wiki/display/ABAP/StepstocreatecustomIDOC - Creating Custom idocs

  • Outbound IDoc for Goods Movement

    HI
    We need to generate XML files for goods movement posted in SAP at Goods Receipt (MIGO) and Post Goods Issue (VL02N). Requirement is asynchronous update where the receiving system will poll the xml file at the end of the day.
    I have not been able to find any standard outbound idoc for goods movement.Can someone advise how they tackled any similar requirement? Any other approach also appreciated.
    Thanks
    Sriram

    Answer to the question, which would be useful to all.
    <b>MIGO</b>
    MB_CF001 - Customer Function Exit in the Case of Updating a Mat. Doc.
    This exit is called on update task, populate segments (edidc & edidd) of WMMBID02 (WMMBXY message type) and use MASTER_IDOC_DISTRIBUTE. Also you need to maintain the ALE Distribution model in WE64 for this message type.
    Inside the code you can restrict based on movement type. No need to issue COMMIT.
    <b>VL02N</b>
    You can use BAdi: LE_SHP_DELIVERY_PROC to perform this.
    Create Implementation and use the method SAVE_AND_PUBLISH_DOCUMENT.
    Hope this help to others as well.

  • Outbound IDoc for AR Correspondence (Credit/Debit Memo)

    We currently use the Print Correspondence function to generate automatic correspondence. In transaction OB78 we have each correspondence type linked to a print program which generates a .pdf "AR Invoice" via SAPScript.
    Our new requirement is to generate an Outbound IDoc for the same miscellaneous AR Correspondence output. There does not seem to be any configuration means by which to generate an IDoc for these financial documents. Enhancement RFKORIEX only allows for fax or email.
    Please advise how to generate IDoc via configuration without extensive coding.

    We currently use the Print Correspondence function to generate automatic correspondence. In transaction OB78 we have each correspondence type linked to a print program which generates a .pdf "AR Invoice" via SAPScript.
    Our new requirement is to generate an Outbound IDoc for the same miscellaneous AR Correspondence output. There does not seem to be any configuration means by which to generate an IDoc for these financial documents. Enhancement RFKORIEX only allows for fax or email.
    Please advise how to generate IDoc via configuration without extensive coding.

  • How to create outbound IDOC for Accounting document type RV

    Hello All,
    We have a requirement to create a downpayment request for a customer. We have copied the FAZ billing type and created a ZFAZ. For this the accounting document type generated is RV. This RV is a statistical document and does not contain any debits and credit entries. It is just to inform the customer to pay. We have to generate an IDOC for the same. I have configured FIDCC1 standard FI message type for this in ALE. But it does not seem to work.
    Does anyone have any inputs on this ? May be RV does not use the message type FIDCC1 ? Anything in relation to RV or downpaymnts, please let me know..
    Appreciate your responses.
    Thanks
    SH.

    Hello Alpesh,
    I tried adding breakpoints to the following userexits and many other places where they occur..but while creating billing doc FAZ nor while generating accounting document RV they were triggered.
    I have created a distribution model and created the partner profile with outbound for basic type INVOIC02 for message type INVOIC . What do you say?
    Just a note that this is an outbound process and i cannot use process codes.
    - EXIT_SAPLVEDF_001 User_Exit controll data IDoc_Output_Invoic
    - EXIT_SAPLVEDF_002 User_Exit customer enhancement of segments outbound invoice
    Thanks
    Smitha
    Edited by: Smitha H on Jul 25, 2008 7:56 AM

  • Trying to change Inbound IDOC to Outbound IDOC for testing....

    Hi Friends,
    I am trying to do the following
    1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
    2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
    3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
    4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
    HELP!! Rewards

    Hi Friend,
            The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
    Use
    You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an “empty” IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
    You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
    Activities
    ·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
    You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the “file“ type. The default file is the inbound file entered there.
    ·        You generate the IDoc using .
    The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
    ·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
    You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
    ·        Click on the white fields to change data in the segments.
    In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
    In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
    ·        The additional procedure depends on whether you want to test inbound or outbound processing.
    Test: Outbound Processing from MC
    Use
    Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
    Prerequisites
    You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
    ·        Customer or vendor records
    ·        Material records
    ·        Info records
    ·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as “messages” from the respective application.
    The appropriate file ports and partner profiles must exist in the IDoc Interface.
    Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to “1” (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
    Activities
    Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
    Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to “Collect IDocs” in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode “Collect IDocs” in live operation.
    Activities
    You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
    You can decide whether the output mode is set to “Start subsystem” or “Do not start subsystem” in the partner profile. This defines whether the external (sub) system processes the IDocs further.
    Use
    This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to “File”.
    Prerequisites
    A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are “credited” to the relevant IDoc in the form of status records in the SAP System.
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
    Test: Inbound Processing: Modified Outbound File
    Use
    This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to “File”.
    Prerequisites
    You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type “File” must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
    Standard inbound processing is then triggered;
    ·        Reading the modified file
    ·        Generating the IDoc(s) in the SAP System
    ·        Processing in the application
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
    Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
    The recipient in this case is the SAP System. The port is used for identification purposes:
    ·        SAP (for example RSMITH
    Test: Inbound Processing: Original Inbound File
    Use
    This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
    Prerequisites
    You require a correct inbound file. In this case, correct means that the:
    ·        Sender and recipient in the control record are correct
    ·        Direction in the control record is set to 2 (inbound)
    ·        Client in the control record and data records are correct or empty
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
    The file is deleted after being read successfully!
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
    ·        Inbound port
    ·        Name and directory of the file
    These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
    Thanks

  • How do i generate the idoc for the custom infotype?

    Hi Experts,
        I have a requirement to create the custom infotype and generate the idoc for the custom infotype
        whenever the user change or crate the data by PA30, PA40 transaction .
    so please give some help to write a logic for generate the idoc?
    Thanks in advance.
    Venkat

    I have just found out from the Archives, it is not possible to generate a formula line (trend line) in Numbers_08.
    I am currently upgrading to Numbers_09.

Maybe you are looking for