New Requirement

3
New requirement during I Demand 29000519 1 29000519 2 29000519 3 29000519 4 29000519 5 29000519 6 29000519 29000484 1 29000484 2 29000484 3 29000484 4 29000484 5 29000484 6 Intergration test new re Demand 29000519 1 29000484 2

description

New requirement

Transcript of New Requirement

Page 1: New Requirement

New requirement during Implementation

Demand

29000519 1

29000519 229000519 3

29000519 4

29000519 5

290005196

29000519

29000484 1

29000484 2

29000484 329000484 4

29000484 5

29000484 6

Intergration test new requirementDemand

290005191

29000484 2

Page 2: New Requirement

New requirement during Implementation

Additional sequence checkHQ deposit use scenario was not part of the HLD and was developed as requested

Updating the custom table upon post processing of the IDOCs (BD87) in all the 5 cases

TOTAL for 2900519

Addition of node <transactions> in the XML schemaError message corrections

Two types of error file which required additional efforts in creating of XML transformation

TOTAL for 2900484

Intergration test new requirement

Error file has to be generated in case if the file contains and Invoice with Transaction ID already presTotal

Issue Description

Determine the incoming payment as Invoice payment or Downpayment based on status field of the BSID document/ as per HLD the ‘payment method’ was supposed to be the differentiating factor

For parallel processing, HLD specified maintenance of table but it required substantial amount of Technical efforts

Error message changes/ No error message was specified in the HLD and the description had to be changed as requested

Posting _type logic change to identify if the type is Downpayment or Invoice

For parallel processing, HLD specified maintenance of table but it required substantial amount of Technical efforts

Change in the way the system should consider the mandatory values in the XML file based on the payment method & accordingly changes in the error message

Invalid sequence as per the HLD has to be changed to valid sequence (PSTB status Rejected – file status Pending should be a valid sequence and should be treated accordingly)

Page 3: New Requirement

Technical efforts Functional efforts Total

1.25 0.75 2

1 0.5 1.51 1 2

3 2 5

1 2 3

3 2 5

10.25 8.25 18.51.25 0.75 2

3 2 5

5 3 71 1 2

2 1 3

2 2 4

14.25 9.75 23

Technical Efforts (days) Functional efforts (days) Total (days)

0.5 0.5 1

1 0.5 1.51.5 1 2.5