CVI Workshop III

Customer Vendor
Integration (CVI)
in ERP2005
Steffen Dockhorn
SAP AG
Overview
Controller and Strategy
Key Mapping and Key Assignment
Data Mapping
Dialog Extensions@FS-BP
Complex Interface for CVI
Special Functions
Documents & Question & Answers
Overview
General Information
 The replication between business partner, customer master (including
customer contact) and vendor master is bidirectional and synchronous. The
changes in the business partner are replicated directly within the same LUW
to the corresponding ECC object and vice versa.
 CVI is part of MiniPlatform in ERP2005 where a common architecture for
business partner and product master is used.
 Coding is located in SW layer SAP_ABA 7.0 (general parts of controller) and
SAP_APPL 6.0 (maintenance systems S7B and P7D)
 It is possible to switch on (or switch off) the whole replication or even parts of
the replication.
 CVI was designed to be used in one system in one client (no distribution)
 CVI was not designed to replace maintenance transactions from FI/SD/MM
 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Overview
Old solution (up to ERP2004) New solution

Unidirectional replication from BP to  Bidirectional replication from BP to
customer/vendor customer/vendor and vice versa
Cannot be activated/deactivated Can be activated/deactivated partially or
Only runs in BDT based maintenance completely
transactions (dialog or Direct Input) Runs in all channels (dialog, BAPI…)
FI data saved using function module Customer/vendor data saved using
(customer) and batch input (vendor) special customer/vendor APIs
Only one company code and sales area Maintenance of multiple company codes,
can be maintained (no change without sales areas and purchasing organization
leaving transaction BP) possible without leaving transaction BP
Company code and sales area cannot be Company code, sales area and
deleted also if they have not yet been purchasing organization can be deleted as
saved (only abort possible) long as they have not been saved
Company code is always valid for all Company code can be assigned to single
assigned objects (BP, customer, vendor) objects

Overview
Old solution (up to ERP2004) New solution

Optional customer based roles can be Optional customer based roles can be
set as customer based (without undo set as customer based (undo before
function, only abort possible) saving possible)
Limited support of default values Support of optional vendor based roles
(customer fields only; only tables KNA1, Support of default values for customer
KNB1 and KNB5) and vendor fields (complete data
No enhancement possible without catalogue)
modification, very complicated Easy enhancement using BAdIs and
Difficult maintenance due to multiple BDT (dialog parts)
BDT applications, function groups and Easier maintenance due to use of object
cumbersome coding oriented XO framework (dialog extensions
and complex interface) as well as clear
separation between single components
Enhanced field catalog for BP dialog
(e.g. purchasing data)
Complex BP interface offered
Mass data synchronization possible

Overview
Architecture

Overview
Architecture
CVI Complex Interface
Dialogue Direct
BUS BURS VMDS CMDS (Classic Dynpro) Input
BP APIs FS Enhancements BDT
XO
Get
CVI
Outbound
Customer Vendor
APIs APIs
Customer Vendor Business Partner

Overview - Architecture
Validation
Packages and Responsibilities method calls
BDT objects
CVI_FS_UI_CU CVI_FS_UI_VE
STOMER NDOR
AP-MD-BP-SYN
FS-BP
FS_BP_ECC CVI_FS_INTEG CVI_SYNC_CO

RATION NTROL
company code
LO-MD-BP-SYN
handling
CVI_FS_APPLIC CVI_MAPPING VMD_INTERFA CVI_INTERFAC CMD_INTERFA

ATION_LOGIC CE E CE
BDT/DI & EI
integration incl.
default values
business logic
(xo technology
adoption)
CVI_MAPPING_ BUPA_INTERFAC
EXTENSION E_COMPLETE
data completion
method calls

Overview
Data Mapping
Special Functions
Controller & Strategy
Controller
 Platform specific tool residing in software layer SAP_ABA called by every
maintenance operation of master data (implementation in SAP_APPL)
 Controls the synchronization of data between the different object types
including data locking/unlocking and avoiding roundtrips during the
synchronization
 Each source object sends data to the controller without knowledge of the type
or number of target objects:
 Business Partner using BP outbound (CRMC_BUT_CALL_FU )
 Customer using BTE 00001321
 Vendor using BTE 00001421
 Realized in class MDS_CTRL_CONTROLLER

