Setup a vendor for electronic payment

Hi All,
I need to setup a vendor for electronic funds transfer (EFT). we have been paying vendors through checks so far. can anyone please provide steps to change vendor payment from checks to EFT?
Thanks in advance.

You can do that in tcode F110. Give the payment method as 'V'.
Thanks

Similar Messages

E-Text Template issues for Electronic Payments

Hi Experts,
we have a requirement to generate a Delimited Text File for Electronic Payment.
The Delimited Text File should have 3 lines of data
1)File Header
2)First Party Detail
2)Second party detail
for example
File Header -->a,b,c,d
First Party Detail -->1,2,3,3
Second Party Detail --> !,#,$,
i am able to successfully generate the delimited text file ,but the data is coming in single line
i.e. a,b,c,d,1,2,3,4,!,#,$
I have tried using <NEW RECORD> Tag but still its not working.
Could you all please provide any input
Thanks in Advance
Anand

Hello Gurus,
Just posting again... haven't received any reply...
Request you to help me out.
Thanks!

Setup needed for ACH payments to the Employee and Supplier

Hi,
I am looking for a document to know the setup steps needed for ACH payment to the Employees and the Suppliers. Can anybody give me a detailed document on that or let me know where I will find one?
Thanks,
Arun
Edited by: 834011 on Feb 4, 2011 3:55 PM

hi
I am working on 11i to R12 upgrade project.
All I have is SQL and flatfile from 11.5.10 instance..I need to implement ACH in R12...
How this flatfile is created in R12
Do I need to create a Etext RTF template in R12? My bank is wellsfargo
I need to create and implement ACH/credit/debit format in R12 environment.
whate are the steps to create a bank accepting flat file in R12
Can you please tell me how should create the flat file in r12? Should i create etext template or
XML RTF template..
appreciate your reply
kp

Check for down payment

Hi,
I have requirement like below
Check issued for vendor for down payment
Check was cashed on 01.01.2008
Check was voided on 15.05.2008
So how to reverse that and it should be normal check
How to do this
please help me
i will assign points
Thanks
Radha

Hi Radha,
What were the transactions that has been posted related to this already? I am not clear as to how an encashed cheque be voided and what you mean by "It should be a normal cheque".
FCH8 transaction would void and reverse the payment if this is what you are after.
Rgds
NW

Double vendor for invoicing

Dear SAP Expert,
I have a little question about SAP.
Here is the root case :
My client (Z) have a contract with vendor X while several service in contract was perform
by vendor Y. In Contact paper documentation, it was writen. But in SAP data, contract only
exist for vendor X. Then vendor X should pay to vendor Y.
But some regulation changed.
This situation is not permitted. So, if i want to create SO, invoice document should
created for two vendor (X and Y). I just try using partner function in vendor master data
and contract data. But SO still can not invoiced for two vendor.
Error message was occured in SAP : only one invoice presented by can be entered.
My questions are :
1. Does SAP really not allowed us to created invoiced for more than one vendor?
Please let me know the business explanation for this.
2. Is there any solution for this matter?
3. Can partner function perform this request? since i just failed to using this function.
Appreciate for your help
Thank you so much
Regards,

hi,
Invoice can be paid for the single vendor in the single trasaction MIRO..
Even if you define the partner functions, at a time you can enter the only one vendor for the payments...
You can do this just only by creating the PO for the two different vendors differently and then post the invoice for both of them differently...
> its easy to explain, because when you make the MIRO(IR doc), you can see the vendor field, where there you can enter only one vendor...Partner function is use to have different functions of your vendor as partner like invoicing party, ordering address, freight payment etc...
Hope it helps..
Regards
Priyanka.P

Electronic Payments for the vendors

