cancel
Showing results for 
Search instead for 
Did you mean: 

APO sales order date error with Brazilian daylight time

Former Member
0 Kudos

Dear all,

We have a problem in APO with sales orders with scheduling line date in the beginning of Brazilian daylight time.

When the order is created using VA01 there is the error u201CCustomer requirement: Schedule line has invalid time stamp u201C in the APO inbound CIF queue.

Using delta report (transaction /SAPAPO/CCR) there is error: Order: Difference in material availability date (APO: 15.07.2011 03:00:00 <-> R/3: )

We have updated the notes below, without success.

1408304 Invalid schedule line (01.01.1970) with daylight saving

1547603 Inconsistent Time stamp conversion with Day Light savings

Can you help us?

Thanks in advance.

Januario Faria

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

Hi Hubert,

Should we do this change in which environment?

ECC, APO or both?

Thank you very much.

Januario Faria.

Former Member
0 Kudos

Hello Hubert,

Iu2019ve Just talked about your suggestion with our Basis consultant and he has some questions:

1. The table TTZDV has only YEARFROM field. There is no YEARTO. How to delete the old entry valid from 1998 to 2010?

2. Did you updated the data directly in the table or did you use the transactions like STZBC?

Thank you very much.

Januario Faria

hubert_spohn
Active Participant
0 Kudos

Hi Januario,

- use STZBC for maintaining the data

- delete both entries for the current setting

- create one new entry valid from 1998

Regards.

Hubert

Former Member
0 Kudos

Hi Hubert,

Thanks for your replay.

We have two records in this table. One of them with yearfrom 1998 and another one with 2010.

According to our basis team we have created it to adjust some changes that occurred in 2010 Brazilian daylight time.

Regards.

Januario Faria.

hubert_spohn
Active Participant
0 Kudos

Hi,

I suggest to change the data:

  • delete the old entry valid from 1998 to 2010

  • change the new entry and make it valild from 1998 to 9999

This should be no problem because you hopefully do not have any more active data in the system in the past.

We have had a similar problem in our system and have got this solution from SAP when creating an OSS request.

From my point of view it's a SAP bug, anyway the workaround has fixed the problem.

(at least it seems to be a problem in the kernel because the ABAP command

CONVERT DATE ... INTO TIME STAMP delivers the wrong result in that case)

Best regards.

Hubert

hubert_spohn
Active Participant
0 Kudos

Hello,

please check in table TTZDV the field 'yearfrom' for your daylight saving rule.

This year should be 1998.

Regards.

Hubert

Former Member
0 Kudos

Dear Tibor

Thanks for your reply.

We have run the report /sapapo/sdrqcr21 without success.

Regards,

Januario Faria

tibor_nagy
Contributor
0 Kudos

Dear Januario Faria

to correct these customer requirements I would propose to run the report /sapapo/sdrqcr21 with the option 'check SD order tables'.

For further help the queue should be analyzed deeper.

You can find further help regarding the dates in APO here:

http://help.sap.com/saphelp_scm70/helpdata/EN/89/e8693728e52456e10000009b38f889/frameset.htm

Regards,

Tibor