Alpha Name and Search Routine for Asian language

Purpose of Document

In implemented EnterpriseOne globally and records all the data in a single DB there can be issues in dealing with Asian languages which can be recoded in Unicode.

So to minimize confusion, this document is to explain,

• How address book search is working in P01012in Asian languages
• How applications interface values entered in running applications

Most commonly languages below (UDC 01/LP),

As <Document 950216.1> - E1: 01: FAQ - Frequently Asked Questions about Address Book Word Search (P01BDWRD & R01BDWRD) reads P01012 - Address Book contains 4 columns which may affect search result as below,

How to populate ALP1 and MLN1 in P01012 - Address Book?

Secondary Alpha Name (ALP1) and Secondary Mailing Name (MLN1) are to be populated only when F0092.LNGP (Language) belongs to value listed above (CS, CT, J and KO) and it's special handling code is 2 or 3.

What is the usage of Special Handling Code 2 and 3 in UDC 01/LP?

In non-Unicode environment this value is to determine how many bytes needed to encode/decode a single character. So 2 means it needs two bytes to encode one character.

However it requires 2 bytes in encoding/decoding a character in Unicode environment so this value is more for controlling how the behavior of application and how it build search strings based on Alpha Name and other information if needed.

How the form W01012B is made up of?

The form W01012B - [Work With Addresses] made up of two components,

• Form Header: Alpha Name and Search Type. Though it is displayed as "FC Alpha Name" actual column value handled here is DC (Description - Compressed)
• Grid: "GC Alpha Name" in Grid is actual value of F0101.ALPH where Grid control does not contain DC as a member

     : Owing to this settings the value returned may be vary

How it populates F0101.DC in Asian language?

As we have discovered above, Secondary Alpha Name (ALP1) is to be populated then Description - Compressed (DC) is to be populated based on Secondary Alpha Name (ALP1) not Name - Alpha (ALPH). In case the language setting in your user profile is different between addition of address book and changing of address book, which may yield different result.

For instance,

• Adding a new address book with 'Blank' Language in User Profile: DC is populated based on ALPH
• Changing same address book information with 'CS' Language in User Profile: DC is populated based on ALP1

How it compresses ALP1 to DC which is used for search text?

Refer <Document > - E1: 01: FAQ - Frequently Asked Questions about Address Book Word Search (P01BDWRD & R01BDWRD)
For Asian language,

• There is NO stripping based on UDCH95/SC (so bracket and hyphen etc will be remained)
• NO upper case
• So it only removes a space in between words

In running application how it returns Address Number in exiting Customer/Supplier?

In case you knows partial description of supplier or customer, which narrows down which meets condition input,

• In system code 42/43 ALKY is handled by N0100061 - Scrub Address Number (ScrubAddressNumberNER). The purpose of this NER is to call/populate P0101SL - Address Book Long Search. For this example this NER is to be serialized (object) and can call other serialized object (P0101SL)
• In system code 03B/04 ALKY is handled by B0100016 - F0101 Edit Address Number (ScrubAddressNumber)

         : The routine between SO/PO and AR/AP are different because AR/AP is dealing with Customer/Supplier which are already specified in SO/PO process