JDEdwardsE1 - SendOrderToBackoffice
This document describes the process of sending an order from App4Sales to the JDEdwardsE1 ERP system. The process involves several steps, including authentication, order creation, and response handling. The connector communicates with the JDEdwardsE1 system through a REST API.
Data Source Configuration
The connector sends order data to a JDEdwardsE1 REST API. The base URL is configured in the administration settings. The following API routes are used:
tokenrequest: For authentication and obtaining a token.appstack: For creating and managing the order session in JDEdwardsE1.
Order Header Logic
The order header is constructed with the following logic:
A check is performed to see if the customer is allowed to order. This is done by checking if the customer's classification is set to "NotAllowedToOrder". If so, the process is aborted.
The connector authenticates with JDEdwardsE1 using the credentials from the settings and obtains a token.
A session is opened in JDEdwardsE1 for the order creation form (P4210_W4210E).
The `YourReference` field is truncated to a maximum of 25 characters.
App4Sales Field | Source Field (API/Excel/DB) | Logic/Notes |
Business Unit |
| The business unit for the order. |
Customer Code |
| The customer's code. |
Your Reference |
| The customer's reference for the order. Truncated to 25 characters. |
Line & Pricing Logic
Order lines are mapped directly from the App4Sales order to the JDEdwardsE1 request. There is no specific pricing logic in the connector; pricing is handled by JDEdwardsE1.
App4Sales Field | Source Field (API/Excel/DB) | Logic/Notes |
Item Code |
| The code of the item being ordered. |
Quantity |
| The quantity of the item. Defaults to 1 if not specified. |
Responses & Error Handling
The connector handles responses from the JDEdwardsE1 API as follows:
If the API returns errors, the process is aborted, and the error messages are logged and returned to the user.
If the API returns warnings, the connector proceeds to accept the order by sending a confirmation action.
Upon successful order creation, the ERP order number is retrieved from the response and stored in the App4Sales database.
After the order is processed, the application session in JDEdwardsE1 is closed.
Related Settings & Prerequisites
The following settings are used in the Send Order process:
BusinessUnit: The business unit for creating the order.UserRole: The user role for authentication.TokenDuration: The duration in minutes for which the authentication token is valid.ApplicationId: The application ID for the JDEdwardsE1 form.EnableAcceptanceOrder: A boolean setting to enable an additional acceptance step. This is currently not implemented.