Info Blocks in Detail 

...

       1.      The RFC ISU XML Connector info block displays the industry-specific data from the IS-U system. This info block belongs to the CL_CRM_CCKPT_IO_XML_RF class.  To customize this info block, specify the RFC destination and HTML data selection (you make these settings in the Customizing transaction of the IS-U system under Utilities Industry ® Customer Service ® Customer Interaction Center ® Define HTML Customer Overview).

       2.      The open or closed transactions after the business agreement info blocks display the data in the same way as the existing CRM info blocks. The transactions are displayed sorted by business agreement.  These info blocks belong to the CL_CRM_CCKPT_IO_PROCESS_OP_GV or CL_CRM_CCKPT_IO_PROCESS_CL_GV classes.  In Customizing, you must select the period in months from which you want the data to be selected.

       3.         XSLT style sheet and processor is not actually an info block but is used for Customizing (class CL_CRM_CCKPT_IOS_XML_RFC_STYLE). It determines which style sheet and XSLT processor are used to display a view.  You can choose from the following:

·        XSLT processor: enter the processor that you want to carry out the transformation.  You have the same options as specified in the table, under Technical Description of Fact Sheet, for controlling via the URL. (Standard)

·        XSLT program: Enter the XSLT program that you want to use for the style sheet.  You can edit the XSLT program in the workbench (transaction SE80).  The standard XSLT program with IS-U data is CRM_CCKPT_CFS_SERVICE_IS-U; the XSLT program with CRM data is CRM_CCKPT_CFS_SERVICE_DEFAULT.

·        Application: Enter the application on the WAS that contains the XSLT program.  You can also edit these objects in the workbench (transaction SE80).  In addition to the entry, specify a page (path).  The default value for the application is CRM_BSP_CCKPT_SERVICE_HTTP (optional procedure).

·        Path: Enter the page of the application that you want to use for the style sheet) optional procedure).

 

Not all of the possible combinations make sense.

 

Example:

·        XSLT programs can be transformed using the SAPI processor.

·        BSP applications can be transformed using the SAP, EXT, and CNPL processors.

·        If you choose EXT for the processor, you must call the CFS with an XSLT-compatible program to perform the transformation. Examples include Internet Explorer 5.5 with the corresponding Microsoft enhancement.

·        If you choose XML for the processor, the CFS is not transformed but returned in the form of XML data.

The standard settings for IS-U data are:

·        XSLT processor:   SAPI

·        XSLT program:      CRM_CCKPT_CFS_SERVICE_ISU

       4.      View Filter: This Info block enables you to include a view A (from the CFS) as an Info block in view B.  You can also an XSL style sheet to change the data of view A. The class of this info block is CL_CRM_CCKPT_IO_VIEW_FILTER. A possible application for the view filter is to read and transform the data from 2 systems in view A and then transfer the data to view B (for example, contacts (IS-U) and activities (CRM)).  In Customizing you must enter the view and style sheet with which you want to transform the data.

       5.         The HTTP_IS-U XML Connector info block displays industry-specific data from an IS-U system.  The info block belongs to the CL_CRM_CCKPT_IO_XML class.   To customize this info block, enter the URL of the HTTP connection, separating the host, port and path.

You can find all the available info blocks in the CRMV_CCKPT_CLASS view (transaction SM30 - maintain table view). If there is no info block for a certain class, you can add it to the table as appropriate.