Sei sulla pagina 1di 20

INTERNAL USE ONLY

SAP Convergence

Functional Specification
Project <Mexico FS-CD >
FS Name: <FS_Master data mode.docx>
(Where ** is the code for the roll-in BU Code and XXXX is the 4 digit RICEF
number)

260307202

1 of 20

INTERNAL USE ONLY


SAP Convergence

Document History
Document details:
Author
Workstream
Business Unit (BU)

Mariano Duro/Sakshi Gupta

Version(s):
Date

Name

Version

03.12.2014

Mariano Duro

1.0

Details of Change
Creation FS for master data
model

Reviewer(s):
Date

Name

Version

Signature

Version

Signature

Approver(s):
Date
Name
Business
Representati
ve
GFC Core
GFC HUB
Core
BI BW Core
Local roll-in
Owner
Developmen
t Owner

260307202

2 of 20

SAP Convergence

Table of Contents
Document History........................................................................................2
Table of Contents.........................................................................................3
1

RICEF Objective.....................................................................................4
1.1
1.2
1.3
1.4
1.5

General Requirements...........................................................................5
2.1
2.2
2.3
2.4

Management Summary...................................................................4
RICEF Characteristics......................................................................4
Contact Information.........................................................................4
Related Documents.........................................................................4
Open Points.....................................................................................4

General Overview............................................................................5
Master data process.......................................................................6
Design.............................................................................................7
Customizing MD model..................................................................13

Functional Requirements Report or Program.....................................14


3.2
3.3

General Business Process Model Sakshi and following...............16


Technical Considerations...............................................................17

260307202

3 of 20

SAP Convergence

1 RICEF Objective
1.1 Management Summary
1.2 RICEF Characteristics
Global/

Scope:
Priority:
Complexity:

CORE
High
High

Local Roll-In
Medium
Medium

Low
Low

1.3 Contact Information


Who

Name

Phone E-Mail

1.4 Related Documents


Document Title

Stored

1.5 Open Points


Topic

BP MD Field

260307202

Description
Are the below fields used & for
which purpose?
- Tax office
- Tax Number
- WH Tax Country
- Sort key Eg. MX1
- Cash mgmnt group Eg. A3

Responsible

Due

Business

13.02.2017

4 of 20

SAP Convergence

2 General
2.1 Assumptions for the model

A business partner (a Vendor in Legacy FI) can exist just in one


company code.

In no case a BP can be assigned to several company codes

If there are multiple company codes for the same vendor, as it is


currently happening in the PCL 350 Fi client, this can be considered
an exception. When the business user will try to assign the same
Vendor code/external number, the Excel upload tool will deliver an
error message. To avoid the error message the Excel upload creates
the UDIS partner adding (concatenating) the company code to the
Vendor code/external number in the search field.

The search field will be used to contain the trace with the code
existing in the feeder system.

In Mexico there are 4 different categories of Partners:


1. CPD partners used for one time payments related to Claims
and premiums reimbursement
2. Agents Brokers for which Zurich MX pays the commission
3. Udis Partner: Sundry partners, intermediaries, paid from Zurich
for that are going to receive a fee in case of sales of Zurich
policies
4. One time partner: Not used as the BP for the posting but as a
receiver of the money for posting concerning the CPD
partners; For this reason their master data will be created
during the posting process and not with the separated MD
process (master data upload via Excel) mentioned above
The above categories, except the one time partner, correspond to a
group account category of Vendors existing in the Local FI system in
Mexico:

260307202

5 of 20

SAP Convergence

o CPD partner CPDA


o Agents (Broker) AGED for GI (MX16 and MX20)
o Agents (Broker) AGEN for LIFE (MX17)
o Udis Partner MAIT (saved a sundries)

2.2 Process and source of the Master data


2.2.1

Process for the current existing partners

All existing vendors, in use in the local FI client, will be created as Business
Partners in FS-CD via Excel Upload.
The Excel upload creates the full Hierarchy required for postings: the BP
master data, the contract account and the Insurance Object.
The excel upload can be also used for modifications/updates afterwards.
NOTE: The above process does not apply to one time partner which are
created directly from the posting process in the interface

2.2.2

Process for new Partners

For new partners the process will be the following:

Difference from the AS-IS in FI.


1. The trigger for the creation of a new partner can be an email from a
feeder system user to the user in SAP FS-CD or an error message
260307202

6 of 20

SAP Convergence

during the upload of a posting file, which will inform the business
user in FS-CD about the missing Partner.
2. The FS-CD business user will upload via Excel the new partner
hierarchy storing the corresponding vendor code from the feeder
system in the FS-CD search field
Therefore, thought this field, FS-CD will store the mapping between the FSCD Business Partner and the Vendor in FI.

