FAQ: Account Generator (Doc ID 216831.

1)
Modified: 08-Feb-2013 Type: FAQ
APPLIES TO:
Oracle Purchasin
!nfor"a#ion in #his docu"en# applies #o any pla#for"$
PURPOSE
P%&'(A)* O&+*&): Accoun# ,enera#or - &elease 10$-. 11$0. 11$/$0. 12$0- 12$1$0
Fre1uen#ly repor#ed ho2-#o 1ues#ions rela#in #o produc# specific prora"s$
QUESTIONS AND ANSWERS
What does the Account Generator process do?
The Accoun# ,enera#or process builds chare. bude#. accrual. and 3ariance accoun#s for each purchase
order. release. and re1uisi#ion dis#ribu#ion based on #he dis#ribu#ion4s des#ina#ion #ype$ !# is a synchronous
5or6flo2 process$
What are the Pre-reu!s!tes to use Account Generator?
7efore usin #he Accoun# ,enera#or you "us#:
- +efine your Accoun#in fle8field s#ruc#ure for each se# of boo6s$
- +efine fle8field se"en# 3alues and 3alida#ion rules$
- )e# up Oracle 5or6flo2$
- +ecide 2he#her you 2an# #o use #he Accoun# ,enera#or processes as seeded in Oracle Purchasin. or you
need #o cus#o"i9e #he" #o "ee# your accoun#in needs$
What are the "or#$%o" !te& t'pes used !n Account Generator?
For Purchase Orders: PO5FPOA,
For &e1uisi#ions: PO5F&QA,
*ach Accoun# ,enera#or i#e" #ype con#ains #he follo2in #op-le3el 2or6flo2 processes:
,enera#e +efaul# Accoun#
,enera#e Accoun# %sin Fle8 7uilder &ules
!f you are upradin fro" 10$-. and you ha3e been usin #he fle8 builder #o enera#e #he accoun#s. you ha3e
an op#ion of upradin your e8is#in fle8 builder rules for Accoun# ,enera#or$ !n 2hich case. you should use
#he :,enera#e Accoun# %sin Fle8 7uilder &ules; process$
I ha(e )een us!n* the +%e, )u!%der ru%es !n Re%ease -./0 to )u!%d the accounts/ 1an I cont!nue
us!n* the sa&e setup !n account *enerator !n --/, a%so?
<es$ The sa"e se#up can be used 2i#h accoun# enera#or also$ To achie3e #his. #he follo2in ac#ions should
be perfor"ed on up rada#ion #o accoun# enera#or$
- &un #he prora" in =F>+?TOP@bin@F>+F7PA)$ This 2ill crea#e a PA@)QA pac6ae #ha# 2ill con#ain all #he fle8
builder rules$
- Apply #he ne2ly crea#ed PA@)QA file #o #he da#abase$ This 2ill crea#e a pac6ae called
PO?PO?'(A&,*?A''O%>T @
PO?&*Q?'(A&,*?A''O%>T
- Berify #ha# #he pac6ae is crea#ed successfully and #ha# i# is 3alid in da#abase$
- 'hoose #he Accoun# ,enera#or Top le3el process as ,enera#e Accoun# %sin Fle8 7uilder$
- Tes# #he accoun# enera#or$
)6ip #o con#en#
Page 1 sur 4 Document 216831.1
28/01/2014 https://support.oracle.com/epmos/faces/DocumentDisplay?a!f.ctrl"state#13$r%e&4's...
The flex builder rules package PO_PO_CHARGE_ACCOUNT is being oer!ri""en !heneer # appl$
a fa%il$ pack& 'h$(
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.
'ha" are "he s"eps "o genera"e "he ')*TAT ou"pu" for Accoun" Genera"or(
1. Set the following profiles:
- Account Generator: Run in Debug Node=> Yes
- Account Generator: Purge Runtime Data=> No
PO: Set Debug Workflow On => Yes
2. Nake sure that the concurrent program "Purge Workflow Obsolete Runtime Data" is NOT running.
3. Open Purchase OrderfRequisitions 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 lost):
Help=> Diagnostics => Examine
Enter in 1st field => parameter
Enter in 2nd field => charge_acc_wf_itemkey
Then tab out. The !tem key will appear in the third field.
+. Now save the purchase orderfrequisition. !f 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. !f 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 = '8item_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_TOPfsqlfwfstat.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
FRON po_wf_debug
WHERE item_key = '8!tem_key'
ORDER BY execution sequence;
'ha" exac"l$ does profile op"ion +Accoun" Genera"or, Run in -ebug .ode+ do(
This profile option controls whether the account generator workflow process runs in synchronous mode
(workflow-on-a-fly) or asynchronousfpersistent 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 etc.
'ill "he accoun" genera"or build "he charge accoun" based on pro/ec" infor%a"ion(
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.!S_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.
Page 2 sur 4 Document 216831.1
28/01/2014 https://support.oracle.com/epmos/faces/DocumentDisplay?a!f.ctrl"state#13$r%e&4's...
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 customized.
When the charge account field is non updateable?
!n the following cases the charge account field is not updateable:
1. !f the destination type code is !NvENTORY or SHOP FLOOR.
2. !f the distribution is already encumbered.
3. !f the PO is created from a encumbered Requisition
+. !f the destination type code is Expense and
!f the project is entered and the profile option PA: Allow Override of PA Distributions in APfPO is set to NO
!f the expense accrual code= RECE!PT
If the account generator process raises a blank error message, what does it mean?
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
type
Item
type/WIP
type
Sub inventory/WIP Entity
type/Bom_cost_element_id
Account Hierarchy Inventory
. . . expense_account - subinventory
. Expense Not NULL
expense_account - mtl_system_items
!nventory . . expense_account - mtl_parameters
. . NULL material_account - mtl_parameters
. . Expense expense_account -
mtl_secondary_inventories
. Asset Expense expense_account - mtl_parameters
. . Asset mtl_secondary - mtl_secondary_inventories
. . Asset material_account - mtl_parameters
. . . .
Expense . . expense_account - mtl_system_items
. (Req) default_code_combination_id
-hr_employees_current_v
. . . .
. . W!P - type 6,7 st_eamcost_pub.get_direct_item_charge_acct
. . Bom !d 5 overhead_account - wip_discrete_jobs
. . + outside_processing_account -
wip_discrete_jobs
. . 3 resource_account - wip_discrete_jobs
. . 2 material_overhead_account -
wip_discrete_jobs
Page 3 sur 4 Document 216831.1
28/01/2014 https://support.oracle.com/epmos/faces/DocumentDisplay?a!f.ctrl"state#13$r%e&4's...
. . 1 material_account - wip_discrete_jobs
. . NULL flex_value - fnd_flex_values_vl
. . . .
Shop Floor . . .
. . Bom !d 5 overhead_account - wip_discrete_jobs
. . + outside_processing_account -
wip_discrete_jobs
. . 3 resource_account - wip_discrete_jobs
. . 2 material_overhead_account
-wip_discrete_jobs
. . 1 material_account - wip_discrete_jobs
. . NULL flex_value - fnd_flex_values_vl
. . . .
REFERENE!
Page 4 sur 4 Document 216831.1
28/01/2014 https://support.oracle.com/epmos/faces/DocumentDisplay?a!f.ctrl"state#13$r%e&4's...