Sie sind auf Seite 1von 3

IS-U-Spezifika Set-up and Load-Guide zum Geschftspartners

IS-U-Specifics on the Set-up-and-Load-Guide for the


Business Partner
Introducti on
Note
Before newly created business partner data from the SAP CRM system is replicated in
the SAP IS-U system, you must first execute an initial data transfer. You use the Start
Initial Load transaction (transaction code R3AS) to transfer the business partner data to
the CRM system.
Make the settings described below, after you have made the configuration settings for business
partners in SAP CRM, which are described in the Solution Manager.
The following provides a short summary of the ERP Business Partner SD Customer concept in SAP
IS-U:
When creating or changing a business partner with the role Sales Prospect or Contract Partner, you
can specify a sample customer (SD customer). This creates an SD customer with the same number as
the business partner. Data is copied from the sample customer (tables KNA1, KNB1, KNVV, KNVP,
KNVA, KNVI, KNVD, KNEX, KNVS and KNVL). Name and address data, as well as some additional
fields, are transferred from the business partner. If the SD customer already exists, the system only
transfers part of the data from the sample customer (only the sales and distribution areas that do not
yet exist).
If you now connect a CRM system, the central data from the CRM business partner is exchanged with
the ERPbusiness partner, and the CRM-specific data is exchanged with the SD customer. The CRM
business partner has the same number as the ERP business partner and SD customer.
You work mainly with the BUPA_MAIN queue. You only work with the CUSTOMER_MAIN queue
when you are changing SD customer data, such as sales area data.
Control Table Conversion
To execute the IS-U specific business partner concept, you must convert the following control tables.
Make the following entries (with call indicators set) for the Business Partner object BUPA in the IS-U
table COM_BUPA_CALL_FU (transaction SM30):
Event Item Name of Function Module
Mapping Inbound Processing 5000 COM_BUPA_MWX_FILTER_ISU
Mapping Inbound Processing 10000 COM_BUPA_MWX_FILTER_MAIN
Mapping Inbound Processing 50000 COM_BUPA_MWX_MAP_NUMRANGE
Mapping Inbound Processing 100000 COM_BUPA_MWX_MAP_MAIN_CENTRAL
Mapping Inbound Processing 150000 COM_BUPA_MWX_MAP_ISU
R/3 Object Inbound Processing 3000000 COM_BUPA_MAIN_INBOUND_ISU
R/3 Object Outbound Processing 1000000 COM_BUPA_MWX_CREATE_MAIN
Mapping Outbound Processing 100000 COM_BUPA_MWX_BPS_FILL_CENTRAL
Mapping Outbound Processing 150000 COM_BUPA_MWX_BPS_FILL_ISU
Delete other entries for this event.
Adjust the following entries (with call indicators set) for the Business Partner object BUPA in the
table CRMC_BUT_CALL_FU (transaction SM30) according to the note 757955:
This should be done for the ERP-System and also for the CRM-System !
IS-U-Spezifika Set-up and Load-Guide zum Geschftspartners
In view V_SMOFEVOB, you must use SM30 to delete the entries for the following events in CRM:
00001321
CAM_1000
CAM_2000
CAM_3000
Use the Change Application modules per Publish / Subscribe Interface transaction (transaction code
BF31) to change the function module allocation for the following two Business Transaction Events
(BTE) in SAP IS-U:
Event Applc. Function Module
DE_KTOKD IS-U COM_INTERFACE_DE_KTOKD_ISU
00001321 IS-U ISU_INTERFACE_00001321
Delete all other entries for these two BTEs and the following events:
CAM_1000
CAM_2000
CAM_3000
Exchangi ng Roles
Sold-to-parties in CRM are replicated as contract partners in the OLTP system, and vice versa.
The role Installer is not transferred to the CRM System.
Other roles, such as customer-specific roles, are only adopted in CRM if they are created there.
Setti ngs for Groupi ngs and Number Ranges
To ensure that business partner numbers are identical, you must create an external number range
with the same area for each internal number range (number range object BU_PARTNER) in the other
system. This external number range must then be allocated to a grouping (IS-U or CRM table
V_TB001; transaction SM30). During the data exchange, the system automatically selects a grouping
that is allocated to this number range.
Set up the areas in such way, that there is enough space for a long-term operation.
As with settings for the number range, the account group selection takes place when creating a
business partner in CRM. An external number range (number range object DEBITOR) must exist for
the number that is used to create a business partner in CRM. An account group (IS-U table T077D;
transaction SE16) must be allocated to this number range. This account group must also fulfill other
requirements, such as corresponding to the role in CRM (Sales Prospect or Sold-to-Party). If several
account groups are available for selection, the group intended for FI-CA (see table TFK077D) is used.
During the initial download, you must temporarily convert all number ranges to external. This makes it
possible to create all the business partners with the same number. During the delta download the
system searches for a grouping that is allocated a suitable external number range.
Sample Customers in the Delta Upload
You can store sample customers in the IS-U table TCRMBP_REFCUST (transaction SE16). These
sample customers are used when creating a CRM business partner. This means that less data is
transferred than when creating an ERP business partner (IS-U tables KNVD, KNB1, KNEX, KNVS and
KNVL; transaction SE16).
In table TCRMBP_REFCUST, the system searches generically for a sample customer:
First with Category, Grouping and Type, then with Category and Grouping (Type equals SPACE), then
only with Category
IS-U-Spezifika Set-up and Load-Guide zum Geschftspartners
(Grouping and Type equal SPACE), and finally with all three key fields equaling SPACE.
Initial Download
Before performing the initial download, check whether an SD customer has been created for all
business partners in the ERP system, for which this is desired or necessary. (For example, to an SD
customer is necessary to use the billing engine in CRM.)
You should also check whether business partners already exist for all SD customers. Business partner
creation for SD customers is supported by tools (for example, during the IS-U implementation). In the
scenario described, you must not directly create any SD customers (except sample customers), since
you are not replicating anything in the CRM System.
Note
Regarding the data exchange of sales areas in delivery Customizing, check whether the
following three entries exist in IS-U table CRMINTBAP (transaction SE16) for the IS-U
table KNVV (transaction SE16).
TABNAME BAPISTRNAM INTTABFLD BAPSTRFLD
KNVV BSC_SALESA SPART DIVISION
KNVV BSC_SALESA VKORG SALES_ORG
KNVV BSC_SALESA VTWEG CHANNEL

Das könnte Ihnen auch gefallen