---
title: "Detailed Design — JBSbatKKOpsvkeiDelTrgtChsht.setDelTrgtDataMyHp()"
created_at: "2026-06-28"
updated_at: "2026-06-28"
file: "source/koptBatch/src/eo/business/service/JBSbatKKOpsvkeiDelTrgtChsht.java"
loc: 37
---

# Business Logic — JBSbatKKOpsvkeiDelTrgtChsht.setDelTrgtDataMyHp() [37 LOC]

| Field | Value |
|-------|-------|
| Fully Qualified Name | `eo.business.service.JBSbatKKOpsvkeiDelTrgtChsht` |
| Layer | Service (Batch Service Component) |
| Module | `service` (Package: `eo.business.service`) |

## 1. Role

### JBSbatKKOpsvkeiDelTrgtChsht.setDelTrgtDataMyHp()

This method is responsible for configuring **delete-target data** for a customer's My Homepage (My HP) service in the K-Opticom telecom billing system. It is one of several type-specific delete-target configuration methods called from the batch processing entry point `execute()`, which dispatches based on the `opSvcCd` (operation service code). When the service code equals `"B002"` (My Homepage), `setDelTrgtDataMyHp` is invoked to determine what data should be flagged for deletion.

The method implements a **dual-branch routing pattern** — it independently checks for the presence of a URL value (the original homepage deletion trigger) and a webID value (added in IT1-2013-0000285, for aging-update deletion). Each branch, when triggered, initializes a new output map via `initData()`, configures it with the appropriate deletion transaction type (`DEL_TRAN_SBT`), deletion target type (`DEL_TRGT_SBT`), and the relevant data field (URL or webID), then adds it to the output bean for downstream processing. This design allows **both a URL and a webID to be present simultaneously**, resulting in two separate delete-target output records being produced.

In the larger system, this method serves as a **service-type-specific configuration helper** — it is a private method exclusively called by `JBSbatKKOpsvkeiDelTrgtChsht.execute()`. It does not perform any database operations itself; rather, it transforms input batch data into structured output records that downstream components use to identify and process deletion targets.

## 2. Processing Pattern (Detailed Business Logic)

```mermaid
flowchart TD
    START(["setDelTrgtDataMyHp(inMap, outputBean)"])
    START --> GET_URL["Extract URL from inMap.KEY_URL"]

    GET_URL --> CHECK_URL{"URL != null AND not empty?"}

    CHECK_URL -->|True| URL_TRUE["Process URL branch"]
    CHECK_URL -->|False| CHECK_WEBID["Check webID branch"]

    URL_TRUE --> URL_INIT["outMap = initData(inMap)"]
    URL_INIT --> URL_SET_DELSBT["outMap.setString(DEL_TRAN_SBT, getDelTranSbt(inMap))"]
    URL_SET_DELSBT --> URL_SET_DEL_TRGT["outMap.setString(DEL_TRGT_SBT, DEL_TRGT_SBT_URL]")
    URL_SET_DEL_TRGT --> URL_SET_URL["outMap.setString(URL, url)"]
    URL_SET_URL --> URL_SET_OUTFLG["outMap.setOutFlg(true)"]
    URL_SET_OUTFLG --> URL_ADD["outputBean.addOutMapList(outMap)"]
    URL_ADD --> CHECK_WEBID

    CHECK_WEBID --> GET_WEBID["Extract webID from inMap.WEB_ID"]
    GET_WEBID --> CHECK_WEBID_VAL{"webID != null AND not empty?"}

    CHECK_WEBID_VAL -->|True| WEBID_TRUE["Process webID branch"]
    CHECK_WEBID_VAL -->|False| END_NODE(["End"])

    WEBID_TRUE --> WEBID_INIT["outMap = initData(inMap)"]
    WEBID_INIT --> WEBID_SET_DEL_TRAN["outMap.setString(DEL_TRAN_SBT, DEL_TRAN_SBT_AGING_UPD"]
    WEBID_SET_DEL_TRAN --> WEBID_SET_DEL_TRGT["outMap.setString(DEL_TRGT_SBT, DEL_TRGT_SBT_WEBID"]
    WEBID_SET_DEL_TRGT --> WEBID_SET_WEBID["outMap.setString(WEB_ID, webID)"]
    WEBID_SET_WEBID --> WEBID_SET_OUTFLG["outMap.setOutFlg(true)"]
    WEBID_SET_OUTFLG --> WEBID_ADD["outputBean.addOutMapList(outMap)"]
    WEBID_ADD --> END_NODE
```

### Constant Resolution

