My Oracle Support Banner

WS: 83: FASTR Journal Entries to Invalid Accounts are not Created Properly (P83410) (Doc ID 2963361.1)

Last updated on JULY 26, 2023

Applies to:

JD Edwards World FASTR - Version A9.4 and later
Information in this document applies to any platform.

Symptoms

Journal entries created by FASTR to invalid accounts (Dynamic Account Creation) are created with inconsistent and/or incorrect data in the F0911 Account Ledger detail file. The following is noted:

An account number to be created dynamically using the feature of Dynamic Account Creation without the required preceding & (ampersand sign) will generate error 0028, Account Number Invalid.   

Steps:

  1. Allow Invalid Accounts with the following requirements (refer to Document 627082.1):
    1. The field "Allow Invalid (Y/N)" in the General Accounting Constants (P000909, Fast Path 9K or G0941/2) must be set to Y 
    2. A model business unit must be defined for every business unit type (STYL)
    3. The business unit type assigned to the business unit where the new accounts will be added must be the same as the business unit type in the model (e.g. STYL = MD)
    4. The account must exist in the model chart of accounts
    5. Accounts in the model business unit must allow posting
  2. Create a FASTR Column Report with Journal Entry Specifications in the Column Specifications to write the Report Results and J.E Offset to an Invalid Account and with the Journal Entry Specifications in Final mode (refer to Document 627070.1).
  3. Run the FASTR version (1 in the Option field).
  4. Review the report output and note the Batch Number created.
  5. Review the Journal Entry Batch:
    1. Go to General Journal Review (G0911/7)
    2. Enter the Batch Number from step 4 in the Batch Number field
    3. Enter 1 (Detailed Batch Review) in the Option field and press enter 
    4. Enter 1 (Individual Document Review) in the Option field and press enter
    5. Note the preceding & is missing for the Account Number
  6. Use a query tool (e.g. SQL or RUNQRY) to view the data in the F0911 file for the Journal Entry Batch created by FASTR and note any of the following:
    • The Document Company GLKCO is blank
    • The Company GLCO is blank
    • The Account Number GLANI is missing the preceding & 

 

Changes

N/A 

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.