# Business Logic — JKKCancelSvcWribCC.editErrInfoEKK1391C040() [104 LOC]

| Field | Value |
|-------|-------|
| Fully Qualified Name | `com.fujitsu.futurity.bp.custom.common.JKKCancelSvcWribCC` |
| Layer | CC/Common Component |
| Module | `common` (Package: `com.fujitsu.futurity.bp.custom.common`) |

## 1. Role

### JKKCancelSvcWribCC.editErrInfoEKK1391C040()

This method performs error information mapping for the **data extraction item settings completion** stage (データ抽出項目設定完了のエラー情報マッピング処理) within the telecom service contract cancellation workflow. It is a private utility method in the cancel service write common component, responsible for propagating CBS (Central Billing System) response status and per-field validation errors back into the request parameter object so that the presentation layer can display meaningful error messages to the operator.

The method implements a **status-priority override pattern**: it compares the CBS template's return status against the BP-side return code, and only pushes the CBS status upward if it represents a more severe condition. This ensures that lower-priority or client-side errors do not silently override genuine service-level failure codes coming from downstream CBS processing.

It then processes **six error-specific fields** from the CBS response template — covering data extraction setup number, completion type code, end date, movement classification, completion opportunity code, and pre-update timestamp — copying each into the operation work map's data container using a "copy-on-absent" strategy (only writing if the target key does not already exist). This prevents overwriting previously set values during multi-record or retry scenarios.

The method acts as a **shared error-translation bridge** between the CBS response layer and the screen mapping layer. It is called by `editRetEKK1391C040()`, which orchestrates the broader cancel-service-write return flow, and follows this call with additional error-info aggregation via `TemplateErrorUtil.getErrorInfo()`.

## 2. Processing Pattern (Detailed Business Logic)

```mermaid
flowchart TD
    START(["editErrInfoEKK1391C040
(param, templates, returnCode, fixedText)"])

    START --> A1["Extract template = templates[0]"]
    A1 --> A2["templateStatus = template.getInt
(EKK1391C040CBSMsg.STATUS)"]

    A2 --> COND1{returnCode != 0?}
    COND1 -- Yes --> COND1_YES["templateStatus = 9000
(Error status override)"]
    COND1 -- No --> COND2

    COND1_YES --> COND2{JCMAPLConstMgr.getString
(\"RETURN_MESSAGE_\" +
formatStatus) == null?}
    COND2 -- Yes --> COND2_YES["templateStatus = 0
(Invalid status -> default)"]
    COND2 -- No --> BP_STATUS

    COND2_YES --> BP_STATUS["bpStatus = param.getControlMapData
(SCControlMapKeys.RETURN_CODE)"]

    BP_STATUS --> COND3{templateStatus > bpStatus?}
    COND3 -- Yes --> COND3_YES["Push CBS status:
setControlMapData(RETURN_CODE,
formatStatus)
setControlMapData(RETURN_MESSAGE,
message)"]
    COND3 -- No --> WORK_AREA

    COND3_YES --> WORK_AREA["workMap = param.getMappingWorkArea()
Ensure workMap is non-null
(initialize HashMap if null)"]

    WORK_AREA --> DATA_FETCH["inMap = param.getData(fixedText)
(Get operation data container)"]

    DATA_FETCH --> FIELD1{!template.isNull
(DCHSKMST_NO_ERR)?}
    FIELD1 -- Yes --> F1_CHECK{!inMap.containsKey
(\"dchskmst_no_err\")?}
    F1_CHECK -- Yes --> F1_PUT["inMap.put(\"dchskmst_no_err\",
 template.getString(DCHSKMST_NO_ERR))"]
    F1_CHECK -- No --> FIELD2
    F1_PUT --> FIELD2
    FIELD1 -- No --> FIELD2

    FIELD2{!template.isNull
(DCHSKMST_FIN_SBT_CD_ERR)?} --> F2_CHECK{!inMap.containsKey
(\"dchskmst_fin_sbt_cd_err\")?}
    F2_CHECK -- Yes --> F2_PUT["inMap.put(\"dchskmst_fin_sbt_cd_err\",
 template.getString(DCHSKMST_FIN_SBT_CD_ERR))"]
    F2_CHECK -- No --> FIELD3
    F2_PUT --> FIELD3
    FIELD2 -- No --> FIELD3

    FIELD3{!template.isNull
(DCHSKMST_END_YMD_ERR)?} --> F3_CHECK{!inMap.containsKey
(\"dchskmst_end_ymd_err\")?}
    F3_CHECK -- Yes --> F3_PUT["inMap.put(\"dchskmst_end_ymd_err\",
 template.getString(DCHSKMST_END_YMD_ERR))"]
    F3_CHECK -- No --> FIELD4
    F3_PUT --> FIELD4
    FIELD3 -- No --> FIELD4

    FIELD4{!template.isNull
(IDO_DIV_ERR)?} --> F4_CHECK{!inMap.containsKey
(\"ido_div_err\")?}
    F4_CHECK -- Yes --> F4_PUT["inMap.put(\"ido_div_err\",
 template.getString(IDO_DIV_ERR))"]
    F4_CHECK -- No --> FIELD5
    F4_PUT --> FIELD5
    FIELD4 -- No --> FIELD5

    FIELD5{!template.isNull
(DCHSKMST_FIN_OPTY_CD_ERR)?} --> F5_CHECK{!inMap.containsKey
(\"dchskmst_fin_opty_cd_err\")?}
    F5_CHECK -- Yes --> F5_PUT["inMap.put(\"dchskmst_fin_opty_cd_err\",
 template.getString(DCHSKMST_FIN_OPTY_CD_ERR))"]
    F5_CHECK -- No --> FIELD6
    F5_PUT --> FIELD6
    FIELD5 -- No --> FIELD6

    FIELD6{!template.isNull
(UPD_DTM_BF_ERR)?} --> F6_CHECK{!inMap.containsKey
(\"upd_dtm_bf_err\")?}
    F6_CHECK -- Yes --> F6_PUT["inMap.put(\"upd_dtm_bf_err\",
 template.getString(UPD_DTM_BF_ERR))"]
    F6_CHECK -- No --> RETURN
    F6_PUT --> RETURN
    FIELD6 -- No --> RETURN

    RETURN(["return param"]) --> END(["End"])
```

