The advantages are:

the organizational model is more user-friendly

in case of specific development, the technical consultant has a direct mapping

between business partner ID and organizational unit ID

if you transport the organizational model from Development system to Quality &
Production system, you'll have the same IDs between all systems: its a behavior
closer to customizing than to master data. It's more consulting-friendly.

improvement of reliability of transport the organizational model with program

RHMOVE30

4/ Synchronize the ID of business partner and organizational unit

Customizing path: SPRO > Customer Relationship Management > Master data > Integration
Business Partner Organization Management > Set-up integration with organizational
management

Group

Sem. Abbr.

Value
Abbr.

Description

HRALX

OADBP

Business Partner of
Standard Address

HRALX

OADRE

Address Necessary
for Business
Partner?

HRALX

OBPON

ON

Integration O-BP
Activated

HRALX

OBWIG

Ignore Business
Partner Warnings

Remark

Yes, we want the

integration

HRALX

ONUMB

HRALX

OSUBG

Z0

The value 3 means the

ID of business partner
is the same than
organizational unit
Business Partner
Subgroup
(Organizational
Unit)

This is the business

partner range number