29.03.2017
Michael Baumgartner
Author: Michael Baumgartner
connect on xing

About Trans­ac­tion Fig­ures in SAP®

This article discusses the account balance display. There are several postings per vendor respectively customer in one year. The tables LFC1 and KNC1 offer a consolidated view to vendor postings or customer postings within a period. This article describes the mentioned tables. Furthermore, the corresponding transactions in SAP® are described.

Struc­ture of ta­ble LFC1

The values are stored in this table per vendor number (field LIFNR), company code (field BUKRS) and fiscal year (field GJAHR). The balance carried forward is stored in the field UMSAV at the beginning of the fiscal year; this corresponds to the open amount which was not cleared in the last fiscal year.

The following fields are listed per period, this means 16 times. XX is the placeholder for the current period. One posting period corresponds to one month, periods 13 – 16 are special periods where year-end closing postings are done:

  • LFC1_UMXXS: Sum of the debit postings in the period
  • LFC1_UMXXH: Sum of the credit postings in the period
  • LFC1_UMXXU: Turnover in the period

The field includes the sum of all sales-related postings in this posting period. It depends on the posting key if a posting is sales-related. For instance, a vendor invoice is sales-related whereas a payment is non-sales-related; this means that it is not relevant for the turnover amount if a vendor invoice has been already cleared.

The following example displays transaction figures of vendor 111 in the transaction SE16. For space reasons, the view was separated to two screenshots:

Figure 1: Structure of table LFC1: First part

Figure 2: Structure of table LFC1: Second part

In this example, the balance carried forward had a credit amount of 158,385.48 Euro at the beginning of fiscal year 2004. A negative amount represents credit postings whereas a positive amount represents a debit posting. The balance carried forward was calculated by making the balance of all debit postings and credit postings in the previous year. If all open items had been cleared at the beginning of fiscal year 2004, the balance carried forward would have been 0 Euro.

Furthermore the sum of the credit and debit postings as well as the sum of the turnover is listed for each period. You see in this example that turnovers are only displayed with a negative amount. As already mentioned, credit postings are totaled as negative amount. Since the credit sum is always corresponding to the turnover sum, the credit postings were always sales-related. In period 12, the sum of the debit postings had an amount of 213,275.06 Euro. Since this amount did not influence the turnover in period 12, the debit postings were not sales-related.

Details about these postings will be given in the next chapter.

Dis­play­ing the ven­dor trans­ac­tion fig­ures in trans­ac­tion FK10N

You get a different view to the data in the SAP® transaction FK10N. The following information is given about vendor 111, company code 1000 and fiscal year 2004:

Figure 3: Vendor Balance Display in Transaction FK10N

You see here that the balance and the cumulated balance are listed additionally. These values are, except from the balance carried forward, not stored in table LFC1 but they are calculated at run time. The origin of the values can be retraced by double-clicking to the corresponding fields. For example, you get to the following screen by double-clicking the field “Balance” in period one:

Figure 4: Vendor Line Item Display

A document with the document type RE (= vendor invoice) was posted to the credit in period 1. By double-clicking this line you get the following document display:

Figure 5: Display document

This screen shows that the invoice was posted with posting key 31 (= Invoice). In table TBSL, the setting is stored that you have a sales-related credit posting if you use posting key 31.

The most important fields of table TBSL which are relevant for the example will be shortly explained:

  • BSCHL: Posting key
  • SHKZG: Debit/Credit indicator
  • KOART: Account. The posting key can only be used with account type K (= Vendor account) in the accounts payable.
  • XUMSW: If the field is filled with an „X“, then it is a sales-related transaction.

Let’s go back to the vendor balance display of transaction FK10N:

Figure 6: Vendor Balance Display in Transaction FK10N

Click the field “Balance” which is located in the total line to display all postings of the fiscal year:

Figure 7: Vendor Line Item Display

All postings in the year 2004 are listed here. You see that the amount of 213.275,06 Euro is a payment to a vendor (document type KZ). The Balance has an amount of 158.385,48 Euro. Since we had a balance carried forward of 158.358,48 Euro in transaction FK10N (respectively table LFC1), we could conclude that all open items were cleared with this payment. To find out which documents were cleared by the payment, we can use the menu Environment -> Clearing transactions.

Figure 8: Clearing Transactions

You see in this figure that all invoices were cleared by document 1500000014 (column 2). The document numbers which were cleared are listed in column 4. Indeed, you only see postings of the year 2004; the outgoing payment has possibly also cleared older open items. Also in this screen, it is possible to change to the document display view. For instance, you can find out which posting key was used for the outgoing payment by double-clicking the document number 1500000014.

Figure 9: Display the outgoing payment document

The outgoing payment was posted with posting key 25. In TBSL is defined that this posting key is not sales-related and therefore has no influence to the turnover as we have already seen in transaction FK10N.

In contrary to LFC1, the turnover is displayed as positive amount. The reason is that the customer invoices are posted sales-related in the debit und debit postings are totaled as positive amounts.

Since the presentation of the amounts is analog to transaction FK10N and there also exists the possibility to link to the line item and to the document display, a detailed description is not given.


Comments (0)
Be the first who comments this blog entry.
Blog login

You are not logged in. Please log in to comment this blog entry.

go to Login