Re: SWIFT requirement question confirmation

[Kampanat Mongkholrangsalid]

Dear Lili,

    Please see my answer below.

Thank you.

Kampanat

On Wed, Feb 19, 2014 at 3:41 PM, Lili Chen <lili...@chinasystems.com> wrote:

Dear Suang,

As per our discussion, about the SWIFT requirement in document FS_Trade Finance_WSTF13_SWIFT and TELEX Maintenance.docx, there are following issues required to further confirmation.

1. How to decide whether the incoming SWIFT message can be used to create TF transaction or not? It's decided by business operator's thinking or decided by EE system with some rule. In page P26, it seems that system will decide whether protect the field Assign to Module and Assign to Function based on this. But how does system know it can be or can not be used to create TF transaction. The related part is as below:

Assign to Branch (This is the case of assigning Incoming SWIFT message that cannot be used to create TF transaction):

Assign to Branch/Module/Function (This is the case of assigning Incoming SWIFT message that can be used to create TF transaction):

You have taken an example about MT799 which is only used for show information, can you give me the message type list? If the message type is in this list, then system thinks this can not be used to create TF transaction.

     CSTH: It should be have list of message type that the system can create TF Transaction.

 

2. In EEV2.6.2 version, EE-7132 feature, EE system can convert the outgoing SWIFT to Incoming SWIFT message for internal receiver bic which exists in table EXIMUSER.SEC_BUSINESS_UNIT. I have attached this EE-7132 test scenario for your reference. If you consider use EE feature to implement convert outgoing message to incoming message, then ISN number (with format “ASSSSSSSSSS”, "SSSSSSSSSS" is random numbers?) property is required to be enhanced. So please kindly give us your decision, use EE EE-7132 feature or use interface to implement.

   CSTH: Please discus with Suang.

 

3. Below approve function can catch the records with same process status 'W'. If there is one record with 'W' process status, and required branch to do approve in the transaction flow, but HO can also catch this record and approve it after upgrade VTB to EEV2.6.2_CRM001 with GPC feature. Whether this operation flow is allowed or forbidden? Or should change the process status? For example, Branch can only catch 'BW' process status, HO can catch 'CW' process status?

• SWIFT Incoming Approval Function for HO
  
• SWIFT Incoming Approval Function for Branch
  

     CSTH :    

                 The system must catch 2 fields. First is process status. Second is Unit Code. 

                 SWIFT Incoming Approval Function for HO must catch process status is "W" and Unit Code is HO.

                 SWIFT Incoming Approval Function for Branch must catch process status is "W" and Unit Code is Branch.

Please kindly give us the response asap. We need your confirmation to continue the following steps. Thanks!

Any problems or comments, please let us know freely. 

Best Regards,

Lili

[Suang Kamutpornthitaree]

Dear Lili,

Pls see my comment belows.

On Thu, Feb 20, 2014 at 8:21 AM, Lili Chen <lili...@chinasystems.com> wrote:

Dear Kampanat,

Thanks for your kindly response.

Best Regards,

Lili

On Wed, Feb 19, 2014 at 6:58 PM, Kampanat Mongkholrangsalid <kamp...@chinasystems.com> wrote:

Dear Lili,

    Please see my answer below.

Thank you.

Kampanat

On Wed, Feb 19, 2014 at 3:41 PM, Lili Chen <lili...@chinasystems.com> wrote:

Dear Suang,

As per our discussion, about the SWIFT requirement in document FS_Trade Finance_WSTF13_SWIFT and TELEX Maintenance.docx, there are following issues required to further confirmation.

1. How to decide whether the incoming SWIFT message can be used to create TF transaction or not? It's decided by business operator's thinking or decided by EE system with some rule. In page P26, it seems that system will decide whether protect the field Assign to Module and Assign to Function based on this. But how does system know it can be or can not be used to create TF transaction. The related part is as below:

Assign to Branch (This is the case of assigning Incoming SWIFT message that cannot be used to create TF transaction):

Assign to Branch/Module/Function (This is the case of assigning Incoming SWIFT message that can be used to create TF transaction):

You have taken an example about MT799 which is only used for show information, can you give me the message type list? If the message type is in this list, then system thinks this can not be used to create TF transaction.

     CSTH: It should be have list of message type that the system can create TF Transaction.

 

