Order To Cash Process

Application Handbook
Oracle Applications - Order to Cash

Order To Cash Process

Document details
File Location/Name
Current Version:
Original Author:
Date Created:
Last Updated By:
Date Last Updated:
Approved By:
Approval Date:

Order To Cash Process

Revision History
Version
Number

Date Updated

Revision Author

Summary of Major Changes Made

0.1
1.0
1.1

1.2
1.3
1.4
1.5
1.6
1.7

ii

Order To Cash Process

Table of Contents
1. Introduction.....................................................................................1
Business Overview............................................................................................................................ 1
High Level System Flow Diagram...................................................................................................... 2
Overview............................................................................................................................................ 3
Business Flow Diagram- Order to Cash Cycle...................................................................................6
Order to Cash Cycle........................................................................................................................... 7
Key system user roles and privileges............................................................................................... 52

2. System Details...............................................................................53
System Flow Diagram...................................................................................................................... 53
Database Schema........................................................................................................................... 54
Test Plans and Cases...................................................................................................................... 56

3. Technical Processes........................................................................57
Software Configuration..................................................................................................................... 57
Environments................................................................................................................................... 58
Naming Conventions........................................................................................................................ 59
Coding Standards............................................................................................................................ 59
Test Procedures............................................................................................................................... 60
Job Scheduling / Sequencing of Batch Jobs....................................................................................60
Transaction Volume / Data Volume.................................................................................................. 60
Month End / Quarter End / Year End Processing.............................................................................61
Release and Deployment Procedures..............................................................................................61
Change Request Procedure............................................................................................................. 62
DBA activities................................................................................................................................... 66
Escalation Procedures..................................................................................................................... 66
Communication Procedures............................................................................................................. 66
Archiving / Purging Procedures........................................................................................................ 66
Application Support Activities........................................................................................................... 67

4. Tools and Utilities...........................................................................68

5. User/SME Contacts..........................................................................69
6. Application Support History............................................................70
Calls and Resolutions...................................................................................................................... 70
Common Problems and Resolutions................................................................................................70

7. Document Inventory.......................................................................71
APPENDICES.......................................................................................73
Attached is the list of components/customizations covered in the Transition...................................73

Glossary.............................................................................................74
Business Terminologies................................................................................................................... 74

iii

Order To Cash Process

1. Introduction
Oracle E-Business suite is an enterprise platform used at Kronos for financials, quoting, procurement
and manufacturing functions. The suite is currently integrated with Vertex for tax management and Optio
reporting tool for producing customer invoice documentation. Outside of these integrated solutions Kronos
also uses ADI/ Web ADI for financial reporting. Oracle E-Business suite is also integrated with other third
party applications via web Methods, Informatics or direct connection for data exchange for transaction
consistency and processing as well as reporting and analytics

Business Overview
Following are the list of modules being used.
General Ledger
Account Receivables
Order Management
Inventory
BOM
Service Contracts
Oracle Quoting
Oracle Install base
Cash management
XML Publisher

Note: The above modules are included in Order to cash cycle and system setup or installation will not be
part of the

Order To Cash Process

High Level System Flow Diagram

Standard integration between Oracle Modules at Kronos

Order To Cash Process

Overview
Brief description of Integration with other systems
Kronos uses number of other off the shelf and custom developed application to manage various business
operations. Most of them have integration with Oracle applications either as point to point interface or
using Webmethods Enterprise service bus. Following is the brief descriptions of the important interfacesAGILE to Oracle Inventory

Kronos has Oracle manufacturing modules up and running as they were used to manage companys
manufacturing operations. However, Kronos manufacturing operations have been outsourced in the
recent past. As a result, the manufacturing modules like BOM, MRP, WIP, and Quality are no more in use.
The only manufacturing modules that are in active use are inventory and costing.
The manufacturing vendor maintains the item records in AGILE. The items are then interfaced to Oracle
inventory as finished goods. The costing is done at the standard purchase price. WIP is maintained by the
vendor and not interfaced to Oracle.

Contracts Install Base and AR to AMDOCS

AMDOCS is a customer service tools developed on Oracle platform. The tool is heavily customized.
There is a possibility that some of the customizations developed on clear basic tool might have to be
redeveloped on Java. Customer information is interfaced to AMDOCS however contract details remain in
Oracle and AMDOCS access them as a view.
AMDOCS receives customer contract details from Oracle Contracts and Install base. Invoice
confirmations are also fed back to AMDOCS.
Apart from that there are two other interfaces from AMDOCS-

Order To Cash Process

Inquira which is a knowledge management tool used by the customer service team and
integrated to E-case
Ecase- Custom developed (in-house tool) based on .net for customer issue tracking.

Data flow (Inquira->E-case->AMDOCS)

Scope: From Oracle perspective The interface between Oracle and AMDOCS.

Changepoint to Oracle

Changepoint is a PSA automation tool based on Windows/SQL server and used by professional service
group for project engagements. Kronos is Planning to replace Changepoint with Open-Air. The project is
currently in testing phase with planned go-live of November 2011. Changepoint sends Invoice and credit
reports to Oracle using Webmethod.
The tool has similar functionalities as Oracle projects with project management functions and Financials
functions. Project related invoices are created in the changepoint system and interfaced to Oracle using
auto invoicing. Invoice number confirmation is sent back to Changepoint.
Great Plains to Oracle

Great Plains is the Microsoft based ERP system used for international subsidiaries of AUS, NZ, MEX and
UK. Monthly Trial Balance from Great Plains is loaded to Oracle using standard Oracle interface. Item
cost and currency information flow back to Great Plains.

Order To Cash Process

Axapta to Oracle

Axapta is the ERP system used for Eastern Europe. Monthly Trial Balance from Axapta is loaded to
Oracle using standard Oracle interface. Item cost and currency information flow back to Great Plains.
Oracle to Varicent

Varicent is .net based sales and commission application. Sales data is interfaced from Oracle and other
systems to Varicent. The commission calculation takes place with Varicent. Varicent then interface the
commission data to Payroll for payment processing.
Knowledge Pass to Oracle

Knowledge pass is another customer database that maintains pricing information. Pricing modifications
are sent periodically to Oracle.

Order To Cash Process

Business Flow Diagram- Order to Cash Cycle

Below diagram shows the flow for order to cash cycle. The quotes are created first. Once we place order
from quotes, order is created in order management and depending upon the warehouses and items it will
be auto shipped. Once the shipping process is over then Invoices can be created in AR and if the orders
are having service line then service contract will be created.

Order To Cash Process

Order to Cash Cycle

Business Flows and Customization

1) Oracle Quotes: - Quotes are created for customers where user will select the contract
number in header DFF. They will enter the items and the license if its a software line. They will
price and then approve the quote.
Flow diagram for Oracle Quotes

Order To Cash Process

There are two personalizations in this module. To display the default currency for the
operating unit and zoom is enabled to create the contracts.

There is form customization also done on quoting form.

o

Quoting Gross Margin Calculation and DFF population: - A DFF was created
(ASO_QUOTE_LINES_ALL.Attribute7) to store and display the gross margin
value of the quote which can be viewed by the sales persons which is helpful in
calculating commission. Zoom function is enabled to calculate gross total for the
quotes.
Solution: - A before Insert or Update trigger kron_aso_qute_ln_all_iu_trg is
written on ASO_QUOTE_LINES_ALL which will calculate the Gross Margin and
populate the same into the DFF Attribute7. The zoom function enabled on the
toolbar on the Quote form, when user clicks on this they see first message as
Quote will be saved before it displays the Quote Header Gross Margin Amount.
On clicking OK it saves. After that a message with Total Gross Margin Amount
Estimated = xxxx will be displayed on the screen for the user.
Flow Diagram for Quoting Gross Margin Calculation

