Middleware monitoring

Hi Everybody,
Iam doing middleware monitoring. In SMW01, Iam getting an error with Bdoc description has "Partially send, receivers have errors" The error message is-" Exchange object name could not be determined". If anyone know how to rectify this error please reply. Useful replies will be suitably rewarded.
Thanks and Regards,
Deepika

Hi Deepika,
Can you provide Some more details like BDOC type, Flow context description and Queue name.
If possible send the screen shots to this id.
ranganadh1981'at'yahoo.com
in the above address 'at' stands for @
Regards
Nadh

Similar Messages

Middleware Monitoring (Trn: SMW01) BDoc Msgs

Hi All,
We are currentely working on CRM 4.0 and i am facing an issue in the area of Middleware Monitoring (Trn: SMW01) where we monitor BDoc Msgs. There are aproximately 1000 BDocs in error state with "BDoc Validation Error" for a particular period e.g. from 1st Feb 2008 to 29th Feb 2008.
I was told that i can reprocess them (by selecting some BDocs regularly).
While Reprocessing them there is a pop-up stating "Reprocessing BDocs can cause inconsistency"
But still our team is going for "YES" option.
Can we do this?
or Is there any other way we can make them clear. Kindly advise me in this issue. It is bit URGENT and need to be addressed immediately.
Thanks and Regards,
Ramana Rao

Hi
It is not suggested to reprocess the error BDoc.
BDocs in Error status should be marked as deleted to avoid re-processing that might lead to inconsistencies.
By marking the BDoc as deleted saving its IDs the object ID is added to the BDoc Recovery Work List which allows for further analysis in transaction SMW3RC.
Two main selection options are possible from SMW3RC: Displaying the work list and displaying the process list.
The work list is the list of BDoc messages which needs to be recovered. As soon as a BDoc message is deleted in SMW01 by saving the identifiers, it is stored into that work list.
This list can be analyzed by the administrator who must decide which operation is adequate for processing the data. Possible operations are:
1. Extracting the data from CRM (Post)
2. Create a Request from R/3
3. Create a DIMA comparison
4. Mark the BDoc message as completed
As soon as the administrator has selected the desired operation, the entries are removed from the work list and stored into the process list.
From the process list, it is possible to start the desired operation.
For mass processing of the process list use transaction SMW3RCW

Middleware Monitoring--Exchange Object Name

Hi
I am monitoring CRM middleware. In tcode SMW01 Iam getting an error as "Partially send, receivers have errors". Its long text indicates "Exchange object name could not be determined". Anybody knows wht this exchange object is and how to solve this error.
Useful suggestions will be awarded.
Regards
Deepika

Hi all,
Can anybody who have worked with middleware tell why the problem is appearing?
Thanks
Deepika

CRM Middleware Monitoring Cockpit

Hi Gurus,
Iam new to the Middleware when i go to the TC - SMWP,
for the Generation Information -> Missing indexes Status is Yellow
for the Runtime Information -> Adapter Status Information -> Parameters in R/3 Backend(s) -> ECC System -> Parameters for object load management Status is Yellow
Does this lead to any problem or not and how to make it green can anybody help me out
Thanks

Hi Devi,
Yellow status means a pending request/Bdoc processing.
Generally, if you have R/3 CRM connection, then yellow means notification is not received from R/3 system since a bdoc being send to R/3 system from CRM system.
can you elaborate upon the description you get for the yellow status bdoc.
Best Regards,
Pratik Patel
<b>Reward with Points!</b>

'Item Not Found 'error in Middleware Monitor

Hi,
Monitoring the MW Monitor..
There is a BDoc Validation error. BDoc type is 'BEABILLDOCCRMB'.
The message on the error segment says ' Item was Not found', Module CRM_DOWNLOAD_BEA_VAL.
Can anyone help me.
Pratima

Hi Animesh,
There is an Accounting document and it is transferred to finance.
But it is still in the 'Item Not found' state in the MW monitor with a validation error.
Regards,
Pratima

