【转】BW-- BW项目的对象传输(稍作修改)

最新推荐文章于 2024-12-17 21:47:02 发布

转载最新推荐文章于 2024-12-17 21:47:02 发布 · 912 阅读

文章标签：

#system #button #import #bi #object #tree

BW 专栏收录该内容

41 篇文章

订阅专栏

本文详细介绍了BW项目中对象从开发系统到生产系统的传输过程，包括R/3系统中的数据源传输步骤及BW系统中BI对象的两种传输方法。此外还提供了如何在不同系统间维护映射表以及在DEV系统中收集和传输对象的具体指导。

【转】BW-- BW项目的对象传输(稍作修改)

一、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,then to PRO;

2)transport BW objects to QA, then to PRO;

三、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.

备注：平常RSA5激活数据源后挂在相应请求号上，再按照普通传输即可

四、BW传输步骤如下

IN QA/PRO System

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.

（一）method one：

a) RSA1

b) Click on the “Transport Connection” Tab

c) Choose "Conversion（转换）" Button with quick info Conversion of Log. System Name.

（一）method two：

a) RSA1

b）On the Data Warehousing Workbench: Modeling screen, choose “Tools”

c）then click “Conversion of the Logical System Names”（转换逻辑系统名称）.

The View: Conversion of Source System Names after the Transport screen appears.

其中的OriginalSourceSystem“原源系统”对应的开发机中数据的来源，而Target SourceSystem “目标源系统” 则对应的是测试机数据来源，如果链接多个系统，则需要做多个映射配置；

添加了相应的系统映射后，则可以在BW中做模型传输了。如果不清楚逻辑系统名，则可以在相应系统中采用SCC4进行查看，在显示“客户端”明细视图中可以看到逻辑系统名。

Alert Following：

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

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 Chain：
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.