Overpayments

HI,
1. Would like to inquire how to deal in SAP B1 when customer request return payment due ( overpayment) , what would be the financial implications and banking implications.
2. In some localization there are tax practices " A/R creditable withholding tax' aside from Vat ( invoices) , the customer deducts a certain with expandable withholding tax and is reflected only during the payment not in the invoice how is the treatment in SAP B1.
Cheng

Hi Cheng,
please post only 1 question per thread & open another one for you WTax question.
If a customer owes you u20AC50 & he renders a payment of u20AC100, then the additional u20AC50 should be received as payment on account. The balance is then captured on the BP balance. Should this customer wish to be reimbursed, you can create a manual outgoing payment to customer. The payment wizard cannot be used for this transaction, so you'll need to instruct your bank to transfer the funds back to your customer in another way or issue a cheque.
You could also suggest to the customer to hold on to the overpayment & offset it against future invoices, though.
All the best,
Kerstin

Similar Messages

Lockbox Overpayments and tolerance

Hi,
Is there a way to post the incoming customer overpayments thru lockbox, to post to customer as " On account"? I tried to do so, but the system still applies the full payment to the invoice ( eg $1000 payment applied to $500 invoice") regardless of the tolerance set in OBA3/OBA4; Is there a way to force the lockbox to post the payment to the customer account as "On Account" instead of Applied in such a situation? (I do not want the payment difference to be posted to any GL account either; the amount shud stay in the customer account)
Any help would be rightly rewarded.
Thanks,
Deepak.

Hi,
It should work both ways. If this is an over payment a credit residual will be created with DZ-16 else if it is a under payment
it should be DZ-06.
-Ashu

Define Accounts for Overpayments/Underpayments

Dear sir,
Now, I have to define Accounts for Overpayments/Underpayments, but i dont know what is it function? can you explain me and give me some examples such and its account number.
Thank you very much.
Faithfully,
Hangvt

Hi,
Under Payment and over payments applicable for vendors/Customers
I have to pay $ 100 but I paid 98 this is a under payment for me it is a gain that why create account under incomes
I have to pay $ 100 but I paid 102 then is a overpayment $2 is a overpayment it is a expenditure crate accounts for Exp
Opposite to Customers
When you are clearing payment there residual payment and partial payment will be there
Partial payment: I have to Pay $100 but I paid 98 $2 will as a open items
Residual Payment :I have to Pay $100 but I paid 98 $2 will not show as a open item here under payment and over payment concept will come.
Configuration Steps:
T.Code: OBBE create
Rcd       DES
02     Payment diff
Save
Step2:
Create Accounts in FS00 for exp and income Accounts
Step 3:
Assign Accounts in OBXL
Dr EXP A/C
Cr INC A/C
Payment received or paid
Entry should like this
Vendor A/C $ 100
   To
      Cash/Bank 98
    To Payment Diff $2
If you need any further clarification please ask me
If it is use full Please assign points
Thanks
Shiva

Clearing Payment to a G/L account set up in Reason Code

I am having a problem posting an overpayment/underpayment to a G/L account using a reason code. What I am attempting to do is, using F-28, have the remainder of an underpayment post to a G/L account attached to the reason codes. What I need to have work is that in F-28 I do not want to have to enter any data on what the residual amount is, it should just take whatever is not paid and apply it to the G/L account tied to the reason code. I have set 3 new reason codes in OBBE to test different possibilities with the checkboxes in that transaction, and have attached each of the reason codes to accounts using OBXL. What is happening now is that when I enter a short pay amount for an invoice and I enter a reason code in the RCd field in the residual tab - I hit save and it seems to try to attach the remaining amount to an account that is currently tied to a blank reason code in our setup in OBXL. I would think that since I am placing a code in the RCD field, that it would use the account tied to that. I have also tried to use the reason code field below, but encounter the same results or, with one of my codes that has the "charge off difference via separate account" checkbox checked, it will not allow that code in that field below.
There must be a way to take the shortpay amoun,t and without entering the residual amount anywhere, use the G/L account tied to the reason code to post the remainder to. Can anybody help on what I may need to do to get this to work?
Thanks -
PS. This is not a tolerance issue as I have set the tolerances for both the customer and the user high enough to allow under/overpayments.

No... this is SAP standard.... if you are treating them as residual payment and the GL is seperate than the small diff GL we have to enter the amount there..... as system cannot understand whats the differnece when we dont put the amount there......
we can always see the field NOT ASSIGNED in the bootom.. it is just the matter of copy paste for the user.... it has to come thro user discipline.... i dont see a standard sap way of doing it,....

How to handle the SQL Error: ORA-01704: string literal too long

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta name="generator" content="HTML Tidy for Java (vers. 26 Sep 2004), see www.w3.org">
<title></title>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">
<meta content="MSHTML 6.00.2900.2963" name="GENERATOR">
</head>
<body class="BodyContent">
HI please chek the query getting error like string literal too long update PRVDR_ENRLMNT_AGREEMENT B set b.terms=q'#
<div class="widget-title">
<h5>Medical Assistance Provider Enrollment & Trading Partner Agreement - Conditions:</h5>
<a href="# class="btn-minimize pull-right"></a></div>
<div class="widget-content">
<table width="100%" border="0">
<tbody>
<tr valign="center">
<td class="Label" align="left" width="14%" colspan="2" height="32">In applying for enrollment as a provider or trading partner in the Medical Assistance Program (and programs for which the Michigan Department of Community Health (MDCH) is the fiscal intermediary), I represent and certify as follows:</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">1.</td>
<td class="LabelValue" valign="top" align="left" height="32">The applicant, and the employer (if applicable), certify that the undersigned has/have the authority to execute this Agreement.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">2.</td>
<td class="LabelValue" valign="top" align="left" height="32">Enrollment in the Medical Assistance Program does not guarantee participation in MDCH managed care programs nor does it replace or negate the contract process between a managed care entity and its providers or subcontractors.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">3.</td>
<td class="LabelValue" valign="top" align="left" height="32">All information furnished on this Medical Assistance Provider Enrollment & Trading Partner Agreement form is true and complete.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">4.</td>
<td class="LabelValue" valign="top" align="left" height="32">The providers and fiscal agents of ownership and control information agree to provide proper disclosure of provider's owners and other persons criminal related to Medicare, Medicaid or Title XX involvement. [42 CFR 455.100]</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">5.</td>
<td class="LabelValue" align="left" height="32">The applicant and the employer agree to provide proper disclosure of any criminal convictions related to Medicare (Title XVIII), Medicaid (Title XIX), and other State Health Care Programs (Title V, Title XX, and Title XXI) involvement. [42 CFR 455.106 and 42 U.S.C. ? 1320a-7]</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">6.</td>
<td class="LabelValue" align="left" height="32">I agree to read the Medicaid Provider Manual from the Michigan Department of Community Health (MDCH). I also agree to comply with 1) the terms and conditions of participation noted in the manual, and 2) MDCH's policies and procedures for the Medical Assistance Program contained in the manual, provider bulletins and other program notifications.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">7.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with the provisions of 42 CFR 455.104, 42 CFR 455.105, 42 CFR 431.107 and Act No. 280 of the Public Acts of 1939, as amended, which state the conditions and requirements under which participation in the Medical Assistance Program is allowed.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">8.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with the requirements of Section 6032 of the Deficit Reduction Act of 2005, codified at section 1902 (a)(68) of the Social Security Act which relates to the conditions and requirements of "Employee Education About False Claims Recovery."</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">9.</td>
<td class="LabelValue" align="left" height="32">I agree that, upon request and at a reasonable time and place, I will allow authorized state or federal government agents to inspect, copy, and/or take any records I maintain pertaining to the delivery of goods and services to, or on behalf of, a Medical Assistance Program beneficiary. These records also include any service contract(s) I have with any billing agent/service or service bureau, billing consultant, or other healthcare provider.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">10.</td>
<td class="LabelValue" align="left" height="32">I agree to include a clause in any contract I enter into which allows authorized state or federal government agents access to the subcontractor's accounting records and other documents needed to verify the nature and extent of costs and services furnished under the contract.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">11.</td>
<td class="LabelValue" align="left" height="32">I understand that the incentive payment requested using my National Provider Identifier (NPI) number will be made directly to the Tax ID Number (TIN) that was indicated during the registration process.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">12.</td>
<td class="LabelValue" align="left" height="32">I am not currently suspended, terminated, or excluded from the Medical Assistance Program by any state or by the U.S. Department of Health and Human Services.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">13.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with all policies and procedures of the Medical Assistance Program. I also agree that all disputes, including overpayments, may be adjudicated in administrative proceedings convened under Act No. 280 of the Public Acts of 1939, as amended, or in a court of competent jurisdiction. I further agree to reimburse the Medical Assistance Program for all overpayments, and I acknowledge that the Medicaid Audit System, which uses random sampling, is a reliable and acceptable method for determining such overpayments.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">14.</td>
<td class="LabelValue" align="left" height="32">I agree to comply with the privacy and confidentiality provisions of any applicable laws governing the use and disclosure of protected health information, including the privacy regulations adopted by the U.S. Department of Health and Human Services under the Health Insurance Portability and Accountability Act of 1996 (HIPAA), and Public Acts 104-191 (45 CFR Parts 160 and 164, Subparts A and E). I also agree to comply with the HIPAA security regulations, as applicable, for electronic protected health information by the compliance date, which is currently April 21, 2005 (45 CFR Parts 160 and 164, Subparts A and C).</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">15.</td>
<td class="LabelValue" align="left" height="32">This Agreement shall be governed by the laws of the State of Michigan and applicable federal law including, but not limited to, the Health Insurance Portability and Accountability Act of 1996 (HIPAA).</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">16.</td>
<td class="LabelValue" align="left" height="32">The provisions of this Agreement are severable. If any provision is held or declared to be illegal, invalid or unenforceable, the remainder of the Agreement will continue in full force and effect as though the illegal, invalid or unenforceable provision had not been contained in this Agreement.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">17.</td>
<td class="LabelValue" align="left" height="32">Failure or delay on the part of either party to exercise any right, power, privilege, or remedy in this Agreement will not constitute a waiver. No provision of this Agreement may be waived by either party except in writing and signed by an authorized representative of the party requesting the waiver.</td>
</tr>
<tr valign="center">
<td class="Label" align="left" width="14%" colspan="2" height="32"></td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">18.</td>
<td class="LabelValue" align="left" height="32">If the nursing facility named on the Medical Assistance Provider Enrollment & Trading Partner Agreement is sold, the seller will notify MDCH of the sale at least ninety (90) days prior to the expected sale date. Further, it is understood that the sale will not be recognized for reimbursement purposes under the Medical Assistance Program until ninety (90) days after such notification. Provisions of 42 CFR 413.135(f) will be retrospectively satisfied at that time. Any exception must be approved in writing by MDCH. The new owner/provider must receive Medicare certification for all Medicaid-only beds in the facility within one year from the date of purchase of an operating nursing facility or from the date of reopening a previously closed nursing facility.</td>
</tr>
<tr valign="center">
<td class="Label" align="middle" width="14%" colspan="2" height="32">Medical Assistance Provider - Employer/Employee Conditions</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">19.</td>
<td class="LabelValue" align="left" height="32">The applicant is employed by the business listed, now referred to as the "employer", to provide Medical Assistance Program services to eligible beneficiaries at the service address listed.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">20.</td>
<td class="LabelValue" valign="top" align="left" height="32">The employer and the applicant shall advise MDCH within thirty (30) days after any change(s) in the employment relationship.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">21.</td>
<td class="LabelValue" align="left" height="32">The employer and the applicant agree to be jointly and severally liable for any overpayments billed and paid under Act No. 280 of the Public Acts of 1939, as amended, for services provided by the applicant to eligible beneficiaries.</td>
</tr>
<tr valign="center">
<td class="Label" align="middle" width="14%" colspan="2" height="32">Trading Partner Provisions</td>
</tr>
<tr valign="center">
<td class="Label" align="left" width="14%" colspan="2" height="32">The MDCH and its Trading Partner desire to facilitate the exchange of healthcare transactions ("Transactions") by electronically transmitting and receiving data in agreed formats in substitution for conventional paper-based documents.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">1.</td>
<td class="LabelValue" align="left" height="32">Companion Documents; Standards; Other Documentation. MDCH makes available certain inbound and outbound Electronic Data Interchange (EDI) transaction sets/formats and associated version. From time to time during the term of this Agreement, MDCH may modify supported transaction sets/formats. In submitting Transactions to MDCH, the Trading Partner agrees to conform to MDCH-issued provider publications and MDCH Companion Guides as amended from time to time. The MDCH Companion Guides, incorporated by reference herein, contain specific instructions for conducting each Transaction and as such supplement Implementation Guides issued under the Standards for Electronic Transactions mandated by the Health Insurance Portability and Accountability Act of 1996 (HIPAA) as amended. The MDCH Companion Guides are not intended to be complete billing instructions and do not alter or replace applicable physician guides or other healthcare provider billing publications issued by MDCH or by other third party payers. The Trading Partner agrees to comply with the requirements set forth in the applicable MDCH Companion Guides. The Trading Partner, or its vendor, or other authorized technical representative responsible for EDI software will document Trading Partner Information, data formats and related versions, trading partner identifiers, and other information MDCH requires to receive and transmit specific Transactions supported by MDCH.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">2.</td>
<td class="LabelValue" align="left" height="32">Support. 
As to software, equipment, and services associated with each party's performance under this Agreement, the parties agree to provide support services sufficient for Transactions to be exchanged. Each party will assist the other in establishing and/or maintaining support procedures, and will complete appropriate problem determination procedures prior to contacting the other with a support related matter. The parties agree to use all commercially reasonable efforts to avoid and resolve performance and unavailability issues. Each party will perform remedial action, as requested by the other, to assist in problem resolution. Each party, at its own expense, shall provide and maintain the equipment, software, services, and testing necessary to effectively and reliably transmit and receive transactions.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">3.</td>
<td class="LabelValue" align="left" height="32">Data Retention. 
MDCH will log all Transactions for the purpose of problem investigation, resolution, and servicing. The Trading Partner is responsible for maintaining and retaining its own records of data submitted to MDCH. Trading Partners who are healthcare providers will ensure that electronic healthcare claims submitted to MDCH can be readily associated and identified with the correct patient medical and business office records, and that these records are maintained in a manner that permits review, and for the time period as may be required by MDCH or other third party payer responsible for claim payment.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">4.</td>
<td class="LabelValue" align="left" height="32">Proper Receipt and Verification for Transactions. 
Upon proper receipt of any ANSI ASC X12N Standard Transaction, the receiving party shall promptly and properly transmit a functional acknowledgement in return, unless otherwise specified. The functional and interchange acknowledgements must be accepted and reviewed, when applicable, to confirm the receipt of a Transaction. The ability to send or receive functional acknowledgements is applicable only to ANSI ASC X12N Standard Transactions. Additionally, MDCH originated outbound Transactions must be accepted and reviewed, when appropriate, to obtain MDCH's response to specific inbound Transactions. The acknowledging party does not attest to the accuracy of the data contained in the transmission; rather, it only confirms receipt of the transmission.</td>
</tr>
<tr valign="center">
<td class="Label" valign="top" nowrap align="right" width="1%" height="32">5.</td>
<td class="LabelValue" align="left" height="32">Liability. 
MDCH shall not be responsible to the Trading Partner nor anyone else for any damages caused by loss, delay, rejection, or any misadventure affecting such electronic information. In addition, MDCH shall be excused from performing any EDI servi

