Oracle Workflows

When you enter an expense claim in iExpenses, one of the key fields that you select a value for is “Expense Type field” at the time of data entry..

Expense type value will dictate whether the Expense Line is of type Project or Non-Project.

Almost all the businesses will require Default Accounts to be generated, to assist user with data entry.
However businesses will also require a different Account Code Combination to be generated for Expense with Project Line and the Expense for non-Project Line.
Surely, this means that logic for costing/accounting is usually different for expenses and revenues against Project Accounting transactions.

How do I generate a default account using custom logic, for a non-Project line?
Do I use an account generation workflow?
For a non-project expense line, Oracle provides a PL/SQL API Hook into which you can write your custom logic to build a default GL Account Combination.
There is no need of development of Workflow in this case.
Note:- This default account can be overridden by the end user in the screen [Subject to certain OIE Profile Options].

How do I generate a default account using custom logic, for a Project based line?
In this case, Oracle provides a Workflow named "Project Expense Report Account Generator"
The item key of this workflow is PAAPWEBX.
Depending upon your business requirements, you will have to customize your workflow to generate a GL Code Combination for project based expense lines.
For Project Expenses, iExpense screen actually calls PL/SQL API pa_acc_gen_wf_pkg.ap_er_generate_account which in turn calls the Workflow PAAPWEBX for account generation.
Note:- This default account can be overridden by the end user in the screen [Subject to certain OIE Profile Options].

But for a project based expense line, how will the Workflow get a handle to the Project/Task/Expenditure Organization etc?
When iExpenses OA Framework screen will calls workflow account generation process, the screen also initializes various WF Attribute Columns.
Your custom logic can read those attribute values and build a default account.

    ap_web_cus_acctg_pkg.buildaccount
        This is where you actually build the default account for non-project expense line.

What do I write into these pl/sql API’s, any sample Code
getiscustombuildonly API this must return 1 if you want your custom logic to kick-off.
If this API does not return 1, then iExpenses will use the person level default accounts from HRMS.
Sample code you can use is
  FUNCTION buildaccount(p_report_header_id      IN NUMBER
                       ,p_report_line_id        IN NUMBER
                       ,p_employee_id           IN NUMBER
                       ,p_cost_center           IN VARCHAR2
                       ,p_exp_type_parameter_id IN NUMBER
                       ,p_segments              IN ap_oie_kff_segments_t
                       ,p_ccid                  IN NUMBER
                       ,p_build_mode            IN VARCHAR2
                       ,p_new_segments          OUT NOCOPY ap_oie_kff_segments_t
                       ,p_new_ccid              OUT NOCOPY NUMBER
                       ,p_return_error_message  OUT NOCOPY VARCHAR2)
    RETURN BOOLEAN IS
    l_account_array fnd_flex_ext.segmentarray;
  BEGIN
    p_new_ccid := 240694; --do not hard code in realiy, this is just sample
    l_account_array(1) := 'FOCUST';
    l_account_array(2) := 'CONSULTANCY';
    l_account_array(3) := 'R12';
    l_account_array(4) := '165122';
    l_account_array(5) := '0';
    l_account_array(6) := '0';
    l_account_array(7) := '0';
    p_new_segments := ap_oie_kff_segments_t('');
    p_new_segments.EXTEND(l_account_array.COUNT);
    FOR n_ctr IN 1 .. l_account_array.COUNT LOOP
      p_new_segments(n_ctr) := l_account_array(n_ctr);
    END LOOP;
    RETURN TRUE;
  END buildaccount;

Anil Passi

Add comment