New Date field for Vendor Invoices

The business would like the ability to enter an additional date (date invoice is received by AP) for vendor invoices. There doesn't seem to be any additional date fields available in the BSEG/BKPF tables. We want the field available in the TCodes where vendor invoices are entered or parked (FB60, FB65, FV60, FV65, MIRO) We are on ECC 6.0. Can anyone help answer the following questions:
Are there fields available for this that I am not aware of
Have others added new custom fields to any of the above TCodes?
If it is possible, is the field created in a custom table? Would we need to create new custom TCodes for the 5 programs used to enter invoices?
Any details or suggestions would be greatly appreciated.
Thank you
Cindy C

Hi Cynthia
You can use the Header text fields (XREF or XBLNR) to capture this info
You can make use of the XREF1 to 3 fields in vendor line item as well to capture this info. Make these fields mandatory in the field status group or use a validation in GGB0
Another option is you can add a custom field to BKPF table and it will be visible to you in all the transactions you need
Br. Ajay M

Similar Messages

Field for Vendor Invoice status

Hi guys,
We have to fetch the vendor invoice status for the given invoice.
I checked with the table RBKP there the field RBSTAT shows the status, but it shows only status like (PARK, POSTED etc)
but the requirement is to get the status like (PAID, VOID, OPEN etc).
I searched through the SDN and SAP, did not found the exact solution.
Is there is any field for that, or any code sample/ logic any one have..
Thanks,
Anmol.

Clossing the threat,
tried using BSIK and BSAK used payment block from BSIK.
If entry exist in BSAK-paid
if A in payment block - Blocked
if payment block is initial - invoice only

How system will automatically populate clearing date field for invoices paid similar to when payments are made to the vendors

Hi SAP Gurus,
Could you help me on this, How system will automatically populate clearing date field for invoices paid similar to when payments are made to the vendors.
Regards
Mohan

Hi Ramakrishnappa,
If you clear the invoice against payment, then the invoice clearing date would be payment document posting date.
Regards,
Mukthar

How to add a new data element for existing table filed(Primary key field)

Hi Experts,
How to add a new data element for existing table field(Primary key field)
For this filed ther is no foreign key relation ships and even check table.
while activating table it is giving message like below.
can you help any one to solve this and wil steps to add new dataelement for existing primary key filed of a table.
Check table (NAMING SPACE/TABLE NAME(EX:/TC/VENDOR)) (username/19.02.10/03:29)
Primary key change not permitted for value table /TC/VENDOR
Check on table /TC/VENDOR resulted in errors
Thanks
Ravi

Hi,
Easiest way is to download the table eg into an Excel table (if possible) or text table. Drop the table from the database. Build your table with the new key field. Build the database table again and fill it.
You can do it also over the database into a new table. Drop the old one. Build the enhanced one and fill it. Afterwards drop your (temporary) table.
Maybe there are other ways, but this works.
Success,
Rob

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

Solved - Group Fields for Vendor Master Records in IMG

This was the solution.
The new field's data element I added to LFB1 did not have the "change document" field checked. I made that change and now that field shows up in IMG.
Hello all,
I added an append structure to the table LFB1. This structure has 1 field. I then created a "Modification-Free Enhancement of Vendor Master Record" to add the new LFB1 field to the vendor master screen, edit and display screens. This is the 3rd time I have done this. So far so good.
Now our functional analyst went into IMG to add this new LFB1 field to a "Group Fields for Vendor Master Records" which we have done 2 other times.
The new LFB1 field does not show up in the list of possible Table-fields.
There must be some other step I am missing.
Does any of this ring a bell? We are on version 4.7.
Thanks
Bruce
p.s.
This is the IMG path for adding 'Field Groups' to vendor master fields.
Financial Accounting/
Accounts Receivable and Accounts Payable/
Vendor Accounts/
Master Data/
Preparations for Creating Vendor Master Data/
Group Fields for Vendor Master Records
Edited by: Bruce Tjosvold on Nov 21, 2008 1:18 PM

