Difference between Sp.procurement key 50 and 60

[Former Member]

Hi Freinds ,

Please explain me the difference between sp procurement key 50 Phantom assembly and 60 Phantom in planning with an example .

Regards

Sandeep

[Former Member]

Hi,

If my solution is okay, answered your question please close the thread, if not please raise your question

[Former Member]

special procurement key 50 is available.

This is used inform the system that the material is phatom assembly so that the BOm of this material is attached to the header material of phatom assembly

ex- assemly A, B, C, A requires B, B requies C

let us say you have eneterd 50 for B.

then The component of B i.e. C will be assigned to A during MRP run and in planned order/prod order.

key - 60 I have not heard off, but if you waht photom assbmly planning use the following link

http://help.sap.com/search/highlightContent.jsp

or use the following

Prerequisites

You must maintain the master data of the phantom assembly as follows:

Strategy group 59 on the MRP screen.

Set the indicator for assembly planning, the Mixed MRP indicator, to 1 on the MRP screen.

Consumption parameters (Consumption mode, Bwd consumption, Fwd consumption on the MRP screen) to allow for consumption of planned independent requirements.

Set the Special procurement field on the MRP screen to 50 (phantom assembly)

If you are using this strategy in a make-to-stock environment, you must set the Individual/coll. indicator is set to 2 on the MRP screen.

You also must set the Backflush field to 1 (2 may also be possible) on the MRP screen of the material masters for the components of the phantom assembly.

Backflushing is essential because the components are planned with only one planned independent requirement which can only be planned correctly if all reservations are reduced at the same time. This is only possible when the goods issue for the components is posted at a later stage as in backflushing. In addition, all components of the phantom structure have to be linked to the same operation.

BOMs must be maintained for the finished products and for the phantom assembly.

Process Flow

For a detailed example of the entire process, see Sample Scenario: Strategy 59.

This strategy should be used in the following business context:

Component requirements can be planned relatively effectively. Procurement (planned by means of planned independent requirements) is therefore triggered before the production order stage.

Smoothing procurement according to order demand is possible. In this strategy, however, the ability to react flexibly to customer requirements is more important.

An accurate availability check is performed according to ATP logic during production order processing. An availability check at component level is possible in the production order. See Availability Check.

Requirements from production orders (or schedule lines) are passed on to production and can lead to changes being made to procurement after the sales order stage, if the order quantities exceed the planned independent requirement quantities.

The planned independent requirements are consumed during the production stage. This means that you can compare the planned independent requirements situation with the actual order requirements.

In contrast to strategy 70, however, stock does not exist for the assembly in strategy 59, due to its ‘phantom’ nature.

[Former Member]

I am not sure 60 is a SAP delivered Sp proc key. You might want to check the parameters associated with both of the keys in customizing.

50- Phantom assembly is used when you do not want to plan/produce the parent level item and only the components in the BOM.