K-Rise Web Order Creation
In the order creation process, the order is first recorded in the K-Rise database. This is done by EASYProcess process PRC-10000132 (CreateWebSalesOrder). This process is the step in order creation is where K-Rise tables can be referenced or written to when recording usage patterns.
How The EASYProcess Process Works
Input: This process should have all information regarding the items, promotions, and user passed into it as input.
Outside Resources Used: If necessary, this process can reference EASYCommerce tables such as the item master, but only if the information needed is not passed in as input. This process will not query the database to gather information about the particular user or their item source (list, jde order template, quote, or cart).
Output: This process outputs a success flag, message, exception (if exists) and the WebOrderNumber (internal K-Rise order id).
Database Tables Accessed
All information about the order is saved into designated order tables.
- Related to Drop Ship/Bill addresses:
- EC_Order_Addresses (for Drop Ship and Drop Bill)
- EC_Order_Detail_Segments (Used in configured items)
- EC_Order_Detail_Components (Used in kit items)
- Related to Promotions Feature (used with carts)
This process is the place during order creation where any EASYCommerce system tables are reference, such as usage patterns. The following tables are updated with usage information:
- EC_Item_Usage (item ordering frequency)
- EC_Promotion_Coupon_Usage (promotion feature)
Order Creation Failures
This process is responsible for writing to K-Rise tables, however if they fail, depending on the importance of the table record, it may or may not be considered an order failure. The behavior when it comes to each database table can be altered to add additional error handling, but the the default behavior is shown below.
Failure in Insert Considered Web Order Failure
No - but an email is sent to Admin (Subject: Possible Drop Ship/Bill Failure for Order)
If Web Order creation fails, order creation stops and it will never reach ERP Order Creation. The information needed for the order cannot be saved and in order to resubmit the order, action on the user’s side is necessary. For this reason, the user is informed of the order creation failure. The EASYCommerce site admin is also informed via an email (Subject: Internal Order # has failed).
Call to ERP Order Creation Process
The initiation of the ERP order creation can be done in two ways: Workflow or direct call to the process responsible for ERP order creation. The decision is made by a configuration variable:
Direct Process Call
If the configuration variable is set to “False”, the ERP Order Creation process will be called directly. This will immediately begin the next step of the order creation process flow.
If the configuration variable is set to “True”, a request is made for the EASYProcess Workflow WFLOW-10000102 (EASYCommerce Order Creation Workflow) and the workflow is executed with that request.
Depending on the workflow approvers set up in EASYProcess, the order can be sent to approvers for approval who can either approve or deny the order request. This workflow structure is used so that if approvers are needed, a workflow can handle the approval system customizations.
After the order is approved, it calls the process to create the ERP Order Creation process.