This document displays relationships between SAP database tables. Tables are displayed graphically showing one-to-one, one-to-many, and cluster relationships. Key tables described include those for profit centers, cost centers, customers, vendors, general ledger accounts, and various FI/CO and MM transaction tables.
Blogs on Document Splitting at www.veritysolutions.com.au
Document Splitting is a very powerful feature delivered by SAP ECC.
Previous to SAP ECC, if new fields were required to General Ledger SAP had to deliver these new fields in Special Purpose Ledger tables. Profit Centre Accounting in R3 was Special Purpose Ledger table 8*, Joint Venture Accounting was ledger 4*. This essentially meant that data had to be copied from General Ledger table GLT0 to special ledger tables so these could be reported upon. However, technical glitches in code and incorrect usage of functionalities caused imbalances between the main ledger GLT0 and the special purpose ledgers.
SAP customers who wanted to expand the functionality of General Ledger to cater to special business requirements (like reporting General Ledger with another fiscal year variant) had to create custom Special Purpose Ledger tables. For example, if a customer wanted to report by two fiscal year variants, they could report one variant using General Ledger and the other variant using Special Purpose Ledger.
All this disparate ledgers reported the same source information in different views. Customers had to execute several month end jobs to ensure synchronisation of data across all these ledgers. Differences in balances and information between ledgers led to delays in month end close and reporting.
With SAP ECC new GL, SAP Customers can add new fields (which SAP calls “scenarios”) into General Ledger. This allows customers to perform, for example, Profit Centre Accounting and Reporting within General Ledger.
With SAP ECC new GL, SAP Customers can add new ledgers (which SAP calls “parallel accounting”) into General Ledger. This allows customers to report, for example, the same General Ledger data in multiple fiscal year variants.
This replication of data happens in real-time. SAP customers no longer need to execute month end jobs to synchronise data between different ledgers.
as per my experinece i have prepared this docuemnt for future referenec and also this document will help to leart GST impact in SAP SD and S4 HANA
Kindly comment your feedback and suggistions
Automatic Vendor payment advice notes by email with attachment when a payment is made via APP (Automatic payment program by using T-code F110 and email a sap script form as a PDF attachment along with the mail body in the desired language.
S4 HANA sattlement management_Ganesh Tarlana Ganesh Tarlana
Settlement Management functionality supports all types of settlement processes, including core business processes that need to be fully integrated in the order-to-cash cycle or within in a procure-to-pay scenario, such as condition contract settlement (rebate settlement), as well as standalone processes, whereby you provide special financial settlement services for your business partners
SAP FICO Overview, This Slide provides you the Basic Overview of SAP FICO ,Finance and Controlling module deals with the Financial Management of an Organisation. SAP Provides an ERP Solution to handle Accounts for Major Enterprises
Blogs on Document Splitting at www.veritysolutions.com.au
Document Splitting is a very powerful feature delivered by SAP ECC.
Previous to SAP ECC, if new fields were required to General Ledger SAP had to deliver these new fields in Special Purpose Ledger tables. Profit Centre Accounting in R3 was Special Purpose Ledger table 8*, Joint Venture Accounting was ledger 4*. This essentially meant that data had to be copied from General Ledger table GLT0 to special ledger tables so these could be reported upon. However, technical glitches in code and incorrect usage of functionalities caused imbalances between the main ledger GLT0 and the special purpose ledgers.
SAP customers who wanted to expand the functionality of General Ledger to cater to special business requirements (like reporting General Ledger with another fiscal year variant) had to create custom Special Purpose Ledger tables. For example, if a customer wanted to report by two fiscal year variants, they could report one variant using General Ledger and the other variant using Special Purpose Ledger.
All this disparate ledgers reported the same source information in different views. Customers had to execute several month end jobs to ensure synchronisation of data across all these ledgers. Differences in balances and information between ledgers led to delays in month end close and reporting.
With SAP ECC new GL, SAP Customers can add new fields (which SAP calls “scenarios”) into General Ledger. This allows customers to perform, for example, Profit Centre Accounting and Reporting within General Ledger.
With SAP ECC new GL, SAP Customers can add new ledgers (which SAP calls “parallel accounting”) into General Ledger. This allows customers to report, for example, the same General Ledger data in multiple fiscal year variants.
This replication of data happens in real-time. SAP customers no longer need to execute month end jobs to synchronise data between different ledgers.
as per my experinece i have prepared this docuemnt for future referenec and also this document will help to leart GST impact in SAP SD and S4 HANA
Kindly comment your feedback and suggistions
Automatic Vendor payment advice notes by email with attachment when a payment is made via APP (Automatic payment program by using T-code F110 and email a sap script form as a PDF attachment along with the mail body in the desired language.
S4 HANA sattlement management_Ganesh Tarlana Ganesh Tarlana
Settlement Management functionality supports all types of settlement processes, including core business processes that need to be fully integrated in the order-to-cash cycle or within in a procure-to-pay scenario, such as condition contract settlement (rebate settlement), as well as standalone processes, whereby you provide special financial settlement services for your business partners
SAP FICO Overview, This Slide provides you the Basic Overview of SAP FICO ,Finance and Controlling module deals with the Financial Management of an Organisation. SAP Provides an ERP Solution to handle Accounts for Major Enterprises
SAP PM Training Manual - www.sapdocs.infosapdocs. info
SAP PM - Step by step training manual for beginners
Please visit http://sapdocs.info/sap/plant-maintenance/sap-pm-training-manual/ to download file for free
well,
This presentation gives very breif insight into SAP basics for noobs or dummies as i may call them (like me)
nevertheless i presume this is not an elegant presentation ....
2 TUP signifie « 2 Track Unified Process »: c’est un processus de développement logiciel qui implémente le Processus Unifié (UP).
2 TUP est un processus qui apporte une réponse aux contraintes de changement continuel imposées aux systèmes d’information de l’entreprise.
SAP FS PM Training | SAP FSPM Online Course | SAP FS-PMSAPIDESTRAINING
SAP FS PM Training by expert consultants with lab set up. Join for SAP Financial Services – Policy Management training. We deliver FS PM corporate Training
For more information visit us @:
SAP IDES TRAINING :
Phone : +91 8121 020 888
Mail : info@sapidestraining.com
Website : www.sapidestraining.com
Stats of Linkedin, Shine.com, Monster.com and Naukri.com shows that the demand of the candidate with an Informatica MDM skill is very high. If you have a passion for learning new things, then here you can explore many things. Glory IT Technologies Provides Live Instructor Led Informatica MDM Online Training by Certified Experts. Ensure Quality Training as well as empowers students with tools that consistently define for manage the critical data of an organization to provide a single point of reference.
We are SAP ABAP training and placement institute in Pune. Learn ABAP programming with industry expert and start your SAP career. Attend the first lecture as Free Demo.
Memorandum Of Association Constitution of Company.pptseri bangash
www.seribangash.com
A Memorandum of Association (MOA) is a legal document that outlines the fundamental principles and objectives upon which a company operates. It serves as the company's charter or constitution and defines the scope of its activities. Here's a detailed note on the MOA:
Contents of Memorandum of Association:
Name Clause: This clause states the name of the company, which should end with words like "Limited" or "Ltd." for a public limited company and "Private Limited" or "Pvt. Ltd." for a private limited company.
https://seribangash.com/article-of-association-is-legal-doc-of-company/
Registered Office Clause: It specifies the location where the company's registered office is situated. This office is where all official communications and notices are sent.
Objective Clause: This clause delineates the main objectives for which the company is formed. It's important to define these objectives clearly, as the company cannot undertake activities beyond those mentioned in this clause.
www.seribangash.com
Liability Clause: It outlines the extent of liability of the company's members. In the case of companies limited by shares, the liability of members is limited to the amount unpaid on their shares. For companies limited by guarantee, members' liability is limited to the amount they undertake to contribute if the company is wound up.
https://seribangash.com/promotors-is-person-conceived-formation-company/
Capital Clause: This clause specifies the authorized capital of the company, i.e., the maximum amount of share capital the company is authorized to issue. It also mentions the division of this capital into shares and their respective nominal value.
Association Clause: It simply states that the subscribers wish to form a company and agree to become members of it, in accordance with the terms of the MOA.
Importance of Memorandum of Association:
Legal Requirement: The MOA is a legal requirement for the formation of a company. It must be filed with the Registrar of Companies during the incorporation process.
Constitutional Document: It serves as the company's constitutional document, defining its scope, powers, and limitations.
Protection of Members: It protects the interests of the company's members by clearly defining the objectives and limiting their liability.
External Communication: It provides clarity to external parties, such as investors, creditors, and regulatory authorities, regarding the company's objectives and powers.
https://seribangash.com/difference-public-and-private-company-law/
Binding Authority: The company and its members are bound by the provisions of the MOA. Any action taken beyond its scope may be considered ultra vires (beyond the powers) of the company and therefore void.
Amendment of MOA:
While the MOA lays down the company's fundamental principles, it is not entirely immutable. It can be amended, but only under specific circumstances and in compliance with legal procedures. Amendments typically require shareholder
Taurus Zodiac Sign_ Personality Traits and Sign Dates.pptxmy Pandit
Explore the world of the Taurus zodiac sign. Learn about their stability, determination, and appreciation for beauty. Discover how Taureans' grounded nature and hardworking mindset define their unique personality.
Attending a job Interview for B1 and B2 Englsih learnersErika906060
It is a sample of an interview for a business english class for pre-intermediate and intermediate english students with emphasis on the speking ability.
[Note: This is a partial preview. To download this presentation, visit:
https://www.oeconsulting.com.sg/training-presentations]
Sustainability has become an increasingly critical topic as the world recognizes the need to protect our planet and its resources for future generations. Sustainability means meeting our current needs without compromising the ability of future generations to meet theirs. It involves long-term planning and consideration of the consequences of our actions. The goal is to create strategies that ensure the long-term viability of People, Planet, and Profit.
Leading companies such as Nike, Toyota, and Siemens are prioritizing sustainable innovation in their business models, setting an example for others to follow. In this Sustainability training presentation, you will learn key concepts, principles, and practices of sustainability applicable across industries. This training aims to create awareness and educate employees, senior executives, consultants, and other key stakeholders, including investors, policymakers, and supply chain partners, on the importance and implementation of sustainability.
LEARNING OBJECTIVES
1. Develop a comprehensive understanding of the fundamental principles and concepts that form the foundation of sustainability within corporate environments.
2. Explore the sustainability implementation model, focusing on effective measures and reporting strategies to track and communicate sustainability efforts.
3. Identify and define best practices and critical success factors essential for achieving sustainability goals within organizations.
CONTENTS
1. Introduction and Key Concepts of Sustainability
2. Principles and Practices of Sustainability
3. Measures and Reporting in Sustainability
4. Sustainability Implementation & Best Practices
To download the complete presentation, visit: https://www.oeconsulting.com.sg/training-presentations
RMD24 | Debunking the non-endemic revenue myth Marvin Vacquier Droop | First ...BBPMedia1
Marvin neemt je in deze presentatie mee in de voordelen van non-endemic advertising op retail media netwerken. Hij brengt ook de uitdagingen in beeld die de markt op dit moment heeft op het gebied van retail media voor niet-leveranciers.
Retail media wordt gezien als het nieuwe advertising-medium en ook mediabureaus richten massaal retail media-afdelingen op. Merken die niet in de betreffende winkel liggen staan ook nog niet in de rij om op de retail media netwerken te adverteren. Marvin belicht de uitdagingen die er zijn om echt aansluiting te vinden op die markt van non-endemic advertising.
3.0 Project 2_ Developing My Brand Identity Kit.pptxtanyjahb
A personal brand exploration presentation summarizes an individual's unique qualities and goals, covering strengths, values, passions, and target audience. It helps individuals understand what makes them stand out, their desired image, and how they aim to achieve it.
Remote sensing and monitoring are changing the mining industry for the better. These are providing innovative solutions to long-standing challenges. Those related to exploration, extraction, and overall environmental management by mining technology companies Odisha. These technologies make use of satellite imaging, aerial photography and sensors to collect data that might be inaccessible or from hazardous locations. With the use of this technology, mining operations are becoming increasingly efficient. Let us gain more insight into the key aspects associated with remote sensing and monitoring when it comes to mining.
Buy Verified PayPal Account | Buy Google 5 Star Reviewsusawebmarket
Buy Verified PayPal Account
Looking to buy verified PayPal accounts? Discover 7 expert tips for safely purchasing a verified PayPal account in 2024. Ensure security and reliability for your transactions.
PayPal Services Features-
🟢 Email Access
🟢 Bank Added
🟢 Card Verified
🟢 Full SSN Provided
🟢 Phone Number Access
🟢 Driving License Copy
🟢 Fasted Delivery
Client Satisfaction is Our First priority. Our services is very appropriate to buy. We assume that the first-rate way to purchase our offerings is to order on the website. If you have any worry in our cooperation usually You can order us on Skype or Telegram.
24/7 Hours Reply/Please Contact
usawebmarketEmail: support@usawebmarket.com
Skype: usawebmarket
Telegram: @usawebmarket
WhatsApp: +1(218) 203-5951
USA WEB MARKET is the Best Verified PayPal, Payoneer, Cash App, Skrill, Neteller, Stripe Account and SEO, SMM Service provider.100%Satisfection granted.100% replacement Granted.
India Orthopedic Devices Market: Unlocking Growth Secrets, Trends and Develop...Kumar Satyam
According to TechSci Research report, “India Orthopedic Devices Market -Industry Size, Share, Trends, Competition Forecast & Opportunities, 2030”, the India Orthopedic Devices Market stood at USD 1,280.54 Million in 2024 and is anticipated to grow with a CAGR of 7.84% in the forecast period, 2026-2030F. The India Orthopedic Devices Market is being driven by several factors. The most prominent ones include an increase in the elderly population, who are more prone to orthopedic conditions such as osteoporosis and arthritis. Moreover, the rise in sports injuries and road accidents are also contributing to the demand for orthopedic devices. Advances in technology and the introduction of innovative implants and prosthetics have further propelled the market growth. Additionally, government initiatives aimed at improving healthcare infrastructure and the increasing prevalence of lifestyle diseases have led to an upward trend in orthopedic surgeries, thereby fueling the market demand for these devices.
Business Valuation Principles for EntrepreneursBen Wann
This insightful presentation is designed to equip entrepreneurs with the essential knowledge and tools needed to accurately value their businesses. Understanding business valuation is crucial for making informed decisions, whether you're seeking investment, planning to sell, or simply want to gauge your company's worth.
Unveiling the Secrets How Does Generative AI Work.pdfSam H
At its core, generative artificial intelligence relies on the concept of generative models, which serve as engines that churn out entirely new data resembling their training data. It is like a sculptor who has studied so many forms found in nature and then uses this knowledge to create sculptures from his imagination that have never been seen before anywhere else. If taken to cyberspace, gans work almost the same way.
Discover the innovative and creative projects that highlight my journey throu...dylandmeas
Discover the innovative and creative projects that highlight my journey through Full Sail University. Below, you’ll find a collection of my work showcasing my skills and expertise in digital marketing, event planning, and media production.
1. SAP Table Relations
version 1.0.0
compiled by
Christopher Solomon
with
contributions by
various SAP Professionals
2. How to use this document?
This document displays and describes the relationships and links between the various SAP database tables. These relationships are
displayed graphically as described below:
Table Key
Transparent Table Cluster Table
SAP Table Name SAP Table Information SAP Table Name
(Table Description) (Table Description)
SAP Field Name (Field Description)
SAP Field Name (Field Description)
Useful Fields
Link Key
One-to-One
One One
One-to-Many
One Many
3. Master Data Tables
CEPC = Profit Center Master Data Table
CSKS = Cost Center Master
KNA1 = Cutomer Master (General Data)
LFA1 = Vendor Master (General Data)
MARA = Material Master (General Data)
SKB1 = G/L Account Master (Company Code)
T001W = Plants/Branches
T001 = Company Codes
4. SAP - FI/CO
Accounts
Payable
Reconcillation Ledger
General Financial Special Purpose
Ledger Accounting Ledger
Custom
Ledger
Accounts
Receivable
Controlling
Profit Center Cost Center
Accounting Accounting
Tables:
BSAD
BSAS
BSEG
BSES
BSIK
BSIS
6. BSIP
BVOR PAYR (Index for vendor validation of double
(Intercompany posting procedures) (Payment transfer medium file) documents)
Intercompany No (BVORG) Paying Company (ZBUKR) Company Code (BUKRS)
Company Code (BUKRS) House Bank (HBKID) Vendor (LIFNR)
Account (HKTID)
Fiscal Year (GJAHR) Currency (WAERS)
Payment Method (ZLSCH)
Document No (BELNR) Document Date (BLDAT)
Check No (CHECKT) Duplicate Invoices Reference Doc (WRBTR)
Amount (WRBTR)
VBLNR Document No (BELNR)
Fiscal Year (GJAHR)
Line Items (BUZEI)
BKPF
(Accounting document header)
BSAD Company Code (BUKRS)
BSIK
(Accounting: Secondary index for Document No (BELNR) (Accounting: Secondary index for
customers (cleared items)) Fiscal Year (GJAHR) vendors)
Company Code (BUKRS)
Customer (KUNNR) Company Code (BUKRS)
documents
Special G/L Trans (UMSKS) Vendor (LIFNR)
All FI
Special G/L Ind (UMSKZ) Closed items Open Items Special G/L Trans (UMSKS)
Clearing Date (AUGDT) Special G/L Ind (UMSKZ)
Clearing Doc (AUGBL) Clearing Date (AUGDT)
Allocation No (ZUONR) Clearing Doc (AUGBL)
Fiscal Year (GJAHR) Allocation No (ZUONR)
BSEG
Document No (BELNR) Fiscal Year (GJAHR)
(Accounting document segment)
Line Items (BUZEI) Document No (BELNR)
Company Code (BUKRS) Line Items (BUZEI)
Document No (BELNR)
Fiscal Year (GJAHR)
Line Item (BUZEI) Closed items
Open Items BSAK
(Accounting: Secondary index for
BSID
vendors (cleared items))
(Accounting: Secondary index for
customers) Company Code (BUKRS)
Vendor (LIFNR)
Company Code (BUKRS) Special G/L Trans (UMSKS)
Customer (KUNNR) Special G/L Ind (UMSKZ)
Special G/L Trans (UMSKS) Clearing Date (AUGDT)
Special G/L Ind (UMSKZ) Closed items Clearing Doc (AUGBL)
Open Items
Clearing Date (AUGDT) Allocation No (ZUONR)
Clearing Doc (AUGBL) Fiscal Year (GJAHR)
Allocation No (ZUONR) Document No (BELNR)
Fiscal Year (GJAHR) Line Items (BUZEI)
Document No (BELNR)
Line Items (BUZEI) KNC1
(Customer master (trans figures))
BSAS Customer (KUNNR)
BSIS (Accounting: Secondary index for G/L Company Code (BUKRS)
accounts (cleared items)) Fiscal Year (GJAHR)
Company Code (BUKRS) Company Code (BUKRS)
G/L Account (HKONT) G/L Account (HKONT)
Clearing Date (AUGDT) Clearing Date (AUGDT)
Clearing Doc (AUGBL) Clearing Doc (AUGBL) LFC1
Allocation No (ZUONR) Allocation No (ZUONR) (Vendor master (transaction figures))
Fiscal Year (GJAHR) Fiscal Year (GJAHR) Vendor (LIFNR)
Document No (BELNR) Document No (BELNR) Company Code (BUKRS)
Line Items (BUZEI) Line Items (BUZEI) Fiscal Year (GJAHR)
7. SAP FI/CO
Financial Accounting
RFBLG
BKPF
(Cluster for accounting
(Accounting document header)
document)
Company Code BSEC
Document No BSED
Fiscal Year BSEG Physical
BSES
BSET
BSEG
(Accounting document
segment)
Company Code
ts
en Document No
c um Fiscal Year
Line Item
do
I
F
ll
A
BSEC
BKPF One time accounts (One-time account data
(Accounting document header)
document segment)
Company Code
Document No Company Code Logical
Fiscal Year Ta Document No
x Fiscal Year
do
cu Line Item
m
en
ts
BSET
(Tax data document
segment)
Company Code
Document No
Fiscal Year
Line Item
8. SAP FI/CO
Controlling Special Purpose Ledger
Profit Center GLPCA
Accounting (EC-PCA: Actual Line Items) Example of a Custom
Record No (GL_SIRID) Ledger
GLPCT
(EC-PCA: Totals Table) ZZGLO
Ledger(RLDNR) ROBJNR Object (OBJNR)
Record Type (RRCTY) ROBJNR
GLPCO
Plan Version (RVERS) (EC-PCA: Object Table for Account
Fiscal Year (GJAHR) ZZGLT
Assignment Elements)
Object (ROBJNR)
Object (COBJNR) COBJNR Object (OBJNR)
Ledger(RLDNR)
Object (SOBJNR) Record Type (RRCTY)
Currency (RTCUR) Version (RVERS)
UOM (RUNIT) ZZGLO Fiscal Year (GJAHR)
Debit/Credit Ind (DRCRX) Object (ROBJNR)
Period (RPMAX) Record No (GL_SIRID) Object (SOBJNR)
GLPCC Currency (RTCUR)
(EC-PCA: Transaction Attributes) UOM (RUNIT)
Object (OBJNR) Debit/Credit Ind (DRCRX)
Period (RPMAX)
________________________________________________________
Cost Center COEP COFIO2
(CO object: period-related line items) Reconcillation (Transaction-dependent fields for
Accounting Controlling Area (KOKRS) Ledger reconciliation ledger)
NR
Document No (BELNR) BJ Object (OBJNR)
COSP COFIT CO
Line Item (BUZEI)
(CO Object: Cost Totals - External (Totals records - reconciliation ledger)
Postings)
Ledger (LEDNR) Ledger(RLDNR)
Object (J_OBJNR) Record Type (RRCTY)
Fiscal Year (GJAHR) Version (RVERS)
Value Type (WRTTP) Fiscal Year (GJAHR) ROBJNR
Version (VERSN) Object (ROBJNR)
Cost Element (KSTAR) Object (COBJNR)
CO Key (HRKFT) Object (SOBJNR)
CO Trans (VRGNG) Currency (RTCUR)
Trading Part ID (VBUND) COFIO1
UOM (RUNIT) (Object Table for Reconciliation
Trading Part BA (PARGB) COBK Debit/Credit Ind (DRCRX)
Ledger COFIT)
Debit/Credit Ind (BEKNZ) Period (RPMAX)
Currency (TWAER) Object (OBJNR)
Controlling Area (KOKRS)
Period Block (PERBL) Document No (BELNR)
9. SAP FI/CO
Accounts Payable
Vendor Master Data
Purchasing Data General Data Company Code Data
LFM1 LFA1 LFB1
(Vendor master record purchasing (Vendor master (general section)) (Vendor master (company code))
organization data)
Vendor No (LIFNR) Vendor No (LIFNR)
Vendor No (LIFNR)
Company Code (BUKRS)
Purch Org (EKORG)
LFM2
(Vendor Master Record: Purchasing LFBK LFB5
Data) (Vendor master (bank details)) (Vendor master (dunning data))
Vendor No (LIFNR) Vendor No (LIFNR) Vendor No (LIFNR)
Purch Org (EKORG) Bank Cntry (BANKS) Company Code (BUKRS)
Sub-range (LTSNR) Bank Key (BANKL) Dunning Area (MABER)
Plant (WERKS) Bank Acc (BANKN)
10. SAP FI/CO
Accounts Receivable
Customer Master Data
Sales Area Data General Data Company Code Data
KNVP
(Customer Master Partner Functions)
Customer No (KUNNR)
Sales Org (VKORG) KNA1 KNB1
Distribution Ch (VTWEG) (General Data in Customer Master) (Customer master (company code))
Division (SPART)
Partner Function (PARVW) Customer No (KUNNR) Customer No (KUNNR)
Partner Counter (PARZA) Company Code (BUKRS)
KNVV
(Customer Master Sales Data)
Customer No (KUNNR)
KNB5
Sales Org (VKORG)
(Customer master (dunning data))
Distribution Ch (VTWEG)
Division (SPART) Customer No (KUNNR)
Company Code (BUKRS)
Dunning Area (MABER)
KNVD
(Customer master record sales
request form)
Customer No (KUNNR)
Sales Org (VKORG)
Distribution Ch (VTWEG)
Division (SPART)
Output Type (NA_KSCHL)
Mess Language (SPRAS)
11. SAP FI/CO
Master Data
Cost Elemet
Profit Center Cost Center
CSKA
(Cost elements (data dependent on
CEPC CSKS chart of accounts))
(Profit center master data table) (Cost center master) COA (KTOPL)
Profit Center (PRCTR) Controlling Area (KOKRS) Cost Element (KSTAR)
Valid to Date (DATBI) Cost Center (KOSTL)
Controlling Area (KOKRS) Valid to Date (DATBI)
CSKB
(Cost elements (data dependent on
controlling area))
Controlling Area (KOKRS)
COA (KTOPL)
Cost Element (KSTAR)
Valid to Date (DATBI)
CEPCT CSKT
(Texts for Profit Center Master Data) (Cost Center Texts)
Language (SPRAS) Language (SPRAS) CSKU
Profit Center (PRCTR) Controlling Area (KOKRS) (Cost Element Texts)
Valid to Date (DATBI) Cost Center (KOSTL) Language (SPRAS)
Controlling Area (KOKRS) Valid to Date (DATBI) COA (KTOPL)
Cost Element (KSTAR)
General Ledger
SKB1 SKA1 SKAT
(G/L account master (company code)) (G/L accounts master (chart of (G/L account master record (chart of
Company Code (BUKRS) accounts)) accounts: description))
G/L Account (SAKNR) COA (KTOPL) Language (SPRAS)
G/L Account (SAKNR) COA (KTOPL)
G/L Account (SAKNR)
13. KNMT
(Customer-Material
Info Record Data
Table)
makt-matnr = knmt-matnr
and
makt-spras = sy-langu
MAKT
(Material
Description)
MDKP
(MRP Header)
EKKO
(Purchasing Doc
Header)
MDKP-DTNUM =
MDTB-DTNUM
EKPO-EBELN =
EKKO-EBELN
MDTB
(MRP Detail)
EKPO
(Purchasing Doc
Item)
MM
Table Mapping
14. SAP MM - Purchasing
Purchasing Requisition
EBKN
STXH EBAN (Purchase Requisition Account
(STXD SAPscript text file header) (Purchase Requisition) Assignment)
Texts (TDOBJECT) Purchasing Req (BANFN) Purchasing Req (BANFN)
Text Name (TDNAME) Item (BNFPO) Item (BNFPO)
Text Id (TDID) Preg Account Assignment (ZEBKN)
Language (TDSPRAS)
STXL
(STXD SAPscript text file lines))
(RELID)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(SRTF2)
15. SAP MM - Purchasing
Purchase Orders
S011 S012
(PURCH: Purch. Group Statistics) (PURCHIS: Purchasing Statistics)
EINE
Statistics (SSOUR) Statistics (SSOUR)
(Purchasing Info Record: Purchasing
Version (VRSIO) Version (VRSIO)
Organization Data)
Month (SPMON) Month (SPMON)
Day (SPTAG) Day (SPTAG) Info Record (INFNR)
Week (SPWOC) Week (SPWOC) Purchasing Org (EKORG)
Posting Period (SPBUP) Posting Period (SPBUP) Info Record Type (ESOKZ)
Purchasing Org (EKORG) Purchasing Org (EKORG) Plant (WEKS)
Purchasing Group (EKGRP) Purchasing Group (EKGRP)
Vendor No (LIFNR) Material No (MATNR)
Plant (WERKS)
Info Record Category (ESOKZ)
Material Group (MATKL)
Info Record (INFNR)
Country (LAND1)
EKET
(Delivery Schedules)
Purchasing Doc (EBELN)
Item (EBELP)
Delivery Schedule (ETENR)
EKPO EINA
(Purchasing Document Item) (Purch Info Record: General Data)
Purchasing Doc (EBELN) Info Record (INFNR)
Item (EBELP)
EKKN
(Account Assignment in Purchasing
Document)
Purchasing Doc (EBELN)
Item (EBELP)
Account Assignment (ZEKKN)
EKKO EORD
(Purchasing Document Header) (Purchasing Source List)
Purchasing Doc (EBELN) Material No (MATNR)
Plant (WERKS)
Source List No (ZEORD)
16. SAP MM - Purchasing
Goods Receipt
S011
(PURCHIS: Purchasing Group
Statistics)
Statistics (SSOUR)
Version (VRSIO)
MKPF MSEG Month (SPMON)
(Header: Material Document) (Document Segment: Material) Day (SPTAG)
Document No (MBLNR) Document No (MBLNR) Week (SPWOC)
Fiscal Year (MJAHR) Fiscal Year (MJAHR) Posting Period (SPBUP)
Line Item (ZEILE) Purchasing Org (EKORG)
Purchasing Group (EKGRP)
Vendor No (LIFNR)
S013
(PURCHIS: Statistics for Vendor
Evaluation)
Statistics (SSOUR)
S031 Version (VRSIO)
EKBE MVER (Statistics: Movements for current Month (SPMON)
(History of Purchasing Document) (Material consumption) stocks) Day (SPTAG)
Purchasing Doc (EBELN) Statistics (SSOUR) Week (SPWOC)
Material NO (MATNR)
Item (EBELP) Version (VRSIO) Posting Period (SPBUP)
Plant (WERKS)
Account Assign (ZEKKN) Month (SPMON) Purchasing Org (EKORG)
Fiscal Year (GJAHR)
Trans Type (VGABE) Day (SPTAG) Purchasing Group (EKGRP)
Period (PERKZ)
Fiscal Year (MJAHR) Week (SPWOC) Vendor No (LIFNR)
Follow-on Records (ZAHLR)
Document No (MBLNR) Posting Period (SPBUP) Material No (MATNR)
Line Item (ZEILE) Plant (WERKS) Plant (WERKS)
Material No (MATNR) Info Record Cat (ESOKZ)
Storage Loc (LGORT) Info Record (INFNR)
17. SAP MM - Master Data
Purchasing Data Basic Data Accounting Data
MARC MAKT
(Material Master: C Segment) (Material Descriptions)
Material No (MATNR) Material No (MATNR)
Plant (WERKS) Language (SPRAS)
MARA MBEW
(Material Master: General Data) (Material Valuation)
Material No (MATNR) Material No (MATNR)
Valuation Area (BWKEY)
Valuation Type (BWTAR)
MARM
MLAN
(Units of Measure)
(Tax Classification: Material)
Material No (MATNR)
Material No (MATNR)
UOM (MEINH)
Country (ALAND)
18. SAP MM - Purchasing
Purchasing Info Record
KONP KONH
(Conditions (Item)) (Conditions (Header))
Condition No (KNUMH) Condition No (KNUMH)
Seq No (KOPOS)
EINA EINE
(Purchasing Info Record: General (Purchasing Info Record: Purchasing
Data) Organization Data)
Info Record (INFNR) Info Record (INFNR)
Purchasing Org (EKORG)
Info Record Type (ESOKZ)
Plant (WERKS)
A017
(Material Info Record (Plant-Specific))
Application (KAPPL)
Condition Type (KSCHL)
Vendor (LIFNR)
Material No (MATNR)
Purchasing Org (EKORG)
Plant (WERKS)
Info Record Category (ESOKZ)
Validity (DATBI)
21. SAP PP - Project Planning
PROJECTS
Project and WBS element numbers have a domain with a conversion
function module which converts it from 8 numc input to 24 char on output.
PROJ
(Project definition)
Project Number (PSPNR)
Project Name (PSPID)
PRTE
(Scheduling Data for Project Item)
PRPS Project Number (PSPHI)
(WBS (Work Breakdown Structure) WBS Element Number (POSNR)
Element Master Data))
Project Number (PSPHI)
WBS Element Number (PSPNR)
WBS Name (POSID) PRTX
(PS Texts (WBS))
WBS Element Number (PRPSPNR)
Text Identifier (PRTXTKY)
PRHIS
(Standard WBS, Edges (Hierarchy
pointers))
Project Number (PSPHI)
WBS Element Number (POSNR) PSTX
(PS Texts (Header))
Text Identifier (PRTXTKY)
PS text description (PSTXTTI)
PSTT
(PS texts (description))
Text Identifier (PRTXTKY)
PS text: Description(PTKTEXT)
22. SAP - Sales and Distribution
Sales
Finacial Accounting Accounts Receivable
Shipping Sales and Distribution
Materials Mgmt. Material Master
Billing
Tables:
KONV
LIKP
LIPS
VBAK
VBAP
VBBE
VBEH
VBEP
VBFA
VBLB
VBLK
VBPA
VBRK
VBRP
VBUK
VBUP
VEKP
VEPO
VEPVG
24. SAP SD - Sales Tables
VKDFS
(SD Index:Billing Initiator) STXL
(STXD SAPscript text file lines)
Billing Cat (FKTYP)
Sales Org (VKORG) (RELID)
STXH
Billing Date (FKDAT) Texts (TDOBJECT)
(STXD SAPscript text file header)
Customer (KUNNR) Text Name (TDNAME)
Texts (TDOBJECT) Text Id (TDID)
Billing Type (FKART)
Text Name (TDNAME) Language (TDSPRAS)
Country (LLAND)
Text Id (TDID) (SRTF2)
Sales doc (VBELN) VBUK
Language (TDSPRAS)
(Header Status)
Sales doc (VBELN)
VAPMA
(SD Index:Order Items by Material)
Material No (MATNR)
Sales Org (VKORG) VBFA
Trans Group (TRVOG) (Sales Document Flow)
Document Date (AUDAT) VBAK
Distribution Channel (VTWEG) Preceding Sales Doc (VBELV)
(Sales Document :Header)
Division (SPART) Preceding Item (POSNV)
Document Type (AUART) Sales doc (VBELN) Subsequent Sales doc (VBELN)
VBUP
Sold-to-Party (KUNNR) Subsequent Item (POSNN)
(Item Status)
Sales Office (VKBUR) Document Cat (VBTYP_N)
Sales doc (VBELN)
Sales Group (VKGRP) Item (POSNR)
Customer PO No (BSTNK)
User Name (ERNAM)
Sales Ord (VBELN)
Item (POSNR)
To Shipping through
LIPS
LIPS-VGBEL = VBAP-VBELN
VAKPA VBAP and
(SD Index:Order by Partner Function) (Sales Document : Item Info) LIPS-VGPOS = VBAP-POSNR
Sales doc (VBELN)
Partner No (KUNDE)
Item (POSNR)
Partner Function (PARVW)
Sales Org (VKORG)
Trans Group (TRVOG)
Document Date (AUDAT)
Sales Office (VKBUR)
Sales Group (VKGRP)
VBKD
Distribution Channel (VTWEG)
VBEP (Sales Document : Business Data)
Division (SPART)
(Sales Document : Schedule Lines)
Document Type (AUART) Sales doc (VBELN)
Customer PO No (BSTNK) Sales doc (VBELN) Item (POSNR)
Sold-to-Party (KUNNR) Item (POSNR)
User Name (ERNAM) Schedle Line (ETENR)
Sales Ord (VBELN)
VBEH VBPA
(Schedule Line History) (Sales Document :Partner)
Sales doc (VBELN) Sales doc (VBELN)
Item (POSNR) Item (POSNR)
Schedle Line (ETENR) Partner Function (PARVW)
25. SAP SD - Shipping Tables
VTTP
(Shipment Item) VBLK
Delivery Doc Number(VBELN) (SD:Delivery Note Header)
Shipment Number (TKNUM) Delivery Document Number (VBELN)
Shipment Item (TPNUM)
VTTP-VBELN =
VTTK-TKNUM = LIKP-VBELN
VTTP-TKNUM
VBLK-VBELN =
LIKP-VBELN VEPO
VTTK (SD Doc:Shipping Item content)
(Shipment Header) Delivery Document Number (VBELN)
Shipment Number (TKNUM) Delivery Item (POSNR)
LIKP
(Sales Doc:Delivery Header) Shipping Unit Number (VENUM)
Shipping Unit Item (VEPOS)
Delivery Document Number (VBELN)
VTFA
(Shipment Doc. Flow) VEPO-VENUM =
Shipment Number (TKNUM) VEKP-VENUM
VBUK
Preceeding Doc. (VBELV)
(Header Status)
VEPO-VBELN =
Delivery doc (VBELN)
LIPS-VBELN
and VEKP
VEPO-POSNR = (SD Doc:Shipping Unit Header)
LIPS-POSNR Shipping Unit Number(VENUM)
VBFA LIPS-VBELN =
(Sales Document Flow) LIKP-VBELN
Preceding Sales Doc (VBELV)
Preceding Item (POSNV) VBUP
Subsequent Sales doc (VBELN) (Item Status)
Subsequent Item (POSNN) Deliverydoc (VBELN)
Document Cat (VBTYP_N) Item (POSNR)
From Sales throughVBAP LIPS
LIPS-VGBEL = VBAP-VBELN (Sales Doc:Delivery Items) To Biling through VBRP
and Delivery Document Number (VBELN) VBRP-VGBEL = LIPS-VBELN
LIPS-VGPOS = VBAP-POSNR Item (POSNR) and
VBRP-VGPOS = LIPS-POSNR
26. SAP SD - Billing Tables
VKDFS VBSK VBSS
VRKPA
(SD Index: Billing Initiator) (Collective Processing for a Sales (Collective Processing: Sales
(Sales Index: Bills by Partner
Document Header) Documents)
Functions) Billing Cat (FKTYP)
Partner No (KUNDE) Sales Org (VKORG) Grouped Delivery (SAMMG) Grouped Delivery (SAMMG)
Partner Function (PARVW) Billing Date (FKDAT) Sales doc (VBELN)
Sales Org (VKORG) Customer (KUNNR)
Billing Date (FKDAT) Billing Type (FKART)
Distribution Channel (VTWEG) Country (LLAND)
Billing Type (FKART) Sales doc (VBELN)
Payer (KUNNR)
Sold-to-Party (KUNNR)
SD Doc Cat (VBTYP)
User Name (ERNAM) NAST
Billing Doc (VBELN) (Billing: Header Data)
Application (KAPPL)
Object (OBJKY)
VBRK Output Type (KSCHL)
(Billing: Header Data) Language (SPRAS)
VRPMA Mess Partner (PARNR)
(SD Index: Billing Items per Material) Billing doc (VBELN) Partner Func (PARVW)
Date (ERDAT)
Material No (MATNR) Time (ERUHR)
Sales Org (VKORG)
Billing Date (FKDAT)
Distribution Channel (VTWEG)
Billing Type (FKART)
Payer (KUNNR)
Sold-to-Party (KUNNR) VBUK
SD Doc Cat (VBTYP) (Header Status)
User Name (ERNAM) Sales doc (VBELN)
Billing Doc (VBELN)
Item (POSNR)
VBRP
(Billing: Item Data)
Billing doc (VBELN)
Item (POSNR)
From Shipping through
LIPS VBFA
VBRP-VGBEL = LIPS-VBELN (Sales Document Flow)
and Preceding Sales Doc (VBELV)
VBRP-VGPOS = LIPS-POSNR Preceding Item (POSNV)
Subsequent Sales doc (VBELN)
VBUP Subsequent Item (POSNN)
(Sales Document: Item Status) Document Cat (VBTYP_N)
Sales doc (VBELN)
Item (POSNR)
27. SAP SD - Links to FI Tables
Customer Master Data
Sales Area Data General Data Company Code Data
KNVP
(Customer Master Partner Functions)
Customer No (KUNNR)
Sales Org (VKORG) KNA1 KNB1
Distribution Ch (VTWEG) (General Data in Customer Master) (Customer master (company code))
Division (SPART) Customer No (KUNNR) Customer No (KUNNR)
Partner Function (PARVW) Company Code (BUKRS)
Partner Counter (PARZA)
KNVV
(Customer Master Sales Data)
Customer No (KUNNR) KNB5
Sales Org (VKORG) (Customer master (dunning data))
Distribution Ch (VTWEG) Customer No (KUNNR)
Division (SPART) Companu Code (BUKRS)
Dunning Area (MABER)
KNVD
(Customer master record sales
request form)
Customer No (KUNNR)
Sales Org (VKORG)
Distribution Ch (VTWEG)
Division (SPART)
Output Type (
28. SAP SD - Links to MM Tables
Material Master Data
Sales Data Basic Data Sales Text Data
MARC
MAKT
(Material Master: C Segment)
(Material Descriptions)
Material No (MATNR) Material No (MATNR)
Plant (WERKS) Language (SPRAS)
STXH
(STXD SAPscript text file header)
MVKE
Texts (TDOBJECT)
(Material Master: Sales Data)
Text Name (TDNAME)
Material No (MATNR) Text Id (TDID)
Sales Org (VKORG) Language (TDSPRAS)
Distribution Chan (VTWEG)
MARA
Product Hierarchy (PRODH)
(Material Master: General Data)
Material No (MATNR)
T179
(Materials: Product Hierarchies)
Product Hierarchy (PRODH)
STXL
*use to ge text for hiearchy levels (STXD SAPscript text file lines)
(RELID)
MARM Texts (TDOBJECT)
(Units of Measure) Text Name (TDNAME)
MLAN Material No (MATNR) Text Id (TDID)
(Tax Classification: Material) UOM (MEINH) Language (TDSPRAS)
Material No (MATNR) (SRTF2)
Country (ALAND)
29. Contributions by
Master Data FI/CO HR
Jim Lewis (Whittman-Hart, inc.) Michael Rhodes (MedPartners, inc.)
MM SD
PP Paul Evans (Whittman-Hart, inc.)
Jim Lewis (Whittman-Hart, inc.)
Krishna Prasad (Whittman-Hart, inc.)
Michael Rhodes (MedPartners, inc.)
Russ Smith (Benteler)
Michael Rhodes (MedPartners, inc.)