检查BW与SAP的连接

1.       表T000  

BW端

SAP端  

 

2.       表RSBASIDOC

BW端

SAP端

两系统中两条记录需一致。

如果表中没有则需要恢复，步骤如下

 RSA1 --> 建模 -->源系统 --> SAP系统 -->恢复

 

 

3. 检查SAP源系统的RFC目标 【这步貌似没有验证成功，因为没有必要从BW抽数到SAP】
On the SAP sourcesystem the RFC-Destination has the same name as the logicalsystem name of the BW system.

·        SAP sourcesystem: transactionSM59 -> Double click on the destination

·        Compare the hostname to thesever name of the BW system (transaction SM51)

Target Host 跟BW端对不上。 SystemNumber对上。

ECC 端：检查权限

 

Check if the update user in the BW system has the authorization profile‘S_BI-WHM_RFC’ (SAP Note 150315)

SAP端口SM59

BW端 SU01 S_BI-WHM_RFC

 

4. 检查BW系统的RFC目标: 
On the BW system you can get the name of the SAP sourcesystem RFC-Destinationby tableRSLOGSYSDEST. If there isn‘t an entry forthe source system, the name is the logical system name of the SAP sourcesystem

BW端   SM59

SAP端   SM51

BW 端 检查权限

 
Check if the user in the source system has the authorization profile‘S_BI-WX_RFC’ (SAP Note 150315)

BW端口

SAP端SU01检查 S_BI-WX_RFC

 

5. 检查伙伴定义: 
WE20

BWsystem:

·        寻找逻辑系统

·        

·        双击RSRQST –双击接收方端口

·        

·        保证与BW中SM59中一致。

·        进站参数 
RSINFO
RSSEND

 

ECC端口:WE20

·        出站参数

·        双击RSINFO-双击接收方端口

与SM59中一致

·        双击RSSEND –双击接收方端口-> RFC目标-> 与SM59一致

 

·        进站参数
RSRQST

1.    授权
BW 端的用户应当看到以下参数文件：S_BI-WHM_RFCand S_RS_ALL.

ECC端 SU01 ALEREMOTE,应当有以下参数文件S_BI-WX_RFC, S_IDOC_ALLand B_ALE_ALL.

Human administrator in both systems with S_RS_ALL

SAP Note 150315

S_BI-WHM_RFC的授权

 

1. The profile S_BI-WHM_RFC must contain(at least) the following authorizations:

Profile
  |
  ---   S_BI-WHM_RFC <PRO> Business InformationWarehouse, RFC user
      |
      |--  B_ALE_ALL    <PRO>All authorizations for ALE/EDI
      |--   S_BI-WHM_SPC <PRO>Business Information Warehouse, special
      |--   S_BTCH_ADM  <PRO> BC: Batch - Processing authorization
      |--  S_BW_RFC    <PRO> BW: Authorization Profile: Other
      |--   S_IDOC_ALL  <PRO> All authorizations for IDoc functions
      |--   <sufficientauthorizations to perform BW admin tasks>

2. The referredfunctionality is 2. 1. V), thus the authorizations to executeIMG-functionality, to execute Transaction SBIW and to maintain theapplications, which shall be customized, must be temporarily given toALEREMOTE, if you want to execute the functionality from BW-side. Thepermissions for executing the customizing is not included in the profileS_BI-WX_RFC, since this is a critcal functionality.

              Howeverthere is the possibility to execute the customizing in the OLTP by a humanadministrator by hand, using Transaction SBIW.

3. For sendingthe Idocs and reading RFC-destinations the profile S_BI-WX_RFC is incomplete.

Please check, if the following authorizations are included:

Profile
  |
  ---   S_BI-WX_RFC  <PRO> BusinessInformation Warehouse, RFC User
      |
      |--  B_ALE_ALL    <PRO>All authorizations for ALE/EDI
      |--   S_APPL_LOG_A <PRO>Application log: All
      |--   S_BTCH_ADM  <PRO> BC: Batch - Processing authorization
      |--  S_BW_RFC    <PRO> BW: Authorization Profile: Other
      |--   S_IDOC_ALL  <PRO> All authorizations for IDoc functions
      |--   S_RO_OSOAC  <PRO> SAPI DataSource completely

- BW AddOn BW-BCT 1.2B:
These authorizations have been delivered with BW AddOn Patch 2 (see 158489 forthe AddOn Patch information), except release 45B. For 45B, the authorizationsare delivered with BW AddOn Patch 1.

- PI2000.1:
For 4.6B and 4.6C due to delivery errors, this profile also is incorrect.Please transport it from the BW into the Oltp (it is the same in any system andrelease).

- PI2000.2:
For 4.6C due to delivery errors, this profile also is incorrect.
Please transport it from the BW into the OLTP (it is the same in any system andrelease).

- PI2001.2:
For 4.6C due to delivery errors, this profile also is incorrect.
Please transport it from the BW into the OLTP (it is the same in any system andrelease).

Alternatively, import the sapserv* transport BRSK002208 under the directory\\general\R3server\abap\note.0150315 into your OLTP-System.

For help on the sapserv* transport refer to Note 13719.

5) If you have PI-Basis 2005.1 in your source system, you need to attach roleSAP_RO_BCTRA to your user in the source system. Otherwise, the functionalitymentioned in the message is not available. The system continues to function asbefore, you may ignore the warning.