Feedback-ID: i76984098:Fastmail
Message-ID: <adddb99c-448a-4a6e-a1d1-ab8c50b6c073@aklaver.com>
Date: Thu, 8 Aug 2024 09:56:25 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Destination Table - Condition Amount 0
To: Anthony Apollis <anthony.apollis@gmail.com>,
 pgsql-general@lists.postgresql.org
References: <CAJyMCYJ9GJvJoY9MGvzyf-gO9ZnAwVrZSgrPfn0dGaChdb93HA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAJyMCYJ9GJvJoY9MGvzyf-gO9ZnAwVrZSgrPfn0dGaChdb93HA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/adddb99c-448a-4a6e-a1d1-ab8c50b6c073%40aklaver.com>
Precedence: bulk

On 8/8/24 09:35, Anthony Apollis wrote:
> I need your assistance with an ETL process that runs every six months. 
> Currently, we are in Calendar Year/FY 2025, which started in July 2024.
> 
> The issue is with the "Condition Amount" for FY 2025. Data comes through 
> correctly until the "Insert Data Into Task" step (please see the 
> attached screenshot). However, it appears that the code responsible for 
> the "Update PD Credit" step is not functioning as expected.
> 
> image.png
> 
> 
> The destination table [Turkey - NCD Revenue Reporting Model_Table_Model] 
> is receiving data for FY 2025, but the "*Condition Amount*" column 
> contains zeros for 2025. Please see the attached sample data for reference.
> 
> To help diagnose the issue, I have included the following:
> 
> DDL for all three tables.
> 
> Insert/Update scripts for the two tasks as depicted in the screenshot above.
> 
> Sample raw data for the two tables.
> 
> SSIS can also be found attached for better understanding
> 
> Sample data for the "Insert Data Into
> 

Honestly I have not looked through all the files and probably won't. I 
did find this though:

CASE
         WHEN NCD_EXCL."Order Quantity" IS NULL OR NCD_EXCL."Order 
Quantity" LIKE 'Excluded' THEN
             0
         WHEN NCD_EXCL."Order Quantity" LIKE 'NCD Valid' THEN
             NCD_AMOUNT."Condition Amount"
         ELSE
             0

which looks suspicious in that it can turn a "Condition Amount" into 0.

I would start by running the SELECT that this is part of and seeing what 
it does to the data and if that is what you want it to do.

-- 
Adrian Klaver
adrian.klaver@aklaver.com