2.3 Design
The FS-CD master data model consists of 3 levels: Business Partner; The
insurance Object; The contract account:

2.3.1

Master data types, naming conventions, function

2.3.1.1 Business Partner


Business Partners (insured or policy holders, claimants, brokers, experts,
insurance companies) is the main master data in the FS-CD processes.
Each FS-CD will correspond in a relation 1 to 1 with the Vendor codes in
the Legacy SAP FI. A CPD or an Agent vendor will correspond 1:1 with a
Business Partner in FS-CD.
NOTE: Such a relation, between Vendor and Partner, might not be verified
for UDIS, due to inconsistent data already checked with the Business.
The BP ID is created in a way to identify the country to which the BP
belongs and the role type and function it has.
Below the BP naming convention for Mexico:

MX= first 2 digits represent the country ISO code


D, B, S or O;
o D= Dummy partners - CPD ones are create for one-time payment
o B for brokers and agencies
o O for general and Third parties
o S for Sundries (UDIS)
Number internal to identify a unique partner (see chapter 3.3.2)

2.3.1.2 Insurance Object


FS-CD insurance object master data are used to store information related
to the contract or to the agreement in place between the business partner

260307202

7 of 20

SAP Convergence

and the Zurich Companies Insurance objects; in FS-CD they can be used to
identify:

Policies
Claims
Premiums
Commissions
Brokerage Agreements
Reinsurance contract

Based on the project scope, i.e. Technical payments (disbursements), the


data model for Mexico will have a single insurance object/ contract
account per business partner (Main).

2.3.1.3 Contact Account


This is a further view on postings to store parameters used for various
processes (Dunning, clearing etc.)
It is also the level on which will be stored the company code for which the
processes are possible.

2.3.2

Master data model

2.3.2.1 CPD Master data model


BP (business partner, naming convention logic):
MX= first 2 digits represent the country ISO code
1 Digit for Insurance Object related to dummy partner
7 digits number assigned in customizing to the Vendor created in SAP FI
(old system)
CA (contract account category, naming convention logic):

MV for Mexican CPD life; MD for Mexican CPD GI, MF for Finance
Number range the same as for GCIE
IO (Insurance Object, Naming convention logic):

MX for the country;


CPD Authorization group for the role type,
The authorization group for the CPD partner (MXDC for GI CPD used for
claims, MXDP for the premium reimbursement, MXVC for Life CPD for
Claims and MXVP for premium reimbursements, MXFC for CPD used
for MX20 CPD payment for claims, and MXFP)
Defined in a customizing table

260307202

8 of 20

SAP Convergence

CPD partners company codes MX16:

CPD partners company codes MX17:

260307202

9 of 20

SAP Convergence

CPD partners company codes MX20:

2.3.2.2 Broker Master data model (AGED & AGEN)


BP (business partner, naming convention logic):
MX= first 2 digits represent the country ISO code
B = 1 Digit for Brokers
Sequential number
CA (contract account category, naming convention logic):

MB = Mexican Brokers
Number range the same as for GCIE CA for brokers

IO (Insurance object, naming convention logic)

MX= first 2 digits represent the country ISO code


BS = 2 Digits (Broker standard)
1 digit D or V to distinguish life from GI business (Vida, Daos)
1 Digit M for the general main object

Broker partners master data model for company codes MX16 and
MX20:
260307202

10 of 20

SAP Convergence

Broker partners master data model for company code MX17:

260307202

11 of 20

SAP Convergence

2.3.3
UDIS Master data model (Account group MAIT)
cross company code (MX16, MX17 and MX20)
BP (business partner, naming convention logic):
Intermediate existing as SAP FI master data with the account group MAIT.
Postings coming in the system are just commissions

MX for the country ISO code


S 1 digit for the partner type (sundry)
A digit representing the company code D for MX16, V for MX17, and F
MX20
Sequential number for the remaining digits

CA (Contract account, naming convention logic):

MU: for Mexican Udis partner

IO (Insurance Object, naming convention logic):

MX for the country Iso code


UD for the partner role type UDIS
M for main Object
D, V, or F depending on the company code
Sequential number

260307202

12 of 20

SAP Convergence

2.3.4

One time partner

One time partner are not relevant because there is no master data model
to present

260307202

13 of 20

SAP Convergence

2.4 Customizing MD model


2.4.1

Contract Account:

Collection and Disbursement Basic Function Contract accounts


Configure contract account Categories and Assign number range:

Values created for Mexico:

