Lesson: debit balance check

In automatic payment transaction additional log when i try to choose both payment method selection in all cases and another option of payment method selection if not possible then the system throws me the below error.
Select only one of the two fields
Message no. F0045
please help me to solve this issue...

Hi
Payment selection in all cases already details your other check box too. What is the point in selecting both?
Regards
Sowmya

Similar Messages

Debit balance check

Hi all
I am trying to run APP. payment to one of the vendors is blocked for debit balance. How to carry out Debit Balance check ?
eg
vendor invoice 100
credit memo 50
should pay 50
currently APP is blocking the payment
thanks
pushkaraj

Hello Kulkarni,
Either in the Vendor master or in the invoice, check the Automatic payment Transactions --> Payment Block -- Change to Free for Payment.
This should solve the problem.
Regards,
Hemachandra K S
<b>Please, donot forget to mark the answer as Helpful, Very Helpful or Problem solved.</b>

F110 Debit Balance Check auto block account

Hi:
on F110 , I run debit balance check and execute the and put block.
Is this really block vendor account or not? I go to FK05 but it not put the block there.
pls advise.

Hi Mandy,
BTE 1820 is used for debit balance check in F110. But after executing it won't put any block in vendor account but it does so in run time when you execute proposal.
At the stage of proposal, it will analyze as per the logic that you have specified in the BTE and will propose you the payment list. If you run again the second time, it will analyze afresh based on entries posted in the system at that point of time..so it won't put any permanent block on any Vendor. It is for the scheme of entries posted at that point of time when you are running proposal.
Hope it helps..
Regards,
Kavita

Debit balance check while running F110

Hi,
At the time of running F110, I want the system to check the debit balance with other payment methods.
Please let me know what configuration is required to make this available.
Regards

Hi
According to me while run F110, system will check to make the payment for all the open items in one bank account. Not possible part/combination/debit balance payments.
Regards
Sridhara Rao D

Debit balance in vendor account due to outward

Dear All,
While analyzing debit balance in vendor account, we came across that in most of the cases the debit balances
arisen due to stock outward to vendor from stores and DCs. As we know that in case of Food, the PO/GRN and
returns happens at each stores and DC. In all these cases it is not possible to check the balance in vendor account by stores and DC and due to outward to vendor accounts, the debit balances arises.
Therefore how do we build the logic in System which will not allow any outward to a particular vendor account.
Is it possible through standard process or we need to build validation for the same.
Regards,
Vissu

Hi Aditya,
In F110
Choose Edit → Proposal → Debit Balance Check → Simulate.
(Confirm the program RFF110SSP. Choose Continue.)
The system then displays a list of accounts that would be blocked in an update run. Carry out the update run.
Choose Edit → Proposal → Debit Balance Check → Execute.
(Confirm the program RFF110SSP. Choose Continue.)
This will solve your problem
Regards
Jyostna

Debit balance in APP

Hi All
Can you please tell how to have check on vendor debit balance while making APP .That whether i can adjust the debit balance while making APP to vendore.
Thanks
Abul

Hi,
The same is possible when you create a proposal Once a proposal is created you have to follow the path
Edit-Proposal-Debit Balance Check-Simulate-Execute the Prog RFF110SSP you can select Payment Block for the same and Execute the items with Debit Balance get blocked.
To remove the blocks from Proposal select Edit Proposal and double click on the line item and enter payment block similarly you can remove the same as well.
Revert for further assistance,
Regards
Rahul

How 2 prevent/curb debit balances coming in GR/IR Clearing A/c for a PO?

Hi SAP Gurus,
My client in ECC 6.0 is having a specific requirement to curb the debit balances appearing in GR/IR Clearing Account with respect to a Purchase Order.
The scenario exists as follows:-
1.Goods receipt accounted against PO with movt type-101.
2.The bill passing in SAP will be done for the PO using MIRO.
3. Whenever the goods are to be send back to the vendor, the users are calling the material document posted for goods receipt in MIGO and then reversing the same.Suppose for goods rec'd with Movement Type-101 reversed with 102.The system will post a follow on FI document with reverse entry in finance.
4.This leaves a debit balance in GR/IR Clearing Account for the particular PO.
The users have to sit later to tie up the GR/IR Clearing account at a later point of time.
Is there any validation could be brought up to prevent the system from reversing the material document receipt if there is an invoice open item pending for the PO?
What is the best business practice that SAP suggests for this situation?
Regards
Deepak

