SHARE
TWEET

Untitled

a guest Jan 11th, 2019 59 Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. ++================ Bug fix comments by DevOps  - Start ============++
  2. @ Functional Analysis
  3. @ -------------------
  4. @
  5. @ This is a request to enhance custom report "Inventory Excess & Obsolete Data
  6. @ Report". The enhancement is the addition of a filter to mark an item as
  7. @ Make or Buy, based on the Make or Buy attribute of the item. If the item is a
  8. @ Buy item, then the name of the Buyer, as well as his/her HR management hierarchy
  9. @ will be displayed. If it is a Make item, then the name of the Planner, as well as
  10. @ his/her HR management hierarchy will be displayed. Currently, the report shows
  11. @ only the information of the Buyer, even if the item is a Make item.
  12. @
  13. @ The report output was modified as follows:
  14. @
  15. @ - A column was added to the left of the 'Buyer' column to signal when an item is
  16. @   Make or Buy.
  17. @ - The 'Buyer' column was renamed as Buyer/Planner. If the Make/Buy column
  18. @   indicates Buy, the Buyer/Planner columns will show the name of the buyer of the
  19. @   item; otherwise, the name of the Planner.
  20. @
  21. @ Technical Analysis
  22. @ ------------------
  23. @ Concurrent program "Inventory Excess & Obsolete Data Report" ($MIS_INV_TOP/patch/115
  24. @ /sql/MISINV_EXCESS_OBSOLETE_DATA_B.pls, ARCS v 120.2) was modified as follows:
  25. @
  26. @ 1. The original report used a query to obtain HR data of the buyer of the item. An
  27. @    IF conditional was added to check the mtl_system_items_b.planning_make_buy_code
  28. @    attribute of an item. If value is 2 (Buy) then query to obtain HR information
  29. @    of buyer is executed. If value is 1 (Make) then query to obtain HR information
  30. @    of Planner is executed.
  31. @
  32. @ 2. The program uses the Fnd_File.Put_Line procedure to generate the report as a
  33. @    comma-separated-values file. The arguments passed to the function were changed,
  34. @    which determine the column of the spreadsheet, adding the "Make/Buy" column.
  35. @    Also, the "Buyer name" column was changed to "Planner/Buyer"; this column will
  36. @    display the name of the Planner or Buyer according to the value determined by
  37. @    the conditional explained in point 1.
  38. @
  39. @ Functional Impact
  40. @ -----------------
  41. @ The report is used to analyze inventory excess & obsolescence, every quarter mainly.
  42. @ This analysis was affected by the original state of the report, because it showed
  43. @ buyer information when planner information was expected for Make item.
  44. @
  45. @ Code Reviewed By
  46. @ ----------------
  47. @ francisco.aguirre@oracle.com
  48.  
  49. @ To be Filled by Reviewer:
  50. @ -------------------------
  51. @ Does this impact existing functionality (Yes/No) : Yes
  52. @ Has a thorough impact analysis been done(Yes/No) : Yes
  53. @ .
  54. @ Impact:
  55. @ -------
  56. @ 1) Magnitude of code change: The changes to the report are significant, they
  57. @    change the core information displayed by the report.
  58. @ 2) Module(s) affected: Custom Inventory
  59. @ 3) Unit Test details: The report was generated in GSIBB. 20 random rows were checked
  60. @    to verify that if the item was Make, the name of the planner would show up; if
  61. @    item was Buy, the name of the buyer. The check was successful. Also, the manager
  62. @    level 1 and 2 was checked against information of the buyer/planner in ARIA for
  63. @    these20 random rows. Filer verified the results (see update
  64. @    *** MPARIKH 09/14/11 12:18 pm ***).
  65. @ ---------------------------
  66.  
  67. ++================ Bug fix comments by DevOps  - Close ============++
RAW Paste Data
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy. OK, I Understand
 
Top