Hello,
We are going to implement the electronic payments to the vendors accounts using (BizTalk)...
Is iPayment useful for that ? can we implement iPayment only for online payments not for all features ?
More details:
1- We have to realese the payment from ERP to a text file using a special format (mt103) which will be sent
Through (Microsoft BizTalk server) to the bank server to deposit the amount in the vendor account !!
2- After that we will get the confirmation from the bank in the same way .....
Example of the text file ::
+:20:001050000147+ <----------- Sequense number.
+:32A:051031SAR1391518,42+ <----------- Date/Currency/Amount.
+:50K:/##############+ <---------- Our Company Account number.
ABCXYZ Company <--------- Our Company Name
P.O.Box 000000 <--------- Our Company address 1
WSD <--------- Our Company address 1
+110022+ <--------- Our Company address 1
+:52A:ABCXYZ001+ <----------- Company Code.
+:57A:SAMBSARI+ <----------- Bank SWIFT.
+:59A:/##############+ <---------- Vendor Account Number.
Vendor XYZ <--------- Vendor Name.
Vendor XYZ Address. <--------- Vendor Address.
+:70:Online Account Transfer+ <--------- Description.
Did somebody implement this before?
We need the details and the best way to implement.
We are using now a customized form to show the payments and confirmation button, after clicking the button the text file will be generated and placed somewhere in the server,,,,,, but we need to follow the standards ....
Regards

Hi I have implemented this before a in few project. There wasn't a standard way of approach but can be as follows.
(if you want to pay single, use MT103 otherwise MT102)
General structure:
Create a unix directory and add this in utl_file_dir (or use database CREATE DIRECTORY command)
Create a unix script that sends this information to bank via an agreed method, ftp or e-mail etc
Single Payment :
On the payment, enable tools option for earlier versions for a button as you did.
Create file using utl_file in appropriate format.
Payment Batches;
Setup a bank which uses electronic format, format name and assign you program on it.
Create payment batch, it will automaticly calls your format and program that is assigned to format.
Create file for multiple payment
It depends to bank, but you send identifier to bank and you get them back on MT940 where you can reconcile automaticly on cash management.
Many other solutions available.
I hope this helps
Bilal

Setup for Down Payment made to the Vendor for Capital Assets(Otherthan AUC)

Hello,
Can any one explain how we can make down payments to vendors against capital assets and what setup is required for this.
Plz advice.

Hi,
At the time of making down payment to vendor under capital assets purchase specify the purchase order number. For this vendor reconcialtion account and down payment special g/l symbol should assign first in OBYR.
There u can choose the special gl indicators.
Hope this is helpful, if yes assign points.
Regards,
Sankar

Cross Company code posting is available for recurring payment setup?

Hi All,
I could not find the cross company code field for recurring payment setup with useing T code FBD1.
Vendor is created in paying company code 1000, however, the rent has be booked to cross company code (1001) cost center (2000).
So, while trying to do recurring payment setup, I could not see the field.
I know the alternative option that i can use the "Cost Center(1000)" is assigned to CoCd 1000 and do recurring setup without useing cross company code, later i can post the manual journal for correction (as below), however, I do not want use this option.
Dr/Cr       CoCd                         GL account            Cost Center           Amount
Dr            1001                         Rent account          2000                      XXXXX
Cr            1000                         Rent account          1000                      XXXXX
Please let me know your thoughts on this.
Thanks,
Srinivas

Hi, ok17 is not for cross company,but for CO-FI real time integration.
Ex. you maintained for "RKL     Actual activity allocation" Dr 123 Cr 567
Then while posting activity allocation in CO you'll get posting like Dr 123 Cr 567   (with corresponding CO objects)

Vendor ageing report for down payment bucketwise

Hi
I have paid many downpayment to various vendors. Now i want the ageing report for the same (i.e. bucket wise i.e. 0-30 days, 31-60 days and so on).
This i am getting for vendor invoices in TCode: S_ALR_87012085 (Vendor payment history with OI sorted list).
Please let me know if the bucketwise report is possible for the downpayment too.

