AMI Capabilities : Operational Status

This post is on the basic customizing for AMI capabilities of a device with an execution of the Operational State capability (more on this here).

• The AMI Capability is defined at 2 levels: Advanced Metering System (AMS) and Device.
• A capability has to be defined for both AMS and Device for SAP to process. SAP takes into account all the capabilities that have been predefined. Any custom capability is not handled by SAP processes.
• We need to define the determination group for AMS and Device. These are defined in the Device Category. So once the Device Category has been defined as ‘Advanced Meter’ we need to maintain these parameters. So it’s like another level of abstraction.

So below are the SAP standard AMI capabilities. The one defined in 9* are custom. The AMS check box is for relevant for Advance Metering Systems and the one for AMCG is relevant for Devices.

So for the AMS we have the below AMI capabilities defined. I had previously defined 91 – for AMS and 92 – for AMCG(Device). We can see that in F4 help all are shown but we should assign only the ones which are checked for AMS here. If we select 92 we get an error and the table gets locked. Possibly SAP should correct this error. 🙂

Here we define the AMI capabilities of the Device. Here too we get all AMI capabilities in F4 but allocate only the ones suitable for the Device.

We can define default capability group in the Determination group if we have more than one capability groups. Here we have one each only.

Now we can allocate them to the Device Category as shown below.

So now I am creating a Device with material as this Device Category just defined above. Below is the AMI data of the device. As I had written earlier only predefined AMI capabilities allocated for both the AMs and Device shall be used by SAP. They would be highlighted in green always. Shown below are the capabilities which would work in green.

Now I make changes in the AMI capabilities of the Device and include 6 – Request Operational State as shown below.

Now we can see that this has also been highlighted in green as this is now a common capability between the AMS and the Device.

So we may need to determine the current operation state of an AMI device for many reasons.
Like we want to query whether the device is supplied from the grid and whether it is available to the end customer.

We can request the operation state of an advanced meter from the device transactions and the transactions for the connection object.

The operation state request is made using the enterprise serviceUtilitiesDeviceERPSmartMeterOperationalStateByIDQuery.
The response is transmitted by the enterprise serviceUtilitiesDeviceERPSmartMeterOperationalStateByIDResponse
and returns one of the following values as the overall status:
• Unknown
• Inactive
• Active
There are different Type Codes (i.e. what all data is to be sent for confirmation of Operational status) for Operational status which need to be sent in the request.
• 0001 Overall Status
• 0002 Communication Status
• 0003 Disconnection Status

The AMI Monitoring would like below.

Once the confirmation is received the xml status changes.

There is a standard Deletion of Operational State report to delete requested operational states.
Report is REAMI_DELETE_OPERATIONAL_STATE.

If we don’t select the check box in the General Data tab then this report will just serve as log to show which all states will be deleted.

When we select the check box the state and all its attributes will be deleted.

Also the request would not be shown in the device.

That’s all.