This document describes relationships between SAP tables. It includes tables related to financial accounting (FI/CO), materials management, purchasing, accounts payable, accounts receivable, and more. Key tables described include BKPF for document headers, BSEG for document line items, CEPC for profit centers, CSKS for cost centers, EKKO and EKPO for purchase orders, KNA1 and KNB1 for customer master data, and LFA1 and LFB1 for vendor master data. Relationships are shown graphically and include one-to-one, one-to-many, transparent, and cluster table links.
The document describes relationships between SAP database tables related to financial accounting, materials management, and master data. Key tables include BKPF for document headers, BSEG for document line items, MARA for material master general data, and CEPC for profit center master data. Tables are mapped between functional areas, such as linking purchasing documents to goods receipts. Fields like company code, document number, and material number are commonly used to link related records across tables.
This document displays relationships between SAP database tables related to financial accounting (FI), materials management (MM), and master data. Key FI tables include BKPF, BSEG, BSIK, and BSAD for accounting documents and KNA1, LFA1, and MARA for master data. Key MM tables include EKKO, EKPO, and MSEG for purchasing documents and MKPF and MSE for goods receipts. The document provides table mappings and descriptions to understand how different business processes and master data are linked in SAP.
The document discusses various SAP MM business scenarios including procure to pay cycle, vendor consignment, pipeline procurement, subcontracting, and stock transport order. It provides details on the key transactions and accounting entries for each scenario. The procure to pay cycle involves purchase requisition, request for quotation, purchase order processing, goods receipt, and invoice receipt. Vendor consignment uses purchase order, goods movement, and material document. Pipeline procurement uses goods issue and material document. Subcontracting requires BOM, purchase requisition, purchase order, and goods movement. Stock transport order can be intra-company or inter-company.
This document displays relationships between SAP database tables. Tables are shown graphically linked by relationships like one-to-one and one-to-many. It includes tables for master data, financial accounting, materials management, and purchasing. Key FI/CO tables shown include BKPF, BSEG, BSAD, and tables for profit centers, cost centers, and G/L accounts. Key MM tables include EKKO, EKPO, and tables for materials, purchasing documents, and goods receipt.
This document describes relationships between SAP tables. It includes tables related to financial accounting (FI/CO), materials management, purchasing, accounts payable, accounts receivable, and more. Key tables described include BKPF, BSEG, MARA, KNA1, LFA1, and others. Relationships shown include one-to-one, one-to-many, and links. The document is intended to help understand how data moves between SAP tables.
Yes, this is correct behavior in SAP. Inventory and non-inventory items cannot be billed together in the same billing document. At the time of billing document creation, SAP will split the delivery into two billing documents - one for inventory items and another for non-inventory items.
This is done to maintain the separation between inventory and non-inventory transactions in the accounting. Inventory items involve stock/goods movement and valuation, whereas non-inventory items are direct expenses. Keeping them separate in billing helps maintain the integrity of inventory and non-inventory accounting entries.
So in summary:
- Delivery can contain both inventory and non-inventory items
- But at billing, SAP will automatically split and create separate billing
This document provides an overview of PI sheets in SAP, which can be used to inform production operators of steps to perform. There are two types: ABAP-based and browser-based. Browser-based PI sheets are configured by defining master data like materials and BOMs, transporting standard SAP settings, creating control recipes and destinations, defining process message characteristics, assigning process instructions to recipes, releasing control recipes to generate PI sheets, and using the sheets to record operator inputs and update order data. PI sheets allow recording of various production activities and values in a flexible manner.
Sap Study Materials and certification exam dumpERP Training
This document provides a list of certification courses, study materials, and exam dumps for SAP S/4HANA 1909 modules including Sourcing & Procurement, Sales, Logistics, Finance, and Treasury & Risk Management. It outlines training video courses and certification books at discounted prices for each module in SAP S/4HANA 1909 and earlier releases.
The document describes relationships between SAP database tables related to financial accounting, materials management, and master data. Key tables include BKPF for document headers, BSEG for document line items, MARA for material master general data, and CEPC for profit center master data. Tables are mapped between functional areas, such as linking purchasing documents to goods receipts. Fields like company code, document number, and material number are commonly used to link related records across tables.
This document displays relationships between SAP database tables related to financial accounting (FI), materials management (MM), and master data. Key FI tables include BKPF, BSEG, BSIK, and BSAD for accounting documents and KNA1, LFA1, and MARA for master data. Key MM tables include EKKO, EKPO, and MSEG for purchasing documents and MKPF and MSE for goods receipts. The document provides table mappings and descriptions to understand how different business processes and master data are linked in SAP.
The document discusses various SAP MM business scenarios including procure to pay cycle, vendor consignment, pipeline procurement, subcontracting, and stock transport order. It provides details on the key transactions and accounting entries for each scenario. The procure to pay cycle involves purchase requisition, request for quotation, purchase order processing, goods receipt, and invoice receipt. Vendor consignment uses purchase order, goods movement, and material document. Pipeline procurement uses goods issue and material document. Subcontracting requires BOM, purchase requisition, purchase order, and goods movement. Stock transport order can be intra-company or inter-company.
This document displays relationships between SAP database tables. Tables are shown graphically linked by relationships like one-to-one and one-to-many. It includes tables for master data, financial accounting, materials management, and purchasing. Key FI/CO tables shown include BKPF, BSEG, BSAD, and tables for profit centers, cost centers, and G/L accounts. Key MM tables include EKKO, EKPO, and tables for materials, purchasing documents, and goods receipt.
This document describes relationships between SAP tables. It includes tables related to financial accounting (FI/CO), materials management, purchasing, accounts payable, accounts receivable, and more. Key tables described include BKPF, BSEG, MARA, KNA1, LFA1, and others. Relationships shown include one-to-one, one-to-many, and links. The document is intended to help understand how data moves between SAP tables.
Yes, this is correct behavior in SAP. Inventory and non-inventory items cannot be billed together in the same billing document. At the time of billing document creation, SAP will split the delivery into two billing documents - one for inventory items and another for non-inventory items.
This is done to maintain the separation between inventory and non-inventory transactions in the accounting. Inventory items involve stock/goods movement and valuation, whereas non-inventory items are direct expenses. Keeping them separate in billing helps maintain the integrity of inventory and non-inventory accounting entries.
So in summary:
- Delivery can contain both inventory and non-inventory items
- But at billing, SAP will automatically split and create separate billing
This document provides an overview of PI sheets in SAP, which can be used to inform production operators of steps to perform. There are two types: ABAP-based and browser-based. Browser-based PI sheets are configured by defining master data like materials and BOMs, transporting standard SAP settings, creating control recipes and destinations, defining process message characteristics, assigning process instructions to recipes, releasing control recipes to generate PI sheets, and using the sheets to record operator inputs and update order data. PI sheets allow recording of various production activities and values in a flexible manner.
Sap Study Materials and certification exam dumpERP Training
This document provides a list of certification courses, study materials, and exam dumps for SAP S/4HANA 1909 modules including Sourcing & Procurement, Sales, Logistics, Finance, and Treasury & Risk Management. It outlines training video courses and certification books at discounted prices for each module in SAP S/4HANA 1909 and earlier releases.
A functional specification describes a product's intended capabilities, appearance, and user interactions in detail for software developers. It includes requirements defined by product planners based on market and customer input, objectives written by designers in response to requirements, a logic specification of code modules and structure, and user documentation derived from previous documents to instruct users. Ideally, the final product fully implements the functional specification and design changes identified during testing.
SAP PP stands for Production Planning. In SAP domain, SAP PP works as an integral part of logistics modality and it is integrated with other SAP modules like Materials Management (MM) and Plant Maintenance (PM). As production planning is an essential part of a company’s supply chain, SAP PP certified professionals are in great demand. Global Online Trainings conducts online SAP PP training for professionals willing to explore their career in SAP production and planning stream.
This is an overview for SAP HANA SD S/4 1709. for more details, please checkout: https://www.amazon.com/dp/B083C3X8YY ERP Made Simple: ERP Explained in 80 Pages or Less
This is a highlevel view of PP.
For more comprehensive details, please checkout: https://www.amazon.com/dp/B083C3X8YY ERP Made Simple: ERP Explained in 80 Pages or Less
This document describes the key data structures needed for the material management module of SAP for Capital Industries. It outlines the plant, storage location, purchase organization, and purchasing group structures. It also defines the material master settings like material type, material group, valuation class, and unit of measure. Vendor master settings like account groups, schema groups, payment terms, and Incoterms are provided. Service master categories and procurement document types for purchase requisition, quotation, and purchase order are listed. The pricing procedure and tax procedure for domestic and import transactions are specified. Finally, the document discusses the release strategy for approving purchase orders.
This document discusses the ASAP methodology for SAP implementations and provides details on key phases of the implementation process including scoping, as-is, to-be, business blueprint, realization, integration testing, and go-live preparation. It also defines baseline configuration and final configuration phases. Additionally, it provides guidance on creating end user manuals and documents the steps involved in understanding a client's existing "as-is" business processes during an SAP implementation.
Functional spcification doc for vendor debit memo reportLokesh Modem
The document describes a new vendor debit memo report that will be developed for SAP. The report will display information for vendor debit memos including plant, vendor, MIRO document number, document type, quantities, tax values, and totals. Selection criteria include plant, vendor, and date ranges. The report logic will retrieve document information from various SAP tables and sort it according to selection criteria.
The document provides an overview of key SAP tables used in different SAP modules like FI/CO, Controlling, Accounts Payable, Accounts Receivable, Profit Center Accounting, Cost Center Accounting, and more. It lists the table names, describes their purpose and relationship to other tables through lines and arrows. The tables store master data like vendor, customer, profit center and transactional data like documents, items, postings related to different business processes in SAP.
This document provides information on configuring organizational structures and master data in SAP SD. It discusses defining elements like company code, sales organization, distribution channel, and others. It also covers assigning these elements and defining related entities. Finally, it describes key master data used in SD, including customer, material, pricing, and partner records. The document is a guide for SD consultants to setup the required configuration for transactions.
This document lists SAP tables related to plant maintenance. It includes tables for maintenance orders, equipment master data, tasks lists, inspection characteristics, and more. The tables store information such as order headers and items, work orders, equipment, maintenance plans, bills of materials, and quality inspection results.
The document provides an introduction to the ERP structure in SAP. It discusses the key components including the client, company, plant, and storage location. It also outlines some of the main business processes in SAP like sales and distribution, materials management, financial accounting, and production planning. Finally, it shows how the different business processes are integrated together and how information flows between the procurement, production, and sales orders.
Important sap ewm tables for key functional areasGhassen B
This document provides a list of important tables in SAP Extended Warehouse Management (EWM) organized by key functional areas. It includes tables for waves, outbound and inbound deliveries, handling units, warehouse tasks, warehouse orders, stock and bins, physical inventory, transportation units, and more. An expanded list of EWM tables can be downloaded for more comprehensive reference.
SAP R3 Month-end Cross-Module Closing ScheduleMichael Knowles
This document provides a month-end closing cross-module planning schedule for SAP R3. It includes activities for various modules like FI, CO, LO, and their suggested sequence and timing. General notes provide guidance on dependencies between activities and updating the schedule. The schedule is intended to coordinate the month-end closing process across different areas to ensure a smooth closing.
This document discusses vendor master records in SAP, which contain all key information for a company's contacts with vendors, including for procurement and sales. It notes the vendor master contains details like name and address and is the main source of vendor data. The document also provides the menu path and transaction code for creating a vendor master record in SAP and lists some of the information sections included in a vendor record, such as purchasing organization data and bank details.
1. The document discusses planning, costing, and settlement concepts and configurations in SAP.
2. It includes topics like master data, cost elements, internal orders, production processes, value types, document types, and allocation methods.
3. The numerous SAP transaction codes mentioned relate to functions for budgeting, costing, activity management, profitability analysis, and financial posting.
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.
This document provides detailed configuration steps for Materials Management in SAP. It describes settings for enterprise structure such as defining valuation level, plants, storage locations, and purchasing organizations. It also covers assignments of these organizational units and defining attributes for material master, types, and number ranges. The goal is to configure Materials Management according to the business requirements of ITZ.
As functional consultants, during implimentation we are facing a lot of problems to simplify O2C process and sales order entry its self. After a lot of research to simplify sales order entry process with out enhancement and modifications, find out certain functionalities that improve End user experience. Please share your experience, opinions and suggestions.
This document provides an overview of ASAP's business blueprint for Crescent Pharmaceuticals' sales and distribution processes. It outlines the objective to map current business scenarios to SAP in order to configure the necessary processes. The methodology follows ASAP with documentation of current processes, gap analysis, and configuration. Key processes covered include sales orders, deliveries, billing, pricing, credit management, returns, and master data for customers and materials.
This document describes standard business processes for purchasing in SAP MM, including:
1) Stock purchases from non-ERS vendors using MRP and purchase orders.
2) Stock purchases from ERS vendors using purchase orders and automatic ERS invoices.
3) Direct purchases of non-stock items using purchase requisitions with account assignments.
4) Direct purchases of services using purchase requisitions with account assignments.
It provides step-by-step explanations of processes like MRP runs, purchase requisition creation and processing, purchase order creation, goods receipt, invoice receipt, and payment. Pre-requisites and configurations for different purchase scenarios are also outlined.
This document provides 3 levels of summaries for the SAP Table Relations document:
1) The document displays relationships between SAP database tables graphically and provides descriptions of table fields and relationships. It covers master data, financial, and materials management modules.
2) Key sections include an overview of master data, FI/CO, and materials management tables. The FI/CO section maps tables for accounts payable, accounts receivable, and financial accounting.
3) Table relationships for specific FI/CO processes are shown, like accounts payable linking vendor, purchasing, and invoice tables and accounts receivable linking customer, sales, and invoice tables.
This document displays relationships between SAP database tables. Tables are shown graphically linked by relationships like one-to-one and one-to-many. It includes tables for master data, financial accounting, materials management, and purchasing. Key FI/CO tables shown include BKPF, BSEG, BSAD, and tables for profit centers, cost centers, and G/L accounts. Key MM tables include EKKO, EKPO, and tables for materials, purchasing documents, and goods receipt.
A functional specification describes a product's intended capabilities, appearance, and user interactions in detail for software developers. It includes requirements defined by product planners based on market and customer input, objectives written by designers in response to requirements, a logic specification of code modules and structure, and user documentation derived from previous documents to instruct users. Ideally, the final product fully implements the functional specification and design changes identified during testing.
SAP PP stands for Production Planning. In SAP domain, SAP PP works as an integral part of logistics modality and it is integrated with other SAP modules like Materials Management (MM) and Plant Maintenance (PM). As production planning is an essential part of a company’s supply chain, SAP PP certified professionals are in great demand. Global Online Trainings conducts online SAP PP training for professionals willing to explore their career in SAP production and planning stream.
This is an overview for SAP HANA SD S/4 1709. for more details, please checkout: https://www.amazon.com/dp/B083C3X8YY ERP Made Simple: ERP Explained in 80 Pages or Less
This is a highlevel view of PP.
For more comprehensive details, please checkout: https://www.amazon.com/dp/B083C3X8YY ERP Made Simple: ERP Explained in 80 Pages or Less
This document describes the key data structures needed for the material management module of SAP for Capital Industries. It outlines the plant, storage location, purchase organization, and purchasing group structures. It also defines the material master settings like material type, material group, valuation class, and unit of measure. Vendor master settings like account groups, schema groups, payment terms, and Incoterms are provided. Service master categories and procurement document types for purchase requisition, quotation, and purchase order are listed. The pricing procedure and tax procedure for domestic and import transactions are specified. Finally, the document discusses the release strategy for approving purchase orders.
This document discusses the ASAP methodology for SAP implementations and provides details on key phases of the implementation process including scoping, as-is, to-be, business blueprint, realization, integration testing, and go-live preparation. It also defines baseline configuration and final configuration phases. Additionally, it provides guidance on creating end user manuals and documents the steps involved in understanding a client's existing "as-is" business processes during an SAP implementation.
Functional spcification doc for vendor debit memo reportLokesh Modem
The document describes a new vendor debit memo report that will be developed for SAP. The report will display information for vendor debit memos including plant, vendor, MIRO document number, document type, quantities, tax values, and totals. Selection criteria include plant, vendor, and date ranges. The report logic will retrieve document information from various SAP tables and sort it according to selection criteria.
The document provides an overview of key SAP tables used in different SAP modules like FI/CO, Controlling, Accounts Payable, Accounts Receivable, Profit Center Accounting, Cost Center Accounting, and more. It lists the table names, describes their purpose and relationship to other tables through lines and arrows. The tables store master data like vendor, customer, profit center and transactional data like documents, items, postings related to different business processes in SAP.
This document provides information on configuring organizational structures and master data in SAP SD. It discusses defining elements like company code, sales organization, distribution channel, and others. It also covers assigning these elements and defining related entities. Finally, it describes key master data used in SD, including customer, material, pricing, and partner records. The document is a guide for SD consultants to setup the required configuration for transactions.
This document lists SAP tables related to plant maintenance. It includes tables for maintenance orders, equipment master data, tasks lists, inspection characteristics, and more. The tables store information such as order headers and items, work orders, equipment, maintenance plans, bills of materials, and quality inspection results.
The document provides an introduction to the ERP structure in SAP. It discusses the key components including the client, company, plant, and storage location. It also outlines some of the main business processes in SAP like sales and distribution, materials management, financial accounting, and production planning. Finally, it shows how the different business processes are integrated together and how information flows between the procurement, production, and sales orders.
Important sap ewm tables for key functional areasGhassen B
This document provides a list of important tables in SAP Extended Warehouse Management (EWM) organized by key functional areas. It includes tables for waves, outbound and inbound deliveries, handling units, warehouse tasks, warehouse orders, stock and bins, physical inventory, transportation units, and more. An expanded list of EWM tables can be downloaded for more comprehensive reference.
SAP R3 Month-end Cross-Module Closing ScheduleMichael Knowles
This document provides a month-end closing cross-module planning schedule for SAP R3. It includes activities for various modules like FI, CO, LO, and their suggested sequence and timing. General notes provide guidance on dependencies between activities and updating the schedule. The schedule is intended to coordinate the month-end closing process across different areas to ensure a smooth closing.
This document discusses vendor master records in SAP, which contain all key information for a company's contacts with vendors, including for procurement and sales. It notes the vendor master contains details like name and address and is the main source of vendor data. The document also provides the menu path and transaction code for creating a vendor master record in SAP and lists some of the information sections included in a vendor record, such as purchasing organization data and bank details.
1. The document discusses planning, costing, and settlement concepts and configurations in SAP.
2. It includes topics like master data, cost elements, internal orders, production processes, value types, document types, and allocation methods.
3. The numerous SAP transaction codes mentioned relate to functions for budgeting, costing, activity management, profitability analysis, and financial posting.
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.
This document provides detailed configuration steps for Materials Management in SAP. It describes settings for enterprise structure such as defining valuation level, plants, storage locations, and purchasing organizations. It also covers assignments of these organizational units and defining attributes for material master, types, and number ranges. The goal is to configure Materials Management according to the business requirements of ITZ.
As functional consultants, during implimentation we are facing a lot of problems to simplify O2C process and sales order entry its self. After a lot of research to simplify sales order entry process with out enhancement and modifications, find out certain functionalities that improve End user experience. Please share your experience, opinions and suggestions.
This document provides an overview of ASAP's business blueprint for Crescent Pharmaceuticals' sales and distribution processes. It outlines the objective to map current business scenarios to SAP in order to configure the necessary processes. The methodology follows ASAP with documentation of current processes, gap analysis, and configuration. Key processes covered include sales orders, deliveries, billing, pricing, credit management, returns, and master data for customers and materials.
This document describes standard business processes for purchasing in SAP MM, including:
1) Stock purchases from non-ERS vendors using MRP and purchase orders.
2) Stock purchases from ERS vendors using purchase orders and automatic ERS invoices.
3) Direct purchases of non-stock items using purchase requisitions with account assignments.
4) Direct purchases of services using purchase requisitions with account assignments.
It provides step-by-step explanations of processes like MRP runs, purchase requisition creation and processing, purchase order creation, goods receipt, invoice receipt, and payment. Pre-requisites and configurations for different purchase scenarios are also outlined.
This document provides 3 levels of summaries for the SAP Table Relations document:
1) The document displays relationships between SAP database tables graphically and provides descriptions of table fields and relationships. It covers master data, financial, and materials management modules.
2) Key sections include an overview of master data, FI/CO, and materials management tables. The FI/CO section maps tables for accounts payable, accounts receivable, and financial accounting.
3) Table relationships for specific FI/CO processes are shown, like accounts payable linking vendor, purchasing, and invoice tables and accounts receivable linking customer, sales, and invoice tables.
This document displays relationships between SAP database tables. Tables are shown graphically linked by relationships like one-to-one and one-to-many. It includes tables for master data, financial accounting, materials management, and purchasing. Key FI/CO tables shown include BKPF, BSEG, BSAD, and tables for profit centers, cost centers, and G/L accounts. Key MM tables include EKKO, EKPO, and tables for materials, purchasing documents, and goods receipt.
This document displays relationships between SAP database tables. Tables are shown graphically linked by relationships like one-to-one and one-to-many. It includes tables for master data, financial accounting, materials management, and purchasing. Key tables shown include BKPF, BSEG, MARA, CEPC, CSKS, EKKO, and MAKT.
This document provides descriptions and codes for various accounting topics, accounts, and transaction types in SAP. It includes charts of accounts for general ledger, vendors, customers, and asset accounts. It also lists account types, document types, transaction codes, and tables related to financial accounting, bank accounting, materials management, sales and distribution, asset accounting, and year-end closing activities. Key accounts, document types, and transaction codes are identified for processes like invoice posting, payments, asset accounting, and period-end close.
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.
This document lists and describes important tables used in the SAP FI (Financial Accounting) and CO (Controlling) modules. It includes tables for master data, document headers and line items, account assignments, prices, and more. Some of the key tables mentioned are BKPF for accounting document headers, CSKS for cost center master data, and COBK for CO object document headers. Over 50 tables in total are described, with their main purpose and key fields provided.
The document describes important tables used in SAP FI (Financial Accounting). It lists the table name, description, and important fields for each table. Some key tables mentioned include:
- BKPF - Accounting document header
- BSEG - Accounting document segment
- SKB1 - G/L account master for company code
- SKA1 - G/L account master for chart of accounts
- SKAT - G/L account master record for account description
The tables store transactional document data like document header and segments, as well as master data for accounts, customers, vendors, and more. Fields include document number, company code, fiscal year, account numbers, and other
The PCA report contains all necessary data and can be configured using report painter to present the data in different layouts. Instructions for configuring report painter are available in forums.
The document provides a list of important tables used in SAP FI (Financial Accounting) modules. It includes tables for the general ledger, accounts receivable, accounts payable, asset accounting, bank accounting, and validation/substitution rules. Some of the key tables listed are BKPF for document headers, KNB1 for customer master, LFA1 for vendor master, SKA1 for the chart of accounts, and ANKA for asset classes.
This document provides a functional specification for generating a Payment Advice Note report in SAP. It details that the report is requested to be generated whenever a client makes a payment to a vendor, and should include payment summary details and vendor vs. customer clear adjustments. It outlines the input details and tables/fields required from various SAP tables including BSAK, BSAD, BSIK, BSID, PAYR, REGUH, WITH_ITEM, and LFA1. The report format is also specified as an attachment.
The document provides an agenda and overview for a training session on SAP FI-CO (financial accounting and controlling) modules. It includes sections on introducing SAP R/3 and its evolution, modules in SAP R/3 with a focus on FI-CO submodules, business processes, enterprise structure definitions, financial accounting basic settings, and new features in the SAP general ledger including document splitting. The training aims to provide participants with foundational knowledge on SAP financial modules and configurations.
The document outlines the monthly closing process steps in SAP FI, which includes executing reports for intercompany activity and journal entries, opening the next year's posting period, running business area assignment reports, reviewing and posting recurring journal entries, processing parked accounting documents, performing asset maintenance tasks like additions and retirements, entering payroll data, reconciling asset subledgers, checking bank data and open items, billing documents, inventory, and performing manual adjustments. Key month-end activities include foreign currency valuation, posting recurring entries, accrual/deferral entries, automatic clearing, maintaining exchange rates, posting depreciation, tax payments, and closing periods.
1. The document describes a proposed multi-organization business model for a global company called Globo with operations in Brazil, the UK, and the US.
2. Key aspects of the model include multi-currency, tax, and language support for different locations as well as intercompany accounting and consolidated reporting.
3. The proposal calls for setting up separate operating ledgers for foreign subsidiaries while facilitating data integration and consolidation.
The document provides an overview of SAP's FI (Financial Accounting) General Ledger module. It discusses the key subprocesses including master data, transaction processing, account analysis and reconciliation, periodic processing, and reporting. Transaction processing involves journal entry, document posting, account blocking, and account deletion. Account analysis includes displaying account balances and line items, as well as clearing open items.
A job oriented SAP FICO ONLINE TRAINING by real time domain experts with real time scenarios. Attend a free demo on SAP FICO COURSE to asses the quality of our training. Arrowsol Technologies provide both class room and online training.
The document provides an overview of SAP's FI (Financial Accounting) General Ledger module. It describes the key sub-processes and master data involved in general ledger processing, including transaction processing, account analysis and reconciliation, periodic processing, and reporting. The general ledger forms the core of SAP's financial accounting and integrates with other FI sub-modules and the CO (Controlling) module for management accounting.
This document contains parameters and details for configuring different cost center reports in SAP. It includes default values for fields like controlling area, fiscal year, period, cost center group, and more. It also describes the structure and columns for various standard reports showing actual and planned costs, variances, breakdowns by period, partner, and business transaction. Configuration details are provided for reports comparing costs across fiscal quarters and years.
on SQL Managment studio(For the following exercise, use the Week 5.pdfformaxekochi
on SQL Managment studio
(For the following exercise, use the Week 5 DB Design Excel file. Place the completed file in the
zip folder with your .sql files)
A landscaping firm has tasked you with developing a database for their company. You have
gathered requirements and have come up with the following list of data elements to construct a
basic data structure:
Client name Invoice number Equipment description
Invoice date Job description Payment total
Client city Equipment purchase date Employee name
Invoice total Client address
Client phone Employee payrate
Client zip code Client state
a. Using the DB Design Excel file, do the following:
Name the tables using the drop down menu above each table grid
Add the appropriate fields to each table using the drop down menus within the fields of each
table
Choose the correct data type for each field using the drop down menus within the data type
column next to the field.
Example:
(Vendors) (Invoices) (InvoiceLineItems) VendorID InvoiceID InvoiceSequence
VendorName VendorID (FK to Vendors) InvoiceID (FK to Invoices)
VendorAddress InvoiceDate InvoiceLineItemAmount
VendorAddress2 InvoiceTotal
VendorCity
New Database:
Create a new database named Finances.
Write a script that creates the following tables with the listed attributes. Reference foreign keys
where indicated. Be sure to create the tables in order of their dependencies (if you attempt to
create a table with a reference to another table that hasn’t been created, the script will fail).
Register table
RegisterID INT PK IDENTITY NOT NULL
TransactionID
Transactions table INT FK NOT NULL
TransactionID INT PK IDENTITY NOT NULL
AccountID VARCHAR(25) FK NOT NULL
TransactionDate SMALLDATETIME NOT NULL
TransactionAmount
Account table MONEY NOT NULL
AccountID VARCHAR(25) PK NOT NULL
AccountName VARCHAR(50) NOT NULL
AccountAddress VARCHAR(30) NULL
AccountCity VARCHAR(25) NULL
AccountState CHAR(2) NULL
AccountZip VARCHAR(10) NULL
AccountPhone VARCHAR(14) NULL
Create a database diagram of the Finances database. Take a screenshot of the diagram and save
it as a png file.
if you receive an error message informing you that you don’t have permission for the database,
run the following query:
ALTER AUTHORIZATION ON DATABASE::Finances TO sa
GO
Write a script that creates non-clustered indexes on the foreign keys in the Register and
Transactions tables.
Write an ALTER TABLE statement that adds check constraints to the following columns (use
NOCHECK):
AccountPhone (NOT NULL)
TransactionAmount ( > 0 )
Write an ALTER TABLE statement that adds the follow columns to these tables:
Register table:
ReferenceNo
Transactions table: VARCHAR(15) NULL
TransactionType VARCHAR(15) NOT NULL
TransactionCredit BIT NULL
In the Object Explorer, do the following
Expand the Finances database
Expand the Tables folder
Expand each table
Expand the Columns folder for each table
Expand the Constraints folder for the Account and Transactions tables
Expand the Indexes folder for the Register and Tr.
"Cold Call Campaigns Success visually represent data and information related to the effectiveness of cold calling in sales and marketing strategies. These graphics use a combination of charts, graphs, and illustrations to convey key insights and statistics in a concise and engaging manner.
The infographics may include data on conversion rates, lead generation, call-to-sale ratios, and other metrics to showcase the impact of cold calling on business growth. They can also highlight best practices, tips, and strategies for optimizing cold call campaigns to improve success rates.
By presenting complex information in a visually appealing format, these infographics make it easier for viewers to understand and digest the content quickly. This makes them an effective tool for businesses looking to communicate the benefits of cold calling and its role in driving sales success.
Overall, infographics on Cold Call Campaigns Success serve as a valuable resource for sales professionals, marketers, and business owners seeking to enhance their cold calling strategies and achieve greater success in their campaigns.
1. SAP Table Relations
version 1.0.0
compiled by
Christopher Solomon
with
contributions by
various SAP Professionals
2. Table Key
Link Key
One-to-One
One-to-Many
One One
One Many
SAP Table Name
(Table Description)
SAP Field Name (Field Description)
Useful Fields
SAP Table Information
How to use this document?
SAP Field Name (Field Description)
SAP Table Name
(Table Description)
Transparent Table Cluster Table
This document displays and describes the relationships and links between the various SAP database tables. These relationships are
displayed graphically as described below:
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
Financial
Accounting
Special Purpose
Ledger
Controlling
Accounts
Payable
General
Ledger
Accounts
Receivable
Reconcillation Ledger
Custom
Ledger
Profit Center
Accounting
Cost Center
Accounting
Tables:
BSAD
BSAS
BSEG
BSES
BSIK
BSIS
6. AllFI
documents
Closed items
Open Items
Closed items
Closed items
Open Items
Open Items
Duplicate Invoices
VBLNR
LFC1
(Vendor master (transaction figures))
Vendor (LIFNR)
Company Code (BUKRS)
Fiscal Year (GJAHR)
KNC1
(Customer master (trans figures))
Customer (KUNNR)
Company Code (BUKRS)
Fiscal Year (GJAHR)
BSAS
(Accounting: Secondary index for G/L
accounts (cleared items))
Company Code (BUKRS)
G/L Account (HKONT)
Clearing Date (AUGDT)
Clearing Doc (AUGBL)
Allocation No (ZUONR)
Fiscal Year (GJAHR)
Document No (BELNR)
Line Items (BUZEI)
BSIP
(Index for vendor validation of double
documents)
Company Code (BUKRS)
Vendor (LIFNR)
Currency (WAERS)
Document Date (BLDAT)
Reference Doc (WRBTR)
Amount (WRBTR)
Document No (BELNR)
Fiscal Year (GJAHR)
Line Items (BUZEI)
BSIK
(Accounting: Secondary index for
vendors)
Company Code (BUKRS)
Vendor (LIFNR)
Special G/L Trans (UMSKS)
Special G/L Ind (UMSKZ)
Clearing Date (AUGDT)
Clearing Doc (AUGBL)
Allocation No (ZUONR)
Fiscal Year (GJAHR)
Document No (BELNR)
Line Items (BUZEI)
BSAK
(Accounting: Secondary index for
vendors (cleared items))
Company Code (BUKRS)
Vendor (LIFNR)
Special G/L Trans (UMSKS)
Special G/L Ind (UMSKZ)
Clearing Date (AUGDT)
Clearing Doc (AUGBL)
Allocation No (ZUONR)
Fiscal Year (GJAHR)
Document No (BELNR)
Line Items (BUZEI)
BVOR
(Intercompany posting procedures)
Intercompany No (BVORG)
Company Code (BUKRS)
Fiscal Year (GJAHR)
Document No (BELNR)
PAYR
(Payment transfer medium file)
Paying Company (ZBUKR)
House Bank (HBKID)
Account (HKTID)
Payment Method (ZLSCH)
Check No (CHECKT)
BSAD
(Accounting: Secondary index for
customers (cleared items))
Company Code (BUKRS)
Customer (KUNNR)
Special G/L Trans (UMSKS)
Special G/L Ind (UMSKZ)
Clearing Date (AUGDT)
Clearing Doc (AUGBL)
Allocation No (ZUONR)
Fiscal Year (GJAHR)
Document No (BELNR)
Line Items (BUZEI)
BKPF
(Accounting document header)
Company Code (BUKRS)
Document No (BELNR)
Fiscal Year (GJAHR)
BSEG
(Accounting document segment)
Company Code (BUKRS)
Document No (BELNR)
Fiscal Year (GJAHR)
Line Item (BUZEI)
BSIS
Company Code (BUKRS)
G/L Account (HKONT)
Clearing Date (AUGDT)
Clearing Doc (AUGBL)
Allocation No (ZUONR)
Fiscal Year (GJAHR)
Document No (BELNR)
Line Items (BUZEI)
BSID
(Accounting: Secondary index for
customers)
Company Code (BUKRS)
Customer (KUNNR)
Special G/L Trans (UMSKS)
Special G/L Ind (UMSKZ)
Clearing Date (AUGDT)
Clearing Doc (AUGBL)
Allocation No (ZUONR)
Fiscal Year (GJAHR)
Document No (BELNR)
Line Items (BUZEI)
7. A
ll F
I
docum
ents
One time accounts
Tax
docum
ents
Financial Accounting
Physical
Logical
BKPF
(Accounting document header)
Company Code
Document No
Fiscal Year
BSEC
BSED
BSEG
BSES
BSET
Company Code
Document No
Fiscal Year
Line Item
Company Code
Document No
Fiscal Year
Line Item
BKPF
(Accounting document header)
Company Code
Document No
Fiscal Year
Company Code
Document No
Fiscal Year
Line Item
BSEG
(Accounting document
segment)
BSEC
(One-time account data
document segment)
BSET
(Tax data document
segment)
RFBLG
(Cluster for accounting
document)
SAP FI/CO
8. Profit Center
Accounting
ROBJNR
COBJNR
Cost Center
Accounting
Special Purpose Ledger
COBJNR
ROBJNR
________________________________________________________
Example of a Custom
Ledger
Reconcillation
Ledger
ROBJNR
SAP FI/CO
ZZGLO
Object (OBJNR)
ZZGLT
Ledger(RLDNR)
Record Type (RRCTY)
Version (RVERS)
Fiscal Year (GJAHR)
Object (ROBJNR)
Object (SOBJNR)
Currency (RTCUR)
UOM (RUNIT)
Debit/Credit Ind (DRCRX)
Period (RPMAX)
ZZGLO
Record No (GL_SIRID)
COFIT
(Totals records - reconciliation ledger)
Ledger(RLDNR)
Record Type (RRCTY)
Version (RVERS)
Fiscal Year (GJAHR)
Object (ROBJNR)
Object (COBJNR)
Object (SOBJNR)
Currency (RTCUR)
UOM (RUNIT)
Debit/Credit Ind (DRCRX)
Period (RPMAX)
COFIO2
(Transaction-dependent fields for
reconciliation ledger)
Object (OBJNR)
COFIO1
(Object Table for Reconciliation
Ledger COFIT)
Object (OBJNR)
COSP
(CO Object: Cost Totals - External
Postings)
Ledger (LEDNR)
Object (J_OBJNR)
Fiscal Year (GJAHR)
Value Type (WRTTP)
Version (VERSN)
Cost Element (KSTAR)
CO Key (HRKFT)
CO Trans (VRGNG)
Trading Part ID (VBUND)
Trading Part BA (PARGB)
Debit/Credit Ind (BEKNZ)
Currency (TWAER)
Period Block (PERBL)
COEP
(CO object: period-related line items)
Controlling Area (KOKRS)
Document No (BELNR)
Line Item (BUZEI)
COBK
Controlling Area (KOKRS)
Document No (BELNR)
GLPCA
(EC-PCA: Actual Line Items)
Record No (GL_SIRID)
GLPCO
(EC-PCA: Object Table for Account
Assignment Elements)
Object (OBJNR)
GLPCT
(EC-PCA: Totals Table)
Ledger(RLDNR)
Record Type (RRCTY)
Plan Version (RVERS)
Fiscal Year (GJAHR)
Object (ROBJNR)
Object (COBJNR)
Object (SOBJNR)
Currency (RTCUR)
UOM (RUNIT)
Debit/Credit Ind (DRCRX)
Period (RPMAX)
GLPCC
(EC-PCA: Transaction Attributes)
Object (OBJNR)
Controlling
9. Accounts Payable
Vendor Master Data
Company Code DataGeneral DataPurchasing Data
LFM1
(Vendor master record purchasing
organization data)
Vendor No (LIFNR)
Purch Org (EKORG)
LFM2
(Vendor Master Record: Purchasing
Data)
Vendor No (LIFNR)
Purch Org (EKORG)
Sub-range (LTSNR)
Plant (WERKS)
LFA1
(Vendor master (general section))
Vendor No (LIFNR)
LFB1
(Vendor master (company code))
Vendor No (LIFNR)
Company Code (BUKRS)
LFBK
(Vendor master (bank details))
Vendor No (LIFNR)
Bank Cntry (BANKS)
Bank Key (BANKL)
Bank Acc (BANKN)
LFB5
(Vendor master (dunning data))
Vendor No (LIFNR)
Company Code (BUKRS)
Dunning Area (MABER)
SAP FI/CO
10. Accounts Receivable
Customer Master Data
Company Code DataGeneral DataSales Area Data
SAP FI/CO
KNA1
(General Data in Customer Master)
Customer No (KUNNR)
KNB1
(Customer master (company code))
Customer No (KUNNR)
Company Code (BUKRS)
KNB5
(Customer master (dunning data))
Customer No (KUNNR)
Company Code (BUKRS)
Dunning Area (MABER)
KNVP
(Customer Master Partner Functions)
Customer No (KUNNR)
Sales Org (VKORG)
Distribution Ch (VTWEG)
Division (SPART)
Partner Function (PARVW)
Partner Counter (PARZA)
KNVV
(Customer Master Sales Data)
Customer No (KUNNR)
Sales Org (VKORG)
Distribution Ch (VTWEG)
Division (SPART)
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. Master Data
Cost CenterProfit Center
General Ledger
Cost Elemet
SAP FI/CO
CEPC
(Profit center master data table)
Profit Center (PRCTR)
Valid to Date (DATBI)
Controlling Area (KOKRS)
CEPCT
(Texts for Profit Center Master Data)
Language (SPRAS)
Profit Center (PRCTR)
Valid to Date (DATBI)
Controlling Area (KOKRS)
CSKS
(Cost center master)
Controlling Area (KOKRS)
Cost Center (KOSTL)
Valid to Date (DATBI)
CSKA
(Cost elements (data dependent on
chart of accounts))
COA (KTOPL)
Cost Element (KSTAR)
CSKT
(Cost Center Texts)
Language (SPRAS)
Controlling Area (KOKRS)
Cost Center (KOSTL)
Valid to Date (DATBI)
CSKB
(Cost elements (data dependent on
controlling area))
Controlling Area (KOKRS)
COA (KTOPL)
Cost Element (KSTAR)
Valid to Date (DATBI)
CSKU
(Cost Element Texts)
Language (SPRAS)
COA (KTOPL)
Cost Element (KSTAR)
SKB1
(G/L account master (company code))
Company Code (BUKRS)
G/L Account (SAKNR)
SKA1
(G/L accounts master (chart of
accounts))
COA (KTOPL)
G/L Account (SAKNR)
SKAT
(G/L account master record (chart of
accounts: description))
Language (SPRAS)
COA (KTOPL)
G/L Account (SAKNR)
14. Purchasing Requisition
SAP MM - Purchasing
STXH
(STXD SAPscript text file header)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
EBAN
(Purchase Requisition)
Purchasing Req (BANFN)
Item (BNFPO)
EBKN
(Purchase Requisition Account
Assignment)
Purchasing Req (BANFN)
Item (BNFPO)
Preg Account Assignment (ZEBKN)
STXL
(STXD SAPscript text file lines))
(RELID)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(SRTF2)
15. Purchase Orders
SAP MM - Purchasing
S011
(PURCH: Purch. Group Statistics)
Statistics (SSOUR)
Version (VRSIO)
Month (SPMON)
Day (SPTAG)
Week (SPWOC)
Posting Period (SPBUP)
Purchasing Org (EKORG)
Purchasing Group (EKGRP)
Vendor No (LIFNR)
S012
(PURCHIS: Purchasing Statistics)
Statistics (SSOUR)
Version (VRSIO)
Month (SPMON)
Day (SPTAG)
Week (SPWOC)
Posting Period (SPBUP)
Purchasing Org (EKORG)
Purchasing Group (EKGRP)
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
(Purchasing Document Item)
Purchasing Doc (EBELN)
Item (EBELP)
EKKN
(Account Assignment in Purchasing
Document)
Purchasing Doc (EBELN)
Item (EBELP)
Account Assignment (ZEKKN)
EKKO
(Purchasing Document Header)
Purchasing Doc (EBELN)
EORD
(Purchasing Source List)
Material No (MATNR)
Plant (WERKS)
Source List No (ZEORD)
EINA
(Purch Info Record: General Data)
Info Record (INFNR)
EINE
(Purchasing Info Record: Purchasing
Organization Data)
Info Record (INFNR)
Purchasing Org (EKORG)
Info Record Type (ESOKZ)
Plant (WEKS)
16. Goods Receipt
MKPF
(Header: Material Document)
Document No (MBLNR)
Fiscal Year (MJAHR)
SAP MM - Purchasing
MSEG
(Document Segment: Material)
Document No (MBLNR)
Fiscal Year (MJAHR)
Line Item (ZEILE)
EKBE
(History of Purchasing Document)
Purchasing Doc (EBELN)
Item (EBELP)
Account Assign (ZEKKN)
Trans Type (VGABE)
Fiscal Year (MJAHR)
Document No (MBLNR)
Line Item (ZEILE)
MVER
(Material consumption)
Material NO (MATNR)
Plant (WERKS)
Fiscal Year (GJAHR)
Period (PERKZ)
Follow-on Records (ZAHLR)
S011
(PURCHIS: Purchasing Group
Statistics)
Statistics (SSOUR)
Version (VRSIO)
Month (SPMON)
Day (SPTAG)
Week (SPWOC)
Posting Period (SPBUP)
Purchasing Org (EKORG)
Purchasing Group (EKGRP)
Vendor No (LIFNR)
S031
(Statistics: Movements for current
stocks)
Statistics (SSOUR)
Version (VRSIO)
Month (SPMON)
Day (SPTAG)
Week (SPWOC)
Posting Period (SPBUP)
Plant (WERKS)
Material No (MATNR)
Storage Loc (LGORT)
S013
(PURCHIS: Statistics for Vendor
Evaluation)
Statistics (SSOUR)
Version (VRSIO)
Month (SPMON)
Day (SPTAG)
Week (SPWOC)
Posting Period (SPBUP)
Purchasing Org (EKORG)
Purchasing Group (EKGRP)
Vendor No (LIFNR)
Material No (MATNR)
Plant (WERKS)
Info Record Cat (ESOKZ)
Info Record (INFNR)
17. Accounting DataBasic DataPurchasing Data
SAP MM - Master Data
MARC
(Material Master: C Segment)
Material No (MATNR)
Plant (WERKS)
MLAN
(Tax Classification: Material)
Material No (MATNR)
Country (ALAND)
MAKT
(Material Descriptions)
Material No (MATNR)
Language (SPRAS)
MARA
(Material Master: General Data)
Material No (MATNR)
MARM
(Units of Measure)
Material No (MATNR)
UOM (MEINH)
MBEW
(Material Valuation)
Material No (MATNR)
Valuation Area (BWKEY)
Valuation Type (BWTAR)
18. Purchasing Info Record
KONP
(Conditions (Item))
Condition No (KNUMH)
Seq No (KOPOS)
KONH
(Conditions (Header))
Condition No (KNUMH)
EINA
(Purchasing Info Record: General
Data)
Info Record (INFNR)
EINE
(Purchasing Info Record: Purchasing
Organization Data)
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)
SAP MM - Purchasing
21. 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)
PRPS
(WBS (Work Breakdown Structure)
Element Master Data))
Project Number (PSPHI)
WBS Element Number (PSPNR)
WBS Name (POSID)
PRHIS
(Standard WBS, Edges (Hierarchy
pointers))
Project Number (PSPHI)
WBS Element Number (POSNR)
PRTE
(Scheduling Data for Project Item)
Project Number (PSPHI)
WBS Element Number (POSNR)
PRTX
(PS Texts (WBS))
WBS Element Number (PRPSPNR)
Text Identifier (PRTXTKY)
PSTX
(PS Texts (Header))
Text Identifier (PRTXTKY)
PS text description (PSTXTTI)
PSTT
(PS texts (description))
Text Identifier (PRTXTKY)
PS text: Description(PTKTEXT)
SAP PP - Project Planning
22. SAP - Sales and Distribution
Sales and Distribution
Finacial Accounting
Billing
Accounts Receivable
Sales
Material Master
Shipping
Materials Mgmt.
Tables:
KONV
LIKP
LIPS
VBAK
VBAP
VBBE
VBEH
VBEP
VBFA
VBLB
VBLK
VBPA
VBRK
VBRP
VBUK
VBUP
VEKP
VEPO
VEPVG
24. VBAK
(Sales Document :Header)
Sales doc (VBELN)
VBAP
(Sales Document : Item Info)
Sales doc (VBELN)
Item (POSNR)
VBUP
(Item Status)
Sales doc (VBELN)
Item (POSNR)
VBEP
(Sales Document : Schedule Lines)
Sales doc (VBELN)
Item (POSNR)
Schedle Line (ETENR)
VBPA
(Sales Document :Partner)
VBKD
(Sales Document : Business Data)
Sales doc (VBELN)
Item (POSNR)
Partner Function (PARVW)
Sales doc (VBELN)
Item (POSNR)
VBEH
(Schedule Line History)
Sales doc (VBELN)
Item (POSNR)
Schedle Line (ETENR)
SAP SD - Sales Tables
VBUK
(Header Status)
Sales doc (VBELN)
VKDFS
(SD Index:Billing Initiator)
Billing Cat (FKTYP)
Sales Org (VKORG)
Billing Date (FKDAT)
Customer (KUNNR)
Billing Type (FKART)
Country (LLAND)
Sales doc (VBELN)
VAPMA
(SD Index:Order Items by Material)
Material No (MATNR)
Sales Org (VKORG)
Trans Group (TRVOG)
Document Date (AUDAT)
Distribution Channel (VTWEG)
Division (SPART)
Document Type (AUART)
Sold-to-Party (KUNNR)
Sales Office (VKBUR)
Sales Group (VKGRP)
Customer PO No (BSTNK)
User Name (ERNAM)
Sales Ord (VBELN)
Item (POSNR)
VAKPA
(SD Index:Order by Partner Function)
Partner No (KUNDE)
Partner Function (PARVW)
Sales Org (VKORG)
Trans Group (TRVOG)
Document Date (AUDAT)
Sales Office (VKBUR)
Sales Group (VKGRP)
Distribution Channel (VTWEG)
Division (SPART)
Document Type (AUART)
Customer PO No (BSTNK)
Sold-to-Party (KUNNR)
User Name (ERNAM)
Sales Ord (VBELN)
STXH
(STXD SAPscript text file header)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
STXL
(STXD SAPscript text file lines)
(RELID)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(SRTF2)
To Shipping throughLIPS
LIPS-VGBEL = VBAP-VBELN
and
LIPS-VGPOS = VBAP-POSNR
VBFA
(Sales Document Flow)
Preceding Sales Doc (VBELV)
Preceding Item (POSNV)
Subsequent Sales doc (VBELN)
Subsequent Item (POSNN)
Document Cat (VBTYP_N)
25. LIPS-VBELN =
LIKP-VBELN
VEPO-VBELN =
LIPS-VBELN
and
VEPO-POSNR =
LIPS-POSNR
VEPO-VENUM =
VEKP-VENUM
VBLK-VBELN =
LIKP-VBELN
SAP SD - Shipping Tables
VBLK
(SD:Delivery Note Header)
Delivery Document Number (VBELN)
LIKP
(Sales Doc:Delivery Header)
Delivery Document Number (VBELN)
LIPS
(Sales Doc:Delivery Items)
Delivery Document Number (VBELN)
Item (POSNR)
VEKP
(SD Doc:Shipping Unit Header)
Shipping Unit Number(VENUM)
VEPO
(SD Doc:Shipping Item content)
Delivery Document Number (VBELN)
Delivery Item (POSNR)
Shipping Unit Number (VENUM)
Shipping Unit Item (VEPOS)
VBUK
(Header Status)
Delivery doc (VBELN)
From Sales throughVBAP
LIPS-VGBEL = VBAP-VBELN
and
LIPS-VGPOS = VBAP-POSNR
To Biling throughVBRP
VBRP-VGBEL = LIPS-VBELN
and
VBRP-VGPOS = LIPS-POSNR
VBUP
(Item Status)
Deliverydoc (VBELN)
Item (POSNR)
VTTK-TKNUM =
VTTP-TKNUM
VTTP-VBELN =
LIKP-VBELN
VTTP
(Shipment Item)
Delivery Doc Number(VBELN)
Shipment Number (TKNUM)
Shipment Item (TPNUM)
VTTK
(Shipment Header)
Shipment Number (TKNUM)
VTFA
(Shipment Doc. Flow)
Shipment Number (TKNUM)
Preceeding Doc. (VBELV)
VBFA
(Sales Document Flow)
Preceding Sales Doc (VBELV)
Preceding Item (POSNV)
Subsequent Sales doc (VBELN)
Subsequent Item (POSNN)
Document Cat (VBTYP_N)
26. VRKPA
(Sales Index: Bills by Partner
Functions)
Partner No (KUNDE)
Partner Function (PARVW)
Sales Org (VKORG)
Billing Date (FKDAT)
Distribution Channel (VTWEG)
Billing Type (FKART)
Payer (KUNNR)
Sold-to-Party (KUNNR)
SD Doc Cat (VBTYP)
User Name (ERNAM)
Billing Doc (VBELN)
VRPMA
(SD Index: Billing Items per Material)
Material No (MATNR)
Sales Org (VKORG)
Billing Date (FKDAT)
Distribution Channel (VTWEG)
Billing Type (FKART)
Payer (KUNNR)
Sold-to-Party (KUNNR)
SD Doc Cat (VBTYP)
User Name (ERNAM)
Billing Doc (VBELN)
Item (POSNR)
VKDFS
(SD Index: Billing Initiator)
Billing Cat (FKTYP)
Sales Org (VKORG)
Billing Date (FKDAT)
Customer (KUNNR)
Billing Type (FKART)
Country (LLAND)
Sales doc (VBELN)
VBRK
(Billing: Header Data)
Billing doc (VBELN)
VBUK
(Header Status)
Sales doc (VBELN)
VBRP
(Billing: Item Data)
Billing doc (VBELN)
Item (POSNR)
VBSK
(Collective Processing for a Sales
Document Header)
Grouped Delivery (SAMMG)
NAST
(Billing: Header Data)
Application (KAPPL)
Object (OBJKY)
Output Type (KSCHL)
Language (SPRAS)
Mess Partner (PARNR)
Partner Func (PARVW)
Date (ERDAT)
Time (ERUHR)
VBUP
(Sales Document: Item Status)
Sales doc (VBELN)
Item (POSNR)
VBFA
(Sales Document Flow)
Preceding Sales Doc (VBELV)
Preceding Item (POSNV)
Subsequent Sales doc (VBELN)
Subsequent Item (POSNN)
Document Cat (VBTYP_N)
Grouped Delivery (SAMMG)
Sales doc (VBELN)
VBSS
(Collective Processing: Sales
Documents)
SAP SD - Billing Tables
From Shipping throughLIPS
VBRP-VGBEL = LIPS-VBELN
and
VBRP-VGPOS = LIPS-POSNR
27. Customer Master Data
Company Code DataGeneral DataSales Area Data
SAP SD - Links to FI Tables
Customer No (KUNNR)
Sales Org (VKORG)
Distribution Ch (VTWEG)
Division (SPART)
Partner Function (PARVW)
Partner Counter (PARZA)
Customer No (KUNNR)
Customer No (KUNNR)
Sales Org (VKORG)
Distribution Ch (VTWEG)
Division (SPART)
KNVP
(Customer Master Partner Functions)
KNA1
(General Data in Customer Master)
KNVV
(Customer Master Sales Data)
KNVD
(Customer master record sales
request form)
Customer No (KUNNR)
Sales Org (VKORG)
Distribution Ch (VTWEG)
Division (SPART)
Output Type (
KNB1
(Customer master (company code))
KNB5
(Customer master (dunning data))
Customer No (KUNNR)
Companu Code (BUKRS)
Dunning Area (MABER)
Customer No (KUNNR)
Company Code (BUKRS)
28. Material Master Data
Sales Text DataBasic DataSales Data
MARC
(Material Master: C Segment)
Material No (MATNR)
Plant (WERKS)
Material No (MATNR)
Sales Org (VKORG)
Distribution Chan (VTWEG)
Product Hierarchy (PRODH)
Material No (MATNR)
Country (ALAND)
MVKE
(Material Master: Sales Data)
MLAN
(Tax Classification: Material)
Material No (MATNR)
Language (SPRAS)
MAKT
(Material Descriptions)
Material No (MATNR)
MARA
(Material Master: General Data)
Material No (MATNR)
UOM (MEINH)
MARM
(Units of Measure)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(RELID)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(SRTF2)
STXH
(STXD SAPscript text file header)
STXL
(STXD SAPscript text file lines)
SAP SD - Links to MM Tables
Product Hierarchy (PRODH)
*use to ge text for hiearchy levels
T179
(Materials: Product Hierarchies)
29. SD
Paul Evans (Whittman-Hart, inc.)
Krishna Prasad (Whittman-Hart, inc.)
Russ Smith (Benteler)
Michael Rhodes (MedPartners, inc.)
FI/CO
Michael Rhodes (MedPartners, inc.)
MM
Jim Lewis (Whittman-Hart, inc.)
Michael Rhodes (MedPartners, inc.)
Master Data
Jim Lewis (Whittman-Hart, inc.)
Contributions by
PP
HR