SAP PSOLF Saving Changed Vendors for Execution Table data and field list

PSOLF is a standard SAP Table which is used to store Saving Changed Vendors for Execution data in SAP systems, such as SAP R/3, S/4HANA, depending on the version and release level.

The PSOLF table consists of various fields, each holding specific information or linking keys about Saving Changed Vendors for Execution data available in SAP. These include LIFNR (Account Number of Vendor or Creditor), BUKRS (Company Code)... See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .

PSOLF table Technical Details:

Delivery Class: A - Application table (master and transaction data)
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type)


SAP PSOLF table fields - Full list of fields found in SAP data dictionary

Looking for S/4HANA specific information? Click here to explore the details, fields and extensibility available for this table in the SAP S/4HANA version of the PSOLF table. Also check whether the table still exists or has been transformed into a CDS view as part of the HANA simplifications.
Field Description Data Element Data Type length (Dec) Check table Conversion Routine Domain Name MemoryID SHLP
MANDTClient MANDTCLNT3Assigned to domainMANDT
LIFNRAccount Number of Vendor or Creditor LIFNRCHAR10Assigned to domainALPHALIFNRLIFKRED_C
BUKRSCompany Code BUKRSCHAR4Assigned to domainBUKRSBUKC_T001

Key field Non-key field



How do I retrieve data from SAP table PSOLF using ABAP code

The following ABAP code Example will allow you to do a basic selection on PSOLF to SELECT all data from the table
DATA: WA_PSOLF TYPE PSOLF.

SELECT SINGLE *
FROM PSOLF
INTO CORRESPONDING FIELDS OF WA_PSOLF
WHERE...

How to access SAP table PSOLF

Within an ECC or HANA version of SAP you can also view further information about PSOLF and the data within it using relevant transactions such as

SE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).