CRM Tables and FM's for Business Partner :  Commonly used Tables and Function modules for Business partner

• Business Partner Roles: BUT100
• Business Partner Relationship: BUT050
• Business Partner Contact Person: BUT051
• Business partner identification data: BUT0ID
• Business partner Tax classification data: BUT_FRG0011
• Business partner Bank Details: BUT0BK and BUT0BANK
• Business partner Industry data: BUT0IS
• Business partner Payment card data: BUT0CC
• These tables and many more stores the business partner data as entered in the respective tabs. But the above mentioned are more commonly used.

Business Partner Hierarchy

• In table BUT_HIER_TYPE the tree type guid can be found. For each tree type there can be multiple hierarchy trees.
• With the tree type guid we can go to table BUT_HIER_TREE and find the tree guid and tree description from table BUT_HIER_TREE_D
• The Node guids are maintained in table BUT_HIER_NODE and BUT_HIER_NODE_D.
• With this tree guid and the node guid we can go to table BUT_HIER_STRUCT and find the business partner hierarchy. For a child node we can get the parent node.

Business Partner Sales area data

• The maintained sales area for a business partner can be found by executing the function module CRM_BUPA_SELECT_SALES_AREA. The function module is called from the BP transaction which can either called in with dialog or without dialog mode.
• CRMM_BUT_FRG0100: Table containing Business Partner & sales area
• Business partner sales area data displayed in the sales tab can be found from table CRMM_BUT_LNK0011. With the SET_GUID the details can be found in table CRMM_BUT_SET0010.
• Same rule exists for business partner billing data ( CRMM_BUT_LNK0031 and CRMM_BUT_SET0030 ), shipping data ( CRMM_BUT_LNK0021 and CRMM_BUT_SET0020), etc.
• The business partner sales area specific partner function can be found in table CRMM_BUT_FRG0081 and CRMM_BUT_FRG0080.

          All the BPs for a particular Sales areaUse these tables - BUT000 & CRMM_BUT_LNK0010 , CRMM_BUT_LNK0020,  CRMM_BUT_LNK0030

          Take the Partner_guide from BUT000 table and pass the Guid value into any one table  - CRMM_BUT_LNK0010, CRMM_BUT_LNK0020, CRMM_BUT_LNK0030

          Database View

CRMV_BP_FRG0010                SAP BP, Mass Update: Sales Data

CRMV_BP_FRG0020                SAP BP, Mass Update: Shipping Data

CRMV_BP_FRG0030                SAP BP, Mass Update: Pricing Data

CRMV_BP_FRG0050                CRM BP: View FRG0050 for Mass Update

CRMV_BP_FRG0140                SAP BP, Mass Update: Organization Data

Marketing Table Relationships

• CABN Attribute Details - The attribute, like Hobby etc..
• CAWN Attribute's values, like under Hobby - Cricket, Football etc...
• KLAH Class ID or the Attribute Set ID. Like Hobby could be under Personal Interest Attribute set
• SWOR Key word for Attribute Set
• KSSK Attribute set ID vs Object ID (linking to BP) - Which partners has been assigned an attribute set.
• INOB Object ID vs BP ID - Object ID linked to the BP ID
• AUSP Gives BP GUID for an Attribute ID, Value and Object ID

Function Modules for Business Partner

• BAPI_BUPA_CREATE_FROM_DATA : To create BP in CRM
• BAPI_BUPA_FRG0020_GETDETAIL: To obtain shipping data
• BAPI_BUPA_FRG0020_ADD : To insert shipping data in a BP
• BAPI_BUPA_FRG0030_GETDETAIL : To obtain pricing data
• BAPI_BUPA_FRG0030_ADD : To add the pricing details in a BP
• BAPI_BUPA_ROLE_ADD : To add role to a Business Partner
• BAPI_BUPA_FRG0010_ADD :To add Sales data to Business partner
• BAPI_BUPA_FRG0010_GETDETAIL : To get sales data for BP
• BAPI_BUPA_TAX_ADD : To add tax details to BP
• BAPI_INDUSTRYSECTOR_ADD : To add industry code in BP
• CRM_BUPA_SELECT_SALES_AREA.: To get the maintained Sales area data for business partner
• BUPA_DESCRIPTION_GET : To Get then Business Partner Description

Product Master related :Commonly used Tables and Function modules for ProductTables for Product

• In the table COMM_PRODUCT and COMM_PRSHTEXT the product guid, product ID, product type and product description can be found.
• COMV_PR_SALES_OT :Table containing product id against Sales Area
• COMM_PRPRDCATR: Table containing product category against product
• COM_PRODUCT_ID_GET - FM to get product ID from Product Guid
• The product base unit and alternative unit of measures can be found in table COMM_PR_UNIT ( this table is same as MARM table in R/3 ).
• The GTIN ( Global Trade Item Number ) for a particular product is stored in table COMM_PR_GTIN.

Table for Product Hierarchy and Categories

• Different hierarchy ID is stored in COMM_HIERARCHY. Product and category ID assignment is stored in table COMM_PRPRDCATR. The category ID details is stored in table COMM_CATEGORY

Product Set types

• All the relevant data for products is stored as set types.
• For each attribute of set type is generated Data Element with the same name
• When a set type is created it generates a table, programs and function modules. The table name created for a set type is same as the set type name.
• The fields of these generated tables are named as "ZZ" and running number, and their type is Data Element generated for the attribute.
• All set types must have the field FRG_GUID ( set guid ) along with other fields depending upon the attributes assigned to these set types.
• COMM_PR_FRG_REL & COMM_PR_FRG_ROD
  

Function Module for Product

• COM_PRSHTEXT_READ_SINGLE : To Get the product description
• CRM_PRP_READ - To get the Sub item details of a PPR ID
• Class CL_CRM_COMPONENT_SETTYPE Method READ_SETTYPE_DATTA_FROM_PRODUCT may be used for this requirement, passing the parameters: Product Guid of Service Plan product, Set type 'ZPPR' and the Organization data of the Service Order
• CRM_PRODUCT_GETDETAIL_API - To get the details of the product.This is also used for pulling data for a product from set type.ES_PRODUCT_DATA : CATEGORIES - contains category data (contains HIERARCHY_GUID & CATEGORY_ID)
• COM_PRODUCT_READ_SINGLE : To get the details of the product

Function modules for Organization

Organization Attribute