Order To Cash Process

Quotes header payment term: - The standard functionality doesnt have

payment term for each line in quoting form. But as per the business in Kronos it
is possible to have multiple lines having different payment term. For this purpose
DFF is defined at line level to hold the payment terms. Attribute1 in
ASO_QUOTE_LINES_ALL was the DFF created to store the payment terms at
line level. Whenever the user enters or updates the payment term at header level
then it should populate the DFF at line level.
Solution: - To achieve this one trigger is written
KRON_ASO_PAYMENTS_IU_TRG.

Exclude all ADP Customers from Customer selection when entering quotes
and in quote search: - The requirement was not to list the ADP customers in
Quotes header screen and Quotes search screen.
Solution: - If the sales channel = ADP the customer list will not show the ADP
customers. Modifications were done to the custom form KQOTHDDET.fmb and
KQOTUNSRH.fmb which is copy of standard quote form standard quote form
respectively

Order To Cash Process

On Quote search form the Customer and Account LOVs for ADP customers will
get populated. When user enters the Customer name or Account name the
custom code written on the form will check if it is related to ADP customer, and if
it finds the match then throws an error (Account Not Found) else it will continue
with further process.
On Quote Form the Customer and Account LOVs for ADP customers will get
populated. When user enters the customer name or account name the custom
code will check if it is related to ADP customer, and if it finds the match then
throws an error else it will continue with further process.
Flowchart for excluding the ADP Customer

Quote Service Items Filter: - When user is entering quote with the products and
the item flagged as Serviceable then the user can attach a maintenance item to
the product purchase. For this user has to click on Add Service Item which is
displaying all the service items instead of displaying the service items related to

10

Order To Cash Process

the purchased product. The requirement is to display the service items only
related to the purchased product.
Solution: - Custom code is written in the KQOTHDDET.fmb form which is the
customized form from the standard quoting form QOTHDDET.fmb. With this
change user enters the product in the quote form, clicks on Action Button , clicks
on Add Service Items , the Service Items LOV for the entered product will get
populated and displays to the user.
o

Default TAX Handling to STANDARD: - While converting a quote to order there

is a check imposed to verify if tax handling in the quote header is set to
standard, if this fails then one message is displayed. This is done by validation
template.
Solution: - A new procedure CHECK_TAX_HANDLING was created in existing
package KRON_OM_LINE_PKG. When quote is converting to order the
validation (Order Source = Order Capture Quotes and Tax handling field =
Standard) takes place in the Oracle processing constraints and the validation
template Kronos Tax Handling.
Flowchart for Tax handling Customization

11

Order To Cash Process

Copy Quote:- While copying the quotes few fields are set to null i.e. Header
sales credit , Line Sales Credit, Header Salesperson, Sales group , header
contract template, header attribute6(Upgrade type), header
attribute11(Opportunity ID), header attribute12, header attribute8(Internal note),
line attribute15(hardware upgrade), header freight terms, PO number, payment
details(Payment term, credit card information) shipping information. When
Salesperson is entered or changed then Territory will be defaulted or changed
automatically
Solution: - Created custom library KQOTCMCPQ.pll from seeded library
QOTCMCPQ.pll and custom form KRON_QOTCMCPQ.fmb from seeded form
QOTCMCPQ.fmb. Attached the custom library to the custom form. Four
procedures written in the custom package KR_QOTCMCPQ_FIELDS (copied
from seeded package QOTCMCPQ_FIELDS). Four Procedures written in the
package KR_UPDATE_NEW_QUOTE_PKG which will be called from Library
procedure KR_QOTCMCPQ_FIELDS.OK_BUTTON.
Procedure DO_UPDATE has three procedures called.
DELETE_CONTRACT_TEMPLATE: Deletes record link quote to contract
template usages
UPDATE_NEW_QUOTE: Has API to null out quote header attributes, contract
template, shipment attributes, payment details, PO number, and line_attribute15.
UPDATE_LINE_SHIPMENT: Has API to null out Line Shipment freight terms and
ship method

12

Order To Cash Process

Flowchart for Copy Quote Customization

13

Order To Cash Process

Setting Service Start Date and End Date to Null in Quote to Order: - The
service start date and service end date are set to null while creating the sales
order from quotes.
Solution: - A Before Insert trigger KRON_NULL_START_DATE is created on
OE_ORDER_LINES ALL which will set the Service start date and End date to
NULL when record gets inserted into the Order Lines table.
Flowchart for Null out the service Dates

14

Order To Cash Process

Customer Deposits: - As per this customization 35-50% of quoting value

amount is taken from the customer at the time of creating the quotes. This is
done to increase the cash flow and to minimize the risk from the unknown
customers or customers with bad histories.
The requirement was given by the business is to create a DFF at Quote Line to
populate deposit amount (Attribute11) and it should be calculated depending
upon the percentage set at customer level. The lines Deposit Amounts should be
summed up and update the Quote Header Deposit Amount DFF (Attribute 13).
When Order is created from Quote in AR the Deposit AR Transaction should be
created for the deposit amount of the order/quote.
Solution: - A Before Insert or Update trigger
KRON_ASO_QUTE_LN_LL_IU_TRG is created on ASO_QUOTE_LINES_ALL
which gets the payment term and currency code from quote header, gets the item
type and item number for quote line. A function
KRON_QUOTING_PKG.CALCULATE_DEPOSIT_AMT is called which calculates
the deposit amount and updates the quote line deposit amount dff(Attribute11).
Another before insert or update trigger KRON_ASO_QUTE_HDR_ALL_IU_TRG
is created on ASO_QUOTE_HEADERS_ALL which will sum up the deposit
amount of all the lines and updates the data into the Quote Header Deposit
amount DFF.
In order to create the transaction in AR automatically the custom process
KRONOS_ORDER_FLOW is created in the Order Header Workflow which gets
kicked off when the quotes gets transferred to the Order Management by clicking
on the Place Order button from Quoting Screen. Detailed information is
available in Quoting Customizations document.

Flowchart for Customer Deposits Customization

15

Order To Cash Process

16

Order To Cash Process

Line Level Payment Terms from Quoting to OM: - Whenever user converts
Quote to an Order in standard oracle functionality there was no facility to take the
Quote line level payment terms to the Order Management from Quoting.
Solution: - To achieve this requirement DFF (attribute1) was created at Quote
Line level to store the payment term. Also a defaulting rule is created with pl/sql
function as source which will return the DFF value to the defaulting rule which will
populate the line level payment term field on an Order Line in Order
Management.
Package: KRON_OM_LINE_PKG. GET_QUOTE_LN_PMT_TERM

Auto-Populate Pricing Attribute DFF on Order and Quote Line: - Kronos will
be entering the number of licenses/seats in pricing_attribute1 in Quotes and
order management module. The DFF is created on the quote lines to display this
value. It should have same values as defined in pricing_attribute1 so that user
doesnt have to go to pricing attribute form. This was the first requirement and the
second requirement was whenever the user adds any new lines to order or
changes the pricing attribute then the DFF will not updated automatically. So
Kronos wanted to develop extension to keep pricing and order lines DFF in sync.
Solution: - A custom code is written in the Quote form to update the Quote Line
Attribute4 with the Pricing_Attribute1 when ever user updates it. A custom
Before Insert or Update trigger KRON_ORDER_LN_PRC_ATT_IU_TR is written
on OE_ORDER_LINES_ALL. This will fire before the user inserts or updates the
quote line record which will retrieve the Pricing_Attribute1 from the Order Pricing
Attributes table (OE_ORDER_PRICE_ATTRIBS) based on the order_id and
line_id. And then the value of Attribute4 will be updated with the retrieved
Pricing_attribute1.

