RFC FM call problem uni-code to non-unicode?

Hi SDN,
I am calling RFC fun. module from non-unicode system to a uni-code system.
i am calling this FM from various systems is there any way in target system to know whether the call is from uni-code system or non-unicode system.
Regards,
Rahul.

Hi,
I think it is not possible for the reason that an RFC function module can be called from not only an SAP system but also from any non-SAP system like a J2EE Application in which case it does not make sense to know if the calling system in unicode or not.
But still check with the SYST structure in SE11 if there is any system field.
Regards,
Sesh

Similar Messages

Target system install problem (SAPINST searching for Non unicode kernel)

Hi,
I'm currently performing a unicode conversion (from 4.7 to EHP4). I am finished with the upgrade and I'm now in the unicode conversion part.
I have completed the export and selected unicode as the target system. I am done with source system uninstallation and I'm now installing the unicode target system. I have selected unicode during the parameter selection (it's the default option anyway) but during the part where it will ask for the kernel DVD, it doesn't accept the path of my unicode kernel (and instead looks for the non-unicode kernel)

Hi Markus,
Thanks for your response. This problem is now resolved. It turns out that there are some remaining files from the old /usr/sap/<> and /sapmnt/SID/exe that were not deleted yet (after uninstalling for non unicode system). I proceeded to delete again these files and ensure that there are no files from the non unicode system

Report Script output in UTF-8 code with Non-Unicode Application

Essbase Nation,
Report Script output (.txt) file is being coded as UTF-8 when the application is set to Non-unicode. This coding creates a signature character in the first line of the text file, which in turn shows up when we import the file into Microsoft Access. Does anyone know how to change the coding of the output file or know who to remove the UTF-8 signature character.
Any adive is greatly appreciated.
Thank you.
Concerned Admin

You may be able to find a text editor that can do the conversion. Alternatively, I have converted from one encoding to the another programmatically using Java as well.
Tim Tow
Applied OLAP, Inc

Passing chinese character from RFC call between unicode & non unicode syst.

Hi Experts,
I am making a RFC call from an ABAP in non unicode system to a Function module in Unicode system and filling the itab fields in ABAP by using move statement and using offset in order to populate amount fields correctly from flat structure tables returned by function module. But i am facing problem in getting chinese characters correctly in return from the Remote Function Module.
        CALL FUNCTION 'ZFXX_GET_CLR_OI'
          STARTING NEW TASK W_TASKNAME
          DESTINATION S_RFCDES-LOW
          PERFORMING F3100_GET_RFC_DATA ON END OF TASK
          EXPORTING
            P_WAERS               = P_WAERS             "Screen Curr
            P_AUGDT               = P_AUGDT             "Clearing date
            P_BUKRS               = P_BUKRS             "Comp Code
          TABLES
            T_SEL_TABLE           = T_SEL_TABLE
            T_OUTPUT              = T_MCDATA
            T_ERRORS              = T_EMCDATA
          EXCEPTIONS
            COMMUNICATION_FAILURE = 1
            SYSTEM_FAILURE        = 2
            OTHERS                = 3.
       MOVE : t_mcdata1-line+0(32)   TO t_succs-awsys,
               t_mcdata1-line+32(4)   TO t_succs-bukrs,
               t_mcdata1-line+36(10) TO t_succs-belnr,
               t_mcdata1-line+46(4)   TO t_succs-gjahr,
               t_mcdata1-line+50(1)   TO t_succs-shkzg,
               t_mcdata1-line+51(2)   TO t_succs-bschl,
               t_mcdata1-line+53(4)   TO t_succs-gsber,
               t_mcdata1-line+57(16) TO t_succs-dmbtr,
               t_mcdata1-line+73(16) TO t_succs-wrbtr,
               t_mcdata1-line+89(5)   TO t_succs-pswsl,
               t_mcdata1-line+94(6)   TO t_succs-vbund,
               t_mcdata1-line+100(10) TO t_succs-hkont,
               t_mcdata1-line+110(10) TO t_succs-prctr,
               t_mcdata1-line+120(16) TO t_succs-dmbe2,
               t_mcdata1-line+136(20) TO t_succs-txt20.
        APPEND t_succs.
Can anybody suggest or advice me on it ? Any help or suggestion would be appreciated.
Thanks in advance,
Akash

.

RFC Destination - Unicode / non - Unicode behavior

