Collection Strategy: BRF: Tips 11: Config Tables

Table	Name	Remarks
TFKKBRFAPPLCLASS	Application Class: Additional Settings	Refer to Collection Strategy: BRF: Option 2: Step 5: Define Additional Settings for Application Class
TFKKBRFBUFFER	Reserved Buffer Elements	Refer to Collection Strategy: BRF: Tips 10: Default Context such as $FKKMAGRP not available

Collection Strategy: BRF: Tips 10: Default Context such as $FKKMAGRP not available

When creating expression to access context, if system default context such as $FKKMAGRP not found, check Additional Settings for Application Class. Make sure "Application" field is "Collections Management".

Collection Strategy: BRF: Tips 9: Missing Class ID when creating Event

Implementing Class 0FICAEVENT's Maintenance Class from Rule must be 0RULES when creating the event.

Collection Strategy: BRF: Tips 6: How to Delete (Concrete) Action (BRFACT03)

1. Go to t-code BRFAPL03, enter the application class and then click "Delete" button.
   
2. Click "Yes" button.
   

Collection Strategy: BRF: Tips 5: How to Delete (Abstract) Action (BRFACS03)

1. Go to t-code BRFACS03, enter the application class and then click "Delete" button.
   
2. Click "Yes" button.
   

Collection Strategy: BRF: Tips 4: How to Delete Expression (BRFEXP03)

Collection Strategy: BRF: Tips 3: How to Delete Event (BRFEVT03)

1. Go to t-code BRFEVT03, enter the application class and then click "Delete" button.
   
2. Click "Yes" button.
   

Collection Strategy: BRF: Tips 2: How to Delete Implementing Class (BRFIMC03)

1. Go to t-code BRFIMC03, enter the application class and then click "Delete" button.
   
2. Click "Yes" button.
   

Collection Strategy: BRF: Tips 1: How to Delete Application Class (BRFAPL03)

1. Go to t-code BRFAPL03, enter the application class and then click "Delete" button.
   
2. Click "Yes" button.
   

Collection Strategy: BRF: Option 2: Step 5: Define Additional Settings for Application Class

1. Go to SPRO -> Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Business Transactions -> Dunning -> Dunning by Collection Strategy -> Settings in Business Rule Framework -> Define Additional Settings for Application
   
2. Configure application class and choose appropriate Application, for collection strategy, this should be Collections Management.
   

Field Name	Usage
Application Class	Application Class that you have created for Collection Strategy
Application	Application that is calling this application class: ·         TOBJ - Object-Based Tax Calculation and Validation ·         TFOR - Form-Based Tax Calculation and Validation ·         COLL - Collections Management ·         PTAX                                                            ·         0001                                                            ·         REF1 - Refund Process ·         REG1 - Registration Process
Time-Dependent	Whether the BRF objects are time-dependent
NoEndTime	Excluding End Time, for example, the validity date is  from 2/1/2013 to 2/1/2015, if this is selected, 2/1/2015 will be excluded.
Time Unit	Day or Hour

Collection Strategy: BRF: Option 2: Step 5: Create Second Action to Determine Collection Step

1. Right click on "Actions" node, select "New Action". 
   
2. Enter Action Name.
   
3. Enter Short Text Name
   
4. Add Implementing Class: 0FICACS001, after that, click "Save" button.
   

Collection Strategy: BRF: Option 2: Step 4: Create First Action to Obtain Context

1. Right click on "Actions" node, select "New Action".
   
2. Enter Action Name
   
3. Enter Short Text Name
   
4. Add Implementing Class: 0FICAIN001. 
   

Collection Strategy: BRF: Option 2: Step 3: Create Event

1. Right click at "Events" node, click "New Event".
   
2. Enter the event name, this will be configured in Collection Strategy.
   
3. Implementing Class: 0FICAEVENT
   
4. Controller Class: CL_FKK_BRF_EVENT
   
5. After that, click "Save" button.
   

Collection Strategy: BRF: Option 2: Step 2: Add FICA Implementing Class (BRFIMC01)

1. Go to t-code BRFIMC01.
   
