Skip to Content
avatar image
Former Member

Product interchangeability

Hi Gurus,

I have question on using Product intechangeability for a particular scenario:

Manufactuirng plant produces 3 finished goods F1, F2 and F3 and ships to a customer (internal customer), but customer  identifies these 3 products as a single code say F1.

The manufacturing plant can decide basing on the capacity and product availability it can either ship one product (F1) for the entire quantity what customer is asking or it can ship combination of 2/3 products (F1, F2 or F3) to suffice cutomer requirement. But the customer would identify this as a single product which is F1.

My question is there a way we can use Product interchangeability to achieve this? Can anyone provide some guidance?

Thanks,

Murali

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Oct 04, 2012 at 04:27 AM

    Hello Murali,

    Please check whether FFF classes in interchangeability functionality fits your requirement. I think it will.

    Online help: http://help.sap.com/saphelp_scm70/helpdata/en/1d/0ee13dc2fd605ae10000000a11405a/content.htm

    Best Regards,

    Ada

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Ada - Thanks for your message. Can you elaborate more on how to configure this?

      Our scenarios could be multiple plants shipping with different Code numbers (F1 @ Mnfg plant 1, F2 @ Mnfg plant 2, F3 @ Mnfg plant 3), but customer identifies with a single code number which is F1 when they receive it.

      It would be helpful if you can elaborate on how to use FFF for this scenario?

      Thanks,

      Murali

  • Oct 08, 2012 at 12:01 PM

    Murali -

    In which application, this scenario is need to be used ? . I mean do you need to implement this

    • When Planning ( Forecasting ) for F1 or
    • Forecasting is already done for F1 and you need to cover the demand for F1 from all possible sources ? If so forecasting done only for F1 or for all three F1,F2, F3 ?

    br,

    Valavan

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Manas - Thanks for the message. I did release the interchangeability group and it doesn't work for my scenario.

      Just a small brief of our scenario:

      Manufactuirng plant produces/packages 3 finished goods F1, F2 and F3 and ships to a Market (internal customer), but customer  identifies these 3 products as a single code say F1.

      The manufacturing plant can decide basing on the capacity and product availability it can either ship one product (F1) for the entire quantity what customer is asking for it can ship combination of 2/3 products (F1, F2 or F3) to suffice cutomer requirement. But the customer would identify this as a single product which is F1.

      These are the steps I followed:

      • Supersession chain was created with full interchangeability with F1 <-> F2 at the manufacturing location. (Took two products to get my scenario working)
      • Forecast is released from DP to SNP at the market/customer location for F1.
      • SNP Heuristics was run for F1 at the Customer location so that the distribution demand is placed on  F1 at the manufacturing location. T-lane was maintained for this product.
      • When I run heuristics for F1 at Manufacturing location it just generates SNP Planned orders and I don't see subsitution orders on F2. Why Distribution demand wasn't considered as a demand element? Is this standard behavior?

      So it avoid that issue, I created forecast on F1 at manufacturing location and ran heuristics it did generate subsitution orders on F2. (we don't generate forecast on manufacturing location)

      Now my question is, what happens when it goes to ECC system? How is this product shipped to the market location? Since the market location doesn't have F2 extended?

      I would need help in getting the end to end scenario work. Would really appreciate if you can provide some guidance and steps around this scenario.

      Thanks,

      Murali