Some basic SAP Master Data tables in ECC

Object	Table Name	Description
Material Master	MARA	Basic data
	MAKT	Material description
	MVKE	Sales area
	MARC	Plant data
	MARD	Storage location
	MARM	All unit of measure data
	MBEW	Accounting
	MLAN	Tax
	MAPL	Assignment of Task Lists to Materials
	MKPF	Header: Material Document
	MSEG	Document Segment: Material
	MGEF	Hazardous Materials
BOM	MAST	Material to BOM Link
	STKO	BOM header data
	STPO	BOM item
	STAS	BOMs - Item Selection
Classes	KLAH	Class Header Data
	KLAT
	STXL	Data Lead
	KSML
	SWOR
Characteristics	CABN	Classification
	CABNT
	CAWN
	CAWNT
	AUSP	Characteristic Values
	KSSK	SAP Allocation Table: Object to Class Table and data
	MCHA	Batches
	MCH1	Batches (if Batch Management Cross-Plant)
PIR	EINA	Header Data
	EINE	Item data
Source list	EORD	Source list data
CMIR	KNMT	Customer Material Info record data
Ship Chain (Material Determination)	KONDD	Material Substitution - Data Division
	KONDDP	Conditions: Additional Materials for Material Determination
Inventory Movement	IKPF	Header: Physical Inventory Document
	ISEG	Physical Inventory Document Items
Production Versions	MKAL	Production Versions of Material
Purchase Requisition	EBAN	Purchase Requisition
Purchase Order	EKKO	Purchasing Document Header
	EKPO	Purchasing Document Item
	EKBE	History per Purchasing Document
Sales Order	VBAK	Sales Document: Header Data
	VBAP	Sales Document: Item Data
	LIKP	SD Document: Delivery Header Data
	LIPS	SD document: Delivery: Item data
	VBBE	Sales Requirements: Individual Records
	VBKD	Sales Document: Business Data
Vendor Master	LFA1	General data
	LFB1	Company Code data
	LFM1	Purchase org  data
	ADRC	Address Data
	ADR2	Vendor Telephone Numbers
	ADR4	Vendor Fax Numbers
	ADR6	Vendor Email-Addresses
	LFBK	Bank data
	LFB5	Dunning data
	LFAS	Vendor master (VAT registration numbers general section)
	LFBW	Vendor master record (withholding tax types) X
	WYT3	Partner Functions
	BKPF	Accounting Document Header
	BSEG	Accounting Document Segment
Customer Master	KNA1	General data
	KNB1	Company Code data
	KNVV	Sales area  data
	KNVP	Partner function data
	KNBK	Bank data
	KNVH	Hiearchy data
	KNVI	Tax data
	KNKK	Dunning data
	KNKA	Customer master credit management: Central data
	KNVK	Customer Master Contact Partner
	ADRC	Customer & Contact Person - Address Data
	ADR2	Customer & Contact Person - Telephone Numbers
	ADR4	Customer & Contact Person - Fax Numbers
	ADR6	Customer & Contact Person - Email-Addresses
	KNB5	Customer master (dunning data)
	BSID	Accounting: Secondary Index for Customers
	KNAS	Customer master (VAT registration numbers general section)
	VBRK	Billing Document: Header Data
Cost Centers	CSKS	Cost Center Master Data
	CSKT	cost center Texts
	CSSK	cost center /cost element
	CSSL	cost center/Activity Type
Cost Center Group / Hierarchy	CSKS
Profit Centers	CEPC	Profit Center Master Data Table
	CEPCT
	T005
	T002
	CEPC_BUKRS
Profit Center Group / Hierarchy	CEPC
G/L Account / Chart of Accounts	SKA1	G/L Account Master (Chart of Accounts)
	SKB1	G/L account master (company code)
Customer Hierarchy	KNVH	Customer Hierarchies
Asset Master	ANLA	Asset Master Record Segment
	ANLB	Asset Depreciation terms
	ANKA	Asset Classes
	ANKB	Asset Classes with dep area.
	ANLZ	Time-Dependent Asset Allocations
Asset Values	ANLC	Asset Value fields
	ANEP	Asset Line Items
Cost Elements	CSKA	Cost Elements (Data Dependent on Chart of Accounts)
	CSKB	Cost Elements (Data Dependent on Controlling Area)
	CSKU	cost Element Texts
Pricing conditions	KONH	Conditions (Header)
	KONP	Conditions (Item)
	A***	Pricing tables
WorkCenter	CRHD	Work Center Header
	CRCA	Work Center Capacity Allocation
	CRCO	Assignment of Work Center to Cost Center
Routings / Task List	PLKO	Task list - header
	PLPO	Task list - operation/activity
	PLAS	Task list - selection of operations/activities
Production Order	AUFK	Order master data
	AFPO	Order Item
	AFKO	Order Header Data PP Orders
Planned Order	PLAF	Planned Order
Cross Application	NAST	Message Status
Activity Price	CLSA	E1BPPLNHDR - CO Planning: Header Information (CSLA)
		E1BPACPOBJ - CO Planning: Objects (CSLA)
		E1BPACPCTRL - CO Planning: Control Values (CSLA)
	COEJT	E1BPACPTOT - CO Planning: Total Values 2 (COEJT)
		E1BPACPVAL - CO Planning: Total Values (COEJL)
Activity_Type_Group	CLSA	E1ACTIVITYTYPEGROUP_CREATE - Header Segment
		EIBPSET_HIER - Interface Structure for Groups - Hierarchy Table
		E1BP1115_VALUES - Activity Type Groups - Intervals in the Hierarchy
Activity_Type	CSLA	activity master
	CSLT	activity type texts
Additive Costs
Bank Master Data	BNKA	Bank master data
	BNKAIN	bank master (Additional Fields for BNKA)
	E1BANK_CREATE	E1BANK_CREATE-Header Segment
	E1BP1011_ADDRESS	E1BP1011_ADDRESS-Transfer structure object 1011: Bank address
	TIBAN	IBAN table

 

How to keep IBP system highly configurable but also optimize its performance?

SAP IBP Planning Area Configuration & Performance Recommendations
Source: https://launchpad.support.sap.com/#/notes/2211255 (Version 4 from Apr 21, 2017 in English)


Symptom
IBP is a highly configurable system and it is possible to configure it in a way that's not optimal for performance. This note describes some general guidelines to achieve good performance for a planning area in IBP both in terms of configuration and sizing.

Other Terms 
IBP, S&OP, Scaling, Performance, Planning Area

Reason and Prerequisites

None. This note is generally valid fo S&OP3.0, IBP4.0,  IBP5.0 and IBP6.0

Solution

1. Sizing and Planning Area Complexity

• It is highly recommended to perform sizing prior to project start to work through the current and future sizing requirements and to also attempt to get the right initial size of the system.
• Sizing is primarily based on the number of stored key figure value (which we call planning points). As each planning area is different in terms of key figure calculations and planning views and charts being used, the details of system performance need to be verified by each project
• During your implementation project, it’s recommended to verify the sizing assumptions after uploading data into the system. 
• SAP recommends a phased approach to go-live with complex planning areas with many configured key figures and to plan for a performance test.

2. Keep your Configuration as Simple as possible

Attributes

• Use as few attributes as possible in master data and even more so in planning levels.
• Do not make attributes as key of master data types or roots of planning levels that really aren’t.

Master Data Types: 

• Keep the number of Master Data Types to a minimum. Fewer Master Data Type also typically reduces the number of planning levels and the need for joins for calculations across multiple planning levels.

Key Figures and Planning Levels

• Model key figures at the required detail with regard to time and attributes. A finer granularity than needed carries a performance penalty. (e.g. if you don't have to plan at the ship-to level for customer, don't)
• You can use non-key attribute of a master data type as root attribute in Planning Levels.  That way you don’t need to model additional Master Data Types
• Minimize the overall number of planning levels in your planning area (but do not increase the amount of data you need to store while doing this)
• Minimize the number of root attributes in a planning level. A root attribute is to model an independent dimension (which means the root attribute is a key to the key figure data). It is recommended to have no more than 5 root attributes for a planning level. 
• Minimize the number of calculations that include different input planning levels wherever possible (but without increasing the number of  key figure values you need to store)
• Avoid on the fly attribute transformations as much as possible, as corresponding queries can be slow. Instead try to store the result of attribute transformation to a stored key figure using Copy Operator.

Attribute as Key Figures

• If you use key figures that are filled via a master data “attribute as key figure”, use time-independent key figures instead of time-dependent ones. If Time Dependent Attribute as Key Figures are required, use From Periods and To Periods settings in Attribute as Key Figure configuration to limit the number of time periods this attribute needs to be copied to.
• In case, an attribute value is not time independent and needs to vary over time, then load it as a regular key figure.
• Do not configure master data attributes used in Supply Planning – such as CRATIO, PRATIO or TRATIO as attributes as key figures. There are key figures for this purpose.
• Attributes of master data types can be used in calculations: You don’t need to add integer attributes as key figures just for using them in calculations.

