2G E// Counters SUMEOABSUCC & SUMOABSUCC

3G / 2G
,
1

Hello, E// exports I hope you all have a nice night :slight_smile:
I’ve a small question, in my network we use SAP BI Launch for statists and analysis so I want to ask in which universe can i found these two counter ( SUMEOABSUCC & SUMOABSUCC )

Thanks.

2

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

3

SUMEOABSUCC–Successful outgoing S1 interface handover count

SUMOABSUCC-Successful outgoing S1 interface total event count( full ymobility)

4

Two separate things here, worth splitting:

  1. Which SAP BI universe. That one only your own BO team can answer — universes are the semantic
    layer someone in your org built on top of the Ericsson PM database, so the universe name and which
    folder these objects sit in are specific to your deployment, not standard across operators. Fastest
    path: in your ENIQ / PM database these map to a formula on a measurement type (MO class), so ask
    whoever owns your BO universe design which universe is built over that PM subject area — or search
    the universe’s object list directly for the counter name. There’s no global universe name anyone
    outside your OSS can give you.

  2. Before you build a KPI on them, sanity-check the counter identity. This thread is tagged 2G/3G,
    but “S1 interface” is an LTE/EPC interface — 2G/GSM handovers don’t run over S1. So either these are
    actually LTE counters (and the 2G tag is off), or the “S1 handover” definition above belongs to a
    similarly-named counter and isn’t right for these two. Confirm the exact definition and the MO class
    against your Ericsson counter library (the CPI / Alex counter description for your BSC or eNodeB SW
    release) before you trust the formula — the name alone has burned people who mapped a look-alike
    counter. Once you know the MO class it belongs to, that also tells you which universe subject area
    to look in.