This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
setting_up_a_new_contract [2025/01/27 20:41] – tina.robles | setting_up_a_new_contract [2025/06/18 18:11] (current) – tina.robles | ||
---|---|---|---|
Line 1278: | Line 1278: | ||
This action moves the contract into the formal review and approval workflow. | This action moves the contract into the formal review and approval workflow. | ||
----- | ----- | ||
+ | |||
+ | **__Excel Offline Pricing Upload Capability in Contracts__** | ||
+ | |||
+ | This highly requested enhancement enables users to update contract data through Excel spreadsheets and import the information directly into contracts, significantly streamlining the creation process for large-scale contract configurations. | ||
+ | ________________________________________ | ||
+ | |||
+ | **Prerequisites and System Requirements** | ||
+ | |||
+ | __Contract Status Requirements: | ||
+ | |||
+ | * Contract must be in draft status | ||
+ | * Contract type field must be completed | ||
+ | * Minimum of one SKU must exist on the product tab | ||
+ | |||
+ | __Recommended Setup Process:__ | ||
+ | |||
+ | * Contractee Selection Priority: Complete contractee selection before Excel configuration to ensure appropriate pricing column availability | ||
+ | * Pricing Structure Optimization: | ||
+ | ________________________________________ | ||
+ | |||
+ | **Product Management Capabilities** | ||
+ | |||
+ | __SKU Addition Process:__ | ||
+ | |||
+ | * Method: Add products directly within Excel document | ||
+ | * Identifier Requirement: | ||
+ | * Automatic Population: Product descriptions auto-populate upon successful Excel upload | ||
+ | |||
+ | **Critical Configuration Requirements: | ||
+ | |||
+ | __Item Type Specification: | ||
+ | |||
+ | * Mandatory Field: Item type must be completed for all new SKUs | ||
+ | * Upload Dependency: Products without item type designation will not process during upload | ||
+ | |||
+ | __Leading Zero Preservation: | ||
+ | |||
+ | * Issue: Excel automatically removes leading zeros from product numbers | ||
+ | * Solution: Prefix product numbers beginning with zero using single quote notation | ||
+ | * Example: Format ' | ||
+ | ________________________________________ | ||
+ | |||
+ | **Data Management and Updates** | ||
+ | |||
+ | __Field Modification Scope:__ | ||
+ | |||
+ | * Capability: All UI-editable contract fields can be updated through Excel | ||
+ | * Consistency: | ||
+ | * Flexibility: | ||
+ | |||
+ | **Export and Import Process:** | ||
+ | |||
+ | __Offline Pricing Feature Access:__ | ||
+ | |||
+ | * Location: Product tab interface | ||
+ | * Function: " | ||
+ | |||
+ | __Product Selection Methods:__ | ||
+ | |||
+ | * Individual Selection: Choose specific products for export and update | ||
+ | * Bulk Selection: Utilize "Check All" function for comprehensive product selection | ||
+ | * Workflow: Select desired products, then activate offline pricing feature | ||
+ | ________________________________________ | ||
+ | |||
+ | **Business Benefits** | ||
+ | |||
+ | __Efficiency Enhancement: | ||
+ | |||
+ | * Streamlined contract creation for complex, multi-product agreements | ||
+ | * Reduced manual data entry requirements | ||
+ | * Improved accuracy through spreadsheet-based data management | ||
+ | |||
+ | __Scalability: | ||
+ | |||
+ | * Optimized for large contract configurations | ||
+ | * Bulk product management capabilities | ||
+ | * Enhanced productivity for contract administrators | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **Excel Import/ | ||
+ | |||
+ | **__Available Operations__** | ||
+ | |||
+ | **Export Products** | ||
+ | |||
+ | * Purpose: Extracts current contract product data to Excel format for external modification | ||
+ | * Application: | ||
+ | * Workflow Position: Initial step in the offline editing process | ||
+ | |||
+ | **Import Products** | ||
+ | |||
+ | * Purpose: Integrates updated Excel data back into the contract system | ||
+ | * Application: | ||
+ | * Workflow Position: Concluding step following Excel-based data updates | ||
+ | |||
+ | __**Process Workflow**__ | ||
+ | |||
+ | **Step 1: Data Extraction** | ||
+ | |||
+ | * Utilize " | ||
+ | * Review and modify data using standard Excel functionality | ||
+ | |||
+ | **Step 2: Data Integration** | ||
+ | |||
+ | * Execute " | ||
+ | * System validates and applies approved modifications to contract configuration | ||
+ | |||
+ | {{: | ||
+ | |||
+ | __**Export Process Workflow**__ | ||
+ | |||
+ | **Data Export Procedure** | ||
+ | |||
+ | **Step 1: Export Initiation** | ||
+ | * Action: Select " | ||
+ | * Display: System presents information corresponding to previously selected product lines | ||
+ | * Verification: | ||
+ | |||
+ | **Step 2: Report Generation** | ||
+ | * Action: Click " | ||
+ | * Function: System compiles selected product data into Excel-compatible format | ||
+ | * Output: Creates downloadable spreadsheet containing specified contract product information | ||
+ | |||
+ | **Process Benefits:** | ||
+ | * Data Validation: Preview functionality ensures correct product selection before export | ||
+ | * Efficiency: Streamlined two-step process minimizes user interaction requirements | ||
+ | * Accuracy: Confirmation step reduces risk of exporting incorrect data sets | ||
+ | |||
+ | {{: | ||
+ | |||
+ | __**Report Access and File Retrieval Process**__ | ||
+ | |||
+ | **Generated Report Management** | ||
+ | |||
+ | **Step 1: Report Completion Verification** | ||
+ | * Location: Navigate to " | ||
+ | * Status: Completed export appears in the reports queue upon successful processing | ||
+ | * Identification: | ||
+ | |||
+ | **Step 2: File Download and Access** | ||
+ | * Action: Click on the designated report name to initiate download | ||
+ | * File Location: Excel document automatically saves to system' | ||
+ | * File Format: Spreadsheet contains exported product data in Excel-compatible format ready for modification | ||
+ | |||
+ | **File Management Best Practices** | ||
+ | |||
+ | **Organization Recommendations: | ||
+ | * File Naming: Consider renaming downloaded files with descriptive identifiers | ||
+ | * Version Control: Maintain clear file versioning for tracking modifications | ||
+ | * Storage: Organize files in dedicated project folders for efficient management | ||
+ | |||
+ | **Next Steps:** Upon successful download, the Excel file is ready for offline editing and subsequent import back into the contract system using the Import Products functionality. | ||
+ | This systematic approach ensures seamless file retrieval and establishes the foundation for efficient offline contract data management. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | __**Excel Document Configuration and Editing Guidelines**__ | ||
+ | |||
+ | **Document Security and Access** | ||
+ | |||
+ | **Protected View Resolution** | ||
+ | * Security Feature: Excel may open documents in Protected View as a security precaution | ||
+ | * Action Required: Click " | ||
+ | * Purpose: Ensures document functionality while maintaining system security protocols | ||
+ | |||
+ | **Document Structure and Interface** | ||
+ | |||
+ | **Visual Consistency** | ||
+ | * Layout Design: Excel document mirrors the user interface screen layout for intuitive navigation | ||
+ | * Column Organization: | ||
+ | * Color Coding: Preserves original color scheme for visual consistency and user familiarity | ||
+ | |||
+ | **Editing Permissions** | ||
+ | * Editable Fields: Standard white/ | ||
+ | * Protected Fields: Grey-highlighted columns are read-only and cannot be modified | ||
+ | * Data Integrity: Protection scheme ensures critical system data remains unchanged | ||
+ | |||
+ | **Data Validation and Controls** | ||
+ | |||
+ | **Dropdown Functionality** | ||
+ | * Controlled Fields: Fields with specific value requirements display as dropdown menus | ||
+ | * Example Application: | ||
+ | * Data Accuracy: Dropdown controls prevent invalid data entry and ensure compliance with system parameters | ||
+ | * Configuration Dependency: Available options reflect current manufacturer-specific settings and business rules | ||
+ | |||
+ | **Business Benefits** | ||
+ | |||
+ | **User Experience: | ||
+ | * Familiar interface reduces learning curve and training requirements | ||
+ | * Visual cues guide proper data entry and modification procedures | ||
+ | * Automated validation prevents common data entry errors | ||
+ | |||
+ | **System Integration: | ||
+ | * Maintains data consistency between offline editing and system database | ||
+ | * Preserves business rules and validation requirements during external editing process | ||
+ | |||
+ | {{: | ||
+ | |||
+ | __**Field Editing Restrictions and System Validation**__ | ||
+ | |||
+ | **Data Protection Mechanisms** | ||
+ | |||
+ | **Edit Restriction Warnings** | ||
+ | * System Response: Attempting to modify protected fields triggers Excel validation warnings | ||
+ | * Example Scenario: Item price fields may display restriction notifications when modification is attempted | ||
+ | * Purpose: Prevents unauthorized changes to system-controlled data elements | ||
+ | |||
+ | **Consistency Protocol** | ||
+ | |||
+ | **UI-Excel Parity Rule** | ||
+ | * Fundamental Principle: Field editing permissions maintain complete consistency between contract user interface and Excel document | ||
+ | * Access Control: Fields that are non-editable within the contract management system remain protected in the Excel environment | ||
+ | * Business Logic: Editing restrictions reflect underlying business rules and data integrity requirements | ||
+ | |||
+ | **User Guidance** | ||
+ | |||
+ | **Error Prevention: | ||
+ | * Proactive Notification: | ||
+ | * Workflow Efficiency: Clear restriction indicators prevent wasted effort on non-modifiable fields | ||
+ | * System Integrity: Protection mechanisms ensure data consistency across all editing platforms | ||
+ | |||
+ | **Best Practice:** Before attempting modifications, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **__Data Import Process and System Integration__** | ||
+ | |||
+ | **File Preparation and Save Protocol** | ||
+ | |||
+ | **Document Completion** | ||
+ | * Action: Save updated Excel document upon completion of all modifications | ||
+ | * Critical Requirement: | ||
+ | * File Integrity: Preserving filename ensures proper system recognition and processing | ||
+ | |||
+ | **Import Procedure** | ||
+ | |||
+ | **Step 1: Import Function Access** | ||
+ | * Navigation: Access " | ||
+ | * Selection: Choose " | ||
+ | * File Location: Browse and select the saved Excel document from designated storage location | ||
+ | |||
+ | **Step 2: Upload and Integration** | ||
+ | * File Upload: System processes the selected Excel document | ||
+ | * Validation: Click " | ||
+ | * System Integration: | ||
+ | |||
+ | **Critical Success Factors** | ||
+ | |||
+ | **Filename Preservation: | ||
+ | * Requirement: | ||
+ | * System Recognition: | ||
+ | * Error Prevention: Filename modifications may result in import failures or data misalignment | ||
+ | |||
+ | **Process Verification: | ||
+ | * Quality Assurance: Review imported data within TPM system to confirm accurate integration | ||
+ | * Data Validation: Verify all modifications have been properly applied to contract configuration | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **__Data Validation and Error Handling Protocol__** | ||
+ | |||
+ | **Import Validation Process** | ||
+ | |||
+ | **Data Quality Assessment** | ||
+ | * Validation Screen: System displays comprehensive data validation results upon import initiation | ||
+ | * Error Identification: | ||
+ | * Quality Assurance: Automated validation ensures data integrity before system integration | ||
+ | |||
+ | **Error Management and Resolution** | ||
+ | |||
+ | **Invalid Product Number Handling** | ||
+ | * System Response: Product numbers not found in TPM database are automatically excluded from import process | ||
+ | * Row Processing: Invalid entries are skipped while valid data continues through normal import workflow | ||
+ | * Error Documentation: | ||
+ | |||
+ | **Data Processing Logic** | ||
+ | * Selective Import: Only validated, system-recognized data is integrated into the contract | ||
+ | * Error Isolation: Invalid entries do not compromise the import of valid data elements | ||
+ | * Process Continuity: Import process continues despite individual row validation failures | ||
+ | |||
+ | **'' | ||
+ | |||
+ | **Pre-Import Verification: | ||
+ | * Product Number Validation: Verify all product numbers exist in TPM system before import | ||
+ | * Data Accuracy: Review Excel data for completeness and accuracy prior to upload | ||
+ | * Error Prevention: Proactive validation reduces import errors and processing delays | ||
+ | |||
+ | **Post-Import Review:** | ||
+ | * Validation Results: Carefully review validation screen for any excluded items | ||
+ | * Data Correction: Address invalid entries and re-import if necessary | ||
+ | * System Verification: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | **__Incomplete Data Handling and Validation Protocols__** | ||
+ | |||
+ | __Partial Data Import Processing__ | ||
+ | |||
+ | **Incomplete Field Management** | ||
+ | * System Behavior: New products with missing required fields trigger "Bad Row" validation warnings | ||
+ | * Import Processing: Despite validation warnings, products are still integrated into the contract configuration | ||
+ | * Data State: Items exist within the contract but remain in incomplete status pending required field completion | ||
+ | |||
+ | __Contract Save Validation__ | ||
+ | |||
+ | **Required Field Verification** | ||
+ | * Save Process: Contract save operation initiates comprehensive data validation | ||
+ | * System Notification: | ||
+ | * User Guidance: Clear messaging directs users to specific fields requiring completion | ||
+ | * Save Prevention: Contract cannot be finalized until all required fields are properly populated | ||
+ | |||
+ | __Data Integrity Management__ | ||
+ | |||
+ | **Two-Stage Validation Process:** | ||
+ | * Import Stage: Allows partial data entry with warning notifications | ||
+ | * Save Stage: Enforces complete data requirements for contract finalization | ||
+ | |||
+ | **Business Benefits:** | ||
+ | * Workflow Flexibility: | ||
+ | * Error Prevention: Multiple validation checkpoints prevent incomplete contract deployment | ||
+ | * Data Quality: Ensures all contracts meet minimum data requirements before activation | ||
+ | |||
+ | __User Action Requirements__ | ||
+ | |||
+ | **Post-Import Tasks:** | ||
+ | * Field Completion: Address all flagged required fields identified during import validation | ||
+ | * Data Review: Verify accuracy and completeness of all imported product information | ||
+ | * Contract Finalization: | ||
+ | |||
+ | {{: | ||
+ | |||
+ |