本文へ移動
cccskills
無料GitHub で公開

database

Expert knowledge of the melosys-api Oracle database schema. Use when: (1) Writing SQL queries against the melosys database, (2) Understanding table relationships and foreign keys, (3) Debugging data issues by querying the database, (4) Understanding what data is stored where, (5) Creating or modifying Flyway migrations, (6) Mapping domain entities to database tables. Triggers: SQL against melosys DB, table/column lookup, FK relationships, "where is X stored", "what column stores X", "why is data missing", beh_resultat_id, behandlingsresultat_id, saksnummer, schema.

日本語の概要は準備中です。原文の説明を表示しています。

インストール方法を見る

含まれるファイル(5)

  • SKILL.md9.7 KB
  • references/core-tables.md10.1 KB
  • references/dvh-tables.md3.6 KB
  • references/kodeverk.md10.0 KB
  • references/period-tables.md8.1 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Melosys Database Schema

Oracle database schema for melosys-api. Connection: jdbc:oracle:thin:@//localhost:1521/FREEPDB1 (user: melosys).

Entity-Relationship Overview

FAGSAK (Case)
├── AKTOER (1:N) - Actors (citizen, employer, authorities)
├── KONTAKTOPPLYSNING (1:N) - Contact information
├── FULLMAKT (via AKTOER) - Power of attorney
├── SKJEMA_SAK_MAPPING (1:N) - Bridge to melosys-skjema-api (V152)
└── BEHANDLING (1:N) - Treatments/processing instances
    ├── MOTTATTEOPPLYSNINGER (1:N) - Received documents/info
    ├── SAKSOPPLYSNING (1:N) - Case data (JSON CLOBs)
    ├── BEHANDLINGSNOTAT (1:N) - Notes
    ├── BEHANDLINGSAARSAK (1:N) - Processing reasons
    ├── TIDLIGERE_MEDLEMSPERIODE (1:N) - Previous membership periods
    ├── PROSESSINSTANS (1:N) - Saga/workflow instances
    └── BEHANDLINGSRESULTAT (1:1) - Result
        ├── LOVVALG_PERIODE (1:N) - Applicable legislation periods
        ├── MEDLEMSKAPSPERIODE (1:N) - Membership periods
        ├── ANMODNINGSPERIODE (1:N) - Exception request periods
        ├── UTPEKINGSPERIODE (1:N) - Designation periods (Art. 13)
        ├── TRYGDEAVGIFTSPERIODE (1:N) - Social security charge periods
        ├── AARSAVREGNING (1:1) - Annual reconciliation (årsavregning)
        ├── VEDTAK_METADATA (1:1) - Decision metadata
        ├── VILKAARSRESULTAT (1:N) - Condition results
        ├── AVKLARTEFAKTA (1:N) - Clarified facts
        └── KONTROLLRESULTAT (1:N) - Control results

Recent changes (V144–V154, Jan–Apr 2026): New skjema_sak_mapping table (bridge to melosys-skjema-api). kilde column added to lovvalg_periode, medlemskapsperiode, helseutgift_dekkes_periode. aarsavregning columns renamed: *_fra_avgiftssystemet → *innbetalt_trygdeavgift. New PROSESS_TYPE for digital søknad-mottak. See Recent Migrations below.

Core Tables

FAGSAK (Case)

Primary case entity. PK: SAKSNUMMER (format: MEL-{sequence}).

ColumnTypeDescription
SAKSNUMMERVARCHAR2(99)Primary key, e.g., "MEL-12345"
GSAK_SAKSNUMMERNUMBERArchive case ID (Joark/GSAK)
FAGSAK_TYPEVARCHAR2(99)FK to FAGSAK_TYPE (EU_EOS, TRYGDEAVTALE, FTRL)
TEMAVARCHAR2(20)FK to FAGSAK_TEMA (MEDLEMSKAP_LOVVALG, UNNTAK, TRYGDEAVGIFT)
STATUSVARCHAR2(99)FK to FAGSAK_STATUS
BETALINGSVALGVARCHAR2(99)Payment choice