Hi
Check the check box at TCode OMBZ for the movement type
Cheers
Srinivas

Payment run for debit balances

Hey Folks:
How to block the invoice payments for vendors who has debit balances more than payments.
Debit balance > invoice amount.
Can someone please throw the light on the configuration I need to perform in Vendor Master and Payment Run config.
Appreciate your time.
NS

This is not pertaining to specific vendor. I want to generalize this rule. Rule being: Any vendor with debit balance should not get a check for invoices before it clears off debit balance.
I am trying to see on what basis F110 is picking up the invoices keeping aside the standard SAP (Standard SAP will not allow to cut the check if the vendor has debit balance).
So, I am actually thinking in terms of grouping key, which is actually grouping before it gets picked up by F110.
Please throw some light into this.

Vendor debit balance - S_ALR_87012082 vs. fbl1n

I'm new to the portal, so first of all would like to say "Hello" to Everybody.
And, of course, comming here with SAP puzzle to be resolved - I hope you will be able to give me some piece of advise.
The thing is that while pulling out vendor debit balance in S_ALR_87012082 I receive different result than in fbl1n. When I check in fbl1n some vendor accounts displayed in S_ALR_87012082 the balance is 0.
This is happening for some company codes - for others, I receive expected result.
Many thanks in advance for all the suggestions where the problem may be.
Regards

Dear Shell,
The reason is S_ALR_87012093 is vendor business for a preiod ( invoices and
Dr. note / Cr. note for a period ) and FBL1N is for vendor balances on a
specific time.. It may be open item or cleared item.. Both are not same..
If you want to track back FBL1N with S_ALR_87012093 then Add / less
accordingly with FBL1N for payments / Dr. and cr. notes.
S_ALR_87012093 is reconciliation account specific, where as FBL1N is vendor
specific, take the list from both the reports and compare, they both are not
the same while selection has to differ if they have to match
Regards
Saurabh

How will vendor debit balance turn into a customer receivable?

How will vendor debit balance turn into a customer receivable?
THX
G

Broadly, you can use the standard special G/L indicator (A)for down payment given in the configuration.
You create a separate Recon account for vendor or customer as the case may be. This is for Down payment. In configuration, you link the new recon account to the Special GL.
While transacting, you call for the down payment special G/L indicator and make a posting. This posting will not be directly visible in FBL5N or FBL1N, unless you check the special G/L check box.
OBYR is used to defining the Recon account for vendor down payment.
OBXR is used to defining the Recon account for customer down payment.

System don't allowed vendor debit balances

Hi SAP Gurus
How to configure the system so that it won't allowed debit balances of Vendors.I mean to say any posting for example debit memo will be stopped if the vendor balance is going in negative.
Thanks
Anant
Edited by: Anant Agarwal on Jan 8, 2010 4:23 AM

Dear,
There is no standard function available for accounts payable as it is credit management for customer.. You will have to go for custom development because at the time of document posting system has to check balance in vendor account.
Regards,
Chintan Joshi,

Vendor's Credit/Debit Balance

Hi,
which table/transaction can I use to check whether the vendor has a credit or debit balance?
Thank you.

>
Abhii wrote:
> DMBTR is the field which will give the balance.
BSEG-DMBTR is the amount of an individual line item, not the balance.
The balance of an account is the sum of all transactions (taking DRs and CRs into account) for a particular fiscal period (usually a month or year).
Table LFC1 holds the balances by month.
Rob
Edited by: Rob Burbank on Nov 12, 2009 10:39 AM

Customer Debit balance is reclassified