• The Attributes assigned to a org unit can be found by using the function module RH_OM_ATTRIBUTES_READ.
• In this function module we need pass the plan version ( which is always 01 i.e. current plan ) , object type ( which can O ( org unit ), US ( user ) and all the valid object types present in table T778O ), SCENARIO ( can be SALE, SERVICE or MARKETING ) and SELDATE ( generally the current system date in order to get the most recent object values.
• This function module is useful in order to the distribution channel, division, currency, country, etc for an org unit.

Organization Hierarchy

• In order to get the organization hierarchy we can use function module RH_STRUC_GET.
• In this function module the meaning of the parameter plan versions, object type and object ID remains the same.
• The parameter ACT_WEGID is used to give the evaluation path. Depending upon this evaluation path the result vary. For example if we use the O-O_DOWN for an org unit we will get all the child for that org unit sorted down.
• All the valid evaluation path is maintained in table T778A.

Organization validation

• A org unit is valid or not can be found from the table HRP1001 or by using the function module RH_MACO.
• The function module RH_MACO in addition can provide the search help for an org model.
• Sales org validation can also be done using function module CRM_ORGMAN_SALES_ORG_CHECK.
• Distribution channel validation can be done from CRMC_DISTCHAN
• Division validation can be done from CRMC_DIVISION.
• The search help to display only sales org is CRM_ORGMAN_SALES_ORG
• The search help for distribution channel is CRM_ORGMAN_DIS_CHANNEL
• For a R/3 Sales org the corresponding CRM sales org can be found by using function module CRM_BUPA_SALES_AREA_TO_CRM and the vice versa by function module CRM_BUPA_SALES_AREA_TO_R3

Transactional data

Enhancements in transaction type

• CRM_ORDERADM_H_BADI: Gets triggered when transaction header data is changed. When a transaction is created this BADI is triggered only first time.
• CRM_ORDERADM_I_BADI: This BADI is triggered per line item. When a new line item is added or deleted this BADI is triggered.
• CRM_OPPORT_H_BADI: This BADI is used when opportunity header data is changed. This is not common for all the transaction type.
• CRM_LEAD_H_BADI: This BADI is used when the lead header data is changed. This is also not common for all the transaction type.
• CRM_ACTIVITY_H_BADI: This BADI is used when the activity header data is changed. This is specific to the transaction type with leading transaction category as activity.

  More BADIs

• There are many more BADIs which help in certain modification of the business transaction during the process of its creation.
• Apart from the list mentioned above the other important BADIs are CRM_SALES_BADI, CRM_ORGMAN_BADI, CRM_SCHEDLIN_BADI, CRM_PRODUCT_I_BADI etc.
• All these BADI have got two methods in common. One method is used for checking and the other one is used for changing data.
• In the method for data changing one of the importing parameters comes with a old value , one with the changed value and other with the names of the fields changed. There is one changing parameter for this method which is may be used according to the business requirement.
• ORDER_SAVE: This badi is used during the saving of any business transaction

Important function modules to read business transaction

• CRM_ORDER_READ is the function module used to read the data for any business transaction.
• There is a program CRM_ORDER_READ which can be used to find out that in which important parameter the relevant data is present.
• In the function module importing parameter there is a IT_REQUESTED_OBJECTS which can be used for performance tuning. That is only passing the object names which are required.

Function module to create or change business transaction

• BAPI_ACTIVITYCRM_CREATEMULTI can be used to create activity or sales order in CRM.
• In the BAPI for each type of data like header or item there is parameter where we need to populate with X in order indicate which data is required to be populated.
• The function module CRM_ORDER_MAINTAIN can be used to change business transaction data. The parameter CT_INPUT_FIELDS is used to specify the object names and the field names which has been changed

SAPCRMInteractionCenter Web Client

Objective

• For users utilizing the Interaction Center (IC) functionality of SAP CRM, IC Web-client provides a Web interface with an aesthetic layout and user-friendly controls. To design the IC web layout, an in-depth understanding of its architecture is a must. The aim behind this program is make the participants well conversant with the same.
• In other words this program would help participants to understand SAP-CRM version 5.0 IC Web architecture and thus facilitate design and implementation of solutions based on the same.

• The SAP Application Server Release 4.6 D is fully based on the ABAP runtime environment.
• User Interfaces (UIs) are based on Dynpro technology. Dynpros are normally displayed on a clients PC via SAP GUI technology.
• Instead of a SAP GUI it is also possible to access the Application Server via a Web Browser. In this case the Internet Transaction Server (ITS) is required as a Web Middleware. ITS is translating the ABAP based Dynpros into HTML pages dynamically at runtime.
• To connect the Application Server to external software components you can use the SAP proprietary Remote Function Call (RFC) protocol.

      Basic Terminologies

• SAP Web Application Server (SAP WAS)
  • SAP WAS is a platform for efficient development and allows the implementation of web applications. It supports the complete development and lifecycle of enterprise applications, and allows a user to develop new kind of enterprise web applications known as BSP applications.

• Business Server Pages (BSPs)
  • BSP contains code and HTML(B), all of which is compiled by the server upon request. The user interface (UI) in IC Web client application is based on the BSP technology.

• HyperText Markup Language Business (HTMLB)
  • BSP extensions provide HTMLB tags that provide excellent look and feel to the Interaction Center layout. HTMLB tags are more powerful than the HTML tags and thus provide better aesthetic options.

• WAS : From the SAP point of view the (WAS or Web AS) is the foundation on which most of their product range runs.
• Its basic function is to allow web development based on SAP standard solutions (usually developed under the ABAP programming language, but in the newer versions also in Java programming language).
• With Web AS, it is possible - for example - to publish queries, programs and ABAP applications in a web environment but linked to and based in a SAP solution infrastructure. The newer versions of the (WAS or WEB AS) also support open standards like Java programming language.
• From the versions 6.20 and higher it is possible to create ABAP only, Java Platform, Standard Edition only or mixed environments.

• The Internet Communication Manager (ICM)
  • For communications between the Web Application Server and external supporters over intranets or the Internet using standard protocols like HTTP, HTTPS, and Simple Mail Transfer Protocol (SMTP).

Views:

• BSP : The SAP Web Application Server provides a page-based programming model with server-side scripting as well as server page technology for developing, designing and implementing Web applications: (BSP). Server-side scripting enables direct access to all elements in the application server (such as function modules, database tables, ABAP Objects, and so on. ).

• HTMLB :It is extension of HTML. More powerful than HTML and user to design UI. We'll see few basic tags of HTMLB during this course.

• IC WebClient : It is the web based framework which is build on WAS and used for SAP applications.

• BSP : The SAP Web Application Server provides a page-based programming model with server-side scripting as well as server page technology for developing, designing and implementing Web applications: (BSP). Server-side scripting enables direct access to all elements in the application server (such as function modules, database tables, ABAP Objects, and so on. ).

• HTMLB :It is extension of HTML. More powerful than HTML and user to design UI. We'll see few basic tags of HTMLB during this course.

• IC WebClient : It is the web based framework which is build on WAS and used for SAP applications.

Navigation Bar

IndexLeadInteraction Hist.OpportunityOpportunityUpdate navigation BarLeadInteraction Hist.

SAP WebAS 6.20

User AccessUser Interface ProgrammingProgramming LanguageConnectivity* SAP GUI

• Web Browser, Mobile Devices* DynPro
• BSP
• JSP* ABAP
• JAVA* RFC
• Access to 3^rd Party (connectors)
• HTTP(s), SMTP, SOAP/XML*J2EE*ABAP*SAP Web AS 6.20*Internet Communication ServiceClient
• The Internet Communication Manager (ICM)
• For communications between the Web Application Server and external supporters over intranets or the Internet using standard protocols like HTTP, HTTPS, and Simple Mail Transfer Protocol (SMTP).

IC Web Client on SAP Web AS 6.20

Business Server Pages( ABAP + HTMLB)ABAPJ2EE*Communication Services*

Scripting

…External Communication SoftwareSAP Web AS 6.20*ABAP Based BSPs*controlling layout and navigation

*JAVA Based services*controlling communication integration and scripting

IC Web Client

• The IC WebClient is based on BSP technology mainly.
• An agent logs on to the IC WebClient application (BSP application CRM_IC) through an URL, portal.
• In parallel to the BSP session there is a second session running on the Java side controlling the integration with third party communication software as well as some other services (alerts and interactive scripting, knowledge search).

Layers in IC Web Client Application

TablesGeneric Interaction LayerBusiness Object Layer(BOL)Business Server Pages (BSPs)(GENIL)Application Programmer Interfaces*Business LayerPresentation LayerDatabase *IC Web Client

• The Business Server Pages (BSPs) are the presentation layer of the IC WebClient. They are used to generate the HTML page of the WebClient running in the agents Browser. The business logic of CRM business objects and processes is not controlled by the BSPs: presentation and data model are handled separately.
• Business objects like business partners, product, transactions, etc. are kept in the Business Object Layer (BOL).
• The Generic Interaction Layer (GENIL) handles the data transfer between database tables and the BOL.
• As we want to focus on WebClient UI customization we will focus on the BSPs rather than the data model of the CRM objects.

Layers in IC Web

• Presentation Layer:
  • Forms the user interface created out of Business Server Pages (BSP). BSP contains code and HTML(B), all of which is compiled by the server upon request.
• Business Layer:
  • Containing the Business Object (BO) layer and the Generic Interface Layer (GENIL).
  • BO layer contains the runtime data of an IC Web client session. It stores the BO data such as Business Partners, Orders, etc.
  • GENIL is the Generic Interaction Layer that provides an interface between the BO Layer and the underlying Business logic. The segregation of BO Layer and GENIL.
• Business Engine:
  • Containing the Application Peripheral Interfaces (API) and the Database tables.
• The above structure ensures a definite segregation between the layers which facilitates the connection of different Business Applications via the Business Layer (BOL and GENIL) to the Presentation (IC Web UI).

Business Layer: Overview

RequestResponseuser

inputdata

outputControllerViewModelPresentation Layer (BSP)Business

LayerDatabase and Applicationdatabase tables storing the business objects of independent structureBOL: Business Object Layerdata structures of the BOL holding business objects for the IC WebClient sessionGENIL: Generic Interaction Layerconnecting BOL to the CRM database table through APIsAPIAPIAPI

• The business layer of the IC WebClient handles the data of the business objects of an IC WebClient session. It consists mainly of two elements:
• The BOL Business Object Layer is a set of structures that hold the data.
• The GENIL Generic Interaction Layer connects the BOL to the CRM database through APIs (Application Programming Interfaces). The APIs are mainly ABAP classes and function modules reading and writing data to and from the CRM standard business logic and database.

IC Workbench: Accessing the BOL Model

BOL Object: CRM Business TransactionData Dictionary Structure (double click)Fields of the structureTransaction:

BSP_WD_WOKBENCH

• This function was available in CRM 4.0 in transaction GENIL_MODEL_BROWSER

Tools for BOL and GENIL
ControllerModelPresentation
LayerBusiness
LayerBOLGENILViewBSPDisplay BOL Model
Transaction: BSP_WD_WORKBENCH or GENIL_MODEL_BROWSERGENIL APIs
IMG: Generic Interaction Layer/Object Layertest data retrieval from database to BOL through the GENIL
Transaction:
GENIL_BOL_BROWSERDatabase and Application

GENIL

Transaction: GENIL_MODEL_BROSWERStructure Displayed would be same as in case of BOL

• The Generic Interaction Layer (GENIL) handles the data transfer between database tables and the BOL.
• Connects to the APIs and CRM Tables for Data retrieval

• SPRO->Customer Relationship Management->CRM Cross Application Components->Generic Interaction Layer/Object Layer->Component Specific Settings->Check Entire Model for Transactions would depict the entire GENIL model based on the relationships.

Generic Interaction Layer
IMG: Generic Interaction Layer/Object Layer à Basic Settings

• You may use this transaction to find out which GENIL classes are responsible for reading and writing data from and to the CRM database.
• For example the Business Partner is accessed via the implementation class CL_CRM_BUIL and its methods.

Genil BOL Browser

Transaction GENIL_BOL_BROWSER or

BSP_WD_WORKBENCH à Environment à BOL Browser

Transaction GENIL_BOL_BROWSER or

*BSP_WD_WORKBENCH à Environement à BOL Browser*

• Here you can test the data retrieval from the CRM database to the BOL (advantage: you do not need the Web Client as a UI to test GENIL and BOL).

Presentation Layer

• BSP is the basis of Presentation layer
• BSP in IC web is based on Model View Controller (MVC) architecture.
  • View:
    • The view provides the layout for display of fields/buttons/dropdowns etc. on the screen and does forms a user interface.
  • Model:
    • Responsible for linking the fields on the view with the underlying BOL.
  • Controller:
    • Would respond according to the user commands.

Business Server Page Technology

• Layout Rendering and event handling is done by pages
• Business Logic is included via Application class
• Flow between pages is defined by event handler

ResponseBusiness Object Layer (BOL)IC Web Client*Business Layer Presentation Layer *Application Class

Attributes + Methods Request

     Common features of BSP Applications:

• Direct request to the server, the server takes the request process to the BSP page.
• BSPs are called via URL.
• BSPs are fully integrated.
• BSPs can read data from the database via the business layer.
• BSPs can call a function module.
• BSPs can be transported.

Model View Controller in BSP

• Extend the BSP Programming model with MVC paradigm
• Enable programming model similar to Java World
• Simplify BSP pages in order to support further customizing options
• BSP using MVC (Model View Controler) concept:
• BSP Views:
• Views
• View sets
• BSP Controllers:
• View controllers
• Custom controllers
• Model:
• Contexts
• Context nodes
• Every view has a controller. Benefit is that a controller from one application can call another application without modification.
• For every business object or model there is a custom controller. The custom controller keeps all data we have for the business object or model to show data in different views.
• Custom controller lives whole time in the IC session. When you end contact you can clean up all custom controllers (this is programmable).
• Context is where the data is stored in IC session working data container built like a hierarchy and node, each node has some data parts.
• Context exists for the session.

Controller View Structure

• Complex call sequence during one HTTP request
• Page fragment aggregated during runtime

1. Within a view set we can call other views.

Object Navigator

• The Standard BSP Application CRM_IC is opened in the Object Navigator SE80. The screen shot shows the presence of Controller, View, Pages and Flow Logic, Page Fragments and MIMEs as a part of the same.

• A page can have the following versions:
• Page with flow logic: These are simple pages with event handlers, but without much application logic or visualization elements. It is possible to build a BSP application exclusively out of pages with flow logic and event handlers.
• View: Views are used to visualize data. Page fragment
• Page Fragments: These are created in the same way as normal BSPs, but are then marked as page fragments. Other BSPs can also include these fragments using the include directive

• Controller and Views would be explained under Model View Controller, the next section.

Model View Controller

• The Model View Controller which is the basis of SAP CRM – IC WebClient BSP.
• The "Controller" would receive the user request and based on the same the output would be displayed on the screen (View).
• If further processing (retrieval of data/setting the data) of the request is intended, the same would be passed on to the "Model".
• The Model would thus retrieve the data from the underlying Business Layer. This concept where the fields on the view are thus linked with the BOL is known as Binding.

View Controller

• The "View Controller" is implemented as a class which is assigned to the view. The methods present in the controller would determine the actions to be taken based on the user commands.

Custom ControllerPresentation Layer (BSP)ControllerView 1ModelContext NodeModelContext NodeControllerView 2Custom ControllerModelContext NodeLifespanBusiness Layer (BOL, GenIL)DatabaseLifespanLifespan

• Since the data held by the View, View controllers and the Contexts are deleted from the memory when the user navigates away from the view, there may lie a need to safeguard this at times.
• Custom controllers would allow this as they have unrestricted lifespan.
• Data can be passed to the custom controller while navigating from one view to the other. 

This document was generated from the following discussion: List Of FM to get data from Product master

More Reference blogs/discussion -

CRM Tables - CRM - SCN Wiki

SAP CRM Marketing tables

This document  is created to  List down of relevant materials for SAP CRM Social Media Integration for use of scn members at one place.

SAP Notes:

1832462 about Social Integration Architecture (Consulting Note)

1832480 - How to implement Twitter API for CRM Interaction Center
1832481 How to implement Facebook API for CRM Interaction Center
1881971 How to implement Sina weibo API for CRM Interaction Center
1947132 How to implement WeChat API for CRM Interaction Center

More information:
Note 1859791 - Additional steps to enable Social Media Integration in CRM Interaction Center
Note 1939476 - Q&A: Social Media Integration in CRM Interaction Center

Blogs:

1. http://scn.sap.com/community/crm/blog/2014/05/08/sap-crm-ehp3-sp04-social-media-integration-solution-new-features
2. http://scn.sap.com/community/crm/blog/2013/11/08/twitteralso-facebook-is-official-integrated-into-crm-70-ehp3

Purpose

Overview

This document will elaborate to change Quote /order /contract status in Header & item as well.

Below are the details..

Go to se37  --> FM CRM_STATUS_UPDATE

After run FM need to choose JEST_UPD. Next

Please the above steps need to perform when user not able to change status's then use above FM & set right status's.

Thanks,

sanjeevb

CRM 2015 Conference: “ENGAGE YOUR CUSTOMERS LIKE NEVER BEFORE”

March 30 - April 1 at the Mirage in Las Vegas, to hear more about SAP’s Customer Engagement & Commerce (CEC) solution portfolio and how successful companies are leveraging SAP® solutions to better engage with their customers.

Come to learn about SAP’s vision and strategy around Customer Engagement and Commerce. See SAP’s market-leading mobile applications for sales
and service in action, and be among the first to hear about our new marketing platform; experience the power of SAP HANA® and how SAP’s predictive analytics redefine sales and marketing. Learn more about SAP’s innovations in the cloud and how to best leverage and expand your SAP CRM on-premise investments. Explore the possibilities of the hybris omni-channel commerce platform to digitally transform your business.

Please join us to engage and network with your peers, SAP partners, and SAP experts. Learn from best practices and case studies across sales, marketing, service, and commerce. Read about our speakers - 2015 CRM Insider Brochure

Register here

• What is Desktop Connection for SAP CRM?

Desktop Connection for SAP CRM is a new offering from SAP that allows you to manage CRM accounts, contacts, emails, tasks, appointments, leads and opportunities from Microsoft Outlook or IBM (Lotus) Notes. Desktop Connection enables users to organize their daily activities and see important CRM data in a familiar application without the need to use the SAP CRM WebClient. Read John Burton's blog about frequently asked questions.

• Seven Things You Need to Know About Fiori for CRM- blog by John Burton

If you’re an existing SAP CRM customer you have probably already heard about SAP Fiori. But you might still have some questions like… What the heck is a Fiori anyway? What SAP CRM functionality is available via Fiori? How much does Fiori cost? Does Fiori require SAP HANA? Read on.

This document will help you how to add a new filed in the table view, so that we can display any data related to that node. So for that we have to create a z (custom) field for that and add it to this screen. Now we will see standard filed and display data in a table view.

We may sometime come across a requirement of adding standard field to table view in CRM web UI.  This article explains how to add standard field to the table view and display data based on search.

Procedure:

1) Add value or model attributes to the table view context node ( in my scenario i have taken value node).

