Order Management Basis Setups

Oracle Order Management Setups

Oracle Order management is one of the most important part of the oracle EBS. The Order Management Application provides many flexible features enabling you to set up your system to begin processing order information. These orders can be created in Oracle Order Management Suite as well as in some other front-desk application. We can integrate these applications with Oracle Order Management for keeping a controlled track of orders and proper business flow. We can create different types of orders using this application can be for inventory stock items or for services.
You must define your business order policies, such as how you classify your orders, as well as various control features prior to processing orders within the application.

Important Setup Steps for Order Management

Click on the links to go to individual setup steps

Step	Optional or Required
1. Define multiple organizations in Oracle Inventory	required
2. Setup Multi-Org (Multiple Organization) Access Control	optional
3. Define key and descriptive flexfields	required under certain conditions
4. Define inventory organizations (warehouses), parameters, subinventories, and picking rules in Oracle Inventory	required
5. Define Profiles	required
6. Setting OM System Parameters	required
7. Define invoicing information, Payment Terms	required under certain conditions
8. Define your sales representatives	optional
9. Define Tax Features	required
10. Define Quickcodes	required under certain conditions
11. Define header and line processing flows	required
12. Define Document Sequences for Order Numbering	required
13. Define Order Import Sources	required under certain conditions
14. Define the units of measure	required
15. Define item information	required
16. Define the items that you sell	required
17. Define the configurations that you sell	required under certain conditions
18. Define price lists	required
19. Define customer profile classes	required under certain conditions
20.Define information on your customers	required
21. Define item cross references	required under certain conditions
22. Define your sourcing rules	optional
23. Define Order Management Transaction Types	required
24. Set up Cost of Goods Sold Accounting flexfield combination	required under certain conditions
25. Define Processing Constraints	optional
26. Define Defaulting Rules	optional
27.Define Credit Checking Rules	required under certain conditions
28. Define Automatic Holds	required under certain conditions
29. Define Attachments	optional
30. Define Freight and Special Charge Types	optional
31. Define shipping parameters	required

Basic Steps and Programs Run during Order to Cash Cycle

