Table OVPM (SAP Business One)

The OVPM table in SAP Business One is the master table for the initial payments. Each row represents a payment document that your company uses to pay money: usually to a supplier, less often as a refund to a customer or directly to an asset account.

You can find the initial payments in SAP Business One under Bank processing > Initial payments. The object type (ObjType) is 46. Incoming payments from customers are available not in OVPM. For that purpose, the table is ORCT (Input payments, ObjType 24) is responsible for.

What OVPM is used for

OVPM contains the header data of an outgoing payment: business partner, date of booking, total amount, currency and the breakdown into payment methods (cash, check, transfer, credit card). Each non-canceled outgoing payment generates a journal entry. Its transaction number is shown in the field TransId. Payments from the payment assistant also end up in OVPM.

The exact details of the payments made are not in my head; they are in the row tables:

VPM1: Checks for payment
VPM2: paid receipts (e.g. incoming invoices, Supplier vouchers, advance invoices, journal entries)
VPM3: Credit card lines
VPM4: Account balances upon account settlement

Important fields of the OVPM table

DocEntry: internal key of the payment voucher. This field links the row tables.
DocNum: Visible proof number of the initial payment (depending on the serial number) Series).
DocType: Type of payment recipient: S = Supplier, C = Customer, A = Account. The field describes not the means of payment.
CardCode / CardName: Code and name of the business partner to whom payment was made (reference to OCRD). In the case of a bank transfer, the field remains empty.
DocDate: Date of booking. TaxDate: Date of proof. DocDueDate: Due date.
DocTotal / DocTotalFC / DocTotalSy: Total amount in domestic currency, foreign currency and system currency.
DocCurr: Currency of payment (reference to OCRN).
CashSum, CheckSum, TrsfrSum, CreditSum: Shares of payment methods include cash, check, wire transfer and credit card. The associated accounts are listed below. CashAcct, CheckAcct and TrsfrAcct.
TrsfrDate / TrsfrRef: Date and purpose of the transfer.
Canceled: Y = cancelled, N = valid. There is no status such as „open“ or „balanced“ for payments.
TransId: Number of journal bookings generated (reference to OJDT).
PayMth / Status: Payment assistant number sequence and license plate, whether the payment was generated by a numerical sequence.
Comments / JrnlMemo: Notes and booking text of the journal booking.

Link to the paid documents

The paid invoices can be found in VPM2. There, the field contains DocNum the DocEntry the payment from OVPM. The field DocEntry in VPM2 refers to the paid receipt, and InvType names its object type: 18 = Initial invoice (OPCH), 19 = Supplier credit (ORPC), 204 = Advance payment invoice (ODPO), 30 = Journal booking (OJDT). The amount paid per receipt is shown in SumApplied.

Example: All valid initial payments to suppliers with the paid initial invoices.

SELECT
    T0.DocNum AS "Payment",
    T0.DocDate AS "Booking date",
    T0.CardCode,
    T0.CardName,
    T0.DocTotal AS "Amount",
    T0.DocCurr AS "Currency",
    T2.DocNum AS "Invoicing",
    T1.SumApplied AS "Paid on account"
FROM OVPM T0
INNER JOIN VPM2 T1 ON T1.DocNum = T0.DocEntry
INNER JOIN OPCH T2 ON T2.DocEntry = T1.DocEntry AND T1.InvType = '18'
WHERE T0.Canceled = 'N'
  AND T0.DocType = 'S'
ORDER BY T0.DocDate DESC

Demarcation

OVPM vs. ORCT: OVPM contains initial payments (money flows in); ORCT contains incoming payments (money flows out). Both tables have an almost identical structure.
OVPM vs. OPDF: Payment drafts are stored in OPDF. Only after they are added does an invoice appear in OVPM.
No connection to the customer order: OVPM does not directly refer to orders. The linking process always takes place via the paid invoices in VPM2.