0HR_PA_EC_01 Extractor error converting from currency in source system

Hi all,
when I run the standard extractor 0HR_PA_EC_01 , I get the following error message in the source system (application log):
Error converting currency from USD to on 09/03/2008
Message no. HRECM00SERVICE006
Thus, the requst in the PSA in BI / BW is Red.
Any recommendations?
Points will be assigned.
Thanks

Rajan,
You can try this function module for converting currency from one format to another format...
CONVERT_TO_FOREIGN_CURRENCY...
other wise... you can try with this function module..
RSW_CURRENCY_TRANSLATION............ this one i'm not sure abt that will convert ur data into required format..

Similar Messages

Gdk-WARNING **: Error converting from UTF-8 to STRING

I just installed Arch64 few days ago. In my old setup I was used to work with 2 softwares: Eclipse CDT and WingIDE.
I tried to start these applications (they require java and python but they are binary releases) locally and I get this errors which I can't solve by myself googling... Reporting snapshots of my desktop too.
[j_zar@Surprise eclipse]$ ./eclipse
(eclipse:7864): Gdk-WARNING **: Error converting from UTF-8 to STRING: Impossibile aprire il convertitore da "UTF-8" a "ISO-8859-1"
(eclipse:7864): Gdk-WARNING **: Error converting from UTF-8 to STRING: La conversione del set di caratteri da "UTF-8" a "ISO-8859-1" non è supportata
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: Failed to load Pango module '/usr/lib/pango/1.6.0/modules/pango-basic-fc.so' for id 'BasicScriptEngineFc'
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: pango_shape called with bad font, expect ugly output
(eclipse:7864): Pango-WARNING **: pango_font_get_glyph_extents called with null font argument, expect ugly output
(eclipse:7864): Pango-WARNING **: pango_font_get_metrics called with null font argument, expect ugly output
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Pango-WARNING **: /usr/lib/pango/1.6.0/modules/pango-basic-fc.so: wrong ELF class: ELFCLASS64
(eclipse:7864): Gdk-WARNING **: Error converting from UTF-8 to STRING: La conversione del set di caratteri da "UTF-8" a "ISO-8859-1" non è supportata
(eclipse:7864): Gdk-WARNING **: Error converting from UTF-8 to STRING: La conversione del set di caratteri da "UTF-8" a "ISO-8859-1" non è supportata
(eclipse:7864): Gdk-WARNING **: Error converting from UTF-8 to STRING: La conversione del set di caratteri da "UTF-8" a "ISO-8859-1" non è supportata
(eclipse:7864): Gdk-WARNING **: Error converting from UTF-8 to STRING: La conversione del set di caratteri da "UTF-8" a "ISO-8859-1" non è supportata
(eclipse:7864): Gdk-WARNING **: Error converting from UTF-8 to STRING: La conversione del set di caratteri da "UTF-8" a "ISO-8859-1" non è supportata
(eclipse:7864): Pango-WARNING **: pango_cairo_font_get_scaled_font called with bad font, expect ugly output
[j_zar@Surprise wingide]$ ./wing
(wing.py:7922): Gdk-WARNING **: Error converting from UTF-8 to STRING: Could not open converter from 'UTF-8' to 'ISO-8859-1'
(wing.py:7922): Gdk-WARNING **: Error converting from UTF-8 to STRING: Conversion from character set 'UTF-8' to 'ISO-8859-1' is not supported
Anybody can help in this???
Last edited by J_Zar (2007-10-30 11:48:28)

There has been talk about adding these config files, that fixes this kinda problems, to a separate pkg with a helper script you run 32bit programs with.
for quick fix
Link
Grab the 3 pango files, throw them somewhere, edit pangorc to corresponding paths for the 2 other files.
Start program with
export PANGO_RC_FILE="/path/to/pangorc"
program
for the string error, if its iconv
export GCONV_PATH=/opt/lib32/usr/lib/gconv
to previous command
Note, you cant start 64bit programs that use pango/iconv from the terminal you exported the variable.

Error converting from service name

