Applitech Solution Limited
Functional Specifications
Order Execution System
Version 1.0
For
3P Consultants Pvt. Ltd.
701, Shikhar, Navrangpura,
Ahmedabad 380009, India
Tel: +91 (79) 656 0248 / 8709 /
8797
Fax: +91 (79) 656 9489
E-Mail: aslahd@vsnl.com
URL: www.applitechsolution.com
Table Of Contents
General Points
for Consideration ........................................ 4
Feature List For The System ............................................. 5
Form Objects ............................................................ 6
Common Features Provided In The System ................................. 7
Security Feature For The System ......................................... 8
Legends ................................................................. 8
Login Screen ............................................................ 9
Company Master ......................................................... 10
Division Master ......................................................... 12
Branch Master .......................................................... 13
Financial Year Master .................................................. 15
Currency Master ......................................................... 16
Country Master .......................................................... 19
Industry Master ......................................................... 20
Parent Group Master ..................................................... 21
Designation Level Master ............................................... 22
Client Master .......................................................... 24
Function Master ......................................................... 30
Ally Master ............................................................. 32
Billing Cycle Master .................................................... 33
Perk Master ............................................................. 34
Out of Pocket Expenses ................................................. 35
Communication Type Master .............................................. 36
Media Master ............................................................ 37
Activity Master ......................................................... 38
Reason Master ........................................................... 40
Employee Master ......................................................... 41
Rate Contract Master .................................................... 42
Inquiry
................................................................. 43
Inquiry Through Shopping Cart .......................................... 47
Proposal ............................................................... 49
Proposal Amendment ..................................................... 53
Sales Order ............................................................ 57
Project Plan ........................................................... 60
Advertising Details .................................................... 64
Transfer of Inquiry / Proposal / Sales Order ........................... 66
Candidate Listing ...................................................... 68
Preliminary Interview Score Sheet ...................................... 70
Interview Schedule ..................................................... 73
Interview Reschedule ................................................... 76
Compensation Details ................................................... 79
Feedback Form .......................................................... 83
Invoice ................................................................. 85
Follow Up with Client .................................................. 87
Follow Up with Candidate ............................................... 89
Prospective Candidate .................................................. 91
Checklist for Project Closure .......................................... 94
Resume Sale ............................................................ 96
Fee Receipt Details .................................................... 98
Annexure A
Auto Generated Activity Code
........................................... 100
Annexure B
Screen Design Standards
................................................ 102
General Points For
Consideration
- The functional specifications document is intended
to present the functionality of the proposed system to 3P Consultants Pvt
Ltd. It contains prototype screens of the proposed system along with a
description, which includes the business rules applicable to each screen
to be used in the Order Execution System.
- Proposed users (involving key users at all levels)
are expected to review the functional specification document and express
their comments and suggestions regarding the present status of design and
development of the proposed system.
- All issues identified during the review by 3P
Consultants Pvt Ltd will be jointly discussed by both parties and
appropriate conclusion will be derived keeping in mind the scope and
nature of the proposed system.
- Any changes agreed upon in the review session will
be documented in another version of the functional specification document.
The same will be submitted on completion of the changes.
- The underlying database behind the prototype
screens is partially conceptualised at this stage. Complete design of the
same can commence only after freezing the functional specifications
document and report requirements.
- If this document is found satisfactory by 3P
Consultants Pvt Ltd, a copy duly signed and sealed must be handed over to
us so that development in the subsequent stages can commence.
- The browser to be used for the Order Execution
System is only Internet Explorer 5.0 and above. The resolution must be 800
by 600 pixels.
Feature list for the system
- Automatic email facility will be provided to send
the interview schedule and for any rescheduling done. The email will be
sent at the address specified by the candidate/ consultant in the
candidate database.
- The system will have list of predefined formats of
proposals, which will be generated as and when specified by the consultant
for an inquiry. The type of proposals that will be generated will be flat
rate, percentage, and turnkey.
- Facility to generate standard letter, which will be
used by the consultant to mail to the clients and candidates, will be
provided in the OES.
- The facility has been provided in the system to
convert an inquiry coming from the shopping cart to be stored in the
database. However this will only be converted into an inquiry (with an
inquiry no. generated) once the consultant specifies so.
Form Objects
|
No. |
Object |
Description |
|
1 |
Combo |
Combo – a combo will give the
list of values pertaining to the item. The user will have to select from the
list. |
|
2 |
Radio Button |
Radio Button – a radio button
is mutually exclusive i.e. in case where there are multiple items specified
against a radio button the user can only select one. |
|
3 |
Check Box |
Check Box – these are mutually
inclusive i.e. in case where there are multiple items specified against a
check box the user can select any number of items. |
|
4 |
Date |
Date – the user will enter the
date from the calendar in dd/mm/yyyy format. In case where the date is
optional then the user will enter through the keyboard and where the date is
mandatory the date will come in form of the calendar. |
|
5 |
Number field |
Number field – the user will
only be allowed to enter number and decimals. Wherever necessary the user
will be allowed to enter up to a maximum of two decimals. Only in case of the
rate the user can enter up to 4 decimals. |
|
6 |
Text Field |
Text Field – the user will
enter the text relevant to the item. |
|
7 |
Text Area |
Text Area – the user will enter
the description relevant to the item. |
Common features provided in
the system
- Menus have been provided at various screens to
enable the user to smoothly navigate.
- Fields are classified as Enter or display. Enter
fields require input from the user and are of two type viz. mandatory
(black) and optional (blue). Display (red) only fields display the values
automatically and the user cannot change the contents of the field.
- A general iconic toolbar is provided on the top of
each form to add, save, view, delete and navigate information on the
screen. The add button will allow the user to add new records, view button
will open a search window with attributes as per individual screen to
allow the user to select and view a particular record and modify, save
button will allow to save a new or modified record after proper validation
and delete button will allow the user to delete a selected record.
- Alerts and validations are provided where the
system requires the user to acknowledge a particular action.
- Each screen will have a section (frame) which will
have links to the following - Login, Masters, Transactions, Reports and
Security.
- The user will login using the Login screen using
his/her user name and password. The user will be allowed to enter the
system only after proper authentication.
- The user will have to select the company, division
and financial year before entering any records. The data pertaining to the
company, division, financial year and branch selected will only be
displayed. A consultant will be associated with only one branch.
- Apart from above each screen will also give the
option to the user to move between Company, Division, Branch and Financial
Year according to the privileges defined by the system administrator for
each consultant.
- The auto generated codes (data type) and the design
standards for the proposed system is attached.
- The fields that can be modified by a normal user
have to be identified and frozen between 3P and Applitech.
Security Feature for the
system
An employee of a Company who will
use the Order Execution System will be given User ID and password by the system
administrator. This User will have access to one or more Company depending on
the role attached and the privileges granted to him. This right will enable the
user to post transaction on selecting a division and financial year of a
particular company.
User level will be defined on the
basis of rights for add, view, save, delete for each screen
(Master/Transaction). The rights for reports that will be generated by user
will be defined. Accordingly each user will be given a user level no.
Legends
A – Auto Generated
M – Mandatory
O – Optional
D – Display
CIN – Company Index Number
PAN – Permanent Account Number
SON – Sales Order Number
PIN – Postal Index Number
Form name: Login Screen
Form Type : Login
Short name : OEL01
Purpose :
Only authorized users with valid user name and password are given access to the
Order Execution System.
Business Rule:
Company will allocate user name
and password to the employee through security module along with his security
level no. The user will be allowed to access the system as per his security
level.
User Name (M):
The user name has to be entered as allocated by company
Password (M):
The password has to be entered as allocated by Company
Submit:
When submit button is pressed the system will verify user name and password and
will give access to OES to user as per security.
In case of wrong user name and password it will ask the user to enter user name
and password again (three trial) after that the user will be blocked.
Cancel:
Cancel button will refresh user name and password text box.
APPLICATION FORMS
Form Name : Company Master
Module : Order Execution System
Form Type : Master
Short Name : OEM01
Purpose :
The system will maintain the name of various Company with whom 3P’s business
will operate.
Business Rules:
This master will maintain
different company under which 3P business has to be classified
Company Code (A):
The code will be auto generated in a sequence for each company created.
Company Name (M):
The user is to enter the name of the company, which is to be created.
Company Short Name (M):
Short name of the company. This will be referred in future during the
transactions.
E.g. For a company created as ‘3P Executive Search
Pvt. Ltd.’ the short name could
be ‘TPE’ to be referred in future transactions for the company.
Business start date (M)
The user is to select the business start date.
Account Start Date (M)
The user is to select the account start date. The Account start date should be
less than or equal to the business start date. The Account start date will be
the starting date of the first financial year. No transactions will be entered
before this date.
PAN Number (M)
The permanent account number for the company.
Address Line 1 (O)
The user can enter Address of Company.
Address Line 2 (O)
The user can enter Address of company.
City (O)
The user can enter City of Company.
State (O)
The user can enter State of Company.
Country (O)
The user can select Country of Company.
PIN Code (O)
The user can enter Pin code of Company.
Phone (O)
The user can enter Telephone no of Company. Multiple numbers can be stored
using a ‘,’ to separate two or more numbers.
Fax No. (O)
The user can enter Fax Company. Multiple numbers can be stored using a ‘,’ to
separate two or more numbers.
Email (O)
The user can enter E-mail of the company. Multiple e-mails can be stored using
a ‘,’ to separate two or more numbers.
Form Name : Division Master
Module : Order Execution System
Form Type : Master
Short Name : OEM02
Purpose :
The system will maintain the name of various divisions for any particular
company.
Business Rules:
This master will maintain
different divisions under a particular company.
Division Code (A)
The code will be auto generated in a sequence for each Division created.
Division (M)
The user is to enter the name of the Division which is to be created.
Remarks (O)
Any description/remarks for the Division.
Example:
3P Consultants Pvt. Ltd. as a company can work in multiple divisions such as
Executive Search, Information Technology etc.
Form Name : Branch Master
Module : Order Execution System
Form Type : Master
Short Name : OEM03
Purpose :
The system will maintain the details of various Branches under each company
Business Rules:
Business transactions will be
carried out only for Branch, which have been created in the Branch Master.
Branch Code (A)
The code will be auto generated in a sequence for each Branch created.
Branch Name (M)
The user is to enter the name of the Branch, which is to be created.
Business Start Date (M)
The user will select the business start date of the branch
Branch Manager (O)
The user needs to enter Name of Branch Manager of the branch.
Address Line 1 (O)
The user can enter Address of the branch
Address line 2 (O)
The user can enter Address of the branch
City (O)
The user can enter City of the branch
State (O)
The user can enter State of the branch
Country (O)
The user can select Country of the branch, this country should be specified in
country master.
Pin (O)
The user can enter Pin code of the branch.
Telephone (O)
The user can enter Telephone no of the branch. Multiple numbers can be stored
using a ‘,’ to separate two or more numbers.
Email (O)
The user can enter E-mail of the branch. Multiple e-mails can be stored using a
‘,’ to separate two or more numbers.
Fax (O)
The user can enter Fax of the branch. Multiple numbers can be stored using a
‘,’ to separate two or more numbers.
Form Name : Financial Year
Master
Module : Order Execution System
Form Type : Master
Short Name : OEM04
Purpose :
All transaction will be created in a financial year.
Business rule:
Every company will have a
separate financial year, which will have to be created before doing any
transaction. The screen is provided with a dynamic table, which will show six
records at a time, which will increase when the user has to enter more no. of records.
Sr. No. (A):
The Sr. no. will be auto generated in series
Start Date (D):
The first financial start date will be account start date entered in company
master. For subsequent financial year the start date would be the immediate
next date after the end date of previous financial year.
End Date (M):
The user needs to enter end date of the financial year.
Form Name : Currency Master
Module : Order Execution System
Form Type : Master
Short Name : OEM05
Purpose :
The various currencies through which 3P carries out its business will be
created through this master.
Business Rule:
Business transactions will be
carried out only in the currencies created hereby. Whenever a company is
created a record with currency name ‘Indian Rupees’ and Currency Short Name
‘INR’ will be auto generated.
Currency Code (A):
The code will be auto generated in a sequence for each Currency defined.
Currency Name (M):
The user is to enter the name of the Currency, which is to be created.
Currency Short Name (M):
The user is to enter the short name of the currency.
Currency Description (O):
Any description for the Currency.
Example:
A currency can be created with name as ‘US Dollar’ and short name as ‘USD’.
Form Name : Country Master
Module : Order Execution System
Form Type : Master
Short Name : OEM06
Purpose :
The system will maintain the name of various Countries.
Business Rules:
Business transactions will be
carried out only with the countries created hereby.
Country Code (A):
The code will be auto generated in a sequence for each Country created.
Country (M):
The user is to enter the name of the Country, which is to be created.
Form Name : Industry Master
Module : Order Execution System
Form Type : Master
Short Name : OEM07
Purpose :
The system will maintain the names of various industries.
Business Rules:
Business transactions will be
carried out only in Industries, which have been listed in the Industry
Information screen.
Industry Code (A):
The code will be auto generated in a sequence for each Division created.
Industry Name (M):
The user is to enter the name of the Industry, which is to be created.
Remarks (O):
Any description for the Industry
Form Name : Parent Group
Master
Module : Order Execution System
Form Type : Master
Short Name : OEM08
Purpose :
The system will maintain the name of Group Company to which a client belongs.
Business Rules:
The Client may be part of a
particular Group Company; this client has to be associated with that Group
Company.
Parent Group Code (A):
The code will be auto generated in a sequence for each Parent Group created.
Parent Group Name (M):
The user is to enter the name of the Parent Group, which is to be created.
Form Name : Designation Level
Master
Module : Order Execution System
Form Type : Master
Short Name : OEM09
Purpose :
The system will maintain the name of various Designation levels as defined by
the user.
Business Rules:
Business transactions will be
carried out only for designation level, which have been created in the
Designation Level Master.
Designation Level Code (A):
The code will be auto generated in a sequence for each Designation Level
created.
Designation Level Name (M):
The user is to enter the name of the Designation level, which is to be created.
Designation Level Description
(O):
Any description for the Designation Level
Designation Type (M):
Radio button to specify whether it is for ‘external Use’ (default), ‘Internal
Use’ or ‘Common’.
The Designation marked ‘internal’ will be only available to specify designation
of the 3P employee and not in other transaction like inquiry, proposal etc.
whereas the Designation (Continuation of Designation Level Master) …marked as
‘external’ will not be available for employee. And designation marked as Common
will be available for all transaction and master wherever required.
Form Name : Client Master
Module : Order Execution System
Form Type : Master
Short Name : OEM10
Purpose :
The system will maintain the details of various Clients of 3P.
Client Master Fields (from
screen):
Header Section:
- Last Date of Update
- Date of Entry (default shown: 01/01/2000)
- Client Code
- Client Name
- Industry Name (dropdown)
- Parent Group Name (dropdown)
- Source of Information
- Company Profile
- Product(s)
- Web Site
- Joint Venture Details
- Technical Collaboration
- Sales Turn Over
- Year
- CIN
- Remark
Client Details Section:
- Contact Person
- Designation
- Correspondence Address
Client Master (continued –
Screen Layout)
Correspondence Address
- Address Line 1
- Address Line 2
- City
- State
- Country
- PIN
- Telephone
- Fax
- E-mail
Registered Address
- Address Line 1
- Address Line 2
- City
- State
- Country
- PIN
- Telephone
- Fax
- E-mail
Factory Details
- Name of Factory
- Personnel Manager
- Address
- City
- State
- Country
- Pin
Top Management Details
- Name
- Designation
- Phone
- E-mail
- Edit / Delete
Executive Details
- Name
- Designation
- Function
- Remarks
- Edit / Delete
Business Rules (Client Master
Continued):
Business transactions will be
carried out only with Clients, which have been created in the Client Master.
Last date of update (A):
The last date of update will automatically take the system date for each Client
which will specify when the record was last updated in the list mode.
Client Code (A):
The code will be auto generated in a sequence for each Client created.
Date of Entry (M):
Date of entry is the date when first time the record was created.
Client Name (M):
The user is to enter the name of the Client, which is to be created.
Industry (O):
The user will enter industry under which the client is to be classified. The
drop-down will contain all records created under Industry Master.
Parent Group (O):
The user will enter the Parent group for client if the client is part of some
Group, this Group has to be created in parent group master.
Example: Reliance Industries is parent group for Reliance Petroleum.
Source of Information (O):
A textbox where the user can enter the source of the information of client
details.
Client Master (Field
Definitions Continued)
Company Profile (O)
A textbox where the user can enter company profile in text box.
Products (O)
A textbox where the user can enter the details of Products in which client is
dealing.
Website (O)
The user can enter URL of the website of client.
JV Details (O)
A textbox where the user can enter the details of Joint venture, if client has
joint venture with other Company / organization.
Technical Collaboration (O)
A textbox where the user can enter details of technical collaboration, if
client has technical collaboration with some other company/organization.
Sales Turnover (O)
The user will enter the sales turnover of the company.
Year (O)
The year for which the sales turnover is entered. Though this is optional it
becomes mandatory in case the user enters the sales turnover.
CIN (O)
The user can enter the company index no of the client as assigned by ROC.
Remarks (O)
A textbox where the user can enter any specific remarks/notes for client.
Contact Person (O)
The user needs to enter Name of contact person at client side
Designation (O)
The user needs to enter Designation of the Contact person, this designation
will be taken from the designation level master which are specified as external
or common
Correspondence Address
Address Line 1 (O)
The user can enter Address for Correspondence of client
Address Line 2 (O)
The user can enter Address for Correspondence of client
City (O)
The user can enter City of correspondence address of client
State (O)
The user can enter State of correspondence address of client
Country (O)
The user can enter Country of Correspondence address of client, this country
should be specified in country master.
Client Master (Field
Definitions Continued)
Pin (O)
The user can enter Pin code of correspondence address Client
Telephone (O)
The user can enter Telephone no of correspondence with client. Multiple numbers
can be stored using a ‘,’ to separate two or more numbers.
Fax (O)
The user can enter Fax for correspondence with client. Multiple numbers can be
stored using a ‘,’ to separate two or more numbers.
Email (O)
The user can enter E-mail for correspondence with client. Multiple e-mails can
be stored using a ‘,’ to separate two or more numbers.
Registered Address
Registered Address Line 1 (O)
The user can enter client’s Registered office Address
Address Line 2 (O)
The user can enter client’s Registered office Address
City (O)
The user can enter City of Registered office of client
State (O)
The user can enter State of Registered office of client
Country (O)
The user can enter Country of Registered office of client. This country should
be specified in country master.
Pin (O)
The user can enter Pin code of Registered address Client
Telephone (O)
The user can enter Telephone no of Registered with client. Multiple numbers can
be stored using a ‘,’ to separate two or more numbers.
Fax (O)
The user can enter Fax for Registered with client. Multiple numbers can be
stored using a ‘,’ to separate two or more numbers.
Email (O)
The user can enter E-mail for Registered with client. Multiple e-mails can be
stored using a ‘,’ to separate two or more numbers.
Factory Details (Multiple)
The user will be able to maintain
details of multiple factory
Name of Factory (O)
The user can enter Name of the factory
Personnel Manager (O)
The user can enter Name of the personnel manager at factory
Factory Address (O)
The user can enter Factory address of client
City (O)
The user can enter City of Factory address of client
State (O)
The user can enter State of Factory address of client
Client Master (Field
Definitions Continued)
Country (O)
The user can enter Country of Factory address of client
Pin (O)
The user can enter Pin code of Factory address Client
Telephone (O)
The user can enter Telephone no of factory with client. Multiple numbers can be
stored using a ‘,’ to separate two or more numbers.
Fax (O)
The user can enter Fax for Factory with client. Multiple numbers can be stored
using a ‘,’ to separate two or more numbers.
Email (O)
The user can enter E-mail for Factory with client. Multiple e-mails can be
stored using a ‘,’ to separate two or more numbers.
Website (O)
The user can enter URL of the website of the factory.
Top Management Details
The user will be able to maintain
details of multiple executive (Top management) for a client
Name (O)
The user to enter Name of the executive
Designation (O)
The user can enter Designation of executive which will be in designation level
master and specified as external / common
Phone (O)
The user can enter Telephone no.
Email (O)
The user can enter E-mail.
Executive Details (Multiple)
The user will be able to maintain
details of multiple executive for a client
Name (O)
The user needs to enter Name of the executive
Designation (O)
The user can enter Designation of executive which will be in designation level
master and specified as external / common
Function (O)
The user can enter Function area of executive, which will be in function
master.
Remarks (O)
Any description/remark for the executive.
Form Name : Function Master
Module : Order Execution System
Form Type : Master
Short Name : OEM11
Purpose :
The system will maintain the name of various Functions to be used during the
course of business.
Business Rules:
Business transactions will be
carried out only for Function, which have been created in the Function Master.
Function Code (A):
Auto generated code for each function created by the user.
Function (M):
The user is to enter the name of the Function, which is to be created.
Function Description (O):
The user can enter any description/remarks for the Function.
Function Type (M):
Radio button to specify whether it is for ‘external Use’ (default), ‘Internal
Use’ or ‘Common’.
marked ‘internal’ will be only
available to specify designation of the 3P employee and not in other
transaction like inquiry, proposal etc. whereas the Function marked as
‘external’ will not be available for employee. And function marked as Common
will be available for all transaction and master wherever required.
Form Name : Ally Master
Module : Order Execution System
Form Type : Master
Short Name : OEM12
Purpose :
The system will maintain the name of various Allies.
Business Rules:
Business transactions will be
carried out only with Ally, which have been created in this Master.
Ally Code (A):
The code will be auto generated in a sequence for each Ally created.
Ally Name (M):
The user is to enter the name of the ally level, which is to be created.
Commission Rate (M):
The user need to enter Commission rate given to ally on selection of the
candidate from inquiry coming from them or for ally’s candidate placed by 3P.
Remarks (O):
Any description/remarks for the Ally.
Form Name : Billing Cycle
Master
Module : Order Execution System
Form Type : Master
Short Name : OEM13
Purpose :
The system will maintain various phase of billing to be specified in proposal
Business Rules:
Business transactions will be
billed only for those phases, which have been created in this master.
Phase Code (A):
The code will be auto generated in a sequence for each Phase created.
Phase Description (M):
The user is to enter the Description for the phase, which is to be created.
Form Name : Perk Master
Module : Order Execution System
Form Type : Master
Short Name : OEM14
Purpose :
The system will maintain the details of Perk for different level.
Business Rules:
Business transactions will be
carried out only for perk, which have been created in the Perk Master. This
perk will be considered to generate invoice if the compensation details of the
candidate is not provided.
Perk Code (A):
The code will be auto generated in a sequence for each Perk created.
Perk Name (M):
The user is to enter the name of the perk, which is to be created.
Standard cost at Sr. level
(M):
Perk to be consider for candidate (in Rs.)
Standard cost at Middle level
(M):
Perk to be consider for candidate (in Rs.)
Standard cost at Jr. level
(M):
Perk to be consider for candidate (in Rs.)
Form Name : Out of Pocket
Expenses
Module : Order Execution System
Form Type : Master
Short Name : OEM15
Purpose :
The system will maintain the name of various Cost head for out of pocket
expense.
Business Rules:
Business transactions will be
carried out only for out of pocket expense, which have been created in the out
of pocket expense Master.
Cost head Code (A):
The code will be auto generated in a sequence for each Cost head created.
Cost head Name (M):
The user is to enter the name of the cost head, which is to be created.
Description (O):
The user will enter any description/remarks for the Cost head.
Form Name : Communication Type
Master
Module : Order Execution System
Form Type : Master
Short Name : OEM16
Purpose :
The system will maintain the name of various type of communication mode through
which consultant interacts with the client or customer.
Business Rules:
Business transactions will be
communicated only in the modes which have been created in this master.
Communication Mode Code (A):
The code will be auto generated in a sequence for each communication mode
created.
Communication Mode Name (M):
The user is to enter the Name of the Communication Mode, which is to be
created, through which the consultant interacts with the client or the
customer.
Communication Description (O):
The user may enter any description/remarks for the Communication.
Form Name : Media Master
Module : Order Execution System
Form Type : Master
Short Name : OEM17
Purpose :
The system will maintain the name of various media used for the assignment.
Business Rules:
Advertisements will be done only
through the medias, which have been created in this master.
Media Code (A):
The code will be auto generated in a sequence for each Media created.
Media Name (M):
The user is to enter the name of the Media, which is to be created (Times of
India, Data Quest etc.)
Media Description (O):
The user can enter any description for the Media
Form Name : Activity Master
Module : Order Execution System
Form Type : Master
Short Name : OEM18
Purpose :
The system will maintain the name of various kinds of Project Activity / Follow
up activity during an assignment.
Business Rules:
Project planning will be done out
only for Activity, which have been created in the Activity Master. Activity
which are mandatory in for project plan will be for hard coded for which only
Std. Time can be changed. The 9 activities mentioned in project plan viz.
Inquiry, Proposal, Sales Order, Adv. Detail, Candidate listing and head
hunting, Preliminary Screening, Resume sent, interview and compensation details
will be system generated for each company created.
Activity Code (A):
The code will be auto generated in a sequence for each Activity created.
Activity Name (M):
The user is to enter the Name of the Project Activity / Follow up activity,
which is to be created.
Std. Time (M):
Std. Time has to be entered for each project activity. Standard time is defined
as the time required to complete the activity in days.
Activity Type (M):
Radio button to enter whether it is a ‘Project activity’ (default), ‘Follow UP
activity’ or ‘both’. The Activity which is specified for Project activity will
be only available for the project plan and related activity, whereas the
activity specified for Follow up activity will be available only for Client
follow up and candidate follow up transaction. And activity specified, as
common will be available for both project plan and Follow up (Client &
candidate)
Form Name : Reason Master
Module : Order Execution System
Form Type : Master
Short Name : OEM19
Purpose :
The system will maintain the name of various Standard reasons for which
candidate rejected / Candidate not joined / Forced closure / Proposal rejected.
Business Rules:
The reasons created under the
different heads viz. candidate rejected, Candidate not joined, Forced closure,
Proposal rejected will be used in the transactions to specify the reason
Reason Code (A):
The code will be auto generated in a sequence for each Reason created.
Reason Type (M):
The user need to classify reason into various category (candidate rejected /
Candidate not joined / Forced closure / Proposal rejected). This reason will be
available only under that category during various transaction
Reason (M):
The user is to enter the name of the standard reason, which is to be created.
Form Name : Employee Master
Module : Order Execution System
Form Type : Master
Short Name : OEM20
Purpose :
The system will maintain the name of various Employees of 3P.
Business Rules:
For an employee to become an
authenticate user of the system it is required to create his/her record in this
master. The system administrator will assign the role and privileges to each
user to give restrict the access of the user.
Employee Code (A):
The code will be auto generated in a sequence for each Employee created.
Employee Name (M):
The user is to enter the name of the employee, which is to be created.
Designation (M):
The user is to enter the Designation of employee. This designation will have to
be selected from designation level master and only those marked either as
‘internal’ or ‘common’ will appear.
Consultant (O):
Check Box to specify whether employee is a Consultant. Only those specified as
consultant will be shown in transaction under consultant drop down wherever
applicable.
Form Name : Rate Contract
Master
Module : Order Execution System
Form Type : Master
Short Name : OEM21
Purpose :
In case of rate contract with client, consultant should be able to see the rate
contract while making proposal.
Business Rule:
The rate contract can be with the
company or parent company (Group). Rate contract will be captured in form of
free text only
Date (M):
The user needs to enter date of contract
Client Parent Group (M):
In case of rate contract with group company user needs to select parent group,
which is entered in parent group master.
Client Name (M):
In case of rate contract with client the user needs to select client name,
which is entered in client master.
Description of contract (M):
The user needs to enter contract details.
Form Name : Inquiry
Module : Order Execution System
Form Type : Transaction
Short Name : OET01
Purpose :
The system should be able to capture details of inquiry from various sources.
The system would record details of inquiry.
Inquiry Screen Fields:
Header Section:
- Inquiry No
- Type of inquiry
- Date of inquiry
- Consultant
Client Details Section:
- Client Name
- Correspondence Address 1
- Address 2
- City
- State
- Country
- Pin
- Telephone
- Fax
- E-mail
Vacancy Details Section:
- Name of Vacancy
- No of Vacancies
- Expected date of sending proposal (default shown:
21/11/2000)
- Designation level
Inquiry (Business Rules
Continued)
Inquiry is the first stage of
the order execution.
Inquiry No. (A):
Inquiry no. will be auto generated in sequence as created by the user.
Type of inquiry (M):
The inquiries may come through any mode of communication for eg. through
e-mail, fax, website, telephone, personal meetings, snail mail etc. The drop
down will get populated by communication type master. The mode of inquiry is to
specify by the user. A separate screen is provided for those inquiries coming
through the shopping cart in form of e-mail.
Date of inquiry (M):
The date on which the inquiry is received is to be specified. The inquiry date
will automatically take the system date, but the user will have the option of
changing the date.
Consultant (M):
Each inquiry is to be handled by a consultant. Automatically a consultant will
be assigned based on the user name through which the system has been logged on.
The user will have the option to change the consultant name.
Client Detail
Client Name (M):
The client name is mandatory and the list of value will be populated from the
client master.
Corresp. Address (D):
Address for Correspondence of client (line 1) will be displayed
Inquiry (Field Definitions
Continued)
Address2 (D):
Address for Correspondence of client (line 2) will be displayed
City (D):
City of correspondence address of client will be displayed
State (D):
State of correspondence address of client will be displayed
Country (D):
Country of Correspondence address of client will be displayed
Pin (D):
Pin code of correspondence address of Client will be displayed
Telephone (D):
Telephone no of correspondence with client will be displayed
Fax (D):
Fax No. for correspondence with client will be displayed
Email (D):
E-mail for correspondence with client will be displayed
Vacancy Detail (Multiple)
Each inquiry will contain
vacancy, which can be for multiple positions. The user will enter the vacancy
details such as name of vacancy, number of vacancy and other details pertaining
to a vacancy.
Name of vacancy (M):
The user will enter the name of the vacancy to be filled
No. of vacancy (M):
The user will enter the no. of vacancy available for the specified vacancy.
Expected date of sending the
proposal (M):
The user will select the expected date on which the proposal will be sent to
the client.
Designation Level (M):
The user will select the designation for the name of vacancy as Per
Industry-Norm which will be populated from the designation level master those
marked as either as ‘External’ or ‘Common’.
Function (M):
The user will select the function for the vacancy, which will be populated from
the industry master.
Industry Background (M):
The user will select the function for the vacancy, which will be populated from
the industry master.
Search Mode (M):
The user will specify the mode of candidate search for the particular vacancy.
The search/selection procedure can be through multiple modes and can be through
advt., data search or head hunting. The user will have to specify at least one
mode of search
Educ. Qualification (O):
The user will enter the educational qualification needed for the vacancy.
Position (M):
The user will select the type of position to be filled. It can either be a
‘Temporary’ or ‘Permanent’. The default position will be ‘Permanent’.
Experience (Min) (O):
The user will enter the minimum experience needed for the vacancy.
Age (max) (O):
The user will enter the maximum age limit for the vacancy.
Approx. Gross Ann. Salary (O):
The user will enter the approximate Annual gross salary offered by the client
for the vacancy.
Currency (O):
The user will enter the currency in which the transactions will be done. The
drop-down will get populated from the currency master.
Posting City (O):
The user will enter the city of posting of the vacancy.
Additional Vacancy Fields
Country (O):
The user will enter the country of posting for the vacancy.
The drop-down will get populated from the country master.
Languages (O):
The user will enter the language needed for the vacancy.
Multiple language can be added by separating it by ‘;’.
Job Description (O):
The user will enter the job description of the vacancy.
Hours (Full Time) (O):
The user will enter the hours (full time) needed for the vacancy to be put in
by the candidate.
Hours (Part Time) (O):
The user will enter the hours (part time) needed for the vacancy to be put in
by the candidate.
Resume Forwarding Details
Each vacancy will have a separate
resume forwarding details.
Automatically the Corresponding address details of the client will be
displayed.
The client will have the option of changing the resume forwarding details.
Contact Person (O):
The user will enter the contact person to which the resume has to be forwarded.
Corresp. Address (O):
Address for Correspondence of client (line 1) will be displayed
Address2 (O):
Address for Correspondence of client (line 2) will be displayed
City (O):
City of correspondence address of client will be displayed
State (O):
State of correspondence address of client will be displayed
Country (O):
Country of Correspondence address of client will be displayed
Pin (O):
Pin code of correspondence address of Client will be displayed
Telephone (O):
Telephone no of correspondence with client will be displayed
Fax (O):
Fax No. for correspondence with client will be displayed
Email (O):
E-mail for correspondence with client will be displayed
Resume Forwarding Details
Each vacancy will have a separate
resume forwarding details.
Automatically the Corresponding address details of the client will be
displayed.
The client will have the option of changing the resume forwarding details.
Contact Person (O):
The user will enter the contact person to which the resume has to be forwarded.
Corresp. Address (O):
Address for Correspondence of client (line 1) will be displayed
Address2 (O):
Address for Correspondence of client (line 2) will be displayed
City (O):
City of correspondence address of client will be displayed
State (O):
State of correspondence address of client will be displayed
Country (O):
Country of Correspondence address of client will be displayed
Pin (O):
Pin code of correspondence address of Client will be displayed
Telephone (O):
Telephone no of correspondence with client will be displayed
Fax (O):
Fax No. for correspondence with client will be displayed
Email (O):
E-mail for correspondence with client will be displayed
Form Name : Inquiry Through
Shopping Cart
Module : Order Execution System
Form Type : Transactions
Short Name : OET02
Purpose :
The screen would help in converting the inquiries coming through the shopping
cart into an Inquiry.
Shopping Cart Inquiry Table
Fields:
- Sr. No
- Client Name
- Vacancy Name
- No of Vacancy
- Location
- Convert to Inquiry (Button)
- Delete (Button)
Business Rule:
The Cyril system will give the
inquiries by shopping cart in a temp table.
The details of the shopping cart will be displayed for all the shopping cart
inquiry that are not converted into inquiry.
When the user presses the Convert
button:
- Shopping cart inquiry opens in inquiry form
- All available details are pre-filled
- Type of inquiry = Shopping Cart
- User enters missing details
After saving:
- User is returned to shopping cart inquiry screen
- Converted entries will NOT be shown again
If Delete button is
pressed:
- Shopping cart entry is deleted
- It will NOT be converted into inquiry
Sr. No. (A):
Auto-generated in series
Client Name (D):
The client name as in shopping cart temporary file will be displayed
Shopping Cart Inquiry Fields
Vacancy Name (D):
The vacancy name as in shopping cart temp file will be displayed.
No of Vacancy (D):
The no. of vacancies as in shopping cart temp file will be displayed.
Location (D):
The location as in shopping cart temp file will be displayed.
Convert to Inquiry:
Button to convert inquiry in shopping cart into inquiry.
Delete Inquiry:
Button to delete shopping cart.
Form Name : Proposal
Module : Order Execution System
Form Type : Transaction
Short Name : OET03
Purpose :
The system should be able to capture details of Proposal.
Proposal Screen Fields
Header Section
- Proposal Date (default shown: 21/11/2000)
- Proposal No
- Client Name
- Inquiry No
- Type of Proposal (e.g., Flat Rate)
- Name of Vacancy
- No of Vacancy
- Designation
- Function
Terms and Conditions Section
Unit:
- Percentage / Value
Currency
Rate
Professional Fees
Amount (in Rs)
Minimum Fees
Amount (in Rs)
Out of Pocket Expenses Section
- Cost Head
- Total Amount
- Total Amount (Rs.)
- Edit
- Delete
Proposal Screen Continuation)
Out of Pocket Expenses Section
- Cost Head
- Total Amount
- Total Amount (Rs.)
- Edit / Delete
Billing Cycle Details
- Activity Phase
- Particulars
- Total Amount
- Remarks
- Edit / Delete
(Max multiple rows allowed)
Confirmation Details
- Proposal Accepted (Yes / No)
- Confirmation Date
- Reason of Non-Acceptance
Core Rule
👉 Proposal is the next
step after Inquiry
- One proposal is created per vacancy
- Multiple vacancies → Multiple proposals per inquiry
Field Logic
Proposal Date (M):
- Defaults to system date
- User can modify
Proposal No (A):
- Auto-generated sequence
Client Name (M):
- Only those clients visible for which inquiry exists
Inquiry (M):
- Select inquiry for proposal
Type of Proposal (M):
- Flat Rate
- % Rate
- Turnkey
Vacancy Mapping
Name of Vacancy (M):
- Populated based on selected inquiry
No of Vacancy (D):
- Auto displayed
Designation (D)
Function (D)
- Auto populated
Pricing Logic
Unit (M):
- Percentage OR Value
Rules:
- Flat Rate → Value
- % Rate → Percentage
- Turnkey → Either
Currency (D):
- Auto displayed
Rate (M):
- Currency conversion to INR
- If INR → rate = 1 (locked)
Professional Fee (M):
- Entered by user
Amount (Rs.) (D):
- Calculated = Fee × Rate
Minimum Fee (O):
- Entered
Amount (Rs.) (D):
- Calculated = Min Fee × Rate
Out of Pocket Expenses:
- Auto-loaded from master
- Editable
Proposal – Advanced Logic)
Out of Pocket Expense Details
Cost Head (M):
- From master
Amount (M):
- Entered in selected currency
Amount (Rs.) (D):
- Calculated = Amount × Rate
Billing Cycle Details
- Max 6 billing cycles allowed
Activity Phase (M):
- From billing cycle master
Particulars (M):
- Description
Total Amount (M):
- Entered
Total Amount (Rs.) (D):
- Calculated = Total × Rate
Remarks (M):
- Adjustable / Non-adjustable
Proposal Status Logic
Proposal Accepted (O):
- Yes / No
- Default = blank
If YES:
- Confirmation Date → Mandatory
- Reason field → Disabled
If NO:
- Reason of Non-Acceptance → Mandatory
- Dropdown from Reason Master
- Confirmation Date → Disabled
Form Name : Proposal Amendment
Module : Order Execution System
Form Type : Transaction
Short Name : OET04
Purpose :
The system should allow the user to make changes into proposal if required
Amended Proposal – Header
Fields
- Client Name
- Original Proposal No
- Inquiry No
- Type of Proposal (e.g., Flat Rate)
- Proposal Date (default shown: 21/11/2000)
- Amendment No
Terms and Conditions (Same as
Proposal)
- Unit (Percentage / Value)
- Currency
- Rate
- Professional Fees
- Amount (Rs.)
- Minimum Fees
- Amount (Rs.)
Out of Pocket Expenses
- Cost Head
- Total Amount
- Total Amount (Rs.)
- Edit / Delete
Billing Cycle Details (Same as
Proposal)
- Activity Phase
- Particulars
- Total Amount
- Remarks
- Edit / Delete
Confirmation Details
- Amended Proposal Accepted (Yes / No)
- Confirmation Date
- Reason of Non-Acceptance
Business Rule: Proposal
Amendment
- Proposal amendment is done to modify an unaccepted
proposal
- Helps track changes across versions
- Can be done at any stage of order execution
- ❗ Only allowed if invoice
has NOT been generated
- ❗ Once amended → original
proposal cannot be deleted (history preserved)
Field Logic
Client Name (M):
User selects client → only those clients shown for which proposals exist
Original Proposal (M):
User selects proposal to amend → only proposals of selected client shown
Inquiry (D):
Auto-populated based on selected proposal
Type of Proposal (M):
Auto-filled from original proposal
Options: Flat Rate / % Rate / Turnkey
User can modify
Proposal Date (M):
Auto-filled from original
User can modify
Amendment No (A):
Auto-generated sequence
- First proposal → Amendment No = 0
- Next amendments → 1, 2, 3…
Pricing Fields (Inherited +
Editable)
Unit (M):
Auto from proposal
User can change
Rules:
- Flat Rate → Value
- % Rate → Percentage
- Turnkey → Either
Currency (D):
Auto-filled
Rate (M):
Auto-filled
User can modify
Professional Fee (M):
Auto-filled
User can modify
Financial & Billing Logic
(Amendment)
Amount Calculations
Amount (Rs.) (D):
= Professional Fee × Rate
Minimum Fee (O):
Auto-filled
User can modify
Minimum Amount (Rs.) (D):
= Minimum Fee × Rate
Out of Pocket Expenses
Auto-loaded from proposal
User can:
- Add
- Modify
- Delete
Cost Head (M):
From master
Amount (M):
Entered
Amount (Rs.) (D):
= Amount × Rate
Billing Cycle Details
Auto-loaded from proposal
User can:
- Modify
- Delete
- Add new
Activity Phase (M):
From Activity Master (Project Activity only)
Particulars (M):
Description
Total Amount (M):
Entered
Total Amount (Rs.) (D):
= Total × Rate
Remarks (M):
Dropdown:
- Adjustable
- Non-Adjustable
Form: Sales Order (OET05)
Module: Order Execution System
Type: Transaction
Purpose:
- Generate unique Sales Order Number (SON)
- Capture complete Sales Order details
📄 Page 55 – Screen
Structure
🔹 Sales Order Header
- Sales Order No
- SON Date
- Client
- Proposal No
🔹 Corresponding Address
- Address Line 1
- Address Line 2
- City
- State
- Country
- PIN
- Telephone No
- Fax
- Email
🔹 Sales Order Details
- Name of Vacancy
- No. of Vacancies
- Designation
- Function
🔹 Search Mode
Options:
- Advertising
- Head Hunt
- Data Search
🔹 Advance Details
- Advance Amount
- Date of Receipt of Advance
- Currency
- Rate
🔹 Schedule Dates For
- Identification of prospective candidates
- Completion of preliminary interview
- Sending resumes to client
Business Rules
🔹 Core Rule
- Sales Order is the next step after Proposal
- Every proposal → one separate Sales Order
🔹 Field Logic
Sales Order No (A):
- Auto-generated
- Sequential based on previous sales orders
SON Date (M):
- Defaults to system date
- User can modify
Client (M):
- User selects client
- Only clients with proposals shown
Proposal No (M):
- User selects proposal
- Only proposals of selected client shown
Corresponding Address (D):
Auto-populated from client
master:
- Address Line 1
- Address Line 2
- City
Sales Order (Continued
Business Rules)
🔹 Auto-Populated Address
Fields (D)
These fields are fetched from Client
Master:
- State → Correspondence address state
- Country → Correspondence address country
- PIN → Postal code
- Telephone → Client contact number
- Fax → Fax number
- Email → Email ID
🔹 Vacancy Details (From
Proposal)
- Name of Vacancy (D) → From selected proposal
- No. of Vacancy (D) → From proposal
- Designation (D) → From proposal
- Function (D) → From proposal
🔹 Search Mode (D)
Auto-displayed based on proposal:
- Head Hunting
- Advertisement
- Data Search
Advance Details
- Advance Amount (O) → User enters amount
- Date of Receipt (O) → Optional but:
- ❗ Mandatory if advance is
entered
🔹 Currency & Rate
- Currency (D) → Auto from proposal
- Rate (D) → Auto from proposal
🔹 Schedule Dates
(Optional Fields)
User can define timeline
milestones:
- Identification of candidates
- Completion of preliminary interview
- Sending resumes to client
➡ All are optional fields
Project Plan (OET06)
🔹 Form Overview
Form Name: Project Plan
Module: Order Execution System
Type: Transaction
Short Name: OET06
🔹 Purpose
- Plan project schedule
- Track assignment progress
- Generate monitoring reports
🔹 Project Plan Header
- Client
- Project Plan No
- Sales Order No
- Consultant
- Plan Type:
- Original Project Plan
- Revised Project Plan
Search Mode (Inherited)
- Advertising
- Head Hunt
- Data Search
🔹 Core Planning Table
|
Field |
Description |
|
Activity Code |
Unique identifier |
|
Activity Name |
Stage of process |
|
Start Date |
Planned start |
|
Due Date |
Expected completion |
|
End Date |
Actual completion |
|
Standard Time |
Expected duration |
🔹 Predefined Workflow
Activities
This is very important 👇
(Your system logic backbone)
- Inquiry
- Proposal
- Sales Order
- Advertisement Details
- Candidate History & Head Hunting
- Preliminary Screening
- Resume Sent
- Interviews
- Compensation Details
🔹 Other Activity Details
- Custom activities can be added
- Extensible workflow
Project Plan (Business Rules –
Core Logic)
🔹 Project Type (M)
User must choose:
- Original Project Plan (default)
- Revised Project Plan
👉 This introduces version
control for execution
🔹 Original Project Plan –
Rules
Client (M)
- Only clients with Sales Orders are shown
Project Plan No (A)
- Auto-generated
- Sequential
Sales Order No (M)
- User selects Sales Order
- Filtered by client
Consultants (D)
- Auto-filled from:
- Inquiry → Proposal → Sales Order
👉 This ensures ownership
continuity
Search Mode (D)
- Head Hunting
- Advertisement
- Data Search
👉 Inherited from earlier
stages
Activity Details (Multiple)
- Auto-loaded based on proposal
- User can:
- Modify
- Delete
- Add
Activity Execution Rules
🔹 Activity Code (D)
- Auto-displayed when activity selected
🔹 Activity Name (M)
Dropdown populated from Activity
Master
Includes:
🔸 System-generated 9
Mandatory Activities:
- Inquiry
- Proposal
- Sales Order
- Advertisement Detail
- Candidate Listing & Head Hunting
- Preliminary Screening
- Resume Sent
- Interviews
- Compensation Details
🔸 Additional Logic
- User can add custom activities
- Activities tagged as:
- Project Activity
- Common
🔸 Smart Rule
❗ If Search Mode ≠ Advertising
→ Disable “Advertisement Detail” activity
👉 This is conditional
workflow logic (very advanced for 2000!)
🔹 Dates Handling
|
Field |
Rule |
|
Start Date (M) |
User enters |
|
Due Date (M) |
User enters |
|
End Date (O) |
Entered after completion |
🔹 Standard Time (D)
- Pulled from Activity Master
- Used to calculate:
👉 Variance = Actual vs
Planned
Project Plan (Final Execution
Logic)
🔹 Activity Intelligence
(VERY IMPORTANT)
System enforces:
👉 9 Mandatory
Activities (Auto-generated)
- Inquiry
- Proposal
- Sales Order
- Advertisement Detail
- Candidate Listing & Head Hunting
- Preliminary Screening
- Resume Sent
- Interviews
- Compensation Details
🔹 Dynamic Behavior
- User can add extra activities
- Activities categorized as:
- Project Activity
- Common
🔹 Smart Conditional Rule
❗ If Search Mode ≠ Advertising
→ Disable Advertisement Detail
👉 This is rule-based
workflow branching
🔹 Execution Tracking
Fields
|
Field |
Logic |
|
Start Date (M) |
User inputs |
|
Due Date (M) |
User inputs |
|
End Date (O) |
Actual completion |
|
Std Time (D) |
From Activity Master |
🔹 Core Concept
👉 System supports:
Planned vs Actual Tracking
Variance = (End Date - Start
Date) - Std Time
Advertising Details (OET07)
🔹 Form Overview
- Form Name: Advertising Details
- Module: Order Execution System
- Type: Transaction
- Short Name: OET07
🔹 Purpose
👉 Maintain all advertising-related
execution data
(sent to client)
🔹 Header Fields
- Advertisement No
- Date
- Client
- Date of Approval
- Consultant
- Payment 3P (Yes/No)
- Reimbursement (Yes/No)
🔹 Media Details Table
|
Field |
Description |
|
Sales Order |
Link to SO |
|
Media |
Newspaper / Portal / Channel |
|
Location |
City / Region |
|
Date |
Publishing date |
|
Cost |
Expense |
|
Approval by Client |
Yes/No |
|
Response to Advertisement |
Results |
📜 Business Rules
(Advertising)
🔹 Core Rule
- One advertisement can cover multiple Sales
Orders
- BUT → must belong to same client
🔹 Critical Constraint
❗ Advertising only allowed if:
👉 Search Mode =
Advertising
🔹 Field Logic
Adv Detail No (A):
- Auto-generated sequence
Date (M):
- User enters
Client (M):
- Only clients with Sales Orders shown
Date of Approval (O):
- Entered when client approves advertisement
Advertising Details (Final
Logic)
🔹 Consultant (D)
- Auto-filled from:
- Inquiry → Proposal → Sales Order
🔹 Payment Logic
Payment 3P (M)
- Who pays for advertising:
- Third Party (3P)
- Client
- Options: Yes / No
- Default = No
Reimbursement (M)
- Whether client reimburses 3P
❗ Rule:
- Enabled ONLY if Payment 3P = Yes
- Else:
- Auto = No
- Field disabled
👉 This is dependent
field logic (important)
Media Details (Multiple
Records)
User can:
- Add
- Modify
- Delete
Fields:
|
Field |
Logic |
|
Sales Order (M) |
Selected from list |
|
Media (M) |
From Media Master |
|
Location (M) |
User enters |
|
Date (M) |
Ad publish date |
|
Cost (M) |
Ad cost |
|
Approved by Client (M) |
Yes / No |
|
Response to Ad (O) |
Text |
🔹 Key Insight
👉 This module enables:
- Cost tracking
- Campaign tracking
- Response tracking
💡 This is basically:
Early version of Marketing
Analytics System
Transfer of Inquiry / Proposal
/ Sales Order (OET08)
🔹 Form Overview
- Form Name: Transfer of Inquiry / Proposal /
Sales Order
- Module: Order Execution System
- Type: Transaction
- Short Name: OET08
🔹 Purpose
👉 Transfer workflow
items:
- Between branches
- Between consultants
🔹 Screen Fields
Order Stage (M)
Options:
- Inquiry
- Proposal
- Sales Order
No (M)
- Select specific record
- Dropdown populated dynamically based on stage
Branch (D)
- Current branch displayed
Consultant (D)
- Current consultant
🔹 Transfer To
- New Branch
- New Consultant
🔹 Transfer Date
- Date of transfer
🔹 Remarks
- Notes / reason
Transfer Engine (Final
Completion)
🔹 Additional Fields
Consultant (D)
- Shows current assigned consultant
Transferred to Branch (M)
- User selects destination branch
Transferred to Consultant (M)
- Dropdown filtered by:
- Selected branch
👉 Dynamic dependency
logic (branch → consultant)
Transfer Date (M)
- Date of reassignment
Remarks (O)
- Optional notes
Candidate Listing (OET09)
🔹 Form Overview
- Form Name: Candidate Listing
- Module: Order Execution System
- Type: Transaction
- Short Name: OET09
🎯 Purpose
👉 Send candidate details
to client for:
- Shortlisting
- Recommendation
🧩 Screen Structure
🔹 Header Section
|
Field |
Meaning |
|
Client Name |
Select client |
|
SON |
Sales Order No |
|
Date |
Listing date |
|
Vacancy Name |
Role |
|
No. of Vacancies |
Count |
|
Send resume before shortlist |
Yes/No |
🔹 Candidate Details
Section
Auto-fetched from Candidate
Database
Includes:
- PEN (Profile ID)
- Name
- Organization
- Designation
- Qualification
- Age
- City
- Contact details
👉 This is master data
integration
🔹 Candidate Response
Table
|
Field |
Meaning |
|
Name |
Candidate |
|
Status |
Final outcome |
|
Candidate Response |
Interested / Not Interested |
|
Communication Mode |
Email / Phone |
|
Edit/Delete |
Actions |
Candidate Listing (Detailed
Logic)
🔹 Auto-Fetched Fields
(Display Only)
From Candidate DB:
- PEN
- Name
- Organization
- Designation
- Qualification
- Past Company
- Age
- City
- Contact agency
- Phone / Mobile
👉 This is normalized
data architecture
🔹 Editable Fields
Status (M)
- Final outcome
- Example: Joined / Rejected
Candidate Response (M)
- Interested / Not Interested
Communication Mode (M)
- Email / Phone
Edit / Delete
- Modify candidate
- Remove from shortlist
🔹 Interaction Flow
- Candidates auto-loaded (from Cyril)
- Displayed in response table
- User clicks Edit
- Candidate details appear above
- Update response/status
OET10 – Preliminary Interview
Score Sheet
🎯 Purpose
👉 Send candidate to
client with:
- One-line summary
- Structured score sheet
💡 This is EXACTLY what
modern AI tools now do:
“Candidate Summary + Fit Score”
🧩 Screen Structure
🔹 Header Section
|
Field |
Meaning |
|
Client Name |
Selected client |
|
Candidate Name |
Selected candidate |
|
Vacancy Name |
Role |
|
Interview Panel |
Evaluators |
|
Date |
Interview date |
|
SON |
Sales Order |
|
PEN |
Candidate ID |
|
No. of Vacancy |
Count |
📊 Assessment Sheet (CORE
ENGINE)
👉 Scoring scale:
- 1 to 10
- (1 = lowest)
🔹 Attributes (You
Defined!)
🎯 Personality & Core
Traits
- Personality
- Career Progression
- Health
- Communication
- Clarity of Thoughts
🎯 Knowledge &
Experience
- Academics
- Job Knowledge
- Experience
- Test Score
🎯 Behavioral / Leadership
Traits
- Managerial Skills
- Initiative / Motivation
- Attitude
- Leadership Quality
- Listening Capability
🔹 Additional Attributes
(15–17)
- Custom fields (flexible system design)
🔹 Total Assessment Score
👉 Aggregate score (manual
or computed)
Deep Candidate Intelligence
Now it becomes very powerful
👇
🔹 Personal Evaluation
Layer
|
Field |
Insight |
|
Family Background |
Context |
|
Strengths |
Positive traits |
|
Weakness |
Risk areas |
|
Exposure to ERP |
Skill relevance |
|
Product Exposure |
Domain expertise |
|
Contribution |
Value potential |
|
Housing |
Stability |
|
Salary Breakup |
Financial structure |
|
Current Compensation |
Current CTC |
|
Expected Compensation |
Expectation |
|
Reason for Change |
Motivation |
Deep Candidate Intelligence
Now it becomes very powerful
👇
🔹 Personal Evaluation
Layer
|
Field |
Insight |
|
Family Background |
Context |
|
Strengths |
Positive traits |
|
Weakness |
Risk areas |
|
Exposure to ERP |
Skill relevance |
|
Product Exposure |
Domain expertise |
|
Contribution |
Value potential |
|
Housing |
Stability |
|
Salary Breakup |
Financial structure |
|
Current Compensation |
Current CTC |
|
Expected Compensation |
Expectation |
|
Reason for Change |
Motivation |
Business Rules
Business Rule:
The preliminary interview score
sheet can be filled only for those SON for which candidate Preliminary
interview are scheduled.
Date (M):
The user needs to enter date of preliminary interview
Client Name (M):
The user will have to select the client name from the dropdown.
SON (M):
The user will have to select the SON from the dropdown. Only SON of the
selected client and whose preliminary interview schedule is done will be shown.
Candidate name (M):
The user need to select the candidate from the dropdown. Only those candidates
for which preliminary interview schedule is done will be shown.
PEN (D):
The PEN of the candidate will be displayed
Vacancy (D):
The vacancy, which is entered in inquiry, will be displayed for selected SON.
No. of Vacancies (D):
The no of vacancies will be displayed for selected SON.
Interview panel (M):
The user needs to enter the interview panel; multiple names can be added using
‘;’.
Assessment Sheet (M):
The user needs to enter the score for each attribute between 1 to 10; 1 being
lowest and 10 being highest.
(no analysis will be possible)
The total will be displayed in total assessment score.
For Sr. no. 15,16,17 the user needs to enter the attribute name and score.
Other assessment details (M):
The user can enter the other assessment details in text box.
Short listed by 3P (M):
The user needs to select whether candidate is short listed by 3P.
Date of short listing (M):
The user needs to enter date of short listing by 3P.
Resume Sent to client (M):
The user needs to select whether the resume is sent to client.
Date of resume sent (M):
The user needs to enter date when resume was sent to client.
Short listed by Client (M):
The user needs to select whether client has short-listed the candidate for
final interview.
Date of short listing by
client (M):
The user needs to enter date when client short-listed candidate.
Note:
a) The date of short-listing will
be less than date of resume sent.
b) The date of short-listing by 3P will be less than date of short-listing by
the client.
Interview Schedule
Form Name: Interview
Schedule
Module: Order Execution System
Form Type: Transaction
Short Name: OET11
Purpose:
The user can schedule the interview details for a candidate, or set of
candidates for both preliminary and final interview.
3P Consultants – Order
Execution System
(Menu options: Login | Masters |
Transactions | Reports | Security)
Fields available at top:
- Company
- Division
- Financial Year
- Branch
Actions: add | view | save |
delete
Navigation: first | previous | next | last
Interview Schedule Section
- Client Name
- Person contacted
- Vacancy name
- Designation Level
- Consultant Name
- Type of Interview (Default: Preliminary)
- Date
- SON
- Phone Number
- Number of Vacancy
- Function
- Interview Round
Candidate Interview Schedule
Columns:
- Candidate PEN
- Candidate Name
- Date of Interview
- Time of Interview
- Interview Venue
- Other Information
- Date of Communication
(Multiple rows for candidates)
Interview Schedule (Business
Rules Continued)
Business Rule:
The preliminary interview can be
only scheduled for the SON whose candidate listing is done.
Whereas the final interview can be scheduled only for SON whose preliminary
interview is done.
Date (M):
The user need to enter date of preparation of interview schedule. By default it
will show the system date.
Client Name (M):
The user will have to select the client name from the dropdown.
SON (M):
The user will have to select the SON from the dropdown. Only SON of the
selected client and whose candidate listing is done will be shown.
In case of the final interview only those whose preliminary interview is done
will be shown.
Person contacted (M):
In case of final interview the user needs to add the person contacted.
Phone (O):
The user can enter telephone no of the person contacted. Multiple numbers can
be stored using a ‘;’ to separate two or more numbers.
Vacancy (D):
The vacancy, which is entered in inquiry, will be displayed for selected SON.
No. of Vacancies (D):
The no of vacancies will be displayed for selected SON.
Designation (D):
The designation level, which is entered in inquiry, will be displayed.
Interview Schedule (Detailed
Rules)
Function (D):
The function, which is entered in inquiry, will be displayed.
Consultant Name (D):
The name of consultant will be displayed, as entered in inquiry.
Type of Interview (M):
It will be either preliminary or final.
- The user need to select preliminary to schedule
preliminary interview to be taken by 3P.
- In case of interview by client the user need to
select final.
- When final is selected round of interview has to be
specified.
Interview Round (A/D):
The round no will be auto generated automatically if the feedback of previous
round is taken and any candidate is short-listed for next round of interview.
Else last round no will be displayed.
Candidate Interview Schedule
In case of preliminary interview:
- All candidates who are selected for candidate
listing and interested in offer will be displayed in table below.
In case of final interview:
- Candidates who are short-listed by client after
preliminary interview will be displayed in table below for first round.
- In subsequent rounds, names of candidates who have
been short-listed in feedback form for next round will be displayed.
The table will have Edit
and Delete buttons.
- The user can enter details against candidate by
pressing edit button.
- Delete button will delete the candidate for that
round and subsequent interview.
PEN (D):
PEN of candidate will be displayed.
Candidate Name (D):
Name of candidate will be displayed (as mentioned above).
Date of Interview (M):
The user needs to select date of interview for the candidate.
Time of Interview (M):
The user needs to enter time of interview for candidate.
Interview Venue (M):
The user needs to enter venue for interview for candidate.
Other Information (O):
The user can enter other information if any.
Date of Communication (M):
The user needs to enter date of communication to candidate.
Mode of Communication (M):
The user needs to select the mode of communication for candidate.
Candidate Communicated (M):
Radio button to specify whether candidate is communicated about the interview.
Candidate Confirmation (M):
Radio button to specify candidate confirmation about interview.
Email ID (M):
The user needs to enter e-mail id of candidate if mode of communication is
email.
Email Candidate (M):
The user need to press button to e-mail candidate regarding interview schedule.
The e-mail button will be enabled only if mode of communication is e-mail and
e-mail id is entered.
Edit:
The user needs to press Edit button to enter the above detail for the
candidate.
Delete:
The user needs to press delete button to delete the candidate for that round of
interview and for subsequent interview if any.
Interview Reschedule
Form Name: Interview
Reschedule
Module: Order Execution System
Form Type: Transaction
Short Name: OET12
Purpose:
The user can reschedule the interview.
3P Consultants – Order
Execution System
(Menu options: Login | Masters |
Transactions | Reports | Security)
Fields available:
- Company
- Division
- Financial Year
- Branch
Actions: add | view | save |
delete
Navigation: first | previous | next | last
Re-Interview Schedule
Left Section:
- Type of Interview (Default: Preliminary)
- Client Name
- Last Interview Date
- Person contacted
- Vacancy name
- Designation Level
- Consultant Name
Right Section:
- SON
- Re-Interview Date
- Phone Number
- Number of Vacancy
- Function
- Interview Round
Candidate Re-Interview
Schedule
Columns:
- Candidate PEN
- Candidate Name
- Date of Interview
- Time of Interview
- Interview Venue
- Other Information
- Date of Communication
(Multiple rows for candidates)
Interview Reschedule (Business
Rules)
Business Rule:
The user can reschedule the
interview details for a candidate, or set of candidates.
All the candidates whose interview is scheduled will be displayed in table once
the user selects the client, SON for which the interview has to be rescheduled.
The user can press edit button
and change/reschedule the interview.
In subsequent schedule the changed details will appear in interview schedule
form.
Only last interview schedule
can be rescheduled.
Field Rules
Type of Interview (M):
The user will select the type of last interview.
Client Name (M):
The user will have to select the client name from the dropdown.
SON (M):
The user will have to select the SON from the dropdown.
Only SON of the client and whose interview is scheduled will be shown.
Last interview date (D):
The last interview date will be displayed.
Interview Date (M):
The user need to enter date of preparation of interview schedule.
By default it will show the system date.
Person contacted (M):
In case of final interview the user needs to add the person contacted.
Vacancy (D):
The vacancy, which is entered in inquiry, will be displayed for selected SON.
No. of Vacancies (D):
The no of vacancies will be displayed for selected SON.
Designation (D):
The designation level, which is entered in inquiry, will be displayed.
Function (D):
The function, which is entered in inquiry, will be displayed.
Interview Reschedule
(Continued Rules)
Consultant Name (D):
The name of consultant will be displayed, as entered in inquiry.
Interview Round (D):
The last round of interview schedule will be displayed.
Candidate Interview Schedule
All the candidates whose
interview is scheduled for that round of interview will be displayed.
The table will have Edit and Delete buttons.
- The user can enter details against candidate by
pressing edit button of that candidate.
- Delete button will delete the candidate for that
round and subsequent interview.
PEN (D):
PEN of candidate will be displayed.
Candidate Name (D):
Name of candidate will be displayed (as mentioned above).
Date of Interview (M):
The user needs to enter date of interview for the candidate.
Time of Interview (M):
The user needs to enter time of interview for candidate.
Interview Venue (M):
The user needs to enter venue for interview for candidate.
Other Information (O):
The user can enter other information if any.
Date of Communication (M):
The user needs to enter date of communication to candidate.
Mode of Communication (M):
The user needs to select the mode of communication for candidate.
Candidate Communicated (M):
Radio button to specify whether candidate is communicated about the interview.
Candidate Confirmation (M):
Radio button to specify candidate confirmation about interview.
Email ID (M):
The user needs to enter e-mail id of candidate if mode of communication is
email.
Email Candidate (M):
The user need to press button to e-mail candidate regarding interview schedule.
The e-mail button will be enabled only if mode of communication is e-mail and
e-mail id is entered.
Edit:
The user needs to press Edit button to enter the above detail for the
candidate.
Delete:
The user needs to press delete button to delete the candidate for that round of
interview and for subsequent interview if any.
Compensation Details
Form Name: Compensation
Details
Module: Order Execution System
Form Type: Transaction
Short Name: OET13
Purpose:
The compensation details of the candidate has to be recorded to calculate the
fees and generate invoice.
3P Consultants – Order
Execution System
(Menu options: Login | Masters |
Transactions | Reports | Security)
Fields available:
- Company
- Division
- Financial Year
- Branch
Actions: add | view | save |
delete
Navigation: first | previous | next | last
Compensation Details
- Client Name
- SON
- Date
- Vacancy Name
- Candidate Name
- Candidate PEN
Compensation Format
- Currency
- Rate
Compensation Table
A. MONTHLY (Per Month –
Prorata)
- Basic Salary
- D.A. (or equivalent)
- Housing
- House Rent Allowance
B. ANNUAL (Per Month –
Prorata)
- Bonus
- Ex-gratia (in lieu of Bonus)
- L.T.A.
- Commission / Incentive / Profit Sharing (Estimated
/ Projected)
Compensation Details
(Continued)
Additional Monthly / Allowance
Components
- Soft / Hard Furnishing
- Car Allowance / Conveyance Allowance
- City Compensation
- Education
- Servant
- Electricity / Gas
- Medical
- Newspaper / Periodicals
- Driver Salary
- Entertainment
- Telephone
- Any other allowances / Reimbursement / Cash payment
SUB TOTAL (B)
C. RETIREMENT BENEFITS
- Provident Fund
- Super - Annuation
- Gratuity
SUB TOTAL (C)
D. INDIRECT BENEFITS
- Benefit due to interest saving (over 18% rate of
interest) arising out of loans advanced by the employer
- Club Fees
- Lump Sum furniture / furnishing outlay
- Sign-Up Bonus
- Equity / Stock Option (at current market value)
SUB TOTAL (D)
Additional Custom Fields
a. __________
b. __________
c. __________
d. __________
FINAL TOTALS
- SUB TOTAL (A)
- TOTAL (A + B + C + D)
Business Rule:
The compensation details can be
filled for only those candidates who are selected by client.
|
Field Name |
Description / Rule |
|
Client name (M): |
The user will have to select
the client name from the drop down. |
|
SON (M): |
The user need to select SON
from dropdown. SON only for the selected client will be available. |
|
Date (M): |
Date of the preparation of
compensation details has to be entered. By default it will show the system
date. |
|
Vacancy name (D): |
The name of vacancy for the SON
will be displayed. |
|
Candidate name (M): |
The user need to select the
candidate from the dropdown. Only those candidate which are selected by
client and whose compensation details are not entered will be only available. |
|
PEN (D): |
The PEN of the candidate will
be displayed. |
|
Currency (D): |
The currency will be displayed,
as entered in inquiry. |
|
Rate (D): |
The rate will be displayed, as
entered in inquiry. |
A. Monthly
|
Field Name |
Description / Rule |
|
Basic Salary (M): |
The user needs to enter the
basic salary offered to the candidate. |
|
D.A. (or equivalent) (M): |
The user needs to enter the
D.A. (or equivalent) offered to the candidate. |
|
Housing (M): |
The user needs to enter cost of
housing offered to the candidate. |
|
House Rent Allowance (M): |
The user needs to enter house
rent allowance offered to candidate. |
|
Soft/ Hard Furnishing (M): |
The user needs to enter cost of
Soft / Hard furnishing offered to candidate. |
|
Car Allowance / Conveyance
Allowance (M): |
The user needs to enter cost of
Car Allowance / Conveyance Allowance offered to candidate. |
|
City Compensation (M): |
The user needs to enter cost of
city compensation offered to candidate. |
|
Education (M): |
The user needs to enter cost of
education offered to candidate. |
|
Servant (M): |
The user needs to enter cost of
servant offered to candidate. |
|
Electricity / Gas (M): |
The user needs to enter cost of
electricity/gas offered to candidate. |
|
Medical (M): |
The user needs to enter cost of
medical facility offered to candidate. |
|
Newspaper / Periodicals (M): |
The user needs to enter cost of
newspaper/periodicals offered to candidate. |
|
Driver Salary (M): |
The user needs to enter cost of
driver provided to candidate. |
|
Entertainment (M): |
The user needs to enter cost of
entertainment offered to client. |
|
Telephone (M): |
The user needs to enter cost of
telephone offered to client. |
Any other allowances (M):
The user can enter any other allowance / reimbursement / payment made to
candidate. The user can add three allowances. The user need to enter both
description and cost.
SUB TOTAL A (D):
The sub total of A will be displayed
B. Annual
Bonus (M):
The user needs to enter the bonus offered to the candidate
Ex-gratia (in lieu of Bonus)
(M):
The user needs to enter cost of Ex-gratia (in lieu of Bonus)
L.T.A (M):
The user needs to enter L.T.A offered to candidate
Commission / Incentive /
Profit Sharing (Estimated / Projected) (M):
The user needs to enter Commission / Incentive / Profit Sharing (Estimated /
Projected) offered to candidate
SUB TOTAL B (D):
The sub total of B will be displayed
C. Retirement Benefits
Provident Fund (M):
The user needs to enter Provident Fund offered to candidate in value
Super - Annutation (M):
The user needs to enter super-annuation offered to candidate in value
Gratuity (M):
The user needs to enter gratuity offered to client in value
SUB TOTAL C (D):
The sub total of C will be displayed
D. Indirect Benefits
Benefit due to interest saving
(over 18% rate of interest) arising out of loans advanced (M):
The user needs to enter Benefit due to interest saving (over 18% rate of
interest) arising out of loans advanced by the employer
Club Fees (Entrance fees/60)
(M):
The user needs to enter club fees offered to candidate
Lump Sum furniture /
furnishing outlay (M):
The user needs to enter Lump Sum furniture / furnishing outlay offered to
candidate
Sign-Up Bonus (M):
The user needs to enter Sign-Up Bonus offered to candidate
Equity / Stock Option (M) (at
current market value):
The user needs to enter Equity / Stock Option offered to candidate
SUB TOTAL D (D):
The sub total for D will be displayed
TOTAL A + B + C + D (M):
The Total cost to company will be displayed
Form Name: Feedback Form
Module: Order Execution
System
Form Type: Transaction
Short Name: OET14
Purpose: The feedback from client is taken regarding outcome of
interview.
Feedback Form Fields
- SON
- Consultant Name
- Name of Vacancy
- Designation
- Candidate Name
- Feedback for Round
- Feedback from Client
- Date of Next round of interview
- Remarks
Right Panel Fields
- Date
- Client Name
- No. of Vacancies
- Function
- PEN
Joining Details (If selected)
- Accepted the Offer: Yes / No
- Date of Acceptance
- Tentative Date of Joining
- Actual Date of Joining
- Remarks
Business Rule
The feedback form can be filled
only for those SON whose Final interview are scheduled.
Field Rules
SON (M):
The user needs to select the SON for the selected client for which the follow
up is made. Only those SON under execution made will be available.
Date (M):
The user needs to enter date of feedback.
Consultant Name (D):
The name of consultant, which is entered in SON, will be displayed.
Client Name (M):
The user needs to select the client for which the follow up has been made.
Vacancy (D):
The vacancy, which is entered in inquiry, will be displayed for selected SON.
No. of Vacancies (D):
The no of vacancies will be displayed for selected SON.
Designation (D):
The designation level, which is entered in inquiry, will be displayed.
Function (D):
The function, which is entered in inquiry, will be displayed.
Candidate Name (M):
The user needs to select the candidate name for which the feedback has to be
taken. The names of the candidate whose interview is scheduled and were short
listed in previous round will only be available.
PEN (D):
The PEN no. of candidate will be displayed.
Feedback for round (D):
The feedback will be for the last round, which will be displayed.
Feedback from Client (M):
The user needs to select feedback from the option
(Short-listed, Not Appeared in Interview, Rejected, Selected, Hold).
If candidate is selected then his joining details has to be taken.
In case of short listed candidates next round of interview has to be scheduled.
Remarks (O):
The user can enter remarks.
Joining Details (If selected)
Accepted the Offer (M):
Radio button to specify whether candidate accepted the offer.
Date of Acceptance (M):
If offer is accepted by candidate date of acceptance has to be entered.
Tentative Date of Joining (M):
If offer is accepted by candidate tentative date of joining has to be entered.
Actual Date of Joining (O):
The user needs to enter actual date of joining after the candidate has joined.
Remarks (O):
The user can enter remarks related to joining if any.
Invoice
Module: Order Execution
System
Form Type: Transaction
Short Name: OET15
Purpose:
The Invoice has to be raised once the candidate joins the company as per the
terms and condition in proposal. Invoice has to be also raised for other type
of fees.
Invoice Form Fields
- Invoice Number
- Invoice Date
- Client Name
- SON
- Proposal No.
- Vacancy Name
- No. of Vacancies
Invoice Type Section
- Invoice Type (e.g., Advance Fees)
- Currency
- Total Amount
- Less: Adjustable amount
- Net Receivable
- Add: Service Tax
- TOTAL
- Remarks
Business Rule
The final invoice can be
generated only for those SON whose candidates compensation details are
available.
Whereas other invoice can be generated as and when required.
There are five types of invoice:
- Minimum Search Fee
- Progression Fee
- Out of pocket expenses
- Advance Fee
- Final Invoice (full and final settlement)
The out of pocket expenses are
not adjustable during final invoice whereas the other fees are adjustable
during final invoice.
Field Rules
Invoice Number (A):
The code will be auto generated in a sequence for each invoice generated.
Invoice Date (M):
The user has to enter date of invoice; by default it will show the system date.
Client Name (M):
The user needs to select the client for which the invoice has to be prepared.
The names of only those clients will appear whose SON is under execution and
are not closed and/or final invoice is not made.
SON (M):
The user needs to select the SON for the selected client for which the invoice
is to be generated. Only those SON under execution and are not closed and/or
final invoice is not made will be available.
Proposal no (D):
The proposal no will be displayed for selected SON
Vacancy (D):
The vacancy will be displayed for selected SON
No. of Vacancies (D):
The no of vacancies will be displayed for selected SON
Invoice Type (D):
The user needs to select the type of invoice to be generated. The user has an
option from Advance, Minimum Search Fee, Progression fee, Out of pocket
expenses and Final invoice.
Currency (D):
The currency entered in proposal will be displayed and invoice will be
generated in that currency
Total Amount (M):
The user needs to enter the amount for which the invoice has to be made.
In case of final invoice total amount will be calculated from the compensation
details available for that SON and as per terms and conditions in proposal.
Less Adjustable amount (D):
In case of final invoice the adjustable amount for which invoice was raised
previously will be deducted.
Net Receivable (D):
In case of final invoice the net receivable will be displayed.
Add: Service Tax (M):
In case of final invoice the user needs to enter the service tax to be charged.
The service tax will be charged over the total amount.
Total (D):
In case of final invoice the total will be displayed (Net receivable + service
Tax).
Remarks (O):
The user can enter the remarks to be printed on the invoice (if any)
Follow Up With Client
Module: Order Execution
System
Form Type: Transaction
Short Name: OET16
Purpose:
The consultants should be able to know the details of the follow-up with
various clients so he can decide on further course of action.
Client Follow Up Fields
- Client Name
- SON
- Name of Vacancy
- Number of Vacancy
- Activity
- Follow Up Date
- Person Contacted
- Mode of Communication
- Result / Outcome
- Remarks
- Next Follow Up Date
Business Rule
The follow up with client can be
entered as and when required.
Field Rules
Client Name (M):
The user needs to select the client for which the follow up has been made.
SON (O):
The user needs to select the SON for the selected client for which the follow
up is made. Only those SON under execution made will be available.
Vacancy (D):
The vacancy will be displayed for selected SON.
No. of Vacancies (D):
The no of vacancies will be displayed for selected SON.
Activity (M):
The user needs to select the follow up activity. The activity, which are marked
for both or follow-up in activity master will be available.
Follow up date (M):
The user will select the date on which follow up with the client is done.
No comments:
Post a Comment