11/21/2023 0 Comments Master atc communications![]() ![]() Such a generic user should have the user role SAP_SATC_XMTP_APPLICANT. But this solution does create ‘open’ RFC destinations in your systems. Despite the generic logon user, you can still identify the user who requested an exemption. This solution also allows developers to request exemptions at the master system without having to logon at the master system. Define the users in the client that you specified in the RFC destination to the ATC master system.Īlternative RFC strategies are as follows:ĭefine logon users with limited authorizations for the RFC destinations between the ATC master system and the development systems. The user IDs must be the same in both the development system and the master system. In the destination to the master system, use the client in which your quality managers are active.ĭefine users (optionally with limited authorizations) for developers in the ATC master system. In your RFC destinations, use the client in the development systems in which your developers are active. Follow this link for help with defining trusted RFC connections. Set up a trusted relationship between the master ATC system and each of the satellite development systems of the master system. ![]() But, with correctly defined users in the master system, this solution also offers high security against unauthorized logons or activity in the master system. With this solution, developers can request exemptions from the master system without going through the logon dialog. SAP recommends using pairs of trusted RFC destinations for the connections between satellite development systems and their master ATC system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |