Replication of Equipment: Prerequisites and General Informat
Replicating Equipment from SAP ERP into SAP Customer Relationship Management (SAP CRM)
This document describes the replication of equipment from SAP ERP into SAP CRM. This means that the pieces of equipment from SAP ERP are represented as objects of an installed base in SAP CRM. If the equipment has an underlying structure, this structure is represented as a hierarchy in the installed base. In addition, it is possible to activate an upload function that transfers changes from SAP CRM to SAP ERP.
Note:
- In the same way as for the equipment download, serial numbers can also be replicated from SAP ERP. For more information, see SAP Note 627279.
- Note that activating the equipment download automatically deactivates the Mobile Bridge for the Equipment R/3 Edition.
Requirements
- You activate the download function by activating the implementation of BAdI Creation of Objects by Equipment Download CRM_EQUI_LOAD.
- For the upload, you must also activate adapter objects DNL_EQUIPMENT and DNL_EQUI_HIER in transaction R3AC1.
- The DNL_EQUIPMENT adapter object is responsible for uploading changes to the
master data of the object.
- Adapter object DNL_EQUI_HIER serves to upload structure changes. If you do
not want to upload structure changes, you can leave the DNL_EQUI_HIER adapter
object inactive, in which case only master data changes to the object will be
transferred to SAP ERP.
- For the upload, you must also specify the SAP ERP system to which the data is to be sent. You can do so in the administration console (transaction SMOEAC) by creating a subscription for the publication Installed Base (MESG) and then assigning it to the corresponding site.
- Materials and business partners are downloaded from SAP ERP into SAP CRM.
- You have defined standard settings for replication in Customizing for Customer Relationship Management under Master Data -> Installed Base -> Replication of Technical Objects from SAP ERP.
- For the assignment of material to equipment to appear properly following replication, you have made the following settings:
- You have allowed product references for objects. You can do so in Customizing for Cross-Application Components under SAP Product -> Basic Settings -> Allow Product References for Individual Objects.
- On the CRM WebClient UI, on the Product Hierarchy page, you have assigned relationship type PROREF to the product categories for equipment or for functional locations.
Scope of Functionality
A two-way data transfer from SAP ERP to SAP CRM and back is supported:- Initial load
The initial load transfers the first data. It can repeated as often as required and overwrites the existing data in SAP CRM.
- Permanent load
The permanent load permanently transfers the newly created equipment from SAP ERP to SAP CRM (usually takes place after the initial load).
- SAP ERP is the leading system for creation of new equipment. In other words, creating new objects in the corresponding object family in SAP CRM does not lead to the creation of new equipment in SAP ERP.
Flow Logic of the Flow
The middleware flow is used to transfer equipment from SAP ERP to SAP CRM. As a result, specific determining factors and a defined process flow are predetermined.The process flow is as follows:
- The equipment BDoc is validated in the CRM validation module CRM_DEQUI_VAL.
- From there the BDoc switches to equipment/installed base handling, which runs through the following steps:
- Initial and permanent replication
- Mapping equipment to objects
The pieces of equipment from SAP ERP are created as objects in the SAP CRM system. The equipment attributes are transferred to the attributes of the set types of the objects.
- Connection to an installed base
If there is no superordinate piece of equipment, an installed base is created in SAP CRM. The piece of equipment is inserted in the installed base as an object.
If there a superordinate piece of equipment ( equipment hierarchy), it is inserted as an object below the existing object in an existing installed base. If an installed base hierarchy that was created like this is changed in SAP CRM by adding additional components of any type, and if an object corresponding to the equipment is moved under one of these components that was generated in SAP CRM (and therefore only exists in SAP CRM), at upload, the link that exists in SAP ERP to a higher-level piece of equipment is broken, if the DNL_EQUI_HIER adapter object is activated. When another change is made to this piece of equipment in SAP ERP, this piece of equipment is not moved to a separate installed base. Instead, it stays under the component that was generated manually in SAP CRM. From SAP ERP's perspective, this component that was added manually functions as a break in the equipment hierarchy, because this component does not correspond to any of the higher-level pieces of equipment.
- Connection to an installed base component
Since objects are components of an installed base, an installed base component is created for the object. Both objects are linked to one another so that the installed base components point to the object.
If there are partners for the equipment, these partners are assigned to the installed base component, as long as there is no partner determination procedure assigned to the object category. If there is an address for the piece of equipment, the address is assigned to the object.
- Restructuring objects
A check is made to see whether any subordinate equipment exists in SAP CRM for the equipment already linked (since the data forwarded by the middleware is not serialized, this is quite possible). If this is the case, the components of the subordinate pieces of equipment are moved to the installed base for the superordinate equipment. If this leads to empty installed bases because the installed bases were only used as containers until the upper-level equipment was replicated, the status of these installed bases is set to Delete.
- Permanent upload
- Structure changes to the installed base hierarchy are transferred into SAP ERP, provided these changes affect the direct links of the objects. Changes to data in the objects is transferred in the corresponding field of the equipment.
Storage as an Object
In the standard system, SAP ERP pieces of equipment are created as objects of the EQUIPMENT (0401) object family in the category 'Equipment' (0401). The attributes are mapped in the following set types:COM_TA_R3_ID - R/3 Identification
| Attribute | Description |
|---|---|
| TAR3_ID | Technical Asset Number |
| TAR3_STRUCTURE_CODE | Structure Indicator |
| TAR3_CATEGORY | Category of Technical Asset |
| TAR3_TYPE | Type of Technical Asset |
| R3MATERIAL_ID | Material |
| R3SERIAL_NO | Serial Number |
| R3BATCH_ID | Master Batch DEF |
| Attribute | Description |
|---|---|
| MANUFACTURER_ID | Manufacturer |
| MANUFACT_COUNTRY | Country of Manufacture |
| MANUFACT_REGION | Manufacturer Region |
| MANUFACT_MODEL | Model Description |
| MANUFACT_PART | Manufacturer Part Number |
| MANUFACT_SERIALNO | Manufacturer Serial Number |
| CONSTRUCTION_DATE | Date of Manufacture |
Two types of long texts are supported in equipment, and they are replicated in the following long text types for objects:
- Long text (LGTXT) -> Basic text (BASIC)
- Internal note (INTV) -> Internal comment (INTC)
Ensure that the Customizing settings are maintained for the available text types for product type Material in transaction SPRO.
COM_LOCAT_ADDR - Address
The mailing address and communication data for telephone and fax is transferred as the location of the object. Address inheritance is not supported in SAP CRM.
Mapping the System Status
Download is supported for the following system statuses of pieces of equipment. In all cases, the status is recorded in the object.- Available
- In the warehouse
- Assigned in delivery note
- At customer site
Mapping Business Partners
You can either map the business partners of the equipment to the object as a relationship, or to the corresponding installed base component as a business partner. If no other settings are made, the program tries to write the business partners to the corresponding installed base component. You must assign a partner determination procedure to the appropriate object category in order to store business partners as a relationship to the object. You can make the settings for this purpose in the transaction COMM_HIERARCHY.To avoid errors during mapping, you should ensure that the respective partner determination procedures conform either to the installed base or to the object category, with the partner functions of the equipment in SAP ERP.
See SAP Note 637173 for more information about mapping set types and business partners in the case of a delta synchronization.
Identification of the Objects and Meaning of the Logical System
The logical object key in SAP CRM consists of:- Object identification: OLTP equipment nummer
- Object family: 0401 (can be influenced by the Business Add-In)
- Logical system: OLTP system (can be influenced by the Business Add-In)
- Description (short texts)
- Long texts
- Set types
- Relationships
You can choose between OLTP and CRM when establishing the logical system of the attributes. In this way it is possible, for example, to create the object with the logical system OLTP, but the set types with the logical system CRM. Therefore in SAP CRM, the object is still an original object of the OLTP system, but its set types can still be changed in SAP CRM.
In the standard system, the object and all its attributes are created with the logical system OLTP.
For more information, see the documentation of the Business Add-In method: DETERMINE_LOGICAL_SYSTEM.
Note:
If you use several SAP ERP systems that replicate to one CRM system, you should ensure that the number ranges of the equipment in the SAP ERP systems do not overlap. Otherwise this can lead to errors during processing.
If the delta load is activated, the data in SAP CRM is updated independently of the definition of the logical system, if the data is changed in SAP ERP. The logical system only affects whether data can be maintained in SAP CRM.
Displaying the Equipment in the CRM System
You can use the equipment number that corresponds to the object ID to search for and display the equipment in SAP CRM.The related installed base is determined using the object ID (equipment number) and the object family.
The equipment is displayed as installed base components of type "Objects". You can view the attributes in the detailed component view.
Technical Data and Facts
The flow runs via the SAP CRM adapter framework and is configured there.| Replication object: | EQUIPMENT |
| BDoc type: | CRM_EQUI_DMBDOC |
| CRM validation module: | CRM_DEQUI_VAL |
Function Modules and Business Add-Ins
The validation coding for equipment mapping is contained in the IB_CRM_INT package. The initial module for the validation logic and processing of the equipment BDoc is: CRM_CREATE_IBASE_FROM_EQUI.The Business Add-In CRM_EQUI_LOAD belongs to the IB_CRM_INT package. This Business Add-In offers you extensive options for influencing the mapping of objects. For more information, see the documentation for the Business Add-In: Equipment Download.
CRM Customizing
Use the activity Define Default Settings for the Equipment Replication to customize the load.
contact us for all your SAP implementation , recruitment and payroll requirements
www.Nvider.com
Posts
Post a Comment