BEHANDLING (Treatment)

Processing instance within a case. PK: ID.

ColumnTypeDescription
IDNUMBERPrimary key (sequence)
SAKSNUMMERVARCHAR2(99)FK to FAGSAK
STATUSVARCHAR2(99)FK to BEHANDLING_STATUS
BEH_TYPEVARCHAR2(99)FK to BEHANDLING_TYPE
BEH_TEMAVARCHAR2(99)FK to BEHANDLING_TEMA
BEHANDLINGSFRISTDATEProcessing deadline
OPPGAVE_IDVARCHAR2(10)External task ID
INITIERENDE_JOURNALPOST_IDVARCHAR2(99)Initiating document ID
OPPRINNELIG_BEHANDLING_IDNUMBERFK to parent BEHANDLING (self-ref)

AKTOER (Actor)

Parties involved in a case. PK: ID.

ColumnTypeDescription
IDNUMBERPrimary key
SAKSNUMMERVARCHAR2(99)FK to FAGSAK
ROLLEVARCHAR2(99)FK to ROLLE_TYPE (BRUKER, ARBEIDSGIVER, etc.)
AKTOER_IDVARCHAR2(99)NAV actor ID (for BRUKER)
PERSON_IDENTVARCHAR2(11)Norwegian ID number
ORGNRVARCHAR2(99)Organization number
EU_EOS_INSTITUSJON_IDVARCHAR2(99)EU/EEA institution ID
TRYGDEMYNDIGHET_LANDVARCHAR2(2)Country code for authority

BEHANDLINGSRESULTAT (Result)

Outcome of a treatment. PK: BEHANDLING_ID (1:1 with BEHANDLING).

ColumnTypeDescription
BEHANDLING_IDNUMBERPK + FK to BEHANDLING
RESULTAT_TYPEVARCHAR2(99)FK to BEHANDLINGSRESULTAT_TYPE
BEHANDLINGSMAATEVARCHAR2(99)Processing method
FASTSATT_AV_LANDVARCHAR2(99)Country that determined result
BEGRUNNELSE_FRITEKSTVARCHAR2(4000)Justification text
FAKTURASERIE_REFERANSEVARCHAR2(40)Billing series reference
TRYGDEAVGIFT_TYPEVARCHAR2(99)Social security charge type

Period Tables

All periods belong to BEHANDLINGSRESULTAT via BEH_RESULTAT_ID — except MEDLEMSKAPSPERIODE, whose FK column is BEHANDLINGSRESULTAT_ID (renamed in V109). Both FK columns reference BEHANDLINGSRESULTAT(BEHANDLING_ID).

LOVVALG_PERIODE (Applicable Legislation Period)

ColumnTypeDescription
FOM_DATO / TOM_DATODATEPeriod start/end
LOVVALGSLANDVARCHAR2(99)Country code
LOVVALG_BESTEMMELSEVARCHAR2(99)Legal provision
INNVILGELSE_RESULTATVARCHAR2(99)Grant/denial result
MEDLEMSKAPSTYPEVARCHAR2(99)Membership type
TRYGDE_DEKNINGVARCHAR2(99)Coverage type

MEDLEMSKAPSPERIODE (Membership Period)

ColumnTypeDescription
FOM_DATO / TOM_DATODATEPeriod start/end
INNVILGELSE_RESULTATVARCHAR2(99)Grant/denial
MEDLEMSKAPSTYPEVARCHAR2(99)Membership type
TRYGDE_DEKNINGVARCHAR2(99)Coverage
BESTEMMELSEVARCHAR2(99)Legal basis
MEDLPERIODE_IDNUMBERMEDL external ID

Common Queries

Find case with all actors

SELECT f.*, a.rolle, a.aktoer_id, a.orgnr, a.person_ident
FROM fagsak f
JOIN aktoer a ON a.saksnummer = f.saksnummer
WHERE f.saksnummer = 'MEL-12345';

Find active treatments for person

