---
title: "Business Logic — JKKCallWrisvcAutoAplyCC.getInvokeCBS() [13 LOC]"
---

# Business Logic — JKKCallWrisvcAutoAplyCC.getInvokeCBS() [13 LOC]

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

## 1. Role

### JKKCallWrisvcAutoAplyCC.getInvokeCBS()

This method is a **shared initialization utility** that returns a pre-wired `HashMap` used as a message-passing envelope in the CAAN (Common Application Access Network) framework. It creates an empty `List<CAANMsg>` (a collection of application messages/error templates), stores it under the framework constant `JCMConstants.TEMPLATE_LIST_KEY`, and returns the populated map. Its primary role is to serve as the **CBS (Component Business Service) entry point** for screen-specific check classes (`*OPBPCheck`). Each caller invokes `getInvokeCBS` to obtain a fresh, framework-compatible parameter map, optionally populates the template list with screen-specific CAANMsg objects, and then passes the map to the downstream CBS layer for message exchange. The method implements the **builder** and **delegation** patterns — it constructs a minimal request envelope and delegates actual message handling to the CAAN message infrastructure. Because it is called from numerous screen-check classes (KKSV0791, KKSV0568, KKSV0384, CRSV0025, CRSV0183, CNSV0045, CRSV0237, CHSV9001, etc.), it functions as a **shared utility entry point** across the entire application suite.

## 2. Processing Pattern (Detailed Business Logic)

```mermaid
flowchart TD
    START(["getInvokeCBS(handle, param, fixedText)"])
    A["Create paramMap: HashMap<String, Object>"]
    B["Create empty templates: List<CAANMsg>"]
    C["Put templates into paramMap[TEMPLATE_LIST_KEY]"]
    D["Return paramMap"]

    START --> A --> B --> C --> D
```

**CRITICAL — Constant Resolution:**
- `JCMConstants.TEMPLATE_LIST_KEY` — The CAAN framework key used to store and retrieve the list of message templates (`CAANMsg` objects) within the parameter map. This key acts as the standardized envelope for passing application messages between the screen layer and the CBS/service layer.

**Requirements:**
- This method has no conditional branches, loops, or method calls beyond basic object creation and `HashMap.put()`.
- Every step is represented as a node.
- Diamond nodes would appear for conditions; none exist in this method.
- All processing steps are shown sequentially.

## 3. Parameter Analysis

| No | Parameter Name | Type | Business Description |
|----|---------------|------|---------------------|
| 1 | `handle` | `SessionHandle` | Session manager handle — carries session context information such as user authentication, transaction state, and locale settings. Used by downstream CBS components to maintain session continuity. (Original: セッションマネージャなどを持ったハンドル) |
| 2 | `param` | `IRequestParameterReadWrite` | Request parameter object — a read-write parameter container holding the model group and control map for the calling screen. Provides access to screen-specific data and configuration metadata. (Original: モデルグループ、コントロールマップを含むパラメータオブジェクト) |
| 3 | `fixedText` | `String` | User-defined arbitrary string — a free-form text string passed by the caller, typically used as an identifier (e.g., `"KKSV079101CC"`, `"HapiePointKeiReSearchForRsvCC"`) that indicates which caller screen or component is invoking the method. May be logged or used for diagnostic tracing. (Original: ユーザ任意文字列) |

**Instance fields read:** None — this method reads no instance fields.

## 4. CRUD Operations / Called Services

This method performs **no database operations or service component calls**. It only constructs and returns a parameter map.

| CRUD | SC / CBS | SC Code | Entity / DB | Operation Description |
|------|----------|---------|-------------|----------------------|
| (None) | — | — | — | This method only creates an empty parameter envelope; all actual CRUD work is performed by downstream CBS components that consume the returned map. |

**How to classify:**
- No calls with names like `insert*`, `create*`, `add*`, `save*`, `find*`, `get*`, `select*`, `update*`, `delete*` exist in this method body.
- `HashMap.put()` is an in-memory data structure operation, not a CRUD persistence operation.

## 5. Dependency Trace

