AP Payables Header Level Entries - Inheritance/Accounting Template Constraint For Balanced Chartfield (Doc ID 2279646.1)

Last updated on JUNE 22, 2017

Applies to:

PeopleSoft Enterprise FIN Payables - Version 9.2 and later
Information in this document applies to any platform.

Goal

On Payables Header Level Entries - Inheritance/Accounting Template constraint for Balanced Chartfield (CF), in a scenario with many AP BUs to one GL BU, PeopleSoft CF Inheritance and Accounting Template designation for a Balanced CF cannot be configured.

Example: AP BU 10001 and 10003 mapped to GL BU 20001

When a voucher is created in AP 10001, the offsetting AP Liability CF should be populated by using the 10001 Accounting Template which specifies the correct Operating Unit. In this example 10001. Unfortunately, because Operating Unit is a "Balanced CF", the configuration FORCES the Voucher Post Process to use the GL Business Unit default which for Volt is a Blank Operating Unit.

The GL Business Unit must be left blank, because 2 AP BUs point to the GL BU and it can not be predetermined which one should be assigned. AP BU 10001 should always use Operating Unit = 10001, AP BU 10001 should always use Operating Unit = 10003.

There is no way to determine how to correctly configure PeopleSoft to generate the correct accounting. Using the available configuration, generates a multitude of undesired accounting lines per transaction.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms