One-Order concept
In CRM all types of transactions are technically integrated into One-Order framework. Order consists of Segments. Examples are
ORDERADM_H ORDERADM_I PARTNERS SALES
Each segment is mapped to database table. Guid is the key to the One-Order transaction. Interaction layer provide interface to the database layer Different types of transactions use segments that are relevant to it to captures the data. Eg.
Activity
ORDERADM_H
Shared Segments
PARTNERS
PARTNERS
. .
OPPORT_H
. .
ACTIVITY_H
Some of the segments and there corresponding database tables are listed below
Tip
ORDERADM_I CRMD_ORDERADM_I
CRMD_PARTNER CRMD_CUSTOMER_H CRMD_CUSTOMER_I CRMD_OPPORT_H
Segment Name will part of the table name and function modules used to read data or update,
Architecture
User Interface
Interaction Layer Database Layer
Advantages
Provides Isolation of User Interface & Business logic GUI programmers need not handle any database operations
Controls screens in
Customer Interaction Center (CIC) CRMD_ORDER transaction Screen control can be customized using the transaction CRMV_SSC. Can be used to perform the following
Screen Profile
Allows different screens to be assigned to same category of transaction based on the transaction type.
Panels
Holds the subscreen areas
Subscreen Areas
Subscreen areas holds the screens.
Tabstrips Panel
Holds the various tabs that are displayed
A custom transaction Z_OP of Opportunity type transaction is configured to show a custom screen. Steps 1 Define Custom program for the screen profile type