Hi,
While installing NW04 6.40 Java System > Distributed > Central Instance Host preparation, i found this error but the installation is still going well. I'm wondering whether it is an issue for my install.
WARNING[E] 2006-11-02 13:07:35 [syxxcnamrs.cpp:128]
PSyServicesEntry CSyIPNameResolverImpl::getServiceByName(const iastring& serviceName, const iastring& protocol) const
Error converting from service name=sapmsRDX/protocol=tcp to port number. SAPRETURN=12
Thanks,
Torpedo

There is an entry missing:
add in /etc/services
sapms<SID> 36<systemnumber>/tcp
Markus

Error in Previewing data from a UD Source System

Hi,
I have created a data source from a UD Source System; however, when I preview data, I am prompted by this message:
"Inbound processing of data package 000001 finished"
There is no error, but there is also no data preview that is displayed.
Can you help me with my problem?
I look forward to your reply experts!
Regards,
Ramon

Hi,
sampling is out of a directory placed on the CLIENT. On runtime the directory must be placed on the SERVER.
So you must have two locations: one for sampling (*local) and one for (*remote) and before deployment you must switch from _local to _remote.
The _remote location points to a directory on the SERVER, don't forget to grant read/write privileges to the oracle user on the file system.
Regards,
Detlef

Error Loading Hierarchy Error when updating Idocs in Source System

Hello Friends,
I am loading hierarchy data using Info pac into 0FUNDS_CTR . I have selected a hierarchy under hierarchy selections tab in the Info pac .
All Partner profiles in WE20 seems OK . But When I loaded data , throwing errrr message as below
Error when updating Idocs in Source System
Diagnosis
Errors have been reported in Source System during IDoc update:
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
When I checked in TC WE05 says that IDoc: 0000000000355113 Status: Error during syntax check of IDoc (outbound) with status 26 .
Please advice .
Many thanks

Hi Krishna4bi,
Actually we will monitor idoc status in BD87 in SAP BI As well ECC , while extracting the data from source sytem if any idoc struck we will manually process in BD87 , But you are telling that while loading the datasource the error occurred , so please check once in ECC side . Otherwise see how many packets are still process, make it red that infopackage and do manually update.
Hope it helps,
By,
Praveen Yagnamurthy,
SAP BI Consultant,
Blue Marlin Systems-INDIA.
http://bluemarlinsys.com/bi.

Error when updating Idocs in Source System - Urgent

Hi Team,
When i was loading the data from SAP R/3 to BW, i was facing the error "Error when updating Idocs in Source System" (0 From 0 Records).
When i check in the Environment>Transaction RFC->In the Source System, it was displaying the error--
<b>" Import container contains errors (are any obligato) in the Function Module: IDOC_ERROR_WORKFLOW_START_R".</b>
Can any one please help me to solve this error.
This is am Urgent requirement for me to deliver.
Thanks & Best Regards,
Venkata.

Hello VenkaTa,
How r u ?
The workflow settings are not proper it seems. Ask the BASIS people to correct the Work Flow Settings. Then try Updating the IDOCs manually.
Also check the Inbound and outbound IDOCs in the Source system. The outbound should contain some warnings or errors.
Best Regards....
Sankar Kumar
+91 98403 47141

Error when updating Idocs in Source System

Hi All,
We did a recent copy from QAS to DEV,after which am unable to run my process chains ,the load status still showin yellow signal,whereas job is getting finished but am unable to load datas to the targets. Am getting the following error message when i see the display message in process chain.
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Source System . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
Error when updating Idocs in Source System
Could anyone please let me know what can be done ?
Thanks
con

Hello All,
I have same problem but its RESOLVED by the following process.
Step - 1
execute the Function module "SCP_LANGUAGES_IN_INSTANCE". It may or maynot give some output. Just note if it give the output
Step - 2
in Transaction SE38 execute the program "RSCPINST".
Just Click on the Activate button (dont select anything).
Step - 3
Again do the same thing specified in Step - 1. Now it will give the output saying that Language is DE.
So by the above procedure my issue is been resolved.
Regards
Sankar

Error in codepage mapping for source system

Hi Experts,
I am getting the following error while loading data from ECC only for Account COPA datasource.
Error in codepage mapping for source system. Error text:
Message no. RSDS_ACCESS013
Regards,
Sandeep Sharma

