++================ Bug fix comments by DevOps  - Start ============++
@ Functional Analysis
@ -------------------
@
@ This is a request to enhance custom report "Inventory Excess & Obsolete Data
@ Report". The enhancement is the addition of a filter to mark an item as
@ Make or Buy, based on the Make or Buy attribute of the item. If the item is a
@ Buy item, then the name of the Buyer, as well as his/her HR management hierarchy
@ will be displayed. If it is a Make item, then the name of the Planner, as well as
@ his/her HR management hierarchy will be displayed. Currently, the report shows
@ only the information of the Buyer, even if the item is a Make item.
@
@ The report output was modified as follows:
@
@ - A column was added to the left of the 'Buyer' column to signal when an item is
@   Make or Buy.
@ - The 'Buyer' column was renamed as Buyer/Planner. If the Make/Buy column
@   indicates Buy, the Buyer/Planner columns will show the name of the buyer of the
@   item; otherwise, the name of the Planner.
@
@ Technical Analysis
@ ------------------
@ Concurrent program "Inventory Excess & Obsolete Data Report" ($MIS_INV_TOP/patch/115
@ /sql/MISINV_EXCESS_OBSOLETE_DATA_B.pls, ARCS v 120.2) was modified as follows:
@
@ 1. The original report used a query to obtain HR data of the buyer of the item. An
@    IF conditional was added to check the mtl_system_items_b.planning_make_buy_code
@    attribute of an item. If value is 2 (Buy) then query to obtain HR information
@    of buyer is executed. If value is 1 (Make) then query to obtain HR information
@    of Planner is executed.
@
@ 2. The program uses the Fnd_File.Put_Line procedure to generate the report as a
@    comma-separated-values file. The arguments passed to the function were changed,
@    which determine the column of the spreadsheet, adding the "Make/Buy" column.
@    Also, the "Buyer name" column was changed to "Planner/Buyer"; this column will
@    display the name of the Planner or Buyer according to the value determined by
@    the conditional explained in point 1.
@
@ Functional Impact
@ -----------------
@ The report is used to analyze inventory excess & obsolescence, every quarter mainly.
@ This analysis was affected by the original state of the report, because it showed
@ buyer information when planner information was expected for Make item.
@
@ Code Reviewed By
@ ----------------
@ francisco.aguirre@oracle.com

@ To be Filled by Reviewer:
@ -------------------------
@ Does this impact existing functionality (Yes/No) : Yes
@ Has a thorough impact analysis been done(Yes/No) : Yes
@ .
@ Impact:
@ -------
@ 1) Magnitude of code change: The changes to the report are significant, they
@    change the core information displayed by the report.
@ 2) Module(s) affected: Custom Inventory
@ 3) Unit Test details: The report was generated in GSIBB. 20 random rows were checked
@    to verify that if the item was Make, the name of the planner would show up; if
@    item was Buy, the name of the buyer. The check was successful. Also, the manager
@    level 1 and 2 was checked against information of the buyer/planner in ARIA for
@    these20 random rows. Filer verified the results (see update
@    *** MPARIKH 09/14/11 12:18 pm ***).
@ ---------------------------

++================ Bug fix comments by DevOps  - Close ============++