Ansicht
Dokumentation

CRM_CODEX_OLTP_CUSTOMIZING - CRM Service: Checklist for Data Transfer

CL_GUI_FRONTEND_SERVICES - Frontend Services   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Purpose

This report is used to check the various Customizing settings that are required for the data transfer between the CRM service and an ERP system. It can be regarded as a type of checklist.

Integration

Prerequisites

CO Integration

You must maintain the controlling scenario if you want to post costs in R/3. A distinction is made between mass and single-object controlling here. You can define this for each transaction type, service organization and responsible organizational unit. Wildcard entries (*) are admissible here. You can also define whether controlling is to be performed at transaction or item level.

If you want to use the single-object controlling type, you should define accounting indicators. You subsequently assign the accounting indicator to the CRM service order or CRM service confirmation. It is used in all actual postings to differentiate the origin.

Organization data determination

To ensure that a company code and a business area can be identified from the data for the service transaction/service contract or the service confirmation (required by the CO translator to create the CO object in R/3), the following assignments must be made in the organizational data determination (OFI)

·,,Assign Billing Unit to Service and if necessary

·,,Assign Company Code to Billing Unit

·,,Assign Business Area to Service and to the Sales Organization if necessary

Plant for material posting

Since it is not possible to specify a plant when entering material consumptions in the confirmation, but this is required for the goods movement 291/292 W, the planning plant is read from the service organization.

The planning plant can only be assigned at the highest level and is inherited down to the technician group.

To ensure that the MM posting is successful, you must also observe the following points:

o,,Material master data must be identical in both CRM and R/3.

o,,Materials can only be posted if they have also been maintained in the plant defined (planning plant in CRM) in R/3.

o,,The material must exist in the plant specified. A corresponding goods receipt can be posted using transaction MB1C with the movement type 561 W by specifying the plant and customer (for the technician).

Personnel number of the technician

The HR personnel number of the technician is determined from the master data for the CRM business partner. The technician in CRM; must also be maintained in the employee role. If you display the technician data (in the employee role), the “Central Data” tab contains the personnel number field. The HR personnel number is entered here.

Number ranges

If an order is to be replicated to R/3, identical number ranges must be maintained in both systems.

The data replication report is used to replicate service-specific data (transaction types, item categories, organizational units, service types, valuation types, product categories including text tables) automatically to R/3.

CATS Profile

An entry profile is required as an entry profile to post or cancel CATS documents. Note that the indicator “No deduction of breaks” must not be selected in the profile. The system only observes this if confirmations of actual times with the same start and end time are found. If a posting is made in CATS in which the start time is the same as the end time, 24 hours are posted regardless of what the technician has entered as an actual time. To avoid this special case, the end time is filled using blanks. CATS only calculates the end time automatically if this indicator is not selected. If this indicator is selected, the end time for CATS is set to midnight in this special case.

Presence and activity type

This data is also required to make a CAT posting. The presence and activity type are defined using the item, service and valuation type. If no entry is made for these types, this is interpreted as a wildcard *. The presence type and activity type are defined for each item.

In some specific circumstances, this Customizing step can be omitted. This is the case if the presence type is always to be identical and the activity type has already been recorded in the personnel master (transaction PA61). The values that you have maintained using the transaction SCRM override the default values in the profile and the personnel information record.

Customer number for goods movement

A customer consignment is used as the goods movement for the transfer. The technician is shown as a customer here. The personnel number cannot be used directly for this type of posting. However, it is possible to find the correct customer number for a personnel number using a workaround. This requires a customer to be maintained in R/3 who corresponds to the technician. When you maintain the company code data for the customer, you enter the personnel number of the technician. Customers can change or create the technician from the following menu path: Accounting ->Financial Accounting -> Accounts Receivable ->Master Records (transactions FD02 or FD01) . A link that is made here is subsequently read from the table KNB1.

Logistics scenario

You use the logistics scenario to define the withdrawal and posting of service materials, which have been confirmed from a CRM service transaction. You can select the various types of logistics scenarios according to the CRM transaction and the service organization. The standard logistics scenario is the withdrawal of service parts from the technician’s consignment stock.

Features

Selection

Standard Variants

Output

Activities

Example

rdisp/max_wprun_time - Maximum work process run time   TXBHW - Original Tax Base Amount in Local Currency  
This documentation is copyright by SAP AG.

Length: 6402 Date: 20240520 Time: 093315     sap01-206 ( 182 ms )