Sunteți pe pagina 1din 9



Modified 28-
Type FAQ

Applies to:
Oracle Purchasing

PURCHASE ORDERS: Account Generator - Release 10.7, 11.0, 11.5.X
Frequently reported how-to questions relating to product specific programs.

Questions and Answers

What does the Account Generator process do?
The Account Generator process builds charge, budget, accrual, and variance accounts for each
purchase order, release, and requisition distribution based on the distributions destination type.
It is a synchronous Workflow process.

What are the Pre-requisites to use Account Generator?

Before using the Account Generator you must:
- Define your Accounting flexfield structure for each set of books.
- Define flexfield segment values and validation rules.
- Set up Oracle Workflow.
- Decide whether you want to use the Account Generator processes as seeded in Oracle
Purchasing, or you need to customize them to meet your accounting needs.

What are the workflow item types used in Account Generator?

For Purchase Orders: POWFPOAG
For Requisitions: POWFRQAG
Each Account Generator item type contains the following top-level workflow processes:
Generate Default Account
Generate Account Using Flex Builder Rules
If you are upgrading from 10.7, and you have been using the flex builder to generate the
accounts, you have an option of upgrading your existing flex builder rules for Account
Generator. In which case, you should use the Generate Account Using Flex Builder Rules

I have been using the Flex builder rules in Release 10.7 to build the accounts.
Can I continue using the same setup in account generator in 11.x also?
Yes. The same setup can be used with account generator also. To achieve this, the following
actions should be performed on up gradation to account generator.
- Run the program in $FND_TOP/bin/FNDFBPLS. This will create a PL/SQL package that will
contain all the flex builder rules.
- Apply the newly created PL/SQL file to the database. This will create a package called
- Verify that the package is created successfully and that it is valid in database.
- Choose the Account Generator Top level process as Generate Account Using Flex Builder.
- Test the account generator.

The flex builder rules package PO_PO_CHARGE_ACCOUNT is being

overwritten whenever I apply a family pack. Why?
The family pack will contain POXWFB1S.pls and POXWFB1B.pls, which contains a blank
definition of the PO_PO_CHARGE_ACCOUNT for compilation purpose. This will override the
already existing PO_PO_CHARGE_ACCOUNT package created from flex builder rules. So the
Client must take a backup of the Flex builder rules package before applying the patch, and revert
back the package PO_PO_CHARGE_ACCOUNT using that file.

What are the steps to generate the WFSTAT output for Account Generator?
1. Set the following profiles:
- Account Generator: Run in Debug Mode=> Yes
- Account Generator: Purge Runtime Data=> No
PO: Set Debug Workflow On => Yes
2. Make sure that the concurrent program "Purge Workflow Obsolete Runtime Data" is NOT
3. Open Purchase Order/Requisitions form, go to the distributions window, enter necessary fields
and click on charge account field to start generating the charge account. After the account
generator has done building the account, or errors out, do the following from the toolbar (DO
NOT exit the form or navigate to any other block or record, otherwise this information would be
Help=> Diagnostics => Examine
Enter in 1st field => parameter
Enter in 2nd field => charge_acc_wf_itemkey
Then tab out. The Item key will appear in the third field.
4. Now save the purchase order/requisition. If you are not able to save, then clear the distribution
record and navigate back to the shipment window and save the form. Saving the form is must,
because a commit is required to save the workflow information in tables, for generating the
wfstat output.
5. If step#3 could not give you an item key, then use the following query to identify the relevant
item key:
Select item_key, item_type, begin_date
from wf_items
where item_type = '&item_type'
order by begin_date desc;
For PO, use 'POWFPOAG' item type in above query, and for requisition, use 'POWFRQAG'.
6. To generate the WFSTAT output,
Run the sql in $FND_TOP/sql/wfstat.sql with above item_type and item_key. Spool the output.
7. To get the wf debug information, run the following query:
SELECT item_key, item_type, debug_message
FROM po_wf_debug
WHERE item_key = '&Item_key'
ORDER BY execution sequence;

What exactly does profile option "Account Generator: Run in Debug Mode"
This profile option controls whether the account generator workflow process runs in synchronous
mode (workflow-on-a-fly) or asynchronous/persistent mode (save the runtime data).
When this profile is NULL or "No", the workflow runs in synchronous mode and it will NOT
store any runtime data in database. So you cannot generate the wfstat etc for debug purposes.
However once you set this profile option to "Yes", then the process would run in persistent
mode, thereby the runtime data would be stored in database. Now you can generate the wfstat

Will the account generator build the charge account based on project
No. By default, the Account Generator process as seeded in Oracle Purchasing would not
consider the project information to build the account. To achieve this functionality, you should
customize the Account Generator to consider the project details. There is a dummy sub process
'Build Project Related Account' seeded in the Account Generator workflow, available for
customization. You would also have to modify function
PO_WF_PO_CHARGE_ACC.IS_PO_PROJECT_RELATED to return a value of "True".
For more information on how to customize the Account Generator, please refer to the manual
Oracle Purchasing Account Generator Workflow Customization Example.

Will the account be generated for amount based/one time item lines?
No the Account will not be generated if you are using the Account Generator as seeded in Oracle
Purchasing. Either the account should be manually entered or the account generator should be

When the charge account field is non updateable?

In the following cases the charge account field is not updateable:
1. If the destination type code is INVENTORY or SHOP FLOOR.
2. If the distribution is already encumbered.
3. If the PO is created from a encumbered Requisition
4. If the destination type code is Expense and
If the project is entered and the profile option PA: Allow Override of PA Distributions in AP/PO
is set to NO
If the expense accrual code= RECEIPT

If the account generator process raises a blank error message, what does it
Check the invalid objects in the database. Recompile the invalid objects.

Where do the various accounts come from?

Here is a list of all possible places from where account will be picked:
Destination Sub inventory/WIP Entity
type/WIP Account Hierarchy Inventory
type type/Bom_cost_element_id
. . . expense_account - subinventory

. Expense Not NULL expense_account -


Inventory . . expense_account - mtl_parameters

. . NULL material_account - mtl_parameters

expense_account -
. . Expense mtl_secondary_inventories
expense_account - mtl_parameters
. Asset Expense

mtl_secondary -
. . Asset mtl_secondary_inventories

. . Asset material_account - mtl_parameters

. . . .
Expense . . expense_account -

. (Req) -hr_employees_current_v

. . . .
WIP - type 6,7 arge_acct
. .

overhead_account -
. . Bom Id 5 wip_discrete_jobs
outside_processing_account -
. . 4 wip_discrete_jobs
resource_account -
. . 3 wip_discrete_jobs
material_overhead_account -
. . 2 wip_discrete_jobs
material_account -
. . 1 wip_discrete_jobs

. . NULL flex_value - fnd_flex_values_vl

. . . .
Shop Floor . . .
overhead_account -
. . Bom Id 5 wip_discrete_jobs
outside_processing_account -
. . 4 wip_discrete_jobs
resource_account -
. . 3 wip_discrete_jobs
. . 2 -wip_discrete_jobs
material_account -
. . 1 wip_discrete_jobs
. . NULL flex_value - fnd_flex_values_vl

. . . .

Information Needed to Diagnose Problems with

the PO Account Generator Workflow [ID

Modified 11-NOV-2010 Type HOWTO Status


In this Document

Applies to:
Oracle Purchasing - Version: 11.0.3 to 12.1.3 -
Release: 11 to 12.1
Information in this document applies to any platform.
*** Checked for relevance on 11-NOV-2010 ***

POWFPOAG - PO Account Generator Workflow

FORM:POXPOEPO.FMB - Enter Purchase Orders


The purpose of this document is to provide a listing

of the steps to perform and the information to
provide for Oracle Support Services when a problem
is encountered with the PO Account Generator
workflow process.

Please provide the following information:

1) Upload the output of report 'Diagnostics: Apps

Check' run with these parameters:

- Application 1: Purchasing
- Application 2: Inventory
- Application 3: Projects
- leave all other parameters blank

This is a standard report which should be available

using the Purchasing Super User responsibility. If it
does not appear in the list of standard reports,
have the System Administrator add it to the request
group of the Responsibility being used.

2) Does the same problem exist with both Purchase

