Skip to content

APCCOMP

APCCOMP is to set out Administered Price Cap (APC) compensation periods for a participant.

Deprecation Warning

This table is in the HISTORICAL TABLES package, so is likely deprecated.

APCCOMP is public data, and is available to all participants.

Source

APCCOMP is empty until an Administered Price Cap event occurs.

Not in use - never used

Column Schema

APCID

APC event identifier.

SQL Type: VARCHAR2(10) Polars Type: str

This column is mandatory, and a primary key.

ENDDATE

Settlement end date

Warning

Despite what the name suggests, this is a datetime, not a date.

SQL Type: DATE Polars Type: pl.Datetime()

This column is not mandatory.

Example: 2026/01/20 00:05:00

ENDPERIOD

Settlement end period (1-48)

SQL Type: NUMBER(3,0) Polars Type: pl.Int16

This column is not mandatory.

LASTCHANGED

Last date and time record changed

For more information, see the dedicated documentation page.

SQL Type: DATE Polars Type: pl.Datetime()

This column is not mandatory.

Example: 2026/01/20 00:05:00

REGIONID

Region

For more information, see the dedicated documentation page.

The SQL type is VARCHAR2(10). This is actually a factor/enum, with values:

  • QLD1

  • VIC1

  • TAS1

  • NSW1

  • SA1

  • SNOWY1

This column is not mandatory.

STARTDATE

Settlement start date

Warning

Despite what the name suggests, this is a datetime, not a date.

SQL Type: DATE Polars Type: pl.Datetime()

This column is not mandatory.

Example: 2026/01/20 00:05:00

STARTPERIOD

Settlement start period (1-48)

SQL Type: NUMBER(3,0) Polars Type: pl.Int16

This column is not mandatory.

New Data Timing

When a Administered Price Cap event occurs

Code Examples

Polars

Casting is enums, categoricals etc is not essential, but may speed up parsing. Swapping int for pl.UInt16, pl.Int32 would also speed up parsing. However some of the datatypes are inferred, so they may be wrong.

This code deduplicates for you. Deduplication is normally only required across multiple months.

This code assumes that all columns are present, which may not be true for older files.

import polars as pl
import polars.selectors as cs

# e.g. "2029/03/15 00:05:00"
dt_s_fmt = "%Y/%m/%d %H:%M:%S"

csv_paths = ["SOMEFILE.CSV", "OTHERFILE.CSV"]

lf = (
    pl.concat(
        [
            pl.scan_csv(
                csv_path,  # must be unzipped beforehand
                skip_rows=1,  # skip the header
                infer_schema=False,  # much faster
            )
            .filter(cs.by_index(0) == "D")  # drop the footer
            .select(~cs.by_index(range(4)))  # drop metadata columns
            for csv_path in csv_paths
        ],
        how="diagonal_relaxed",
    )
    .with_columns(
        pl.col("ENDDATE", "LASTCHANGED", "STARTDATE").str.strptime(
            pl.Datetime, dt_s_fmt
        ),
    )
    .cast(
        {
            "APCID": str,
            "ENDPERIOD": int,  # or pl.Int16
            "REGIONID": pl.Enum(["QLD1", "VIC1", "TAS1", "NSW1", "SA1", "SNOWY1"]),
            "STARTPERIOD": int,  # or pl.Int16
        }
    )
    # Deduplicate
    # We want one row per ['APCID']
    # Tie-breaker: greatest value of ['LASTCHANGED']
    .sort(["LASTCHANGED"], descending=False)
    .unique(subset=["APCID"], keep="last")
)

Nemosis

This table is not yet available in Nemosis.

Availability

Visibility: Private

This table is not available in the public monthly MMSDM archive. Is is only available to registered market participants over FTP inside a VPN.

Deduplication and PDR Loader Configuration

The primary keys are:

PDR Loader configuration does not mention this table, so it is unclear how to choose which row to keep when there are multiple rows for a given set of primary keys.

You should probably take the row with the maximum LASTCHANGED.

Indexes

This page as JSON (schema documented here, but may change)

Download a JSON Schema specification for this table.

Official AEMO schema documentation

Other Information

Package: HISTORICAL TABLES