Periodic Inventory Value Report question

Hi,

I am currently looking at this and will provide you with a Blitz version of the standard report tomorrow and will also highlight the changes I have made in regards to allowing multiple values for the Cost Group ID parameter.

Kind Regards,

Eric

Hi,

Please find attached the Blitz Report definition XML zipped file for the Blitz implementation of the Standard Oracle Periodic Inventory Value Report.

You can import this from the Blitz Report Setup form using the Tools – Import menu option and selecting XML Upload as the upload type.

In regards to making the Cost Group parameter multiple values enabled, the following changes were made:

1. Cost Group Parameter

This was changed from a bind parameter to a lexical parameter. With it being made a lexical parameter, multiple values is then enabled for the parameter
So as not to impact the :p_cost_group_id parameter used in the before report trigger of the standard Oracle Package (to select the cost group name from the specified parameter) the bind variable used in the lexical was change to :p_cost_group_id2

2. Since the standard Oracle Package before report trigger will error if the :p_cost_group_id bind is not populated, a new dummy hidden parameter has been created using the :p_cost_group_id bind as the anchor.

This will default from the visible Cost Group parameter. In the event multiple cost groups are selected in the Cost Group parameter, the hidden parameter will default to one of the selected cost groups:

select
ccg.cost_group_id
from
cst_cost_groups ccg
where
xxen_util.contains(:$flex$.cost_group,ccg.cost_group_id) = ‘Y’ and
rownum <= 1

This is only used in the Oracle package beforereport trigger to get the cost group name, which is not used in the Blitz Report, the value passed is not significant. The Blitz Report query has been modified to retrieve the cost group instead.

3. Category Organization parameter which was dependent on the Cost Group parameter.

The LOV for this parameter has been changed from an Oracle LOV to a custom LOV and the LOV query modified to change the where clause:

from
and ccg.cost_group_id = :$flex$.CST_SRS_PAC_COST_GROUP
to
and xxen_util.contains(:$flex$.cost_group,ccg.cost_group_id)=’Y’

this takes account of the fact the Cost Group parameter may have multiple values

Other Changes made to the report:

1. The Report Option (Summary/Detail) parameter has been hidden.

The report will always run in detail mode and the use can now select the output content through the available Detail or Summary Templates:

2. When run in detail mode, the header level cost and value columns are included against  the first row for each item only. They are not repeated against each detail row. This will allow users to build pivots on the dataset without any aggregations against the header level costs/values being overstated which they would be if they are repeated on each line in the report.

I have only been able to do limited testing of the report due to the fact that we do not have much available data in our demo instance. I have verified the report reconciles to the standard oracle report. But I have not been able to any volume testing to verify the performance is ok etc.

Please review and let me know if this satisfies your requirements.

Kind Regards,

Eric