Hi All,
In our current production system the RFC destination from R3 to Xi is non-unicode.We have currently 300 Interfaces running using this RFC destination in production.
In few upcoming requirements for some 15 Interfaces some special characters will come from R3 to Xi system.In this case we need a unicode RFC Destination.
I have a query here , can i go ahead and change the existing RFC destination to Unicode or is it suggestible to create a new RFC destination only for these 15 Interfaces?
Need expert advice on this?
<<Text removed>>
Regards,
RK
Edited by: Matt on Oct 5, 2011 9:38 AM

Hello,
The Non-Unicode Single code page systems are supported by SAP for older applications for historical reasons - unicode was not available when they were released. These systems are restricted to only processing characters from their specific code page. This means their can be restrictions if they need to support language combinations that span multiple code pages - basically it is not possible. In addition some languages are not fully available at all for single code page systems like Thai. In addition the Euro symbol is not available.
Unicode is the future for all applications - SAP or otherwise. The significance at the moment is where customers who needs to convert to unicode to support additional business requirements like additional languages. Converting a system, although a simple process is not a trivial process in terms of time and resources.
So u can go ahead and change the existing RFC destination to Unicode .it will not create any prob. for other interfaces which are using non unicode setting.
Regards
Monica

CRM2007 unicode system display broken charactor downloaded non-unicode R/3.

Hi all
CRM2007 is only unicode system and R/3 is 620 non_unicode system.
CRM2007 unicode system display broken charactor downloaded data from non-unicode R/3.
how can I do??
any help
thanks

Lee,
Technically it is not supported. You could change a few middleware settings to transmit the bdocs as XML to prevent issues, but really if your CRM is unicode then ERP needs to be unicode and vice-versa.
Only exception is that generally the english code-page non-unicode works okay with unicode english.
You can adjust CRMRFCPAR for the bdoc to transmit in xml vs native.
Take care,
Stephen

Problem in RFC call in ABAP code...Urgernt

Hi ,
I am working on scenario wherein , i have created remote enabled RFC in target system SAP R/3 one . I have maintained RFC in original system where i have my calling program.This done by using sm59 transaction .When i execute my abap calling program as follows , it gives out error as RFC destination not known.The code is
CALL FUNCTION 'ZRFC_01' DESTINATION 'IDECECC5'
EXPORTING nu1 = num1 nu2 = num2
IMPORTING res = result .
write: result .
This call passes two numbers for addition and returns result as addition in import parameters.
KIndly help me on this

Hi,
First of all do not forget to add standard SAP exceptions to your code to avoid shotdumps in case there is something wrong with the RFC connection:
CALL FUNCTION 'ZXXX' DESTINATION 'ZXXX'
   EXCEPTIONS
     SYSTEM_FAILURE = 1
     COMMUNICATION_FAILURE = 2.
Test your RFC connection in SM59 transaction. Make sure as well you did not make any typing errors, the best would be just copy its name from SM59 to your code.

Syntax errors while migrating from non- unicode to Uni code

What are the syntax errors while migrating from non unicode to Uni code

Hi Sudheer,
u can get the information related to errors while migrating from non- unicode to Uni code from the below...pls go through...
Note 765475 - Unicode Conversion: Troubleshooting
these are the notes related to the issues of migration form non unicode to ounicode.
Related Notes
986907 - SQL Server settings for R3load based system copy
954001 - Error fix: ILLEGAL_SUBSTRING_MODIFICATION in SUMG
936441 - Oracle settings for R3load based system copy
928909 - Repair table data in SUMG in Unicode systems
895804 - Problematic rows in table DMEE_TREE_NODE
895560 - Support for languages only available in Unicode system
885441 - Common Migration Errors
842788 - DB Multiconnect: Unicode Migration
837173 - RADCUCNT in Unicode Conversion: Collective Note
756534 - Automatic Assignment of Languages with Character Statistics
753334 - Unicode Conversion: Problem in Japanese device types
726954 - Private Use Areas in Unicode Systems
722193 - RFC legacy non-Unicode clients and Unicode servers
718329 - R3load terminates the export during a Unicode conversion
695196 - Error in the export for Unicode migration
672835 - Textflags could cause problems during Unicode conversion
627764 - Unicode migration: table pools inconsistent after conversion
614550 - Troubleshooting BC-I18
587896 - Add. info on upgrade to SAP R/3 Enterprise Core 4.70 SR1
573044 - Unicode conversion for HR application
480671 - The Text Language Flag of LANG Fields
379940 - Unicode based mySAP availability
79991 - Multi-Language and Unicode support of SAP applications
73606 - Supported Languages and Code Pages
42305 - RSCPINST (I18N configuration tool)
regards,
rudra..
Assign points if helpful