Aggregations and Disaggregations

• If request level calculation is SUM or AVG, use the aggregation mode of SUM or AVG instead of CUSTOM. For Min , Max or Weighted Average Calculations continue using CUSTOM aggregation mode.
• If you need to disaggregate a key figure based on a calculated key figure, avoid the Advanced Simulation Operator if possible as it may have some performance impact.. Rather consider using copy operator to copy the calculated key figure to a stored key figure using a batch job.
• Keep the number of attributes in the planning views to minimum necessary. More than 6 attributes in planning view may affect disaggregation performance.

Verification (very important)

• Check for attributes or key figures that are not used in planning views or analytics and remove them from planning area or even from master data. You can ask SAP for help if you have a large number of attributes to check.

3. Topics that require Special Performance Consideration:

Multiple Planning Areas:

• If you have multiple planning areas in your system, it is recommended to have separate master data types for each.

Data Integration

• Schedule large data loads during off hours. During import jobs users might be blocked from saving data.
• Implement a delta mechanism to limit the number of rows per periodic data import job.
• Don’t load data frequently if not required.
• Use the purge functions to purge data that is not used in the system. There are different options: PURGE (Purge Operator for time series) , PCH ( Purge Change History) ,  Deletion of Key Figure Values and/or master data.

Change History:

• Only switch on change history for planning areas and individual key figures where it’s really required.For example Key Figures that are changes from excel.
• Usually it’s not required to track changes for key figures loaded from external systems. If you need to make manual changes to such key figures, which you want to track in the change history, it is better for logical and for performance reasons to introduce an additional key figure where you make the change and use an overwrite calculation (defaulting).

Snapshots and Copy Operator

• Avoid Snapshots or Copy of key figures with complicated calculations. Instead try to copy the input key figures and then reconstruct the calculation with the copied key figured.
• For example if you want to snapshot a Key figure with currency and/or UOM conversions, first snapshot the key figure without conversion and later apply conversion on the snapshotted key figure.      
•  It is recommended to use Copy Operator instead of Snapshots if  you’re not using cascading of Key Figures for snapshots or if you don’t need the entire time series in the snapshot.. Copy Operator is preferred because you can change the duration, define Target Key Figures and  you have the flexibility  to modify calculations.

Global Configuration Parameters.

• Make sure the following global configuration parameters are configured to the recommended default settings to get better performance. The defaults are available in the system for reference:
• TRACE->TRACELEVEL .
  • Make sure it is not set to D for debugging or some parts of the application like disaggregation will be slowed down
• PLAN_VIEW->MAX_RESULT_ROW_SIZE
• INTEGRATION-STAGCLEANUP
• PLAN_VIEW->MAX_DIM_MEMBERS
• SCN_COUNT_MAX 

Planning Operators:

• Schedule the planning operators staggered so that they don’t overlap each other and cause unwanted locking.

Scenarios and Versions:

• Creating many versions can increase your system database size. It is recommended to have 4 or less versions.
• Try using more baseline key figures as reference key figures for versions in place of version-specific key figure
• Ensure that the number of end user created scenarios remains reasonable and manageable. This requires educating the users on use cases.

MRP Planning Strategy

MTS - Make to Stock (push model); easy to forecast, moves fast
MTO- Make to Order (pull model): slow moving products, hard to fast, costly to keep in the inventory
BTO - Build to Order (pull model)
ATO - Assemble to Order (pull model): Motorcycle, Bike, customized garment, computers
ETO - Engineer to Order (pull model): construction, engineering firm,


Below the some more specifics about MTO model:

MTO - manufacturing process , manufacturing starts only after a customer order is received

It's a pull type of operation.

Production is triggered from a Sales Order, or a Customer Order

Make to order production is largely a production planning configuration. It is also controlled by the requirements type, which is determined by three things the strategy group (MRP 3) in MMR the MRP group (MRP1) in MMR the item category and MRP type (MRP 1)

The requirements type is determined on the basis of the MRP group (MRP1) and the strategy group (MRP3) in the material master record. In addition, a plant must be assigned for make-to-order items in the sales order.

The strategy group groups all the planning strategies that can be used for a particular material. The planning strategy represents the procedure used for planning a material and is (technically speaking) controlled by the MRP types. Dependencies You define planning strategies and strategy groups in Customizing for demand management.