Hi,
Vendor ageing for down payments as well as invoice i use to see from T.code FBL1N by creating layouts.
Choose Arreas after net due date from layout and for that column you can apply a rule that from 0 to Lessthan or equal to 30.
Like that you can create the layouts. In FBL1N you can give this layout (down) so information come in that format.
The one disadvantage is that you have to select manually the layouts and you can see only one ageing information at a time.
Regards,
Sankar

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

UserExit or Customer Exit for F110 - '*' on Vendor Line Item Payment Run

Dear all,
Background
Currently in F110, when processing for vendor payments, the item text ( or segment text) is only printed out when item text begins with an asterik ' * '. The asterik is meant to indicate that this document/item is posted from external system. You may do a F1 on the text field for detail explanation.
In the event, asterik is not present on the item text even if the text is not blank, it will not be printed at all.
Here are two OSS notes on the asteriks: 312623 and 1292333.
Include: F110SFS0_SATZ_KOMPLETTIEREN
*------- Segementtext
IF REGUP-SGTXT(1) NE '*'.
    REGUP-SGTXT = SPACE.
ENDIF.
Requirement
User is requesting for item text to be printed at all time, when the text exist, regardless of ' * '.
Question
Does anyone know of a user exit / customer exit that i could use to do modification for SGTXT ?
Would appreciate it, if you could share your suggestions / experiences - on this matter, even if it doesn't need to be resolved through user exits. Thanks in advance

BTW..you have fot following exits for F110;
Transaction Code - F110                     Parameters for Automatic Payment
Enhancement/ Business Add-in            Description
Enhancement
RFFOX074                                Frame for user exit RFFOX074 (in program RFFOCH_U)
RFFOX075                                Frame for user exit RFFOX075 (in program RFFOCH_U)
RFFOX081                                Frame for user exit RFFOX081 (in program RFFOF__T)
RFFOX082                                Frame for user exit RFFOX082 (in program RFFOF__T)
RFFOX100                                Frame for user exit RFFOX100 (in program RFFOUS_T)
RFFOX101                                Frame for user exit RFFOX101 (in program RFFOUS_T)
RFFOX102                                Frame for user exit RFFOX102 (in program RFFOUS_T)
RFFOX103                                Frame for user exit RFFOX103 (in program RFFOUS_T)
RFFOX104                                user exit
RFFOX105                                Frame for user exit RFFOX105 (in program RFFOUS_T)
RFFOX200                                Frame for user exit RFFOX200 (in program RFFONZ_T)
RFFOX210                                Frame for user exit RFFOX210 (in program RFFOAU_T)
RFFOX211                                Frame for user exit RFFOX211 (in program RFFONZ_T)
RFFOX230                                General program for user exit RFFOX230 (in program RFFOJP_L)
RFFOX240                                Enhancement for User Exit 240 (RFFOAT_P)
RFFOX250                                Enhancement for User Exit 250 (RFFODK_E)
RFFOX901                                Framework for user exit RFFOX901 (in program RFFOM100)
RFFOX902                                Framework for user exit RFFOX902 (in program RFFOM100)
FDTAX001                                Enhancement to Transaction FDTA (event after the download)
FEDI0002                                Function exits for EDI DOCS in FI - Incoming pyt adv.notes
FEDI0003                                Function exits for EDI docs in FI - Save PEXR segments
FEDI0004                                Function exits for EDI docs in FI - particular events
FEDI0006                                Function Exits for EDI-docs in FI: Save IDCR Segments
RFFOX003                                Frame for user exit RFFOX003 (in program RFFOM100)
RFFOX041                                Framework for user exit RFFOX041 (in program RFFOBE_I)
RFFOX042                                Framework for user exit RFFOX042 (in program RFFOBE_E)
RFFOX043                                Framework for user exit RFFOX043 (in program RFFOBE_D)
RFFOX061                                Frame for user exit RFFOX061 (in program RFFOCH_P)
RFFOX062                                Frame for user exit RFFOX062 (in program RFFOCH_P)
RFFOX063                                Frame for user exit RFFOX063 (in program RFFOCH_P)
RFFOX064                                Frame for user exit RFFOX064 (in program RFFOCH_P)
RFFOX065                                Frame for user exit RFFOX065 (in program RFFOCH_P)
RFFOX066                                Frame for user exit RFFOX066 (in program RFFOCH_P)
RFFOX071                                Frame for user exit RFFOX071 (in program RFFOCH_U)
RFFOX072                                Frame for user exit RFFOX072 (in program RFFOCH_U)
RFFOX073                                Frame for user exit RFFOX073 (in program RFFOCH_U)
Business Add-in
FI_BSTM_MC_EXIT                         FI Account Statement: Exit from MultiCash Conversion
FI_F110_SCHEDULE_JOB                    F110: Check before scheduling a proposal/update run

Asset is getting capitalized at the time down payment to vendor for AssetPO

Dear All,
I am working on one scenario in which asset is getting capitalized at the time of down payment to vendor.
I have created on Asset PO and i am doing downpayment to vendor against this Asset PO using F-48. Now it works fine and also this downpayment appear in that Asset PO also but i have only one problem when i have done with this downpayment, Asset is capitalized on down payment amount actually it should capitalized only when the actual goods received i.e at the time MIGO.
Kindly let me know how to solve this issue. I dont want asset capitalized at the time of down payment.
Thanks in advance.
Marmik Shah

This topic is already old but we had the same requirement. The asset should not be posted to during the down payment with F-48 but only during the good receipt.
OSS note 310368 provides the solution for this. In short:
- implement the corrections if needed
- suppress the fields asset number/subnumber in the field group of the account allocated to the special G\L indicator "A - Down payment on current assets" (transaction OBC4)
- change error message F5 378 to warning (transaction OBA5)
After this, the down payment is only posting to the vendor and e.g. a bank account and the asset is only posted to during the goods receipt. Any additional AA customizing regarding account assignment for down payments is in this case also not needed.

With holding tax base amount for 1099 vendors with discounted payment term

Hi Friends,
We have a below situation for 1099 vendors,
Some of the 1099 vendors are set-up in the system with payment term with discounts i.e. 2% if paid within 10 days
As per config, system posts with holding tax base amount at the time of posting payment.
With holding tax rate is 0%,
Based on modified net amount calculation
and
Cash discount calculation before w/tax calculation
When we have vendor with input tax, system excludes tax amount at the time of payment but for the with holding tax base calculation amount system does not exclude input tax type.
Which causes difference in 1099 misc vendors
Below is the example of how system calculates the amount.
Invoice $ 1000, payment term 2% if paid within 10 days. Input tax 7.25%
Payment going out=
$1000- $ 72.5(tax 7.25%) = $ 927.5 18.55 [2% discount] = $ 908.95 (payment amount)
With holding base calculation =
$ 1000 100 (2% discount) = $ 900
Difference between payment going out and with holding tax base = 908.98 900 = 8.98
Can some one please tell me how to get rid off this difference?
Moreover, please tell me if its normal to have 1099 vendors with discounted payment term.
Any thoughts on above situation will be helpful
Edited by: Shefford William on Jan 28, 2008 11:36 PM