2) redefine GET_TABLE_LINE_SAMPLE and extend the existing structure by adding z fields

3) go to SPRO and search for design layer. There you have to check disable hiding of fields by design layer checkbox

4) Find out the relation between context nodes.

5) populate the value in the fields by using relation name in GETTER and SETTER method.

Step 1: Add value attributes to the table view context node

            go to table context node right click and create.

Provide the attribute name any name which is relevant to your requirement and DDIC structure that is data element for that field.

click on continue.

Click on complete the wizard will generate one filed under your context node.

While creating table view at that moment wizard will create one structure in GET_TABLE_LINE_SAMPLE.

Step 2 : redefine GET_TABLE_LINE_SAMPLE and extend the existing structure by adding z fields

Enhance the GET_TABLE_LINE_SAMPLE method under your context node..

Extending the structure by adding your field in to GET_TABLE_LINE_SAMPLE.

Step 3 : go to SPRO and search for design layer. There you have to check disable hiding of fields by design layer checkbox

SPRO->CRM->UI Framework->Design layer-> Deactivate Hiding of Fields.

Go to table view click on configuration move your filed form available to display.

Then we can see your filed in result view.

If we want to display data for that filed we can write the code in getter and setter methods.

Based on the relation we can fetch the data.

Step 4: Find out the relation between nodes.

