'Classic' RFC library - password limited for rfc calls ?

Hi ,
we are using the 'classic'  RFC library to connect  to SAP for calling RFC function modules. Due to the fact that there are often older SAP systems involed, we use only passwords with 8 digits. But now we have the requirement to use passwords for the rfc user with more than 8 digits.  According to my todays knowlede, the password is limited to 8 digits with the standard rfc lib.
Can the newer SAP NW RFC lib handle a password with more than 8 digits ?
But  am i right that the SAPNW RFC lib is unable to handle rfc calls with opening a SAPGUI ?
thx
Heike

Hi,
thank you for your answer!
I have investigated something new yesterday:
I thought at the beginning, that the problem just occurs, when the system work processes are reached. The system has for example set up 15 dialog processes and the external server is calling the function 20 times in parallel. Then we normally need 5 dialog processes more. The system is taking then all 15 dialog processes and the locks got stucked.
That means, that I´ll maybe only get 4 or 5 uploads, which have really been updated the tables. All the others couldn´t get the table locked for their process.
But if I now let the server call the function just about 13 times in parallel, nearly all uploads have been updated the table!
From my point of view, the lock from SAP gets stucked, when the limit of dialog processes is reached. It´s not working in the right way anymore...
The same is happening, when you set up in the system, that only 10 work proecesses can be used by RFC. If I have more than 10, it´s going to be critical with the locks....
WEIRD!
Can anybody help me out of trouble?
Thank you!

