...
In order to run various NLINK SAP CoNNectors® and Wizards, the NLINK user id will need authorizations in SAP for certain function modules, transaction codes and/or data dictionary objects. The extent of required authorizations decreases as the project progresses from development through testing to production. The following sections describe how NLINK uses the various SAP objects.
The NLINK user should ultimately be a background (communications) user. It will require the same authorizations that a regular user would need to perform the various functional tasks that the interfaces are replicating, e.g., create purchase orders. We cannot recommend any particulars in this area, as authorization schemes vary wildly across SAP systems. This article covers the additional technical authorizations specific to configuring and running an NLINK Server.
Generally, a separate (temporary) dialog user will be needed during development and testing. Whoever is configuring the NLINK Server will use this user to access the SAP system via the SAPGUI. This temporary user id will need full access to the relevant functional areas, and also much access to ABAP Workbench areas such as SE37 (display and test), SE11 (display), SE16 (display), etc. If you want to keep the authorizations for the background user to a minimum, the NLINK meta-database can be configured to use the dialog user during development (in order to run the Wizards, etc.), and switched to the background user for testing.
| Note |
|---|
|
| An SAP service user is not appropriate. |
...
In order to run various NLINK SAP CoNNectors® and Wizards, the NLINK user id will need authorizations in SAP for certain function modules, transaction codes and/or data dictionary objects. The extent of required authorizations decreases as the project progresses from development through testing to production. The following sections describe how NLINK uses the various SAP objects.
The NLINK user should ultimately be a background (communications) user. It will require the same authorizations that a regular user would need to perform the various functional tasks that the interfaces are replicating, e.g., create purchase orders. We cannot recommend any particulars in this area, as authorization schemes vary wildly across SAP systems. This article covers the additional technical authorizations specific to configuring and running an NLINK Server.
Generally, a separate (temporary) dialog user will be needed during development and testing. Whoever is configuring the NLINK Server will use this user to access the SAP system via the SAPGUI. This temporary user id will need full access to the relevant functional areas, and also much access to ABAP Workbench areas such as SE37 (display and test), SE11 (display), SE16 (display), etc. If you want to keep the authorizations for the background user to a minimum, the NLINK meta-database can be configured to use the dialog user during development (in order to run the Wizards, etc.), and switched to the background user for testing.