What is bdoc

Word in Term. Term » Abbr. Filter by: Select category from list Couldn't find the full form or full meaning of BDOC? Notify me of new comments via email.

Cancel Report. Create a new account. Log In. Know what is BDOC? Got another good explanation for BDOC? Don't keep it to yourself! Add it HERE! Still can't find the acronym definition you were looking for? Use our Power Search technology to look for more unique definitions from across the web! Search the web. Citation Use the citation options below to add these abbreviations to your bibliography. Powered by CITE. Monitors the age in minutes of the oldest BDoc message in error state based on the configured selection criteria.

Counts the number of BDoc messages with errors based on the configured selection criteria. Counts the number of BDoc messages in an intermediate state based on the configured selection criteria. Monitors the age in minutes of the oldest BDoc message in an intermediate state based on the configured selection criteria. In classic BPMon you had the possibility to use key figures that had a combined rating for number of messages and age of entries for critical and intermediate state.

To model this behavior in ICMon these key figures are presented by two metrics that are correlated on alert level. From a functional point of view these metrics behave in the same way as the single metrics Number of BDoc messages in error state and Age of oldest BDoc message in error state. However, they share a common event, which means an alert is only raised if both metrics exceed their threshold values. If you do not configure one of the metrics the system behaves as if only the single metric has been configured.

Use these metrics if you are not just interested in the amount of erroneous messages or the age of the oldest erroneous message, but in the combination of those values. Consequently, you can use these metrics to get alerted about the age of the oldest erroneous message only if a certain number of erroneous messages exist, or get alerted about the number of erroneous messages only if the oldest of these messages has reached a certain age.

All available status codes are either grouped into one of these severity groups, or are ignored for monitoring if they indicate a final state already. The actual list of status codes within one of these groups does also depend on the release of the CRM system. Earlier releases have fewer different states. The data collector automatically assigns the available status codes to the two severity groups. This template provides metrics to analyze the BDoc message processing on the managed system.

This includes not only critical message states, but also the throughput of BDoc messages within a certain timeframe. The data can be used for monitoring and alerting, too. However, it is mainly intended to feed the Business Process Operations reporting tools. This metric counts the number of BDoc messages based on the configured selection criteria. It is intended to be used for measuring BDoc messages in a critical status.

It is intended to be used for measuring BDoc messages in an uncritical status. This template provides metrics for checking for errors in the underlying CRM Middleware infrastructure, with a special focus on the data exchange between SAP CRM system and mobile clients.

Five commonly used transactions related to the area of mobile clients are in scope of the monitor:. This metric checks if there are any mobile sites for which synchronization has been overdue for a specified time. This metric checks if there are any queues in status "HOLD". This metric counts the number of entries in the selected queues. As a result you get an alert for every queue that contains entries telling you how many entries are in the selected queues. This metric counts the number of nodes in the MW Cockpit which are in a warning or error status.

As a result you get red alerts for the nodes that are in an error status and yellow alerts for nodes that are in a warning status. This metric calculates the number of BDoc messages which have been processed yesterday.

This metric calculates the average processing time of all BDoc messages which have been processed yesterday. It is calculated by the sum of all processing times divided by the sum of BDocs processed. This metric checks the number of mobile sites with import failures.

The parameter fields also have an input help which helps you to select the correct values. Navigate to the Define Scope step. You can create a new scenario or use an existing one. Make sure the sender and the receiver system are part of the Interface and Connection Monitoring scenario.

If you want to use the metrics including a combination with the age of the BDocs you have to set values for the Minimum Age errors and Minimum Age intermediate. If the parameter is empty, all found messages are counted immediately. Usually it is not necessary to include all the available metrics. For a status monitoring, you might not be interested in the absolute number of messages in an erroneous state, as you have to react anyway, no matter whether it is just one failed message or several of them.

A monitoring of the intermediate states does not include the erroneous states as well, so you are advised to configure at least one metric from both status severity groups.

You can maintain attributes as described in the Interface and Connection Monitoring Setup on the Attributes tab. Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click Next in the main guided procedure to move to the Activation step. Their size depends on the amount of processed BDocs messages within the residence time before reorganization takes place, and the amount of all messages in a non-final state which prevents reorganization.

In case of a huge amount of BDoc messages in the system, use this monitoring template with care, as it causes an additional workload on the monitored CRM server. Please avoid running the data collection with a high monitoring frequency and avoid complex configurations of the selection criteria, especially those with patterns, ranges and exclusions. If you are in doubt, try to simulate the filter criteria with transaction SMW01 or SMW02, to get an idea about the possible runtime of the data collection.

For the exchange of BDoc messages e. In many cases there is a relation between a BDoc message status and a corresponding qRFC queue entry. Therefore, it is highly recommended to set up a qRFC monitoring as well. Note that technically both metrics produce the same result if configured identically. However, the Number of BDoc messages in critical status es metric is supposed to be used for measuring BDocs in an error state only, whereas the Number of BDoc messages in uncritical status es metric can be used for throughput measurements too number of successful BDoc messages.

Consequently in the Interface Channel Monitoring application the metrics are categorized as Exceptions and Performance , respectively. BDoc Channel. The internal data flow consists of three main steps: Inbound processing - Incoming data of different formats, e. If not assigned to an mBDoc type, the sBDoc message is directly passed to outbound processing i.

The CRM Server is not interested in this information and therefore the incoming sBDocs are directly passed to the outbound adapter. Validation - The incoming data in form of mBDoc messages is validated by the application, e.

If the validation is successful, the mBDoc message is passed to outbound processing. If the incoming data is not valid, the mBDoc is updated with an error message and then sent back to the sender. Outbound processing - The receiving systems e. Then the mBDoc message is passed to the corresponding outbound adapter which converts the message into the data formats of the receivers.

Technical Prerequisites. Available Monitoring Content.