| |

How to Understand the Production Data Structure

ByShaun Snapp

Executive Summary

  • The SAP PDS is a fundamental master data structure for PP/DS.
  • Learn about the many dimensions of the SAP PDS.

Introduction

Strangely this has no definition of SAP PDS in the SAP Help, which is pretty unusual for a term as important as the SAP PDS in SCM.

The book Sales and Inventory Planning with Marc Hoppe describes this object.

“It differs from PPM in that it provides more flexible options for combining and reusing individual routings and bills of material. The information already given on SNP PPM also applies to SNP-PDS.” – Marc Hoppe

However, this is only part of the reason for the development of this object, and in fact, it is probably only a minor reason for using the SAP PDS. This is especially the case when one figures out that SAP has no good solution for PLM. See this article for details.

Notice of Lack of Financial Bias: We have no financial ties to SAP or any other entity mentioned in this article.

  • This is published by a research entity, not some lowbrow entity that is part of the SAP ecosystem. 
  • Second, no one paid for this article to be written, and it is not pretending to inform you while being rigged to sell you software or consulting services. Unlike nearly every other article you will find from Google on this topic, it has had no input from any company's marketing or sales department. As you are reading this article, consider how rare this is. The vast majority of information on the Internet on SAP is provided by SAP, which is filled with false claims and sleazy consulting companies and SAP consultants who will tell any lie for personal benefit. Furthermore, SAP pays off all IT analysts -- who have the same concern for accuracy as SAP. Not one of these entities will disclose their pro-SAP financial bias to their readers. 

Why Was the SAP PDS Developed?

The real reason for the development of the SAP PDS is the performance problems with the PPM (the object it replaced) and the fact that the PPM has several issues related to converting the object between PP/DS and SNP. PDSs are the same between PP/DS and SNP except for detailed scheduling information, which is resident in the PP/DS PDS, but not the SNP PP/DS. SAP changed the PDS design and wrote the object in C+ to improve performance – and allows the single object to be addressable by either PP/DS or SNP without conversion. However, the downside of not being able to maintain the PDS in SCM has significantly reduced its adoption. However, the real reason to use the SAP PDS is not discussed by SAP because they do not want to admit to the performance issues regarding PPM.

Thus they push customers towards it by focusing on the benefits of SAP PDS and dropping “support” for the PPM, which they did way back in SCM 4.0.

Quotes on the Topic

This is addressed further by Marc Hoppe as he goes on to write.

“You can either create the Integrated Product and Process Engineering (iPPE) data in a connected Discrete Industries/Mill Products (DIMP) systern and transfer it to an SAP SCM system via the CIF, or create it directly in the SAP SCM system. You should note that for SNP you must use an SNP routing in the iPPE data. Then create a product version for the iPPE data and, from that, generate an SNP PDS. In the production versions, specify the validity period of the routing data for a product and a location, as in a PPM or an SAP ERP production version. You can also define costs and co-products here. In the production version, you can also specify a PP/DS production version, which is then factored by PP/DS when SNP is implemented in PP/DS orders.” – Marc Hoppe

The other method is to go and create the necessary precursor objects in SAP ERP.

“To use this option, generate the SNP PDS in the SAP ERP system directly from the routing, bill of material, and production version data. In our example, to do this, you have to select “SNP” or “SNP subcontracting” as the PDS type in the CIF integration model. The corresponding SAP ERP data is then transferred to the SAP SCM system, and an SNP PDS is automatically created from that data in the SAP SCM system, f you select “SNP subcontracting,” the product master data (for components too) is automatically created in the subcontractor location. Also, the transportation lane is automatically created between plant and subcontractor (although this is not possible if you are using an SNP PPM).” – Mark Hoppe

Screenshots of the SAP PDS

You then have to select the Variant for this SAP PDS.

SAP PDS and Quota Arrangements

PDSs can be used in conjunction with quota arrangements. It uses this transaction: /SAPAPO/SCC_TQ1 – Quota Arrangement. See this link for more details.

Costs and SAP PDS

Costs are uploaded using this BAdi: /SAPAPO/CURTO_SNP

