cancel
Showing results for 
Search instead for 
Did you mean: 

Error:Data inconsistency: Time stream ITALLSC7D no longer in database table

Former Member
0 Kudos

HI All,

I have a problem with a time stream that I have created in APO and attached to a number of locations in the shipping calendar.

Each time heuristics is executed in batch jobs, we receive the subject error. APO does not make clear if the error relates to all product / locations or the error is specific to one product / location.

The time stream is still clearly available to be used and is assigned to a number of shipping locations.

We have othere time streams that are created in exactly the same way which DO NOT give this error so I dont think it is anything t

o do with them being created incorrectly.

Last week I tried deleting this time stream and completely recreating yet still we receive this error.

The performance assistance shows the following message:

Data inconsistency: Time stream ITALLSC7D no longer in database table

Message no. /SAPAPO/SNP326

We are using SCM release 5

Has anyone had this issue and can you advise the possible causes.

Thanks

Mark

Accepted Solutions (1)

Accepted Solutions (1)

tibor_nagy
Contributor
0 Kudos

Dear Mark,

Generally speaking, error message 'Time stream ITALLSC7D no longer in database table' means that there is at least one time stream which is generated without a valid time range.

Possible reason for this error that for specified product and location you have maintained a SNP Production Horizon e.g. 999 Days. But the TimeStream exists lesser than the expected planning horizon end date for specified product and location.

In this case you have two options:

1. You have to extend the time stream

2. You can reduce the SNP Production Horizon in the production master

so that the planning horizon ends before time stream end date.

Please run Model consistency check using transaction /SAPAPO/CONSCHK

Please also make sure that the following conditions are met:

1) The planning calendar has the same number of years in the future/

past than the factory calendar

2) The years in past or in future of the planning calendar or

of the factory calendar are wide enough.\

Check also notes 996713 and 1240854 if they are implemented in your system.

Regards,

Tibor

Answers (0)