Skip to main content
All too often, a customer will ask us about the relationship between the date fields on a customer order line and what one should or can be able to change and what the ultimate effect of those dates are elsewhere in the system. The help text can be rather unclear on these fields; target date on the customer order. It would be nice if we had a quick reference on these fields and what field should be changed and when. It would be nice to know what roles would or should change what dates. Thanks!
I hear you on this. We took a let’s define it ourselves approach. Hiding field that were not relevant. That help but hasn’t fully solved the issue. You really need to understand the backwards scheduling and the lead times to get the full use of the application.
In our organization - we frequently are entering requested wanted date on POs pegged (supply codes PO Transit and O Direct) to customer orders based on the business needs. What we figured out was



If we enter the PO wanted date in the customer order line Target Date, that flows to the Planned delivery date on customer order line - which then flows to Wanted Receipt Date on the requisition line created - which then makes it to the PO line.

Does anyone have the information on how dates impact the Customer Order Lines if changed?

All too often, a customer will ask us about the relationship between the date fields on a customer order line and what one should or can be able to change and what the ultimate effect of those dates are elsewhere in the system. The help text can be rather unclear on these fields; target date on the customer order. It would be nice if we had a quick reference on these fields and what field should be changed and when. It would be nice to know what roles would or should change what dates. Thanks!

Reply


Terms & ConditionsCookie settings