CRM Middleware Monitoring: Adapter Status Information. Waiting Objects

Hello
I am having a problem sending messages of type RSREQUST from CRM to BW
I have been seeing in the SMWP transaction that we have waiting objects in Request Status of Adapter Status Information.
I dont know how I can start it or solve this error
Thanks in advanced
Best regards

Hi,
It seems that the maximum number of parallel processing threads(usually 5) have been set in ur system which is why the objects are in status WAIT. Status WAIT is not an error. To correct, would you check the transaction R3Ar3 for all requests tht are in running status. If you have 5 requests here, abort one or two out of them. Then go to SMQ2 and select the queue tht is in status WAIT. Unlock the queue immediately. It should change to status "READY" and should flow across to BW.
Reward points if it helps !!
Rgds
Priyanka Bansal

Validation error 'Item not found' in Middleware

Hi,
In the middleware monitor, I have some bdocs failed with the validation error ' Item was not found. Validation error occured. module CRM_DOWNLOAD_BEA_VAL, BDoc Type BEABILLDOCCRMB'.
When i look at the document numbers associated , they do exist.
It is in this state for a long time.
Can anyone help.
Regards,
Pratima

Hi Venkat,
There are no messages in the outbound or inbound queue releated to these bdocs.
These bdocs exist only in the monitor with validation error.
Regards,
Pratima

Production support - Middle ware monitoring checklist

HI Forum,
I have been assigned to a PPS project and need to handle middleware related activites. I have a basic checklist to go about with.
But i need the help of this forum to enhance the checklist.
Request you all to share some points like imp tcodes, reports, tables etc to be checked.
Client envt:
CRM 5, ECC 6 with sales service and IC web in place.
CRM is the leading system.
THanks in anticipation.

Nicol,
I had prepared a comprehensive middleware monitoring and understanding doc. while on a similar AMS (application management & support) project.
Hope it is useful.
Julius

CRM Monitoring T-codes

Hi All,
Can any of them help me in monitoring steps and T-code used while monitoring a CRM Server.
Regards,
Sandeep Singh

Hi ,
If you are looking for CRM Middleware monitoring T-Codes . Here are few :
1) SMW01 -- Display Bdoc
2) SMW02 - Display Bdoc summary
3) To view the Unprocessed Bdoc Type in the sytem use : SMW03
4) SMW20 - for Bdoc Procsing
5) SMWMFLOW - Monitoring Message Flow
For qrfc related monitroing check
SMQR -- QIN Scheduler ( Inbound Queue checking )
SMQS -- Qout Scheduler ( OutBound Queue checking )
If you have to monitoe R&R queues use transaction : SMOHQUEUE
Hope this helps
Vinayak

SYSFAIL Error in SMQ2 - Transfer of material from R/3 to CRM

Hi,
We are using standard BDOC to transfer material from R/3 to CRM. BDOC Type is PRODUCT_MAT, Queue name is R3AD_MATERIA<Material No>.
There are some queues which are struck in SMQ2. There are no struck queues in R/3. The struck queue has the status SYSFAIL and when I double click, it shows Message - Error in Mapping (Details: transaction SMW01)
I checked transaction - SMW01. The queue name which is in SYSFAIL status is not coming up in SMW01.
I do not understand whereelse I can see the detailed error message.
This error does not occur for all articles.
As I don't have sufficient knowledge in CRM and BDOCs, any pointers regarding the issue will be very much helpful.
Thanks and Regards,
Lakshmi

