Crop Plan Module
Also known as SCP (Single Crop Plan).
Module Purpose
The Crop Plan module manages the annual declaration of land use by beneficiaries. It captures crop types, agricultural parcels and declared areas that underpin area-based payments and cross-compliance.
- Crop Plan Module
- Module Purpose
- Accessing the module
- SCP publish process
- Synchronisation
- Key Tables / Procedures / Functions
- Key Columns
- Data Flow
- Integration Points
- Configuration Details
- History tracking
- Quick reference
Accessing the module
Open the back-office web GUI. In the Menu Index search for Single Crop Plan. This module allows:
- Viewing farms from bird's-eye view
- Editing registries and land usage
- Specifying crops for the current year (daily accuracy)
- Managing farmer cultivation declarations
Farmers use a smartphone interface to declare cultivation and apply for funding.
SCP publish process
SCP Publish exports data from the SCP software to IACS, specifically declarations of what farmers have declared they are cultivating.
Publication steps
- Query SCP for the latest plan version for the farmer
- Verify the plan version is not already official for the current campaign
- Download list of areas (cadastral sections) where the farmer's SCP is present
- Publish the SCP to IACS
Failures at any point cause the entire process to rollback. Errors are logged in CROPPLAN_TO_IACS_LINK_FAILURES.
Synchronisation
The Crop Plan module synchronises with LPIS (Land Cover Layer in schema SITI) to maintain consistency between land cover and land use data.
Sync types
| Type | Description |
|---|---|
| LPIS | Full LPIS sync (via SitiClient10 C++ component) |
| Lite | Skips parcels marked in legacy skip table |
| Copy Campaign | Copies declarations between plans/years (manual use only) |
Sync triggers
- When changing LPIS or SitiClient values (if not marked TO SKIP)
- Automatically when opening a plan (checks for modifications since last sync)
- Manually via Batch Manager or sitiqueues
- For skipped cases: client calls Batch Job "Apply sync manually"
Batch manager access
Main Menu > Administration & Configuration > Service Management > Batch Manager:
- APPLY LPIS CHANGES TO SCP
- APPLY LPIS CHANGES TO SCP - FIC LEVEL
Key Tables / Procedures / Functions
This section lists the primary database tables, key PL/SQL packages and views used by the Crop Plan module. The listings below are drawn from the repository documentation and database exports under Makan Files.
Core crop plan tables
| Table | Description | Rows |
|---|---|---|
TPIANO_COLTURE |
Main crop plan declarations | 9,687,903 |
TPIANO_COLTURE_STATO |
Crop plan status | 1,174,698 |
TPIANO_COLTURA_STORIA |
Crop plan history | 1,111,656 |
TPIANO_COLTURA_DT_STORIA |
Crop plan date history | 1,080,167 |
TPIANO_COLTURE_IMPRONTA |
Crop plan fingerprint | 114,050 |
TPIANO_COLTURE_ORIGINALE |
Original crop plan | 115,247 |
GIS / Utilisation tables
| Table | Description | Rows |
|---|---|---|
UTILIZZO_GIS |
GIS land utilisation | 8,787,629 |
UTILIZZO_GIS_GRAFICO |
GIS graphic utilisation | 5,813,912 |
UTILIZZO_GIS_GRAFICO_STORY |
GIS graphic history | 6,177,200 |
UTILIZZO_GIS_GRAFICO_STORIA |
GIS graphic history (alt) | 3,023,571 |
UTILIZZO_GIS_DEF_COMPONENTE |
GIS component definitions | 23 |
TUTILIZZO_COMPONENTE |
Utilisation components | 6,549,614 |
Diversification tables
| Table | Description | Rows |
|---|---|---|
TDIVERSIFICAZIONE |
Crop diversification records | 222 |
TDIVERSIF_STORIA |
Diversification history | 55,648 |
TDIV_COMP_STORIA |
Diversification component history | 165,792 |
TDIV_GIS_STORIA |
Diversification GIS history | 48,102 |
Cadastral reference tables
| Table | Description | Rows |
|---|---|---|
TPARTICELLA_CATASTO |
Cadastral parcels | 5,185,100 |
TPARTICELLA_ELEGGIBILE |
Eligible parcels | 2,949,568 |
TPARTICELLA_LAVORATA |
Worked parcels | 4,339,851 |
TPARTICELLA_HISTORY |
Parcel history | 173,668 |
TCATASTO_SUPERFICIE |
Cadastral surface areas | 2,949,568 |
TCATASTO_LOCAL |
Local cadastral data | 3,614,131 |
TCATASTO_ORIGINE |
Cadastral origin data | 5,082,680 |
TCATASTO_INFO |
Cadastral information | 5,032,119 |
Crop definition tables
| Table | Description | Rows |
|---|---|---|
TCOLTURA |
Crop type definitions | 2,046 |
TDEF_COLTURA |
Crop definitions | 2,067 |
TDEF_COLTURA_SIAN |
SIAN crop definitions | 2,012 |
TDEF_COD_PRODOTTO |
Product code definitions | 2,243 |
TDEF_DESTINAZIONE |
Destination definitions | 7,823 |
Key PL/SQL packages and procedures
| Package / Procedure | Purpose |
|---|---|
PIANOCOLTURE_ROUTINE_PCK |
Crop plan processing |
MAP_PCK |
Mapping / GIS operations |
GRAFICO_PCK |
Graphic parcel handling |
DIVERSIFICATION_PCK |
Diversification calculations |
CADASTRAL_PCK |
Cadastral operations |
IMPORT_ALBERO_PCK |
Tree import processing |
Key views
| View | Purpose |
|---|---|
VTCATASTO |
Cadastral data view |
VTCATASTO_GRAFICO |
Graphic cadastral view |
VPIANO_COLTURE |
Crop plan view |
VUTILIZZO_GRAFICO |
GIS utilisation view |
VPARTICELLA_ELEGGIBILE |
Eligible parcel view |
Key Columns
TPIANO_COLTURE (Crop Plan)
| Column | Type | Nullable | Description |
|---|---|---|---|
PKID |
NUMBER | N | Primary key |
ID_PIANO_COLTURE |
NUMBER | N | Crop plan ID |
ID_ENTITA |
NUMBER | N | Entity ID |
ID_DOMANDA |
NUMBER | N | Application ID |
ID_FASCICOLO |
NUMBER | N | Dossier ID |
ANNO |
NUMBER | Y | Year |
COD_NAZIONALE |
VARCHAR2(6) | Y | National code (province) |
FOGLIO |
VARCHAR2(10) | Y | Map sheet |
PARTICELLA |
VARCHAR2(10) | Y | Parcel number |
SUB |
VARCHAR2(10) | Y | Sub-parcel |
ID_COLTURA_1 / _2 / _3 |
NUMBER | Y | Crop type IDs |
COD_USO_SUOLO |
NUMBER | Y | Land use code |
SUP_DICHIARATA |
NUMBER | Y | Declared area |
SUP_CATASTALE |
NUMBER | Y | Cadastral area |
SUP_CONDOTTA |
NUMBER | Y | Managed area |
SUP_GRAFICA |
NUMBER | Y | Graphic area |
SUP_ELEGGIBILE |
NUMBER | Y | Eligible area |
SUP_RIFERIMENTO |
NUMBER | Y | Reference area |
ID_CONSOCIAZIONE |
NUMBER | Y | Crop association ID |
Data Flow
See diagram: 
Integration Points
Inbound
- Land Parcel Identification System (LPIS): National cadastral and GIS data
- Dossier: Land registered in beneficiary dossier (TFASCICOLO)
- Previous Years: Historical crop declarations
Outbound
- Applications: Crop plan data feeds area-based applications
- Controls: Comparison of declared vs. measured areas
- Greening: EFA and diversification compliance checks
- Payments: Eligible area calculations
Configuration Details
- Batch jobs and scheduled synchronisation tasks are managed via the application Batch Manager in the backoffice (
Main Menu > Administration & Configuration > Service Management > Batch Manager). - Sync types and triggers are defined by the LPIS / SitiClient settings and the Batch Manager jobs (see the "Sync types" and "Sync triggers" sections).
- Error logging for publish/synchronisation failures uses the
CROPPLAN_TO_IACS_LINK_FAILURESartefact.
History tracking
Crop plan changes are tracked via:
TPIANO_COLTURA_STORIA: Full record historyTPIANO_COLTURA_DT_STORIA: Date-based historyTPIANO_COLTURE_STATO: Status transitionsUTILIZZO_GIS_GRAFICO_STORY: GIS graphic history