cancel
Showing results for 
Search instead for 
Did you mean: 

How to aggregate the SNP PDS operations to 1 day

Former Member
0 Kudos

Hi Friends,

We are using SNP PDS. While maintaining routing I assign workcenter and enter activities ie., setup time and producion time for each operation.

For examplle i have 3 operations with activities

Operation 10 : Setup 30 mins and Produce 1 hour

Operation 20 : Produce 3hrs

Operation 30: Produce 2 hours

I CIF this BOM+Routing by selecting SNP PDS in CFM1 to APO. When this is tranferred to APO SNP

I see operation 10: setup 30 mins which is 1Day in SNP + Produce 1 hour is 1 Day in SNP. L:ike wise the other operations are 1 Day each.

By this when I check the PDS total number of production time will be 4Days.. which is supposed to be

30mins1hr3hts+2hours = 6.5hours.===> 1 Day in SNP ( My requirement)

By this my 6.5hours of production time is expressed as 4days in SNP. This is because the least time buket in SNP is 1 Day.

So how can i aggregate this operation with activities into actual production time. Mean to say aggregating the activities to 1 Day. How can I do this.

Can anyone of you had the same issue and have overcome this issue by any development do let me know. I do appreciate for your the help.

Regards

KRN

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi KRN

This sounds similar to something I have done where we use a APO BADI to modify the PDS to contain one operation and one activity with all modes having a duration of one day. We found that consolidating into one operation alone was not enough and that everything needed to be consolidated into one activity in one operation. The result is orders created have a duration of one day. The capacity consumption for each resource still exists all within the one activity. If a resource occurs in more than one activity(phase) then it's consumption is accumulated. All activity relationships are then deleted and components assigned to correct activity. We also have coded for time dependent changes in the SNP PDS (5.0) which complicates the consolidation of the operations and activities. The difference we had is that setup is not modeled in SNP (yet) so it was not factored.

There are a few things to look out for - SNP expects one resource capacity per activity so fixed/var consumption needed to be corrected in another enhancement when SNP orders are exploded and also in capacity leveling BADI. If you have a complex recipe then the SNP PDS is harder to validate in the consolidated form - using PPDS PDS as a reference helps.

Andy

Former Member
0 Kudos

Andy,

I do appreciate for our reply.

As per your reply you have mentioned you have used BADI, can I know the name of BADI and also do provide me more details how to handle this issue. As a funcitonal consultant I have given the requirement to my technical team for this development. Also I have provided few OSS notes, one of them is 1259563 (report to create SNP PDS with operation condensation) I need to know how this condensation of operations to one day will happen. When you see the PPM ==> BOM+Routing will be CIFed as PP/DS PPM and you have to convert this to SNP PPM. When you are converting to SNP PPM the operations are automatically get condensed. What approach should I follow for my requirement.

So our requirement is when you CIf the BOM+Routing using CFM1 by selecting the SNP PDS options all the activiites are CIFed as 1 Day each, Which should not happen. So need a enhancement to do so.We have complex recipe. It is purely a simple BOM with 2/3 levels.

Can you please help me in developing a new ehnancement. I really appreciate for your help.

Regards

KRN

Former Member
0 Kudos

KRN -

I have looked at the OSS message you provided - it was not out when we created our enhancement. The solution from SAP is not perfect and I guess it is something quick they came up with to provide something until a better solution can be provided in a future release. You must transfer the SNP PDS then run the provided program which only allows for a single PDS to be run at a time. Since it is a zprogram your developer could customize it to run for multiple PDS' maybe by looking at what changes have occured in some frequency you decide on. The idea would be to automate the program based on changes instead of running for all PDS'. This may work for you if you do not use secondary capacities in your recipe since the program does not account for those. Also time dependent changes (TDPP) are not carried into the SNP PDS. If you are ok with scheduling the program and with what the program does then this your solution.

The program SAP provided in the OSS would not have met our requirements and the process of having to run a program in APO periodically after new/changed BOM/recipes are sent to APO seems like alot compared to customizing the PDS in a BADI because it is automatic when the PDS is transferred. The BADI is /SAPAPO/CURTO_SNP which in our system was activated by SAP with example code for the bucket calculations and eliminating non-SNP data from the PDS. It is a single use BADI so we deactivated the SAP implementation and created our own utilizing the sample code. The collapse is in the CHANGE_SNP_PDS_R3 method.

I would recommend using the BADI to eliminate an extra step after PDS transfer and use the SAP provided code from the OSS message as a starting point for your developers.

Andy

Former Member
0 Kudos

Andy,

As mentioned using the BADI my technical team has come up with development. When I'm trying to execute the development and in a process of CIFing the PDS it is giving the error No bucket consumption for resource, operation.... the integration model is not getting activated, it stops with the error as mentioned.

I tired testing the development and I felt it is working fine, but the reason it was doing so was I had maintained a integration model before this development. My developer was trying to CIF this routing data usng the transaction Curto_Create, since the old integration model was active this transacton (Curto_Create) was picking this activated integration model to transfer the data.

But I wanted to test this deactivating the old integration model and creating a new integration model for this new development testing. When I'm trying to activate the integration model it is giving the error. First I had a feeling that there is some issue with my BOM and Routing data but it is not. When I use the same BOM and routing data with SAP standard BADI active it works fine, the data gets transferred to APO but the only thing it does not aggregate. I'm not able to find where we are going wrong.

Also I need to know the correct way of CIFing the routing data after the new development. Should I first activate integration model and then use Curto_Create transaction for data transfer or Should I use the standard way CFM1 and CFM2 for transfering the data.

Since you have past experience for the same kind of development your valuable inputs are really appreciated.

Regards

KRN

Former Member
0 Kudos

Hi KRN

One of of the resources in the PDS has zero or minimal consumption. Your structure should be similar to this (orders will still be create with one day total duration):

Operation 1

Activity 1

Mode 1 - duration 1 day

Capacity Req

2nd capacity req (if applicable)

Mode 2 - duration 1 day

Capacity Req

2nd capacity req (if applicable)

Mode 3 - duration 1 day

Capacity Req

2nd capacity req (if applicable)

I can't see your data or the code to really know what is wrong - the developer should be able to see the capacity requirements in debug after his code completes to know if a value is incorrect. If you had multiple instances of the same resource in the routing operations then they would need to be accumulated in the consolidated PDS. Is your code to consolidate the SNP PDS on the APO or R3/ECC side?

The old active integration model should not affect the transfer of the PDS with the new development. You could have left the old integration model active, delete the PDS in APO then use curto_create to resend the PDS. You do not need to create a new integration model becuase the enhancement was created but you will want to delete the PDS in APO. If the activation of the integration model is resulting in an error then the developer can set up his ID so that he/she can activate the model and debug the queue in APO - unless the error is happening in R3 then the developer can debug there. I imagine the error is in APO so the developer should investigate/debug there. If the error is sitting in a queue then you can look at the internal tables in the queue to see if anything looks unusual in the capacity requirements or mode tables and even debug from there.

What I have done on several projects is to use CFM1/CFM2 for the integration models then use CURTO_CREATE for the changes using the change transfer option. You will need to still perform deltas to incorporate new PDS' into the models. This can all be set up as batch job(s).

Let me know if you still need help - but it is hard not knowing what the developer has done.

Andy