You cannot use string literal of more than 4000 characters in an Oracle SQL statement. I'm not going to count that string you so rudely posted but I presume it is longer than that figure. You'll need to use a variable instead.
declare
 c clob := '<your vast XML doc here>';
begin
 update PRVDR_ENRLMNT_AGREEMENT B set b.terms= c
 where ....
{code}
Cheers, APC

Well here we go again with the Usage

I've had problems in the past with the meter saying my son and I were using 90gb a month. I finally got the matter resolved with the help of Sean via here and the overpayments were refunded and things settled back down again. That was last year.
I've had odd spikes from time to time but its been fine, in fact we have (according to the meter) been using on average about 25gb a month (I'm on a 40gb usage limit). So I stopped checking religiously every day - after all, it was back to where it should be given we dont stream movies, watch iplayer, all the things we are told just simply EAT the usage.
Then last month I received an email to say we had gone over 28GB!! The remainder of the month I was checking daily, we scrapped in with less than 2GB left by 31/10.
So now I am back to checking the figures every morning and guess what... I don't believe them again.
0.66        1/11/14
1.57        2/11/14
5.24        3/11/14
I've used over 5GB in 3 days? And more to the point I used 3.67gb yesterday??I am so not a happy bunny today.

Hi adam_ant16
I am sorry you are having trouble with your broadband, would you be willing to give the Mod team a chance to fix this first? I'll be happy to get involved and make sure we get everything sorted out for you.
Could you drop me in an email please? Use the 'contact us' form in my forum profile under the 'about me' section. You can find it by clicking on my username.
Thx
Craig
BTCare Community Mod
If we have asked you to email us with your details, please make sure you are logged in to the forum, otherwise you will not be able to see our ‘Contact Us’ link within our profiles.
We are sorry but we are unable to deal with service/account queries via the private message(PM) function so please don't PM your account info, we need to deal with this via our email account :-)”
td-p/30">Ratings star on the left-hand side of the post.
If someone answers your question correctly please let other members know by clicking on ’Mark as Accepted Solution’.