| Constant | Resolved Value | Business Meaning |
|----------|---------------|------------------|
| `DEL_TRGT_SBT_URL` | `"07"` | Deletion target type — URL (My Homepage) |
| `DEL_TRGT_SBT_WEBID` | `"14"` | Deletion target type — Web ID |
| `DEL_TRAN_SBT_AGING_UPD` | `"2"` | Deletion transaction type — Aging update |
| `DEL_TRAN_SBT_DEL_SOD_AGING_UPD` | `"3"` | Deletion transaction type — Delete SOD + aging update |
| `KEY_URL` | `"URL"` | Input map key for URL value |
| `KEY_ORDER_UM_FLG` | `"ORDER_UM_FLG"` | Input map key for order issuance flag |
| `JBSbatKK_T_OPSVKEI_ISP.WEB_ID` | `"WEB_ID"` | Table field key for Web ID |

## 3. Parameter Analysis

| No | Parameter Name | Type | Business Description |
|----|---------------|------|---------------------|
| 1 | `inMap` | `JBSbatServiceInterfaceMap` | Input message (denpyo) carrying batch service parameters. Contains the URL of the My Homepage to be checked for deletion (`KEY_URL = "URL"`), the Web ID for aging-update deletion (`WEB_ID` from `JBSbatKK_T_OPSVKEI_ISP`), and the `ORDER_UM_FLG` order issuance flag used by `getDelTranSbt()` to determine whether a registered SOD (Service Order Data) has already been issued. |
| 2 | `outputBean` | `JBSbatOutputItem` | Output container that accumulates delete-target configuration records. This method calls `addOutMapList()` to push one or two prepared `JBSbatServiceInterfaceMap` records into the output, depending on whether the URL branch, webID branch, or both are triggered. |

### Instance Fields / External State Read

| Field | Source | Usage |
|-------|--------|-------|
| `DEL_TRGT_SBT_URL` | Constant in this class = `"07"` | Set as the deletion target type for the URL branch |
| `DEL_TRGT_SBT_WEBID` | Constant in this class = `"14"` | Set as the deletion target type for the webID branch |
| `DEL_TRAN_SBT_AGING_UPD` | Constant in this class = `"2"` | Set as the deletion transaction type for the webID branch |
| `KEY_URL` | Constant in this class = `"URL"` | Input map key to extract the URL value |
| `KEY_ORDER_UM_FLG` | Constant in this class = `"ORDER_UM_FLG"` | Input map key read by `getDelTranSbt()` to determine deletion transaction type |

## 4. CRUD Operations / Called Services

| CRUD | SC / CBS | SC Code | Entity / DB | Operation Description |
|------|----------|---------|-------------|----------------------|
| - | `JBSbatKKOpsvkeiDelTrgtChsht.initData` | - | - | Calls `initData(inMap)` to create and populate a new output map with service contract fields (SVC_KEI_NO, SVKEI_GADTM, OP_SVC_KEI_NO, OPSVC_KEI_GADTM) |
| R | `JBSbatKKOpsvkeiDelTrgtChsht.getDelTranSbt` | - | - | Calls `getDelTranSbt(inMap)` to determine the deletion transaction type by checking the ORDER_UM_FLG flag |
| - | `JBSbatServiceInterfaceMap.getString` | - | - | Reads URL and webID values from the input map |
| - | `JBSbatServiceInterfaceMap.setString` | - | - | Sets DEL_TRAN_SBT, DEL_TRGT_SBT, URL/WEB_ID fields on the output map |
| - | `JBSbatServiceInterfaceMap.setOutFlg` | - | - | Marks the output map with a true flag indicating it is a valid delete-target record |
| C | `JBSbatOutputItem.addOutMapList` | - | - | Adds the configured output map to the output bean's list of delete-target records |

**Classification rationale:**
- This method is a **data transformation/configurator** — it does not directly perform C/R/U/D against database tables. All operations are in-memory map manipulations.
- `initData` and `getDelTranSbt` are sibling private methods within the same class that perform further in-memory data extraction and business logic.
- The ultimate side effect is writing records into `outputBean` via `addOutMapList`, which downstream batch consumers will process.

## 5. Dependency Trace

### Pre-computed evidence from code analysis graph:

Direct callers found: 1 methods.

| # | Caller (Screen/Batch) | Call Chain (Full Path to this Method) | Terminal (SC / CRUD / Entity) |
|---|----------------------|--------------------------------------|-------------------------------|
| 1 | Batch: `JBSbatKKOpsvkeiDelTrgtChsht.execute()` | `execute(inMap)` → `setDelTrgtDataMyHp(inMap, outputBean)` | `initData [-]`, `getDelTranSbt [-]`, `setOutFlg [-]`, `addOutMapList [C]` |

