Automatic Report shipping- Inconsistency period message for program RCVDDISP

[ashish25bp]

Hello Experts

I am getting ' Date inconsistency' in the log message for Subsequent shipping after the periodic run of program RCVDDISP (The job is set for this program).

• The relevant environment parameters (e.g Last Export Date or Subsequent shipping date) are auto set correctly with current date.
• The customization is also correctly done as per SAP documentation.
• The subsequent shipping function is also working correctly for e.g When I create a new relevant version (2.0 to 3.0) , system is triggering subsequent shipping correctly and processed successfully in CVD1.

But not sure why this log message appears for inconsistent date.

Regards,

Ashish

[Mark-Pfister · Accepted solution]

Hello ashish25bp ,

The report expects a date before today's date. It exports reports from the last run date - to yesterday! (As it is only date precise and not stores the second it was last run)

Maybe the report ran already today?You have scheduled the job more than once per day?

Best

Mark

[ashish25bp · Accepted solution]

Thanks for the suggestion. I have setup a report to run once per day at midnight and the inconsistency message has stopped. Now the message looks like this and I assume this should be correct.

[ashish25bp]

Thanks Christoph and Mark,

I agree to the points suggested, and the fact is even today also subsequent shipping is working correctly with one day difference. For e,g If I create a new Main version today V2 to V3 , the subsequent shipping takes place after one day only, it means tomorrow. If that is the case, the message in program RCVDDISP dose not provide any relevant hint to the issue. But let me reschedule the job to run only the next day to bring it to the one day difference as suggested above.

[Mark-Pfister]

That is "working as designed" as the saying goes: Reports created today can only be exported the next day!

This is due to the fact that all time stamps in SAP EHS are only have day 'precession' - there is no information about at what second the report was released. Therefore a program could never decide if it already exported the report already or still has to export it (without looking into the export history - which is not how the program is designed...)

[christoph_bergemann]

Hello Ashish

the "enivronment parameter" is "special".. (e.g. refer to: https://www.sapdatasheet.org/abap/cus0/ehs_md_100_3.html)

If i remember correct.

This parameter should support (I believe) the "EXP_CALL" process; based on "error" message (and using some assumptions") we have:

09.04.2023 - 10.04.2023 as the "period"; I found by hazard only this:

https://www.michaelmanagement.com/sap-error-messages/en/dv/dv552.

Question: i would assume that the process was "ok" "Yesterday" and "now" it is getting wrong; was there any change in "ABAP" or Customizing which could be the reason of the "error"

Based on your "detail" screen. Normally there must be at least a day difference between "current" date and last export. And this seems not to be the case

C.B.