Similar Messages

  • Call time limiting for VOIP calls

    Hi,
    i want to limit voip calls to a specific period of time. Is there a way to handle this issue (with or without gatekeepers)? I'm using IOS gatekeepers and gateways with FXS,FXO and BRI.

    had same issues with disconnection with FXO for all my sites.
    had a post with the resolution. mine was also loop start. asked service provider to put lines into a trunk (minimal cost). the reason for this is that we can enable disconnect to be handled from service proivder instead of the FXO itself. that fixed issue (BTW issue was that even though call ended, fxo disconnected after may two hours, and some didnt at all).
    i also had a few routers that still gave a long diconnect time although i cocnverted, i had to enable the supervisory disconnection options as well as TIMING SUP-DISCONNECT parameter (Please note not available in all IOS versions). i set my disonnect to be 300 matching up to my provider. Now, all my sites are working great.
    as for ground start, ive tried it once and that really did work great(for a time.) i did have issues later on where i couldnt make any calls outside etc etc. reverted to my initial loop-start workaround and that worked fine.
    i am giving suggestions to try since i was in a serious dilema for a few months, trying to fix this. for me i know its frustrating so i hope it may help.

  • HT1937 Dear Sirs, i have a sugestion to the Apple that: in IOS7 you should add a funtion time limited for a call. For example after talking 10 minutes the phone will hang up. Thank you very much.  Truly, Nguyen Tuan Thinh

    Dear Sirs,
    I have used an Iphone 5 for some months ago. But I cannot find the way to hang up automatically. So I suggest to the Apple that in IOS7, you should ad that function. For example, after talking 8 or 10 ... Minutes, the phone can hang up automatically. Because, there are many services provider promost 10 minutes free.
    Thank you very much.
    Tuan Thinh

    We are not Apple, we are users just like you. To communicate with Apple go to http://www.apple.com/feedback/iphone.html

  • RFC Strucutre Size Limitation

    Hi all,
    Can you please tell if there is a strucure size (let's say number of characters) limitation for RFC's? Thank you in advance.

    Hi,
    Maximum number of characters in ABAP is 65535 bytes.
    I think in RFC you cannot declare a field of more than 65535 bytes. How many characters data you want to send to RFC?
    Regards,
    Saba

  • Setting password limits on SYS, SYSTEM, DBSNMP

    We are having a security audit conducted and the auditors want us to set password limits for system accounts (SYS, SYSTEM, DBSNMP). They're asking us to set PASSWORD_LIFE_TIME, PASSWORD_GRACE_TIME, PASSWORD_REUSE_MAX, PASSWORD_REUSE_TIME. I have not been able to find any documentation that discusses the implications of doing this, if any. I'm wondering what will happen if these accounts become locked and/or expired because of invalid login attempts and not changing the password in time. I need something definitive one way or the other to show the customer. Please help!
    Thanks,
    Susan

    Which operating System and which database release?
    In AIX you can define password limit on OS level (using smitty for it) very straight forward.
    You can also use OEM to do the password configuration which includes your assignment.
    DN

  • RFC Adapter Receiver - change SAP User for each call

    Hi guys,
    I need to create one connection between PI and SAP, all right, i can use RFC Adapter Receiver, no problem.
    But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
    Can anybody help me, please?

    hi,
    >>But, for each call i need to use User and Password different, then, I would pass SAP User and Password in my XML Payload.
    sure we can help you but no in this way:)
    it is possible to change the user for RFC adapter but using
    principal propagation:
    /people/alexander.bundschuh/blog/2007/01/16/principal-propagation-in-sap-xi
    this is the way you need to go and not send password in XML payload
    (this is certainly not the way and no client will approve it)
    why use a password is anyone can see it ?
    Regards,
    Michal Krawczyk

  • Rfc Library Call to SXMI_XMB_SYSLOG_READ : INVALID_DATE_TIME error

    I have a distributed NetWeaver 2004S Environment: Main SAP Instance and Database are located in a CST Time Zone on the same machine. A dialog SAP instance, installed on an HP-UX Itanium Host, is located in a PST Time Zone, but, the system clock set for CST time - 2 hours behind the main SAP instance host system clock time.
    My application is installed on the HP-UX Itanium Host and connects to the local (dialog) SAP instance, and makes RFC library calls to collect data. For Syslog data, the RfcCallReceive call is made to function SXMI_XMB_SYSLOG_READ with all the required input parameters. This call succeeds for the first time, but, fails all subsequent times if the call is repeated at 1 minute interval. Following error message is returned:
    gid:105 key:INVALID_DATE_TIME
    The date times on start and stop times are correct - they match very well with the system clock time.
    Now, if I increase the repetition interval from 1 minute to 5 minute, the Rfc call to the function SXMI_XMB_SYSLOG_READ succeeds for the repeated calls.
    Please note that the Rfc application was compiled on an HP PA-RISC development machine, and, uses ARIES emulator to run on HP Itanium Host.
    There is another piece of information I can provide here if that helps: I am able to make 1 minute spaced repeated Rfc call to SXMI_XMB_SYSLOG_READ function with success on a PA-RISC dialog instance of another SAP deployment that has the main SAP instance plus database on one machine in a CST time zone, and, the dialog SAP instance hosting the application on PA-RISC host on a different machine, but, in the same CST time zone.

    Hi Manoj,
    The Application and the dialog instance are on the same machine - HP-UX IA64. This is what TZ has on this host
    TZ=CST6CDT
    How do I synchronize the application and the SAP dialog instance  - they are located on the same physical machine?
    The main instance and the database are on another machine - SunOS5.10 sparc. This is what TZ has on that host
    TZ=US/Central
    The date on HP-UX IA64 (dialog instance) is
    date
    Fri Nov 21 13:13:35 CST 2008
    The date on SunOS5.10 sparc (Main Instance + Database) is
    date
    Fri Nov 21 13:13:35 CST 2008
    Please note that the dialog instance and the main instance are located geographically in PST and CST time zones - being 2 hours apart.
    I appreciate very much your effort. Looking forward to the follow-up.
    Thanks

  • Not able to use password with characters for RFC User.

    hi All,
    I have installed SAP SCM 5.0 with MaxDB 7.6and liveCache 7.6.
    I created RFC user and RFC destination to administer liveCache globally as per SAP notes 305634 and 452745. I changed the initial passwords and tested Remote login for RFC User.
    But when I try to start liveCache with startrfc following the link below
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/95/379f3cad1e3251e10000000a114084/frameset.htm
    I got the following error
    RFC Call/Exception: SYSTEM_FAILURE
    Group       Error group 104
    Key         RFC_ERROR_SYSTEM_FAILURE
    Message     Name or password is incorrect (repeat logon)
    Then I logged into the CI with RFC user and try to start the liveCache with RSLVCSTART T-Code SE38..I got the following error.
    Error DBMCLI_COMMAND_EXECUTE_ERROR when starting liveCache LCS on server saplcslc
    Message no. LVC007
    I tried by changing the password for RFC user to numeric [0-9] and special characters [$,:] which worked fine.
    Does anyone faced this issue earlier? I searched notes, sdn and finally google ... but no luck to resolve the issue.
    Your help is much appreciated.
    Thanks,
    Venkat

    Yes I used LCA as liveCache connection. I resolved the issue with RSLVCSTART. Thanks for your suggestion to run connection test. I used wrong password for control user in the LCA connection. Now LCA connection shows everything is fine.
    But I am still not able to use alphanumeric password RFC user to start the liveCache from command line. I get the following when run startrfc command...
    bash-3.00$ /usr/sap/CAT/rfcsdk/bin/startrfc -3 -d LCSCLNT001 -h sapcatci -s 51 -c 001 -u LCSRFC -p Mach1cspsap\$ -l EN -F START_LIVECACHE_LVC -E IV_CON_NAME=LCA
    RFC Call/Exception: SYSTEM_FAILURE
    Group       Error group 104
    Key         RFC_ERROR_SYSTEM_FAILURE
    Message     Name or password is incorrect (repeat logon)
    bash-3.00$ echo $?
    1
    But I can start the liveCache from command line with numeric password successfully.
    bash-3.00$ /usr/sap/CAT/rfcsdk/bin/startrfc -3 -d LCSCLNT001 -h sapcatci -s 51 -c 001 -u LCSRFC -p 19811983\$ -l EN -F STOP_LIVECACHE_LVC -E IV_CON_NAME=LCA
    bash-3.00$ echo $?
    0
    Note the difference between the passwords used. Do i need to change any settings to accept alphanumeric passwords for RFC user.
    Note that I am able to start liveCache server in both cases(alphanumeric password and numeric password) by logging into SAP GUI and RSLVCSTART program. The problem is only when i try to start the liveCache from the commandline.
    Any help will be much appreciated.
    Thanks,
    Venkat

  • XML pay load for RFC call in java mapping

    Hi,
    I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
    Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
    Say i have 2 import parameters(input1,input2) and one output(output1)......
    Thanks in advance,
    H.L.Babu

    >
    hlbabu123 wrote:
    > Hi,
    > I searched in many forums about the payload to be given for RFC Lookup from a functional module,but i think i am not able to get it correct.
    >
    > Can any one please give me the exact structure of XML Payload to be sent while invoking the function module via RFC LOOKUP
    >
    > Say i have 2 import parameters(input1,input2) and one output(output1)......
    >
    > Thanks in advance,
    > H.L.Babu
    have a look at this document - https://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/a03e7b02-eea4-2910-089f-8214c6d1b439&overridelayout=true
    in case u still have issues do get back

  • Password for RFC USer

    Hi experts,
    We need to set the password for RFC User in small letters.But we are not able to do it ,because of our 'login/*' parameter values.
    Is there is any other method to create the password for User ID with small letters(Ex:welcome,hello)?
    Thanks in Advance,
    Karthika

    > > Login rules are not specific to user types. It is same for all type of users.
    > Sorry, this is not correct. The password validity rules are a good example which don't apply to SYSTEM and SERVICE type users. Other examples are the idle time rules and compliance to policy rules and the logon ticket rules and remote login via debugging rules and...
    >
    I tried to talk about is as per the ongoing discussion topic i.e. Case sensitiveness of Passwords and not other attributes. So from this point of view there is no such separate rule applies during admin imposed password or during a change (the cases where system prompts for changing password).
    > > From NAS 7 there is a change in the password rules.
    > There were major changes in 46B, and 6.10 and 6.40 as well, and Karthika still has not told us which release she is on.
    >
    Agreed totally.
    > > [Note 750390 - USR02: various problems with password attributes|https://service.sap.com/sap/support/notes/750390]
    > > [Note 624635 - Error messages with password change using RFC function|https://service.sap.com/sap/support/notes/624635]
    > I cannot see how these notes are related to this silly requirement of setting a lower-case only password.
    >
    I didn't went through in details fully but seen it contains a considerable error details.... may be of any help to OP.
    > I think either Karthika is playing a joke on us, or the person interviewing Karthika is playing a joke on her... These would be the only logical explanations left which I can see for for such a requirement.
    >
    May be.. but of course need more information and purpose of such strictness for setting such password. Also the FM PASSWORD_FORMAL_CHECK can be used with required customizations but you are the best person to tell this properly.
    regards,
    Dipanjan

  • Urgent  background  call for RFC?

    Hello all,
               I have designed a RFC(that is FM with RFC tab clicked)
    everything is fine ,but i just want to execute this RFC in background.what is  the procedure can anybody plz explain.

    Hi,
    Create an se38 report which calls this function module. Pass all the parameters. You may also give some select options too. Then schedule the report in background, which can satisfy ur requirement.
    If u have any further doubts pls post here.
    Regards,
    Renjith Michael.

  • Where may I download package for JAVA call SAP RFC

    Hi all,
    I need to call a RFC in a JAVA based system. I found I need to install two package before I call, such as:
    import com.sap.rfc.*;
    import com.sap.rfc.exception.*;
    import com.ibm.sap.bapi.*;
    import com.ibm.sap.bapi.generated.*;
    where can I download these 2 package?
    Thanks a lot in advance.
    Ned

    Hai ,
    im telling in Eclipse ..
    Take a look to see that those packages are listed in the plug-ins under
    Windows > Preferences > Target Platform.  This should point to an Ecilpse
    installation which should have most of those packages.
    You will need to install GEF separately.  It does not come with Eclpse.  Go
    to http://www.eclipse.org/gef/ and click on Downloads.
    Regards ,
    Venkat

  • Limitations of RFC Adapter XI 3.0

    In this presentation ( https://www.sdn.sap.com/content_documents/.../SAP%20XI%202.0%20-%20Features.pdf page 20), the following limitations are listed for the RFC Adapter for XI 2.0:
    Functionality
    Synchronous RFC
      No support forRFMsthat use update task without COMMIT WORK
      No SAP GUI
      No callbacks
      No session handling
      No RFCs to non-SAP systems (using RFC client or server libraries)
    tRFC: Support for exactly-once delivery for one message/call
      Not all tRFC functionality
      No „bundling“ of multiple calls
    With version 3.0, what are the current limitations??

    SAP Documentation states the following:
    Constraints
    Note the following restrictions:
    ·        Assignment is only guaranteed for transactional RFCs (tRFCs), that is, for messages with quality of service Exactly Once (EO).
    ·        There is no transactional context for more than one RFC call for each LUW (Logical Unit of Work).
    ·        Not provided: SAPGUI, callbacks, and qRFC (quality of service Exactly Once In Order (EOIO)).
    ·        RFC library clients (RFC SDK) are not supported.
    ·        The context in the called system is not kept open over multiple calls (calls are stateless; there is no session).
    ·        Only the payload of a received message is evaluated. Additional attachments are ignored and not forwarded.
    ·        The receiver adapter can only process valid RFC XML documents, for example, those generated by the sender adapter or by the SAP JCo.
    available at: http://help.sap.com/saphelp_nw04/helpdata/en/33/c6e63b60c25767e10000000a11402f/content.htm
    best Regards
    Christien

  • RFC destination for RFC to File scenario

    Hi,
    I m creating a TCP/IP RFC destination in R/3 system for my RFC to File scenario.
    Step 1:
    For this a Registered server program is created in Jco RFc Destinations with,
    Program Id : pgm1
    Gateway host : PI's host
    Gateway service : PI's service
    application server host: ECC's host
    system numer     : ECC's number
    client  : ECC's client
    logon user : ECC user
    password : pwd
    Step 2:
    In SM59, TCP/IP connection the following parameters are given:
    Program ID : pgm1
    Gateway host : PI's host       -
    > is this correct
    Gateway service : PI's service      -
    > is this correct
    Step 3:
    So i am calling the RFC in ABAP program (R/3 system) like:
    CALL FUNCTION 'Z_HR_OUTBOUND_DATA2'
    IN BACKGROUND TASK DESTINATION 'Z_HR_OUTBOUND_DATA2'
    Step 4:
    In PI side,
    for RFC sender I am passing :
    Application server : PI server
    Application server service: PI host
    program ID: pgm1 which was created in the previos step
    For RFC Metadata Repository Parameter, i am passing all the values related to R/3
    Please let me know whether the steps and values i given is correct.
    B'cos even if i give ECC's information in Gateway host and Gateway service the scenario works fine and if i PI's info then also it works fine.
    so i am confused as which is the correct method. pls clarify

    Ok I will try to explain....
    Assumptions: R3_TO_XI is the name of RFC which I created in ECC of type T.
    While creating the RFC in ECC we mention a unique name which is called Progaram ID. Now the same program id we mention in our sender RFC CC.
    So now when an ABAP Progarm (where you will call this RFC with it's destination) is scheduled/triggered with the code as mentioned below then since the DESTINATION ('R3_TO_XI') mentioned here contain the same program id which we have mentioned in our sender CC, invokes the adapter in PI and soon after that all pipeline steps get executed in XI.
    CALL FUNCTION 'ZBAPI_COMPANY_GETDETAIL'
      IN BACKGROUND TASK
      DESTINATION 'R3_TO_XI'
      TABLES
        comp_detail = company_detail.
    COMMIT WORK.
    Regards,
    Sarvesh

  • RFC Problem:"I::001 Only available with the RFC library from 4.0C onwards."

    Hello,
    Ihave a VBA code that calls a BAPI via RFC to checkout a document. The Problem is that I get an error like in the subject. Here is my Code
    Private Declare Sub RfcAllowStartProgram Lib "librfc32.dll" (value As Any)
    Sub checkout_file()
    Dim oDocument As Object
    Dim oDocumentFile As Object
    Dim oDocumentFiles As Object
    Dim oReturn As Object
    Dim oBAPICtrl As Object
    'Creating BAPI object
    Set oBAPICtrl = CreateObject("SAP.BAPI.1")
    Set oConnection = oBAPICtrl.Connection
    If oConnection.Logon(0, False) = False Then
    MsgBox "No access to R/3 System"
    Exit Sub 'Programm beenden
    End If
    RfcAllowStartProgram ByVal 0&
    'Creating lokal instance of BO "Draw"
    Set oDocument = oBAPICtrl.GetSAPObject("DRAW", "PM2", "A5N00030059989", "D", "000")
    If Err.Number <> 0 Then
    MsgBox "No local BO 'Draw' created!"
    Exit Sub
    End If
    Set oDocumentFile = oBAPICtrl.DimAs(oDocument, "CheckOutView2", "DocumentFile")
    oDocumentFile("WSAPPLICATION") = "DOC"
    oDocument.CheckOutView2 OriginalPath:="D:\test\", _
    DocumentFile:=oDocumentFile, _
    DOCUMENTFILES:=oDocumentFiles, _
    DocumentStructure:=oDocumentStructure, Return:=oReturn
    MsgBox oDocumentFiles.RowCount
    MsgBox oReturn("MESSAGE")
    Set oConnection = Nothing
    Set oBAPICtrl = Nothing
    End Sub
    I have the newest librfc32.dll in my System32 folder (Version 7110.0.46.6208). Where is the problem? Can it be a problem on the application server or something?
    Thank you,
    Thomander

    Hi Thomander,
    Note 885058 indicates that the problem is resolved with the latest    
    RFC and ICU files. The RFC library is contained in the RFCSDK, please 
    ensure that you are using the latest SDK, it can be downloaded from the
    following location:                                                                               
    Support Packages and Patches                                          
        ==> Additional Components                                         
              ==> SAP NW RFC SDK                                          
                   ==> SAP NW RFC SDK 7.10                                
                        ==>Your OS                                                                               
    ICU libraries can be downloaded from service market place as part of  
    sap kernel. There are contained in the complete package sapexe.car    
    & in a seperate package UCLIB.sar                                     
    -> service.sap.com/patches                                           
    -> Entry by application group                                         
    -> additional component                                              
    -> SAP Kernel [ select the correct versions] & download the file                                                                               
    The naming convention of the library files varies depending on the    
    operating system, they may be called                                  
    "libicuuc.so.26", "libicuuc.sl.26", "libicuuc26.so" or "icuuc26.dll", 
    for example. You must therefore adjust the unpacking statements       
    accordingly.                                                                               
    Unpack the library to the temporary directory & then move it to the   
    kernel directory ("/usr/sap/<SID>/SYS/exe/run").                                                                               
    Caution: Make sure that the libicu* libraries do not overwrite any    
    existing files.                                                                               
    Once you are using the latest RFC and ICU files you should be ok.
    Maybe the information in the following link could also be useful for this kind of error:
    https://www.sdn.sap.com/irj/scn/wiki?path=/display/plm/i001Win32error+2
    Best regards,
    Christoph

Maybe you are looking for