| # Business cases Sales order entry via EDI From an external source, the customer's environment receives sales orders from EDI. These sales orders are added to the LN database. As soon as a new sales order is created, a workflow process is triggered to monitor the processing of the sales order. Technical notes: Only the creation of the sales order must be taken into account. For example, if the sales order header is updated or sales order lines are added later no new process is triggered. Note that sales orders from EDI are inserted with their sales order lines, either in the same database transaction or in two subsequent transactions. Sales orders in LN are stored in the Sales Orders (tdsls400) table. Sales orders from EDI can be recognized by means of the Origin (tdsls400.corg) field with the value EDI (tdsls.corg.eop). User-defined attributes to be passed on to the workflow engine include the following: Order Number (tdsls400.orno) Sold-to Business Partner (Customer) ID (tdsls400.ofbp) Order Type (tdsls400.sotp) Inventory on-hand The customer wants to take a more active approach towards inventory control. For that reason, a workflow process must be activated as soon as the inventory on-hand goes below a particular threshold value for an item that is stored in a warehouse. The process that is triggered contains the steps that must be taken to effectively react to the low inventory. Technical notes: In LN, the inventory data per item are stored in the Item Inventory by Warehouse (whwmd215) table. The process must be triggered when the inventory on hand (whwmd215.stoc) drops below a predefined value. User-defined attributes to be passed on to the workflow engine are the following: Warehouse (whwmd215.cwar) Item (whwmd215.item) Inventory on Hand (whwmd215.stoc) Inventory Allocated (whwmd215.allo) Credit limit (Example requiring application customization) When you enter sales quotations or sales orders, a credit limit check is carried out. However, the user wants to check not only whether a credit limit is exceeded, but also wants to initiate a process if a credit limited is being approached, for example, if less than 20 percent of the credit limit remains. The process contains the steps to be taken to handle proactively the credit limit, rather than wait until orders can no longer be entered for a customer. Technical notes: The credit limit check is carried out in the program that maintains sales orders. When you enter or update a sales order, the tdsls4102 script contains logic to check the credit limit. A customization is created for this script, which checks whether 80 percent of the credit limit is exceeded. If so, an event that contains the required data is created and a trigger is invoked. User-defined attributes to be passed on to the workflow engine are, for example: Customer ID Order Number Credit Limit Credit in Use |