Orders and Requisitions?

3) a) Using the System Administrator responsibility,

go to:
Application > Flexfield > Key > Accounts

b) With the cursor in the Application field, choose

View > Find. Select the combination of Application,
Flexfield Title and Structure being used. What are
the values of the following item types:

- PO Account Generator
- PO Requisition Account Generator

4) Set these profile options as follows:

- 'Account Generator: Run in Debug Mode' = Yes

- 'PO: Set Debug Workflow ON' = Yes
- 'Account Generator: Purge Runtime Data' = No
(if this profile exists)

5) In the Purchase Orders form, enter the Line and

Shipment details, then go to the Distribution level.
From the menu, select: Help > Diagnostics > Trace
> Trace with Binds. Take note of the path and
filename which are provided.

6) a) Reproduce the issue while trying to generate

the account. Do not navigate out of the charge
account field. From the menu, select: Help >
Diagnostics > Examine. Manually type in the
following values for Block and Field (they will not
appear in the List of Values), then click in the Value

Block: parameter
Field: charge_acc_wf_itemkey
Value: <The value you get here is the

b) Clear the distribution record

c) Close the Distribution window
d) Close the Shipment window
e) Save the PO.

NOTE: The Purchase Order MUST be saved in

order to store the data from the PO Account
Generator workflow process to table WF_ITEMS.
Without this data being saved, the wfstat.sql script
(step 8 below) will not return any useful information
for diagnosing the issue.

7) From the menu, select: Help > Diagnostics >

Trace > No Trace. Locate the trace file on the
database server, then run tkprof on it. Upload both
the raw trace file and the tkprof output file.

8) Obtain the wfstat.sql output of the process:

a) SQL> spool wfstat.txt

b) SQL> @$FND_TOP/sql/wfstat.sql
- Item type: POWFPOAG
- Item key: <Value of item_key from above>

c) Upload the spooled output file (wfstat.txt).

9) Get the Debug information:

a) SQL> spool debug.txt

b) SQL> select debug_message from
where itemtype = 'POWFPOAG'
and itemkey = '&item_key';

c) Upload the spooled output file (debug.txt).

10) Which version of the following files is being


- $PO_TOP/patch/115/import/US/poxwfpag.wft
- $PO_TOP/patch/115/import/US/poxwfrag.wft

11) Are there any customizations in the PO Account

Generator workflow? If so, please upload the
customized workflow definition file, as well as any
custom or customized packages used by the
workflow process.


Oracle E-Business Suite > Procurement >

Procurement > Oracle Purchasing




Back to top