Hi Lakshmi,
Please follow as below:
SMWP-Middleware Monitoring Cockpit- This transaction gathers a wide set of information about the status of the Middleware & Downloads in both the CRM system, the R/3. All statuses should normally be green but there may be some circumstances which stop this occurring. Expand the section Generation Information which refers to the generation of BDoc Types. Where ever you see error you can right click and Select Analysis Tool then right click and check the error.The log shows the error.
SMQ2- Select a Queue and select Display. Queues connected to R/3 start with a queue name of R3A/D.
Double click on the Status field i.e SYSFAIL. Reason will be shown.In your case it is u201CError in Mapping (Details: transaction SMW01)u201D. Then Continue and select a queue and select Display.You can see the Individual BDocs are beoing displayed.
SMW01- give Bdoc Type as " Product_mat". If it is not displaying then I request you to check if all the objects are generated properly.This may also happen if the objects are not properly generated.Use tx-Genstatus. That will give you a list of error objects to be generated.
Regards...
Arup

Issue in product category replication from R/3 to SRM

Mehul G Shah: BACKGROUND:
We are in the process of replicating Material Group from R/3 to SRM
using transaction R3AR2 & R3AR4. Our Pre-Production server got
refreshed recently & this has caused all EBM data inclucing Logical
System & Destination being overwritten with EBP data.
We have maintained middleware paramaters, viz., CRMCONSUM, CRMRFCPAR,
CRMPAROLTP & also TBE11.
We have also maintained sites in CRM Middleware Monitoring Cockpit
using SMWP.
We have also tried after deleting entries in tables CRMPRLS (R/3) &
CRMMLSGUID (EBM) as suggested by SAP note 765018
We have followed steps mentioned in link /people/marcin.gajewski/blog/2007/02/05/how-to-replicate-material-master-from-r3-to-srm
(But we are not clear about site attributes which needs to maintain as per the CRM Middleware Monitoring Cockpit.)
ISSUE:
Material Group gets replicated to Product Category in SRM. However, the
Product Category gets replicated with Logical System which is not
maintained in EBM

Hi ,
Thanks 4 ur replay,i have maintained Site attributes,please give me detail of site attributes like which attributes should i maintain ?please give me descriptive answer.

Pricing procedure changes from R/3 to CRM

Hi gurus,
We want to change the pricing procedures in r/3 which involves changes to "From" and "to" calculation and as the same pricing procedures are being used in CRM, how do we synchronise the same,
Does system automatically replicate the changes ?
We have to manually make the changes in CRM for the same ?
Looking for valuable advise and suggestions gurus,
Thanks in advance,
Kind regards,
Gopio.

Hello Gopio
It is quite a while since I worked on a CRM project. These are basically middleware transactions which you use to transfer Customizing, Master and Transactional data from R/3 to CRM. Banking on my memory, here is the answer:
Menu Path: While in SAP Easy Access screen, choose Architecture and Technology/ Middleware ® Data Exchange ® Initial Load ® Start.
T code: R3AS.
Then you have to monitor the status of the transfer and check if the transfer is complete by using
Menu Path: Architecture and Technology/ Middleware/Monitoring , Data Exchange/ Monitor Objects or T code R3AM1.
Finally use tcode SLG1 ( options: object: COND_EXCHANGE, subobject: CUSTOMIZING), to display a log for the data transfer.
Hope this helps.

Approval of Leaves (workflow - portal) which are in SENT status from R/3

Hi HR and workflow experts,
I want to approve/reject leaves as an Administrator from R/3 for the records which are created from ESS portal side.
I find that the standard report RPTARQAPP - is only applicable for individual reportees and doesnt work as an administrative tool to approve/reject leaves.
This requirement arises during the year-end, when there are pending leaves (SENT- status) which needs to be approved by the administrator from backend.
Need this urgently.Please help.
Thanks & Regards,
Rohan
Edited by: Rohan Kesireddy on Sep 19, 2010 9:33 PM

