How To Setup AutoPost Journal

AutoPost feature is used to automatically post the journals within ledger, source, category, balance type, and period. The feature would make user easier posting many journal batches after review them. Here the steps to setup AutoPost journals:

Responsibility: General Ledger
Navigation: Setup > Journal > AutoPost

AutoPost Criteria Set Form

Criteria Set --> Criteria Set name

Description --> Description of Criteria Set

Enabled --> Tick to activate the Criteria Set

Posting Submission Options --> Submit All Priorities in Order

Priority --> Priority to process AutoPost Criteria Set

Ledger/Ledger Set --> Ledger/Ledger Set that used to AutoPost

Source --> Journal Sources to be posted

Category --> Journal Category to be posted

Balance Type --> Balance Type journal to be posted

Period --> period of journal to be posted

After setup the AutoPost Criteria Set, we can submit the concurrent program through the same form (Submit button) or from navigation View > Request.

Program - Automatic Posting

Program Name : Program - Automatic Posting

Parameter: AutoPost Criteria Set created

We can also schedule the concurrent program.

PO - APP-PER-50022 Oracle Human Resource could not retrieve a value for the User Type profile option

Error occured when trying to open Employees / Jobs / Positions / Position Hierarchy from Purchasing responsibility

Solution :

Setup profile option HR : User Type for desired responsibility.

Navigate to System Administrator responsibility > Profile > System

Click Find and set value to HR User

Save profile option, and the issue should be resolved

Enable Backdate/ Future Date Document Sequence In Order Management

Business Case :

Oracle standard numbering for Sales Order is maintained by document sequence, and it is not possible for backdate / future date numbering. Numbering will always refer to sysdate, not the Quote Date or Date Ordered.

But it can be modified by editing standard package OE_HEADER_UTIL :

1.      Type the package name in TOAD, then press F4, like screenshot below :

2.      Copy all the package body to TOAD

3.      Dont forget to save file as backup, in case some error happens

4.      After saving backup file, start editing by pressing CTRL + G to find the desired line

Line 7895 – 7909 :

           x_result :=   fnd_seqnum.get_seq_info(

                                             660,

                                             x_doc_category_code,

                                             x_set_of_books_id,

                                             null,

                                             sysdate,

                                             X_doc_sequence_id,

                         x_doc_sequence_type,

                         x_doc_sequence_name,

                                             X_db_sequence_name,

                             seqassid,

                         X_Prd_Tbl_Name,

                         X_Aud_Tbl_Name,

                         X_Msg_Flag

                                             );

Line 7924 – 7933 :

                X_result := fnd_seqnum.get_seq_val(

                                                660,

                                                x_doc_category_code,

                                                x_set_of_books_id,

                                                null,

                                                sysdate,

                        x_doc_sequence_value,

                                                X_doc_sequence_id,

                        'Y',

                        'Y');

From those 2 functions, we can see the parameter is SYSDATE, that’s why backdate / future date is not possible. So, we should change the parameter into :

NVL(p_x_header_rec.QUOTE_DATE, p_x_header_rec.ORDERED_DATE)

which means the parameter will refer to quote date / ordered date. After changed, the function will be :

Line 7895 – 7909 :

           x_result :=   fnd_seqnum.get_seq_info(

                                             660,

                                             x_doc_category_code,

                                             x_set_of_books_id,

                                             null,

                                             NVL(p_x_header_rec.QUOTE_DATE, p_x_header_rec.ORDERED_DATE),

                                             X_doc_sequence_id,

                         x_doc_sequence_type,

                         x_doc_sequence_name,

                                             X_db_sequence_name,

                             seqassid,

                         X_Prd_Tbl_Name,

                         X_Aud_Tbl_Name,

                         X_Msg_Flag

                                             );

Line 7924 – 7933 :

                X_result := fnd_seqnum.get_seq_val(

                                                660,

                                                x_doc_category_code,

                                                x_set_of_books_id,

                                                null,

                                                NVL(p_x_header_rec.QUOTE_DATE, p_x_header_rec.ORDERED_DATE),

                        x_doc_sequence_value,

                                                X_doc_sequence_id,

                        'Y',

                        'Y');

After editing, we have to compile the package body by pressing F9, after that backdate / future date Sales Order numbering is enabled.

Cascading Attribute Sales Order Header to Line

Attributes on sales order header are used as default for sales order line. However, if there is a change in sales order header, entered lines will not get updated automatically. This feature can replace those manual works to update entered lines so lines will always follow the value in sales order header.

How to setup :

1.      Responsibility : System Administrator > Profile > System

Find  profile option : OM: Sales Order Form: Cascade Header Changes to Line

Default value is NULL, change it to Automatic / Ask Me / Manual, in this case we’re using Automatic. Can be changed in Site / Responsibility / User level.

2.      Responsibility : Order Management Super User > Setup > QuickCodes > Order Management

Find lookup type : OM_HEADER_TO_LINE_CASCADE

Tick enable for each attributes that you want to cascade automatically.

Create Internal Suppliers From Employees

We know that to maintain our suppliers at Oracle E-Business Suite, we could utilize suppliers feature at Payables modules. To specifically differ the internal suppliers, such as employees, we could use another type supplier to automatically import the employee information to supplier: supplier used to process expense payment to internal employees. Furthermore, the feature could support the automatic expense report invoices utilization (we would explain this feature for the upcoming posting).

First of all, we usually only have one option to create supplier. When we click on Create button supplier, we immediately have to key in the supplier info, such as, Supplier Name, Alternate Supplier Name, Supplier Name, and do on. Yet to create internal suppliers from importing employee info, we need to grant an access at the menu POS_HT_SP_FULL_ACCESS_MENU.

Responsibility: System Administrator

Navigation: Application > Menu

Click Icon Find: POS_HT_SP_FULL_ACCESS_MENU

Tick all menu to grant the access.

POS_HT_SP_FULL_ACCESS_MENU

After we grant the access, we have another option to create supplier.

Internal Supplier Entry

Secondly, we could choose the the employee to import to internal supplier by pick the name from the list of value at Employee Name. When we choose the Employee Name, the Employee Number would automatically appear align with the employee master data.

Employee Master Data

Employee Import as Internal Supplier

The last, we complete the internal supplier information like we do for the external suppliers. When we finish the supplier creation, we could use the employee as the supplier for Expense Report, Invoice Workbench, or Purchase Orders.