标准的RSMO事务代码能实现什么样的功能

简介:

In RSMO, We have to check the successful, running and failed objects.

When you select Successful one it shows how many records are there in the source system and how many records will be added to BW.

RSMO Transaction is same like Monitor Screen when you schedule any Info Package and monitor. 

Only difference is in the Left Panel you can see all the Jobs Completed, Active & Erroneous for the entire Day 

When you select running (Yellow color), that means it is still running. If the object is running for a long time then we have to check, why it is running from long time. Select and check for pervious data how much time that it takes. And analysis for the time taken.

When you select the failed (Red color), that means that the object is failed. First select that failed one, on the right side one more screen will come. 

Header, status and details. In header is shows the data target, type of update, infopackage, infosource, selections, request etc. In Status tab, it shows some error message, 

Click on error message in down, it shows some message regarding that particular failure. In Details tab we have to check the extraction is over or not and at what step the data is loaded etc.
 

RSMO is a transaction where you can find all the loads currently running in the system.

There are two ways for opening load monitor in BI7.

1) tcode RSMO

2) RSA1-> Administration tab -> Monitors -> Load Monitor

Once you enter the transaction, you can see the various loads information.

Select the tree button to set what all information you require for a load and in which order.

Select the filter button to set the range of date for which you want to see the loads 
eg: today 
yesterday and today 
in the past week etc....

You can find loads of three status types

1) successful(green)

2) currently running(yellow)

3) failed(red)

When you click any load on the right side a information for the particular load will appear.

On the header tab you can see the information related to the load like request number, data source system, infosource, data targets if any, type of load etc...

In the status tab you get to know the technical and total status of the load and if the load has failed you can see the error message button and application log button as well

In the details tab you will get the following information.

- R for Requests says whether the request is working in general ok or not 
- E for Extraction says whether data received and scheduled. How many records are sent for extraction and how many are received for extraction. 
- T for Transfer IDocs indicates how many data packages are there for extraction and how many records arrived in each data packages for extraction. 
- P for processing indicates transfer rules, update rules and update and processing have any errors or not. 
- P for Process Chain will indicate whether it worked ok or not if there is a process chain and load is successful or not.

If you have any subsequent steps like ods activation in the PC for that load, you will get the status of that step also here.

专注于企业信息化,最近对股票数据分析较为感兴趣,可免费分享股票个股主力资金实时变化趋势分析工具,股票交流QQ群:457394862
分类:  SAP BI

本文转自沧海-重庆博客园博客,原文链接:http://www.cnblogs.com/omygod/archive/2011/12/16/2290184.html,如需转载请自行联系原作者
目录
相关文章
|
5天前
|
存储 监控
系统日志规范问题之业务执行日志的定义如何解决
系统日志规范问题之业务执行日志的定义如何解决
|
3月前
|
数据采集 分布式计算 监控
日志服务功能特性
日志服务功能特性
42 7
|
11月前
|
SQL 监控 Java
【开发规范系列】(三)代码提交规范
【开发规范系列】(三)代码提交规范
|
存储 关系型数据库 分布式数据库
PostgreSQL 14中两阶段提交的逻辑解码
PostgreSQL 14中两阶段提交的逻辑解码
157 0
|
消息中间件 数据库 RocketMQ
【JavaP6大纲】分布式事务篇:可靠消息最终一致性方案
【JavaP6大纲】分布式事务篇:可靠消息最终一致性方案
114 0
|
XML 前端开发 Dubbo
优雅的参数校验与全局异常-代码规范的天生落地
代码规范是项目质量的基石,能够帮助开发者和管理者更好的管理/维护项目、专注于推动快速成长的业务、留出更多时间攻坚重难点系统设计。而全局异常和参数校验则是快速开发的利器,本文将结合阿里巴巴开发手册阐述如何定义众所周知的全局异常机制。
738 0
优雅的参数校验与全局异常-代码规范的天生落地
前端团队规范探索:自动格式化、代码校验、提交规范
以往在使用eslint对代码进行规范的时候,经常遇到校验与自动化格式化规则不同的问题,比如eslint中规定末尾必须使用分号,那么你开发工具中代码美化插件也需要配置相应的格式化规则,这是比较麻烦的,所以standard规范太霸道了,大家开发基本都不会去用。
|
运维 JavaScript 开发工具
通过工具来规范代码提交与发布日志
使用https://github.com/conventional-changelog/standard-version和vscode插件”Conventional Commits”工具规范开发人员提交git日志
401 0
通过工具来规范代码提交与发布日志
|
消息中间件 容灾 关系型数据库
核心特性—全局日志变更
MySQL binlog是MySQL记录变更数据的“二进制日志”,它可以看做是一个消息队列,队列中按顺序保存了MySQL中详细的增量变更信息,通过消费队列中的变更条目,下游系统或工具实现了与MySQL的实时数据同步,这样的机制也称为CDC(Change Data Capture,增量数据捕捉)。
115 0
核心特性—全局日志变更