SAP IS-U FICA - Error in worklist config for dunning by dunning strategy

[Former Member]

HI Experts,

We are using dunning by dunning strategy. We have also configured org structure for the same. But When we execute transaction FPWLM we get following error

User <user name> is not assigned to a Collections Department.

We tried debugging this issue and we can see that system is having issues in determining center and unit.

If any one has any idea what could be going wrong? Or if anyone can share step by step documentation on how to configure worklist for dunning by dunning strategy.

[AmlanBanerjee]

Hi Ravi,

The error that you are getting is generated from the FM FKKCLERK_CM_GET_OBJECTIDS_USER. and may be because the User ID is not unique or does not have any unit or any center or any manager assigned to them

You can use transaction FPAGENT, which would enable you to maintain assignments without using the PPOME org structure.  The purpose is to enable the utility collections department to provide worklist/workitem access on a temporary basis to users.

Hope it helps..

Thanks,

Amlan

[Former Member]

Thanks Amlan.

I checked transaction FPAGENT, but here the next issue I am facing

When I enter following parameters

Work item type = Space

User = User name

When I click on "Assign to team" nothing comes up. Any idea what is missing? Is there any other step that has to be done before this?

Note: We have defined collections department in PPOME and also assigned <USER> as manager.

Can you please help us with following

a. We want to make sure all users who are tied to collections department should be able to have access to FPWLM.

[william_eastman]

In that case you have not set up your responsibilities correctly at any level.

Navigation path: Utilities > Contract accounts > Periodic processing > for accounts > dunning > areas of responsibility. 

then make your assignments at all levels - department, unit and then agent.  If FPAGENT isnt showing info, then the higher level org elements have not been set up.

regards,

bill.

[Former Member]

Hi William,

We have done config that you mentioned here we have defined organization unit for credit and collections and also have user assigned as manager.

Is there any good document available on web that I can refer to see if, I am configuring this right at following path?

Navigation path: Utilities > Contract accounts > Periodic processing > for accounts > dunning > areas of responsibility.

Thanks,

Suhas.

[Former Member]

Hi Guys,

When I tried to execute transaction FKKCLERK_CM_CUDUNN I got following error message

" Responsibility for task TS90000130 is not correctly maintained "

And detailed description appears as follows

"

Responsibility for task TS90000130 is not correctly maintained
Message no. >A122

Diagnosis
The responsibilities of task TS90000130 include an object of the type O. However, you are only allowed to assign objects of type S or O (see below).

Procedure
Depending on the application, there are different tasks for the objects Specialist (S), Unit (O) and Department (O).
In Collections Management, use the object types listed below for the tasks described:

Task       Responsibility with Object Type

TS21000269 (FICA Collection Specialist)         S
TS21000273 (FICA Collections Department)    O
TS21000273 (FICA Collections Unit)                O

Change your configuration. On the SAP Easy Access screen, choose Periodic Processing -> For Contract Accounts -> Dunning -> Areas of Responsibility:

• Maintain Department Responsibilities
• Maintain Unit Responsibilities
• Maintain Collection Specialist Responsibilities

Use the object types listed above."

If you guys have any further inputs based on this please let me know.

[william_eastman]

the message details indicate that you have not set up the responsibility correctly.  For a clerk, only a position can be defined as the actor.  it appears that you have defined an or unit (type o).

[Former Member]

Please note that TS21000273 (FICA Collections Unit) should read as TS21000274 (FICA Collections Unit)

[Former Member · Accepted solution]

Thanks for your inputs guys. I was missing assignment of standard tasks to org unit in PPOME. And that what was causing issue. Finally it worked.....