Go to web ui in which field u have to identify the relation place a cursor on that field click on f2 then u can identify the component name, view name, context node.

Go to that component there is a method do_prepare_method.

Place a breakpoint

We have to pass typed_context->context_node->collection_wrapper right side same as like above.

Double click on that.

Click on collection_ref-> ENTITY_LIST-> CONTAINER_PROXY->data_ref->RELATIONS

Under this is the relation.

This relation we have to use.

Step 5: In getter and setter method write this code.

In setter method .

This is the out put..

Thanks & Regards

Srinivas

In this document I will discuss about the steps which needs to be done to integrate a Document Management System (Content Server) with CRM 7.

At first the Content Server needs to be defined which would be compatible with SAP. We have used Open Text Document Access 10.0.

The Content Server has to be integrated with CRM in transaction OAC0:

Once the content server has been defined then we need to decide the document types under which we will be storing the documents. These document types will be created as folders in the content server. This configuration is done in OAC2:

The document types is now assigned to business objects in transaction OAC3. In this transaction we decide which business objects will require the functionality of storing the documents. This configuration stores the combination of Business object, Document type and the content repository.

In addition a new external alias needs to be defined in the content repository service in SICF transaction as shown below:

With all the above mentioned settings the documents can be uploaded and viewed in the attachments assignment block in the respective object as shown below:

Hope the information shared helps the community.

In this series of documents I am going to discuss about the important steps that needs to be done for integrating the address review screen with any of the address screens in SAP CRM. The pre requisite for this activity is SAP DQM (DS 4.1) has to be connected with SAP CRM through standard RFC connections and the address review jobs needs to be run on DQM server. 

Thus I have divided the series into three parts which will cover:

• Basic Integration of DQM with CRM 7
• Integration of DQM services with UI Components
• Additional services provided by DQM

In this document I am going to cover the Basic Integration of DQM with CRM 7

The following activities needs to be done for the basic integration in the following IMG path: SPRO > SAP NetWeaver>Application Server>Basis Services>Address Management>SAP BusinessObjects Data Quality Management

• Maintain settings to switch off the Address Reviewer screen: This activity is required to turn on / off the address review screen based on the country settings.
• Maintain settings for Address Validation Control: This setting should only be done on the country on which the address validation is to be triggered.
• SAP handshake with RFC servers: The RFC connections needs to be maintained are FL_GDQC_SERVER and FL_GDQC_BATCH. These RFC connections connect with DS and fetch address related information.
• Maintain operating parameters: This is the key configuration for integration of CRM with DQM. It determines which RFC user will talk with DQM, how much data can move in batches and what will be width of address review screen etc.

• Maintain fields for address reviewers: This the key configuration which provides the option for putting the sequence of fields that should be shown in the address review.

• Maintain Suggestion List Fields : In this configuration the field list is shown if more than one address has been found in the output

• Activate/Deactivate postal validation functionality: In this setting we can activate / deactivate the DQM functionality by activating / deactivating the BADI /FLDQ/ADDRESS_CHECK.
• /FLDQ/47U6X BC Set also needs to be activated.

In addition the following settings needs to be done in SPRO > SAP NetWeaver>Application Server>Basis Services>Address Management> DQM: Global Data Quality Adapter: CRM7 Extension

• We will have to activate the BADI FLDQ_BS_DUPL_FUZZY_IMPL for the fuzzy search
• BC set /FLDQ/BSP_PV  and /FLDQ/EXT_SEARCH needs to be activated

This completes the basic settings for DQM integration. In the next document I am going to discuss about DQM integration with UI component.

In the part 1 of this series I discussed about the basic settings of DQM with SAP CRM.In this part I will discuss about the integration of DQM service with UI Component.

DQM service is only supported in specific objects. As I am working in Utilities domain, I have integrated the DQM with Business Partner address and Customer Move In process.

The following simple steps needs to be done to integrate the UI component with DQM service:

• Open the UI component in transaction BSP_WD_CMPWB. In this case I have taken the UI component BP_ADDR
• Go to Component Usage in the Runtime repository editor
• Add the component usage : Used Component /FLDQ/DQXI_PV

After the UI Component has been integrated with DQM then the address will get reviewed from DQM as shown in the example below.

This completes the second part about DQM integration with UI component. In the next section I will discuss about the additional features of DQM

In the last two parts of the series I have discussed about the steps about DQM integration. In this section I will discuss about the additional functionalities provided by DQM which could be activated.

DQM provides the following functionalities in addition:

• Duplicate business partner check can be activated based on the address fields. The functionality can be activated in the following IMG : SPRO > SAP NetWeaver>Application Server>Basis Services>Address Management>SAP BusinessObjects Data Quality Management> Activate/Deactivate DES functionality
• Maintain fields for duplicate hit list displays : This IMG setting describes the fields which should be shown for identification if duplicate business partner is identified
• Geoloc services can also be activated with DQM. Geoloc services updates the latitude and longitude of an address.
  • The following settings needs to be done in the IMG :SAP NetWeaver>General settings>Set Geocoding>Register Geocoding Program in the System

• Assign Geocoding Program to Countries : In this setting the Geo program is assigned to the country

• In addition there are a list of mass programs provided for cleanup of address. The main program for this process is /FLDQ/RSADRINI which can be scheduled for the initial cleanup of address.

This brings an end to the series of DQM integration with SAP CRM.  Hope the information provided is helpful to the community.

Summary

Aim of this document is to provide technical developers with some basic code and tool to traverse from Transaction Type to Schema(s), which have the type assigned. Then it lists a list of all Categories, for which it is valid.

Author(s):    Pavel Duchac

Company:    Fujitsu

Created on:  26/02/2015

Author Bio

Pavel is a freelance CRM Consultant, currently working with Fujitsu Australia. He has worked on multiple SAP CRM implementations across Europe and Pacific region.

Background

Multilevel Categorization in SAP CRM for Service Requests is used to display and save hierarchy (of categories), which semantically refers to a certain aspect of business object or business process.

This allows us to capture the attributes in a systematic manner:

You can link schemas with applications either via Subject Profile or via combination of Transaction Type/Catalog Category.

We needed to get all the schemas, which had a particular Transaction Type assigned. Then we needed to get all the categories for all the Schemas we were able to find.

SAP provides functionality which returns all the Application Areas assigned to particular Schema. You can use class CL_FSSC_RDS_CATEGO_DATA_PRO.

To retrieve the information in reverse is more difficult and there is no standard mean.