Credit Limit Check - Exclude Specific Documents / Credits from Exposure

Hi,
I would like to know if it's possible to exclude specific document types (credits) from the credit exposure calculation used during credit limit checks.
The ideia is to exclude "DG" credits in customer GL that are related to Trade Deal/Agreements to avoid over-exposure.
Let me explain:
Currently, our credit management is configured to "Static" + "Open Items" for all credit groups in the CCA. Therefore, SAP calculates the credit exposure as:
          CE = OPEN ORDERS (S066) + OPEN DELIVERIES (S067) + OPEN BILLING (S067) + OPEN ITEMS (BSID)
Regarding "Open Items", I understand that SAP calculates the net value between all debits (receivables) and credits (returns, overpayments, etc...) already posted and not cleared in the Customer GL account. This rationale is correct since the credits are due to the customers and should be deducted from their exposure (i.e. "you may not pay them if you don't receive").
However, in our case, we also pay trade deals contracts (i.e. trade incentives and trade marketing investments) directly to costumers and apart from sales orders or credit memos. The flow is the following: (1) contracts are managed on a satelite system and interfaced to SAP; (2) contracts are created in the costumer GL as a credit (doc. type "DG"); (3) credits are sent to accounts payable for payment via F110.
Problem is that, contract credits volume is significant and are impacting customers credit exposure and limit check, resulting in greater exposure than allowed. That is, orders are being released while contract credits are open in the customer GL up to the max exposure, but when contracts are paid the exposure goes above the limit. For example:
Day 1:
          Costumer Credit Limit: 100
          Sales Balance: 30
          Open Itens: 50 (receivables: 70 / contracts: -20)
          Credit Exposure: 80/100
Day 2:
          Costumer Credit Limit: 100
          Sales Balance: 50
          Open Itens: 50 (receivables: 70 / contracts: -20)
          Credit Exposure: 100/100 (no additional orders are released)
Day 3:
          Costumer Credit Limit: 100
          Sales Balance: 50
          Open Itens: 70 (receivables: 70 / contracts: 0 - contracts are paid on day 3)
          Credit Exposure: 120/100 (exposure is above customer limit since contracts that were being deducted were paid)
Any ideas or thoughts? Is something wrong in the explanation above? Should contracts credits be treated through special GL?
Many thanks!

Hello Julie,
the 2nd, System behavior (how do you interact the credit limit check (yes/no question) via DI?)
Workaround:
Before you issue the Document, you may do a manual check: BP balance againt Credit Limit, and make deceision.
Regards
János

Confused by increase in Monthly Direct Debits

Hi all.
Being a newbie, I'm sure this topic must have been raised in the past.
As a new BT customer, I was paying Monthly Direct Debits of £23.50 to cover my contract for Unlimited Evening and Weekend Plan plus BT Total Broadband Option 1.
After 6 months, I have just received a bill advising me that my Direct Debits would increase to £38.00 per month (a rise of 62%!).
Having been unable to get through to an advisor on the phone, I thought I'd do a little research on the web. I found the BT Help topic "Why has my Monthly Payment Plan amount changed?", which lays out the way the bill is calculated:
Monthly Rental Charges + Last quarter usage divided by 3 + Outstanding charges divided by 6 = Monthly Payment.
In my case, this would be: £23.43 + £3.51/3 + £5.44/6 = £25.51 per month.
Therefore, I'm a little confused, not to mention rather annoyed that my Direct Debits have been increased to £38.00pm, when £26.00pm would seem more reasonable!
Any help would be appreciated.
Martin

