Ansicht
Dokumentation

ECRM_ISU_TO_DIVSETTP - Define Division-dependent Set Types

ECRM_ISU_TO_DIVSETTP - Define Division-dependent Set Types

General Material Data   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you make settings for the use of industry-dependent set types 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 Service Types IMG activity.

In the first section of this IMG activity, you can automatically incorporate the set types assigned beforehand to the divisions 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 set types do not 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 IMG 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 IMG activity, you can have the divisions maintained beforehand transferred into Customzing for the product group 1. These are needed to assign products to a division.

In the fourth section of this IMG activity, 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.

In the fifth section of this IMG activity, 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 thus also display or change warranties using the IBase transactions. The use of this section of the IMG activity is optional.

The sixth section of this IMG activity - Automatic Transfer of Divsions to Product Group 1 - is obsolete with CRM 5.1.






BAL Application Log Documentation   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 3910 Date: 20240523 Time: 170359     sap01-206 ( 81 ms )