**Call chain detail:**
1. The batch entry point `JBSbatKKOpsvkeiDelTrgtChsht.execute(JBSbatServiceInterfaceMap inMap)` reads the operation service code (`opSvcCd`) from the input.
2. When `opSvcCd` equals `"B002"` (`OP_SVC_CD_MY_HP`), the method dispatches to `setDelTrgtDataMyHp(inMap, outputBean)`.
3. This method performs URL and webID deletion target configuration, pushing results into `outputBean`.
4. No screen or CBS entry points call this method directly — it is exclusively a batch-side helper.

## 6. Per-Branch Detail Blocks

**Block 1** — [IF] `(url != null && !"".equals(url))` (L269)

> Checks whether a URL value is present in the input map. If a non-null, non-empty URL exists, this branch configures the URL-based My Homepage deletion target.

| # | Type | Code |
|---|------|------|
| 1 | SET | `String url = inMap.getString(KEY_URL)` // Extract URL value [-> KEY_URL="URL"] |
| 2 | CALL | `initData(inMap)` // Create and populate output map with service contract fields |
| 3 | SET | `outMap = initData(inMap)` // Store initialized output map |
| 4 | CALL | `getDelTranSbt(inMap)` // Determine deletion transaction type (aging update vs. delete SOD + aging update) |
| 5 | EXEC | `outMap.setString(JBSbatKKIFM160.DEL_TRAN_SBT, getDelTranSbt(inMap))` // Set deletion transaction type [-> DEL_TRAN_SBT="DEL_TRAN_SBT"] |
| 6 | EXEC | `outMap.setString(JBSbatKKIFM160.DEL_TRGT_SBT, DEL_TRGT_SBT_URL)` // Set deletion target type [-> DEL_TRGT_SBT="DEL_TRGT_SBT"] [-> DEL_TRGT_SBT_URL="07"] |
| 7 | EXEC | `outMap.setString(JBSbatKKIFM160.URL, url)` // Set the URL value [-> URL="URL"] |
| 8 | EXEC | `outMap.setOutFlg(true)` // Mark record as valid delete-target |
| 9 | EXEC | `outputBean.addOutMapList(outMap)` // Add configured record to output |

**Block 2** — [IF] `(webID != null && !"".equals(webID))` (L285)

> Checks whether a webID value is present in the input map. If present, this branch configures the webID-based deletion target for the aging-update transaction type. This was added in IT1-2013-0000285 (2013/02/13) to support Web ID-based deletion handling on the My Homepage.

| # | Type | Code |
|---|------|------|
| 1 | SET | `String webID = inMap.getString(JBSbatKK_T_OPSVKEI_ISP.WEB_ID)` // Extract webID value [-> WEB_ID="WEB_ID"] |
| 2 | CALL | `initData(inMap)` // Create and populate output map with service contract fields |
| 3 | SET | `outMap = initData(inMap)` // Store initialized output map |
| 4 | EXEC | `outMap.setString(JBSbatKKIFM160.DEL_TRAN_SBT, DEL_TRAN_SBT_AGING_UPD)` // Set deletion transaction type [-> DEL_TRAN_SBT="DEL_TRAN_SBT"] [-> DEL_TRAN_SBT_AGING_UPD="2"] |
| 5 | EXEC | `outMap.setString(JBSbatKKIFM160.DEL_TRGT_SBT, DEL_TRGT_SBT_WEBID)` // Set deletion target type [-> DEL_TRGT_SBT="DEL_TRGT_SBT"] [-> DEL_TRGT_SBT_WEBID="14"] |
| 6 | EXEC | `outMap.setString(JBSbatKKIFM160.WEB_ID, webID)` // Set the webID value [-> WEB_ID="WEB_ID"] |
| 7 | EXEC | `outMap.setOutFlg(true)` // Mark record as valid delete-target |
| 8 | EXEC | `outputBean.addOutMapList(outMap)` // Add configured record to output |

**Block 3** — [Private Helper Method] `getDelTranSbt(inMap)` (L395)

> Determines the deletion transaction type by checking the `ORDER_UM_FLG` flag. If a registered SOD has already been issued (flag is non-null and non-empty), the transaction type is `"3"` (Delete SOD + aging update). Otherwise, it is `"2"` (Aging update only).

