Recalled items after cancel release are not taken into account by FPCI

[Former Member]

Hi dear experts,

We are facing the next problem:

1. The dunning procedure releases as an activity the documents that reach a certain dunning level.

2. The items are submitted to the collection agency using FP03D

3. The users manually recall some of these documents

4. To avoid the automatic resubmission on the next days the users are canceling the release after the recall using FP03E.

5. When this is done the update file created in FPCI is not including the recalled items from step 3, so the agencies are not getting informed about the recalls.

I have been reviewing the SAP notes and I have not found a solution.

Thnks

Sergio

[AmlanBanerjee · Accepted solution]

Hi Sergio,

I think the problem is in Step 4.

When a particular document is recalled, the submission status comes in as 09.

Then if you do not want to resubmit the items back to the collection agency , then in the submisson job (FP03D\FP03DM) , you can exclude the sub status 09.

In this scenario, the recall information will be going in thru FPCI.

Also check in the "Additional Selection" tab under FPCI, whether, the "callback" is ticked or not.

By performing the Reset release, all the necessary information are getting lost and it is as new as an item in step 1.That's why, the information is not getting passed in FPCI to the collection agency.

Hope it helps.....

Thanks,

Amlan

[Former Member]

hello Amlan,

We have tested these steps

1. The dunning procedure releases as an activity the documents that reach a certain dunning level.

2. The items are submitted to the collection agency using FP03D

3. The users manually recall some of these documents

5. Execute FPCI and like this the recall is included in the file.

If we do the previous everything works fine,but I believe the standard SAP is missing something for cancel release cases, because an inconsisty is being created between SAP and the collection agency. If you are reseting something a notice for the collection agencies would have to be created.

On top of that we cannot exclude recalled items (09) in the selection of FP03D (or FP03DM), because we also have systematic recalls that are done according to the longevity of the documents and according to that longevity placed in different collection agencies.

Do you think this can be reported to SAP as an error? The system in any case should prevent you to do the cancel release if the record is not still in any update file (table dfkkcoli_log) to prevent the inconsistency. Just like the system does not allow you to do the cancel release if the item has not been recall first.

Regards,

Sergio

[AmlanBanerjee]

Hi Sergio,

In my opinion, it is not a SAP error, as there can be a scenario, where the item was released incorrectly in the first place. Had there been any validation, you would not be able to reset relase and have to go thru the entire process of submission and recall.

However,the business process that you are presently following for referring the items to the collection agency, there needs to be a validation, so that once the update information is send to the collection agency, only then you will be able to reset release.

Alternatively, a workaround is to give a day gap b/w the recall process from the 1st collection agency and the submission process to the 2nd one.

Step-1- Only Recall from the 1st collection agency on day 1

Step-2- Run FPCI (may be in batch) after the successful completion of all the recalls for day1.Information file contains the recalled information.

Step-3-Perform Reset release on day 2 for the recalled items on day1.

Step-4-Release and submit the items to 2nd collection agency on day2.

Hope it helps...

Thanks,

Amlan