Dear All
i am also having the same problem. The example is
Net invoice Value   = $ 100,000
Input Tax @ 15%   = $ 15,000
Total Invoice Value = $ 115,000
Cash Discount = 20% with in 20 days
On payment the system behavior should be
Debit Vendor invoice Value   = $ 115,000
Debit Cash Discount @ 20%    = $   20,000   ( 20% of the Net Invoice Value that is 20% of $ 100,000)
Credit W/H Tax deduction @ 3.5% = $ 3,325 ( 3.5% of 95,000 the Inv Value - Cash Discount that is $ 115,000 - $20,000)
Credit Bank Account = $ 91,675 ( Inv value - Cash Dic - W/H tax that is $ 115,000 - 20,000 - 3325 = 91,675)
However at the time of payment system is calculating tax as follows
Debit Vendor invoice Value   = $ 115,000
Debit Cash Discount @ 20%    = $   20,000   ( 20% of the Net Invoice Value that is 20% of $ 100,000)
Credit W/H Tax deduction @ 3.5% = $ 3,220 ( 3.5% of 92,000 the Inv Value - Cash Discount that is $ 115,000 - $23,000. This $ 23,000 is only calculated for W/H tax calculation that is 20% of $ 115,000 )
Credit Bank Account = $ 91,780 ( Inv value - Cash Dis - W/H tax that is $ 115,000 - 20,000 - 3220 = 91,780)
this is not the common practice when using the net base value in the system.
Can any one help me in this regard. I really have been stucked in this problem for many days
Regards
Bilal Athar

Using of cash journal for advance payment to vendor or from customer.

using of cash journal for advance payment to vendor or from customer.please give advice?

Hi,
Set up a new transaction for "Advance Payment to Vendor" in Cash Journal IMG. The menu path in IMG is Financial Acct --> Bank Accounting --> Business transction --> Cash Journal --> Create, Change, Delete Business Transactions. Transaction Code for this configuraiton activity is FBCJC2.
Enter Company Code, Business Transaction Type as "K" and Cash Journal Business Transaction as "Advance Payment to Vendor". This will work if you are paying to Vendor from Petty Cash.
Check Receipt from Customer is supported if you take it in Cash Journal and then later deposit to Bank. But check payment to Vendor should be handled trhough either automatic payment program or outgoing payment transaction.
Hope this helps,
Reagrds
CSM Reddy

Process flow with configuration for online payment of vendors

Dear friends,
I need the process flow with configuration for online payment to vendors through rtgs or neft.
Please help me in this regard. One of my client wants to implement online payment process instead of cheque payment.
thanks and regards
satya

1) Payments are initiated at the corporate SAP System using APP and converted into IDOC
Could you please tell me the steps in converting the app into idoc.
There are standard Idoc used for the same , for APP it would be PAYEXT, You need to use this Idoc type.
You define the EDI payment method and assign the program in FBZP (RFFOEDI1)which would created payment medium.
i believe in the app we will create the proposal and run the payment run, after payment proposal created what are the config steps involved in createing the payment run. for example for checque payment we will maintian variant for cheque printing.
The payment run config is done in FBZP, which would include definf check PM and assigning house bank sub gl etc.
2) PI at Client End receives the input through IDOC for the payments
Pl means? and how the client will recieve this idoc what is the set up has to be made?
PI(Process Integration) middleware which will send bank files from sap to bank and vice versa.
3) Bank PI receives the payment and converts the same RTGS/NEFT format
4) Payment Data is received at the Bank RTGS/ NEFT server for further processing
how the payment data will be recieved by bank what is the process?
This is again via PI or any thoird party tool which will send bank files to sap as Idoc, The idoc message type is FINSTA.
or this in SAP you will have to configure the following:
*House bank with partner profile
*Outbound parameters                      what is meant by outbound paramenters and how to create and where to maintian
*Inbound parameters                          what is meant by inbound paramenters and how to create and where to maintian
The outbound and Inbounmd idoc's are the one which we send(PAYEXT) and rec from bank(FINSTA). you create partner profile in WE20 and create partner profile once you create you assign outbound and inbound message types in there.
*EDI Compatible payment methods        how to know about the compaitable payment methods
Please goto house bank FI12 and you will see this in there, assign the PM used.
*APP config                                        i know the app config for cheque payment, for this scenairo any additional settings?
It would be pretty much same, you will have to define the PM used and Payment medium and remaining configuration in FBZP.
*Bank details in Vendor :
You will have to maintain the bank details of the vendor in vendor master.

Setup a vendor for electronic payment

Similar Messages

Maybe you are looking for