AutoInvoice Date Derivation: GL Date, Invoice Date, Due Date, Ship Date, Billing Date, Rule Date

During the process of AutoInvoice you can enter the General Ledger (GL) date and the Transaction date for a particular transaction explicitly in the relevant columns of the RA_INTERFACE_LINES_ALL table or you can allow the AutoInvoice process to derive the dates.

If the dates are provided, AutoInvoice will typically use them. There are a few scenarios where dates cannot be provided as input parameters; these scenarios are discussed in section 2.e titled GL Date Validation.

If the dates are not provided, they will be derived. Date Derivation of the General Ledger date and Transaction date during the process of AutoInvoice depends on the following:


1. The columns that are populated in the RA_INTERFACE_LINES_ALL table, namely:


GL_DATE
TRX_DATE
SHIP_DATE_ACTUAL
SALES_ORDER_DATE
RULE_START_DATE

2. Selection of the Derive Date Option in the Accounting Information Tab of the Transaction Sources window.

3. Whether or not Invoicing Rules and Accounting Rules are used.

4. Setting of the GL Date in a Closed Period option in the AutoInvoice Options tab of the particular Transaction Batch Source.

5. Default Date entered while submitting the AutoInvoice Program.

Once imported as a transaction in receivables, the GL date used by AutoInvoice is stored in the table.column: RA_CUST_TRX_LINE_GL_DIST_ALL.GL_DATE.



Note: The GL date discussed in this note is for the initial accounting entry booked to record the creation of the invoice. For invoices with rules, Revenue Recognition will generate additional accounting entries and may impact the dates seen by users when reviewing transactions in Receivables.

Order to Cash Cycle (O2C)–In R12

Overview

In this practice, you will learn how to create orders with a standard item. Please note that you will be completing an order to cash cycle with a standard item using all the seeded data available in the environment. Examples of seeded data are: Order Type, Customer, Price List, Item, etc.

Create an order to cash lifecycle

1. Create an order.

2. Save and book the order.

3. Pick Release the order.

4. Ship Confirm the order.

5. Use AutoInvoice to create an invoice for the order.

Practices Steps – Order to Cash life cycle

Responsibility: Order Management Super User, Vision Operations (USA)

Create an Order

1. (N) Orders, Returns > Sales Orders

2. Create an order for Business World:

Field	Value
Customer	Business World (1608)
Order Type	Mixed (defaults)

3. Verify the following on the Main tab and Others tab (if the field is not visible on the window, you can folder-enable it):

Field	Value
Operating Unit	Vision Operations
Shipping Method	DHL Note: this may be under (T) Others
Warehouse	M1
Price List	Corporate
Ship To Location Bill To Location	<Both should default depending on the Customer Name/Number selection>

4. (T) Line Items – enter Order Line Information:

Field	Value
Ordered Item	AS54888
Qty	2

5. Save your work. The Status on the line should display as Entered.

6. Click (B) Book Order to book the order. Note your Order Number 66862.

7. Click (B) OK to acknowledge Note.

Note: Ensure you are at the line level prior to checking the workflow. Click (M) Tools > Workflow Status to see the status of the flow. Click (B) View Diagram on the Workflow Status HTML page to see the order processes and activities. A green box around the activity indicates that the activity is in progress. Close the Workflow Status window to return to the Sales Orders window.

8. Close the window.

Pick Release the Order

9. (N) Shipping > Release Sales Orders > Release Sales Orders

10. In the (T) Order tab, the Orders field should show a value of Unreleased.

Enter your order number in the Order Number field.

The Customer and Order Type fields get populated based on the Order Number field value.

11. Click (T) Inventory, enter the following:

Field	Value
Warehouse	M1
Auto Allocate	Yes

12. Click (T) Shipping, enter the following:

Field	Value
Autocreate Delivery	Yes
Auto Pick Confirm	Yes
Ship Confirm Rule	<Clear the field>

13. Click (B) Execute Now to pick release and pick confirm the order.

14. Click (B) OK to acknowledge Note.

15. Close the window.

Ship Confirmation

16. (N) Shipping > Transactions

17. The Query Manager window opens. Enter your order number in the fields From Order Number and To Order Number. Select no value in the Line Status field.

18. Click (B) Find to find your order.

19. The Shipping Transactions window opens to display your order details with the statuses.

20. (T) Delivery

21. Click (B) Ship Confirm and accept defaults.

22. Click (B) OK

23. You will receive a message that the delivery was successfully confirmed. Click (B) OK and close the Shipping Transactions window.

Verifying Status

