Angel Tamayo wrote: >Due to a recent tax reform, a customer needs to change the value added tax >(VAT).
Good luck. This is going to be hard. You have a sandbox to test out your changes with help from your accounting staff? >Currently they have that value inserted as part of the program's code where is >used. In how many places is that constant placed? In one program or in many subsequent called programs? >Now they are looking for the best way/practice to implement that kind of >variables. VAT is too dynamic. As others said, rahter use a dataset to place all your VAT things. Put your VAT in a dataset using records containing VAT-type, VAT rate, start-date, end-date, company name, country, other accounting criterias, transaction type, etc. etc. etc. Oh, protect that dataset with everything you can. Your auditor will asks who can change the contents of that dataset. Forget for now about engaging CICS and using PARMS. Good luck. You and your programmers will need it. Groete / Greetings Elardus Engelbrecht PS: I have contributed in the past with writing+checking of programs for accounting purposes. I'm glad I'm not working much with it these days... ;-) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