Check ADP Migrate: - The custom function check_adp_migrate is written to

checks whether the customer belongs to ADP
(hz_cust_accounts.sales_channel_code =ADP) and returns T or F. If it is true
then pricing modifier set in the Quoting/Order Management will be applied else
Pricing modifier is ignored.

17

Order To Cash Process

o

Quote Header Validation of Account Site Addresses: - Allow only Account

numbers which has exactly one active party address with exactly one active
Account address set up in Operating Unit. Upon populating the default addresses
which meets the above requirement, the validation of the Operating Unit should
be done when the Form is getting saved. The data in the addresses LOV should
be modified so that only the rows related to OU should be displayed. Add Party
ID and Account ID information to the Addresses LOV. Add Customer Code field to
the Quote Header section
Solution: - Added a trigger on SOLD_TO_CUST_ACCT_NUMBER item. Based
on the account number entered it checks whether the a/c number exists and is
active in the table HZ_CUST_ACCOUNTS and throws error if not found.
Validations were written to validate the OU as below,
Save (Form Trigger: KEY_COMMIT)
Exit form (Form Trigger: KEY_EXIT)
Tab change (Form Trigger: WHEN_TAB_PAGE_CHANGED)
Place Order button (Block Item Trigger: WHEN_BUTTON_PRESSED)
View Quote Version button (Block Item Trigger:
WHEN_BUTTON_PRESSED)
Added OU: Site Number: Party Name to Quote To, Bill To and Ship To LOVs to
display only those usages found in the OU.
A new field KR_ACCT_CLASS_CODE is added to the canvas
QOTHDDET_MAIN on the quoting form. Class Code values are added to the
LOVs QOTHDDET_SOLD_TO_ACCOUNT and
QOTHDDET_SOLD_TO_CUSTOMER

Quote Create Service Contract Details for Order Lines: - The requirements
given was to convert the Contract number DFF on Quote Header to LOV. When
user clicks on PLACE ORDER on the Quote form then update the Service
Contract Details. If the Order is an upgrade order type, DFF is not null, contract
number is not valid or Order includes extended warranty then apply Kronos
Contract Review Hold. Allow orders that are between $0 and $10,000 and do not
include any s/w line items then bypass the Kronos Review Hold.
Solution: - A view KR_QUOTING_CONTRACT_LIST_V is created and based on
this table value set KRON_QUOTE_CONTRACT_LIST is created which was
attached to the Contract number DFF.
After Order is created successfully the procedure
KRON_QUOTE_CUSTOM.CREATE_OKS_ORDER_DETAILS is called which will
create records in the table OKS_K_ORDER_DETAILS

18

Order To Cash Process

2) Oracle Order Management: - The main source of orders is from quotes. Quotes are
converted into order and contracts are created. Contracts are also for service items. The header
and lines workflow has been customized as per the Kronos business requirement.
Flow Diagram for Order to Cash

Items are fulfilled from different warehouses(1A1 = Autoship, 1C1 = Jabil Chihuahua Mexico, 1R1
= Jabil Louisville Kentucky )

Orders and lines workflow customization:-

19

Order To Cash Process

o

Orders are put on hold as per condition set in the workflow

Item type = PSA then by pass AR interface

Autoship workflow for 1A1 items. These items are picked and shipped.

The order number + 6 digits get populated in DFF of order headers custom table and
Serial number in lines custom table.

Customization is done to prevent the lower case serial numbers during shipping.

Ship confirm API is used by Jabil Chihuahua and FedEx to update the freight details of
the orders.

APD orders are interfaced using Webmethods. The data is in .txt file which is mapped with
columns of the staging table.

Ceridian alert: - This is alert defined to inform the end user that the order has been processed.
This alert is only for the items defined in specific valueset.

The pricelist used are Corporate USD, Corporate CND and Corporate ADP. Manual price
modifiers are also available to override the price for giving discount. Automatic modifiers are also
available to apply the freight charges and to apply handling charges based upon the shipping
organization.

Customers are directly entered in oracle applications. One account should be linked with only one
address. If there is any change in customer address then new account can be created making the
older one as inactive.

COGS Workflow:- Kronos has modified the cost of goods sold workflow as per their business
requirements. The standard functionality of the delivered COGS Workflow only takes the COGS
account for orders from the Items Cost of Sales Account
The Cost of Goods workflow will be customized to add the necessary conditional logic to retrieve
the different segments of the COGS account from the appropriate places.

20

Order To Cash Process

Flow chart for COGS workflow logic.

21

Order To Cash Process

In the above process following are the custom processes.

1. Kronos Is the sales order an Intercompany Order: - This process calls the package
KRON_COGS_WF_PKG.CHECK_IS_ORDER_INTERCOMPANY. One independent
value set is defined and code is checking the order types there for the intercompany
sales order.

2. Kronos Get Intercompany Salesrep Id: - For Intercompany salesrep id is assigned as

-3.
3. Kronos - Get CCID From Intercompany Trx Type: - The program is picking
cust_trx_type_id from mtl_intercompany_paramters table. Based on shipping
organization and operating unit.

Order Header Workflow: - As a part of business requirement Kronos wanted to place every
order on hold. The orders can be processed further for shipping and invoicing once it has
been reviewed by Kronos users. The holds will be applied on the orders once it has been
booked.
Automatically create AR Deposit Transaction in Accounts Receivable for quotes that have a
deposit amount when the Quote is converted to an order.
Prevent Sales Order header from closing until all associated repair orders related to source
service request have a status not equal to Entered. Changes should not impact Depot repair
orders created directly in Order Management (not in Depot Repair)
The order will be placed on different types of holds depending upon different criteria or logic:1. Kronos Contract review hold:

If the order contains any extended warranty. Extended warranty can be

identified if the orders are having any item starting with EXT.

22

Order To Cash Process

If attribute7 of header attribute is not null

2. Kronos review pending hold:-

If there are any lines on the quote where segment1 of the Sales Reporting
Category = SFW. The amount range held in
KRON_OM_HLD_REV_PEND_TYPES will be evaluated only if there are no
items with SFW on the quote.

The acquisition value (HZ_CUST_ACCOUNTS.ATTRIBUTE1) of the sold to

customer on an order is included among the values in the value set
KRON_OM_HLD_REV_PEND_ACQS;

The order includes a line whose item number is included among the values in
the value set KRON_OM_HLD_REV_PEND_ITEMS

Order Line Workflow: - Following are the list of customizations applied on order lines
workflow.
1. Update order lines of the same organization that do not have a setup with a ship set
id if the line does not meet the following criteria:
Line is auto shippable
Line type of OPTION nor SERVICE,
Line has a scheduling level of ONE
Line Sales Channel Code = ADP
Depot Order
2. Lines will be processed further once the header holds have been removed.
3. Freeze the pricing, if the order is originated from quoting module.
4. Once the line is shipped/fulfilled, check should be done to verify if the whether the
line was shipped from a previously defined ADP inventory. If so,
Pricing attributes associated with the line should be deleted.
Reprice the Line.
5. After order Line is Shipped/Fulfilled, based on order types and item types, there is a
need
to generate unique License Authorization Code and Serial Numbers in the
Globetrotter.
1. If the ordered items type is Software License and its License Method is 1 Globetrotter, then perform following functions

