SNP Deployment Deleted STRs not deleting in ECC?

[Former Member]

Hi,

We run SNP heuristics to create the initial STR, then we run SNP deployment to push out firm excess supplies (as per usual deployment functionality).

As expected in APO the Deployment run creates Deployment STRs (DEP: PReq) and deletes the previous regular heuristic STRs.

The issue I am having is that in ECC MD04 BOTH types exist.. duplicating the STR. I see the new deployment STR and still the previous heuristic STR that was deleted and replaced by the deployment run in APO.

As the new deployment STR's are passing to ECC I can rule out issues with the integration models and CIF.. But I cannot see why STRs deleted in APO are not deleted in ECC.

When I run the CCR, it picks up all the PurReq inconstancies but only provides an option to 'Push to APO'.. e.g., recreate the duplicates in APO too.. Which I don't want, APO shows the correct picture, ECC does not.

Can anyone help? what am I missing, why does the STR deletion by deployment not flush through to ECC?

S SB

[Former Member · Accepted solution]

I'm going to answer my own question (it may help others later)

The basic answer was user error in test systems. The Heuristic STR's that were remaining in ECC were actually created long ago, and then the integration model was temporarily inactivated. Those STRs were deleted in APO, but due to the inactive integration model never got deleted in ECC.

The integration model was then activated.

Then the new Heuristic STRs were passed to ECC, Deployment then ran in APO and they DID actually delete the heuristic STRs.. it was just the really old STRs created in the situation above that remained. Demands had not changed so it just happened to be the same qty and date.

To resolve I had to push the CCR inconsistencies to APO, then delete them in APO (RRP3) and start over.

Anyway.. Question closed!