Professional Documents
Culture Documents
Author:
Viswanadham Sighakolli
Creation Date:
Last Updated:
Document Ref:
RD050 Draft 1B
Version:
DRAFT 1A
Approvals:
<Approver 1>
<Approver 2>
Yogesh Kulkarni
Document Control
Change Record
3
Date
Author
Version
Change Reference
18-Apr-13
18-Mar-13
Viswanadham
Sighakolli
Draft 1a
No Previous Document
Reviewers
Name
Position
Ashish Poogalia
Krishnam Raju
Project Lead
Krishnam Raju
Project Manager
Distribution
Copy
No.
Name
Location
Library Master
Project Library
Krishnam Raju
Project Manager
3
4
Note To Holders:
Page 2
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
If you receive an electronic copy of this document and print it out, please write your name on
the equivalent of the cover page, for document control purposes.
If you receive a hard copy of this document, please write your name on the front cover, for
document control purposes.
Page 3
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Contents
Document Control........................................................................................... ii
Event Catalog................................................................................................ 4
<High-Level Business Function>.................................................................4
Process Listing and Process Descriptions..........................................................5
<High-Level Business Function>.................................................................5
Process Relationships for <High-Level Business Function>.............................5
Function Hierarchy......................................................................................... 6
<High-Level Business Function> NA............................................................6
Process Step Catalogs....................................................................................7
Purchasing Transactions Intrastate Purchases............................................7
Purchasing Transactions Interstate Purchases............................................7
Purchasing Transactions - Imports...............................................................8
Purchasing Transactions Purchase Returns...............................................9
Purchasing Transactions Capital Deferment...............................................9
Purchasing Transactions Capital Goods.....................................................9
Service Procurement or Indirect Procurement.............................................10
Negative Service Tax...............................................................................10
Reverse Service Tax...............................................................................11
Tax Deducted at Source...........................................................................11
Domestic Sales......................................................................................12
Spares Sales.........................................................................................13
Scrap Sales (Material Scrap & Waste Scrap)...............................................14
Export Sales..........................................................................................14
Page 4
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Page 5
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Event Catalog
ote:
An example of an event is a customer order. In responding to the customer order the business executes a
process. Fill out the following information for each event that is identified:
Event ID: Give each event a unique identification.
Name: Name each event as clearly as possible.
Type: Events may be external, internal or temporal (for example, occur at a predetermined time).
Description: Briefly describe the event.
Frequency: Indicate frequency; for example, 10/hour, 1/week, or monthly.
The events here may be the same ones identified earlier during the Current Process Model (BP.040). If so, use
the event catalog developed there. There may be new events that will need to be responded to based on future
business strategies, or there may be new internal events that trigger a process to respond.
This component lists all events to which the business responds.
Type
Description
Frequency
IL-PO1-01
Purchases
India Localization
IL-PO2-01
Purchases
India Localization
IL-IMP-01
Purchases
India Localization
IL-RTV-01
Purchases
India Localization
IL-CD-01
Purchases
India Localization
IL-CAP-01
Purchases
India Localization
IL-SP-01
Services
India Localization
IL-NST-01
Services
India Localization
IL-RST-01
Services
India Localization
IL-TDS-01
Tax Deducted at
Source
India Localization
TDS
IL-DS-01
Sales
India Localization
Domestic Sales
IL-SS-01
Sales
India Localization
Spares Sales
Yearly
IL-SCS-01
Sales
India Localization
Scrap Sales
Page 6 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Name
Type
Description
Frequency
IL-ES-01
Sales
India Localization
Export Sales
IL-BRE-01
Bond Register
India Localization
Yearly
IL-BRI-01
Bond Register
India Localization
Yearly
IL-TCS-01
Tax Collected at
Source
India Localization
TCS Settlement
Monthly / Quarterly /
Yearly
IL-VAT-01
India Localization
VAT Settlement
Monthly /
Quarterly / Yearly
IL-ST-01
Service Tax
India Localization
Monthly / Quarterly /
Yearly
Page 7 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Enter a description for each of the processes within this business function.
Process Title
Description of Process
IL-01
IL-PO1-01
Purchases
IL-02
IL-PO2-01
Purchases
IL-03
IL-IMP-01
Purchases
IL-04
IL-RTV-01
Purchases
IL-05
IL-CD-01
Purchases
IL-06
IL-CAP-01
Purchases
IL-07
IL-SP-01
Services
IL-08
IL-NST-01
Services
IL-09
IL-RST-01
Services
IL-10
IL-TDS-01
TDS
IL-11
IL-DS-01
Sales
Domestic Sales
IL-12
IL-SS-01
Sales
Spares Sales
IL-13
IL-SCS-01
Sales
Scrap Sales
IL-14
IL-ES-01
Sales
Export Sales
IL-15
IL-BRE-01
Bond Register
IL-16
IL-BRI-01
Bond Register
IL-17
IL-TCS-01
TCS Settlement
IL-18
IL-VAT-01
VAT Settlement
IL-19
IL-ST-01
Service Tax
Output
Revision: 04/2008
Sample material purchased on FOC for product development or testing. There is no process difference between
sample purchase and normal purchase except that price would be zero in case of purchase on FOC basis. If business is
paying any taxes / duties in this purchase, adhoc tax category can be created and user can enter amount that is paid
CST payment,Quarterly return & yearly return This is part of report requirement and covered in that section
VAT TDS quarterly return This is part of report requirement and covered in that section
Entry Tax payment, monthly return & Yearly return (for Raw material & Capital goods) This is part of report requirement
and covered in that section
PLA payment to excise This will be included
Purchase return to import supplier details process need to cover. - There is no difference in process whether it is
imports / interstate / intrastate. If any specific process is there, pl. let me know.
Differential custom duty Calculation This is part of report requirement and covered in that section
Vetting of each return and understanding of the field in each and every return that we discussed. This is part of report
requirement and covered in that section
Page 9 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Function Hierarchy
<Company Short Name>
Function:
Function Owner:
Date:
<Function Owner>
<Date>
<Function Name>
Description:
<Function Description>
Functio
n
ID #
Use one row per business function. Follow these guidelines in using the columns:
1) Function ID #: A unique sequence number for each elementary business function.
An elementary business function is a business function which, if started, must either complete successfully or, if it
cannot complete successfully, must undo any effects that it has had up to the point of failure; it is the lowest
available unit of work or task; it corresponds to a process step in a business process.
2) Function Description: A brief description, beginning with an action verb, that captures the functions purpose
and deliverable task (note: each task should have one deliverable).
3) Function/Owner: Title of person executing the function.
4) Type: A combination of Manual or System-Assisted, and Internal or External.
5) Note: Additional relevant information about the function.
Function Description
Function Owner
Type
Notes
Page 10 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Functio
n
ID #
Function Description
Function Owner
Type
Notes
Page 11 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
IL-PO101
Placing of PO with
appropriate tax
category
Automatic
Page 12 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
IL-PO102
Receipt of Raw
Material / Expense
Items once
supplier ships
materials.
Frequency
Notes
Agent
Automation
Manual
Checking of taxes
and claiming of
CenVAT
Finance Team
Manual
IL-PO104
Hitting of Registers
Finace Team
Manual
Page 13 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-PO105
VAT Claim
Finance Team
Manual
IL-PO106
Invoice Booking
Finance Team
Manual
IL-PO107
Payment
Finance Team
Manual
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
Page 14 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILPO201
Placing of PO with
appropriate tax
category
Automatic
ILPO202
Receipt of Raw
Material / Expense
Items once supplier
ships materials.
Manual
Checking of taxes
and claiming of
CenVAT and also
check for CST with
C-form type of tax is
attached or not
Finance Team
Manual
ILPO204
Hitting of Registers
Finace Team
Claiming is
Manual &
Registers
hitting is
Automatic
ILPO206
Invoice Booking
Finance Team
Manual
Payment
Finance Team
Manual
ILPO208
C-Form Issue
Processing
Finance Team
Manual
Page 15 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILPO209
Issue of C-Forms to
Suppliers
Finance Team
Manual
ILPO210
C-Form Upload
Format
Finance Team
Manual
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
Page 16 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-IMP01
As & When
Required
Procurement Team
Manual
IL-IMP02
As & When
Required
Stores
Manual
IL-IMP03
As & When
Required
Finance
Manual
IL-IMP04
As & When
Required
Finance
Manual
System
Automatic
As & When
Required
The process step catalogue identifies the process steps that make up the business process.
Page 17 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Revision: 04/2008
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
IL-RTV01
As & When
Requried
Manual
IL-RTV02
As & When
Required
Manual
IL-RTV03
As & When
Required
Automatic
Page 18 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
Page 19 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-CD01
As & When
Required
Finance
Manual
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
ILCAP01
As & When
Required
Procurement Team
Manual
ILCAP02
As & When
Required
Stores Personnel
Manual
Page 20 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILCAP03
As & When
Required
System
Automatic
Finance
Manual
Finance
Manual
As & When
Required
As & When
Required
Page 21 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILCAP06
As & When
Required
Finance
Manual
ILCAP07
Monthly /
Quarterly /
Yearly
Finance
Manual
Entry tax
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
Page 22 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Revision: 04/2008
Description
Frequency
Notes
Agent
Automation
IL-SP01
As & When
Required
Procurement Team
Manual
IL-SP02
As & When
Required
Stores / Finance
Manual
IL-SP03
As & When
Required
Finance
Manual
IL-SP04
As & When
Required
Finance
Manual
IL-SP05
As & When
Required
Finance
Manual
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
Page 23 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILNST-01
As & When
Required
Procurement Team
Manual
ILNST-02
As & When
Required
Stores / Finance
Manual
ILNST-03
As & When
Required
Finance
Manual
ILNST-04
As & When
Required
Finance
Manual
ILNST-05
As &When
Required
Finance
Manual
ILNST-06
As & When
Required
Finance
Manual
How about Services where tax is not levied by the service provider, shouldnt system pass automatically entry for Service
tax payable? For taxi hire service, it should generate auto service tax payable entry. Further, services where partial credit
can be taken and remaining credit needs to be shown as payable, auto system entry should be passed..--> This is how
system works and is demonstrated in CRP-II. Creation of service item It is part of MDM
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
Page 24 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILRST-01
As & When
Required
Procurement Team
Manual
ILRST-02
As & When
Required
Stores / Finance
Manual
ILRST-03
As & When
Required
Finance
Manual
ILRST-04
As & When
Required
Finance
Manual
ILRST-05
As &When
Required
Finance
Manual
ILRST-06
As & When
Required
Finance
Manual
Suprisingly , no mention of Service Tax Statutory Register, how the data will be imported in to the Statutory registers, for
receipt of services, payment of services , reconciliation with GL ..why all these basic things are missing? Service Tax
Register is taken as part of reporting requirements. I will include
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Page 25 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Revision: 04/2008
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
IL-TDS01
As & When
Required
Finance
Manual
IL-TDS02
As & When
required
System
Automatic
IL-TDS03
As & When
Required
Finance Team
Manual
ILTDS_0
4
Monthly /
Quarterly
Finance Team
Manual
Quarterly
Page 26 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-TDS05
Monthly /
Quarterly
Finance Team
Manual
1.
2.
3.
2.
India Program to
Generate eTDS
Certificates
3.
India Program
Generate eTDS
Quarterly Certificates 16
A 26Q
4.
India Program
Generate eTDS
Quarterly Certificates 16
A 27EQ
IL-TDS06
Monthly /
Quarterly
Finance Team
Manual
IL-TDS07
As & When
Required
Finance Team
Manual
Page 27 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-TDS08
As & When
Required
Finance Team
Manual
As & When
Required
Domestic Sales
Below process flow needs to be followed for Oracle design purpose which has been agreed yesterday by all
business stake holders viz. Finance.. Will include
Here understanding is MU2 will be immediately doing the stock transfer to MU1 at Standard Cost
upon manufacture of FG through Oracle IST process
Excise Permission will be obtained for Storing the Finished goods (ATMs) at a place adjacent (within
3 km as far as possible) . This will be MU1 Warehouse.
Excise duty , VAT liability creation and payment if any will be generated only at MU1 Stage upon
actual need for movement of ATM/Spares from MU1 Warehouse by any trigger from customers end.
Page 28 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Similarly stock transfer intra MU1 will be dealt within the books of MU1. MU1 while doing intra
operating unit stock transfers, will need to pay the Excise duty on the Banks final purchase Order
Price.
MU1 will be the end customer interface and book entire profit for end customer transactions at MU1
Operating Unit .
MU2 will be the pure Cost Center from Manufacturing stand point and will have Variances and
realized Gain/ Losses as its bottom line (profit /Loss) . If any item of cost is incurred by MU2 not
covered through standards, MU2 will reflect unrecoverable expense in the form of expense to MU2
Operating Unit P&L
Interest on Overdraft , audit fees and Corporate office expenses will be mapped to either MU1 or
MU2 or MU3 depending upon who has borrowed the money and for what need
ote:
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
IL-DS01
As & When
Required
System
Automatic
Page 29 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-DS02
As & When
Required
Dispatch Section
Manual
System
Automatic
Dispatch / Finance
Manual
Finance / Dispatch
Manual
As & When
Required
IL-DS04
As & When
Required
IL-DS05
As & When
Required
Page 30 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-DS06
As & When
Required
Finance
Manual
Finance
Manual
IL-DS07
As & When
Required
Spares Sales
ote:
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
IL-SS01
As & When
Required
System
Automatic
Page 31 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-SS02
As & When
Required
Dispatch Section
Manual
System
Automatic
Dispatch / Finance
Manual
Finance / Dispatch
Manual
IL-SS03
As & When
Required
IL-SS04
As & When
Required
IL-SS05
As & When
Required
Page 32 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-SS06
As & When
Required
Finance
Manual
IL-SS07
As & When
Required
Finance
Manual
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
Page 33 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILSCS01
As & When
Required
System
Automatic
As & When
Required
Dispatch Section
Manual
ILSCS03
As & When
Required
Finance
Manual
ILSCS04
As & When
Required
Finance
Manual
ILSCS05
As & When
Required
Finance
Manual
Page 34 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILSCS06
Export Sales
ote:
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
IL-ES01
As & When
Required
Agent
Automation
Manual
As & When
Required
Dispatch Section
Manual
Page 35 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-ES03
As & When
Required
System
Automatic
As & When
Required
Dispatch / Finance
Manual
IL-ES05
As & When
Required
Finance / Dispatch
Manual
IL-ES06
As & When
Required
Finance
Manual
IL-ES07
As & When
Required
Dispatch
Manual
IL-ES08
ARE1 is to be generated
As & When
Required
Finance / Dispatch
Manual
IL-ES09
As & When
Required
Finance
Manual
IL-ES10
As & When
Required
Finance
Manual
Page 36 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-ES11
As & When
Required
Finance
Manual
IL-ES12
As & When
Required
System
Manual
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
ILBRE01
Yearly
Finance
Manual
Page 37 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILBRE02
As & When
Required
Finance
Manual
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
IL-BRI01
Yearly
It is part of customization
Finance
Manual
IL-BRI02
As & When
Required
It is part of customization
Finance
Manual
It is a mandatory statutory
requirement. OK
TCS Settlement
ote:
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Page 38 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Revision: 04/2008
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
ILTCS01
Monthly /
Quarterly /
Yearly
Finance
Manual
ILTCS02
Monthly /
Quarterly /
Yearly
Finance
Manual
ILTCS03
Monthly /
Quarterly /
Yearly
Finance
Manual
ILTCS04
Monthly /
Quarterly /
Yearly
Finance
Manual
ILTCS05
Monthly /
Quarterly /
Yearly
Finance
Manual
ILTCS06
Finalize Settlement
Monthly /
Quarterly /
Yearly
Finance
Manual
Page 39 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
ILTCS007
Monthly /
Quarterly /
Yearly
Finance
Manual
ILTCS08
Quarterly
Finance
Manual
ILTCS09
Quarterly
Finance
Manual
ILTCS10
Yearly
Finance
Manual
ILTCS-11
Yearly
Finance
Manual
VAT Settlement
ote:
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
Page 40 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-VAT01
Monthly /
Quarterly /
Yearly
Finance
Manual
IL-VAT02
Monthly /
Quarterly /
Yearly
Finance
Manual
IL-VAT03
Monthly /
Quarterly /
Yearly
Finance
Manual
IL-VAT04
Monthly /
Quarterly /
Yearly
Finance
Manual
IL-VAT05
Quarterly
Finance
Manual
IL-VAT06
Yearly
Finance
Manual
IL-VAT07
Monthly
Finance
Manual
Page 41 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
The process step catalogue identifies the process steps that make up the business process.
It is optional to perform this step here; when the Gather Business Requirements (RD. 050) are constructed you
will also be developing process steps for each process.
ID: Supply a process step ID. Think about a systematic way for numbering processes and process steps. It
might make sense to build significance into the process ID; for example, BM 01 might represent the first step in
the Bill of Material process.
Description: Record the process step as clearly as possible. If possible, use a simple verb noun format, but do
not hesitate to add information for clarity. For example, answer phone, record (order) information and so on.
Frequency: State the frequency that the process step occurs; hourly, weekly, every other order, every third
piece, and so on.
Notes: Record notes as appropriate to clarify the nature of the step or record any issues which it raises. It is
possible to key word notes in order to later retrieve all notes with the same key word.
Agent: Identify the party who is responsible for the execution and completion of the step.
Automation: Identify whether the step is manual or system-assisted.
ID
Description
Frequency
Notes
Agent
Automation
IL-ST-01
Monthly /
Quarterly /
Yearly
Finance
Manual
Page 42 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-ST-02
Monthly /
Quarterly /
Yearly
Finance
Manual
Monthly /
Quarterly /
Yearly
Finance
Manual
IL-ST-04
Monthly /
Quarterly /
Yearly
Finance
Manual
IL-ST-05
Quarterly
DAILY
required
Finance
Manual
Page 43 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Description
Frequency
Notes
Agent
Automation
IL-ST-06
Half Yearly
Finance
Manual
Page 44 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
To-Be Activities
This component provides details of the activities to be carried out as part of the process flow.
Page 45 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
ID
Issue
Resolution
Responsibility
Target Date
IL-DS-05
Customization
ITAC
KUT
IL-ES-06
Customization
ITAC
KUT
IL-BRI-01
Customization
ITAC
Post Go Live
IL-BRI-02
Customization
ITAC
Post Go Live
IL-VAT-07
Customization
ITAC
KUT
Impact Date
Page 46 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008
Closed Issues
ID
Issue
Resolution
Responsibility
Target Date
Impact Date
Page 47 of 47
Adapted from Oracle Application Implementation Method Handbook, 1999
Confidential Internal Use Only
275842486
Revision: 04/2008