Hi Martin,
Having the same kind of problem with BT...you are not alone!
I signed up to BT Vision back in October10 where the nice salesman told me for the package i was having (phone, broadband and tv) I would be paying £51 a month based on my previous phone usage (this figure was worked out for 3 months in advance). After a few initial teething problems all went well until after 3 months BT then tell me my payments were jumping to £88.50 a month without any explanation (my phone usage had not changed in any way during this time). Another 3 months pass, where in the meantime I had paid BT a total of £265.50 but my bill says I only owed them £151.51 so I was in credit by £113.99. BT still wanted to carry on charging me £88.50 even though that was way over what I should be paying. After cancelling the direct debit ( which was an arduous process over the phone talking with their overseas billing department) I have now received a bill for £50+ .....where has my £113.99 credit disappeared?....wits end?....tearing my hair out?....pulling teeth?...all could be used to describe the BT billing experience. The scary thing is BT would of quite happily carried on taking £88.50 out of my account every month and not done a thing.....but if i wasn't paying enough they would be quick to up my payments. Also they are sitting on my £113....along with doubtless other customers overpayments and getting a nice little bit of interest off it. Unfortunately I am tied into an 18 month contract with them and whilst I cant fault the services they provide (although my broadband usage goes near my 40 GB limit which astounds me because we only use the internet for the usual things e mails you tube etc. but thas another forum issue!) i would quite happily just get a freesat box and another internet provider because it seems BT just dont care!
rant over ...well at least till i try to ring BT later!
Pete

Payment differecne posting on vendor clearing document

Hello,
   Kindly let me know wehre is the payment difference accoutn and positng key configugured, my document is showing wrong postings to the cash discount expnse account instead of booking it to the vendor account itself
1     000001     50          1010146     BOA POLYVISION - AP     102.36-     USD
2     000002     50          4020040     COS-MAT-INV CHANGE     0.97-     USD
3     000003     40          3141020     CASH DISC-PUR FG     0.97     USD
4     000004     25          2010010     A/P TRADE RECON.     102.36     USD
the 3 line item is booking to the cash discount , which is actually the over payment of 0.97 , the 2 line is the payment terms disc wchih is correct.
please let me know where do i correct this,
thnaks very much.

Hi,
I hope you can specify an account for payment differences for over payment and underpayment. the path as follows.
SPRO-FA-AR/AP-Business Transactions-Outgoing payments-Outgoing payments global settings-Define accounts for overpayments and underpayments.
I hope it is clear, please let me know if any other details.
Regards,
Srini
Message was edited by:
        sreenivasulu pasupula

Customer & vendoar Trial balance under Business Area Wise

Dear Experts,
                      Pls tell me the T.code for Customer & vendor Trial balance under Business Area wise.
I am ready to assign full points.
Thanks & Regards
avudaiappan