Generate one unique License Authorization Code for the entire sales order
using format 1234567-XXXXXX where, 1234567 is Order Number &
XXXXXX is 6 digit sequence generated number Insert the License
Authorization Code in the Order Header Attribute5 (DFF)

23

Order To Cash Process

Generate a unique serial number for each of the ordered quantity of the
license item and store each serial number as a row in a custom table,
keyed by order_line_id using format GXXXXXXX Where G= Globetrotter
prefix & XXXXXXX is 7 digit sequence number Insert line_id, serial number
values in custom table
Proceed to the Invoice Line function.

2.
If the License Method is NOT Globetrotter, then proceed to Invoice Line
Function. No other custom integration is then required.
6. If the order lines source is PSA, then invoice integration will be bypassed or invoices
will not be created for those orders.
7. If line is an auto shippable org, currently only 1A1,if so auto pick/release, ship/confirm
line if either of the three scenarios exist:
No order lines exist for trigger organizations, currently only 1M1.
If trigger items exist, auto ship only when one trigger item ships.
The order is an ADP order.
Warning Freight rating failed for trip is permissible for
auto_ship_confirm_delivery procedure.
For debugging purpose kron_debug is the table created by Kronos. Messages are
inserted into this table.

Open AR Conversion acquisitions: - The program is developed to categorize the

customers. The different categories are SOLUTION ID, SOLUTION ID ACQUSITION and
SOLUTION ID HW.
Solution id: - A customer account having or owning at least one active CORE SW part can
be considered as a Kronos Solution.
Solution HW: - Customer owning at least one Kronos hardware can be considered as
solution hardware.
Solution id acquisition: - Customer who has solution id and its acquired by Kronos then in
that case it can be classified as solution id acquisition.
The program is nightly scheduled program which runs every day and classifies the customers
in different categories. The program will pick all the customers having sales_channel_code =
DIRECT and ASP_CUSTOMERS and classify as per below condition

24

Order To Cash Process

Old Class Code

New Class Code

Criteria

Null

SOLUTION ID

If sum of Core > 0 or

potentially core > 0

SOLUTION ID

SOLUTION ID

SOLUTION ID
ACQUISITION

SOLUTION ID

If sum of core > 0 or

potentially core > 0

SOLUTION ID HW

SOLUTION ID

If sum of Core > 0 or

potentially core > 0

If sum of core > 0 or

potentially core > 0

There is one DFF setup at product family category in which we have multiple values like
Core, Non Core and potentially core depending on which the program checks and classify the
customers.

HZ_CUST_ACCOUNT_V2PUB.update_cust_account api is used to update the

customer_class_code column of hz_cust_accounts table.
There is one log table (XXKRON.KRON_SR31318_LOG) defined for this process. The
program cleans the table before run and inserts the data into table during run.

ADP order import integration: - The Webmethods integration is done which reads the file n
FTPs to the web methods integration server and put the data into oracle interface tables.
ADP sends their files to Kronos Tumbleweed. Tumbleweed then puts these files to
directory\\p2ftp\USADPOrders and one scheduled web methods program will copy these
files to APD integration server.

25

Order To Cash Process

Web methods program keeps on polling and as soon as it finds the data file. Web method
program reads the data and transfers data to custom staging table
(XXKRON.KRON_ADP_ORDERS).
The PL/SQL program is called which will pick the data from custom table and puts the data
into order import interface tables.
Users are notified by email (ADPOrderImportUsers@kronos.com) if the file is successfully
processed or if the file had been already imported.
Once the data is imported then the file is archived in archive directory.
The ADP generates different types of files. ADOORDT_yymmddhhmiss.txt,
ADOORDZ_yymmddhhmiss.txt, ADOORDE_yymmddhhmiss.txt,
ADOORDW_yymmddhhmiss.txt.
The package KRON_ADP_ORDERS_IFACE_PKG creates records from custom table to
order import interface tables (OE_HEADERS_IFACE_ALL, OE_LINES_IFACE_ALL and
OE_PRICE_ATTS_IFACE_ALL).
File Identifier:-

1ADP

Identifier
200507

Order Header

1ADP

200507201625

220050614030-KEV 030T030KEV
TEMPUS RESORTS INTL
SAND LAKE ROAD
SUITE 600
ORLANDO
32819 KATHY CUSTER
4072260436 G 170924 N3

7380
FL

3T030KEV
0018600615-429 TIMECLOCK 440 BASIC 512K
(LEAS000000009
000000000000000000L
Order Detail

3T030KEV
0028600947-002 TIMECLOCK 400 ETHERNET KIT
(LE000000009
000000000000000000L

Trailer
9000008900000270000060

The interface process will pick trailer records (order type = 9) in custom table having
interface_status = New. It will then sort by order_type, file_date and file_time. The program
will loop through headers and retrieve the lines and crate record in lines interface table. If the

26

Order To Cash Process

orders line contains SFW product line then it will create records in interface price attributes
tables also. Once the data is created in interface table then interface_status is changed to
Interfaced
Kronos ADP Order File Report will be send to the users to notify that file has been processed
or errored out. After that users can go to the order management and run the order import
concurrent program to import the order in order management.

27

Order To Cash Process

3) Oracle Install Base

Mass edit Functionality: - Oracle seeded install base mass edit functionality was
modified as Kronos IB Mass edit functionality where user can apply notes to multiple
records which is required. This functionality was missing in standard form. The form used
for the new functionality is read only. User is able to search on request number, account
number, customer name. We can export all the details in excel from this form.
An Oracle framework form has been developed for mass update functionality. The
request for mass updates comes from SharePoint. The form is filled at SharePoint and
through web methods integration data comes to Oracle.

Once the data is loaded to oracle, requests are in submitted status. Once it has been
assigned to employee, then status changes to Assigned.

Employees reviews the requests placed by the customer to change the notes and status
of the IB. If they find the notes or status valid then they can accept the request otherwise
reject it. Once the user accepts the request by clicking submit button in the form then
concurrent request is fired at backend which will update the notes or status of IB.

28

Order To Cash Process

If there are many items in the form and user wants to update the common notes to all of
them then he can use the facility given in the form to update. The user can select all the
items and type the common note in new IB note and click on copy to selected. In the
same way new status can also be applied to multiple items.

Kronos Unbundle IB:- There was one problem that individual item instances were not
created for a bundle item. So it was difficult to track the instances for service. So no item
instances were tracked for service, process repair depot. To overcome this one
concurrent program was created Kronos Item Unbundle, this program creates item

29

Order To Cash Process

instances for each serviceable item in a bundle. Two validations used in this program are
item instances must be unique and original service contract should not on QA hold.

The program accepts solution_id as parameter and depending upon the solution_id,
instance_id is populated in instance_id LOV.
This program calls the kr_unbundle_ib.do_it package. It unbundles the bom assembly
and update the same in contract also and expire the bom assembly for e.g.
IB(Before unbundle)

CONTRACT (Befor

IB (After unbundle)

e unbundle)

Part 123
a. Clock
(Primary
Item)

unbundle)

Service Line

Part 123(expired)
a. Clock
(Primary
Item) 456

Sub Line
123

b. Touch Pad
c.