Hi Lakshmi,
Please follow as below:
SMWP-Middleware Monitoring Cockpit- This transaction gathers a wide set of information about the status of the Middleware & Downloads in both the CRM system, the R/3. All statuses should normally be green but there may be some circumstances which stop this occurring. Expand the section Generation Information which refers to the generation of BDoc Types. Where ever you see error you can right click and Select Analysis Tool then right click and check the error.The log shows the error.
SMQ2- Select a Queue and select Display. Queues connected to R/3 start with a queue name of R3A/D.
Double click on the Status field i.e SYSFAIL. Reason will be shown.In your case it is u201CError in Mapping (Details: transaction SMW01)u201D. Then Continue and select a queue and select Display.You can see the Individual BDocs are beoing displayed.
SMW01- give Bdoc Type as " Product_mat". If it is not displaying then I request you to check if all the objects are generated properly.This may also happen if the objects are not properly generated.Use tx-Genstatus. That will give you a list of error objects to be generated.
Regards...
Arup

MAM 2.5 Functionality Syncronize questions

Hi all, I have a couple questions about synchronizing using MAM2.5.
1. When I synchronize from the PDA, is there anyway to confirm on the PDA WHAT data has been sent to the middleware? Is there a log that I can analyze of what actual data was being sent?
My current workaround is to check the Middleware monitor tool, and then to check the R/3 system that the data got there. That seems to be a lot of places just to check. I'd only like to check in one place, preferably on the PDA.
2. When sending/receiving data I synchronize multiple times. At least 2 - 5 times. Is there way to send and receive all data with only one synchronization? Having to always enter your password multiple times and sync multiple times is very repetitive.
Please advise. Thank you.

Hi Alex
1. By default all your changes are sent to the middleware in the next sync. The only way that this would not be possible is if you have a OutDeltaObserver and disabling the Delta from being sent. Otherwise it would definitely go to the middleware on next sync.
2. If you are using asynchoronous syncbos, you can convert them to synchronous syncbos, this can be changed in the middleware in MEREP_SBUILDER. Every syncbo has a checkbox which indicates if it is asynchronous, you could uncheck that.
Alternatively, every download request can be changed to synchronous by setting the following for each syncbo descriptor
SmartSyncRuntime.getSyncBoDeltaRequestFacade().getSyncBoDeltaRequest(syncBoDesc).setProcessing(SyncBoDeltaRequestType.DIRECT_REQUEST);
For your OutDeltas you can write an OutDeltaObserver which changes the send type.
A third option would be to enable repetitive sync
This would call sync repetitively without the user intervention
The parameters are
MobileEngine.Sync.RepetitiveSyncEnabled = true
MobileEngine.Sync.TimeBetweenRepetitiveSyncs = <time between syncs in milliseconds>
MobileEngine.Sync.MaximumNumberOfRepetitiveSyncs = <number of syncs to be called>
Oh by the way you can disable you sync password with the following parameter
MobileEngine.Security.Synchronization.PasswordHandlingOption = local.
This would never ask you for your password during sync but your login password must be the same as your sync password.
Hope you found this useful, incase something is not clear I would be happy to explain it in more detail.
Happy Syncing (Not so much now;) )!
Karthik
Message was edited by: Karthik V Setty

CRM Groupware

Does anyone knoe the limitation of groupware integration. If so plese let me know.
Thakns