**Processing Summary:**

The method follows three distinct processing phases:

1. **Status Priority Resolution** — Extracts the CBS response status, overrides it to `9000` if a non-zero return code indicates an error, then validates the status against `JCMAPLConstMgr` to reject unrecognized codes (resetting to `0`). Compares the resolved template status against the BP-side return code and only propagates the CBS status if it is strictly higher — a priority-based escalation mechanism.

2. **Work Area Initialization** — Ensures the mapping work area exists (creates a `HashMap` if null) and retrieves the operation data container identified by the `fixedText` key.

3. **Error Field Propagation** — For each of the six error fields defined in `EKK1391C040CBSMsg`, checks whether the template contains a non-null value and whether the target data map lacks an existing entry. Only if both conditions are met does it copy the error value from the template into the work map. This "copy-on-absent" pattern preserves previously set error values during repeated or multi-pass operations.

## 3. Parameter Analysis

| No | Parameter Name | Type | Business Description |
|----|---------------|------|---------------------|
| 1 | `param` | `IRequestParameterReadWrite` | The request parameter object carrying the full screen-to-backend data contract — including control map data (return codes, error lists), the mapping work area (operation-level data containers), and field data keyed by `fixedText`. This is the central data bus passed across the BP (Business Process) layer. |
| 2 | `templates` | `CAANMsg[]` | An array of CBS response message templates from the `EKK1391C040` CBS interaction. Each template carries the response fields from the data extraction item settings completion process, including per-field error indicators and status codes. Only `templates[0]` is consumed. |
| 3 | `returnCode` | `int` | The return code from the CBS or upstream processing. A value of `0` indicates success; any non-zero value signals an error, triggering a status override to `9000`. This drives the status priority resolution logic. |
| 4 | `fixedText` | `String` | A key identifier used to retrieve the operation-level data map from `param.getData(fixedText)`. Acts as a namespace separator, allowing multiple data contexts to coexist within the same `IRequestParameterReadWrite` instance. |

**External State:**

| Field | Description |
|-------|-------------|
| `JCMAPLConstMgr` | Global configuration manager providing localized return message strings keyed by `RETURN_MESSAGE_XXXX` pattern. |
| `SCControlMapKeys` | Control map key constants for `RETURN_CODE`, `RETURN_MESSAGE`, and `ERROR_INFO` entries in the parameter's control map. |

## 4. CRUD Operations / Called Services

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

