Note Language: English Version: 3 Validity: Valid Since 02.10.2006 Summary
Symptom
You u external interface CRMXIF_PARTNER_SAVE to import business partners in the 'Employee' role to a CRM Server.
Afterwards you either try to assign the business partners to an organizational unit in the organizational management, or to create a
relation of type "is employee" for them.
In Organizational Management, the assignment terminates with message
CRM_CENTRAL_PERSON003
ID: CRM_CENTRAL_PERSON number: 003
"No central person is assigned to &1. ID &2"
The assignment of the relationship terminates with message R1829:
"Business partner &1 is not an employee"
If you create the same business partner online or if you change and save
the business partner created using the interface online, the assignment is possible.
Other terms
CRMXIF_PARTNER_SAVE, CRMXIF_PARTNER_REL_SAVE, PPOSA_CRM
Reason and Prerequisites
Up to now, the system does not u the XIF interface to update human
resource data for the employee role.
Solution
1.Workaround for the assignment to a sales organization:
In the business partner maintenance, edit and save the business partner. As
a result, the system updates the missing HR data.
2.Create and register the following module in the BDT time control.
FUNCTION z_bupa_create_central_person.
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" EXPORTING
*" REFERENCE(STATUS) TYPE SMWVALSTAT
*" CHANGING
*" REFERENCE(C_BP_STRUCT) TYPE BUS_EI_EXTERN
*" REFERENCE(ERROR_SEGMENTS) TYPE SMW_ERRTAB
*"----------------------------------------------------------------------
DATA:
lv_bp_is_employee TYPE char1,
lv_guid_raw16 TYPE bu_partner_guid,
lv_partner TYPE bu_partner.
status = 'S'.
* get PARTNER_NUMBER via GUID
CALL FUNCTION 'BAPI_BUPA_GET_NUMBERS'
EXPORTING
businesspartnerguid =
c_bp_struct-header-object_instance-bpartnerguid
IMPORTING
businesspartnerout = lv_partner.
CHECK NOT lv_partner IS INITIAL.
* check if partner is an employee
CALL FUNCTION 'CRM_BUPA_IF_CHECK_EMPLOYEE'
EXPORTING
iv_partner = lv_partner
IMPORTING
ev_bp_is_employee = lv_bp_is_employee.
CHECK NOT lv_bp_is_employee IS INITIAL.
lv_guid_raw16 = c_bp_struct-header-object_instance-bpartnerguid.
* check if central person already created or not
CALL FUNCTION 'CRM_CENTRALPERSON_GET'
EXPORTING
iv_bu_partner_guid = lv_guid_raw16
EXCEPTIONS
no_central_person = 1
error_message = 2
OTHERS = 3.
IF sy-subrc = 1.
* create central person
CALL FUNCTION 'CRM_BUPA_CREATECENTRALPERSON'
EXPORTING
iv_bu_partner_guid = lv_guid_raw16
iv_no_commit = 'X'
EXCEPTIONS
error_message = 0
OTHERS = 0.
ENDIF.
ENDFUNCTION.
In transaction CRMC_BUT_CALL_FU, register the module between the central and CRM-specific data update in the inbound (for example, item 100005). Up to Relea CRM 4.0
CRM inbound business partner 100000 BUPA_MWX_BDOC_MAP_MAIN_CENTRAL
CRM inbound business partner 100005 Z_BUPA_CREATE_CENTRAL_PERSON
CRM inbound business partner 200000 CRM_BUPA_BDOC_MAP_MAIN
As of CRM 5.0 you also have to take Note 757955 into account. U the report mentioned in this note to adjust the interface.
The item numbers are:
CRM business partner inbound 1000000 BUPA_INBOUND_MAIN_CENTRAL
CRM business partner inbound 1000005 Z_BUPA_CREATE_CENTRAL_PERSON
CRM business partner inbound 1100000 CRM_BUPA_INBOUND_MAIN_MD
Header Data
Relea Status:Relead for Customer
Relead on:02.10.2006 14:02:30
Master Language:German
Priority:Correction with low priority Category:Workaround for missing functionality Primary Component:CRM-MD-BP Business Partners
Valid Releas
Software Component Relea From
Relea To
Relea
and
Subquent
BBPCRM 3.0300300
BBPCRM 3.1310310X BBPCRM 4.0400400X BBPCRM 5.0500500X BBPCRM 5.1510510X BBPCRM 5.2520520X BBPCRM600600600X BBPCRM700700700X
Related Notes
Number Short Text
774662Enhancement of the business partner data exchanges
