IBD  BASED INVOICE THROUGH EDI

DEAR EXPERTS,
I'M HAVING A SCENARIO WHEREIN MY CLIENT IS IMPORTING SOME GOODS AND THE GOODS ARE VERIFIED AT VENDOR'S SITE BY ONE OF OUR CLIENT'S PERSON AND THE PERSON CREATES A INBOUND DELIVERY IN SAP AND THEN THE GOODS ARE SHIPPED. BASED ON THE IBD MY CLIENT WANTS TO MAKE A PAYMENT OF 60% AND REMAINING 40% AFTER DOING THE GR. HERE THE ISSUE IS I'M NOT ABLE TO DO INVOICE POSTING BASED ON IBD OR WHEN I SELECT THE PO FOR POSTING THE INVOICE, i.e BEFORE DOING GR NEITHER THE QUANTITY OR VALUE COMES IN THE INVOICE WE NEED TO ENTER IT MANUALLY. THERE ARE 100'S OF MATERIAL IN A PO AND IT IS PRACTICALLY DIFFICULT TO ENTER THE QUANTITY AND VALUE MANUALLY. PLEASE DO SUGEST HOW WE CAN POST AN INVOICE BASED ON IBD.
ONE OF OUR FRIENDS IN FORUM SUGGESTED TO USE EDI FOR INVOICE. CAN ANYONE EXPLAIN IN DETAIL HOW TO DO INVOICE THRU EDI BASED ON IBD.
THANKS & REGARDS
DOMINIC RAJAN

Hi Satyamurthy,
                        First you define an output type like "ZEDI". Maintain the Access sequences for it.Now insert this Output type in the output determination procedure. Now assign this procedure to the billing document type(This must have been done already). Now maintain the condition record for appropriate access with medium as "6" and date"4" and the language . And now go to "WE20" and select partner type "KU" and copy an already maintained one. Here you have to be very careful when selecting a message type and process code. Normally the message type would be "INVOIC". Partner  function should be "BP"(Same as what you have maintained in the record).Get the details from the business or development team about the port(WE21-- To Maintain a port. This will be done by Technical people).And insert basic type, select option  Transfer IDoc immediately and now go to Message control and  maintain the Application as"V3" ,Message type "ZEDI(or what ever outouy type you had chosen) and process code.(This is important.You can take abap'ers help while selecting this as this is associated to a function module. I think this should help you.
Regards
Ram Pedarla

