megacable.com.mx
Jul 28, 2026
Database breach of Megacable Comunicaciones de Mexico, a major Mexican cable and telecommunications provider. The leak contains extensive internal business data including supplier records, bank account information, customer data, tax codes, AR/AP financial records, CDR (call detail records), network routing tables, and ERP system data consistent with an Oracle E-Business Suite installation.
Data found in this dataset
Source files
Expand any file to inspect its column headers and the LLM's field-mapping reasoning, recorded during ingestion.
AP_BANK_ACCOUNTS_ALL.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No consistent column structure detected in the provided data. The lines appear to be a series of numeric codes and identifiers without any discernible headers or delimiters that would define column mappings. This appears to be raw record identifiers rather than structured PII fields.
AP_BANK_BRANCHES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file contains only bank/supplier names and codes with no personal identifiers. All columns represent business entities and internal codes (e.g., bank names, branch names, internal reference codes). No PII fields are present. Per exclusion rules, any column containing 'Company', 'Business', or internal identifiers must be skipped. There are no email addresses, phone numbers, names, or other PII in the data.
AP_SUPPLIERSMV.csv1 column3,670 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] header 'VENDOR_NAME', values are full names (e.g., 'CALDERON SALCEDO MONICA', 'ENRIQUE ALMEIDA') |
Notes: Only column 3 contains PII (fullName). All other columns are internal business identifiers, dates, flags, codes, financial data, or system metadata per the exclusion rules.
AP_TAX_CODES_ALL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected in this structured file. All columns represent internal accounting/tax codes, numeric IDs, flags, and timestamps typical of an Oracle E-Business Suite ERP tax configuration table. Values include tax names (e.g., 'IVA 10%'), numeric codes, date timestamps, and system flags — none map to personal data fields.
AR_CUSTOMERSMV.csv2 columns1,323 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 44 | fullName | high | [44] header ATTRIBUTE10, values are full names (first + last) |
| 45 | fullName | high | [45] header ATTRIBUTE11, values duplicate full names from ATTRIBUTE10 |
Notes: 79 columns total, 2 contain PII (full names), rest are business/customer metadata, IDs, timestamps, flags. No emails, phones, addresses, DOB, SSN, or other PII detected in the first 50 rows.
AR_LOOKUPSMV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns represent internal business metadata and lookup codes (credit score commentary, attribute categories, dates, flags). No PII fields are present. Columns like LOOKUP_TYPE, LOOKUP_CODE, MEANING, and ATTRIBUTE fields contain business logic descriptors and values, not personal data. Dates are system timestamps, not DOB. All columns are skipped per exclusion rules for internal business data.
AR_TAX_GROUP_CODES_ALL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is an Oracle E-Business Suite financial/tax configuration table with internal system identifiers and business codes. No personal identifiable information (PII) is present in the sample rows. All columns represent internal reference codes, timestamps, flags, and system metadata that do not contain names, addresses, contact details, or other searchable personal data. The breach context indicates this is part of the ERP system's tax group and transaction category configuration tables.
AR_VAT_TAX_ALL_B_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business/accounting identifiers, timestamps, tax codes, financial flags, and system metadata. No personal PII fields (names, emails, phones, addresses, DOB, SSN) are present. The data appears to be tax/ERP configuration records from Oracle E-Business Suite with no customer or employee personal data exposed.
AR_VAT_TAX_ALL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal financial/tax identifiers, timestamps, flags, and accounting codes. No PII fields detected — VAT IDs are business identifiers, timestamps are non-DOB, and all other columns are system codes, flags, or numeric IDs. No emails, names, addresses, phones, SSNs, or passwords present.
AUDITORIA_A_BORRAR.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file contains only two columns: a numeric column (NUMERO) and a description column (DESCRIPCION). The NUMERO column contains numeric values that do not match any known PII patterns (they are not valid phone numbers, emails, etc.). The DESCRIPCION column contains generic text such as 'Pruebas' (tests) and department names like 'Atencion a Clientes' (customer service). There are no identifiable personal information fields present in the first 50 rows. Therefore, no PII columns can be mapped.
A_CONTACTOS.csv5 columns8,951 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'S_NOMBRE', values are full names (e.g., 'ALEJANDRO CUNILLE') |
| 3 | phone | high | [3] header 'S_TEL', values are 10-digit phone numbers with formatting |
| 4 | phone | high | [4] header 'S_CELULAR', values are mobile phone numbers with formatting |
| 8 | high | [8] header 'S_EMAIL', values contain '@' and domain structures | |
| 15 | password | high | [15] header 'S_PASSWORD', values appear to be raw passwords (non-hashed) |
Notes: 16 columns total, 5 contain PII (fullName, phone x2, email, password). Columns 0,1,5,6,7,9-14 are internal IDs, roles, notes, or non-PII codes and thus skipped.
A_CONTACTOS_1.csv4 columns8,951 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | fullName | high | [2] header 'S_NOMBRE', values are full names (e.g., 'ALEJANDRO CUNILLE', 'LIC. OSCAR VARGAS SANCHEZ') |
| 3 | phone | high | [3] header 'S_TEL', values are formatted phone numbers (e.g., '50-10-81-99', '5284-9741') |
| 4 | phone | high | [4] header 'S_CELULAR', values are formatted mobile numbers (e.g., '044-5416-1810', '(832) 721-6431') |
| 8 | high | [8] header 'S_EMAIL', values contain valid email addresses (e.g., 'acunille@dc.com', 'enrique.quiroz@obsidiana-corp.com') |
Notes: 16 columns total, 4 contain PII. Columns 0-1, 5-7, 9-15 contain internal IDs, job titles, notes, and passwords which are either non-PII or security-sensitive and should be handled appropriately.
A_CONTRATACIONES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal system identifiers, financial codes, and descriptive notes with no PII. No email, phone, name, address, DOB, SSN, or other personal identifiers detected. Values are numeric IDs, status codes, dates (contract dates), and free-text notes about equipment/cabinets. Megacable-2024 breach context confirms this is internal business/ERP data, not customer PII.
A_CONTRATACIONES_1.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal IDs, financial codes, timestamps, or free-text notes. No PII present. Columns like N_ID_CIRCUITO, N_ID_CLIENTE, N_ID_SERVICIO, and S_CUENTA are numeric identifiers. Dates (D_F_CONTRATO, D_F_INSTALACION, D_F_BAJA) are contract/service timestamps, not DOB. S_ESTATUS is a status code, S_CARACTERISTICAS and S_NOTAS are free-text notes or descriptions. No emails, names, addresses, phone numbers, or other PII fields are present.
CDRS_MEXCEDIDOS_LOCAL.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal business identifiers, timestamps, and system codes. No PII fields (email, phone, name, address, dob, ssn, etc.) are present. Columns like A_PARTY_NUMBER and B_PARTY_NUMBER are internal reference numbers, not personal phone numbers. The file contains call detail records and system tracking data from Megacable's Oracle E-Business Suite, with no customer PII exposed in this sample.
CDRS_MEXCEDIDOS_MASTER.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system fields, network routing codes, financial/tax codes, and technical indicators. No PII fields (names, emails, addresses, phones, DOB, SSN, etc.) are present. Values are numeric codes, timestamps, floating-point durations, and status flags typical of CDR (Call Detail Record) data.
CDRS_MIN_LOCAL.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business identifiers, timestamps, and transactional codes. No PII fields detected. Columns contain internal IDs (A_PARTY_NUMBER, B_PARTY_NUMBER, ID_CLIENTE, ID_CUENTA), call routing codes (INCOMING_ROUTE, OUTGOING_ROUTE), status codes (S_STATUS), financial codes (N_TARIFA, N_ID_CICLO), date stamps (ANSWER_DATE_TIME, D_FECHA_CORTE), duration metrics (EXT_DURATION_MINUTES, EXT_DURATION_SECONDS), and system codes (TIPO_LLAMADA, CALL_ID_NUMBER, EXT_CONFERENCIAS, A_PARTY_CATEGORY). No names, addresses, emails, phones, or other PII were found in the first 50 rows.
CDRS_MIN_MASTER.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns represent internal call detail record (CDR) data, network routing, billing indicators, and system codes. No fields map to email, phone, name, address, DOB, SSN, password, username, gender, suffix, or facebookId. The values are system-generated codes, numeric identifiers, timestamps, and technical indicators.
CE_STATEMENT_HEADERS_ALL.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file contains only three columns with numeric identifiers and dates. No PII fields are present. The columns appear to be internal IDs (numeric) and timestamps (dates), all of which must be skipped per exclusion rules. There are no email addresses, phone numbers, names, addresses, DOB, SSN, passwords, usernames, or other PII in the sample.
CE_STATEMENT_HEADERS_INT_ALL.csv0 rows
CE_STATEMENT_LINES_INTERFACE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal business identifiers, timestamps, financial codes, and empty fields. Column 0 shows numeric identifiers, column 1 is a date format (01-JAN-18) which is likely an internal transaction date, column 2 is numeric, column 3 is ISO date format (2018-01-02) likely an internal reference date, column 4 is a fixed string 'CLIABO' likely a business code, and the rest are either empty or contain business transaction codes, monetary values, or other non-PII data. No columns match patterns for email, phone, name, address, DOB, SSN, or other PII types.
CST_ITEM_MAX_TRANSACTIONMV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only two columns: TRANSACTION_DATE and INVENTORY_ITEM_ID. TRANSACTION_DATE is a timestamp and INVENTORY_ITEM_ID is an internal inventory identifier. Neither column contains PII according to the provided rules.
CTL_RUTA_SWITCH.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, status flags, timestamps, or network configuration data. No PII fields are present.
CTL_RUTA_SWITCH1.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business identifiers, site descriptions, traffic types, service names, and system statuses. No PII fields detected.
CTL_RUTA_SWITCH_HIST.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal business/technical identifiers and status fields. No PII fields detected. Columns like TRUNK_GROUP, SITIO, ID_CUENTA, N_NIR_CIUDAD are internal system codes, and date fields (D_FECHA_ALTA, D_FECHA_BAJA) are timestamps. No emails, names, addresses, phone numbers, or other PII present in the sample.
CT_ANILLO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file contains only location data (city/neighborhood names paired with country) with no personal identifiers. All columns represent business locations or generic place names, matching the breach context of Megacable's internal business data (supplier records, network routing tables). No PII fields present.
CT_APLICACIONES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file is a README or description file listing application names and IDs. It contains no personal or identifiable information. All columns are internal system identifiers and application names, which are not PII. Therefore, no columns map to PII fields.
CT_CARRIER_BCD.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All entries are business entities and operational codes (company names, traffic types, internal IDs). No personal identifiers (names, emails, phone numbers, etc.) are present in the first 50 rows.
CT_DASHB_ENUMS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file, but all visible columns appear to be internal business codes and categories (N_ID_ENUM, S_GRUPO_ENUM, S_DESCRIPCION, S_COMENTARIO). No PII fields are present in the first 50 rows. The data appears to be internal classification codes for churn types and related descriptions, not customer PII.
CT_DIAS_FERIADOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only holiday dates and descriptions - no PII fields present. The columns represent date (D_DIA_FERIADO) and description (S_DESCRIPCION) of Mexican holidays, with no personal information such as names, addresses, or other identifiers.
CT_FORMATOS_PROY_ENUMS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: File contains only lookup tables and configuration data - no PII fields present. All columns represent internal codes, statuses, and policy definitions with no personal information.
CT_GIRO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file contains only category codes and descriptions (e.g., BANCOS, AUTOMOTRIZ, CARRIER TELEFONIA LOCAL). No PII fields are present. All columns are business sector classifications and should be skipped.
CT_ICARE_CAUSAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing only internal business codes and statuses. No PII fields are present. All columns represent internal error codes, statuses, and descriptions from a telecommunications provider's network and customer service logs. There are no personal identifiers, contact details, or sensitive customer data in the provided sample.
CT_ICARE_ENUMS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a lookup table / reference file with no personal data. Columns represent failure severity codes, ticket statuses, event types, market types, platform types, network elements, etc. No PII fields detected.
CT_ICARE_GRUPO_CORREO.csv1 column16 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
CT_ICARE_GRUPO_PERSONAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a delimited file but lacks headers and contains only numeric identifiers. No PII fields are present. The columns appear to be internal IDs (N_ID_PERSONAL, N_ES_MAIL_O_PAGER, N_ID_GRUPO_CORREO) which must be skipped per exclusion rules for internal IDs.
CT_ICARE_PROBLEMA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal support / troubleshooting ticket fields (problem IDs, descriptions, severity codes, groups). No PII detected in sample values or headers. These are internal operational codes, not customer data.
CT_IOR_ENUMERACIONES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. File contains only internal codes, location identifiers, carrier names, service types, and status codes. No names, emails, phone numbers, addresses, or other personal data appear in the first 50 rows.
CT_IPS_SERVICIO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: The provided data is purely numeric with no discernible headers or structure. All rows contain only three numeric values that appear to be identifiers and IP addresses, with no PII fields present. There are no email addresses, names, or other personal identifiers visible in the sample data. The format appears to be a simple CSV without headers, but contains no mappable PII columns.
CT_MKT_REGION.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file appears to contain only internal business identifiers (region codes, carrier numbers, strategy flags) and geographic/country codes. All values represent system metadata rather than personal information. The column names and values are entirely non-personal and match the expected structure of Megacable's internal regional and carrier configuration tables.
CT_MKT_TARIFAS_LD.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business identifiers, dates, volumes, monetary values, and currency codes. No PII fields present.
CT_MONEDA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: The sample provided consists of only two rows with two columns each: ['1', 'USD'] and ['2', 'MXP']. These appear to be simple value pairs (likely identifiers and currency codes) with no PII present. There is no header row, and the data does not contain any identifiable personal information such as names, addresses, emails, phone numbers, dates of birth, or other PII fields. Based on the context of a breach involving business data and financial records, these columns likely represent internal codes or currency identifiers, which are not considered PII. Therefore, no columns map to PII fields.
CT_NPA_DIDW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file contains only country names and telephone network type information (Landline, Mobile, etc.). No personal identifiable information (PII) fields are present. The data appears to be a reference list of international phone network types rather than customer records.
CT_NPA_DID_PREFIX.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This file appears to be unstructured data consisting of numeric identifiers or account codes. There are no headers, and the values are purely numeric with no apparent PII patterns (emails, phone numbers, names, addresses, etc.). Based on the context of the breach (Megacable Comunicaciones), these are likely internal reference numbers, supplier codes, or financial identifiers rather than personal data. No PII columns detected.
CT_OPERADORES_SMS.csv0 rows
File structure
Notes: This is a free-form text file with no consistent delimiter or structure. Each line contains business-to-business relationship data in a narrative format, not structured columns. No PII columns are present.
CT_OPORTUNIDADES.csv4 rows
File structure
Notes: The file is free-form text with no consistent delimiter or column structure. Each line appears to be a separate record or note with varying content and length, containing business names, service descriptions, and technical specifications but no structured PII fields. No column mapping is possible.
CT_OT_PS_PLANTILLA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a free-form list of project templates and status codes. Columns are internal identifiers and descriptive text about network projects, work plans, and service tiers. No PII fields are present.
CT_PERMISOS_OBJETOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a headerless structured file containing only business category labels (e.g., 'ESTATUS DE PROYECTOS', 'ADMINISTRADOR'). No PII fields are present. All columns are internal business codes and should be skipped.
CT_TIPO_CUENTA.csv0 rows
File structure
Notes: The provided data is a free-form text listing of business categories and account types rather than a structured dataset with personal identifiable information columns. There are no consistent delimiters or columnar structure present, and each line represents a category name rather than individual records with PII fields. This matches the unstructured opt-out conditions: no consistent delimiter, varying line shapes, and no embedded emails/phones visible in the sample.
CT_TIPO_MOVTOS.csv0 rows
File structure
Notes: This is not a structured dataset but a list of service codes and descriptions. There are no columns with PII data. The content appears to be a reference list of service types and codes rather than actual customer records.
CT_USO_TRONCAL.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be an internal business lookup table with usage codes and descriptions. No PII fields present. Columns are N_ID_USO (numeric ID), S_DESCRIPCION (descriptive string), N_B_ESTATUS (binary flag). All values are business codes and status indicators, not personal data.
CT_USUARIOS.csv3 columns5,018 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | fullName | high | [0] header 'N_ID_CLIENTE' suggests customer identifier but values show human-readable names; maps to fullName as it contains full names |
| 1 | username | high | [1] header 'S_USUARIO' translates to 'S_USER', values are alphanumeric strings used as login identifiers |
| 2 | password | high | [2] header 'S_PASSWORD' translates to 'S_PASSWORD', values are hashed strings |
Notes: Only three columns contain PII: fullName (customer names), username (login IDs), and password (hashed passwords). All other columns appear to be internal system identifiers, numeric codes, or empty fields, and are mapped to skip per exclusion rules.
C_AREAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only organizational area codes and names - no personal identifiable information. All columns represent internal department codes (N_ID_AREA), area names (S_AREA), abbreviations (S_ABREVIACION), and status codes (N_B_ESTATUS). No PII fields present.
C_CATEGORIAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be a category mapping table with no PII fields. Columns represent category IDs (N_ID_C_CATEGORIA), category codes (S_CATEGORIA), and descriptions (S_DETALLE). The content consists of service categories, failure categories, and ISO 9000 documentation controls, which are internal business classifications and do not contain any personal information.
C_CATEGORIAS_1.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be a category mapping table with no personal identifiable information (PII). The columns represent internal service categories and descriptions (N_ID_C_CATEGORIA: numeric category ID, S_CATEGORIA: short category name, S_DETALLE: detailed description). There are no names, addresses, emails, phone numbers, or other PII fields present.
C_CUENTAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a two-column structured file but both columns appear to be internal accounting / customer reference IDs (S_CUENTA = account number, N_ID_CLIENTE = client ID). Values are numeric and sequential with no PII characteristics. No email, phone, name, address, or other personal identifiers are present in the sample. All columns are internal business identifiers and must be skipped per exclusion rules.
C_CUENTAS_1.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only two columns: S_CUENTA and N_ID_CLIENTE, which appear to be internal account and client identifiers. No PII fields are present. The data consists of numeric codes with no names, addresses, emails, or other personal identifiers. These are clearly internal system identifiers and should be skipped per the rules.
C_ESTADOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only geographic/state/country codes and identifiers. No PII fields are present — all columns are internal state/region references or country codes. Columns map to business/internal data only.
C_ESTADOS_1.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only geographic/state and country identifiers (N_ID_ESTADOS, S_ESTADOS, N_ID_PAIS). No PII fields are present. All columns represent internal region codes, state names, and country IDs — these are business reference data, not personal identifiers. No emails, names, addresses, or other PII appear in the sample.
C_ESTADOS_2.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a list of state/region codes with numeric IDs and descriptive names. No PII fields are present. Columns map to geographic identifiers only, which are not considered personally identifiable information under the provided classification rules.
C_MENUS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only application access control metadata - menu items, feature flags, and permission descriptors. No PII is present in the visible rows. All entries are system configuration records with numeric IDs and static descriptions.
C_PERFILES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: File contains only internal role/profile identifiers and descriptions with no PII present. All columns are internal system role codes and textual descriptions of permissions.
C_PERSONAL_HIST.csv2 columns730 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | fullName | high | [1] values are full person names like 'FABIOLA CASTILLO', 'SANDRA OROZCO', etc. |
| 6 | dob | high | [6] values match YYYY-MM-DD date pattern, clearly dates of birth |
Notes: CSV file with 50 rows showing employee records from Megacable Comunicaciones. Only columns containing full names and dates of birth were identified as PII. All other columns contain job titles, department IDs, employee numbers, and timestamps — none contain additional personal identifiable information.
C_PERSONAL_IH.csv1 column1,512 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
C_PERSONAL_ORIGINAL.csv1 column1,504 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
C_PUNTO_PRESENCIA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: All columns contain only company names, location codes, numeric identifiers, and empty values. No PII present. Columns map to business entity data, internal IDs, and flags — all excluded by mandatory rules (Company/Business prefixes, internal IDs).
FND_FLEX_VALUES_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal database identifiers, timestamps, and system flags with no PII. No email, phone, name, address, or other personal identifiers are present in the first 50 rows.
FND_FLEX_VALUES_TL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only internal Oracle E-Business Suite metadata: Flex value IDs, language codes, timestamps, user IDs, and description strings. No PII fields are present. All columns are internal system identifiers or status flags.
FND_LOOKUP_VALUESMV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are metadata/system configuration fields from Oracle E-Business Suite lookup tables. No PII present. Columns like LANGUAGE, TERRITORY_CODE, ATTRIBUTE fields contain business codes, not personal data. Timestamps (CREATION_DATE, LAST_UPDATE_DATE) and IDs (CREATED_BY, LAST_UPDATED_BY) are internal system fields per exclusion rules.
FND_TERRITORIES_TL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns represent internal business metadata (territory codes, creation timestamps, descriptions, sync statuses) with no PII. No names, addresses, emails, phones, or other personal data present.
GL_CODE_COMBINATIONS_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal accounting/financial identifiers, flags, segment codes, and system metadata consistent with an Oracle E-Business Suite financial module. No personal names, addresses, emails, phones, or other PII appear in headers or sample values. This is purely internal business data from the ERP system.
GL_DAILY_RATES_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business data (currencies, conversion rates, timestamps, internal IDs). No PII fields detected. Columns like CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN are internal numeric identifiers. ATTRIBUTE columns appear to be generic placeholder fields with no visible PII in sample values.
GL_DAILY_RATES_VMV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal financial/temporal fields (currency conversion, row IDs, status codes, timestamps, privileges). No PII present. All columns match exclusion rules: conversion rates, internal IDs, status flags, timestamps.
HR_ALL_ORGANIZATION_UNITS_TLMV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains only organizational/business metadata (organization IDs, language codes, names of business groups, timestamps). No personal identifiable information (PII) is present. All columns are internal business identifiers, timestamps, or language settings — none map to PII fields. Therefore, no columns are mapped to PII categories.
HZ_CUSTOMER_PROFILES_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns are internal system identifiers, status flags, dates, numeric counters, configuration settings, and other non-personal data typical of an Oracle E-Business Suite financial/customer account management table. No names, addresses, contact details, or other personally identifiable information appear in the first 50 rows.
HZ_CUST_ACCOUNTS_MVIEW.csv1 column0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 79 | password | high | [79] column name 'PASSWORD_TEXT' matches pattern, values are plaintext passwords |
Notes: Only column 79 (PASSWORD_TEXT) contains PII. All other columns are internal IDs, timestamps, financial codes, status flags, or generic business data. No names, emails, addresses, phones, DOB, or SSN appear in the sample.
HZ_CUST_ACCT_SITES_ALL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, status codes, and flags. No PII fields detected.
HZ_CUST_SITE_USES_ALL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, flags, financial codes, and system metadata. No PII fields detected.
HZ_LOCATIONS_MVIEW.csv5 columns14,614 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 54 | country | high | [54] header 'COUNTRY', values are ISO country codes (MX) |
| 55 | address1 | high | [55] header 'ADDRESS1', values are full street addresses |
| 59 | city | high | [59] header 'CITY', values are Mexican cities |
| 60 | zip | high | [60] header 'POSTAL_CODE', values are Mexican postal codes (5 digits) |
| 61 | state | high | [61] header 'STATE', values are Mexican states (CIUDAD DE MÉXICO) |
Notes: Identified 5 PII columns: country, address1, city, zip, and state. All other columns are internal system identifiers, timestamps, flags, or unstructured attributes with no personal data. This is consistent with Oracle E-Business Suite address book tables.
HZ_PARTIES_MVIEW.csv11 columns13,216 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 70 | firstName | high | [70] header 'PERSON_FIRST_NAME', values are common given names |
| 71 | middleName | high | [71] header 'PERSON_MIDDLE_NAME' |
| 72 | lastName | high | [72] header 'PERSON_LAST_NAME', values are common surnames |
| 73 | suffix | high | [73] header 'PERSON_NAME_SUFFIX', values likely generational suffixes |
| 81 | country | high | [81] header 'COUNTRY', values are country codes |
| 82 | address1 | high | [82] header 'ADDRESS1', values are street addresses |
| 83 | address2 | high | [83] header 'ADDRESS2' |
| 86 | city | high | [86] header 'CITY', values are city names |
| 87 | zip | high | [87] header 'POSTAL_CODE', values match postal codes |
| 88 | state | high | [88] header 'STATE', values are state names |
| 97 | high | [97] header 'EMAIL_ADDRESS', values likely emails |
Notes: 126 columns total, 11 contain PII, rest are business/operational fields, IDs, flags, timestamps, financial data
HZ_PARTY_SITES_MVIEW.csv164 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
JTF_RS_SALESREPS_MVIEW.csv1 column93 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 8 | fullName | high | [8] header 'NAME', values are full names like 'GAMBOA EVELYN' |
Notes: Only column 8 (NAME) contains PII (fullName). All other columns are internal IDs, timestamps, status codes, or generic attributes — none contain email, phone, address, DOB, SSN, password, or username. The NAME field contains full names, which are valid PII.
MASTER_MET.csv0 rows
MTL_SYSTEM_ITEMS_B_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: None of the columns contain PII. All columns are internal identifiers, timestamps, flags, inventory codes, accounting references, and configuration settings. No email, phone, name, address, date-of-birth, SSN, gender, or password fields are present. The data appears to be purely operational/ERP system metadata from Megacable's Oracle E-Business Suite.
MTL_SYSTEM_ITEMS_TL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, and product descriptions with no PII. No emails, names, addresses, or other personal data present in the first 50 rows.
MVW_ITEM_TRANSAC_DISTRIBUTION.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns represent internal business/financial data (transaction dates, account numbers, inventory codes, transaction types). No PII fields present. Values are system-generated identifiers, monetary amounts, and operational codes. This aligns with the breach description of ERP/financial system data rather than customer PII.
NTV2_XML_DATA.csv0 rows
OGIS_GEOMETRY_COLUMNS.csv0 rows
OGIS_SPATIAL_REFERENCE_SYSTEMS.csv0 rows
PA_COUNTRY_VMV.csv0 rows
PER_ALL_ASSIGNMENTS_F_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns are internal IDs, timestamps, flags, or business-specific codes. Values are numeric IDs, status codes, or generic system timestamps with no personal information.
PER_ALL_PEOPLE_F_MVIEW.csv8 columns180 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | lastName | high | header "LAST_NAME" resolves to PII field "lastName" |
| 17 | skip | high | header "DATE_OF_BIRTH" resolves to PII field "dob" |
| 18 | high | header "EMAIL_ADDRESS" resolves to PII field "email" | |
| 22 | firstName | high | header "FIRST_NAME" resolves to PII field "firstName" |
| 24 | fullName | high | header "FULL_NAME" resolves to PII field "fullName" |
| 49 | gender | high | header "SEX" resolves to PII field "gender" |
| 51 | suffix | high | header "SUFFIX" resolves to PII field "suffix" |
| 55 | skip | high | header "WORK_TELEPHONE" resolves to PII field "phone" |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
PO_DISTRIBUTIONS_S.csv0 rows
File structure
Notes: This is a free-form text file containing only a single line with an internal reference number (N_CONSECUTIVO: 5224955). No structured columns or PII present. The file appears to be a snippet of an internal identifier from the Megacable Comunicaciones breach, not a data record with personal information.
PO_HEADERS_S.csv0 rows
File structure
Notes: This is a free-form text file containing only a single line with an internal identifier ('N_CONSECUTIVO') and a numeric value. There is no structured column format, no repeated pattern, and no PII present. This appears to be a fragment of a log or data export header with no actual records or personal data.
PO_LINES_S.csv0 rows
File structure
Notes: File is free-form text with no consistent column structure. The sample shows a single line containing only an internal identifier ('N_CONSECUTIVO') and a numeric value (5314337), typical of a database dump or log file header. No PII fields are present in the sample, and there is no repeating structure to map columns.
PO_VENDORS_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: File contains only internal accounting/financial identifiers and flags (CODE_COMBINATION_ID, LAST_UPDATE_DATE, LAST_UPDATED_BY, etc.). No PII fields present. All columns map to internal ERP system metadata, financial segments, or status flags. No emails, names, addresses, DOB, SSN, or other personal identifiers detected in the sample rows.
PO_VENDORS_MVIEW_2017.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All visible columns are internal system identifiers, timestamps, flags, financial codes, and business metadata. No personal names, addresses, emails, phone numbers, or other PII appear in the first 50 rows.
PO_VENDOR_SITES_ALL_MVIEW.csv7 columns4,713 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 13 | address1 | high | [13] header 'ADDRESS_LINE1', values are street addresses |
| 15 | address2 | high | [15] header 'ADDRESS_LINE2', values are secondary address lines |
| 17 | city | high | [17] header 'CITY', values are city names |
| 18 | state | high | [18] header 'STATE', values are state abbreviations |
| 19 | zip | high | [19] header 'ZIP', values are 5-digit postal codes |
| 21 | country | high | [21] header 'COUNTRY', values are 'MX' (Mexico) |
| 23 | skip | high | [23] header 'PHONE', values are numeric phone numbers |
Notes: Only 7 PII columns identified among 122 total columns. Most columns are internal business identifiers, financial codes, timestamps, and system flags per breach context.
RA_HCUSTOMERS_MV.csv4 columns0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 108 | firstName | high | [108] header 'PERSON_FIRST_NAME' directly maps to firstName; values empty in sample but schema clearly holds personal first names |
| 109 | middleName | high | [109] header 'PERSON_MIDDLE_NAME' directly maps to middleName |
| 110 | lastName | high | [110] header 'PERSON_LAST_NAME' directly maps to lastName |
| 111 | suffix | high | [111] header 'PERSON_SUFFIX' maps to suffix (generational/credential suffixes Jr, Sr, etc.) |
Notes: 120-column Oracle E-Business Suite AR customer master table (megacable-2024). All 50 sampled rows are ORGANIZATION party type; PERSON_* columns (108-113) are empty in the sample but are named PII schema fields that may contain data for PERSON-type party rows elsewhere in the file. CUSTOMER_NAME contains legal business entity names and is skipped per company-name exclusion rules. TAX_REFERENCE (RFC codes) are Mexican business tax identifiers, not personal SSNs. ATTRIBUTE10/ATTRIBUTE11 contain informal contact name strings but are generic EAV attribute columns without reliable PII semantics. PERSON_PRE_NAME_ADJUNCT (107) is an honorific prefix field and is skipped.
RA_TERMS_TL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, and status flags. No PII fields present. Columns like TERM_ID, DESCRIPTION, NAME, LANGUAGE, SOURCE_LANG, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, ZD_EDITION_NAME, and ZD_SYNC are all internal business data and system metadata. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII fields are present.
RDF_PARAMETER.csv0 rows
File structure
Notes: This is not a delimited data file but a series of key-value records describing Oracle E-Business Suite components and versions. It lacks any personal identifiable information (PII) fields and appears to be system metadata rather than customer or user data. There are no structured columns to map to PII fields.
SDO_COORD_AXES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal coordinate/axis system identifiers, orientation codes, abbreviations, unit of measure IDs, and order positions. Values are technical codes and directional abbreviations with no personal information.
SDO_COORD_AXIS_NAMES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The file contains only coordinate and geometric axis data (geodetic, geocentric, local axes, etc.) with no personal identifiable information. All columns are technical/engineering measurements and identifiers, none map to PII fields.
SDO_COORD_OPS.csv806 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
SDO_COORD_OP_METHODS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal geodetic/projection metadata codes and names (no PII). COORD_OP_METHOD_ID is an internal ID, COORD_OP_METHOD_NAME contains projection method names, LEGACY_NAME contains alternate method names, REVERSE_OP is a flag, INFORMATION_SOURCE and DATA_SOURCE contain reference documentation sources, IS_IMPLEMENTED_FORWARD and IS_IMPLEMENTED_REVERSE are boolean flags. No personal or sensitive data present.
SDO_COORD_OP_PARAMS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains structured coordinate reference system (CRS) metadata parameters from EPSG guidance notes and OGP standards. No PII fields (email, phone, names, addresses, DOB, SSN, passwords, usernames) are present. All columns are technical descriptors (parameter IDs, names, sources, units of measure) related to geospatial transformations and coordinate systems. No sensitive personal data was found in the first 50 rows.
SDO_COORD_OP_PARAM_USE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only internal business parameters and configuration codes (COORD_OP_METHOD_ID, PARAMETER_ID, LEGACY_PARAM_NAME, SORT_ORDER, PARAM_SIGN_REVERSAL). No PII fields are present. The data appears to be system configuration parameters from an Oracle E-Business Suite installation, with numeric IDs and flag values. All columns are internal identifiers or settings flags, none contain personal information.
SDO_COORD_OP_PARAM_VALS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected. All columns contain internal system identifiers, numeric parameters, and reference codes with no personal information. Values are purely technical (IDs, numeric values, XML references). This aligns with the breach description of internal business/ERP data rather than customer PII.
SDO_COORD_OP_PATHS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No PII columns detected. File appears to be purely operational transactional data with concatenated operation IDs and references to internal system IDs. No personal identifiers, addresses, emails, phones, or dates are present in the sample.
SDO_COORD_REF_SYS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are technical metadata about coordinate reference systems and projections (geospatial data). No PII fields present. Columns map to EPSG database codes, projection parameters, legacy system flags, and validity indicators. This is infrastructure data, not customer records.
SDO_COORD_SYS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains coordinate system metadata from EPSG and OGP. It describes various spatial reference systems but contains no personal or identifiable information. All columns are technical identifiers, names, and descriptions of coordinate systems, units of measure, and orientations — none map to PII fields.
SDO_CRS_GEOGRAPHIC_PLUS_HEIGHT.csv0 rows
File structure
Notes: The provided data appears to be a list of numeric identifiers or codes (SRID values) with no consistent delimiter, structure, or contextual fields. There are no visible headers, and each line contains only a single numeric value. The values do not resemble typical PII patterns (emails, phone numbers, names, etc.), and the format does not align with structured data like CSV or TSV. This is likely an index or reference list rather than a dataset containing personal information. No PII columns can be identified.
SDO_CS_CONTEXT_INFORMATION.csv0 rows
SDO_CS_SRS.csv811 rows
File structure
Notes: free-form text with embedded spatial/projection data, no consistent row structure
SDO_DATUMS.csv107 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
SDO_DATUMS_OLD_SNAPSHOT.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is not structured PII data; it's a reference table of geographic coordinate reference systems and datums. Columns contain geographic names and numerical shift/rotation/scale values. No personal identifiable information present.
SDO_DIST_METADATA_TABLE.csv0 rows
SDO_ELLIPSOIDS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected. File contains geodetic ellipsoid parameters: names, semi-major/minor axes, flattening values, source references. All columns represent geographic reference systems, not personal data.
SDO_ELLIPSOIDS_OLD_SNAPSHOT.csv0 rows
File structure
Notes: This file contains only geographic and geodetic reference data (ellipsoids, axes, flattening values). No personal or identifiable information present. The format is unstructured tabular data about coordinate systems, not customer PII.
SDO_FEATURE_USAGE.csv0 rows
File structure
Notes: free-form text with no consistent column structure — appears to be Oracle E-Business Suite feature configuration flags, not customer PII. No identifiable rows or delimiters present in the sample.
SDO_GEOR_DDL__TABLE_.csv0 rows
SDO_GEOR_PLUGIN_REGISTRY.csv0 rows
SDO_GEOR_XMLSCHEMA_TABLE.csv0 rows
File structure
Notes: The file is an XML schema definition for Oracle GeoRaster metadata, containing only technical documentation and structure definitions. No personal or identifiable data is present in the provided rows.
SDO_GR_MOSAIC_0.csv0 rows
SDO_GR_MOSAIC_1.csv0 rows
SDO_GR_MOSAIC_2.csv0 rows
SDO_GR_MOSAIC_3.csv0 rows
SDO_GR_MOSAIC_CB.csv0 rows
SDO_GR_PARALLEL.csv0 rows
SDO_GR_RDT_1.csv0 rows
SDO_GR_RDT_2.csv0 rows
SDO_INDEX_HISTOGRAM_TABLE.csv0 rows
SDO_PC_BLK_TABLE.csv0 rows
SDO_PREFERRED_OPS_SYSTEM.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a pure coordinate transformation metadata file with no PII fields. It contains SRID codes and operational IDs for coordinate system conversions between 2065 and 102067, typical of GIS or geospatial databases. No personal or customer data is present.
SDO_PREFERRED_OPS_USER.csv0 rows
SDO_PRIME_MERIDIANS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only geographic and coordinate system metadata (Prime Meridian IDs, names, longitudes, units of measure, sources). No PII fields (emails, names, addresses, etc.) are present. All columns are technical identifiers or geographic references, therefore no columns map to PII fields.
SDO_PROJECTIONS_OLD_SNAPSHOT.csv0 rows
File structure
Notes: This file contains only geographic projection names and system references, no structured records or personal information. It is a list of map projection types and geographic coordinate systems, not a dataset with personal or identifiable information.
SDO_SRIDS_BY_URN.csv0 rows
SDO_SRIDS_BY_URN_PATTERN.csv0 rows
SDO_ST_TOLERANCE.csv0 rows
SDO_TIN_BLK_TABLE.csv0 rows
SDO_TIN_PC_SEQ.csv0 rows
SDO_TIN_PC_SYSDATA_TABLE.csv0 rows
SDO_TOPO_DATA.csv0 rows
SDO_TOPO_RELATION_DATA.csv0 rows
SDO_TOPO_TRANSACT_DATA.csv0 rows
SDO_TXN_IDX_EXP_UPD_RGN.csv0 rows
SDO_TXN_JOURNAL_GTT.csv0 rows
SDO_TXN_JOURNAL_REG.csv0 rows
SDO_UNITS_OF_MEASURE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal unit of measure metadata (UOM_ID, UNIT_OF_MEAS_NAME, etc.). No PII present. Values are measurement codes, unit names, conversion factors, and legacy flags — typical ERP configuration data. No emails, names, addresses, or other personal data.
SDO_WFS_LOCAL_TXNS.csv0 rows
SDO_WS_CONFERENCE.csv0 rows
SDO_WS_CONFERENCE_PARTICIPANTS.csv0 rows
SDO_WS_CONFERENCE_RESULTS.csv0 rows
SDO_XML_SCHEMAS.csv12 rows
File structure
Notes: File is an XML schema definition (geometry.xsd) for GML (Geography Markup Language) — not a data record file. Contains only XML schema declarations and structural metadata, no actual PII data. The sample shows XML elements and types for geometric constructs, not columnar data.
SRSNAMESPACE_TABLE.csv0 rows
TARIFAS_LOCAL.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns contain only internal identifiers (ID_CLIENTE, ID_CUENTA), dates (D_FECHA_CORTE), and numeric tariff/rate values (TARIFA_LOCAL, TARIFA_CELULAR, etc.). No names, addresses, emails, phones, or other personal data present in the first 50 rows.
TARIFAS_LOCAL_BK.csv10 columns0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | Internal ID: numeric identifier pattern |
| 1 | skip | high | Internal ID: numeric identifier pattern |
| 2 | skip | high | Timestamp: date format indicates non-DOB date |
| 3 | skip | high | Financial/numeric: tariff/rate value |
| 4 | skip | high | Financial/numeric: tariff/rate value |
| 5 | skip | high | Financial/numeric: tariff/rate value |
| 6 | skip | high | Financial/numeric: tariff/rate value |
| 7 | skip | high | Financial/numeric: tariff/rate value |
| 8 | skip | high | Financial/numeric: tariff/rate value |
| 9 | skip | high | Financial/numeric: account type code |
Notes: All visible columns contain only internal business identifiers, financial/rate values, and timestamps. No PII fields (names, emails, phone numbers, addresses, etc.) are present in this dataset. The columns map exclusively to internal IDs, account numbers, dates, and tariff/rate codes.
TB_AUSENCIAS.csv1,550 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
TB_BS_DATA.csv3 columns1,338,702 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | high | unlabeled column — sampled values parse as email addresses | |
| 8 | high | unlabeled column — sampled values parse as email addresses | |
| 90 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
TB_CARRIERS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a simple two-column table listing telecommunications operators and numeric keys. No PII fields are present. The columns are operator names and numeric identifiers (N_CLAVE) which are internal business codes, not personal identifiers.
TB_CFG_APLICACIONES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The file is a structured CSV with no PII columns. All entries appear to be internal application IDs, numeric codes, paths, and system metadata (e.g., N_ID_APLICACION, S_CLAVE, S_VALOR, S_DESCRIPCION). No names, addresses, emails, phone numbers, dates of birth, SSNs, passwords, usernames, or other PII fields are present. Values are identifiers, lists of IDs, file paths, and system flags.
TB_CICLO_FACTURACION_LD.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains only internal business cycle metadata: cycle IDs, start/end days, periodicity codes (M=monthly, Q=quarterly, S=semesterly). No personal identifiers or PII present. All columns are internal scheduling/booking codes and therefore skipped per exclusion rules.
TB_CONCILIA_TMX_LD.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. This is a pure call detail record (CDR) dataset with only numeric identifiers (origin/destination numbers), timestamps, durations, and monetary amounts. No names, addresses, emails, or other personal data appear in the header or sample values. All columns fall under skip categories: N_NUM_ORIGEN/N_NUM_DESTINO are internal network identifiers, D_FECHA_LLAMADA is a timestamp, N_DURACION is duration, N_IMPORTE is monetary amount, S_POBLACION appears to be a location code, N_NO_800 is a flag, N_X_COBRAR is a billing flag.
TB_CONEXIONES.csv1 column4,770 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | username | high | [1] header 'S_USUARIO', values appear to be user identifiers |
Notes: This appears to be system logs from an Oracle E-Business Suite installation. Only the user identifier column (S_USUARIO) contains PII. All other columns are system timestamps, connection codes, error codes, and error messages — no PII present.
TB_CONEXIONES_1.csv0 rows
TB_CORPORATIVO.csv0 rows
TB_COSTO_X_CARRIER.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns identified. The file contains only business data: country codes (N_CODIGO_PAIS), carrier IDs (N_ID_CARRIER), NPAs (N_ID_NPA), costs (N_COSTO), currency codes (N_ID_MONEDA), destinations (S_DESTINO), and date ranges (D_FECHA_INICIO, D_FECHA_FIN). No personal identifiers (names, addresses, emails, etc.) are present.
TB_CPP.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No PII columns present - this is a list of numeric ranges (NUM_INI, NUM_FINAL, NIR_INI, NIR_FIN) likely representing account or customer number ranges. Contains only numeric identifiers with no names, addresses, emails, or other personal data. All columns are skip per rules (internal IDs, counters).
TB_CUENTA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: All columns appear to be internal identifiers, timestamps, and financial/transactional data. No PII fields detected. Columns 0-43 are internal IDs, timestamps, flags, and numeric values consistent with ERP system data (e.g., 'Oficina de Representacion' appears to be business unit names, not personal names). No emails, phone numbers, addresses, or other PII visible in the sample.
TB_CUENTAS_CORPORATIVO.csv0 rows
File structure
Notes: free-form text with no consistent delimiter structure; appears to be pairs of numeric values (possibly IDs) without any column headers or identifiable PII patterns
TB_DASHB_ADMIN_CTRLF_CONECT.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be a metadata listing of files rather than actual records containing PII. The columns contain identifiers (N_ID_FILE), filenames (S_NOMBRE_FILE), file sets (S_FILE_SET), timestamps (D_FECHA_ULTIMOPROCESO, D_FECHA_DE, D_FECHA_A), status flags (N_STATUS), and record counts (N_REGISTROS). No PII fields are present in the data shown.
TB_DASHB_APROV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a purely transactional financial dataset with no PII columns. All columns represent internal accounting identifiers (N_ID_CLIENTE, N_ID_SERV_CUENTA), monetary values (N_MONTO_APROV), and date codes (S_MES_ANIO, N_ID_MOVTO). No names, addresses, emails, phones, DOB, SSN, or other PII fields are present. The data appears to be Oracle E-Business Suite transaction logs from Megacable's billing system.
TB_DASHB_CHURN_HIST.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain purely numerical or timestamp data with no discernible PII patterns. Fields appear to represent internal business metrics (IDs, amounts, dates, ratios) rather than personal information. No emails, names, addresses, or other PII were identified in the sample.
TB_DASHB_DATA_CONECT.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to contain only internal numeric identifiers and counters (N_ID_FILE, S_TRKGR_PNR, S_ACTSI_ZE). These match the exclusion rules for internal IDs and transactional counters. The values are purely numeric codes with no personal data characteristics.
TB_DASHB_OBJETIVOS_PKI.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The data contains only internal KPIs, targets, and performance metrics (e.g., service availability, budget compliance, project timelines). No personal identifiers, contact details, or sensitive customer data are present.
TB_DASHB_OBJETIVOS_SEG.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal business tracking fields: years, area IDs, objective IDs, follow-up IDs, status codes, internal notes, and dates. No PII fields detected. Values are internal codes, percentages, status strings, and dates that do not represent birthdays or other personal identifiers. This is consistent with internal ERP/CRM tracking data from Megacable's Oracle E-Business Suite.
TB_DASHB_RPT_VENTAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected. All values represent business/client names and monetary transactions. No email addresses, phone numbers, dates of birth, or other personal identifiers are present in the first 50 rows.
TB_DASHB_VTAS_CAMBIO_ETAPAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains business data and sales pipeline records, but NO identifiable personal information. All columns represent company names, opportunity codes, dates, and sales stages. There are no personal names, addresses, contact details, or other PII fields present.
TB_DASHB_VTAS_CONTACTOS.csv1 column9,829 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
TB_DASHB_VTAS_EDIFICIOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business identifiers, location codes, and system metadata. No PII present. Columns like S_EDIFICIO contain building addresses but are business locations (not personal residences), and all timestamps/IDs are internal system fields.
TB_DASHB_VTAS_METAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain purely numeric IDs and date/amount values. No PII fields (email, phone, name, address, DOB, SSN, gender, etc.) are present. Columns map to internal identifiers, metadata dates, and monetary values — all skip per exclusion rules.
TB_DASHB_VTAS_PERSONAL.csv1 column26 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 5 | high | unlabeled column — sampled values parse as email addresses |
Notes: Heuristic auto-detection: header-named PII columns confirmed by data conformance
TB_DESTINOS_ESPECIALES_LDI.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only numeric identifiers and monetary values (N_ID_CUENTA, N_ID_NPA, N_ID_VOLUMEN, N_MONTO, N_NUM800). No personal identifiable information (PII) fields are present. Columns map to internal business IDs, volume counters, monetary amounts, and flags — all skip categories per exclusion rules.
TB_DETALLE_CREDITO_MVW.csv3 columns1,589 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 1 | address1 | high | [1] header 'ADDRESS1', values are full street addresses |
| 2 | city | high | [2] header 'CITY', values are city names |
| 3 | zip | high | [3] header 'POSTAL_CODE', values are 5-digit postal codes |
Notes: 12 columns total, 3 contain PII (address1, city, zip). Others are internal IDs, financial codes, or static values. No email, phone, name, or DOB columns present.
TB_DETALLE_DIDS_CABLE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No PII columns detected. File appears to contain only numeric IDs and date pairs, consistent with internal business records (likely invoice or transaction IDs with date ranges). No emails, phone numbers, names, addresses, or other personal data visible in the sample.
TB_DETALLE_SERVICIO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: The provided data is purely numerical and lacks any headers or identifiable fields. All rows contain only numeric values with no textual patterns indicative of PII such as names, emails, or addresses. There is no structure to map to known PII categories. Therefore, no columns can be mapped to PII fields.
TB_DOC_TIPS_SEGURIDAD.csv0 rows
File structure
Notes: file is a README/notes document with policy statements and security guidelines, not structured data. contains no column-based PII fields
TB_EDIFICIOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain only internal IDs, counters, flags, or business codes. No PII fields (email, phone, name, address, DOB, SSN, etc.) are present. Columns 23-25 contain dates but they are business process dates (not DOB), and columns 0-22 and 26-30 are internal numeric codes, counters, or empty strings. No email-like patterns (@) or phone-like patterns (10-digit numbers) appear.
TB_EDIFICIOS_SF.csv6 columns17,587 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | address1 | high | [3] values are street addresses with avenue/street names and numbers (AV DEL IMAN RNDA CREPUSCULO # 740, PRESIDENTE MAZARYK 191) |
| 13 | state | high | [13] values are Mexican states/regions (CIUDAD DE MÉXICO, DISTRITO FEDERAL, NUEVO LEON) |
| 14 | city | high | [14] values are city/municipality names (COYOACAN, AZCAPOTZALCO, MIGUEL HIDALGO, MONTERREY) |
| 15 | zip | high | [15] values are 5-digit Mexican postal codes (04530, 02020, 04200, 11700, 64650, 15620) |
| 17 | address2 | medium | [17] values appear to be neighborhood/district names (INSURGENTES CUICUILCO, SAN MARCOS, POLANCO, CAMPESTRE CHURUBUSCO, BOSQUE DE LAS LOMAS) |
| 18 | address1 | medium | [18] duplicate/variant of address field; values are full street addresses (AV DEL IMAN RNDA CREPUSCULO 740, PRESIDENTE MASARYK 191, CERRO LOS REMEDIOS 27) |
Notes: 37 columns total. Columns 0, 1, 4, 6, 8 are internal Salesforce/Oracle record IDs (skip). Columns 2, 12, 24, 26, 30, 31, 35, 36 are flags/counters (skip). Columns 5, 7, 9 are timestamps (skip). Columns 10, 19, 25, 27, 28 are empty or sparse (skip). Columns 11, 20, 21, 22, 23, 29, 34 are business/service metadata (skip). Columns 32, 33 are latitude/longitude coordinates (skip). Mapped 4 definite PII address components: state, city, zip, and two address1 variants. Column 17 (neighborhoods) mapped as address2 (lower confidence, but contextually valid secondary address detail).
TB_ENTRADA_TARGET.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns identified in this file. The data appears to be purely numerical and date-based (MINUTOS, N_NIR_CIUDAD, DIA) with no personal identifiers, names, addresses, or contact details. Likely internal operational or billing data from Megacable's systems.
TB_ENTRADA_UVM_UNITEC.csv3 columns12 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'S_USERID', values are alphanumeric strings likely usernames |
| 5 | fullName | high | [5] header 'S_OTHERPARTYNAME', values are human names like 'alma_balbuena' and 'usuario_disponible24' |
| 6 | skip | high | [6] header 'S_EXTENSION', values are 10-digit numbers matching Mexican phone formats |
Notes: CSV file with 50 rows of call detail records from Megacable. Contains caller/receiver party numbers, timestamps, duration, and internal client IDs. Only columns 4-6 contain PII (username, full name, phone extension). All other columns are internal system identifiers, timestamps, or duration metrics and are skipped per rules.
TB_ESPECIAL_CABLE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns identified. File contains only numeric identifiers (N_ID_NPA), country names (S_PAIS), and numeric tariff values (N_TARIFA). No email, phone, name, address, or other personal data present. This appears to be a reference table of international dialing codes and tariff rates.
TB_FACTURARESUMEN.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain business/account data (customer names are company names, legal addresses, financial figures). No personal PII fields identified. Customer names appear to be corporate entities (S.A. de C.V. format), addresses are legal registration locations, and financial columns show invoice balances. This aligns with the breach context of Megacable's ERP data containing supplier and business customer records.
TB_FORMATOS_PROY.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal business identifiers, financial metrics, and project metadata. No PII fields detected. Columns include project IDs, descriptions, financial figures, dates (non-DOB), status codes, and internal reference numbers. None map to email, phone, name, address, DOB, SSN, password, username, country, gender, suffix, or facebookId.
TB_FORMATOS_PROY_SERV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected in the first 50 rows. The data contains only service codes, descriptions, quantities, and pricing — typical business transactional records without personal identifiers.
TB_ICARE_CC_SEGUIMIENTO.csv0 rows
TB_ICARE_IMPORTANCIA_CLIENTE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII fields detected in the provided data. The columns appear to contain only numeric identifiers (N_ID_CLIENTE), monetary values (N_FACTURACION), and color codes (S_COLOR). There are no names, addresses, emails, phone numbers, dates of birth, SSNs, passwords, usernames, or other PII categories present in the visible data.
TB_ICARE_LISTA_BLANCA.csv0 rows
File structure
Notes: The file appears to be a simple list of numeric country codes with no structured columns or PII. There is no delimiter or consistent row structure, and the content is purely numeric identifiers. This is not a CSV or any structured format with columns to map.
TB_ICARE_MENSAJE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file is a README or description of ticket statuses, not structured customer data. It contains no PII fields. All rows are free-form messages about ticket states, not delimited records of personal information. No columns map to PII fields.
TB_ICARE_MENSAJE_CFG.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file but contains only internal system codes and types (N_ID_MENSAJE, N_ID, S_TIPODATO). No PII fields are present. All columns represent internal identifiers and data types, which are not personal information. Therefore, no columns map to PII fields.
TB_ICARE_TICKET.csv28,481 rows
File structure
Notes: Pre-LLM auto-detection: free-form text with visible emails / phones
TB_ICARE_TICKET_CAUSAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only two columns: N_ID_TICKET and N_ID_CAUSA, both of which are internal numeric identifiers. No PII fields are present.
TB_ICARE_TICKET_CLIENTES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only two columns: N_ID_TICKET and N_ID_CLIENTE, both appear to be internal numeric identifiers (ticket IDs and client IDs). There are no personal identifiable information (PII) fields present. All columns are marked as skip per the exclusion rules for internal IDs.
TB_ICARE_TICKET_CLIENTES_SERV.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal IDs (N_ID_TICKET, N_ID_CLIENTE, N_ID_ENUM_SERVICIOS) and a timestamp (D_FH_RESTABLECIMIENTO). These match the exclusion rules for internal IDs and timestamps. The data represents ticket/service restoration records with no personal identifiable information exposed.
TB_ICARE_TICKET_HIST.csv1 column0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 3 | fullName | high | [3] values are human names in ticket notes (e.g., "David", "Erika Sánchez"). Header "N_ID_PERSONAL" suggests internal user ID linking to names. |
Notes: Only column 3 contains PII (fullName) inferred from values in free-text notes. All other columns are internal ticket IDs, timestamps, and event types (non-PII).
TB_ICARE_TICKET_LISTA_BLANCA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns identified. All visible columns appear to be internal IDs, codes, and timestamps. Values are numeric codes, timestamps, and flags with no personal identifiers (names, emails, addresses, etc.).
TB_ICARE_TICKET_OUT.csv0 rows
TB_IPS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No PII fields detected. The data appears to be purely technical/network infrastructure records (IDs, IP addresses, bandwidth values). No emails, names, addresses, phone numbers, or other PII patterns present in the first 50 rows.
TB_IREAD_COPIA_PEDIDOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to be internal identifiers, timestamps, and transaction codes. Values contain only numeric IDs, dates/times, and status codes with no personal information.
TB_MKT_CARRIERS_LD.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns represent internal telecommunications carrier codes, routing indices, and operational flags. No PII fields (names, addresses, emails, etc.) are present. These are system identifiers, network configuration codes, and activation flags for international/national routing — typical of an Oracle E-Business Suite telecommunications database leak.
TB_MKT_HORARIO_REGION.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a structured table of internal identifiers (N_ID_REGION, N_ID_HORARIO) with no personal data. All values are numeric codes representing regions and schedules, consistent with internal business data from Megacable's ERP system.
TB_MKT_NPA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: This is a list of NPA (Numbering Plan Area) codes and countries, not a dataset with personal identifiable information (PII). There are no columns mapping to PII fields as this appears to be a reference table for telecommunication numbering plans rather than a breach containing user data. All entries are country names paired with numeric codes.
TB_MKT_REGION_NPA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with three columns: N_NPA, N_ID_REGION, and D_FECHA_INICIO. The column names and values indicate this is purely internal network/region configuration data with date stamps. No PII fields are present - all columns are internal identifiers and timestamps. The values represent NPA (Number Planning Area) codes, region IDs, and fixed start dates (all rows show 2002-01-01 or 2002-02-01). There are no emails, names, addresses, or other personal data in this dataset.
TB_MKT_RPT_LCR_COMPARATIVO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal routing / billing codes, carrier identifiers, cost metrics, and region codes. No PII present. Values are numeric codes, carrier names (Avantel, Phonet), cost figures, and technical region labels. None map to any PII field categories.
TB_MKT_RPT_LCR_COMPARATIVO_PRA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain network routing and carrier cost data (INI, FIN, DESTINO, OPERADOR, REGION, COSTO). No personal identifiable information (PII) fields present. Values represent telecommunication route IDs, carrier names, regions, and pricing — all internal business data. No emails, phone numbers, names, addresses, or other PII detected in the sample.
TB_MKT_SERIES_DETALLE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected. All columns appear to be internal identifiers, numeric ranges, and timestamps. No personal identifiable information (names, addresses, emails, phone numbers, etc.) present in the first 50 rows.
TB_MOVTOS_SERVICIOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: The file appears to be a series of log entries or transaction records with no headers. All columns contain only numeric IDs, timestamps, and status codes — no PII fields (names, emails, addresses, etc.) are present. This is typical of internal system logs or database keys, not user data. Therefore, no PII columns can be mapped.
TB_NPAXREGION.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal identifiers (N_ID_NPA, ID_REGION, N_ID_PLAN_TARIFARIO, N_ID_SERIE) and numeric codes. This aligns with the breach context of Megacable's internal business data (supplier records, financials, network routing) rather than customer PII.
TB_NPAXX.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured table of NPA (Numbering Plan Area) codes with geographic descriptors. No PII is present. Columns are: N_ID_NPA (numeric identifier), S_CIUDAD (city name), S_LOCALIZACION (location descriptor), N_CODIGO_PAIS (country code), S_PAIS (country name). All values are geographic entities, not personal data.
TB_OT_DIRECCION_IP.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain network configuration data (IP addresses, subnets, ports, equipment identifiers, timestamps) with no personal identifiable information (PII). This is infrastructure data from an Oracle E-Business Suite deployment, not customer records.
TB_OT_ETAPAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only internal operational IDs and timestamps with no PII. The columns are N_ID_OT (internal transaction ID), N_ID_ENUM (enumeration code), N_ESTATUS (status flag), D_FH_MODIFICACION (modification timestamp), S_DESCRIPCION (free-text description), D_FH_CREACION (creation timestamp). All values are numeric IDs or timestamps with no personal data.
TB_OT_OT.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal business identifiers, timestamps, and status flags. No PII fields detected. Columns like N_ID_CLIENTE, N_ID_PM are internal customer/service IDs, D_FECHA_INI/D_FECHA_FIN are dates, S_ULT_MODIF contains migration notes, and other fields are numeric codes or status indicators. No email, phone, name, address, DOB, SSN, or password values present.
TB_OT_PUNTAS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers or business reference codes (N_ID_OT, N_ID_PUNTA_A, N_ID_PUNTA_B, S_PISO_PUNTA_A, S_PISO_PUNTA_B, N_ID_ENUM_CARRIER, S_CID, D_ACTIVACION, N_CAPACIDAD, N_ID_ENUM_UMEDIDA, N_ID_ENUM_INTERFACE, S_SALESFORCE_PUNTA_A, S_SALESFORCE_PUNTA_B). No personal PII fields are present. The Salesforce IDs are system-generated identifiers, not usernames or user identifiers.
TB_PERMISOS_CONTACTOS.csv3 columns0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | skip | high | column contains numeric codes, no PII pattern |
| 1 | skip | high | column contains numeric codes, no PII pattern |
| 2 | skip | high | column contains only 11111111111 or 00000000000, no PII pattern |
Notes: File contains only numeric codes with no identifiable PII. All columns represent internal reference numbers or flags rather than personal data. The consistent pattern of 11111111111 and 00000000000 suggests system-generated identifiers rather than actual PII.
TB_PLANES_TARIFARIOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file containing internal business data (tariff plans, dates, types) with no PII fields. All columns are internal identifiers, plan descriptions, date ranges, and type codes. No columns map to PII fields per the exclusion rules (company/business-related data, internal IDs, timestamps).
TB_PLAN_NUMERACION.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns identified. All columns appear to contain internal network/telecom identifiers, geographic codes, dates of service activation/consolidation, and operational status codes typical of a telecom provider's infrastructure database. No personal identifiers (names, emails, phone numbers, addresses, etc.) are present in the sample data.
TB_REGIONES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only region codes, descriptions, and type flags. No PII fields are present. All columns are internal business data (region identifiers, descriptions, and flags) and should be skipped per exclusion rules.
TB_RPTCDRS_CERO_MET.csv0 rows
TB_RPTCDRS_X_DESTINO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns represent internal system identifiers, routing codes, timestamps, and traffic counters. No PII fields (names, addresses, emails, phones, DOB, SSN, etc.) are present. Columns like A_PARTY_NUMBER and B_PARTY_NUMBER are internal numeric identifiers, not personal phone numbers or account IDs. DISCONNECT_REASON, FAILURE_CODE, ROUTE fields, and DATE_TIME stamps are system operational data. No actionable PII to map.
TB_RPT_MSG_TIPO_CUENTA_CC.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain purely transactional and internal business data (dates, numeric IDs, amounts, message counts). No PII fields present. Columns map to internal accounting/operational metrics, not personal identifiers.
TB_RPT_TRAFICO_X_TIPO_CUENTA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The file contains only transactional data with columns for date (D_FECHA), account type (S_TIPO_CUENTA), monetary amount (N_IMPORTE), and minutes (N_MINUTOS). No PII fields are present. This appears to be billing or usage records from Megacable Comunicaciones de Mexico, likely from an Oracle E-Business Suite installation as mentioned in the breach context.
TB_SALIDA_TARGET_55.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only three columns: MINUTOS (a numeric timestamp), N_NIR_CIUDAD (a numeric code), and DIA (a date). None of these columns contain PII. The date column represents dates but does not constitute a DOB field as it lacks personal identifiers. No email, phone, name, address, or other PII fields are present.
TB_SERIES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII fields detected. All columns appear to be internal business identifiers, range codes, dates, status flags, and comments referencing companies/organizations rather than individuals. No emails, phone numbers, names, addresses, or other personal data present in the first 50 rows.
TB_SERIES_CTA.csv2 columns915 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 2 | phone | high | [2] all values are 10-digit Mexican phone numbers |
| 3 | phone | high | [3] duplicate of column 2, also 10-digit Mexican phone numbers |
Notes: File contains only year and two identical phone number columns. No other PII fields present. All values appear to be Mexican landline or mobile numbers in standard 10-digit format.
TB_SERIES_LD.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII fields detected. The file contains only network numbering ranges (ID_REGION, N_NUMERO_INICIAL, N_NUMERO_FINAL), city names (S_CIUDAD), and tariff/series identifiers (N_ID_PLAN_TARIFARIO, N_ID_SERIE, N_SERIE_800). These are internal telecommunications routing codes and geographic descriptors, not personal data. All values are location names in standard Mexican town formatting or numeric ranges.
TB_SERVICIOS_ESPECIALES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains service codes and descriptions for a telecommunications provider. No PII fields are present. All columns are service codes, descriptions, call types, and billing flags — no personal data such as names, addresses, emails, or phone numbers.
TB_SERVICIO_CUENTA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All columns appear to contain internal business identifiers, codes, flags, and numeric counters consistent with ERP financial/tax data and network routing tables. No names, emails, addresses, phones, DOB, or SSNs present in sample.
TB_SMS_TOTALES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file contains only business/financial data (SMS counts, account IDs, tariffs, cut-off dates). No personal identifiers or PII fields are present. All columns are internal business metrics and account identifiers, which per exclusion rules must be skipped.
TB_SW_OFFSUM_1.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, dates, and numeric counters related to call detail records (CDR) and billing systems. No PII fields detected.
TB_SW_OFFSUM_7.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal system identifiers, timestamps, counters, and flags with no PII. No email, phone, name, address, DOB, SSN, gender, or other PII fields are present. This is purely operational data from an ERP/CDR system.
TB_SW_PRA_B.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal system identifiers, timestamps, and call detail record counters (TELE_*) with no PII content. Values are numeric IDs, dates, and zero-count usage/seizure/attempt metrics. No emails, names, addresses, phones, DOB, SSN, or passwords detected in the sample.
TB_SW_SL24.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal identifiers, dates, numeric counters, and flags with no PII content. No email, phone, name, address, DOB, SSN, password, or username fields detected. The values are system-generated IDs, dates, and zero/numeric constants typical of internal operational records.
TB_SW_TGCOMP_ERR.csv0 rows
TB_SW_TRAFFLOW_3.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal usage/attempt counters and date/time stamps related to network or program intervals. No PII fields detected.
TB_TARIFAS_CUENTA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be internal business identifiers (N_ID_TARIFA, N_ID_CUENTA, N_ID_REGION, S_TIPO_LD) with no PII detected. Values are numeric codes and flags, consistent with internal system IDs and not personal data. No emails, phone numbers, names, addresses, or other PII fields are present in the sample.
TB_TARIFAS_OK.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. This appears to be a pricing/volume table with three columns: N_ID_VOLUMEN (volume ID), N_ID_TARIFA (tariff ID), and N_MONTO (amount). All values are numeric and represent business/financial data, not personal information. No emails, names, addresses, or other PII present.
TB_TARIFAS_TELEFONIA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. All fields appear to be internal business identifiers, numeric codes, traffic types, client types, tariff references, and timestamps. No personal information such as names, emails, phone numbers, addresses, or dates of birth is present in the sample.
TB_TARIFAS_VOLVOX.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No PII columns detected. This appears to be purely transactional/financial data with internal IDs, amounts, timestamps, and static customer code 'SDOMINGUEZ'. All columns are business/system identifiers or financial metrics, no personal identifiers present.
TB_TFAS_CTA_INT.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: no·Quote: "
Notes: No PII columns identified. All visible columns appear to be numeric IDs, numeric values, and static codes (e.g., DBAMEX, USRSSO) typical of internal business records. No names, emails, addresses, or other personal data visible in the sample.
TB_TIPO_CAMBIO_TMP.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be purely transactional/financial data (dates, numeric values, status flags). No PII fields detected. This aligns with the breach context of internal business data rather than customer PII.
TB_TOP_ACCOUNT_SKYPE.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII columns detected. The file contains only network region identifiers (LDN-CEL), dates, numeric minute counts, and a constant value (55.000). No names, addresses, emails, phone numbers, or other PII appear in the sample.
TB_TOP_ACC_CLIENTES.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns appear to be business/operational data: client names are company/organization names (S_CLIENTE), dates are transaction dates (D_FECHA), numeric codes and pricing (N_NO_E1S, N_PRECIO), billing types (S_TIPO_COBRO), city codes (S_CIUDAD), client types (S_TIPO_CLIENTE), activation flags (N_B_ACTIVO), and order identifiers (S_NOMBRE_ORDEN_ALFA). No personal PII fields (names, emails, addresses, etc.) are present. Per exclusion rules, company/client names and business identifiers are skipped.
TB_TRAFICO_ENTRADA.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business/operational data (account IDs, call types, dates, operators, service codes, status flags). No PII fields present. Values are numeric identifiers, service codes, operator names (company names), call metrics, and status codes — none correspond to email, phone, name, address, DOB, SSN, gender, suffix, or username. Per exclusion rules, columns with 'Company' or 'Business' in name are skipped; all columns here fall into internal IDs or business operational data categories.
TB_TRAFICO_LD_PASO.csv0 rows
TB_TRAFICO_LOCAL.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal identifiers, timestamps, call routing codes, or internal system fields with no PII content. No email, phone, names, addresses, DOB, SSN, or passwords are present. Columns like A_PARTY_NUMBER and B_PARTY_NUMBER contain numeric identifiers that do not map to any PII field type.
TB_TRAFICO_LOCAL_PASO.csv0 rows
TB_VACACIONES.csv468 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
TB_VM_CONTACTOS.csv2 columns13,342 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 6 | phone | high | [6] header 'S_TELEFONO_1', values are 10-digit numbers |
| 7 | phone | high | [7] header 'S_TELEFONO_2', values are 10-digit numbers |
Notes: Only columns 6 and 7 contain PII (phone numbers). All other columns are internal IDs, company names, roles, or status flags and are skipped per rules. No emails, names, addresses, DOB, SSN, etc. are present.
TB_VM_VENTANAS.csv7,322 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
TB_VM_VENTANAS_1.csv7,322 rows
File structure
Notes: Unstructured fallback: no PII columns mapped, but the raw text carries emails
TB_VOLUMEN_TRAFICO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This file appears to be purely transactional/financial data (volume ranges, N_ID_VOLUMEN). All columns represent internal business metrics (volume IDs, start/end ranges) with no personal identifiers. No PII fields detected.
TIPOS_CATALOGO.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: This is a structured CSV file with technical call status codes and descriptions from a telecom system. No PII fields (email, phone, names, addresses, etc.) are present. All columns contain internal system codes, status codes, and textual descriptions of call failures, network statuses, and service types. No columns map to any PII categories.
TIPO_CAMBIO_DEPURAR.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The file contains only two columns: exchange rate values and corresponding dates. No PII fields are present. Columns map to financial transactional data (exchange rates) and timestamps (non-DOB), both excluded by rules.
TIPO_CAMBIO_FACTURACION.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: File contains only two columns: N_TIPO_CAMBIO (exchange rate values) and FECHA (dates). No PII fields detected. Values appear to be financial exchange rate data with dates, typical of currency conversion logs. No names, addresses, emails, phones, or other PII present.
T_PERMISOS.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: No PII detected. File contains only system menu options and permission mappings (N_ID_PERFIL, N_ID_APLICACION, etc.). Values are numeric codes and static menu labels with no personal identifiers.
T_SEGURIDAD.csv2 columns3,401 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 4 | username | high | [4] header 'S_LOGIN', values are alphanumeric usernames |
| 5 | password | high | [5] header 'S_PASSWORD', values appear to be empty or hashed credentials |
Notes: CSV file with 5 columns. Columns 0-3 (N_ID_USUARIO, N_ID_PERSONAL, N_ID_APLICACION, N_ID_PERFIL) are internal IDs and skipped. Columns 4-5 contain username and password fields respectively.
VW_ANTIGUEDAD_SALDOS.csv1 column5,985 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
| Source column | Mapped field | Confidence | LLM assessment |
|---|---|---|---|
| 0 | fullName | high | [0] values appear to be company or organization names, not individual names. These are business entities, not PII for individuals. |
Notes: This file appears to be an accounting or financial ledger containing business-to-business transaction data. The first column contains business/organization names rather than individual PII. Other columns contain invoice numbers, monetary amounts, and accounting codes — all non-PII business data. No valid personal PII fields (email, phone, name, etc.) are present in this sample.
ZX_FORMULA_B_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns contain purely internal business/tax configuration data (tax codes, formula types, flags, timestamps, IDs). No PII fields detected. Columns match exclusion rules: internal IDs (FORMULA_ID, CONTENT_OWNER_ID, CREATED_BY, LAST_UPDATED_BY), timestamps (CREATION_DATE, LAST_UPDATE_DATE), flags (ENABLED_FLAG, CASH_DISCOUNT_APPL_FLAG, etc.), and tax-related codes. No emails, phones, names, addresses, DOB, SSN, or passwords present.
ZX_FORMULA_DETAILS_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business identifiers, timestamps, flags, or compound tax codes. No PII fields are present. Columns such as CREATION_DATE and LAST_UPDATE_DATE are timestamps (not DOB), PROGRAM_LOGIN_ID and OBJECT_VERSION_NUMBER are internal IDs, and all others are tax regimes, attribute codes, and formula identifiers. No emails, names, addresses, phone numbers, DOB, SSN, passwords, usernames, or other PII categories are found.
ZX_ID_TCC_MAPPING_ALL_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are internal business/tax identifiers, timestamps, and flags. No PII present. Columns match exclusion rules: TCC_MAPPING_ID (internal ID), ORG_ID (internal ID), TAX_CLASS/TAX_RATE_CODE_ID/TAX_CLASSIFICATION_CODE (tax codes), CREATED_BY/LAST_UPDATED_BY/LAST_UPDATE_LOGIN/PROGRAM_APPLICATION_ID/PROGRAM_ID/PROGRAM_LOGIN_ID (system users/operations), REQUEST_ID (transaction ID), EFFECTIVE_FROM/EFFECTIVE_TO (date ranges), TAX_TYPE (tax category), SOURCE (module source), LEDGER_ID (accounting ledger), ACTIVE_FLAG (status). No emails, names, addresses, phones, DOB, SSN, passwords, usernames, or gender data present.
ZX_RATES_B_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: All columns are business/tax/ERP metadata (tax codes, effective dates, flags, internal IDs). No PII fields present. All columns match exclusion rules: TAX_RATE_CODE, EFFECTIVE_FROM, EFFECTIVE_TO, TAX_REGIME_CODE, TAX, TAX_STATUS_CODE, SCHEDULE_BASED_RATE_FLAG, RATE_TYPE_CODE, PERCENTAGE_RATE, QUANTITY_RATE, UOM_CODE, TAX_JURISDICTION_CODE, RECOVERY_TYPE_CODE, ACTIVE_FLAG, DEFAULT_RATE_FLAG, DEFAULT_FLG_EFFECTIVE_FROM, DEFAULT_FLG_EFFECTIVE_TO, DEFAULT_REC_TYPE_CODE, DEFAULT_REC_RATE_CODE, OFFSET_TAX, OFFSET_STATUS_CODE, OFFSET_TAX_RATE_CODE, RECOVERY_RULE_CODE, DEF_REC_SETTLEMENT_OPTION_CODE, VAT_TRANSACTION_TYPE_CODE, RECORD_TYPE_CODE, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, ATTRIBUTE1-15, ATTRIBUTE_CATEGORY, PROGRAM_LOGIN_ID, TAX_RATE_ID, CONTENT_OWNER_ID, ADJ_FOR_ADHOC_AMT_CODE, ALLOW_ADHOC_TAX_RATE_FLAG, TAX_CLASS, SOURCE_ID, TAXABLE_BASIS_FORMULA_CODE, INCLUSIVE_TAX_FLAG, TAX_INCLUSIVE_OVERRIDE_FLAG, ALLOW_EXEMPTIONS_FLAG, ALLOW_EXCEPTIONS_FLAG, OBJECT_VERSION_NUMBER — none contain personal identifiers.
ZX_TAXES_B_MVIEW.csv0 rows
File structure
Format: CSV·Delimiter: Comma·Has header: yes·Quote: "
Notes: The provided data contains only tax configuration parameters and system metadata (flags, codes, thresholds, timestamps). No columns contain PII fields such as names, email addresses, phone numbers, dates of birth, SSNs, passwords, or usernames. All columns represent internal business logic for tax calculations, system tracking, and configuration settings.