Skip to Content
avatar image
Former Member

Pegging in SNP Aggregation Planning is lost

Hi All,

Need some insight on an issue:

We are implementing Aggregate Planning in SNP/ CTM. Note that, we are not going to implement Dis-aggregation, Planning results are just required at the Aggregate Planning.

Master Data has been setup: Product Hierarchy and Resource Hierarchy.

Problem with Example:

Product Hierarchy looks as below:

Planning product: P1

Lower Level Product: A

  • Now if A has got a Sales Order "SO1", this "SO1" gets Aggregated and is now shown for Product "P1" as well.
  • Now CTM[Aggregation is active] is executed for Product P1, and Planned Orders get created.
  • But, these new Planned Orders for "P1" has got no pegging information to it. Meaning, these Planned Orders are having no Link to the Sales Orders.
  • I understand that the argument could be that the "SO1" is from Lower Level product and hence pegging is missing.
  • But, could there be any possible way to identify this pegging relation between generated Planned Order and Aggregated SO ? We need this information in one of our reports....

**This happens for all the demands[Reservation, Independent Reqs., Delivery...] which are aggregated from the lower level, and at Aggregate level new Planned Orders are created to cover the demand. The pegging is lost for these new Planned Orders...

Regards,

Avinash

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Oct 06, 2017 at 08:16 AM

    Hi,

    SAP said, there is no possible way to figure out the Pegging relationship.

    We eventually had to write bunch of custom logic in CIF and other programs, so that we generate Production Orders and other entities directly for Planning products, based on it's sub-Products.

    Regards,

    Avinash

    Add comment
    10|10000 characters needed characters exceeded

  • Jul 26, 2017 at 09:28 AM

    No one with some insight here ?

    Add comment
    10|10000 characters needed characters exceeded