Dunning updates field XMVKT "Contract Account not unique" in FKKMAZE

[former_member600096]

Hi,

We have activated Dunning with respective to "Dunning Collection Strategy".

Issue Description:
1. We are running Dunning (FPVA) with parameters - Parallel processing object GPART and selection parameters with full GPART range

2. We are running Dunning (FPVB) with parameters - Parallel processing object VKONT and selection parameters with full VKONT range

However, Dunning is updating the field XMVKT "Contract Account not unique" in FKKMAZE and collection step in blank. Moreover, there is no entry in FKKMAKO header table. But the collection step is updated in document level.

As per analysis, we observed that this is happening to accounts where BP having multiple contract accounts.

Appreciate if you can suggest what is the route cause for this issue.

Regards
Thaheer

[AmlanBanerjee]

Hi Thaheer,

Any specific reason , why you are executing the proposal and the activity within different parallel processing object.

As per my understanding,Dunning with collection strategies can only be executed with parallelization object GPART.

You should not change that.

Thanks,

Amlan

[former_member600096]

HI Amlan,

Thanks for your response.

The reason why we run the proposal and the activity with different parallel processing object is, it was suggested to us that the activity will run faster if it is run based on VKONT.

Do you suggest that we should be using same parallel processing object for proposal and activity as well ??

Also, we are not able to reverse Dunning run through (FPVC and FPM3), for cases FKKMAKO is not updated and the entry in FKKMAZE-XMVKT = X.

Can you please suggest if there is any way to reverse Dunning for above scenarios.

Regards

Thaheer