Skip to Content
0

Customer Account Groups / Required Fields for BPs using CVI - Best Practices

Jul 25, 2017 at 03:53 PM

88

avatar image

Hi Gurus,

I am on a project with the 1610 build of S/4 Hana. I have determined that it is possible to drive different required fields for customers by either:

  1. Creating a different BP role, this will allow for customizing in Cross-Application Components->SAP Business Partner->Business Partner->Basic Settings->Field Groupings->Configure Field Attributes per BP Role
  2. Creating a different BP Grouping will allow a mapping to a different Customer Account Group through Cross-Application Components->Master Data Synchronization->Customer/Vendor Integration->Business Partner Settings->Settings for Customer Integration->Field Assignment for Customer Integration->Assign Keys->Define Number Range Assignment for Direction BP to Customer. (As per note 2314109)

My question is, in the ECC system, we had different account groups for sold-to, ship-to, bill-to and payer. Now, it seems that there is no standard setup in the S/4 1610 build to differentiate between these partners as different account groups. What is the best practice for creating these different customers? Would it be to create new Z-BP Roles, new Z-Groupings? Or is there something else that I have not yet considered?

I just seems odd to me that SAP would not have something for this delivered standard in the system, so I think that I may be missing something.

10 |10000 characters needed characters left characters exceeded
Former Member

Hi Graeme,

I have a similiar issue, but did not receive an answer from anyone yet.

https://answers.sap.com/questions/376049/s4-hana-possibility-to-control-field-status-based.html

Nevertheless, were you able to drive required fields for customers using account groups? In my case, the field group settings for business partner role overwrites whatever was customized at account group. Could you please share what you did?

Thanks,

Ankit

0
* Please Login or Register to Answer, Follow or Comment.

0 Answers