1. SAP Help Portal, SAP S/4HANA 2023, "Pegging": "Pegging creates relationships between the receipt elements and the requirement elements of a product. A pegging relationship links a receipt element with a requirement element. The system uses pegging to identify which requirement is covered by which receipt element." This directly supports the definition of pegging as a "relationship between the receipt the issue elements."
2. SAP Learning Hub, Course S4520, "Advanced Planning in SAP S/4HANA", Unit 4: Production Planning Heuristics: The course material explains that pegging establishes the link between stock, receipts, and requirements. It clarifies that this is a core function of planning heuristics to ensure that every requirement has an assigned receipt, forming a pegging network based on the product's BOM structure.
3. Massachusetts Institute of Technology (MIT) OpenCourseWare, 15.762, "Supply Chain Planning", Lecture 5: Material Requirements Planning (MRP): The course notes define pegging as a key feature of MRP systems that allows for tracing the source of gross requirements for any part number. This confirms that pegging is about establishing the relationship from a requirement back to its origin, which is consistent with the BOM structure.