SAP BLOG Business Partner with Company Code and Sales/ Purchasing view

Motivation​

SAP delivers in standard roles the split of Company Code Data and Sales/ Purchasing data roles.




That separation ensures that you can create a BP in Finance and in Sales/ Purchasing separately – which kind of works like old way split between FK01/FD01 in Finance and VD01 / MK01 in Sales/ Purchasing.

As you see there is no straightforward BP Role which enables you to create both Finance and Sales/ Purchasing at one go.

In the past the split was due to separation of applications and connection between Vendor and Customer maintained only in form of a Partner number in master data. Nowadays they share much more. You may wonder how to replicate functionality of XK01/ XD01 with proper segregation of duties.This blog will help you understand how you can influence the visibility of BP options using standard customizing.

BP View​

In BP Roles customizing:


you can see in settings of each role a BP View is assigned:

BP View in BP Role – FLCU00​

BP View is what controls availability of fields that can be configured for visibility for a BP Role.

BP View can be maintained using BUSD Transaction:

BUSD BP View maintanance​

There are 3 most important settings made for a BP View.

1. Data Sets
2. Calling Applications
3. Screen sequences

Data Sets are assigned to ‘Views’ defined in BUS3 transaction – to userstand the naming of BP screen objects have a look at the excellent blog of Andi Mauersberger with introduction to BDT.

Calling Applications are kind of another grouping of Views that help in easy control of active components of BP.

Screen sequences define the buttons which you can see in BP:

BP View Buttons on BP​

Having learned about that lets check how standard BP roles are defined:

BP View Data Sets​

The CVIC* or CVIV* Sets are assigned – they control the CVI Settings for Customer and Vendor.

The buttons visible above – Company Code/ Sales and Distribution are controlled by Subheaders Id:

BUSD Subheader Ids​

Here you can control which buttons are available for each BP Role.

The Screen Sequences control correct processing of the screen buttons:

BUSD Screen Sequence​

Create new BP View​

BP Views do not need any development and are easy to create. You can assign them to custom roles.

Lets create a new BP View that allows both Company and Sales Area data maintanance.

Start from copying existing view FLCU00 and create your own Z* view:

BUSD – Copy BP View​

All related-entries will be copied as well. Now go to the other role FLCU01 and copy the content of:

Data Sets

Calling Applications

Screen Sequence

Subheader ID

Do not copy the Views part.

At the end in your new role you should have:

BUSD New Screen Sequences​

BUSD New Screen Subheader​

Make sure all data sets are copied from the other role – they controll the visible fields!

Assign new BP View to Role​

BP Views are assigned to BP Roles in customizing:




Copy the existing role FLCU00 to your custom one and assign newly cleared BP View:

New BP Role with Full View​

Create also the BP Role Category with the same name.

Check BP Transaction with new role​

Once customizing is done check in BP transaction if your new role is available and you are able to see all buttons:

BP New role with FI SD view​

Now you can centrall create customer with all views like in XD01.

Segregation of Duties (SOD)​

The separation between Finance and Sales view was not introduced in SAP just becasue it is nice – it also covers an aspect of segregation of duties.

When the views are combined you still need to make sure that user rights are respected. You may want to make sure that Sales Persons do not have view to Finance and the other way around.

Removing the clear BP role separation you need to apply a different way. Fortunatelly the way can be handled via authorizations to Field Groups.

In BP you are able to control authorization by meaning of every field group.

At first define which fields should be contolled via authorizations:


Pick up these field groups (defined in BUS2) which are relevant for restiction – for example these are the fields available for customer in company code data:

BP Field Group Authorization​

Once entered in customizing, you can controll them in role definition by authorization object B_BUPA_FDG:

PFCG B_BUPA_FDG Customizing​

Afterwards system applies the authorization check on each field and secures that only certain data can be edited.

This supports the standard authorization objects for customers/ vendors which anyway allow to restrict if Financial Accounting or Sales or Purchase data can be edited (like object F_KNA1_APP).



Thank you for reading,

Marek Turczyński

First part of Business Partner Blog series: Custom BP Relationship Category and KNVK synchronization

Okumaya devam et...