Hi Sandeep,
This is a issue related to idocsRFC connections from teh sourcesystem....
U can contact ur BASIS team to solve this...
From their end they have to chk the unprocessed/errored idocs in BD87...
They have to run a report:RBDAGAIN to process the errored idoc's in the source which are in STATUS:'02'.
This is a solution for temporarilrly basis...
If this occurs regularly they have to change the settings in SM59 which is so important...
Refer exact note for this: 784381
The SAP note 613389 may also be relevant for the error message "Could not find code page for receiving system", please check the information given in the note and see if you can use it to resolve the problem.
Regards,
Marasa.

Error : Unicode setting doesnot match source system in BW

Hi All,
While replication data in BW im facing the following error :
unicode setting doesnot match source system.
Kindly suggest.
Regards,
Amit Miglani.

Hi,
We have installed a fresh BIW server on MSSQL database 2005. We have selected components like as ABAP.JAVA,EP,EP Core ,BI Java. While replicating the datasource using tcode RSA1 from R/3 Retail Server we are getting an error Error in module RSQL of the datasource inter face .
Details of Support package level-:
SAP_ABA 700 0016 SAPKA70016 Cross-Application Component
SAP_BASIS 700 0016 SAPKB70016 SAP Basis Component
PI_BASIS 2006_1_700 0007 SAPKIPYM07 Basis Plug-In (PI_BASIS) 2006_1_700
SAP_BW 700 0018 SAPKW70018 SAP NetWeaver BI 7.0
BI_CONT 703 0008 SAPKIBIIP8 Business Intelligence Content
Please suggest us the solution.
Note: we are not getting any dump in st22. we have already checked the note 1162821
Regards,
Amit Miglani.

Error in codepage mapping for source system. Error

Hi BW Experts,
I am facing following error:
Error message: Error in codepage mapping for source system. Error text:
Details: Inbound Processing ( 1000 Records ) : Errors occurred
Error in codepage mapping for source system. Error text:
Update PSA ( 0 Records posted ) : Missing messages
I repeated the delta working and everything fine.
Does anybody know why this error occurs?

Run rsa13 (for bi 7.0) find your source system which one you are using for data transfer and double click on it and find special options there select the optioned i mentioned already.
Please search SDN you can fin threads related to this thread
if not let me know.
Regards.

Error in codepage mapping for source system. Error text:

guyz,
im facing the below issue in prod.
Error in codepage mapping for source system. Error text:
Message no. RSDS_ACCESS013
Collection in source system ended
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Inbound Processing
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
need your guidance,
cheerz,
raps.
Edited by: raps on Mar 1, 2012 9:39 AM

Hi ,
Kindly go throught the following threads for your issue resolution::
Error in code page mapping for Source System
Erroe in source system
Regards,
Arpit

Collecting data from two R3 source systems

Dear All,
Scenario:
We are in the process of implementing SAP BI 7.0 in our organisation.
We have a single BI server (7.01) collecting data from two source
systems from two different divisions within the group.
The first system is of Company 1 where we have IS u2013 MILL (ECC 6.0).
BI has been implemented and running successfully in this unit. Now we
have started implementing BI in the second unit u2018Company 2u2019
where the industry specific solution IS u2013 AFS (ECC 6.0) is the source
system.
We are activating BI Standard Content for AFS. When we try to upload
master data, we face a problem.
The master data (0Division, 0Mat_Grp_3, etc.) is already loaded with
IS Mill data (data from the first source system). Now when the data is
loaded from IS AFS (second source system), wherever, the same key
exists in the info object, we notice that the existing data is
overwritten by the freshly loaded data, thus causing loss of existing
data.
A typical example is as follows:
BW Data u2013 Source system 1 u2013 (Before upload of data from source system
2):
0Division
99         EN          Stock Transfer Out
AFS Data (Source system 2) -
0Division
99         EN             STO
BW Data u2013 Source system 1 u2013 (After upload of data from source system 2):
After uploading the master data from AFS, the Values areu2026
0Division
99        EN            STO
The original data is lost.
Similar problem is noticed with other master data as well.
Please suggest the right methodology for upload of master data when
data to BW is sourced from two systems. How to retain the data in the
same Infoobject but at the same time maintain distinction between the
data from the two systems.
We donu2019t find any specific mention of such scenarios in the standard
documentation.
Will such a problem recur when we upload transactional data?
Regards,
Aslam Khan

