Ansicht
Dokumentation

CRMUT_DIVDEP_SETTYPE - Define Division-dependent Set Types

PERFORM Short Reference   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

In this activity, you make settings for the use of industry-dependent set types and further object enhancements in the technical objects.

The set types to be used have been generated, created, and transported.

For the transfer of service types, you have already created the service types in the Assign Set Types to Divisions activity.

If you want to activate the enhancements for the management of temporary technical objects, you have activated management for temporary technical objects in the Maintain Settings for Management of Temporary Technical Objects activity.

In the first section of this activity, you can automatically incorporate the set types assigned to the divisions beforehand into the product/point of delivery category intended for technical objects.

The ECRM_ISU_TO_DIV_SETUP program reads all of the set types that are maintained in customizing for the view cluster. It automatically determines which of the set types exist in the category of the object family 0102 (based on your customizing settings in the COMM_HIERARCHY transaction). If the set types exist, you can add them automatically to the category. You can also delete set types, but only if no IObject exists for this category/division.

In the second section of this activity, you create or enhance the CI include for the technical objects with the set type structures you created with an implicit name that is the prerequisite to the use of set types.

In the third section of this activity, you can trigger the automatic enhancement of the CI includes for the technical objects with several structures:

• First frame: Time slice management
  You can trigger the automatic exchange of the standard set type save functions for customer set types with a generic save function capable of maintaining time slices.

• Second frame: temporary TOs
  You can trigger the automatic enhancement of CI includes for technical objects with structures necessary for the management of temporary technical objects. This includes the maintenance and search of technical objects.

• Third frame: Searching by customer fields
  You can trigger the automatic enhancement of CI Includes for searches of technical objects in order to enhance the searches for technical objects by fields from customer set types.

• Fourth frame:
  You can trigger the automatic enhancement of the CI Include for the technical objects with the DDIC communication structure CRM_SI_WB_COMMSTRUC. This structure provides various address structures:
  
  Structure ADRS1: This structure is based on SAP Central Address Management and contains the main address fields, such as street, postal code, and city.
  8 structures of the type CRM_SI_WB_COMM_ADTEL: You can use these structures to create up to 8 telephone numbers with the main fields COUNTRY, TEL_NUMBER, TEL_XTENS, REMAR, VALID_FROM, and VALID_TO.
  8 structures of the type CRM_SI_WB_COMM_ADSMTP: You can use these structures to create up to 8 e-mail addresses with the main fields SMTP_ADRR, REMARK, VALID_FROM, and VALID_TO.
  4 structures of the type CRM_SI_WB_COMM_ADFAX: You can use these structures to create up to 4 fax numbers with the main fields COUNTRY, FAX_NUMBER, FAX_EXTENS, REMARK, VALID_FROM, and VALID_TO.
  4 structures of the type CRM_SI_WB_COMM_ADURI: You can use these structures to create up to 4 URI addresses with the main fields URI_TYPE, URI_SCREEN, and REMARK.
  
  You can use this section. However, we do not recommend this.

• Fifth frame:
  You can trigger the automatic enhancement of the CI Include for the technical objects with DDIC warranty structure CRM_SI_WB_WARRANTYSTRUC. You can use this structure to easily add up to two warranties for the technical object. For each of the two warranties, the following fields are provided: WARRANTY_PROD, START_DATEWY, START_DATE_RULEWY, END_DATEWY, END_DATE_RULEWY, DETERMINE_DATESWY, DELETE_WYT. The warranties are based on the links between a warranty product and a single object, such as the standard IBase. You can, therefore, also display or change warranties using the IBase transactions.

The use of this section of the activity is optional.

The fourth sectionof this activity - Automatic Transfer of Divisions to Product Group 1 - is obsolete with SAP CRM 5.1.

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: 4851 Date: 20240523 Time: 153304     sap01-206 ( 102 ms )