| CRUD | SC / CBS | SC Code | Entity / DB | Operation Description |
|------|----------|---------|-------------|----------------------|
| - | `JACBatCommon.isNull` | JACBatCommon | - | Utility null-check; used by other callers |
| - | `JACbatRknBusinessUtil.isNull` | JACbatRknBusiness | - | Utility null-check; used by other callers |
| - | `JCHbatSeikyKaknoBusinessUtil.isNull` | JCHbatSeikyKaknoBusiness | - | Utility null-check; used by other callers |
| - | `JBSbatACInsentetivePrcInfoSaksei.isNull` | JBSbatACInsentetivePrcInfoSaksei | - | Utility null-check; used by other callers |
| - | `JBSbatAKCHSeikyYsoInfMake.isNull` | JBSbatAKCHSeikyYsoInfMake | - | Utility null-check; used by other callers |
| R | `JBSbatDKNyukaFinAdd.getData` | JBSbatDKNyukaFinAdd | - | Data retrieval utility; used by other callers |
| R | `JBSbatFUCaseFileRnkData.getString` | JBSbatFUCaseFileRnkData | - | Data retrieval utility; used by other callers |
| R | `JBSbatFUMoveNaviData.getString` | JBSbatFUMoveNaviData | - | Data retrieval utility; used by other callers |
| R | `JBSbatZMAdDataSet.getString` | JBSbatZMAdDataSet | - | Data retrieval utility; used by other callers |
| R | `JFUeoTelOpTransferCC.getData` | JFUeoTelOpTransferCC | - | Data retrieval utility; used by other callers |
| R | `JFUTransferCC.getData` | JFUTransferCC | - | Data retrieval utility; used by other callers |
| R | `JFUTransferListToListCC.getData` | JFUTransferListToListCC | - | Data retrieval utility; used by other callers |
| R | `JESC0101B010TPMA.getString` | JESC0101B010TPMA | - | Data retrieval utility; used by other callers |
| R | `JESC0101B020TPMA.getString` | JESC0101B020TPMA | - | Data retrieval utility; used by other callers |
| R | `KKW12701SFLogic.getData` | KKW12701SFLogic | - | Data retrieval utility; used by other callers |

### Methods specifically called within `editErrInfoEKK1391C040` (actual local calls):

| CRUD | SC / CBS | SC Code | Entity / DB | Operation Description |
|------|----------|---------|-------------|----------------------|
| R | `template.getInt` | EKK1391C040CBSMsg | - | Reads the `status` field from the CBS response template — the completion status code for the data extraction item settings process |
| R | `JCMAPLConstMgr.getString` | JCMAPLConstMgr | - | Looks up a localized return message string by key `RETURN_MESSAGE_XXXX` to validate status code legitimacy |
| R | `param.getControlMapData` | SCControlMapKeys | - | Reads the current BP-side return code from the control map for status priority comparison |
| W | `param.setControlMapData` | SCControlMapKeys | - | Writes the resolved return code and message back into the control map when template status takes priority |
| R | `param.getMappingWorkArea` | - | - | Retrieves the operation-level mapping work area map from the parameter object |
| W | `param.setMappingWorkArea` | - | - | Initializes the work area map if it was null, ensuring downstream processing has a container |
| R | `param.getData` | - | - | Retrieves the operation data map identified by the `fixedText` key — the container for field-level error values |
| R/W | `template.isNull` (x6) | EKK1391C040CBSMsg | - | Checks whether each error field in the CBS response template contains a value (six separate checks: `DCHSKMST_NO_ERR`, `DCHSKMST_FIN_SBT_CD_ERR`, `DCHSKMST_END_YMD_ERR`, `IDO_DIV_ERR`, `DCHSKMST_FIN_OPTY_CD_ERR`, `UPD_DTM_BF_ERR`) |
| R/W | `inMap.containsKey` (x6) | - | - | Checks whether the data map already has a value for the error key — the "copy-on-absent" guard |
| R/W | `inMap.put` (x6) | - | - | Writes the error field value from the template into the data map, guarded by `containsKey` checks |
| R | `template.getString` (x6) | EKK1391C040CBSMsg | - | Extracts the actual error string value for each error field that passed both the `isNull` and `containsKey` guards |

**CRUD Classification Rationale:**
- This method performs **zero direct database or SC calls**. It is purely an in-memory data mapping and transformation method.
- All "R" (Read) operations are on the `IRequestParameterReadWrite` parameter object and the `CAANMsg` template — extracting control map data, work area maps, and CBS response fields.
- All "W" (Write) operations update the same parameter object's control map and work area — setting return codes, return messages, work area containers, and error field values.
- No Create, Update (of persistent entities), or Delete operations occur in this method.

## 5. Dependency Trace