2.4.2

Contract Account Variants

Collection and Disbursement Basic Function Insurance Object Account


Creation Variant settings Define Account creation Variants:

Settings created for Mexico:

260307202

14 of 20

SAP Convergence

2.4.3

ZF1CD_T2010 customizing

Table ZF1CD_T2010 is used for the Excel upload creating master data,
In this table MX company codes (one specific or generals such as MX*)
have to be defined to specify which creation variant has to be used; Which
account view and Account management, which tolerance group and
clearing category

3 Functional Requirements Report or Program


3.1.1

Checks and Mapping For the Excel upload

Each of the partner type defined in the chapter 2.1 is assigned to a


specific FI number range, except for the CPD business partner, which they
start always with the S and they do not have any special rule for the
number range.
Number Ranges per Group Account/Business Partner role:
UDIS partner can contain the below number range in the search Item field
UDIS FI Number
Range
36000000003699999999

260307202

Account
Group
MAIT

FS-CD nr
Range
MXS
+Internal Nr

15 of 20

SAP Convergence

NOTE: even in presence of a group account in common for all company


codes in FI, there are just few cases of Vendors belonging to more than a
company code.
In FS-CD its not requested to enhance such a link. When a Vendor is
already assigned to a BP for a specific company code (e.g. MX16) , when
its requested to assign it to a different company code, FS-CD will generate
a second BP code, which will have in the search field the same Vendor,
with the addition of the company code to which it refers to.

FI Account
Group
AGED
AGEN
MAIT/ UDIS
CPDA

Creation
Manual via
Excel Upload
Manual via
Excel Upload
Manual via
Excel Upload
Manual via
Excel Upload

Account Group/ Company


Code
MX16, MX20
MX17
MX16, MX20, MX17
CPD1 MX16, MX20
CPD2 MX17

Agents GI & LIFE:


Brokers MX17
G0000000G9999999
Brokers MX16
Z000000Z999999

260307202

Account Group

FS-CD nr Range

AGEN for MX17


MXBSV+Int Numer
3600003060

AGED for MX16


MXBSD+Int Numer

16 of 20

SAP Convergence

NOTE: Agents master data are not in scope for the company code MX20.

3.2 General Business Process Model Sakshi and


following
File Field in
Excel File

FSCD Field

BOOKING

MD_TYPE

FI Field
-

FSCD Mapping

Description

Value to be set as X in excel


file which indicates the lines
in the EXCEL-file to proceed.

Account Group

CPD partners will be split


additionally in MXDS and
MXDP for the company code
MX16; MXVS, MXVP for
MX17; MXFS and MXFP for
MX20.

1:1

External Partner number to


be updated with the Vendor
number in FSCD

1:1

Title Eg: Mr./Ms.

AUGRP

BUT000AUGRP

BPEXT

BUT000-BPEXT

TITLE

BUT000-TITLE

ADRC-TITLE_MEDI

NAME_ORG1

BUT000NAME_ORG1

ADRC-NAME1

NAME_ORG2

BUT000NAME_ORG2

ADRC-NAME2

BU_SORT1

BUT000BU_SORT1

ADRC-SORT1

STREET

ADRC- STREET

ADRC- STREET

1:1

HOUSE_NUM
1

ADRC
-HOUSE_NUM1

ADRC
-HOUSE_NUM1

1:1

POST_CODE1

ADRC
-POST_CODE1

ADRC
-POST_CODE1

1:1

CITY1

ADRC-CITY1

ADRC-CITY1

1:1

COUNTRY

ADRCCOUNTRY

ADRC-COUNTRY

1:1

PO_BOX

ADRC- PO_BOX

ADRC- PO_BOX

1:1

POST_CODE2

ADRCPOST_CODE2

ADRCPOST_CODE2

1:1

TEL_NUMBER

ADRC
-TEL_NUMBER

ADRC
-TEL_NUMBER

1:1

FAX_NUMBER

ADRCFAX_NUMBER

ADRCFAX_NUMBER

1:1

OPBUK

FKKVKP
-OPBUK

RF02K-BUKRS

STDBK

FKKVKP-

RF02K-BUKRS

260307202

LFB1-LIFNR

1:1
1:1
1:1

1:1

Company Code will be stored


on Contract Acct in FSCD

1:1

Company Code will be stored


17 of 20

SAP Convergence

STDBK

on Contract Acct in FSCD


Trading partner field is not in
scope for the business
partner types used in Mexico
(there is no company)

VBUND

BUT0IDIDNUMBER

1:1 with BUT0IDTYPE = VBUND

BANKS

BUT0BKBANKS

