Setup: Security
Aptean EDI
•
Article
•
4/29/2023
•
2 min
If EDI activities will be manually processed by users, they must have permission to access the appropriate objects. Please note that these permissions must extend to users who may not work directly with EDI, but do process documents that are designated as being part of an EDI process. For example, if a sales order was created via EDI, the user tasked with posting this document will need a basic “Read” level of EDI permissions.
The following Aptean EDI permission sets have been developed and may be assigned to users:
Permission | Code | Description | Includes |
---|---|---|---|
EDI Read | BC EDI, READ | Allows the user to post documents (such as sales orders or warehouse shipments) that are included as part of an EDI process. Read permissions do not allow any manual EDI processing or setup on the part of the user. | |
EDI Process | BC EDI, PROCESS | Allows the user to manually process EDI messages and documents. This activity could be performed by manually processing an EDI transaction from a source document in Business Central, or by manually instructing the Job Queue to process any pending activities. Process permissions do not allow any setup on the part of the user. | Includes all permissions defined within the EDI Read permissions set. |
EDI Setup | BC EDI, SETUP | Allows the user to make entries in the setup tables that are required to properly configure the Aptean EDI solution. | Includes all permissions defined within the EDI Read and EDI Process permissions sets. |
These permission sets are included as part of Aptean EDI RapidStart Package.