SAP APO Training Classroom Notes

SAP-Enterprise central component
SCM-Deals with material flow

SCH will help in 1.planning the execution
2. Visibility
3. Collaboration
Planning—–> Advanced planning and optimization (APO)
APO:-(Majorly)1.Demand Planning(DP): forecasting
I/P = Sale history
O/P —–> Forecast
2. (more) SNP ——–> I /P——-> Forecast
(Supply N/W planning)O/P ——–> Plant order, production orders
3. (Less) PP/DS ——> I/P ——->SNP Plant order
Production Planning} O/P = Production orders
Detailed Scheduling
4. (Majorly used in oil & Gas) GATP: -I/ P: -Sales order
Global availability to O/P:-confirm sales
5. TM (Transportation Management)—–> I/P :- Stock order, sales order
O /P: – Shipment document
6. SPP
↕ CIF (core inter face) Integration between ECC & SCM
Land Scrape:-
[Development server] —-> [Quality server] —–> [Production server]
Testing is done in Quality

Any company deals with Man, Money, Material
↓ ↓ ↓
HR modules Sales & financial Production
Any product has cost + Profit = Price
Optimizing all the costs for minimizing the price
Cost involves—> Manufacturing cost, transportation cost, strong cost
If the gap between demand & Supply is less, cost will decrease
Iz —–> JDM
Demand & supply planning is done in SCH (APO)
APO —–> DP —>Demand planning
SNP—->Supply Net work planning
PP/DS —–> Production Planning & detailed scheduling
GATP —–> Global availability to promise
TM ——–> Transport Management
SPP ——> Service Parts Planning
SAP ECC and SAP SCM are different 2 servers
Logistics APO
APO will suggest the logistics modules to execute
The data should flow in both directions with the help of CIF
DP —-> I/P: Sales history
O/P: fore casting
SO3——> BW —–>DP —–> sales history
1. With BW server is one method
2. With APO-BW is other
Real time sales history ———->(O/ P) forecasting
SD ↑
SO2 ↑
SO3—————> [BT] (Business intelligence)——->↑
Territory/ district
Dealer Product Month
Location Product Time
*Planning levels and planning objects are technically called as characteristic
*Characteristic can have any no. of values
Each characteristic has its own values
Zone State District Dealer Segment Brand Stock keeping unit (Sky)
South AP HYD HYD01 Sedan Dezire SD-VXI
South AP HYD HYD01 Sedan Dezire SD-ZXI
*Any object which deal with quantities (or) currencies is called Key figure
Planning area
Eg: 1 2 3 4 5 6 7 8 9 10 11
Sales 1 20 30 40 50 60 70 80
Group of characteristics is called master planning object structure (MPOS)
CVC ——> Characteristic value combination ——> unique combination of characteristic values
Set up in APO System
Heart of APO

Planning area is the central data structure and also heart of APO
Before creating planning weekly area SBP, MPOS and UOMS
In SBP, if selected weekly, the sales is done in weekly wise
Restrictions ——-> /.roll wise.eg: District manage
State manage
Zonal manage
2. Location Data wise Eg: two different state managers
SBP define how the data is stored in planning area by roll wise, in planning book we can restrict the key figure and characteristic
By roll wise, we can create any number of planning books
One planning area, we can have any no. planning books
One planning book must contain one date view and any no. of data view can be created
Data view contained time bucket planning [TBP/ PBP]
The customer can only view data view Eg: religion manager
If any data changed in data view, that changes are done in planning area only for particular person
Planning book is a filter of planning area
Eg: Manager planning book
One MPO’s for planning area for one MPO’s we can have any no. of create any no. of SBP but we assign one SBP one Planning area
SAP menu





Work bench
Creating Characteristics
Info area is like a drive
Info objects right click


Local Object

Select HUL-IA
↓ (right click)
Create info object catalog (like folder)

Define info object: HUL-IOC-CHR and same in

Select char (or) key figure

Characteristic stating with ‘O’ is for BW
“ “ “ ‘9A’ for APO from SAP
Eg: Select HUL-IA


Create info object

Give char: HI-zone


Select APO

Give data type: char
Length: 10

Select active button




H1 –zone

After key figure is created with HUSLS


Select Quantity
Select UOH as UNIT of measure

Press [] button
Creating SBP:-



Current settings

TR 32 – Periodicities for planning area

SBP:- HUL –SBP Fi year variant is not own calendar
Select week
Start date:
End date:
Time stream ID
Holiday Calendar:
Create Planning area:-
Planning area ——-> right click

S. Curr: INR

Select key figure aggregate

For all Key figure give
Cal type: P
Di sag. Key fig: APODPDANT

LOGING logic

Except 1st radio button other radio buttons has be activated
When we have seen planning area the planning area is in inactive stage
Fields are called time series object

derision: 00
S.D: 01.12.10

Live cache is to increase the performance error
No Link to Live cache
LC 10 –Name of Data base conn: LCA

Live cache: Monitoring



Start live cache —–> Yes
Creating Time bucket profile:-
SAP Menu




Setting —-> TR 30 Maintain TB for DR& SCF

Time bucket: 6M monthly

Number: 6
Display periodicity: Months} TB: 2mm 2hm
N: 6
Disp: H
N: 2
D: w
Creating planning book:-
SAP Menu



Current settings

Define Planning book



Give HUL –BG
Planning area: HUL


Select all

Select all HPO’s

Continue (One planning book must have
↓ at least one data view)
Data view: BACK GROUND
Status: 2
TB Profile: 6mm 2 hw
TB past: 12M

Key figure description is planning book specific
To check the planning book Hanna


Inter active demand planning
Loading data is nothing but the loading the data from the live cache, as the panning area is not having that data
DB ——> Live Cache —–>DB, PB, PA
For Fore casting
Fore casting planning parameters
1. Period
2. Future period
3. History
4. Fore cast KY
5. Fore cast Model
6. History KF
7. fore casting Model strategy method
These all are maintained in Hastert fore casting profile
3 ways for forecast variant
Uni ——–> History
Multi variant ——-> Budget, environment
Composite ——> both univarient & multivariate
Fore cast model:-this is mostly tactical
Mostly used is Univarient
Univarient has 20 to 30 strategies
1. Moving average
2. Weighted moving average
Constant strategy has 4 formulas different strategies have different formulas

For Maintaining FP-(Interactive)

Maintain FP

Master Prfl: HUL-MFP1
D: “
Fore cast KF: HUL-FCST
Period indicator: H
Fore cast Horizon
Periods: 6
History Horizon
Periods: 12
Model. Section
[] Univariate fore cast: HUL-UM1

Creating Univariate profiles:-
Profile: U/UL-UN1
Key figure: H-SLS. Version: 000
Fore cast strategy: 11

Single profile saves
10-10 is constant strategies
20-29—–> trend strategies
30-39 ——> seasonal strategies
40-49 ——> Seasonal Trend
50-59 ——-> Automatic
56———> Mostly used
60 ——–> Historical data
70 ———> Manual
Execution of fore cast:-
1. Interactive
In planning book: we have to give the option has univarient for execution of fore cast in Univarient model
Fore cast companions for comparing the forecasting models
Assigning user to the planning book of Data view:-
After planning book and data view creation go to
DP ——>planning——> Interactive DP ——> Select the planning book in that select the data view —–> Next ——> Press selection, window icon and give object selection parameters
Eg:-show RHS-PROD
Apo planning version: 000
RH3-Place: HYD
And click on save ——> It will ask the name for the selection window
Eg: Given as manager prod view

Then press selection profile button below selected objects

On the left side under selection all selection IDS manager product view

Select that selection id and drag to the right side below SAP user

Then save
(Mostly Done at Background)


DP in BG

Define Activities for Mass processing




Fore cast
Master prl(PA) —–> HUL-MFP1

Execute (Macro: Tool which is
↓ used to do more simplest
Save from more complex data)

Creating back ground Job

Job no: HUL-FCST

Status: S

Activity: HUL-FCST
Parallel processing profile (Basis need in real time)

[] Generate log
Selection id * one HYD_LUX
Select all
Aggregation level
Select the state & brand


Schedule DD in BG

Job No: HUL.FCST ——-> execute

Date / time
[√] Periodic job

Period values

Select daily

Factory calendar: 01
Work day: 3
(*) Beginning of month

Immediate ——> save
INSH 37:- ——-> JN: *HUC*
UN: SAP user
Job status: schedule




Calculate proportional factors

Basic settings ↓

PV: 000
P from: 01.06.2012
To: 30.11.2012
Cal P:
PV: 000
From: 01.12.2012
To: 28.02.2013
(*) Fixed propositions

Save as variant HUL-prop-calc
Other settings
Only for Lux
Calculation type: P —-> APOOD DENT
To find proposal factor
To find with how much percentage

Seg (1)
↙ ↓ ↘
Seg1 seg2 seg3
Calculation Proportional factors:-
Period D from:-
A value for XXX[S]
A value for YYY[-1]
6 7 8 9 10 11 12
/——————————————————–/ 0
(end of 11th month)
Beginning of mth-XX months
End of mth +YY months -XXX
XXX – 1 +YXX
YXY – 5
Info cabe: used as data storage
Data: Un-structured information
Information is a structured info
2 dimensional tables take more time in performance of retrieving the data
So developed 16 dimensional tables called cube
<----------[Fact Table]------> 16 dimensional

Fact table deal with quantity, it is a key figure 3 dimensions are mandatory
1 dimension is Data pack
2 Dimension is Time
3 Dimension is UOM
Remaining 13 dimensions are customized
Customized dimensions Eg: Product dimension
Location dimension
Organization dimension {Depot, Terr, state, zone}
Each dimension can have 24 Characteristic.
Eg: Product dimension
1. Product
2. Brant
3. Segment
Info cube which can hold max information called as Star Schema
Fact table is connected to product dimension by DIM
From product dimension to 246 values (or) Characteristic is by SID (System ID)
Modeling ——–> Mapping
Extraction ——–> extracting the data
Reporting ——>

RSA 1:- Cube is called info provide, cube is one type of info provider
Physical data & —————–
Pseudo data —————- Remote
(Multi provides)
Info cube is created in info provider
Info provider

Select the HUL-LA
↓ (Info cube must be between 3 to 9 digits)
Create info cube

Info cube: HUL-SLS
(*) Standard info cube
Select BW

Dimensions (Data package, Time, Unit, Dimension)

Right Click and give name as product
And again RC on dimension
Create dimension

———> Fact Table Key

Key figure
Time —-> 0 Cal months
APO planning version from character stick
9 versions to product dimension

Creating source system:-
Source systems ——-> right click on source system


0 file system

Logical system name: R3-H-Exl
Creating data source:-
Data sources ——-> Click icon
SAP (Application component is nothing
File but a folder)
Under file select
Right click on data source for R3-H-EXL




Select HUL-ACJ, RC

Create DS

DT DS: Transaction data



Extraction ——>12
Any System has 3 data:-
Configuration data – Structure
Transaction data —> repeated
Master data —-> one changed rarely
—-> Delta process: Delta by full upload
Adapter: Load text- type file from: Local work station
Name of file: ————–
Header: 1
Data format: CSV
Data sep:
Escape sign:
Load Example data
Sales – H. sales
Month- O cal month
Zone – H – Zone
Read preview data
1. DS-IA(rc) ————-> Create transformation from DS
2. From info provide select H-Sate ——> Create transformation
OT: Info cube
N: H- sale
Object type: DS
Loading data to DS:-
↓ rc
Create info package


↓ (structure never hold data)
Processing PSA: Persistent Staging Area
(*) Only PSA Data source structure is a table it is a PSA
(*) Full update
Start —> Delta fooding from ECC system to APO system

Monitor icon

To see PSA table click o icon


Create DTP

Gives U all the information


Active icon

When data is loaded into info cube, request id is created
TO see data in info cube
After loading data into info cube, we have to load data into planning area
Loading data from info cube to planning area


Data administration

Any memory will have 4 steps
1. What is Macro
2. Iterations
3. Result
4. Argument (or) Calculations
Cube —–> Load —–> fore cast —–> Manage FCST —-> SNP Release


Info package <---- Sales Loading data from live cache to planning area Macro is used for simplest calculation to most complex calculations Any Macro can be executed in both 1. Interactive 2. Back ground Interactive execution of macro takes when it has to execute In interactive, 4 options 1. Default macro 2. Start macro Macro is also a data view specific Life Cycle Planning:- 1. Like models 2. Phase in-phase out Maximum no. of characteristics used in life cycle planning is 6 Like Model:- Fore cast ------>MFP —–> LPA ——> (no) fore cast strategy
↑ ↓ (yes) ↓
Selection Assignment table fore cast
↑ ↓
P-104 P-104 P-102↗
102 ↓
Like profile
Realignment:-Reorganizing master data & transaction data

Data Realignment

1. Correction of Master data
2. Delection of MD
3. Division of MD
4. Combining of MD
Realignment is changing of data in live cache
Realignment works on MPO’s
Copy works on planning area
Export fore casting: Fore casting for past periods
For doing export for casting we use 2 methods
1. Out line correction: sigma is used for outline correction
0.6 ——> 2.0 (range is from)
Default —–> 1.25
Threshold value is controlled by sigma value
Threshold value is done by export fore cast
0.6 ——-> higher no. of correction
2.0 ——-> Lower no. of correction
Correct history is based on sigma value
2. Medium method: taking the middle value

Maintain forecast profile
Alpha is used in constant strategies
Beta is used trend
Gamma is used seasonal
Ranges from 0 to 1 —> default values: 0.3 ———-> (If it is 0.3, it will give equal importance to all the
Smutting factor: points, if latest pattern, then value change to 0.9)
It tells us the information whether it has to give importance
To past pattern (or) the Latest patterns
Eg: 0.3 ——> Past
0.9 ——-> Latest
Crosten method: It is used for automatic strategy

Used for un-even demand (speradik demand)
Automatic model 1: It will execute only on alpha value
Automatic model 2: It a detailed executions alpha 2 is nothing but the increment value
Eg: Inc [1]
Then execution will be [0.30, 0.40, 0.50, 0.60, 0.70, 0.80, 0.90]
It is a detailed explanation of the values
Fore casting Error: It is done for export fore casting
MAD ——-> Mean absolute deviations
MSE —–> Mean square error
RMSE —–> P
MAPE ———> Mean absolute percentage errors
MPE ———> Mean percentage error
Macro:-(Manual Interactive)

