Reduce vendor invoice in total

Dear all,
If i have invoice with many line items in MIRO T,Codes, now supplier invoice came with less amount and i would like to reduce my invoice amount at MIRO before posting, so i need to go to each line items and reduce some amount from each line items, is any way i could do that without referring to each line items, i mean in total.

Pls go through below
Invoice reduction is done when there is a difference between the MIRO value as your system calculates it and when the vendor has given in his invoice. This can be both for a higher or lesser value. Invoice reduction can be done at item or at total level depending on the requirement.
See link...
MM > Iogistics invoice verification > Posting total based difference.
http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm
http://help.sap.com/search/highlightContent.jsp
For item level invoice reduction...
MM > LIV > Invoice verification Online > Invoice items > Entering qty or price variance and Invoice Reduction: correction or quantities or values.
http://help.sap.com/saphelp_47x200/helpdata/en/a8/b99f58452b11d189430000e829fbbd/frameset.htm
BR,
Krishna
Further more, I guess
You only use total based reduction when all of the following conditions are fulfilled:
The invoiced amount is larger than the planned amount.
You have not reduced the invoice manually.
You have not yet accepted the difference in the invoice manually.
The difference exceeds the positive small difference set in Customizing for Logistics Invoice Verification.
An invoice reduction tolerance has been set for the vendor and company code in Customizing for Logistics Invoice Verification.
The difference lies within the invoice reduction tolerance limits set.
BR,
Krishna
Edited by: Krishna Chaitanya Reddy Katakam on Mar 29, 2011 8:00 PM