SELECT b.*, f.saksnummer
FROM behandling b
JOIN fagsak f ON b.saksnummer = f.saksnummer
JOIN aktoer a ON a.saksnummer = f.saksnummer
WHERE a.rolle = 'BRUKER' AND a.person_ident = '12345678901'
AND b.status NOT IN ('AVSLUTTET');

Find membership periods for case

SELECT mp.*
FROM medlemskapsperiode mp
JOIN behandlingsresultat br ON mp.behandlingsresultat_id = br.behandling_id
JOIN behandling b ON br.behandling_id = b.id
WHERE b.saksnummer = 'MEL-12345';

Check prosessinstans status

SELECT p.*, b.saksnummer, b.status as beh_status
FROM prosessinstans p
JOIN behandling b ON p.behandling_id = b.id
WHERE b.id = :behandlingId
ORDER BY p.registrert_dato DESC;

Find stuck treatments

SELECT b.id, b.status, b.endret_dato, f.saksnummer
FROM behandling b
JOIN fagsak f ON b.saksnummer = f.saksnummer
WHERE b.status = 'IVERKSETTER_VEDTAK'
AND b.endret_dato < SYSDATE - INTERVAL '2' HOUR;

Recent Migrations

Latest migration is V155 (tekstblokker). Changes since V143:

VDateWhat
V1442026-01-07New PROSESS_STEG LAGRE_PERSONOPPLYSNINGER
V1452026-01-15New PROSESS_STEG OPPRETTE_AARSAVREGNING_ENDRING (auto-opprett årsavregning tilbake i tid)
V1462026-01-19saksopplysning_kilde adds versjon NUMBER(19) DEFAULT 0 — optimistic locking fix for orphanRemoval race condition
V1472026-02-16New PROSESS_TYPE MELOSYS_MOTTAK_DIGITAL_SØKNAD + 4 nye steg (HENT_SØKNADSDATA, OPPRETT_SAK_OG_BEHANDLING_SØKNAD, OPPRETT_OG_FERDIGSTILL_JOURNALPOST_SØKNAD, LAGRE_SAKSOPPLYSNINGER_SØKNAD)
V1482026-02-16kontaktopplysning.kontakt_telefon utvidet til VARCHAR2(255)
V1492026-02-27Fjerner steg LAGRE_SAKSOPPLYSNINGER_SØKNAD (lagring nå i OPPRETT_SAK_OG_BEHANDLING_SØKNAD)
V1502026-03-16New PROSESS_STEG AVSLUTT_AARSAVREGNINGER (lukker åpne årsavregninger ved annullering)
V1512026-04-16helseutgift_dekkes_periode adds kilde VARCHAR2(30) DEFAULT 'MELOSYS' NOT NULL
V1522026-04-20NEW TABLE skjema_sak_mapping (RAW(16) skjema_id ↔ saksnummer). New PROSESS_TYPE MELOSYS_MOTTAK_EKSISTERENDE_DIGITAL_SØKNAD. Steg fra V147 omdøpt til *_DIGITAL_SØKNAD-varianter (HENT_DIGITAL_SØKNADSDATA, OPPRETT_SAK_OG_BEHANDLING_DIGITAL_SØKNAD, OPPRETT_OG_FERDIGSTILL_JOURNALPOST_DIGITAL_SØKNAD) + nye HÅNDTER_EKSISTERENDE_SAK_DIGITAL_SØKNAD, SEND_SAKSNUMMER_TIL_MELOSYS_SKJEMA_API
V1532026-04-23aarsavregning columns renamed: har_trygdeavgift_fra_avgiftssystemet → har_innbetalt_trygdeavgift, trygdeavgift_fra_avgiftssystemet → innbetalt_trygdeavgift
V1542026-04-30medlemskapsperiode.kilde + lovvalg_periode.kilde added (VARCHAR2(30), nullable)
V155—NEW TABLE tekstblokker (TEKSTBLOKK + TEKSTBLOKK_TAG, reusable text blocks with tags)

