portal7.info Online Source Download and Free Ebook PDF Manual Reference. Sap -crm-middleware-optimization-guide Printablefile. Free Download Books. Online Source Download and Free Ebook PDF Manual Reference. Sap-crm- middleware-optimization-guide-h Printablefile. Free Download Books . Quick introduction tutorial about SAP CRM middleware portal7.info guide contains about its components, tcodes and PDF user guides. Middleware tool to enable.
|Language:||English, Spanish, German|
|Genre:||Health & Fitness|
|ePub File Size:||18.38 MB|
|PDF File Size:||19.64 MB|
|Distribution:||Free* [*Sign up for free]|
Bonn. Boston. Juliane Bode, Stephan Golze, Thomas Schröder. SAP®. CRM Middleware Optimization. Guide. book Seite 3 Freitag, 3. August In the context of an SAP CRM landscape, Middleware refers to the R3 adapter, which is used to transfer data from the CRM to external systems. This book, based on the experience of SAP Active Global Support, helps you proactively avoid problems with CRM Middleware — whether they be performance.
In today's highly competitive business environment, the focus of top companies is increasing on its most valuable assets — customers. Thus, the companies require a suitable software solution to cater to its customers which is user-friendly, easily customizable, fully integrated, and can be implemented flexibly. Customer Relationship Management is a business strategy for optimizing customer interactions. It helps in understanding your customers, their needs and requirements. This way organization can achieve customer expectations with the types of services and products that he or she actually needs. NetWeaver provides the development and runtime environment for SAP applications and is used for the custom development and integration with other applications and systems. If the resolution can not be provided immediately by the front - end customer representatives they raise a ticket in SAP - CRM which is addressed by a more technically equipped personnel.
Reprocessing the queue will reproduce the dump. Failed outbound queues on the R3 will also usually have a corresponding short dump on the R3. Also, check for corresponding short dumps on the CRM. As mentioned previously, this is normal. A STOP entry has been set y the application.
The entry has been manually set by a user. This must be investigated from the application side. It may be that the queue is waiting for a dialog work process to become free, or that the queue has not been registered in SMQR inbound or the destination has not been registered in SMQS outbound.
However, if queues remain in this status permanently, or for a very long time, then this indicates a problem. Check for these symptoms. However, it is still necessary to permit the queues that already exist to be processed in order to maintain data consistency.
The CRM system is still busy processing only the inbound queues and no other work can be performed with the CRM system this also applies in particular for the system administrator. The processing time of the individual data records also multiplies due to the CPU bottleneck. The problems that BGS experienced in the last example were not caused by the number of inbound queues being too high, but due to the fact that the inbound queue scheduler occupied too many dialog work processes of the CRM system.
All work processes available to the inbound queue scheduler are used for the processing until all inbound queues are empty. You can only prevent this kind of overloading by limiting the number of dialog work processes that the inbound queue scheduler is allowed to occupy.
For this purpose, the inbound queue scheduler is assigned to an RFC server group. The first group without a name is the standard group. This group is always used if there is no explicit assignRFC server group www. In principle, several instances can also be assigned to a group. In such cases, when a user logs on, the instance with the best response times is determined automatically and the user is logged on to this instance.
To display the resource assignment of an instance or to change it, double-click the corresponding row. Activated 0 or 1 Parameters of the RFC server group Switch for activating the determination of resources. The default value is 5. The remaining percentage continues to be reserved for dialog and HTTP users, i. The default value is Maximum No. If the number of separate logons exceeds this value, the user is not assigned any further resources. Ideally, this value should not be greater than the Max.
If the number of dialog work processes used exceeds this value, the caller is not assigned any further dialog work processes. Minimum Number of Free WPs Quote for the number of dialog work processes that must be reserved for other users. If the number of free dialog work processes is less than the number specified in the quote, the caller is not assigned any dialog work processes.
The default value is 1.
If the number of entries used exceeds this value, the caller is not assigned any resources. The actual wait time is determined from the available resources. The fewer resources available, the longer the wait time. Profile parameters of RFC server group All settings that you implement in Transaction RZ12 are immediately active, however, they are only saved up until the next time when you restart the instance.
After you restart the instance, the settings are lost and the old values are active again. To save the values permanently, you must save them as profile parameters.
RZ12 Activated 0 or 1 Max. Assigning an RFC server group Figure 8. If you use a pure mobile sales scenario, online or Internet sales users must not be considered when the system is being optimized. In this case, almost all work processes can be made available to the RFC. In all other cases, you must limit the resources for the RFC in such a way that the users will still be able to continue using the system, even if the RFC load is high.
If the CRM system has more than one application server, you may find it useful to set up the RFC server groups in such a way that the RFC processing is restricted to the resources of one application server, while the online users use a different application server. By adopting this approach, you can ensure that the users and the RFC will not disturb one another. Optimum setting for the RFC server group www. The distribution of resources should reflect the actual load distribution — RFC load versus online load — in each case.
To prevent the inbound queue scheduler from using all work processes of the CRM system, you must set the Max. If the system has sufficient dialog work processes, the Minimum Number of Free WPs parameter should have the value 3, rather than the default value 1.
This ensures that you can still log on to this instance through the SAPGUI, even if the load on the system is very high.
This recommendation applies only to a pure mobile sales scenario or a pure RFC instance. When determining the Max. NET Connector. If you select a value that is too high, although the inbound queues will be processed quickly, the data will accumulate in other areas of the CRM Middleware because resources will not be available there.
Click Search Documentation. Some of these are listed in Table 8. The user who executes a transaction often acts as a filter for the performance analysis, in order to find the correct statistical data records or trace a particular action in the system.
Analysis transactions www. Otherwise, the queue processing is performed under the user ID that is currently processing a registered queue this does not have to be the same queue. Therefore, a queue entry is not necessarily processed further by the user ID that has written it into the queue; instead, it can be processed using a different user ID.
If both of these users have different rights, a user with insufficient rights may try to process the queue entries of another user. The resulting errors are very difficult to analyze because, generally, they rarely occur and can seldom be reproduced. There is little effort required, but the benefits are great.
You must perform the following steps to create a logical destination: Create a new internal connection in Transaction SM Select the corresponding queue. Click the Registration button. Confirm your entries. Repeat these steps until you have assigned a logical destination and therefore a separate user to all inbound queues in Transaction SMQR.
You can now see directly from the process overview Transaction SM50 which work processes are working on particular inbound queues. The user also proves to be helpful in other transactions. You can access the message flow statistics by using following specified path in the SAP Easy Access menu: You can choose between different statistics: Therefore, prior to a performance analysis, you should check to ensure that the statistics are written.
First, select Goto Activate statistics from the menu. To ensure that the statistics are written for the CRM Middleware, you should mark the checkbox in the Middleware Message Hub Statistic row in the active column. Both the Monitoring Message Flow and the Collector should be switched on for an analysis.
When you click the Last Minutes Workload button, the current load of the last x minutes of the CRM instance on which you are working is displayed. You can display statistics of one instance or all instances and choose between different time intervals.
In both cases, the layout of the results window is identical. You receive data about the number of BDocs per type that were processed in the time period, as well as data about the processing time, CPU time, wait time, database time and the number of Kbytes requested. You also receive additional information about the total time and the average time for all time data see Figure 8.
Transaction SM51 can used to determine how many dia WPs have been configured for any system. Check transaction SMQS. In order to optimise performance, this entry should be excluded as described in note In client there must be entries both for. All of these entries should also be excluded. Either of these symptoms can be the result of performance issues. Check also transaction SM58 for error messages. Which data are sent to individual external sites ie — sites other than the CRM or CDB is governed by which subscriptions are assigned.
For further information on the Conntrans application and tips on troubelshooting problems with conntrans, please refer to the following Wiki links:. Conntrans Survival Guide. Commonly used notes for conntrans and communication station. CRM Mobile Sales. Welcome , Guest Login Register. Getting Started Store. A t tachments 0 Page History.
Created by Former Member , last modified on Dec 19, Purpose You need information to help resolved common problems with CRM middleware. Start Initial load R3AC1: Important qRFC Transactions: There are 3 types of download objects: Queue Analysis. As mentioned previously, this is normal. A STOP entry has been set y the application. The entry has been manually set by a user.
Further points to note: To find the state, proceed as follows: If it becomes necessary to open a Sapnet message include all of this information in the message text.
Refer to the note below that corresponds to the BDoc s in question: Only CDB data are relevant for mobile cleints. When a mobile client is created and activated an Extract should be performmed to send required data to the client. After the first extract has been performed, data are send and received to and from mobile clients using the conntrans application installed on the client. Problems with Conntrans: For further information on the Conntrans application and tips on troubelshooting problems with conntrans, please refer to the following Wiki links: No labels.
Former Member. Permalink May 27, Pradeep Parida. Nice blog.