In my last blog, I explained some fundamentals of outline agreements (value and quantity contracts, and also scheduling agreements) in SAP®. As mentioned, I will now examine outline agreement release orders. I will first briefly explain how to look up these in SAP®, before moving on to the data situation. In detailed terms, this involves logging release orders at table level.
In this blog I would like to give you an overview of outline agreements in SAP® in the purchasing module. Extra to sketching the concept itself, I will give you insight into its mapping from a viewpoint of data analytics, in other words SAP® tables and field level.
In this blog post I will discuss “free goods”. They play an important role both in projects which we implement for our customers and also in our dab:AnalyticSuite, and form the subject of many queries. Important factors include profitability in terms of calculating profit in a customer’s business, compliance (bribery through payments in kind, formation of black accounts, undue advantage) or simply monitoring possible IT interface errors which can result in proper deliveries inadvertently not being invoiced.
In this blog post, I will discuss ways in which you can use data from SAP® systems to obtain information about your data. Although the article is fairly technical because it deals with meta data, I will use brief examples to illustrate specific issues. To begin with, I will describe the starting point, before drawing on selected examples to explain how the Data Dictionary can be used, and then ending with a brief conclusion.
As the weather gets colder, you often find savory hotpots dished up, with all kinds of ingredients. But in data analytics it can be better not to put too many ingredients in a single pot for analysis. Or to know exactly which ingredients are right to enjoy a clear structure — or even to deconstruct, as you might say.
This article will demonstrate the difference between Purchasing Document Category (EKKO_BSTYP) and Purchasing Document Type (EKKO_BSART) which can be found in table EKKO. The table EKKO includes the header data of all purchasing documents. Which documents are concretely concerned, will be described in the following chapters.
This article discusses the account balance display. There are several postings per vendor respectively customer in one year. The tables LFC1 and KNC1 offer a consolidated view to vendor postings or customer postings within a period. This article describes the mentioned tables. Furthermore, the corresponding transactions in SAP® are described.
For many a production process it is not enough to conduct an analysis just at material level. Instead you have to look at single batches of a material. This blog post points to SAP® transactions and associated tables that may be needed for the job.
Runners are likely to understand something by this. In sport PACE is the time a runner needs for a certain distance, e.g. for a kilometer. If you want to run a marathon in less than 4 hours for instance, you should aim for a PACE of 5:40 minutes per kilometer.
It is pretty warm outside, so let’s keep this article short and as to-the-point as possible. I want to have a closer look at the AR (Accounts Receivables) documents in SAP® FI, to be more exact at incoming payments.
In this article I will explain a fact which might sometimes be a little confusing when looking at SAP® tables using the SAP® GUI transaction SE16 compared to downloading the data using a download tool. I will explain how SAP® displays data making it look like it was in one table, but in fact the data is separated in a table containing settings and technical information (a “Customizing Table”) and a table containing the descriptions and long texts in different languages (a “Text table”). I will explain where SAP® mixes those two, but also how you can find out about where the data really is located in the database tables.