=== Prompt 6 ===
Which classes call into JKKHakkoSODCC (upstream callers)? And which services does JKKHakkoSODCC call (downstream)?

=== Tool Calls ===
search_files, list_directory, read_file, read_file, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, search_files, read_file, read_file, read_file, search_files, search_files, search_files, search_files, read_file, search_files, search_files, search_files, search_files, search_files, search_files, search_files

=== Response ===
Short answer up front

- Upstream callers (who calls JKKHakkoSODCC.hakkoSOD / its public entrypoints): I could not find any direct Java callers in this repository — there are no explicit references like MyComponent.hakkoSOD(...) or "new JKKHakkoSODCC()" or imports of that class in other .java files. That suggests JKKHakkoSODCC is invoked by the application/container (reflection/EJB/component registry) rather than by direct static calls from other classes in this repo.

- Downstream services (what JKKHakkoSODCC itself calls): the class calls many SC/CBS service components and maps to many CBS message/result editors. I extracted the list of its downstream call methods (callEKK*, callEKU*, callEZM*, callETU*, etc.) from the repository’s code index (.codewiki). The class talks to many EKK/EKU/EZM/ETU/EDK message/service adapters (examples below).

Evidence / how I searched
- Primary source location (class): Source/koptBp/ejbModule/com/fujitsu/futurity/bp/custom/common/JKKHakkoSODCC.java (class and method list is indexed in the repo wiki)
- I searched the Java sources for uses of the class and for direct calls to its hakkoSOD entrypoint; no matches were found in the codebase for callers (searches for "JKKHakkoSODCC", ".hakkoSOD(", "hakkoSOD(" returned only the JKKHakkoSODCC definition/index pages in the codewiki).
- The repository code index/manifest contains the full list of methods inside JKKHakkoSODCC — that index is where I took the downstream-call method names.

Upstream callers — details and next steps
- What I found:
  - No other .java files in this repo call methods on JKKHakkoSODCC directly (no static references found).
  - The class appears to be a central business component / EJB-style component (see its location under ejbModule and it extends AbstractCommonComponent per the code wiki).
- Why that makes sense:
  - Enterprise apps often invoke such components through the container (dependency injection / lookup by name / a central component registry) or from XML/process definitions that are not necessarily visible as a static Java call site.
- How you can confirm runtime callers:
  - Search runtime logs for the method/class name (e.g., "JKKHakkoSODCC" or "hakkoSOD") to see which request flows cause it to run.
  - Inspect DI / component registration code, configuration files, or XML (if present) that map requests to CC (common component) classes.
  - If you can run the app, produce a call graph (profiling or APM) or enable debug logging in the entry points that call it.

Downstream services — concrete list (extracted from the class’s method index)
The class contains many helpers named callEKK*, callEKU*, callEZM*, callETU* and a large number of editResultRP_* / editErrorInfo_* methods that adapt external CBS messages back into the application. The names here correspond to service adapters / CBS message types it invokes or processes. Representative downstream calls include (method names as indexed in the code wiki / manifest):

- EKK* calls (many)
  - callEKK1081C011SC
  - callEKK0081A010SC
  - callEKK0341A010SC
  - callEKK0401A010SC
  - callEKK0411A010SC
  - callEKK0161A010SC
  - callEKK0191A010SC
  - callEKK0161B003SC
  - callEKK0161B004SC
  - callEKK0351A010SC
  - callEKK0361A010SC
  - callEKK0351B010SC
  - callEKK0351B002SC
  - callEKK0341B002SC
  - callEKK0251B003SCCAAMsg
  - callEKK0341B504SC
  - callEKK2811B010SC
  - callEKK2811A010SC
  - callEKK1041A010SC
  - callEKK0341B008SC
  - callEKK0341B008_02SC
  - callEKK0191B001SC
  - callEKK1681B001SC
  - callEKK0251B001SC
  - callEKK0161B008SC
  - callEKK0191B502SC
  - callEKK0161B011SC
  - callEKK0251B003SC
  - callEKK2101B002SC
  - callEKK2091A010SC
  - callEKK2101B001SC
  - callEKK0341B029SC
  - callEKK0341B008SCRireki
  - callEKK0341B001SC
  - callEKK0341B021SC
  - callEKK0191B001_2SC
  - callEKK0091A010_SC
  - callEKK0891A010_SC
  - callEKK0881A010_SC
  - callEKK1041B001SC
  - callEKK0351B002SC
  - callEKK0161B011SC
  - ... (the class contains many such callEKK* methods — the manifest/index shows dozens more)

- EKU* calls
  - callEKU0011A010SC
  - callEKU0081B010SC

- EZM* calls
  - callEZM0411A010SC
  - callEZM0321A010_SC
  - callEZM0121A010SC
  - ... (mapped methods exist for EZM messages)

- ETU* calls
  - callETU0011B010SC

- Other downstream things in this class:
  - Many editResultRP_* and editErrorInfo_* methods mapped to specific CBS message types, e.g.:
    - editResultRP_EKK1081D010CBS
    - editErrorInfo_EKK1081D010CBS
    - editResultRP_EKK1551D010CBS and associated editErrorInfo...
    - editResultRP_EKK0791A010SC
    - editResultRP_EKK1081B001SC
    - editResultRP_EKK0081B004SC
    - ... (lots of message/result-specific editors exist inside this class)
  - Message classes (CBS message types) are present under Source/koptModel/src/eo/ejb/cbs/cbsmsg/*.java (examples: EKK0341A010CBSMsg.java etc). JKKHakkoSODCC maps to those message types when calling downstream SC adapters or processing their results.

References I used
- The class location and method inventory (indexed in the repo wiki): Source/koptBp/ejbModule/com/fujitsu/futurity/bp/custom/common/JKKHakkoSODCC.java (referenced by the codewiki pages)
- Extracted method names and downstream-call methods from .codewiki/manifest.json (entries listing callEKK*/callEKU*/callEZM* methods for JKKHakkoSODCC)
  - See .codewiki/pages/entity:com.fujitsu.futurity.bp.custom.common:JKKHakkoSODCC.json and .codewiki/manifest.json for the full method list and the many callEKK* method entries.

If you want a fully enumerated, copy-pasteable downstream list
- I can extract and print the complete list of all callEKK*/callEKU*/callEZM*/editResultRP*/editErrorInfo* method names captured in the wiki/manifest (it’s several dozen to a couple hundred method names inside that single class). Tell me whether you want:
  - a compact list of the unique service prefixes used (EKK, EKU, EZM, ETU, EDK, …), or
  - a complete line-by-line enumerated list of all call* and edit* methods.

If you want to discover real upstream callers at runtime
- Search runtime logs for the class/method names; or
- Enable tracing / profiling on the running app to see which controllers / handlers invoke it; or
- If you have the application deployment descriptors or component registration files, share them and I’ll inspect for mappings that point requests to JKKHakkoSODCC.

Would you like the complete downstream-method list exported here?