Skip to main content

How the Account Generator Compares to AutoAccounting

How the Account Generator Compares to Auto-Accounting

You can implement the Account Generator to create the same accounting transactions that are created using your AutoAccounting implementation. This section compares the Account Generator to AutoAccounting to help you understand and implement the Account Generator based on your knowledge of AutoAccounting.
A function in AutoAccounting is equivalent to an item type in Workflow.
A parameter in AutoAccounting is equivalent to an attribute in Workflow.
The definition and assignment of rules to segments in AutoAccounting are equivalent to a process in Workflow.

See Also

Converting from FlexBuilder (Oracle Applications Flexfields Guide)

Assigning a Constant to a Segment

This section describes the steps required to assign a constant to a segment using the Account Generator.
Account Generator Functionality Similar Functionality in AutoAccounting

Assign a constant to a segment Assign a constant AutoAccounting rule to a segment


   To assign a constant value to a segment, you perform the following steps:

    1. Drag and drop the Assign Value to Segment function from the Standard Flexfield item type to your account generation process.
    2. Connect this function to prior and subsequent steps.
    3. Select Properties for this function.
    4. In the Comment field, you can optionally specify a comment to describe the action being performed in this step.
    5. Select the Attribute Values tab and enter the values for the four attributes.
    6. For the Value attribute, select Constant as the Value Type. Enter the constant under Value.
This function is used in Node 2 of the sample Account Generator process for Oracle Projects. See: Customization Example. For detailed information about this function, see Account Generator (Oracle Applications Flexfields Guide).

Assigning an Attribute Parameter to a Segment

This section describes the steps required to assign an attribute parameter to a segment using the Account Generator.
Account Generator Functionality Similar Functionality in AutoAccounting

Assign an attribute parameter to a segment Assign an AutoAccounting rule that uses a parameter, which becomes the segment value (a lookup set is not used)


   To assign an attribute to a segment, you perform the following steps:

    1. Drag and drop the Assign Value to Segment function from the Standard Flexfield item type to your account generation process.
    2. Connect this function to prior and subsequent steps.
    3. Select Properties for this function.
    4. In the Comment field, you can optionally specify a comment to describe the action being performed in this step.
    5. Select the Attribute Values tab.
    6. For the Value attribute, select Item Attribute as the Value Type. Then select the attribute whose value will be assigned to the segment.
For detailed information about this function, see Account Generator (Oracle Applications Flexfields Guide).

Assigning a Lookup Set Value to a Segment

Account Generator Functionality Similar Functionality in AutoAccounting

Assign a lookup set value to a segment Assign an AutoAccounting rule that passes a parameter to a lookup set to determine the segment value


Deriving a Segment Value via SQL Statements or If Conditions

Account Generator Functionality Similar Functionality in AutoAccounting

Derive a segment value via SQL statements or If conditions Use an AutoAccounting rule that derives the intermediate value or segment value via a SQL statement.

You typically use SQL statements for if/then logic. With the Account Generator, you can do this with either conditional nodes (used in Nodes 3, 4, 5, and 6 in the sample Account Generator process for Oracle Projects) or SQL functions (used in Nodes 7 and 8 in the sample Account Generator process for Oracle Projects). See: Customization Example.

SQL Functions

You must follow Workflow standards when writing SQL procedures for the Account Generator. The values of any attributes required can be retrieved within the procedure code using calls to the standard Workflow functions. The final value determined by the procedure is copied into one of the attributes. This value can be then assigned to a segment. SQL functions are illustrated in Nodes 7 and 8 in the sample Account Generator process for Oracle Projects. See: Customization Example.

See Also

The Sample Process for Account Generation Overview of AutoAccounting
Oracle Applications Flexfields Guide

Comments

Post a Comment

Popular posts from this blog

SQL Query to extract Oracle Purchase Order Information

SELECT   poh.po_header_id,    poh.type_lookup_code PO_TYPE,   poh.authorization_status PO_STATUS,   poh.segment1 PO_NUMBER,   pov.vendor_name SUPPLIER_NAME,   povs.vendor_site_code Location,   hrls.location_code Ship_To,   hrlb.location_code Bill_to,   pol.line_num ,   msib.segment1 Item,   pol.unit_price,   pol.quantity,   pod.amount_billed Amount,   pod.destination_subinventory,   ppf.full_name Buyer_Name,   poh.closed_Code  FROM   PO_HEADERS_ALL poh,   PO_LINES_ALL pol,   mtl_system_items_b msib,   PO_LINE_LOCATIONS_ALL poll,   PO_DISTRIBUTIONS_ALL pod,   po_vendors pov,   po_vendor_sites_All povs,   hr_locations_all hrls,   hr_locations_all hrlb,   per_all_people_f ppf,   po_line_types polt WHERE   1                         =1 AND polt.line_type_id    = pol.line_type_id AND povs.vendor_site_id     = poh.vendor_site_id AND pov.vendor_id           = poh.vendor_id AND pol.item_id             = msib.inventory_item_id AND msib.organization_id  
Post a Comment
Read more

Query to find Operating Unit, Business Group and Legal Entity Information

SELECT   DISTINCT   hrl . country ,                  hroutl_bg . name              bg ,                  hroutl_bg . organization_id ,                  lep . legal_entity_id ,                  lep . name                    legal_entity ,                  hroutl_ou . name              ou_name ,                  hroutl_ou . organization_id   org_id ,                  hrl . location_id ,                  hrl . location_code ,                  glev . flex_segment_value FROM     apps . xle_entity_profiles   lep ,         apps . xle_registrations   reg ,         apps . hr_locations_all   hrl ,         apps . hz_parties   hzp ,         apps . fnd_territories_vl   ter ,         apps . hr_operating_units   hro ,         apps . hr_all_organization_units_tl   hroutl_bg ,         apps . hr_all_organization_units_tl   hroutl_ou ,         hr_organization_units   gloperatingunitseo ,         apps . gl_legal_entities_bsvs   glev WHERE    lep . transacting_entity_flag   =   'Y'         AND   l
Post a Comment
Read more

List of iExpenses Tables

List of iExpenses Tables  Table Name Description AP_EXPENSE_REPORT_HEADERS_ALL Expense report header information AP_EXPENSE_REPORT_LINES_ALL Expense report lines information AP_EXP_REPORT_DISTS_ALL Expense report distribution information. It contains the accounts against each expense report line. AP_CREDIT_CARD_TRXNS_ALL Table to store the corporate credit card transactions that are sent by the banks. These lines are saved as expense lines when the user creates the expense lines for credit cards AP_NOTES Table to store the comments entered by approvers and auditors     Setup tables   AP_EXPENSE_REPORTS_ALL This table contains the header level information about the expense templates AP_EXPENSE_REPORT_PARAMS_ALL This table contains the detail level information about the expense templates AP_POL_CAT_OPTIONS_ALL Table to store the policy options AP_POL_CONTEXT Table to store the policy context     AP_POL_LOCATIONS_TL Table
Post a Comment
Read more