Process in ECC (Process flow of Strategy 20:)

https://blogs.sap.com/2014/05/11/make-to-order-strategies-strategy-20/

1. Creation of sale order  – VA01

2. MRP run – MD01/MD02

3. Planned order conversion to production order – MD04

4. Production Execution – CO02, MB1A, CO15, MB31

5. Sale order stock in plant- MD04

6. Delivery of the stock to customer against the sale order – VL01N

MRP Strategies

https://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=396460060

Make - To - Stock

10 - Make to stock production: http://scn.sap.com/docs/DOC-50032

• For Finished product (Material master – MRP3 tab)
• Only the planned independent requirement important when run the MRP
• Sales order only info, not relevant for MRP, but you can display them
• determined without reference to sales orders
• FIFO principle (oldest PIR reduced first)

11 - Make-to-stock prod./gross reqmts plnning: http://scn.sap.com/docs/DOC-53077

30 - Production by lot size:

• For Finished product (Material Master – MRP3 tab)
• FIFO principle (oldest PIR reduced first)
• Sales order is MRP relevant
• Planned independent requirements are not consumed by sales orders

40 - Planning with final assembly:

• For Finished Product (Material Master – MRP3 tab)
• Sales order is MRP relevant
• Planned independent requirements are consumed by sales orders
• If the customer requirements exceed the PIR, automatically creates planned order (including unplanned quantities) for sales order.

Example: Material Master settings in MRP3 tab:

• Strategy group: 40
• Consumption mode: 2 (Backward/Forward comsumption)
• Bwd consumption period: 30 day
• Fwd consumption period: 20 day

With this settings the Sales Order will be consume the required quantities from the Backward PIR (to 30 days from SO date), and afterward from the Forward PIR (to 20 days from SO date), still the Sales Order not will be ok.

• MD73 shows you the Planned Independent Requirements
• Sales Order not will be visible in MD04
• SE16:
  • PBIM: search Material, and copy the Requirement Pointer
  • PBED: insert Requirement Pointer, the quantitites will be visible
  • PBHI:
• MD74: if you delete the Sales Order, the Planned Independent Requirement will be visible again in MD04 (Stock List)

70 - Planning at Assembly Level:

• For Semi-finished product (Material Master – MRP3 tab)
• The finished product can show any strategy!
• The requirements consumed by sales orders in the second level of BOM
• Using this strategy for example: in car manufacturing

Make - To - Order

20 - Make to order production: http://scn.sap.com/docs/DOC-54915

• Without PIR
• Production only if there is sales order
• Using this strategy for example: special yacht or spaceship manufacturing etc.
• Material Master MRP4 tab you can set Ind/Coll. (only to subassembly), and then you can see the Orders what you are set in here:
  • 0 – inheritance from header
  • 1 – Individual: stated individually
  • 2 – Collective: grouped together
• MRP elements are created with reference to sales orders  
• MD50: MRP run for the grouped segment

50 - Planning without final assembly:

• Assemblies and components are kept in stock until the SO is received
• Indepenedent planning from SO with planned independent requirements (PIRs)
• High value added at final assembly level
• Reduce delivery times
• Individual/ collective indicator except for the final assembly it is set to 2

Existing Planning Strategies in SAP

Strategy	RTyp for Demand Management	RTyp for Customer Order/requirement	Name
0			No planning / no requirements transfer
1		41	Make to Order
10	LSF	KSL	Make-to-stock production
11	BSF	KSL	Make-to-stock prod./gross reqmts plnning
20		KE	Make-to-order production
21		KP	Make-to-order prod./ project settlement
25		KEK	Make-to-order for configurable material
26		KEL	Make-to-order for stock item
30	LSF	KL	Production by lot size
40	VSF	KSV	Planning with final assembly
50	VSE	KEV	Planning without final assembly
51	VSE	KPV	Plng w/o final assembly / project settl.
52	VSE	KSVS	Plnng w/o final assem. w/o make-to.stock
54	VSE	KEKT	Planning variants
55	VSE	KELV	Planning stock item w/o final assembly
56	VSE	KEKS	Characteristics planning
59	VSEB		Planning at phantom assembly level
60	VSEV	KEVV	Planning with planning material
61	VSEV	KPVV	Plng with plng material / project settl.
63	VSEV	KSVV	Planning w.plng material w/o mke-to-ord.
65	VSEV	ELVV	Planning stock item with plnng material
70	VSFB		Planning at assembly level
74	VSEM		Plng at assembly lvl w/o final assembly
80		KPX	Project settlement for non-stock items
81		KMSE	Assembly processing with repetitive mfg
82		KMFA	Assembly processing w. production orders
83		KMNP	Assembly processing with networks
84		SERA	Service orders
85		KMPN	Assembly processing with network/project
86		KMPA	Configuration with process orders
89	VSE	KMSE	Assembly proc. w. characteristics plng

