FIN ARG 9.1: Inflation Adjustment - Document Sequence and Process Instance Not Populated (Doc ID 2904343.1)

Last updated on OCTOBER 26, 2022

Applies to:

Symptoms

FIN AM ARG 9.1 - Inflation Adjustment - Document Sequence and Process Instance not populated

When running Inflation Adjustment (AMDPINFL) process, all Document Sequencing related and Process Instance fields  are not populated on the DIST_LN table.

 - Document sequencing, sequence number, and processing date
 - Process Instance field

Steps to replicate:

  1.  Log in PS as VP1
  2.  Create a new GL and AM, enabling document sequencing feature
  3.  Set up document type for the category.  Ensure that inflation has its own document type: i.e. AM-INF
  4.  Enter inflation indexes (i.e. exchange rates)
  5.  Check open periods.
  6.  Add asset with existing profile.
       Check document sequencing tab by default. OK
       Keep default use life and methods and check inflation information within the framed link. 
  7.  Check index.  Just leave defaults on last page.
  8.  Asset created successfully.
  9.  Run depreciation process.
10.  Run accounting entries for asset addition.
       Accounting entry generated and document sequencing information generated. OK
11.  Run depreciation close process.
12.  Review generated entries
       Doc sequencing generated successfully for periods. OK
13.  Now run Inflation process for FY and Periods
       Period 1 does not create accounting entries since it is the addition period. OK
       On Period 2.
          - Document sequencing related fields are empty.  For this setup, it is expected to have doc type: AM-INF, a sequenced number, and processing date and it has generated for the other processes.
          - As a collateral issue, Process instance field is not populated either for DIST_LN table.  This is important since it helps to keep trail between entries and the process that have been generated.
14.  Check Process monitor.

See replication document here.

NOTE: In the <images or examples> <above or below> and/or the attached document, user details / customer name / address / email / telephone number represent a fictitious sample
(based up made up data used in the Product name test environment). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

Changes

Cause

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