1. Enter Order in OM (Customer, Order type, Pricelist, shipping details, etc)
2. Enter the Items details and sourcing details in Order Line
3. Check for the availability and Book the Order
4. Schedule and Reserve the Order
5. Pick Release the Order (Reports here: Pick Selection List Generation, Pick Slip Report, Shipping Exception Report)
6. Ship confirm the order in Shipping transaction form (Reports here: Bill Of Ladding, Packing Slip Report, Commercial Invoice, Vehicle Load Sheet Details, Interface Trip Stop)
7. Line Status become Interfaced in Shipping Transaction form
8. Sales Order Line status will be Shipped
9. Run Workflow Background Concurrent request to close the workflow which in turn will close the order line.
10. This will trigger Autoinvoice Master program (inturn it will run Autoinvoice Import Program)
11. Then will trigger Prepayment Matching Program
12. Invoice (Transaction#) can be found in Account Receivables
13. After getting the Cash from customer, Create the Receipt.
14. After creation of the receipt, match the receipt with the invoice transaction
15. Once the receipt is matched, then the data can be transferred to General Ledger by running General ledger Transfer Program.
16. Then Journal can be Imported in GL by Import Journals
17. Then Journals can be posted to GL by Post Journals.

Order to Cash Lifecycle: Party

Party:

In business transactions, various players participate in the purchase and sale of product or services. A party refers to an entity involved in such business transactions. It can be an organization, a person or a relationship.

A party is an entity which can enter into business with another party.

A party is defined by its information and not by relationships with other parties. E.g. the name Vision Corporation is part of the definition of a party with the organization party type.

A relationship is defined by the characteristics or terms and condition of that relationship. The definition of a party is independent of its relationship. E.g. a party, named Jeremy Smith, with the party type of Person exists independent of any relationship entered by Jeremy Smith.

Party Site:

A party site is the location linked to a party indicating that the party’s usage of location.

A location is a point in geographical space described by a street address.

A Party Relationship is a binary relationship between two parties such as a partnership.

A contact point is a means of contacting a party. E.g. the contact numbers, email address of a party.

 

Customer:

A customer is an organization or a person with whom you have a selling relationship.

This relationship can result from purchasing or products and services or from the negotiation of terms and conditions that provides the basis for future purchases.

A customer account represents the business relationship that a party can enter into with another party.

Customer Account:

This contains the terms and conditions for doing business. E.g. if a division of Vision Distribution is a customer, then you can open a commercial account for purchases to be made for its internal use. You can also open a reseller account for purchases made for sales of your products to end users.

You can create multiple customer accounts for a party to maintain information about categories of business activities. E.g. to track invoices for different types of purchases, you can maintain two accounts, one for purchasing office supplies and another for purchasing furniture.

You can also maintain multiple accounts for a customer that transacts with more than one line of business in your organization. For this, you maintain separate customer profiles, addresses, and contacts for each customer accounts.

Contact:

A contact communicates for or acts on behalf of a party or a customer account.

A contact can exist for a customer at the account or the address level.

A person usually acts as a contact for an organization but at the same time can also be a contact for another person, e.g. an administrative assistant can be a contact for an executive.

Party Registry:

This stores information about relationships between parties, such as organizational hierarchies, business relationships, personal relationships, and organizational contacts.

This also stores the reciprocal data for the relationships.

Party Model:

In the party model, a single record represents both a prospect and a customer. Till the time, the customer terms are established, the record represents a prospect. After the terms are recorded, the same record represents the entity as your customer. So there are no separate lists to maintain and reconcile.

Each Application uses different features of the party model. For instance, the customer relationship management (CRM) suite application use more details about party relationships and new prospects. The receivables and order management use more of the customer accounts.

The Party model contains a unique set of information about a person, organization or relationship. The tables store information such as parties, addresses and bank accounts. You can interact with the party model through customer forms, party interfaces, or party and customer account merge.

Customer forms are used for online entry and query of customer account information.

Party Interface is used for batch load of party information.

Party and customer account merge is used if a party is entered incorrectly, in duplicate or due to a business consolidation.

Order to Cash Lifecycle: Party

Party:

In business transactions, various players participate in the purchase and sale of product or services. A party refers to an entity involved in such business transactions. It can be an organization, a person or a relationship.

A party is an entity which can enter into business with another party.

A party is defined by its information and not by relationships with other parties. E.g. the name Vision Corporation is part of the definition of a party with the organization party type.

A relationship is defined by the characteristics or terms and condition of that relationship. The definition of a party is independent of its relationship. E.g. a party, named Jeremy Smith, with the party type of Person exists independent of any relationship entered by Jeremy Smith.

Party Site:

A party site is the location linked to a party indicating that the party’s usage of location.

A location is a point in geographical space described by a street address.

A Party Relationship is a binary relationship between two parties such as a partnership.

A contact point is a means of contacting a party. E.g. the contact numbers, email address of a party.

 

Customer:

A customer is an organization or a person with whom you have a selling relationship.

This relationship can result from purchasing or products and services or from the negotiation of terms and conditions that provides the basis for future purchases.

A customer account represents the business relationship that a party can enter into with another party.

Customer Account:

This contains the terms and conditions for doing business. E.g. if a division of Vision Distribution is a customer, then you can open a commercial account for purchases to be made for its internal use. You can also open a reseller account for purchases made for sales of your products to end users.

You can create multiple customer accounts for a party to maintain information about categories of business activities. E.g. to track invoices for different types of purchases, you can maintain two accounts, one for purchasing office supplies and another for purchasing furniture.

You can also maintain multiple accounts for a customer that transacts with more than one line of business in your organization. For this, you maintain separate customer profiles, addresses, and contacts for each customer accounts.

Contact:

A contact communicates for or acts on behalf of a party or a customer account.

A contact can exist for a customer at the account or the address level.

A person usually acts as a contact for an organization but at the same time can also be a contact for another person, e.g. an administrative assistant can be a contact for an executive.

Party Registry:

This stores information about relationships between parties, such as organizational hierarchies, business relationships, personal relationships, and organizational contacts.

This also stores the reciprocal data for the relationships.

Party Model:

In the party model, a single record represents both a prospect and a customer. Till the time, the customer terms are established, the record represents a prospect. After the terms are recorded, the same record represents the entity as your customer. So there are no separate lists to maintain and reconcile.

Each Application uses different features of the party model. For instance, the customer relationship management (CRM) suite application use more details about party relationships and new prospects. The receivables and order management use more of the customer accounts.

The Party model contains a unique set of information about a person, organization or relationship. The tables store information such as parties, addresses and bank accounts. You can interact with the party model through customer forms, party interfaces, or party and customer account merge.

Customer forms are used for online entry and query of customer account information.

Party Interface is used for batch load of party information.

Party and customer account merge is used if a party is entered incorrectly, in duplicate or due to a business consolidation.

Order to Cash Cycle Step by step hands on

Order to Cash Cycle

Following are the steps the process will go through from creating a Sales Order to Posting the details in GL.

·         Enter the Sales Order

·         Book the Sales Order

·         Launch Pick Release

·         Ship Confirm

·         Create Invoice

·         Create the Receipts either manually or using Auto Lockbox ( In this article we will concentrate on Manual creation)

·         Transfer to General Ledger

·         Journal Import

·         Posting

Involved Modules

Order Management: Creating and shipping the Order

Inventory:  Onhand availability, Reservation

Receivables: For Receipt against invoice

General Ledger: Importing, entering and posting the journals.

Enter the Sales Order:

Order Management Super User Operations (USA)>Orders Returns >Sales Orders

Enter the Customer details (Ship to and Bill to address), Order type.

Click on Lines Tab. Enter the Item to be ordered and the quantity required

Line is scheduled automatically when the Line Item is saved.

Scheduling/unscheduling can be done manually by selecting Schedule/Un schedule from the Actions Menu.

You can check if the item to be ordered is available in the Inventory by clicking on Availability Button.

Save the work.

Tables Affected:

OE_ORDER_HEADERS_ALL

OE_ORDER_LINES_ALL

Columns used for identification of flow

FLOW_STATUS_CODE in both the tables which is ENTERED.

Book the Sales Order

Book the Order by clicking on the Book Order button

Now that the Order is BOOKED, the status on the header is change accordingly.

Tables affected:

The FLOW_STATUS_CODE in the table OE_ORDER_HEADERS_ALL would be BOOKED.

The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will be AWAITING_SHIPPING.

New records will be created in WSH_DELIVERY_DETAILS with RELEASED_STATUS=’R’ (Ready to Release)

Also Record(s) will be inserted into WSH_DELIVERY_ASSIGNMENTS

At the same time DEMAND INTERFACE PROGRAM runs in the background and inserts into MTL_DEMAND.

Launch Pick Release

Shipping > Release Sales Order > Release Sales Orders

Give the Sales Order and Rule details as required

Key in the details in Shipping Tab, Autocreate Delivery: Yes, Auto Pick Confirm: Yes, Autopack Delivery: Yes

Similarly key in the Subinventory, location and org details in Inventory tab as required

Then select Execute Now button.

On completion this will show below window

Pick Release process will in turn run few more concurrent requests like

Auto Pack Report, Pick Slip Report, Shipping Exceptions Report (These are what we have chosen in the shipping tab during Pick Release)

Tables Affected

If Autocreate Delivery is set to ‘Yes’ then a new record is created in the table WSH_NEW_DELIVERIES

DELIVERY_ID is populated in the table WSH_DELIVERY_ASSIGNMENTS

The RELEASED_STATUS in WSH_DELIVERY_DETAILS would be now set to ‘Y’ (Pick Confirmed) if Auto Pick Confirm is set to Yes otherwise RELEASED_STATUS is ‘S’ (Release to Warehouse)

Pick Confirm the Order:

If Auto Pick Confirm is set to Yes during Pick Release, then this process will happen systematically.

In other cases, need to do this by doing a move order transaction

Inventory Super User > Move Order> Transact Move Order

Take the Move Order Number form the Shipping Transaction Form and find that and transact.

Ship Confirm the Order:

Order Management Super User>Shipping >Transactions

Find by Order Number

Here you can find all the details

If the line status is Staged/Pick Confirmed, we can go for a shipment

Then Click on the Delivery tab

Then Click Ship Confirm

Note: If Ship Confirm button is inactive, then please check to the user id you are logged in, whether Shipping Grant given or not. If not they add a shipping grant to the user id and try again.

Then OK.

The Status in Shipping Transaction form in Delivery tab should be closed

This will kick off concurrent programs like.INTERFACE TRIP Stop, Commercial Invoice, Packing Slip Report, Bill of Lading

Tables Affected:

RELEASED_STATUS in WSH_DELIVERY_DETAILS would be ‘C’ (Ship Confirmed)

FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL would be “BOOKED“

FLOW_STATUS_CODE in OE_ORDER_LINES_ALL would be “SHIPPED“

Once all background process completes, the Shipping Transaction Status in Lines/LPNs tab becomes Interfaced

Create Invoice:

Run workflow background Process

Order Management >view >Requests

Workflow Background Process inserts the records RA_INTERFACE_LINES_ALL with

INTERFACE_LINE_CONTEXT     =     ’ORDER ENTRY’

INTERFACE_LINE_ATTRIBUTE1=     Order_number

INTERFACE_LINE_ATTRIBUTE3=     Delivery_id

And spawns Auto invoice Master Program and Auto invoice import program which creates Invoice for that particular Order 

Check the Invoice:

The Invoice created can be seen using the Receivables responsibility

Receivables Super User> Transactions> Transactions

Query with the Order Number as Reference

Affected Tables:

RA_CUSTOMER_TRX_ALL will have the Invoice header information. The column INTERFACE_HEADER_ATTRIBUTE1 will have the Order Number. 

RA_CUSTOMER_TRX_LINES_ALL will have the Invoice lines information. The column INTERFACE_LINE_ATTRIBUTE1 will have the Order Number.

Create receipt: Receivables> Receipts> Receipts

Click Apply to apply this to an invoice and then select the invoice in next screen and then apply.

Tables affected:

AR_CASH_RECEIPTS_ALL

Transfer to General Ledger:

To transfer the Receivables accounting information to general ledger, run General Ledger Transfer Program

Receivables> View Requests

Parameters:

• Give in the Start date and Post through date to specify the date range of the transactions to be transferred.
• Specify the GL Posted Date, defaults to SYSDATE.
• Post in summary: This controls how Receivables creates journal entries for your transactions in the interface table. If you select ‘No’, then the General Ledger Interface program creates at least one journal entry in the interface table for each transaction in your posting submission. If you select ‘Yes’, then the program creates one journal entry for each general ledger account.
• If the Parameter Run Journal Import is set to ‘Yes’, the journal import program is kicked off automatically which transfers journal entries from the interface table to General Ledger, otherwise follow the topic Journal Import to import the journals to General Ledger manually.

Tables Affected:

GL_INTERFACE

Journal Import:

To transfer the data from General Ledger Interface table to General Ledger, run the Journal Import program from Oracle General Ledger.

General Ledger > Journal> Import> Run

Parameters:

• Select the appropriate Source.
• Enter one of the following Selection Criteria:

No Group ID: To import all data for that source that has no group ID. Use this option if you specified a NULL group ID for this source.

All Group IDs: To import all data for that source that has a group ID. Use this option to import multiple journal batches for the same source with varying group IDs.

Specific Group ID: To import data for a specific source/group ID combination. Choose a specific group ID from the List of Values for the Specific Value field.

If you do not specify a Group ID, General Ledger imports all data from the specified journal entry source, where the Group_ID is null.

• Define the Journal Import Run Options (optional)

Choose Post Errors to Suspense if you have suspense posting enabled for your set of books to post the difference resulting from any unbalanced journals to your suspense account.

Choose Create Summary Journals to have journal import create the following:

• one journal line for all transactions that share the same account, period, and currency and that has a debit balance

• One journal line for all transactions that share the same account, period, and currency and that has a credit balance.

• Enter a Date Range to have General Ledger import only journals with accounting dates in that range. If you do not specify a date range, General Ledger imports all journals data.
• Choose whether to Import Descriptive Flexfields, and whether to import them with validation.

Click on Import button

Affected tables

GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES

Posting:

We have to Post journal batches that we have imported previously to update the account balances in General Ledger

General Ledger> Journals > Enter

Click Find

From the list of unposted journals displayed, select one journal at a time and click on Post button to post the journal.

If you know the batch name to be posted you can directly post using the Post window

Order to Cash Cycle Step by step hands on

Order to Cash Cycle

Following are the steps the process will go through from creating a Sales Order to Posting the details in GL.

·         Enter the Sales Order

·         Book the Sales Order

·         Launch Pick Release

·         Ship Confirm

·         Create Invoice

·         Create the Receipts either manually or using Auto Lockbox ( In this article we will concentrate on Manual creation)

·         Transfer to General Ledger

·         Journal Import

·         Posting

Involved Modules

Order Management: Creating and shipping the Order

Inventory:  Onhand availability, Reservation

Receivables: For Receipt against invoice

General Ledger: Importing, entering and posting the journals.

Enter the Sales Order:

Order Management Super User Operations (USA)>Orders Returns >Sales Orders

Enter the Customer details (Ship to and Bill to address), Order type.

Click on Lines Tab. Enter the Item to be ordered and the quantity required

Line is scheduled automatically when the Line Item is saved.

Scheduling/unscheduling can be done manually by selecting Schedule/Un schedule from the Actions Menu.

You can check if the item to be ordered is available in the Inventory by clicking on Availability Button.

Save the work.

Tables Affected:

OE_ORDER_HEADERS_ALL

OE_ORDER_LINES_ALL

Columns used for identification of flow

FLOW_STATUS_CODE in both the tables which is ENTERED.

Book the Sales Order

Book the Order by clicking on the Book Order button

Now that the Order is BOOKED, the status on the header is change accordingly.

Tables affected:

The FLOW_STATUS_CODE in the table OE_ORDER_HEADERS_ALL would be BOOKED.

The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will be AWAITING_SHIPPING.

New records will be created in WSH_DELIVERY_DETAILS with RELEASED_STATUS=’R’ (Ready to Release)

Also Record(s) will be inserted into WSH_DELIVERY_ASSIGNMENTS

At the same time DEMAND INTERFACE PROGRAM runs in the background and inserts into MTL_DEMAND.

Launch Pick Release

Shipping > Release Sales Order > Release Sales Orders

Give the Sales Order and Rule details as required

Key in the details in Shipping Tab, Autocreate Delivery: Yes, Auto Pick Confirm: Yes, Autopack Delivery: Yes

Similarly key in the Subinventory, location and org details in Inventory tab as required

Then select Execute Now button.

On completion this will show below window

Pick Release process will in turn run few more concurrent requests like

Auto Pack Report, Pick Slip Report, Shipping Exceptions Report (These are what we have chosen in the shipping tab during Pick Release)

Tables Affected

If Autocreate Delivery is set to ‘Yes’ then a new record is created in the table WSH_NEW_DELIVERIES

DELIVERY_ID is populated in the table WSH_DELIVERY_ASSIGNMENTS

The RELEASED_STATUS in WSH_DELIVERY_DETAILS would be now set to ‘Y’ (Pick Confirmed) if Auto Pick Confirm is set to Yes otherwise RELEASED_STATUS is ‘S’ (Release to Warehouse)

Pick Confirm the Order:

If Auto Pick Confirm is set to Yes during Pick Release, then this process will happen systematically.

In other cases, need to do this by doing a move order transaction

Inventory Super User > Move Order> Transact Move Order

Take the Move Order Number form the Shipping Transaction Form and find that and transact.

Ship Confirm the Order:

Order Management Super User>Shipping >Transactions

Find by Order Number

Here you can find all the details

If the line status is Staged/Pick Confirmed, we can go for a shipment

Then Click on the Delivery tab

Then Click Ship Confirm

Note: If Ship Confirm button is inactive, then please check to the user id you are logged in, whether Shipping Grant given or not. If not they add a shipping grant to the user id and try again.

Then OK.

The Status in Shipping Transaction form in Delivery tab should be closed

This will kick off concurrent programs like.INTERFACE TRIP Stop, Commercial Invoice, Packing Slip Report, Bill of Lading

Tables Affected:

RELEASED_STATUS in WSH_DELIVERY_DETAILS would be ‘C’ (Ship Confirmed)

FLOW_STATUS_CODE in OE_ORDER_HEADERS_ALL would be “BOOKED“

FLOW_STATUS_CODE in OE_ORDER_LINES_ALL would be “SHIPPED“

Once all background process completes, the Shipping Transaction Status in Lines/LPNs tab becomes Interfaced

Create Invoice:

Run workflow background Process

Order Management >view >Requests

Workflow Background Process inserts the records RA_INTERFACE_LINES_ALL with

INTERFACE_LINE_CONTEXT     =     ’ORDER ENTRY’

INTERFACE_LINE_ATTRIBUTE1=     Order_number

INTERFACE_LINE_ATTRIBUTE3=     Delivery_id

And spawns Auto invoice Master Program and Auto invoice import program which creates Invoice for that particular Order 

Check the Invoice:

The Invoice created can be seen using the Receivables responsibility

Receivables Super User> Transactions> Transactions

Query with the Order Number as Reference

Affected Tables:

RA_CUSTOMER_TRX_ALL will have the Invoice header information. The column INTERFACE_HEADER_ATTRIBUTE1 will have the Order Number. 

RA_CUSTOMER_TRX_LINES_ALL will have the Invoice lines information. The column INTERFACE_LINE_ATTRIBUTE1 will have the Order Number.

Create receipt: Receivables> Receipts> Receipts

Click Apply to apply this to an invoice and then select the invoice in next screen and then apply.

Tables affected:

AR_CASH_RECEIPTS_ALL

Transfer to General Ledger:

To transfer the Receivables accounting information to general ledger, run General Ledger Transfer Program

Receivables> View Requests

Parameters:

• Give in the Start date and Post through date to specify the date range of the transactions to be transferred.
• Specify the GL Posted Date, defaults to SYSDATE.
• Post in summary: This controls how Receivables creates journal entries for your transactions in the interface table. If you select ‘No’, then the General Ledger Interface program creates at least one journal entry in the interface table for each transaction in your posting submission. If you select ‘Yes’, then the program creates one journal entry for each general ledger account.
• If the Parameter Run Journal Import is set to ‘Yes’, the journal import program is kicked off automatically which transfers journal entries from the interface table to General Ledger, otherwise follow the topic Journal Import to import the journals to General Ledger manually.

Tables Affected:

GL_INTERFACE

Journal Import:

To transfer the data from General Ledger Interface table to General Ledger, run the Journal Import program from Oracle General Ledger.

General Ledger > Journal> Import> Run

Parameters:

• Select the appropriate Source.
• Enter one of the following Selection Criteria:

No Group ID: To import all data for that source that has no group ID. Use this option if you specified a NULL group ID for this source.

All Group IDs: To import all data for that source that has a group ID. Use this option to import multiple journal batches for the same source with varying group IDs.

Specific Group ID: To import data for a specific source/group ID combination. Choose a specific group ID from the List of Values for the Specific Value field.

If you do not specify a Group ID, General Ledger imports all data from the specified journal entry source, where the Group_ID is null.

• Define the Journal Import Run Options (optional)

Choose Post Errors to Suspense if you have suspense posting enabled for your set of books to post the difference resulting from any unbalanced journals to your suspense account.

Choose Create Summary Journals to have journal import create the following:

• one journal line for all transactions that share the same account, period, and currency and that has a debit balance

• One journal line for all transactions that share the same account, period, and currency and that has a credit balance.

• Enter a Date Range to have General Ledger import only journals with accounting dates in that range. If you do not specify a date range, General Ledger imports all journals data.
• Choose whether to Import Descriptive Flexfields, and whether to import them with validation.

Click on Import button

Affected tables

GL_JE_BATCHES, GL_JE_HEADERS, GL_JE_LINES

Posting:

We have to Post journal batches that we have imported previously to update the account balances in General Ledger

General Ledger> Journals > Enter

Click Find

From the list of unposted journals displayed, select one journal at a time and click on Post button to post the journal.

If you know the batch name to be posted you can directly post using the Post window

Order to Cash Lifecycle: Processes

Order to Cash Cycle

The Life Cycle of the Order

Following are the steps the process will go through from creating a Sales Order to Posting the details in GL.

·         Enter the Sales Order

·         Book the Sales Order

·         Launch Pick Release

·         Ship Confirm

·         Create Invoice

·         Create the Receipts either manually or using Auto Lockbox ( In this article we will concentrate on Manual creation)

·         Transfer to General Ledger

·         Journal Import

·         Posting

Applications Involved

Order Management: Creating and shipping the Order

Customer Master for customer details in OM

Inventory:  Onhand availability, Reservation

Pricing for List Price details in OM line

Receivables: For Receipt against invoice

General Ledger: Importing, entering and posting the journals.

Order Management Processes:

Orders can be created in following processes

1.       Enter Order manually

2.       Copy and Order or Return

3.       Import Orders from CRM or other legacy systems

Note: CRM (Customer Relationship Management) includes iServe, iStore, Teleservices, Telesales, Sales Online, iSupport.

Scheduling Process:

1.       Checking Available to Promise (ATP)

2.       Placing Demand

3.       Reserving Onhand

4.       Running Pick Release

5.       Shipping the Order

Pricing Process:

1.       Order line entered, take the part and customer details from Order

2.       Check price list or agreement

3.       Check for the modifiers

4.       Calculates the unit price

Shipping Process:

1.       Run Pick Release creates Move Order

2.       As per the Move Order details, parts moved out of the Subinventory (Transact Move Order)

3.       After getting the part from Subinventory, it will be dropped to Staging area (Pick Confirm, this runs automatically during Pick Release)

4.       After loading the goods into the Truck from Staging area, Ship Confirm can be run

5.       This ship confirm will decrement quantity from Inventory and update the sales order

6.       The information can be transferred to Receivables through AutoInvoice program and will generate the invoice for customer.

AutoInvoice Process:

1.       Transaction data can be transferred from a number of locations like Order Management, Contracts and Legacy Systems

2.       Data are brought to the Interface table, if any error, that will move to Interface exception table and after correction, again will be brought to the interface table

3.       Correct data gets inserted to the Receivables by AutoInvoice program. This can be related to Debit Memos, Memos and as Invoices

Receivable Process:

1.       Imported Invoices and manually generated invoices

2.       Review and correct data

3.       Print Invoices

4.       Send Invoices

5.       Collect Payement

6.       Post Receipts

Cash Management Process:

1.       Receive Bank Statements

2.       Load and verify bank statements

3.       Perform Reconciliations

4.       Review Results

5.       Enter Manual Entries if needed

6.       Post to General Ledger

Order to Cash Lifecycle: Processes

Order to Cash Cycle

The Life Cycle of the Order

Following are the steps the process will go through from creating a Sales Order to Posting the details in GL.

·         Enter the Sales Order

·         Book the Sales Order

·         Launch Pick Release

·         Ship Confirm

·         Create Invoice

·         Create the Receipts either manually or using Auto Lockbox ( In this article we will concentrate on Manual creation)

·         Transfer to General Ledger

·         Journal Import

·         Posting

Applications Involved

Order Management: Creating and shipping the Order

Customer Master for customer details in OM

Inventory:  Onhand availability, Reservation

Pricing for List Price details in OM line

Receivables: For Receipt against invoice

General Ledger: Importing, entering and posting the journals.

Order Management Processes:

Orders can be created in following processes

1.       Enter Order manually

2.       Copy and Order or Return

3.       Import Orders from CRM or other legacy systems

Note: CRM (Customer Relationship Management) includes iServe, iStore, Teleservices, Telesales, Sales Online, iSupport.

Scheduling Process:

1.       Checking Available to Promise (ATP)

2.       Placing Demand

3.       Reserving Onhand

4.       Running Pick Release

5.       Shipping the Order

Pricing Process:

1.       Order line entered, take the part and customer details from Order

2.       Check price list or agreement

3.       Check for the modifiers

4.       Calculates the unit price

Shipping Process:

1.       Run Pick Release creates Move Order

2.       As per the Move Order details, parts moved out of the Subinventory (Transact Move Order)

3.       After getting the part from Subinventory, it will be dropped to Staging area (Pick Confirm, this runs automatically during Pick Release)

4.       After loading the goods into the Truck from Staging area, Ship Confirm can be run

5.       This ship confirm will decrement quantity from Inventory and update the sales order

6.       The information can be transferred to Receivables through AutoInvoice program and will generate the invoice for customer.

AutoInvoice Process:

1.       Transaction data can be transferred from a number of locations like Order Management, Contracts and Legacy Systems

2.       Data are brought to the Interface table, if any error, that will move to Interface exception table and after correction, again will be brought to the interface table

3.       Correct data gets inserted to the Receivables by AutoInvoice program. This can be related to Debit Memos, Memos and as Invoices

Receivable Process:

1.       Imported Invoices and manually generated invoices

2.       Review and correct data

3.       Print Invoices

4.       Send Invoices

5.       Collect Payement

6.       Post Receipts

Cash Management Process:

1.       Receive Bank Statements

2.       Load and verify bank statements

3.       Perform Reconciliations

4.       Review Results

5.       Enter Manual Entries if needed

6.       Post to General Ledger