Problem using RFC to call an adobe form to create pdf file........

Hi,
   I have an RFC that calls an adobe form to display the pdf output back in a bsp page...the RFC fails at the call to the adobe form (next call after after getting the form name) ...while debugging it looks like within this call it is trying to call fpcomp_job_open and failing on the call check_job_open ...
The code in my RFC looks like this....
DATA:
    gs_outputparams TYPE sfpoutputparams,
    fn_name           TYPE rs38l_fnam,
    fp_docparams      TYPE sfpdocparams,
    fp_formoutput     TYPE fpformoutput,
    frm_result        TYPE sfpjoboutput,
    lv_form           TYPE fpname.
DATA: l_pdf_xstring TYPE xstring,
       l_pdf_len      TYPE i.
lv_form = 'ZHR_ASSESSMENT_FORM'.
Start formrocessing - OPEN spool job to send to printer
gs_outputparams-getpdf = 'X'.
call function 'FP_JOB_OPEN'
    changing
      ie_outputparams = gs_outputparams
    exceptions
      others          = 1.
IF sy-subrc <> 0.
*//    RAISE FP Open Error.
      exit.
ENDIF.
Get name of the generated function module for the form
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
    EXPORTING
      i_name     = lv_form
    IMPORTING
      e_funcname = fn_name.
IF sy-subrc <> 0.
*//    RAISE FP Get Form Module Name Error.
        exit.
ENDIF.
Call the Adobe Form
CALL FUNCTION fn_name
EXPORTING
      /1bcdwb/docparams = fp_docparams
      gv_appraisal_id = gv_appraisal_id
IMPORTING
     /1bcdwb/formoutput = fp_formoutput
    EXCEPTIONS
      usage_error        = 1
      system_error       = 2
      internal_error     = 3
      others             = 4.
IF sy-subrc <> 0.
*//    RAISE Call Form Module Error.
        perform f_build_message using 'E'
                                  'ZEXT'
                                  012
                            changing return.
       exit.
ENDIF.
End from processing - Close spool job
CALL FUNCTION 'FP_JOB_CLOSE'
    IMPORTING
      e_result       = frm_result
    EXCEPTIONS
      usage_error    = 1
      system_error   = 2
      internal_error = 3
      OTHERS         = 4.
IF sy-subrc <> 0.
*//    RAISE FP Close Error.
       exit.
ENDIF.
form = fp_formoutput-pdf.
Thanks,
Venkatesh

what is the solution for this problem? I have the same problem. I get sy-subrc = 1 after CALL FUNCTION 'FPCOMP_JOB_OPEN'.
If I look more in detail I see that "Perform check_job_open" is creating the problem:
FORM check_job_open.
IF fpstat-is_opened = c_true. (--> exactly here is the problem. This condition is true so the program is terminated.)
    PERFORM reset_status.
    MESSAGE ID 'FPRUNX' TYPE 'E' NUMBER '101' RAISING usage_error.
ENDIF.
fpstat-is_opened = c_true.
fpstat-is_started = c_false.
ENDFORM.
Does somebody know why my job is open and what is the solution to have the job closed at the beginning of my processing?
Thanks in advance.

Regarding Conversion Of ABAP program from non unicode to uni code

Hi Can you please let me know the procedure for converssion of non unicode to unicode?
Thanks in advance,
zubera

