TC No Test Case Title Summary

[AGR_D_001] Verify the 'Contract Policy

Type' [Simple/Complex] value during
175045.1 agreement creation based on the analysis
of the business needs .

175045.2

175045.3

175045.4

175045.5

175045.6

175045.7

175045.8

175045.9
175045.1

175045.11 Pre-requisities:A contract request

should exist with approved
state,having contract policy type as
Simple/Complex as per entered by
CM in request in 'for contract
Manager only' section.contract
175045.12 Manager should have access to
175045.13 above contract request.
[AGR_D_003] Verify the Agreement code
format after agreement creation.
175046.1

175046.2

175046.3

175046.4
175046.5

175046.6
Pre-requisities:1. A contract request
should exist with approved state and
CM should can create agreement for
175046.7 that request.
[AGR_D_004] Verify that contract manager
will only select mandatory attribute value
175047.1 of 'Sanofi Legal Entity' and it should not be
175047.2 available during request creation form.

175047.3

175047.4

175047.5

175047.6

175047.7
175047.8
Pre-requisities:A request type
175047.9 contract type should exist .
[AGR_D_005] Verify that agreement
created for MSA contract type is always a
175061.1 complex contract and Work order/SOW
created from MSA will be Simple contract.

175061.2

175061.3

175061.4

175061.5

175061.6

175061.7
 175061.8
175061.9

175061.1

175061.11

175061.12

175061.13

Pre-requisities:-All the agreement

type contract types should be
published [MSA,WO,SOW] .
-A contract request should exist
having approved state, having
175061.14 contract policy type as a complex and
 during request creation
contract type selection rule should
175061.15 get satisfied which include MSA
contract type.-A request for WO and
SOW should exist having approved
175061.16 state and contract policy type as a
175061.17 simple.
[AGR_D_007] Verify that Work Order will
get created from new Request always and
175062.1 there should not be any inheritance [MSA]
in work order.

175062.2

175062.3

175062.4

175062.5

175062.6

Pre-requisities:A contract request

175062.7 should exist having approved state,
during request creation contract type
selection rule should get satisfied
175062.8 which include WO contract type.
 [AGR_D_009] Verify that Leading cost
centre gets inherited on Contract form
175064.1 from the contract request.

175064.2

175064.3

175064.4

Pre-requisities:A contract request

175064.5 should exist having approved state,
during request creation contract type
selection rule should get satisfied
which include contract type.Contract
request should have the value for
175064.6 'Leading cost centre'.
[AGR_D_010] Verify that approver/finance
controller of the contract gets determined Pre-requisities:-An agreement with
175067.1 depending on the value of the 'Leading cost draft state should exist having value
centre'. for 'Leading cost centre'-Approver
rule for different values of 'Leading
cost centre' should exist.Rule 1: if
175067.2 'Leading cost centre' is equal to
1000require approval from financial
controller [Approver] 1Rule 2: if
175067.3 'Leading cost centre' is less than
1000require approval from financial
controller [Approver] 2Rule 3: if
'Leading cost centre' is greater than
1000require approval from financial
175067.4 controller [Approver] 3
[AGR_D_001] [AGR_D_013] Verify Simple
[contract policy type] agreement creation
175070.1 based on the analysis of the business needs
.

175070.2

175070.3

175070.4

175070.5

175070.6

175070.7
 175070.8

175070.9
175070.1 Pre-requisities:-A contract request
should exist with approved
state,having contract policy type as
Simple as per entered by CM in
175070.11 request in 'for contract Manager
175070.12 only' section.contract Manager
should have access to above contract
request.
 
175070.13  
[AGR_D_001] Verify Complex [contract
policy type] agreement creation based on
175072.1 the analysis of the business needs .

175072.2

175072.3

175072.4

175072.5

175072.6

175072.7

175072.8

175072.9
175072.1

Pre-requisities:A contract request

should exist with approved
175072.11 state,having contract policy type as
Complex as per entered by CM in
request in 'for contract Manager
only' section.contract Manager
should have access to above contract
request.
 Pre-requisities:A contract request
should exist with approved
state,having contract policy type as
Complex as per entered by CM in
request in 'for contract Manager
only' section.contract Manager
should have access to above contract
175072.12 request.
[AGR_D_011] Verify that how Simple
contract gets converted to Complex
175075.1 contract when agreement gets deviated.

175075.2

175075.3

175075.4

175075.5

175075.6

175075.7

175075.8
175075.9

175075.1
175075.11

175075.12
Pre-requisities:A contract request
should exist with approved
state,having contract policy type as
175075.13 Simple as per entered by CM in
request in 'for contract Manager
only' section.contract Manager
175075.14 should have access to above contract
175075.15 request.
[AGR_D_011] Verify that how Simple
contract gets converted to Complex
175076.1 contract when CM identifies that it should
be complex.

175076.2

175076.3

175076.4
 175076.5

175076.6

175076.7

175076.8
Pre-requisities:A contract request
should exist with approved
state,having contract policy type as
175076.9 Simple as per entered by CM in
175076.1 request in 'for contract Manager
only' section.contract Manager
should have access to above contract
175076.11 request.
[AGR_D_010] Verify that Leading cost
centre is linked to Controller Group and
175078.1 each Controller Group will have one or
more Finance Controllers as an Approvers.
175078.2

175078.3

175078.4

175078.5
175078.6

175078.7

175078.8

175078.9

175078.1

175078.11

175078.12

175078.13 Pre-requisities:-A controller group

[user group] should present having
more than one users in it.-A request
contract type should have lookup
cascade for the 'Leading cost centre'
masterdata.--n approver rule should
exist for the agreement depending
 Pre-requisities:-A controller group
[user group] should present having
more than one users in it.-A request
contract type should have lookup
175078.14 cascade for the 'Leading cost centre'
masterdata.--n approver rule should
exist for the agreement depending
upon the leading cost centre
175078.15 attribute value.Rule 1: if 'Leading
cost centre' is equal to 1000require
approval from controller group 1Rule
175078.16 2: if 'Leading cost centre' is less than
1000require approval from controller
group 2Rule 3: if 'Leading cost centre'
is greater than 1000require approval
175078.17 from controller group 3
[AGR_D_016] Expiry date will be manually
entered by contract manager.
175090.1

175090.2

175090.3

175090.4

175090.5

175090.6

175090.7

175090.8
Pre-requisities:
175090.9 -A contract request should exist with
approved state.- contract Manager
should have access to above contract
175090.1 request.
[AGR_D_014] Verify that user can enter
vendor details manually when vendor
175122.1 details [masterdata] are not available into
the system.

175122.2

175122.3

175122.4
 175122.5

175122.6

175122.7

175122.8
Pre-requisities:
175122.9 - A contract request should exist with
approved state.- contract Manager
should have access to above contract
175122.1 request.
Verify that MSA is linked into the WO and
number gets updated.

177773.1

177773.2

177773.3

177773.4
177773.5

177773.6

177773.7

177773.8
177773.9

177773.1

177773.11

177773.12
177773.13

177773.14

177773.15

177773.16
177773.17

177773.18
Pre-requisities:-An agreement for
MSA contract type should exist
177773.19 having any state after publish.-WO
contract type should have an
attribute which gives value of MSA
177773.2 agreement when MSA is added to
177773.21 the WO.- Purchasing partner should
have access to create request and
contract types which are of type
177773.22 request.- Vendor details should exist
into the SAP.- Contract type selection
rule should exist for the contract
request.- An event rule to add CM to
177773.23 request should exist for the contract
177773.24 request.
Verify that contract manager can recall the
agreement from signatory user.
177774.1

177774.2

177774.3

177774.4

177774.5

177774.6
 177774.7

177774.8

177774.9

177774.1
177774.11

177774.12

177774.13

177774.14

177774.15

177774.16

177774.17

177774.18

177774.19

177774.2 Pre-requisities:- A Contract request

should exist with approved state. -
External/internal signatory rule
177774.21 should exist.
Verify the change in agreement document
rejection flow when vendor reject and
177775.1 changes the document data.

177775.2

177775.3
 177775.4

177775.5

177775.6

177775.7

177775.8

177775.9

177775.1

177775.11
Pre-requisities:- An own type of
agreement should exist with draft
177775.12 state.-Agreement should consist of
177775.13 vendor name for external review.
Verify that user can add expert during
elaboration/approval.
177779.1

177779.2

177779.3
177779.4

177779.5

177779.6

177779.7

177779.8

177779.9

177779.1
177779.11
177779.12

177779.13

177779.14

Pre-requisities:- An own type of

177779.15 agreement should exist with draft
177779.16 state.
[AGR_DA_002] Verify that Clause Deviation
analysis happens, but no notifications sent
178020.1 automatically. CM choses (anybody) the
deviation approver and send the
notification manually from the system.
178020.2

178020.3

178020.4

178020.5
178020.6

178020.7

178020.8

178020.9

178020.1

178020.11

Pre-requisities:1. An agreement
having 'complex' contact policy type
178020.12 should exist with draft state.
[AGR_DA_006] Verify that For NA deviation
approver will always be Contract Manger.
178045.1 For France deviation approver will always
be Legal Team.
 [AGR_DA_006] Verify that For NA deviation
approver will always be Contract Manger.
For France deviation approver will always
be Legal Team.

178045.2

178045.3

178045.4

178045.5
178045.6

178045.7

178045.8

178045.9

178045.1

178045.11

178045.12

178045.13

178045.14

Pre-requisities:1. Two agreement

having 'complex' contact policy type
should exist with draft state.- 1
agreement with French language and
178045.15 another with English language.
Action
Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper.

Click on next button.

Verify the 'Contract Policy Type' attribute value.

Enter other mandatory data. In case of Own type-satisfy the

template selection rule In case of third party-upload the third
party document.

Click on next button.

Select the template and click on next button.

Click on create button.Click on publish button.

Verify the team tab.

Login to the application by valid user [CM of the pre-

requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

Verify that on click on view record button.

Click on create contract button.

Select the category, contract type and type of paper. Click on
next button.

Enter other mandatory data and create the agreement.

Check the agremeent code format.

Login to the application by valid user and navigate to request
creation.
Click on create request tile.
Verify the attribute 'Sanofi Legal Entity' on all the pages during
request creation.
Enter data into all the attributes and create the request.
Approve the request.

Click on create contract button.

Select the category, contract type and type of paper. Click on

next button.
Verify the mandatory attribute 'Sanofi Legal Entity' on all the
pages during agreement creation.
Enter data into the ''Sanofi Legal Entity' .

Enter other mandatory data and create the agreement.

Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

Verify that on click on view record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper. Contract type -MSA

Click on next button.

Verify the 'Contract Policy Type' attribute value.

Select the 'Contract Policy Type' attribute value as a 'Complex'
and enter othe mandatory data.
Crete the agreement.

Verify that the User is able to Search for the pre-requisities

Contract request [WO and SOW] from contract request Index
page/ main Search page.

Verify that on click on view record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper. Contract type -WO/SOW

Click on next button.Verify the attribute value which is related

to MSA [As per consideration the re should be an attribute
like MSA parent agreement and it should have value of MSA
agreement]

Verify the 'Contract Policy Type' attribute value.

Select the 'Contract Policy Type' attribute value as a 'Complex'
and enter othe mandatory data.
Crete the agreement.
Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

Verify that on click on view record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper. Contract type-Work Order

Check for the inheritance availability on attribute page.

Click on next button.

Enter all the mandatory data and create the agreement.

Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

Verify that on click on view record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper.

Check for the inherited data from the request on attribute

page.
Login to the application by valid user [CM/primary owner of
the pre-requisities agreement].

Verify that the User is able to Search for the above created
agreement [Pre-requisities]from agreement Index page/ main
Search page.

Verify that on click on view record button.

Check the 'Leading cost centre' attribute value'. Click on team

tab and check for the approvers.
Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper.

Click on next button.

Verify the 'Contract Policy Type' attribute value.

Select 'Contract Policy Type' value and enter other mandatory
data. In case of Own type-satisfy the template selection rule
In case of third party-upload the third party document.

Click on next button.

Select the template and click on next button.

Click on create button.Click on publish button.

Now create the simple [contract policy type] agreement for

the CDA contract type by using above steps.
Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper.

Click on next button.

Verify the 'Contract Policy Type' attribute value.

Select 'Contract Policy Type' value and enter other mandatory

data. In case of Own type-satisfy the template selection rule
In case of third party-upload the third party document.

Click on next button.

Select the template and click on next button.

Click on create button. Click on publish button.

Verify the team tab.
Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper as 'Own'.

Click on next button.

Verify the 'Contract Policy Type' attribute value.

Now enter other mandatory data, select template and create
the agreement. Publish the agreement.
Check for the deviations.

Download the document and change/edit data from the

clause and save the document. Upload the updated
document.
Check for the deviations.

Verify the team tab.

Navigate to summary page and click on edit button update

the 'Contract policy type' from 'Simple' to Complex.
Fill all the legal approvers as required and update the
agreement.
Verify team tab
Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should
display depending on the contract tye selction rule of request]
and type of paper as 'Own'.

Click on next button.