Hi Aslam,
            Please use some compounding attribute for your master data object like Sourcesystem ID. While loading the master data from different source systems... you should have two different flows to fill the same master data object. In each flow you can specify the Source system ID as constant value ... eg SS1 (Source system 1) and SS2(Source system 2) in each of the data flows.   This should solve your issue without overwriting your master data
Thanks
Kishore

Master Data cleansing and transformation from non-SAP source systems

Hi all,
Our client (Media)wants to cleanse and transform his master data from non-SAP source system to be uploaded into BW (no R/3 yet). If anybody has a document regarding this topic that i could use, i will appreciate if u sent it to me.
thanks.

Hi,
https://websmp203.sap-ag.de/~sapidb/011000358700001965262003
https://websmp203.sap-ag.de/~sapidb/011000358700006591612001
https://websmp203.sap-ag.de/~sapidb/011000358700001971392004
https://websmp203.sap-ag.de/~form/sapnet?_SHORTKEY=01100035870000471477&_OBJECT=011000358700008927932002E
/manfred

Differentiating Master Data from two different source systems

Friends,
i have used standard InfoObjects that provide master data for two InfoCubes which take data from two different source systems. Now the some of the master data is identical in both the source systems (example: 10 stands for "Industrial" in one whereas 10 stands for "Agricultural" in the other). What do i do so that the system(BW) differentiates the two.
Thanks in advance for all the help.
Mike

I tried to include the 0SOURSYSTEM in the compounding of this InfoObject (for master data) but it gives me a list of other objects that use this InfoObject as a reference characteristic and also says that this InfoObject is used in a ODS and data needs to be emptied in the ODS before activating this InfoObject. Please let me know if there is any way out of it.
Thanks
Mike

Error is data loading from 3rd party source system with DBCONNECT

Hi,
We have just finished an upgrade of SAP BW 3.10 to SAP NW 7.0 EHP1.
After the upgrade, we are facing a problem with data loads from a third party Oracle source system using DBConnect.
The connection is working OK and we can see the tables in the source system. But we cannot load the data.
The error in the monitor is as follows:
'Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.'
But, unfortunately, the error message has no further information.
If we look at the job log in sm37, the job finished with the following log -
27.10.2009 12:14:19 Job started                                                                                00           516          S
27.10.2009 12:14:19 Step 001 started (program RSBATCH1, variant &0000000000119, user ID RXSAHA)                    00           550          S
27.10.2009 12:14:23 Start InfoPackage ZPAK_4FMNJ2ZHNNXC6HT3A2TYAAFXG                                              RSM1          797          S
27.10.2009 12:14:24 Element NOAUTHORITYCHECK is not available in the container                                     OL           356          S
27.10.2009 12:14:24 InfoPackage ZPAK_4FMNJ2ZHNNXC6HT3A2TYAAFXG created request REQU_4FMXSQ6TLSK5CYLXPBOGKF31G     RSM1          796          S
27.10.2009 12:14:24 Job finished                                                                                00           517          S
In a BW 3.10 system, there is no message related to element NOAUTHORITYCHECK. So, I am wondering if this is something new in NW 7.0.
Thanks in advance,
Rajib

There will be three things to get the errors like this
1.RFC CONNECTION FAILED
2.CHECK THE SOURCE SYSTEM
3.CHECK IT OUT WITH Oracle Consultants WEATHER THEY ARE FILLING UP THE LOADS.TELL THEM TO STOP
4.CHECK I DOC PROCESSING
5.FINALLY MEMORY ISSUES.
6.CATCH THE DATA SOURCE FIRST CHANGE IT AND THEN ACTIVATE AND RUN THE LOAD
7.LAST IS MEMORY ISSUE.
and also Check the RFC connection in SM59 If it is ok then
check the SAP note : 692195 for authorization
Santosh

0HR_PA_EC_01 Extractor error converting from currency in source system

Similar Messages

Maybe you are looking for