| # | Caller (Screen/Batch) | Call Chain (Full Path to this Method) | Terminal (SC / CRUD / Entity) |
|---|----------------------|--------------------------------------|-------------------------------|
| 1 | KKSV0791 | `KKSV0791_OPOperCheck` -> `getInvokeCBS` (jkkopchrirekilistdlydcc) | (none) |
| 2 | CRSV0183 | `CRSV0183_OPOperCheck` -> `getInvokeCBS` (jcrgetdenshifilectl1icc) | (none) |
| 3 | KKSV0339 | `KKSV0339_OPOperCheck` -> `getInvokeCBS` (jkknosvcinfocc) | (none) |
| 4 | SCSV0028 | `SCSV0028_OPOperCheck` -> `getInvokeCBS` (jscsv002801cc) | (none) |
| 5 | CRSV0025 | `CRSV0025_OPOperCheck` -> `getInvokeCBS` (jcrjudgengwordcc, jcraddtaiokrkdtlcallcc, jcraddhotvoiccc) | (none) |
| 6 | KKSV0630 | `KKSV0630_OPOperCheck` -> `getInvokeCBS` (jkkhapiepointkeiresearchforrsvcc) | (none) |
| 7 | KKSV0781 | `KKSV0781_OPOperCheck` -> `getInvokeCBS` (jkksamescreenheadercc, jkkintrinfochgcfmcc) | (none) |
| 8 | KKSV0568 | `KKSV0568_OPOperCheck` -> `getInvokeCBS` (jkkcancelsvcwribcc, jkkcanceluseplaceinfocc, jkkcancelsvckeimobilecc, jkkcancelsvckeitelcc, jkkcancelsvckeitetvcc, jkkcancelicjknsettecc, jkkaplyseiopsvckeicc, jkkaplytajgswribkeimskmcc, jkkcancelmskminfocc) | (none) |
| 9 | KKSV0384 | `KKSV0384_OPOperCheck` -> `getInvokeCBS` (jkkseikykeirrkilistcc) | (none) |
| 10 | DKSV0141 | `DKSV0141_OPOperCheck` -> `getInvokeCBS` | (none) |
| 11 | CRSV0237 | `CRSV0237_OPOperCheck` -> `getInvokeCBS` | (none) |
| 12 | CRSV0197 | `CRSV0197_OPOperCheck` -> `getInvokeCBS` | (none) |
| 13 | KKSV0495 | `KKSV0495_OPOperCheck` -> `getInvokeCBS` (multiple components) | (none) |
| 14 | ZMSV0105 | `ZMSV0105_OPOperCheck` -> `getInvokeCBS` | (none) |
| 15 | CRSV0124 | `CRSV0124_OPOperCheck` -> `getInvokeCBS` | (none) |

**Notes:**
- This method itself calls no downstream services, CBS components, or CRUD operations.
- The returned `paramMap` is consumed by the caller, which may then pass it to other CBS layers. The terminal entity/CRUD effects are determined by the caller's downstream processing, not by `getInvokeCBS` itself.
- All callers are `*OPBPCheck` classes — screen-level business process check components that validate preconditions before screen rendering.

## 6. Per-Branch Detail Blocks

**Block 1** — [SEQUENTIAL] `(no branching)` (L108)

> Creates the parameter map envelope for the CAAN framework message exchange.

| # | Type | Code |
|---|------|------|
| 1 | SET | `paramMap = new HashMap<String, Object>()` |
| 2 | SET | `templates = new ArrayList<CAANMsg>()` // Creates an empty message template list (Original: チェック用サービスインターフェース) |
| 3 | SET | `paramMap.put(JCMConstants.TEMPLATE_LIST_KEY, Arrays.asList(templates))` // Stores the empty template list under the framework constant key [-> `TEMPLATE_LIST_KEY`] |
| 4 | RETURN | `return paramMap` |

**Block 1.1** — [nested inside Block 1, SET statement 3] `(paramMap.put)`

| # | Type | Code |
|---|------|------|
| 1 | EXEC | `paramMap.put(JCMConstants.TEMPLATE_LIST_KEY, ...)` // Puts the template list into the map [-> `JCMConstants.TEMPLATE_LIST_KEY`] |

No other conditional branches, loops, try-catch blocks, or nested structures exist in this method.

## 7. Glossary

| Term | Type | Business Meaning |
|------|------|------------------|
| `handle` | Field | Session handle — context object carrying user session, authentication, and transaction information |
| `param` | Field | Request parameter — read-write container for model data and control map passed between screen and CBS layers |
| `fixedText` | Field | User-defined string — arbitrary text string used as a caller identifier or diagnostic label |
| CAANMsg | Business term | Common Application Access Network Message — a message object used in the CAAN framework for passing application messages, error codes, and notification data between layers |
| TEMPLATE_LIST_KEY | Constant | Framework constant key — the map key under which the `List<CAANMsg>` template list is stored in the parameter envelope |
| SessionHandle | Technical term | Session manager handle — carries session context (user ID, locale, transaction state) for the current request |
| IRequestParameterReadWrite | Technical term | Interface for request parameter read/write — allows the CBS layer to both read input data from the screen and write results back |
| OPBPCheck | Business term | Operation Business Process Check — screen-level validation component that verifies preconditions and builds the initial message envelope before screen rendering |
| CBS | Business term | Component Business Service — the service layer that executes business logic and persists data |
| CC | Business term | Common Component — a shared utility class in the `common` package used across multiple screens and services |
| JCMConstants | Technical term | Java Common Module Constants — framework constant definitions used across the CAAN application framework |

---

*Document generated from `JKKCallWrisvcAutoAplyCC.java`, lines 108–120. 13 lines of code.*