CONTRACT(After

b. Touch
Pad - 789

Item 3

c.

Item 3 999

Service Line
Sub Line
123(expired)
456
789
999

For every new items created by the package, old items or original item reference will be
copied to EXTERNAL_REFERENCE column. We can find the original item in the DFF
(Ordered item field).

The pricing attributes for the install base represents the license capacity that was
purchased and the license type. Initially there was no option to create the pricing
attributes for the parts in install base; this was manually entered whenever any
acquisition happened. But later on one concurrent program Kronos Install Base Pricing
Attribute Create which will take IB Number and Number of licenses as a parameter and
updates the price list if pricing attribute does not exist and product is valid in Corporate
USD and Corporate CAD price lists.

30

Order To Cash Process

One Concurrent program was created to expire or to end all the non serialized install
base instances that are created by depot shipments and whose receipts are created.

Whenever Create item Instance event occurs from order management and Kronos
Leasing is identified as bill to then one function is written to update the bill to with bill to
account associated with the instance owner.
If more than one party site for an account is found, the Active party should be
selected.
If more than one Bill-To Usage is found for the Owner Account, the Active,
Primary usage should be selected.
If the Bill-To Usage(s) for the Owner Account is Inactive, the Bill-To should NOT
be updated
If there is no Bill-To Usage (Active or Inactive) defined for the Owner account,
create the usage Bill To and update it on the instance. (Note: All required data for
the new usage must be set to match the Ship to usage i.e. House Account Rep must
match the Ship To House Account Rep. Also, ensure that the Profile flag is set.

In above picture, Kraft Foods has been entered as a different party and each party is
having only one active account, bill_to and ship_to.

Kronos Expire Non-Serialized IB Created by Depot Shipment: - When a depot order

is processed for non-serialized products, new, additional IB instances for the products are
created. These shipped products are not and should not be added to the customers
contract and increase the number of products in the Installed Base that the customer
owns. The install base for a customers should show only items which they really own.
So we need to change the status of extra products to Expired.

31

Order To Cash Process

The program will Expire non-serialized IB instances that were created by Depot
shipments where the receipt was completed. The program will check following
conditions.
Both the ship and receipt lines being considered must be under the same Repair
Order Number
A customer must be identified as the Owner of the IB instance. If the Owner is
Kronos IB, it does not have to be expired because it will not be counted as a
product owned by the customer.
Shipped item must be Non-Serialized
The status of the Shipped IB instance should not be EXPIRED
The ship and return lines must be fully processed. I.e. Ship line has a status of
SHIPPED and the return line has a status of RECEIVED.
The shipped item number must equal the returned item number.
The seeded api csi_item_instance_pub.expire_item_instanceis used to achieve this
task.

32

Order To Cash Process

4) Service Contracts

Deport Repair module is implemented to automate the replacement of products which are
in service contracts. As standard replacement functionality will create a replacement
subline having all the information same as the parent and parent will be end dated as of
start date of subline. The purpose of the custom extension is to apply the replacement
functionality to contracts in Entered status. This module is directly integrated with the
Order management. There are 3 DFF setup on service request to capture the shipping
instruction, packing instruction and customer freight account. These are stored in
External_Attribute_4, External_Attribute_5 and External_Attribute_6 respectively.

The information from Install Base and Service Contracts is available for Global Customer
Service support team as a VIEW which will quickly helps in knowing the details of the
product (eligible for Service or not etc). This VIEW is maintained in the system called
AMDOCS. AMDOCS is a system used for call tracking and customer support. AMDOCS
uses a view to Install Base and Service contracts.

The Cancellation/Reinstatement process for Renewals involves copying Terminated

contracts. When the new contract is created, the prices copy over as $0 and the
terminated amounts are also set to $0. The original prices are not available on the new
contract and as the original pricing on the Terminated contract is not readily available,
accurately re-creating invoices for these contracts would require significant manual effort.
Approximately 75 Reinstatement contracts, containing an average of 2000 lines, are
processed each month.

Copy Contract: - In order to minimize the impact of the TrueValue pricing, the copy
contract functionality is enhanced to calculate the original price of each line/subline which
inserts the prices into the newly created contract. An option on the copy contract form
was provided to calculate original prices for a contract. This will allow the business to
calculate the original pricing for Reinstatements.

33

Order To Cash Process

34

Order To Cash Process

The users want the system to automatically format the contract_modifier_number for
manually created contracts. The different types of modifier available are C- Rebill, XReinstatement and S-Subscription. The modifier should be formatted as X<DD-MON-YY
HH24: MI: SS> e.g. C18-May-11 02:46:33 depending upon the modifier type selected.

Except the Services Only contracts the same contract number is to be maintained that of
copied from contract. To maintain this one contract number modifier is added. To ensure
that the correct solution id and address are populated on the contract header, the fields in
the new contract will be nulled out. These fields will be repopulated by the programs to
update the customer account and customer addresses in contracts that are scheduled to
run on a regular basis.

QA Checklist: - Kronos has implemented some custom checks, which were added to
the standard Oracle QA Check logic. The Kronos QA Checklist must be executed in order
for a contract to move into Signed or Active status. In other words, when a contract is
opened for update, the system places it in a QA Hold status; it must then pass QA
Check in order to return to a Signed or Active status. All newly created contracts are

35

Order To Cash Process

created in an Entered status, and must pass QA Check in order to be submitted for
approval (i.e. and thus become Signed or Active). Similarly, the renewal program runs
QA Check against all contracts that qualify for renewal and the renewal contract will not
be created if theres a QA error. If the renewed contract passes QA Check but the
resulting renewal contract does not, it is created in Entered status. There were around 40
custom check lists added.

When we submit the contract for approval the custom workflow process is fired.
After approval the status changes to active and its locked for update. If you would like to
update that contract then you have to click on Open for Update button which is only
available from superuser responsibility. As soon as you click on Open for update the
contract opens in editable mode and status changes from Active to QA Hold. Once

36

Order To Cash Process

modification is done again we have to go through the QA check and status will again
become active.

37

Order To Cash Process

Custom Menu - KronosTools

KronosTools Menu Items : Renewal Checklist, Kronos Email Quote, Kronos
Rounding Tool

1. Renewal Checklist:- When we do renewal check list it will also run the renewal QA
check list and then report will be generated and it will stored as attachments. User can go
to the attachments and see the report. In the report all the errors are listed first and then
all other warning and success QA item are listed below.

Pick up the last attachments to see the results of the latest Renewal Check List run.

38

Order To Cash Process

The kronos renewal QA check list/QA checklist is defined in Service Contract Analyst US
(responsibility)-> Setup ->Quality Assurance

39

Order To Cash Process

The processes listed n above screen are defined in Service Contract Analyst US
(responsibility)->Setup->Process Definition.

Here we can call the custom process for validation.

2. Kronos email Quote: - It is the facility provided to send the contract quotes to the customers as
an attachment. It opens a form where we have to input the customer mail address and select the
template in which customer would like to receive the mail (i.e. English, French and Canadian).

40

Order To Cash Process

3. Kronos rounding tool: - It is used for rounding up the values. Price defined in pricing
sometimes has more than 6 decimal places. so summing up the line level creates a
problem when the line and header sum doesnt match. So in order to overcome this issue
rounding tool was introduced which will round off the values at product level and then to
line level in 2 decimal values and then the values are committed to the database.

41

Order To Cash Process

It submits concurrent request which can be view to know which all lines has been
rounded off.

Contract reinstatements, Contract cancellations and Service-only orders involve the

creation of a new contract within Contracts, rather than through OM Interface. To ensure
that proper approvals happen for the new contracts customizations for the oracle
standard workflow were done. The timeout value for the approvals was increased from 7
days to 30 days where 7 days was the standard functionality. Four approval levels for
renewal contracts and 2 approval levels for new contracts were set. Each of the approval
levels are authorized to approve contracts upto a specified amount.

5) Accounts Receivables: - Once the orders are shipped invoices will be created in AR.
Flowchart for AR

