Reference Objects

You can assign objects to which a quality issue refers (such as materials, batches, vendors, delivery items) as reference objects. Technically, the reference objects can be located in other systems.

Integration

You can open the reference objects in the source system via links from the QIM system.

For information about how the technical integration is implemented, see Technical System Integration.

Features

Delivered Reference Objects

In the standard system, object types and object categories are delivered for numerous types of reference objects. The object type describes an entity in general (for example, material); the object category describes the origin more exactly (for example, material in ERP or material/product in SAP NetWeaver). For some object types, there are several object categories for different release levels of the system in which the object is available (for example, maintenance notification).

You can find out which object types and object categories are available for reference objects in Customizing for QIM under Start of the navigation path Basic Settings Next navigation step Generic Settings for Reference Objects End of the navigation path .

General Reference Objects

One notable case is the delivered External reference object (object type GOJ) that is intended for flexible use because it does not have a technical equivalent in another system. It is based on the BOL component IAMGOJ for the business object GeneralObject. This BOL component can also be used as the basis for other reference objects. For example, it is the basis for another delivered object type Storage location (STL).

All reference objects that are based on the BOL component IAMGOJ have the following special features:

The reference to the object in another system only means that you can search for this object in the external system. For this purpose, you can define your own search help in the external system if required and assign it in Customizing for the object type. However, this type of search help has the constraint that you can only search for the technical name and description (or for a combination of two technical names as with the reference object storage location).
In the QIM Web application, you cannot jump to the respective object in another system.
If you create your own reference objects on the basis of IAMGOJ, you do not need to create your own BAdI definition; you can copy the enhancement implementation /IAM/ACCESS_GENERALOBJECT_NW for the delivered BAdI /IAM/BADI_GENERALOBJECT_CAT. In the copied enhancement implementation, you can reuse the delivered BAdI implementation /IAM/ACCESS_ERP_GENERALOBJECT with another filter value.

Navigation and Jumps

From the QIM user interface, you can navigate to the assigned reference objects in the remote systems. Note, however, the following features for some delivered reference objects:

If reference objects are located in an older system that does not support the display of Web applications (for example, SAP R/3 4.6C) and you are working with SAP NetWeaver Business Client for HTML, only restricted navigation is possible in the source system. For example, you cannot jump to other applications.
For products (object category Material in NW, MAT_NW), only restricted navigation is possible in the source system for each release level for technical reasons.
Retail articles and product groups are handled as ERP materials and belong to the object category MAT_ERP, that is, the data is displayed via the material master display (transaction MM03).
No jump is supported for the following object categories:
- External reference object (GOJ_NW)
- Plant (PLANT_ERP)

Activities

Entering Systems for Reference Objects

In Customizing for QIM, you specify in which systems the reference objects are located (under Start of the navigation path Basic Settings Next navigation step Generic Settings for Reference Objects Define Object Access End of the navigation path ). An easier means of maintaining object access is provided by a wizard, which you can find in Customizing for QIM under Start QIM Customizing Wizards .

Note Note

The user that is stored in the RFC connection for the source system must have authorization to access the required object in the source system. In addition to object-specific authorizations, the underlying RFCs must be stored in the authorization object S_RFC. For information about which RFCs are relevant for which object, see the Customizing activity for object access in the settings for the object category under (Implementation Information).

End of the note.

Defining Other Reference Objects

For more information about how you define additional reference objects, see SAP Note 1820834.