You created an Organizational unit XYZ, where you added role Company. In this case, the system created an Associated Business Partner which is Account XYZ. Thereafter, in test-productive transport, Organizational Unit XYZ was marked as not Company, and in this case Account XYZ was marked to Obsolete. If you marked Organizational Unit XYZ as a Company again, the system creates new Account YYYYY instead of marking XYZ Account to Active status.
where XYZ represents the Organizational Unit and the Account ID
YYYYY represents the Account ID
SAP Cloud for Customer
Reproducing the Issue
- Go to Organizational Management work center
- Go to Org Structures view
- Search the Org Unit XYZ
- View the Org Unit
- In the Header section, the Associated Business Partner is YYYYY instead of XYZ
For the example in scenario, the situation of Organizational Unit XYZ and Account XYZ in the system may be as follows:
On DD1.MM1.YYYY1 HH1:MM1:SS1 the Account XYZ was created.
On DD2.MM2.YYYY2 HH2:MM2:SS2 the Account XYZ was set to status Obsolete.
On DD3.MM3.YYYY3 HH3:MM3:SS3 the Organizational Unit XYZ was created.
On DD4.MM4.YYYY4 HH4:MM4:SS4 the Company indicator for Organizational Unit XYZ was set.
The company indicator for Organizational Unit XYZ was not changed since then.
When an Organizational Unit is turned into a Company, but an Account with a matching Internal ID already exists the program logic has to assume this Account is unrelated to the Organizational Unit since it has been created prior. Hence in this case (and only this case) the Account gets an Internal ID drawn from the Internal Number Range. Otherwise, when the Company indicator is reverted (and subsequently set) for an Organizational Unit this should not change the related Account.
Organizational Unit, Company, Associated Business Partner, Account, Active , KBA , LOD-LE-BP-BP , Business Partner , Problem