| # | Type | Code |
|---|------|------|
| 1 | SET | `String delTranSbt = null` // Initialize result |
| 2 | SET | `Object orderUmFlg = inMap.get(KEY_ORDER_UM_FLG)` // Get order issuance flag [-> KEY_ORDER_UM_FLG="ORDER_UM_FLG"] |
| 3 | IF | `(orderUmFlg != null && !"".equals(orderUmFlg))` // SOD already issued? |
| 3.1 | SET | `delTranSbt = DEL_TRAN_SBT_DEL_SOD_AGING_UPD` // = "3" [Delete SOD + aging update] |
| 3.2 | ELSE | |
| 3.2.1 | SET | `delTranSbt = DEL_TRAN_SBT_AGING_UPD` // = "2" [Aging update only] |
| 4 | RETURN | `return delTranSbt` |

## 7. Glossary

| Term | Type | Business Meaning |
|------|------|------------------|
| `setDelTrgtDataMyHp` | Method | Set delete-target data configuration for My Homepage — configures what data to delete when a customer's My Homepage service is cancelled |
| `DEL_TRAN_SBT` | Field | Deletion transaction type — classifies the kind of deletion operation ("2" = aging update only, "3" = delete SOD + aging update) |
| `DEL_TRGT_SBT` | Field | Deletion target type — classifies the category of the data to delete ("07" = URL, "14" = Web ID) |
| `DEL_TRGT_SBT_URL` | Constant | Deletion target type value "07" — URL (My Homepage homepage URL) |
| `DEL_TRGT_SBT_WEBID` | Constant | Deletion target type value "14" — Web ID |
| `DEL_TRAN_SBT_AGING_UPD` | Constant | Deletion transaction type value "2" — Aging update (update aging-related data as part of cancellation) |
| `DEL_TRAN_SBT_DEL_SOD_AGING_UPD` | Constant | Deletion transaction type value "3" — Delete SOD + aging update (when a Service Order Data has already been issued) |
| `KEY_URL` | Constant | Input map key "URL" — used to extract the My Homepage URL from input data |
| `KEY_ORDER_UM_FLG` | Constant | Input map key "ORDER_UM_FLG" — order issuance flag that determines whether SOD has been issued |
| `SVC_KEI_NO` | Field | Service contract number — primary key of the service contract table |
| `SVKEI_GADTM` | Field | Service contract registration date/time — when the service contract was registered |
| `OP_SVC_KEI_NO` | Field | Operation service contract number — links to the specific operation/service line item |
| `OPSVKEI_GADTM` | Field | Operation service contract registration date/time |
| `opSvcCd` | Field | Operation service code — classifies the type of service (email, My Homepage, mailing list, fixed IP, 050 number) |
| `OP_SVC_CD_MY_HP` | Constant | Service code "B002" — My Homepage service type |
| `WEB_ID` | Field | Web ID — identifier for the customer's My Homepage login, from the `JBSbatKK_T_OPSVKEI_ISP` table |
| `JBSbatKK_T_OPSVKEI_ISP` | Table | Operation service ISP table — stores ISP-related contract data including Web ID |
| `SOD` | Acronym | Service Order Data — a telecom billing entity representing an ordered service that triggers downstream provisioning |
| `initData` | Method | Initialize output map — extracts service contract and operation service contract identifiers from input and populates the output map with common fields |
| `getDelTranSbt` | Method | Get deletion transaction type — determines whether the deletion should include SOD cancellation or just aging update |
| `inMap` | Parameter | Input denpyo (electronic message) — the batch input carrying service parameters and configuration |
| `outputBean` | Parameter | Output item — the batch output container that accumulates configured delete-target records |
| `setOutFlg` | Method | Set output flag — marks a record as a valid output delete-target for downstream processing |
| `addOutMapList` | Method | Add to output map list — pushes a configured map into the output bean's list |
| `execute` | Method | Main batch processing entry point — dispatches to type-specific delete-target configuration methods based on service code |
| `IT1-2013-0000285` | Change ID | Issue/change tracking ID — the change request that added Web ID support to the My Homepage deletion target processing (2013/02/13) |
| `denpyo` | Japanese term | 電文 — electronic message / data packet in batch processing context |
| `消去対象データ` | Japanese term | Delete-target data — data identified for deletion during service cancellation |
| `エージング更新` | Japanese term | Aging update — a billing data update operation that updates aging-related fields during service cancellation processing |
| `登録SOD発行済み` | Japanese term | Registered SOD already issued — indicates a Service Order Data has been created for this service |
| `登録SOD未発行` | Japanese term | Registered SOD not yet issued — indicates no Service Order Data has been created yet |