Vendor Invoice Workflow

Dear Friends,
Hope you are doing well.
I am getting a below problem in my vendor invoice worflow. It get triggered at the time of parking the vendor invoice. but it suddenly goes in to error mode. when i check, i get the entry in tcode SWU2 (Transactional RFC) stating that
Enter rate / INR rate type M for 23.01.2008 in the system settings.
I have checked the authorization. all are ok but error are still coming. I am confused from where should i start looking into this.
Please give me ur valuable suggestions.
Thanks & Regards,
Arti

It is a currency conversion that fails, so there's something missing either in the configuration of currency conversion rules or in the data (currency values/rates). Authorization is not an issue. I suppose this would be a case for the FI people.

Similar Messages

Vendor invoice workflow approval & Payment Run

Hi All,
I have this scenario happened (only happened in 3 documents):
1. Based on workflow log, user managed to release and approve vendor invoice (in FY2009)
2. Payment Run is executed against this invoice and posted (in FY2010)
3. The end result is:
    a. BKPF status is "V" (Parked Document)
    b. VBKPF - no record for the invoice
    c. Can't displayed the invoice under "Parked Document"
Any possible explanation how this can happen?
Thanks a lot for your attention and time,
Tony

Hi experts,
any suggestions?
Regards,
Elena

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

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

Vendor invoice approval workflow.

Hi,
I have been assigned to work on vendor invoice approval workflow. I need info as to which business object can be used...
Cheers,
Sukumar.

You make the choice - BKPF or FIPP
Imthiaz

Standard workflow for FB60 vendor invoice

Dear experts,
I am looking for a standard workflow for transaction FB60. Is that WS00400012(BO: BSEG)?
I just wonder if I could check the link between a transaction and business object.
In SWO1, BSEG is noted as "Accounting document line item". So i am not sure if it is for Vendor Invoice.

There are several standard workflows for vendor invoices. WS00400012 is for release of payment. If that is what you are looking for, it is fine. But go to the customizing to find more information about both the release for payment solution and the release for posting solution from SAP. Can't recall the customizing path now, but it is in Financial Accounting, I think the path is Accunts Receivable and Payable, then Business Transactions, and there you will at least find the Release for Payment part of it. The customizing screens are partly common, but the help available for the customizing nodes is most likely specific for each solution. I have never set up release for posting, so I don't know it.

Workflow for archiving vendor invoice

Dear Gurus
my client asked me to develop workflow for massive archiving vendor invoice.
Is tbere a standard workflow?
Which are the steps to set the Archive link?
Best regards
Vanessa

Hi,
It might be that this has nothing to do with workflow? You are supposed to archive the vendor invoices with transaction SARA, or? And for this you need ArchiveLink?
If this is the case, please look help for example at the new Archiving forum:
Information Lifecycle Management
Regards,
Karri

Non PO Invoice Workflow - Error while Posting Document

Hi Experts
Hope I am posting this in the right forum as I am new to SDN!
We have customized a multi-level non PO invoice workflow which triggers at the time of clicking 'Save as Completed' in tcode FV60.
It has been configured to automatically post the document once it is approved at all the required levels. However, the document cannot be posted even after it receives all levels of approval. The status shows as 'Complete' but the error message shown is 'No Amount Authorization for Customer/Vendor in Company Code' in the workflow screen (MSGID F5, MSGNO 155).
Now as I understand, this is the error for maintenance of user ID in tolerance groups. However, all user IDs have already been maintained and no matter who parks the document, the same error appears in the workflow screen.
We have no idea whether this is happening due to some missing config from FI side or WF side.
Regards

Hi
Go to Tcode: OBA3 Assign tolerance group under your company code and give all limits for each group. If you done this one your properly your problem should solve.

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

Memoryze barcode for vendor invoices

Hi all
We want to save, after have posted a vendor invoice with barcode, the link between the document and the barcode. Now the link is present in the BDS_BAR_IN table but when the corresponding record in BDS_BAR_EX appear, both the two are deleted.
I saw that for the 46c SAP suggest (note 564547) to use a workflow raised by the event barcode.assigned. For the ecc6.00 exist a different modality (without development work) or I must use the same modality suggested for the 46c?
Thanks
Davide