Verify the 'Contract Policy Type' attribute value.

Change the 'Contract Policy Type' attribute value to Complex.

Enter other mandatory data, select template and create the
agreement. Publish the agreement.

Download the document and change/edit data from the

clause and save the document. Upload the updated
document.
Check for the deviations.

Verify the team tab.

Login to the application by valid user and navigate to
masterdata-Create masterdata.
Select 'Leading cost centre' contract type and click on next
button.
Enter data into all the attribute. Enter data for the attribute
which is linked to the controller group.

Create the master data.

Login to the application by valid user and navigate to contract
request-Create contract request.
Select request ,category and click on next button.

Select value into the attribute for which 'Leading cost centre'
is available as lookup and cascade. User should able to select
value from lookup search pop-up.
Enter other mandatory data and create the request. Approve
the request.
Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper.
Click on next button.

Check the 'Leading cost centre' attribute value which came

from contract request.
Enter other mandatory data and create the agreement.
Publish the agreement.

Verify the team.

Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should

display depending on the contract tye selction rule of request]
and type of paper.

Click on next button.

Check for Expiry date attribute.

Select effective date of the agreement and check for expiry

date calculation.

Select expiry date of the agreement.

Enter other mandatory data and navigate to verify tab.

Login to the application by valid user [CM of the pre-
requisities contract request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

click on view (eye icon) record button.

Click on create contract button.

Select the category, contract type [contract type should
display depending on the contract tye selction rule of request]
and type of paper.

Click on next button.

Check for the attribute related to Vendor details.

Select attribute value as -Yes

Select attribute value as -No.

Enter data into the attribute vendor name, address and
contact details

Log-on to ICM application with Purchasing Partner user

credentials

Click on agreement management->Create request Tile

Select Catrgory as 'Buy side' and request type as "Buy side"
from the dropdown list.
Click Next to proceed to the next step of contract request
creation process
Enter valid data into all the attributes.
Select proper 'Contract Manager Team' from the dropdown
list.

Click Next to proceed to the next step of contract request

creation process

Click Create request button to create the contract request

Click on submit button.

Verify the buttons displaying on details page of the contract

request.
Login to the application by valid user [CM of the above
contract request].

Verify that the User is able to Search for the above created
Contract request from contract request Index page/ main
Search page.
click on view (eye icon) record button.

Click on create contract button.

Select the category-Buy side, Contract type name- Work

Order and type of paper as 'Own'.

Click Next to proceed to the next step of contract creation

process
Enter data into all the mandatory fields.
Click Next to proceed to the next step of contract creation
process

Upload the third party document and click on next button.

Click Create Button to create the contract

Click on publish button.

Click on send for approval button.

Close the validation message. Click on add (+) button present

in front of the association name and add association from
search pop-up.
Check the MSA number attribute value.
Login to the application by valid user [CM of the above
contract request].

Verify that the User is able to Search for the above created
Contract request from contract request Index page/ main
Search page.

click on view record (eye icon) record button.

Click on create contract button.

Select the category-Buy side, Contract type name and type of

paper.

Click Next to proceed to the next step of contract creation

process
Enter data into all the mandatory fields. Select external
signatory, internal signatory and electronic signature.
Click Next to proceed to the next step of contract creation
process

Click on next button.

Click Create Button to create the contract

Click on publish button.

Click on team tab.

Click on send for approval button and approve the agreement
[No approvers]

Click on send for external signature button.

Open the email by using external signature details and click on
view document.

In ICM, login with primary owner and click on recall button.

Open the email by using external signature details and click on
view document.

Click on edit button by primary owner and change the

external and internal signatory user. Update the agreement.

Send agreement for approval and Approve the agreement.

Click on send for external signature button.

Open the email by using external signature details and click on
view document.
Login to the application by valid user [CM of the above
agreement].

Verify that the User is able to Search for the above created
agreement from agreement Index page/ main Search page.

click on view record (eye icon) record button.

Click on collaborate button.
Login to the Supplier portal by using the valid credentials.
Download the agreement document.

Now change the agreement document data (Clause data) and

upload the same to the portal. Verify the email notification
after upload document.
Open the ICM application and check for the modifications
done into the agreement document.

Now do not change the original agreement document with

vendors comment. Enter the comments about rejection of the
changes and again send to the vendor.
Check the comments provided by CM/Primary owner and
make the changes into the document.

Send agreement document back to the CM/Primary owner.

Open the ICM application and check for the modifications
done into the agreement document.
No change the original agreement document with vendors
comment.
Approve the agreement by approvers.
Login to the application by valid user [CM of the above
agreement].

Verify that the User is able to Search for the above created
agreement from agreement Index page/ main Search page.

click on view record (eye icon) record button.

Click on team tab and click on 'Add user(+)' button.
Select one user, select role as observer and click on add
button.
Login to the application by observer and open above
agreement.
Verify that user can view agreement details and can download
the agremeent.
Login to the application by valid user [CM of the above
agreement].

Verify that the User is able to Search for the above created
agreement from agreement Index page/ main Search page.

click on view record (eye icon) record button.

Send agreement for approval.
Click on team tab and click on 'Add user(+)' button.
Select one user, select role as observer and click on add
button.
Login to the application by new observer and open above
agreement.
Verify that user can view agreement details and can download
the agremeent.

Login to the application by valid user [CM of the pre-

requisities agreement].

Verify that the User is able to Search for the above created
agreement [Pre-requisities]from agreement Index page/ main
Search page. Open the agreement.

click on view (eye icon) record button.

Download and Open the downloaded document and make

changes and save the document. Subsequently Click on
Upload document and upload the previously saved document

Click on "Clause Comparison Report" on the top of View Panel

Click on deviation tab.

Click on Versions Tab

Click on team tab.

Click on "Team" tab. Click on add team (+) button.

Select role as deviation approver, step number as 1. Select

clause [Only deviated clauses should be display] from the
dropdown list. Add multiple approvers to 1 clause with
different step number. Select another clause and add other
user from the pop-up and different step number. Click on add
button.

login by deviation approver and verify that deviation approver

get notification about 'user is added to the team.

Login to the application by valid user [CM of the pre-

requisities agreement]. Send agreement for approval.
Login to the application by valid user [CM of the pre-
requisities agreement].
Verify that the User is able to Search for the above created
agreement [Pre-requisities]from agreement Index page/ main
Search page. Open french language agreement.

click on view (eye icon) record button.

Download and Open the downloaded document and make

changes and save the document. Subsequently Click on
Upload document and upload the previously saved document
Click on "Compare changes with previous document version"
on the top of View Panel.
Click on deviation tab.

Click on team tab.

Click on "Team" tab. Click on add team (+) button.

Select role as deviation approver, step number as 1. Select

clause [Only deviated clauses should be display] from the
dropdown list. Select Legal approver as a deviation approver
for the 'French' language agreement. Click on add button.

Now Search for the second agreement-English language

agreement [Pre-requisities]from agreement Index page/ main
Search page. Open the agreement.

click on view (eye icon) record button.

Click on deviations tab.

Click on team tab.

Click on "Team" tab. Click on add team (+) button.

Select role as deviation approver, step number as 1. Select

clause [Only deviated clauses should be display] from the
dropdown list. Select CM as a deviation approver for the
'English' language agreement. Click on add button.
Expected Result Pass/Fail Bug ID

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.

Attribute value should be display as per entered into the

request and in dropdown below values should be display. 1.
Simple 2. Complex

Entered mandatory data should be display. File should get

uploaded.

In case of Own type of paper-template selection page should

be display. In case of third party- verify page with all the
entered data should be display.
Verify page should be displayed.

Agreement should get created and published. A notification

should get created for agreement creation and history should
get generated.

By default Primary owner should be display. CM should be the

PO of the agreement. Other users should display depending
upon the satisfied conditions of the rule.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.
All the selected data should be display on contract type page.
Attribute page should display inherited data from contract
request for which data is entered during request creation.
An agreement should get created. An agreement code should
also get created and it should be unique.

Agreement code should display in below format: Contract

type name_current year_6digit number Example:
MSA_2017_000001 SOW_2017_000002

Request index page should be display.

A contract request creation page should be display.

Sanofi Legal Entity' attribute should not be display.

Request should get created and approved.

Agreement creation page should be display with category,
contract type and type of paper attribute.

All the selected data should be display on contract type page.

Attribute page should display inherited data from contract
request for which data is entered during request creation.

Sanofi Legal Entity' attribute should be display.

Entered data should be display.
An agreement should get created. An agreement code should
also get created and it should be unique.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.

attribute should display below attribute. 1. Simple 2. Complex

Entered data should be display preperly.
Agreement should get created.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.[As per consideration there
should be an attribute for WO/SOW like MSA parent
agreement and it should have value of MSA agreement code]

attribute should display below attribute. 1. Simple 2. Complex

Entered data should be display preperly.

Agreement should get created.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

In work order, MSA entity should not be availabe for
inheritance.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.

An agreement should get created for WO contract type.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Leading cost centre value should also get inherited from the
contract request during agreement creation. Leading cost
centre should have only one value for each request.

User should be logged in successfully.

1. Ageement should be displayed in the Search results. 2.

Columns should reflect the agreement data.
On click on view record button agreement details should be
display.

By default primary owner should be display. Depending upon

the satisfied condition of the approver rule [Pre-requisities],
financial controller approver will get displayed into the team
tab.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.
Simple' as a Attribute value should be display. This attribute
will be editable.
Entered mandatory data should be display. File should get
uploaded.

In case of Own type of paper-template selection page should

be display. In case of third party- verify page with all the
entered data should be display.
Verify page should be displayed.

Agreement should get created and published. A notification

should get created for agreement creation and history should
get generated.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.
Complex' as a Attribute value should be display. This attribute
will be editable.

Entered mandatory data should be display. File should get

uploaded.

In case of Own type of paper-template selection page should

be display. In case of third party- verify page with all the
entered data should be display.
Verify page should be displayed.

Agreement should get created and published. A notification

should get created for agreement creation and history should
get generated.
By default Primary owner should be display. CM should be the
PO of the agreement. Other users should display depending
upon the satisfied conditions of the rule.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.
Simple' as a Attribute value should be display. This attribute
will be editable.

An agreement should get created and published.

Deviation should not get generate for the clauses.

Document should get saved and should get uploaded

successfully.
Deviation should get generate for the clauses.
Deviation approver should also get added to the team [if
deviation approver rule is available]

Contract Policy Type' value should get changed to 'Complex'.

Agreement should get updated.

Legal approvers and deviation approvers and CM. Draft

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.
Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.
Simple' as a Attribute value should be display. This attribute
will be editable.

' Complex' as a Attribute value should be display. An

agreement should get created and published.

Document should get saved and should get uploaded

successfully.
Deviation should get generate for the clauses.
Deviation approver should also get added to the team [if
deviation approver rule is available]
User should be logged in successfully. Create masterdata page
should be display.

Attribute page should be display.

Entered data should be display.

A masterdata for 'Leading cost centre' should get created.

User should be logged in successfully. Create request page
should be display.
Attribute page should be display.

Selected value should be display.

Request should get created and approved.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should
display inherited data from contract request for which data is
entered during request creation.

Leading cost centre attribute value should be display as per

entered during masterdata creation and as per request.

An agreement should get created and published.

Depending upon the satisfied condition of the approver rule

[Pre-requisities], Financial controllers as approvers will get
displayed into the team tab

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.
Expiry date attribute should be an date type attribute and no
data should be display into it from the request.

After selection of effective date, expiry date should not get

calculated [no auto generation of configuration should
present for expiry date].

Primary owner/Contract Manager can select expiry date.

On verify tab, correct data for all the attribute should be
display.

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.
Selected data should be display properly.

Attribute page should be display. Attribute page should

display inherited data from contract request for which data is
entered during request creation.
A toggle button should be display for the attribute 'Vendor
available'

Vendor details attribute with lookup will get displayed and

user can select the vendor from lookup search pop-up.
Vendor details attribute without lookup should be display and
user should able to enter data.

Entered data should be display.

a. System should navigate user to ICM Dashboard. b. Function

Tiles and Dashboard KPI's should appear on the screen based
on the access permissions assigned to the log-in user.

User should be navigated to create request wizard

Selected category and request type should be displayed.

a. System should navigate to Attribute tab

Entered data should be display.

Select team should be display.

a. System should navigate to summary page. B. All the

metadat information should be displayed correctly in
summary page. C. All the contract types which satisfies the
contract type selection rule should be display.

System should create the contract request. Verify the

information displayed in details tab. A notification should get
created after contract request creation. Contract request
creation history should get created.
Contract request should get approved.

Buttons should not be display. Purchasing partner should not

be able to edit the contract request after approval of the
request.

User should be logged in successfully.

a. Contract request should be displayed in the Search results.

b. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type attribute.

Contract Type dropdown list should show all the contract

types for which access is provided to the log-in user and are
present under selected category. Selected contract type
should be displayed.

a. System should navigate to Attribute tab b. Attribute page

should display inherited data from contract request for which
data is entered during request creation. C. Mandatory
metadata fields should be indicated with an Asterisk (*)
symbol.
All the entered values should be display properly.
System should display approriate template depending on the
selected language and agreement type.
System should display Verify tab. All the metadat information
should be displayed correctly in verify tab
System should create the contract. Verify the information
displayed in details tab
Agreement should get published.

A mandatory association validation message gets displayed.

Selected association/record should get added to the system.

MSA number should get updated.

User should be logged in successfully.

a. Contract request should be displayed in the Search results.

b. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type attribute.

Contract Type dropdown list should show all the contract

types for which access is provided to the log-in user and are
present under selected category. Selected contract type
should be displayed.

a. System should navigate to Attribute tab b. Attribute page

should display inherited data from contract request for which
data is entered during request creation. C. Mandatory
metadata fields should be indicated with an Asterisk (*)
symbol.
All the entered values should be display properly.
System should display approriate template depending on the
selected language and agreement type.
System should display Verify tab. All the metadata
information should be displayed correctly in verify tab
System should create the contract. Verify the information
displayed in details tab
Agreement should get published.
Primary owner, approvers and signatory users should be
display.

Agreement should get approved.

Agreement status should become 'Waiting for external

signature from (username). External signature user should get
email for sign.
An agreement document should get opened. User should able
to sign on the document.

Agreement status should become 'approved. External

signature user should get email for voidation of the sign.
An agreement document should not get opened. User should
not able to sign on the document.

An agreement should get updated with new data.

Agreement should get approved.

Agreement status should become 'Waiting for external

signature from (username). External signature user should get
email for sign.
An agreement document should get opened. User should able
to sign on the document.

User should be logged in successfully.

a. agreement should be displayed in the Search results. b.

Columns should reflect the agreement data.
On click on view record button agreement details should be
display.
An agreement document will get shared with the vendor via
supplier portal.(A vendor is already provisioned into the ICM
and should have login details) A notification should get
generated to the vendor/user.
User should get login successfully and document should get
downloaded successfully.

A document should get uploaded successfully. An email

should get generated to the primary owner about the
deviation.

In agreement document changed data should be display.

Vendor should get email from ICM application with

CM/primary owners' comments.
Agreement document should get updated as per comments
provided by CM/Primary owner .

CM/Primary owner should get updated document.

In agreement document changed data should be display.

Agreement document should get updated as per
changes/cpmments provided by Vendor .
Agreement should get approved.

User should be logged in successfully.

a. agreement should be displayed in the Search results. b.

Columns should reflect the agreement data.
On click on view record button agreement details should be
display.
Select user pop-up should be display.

A user with selected role should get added.

User should login successfully and agreement details page
should get opened.

Observer should able to download the document.

User should be logged in successfully.

a. agreement should be displayed in the Search results. b.

Columns should reflect the agreement data.
On click on view record button agreement details should be
display.
Agreement status should be 'Waiting for approval'.
Select user pop-up should be display.

A user with selected role should get added.

User should login successfully and agreement details page
should get opened.

Observer should able to download the document.

User should be logged in successfully.

1. Agreement should be displayed in the Search results. 2.

Columns should reflect the agreement data.
On click on view record button agreement details should be
display.

System should upload and refresh the screen

System should display the changes made in clauses

System should display deviations.
System should display all versions associated with the
agreement
System should display all the users correctly. Currently there
is no deviation approvers.
Select user pop-up will get displayed with all the provisioned
users.

Selected user with role, step number should be display.

Example: Clause A -requires approval from all approvers
[approver 1, approver 2] present at step 1 Clause B -requires
approval from all approvers [approver 3, approver 4] present
at step 2

A notification should get generate to the deviation approver.

Agremeent status should become 'Waiting for deviation

approval 'Username'. A notification, task should generate to
deviation approver. History should generate for the approval
action.

User should be logged in successfully.

1. Agreement should be displayed in the Search results. 2.
Columns should reflect the agreement data.
On click on view record button agreement details should be
display.

System should upload and refresh the screen

System should display the changes made in clauses

System should display deviations.
System should display all the users correctly. Currently there
is no deviation approvers.
Select user pop-up will get displayed with all the provisioned
users.

Selected user with role, step number should be display.

1. Agreement should be displayed in the Search results. 2.

Columns should reflect the agreement data.
On click on view record button agreement details should be
display.

System should display all the deviations if already present.

System should display all the users correctly. Currently there
is no deviation approvers.
Select user pop-up will get displayed with all the provisioned
users.

Selected user with role, step number should be display.

Comments
TC No Test Case Title Summary
[REQ_I_001] Verify name of the request
type is "Buy Side" for Buy Side as well as
CDA/NAD requests

172694.1 Pre-requisite :
 
1. Contract type precondition :
1. Contratc
Request agreement type
172694.2 should exists in the system
2. Rules precondition :
NA 
172694.3 3. User precondition &
privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
172694.4 manage previleges on Agreements
Tile
172694.5  
172694.6 4. Others if any
[REQ_I_001] Verify Purchasing Partner can
manually create request in ICM e-Contract
application Pre-requisite :
 
1. Contract type precondition :
172695.1
1. Contratc
Request agreement type
should exists in the system
2. Rules precondition :
NA 
172695.2 3. User precondition &
privileges :
- Purchase Partner should have
172695.3 Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
172695.4 4. Others if any
[REQ_I_002] Verify if Contract Manager has
access on Contract request Pre-requisite :
 
1. Contract type precondition :
1. Contratc
172714.1
Request agreement type
should exists in the system
2. Rules precondition :
NA 
3. User precondition &
172714.2 privileges :
- Contract Manager should have
Manage privilege on ICM
172714.3 - Contract Manager should
have manage previleges on
Agreements Tile
 
4. Others if any
172714.4 NA
 Verify if Contract request category “Buy”
and contract request type “Buy Side”
defaulted automatically while creating
contract request Pre-requisite :
172739.1  
1. Contract type precondition :
1. Contratc
Request agreement type
should exists in the system
2. Rules precondition :
172739.2 NA 
3. User precondition &
172739.3 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
172739.4 4. Others if any
Verify that Once the contract request is
submitted, the contract request will be
routed to selected contract manager

172794.1

172794.2

172794.3

Pre-requisite :
 
1. Contract type precondition :
172794.4
1. Contratc
Request agreement type
172794.5 should exists in the system
2. Rules precondition :
172794.6 NA 
172794.7 3. User precondition &
privileges :
- Purchase Partner should have
172794.8 Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
172794.9 4. Others if any
172795.1 [REQ_D_001] Verify the format of system
generated request number as per defined
format
172795.2

172795.3

Pre-requisities:1. A request type

contract type should exist with
approved state and Purchasing
partner should have manage
privilege for contract request tile and
 format

Pre-requisities:1. A request type

172795.4 contract type should exist with
approved state and Purchasing
partner should have manage
privilege for contract request tile and
172795.5 request contract type.
172797.1 [REQ_D_002] Verify if the request name
field is the mandatory field
172797.2

172797.3

172797.4 Pre-requisities:1. A request type

contract type should exist with
approved state and having Request
name
172797.5 2. Purchasing partner should have
manage privilege for contract
request tile and request contract
172797.6 type.
172798.1 [REQ_D_002] Verify if the request
description field is non-mandatory field
172798.2

172798.3

172798.4 Pre-requisities:1. A request type

contract type should exist with
approved state and
having request description.2.
172798.5 Purchasing partner should have
manage privilege for contract
request tile and request contract
172798.6 type.
172825.1 [REQ_D_003] Verify Purchasing Partner has
the ability to select one or “Spend
Category”
172825.2

172825.3
172825.4

Pre-requisities:1. A request type

172825.5 contract type should exist with
approved state and having 'Spend
172825.6 Category' attribute.2. Purchasing
partner should have manage
privilege for contract request tile and
172825.7 request contract type.
 172826.1 [REQ_D_004] Verify that only one vendor is
allowed per request. Multi-vendor is not in
scope.
172826.2

172826.3
172826.4

172826.5

172826.6
172826.7

172826.8

Pre-requisities:1. A request type

172826.9 contract type should exist with
approved state and having vendor
attributes with lookupcascade.2.
172826.1 Purchasing partner should have
manage privilege for contract
request tile and request contract
type.3. Vendor masterdata should
172826.11 exist.
172827.1 [REQ_D_005] Verify if 'End User' field is the
mandatory field on contract request form
172827.2

172827.3
Pre-requisities:1. A request type
172827.4 contract type should exist with
approved state and having 'End User'
attribute.2. Purchasing partner
should have manage privilege for
172827.5 contract request tile and request
172827.6 contract type.
172828.1 [REQ_D_006] Verify purchase partner can
select one 'leading cost centre' per request.
172828.2

172828.3
Pre-requisities:1. A request type
contract type should exist with
approved state and having 'Leading
172828.4 cost centre' attribute 2. Purchasing
partner should have manage
172828.5 privilege for contract request tile and
request contract type.2. A
masterdata record for 'Leading cost
172828.6 centre' should exist.
172829.1 [REQ_D_007] verify if 'Business Area' field
is a free-text and non-mandatory field.
 [REQ_D_007] verify if 'Business Area' field
is a free-text and non-mandatory field.
172829.2

172829.3

Pre-requisities:1. A request type

contract type should exist with
172829.4 approved state having 'Business
172829.5 Area' attribute.2. Purchasing partner
should have manage privilege for
contract request tile and request
172829.6 contract type.
172830.1 [REQ_D_008 ] Verify that Effective and
Expiry fields are not present on request
form. "Needed by date" non-mandatory
172830.2 field should be there.

172830.3

172830.4

172830.5

172830.6
Pre-requisities:1. A request type
contract type should exist with
172830.7 approved stateand this contract type
should not have effective and expiry
172830.8 date attribute.2. Purchasing partner
should have manage privilege for
contract request tile and request
172830.9 contract type.
172831.1 [REQ_D_009] Verify renamed fields :
Vendor email address, Vendor contact
number and Attribute Contract Manager
172831.2 comments needs to be nonmandatory field
Pre-requisities:1. A request type
contract type should exist with
172831.3 approved state and should have
'Vendor contact email address',
'Vendor contact phone
number'and  'Contract
manager comments' attribute.2.
Purchasing partner should have
manage privilege for contract
request tile and request contract
172831.4 type.
[REQ_D_010] Verify if the appropriate
message is getting displayed if Request for
Amendment is set as 'Yes'

172832.1

Pre-requisite :
 
1. Contract type precondition :
1. Contratc
Request agreement type
 [REQ_D_010] Verify if the appropriate
message is getting displayed if Request for
Amendment is set as 'Yes'

Pre-requisite :
 
1. Contract type precondition :
172832.2
1. Contratc
Request agreement type
172832.3 should exists in the system
2. Rules precondition :
NA 
3. User precondition &
privileges :
- Purchase Partner should have
172832.4 Manage privilege on ICM
- Purchase Partner should have
172832.5 manage previleges on Agreements
Tile
 
172832.6 4. Others if any
[REQ_D_011] Verify if the message is
getting dsaplayed to Purchasing partner
informing to upload the required
attachments in Association, before
172834.1 submitting the Request

172834.2
Pre-requisite :
172834.3  
1. Contract type precondition :
1. Contratc
Request agreement type
should exists in the system
2. Rules precondition :
172834.4 NA 
3. User precondition &
172834.5 privileges :
- Purchase Partner should have
172834.6 Manage privilege on ICM
172834.7 - Purchase Partner should have
manage previleges on Agreements
Tile
 
172834.8 4. Others if any
172835.1 [REQ_D_012] Verify is send for approval
button is remaned as 'Submit'
172835.2

172835.3
172835.4
172835.5 Pre-requisities:1. A request type
contract type should exist with
172835.6 approved state.2. Purchasing partner
should have manage privilege for
contract request tile and request
contract type.
 Pre-requisities:1. A request type
contract type should exist with
approved state.2. Purchasing partner
should have manage privilege for
contract request tile and request
172835.7 contract type.
[REQ_D_014] Verify if attribute :
'Reportable consulting agreements' is
added in the request form

172836.1

Pre-requisite :
172836.2  
1. Contract type precondition :
1. Contratc
172836.3 Request agreement type
should exists in the system
2. Rules precondition :
NA 
3. User precondition &
172836.4 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
172836.5 4. Others if any
[REQ_D_015] Verify if Delete and Edit
buttons are not getting displayed once the
request got approved

172837.1

172837.2

172837.3
Pre-requisite :
 
1. Contract type precondition :
1. Contratc
172837.4 Request agreement type
should exists in the system
2. Rules precondition :
172837.5 NA 
172837.6 3. User precondition &
172837.7 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
172837.8 4. Others if any
 [REQ_D_016] verify that Sanofi entity
Registration code should appear only for
entity : France
172838
[REQ_D_018] verify if attribute :
"Geographical Coverage" is created to
identify a Contract is created for
Worldwide or to a specific country or
172839.1 multiple countries.

Pre-requisite :
172839.2  
1. Contract type precondition :
1. Contratc
172839.3 Request agreement type
should exists in the system
2. Rules precondition :
NA 
3. User precondition &
172839.4 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
172839.5 4. Others if any
[REQ_D_019] Verify that Country, BU
attributes will not be present in Request
creation and Contract creation form

172840.1

Pre-requisite :
 
1. Contract type precondition :
172840.2
1. Contratc
Request agreement type
172840.3 should exists in the system
2. Rules precondition :
NA 
3. User precondition &
privileges :
- Purchase Partner should have
172840.4 Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
172840.5 4. Others if any
[REQ_C_001] Verify if Contract Manager
can select the CM group, instead of Triage

176108.1
 [REQ_C_001] Verify if Contract Manager
can select the CM group, instead of Triage

176108.2

176108.3

176108.4

176108.5 Pre-requisite :
176108.6  
1. Contract type precondition :
176108.7
1. Contratc
176108.8 Request agreement type
176108.9 should exists in the system
2. Rules precondition :
176108.1 NA 
176108.11 3. User precondition &
privileges :
- Purchase Partner should have
176108.12 Manage privilege on ICM
176108.13 - Purchase Partner should have
176108.14 manage previleges on Agreements
Tile
176108.15  
176108.16 4. Others if any
[REQ_C_002] Verify if Contract Manager
can fill required information on Request
form/ attribute page

176110.1

176110.2

176110.3

176110.4
Pre-requisite :
176110.5  
1. Contract type precondition :
176110.6 1. Contratc
176110.7 Request agreement type
should exists in the system
2. Rules precondition :
176110.8 NA 
3. User precondition &
privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
 1. Contratc
Request agreement type
should exists in the system
2. Rules precondition :
NA 
3. User precondition &
privileges :
- Purchase Partner should have
Manage privilege on ICM
176110.9 - Purchase Partner should have
manage previleges on Agreements
Tile
176110.1  
176110.11 4. Others if any
[REQ_C_003] Verify if CM can identify Request agreement type
Simple, Complex and Exempt type on should exists in the system
Contract Request stage 2. Contract Request - A should be
176111.1 created and in approved state
 
2. Rules precondition :
NA 
3. User precondition &
176111.2 privileges :
- Purchase Partner should have
176111.3 Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
- Contract
176111.4 Manager should have Manage
privilege on ICM
- Contract
Manager should have manage
previleges on Agreements Tile
 
176111.5  
176111.6 4. Others if any
[REQ_C_004] Verify if email notification
sent to appropriate users post creation of
request

176120.1

176120.2

176120.3

176120.4

176120.5
176120.6
176120.7

176120.8
176120.9
Action

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Login to the ICM application as Contract Manager

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Fill all required fields and hit next button
Hit Create Request button

Hit Submit Button

1. Now login with valid CM_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile
Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Enter all the mandatory data and create the contract request.

Check the request code format.

Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Verify the 'Request name' attribute.

Without entering any data , click on next button.

Enter other required mandatory data and create the request.

Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Verify the 'Request description' attribute.

Without entering any data , click on next button.

Enter other required mandatory data and create the request.

Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Now check for the attribute 'Spend category'.

Click on search icon to select the record.

Check for 'Sub Spend category' attribute.

Without entering any data , click on next button.

Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Check for vendor attribute.

If user select as 'Yes'

If user select as 'No'

Again set toggle to 'Yes'

Click on search icon displaying in front of the vendor name.

Verify that user can select multiple vendors.

Select one vendor record and click on add button.

During contract/agreement creation also user can select only

one vendor masterdata.For each vendor separate contract
should get created.
Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Now check for the attribute 'End User'.

Click on search icon present infront of the end user.

Without entering any data , click on next button.
Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Check for the attribute related to 'Leading cost centre'. Click

on search pop-up present infront of the attribute.
Verify that user can select more than one 'Leading cost
centre'

Without entering any data , click on next button.

Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Check for the attribute related 'Business Area'.

Enter data into 'business area' attribute.

Without entering any data , click on next button.

Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Check for the attribute Effective date and Expiry date.

Check for the attribute 'Needed by date'. Enter data into

'Needed by date' attribute.

Without entering any data , click on next button.

Check for the attribute 'Description of service'.

Check for the attribute Service Delivery address and its
related attributes.

Do not enter data into any attribute and clcik on next button.
Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Verify the attributes 'Vendor contact email address', 'Vendor

contact phone number'and 'Contract manager comments.

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

On attribute page toggle button from No to Yes for 'Is this an
amendment ?' attribute

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Fill all required fields and hit next button
Hit Create Request button

Hit Submit Button

Login to the ICM application by purchasing partner.
Navigate to agreement management->create contract
request

Select category, contract type name and click on next button.

Enter data in all the mandatory attribute.
Click on create request button.
Check the buttons displaying below the attributes on details
page.
Click on submit button.

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Fill all required fields and hit next button
Hit Create Request button

Hit Submit Button

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Fill all required fields and hit next button
Hit Create Request button
Hit on Team section
Add contract manager to the team
Login as CM
Hit on team section

Try to add CM group

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Fill all required fields and hit next button
Hit Create Request button

Hit Submit Button

1. Now login with valid CM_x000D_
2. Click on agreement tile _x000D_
3. Click on request tile

Hit edit button

Login to the ICM application as Contract Manager

Click on Agreement Tile

Click on Request Tile

Click on Request A (Mentioned in pre-requisite)

Click on edit button

Login to the ICM application as Purchase Partner

Click on agreement tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Hit Next button

Fill all required fields and hit next button
Hit Create Request button

Hit Submit Button

Expected Result Pass/Fail Bug ID

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

1. System should allow Contract Manager_x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Contract Manager.

1. Contract Manager should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Contract Manager

Contract Manager should navigate to Create request page

1. Contract Manager should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'
1. System should allow Purchase Partner _x000D_
to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy, request type should be
displayed as 'Buy Side' (defaulted automatically)

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

User should navigate to confirmation page.
Contract Request should get created in draft state
1. Agreement should move to approved state_x000D_
2. Appropriate CM should get added to the team

1. CM should navigate to contract request page

successfully._x000D_
2. Previously created contract request should be displayed in
approved state.
User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

A contract request should get created. A request code should
also get created and it should be unique. A notification and
history should get genrated.

Request code should display in below format:

REQ_year_6digit number Example: REQ_2017_000001
REQ_2017_000002
User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Request name should be mandatory and editable attribute.

Purchasing manager can enter data into this attribute.

Validation message for 'Request name' should be display.

Validation message for 'Request description' should not be
display.
A request should get created. A notification and history
should get genrated.
User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Request name should be non-mandatory and editable

attribute. Purchasing manager can enter data into this
attribute.

Validation message for 'Request name' should be display.

Validation message for 'Request description' should not be
display.
A request should get created. A notification and history
should get genrated.
User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Spend category attribute should be non-mandatory.

Search pop-up should display 'HACAT code' and description.

User is able to select more than one record from serch pop-
up.

This attribute should not be display during request creation.

Validation message for 'Spend category' should not be display.

User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Vendor attribute with toggle should be display.

all the vendor attributes with lookup should be display.

all the vendor attributes without lookup should be display.

User can enter manually data for the vendor attributes.
Vendor attribute with lookup should be display.
A search pop-up with all the records of vendor masterdata
should be display.

User should not be able to select multiple vendor records.

User is able to create request for only one vendor.
All the vendor details available for that record should be
display in vendor attributes.

User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Spend category attribute should mandatory .

A search pop-up with all the provisioned users should be

display. Purchasing manager is able to select any user from
the search pop-up.
Validation message for 'End user' should be display.
User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

A search pop-up should be display all the records/instances of

'Leading cose centre' masterdata. This attribute should be
non-mandatory.

User will select only one 'Leading cost centre' for request.
Validation message for 'Leading cost centre' should not be
display.
User should be logged in successfully.
1. Contract request creation page should be displayed.

Attribute page should be display.

Business area attribute should be a textbox and user can

manually enter the data. Business area attribute is a non-
mandatory attribute.
Entered data should be display.

Validation message for 'Business area' should not be display.

User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Effective date and Expiry date attribute should not be display.

Date type attribute 'Needed by date'should be display and it

should be non-mandatory.Entered data should be display [ It
will be the date by which Contract needs to be created in e-
Contract tool].

Validation message for 'Business area' should not be display.

Text type attribute should be diplay and it should be non-
mandatory.
Service Delivery address and its related attributes needs to be
excluded on request creation form
Mandatory validation message should not be display for
above attributes.
User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Updated attribute name should be display. Vendor email

address should be renamed as Vendor Contact Email address
Vendor Contact Number should be renamed as Vendor
Contact Phone Number Contract Manager comments
attribute should be non-mandatory

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .
1. Purchase Partner should navigate to Agreement
Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

Attribute to search parent contract should be displayed with
label : 'Parent Contract'

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

User should navigate to confirmation page.
Contract Request should get created in draft state

Application should display a message to the user informing to

upload the required attachments in Association before
submitting contract request.
User should be logged in successfully.

1. Contract request creation page should be displayed.

Attribute page should be display.

Entered data should be display.
A contract request should get created.
Edit, Submit, delete, Request review, on hold, cancel buttons
should be display.
A contract request should go for approval and status should
become 'Waiting for approval'

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

1. User should naviagte to attribute page of Contract

Request_x000D_
2. 'Reportable Consulting Agreements' attribute with yes/no
dropdown values should be displayed on attribute page.

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

User should navigate to confirmation page.
Contract Request should get created in draft state

1. Agreement should move to approved state_x000D_

2. Appropriate CM should get added to the team by
rule_x000D_
3. Delete and Edit buttons should not be displayed on the
page
1. System should allow Purchase Partner _x000D_
to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

1. User should naviagte to attribute page of Contract

Request_x000D_
2. 'Geographical Coverage' attribute with values :
'WORLDWIDE' and other countries should be displayed on the
page

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

1. User should naviagte to attribute page of Contract

Request_x000D_
2. Country and BU these attributes should not be displayed on
the attribute page

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .
1. Purchase Partner should navigate to Agreement
Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

User should navigate to confirmation page.
Contract Request should get created in draft state
Team page should be displayed
User should be able to add CM successfully.
CM should login to the application successfully.
Team page should be displayed

CM should be able to add CM group to the team successfully.

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

User should navigate to confirmation page.
Contract Request should get created in draft state
1. Agreement should move to approved state_x000D_
2. Appropriate CM should get added to the team
1. CM should navigate to contract request page
successfully._x000D_
2. Previously created contract request should be displayed in
approved state.
1. User should navigate to Attribute in edit mode_x000D_
2. User should be able to edit request successfully

1. System should allow user to login to the application

successfully._x000D_
2. Agreement tile should be visible to the user.

1. User should navigate to Agreement Management

Page_x000D_
2. Request and Create requests tiles should be displayed on
the page
User should navigate to Requests page

1. User should navigate to Request A page_x000D_

2. Request A should be in approved state_x000D_
3. Edit button should be displayed to the user on the page

1. User should navigate to Attribute page_x000D_

2. Under 'For Contract Managers Only' section user should be
able to select policy type as : 'Simple' or 'Complex' or 'Exempt'

1. System should allow Purchase Partner _x000D_

to login to the application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

User should navigate to confirmation page.
Contract Request should get created in draft state

1. Agreement should move to approved state_x000D_

2. Appropriate CM should get added to the team_x000D_
3. Appropriate CM should get email notification
Comments
TC No Test Case Title Summary
186328.1 Verify validations on outbound CSV file for
data of "Expired" agreements.

186328.2
186328.3

186328.4

186328.5
186328.6

186328.7
186328.8
186328.9

186328.1
Verify the file structure of the "Executed",
"Expired" agreements on the SFTP server.
186329.1

186329.2

186329.3

186329.4

186329.5

186329.6

186329.7

186329.8
 186329.9

186329.1
186331.1 Verify that SFTP to ICM CSV file of "Vendor
Master data" is processed by ICM
186331.2

186331.3
186331.4
186332.1 Verify the user able to add/ update/
activate and deactivate the records of
186332.2 "Vendor masterdata" with Cyrilic
Characters
186332.3
186332.4

186332.5
186332.6

186332.7
186332.8

186332.9
186332.1
186332.11
186332.12
186332.13
186332.14
186332.15

186332.16
186333.1 Verify the folder structure for "vendor
masterdata".
186333.2

186333.3

186333.4

186333.5

186333.6
 186333.7

186333.8
186333.9
186334.1 Verify that SFTP to ICM CSV file of "Leading
Cost Center" is processed by ICM
186334.2

186334.3
186334.4
186335.1 Verify the user able to add/ update/
activate and deactivate the records of
186335.2 "Leading Cost Center".

186335.3
186335.4

186335.5
186335.6

186335.7
186335.8

186335.9
186335.1
186335.11
186335.12
186335.13
186335.14
186335.15
186336.1 Verify the folder structure for "Leading Cost
Center" masterdata.
186336.2

186336.3

186336.4

186336.5

186336.6
186336.7
186337.1 Verify that SFTP to ICM CSV file of
"Controller Assignment " is processed by
ICM
186337.2

186337.3
186338.1 Verify the user able to add the records of
"Controller Assignment".
186338.2
186338.3

186338.4
186338.5
186338.6
186338.7

186338.8
186339.1 Verify the folder structure for "Controller
Assignment" masterdata.
186339.2

186339.3

186339.4
186339.5

186339.6

186339.7
[Sanofi][Vendor]: Verify if vendor name
concatenation with Vendor ID
273559.1
273559.2
273559.3
273559.4

273559.5
273594.1 [Sanofi]: Verify Auto renewal Functionality

273594.2

273594.3

273594.4
273594.5

273594.6

273594.7
[Sanofi]: Verify the ability to change the
template post Agreement Publish
273603
[Sanofi][Wave 0]: Verify 'Easy Access'
integration.
285294.1

285294.2

285294.3

285294.4
[Sanofi][Wave 0]: Verify if ''Leading cost
center' is getting Auto selected on the basis
of Requestor
285305
[Sanofi][Wave 0]: Verify the currency
selection depending upon country specified
in Easy Access.
285975
[Sanofi][Preprod]: Vendor integration with
3 new SAP
289240
Action
Pre-Requisite:Request should be in approved state.

Log-on to ICM application with CM of (Above request) user

credentials"
Click on agreement management->Request Tile

Open the above created "Request" and click on "Create

Contract" button.

Fill all the attributes values and click on "Next" button. Upload
the file if type of paper is "third party".
Select the template and click on "Next" button.
Create and publish the agreement with expiry date as
yesterday
Execute the agreement till the "Approved" state.
Execute the agreement till the "Executed" state.

Ask developer to run the Expiry task.

Pre-Requisite: File for "Execute" ,"Expired" and "Terminate"
agreement should be generated.

Verify the "column D" content of the file.

Verify the two CSV files placed on SFTP server.

Verify the file placed on correct folder.

Verify the "Active" flag for "Executed" agreements/
Amendments.
Verify the "Active" flag for "Expired" agreements/
Amendments.
Verify the name in the file for the "Executed" agreements/
Amendments.
Verify the name in the file for the "Executed" agreements/
Amendments.
Verify the layout of the csv file for "Executed" agreements.

Verify the layout of the csv file for "Expired" agreements.

Login to SFTP server

Verify that ICM job has run successfully at the scheduled time

Verify that the records that are correct.

Verify the only active records get display.
Login to "SFTP" server.
Navigate to latest "CSV" file and open the file.

Select the "Active flag" as "Yes" for the one or more records.
Enter the all details for the new record.
Select the "Active flag" as "Yes" for the one or more records
for existing record.
Update the some values of the records.

Select the "Active flag" as "NO" for the one or more records.
Enter the all details for the new record.
Select the "Active flag" as "NO" for the one or more records
which is existing.
Verify task run successfully.
Navigate to "ICM" master data and verify the records.
For "New Record" and "Active flag" as "Yes"
For "Existing Record" and "Active flag" as "Yes"
For "New Record" and "Active flag" as "NO"
For "Existing Record" and "Active flag" as "NO"

Try above scenarios with some Cyrilic characters.

Login to SFTP server
Verify the unique key identifier in the "File".

Verify the folder after the post processing of file.

Verify the "failed to upload file" stored on SFTP.

Verify the column names in the file.

Verify the notification get generate when upload task is failed.

Verify that CSV file naming convention.

Verify the header of the CSV file.

Verify the file placed in correct folder.
Login to SFTP server

Verify that ICM job has run successfully at the scheduled time

Verify that the records that are correct.

Verify the only active records get display.
Login to "SFTP" server.
Navigate to latest "CSV" file and open the file.

Select the "Active flag" as "Yes" for the one or more records.
Enter the all details for the new record.
Select the "Active flag" as "Yes" for the one or more records
for existing record.
Update the some values of the records.

Select the "Active flag" as "NO" for the one or more records.
Enter the all details for the new record.
Select the "Active flag" as "NO" for the one or more records
which is existing.
Verify task run successfully.
Navigate to "ICM" master data and verify the records.
For "New Record" and "Active flag" as "Yes"
For "Existing Record" and "Active flag" as "Yes"
For "New Record" and "Active flag" as "NO"
For "Existing Record" and "Active flag" as "NO"
Login to SFTP server
Verify the unique key identifier in the "File".

Verify the folder after the post processing of file.

Verify the failed to upload file stored on SFTP.

Verify the column names in the file.

Verify the notification get generate when upload task is failed.

Verify that CSV file naming convention.
Login to SFTP server

Verify that ICM job has run successfully at the scheduled time

Verify that the records that are correct.

Login to "SFTP" server.
Navigate to latest "CSV" file and open the file.
Enter the details of records.

Verify the properties of conroller group and it's users.

Enter the 10 user details for one controller group.
Verify task run successfully.
Navigate to "ICM" master data and verify the records.

Verify the new records and 10 users entry.

Login to SFTP server
Verify the unique key identifier in the "File".

Verify the folder after the post processing of file.

Verify the failed to upload file stored on SFTP.

Verify the column names in the file.

Verify the notification get generate when upload task is failed.

Verify that CSV file naming convention.

Create CSV files containing new vendor with mandatory data

Place the file under desired file location on SFTP
Run the task, Check if file is processed.
Log in to ICM.
Navigate to Vendor master and check if newly created
vendors are appearing with ID concatenated.
Log in to ICM.

Create agreement with Own paper type and Set Auto renew
to yes and provide valid data for Period, Cycles attributes.

Continue the agreement flow till agreement gets executed.

Task for Autorenewal shoul dbe in placec. Let the task runs.
Post task run, agreement should get Agreement Expiry date
changed depending upon the data we have submitted.
Try this for third party amd Own paper type. with all available
contract types.
Also try for multiple agreements due for auto renewal at
same time

Create a excel file with users to be uploaded to Sanofi

econtract. And provide this to Sanofi Team.

Log in with newly added user and check for access and other
details provided in the user creation Excel.
Another way of testing this is by creating User master data on
UI.

Verify this integration with combinations of different data.

Expected Result Pass/Fail Bug ID

a. System should navigate user to ICM Dashboard. b. Function

Tiles and Dashboard KPI's should appear on the screen based
on the access permissions assigned to the log-in user.
User should be navigated to create request wizard

User able to opened the "Request". "Create Contract" button

should be available and User navigate to agreement creation"
page.

User should able to enter the values. User should navigate to

"Template" selection page if type of paper is "Own".
User should navigate to "Attribute verify "page.

Agreement should get published.

Agreement should be in "Approved" state.
1. Agreement should go in executed state

Above executed agreement should get expired. 2. Once

agreement is executed following data needs to be transferred
from Icertis e-Contract application to eBuy : - Contract
ID/code ICMAgreementCode - Contract Name Name -
Vendor ID ICMVendorID - Vendor Name ICMVendorName -
HACAT number ICMSpendCategory - Amount
ICMContractValue - Currency Currency_ICMContractValue

column D should be put in double quotes not every part of

the concatenated string “[ContractName]-[VendorID]-
[VendorName]-[HACAT code]-[Amount]-[Currency]”

i. Executed contracts (Active list) Contract

code_DDMMM_HHMMSS ii. Expired contracts (Inactive list)
Expired_Date_DDMMM_HHMMSS
Files placed on Sanofi’s SFTP in the folder
“/Incoming/LookupValues”

"Active" flag should be a "Yes".

"Active" flag should be a "No".

need to confirm
Name= Active="Yes". External Ref Num = Contract code
Lookup = eContract
Name= Active="NO". External Ref Num = Contract code
Lookup = eContract
Login successful
Inbound CSV file is generated with new vendor records added
to it from SFTP

Corresponding valid records are created in ICM successfully.

Only active records should get display.
User should able to login successfully.
File should get opened.

All the record reflects in the ICM masterdata.

New records should get created.

Change records should get reflected in "ICM".
New records should not get created.
Existing record should get deactivate.
vendors should get created, updated, or deleted/deactivated
with Cyrilic characters.
Login successful
"Vendor number" should be a unique identifier.

“Processed” folder with file name

“Processed_TBD_YYYYMMDDhhmmss” “Failed” folder with
file name “Failed_TBD_ YYYYMMDDhhmmss”.
Failed file store on SFTP and next time it have first preference
to upload.

Vendor Name|Vendor ID|Company Code|Vendor Address 1|

Vendor Address 2|Vendor City|Vendor State|Vendor Zip
Code|Vendor Country Name|Vendor Tax ID Number|Vendor
Registration Number|Active|

Notification email should be generated.

File naming is as expected List_<env>_<SAP platform
name>_vendor _yyyyMMddhhmmss.csv

Vendor ID,Company Code, Vendor Address 1, Vendor Address

2, Vendor City, Vendor State,Vendor Zip Code, Vendor
Country Name, Vendor Tax ID Number, Vendor Registration
Number, Active
/icmdusr/SanofiToICM/dataout
Login successful
Inbound CSV file is generated with new "Leading Cost Center"
records added to it from SFTP

Corresponding valid records are created in ICM successfully.

Only active records should get display.
User should able to login successfully.
File should get opened.

All the record reflects in the ICM masterdata.

New records should get created.

Change records should get reflected in "ICM".
New records should not get created.
Existing record should get deactivate.
Login successful
"Leading Cost Center" should be a unique identifier.

“Processed” folder with file name

“Processed_TBD_YYYYMMDDhhmmss” “Failed” folder with
file name “Failed_TBD_ YYYYMMDDhhmmss”.
Failed file store on SFTP and next time it have first preference
to upload.

Leading Cost Center, Company Code, Cost Center, Cost Center

Name, Management Center, Department, Controller Group

Notification email should be generated.

csv file name format will be <Region
Name>_LeadingCostCenter_yyyyMMdd "
Login successful
Inbound CSV file is generated with new "Leading Cost Center"
records added to it from SFTP

Corresponding valid records are created in ICM successfully.

User should able to login successfully.
File should get opened.
User should able to entered the details.
i. Maximum Controller groups = 3300 ii. Maximum users
assigned to one controller group is 9
User should able to enterd the details.
All the record reflects in the ICM masterdata.

New records should be reflected and 10 th user entry should

get failed.
Login successful
"Controller Group" unique identifier.

“Processed” folder with file name

“Processed_TBD_YYYYMMDDhhmmss” “Failed” folder with
file name “Failed_TBD_ YYYYMMDDhhmmss”.
Failed file store on SFTP and next time it have first preference
to upload.
Controller Group, conroller should be present.

Notification email should be generated.

"Region Name_ Controller Group_yyyyMMdd " file should be
this.

User should be able to successfully create CSV file for vendors.

File should get successfully placed.
File should get process with success message
User should get successfully logged in to the icm

The vendor name should be present with ID separated by -

User should get logged in.

User should be able to create agreement with Auto renewal

flag set to yes.

Agreement should get executed.

Task should get successfully run.

The agreement autorenewal should work for all valid
agreements due for autorenewal.

Sanofi team will push the API to the system. All the provided
users with all the data entered within should reflect on UI.

All the created user should have data as per excel file. Also
user should have privileges as per the specifications.

As per data filled up, the access, Privileges should work.

Comments
TC No Test Case Title Summary
[158710] Sanofi: Default value in Contract
Category field needs to be "Buy Side"
176126.1 Pre-requisite :
 
1. Contract type precondition :
1. Contract
Request agreement type
176126.2 should exists in the system
2. Rules precondition :
NA 
3. User precondition &
176126.3 privileges :
- Purchase Partner should have
Manage previlege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
 
176126.4 4. Others if any
[158723] Sanofi: Restrict CM to send the
contract document for Approval, if vendor
176202.1 is not selected.

176202.2

176202.3

176202.4

176202.5

176202.6

176202.7

176202.8
176202.9
176202.1
176202.11

176202.12
Pre-requisite :
 
1. Contract type precondition :
1. Contract
Request agreement type
should exists in the system
176202.13 2. Rules precondition :
NA 
3. User precondition &
176202.14 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
176202.15 manage previleges on Agreements
Tile
- Contract Manager should have
Manage privilege on ICM
- Contract
176202.16 Manager should have manage
privileges on Agreements Tile
176202.17  
176202.18 4. Others if any
[160173] Sanofi: Association page, hide the
Agreement code, Business status and
Name attribute during Request and
Contract creation
176297.1

176297.2

176297.3

176297.4

176297.5
176297.6
176297.7
 176297.8

176297.9

176297.1 Pre-requisite :
 
176297.11 1. Contract type precondition :
1. Contratc
Request agreement type
should exists in the system
2. Contract Request - A should be
present in the system with approved
176297.12 state.
2. Rules precondition :
NA 
3. User precondition &
privileges :
- Purchase Partner should have
Manage privilege on ICM
176297.13 - Purchase Partner should have
manage privileges on Agreements
Tile
- Contract Manager should have
Manage privilege on ICM
- Contract
176297.14 Manager should have manage
privileges on Agreements Tile
176297.15  
176297.16 4. Others if any
[160178] Sanofi: Expiry notification to be
sent to Contract owners before 180, 90 and
176544.1 30 days
Pre-requisite :
 
1. Contract type precondition :
176544.2 1. Contract
request should be present in
176544.3 the system with approved state.
2. Rules precondition :
NA 
176544.4 3. User precondition &
privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
176544.5 manage privileges on Agreements
Tile
- Contract Manager should have
Manage privilege on ICM
- Contract
Manager should have manage
privileges on Agreements Tile
 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage privileges on Agreements
Tile
- Contract Manager should have
176544.6 Manage privilege on ICM
- Contract
Manager should have manage
privileges on Agreements Tile
176544.7  
4. Others if any
-A notification subscription should
exist for the contract type
176544.8 (MSA) which gets generated
before 180 and 90 days of agreement
expiration .
A notification subscription should
176544.9 exist for the other contract
type/agreement which gets
176544.1 generated before 90 and 30
176544.11 days of agreement expiration .
[170222] Sanofi: Enable File Selection On Pre-requisite :
Template Page  
1. Contract type precondition :
1. Contratc
176582.1 Request agreement type
should exists in the system
176582.2 2. Contract Request - A should be
present in the system with approved
state.
2. Rules precondition :
NA 
3. User precondition &
176582.3 privileges :
- Purchase Partner should have
Manage privileges on ICM
- Purchase Partner should have
176582.4 manage privileges on Agreements
Tile
- Contract Manager should have
176582.5 Manage privileges on ICM
- Contract
176582.6 Manager should have manage
privileges on Agreements Tile
 
176582.7 4. Others if any
[158708] Sanofi: Vendor Lookup search
window to display specific columns

176586.1

176586.2

176586.3
 176586.4

176586.5

176586.6

176586.7

176586.8

176586.9
176586.1
176586.11

176586.12

176586.13

176586.14
Pre-requisite :
 
1. Contract type precondition :
1. Contratc
176586.15 Request agreement type
should exists in the system
 
2. Rules precondition :
NA 
3. User precondition &
176586.16 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
176586.17 manage privileges on Agreements
Tile
- Contract Manager should have
Manage privilege on ICM
- Contract
Manager should have manage
privileges on Agreements Tile
 
4. Others if any
 privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage privileges on Agreements
Tile
- Contract Manager should have
Manage privilege on ICM
176586.18 - Contract
Manager should have manage
privileges on Agreements Tile
176586.19  
176586.2 4. Others if any
[160174] Sanofi: Last signed date to get
updated post execution of Contract

176621.1 Pre-requisite :
 
176621.2 1. Contract type precondition :
1. Contratc
Request agreement type
should exists in the system
2. Contract Request - A should be
present in the system with approved
176621.3 state.
2. Rules precondition :
NA 
3. User precondition &
176621.4 privileges :
- Purchase Partner should have
Manage privileges on ICM
- Purchase Partner should have
manage privileges on Agreements
176621.5 Tile
- Contract Manager should have
Manage privileges on ICM
- Contract
Manager should have manage
privileges on Agreements Tile
176621.6  
176621.7 4. Others if any
[160296] Sanofi: ICM integration with eBuy
for transferring contract information

176725.1

176725.2

176725.3

176725.4

Pre-requisite :
 
176725.5 Pre-requisite :
 
1. Contract type precondition :
1. Contratc
Request agreement type
should exists in the system
2. Contract Request - A should be
present in the system with approved
state.
2. Rules precondition :
NA 
176725.6
3. User precondition &
privileges :
- Purchase Partner should have
Manage privilege on ICM
- Purchase Partner should have
manage previleges on Agreements
Tile
- Contract Manager should have
Manage privilege on ICM
- Contract
176725.7 Manager should have manage
privileges on Agreements Tile
176725.8  
176725.9 4. Others if any
[172978] Sanofi : Outbound ICM
integration with eBuy – For Expired and
Terminated Contracts Daily Scheduled Task

176741.1

176741.2

176741.3

176741.4

Pre-requisite :
 
1. Contract type precondition :
1. Contratc
176741.5
Pre-requisite :
 
1. Contract type precondition :
1. Contratc
Request agreement type
should exists in the system
2. Contract Request - A should be
present in the system with approved
state.
176741.6 2. Rules precondition :
NA 
3. User precondition &
privileges :
- Purchase Partner should have
Manage privileges on ICM
- Purchase Partner should have
manage privileges on Agreements
Tile
- Contract Manager should have
Manage privileges on ICM
176741.7 - Contract
176741.8 Manager should have manage
privileges on Agreements Tile
176741.9  
176741.1 4. Others if any
1. Contratc
[171720] [Sanofi]: Rename Default Request agreement type
Contract Category & Request Category as should exists in the system
176816.1 "Please Select"
2. Rules precondition :
NA 
3. User precondition &
privileges :
- Purchase Partner should have
176816.2 Manage privileges on ICM
- Purchase Partner should have
manage privileges on Agreements
Tile
176816.3  
176816.4 4. Others if any
present in the system with approved
[173767] Sanofi: Hide "Create and Send for state.
Approval" Button 2. Rules precondition :
NA 
3. User precondition &
176839.1 privileges :
- Purchase Partner should have
Manage privilege on ICM
176839.2 - Purchase Partner should have
 - Purchase Partner should have
manage previleges on Agreements
Tile
- Contract Manager should have
Manage privilege on ICM
176839.3 - Contract
Manager should have manage
previleges on Agreements Tile
 
176839.4 4.
1. Others
Contractif type
any precondition :
[158735] Sanofi: [On Hold] Agreement 1. Contratc
code from MSA to be copied to Work Order Request agreement type
contracts should exists in the system
2. Contract Request - A should be
176927.1 present in the system with approved
state.
3. MSA Agreement B Should present
176927.2 in the system in executed state.
2. Rules precondition :
NA 
3. User precondition &
privileges :
176927.3 - Purchase Partner should have
Manage privileges on ICM
176927.4 - Purchase Partner should have
manage previleges on Agreements
Tile
- Contract Manager should have
Manage privileges on ICM
- Contract
176927.5 Manager should have manage
privileges on Agreements Tile
176927.6  
176927.7 4. Others if any
[163228] Sanofi: Custom Report: Cycle
Time report
176967.1

176967.2
Pre-requisite :
 
1. Contract type precondition :
 
2. Rules precondition :
NA 
3. User precondition &
privileges :
- Contract
Manger should have Manage
privileges on ICM
- Purchase Partner should have
Manage privileges on ICM
- Contract
Manger should have Manage
privileges on Reports tile
- Purchase Partner should have
Manage privileges on Reports tile
176967.3  
176967.4 4. Others if any
 1. Contract type precondition :
[172411] Sanofi: SSO setup to be done in  
UAT/PROD systems in C6 2. Rules precondition :
NA 
176991.1 3. User precondition &
privileges :
- Contract
176991.2 Manger should have Manage
privileges on ICM
176991.3 - Purchase Partner should have
Manage privileges on ICM
176991.4  
176991.5 4. Others if any
[171721] [Sanofi]: Sanofi Entity & Leading
Cost center Selection Pop Up Screen
177036.1 columns to be fixed.

177036.2

177036.3

177036.4

177036.5

177036.6

177036.7

177036.8

Pre-requisite :
 
 Pre-requisite :
 
1. Contract type precondition :
1. Contratc
Request agreement type
should exists in the system
2. Rules precondition :
177036.9 NA 
3. User precondition &
privileges :
- Purchase Partner should have
Manage privileges on ICM
- Purchase Partner should have
manage privileges on Agreements
Tile
177036.1  
177036.11 4. Others if any
[162555] Sanofi [HOLD]: Amendments to
contract, to have an unique number
sequence in Agreement code
Pre-requisite :
177114.1  
1. Contract type precondition :
1. Contratc
177114.2 Request agreement type
should exists in the system
2. Contract Request - A should be
present in the system with approved
state.
177114.3 2. Rules precondition :
NA 
3. User precondition &
privileges :
177114.4 - Purchase Partner should have
Manage privileges on ICM
177114.5 - Purchase Partner should have
manage privileges on Agreements
Tile
- Contract Manager should have
Manage privileges on ICM
- Contract
177114.6 Manager should have manage
privileges on Agreements Tile
 
177114.7 4. Others if any
[163234] Sanofi: Raw data dump required
for Request and Contract transactional data
177116.1 Pre-requisite :
 
1. Contract type precondition :
177116.2 NA
2. Rules precondition :
NA 
3. User precondition &
privileges :
NA 
4. Others if any
 
User should have access on ICM SFTP
location
 [163234] Sanofi: Raw data dump required
for Request and Contract transactional data
Pre-requisite :
 
1. Contract type precondition :
NA
2. Rules precondition :
NA 
3. User precondition &
privileges :
NA 
4. Others if any
 
User should have access on ICM SFTP
177116.3 location
[164096] Sanofi: Supplier portal setup to be Pre-requisite :
done on B2C  
1. Contract type precondition :
1. Contratc
177202.1 Request agreement type
should exists in the system
2. Contract Request - A should be
177202.2 present in the system with approved
state.
2. Rules precondition :
NA 
3. User precondition &
177202.3 privileges :
- Purchase Partner should have
Manage privilege on ICM
177202.4 - Purchase Partner should have
manage previleges on Agreements
Tile
- Contract Manager should have
177202.5 Manage privilege on ICM
- Contract
Manager should have manage
177202.6 previleges on Agreements Tile
- One or more supplier records (in
ICM - external with login previleges)
should be present in ICM and same
records should be added in Azure AD
 
4. Others if any
- Supplier portal should be present to
177202.7 access agreement for supplier
183729.1 [173767] Verify if 'Create and Send for
approval button' is hidden from agreement
creation.
183729.2

183729.3

183729.4

183729.5
260147.1 [Sanofi][June-2018][PBI-253439]: Verify if
Search section have default selection as
'Contract Request'
260147.2
 [Sanofi][June-2018][PBI-253439]: Verify if
Search section have default selection as
'Contract Request'

260147.3

260147.4
260159.1 [Sanofi][June-2018][253439]: Verify if user
can select other available entity than
'Agreement', 'Contract Request' and
260159.2 'Associated Documents'.

260159.3

260159.4

260159.5
260159.6
260306.1 [Sanofi][237755]: Verify the integration for
Vendor master.
260306.2

260306.3
264003.1 [Sanofi]:Default columns when dding MSA
to WO
264003.2
264003.3

264003.4
264003.5
Action

Login to ICM application as Purchase Partner

Click on Agreement Tile

Click on 'Create Request' tile

Click on 'Create agreement' tile

Login to ICM application as Purchase Partner

Click on agreement tile and navigate to create request page

Select category and request type as 'Buy Side' and click next

1. Fill all required details_x000D_

2. Set value for 'Is this an existing vendor' as : NO_x000D_
3. Put vendor details manually._x000D_
4. Submit and approve the request

1. Login as Contract Manager_x000D_

2. Click on agreement management tile and navigate to
Requests page_x000D_
3. Select previously created Contract Request and view the
request.

1. Click on edit button, change the value of 'Contract policy

type' to simple/complex._x000D_
2. Keep value for 'Is this an existing vendor' as : NO_x000D_
3. Go to verification page and update the request.

Click on submit button to approve the request.

Open the above request and click on Create contract button.

Enter data into all the mandatory field.
Check vendor name and vendor address.
Click on next button.

Click create button.Click on publish button.

Now click on send for approval button.

ClickLogin by CM and click on approve button.

Change the vendor details or make the temp vendor as a

registered vendor. Make the temp vendor as registered
vendor by saving data into the SAP.

Approve agreement by CM.

Login to the ICM application as Purchase Partner

Click on agreement management tile

Click on Create Request tile

From 'Category' and request type dropdown select value : Buy

Side

Hit Next button

Fill all required fields and hit next button
Click on Create Request button
Click on Submit Button

Click on + icon of Supporting document

1. Now login with valid CM_x000D_

2. Click on agreement management tile _x000D_
3. Click on request tile and search for above created request.
Open appropriate Contract Request and click on create
contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Type of Paper anyClick on Next

1. Fill required data_x000D_

2. Select appropriate template and click on next_x000D_
3. Click on create and publish

Click on + icon of Supporting document

Login to the application by valid user [CM of the pre-

requisities request].

Verify that the User is able to Search for the above created
Contract request [Pre-requisities]from contract request Index
page/ main Search page.

Verify that on click on view record button.

Click on create contract button.

Select the category, contract type and type of paper. [Select

MSA contract type] Click on next button.
Enter other mandatory data and create the agreement.

1. Set Expiry Date after 180 days from today's date_x000D_

2. Select appropriate template and hit next_x000D_
3. Click on create, publish and execute the agreement

Repeat steps 1-6 and set expiry date after 90 days from
today's date._x000D_
[Select contract type MSA or other contract type]

Repeat steps 1-6 and set expiry date after 30 days from
today's date_x000D_
[Select contract type other than MSA ]

1. Login with valid CM user_x000D_

2. Click on agreement management tile _x000D_
3. Click on request tile

Open Contract Request A and click on create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Type of Paper:OwnClick on Next

Fill all required details and click on next button

Click on select file button and upload one file instead of
template.
Click on next button and create agreement._x000D_
Publish agreement.

Download and check the agreement document.

Login to the ICM application as Purchase Partner

Click on agreement management tile

Click on Create Request tile

From 'Category' dropdown select value : Buy Side

Click on Next button.

Now check for 'Is this for an existing vendor?'

attribute._x000D_
Select yes from the dropdown value._x000D_

Click on search icon to select vendor from the lookup search

pop-up.

Verify that user can search vendor by using vendor name.

Select one vendor from the lookup search and add the
vendor.
Fill all required fields and hit next button
Hit Create Request button

Hit Submit Button

1. Now login with valid CM_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile
Open appropriate Contract Request and hit create contract
button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Paper Type anyHit Next

Now check for 'Is this for an existing vendor?'

attribute._x000D_
Select yes from the dropdown value._x000D_

Click on search icon to select vendor from the lookup search

pop-up.
Verify that user can search vendor by using vendor name.
Select one vendor from the lookup search and add the
vendor.
Fill all required fields and hit next button

1. Login with valid CM user_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile

Open Contract Request A and hit create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Paper Type anyHit Next

1. Fill required data and set Electronic Signature_x000D_

2. Select appropriate template and hit next_x000D_
3. Click on create, publish and approve the contract

1. send the agreement for external signatory and get it

signed_x000D_
2. Send the agreement for interna signatory and get it signed

Repeat steps 1-5 with Signature as Manual Signature

1. Login with valid CM user_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile

Open Contract Request A and hit create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Paper Type anyHit Next

1. Fill required data_x000D_

2. Select appropriate template and hit next_x000D_
3. Click on create, publish and approve the contract
1. send the agreement for external signatory and get it
signed_x000D_
2. Send the agreement for internal signatory and get it signed

Create an amendment of newly created agreement and

execute it. _x000D_
Expiration date as today's date

1. On the next day _x000D_

OR_x000D_
1. Expire the agreement with developer's help on the same
day

1. Login with valid CM user_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile

Open Contract Request A and hit create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Paper Type anyHit Next

1. Fill required data and set Expiration date as today's

date_x000D_
2. Select appropriate template and hit next_x000D_
3. Click on create, publish and approve the contract
1. send the agreement for external signatory and get it
signed_x000D_
2. Send the agreement for internal signatory and get it signed

Create an amendment of newly created agreement and

execute it. _x000D_
Expiration date as today's date

1. On the next day _x000D_

OR_x000D_
1. Expire the agreement with developer's help on the same
day

Login to ICM application as Purchase Partner

Click on Agreement Tile

Click on 'Create Request' tile

1. Login with valid CM user_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile

Open Contract Request A and hit create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Paper Type anyHit Next

1. Fill required data_x000D_

2. Select appropriate template and hit next

1. Login with valid CM user_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile

Open Contract Request A and hit create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Work Order_x000D_
3. Paper Type anyHit Next
Inherit MSA - B (As mentioned in pre-requisite)

1. Fill required data._x000D_

2. Select appropriate template and hit next_x000D_
3. Click on create, publish and approve the contract

Login as valid user to ICM application

Click on reports tile

Click on Cycle time report

Login to ICM application as Purchase Partner

Click on login as link and try to login with different user

Click on logoff link

Repeat steps 1-3 with Contract Manager Login

Login to ICM application as Purchase Partner

Click on agreement tile and navigate to create request page

Selct catrgory as 'Buy Side' and click next

Click on Search icon (magnifying glass icon) of Sanofi Entity

Click on Search icon (magnifying glass icon) of Leading Cost

Centre

Create and submit the Contract request

1. Now login with CM user_x000D_

2. Navigate to Request page_x000D_
3. Click on request created in previous step_x000D_
4. Click on create contract button

1. Select Category : BuySide_x000D_

2. Select Contract Type : Any_x000D_
3. Select Type of paper : Any_x000D_
Click Next
Click on Search icon (magnifying glass icon) of Sanofi Entity

Click on Search icon (magnifying glass icon) of Leading Cost

Centre

1. Login with valid CM user_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile

Open Contract Request A and hit create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Paper Type anyHit Next

1. Fill required data_x000D_

2. Select appropriate template and hit next_x000D_
3. Complete the signatory flow
Click on add amendment button

Fill all required data and publish the amendment

Add one more amendment to the agreement

Open SFTP Application say (FileZilla) and login to the
application as valid user
Navigate to specified location where raw data dump file is to
be placed.
Open the file

1. Login with valid CM user_x000D_

2. Click on agreement tile _x000D_
3. Click on request tile

Open Contract Request A and hit create contract button

Select :_x000D_
1. Category as : Buy Side_x000D_
2. Contract Type Name : Any_x000D_
3. Paper Type anyHit Next
1. Fill required data_x000D_
2. Select appropriate template and hit next

Click on create and publishbutton

1. Click on collabrate button_x000D_
2. Select required supplier

1. Now, open supplier portal_x000D_

2. Login with valid supplier
Log in to ICM with valid credentials.
Navigate to Agreement management tile and Click on Create
agreement tile.

Fill up all the details. click on next.

Observe buttons availabel on verify page.

Repeate same steps for Amendments also.

Log in to ICM Sanofi with valid credentials.

Click on Advanced Search option present on top right Section.

Observe the By default value for Entity.

Try above scenario by navigating from different ICM section

such as Request, Master data, Clouses, Templates.
Log in to ICM Sanofi with valid credentials.

Click on Advanced Search option present on top right Section.

Observe the By default value for Entity.

Change the default value by entering any other entity from
drop down available.

Try above scenario by navigating from different ICM section

such as Request, Master data, Clouses, Templates.

Log in to SFTP server using Valid credentials.

Put the CSV file under desired folder. run the task.
check the results on UI. While checking verify that Vendor
name and Vendor ID.
Log in to ICM with valid credentials.
Navigate to Create agreement >> Select WO
Select MSA to Associate to the WO.

Observe the Columns available on MSA selection POP up.

Try to Add some extra column in it.
Expected Result Pass/Fail Bug ID

System should allow user to login to the system successfully.

1. User should navigate to agreement management page

successfully_x000D_
2. Requests and Create Request tiles should be visible to the
user

1. User should navigate to Create Request page_x000D_

2. On Create request page - Default Category should be : Buy
Side

1. User should navigate to Create agreement page_x000D_

2. On Create agreement page - Default Category should be :
Buy Side _x000D_
3. The next category in the drop down list should be
"CDA_NDA"
System should allow user to login to the application
successfully.
User should navigate to create contract request page
successfully

User should navigate to attribute page of Contract Request

1. Notification should be sent to appropriate Contract

Manager_x000D_
2. Buttons [edit, delete etc] should not be displayed on
Request details page for Purchasing partner after request
submit.

1. User should navigate to Request Details page

successfully._x000D_
2. Edit button should be displayed on the page for Contract
manager.

1. Contract request should remain in draft status.

1. A request should get approved._x000D_

2. User should be able to approve the request if the vendor is
Temp Vendor or if the Vendor does not exists in ICM.

Contract/agreement creation page should be display.

Entered data should be display.
Temporary details of the vendor should be display.
a. System should navigate to summary page. B. All the
metadata information should be displayed correctly in
summary page. C. All the contract types which satisfies the
contract type selection rule should be display.

a. System should create contract. b. A contract status should

become 'Draft'. c. Verify the information displayed in details
tab. d. A notification should get created after contract
creation. e. Contract creation history should get created.

Agreement goes to the approval to the contract manager, as

temp vendor exist into the agreement._x000D_
"An agreement status should be 'Waiting for approval from
user ( multiple approvers)'_x000D_
A notification and history should get generated.
On click on approve button a validation messgae should be
display to register the temp vendor.

Temp vendor should get registered and SAP vendor number

should get generate to the temp vendor.

Agreement approval should pending from other approval (in

case more approvers are present) approvers._x000D_

1. System should allow Purchase Partner to login to the

application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned

category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

User should naviagte to attribute page of Contract Request

User should navigate to confirmation page.
Contract Request should get created in draft state
1. Contract request should move to approved state_x000D_
2. Appropriate CM should get added to the team_x000D_
3. User should be able to add assocoations from - Supporting
Documents

1. User should navigate to assoicated document page_x000D_

2. User should not see below attributes on assoication :
_x000D_
- Agreement Code_x000D_
- Business Status_x000D_
- Name

1. CM should navigate to contract request page

successfully._x000D_
2. Previously created contract request should be displayed in
approved state.

User should navigate to contract creation page.

User should navigate to attribute page of Agreement Contract

Type

1. User should navigate to agreement details page_x000D_

2. User should be able to add association under Supporting
Documents_x000D_
3. Count of associations added while creating Contract
Requests should be displayed

1. User should navigate to assoicated document page_x000D_

2. User should not see below attributes : _x000D_
- Agreement Code_x000D_
- Business Status_x000D_
- Name

User should be logged in successfully.

1. Contract request should be displayed in the Search results.

2. Columns should reflect the contract request data.
On click on view record button contract request details should
be display.
Agreement creation page should be display with category,
contract type and type of paper attribute.

All the selected data should be display on contract type page.

Attribute page should display inherited data from contract
request for which data is entered during request creation.
An agreement should get created. An agreement code should
also get created and it should be unique.

System should send Contract Expiry notification to all team

members befor 180 days (for 180 days)

System should send Contract Expiry notification to all team

members (for 90 days)

System should send Contract Expiry notification to all team

members (for 30 days)

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract creation page

User should navigate to attribute page of Agreement Contract

Type

1. User should navigate to template selection page_x000D_

2. Upload template section with Selct File button should be
displayed on template selection page

Selected file should get uploaded successfully.

Agreement should get created and published .

Uploaded file data and downloaded file data should be same.

1. System should allow Purchase Partner to login to the

application successfully._x000D_
2. Agreement tile should be visible to the Purchase Partner .

1. Purchase Partner should navigate to Agreement

Management page_x000D_
2. Create request tile should be visible to Purchase Partner

Purchase Partner should navigate to Create request page

1. Purchase Partner should be able to select mentioned
category successfully._x000D_
2. Once user selects category as Buy side, request type should
be displayed as 'Buy Side'

1. User should naviagte to attribute page of Contract

Request_x000D_
_x000D_

On click on yes , vendor related all the lookup-cascade

attributes should be display._x000D_
Vendor name should have search icon.

1. The popup search window should display columns as :

Vendor Name, Vendor ID, Vendor Address 1 and City with
search functionality.

Under vendor information section user should be able to

search and select vendor based on the Vendor name.
All the vendor related data should be display in all the
attributes.
User should navigate to confirmation page.
Contract Request should get created in draft state

1. Agreement should move to approved state_x000D_

2. Appropriate CM should get added to the team_x000D_
3. User should be able to add assocoations from - Supporting
Documents

1. CM should navigate to contract request page

successfully._x000D_
2. Previously created contract request should be displayed in
approved state.

User should navigate to contract creation page

1. User should navigate to attribute page of Agreement

Contract Type_x000D_

On click on yes , vendor related all the lookup-cascade

attributes should be display._x000D_
Vendor name should have search icon.

1. The popup search window should display columns as :

Vendor Name, Vendor ID, Vendor Address 1 and City with
search functionality.
 Under vendor information section user should be able to
search and select vendor based on the Vendor name.
All the vendor related data should be display in all the
attributes.
User should navigate to verify page.

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract createion page

User should navigate to attribute page of Agreement Contract

Type

Contract should be displayed in approved state

1. Agreement should go in executed state_x000D_

2. The date on which contract got executed, that date should
get stored in 'Last signed date' attribute

1. Agreement should go in executed state._x000D_

2. In case of Manual signature, post upload of contract
document or at the time of upload, provide a pop-up message
to the user to update the Last Signed date.

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract createion page

User should navigate to attribute page of Agreement Contract

Type

Contract should be displayed in approved state

Once agreement is executed following data needs to be
transferred from Icertis e-Contract application to eBuy : -
Contract ID/code ICMAgreementCode - Contract Name Name
- Vendor ID ICMVendorID - Vendor Name ICMVendorName-
HACAT number ICMSpendCategory Amount
ICMContractValue Currency Currency_ICMContractValue

1. Agreement should go in executed state_x000D_

2. Once agreement is executed following data needs to be
transferred from Icertis e-Contract application to eBuy : -
Contract ID/code ICMAgreementCode - Contract Name Name
- Vendor ID ICMVendorID - Vendor Name ICMVendorName-
HACAT number ICMSpendCategory - Amount
ICMContractValue - Currency Currency_ICMContractValue

ICM e-Contract system should send below details to ebay

system collectively for all expired agreements and
amendments :- Contract ID/code ICMAgreementCode -
Contract Name Name - Vendor ID ICMVendorID - Vendor
Name ICMVendorName- HACAT number ICMSpendCategory -
Amount ICMContractValue - Currency
Currency_ICMContractValue

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract createion page

User should navigate to attribute page of Agreement Contract

Type

Contract should be displayed in approved state

Once amendment is executed following data needs to be
transferred from Icertis e-Contract application to eBuy : -
Contract ID/code ICMAgreementCode - Contract Name Name
- Vendor ID ICMVendorID - Vendor Name ICMVendorName-
HACAT number ICMSpendCategory Amount
ICMContractValue Currency Currency_ICMContractValue

1. Agreement should go in executed state_x000D_

2. Once agreement is executed following data needs to be
transferred from Icertis e-Contract application to eBuy : -
Contract ID/code ICMAgreementCode - Contract Name Name
- Vendor ID ICMVendorID - Vendor Name ICMVendorName-
HACAT number ICMSpendCategory - Amount
ICMContractValue - Currency Currency_ICMContractValue

ICM e-Contract system should send below details to ebay

system collectively for all expired agreements and
amendments :- Contract ID/code ICMAgreementCode -
Contract Name Name - Vendor ID ICMVendorID - Vendor
Name ICMVendorName- HACAT number ICMSpendCategory -
Amount ICMContractValue - Currency
Currency_ICMContractValue

System should allow user to login to the system successfully.

1. User should navigate to agreement management page

successfully_x000D_
2. Requests and Create Request tiles should be visible to the
user

1. User should navigate to Create Request page_x000D_

2. On Create request page - First value of the category
dropdown should be displayed as : Please Select

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract createion page

User should navigate to attribute page of Agreement Contract
Type

1. User should navigate to verify page_x000D_

2. 'Create and Send For Approval' should not be displayed on
the page (Please refer screenshot)

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract createion page

User should navigate to attribute page of Agreement Contract

Type
User should be able to inherit MSA successfully.

1. Contract should be displayed in approved state_x000D_

2. MSA Agreement number should be displayed under
ICMMSANumber attribute. This number will not be viewable
on the page .(Verify it in developer tool / view source)

1. System should allow user to login to the application

successfully.
Under Custom Reports section : Cycle Time Report should be
displayed

1. Cycle time report shold get opened in new tab_x000D_

2. Report Should display following details :_x000D_
- Request Status_x000D_
- Report needs to capture the time spent by per user profile
(Agreement)_x000D_
- Reort should capture spent time, per profile, contract type
(complex & simple), process step & procurement
category (HACAT) from request initialization to contract
storage through following steps: Request initialization ;
Request submission ; Request assessment ; Contract
elaboration & approval (with a detailed information on
time spent per profile per elaboration activity) ; Contract
signature & storage ;
1. SSO login should be available for the user_x000D_
2. User should be able to login to the application successfully.

User should be able to use 'login as' functionality successfully.

User should be able to logoff from ICM application
successfully.

System should allow user to login to the application

successfully.

User should navigate to create contract page successfully

1. User should navigate to attribute page of Contract

Request_x000D_
2. 'Sanofi Entity' and 'Leading Cost Centre' attributes should
be displayed on the page

1. New pop-up window should get opened_x000D_

2. Below column sequence should be displayed
:ICMSanofiEntityCode ICMSanofiEntity
ICMSanofiEntityAddress1 ICMSanofiEntityCity
ICMSanofiEntityState ICMSanofiEntityZipCode
ICMSanofiEntityCountry ICMSanofiEntityRegistrationNumber
ICMSanofiEntityRegistrationLocation
ICMSanofiEntityLegalForm ICMSanofiEntityCapital1
ICMGoverningLaw

1. New pop-up window should get opened_x000D_

2. Below column sequence should be displayed
:ICMLeadingCostCenter ICMCompanyCode ICMCostCenter
ICMCostCenterName ICMManagementCenter
ICMDepartment ICMControllerGroup
1. Request should go in Approved state_x000D_
2. Notification should go to appropriate CM

User should navigate to Create Agreement Page

1. User should Navigate to Attribute page of agreement

_x000D_
2. 'Sanofi Entity' and 'Leading Cost Centre' attributes should
be displayed on the page
1. New pop-up window should get opened_x000D_
2. Below column sequence should be displayed
:ICMSanofiEntityCode ICMSanofiEntity
ICMSanofiEntityAddress1 ICMSanofiEntityCity
ICMSanofiEntityState ICMSanofiEntityZipCode
ICMSanofiEntityCountry ICMSanofiEntityRegistrationNumber
ICMSanofiEntityRegistrationLocation
ICMSanofiEntityLegalForm ICMSanofiEntityCapital1
ICMGoverningLaw

1. New pop-up window should get opened_x000D_

2. Below column sequence should be displayed
:ICMLeadingCostCenter ICMCompanyCode ICMCostCenter
ICMCostCenterName ICMManagementCenter
ICMDepartment ICMControllerGroup

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract createion page

User should navigate to attribute page of Agreement Contract

Type

1. Agreement should go in executed state._x000D_

2. Add amendment button should be displayed
User should navigate to attribute page of amendment

1. Amendment should get published and draft status should

be displayed_x000D_
2. Amendment should get same code as Agreement code
ending with '_V1'_x000D_
eg. MSA_2017_001_V1
Amendment number/code sequence should be incremental
number. e.g MSA_2017_001_V2

User should login to the system successfully.

Raw data dump file sould be placed at this location on weekly
basis
File format should be :_x000D_
1. All contract types will be listed in one column_x000D_
2. The trailing end columns will be contract type specific
attributes (e.g. template specific)_x000D_
3. Header column labels which are specific to contract type
need to have a prefix of contract type name_x000D_
eg. SSA, MSA, CDA, WO

1. CM should navigate to contract request page

successfully._x000D_
2. Contract request A (mentioned in pre-requisite) should be
displayed in approved state.

User should navigate to contract createion page

User should navigate to attribute page of Agreement Contract

Type

1. User should navigate to verify page

1. Agreement should get published successfully_x000D_

2. User should navigate to agreement details page_x000D_
3. Collabrate button should be displayed on the page
1. Supliers list added in ICM and Azure AD should be displayed
in popup window for the selection

1. Supplier should be able to user supplier portal

successfully_x000D_
2. Supplier should be able to login to ICM successfully from
supplier portal_x000D_
3. Supplier should be able to download and upload agreement
tuccessfully
User should get successfully logged in.
Agreement creation wizard should get open showing all the
attributes defined for Contract.

User should get navigated to Template selection page in case

of own paper type. else user should get navigated to Verify
page.

Create and send for approval' button should not be present

on the verify page. only 'Create' 'Create and Publish' 'Previous'
and 'Discard' buttons should be available.
For amendments also 'Create and Send for approval' button
should be hidden.
User should get successfully logged in.

User should get successfully navigated to Search Section.

By default selection for entity should be 'Contract Request',
'Agreements' and 'Associated Document'

Whenever user get navigated to Search page, be default

selection should be 'Agreement', 'Contract request' and
'Associated Document'.
User should get successfully logged in.

User should get successfully navigated to Search Section.

By default selection for entity should be 'Contract Request',
'Agreements' and 'Associated Document'
User should be able to Select other entities and Search result
should be present.

Whenever user get navigated to Search page, be default

selection should be 'Agreement', 'Contract request' and
'Associated Document'.

User should get successfully logged in.

User should be successfully placed the file.
After successfully upload of File, Vendor name and ID should
get concatinated single column.
User should get successfully logged in.
User should be able to create the WO agreement.
User should be ablt to Selecvt the MSA
Columns names should be as per the Requirement with valid
values in it.
user should be able to add or remove extra column
Comments
Test Case Title Summary
[Sanofi][Wave1][310803]: Verify if user
form 'Other group' is able to create/ Edit
Contract request.

[Sanofi][Wave1]: Verify reprots for

Agreement Approver.

[Sanofi][Wave1]: Verify if Local users only

can reset the Expiry date of agreement.

[Sanofi][Wave1]: Verify if user is not able to

delegate the agreement to outside user
group.
[Sanofi][Wave1]: Verify Multi-Party
Contract.

[Sanofi][Wave1]: Verify if 'Add External

User' button is removed from all user fields.

[Sanofi][Wave1]: Verify reprots for

Agreement Sanofi Signatory.

[Sanofi][Wave1]: Verify reprots for

Agreement illegitimate Primary and
Secondary owner
[Sanofi][Wave1]: Verify reprots for
Agreement illegitimate Primary and
Secondary owner

[Sanofi][Wave1]: Verify if user is able to

drag and drop E sign tags
Action
Log in to ICM with User form 'Other' user group.

Navigate to Agreement management tile >> Click on

Create Request tile

Select Buy side request. Click on Next

Click on 'Create Request' button.

Verify if newly created Request is present in the request Grid.

Also check for all other request availabel on the grid
Open newly created request and Click on edit the contract
request.
Log in to ICM with User form 'Other' user group.

Navigate to Request tile >> Navigate to Contract

Approver Report tile
Log in to ICM with User form 'Other' user group.

Navigate to Agreement management tile >> Click on

Create Request tile

Select Buy side request. Click on Next

Click on 'Create Request' button.

Verify if newly created Request is present in the request Grid.

Also check for all other request availabel on the grid
Open newly created request and Click on edit the contract
request.
Log in to ICM with User form 'Other' user group.

Navigate to Agreement management tile >> Click on

Create Request tile

Select Buy side request. Click on Next

Click on 'Create Request' button.

Verify if newly created Request is present in the request Grid.

Also check for all other request availabel on the grid
Open newly created request and Click on edit the contract
request.
Log in to ICM with User form 'Other' user group.

Navigate to Agreement management tile >> Click on

Create Request tile

Select Buy side request. Click on Next

Click on 'Create Request' button.

Verify if newly created Request is present in the request Grid.

Also check for all other request availabel on the grid
Open newly created request and Click on edit the contract
request.
Log in to ICM with Valid user.

Navigate to Agreement management tile >> Click on

Create Request tile

Select Buy side request. Click on Next

Click on 'Create Request' button.

On User fields, Click on Add suer to enter, Requestor, Finance
approver, orLegal Approver,
Verify this for Request as well as Agreement.
Log in to ICM with User form 'Other' user group.

Navigate to Request tile >> Navigate to Contract

Approver Report tile
Log in to ICM with User form 'Other' user group.
Navigate to Request tile >> Navigate to Contract
Approver Report tile
Log in to ICM with CM user.

Create agreement >> Set Adobe tags attribute to yes.

Once Approved, Click on Send for External Signature.

Expected Result Pass/Fail Bug ID
User should be able to log in to ICM.

User should be able to See 'Agreement Management' tile. And

Whwn clicked on 'Create Request tile'; Request Selection page
should appear.

user should land on the Request Attribute page. User should

be able to fill up all the available attributes with valid values.
User should get navigated to Verify page.

The request should get created. All the attributes should be

available with values entered. User should get navigated to
Grid page

Request created by logged in user should be visible to the

user.
User should be able to Edit request.Change some values and
click on Update.
User should be able to log in to ICM.

User should be able to see the reprot listed._x000D_

On clicking the report, the filters should appear with
user/User group selection.
User should be able to log in to ICM.

User should be able to See 'Agreement Management' tile. And

Whwn clicked on 'Create Request tile'; Request Selection page
should appear.

user should land on the Request Attribute page. User should

be able to fill up all the available attributes with valid values.
User should get navigated to Verify page.

The request should get created. All the attributes should be

available with values entered. User should get navigated to
Grid page

Request created by logged in user should be visible to the

user.
User should be able to Edit request.Change some values and
click on Update.
User should be able to log in to ICM.

User should be able to See 'Agreement Management' tile. And

Whwn clicked on 'Create Request tile'; Request Selection page
should appear.

user should land on the Request Attribute page. User should

be able to fill up all the available attributes with valid values.
User should get navigated to Verify page.
The request should get created. All the attributes should be
available with values entered. User should get navigated to
Grid page

Request created by logged in user should be visible to the

user.
User should be able to Edit request.Change some values and
click on Update.
User should be able to log in to ICM.

User should be able to See 'Agreement Management' tile. And

Whwn clicked on 'Create Request tile'; Request Selection page
should appear.

user should land on the Request Attribute page. User should

be able to fill up all the available attributes with valid values.
User should get navigated to Verify page.

The request should get created. All the attributes should be

available with values entered. User should get navigated to
Grid page

Request created by logged in user should be visible to the

user.
User should be able to Edit request.Change some values and
click on Update.
User should be able to log in to ICM.

User should be able to See 'Agreement Management' tile. And

Whwn clicked on 'Create Request tile'; Request Selection page
should appear.

user should land on the Request Attribute page. User should

be able to fill up all the available attributes with valid values.
User should get navigated to Verify page.

The request should get created. All the attributes should be

available with values entered. User should get navigated to
Grid page
On the user selection pop up, 'Add external user' button
should not be available.
In any case, the button should be available.
User should be able to log in to ICM.

User should be able to see the reprot listed._x000D_

On clicking the report, the filters should appear with
user/User group selection.
User should be able to log in to ICM.
User should be able to see the reprot listed._x000D_
On clicking the report, the filters should appear with
user/User group selection.
User should get successfully logged in.

User should be able to fill up all the details and Continue the
agreement floe till Status become Approved.

Pop Should open the agreement document with all the

signature attributes in it. _x000D_
It should allow user to place the signature attributes.
Comments