Kirby Corp Oracle ERP: M A G - S O POA L POE

You might also like

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 6

MD.

050
Kirby Corp Oracle ERP

MODIFY THE ACCOUNT GENERATOR – SET


ORG SEGMENT IN PO ACCRUAL LIABILITY
ACCOUNT TO SAME AS PO EXPENSE ACCOUNT

Data Conversion - Interface – Extension –


Form Functional
Design & Specification

Author: Thomas Conrad


Creation Date: Sep 09, 2021
Last Update: Sep 0913, 2021
Version: 1.10

Approvals:

Tim Pajaro

Anita Jacob

591893283.doc 11
Company Confidential - For internal use only
Change Record

Date Author Version Change Reference

09/09/2021 Thomas Conrad 1.0 Initial Draft


09/13/2021 Thomas Conrad 1.1 Update section 1.1 after input from Melissa.

Updated section 1.4 to include manual PO\


Requisitions from Purchasing

Reviewers

Name Role / Position Phone email

Melissa Kocurek Melissa.Kocurek@kirbycorp.com


Greg Forestieri Greg.Forestieri@kirbycorp.com
Simon Chiang Simon.Chiang@kirbycorp.com

591893283.doc 21
Company Confidential - For internal use only
1. Background 2
1.1. Business Requirement 2
1.2. Major Features 2
1.3. User Procedures 2
1.4. Business Rules 2
1.5. MLS Requirements 3
1.6. Assumptions 3
1.7. Related Documents 3
2. Open and Closed Issues 43
2.1. Open Issues 43
2.2. Closed Issues 43

591893283.doc 11
Company Confidential - For internal use only
1. Background
This deliverable is used to define and create design specifications for a
modification to the Account Generator for the PO Liability Accrual
Account.

This customization will modify the account generator so that the accrual
liability account on PO’s has the same org as the charge account on the
PO.

1.1. Business Requirement

The Business would like the PO Liability Accrual account to have the same
Org as the PO Charge account. This will apply to all Purchase Orders \
Requisions entered through Oracle Purchasing and iProcurment.

1.2. Major Features

NA

1.3. User Procedures

NA

Manual

1.4. Business Rules


1.5.
1.6.

For PO’s\Requisitions coming in through iProcument the Account Generator


workflow will need to be modified.

The default Account Generator configuration in Oracle Purchasing builds a charge,


budget, accrual, and variance account for each purchase order, release, and
requisition distribution based on the distribution's Expense, or Inventory,
destination type. Oracle Purchasing always builds these accounts using the Account
Generator; you cannot disable this feature.

Each Account Generator workflow is called an item type. Oracle Purchasing comes
with the following Account Generator item types for purchase orders and releases:

PO Accrual Account Generator


PO Budget Account Generator
PO Charge Account Generator
PO Variance Account Generator

The following Account Generator item types exist for requisitions:

PO Requisition Accrual Account Generator


PO Requisition Budget Account Generator

591893283.doc 21
Company Confidential - For internal use only
PO Requisition Charge Account Generator
PO Requisition Variance Account Generator.

The PO Accrual Account Generator and PO Requisition Accrual Account Generator items need to
be modified to Force the Org segment of the PO Accrual account to be the same as the PO or
Requisition PO Charge Account.

Below shows a current example of the associated accounts:

 
This is what the Business would like the accounts to be

For PO’s\Requisions entered manually through Oracle Purchasing the Purchasing Options Automatic
Offset option need to be set to “Balancing”

To populate the Accrual account for distributions with an Expense destination type, the Account Generator
locates the Expense AP Accrual Account that you specify in Define Purchasing Options as part of your
application setup and copies it into the Accrual Account in your document. The Account Generator then
overlays the balancing segment of the AP Accrual Account with the balancing segment of the charge
account so that your transactions always balance by fund.
 

1.7. MLS Requirements


Not applicable.

591893283.doc 31
Company Confidential - For internal use only
1.8. Assumptions

This is to apply to Requisitions and Purchase Orders entered through Oracle


Purchasing and iProcurement.

1.9. Related Documents

NA

2. Open and Closed Issues

2.1. Open Issues

ID Issue Resolution Responsibility Target Date Impact


Date

1
2

2.2. Closed Issues

ID Issue Resolution Responsibility Target Date Impact


Date

591893283.doc 41
Company Confidential - For internal use only

You might also like