
***Examples/Data/Images this Blog is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.***
Hello SAP S/4HANA Cloud Community,
Introduction:
I work on the LO-MD-BP component for SAP S/4HANA Cloud and I have had several customers queries about how to maintain the Sales Partner Function CP Contact Person in Customer Master Data and how to determine the Contact Person ID via the CDS Views in SAP S/4HANA Cloud.
How to Create Contact Person in SAP S/4HANA Cloud:
To create a contact person which can be used as Partner Function you need to follow the following steps:
The contact person BP will be synchronized to contact person via CVI. The synchronization will create a record in table KNVP for the BP which is a contact person, this number will be different to the BP number. Then you can use the contact person number in other applications such as purchasing partner function etc, using the KNVP number.
To see the KNVP number, when adding the Contact Person as a CP Partner function press the F4 help button in the field for inputting the contact person number.
So you can enter the ID 51 for partner function CP. This is the contact person ID linked to contact BP ID 5000078.
This information is also mentioned in SAP Knowledge Base Article 2576618 - How to use a contact person in SAP S/4HANA.
How to Determine Contact Person ID and relationship between Contact Person ID and Contact BP ID via CDS Views?
As S/4HANA cloud migration does not support on assignment of contact person to customer BP, it is suggested to do mass maintenance after BP relationship is created by migration object Customer.
Therefore, it is required to get the contact person ID with its contact BP ID after Migration Object Customer is imported and before mass maintenance.
To achieve this and determine the relationship between Contact Person ID and Contact BP ID, a custom CDS View must be created based on released CDS Views.
ODATA Service API_BUSINESS_PARTNER for determining Contact Person ID
API_BUSINESS_PARTNER cannot be used to yet to determine the relationship Contact Person ID and Contact Person BP ID.
The below URI will not be helpful in this scenario as Partner Function information is stored in table KNVP whereas Contact Person information is stored in KNVK.
sap/opu/odata/sap/API_BUSINESS_PARTNER/A_CustomerSalesArea(Customer='1816',SalesOrganization='1710',DistributionChannel='10',Division='00')/to_PartnerFunction
URI: /sap/opu/odata/sap/API_BUSINESS_PARTNER/A_BusinessPartnerContact() will also not help as it will return only the Contact Person BP ID. It does not give us the ContactPerson and the Business Partner Link.
The result would something like this:
"RelationshipNumber" : "506",
"BusinessPartnerCompany" : "1000067",
"BusinessPartnerPerson" : "50000078",
"ValidityEndDate" : "\/Date(253402214400000)\/",
"ValidityStartDate" : "\/Date(1559606400000)\/",
"IsStandardRelationship" : false,
"RelationshipCategory" : "BUR001".
However, Business Partner Person (Contact Person BP ID) cannot be passed via API or maintained manually in App Maintain Business Partner as system expects the Contact Person ID.
Therefore, we can conclude that we can determine Contact Person ID either by using F4 help in App Maintain Business Partner or via CDS Views.
Best Regards,
Varun
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
2 | |
2 | |
2 |