| # | Caller (Screen/Batch) | Call Chain (Full Path to this Method) | Terminal (SC / CRUD / Entity) |
|---|----------------------|--------------------------------------|-------------------------------|
| 1 | Screen:KKSV0313 | `KKSV0313OP_EKK1391C040BSMapper.doMapping` → `editErrInfoEKK1391C040` | `template.getInt(status) [R]`, `param.getControlMapData(RETURN_CODE) [R]`, `param.setControlMapData(RETURN_CODE) [W]`, `param.getData(fixedText) [R]`, `template.getString(DCHSKMST_NO_ERR) [R]`, `inMap.put(dchskmst_no_err) [W]`, (5 additional error field gets + puts) |
| 2 | KKManAplyWribSvcKeiCC | `SvcKeiCC.editAndWriteReturn` → `editErrInfoEKK1391C040` | Same terminal set as KKSV0313 |

**Caller Details:**

- **JKKCancelSvcWribCC.editRetEKK1391C040()** — This is the primary caller defined within the same class. The method `editRetEKK1391C040` orchestrates the full cancel-service-write return flow: it builds data maps, copies fields from the CBS template to the data/work data maps (including service contract number, update datetime, operation counts, invalid flags), then delegates to `editErrInfoEKK1391C040` to handle error status propagation, and finally aggregates errors via `TemplateErrorUtil.getErrorInfo()`.

- **KKManAplyWribSvcKeiCC** — A variant caller in the service contract management application layer, which has its own overloaded signature of `editErrInfoEKK1391C040` accepting 5 parameters (including a `delHanyoSvcMap`), distinct from the method documented here which takes 4 parameters. This represents a different overload, not a call to the same method.

## 6. Per-Branch Detail Blocks

**Block 1** — [IF] `returnCode != 0` (L1311)

> If the return code is non-zero, override the template status to 9000, indicating a service component error.

| # | Type | Code |
|---|------|------|
| 1 | SET | `templateStatus = 9000` // Override status to indicate CBS error when return code is non-zero |

**Block 2** — [IF] `JCMAPLConstMgr.getString("RETURN_MESSAGE_" + formatStatus) == null` (L1313–L1315)

> Validates that the resolved template status has a corresponding message in the constant manager. If not, the status code is invalid or unrecognized, so reset to 0.

| # | Type | Code |
|---|------|------|
| 1 | SET | `formatStatus = String.format("%1$04d", templateStatus)` // Zero-padded 4-digit status |
| 2 | CALL | `JCMAPLConstMgr.getString("RETURN_MESSAGE_" + formatStatus)` // Lookup localized message |
| 3 | SET | `templateStatus = 0` // Reset invalid/unrecognized status to default |

**Block 3** — [IF/ELSE] `param.getControlMapData(SCControlMapKeys.RETURN_CODE)` null check (L1318–L1326)

> Reads the BP-side return code from the control map. If absent, treats the BP-side status as -1 (ensuring any valid template status will override it). Otherwise, parses the string value as an integer.

| # | Type | Code |
|---|------|------|
| 1 | SET | `obj = param.getControlMapData(SCControlMapKeys.RETURN_CODE)` // Retrieve BP return code |
| 2 | IF | `obj == null` (L1319) |
| 2.1 | SET | `bpStatus = -1` // No prior BP status — any CBS status takes precedence [L1321] |
| 2.2 | ELSE (L1323) | |
| 2.2.1 | SET | `bpStatus = Integer.parseInt((String) param.getControlMapData(SCControlMapKeys.RETURN_CODE))` // Parse BP status [L1325] |

**Block 4** — [IF] `templateStatus > bpStatus` (L1328–L1334)

> The core status priority decision: only push the CBS status into the control map if it represents a more severe condition than what the BP already has. This prevents lower-severity CBS status from overwriting a higher-severity BP-side error.

| # | Type | Code |
|---|------|------|
| 1 | SET | `formatStatus = String.format("%1$04d", templateStatus)` // Re-format as zero-padded 4-digit string |
| 2 | SET | `message = JCMAPLConstMgr.getString("RETURN_MESSAGE_" + formatStatus)` // Retrieve localized error message |
| 3 | EXEC | `param.setControlMapData(SCControlMapKeys.RETURN_CODE, formatStatus)` // Write the escalated status code |
| 4 | EXEC | `param.setControlMapData(SCControlMapKeys.RETURN_MESSAGE, message)` // Write the associated error message |

**Block 5** — [IF/ELSE] `workMap == null` initialization (L1338–L1344)

