cancel
Showing results for 
Search instead for 
Did you mean: 

tRFC error when we load BW from ECC

Former Member
0 Kudos

Hi experts,

I'm looking for your advise and help with an issue that we have when we load from ECC to BW. From time to time, the load from ECC fails because of tRFC error in the source system. In reality the load just stops (RSDS_ACCESS013 Error in codepage mapping for source system.) and when we reprocess the tRFC via SM58 (F6) in ECC the load restart in BW. Our Basis consultants are not able to fix this issue and we have to monitor the tRFC in ECC an manually reprocess them one by one when they are in error.

Any help with this issue would be very appreciated.

This is our systems specs

BW

SAP_ABA 730 0004 SAPKA73004 Cross-Application Component

SAP_BASIS 730 0004 SAPKB73004 SAP Basis Component

PI_BASIS 730 0004 SAPK-73004INPIBASIS Basis Plug-In

ST-PI 2008_1_710 0004 SAPKITLRE4 SAP Solution Tools Plug-In

SAP_BW 730 0004 SAPKW73004 SAP Business Warehouse

BI_CONT 735 0004 SAPK-73504INBICONT Business Intelligence Content

BI_CONT_XT 735 0004 SAPK-73504INBICONTXT BI_CONT_XT 735: Add-On Installation

ST-A/PI 01N_710BCO 0000 - Servicetools for other App./Netweaver200

ECC

SAP_ABA 700 0017 SAPKA70017 Cross-Application Component

SAP_BASIS 700 0017 SAPKB70017 SAP Basis Component

PI_BASIS 2006_1_700 0008 SAPKIPYM08 Basis Plug-In (PI_BASIS) 2006_1_700

ST-PI 2008_1_700 0002 SAPKITLRD2 SAP Solution Tools Plug-In

SAP_BW 700 0019 SAPKW70019 SAP NetWeaver BI 7.0

SAP_AP 700 0014 SAPKNA7014 SAP Application Platform

SAP_APPL 603 0003 SAPKH60303 Logistics and Accounting

SAP_HR 600 0030 SAPKE60030 Human Resources

EA-IPPE 400 0014 SAPKGPID14 SAP iPPE

EA-APPL 603 0003 SAPK-60303INEAAPPL SAP Enterprise Extension PLM, SCM, Finan

EA-DFPS 600 0011 SAPKGPDD11 SAP Enterprise Extension Defense Forces & Public Security

EA-FINSERV 600 0014 SAPKGPFD14 SAP Enterprise Extension Financial Services

EA-GLTRADE 600 0011 SAPKGPGD11 SAP Enterprise Extension Global Trade

EA-HR 600 0022 SAPKGPHD22 SAP Enterprise Extension HR

EA-PS 603 0003 SAPK-60303INEAPS SAP Enterprise Extension Public Services

EA-RETAIL 600 0011 SAPKGPRD11 SAP Enterprise Extension Retail

FINBASIS 600 0014 SAPK-60014INFINBASIS Fin. Basis

ECC-DIMP 600 0011 SAPK-60011INECCDIMP DIMP

ERECRUIT 600 0011 SAPK-60011INERECRUIT E-Recruiting

FI-CA 600 0011 SAPK-60011INFICA FI-CA

FI-CAX 600 0011 SAPK-60011INFICAX FI-CA Extended

INSURANCE 600 0011 SAPK-60011ININSURANC SAP Insurance

IS-CWM 600 0011 SAPK-60011INISCWM Industry Solution Catch Weight Management

IS-H 600 0012 SAPK-60012INISH SAP Healthcare

IS-M 600 0011 SAPK-60011INISM SAP MEDIA

IS-OIL 600 0011 SAPK-60011INISOIL IS-OIL

IS-PS-CA 600 0011 SAPK-60011INISPSCA IS-PUBLIC SECTOR CONTRACT ACCOUNTING

IS-UT 600 0011 SAPK-60011INISUT SAP Utilities/Telecommunication

LSOFE 600 0011 SAPK-60011INLSOFE SAP Learning Solution Front-End

SEM-BW 600 0014 SAPKGS6014 SEM-BW: Strategic Enterprise Management

ST-A/PI 01N_700ECC 0000 - Application Servicetools for ECC 600

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

For error message,

"Error in codepage mapping for source system"

It seems to be due that some characters contained in the loading packages where not able to be interpreted during the RFC transmition. Therefore the content of the packages could not be transfer to BW.

The error can be due to two reasons.

1. The data you are loading contain corrupted characters. Therefore please review the data in R/3 contained in those error packages. If the data is correct then go to step 2.

2. If both BW and R/3 source system are unicode setting, but the Unicode option have not been selected in the RFC

maintenance screen(TCode SM59), please set it manually.

If one of the BW and R/3 source system is NON-Unicode and another is unicode, please follow the below notes:

814707 Troubleshooting for RFC connections Unicode/non-Unicode

663089 RFC bit options in SM59

647495 RFC for Unicode ./. non-Unicode Connections

547444 RFC Enhancement for Unicode ./. non-Unicode Connect

Review below note too,

1280898 IDoc hangs when it is to be sent immediately with qRFC

Regards,

Mani