Similar Messages

  • Invoice through EDI

    HI,
        Can anybody let me know how the invoice(MIRO) get generated when vendor send an invoice through EDI. Is there any Job which creates the invoice using the IDOC.
    Can anybody let me know the process flow and if possible transaction codes also.
    Points will be awarded.
    Regards,
    Shree.j

    Hi ,
    Please refer the below link:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/2d/b12d3b1daca008e10000000a114084/frameset.htm
    Please assign points as way to say thanks
    Ravi

  • Incoming invoice through EDI

    Hi everyone,
    How to configure incoming vendor invoice using edi
    Thanks
    Genie

    Hi ,
    Please refer the below link:
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/135b0b94-0701-0010-f6a9-86a14057544a
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/2d/b12d3b1daca008e10000000a114084/frameset.htm
    Please assign points as way to say thanks
    Ravi

  • Split the posting amount while creating invoice through EDI.

    Hi All,
    We receive invoice via an IDOC and is processed using function moudle INPUT_IDOC_INVOICE_MRM. When the invoice gets created and the amounts get posted. In the accounting document that got created, I need to split the amount to specific accounts.
    Does anyone have an idea about the solution that could be used?
    Thanks in advance. Points after the replies.
    Regards,
    Ashutosh.

    Hello Ashutosh
    For Logistics Invoice verification the accounts are determined by account determination configuration set in your system...
    Please check with your MM/Fi consultant. Please chk transactions like OBYC .. should give you an idea...
    Regards,
    Arun

  • GR BASED INVOICE

    hi sir,
    can i maintain gr based invoice through Scduling agreement like purchase order NB.it is possible or not

    Hi,
    You can use the GR Based IV check box in Scheduling agreement or PO.
    The features of both these documents are almost similar except some.
    You have 2 options
    1) In the Vendor master creation in XK01/Xk02
    2) In Purchase info record ME11/ME12
    If you had maintained here system will default the same in the Scheduling agreement whether it is NB or customized document type.
    rgds
    gsc

  • EDI - Incoming Invoice Error and GR based Invoice Verification - 51 No GR

    Hi,
    We are implementing EDI for incoming invoices and use Goods Receipts based Invoice Verification.  When processing an inbound IDOC Invoice (type INVOIC01) where the Goods Receipt has not yet been posted, then Inbound IDOC is siiting at Error Status, 51 - No GR documents found.
    Is there any way we can process this as a Parked Invoice or for Verification in the background (MIRA)?  because the current situation is a problem, as 95% of our Inbound Invoices will be received electronically before the Goods are Received. 
    The actual Vendor's delivery note is stored in the segment E1EDP02 (Qualifier 016), field BELNR.
    Currently the IDOC as to sit in error until the Vendor's Delivery Note is Goods Receipted which can be several days later - SAP OSS Note 393883 fro 2001 suggests doing this, but surely this is a common situation.  The IDOC sitting in error in WE02 in the list of IDOCs is difficult to isolate from true errors.
    If this is was mnaul Invoice it could be processed through MIRA for background Invoice Verification later with program RMBABG00.
    We havd SAP version ECC 6.0
    I have spotted OSS Note 501524 which implies that is possible automatically Park Incoming EDI IDOC Invoices, has anyone tried this?  and what would be the transaction/program that could be used to post several at once when the GR has been processed (similar to RMBABG00)

    Hi ,
    You can use the program   RBDMANI2   which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
    We had the same scenario and we have scheduled this program as a daily job at night .
    Regards,
    Hari.

  • Non PO Charges through EDI Incoming Invoice

    Hi
    I would be very thankful if somebody can answers these questions. I am designing EDI based invoice LIV.
    1) Is it possible to post some charges in invoice which are without PO reference.Is it possible to post these kind of charges with EDI message INVOIC01 or we have to post through FI posting.? or we need to use INVOIC02
    2) If possible through EDI in which segment of IDOC we will enter these charges with amt I am not able to find out the segment I tried in EIEDP01 but failed
    3)Also is it possible to post credit memo also with EDI?
    Thanks
    [email protected]

    try out with segment E1EDP05.

  • Urgent :Accounts Payabale Invoice automation  through EDI

    Hi All,
    Through EDI, We would like to automate <b>accounts Payable Invoice in SAP</b>.
    Kindly provide me the following details to create partner profile for this automation
    <b>1. Which Partner type ( Customer / Vendor / User / etc.,) to be used
    2.Which Partner function to be used
    3.Which Message type to be used
    4. Which Process code to be used</b>
    Apart from the above process, any other settings are to be done for accounts Payable EDI automation.
    Points will be rewarded.
    Thanks & Regards,
    A. Raja

    Hi,
    You can use invoic message type of IDOc for needed processing .& IDoc type will be either INVOIC01/INVOIC02.
    Please provide additional details of trnasctions you would like to automate that will be helpful to provide further info.
    Thanks.
    Mark points if helpful.

  • Invoice BLOCK & HOLD through EDI Processing

    Hi SAP Gurus,
    Can you please let me know as to how to BLOCK & HOLD Invoices while processing through EDI.
    Regards,
    Yasir

    Hi ,
    You can use the program   RBDMANI2   which will reprocess all the IDOCs (EDIinvoices )that have failed . You can schedule this program in the background and it will post all failed invoices which have the GR posted later .
    We had the same scenario and we have scheduled this program as a daily job at night .
    Regards,
    Hari.

  • 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

  • Re : Inter company stock transfer through EDI

    Hi
          How to do the intercompany stock transfer through EDI. In this if Purchase order is created from one comapny a sales order should created automaticall in another Company. Fot this what is the SPRO settings.
    How to do this.
    Thanks
    Anto

    Hi,
    continues from here,
    Inbound file:     edi_in
    Function module:     See text below.
    Status file parameters
    Directory:     /home/edi/<portname>/
    Outbound file:     status.idoc
    Function module:     Leave blank if using above
    u2022     Both the portname and the exchange directory should be created according to the same naming convention. However, the portname should be in upper case whereas the corresponding directory name should be in lower case (see examples below).
         Portname (upper case):
                             <portname>
         Exchange directory name (lower case):           
                             /home/edi/<portname>
         where <portname> consists of:
         EDI<system name><client number><id char>
         <system name> is the name of  system on which port exists eg.      F01, PG1 etc.;
         <client number> is name of client on system which will use this      port; and
         <id char> is a single alphabetical character such as u2018au2019,u2019bu2019 etc.      typically,      u2018au2019 will denote dynamic outbound file naming (used      for testing) whereas      u2018bu2019 will denote static outbound file naming.      All ports will use static       inbound filenames.
    For example, the name of a port using dynamic file naming on system F01, client 610 would be named EDIF01610A.  The exchange directory would be named edif01610a. Similarly, the name of port using static file naming on system PG1, client 600 would be EDIPG1600B. The exchange directory name would be edipg1600b.
    Note that the function u201CEDI_PATH_CREATE_USERNAME_DT_TMu201D  can be used in the u201CFunction moduleu201D field  of the Outbound file parameters if IDocs are to be written to multiple files. In this case, the corresponding outbound filename field should be left blank. The standard IDoc exchange interface between the SAP EDI component and the EDI subsystem uses a single file for each transfer direction. However, should the exchange interface change, or for testing purposes, the function modules for dynamic naming can be used.
    2.4.2.     Control of EDI processes in R/3
    2.4.2.1.      Maintain: Outbound Process Code (WE41)
    IMGCross-Application ComponentsALE Extensions  Outbound
    Check that the outbound EDI processes in the R/3 system are defined.  Indicates which ABAP/4 function module to execute in order to create an outbound IDoc.
    The following assignments are available for R/3:
    2.4.2.2.      Maintain: Inbound Process Code (WE42)
    IMGCross-Application Components  ALE  Extensions  Inbound
    Check that the inbound EDI processes in the R/3 system are defined.  Indicates what kind of inbound processing to execute.
         A long list of options is available under Processing by function module, relevant ones are:
    INVF     INVOIC FI     Invoice receipt (Financial Accounting)
    INVM     INVOIC MM     Invoice verification (Mat Management)
    ORDC     ORDCHG     Change customer order
    ORDE     ORDERS     Create customer order
    ORDR     ORDRSP     Purchase order confirmation
    2.4.2.3.      Control: System Process Codes (WE40)
         Choose Processing by task.  Check that the codes indicating the type of EDI processing error are defined.  The only valid entries are the entries shown on the screen, as they are directly called via the EDI basis module.
    2.4.2.4.      Control: Status maintenance (WE47)
         Check that the codes indicating status of IDoc processing are defined.  The status values for outbound IDocs are between 01 and 39, while the status values for inbound IDocs begin with 50.  These values are delivered by SAP and cannot be customised.
    2.4.2.5.      Control: Partner Types (WE44)
         Check that the codes that identify the commercial relationships between the receiver and sender are defined.  Values are delivered by SAP.  Names of the programs and routines that validates the entry of the EDI trading partner ID:
    Partner type     Report name     Form routine
    B - Bank     RFETESTP     READ_T012
    KU - customer     RSETESTP     READ_KNA1
    LI - vendors     RSETESTP     READ_LFA1
    LS - logical system ( ALE)     RSETESTP     LOGSYS
    2.4.2.6.      Control: Forward Inbound (WE45)
    Allows for the forwarding of IDocs to a specific application.  Contains the exactly defined destination of an inbound IDoc within the SAP system.  Usually no changes are required.
    2.4.2.7.      Control: Status Process code (WE56)
    Choose Processing by task: The following set-up has been provided as default:
    Process code:     EDIS
    Identification:     TS30000078
    Description:     EDI-IDoc  status record processing
    The process code is for inbound status, The ID type is an identification code for inbound processing method (workflow or standard task) of the status record.
    3.     MM IMG CONFIGURATION
    3.1.     Global settings (IMG):
    3.1.1.     Units of measure (IMG  Global settings):
    The ISO code is important for EDI.  It is used to convert the internal SAP units of measure into standard units.
    The MM configurer must link the Unit Of Measure, EACH, with the ISO code PCE (Piece).
    3.2.     Link Schema to Purchase order
    Check the following:
    IMG  MM  Purchasing  Message determination  Message determination  Message Schemas
    Execute transaction u201CDefine Message Schemas for Purchase Orderu201D
    Select  transaction: Assign Schema to purchase order
    Add:      Usage =B for output
         Application = EF for purchase order
         Procedure = RMBEF1 for purchase order
    3.3.     Link application to EDI interface via message control:
    IMG  MM  Purchasing  Messages  Output Control
    Check following under Output Control:
         Condition table
         Access sequence
         Message types
         Message schema
         Output control
    3.4.     Enabling Multiple Output for Purchase Orders (Optional)
    For example: EDI & Printing
    IMG  MM  Purchasing  Message determination  Message determination Access sequence
    u2022     Create new access sequence (e.g. ZPUR), copy the access sequence 0001 but leaving the ''E'' flag blank (Exclusive is off). (Transaction M/50)
    u2022     Goto Define message types  maintain message types:
         Create a new message type (e.g. NEU1), setting the output type to 1 for printed output and using ZPUR as access sequence. (Transaction M/34)
    u2022     Goto Message Schema  define message schema  maintain output determination procedure:
         Update procedure RMBEF1 by adding a step for the new condition type (e.g. NEU1) prior to the standard delivered step for NEU. (Transaction M/36)
    u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
         - Add a NEU1 record to table TNAPR.  The program FORM Routine and layout must be specified.  (Copy an existing NEU record). (Transaction OMTB)
    u2022     Goto Processing program  Define Processing program  Output by partner type.
         - Add NEU1 record for VN (vendor). (Transaction OMTG)
    3.5.     Link Output type (fax=2, E-mail=7) to NEU (Purchasing)
    IMG  MM  Purchasing  Message determination  Message determination Access sequence
    u2022     Goto Processing program  Define Processing program  Output program: Purchase Order.
         - Add another NEU record to table TNAPR with the appropriate output medium. Copy an existing NEU record. (Transaction OMTB)
    u2022     Goto Processing program  Define Processing program  Output by partner type.
         - Add NEU record for VN (vendor). (Transaction OMTG)
    4.     SD APPLICATION REQUIREMENTS
    Assumption: SD is only used for testing purposes and configuration is based on a need basis - only configure the minimum.
    Reference SAP Course manual Chapter 11.
    4.1.     EDI Configurations
    4.1.1.     Conversion of SAP item categories to IDOC item categories (VOE1)
    IMG  S&D  EDI  EDI Messages  Conversion of SAP item categories to IDOC item categories
    Add the following entry:
    For Standard Item description :     0     OR     LDN
    Typically error message: ''Transaction LDN is not defined".
    4.1.2.     Partner functions
    IMG  S&D  EDI  EDI Messages  Configure EDI Partners Partner  Application  Partner function
    Check that the following partner functions exist: (at least)
    SP     Sold-to party
    VN     Vendor
    BP     Bill-to party
    SH     Ship-to party
    Note - the German abbreviation is passed to the IDoc.
    4.2.     S&D Sales Configurations
    4.2.1.     Maintain Item categories
    IMG  S&D  Sales  Sales document  Sales doc item  Define item categories
    Add LDN for standard item:
              Item type = B
              Relev for billing = B
              Tick following:     Bus data item
                                  Sched line allowed
                                  Credit active
                                  Pricing
              Screen seq. grp = N
    4.2.2.     Assign Item categories
    IMG  S&D  Sales  Sales document  Sales doc item  Assign item categories
    Add/Update the following entries:
         1     2     3
    Sales doc type     OR     OR     OR
    Item category group     NORM     DIEN     LEIS
    Item category     LDN     TAD
    LDN     LDN
    4.2.3.     Assign Schedule line categories
    IMG  S&D  Sales  Sales document  Schedule lines  Assign Schedule line categories
    Add Item category LDN to table (with no other parameters).
    4.3.     S&D Pricing Configurations
    4.3.1.     EDI pricing condition types
    IMG  S&D  Basic functions  Pricing  Pricing control  Define condition types  Maintain condition types
    Maintain the following condition types:
         EDI 1 - Calculate type =C for Quantity
         EDI 2 - Calculate type = B for Fixed amount
    4.3.2.     SD Pricing procedures (V/08)
    IMG  S&D  Basic functions  Pricing  Pricing control  Define & Assign pricing procedures
    Maintain pricing procedure for ZVAA01 (Standard). 
    Select control and add EDI1 and EDI2  as steps 1 and 5 respectively with no other parameters.
    5.     INVOICE IMG CONFIGURATION
    No additional IMG configuration (not partner specific) was needed for Inbound Invoice processing.
    Thanks,
    Swamy H P

  • Unable to Change Withholding Tax Base Amount while creating Service AP Invoice through DI API?

    Dear All,
    I am trying to create Service AP Invoice through DI API.
    If I post the document without changing SAPPurchaseInvoice.WithholdingTaxData.TaxableAmount the dount ocument is created in SAP without any problem.
    But if I change amount in above field then DI API throws error Unbalanced Transaction.
    If I post same document in SAP with changed base amount it got posted in SAP without any Issue.
    Where I am doing wrong?
    please guide.
    Using:
    SAP B1 version 9 Patch Level 11
    Location : India.
    Thanks.

    Hi ,
    maybe you can find solution to these note 1812344
    1846344  - Overview Note for SAP Business One 8.82 PL12
    Symptom
    This SAP Note contains collective information related to upgrades to SAP Business One 8.82 Patch Level 12 (B1 8.82 PL12) from previous SAP Business One releases.
    In order to receive information about delivered patches via email or RSS, please use the upper right subscription options on http://service.sap.com/~sapidp/011000358700001458732008E
    Solution
    Patch installation options:
    SAP Business One 8.82 PL12 can be installed directly on previous patches of SAP Business One 8.82
    You can upgrade your SAP Business One to 8.82PL12 from all patches of the following versions:8.81; 8.8; 2007 A SP01; 2007 A SP00; 2007 B SP00; 2005 A SP01; 2005 B
    Patch content:
    SAP Business One 8.82 PL12 includes all corrections from previous patches for releases 8.82, 8.81, 8.8, 2007, and 2005.
    For details about the contained corrections, please see the SAP Notes listed in the References section.
    Notes: SAP Business One 8.82 PL12 contains B1if version 1.17.5
    Patch download:
    Open http://service.sap.com/sbo-swcenter -> SAP Business One Products -> Updates -> SAP Business One 8.8 -> SAP BUSINESS ONE 8.82 -> Comprised Software Component Versions -> SAP BUSINESS ONE 8.82 -> Win32 -> Downloads tab
    Header Data
    Released On
    02.05.2013 02:34:18  
    Release Status
    Released for Customer  
    Component
    SBO-BC-UPG Upgrade  
    Priority
      Recommendations/additional info  
    Category
      Upgrade information  
    References
    This document refers to:
      SAP Business One Notes
    1482452
    IN_Wrong tax amount was created for some items in the invoice with Excisable BOM item involves
    1650289
    Printing Inventory Posting List for huge amount of data
    1678528
    Withholding amount in the first row is zeroed.
    1754529
    Error Message When Running Pick and Pack Manager
    1756263
    Open Items List shuts down on out of memory
    1757641
    Year-end closing
    1757690
    SEPA File Formats - New Pain Versions
    1757898
    Incoming Bank File Format
    1757904
    Outgoing Bank File Format
    1762860
    Incorrect weight calculation when Automatic Availability Check is on
    1770690
    Pro Forma Invoice
    1776948
    Calendar columns are wrong when working with Group View
    1780460
    OINM column description is not translated
    1780486
    UI_System crash when you set extreme value of double type to DataTable column
    1788256
    Incorrect User-Defined Field displayed in a Stock Transfer Request
    1788372
    ZH: 'Unacceptable Field' when export document to word
    1788818
    RU loc: No freight in the Tax Invoice layout
    1790404
    Cash Flow Inconsistency when Canceling Payment
    1791295
    B1info property of UI API AddonsInstaller object returns NULL value
    1791416
    Adding a new item to BoM is slow
    1794111
    Text is overlapping in specific localization
    1795595
    Change log for item group shows current system date in all the "Created" fields
    1797292
    Queries in alerts should support more query results
    1800055
    B1if_ Line break issue in inbound retrieval using JDBC
    1802580
    Add Journal Voucher to General Ledger report
    1803586
    Not realized payment is exported via Payment Engine using 'SAPBPDEOPBT_DTAUS' file format
    1803751
    Period indicator of document series can be changed although it has been used
    1804340
    LOC_BR_Cannot update Nota Fiscal Model
    1805554
    G/L Account displayed in a wrong position when unticking the checkbox "Account with Balance of Zero"
    1806576
    Payment Cannot Be Reconciled Internally
    1807611
    Cannot update UDF in Distribution Rule used in transactions
    1807654
    Serial No./Batch inconsistency by canceled Inventory Transfer
    1808694
    BR: Business Partner Code cannot be updated with CNPJ CPF error
    1809398
    CR_Cannot Display Related Multi-Value Parameters
    1809758
    Arrow key not work for Batch/Serial Number Transactions Report
    1810099
    Tax Amount is Recalculated Even if Tax Code Is Not Changed
    1811270
    Upgrade fails on Serial And Batches object with error code -10
    1811846
    Cannot run Exchange Rate Differences when multi branch is activated
    1812344
    Withholding Tax Amount Is Not Updated in Payment Once Witholding Tax Code Is Changed in Document through DI API
    1812740
    DI:"Operation Code" show wrong value when add "A/P Tax Invoice" based on "A/P Invoice"
    1813029
    US_Vendor address on 1099 Summary by Form/Box Report is not updated according to the latest Invoice
    1813835
    Wrong amounts of Goods Return in Open Item List
    1814207
    Preliminary page prints setting does not keep after upgrade
    1814860
    Value "Zero" cannot be imported to "Minimum Inventory Level" field via Excel file
    1815535
    RFQ: Web front end not displayed in supplier language
    1815810
    GT: Adding Incoming Payment for Some Cash Flow Relevant Accounts Fails
    1816191
    BR:System Crashes While Working with Tax Code Determination Window
    1816611
    CR_Crystal Report Displayed Incorrectly Afte

  • System Calculating HCess twise while posting MM Invoice through MIRO

    Dear Gurus,
    System calcuating Highter Cess twise while posting MM invoice through MIRO.
    Please guide where could be problem... Pls provide standard steps need to verfy one by one to analysis the same.
    Regards,
    Venkat

    Dear Santosh,
    We are using TAXINN-Condition based method. We are maintaing JSEP as HCESs condition and JHX1 as Off-setting conditiong type.
    But system calcuating condition value against both in IV........
    Regards,
    Venkat

  • "Indicator: GR-Based Invoice Verification" direct input Upld PO LSMW

    Hi, Im using lsmw direct input method. I am uploading the PO. But the GR Based invoice verification field was not checked ON. Im trying this using USER_EXIT in enhancement MM06E005, with EXIT_SAPMM06E_017.
    Any body can tell me how i can check ON the field WEBRE( GR based invoice verification) while creating the PO through LSWM.
    regards
    RAJ

    Hi,
    How you solved, kindly explain
    Also explain how to upload PO through LSMW in the case of multiple line items for single PO?
    Thanks & Regards
    Ravi

  • How to send invoice through email with output type RD00?

    What are the configuration settings to send invoices through email with output type RD00?

    Hi,
    Please go through the following links:
    [E-mail|Email Configuration Settings]
    [e-mail|Re: EMAIL BILLING DOCUMENT TO CUSTOMER THROUGH SEND MAIL OPTION IN VF02]
    After triggering the output,goto T.Code SOST and process it.
    So that e-mail will be triggered immediately.
    You can use External send/EDI/simple mail for this.
    Regards,
    Krishna.

Maybe you are looking for