Scribd
Upload
69 views

Creating Reports Using Java

This document discusses creating reports from a spreadsheet that logs errors encountered during nightly batch processing. The spreadsheet contains details of issues that occur with batch jobs run by various Retek applications. The goal is to build a tool that can quickly generate reports extracting specific information from the spreadsheet like errors for a particular application or job failures after a certain date. This would help reduce time spent resolving repeated issues by maintaining a history of problems and solutions.

Uploaded by

Ramamurthy Arts
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
69 views

Creating Reports Using Java

This document discusses creating reports from a spreadsheet that logs errors encountered during nightly batch processing. The spreadsheet contains details of issues that occur with batch jobs run by various Retek applications. The goal is to build a tool that can quickly generate reports extracting specific information from the spreadsheet like errors for a particular application or job failures after a certain date. This would help reduce time spent resolving repeated issues by maintaining a history of problems and solutions.

Uploaded by

Ramamurthy Arts
Copyright
© © All Rights Reserved
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 18

CREATING REPORTS

USING JAVA
by
ABARNA
JAYARAM

INTRODUCTION

Retail stores throughout the continental U.S. might


require its online systems to be available from 8 AM
Eastern Standard Time, when its East Coast offices
open, until 9 PM Pacific Standard Time, when its
West Coast stores close.

Hence, nightly batches are run in their non-business


hours. While batches are running, if an error occurs
with a batch program, administrator/support
personnel must correct the error and manually rerun
the entire or part of the batch program that failed.

OBJECTIVES

The main purpose of our project is to extract


information from a Spreadsheet which contains all
the errors encountered during RMS nightly batch by
searching through the spreadsheet for specific error
or for specific program that failed earlier and to
generate a short report quickly.

This is necessary as the spreadsheet acts as a


database containing huge amount of issues
happening in the nightly batch. This project will act
as a tool to extract information from the
spreadsheet and will produce a report based on the
requirement.

LIST OF TOPICS COVERED

Overview of Batch Processing


Brief explanation of Retek Applications.
Flow Diagram.
Overview and brief explanation about GMTN
Production spreadsheet
Sample list of reports that can be generated.

BATCH PROCESSING

Batch Processing
Batch processing is the execution of a group of
batch programs (jobs).
The results are returned without user intervention.
Batch programs are commonly used for the
following reasons:
To process large volumes of transaction data
To interface with external systems
To perform internal maintenance

RETEK APPLICATIONS

Retek applications play a major role in streamlining the


process, controlling the data, performing activities that
pertain to business needs.

The integrated Merchandising batch schedule combines


the batch modules for the following Retek applications:
Oracle Retail Merchandising System (RMS)
Oracle Retail Price Management (RPM)
Oracle Retail Demand Forecasting (RDF)
Oracle Retail Data Warehouse (RDW)
Oracle Retail Integration Bus (RIB)
Oracle Retail Distribution Management (RDM)
Oracle Retail Invoice Matching (ReIM)

RETEK APPLICATIONS (CONT..)

RMS:
Oracle Retail Merchandising System is used to execute
core merchandising activities, including merchandise
management, inventory replenishment, purchasing,
vendor management, and financial tracking.

RDF:
Oracle Retail Demand Forecasting system enhances the
retailers supply-chain planning, allocation, and
replenishment processes, enabling a profitable and
customer-oriented approach to predicting and meeting
product demand.

RETEK APPLICATIONS (CONT..)

RDW:
Oracle Retail Data Warehouse (RDW) organizes and
standardizes data so that it can be stored in a consistent
format in the data warehouse. RDW provides a place for
efficiently storing and analyzing information.

RDM:
Retek Distribution Management (RDM) is an N-tier, Webarchitected warehouse management system. RDM
streamlines the supply chain for multi-channel retailers,
including stores, catalog, and e-commerce retailers. RDM
also supports consumer-direct fulfillment capabilities,
moving merchandise both to and from the customer faster
and at a lower cost.

FLOW DIAGRAM

OVERVIEW OF GMTN PRODUCTION SPREADSHEET

GMTN Production spreadsheet is used to


record issues and resolution steps taken to
solve issues encountered in the RMS nightly
batch.
The main purpose of documenting the issues
in the spreadsheet is to reduce the amount
of time in solving the same issue if it occurs
in future and also to check if the issue has
happened before or not. This sheet serves
more or less like a history.

COLUMNS IN THE SHEET

Issue Date (mm/dd/yy)


Application Name
Chain
Job Name
Error Msg
Fix Details
Fixed By

COLUMN DESCRIPTIONS

Issue Date:
This column holds a date value. This is used to record the
date on which the issue occurred.

Application Name:
The integrated Merchandising batch schedule combines
the batch modules in various Retek applications such as
RMS,RDW, etc.

Chain:
This column holds string value. All the modules are
enclosed in a chain and all the chain are enclosed in
another chain (For eg: RETEK_RMS_BATCH- The main
chain on which all the other chains and modules are
scheduled).

COLUMN DESCRIPTIONS
(CONT..)

Job Name:
This column holds string value. This column holds the job
name which got aborted.

Error Message:
This column is a string column. This column holds the
error message for the aborted job. There are different
types of error that can happen as listed below:
Oracle standard errors (for eg, ORA-1403).
Connectivity issues with the client terminals.
Process-oriented errors (for eg, eways down).
Permission issues (for eg, DB issues).
Source Code issues.
Issues with the input file sent to the modules.

COLUMN DESCRIPTIONS
(CONT..)

Solution to each error may differ. Here the question arises


who solves the error. A support personnel need to monitor
the batch and give fixes to the error that they could and
record them on daily basis.

Fix Details:
This column holds a string value. For every aborted job,
there should be steps taken to solve the issue. So this
column holds the resolution steps taken for the aborted
job

Fixed By:
This column holds a string value. This includes the details
who exactly fixed the issue like client /support person.

FUTURE ENHANCEMENT
Sample reports that can be generated from the sheet:

Print the last occurrence date of a particular error.

Print different source of the resolution taken for a given error and
how many times each of them solved it.

Find how many errors occurred in a particular application?

Number of times a particular error occurred after a particular date?

Given the input file, ignore the duplicate entries in the file and write
the output to a new file.

Print the report stating the name of the application and how many
different programs aborted in each of the application?

CONCLUSION

The primary goal of this report is to extract


information easily from a spreadsheet and also to
reduce the amount of time in solving the repeated
issues by maintaining perfect issue logs and
extracting information in no time.

A support person can build this tool and can share it


with client stating it as enhancement that is done
from their end to extract information easily.

Queries???

THANKS FOR YOUR


ATTENTION

You might also like