Controller - Customizing I
 Synchronization Objects - MDSV_CTRL_OBJ
 Delivered by SAP (AP-MD-BF-SYN)
 Based on table MDSE_CTRL_OPT (type E)
 Available in IMG via Cross-Application Components  Master Data Synchronization
 Synchronization Control  Synchronization Control  Synchronization Objects

Controller - Customizing II
 active synchronization strategies - MDSV_CTRL_OPT_A
 Not delivered by SAP in SAP_APPL, BP relevant entries delivered in EA-FINSERV
 Based on table MDSC_CTRL_OPT_A (type C  manual transport required!)
 Available in IMG via Cross-Application Components  Master Data Synchronization
 Synchronization Control  Synchronization Control  Activate Synchronization
Options

Strategy
 Called by the controller
 Creates entries for Post Processing Office in case of errors (if active)
 Calls the strategy implementations for the active combinations of source and
target object
 business partner to customer: CVI_STRATEGY_BP_CUSTOMERPROCESS
 business partner to vendor: CVI_STRATEGY_BP_VENDORPROCESS
 customer to business partner: CVI_STRATEGY_CUSTOMER_BPPROCESS
 vendor to business partner: CVI_STRATEGY_VENDOR_BPPROCESS
 Also used to synchronize SAP product and material master data

Errors/Problems related to Controller & Strategy

 No synchronization started
 BP outbound disabled in CRMC_BUT_CALL_FU
 Check CRMC_BUT_CALL_FU if function module MDS_BUPA_OUTBOUND is
active using event BPOUT
 Customer and/or vendor BTE are disabled
 Check if CMD_CUSTOMER_BTE_1321_IMPL and/or
VMD_VENDOR_BTE_1421_IMPL are running
 Active synchronizations have not been transported to target client
(MDSC_CTRL_OPT_A is type C!)
 Check MDSV_CTRL_OPT_A for relevant entries
 Short dump due to API error
 Post Processing Office switched off
 Check IMG for activation of PPO (recommended for further analysis)

Errors/Problems related to Controller & Strategy

 Only source object saved
 Error while saving target object
 Check PPO using transaction MDS_PPO2 for the reason
 Remove the cause (in most cases empty required fields)
 Synchronization not active
 Check MDSV_CTRL_OPT_A for relevant entries
 BP Role, BP Grouping or C/V Account group not relevant
 Check relevant customizing views (for details see chapter “Key Mapping & Key
Assignment”)

Overview
Data Mapping
Special Functions
Key mapping
 Key mapping is used to create and read assignments of BPs to customers,
customer contact persons and vendors if required (and vice versa)
 Realized in classes in package CVI_MAPPING
 CVI_KA_BP_CUSTOMER to assign customers and contact persons to BPs
 CVI_KA_BP_VENDOR to assign vendors to BPs
 Important methods:
 GET_ASSIGNED_CUSTOMER_FOR_BP
 IS_CUSTOMER_REQUIRED_FOR_BP
 GET_ASSIGNED_VENDOR_FOR_BP
 IS_VENDOR_REQUIRED_FOR_BP
 UKMS interface implemented

Key mapping tables

 New link tables have been created containing BP GUID and customer/vendor
number:
 CVI_CUST_LINK
 CVI_CUST_CT_LINK
 CVI_VEND_LINK
 Migration of existing link tables BD001 and BC001 is not required for general
functionality
 Old and new link tables are used for reading
 New entries are saved to new tables only
 Migration reports are offered by SAP
 CVI_MIGRATE_CUST_LINKS
 CVI_MIGRATE_VEND_LINKS
 Regarding performance and search help migration is recommended

Key mapping pre-conditions

 Mapping of old CVI solution has been retained unchanged for direction BP 
customer/vendor based on BP grouping and BP role
 Mapping of direction customer/vendor  BP was added based on
customer/vendor account group
 Several combinations regarding number assignment are possible (internal or
external number assignment, same number option)
 Exceptions:
 Account group is used for consumer
 Customer is retail site
 Vendor is retail distribution center

