1 / 8

DBSi 5.0 Data Cleansing

DBSi 5.0 Data Cleansing. Agenda. Introduction Customer Information Special Characters & Validity Checks Sample Sequel Related documentation Questions. Introduction.

hsilvas
Download Presentation

DBSi 5.0 Data Cleansing

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DBSi 5.0 Data Cleansing

  2. Agenda • Introduction • Customer Information • Special Characters & Validity Checks • Sample Sequel • Related documentation • Questions

  3. Introduction • There are special characters that either are not allowed or are used for specific purposes within the XMLI interface to CODA or CODA itself. Specific data fields in the Vendor and Customer conversions to CODA need to be validated to determine that none of these characters exist. Data validation and required “clean-up” must be performed prior to executing any data conversions. • Sequels have been created to perform the data validation and report any data issues. These sequels can be created from examples provided in the ‘DBS 2.3.4 to 5.0 Data Cleansing Guidelines’ document in the DDP.

  4. Customer Information • Only customers within CODA v4 (i.e. receivable customers) are converted to CODA eFinance prior to DBSi 5.0 Go Live • Customers from CODA v4 and related data are downloaded into an Excel spreadsheet • New 5.0 field data is added manually and other data can be adjusted as necessary in the spreadsheet • The spreadsheet data is uploaded to an AS/400 file • The Customer Account conversion loads the AS/400 file data and other data (selected during the conversion load) from the DBS Customer file (CIPNAME0) to CODA eFinance • Once DBSi 5.0 is in production use, customers (i.e. receivable) are added to CODA from DBS customer adds

  5. Special Characters and Validity Checks • 20 sequels that evaluate different fields on the DBS customer file CIPNAME0 • 1 sequel that evaluates the CIPLADR0 file (DBS 2.3.4 only) • 19 sequels evaluate information on the LFA1 vendor master • 22 sequels that validate Vendor account data from Coda V4 (DBS 2.3.4 only) • These sequels are looking for special characters such as: ?, *, “, ~, ;, #, !, @, ‘, [, ], <, > • The files are also interrogated for valid currency indicator, valid state code and valid country code

  6. Sample Sequel Fields Validated CUNM – Customer Name SQL Statement SELECT cuno, cunm, cunm2 COLHDG("Cust Name2"), ivtypi COLHDG("Inv" "Ind") FROM cipname0 WHERE cunm CONTAINS '?' OR cunm CONTAINS '"' OR cunm CONTAINS '~' OR cunm CONTAINS ';' OR cunm CONTAINS '*' OR cunm CONTAINS '<' OR cunm CONTAINS '>' ORDER BY cuno

  7. Related Documentation • ADMS Sharepoint • DBS 2.3.4 to 5.0 Data Cleansing Guidelines

  8. Questions / Comments

More Related