Vous êtes sur la page 1sur 11

Introduction

A sales order is a document that specifies products and/or services


ordered by a specific business partner (customer), as well as the price
and terms and conditions.
The Sales Order window allows to register sales related documents with
different purposes which is regulated by the Transaction
Document field. Depending on the chosen value, the consequences when
booking the sales order will be different. These are the types of sales
order documents that are available:
Standard Order. When the transaction document is standard upon
booking of the document there is no additional documents created.
Goods shipment and sales invoice still have to be created (compare
it with the below documents)

POS Order. The Point of Sale order is for the situation when a customer walks into a shop, orders a product, pays
for it and takes the product home. Upon booking of the sales order with this document type, the shipment and the
sales invoice are created automatically.

Warehouse Order. A warehouse order is used for the situation where the good shipment takes place at the time
that the sales order is booked (for example, customer is taking goods right away directly from the warehouse).




DESCRIPTION

ORDER MANAGEMENT
The Order Management process covers the business processes required for the creation of a quotation for a prospect or customer,
sales order management, invoicing and the receipt of cash. The functionality is tightly integrated with Materials Management and
Customer Relationship Management.
Compiere is preconfigured to handle a number of sales order scenarios. System administrators can add new sales order types or
change the rules associated with existing orders to match specific requirements.

Sales Orders
A Sales Order is the "fulfillment control document" that is the foundation for generating sales order, shipment and invoicing
documentation. In addition, Vendor Purchase Orders may be created automatically for the items specified on a sales order and directly
shipped to the customer if appropriate.
Different types of sales orders cause different business process behavior in Compiere. For example, a "Prepaid Order" will not allow
shipments until payment occurs. A "Point of Sale" order assumes the customer is at the counter with the goods in hand and generates
all transactions including stock decrement, invoicing, and payment through the entry of a single document. A "Standard Order" by
comparison, will check availability before accepting the order then queue the order for fulfillment by the warehouse and then generate
an invoice in the next invoice run or otherwise in accordance with the invoice rules for that customer.
Compiere supports the following Sales Order Situations:
Standard Order This is used when shipping products by availability. Users can generate the invoice immediately or after the
shipment.
POS Order This is used in 'over the counter' sales situations with anonymous customers. The order generates the shipment and
invoice. The payment is received via Cash, Check, Credit Card, etc.
Credit Order This is used for known (on account) customers, with or without a credit line. The order generates the shipment, invoice,
and optionally receives the payment.
Warehouse Order This is used when creating summary invoices. Users can select the shipments manually or create the invoice
based on invoicing rules (e.g. weekly, on the 1st and 15th of a month, etc.).
Prepay Order This is used in Web Store Transactions. Users can send the shipment and generate the final invoice after receipt of the
money.






Customer Invoices


Generate invoices according to general business rules or based on specific arrangements in place with the customer. Generate
invoices:
Immediately after each shipment.
When the order is completely shipped.
Based on a predefined invoice schedule specific to the customer.
For example, an invoice schedule could be established to arrange for the creation of a summary invoice including all
shipments to the customer over the previous day, week, or month.

Implementation

The impact of implementing a project management, time-recording, work-in-progress and invoicing system can be far reaching. Our
implementation methodology has been developed to help our clients through the system delivery process.
The purpose of this structured approach is to give you an outline of the Timemaster implementation process. We have summarized the
stages below and given a brief description of what takes place at each stage. The average Timemaster implementation is five days,
including consultancy, technical installation and training, comprising of these stages:
1. New Client Information document
After the Timemaster contracts are signed by both parties Equisys will complete a New Client Information document for you. This will
consist of information about your company, who our contacts are, which Timemaster licenses you have purchased and your estimated go
live date. This document will be circulated to all of the relevant contacts at Equisys who will be involved in your implementation.
2. Delivery to customer of Timemaster data import spreadsheet
This spreadsheet will contain all of the information to be imported from your current system into Timemaster. For example, this will
include your static data such as staff details and customer details, plus your on-going project data. At this stage we would recommend
that you take a look at the spreadsheet and familiarize yourself with the information that will be required. Some of the requested data
will be unfamiliar to you, but don't worry as this will be covered during the next stages of your implementation.
3. Discovery workshop
This is a half day workshop led by our Timemaster Consultant either remotely, or onsite depending on location and preference. The aim
of this workshop is to determine your exact requirements for Timemaster. Our Timemaster Consultant will work through a series of
questions and discussions around a number of topics including some general company information and the Timemaster modules that you
have purchased. We may ask you for some information in preparation for this scoping workshop, such as your company structure and
hierarchy of Timemaster users.
4. Scoping and delivery plan
A personalized scoping and delivery plan is produced as part of the discovery workshop. This document will include all of the answers
from your discovery day, and will map out your exact requirements. We will also include an accurate number of the training days you will
require based on the information provided. It could be determined that you require some additional development work for bespoke
reporting, account package integration or invoice template creation. Timescales and costs will be agreed before installation commences
and details will be included in your scoping and delivery plan. This document needs to be agreed and signed off by you before we can
progress with your implementation.

