Fixing order and date is allowing change in MAD .

[former_member906762]

Hello All ,

                    Currently we are fixing order quantity and date  on the line item which would skip BOP but when we manually run ATP on the line item APO is giving a new MAD date even when the Fixed order Quantity is checked on the sales order line item . Is there a configuration which would prevent the line item from getting REATP . the issue is further discussed below .

Availability Check  does not honor Schedule Line "Fixed date and qty" flag

When the schedule Line "Fixed date and qty" flag is true, BOP honors this setting by not rescheduling the line if it has a confirmation. When in ECC and performing a manual "Check Availablity", APO sends back a new MAD.

Is there "standard" configuration on ECC/APO, that will disallow a MAD date change on a "Fixed date and qty" order line. If there is not, std config, is there an exit (on ECC/APO) that we can used to accomplish this?.

Regards,

NICK

[Former Member]

Nick,

 Availability Check  does not honor Schedule Line "Fixed date and qty" flag

This is not true. normal FDQ flag behavior is exactly as you have described.  FDQ flag does not mean that the confirmation date is 'locked', it only means that someone has made a business decision to use the existing confirmation date for planning purposes, and the customer's requested date is no longer the goal.. ERP rescheduling, and APO BOP, will generally not attempt to reschedule these confirmations..

However, like a fixed planned order, the confirmation dates of a schedule with the FDQ flag set can be manually overridden.  This is a 'feature', not a bug.  It would be quite cumbersome if the user had to un-set the FDQ flag on the schedule every time he needed to perform an ATP.  Most companies find it necessary to perform manual sales order rescheduling all the time, based upon changes requested by the customers.  Before you embark upon this path, make sure you know what you are getting into.

Anyhow, as you mentioned, SAP has userexits that can alter ATP behavior.  I have never tried this particular mod, but the first place I would look would be APO userexit APOAT005.  Make sure you have fully defined your business rules before you ask a programmer to create his code.

Best Regards,

DB49