Key mapping customizing

 Mapping customizing for direction BP  customer/vendor
 V_TBD001 – assignment of BP grouping to customer account group
 V_TBD002 – setup of BP role categories as (optional) customer based
 V_TBC001 – assignment of BP grouping to vendor account group
 V_TBC002 – setup of BP role categories as (optional) vendor based
 Mapping customizing for direction customer/vendor  BP

 CVIV_CUST_TO_BP1 – assignment of customer account group to BP grouping
 CVIV_CUST_TO_BP2 – assignment of customer account group to BP role
 CVIV_VEND_TO_BP1 – assignment of vendor account group to BP grouping
 CVIV_VEND_TO_BP2 – assignment of vendor account group to BP role


 Mapping customizing for BP grouping to customer account group (view
V_TBD001) can be found in IMG using the following path:
 Cross Application Components
 Master Data Synchronization
 Customer/Vendor Integration
 Business Partner Settings
 Settings for Customer Integration
 Field Assignments for Customer Integration
 Assign Keys
 Define Number Assignment for Direction BP to Customer


 Mapping customizing for (optional) customer based BP roles (view
V_TBD002) can be found in IMG using the following path:
 Set BP Role Category for Direction BP to Customer


 Mapping customizing for BP grouping to vendor account group (view
V_TBC001) can be found in IMG using the following path:
 Settings for Vendor Integration
 Field Assignments for Vendor Integration
 Assign Keys
 Define Number Assignment for Direction BP to Vendor


 Mapping customizing for (optional) vendor based BP roles (view V_TBC002)
can be found in IMG using the following path:
 Set BP Role Category for Direction BP to Vendor


 Mapping customizing for customer account group to BP grouping (view
CVIV_CUST_TO_BP1) and BP role (CVIV_CUST_TO_BP2) can be found in
IMG using the following path:
 Assign Keys
 Define Number Assignment for Direction Customer to BP

 Define BP Role for Direction Customer to BP


 Mapping customizing for vendor account group to BP grouping (view
CVIV_VEND_TO_BP1) and BP role (CVIV_VEND_TO_BP2) can be found in
IMG using the following path:
 Field Assignments for Vendor Integration
 Assign Keys
 Define Number Assignment for Direction Vendor to BP

 Define BP Role for Direction Vendor to BP

Errors/problems related to key mapping

 Only BP (source object) saved
 BP grouping is not relevant for replication
 Check view V_TBD001/V_TBC001
 BP role is not customer/vendor based
 Check view V_TBD002/V_TBC002
 BP role is optional customer/vendor based but flag is not set
 Set flag in dialog or check function module in role settings
 Only customer/vendor (source object) saved
 Account group is not relevant for replication
 Check view CVIV_CUST_TO_BP1/ CVIV_VEND_TO_BP1
 Account group is consumer account group
 Check account group settings for customer accounts (no correction)
 Customer/vendor is retail site
 Check table T001W for customer/vendor number (no correction)

Overview
Data Mapping
Special Functions
Data Mapping
Data mapping
 Data mapping is used to synchronize data that is available at BP as well as at
customer/vendor master with same meaning
 It is initiated by the responsible strategy triggered by
 Business partner outbound
 Customer BTE 00001321
 Vendor BTE 00001421
 Complex structures are used for CVI objects
 BUS_EI_EXTERN for BP and BP relationship data
 CMDS_EI_EXTERN for customer data
 VMDS_EI_EXTERN for vendor data