Following code shows one way how this can be achieved.

REPORT zucs_crm_cat_schema01.
* Structures
DATA: lv_object_ext_key TYPE crm_erms_cat_ob_extkey,      ls_cate_data      TYPE fssc_rds_s_catego_category,      es_schema_data    TYPE crmt_erms_cat_as_buf.
* Tables
DATA: lt_tab       TYPE TABLE OF crmc_erms_cat_sp,      lt_guids     TYPE TABLE OF guid,      lt_olink     TYPE crmt_erms_cat_ob_update_ttype,      lt_link      TYPE crmt_erms_cat_ln_update_ttype,      lt_cate_data TYPE fssc_rds_t_catego_category.
* Objects
DATA: gr_file_server   TYPE REF TO cl_fssc_rds_catego_file_srv,      lr_schema        TYPE REF TO if_crm_erms_catego_aspect,      mr_data_provider TYPE REF TO cl_fssc_rds_catego_data_pro.
FIELD-SYMBOLS <ls_guid> TYPE guid.
SELECTION-SCREEN BEGIN OF BLOCK one WITH FRAME TITLE text-001.
PARAMETERS: p_ptype TYPE crmt_process_type DEFAULT 'ZFIA'.
SELECTION-SCREEN END OF BLOCK one.
CREATE OBJECT gr_file_server.
* Get a subset of tx types / cat types and subj profiles
SELECT * FROM crmc_erms_cat_sp INTO TABLE lt_tab.
LOOP AT lt_tab ASSIGNING FIELD-SYMBOL(<ls_tab>).  IF <ls_tab>-scheme_val(4) EQ p_ptype.    APPEND INITIAL LINE TO lt_guids ASSIGNING <ls_guid>.    MOVE <ls_tab>-scheme_guid TO <ls_guid>.  ENDIF.
ENDLOOP.
DELETE ADJACENT DUPLICATES FROM lt_guids.
* Get Object IDs from OBJ_EXT_KEY
IF lt_guids IS NOT INITIAL.  LOOP AT lt_guids INTO <ls_guid>.    MOVE <ls_guid> TO lv_object_ext_key.    CALL METHOD cl_crm_erms_cat_ob_db=>get_object_links      EXPORTING
*       iv_object_guid            =        iv_object_extkey          = lv_object_ext_key      IMPORTING        et_object_links           = lt_olink
*       es_object_link            =      EXCEPTIONS        object_link_not_found     = 1        invalid_search_parameters = 2        OTHERS                    = 3.    IF sy-subrc <> 0.
*   Implement suitable error handling here    ELSE.
*     Filter all ASP IDs by their status - we want active Categorization schemas only ('V')      LOOP AT lt_olink ASSIGNING FIELD-SYMBOL(<ls_olink>).        CALL METHOD cl_crm_erms_cat_ln_db=>get_category_links          EXPORTING            iv_obj_guid               = <ls_olink>-obj_guid          IMPORTING            et_link                   = lt_link
*           es_link                   =
*           et_obj                    =          EXCEPTIONS            invalid_search_parameters = 1            OTHERS                    = 2.        LOOP AT lt_link ASSIGNING FIELD-SYMBOL(<ls_link>).
*         Get CRM categorization schema data.          CREATE OBJECT mr_data_provider            EXPORTING              iv_schema_guid = <ls_link>-cat_guid.          lr_schema = mr_data_provider->get_schema_inst( ).          IF lr_schema IS  BOUND.            CALL METHOD mr_data_provider->get_schema_detail              IMPORTING                es_schema = es_schema_data.            CHECK es_schema_data-asp-asp_state EQ 'V'. "Active Schema only            CALL METHOD gr_file_server->prepare_data_for_export              EXPORTING                iv_schema_guid = es_schema_data-asp-asp_guid                iv_with_attr   = 'X'              IMPORTING                et_cate_data   = lt_cate_data.
*           Result output            WRITE: 'Categories:'.            LOOP AT lt_cate_data ASSIGNING FIELD-SYMBOL(<ls_cate_data>).              WRITE:/ <ls_cate_data>-cat_id.            ENDLOOP.          ENDIF.        ENDLOOP.      ENDLOOP.    ENDIF.  ENDLOOP.
ENDIF.

The basics steps are first to define a Catalog, then Code Group Profiles and finally defining a subject profile.

1. Follow the following SPRO path:

2. Define Catalog:

    Define a catalog for every level of hierarchy level. (3 catalogs will create a 3-level categorization)

3. Next, define Code Group Profiles:

     Select the Catalog (defined in the previous step) and create a Code Group for it.
     One Code Group per Catalog.

     Proceed by creating Codes for your Code Groups.
     One Code for every value (values are per Catalog)

4. Next, define a Subject Profile

    Create a new Subject Profile. (One per Code Group Profile)

    Assign the relevant Code Group Profile and Code Groups

Lastly, log into CRM Web UI with the IC_MANAGER Business Role and find the Create Categorization Schema under the Knowledge Management Work Center:

Create a new Schema and make sure to assign it the appropriate Subject Profile:

Make sure here to declare the appropriate valid-from and valid-to dates in order to activate.

   Define your entire schema and save.

Assign to a transaction type and enjoy

Purpose

Overview

This document will elaborate to change Quote /order /contract status in Header & item as well.

Below are the details..

Go to se37  --> FM CRM_STATUS_UPDATE

After run FM need to choose JEST_UPD. Next

Please the above steps need to perform when user not able to change status's then use above FM & set right status's.

Thanks,

sanjeevb

Many companies have implemented SAP CRM for the Inbound Contact Center scenario. One of the biggest challenges that they find is the integration with the backend ECC system for quote and order creation at the time the customer is in the phone line waiting for the confirmation number. In this aspect, SAP offers to implement different standard approaches.

List of Standard Solutions:

1. Implementing SAP CRM Sales integrated with SAP SD Backend, the agent of the contact center will create a sales order object in SAP CRM  during the inbound call. This order will get replicated into SAP ECC. For this option you need to make sure that SAP CRM has configured all the pricing, material master and order customizing properly. If the company has implemented SAP SD for many years, a harmonization of SAP CRM will be necessary for all the validations applied in user exits/badis in the SAP ECC SD module.
2. Another solution would be the SAP CRM Lean Order WebUI Interface with a backend SAP SD module instead of SAP CRM. SAP CRM offers a Web Interface that routes the information through RFC into SAP SD and vice versa.The approach considers many validations of the backend of SAP SD because the RFC calls points to the same places as you were creating the order in the VA01 (except module pool screen validations). One of the biggest challenges of this solution is the performance, since we are calling the SAP SD from SAP CRM as many times as the user is hitting “enter”. Another challenge could be that Lean Order does not support configurable products into the maximum extent as you were implementing SAP SD.
3. The last option would be the so-called “transaction launcher”. This solution is a technique to call SAP ECC through a HTTP request session that shows the SAP GUI in a web-browser. This solution will cover all the scenarios of your pricing and order creation but the performance is not good if you consider a customer in the line waiting for the order confirmation. Additionally, there is no standard way to configure the linkage between the order confirmation and your interaction record object.

Besides the standard solutions, I would like to share a new technique for integrating the SAP CRM with SAP ECC. This method is based on the SAP shortcut sending parameters to the process of Order/Quote Creation or any transaction you desire.

Features:

• Ability to call any transactions of SAP ECC from SAP CRM
• Multiple SAP logins available
• Roundtrip or callback information to SAP CRM. For example, an order gets created, and SAP CRM could trace the order from the interaction record. The order confirmation is sent back to SAP CRM
• SAP GUI shortcut has magnificent performance in the integration with SAP CRM during a telephone call
• Implemented in more than five contact centers

Please "click" on the following slides:

As you can see, we have inserted a button in the account overview that calls the VA01 (Order Creation in SAP ECC) sending over the parameters such as Customer number, Order Type, Contact Person. The order creation will be very fast. As soon as the interaction with the client is finished, we can connect the order number with a particular interaction record of SAP CRM.

Now let's take a look at the scenario for displaying past orders/quotes created from SAP CRM.

We have created a web ui component in the account overview that lists the previous orders of the customer. In this particular component, we can click on the quote/order and jump again into SAP ECC for visualization.

Additionally, we have implemented a component in the Account overview where you can add categories and transactions or websites for your convenience:

The user can click over the transactions and the SAP ECC GUI will open the corresponding transaction or Website URL.

