8/4/2019 Issues 2[1]CSC

1/2

Sir,

Yesterday I tested DCW/TCW, the following problems have been identified

1. While revision 1 , Please remove NBGD to BGTD function for ECW, TCW and DCW.

IT was given in FS that when ever revision is 1 for TC and ES projects, status shouldchange. It is not an issue, please provide a change request to do it.

2. Please remove mandatory for payment fields . Kept the purpose of NBGD in User Status

as like in T&D and Bulk Schemes.

It is given in FS that certain payments should be mandatory. It is not an issue, pleaseprovide a change request to do this change.

3. In ECW /T CW, even though system status is not B UDG , WBS is releasing , it should not

happen like that.I need to check this. Please provide whether you are incorporating status ZPSRA01 ornot on WBS Element.

4. All pa y ment details will be captured in user fields and FBCJ document numbers. Based

on this, payment information report is required (estimated and paid). For HT, installments

will be allowed, hence it should be captured in WBS and reports.Still user fields population logic is not given. Then it is not an issue in currentdevelopment. Please provide a change request to carry out this change.

5. In FBCJ document, WBS number should be captured.

Logic was not given initially. Please incorporate this in new change request then I willtake it further.

6. MIGO for alternative meters can be accepted for a particular reservationagainst network.

Alternative numbers logic is given in FS? It is only today that we discussed about thisissue. Please provide the complete details of your problem, also rather it is a functionalissue, should be dealt with MM team also.

7. In revision 0 (application registration), it is generating directly WBS. When extension only

it should create new WBS.But for some categories (categories like HT, LT-III, IV, V, VI, VIII should create directlyWBS.For remaining Categories LT-I, II, VII, it should not create WBSIn all FS it is clearly given that WBS element should be created. If you want above

change to be done, then it should be a change in current development. Also category logicshould be incorporated in current CSC/ development.

8. After approval of estimate, payments will be made in EROs through cash (in cases). It

should also captured in SAP as like in CSC flat file.PR Number capture logic is not given in ongoing developments. Please provide the logicthen I will incorporate the development.

9. For supply to apartments, more than one application will be registered, for this it should

create one WBS in revision 0 scenarios.Logic needs to be taken from CSC. It will be handled on provision of complete details.

10. In ECW scenario, revision 2 is not working (i.e. meter is not issuing)Please check the FS given for ECW, above logic is not given. Then it is not an issue incurrent development. Please provide a change request to carryout the change.

11. Additional load registration :1. For some categories only Payments will be made.2. For some categories wbs has to be created. After approval, payments will bemade.

Provide the complete details. It seems to be new requirement which was never discussed.

12. Test run is required for upload transaction code ZPSA010.

8/4/2019 Issues 2[1]CSC

2/2

I will check the possibility of this and let you know. Also system performance should beconsidered for test run.

13. For DCW scenario, revision 2 is not required.Check FS, above point is given. Please provide a change request to carryout abovechange.

14. DCW settlement rule is not defined.We are trying for RA for DCW, it was discussed with CO team already about thepossibility. And this point is not linked with CSC interfacing.

15. TCW result analysis pending.\

As per my knowledge TCW doesnt require settlement or RA. I will check with CO teamon this.

16. ECW/DCW/TCW planning and actual Over head charges is pendingPlease provide the details.