Data Mapping
Data mapping – data sets

 General & address data
 Bank data & credit cards
 Old mapping was wrong (BUT0BK-BKVID  KNBK-BVTYP/ LFBK-BVTYP but had
to be kept to avoid data conversion for POT users
 Problems caused by multiple use of bank accounts and credit cards with BP
 Tax data as in CRM (new)
 Migration is required for upgrade customers using reports (see migration chapter)
 Industry sector
 Taken from former releases (e.g. TR-BP SAP BP)
 Trading partner
 Contact person (new, switched off by default)
 Data from FS dialog enhancements and complex interface is forwarded to
complex customer/vendor structures

Data Mapping
Data mapping classes

 Important classes in package CVI_MAPPING:
 CVI_MAPPER – assign data of CVI objects
 MAP_BPS_TO_CUSTOMERS
 MAP_BPS_TO_VENDORS
 MAP_CUSTOMERS_TO_BPS
 MAP_VENDORS_TO_BPS
 CVI_FM_BP_CUSTOMER – assign data of BP and customer

 MAP_BP_TO_CUSTOMER
 MAP_CUSTOMER_TO_BP
 CVI_FM_BP_VENDOR – assign data of BP and vendor

 MAP_BP_TO_VENDOR
 MAP_VENDOR_TO_BP
 CVI_FM_BP_CUSTOMER_CONTACT – assign data of BP and customer contact

Data Mapping
Data mapping customizing

 Data sets based on different customizing tables for BP and customer/vendor
require special customizing settings
 Customizing is maintained using special views:
 CVIV_CCID_LINK – assign payment card type
 CVIV_LEGFORM_LNK – assign legal form
 CVIV_MARST_LINK – assign marital status
 CVIV_CP1_LINK – assign department numbers of contact person
 CVIV_CP2_LINK – assign function of contact person
 CVIV_CP3_LINK – assign authority of contact person
 CVIV_CP4_LINK – assign VIP indicator for contact person
 Mapping of customer contact has to be activated in view
CVIV_MAP_CONTACT

Data Mapping
Data mapping customizing

 Customizing views can be found in IMG using the following path:
 AssignAttributes
 Assign Marital Status
 Assign Legal Form to Legal Status
 Assign Payment Cards
 Assign Industries
 Contact Person
 Activate Assignment of Contact Persons
 Assign Department Numbers for Contact Persons
 Assign Functions of Contact Persons
 Assign Authority of Contact Persons
 Assign VIP Indicator for Contact Persons

Data Mapping
Data mapping enhancements

 CVI_CUSTOM_MAPPER
 enhance or change complete mapping of BP data to customer/vendor (and vice
versa) fitting to customer needs
 Called at the end of field mapping after standard mapping procedures
 CVI_MAP_BANKDETAILS (CL_DEF_IM_CVI_MAP_BANKDETAILS)
 enhance or change bank data mapping
 standard implementation covers old mapping between BP bank ID and bank type
 CVI_MAP_CREDIT_CARDS (CVI_MAP_CREDIT_CARDS)
 enhance or change payment card mapping
 CVI_MAP_TITLE
 CVI_MAP_TITLE_DIRECT for direct mapping of titles
 CVI_MAP_BP_CATEGORY to determine BP type based on title

Data Mapping
Data mapping enhancements

 BAdIs can be found in IMG using the following path
 Business Add-Ins (BAdIs)
 BAdI: Data Assignment BP Customer/Vendor/Contact Person
 BAdI: Data Assignment of Bank Details BP Customer/Vendor
 BAdI: Data Assignment of Payment Cards BP Customer/Vendor
 BAdI: Data Assignment of Form of Address from Customer/Vendor to BP

Data Mapping
Errors/problems related to field mapping

 No or incomplete data mapping
 BP outbound disabled in CRMC_BUT_CALL_FU
 Synchronization is not active
 BP Role, BP Grouping or C/V Account group not relevant
 Check and complete customizing tables
 Customer/Vendor Account group is Consumer account group
 Change account group or grouping
 Customer/Vendor is retail site
 Short dump due to mapping error
 Customizing tables for data assignment not maintained
 Check and maintain IMG/tables
 Data for target object partially lost
 Error in customer implementation of BAdIs
 Check if error still exists with inactive BAdIs

Overview
Data Mapping
Special Functions
Dialog Extensions
 Additional fields for customer and vendor are offered in BP dialog,
especially in company code, sales and purchasing data (all fields already
offered in the old solution + extensions according to requirements)
 Fields are arranged in a way to easily differentiate responsible objects
 Header data in company code, sales and purchasing organization can be
changed within one transaction for single BPs
 For the customer and vendor representation the Customer Vendor

Integration solution extends XO components


Dialogue Direct
XO
Get
CVI
Outbound
Customer Vendor
APIs APIs

Dialog Extensions – BDT elements

Customer & vendor specific parts of dialog completely replaced:
 3 BDT applications required (+ FSBP active):
 CVIC – Customer Link
 CVIV – Vendor Link
 FIDT – Company code
 33 screens, 72 sections, 120 views (according naming conventions)
 220 field groups (1800 – 2039 + 389, 504, 505)
 10 customer data sets (adequate to customer tables e.g. KNB1)
 7 vendor data sets (adequate to vendor tables e.g. LFB5)
 1 common data set (trading partner)

Customer objects
1..* * 1..* * * 1
fsbp_business_object fsbp_application_object fsbp_memory_object fsbp_persistence_object

(f rom f s_bp_al_generic_serv ices) (f rom f s_bp_al_generic_serv ices) (f rom f s_bp_al_generic_serv ices) (f rom f s_bp_al_generic_serv ices)
cvi_ao_customer cvi_po_customer
cvi_mo_customer
fsbp_bo_cvi
cvi_po_cust_text
cvi_ao_customer_company_code cvi_ao_customer_sales_area
CMD_INTERFACE
fsbp_company_code cvi_sales_area
cvi_mo_cust_text cvi_mo_kna1 cvi_mo_knat cvi_mo_knb1 cvi_mo_knb5 cvi_mo_knbw cvi_mo_knex cvi_mo_knva cvi_mo_knvi cvi_mo_knvp cvi_mo_knvv

Vendor objects
1..* * 1..* * * 1
fsbp_business_object fsbp_application_object fsbp_memory_object fsbp_persistence_object

(f rom f s_bp_al_generic_serv ices) (f rom f s_bp_al_generic_serv ices) (f rom f s_bp_al_generic_serv ices) (f rom f s_bp_al_generic_serv ices)
cvi_ao_vendor cvi_mo_vendor cvi_po_vendor

fsbp_bo_cvi
VMD_INTERFACE
cvi_ao_vendor_company_code cvi_ao_vendor_purchase_org
fsbp_company_code cvi_purchasing_org
cvi_mo_lfa1 cvi_mo_lfat cvi_mo_lfb1 cvi_mo_lfb5 cvi_mo_lfbw cvi_mo_lfm1

Dialog Extensions – default values

 Customer/vendor fields can be filled with default values under some
conditions:
 BP is created in customer/vendor based role (all customer/vendor fields except
mapped from BP)
 First customer/vendor based role is added to existing BP (all fields possible,
exceptions see below)
 Sales area or purchasing organization is added
 First company code is entered (no cc exist for any object!)
 Company code is added and customer/vendor option is activated in company code
overview screen
 Defaulting can be implemented using extension spot
CVI_DEFAULT_VALUES
 CVI_DEFAULT_VALUES_CLASSIC calls function module entered in view
V_TBD002/V_TBC002 as in older releases

Errors/Problems related to Dialog Extensions

 Fields only displayed in change mode
 No active synchronizations
 Check MDSV_CTRL_OPT_A
 No customer/vendor required for BP (due to BP grouping and/or BP role)
 Change BP grouping/BP role or relevant customizing
 Role is optional customer/vendor based
 Switch to customer/vendor based on “Customer/Vendor: General Data”
 No company code/sales area/purchasing organization entered
 Fill header data (press enter) or mark company code for object in detail screen
 Field is set to display mode
 Use report BUPA_CHECK_VISIBILITY or check transaction BUCG
 Customer/vendor is retail site
 No action possible


 Fields are not displayed
 Application CVIC/CVIV is switched off
 Activate application in transaction BUS1
 Data set and/or application are missing at current BP view, wrong BP view
 Add data set and or application in transaction BUSD
 Change assigned BP view in IMG (e.g. to FLCU00, FLVN00 or FS0005)
 Field is set to be hidden
 Use report BUPA_CHECK_VISIBILITY or check transaction BUCG
 Subheader for company code, sales area and purchasing data are missing
 All fields of relevant screen sequences are set to be hidden
 Change settings to required mode (e.g. Opt. entry) in transaction BUCG
 Subheaders are not set as active
 Check view V_TBZJ1C and activate FS0001
 Application switched off by so called “FS switch”: remove FIDT from table TPZ40
 Activate application FIDT in BDT (transaction BUS1)


 Customer/Vendor created/changed only with mapped data
 Application FSBP is switched off
 Activate application FSBP in transaction BUS1
 Error in PAI function module or function module is missing in BDT view
 Short dump while saving due to API error
 Empty required field & Post Processing Office switched of
 Check IMG for activation of PPO
 Maintain assigned fields in BP dialog as required (BUCG)
 Only source object saved
 Error while saving target object with empty required field
 Check PPO using transaction MDS_PPO2 for the reason
 Maintain assigned fields in BP dialog as required (BUCG)

Overview
Data Mapping
Special Functions

Dialogue Direct
XO
Get
CVI
Outbound
Customer Vendor
APIs APIs

CVI_EI_INBOUND_MAIN
 Submit BP and BP relationship data, submit customer and vendor data
(except attributes mapped from BP)
 Optional customer/vendor based roles can be switched
 No call of default value implementations/function modules
 Not RFC enabled, not released for customer use
CVI_EI_EXTERN
BUS_EI_EXTERN – Business Partner Master Data
BURS_EI_EXTERN – Business Partner Relation Data
CMDS_EI_EXTERN – Customer Master Data
VMDS_EI_EXTERN – Vendor Master Data
CVI_ENSURE_CREATE – Make sure a customer/vendor will

be created for optional customer/vendor roles

CVI_EI_INBOUND_MAIN_DEFAULT
 Submit BP and BP relationship data
 Optional customer/vendor based roles can be switched
 call of default value implementations/function modules
 Call of CVI_EI_INBOUND_MAIN
 Not RFC enabled
CVI_EI_EXTERN
BUS_EI_EXTERN – Business Partner Master Data
BURS_EI_EXTERN – Business Partner Relation Data
CVI_ENSURE_CREATE – Make sure a customer/vendor will

be created for optional customer/vendor roles

Overview
Data Mapping
Special Functions
Special Functions
Creation of BPs from existing customers/vendors

 Transaction FLPBD1 and FLBPC1 still work
 If customizing is set up, automatically done using FI transactions
 Creation of mass data can be done using Synchronization Cockpit
 Customizing for direction customer/vendor  BP required
Linking of existing BPs with customers/vendors

 Transactions FLBPD2/FLBPC2
 Still not possible in BP dialog
 Customizing for direction BP  customer/vendor and customer/vendor  BP
required
 Layout completely changed

Special Functions
Creation of BPs from existing customers/vendors

FLBPD1 – Create BP
from Customer
FLBPC1 – Create BP
from Vendor

Special Functions
Linking of existing BPs with customers/vendors

FLBPD2 – assign BP
to Customer
FLBPC2 – Assign BP
to Vendor

Special Functions
Post Processing Office (PPO)

 Transaction MDS_PPO2
 Comfortable error handling and error analyzing especially for mass
processing
 Offers restart functionality and direct maintenance using known transactions
 Can be activated or deactivated in customizing
 Workflow activation possible
Synchronization Cockpit
 Transaction MDS_LOAD_COCKPIT
 Mass synchronization of BP and customer/vendor master data (especially for
initial load)
 Several options can be selected (e.g. number range or account group)
 Initial reports for customizing adjustment can be started

Special Functions
Post Processing Office (PPO)

 PPO can be activated in IMG using the following path:
 Cross-Application Components
 Synchronization Control
 Activate PPO Requests for Platform Objects in the Dialog
 Workflow items can activated in IMG using the following path:
 Cross-Application Components
 Establish Recipient of Postprocessing Messages

Special Functions
Post Processing Office (PPO) – Select screen

Special Functions
Post Processing Office (PPO) – Order overview

Special Functions
Post Processing Office (PPO) – Order details

Special Functions
Synchronization Cockpit

Special Functions
Migration reports
 Tax data
 Adjust tax data entries in DFKKBPTAXNUM and KNA1/KNAS/LFA1/LFAS
 Required due to implementation of tax data mapping (prevent data loss)
 CVI_ANALYZE_CUST_TAX_NUMBERS, CVI_ANALYZE_VEND_TAX_NUMBERS,
CVI_SYNC_CUST_TAX_NUMBERS, CVI_SYNC_VEND_TAX_NUMBERS
 Link table entries
 Copies link entries from BD001/BC001 to CVI_CUST_LINK/CVI_VEND_LINK,
entries have to be deleted manually from old tables
 Not required but recommended for performance and search help
 CVI_MIGRATE_CUST_LINKS, CVI_MIGRATE_VEND_LINKS
 Role customizing
 Replace BDT data sets and applications by new ones, adjust field status settings
 Only required if customer uses own roles
 CVI_ADJUST_ROLE_CUSTOMIZING

Overview
Data Mapping
Special Functions
Documents
 Release Notes and IMG documentation

 Customizing Guide in note No. 956054
 BDT Customizing overview of new and obsolete elements (Note No. 852870)
https://portal.wdf.sap.corp/irj/go/km/docs/guid/a0eab9d9-cc9b-2810-45af-e41298cef935
 Assignments of BDT field groups to field groupings of customer/vendor (note

No. 928616)
https://portal.wdf.sap.corp/irj/go/km/docs/guid/7080aeea-ca9b-2810-969b-8b8c6808f011

Documents
 Important Notes:
 851444 - BP_CVI: Data assignment of CVI in ERP 2005
 851445 - BP_CVI: Details for the reports to be executed for ERP 2005
 852870 - BP_CVI: Changes in BDT Customizing for ERP 2005
 852991 - BP_CVI: Extension options of CVI in ERP 2005
 858005 - ERP 2005 SP Stack 1 (10/2005) Release and Information Note
 872185 - BP_BCL: Performance optimization in the XO framework
 874412 - Additional info about upgrading to SAP ECC 6.0 with IS-M
 878817 - BP_BCL: Date fields in the direct input are not initialized
 879287 - BP_CVI Deleting mandatory partner roles
 880840 - BP_CVI Deleting dunning area deletes everything
 881467 - Notification workflow when creating a postprocessing order
 890371 - BP_CVI: Missing names in the BP dialog
 898519 - BP_CVI: CVI_SYNC_CUST_TAX_NUMBERS - lock table overflow
 898560 - BP_BCL: Blank change indicator is not ignored
 905917 - BP_CVI: Company code w/o customer/vendor results in error
 907860 - ERP 2005: Details for the Business Partner administration

Documents
 Important Notes:
 908022 - International Version of address not synchronized completely
 912426 - Usability of maintenance views
 912884 - BP_CVI: BP maintenance module with defaults
 914027 - Special processing in the controller for return vendors
 916443 - BP_CVI: Call for the entry of an order during the saving
 921848 - BP_CVI: Own role not possible when creating customer/vendor
 923833 - BP_CVI: Performance problem with tax data conversion
 925837 - BP_CVI: Preassigned company code is not transferred
 928145 - BP_CVI: Company code automatically created for customer
 928616 - BP_CVI: Customiz of required entry fields at BP/cust/vendor
 929320 - BP_CVI: Field control with inactive strategy
 929557 - Credit card synchronisation leads to a dump
 932820 - BP_CVI: Error in company code maintenance
 936646 - BP_CVI: Reading business partner customer data
 936660 - BP_CVI: Übersicht von Buchungskreis, Vertrieb und Einkauf
 956054 - BP_CVI Debitoren/ Kreditoren Integration ab ERP2005 (ECC600)

Questions & Answers

CVI Workshop III

Cargado por

Información del documento

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

CVI Workshop III

Cargado por

Copyright:

Formatos disponibles

Customer Vendor

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Old solution (up to ERP2004) New solution

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Old solution (up to ERP2004) New solution

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

BP APIs FS Enhancements BDT

Customer Vendor Business Partner

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

FS_BP_ECC CVI_FS_INTEG CVI_SYNC_CO

CVI_FS_APPLIC CVI_MAPPING VMD_INTERFA CVI_INTERFAC CMD_INTERFA

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Errors/Problems related to Controller & Strategy

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Errors/Problems related to Controller & Strategy

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

 UKMS interface implemented

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping tables

 Regarding performance and search help migration is recommended

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping pre-conditions

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping customizing

 Mapping customizing for direction customer/vendor  BP

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping customizing

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping customizing

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping customizing

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping customizing

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping customizing

 Cross Application Components

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Key mapping customizing

 Cross Application Components

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Errors/problems related to key mapping

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Data mapping – data sets

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Data mapping classes

 CVI_FM_BP_CUSTOMER – assign data of BP and customer

 CVI_FM_BP_VENDOR – assign data of BP and vendor

 CVI_FM_BP_CUSTOMER_CONTACT – assign data of BP and customer contact

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Data mapping customizing

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Data mapping customizing

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Data mapping enhancements

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Data mapping enhancements

 SAP AG 2005, CVI in ERP2005 / Steffen Dockhorn / ‹#›

Errors/problems related to field mapping