5. Timemaster data import spreadsheet completion
Using the information gathered during your scoping workshop you will need to complete the Timemaster import spreadsheet; we will
assist with this as required. Once complete, this is now ready to import into your new Timemaster database.
6. Technical installation including setup of initial database
A Timemaster installation engineer will perform either a remote installation, or they will aid your internal technical department if you are
deploying Timemaster on premise. If we are hosting Timemaster for you, we will set up the database and import your data. The technical
installation typically takes half a day.
7. Commencement of training days
Your training days will commence on a mutually agreeable day. These days can include a mixture of onsite and remote training, and are
chargeable once completed on a half or full-day basis. The average number of training required is three days, usually spaced out over a
number of weeks to give you time to familiarize yourself with each stage of the software. A standard training breakdown is listed below:-
Day 1 - Creating new projects, time and expenses, timesheet approval
Day 2 - Resource planning including estimating, absence management, reporting options
Day 3 - WIP and invoicing
8. User Acceptance
After the completion of each training day, the customer signs off our Timemaster delivery plan, in order to feel confident that all relevant
areas have been covered during the training and any comments or additional queries will be noted.





Future Enhanced Intercompany Invoicing for Internal Sales Orders
Setup
You can generate Intercompany Invoices for Internal Sales Orders which have a
Transfer Type of "Intransit." In order to use this feature:
Setup Intercompany Invoicing See the Oracle Advanced Pricing
Implementation Guide and the Oracle Inventory User's Guide for more
information.
Set the profile option INV: Intercompany Invoice for Internal Orders to "Yes."
This profile option can be set at the site level and has a Default value of "No."
If you have Advanced Pricing installed you can derive the intercompany invoice price
for an item:



Set the profile option INV: Intercompany Invoice for Internal Orders to "Yes."
This profile option can be set at the site level and has a Default value of "No."
Set the profile option INV: Advanced Pricing for Intercompany Invoicing to
"Yes." This profile option can be set at the site level.


HARDWARE REQUIREMENT

1-40GB/HD
2-2GBRAM
3-PROCESSOR(p4)
4-PRINTER

SOFTWARE REQUIREMENT

1-VISUAL STNELS 2013
2-MSSQL 2008
3-XML
BIBLOGRAPH
1-W3school.com
2-dynamic drive.com
3Asp.net
4-java script

Featured Documents related to data flow diagram of sales
order processing system


Register to access your free content from TEC and more!
First Name

Last Name

Company Email



Company

Telephone



Please sele

select

Please se

select



Send me the TEC Newsletter
Generate New Image
Type the code above
Documents related to data flow diagram of sales order processing system


Data Flow Diagrams
Company
Customer
Despatch
Note +
Goods
Order
Rejected
Order
Context Diagram


Sales
Check Credit
Rating
3
Unique Number Where its done
Whats done
Output Data
Input
Data
The Process Symbol

The Place of Data Flow Modelling
D
e
c
i
s
i
o
n

S
t
r
u
c
t
u
r
e
P
o
l
i
c
i
e
s

a
n
d

P
r
o
c
e
d
u
r
e
s
U
s
e
r

O
r
g
a
n
i
s
a
t
i
o
n
Investigation
Construction
Specification
Conceptual Model
Internal design
External
Design
BAM
RD
WPM
DFM
LDM
B
S
O



1 Order Stock
Purchase Order
Cabinet
M1
Manager
e
Stock
File
M2
*
Produce
Stock
List
1.1
*
Record
Purchase
Order
1.2
Stock List
Purchase Order
Purchase Order
Stock List
Data Flow Diagrams
Decomposing Data Flow Diagrams


Conclusion

Solutions - Invoicing & Sales Order ProcessingThis comprehensive Invoicing module can
generate Invoices, Credit Notes, Quotations, Proforma's and Sales Orders. Booksolve will
personalise your invoices to your requirements and include your own branding. The
highlights of this module are:-

Create Invoices, Credit Notes, Quotations, Profromas and Sales Orders
Capture customer orders and the system will manage and combine picking some
lines from stock and ordering shortfalls from the supplier
An invoice layout which includes your branding and can be customised to meet your
requirements
Up to four layouts are available for customisation, this can be invaluable if you deal
with library suppliers who have specific requests. Discuss your requirements with our
sales manager
Automatically record customer dues so orders can be cancelled automatically if not in
stock
Links into Booksolve websites for the automatic download of customer web orders
Links into Accounts packages
For multiple branches you can use the module in conjunction with the EDI modules to
move stock around the business keeping a useful audit