APO
Is called a plant in ECC.
Location in APO.
Migrates master and transaction between ECC and APO as needed
CIF
Review MRP elements, including planned demand and planned receipts, firmed receipts
MD04
Used to differentiate MTO or MTS with forecast consumption. The ending letter “F” is used at the demand plants. Manufacturing plant should not include F. Once this field is updated, it will automatically update the procurement type on MRP 2 tab. (E for in house production. F for external procurement.)
MRP Group
Area in TLB interactive planning where you can set up custom lanes for your work area, an easy way for planners to load specific, frequently used data.
Selection Profile
Similar to the SNP Planning Book, however this Planning Book allows for access to TLB (Transportation Load Builder) and the running of Deployment Heuristics
Deployment Planning Book
This is the process of generating planned replenishment orders from the plants to the Distribution Centers
Replenishment Planning
Provides deployment details on ATD quantities, unconfirmed purchase requisitions, and STO/PSTO quantities
ZAPO_DEPLOY
This horizon refers to the period of time over which deployment takes into account the planned distribution demand. This horizon starts from today’s date.
Pull Deployment Horizon
After executing TLB, doing this will send the PSTO or ESTO to ECC
Refreshing
Typically this type of STO is used to support prod-push manufacturing processes & is used for planning purposes only
PSTO
In SAP, boxes marked with a check indicate
Required Entry
Reports APO transportation lane data.
ZAPO_TLANE
This horizon refers to the period of time over which deployment takes into account the receipts defined in the ATD receipt category group of the location master.
Push Deployment Horizon
When can you make a change to a STO in APO?
Prior to sending to ECC
An algorithm that allows SNP to calculate quantities that must be delivered to a location on a time bucket basis in order to match demand and maintain desired service levels
Heuristics
This happens if data originating in ECC in maintained in APO only
Data is overwritten during next planning run
Product Master Maintenance: Maintain master data (including planning and deployment parameters) for products at locations
/SAPAPO/MAT1
The system immediately distributes all supply to the demand locations (ignoring the demand dates specified at the demand locations) to fulfill all demands within the pull deployment horizon.
Push/Pull Distribution
Clicking this button will allow you to load data such as APO Transportation lane in order.
Selection window/shuffler/Tulips
Plans the supply of finished goods across the entire TreeHouse Foods network and ensures the optimal use of Purchasing, Manufacturing, Distribution, and Transportation in meeting forecasts and actual demand - while considering all constraints in the Supply Chain
SNP
Material List Report: A custom report used to view and analyze APO product master data. The report can be sorted, filtered and exported to Excel. Can also be used to mass change Product Master. This report has download and upload processing with fix production functionality to hole SNP orders static during the SNP Planning run.
ZAPO_MATLIST
The system immediately distributes all supply to the demand locations (ignoring the demand dates specified at the demand locations) to fulfill all demands within the pull deployment horizon
Push Distribution
After the release of the STO in APO to ECC, doing this can only happen in ECC.
Making changes to the STO