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.
Procurement Workflow in terms of SAP Tables ChangesANURAG SINGH
1. The document outlines the key SAP tables involved in the procure-to-pay process, including tables for purchase requisitions (EBAN, EBKN), purchase orders (EKKO, EKPO, EKKN), goods receipts (COOI), and invoices (EKBE, BKPF, BSEG, RBKP, RSEG).
2. It describes how transactions like creating a requisition, purchase order, and invoice populate and link these tables. For example, a requisition creates records in EBAN and EBKN, a purchase order creates records in EKKO, EKPO, EKKN and links to the requisition records.
3. It also
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.
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 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.
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
This document lists important tables in SAP related to financial accounting, general ledger accounting, accounts receivable, bank accounting, asset accounting, cost center accounting, profit center accounting, and more. It provides the table name, description, and important fields for each table. The tables contain key transactional and master data used throughout the SAP modules.
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.
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.
Procurement Workflow in terms of SAP Tables ChangesANURAG SINGH
1. The document outlines the key SAP tables involved in the procure-to-pay process, including tables for purchase requisitions (EBAN, EBKN), purchase orders (EKKO, EKPO, EKKN), goods receipts (COOI), and invoices (EKBE, BKPF, BSEG, RBKP, RSEG).
2. It describes how transactions like creating a requisition, purchase order, and invoice populate and link these tables. For example, a requisition creates records in EBAN and EBKN, a purchase order creates records in EKKO, EKPO, EKKN and links to the requisition records.
3. It also
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.
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 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.
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
This document lists important tables in SAP related to financial accounting, general ledger accounting, accounts receivable, bank accounting, asset accounting, cost center accounting, profit center accounting, and more. It provides the table name, description, and important fields for each table. The tables contain key transactional and master data used throughout the SAP modules.
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.
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 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, EKKO, and EKPO. Graphical representations show relationships like one-to-one, one-to-many, and transparent versus cluster tables. The document is intended to help users understand how SAP database tables are linked.
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.
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. Table fields are also listed to show how different tables are linked together through common fields like company code, document number, and material number. The document is intended to help users understand how SAP tables relate to each other for different business processes and modules.
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, EKKO, and EKPO. Graphical representations show relationships like one-to-one, one-to-many, and transparent versus cluster tables. The document is intended to help users understand how SAP database tables are linked.
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 users understand how SAP database tables relate to each other.
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, EKKO, and EKPO. Graphical representations show relationships like one-to-one, one-to-many, and transparent versus cluster tables. The document is intended to help users understand how SAP database tables are linked.
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 include document number, item, material, and company code to link tables together.
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.
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 can be used to understand how data in different SAP modules and tables are related.
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.
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. Table fields are also listed to show how different tables are linked together through common fields like company code, document number, and material number. The document is intended to help users understand how SAP tables relate to each other for different business processes and modules.
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.
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.
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 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 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.
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 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.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
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, EKKO, and EKPO. Graphical representations show relationships like one-to-one, one-to-many, and transparent versus cluster tables. The document is intended to help users understand how SAP database tables are linked.
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.
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. Table fields are also listed to show how different tables are linked together through common fields like company code, document number, and material number. The document is intended to help users understand how SAP tables relate to each other for different business processes and modules.
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, EKKO, and EKPO. Graphical representations show relationships like one-to-one, one-to-many, and transparent versus cluster tables. The document is intended to help users understand how SAP database tables are linked.
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 users understand how SAP database tables relate to each other.
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, EKKO, and EKPO. Graphical representations show relationships like one-to-one, one-to-many, and transparent versus cluster tables. The document is intended to help users understand how SAP database tables are linked.
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 include document number, item, material, and company code to link tables together.
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.
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 can be used to understand how data in different SAP modules and tables are related.
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.
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. Table fields are also listed to show how different tables are linked together through common fields like company code, document number, and material number. The document is intended to help users understand how SAP tables relate to each other for different business processes and modules.
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.
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.
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 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 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.
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 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.
Freshworks Rethinks NoSQL for Rapid Scaling & Cost-EfficiencyScyllaDB
Freshworks creates AI-boosted business software that helps employees work more efficiently and effectively. Managing data across multiple RDBMS and NoSQL databases was already a challenge at their current scale. To prepare for 10X growth, they knew it was time to rethink their database strategy. Learn how they architected a solution that would simplify scaling while keeping costs under control.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
Generating privacy-protected synthetic data using Secludy and MilvusZilliz
During this demo, the founders of Secludy will demonstrate how their system utilizes Milvus to store and manipulate embeddings for generating privacy-protected synthetic data. Their approach not only maintains the confidentiality of the original data but also enhances the utility and scalability of LLMs under privacy constraints. Attendees, including machine learning engineers, data scientists, and data managers, will witness first-hand how Secludy's integration with Milvus empowers organizations to harness the power of LLMs securely and efficiently.
The Microsoft 365 Migration Tutorial For Beginner.pptxoperationspcvita
This presentation will help you understand the power of Microsoft 365. However, we have mentioned every productivity app included in Office 365. Additionally, we have suggested the migration situation related to Office 365 and how we can help you.
You can also read: https://www.systoolsgroup.com/updates/office-365-tenant-to-tenant-migration-step-by-step-complete-guide/
Taking AI to the Next Level in Manufacturing.pdfssuserfac0301
Read Taking AI to the Next Level in Manufacturing to gain insights on AI adoption in the manufacturing industry, such as:
1. How quickly AI is being implemented in manufacturing.
2. Which barriers stand in the way of AI adoption.
3. How data quality and governance form the backbone of AI.
4. Organizational processes and structures that may inhibit effective AI adoption.
6. Ideas and approaches to help build your organization's AI strategy.
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
Programming Foundation Models with DSPy - Meetup SlidesZilliz
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Essentials of Automations: Exploring Attributes & Automation ParametersSafe Software
Building automations in FME Flow can save time, money, and help businesses scale by eliminating data silos and providing data to stakeholders in real-time. One essential component to orchestrating complex automations is the use of attributes & automation parameters (both formerly known as “keys”). In fact, it’s unlikely you’ll ever build an Automation without using these components, but what exactly are they?
Attributes & automation parameters enable the automation author to pass data values from one automation component to the next. During this webinar, our FME Flow Specialists will cover leveraging the three types of these output attributes & parameters in FME Flow: Event, Custom, and Automation. As a bonus, they’ll also be making use of the Split-Merge Block functionality.
You’ll leave this webinar with a better understanding of how to maximize the potential of automations by making use of attributes & automation parameters, with the ultimate goal of setting your enterprise integration workflows up on autopilot.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Saptables[1]
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
(Table Description)
SAP Table Information
SAP Field Name (Field Description)
SAP Field Name (Field Description)
Useful Fields
Link Key
One-to-One
One
One
One-to-Many
One
SAP Table Name
(Table Description)
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
Ledger
Financial
Accounting
Special Purpose
Ledger
Custom
Ledger
Accounts
Receivable
Controlling
Profit Center
Accounting
Tables:
BSAD
BSAS
BSEG
BSES
BSIK
BSIS
Cost Center
Accounting
6. PAYR
(Payment transfer medium file)
Paying Company (ZBUKR)
House Bank (HBKID)
Account (HKTID)
Payment Method (ZLSCH)
Check No (CHECKT)
BVOR
(Intercompany posting procedures)
Intercompany No (BVORG)
Company Code (BUKRS)
Fiscal Year (GJAHR)
Document No (BELNR)
VBLNR
BKPF
(Accounting document header)
Company Code (BUKRS)
Document No (BELNR)
Fiscal Year (GJAHR)
All FI
documents
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)
BSIP
(Index for vendor validation of double
documents)
Company Code (BUKRS)
Vendor (LIFNR)
Currency (WAERS)
Document Date (BLDAT)
Duplicate Invoices Reference Doc (WRBTR)
Amount (WRBTR)
Document No (BELNR)
Fiscal Year (GJAHR)
Line Items (BUZEI)
Closed items
Open Items
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)
Open Items
BSEG
(Accounting document segment)
Company Code (BUKRS)
Document No (BELNR)
Fiscal Year (GJAHR)
Line Item (BUZEI)
Open Items
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)
Closed items
Closed items
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)
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)
KNC1
(Customer master (trans figures))
Customer (KUNNR)
Company Code (BUKRS)
Fiscal Year (GJAHR)
LFC1
(Vendor master (transaction figures))
Vendor (LIFNR)
Company Code (BUKRS)
Fiscal Year (GJAHR)
7. SAP FI/CO
Financial Accounting
RFBLG
(Cluster for accounting
document)
BKPF
(Accounting document header)
Company Code
Document No
Fiscal Year
BSEC
BSED
BSEG
BSES
BSET
Physical
BSEG
(Accounting document
segment)
A
BKPF
(Accounting document header)
Company Code
Document No
Fiscal Year
F
ll
I
do
c
um
en
ts
One time accounts
Ta
x
do
cu
m
en
Company Code
Document No
Fiscal Year
Line Item
BSEC
(One-time account data
document segment)
Company Code
Document No
Fiscal Year
Line Item
ts
BSET
(Tax data document
segment)
Company Code
Document No
Fiscal Year
Line Item
Logical
8. SAP FI/CO
Special Purpose Ledger
Controlling
Profit Center
Accounting
GLPCA
(EC-PCA: Actual Line Items)
Record No (GL_SIRID)
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)
Example of a Custom
Ledger
ZZGLO
ROBJNR
COBJNR
Object (OBJNR)
ROBJNR
GLPCO
(EC-PCA: Object Table for Account
Assignment Elements)
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)
GLPCC
(EC-PCA: Transaction Attributes)
Object (OBJNR)
________________________________________________________
Cost Center
Accounting
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)
Reconcillation
Ledger
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)
CO
BJ
NR
COFIO2
(Transaction-dependent fields for
reconciliation ledger)
Object (OBJNR)
ROBJNR
COFIO1
(Object Table for Reconciliation
Ledger COFIT)
Object (OBJNR)
9. SAP FI/CO
Accounts Payable
Vendor Master Data
Purchasing 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)
General Data
Company Code Data
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)
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)
Distribution Ch (VTWEG)
Division (SPART)
Partner Function (PARVW)
Partner Counter (PARZA)
KNA1
(General Data in Customer Master)
KNB1
(Customer master (company code))
Customer No (KUNNR)
Customer No (KUNNR)
Company Code (BUKRS)
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)
KNB5
(Customer master (dunning data))
Customer No (KUNNR)
Company Code (BUKRS)
Dunning Area (MABER)
11. SAP FI/CO
Master Data
Cost Elemet
Profit Center
Cost Center
CEPC
(Profit center master data table)
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)
CSKB
(Cost elements (data dependent on
controlling area))
Controlling Area (KOKRS)
COA (KTOPL)
Cost Element (KSTAR)
Valid to Date (DATBI)
CEPCT
(Texts for Profit Center Master Data)
Language (SPRAS)
Profit Center (PRCTR)
Valid to Date (DATBI)
Controlling Area (KOKRS)
CSKT
(Cost Center Texts)
Language (SPRAS)
Controlling Area (KOKRS)
Cost Center (KOSTL)
Valid to Date (DATBI)
CSKU
(Cost Element Texts)
Language (SPRAS)
COA (KTOPL)
Cost Element (KSTAR)
General Ledger
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)
13. KNMT
(Customer-Material
Info Record Data
Table)
makt-matnr = knmt-matnr
and
makt-spras = sy-langu
MAKT
(Material
Description)
EKKO
(Purchasing Doc
Header)
MDKP
(MRP Header)
MDKP-DTNUM =
MDTB-DTNUM
EKPO-EBELN =
EKKO-EBELN
EKPO
(Purchasing Doc
Item)
MDTB
(MRP Detail)
MM
Table Mapping
14. SAP MM - Purchasing
Purchasing Requisition
STXH
(STXD SAPscript text file header)
EBAN
(Purchase Requisition)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
Purchasing Req (BANFN)
Item (BNFPO)
STXL
(STXD SAPscript text file lines))
(RELID)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(SRTF2)
EBKN
(Purchase Requisition Account
Assignment)
Purchasing Req (BANFN)
Item (BNFPO)
Preg Account Assignment (ZEBKN)
15. SAP MM - Purchasing
Purchase Orders
S011
(PURCH: Purch. Group Statistics)
S012
(PURCHIS: Purchasing Statistics)
Statistics (SSOUR)
Version (VRSIO)
Month (SPMON)
Day (SPTAG)
Week (SPWOC)
Posting Period (SPBUP)
Purchasing Org (EKORG)
Purchasing Group (EKGRP)
Vendor No (LIFNR)
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)
EINE
(Purchasing Info Record: Purchasing
Organization Data)
Info Record (INFNR)
Purchasing Org (EKORG)
Info Record Type (ESOKZ)
Plant (WEKS)
EKET
(Delivery Schedules)
Purchasing Doc (EBELN)
Item (EBELP)
Delivery Schedule (ETENR)
EKPO
(Purchasing Document Item)
Purchasing Doc (EBELN)
Item (EBELP)
EINA
(Purch Info Record: General Data)
Info Record (INFNR)
EKKO
(Purchasing Document Header)
Purchasing Doc (EBELN)
EORD
(Purchasing Source List)
Material No (MATNR)
Plant (WERKS)
Source List No (ZEORD)
EKKN
(Account Assignment in Purchasing
Document)
Purchasing Doc (EBELN)
Item (EBELP)
Account Assignment (ZEKKN)
16. SAP MM - Purchasing
Goods Receipt
MKPF
(Header: Material Document)
MSEG
(Document Segment: Material)
Document No (MBLNR)
Fiscal Year (MJAHR)
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)
Document No (MBLNR)
Fiscal Year (MJAHR)
Line Item (ZEILE)
EKBE
(History of Purchasing Document)
MVER
(Material consumption)
Purchasing Doc (EBELN)
Item (EBELP)
Account Assign (ZEKKN)
Trans Type (VGABE)
Fiscal Year (MJAHR)
Document No (MBLNR)
Line Item (ZEILE)
Material NO (MATNR)
Plant (WERKS)
Fiscal Year (GJAHR)
Period (PERKZ)
Follow-on Records (ZAHLR)
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. SAP MM - Master Data
Purchasing Data
Basic Data
MARC
(Material Master: C Segment)
MAKT
(Material Descriptions)
Material No (MATNR)
Plant (WERKS)
Accounting Data
Material No (MATNR)
Language (SPRAS)
MARA
(Material Master: General Data)
Material No (MATNR)
MLAN
(Tax Classification: Material)
Material No (MATNR)
Country (ALAND)
MBEW
(Material Valuation)
Material No (MATNR)
Valuation Area (BWKEY)
Valuation Type (BWTAR)
MARM
(Units of Measure)
Material No (MATNR)
UOM (MEINH)
18. SAP MM - Purchasing
Purchasing Info Record
KONP
(Conditions (Item))
KONH
(Conditions (Header))
Condition No (KNUMH)
Seq No (KOPOS)
Condition No (KNUMH)
EINA
(Purchasing Info Record: General
Data)
EINE
(Purchasing Info Record: Purchasing
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
(WBS (Work Breakdown Structure)
Element Master Data))
Project Number (PSPHI)
WBS Element Number (POSNR)
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
Shipping
Accounts Receivable
Sales and Distribution
Materials Mgmt.
Billing
Tables:
KONV
LIKP
LIPS
VBAK
VBAP
VBBE
VBEH
VBEP
VBFA
VBLB
VBLK
VBPA
VBRK
VBRP
VBUK
VBUP
VEKP
VEPO
VEPVG
Material Master
24. SAP SD - Sales Tables
VKDFS
(SD Index:Billing Initiator)
Billing Cat (FKTYP)
Sales Org (VKORG)
Billing Date (FKDAT)
Customer (KUNNR)
Billing Type (FKART)
Country (LLAND)
Sales doc (VBELN)
STXL
(STXD SAPscript text file lines)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
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)
VBUK
(Header Status)
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)
(RELID)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(SRTF2)
STXH
(STXD SAPscript text file header)
VBFA
(Sales Document Flow)
VBAK
(Sales Document :Header)
Sales doc (VBELN)
VBAP
(Sales Document : Item Info)
Preceding Sales Doc (VBELV)
Preceding Item (POSNV)
Subsequent Sales doc (VBELN)
Subsequent Item (POSNN)
Document Cat (VBTYP_N)
VBUP
(Item Status)
Sales doc (VBELN)
Item (POSNR)
To Shipping through
LIPS
LIPS-VGBEL = VBAP-VBELN
and
LIPS-VGPOS = VBAP-POSNR
Sales doc (VBELN)
Item (POSNR)
VBKD
(Sales Document : Business Data)
VBEP
(Sales Document : Schedule Lines)
Sales doc (VBELN)
Item (POSNR)
Sales doc (VBELN)
Item (POSNR)
Schedle Line (ETENR)
VBEH
(Schedule Line History)
Sales doc (VBELN)
Item (POSNR)
Schedle Line (ETENR)
VBPA
(Sales Document :Partner)
Sales doc (VBELN)
Item (POSNR)
Partner Function (PARVW)
25. SAP SD - Shipping Tables
VTTP
(Shipment Item)
Delivery Doc Number(VBELN)
Shipment Number (TKNUM)
Shipment Item (TPNUM)
VBLK
(SD:Delivery Note Header)
Delivery Document Number (VBELN)
VTTP-VBELN =
LIKP-VBELN
VTTK-TKNUM =
VTTP-TKNUM
VBLK-VBELN =
LIKP-VBELN
VTTK
(Shipment Header)
Shipment Number (TKNUM)
VEPO
(SD Doc:Shipping Item content)
Delivery Document Number (VBELN)
Delivery Item (POSNR)
Shipping Unit Number (VENUM)
Shipping Unit Item (VEPOS)
LIKP
(Sales Doc:Delivery Header)
Delivery Document Number (VBELN)
VTFA
(Shipment Doc. Flow)
Shipment Number (TKNUM)
Preceeding Doc. (VBELV)
VEPO-VENUM =
VEKP-VENUM
VBUK
(Header Status)
Delivery doc (VBELN)
VBFA
(Sales Document Flow)
LIPS-VBELN =
LIKP-VBELN
Preceding Sales Doc (VBELV)
Preceding Item (POSNV)
Subsequent Sales doc (VBELN)
Subsequent Item (POSNN)
Document Cat (VBTYP_N)
VEPO-VBELN =
LIPS-VBELN
and
VEPO-POSNR =
LIPS-POSNR
VEKP
(SD Doc:Shipping Unit Header)
Shipping Unit Number(VENUM)
VBUP
(Item Status)
Deliverydoc (VBELN)
Item (POSNR)
From Sales throughVBAP
LIPS-VGBEL = VBAP-VBELN
and
LIPS-VGPOS = VBAP-POSNR
LIPS
(Sales Doc:Delivery Items)
Delivery Document Number (VBELN)
Item (POSNR)
To Biling through VBRP
VBRP-VGBEL = LIPS-VBELN
and
VBRP-VGPOS = LIPS-POSNR
26. SAP SD - Billing Tables
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)
VKDFS
(SD Index: Billing Initiator)
Billing Cat (FKTYP)
Sales Org (VKORG)
Billing Date (FKDAT)
Customer (KUNNR)
Billing Type (FKART)
Country (LLAND)
Sales doc (VBELN)
VBSK
(Collective Processing for a Sales
Document Header)
VBSS
(Collective Processing: Sales
Documents)
Grouped Delivery (SAMMG)
Grouped Delivery (SAMMG)
Sales doc (VBELN)
NAST
(Billing: Header Data)
Application (KAPPL)
Object (OBJKY)
Output Type (KSCHL)
Language (SPRAS)
Mess Partner (PARNR)
Partner Func (PARVW)
Date (ERDAT)
Time (ERUHR)
VBRK
(Billing: Header Data)
Billing doc (VBELN)
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)
VBUK
(Header Status)
Sales doc (VBELN)
VBRP
(Billing: Item Data)
Billing doc (VBELN)
Item (POSNR)
VBFA
(Sales Document Flow)
From Shipping through
LIPS
VBRP-VGBEL = LIPS-VBELN
and
VBRP-VGPOS = LIPS-POSNR
VBUP
(Sales Document: Item Status)
Sales doc (VBELN)
Item (POSNR)
Preceding Sales Doc (VBELV)
Preceding Item (POSNV)
Subsequent Sales doc (VBELN)
Subsequent Item (POSNN)
Document Cat (VBTYP_N)
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)
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 (
KNA1
(General Data in Customer Master)
KNB1
(Customer master (company code))
Customer No (KUNNR)
Customer No (KUNNR)
Company Code (BUKRS)
KNB5
(Customer master (dunning data))
Customer No (KUNNR)
Companu Code (BUKRS)
Dunning Area (MABER)
28. SAP SD - Links to MM Tables
Material Master Data
Sales Data
MARC
(Material Master: C Segment)
Material No (MATNR)
Plant (WERKS)
Basic Data
MAKT
(Material Descriptions)
Material No (MATNR)
Language (SPRAS)
STXH
(STXD SAPscript text file header)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
MVKE
(Material Master: Sales Data)
Material No (MATNR)
Sales Org (VKORG)
Distribution Chan (VTWEG)
Product Hierarchy (PRODH)
Sales Text Data
MARA
(Material Master: General Data)
Material No (MATNR)
T179
(Materials: Product Hierarchies)
Product Hierarchy (PRODH)
STXL
(STXD SAPscript text file lines)
*use to ge text for hiearchy levels
MARM
(Units of Measure)
MLAN
(Tax Classification: Material)
Material No (MATNR)
Country (ALAND)
Material No (MATNR)
UOM (MEINH)
(RELID)
Texts (TDOBJECT)
Text Name (TDNAME)
Text Id (TDID)
Language (TDSPRAS)
(SRTF2)
29. Contributions by
Master Data
Jim Lewis (Whittman-Hart, inc.)
MM
Jim Lewis (Whittman-Hart, inc.)
Michael Rhodes (MedPartners, inc.)
FI/CO
HR
Michael Rhodes (MedPartners, inc.)
PP
SD
Paul Evans (Whittman-Hart, inc.)
Krishna Prasad (Whittman-Hart, inc.)
Russ Smith (Benteler)
Michael Rhodes (MedPartners, inc.)