Tables for Payment Proposal and Payment Run by user

HI,
I am looking for some help on a task that I have been given to complete
I am looking for tables on a payment proposal and a payment run
I would like to be able to see who run the proposal and who run the payment run for a year to date
Thanks and Kind Regards
Angela Prinsloo

Hi,
Payment proposal and payment run
Table REGUV
XVORE = 'X'
XECHT = ' '
Payment run user details
REGUA
You can explore REGU* tables for more automatic payment run related details.
Best Regards,
Madhu

Similar Messages

Payment proposal and payment run

Hi
Could any one send me some informaiton abt payment proposal and payment run.
I mean purpose of payment proposal and payment runand . and their t.codes alsol
Regards
John

Hi,
Both of them are executed from transaction F110.
Proposal is the first step, in which depending on the parameters you selected, some documents are preselected for payment. Proposals can be deleted and the systems would be as it was. No postings done.
Payment run is the 2nd step and always comes after a proposal. In this step the actual postings are done and documents are created. Also DME (files for banks), checks and/or scripts (letters) can be printed / generated.
For deeper and better info I suggest you visit this Wiki:
<a href="http://www.hostlogic.hu/caghelp/Transactions/Finance/content/f110%20-%20run%20payment%20program/cc/html/index.htm">F110 Wiki</a>
Regards,
Alfonso

Approval Process between Payment proposal and Payment run(F110)

Hi All,
We have a requirement on the approval process in Automatic Payment Run.
Requirement is a person runs the payment proposal and the details are to be send to the Approver. Once the approver reviews the details in the proposal run, he can either approve or reject the payment run.Once approved then only payment need to be executed.
Is it possible to build a approval workflow between proposal or payment run?
if manual approval is happening outside SAP, is it possible to provide a stop payment run until it is approved?-or it only through security?
Is there any possiblity to attach documents to the each and every proposal run?
Understand this is a common requirement everyone is having...Looking out for solutions
Can you please provide SAP standard or a customised solution?
Regards,
Suresh

Hi Suresh,
Welcome to SDN Forums!
According to me there is no standard workflow system for payment proposals approvals.
Have you tried with the authorisation concept?
In F110, go to menu item -> Environment -> Authorisations
Assign the activities to users according to your requirement.
Please check with your ABAP & BASIS collegues.
REgards,
Srinu

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

F110 problem (when running the proposal and payment run) in ECC6.0

Hi,
when i am am running F110 (T.code for proposal and payment run) in ECC6.0.
after completion of payment system seen two jobs are created in logs. give me the suggestions . is their any diff between 4.6c F110 and ECC6.0 F110.
Regards,
babu

no only passing 1 document number after proposal number and debit note number generated .
in job log entries: duedate document and posting document generated 2 .but in 4.6c its generates 1 duedate date and 1 posting date document.

F110S Proposal and Payment run - Job Scheduling

Hi,
I found few threads explaining how to use F110S function but didn't find a solution for the scenario that I was looking for.
Scenario:
How can we use F110S to create a proposal and run the payment after few hours for the same payment proposal.?
Ex: Create payment proposal using background job at 7 AM. ( by activating the proposal run box in F110S it creates the proposal list)
Users would go though the exception list and edit the proposal if required.
Run the payment using background job at 10 AM for the proposal created at 7 AM.
Is this possible using F110S?
Thanks...

Hi,
The program to schedule the Proposal and Payment is the same. When you run the proposal, you should tick the Proposal tick in the program and when you have to schedule the Payment tick, you need to remove the proposal tick.. otherwise the process remains same.
I am not in front of the system now.. so cannot give you the exact program name..
Regards,
SAPFICO

Re: No G/L accounts are defined for bank ICICI and payment method C

