SRM 5.0 Exception E:BBP_BUPA:034 -Organizational unit in SUS

[Former Member]

Hello,

We are in process of upgrade srm 4.0 to srm 5.0 , as configured Plan driven procuremnet with supplier enablement scenario . Connected R/3 (46 c) to SUS using PI 7.0 . But stuck in problem as no new vendor replicated in sus from R/3. XML message processing shows error at SUS system ie ..

"An error occured within an XI interface: Exception occurredE:BBP_BUPA:034 -Organizational unit 50000001 does not exist; check entries Programm:"

while successfully updated existing( working with srm 4.0 since last two years) vendors from same system ,

pls advise.

Regards,

Santosh

I am came across the organization plan change for srm 5.0. Want to be clarify that is it also applicable for SUS organization for vendors.

report BBP_XPRA_ORGEH_TO_VENDOR_GROUP

can any one light on it.

Message was edited by:

Santosh Patil

[Former Member]

Hello Atul,

Thanks for detailed information , I have executed this report with mode all 2 level nodes are org unit option

Find result entry in bbp_marktp_info table changed and two new vendor groups

generated one of them starts with name "atul"

But find some vendors are missing in newly created vendor groups .

As well I have created new vendor group under root node but unable to assign

replicated vendor to new_vendor group. newvendor _group has been maintained with some custom attributes .

so stuck in this.

Regards,

Santosh

[Former Member]

Hi,

Pls see if the foll notes are useful :

Note 928881 - BBP_XPRA_ORGEH_TO_VENDOR_GROUP: Problem w/ check mode 9 (2)

917536 BBP_XPRA_ORGEH_TO_VENDOR_GROUP: Problem with check mode 9

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Thanks Disha for your inputs as I have already executed this report with mode "3" and completed can we reschedule same report with mode "9 ?

Can you pls brief me diff between mode "9" and mode "3" as read a lot document but can't reach to conclusion.

Queries

1) Earlier version we use to maintain attribute at vendor level so as per conversion

result now I have created new vendor group and attached custom attribute but unable to assign vendor to it . Though I selected business partner of vendor it shows error mesage

"Business partner is not a vendor" system could not perform changes.

Regards,

Santosh

[Former Member]

Hi

<u>Please read this carefully -></u>

See the following SAP OSS Notes as well ->

Note 957851 SRMSUS: Modification in usermanagement for CUA replication

Note 792364 SRM50/SUS/BP: Conversion of SUS business partner

Note 628547 SRM-SUS: Corrections for SUS 2.0 SP01: business partner,user

<b>Report BBP_XPRA_ORGEH_TO_VENDOR_GROUP</b>

<u>[Convert Org. Units to Vendor Groups ]</u>

<b>Mode details</b>

Mode                 Short text                                                                                
0    Do not carry out structure checks                            
1    Business partner exists for root org.                        
2    Partner for root org. (only) has org. unit role              
3    All level 2 nodes are org. units                             
4    All level 2 nodes have business partners                     
5    All level 2 nodes have (only) org. unit role                 
6    All level 3 nodes are org. units                             
7    All level 3 nodes have business partners                     
8    All partners (level 3) has (at least) org.unit + bidder role 
9    All level 4 nodes are positions 

<b>Purpose of this report</b>

This report converts the HR organizational model for external business partners (bidders, vendors, and their employees).

You have to run this report after an upgrade from BBP 2.0C, EBP 3.0, EBP 3.5, EBP 4.0 and SRM Server 5.0 for every root organizational unit of these external business partners (if you have several such root unit, you have to run the report several times).

This report does not run across clients, so you have to start it separately in every client that you have.


The conversion is required because, in the new HR organizational model, external objects can no longer be stored as object 'O' (=organizational unit); consequently, it is no longer possible to create positions for external objects.


This has the following effects for external business partners who are stored in the organizational model:

The old root object, the 'Central Organizational Unit for Vendors' will in future not be an organizational unit, but rather an organizational object of the type 'VG' (=vendor group)
The interim nodes that were created for reasons of system performance (each containing 100 vendors/bidders) will in future not be an organizational unit, but rather an organizational object of the type 'VG' (=vendor group)
The external business partners of the type Organization (bidders, vendors) are no longer represented by a separate organizational object (in other words, there is no longer an organizational object that has the identity relationship to the partner)
Since the org. object that previously represented the partners is missing, the business partners are now linked directly with the interim nodes (previously, the organizational unit for the partner, and not the partner itself, was linked)
If a business partner has a set of attributes that is different to the attribute values specified for the interim node, the partner in question is not linked directly to the interim node, but rather to another 'VG' object (which has the attributes of the partner), which in turn is linked to the interim node.
Previously, if an external business partner had an employee and this employee has a user in the system, the employee staffed the position in the organizational unit that represented the partner. However, since this organizational unit no longer exists, the position and the staffing relationship no longer exist either. This means, among other things, that there is no reporting option in HR that enables you to navigate from a user to the business partner of the user's company.
Since there is currently no way of directly assigning a user to a business partner (of the type Person), the organizational object 'CP' (=Central Person) is still used to establish this link.

Once the conversion report has run successfully, you will no longer be able to see the organizational structure of the external business partners by calling transaction PPOSA_BBP (or PPOMA_BBP).

However, a new transaction called PPOMV_BBP is available instead. You can use this transaction to display the converted (and newly generated) structure for bidders/vendors.

Prerequisites
Before you actually convert your organizational structure, you should let the report check the structure, and correct any errors that the report detects.

Features
The report has the following features:

A 'Check Only' mode is available, which you can use to check the consistency of the organizational structure of the external business partners at different levels
The report can be restarted. This means if the conversion is canceled due to errors or system problems, and you restart the report, it will recognize any new objects that have already been generated, thus ensuring that structure elements that have already been processed are not converted a second time (this is achieved by evaluating at runtime the log tables BBP_O_TO_VG_OBJ (for generated objects) and BBP_O_TO_VG_REL (for generated relationships)).
If you use table BBP_MARKETP_INFO to store the root organizational units, the report changes the old entries accordingly.
The report writes an application log (log object BBP_XPRA_O_TO_VG) in which messages are logged at two different levels; alternatively, you can request that the message be output directly ('WRITE', for background spool lists).
Although we do not recommend that you do this (because it can result in very long response times), you can run the report in parallel and thus convert several root organizational units at the same time.

Activities
Start the report for every 'Central Organizational Unit for Vendors' (root organizational units for external business partners) in every client that you use.

Annotations
We recommend that you do not use the 'Direct Message Output' option (that is, the option where an application log is not written) in conjunction with the 'Detailed Message Output' option for larger organizational structures, because every object and relationship that is generated will be output, and you will not feasibly be able to process this list.

Even if you use it in conjunction with the writing of an application log, the 'Detailed Message Output' option rarely makes sense if you have tens or hundreds of thousands of vendors/bidders.

Estimated work/expenditure necessary
The runtime for this report depends on the hardware, system load, and structure involved (for example, the number of vendors/bidders who have employees and users and, therefore, also positions, the number of vendors who have attributes different than those of the interim node, and so on).

As a rule of thumb, though, structures with vendors where 10% of users have their own individual attributes are processed at the rate of approximately 25,000 per hour.

Remember, however, that the time required depends to a large degree on the number of nodes where local attributes have been defined, and on the number of business partners who have users.

This can lead to situations where an organizational structure with 100,000 nodes but no local attributes or users can be converted more quickly that a structure with only 5,000 nodes but with local attributes and assigned users.

Hope this will help.

Regards

- Atul

[Former Member]

Hi Atul,

Thanks for sharing detailed information. actually after execution of report "BBP_XPRA_ORGEH_TO_VENDOR_GROUP" I have replicated Vendor A05763 from R/3 to SUS shown BP 0000002432 bydefault it is assigned to VG- 50003534 .

In srm 4.0 we used to attach cutom attributes to position of vendor in org unit.

To meet same in srm 5.0. I have created another VG - 50003537 and assigned custom attributes to that.

Now when I try to assign existing vendor to this node not able to assign this eg. tried with assigning BP 0000001772 to newly created VG 50003537 below messages appear for existing vendors from srm 4.0

Object cannot be assigned to object Transporter

in the period 03.06.2003 - 31.12.9999

And for newly replicated vendors message appears like

Business partner is not a vendor

Caution: system could not perform all data changes

Regards,

Santosh

[Former Member]

Hi

Seems to be a bug.

Please raise a Customer OSS Message with SAP at the earliest.

Do update me as well.

Regards

- Atul

[Former Member]

Hi,

I am currently in SRM upgrade from SRM 3.0 to SRM 7.0.

i am executing the report : BBP_XPRA_ORGEH_TO_VENDOR_GROUP

how to select Check node ..which check node to select..

what is the selection criteria . We are in SRM 3.0

if you are executing one check node say 1whether we ccan run the report again and select 2 and execute

Regards

G.Ganesh Kumar

[Former Member]

Hi Atul,

We are doing SRM upgrade from SRM 3.0 to SRM 7.0.

I am running the above report :BBP_XPRA_ORGEH_TO_VENDOR_GROUP

I am getting an error 2 error

1) Check mode 9 invalid objects on supplier node

Structure must be corrected /repaired manually.

2) check mode 7: nodes bewlo intermeditae mode have no partners assigned

how to solve the above error

There is two sap notes:917536 & 928881

whether we have to apply these notes on SRM 7.0 Development server

Please give us solution on how to proceed

Regards

G.Ganesh Kumar

[Former Member]

Hi,

In SRM5.0 the vendorgroups are in transaction ppomv_bbp and not anymore in the ppoma_bbp. Also the report 'bbp_xpra_orgeh_to_vendor_group' needs to be executed executed after an upgrade.

Extract from help.com:

<b>BBP_XPRA_ORGEH_

TO_VENDOR_GROUP -->This report deletes all organizational units and organizational plans of the vendor from the internal organizational plan (transaction PPOMA_BBP) and groups these according to their attributes in new organizational objects (transaction PPOMV_BBP).

Vendor groups (VG) are used for grouping; it is no longer obligatory to have one VG per vendor, as was previously the case for organizational units. If several vendors (who previously were assigned to an organizational unit) have identical attributes, they are now assigned directly to a common VG.

After an upgrade to SRM 5.0, you must run this report in each client for each central organizational unit for vendors ("root organizational unit"). This applies both to EBP (SAP Enterprise Buyer) and to SUS (SAP Supplier Self-Services) systems.</b>

After executing the report you can use following reports:

- BBP_VENDOR_UPDATE_DATA_JOB for updating existing vendors

- BBP_VENDOR_GET_DATA_JOB for replicating new vendors.

BR,

Disha.

Pls reward points for useful answers.

[Former Member]

Hi

<b>Please go through the following links, which will definitely help -></b>

Note 917536 - BBP_XPRA_ORGEH_TO_VENDOR_GROUP: Problem with check mode 9

Note 928881 - BBP_XPRA_ORGEH_TO_VENDOR_GROUP: Problem w/ check mode 9 (2)

Note 723610 - SUS 3.0: Portal Integration doesn't work

Note 880735 - UME/SUS: error with administrational user creation

Do let me know.

Regards

- Atul