Please feel free to connect me if you need any advice on how to implement a similar approach.

Federico Kamelhar

Moderation: Please, do not insert your contact data in a SCN blog.

Purpose

This page shows how to find out the outbound mail information with their linked service ticket no in ERMS.

Overview

In ERMS we can easily find out the inbound mails and out outbound mails Information but it’s difficult to find out the outbound mail with their linking service ticket number information.

This wiki will help you how to find out the outbound mails with their linking service ticket numbers before that I will explain what are the tables which are frequently used in ERMS.

Detailed Explanation about ERMS tables

CRMD_ERMS_HEADER : This will gives Header Details information.

This table will give's the information about mails like From mail address,TO mail address, Creation Date, Changed Date, Status, Work Item ID, Employee responsible etc..

each and every mail will attached with there corresponding service ticket.

CRMD_ERMS_E21O: link email to one order.

This table will give’s the information about the Linkage from E-Mail to one order object. Here every mail id have there own id that is CON_ID and linked GUID. This GUID will gives the service ticket no.

CRMD_ERMS_CONTNT: Get subject of the mail.

This table will give's the E-Mail subject information based on CON_ID.

CRMD_ERMS_EVENTT: This will give’s the E-Mail event text.

This table will give's Email event text which is like replied, rejected,process, new etc..

CRMD_ERMS_STATUS:  E-Mail status.

This table will give's E-Mail Status Description based on Status_id.

SOOD,SOST,SOES this table are helpful to find out the outbound mail info with there linked service ticket number.

SOOD: SAPoffice: Object definition.

This table will give's the email information like Created Date, Created Time,Description based on OWNTP = 'USR'.

SOST: SAPoffice: Status log table.

This table will gives the Status log details.

SOOS : Send process.

This table will gives the TO,CC and BCC mails information.

SOES: This will gives the outbound From mail address , outbound To mail address and Status.

If we observe standard ERMS Process For each service ticket under there is inbound and outbound mails. This mails are having their own ids that is CON_ID.

if we want to know the service ticket no for the replied mail id we have a function module.

In that function module we have to pass CON_ID  and object type = ‘SOFM’ then will get guid for the corresponding linked service ticket.

Pass that GUID into crmd_order_read or crmd_orderadm_h you will get service ticket no.

     lv_root-objkey = lv_conid.
      lv_root-objtype = 'SOFM'.

* Get the persisted doc flows
      CALL FUNCTION 'SREL_GET_NEXT_RELATIONS'
        EXPORTING
          object         = lv_root
          max_hops       = 1
        TABLES
          links          = lt_bor
        EXCEPTIONS
          internal_error = 1
          no_logsys      = 2
          OTHERS         = 3.
      IF sy-subrc <> 0.
        RETURN.
      ENDIF.

      READ TABLE lt_bor INTO ls_bor INDEX 1.
      IF sy-subrc = 0.
        lv_guid = ls_bor-objkey_a.

APPEND lv_guid TO it_header_guid.

        CALL FUNCTION 'CRM_ORDER_READ'
          EXPORTING
            it_header_guid       = it_header_guid[]
          IMPORTING
            et_orderadm_h        = it_orderadm_h[]
          CHANGING
            cv_log_handle        = lv_log_handle
          EXCEPTIONS
            document_not_found   = 1
            error_occurred       = 2
            document_locked      = 3
            no_change_authority  = 4
            no_display_authority = 5
            no_change_allowed    = 6
            OTHERS               = 7.
        IF sy-subrc <> 0.
*   Implement suitable error handling here
        ENDIF.

        READ TABLE it_orderadm_h INTO wa_orderadm_h WITH KEY process_type = 'ZSRT'.

        IF sy-subrc <> 0.
        wa_data-service_tkt =  wa_orderadm_h-object_id.

       ENDIF.
      ENDIF.

Actual Requirement :

I have designed one BSP Component which is like search and result and custom model too.

Step by step procedure to achieve this requirement.

1)       Create one custom model.

2)      create search/result bsp component.

3)      Attach model to that component.

4)      Create search and result view.

Here we have so many blogs which is already explained how to create custom model and search/result bsp component.

So that I haven’t explain procedure to create model or search/result view.

Creating Custom Search/result view link..

http://scn.sap.com/docs/DOC-26564

http://scn.sap.com/community/crm/webclient-ui-framework/blog/2012/05/29/custom-component-based-on-custom-genil-component

Creating Custom Model..

http://scn.sap.com/community/crm/webclient-ui-framework/blog/2012/05/28/custom-genil-object-model-an-overview

ZCRM_ERMS_SRVO this is my structure which is I have used in my model.

This is the my Custom Model class ZCL_CRM_ERMS_SRVO.

Redefine the method IF_GENIL_APPL_INTLAY~GET_DYNAMIC_QUERY_RESULT and write the logic.

*****************************************************
*    Declaring  select-options                      *
*****************************************************
  TYPES : BEGIN OF t_selopttab,
           sign   TYPE crmsignran,
           option TYPE crmoptran,
           low    TYPE symsgv,
           high   TYPE symsgv,
          END OF t_selopttab.

  DATA : it_sel_objdes      TYPE STANDARD TABLE OF t_selopttab,
         it_sel_crdate        TYPE STANDARD TABLE OF t_selopttab,
         it_sel_emaifrom    TYPE STANDARD TABLE OF t_selopttab,
         it_sel_emailto     TYPE STANDARD TABLE OF t_selopttab,
         wa_sel             TYPE t_selopttab,
         wa_param           TYPE genilt_selection_parameter,
         lr_entity           TYPE REF TO if_genil_cont_root_object,
         lr_attr_props       TYPE REF TO if_genil_obj_attr_properties,
         v_key               TYPE string,
         lv_conid            TYPE string.

  DATA :  it_data TYPE STANDARD TABLE OF zcrm_erms_srvo,
          wa_data TYPE zcrm_erms_srvo,
          it_srvkt TYPE STANDARD TABLE OF zcrm_srvtkt_emp,
          wa_srvkt TYPE zcrm_srvtkt_emp.

  DATA :  lv_root          TYPE borident,
          lt_bor           TYPE crmt_ic_irec_links,
          ls_bor           TYPE relgraphlk,
          lv_guid          TYPE swo_typeid,
          it_header_guid   TYPE crmt_object_guid_tab,
          it_orderadm_h    TYPE crmt_orderadm_h_wrkt,
          wa_orderadm_h    TYPE crmt_orderadm_h_wrk,
          lv_log_handle    TYPE balloghndl.

*****************************************************
*            DECLARE THE TYPES                      *
*****************************************************

  TYPES : BEGIN OF t_sood,
          objtp  TYPE sood-objtp,
          objyr  TYPE sood-objyr,
          objno  TYPE sood-objno,
          objdes TYPE sood-objdes,
          crdat  TYPE sood-crdat,
          crtim  TYPE sood-crtim,
          END OF t_sood,
          BEGIN OF t_sost,
          rectp  TYPE sost-rectp,
          recyr  TYPE sost-recyr,
          recno  TYPE sost-recno,
          objtp  TYPE sost-objtp,
          objyr  TYPE sost-objyr,
          objno  TYPE sost-objno,
          msgid  TYPE sost-msgid,
          END OF t_sost.

  TYPES   : BEGIN OF t_soes,
            rectp  TYPE soes-rectp,
            recyr  TYPE soes-recyr,
            recno  TYPE soes-recno,
            msgid  TYPE soes-msgid,
            msgv1  TYPE soes-msgv1,
            msgv2  TYPE soes-msgv2,
            msgv4  TYPE soes-msgv4,
            status TYPE soes-status,
            END OF t_soes.

  DATA : lv_msgid TYPE symsgid,
         lv_langu TYPE char2 VALUE 'EN',
         lv_msgno TYPE char3,
         lv_msgv1 TYPE string,
         lv_msgv2 TYPE string,
         lv_msgv4 TYPE string,
         lv_message TYPE string.

  DATA : gt_sood TYPE STANDARD TABLE OF t_sood,
         gs_sood TYPE t_sood,
         gt_sost TYPE STANDARD TABLE OF t_sost,
         gs_sost TYPE t_sost,
         gt_soes TYPE STANDARD TABLE OF t_soes,
         gs_soes TYPE t_soes.

