Skip to main content

SYSPRO Customization

Overview

This document describes the custom SYSPRO components created for the MiniMrpOrderCreation dashboard, including custom tables, views, forms, and SQL scripts.

Custom Database Objects

CG_InventoryOrdering_View

Purpose: Calculate MRP requirements based on safety stock and minimum quantities.

Key Features:

  • Combines data from multiple tables
  • Calculates reorder quantities
  • Considers allocations and WIP
  • Handles both safety stock and minimum quantity methods

CG_v_SalesOrderJobDemand

Purpose: Show demand from sales orders and jobs.

Key Features:

  • Aggregates demand by type
  • Shows allocations by warehouse
  • Includes customer information
  • Tracks due dates

Custom Forms (CustomForms.xml)

Configuration

XML-based form definitions for:

  • Extended purchase order entry
  • MRP calculation display
  • Supplier selection dialogs

Integration Points

  • Hooks into standard SYSPRO programs
  • Adds custom fields and validations
  • Implements business-specific logic

SQL Script Management

DatabaseValidation.json

Configuration file defining:

  • Required database objects
  • Version checking
  • Update scripts
  • Validation rules

Script Deployment Pattern

  1. Check if object exists
  2. Compare version/structure
  3. Apply update if needed
  4. Log changes for audit

Custom Field Handling

Adding Custom Fields

  • Use SYSPRO's custom form designer
  • Map to database columns
  • Implement validation rules
  • Handle in business objects

Data Types

  • Support for all SYSPRO data types
  • Custom formatting rules
  • Validation patterns
  • Default value handling

Testing Strategies

Database Object Testing

  • Verify view performance
  • Test calculation accuracy
  • Validate data integrity
  • Check index usage

Integration Testing

  • Test with SYSPRO test environment
  • Validate business object responses
  • Verify custom form behavior
  • Check data flow end-to-end

Deployment Considerations

Version Management

  • Track custom object versions
  • Maintain upgrade scripts
  • Document dependencies
  • Test rollback procedures

Environment Promotion

  • Development → Test → Production
  • Script validation at each stage
  • Data migration considerations
  • Rollback planning

Best Practices

  • Prefix custom objects with 'CG_'
  • Document all customizations
  • Version control SQL scripts
  • Test in isolated environment
  • Maintain backward compatibility