Skip to content

x Want to participate? Join the group to interact
  • State Not Answered
  • Replies 3 replies
  • Subscribers 128 subscribers
  • Views 389 views
  • Users 0 members are here
Browse Forums
Announcements
289
topics
43
replies
General Discussion
5k
topics
15k
replies
Sage Data & Analytics
46
topics
108
replies
Sage Enterprise Intelligence
183
topics
479
replies
Sage Intelligence Reporting
116
topics
325
replies
Evan Armstrong

DEMDLVDAT & SHIDAT off by a year in December

Posted By

DEMDLVDAT & SHIPDAT is populating in SAGE but is off by a year. 


We placed an order on 2024-11-19 (ORDDAT & VCRINVCNDDAT - 20241119).  We passed a final arrival date (FINDELDAT) of 2025-01-02 and an appointment date (ZPDATEAPP) of 2025-01-06


SHIDAT updated to 2025-12-30, rather than 2024-12-30

DEMDLVDAT updated to 2025-12-31, rather than 2024-12-31


Can anyone advise what the issue might be, pls? 

  • 0

    Hi Evan,

    I'd check if any customizations causing this issue. You mentioned the following "We passed a final arrival date (FINDELDAT) of 2025-01-02 and an appointment date (ZPDATEAPP) of 2025-01-06".

    Second, I would check if the users are updating the Sales order Delivery address after the order is generated ?

    And does it have different work days for each of the delivery addresses?

  • 0

    Hi Joel. Thanks for getting back. Apologies for the delayed reply. 

    What would be possible customizations to check?  Could the load calculation / product-lead-time be causing this? 

  • 0 in reply to Evan Armstrong

    Hi Evan,

    Do you see any delivery LT on the sales order header or lines?

    Delivery LT is set up at the delivery address level.

    You can disable the SPE codes in the SOH* screens and test the behavior to rule out any customizations.

    Also check if there are any entry points.

    If you can replicate the behavior in SEED, please enter a support ticket.

*Community Hub is the new name for Sage City