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.
   

Billing: Define Checks per Outsorting Check Group for Billing

1. Go to SPRO -> SAP Utilities -> Contract Billing -> Billing Execution -> Outsorting for Billing -> Define Checks per Outsorting Check Group for Billing
   
2. Enter configuration details:
   
3. Explanation:
   

   Field Name	Usage
   Outsort. Chk grp	Name of the Outsorting Check Group
   Billing Trans.	01           Periodic Billing (01) 02           Interim Billing (02) 03           Final Billing for Move-Out (03) 04           Period-End Billing (04) 05           Service Territory Transfer (05) 06           Manual Credit Memo/Backbilling (06) 07           Contract Change (07) 08           Customer change (08)
   Consecutive no.	Consecutive number of checking per billing transaction
   Mass Simulation	No Restrictions 1              Do Not Carry Out Check in Mass Simulation 2              Only Carry Out Check in Mass Simulation
   Bill. Validation	Refer to Value Table TE007
   Parameters 1 to 4	Parameters for outsorting validation, these parameters behave differently per validation, typically used as range of amount to be validated
   Parameter 5	Parameter for outsorting validation, this parameter accepts characters input
   Text	Description of the outsorting check group defined.

4. This outsort check group can then be assigned to contract.

Billing: Define Outsorting Check Groups for Billing

1. Go to SPRO -> SAP Utilities -> Contract Billing -> Billing Execution -> Outsorting for Billing -> Define Outsorting Check Groups for Billing
   
2. Enter Outsorting Check Group Name and its Text (Description)
   

Invoicing: Define Manual Bill Outsorting for Invoicing

1. SPRO -> SAP Utilities -> Invoicing -> Invoice Processing -> Outsorting for Invoicing -> Define Manual Bill Outsorting for Invoicing
   
2. Enter the reason for manual bill outsorting for invoicing, description, number of manual outsorting, outsorting for invoice or bill printing.
   
3. Explanation:
   

   Field Name	Usage
   Man. OS inv	Reason for Manual Outsorting Invoice
   Text	Description of the manual outsorting invoice
   No. man.OS	Number of manual outsort, this will be the default number of outsortings upon entering the reason for manual outsorting invoice. The number of outsortings will be reduced whenever the contract account gets invoiced.
   OutSrt. Invoic.	Indicates that this is an outsorting for Invoicing
   OutSrt. Print.	Indicates that this is an outsorting for Bill Printing

AMI: Define External VEE Codes

1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define External VEE Codes
   
2. Enter VEE Code and its description.
   
3. VEE stands for Validation, Estimation, Editing of register read or interval data in external system. 
4. This is assigned at register level.
5. In SAP, VEE code is for information only and is not used for meter readings validation.
6. VEE codes defined here should correspond to the codes used in external system.