SAP APO Master Data: The 5 Objects Your Plan Depends On

Avadhut Adake · 4 February 2026 · 3 min read

Location, product, resource, PDS and transportation lane: what each SAP APO master data object holds, its transaction code, and how it carries over to S/4HANA PP/DS.

Every plan SAP APO produces is only as good as the master data under it. A missing transportation lane or an invalid PDS often shows up not as an error but as orders with no source of supply, or no orders at all. Here are the five objects, their transactions and what to check first.

Where the data comes from

In a classic landscape SAP ECC is the system of record. Plants, materials, work centers, BOMs, routings and purchasing info records are created there and sent to APO through the Core Interface (CIF), using an integration model. In APO you mostly add planning settings to it.

The five objects

1. Location ( /SAPAPO/LOC3 )

A location is any place where products or resources are planned. Menu path: SCM Basis > Master Data > Location > Location. The location type says what kind of place it is:

• 1001 production plant

• 1002 distribution center

• 1010 customer

• 1011 vendor

2. Product ( /SAPAPO/MAT1 )

The product master sits in SCM Basis and is shared by all APO applications. It has a global view, valid everywhere, and location-specific views that hold the planning settings per plant or DC, such as procurement type and lot size.

3. Resource ( /SAPAPO/RES01 )

Work centers and their capacities arrive in APO as resources, with working times and available capacity. There are four resource categories: production, transportation, warehouse and handling unit. Scheduling uses them to decide when an activity can run.

4. Production data structure ( /SAPAPO/CURTO_SIMU )

A PDS combines the BOM (which components) with the routing (which operations, in which sequence). CIF creates it in APO from the transferred BOM and routing, and each activity names, in its mode, the resource it runs on. If a PDS was deleted in APO, send it again from ECC with CURTO_CREATE ; this needs an existing integration model for PDS.

• No PDS at all: SNP still creates planned orders, but without a source of supply.

• PDS present but invalid: no SNP planned orders are created.

5. Transportation lane ( /SAPAPO/TL1 )

A transportation lane links a source location to a destination location. Transferring purchasing info records (standard, subcontracting, consignment or pipeline), scheduling agreements or contracts from ECC creates lanes in APO, with the planned delivery time, validity period, price conditions and under- and overdelivery tolerances. The means of transport (truck, rail) must exist in APO, and each lane keeps the transport duration per means of transport.

• No lane: stock transport requisitions are created without a source of supply.

• Lane present but invalid: no stock transport requisitions are created.

What changes in SAP S/4HANA PP/DS

With PP/DS embedded in S/4HANA, planning runs in the same system as the material master and work centers, so there is no separate ERP to copy from. The roles stay the same: plants act as locations, materials as products, work centers as resources. The PDS is the only production structure; PPM is not supported. A material is made relevant for PP/DS in the Advanced Planning view of its material master. Network-wide supply planning, the job of APO SNP, is usually done in SAP IBP.

Key takeaways

• ECC or S/4HANA owns the master data; CIF moves it and APO adds planning settings.

• When a plan looks wrong, check the location-specific product settings first.

• A missing PDS or lane gives orders without a source; an invalid one gives no orders.

• In S/4HANA PP/DS the objects remain, with PDS as the only production structure.

Want to set up planning master data hands-on with a trainer? See our SAP S/4HANA PP/DS course .