Hi Vandana,
There are several tables that are contain Vendor Master related data which can be used for extraction to BW. Some of the tables which can be useful for you are:
LFA1 : Vendor Master (General Section)
LFM1 : Vendor master record purchasing organization data
LFBW : Vendor master record (withholding tax types) X
WYT3 : Partner Functions
LFBK : Vendor Master (Bank Details)
LFB1: Vendor Master (Company Code)
ADRC: Addresses (Business Address Services)
ADR3: Fax Numbers (Business Address Services)
ADR6: SMTP Numbers (Business Address Services)
ADRT: Communication Data Text (Business Address Services)
You may use the Data sources mentioned in the previous update from Venky above namely :
0VENDOR_ATTR --- for master data attributes
0VENDOR_TEXTS -- For texts
Since the fields that you are using are from different tables so its better if you go for a Generic Data source where you can use the fields as per your requirement.
Thanks
Pawan
Edited by: pawan190187 on Aug 19, 2011 12:40 PM

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
Expertia

Dear 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

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

Strange behaviour of data field in Monthly Invoice.

Dear all,
I need to create new layout for monthly invoice using Print Layout Designer. I need to add the closing date procedure code, so I create new data field refering to the Closing Date Procedure file. This first data field shows many files. But when I want to add another new data field, this second data field only shows the Administration and Closing Date Procedure file. I need to add field from other file, but it does not appear.
If I delete the second data field, I can find the file I need in the first data field (the one supposed to be fill with closing date procedure code).
Is there any idea how to get other files in the second data field ?
By the way, I am using SBO version 2004.2b for Japanese user, and monthly invoice is an important function in Japan.
Thank you very much,
Emiliana

Thank you, Adele.
Do you also know how to display list of the variables used in the monthly invoice layout ?
Thanks again.
Emiliana

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
Udo

Dear 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

BAPI for Vendor invoice Park FV60

Hi All,
   Do you knwo any BAPI for vendor invoice Park through FV60, I have tried
   BAPI_INCOMINGINVOICE_PARK - Got struck where It is asking to pass teh PO data in Itme level, where as i have to uplaod only
   GLaccounts data.
and i tryed for another BAPI_ACC_DOCUMENT_POST   but is not working its not related to my requiremment it seems...
Can any one know better about the process to do this.. pleas let me know..?
Can anybody did the same, if ues please share with me... its very urgent it need it...
Thanks,

use bapi: BAPI_INCOMINGINVOICE_PARK

Shipment document number and cost document number for vendor invoice

Hi,
Given a Vendor invoice number ( MIRO) how to find out the shipment number and cost docuemnt number?
Regards,
Krishna prasad.

Hi,
Please try using SREL_GET_NEXT_RELATIONS. Please try to search on SDN and you should find an example fo this. The only thing you need to pass is the Business Object Name for Vendor Invoice number. Or if you have an alternal field like even PO that you can pass , that will be of great help as well.
You may want to take a look at:
SREL_DISPLAY_LIST_OF_NEIGHBORS
SREL_GET_NEXT_RELATIONS
Pls reward points if useful.
Thanks
Ganesh.S

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 advance

Hi,
check this IDOC types..
SINGLEREMUNRQS_CREATE01 "46A
SINGLEREMUNRQS_CREATE02 "620
regards
vijay

BAPI_ACC_INVOICE_RECEIPT_POST for vendor invoice posting

Hi ,
I am using BAPI_ACC_INVOICE_RECEIPT_POST for vendor invoice posting, I have made the header , and account paybale table
, can any body give link for the sample code or give me sample code.