Once again test u r patiency.. ur self...
SAP FI Transaction Code List 2
FG99    Flexible G/L: Report Selection
FGI0    Execute Report
FGI1    Create Report
FGI2    Change Report
FGI3    Display Report
FGI4    Create Form
FGI5    Change Form
FGI6    Display Form
FGIB    Background Processing
FGIC    Maintain Currency Translation Type
FGIK    Maintain Key Figures
FGIM    Report Monitor
FGIO    Transport Reports
FGIP    Transport Forms
FGIQ    Import Reports from Client 000
FGIR    Import Forms from Client 000
FGIT    Translation Tool - Drilldown Report.
FGIV    Maintain Global Variable
FGIX    Reorganize Drilldown Reports
FGIY    Reorganize Report Data
FGIZ    Reorganize Forms
FGM0    Special Purpose Ledger Menu
FGRP    Report Painter
FGRW    Report Writer Menu
FI01    Create Bank
FI02    Change Bank
FI03    Display Bank
FI04    Display Bank Changes
FI06    Mark Bank for Deletion
FI07    Change Current Number Range Number
FI12    Change House Banks/Bank Accounts
FI12CORE   Change House Banks/Bank Accounts
FI13    Display House Banks/Bank Accounts
FIBB    Bank chain determination
FIBC    Scenarios for Bank Chain Determin.
FIBD    Allocation client
FIBF    Maintenance transaction BTE
FIBHS   Display bank chains for house banks
FIBHU   Maintain bank chains for house banks
FIBL1   Control Origin Indicator
FIBL2   Assign Origin
FIBL3   Group of House Bank Accounts
FIBPS   Display bank chians for partners
FIBPU   Maintain bank chains for partner
FIBTS   Dis. bank chains for acct carry over
FIBTU   Main. bank chains for acctCarry over
FIHC    Create Inhouse Cash Center
FILAUF_WF_CUST Store Order: Workflow Customizing
FILE    Cross-Client File Names/Paths
FILINV_WF_CUST Store Inventory:Workflow Customizing
FINA    Branch to Financial Accounting
FINF    Info System Events
FINP    Info System Processes
FITP_RESPO      Contact Partner Responsibilities
FITP_SETTINGS   Settings for Travel Planning
FITP_SETTINGS_TREE      Tree Maintenance Current Settings
FITVFELD        Tree
FJA1    Inflation Adjustment of G/L Accounts
FJA2    Reset Transaction Data G/L Acc.Infl.
FJA3    Balance Sheet/P&L with Inflation
FJA4    Infl. Adjustment of Open Items (FC)
FJA5    Infl. Adj. of Open Receivables (LC)
FJA6    Infl. Adj. of Open Payables (LC)
FJEE    Exercise Subscription Right
FK01    Create Vendor (Accounting)
FK02    Change Vendor (Accounting)
FK02CORE   Maintain vendor
FK03    Display Vendor (Accounting)
FK04    Vendor Changes (Accounting)
FK05    Block Vendor (Accounting)
FK06    Mark Vendor for Deletion (Acctng)
FK08    Confirm Vendor Individually (Acctng)
FK09    Confirm Vendor List (Accounting)
FK10    Vendor Account Balance
FK10N   Vendor Balance Display
FK10NA Vendor Balance Display
FK15    Transfer vendor changes: receive
FK16    Transfer vendor changes: receive
FKI0    Execute Report
FKI1    Create Report
FKI2    Change Report
FKI3    Display Report
FKI4    Create Form
FKI5    Change Form
FKI6    Display Form
FKIB    Background Processing
FKIC    Maintain Currency Translation Type
FKIK    Maintain Key Figures
FKIM    Report Monitor
FKIO    Transport Reports
FKIP    Transport Forms
FKIQ    Import Reports from Client 000
FKIR    Import Forms from Client 000
FKIT    Translation Tool - Drilldown Report.
FKIV    Maintain Global Variable
FKIX    Reorganize Drilldown Reports
FKIY    Reorganize Report Data
FKIZ    Reorganize Forms
FKMN
FKMT    FI Acct Assignment Model Management
FLB1    Postprocessing Lockbox Data
FLB2    Import Lockbox File
FLBP    Post Lockbox Data
FLCV    Create/Edit Document Template WF
FM+0    Display FM Main Role Definition
FM+1    Maintain FM Main Role Definition
FM+2    Display FM Amount Groups
FM+3    Maintain FM Amount Groups
FM+4    Display FM Budget Line Groups
FM+5    Maintain FM Budget Line Groups
FM+6    Display FM Document Classes
FM+7    Maintain FM Document Classes
FM+8    Display FM Activity Categories
FM+9    Maintain FM Activity Categories
FM+A    Display Doc.Class->Doc.Cat. Assgmt
FM+B    Maintain Doc.Clase->Doc.Cat.Assgmt
FM03    Display FM Document
FM21    Change Original Budget
FM22    Display Original Budget
FM25    Change Supplement
FM26    Display Supplement
FM27    Change Return
FM28    Transfer Budget
FM29    Display Return
FM2D    Display Funds Center Hierarchy
FM2E    Change Budget Document
FM2F    Display Budget Document
FM2G    Funds Center Hierarchy
FM2H    Maintain Funds Center Hierarchy
FM2I    Create Funds Center
FM2S    Display Funds Center
FM2T    Change Releases
FM2U    Change Funds Center
FM2V    Display Releases
FM3D    Display Commitment Item Hierarchy
FM3G    Commitment Item Hierarchy
FM3H    Maintain Commitment Item Hierarchy
FM3I    Create Commitment Item
FM3N    Commitment Items for G/L Accounts
FM3S    Display Commitment Item
FM3U    Change Commitment Item
FM48    Change Financial Budget: Initial Scn
FM48_1 PS-CM: Create Planning Layout
FM48_2 PS-CM: Change Planning Layout
FM48_3 PS-CM: Display Planning Layout
FM49    Display Financial Budget: Init.Scrn
FM4G    Budget Structure Element Hierarchy
FM5I    Create Fund
FM5S    Display Fund
FM5U    Change Fund
FM5_DEL    Delete fund preselection
FM5_DISP   Display fund preselection
FM5_SEL    Preselection Fund
FM6I    Create Application of Funds
FM6S    Display Application of Funds
FM6U    Change Application of Funds
FM71    Maintain Cover Pools
FM72    Assign FM Acct Asst to Cover Pool
FM78    Charact.Groups for Cover Pools
FM79    Grouping Chars for Cover Pool
FM7A    Display Cover Eligibility Rules
FM7I    Create Attributes for FM Acct Asst
FM7P    Maintain Cover Eligibility Rules
FM7S    Display Cover Eligibility Rules
FM7U    Maintain Cover Eligibility Rules
FM9B    Copy Budget Version
FM9C    Plan Data Transfer from CO
FM9D    Lock Budget Version
FM9E    Unlock Budget Version
FM9F    Delete Budget Version
FM9G    Roll Up Supplement
FM9H    Roll up Original Budget
FM9I    Roll Up Return
FM9J    Roll Up Releases
FM9K    Change Budget Structure
FM9L    Display Budget Structure
FM9M    Delete Budget Structure
FM9N    Generate Budget Object
FM9P    Reconstruct Budget Distrbtd Values
FM9Q    Total Up Budget
FM9W    Adjust Funds Management Budget
FMA1    Matching: Totals and Balances (CBM)
FMA2    Matching: CBM Line Items and Totals
FMA3    Matching: FI Line Items (CBM)
FMA4    Matching: FI Bank Line Items (CBM)
FMAA    Matching: Line Items and Totals (FM)
FMAB    Matching: FI FM Line Items
FMAC    Leveling: FM Commitment Line Items
FMAD    Leveling: FI-FM Totals Records
FMAE    Display Change Documents
FMAF    Level Line Items and Totals Items
FMB0    CO Document Transfer
FMB1    Display Security Prices-Collect.
FMBI    Use Revenues to Increase Expend.Bdgt
FMBUD005   FIFM Budget Data Export
FMBUD006   FIFM Budget Data Import
FMBV    Activate Availability Control
FMC2    Customizing in Day-to-Day Business
FMCB    Reassignment: Document Selection
FMCC    Reassignment: FM-CO Assignment
FMCD    Reassignment: Delete Work List
FMCG    Reassignment: Overall Assignment
FMCN    Reassignment: Supplement.Acct Assgt
FMCR    Reassignment: Display Work List
FMCT    Reassignment: Transfer
FMD1    Change Carryforward Rules
FMD2    Display Carryforward Rules
FMDM    Monitor Closing Operations
FMDS    Copy Carryforward Rules
FMDT    Display Carryforward Rules
FME1    Import Forms from Client 000
FME2    Import Reports from Client 000
FME3    Transport Forms
FME4    Transport Reports
FME5    Reorganize Forms
FME6    Reorganize Drilldown Reports
FME7    Reorganize Report Data
FME8    Maintain Batch Variants
FME9    Translation Tool - Drilldown
FMEB    Structure Report Backgrnd Processing
FMEH    SAP-EIS: Hierarchy Maintenance
FMEK    FMCA: Create Drilldown Report
FMEL    FMCA: Change Drilldown Report
FMEM    FMCA: Display Drilldown Report
FMEN    FMCA: Create Form
FMEO    FMCA: Change Form
FMEP    FMCA: Display Form
FMEQ    FMCA: Run Drilldown Report
FMER    FMCA: Drilldown Tool Test Monitor
FMEURO1 Create Euro FM Area
FMEURO2 Refresh Euro Master Data
FMEURO3 Display Euro FM Areas
FMEURO4 Deactivate Euro FM Areas
FMEV    Maintain Global Variable
FMF0    Payment Selection
FMF1    Revenue Transfer
FMG1    FM: Create Commitment Item Group
FMG2    FM: Change Commitment Item Group
FMG3    FM: Display Commitment Item Group
FMG4    FM: Delete Commitment Item Group
FMG5    Generate BS Objects fr.Cmmt Item Grp
FMHC    Check Bdgt Structure Elements in HR
FMHG    Generate Bdgt Struc Elements in HR
FMHGG   Generate BS Elements f. Several Fnds
FMHH    Master Data Check
FMHIST Apportion Document in FM
FMHV    Budget Memo Texts
FMIA    Display Rules for Revs.Incr.Budget
FMIB    Increase Budget by Revenues
FMIC    Generate Additional Budget Incr.Data
FMIL    Delete Rules for Revs Incr. Budget
FMIP    Maintain Rules for Revs.Incr.Budget
FMIS    Display Rules for Revs.Incr.Budget
FMIU    Maintain Rules for Revs.Incr.Budget
FMJ1    Fiscal Year Close: Select Commitment
FMJ1_TR Settlement: Select Commitment
FMJ2    Fiscal Year Close: Carr.Fwd Commts
FMJ2_TR Settlement: Transfer Commitment
FMJ3    Reverse Commitments Carryforward
FMJA    Budget Fiscal Year Close: Prepare
FMJA_TR Budget Settlement: Prepare
FMJB    Determine Budget Year-End Closing
FMJB_TR Budget Settlement: Determine
FMJC    Budget Fiscal-Year Close: Carry Fwd
FMJC_TR Budget Settlement: Transfer
FMJD    Reverse Fiscal Year Close: Budget
FMLD    Ledger Deletion
FMLF    Classify Movement Types
FMN0    Subsequent Posting of FI Documents
FMN1    Subsequent Posting of MM Documents
FMN2    Subsequent Posting of Billing Docs
FMN3    Transfer Purchase Req. Documents
FMN4    Transfer Purchase Order Documents
FMN5    Transfer Funds Reservation Documents
FMN8    Simulation Lists Debit Position
FMN8_OLD   Simulation Lists Debit Position
FMN9    Posted Debit Position List
FMN9_OLD   Posted Debit Position List
FMNA    Display CBA Rules
FMNP    Maintain CBA Rules
FMNR    Assign SN-BUSTL to CBA
FMNS    Display CBA Rules
FMNU    Maintain CBA Rules
FMP0    Maintain Financial Budget
FMP1    Display Financial Budget
FMP2    Delete Financial Budget Version
FMR0    Reconstruct Parked Documents
FMR1    Actual/Commitment Report
FMR2    Actual/Commitment per Company Code
FMR3    Plan/Actual/Commitment Report
FMR4    Plan/Commitment Report w.Hierarchy
FMR5A   12 Period Forecast: Actual and Plan
FMR6A   Three Period Display: Plan/Actual
FMRA    Access Report Tree
FMRB    Access Report Tree
FMRE_ARCH    Archive Earmarked Funds
FMRE_EWU01   Earmarked Funds: Euro Preprocessing
FMRE_EWU02   Earmarked Funds: Euro Postprocessing
FMRE_SERLK   Close Earmarked Funds
FMRP18 Clear Subsequent Postings
FMSS    Display Status Assignment
FMSU    Change Assigned Status
FMU0    Display Funds Reservation Doc.Types
FMU1    Maintain Funds Reservation Doc.Types
FMU2    Display Funds Reservtn Fld Variants
FMU3    Maintain Funds Resvtn Field Variants
FMU4    Display Funds Reservation Fld Groups
FMU5    Maintain Funds Reservatn Fld Groups
FMU6    Display Funds Reservtn Field Selctn
FMU7    Maintain Funds Resvtn Field Selctn
FMU8    Display Template Type for Fds Resvtn
FMU9    Maintain Template Type for Fds Resvn
FMUA    Dispay Fds Res.Template Type Fields
FMUB    Maintain Fds Res.Template Type Flds
FMUC    Display Funds Res. Reference Type
FMUD    Maintain Funds Res.Reference Type
FMUE    Display Funds Res.Ref.Type Fields
FMUF    Maintaine Fds Rsvtn Ref.Type Fields
FMUG    Display Reasons for Decision
FMUH    Maintain Reasons for Decisions
FMUI    Display Groups for Workflow Fields
FMUJ    Maintain Groups for Workflow Fields
FMUK    Display Fields in Groups for WF
FMUL    Maintain Fields in Groups for WF
FMUM    Display Field Selctn ->Variant/Group
FMUN    Display Field Seln->Variant/Group
FMUV    Funds Resvtn Field Status Var.Asst
FMV1    Create Forecast of Revenue
FMV2    Change Forecast of Revenue
FMV3    Display Forecast of Revenue
FMV4    Approve Forecast of Revenue
FMV5    Change FM Acct Asst in Fcst of Rev.
FMV6    Reduce Forecast of Revenue Manually
FMVI    Create Summarization Item
FMVO    Fund Balance Carryforward
FMVS    Display Summarization Item
FMVT    Carry Forward Fund Balance
FMVU    Change Summarization Item
FMW1    Create Funds Blocking
FMW2    Change Funds Blocking
FMW3    Display Funds Blocking
FMW4    Approve Funds Blocking
FMW5    Change FM Acct Asst in Funds Blkg
FMWA    Create Funds Transfer
FMWAZ   Payment Transfer
FMWB    Change Funds Transfer
FMWC    Display Funds Transfer
FMWD    Approve Funds Transfer
FMWE    Change FM Acct Asst in Funds Trsfr
FMX1    Create Funds Reservation
FMX2    Change Funds Reservation
FMX3    Display Funds Reservation
FMX4    Approve Funds Reservation
FMX5    Change FM Acct Asst in Funds Resvn
FMX6    Funds Reservation: Manual Reduction
FMY1    Create Funds Commitment
FMY2    Change Funds Commitment
FMY3    Display Funds Precommitment
FMY4    Approve Funds Precommitment
FMY5    Change FM Acct Asst in Funds Prcmmt
FMY6    Reduce Funds Precommitment Manually
FMZ1    Create Funds Commitment
FMZ2    Change Funds Commitment
FMZ3    Display Funds Commitment
FMZ4    Approve Funds Commitment
FMZ5    Change FM Acct Asst in Funds Commt
FMZ6    Reduce Funds Commitment Manually
FMZBVT Carry Forward Balance
FMZZ    Revalue Funds Commitments
FM_DL07    Delete Worklist
FM_DLFI    Deletes FI Documnts Transferred from
FM_DLFM    Deletes all FM Data (fast)
FM_DLOI    Deletes Cmmts Transferred from FM
FM_EURO_M Parameter maintenance for euro conv.
FM_RC06    Reconcile FI Paymts-> FM Totals Itms
FM_RC07    Reconcile FI Paymts-> FM Line Items
FM_RC08    Reconcile FM Paymts -> FM Line Items
FM_RC11    Select Old Payments
FM_S123    GR/IR: Post OIs to FM Again
FM_S201    Post Payments on Account to FIFM
FM_SD07    Display Worklist
FN-1    No.range: FVVD_RANL (Loan number)
FN-4    Number range maintenance: FVVD_PNNR
FN-5    Number range maintenance: FVVD_SNBNR
FN-6    Number range maintenance: FVVD_RPNR
FN09    Create Borrower's Note Order
FN11    Change borrower's note order
FN12    Display borrower's note order
FN13    Delete borrower's note order
FN15    Create borrower's note contract
FN16    Change borrower's note contract
FN17    Display borrower's note contract
FN18    Payoff borrower's note contract
FN19    Reverse borrower's note contract
FN1A    Create other loan contract
FN1V    Create other loan contract
FN20    Create borrower's note offer
FN21    Change borrower's note offer
FN22    Display borrower's note offer
FN23    Delete borrower's note offer
FN24    Activate borrower's note offer
FN2A    Change other loan application
FN2V    Change other loan contract
FN30    Create policy interested party
FN31    Change policy interested party
FN32    Display policy interested party
FN33    Delete policy interested party
FN34    Policy interested party in applic.
FN35    Policy interested party in contract
FN37    Loan Reversal Chain
FN3A    Display other loan application
FN3V    Display other loan contract
FN40    Create other loan interested party
FN41    Change other loan interested party
FN42    Display other loan interested party
FN43    Delete other loan interested party
FN44    Other loan interest.party in applic.
FN45    Other loan interested prty in cntrct
FN4A    Delete other loan application
FN4V    Delete other loan contract
FN5A    Other loan application in contract
FN5V    Payoff other loan contract
FN61    Create collateral value
FN62    Change collateral value
FN63    Display collateral value
FN70    List 25
FN72    List 54
FN80    Enter manual debit position
FN81    Change manual debit position
FN82    Display manual debit position
FN83    Create waiver
FN84    Change waiver
FN85    Display waiver
FN86    Enter debit position depreciation
FN87    Change debit position depreciation
FN88    Display debit position depreciation
FN8A    Manual Entry: Unsched. Repayment
FN8B    Manual Entry: Other Bus. Operations
FN8C    Manual Entry: Charges
FN8D    Post Planned Records
FNA0    Policy application in contract
FNA1    Create mortgage application
FNA2    Change mortgage application
FNA3    Display mortgage application
FNA4    Complete mortgage application
FNA5    Mortgage application in contract
FNA6    Create policy application
FNA7    Change policy application
FNA8    Display policy application
FNA9    Delete policy application
FNAA    Reactivate deleted mortgage applic.
FNAB    Reactivate deleted mortg. int.party
FNAC    Reactivate deleted mortgage contract
FNAD    Reactivate deleted policy applicat.
FNAE    Reactivate deleted policy contract
FNAG    Reactivate deleted other loan applic
FNAH    Reactivate del. other loan int.party
FNAI    Reactivate deleted other loan cntrct
FNAK    Select file character
FNAL    Reactivate deleted BNL contract
FNAM    Reactivate deleted policy contract
FNASL   Loans: Account Analysis
FNB1    Transfer to a Loan
FNB2    Transfer from a Loan
FNB3    Document Reversal - Loans
FNB8    BAV Information
FNB9    BAV transfer
FNBD    Loans-Automatic bal.sheet transfer
FNBG    Guarantee charges list
FNBU    DARWIN- Loans accounting menu
FNCD    Transfer Customizing for Dunning
FNCW1   Maintain Standard Role
FNCW2   Transaction Release: Adjust Workflow
FNDD    Convert Dunning Data in Dunn.History
FNEN    Create Loan
FNENALG   Create General Loan
FNENHYP   Create Mortgage Loan
FNENPOL   Create Policy Loan
FNENSSD   Create Borrower's Note Loan
FNF1    Rollover: Create file
FNF2    Rollover: Change file
FNF3    Rollover: Display file
FNF4    Rollover: Fill file
FNF9    Rollover: Evaluations
FNFO    ISIS: Create file
FNFP    ISIS: Change file
FNFQ    ISIS: Display file
FNFR    ISIS: Fill file
FNFT    Rollover: File evaluation
FNFU    Rollover: Update file
FNG2    Total Loan Commitment
FNG3    Total Commitment
FNI0
FNI1    Create mortgage application
FNI2    Change mortgage application
FNI3    Display mortgage application
FNI4    Delete mortgage application
FNI5    Mortgage application to offer
FNI6    Mortgage application in contract
FNIA    Create interested party
FNIB    Change interested party
FNIC    Display interested party
FNID    Delete interested party
FNIE    Reactivate interested party
FNIH    Decision-making
FNIJ    Create credit standing
FNIK    Change credit standing
FNIL    Display credit standing
FNIN    Create collateral value
FNIO    Change collateral value
FNIP    Display collateral value
FNK0    Multimillion Loan Display (GBA14)
FNK1    Loans to Managers (GBA15)
FNKO    Cond.types - Cond.groups allocation
FNL1    Rollover: Create Main File
FNL2    Rollover: Change Main File
FNL3    Rollover: Displ. Main File Structure
FNL4    New business
FNL5    New business
FNL6    New business
FNM1    Automatic Posting
FNM1S   Automatic Posting - Single
FNM2    Balance sheet transfer
FNM3    Loans reversal module
FNM4    Undisclosed assignment
FNM5    Automatic debit position simulation
FNM6    Post dunning charges/int.on arrears
FNM7    Loan reversal chain
FNMA    Partner data: Settings menu
FNMD    Submenu General Loans
FNME    Loans management menu
FNMEC   Loans Management Menu
FNMH    Loans management menu
FNMI    Loans information system
FNMO    Loans Menu Policy Loans
FNMP    Rollover
FNMS    Loans Menu Borrower's Notes
FNN4    Display general file
FNN5    Edit general file
FNN6    Display general main file
FNN7    Edit general main file
FNN8    Display general main file
FNN9    Edit general overall file
FNO1    Create Object
FNO2    Change Object
FNO3    Display Object
FNO5    Create collateral
FNO6    Change collateral
FNO7    Display collateral
FNO8    Create Objects from File
FNO9    Create Collateral from File
FNP0    Edit rollover manually
FNP4    Rollover: Display file
FNP5    Rollover: Edit File
FNP6    Rollover: Display main file
FNP7    Rollover: Edit main file
FNP8    Rollover: Display overall file
FNP9    Rollover: Edit overall file
FNQ2    New Business Statistics
FNQ3    Postprocessing IP rejection
FNQ4    Customer Inc. Payment Postprocessing
FNQ5    Transact.type - Acct determinat.adj.
FNQ6    Compare Flow Type/Account Determin.
FNQ7    Generate flow type
FNQ8    Automatic Clearing for Overpayments
FNQ9    Int. adjustment run
FNQF    Swiss interest adjustment run
FNQG    Swiss special interest run
FNR0    Loans: Posting Journal
FNR6    Insur.prtfolio trends - NEW
FNR7    Totals and Balance List
FNR8    Account statement
FNR9    Planning list
FNRA    Other accruals/deferrals
FNRB    Memo record update
FNRC    Accruals/deferrals reset
FNRD    Display incoming payments
FNRE    Reverse incoming payments
FNRI    Portfolio Analysis Discount/Premium
FNRS    Reversal Accrual/Deferral
FNS1    Collateral number range
FNS4    Cust. list parameters for loan order
FNS6    Installation parameter lists
FNS7    Loan Portfolio Trend Customizing
FNSA    Foreign currency valuation
FNSB    Master data summary
FNSL    Balance reconciliation list
FNT0    Loan correspondence (Switzerland)
FNT1    Autom. deadline monitoring
FNT2    Copy text modules to client
FNUB    Treasury transfer
FNV0    Payoff policy contract
FNV1    Create mortgage contract
FNV2    Change mortgage contract
FNV3    Display mortgage contract
FNV4    Delete mortgage contract
FNV5    Payoff mortgage contract
FNV6    Create policy contract
FNV7    Change policy contract
FNV8    Display policy contract
FNV9    Delete policy contract
FNVA    Create paid off contracts
FNVCOMPRESSION Loans: Document Data Summarization
FNVD    Disburse Contract
FNVI    Loans: General Overview
FNVM    Change Contract
FNVR    Reactivate Contract
FNVS    Display Contract
FNVW    Waive Contract
FNWF    WF Loans Release: List of Work Items
FNWF_REP   Release Workflow: Synchronization
FNWO    Loans: Fast Processing
FNWS    Housing statistics
FNX1    Rollover: Create Table
FNX2    Rollover: Change Table
FNX3    Rollover: Display Table
FNX6    Rollover: Delete Table
FNX7    Rollover: Deactivate Table
FNX8    Rollover: Print Table
FNXD    TR-EDT: Documentation
FNXG    List of Bus. Partners Transferred
FNXU    List of Imported Loans
FNY1    New Business: Create Table
FNY2    New Business: Change Table
FNY3    New Business: Display Table
FNY6    New Business: Delete Table
FNY7    New Business: Deactivate Table
FNY8    New Business: Print Table
FNZ0    Rejections report
FNZ1    Postprocessing payment transactions
FNZA    Account Determination Customizing
FN_1    Table maint. transferred loans
FN_2    Table maintenance transf. partner
FN_UPD_FELDAUSW   Update Program for Field Selection
Dasharathi...

