Hi Mfalco 

Mfalco said:

after launching the stock accounting, several of stojou records keep the field PITVALFLG to 0 instead of 2.

Are you sure they are properly posted?
Is running the resynch FUNSYNPIT helps?

Mfalco said:

although I think both are fixed in P34.

I think it is fixed in 23R2. But you should report the behavior on stojou records keeping the field PITVALFLG to 0 to Sage support.

Hi Julien,

About the first point, the stojou are really posted, and I suppose with the proper amounts! 

the FUNSYNPIT function is by range of product, by year and period, so difficult to have an overwiew of the situation, Anyway, I tried with a period in simulation and big range of products and in the trace appear lots of updated records but not much info.

But What is the reason of all those updates? Is that normal to see it if launched to any Folder?  

About the second point, yes, I reported to my spanish sage support but they say needing to replicate it to help us, and that maybe the 23R2 fixes it too.

Those with 0 value are not considered in stock valuation reports by accounting date. If I updated to 2, then ok

I first analized the FUNSTVAPIT called from FUNSTVA of that report, and I saw the FITVALFLG to be filtered to 2 just when used by accounting date range, then, I tried to analize the FUNSTKACC from stock accounting, and I saw that the field was update to 2 in many places, but I've not analized it so deeply as to find the case when is not updated. 

Some are updated others aren't!

Mfalco said:

But What is the reason of all those updates?

Hi Mfalco 

Assuming your question about 'those updates' is about the flag PITVALFLG, you need this flag to ensure the records is taken into account in the PIT (point in time) tables. These PIT tables are the one used when running the stock valuation report with accounting date ticked. The table is different depending on the valuation method of the product:

• ITMCOSTPIT (ITCP) - Standard cost & Revised standard cost
• ITMMVTPIT (ITVP) - Average unit cost
• STOLOTFCYPIT (SLFP) - Lot average unit cost
• STOCOSTPIT (STPP) – FIFO cost & LIFO cost

In a nutshell, if the PITVALFLG is zero, there is a risk that the related stock movement has not updated the total quantities and amounts that you see in the stock valuation report. To check you can try to compare the stock valuation report amount and the stock balance on the same period.

Mfalco said:

Is that normal to see it if launched to any Folder?  

I am afraid I don't understand the question.

Mfalco said:

they say needing to replicate it

This is the standard process to ensure the problem is not linked to a custom modification, you need to be able to replicate at will (on a standard environment).

I understand that finding the replication criteria can be difficult and time consumming. You can contact Sage to have expert assistance from Center of Excellence team but this will be on a billable basis.

Hi  Julien Patureau 

I've updated the p34 STKPITLIB to my p33 customers and it seems by now it works ok.

Also fixed the others errors I mentioned above such as the error @X3.TRT/STKPITLIB$adx (927) Error 7 : Non-existent class [F:STPP]  or (842) Non-existent variable BPSNUM

But, is it possible to resync. massively the *IPT tables, just in case, after have updated those stojou records to 2 ?

Regards

Hi Mfalco,

Yes it is possible to resynch the *PIT tables using either FUNSYNPIT if the fiscal year and period is opened or FUNCREPIT if the fiscal year is closed.

Mfalco said:

have updated those stojou records to 2 ?

If you have already forced the flag PITVALFLG to 2, I am not sure if these resynch tools will work.

Thanks Julien Patureau 

Some doubts about these processes:

About FUNSYNPIT, what imply to mark "Create beginning balance records" ?

And

About FUNCREPIT, "Clear previous data", is it to Delete the previous history?   and "Transfer"  ?

Thanks a lot