Hope this is wat you are looking for
1)     The Groupware Integration Mappings shipped by SAP cannot be extended or changed by Customers. The mapping framework does not support this extension.
2)     E-Mail integration is not supported by this solution.
3)     A central Monitoring tool is not available to track the flow of messages between CRM and Groupware and vice versa.
The Middleware monitoring tool (transaction smw01) Display BDoc Messages shows the flow of messages to the Groupware Adapter Site Type on the CRM Server. A green light in this tool for a particular BDoc message only indicates that Mapbox has processed the message. But it does not indicate that the object has reached Groupware.
4)     Multi Language support is not available in Groupware Integration.    Only one language is supported by Groupware Integration. Hence if the default language is set to English in the property field DLANG of the IMG customizing view Maintain General Groupware Settings, all the text and description will be shown in English on Groupware.
E.g. in Groupware Contacts the Country name, Title, Prefix                will have English long text.
For a Groupware Appointment or Task the description field will be taken from Text type like Note or Preparation or Report with   language= English from a CRM Business Activity. Similarly in the reverse direction when an appointment is updated in Groupware it will update only the text related to language=English.
5)     The Groupware User must enter a value in the category field of the Groupware Appointment, Task and Contacts. The category field must contain a string starting with CRM_ACT for Appointment/Tasks and CRM_BP for Contacts. Only groupware objects with this category value will be synchronized in the direction Groupware to CRM.
Example: For a meeting request created in Groupware the user can enter the category as CRM_ACT 001 (CRM Activity Management Sales Call) or just CRM_ACT.
6)     Only One-directional synchronization of contacts to private contact folder from CRM to Groupware is supported. Synchronization of Contacts from Private Contact Folder in Groupware to CRM is not supported. Any updates to contacts in the private contact folder will not reach CRM.
7)     In Public folder Contact synchronization only the Business Partner Master Data is exchanged. No relationship data to an account or organization or Group is mapped.
For example it there is a Business Partner having the role Contact Person, it is not possible to map any of the relationship details of the account to which he/she is associated. Hence it is not possible to map the address and phone number of the organization.
8)     In CRM only the Business object of type BUS2000125 (Task) and BUS2000126 (Business Activity) are synchronized with Groupware as Groupware Task and Appointment/Meeting Request. Periodic Rules and Recurring Appointments are not supported.
9)     The SMTP address of each Business Partner who takes part in Groupware Integration of CRM Activity Management should be unique. No two partners can share the same email address. The integration will fail if the e-mail address is shared by more than one partner. Also it is mandatory that this e-mail address is maintained in the Master data and not in any relationship data.
10)      Business Partners will be exchanged as contacts in Groupware even if the E-mail address is not maintained for this partner. The E-mail address should be maintained for partners who wish to take part in Business Activity.
11)      For Activity Management synchronization to work with this Groupware solution, the E-Mail address of each Partner who would be part of the Business Activity should be maintained in the Address Dependent Communication section (Private communication address) of the Business Partner Master Data. It will not help if E-mail address is maintained in the relationship data.
12)      It is not recommended to use the synchronization of contacts from Public folder in Groupware to CRM. If the Customer wants to use this feature, a proper policy should be established, such that only authorized users can change the contact data, which will then update the Master data in CRM.
Sometime this synchronization will also lead to duplication of Master Data in CRM. This normally happens when the mapping cannot resolve the correct Business Partner to update in CRM.
To turn off this synchronization in the direction Groupware to CRM, the following steps needs to be carried out:
a) Shutdown the Groupware Connector.
b) In the Groupware connector installation folder you will find a tool called as AdminTool.exe. Run this tool and select Proxies->General.
c) Double click on the Proxy Instance or press Edit Proxy Configuration.
d) Another window would come up, select the node Replication.
    There you can tick the section
    Don't Replicate Changes in Public Contacts.
    Don't Replicate Changes in Private Contacts.