Lockbox partial application

Hi,
By default, when lockbox payments come, the partial payments are posted as residual items and the original invoice is cleared . We need to keep the AR original invoice open and post the incoming as partial payment. Where do we configure this? ANy help will be appreciated.
Thanks,
Deepak

Hi Karthik,
Were you able to solve the issue abt the tolerance? I have a problem with the lockbox; In case of overpayments thru lockbox, the system still applies the payment to the invoice regardless of the tolerance set in OBA3/OBA4; Is there a way to force the lockbox to post the payment to the customer account as "On Account" instead of Applied in such a situation? (I do not want the payment difference to be posted to any GL account either; the amount shud stay in the customer account)
Any help wud be rightly rewarded.
Thanks,
Deepak.

RFC is to be created in ECC that should fetch the data from CRM

Hi Gurus,
I am facing with a problem in knowing the fields and table to develop an RFC in ABAP.
My exact requirement is :
ABAP : the field PERNR is passed as exporting parameter to RFC and imporitng paramter is an internal table that consists of   PERNR and overpayment status field.
         ABAP                                                                             CRM
Exporting Parameter = PERNR                                  Importing Parameter= ? " Which field should i take as importing field"
Importing Parameter = LT_ITAB                                Exporting Parameter= ? " internal table consisting input field and
overpayment status field "
NOTE : In order to provide a means of progressing overpayments and to provide a statistical analysis of overpayments, RFC is required that combines the information in CRM with that in ECC6 for overpayment details.
Pls Can u Help me by providing table and field name in CRM
Thanks,
Reddy..