Hi, all:
My issue is: customer debit balance is reclassified (tcode: FAGLF101) ? Why?
My configuration as follows:

Dear Sreebha,
You can check the settings as mentioned by Ankur.
If the credit check is required in sales order level , check in OVAK whether the credit group and D(dynamic credit check ) is assigned to your sales order type.
If the credit check is required for delivery/PGI in SPRO.IMGSALES & DISTRIBUTION> BASIC SETTINGS> CREDIT MANAGEMENT--> Credit limit check for delivery types
Check whether the sales area you are making the sales order have a credit control area in ovfl.
After this configuration checks, you can check in FD32 whether the credit exposure is 0 and also the the
risk category is assigned.
If the configurations and master data are perfect, then run RVKRED88/RVKRED77/F.28 for the customer code .
Please check and revert back.
Also please go through the forum and be sure you have not missed any credit control configuration settings.
Thanks & Regards,
Hegal K Charles

Advance Received from customers is appearing as Debit balance...

Hi All,
Please let me know what could be done for the below issue...
We have noticed an error in our books where the
Advance received from customers is appearing as a debit balance at few business
areas.
Awaiting for responses

Hi,
Please note that advance recived from customer should stand as a liability in financial. Advances GL accounts are mapped in OBXR. Will you please tell me complete entry that generated. May be it is a reversed document. Please check it if it is a reversal of an advanced wrongly booked earlier.
Regards

Screen dump when posting debit balances to an expense account

dear experts.
A screen dump is produced when saving or posting debit balances to expense accounts for only certain periods and for a certain fiscal year in this case year 2006. what might be the problem. can the problem be solved form the ABAP side or FI side?
its urgent

below is part of the screen dump:
ABAP/4 runtime error                                                            DBIF_RSQL_SQL_ERROR
                    Occurred on                                        26.02.2007                              at          08:26:04
