Enhancement #6704

[UAT_SB_SOCSO-005] : Add new validation rule on SOCSO File

Added by Tan Lee Yong almost 8 years ago. Updated almost 8 years ago.

Status:Closed - End of life cycleStart date:November 15, 2016
Priority:ImmediateDue date:November 15, 2016
Assignee:Norhaidah Md Dasuki% Done:

100%

Category:UAT - SOCSOSpent time:-
Target version:-

Description

New validation rules:
1. Employer Code – Customer to use the same Employer Code (Successful) during the Testing.

2. Contribution Month – Must be greater than ‘00’ and less than or equal to ‘12’, No advance Contribution Month.

3. Contribution Year – Valid year “YYYY”, No advance Contribution Year.

4. Contribution Amount – Valid Number

5. Payment Date – Valid Date, no advance date

6. Payin Slip Number – Should be tally with EMPE01.txt file and unique to each transaction / payment.

7. IC Number – PERKESO advice to use New IC number. – No duplication of IC allowed in the same transaction.

Error Message to Display (V 0 1).docx (16.9 KB) Norhaidah Md Dasuki, November 04, 2016 11:55

Error Message to Display (V 0 2).docx (19.9 KB) Norhaidah Md Dasuki, November 15, 2016 16:39

Brg8A.txt Magnifier (450 Bytes) Nurul Akmal, November 15, 2016 19:12

Task #6704 Test Result [UAT_SB_SOCSO-005] - New Validation Rule on SOCSO File.docx (882 KB) Nurul Akmal, November 16, 2016 17:04

History

#1 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn almost 8 years ago

  • Status changed from New - Begin Life Cycle to Internal Testing
  • Assignee changed from Ngoh Chee Onn to Erni Suhaireen Zulkifli

Hi Erni,

Please refer below in both for my comment.

1. Employer Code – Customer to use the same Employer Code (Successful) during the Testing.
- This refer to SOCSO testing file report, please help to check current system isn't fullfil socso requirement.

2. Contribution Month – Must be greater than ‘00’ and less than or equal to ‘12’, No advance Contribution Month.
- Validation added when user upload the socso file from BIB.

3. Contribution Year – Valid year “YYYY”, No advance Contribution Year.
- Validation added when user upload the socso file from BIB.

4. Contribution Amount – Valid Number
- Validation added when user upload the socso file from BIB.

5. Payment Date – Valid Date, no advance date
- Payment Date according to approve date, it wouldn't save advance date in db.**

6. Payin Slip Number – Should be tally with EMPE01.txt file and unique to each transaction / payment.
- This refer to SOCSO report, please help to check current system isn't fullfil socso requirement.

7. IC Number – PERKESO advice to use New IC number. – No duplication of IC allowed in the same transaction.
- Validation added when user upload the socso file from BIB.

**Please test after kah yan deploy to SIT.

Thank you.

#2 Updated by Norhaidah Md Dasuki almost 8 years ago

Hi Erni,
Attached is the error message forward by Idayu for your reference.

#3 Updated by Norhaidah Md Dasuki almost 8 years ago

  • Category changed from Development to UAT - SOCSO

#4 Updated by Norhaidah Md Dasuki almost 8 years ago

  • Assignee changed from Erni Suhaireen Zulkifli to Nurul Akmal

#5 Updated by Norhaidah Md Dasuki almost 8 years ago

  • File Error Message to Display (V 0 2).docx added
  • Subject changed from SOCSO: Add new validation rule on SOCSO File to [UAT_SB_SOCSO-005] : Add new validation rule on SOCSO File
  • Due date set to November 15, 2016
  • Status changed from Internal Testing to Development / Work In Progress
  • Assignee changed from Nurul Akmal to Ngoh Chee Onn
  • Priority changed from Normal to Immediate
  • Start date changed from October 14, 2016 to November 15, 2016

Refer email from Idayu
date: Tue, Nov 15, 2016 at 4:24 PM
subject: RE: CMS: SOCSO

Chee On, Please fix. Tq

#6 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn almost 8 years ago

  • Assignee changed from Ngoh Chee Onn to Yap Kah Yan

Hi Kah Yan,

Please help to pull and deploy into SIT and UAT environment. Please run below query in server db.
update dbo.IB_FILE_FIELD set FIELD_NAME = 'Contribution Amount' where FIELD_NAME = 'Contribution';

Thank you.

#7 Updated by Norhaidah Md Dasuki almost 8 years ago

Updated by Idayu date: Tue, Nov 15, 2016 at 5:02 PM

For field validation No. 1 – Yes, confirmed. Customer allow to upload another file during testing but only if customer using the same Employer Code. BIB should validate if customer upload file using different Employer Code.

  • Update by Chee Onn - For field validation no 1, current system only allow user to upload socso with one employer number, which setting in IBAM under company enquiry module. If user upload file not same with the employer number settting in IBAM, system is validate and throw error message 'Invalid Employer Number'. That's why, customer will not able to upload file other than the employer number setting in IBAM or employer number not same as last uploaded successful file but under testing.
  • Update by Idayu - Noted on the clarification thus it’s cover for the field validation no 1. But as mentioned in the expected result, kindly change the error message from Employer Number not registered to Invalid Employer Code.

Field Validation No. 5 – Understand and confirmed.

#8 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn almost 8 years ago

Hi Kah Yan,

I got modified the error message from invalid employer no to invalid employer code. Please pull and help to deploy.

Thank you.

#9 Updated by Nurul Akmal almost 8 years ago

  • File Brg8A.txtMagnifier added
  • Assignee changed from Yap Kah Yan to Ngoh Chee Onn

Hi Chee Onn,
Kindly check this file.
Got an error message when approve the transaction.

Step to reproduce.
  1. Login as Initiator.
  2. Upload File to SOCSO.
  3. Login as approver.
  4. Approve transaction.
    
Error message: Error while performing your request.

Thank you.

#10 Avatar?id=1966&size=24 Updated by Ngoh Chee Onn almost 8 years ago

  • Assignee changed from Ngoh Chee Onn to Yap Kah Yan

Hi Kah Yan,

Please pull and help to deploy. The root cause is the terminate date is empty in file but approver there didn't check the null pointer exception.

Thank you.

#11 Updated by Yap Kah Yan almost 8 years ago

  • Status changed from Development / Work In Progress to Internal Testing
  • Assignee changed from Yap Kah Yan to Nurul Akmal

Deployed. Please retest

#12 Updated by Nurul Akmal almost 8 years ago

Hi Kak Haida,
Kindly review Test Result attached.

Thank you.

#13 Updated by Norhaidah Md Dasuki almost 8 years ago

  • Status changed from System Integration Test to User Acceptance Test

reviewed. send for user retest

#14 Updated by Norhaidah Md Dasuki almost 8 years ago

  • Status changed from User Acceptance Test to Closed - End of life cycle

16/11/2016 [Idayu] Retest and pass

Also available in: Atom PDF