Hi Kalpana,
if you want to fetch ecc data to crm you have to create one rfc enabled function module in ecc use that function module in crm.
calling a smart form is different scenario go through this links you can get to know how to call..
**************** - Calling an RFC function module from one system to another
Print an Adobe Form from CRM Web UI - CRM - SCN Wiki
Call a Smartform in webUi
example:
sample code:
clear lv_client.
IF sy-mandt = '110'.
     CONCATENATE 'ECDCLNT' sy-mandt INTO lv_client.
   ELSEIF sy-mandt = '200'.
     CONCATENATE 'ECQCLNT' sy-mandt INTO lv_client.
   ELSEIF sy-mandt = '300'.
     CONCATENATE 'ECPCLNT' sy-mandt INTO lv_client.
endif.
call function 'zfunction_module' destination lv_client
exporting
is_date = lv_date
tables
ot_tab = ot_tab.
Thanks & Regards,
Srinivask

Lockbox Cash app not applying correct

Here is an example of an issue I am having.
On 4/4 check # 15093 (Doc # 140008734 and # 100014472) created one deduction for $3,076.77 and two overpayments ($167.53 and $704.34).
On 4/19 check # 15194 (Doc # 1400010705) was system applied. This application picked up the two overpayments from the prior check ( $167.53 and $ 704.34) and created a deduction in the amount of $428.81. The problem is the deduction should have been for $1,300.68. (428.81 + 167.53 + 704.34). These overpayments that the system picked up did not reference anything on the current check.
Does anyone know why this may be occuring?