2. Add the following implementing classes to the application class:
1. 0FICACS001
1. Short Text: Determine Collection Step and Evaluation Number
2. Class Type: A
3. Implementing Class: CL_FKK_BRF_AC_COLLECTION
4. Maintenance Class: CL_FKK_BRF_AC_COLLECTION_MNT
5. Icon/Symbol: @BC@
6. Object Name for Title: Define Collection Step
7. Title for Create: Create Rule &1 Collection Step and Valuation Number
8. Title for Change: Change Rule &1 Collection Step and Valuation Number
9. Title for Display: Display Rule &1 Collection Step and Valuation Number
   
2. 0FICADR001
1. Short Text: Access Context Information
2. Class Type: F
3. Implementing Class: CL_FKK_BRF_DATA_REQUEST
4. Maintenance Class: CL_FKK_BRF_DATA_REQUEST_MNT
5. Icon/Symbol: @71@
6. Object Name for Title: Access Context
7. Title for Create: Access Context Information Create &1
8. Title for Change: Access Context Information Change &1
9. Title for Display: Access Context Information Display &1
   
3. 0FICAEVENT
1. Short Text: Impl.Class for Events
2. Class Type: E
3. Implementing Class: CL_FKK_BRF_EVENT
4. Maintenance Class: CL_EVENT_MNT_BRF
5. Icon/Symbol: @5M@
6. Object Name for Title: Event
7. Title for Create: Create Event &1
8. Title for Change: Change Event &1
9. Title for Display: Display Event &1
   
10. Maintenance Class for Rules: 0RULES
    
4. 0FICAIN001
1. Short Text: Obtain Context Data
2. Class Type: A
3. Implementing Class: CL_FKK_BRF_AC_BUFFER_INIT
4. Maintenance Class: CL_FKK_BRF_AC_BUFFER_INIT_MNT
5. Icon/Symbol: @5Y@
6. Object Name for Title: Obtain Context Data
7. Title for Create: Get Context Data &1 Create
8. Title for Change: Get Context Data &1 Change
9. Title for Display: Get Context Data &1 Display
   
5. 0FICAMSG001
1. Short Text: Issue Message
2. Class Type: A
3. Implementing Class: CL_FKK_BRF_AC_MESSAGE
4. Maintenance Class: CL_AC_MESSAGE_MNT_BRF
5. Icon/Symbol: @0S@
6. Object Name for Title: Issue Message
7. Title for Create: Issue Message Create &1
8. Title for Change: Issue Message Change &1
9. Title for Display: Issue Message Display &1
    
6. 0RULES
1. Short Text: Rules for Events
2. Class Type: R
3. Maintenance Class: CL_RULES_MNT_BRF
4. Icon/Symbol: @03@
5. Object Name for Title: Rules in Event
6. Title for Change: Change Rule &1
7. Title for Display: Display Rule &1
   

Collection Strategy: BRF: Option 2: Step 1: Configure Business Rules Framework (BRF)

1. Go to SPRO -> Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Business Transactions -> Dunning -> Dunning by Collection Strategy -> Settings in Business Rule Framework -> Configure Business Rules Framework
   
2. Click on "Wizard" button.
   
3. Start: Click "Continue" button.
   
4. Define Application Class (Cross-Client): Enter Application Class Name and Description, After that click "Continue" button.
   
5. Define Cross-Client Settings: 
1. Trace Class: CL_TRACE_BRF
2. Impl. Tree Class: CL_WB_TREE_DEFAULT_BRF
3. General Services: CL_FKK_BRF_APPLCLASS_SERVICES. After that, click "Continue" button.
   
6. Select Object Types (Implementing Classes): Click "Continue" button.
   
7. Edit Short Texts of Object Types: Click "Continue" button.
   
8. Define the First Context: Click "Continue" button. (We don't want to create Context over here because Dunning is getting Context differently)
   
9. Define the First BRF Event: Click "Continue" button. (We don't want to create Event over here because Dunning is using different Implementing Class)
   
10. Complete: Click "Complete" button.
    

Collection Strategy: BRF: Option 1: Step 1: Create Client-Independent Application Class

1. Go to SPRO-> Financial Accounting (New) -> Contract Accounts Receivable and Payable -> Business Transactions -> Dunning -> Dunning by Collection Strategy -> Settings in Business Rule Framework -> Create Client-Independent Application Class.
   
2. Enter Application Class Name
   
3. Enter Application Class Description and then click "Save" button.