Planning Areas used in IBP Time-series based planning And Order-based planning

SAP2, SAP4(C), SAP6, SAP3, SAP5, SAP7 are standard SAP delivered sample planning areas.

IBP - Things to consider regarding Co-products in Production Source of supply

Things to consider regarding Co-products in Production Source of supply

Optimizer

The optimizer doesn’t distinguish between the main output product and co-products. If overall costs allow, the production source for the main product will also be used to satisfy the demand for co-products.

Lot Sizing

Lot-size parameters (for example, to define minimum and/or maximum lot size) aren't available for co-products. You can only specify them for the main (output) product.

IBP- CPI Integration - Best Practices for Extracting Data out of IBP

Source: SAP note - 2493042

You are using SAP Cloud Platform Integration for data services to export key figure data from an IBP application. 

Please note that SAP HANA Cloud Integration(HCI) has been renamed to SAP Cloud Platform Integration(CPI)

Environment

• Supply Chain Management (SAP SCM)
• Integrated Business Planning (SAP IBP)

Cause

You are using SAP Cloud Platform Integration for data services to export key figure data from an IBP application.

For extracting the key figure data, a calculation scenario is used to extract the data out of IBP. A calculation scenario is a special construct in the SAP HANA database that the integration service can use to read data from an IBP application and to write to a file, or to write the data directly to the target on premise system using a web service call. Calculation scenarios are generated in the planning area of the IBP application.

While defining the Data Export Task, it becomes essential to put necessary filters and optimize the filter conditions to ensure that filter conditions are pushed down to IBP.

• It decreases the run time of Data Export Task and optimal usage the resource/CPU/Memory consumption.
• Minimize the impact of this task on the normal business activities of the users. 
• It also reduces the chances of exceptions like connection reset which might lead to an open cursor IBP and in turn impact the performance of IBP.

Resolution

Kindly follow the below guidelines while designing the Data Export Task in CPI-DS.

1. You should split the data extraction needs into multiple tasks based on different filter conditions wherever possible. You need to ensure that smaller data set is extracted from IBP for the optimal usage of resources in HANA.
2. You should avoid the concurrent execution of the Data Export Task. Instead, you schedule the Data export task sequentially 
3. You should always specify the exact PERIODIDn attribute based on the time level you want to extract the data, instead of selecting the generic PERIODID attribute in your data flow. Please note PERIODIDn do not refer directly to the time profile level. For your planning area PERIODIDn are mapped as follows to the time profile level.  
• PERIODID0 Day (Lowest Time Profile Level)
• PERIODID4 Week
• PERIODID3 Month
• PERIODID2 Quarter
• PERIODID1 Year (Highest Time Profile Level)
4. You should not use the IN/NOT IN operator, instead you can use the OR operator for filter conditions.
• For e.g. instead of PRDID IN('X','Y') use (PRDID='X' OR PRDID='Y')
5. You should put the filter on PERIODIDn attribute instead of TSTFR for time period filter conditions. You can give the relative filter conditions for the PERIODIDn.
• For e.g. If you want to extract the data for the current period+12 periods in future, you can define the filter as (PERIODIDn>=0 AND PERIODIDn<=12).
• If you only use the equal to filter, then you need to provide the absolute technical PERIODID which can be retrieved from the excel UI. The filter condition will be like PERIODIDn=1067
• You may also use CPI DateTime functions like WEEK_IN_YEAR, MONTH to meet the different extraction requirement from the Business Perspective. You can refer to the following help document for the full list of CPI DS functions: https://hcids.hana.ondemand.com/DSoD/help/index.html#5cc2bab3d53e43c1bfdeda50c6674625.html

Product

	Product or Product Version
	SAP Integrated Business Planning 1702
	SAP Integrated Business Planning 1705
	SAP Integrated Business Planning 1708

This document is referenced by

	Number	Title
	2571962	Key Figures aggregating at wrong level - SAP Cloud Platform Integration for data services
	2565151	Error: Exception Message: SAP DBTech JDBC: [260]: invalid column name .TSTFR - SAP Cloud Platform Integration for data services
	2516625	HCI:attribute is missing in the Calculation Scenario