*****************************************************
*    Search Qurey and Selection Screen inputs       *
*****************************************************

  IF iv_query_name = 'SEARCH_SRVO'.

    LOOP AT it_selection_parameters INTO wa_param.
      CASE wa_param-attr_name.
        WHEN 'DESCRIPTION'.
          MOVE-CORRESPONDING wa_param TO wa_sel.
          REPLACE ALL OCCURRENCES OF '*' IN wa_sel WITH '%'.
          APPEND wa_sel TO it_sel_objdes.
        WHEN 'FROM_DATE'.
          MOVE-CORRESPONDING wa_param TO wa_sel.
          APPEND wa_sel TO  it_sel_crdate.
        WHEN 'EMAIL_FROM'.
          MOVE-CORRESPONDING wa_param TO wa_sel.
          APPEND wa_sel TO it_sel_emaifrom.

        WHEN 'EMAIL_TO'.
          TRANSLATE wa_param-low TO LOWER CASE.
          TRANSLATE wa_param-high TO LOWER CASE.
          MOVE-CORRESPONDING wa_param TO wa_sel.

          APPEND wa_sel TO it_sel_emailto.
      ENDCASE.
      CLEAR : wa_param,wa_sel.
    ENDLOOP.

* <---data fetching logic based on selection screen inputs--->

    SELECT objtp objyr objno objdes crdat crtim INTO CORRESPONDING FIELDS OF TABLE gt_sood FROM sood
                                                                                  WHERE crdat IN it_sel_crdate
                                                                                  AND   owntp = 'USR'.

    IF gt_sood[] IS NOT INITIAL.

      SELECT rectp recyr recno objtp objyr objno msgid FROM sost INTO CORRESPONDING FIELDS OF TABLE gt_sost
                                                      FOR ALL ENTRIES IN gt_sood WHERE objtp = gt_sood-objtp
                                                                                 AND   objyr = gt_sood-objyr
                                                                                 AND   objno = gt_sood-objno
                                                                                 AND   msgid = 'SO'.
      IF gt_sost[] IS NOT INITIAL.
        SELECT rectp recyr recno msgid msgv1 msgv2 msgv4 status FROM soes INTO CORRESPONDING FIELDS OF TABLE gt_soes FOR ALL ENTRIES IN gt_sost
                                                         WHERE   rectp = gt_sost-rectp
                                                         AND     recyr = gt_sost-recyr
                                                         AND     recno = gt_sost-recno
                                                         AND     msgv1 IN it_sel_emailto
                                                         AND     msgv2 IN it_sel_emaifrom.
      ENDIF.
    ENDIF.

    LOOP AT gt_soes INTO gs_soes.

      READ TABLE gt_sost INTO gs_sost WITH KEY rectp = gs_soes-rectp
                                               recyr = gs_soes-recyr
                                               recno = gs_soes-recno.
      IF sy-subrc = 0.

        READ TABLE gt_sood INTO gs_sood WITH KEY objtp = gs_sost-objtp
                                                 objyr = gs_sost-objyr
                                                 objno = gs_sost-objno.
        IF sy-subrc = 0.

          wa_data-objtp = gs_sood-objtp.
          wa_data-objyr = gs_sood-objyr.
          wa_data-objno = gs_sood-objno.
          wa_data-description = gs_sood-objdes.
          wa_data-from_date = gs_sood-crdat.
          wa_data-send_time = gs_sood-crtim.

          wa_data-email_from = gs_soes-msgv2.
          wa_data-email_to = gs_soes-msgv1.

          lv_msgid = gs_soes-msgid.
          lv_msgno = gs_soes-status.
          lv_msgv1 = gs_soes-msgv1.
          lv_msgv2 = gs_soes-msgv2.
          lv_msgv4 = gs_soes-msgv4.

          CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
            EXPORTING
              input  = lv_msgno
            IMPORTING
              output = lv_msgno.

          CALL FUNCTION 'FORMAT_MESSAGE'
           EXPORTING
             id              = lv_msgid
             lang            = 'EN'
             no              = lv_msgno
             v1              = lv_msgv1
             v2              = lv_msgv2
*         V3              = lv_MSGV3
             v4              = lv_msgv4
           IMPORTING
             msg             = lv_message
*       EXCEPTIONS
*         NOT_FOUND       = 1
*         OTHERS          = 2
                    .
          IF sy-subrc <> 0.
* Implement suitable error handling here
          ENDIF.

          wa_data-status = lv_message.

          CLEAR : lv_msgid,lv_msgno,lv_msgv1,lv_msgv2,lv_msgv4.

          CONCATENATE gs_sood-objtp gs_sood-objyr gs_sood-objno INTO lv_conid.
          wa_data-conid = lv_conid.

          SHIFT lv_conid BY 17 PLACES RIGHT.

          lv_root-objkey = lv_conid.
          lv_root-objtype = 'SOFM'.

* Get the persisted doc flows
          CALL FUNCTION 'SREL_GET_NEXT_RELATIONS'
            EXPORTING
              object         = lv_root
              max_hops       = 1
            TABLES
              links          = lt_bor
            EXCEPTIONS
              internal_error = 1
              no_logsys      = 2
              OTHERS         = 3.
          IF sy-subrc <> 0.
            RETURN.
          ENDIF.

          READ TABLE lt_bor INTO ls_bor INDEX 1.
          IF sy-subrc = 0.
            lv_guid = ls_bor-objkey_a.

            APPEND lv_guid TO it_header_guid.

            CALL FUNCTION 'CRM_ORDER_READ'
              EXPORTING
                it_header_guid       = it_header_guid[]
              IMPORTING
                et_orderadm_h        = it_orderadm_h[]
              CHANGING
                cv_log_handle        = lv_log_handle
              EXCEPTIONS
                document_not_found   = 1
                error_occurred       = 2
                document_locked      = 3
                no_change_authority  = 4
                no_display_authority = 5
                no_change_allowed    = 6
                OTHERS               = 7.
            IF sy-subrc <> 0.
*   Implement suitable error handling here
            ENDIF.

            READ TABLE it_orderadm_h INTO wa_orderadm_h WITH KEY process_type = 'ZSRT'.

            wa_data-service_tkt =  wa_orderadm_h-object_id.
          ENDIF.

          APPEND wa_data TO it_data.
        ENDIF.
      ENDIF.
      CLEAR : wa_data,lv_conid,lv_guid,it_header_guid,wa_orderadm_h,it_orderadm_h,lt_bor,lv_root,lv_log_handle.
      CLEAR : gs_soes,gs_sood.
    ENDLOOP.

*populating data into result

    LOOP AT it_data INTO wa_data.

      TRY.
          CALL METHOD iv_root_list->add_object
            EXPORTING
              iv_object_name = 'RESULT_SRVO'
              is_object_key  = wa_data
            RECEIVING
              rv_result      = lr_entity.

        CATCH cx_crm_genil_duplicate_rel .
        CATCH cx_crm_genil_model_error .
      ENDTRY.
      CALL METHOD lr_entity->set_attributes
        EXPORTING
          is_attributes = wa_data.

      CLEAR : wa_data.
    ENDLOOP.

  ENDIF.

this is the final output here we can come to know sent mails based on creating date.

Related Content

http://scn.sap.com/thread/1340812

http://scn.sap.com/thread/3181618

Related Documents

E-MAIL INBOUND CONFIGURATION- ALM: Incident Management#MAILINBOUNDCONFIGURATION-ALM:IncidentManagement-3SAPBusinessWorkflowandCommunicationSettings

How to set up Threading in ERMS

• Use CG3Y or CG3Z transaction if your system has EA-APPL component installed...Refer Blog Guide: how to download files from AL11?

        Or Refer Custom program  - Custom program Instead of cg3y and cg3z with F4 help

• In CRM, CG3Y transactions does not exists usually and use the transaction SXDA_TOOLS

Object Type: DXPROJECT

Program Type: BAPI

Program: CREATE

The above values are dummy info because the fields are mandatory to proceed , Then press the Copy file button (Copy).

• Report program RSSM_TRANSFER_FILE_TO_APPSERV for moving the CSV file to the app server

PC file (file to be written): e.g: C:\Users\Edwin\Desktop\sample.csv

App.Serv.file (to be written): e.g: /usr/sap/BIY/SYS/global/sample.csv

AL11 - transaction for checking the files in the app server (like /usr/sap/Q93/SYS/global/ )

This document will elaborate to change Quote /order /contract status in Header & item as well.

Below are the details..

Go to se37  --> FM CRM_STATUS_UPDATE

