FSCM-COL: New Basis Rule for specific contact day

[Former Member]

Hi Mark,

you are an expert hence this riddle for you:

I have same situation as Bruno. I advised the client to have different group. Same as you sugest. That saves lot of efforts of customization. However they are not flexible.

When the user creates contact, it has several options to select as a RESULT of his/her call.

Can I build a Rule to create Work List based on this Result?

eg:

As per existing strategy exit the if the contact is successful then the contact appears after 7 days on the Work List.

We need to add Collection Rule to the strategy: If the Result is 2nd Voice mail then the contact should appear on the Worklist after 3 days (Not 7 days).  :

Can you advise if I can add it as A Basic or Collection Rule using BADi ?

-D

[Former Member · Accepted solution]

hi Dinesh

You have a couple of options here.

1 - use the resubmission process to control when the customer appears on the worklist after a type of contact.

2 - Your suggestion around the status of the customer contact could work, I have not done this personally, however the approach would be to create a new basic rule, and then assign that to a new collection rule.

[Former Member · Accepted solution]

Hi Mark,

1, I suggested submission option but then the callers need to remember call back (appearance on the next WorkList) period for each Result.

2. The client decided to use this second option. We will build the Basic Rule/s where the supervisor could set up number of days to call back for each result...so about 17-18 rules to be added in the strategy.

We haven't done it earlier. I believe we use  BADi to build each business rule.

Where could I get more tech information on BADis to build rules based on Results, tables that may get affected etc.

The client has concerns on what happens when they update their systems?

Again, Mark thanks for your support. It is invaluable contribution.

-D

[Former Member · Accepted solution]

This is the SAP help that can be found in SPRO - this should give you what you need.

If you are happy - please can you close the thread

BAdI: Basic Rules

Use

You use the Business Add-In (BAdI) UDM_BASIS_RULE in the component SAP
Collections Management (FIN-FSCM-COL). It implements basic rules that
are used in the collection rules and
strategies. The
task of a basic rule is:

• Verbal formulation of a condition for strategy maintenance and for the
  explanation of the strategy valuation in the worklist

• Check of the selection conditions entered in strategy maintenance

• Check whether the condition applies for a business partner in the collection
  segment, both in the simulation of a strategy and for the prioritization for the
  creation of the worklist

• Preparation of extensive documentation that explains the condition checked
  (see below)

The methods GET_TEXT,
CHECK_SELOPTS,
and EVALUATE
are available.

Requirements

Create the basic rule in Customizing (see IMG activity Define Collection
Rules). This table entry in Customizing is used as a filter for the
BADI. From Customizing, you can go directly to the implementation of the related
BAdI.

Standard settings

The implementation of all basic rules delivered by SAP is active in the
standard system. You should not modify or deactivate these basic rules. In the
definition of
rules, you decide which of the rules delivered by SAP and which
additionally implemented rules are to be used in strategies and therefore in SAP
Collections Management.

Activities

After you call the IMG activity, the system displays a dialog box where you
enter a name for the implementation.

If implementations of this Business Add-In have already been created, the
system displays them in a dialog box. You then choose one of them by choosing
Create, and continue as follows:

1. In the dialog box, enter a name for the implementation of the Add-In and
choose Create.
The system displays the initial screen for
creating Business Add-In implementations.

2. On this screen, enter a short description for your implementation in the
Implementation Short Text field.

3. If you choose the Interface tab, you will notice that the
system has populated the Name of the Implementing Class field
automatically, by assigning a class name based on the name of your
implementation.

4. Save your entries and assign the Add-In to a package.

5. To edit a method, double-click its name.

6. Enter your implementation code between the method <Interface
Name>~<Name of Method>. and endmethod. statements.

7. Save and activate your code. Navigate back to the Change
Implementation screen.
Note: You can also create an implementation
for an Add-In and not activate it until later. If you want to do this, do not
perform the following step:

8. Choose Activate.
When the application program is
executed, the code you created is run through.

9. Choose Documentation.

• Document the implementation of the BAdIs. This documentation is available
• for the definition of rules and for strategy maintenance, and should therefore
• explain the conditions that the method EVALUATE checks.

[Former Member · Accepted solution]

Hi Mark, Thanks for your help. Somehow I do not see option to close this thread or change status as Answered...

[Former Member · Accepted solution]

Hi Mark,

Before I close the thread, Now I have convinced the client to consider the option for submission. However, they have genuine issue. They do not want to give too much flexibility to the callers. Can the Supervisor / Admin have control over calendar...open calendar only for 5 days from today...?

[Former Member · Accepted solution]

you can report on open re-submissions, so run a report to show resubmissions that are too far in the future.

A resubmission can be edited, therefore the date can be changed, so there is some control around the process - however it is reactive - rather than pro-active.