Hi
The Link will be helpful to you.
Re: Upgrade 4.6 to ECC - What are the responsibilites
regarding Unicode influence in Standard programs
Very good document:
http://www.doag.org/pub/docs/sig/sap/2004-03/Buhlinger_Maxi_Version.pdf
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d37d1ad9-0b01-0010-ed9f-bc3222312dd8
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/589d18d9-0b01-0010-ac8a-8a22852061a2
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f8e316d9-0b01-0010-8e95-829a58c1511a
You need to use the transaction UCCHECK.
The report documentation is here
ABAP Unicode Scan Tool UCCHECK
You can use transaction UCCHECK to examine a Unicode program set for syntax errors without having to set the program attribute "Unicode checks active" for every individual program. From the list of Unicode syntax errors, you can go directly to the affected programs and remove the errors. It is also possible to automatically create transport requests and set the Unicode program attribute for a program set.
Some application-specific checks, which draw your attention to program points that are not Unicode-compatible, are also integrated.
Selection of Objects:
The program objects can be selected according to object name, object type, author (TADIR), package, and original system. For the Unicode syntax check, only object types for which an independent syntax check can be carried out are appropriate. The following object types are possibilities:
PROG Report
CLAS Class
FUGR Function groups
FUGX Function group (with customer include, customer area)
FUGS Function group (with customer include, SAP area)
LDBA Logical Database
CNTX Context
TYPE Type pool
INTF Interface
Only Examine Programs with Non-Activated Unicode Flag
By default, the system only displays program objects that have not yet set the Unicode attribute. If you want to use UCCHECK to process program objects that have already set the attribute, you can deactivate this option.
Only Objects with TADIR Entry
By default, the system only displays program objects with a TADIR entry. If you want to examine programs that don't have a TADIR entry, for example locally generated programs without a package, you can deactivate this option.
Exclude Packages $*
By default, the system does not display program objects that are in a local, non-transportable package. If you want to examine programs that are in such a package, you can deactivate this option.
Display Modified SAP Programs Also
By default, SAP programs are not checked in customer systems. If you also want to check SAP programs that were modified in a customer system (see transaction SE95), you can activate this option.
Maximum Number of Programs:
To avoid timeouts or unexpectedly long waiting times, the maximum number of program objects is preset to 50. If you want to examine more objects, you must increase the maximum number or run a SAMT scan (general program set processing). The latter also has the advantage that the data is stored persistently. Proceed as follows:
- Call transaction SAMT
- Create task with program RSUNISCAN_FINAL, subroutine SAMT_SEARCH
For further information refer to documentation for transaction SAMT.
Displaying Points that Cannot Be Analyzed Statically
If you choose this option, you get an overview of the program points, where a static check for Unicode syntax errors is not possible. This can be the case if, for example, parameters or field symbols are not typed or you are accessing a field or structure with variable length/offset. At these points the system only tests at runtime whether the code is sufficient for the stricter Unicode tests. If possible, you should assign types to the variables used, otherwise you must check runtime behavior after the Unicode attribute has been set.
To be able to differentiate between your own and foreign code (for example when using standard includes or generated includes), there is a selection option for the includes to be displayed. By default, the system excludes the standard includes of the view maintenance LSVIM* from the display, because they cause a large number of messages that are not relevant for the Unicode conversion. It is recommended that you also exclude the generated function group-specific includes of the view maintenance (usually L<function group name>F00 and L<function group name>I00) from the display.
Similarly to the process in the extended syntax check, you can hide the warning using the pseudo comment ("#EC *).
Applikation-Specific Checks
These checks indicate program points that represent a public interface but are not Unicode-compatible. Under Unicode, the corresponding interfaces change according to the referenced documentation and must be adapted appropriately.
View Maintenance
Parts of the view maintenance generated in older releases are not Unicode-compatible. The relevant parts can be regenerated with a service report.
UPLOAD/DOWNLOAD
The function modules UPLOAD, DOWNLOAD or WS_UPLOAD and WS_DOWNLOAD are obsolete and cannot run under Unicode. Refer to the documentation for these modules to find out which routines serve as replacements.
Regards
Anji

ACE# sh script code - Error: Called API is invalid or non-existant

What is this ??
ACE# dir disk0:
2846 Jun 14 2010 15:40:33 NORDICID_PROBE
ACE# sh script code NORDICID_PROBE
Error: Called API is invalid or non-existant
Hardware is ACE-4710-K9 and software A3(2.7)
The probe itself is functioning ok according to show probe detail.
However show script script_name probe_name -counters all remain at zero for some reason. This wasn't the case on the previously use ACE software.
To my recollection the command show script code has worked successfully before on the same ACE software. Not 100% sure though, but it definitely worked on the previous software we ran on the ACE.

Hi Timo,
You could be hitting CSCtu33866 (see
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtu33866 for more details)
If you are really hitting this bug, a reboot should fix the issue.
I hope this helps
Daniel

RFC destination definition with non-unicode external program

Hello All,
we have one issue with our RFID system connecting to WM system (SWD).
For most functions, external RFID server/middleware makes RFC call to SAP system. Means, from outside system to inside SAP. This seems to be working fine.
But in one case, SAP needs to print label to RFID printer. In this case, SAP is calling external RFID server/middleware using RFC destination. Means, from inside SAP to outside system. This is failing.
We think this has something to do with ECC60 being unicode system, and the RFC destination setup. We define rfc destination "ZRFID_SSI" in SM59. We define it same way as in as-is SSI 4.6B production system. But in SWD ECC60 system, SM59 has more options. We define as 'non-unicode' because target RFID server/middleware is non-unicode Windows server. RFC destination is actually working ok.
To send label to printer, SWD calls function ZFSSIRF202 with remote destination ZRFID_SSI. Listener on RFID server/middleware will respond to function call. This also seems to be working. But then, RFID server/middleware cannot process the data from ZFSSIRF202, log says that data is "0". (Actually, the first time SWD calls, log says 0 data, the 2nd time there is connection failure, the 3rd time it is 0 data, 4th time connection failure, etc, etc.)
Compared with production environment, everything is the same, except that SAP is unicode system. So, our suspicion is, that when ECC60 system sends data, it is encoded somewhat a little different than when SAP 46B system sends data. I have similar experience with our other interface (XSI), also involving RFC desintion, but XML file exchange. Here, ECC60 is encoding XML file with UTF-16, but SAP46B was encoding with UTF-8.
Anyone know how to help ?

Hi Jeongbae,
as of NW 7.0 EhP2, it is possible to directly set the code page in SM59.
In earlier releases, this is not possible.
In general, SAP systems use the logon language (SY-LANGU) to determine the code page, if this is available.
Please check SAP note 788239.
Please also have a look at SAP note 991572 for possible alternative settings, if SY-LANGU is not available.
In addition I would recommend to have a look at SAP note 1021459.
However in order to analyze the problem properly, you need to know the exact short dump text (via rfc trace).
For XML processing, please read SAP note 1017101. UTF-16 should NOT be used in an XML file !
Best regards,
Nils Buerckel
SAP AG

Program send from uni code system to XI

I will send data from uni-code system to XI system
but I need to sent using non-unicode mode (setting RFC)
But I have a problem when I sent data กรกช Data will determin in SAP XI as "####" how can I do?
Best REgards,
@tom

please read the rule of engagement dont raise multiple thread.
with non unicode RFC setting in R3 is not possible as said in another thread.
chirag

RFC Message: Internal Problem, in REDWOOD CPS.

We have Redwood CPS 7 connected up to SAP IS-U Supply.
We keep getting random RFC errors when executing a script.
Any Idea
ERROR LOG   *******************
ABAP_RUN: R/3 call BAPI_XBP_JOB_OPEN failed
RFC error: XM034
RFC Message: Internal problem (function BAPI_XBP_JOB_OPEN)
TCTRETURNS/        : deleted
/ERROR LOG   *******************

Hi,
if this is a random issue I assume that the authorizations of the CPS communication user are OK, otherwise please verify:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/49/bb35b8623a489aa63abd9f5ebf2448/frameset.htm
If this random issue happens only if you execute your custom script, I would assume that the script wants to create a job with invalid data. For example: some data is missing or wrong like start date/time, job class, job user, job name.
Let's analyze what you have posted here:
RFC error: XM034
RFC Message: Internal problem (function BAPI_XBP_JOB_OPEN)
-> XM034 point to the XMI log
-> use transcation RZ15 to analyze the XMI log
-> XM034 means "problem detected" (see appendix 8 of document ftp://ftp.sap.com/pub/icc/bc-xbp/BCXBPDOC70V3.pdf)
I locked into the code and indeed it seems that function BAPI_XBP_JOB_OPEN returns this message if the job cannot be created.
So if Sys- and XMI-Log cannot help you in solving this issue, I would create a message for dev. support.
Cheers,
Martin
http://service.sap.com/jsm

SLDCHECH: Function call returned exception code 3

Hi all.
I am trying to set up ESS and MSS on EP 6.0 SP15.
I have configured the RFC destination, and when i do a test in RZ70 and SM59 everything is ok, but when i try running transaction SLDCHECK i get the following error:
Use transaction SLDAPICUST if you wish to maintain the SLD server access data
Launching the SLD GUI in a separate browser window...
=> Verify in the browser GUI that the SLD is in a healthy running state!
Calling function LCR_LIST_BUSINESS_SYSTEMS
Retrieving data from the SLD server...
Function call returned exception code 3
=> Check whether the SLD is running!
Summary: Connection to SLD does not work
=> Check SLD function and configurations
Can anybody shead some light on this problem?
Regards Liselotte

Dear Liselotte,
This will help you,
http://help.sap.com/saphelp_nw04/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
Might be Java version to the proxy settings. Try to go thru listed down various troubleshooting steps in following this weblog.
Unable to open IR/ESR/ID ? (XI/PI/PI 7.1) [Updated for PI 7.1 support]
Regards
Agasthuri Doss

RFC FM call problem uni-code to non-unicode?

Similar Messages

Maybe you are looking for