# Fmprod Fmdel Crosswalk

> Map FMPROD and FMDEL green-screen fields to Db2 for i SQL UDTFs, Kotlin API endpoints, Angular UI fields, and documentation. Use when comparing legacy screens with REST calls, TF_FMPROD* objects, product inquiry/status behavior, field mappings, maintenance screens, or docs/fmprod analysis under /home/hcantor/Projects.

- Skill: `hugocantor/fmprod-fmdel-crosswalk` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add hugocantor/fmprod-fmdel-crosswalk`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hugocantor/fmprod-fmdel-crosswalk/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: hugocantor (https://skillmd.com/u/hugocantor)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/hugocantor/fmprod-fmdel-crosswalk

---


# FMPROD/FMDEL Crosswalk

## Purpose

Use this skill when the user asks how legacy FMPROD/FMDEL screen fields, business behavior, SQL objects, API routes, and Angular UI fields correspond.

## Workflow

1. Identify the screen, panel, field label, option, or workflow being mapped.
2. Gather evidence from the canonical locations in [reference.md](reference.md).
3. Build the chain in this order when possible:
   - Legacy screen or RPG source.
   - SourceAnalysis file/table/program evidence.
   - `sqlobjects` UDTF, view, or procedure.
   - Kotlin `apis/apiv1` endpoint and DTO.
   - Angular API/model/mapper/facade/component field.
   - Docs or analysis markdown that explains business meaning.
4. Distinguish display labels from physical fields, SQL aliases, DTO names, and Angular property names.
5. If any link is missing, report it as unknown instead of filling it in from naming similarity alone.

## Output Format

For crosswalk answers, prefer this compact table shape:

```text
Legacy field | Meaning | Source evidence | SQL object | API endpoint/DTO | Angular field | Notes
```

For implementation planning, return:

- Existing behavior and source evidence.
- New or changed SQL/API/frontend contract.
- Files likely affected.
- Tests or parity checks to run.
- Open questions where the legacy mapping is ambiguous.

## Guardrails

- Treat `docs/fmprod_analysis_*` and related markdown as narrative evidence, not a substitute for source when changing behavior.
- Do not assume FMPROD and FMDEL names are interchangeable; verify the workflow and source path.
- Preserve legacy-compatible field meanings unless the user explicitly asks to redesign the contract.