Skip to main content

Commonly used Tables in SD

Customer Master Data 

KNA1 - General Data
KNB1 - Company Code Data
KNVV - Sales Area Data
KNVP - Partner Function Data
KNVI - Tax Classification Data

Material Master Data

MARA - Basic Data
MARC - Plant Level Data
MARD - Storage Location Data
MARDH - Storage Location history Data
MVKE - Sales Data
MBEW - Accounting Data
MBEWH - Accounting History Data

Customer Material Info Record

KNMT - Customer-Material Info Record Data Table

Sales Document Data

VBAK - Header Data
VBAP - Item Data
VBEP - Schedule Line Data
VBKD - Business Data
VBUK - Sales Document Status
VBFA - Document Flow
VBPA - Sales Partner Data

Delivery Document Data

LIKP - Header Data
LIPS - Item Data

Billing Document Data

VBRK - Header Data
VBRP - Item Data

Pricng Tables

KONV - Conditions (Transaction Data)

Logic to fetch pricing data from KONV Table

Fetch KNUMV (Condition Number)  from VBAK table and pass onto KONV table to fetch conditions data

Pricing Field Catalog Structures

KOMK - Communication Header for Pricing
KOMP - Communication Item for Pricing
KOMG - Allowed Fields for Condition Structures

Address Tables

ADRC - Addresses (Business Address Services)
ADR2 - Telephone Numbers (Business Address Services)
ADR3 - Fax Numbers (Business Address Services)
ADR4 - Teletex Numbers (Business Address Services
ADR5 - Telex Numbers (Business Address Services)
ADR6 - E-Mail Addresses (Business Address Service)
ADR7 - Remote Mail Addresses (SAP - SAP - Communication)

Logic to fetch Address data from customer Master Data

Fetch ADRNR from KNA1 table and pass ADRNR into above address tables to fetch relevant data

Logic to fetch Address data from Sales, Delivery and Billing Partner Data

Fetch ADRNR from VBPA table and pass ADRNR into above address tables to fetch relevant data


Comments

Popular posts from this blog

M7021 : Deficit of stock relevant error message during Material Document Cancellation

Issue : When posting a Cancellation for a Material Document in transaction MIGO, you see error 'M7021 Deficit of not stock relevant' although the Purchase Order is setup with an Account assignment. Material / Batch is not managed on Stock Level even though material is valuated. Resolution : The issue is due to program bug and require to implement note - 2502183 - Slog: correction for quantity check. This note is applicable for S/4 HANA 1610 (S4CORE 101) and 1709 (S4CORE 102).

Add Custom fields to sales order screen in Additional Tab B - Header

SAP has provided Additional data Tab A and Tab B for the addition of custom fields to the Standard sales order screen. Screens 8309, 8310 are used for header level and 8459,8460 for item level. Prior to this, we are required to append the custom fields of the Sales order sub screen in VBAK or VBAP. Pass Custom field values in PAI of screen 8309 within Chain statement CHAIN. FIELD: VBAK-<Custom Field 1>         VBAK-<Custom Field 2>         VBAK-<Custom Field 3> ENDCHAIN. Thank you.

User Exits in Delivery

FORM routine USEREXIT_REFRESH_DOCUMENT (include MV50AFZ1) Purpose The FORM routine USEREXIT_REFRESH_DOCUMENT is used for the initialization of your own data areas before the processing of a new delivery document. Call The routine is called from within the standard routine BELEG_DATEN_INIT (SAPMV50A). Basically, the data initialization is called on the following occasions: FORM routine USEREXIT_DELETE_DOCUMENT (include MV50AFZ1) Purpose If a delivery is deleted, you can delete your own dependent data using this FORM routine. Call The FORM routine is called from the FORM routine BELEG_LOESCHEN (SAPMV50A) if the document can be deleted completely. Immediately after the FORM routine  USEREXIT_DELETE_DOCUMENT is called, the document backup is called for which the logically deleted delivery is removed from the database. FORM routine USEREXIT_READ_DOCUMENT (include MV50AFZ1) Purpose The exit is used to make your own data availabl...