# Business Logic — JKKAdchgHakkoSODCC.htclNoDslOdrCtrl() [752 LOC]

| Field | Value |
|-------|-------|
| Fully Qualified Name | `com.fujitsu.futurity.bp.custom.common.JKKAdchgHakkoSODCC` |
| Layer | CC / Common Component (Shared service-order control layer) |
| Module | `common` (Package: `com.fujitsu.futurity.bp.custom.common`) |

## 1. Role

### JKKAdchgHakkoSODCC.htclNoDslOdrCtrl()

This method implements the **Light Phone Cancellation Order Control Process** (光電話番号解約オーダ制御処理). It is the central orchestrator responsible for generating the correct set of Service Order Data (SOD) records when a light phone (eo光電話) service is being cancelled, whether as a standalone cancellation, a move-related cancellation (移転), or a withdrawal-completion (撤去完了) scenario.

The method handles **four primary service branches** based on the order execution trigger (`odr_exec_div`):
1. **New-service completion** (`ODR_EXEC_DIV_NEW_END = "3"`): Checks for phone number changes, address changes, and existing DSL orders to determine whether SIP cancellation SODs should be issued.
2. **Withdrawal completion** (`ODR_EXEC_DIV_DSL_END = "2"`): Unconditionally fires SIP cancellation orders.
3. **Address-registration creation** (`ODR_EXEC_DIV_AD_CHG = "1"`): Pass-through behavior.
4. **Other triggers**: Pass-through or no-op.

It implements a **dispatch-and-delegate design pattern**: the method first gathers all relevant device and contract data (VA equipment, multi-function router info, FTTH auth registration), then branches into distinct order-generation sub-flows — OLS (optical line terminal) setup/cancellation, multi-function router VA-disc setup/cancellation, SIP/ENUM cancellation, emergency notice/cancellation, and Radius authentication cancellation. Each sub-flow delegates to `addSOD()` to create individual SOD records with specific order content codes.

As a **shared utility called by many screens and cancellation flows**, this method sits at the heart of the K-Opticom customer core system's service-order fulfillme