> Ensures the mapping work area exists. If the work area was never initialized, create a new HashMap and attach it to the parameter. This prepares the data container for subsequent error field propagation.

| # | Type | Code |
|---|------|------|
| 1 | SET | `workMap = (Map) param.getMappingWorkArea()` // Get existing work area [L1340] |
| 2 | IF | `workMap == null` (L1341) |
| 2.1 | SET | `workMap = new HashMap()` // Create new container [L1342] |
| 2.2 | EXEC | `param.setMappingWorkArea(workMap)` // Attach initialized map [L1343] |

**Block 6** — [SET] Data container retrieval (L1347)

> Retrieves the operation-level data map using the `fixedText` key as a namespace identifier. This map is the target destination for all error field values.

| # | Type | Code |
|---|------|------|
| 1 | SET | `inMap = (HashMap) param.getData(fixedText)` // Get operation data container keyed by fixedText |

**Block 7** — [IF/ELSE] `dchskmst_no_err` — Data extraction item setup number error (L1349–L1353)

> Copies the data extraction item setup number error field from the CBS template if present and not already set in the data map.

| # | Type | Code |
|---|------|------|
| 1 | IF | `!template.isNull(EKK1391C040CBSMsg.DCHSKMST_NO_ERR)` — Template has error value [L1349] |
| 1.1 | IF | `!inMap.containsKey("dchskmst_no_err")` — No prior value in data map [L1350] |
| 1.1.1 | SET | `inMap.put("dchskmst_no_err", template.getString(EKK1391C040CBSMsg.DCHSKMST_NO_ERR))` // Copy error field [L1352] |

**Block 8** — [IF/ELSE] `dchskmst_fin_sbt_cd_err` — Data extraction item setup completion type code error (L1356–L1360)

> Copies the completion type code error. This code classifies the type of completion that was reached (e.g., normal completion, partial completion, error termination).

| # | Type | Code |
|---|------|------|
| 1 | IF | `!template.isNull(EKK1391C040CBSMsg.DCHSKMST_FIN_SBT_CD_ERR)` — Template has error value [L1356] |
| 1.1 | IF | `!inMap.containsKey("dchskmst_fin_sbt_cd_err")` — No prior value in data map [L1357] |
| 1.1.1 | SET | `inMap.put("dchskmst_fin_sbt_cd_err", template.getString(EKK1391C040CBSMsg.DCHSKMST_FIN_SBT_CD_ERR))` // Copy error field [L1359] |

**Block 9** — [IF/ELSE] `dchskmst_end_ymd_err` — Data extraction item setup end date error (L1363–L1367)

> Copies the end date error. The end date indicates the cutoff date for data extraction item settings completion.

| # | Type | Code |
|---|------|------|
| 1 | IF | `!template.isNull(EKK1391C040CBSMsg.DCHSKMST_END_YMD_ERR)` — Template has error value [L1363] |
| 1.1 | IF | `!inMap.containsKey("dchskmst_end_ymd_err")` — No prior value in data map [L1364] |
| 1.1.1 | SET | `inMap.put("dchskmst_end_ymd_err", template.getString(EKK1391C040CBSMsg.DCHSKMST_END_YMD_ERR))` // Copy error field [L1366] |

**Block 10** — [IF/ELSE] `ido_div_err` — Movement classification error (L1370–L1374)

> Copies the movement classification error. This field distinguishes between different types of service movements (e.g., port-in, port-out, transfer).

| # | Type | Code |
|---|------|------|
| 1 | IF | `!template.isNull(EKK1391C040CBSMsg.IDO_DIV_ERR)` — Template has error value [L1370] |
| 1.1 | IF | `!inMap.containsKey("ido_div_err")` — No prior value in data map [L1371] |
| 1.1.1 | SET | `inMap.put("ido_div_err", template.getString(EKK1391C040CBSMsg.IDO_DIV_ERR))` // Copy error field [L1373] |

**Block 11** — [IF/ELSE] `dchskmst_fin_opty_cd_err` — Data extraction item setup completion opportunity code error (L1377–L1381)

> Copies the completion opportunity code error. This code indicates the circumstances or trigger under which the completion occurred.

| # | Type | Code |
|---|------|------|
| 1 | IF | `!template.isNull(EKK1391C040CBSMsg.DCHSKMST_FIN_OPTY_CD_ERR)` — Template has error value [L1377] |
| 1.1 | IF | `!inMap.containsKey("dchskmst_fin_opty_cd_err")` — No prior value in data map [L1378] |
| 1.1.1 | SET | `inMap.put("dchskmst_fin_opty_cd_err", template.getString(EKK1391C040CBSMsg.DCHSKMST_FIN_OPTY_CD_ERR))` // Copy error field [L1380] |