1:1

BANKL

BUT0BKBANKL

1:1

BANKN

BUT0BKBANKN

1:1

SWIFT

Used to derive other bank


details

IBAN

Used to derive other bank


details

KOINH

BUT0BKKOINH

AZAWE_X

*** NO DATA
IN EXAMPLE
FILE ***

ABVTY_X

*** NO DATA
IN EXAMPLE
FILE ***

1:1

3.3 Technical Considerations


For all the account groups the business partner together with the master
data will be created manually via excel upload. In order to facilitate the
process a new program has been written that will perform this task.
It has to be noted that excel files will have always the same format and
the same structure regardless the type of the master data.

3.3.1

Program Name and Transaction Code


Name of the Program
Name of the Transaction
Code

3.3.2
-

ZMXCD_MD_EXCEL_UPLOAD
ZMXCD_T_MD_XL_UPLD

Master Data

Business Partner: Business Partner number is different in FS-CD, but


addresses will be migrated from the existing implementation. Since
the Mexico master data is going to be in the same client with several
other countries a differentiation of the numbering of the objects is

260307202

18 of 20

SAP Convergence

going to be very important especially in order to keep apart batch


processing over a larger number of accounts.
Accou
nt
Group

Object number in FSCD

Country prefix (2 digits)


+ Partner type
Prefix (1 digit) +
sequence number per
vendor number

AGEN

Country prefix (2 digits)


+ Partner type
Prefix (1 digit) +
sequence number per
vendor number

AGED

Country prefix (2 digits)


+ Partner type
Prefix (1 digit) + unique
number derived from
table - ZMXCD_CPDA

CPDA

Country prefix (2 digits)


+ Partner type
Prefix (1 digit) +
sequence number

MAIT/
UDIS

Tables Used

Example

BP prefix and number


ranges object are
defined in table ZMXCD_T2014

MXB0000001
Unique Vendor number
stored in field BPEXT of
the partner.
The vendor numbering is
stored in table ZMXCD_ACCGR

BP prefix and number


ranges object are
defined in table ZMXCD_T2014

MXB0000001
Unique Vendor number
stored in field BPEXT of
the partner
The vendor numbering is
stored in table ZMXCD_ACCGR

BP prefix is defined in
table - ZMXCD_T2014
and a unique number
is added which is
derived from table ZMXCD_CPDA

MXD0000001

BP prefix and number


ranges object are
defined in table ZMXCD_T2014

MXS0000001

Vendor will be stored in


FS-CD in field Search
term 2 for business
partner (BU_SORT2) of
the partner and the
unique number derived
from table ZMXCD_CPDA will be
strored inBPEXT
Vendor will be stored in
FS-CD in field Search
term 2 for business
partner (BU_SORT2) of
the partner and vendor
number+ company code
is stored in BPEXT
The vendor numbering is
stored in table ZMXCD_ACCGR

Contract Account: represents the partners sub-ledger accounts.


Each of these is assigned to a contract account category. These
categories and the creation variant are defined in table ZMXCD_T2014. The other parameters used for the account creation
such as, Tolerance group, Clearing Category, Relationship of

260307202

19 of 20

SAP Convergence

Business Partner to Contract Account, Account View, Account


Management are stored in table - ZF1CD_T2010.
-

Insurance Object: To ensure a unique numbering for insurance


objects coming from various feeder systems to FS-CD a countryspecific prefix will be part of the insurance object number. It is
followed by a 3 digits prefix that will indicate the type of business
that is handled over this object.

Accou
nt
Group

Object number in FSCD

Tables Used

Example

IO prefix is defined in
table - ZMXCD_T2014

MXBSVM000001

AGEN

Country prefix (2 digits)


+ IO type
Prefix (3 digits) + M +
unique vendor

IO prefix is defined in
table - ZMXCD_T2014

MXBSDM000001

AGED

Country prefix (2 digits)


+ IO type
Prefix (3 digits) + M +
unique vendor

IO prefix is defined in
table - ZMXCD_T2014

MXCPD210MXDS2015

CPDA

Country prefix (2 digits)


+ IO type
Prefix (3 digits) + unique
number (from tableZMXCD_CPDA) + Auth.
Group from input file +
year
Country prefix (2 digits)
+ IO type
Prefix (3 digits) +
sequence number

IO prefix and number


ranges are defined in
table - ZMXCD_T2014

MXUDM0000001

MAIT/
UDIS

Auth. Groups are defined


in custom tableZMXCD_AUGRP

The above tool runs with the below template:

MD_MX_Update.xls

260307202

20 of 20

Potrebbero piacerti anche