After run FM need to choose JEST_UPD. Next

Please the above steps need to perform when user not able to change status's then use above FM & set right status's.

Thanks,

sanjeevb

In this document I will discuss about the steps which needs to be done to integrate a Document Management System (Content Server) with CRM 7.

At first the Content Server needs to be defined which would be compatible with SAP. We have used Open Text Document Access 10.0.

The Content Server has to be integrated with CRM in transaction OAC0:

Once the content server has been defined then we need to decide the document types under which we will be storing the documents. These document types will be created as folders in the content server. This configuration is done in OAC2:

The document types is now assigned to business objects in transaction OAC3. In this transaction we decide which business objects will require the functionality of storing the documents. This configuration stores the combination of Business object, Document type and the content repository.

In addition a new external alias needs to be defined in the content repository service in SICF transaction as shown below:

With all the above mentioned settings the documents can be uploaded and viewed in the attachments assignment block in the respective object as shown below:

Hope the information shared helps the community.

Company Background

• 3rd largest captive finance company in US
• 7th largest finance company in US
• Currently employs over 3,000 associates nationwide
• Managed assets totaling $50 billion
• Offers financial services to support  purchase of Forklifts and commercial truck dealers across the USA
• Forklift Market Share 50.58%,   Truck Market Share 46.47%
• Electric and alternative fuel vehicle financing
• Fleet Financing for National Account customers
• Financing for industrial Warehouse products

Objective

To enable the customer’s Commercial Finance Group to support Distributors, Dealers, and end customers, provide quality service, reduce risks, grow the business, and pursue new opportunities by replacing current legacy systems (Origination: Web-based, Back-End: Mainframe)

Pain Points

• (A) Legacy Systems Environment
  • Mainframe based processing application – Inflexible, expensive to enhance and maintain and no longer supported by the software vendor. Huge customization on top of the delivered product
  • Web based Origination system – Inflexible, expensive to support and enhance and not integrated with any other system

• (B) Operational Environment
  • Inordinate number of manual, labor-intensive processes to support system deficiencies
  • Dealers send business elsewhere due to frustrations with legacy systems
  • Credit process is completely manual and unable to support projected growth (over 100% in 5 years)

• (C) Risks and Exposure
  • Legal risks in manual processes and limited system controls
  • Financial risks due to limited business intelligence
  • Satisfaction risk in not being able to meet brand commitment

Proposed Solution

Implement SAP Leasing (Asset Financing and Leasing)

Benefits Summary

• Increased efficiencies will enable the Commercial Finance department to support the forecasted increased volumes
• Improved data accuracy and reduced legal exposure
• Improved decision making
• End-to-End electronic integration with peripheral systems
• Ability to quickly enhance and introduce products

Strategic Blueprinting

• § Visualize “future-value” through multi-level Policy Objective (PO) Matrix (see Fig. 1)
• § Facilitate contentious business decisions through Structure for Enhancing Daily Activities through Creativity (SEDAC) Tool (see Fig. 2)
• § Agile blueprinting process (see Fig. 3)
  • foundation of AS-IS system documentation
  • TO-BE process definition aligned to PO Matrix
  • Strategy definition for build (listed below)
  • Demonstrate vanilla E2E scenarios
• § Build Strategies:
  • Organization Change Management Strategy
  • Scope and Change Management Strategy
  • Portal Strategy
  • BI and Reporting Strategy
  • Data Conversion Strategy
  • Functional Training and Documentation Strategy
  • Interface Strategy
  • Master Data Strategy
  • Security and Controls Strategy
  • Technology Strategy
  • Testing Strategy
  • Third Party Tools Strategy
  • Technical Knowledge Transfer Strategy
  • Release Strategy

Functionality Scope

1. Operating Lease
2. Direct Finance Lease
3. Loan

High Level BPML

1. Operational processes:

• § Origination and Credit Check
• § Finalize Contract
• § Invoicing and Payment processing
• § Default contract processing
• § Contract Changes (Customer Call Center)
• § End of Term Actions
• § Liquidate Inventory (Remarketing)

1. Master Data Maintenance

• § Setup Business Partner
• § Setup Products – Physical and Financing
• § Setup Pricing
• § Setup Financing Products & Programs

Product Architecture

• § Quotation / Origination: Legacy application (outside SAP)

• § Front-End (SAP CRM 7.0 UI)
  • Contract Creation / Validation
  • Tax Call (Vertex)
  • Inception
  • Billing
  • Customer Service (Customer Interaction Center)
  • Change Processes
  • Remarketing

• § Back-End (ECC 6.0)
  • FI-LA (Lease Accounting Engine)
    • Inception Accounting
    • Classifications (US GAAP)
    • Accrual / Deferral
    • Revenue Recognition
    • Payable creation
    • Periodic Postings
    • Asset creation

• FI-AA (Asset Accounting)
  • Asset management
  • Depreciation postings

• FI-CA (Contract Accounting)
  • Receivables Management
  • Dunning
  • Payables Management
  • Payment Hierarchy
  • Incoming Payments
  • Outgoing Payments

• FI-GL (General Ledger)
  • All financial postings

Financing Product

• Relationship with the Physical Product

• Define Payment Structure
  • Cash flows with due dates
    • Financed Amount
    • Residual Value
    • Annuity
    • Fees

• Payment Frequency
  • Monthly in Advance / Arrears
  • Quarterly in Advance / Arrears

• Step Payments

• Financing Options
  • EOT Purchase Options (Buyout)
  • FLEX Lease (3/2)

Change Processes

• Mid Term Changes
  • Payment Deferral
  • Change of Ownership
• End of Term Changes
  • Evergreen Lease
  • Extensions / Renewal
  • Buyouts
  • Termination with Return
  • Balloon Loan Rollover
  • Repossession – Voluntary or Involuntary

Lessons Learnt during Integration Testing

Integration Testing

• Test for processes Focus is not to test every single configuration which should be done at unit level
• Don’t test for exceptions Empirical analysis of high-volume critical processes to be done prior to scenario selection
• Business owns testing Business should own testing and SI to support
• Expected results are mandatory Without expected results defined for all test cases, Offshore cannot be leveraged
• Test interfaces for correctness Interfaces should be tested not only or communication but also for all process variations
• Test Customer touch-points repeatedly Special focus on all customer communications with multiple cycle testing
• Multiple clients for testing Rigorous planning to be done if testing is done on multiple clients
• Involve End-Users early Involve future Power-Users early in testing cycles
• Accounting periods Special attention on Accounting periods for testing G/L
• Tax processing Test Tax processes standalone as well as integrated with E2E processes

Product Highlights

1. Supports Lease / Loan / Full Service Leasing Contracts
2. Dealer Financing Programs – Subsidy (Subvention) / Participation
3. Complex Pricing conditions can be created
4. FiMa (Financial Mathematics) provides wide flexibility to create payment structures, cash flows, financing views
5. Lease Accounting Engine (FI-LA) is very strong from financial mathematics standpoint
6. A wide variety of built-in contract change processes such as Renewal, Rollover, Early Buyout, Change of ownership, Change of Location etc.
7. SAP FI-CA supports a flexible payment hierarchy
8. FCC – Financial customer care integrates call center with accounts receivables system

Project Highlights

• Unique 4000+ task level requirements documented
• All requirements linked for future traceability and Change Impact
• Baseline Configuration of 3 critical business scenarios on Sandbox after Blueprint
• BPML created to Level 4 processes
• Total 14 Roadmap Strategy documents created to form basis of Realization
• Defining KPI’s for each L4 process to tie back to P/O Matrix objectives
• Rapid Implementation : Quick learning and implementation – Technical : CRM UI and Functional : Leasing updates
• Migration: First ever Leasing successful migration – super complex financial balancing
• Sales Tax integration: First CRM UI integration with Vertex ‘O’ Series
• Alternate solutioning: Fill Leasing ‘White Space’ with minimum and flexible  enhancement (Pass Through, Financing of Tax, etc.)
• Fast-Tracking training: Over 90 BPPs (Business Process Procures) created which quickly translated into training materials with minimum effort by Training Vendor (RWD)
• SAP Development: Unique development relationship with SAP – exchange of resources
• SAP Relationship: Multiple SAP liaisons – Strategic (External SteCo), Tactical (Weekly Status call), Operational (OSS/Daily call)
• Post-Implementation: No Severity 1 tickets logged since July 2008 and <30 Severity 2 tickets