42

Order To Cash Process

Invoices are created in AR for the different transactions which comes from different
modules or sources like OM, oracle OKS Contracts, Customer Service, Professional
Service, Educational service and Intercompany. There are two different request sets for
Auto Invoice.
o

All Batch Source which is runs every day at evening. This is mainly for US,
Canadian and Brazil logs

Single Batch Source which runs every day during evening time. This is mainly
OKS Contracts from Canadian org.

These request sets consist of Following programs:o

Kronos Autoinvoice Preprocessor

Autoinvoice Master Program

Autoinvoice Import Program

43

Order To Cash Process

o

Kronos Invoice Line Detail Import

Prepayment Matching Program

Revenue Recognition.

Once the Autoinvoice programs are completed then Create intercompany program is run.

Every night GL transfer program runs in US, CA, AS, BZ org once the autoinvoice
program is completed. This set consists of General Ledger Transfer Program, Revenue
Recognition, Revenue Contingency Analyzer, Journal Import, Update Posting Control,
Unposted Items Report, Kronos Receivables Account Exception Report, Aging -7 Buckets
By Account Report.

Kronos is using Optio to print the invoice. Which has feature to take the input from oracle
applications and apply to the defined template and print or mail as per the requirement of
the customer. Apart from printing Optio is being used as a repository for invoices. Which
can be fetched by passing the invoice number, customer number, request id, invoice date
etc.

The invoices can be print in US English and Canadian French.

Kronos is using the auto lockbox feature with two banks Royal Bank of Canada (Canada)
and Citizens Bank (US).Webmethods is used for picking the files and inserting the data
into tables and then user receives the notification. The user queries the receipt batch and
compares the counts and counts on lockbox summary reconciliation report. Then update
the batch total and post the quick cash.

Receipts are created manually if any error occurs in lockbox. ACH/Wire [ACH
Automated Clearing House: These transactions include the online bill pay, and often
when you use your debit card], EZ Deposit (MICR reader scanning the checks
electronically) and Cross Currency receipt.

Credit cards are handled through ipayment which is executed via PayPal gateway. Credit
card receipt activity is reconciled daily using the Kronos Balance Credit card Receipts
Report and compared with PayPal activity and the Automatic Remittances Execution
Report from the overnight batch. The request set Kronos US Credit Card Processing
contains Automatic Receipts Creation Program, Automatic Remittances Creation
Program, Automatic Receipt Batch Management Report, Automatic Receipts Awaiting
Confirmation, Receipts Awaiting Remittance Report, Remittance Batch Management
Report and Receipts Awaiting Bank Clearance Report is scheduled to run overnight after
the autoinvoice has completed.

There are some invoices created manually by user for billing which are not done in OM,
changepoint. Requests for manual credit memos are sent to
addresscredits@kronos.com. Later the requests are approve by creating the CM in AR.

Oracle advanced collection is used by Kronos for customer collections. The Kronos
Descending Dollar Value Aging by Territory is the primary report used by the collectors in
conjunction with the collections Workbench (Kronos Collections). Universal Work queue
and Strategies are not used in collections at Kronos instead Kronos Account Scoring and
Strategy request set (Promise Reconciliation, Scoring Engine Harness etc..) is used to
maintain Kronos Collections. The interaction history is also used which is recorded in

44

Order To Cash Process

Kronos collector. Call logs report, Disputes for, adjustment form, processing payment
form for credit card payments to past due invoices.

The Kronos dunning letter report and Kronos detail aging report by salesrep are run once
in a month.

ADP outbound invoice and report: - The ADP invoices are only for US and printed in
English language. 12 invoice files are sent to the ADP on every Monday for the business
done on last week Sunday to Saturday.
The files contain the invoices extract and reports for following sections and for two
different groups.
All Invoices
Hardware, Software (no credits)
All credits
Depots, Installs, De-Installs
Repairs
Other Invoices
The two groups are:
T &E invoices are combined together (ADP type E for enterprise Etime business
value = ADP Reporting - E and ADP Type T orders for Hardware only business value
= ADP Reporting =T)

ADP Type Z orders for Ezlabors business value = ADP Reporting Z

45

Order To Cash Process

When we are submitting the request set Kronos Print Weekly Invoices then
KRON_OTIR107_SH.prog is called. The UNIX script is looping six times and submits the
concurrent program for report and invoice extract and which will be mailed to the ADP.
Following are the different files being created for different sections:
Hardware/Software No Credits = ADPINVHS.txt

All Credits = ADPINVCRD.txt

Repairs = ADPINVRPR.txt
Depots, Installs, De-Installs = ADPINVDEP.txt
All Other = ADPINVATR.txt
All Invoices = ADPINVALL.txt

Business Event (Create/Update party relationship): - Kronos has defined business

event to create or update the party relationship whenever user enters the data in party
relationships. This will reduce the manual entry in party relationships screen.
Business Event Name: oracle.apps.ar.hz.CustAcctRelate.Create

46

Order To Cash Process

This business event is calling the database package

(kr_cust_event.cust_acct_relate_created) to create the relationship.

Click on party relationships button. Initially there are no relationships defined.

47

Order To Cash Process

Click on relationships tab. Define relationship

Now go and check the relationships. The business event will be created automatically.

48

Order To Cash Process

Open AR Conversion for Acquisition: - During any acquisition done by Kronos, the open
invoices of acquired company will be fed into to oracle or Kronos. The acquisitions done by
Kronos are Stromberg, Nextime and AST acquisitions. The data will be loaded to staging
table from excel data sheet and then through concurrent program we can load and validate
the data to interface table.
Once data is loaded to interface table, then we can run the autoinvoice program to load the
data into base tables.

49

Order To Cash Process

Oracle Quote Print Report (XML Publisher)

At Kronos the Order Form for Quote Prints is generated through XML publisher. The general
flow to generate this pdf form is,
Login into Apps -> Go to Quoting Responsibility -> Open the Quote -> Click on Actions button
-> Click on Print Quote -> Select required template of the Order Form -> Click on submit ->
Order Form gets generated.
All the files related to this report will be available in following path,
$JAVA_TOP/oracle/apps/aso/print/server on the Application server
Few of these files are :
HeaderAttachmentVOImpl.class,HeaderAttachmentVORowImpl.class,HeaderVORowImpl.cla
ss,InternalOrgVORowImpl.class,LineAttachmentVOImpl.class,LineAttachmentVORowImpl.cla
ss,LinesVORowImpl.class,HeaderAttachmentVL.xml,HeaderAttachmentVO.xml,HeaderVO.x
ml,InternalOrgVO.xml,LineAttachmentVL.xml,LineAttachmentVO.xml,LinesVO.xml,QuoteAdd
ressVO.xml,QuoteShipmentVO.xml
At high level whenever enhancement is needed in this report the developer has to do
changes in three files,
Modify the query in the xml file -> Modify the code in java file -> Modify the xsl template
layout file.

Oracle Quotes Reports (.rdf )