>> Short dump has not been completely stored. It is too big.
SQL error 1438 occurred when accessing table "GLT0 ".
What happened?
When writing a data record to the database (i.e. when
updating the database), only part of the data field was
written (updated). The rest was truncated.
What can you do?
If the error occurred in Open SQL, there is probably an inconsistency
between the NAMETAB and the ABAP/4 Dictionary.
Compare the length specifications of the fields in the NAMETAB with
those in the ABAP/4 Dictionary and contact someone who is able to
perform a consistency check and eliminate the problem.
In most cases, this person will be your SAP consultant.
Please make a note of the actions and input which caused the error.
To resolve the problem, contact your
SAP system administrator.
Select the "Print" function to obtain a hardcopy of the
current termination message.
Error analysis
The problem has arisen because, within the database interface,
one of the data buffers made available for the INSERT (UPDATE)
is longer than the maximum defined in the database.
On the other hand, it may be that the length in the NAMETAB
does not match the maximum length defined in the database.
(In this case, the length in the NAMETAB is longer.)
How to correct the error
Database error text........: "ORA-01438: value larger than specified precision
allows for this column?"
Internal call code.........: "[RSQL/UPDT/GLT0 ]"
Please check the entries in the system log (Transaction SM21).
You may able to find an interim solution to the problem in the
SAP note system. If you have access to the SAP note system yourself,
please use the following search criteria:
"DBIF_RSQL_SQL_ERROR"
"SAPLGIVA" or "LGIVAF10"
"UPDATE_TT_GLT0"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "31H"
Application server....... "umprod"
Network address.......... "10.1.1.9"
Operating system......... "Windows NT"
Release.................. "0"
Hardware type............ "PENTIUM"
Database server.......... "UMPROD"
Database type............ "ORACLE"
Database name............ "UMP"
Database owner........... "SAPR3"
Character set............ "English_United State"
SAP kernel............... "31I"
Created on............... "Jun 21 1999 04:44:28"
Created in............... "NT 4.0 1381 Service Pack 3 x86"
Database version......... "ora OCI_73211"
Patch level.............. "315"
Patch text............... " "
Supported environment....
Database................. "ORACLE 7.2..., ORACLE 7.3..., ORACLE
8.0...*"
SAP database version..... "31I"
Operating system......... "Windows NT 51 3, Windows NT 0 4"
User, transaction...
Client.............. 600
User................ "HAVIREO"
Language key........ "E"
Transaction......... "FB01"
Program............. "SAPLGIVA"
Screen.............. "RSM130003000"
Screen line......... 2
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLGIVA" in
"UPDATE_TT_GLT0".
The main program was "RSM13000".
The termination occurred in line 542
of the source code of program "LGIVAF10" (when calling the editor 5420).
The program "SAPLGIVA" was started in the update system.
Source code extract
005120                               HSL10 = HSL10 + TAB_GLT0-HSL10
005130                               KSL10 = KSL10 + TAB_GLT0-KSL10
005140                               TSL11 = TSL11 + TAB_GLT0-TSL11
005150                               HSL11 = HSL11 + TAB_GLT0-HSL11
005160                               KSL11 = KSL11 + TAB_GLT0-KSL11
005170                               TSL12 = TSL12 + TAB_GLT0-TSL12
005180                               HSL12 = HSL12 + TAB_GLT0-HSL12
005190                               KSL12 = KSL12 + TAB_GLT0-KSL12
005200                               TSL13 = TSL13 + TAB_GLT0-TSL13
005210                               HSL13 = HSL13 + TAB_GLT0-HSL13
005220                               KSL13 = KSL13 + TAB_GLT0-KSL13
005230                               TSL14 = TSL14 + TAB_GLT0-TSL14
005240                               HSL14 = HSL14 + TAB_GLT0-HSL14
005250                               KSL14 = KSL14 + TAB_GLT0-KSL14
005260                               TSL15 = TSL15 + TAB_GLT0-TSL15
005270                               HSL15 = HSL15 + TAB_GLT0-HSL15
005280                               KSL15 = KSL15 + TAB_GLT0-KSL15
005290                               TSL16 = TSL16 + TAB_GLT0-TSL16
005300                               HSL16 = HSL16 + TAB_GLT0-HSL16
005310                               KSL16 = KSL16 + TAB_GLT0-KSL16
005320                           WHERE
005330                           RLDNR                   = TAB_GLT0-RLDNR                  AND
005340                           RRCTY                   = TAB_GLT0-RRCTY                  AND
005350                           RVERS                   = TAB_GLT0-RVERS                  AND
005360                           BUKRS                   = TAB_GLT0-BUKRS                  AND
005370                           RYEAR                   = TAB_GLT0-RYEAR                  AND
005380                           RACCT                   = TAB_GLT0-RACCT                  AND
005390                           RBUSA                   = TAB_GLT0-RBUSA                  AND
005400                           RTCUR                   = TAB_GLT0-RTCUR                  AND
005410                           DRCRK                   = TAB_GLT0-DRCRK                  AND
          >                 RPMAX                   = TAB_GLT0-RPMAX                  .
005430                         ENDFORM.
005440                         *eject
005450                         *                                                                                                                                            *
005460                         *
005470                         *                                                                                                                                            *
005480                         *         FORM UPDATE_TT USING UTP_TAB.
005490                         *         Diese Form fuehrt die Tabellenupdates durch
005500                         *         Dabei wird die optimierte Form von UPDATE
005510                         *         verwendet
005520                         *                                                                                                                                            *
005530
005540                         FORM UPDATE_TT_GLT3      .
005550                           DATA: W_0 LIKE GLU1-TSL VALUE 0.
005560                           UPDATE GLT3
005570                           SET TSLVT = TSLVT + TAB_GLT3-TSLVT
005580                               HSLVT = HSLVT + TAB_GLT3-HSLVT
005590                               KSLVT = KSLVT + TAB_GLT3-KSLVT
005600                               TSL01 = TSL01 + TAB_GLT3-TSL01
005610                               HSL01 = HSL01 + TAB_GLT3-HSL01

Lesson: debit balance check

Similar Messages

Maybe you are looking for