Uploading excel to create synonym creates A7V as ACTUAL instead of A7B or A7 when the machine requirements are below:

The OracleDB character set to "JA16SJISTILDE
Oracle Client NLS_LANG: JAPANESE_JAPAN.AL32UTF8
WebFOCUS Client and Server: UTF-8

ACTUAL is A7B is not good. 

This is that the Oracle can store 3 DBCS chars at  CHAR(7 BYTE) with JA16SJISTILDE. The reporting server receives 10 byte as maximum with AL32UTF8 of NLS_LANG value.  If it is A7B, the data cuts at 7 bytes.

ACTUAL is A7 also is not good because of the following.

data is 3 DBCS chars with one space        4 unicode chars  reporting server receives 
data is 2 DBCS chars with three spaces    5 unicode chars  reporting server receives
data is 'ABCDEFG'                                    7 unicode chars  reporting server receives.

Therefore, we use A7V at ACTUAL.

The Oracle fills spaces at the rest of the area when you insert data less than 7 byte like 12345 with NLS_LANG is JA16SJISTILDE.
The reporting server receives data as follows with NLS_LANG is AL32UTF8.

12345    is  0x31 0x32 0x33 0x34 0x35 0x20 0x20

When you insert DBCS data is あいう with NLS_LANG is JA16SJISTILDE , the reporting server receives data as follows with NLS_LANG is AL32UTF8.

あいう    is 0xE3 0x81 0x82 0xE3 0x81 0x84 0xE3 0x81 0x86 0x20

When you use A7, the result loose training space.

The A7V of the current result is the correct result because Oracle returns trailing space.