Billing & Charging
Routes under: bill
- bill > area > add
- bill > area > all
- bill > deposit > add
- bill > deposit > all
- bill > proc > all
- bill > serbill > all
- bill > serdoc > all
bill > area > add
bill > area > add
Route: bill/area/add
URL: https://admin.myslbb.com/#/bill/area/add
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Name, Description, Bill Base Month, Bill Day
- Actions detected: Auto, Close, Billing, Billing Area, Create Billing Area
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
create_new
Captured URL: https://admin.myslbb.com/#/bill/area/add
bill > area > all
bill > area > all
Route: bill/area/all
URL: https://admin.myslbb.com/#/bill/area/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Billing, Billing Area, Add Billing Area, Clear, BLA/-0001, Default Billing Area
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/bill/area/all
ui_tab_1
Captured URL: https://admin.myslbb.com/#/bill/area/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/bill/area/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/bill/area/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/bill/area/all
bill > deposit > add
bill > deposit > add
Route: bill/deposit/add
URL: https://admin.myslbb.com/#/bill/deposit/add
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Deposit Name, Deposit Type
- Actions detected: Auto, Close, Billing, Deposit Management, Save, Cancel
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
create_new
Captured URL: https://admin.myslbb.com/#/bill/deposit/add
bill > deposit > all
bill > deposit > all
Route: bill/deposit/all
URL: https://admin.myslbb.com/#/bill/deposit/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Actions detected: Auto, Close, Billing, Deposit Management, Add Deposit, Clear
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/bill/deposit/all
ui_tab_1
Captured URL: https://admin.myslbb.com/#/bill/deposit/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/bill/deposit/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/bill/deposit/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/bill/deposit/all
bill > proc > all
bill > proc > all
Route: bill/proc/all
URL: https://admin.myslbb.com/#/bill/proc/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Select Date, Select Billing Area
- Actions detected: Auto, Close, Billing, Billing Process, Clear
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/bill/proc/all
ui_tab_1
Captured URL: https://admin.myslbb.com/#/bill/proc/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/bill/proc/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/bill/proc/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/bill/proc/all
bill > serbill > all
bill > serbill > all
Route: bill/serbill/all
URL: https://admin.myslbb.com/#/bill/serbill/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Search Field, Search Type
- Actions detected: Auto, Close, Billing, Billing Area, Clear, Cult Fit, sybr_hiranandani_cult, abdul rehaman rashid maredia, abdul22, r.e r.e, r.e, dharamshingh sonar, dharamshingh22, vijay panchal, s_vijay, sanjay rana, rana22, rahul sharma, rahulsharma22, Khan
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/bill/serbill/all
ui_tab_1
Captured URL: https://admin.myslbb.com/#/bill/serbill/all
common_tab_1
Captured URL: https://admin.myslbb.com/#/bill/serbill/all
common_tab_2
Captured URL: https://admin.myslbb.com/#/bill/serbill/all
bill > serdoc > all
bill > serdoc > all
Route: bill/serdoc/all
URL: https://admin.myslbb.com/#/bill/serdoc/all
Overview
This page is a draft SOP reference for the above screen in i2i Core OSS/BSS. It is auto-generated from UI exports and should be reviewed for operational correctness before customer release.
When to Use
- Use this screen for the workflow represented by this route.
- Do not make billing/AAA/provisioning-impacting changes without required authorization.
Typical Workflow
- Verify you are working on the correct entity (Customer/Account/Service).
- Review the current lifecycle state before making changes.
- Apply changes and validate system response.
- Confirm downstream impact (AAA/Provisioning/Billing) where applicable.
Field & Action Hints (Auto-detected)
- Fields detected: Select Partner, Date Range, Billing Type
- Actions detected: Auto, Close, Billing, Documents List, Clear Filters
Validation & Safety Checks
- Confirm identifiers before saving.
- Confirm lifecycle state allows the change.
- Confirm rollback/support path exists for production actions.
Escalation Guidance
- L1: Verify input, permissions, and entity state.
- L2: Validate dependencies and downstream state.
- L3/Admin: Policy/config changes or suspected defect.
Screenshots
default
Captured URL: https://admin.myslbb.com/#/bill/serdoc/all
default
Captured URL: https://admin.myslbb.com/#/bill/serdoc/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/bill/serdoc/all
drilldown_one_item
Captured URL: https://admin.myslbb.com/#/bill/serdoc/all