Duplication Check for Vendor Invoices
Can we check for duplicate invoices in SAP
Regards
Satish
Hi
The configuration settings are made in
IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate Invoice
In vendor master you need to maintain the tick for Duplicate Invoice Check
Thanks & Best Regards
Sanil K Bhandari
Similar Messages
-
Configuring double invoice check for vendor invoices posted through FB60
Dear all
Can anyone tell me how to configure double invoice check for vendor invoices posted through FB60.
for miro documents..we can use Tcode OMRDC
Is there any such tcode which can be used for configuring fi invoices for double checking..
regards
ExpertiaDear Expertia,
In FI,when checking for duplicated invoices, the system compares the
following :Vendor, currency, company code, gross amount of the invoice,
reference document number and Invoice document date.
SAP Note 305201 clarifies this in a more details; please read it.
The following fields must be identical for Duplicate invoice check
Company code (BUKRS)
Vendor number (LIFNR)
Currency (WAERS)
Reference number (XBLNR)
Amount in document currency (WRBTR)
Document date (BLDAT)
If the document is having any one of the above filed different then the
system does not consider it as a duplicate invoice.
Also It will check duplicate invoice check in vendor master data and
in posting key is there check box selected for sales related
The setting you making in OMRDC i.e Materials management->Logistics
Invoice Verification->Incoming Invoice ->Set Check for Duplicate
Invoices is only valid for MM and not FI invoices posted via FB60/FB65
You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
in the relevant vendor master record (transaction FK03).
Please also check, that message F5 117 has been set correctly in the
IMG using this path:
Financial Accounting -> Financial Accounting Global Settings ->
Document -> Default Values for Document Processing -> Change Message
Control for Document Control For Document Processing
Finally & mainly, go to the relevant posting key is defined as sales
related in transaction OB41. You have to flag this field if the
duplicate invoice check should work.
I hope this helps You.
mauri -
MM-Check Double Invoice functionality for Vendor Invoices
Dear All,
How Check Double Invoice functionality for Vendor Invoices can be implemented in SAP?
We have implemented Check double invoice with the standara sttings for it however if i give my referenece text differently it will aloow me to post double invoices and against vendor open items are shown for payment?
Is there any other efficient way to do it?
Thanks and Regards
Shrinivasdear SAPian friend,
go through the below link and you will find the solution with the screenshots.
http://sapfunctional.com/MM/Duplicate/Invoices.htm
U can also do the setting using the SPRO t-code:-
path is
>>SPRO
>>SAP Reference IMG
>>Materials Management
>>Logistics Invoice Verification
>>Incoming Invoice
>>Set check for duplicate invoices -
Double Invoice Check for Vendors
Hi
How can we create a check for Double Invoices for Vendors?
regards
RupalHI
Pls follow the path to set the status for Double Invoice Check
IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate Invoices
Moreever, in vendor master, you need to maintain the double invoice check tick in the company code data. I suggest you make this as a compulsory field in Field Status group for all your vendor account groups.
Thanks & Regards
Sanil K Bhandari -
Hi,
1) Can someone explain me what is meant by "Check for double invoices " field in vendor master and its importance?
2) I am also confused between "Check for double invoices " filed in vendor master, and set check for Invoce duplication in "SPRO -> SAP Reference IMG -> Materials Management -> Logistics Invoice Verification -> Incoming Invoice -> Set check for duplicate invoices". Can some one exaplin that too?Hi,
1) Can someone explain me what is meant by "Check for double invoices " field in vendor master and its importance?
This field for vendor reference while doing MIRO
2) I am also confused between "Check for double invoices " filed in vendor master, and set check for Invoce duplication in "SPRO -> SAP Reference IMG -> Materials Management -> Logistics Invoice Verification -> Incoming Invoice -> Set check for duplicate invoices". Can some one explain that too?
here you can define criteria for duplicate invoice including reference field also
In vendor master press F1 for duplicate invoice indicator ,you will get good info with Example.
how it work
check following link also
[http://help.sap.com/saphelp_470/helpdata/en/ce/4f3e39ea3aee02e10000000a114084/content.htm]
Regards
kailas Ugale
Edited by: kailasugale on Jan 16, 2012 2:43 PM -
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 -
Validation Check - Duplicate vendor Invoices
Hi,
We have a situation where the Duplicate Vendor Invoices have been entered by the users, bearing the same date and reference nos. as the original ones. When we checked we observed that, the system gives the warning message, but the same is ignored by the users. To prevent the same from happening again, we want to convert the warning message into the error message.
Could any one guide as to how can we set up the validation checks, such that the system would throw an error message. In the vendor masters, we have set up the check for Duplicate Invoices.
Thanks in advance.
Best Regards,Hi,
If you already know the message number, then go to T.code:OBA5 or
T.code:SE91 (if its an custom message class) and change the message from waring to Error.
If you are not aware of Message, and try to post a duplicate invoice & when the warning message comes, double click on the same, it will give you the message number.
This will resolve your issue.
Please let me know the result of the same
Thanks
Kalyan -
Reject duplicate References for Vendor Invoices
I have a requirement to check for duplicate invoices. I have put in the neccesary config to make the reference Field mandatory, I have also checked the 'Check duplicate Invoice" field in the vendor master and the 'set check for duplicate invoice' in Logistic Invoice Verification (IMG). All this works fine if I enter the same invoice reference, date, amount and company Code. but if I change the invoice date for example, the system accepts the invoice. I dont want this- I want the system to reject the invoice if if has the same reference irrespective of other parameters. that is, the control should be on the reference field (the same kind of control we have by making VAT reg No REQUIRED in the vendor master). How may i do this please??
Hi Joe,
Can you let me know you are posting PO invoice or non PO Invoice.
Thanks,
Venkatesh -
SAP Workflow for vendor invoice is posting into past?
Dear experts
I have a heavy problems with the workflow for vendor invoices. The following example demonstrates it:
I have created a vendor invoice on 1st of December 2011.The responsible person has checked and released this invoice on 3rd January 2012. In Customizing it is setup that posting date will be overwritten with system date.
Does anybody has an idea why it is not posted in January 2012?
What does the workflow? It is posting that invoice with posting date 1st December 2011 not with 3rd January. If I have a closer look into the head of the SAP document the following parameters are shown: document date: 1st December, posting date: 1st December, entry date: 3rd January.
Does anybody has an idea why entry date is 3rd January?
Thanks in advance
UdoDear expert
It is not standard behavior for the posting date to overwrite the document date - at least its not something that I've ever come across. I'm wondering if there is a custom substitution on your system that is overwriting the document date . Check t-code OBBH. The substitution is most likely at the document header level.
Regards
Ajeesh.s -
My client required Approval for Vendor Invoice Payment from senior person. How can i configured this scenario in sap AP?
Pls ReplyHi,
Please check this link:
[Workflow for Payment Release|http://www.google.co.in/url?sa=t&rct=j&q=workflow%20for%20payment%20release%20sap&source=web&cd=1&ved=0CBsQFjAA&url=http%3A%2F%2Fhelp.sap.com%2Fprintdocu%2Fcore%2FPrint46c%2Fen%2Fdata%2Fpdf%2FFIBP%2FFI-AP-AP-RP.pdf&ei=QdjETqe6Ds-xhAfv6NSEDg&usg=AFQjCNGlK2kUdPUyvPIgG32Ulni3ks9tuA&cad=rja]
Regards,
Jigar -
Standard interfaces for vendor invoice and salary posting
Hi all,
Our customer is asking for a standard interface for vendor invoices (not purchase invoices, only for invoices entered in FB60), if they could have a CSV file from vendor and import that to SAP. Is there a standard functionality or do we have to build an own interface?
They also ask if there is a standard interface for salary file so they can tell the company that create the salary file that they should use a standard format or do we need o to create an interface there to?
Thanks in advance!
BR LHi,
You can either go with INVOICE01 or INVOICE02, As per the requirement you can check with the Function module attach with the idoc type, and whether it is providing the appropriate functionallity or not.
Thanks & Regards,
Navneet Chaubey -
Standard idoc type for Vendor invoices
Hi All,
Can anyone tell me if any <b>standard idoc type for Vendor invoice(Cleared items)</b> exists and if any standard report is there to populate and distribute that idoc?
I want the fields bukrs,belnr,lifnr,bldat,cpudt,zfbdt,zterm,xblnr,waers,dmbtr and mwsts in that standard IDOC.
Thanks in advanceHi,
check this IDOC types..
SINGLEREMUNRQS_CREATE01 "46A
SINGLEREMUNRQS_CREATE02 "620
regards
vijay -
Print-off the scanned images for vendor invoices
Required report.
Print-off the scanned images for vendor invoices
Basically, his selection screen will be:
Vendor Invoice XXXXXXXXXX to XXXXXXXXXX
Once the user executes the program a list of invoices is presented to the screen.
Then the user will be able to select one or several of these invoices and click a print button.
However, the attachments are stored in Adobe .pdf format.
Kind Regards
Mark H,Hi,
Write a report to fetch the data from Tables RBKP and RSEG for the vendor INvoices, based on the Invoice No(BELNR) entered on the Selection screen.
display them with the required fields on the first list. Take a single CHAR field in the internal table for CHECK BOX and display that Internal Table fields.
Keep buttons (SELECT and PRINT) on the MENU of the output screen for processing the selected records on the output and printing the selected records in the interactive report using AT USER-COMMAND function.
reward if useful
regards,
ANJI -
Problem in Set Check for Duplicate Invoices
Hi,
I have did all the required setting s for check duplicate invoice , but when i do miro , its not giving any error or warning msge.. i did all the config as per blw link..
FYI- in migo, i have entered the 3434 as a invoice ref # in delveriy note column and while doing miro , i have entered 3434 in ref column and give the 3434 as a dlvery note # in item tab .. but its not giving any error?
Pls guide, where the mistake has gone wrongly??
Problem in Set Check for Duplicate Invoices
Edited by: UJ on May 15, 2009 1:45 PMHello,
Hope you have done all the required configurations for the checking of double invoice and ticked the vendor for the double invoice checking in vendor master record.
You have to understand the way the system does the double invoice check.
As per the configuration, if the system identifies an invoice for a vendor whose double invoice check is activated, at the time of MIRO, system will update a separate table.
So system will check for the double invoice entry among the invoices entered after making the tick in the vendor master.
i meant to say that, if you are introducing this double invoice check in between the transactions, the check will be valid only for the invoices entered after the activation of double invoice check.
Regards -
Set Check for Duplicate Invoices.
Hi,
what is the difference if is set "<b>Set Check for Duplicate Invoices</b>"
in MIRO?
Best regardsHI,
This check will prevent incoming invoices being accidentally entered and paid more than once.
You can choose whether to activate or deactivate the check criteria of company code, reference document number and invoice date for each company code. The more criteria that you activate, the lower the probability of the system finding a duplicate invoice.
The company code check makes sense if you work with more than one company code.
Depending on the reference document number entry, the system checks as follows:
1. If you have entered a reference document number, the system checks whether the invoice matches in the following attributes:
Company code
Vendor
Currency
Invoice date
Reference document number
2. If you have not entered a reference document number, the system
3. checks whether the invoice matches in the following attributes:
Company code
Vendor
Currency
Invoice date
Amount in
document currency
Depending on the system settings, a warning message or an error message appears if the system finds an invoice that matches all attributes.
Requirements
The field Chk double inv. (Check for duplicate invoice) must be flagged on the Accounting view in the vendor master record.
Regards
Aasif
Maybe you are looking for
-
How can I pass a value from Client to EntityImpl class?
Hi everyone, I am using ADF BC to develop my Application. I want to do something in the EntityImpl class. My job needs a value from Client. I can't find any way to slove the problem. Is there anyone have an ideal, please tell me. Thanks, Tuan Vu Minh
-
Problems with import from textfile
Hi We are experiencing problems with importing tables from a text-file. We are using Designer 6i (NT) release 2. Some of the column sequences are lost others are changed. Foreign keys are lost if the referenced table is after in alphbetical order! No
-
Double charge for a 1-year export pdf membership
I want to cancel one of the charges and I'm struggling with the adobe system to cancel one of the memberships. How do I complete a cancellation?
-
Airport 802.1x w/ TLS Authentication Certificate Problem
Trying to set up an Airport connection to my company's Wireless network. I've gone into the Internet Connect application and tried to create a new 802.1x connection. I named the connection, choose Airport as the port, provided my username and passwor
-
Creating iPhoto smart album with criteria based on another smart album
When I create Smart Playlists in iTunes, I can set one of the criteria to include/exclude items based on a different smart playlist. For example, Smart Playlist 1=all songs by artist a, b, c, d, etc. Smart Playlist 2=all songs where "genre=Holiday" S