See this link for more details.

Creating the SAP PDS

The SAP PDS is different from the PPM in that it cannot be created within APO, but the precursors must first be created in ECC and then be CIFed over to APO. The precursors are the following:

“For each production version a production data structure (PDS) is generated in SAP APO. For this, the combination of routing and BOM from the production version is mapped in a production data structure in SAP APO” – SAP Help

The BOM is well known among people that work in the supply chain, but the production version is often a bit more convoluted. The production version has the following fields (the commonly used fields are colored orange):

Production Version

  1. Plant x
  2. Material x
  3. Production Version x
  4. Check Date x
  5. Valid from x
  6. Valid to x
  7. From Lot Size (smallest lot size) x
  8. To Lot Size (largest lot size) x
  9. UOM x
  10. Alternative BOM x
  11. BOM Usage x
  12. Apportionment Structure
  13. Detailed planning group x
  14. Group Counter x
  15. Type (Equipment Task List, Routing, Inspection Plan, Master Recipe, Rate Routing, Reference Operation Set, Rough Cut Planning Profile, Standard Network, Task List for Functional Location) x
  16. OB Reference Material
  17. Change Number
  18. REM
  19. Allowed Product LinePlanningID
  20. Rate Based Planning Group
  21. Group Counter Rate Based Planning
  22. LT Type Rate Based
  23. Rough Cut Planning
  24. Group Distribution Key
  25. Received Location x
  26. Issue Storage Location x

Use of the Term Production Version

I find the use of the term to be often confusing. Frequently it seems used only to describe a usage where different versions of the production process for one product are modeled. This is true; the production version is where different versions of the same product are modeled. However, it is not the only use of a production version. Even if there are no variations to the product’s production process, a production version is still required. In simple terms, the production version is all non-routing, non-BOM, and non-Work Center information that is relevant for the production process.

These master data objects are the major controls for production planning and point to one another in a relational schema. This allows different BOMs to be associated with different manufacturing equipment and different production sequences or flow through the facility. The production version controls things like min and max lot sizes, alternative BOMs, and some other factors, so it can be seen as simply another relational master data object providing extra flexibility.

It is, in a way, the capstone master data object for production planning. Although in truth, there is no real hierarchy, as all four master data objects work together.

The BOM and the PDS

Of course, a big part of the SAP PDS is the BOM. The fields in the BOM are listed below (the commonly used fields are colored orange):

  1. Material x
  2. Plant x
  3. Alternative BOM x
  4. Item Number x
  5. Component x
  6. Item Category x
  7. Item ID x
  8. Quantity x
  9. UOM x
  10. Operation scrap in %
  11. Component scrap in %
  12. Co-product
  13. AltItemGroup
  14. Recurs. allowed
  15. RecursiveCAD
  16. IndicatorALE
  17. IndicatorLead time offsetOper.
  18. TL offset
  19. Distribution Key
  20. Phantom item
  21. Special procurement
  22. Engineering/design
  23. Production relevant
  24. Spare part indicator
  25. Relevant to sales
  26. CostingRelevancy
  27. Material Prov Ind
  28. Bulk Material
  29. Bulk Mat.Ind.Mat.Mst
  30. Prod. stor. locatin
  31. Prodn Supply Area
  32. Validity to x
  33. Validity from x

(BOM management is one of the great opportunities in companies. Most are either managing the BOM in the ERP system or with spreadsheets and uploading to ERP systems. Both approaches are deplorable practices. For more on this topic, see this article or )

Routing Fields

The routing controls the flow through the factory (the commonly used fields are colored orange):

  1. Operation x
  2. SOp
  3. Work Center x (colored blue as it will be explained in a topic below, which is also highlighted in blue)
  4. Plant x
  5. Control key
  6. PRT Classification
  7. Object deps
    Period-Dependent Operation Parameters Exists
  8. Cumulative type
  9. Subops Do Not Apply to Order
  10. Base Quantity x
  11. Unit of Measure for Op
  12. Std Valu
  13. Scrap
  14. Change Number x
  15. Valid From x
  16. Valid To x
  17. Created On x
  18. Changed On x
  19. Changed By x

