RFC-User in ChangeLog of Processorders

Dear all,
when a process order is changed in R/3 that is already integrated to APO then (after the process order has been sent to APO and back) the userid mentioned in the change log is the RFC-User.
Is there any chance to supress this?
Implementing the user-exit at order creation wouldn't be the best solution in terms of performance I think...
Thanks,
Niko

Hi Niko - I believe the only way to change this is to do so in a user exit by changing the user in the control parameter structure for the CIF queue. EXIT_SAPLCORD_005 of CIFORD03 provides the spot to do so. This change is minimal and if coded correctly will have no impact on performance. The user who triggered the CIF transfer is in the same structure is_ctrlparams so that field can be moved to the user name field. I have never changed the user name before so you may want to look for other tables in the user exit that have the user or changed by fields.
Regards
Andy

Similar Messages

  • Invalid_jobdata when submitting job with rfc user

    Hi,
    I've created a function module in the erp system to remotly trigger a report program by a bw prossess chain.
    When running in the forground it works fine, but the runtime is so long that I want it as a background job.
    So I call job_open, job_submit, job_close in the function module. When I test the function module in the erp system with my dev user it opens a new job, adds a step and release correctly. It also runs fine if I intercept it in the debugger and change sy-uname to aleremote (the standard rfc user).
    It does not work when it's acctually called rfc from the bw system. The job is opened, but job_submit throws invalid_jobdata.
    Could this have anything to do with rfc or the executing user (which is of type SYSTEM)?

    I've caught the execption so there is no dump, but I'm unable to determine why the function module job_submit gives invalid_jobdata only when the executing user is the aleremote user and only when the call originated (the call to my module) from a remote system (the module job_submit is called locally thru my module). Authorization for the user is sap_all, but I was woundering maybe the user type system could be a problem?

  • Password inconsistancy issue with RFC users in ECC 6.0 System after upgrade

    Hi,
    We have upgraded the system from 4.7 to ECC 6.0, but facing the password inconsistancy problem for RFC users. We have set the parameters like "login/min_password_lng" as "8" and "login/password_downwards_compatibility" as "3" & RFC user Type is "system". Could you please suggest how to resolve the password inconsistancy issue.

    Hi Chandan,
    you need to run the txn. SECSTORE and there it will shows you all the RFCs that have inconsistent passwords. Please maintain the correct passwords there.
    In case the existing passwords are no longer acceptable due to new security policies as per the new SAP version, you will have to change the password from SU01.
    Regards,
    Shitij

  • RFC function module always creating BPs with the same user name (RFC user )

    Hi All
    I posted the below question in a different area before. But thought it would be more suitable here.
    Moderators - Please let me know if am doing any mistake.
    Question:
    I have a RFC function module in CRM that creates Business Partners in ECC (XD01 tcode).
    I am using a dialog RFC destination configured in SM59 in CRM.
    But my RFC function module in CRM is always creating the Business Partners in ECC with the RFC user id (the user that we maintain for the RFC destination in SM59).
    This is a problem for the users because they are not able to track the actual person responsible for creating these Business Partners.
    Can somebody please let me know how to solve this problem?
    Thanks
    Raj

    Hi.
    You may use the trust relationship between CRM and R/3 and in SM59 instead of set a specific username, you set the flag "current user".
    With this flag, the system will access R/3 system with the user logged in CRM system. The Trust relationship must be created between CRM and R/3 in order to the system doesn't ask for a password to login in R/3.
    If you need more details please reply.
    Kind regards,
    Susana Messias

  • Authorization Required for RFC user  in R/3-APO system.

    Could you please help regarding one authorization issue. I want to know the authorization required for one RFC user. Now this RFC user used for RFC connection of SAP R/3 - SAP APO system. user type is given dialog type and SAP_ALL profile has been given to this user  id. Now I have to remove SAP_ALL from this user id in R/3 and APO system and  provide the required the authorization in R/3 and APO system.
    Regard
    Auroshikha

    The RFC authorisation depends completely on what the user is doing (ALEREMOTE?).  We can't tell you what RFC auths your connection requires. 
    There is a guide to doing this here: https://wiki.sdn.sap.com/wiki/display/Security/BestPractice-HowtoanalyzeandsecureRFC+connections

  • AUTO PO print out creates spool with RFC user.

    We have classic scenario where AUTO SRM PO print out spool is create with RFC user. While PO data is passing to R/3 is correct with correct user (created_by). Out put is created on the name with RFC user not with user who create SRM SC& PO. BADI BBP_CREATE_PO_BACK will help?

    Hi Vishal,
    Welcome to SDN.
    Do they use custom PO SAPScript/Smartform?
    If they do, you may want to check the print program (custom one) and the custom PO form. Perhaps there is some logic to set/display with the european decimal notation.
    If they don't, you can also check the print program setting and do debugging (if necessary) to find out the logic to assign european decimal notation. 
    Hope this will help.
    Regards,
    Ferry Lianto
    Please reward point if helpful.

  • RFC User Type

    Hi
    Calling gurus.
    When gererating RFC users for the READ and TMW rfc's in Solution Manager users gets generated, and I know the user type is Communication user, however should you be forced to have to create your own users to use within this rfc would it be best to stick to communication user type, or could a system user type be used. 
    It is my understanding that logon via read rfc should not be allowed as it could be a security risk.
    If I am on the wron track please enlighten me or point me towards a conclusive best practice regarding this.
    Thanks in advance.

    Hello again Paul,
    1.-
    At the same 2008 manual "Activating the SAP EarlyWatch Alert on Solution Manager 7.0" yo can see on page 11 this:
    ...A working dialog connection such as *TRUSTED or LOGIN. Once the *BACK destination is created, these can be deleted again...
    This prerequisites are need for the creation ob RFC "_BACK" on remote system, but for remote call of sdccn the prerequisites on Page 15 are not enough !!!
    If you want to call remotely sdccn from solution manager you need a dialog trusted connection.
    I have just tested on our solution manager 5 minutes ago, you are invited to our solution manager if you want to check it.
    2.-
    What about this:
    My question is, Will take into account SAP this users for the "SAP Security user audit" ?
    Regards:
    Luis

  • JCO getDefaultConnection() not using RFC user from XCM

    Hello,
    I am writing a custom backend class to call a custom function module in R3 to get some data. As this has to run before the application start page is loaded, I have used a exit before the /b2b/startapp.do is called.
    The problem here is that when I am using the getDefaultJCoConnection() method in the backend class which extends the IsaBackendBusinessObjectBaseSAP class, the JCO user is determined as the application user rather than the RFC user which I have configured in XCM. Because of this there is an authorization error as the application user does not have auth to the custom function group.
    I have written many other exits in the application and they are all working fine and picking up the RFC user which has relevant authorizations.
    Am I missing something here?
    Pradeep

    Thanks Easwar
    stateless was giving me other issues.
    I managed to solve the problem with the below code.
    ManagedConnectionFactoryConfig mConfig = (ManagedConnectionFactoryConfig)    (getConnectionFactory().getManagedConnectionFactoryConfigs().get("JCO"));
    Properties props = mConfig.getConnectionDefinition("ISA_COMPLETE").getProperties();
    connection = getDefaultJCoConnection(props);
    Pradeep

  • RFC User for satellite systems

    Hello Gurus,
    I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
    Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
    Many thanks in advance for your help
    Miloslav Pudil
    IDS Scheer
    Prague
    Czech Republic

    >
    Miloslav Pudil wrote:
    > I just wanted to ask about one issue. We are a SAP partner and using Solution Manager in VARs scenario. There are many systems of our customers connected to our Solution Manager..
    > Now I want to ask about RFC user(s). As I see, in our Solution Manager there are many users(communications type C) with Synthax SOLMAN<system id> or something like that. It means basically, that we have for every particular customerS system one SOLMAN user for RFC(cust_scout) in our Solution Manager. My question is if we can replace all of these users with only one RFC user for all the systems and customers?
    Hi Miloslav,
    Technically, it will work that you define one common RFC user in your SolMan for communication (RFC BACK destination) from all connected managed systems.
    BUT, I would never recommend it.
    Once a managed system cause issues in your SolMan, you are not able (or at least it's much more difficult) to identify the managed system. Same happens, if a invalid password in the BACK destination leads to a locked user.
    My recommendation: Spend the extra effort in creating a user per managed system. Operation will be much easier later.
    See also this guide:
    [Activating EarlyWatch Alert [EWA] in End Customeru2019s System |http://service.sap.com/~form/sapnet?_SHORTKEY=00200797470000089947&_OBJECT=011000358700000567342009E]
    Best regards,
    Ruediger

  • 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

  • RFC User for Connectivity with ABAP Server Proxy Required?

    Hi people,
    I am just wondering how I set-up my connectivity between XI and my business system B.
    Our basis already set-up the connection to the runtime workbench from B->XI
    For that sake they've added the xirwbuser to B (Xi has it as well, of course).
    Now I am configuring the whole thing in the Directory. There I need an receiver agreement and a channel. For that I take the adapter type "XI". Anyway, I need to give here an RFC destination as well. I've added one of type "H".
    And now the issue: Do I really need a separate user for that rfc connection? I thought with proxies the systems are somewhat like "hard-wired" and do not need special users.
    Anyway, if I need a dedicated RFC user: Is a certain role enough or do I need special roles depending on the stuff I am doing in the business system?
    Thanks in advance!
    Helge

    You can of course use an existing service user.
    But for monitoring purpose it is receommended to use a seperate user. (Think about system log entries).
    The user needs the role SAP_XI_APPL_SERV_USER.
    Regards
    Stefan

  • RFC user logon failed R3077

    Hello
    RFC user logon failed.
    Can anybody help me out for R3077
    Its occuring regularly
    Thanks And Regards
    Akash Gupta

    Hello akash,
    Possible reasons :-
    1> user must be of type "System" in logon data.
    2> must be unicode "in RFC"
    Rest you could follow this link :-
    /thread/250014 [original link is broken]
    Please do write to me at [email protected] in case of more queries.
    Thank you.
    Regards,
    Manomeet
    Award points if helpful **

  • Standard roles, groups, profiles of a rfc-user

    hi,
    can anybody tell me please, which are the standard roles, groups and profiles of a rfc-user in our sap xi-system?
    thanks.
    regards
    Stefan

    Hi,
    Check the links for authorizations.
    http://www.erpgenie.com/sap/netweaver/xi/xiauthorizations.htm
    also check if your user have this roles in abap stack TECODE su01
    SAP_XI_ADMINISTRATOR
    SAP_XI_CONFIGURATOR
    SAP_XI_CONTENT_ORGANIZER
    SAP_XI_DEVELOPER
    SAP_XI_DISPLAY_USER
    SAP_XI_MONITOR
    SAP_ALM_ADMINISTRATOR
    SAP_J2EE_ADMIN
    SAP_SLD_ADMINISTRATOR
    SAP_SLD_CONFIGURATOR
    SAP_SLD_DEVELOPER
    SAP_XI_ADMINISTRATOR_ABAP
    SAP_XI_ADMINISTRATOR_J2EE
    SAP_XI_CONFIGURATOR_ABAP
    SAP_XI_CONFIGURATOR_J2EE
    SAP_XI_ID_SERV_USER
    SAP_XI_IR_SERV_USER
    SAP_XI_RWB_SERV_USER
    SAP_ALM_CUSTOMIZER
    SAP_BC_BASIS_ADMIN
    SAP_BC_BASIS_MONITORING
    ARG_XI_DEV
    Thanks,
    Vijaya.
    Edited

  • 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

  • RFC user in CPS

    HI All,
    Iam geteting the following error whentrying to start the one of the process server in CPS
    Service "SAPR3Service" on process server "lzuce0dx_SE1_63_ProcessServer" stopped unexpectedly.
    Details:
    Exception: 126: BAPI exception while calling BAPI_XMI_LOGON: E XM 026 You have no authorization to log on to interface XBP [XBP, , , ]
    My Question is:
    I have entered my SAP login ID in the XBP tab of the SAP systems under "Environment" , does this ID does not have the previlage to enter the XBP ?
    Or the RFC user does not have the authorisation to enter the XBP ?
    Please advise.
    Regards
    Kiran

    Hi,
    If I read your description correctly, you have entered your SAP login credentials on the XBP tab.
    That means, that your credentials are used for the RFC connection.
    So your user does not have sufficient privileges to connect (via RFC) to the XBP interface.
    In the documentation there is a list of privileges/profiles required for the CPS RFC user.
    Please verify if your user has these privileges, or even better: create a separate RFC user for CPS.
    Regards,
    Anton.

Maybe you are looking for