Professional Documents
Culture Documents
SRF - CER - SRV000367 - Field Overflow Error - ZWM004 Carton ID Label Report - V1.0
SRF - CER - SRV000367 - Field Overflow Error - ZWM004 Carton ID Label Report - V1.0
1. REQUESTOR INFORMATION
2. REQUEST INFORMATION
3. CHANGE HISTORY
4. REQUIREMENT DEFINITION
a. Current Situation
CER encounter field overflow error when sum up field of Label Scan Qty column in the
ZW004 report. This error also can be found for Full Carton Qty column in the same report.
This is due to the fixed length of 4 for field Label Scan Qty table and Full Carton Qty
b. Requirement Definition
Change only field length of Label Scan Qty and Full Carton Qty from 4 to 6 digit for the report
ZWM004 only.
c. Business Justification
a. Work Scope
i. To change max length digit character from 4 to 6 for2 fields Label Scan Qty and Full
Carton Qty in report ZWM004..
b. Expected Outcome/Result
i. New maximum 6-digit character field length Label Scan Qty and Full Carton Qty
column for the report ZWM004.
ii. Label Scan Qty and Full Carton Qty column for the report ZWM004 can sum up to
6-digit character field length.
c. Impact Analysis
d. Assumptions
i. Abeam is responsible in updating the Functional Specification and performing the unit
test based on the work scope and expected result as specified in the approved SRF.
ii. ABeam will be responsible on performing the unit test based on the work scope and
expected result.
iii. CER will be responsible for:
a. User Acceptance Testing (UAT)
b. Master Data maintenance, if any
c. Mapping Table and Customized Table maintenance, if any
d. Regression testing
e. Confirm and Accept the closure of the CR
iv. Any system inconsistencies not related to this change but affecting the implementation
of this change will be reviewed and may require additional effort
i. Any request for UAT and Post Go Live support shall be charged per actual effort
e. Technical Details
a. Deliverable Documents
PRD Confirmation
7. ESTIMATION DETAILS
c. Total Effort
• Unless approved by the client, the requirements for this SRF are valid only for five (5) working days
commencing from the date of submission to the client, after which, it is subject to possible changes
where ABeam Consulting reserves the right to request for a resubmission of SRF or decline the
SRF.
• ABeam Consulting reserves the right not to pursue with the SRF for reason owing to dependencies
not wholly under the control or jurisdiction of the Service Provider.
• The submitted SRF shall not take into consideration the impact of additional requirements or
changes received after the approved date from the client. If so required, this will initiate another
revision of the SRF.
• ABeam Consulting shall not be obligated to meet any new or changes to requirements received
after the approved date (from the client) and if so required, shall go through a change control
process followed by submission of a revised SRF.
• ABeam Consulting will not be held responsible for the inaccuracy of deliverables in the absence of
validation for the above listed assumptions, if available, prior to the approval of the SRF.
• ABeam Consulting shall not be responsible for the outcome of delivery that is adversely affected
directly or indirectly by third party implementation or customization which is not part of ABeam’s
subcontractor/partnership engagement.
• A support warranty of 1 (one) calendar month effective from the date of transport to the Target/
Production System shall be applied accordingly and its warranty status shall same be observed.
The support warranty will only be limited to issues that are within the scope of this signed off change
request and functional specification. Any additional requirement deemed necessary which is
beyond the scope of the current change request shall be taken up as part of change control and
possibly raised as a separate new change requirement with additional effort estimation proposed.
Issues discovered after the 1 (one) month warranty shall be treated as the usual ticket-based
support drawn from the client’s support budget.
• The time length between the date of completion of UAT and date of transport to the
Target/Production system shall be considered a lapse and granted a maximum of five (5) working
days from which the warranty shall take effect from the 5th day counting towards the 1 (one)
calendar month support warranty if the delivered objects have yet to be transported to the
Target/Production system after the 5th day of the lapse period.
9. APPROVAL DETAILS
Comment
Reviewed By Approved By
Position Position
Reviewed Date Approved Date