Analysis of Customers and Vendors in SAP ECC

To conduct a comprehensive analysis of customers and vendors in SAP, you can refer to the following tables and reports:

Customer Master Data:

  1. Tables:

    • KNA1 - General Data in Customer Master
    • KNVV - Customer Sales Area Data
    • KNVP - Customer Master Partner Functions
    • KNB1 - Customer Master Company Code Data
    • KNC1 - Customer Master Credit Control Area Data
    • VBAK - Sales Document: Header Data
    • VBRK - Billing Document: Header Data

  2. Reports:

    • RFDKAG00 - Customers with Missing Data (General Data)
    • RFDABL00 - Inactive Customers
    • RVKRED77 - Credit Management: Check Open Documents
    • S_ALR_87012179 - Customer List

Vendor Master Data:

  1. Tables:

    • LFA1 - General Data in Vendor Master
    • LFB1 - Vendor Master Company Code Data
    • LFM1 - Vendor Master Purchasing Data
    • LFBK - Vendor Master Bank Details
    • EKBE - Purchasing Document History
    • RBKP - Invoice Document Header

  2. Reports:

    • RFKKAG00 - Vendors with Missing Data (General Data)
    • RFLAEX00 - Inactive Vendors
    • ME2N - Purchase Orders by Vendor
    • S_ALR_87012086 - Vendor List

Customer-Supplier Relationships:

  1. Tables:

    • BUT050 - BP Relationships
    • KNVP - Customer Master Partner Functions

  2. Reports:

    • BP Relationships Report (transaction code BP)

Archiving Analysis:

  1. Tables:

    • ARCRL - Archive Administration: Contents of Archive
    • ARCHIVE_DOCS - Archive Documents Table

  2. Reports:

    • SARA - Archive Administration (to evaluate and manage archiving objects)

By reviewing these tables and reports, you can determine the activity status, completeness, and relationships of your customer and vendor master data, and identify candidates for archiving.

Comments

Post a Comment

Popular posts from this blog

How to Use MDS_LOAD_COCKPIT - a Quick View

How to Use MDS_LOAD_COCKPIT for Synchronizing Business Partners with Customers/Vendors Many customers often inquire about how to effectively use the MDS_LOAD_COCKPIT tool to synchronize Business Partners (BP) with Customers or Vendors in SAP. In this article, I will guide you through the step-by-step process to achieve this synchronization using the MDS_LOAD_COCKPIT transaction. Step 1: Launching MDS_LOAD_COCKPIT To begin the synchronization process, you first need to run the transaction code MDS_LOAD_COCKPIT in SAP. This transaction is specifically designed for synchronizing master data between Business Partners and Customers/Vendors. Step 2: Selecting the Synchronization Process Once you enter the MDS_LOAD_COCKPIT, you will see the "Synchronization Process" section in the top-left corner of the screen. This is where you can choose the synchronization process that fits your requirements. Before proceeding, it's essential to ensure that the desired synchronization proces...
Read more

Integration of GRC and C-IAG

GRC / IAC Integrating SAP Access Control 12.0 with SAP Cloud Identity Access Governance: A Step-by-Step Guide This guide provides a comprehensive overview of integrating SAP Access Control 12.0 (GRC AC) with SAP Cloud Identity Access Governance (IAG). The integration allows GRC AC to facilitate access requests and perform risk analysis for cloud applications. If you do not have a GRC AC system, consider using the IAG Standard edition. Prerequisites Before beginning the integration, ensure the following steps are completed: IAG Initial Setup : Ensure that SAP Cloud Identity Access Governance is properly set up. Cloud Application Connection : Connect at least one cloud application (e.g., SAP Ariba). Repository Synchronization : Run the repository sync job in IAG for the target cloud application. Cloud Connector Setup : Complete the initial configuration, including user credentials. Integration Process Overview 1. Connect Cloud Connector with IAG Subaccount Action Details Log in to Cloud ...
Read more

How to Check Error Logs in MDS_PPO2 - Quick View

 How to Check Error Logs in MDS_PPO2 for Synchronization Issues in SAP In a previous blog, I introduced how to use the transaction code MDS_LOAD_COCKPIT for synchronizing Business Partner (BP) data with Customer or Vendor data in SAP. However, when working with S/4HANA systems or after activating Customer Vendor Integration (CVI) in an ERP system, you might encounter issues where changes made to a BP in the customer/vendor role are not saved correctly. These issues are often due to errors in the synchronization process. To troubleshoot these issues, you can use the transaction code MDS_PPO2 to check error logs. In this article, I will guide you through the steps to identify and analyze synchronization errors using MDS_PPO2 . Scenario: Failed Synchronization of Customer Data Imagine you’ve just made a change to the house number for Customer 100430 and saved it. However, upon checking, you notice that the corresponding BP data hasn’t been updated successfully. This indicates that a...
Read more