Kontakt

Ansicht
Dokumentation

BBP_XPRA_ORGEH_TO_VENDOR_GROUP - Convert Organizational Units to 'Supplier Groups'

BBP_XPRA_ORGEH_TO_VENDOR_GROUP - Convert Organizational Units to 'Supplier Groups'

PERFORM Short Reference   PERFORM Short Reference  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

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.






TXBHW - Original Tax Base Amount in Local Currency   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 6874 Date: 20240601 Time: 011127     sap01-206 ( 128 ms )