1. Quotes Entered Report
This report extracts the data from Order Management and Oracle Quoting modules into excel file
format. These excel sheet will then are emailed to the Users.
It has three parameters Quote Entered Date From, Quote Entered Date To, Territory (Eg.
Enterprise). The file name of this report is KRON_QTER012.rdf
2. Order Hold History Report
The output format of this report is excel. The name of this report is KRON_QTER013.rdf
This report works based on the below logic,
a. Select orders where Order Source = Order Capture Quotes
b. Include all order statuses, including cancelled (10/4/06 remove logic to exclude orders
where Order Status = Cancelled)
c.

Column for product revenue should be based off of Business Line Item Category
where Business Line in HDW, SFW, OPM and OPN

d.

Orders will have multiple lines on the report if multiple holds were applied to the order

e.

Quote Group: Allow users to run report based on Sales group hierarchy as defined in
CRM Foundation.

50

Order To Cash Process

Effective dates of parent and children groups should be considered. Group will be
filtered using the Sales Group field on the quote header. ie. Select Enterprise from LOV
returns all quotes that have a sales group where Enterprise is the parent group. If no
group is specified, the order should appear on the corporate version of the report.

51

Order To Cash Process

Key system user roles and privileges

Role

Operation

Oracle Developer

All access in development and select in production and Test

environments

Business
Analysts

Select in all environments

DBA

Select/Insert/Update in all environments

52

Order To Cash Process

2. System Details
System Flow Diagram

Third party tools implemented and integrated with Oracle Applications E-Business Suite (Via Web
Methods/Point To Point Interfaces) at Kronos are:

Vertex for Tax Calculations

Optio Tool for invoice printing
Budget System
Oracle Agile
AMDOCS
On Track
Change Point (Currently Open Air project is in progress to replace this application

53

Order To Cash Process

Database Schema
Tables /Files / Views
Schema Name

Purpose

XXKRON

Custom Schema

ONT

Order management

AR

Accounts Receivables

ASO

Oracle Quotes

OKS

Service Contracts

CSI

Install Base

54

Order To Cash Process

Templates for Quote Print Report

Below are the templates in the Oracle apps for Quote Print Report,
Kronos English Order Form Detail

KRON_QTER008_EN_OF_DET.xsl

Kronos English Order Form Detail with Discounts

KRON_QTER008_EN_OF_DET_DISC.xsl

Kronos English Lease Schedule

KRON_QTER008_LS.xsl

Kronos English Lease Schedule Leasing Agreement

KRON_QTER008_LS_LA.xsl

Kronos French Order Form Summary

KRON_QTER008_FR_OF_SUM.xsl

Kronos French Order Form Detail

KRON_QTER008_FR_OF_DET.xsl

Kronos French Order Form Detail with Discounts

KRON_QTER008_FR_OF_DET_DISC.xsl

55

Order To Cash Process

Test Plans and Cases

As of now the Test Plans and Test Cases are being created by the Developer based on the analysis done
on the business requirement document.
Expected process in future is that these will be provided by the BAs along with the Requirement
Document.

56

Order To Cash Process

3. Technical Processes
Software Configuration
Software

Version

Purpose

Toad

10.6

Oracle Developers Tool to

query, create and work
with backend tables

Forms & Reports

6i

To Develop and Customize

Oracle Forms and Reports

Oracle Applications

11.5.10.2

ERP used with multiple

modules

Workflow Builder

2.6.3.0.1

To develop and Customize

Oracle Workflows

Visual Source Safe

6.0c

To maintain the code

versions

Putty

0.60

To access the Unix servers

Oracle DB

10.2.0.2.0

Database to store the data

57

Order To Cash Process

Environments
Development and Test Environment
Software

Version

Purpose

Server

Toad

10.6

Oracle Developers Tool to

query, create and work with
backend tables

TESTDB

Forms & Reports

6i

To Develop and Customize

Oracle Forms and Reports

TESTAPP

Oracle
Applications

11.5.10.2

ERP used with multiple

modules

TESTDB

Workflow Builder

2.6.3.0.1

To develop and Customize

Oracle Workflows

TESTDB

Visual Source
Safe

6.0c

To maintain the code

versions

TESTAPP & TESTDB

Putty

0.60

To access the Unix servers

TESTAPP & TESTDB

Oracle DB

10.2.0.2.0

Backend database to store

the data processed by and
through Oracle

TESTDB

Customer Facing Sites

Planet.Kronos.com
https://customer.kronos.com/Default.asp

58

Order To Cash Process

Production Environment
Software

Version

Purpose

Server

Toad

10.6

Oracle Developers Tool

to query, create and
work with backend
tables

PRODDB

Oracle
Applications

11.5.10.2

ERP used with multiple

modules

PRODAPP

Workflow Builder

2.6.3.0.1

To develop and
Customize Oracle
Workflows

PRODDB

Oracle DB

10.2.0.2.0

Backend database to
store the data
processed by and
through Oracle

PRODDB

Forms & Reports

6i

To Develop and
Customize Oracle
Forms and Reports

PRODAPP &
PRODDB

Naming Conventions
The custom Application Top folder for Kronos in Oracle Applications is $XXKRON_TOP
The Customized forms by Kronos should start with:KRON for forms fmb files (E.g.: KRON_QOTCMCPQ.fmb), K for forms library pll files (Eg:
KQOTCMCPQ.pll)
The Customized reports by Kronos should start with:KRON (E.g.: KRON_OTIR084_2.rdf)
The customized packages, procedures and other oracle objects should start with KR,
E.g. : KR_UPDATE_NEW_QUOTE_PKG.pks, KR_UPDATE_NEW_QUOTE_PKG.pkb

Any object or component with the name KRON/KR represents that it was customized at Kronos.

Coding Standards
There are no specific coding standards defined apart from defining all custom processes starting with
word K/KR/KRON.

59

Order To Cash Process

Test Procedures
When working on the quote print report in dev instance, if we need the .java file for .class file, request the
Release engineers to decompile and give the .java file to developer. Also request them to BOUNCE the
Apache Server (Web Server) so that the modified .class file will be reflected.
When releasing to QA give the instructions as below in CRF doc,
Copy files to TESTAPP:
1. Copy the following files from the deployment location to the target location:
a. HeaderAttachmentVO.xml
b. LineAttachmentVO.xml
c. InternalOrgVO.xml
d. InternalOrgVORowImpl.java
2. Compile the Java source file InternalOrgVORowImpl.java on TESTAPP.
3. Copy the resulting .class file to the target location and back to the deployment location.
4. Remove the .java file from the target location.
5. Bounce the Apache server.
Also give instructions to replace the template with the new modified template with screenshots.

Job Scheduling / Sequencing of Batch Jobs

Job/Program

Frequency

Autoinvoice program

Daily runs at night

Workflow background Process

Every 5 Mins

Kronos Update Customer Class Code

Daily runs at night time

Kronos ADP Daily Orders Report

Daily runs at night time

Kronos US Credit Card Processing

Daily runs at night time

Kronos Dunning Letter Report

Monthly

Kronos Detail Aging by Salesrep Program

Monthly

Transaction Volume / Data Volume

1. Approximately 75 reinstatement contracts, containing an average of 2000 lines are processed in
a month.

60

Order To Cash Process

Month End / Quarter End / Year End Processing

There are many month end processes performed by SME.
1. Opening and closing inventory periods
2. Opening/Closing Accounting periods

Release and Deployment Procedures

<Details are captured in Common Processes documents>

61

Order To Cash Process

Change Request Procedure

<Detailed Steps are captured in Common Processes Document>
Steps to be followed when working with Quote Prints Enhancements

1. Login into VSS and Navigate to the respective Folder to get the latest
versions of java files, xml files, xsl files

62

Order To Cash Process

2. Right click on the source files and click Check Out to target VSS working
folder the file gets red colored symbol on it. Once the file is checked then no
other person can work with it unless it is restored or checked again by him.
3. Now from VSS working directory copy the files to your local drive (C:\).
4. After modifications to the files and save them.
5. Upload the new file to XML publisher,
6. Go to XML publisher Administrator -> Templates and upload the new xsl file

63

Order To Cash Process

In the above screen you can update the new xsl file uploaded if there is only
change to xsl file and new template is not created. If there is a need to create
new template for the xsl file then,

Give name for the template, Application (e.g. Order Capture), End date,
Description, Code
(ASOPRT) and start date and click Apply.
To create new template click on template

64

Order To Cash Process

Click Apply.
7. For Testing the Quote Print Order Form,
Login into Apps -> Go to Quoting Responsibility -> Open the Quote -> Click
on Actions button -> Click on Print Quote -> Select required template of the
Order Form -> Click on submit -> Order Form gets generated.
8. After completion of development and testing move the modified files from C:
to the VSS Working Directory.
9. For updating in VSS
From VSS Working Directory move files to
Oracle\Apps\Deployments\<mercury#> folder (Mercury number is the
target folder name).
In the same folder place the CRF (Code Release Form filled) and update
the technical spec.
10.
Give detailed steps under Release Instructions section CRF form for
DBA.
11.
Release Engineers will pick the file from QA instance and will deploy in
the Production. Once the production deployment is successful move the
modified file to the VSS Working Directory.
12.
Right click on the modified file in the VSS Working Directory and click
Check In. With this step the latest version of the file will be replaced in the
VSS in the place of old file.