2. In EEV2.6.2 version, EE-7132 feature, EE system can convert the outgoing SWIFT to Incoming SWIFT message for internal receiver bic which exists in table EXIMUSER.SEC_BUSINESS_UNIT. I have attached this EE-7132 test scenario for your reference. If you consider use EE feature to implement convert outgoing message to incoming message, then ISN number (with format “ASSSSSSSSSS”, "SSSSSSSSSS" is random numbers?) property is required to be enhanced. So please kindly give us your decision, use EE EE-7132 feature or use interface to implement.

   CSTH: Please discus with Suang.

             Suang: the format could be like this 0000001, just sequence number from 1.  For outgoing message conversion to incoming message, we can accept what standard feature in EE 2.6.2 if the output are same as in FS.    

 

3. Below approve function can catch the records with same process status 'W'. If there is one record with 'W' process status, and required branch to do approve in the transaction flow, but HO can also catch this record and approve it after upgrade VTB to EEV2.6.2_CRM001 with GPC feature. Whether this operation flow is allowed or forbidden? Or should change the process status? For example, Branch can only catch 'BW' process status, HO can catch 'CW' process status?

• SWIFT Incoming Approval Function for HO
  
• SWIFT Incoming Approval Function for Branch
  

     CSTH :    

                 The system must catch 2 fields. First is process status. Second is Unit Code. 

                 SWIFT Incoming Approval Function for HO must catch process status is "W" and Unit Code is HO.

                 SWIFT Incoming Approval Function for Branch must catch process status is "W" and Unit Code is Branch.

Please kindly give us the response asap. We need your confirmation to continue the following steps. Thanks!

Any problems or comments, please let us know freely. 

Best Regards,

Lili

--
Best Regards,

Walachanat  Kamputpornthitaree
Support and Implementation Manager
China systems (Thailand) Co., Ltd.
21/10 Soi Ruamrudee 1, Ploenchit Rd
Lumpini, Pathumwan, Bangkok 10330, Thailand.
Tel No. 662 650 7915
Fax No. 662 650 7914
Mobile: +6681-562-0333

[Suang Kamutpornthitaree]

Hi Lili,

Sorry for late reply.   We have reviewed but there is no internal message mentioned in this.    

Thanks.

On Mon, Feb 24, 2014 at 2:03 PM, Lili Chen <lili...@chinasystems.com> wrote:

Dear Suang,

The Function Specification of SWIFT requirement is available now and required your review and confirmation. You can get it from the SharePoint with the path below and the file name is Functional Specification[ERFEE-100766]-VTB SWIFT and TELEX Maintenance.doc.

http://sp.eximbills.com/products/ee/Shared%20Documents/Forms/AllItems.aspx?RootFolder=%2fproducts%2fee%2fShared%20Documents%2fEE%20Patch%20Release%2fProject%2fVTB%2fFunction%20Spec&FolderCTID=&View=%7bA877D6FD%2d2B17%2d4226%2dB807%2dDCB3C32A7455%7d

The preliminary estimated man-day is 42 containing the items below:

• Function Spec: 12 man-day
  
• Coding &Unit Test: 15 man-day
  
• Test&Document: 15 man-day
  

As discuss with Alec, the target delivery date is at the end of April, 2014.

Any comment is welcome and appreciate. Thanks!

Best Regards,

Lili

[Suang Kamutpornthitaree]

Dear Lili,

Sorry for late reply.

Kampanat accepted your solution and we will use standard Convert SWIFT message to inward message.  

Pls proceed.

On Wed, Mar 5, 2014 at 3:51 PM, Lili Chen <lili...@chinasystems.com> wrote:

Dear Suang,

Due to there is no clear response about who will convert outgoing message to incoming message, and in your FS, it's depend on SWIFT B2B interface, so it's not mentioned in this Function Spec. I have ever sent the test scenario to you before about how EE convert outgoing SWIFT to incoming message for internal BIC, here I attach the related function spec and test scenario again for your reference and confirmation. This feature has been implemented in EEV2.6.2. Once VTB upgrade to this version, this feature is there.

Due to the document is too large, please get them form the FTP with the path below:

ftp:/ftp.eximbills.com//CSNJ/EE/Projects/VietinBank/Document/

• Functional Specification[EE-7132]-Internal Outward to Inward Box.rar
  
• TestS[EE-7132]-Convert outward SWIFT message to inward message for internal receiver's BIC.rar

Any problem, please contact us freely. Thanks!

Best Regards,

Lili