Work Center Fields

  1. Work Center x
  2. Plant x
  3. Person Responsible
  4. Location
  5. QDR System
  6. Supply Area
  7. Usage x
  8. Standard Value Key
  9. Conrol Key x
  10. Setup
  11. Machine
  12. Labor
  13. Capacity category
  14. Pooled capacity
  15. Setup formula
  16. Processing formula
  17. Teardown formula
  18. Other formula
  19. Distribution
  20. Int.dist.key
  21. Prod: Setup rqmts
  22. Prod: Machine rqmnts
  23. Capacity category x
  24. Capacity
  25. Std. Queue Time x
  26. Work dimension x
  27. Work Unit x

Therefore, the SAP PDS is created from the combination of the following:

“You can generate the SNP PDS directly from work plan, bill of materials, and production version data in SAP R/3. To do this, you must select SNP or SNP Subcontracting as the PDS type in the CIF integration model. The relevant SAP R/3 data is then transferred to the SAP SCM system automatically, and an SNP PDS is then generated from it in the SAP SCM system.” – SAP Help

However, this quote seems to contradict logic as well as the quote I listed above, which I will list again:

……combination of routing and BOM from the production version is mapped in a production data structure. – SAP Help

That makes a lot more sense.

However, the routing contains the work center. So, in fact, the following are used to create the PDS.

  1. Production Version
  2. BOM
  3. Routing
  4. Work Center

Preparing the Creation of the SAP PDS in the CIF

The action is really all in ECC, as described above. The CIF merely combines the four master data objects into a single master data object.

This is set up in the create integration model transaction, which is CFM1 in ECC.

CIF for PDS32

As you can see, you can select from several different PDS types. Either PP/DS or  SNP and either internal or subcontracting. The subcontracting PDS resides at a subcontract vendor, which is treated as an external location for the procurement of the sub-component, but as an internal location for the procurement of the finished good.

SAP PDS Details

Interestingly, while the four ECC master data objects are voluminous, they very much compress in the creation of the SAP PDS. The SAP PDS also is perceived as much smaller than the PPM, even though the two master data objects perform the identical function.  The SAP PDS is a hierarchical structure. The SAP PDS has the following levels and the following fields in each level.

Level 1: SAP PDS (header)

  1. Product x
  2. Planning Location x
  3. Production Location
  4. Source of Supply x
  5. PDS Description x
  6. Usage x (SNP-CTM, PP/DS, CTM, etc..)
  7. Explosion (Date)
  8. Plan Explosion (typically states “Generated from R/3)
  9. Rtng Type
  10. Valid From x
  11. Valid To x
  12. Min LS (Lot Size) x
  13. Max LS (Lot Size) x
  14. UOM x
  15. Planing Version x
  16. Dicretization
  17. Bucket Offset
  18. Period Factor
  19. Object Dependency
  20. Simulate
  21. Obs.Status
  22. Creation Date

Level 2: Components

  1. Product Number x
  2. Product Short Description x
  3. Location x
  4. Location Description x
  5. Phantom
  6. Assembly
  7. Valid From x
  8. Valid To x
  9. Activity
  10. I/O Type x
  11. PrimaryPrd
  12. UOM x
  13. MatCons
  14. Based Unit x
  15. Costs
  16. Strategy
  17. RO
  18. Usage %
  19. SubLoc
  20. Explosion
  21. Factor x

Level 2: Operation

  1. Operation x
  2. Valid From
  3. Valid To
  4. Operation Description x

Level 2: Activities

  1. Activity Type x
  2. Operation x
  3. Setup Act
  4. Setup Group/Setup Key
  5. Short Description
  6. Setup Grp
  7. Scrap %
  8. Overlap
  9. Min Send Ahead
  10. Dep.Param.

References

Some of the detail for this post was provided by Ranga Chellappan and Suman Bhattacharyaa of IBM Global Services

https://help.sap.com/saphelp_scm41/helpdata/en/71/513b407b686913e10000000a1550b0/content.htm