Similar Messages

  • Tables for vendor invoice and payment

    Hi Gurus.
    I want to know from which tables i can get the information for folllowing points.
    1.       Vendor Invoices  - Complete (Header and Item)
    2.       Vendor Payments Details – Detail about payment method (check, wire, etc)
    Please tell me tje table names.

    There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
    |Table Name               |Table Description                                           |
    |/BEV3/CHKOMPAZVV         |Append Structure CH -> CO PA                                |
    |/CWM/ACCIT               |Append Structure for Enhancement of Structure ACCIT in CWM  |
    |/CWM/KOMP                |Catch Weight Management Enhancement                         |
    |/DSD/TAXJURCD            |Ship From Tax Jurisdiction Code: for Header Prc Comm Str    |
    |/SAPNEA/J_SC_LFA1        |Subcontractor Information                                   |
    |/SAPNEA/J_SC_LFB1        |Subcontracting Management                                   |
    |/SAPPSPRO/A_FI2_LONGNUM  |IBU-PS:  Append structure for structure NONBSEG             |
    |/SAPPSPRO/A_LONGNUMBER   |additional fields for SPIIN number                          |
    |/SAPPSPRO/EADD           |Purchasing Document Header: Additional Data                 |
    |/SAPPSPRO/EADD_DATA      |Purchasing Document Header: Data Part Additional Information|
    |/VSO/R_KNA1_A            |Append to KNA1 for Vehicle Space Optimization               |
    |/VSO/R_KNA1_I            |Additional Data for Vehicle Space Optimization for KNA1     |
    |AACCHD_FMFG              |US federal fields                                           |
    |AACCHD_PSO               |IS-PS: ACCHD Append Structure for Payment Requests          |
    |AACCIT_GM                |Append for Grants Management                                |
    |AACCIT_PSO               |IS-PS: ACCIT Append Structure for Payment Requests          |
    |AACCIT_SSP               |Append for Payment Statistical Sampling Process             |
    |AACCIT_USFG              |Append structure for US federal government                  |
    |AAUSZ_CLR_USFG           |Clearing information for US Fed (Tresury Confirmation)      |
    |ABKPF_PSO                |IS-PS: BKPF Append Structure for Payment Requests           |
    |ABKPF_UMB                |IS-PS: Append Structure for Transfer Transaction FMITPO     |
    |ABSID_PSO                |IS-PS: Data appendix of open items customers                |
    |ABSIK_PSO                |IS-PS: Data appendix of open items vendors                  |
    |ABSIS_PSO                |Local Authorities                                           |
    |ABUZ                     |Help Structure for Line Items to be Generated Automatically |
    |ACCCR                    |Accounting Interface: Currency Information                  |
    |ACCCR_FKEY               |Key: Acctg Currency Data for Line Item Including Currency   |
    |ACCCR_KEY                |Key: Accounting Currency Data for Line Item                 |
    |ACCFI                    |Interface to Accounting: Financial Acctg One-Time Accts     |
    |ACCHD                    |Interface to Accounting: Header Information                 |
    |ACCHD_KEY                |Key: FI/CO Document Header                                  |
    |ACCIT                    |Accounting Interface: Item Information                      |
    |ACCIT_EXTENSION          |ACC Document: Additional Item Information                   |
    |ACCIT_JV                 |Joint Venture Accounting                                    |
    |ACCIT_KEY                |Key: FI/CO Line Item                                        |
    |ACCIT_WT                 |Withholding tax information for FI Interface                |
    |ACCRDF                   |Fields for Posting Small Differences: Preparation           |
    |ACC_DOCUMENT             |Accounting document                                         |
    |ACC_KONTEXT              |Context Info for FI Single Screen Transactions FB50 and FB60|
    |ACERRLOG                 |Return Parameter                                            |
    |ACGL_HEAD                |Fields for Document Header Entry Screen                     |
    |ACGL_ITEM                |Structure for Table Control: G/L Account Entry              |
    |ACSCR                    |Communication Structure for Field Modification SAPLFDCB     |
    |ACSPLT                   |Carrier for Split Information re: Current Account Line Items|
    |ACSPLT_WTNEW             |Proportion of New Withholding Tax                           |
    |ACSPLT_WTOLD             |Proportion of Old Withholding Tax                           |
    |ADDR1_SEL                |Address selection parameter                                 |
    |AEBPP_KNBK               |Additional Fields Bank Data Biller Direct                   |
    |AEBPP_LFBK               |Additional Fields Bank Data Biller Direct                   |
    |AFMIOI                   |Append for new fields ECC50/ERP                             |
    |AFMIOI_USFG              | SD order needs quantity                                    |
    |AFMISPS                  |Additional Fields for Table FMISPS                          |
    |AFM_ACCIT_EXTENSION      |Extension for FM Payment Update                             |
    |AFM_FAGL_GLT0_ACCIT_EXT  |Extension FM Account Assignments                            |
    |AFM_FI_BKPF_SUBST        |Append to Structure BKPF_SUBST                              |
    |AFM_FMFCTF               |Append for Fund Center substrings                           |
    |AFM_FMFINCODE            |Append for Fund substrings                                  |
    |AIFM01D                  |Append for IFM01D                                           |
    |AKNA1_FMFG               |US Federal Government Customer Master Data Additional Fields|
    |AKNA1_PSO                |Local Authority Additional Fields                           |
    |AKNB1_PSO                |IS-PS: Customer Master Record, Additional Data (Co.Code)    |
    |AKNBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALFA1_FMFG               |US Federal Government Vendor Master Data Additional Fields  |
    |ALFA1_PSO                |Local Authority Additional Fields (Address)                 |
    |ALFB1_FMFG               |PS fields for company code-specific master data field       |
    |ALFB1_PSO                |IS-PS: Data Appendix Vendor Master Record (Company Code)    |
    |ALFBK_PSO                |Bank Details Dependent on Time and Account Holder           |
    |ALVDYNP                  |ALV dialog screen fields                                    |
    |ALV_S_FCAT               |Field Catalog (for LVC and for KKBLO)                       |
    |ALV_S_FILT               |Filter Criteria (for LVC and for KKBLO)                     |
    |ALV_S_GRPL               |Group Levels (for LVC and for KKBLO)                        |
    |ALV_S_LAYO               |Layout (for LVC and for KKBLO)                              |
    |ALV_S_PCTL               |Structure for Checking Print in ALV                         |
    |ALV_S_PRNT               |Print settings (for LVC and KKBLO)                          |
    |ALV_S_QINF               |Structure for Quickinfos of Exceptions                      |
    |ALV_S_SGRP               |Field Groups (for LVC and for KKBLO)                        |
    |ALV_S_SORT               |Sort Criteria (for LVC and for KKBLO)                       |
    |ANBZ                     |Help structure for asset line item                          |
    |ANLZACCOUNT              |Additional Account Assignment Objects in Asset Accounting   |
    |ANLZACCOUNT_FKBER        |Account Assignment Objects: ANLZACCOUNT with Function Added |
    |ARC_PARAMS               |ImageLink structure                                         |
    |AT003_XBLNR2             |Append structure for US federal government                  |
    |AUSZ1                    |Clearing Table 1                                            |
    |AUSZ2                    |Clearing Table 2                                            |
    |AUSZ_CLR                 |Assign Clearing Item to Cleared Items                       |
    |AUSZ_CLR_ASGMT           |Assgt of Clrg Items - Cleared Items with Acct Assignment    |
    |AUSZ_INFO                |Open item data for clearing transactions                    |
    |AVBKPF_FMFG              |US federal                                                  |
    |AVBKPF_PSO               |IS-PS: Append Structure VBKPF for Payment Requests          |
    |AVBSEGDPSO               |IS-PS: Append Structure VBSEGD for Payment Requests         |
    |AVBSEGKPSO               |IS-PS: Append Structure VBSEGK for Payment Requests         |
    |AVIK                     |Payment Advice Header                                       |
    |AVIP                     |Payment Advice Line Item                                    |
    |BALHDR                   |Application log: log header                                 |
    |BALMT                    |Application Log: Structure for a formatted message          |
    |BAL_S_CLBK               |Application Log: Return routine definition                  |
    |BAL_S_CONT               |Application Log: Context                                    |
    |BAL_S_MSG                |Application Log: Message Data                               |
    |BAL_S_PAR                |Application Log: Parameter Name and Value                   |
    |BAL_S_PARM               |Application log: Parameters                                 |
    |BAPIASCONT               |Business Document Service: File Content ASCII               |
    |BAPIBDS01                |Business Document Service: Reference Structure for BAPIs    |
    |BAPICOMFIL               |BDS: Command File for Transport Entries                     |
    |BAPICOMPO2               |SBDS: Enhanced Component Information                        |
    |BAPICOMPO3               |SBDS: Enhanced Component Information                        |
    |BAPICOMPON               |Business Document Service: Component Table                  |
    |BAPICONNEC               |BDS: Structure for BDS Links                                |
    |BAPICONTEN               |Business Document Service: File Content                     |
    |BAPIDPROPT               |BDS: Structure for Properties                               |
    |BAPIFILES                |Business Document Services: Transfer Table for File Names   |
    |BAPIPROPER               |BDS: Structure for Properties                               |
    |BAPIPROPTL               |BDS: Structure for KPRO Properties                          |
    |BAPIQUERY                |BDS Structure for Query Table                               |
    |BAPIRELAT                |Business Document Service: Relations                        |
    |BAPIRET1                 |Return Parameter                                            |
    |BAPIRETURN               |Return Parameter                                            |
    |BAPISIGNAT               |Business Document Service: Signature Table                  |
    |BAPISRELAT               |Business Document Service: Relationship Table with Signature|
    |BAPIURI                  |Business Document Service: URI Table                        |
    |BDCMSGCOLL               |Collecting messages in the SAP System                       |
    |BDCRUN                   |Batch input: Runtime analysis                               |
    |BDIDOCSTAT               |ALE IDoc status (subset of all IDoc status fields)          |
    |BDI_SER                  |Serialization objects for one/several IDocs                 |
    |BDN_FKT                  |Business Document Navigator: Functions to be Excluded       |
    |BDWFAP_PAR               |Parameters for application function module - IDoc inbound   |
    |BDWFRETVAR               |Assignment of IDoc or document no. to method parameter      |
    |BDWF_PARAM               |Parameters for workflow methods for IDoc inbound processing |
    |BKDF                     |Document Header Supplement for Recurring Entry              |
    |BKDF_SUBST               |Process Interfaces: Substitutable fields during posting     |
    |BKORM                    |Accounting Correspondence Requests                          |
    |BKP1                     |Document Header Supplement for Update                       |
    |BKPF                     |Accounting Document Header                                  |
    |BKPFBU_ALV               |Document Overview: Display Document Headers in ALV Grid Ctrl|
    |BKPF_CARD                |Credit Card: Append for BKPF                                |
    |BKPF_LINE                |Item Category for XBKPF_TAB                                 |
    |BKPF_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BKPF_USFED               |Append structure for US federal government                  |
    |BLNTAB                   |Document Number Table for Financial Accounting              |
    |BNKA                     |Bank master record                                          |
    |BNKAAPP                  |Appendix to Table BNKA                                      |
    |BNKT                     |Conversion of temporary to internal bank keys               |
    |BOOLE                    |Boolean variable                                            |
    |BSEC                     |One-Time Account Data Document Segment                      |
    |BSEC_LINE                |Item Category for XBSEC_TAB                                 |
    |BSED                     |Bill of Exchange Fields Document Segment                    |
    |BSEE                     |Changeable Fields in the Line Item                          |
    |BSEG                     |Accounting Document Segment                                 |
    |BSEGL                    |Document Segment: Fields Derived for Line Layout Variant    |
    |BSEGS                    |G/L Item Transfer Structure for Single Screen Transactions  |
    |BSEGT                    |Transfer Table for the Tax Postings to be Generated         |
    |BSEGZ                    |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
    |BSEG_ALV                 |Document Overview: Document Item Display in ALV Grid Control|
    |BSEG_LINE                |Item Category for XBSEG_TAB                                 |
    |BSEG_SUBST               |Process Interfaces: Substitutable Fields During Posting     |
    |BSET                     |Tax Data Document Segment                                   |
    |BSEU                     |Line Item Additional Information (Update)                   |
    |BSEZ                     |Line Item Additional Information (Online)                   |
    |BSEZ_LINE                |Line Item Category for XBSEZ_TAB                            |
    |BSID                     |Accounting: Secondary Index for Customers                   |
    |BSIK                     |Accounting: Secondary Index for Vendors                     |
    |BSIP                     |Index for Vendor Validation of Double Documents             |
    |BSIS                     |Accounting: Secondary Index for G/L Accounts                |
    |BSIX                     |Index table for customer bills of exchange used             |
    |BTXKDF                   |Fields for Exch.Rate Difference Posting for Taxes           |
    |BVOR                     |Intercompany posting procedures                             |
    |CACS_A_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_A_CUST_COND         |Commissions: Customer Fields Condition Technique            |
    |CACS_A_FIELDSPRICING     |Append for Condition Technique Fields from Commission System|
    |CACS_S_CRM_SALES_COND    |Additional CRM Fields (Construction) From Sales Order Area  |
    |CACS_S_CUST_COND         |Condition Attributes                                        |
    |CACS_S_FIELDSPRICING     |Comm.: All Condition Technique-Relevant Commission Fields   |
    |CACS_S_FSINS             |Customer Fields for Condition Technique of Insurances       |
    |CCDATA                   |Payment cards: Database fields relevant to both SD and FI   |
    |CFW_LINK                 |CFW: Link Info of a Container                               |
    |CI_COBL                  |Extension                                                   |
    |CKI_ACCIT_ML             |Transfer from MM to ML in accit-structure                   |
    |CNTLSTRLIS               |Control stream list                                         |
    |COBK                     |CO Object: Document Header                                  |
    |COBK_ONLY                |Non-key fields only in COBK (INCLUDE structure)             |
    |COBL                     |Coding Block                                                |
    |COBLF                    |Coding block: Tax table structure                           |
    |COBL_COKZ                |Assignment types for CO account assignments                 |
    |COBL_DB_INCLUDE          |Include with Additional Account Assignments for DB Tables   |
    |COBL_EX                  |Coding Block for External Applications (Not CO/FI)          |
    |COBL_FI                  |Fields from COBL that Must not Be Overwritten in FI         |
    |COBL_FM                  |Additional Fields for FM                                    |
    |D010SINF                 |Generated Table for View D010SINF                           |
    |D020S                    |System table D020S (screen sources)                         |
    |D020T                    |Screen Short Description                                    |
    |DBSEG                    |Dialog Supplementation BSEG (Taxes)                         |
    |DD02L                    |SAP Tables                                                  |
    |DD03P                    |Structure                                                   |
    |DD03V                    |Table fields view                                           |
    |DD07V                    |Generated Table for View DD07V                              |
    |DD23L                    |Matchcode ID                                                |
    |DD32P                    |Interface structure for search help parameters              |
    |DDSHDEFLT                |Description of a default value for search help fields       |
    |DDSHDESCR                |Interface: elementary search helps of a search help         |
    |DDSHFPROP                |Characteristics of search help parameters                   |
    |DDSHIFACE                |Interface description of a F4 help method                   |
    |DDSHRETVAL               |Interface Structure Search Help <-> Help System             |
    |DDSHSELOPT               |Selection options for value selection with search help      |
    |DDSUX030L                |Nametab Header, Database Structure DDNTT                    |
    |DDSUX031L                |Nametab Structure, Database Structure DDNTF                 |
    |DDTYPES                  |Table of all Dictionary types and classes                   |
    |DFIES                    |DD Interface: Table Fields for DDIF_FIELDINFO_GET           |
    |DISVARIANT               |Layout (External Use)                                       |
    |DOKHL                    |Documentation: Headers                                      |
    |DPPROPS                  |General property structure for data provider                |
    |DTC_S_LAYO               |Structure for Design of Double Table Control                |
    |DTC_S_TC                 |Structure for table controls in the double table dialog box |
    |DTC_S_TS                 |Tab Title Structure                                         |
    |DYNPREAD                 |Fields of the current screen (with values)                  |
    |E071                     |Change & Transport System: Object Entries of Requests/Tasks |
    |E071K                    |Change & Transport System: Key Entries of Requests/Tasks    |
    |EAPS_20                  |Field Enhancements for EA-PS 2.0                            |
    |EDIDC                    |Control record (IDoc)                                       |
    |EDIDS                    |Status Record (IDoc)                                        |
    |EDIFCT                   |IDoc: Assignment of FM to log. message and IDoc type        |
    |EDIMESSAGE               |Transfer Structure with all Sy Fields for T100              |
    |EDI_DS                   |Status record for interface to EDI subsystem                |
    |EDI_HELP                 |Help Structure for Reference Fields in EDI Function Groups  |
    |EK05A                    |Communication Area Purchasing - Financial Accounting        |
    |ESKN                     |Account Assignment in Service Package                       |
    |EUDB                     |Development Environment Objects                             |
    |EUOBJ                    |Workbench: Development Objects                              |
    |EXCLTAB_LINE             |Lines of EXCLTAB with OK Code to be Deactivated             |
    |EXISTING_DOC             |Original Document                                           |
    |F05ACTRL                 |Control Fields for SAPMF05A and Subprograms                 |
    |FAGLBSEGL_S              |Additional Sender Flds from General Ledger for Doc. Overview|
    |FAGL_GLT0_ACCIT_EXT      |Line Information for Document Splitting                     |
    |FAGL_MIG_S_BUKRS_LEDGER  |Combination of Company Code and Assigned Ledgers            |
    |FAGL_SPLIT_FLD_S         |Characteristics Permitted for Split                         |
    |FAGL_S_APPLICATION       |Application and Subapplication                              |
    |FAGL_S_BALDIM            |G/L Characteristics of Document Split in New General Ledger |
    |FAGL_S_BUKRS             |Structure with Company Code                                 |
    |FAGL_S_BUKRS_EXT         |Structure: Company Codes --> Ledgers                        |
    |FAGL_S_CURTYPES          |Currency Types of a Ledger                                  |
    |FAGL_S_MIG_001           |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S           |
    |FAGL_S_MIG_MGPLN_EXT     |Structure: Extended Migration Plan Information              |
    |FAGL_S_T8G40_BS          |Split Fields with Characteristic "Balance Sheet"            |
    |FCRD_VBKPF               |Credit Card: Include for Appends for BKPF, VBKPF            |
    |FCRD_VBSEG               |Include for Appends for VBSE*                               |
    |FDM_AR_CASE_ATTR_1       |FSCM DM:                                                    |
    |FDM_AR_LINE_ITEM         |FSCM: DM                                                    |
    |FDM_AR_RFPOS             |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
    |FELD                     |Screen Painter fields (internal)                            |
    |FICCO                    |Adjustment Values for External Document Items               |
    |FICCT                    |Totals Information for Interclient Posting                  |
    |FICTX                    |Tax Information for ICT                                     |
    |FIELDINFO                |Field attributes for a specific field                       |
    |FIN1_PARAM               |OBNG: Trans. structure for official doc. numbering (global) |
    |FIN1_PARAM_FI            |OBNG: FI parameters                                         |
    |FIN1_PARAM_MM            |OBNG: MM Parameters                                         |
    |FIPEX_STRUC              |Subfields Commitment Item                                   |
    |FIPOEXT                  |Help structure for line items to be generated automatically |
    |FIREVDOC                 |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS     |
    |FISTL_STRUC              |Substructure Fund Center                                    |
    |FM01                     |Financial Management Areas                                  |
    |FMBLSTRING_COMPONENTS    |Component of the BL String                                  |
    |FMCI                     |Commitment items master data                                |
    |FMDY                     |FIFM: Screen Fields                                         |
    |FMFCTR                   |Funds Center Master Record                                  |
    |FMFG_ACCIT_EXTENSION     |Extention for all fields that have to be transfered into BL |
    |FMFINCODE                |FIFM: Financing code                                        |
    |FMFPO                    |FIFM: Commitment Item                                       |
    |FMHRBA_NEG_DOC_TYPES     |HR Integration: Doc. Types for Negative Funds Commitments   |
    |FMHRBA_SETTINGS          |Integration with HR: Settings                               |
    |FMHRBA_VAD_SETTINGS      |HR Integration: Generate Value Adjustment Docs for Changes  |
    |FMICCN                   |FM: Append Structure for FMIOI (CCN Fields)                 |
    |FMIDATA                  |Common Data for Funds Management Actual Data                |
    |FMIDATAFI                |Clean FI Data for Funds Management Actual Data              |
    |FMIDATAOI                |Clean Open Item Data for Funds Management Actual Data       |
    |FMIFIIT                  |FI Line Item Table in Funds Management                      |
    |FMIKEY                   |Common Key for Funds Management Actual Data                 |
    |FMIKEYFI                 |FI - Key for Funds Management Actual Data                   |
    |FMIKEYOI                 |Common Key for Funds Management Actual Data                 |
    |FMIOI                    |Commitment Documents Funds Management                       |
    |FMIOIKEY                 |Key for Table FMIOI                                         |
    |FMIOI_USFG               | SD order needs quantity                                    |
    |FMIREF                   |Ref. Funds Management Actual Data to Preceding Document     |
    |FMISPS                   |General Parameters for Funds Management                     |
    |FMIT                     |Totals Table for Funds Management                           |
    |FMMRESERV                |Include for the Reduction of Funds Reservations (FM)        |
    |FMRFC                    |Function Modules and their RFC Destinations                 |
    |FMSP_SPLIT_FIELDS        |PSM Fields used in multiple account splitting               |
    |FMT001                   |Additional Customizing for Funds Management                 |
    |FMUP00T                  |Update Profiles                                             |
    |FMUP01                   |Update Control with Value Type Dependency                   |
    |FMUP_INV_KEY             |Extension for FM Update: FI Key of Invoice                  |
    |FMUP_PAY_KEY             |Extension for FM Update: FI Key of Payment                  |
    |FS006                    |Fields for Optical Archiving                                |
    |FTCHECK                  |Foreign Trade: Import Simulation - Ctrl Fields for Pricing  |
    |FTEXTS                   |Communication Structure for Additional Components           |
    |FTGENERAL                |Foreign Trade: General Fields Item                          |
    |FUND_STRUC               |Substructure Fonds                                          |
    |FVD_TZB0A                |Append to TZBOA: Loans Fields                               |
    |GLACCOUNT_CCODE          |G/L Account Master Record: Company Code                     |
    |GLACCOUNT_CCODE_DATA     |G/L Account Master Record: Company Code - Data              |
    |GLACCOUNT_CCODE_INFO     |G/L Account Master Record: Company Code - Information       |
    |GLACCOUNT_CCODE_KEY      |G/L Account Master Record: Company Code - Key               |
    |GLX_ORG_INFO             |Organizational Assignment                                   |
    |GMBSEGZ                  |Grants Management Add-on                                    |
    |GXXLT_H                  |XXL interface: horizontal features                          |
    |GXXLT_O                  |XXL_interface: texts for online display                     |
    |GXXLT_S                  |XXL interface: structure of the semantics table             |
    |GXXLT_V                  |XXL interface: vertical features                            |
    |HELPVAL                  |Restrict Value Range - Transfer Table                       |
    |HELP_INFO                |Transfer Values for the Help Processor                      |
    |HELP_VALUE               |Structure or Function Module HELP_VALUE_GET_FOR_TABLE       |
    |HHM_COBL                 |Include for COBL from FM                                    |
    |IADDR_PSO                |Local Authority Additional Fields (Address)                 |
    |IBKPF_PSO                |IS-PS: Include Structure BKPF Payment Request Doc.Header    |
    |ICDIND                   |Structures for generating change document update programs   |
    |ICON                     |Icons table                                                 |
    |ICONS                    |Icons                                                       |
    |ICURR                    |Interface for Currency Translation                  

  • Report for the account of vendor invoices not received ?

    Hi friends;
    Is there a report or a transaction that would list the details (expense accounts, cost center an amounts) in the account of vendor invoices not received ?
    Thinks

    Hi ,
    me2n report in which u get total amount for invoiced and another column still to be invoiced amount .So check in that report even it is with PO number.

  • Clearing between customer and vendor invoice with F110 transaction

    Hello,
    I have an issue related to the functionalities of the transaction F110.
    I'd like to clear the vendor invoice with the custome invoice.
    Customer and vendor records are linked properly and the flag 'Clrg with Cust.' is set on vendor and 'Clearing with Vendor' is set on customer.
    Both the invoice are in USD and the amount in document currency of the vendor invoice is > of the amount in document currency of the customer invoice.
    I entered in both the invoice the same payment method (outgoing payment method).
    The error that I can see in the proposal log is related to the customer invoice and is:
    Payment method selection for items due now to the amount of USD          500,00
    Due items with currency USD, pmnt method  - items total is > 0
    ..none of the payment methods defined can be used for these items
    information re. vendor xxxxxxxx / customer yyyyyyy / paying company code TS01 ...
    .. payment not possible because of reported error
    According to the log of the proposal the vendor invoice can be paid.
    If I click on display proposal and double click on the customer invoice (with red light) I can read the note:
    No pymt possible because items with a debit
    Following the settings of the payment method used:
    Payment method in the country
    - Payment method for outgoing payment selected
    - Bank transf. selected
    - allowed for personal payment flagged
    - Bank details flagged
    - Document type for payment XX
    - clearing document type XX
    - Use classic payment medium program selected
    Currency allowed: This table is empty (will mean that all currencies are permitted)
    Payment method in company code
    Minimum amount: 0,01
    Maximum amount: 9.999.999.999,99
    Distribution amnt: 0,00
    Single paymentfor marked item selected
    Foreign business partner allowed selected
    foreign currency allowed selected
    Cust/vend bank abroad allowed? selected
    Bank selection control "No optimization" selected
    Can you please help me to understand the error?
    I'm afraid it is a problem with the bank but I don't understand why the payment of the vendor invoice is allowed and the customer invoice not.
    Thank you very much in advance
    Kind R

    Hello,
    I have an issue related to the functionalities of the transaction F110.
    I'd like to clear the vendor invoice with the custome invoice.
    Customer and vendor records are linked properly and the flag 'Clrg with Cust.' is set on vendor and 'Clearing with Vendor' is set on customer.
    Both the invoice are in USD and the amount in document currency of the vendor invoice is > of the amount in document currency of the customer invoice.
    I entered in both the invoices the same payment method (outgoing payment method).
    The error that I can see in the proposal log is related to the customer invoice and is:
    Payment method selection for items due now to the amount of USD          500,00
    Due items with currency USD, pmnt method  - items total is > 0
    ..none of the payment methods defined can be used for these items
    information re. vendor xxxxxxxx / customer yyyyyyy / paying company code TS01 ...
    .. payment not possible because of reported error
    According to the log of the proposal the vendor invoice can be paid.
    If I click on display proposal and double click on the customer invoice (with red light) I can read the note:
    No pymt possible because items with a debit bal.still exist; see job log
    Following the settings of the payment method used:
    Payment method in the country
    - Payment method for outgoing payment selected
    - Bank transf. selected
    - allowed for personal payment flagged
    - Bank details flagged
    - Document type for payment XX
    - clearing document type XX
    - Use classic payment medium program selected
    Currency allowed: This table is empty (will mean that all currencies are permitted)
    Payment method in company codeMinimum amount: 0,01
    Maximum amount: 9.999.999.999,99
    Distribution amnt: 0,00
    Single paymentfor marked item selected
    Foreign business partner allowed selected
    foreign currency allowed selected
    Cust/vend bank abroad allowed? selected
    Bank selection control "No optimization" selected
    Can you please help me to understand the error?
    I'm afraid it is a problem with the bank but I don't understand why the payment of the vendor invoice is allowed and the customer invoice not.
    Thank you very much in advance
    Kind Regards
    Emanuela

  • Recommendations, samples, etc for creating a "Vendor Invoice" Content Type.

    I am developing a "Vendor Invoice Approval" application in SharePoint 2013. My development platform is "Visual Studio 2013". This will be an "Intranet only" application running only on our internal SharePoint
    2013 Farm.
    I am planning on using a "Document Library" to store all of the Invoices. I believe the "correct" approach (or one of many, probably, lol) would be to create a "Content Type" called "Vendor Invoice". The "content
    type" would then need to have the following functionality:
    Custom Columns. Some columns would be "required", some would be "optional".
    Vendor Name - Chosen from a “Vendors” list (a SharePoint "custom" list that contains "Vendor Name" and "People Responsible" (which will be a "People" type column and allow multiple choices/people from
    a SharePoint Group called "Vendor Invoice Person Responsible"). The user may also enter a new Vendor Name.
    Person Responsible - Limited to the users in the “Vendor Invoice Person Responsible” SharePoint Group. Will allow the selection of 1 or more "people" from that Group. (When a Vendor Name is "chosen" (above), this field
    should be populated with the values from the "People Responsible" record for that Vendor. The user can then ONLY choose between those users or choose them all. Optionally, I may just store a single Person in the "Vendors" list and use that
    to populate this field with a "default" value, but then allow the user to pick ANY user from the "Vendor Invoice Person Responsible" SharePoint Group).
    Invoice Number (Will probably renamed the “Title” column.)
    Invoice Date
    Invoice Amount
    PO Number (When entered, look it up in our ERP system and populate as many fields as possible, such as the Vendor Name, Account Number and Plant.)
    Status - Most likely this field will only be adjusted via "workflows". Choices are:
    “Created” – The initial Status when an Invoice is created (BEFORE any “Issue” or “Approved”).
    "Pending Issue" - An "Issue" needs to be resolved. (See "Issue" below.)
    “Issue Resolved” – The current “Issue” has been resolved. The next status could be “Pending Issue” (if there is another Issue to resolve) or “Approved”.
    “Approved” – All Issues have been resolved.
    “Issue Check” – The Invoice was “Approved” and a check may now be issued to the Vendor.
    “Completed” – The Invoice has been “Approved” and the vendor has been issued a check.
    Issue - Chosen from an “Invoice Issues” list (a SharePoint "custom" list that contains "Issue" and the name of a "WorkFlow" to execute on the "Invoice" in order to resolve that particular "Issue").
    When an Issue is chosen, this will trigger a "Workflow" (or more than one?? probably only one...) to start.
    Account Number
    Plant (Choices: 1-New York, 2-Los Angeles,99-Headquarters)
    Invoice Notes
    Template/Forms (Insert/Update)/Development/Event Receivers/Display Template/"UI". This is the part that I am unsure of and where "Visual Studio" will be used. (I have quite a bit of experience developing "SharePoint
    Solutions". I am not interested in using the new "App Model". I have read about it, studied it, setup a local "App Store", etc, but for this particular application, I am going to stick with the "old" Solution based model.
    I am more familiar with it and "believe" it will give me the most "power" and "flexibility". As I said.... I am unsure how to "categorize" the following "needs", so I am just going to lump the rest of the "features"
    I need into the list below and ask for any feedback and/or help. :)
    Adding Invoices - Ideally, the "drag and drop" feature will (can) be utilized by the user to add the new Invoices (I can force them to only add one Invoice at a time). If this is just "too much trouble", I
    could require the user to only add them using the "Upload Document" control. Or, I could develop the UI  (or just the Insert/Update UI) using traditional "ASP .Net" controls and insert/update the data using the Server
    Object Model or the Client Object Model (CSOM).
    Preview Invoices - There are several times I would like to show the Invoice (pdf) as a "preview" (when the Invoice is being Added or Edited, when the user is "Approving" or "Denying"
    on Invoice via a "WorkFlow", or when an Invoice is "hovered" over in a Document Library View). Basically, anytime the Invoice needs to be acted on by a user, I would like to show the PDF in a "preview" window and
    I don't mean just open it in a separate Tab or Window. I mean use something like an "IFrame" in a certain area of the page (depending on what the page is doing: Inserting/Editing/Viewing/etc) to show that preview.  (For the "hover
    preview", I believe I can use the same skills I learned when modifying how the "Enterprise Search Center" works with PDFs. Basically, it involved adding a new Display Template for the Search Item and referencing that template
    in a new "Search Result Type". The new Display Template created an "IFrame" and populated it using our Office Web App Server via "WOPI". Anyway, I believe I can simply do the same thing in a Document Library View and most
    likely in whatever "form" or "page" is responsible for the Insert/Edit. I suppose I am just looking for someone to tell me if this is "doable" (and as "easy" as I think it might be), what the "best"
    way to accomplish it would be, or if it is a bad idea, etc. etc.)
    "Auto Populate" the columns. When a new Invoice is added, I would like to use the (Enterprise) Search functionality (OCR and "graphic matching") to somehow populate as many of the columns (metadata) as possible.
    This might involve looking for some particular "text" or graphic(s) (like a company logo?) to determine the Vendor. Then, once the Vendor is determined, I might be able to figure out other items, such as the "Invoice Number" and "PO".
    Usually our Vendor Invoices don't change very often. This would only serve as "default" values, so it wouldn't have to be 100% correct. Anything I can do to save the user time or make it easier to enter new Invoices will go along way towards
    acceptance of this application. (Currently, they use an Excel Spreadsheet, along with email. So, from their point of view, the existing "system", "works" and is very "easy" to use,  etc....)
    More uses for the "Search Index Results". It would also be "nice" if we could setup some "weighted rules" on a "per Vendor" basis to help determine who the "responsible user" is. (For instance,
    we may get Invoices from a single Vendor that could possibly go to 1 of several "responsible users". In order to determine the correct user, I would like to setup some "rules" for each vendor to give "weighted" values to
    certain "keywords". For instance, if the word "Computer" appears on the invoice, that might be worth "100 points" towards the "IT Manager". So, when the user is selecting the person responsible for this particular invoice,
    I could order the list they are choosing from by the "total points" (as calculated from the "weighted rules") which would put the "Person" who is most "likely" the "Person Responsible" at
    the top of the list, followed by the second most likely, and so on. I don't think this be that "hard" to do. I would simply need to store "keywords" and "values" and have access to the "Search Index Results" for the
    document (Invoice) the user is currently adding.
    **Another "option" I have for developing this application is to basically develop it using a traditional "ASP .Net" framework and controls (which I definitely have more experience with, but as I mentioned, I also
    have quite a bit (4-5 years) of SharePoint development experience) and just using the "out of the box" features of SharePoint (and Custom Lists, Document Libraries, SharePoint Security Groups, WorkFlows), etc. What I am trying to describe is that
    I would develop the "UI" (add/change/delete) using traditional "ASP .Net" controls and just use SharePoint for my "Data Source". (I DO need to AT LEAST use SharePoint as the "Data Source". This is for reasons that
    I don't want to get into here and just bog down the discussion. I certainly realize this application could easily be a "traditional" "ASP .Net" application using "SQL" for the Data Source. So that part really isn't what I am looking
    for "advise" on.)
    Any help/advice/samples would be very MUCH appreciated!
    Shayne

    You should generate the XSD form the DTD files. Also you should list values unless necessary. XMLSpy is good tool I use.
    You can send the XML schema file to me if you can't register it to XML DB. I will help you take a look.

  • How to link Vendor Invoice to Customer Invoice in Third Party Sales Custom Report

    I have a requirement wherein I want the Invoice to have as many line items as MIRO have if partial delivery happens... invoices (one for each MIRO)..
    We are currently using the Third Party with Shhipping notification...
    I have tried using VF04 for billing but only one line item is coming for Billing in Invoice...
    I mean how to link the RSEG - partial vendor Invoice line items to Invoice...
    Ex: Third Party Order 20 qty
    Partial delivery 12 & 8... I can see 2 MIRO line item values in the table RSEG...
      If i do invoice in VF04..i can only see 1 line item for total billing....
      Can anybody help me how to solve this??? How can i link
      Vendor Invoice to the Customer Invoice....
      I have to solve this for a Third Party report???
      Thanks in Advance...

    Hi Senthil,
    I have seen the table VBRP..but it is showing only 1 line item 20 against 2 invoices 12 & 8...
    My requirement is that VBRP should show 2 line items of Vendor invoices 12 & 8...

  • Requirement to bill customer before vendor invoice in third party processing

    We have a requirement to bill a customer before the vendor invoice in third party processing. The reason behind this is because the vendor send invoices only once in a month and the customer cannot wait for so long to to receive their invoice from the business.
    I saw some discussions that the third party processing with shipment notification can be used however when I check the business flow in that case I see the following.
    A Third-Party Sales Order is created and a purchase requisition is generated automatically 
    A list of purchase requisitions to be assigned is displayed 
    The assigned purchase requisitions are converted into purchase orders 
    The purchase orders are approved 
    A statistical goods receipt is posted 
    The vendor invoice is verified and posted 
    The billing is created
    It clearly says that the customer billing document is only possible after entering the invoice from the vendor. Which would be the best way to fullfill this requirement?

    Do you mean the goods issue done by the vendor to the customer in the vendor system? And this quantity will be copied into our ( where the third party order is created) system?
    No, MIGO done by in our company system only. May be you might have misunderstood because of  my sentence.instead of company i mentioned as Vendor.
    For Vendor this process will become as standard sales and he will do PGI. However in our system we do MIGO .
    Suppose the customer ordered 10 Qty. Vendor delivered 2 Qty wouldn't the above equation Order qty- MIGO qty= Invoice qty be 10-2= 8? but we should be really billing the customer only for 2 right?
    No you have mistaken my idea, it was not a formula just i was giving example.
    Billing qty is nothing but it is qty copies from source document to target document.
    E
    Goods receipt quantity less invoiced quantity
    for example order qty is =10 and vendor delivered first time 2 qty to the customer and he billed our company for 2qty and we billed the customer for 2 qty.
    And next time let us assume again Vendor delivered 4 more qty and billed us 4qty.And this time when you are billing the customer in VF01 system will propose the 4qty only( total goods receipt qty 6 - already invoiced qty 2).
    Hope now you understood the meaning of E(goods receipt qty less invoices qty).
    And did you try your requirement as mentioned in my first reply?
    thanks,
    Srinu.

  • Vendor Invoice input tax in sales

    Dear All,
    We are implementing SAP in legal industry and we came across a scenario where we need to bill the Hard Cost, that we are treating as a material in SD side and we are determining this material in SD through Resource related billing.
    We post the Vendor invoice (HArd Cost as disbursement in service and legal indusrty) through  transaction FB60.
    Requirement is like that we need to bill the expense which i am treating as a Hard cost(Material) in sales with input tax.
    I know in SAP input and output taxes are handled seprately. But this is legal industry and we need to bill the HArd cost( posted vendor invoice through fb60) with Tax which i have paid to vendor. As i am not modifying this material so i am passing the total amount (expense plus tax portion which i have paid to the vendor) to the client to recover.
    We are already billing this expense in billing as a Hard cost, but according to business requirement we need to bill the expense with portion of Input Tax which i have paid to the Vendor.
    Any help on the above issue will really appreciate.

    Hello Anand Bakshi
    This is an interesting question, I don't have ready answers but can throw some pointers at you.
    1) Try Bill of Services, a complicated subject,  but it integrates  SD with MM by facilitating copy of  MM pricing conditions  to SD via costing sheet.
    IMG Menu Path: SPRO/IMG/Sales and Distribution/Bill of Services
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/8d/7638b88f3f11d2b47f006094b93006/frameset.htm
    2) Use SAP Industry Solution  (IS) - SAP for Professional Services, I am sure it will have this scenario covered or if you can not use the IS for some reason, try following the concept.
    Musically yours
    Lakshmi- Pyare
    ( just kidding to end the week with a smile, don't take it seriously)

  • Credit memo against a vendor invoice

    Hi All,
    I am trying to post a credit memo against a vendor invoice. After posting the credit memo I want the outstanding balance against the vendor to be reduced by amount of credit memo when I do F-44: vendor clearing.
    So for eg: if the invoice amount is $100 & credit memo amount is $10, I want to see only $90 in F-44. How can I achieve this?
    Right now I see Invoice amount $100 & credit memo amount $10 separately.
    Thanks!

    Hi,
    you have 3 ways to clear the Open line items(OLTs)
    example:
    1. follwoing document posted in FB01:
        invoice        : 40 expense 1000 USD/ 31 vend13  1000 USD
        credit memo:21 vend13     100 USD/  40 expense 100 USD
    2. A :you could clear above 2 OLTs using "charge off differece" in F-44, enter posting key 31, vendor and
            amount 900 USD. the result should be:
             001 31  0001 VEND13    900-
             002 27  0001 VEND13    900
       B:residual clearing in F-44, you will receive the below result:
          001 34  0001 VEND13  900-
          002 27  0001 VEND13  900
       But the re-requisition ifor above 2 solutions are the values in all fields which are includeded in structutre
       KONTAB_1ST are the same.
       C:partial payment in F-44, Below result:
           001 27  0001 VEND13   100
           002 37  0001 VEND13   100-
        Then clearing the the left amount 900 in invoice, you should select the inovice and the partial clearing
        document together.
    Hope above infor. could help you to solve your query!
    With Best Regards,
    Gladys Xing

  • F110 prints the check on the wrong page/leaf when vendor invoices overflow

    Hi all,
    When paying vendor invoices with a check printed through F110, if a vendor has more invoices than fit on a single check leaf, the following should happen:
    - Invoices overflow to the next page
    - Any checks before the last one are left blank and voided by the system
    - The check on the last page is printed with the total amount and is marked as valid by the system
    However, what's happening is the following:
    - Invoices overflow to the second page
    - The check on the first page is printed with the amount, date, etc. and marked as void by the system
    - The check on the second page comes out blank and is marked as valid by the system
    For some reason the form or print program isn't waiting until the last page to print the check. I can't find anything about check printing in case of an overflow in SAP Notes or transaction FBZP. Is this controlled by a setting in the program variant, or somewhere else?
    Thanks!
    Edited by: Pedro G. on Sep 9, 2010 5:43 PM

    Thanks for the reply, Brad.
    I see the CHECK window on the FIRST page has text elements 540 and 545, but the rest of the lines are commented out. There seems to be nothing printing there. Instead, this particular check layout has the date and payee in one window and the amount in another one, both on the FIRST page of the SAPscript, but there are no calls to WRITE_FORM for either of those two windows. Does the CHECK window have any special properties that (should) cause it to always print at the end, and could I then apply those properties to these other two windows to fix the problem?
    As for the debugger, I guess what I should be looking for is the moment when the check gets printed, and see what happened exactly before that triggered it? Then see if I can delay that trigger until the end?

  • Vendor Invoice Holds

    My client has a process called u201CVendor Holdsu201D where in they hold newer invoices totaling up to a set amount limit. They pay only oldest of the invoices that exceed that amount limit. This process is used for safeguarding themselves against vendoru2019s debit balance. Here is an example:
    Invoice-1: $100 (Due on Oct/1)
    Invoice-2: $200 (Due on Oct/2)
    Invoice-3: $300 (Due on Oct/3)
    Invoice-4: $400 (Due on Oct/4)
    Invoice-5: $500 (Due on Oct/5)
    Vendor Hold limit: $1200
    In this example, when they process the payment run on Oct/5th, only Invoice-1 and Invoice-2 are paid because they are older and they exceed the hold limit. The remaining 3 invoices are blocked during that payment run and the block is released once that particular payment run is completed.
    (1)     Is there any standard functionality in SAP that can support this vendor hold process?
    (2)     Is there a transaction in SAP using which we can block/unblock multiple FI-AP vendor invoices?
    regards
    mohammed

    Hi,
    It is not a standard SAP functionality for vendor hold
    During invoice verification in MIRO you can hold the invoice,the person who is processing has to post the invoice  later based on the invocie number only.
    (OR)
    During payment run some one has to check and physically pay to the vendor.
    It is difficult to do  in SAP
    Best solution: The person who is posting the bills in SAP has to control
    G.Ganesh Kumar

  • Vendor Invoice amount allowing any higher value

    Hi
    1. While I do a vendor invoice for a PO, the document balance field (DIFFERENZ) is showing in Green light even before I input the amount in the Amount field.(WRBTR)
    2. And also, if the total invoice amount is USD 1000.00, the amount field is allowing any higher amount. How do i control that ?
    Thanks
    Maruthi Ram

    Hi,
    U can Block Invoice for Higher Limit as well as lower Limit.
    Go to SPRO -->  MM --> Logistic Invoice --> Invoice Block
    Here Go to Company Code and PP - Price Variance and maintain Upper and lower Limit.
    Hope Help U !
    Regards,
    Pardeep Malik

  • Steps to upload vendor invoice(tcode fb60) in bdc

    hi, iam srinivas can any one plz send me the steps to upload veneor invoice tcode is (fb60).i dont want the code but i want the steps to create .
    thanks and regards.
    Srinivas.

    refer this site.
    FI_AP_FBR2_Post_With_Reference (FBR2)
    Business Process Description Overview
    Use this procedure to copy a previously posted non-PO invoice document that uses many of the same values.
    This may help reduce data entry time if used correctly.  For example, the library invoice vouchers that have the same vendor but many invoices on them might be a good example of when to use this transaction code.
    Trigger
    Perform this procedure when there is an invoice that needs to have data entered where most of the fields are the same as a prior invoice document already entered in the system.
    Prerequisites
    ·         Security Role:  AP_DIR_INV_ENTRY
    ·         An FB60 invoice has already been data entered.
    Menu Path
    None
    Transaction Code
    FBR2
    Tips and Tricks
    ·         If you would like to save this transaction under your "Favorites" folder, right-click on the "Favorites" folder, select "Insert Transaction" and type in this t-code when the box appears.
    ·         You may use the transaction code:  search_sap_menu to search for a transaction codes menu path.
    Procedure
    Enter Vendor Invoice: Company Code PUR
    Typically the FBR2 - Post With Reference transaction is accessed from the Financial transaction code that you just used.  For Accounts Payable, typically we would use the FB60 transaction code to enter invoices that are not PO-related.  After you have entered an invoice, you can now post a second invoice.  Feel free to post an invoice in DEV to the Vendor ID number:  31.  Choose today's date as the Invoice Date.  Enter a Vendor Invoice in the Reference Field. Enter $1000 as the Amount.  Enter a Text that you want to show on the remittance advice to the vendor.  Choose your own GL Account and Cost Center.  Enter 21010000 as the Fund.  Make sure to also enter $1000 in the Amount in doc. curr. field.
        Please be aware that the FB60 screenshot above is using the ZPurdue Variant so unless you are also using that same variant the order of your columns may differ.
        Refer to FB60 documentation for more information regarding entering a non-PO related invoice.
        After an invoice has been entered, you may proceed to step 1.  If you prefer not to enter an FB60 invoice then after you open FB60, immediately do step 1, but enter "1900001354" in the Document Number field.
    1.       Select Goto Post with reference           Shift+F9 to go to the FBR2 transaction.
    Post Document: Header Data
    The document number you just entered in FB60 should now display.  If you did not first enter your own FB60 invoice, please enter 1900001354 in the Document Number field.  Make sure Company Code is PUR and Fiscal Year is 2007.
        If you did enter your own FB60 invoice to reference to, please be aware that the data entry fields will have different content in the screen shots than what you are seeing on your screen.
    2.       Click  or the "Enter" key to proceed.
    Post Document: Header Data
    Because we want to avoid paying the same invoice twice, we must change the reference field to another Vendor Invoice text.
    3.       As required, complete/review the following fields:
    Field Name
    R/O/C
    Description
    Reference
    R
    Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP.  Any SAP-posted document number can be used as a "reference" when entering a new document.
    Example:          VENDORINVOICE#2
        Your reference number should be different than the one above.  Otherwise, the system will think you are entering a duplicate invoice.  Please change your text slightly.
    Post Document: Header Data
    4.       Click  or the "Enter" key to proceed.
    Post Document Display Overview
    You are now viewing the document overview screen.
    5.       Double-click  to open that line item.
    Post Document Correct Vendor item
    When you open the Vendor line item, you may change the Text field here to change what appears on the remittance advice.
    6.       As required, complete/review the following fields:
    Field Name
    R/O/C
    Description
    Text
    O
    Description field for an entry.
    Example:          prints on remittance advice - for second invoice
    Post Document Correct Vendor item
    7.       Click  to return to the document overview screen.
    Post Document Display Overview
    The document overview screen.
    8.       Click  to post this second invoice which has the same fields as the original except a different vendor invoice number and a different remittance advice text.
    Information
    Pending upon your user settings, you may not get this pop up box, but just a message in the bottom left hand corner of the screen.
    9.       Click  to close the box.
    Enter Vendor Invoice: Company Code PUR
    Because you used the menu (Goto Post with reference) from FB60 to access the FBR2 transaction code, you are then returned to the FB60 transaction after you have posted the invoice.
    10.     Another way to access FBR2 is to just type the t-code in the field at the top of the screen.  As required, complete/review the following fields:
    Field Name
    R/O/C
    Description
    Transaction Code
    R
    A unique four-character (in most cases) identification assigned to each SAP transaction based on its purpose.
    Example:          /nfbr2
    11.     Click  or the "Enter" key to proceed.
    Post Document: Header Data
    The FBR2 transaction code opens with the last document number entered as the default.
    12.     Click  or the "Enter" key to proceed.
    Post Document: Header Data
    This time we will change the vendor number
    13.     Change the Reference field.  As required, complete/review the following fields:
    Field Name
    R/O/C
    Description
    Reference
    R
    Allows for further clarification of an entry by reference to other sources of information, either internal or external to SAP.  Any SAP-posted document number can be used as a "reference" when entering a new document.
    Example:          VENDORINVOICE
        Your reference number should be different than the one above.  Otherwise, the system will think you are entering a duplicate invoice.  Please change your text slightly.
    Post Document: Header Data
    14.     As required, complete/review the following fields:
    Field Name
    R/O/C
    Description
    Account
    R
    Unique identification number. SAP uses several kinds of accounts. SAP's general ledger accounts are similar to standard in most accounting systems. SAP also uses sub-ledger accounts for customers (accounts receivable), vendors (accounts payable), and assets (asset accounts). These sub-ledger accounts roll-up to a general ledger account.
    Example:          5000129
        Vendor 5000129 in DEV has withholding tax applied to it in the vendor master.
    Post Document: Header Data
    15.     Click  or the "Enter" key to proceed.
    Post Document Add Vendor item
    If the vendor invoice date was a date in the past, the due date for pay immediately will be in the past.  You may get the above informational message to alert you of the date.  If you do, just hit the "Enter" key to acknowledge it.
    Enter Withholding Tax Information
    Because this vendor has withholding tax information in its vendor master, you will receive this popup up box.
    16.     Click  to accept it.
        Refer to the Tax Department for more information regarding withholding tax.
    Post Document Display Overview
    You should now see the document overview screen.  If you do not, then click on .
    17.     Double-click  OR click  to open it.
    Post Document Correct Vendor item
    18.     As required, complete/review the following fields:
    Field Name
    R/O/C
    Description
    Text
    O
    Description field for an entry.
    Example:          change remittance advice text
    Post Document Correct Vendor item
    19.     Click  to view that Vendor's Withholding tax information again.
    Enter Withholding Tax Information
        If for some reason, for this invoice the vendor should not have any withholdings, you would enter a 0.00 in both the W/Tax Base and W/Tax Amt fields.
        When using the FBR2 to change withholding tax amounts, you need to be very careful if using this new invoice as the "reference" invoice for the next one.  For example, if you put 0.00 in both W/Tax Base and W/Tax Amt fields then if this is the reference invoice, those 0.00 amounts will automatically be applied to the next; however, you won't see the 0.00 displayed.  The 0.00 will be assumed.
    20.     Click  to close the box.
    Post Document Correct Vendor item
    21.     Click  to post the invoice.
    Post Document: Header Data
    Your new document number will display in the bottom left hand corner.  Pending upon your user settings, you may also get a pop up box to acknowledge.
    You have posted another invoice, but this time you changed the vendor ID used, the vendor invoice, and the text on the remittance advice.
        Notice that the "Document Number" field now defaults to the newly posted invoice number.
        Because you entered FBR2 in the transaction code field to access this screen, when you post an invoice you are returned to the beginning of the FBR2 screen.  Remember, when you accessed it from the menu line of FB60?  If you access it that way, you are then returned to FB60 after the Post with Reference document is posted.
    22.     Because you are returned to the start of FBR2 again, you may just click  or the "Enter" key to proceed.
    Post Document: Header Data
    Now you are at the start of entering a new invoice again.
    23.     Click  to return to the main menu without finishing the process of entering another invoice.
    24.     You have completed this transaction.
    Result
    You have posted two documents by using a reference document.  This reduced the data entry required since it defaults the fields from the reference document.
    Comments
    Be very careful using this transaction if you change withholding tax amounts.
    To see the results/calculations of discounts and withholdings, you must run F110, the Payment Program.
    http://www.purdue.edu/onepurduehelp/content/fi_ap_fbr2_post_with_reference/wi/html/index.htm
    Message was edited by:
            Karthikeyan Pandurangan
    Message was edited by:
            Karthikeyan Pandurangan

  • Cross Company Sales Automatic Vendor Invoice Not Created

    Hi,
    I have an issue in Cross company Sales Scenario (Inter company Sales),
    During the Intercompany Invoice we can trigger output RD04 to create Automatic Vendor Invoice in the Ordering Company.
    I have done the necessary configuration for creating Idoc (RD04), FI & MM.
    I could able to create an Idoc successfully and the status of the Idoc is 53.
    However when I check the Vendor Invoice in the Ordering Company T.Code FBL1N, system gives me message that no items found for the Vendor.
    I request please let me know me what configuration I have to do to create Cross Company Sales Automatic Vendor Invoice
    Regards,
    Murali
    Edited by: Murali Mikkili on Jul 27, 2008 9:05 AM
    Edited by: Murali Mikkili on Jul 28, 2008 11:49 AM

    Hi Daniel,
    Both the company codes should be assigned to the same company.
    Clearing accounts must be defined in every company code before a cross-company code transaction may be carried out. The clearing accounts may be G/L accounts, customer, or vendor accounts.
    In the configuration you must assign clearing accounts to every possible combination of two company codes to allow cross-company code postings between these combinations
    To reduce the number of clearing accounts, you can use just one company code as the clearing company code. In this case, you only have to assign clearing accounts to every combination of the clearing company code
    In T-code OBYA
    For ex: company code 1000 clearing account 12345 is same for Debit and credit
    Company code 2000 Clearing account 67890 is same for debit and credit
    Posting keys must be assigned to the clearing accounts to identify their account
    types.
    Hope this helps you to solve your probelm.
    Regards,
    Mir

  • Profit center splitting - Intercompany FB60 - Sales/Use Tax Vendor invoices

    We are implementing Use Tax calculations for Vendor invoices and are stuck on an issue with profit center splitting when entering intercompany AP transactions (FB60).     The tax postings of the non-leading company are being split between the two company profit centers.
    When posting a vendor invoice with more than one company the tax items of the leading company are posting with the correct profit center but tax items if the non-leading company are splitting between the profit centers of the two companies.   The total amount of the tax is still correct, just part of it is posted to the wrong profit center. 
    We are assuming this is a document splitting issue but changes to document splitting configuration did not get the desired effect of not splitting the tax accounts.   
    Are there any suggestions of particular areas of document splitting that we should look into or other areas that might be causing this profit center splitting for the tax items?  Any ideas would be appreciated.
    Thanks,
    Jeff

    Hi Murlidhar,
    Here's a sample transaction with the problem results we are seeing.  Normal AP transactions are posting fine, it is only when Sales/use tax is added that we are finding a problem with the profit center splitting.
    Entering a two line FB60 transaction under company 0001.
    Line 1  - Company 0001, profit center 220020, $100
    Line 2 - Company  0002, profit center 250020, $100
    SAP sends this transaction to our external tax system which returns the tax amounts to accrue for each line item.
    Line 1 $7.30 for company 0001
    Line 2 $9.05 for company 0002
    When the transaction is then viewed in General Ledger View we see the tax amount of $7.30 posting to profit center 220020 but the tax amount for line 2 of $9.05 is evenly divided between profit centers 220020 and 250020. 
    The $9.05 should be posting only to profit center 250020 as the profit center assigned to line 2 of the transaction.
    Thanks,
    Jeff

Maybe you are looking for