The "Big Two" SAP Financial Accounting (FI) Transaction Data Tables

 BKPF - Accounting Document Header

 BSEG - Accounting Document Segment

Table BKPF holds the Header data for all Financial transactions in SAP while table BSEG holds the Segment or Item data for all
Financial transaction in SAP. In Alteryx you will typically extract data from both tables in order to get the full picture for a Financial
transaction.

There are a number of other SAP Financial Accounting transaction tables that can be used in association with BKPF and BSEG.

Tables that can be used with BKPF:

 BVOR - Intercompany posting procedures
 BSIP - Index for Vendor Validation of Double Documents (Note: "Double" means Duplicate)

Tables that can be used with BSEG:

 BSID - Accounting: Secondary Index for Customers (Open Items)
 BSAD - Accounting: Secondary Index for Customers (Cleared Items)
 BSIK - Accounting: Secondary Index for Vendors (Open Items)
 BSAK - Accounting: Secondary Index for Vendors (Cleared Items)
 BSIS - Accounting: Secondary Index for G/L accounts (Open Items)
 BSAS - Accounting: Secondary Index for G/L Accounts (Cleared Items)

The following SAP Financial Accounting transaction tables are also useful and can be used in association with table BKPF:
 BSEC - One-Time Account Data Document Segment
 BSET - Tax Data Document Segment

Key SAP Controlling (CO) Transaction Data Tables

Cost Centre Accounting
 COBK - CO Object: Document Header
  COEP - CO Object: Line Items (by Period)
 COSP - CO Object: Cost Totals for External Postings
Profit Centre Accounting
 GLPCC - EC-PCA: Transaction Attributes
 GLPCO - EC-PCA: Object Table for Account Assignment Elements
 GLPCA - EC-PCA: Actual Line Items
 GLPCT - EC-PCA: Totals Table

Important SAP Finance and Controlling (FI/CO) Master Data Tables

General Ledger
 SKA1 - G/L Account Master (Chart of Accounts)
 SKAT - G/L Account Master Record (Chart of Accounts: Description)
 SKB1 - G/L account master (Company Code)
Cost Centre
 CSKS - Cost Center Master Record
 CSKT - Cost Center Texts
Cost Element
 CSKA - Cost Elements (Data Dependent on Chart of Accounts)
 CSKU - Cost Element Texts
 CSKB - Cost Elements (Data Dependent on Controlling Area)
Profit Centre
 CEPC - Profit Center Master Data Table
 CEPCT - Profit Center Master Data
Accounts Payable - Vendor Master Data
Vendor Master - General Data
 LFA1 - Vendor / Supplier Master (General Section)
 LFBK - Vendor / Supplier Master (Bank Details)
Vendor Master - Purchasing Data
 LFM1 - Vendor Master Record purchasing organization data
 LFM2 - Vendor Master Record: Purchasing Data
Vendor Master - Company Code Data
 LFB1 - Vendor Master (Company Code)
 LFB5 - Vendor master (dunning data)
Accounts Receivable - Customer Master Data
Customer Master - General Data
 KNA1 - General Data in Customer Master
Customer Master - Sales Area Data
 KNVP - Customer Master Partner Functions
 KNVV - Customer Master Sales Data
Customer Master - Company Code Data
 KNB1 - Customer Master (Company Code)
 KNB5 - Customer master (dunning data)

Useful SAP Finance and Controlling (FI/CO) Configuration Data Tables

 M_KOSTS - Generated View for Matchcode ID KOST-S (Cost Centre Texts)
 T001 - Company Codes
 T001K - Valuation area
 T077S - G/L account groups
 TBSL and TBSLT - Posting Key and Posting Key Names
SAP S/4HANA Finance Tables
 ACDOCA - Universal Journal Entry Line Items

With SAP S/4HANA, table ACDOCA contains all the Item data for Finance ( Controlling (CO) and Asset Accounting (AA).
ACDOCA can be used as an alternative to:
 BSEG - Accounting Document Segment
 COEP - CO Object: Line Items (by Period)

Table BKPF still holds the Header data for all Financial transactions in SAP S/4HANA.
TYPES OF SAP PROJECTS
1. SAP Implementation Project:

Company wants to implement SAP Module for the first time. In implementation projects consultant from various modules do
configuration based on company requirements. Role of consultants are configuration, integration of several modules, Data migration
from Legacy system to SAP system, prepare interfaces/RFC’s to interact with sap/3rd party systems, testing’s, document preparation,
end user training etc. Methodology suggests by SAP for implementation is ACTIVE/(old)ASAP.

2. SAP Support Project.

After implementation of SAP modules customer/business need assistance of consultants in their day-to-day business operations using
SAP software. The end user raises their concerns, issues, errors etc., through a ticket handling tool. A ticket handing tool is must for a
support project, it helps to track the status of tickets. Basically, there is no phases in it. Roles of a consultant Accept /Acknowledge the
tickets, analysis the issue, document it, solve, provide solutions to client, Get confirmation from the user & close the ticket.

Change request and service request is the main roles in support projects.

The important roles and responsibilities in the Support project are

Issues and errors resolution

Provide assistance to the users during the month and year-end activities

Configuration in existing system as per requirements of a client.

We can two types of supporting projects i.e.

Ticket Based Support: In this project, we support to the client’s companies based on the Tickets

To raises a SAP ticket and the priority is set in one of the below:

1. Low 2. Medium 3. High.

 Once the calls came to the work group the support consultant or the team needs to send an IR (Initial Response) to the
user depending upon the priority of the calls. (Top, High, Med, Low, None)

Example of SAP Support ticket raise

End user is not able to Create Sales order for a customer from a New plant, since shipping point determination is not
happened. (Without Shipping point the document becomes INCOMPLETE and he will not be able to proceed further
like DELIVERY, BILLING).

Now you need to solve this ticket. You would analyze the problem and identify that the SP configuration has to be done
for the new plant.

You would request a transport for DEV CLIENT to BASIS. You do the change and Request one more Transport to
BASIS for QA client. The End user will test the same by creating a sales order for the new plant and approve it.

Finally, you request a transport to move the changes to PRODUCTION. Once the change is deployed in production the
TICKET is closed.

Production Support: The support team will be available by 24/7 for support in production system.

3. Roll Out Project

Company is already using SAP, but they want to implement SAP for another country/plant or legal entity based on the existing
country. Roll Out project can implement

To follow a unique method of transactions recording

To generate consolidated financial statements within the SAP system.

The different types of Rollout projects are

Country Rollout: In this Rollout project, we will copy the data from the existing company to a new country.
Company Code Rollout: In this project, we will copy the data from an existing company to a new company.

4. Upgradation / Migration Project

It involves upgrading from the old version to the new version of the SAP system. The duration of upgrade project can be For Example:
– Migrating from SAP ECC Systems to the S4Hana system.

It also involves the implementation of new functionalities like

Implementation of New G/L Accounting functionality

Adapting Material ledgers, etc.