cancel
Showing results for 
Search instead for 
Did you mean: 

Copy operator Is doubling qty in target KF

ankpatel
Contributor
0 Kudos

Hello,

Am facing an issue where copy operator is doubling qty in the target KF. It is simple copy operator which is copy of standard copy operator to copy consensus demand plan qty to consensus demand.

We have another copy operator in which source KF is same as above and target KF is different and this copy operator is working perfectly fine.

Regards

Ankur

Accepted Solutions (0)

Answers (2)

Answers (2)

ankpatel
Contributor
0 Kudos

Hi Matheus

Yes, I have already checked this and it is not matching. Basically, it is one to one which means, 3710 is supplying to only one customer 10100001.

I have raise OSS message for this issue.

Regards

Ankur

former_member367912
Participant
0 Kudos

Hi Ankur,

Can you share the response/solution for this issue.

Cheers,

Akki

ankpatel
Contributor
0 Kudos

Hi Akki,

There were duplicate entries in the Excel backend table for the same planning combination which SAP had to clean from the backend.

Regards

Ankur

mkorndoerfer
Contributor
0 Kudos

Hello Ankur,

Source KF ZCOPYAPODEMAND is on Planning Level WKPRODLOCCUST (Product Location Customer) while the Target KF CONSENSUSDEMAND is on Planning Level WKPRODCUST (Product Customer). I will use period TW40 2017 as example:

It seems that Source KF ZCOPYAPODEMAND has a total of 152 considering all Location IDs for Customer ID 10100001 and Product ID IBP-100. For the specific Location ID 3710, it is only 76.
In the planning view, if you remove Attribute Location ID, you should see KF ZCOPYAPODEMAND as 152 as well.

As the Target KF CONSENSUSDEMAND in on Planning Level Product Customer, the total sums up the values of ZCOPYAPODEMAND for all Location IDs (e.g. 3710, etc). Please sum all the values of KF ZCOPYAPODEMAND for all Location IDs for Customer ID 10100001 and Product ID IBP-100 and the result should be the same as the value for KF CONSENSUSDEMAND.
If this is correct, then it is just a Planning Level difference; in case this is incorrect, please create an incident for component SCM-IBP-XLS for further analysis.

Best regards,
Matheus