My Oracle Support Banner

GLPPOS Posting in Primary Ledger Gives Error33 - Invalid Account In Chart Of Accounts Mapping (Doc ID 1913861.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle General Ledger - Version 12.1.3 and later
Information in this document applies to any platform.
Executable:GLPPOS - Posting
Error33

Symptoms

When a journal entry is created in Primary Ledger using a code combinations that does not exist and the Secondary Ledger Chart of Accounts (COA) has dynamic insert checked, when run the journal posting program the following error occurs:-

Error
------
"Invalid account in chart of accounts mapping".


When the code combination is created manually in the Secondary Ledger for testing purpose, Posting in the Primary Ledger is successful.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.