Documente Academic
Documente Profesional
Documente Cultură
Q UICK G UIDE :
A UTHOR :
J OHAN H OLIERHOEK
D ATE : 16-3-2016
Contents
CONCEPT .................................................................................................................... 2
CUSTOMIZING ............................................................................................................ 4
SELECT THE RELEVANT ROLES ............................................................................................. 4
ASSIGN THE NUMBER RANGE BP (ONE NO. RANGE SCENARIO BP AND CUST,/VEND,) ............................. 5
Define Number Ranges ............................................................................................. 5
Define Groupings and Assign Number Ranges .............................................................. 5
SET THE NUMBER RANGES FOR CUSTOMERS (ONE NO. RANGE SCENARIO BP AND CUST,/VEND,) ................ 5
SET THE NUMBER RANGES FOR VENDORS (ONE NO. RANGE SCENARIO BP AND CUST,/VEND,) ................... 6
CUSTOMER VENDOR INTEGRATION (CVI) CUSTOMIZING .............................................................. 6
Synchronization Objects ........................................................................................... 6
PPO activation ......................................................................................................... 6
Activate Synchronization Options ............................................................................... 7
Establish Recipient of Postprocessing Messages (optional) ............................................. 7
Set BP Role Category for Direction BP to Customer ...................................................... 8
Define BP Role for Direction Customer to BP ................................................................ 9
Define Number Assignment for Direction BP to Customer .............................................. 9
Define Number Assignment for Direction Customer to BP ............................................. 10
Set BP Role Category for Direction BP to Vendor ......................................................... 10
Define BP Role for Direction Vendor to BP .................................................................. 11
Define Number Assignment for Direction BP to Vendor................................................. 11
Define Number Assignment for Direction Vendor to BP................................................. 12
FIELD SETTINGS BP (THE BP WILL BE LEADING) ...................................................................... 12
Configure Field Attributes per BP Role ....................................................................... 12
MAINTAIN TAX NUMBER CATEGORIES ................................................................................... 14
Change the message control from warning to error ..................................................... 15
M EER ENDON KWEG 11 5216 TZ ` S - HERTOG ENBOSCH POSTBUS 773 5201 AT ` S - HER TOG ENBO SCH
T . +31 (0)73 692 06 92 F . +31 (0)73 692 06 88 E . INF O @ CTAC . NL I . WWW . C TAC . NL
CONCEPT
Business partner
structures
Patient
Loan
recipient
Employee
Creditor
SAP
Business
Partner
Tenant
Vendor
Customer
Debitor
neutral
persons and organizations
cross-application
open infrastructure
integration through
business concepts
Plant
A SAP Business Partner is an Organization (firm, branch office), person or a group of persons or organizations in which your company has a business interest.
You can create and manage your business partners centrally for different business transactions.
This is of prime interest if a business partner plays different roles for a company, such as sold-to party and
ship-to party.
You can create a business partner in different business partner roles. During the course of the business relationship, the business partner can also get other business partner roles. You do not need to create the general data, which is independent of a business partners function, again for this business partner. You just add
a Role which will contain the relevant information. This prevents data being created and stored redundantly.
A Business partner consists of general data (Name, address, bank information etc.) and Role specific information (e.g. customer / vendor / employee / etc.). these roles are linked to other parts within SAP. When a
BP has the role customer the link with the customer / sales sub administration and the general ledger is mandatory. On creation the relevant fields for and links to these areas are made.
P AGE 2
OF
17
It is advised is to implement the BP functionality for new implementations where the BP will be leading regarding the numbering of the customers and vendors (this means the customer and vendor will have the
same number range) . With upgrades up to the 1503 release the BP functionality can be implemented but is
not needed. As from the 1511 release the HANA core the BP is mandatory and the old FD01/02/03 and
FK01/02/03 will not be available anymore. The BP is the only way to create the customers and vendors. In
this case the customer needs to decide how to deal with the number ranges.
The options are:
harmonizing the two (e.g. the customer number range will remain the same and the vendors will be
migrated to the main customer number range. After this has been done the BPs can be generated
using the same numbers)
o Disadvantage: you lose the history of your vendors (the data is divided over two numbers)
You do not have to migrate the vendors to a new number range.
o Advantage: when you start to use e.g. FSCM collection management or CRM, which uses
the BP number, you will have no confusion regarding the number you are referring to.
keep using the numbers and link them to the BP which will have a whole new number range.
o Disadvantage: when you start to use e.g. FSCM collection management or CRM, which
uses the BP number, you will have confusion regarding the number you are referring to
o Advantage: you do not lose the history of your vendors
You do not have to migrate the vendors to a new number range
P AGE 3
OF
17
CUSTOMIZING
S ELECT
IMG Cross-Application Components SAP Business Partner Business Partner Basic Settings
Business Partner Roles Define BP Roles
Hide the roles which are not relevant. This prevents a wrong selection by the users.
T-Code BP
P AGE 4
OF
17
A SSIGN THE
CUST ,/ VEND ,)
NUMBER
RANGE
BP ( ONE
NO .
RANGE
SCENARIO
BP
AND
S ET
( ONE
NO . RANGE SCENARIO
BP
AND
CUST ,/ VEND ,)
T-code: XDN1
The Customer number ranges in FI are external. The BP will determine the number.
The number range of the customer and vendor are equal. Reason the BP is leading and that number can be
a customer or vendor
P AGE 5
OF
17
S ET
CUST ,/ VEND ,)
( ONE
NO . RANGE SCENARIO
BP
AND
T-code: XKN1
The Vendor number ranges in FI are external. The BP will determine the number.
The number range of the customer and vendor are equal. Reason the BP is leading and that number can be
a customer or vendor
C USTOMER V ENDOR
INTEGRATION
(CVI)
CUSTOMIZING
SYNCHRONIZATION OBJECTS
IMG Cross-Application Components Master Data Synchronization Synchronization Control Synchronization Control Synchronization Objects
Synchronization
Object
BP
CUSTOMER
VENDOR
Synchronization Mode
1
1
1
Extractor Class
CVI_BP_EXTRACTOR
CMD_EI_API_EXTRACT
VMD_EI_API_EXTRACT
Description
Business Partner
Customer
Vendor
Platform Object
X
Block
Size
50
50
50
PPO ACTIVATION
P AGE 6
OF
17
IMG Cross-Application Components Master Data Synchronization Synchronization Control Synchronization Control Activate PPO Requests for Platform Objects in the Dialog
Synchronization Object
BP
PPO Active
X
P AGE 7
OF
17
The business processes for which you can use the Postprocessing Office are contained in the Business Processes (/SAPPO/S_BPROC) system table.
Below you will find the Processes for Business partner integration
P AGE 8
OF
17
The FLCU00 is the role for the FI part of the customer data
The FLCU01 is the role for the SD part of the customer data
Here the link between the BP roles and the FI customer group is defined
P AGE 9
OF
17
P AGE 10
OF
17
The FLVN00 is the role for the FI part of the vendor data
The FLVN01 is the role for the MM part of the vendor data
P AGE 11
OF
17
F IELD
SETTINGS
BP ( THE BP
WILL BE LEADING )
Since the BP is leading you should not change the screen layout of the account groups in FI.
However when you change the screen layout of the account groups in FI you need to make sure
that these settings will match with the field settings in BP. If they do not match you will have
problems when saving the BP. (e.g. you make a field mandatory in FI but not in the BP. When
saving the BP the changes will not be saved if the mandatory filed is not filled. When there are
issues you can find a detailed error log in transaction MDS_PPO2 (Post Processing Office)
OF
17
Hide field groups completely (when you hide all fields within a group)
Hide Tab pages completely (when you hide all fields within all groups on a tab page)
E.G you want to hide the following fields in tab page [customer: additional data]
Select the relevant role in which you want to change the field attributes
P AGE 13
OF
17
IMG Cross-Application Components SAP Business Partner Business Partner Basic Settings Tax Numbers Maintain Tax Number Categories
Here the default settings regarding the Tax numbers of the different countries are maintained.
You can also (de-)activate the duplicate check.
P AGE 14
OF
17
This setting will activate the check on duplicate Tax numbers. The message will be a warning.
The next chapter describes how to change the message type from warning to error.
P AGE 15
OF
17
add following entry to set an error for the message 'BUPA_TAX 400':
P AGE 16
OF
17
P AGE 17
OF
17