Recalled items reported incorrectly to collection agency

[Former Member]

Hi there,

We recently upgraded our system to ECC 6.0 in the month of February 2010. We have a problem with recalled items.

Issue description: Open items are submitted (Transaction: FP03M)to collection agency 'X' by the dunning activity when they reach a certain dunning level. After a 60 day period, the uncollected items (at colleciton agency) are recalled back (Transaction FPCI) to the organization from the collection agency 'X'. The recalled items are written-off 5 days later (Transaction FP04M). This write-off process creates a) Statistical Write-off and b) Write-Off receivable items. The Statistical Write-off items are submitted to a different collection agency 'Y' (Transaction FP03M). Later, the business users reverse these items (Statistical write-off and write-off receivables items) to make corrections/adjustments on them. When the users reverse these items the updates ( reversals, resets, payments etc.) on these items should be sent to collection agency 'Y' and not to collection agency 'X' because they have been recalled from this agency. But the updates are being sent to both the collection agencies (X and Y). With the updates sent to collection agency 'X' after recall, there is mis-matching balances between our organization and collection agency 'X'.

Has anyone come across this problem? Anyone there to help me out? Any clues/suggestions are welcome and appreciated.

Regards,

Praveen

[AmlanBanerjee]

Hi,

I am not sure about the submission status of the items when they are recalled from collection agency "X".

It should have a submission status of 09 when it is recalled from the agency.

Standard transaction code -FP03(for individual) and FP03U (for mass) is used for this purpose.

Once the item has a submission status of 09 for a particular agency, no further information is send to the agency other than the recall one.

Otherwise, if you want to take care in the file that is sent to the third party, you need to make changes in 5052 event.

Hope it helps.

Thanks,

Amlan

[Former Member]

Thanks for the quick response Amlan. I have checked the events (5052) concerned, there is no defect in them. Interestingly, this process is working right in Development system but not in Production system. The events and codes are all the same in both systems. Just wondering whats going wrong. Is it how the process is handled by the user? or something else?

Thanks,

Praveen

[AmlanBanerjee]

Hi Praveen,

Assuming the custom codes and config. related to collection agencies in both your systems are in sync, I would suggest you to compare and check the variant for FPCI in both your Prod and Dev systems for the collection agency "Y".

Thanks,

Amlan

[Former Member]

Hi Amlan,

I tried this too. The variants are same in both the systems. Unfortunately, Production seems not to work right.

I have a explanation of this issue in a different view which might help understand it better.

The order of submission status is different in Production system compared to same scenario in Development.

Order of submission status for open items:

Production:

01- Receivable released for submission

02 - Receivable submitted

09 - Receivable Recalled

06 - Receivable Written-0ff

05 - Receivable Reversed (here, after write-off on recalled items, Statistical write-off and Receivable write-off items are reversed)

02 - Receivable submitted

Above order of submission status for an item seems unachievable in development.

Development/QA:

01- Receivable released for submission

02 - Receivable submitted

09 - Receivable Recalled

06 - Receivable Written-0ff

09 - Receivable Recalled (System assumes this status after the item(write-off receivable) is reversed)

05 - Receivable Reversed

If you notice the order of submission status above, in Production status is ending with 02 for an item. System is assuming 02 status as receivable submitted to first collection agency 'X'. And hence when the item is reversed, the updates are sent to first collection agency too.

Thanks,

Praveen

[AmlanBanerjee]

Hi Praveen,

Thanks for explaining the issue in detail.

I would suggest you to send the original document to the collection agency Y after it has been recalled from the collection agency 'X before you perform the write-off. After you have submitted the original debt to the coll agnecy "Y" perfrom the write-off, and send the write-off information to the collection agency "Y".

It does not matter from a collection agency prespective, whether they are following up for a written-off document or a original document.

Hope it Helps...

Thanks,

Amlan

[william_eastman]

Praveen:

IF your testing was identical, then you should assume a difference in some code. For the DEV environment, possibly notes have been applied which have not been transported OR someone has made some changes to custom logic which is not the same as in the PRD system. Possibly also, configuration changes were made directly in PRD which were not copied into the DEV system.

regards,

bill.

[Former Member]

Hi Amlan,

When the items are recalled they have submission status 09. I guess its not possible to submit items to different collection agency then, unless the submission status comes to 01 (Receivable released for submission). I am unable to release the recalled items using transaction FP03E, therefore couldn' t submit them to collection agency 'Y'. When I write-off the recalled items two new items are created like I explained earlier. One among them (statistical write-off item) is submitted to collection agency 'Y' for follow-up. But when we reverse these two new items the Reversal information is being sent ot both the collection agencies.

Regards,

Praveen

[Former Member]

Hi Bill,

Thanks for your response. Yes, I did compare (Using Remote Comparision) the custom codes in Dev and Prod. They appear to be same in both the systems. We did implement OSS Note: 1391733 to correct the 'Reversal Information on submitted items' sent to collection agencies last month. This note is already in Prod. There is not any difference between the other codes in the systems.

Regards,

Praveen

[AmlanBanerjee · Accepted solution]

Hi Praveen,

There is a concept of reset release in ISU.

You can get it in the EDIT menu of the T.code-FP03.

Through reset release, you can remove the submission status of the item and it is as good as a new item being submitted to the collection agency.

Hence after the item is recalled, reset release the item and again release and submit it to the collection agency 'Y'.

Thanks,

Amlan

[Former Member]

That's right. I could do that. I will try to work on this concept. Thanks for the idea Amlan. Appreciate it.

[Former Member]

Amlan, William

Thanks for views and interest in helping me resolve this issue. Your inputs were valuable to me. I have successfully re-created the scenario in Development and was able to resolve the issue. I found that when reversing the Final bill items (after write-off), there is a check box for 'Dunning Reversal' which is selected(Back-office transaction CIC0 for customer billing). This is reversing all the earlier dunning levels and bringing the items back to submission status 02. Ultimately, when information is sent to collection agency 'A' the system is sending incorrect reversal records becase the submission status is now 02 for these items.

Thanks,

Praveen

[Former Member]

Issue Resolved.