65

Order To Cash Process

DBA activities
When working on the quote print report in dev instance, if we need the .java file for .class file, request the
Release engineers to decompile and give the .java file to developer. Also request them to BOUNCE the
Apache Server (Web Server) so that the modified .class file will be reflected.
When releasing to QA give the instructions as below in CRF doc,
Copy files to TESTAPP:
1. Copy the following files from the deployment location to the target location:
a. HeaderAttachmentVO.xml
b. LineAttachmentVO.xml
c. InternalOrgVO.xml
d. InternalOrgVORowImpl.java
2. Compile the Java source file InternalOrgVORowImpl.java on TESTAPP.
3. Copy the resulting .class file to the target location and back to the deployment location.
4. Remove the .java file from the target location.
5. Bounce the Apache server.
Also give instructions to replace the template with the new modified template with screenshots.

Escalation Procedures
In case developers face any issue with standard functionality, they will open service request with oracle
with prior consultation with SME or onsite manager.

Communication Procedures
Developers
1. Whenever Change Request is raised and once the developer is done with his coding, testing etc
he has to place all the related files in the deployment folder, have to fill the CRF document
completely, create a Release Request for the Mercury Ticket and then inform the same to the
Release Engineers for further process.
2. When there is a need of DBAs/Release Engineers in Development/test Phase developer can
communicate and take help from them through Mail or Phone.

Archiving / Purging Procedures

Standard Purging processes are taken care by DBAs

66

Order To Cash Process

Application Support Activities

<Details are captured in Common Processes documents>

67

Order To Cash Process

4. Tools and Utilities

Oracle Forms 6i

Oracle Reports 6i

Toad

Optio

Core FTP
LE

Edit/Notepad++

To
develop/customize
Oracle Apps
Forms

To
develop/customize
reports in Oracle
Apps

Tool used by
developer for
creating
objects,
coding and
querying

Tool used
for Invoice,
PO, Pickslip,
Packslip and
Payable
Checks
reports

Used to FTP
the files
related to
Forms,
Reports and
other
database
objects to
other
instance

Used to edit the

code related to
Oracle, xml, xsl
templates etc.

68

Order To Cash Process

5. User/SME Contacts
SME/Developer

BAs

Tim Jung

Kristen Cornila

Van-Loc Doran

Marcia Corbett

Michael Emmons

Nancy Hicks

Henk Van Lingen

Lynn Andrews
Jennifer Larco

69

Order To Cash Process

6. Application Support History

Calls and Resolutions
Any Oracle related heat tickets will be assigned to BAs first. BAs will do initial analysis of the ticket and
will assign to developers by raising a new CR in mercury for the ticket if the issue is related to code
enhancement, bug fixing etc.

Common Problems and Resolutions

Mostly new enhancement requests will be raised by the business. These can be new enhancement or
further enhancement to the already customized component.

Last enhancement done to the Quoting Form is in Mar 10, 2011. No problems faced on quoting module
from past 2 years.

The last enhancement for Quote Prints report was done on Mar 9, 2011. This was for adding a new
column Instance_Name.

A developers responsibility includes giving correct and proper information and screenshots in CRF
document. DBAs will follow the instructions given by us and in most cases does the copy paste of the
setup information or commands given in the CRF document. If something goes wrong then deployment
will be delayed.

Tickets from last 3 years.

Oracle CRs from past

3 YEARS.xls

70

Order To Cash Process

7. Document Inventory
Sr.
No.

Document Name

Document Description

URL

KronosQuoteTechnicalDoc_v1.1.d
oc

Initial version the quote print report

from Prostege Solutions

https://collabora
te.kronos.com/s
ites/globit/corpo
rateit/busapps/
Applications
%20OOTB
%20WF/Forms/
AllItems.aspx

Tech Spec - QTE.R008 Quote

Print Reports.doc

Updated version of quote print

report by Tim

https://collabora
te.kronos.com/s
ites/globit/corpo
rateit/busapps/
Applications
%20OOTB
%20WF/Forms/
AllItems.aspx

PROD CRF - 40079.docx

Sample Production Code Request

Form for adding new column
Instance_Name

https://collabora
te.kronos.com/s
ites/globit/corpo
rateit/busapps/
Applications
%20OOTB
%20WF/Forms/
AllItems.aspx

Technical Specification Order

Header Workflow

Customization on order header WF

https://collabora
te.kronos.com/s
ites/globit/corpo
rateit/busapps/
Applications
%20OOTB
%20WF/Forms/
AllItems.aspx

5.

Tech Spec
COGS_Workflow_Extension

Technical specification on COGS

workflow extension

https://collabora
te.kronos.com/s
ites/globit/corpo
rateit/busapps/
Applications
%20OOTB
%20WF/Forms/
AllItems.aspx

71

Order To Cash Process

6

Technical Specification Order

Line Workflow

Customization on order line WF

https://collabora
te.kronos.com/s
ites/globit/corpo
rateit/busapps/
Applications
%20OOTB
%20WF/Forms/
AllItems.aspx

Tech Spec ADP order file import

Technical specification for ADP file

import using Webmethods

https://collabora
te.kronos.com/s
ites/globit/corpo
rateit/busapps/
Applications
%20OOTB
%20WF/Forms/
AllItems.aspx

72

Order To Cash Process

APPENDICES
Attached is the list of components/customizations covered
in the Transition

List of
Components-Customizations covered in Transition.xls

73

Order To Cash Process

Glossary
Business Terminologies
OKS = Oracle Service Contracts
AR = Accounts Receivable
OM = Order Management
ASO = Oracle Quotes
OKC = Service Contracts
Solution ID = Account Number of the Customer

74