Showing posts with label Configuration. Show all posts
Showing posts with label Configuration. Show all posts

Monday, September 14, 2020

AMI: Step 8: Advance Metering Infrastructure of Capability Activation Group (AMICAG)

  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Activation Groups for AMI Capabilities
  2. The purpose of this configuration is to define activation group that can be used to activate or deactivate AMI capabilities of a meter independently of the capabilities of the corresponding AMS (Advanced Metering System) and AMCG (Advanced Meter Capability Group). This is an optional field on meter.
  3. Enter "Activation Group Name" and its description.
  4. Select "AMI Capabilities for Activation Group". Assign AMI capabilities to the activation group
  5. Note: AMS and AMCG must support the capabilities as well if you need to turn on the capabilities in activation group.

Friday, August 14, 2020

AMI: Step 7: Determination Group of Advance Meter Capability Group (AMCG DG)

  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Advanced Meter Capabilities
  2. Select "Determination Group of Advance Meter Capability Group (AMCG DG)". The purpose of this configuration is to determine advance meter capability group. It is assigned to device category, and if default AMCG is selected, it will be assigned to AMI meter during meter creation.
  3. Enter "Advance Meter Capability Group Determination Group Name" and its description.
  4. Select "Advance Meter Capability Group of a Determination Group (AMCG DG)". Assign "Advance Meter Capability Group (AMCG)" to this determination group.

Tuesday, July 14, 2020

AMI: Step 6: Capability Group of Device (AMCG)

  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Advanced Meter Capabilities
  2. The purpose of this configuration is to group functions of a device
  3. Select "Capability Group for Device". Enter "Advance Meter Capability Group" (AMCG) Number and its description
  4. Select "Capabilities of Device". Assign "Advance Meter Capabilities" to this device.

Tuesday, June 30, 2020

AMI: Step 5: Advanced Metering System of a Determination Group (AMS DG)

  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Advanced Meter Capabilities
  2. Select "Advanced Metering System Determination Group". The purpose of this configuration is to group AMS system, this determination group is assigned to device category, if default AMS is selected, it will be assigned to AMI meter during meter creation.
  3. Enter "AMS Determination Group Name" and its description.
  4. Select "Advanced Metering System of a Determination Group". Assign AMS to "AMS Determination Group".

Sunday, June 14, 2020

AMI: Step 4: Advance Metering System (AMS)

  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Advanced Meter Capabilities
  2. Select "Advanced Metering System". The purpose of this configuration is to define system that AMI meter is connected in the advanced metering infrastructure.
  3. Enter AMS system name, validity date, description of the AMS system, MDUS that it is communicating to, and the capability group of AMS

Thursday, May 14, 2020

AMI: Step 3: Capability Group of Advanced Metering System (AMS CG)


  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Advanced Meter Capabilities
  2. Select Capability Group of Advanced Metering System. The purpose of this configuration is to group of functions of an advanced metering system.
  3. Enter "Capability Group Number" and its description
  4. Select "Capabilities of Advanced Metering System", after that, assign capabilities into this group.

Tuesday, April 14, 2020

AMI: Step 2: Meter Data Unification & Synchronization (MDUS)


  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Advanced Meter Capabilities
  2. Select "Meter Data Unification & Synchronization", enter MDUS system name. MDUS system is an interface between advanced metering systems and the SAP system.

Saturday, March 14, 2020

AMI: Step 1: Advanced Meter Capabilities

  1. Go to SPRO -> SAP Utilities -> Advanced Metering Infrastructure -> Basic Settings -> Define Advanced Meter Capabilities
  2. SAP predefined the following advanced meter capabilities:
    1. Remote disconnection
    2. Remote reconnection
    3. Remote meter reading
    4. Manual meter reading using AMS
    5. On-demand meter reading
    6. Request operational state
    7. Receive message
  3. If AMS-Rel. is checked, this capability will be available when configuring Capability Group of Advanced Metering System
  4. If AMCG-Rel. is checked, this capability will be available when configuring Capabilities of Device
  5. Use 9000-9999 for custom entries

Sunday, September 1, 2019

Billing: Create Custom Outsort Check (Part 1)


  1. Go to SPRO -> SAP Utilities -> Tools -> System Modifications -> User-Defined Enhancements for Billing -> Define Check List for Billing
  2. Enter new billing validation name, and text for the parameters

Tuesday, November 27, 2018

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".

Thursday, August 17, 2017

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

Thursday, July 27, 2017

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.

Tuesday, June 27, 2017

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. 

Friday, May 26, 2017

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.

Wednesday, April 26, 2017

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

Sunday, March 26, 2017

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.