e) Restart Connector.
13)      For Business Partners who require synchronization of Business Activities in both directions i.e. CRM to Groupware and vice versa, such partners should be maintained with the role Employee (BUP003) with a valid E-mail address in the Business Partner Master data.
For partners maintained with this role, the Groupware connector will poll for changes in the mailbox at regular intervals.
14)      Scenario: Private Folder Contact Synchronization-
Contact Person in CRM having the relationship Is Contact Person For shows the address of the organization in the contact data.
Limitation:
During Synchronization of Contact Person to Outlook private folder, multiple relationship data to an Organization displays the address data of only one Organization i.e. if a Contact Person is having the relationship Is Contact Person For to more than one organization, only the address of one of these organization is shown in outlook contact data. Also it is not possible to determine which organizations address is shown.
15)      When a Contact Person is exchanged from CRM to Groupware having the relationship Is Contact Person For to an Organization in CRM, the name of the Company is displayed in Outlook Contact data. Also there is an option to display the address of the organization in the contact persons communication fields.
If the name of the Organization is changed or address data or communication fields are changed at a later point in time in CRM the updated name or address of the Company is not reflected in groupware contact for this Contact person.
The user has to manually trigger an extract of contact persons data for each site type from Admin Console, only then this new change in organization data will be reflected in the contact details of the contact person.
16)      During the synchronization of Contacts from Public Folder of Groupware to CRM, the category entered should be one among the following
CRM_BP Natural Person
CRM_BP Organization
CRM_BP Group
CRM_BP
Directly providing the Role along with the category is not supported. It is not possible to create different roles in CRM for Contacts created in Groupware. However for contacts created in Public folder, it is possible to associate a default role under which this Business Partner will be created on CRM.
17)      For a Business Activity only one text type like Note or Preparation or Report etc., of the specified default language is synchronized with Groupware. This text type can be customized per transaction type.
E.g. for the Transaction type 0001 (Sales call) it is possible to customize the text type that needs to be exchanged as Note (A002). Only the Note entered in the language=English section will be exchanged with Groupware assuming that the DLANG property in the IMG customizing view Maintain General Groupware Settings is set to English.
18)      For a Business Activity created in CRM, the partner function with the role planner/organizer will be the organizer of the Meeting. All the other partner functions having the calendar maintenance flag will be marked as     attendees     in   the                        Appointment/Meeting Request.
If a partner in a Business Activity does not have a valid email address maintained, this partner will not be in the attendee list of the appointment. However if the organizer itself has an invalid email address, there will be appointment created in groupware.
19)      A Task created in CRM will be sent only to the Task Responsible in Groupware. No other partner function will receive this information about the task.
Similarly for a task created in Groupware, only the Task responsible will be in the partner list of the Business Activity with an associated partner function. There is no information on the person who created the task on Groupware.
20)      If a Meeting request is created in Groupware and a Contact Person is invited as attendee by adding his/her email address. The email address is mapped to the Contact persons email address maintained in the   Business Partner Master data, not the organization email address maintained the relationship data. Hence it is suggested that the customer maintain the same email address in the relationship data and the contact persons email communication master data.
21)      If a Meeting request is created in Groupware with a Contact Person as invitee, his organization is NOT determined and added to the Business Activity.
E.g. it is NOT possible to determine the account of the contact person and add this account as the Activity Partner in the Business Activity.
22)      The maximum size of all the attachments put together in a Business Activity should not exceed 1 MB. The synchronization will fail if the attachment size exceeds this limit.
23)      Initial download of Business Activities or Appointments/Tasks is not supported either from CRM or from Groupware.
24)      If the Customizing setting NO_BSP_URL in the in the IMG customizing view Maintain General Groupware Settings has the property value as X
then the appointment or task will not have the BSP URL link. Also if there is an associated opportunity the Summary of Opportunity is not shown.
If this customizing field NO_BSP_URL does not contain the property value as X then the attachment containing the summary of opportunity (if this activity is a follow up from an opportunity) and the attachment containing the link to BSP page is displayed in the appointment or task created in Groupware.
25)     The link to the BSP or Portal page contained in a Groupware Tasks does not work as expected.
26)     The link to BSP URL and Enterprise Portal URL which is displayed as a part of the Appointment or Task in Groupware cannot be customized. Only the Web Server/Portal Server and Port is customizable.
27)      For an attendee to receive Business Activity in Groupware as appointment, the Calendar Maintenance flag should be ticked/checked for this partner in the Business activity application on CRM.
28)      Work Force Management application supports simple recurring appointment with no support for exceptions.
29)      In Work Force Management application integration with groupware, deletion of All Day Recurring Appointments is not supported from Groupware to WFM.
30)      In Work Force Management application integration, Yearly Recurring Appointments from Groupware to WFM is not supported.
31)      In Work Force Management application integration, All Day recurring Appointments whose Appointment Start Date and End Date cross over Midnight is not supported. This is not supported in both directions.

Middleware monitoring

Similar Messages

Maybe you are looking for