24. Open the Sales Orders window to check the status of your order. (T) Line Items: the line status should display as Shipped.

25. Click (M) Tools > Workflow Status to see the current status of your order. Click (B) View Diagram to see the diagrammatic representation of the order flow. When a workflow activity is enclosed in a green box, it implies that the activity is in progress.

Viewing the Shipping Details from the Sales Orders window

26. Click (B) Actions > Additional Line Information to view the delivery and trip information and status.

Additional Line Information

Delivery Status: Closed Picked Status: Shipped Trip Status: Closed

Interfacing to Receivables using the Workflow Background Process Concurrent Program

Note: These steps may not be necessary if the Workflow Background program is already running on a scheduled basis.

27. From the Sales Orders window, navigate to (M) View > Requests.

· Click (B) Submit a New Request

· Select Single Request

· Request Name: Workflow Background Process.

· Enter the following as parameters in the Parameters window:

Parameter	Value
Item Type	OM Order Line
Process Deferred	Yes
Process Timeout	Yes
Process Stuck	<Clear the default value>

28. Click (B) OK to accept parameters

29. Click (B) Submit to process your request. You will get a request ID that you can track in the Find Requests window. Click (B) No in the Decision pop-up.

Note: Click (B) Find to see your request processed. It should complete as Normal.

30. Return to the Sales Orders window. Query for your order by using the F11 key. Enter your order number and use the Ctrl-F11 keys to get the query results. Though your order status still displays as Booked, the line status should show up as Closed.

31. Close the window.

Run AutoInvoice

32. (N) Receivables > Interfaces > AutoInvoice

· Click (B) OK to Submit a Single Request. The concurrent programs window opens to enable you to run AutoInvoice.

33. In the Name field select the AutoInvoice Master Program and enter the following parameters in the parameters window:

Parameter	Value
Organization	All
Invoice Source	ORDER ENTRY
Date	<current date>
(Low) Sales Order Number	<Look for your Sales Order Number range in the LOV and select it>
(High) Sales Order Number	<Look for your Sales Order Number range in the LOV and select it>

34. Click (B) OK and return to the main window. Click (B) Submit to run AutoInvoice. You will be given a request ID, which you can use to track the status of your request. It should complete as normal.

Viewing your Invoice Details

35. (N) Orders, Returns > Order Organizer

36. Enter your order number and click (B) Find.

37. When your order appears in the result list, click (B) Actions > Additional Order Information > (T) Invoices / Credit Memos.

38. Click (B) Invoice Details to view the invoice autocreated from your order.

39. Click on the invoice print (B) .

40. Close the screen and return to the navigator

Order to Cash (O2C) Accounting Entries

Order to Cash Accounting Cycle :
Below table show the order to cash accounting entries creation for each level

PARTICULARS	DR	CR	SPL NOTES	ACCOUNT IS PULLED FROM
Sales order entry
No Accounting
Sales Order Pick
From Sub Inventory A/c		100	At Standard Cost	Sub-inventory Material A/c Setup
To Sub Inventory A/c	100		At Standard Cost(Staging)	Sub-inventory Material A/c Setup
Sales Order Issue
COGS	100		It can be fetched from five places	Master Item/Org/Order Type/Line Type/Shipping Params
To Sub Inventory A/c		100	At Standard Cost	Sub-inventory Material A/c Setup
Transaction level
Receivable A/c	120			Auto Accounting
Tax A/c		10		Auto Accounting
Freight A/c		10		Auto Accounting
Revenue A/c		100		Auto Accounting
Receipts
Receipts with no remittance method
Cash	100		Before application of the receipt	Receipt class
Unapplied A/c		100		Receipt class
Unapplied A/c	100		After application of the receipt to the transaction	Receipt class
Receivables A/c		100		Receipt class
Cash A/c	100			Receipt class
Unidentified A/c		100	In case of receipt without customer or transaction	Receipt class
Unidentified A/c	100		when customer identified	Receipt class
Unapplied A/c		100		Receipt class
Receipts with remittance method.
Confirmed receipts A/c	100		At the time receipt entry	Receipt class
Unapplied A/c		100		Receipt class
Remitted receipts A/c	100		On remittance to bank	Receipt class
Confirmed receipts A/c		100		Receipt class
Cash	100		On clearance of cheque	Receipt class
Remitted receipts A/c		100		Receipt class
Receipts with discount/unearned discounts
Cash	90		At the time earned discounts	Bank
Discount earned A/c	10			Receivable activity
Receivable A/c		100		Transaction Type
Cash	90		At the time of unearned discount	Bank
Discount unearned A/c	10			Receivable activity
Receivables A/c