**Block 12** — [IF/ELSE] `upd_dtm_bf_err` — Pre-update timestamp error (L1384–L1388)

> Copies the pre-update timestamp error. This timestamp records the state of the update datetime before the current operation modified it.

| # | Type | Code |
|---|------|------|
| 1 | IF | `!template.isNull(EKK1391C040CBSMsg.UPD_DTM_BF_ERR)` — Template has error value [L1384] |
| 1.1 | IF | `!inMap.containsKey("upd_dtm_bf_err")` — No prior value in data map [L1385] |
| 1.1.1 | SET | `inMap.put("upd_dtm_bf_err", template.getString(EKK1391C040CBSMsg.UPD_DTM_BF_ERR))` // Copy error field [L1387] |

**Block 13** — [RETURN] (L1391)

> Returns the modified parameter object with all resolved status codes and propagated error fields.

| # | Type | Code |
|---|------|------|
| 1 | RETURN | `return param` // Return modified parameter with updated control map and error fields |

## 7. Glossary

| Term | Type | Business Meaning |
|------|------|------------------|
| `DCHSKMST_NO_ERR` | Field | Data extraction item setup number error — the error value for the internal tracking number of data extraction settings |
| `DCHSKMST_FIN_SBT_CD_ERR` | Field | Data extraction item setup completion type code error — classifies the type of completion (normal, partial, error) |
| `DCHSKMST_END_YMD_ERR` | Field | Data extraction item setup end date error — the cutoff date for settings completion, in YYYYMMDD format |
| `IDO_DIV_ERR` | Field | Movement classification error — distinguishes service movement types (port-in, port-out, transfer) |
| `DCHSKMST_FIN_OPTY_CD_ERR` | Field | Data extraction item setup completion opportunity code error — the trigger/circumstances for completion |
| `UPD_DTM_BF_ERR` | Field | Pre-update datetime error — the timestamp before the current update operation |
| `STATUS` | Field | CBS response status code — indicates the result of the CBS data extraction item settings process |
| `RETURN_CODE` | Field | Control map key for the BP-side return code — the current error level tracked in the control map |
| `RETURN_MESSAGE` | Field | Control map key for the localized error message — human-readable description mapped to a return code |
| `ERROR_INFO` | Field | Control map key for the aggregated error list — combined error info from CBS and BP layers |
| `fixedText` | Field | Operation data map namespace key — used to isolate different data contexts within the same parameter object |
| `templateStatus` | Local | Resolved CBS template status — the effective status after override and validation logic |
| `bpStatus` | Local | BP-side return code status — the current error level already set by the business process |
| CAANMsg | Technical | Fujitsu's message schema class — strongly-typed container for CBS request/response data fields |
| CBS | Acronym | Central Billing System — the backend billing/ordering system |
| BP | Acronym | Business Process — the application-layer business logic processing tier |
| CC | Acronym | Common Component — shared utility class in the service component architecture |
| JCMAPLConstMgr | Technical | Global configuration manager for localized message strings — provides `RETURN_MESSAGE_XXXX` keyed messages |
| IRequestParameterReadWrite | Technical | Interface for bidirectional request parameter access — carries control map, work area, and field data |
| EKK1391C040 | SC Code | Data extraction item settings completion — the CBS service component for completing data extraction settings in the cancel service flow |
| SC | Acronym | Service Component — a discrete business logic unit in the service-oriented architecture |
| 9000 | Constant | Error status code — indicates a CBS-level processing error |
| 0 | Constant | Success/default status code — indicates no error or an unrecognized status that was reset to default |
| 設定完了 | Business term (Japanese) | Settings completion — the finalization of data extraction item configuration in the cancel service workflow |
| エラー情報マッピング処理 | Business term (Japanese) | Error information mapping processing — translating CBS error fields into the parameter's work area |
| 作業者項目 | Business term (Japanese) | Operator fields — data items at the operator/work level scope |
| 異動区分 | Business term (Japanese) | Movement classification — categorization of service movements (port-in/out, transfers) |
| 契機コード | Business term (Japanese) | Opportunity/trigger code — the circumstances that caused the completion action |
| 更新年月日時秒(更新前) | Business term (Japanese) | Update datetime before update — snapshot of the timestamp prior to the current modification |