Note on PROSESS_STEG renames (V152): Oracle doesn't support ON UPDATE CASCADE, so the pattern is INSERT new code → UPDATE child rows (PROSESSINSTANS.SIST_FULLFORT_STEG, PROSESSINSTANS_HENDELSER.STEG) → DELETE old code. Use this same pattern for any future PROSESS_STEG rename.

Detailed Documentation

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

コメント

ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。

まだコメントはありません。最初のコメントを書いてみませんか。

送信するとすぐに公開されます。メールアドレスや電話番号などの個人情報は書かないでください。URL は 2 つまでです。

0 / 1000 文字

このフォームは reCAPTCHA で保護されており、Google のプライバシーポリシーと利用規約が適用されます。

同じリポジトリのスキル

Expert knowledge of Altinn A1 application processing for posted workers in melosys-api. Use when: (1) Understanding Altinn søknad/skjema processing, (2) Debugging MedlemskapArbeidEOS form mapping, (3) Understanding SoeknadMapper transformations, (4) Investigating posted worker application issues, (5) Understanding the MOTTAK_SOKNAD_ALTINN saga flow.

日本語の概要は準備中です。原文の説明を表示しています。

navikt/melosys-api22026年10月21日 更新

Expert knowledge of Employer/Employment integration (EREG/AAREG) in melosys-api. Use when: (1) Working with organization data from EREG (Enhetsregisteret), (2) Working with employment data from AAREG (Arbeidsforhold), (3) Understanding employer/organization lookup, (4) Debugging employer or employment issues, (5) Understanding the mapping between register data and domain models. Triggers: orgnummer, arbeidsforhold, EREG, AAREG, Enhetsregisteret, registeropplysninger, ansettelsesperiode, saksopplysning.

日本語の概要は準備中です。原文の説明を表示しています。

navikt/melosys-api22026年10月21日 更新

Modular monolith architecture overview for melosys-api. Use when needing to understand module structure, dependencies between modules, where to place new code, or when changes in one module might affect others. Triggers: "architecture", "module dependencies", "where should I put", "which modules", "dependency graph".

日本語の概要は準備中です。原文の説明を表示しています。

navikt/melosys-api22026年10月21日 更新

Expert knowledge of Behandling (case treatment) domain in melosys-api. Use when: (1) Understanding the behandling lifecycle and status transitions, (2) Debugging issues with behandling creation, status changes, or closure, (3) Understanding relationships between Fagsak, Behandling, and Behandlingsresultat, (4) Investigating why a behandling is stuck or has wrong status, (5) Understanding Behandlingstyper, Behandlingstema, Behandlingsstatus enums, (6) Debugging journalføring or SED-triggered behandling creation, (7) Understanding behandling creation via saksflyt sagas.

日本語の概要は準備中です。原文の説明を表示しています。

navikt/melosys-api22026年10月21日 更新

Expert knowledge of Behandlingsresultat (treatment result) domain in melosys-api. Use when: (1) Understanding result types and their meaning (FASTSATT_LOVVALGSLAND, MEDLEM_I_FOLKETRYGDEN, etc.), (2) Working with periods - Lovvalgsperiode, Medlemskapsperiode, Anmodningsperiode, Utpekingsperiode, (3) Debugging vedtak/decision metadata, criteria evaluation, or social insurance charges, (4) Understanding EU/EEA coordination logic and Article 16 exception handling, (5) Working with trygdeavgift (social insurance charge) calculations.

日本語の概要は準備中です。原文の説明を表示しています。

navikt/melosys-api22026年10月21日 更新

brev

無料

Expert knowledge of Brev (letter generation) in melosys-api. Use when: (1) Producing letters and decision documents (vedtaksbrev), (2) Understanding Dokgen templates and mapping, (3) Configuring letter recipients and distribution, (4) Debugging letter generation issues, (5) Adding new letter types or templates.

日本語の概要は準備中です。原文の説明を表示しています。

navikt/melosys-api22026年10月21日 更新

navikt のスキルをすべて見る

このスキルの問題を報告する