unable to see item in price list LOV in r12 order management

Issue:

Unable to see Inventory item in order management price list LOV

Solution:

Attach profile option "QP:Item Validation Organization" under your order management responsibility level  then reproduce the steps.

user defined exceptions in package oe_schedule_util procedure insert_into_mtl_sales_orders FND_FLEX_SERVER2.get_qualsegs() could not find any segment for the flexfield specified by application ID=401, code=MKTS and structure number=101

Issue:

user defined exceptions in package oe_schedule_util procedure insert_into_mtl_sales_orders

FND_FLEX_SERVER2.get_qualsegs() could not find any segment for the flexfield specified by application ID=401, code=MKTS and structure number=101

Solution:

Fnd_flex_server2.Get_qualsegs() Could Not Find Any Segments (Doc ID 797564.1)

Applies to:

Oracle Order Management - Version 12.0.4 and later
Information in this document applies to any platform.

Symptoms

-- Problem Statement:
On 12.0.4 in Production:
When attempting to enter the Sales Orders form, the following error occurs:

ERROR
"Program error. The data that defines the flex field on this field may be inconsistent.
Inform you system administrator that the routine FND_FLEX_SERVER2.get_qualsegs() could not find any
segments for the flex field specified by Application ID = 401, Code = MKTS and structure number = 101"

-- Steps To Reproduce:
The issue can be reproduced at will with the following steps:
Configuring OM module in R12. Configure all parameters, then:
1. Start the Sales Orders Form
2. Fill all fields
3. Press "Line Item" tab.
4. The message error is displayed.

Cause

The Flex Field for "MKTS" and title "Sales Order" was not setup.

Document 93466.1 has the information that is needed to set up the Inventory - Sales Order flex field.
Document 236108.1 Oracle Applications Flex fields Guide Release 11i.

Solution

From Document 93466.1:

Check the setup for the Sales Order flex field and make corrections wherever required.

1. Check if you have the segments of the Sales Order flex field set to the following:

segment 1 - sales order
segment 2 - order type
segment 3 - order source
If the above values do not tally, change the values, freeze and recompile
the flex field.
System Administrator Responsibility: Application --> Flexfield--> Key

2. Use the following script to check the above values at the database level:

Select Sales_Order_ID, segment1, segment2, segment3
From MTL_SALES_ORDERS
Where segment1 = 'order number'

The correct entry should return the following result:

Sales_Order_ID segment1 segment2 segment3
Sales_Order_ID number Order Number Standard ORDER ENTRY

Select the Sales_Order_ID that does not have the above result. Update the
MTL_TRANSACTIONS_INTERFACE table with the Transaction_Source_ID that has the
correct result using the following script:

Update MTL_TRANSACTIONS_INTERFACE
Set Transaction_Source_ID = correct sales order id number;

3. Check if dynamic insert has been enabled for Sales Order flex field. If you have not enabled
it, unfreeze the flex field, enable dynamic inserts, freeze and compile the flex field.

4. Check the segment separator for the flex field. It should be set to '.' (dot)

5. Check for the Value Set attached to the segments of the sales order flex field. Check if the
actual value passed is within the maximum value allowed for the Value Set.

6. Check that you have set the profile option "Validate on Server" for the Sales Order flex field
to "No."

Error while opening r12 sales order form. EOERR: ORA-4062 "timestamp/signature

Issue: 

EOERR: ORA-4062 "timestamp/signature


Solution:

We have to compiled particular form using adadmin in database.

Check below Oracle Support Note for more details.

OERR: ORA-4062 "timestamp/signature of %s has been changed" (Doc ID 19851.1)

Error:  ORA-4062
Text:   timestamp/signature of %s has been changed
-------------------------------------------------------------------------------
Cause:  Attempt to execute a stored procedure to serve
        an RPC stub which specifies a timestamp/signature that is different 
        from the current timestamp/signature of the procedure.
Action: Recompile the caller in order to pick up the new timestamp/signature.

*** Important: The notes below are for experienced users - See Note:22080.1
 
Note: Simply re-executing the procedure that calls the remote one will cause
      it to be re-compiled.

      Note also that this error is only returned when calling remote procedures.
      The way to avoid it as far as possible is to only ever call remote
      *packaged* procedures, whose body may be re-built without affecting the
      timestamp (stored in the specification).

      It is also advisable to set <Parameter:REMOTE_DEPENDENCIES_MODE> to
      SIGNATURE on releases supporting this.