Hi Richard
I am having the same problem.......Actually it picks up the previous payments (doc type ZS in our case) as payment difference....I don't know of a method to fix this.....but I explained my client that it picks up the previous open payments as payment difference & asks you to enter a text for it because they have made text field mandatory for PK16 (difference payment posting key). I would love to hear from somebody as to why that happens....
Thanks
Morgan

Accounts overdue report

Can you please help me, Im trying to locate an accounts overdue report on for Accounts Receivable that lists Unpaid Cash accounts, and overdue 7 & 14 day accounts. For 30 day and longer term accounts we use the Age Analysis Report but this doesnt help us for terms shorter than 30 days.
Hope you can help .
Regards
Pradeep

Hi.
One option for the AR dates is to change the interval of the reporting buckets on the selection screen of the AR aging report. Setting it down to a 7 day interval, rather than the 30 day default, creates a report that will break out the shorter dates. Perhaps you could create a customer property for the "under 30 day terms", and just run the AR aging report against that property.
I'm not sure what you mean by unpaid cash accounts, but we developed a query to report just unapplied customer cash. Using Query generator, it looks like:
SELECT T0.[DocNum], T0.[DocDate], T0.[DocDueDate],
T0.[NoDocSum] FROM ORCT T0
WHERE T0.[NoDocSum] >0 AND T0.[DocType] = 'C' AND T0.[Canceled] = 'N'
Catches overpayments, too. Hope this helps.

Payment scheme termination

Hi Experts,
I have created a function module which will call a standard function module ' ISU_PAYSCHEME_TERMINATE'. Can any tell me how this FM will work and where can I see its effect?
Regards,
Pravesh Gupta.

You use transaction E61PSD or method TERMINATE of BOR object PAYSCHEME to end a payment
scheme.
Select a payment scheme that you want to end and enter the end date. If you have maintained table
Payment Scheme Deactivation Reason (TE561), enter a deactivation reason as well. This has no effect
on the deactivation process and is not analyzed by the system. However, you can use it at a later point intime to analyze the deactivated payment schemes.
Once you have entered the end date, the system checks whether payment scheme requests that have
already been paid exist after the end date. If this is the case, the end date is set to the next due date plus
one day.
Depending on the sequence of the end date and the first payment date of the payment scheme, the
system proceeds as follows:
u2022 If the end date lies before the first payment date of the payment scheme, the payment scheme is
deleted from the database. If you have already created statistical requests for this payment scheme,
they are cleared.
u2022 If the end date lies after the first payment date of the payment scheme, the system executes the
following actions:
a. The payment scheme sample line that is active on the end date is prorated so that its end
date is the same as the end date of the payment scheme. A new sample line is created for
the part of the sample line that comes after the end date.
b. All payment scheme sample lines with a start date that comes after the end date are
deactivated.
c. The end date and, if necessary, the deactivation reason are entered in the payment scheme
header data.
d. All statistical requests with due dates that lie after the end date are cleared.
Payment schemes that are ended this way remain active until the end date. You can either change
the payment scheme manually or during creation of an interim or periodic bill. You can also create
statistical requests for this payment scheme. You can change the end date again as long as the
new date comes before the end date that was entered previously.
In order to ensure that a payment scheme can no longer be changed, you must deactivate it once it
has ended. You do this by creating an interim or periodic bill with a billing period that contains the
end date of the payment scheme. During creation of this bill, all payment scheme requests that
have not yet been paid are cleared. Requests with due dates that come after the most recent
interim or periodic bill and that have already been paid are settled against the current consumption
billing when the bill is created. Any overpayments can be refunded at a later point in time. The
system removes the clearing restriction u201CRu201D from all items that were transferred to the payment
scheme that have not yet been paid.
If the interim/periodic bill is reversed, the entire process is cancelled. This means that the clearing of
the paid requests against the transferred items and the current consumption billing is also reversed.
All items that had the clearing restriction u201CRu201D before the bill was created are assigned it again.
u2022 If you enter the current date as the end date, the system may react differently to the above
description. This happens when event Automatic Account Maintenance When Payment Scheme is
Ended (R531) returns parameter X_NO_ACC_MAIN (No Automatic Account Maintenance When PS
is Ended) with the value " ". When the payment scheme is ended, the system carries out integrated
automatic account maintenance. In account maintenance, all payment scheme requests that were
paid after the last interim/periodic bill are settled against all the open items that were transferred to
the payment scheme. If the payments are not enough to clear the items, the clearing restriction u201CRu201D
is removed from the remaining open items. If the amount paid is too high, the clearing restriction u201CRu201D
is removed from the payment scheme request payments that are not required for account
maintenance. You can either refund the customer directly or settle the excess payment in the next
consumption billing.
Regards,
Shiva Kumar

Overpayments

Similar Messages

Maybe you are looking for