Suppose your business application has an order entry process and displays the following data entry panel:
┌──────────────────────────────────────────────────────────┐ ┐ │ ***** SALES ORDER ENTRY ***** │ │ │ │ │ │ ORDER NUMBER : DATE : │ │ │ │ CUSTOMER NUMBER : ____________ │ │ CUSTOMER NAME : │ │ EMPLOYEE NUMBER : │ │ EMPLOYEE NAME : │ │ BRANCH CODE : │ │ │ │ DELIVERY DATE : __-_-__ (YY-MM-DD) │ │ │ │ PRODUCT PRODUCT PRODUCT TOTAL │ │ NUMBER NAME DESCRIPTION QTY PRICE │ │ │ │ _______ ___ │ │ _______ ___ │ │ _______ ___ │ │ _______ ___ │ │ _______ ___ │ │ │ └──────────────────────────────────────────────────────────┘
The order entry process displays data from the previous processes in ORDER NUMBER, DATE, EMPLOYEE NUMBER, EMPLOYEE NAME and BRANCH CODE fields. Then it asks the operator to input ordering information into CUSTOMER NUMBER, PRODUCT NUMBER, DELIVERY DATE and QTY fields. It displays data in CUSTOMER NAME, PRODUCT NAME and TOTAL PRICE fields by querying customer database and product database, and updates order database.
The order entry process should support DBCS in the following items.
Messages and panels, e.g. the above panel, should be DBCS enabled and translated to national languages.
Fields for text such as PRODUCT DESCRIPTION should support DBCS.
Fields for names such as CUSTOMER NAME, EMPLOYEE NAME and PRODUCT NAME should support DBCS.