< MODERATOR: Message locked. Please read [this|Before you post: Rules of Engagement; before posting next time. use an appropriate subject... something other than what was copied from an email would be appreciated. >
Hi Friends,
When i am doing T.Code F-58 i am getting an error of
(No G/L accounts are defined for bank ICICI and payment method C) so could anybody please help me how to solve this problem awaiting for your reply friends.
Points will be assigned.
Thanks in advance.
KUMAR.

Hi Kumar,
You will have to configure the House Bank with T Code FI12 and further mention the payment method in FBZP. You will have to select one of the follwing as payment method, check/transfer/postal giro transfer/bill of exchange. Though check (C) is widely used.
Assign points, if useful.
Regards,
Saurabh Agarwal

No G/L accounts are defined for bank 24001 and payment method C

Hi SAP Gurus,
Iam getting error while cheque payment to vendor - No G/L accounts are defined for bank 24001 and payment method C, Message No.: F5459.
I have created the Bank A/c,Detail is House Bank No.24001, Account ID : 24001, Bank A/c No. 2111111111, GL A/c No. 40000000.
Kindly help for the above matter.
Regards,
Amitabh

Hi Amitabh,
As per the error you have not yet assigned your GL account for the particular Bank Account.
For example while giving payment by Cheque. Method is Cheque, GL account is Outgoing account right.
The entry would be
Cheque Issued Out Ac Dr.
To Main Bank Ac Cr.
You hv to assign both GL Account.
Please check Assign accounts to account symbols area.
Warm Regards,
Sivakumar Sathiyamoorthy

Printing Payment Advice and Payment Media for Manual Payments

Hello Gurus,
In my company, we process very few invoices in a day and we have opted for manual payment of invoices. When this payment is done, I will like to print both the payment media and payment advice for the manual payments that have been done for vendor invoices. Does anybody have an idea how I can go about this? Thanks in advance for your help.
Cheers

To print payment advices and payment media you can use transaction F-58. When you enter your bank details and printer details make sure you enter printer name for both the payment media and payment advices. Then it will print both.
Hope this helps.
Shail

Payment Advice and Payment Files

AT F110, i know it clears the open item line item and creates checks, but what is the Payment Advice and Payment Files that are created, where they will be created. How to see them. If it is to send to Bank how to send it. Please can any one eloborate.
Satish

Hi Satish
Payment advice is something you send as a notice to the vendor whoever is getting paid. Generally when creating the variant for the payment program you would have clicked the 'payment advice' check box for it to be printed along with the check. If you haven't clicked that, then please click that & you will see two pages, one with check & the other with the advice.
The second part of your question about files & how they need to be sent to the bank....if you are going to be sending for example ACH payment file to the bank, we need to use program RFFOUS_T to generate a file. The variant for this program has to be configured with output medium as '0' & file identifier as 'A'. But before that you need to make sure in FBZP -> House banks -> DME config there is something entered in 'Company number' field. Once that is done, please check all the standard settings like the payment method in country, in company code, etc. Also make sure there are bank details of the vendor in the vendor master. Then if you do the payment proposal & check the box that says 'create payment medium' & then if you goto 'Environment -> DME Admin -> PAyment medium' in F110 screen, it will take you to a user screen & then if you hit execute it will pull up the file that you generated. Then when you do the payment run, click on that 'create payment medium' box & it would have generated the actual file in DME admin screen. This file could be sent to the bank from that DME admin screen. Play with it for a little bit & I am sure you will understand that.
Award points please, if you find this useful.
Thanks

Tables for Collection, dispute and credit management

Hi SAP Gurus,
I would appreciate if any one could provide the list of tables for collection, dispute and credit management. Thanks!
Regards,
aj

I think you mean the tables for FSCM.
The easiest way to find it is to do SE16 FDM*
FDM_AR_WRITEOFFS               FSCM-DM: Automatic Write-Offs Not Executed
FDM_BUFFER                     Cluster for Decoupling in 1-System Scenari
FDM_BW_INV_DELTA               Delta Queue for BI Invoice Extractor
FDM_COLL_CCOLOAD               Company Codes for which Initial Load Perfo
FDM_COLL_CFIELD                FSCM-COL: Relevant Fields for Document Cha
FDM_COLL_COMPCOD               FSCM-COL: Active Company Codes of Collecti
FDM_COLL_DUNNLEV               Harmonized Dunning Levels
FDM_COLL_LASTPAY               Last Payments of Business Partner
FDM_COLL_LTRIG                 Missing Entries of Table FDM_COLL_STRIG
FDM_COLL_SFIELD                FSCM-COL: Relevant Fields for Document Cha
FDM_COLL_STRIG                 FSCM-COL: Control of Trigger Update in TRO
FDM_COLL_TROBJ                 FSCM-COL: Trigger Table for Collections Ma
FDM_CONTACT_BUF                Personalization of Contact Person Data
FDM_DCOBJ                      FSCM-DM Integration: Disputed Objects
FDM_DCPROC                     FSCM-DM Integration: Dispute Case Processe
FDM_P2P_ATTR                   Attributes of Promise to Pay; Required for
FDM_PERSONALIZE                Personalization of Collections Management
FDM1                           Cash Management & Forecast: Line Items of
FDM2                           Cash management line items from MM purchas
FDMV                           Cash Planning Line Items of Earmarked Fund
Hope this helps, award points if useful.

Settings for Item Proposal and Product Proposal

Hi Gurus,
How to do the configuration settings for Item Proposal and Product Proposal.
I also want to know what is the difference between Item Proposal and product Proposal.
Give me your Solution.

Item proposal is the list of regularly/frequently ordered items of a particular customer. this will be useful when u are entering the sales order. it will be used to speed up the order entry process.
For that Goto VA51, enter item proposal type as MS and sales area details.
enter the customer name and the list of products and save. Assign the item proposal No in the customer master sales area data, sales tab.
create the sales order and enter the customer no and press the propose items button in the sales order.
the system will propose one box and it will display all the materials. then u can continue further.
Product proposal:
To configure product proposal, Go to IMG,SD, Basic functions, Dynamic product proposal, Maintain all the settings
**A product proposal is a list of products for a specific customer that is automatically proposed during sales document processing. You can decide for yourself which materials should be displayed as product proposals in the sales document. You can also determine the sequence in which the materials appear in the product proposal.
During sales document processing, the system displays a product proposal in the item overview according to the customer and the business transaction. It displays the material number, material description, and historical order quantites in the sales unit last used. To use a material again, you just have to copy it. The system does not run the standard checks (pricing, availability, incompletion, material determination, free goods determination and so on) until you have entered the order quantities.
The product proposal is both an entry help and an aid to sales support and promotions. It is particularly useful in Telesales, where the employee automatically receives a display of all the materials that are of interest to a particular customer. This helps them to provide appropriate advice to the customer quickly and easily. The sales document history enables you to analyse the purchasing behaviour of a customer and recognize early on if it changes, for instance, when the customer suddenly stops ordering a product.
The product proposal differs to cross-selling in that it is dependent on the customer and sales area, and is displayed in the sales document as soon as you have entered a customer. Cross-selling, on the other hand, is triggered by a material. In other words, the system proposes cross-selling materials according to the material or a characteristic of the material you have entered.
You can determine the product proposal from different data sources:
Order history
Listed materials
Excluded materials
Item proposal
Customer-material info records
Customer-specific data sources
You can combine materials from these data sources to create a product proposal. The system then accesses the data sources either online or in the background.
To define a product proposal for sales document processing, you must carry out the following activities in Customizing:
Define customer procedure for product proposal
Define document procedure for product proposal
Assign document procedure for product proposal to order types
Maintain table of origin for product proposal
Define product proposal procedure and determine access sequences
Maintain procedure determination (in background) for product proposal
Maintain procedure determination (online) for product proposal
The product proposal procedure determines how the system displays the product proposal in the sales document. For instance, if the system has accessed the order history, it determines how many columns should be displayed in the sales document, in which period intervals thehistoric order quantities should be displayed (for instance, day, week, or month), and most importantly, the sequence in which the system should access the data sources (for example, order history, listing, exclusion).
The product proposal procedure depends on the:
Customer determination procedure
The customer procedure determines which product proposal procedure the system automatically uses when you create a sales document for a particular customer.
It is specified in the customer master record per sales area.
Document determination procedure
The document procedure determines which product proposal procedure the system automatically uses for a certain document type. The document procedure is stored as a key in the header for the sales document type.
If you use online processing, the product proposal procedure is determined according to the customer and document determination procedures.
If you use background processing, the product proposal procedure is determined according to the sales area in the customer master and the customer determination procedure. It does not use the document determination procedure because the document type is not recognized in background processing.
Difference:
Item proposal is the list of products the customer used to buy frequently.
Product proposal is also the list of products but it will explode in the sales order, once u enter the sold to party field. But this will be based on the following criterias.
Order history
Listed materials
Excluded materials
Item proposal
Customer-material info records
Customer-specific data sources
Hope this clarifies.
Reward points if useful

Combine Down Payment Request and Payment of Open Item

I am paying $ 1000 to a vendor to cover $ 300 down payment request and $ 700 for an open invoice. Is it possible to make one payment transaction to cover “down payment request” and “payment of open item”? I want only one amount to appear in the bank ledger account. Thank you, Pravin

Hi
In payment program configuration under the payment method configuration for your company codes, make sure that under grouping of items, the two radio buttons are not selected. This should combine the two items into one payment document. Screen shot attached
regards
Sanil Bhandari

Wait for 3 minutes and then run another method

I'm calling a JMS service lets say runProgress() the method adds a new row into a database then waits for 3 minutes and then runs another method that removes the row from the table.
I was thinking about this, and thought that I could create a new Thread, let it wait for 3 minutes and the run the other method.
The thing is what happens if there are 10.000 users running this at the same time, then there would be 10.000 Threads, wouldn't it be a hevy load on the server.
Is there any other way?? Suggestions?

What do you think about if there are massive, like
10.000+, queue's in memory, this would be slow down
for the server, right? or isn't it a trouble?you don't need 10.000 queues - just one single queue. you may have a lot of objects in the queue but this is at most a memory problem - depends on the size of the information you need.
maybe i was not clear enough: you have a single queue where the tasks are put into. then there are other threads (at least 1) that read from the queue and perform actions.
One option, that I don't know how to do yet but
thinking about it, is to let the database have some
kind of a procedure that would run after 3 minutes,
but I guess that I were only moving the memory trouble
from the app-server to the database. (hope you
understand me)yes, i think so.
So it would be just as good to do this in the
app-server as in the database, what do you think?a good idea. typically with all these optimization issues you just have to try out. otherwise you won't know the result.
robert

What is the field and Table for "Batch Class" and "Class Type" in QM.

Hi All,
What is the field and Table for "Batch Class" and "Class Type" in QM.
Thanks,

Hi,
For batch class the class type value is '023' . This you can find from KLAH table and the fileld for class type is KLART..
And also all the data related to batch class are found in tables INOB, KLAH,KKSK and for the characeteristics of batch materials you can refer AUSP table.
In INOB table, for batch class, you need to give 023 in KLART field and value MCH1 in OBTAB filed.
Please check this and let me know if this you need any more details?

Tables for Payment Proposal and Payment Run by user

Similar Messages

Maybe you are looking for