Skip to main content

SYSPRO Data Models

Overview​

The EFT Remittance Dashboard interacts with various SYSPRO data models, including standard SYSPRO tables and custom extensions. This document details the data model architecture, relationships, and constraints that govern the dashboard's data layer.

Key Concepts​

  • SYSPRO Standard Tables: Core ERP tables (ApSupplier, ApTrans, etc.)
  • Custom Tables: Application-specific extensions (MepAppsApEftRemittanceAudit)
  • Views and Stored Procedures: Custom database objects for reporting
  • Entity Mappings: Entity Framework configurations for SYSPRO tables
  • Data Integrity: Constraints and relationships

SYSPRO Standard Tables​

ApSupplier Table​

Stores supplier master data:

  • Supplier: Primary key (15 chars)
  • SupplierName: Supplier description
  • Email: Remittance email address
  • Currency: Transaction currency
  • OnHold: Credit hold status

ApTrans Table​

Accounts payable transactions:

  • Supplier: Foreign key to ApSupplier
  • Invoice: Unique invoice identifier
  • TransactionType: I=Invoice, C=Credit, P=Payment
  • TransactionDate: Transaction posting date
  • GrossAmount: Original invoice amount

ApRemit View​

Custom view for remittance processing combining multiple tables.

Custom Data Models​

MepAppsApEftRemittanceAudit​

Audit trail for remittance activities with fields for tracking user actions, timestamps, and email details.

Entity Framework Mappings​

The PluginSysproDataContext configures Entity Framework to work with SYSPRO's database structure, including proper key configurations, relationships, and SYSPRO-specific conventions.

Best Practices​

  1. Always respect SYSPRO field constraints
  2. Use appropriate data types for SYSPRO compatibility
  3. Maintain referential integrity
  4. Follow SYSPRO naming conventions

Summary​

The data model layer provides a robust foundation for the EFT Remittance Dashboard, bridging SYSPRO's standard tables with custom extensions while maintaining data integrity and performance.