J1IEX Vendor invoice status

Dear Experts
In j1iex vendor invoice  status is showing as in process even after posting has done. becuase it is showing under ParI and Part II posted items in J1I7 but status is not updated as posted
what could be the reasons
can any one tell me the solution
Thanks and Regards

Hi
  If you have only few documents for which though the part1 and part2 posting is done and status of the documents shows IN PROCESS then you can change the status of those documents at table level as P -POSTED. This is only recommended only you have limited documents. You have to change the status for both ITEM and as well as HEADER table.
  Also Please seach for SAP notes for this.
Regards
MBS

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

  • Invoice status info to vendors

    Hello All
    Is there any readymade package available from SAP, wherein the suppliers can check the invoice status.
    For e.g. Whether the Invoice has been entered in SAP, what is the due date, whether it is already paid, or if there is any block?
    Currently we are getting a high volume of calls to A/P support from vendors enquiring about the status of their invoices.
    We thought about making a BW report available to suppliers thru Enterprise portal, but are really unsure about the feasibility and cost required for extending the portal to thousands of suppliers.
    As a pilot we would like to start with the indirect suppliers.
    Regards
    Kedar

    Thanks Krithika and Sanjeev
    1) We are concerned with not only SUS vendors (which are few) , but all the vendors.
    2) Regarding creating zprog and sending email to suppliers, we are rather looking at a more real time
    system , where the suppliers can themselves , check the status.
    For e.g. even Transaction FBL1N, if available to each supplier over internet could be very helpful.
    ( as long as they are restricted to check only their own invoices)
    Any pointers to such a system would be appreciated
    Regards
    Kedar

  • Wrong Vendor Invoice Posting Due To Wrong Excise Tax Code

    Hi:
    We have created a Purchase Order as per below:
    Qty     10
    Price     100
    Value     1000
    Excsie 10%     0
    Cess     0
    SECess     0
    Value+Excise     1000
    VAT 5%     50
    ValueExciseVAT     1050
    (Please note that the PO was to be created in the following fashion as the Material was excisable)
    Qty     10
    Price     100
    Value     1000
    Excsie 10%     100
    Cess     2
    SECess     1
    Value+Excise     1103
    VAT 5%     55.15
    ValueExciseVAT     1158.15
    We did the Goods Receipt and the FI Document is as follows:
    24340000     Paper Stock     BSX     1,000.00
    13110100     GR/IR-ext proc     WRX     1,000.00-
    We did the Vendor Invoice Posting as follows:
    100183     SIEGWERK INDIA PVT LTD (SICPA)     KBS     1,050.00-
    13110100     GR/IR-ext proc     WRX     1,000.00
    24638100     VAT Recoverable     JP5     50.00
    The Material was issued to Cost Centre
    Later at the time of Excise Invoice posting, we came to know that the Tax Code in the Purchase Order was wrong. Here in our case, we have created separate Tax Code based on Excise Percentage. For example, V1 for VAT 5%, E1 for VAT %+Excise 10.3%.
    To post the excise invoice, we changed the Tax Code in the Purchase Order and did the Excise Posting as follows:
    24820020     CENVAT Inp SHEcess     1.00
    24820000     CENVAT Inp BED     100.00
    24820010     CENVAT InpEcess     2.00
    13113920     CENVAT clearing     103.00-
    My Question:
    a. Is this the correct way?
    b. What about the following FI Entries which got generated when we do the MIRO with actual Tax Code:
    100183     SIEGWERK INDIA PVT LTD (SICPA)     KBS     1,158.15-
    13110100     GR/IR-ext proc     WRX     1,000.00
    13113920     CENVAT clearing     JI1     100.00
    13113920     CENVAT clearing     VS9     2.00
    13113920     CENVAT clearing     JI6     1.00
    24638100     VAT Recoverable     JP5     55.15
    Please guide.
    Regards,

    Thanks Sanjoo for the reply.
    Here my worry is the all the postings have been made in SAP in Production Client.
    The User has already done the postings for MIRO & J1IEX without informing to us, and the volume of transactions is huge.
    We are in the back-log mode and at this stage, we can't go for any reversal . I am Just exploring the alternatives.
    Our MM & FI Users are little bit smart, when ever they do some mistake, they simply say "we will pass a JV" and we are not able to educate them that the JV is not a Solution. Please guide.
    Regards,
    PK

  • 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                  

  • Vendor invoices to internal order

    Hi Experts,
    Create Asset Under Construction using asset class for AUC .
    Create Vendor invoices to Internal Order (not to asset account) F-90
    How can i create the vendor invoice to internal order..please send the transacction code and procedure ..with one example.
    this is urgent ..
    Regards
    msr

    Dear,
    in F-90 only you can post the asset aquisition.
    You should do it in F-43.
    Before doing invoice for AUC - please check the GL account assign for AUC.where check the field status group internal order field it should be optional/required.......
    After that go for F-43 ther you can find a internal order field as
    Order
    Don,t forget to assign points,if it helps you.
    Rgds,
    Madhuri

  • 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

  • Processing options for EDI vendor Invoices

    I'm trying to get a better understanding of what my options are for processing EDI vendor invoices and would appreciate some help.  I'm using  message type INVOIC02 with process code INVL and in configuration I've set the processing option in table T076S to 4 (tolerence corresponding to online processing).  When an invoice fails either the vendor specific tolerance check or the payment blocking checks the invoice gets parked with error status 3.  This is behaving as I would expect.  The issue I have is the price on the parked invoice is the price from the PO and not the price from the EDI segment.  Is there anyway to change this?  This makes it difficult to analyze the cause of the error without going back to the Idoc segments.  I've tried playing with the other processing options but they also enter the PO price in the parked invoice.  If it's not possible to change this are there any tricks that i'm missing that can help the users analyze the cause of the errors without going back into the idoc?
    thanks,

    If anyone has any expierence with this, I would appreciate any advice you may have.
    thanks,

  • Open vendor invoices not picked up in F-44, F-53

    Hi All,
    I have a problem here. Many vendor invoices aren't being seen at all in the F-44, F-53 screens and I'm not being able to make payments or clear invoices against credit memos. What could possibly be the reason.
    I tried comparing these invoices to others that did get picked up by the system and I see no difference in them except for the fact that all these invoices in error were posted on 31st Oct. What could have gone wrong and where?
    Thanks & Regards,
    Tejas

    hi,
    check the status of the document u are clearing.
    It seems they are already cleared as credit memo is issued using clear functions.
    Check the account with open items does it display there.
    Regards,
    Atul

  • Excise invoice status P in table

    Hi
    for excise invoice If i display excise invoice in J1IEX ,status is in process,But accounting docuement is generated
    If I check table J_1IEXDTL.STATUS is posted
    If check same in J_1IEXCHDR SATUS is not posted
    so question is which is true,whiel doing MIRO user not get any message like part2 is not done
    If status is in process ,then how accounting docuement is generated for same
    Note: part2 post through J1IEX
    Regards
    kailas Ugale
    Edited by: kailasugale on Jul 19, 2011 5:10 PM

    Hi
    I am getting part1 and part2 entries correct,still status not change of docuement,in J1IEX and MIGO status showing
    " In process"
    Regards
    kailas ugale

  • Vendor Invoice Output to non-SAP Application

    Hello,
      We want to send the posting status of Vendor Invoices to a non-SAP application. What is the appropriate output condition type, Message type and IDOC type that we can use?
    Thanks,
    Venu

    The remittance advice/payment order (820 in ANSI X12, PAYADV in EDIFACT) is a transaction that can be
    used to advise a payee about a payment that has been made to the payee's account either by a payment
    order or through other means (inbound).
    PEXR2001 (IDoc)
    REMADV (message)
    hope this help
    Regards
    Eduardo Chagas

  • Getting error while posting vendor invoice

    Hi, I was trying to post a vendor invoice and am getting an error  "Balancing field "Profit Center" in line item 001 not filled"
    I have changed the field status of the posting key and the reconciliation account but am still getting the same message.
    Can anyone please help?

    Hi,
      check the below links
    balancing field "profit center" in line item 001 not filled"
    Balancing field "profit center" in line item 001 not filled
    This is a frequently asked question. Please search in the forums before you post a thread.
    Regards,
    Radhika.

  • PO field not appearing while posting Vendor Invoice

    Hello,
    While posting an entry using FB01/ F-43, for posting key 31(Vendor Invoice), despite making Purchasing Document (Purchase Order) field optional in the field status group of both the posting key 31 as well as the Reconciliation (GL) Account, the Purchasing Document field is not appearing. Please provide the solution if it's possible to get this field while posting the entry.
    Thanks and Regards,
    Sumita

    If you try to book vendor invoice through F-43 or FB01 t codes, then, the system would always show PO open for invoice verification.
    In case of a PO, IV should always be done through MIRO t code.
    Thanks.
    VS

  • 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.

  • A workflow for a new MM vendor invoice showing the error.

    We have detected the following strange behaviour in our workflow runtime environment.
    A workflow for a new MM vendor invoice is started as it should.When we see the workflow overview it shows status u201CIn Processu201D. 
    f the workflow shows the status u201CIn Processu201D for an hour or more, a new undesired workflow (same WF-task) is started automatically for the same invoice. Nobody has triggered this new undesired workflow.
    Please let us know the what is the problem
    Thanks
    Sarin23

    Hi,
    Please see the below link and this will help you.
    http://help.sap.com/printdocu/core/print46c/en/data/pdf/BCBMTWFMMM/BCBMTWFMMM.pdf
    http://help.sap.com/saphelp_46c/helpdata/EN/c5/e4a930453d11d189430000e829fbbd/content.htm
    Anil

Maybe you are looking for