├── screen ├── ubpl │ ├── Accountant Records Invoice From Vendor.cwiki │ ├── Sales Representative Seeks Prospects and Opportunities.cwiki │ ├── OAGIS Procure to Pay.cwiki │ ├── Product Marketer Maintains Product Information.cwiki │ ├── Bank Reconciliation.cwiki │ ├── Sales Representative Leads Prospects from RFQ to Sales Order.cwiki │ ├── Accountant Pays Invoices.cwiki │ ├── Accountant Receives Invoice and Sends Payment.cwiki │ ├── Accountant Sends Invoice and Receives Payment.cwiki │ ├── Shipment Receiver Receives Shipment with Packing Slip but No PO.cwiki │ ├── Customer Cancels Order.cwiki │ ├── Company Approves Sales Order.cwiki │ ├── Inventory Mover Checks Physical Inventory.cwiki │ ├── Marketer Maintains General Site Content.cwiki │ ├── Placing Customer Adds Product to Cart.cwiki │ ├── Inventory Mover does Stock Move.cwiki │ ├── Customer Creates and Edits Account (Profile).cwiki │ ├── Customer Reviews Order History and Status.cwiki │ ├── Story of Online Retail Company.cwiki │ ├── Inventory Mover Puts Away Inventory.cwiki │ ├── Buyer Places Purchase Order.cwiki │ ├── Carrier Does Not Deliver Shipment to Customer.cwiki │ ├── Carrier Returns Undeliverable Shipment to Company.cwiki │ ├── Placing Customer Places a Sales Order (Through CSR).cwiki │ ├── Placing Customer Places a Sales Order (Through EBay).cwiki │ ├── OAGIS Work Plan to Cash.cwiki │ ├── Shipment Receiver Receives Shipment.cwiki │ ├── Customer Returns Product.cwiki │ ├── Company Fulfills Sales Order.cwiki │ ├── Customer Finds Product.cwiki │ ├── Actor Definitions.cwiki │ ├── Placing Customer Places a Sales Order (Online Checkout).cwiki │ ├── UBPL Index.cwiki │ ├── UBPL Introduction.cwiki │ ├── Resources with Information about General Business Processes.cwiki │ ├── Company Processes Return Received.cwiki │ └── OAGIS Order to Cash.cwiki └── ubpl.xml ├── README.md ├── data └── UbplSetupData.xml ├── AUTHORS └── LICENSE.md /screen/ubpl/Accountant Records Invoice From Vendor.cwiki: -------------------------------------------------------------------------------- 1 | Accountant records invoice (bill) received from vendor. Using invoice due date, accountant schedules invoice for payment. 2 | -------------------------------------------------------------------------------- /screen/ubpl/Sales Representative Seeks Prospects and Opportunities.cwiki: -------------------------------------------------------------------------------- 1 | h1. Sales Representative Seeks Prospects and Opportunities 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * Contacts 6 | * Find and Contact Leads 7 | * Qualify Prospects 8 | * Track Opportunities 9 | 10 | h4. Story 11 | 12 | -------------------------------------------------------------------------------- /screen/ubpl/OAGIS Procure to Pay.cwiki: -------------------------------------------------------------------------------- 1 | {toc} 2 | 3 | h2. Introduction 4 | 5 | This process covers purchasing/sourcing and manufacturing. 6 | 7 | h2. OAGIS Scenarios 8 | 9 | h3. Incorporated Scenarios 10 | 11 | * TODO 12 | 13 | h3. Related Scenarios 14 | 15 | * TODO 16 | 17 | h2. Actors 18 | 19 | 20 | h2. Process Story 21 | 22 | h2. OAGIS Documents Used 23 | 24 | -------------------------------------------------------------------------------- /screen/ubpl/Product Marketer Maintains Product Information.cwiki: -------------------------------------------------------------------------------- 1 | h1. Product Marketer Maintains Product Information 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * new products 6 | * pricing 7 | * content (photographer, copy writer, copy translators) 8 | * categorization 9 | * promotions 10 | * virtual/variant products (virtual first, variants first) 11 | 12 | h4. Story 13 | 14 | -------------------------------------------------------------------------------- /screen/ubpl/Bank Reconciliation.cwiki: -------------------------------------------------------------------------------- 1 | Accountant uses Bank Statement and verifies that the entries and amounts on the bank statement are consistent or compatible with the amounts in the financial account (of type bank account) transactions in accounting system. 2 | When verified accountant completes GL postings to bank assets accounts and in-transit bank account. 3 | 4 | Reconciliation process is also applicable for credit card financial accounts. 5 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Mantle Universal Business Process Library 2 | 3 | A library of business process story and related documents. These are generic requirements for enterprise systems. 4 | 5 | While you can view the documents directly they are all wiki files so the easiest way to view them is by adding this 6 | component to a Moqui Framework installation. 7 | 8 | To add this component to Moqui the easiest approach is to use the Gradle get component task: 9 | 10 | $ ./gradlew getComponent -Pcomponent=mantle-ubpl 11 | -------------------------------------------------------------------------------- /screen/ubpl/Sales Representative Leads Prospects from RFQ to Sales Order.cwiki: -------------------------------------------------------------------------------- 1 | h1. Sales Representative Leads Prospects from RFQ to Sales Order 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * Sales Representative Communicates Product Information 6 | * Prospect sends Request For Quote (RFQ) to Sales Representative 7 | * Sales Representative Prepares Quote and Delivers to Prospect 8 | * Placing Customer Creates Sales Order from Quote 9 | * Sales Representative Receives Sales Order 10 | 11 | h4. Story 12 | 13 | TODO 14 | -------------------------------------------------------------------------------- /screen/ubpl/Accountant Pays Invoices.cwiki: -------------------------------------------------------------------------------- 1 | h1. Accountant Pays Invoices 2 | 3 | Accountant finds all invoices ready for Payment. In preparation of Invoice batch, accountant groups invoices by payTo party, allocates set of check numbers for set of checks. Accountant writes check to each vendor. Records payment in payment log. Accountant also documents payment identifier (from payment log) in deposit withdrawal log of bank account. 4 | 5 | Payment identifier (from payment log) and amount is also documented with invoice and invoice is marked as paid if invoice is fully paid. 6 | -------------------------------------------------------------------------------- /screen/ubpl/Accountant Receives Invoice and Sends Payment.cwiki: -------------------------------------------------------------------------------- 1 | h1. Accountant Receives Invoice and Sends Payment 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * None! 6 | 7 | h4. Dependencies 8 | 9 | * [Shipment Receiver Receives Shipment] 10 | 11 | h4. Story 12 | 13 | Supplier sends invoice or other payment request to Accountant. If payment term is "pay on deliver" Accountant 14 | sends the payment immediately. If payment term is "credit" Accountant sends payment within the payment 15 | period agreed to. 16 | 17 | If Accountant receives an invoice that does not match the PO, Accountant notifies Buyer who contacts Supplier to resolve the issue. 18 | -------------------------------------------------------------------------------- /screen/ubpl/Accountant Sends Invoice and Receives Payment.cwiki: -------------------------------------------------------------------------------- 1 | h1. Accountant Sends Invoice and Receives Payment 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Dependencies 6 | 7 | h4. Story 8 | 9 | *(CC Payment)* When shipment is marked as Packed: for all orders associated with the shipment that were paid by credit card and the payments have not been captured, Accounting captures payment (automated). 10 | 11 | *(Billing)* When shipment is marked as Packed: Accountant creates an invoice and sends it to Bill-To Customer for the relevant order(s). When payment is received from Bill-To Customer, Accountant associates it with relevant invoice(s) and marks invoices with full payment as paid. 12 | -------------------------------------------------------------------------------- /screen/ubpl/Shipment Receiver Receives Shipment with Packing Slip but No PO.cwiki: -------------------------------------------------------------------------------- 1 | Shipment Receiver receives shipment. It has invoice tucked into it. Receiver records vendor name, vendor contact, amount due, invoice due date and terms. Receiver records all items received, quantity of each item, and unit price. Receiver also records tax and shipping charges as in invoice. 2 | 3 | Information is recorded on AP invoice. Inventory QOH is increased. Inventory account is debited. Accounts Payable account is increased by amount of the bill. 4 | 5 | If no invoice but only packing slip is received, receiver does not record money part of transaction. Later when Invoice is received from vendor accountant updates AP invoice.]]> 6 | -------------------------------------------------------------------------------- /screen/ubpl/Customer Cancels Order.cwiki: -------------------------------------------------------------------------------- 1 | h1. Customer Cancels Order 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Story 6 | 7 | Customer sends email to request cancellation of an order. CSR reviews email, finds the order, and if it has not shipped (shipment packed) then records the order as cancelled. If payment has been received for the order Company automatically refunds the payment. If the order has shipped CSR replies to customer by email to notify that the item has been shipped and they are liable to pay. 8 | 9 | Customer reviews order online and if any of it has not been shipped a cancel button will be available for the entire order and each item that has not shipped. Customer cancels entire order or individual item. Company automatically changes status, cancels inventory reservation(s), and if payment has been received then refunds payment. 10 | -------------------------------------------------------------------------------- /screen/ubpl/Company Approves Sales Order.cwiki: -------------------------------------------------------------------------------- 1 | h1. Company Approves Sales Order 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * Special case statuses and manual approval 6 | 7 | h4. Story 8 | 9 | Sales Orders are approved automatically when paid by credit card and CC authorization is successful. 10 | 11 | Sales Orders are placed in Pending status approval after checkout then auto-approve once third-party payment processor (PayPal, GoogleCheckout, etc) sends notification. 12 | 13 | Sales Orders are placed in Rejected status when authorization fails. 14 | 15 | Once order is approved Company reserves inventory for approved order, reducing Available To Promise (ATP) quantity. If inventory is not available negative inventory reservations are created and the order is placed on back-order. 16 | 17 | Company sends confirmation email to the Placing Customer. 18 | -------------------------------------------------------------------------------- /screen/ubpl/Inventory Mover Checks Physical Inventory.cwiki: -------------------------------------------------------------------------------- 1 | h1. Inventory Mover Checks Physical Inventory 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Dependencies 6 | 7 | h4. Story 8 | 9 | Inventory Mover receives a list of stock locations scheduled to be checked, sorted by least-recently-checked location first, and then by facility location code. Locations with an outstanding pick or stock move will be removed from the list. System will track outstanding stock checks by location and not issue picks or stock moves for those locations until the stock check is recorded. Outstanding picks, moves, and stock checks have a timeout, and are cleared at the end of the day. Inventory Mover records the actual quantity at each location, causing a record of variance to be created if the currently recorded quantity for that location is different than the actual quantity recorded by Inventory Mover. 10 | -------------------------------------------------------------------------------- /screen/ubpl/Marketer Maintains General Site Content.cwiki: -------------------------------------------------------------------------------- 1 | h1. Marketer Maintains General Site Content 2 | 3 | h4. Story 4 | 5 | Marketer writes copy and creates or gathers images to be included in the public facing web site. Marketer reviews list of existing content on the site (associated with named placeholders or content managed pages) and finds the content to update with the new text and/or images. Marketer uploads images and edits or pastes text to modify the selected content. 6 | 7 | If there is no existing content on the site and Marketer wants to add content to an existing dynamic page Marketer contacts Developer to add a placeholder. 8 | 9 | If there is no existing content on the site and Marketer wants to create a new content managed page Marketer adds page, selecting the desired decorator screen so that common parts look the same as other pages. Marketer adds content to the page as desired. 10 | -------------------------------------------------------------------------------- /screen/ubpl/Placing Customer Adds Product to Cart.cwiki: -------------------------------------------------------------------------------- 1 | h1. Placing Customer Adds Product to Cart 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * Add Variant to Cart 6 | * Add Configurable Product to Cart 7 | * Input Addition Information about Purchase (survey; product personalization, etc) 8 | 9 | h4. Story 10 | 11 | *Simple Add to Cart* Once a product is selected Customer adds it to the list to be ordered (which may be a shopping cart to order now, or shopping list to order later), specifying the quantity of the product desired. 12 | 13 | If the product Customer wants to order has configuration options, variants (variations) to select, or additional information to gather Customer will specify that information as they add it to the list. 14 | 15 | As product is added or removed from a list to be ordered (that is a cart list) Company will calculate promotions and other adjustments based on the combination of items on the list. 16 | -------------------------------------------------------------------------------- /screen/ubpl.xml: -------------------------------------------------------------------------------- 1 | 2 | 15 | 18 | 19 | 20 | 21 | 22 | 23 | -------------------------------------------------------------------------------- /screen/ubpl/Inventory Mover does Stock Move.cwiki: -------------------------------------------------------------------------------- 1 | h1. Inventory Mover does Stock Move 2 | 3 | Trigger: 4 | Trigger: Based on touch frequency or other report showing a non-optimical location, move inventory to match frequency or other criteria (Optimize Locations) 5 | 6 | h4. Ideas to Incorporate 7 | 8 | * None! 9 | 10 | h4. Dependencies 11 | 12 | h4. Story 13 | 14 | *(Bulk-to-Pick)* Inventory Mover gets a list of inventory items by Product ID and facility location (generated according pick location where quantity drops below configured threshold). Inventory Mover moves inventory from bulk location to pick location according to list. Inventory Mover records actions to represent actual inventory moves (not listed ones). If Inventory Mover finds that inventory in the bulk location is short of system record during a stock move, Inventory Mover records moves of available quantity and records a physical inventory adjustment with difference between requested move amount and actual move amount. 15 | 16 | *(Optimize Locations)* TODO 17 | -------------------------------------------------------------------------------- /screen/ubpl/Customer Creates and Edits Account (Profile).cwiki: -------------------------------------------------------------------------------- 1 | h1. Customer Creates and Edits Account (Profile) 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Story 6 | 7 | Customer decides they need or want an account. Customer sends personal, contact, and other relevant information to Company who records it for future use. Customer also submits desired User Login ID and password. If User Login ID is already in use by another user, Company notifies Customer and Customer submits an alternate ID until an available one is found. Company notifies Customer that account is created. 8 | 9 | Customer reviews their account information on record with Company. Information on record may include: Personal Information, Loyalty Points, Contact Information, Payment Method Information, Tax Identification and Exemption, Username & Password, Default Shipment Method, File Manager, Contact Lists, Surveys, and Messages. 10 | 11 | Customer may create, update, or delete various parts of this information (TODO: add detailed options and processes for each). 12 | -------------------------------------------------------------------------------- /screen/ubpl/Customer Reviews Order History and Status.cwiki: -------------------------------------------------------------------------------- 1 | h1. Customer Reviews Order History and Status 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Story 6 | 7 | Customer reviews order history list with Order ID, Date, Total Amount, Status, and related Invoices for each. Customer requests information for a single order and reviews order detail including: status history, shipping and billing details, order item details, and order totals including tax, shipping, grant total. Customer requests printable copy of order, and Company generates a PDF file and sends it to Customer. 8 | 9 | Customer may add all or any order items (with ordered quantities) to the cart for repurchase, or add to a recurring order (type of shopping list) to receive the products periodically as specified by Customer. 10 | 11 | If Order is not completed (items not yet packed for shipping) Customer may request cancellation of part or all of the order. See [Customer Cancels Order] for process once Customer has initiated this. 12 | 13 | Customer reviews digital downloads available based on orders approved or complete, including Order ID, Product Name, Digital Content Name, Content Description, and option to download the content. Customer requests content download and receives purchased content file. 14 | -------------------------------------------------------------------------------- /screen/ubpl/Story of Online Retail Company.cwiki: -------------------------------------------------------------------------------- 1 | h1. Story of Online Retail Company 2 | 3 | Someone decides to sell a product. [Product Marketer Maintains Product Information]. [Buyer Places Purchase Order]. [Marketer Maintains General Site Content]. 4 | 5 | When new inventory is needed [Buyer Places Purchase Order]. When shipments arrive [Shipment Receiver Receives Shipment], then [Inventory Mover Puts Away Inventory]. 6 | 7 | [Customer Finds Product]. [Placing Customer Adds Product to Cart] and [Placing Customer Places a Sales Order (Online Checkout)]. Alternatively [Placing Customer Places a Sales Order (Through CSR)] or [Placing Customer Places a Sales Order (Through EBay)]. 8 | 9 | If desired during checkout or for other reasons, [Customer Creates and Edits Account (Profile)]. As desired [Customer Reviews Order History and Status]. If Customer decides to, [Customer Cancels Order]. 10 | 11 | Once order is ready [Company Approves Sales Order]. 12 | 13 | When inventory is not sufficient in a pick location [Inventory Mover does Stock Move]. [Company Fulfills Sales Order]. [Accountant Sends Invoice and Receives Payment]. Sometimes special cases come up, like [Carrier Does Not Deliver Shipment to Customer] and [Carrier Returns Undeliverable Shipment to Company]. 14 | 15 | [Customer Returns Product]. [Company Processes Return Received]. 16 | -------------------------------------------------------------------------------- /screen/ubpl/Inventory Mover Puts Away Inventory.cwiki: -------------------------------------------------------------------------------- 1 | h1. Inventory Mover Puts Away Inventory 2 | 3 | h4. Ideas to Incorporate 4 | 5 | * None! 6 | 7 | h4. Dependencies 8 | 9 | * [Shipment Receiver Receives Shipment] 10 | 11 | h4. Story 12 | 13 | Inventory Mover receives the product from Shipment Receiver. 14 | 15 | Inventory Mover prints and applies label containing Product ID (bar code and text). Inventory Mover optionally prints and applies label with Inventory Item ID, noting that if items are split system will have different Inventory Item IDs for some items later on. 16 | 17 | Inventory Mover then determines location for items. If the product does not have a primary location, the Inventory Mover finds an appropriate empty location to use and assigns that as the primary location for the product. Inventory Mover fills the primary location and puts any excess product in a bulk location. 18 | 19 | Inventory Mover assigns location where items were placed to the inventory item previously received. If items were placed in multiple locations Inventory Mover does quick stock moves to record where inventory was actually placed, and checks to make sure the quantity that remains in the original location is the quantity actually placed there. If inventory is received into both bulk and pick/primary locations then original location should be the bulk location and the stock move should be done to the pick/primary location. 20 | -------------------------------------------------------------------------------- /data/UbplSetupData.xml: -------------------------------------------------------------------------------- 1 | 2 | 15 | 16 | 17 | 20 | 21 | 22 | 23 | 25 | 27 | 28 | -------------------------------------------------------------------------------- /screen/ubpl/Buyer Places Purchase Order.cwiki: -------------------------------------------------------------------------------- 1 | h1. Buyer Places Purchase Order 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * None! 6 | 7 | h4. Dependencies 8 | 9 | * [Product Marketer Maintains Product Information] 10 | 11 | h4. Story 12 | 13 | If this is the first time a product has been ordered from a supplier: Buyer makes arrangement with Manufacturer or Distributor (acting as Supplier) to supply the product. Buyer agrees with Supplier on payment terms (pay in advance, pay on delivery (COD), or credit (billing account) with net payment period). Buyer records initial supplier information for product with at least minimum and increment quantities and latest supplier cost (for a given quantity). Buyer may also record more detailed agreement information. 14 | 15 | Buyer creates Purchase Order for a single Supplier based on existing re-order Requirements or on manual/external planning. Buyer specifies ship before date (aka "cancel if not shipped by" date) and "cancel all back orders after" date. Buyer may specify a PO#, otherwise it is generated automatically. Buyer approves purchase order. When recording PO, Company automatically sets price as "last price" on Supplier-Product record. 16 | 17 | Buyer places an order with the given Supplier by sending Supplier order as a printed document, email, OAGIS or UBL XML message, or by phone. Supplier tells Buyer one or more estimated ship dates and Buyer records those dates. 18 | 19 | If the payment term is pay in advance Buyer notifies Accountant who immediately sends payment to Supplier. 20 | -------------------------------------------------------------------------------- /screen/ubpl/Carrier Does Not Deliver Shipment to Customer.cwiki: -------------------------------------------------------------------------------- 1 | h1. Carrier Does Not Deliver Shipment to Customer 2 | 3 | h4. Dependencies 4 | 5 | * [Company Fulfills Sales Order] 6 | 7 | h4. Story 8 | 9 | Customer contacts CSR to request information about a item that has not arrived. CSR reviews information from Customer and finds the order. If item has not been shipped CSR notifies Customer that it has not shipped and what the ETA is. If Customer does not want to wait Customer requests that the order be canceled. CSR reviews cancellation request and cancels the order. If payment has been received on the order Company refunds payment. 10 | 11 | If the item has been shipped CSR notifies Customer and asks them to check at the post office for the package. If Customer contacts CSR again saying package has not arrived and is not at the post office and it has been more than a reasonable number of days (decided by the CSR based on feedback from Customer) then package is considered lost. CSR contacts Customer to check the address and if it is not correct updates it. If the package is insured, CSR places a new zero amount order for a replacement item. If the package is not insured CSR contacts Customer to see if it is okay to send another item and charge them shipping. If Customer agrees CSR places replacement order with the price of the item(s) discounted but with full shipping cost. If Customer does not agree to shipping CSR negotiates with Customer, and may send out replacement totally free of charge. CSR may also upgrade the shipping method on the replacement order for customer satisfaction reasons. 12 | -------------------------------------------------------------------------------- /screen/ubpl/Carrier Returns Undeliverable Shipment to Company.cwiki: -------------------------------------------------------------------------------- 1 | h1. Carrier Returns Undeliverable Shipment to Company 2 | 3 | h4. Dependencies 4 | 5 | [Company Fulfills Sales Order] 6 | 7 | h4. Story 8 | 9 | Carrier Returns Undeliverable Shipment to Company. Shipment Receiver sets the package aside and notifies CSR. CSR contacts Customer to check and correct address and see if Customer still wants the item(s). CSR creates a new label (through any Carrier, preferably the original carrier), places a new label on the package(s), records the new tracking number (edit the same shipment), and ships them out again. CSR may choose to charge Customer for shipping after clearing it with Customer (create order for shipping only). 10 | 11 | If Customer does not want the item(s) CSR creates a return and sets the response type on the return to either store credit, refund, or replacement (may be partial payment, etc; CSR sets other return fields) and sets return status to approved and complete (original package received). 12 | 13 | Carrier sends notice that they could not deliver package or Customer refuses to pay the customs and specifies approximate number of days to resolve the issue. CSR contacts Customer to notify them and request they go pick it up. If Customer does not pick up package from Carrier or contact Carrier for delivery within the number of days specified by Carrier, Carrier may destroy the package right away. Carrier may also contact Company (via Carrier Contact) and ask what to do with the package. Carrier Contact will review the value of the item(s) and instruct Carrier to either return the package (and incur a charge) or fax a "please destroy" form so that Carrier can destroy the package. 14 | -------------------------------------------------------------------------------- /screen/ubpl/Placing Customer Places a Sales Order (Through CSR).cwiki: -------------------------------------------------------------------------------- 1 | h1. Placing Customer Places a Sales Order (Through CSR) 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Story 6 | 7 | Customer contacts CSR through phone, fax, or email with a request for an order for specific products and quantities for each, plus where needed other details such as size, color, and so on. Customer specifies shipping and billing details, contact information. If Customer does not specify important details CSR contacts Customer to get additional information. CSR records order information and finalizes order. 8 | 9 | If Customer is a new organization that wants to purchase on credit, CSR creates Party (using new customer) for Customer and Billing Account with a beginning limit determined by Company. Customer sends copy of their internal Purchase Order by fax (possibly scan/email or mail) with certain required information/etc. If Customer does not specify email address CSR enters dummy address that will receive confirmations. CSR enters sales order for PO with the Billing Account instead of payment method, and approves the order. 10 | 11 | If Customer wants to modify the order Customer contacts CSR. Customer may request to add items, remove items, change quantities, change sizes/colors, change address, change shipping method, change billing info, add gift message. If new order grand total is greater than the original (before the requested changes) and the order is paid by credit card, Company automatically cancels original authorization and authorizes the new grand total. If that authorization fails CSR is notified and contacts Customer to resolve. Customer may request other changes to resolve issue and CSR will "re-finalize" the order to do a new authorization. 12 | -------------------------------------------------------------------------------- /screen/ubpl/Placing Customer Places a Sales Order (Through EBay).cwiki: -------------------------------------------------------------------------------- 1 | h1. Placing Customer Places a Sales Order (Through EBay) 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Story 6 | 7 | eBay Marketer selects products to add to eBay Store and automatically sends them to eBay. eBay Marketer allocates inventory to warehouse for eBay auctions. eBay Marketer creates eBay Auctions from listings in the eBay Store. 8 | 9 | Placing Customer places an order through eBay Store, or places the highest bid in an eBay Auction. 10 | 11 | eBay Marketer imports eBay orders (auctions and store orders) to get paid orders by specifying begin/end time, views orders placed in that time, and then selects orders to import. eBay Marketer reviews imported orders and manually approves them, mainly making sure orders match the orders in eBay. If Placing Customer orders multiple items they will come in as separate orders and eBay Marketer will combine the orders into a single order. 12 | 13 | For credit card payment the order is placed on eBay and Placing Customer calls eBay Marketer and gives CC#. eBay Marketer either enters entire order including payment information manually, or finds the order already imported from eBay and adds payment information to the order, and then authorizes the payment. 14 | 15 | If Customer sends money via PayPal and skips ordering on eBay, eBay Marketer manually creates an order. When order is complete eBay Marketer marks as shipped in PayPal. 16 | 17 | Once items are shipped Company automatically sends message to eBay and sends standard ship notification email. 18 | 19 | On returns order is returned as normal, and then eBay Marketer manually marks order as returned in eBay and if application refunds payment in PayPal, and if PayPal was not used manually refunds credit card or other payment. 20 | -------------------------------------------------------------------------------- /screen/ubpl/OAGIS Work Plan to Cash.cwiki: -------------------------------------------------------------------------------- 1 | {toc} 2 | 3 | h2. Introduction 4 | 5 | This process covers project work including billable time and expenses. OAGIS doesn't have many scenarios to cover this literally, so it is a mostly an adaptation of similar manufacturing scenarios. 6 | 7 | h2. OAGIS Scenarios 8 | 9 | * 9 - Project Accounting Synchronization 10 | * 10 - Feeder Applications to Project Accounting 11 | * 11 - Human Resources to Manufacturing 12 | * 20 - Plant Data Collection / Warehouse Management / Time and Attendance 13 | * 32 - Human Resources Integration to Manufacturing 14 | * 33 - Human Resources to Time Data Collection 15 | 16 | h2. Actors 17 | 18 | TODO 19 | 20 | h2. Process Story 21 | 22 | Budget, Accounts Receivable, Order Management, Purchasing, Accounts Payable, Time and Labor, and Travel and Expenses send PostProjectAccounting to Project Accounting then Project Accounting sends back ConfirmBOD. 23 | Project Accounting sends SyncProjectMaster to Budget, Accounts Receivable, Order Management, Purchasing, Accounts Payable, Time and Labor, and/or Travel and Expenses then each sends ConfirmBOD to Project Accounting. 24 | 25 | Human Resources sends SyncPersonnel to Work Planning and Work Planning sends ConfirmBOD to HR. 26 | Human Resources sends SyncEmployeeWorkSchedule to Work Planning and Work Planning sends ConfirmBOD to HR. 27 | Work Planning sends SyncField to HR and HR sends ConfirmBOD to Work Planning. 28 | 29 | Time Collection sends GetPersonnel to Work Planning and Work Planning sends ShowPersonnel to Time Collection. 30 | Time Collection sends UpdateEmployeeWorkTime to Work Planning and Work Planning sends RespondEmployeeWorkTime to Time Collection. 31 | 32 | HR pays worker. HR sends PostJournalEntry to GL and GL sends PostAcknowledgeJournalEntry to HR. 33 | 34 | h2. OAGIS Documents Used 35 | 36 | * PostProjectAccounting - ConfirmBOD 37 | * SyncProjectMaster - ConfirmBOD 38 | 39 | * SyncPersonnel - ConfirmBOD 40 | * SyncEmployeeWorkSchedule - ConfirmBOD 41 | * SyncField - ConfirmBOD 42 | * GetPersonnel - ShowPersonnel 43 | * UpdateEmployeeWorkTime - RespondEmployeeWorkTime 44 | 45 | * PostJournalEntry - PostAcknowledgeJournalEntry 46 | -------------------------------------------------------------------------------- /screen/ubpl/Shipment Receiver Receives Shipment.cwiki: -------------------------------------------------------------------------------- 1 | h1. Shipment Receiver Receives Shipment 2 | 3 | h4. Ideas to incorporate: 4 | 5 | h4. Dependencies 6 | 7 | * [Buyer Places Purchase Order] 8 | 9 | h4. Story 10 | 11 | Supplier ships items ordered via Carrier. 12 | 13 | When Carrier delivers shipment, Shipment Receiver briefly reviews incoming shipment and signs for receipt of the product from Carrier. If the quantity is not the quantity ordered or it is clearly a different product Shipment Receiver will contact Supplier and resolve issue before signing for receipt. If no resolution is come to Shipment Receiver will not sign for receipt and the shipment will be returned to Supplier. 14 | 15 | If shipment received is clearly a return (has RMA# or Return ID), Shipment Receiver gives items to CSR for handling. If shipment received does not correspond to a known PO or Return, Shipment Receiver gives items to Buyer for handling. 16 | 17 | If shipment received is clearly for a purchase order (has PO#) Shipment Received processes incoming inventory. Shipment Receiver finds the PO corresponding to the items received and records PO receipt (inventory) information for it including quantity and cost, but no location yet. If Shipment Receiver records a higher quantity received than was ordered, system automatically adjusts the PO being received against. 18 | 19 | Shipment Receiver reviews incoming items. Shipment Receiver determines the Product ID. Shipment Receiver checks the item to make sure all features match what is currently in the system performs quality checks according to a checklist specific to that product (if one exists). 20 | 21 | If the product is a different color than what is in the system Shipment Receiver creates a new Product ID and records it. 22 | 23 | If product that arrives is not the product on the PO and has already been received (and not just a different color) then Shipment Receiver sends it to Buyer for handling. 24 | 25 | Shipment Receiver sets the inventory aside for Inventory Mover to put away. 26 | 27 | If part of the PO is not yet received Buyer contacts Supplier and resolve any issues (not yet received inventory, wrong inventory, etc). 28 | -------------------------------------------------------------------------------- /screen/ubpl/Customer Returns Product.cwiki: -------------------------------------------------------------------------------- 1 | h1. Customer Returns Product 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Dependencies 6 | 7 | * [Company Fulfills Sales Order] 8 | 9 | h4. Story 10 | 11 | If Ship-To Customer finds the product to be faulty or End-User Customer decides they do not want the product, they will contact Customer Service Representative (CSR) by phone or email and request return authorization, specifying reason for return (and for defective items notes about problem experienced) and desired return response (Refund, Partial Refund, Replacement). If appropriate CSR handles issue directly with Customer in order to avoid the return and if a return has already been entered cancels the return. If item(s) are flagged as not returnable then CSR explains policy to Customer. 12 | 13 | Otherwise CSR authorizes return, specifies if other misc adjustments applied, and records it. CSR optionally emails electronic shipping label from Carrier to Customer. Ship-To Customer or End-User Customer ships the product via Carrier to the warehouse. 14 | 15 | For Wait and Replace responses: Company creates a zero amount order for the replacement items configured on the return. The order is left in the "Held" status so that it is not shipped but inventory is reserved while waiting for the original item to be received by Company. 16 | 17 | For Cross-Ship Replacement responses: Customer specifies a credit card that the replacement order will be charged to, and that will receive the credit when the original item is received by Company. 18 | 19 | If Customer was sent the incorrect item and they do not want it, Customer contacts CSR. CSR creates return for replacement (cross-ship or wait). CSR adjusts inventory to increment QOH for item ordered and decrement QOH for item actually shipped (physical inventory adjustment reason: mis-shipped item). 20 | 21 | (Exchange for a Different Item) If Customer wants to exchange an item (return an item and order another item), Customer contacts CSR. CSR creates return for refund for the original item. CSR creates "exchange order" that links back to the original order and for the same customer, but otherwise is created like any normal sales order. 22 | -------------------------------------------------------------------------------- /screen/ubpl/Company Fulfills Sales Order.cwiki: -------------------------------------------------------------------------------- 1 | h1. Company Fulfills Sales Order 2 | 3 | h4. Ideas to incorporate: 4 | 5 | h4. Dependencies 6 | 7 | * [Company Approves Sales Order] 8 | 9 | h4. Story 10 | 11 | *(Pick)* Once inventory is available (for part or all of the order, depending on preference) Fulfillment Manager creates a picklist and prints it (for up to X orders at a time, depending on batch pick size; only orders where inventory is available for part or all of the order, depending on preference). Picker walks the pick floor and at each location listed on the pick sheet Picker picks the amount specified for the location and places items in the cart bin(s) specified on the pick sheet, and verifies each is the correct location by looking at the pack sheet for the order in that bin. Once all items on the pick sheet are picked Picker records status update for the picklist. 12 | 13 | If Picker notices that there is insufficient quantity in the pick location for a given picklist item Picker will ask a Inventory Mover to find inventory in a bulk location. If Inventory Mover finds needed inventory in a bulk location they will do a quick Stock Move for that inventory from the bulk to the pick location. If Inventory Mover does not find bulk inventory Picker puts anything picked back in the appropriate location(s). Inventory Mover records the physical inventory adjustment. 14 | 15 | *(Pack)* Packer selects a pick bin and removes the packing sheet and scans the Order ID bar code (which contains order and ship group info). Packer selects the appropriate packaging (boxes). Packer scans the Product ID on each item and places the items within the packaging. Packer weighs each package as it is filled (including all packing materials) and records the weight. Packer marks the shipment as packed. 16 | 17 | Packer fills out any applicable customs forms based on the information returned, and attaches to package(s). Packer prints a shipping label and attaches it to each package. Packer prints personalized inserts and places inside the package. Packer seals the package and places into the appropriate outgoing carrier container. 18 | 19 | Company automatically creates Parcels Shipped Report. Divided by: shipping method, packer. Purpose: used for packer incentives, capacity planning. 20 | 21 | Carrier picks up packages in outgoing container and delivers them to Ship-To Customer. 22 | 23 | If Placing Customer wants to pick up an order at the warehouse, then Customer Service picks and packs the order and uses the Quick Ship functionality so the system recognizes that the order is fulfilled. 24 | -------------------------------------------------------------------------------- /screen/ubpl/Customer Finds Product.cwiki: -------------------------------------------------------------------------------- 1 | h1. Customer Finds Product 2 | 3 | h4. Ideas to incorporate: 4 | 5 | * Product Selection Wizards 6 | * Compare Similar Products 7 | 8 | h4. Story 9 | 10 | Customer reviews marketing materials and catalog resources to search among available products to find the product that meets their applicable needs or desires. 11 | 12 | *Browse Category Hierarchy* For larger numbers of available products when they know they want something that performs a certain function or has a certain form, and they look at the top level product categories and see something relevant to that function they may choose to select that top level category. Once that top level category is selected with that same function in mind they may choose a sub-category that more closely matches the form or function they have in mind. This may be repeated until they go down deep enough to find the category that represents the set of available products relevant to the form or function in mind. 13 | 14 | *Keyword and Parametric Search* If Customer does not see a category that matches what they have in mind, but they have some words to describe what they have in mind they may do a simple keyword search or go to an advanced search page that presents more searching options. If there is no category selected (ie Customer is not searching within a category) the advanced search options will be generic and may not include anything for a parameterized search (ie features of different types that can be selected to search by), but it may include some common parameters (features) to search by that are generally applicable across all or most of the available products. 15 | 16 | *Combined Search (category, keyword, parameter)* If Customer has already selected a category relevant to what they are looking for but they do not see a sub-category that also matches their needs (or there are multiple apparently relevant sub-categories and they choose not to explore each one), they may choose to search within a category. This can be a simple search but is generally an advanced search where Customer selects from a set of parameters (features) that are relevant for the category they are searching in. 17 | 18 | *Multi-Category Search* If Customer is browsing categories and finds two categories that are not specific enough to match the form or function they have in mind, but that together seem to describe it Customer may search with both categories as constraints and the results will be the products that are in (or in categories under) both of the selected categories. 19 | 20 | *View Product Detail* TODO 21 | 22 | -------------------------------------------------------------------------------- /screen/ubpl/Actor Definitions.cwiki: -------------------------------------------------------------------------------- 1 | h1. Actor Definitions 2 | 3 | h4. Accountant 4 | 5 | tracks financial impact of company activities for management and accountability reporting; manages cash flow 6 | 7 | creates and manages financial tools that multiply short-term profits in exchange for long-term fiscal stability (definition added in honour of Sep 2008) 8 | 9 | h4. Buyer 10 | 11 | purchases product or materials from third party suppliers (distributors, manufacturers, etc) 12 | 13 | h4. Carrier 14 | 15 | party that carries inventory from one place to another, often delivering shipments from Supplier to Company and from Company to Customer 16 | 17 | h4. Company 18 | 19 | the organization from whose perspective the processes are described, and who will own and run the eventual system 20 | 21 | h4. Customer 22 | 23 | a person or organization that purchases product from the company, can do so in one or more of these more specific Actor roles: 24 | 25 | h5. End-User Customer 26 | 27 | party who uses the product 28 | 29 | h5. Placing Customer 30 | 31 | party who places the order for the product 32 | 33 | h5. Ship-To Customer 34 | 35 | party who the product is shipped to from the company (and who will pass it on to the End-User Customer if they are not also that actor) 36 | 37 | h5. Bill-To Customer 38 | 39 | party to receives and who is responsible to pay the invoice for the order 40 | 41 | h4. Customer Service Representative 42 | 43 | h4. Distributor 44 | 45 | h4. Fulfillment Manager 46 | 47 | h4. Inventory Mover 48 | 49 | moves inventory (stock) around the warehouse, including put away but not including shipment picking 50 | 51 | h4. Manufacturer 52 | 53 | creates actual product, either finished goods and/or sub-assemblies, from materials 54 | 55 | h4. Marketer 56 | 57 | h4. Picker 58 | 59 | person responsible for picking inventory in warehouse and delivering it to packing area 60 | 61 | h4. Packer/Shipper 62 | 63 | packs inventory into boxes for shipping 64 | 65 | h4. Product Marketer 66 | 67 | manages customer facing product information and general pricing, promotions, and advertising about products; may be organized into multiple product marketers responsible for different sets of products that Company offers 68 | 69 | h4. Prospect 70 | 71 | a party who is interested in purchasing product (prospective customer) 72 | 73 | h4. Repairer 74 | 75 | h4. Sales Representative 76 | 77 | Company agent responsible for selling product offered by Company 78 | 79 | h4. Shipment Receiver 80 | 81 | person in the warehouse responsible for receiving shipments 82 | 83 | h4. Supplier 84 | 85 | a party that supplies product to the company, typically either a Manufacturer or Distributor 86 | 87 | -------------------------------------------------------------------------------- /screen/ubpl/Placing Customer Places a Sales Order (Online Checkout).cwiki: -------------------------------------------------------------------------------- 1 | h1. Placing Customer Places a Sales Order (Online Checkout) 2 | 3 | This story starts once Placing Customer has added products to a list in order to place a sales order. The interactions could take place through various mediums to send the information to the company, including internet, phone, fax, mail, or in-person. 4 | 5 | Placing Customer (PLC for this story) reviews list of items to order and decides to place a sales order with that set of items. 6 | PLC specifies general profile information including: 7 | 8 | * first and last name (optionally middle initial or middle name, title, prefix, suffix) 9 | * primary contact phone number (home, work, or mobile) 10 | * primary contact email address 11 | * shipping address (optionally multiple shipping addresses) 12 | * preferred payment method, with billing address where applicable (optionally multiple payment method; includes credit cards, EFT accounts, etc) 13 | * general preferences 14 | 15 | If PLC wants to create an account to access order status and other information later on in an automated way, PLC selects as username and password that will be used for future authentication. 16 | 17 | If PLC wants to split the order into multiple ship-groups for shipping to different destinations and/or shipping by different carriers or shipment methods, then PLC specifies ship groups desired and which quantity units of each item is associated with which ship-group. 18 | 19 | PLC specifies order-specific information including: 20 | 21 | * which shipping address to use for each ship-group (if more than one is on file) 22 | * the shipment method and carrier (if PLC allowed to select the carrier) to use for each ship-group 23 | * whether to ship the order all at once or as inventory is available 24 | * the payment preference(s) for how to pay for the order, including payment methods associated with the PLC, financial accounts, or other payment method options not setup in advance (COD, offline pre-payment, etc) 25 | * if PLC has a billing account setup they can use whatever is left on the credit limit of that billing account to defer payment until the order if fulfilled (more specifically until each package related to the order is packed) 26 | 27 | Company calculates additional adjustments such as a shipping cost estimate to be charged to Customer and the applicable taxes based on the items in the order and the shipping destination for each. 28 | 29 | Company will communicate to Customer all order information including what PLC specified and what Company calculated based on that. If everything looks correct and according to what PLC wants and/or needs, PLC will finalize the order, officially placing it with Company. 30 | 31 | -------------------------------------------------------------------------------- /screen/ubpl/UBPL Index.cwiki: -------------------------------------------------------------------------------- 1 | 2 | h2. [UBPL Introduction] 3 | 4 | h2. [Actor Definitions] 5 | 6 | h2. General Business Process Stories 7 | 8 | 9 | 10 | * Marketing 11 | ** [Product Marketer Maintains Product Information] 12 | ** [Marketer Maintains General Site Content] 13 | ** Product Market Study 14 | ** Advertising 15 | ** Customer Tracking 16 | 17 | * Procure to Pay, Demand to Inventory 18 | ** Sales Forecasting 19 | ** Inventory Level Monitoring 20 | ** [Buyer Places Purchase Order] 21 | ** [Accountant Receives Invoice and Sends Payment] 22 | ** [Shipment Receiver Receives Shipment] 23 | ** [Inventory Mover Puts Away Inventory] 24 | ** [Shipment Receiver Receives Shipment with Packing Slip but No PO] 25 | 26 | * Opportunity to Order 27 | ** Through Sales Representative 28 | *** [Sales Representative Seeks Prospects and Opportunities] 29 | *** [Sales Representative Leads Prospects from RFQ to Sales Order] 30 | *** [Customer Requests Quote from Cart] 31 | *** [Customer Places Order for Quote] 32 | ** Customer Direct 33 | *** [Customer Finds Product] 34 | *** [Placing Customer Adds Product to Cart] 35 | *** [Customer Creates and Edits Account (Profile)] 36 | *** [Placing Customer Places a Sales Order (Through CSR)] 37 | *** [Placing Customer Places a Sales Order (Online Checkout)] 38 | *** [Placing Customer Places a Sales Order (Through EBay)] 39 | *** [Customer Reviews Order History and Status] 40 | *** [Customer Cancels Order] 41 | 42 | * Order to Cash 43 | ** [Company Approves Sales Order] 44 | ** [Company Fulfills Sales Order] 45 | ** [Accountant Sends Invoice and Receives Payment] 46 | ** [Carrier Does Not Deliver Shipment to Customer] 47 | ** [Carrier Returns Undeliverable Shipment to Company] 48 | 49 | * Return Management 50 | ** [Customer Returns Product] 51 | ** [Company Processes Return Received] 52 | 53 | * Warehouse Management 54 | ** [Inventory Mover does Stock Move] 55 | ** [Inventory Mover Checks Physical Inventory] 56 | 57 | * Manufacturing 58 | 59 | * Financial Management 60 | ** Budgeting 61 | ** Internal Financial Analysis (management metrics, balanced score card) 62 | ** External Reporting (government, investors, etc) 63 | 64 | * Accounting 65 | ** Financial Accounts 66 | ** [Bank Reconciliation] 67 | ** Periodic Reporting 68 | 69 | * Work Plan to Pay 70 | ** Projects and Tasks 71 | ** Requests 72 | ** Time and Expense Recording 73 | ** Receive and Pay Vendor/Worker Invoice 74 | ** Send Client Invoice, Receive Client Payment 75 | 76 | 77 | h2. Stories for Specific Types of Organizations 78 | 79 | * [Story of Online Retail Company] 80 | * Story of Manufacturer 81 | * Story of Professional Services Company 82 | * Story of Service Provider 83 | * Story of Service Provider Alliance 84 | 85 | h2. OAGIS Scenarios 86 | 87 | * [OAGIS Order to Cash] 88 | * [OAGIS Work to Cash] 89 | * [OAGIS Demand to Inventory] 90 | -------------------------------------------------------------------------------- /AUTHORS: -------------------------------------------------------------------------------- 1 | Mantle Business Artifacts (http://github.com/moqui/mantle) 2 | 3 | This software is in the public domain under CC0 1.0 Universal plus a 4 | Grant of Patent License. 5 | 6 | To the extent possible under law, the author(s) have dedicated all 7 | copyright and related and neighboring rights to this software to the 8 | public domain worldwide. This software is distributed without any 9 | warranty. 10 | 11 | You should have received a copy of the CC0 Public Domain Dedication 12 | along with this software (see the LICENSE.md file). If not, see 13 | . 14 | 15 | =========================================================================== 16 | 17 | Copyright Waiver 18 | 19 | I dedicate any and all copyright interest in this software to the 20 | public domain. I make this dedication for the benefit of the public at 21 | large and to the detriment of my heirs and successors. I intend this 22 | dedication to be an overt act of relinquishment in perpetuity of all 23 | present and future rights to this software under copyright law. 24 | 25 | To the best of my knowledge and belief, my contributions are either 26 | originally authored by me or are derived from prior works which I have 27 | verified are also in the public domain and are not subject to claims 28 | of copyright by other parties. 29 | 30 | To the best of my knowledge and belief, no individual, business, 31 | organization, government, or other entity has any copyright interest 32 | in my contributions, and I affirm that I will not make contributions 33 | that are otherwise encumbered. 34 | 35 | Signed by git commit adding my legal name and git username: 36 | 37 | Written in 2010-2016 by David E. Jones - jonesde 38 | 39 | =========================================================================== 40 | 41 | Grant of Patent License 42 | 43 | I hereby grant to recipients of software a perpetual, worldwide, 44 | non-exclusive, no-charge, royalty-free, irrevocable (except as stated in 45 | this section) patent license to make, have made, use, offer to sell, sell, 46 | import, and otherwise transfer the Work, where such license applies only to 47 | those patent claims licensable by me that are necessarily infringed by my 48 | Contribution(s) alone or by combination of my Contribution(s) with the 49 | Work to which such Contribution(s) was submitted. If any entity institutes 50 | patent litigation against me or any other entity (including a cross-claim 51 | or counterclaim in a lawsuit) alleging that my Contribution, or the Work to 52 | which I have contributed, constitutes direct or contributory patent 53 | infringement, then any patent licenses granted to that entity under this 54 | Agreement for that Contribution or Work shall terminate as of the date such 55 | litigation is filed. 56 | 57 | Signed by git commit adding my legal name and git username: 58 | 59 | Written in 2010-2016 by David E. Jones - jonesde 60 | 61 | -------------------------------------------------------------------------------- /screen/ubpl/UBPL Introduction.cwiki: -------------------------------------------------------------------------------- 1 | h1. UBPL Introduction 2 | 3 | h4. Why a Universal Business Process Library? 4 | 5 | 6 | The general idea is to create something like the "Universal Data Model", and that will continue to provide the basic business information concepts that we all use on a daily basis. Instead of for data structures, this would be for business processes. 7 | 8 | I've spent some time over the years, and others I work work have spent some time more recently, trying to find some sort of business process library we could base this on, but with no real luck. The closest things I've found are some semi-helpful books about business best practices, and documents created as a part of a number of business related specifications. I've started a page with those here: 9 | 10 | [Resources with Information about General Business Processes] 11 | 12 | Still, these are not adequate for our needs, and even if they were I think we would want something that the community could get behind to maintain and expand, and also tie these artifacts to actual things that exist in Mantle. So, here we are, a few things I've thrown together to start assembling a Universal Business Process Library: 13 | 14 | [Universal Business Process Library Index] 15 | 16 | This isn't meant to include everything that every business might do, but to be a library of general business activities that make up common processes that are shared by a wide variety of businesses. Some may of course be less commonly used, but the general intent will be similar to that of the rest of Mantle, ie things that can be customized and reused or used as-is for a wide variety of businesses to help with their process automation efforts. 17 | 18 | h4. What is in this Library? 19 | 20 | This library will consist of Business Process Stories. These stories are basically a series of sentences, each one consisting of an actor and an action. Just keep that in mind, it's _always_ actor and action, actor and action, actor and action. Hopefully that's clear... ;) All sentences need both, and may have conditions on them and other things as well, but always need an actor and an action. One basic rule based on that is no actions with actors. 21 | 22 | The top level document has 3 main parts: 23 | 24 | 1. Actor Definitions 25 | 2. General Business Process Stories 26 | 3. Stories for Specific Types of Organizations 27 | 28 | In part #2 we'll create the library of smaller stories that make up parts of the higher level stories that are in #3. For example, look at the Story of Retail Company: 29 | 30 | [Story of Online Retail Company] 31 | 32 | There are a lot of high level steps in that story that describe general business activities. These are assembled in a way that makes sense for a retail company, but many of the individual activities are just as applicable in different parts of the high level stories for other types of organizations. 33 | 34 | Again, part #2 has smaller scoped processes that can be reused in many different types of companies, and based on writing stories for specific types of organizations we'll flesh that out to include a wide variety of business activities organized according to yet higher level business concepts, like the Marketing, Sales, Warehouse Management, etc that are currently in there. 35 | 36 | In part #2 each of these process names should also include both actor and action, and for higher level things like this the actor should be the "primary" actor for the story, there will certainly be other actors involved in most of them. 37 | 38 | h4. Concepts Behind This, and "HEMP" 39 | 40 | The idea of using stories (aka "narratives") like this is a common one. Part of the reason for writing them specifically in the way I've described here is to make them a good starting point for further UI and system design efforts. For those interested, this is based on a lot of research I've done over the years while trying to work more effectively with clients, and have written a book on that topic called "HEMP: An agile approach to analysis and design". HEMP stands for "Holistic Enterprise Mechanization Process". On a side note, a better word for "mechanization" is "automation", but I thought HEMP would make a more colourful and interesting title than "HEAP". 41 | 42 | The book and other details are available at: [http://www.dejc.com/HEMP] 43 | 44 | h4. A Special Note on Testing 45 | 46 | The requirements and designs that come out of this effort will also help drive automated and manual testing efforts. Sometimes a problem with testing is we don't know what to test, or what the business activities the software is trying to support. This will help with the problem. Along with these business process stories we may want test scenarios based on them, that are linked to from the stories. There may be many things linked to from these stories actually.... 47 | -------------------------------------------------------------------------------- /screen/ubpl/Resources with Information about General Business Processes.cwiki: -------------------------------------------------------------------------------- 1 | h1. General Resources 2 | 3 | h2. UBL 4 | 5 | h3. General Info 6 | 7 | Site: http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=ubl 8 | 9 | Current Version: 2.0 10 | 11 | Detailed info archive: http://docs.oasis-open.org/ubl/os-UBL-2.0.zip 12 | 13 | h3. Parts of the Standard to Implement 14 | 15 | h3. Related Data Model Elements 16 | 17 | h2. OAGIS 18 | 19 | h3. General Info 20 | 21 | OAGIS is a standard created by the Open Applications Group. 22 | 23 | Site: http://www.oagi.org/ 24 | 25 | Current version: 9.3 26 | 27 | h3. Parts of the Standard to Implement 28 | 29 | h3. Related Data Model Elements 30 | 31 | h3. Reusable from OFBiz 32 | 33 | The following messages are implemented in the specialpurpose/oagis component: 34 | 35 | # Confirm BOD (send and receive) 36 | # Process Shipment (send) 37 | # Receive Delivery (Send) 38 | # Sync Inventory (receive) 39 | # Show Shipment (receive) 40 | # Acknowledge Delivery (receive), for PO, RMA, Status Change 41 | 42 | There is a service defined for each of these in the specialpurpose/oagis/servicedef/services.xml file. 43 | 44 | Note that these were implemented against and older version of OAGIS: 7.2.1 45 | 46 | h2. XBRL 47 | 48 | h3. General Info 49 | 50 | The general idea here is that instead of creating PDF or other reports (or in addition to the basic PDF reports) we can use these as a standardized structure for financial reporting. I've read about XBRL over the years and from what I can tell in the last couple of years it has really become commonly used among companies large and small for internal reporting as well as reporting to government agencies in many parts of the world, and for sharing financials informations with partners (more accounting firms and such than suppliers or customers, just to clarify). 51 | 52 | This would be a great thing, and leaning on such standards will lend some clout to our accounting component. I figure that the numbers coming out of the accounting package are the most important thing about it, so basing those on a standard like this gives us a huge step forward for prospective user organizations both large and small. 53 | 54 | Technical information about the XML document structures and such is here (look at the first section, for XBRL 2.1): 55 | http://www.xbrl.org/SpecRecommendations/ 56 | 57 | h3. Parts of the Standard to Implement 58 | 59 | XBRL is a file structure for financial data that has a number of taxonomies defined on top of it. Those taxonomies are the real spec for what should be included in each report. 60 | 61 | There are three that would be great to have done for our most likely near future users: 62 | 63 | 1. IFRS-GP 2006: International Financial Reporting Standards General Purpose Financial Reporting for Profit-Oriented Entities 64 | http://xbrl.iasb.org/int/fr/ifrs/gp/2006-08-15/summary_page.html 65 | 66 | 2. US-GAAP-CI: United States Generally Accepted Accounting Practices for Commercial and Industrial 67 | http://www.xbrl.org/us/fr/gaap/ci/2005-02-28/us-gaap-ci%20Summary%20Page.htm 68 | 69 | 3. XBRL GL: General Ledger Taxonomy 70 | http://www.xbrl.org/GLTaxonomy/ 71 | 72 | The first two are more for reporting that can actually be delivered to government and other agencies, and used with tools internally for visualization and such. The third will allow us to export financial information in a standard way that can then be combined with financial information from other systems for reporting. For large organizations this could be the key to letting the system run everything it is responsible for and then export financial data in a standard way so the corporation can use XBRL compatible tools to combine it with information from other systems and such. 73 | 74 | A more general list of financial reporting taxonomies is available here: 75 | http://www.xbrl.org/FRTaxonomies/ 76 | 77 | h3. Related Data Model Elements 78 | 79 | h1. Integration Oriented Standards 80 | 81 | h3. UBL 2.0 Business Processes 82 | 83 | This is an important one because if we want to implement an integration standard this is a big one to consider (ie UBL 2.0), and OAGIS is another. 84 | 85 | This document has quite a few diagrams and definitions which are very helpful. 86 | 87 | http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.html#BUSINESSPROCESSES 88 | 89 | Also in the same document the list of schemas for process communication documents is helpful: 90 | 91 | http://docs.oasis-open.org/ubl/os-UBL-2.0/UBL-2.0.html#SCHEMAS 92 | 93 | h3. ebXML Catalog of Common Business Processes 94 | 95 | This is a little older from 2001, but still useful and includes a list of related processes in many different standard specs. This is a large document with a really long list of fairly granular processes. 96 | 97 | http://www.ebxml.org/specs/bpPROC.pdf 98 | 99 | h3. Universal Business Language 1.0 ebBP 2.0 Business Process Definitions 100 | 101 | This is more related to UBL 1.0, but is recent (from 2006) and useful. It is brief though. 102 | 103 | http://docs.oasis-open.org/ubl/cs-UBL-1.0-SBS-1.0/universal-business-process-1.0-ebBP/ 104 | 105 | -------------------------------------------------------------------------------- /screen/ubpl/Company Processes Return Received.cwiki: -------------------------------------------------------------------------------- 1 | h1. Company Processes Return Received 2 | 3 | h4. Ideas to Incorporate 4 | 5 | h4. Dependencies 6 | 7 | * [Customer Returns Product] 8 | 9 | h4. Story 10 | 11 | Carrier delivers return shipment. Shipment Receiver receives the return shipment. If the original packaging is unopened Shipment Receiver sends it to Inventory Mover for put away. Otherwise Shipment Received sends it to Repairer for review/testing, refurbishment, return to manufacturer, or disposal of damaged inventory. If Repairer finds the product to be in good condition or is able to repair the item to pass all tests Repairer changes inventory item to point to refurbished version of the product, and sends it to Inventory Mover for put away. In all cases Repairer (or Inventory Mover if Repairer does not touch the item) records information about action taken for the return shipment. 12 | 13 | If Customer ships the wrong item CSR contacts Customer and asks if they want to have the item shipped back to them (and pay for shipping), or if they want to create a new return for that item (and cancel the original return), or other resolution. 14 | 15 | Company responds to return according to response type desired by customer and approved by CSR (see Return Handling by Response Type per Item section below). 16 | 17 | *(Refund Payment)* If payment was by credit card then Company automatically refunds to the credit card as a refund against the original transaction. There may be multiple transactions if the return includes items from multiple orders. If the total refund amount is greater than 110% (or whatever value the payment gateway, CC company, and merchant bank support), then a new transaction to send funds to the card will be created (NOTE: if this is not possible with payment gateway or CC company or merchant bank then look into store credit as an alternative). 18 | 19 | If payment was by PayPal then Company automatically refunds to via PayPal against the original transaction. If refund amount is greater than the original transaction amount the amount above the original transaction amount will be sent in a new transfer. 20 | 21 | If payment was by Money Order or Business Check then Company puts refunded amount into store credit (in a Financial Account unless Customer has a Billing Account with negative balance). In special cases VP may choose to send a check to Customer for refund. 22 | 23 | *(Complete Return)* Return is completed when all items needing to be received arrive, and only then are return responses done (ie no responses for one return item at a time). 24 | 25 | h4. Return Handling by Response Type per Item 26 | 27 | h5. Wait and Refund 28 | 29 | Customer sends original item back. Warehouse (Shipment Receiver and either Inventory Mover or Repairer) processes the return and sets the item status as received. Company refunds the amount configured on the return for the item. 30 | 31 | h5. Wait and Replace 32 | 33 | Customer sends original item back. Warehouse processes the return and sets the item status as received. Company approves replacement order created when return was approved. If replacement order has been cancelled then Company automatically creates zero amount replacement order. 34 | 35 | h5. Refund Immediately (don't expect return of original) 36 | 37 | (generally for small items with damage, and time or other factors prevent replacement) The status for the return will be approved. Company refunds the amount configured on the return item. 38 | 39 | h5. Replace Immediately (don't expect return of original) 40 | 41 | (generally for smaller items that cost less than the shipping, or for lost packages) The status for the return will be approved. Company creates a zero amount order for the replacement items configured on the return item. 42 | 43 | h5. Refund and Replace Immediately (request but don't worry about return of original) 44 | 45 | The status for the return will be approved. Company refunds the amount configured on the return, creates a zero amount order for 46 | the replacement items configured on the return. Customer may send the original item(s) back. Company receives the items and processes them. 47 | 48 | h5. Cross-Ship Replacement and Refund 49 | 50 | The status for the return will be approved. Customer sends proof of shipping for orignal item(s) in the form of a tracking number or a scanned receipt or something by email. Customer Service Representative receives the email and sets the return item status to "proof of shipping received". For item(s) to replace Company creates a zero amount order for the replacement items configured on the return. For item(s) to refund Company refunds the amount configured on the return. Customer sends the original item(s) back. Company receives the items and processes them. Company sees that the replacement has already been sent and sets the return status to complete. 51 | 52 | If X days have passed and the original item(s) have not been received for the return Customer Service Representative contacts customer once to try to find more information and resolve the issue. 53 | 54 | h5. Cross-Ship Replacement (guaranteed by credit card) 55 | 56 | The status for the return will be approved. For item(s) to replace Company creates an order charged to the selected credit card for the replacement items configured on the return. Customer sends the original item(s) back. Company receives the items and processes them. Company sees that the replacement has already been sent and sets the return status to complete. Company credits amount charged for the replacement back to credit card selected for return. For refund after a return for replacement use payment transaction info from original order even though order attached directly to the return is a zero amount order. 57 | -------------------------------------------------------------------------------- /screen/ubpl/OAGIS Order to Cash.cwiki: -------------------------------------------------------------------------------- 1 | {toc} 2 | 3 | h2. Introduction 4 | 5 | This process covers Customer and Supplier processes from Order through Cash plus Quotes and GL. 6 | 7 | h2. OAGIS Scenarios 8 | 9 | h3. Incorporated Scenarios 10 | 11 | * 1 - General Ledger to Sub Ledgers 12 | * 5 - Order Management to Accounts Receivable and General Ledger 13 | * 7 - Purchasing to Accounts Payable to General Ledger 14 | * 8 - Purchasing to Accounts Payable to General Ledger Posting from Purchasing 15 | * 12 - Basic Purchase Order Process 16 | * 25 - Invoice Matching, Matching in Accounts Payable 17 | * 27 - Sales Force Automation to Order Management, Updating Orders 18 | * 28 - Sales Force Automation to Order Management, Inquiry of Orders 19 | * 29 - Sales Force Automation to Order Management and Shipping 20 | * 30 - Supply Chain Integration 21 | * 37 - Catalog and Price List Exchange 22 | * 39 - Request for Quote and Quote Exchange 23 | * 47 - Full Cycle Purchasing 24 | * 53 - Inventory Visibility 25 | * 54 - Mid Market Order to Cash Procure to Pay 26 | * 55 - High Tech Procure to Pay 27 | * 56 - High Tech Invoicing 28 | * 58 - Metals Industry Order to Cash Procure to Pay 29 | * 59 - High Tech Logistics - Direct Ship Model 30 | * 60 - High Tech Logistics - Standard VMI With Outsourced - Customer Agent 31 | * 61 - High Tech Logistics - Customer Operated Hub 32 | 33 | h3. Related Scenarios 34 | 35 | * 3 - Order Management to Accounts Receivable 36 | * 4 - Order Management to Credit Management to Accounts Receivable 37 | * 14 - Plant Data Collection / Warehouse Management / Issues 38 | * 15 - Plant Data Collection / Warehouse Management / Transfers 39 | * 19 - Plant Data Collection / Warehouse Management / Shipping 40 | * 21 - Manufacturing to Purchasing (Requisitions, Purchasing, Inspection, Receiving, MRP) 41 | * 22 - Manufacturing with Available to Promise to Order Management 42 | * 23 - Manufacturing to Order Management Financials with Manufacturing for Engineer to Order and Configure to Order (Engineering - BOM, Inventory - Finished Goods, Order Management, Manufacturing, Inventory - Work In Progress, GL, Costing, AR) 43 | * 31 - Customer Service Integration, Field Service, No Returns 44 | * 48 - Sales Lead 45 | * 49 - Sales Opportunity 46 | 47 | h2. Actors 48 | 49 | * Customer - purchase product from Supplier 50 | * Supplier - sells product to Customer 51 | * Carrier - transports product from Supplier to Customer 52 | * Organization - general organization, may be Customer or Supplier or other 53 | 54 | h2. Process Story 55 | 56 | h3. Catalog 57 | 58 | Supplier Catalog Management sends SyncCatalog to Supplier Order Management and Purchasing, and each sends ConfirmBOD to Catalog. 59 | Catalog sends SyncPriceList to OM and Purchasing, and each sends ConfirmBOD to Catalog. 60 | Inventory sends SyncItemMaster to OM, Catalog, and Purchasing and each sends ConfirmBOD to Inventory. 61 | 62 | Customer sends GetCatalog to Supplier and Supplier sends ShowCatalog to Customer (alternatively Supplier Sync and Customer Confirm). 63 | Customer sends GetPriceList to Supplier and Supplier sends ShowPriceList to Customer (alternatively Supplier Sync and Customer Confirm). 64 | 65 | Customer sends GetInventoryBalance to Supplier and Supplier sends ShowInventoryBalance to Customer. 66 | Alternatively, Supplier sends SyncInventoryBalance to Customer and Customer sends ConfirmBOD to Supplier (and optionally vice-versa). 67 | 68 | h3. Quote 69 | 70 | Customer sends ProcessRFQ to Supplier and Supplier sends AcknowledgeRFQ to Customer. 71 | To change a RFQ, Customer sends ChangeRFQ to Supplier and Supplier sends RespondRFQ to Customer. 72 | To get RFQ details, Supplier sends GetRFQ to Customer and Customer sends ShowRFQ to Supplier. 73 | To cancel an RFQ, Customer sends CancelRFQ to Supplier and Supplier sends ConfirmBOD to Customer. 74 | 75 | Supplier sends ProcessQuote to Customer and Customer sends AcknowledgeQuote to Supplier. 76 | To change a quote, Supplier sends ChangeQuote to Customer and Customer sends RespondQuote to Supplier. 77 | To get quote details, Customer sends GetQuote to Supplier and Supplier sends ShowQuote to Customer. 78 | To cancel a quote, Supplier sends CancelQuote to Customer and Customer sends ConfirmBOD to Supplier. 79 | 80 | h3. Order 81 | 82 | Customer sends ProcessPurchaseOrder to Supplier (supplier internally creates SalesOrder) and Supplier sends AcknowledgePurchaseOrder to Customer. 83 | To change a purchase order Customer sends ChangePurchaseOrder to Supplier and Supplier sends RespondPurchaseOrder to Customer. 84 | To cancel a purchase order Customer sends CancelPurchaseOrder to Supplier and Supplier sends ConfirmBOD to Customer. 85 | To get purchase order info Supplier sends GetPurchaseOrder to Customer and Customer sends ShowPurchaseOrder to Supplier. 86 | 87 | Supplier Sales sends SyncPurchaseOrder to Supplier Order Management. 88 | Supplier Order Management sends SyncPurchaseOrder to Manufacturing, Shipping, and/or Billing and each sends ConfirmBOD to OM. 89 | 90 | For separate internal Sales/SFA within Supplier: 91 | Sales (SFA) sends ProcessSalesOrder to Order Management and OM sends AcknowledgeSalesOrder to Sales. 92 | To change a sales order Sales sends ChangeSalesOrder to OM and OM sends RespondSalesOrder to Sales. 93 | To cancel a sales order Sales sends CancelSalesOrder to OM and OM sends ConfirmBOD to Sales. 94 | To get sales order info OM sends GetSalesOrder to Sales and Sales sends ShowSalesOrder to OM. 95 | If Supplier has separate Manufacturing, Shipping, or Billing (or Dispatch, Weight Bridge) Supplier OM sends SyncSalesOrder to each and each sends ConfirmBOD to OM. 96 | 97 | h3. Shipping 98 | 99 | Customer sends ProcessPlanningSchedule to Supplier and Supplier sends AcknowledgePlanningSchedule to Customer. 100 | 101 | (pick/pack) Supplier Manufacturing sends UpdatePickList to Supplier Shipping and Supplier Shipping sends RespondPickList to Supplier Manufacturing. 102 | Supplier Shipping sends PostJournalEntry to Supplier GL and GL sends PostAcknowledgeJournalEntry to Shipping. 103 | 104 | (carrier) Supplier sends ProcessShipment to Carrier and Carrier sends AcknowledgeShipment to Supplier. 105 | Supplier sends ProcessCommercialInvoice, NotifyShippersLetterOfInstruction, NotifyExportDeclaration, and NotifyHazardousMaterialShipmentDocument to Carrier (as needed) and Carrier sends ConfirmBOD to Supplier. 106 | 107 | Carrier picks up shipment from Supplier. 108 | 109 | Supplier sends NotifyShipment to Customer and Customer sends ConfirmBOD to Supplier. 110 | Supplier sends NotifyShipment to Carrier and Carrier sends ConfirmBOD to Supplier. 111 | 112 | Carrier delivers shipment to Customer. 113 | 114 | Carrier sends NotifyShipmentUnit to Supplier and Customer, and each send ConfirmBOD to Carrier. 115 | Carrier sends ProcessInvoice (for freight) to Supplier and/or Customer, and Supplier and/or Customer send AcknowledgeInvoice to Carrier. 116 | Carrier sends NotifyReceiveDelivery to Supplier and Supplier sends ConfirmBOD to Carrier. 117 | 118 | Customer sends NotifyReceiveDelivery to Supplier and Supplier sends ConfirmBOD to Customer. 119 | 120 | h3. Supplier AR 121 | 122 | Supplier AR sends ProcessInvoice to Customer AP and Customer AP sends AcknowledgeInvoice to Supplier. 123 | 124 | Supplier Billing sends PostJournalEntry to Supplier General Ledger and GL sends PostAcknowledgeJournalEntry to Billing. 125 | Alternatively, Supplier Billing sends LoadReceivable to Supplier AR and AR sends ConfirmBOD to Billing, then Supplier AR sends PostJournalEntry to Supplier GL and GL sends PostAcknowledgeJournalEntry to AR. 126 | Alternatively, Supplier Order Management sends LoadReceivable to Supplier AR and AR sends ConfirmBOD to OM, then AR sends PostJournalEntry to GL and GL sends PostAcknowledgeJournalEntry to AR. 127 | 128 | h3. Customer AP 129 | 130 | Customer Purchasing sends SyncPartyMaster to AP and AP sends ConfirmBOD to Purchasing (and vice-versa to keep in sync). 131 | 132 | Customer Purchasing sends LoadPayable to AP and AP sends ConfirmBOD to Purchasing. AP or Purchasing sends PostJournalEntry to GL and GL sends ConfirmBOD back. 133 | 134 | Customer sends NotifyRemittanceAdvice to Supplier and Supplier sends ConfirmBOD to Customer. 135 | 136 | h3. Sub-Ledger 137 | 138 | If Organization has separate General Ledger and Sub-Ledger(s), Organization GL sends SyncChartOfAccounts to Sub-Ledger and SL sends 139 | ConfirmBOD to GL. SL sends PostJournalEntry to GL and GL sends PostAcknowledgeJournalEntry to SL. 140 | 141 | h2. Simple Order to Cash Scenario 142 | 143 | Customer sends ProcessPurchaseOrder to Supplier (supplier internally creates SalesOrder) and Supplier sends AcknowledgePurchaseOrder to Customer. 144 | 145 | Supplier sends NotifyShipment to Customer and Customer sends ConfirmBOD to Supplier. TODO: NotifyBOM? 146 | 147 | Customer optionally sends NotifyReceiveDelivery to Supplier and Supplier sends ConfirmBOD to Customer. 148 | 149 | Supplier sends ProcessInvoice to Customer and Customer sends AcknowledgeInvoice to Supplier. 150 | 151 | Customer sends NotifyRemittanceAdvice to Supplier and Supplier sends ConfirmBOD to Customer. 152 | 153 | h2. OAGIS Documents Used 154 | 155 | h3. Party 156 | * SyncPartyMaster - ConfirmBOD 157 | 158 | h3. Catalog and Inventory 159 | * SyncCatalog - ConfirmBOD 160 | * SyncPriceList - ConfirmBOD 161 | * SyncItemMaster - ConfirmBOD 162 | * GetCatalog - ShowCatalog 163 | * SyncInventoryBalance - ConfirmBOD 164 | 165 | h3. RFQ and Quote 166 | * ProcessRFQ - AcknowledgeRFQ 167 | * ChangeRFQ - RespondRFQ 168 | * GetRFQ - ShowRFQ 169 | * CancelRFQ - ConfirmBOD 170 | * ProcessQuote - AcknowledgeQuote 171 | * ChangeQuote - RespondQuote 172 | * GetQuote - ShowQuote 173 | * CancelQuote - ConfirmBOD 174 | 175 | h3. Purchase Order 176 | * ProcessPurchaseOrder - AcknowledgePurchaseOrder 177 | * ChangePurchaseOrder - RespondPurchaseOrder 178 | * CancelPurchaseOrder - ConfirmBOD 179 | * GetPurchaseOrder - ShowPurchaseOrder 180 | * SyncPurchaseOrder - ConfirmBOD 181 | 182 | h3. Sales Order 183 | * ProcessSalesOrder - AcknowledgeSalesOrder 184 | * ChangeSalesOrder - RespondSalesOrder 185 | * CancelSalesOrder - ConfirmBOD 186 | * GetSalesOrder - ShowSalesOrder 187 | * SyncSalesOrder - ConfirmBOD 188 | 189 | h3. Shipping 190 | * ProcessPlanningSchedule - AcknowledgePlanningSchedule 191 | * UpdatePickList - RespondPickList 192 | * ProcessShipment - AcknowledgeShipment 193 | * ProcessCommercialInvoice, NotifyShippersLetterOfInstruction, NotifyExportDeclaration, NotifyHazardousMaterialShipmentDocument - ConfirmBOD 194 | * NotifyShipment - ConfirmBOD 195 | * NotifyShipmentUnit - ConfirmBOD 196 | * NotifyReceiveDelivery (aka NotifyDeliveryReceipt?) - ConfirmBOD 197 | 198 | h3. AR, Invoice, AP, Payment 199 | * LoadReceivable - ConfirmBOD 200 | * ProcessInvoice - AcknowledgeInvoice 201 | * LoadPayable - ConfirmBOD 202 | * NotifyRemittanceAdvice - ConfirmBOD 203 | 204 | h3. Ledger 205 | * PostJournalEntry - PostAcknowledgeJournalEntry 206 | * SyncChartOfAccounts - ConfirmBOD 207 | 208 | h2. Initial Documents to Support 209 | 210 | * ProcessPurchaseOrder - AcknowledgePurchaseOrder 211 | * NotifyShipment - ConfirmBOD 212 | * ProcessInvoice - AcknowledgeInvoice 213 | * NotifyRemittanceAdvice - ConfirmBOD 214 | -------------------------------------------------------------------------------- /LICENSE.md: -------------------------------------------------------------------------------- 1 | Because of a lack of patent licensing in CC0 1.0 this software includes a 2 | separate Grant of Patent License adapted from Apache License 2.0. 3 | 4 | =========================================================================== 5 | 6 | Creative Commons Legal Code 7 | 8 | CC0 1.0 Universal 9 | 10 | CREATIVE COMMONS CORPORATION IS NOT A LAW FIRM AND DOES NOT PROVIDE 11 | LEGAL SERVICES. DISTRIBUTION OF THIS DOCUMENT DOES NOT CREATE AN 12 | ATTORNEY-CLIENT RELATIONSHIP. CREATIVE COMMONS PROVIDES THIS 13 | INFORMATION ON AN "AS-IS" BASIS. CREATIVE COMMONS MAKES NO WARRANTIES 14 | REGARDING THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS 15 | PROVIDED HEREUNDER, AND DISCLAIMS LIABILITY FOR DAMAGES RESULTING FROM 16 | THE USE OF THIS DOCUMENT OR THE INFORMATION OR WORKS PROVIDED 17 | HEREUNDER. 18 | 19 | Statement of Purpose 20 | 21 | The laws of most jurisdictions throughout the world automatically confer 22 | exclusive Copyright and Related Rights (defined below) upon the creator 23 | and subsequent owner(s) (each and all, an "owner") of an original work of 24 | authorship and/or a database (each, a "Work"). 25 | 26 | Certain owners wish to permanently relinquish those rights to a Work for 27 | the purpose of contributing to a commons of creative, cultural and 28 | scientific works ("Commons") that the public can reliably and without fear 29 | of later claims of infringement build upon, modify, incorporate in other 30 | works, reuse and redistribute as freely as possible in any form whatsoever 31 | and for any purposes, including without limitation commercial purposes. 32 | These owners may contribute to the Commons to promote the ideal of a free 33 | culture and the further production of creative, cultural and scientific 34 | works, or to gain reputation or greater distribution for their Work in 35 | part through the use and efforts of others. 36 | 37 | For these and/or other purposes and motivations, and without any 38 | expectation of additional consideration or compensation, the person 39 | associating CC0 with a Work (the "Affirmer"), to the extent that he or she 40 | is an owner of Copyright and Related Rights in the Work, voluntarily 41 | elects to apply CC0 to the Work and publicly distribute the Work under its 42 | terms, with knowledge of his or her Copyright and Related Rights in the 43 | Work and the meaning and intended legal effect of CC0 on those rights. 44 | 45 | 1. Copyright and Related Rights. A Work made available under CC0 may be 46 | protected by copyright and related or neighboring rights ("Copyright and 47 | Related Rights"). Copyright and Related Rights include, but are not 48 | limited to, the following: 49 | 50 | i. the right to reproduce, adapt, distribute, perform, display, 51 | communicate, and translate a Work; 52 | ii. moral rights retained by the original author(s) and/or performer(s); 53 | iii. publicity and privacy rights pertaining to a person's image or 54 | likeness depicted in a Work; 55 | iv. rights protecting against unfair competition in regards to a Work, 56 | subject to the limitations in paragraph 4(a), below; 57 | v. rights protecting the extraction, dissemination, use and reuse of data 58 | in a Work; 59 | vi. database rights (such as those arising under Directive 96/9/EC of the 60 | European Parliament and of the Council of 11 March 1996 on the legal 61 | protection of databases, and under any national implementation 62 | thereof, including any amended or successor version of such 63 | directive); and 64 | vii. other similar, equivalent or corresponding rights throughout the 65 | world based on applicable law or treaty, and any national 66 | implementations thereof. 67 | 68 | 2. Waiver. To the greatest extent permitted by, but not in contravention 69 | of, applicable law, Affirmer hereby overtly, fully, permanently, 70 | irrevocably and unconditionally waives, abandons, and surrenders all of 71 | Affirmer's Copyright and Related Rights and associated claims and causes 72 | of action, whether now known or unknown (including existing as well as 73 | future claims and causes of action), in the Work (i) in all territories 74 | worldwide, (ii) for the maximum duration provided by applicable law or 75 | treaty (including future time extensions), (iii) in any current or future 76 | medium and for any number of copies, and (iv) for any purpose whatsoever, 77 | including without limitation commercial, advertising or promotional 78 | purposes (the "Waiver"). Affirmer makes the Waiver for the benefit of each 79 | member of the public at large and to the detriment of Affirmer's heirs and 80 | successors, fully intending that such Waiver shall not be subject to 81 | revocation, rescission, cancellation, termination, or any other legal or 82 | equitable action to disrupt the quiet enjoyment of the Work by the public 83 | as contemplated by Affirmer's express Statement of Purpose. 84 | 85 | 3. Public License Fallback. Should any part of the Waiver for any reason 86 | be judged legally invalid or ineffective under applicable law, then the 87 | Waiver shall be preserved to the maximum extent permitted taking into 88 | account Affirmer's express Statement of Purpose. In addition, to the 89 | extent the Waiver is so judged Affirmer hereby grants to each affected 90 | person a royalty-free, non transferable, non sublicensable, non exclusive, 91 | irrevocable and unconditional license to exercise Affirmer's Copyright and 92 | Related Rights in the Work (i) in all territories worldwide, (ii) for the 93 | maximum duration provided by applicable law or treaty (including future 94 | time extensions), (iii) in any current or future medium and for any number 95 | of copies, and (iv) for any purpose whatsoever, including without 96 | limitation commercial, advertising or promotional purposes (the 97 | "License"). The License shall be deemed effective as of the date CC0 was 98 | applied by Affirmer to the Work. Should any part of the License for any 99 | reason be judged legally invalid or ineffective under applicable law, such 100 | partial invalidity or ineffectiveness shall not invalidate the remainder 101 | of the License, and in such case Affirmer hereby affirms that he or she 102 | will not (i) exercise any of his or her remaining Copyright and Related 103 | Rights in the Work or (ii) assert any associated claims and causes of 104 | action with respect to the Work, in either case contrary to Affirmer's 105 | express Statement of Purpose. 106 | 107 | 4. Limitations and Disclaimers. 108 | 109 | a. No trademark or patent rights held by Affirmer are waived, abandoned, 110 | surrendered, licensed or otherwise affected by this document. 111 | b. Affirmer offers the Work as-is and makes no representations or 112 | warranties of any kind concerning the Work, express, implied, 113 | statutory or otherwise, including without limitation warranties of 114 | title, merchantability, fitness for a particular purpose, non 115 | infringement, or the absence of latent or other defects, accuracy, or 116 | the present or absence of errors, whether or not discoverable, all to 117 | the greatest extent permissible under applicable law. 118 | c. Affirmer disclaims responsibility for clearing rights of other persons 119 | that may apply to the Work or any use thereof, including without 120 | limitation any person's Copyright and Related Rights in the Work. 121 | Further, Affirmer disclaims responsibility for obtaining any necessary 122 | consents, permissions or other rights required for any use of the 123 | Work. 124 | d. Affirmer understands and acknowledges that Creative Commons is not a 125 | party to this document and has no duty or obligation with respect to 126 | this CC0 or use of the Work. 127 | 128 | 129 | =========================================================================== 130 | 131 | Grant of Patent License 132 | 133 | "License" shall mean the terms and conditions for use, reproduction, and 134 | distribution. 135 | 136 | "Licensor" shall mean the original copyright owner or entity authorized by 137 | the original copyright owner that is granting the License. 138 | 139 | "Legal Entity" shall mean the union of the acting entity and all other 140 | entities that control, are controlled by, or are under common control with 141 | that entity. For the purposes of this definition, "control" means (i) the 142 | power, direct or indirect, to cause the direction or management of such 143 | entity, whether by contract or otherwise, or (ii) ownership of fifty 144 | percent (50%) or more of the outstanding shares, or (iii) beneficial 145 | ownership of such entity. 146 | 147 | "You" (or "Your") shall mean an individual or Legal Entity exercising 148 | permissions granted by this License. 149 | 150 | "Source" form shall mean the preferred form for making modifications, 151 | including but not limited to software source code, documentation source, 152 | and configuration files. 153 | 154 | "Object" form shall mean any form resulting from mechanical transformation 155 | or translation of a Source form, including but not limited to compiled 156 | object code, generated documentation, and conversions to other media types. 157 | 158 | "Work" shall mean the work of authorship, whether in Source or Object form, 159 | made available under the License, as indicated by a copyright notice that 160 | is included in or attached to the work. 161 | 162 | "Derivative Works" shall mean any work, whether in Source or Object form, 163 | that is based on (or derived from) the Work and for which the editorial 164 | revisions, annotations, elaborations, or other modifications represent, as 165 | a whole, an original work of authorship. For the purposes of this License, 166 | Derivative Works shall not include works that remain separable from, or 167 | merely link (or bind by name) to the interfaces of, the Work and 168 | Derivative Works thereof. 169 | 170 | "Contribution" shall mean any work of authorship, including the original 171 | version of the Work and any modifications or additions to that Work or 172 | Derivative Works thereof, that is intentionally submitted to Licensor for 173 | inclusion in the Work by the copyright owner or by an individual or Legal 174 | Entity authorized to submit on behalf of the copyright owner. For the 175 | purposes of this definition, "submitted" means any form of electronic, 176 | verbal, or written communication sent to the Licensor or its 177 | representatives, including but not limited to communication on electronic 178 | mailing lists, source code control systems, and issue tracking systems that 179 | are managed by, or on behalf of, the Licensor for the purpose of discussing 180 | and improving the Work, but excluding communication that is conspicuously 181 | marked or otherwise designated in writing by the copyright owner as "Not a 182 | Contribution." 183 | 184 | "Contributor" shall mean Licensor and any individual or Legal Entity on 185 | behalf of whom a Contribution has been received by Licensor and 186 | subsequently incorporated within the Work. 187 | 188 | Each Contributor hereby grants to You a perpetual, worldwide, 189 | non-exclusive, no-charge, royalty-free, irrevocable (except as stated in 190 | this section) patent license to make, have made, use, offer to sell, sell, 191 | import, and otherwise transfer the Work, where such license applies only to 192 | those patent claims licensable by such Contributor that are necessarily 193 | infringed by their Contribution(s) alone or by combination of their 194 | Contribution(s) with the Work to which such Contribution(s) was submitted. 195 | If You institute patent litigation against any entity (including a 196 | cross-claim or counterclaim in a lawsuit) alleging that the Work or a 197 | Contribution incorporated within the Work constitutes direct or 198 | contributory patent infringement, then any patent licenses granted to You 199 | under this License for that Work shall terminate as of the date such 200 | litigation is filed. 201 | --------------------------------------------------------------------------------