SAP CRM Middle ware Modeling

SAP CRM Middle ware Modeling has A BDoc kind consists of a header and a body.The BDoc header consists of one single information section, the so-known as control segment.The BDoc physique consists of one or more data segments and of one error segment.The management segment merely incorporates header info, whereas the individual data segments contain the precise desk entries that make up the corresponding business object.The error section can be used to store error information.

Every data section incorporates phase fields, also known as segment attributes. These fields are mapped to actual data fields of physical database tables.In BDoc sorts used for knowledge alternate between cell shoppers and the CRM Server, an information section is mapped to precisely one database desk, whereas in BDocs used, for instance, on the consumer side solely, a data segment can also be mapped to a be a component of of tables or to a desk view.
BDoc segments are organized in a hierarchical fashion to model dependencies of data. That is achieved by specifying mother or father-little one relationships between segments.On prime of the hierarchy there is all the time a novel root knowledge segment. It comprises a unique root ID used to duplicate the BDoc to the cellular clients.Within the BDoc Modeler, it is doable to navigate from the BDoc overview level all the best way to the mapping of BDoc phase fields to bodily desk fields and their data elements.All information related to a BDoc is made seen and modifiable by detail viewing screens.Additionally, all tables, data parts and domains belonging to the BDocs can be viewed.Tools for the generation of modeling experiences and for consistency checking are also provided.

The BDoc Modeler (in CRM 2.0B) is an external (i.e. a non-R/3) software used for creating, displaying and modifying BDocs.All existing BDocs are listed in the BDoc Overview (navigation tree) of the BDoc Modeler. There you may select and broaden a BDoc to display its structure. The structure shows the hierarchical sequence of the individual information segments in addition to the mapped CDB tables.With the BDoc Modeler you can also display the most important points of a knowledge phase chosen within the BDoc Overview tree. These embrace the individual fields contained in the selected data segment in addition to the small print for each of those fie lds, for example, the sphere names throughout the data phase and the names of the corresponding CDB table fields.

There are two tools that modify each BDoc repositories, the RepGuardian and the BDoc Modeler.The latter also accesses the IDES database on the mobile repository server.The BDoc Modeler is a instrument with which you'll define and modify BDoc varieties and their technical attributes.The RepGuardian is a device with which you'll copy ABAP dictionary (DDIC) objects to each BDoc repositories.The ABAP dictionary is barely modified by the SAP GUI.

Create or modify?
Should extra information fields be added to an current BDoc, or is it a completely new object type that's being modeled? Within the former case it is usually adequate to add for example an additional section to an current BDoc, within the latter case a model new BDoc needs to be created.Will a model new BDoc only be used on the consumer or will it even be used for knowledge change between the cell client and the CRM Middle ware? Will the BDoc be used to retrieve data from the native consumer database ( i.e. are WHERE clauses required)?

The logical (phase) construction of a BDoc must be clearly outlined earlier than the BDoc Modeler is used to really define the BDoc.If the BDoc corresponds to a business object that is also uploaded to the OLTP R/3 system, the R/3 Adapter might have to know which discipline(s) in the section correspond to R/3 key fields.To specify the overall DBoc knowledge for a new BDoc sort, proper-click on the root node (labeled with VERSION 1.2) within the BDoc overview window and select Add BDoc... in the popup menu.The name of the BDoc (up to 30 characters) ought to replicate the content material of the BDoc and possibly also its purpose.

The quick title (as much as 14 characters solely as a consequence of DDIC limitations) identifies the BDoc on the CRM Middle ware. Make certain that the quick title is unique.Observe that BDoc name and short identify must lie within the customer namespace, i.e. begin with ‘Z’.When creating a model new BDoc, a BDoc kind needs to be specified:
  1. BDocs of sort Normal, Query and Special are used for exchanging data between the cell client and the CRM Middle ware and for information retrieval on the client, with various kinds of read access (see Cellular Application Studio for particulars).
  2. BDocs of kind Generic, Extract and Bulk are at present not used at all.
When a data alternate BDoc is obtained on the CRM Middle ware, an inbound operate module is called. If this subject is left clean, the following naming conference is used:

/1CRMG0/’ + BDoc Short Identify + ‘_I01

The phase name should lie in the customer name area, i.e. it must start with ‘Z’. Additionally the corresponding R/3 structure should be distinctive on the CRM server. The phase title mustn't start with ‘Z_’, for the rationale that era of the corresponding DDIC construction will fail. n Every phase consists of segment fields that correspond to fields of a bodily database table.Some further attributes of segments and section fields might be chosen that are related for the mobile client application only.

For information exchange BDocs (additionally known as Write-BDocs), each section must correspond to exactly one database table , for query BDocs (additionally referred to as Read-BDocs), a section could be mapped to fields from a quantity of tables.The section field mapping is done most comfortably by Direct Mapping: after specifying a database desk to map to, a selection of desk fields is made, and the corresponding phase fields (of the same name) are created and routinely mapped to the table fields.Handbook mapping is possible however crucial only in special instances (confer with the BDoc Modeler documentation for further details).

Be aware that the fields TR_STATUS, TASK, BEF_IMG and SENDBITS are added to the segment automatically.The Header of a BDoc message accommodates the message ID, the sender ID and information about the BDoc instance and BDoc type.The first data section of the body of a BDoc message is also known as root segment. In contrast to all different information segments, the foundation section solely contains one key field. All subsequent information segments include two key fields: an personal one and the one of the earlier data segment.For every phase (aside from the basis segment), a father or mother section is specified, inducing a certain hierarchy among the many segments of a BDoc.

On the BDoc Modeler, an Edit Copy of a BDoc type is produced when beginning to modify a brand new or current BDoc type. Modifications are stored regionally within the now Dirty Copy of the BDoc type.One can then decide to save the modifications domestically in addition to in the Middle war repository, however with out activation.When activating the changes, the technology course of on the CRM Middle ware is triggered. Upon exiting the BDoc Modeler, stored procedures might be generated within the IDES database of the connected cellular repository server (for additional improvement).

For data retrieval and show functions on the mobile client, it might be helpful and even necessary to embrace knowledge from two different tables into one single BDoc segment. This can be executed by mapping the segment to two or extra tables.A be an element of condition on a area widespread to each tables is then specified to be sure that matching data from the 2 tables are retrieved from the database when reading this segment.

Parameters of Bdoc

When utilizing a BDoc on the cell client for retrieving information from the local database, one may want to apply a certain situation limiting the information read into the BDoc, presumably to a single record.n It is possible to specify a quantity of BDoc parameters and to incorporate them in WHERE clauses which are then included within the saved procedures generated for the cellular client.

Example: Based on the example supplied , a saved procedure of the shape ‘... SELECT ... FROM ... SMOADRC ... WHERE SMOADRC.COUNTRY = COUNTRY ...’ is generated. When providing a combo field in the cellular software it is now possible to pick only these clients that reside, for instance, in Spain by specifying the parameter value COUNTRY = ‘Spain’ (or the identifier for Spain) when invoking the info retrieval.

BDoc parameters are outlined on the BDoc level. The parameter name must be chosen to replicate the subject title it'll later be used with in the WHERE clause. The parameter kind (knowledge element) may be chosen by straight specifying it, or by selecting it in accordance with an present section subject or table subject kind (data factor).WHERE clauses are also used in the CRM Middle ware to differentiate for instance between CAP and CON entries within the SOURCE subject of table SMOKNA1.

Compatible adjustments

Add new non-obligatory segments add new fields at the finish of segments regeneration of runtime objects run time objects can handle both old and new BDoc variations.Incompatible modifications add necessary segments, change section fields (not allowed) new BDoc sort (new entrance-finish software logic) deletion of segments.

Viewing BDoc Structure

Begin the BDoc Viewer: Transaction SMOGBV.Select the BDoc type (only works for BDocs which are energetic and used in the CRM Middle ware, and for which structures and code have already been generated).View the segment structure, the generated providers etc.Determine the structure name (DDIC title) of the section in the BDoc structure show above.Use transaction SE11 to view the phase structure.

Related Posts

SAP CRM Organizational Model
People Centric SAP CRM IntroductionCRM Interaction Center Agent Perform
CRM Interaction Center ManagementCRM Software Architecture
Mobile Scenarios in SAP CRMCRM Middle ware Software Distribution

CRM Middle ware System Architecture
CRM Middle ware Enhancement

No comments :

Post a Comment