3612.2001-02-21.farmer.ham.txt 2.1 KB

1234567891011121314151617181920212223242526272829303132333435
  1. Subject: eol deal ids in path manager
  2. thought you might want to see this .
  3. - - - - - - - - - - - - - - - - - - - - - - forwarded by edward terry / hou / ect on 02 / 21 / 2001 09 : 19
  4. am - - - - - - - - - - - - - - - - - - - - - - - - - - -
  5. from : matt pena / enron @ enronxgate on 02 / 21 / 2001 09 : 11 am
  6. to : edward terry / hou / ect @ ect , george f smith / hou / ect @ ect , patti
  7. sullivan / hou / ect @ ect , katherine l kelly / hou / ect @ ect , robert
  8. superty / hou / ect @ ect , victor lamadrid / hou / ect @ ect , beverly beaty / hou / ect @ ect ,
  9. donna greif / hou / ect @ ect , richard pinion / hou / ect @ ect
  10. cc : chris schomer / enron @ enronxgate , brian ripley / enron @ enronxgate , bob m
  11. hall / na / enron @ enron , bryce baxter / hou / ect @ ect
  12. subject : eol deal ids in path manager
  13. as you ' re aware , we ' re having to bridge houston street ids into unify from
  14. sitara .
  15. we are being asked , as a requirement , to not display the eol id on statements
  16. that are identified as " broker eol trade " deals originating from eol . we
  17. have two options to accomodate this requirement :
  18. option 1 is to have the modify the bridge code to not bridge over the eol
  19. deal id if the deal is a " broker eol trade " deal . one of the drawbacks of
  20. this option is that you won ' t be able to referenence the eol id on the path
  21. manager for these related deals . all other deals will have the eol deal id ,
  22. if applicable . the eol id would not show up on the statements because it
  23. wouldn ' t be populated .
  24. option 2 is to modify several areas of code in the settlements area which may
  25. be more time consuming . the obvious code change would be in the statement
  26. generation area as well as other report type information .
  27. option 2 allows you the greatest flexibility while option 1 may be quicker to
  28. implement .
  29. please pass this along to others in your group and get feedback . please
  30. share your thoughts . . . .
  31. i ' ve attached an email explaining the broker eol trades . this is not to be
  32. confused with broker deals done at a given point with not transportation .
  33. these will continue to come across as you ' d normally expect .
  34. any questions , please ask . . .
  35. thanks !