continue....
FORM build_bapi_parameters2.
*Build account GL data for BAPI
wa_accountgl-itemno_acc   = 2.             " Line Item Number
wa_accountgl-gl_account   = '0000720300'. " GL Account Number
wa_accountgl-comp_code    = '0050'.        " Company Code
wa_accountgl-pstng_date   = '12012006'.    " Posting Date
wa_accountgl-doc_type     = 'KQ'.          " Document Type
wa_accountgl-fisc_year    = '2006'.        " Fiscal Year
wa_accountgl-fis_period   = '12'.          " Fiscal Period
wa_accountgl-item_text    = ''.            " Item Text
APPEND wa_accountgl TO accountgl.
CLEAR wa_accountgl.
*Build currency data for BAPI
wa_curramount-itemno_acc   = 2.             " Line Item Number
wa_curramount-curr_type    = '00'.          " Currency Type
wa_curramount-currency     = 'USD'.          " Currency Key
wa_curramount-currency_iso = 'USD'.         " ISO Code
wa_curramount-amt_doccur   = '5000.00'.     " Amount
wa_curramount-amt_base     = ''.            " Base Amount
APPEND wa_curramount TO curramount.
CLEAR wa_curramount.
ENDFORM.                    " build_bapi_parameters
FORM build_bapi_parameters3.
*Build account GL data for BAPI
wa_accountgl-itemno_acc   = 3.             " Line Item Number
wa_accountgl-gl_account   = '0000256166'. " GL Account Number
wa_accountgl-comp_code    = '0050'.        " Company Code
wa_accountgl-pstng_date   = '12012006'.    " Posting Date
wa_accountgl-doc_type     = 'KQ'.          " Document Type
wa_accountgl-fisc_year    = '2006'.        " Fiscal Year
wa_accountgl-fis_period   = '12'.          " Fiscal Period
wa_accountgl-item_text    = ''.            " Item Text
APPEND wa_accountgl TO accountgl.
CLEAR wa_accountgl.
*Build currency data for BAPI
wa_curramount-itemno_acc   = 3.             " Line Item Number
wa_curramount-curr_type    = '00'.          " Currency Type
wa_curramount-currency     = 'USD'.          " Currency Key
wa_curramount-currency_iso = 'USD'.         " ISO Code
wa_curramount-amt_doccur   = '-1000.00'.     " Amount
wa_curramount-amt_base     = ''.            " Base Amount
APPEND wa_curramount TO curramount.
CLEAR wa_curramount.
ENDFORM.               " build_bapi_parameters
Edited by: krupa jani on Aug 12, 2009 1:45 PM

BDC FOR VENDOR INVOICE FB60

Hi,
I need to make a BDC to upload transaction data for Vendor invoice thru fb60. Can someone help me with making this BDC. I have multiple invoice line items where G/L Accounts can be same for multiple line items.
plz any help soon will be appreciated ...

hi Raj,
Here a Example:
report ZTEST
no standard page heading line-size 255.
include bdcrecx1.
start-of-selection.
perform open_group.
perform bdc_dynpro using 'SAPMF05A' '1100'.
perform bdc_field using 'BDC_OKCODE'
'=DUMMY'.
perform bdc_field using 'RF05A-BUSCS'
'R'.
perform bdc_field using 'BDC_CURSOR'
'INVFO-XMWST'.
perform bdc_field using 'INVFO-ACCNT'
'4711'. "LIFNR
perform bdc_field using 'INVFO-BUDAT'
'07.07.2006'.
perform bdc_field using 'INVFO-WRBTR'
'1000'.
perform bdc_field using 'INVFO-WAERS'
'EUR'.
perform bdc_field using 'INVFO-XMWST'
'X'.
perform bdc_field using 'INVFO-MWSKZ'
'V4'.
perform bdc_dynpro using 'SAPMF05A' '1100'.
perform bdc_field using 'BDC_OKCODE'
'=BU'.
perform bdc_field using 'RF05A-BUSCS'
'R'.
perform bdc_field using 'BDC_CURSOR'
'INVFO-XBLNR'.
perform bdc_field using 'INVFO-ACCNT'
'4711'. "LIFNR
perform bdc_field using 'INVFO-XBLNR'
'test'.
perform bdc_field using 'INVFO-WRBTR'
'1.000,00'.
perform bdc_field using 'INVFO-XMWST'
'X'.
perform bdc_field using 'INVFO-MWSKZ'
'V4'.
perform bdc_dynpro using 'SAPMF05A' '1100'.
perform bdc_field using 'INVFO-BLDAT'
'07062006'.
perform bdc_field using 'INVFO-XBLNR'
'TEST'.
perform bdc_field using 'ACGL_ITEM-HKONT(01)'
'467000'.
perform bdc_field using 'ACGL_ITEM-WRBTR(01)'
' 1000'.
perform bdc_field using 'ACGL_ITEM-KOSTL(01)'
'1000'.
perform bdc_transaction using 'FB60'.
perform close_group.
OR Also u can use the
U can use the std batchinput RFBIBL00 (or a BAPI, like BAPI_ACC_DOCUMENT_POST ) instead of to write an own BDC program for FB60.
FB60 is enjoy trx and it couldn't support the BDC for all its functionalities.
For more infor abt the BDC
http://www.sap-img.com/abap/learning-bdc-programming.htm
Assing the points if helpfulll
ranjit
null
null

New Date field for Vendor Invoices

Similar Messages

Maybe you are looking for