Current settings

Macro work bench

Select HUL-BG view


6 iteration
A row: H3-MHFCST
Row: H2 Fore cast

Keep in depot

See the effect in PB
In interactive 2 ways:-
1. Manual
2. Automatic
Keep Marco as default in macro screen
When U see PB —–> automatically loaded in events
Performance will below 1. Default —-> Copy FCST
2. Start ——> copy FCST
3. Level change when drill down happen to detail (all),it will work
4. Exit
2. Forecast intimation (Future)
Making FCST and MECST at the starting day of month
3. FCST variation for last 3 month
(3 iteration – 3 month from step up function)
Auxilation table
(Temperaty) ——-> adding
AVG () or
MANGR FCST variation
——> New set (3 iteration H: 09 to 11
—–> row Avg of 3 months(From M 09.2012)
Function AVG[$H1-sales(09.2012; H1-sales (M 11.2012)]
——> MNGR FCST variation: (1 literations H 12.2012: H12.2012
——> Row: MNGR FCST variation (Frm M12.2012)
ABS (Row: R3-MG FCST (From M 12.2012)
Row Avg of 3 months (Fm M 12.2012)
Row: H3-HGFCST (frm M 12.2012)
• 100
Step: Information
If (condition)
MNGR FCST Variations 25 %
Row MNGR FCST variation (From M 12.2013)
Row: M3-MG
Life cycle planning:-

Life cycle planning



Like profiles

Like profile: Liril
D: 1
Ref value Action %
L-100 S 100




APO product H2.State like profile
LR-1000 AP Lirl


Life Cycle planning Active in – for cast profile
Realignment :-(SAP APO/ MC 62 (For MPOS)
SAP APO / RLG copy (PB must not be opened)
(*) Realignment

Create change table (nothing but characteristics)


Yes (Hyd-01
↓ HYD -02)
Select Depot

Maintain Entries

Copy factor: 100, Copy Log is [M] is for transaction data
Step status
Source: HYD-01
Dest: HYD01
[√] Delete source

When realignment is done, transactional data will also update
Realignment can do two actives
1. Master data
2. Transactional data
Transactional data is nothing but key figure values
Creating of new depot:-
Copy: Only transactional data will be copied only PA
Realignment in MPOS
For manager forecast:-

Package will contain request
When assigning user to PB, Request id must be go to SE 09 for release of request id
/ nstms
/ npfcg—-> IDES /SCM
Activate live cache lock- at characteristic level

Info cube ——-> CVC load ——-> PA reinialize ——> [Initizek F] —–> Prop faction variant —->[FCST]
↓ (DTP) 4↓ (Macro)—> JOB ↓
DS consistency [Copy to Manager]
↑(info pack) ↓
Excel Macro (Job)
For Job execution, we are using variant
SE38 / Sap APO /TS * REIN*
DP —–> Time series
SNP —–> Category, order series data
PA —–> Key figure —-> Details —–> semantic (001) —-> for DP
In Ecc. RSA6
RS02 —- Creation of LS 02
Lbwb —- Lo data extraction
RSF 4 —- To see the data
RSds —- Ecc —-> data source repository
In —PA —-> Info /rspc —> Environment

Maintain process chains

Create icon

Process variants: HUL-START



Direct scheduling —–> Change selection
From APO ↓c
{Starting using Immediate
Meta chain} ↓
↓ √
Done by tibco ↓
And other jobs Save



$ tmp

Process type’s icon X
Select SCH –DP

Generate CVC

Drag and drop on right side

Give name


Contents: HUL- GEN [√] change icon


Draw a line between HUL-Start and HUL-Gen

Click on time series consistency

Drag drop


Create variant for consistency

Draw line between HUL_CVC- Gen and Time series check

It will ask U successful

Load from cube





Initialize (Create time series objects)



Draw Line

DP back ground processing

Calculate propos

DP back ground Kob


Check icon

Activate icon
—–> Macro is data view specific
Alert: types
1. Dynamic alerts[Run time errors disadvantage: performance]
2. Data base[Alerts are stored in data base(SAP recommendations)]
Configuration:-Interactive planning book, Click univarient icon

Diagrrosis group

Upper limit: 10,000

Save group
SAP Menu


Supply chain Monitoring

Alert monitor

Alert monitor

Overall profile


Relative time interval
(*) Months: 3
Planning version: 000
Forecast tap
Fore cast Alert prof: HUL-FCST-ALT
Error total:
MAPE upper limit


Save fore cast

Save (Over all proof save)

Redetemine alerts


Maintain alerts for DP/ SNP ← Customized alerts

New entry

Type: 9999
Priority: error
Text: You’re fast deviated more than 30 % of last 3 months AVG


Create request

Name: DP-Alerts
——> Data base alerts
SDP tab

Customized alerts are used in Macros
Customized alerts
In interactive planning book
ECC ———–> APO
<--------- (IM) Integration model ECC APO 1. Define logical system procedure 1. Define Logical system Forgive name for logical system APOCLNT 800 ECC CLNT 800 ECC CLNT 800 APO CLNT 800 2. Assign logical system to client 2. Assign Logical system to client (ECC CLNT 800) APO CLNT 800 3. Apo version 3.RFC 4. RFC(Remote function call) ECC system IP address ----> APO system IP address Log in ID & PWD
—-> Login ID & PWD 4. Define BSG (Business system group)
5. QUUE type 5.Assign BSG & Queue type
In bound or
Out bound
Mostly out bound
BSG: ECC2 (BSA2) ————->APO (1001 table)
Eg: ECCS (Eg: 1001 pen) ———-> APO
In ECC system:-
Transaction code: SALE


Integration with other my SAP Com components

Advanced planning and optimization

Basic setting for setting up the system landscape

Name Logical system

For ECC (T90 CLNT 090)
(APO CLNT 090)


Assign logical system to client

800: Logical system: T90CLNT 090


Specify SAP APO release

APO CLNT 800 —–> 50

Setup of RFC connections

↓ (double click)
Change icon

Target host: visuinfo scm
System No: 55
IP address:
Log on & security
User: SAP user
Pw: welcome


Set target

APO CLNT 800: blank (out bound type)
1(In bound)
APO Settings:-

Integration with SAP components

Integration via APO core interface (CIF)

Basic setting for creating the system Land scrape

Name Logical systems

T90 CLINT 090


Assign LS to client
800 ——>(details) LS: APO CLNT 800

Set up RFC connections

ABAP connection

T90 CLNT 90

Target host:
System No: 24
Log on & security:-


Connection Test

Maintain BS Group


Assign Logical system & QT

BSG1: Apo CLNT 800 50
For R3 BSG@: MOCLNT 090: X: 600: out bound Queue strike


Create plant in ECC

P 001 ——> for mang facture
D 001 —–> for Depot


Distribution resource planning

Basic setting

Maintain Assignment of node type to plant

Allocation of node type

P001 ——> blank or PL
D00L ——> DC


Data transfer:-
CFM1: (create integration model)

Model Name: R3 –PLANTS
Logical system: APO CLNT 800
APO app: R3-Plants
[√] plants
First plants then only material
Plant: Poo1
: Doo1

Variant: R3-Plants

Generate icon

Select plant and click on generate IM icon

/NC FMZ (activating the integration modes)


Select row and click on active then after start


Master data


Location: Poo1
——–> [BW] ————-> [APO-BW]
↑ modeling ↓
Sales order CVC
↑——–ECC POO1 —–>(CIF) ↓
LUX 100 DP

SNP Poo1 LUX 100
Relese: /n/ SAP APO /MC90



Rea ease DP to SNP

PVE: 000
Key figure: final demand
Constant demand

1. Income PVer: 000 SNP: is order series date
2. Outcome Category FA (or) FC Purchase requisition is just like quotation
3. Balance A —–> receipt (incoming)
4. Fore cast B ——> outcome
C —–> Stock
FA—-> fore cast

From date:
To date:

SDP 94:-
PA ——> extras —–> Data extratation tool

PA: HU Backup infoube = PA
Data source: HUA-BK ↕
↓ Data source
Generate Data source ↑
↓ APO system
Give Name DS


Data backup button




/n RSA1

Data source

BI —-> Data source (APO)

Business ware house
Data source: HUL
Source system:
Before fest, Realignment & Release to SNP,
I : 1st time =P
2nd time = S
A: Average (rare)
S: Pro-rata basis
Product split
LEX 100 ↗Lux 100 + 10 % extra
↘Lux with 2 % off
Release from DP to SNP
Product sp lit

Product split
Location: 0002
LUX 100
Ping version: 000
From: 01.01.13
No. of periods: 3
Period: M
Target product: Lux 100 + 10%
Lux 100-2%
Supply Date: 01.01.2013
Proportion 10%: 0,7
4 Back ground
1. Fore cast
2. Macro
3. Release prfl
4. R/3 Transfer prfl

DP—-> 1. SNP
2. R3 (Planned independent requirement
RMDP – share-version-M
D001- Lux 100 —————-> Doo1 –LUX 100
Final demand ————> Forecast for SNP sales order
Demand + Safety – Stock on
Stock hand
1000 + 100 -400
Net = 700

Poo1 1. Heuristics
Poo3 2. Optimizer
↙ 3. CTM (Capability too much)
Product ↓
Line1 3methods which help u for find
The source
Heuristics works on priority basis disadvantage: It will not check capacity of the plant
Optimizer: It will do all the cost and capacity calculations It takes lot of time
CTM: How much to manufacture
DOO2 ——> 1400 (forecast)
Poo1 ———> 700 ——> Poo2(2100)——-> 1500 (D>S)—–> Deployment ——->Transportation

A: 2:1: ratio for 2 depots
B: On priority
FA sharing between 2 deport
If 3000 S >D

Push method for product to depot as the optimizer method store cost is more in plant than depot (eg)
PP/ DS: Will give U the detailed description of the product manufacturing

Done for only 10 days in evening minute it is detailed planning
SNP is tactical planning
PD/ DS is a detailed planning
CBF —–> Characteristic base fore cast
CFM —–> Customer fore cast mgt
Collaborative DP
Product split
BW: DSO —–> Data structure object
Multi provider
RUN SAP method dogim:-

To- be (After APO)
↓gap analysis
Go- Live

SAP Products:-
1. Business one
2. All in one
3. R/3 ——> R /3 Successes in integration
4. Business suite
Any Company as{1. Finance ——> (4)
2. Sales ——–> (3)
3. Material Mgt ——-> (1)
4. Production mgt –> (2)
5. HR ——-> (5)} R/3 functions
Importance of APO:-
Business suit has modules likes CRM
← ←SCM
↓ SEM —->[Supply enter price mgt]
Planning only ← APO ——-> DP —–> Demand estimation
Execution happens only in R / 3 System
We store the data in BW related to business storing, extraction and for reporting is more flexible in BW because will store the data in 16 dimensional table called fact table and R/3 is only 2 dimensional table
R/3 ————> BW
↘ ↙
DP—-> SNP Forecast released to SNP
SNP has distribution planning and supply planning
SNP has minimum planning in daily
PPDS has detailed planning in seconds wise, resource capacity, workers required, machine details
Output of SNP is input to PPDS
TPVS —–> Old module
TM is transportation planning & vehicle scheduling ITC & HNL
TPVS will minim the no. of trucks
GATP ——> Global availability to promise
Hange program is called Node
Big change ——> Patch
Bigger change ——-> Version (release)
Adjustment not possible in R/3
APO works mostly on make to stock ——-> keeping stock and then supplying
Customer durables: Make to order ——> Only after the order comes, the material will be produced
Client: Readies
HLL Under client ——> user will be there
1. Implementation ——> Fresh system preparation
2. Support
3. Rollout
We will fetch the history from R/3 and store the data in BW. It depends on the clients, for planning, we require history, that Y we fetch data from BW to APO
We fetch history and current data
Purchase order: From one plant to go down ie from manufacture plant to go down
Current data ——> Sales order not complete plant data, purchase order
The current data will go directly form R/3 to APO
Master data in R/3 ——–> Customer data
Material data
Vendor data
BOM —–> Main product & Sub –products
Machine / Man
Route –Sequence of operations
Business organization element:-

Company code1 Company code2
↓ ↓
Plant / DC ——————————> Plant
Intra Company
Stock transfer
Ready to used product is only transferred to APO not the unfinished goods
3 Types of data:-
1. Master data
2. Transactional data
3. Organizational elements (like plant)
CIF acts a bridge between R/3 and APO CIF will not work with other platforms like oracle and SAP APO
We have to create name for R/3 and APO to do CIF
Administration team (Basics) will give the names to R/3 and APO systems and the mapping between the filterining
Front end –SAP easy access (user access)
Backend —- SPRO —-> IMG (Implementation guide)
Land scrape:-
Development System: Changes or configurations
Quality system: Testing
Production system: It’s a real time environment
Client copy (or) Client refresh:-The production info is copied to the Quality & development system
Transport Management:-When a change is done in development system, then a transportation request will be generated with this request we will move to the quality
Each environment has a client number
100 Development systems
120 Quality systems
160 production system
Apart from these 3 environments, we have the sand box environment. It is used for practice system. It is a company system provided for practice purpose for my sack
Master data can be created in Quality but the configuration data is not created in Quality
* How frequents the client will take system for 3 month, 6 month refresh (or) copies
Master data is created in production system the master data that is present in quality is not the azurite data
To increase the performance of the production server, they will decrease the quality server size and increase the production serve
Data is stored in table i.e master data (or) configuration data (or) transactional data
KN A1 ——> Customer General Data
KN B1 ——-> Customer company data
KN VV ——–> Customer sales data
XDO1 ——-> Creating Customer
Tables are 1. Standard table
2. Structural table: Data will not be stored in this table only for organizing the data this table will be used (or) arrange the data in required manner
In APO, the data is stored in live cache & in tables
LSWMW- Legasy system migration wok bench for mass upload
APO will have the separate serve apart from R/ 3
[Dev]< --------- [Dev] [Quality] < ---------- [Quality] [Product]< -----------[Produ] CIF 1.Logical system Name 2. Assign Logical system name to client In Real time, Logical system involves development, Quality & Production server/client. In IDES, We have only one client for practice 800. So we map 800 (R/3) to APO () Retrofitted: The transport request will be moved to project team from support team called as retrofitted In Real time Project team Support team Land scrape X A Y B C C The latest changes will be available in project land scrape. Then the changes made in support land scape are not used. If 2 teams are working on same project like project team & support team. The 2 team will have 2 different lands scrape, the admin people will move the transportation request to the other server or clients SU01 -------> Creation of user id
SU01d ——> user maintenance
System —> Status ——-> to see the program as per the T. code
sUO1d:- In profile lab, sap-all means all the authorization given to the SAP consultant
1. Logical system Name
SAP easy access



Integration with other my SAP.com components

Advanced planning and optimization

Basic settings for setting up the system Land scrape

Name logical system

T90CLNT 090(R/3 system logical name IDES)
System name CLNT 800(In Real time)
Eg:- ECC CLNT 800


Assign Logical system name to client

800 —-> Client 800

Select the row ——-> details button


Specific SAP release

A Note ——> T code for note
Note ——-> change (or) new program for implementation
Patch ———> more than the note
Version ——-> New enhancement adding new topics (or) new module adding to the previous version
System Health Check: After shut down, and after restart, we do the health check

Set up RFC connections


Technical settings tab

Target host (or) IP address

Click on connection test

When doing health check, the connection test has to be performed in R/3 system RFC setup connection

Set target system and Q-type (Q—-> The boning of Master data from R/3 to APO for a particular custom (or)
↓ For a particular master data)
Qty pw: empty


Wait R/3 out bound ———> the Q will be waiting in R/3
APO in bone ———> the Q will be waiting in APO
I ——–> Inbound
Empty ———-> out bound
T-code –SMQ2 ——> Inbound (Standard program change will be done by SAP
SMQ1 ———> out bound company)


Integrated with SAP components

Integrated via
SM59 –RFC connections To see package of version system
ABAP connections ↓ ↓
↓ Maintain BSG connections Utilities
APO CLNT 800 ↓ ↓ Assign logical system to BSG from APO
↓ ↓ ABAP connect
Logon & security ↓ ↓
Release means version post processing errors in we can park T90 CLNT 90
The error in post processing ↓
Eg: R/3 < ------ APO Mat /plant Mat/Plant < ------- Purchase order If mat/plant deleted in R/3, then the Queue has to wait in SMQ 1 or SM2, for this type of error, they wait in post processing systems BSG:-Business system group (In real time the queries will be packed in APO in bound from R /3 to APO and APO out bound from APO to R/3) Chips –123M.no[R/3 1] ↘ [APO] ↗ Cig --- 123 M. no [R/3] As the material no is same and the description of the material no differe, as we are sending the data to APO in APO, we have to create BSGS for 2 materials 2 BSG’s Chips with BSG 1 Cig with BSG2 Data will bound and the data will be sent to APO in the form of Queue R/3 HPO Plant/ go down Location / Location type Customer } 1001 ---Manufacturing plant Vendor 1002 --- Distribution center gowdon 1010 ---- Customer 1011 --- Vendor PIR (Purchase info record) -------> Transportation lane
Plant /Material ———-> Product
Work center ———> resource
Work center ——> PPM /PDS
Integration model: What type of Master Data?
What type of transactional data?
It is available in R /3 only; it is not available in APO
Integration model is used for filtering data
For integration model, T. code CFM1 in R/3
1. Plants(Plant is created in MM)
Model name – Plant MM01
Logical Name –APO CLNT 800
Plnt: MM01


Variant Name: Plant- mm01

Generate IM

CFM2 —–> Activate the integration model by default it will take as production plant
Hot coding:-When a material is created, it is automatically added to the carient
It given empty in material,, then all the material, that are externally planned will go to APO.
All externally planned products will go to APO, which is maintained in material master data MMO1
MRP type —-XO (external planning)
Integration model is
1. Hot coding and
2. Maintaining other data
In CRMI & CFM2 {RIMOGEN, RIMODACT} are the 2 programs that are running at back ground CFM3- Activate (or Deactivated integration mode in back ground
Variant are used for back ground execution at the end of day
The views required for APO from MM01
1. Basic view1
2. Basic view 2
3. MRP 1
4. MRP 2
5. MRP 3
6. MRP 4
T- code to see & execute: the program SE38
Program: RIMODGEN —-> F8
CIF T-Code to execute the jobs- SM36 (Create a job)
SM 36 —– Create a Job
SM 37 —- To see the scheduled jobs
Master data is unidirectional R /3 (to) ——> APO
Transfer of data 2 types from R/3 to APO
1. Delta transfer
2. Initial transfer
Generally, we do delta transfer
Change pointer: When master data is created, for each and every field in the master data, change pointer is created for each and every field.
Delta transfer than, initial transfer, master data is done by initial transfer and the transactional data done by initial transfer will act directly performance
Directly execute recent integration model- Delta transfer initial transfer are done only on weekend, but the delta transfer are done every day. Initial transfers are done at day time, but the delta transfers are done at day time also
CFM5 — To see integration model name
Select plant —–> Choose plant ——> model tab
In R/3 to see tables ——SE 1/6
TO see Plant data —— T001 w
Technical name for Plant – WORKS
Technical name for customer –KUNNR
To add fields to the plant table data

Fields for selection
SM30 —– authorization for roles
In APO, SE 16 ——> /SAP APO /LOC /Location type: 1010
Node type —–> Godown

Distribution resource planning

Basic settings

Maintain assignment of node type- plant
Plant —–> Node —-> (In production system to changes are allowed in
Eg: MM02 —–> DC —–> Spro the SPRO changes will be done in development
Queue Name for CF —-> CF * Development system No configuration changes in
/SAP APO / MAT 1—-> TO see product in production system)
In initial transfer, 1st we have to active the existing transfer and then activate the recent transfer, In delta transfer, if we activate the recent integration model, the old IM will automatically get deactivate
Delta transfer —–> the changes only will go to APO
Initial transfer —–> if APO is not getting the material
So we have to do initial transfer
Initial transfer is required only when changes happened in R/3 system
In initial transfer are required only when changes happened in R/3 system
In initial transfer, we have to deactivate the executing integration model and then activate the recent integration model. For transactional, data not recommended to do initial transfer in day time because, the transaction data means sales orders purchase order, when doing initial transfer in transactional data, the performance of the system decreases as well as /SAP APO/ SP1 what orders or send R/3 and what orders not to send to R/3 for that publication type is use in APO publication type is an external procurement for purchase orders/ Purchase requisitions
For manufacturing plant, we have maintain external procurement, in-house production and sales in publication type
CFM1 —–> Create integration model
CFM2——>Activate (or) Deactivation I.M in Back ground
CFM3 ——> Activate (or) Deactivation I.M in Back ground
CFM4 ——-> Display integration model
CFM5 ——> checking the integration model each for product in integration model
CFM6 ——-> Change I.M
CFM7 ——-> Deletion of I.M
Log is only maintained only for 15 days
RIMOD DEL program for deletion of CM
SMQ 1 —–> outbound queue
SMQ2 —–> Inbound Queue
If Publication type is not maintained in APO, queue will not be generated
SMQ3 —- Parking the errors queues
SMQ2 —–> edit —–> Save LVW
Ready Queues will not go to other system, so for that we have to activate that queue for that
Unlock icon ——> activate
SMQ3 ——> after the Queue is resolved without error —-> edit ——-> restore LVM’s
CPP-CIF post processing —– It as to done every day by CIF consultant

T. code
The Queue will go and wait in CPP instead of SMQ1 for error handling.
For product in DP ——> Planned in depend requirements
50000 —— 9000158 planned orders
50001 ↗
Transactional data floes from R/3 to APO and APO to R/3 (Bi directional)
Master data flows from R/3 to APO only as we are not creating a Master data in APO
Eg: APO /500 kg
R/3 2oo kg
300 kg
If 500 kg is required for a godown by today or now 1 as we rin in APO the orders will be sent by tomorrow as the job will be run at night, so for this we create for 200 kg in manually in R/3 and that manually created orders for 200 kg will be sent to APO and at last it will create order only for 300 kg in APO
Plant to plant transfer (or) Stock transfer orders:-
Stock transfer order ——> Delivery —–> PGI —–> Goods receipt
Eg: 1000 pieces —–> 1000 pieces —–> 800 pieces —> By GR the godown will add the goods to godown
Customer Transfer (or) Sales:-
Inquiry —-> Quotation —–> Sales order ——> Delivery —-> PGI —–> Billing
Vendor—-> Plant:-
Plant will raise purchase order ——-> GR
The future planned orders that are created in APO will have come number range that starts with ‘9’ this planned orders will be sent to R/3 and in R/3 that orders will have different number range assigned to that orders. So in R/3 that orders will assign their number range and after transferring to APO that orders are which have APO number range will be replaced by R/3 number range when the orders are saved in APO.
CFG1 ——-> errors data in APO and to R/3
Application Log
R/3 ——> CFG1 —–
CPP ——> It will allow only one user
CPP1 —–> Multiple user access to login
When doing back ground job, the queues that are having errors will be stored in CPP and the remaining queues will go to R/3
CFG1 —–> The error that we get in CPP of APO is not clear, it gives only message in APO so if we go R/3 —–> CFG1 (It will give the exact application or in R/3 error)
SLG1 ——>Application log in APO
↓ ↓
Object: CIF

Only very important logs

Give date range


User name:

Unlock icon (To lock the user)
Target system: T90 CLNT090 In house production

Planned orders
Obsolete:-If the delivery data is passed (or) the delivery data is yesterday, we have to the permission from the business and keeping the Queue in absolute. Obsolete means removing from CPP queue, If the old queue and do it obsolete deleting the queue from CPP
/ C / SAP APO /CCR ——> compassion and reconciliation of transaction data
It is used to check the difference between the R/3 and APO CCR is used to compare the R/3 and APO
EG: An order is created in APO and R/3 didn’t received that order, for that we have to run CCR, by that we get to know where the order is there , by that pass the order to CPP from CCR
Eg:- If we are not able to see the queue in APO, R3, SNP1,SNP2, then the problem is publication type is not maintained
Different types of queue status:-
1. Ready: We have to activate the queue (or) we have to unlock the queue by unlock icon
2. Running:- If Queue is running status, we can not to do anything i.e any changes to queue
3. Waiting:- If the queue is in waiting status, we have to double click the queue because
That queue is waiting for other queue, after 7 times double clicking, and then it will through an error for this we have to go SMQ1 and check the queue position there

1. Waiting
2. Waiting
3. Waiting
4. Waiting
5. Waiting
6. Waiting
7. Waiting not to do click, we have to copy the queue and again go to SMQ1 and check the queue also, then check the queue, if you see queue in ready status, we have to activate the queue, then all the queues will be executed
SMQ1 is the general transaction before the post processing
4. Completed:- The queue completed
Error queue status:-
1. Sys fail
2. No send
3. CIF Stop
/n/SAP APO/ CP3 – Publication type
SE/6 ——-> Tatc ——> TO see transaction codes for given transaction code eg: /SAP APO / CP*
St22 ——>
Based on the size of the company the plan for levels
Product/ Brand / division / segment / Location / Brach / Region / Country/ customer/ DC /Vendor / Plants
These are called level based on this levels, the client will decide to plan

Eg:- Food(segment) (higher person)

↓ ↓ ↓
Snacks Biscuits Ready to eat ——>Division (regional person)

Lays ——>Branch (Branch manager)

Tomato Limon/ chilly ——-> Products (Sales executive)
5 to 40 max characteristic
Characteristics means at level u are going to plan
Most of the organizations will plan from godown level not the customer level
Product Brand Division Segment Location Branch Region Country
Tomato Lays Snacks Food HYD Ameerpet South IN
Product——–> Characteristics
Tomato ——–> Characteristic value
Characteristic value combination (CVC) ——-> combining all values of the characteristics
CVC is unique
Us army ——–> 512 GB RAM
IT ————> 256 GB RAM
Finacor is application used by banks
Values (or) Quantity and times are stored in Key figures:-
Fore cast, manager forecast, corrected forecast, Branch manager fore cast, consensus fore cast, sales history key figure are the different key figures
By applying some strategy we get the fore cast value
The fore cast key figure is changeable by coping the fore cast KF manger fore cast key figure R/3 to APO sales is stored in sales history key figures.
For each CVC, key figure is attached
IPOS —–> Master Planning Object System
Safety stock is measured in quantity (or) in days
MPOs will have different characteristics
MPOS will controls the planning
In further, if any characteristics has to be added to the existing characteristics, 1st we have to take backup and then deactivate the MPOS, after the deactivation of MPOS, all the CVC will be lost. We then add characteristics
Key figures are available in planning area
Planning area is contains data
/SAP/ APO/ MSDP-admin- for MPOS creation
Characteristics starts with ‘OP’ are BW characteristics
Characteristics starts with ‘9A’ are APO characteristics
9A Brand —— Brand
9A Cust- No —- Ship-to-party (customer)
9A /Loc no —– APO Location
9A MATNR —- APO Product
SAP easy menu




SC planning


Basic setting (Se93-Creation of new transactional
↓ Codes
Data ware housing work bench Se16 – Data browser to see location)

Continued on data 20/3/2013
Characteristics ——-> MPOS
(or) CVC’S ↓
Key figure ————> PA ← Storage bucket profile
↓ ← Unit of measure
[Planning book/Data view] ——> Planning bucket profile
“MPOS is a cube”.“ CVC’s are the master data “available in DP we use only CVC’s in DP
Storage bucket profile:-1. How many years data storage required?
2. How do want to store the data i.e, weekly, monthly
In DO, the minimum planning is weekly period is not a week
[] Daily
[] Weekly
[] Monthly
[] Quarter
[] Year
Period is not a week
Period — 1-7
Planning — 8-15
23- end of the monthly
In DP, period planning also possible
If monthly planning is done, we cannot disaggregate the planning in weekly
*Mandatory is weekly (real time)
Unit Q measure:- In which U measure , In which way the measure is planned
Eg:-(E 19)
Basic unit of measure is which they are measuring the products
*How the unit of measure is extracted from R/3?
Global settings {Except Unit of measure, Factory calendar}
All other setting will be cifed from R/3 to APO
1 each 1 bottle or 2 bottles we maintain conversion factor in material master in R/3. When cifing the material master from R/3 to APO, the conversion factors will also CIF
Planning Book:-One planning book is having data view. Without a data view, planning book cannot created
Planning bucket profile:-How the
*DP —–> Weekly monthly for interactive purpose one planning book
Manual change in planning book is called interactive
For Back ground purpose, one planning book
Planning in 2 ways:-
1. Interactive —–> In the planning book
2. Back ground —–> Process chains by linking jobs
Back ground job are done at night time
To create space for the future month (or) week
If initialization is not done, then 12 month data will not be stored
For short term data view and long term data view we have to create 2 different data view, if not it will affect the performance
In SNP, the days will be 180 days for planning
Continuation for date 19/3/2013
↓ (key figure & characteristic are info
Info object objects in BW)

RC on info object

Create info area

Info area: HLL-inar

Select the info area

RC on info area ‘HLL-inf’

Create info object catalog

Info object: HLL-Char1

Consistency check then

Package: stmp

Local object


Same way create key figure HLL-KEY

RC on HLL-char 1

Create info object


Select APO

Save (In real time, they create, the characteristic
↓ with ‘Z’ set 6——> Table: TSTC
Date type: CHAR T. code: Z* ——> these are customized T.code
Length: 10 The planning will take place depending
↓ upon the unit of measure mentioned
Activate icon in planning area)


Same way create HL- DIVISI
HL- Branch
HL- Region
HL- Country

In same way create key figures HLL-sales

S & DP administrator (/SAP SPO/MSDP-admin)


Create planning object structure

↓ (In APO, also internal BW available, so
HL-Brand in MPOs, the characteristics value starting
HL-Branch with ‘O ‘ appears
HL-Country When MPOS is create, a cube is created)
HL- Region
9A Matnr
9A Loc No

Activate icon


Char. Combination


Create charastictic combination

*Create manually
[√] Adjust time series objects

Create button

SAP easy access (Consistency check for MPOS)

APO administration

Consistency check


Consistency check for planning object structure

Select check
Select condition
Grouping condition

Program —-> Execute in back ground
Output device: LPO 1

ERROR:” Live cache anchor not found” for that we have to do MPOS consistency check
SM37 —–> Check the job (or)
Monitoring jobs

Create storage bucket profile (/SAP APO /TR32)
Easy access SPro




Current setting

Periodicities for PA
[√] week
[√] Month
Start date: 1.1.2011
End date: 3.12.2016

Creating planning area
/SAP APO / MSDP-admin


Create planning area

SBP: HL-storage


Details icon

Key figure aggression tab

Fore cast: P (Based on different KF)

Locking logic

Select all

Aggregation and disaggregation will depend upon the calculation type in PA (Key figure attributes tab)

Activating the PA by RC on HL-PA

Time series object

Planning version: 000


SAP APO / SDP 8B —–> define book

HL-Book —–> create button


Select all bring from PA to PB
Select all bring PA to PB —->

Data view: HL-Month
Planning start: empty (current date is the planning date)
20.03.2013(It will start planning from the given date)

12 months
12 months



For interactive planning book
In interactive planning book, in design model we can do any changes to the PB in work space (or) in Live mod we cannot do any changes to PB
Time bucket profile: HL-12 month
Planning bucket profile 12 M
2 W
2 T(days)
*If different key figures — we can create, DV
If similar key figures —— we can create DV
*How many PB Created under each PB how many DV?
For interactive purpose —–1 PB
For Back ground purpose —-1 PB
For Data backup —– 1 Planning book
—–eg: D. Reddies
For each planning book, monthly and weekly data view monthly planning is for estimation purpose of the demand
Weekly planning —- 1 year
Monthly planning —- simulation version
Versions ——-> Active version (1000) — whatever planning is done is used for execution
Versions ——–> Inactive version (001) —–> While not be published to R3 only for planning purpose
Inactive version is also called simulation version
We version, the planning results will be transformed to for execution. The data is copied from active version to inactive version. The fore cast will not be copied from 000 to 001 only the data and transactional data will be copied from 000 to 001
Long run planning is done in Inactive version
No long run planning is done in active version
In active version is copied to in active version of SNP similarity active version to active version
Inactive version data is stored in BW for reporting purpose
Info cube Modeling (or) Data Mart:-

Info cube: where U are going to store the data feis final
In BW, we store the data in info objects
Data source is the replication of Source system

Source system can be R/3 , excel, APO
Info cube consists of 16 dimensions, out of 3 are standard and 13 are user defined source system can be APO, in the sense used for backup in BW then source system is APO and target system is BW
For reporting purpose info cube is used in BW
For reporting purpose, info cube is used in BW
BW stores data from non-SAP
Info provider is the provides, Info cube is available in info provider
Info package and DTP steps will be there in process chain
Transformation means mapping of data source field value to info cube info object
Data stored in data source is in PSA tables
[Info package, DTP, create CVC & load data steps will be there in process chain (every week)]
When CIFing the material, material is created as material /Location, but CVC will not be created
PSA: Persistent Staging area
Reporting and extraction is not possible from internal APO-BW system. From R/3 also we can fetch data to APO-BW so far reporting & extraction, separate BW is required
T.code RSA1

Creating source select source systems

RC on source systems

Select source system

RC on source systems

↓ (KNFIVV-combination of general &
Select file system sales data for customer master data
↓ Material:-
LN: HL-sou sys MARA- Material
S.S: HL-Sou sys MARC-Plant specific data
↓ MARD-Storage location
Save MVES- sales order
↓ VBAK -header
Under file HL-sou sys VBAP -item
Create data source ——> Select data source VBEP –Schedule unes
↓ Route data:-
From file icon TVRO-Route data
File —-> HL-Sou sys
RC on date source name

Create application component ——> Name HL APO comp —–>

Structure is nothing but combining different tables (or) table joining. The structure is designed as per the requirement structure is also a table, but it a customized table. Structure is not defined by SAP. We have to map the structure as source system structure is designed by ABAP’s
SE16N –Customized T. code to browse the data of tables
—–> SE16 & SE 30 for table data changes
In real time, only certain tables can be accessed through SE16N. The tables that are mapped to SE16N are only access able
T. Code: SQVI ——> TO join 2 different tables at a time
SQVI ——> Normal Quarry
SQ01 ——> ABAP Quarry
V lookup: It is used to compare the values in true (or) false mode
In Excel:-
Eg DP fore cast SNP wrongly uploaded vii
A 10 G 10 =V look up (F2, AB, 2,0)
B 20 O 10
G 30 J 10
J 10 A 10
T 45 B 10
I 78 T 10
U 95 I 10
O 45 U 10

=UU /= G2 =H2
SUM-Sum (Col number + Col number)
=Concatenate (A2+B2)
Result will be A10

HL-AP comp

RC on HL-AP comp

Created data source
DS: HL- Data source
Data type: transactional data


Genera Info: Descriptions only
Delta process: Full up load (For file eg: excel)
File name: C: / HL-file CSV for R/3 it is paseial upload
Header rows: 1
Data format: separate with separator
Data separator:
Escape sign:

Proposal tab
Load example date


Fields tab ——>
Create file: MC62


Display characteristic

Down load

Local file

Spread sheet

Name: HL- File.XLS

Excel File:-
APO Location Product HL-Branch HL-country HL-Division HL-Regio Date
HYD COL 100 SR Nagar colgate IN TP south 092012
“ “ “ “ “ 112012
“ “ “ “ “ 122012
“ “ “ “ “ 012013
“ COL200 “ “ “ 022013
Sales VOM
100 PC
200 PC
300 PC
400 PC
500 PC
600 PC
Select date and FC —–> Format ——> Text
Save the file in CSV (Command Delimited Format)
——> Date: Cal month When loading the excel, the excel file should
↓ be closed
Preview tab
Read preview data


Go to Info provides


RC create info cube

Name: HLL-Cube
Info area: All-INAR

Create icon

Select BW
↓ 3 standard dimensions
Dimensions 1.Data Package
1. Data package 2. Time
2. Dimension 1 3. Unit
( Dag and drop from info HL-Branch
Object catalog icon) HL-Countr
HL- Region
Drag and drop from all object ——-> APO product
APO Location
9A Version
Catalog icon key figure——-> HLL –sales
Of charaterictis 3. Time
↓ 4. Unit – o unit ——–> applies when
Navigation attributes are mainly uses in SNF for location
In TLB —–> we have to define source location and destination location and means of transport are added to SNP MPOs

Then consistently check


Package as $TMP

Local object

RC on info cube

Create transformation

Object type: Date source
Date source: HL-Data source
Source system: HL-sou sys

Create [√]

9A version ———> RC

Rule details

Rule type: constant
Description: 000

Transfer values button

Consistency check


Package ——–> Local object ——–> Save
From R3 to APO cifing ——–> default is 000 versions
But from BW to APO———> we have to select the version 000 or 001
• Green color —–> active
• White color —–> Inactive

RC on data source

Create info package
HL- Info pack


Schedule tab


Monitor icon [√]

PSA [√] —–> TO see data in data source

RC on Info cube

Create DTP


Extraction: Delta
Update tab
Error handling: Valid records update, no records


Execute tab
Execute icon


Easy access




Data administration

Load data from info cube SAP APO /TS cube

Info cube: HLL-Cube
Planning version: 000
Planning area: HL_PH
Version: 000
From: 01.09.2012 to 29.02.2013

In real time, we load the data from external BW to internal BW of APO, then from internal BW to planning area without external BW we can load data to internal BW of APO from R/3

Key figure ——> Key figure assignment HL-sales to HL-sales




Save as variant (Load test)
By assigning parallel processing profile, the performance of the system wills pickup



Generate immediately

Load data from: Info provides
Info provides: HLL-Cube
Version: 000
Date from: 01.09.2021

Adjust time series
↓ (In real time CVC’s creation after DTP and then load execute Data to PA)

AL 11 ——> Application directory (File keeping place) we can load from excel to directly to PA
Ctrl+ F ——> to find path for given T code o for given name
Master fore cast profile: It controls the fore cast
These are maintained in master fore cast profile:-
1. How much history period
2. What is the key figure to read?
3. What is the version?
4. Once forecasted: in which fore casted value has to be stored
5. How much period fore casting has to be done
6. Which planning area
In a company, each and every product will be categorized into A/ B/C classification
Implementation in MFP:-
At client side, they have fore casting experts these experts will be provided with all year’s history if no fore casting experts, then DP consultant will decide the technique
The experts will apply the technique on the history for fore casting, if the error percent is less, then that technique will be implemented by the client
3 Types of Techniques:-
2. MLR
3. Composite
1. Univarient: It depends only on history
Single variable is history only most of the companies will use univarient technique only
If given dates in future & history horizon ——-> It will not roll the month to next month so we use periods
Univarient Technique
It has 6 methods
1. Constant method
2. Trend
3. Seasonal
4. Seasonal
5. Automatic
6. Croston method
1. Constant –Method:- Much division will not be there in sales
Eg: *——–*——-*——-*——–*——-*——
100 105 102 103 104 100
2. Trend Method:-Some growth will be there in sales by monthly (or) yearly

We will take more data i.e. 3 years (or) 5 years history for deciding which fore casting technique has to be used. If applied seasonal method for a product, system itself will through error as the history is not enough.
4. Seasonal Trend:-Business is seasonal and in that season also we are following the trend

Trend can be a division in upward or downwards is sales
5.Automatic: In automatic method , when running the fore casting profile 1st it will run constant method, then trend, then season, then seasonal trend
Most of the company won’t use automatic method
6. Crpston Method: If data for doing the fore casting, is less than 60% then the fore casting result will not be accurate
For history > 60% then crpston method is used
Reaching 80 % ——> excellent planning
Below 80% ——–> best planning
The planning is done in classification (ABC) of product
The planning is not done on product based
Eg: One product fore casting is 80 %
Other product fore casting is 50% then we can use trend method, because the forecasting is done on their product history only before forecasting, we will classify the product, for food we use constant method in constant method, we have 2 averages
1. Weighted moving average:-
Recent history given more weight, less weight age to last history or data points
2. Moving average:-
Last 2 months average
1st month: 140 130 115 140 170 150 170
Weight age: 10% 10% 10% 10% 20% 20% 20%
: 14+13+11.5+14+34+30+34
Difference between last 2 months
2. MLR [Multi Leaner regresit]
Taking into history and along with that w have other conditions also that effects the business
Eg: Political conditions, climates, taxes
3. Composite:-
Combination of both univarient and percentage of both techniques MLR is Composite
Easy access



Maintain fore cast profile —-> SAP APO / MA 96 B

Master profile: HL- Mst prf
Fore cast KF: Fore cast
Period indicator: M
Fore cast period: 6
History periods: 6
(Pasting period depends on client requirement)
Eg: Jan 31
1 – 7
8 – 14
15 – 21
22- 28
29 ↘
30 → 5th Week A
31 ↗
1 ↘
2 ↘
3 → {6th week B}
4 ↗
APO—-> SC planning
Univariate: HL-MST PRF

Set the model

Profile: HL-MST PRF
KF: HLL- sales
Version: 000
Fore casting strategy: 20

Consensus based fore casting:-
Discussion between who is going to do business and the higher person
Dis-aggression: The value is divided into lower level
Aggression: The change in value and combine the value to SM

If the consensus fore casting is done, the release to SNP is 4 days for that the fore casting is on from 25th of every month
*If mar 31 is the lasting day of the month, then for that also planning is done, to skip and add in last month offset is used to skip on month is maintained in offset if maintained one day, then skip that day
Eg:-Mar31/ Apr /may
Extrapolation:-If offset is there is offset we use extrapolation for the fore cast, we require the month data to fore cast
Eg:-If I am in 4th week of month, for forecast I requisite entire month to fore cast, but I have no 4th week history for that I copy the 3 rd week history to 4th week as history we having planning book, data view table 1 and table 2
Super user:
User: Client side employee
1. Production user
2. Category user
Normal users will not the authorization to have the tickets directly. Then super user will have the tickets and then send to user
In real time, we have 10,000 easy accesses




Selection organization
SAP APO / MC77 Maintain selection assignments
Only DP guys will have option to assign the profile
SUO1- User maintenance
SUO 10- User roles
A trend method can be at one time it can be become constant
Table 1 and table 2 in data view is used to split the key figures
Key figure description is planning book specific hot the data view specific
Setting fore cast to non- editable mode
R con fore cast key figure in design mode ——> selected rows —–> Output type
If quality server, if wanted to any changes to non-editable fore cast key figure change to input /output type and in SNP only product & Location planning
Disaggregation method
Is the SAP standard proportional factor key figure
Proportional factors:- How to distribute the values, if the values are not there in proportional factor key figure, then it understand that all the values are same
Eg:- PF
1000 333
Select the manual proportional maintenance in planning book 1st screen
Pro-rata: As per the history, the value is distributed
For on I and P, APO DPDANT is given
Easy Access




Calculate proportional factors

PA: HL-PA [Ctrl + Y to copy product to text
↓ Ctrl + V —-> for only 8 visible entries
Execute upload from clip board —–> Load all
Basic for PD↓ the data
PA: HL-PA eg: Note pad
Version: 000 1 5 9
Key f: HLL-SALES 2 6 10
Period: 01.10.2012 to 31.03 2013 3 7
Cal proportions 4 8
PA: HL-PA Ctrl +V Clip board
PVER: 000 1 1
Transfer proportional to:- 2 2
From: 01.04.2013 3 3
To 4 4
31.12.2013 5 5
↓ 6 6
Generate 7 7

I-Calculation type —————> 1st time it acts as P and then according to cattiest the percentages distributed it is mostly used for cast 55 (mandatory)
I-First time Q after that latest proportional
Eg:- Fore cast value 500
A 40% 200 250 50% 275
B 60% 300 250 50% 275
In consensus based fore casting, we use ‘I’ Calculation type
Consensus based fore casting means the meeting held between the manager and the sales executive about the target sales. If one executive, says that we can do 200 instead of 250 the other 50 will be adjusted to then other person that is called consensus based fore casting
In consensus based fore casting, we will not change the fore cast value we will apply ‘I’ calculation type
System generated fore cast is in manager fore cast key figure will contain the copy of the fore cast key figure
In PA, key figure attributes
KF1 – I – Apodp dent
KF2 – A (average)
KF3- N (No calculation)
Fore cast –P- APODPDANT
In active planning book, only required fields has to appear in work area – key figure selection —-> multiple key figure
Select manager fore cast
Fore cast
Proportional factor
Then we can see only these 3 key figures in the work area
(A) (B)
75 + 125/2 =200/2 =100(not applicable)
100+100/2 =200/2 = 100 (applicable for average)
Calculation type Key figure Total 100
A (Average) Additional A 100
Key figure B 100
If total is 100, then it will give equal values to the item the other formula
75 + 125/2 = 200/2 =100
Is not applied to the items
For ‘N’ (Calculation type) –No aggregation and No disaggregation
‘S’ —Pro-rata
The disaggregation is equally distubition
‘D’ — At the disaggregation at lowest level the aggregation will be done
MACRO’s: Calculation will be done and store in Key figure
Cop fore cast —–> to other key figure
If else conditions
Functional module we can use in
Multiple places (advantage)
Macros: Types of macros
1. Start
2. Default
3. Level change
4. Exist
5. User executable macro
If the macros is assigned to any macro from 1 to 4 then it is automatic, if not assigned, it is called user executable macro (Manual execution of the macro)
1. State: Loading data into planning book the macro will work
2. Default: When loading the data or changes in the values of PB in any level, then default will work
3. Level change: If any level changes, then level change will work
Eg: Branch eg: product load in PB and then product is drilled down by
Level1. Product location, then this will work
Level2. Location
4. Exist: when we are coming out from PB, the exits macros will work
This macro is used for properly save the data in live cache
Macros —-> IMG



Basic settings

Define macro —- (/SAP APO/ AVM)
Macro is data view specific not the planning books select the data view HL-Monthly

The screen is Macro work bench
*Once the macro is activated the macro is activated the macro will be parked from in depot
*If the macro or a step deleted will go to clip board

Macro looks like:-
The Macro has 4 steps
1. Macro defining the macro name
2. Step (The iteration will be maintained)
3. Result:
4. Argument (or) Calculation
*In view point of view
1. Types of Macros
2. Steps in Macro
5. User executable macro: This macro is not assigned to any type of macro it will execute as user executable macro in PB
Step:-Drag and drop in work space
D: Copy to manager
[√] No confirmation prompt [Collective macro are used when U
(*) All planning objects want to execute the macros in Sequence
(if this is set —> [√]Do not display initial value maximum macros for execution in collective
The zero) ↓ macro]
Continue Macro:-
↓ 1.User-exitable macro —->
Drag and drop from elements (Step) [Information prompt is used in user
↓ Excisable macro, but not in back ground
Screen macros]
(If total is used, (*) User defined 2. Background
Both past &future from period: 01.04.2013
Will be calculated mostly TO period: 31.12.2013
Used is future ↓
Read area: Drag & drop row from element to Row consist of key figure so
Workspace select the key figure

Row: Manager fore cast
Calculation: 01.04.2013 start
(*) Whole table
(*) write in boundary value
(*) No Value

Row (Create next level)
Fore cast
Macro Now:-
000 copy to manager
—–> Row: Manager fore cast
Row: Fore cast

Checking consistency


Park the macro in dept


Go to planning book
Absolute Macro: The macro will replace ‘0’ with changing additional key figure cast in PB
In the PB, we can see the macros used key figures with different symbol
1. Maco name
Consensus fore cast

2. Step: Name: Consensus forecast


Condition: Consenter fore cast

Control statement

If —–> Continue

Condition: consensus fore cast
Manager fore cast > Fore cast




Manager fore cast


Opened —–> fore cast
000 Consensus fore cast
——> Consensus fore cast (9 iterations: 09.04.2013; 01.12.2013)
[] If
⌂ Consensus fore cast
□Row: manager fore cast (from 01.04.2013)
□ > =
□Row: fore cast (Fm 01.04.2013)
Row: consensus fore cast (From 01.04.2013)
Row: Manager fore cast (From 01.04.2013)
Consensus fore cost (From: 01.04.2013)
Row: Forecast (from: 01.04.2013)
Row ————–> End if
Life cycle planning:-
Manual transform request creation for DP & SNP an option to create transportation request for planning area and planning book only one person can change the macros, even the macro work bench is accepting the other user to allow changes
Launch —–> growth —–> maturate ——> declay
Product Life Cycle in DP:-(/n/SAP APO /MSDP- FCST1)
If launching new product, the similar old product history is referred for fore casting
If the launching new product and having no similar to the launching product, the server is conducted and manual estimate is done for new product we will not copy the history of the old product, we will only reference the old product history referencing the old product history percentage is called Like profile.
This like profile is assigned to new product
In like profile we maintain how much percentage of history must be referred
Phase-In: Instead of referring the old product history for 1st time with minimum manual fore cast we will increase the product fore cast in percentage by month wise
Eg: 1st month – 10%
2nd month – 20%
3rd month – 30%
4th month – 60%
5th month – 80%
In phase-in also it will refer the old product history
Fore cast is weekly work
We will decrease the old product percentage and increase the new product percentage
Old Product
1st month—–80%
2nd month —- 40%
3rd month—-20%
4th month —- 10%
After new product percentage increases, until the stock is cleared, we won’t delete the old product
New Product — Predecessor
Old Product — Successor
If the demand is coming for new product and supplying the old product for clearing the stock of old product is called interchangeability
Easy access




Life cycle planning.MSDP-FCST1

(*) Basic setting



9A MATNR ——> Close —–>Back
Edit —–> Assign product / Location
Eg: Product: Z –Product
Location: Z—Location
If this assignment is not done in MPOA, then we cannot do life cycle planning and release
—–> Like profile button

Like profile: Like < 200 Like profile definition Ref Values Action % LUX-100 S 100 ↓ Save ↓ Back (If CVC don’t exist, no life cycle planning for new ↓ product) (*) Assignment ↓ APO product: LUX 200 Like profile: Like < 200 ↓ Select ↓ Generate ↓ Back For doing life cycle planning to new product, the life cycle planning must be active in master fore cast profile (*) Basic setting ↓ Phase- in button ↓ PA: HL-PA Time series: Lux-phasein Des “ Start date: 01.04.2013 End date: 31.08.2013 Period: M Maintain values:- Period Values 04.2013 10 05.2013 30 06.2013 40 07.2013 60 08.2013 70 ↓ Adopt ↓ Back ↓ (*) assignment ------> generate

Assign phase in profile Lux-phasein in assignment


If stat date and end date is maintained in master fore cast profile then w have set the offset option, if period is maintained no offset option is required
ERROR:-No version mapped or assigned this is because the version 001 is deinitilized, if from and to is know, we can do re initialized
Inactive version (001) is used for reporting and analyzing





Target PV: 000
Category: FA(Fore cast )
[√] add data eg: Hydf—–>1.UK1 50 2. USA 100
From data: 01.04.2013
Product: COL 100
Location: * —->
DB02- Basic T. Code
2. Flexic table
Used only foe calculation used for back ground job. It will automatically refreshed
Error: TO see errors in J back ground jobs SM37
St22 ——> ABAP runtime error
To see the exact of the error information
Deletion of Fore cast:-
Category: FA, product: Col 100, location Hyd1
—->[ extendeck]
Product characteristic: 9AMATNR
Location characteristic: 9ALOCNO
Requirements strategy: 20 the fore cast is consumed
[√] Results log

Fore cast consumption strategy:-
Eg:-forecast —–100 requirement
Sales order for 10 came
Then the forecast has to reduce to 90 and the total is 100 with 10 requirements
The location / product master data must be available in SNR for planning but location/product master data is the or not doesn’t matter in DP
// SM12 —–> Locking the entries//
Error:-the product COL 100 for location HYD1 of 000 does not exist for this error we have to create (or) if the location/product master data
SAP APO / Mat1 ——-Product
Product – Col 100
Location — Hyd1


Maintain other unit IPC, IEA


Assign model button

Select 000
Assign brick —-> save
When creating master data manually, the master data is not assigned to any model or version if we CIF from R/3, the master data will be assigned to model or version
Model is assigned to live cache
Live cache is there in data base
/ Sap APO / SNP 94 —–> we can see fore cast in SNP
Interview Questions
Jobs, copy of jobs
Process chain
In DP, most of the companies use process chain
Job Process chain
1. Step –by-step at a time only one 1.Step and step at a time we can run so many
Process can be run process at a time
Eg:- step 1 start
2 ↓
3 ↓———————↓
4 A B
5 ↓ ↓
↓——–↓——↓ ↓—-↓—–↓
1 2 3 1 2 3
T. Code: process chain RSPC
Easy access




Maintain process chains

Create button

Process: HL-Process
Chain HL-Process (Process chain will start with start process
↓ start name must be unique)


Process varients: check-HL-start


Click[X] button

SCM-demand planning

Generate CVC

Drag and drop on fight side

HL-create CVC


Program variant: [*] change
Process variant: It is used to name the particular step
Program variants: Real variant
Variant is nothing but the selection of data
eg: Variant is like favorites
Variant is the higher level, within the variant
We specific selection id

Create CVC screen
Generate immediately
Load data from: info provider
Info provider: HLL-cube
Version: 000
[√] adjust time series objects

Variant: HL-CVC gen


Load data from info cube

Load history
Variants are 1.Dynamic variant
2. Normal variant
Dynamic variant means automatic update
Eg: date from & to

Program variant:

/ TS consc ← Time consistency check [Start/HL-Start]
Calculate proportional factors ↓
Variant Name: HL-Proportional [Generate / HL-Load CVC]
↓ ↓
Dynamic Variant [Load info cube/Load history]
↓ ↓
From date Selection variant: D [Calculate proportional/
Name of variant: Current date- 13 days HL-proportional]
To date: Current date + 180 days ↓
Current data+/- ? ? days [DP back ground processing/
12 HL-Job]
DP back ground processing for fore cast
Creating activity
Define activity for mass processing
Activity: HL-act
PB: HL-monthly
RC on start button to

Display variant

Change icon Time system
↓ ↓
Change sections Status
Real time process chain must be created in back ground
User —-> RFE user
SM 37

For scheduling the jobs
SUO 1 D: RFC-User
Process chain


Execution user

Current user
In realignment
Over write-M } —> copy logic
100 200
70 230—> Add
30 —> over write
Copy logic over write is used in history copy percentage
Copy Process chain:-
Select the 1st process chain

Process chain


Give name


It will give error as same start

Then remove the link and

Remove the start process
Again add start process

By default the process chain created will be assigned to not assigned link
To assign the process chain to FO-ZBA-FCST
The click on ∆+ icon

Select 2 BA-FCST

SM62 – event history
SM60 – Display control job list SM/6
Event is a condition, In event we can ↓
Specific time and also other job TSTC
Event creation ↓
SM62 ——-> Back proc event

Create icon

SM 37

Select the scheduled job

*eg: If 100 products

Dependent Job ——-> Fore cast job
ControlM —–> Job monitoring tool
In that tool we can keep file watch’s
AL11—-Application directory
File watches
If the job has to start 8 pm, it will check AL11, if the file exists, the jobs will be executed other wise the job will be stopped
To reduce the job running time, 2 options:-
1. Parallel processing profile
2. Basis
Parallel Processing Profile: If a job triggers, the locations of works pace to the job. In parallel processing
Profile, 2 or more job parallel processing profile, 2 or more job can run at a time setting up parallel processing profile is easy, but test with different values and see which value takes less time for the running of job, then value is set to the parallel processing profile



Supply Chain planning



Define parallel processing profile

Parallel-generators is used
As server group in real time also [Mat logs/Clean up
↓ activity]
Maintain and then save Clean up activities will take 2 to
↓ 3 months
Go to proportional factors screen

Other setting

Parallel processing profile
Manual transport Connection for SNP and DP:-
For work bench, we will not have transport request
SE 10
To see transport request
[√] Transport planning book
Planning area HL PA
[√] Transport planning area
Planning area HLP
[√]With fore cast profile


Create icon

HL –PA-transport- 16042013(00277)


SE09 —–> Display

Select the request no and click on track icon for release now the task is release to general
Solution manage tool:-
1. Transport request mgt
2. Documentation
3. Functional spects
4. Technical spects
SM7 –HP – Ticketing
Remedy – Ticketing tool
SAP help desk
If solution manager tool, is used means we can release directly from development to purity but in sap when the request is released from development, the basis team as to release the request to quality server



Supply chain planning


Basic setting

Maintain manual transport link for DP/SNP
Mostly Used:-
Planning area
Planning books
OLTP setting
Alerts:-It gives the information alerts are created by uses, but they consultant the SAP when new alerts are required
In plaster forecast profile


Diagnosis groups

HL- grows

Mad: 50%
[√] alert when fore cast couldn’t b made


Save master fore cast profile
Creation of alerts
Easy access


Supply chain monitoring

Alert monitor

Current setting

Set alert monitor (/SAP APO / Amon setting)

Under APP Splecfic alert profiles

APO: Fore cast planning

Create icon

Profile id name –HL-aprfl
Amo app: Fore cast planning

Selection Tab
Select MAD threshold value for prior: 45

Planning book:- HL-monthly
Selection des: Text –HL –selection


/n/ SAP APO/ sdp 94

Load data

Delete the fore cast
Easy access


Supply chain monitoring

Alert monitoring

/amon 1

Select alert

Determine alerts

P version: 000

Select days

Determination alerts

Select the selection

Check the error percentage
Our layer correction: History clearing
BW Loaded (PA) ———> Raw history

Sigma factor starts from 0.3 to 2
Less sigma value is lower values
If sigma factor
We add sigma factor to + to higher value
– To lower value
Out Layer correction:-It will cut the values from upper values and lower value and keep in base value
Ex fore cast:-
Eg:-History is 100 and
Fore cast for previous month are 90
Then we get the error percentage the difference between history and fore cast -70 for previous month is called Ex-post fore cast
Calculating the fore cast values for history back period is called Ex-post fore cast
The correction in the history and fore cast value for history is called ex-post fore cast by this base fore cast value is calculated
To remove ex-post fore cast method
In master fore cast profile, remove ex-post fore cast from the method
Outline correction (or) Tolerance = ex- post fore cast +,- MAD 125
Mean absolute deviation [MAD]
Eg: 2 3 4 5 6 10
2+3+4+5+6+10 =30
Average = 30/6 =5
5 is the mean value
2nd absolute deviation is -5
2-5 3-5 4-5 5-5 6-5 10-5
3+2+1+0+1+5 =12/6 =2
2 is the mean absolute deviation
1st –mean value is calculated
2nd – Deviation value
The result is the MAD
Basic value
G (T) = (G (t-1) +a(v(t) –G (t-1))
G (T) = the current basic value for the current period (t)
G (t-1) = the previous basic value from the previous period
V (t) = Actual demand for the current period (t)
A = smoothing factor is 0.1 to 0.5
1st – It will calculate the ex-post fore cast method
Basic value is the corrected history
Corrected history + Trend value = future fore cast value
For Trend –we use MAD
Production versions
BOM+ machine
Sequence of operations


Releasing fore cast at customer level or DC level
Stock up date at DC:
*Stock integration model active
*Movement type in R/3
In good issue, the movement is update
Transactional data is automatic update and manual data is manually update
To see customer stock we use separate soft ware SIFEE
Customer stock —–> R/3 —–> APO
SNP character is standard characteristics
DP —–> Demand estimate
SNP —-> The demand we got in DP can be filled or not
Sub-contracting —-> half work is done by vendor
Purchasing —-> Purchasing
How much is the demand?
Which demand has to send to which distribution planning?
Transportation planning— How the product has to send
/ SAP APO / MSDP –admin
[√] SNP possible
{APO Activity —-> 9AACT NAME
APO Location —-> 9A LOC NO
APO Product —–> 9AMATNR
APO resource Name —-> 9APR NAME
APO Transportation Lane —-> 9ATR NAME} Standard characteristic are only used
SNP planning is always the combination of location and product
But in DP we can plan any level
In SNP and distribution pla –based on Location / Product
In TP ——> based on transportation lane
Navigation attribute: To differencate the source location and distribution location we use navigational attributes
Click navigational attribute
9ATR NAME- 9ATYPE} these 3 are mapped automatically added to the characteristics in SNP MPOS
Location /product/resources
Location /resources
Consistency check
/D / SAP SPO /

Output device: LP01
MALA —-Material /Lane
MALARE —-Material /Lane /resource
MARE —-Material /resource
MALORE —-Material
In APO, the master data is stored in table in hexadecimal format
SQA —-> table joining in R/3
To see hexadecimal format name
SE 16 —-> Table name /SAP APO /mat key

MFTIP: 22*8 {06 SNLCS mevo dajG *G} Internal number in APO for planning this no is only used
V-mat loc-for location
Planning data is stored in live cache
/SAP/APO – TR- Transportation lane
If the consistency check gain arises, click only
[√] repair for consistency in
/ SAP APO/ TS cons
Do the product consistency for more than 5 times then keep the
Product in exclusion

How to keep the products in exclusion
In planning book

Selection id

Select the Location
↓ (arrow)
Planner code excluded the product tab give name
Created 1 A ——> 4000 —>(1)
Created 3rd B —-> 4000 —-> (3)
Created 2nd C ——> 4000 —-> (2)
Truck capacity —-> 9000
1st —– 4000
2nd —– 4000
3rd —– 4000 {b-3000 will be ignored}
/n / SAP APO / RR P3
PV —- 000
Standard HPOS for SNP – 9ASNPBAS
Standard PA for SNP – 9ASNOBAS
Standard PA for SNP – 9ASNPO2
9ASNPO5 —-> Other PA are also there ‘r’
MPO’s —-It takes 8 alpha –numeric only 6 characteristics are used in SNP and 3 navigational attributes
Add—other navigational attributes


Info objects

Find button

Give 9A loc no

DC on APO location

Attribute tab

Add the characteristic to the attribute tab to act as
Navigational attribute
(The standard navigational attribute are assigned to 9 STRNAME i.e Transportation Lane
The navigational attribute is also created as a characteristic is assigned is other characteristic so called
Navigational attributes)
Planning area for SNP:-
/n/ SAP APO /MSDP-admin


After PGI, the order will disappear from APO planned order after production will become stock
Planned order —-> one week
TLB —-> 2 or 3 days deployment is for 10 to 15 days or 2 to 3 weeks
Active version ——–> (Copy) Inactive version —–> sent to BI
Very week initialization will be done.

Aggregates: In BW, at any level the extraction of data will take place. That will be defined in SNP
Aggregates tab: –
9 A RE
Key figures tab: –
Key fig ur. Selection button
Scmentic: means what type of key figure
Op – Time series KF – 001
SNP – Order series KF – 000
Live cache KF
Info cube KF – 002
In SNP, order series KF is used
In order, we have time series
In DP, in which month how much is 75 quantity, but in SNP, how much is the order quantity
*Key figure function
Category: Type of order or it represents the order
Sales order category —>BM
Planned order category —–>EE
Production order category —>AI
Stock (unrestricted) —>CC
Purchase requisition —>AG
Forecast requisition —>FA
Delivery (in BM) —- BR
In SNP, the data is displayed in category
9ASNPO2 —->is order based SNP
The characteristics that has no category
Eg: Safety stock
The time – series KF’s will not have category group. We can show group of category’s in category group
In SNP, we use only ‘S’ – pro – data
Key – figure assignment: In this key figures are assigned to aggregates
In TLB —>Transportation lane
Easy access

S pro



Supply chain planning

Basic setting

Maintain category group
Questions: –
1. Sementics
2. Aggregates
3. Key figure functions
4. Category
5. Category group
*In R/3, sales order is created? How can u see that BM in APO is sales order?
ANS: -It a standard functionality that is written inside the program
1. It is time – based planning 1. It is order based planning
2. It is time based 2. It is category based planning
3. Aggregates are not there 3. Aggregates can be defined
SNP Master Data SNP
} → Location
Transportation zone
Material → product (combination with location)
PIR/Scheduling agreements/contracts → Transportation lane, MOT (is only APO master data)
Production version → PPM/ POS
Work center —>resource
SNP heuristic doesn’t support contracts PP/DS heuristic has to be run in SNP also
PP/DS will support contracts
T. Lane = source location + destination
PPM: -production process material
PDS: -production data structure
Routing —- sequence of operations
Quota is maintained in APO only
2 types of Quota
1. Inbound quota: How much quantity the dc has to take from 2 different places
2. Outbound quota: -How much quantity the plant has to distribute allocate the stock
Inbound quota is used in heuristic outbound is used in deployment
In SNP, we use location/material mostly
Location /material is not only SNP related it is SCM master data
Transportation zone in location master data is mostly used in TPDS module
Transportation zone plant to zone
Eg: -If 2 dc are at same place, why do have 2 dc at same place
Ans: -2 dc are allocating for local people and other for non local people
Stages is mostly used for customer
If we want to plan for customer, we want to the stock available in plant. We plan mostly at dc level only
Fore cast → release → SNP
After release of forecast to SNP, the demand has to be produced for manufactured. It can be done in 2 ways
1. Manufactured at plant
2. Purchasing from vendor
Forecast or demand is done at dc. But we produce at plant. So we have to send the demand to the manufacturing plant
MC 77 → assigning selection ids to users
Demand + stock = net requirement
Net requirement will be sent to dc or source
To bring .net requirement from destination to source we use uristic or program or optimization
We use heuristic because on
If the procurement type is F in master data
F —–>External procurement
After running the net requirement,
Source —->T. Lane
If 4 T. Lanes, we
If running heurist at plant level
Source —->PPM

If 4 machines we have 4 PPM’s
T. Lane checking
1st ——- check for quota
2nd —— priority
3rd —— cost
4th —— lowest time for giving the product
Heuristic: -Heuristic is an engine, it calculates the net requirement then checks the procurement in product master
If procurement type is F, then check the T.Lane. if the source is only, then net requirement will be sent as the demand to source and at destination receipts will be created
If multiple sources are there, then check the T. Lane checking
3 types of heuristic
1. Location heuristic: System will run one location and one product at a time
2. Network heuristic
3. Multilevel heuristic

Location heuristic: –
Eg: -Product location
A ———-> Hyd 1
B ———> Hyd 2 one after another
C ——-> Hyd 3
When location heuristic is runned, it will take one product and one location. The heuristic will calculate the net requirement and receipt will be created at Hyd1. Then only it will run the heuristic for next product and next location
Next requirement will be sent to source
If source is not there, then the after running heuristic, it will calculate the net requirement. If the producement type is F, it will check for transportation lane and it will product receipts also as there is no source. The receipts will not be sent to the source. Then the demand can’t be produced from source
In SNP, we use future time bucket profile only
If we want to see the past orders, we can see all orders in combined form in initial column of planning book
[If the old planned order is there means, it will check the old planned]
Due to inconsistency in the deletion program of planned order, the planned order is not deleted. So we can’t create the new planned order. For that we have to delete the old planned order. Then only we can create new planned orders
Demand elements in PB of SNP
1. Forecast
2. Sales order
3. Distribution demand (planned)
4. Distribution demand (conformed)
5. Dependent demand
Receipts elements: –
Heuristic —–> Distribution receipt (planned)
Deployment —> Distribution receipt (confirmed)
TLB —-> Distribution receipt (TLB)
If demand is there and supply shortage is there. Then it will show in supply shortage /n/SAPAPO/TL3
Model: 000
Heuristic is runned at destination location
After heuristic, deployment is runned at source location
Base unit of measure
Purchase order created, delivery date is 17.04.2013 and start 16.04.2013
V LOIN —— Delivery
V L10B —— Master delivery
In APO —->Start 09.04.2013
Model: 000
Start location: ba01
Destin: hcl2
SE38 (Manual forecast release)
Program: /SAPAPO/Sjkt st04
Unit of measure is global data it is not location/material specific. The material wherever is used can use the unit of measure that is maintained in /SAPAPO/mat1. It is similar to all plants

Date view: SNP94 (1)
SNP Add products from supersession chains
↓ ↓
(.) Location Means inter changeability 80

In/SAPAPO/SNP94, Location heuristic button

In planning book, we can’t restrict the heuristic but in /SAPAPO/SNP01 —- Planning horizon in days is used to restrict the heuristic
/SAPAPO/SNPAPLOG —–>If heuristic is runned deployment is runned. The log will be created
If the heuristic is running through /SAPAPO/SNP01 or in / SAPAPO/SNP94 —->The results will appear in planning book
Copy the time from SM39

Application: SNP Heuristic
Copy time at from (Date/Time) field
Network heuristic: -Running of entire network is called net work heuristic
OC —–>Mother God own —-> plant
Network heuristic is run whole network at once
In /SAPAPO/SN01 —->Click network (heuristic)
Then location will be disabled
That means it is at product level
But we have to know at what level the heuristic to run

Easy access




SNP in back ground

Determine low – level code

(.) Temporary
( ) Manual selection
Bao1, hcl1

Execute —-> BA01 – 1
Hcl 2 – 0
In network heuristic, the product will run at low level code
1st – 0 will be run
Then – 1

Model name: 000
Star: BA02

To change producement type: F in /SAPAPO/Mot1
Peg areas —->Link
Pegging areas creation T. code

Product: Rin
Planning area: Ba01, Bao2
(.) Create pegging area
CTM: Capability to math
Fixed pegging —>already the order is fixed that order cannot be given to other. Without removing the pegging. Mostly used is location heuristics
Consistency checks: -Time series consistency check live cache consistency 0M17
Pegging areas creation
Then generate low – level code
Then network heuristic execution
If pegging areas there means, low level code will be created
Program: TS – LCM – cons – check
Heuristic —-> over —->confirmed
TLB —–>
At destination
Distribution Receipt (planned) —->heuristic
Distribution Receipt (confirmed) —>Deployment
Distribution Receipt (TLB Confirmed) —>TLB
At source
Distribution Demand (manned)
Distribution Demand (confirmed)
Distribution Demand (TLB confirmed)
Location heuristics is running on one level based
Eg: –
Pic 1: –
If location heuristic is running for this eg – level 1 will be running, because the net requirement must be calculated and that will be sent to M.DC1
At DC’s ———->Receipts (planned) will be created
At M.DC’s ——–>Demand (planned) will be created
Receipts (planned) will be created
When the heuristic is runned at M.DC’s
At plant —->Demand planned will be created
↗ ↗
We have the job running times
Deployment: -Plant has to do the deployment
How much is there at my place —–>Deployment
How much I need —> heuristic
For calculation
Of net
Net quantity —–> Receipts + issues
Plant will calculate the receipts – plant issues = net requirement
What is the key figure to add for receipts are called ATD (Available to Deploy) receipts
ATD issues
Net quantity = ATD Quantity
What are the figures to add for ATD receipts are called category group
In product master: RIN


SNP2. Tab

ATD receipts
ATD issues

Category group


Supply chain planning


Basic setting

Maintain category groups

Select ATR and click categories

In planning book,
In receipts —->we get the stock
In demand –>we give the demand
AI —–>Production (confirmed) in planning book
EE —->Production (planned) in planning book
AJ —>Planned orders (fixed)
BF —>Purchase order —->In PB, TLB confirmed (distribution receipt)
CC —->Stock
BM —> Sales order
After creating category groups, we have to assign that category group to the product master.
/SAPAPO/MAT1 in SNP2 tab in

ATD receipts
ATI issues
Product view
/SAPAPO/rrp3 —->ping version: 00


Create order

Req Qty: 125

Formed order mostly used PP/DS
T. Code: /RLC DEL – Initial column delete
Program – Se38 —->/SAPAPO/rLc delete
In initial column
Stock on hand = demand – receipts
Deployment: Confirming the demand quantities as per the dc’s

9ASNT 94
SRP 94 (1)
Days = 10 (how many days deployment will be done)
Manual selection: 000
Destination: Warg
Go to plant master data as deployment is done at plant

SNP2 Tal
SNP lernand profile
Pull 0 valuator – 15 (How many days dang part are to consider)
Is mentioned in pull depl.hor
SNP Supply profile: –
Push depl.hor (incoming stock for the plant eg: Bang1)
Demand (planned) —>demand profile
Production (planned)
} supply
Production (confirmed)
Deployment in active version (100) —>for 1 or 2 weeks or 10 days
Heuristics runs for 50 days in 000 versions
SNP Deployment profile: –
Push distribution:
ATD > Demand system uses push distribution
ATDC < Demand system uses far share rule Stock on hand: - Rule 1: pull = In pull, according to demand supply demand sent as per the day requirement the system deploys Pull/push: - Pull Eg: 1 2 3 4 5 6 7 8 9 10 Demand 10 100 200 100 100 50 50 100 50 50 Supply 1000 0 0 1000 0 0 0 0 0 0 (Planned or confirmed) 1 2 3 4 5 6 7 8 9 10 Deploy: 100 100 200 100 (Demand) Closing stock 990 890 690 1590 Opening stock 990 890 1690 Closing stock will be the opening stock for next day Push means ATD > Demand
Roll FWD —>It will give the stock for next days
ATD Quantity will be calculated for every day. Day means bucket
( ) By category j,
Category – EG
SNP last output is —->SNP planned orders
Production (confirmed) is PP/OS
To create receipts in production (confirmed) we have to go to ntp3 as it the PP/OS quantity
To delete PD/DS orders
/SAPAPO/Delete – pp – orders deletion
We use 3 deletions
1. SNP orders deletion
2. PP/OS deletion
3. Sales orders deletion – R/3
In /SAPAPO/Delete – pp – orders program
To delete fixed orders
Click fixed orders as the AJ can be fixed and normal
Pull/push – if stock is available means, it will pull the future days and supply the stock & bull deploy horizon & supply horizon
Lot size –
Fixed lot size in product master data
Model: 000
Local: WAS 9
Heuristic is inbound Quota: 000
To execute Quota – TL must be opened
Push by demand: Act same as pull/push
In push by demand will not consider the demand horizon or pull dept horizon
Pull/push —- DC
Fb plant as storage constraints then it will take push by demand
Planning horizon means —>the PB —->time bucket profile
Push by demand will consider the entire planning horizon. If the demand exist for only 10 days, then till the demand is their it will consider push by demand
Customer – safety stock 7 – 10
God owns – safety stock 17 – 30 days
Plants – safety stock 4 – 5 days
Plant to god owns —->push by demand
ATD > demand – push distribution
ATD will calculate every bucket
ATD < demand – Fair share rule Push by demand will ignore pull Depl. Hori and consider the push. Depl. Hor ↓ (Demand) ↓ (supply) Pull. Depl. Hori:-10 days Eg: - 1st day 2 3 4 5 6 7 8 9 10 11 12 Demand 10 10 10 10 10 10 10 10 10 10 10 10 Supply 1st day 5000 Pull 10 10 10 10 10 10 10 10 10 10 (Empty) Pull/push 100 it will pull the 10 days demand and supply the demand Push by demand 1st day 3650 it will give Quota buckets They will done product by heuristic and deployment In user say that receipt are not treating as then we have check is 1. Transportation pan 2. Run heuristic 3. Check job 4. Check tables EBAN 5. MEZ3 then Or 6. RLCDEL check Push by Quota (Q): - Pic 2: - If the plant has 10, 000 productions and the ware house has only demand 2000 even though the 10000 producted will be supplied to ware house. If the demand is O also the producted will be supplied to the ware For push by quota ---->out bound quota has to be maintained
/SSC – Tq1 ↓bang
[√] outbound Quota
In push by Quota it will not consider whether the demand is there or not
If the dc has no demand also, it will supply the product but it will consider the supply horizon
Fair share rule: -Fairly distributing the stock proportional distribution based on demand (A)
Forecast – FA
Additional forecast – FC
Sales order – BM
Heuristic runned: –
At destination: Distribution receipt (planned) – AG
At source: Distribution demand (planned) – BH
At destination: Distribution receipt (confirmed) – EF
At source: Distribution demand (confirmed) = EG
BH – PReRel
TLB – conRel
DC —— To —– plant —->purchase requisitic
Plant —- To —– DC —>Stock transport requisitic
Stock transport with TLB —>Stock transport order requisitic
Plant —-> to —->DC —->purchase order
Purchase requisitic converted to purchase order
At destination —->Distribution receipt (TLB) BF
At source —->Distribution dement (TLB) —-> BI
STOCK —>on hand —->cc
Planned order – EE
Production order – AI
1. Proportional distribution based on demand (A)
2. Proportional distribution based on Quota (C)

Dn quota, demand will not be checked
It will allocate the stock as per the Quotas maintained outbound Quota
3. Proportional distribution based on priority (D)
Procurement priority – in heuristic
Distribution priority – Independent
O – Highest
1 – Next priority
4. Proportional fuifulment of target (B) for DC. In lot size tab in product/location master data
Target stklvl method: empty
Target days supply: 10 days
How the key figure has to behavior depends up on key figure function
Lot size from product master
Targ stklvl method: empty
Target days supply: 10 days
Target stock level: How many days is maintained in demand
It will be calculated from next day and also for safety also it will calculate from next day
System equals the target stock level at every DC’s
Until the stock level percentage are equal then for both DC’s then it will allocate the stock
EX: –
DC’s available stock demand stock level (%)
A 200 1000 20%
B 10 20 5%
Until the stock level percentage of B become 20% it will not allocate to A
It will equal the stock level percentage not the stocks
Plant – 100 DC’s available stock demand stock level
A 200 1000 20%
B 10 200 5%
To level the stock level of B to 20%
10 – 5%
10 – 5%
10 – 5%
Then stock level of B is 20% by given 30 stocks to B out of 100 in plant
Then now the plant has 70%
After it will equally distribute the stock to DC’s then 1% to A and 1% to B
10 10 10 10 10 10 – A – then % is 21%
2 2 2 2 2 2 – B – then % is 21%
Till the 70 stock is supplied to DC’s equally then at last the %s are 26% to both DC’s
If we use this rule, it will allocate the stock then that is required for the DC. In this rule only, it will read dc’s stock also, but in rules A, C, D. it will not read the stock of DC’s
Reduce option in deployment options
Eg: Distribution demand (planned): 210
Production (planned): 100
After deployment
Distribution demand (planned) = 110
Distribution demand (confirmed) = 100
Production planned = 100
Delete option in deployment settings
↓1st ↓2nd ↓3rd
Eg: Distribution demand (planned) = 210. 10. 10
Production (planned) = 100
After deployment
Distribution demand (planned) = empty for all days
Distribution demand (confirmed) = 100
Minimum value and maximum value are maintained in —->weight, volume, floor s parts
Stacking factor
Floor s parts = 30
Stacking factor = 2
We can load 60
Stracking factor is maintained in product/location master
In properties tab, stacking factor
FLB profile is based on means of transport
Creation of TLB Profile: –
Easy access




Current settings


Define TLB Profiles (/SAPAPO/TLBPRF)

Go to change mode

Creation icon



Click [+] icon

Rule: 1
Parameter: weight
Oper LL: >=
Param. Val: 40
Oper. LL = < = Param. Val: 60 00M: KG ↓ Press enter ↓ Save ↓ Go to/SAPAPO/TL3 ↓ I MOT, Viz = Bang Warg = Bang ↓ Save ↓ Go to SNP 94 ↓ Selection window APO Transport lane APO source location: bang APO destination loc: warg, vizak ↓ Select Bang ---->Warg

Click TLB view

Select again Warg

We can see deployment

Select the demand

And click

+TLB (SNP04)

Then it create orders

For manual creation of TLB

Selection on 07.05.2013


For shipment (TLB) Partial orders


It is create an order without considering the TLB parameter values
For TLB orders, only the stock will be moved and in R/3, the stock will be transferred for distribution demand (confirmed), the stock will be not be moved
After TLB is done and went to R/3 and came back to APO, we cannot, delete the R/3 order but we can delete in R/3
/ME22 – in R/3
ME23N – for purchase order and purchase requiristion

PO →Purchase order history tab
If purchase order created in APO and not going to R/3
After good issue is done, then the purchase order will be deleted from APO
At DC’s screen, if showing intrensit exists that means goods issue is done and the stock is delivered to dc from plant
In R/3 PO – delivery date is end date in APO
VL10B – mass delivery
Purchase requisition – ME53N
(Only) ME23N → Purchase requisition
rrp3 —>product view

Stock, forecast, product/location data
M004 —>material requirement list

To see M004, we have set all the setting in plant
rrp3 details in APO —>can be seen in M004 in R/3
If vendor concept is there means, deployment will not be there we use SNP collebration module, to do deployment for vendor or for customer
For customer planning we use SIFI software for the customer sales
For vendor planning we use proxy software for vendor. We connect these 2 software’s to the SAP. After that the planned data for customer & vendor will be coming automatically from that s/w to SAP
For eg: -Vendor as send 80 requirement in SAP, the components required for that requirement has to explore, that is the BOM explore
If running heuristic at vendor requirement, the components will be explored and along with that the vendor requirement value will also change as per the BOM explore. But the vendor requirement must not change. In SNP, it is not possible, so we use PP/DS BOM explore heuristic. According to PP/DS BOM explore heuristic, if heuristic is runned at vendor requirement, the components or BOM will explore based on the vendor requirement
Eg: –
SNP: –
Vendor requirement = 80
BOM has 2 components
1st value is = 40
2nd value is = 80
After running heuristic, now in SNP, the vendor value changes to 120
But that is not correct
But in PP/DS after running heuristic the vendor value = 80 will be applied to the BOM values
i.e., vendor value = 80
1st value = 40
2nd value = 40 in PP/DS
We have maintain volume
We have to check the volume quantity in product master
Select the TLB —- Bang
And click [+] icon
Rule: 2
Parameter = volume
Op = > =
<= 40 UOM = M3 [Relationship between (and) and (or)] is if any one condition satisfies then to do TLB, automatically we must have deployment orders without deployment order also, we can create TLB orders manually If the requirement is not met, it will combine the orders and TLB will be done by next day /SAPAPO/SNP042 [√] Simulate TLB run ---->if we check this option, the result will not be saved in the planning book
From and to dates means the deployment orders must be considered
Start of planning period (opt): present day (TLB order we have to do)
Planning horizon = present day + 2 days
Eg: -Deployment orders
From: 08.05.2013
To: 15.05.2013
Start of planning period (opt): 8.5.2013
Planning horizon = 2 days
In this situation, the system will create the TLB orders from today by considering the planning horizon – of 2 days that means the system will ignore the deployment orders from 11.05.2013 (in normal situation)
Pull horizon = 3 days
Pull horizon is maintained in MOT (Means of transport)
In pull horizon concept, it will pull the future quantity order and then create the TLB order on same day, this situation comes into picture when stock is available in plant – pull horizon is used to up size the shipment. It will pull horizon
Eg: – 8 9 10 11 12 13 14 15
Deployment 10 10 10 10 10 10 10 10
TLB profile for 20 quantities
Planning horizon = 2 days
TLB order will not be created on 8th because the requirement of 20 is not met. So it will create the order on 9th with 20 quantity and pull horizon in MOT, it will pull the 11th quantity and create 20 order on 10th because as we maintain planning horizon = 2 days
In TLB Profile;
BANG: Connect upper limits ‘and’ and lower limits with “OR”
Upper limits weight 60
Volume 39
Lower limits weight = 40
Volume 30
To create TLB: 1st it considers is volume – in that upper volume
39 => M3 = 39
40 and 60 of weight
—->Connect upper limits “and” and lower limit with “and”
It will not create, because both the volume and weight must be satisfied
Upper limits: weight: 60
Volume: 39
Lower limit: w: 40
V: 30
As volume 1st considered as 39, which is not in between 40 and 60 as 2 conditions has to satisfy, it will not create the order
—>Connect upper limits “and” lower limit with “OR”
Eg: upper limit weight = 60
Volume = 39
Lower limit weight = 40
Volume = 30
As at least one condition has to satisfy then it will create the TLB order
At the end of the day, after the creation TLB orders and get confirmed in TLB confirmed then we delete the remaining quantity
GUID Concept:
Eg: 1 A —— 4000
2 B —— 4000
3 C ——- 4000
Truck capacity = 8000 – 9000 quantity
(Mix) (max)
Created the materials in R/3 as 1st —- F
2nd —– B
3rd —– C
And CIFED to APO as 1st —– A
2nd —– C
3rd —— B
By cifing the material from R/3 to APO the system will create its own GUID by that GUID only TLB loading will be done
By above ex: A = 4000
C = 4000
B = 1000
Remaining = 3000 of B will be delivered for next day. Ib for next day no orders exists, we will delete the remaining 3000 quantity. If urgently required of 3000 quantity we will manually create the TLB order
/SAPAPO/SN04 —— for TLB
TLB will check on the based on MOT
GUI – ID con
Table /SAPAPO/Mat key

Product: Internal product no in APO
While doing TLB, shipment will be done based on loading group in product master
Loading methods are 2 types
1. Straight loading (Default)
2. Load balancing
Pull horizon:
For means of transport maintain pull in horizon as: 3
9th p (planned) —– 4000
10th p (plan) —— 4000
11th p (p) —— 8000
Pull in horizon will work if the stock is there only pull in horizon is used to up size the shipment
In pull in horizon, it will take the minimum quantity that is maintained in TLB Profile
For cyclicing pegging areas N/W heuristic will not work
Safety stock planning: is maintained to meet unexpected demand
Other elements:
1. Delay in receiving material
2. Strick
3. Labour stricks in company
We maintain safety stock at different level
7 days 1 days —— 1) customers (distributor, retailer)
17 to 30 days ——- 2) DC’s
3) Central ware house
4 to 5 days <----- 4) plants Safety stock is measured in quantities and days Safety stock will not include current day demand Eg: If I say I have safety stock of 30 quantities what is considered 1+30 = 31 2 types of safety stocks 1. Standard 2. Dynamic Standard safety stock: - 1. Safety stock 2. Safety days 3. Max (safety stock & safety days) Safety stock: -If the demand is there are not considered, it will maintain the stock constant for every days Safety days: -It will consider the demand element how many days demand should be considered /n/SAPAPO/Mat1 ↓ Lot size tab ↓ Quantity and date determination Safety stock = 100 Safety stock method: SB (safety stock from location product master) Safety stock is also demand element Safety stock is runned at heuristic engine Net requirement = demand + safety stock – stock on hand Safety stock will run at heuristic engine and also at optimization engine also Net requirement will be calculated by day by heuristic Net requirement will be calculated for every bucket Eg: - On11.05.2013 ------- demand = 20 Safety stock = 100 Stock on hand = 0 Net requirement = 120 Receipts = 120 Closing stock = 100 On 12.05.2013 = demand = 20 Safety stock = 100 Stock on hand = 80 Opening stock = 100 Net requirement = 100 – 80 = 20 Irrespective of demand, I will keep the safety stock amount as safety stock SB (safety stock from location product master) is rarely used Sz (Safety says from location product master) We have to give safety day’s supply = 10 In location product master Mostly used - SZ Rarely used - SB By using this, it will calculate according to my demand It will consider the demand element in days By using this, it will calculate according to my demand It will consider the demand element in days. If demand is not there means, it will not keep the safety stock Today’s demand + future 10 days demand will be shown as safety stock Net requirement > 0 (It will create receipts)
SM: Compare SB and SZ, which safety stock is greater that method will be taken into account
i.e. max (SB and SZ)
Demand + safety days – stock on hand = net requirement
We have shipping conditions for shipping points. But we don’t have shipping conditions for plant so to give shipping conditions to plant we create plant as a customer and assigned to plant
Plant as to act as a customer and plant as to act a vendor
So go to SE16 —>Table too1w
SNP planner will be coordinated with supply planner, production planner, transportation planner’
Safety stock planning: –
Dynamic method
1. Safety stock —– MB
2. Safety days —— MZ
3. Max (safety stock & safety days) —– MM

Safety stock dynamic is time based. By this we can change the stock in the planning book itself. There is no provision to change the safety stock in master data of product. For that we maintain separate key figure for safety stock dynamic in planning book
9ASNP05 — is used for time based safety stock. The standard planning book planning area 9ASNP02 will not have this key figure for dynamic safety stock
9ASNP – SSP —- for safety stock dynamic safety
We mostly use only standard safety stock method only in that SZ
We don’t use dynamic safety stock method, this is because we can’t estimate for each and every day what is the demand we get
14th 15th 16th 17th 18th
Safety day’s supply 2 10 12 15 10
Safety stock (planned) 10 20 30 40 50 60
There are other methods
Flghe, beta, gamma
These are not used at all
SE16 ———- Only used
SE16N ————- Customized T code
VMI: -Vendor management inventory
In APO, we can’t plan customer because we need stock
Forecast released weekly
Scenario: –
↓ MOMB Cali
↓Pulscer →Race bikes
New z is created as customer to Banz
In this scenario, that customer can be plant or DC
In TLB Profile
3 (Relationship is specified by customer)
Rule details ———— (1 and 2) or (3 and 4)
It will 1st check for the highest value, if not met it will check for the lowest value
Setting for customer sales order to APO from R/3: –
Who place an order —— sold to party
Shipping to whom ——– ship to party
Who day money to company ——- payer
Customer can be distributor, retailer, and wholesaler
Va01 ———- create sales order
Order type [OR]
Sorg: 1000
DC: 10
Div: 00

When cifed the customer to APO, ship to customer will come by default
Location: US1234
L. Type: 1010


VMI Customer tab
Location for sold – to – party [ ]
If not maintained, that orders will not be flow to R/3

Come to R/3
Given customer number

See sales area tab
Partner function
Customer created
CFM1: –
Model name: br – cust
Br – cust
[√] customers —->116
In Loc3
Loc = *116 <----- F4 Publication type ------ /n/SAPAPO/CP1 Sales order ----------- warg External p --------- warg (Purchase order & purchase requisition) In – house -------- warg R/3 SM30 Table ↓ Ci6vMisd We cifed the ↓path Sprm ↓ IMG ↓ Integration ↓ APO ↓ Application specific setting and enhance ↓ Setting & en for sales order ↓ Setting for VMI ↓ Assign sales area and order type to ordering party/plant ↓ Customer: 14100 Sales type: Q4 As per the company norms the order must be referred with VMI Scenerio: - 1. Assign sold – to – party in VMI – Cuts loc3 2. Publication type in APO/CP1 3. Assign sales area/sales order types in cifed VMI setting 4. VMIEDI – IDOC IDOC ----->Data container
For eg —–>we
ALE —–>For IDOE we use ALE
Application link enabling

In APO, we have to set to setting for IDOC for customer in APO
APO —–>SE16


SM30 —–>
Table/view: /SAPAPO/VMIEDI







Maintain IDOC Setting for stock in transit
Customer: number
: Stock/sales through EDI/XMI
Sub contracting: Partially dividing the work to 3rd party
In this concept, we will give the raw materials to vendor and ask him to give us the finished product
Purchasing sub contracting
1. We won’t provide a raw material 1. We provide raw material to the vendor to get
To the vendor we directly purchase finished product from him
The finished good from vendor
2. We pay him the purchasing amount 2. We pay him processing amount
We required
1. Vendor
2. Distination location
3. Products or finished goods
4. Raw material or semi – finished goods
One direction finished good T. lane
Source is vendor
Distination is O.C
One direction raw material T. lane
Source is DC
Distination is vendor
100 F finished goods
[Vendor] ————— OC
Planned order
One received the demand to the vendor that demand has to be immediately split to the raw materials through PPM/PDS. We run the heuristic at DC, but at vendor automatically heuristic will run and planned order. The source will be the PPM or PDS for vendor
In PPM/PDS —->the both will explode and the raw material will get the demands
Eg: –
↗ ↖
r r3
100 100
Eg: -Finished goods are lays pack
Components of lays is packing cover & lays
[Lays pack] —– 100
↗ ↖
R1 R2
100 * 100 = 10, 000 100 covers
For finished: vendor —– in house procurement
Product: DC – external procurement
For raw material: Vendor – external procurement
DC – external procurement
In sub contracting heuristic is
Heuristic is an engine, it 1st calculate the net requirement, and then it checks for procurement type F, then check for the T. lane. If the procurement type is E (external procurement), it will check for the PPM/PDC’s where PPM/PDC is the source. In PPM/PDS, we have the BOM, it will explore and the demand will be sent to the raw materials
Master data
DC to be created —–>ci6 ——–> APO location — 1002
Vendor ———- Location ———– 1050 (Subcontracting)
Material to be extended to DC ——-> mat loc

In mrp [30]

Sub contracting
Com R1/DC ——–>
R2/DC ——>
BOM – DC with finished good —————- don’t sent this to APO
And BOM usage is universal —- 3
Production version DC with finished good
BOM created as to be assigned to production version
Sub – contracting info
Record has to be created
Production version has to be assigned to sub – contracting info record
Copy the plant, not own plant creation
1. Assign plant to company code
2. Assign p org to plant
3. MM01 —–>Material: Colgate
Industry sector —- food a no l related products
Material type — fert

UOM MG: 0001
GW: 250
NW: 200
V: 10 cublic CM
Plant: warg
Mrp1 MRP: X0
M: C: 000

MRP: 2 to 6
Procurement: F
Special procurement: 30
Sched margin: 000
Planned delivery day: 1
Availability check: 02
Valuation class: 7920
Standard price: 40
Loading group: 001
Raw materials:
Material —— paste
I. s —– F & Re
MT: Raw material
No need to maintain special procurement
GW: 200
NW: 180
V: 9
Valuation class: 3000
Standard price: 9

Material —- pack up
GW: 50
NW: 50
V: 10
4. CFM1
Model name: sub – mat
Sub – mat
[√] materials materials: Colgate
Pack p
5. CFM2
6. Go to APO
7. To see materials in table
SAPAPO/V- Mat loc

Location: Warg

8. R/3 —->XK01 —– vendor master data
C. code —— 1000
P. org —— 0001
A. group —– 0001

Name: FM Logistics
Country: DE

Recong: 31000
Cash mgt A1
Order currency: Eur

9. CFM1
Sub – vendor
[ ] Vendor vendor: 0000700225

10. CFM2
11. APO —– /LOC3
11. R/3 —— BOM Creation —– CS01
Material: Colgate
Plant: Warg
BOM Usage: 3

Paste: Quantity: 1 un: pc
Pack p: 1
12. Production version: C223
Plant: BA01
M: Colgate
BA01: Colgate
Version: Sub
Text: Sub
Valid from: 16/05/2013
To: 31/12/9999
Loot size: 1 to 10000
Production version is where you are going to produce routing is used in production in process industry we use receipy. Receipy is also sequence of operation. Routing is maintain when production capacities
Eg: pharmaceutical car
U: pc
Alternative BOMAL: 1
B: 3

Select the row

Consistency check

If BOM exists

It will be in green color
If the base quantity is not maintained means, it will not be cifed as PPM/PDS
Production version will explode the BOM
13. Sub contracting info record

↗ Vendor: 700225 Colgate
Creating link p.org: 0001
Between vendor plant: BA01
And production version
(.) Sub contracting
P. org:
Version: Sub
Stand Qt: 10
Min Qt: 10
Net price: 10
Pur. Gp: 000

14. CFM1 Material:
[√] DDS
(.) SNP Subcontracting
Prod. Ver: SUB
Plant: BA01

If cifed as PPM, it will be created as main T. lane
Vendor ———- Ba01 Colgate

If cifed as PDS, It will also create the reverse.

Vendor ——- Ba01

15. APO (To see PDS)

Product = Colgate, location = vendor number or name

PDS is created at vendor location
16. Cif subcontracting info record
[√] pur. Info record
Material: Colgate
Plant: ba01
[√] subcontracting info record
[ ] material Dep ——- for —— vendor
[ ] include depen ———— plant
Dest. Location: BA01
} Create MOT
Product: Colgate

Source: BA01
} Create MOT
Dest. Lo: vendor 700225
Only T.Lane will be created not the MOT we have to create MOT
I have to run the heuristic at
DC and 2 at component level
Master data —— /SAPAPO/Vercop —-> for version copy
Every week we have version copy
1) In which sequence we will cif the data?
1. Plant
2. Plant/mat
3. Vendor, customers
4. PIR
5. Work center
6. PPM or PDS – production process model
2) Transactional data is dynamic —- automatically updated in APO
3) Master data has to be cifed to APO
4) Initial transfer program: RIMODDNI
5) Version frozen: once the version is frozen, we cannot do any changes to the version
Live cache
Version 000
Version dependent: -not required to mention version
Transportation lane is model specific. Transportation lane is link between source plant & destination plant. It is not version specific
Vendor } Version specific
Transportation lane is ——>model specific
Quota is both
If it is model specific, we can see that information in any version
Resource is version and model specific
/n/SAPAPO/RES01 —- Resource
Why we need to run CCR?
Queue generated not updated in APO
Plant ——- DC
CCR is used for consistency check between R/3 and APO
Integration model
R/3 Purchase orders can be seen in CPP, but sales orders and all other will not be seen in CPP. When an order is created in APO with some number series will go to R/3 and replace the number series of R/3 and the number series will be updated in APO number series. Finally R/3 number series will exist in APO also
If pushing the Queue from CCR to R/3, one order will be created in R/3, when the same Queue exists in CCR, if once again pushed the same order will be created in R/3 with different order number
Obsolete: -Remove from CPP
The orders that are removed from CPP can also be seen in CCR
When the CVC or orders created in APO, GUI id is created at backend. GUI id is an ex – decimal number
After delta transfer also, if the data is not been sent to APO, then we can do initial transfer
Queues 1. Create
2. Delete order: Deletion in APO and sent to R/3, then that orders also will be deleted in R/3
Errors: –
1) Ingration model inactive
2) MRP type
CFG1 —->APO to R/3 —–>R3 log
SLG1 —–>R/3 to APO —->APO log

021 ——>external procurement ——>Purchase requisition
Purchase orders
031 —->In house production —->planned order
Block size settings BS for the data transfer
Initial data transfer
Set filter and selection block size
CIF of plant to APO
1. Node type is maintained by APO. It is a plant type distribution center
In APO to R3: -2. Maintaining publication type
If publication type is not maintained means the queue will be generated
From version 7 onwards only the node type from plant to DC
/Mat1 —–>Deletion flag for deletion of material
SE16 —–>/SAPAPO/Change
SE38 —->/SAPAPO/Change – Loc type

To see programs
Maintain the time for the columns visible from field variant
Characteristic navigational attribute
Copy option in realignment
DP Structure
How to debug
Steps required when new plant went to APO & steps to plan
What data will flow APO to R/3 to APO options in Q
Integration execution ofter checking RFC connection
Deletion of Queue
For debugging F5, F6, F7
Navigation attributes —— SNP —->In MPOS
Time stream id in storage bucket profile
Sem in PA details button
Locking logic & calculation type in PA
Change pointer T. code
1002 to 1001 change program
Concadenate formula in SNP for transportation lane
*parallel processing profile
File waiting options
Univarient fields in alerts
Processing direction ——- in SNP
Planner codes

Leave a Reply