HI David,
I was able to assign barcode to BDS_BAR_IN table and also be able to assign barcode externally with the function module
BAPI_BARCODE_SENDLIST, It created the barcode entry in BDS_BAR_EX table.
Though the same barcode exist in both BDS_BAR_IN & BDS_BAR_EX tables, they are not getting matched and disappearing for some reason in OAM1.
Any idea what might be cauing this issue?
Thanks
Aj

Customer & vendor invoices

Hi gurus & experts,Here i got an issue regarding customer & vendor invoices.
I tried to post an entry using t-code f-22(customer invoice)/f-43vendor invoice, able to post but unable to view the document no. and then system shows the following error message. Express Document' updates terminated' by author.
Here i found that when we post the document directly its shows error message and the document is going directly to business workplace (t-code SBWP). Just see in that inbox, And see in t-code(ST22) ,userid : jyothin, SYNTAX_ERROR there you find some run time error problem.
Regards,
I will Assign Max points.

Hi,
Check whether any workflow is attached.
Thanks,
Sridevi
<i>* Pls. assign points if useful</i>

Error Message M8 534 when posting vendor invoice

Hello Guru's!
My client has a BSP application that the purchasers are using to approve and post vendor invoices.
When the user is approving the invoice, we have a WF setup to automatically post the invoice to FI.
We're using standard SAP functionality. BUS2081, method PreliminaryPost.
First, this method is reading the preliminary invoice using method MRM_INVOIC_READ, then it goes on to try to post the invoice, using MRM_PARKED_INVOICE_POST.
In about 50% of the approvals, the invoice is posted to FI but the other 50% kicks out with a message M8 534 - Balance not zero: & debits: & credits: &.
Then the system is setup to generate a new WI in order to post the invoice manually.
The issue, is that before the method PreliminaryPost is carried out, there is a check online to make sure the document ís OK.
So, i know that there is no balance on the document, and it should be ok to post.
This issue arised recently after my client went through an upgrade from ECC 5 to ECC 6.
I have seearched OSS for notes, adn related notes are implemented.
Any thoughts on this
Thank you for sharing your wisdom.
Lars

The functions that i'm using are SAP developed functions and used by the bapi 'BAPI_INCOMING_INVOICE'
However, i found out from SAP that these functions are only supported from SAP using 3 standard workflows.
WS20000397 Release of invoice blocked due to price
WS20001003 Parking: Complete invoice
WS20001004 Parking: Release complete invoice documents
They hinted that i should try the function MRM_DBTAB_REFRESH.
Havent had time to try this yet, but will do, soon.
Regards
/lars

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.

Approval for Vendor Invoice

My client required Approval for Vendor Invoice Payment from senior person. How can i configured this scenario in sap AP?
Pls Reply

Hi,
Please check this link:
[Workflow for Payment Release|http://www.google.co.in/url?sa=t&rct=j&q=workflow%20for%20payment%20release%20sap&source=web&cd=1&ved=0CBsQFjAA&url=http%3A%2F%2Fhelp.sap.com%2Fprintdocu%2Fcore%2FPrint46c%2Fen%2Fdata%2Fpdf%2FFIBP%2FFI-AP-AP-RP.pdf&ei=QdjETqe6Ds-xhAfv6NSEDg&usg=AFQjCNGlK2kUdPUyvPIgG32Ulni3ks9tuA&cad=rja]
Regards,
Jigar

Business objects for parking of vendor invoices (Both FV60 and MIR7) ?

Workflow guus,
I have a situtation where I have to send certain email when a vendor invoice document is parked using
1) FI vendor invoices using transaction FV60. Can someone tell which business object has event for parking of FI vendor invoice ?
2) Logistics vendor invoices using transaction MIR7. Can someone tell which business object has event for parking of logistics vendor invoice ?
Please help.
Regards,
Rajesh.

HI Experts,
I have to do LSMW for Transaction FV60 . For that i am going to use BAPI .
Please let me know the Business Object and Method for Parking Document
Thanks in advance

Vendor Invoice Workflow

Similar Messages

Maybe you are looking for