Block Planning and Setup dependency objects

[Former Member]

Hi Experts,

I have a problem in the implementation of block planning in my client.

We are using SCM 7.0 with ECC 6.0.

We are using block planning for one resource. In the master recipe we have dependency objects for the setup phase.

The block planning runs ok, but when we create the setup phase, put the dependency objects to it and make the integration model (we are using PDS), the new orders generate do not respect the blocks restrictions.

But when we have a setup phase without the dependency objects, the orders generated respects the blocks restrictions.

Does anyone knows what is happening? how can we proceed with this issue?

thanks in advance

Thiago Cyrillo

[Former Member]

Thiaggo,

Are you using the dependency object in APO for some sort of planning? This might be a basic question, so please ignore if it calls for a detailed explaination of basics in APO.

But the idea is if this is classification of setup activity is not needed in APO, why not just delete it in APO with user exit. The guess i have is since the dependency object is written in R/3, it overwrites the one with activity or product master.

Kedar

[Former Member]

Kedar, we are using Super Recipe, sou we need the dependency to define wich is the correct Setup group for each order.

We need this dependency in APO.

[Former Member]

Solution proposed by SAP:

"Dear customer,

the reason for the reported issue is that characteristic

ZPL_FAIXA_DIAM_EXTERNO is not valuated at characteristic level if you

assign procedure ZST_GROUP to the activity.

The procedure assigns a specific value to a characteristic on activity

level. As long as you do not valuate characteristics manually (by

procedure) the system propagates the valuations from the top level

configuration (in that case the configuration of the variant) to the

activity.

However there must be the possibility to propagate characteristics to

activities selective, like when setting char values by procedures at

activity level. In that case the system must assume that only some

characteristics should be propagated but not all. Hence the system does

not merge in the top level configuration into the activity

configuration.

Eventually the propagation is completely in customer responsibility if

procedures become assigned that change activity characteristic

valuations to provide flexibility. Consequently please also propagate

characteristic ZPL_FAIXA_DIAM_EXTERNO to the block planning relevant

activity by extending procedure ZST_GROUP for instance by line

$SELF.ZPL_FAIXA_DIAM_EXTERNO = $ROOT.ZPL_FAIXA_DIAM_EXTERNO."

The characteristic ZPL_FAIXA_DIAM_EXTERNO is the one used to the block blanning.

[Former Member]

Thiaggo,

I guess there is a BADI to activate block planning for non production activities in PDS. Make use of that and then do an initial transfer of PDS. I could succesfully use this for BOM/Routing scenario.

The BADI is in APO is named /SAPAPO/CURTO_CREATE and METHOD - BLOCK_PLANNING_RELEVANCE.

Kedar

[Former Member]

Hi Kedar,

thanks for the reply.

Our problem is not related to the non production activity, because when we have the Setup activity integrated but without a dependency objects tothis activity, the orders generated respects the blocks restriction.

The problem is when we put the dependency object at the setup phase on ECC, and integrated them. After that the new order generated do not respect the Block restriction.

Regards

Thiago Cyrillo