ICV Implementation in Region ERP- Status update
March 2011 & Plan for Go-Live
REMSC, 2011
© ABB Group
ICV Implementation-REMSC countries
 Recap of the activities for ICV implementation as of Mar-2011
 Further activities to be completed for Go-Live
 Points raised by countries so far and clarifications/ explanations
 ICV Transactions for business users
 Country Mappings Dashboard (summary of mappings done so far by countries in terms of profit
center, customers and vendors)
 Long term approach for ICV- elimination of duplicates and have ICV ID as Local ID
 ICV further developments awaited:
 Online connectivity with MDM server to get updated ICV details without the need to upload
in the local ERP
 Partner function enhancement (MDM database to have the functionality to hold multiple
addresses (Sold to, Ship to) etc., for the same ICV ID
 ICV data in the interfaces (OMS/ BOL/ B2B etc.,)
© ABB, SREMSC
April 8, 2015 | Slide 2
Recap of the activities for ICV implementation as of Mar-2011
ICV implementation activity description
Date
Mail communication sent to countries for mapping the ICV data (Profit Center, Customers,
Vendors)
23-Nov-10
ICV initial package
06-Dec-10
Kick off meeting with ICV team and pilot countries
09-Dec-10
Demo of the ICV fields in master and transaction data after import of ICV package and initial
testing within REMSC
15-Dec-10
ICV initial assessment
23-Dec-10
Meeting with the ICV team and the first pilot countries (AU, SG, IN) proposed by ICV team
24-Jan-11
Discussions with the countries (TH, AU, SG, IN, NZ, AE, MY)
14-Feb to
25-Feb-11
Delivery of package with final set of corrections
03-Mar-11
Local enhancements for template specific validations in consultation with ICV team
2nd week
Mar-11
(details of the package corrections and local enhancements attached in the presentation)
© ABB Group
April 8, 2015 | Slide 3
Further activities to be completed for Go-Live
 Additions/ Change in Global fixed values for customers/ vendors which needs to be resolved
as part of Gate 3 checklist for ICV implementation. Concurrence/ formal approval is required
from countries to move these mappings/ validations. Parameters involved are as follows:
 Region field in customer master (account groups 2500, 2600) to make it optional for all
countries except IN from current mandatory settings
 Search term1 in customer/ vendor master to be mapped with Abacus
 Specific blocking reason for ICV
 Explanation of the above parameters are given in the coming slides
 A feedback excel sheet is sent along with this email in which the countries need to send the
feedback latest by 31-Mar-11
© ABB, SREMSC
April 8, 2015 | Slide 4
Customer/ Vendor master –Mandatory fields mapped in ICV customizing
We need to map minimum of
those fields which are mandatory
in our SAP system
Customer/ vendor master fields
mapped in ICV customizing
Name, Search term1, Country
(account groups 1500, 1600,
1800, 2500, 2600, 2800)
City , Region (only for customer
account groups 2500, 2600)
Technically those fields which are
mapped in ICV customizing will be
filled with the data from ICV
connector / table into the
customer/ vendor master when
the user is creating through ICV
transaction
Customer/ Vendor Master Fields- Change in Optional/ Mandatory due to ICV
■ For creation of vendors/ customers through ICV transaction, we need to have the minimum number of
parameters which are mandatory as per our system configuration for creating a customer/ vendor
■ Currently for Internal customers and vendors mandatory field mappings are as follows
■ Customer account groups 2900, vendor account groups 1500, 1600, 1800: Name, Search Term1,
Country
■ Customer account groups 2500, 2600 : Name, Search Term1, Country, City, Region
■ This needs to be maintained in the mapping table for ICV where we relate the field in customer/ vendor
with respect to ICV custom table. During creation of customer/ vendor through ICV transaction, values in
ICV table will populate the values in our customer/ vendor master
■ Region Field mandatory / optional in customer master (Account groups-2500, 2600)
■ Currently Region is mandatory for customers belonging to 2500, 2600 account groups for all
countries
■ With ICV implementation when the user is creating a customer through the ICV transaction
/ABBICV/ICV_CR which will be available for the users through the area menu ZCAGLICV_USERS,
since the region value is not there in ICV data system will throw error
■ As per business requirement Region is required only for country IN due to taxation requirements
■ Hence we propose to make the Region field optional for other countries and bring in validation to
enter the region only for IN for the above account groups
■ Search term to be mapped for Abacus
■ Currently most of the countries are using search term for Abacus codes relevant for the customer /
vendor
■ So we propose for mapping the Abacus code to the search term in customer / vendor master
■ With this mapping, when the user is creating a customer/ vendor through the ICV transaction, it will
populate the Abacus values from the ICV table
■ Both the above are illustrated in the coming slides
© SAS ERP-SERMSC
April 8, 2015 | Slide 6
Customer Master –Region Field mandatory
Currently Region field is
mandatory for customer account
groups 2500, 2600 for all the
countries. This needs to be
mandatory only for IN and other
countries are maintaining some
value since there is a system
prompt
In the ICV data, since Region field
value is not there, while trying to
create a customer/ vendor through
ICV transaction, user can’t create
a record. To avoid this it is
proposed to have the Region field
optional for other countries and
bring in validation only for IN to
input the value. In the ICV creation
transaction itself, a validation
through enhancement is planned
Customer Master –Region Field mandatory
During Creation of a customer through ICV transaction for account
groups 2500, 2600 if the country code of customer is IN (India)
system will prompt for entering the Region. For all other countries
system will not prompt for Region. If any other countries want
Region to be mandatory, please specify the same in the feedback
excel sheet
Customer Master –Search Term1 field & Abacus code
Currently most of the countries are
maintaining the ABACUS code of the
Internal customer/ vendor in the
Search term 1 field or in some cases
ABACUS –PG
We want the confirmation from the
countries whether we can map this
field to the Abacus code. Impact of this
will be during creation of customer/
vendor, system will copy the Abacus
field value from the ICV connector /
table into this field
Those countries who are filling up with
ABACUS-PG need to take note that
PG is available in the ICV tab and also
search functionality with respect to
ABACUS-BU-PG is available at master
data level and also transaction level
(PO or SO) . So they can manage only
with ABACUS in search term1 field
Customer Master –Blocking Reason
It is proposed to have a new blocking reason 90 (Block from ICV) for the
customer master. The same will be mapped in ICV configuration. If a particular
ICV ID is “Set to inactive” in ICV MDM server, then
i) After the ICV connector is implemented, those records which are mapped
to Inactive ICVs in SAP system will be set with this new blocking reason
90 (Order block)
ii) While one can perform already open transactions, further sales orders
can’t be created for those
ICV Transactions for business users
Transaction Code
Transaction
ZCAGLICV_USERS
Area menu for ICV
ZCAGLICV04
ICV Mapping Percentage
/ABBICV/ICV_CR
ICV Customer/Vendor creation
/ABBICV/DATA_MIGRT
ICV data migration
All the above transactions have been given to the UATIDs of the countries. In
production environment once the package is moved in April-11 request for
assigning transactions to relevant master roles will be placed
© ABB Group
April 8, 2015 | Slide 11
Recap of the activities for ICV implementation as of Mar-2011
ICV implementation activity description
Date
Mail communication sent to countries for mapping the ICV data (Profit Center, Customers,
Vendors)
23-Nov-10
ICV initial package
06-Dec-10
Kick off meeting with ICV team and pilot countries
09-Dec-10
Demo of the ICV fields in master and transaction data after import of ICV package and initial
testing within REMSC
15-Dec-10
ICV initial assessment
23-Dec-10
Meeting with the ICV team and the first pilot countries (AU, SG, IN) proposed by ICV team
24-Jan-11
Discussions with the countries (TH, AU, SG, IN, NZ, AE, MY)
14-Feb to
25-Feb-11
Delivery of package with final set of corrections
03-Mar-11
Local enhancements for template specific validations in consultation with ICV team
© ABB Group
April 8, 2015 | Slide 12
Process Flow for ICV- Migration, creation or change
Activity
Description
Country ICV team
Migration of existing
records
Mapping of Profit centers,
customers/ vendors to be done
with ICV Level 2 ID
Creation of new Internal
customer/ vendor (account
groups 2500, 2600, 2800,
1500, 1600, 1800)
Create the record with respect to
ICV details through the
transaction /ABBICV/ICV_CR
Change of ICV details for a
particular record (scenario:
if a particular record has a
wrong assignment of ICV)
Country team to provide the
Change of address details
© ABB Group
April 8, 2015 | Slide 13
REMSC
Remarks
Upload the mappings of
profit centers, customers/
vendors
For the mapped profit
centers, customers/ vendors
ICV details will be populated
into master data which will
further flow to transactions
N.A
Points raised by countries and clarifications
Points raised by countries/
Doubts
Clarification
Country
What needs to be done for flow of
ICV details in open transactions
Logic in the forms is system will look for the transaction for the ICV details and if it is not there then
it will fetch the ICV details from master data (customer/ vendor). So there is no need to go into the
open transaction and change any parameters for getting the ICV details
All
countrie
s
IDTO vendors and customers
(account groups 1600, 2600) to be
included in ICV mapping
ICV configuration has been done for the same and so the ICV details will flow to the master data
and later into transactions for these account groups. Those countries who want the ICV details for
these account groups, should specify in their solution manager calls for Forms to include the IDTO
customer/ vendors also. Those countries who don’t want to consider the IDTO will still get the
blank ICV tabs in the customer/ vendor master and their forms will not carry any ICV details
TH
Link to the ICV portal High Level
Q&A for ICV roll-out in ABB
http://inside.abb.com/cawp/gad00914/9c82bcb38d99f5d3c12577fa0041f2ab.aspx
© ABB Group
April 8, 2015 | Slide 14
Country Mappings Dashboard
Category
Overall mapping status of the
countries as of 20-Mar-11
© ABB Group
April 8, 2015 | Slide 15
Mapping File
Long term approach for ICV- elimination of duplicates and have ICV ID as Local ID
 After the implementation of ICV, we are going to have multiple vendor/ customer codes per ICV
ID in many cases because we are following mapping method
 To eliminate
© ABB, SREMSC
April 8, 2015 | Slide 16
© ABB, SREMSC