BW-- BW项目的对象传输
2008-10-08 22:38
288 查看
一、BW项目的对象传输分两部分:
1)Transport all relation BW Object in R/3 system;
2)Transport BW Object in BI system;
二、传输步骤
1)first you have to transport R/3 objects to QA;
2)THen transport BW objects to QA;
三、R/3传输步骤
1: Using transaction RSA6, all DataSources in your Source System are displayed
2: Select the DataSource that you wish to save (transport) and click on the transport icon.
3: Repeat for all DataSources
4: SE10 to release the transport
5: go to R/3 QA system and use STMS to import request.
四、BW传输步骤如下
IN QA System
1: To transport source-system-specific BI objects, you have to maintain the mapping table (RSLOGSYSMAP) in the BI target system. These BI objects are converted during the transport using mapping tables.
a) RSA1
b) Click on the “Transport Connection” Tab
c) Choose "Conversion" Button with quick info Conversion of Log. System Name. On the Data Warehousing Workbench: Modeling screen, choose Tools ® Conversion of the Logical System Names. The View: Conversion of Source System Names after the Transport screen appears.
2: The DataSource metadata from the original source system has to be transported into the specified target source system and is replicated in the postprocessing of the assigned BI objects. Make sure that the DataSource exists in the target source systems before you import DataSource-dependent BI objects.
IN DEV System
3: You first need to decide
– Which objects you want to collect
– How you want to collect them
4: RSA1
5: Click on the “Transport Connection” Tab
6: Click on the “Source System” button to Select the Source System(s) that you wish to save dependent objects for
7: Select the BW objects
8: Select the Grouping option(necessary/before/after/before and after)
9: Click on the "Excute" button to gather dependent objects.
10: Click on the "Transport" Button to add all object to request
11: SE09 - display request - req is modifiable in tree - select request - release task - release parent as well - get screen with status ;
IN QA System
12: STMS - click bus - choose bp2 - opens all transports - shows my req - click import icon ONLY my request - import done - ready message.
13: Check in RSA1 in production
Memo:
Process Main
This is standard 'feature' of SAP. Why, I can only guess :) Either the activation and execution is linked and you do not want to run the process chain the moment it transports, or, you want a manual intervention one time to make sure you are not getting it in 'active' status without proper checks.It will happen on PRD as well.Please note that you would have executed the process chain when you ran the FM. You may inadvertantly execute the PC when you mean to 'only activate' it, as that is what the FM does (I think). Something to note of, if you are doing it on PRD.
Handle Method:
1)Process chains remain 'inactive' after transport. You can try activating them in RSPC,
2)Execute FM (in SE37, single test) 'RSPC_CHAIN_ACTIVATE_REMOTE' and specify the process-chain there (this will activate and execute the chain). FM did not ask request.
相关链接:
1)Transport all relation BW Object in R/3 system;
2)Transport BW Object in BI system;
二、传输步骤
1)first you have to transport R/3 objects to QA;
2)THen transport BW objects to QA;
三、R/3传输步骤
1: Using transaction RSA6, all DataSources in your Source System are displayed
2: Select the DataSource that you wish to save (transport) and click on the transport icon.
3: Repeat for all DataSources
4: SE10 to release the transport
5: go to R/3 QA system and use STMS to import request.
四、BW传输步骤如下
IN QA System
1: To transport source-system-specific BI objects, you have to maintain the mapping table (RSLOGSYSMAP) in the BI target system. These BI objects are converted during the transport using mapping tables.
a) RSA1
b) Click on the “Transport Connection” Tab
c) Choose "Conversion" Button with quick info Conversion of Log. System Name. On the Data Warehousing Workbench: Modeling screen, choose Tools ® Conversion of the Logical System Names. The View: Conversion of Source System Names after the Transport screen appears.
2: The DataSource metadata from the original source system has to be transported into the specified target source system and is replicated in the postprocessing of the assigned BI objects. Make sure that the DataSource exists in the target source systems before you import DataSource-dependent BI objects.
IN DEV System
3: You first need to decide
– Which objects you want to collect
– How you want to collect them
4: RSA1
5: Click on the “Transport Connection” Tab
6: Click on the “Source System” button to Select the Source System(s) that you wish to save dependent objects for
7: Select the BW objects
8: Select the Grouping option(necessary/before/after/before and after)
9: Click on the "Excute" button to gather dependent objects.
10: Click on the "Transport" Button to add all object to request
11: SE09 - display request - req is modifiable in tree - select request - release task - release parent as well - get screen with status ;
IN QA System
12: STMS - click bus - choose bp2 - opens all transports - shows my req - click import icon ONLY my request - import done - ready message.
13: Check in RSA1 in production
Memo:
Process Main
This is standard 'feature' of SAP. Why, I can only guess :) Either the activation and execution is linked and you do not want to run the process chain the moment it transports, or, you want a manual intervention one time to make sure you are not getting it in 'active' status without proper checks.It will happen on PRD as well.Please note that you would have executed the process chain when you ran the FM. You may inadvertantly execute the PC when you mean to 'only activate' it, as that is what the FM does (I think). Something to note of, if you are doing it on PRD.
Handle Method:
1)Process chains remain 'inactive' after transport. You can try activating them in RSPC,
2)Execute FM (in SE37, single test) 'RSPC_CHAIN_ACTIVATE_REMOTE' and specify the process-chain there (this will activate and execute the chain). FM did not ask request.
相关链接:
相关文章推荐
- BW-- BW项目的对象传输
- BW-- BW项目的对象传输
- BW-- BW项目的对象传输
- ActiveMQ服务器之间传输对象,项目A发送对象到项目B接收发送对象《一》
- ActiveMQ服务器之间传输对象,项目A发送对象到项目B接收发送对象《二》
- Java传输对象模式
- CoreData 数据传输对象DTO(data transfer object)
- springboot整合gprc 传输对象
- 第五周项目二——对象作为数据成员
- Web项目在启动时启动一个服务或者实例化一个对象
- DTO--数据传输对象
- 第五周项目二之对象作为数据成员
- 第五周 项目二 对象作为数据成员
- java中传输对象时候的问题
- 第六周项目零:阅读程序(5):结构函数和析构函数,对象的赋值
- BW--BW各种对象对应的图标列表
- .NET平台开源项目速览(2)Compare .NET Objects对象比较组件
- WCF 项目应用连载[7] - 绑定、服务、行为 大数据传输与限流 - 上
- Mina二进制传输对象IoBuffer的使用
- Java Socket实战之五 使用加密协议传输对象