Minimum Version Required: 22.01
Pre-Conditions
User must have appropriate permissions to import sheet return data
Import file must contain properly formatted data for sheet returns
Required fields must be mapped and populated in the import file
Related records (like product codes) should already exist in the system
Steps
EDBL Routines Disclaimer: This EDBL routine represents advanced functionality primarily intended for use by Encompass technical staff. While technically proficient customers may utilize these routines, please be aware that they fall outside the scope of standard support. Assistance with EDBL routines is not covered under standard support agreements and may require billable services from our Professional Services team. Please ensure you thoroughly understand this routine before implementation in your production environment
The LoadSheetReturn routine imports sheet return data from external files into the system. This routine processes return information for sheet products, updating inventory, tracking return reasons, and maintaining audit trails.
When running this import:
The system first validates all data in your import file against system requirements
For each record, the system attempts to find if a matching sheet return already exists
The routine processes the main SheetReturn record and any related information (return reasons, condition codes, etc.)
Actions are performed based on your selected import method:
Add Only: Only creates new return records; skips records that already exist
Add or Update: Creates new returns or updates existing ones
Update Only: Only updates existing returns; skips records not already in the system
The system uses several methods to match records to existing returns, including internal IDs and translation values that map to external system identifiers
Fields And Definitions
Core Return Fields:
ReturnID: External system identifier for the return
ReturnDate: Date when the return was processed
ProductCode: Identifier for the returned product
Quantity: Number of sheets returned
ReturnReason: Code indicating why the product was returned
ConditionCode: Status/condition of the returned sheets
CustomerID: Identifier for the customer making the return
InvoiceNumber: Original invoice number for the returned product
ReturnAmount: Monetary value of the return
ProcessedBy: User who processed the return
Notes: Additional information about the return
Optional Fields:
QualityIssueDetails: Specific information about quality problems
ReplacementOrderNumber: Order number if replacement was issued
DispositionCode: How the returned product was handled
ApprovalCode: Code for special approval situations
ReturnShippingCost: Cost of return shipping if applicable
Best Practices
Validate data before importing, especially dates, quantities, and product codes
Use consistent identifier formats for ReturnID and related fields
Include all available information for returns to ensure complete record-keeping
Consider validating returns in a test environment before importing to production
When updating existing returns, verify return status to avoid modifying finalized records
Keep translation tables updated to ensure accurate matching with external systems
For large imports, process in smaller batches to improve performance and error tracking
Review import logs after processing to identify and address any warnings or errors