Specification » History » Version 2
chin-yeh, 08/10/2011 09:30 AM
1 | 1 | chin-yeh | {{toc}} |
---|---|---|---|
2 | |||
3 | h1. Specification |
||
4 | |||
5 | h2. Table Schema |
||
6 | |||
7 | h3. VP_INTERFACE |
||
8 | |||
9 | 2 | chin-yeh | This table stores those events which are needed to submit to VP services. It can also be used to track the status of the submitted events. |
10 | 1 | chin-yeh | |
11 | <pre> |
||
12 | <code class="SQL"> |
||
13 | create table vp_interface ( |
||
14 | id int not null generated always as identity, |
||
15 | process_code varchar(30), |
||
16 | trx_id varchar(30) not null, |
||
17 | trx_type varchar(15), |
||
18 | country_code varchar(10), |
||
19 | member_id varchar(20), |
||
20 | member_name varchar(100), |
||
21 | reg_date varchar(8), |
||
22 | expiry_date varchar(8), |
||
23 | vp_amount decimal(10,2), |
||
24 | invoice_amount decimal(10,2), |
||
25 | status varchar(15), |
||
26 | last_updated timestamp, |
||
27 | error_code varchar(10), |
||
28 | error_message varchar(255), |
||
29 | primary key (id) |
||
30 | ); |
||
31 | |||
32 | create unique index idx_vp_id_type on vp_interface(trx_id,trx_type); |
||
33 | create index idx_vp_status on vp_interface(status); |
||
34 | create index idx_vp_err_code on vp_interface(error_code); |
||
35 | </code> |
||
36 | </pre> |