Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. The Capable-to-Promise function calculates an earliest shipment on a weekend for a working week unexpectedly if the Outbound Whse. Handling Time is added in Microsoft Dynamics NAV

The Capable-to-Promise function calculates an earliest shipment on a weekend for a working week unexpectedly if the Outbound Whse. Handling Time is added in Microsoft Dynamics NAV

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for all language locales.

↑ Back to the top

Symptoms



Consider the following scenario in Microsoft Dynamics NAV:
  • You have a sales order that uses the Order Promising function (Capable-to-Promise).
  • The customer has a Working Week Calendar Setup (Monday to Friday).
  • A "Outbound Whse. Handling Time" setup is specified on the location card.
 In this Scenario, the Capable-to-Promise function is used to calculate an earliest shipment date because of the shipment date of the "Outbound Whse. Handling time" setup is suggested on a weekend. This is incorrect because the Calendar Setup is not considered.
This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1(SP1)
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 5.0 Service Pack 1(SP1)

↑ Back to the top

Resolution

Hotfix information

A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 2009 service pack or the next Microsoft Dynamics NAV version that contains this hotfix.

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

↑ Back to the top



Installation information


Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure. However, they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.

Note Before you install this hotfix, verify that all Microsoft Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. You should be the only client user who is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.

We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" role ID, you must verify that the user account has the following permissions:
  • The Modify permission for the object that you will be changing.
  • The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.


Note You do not have to have rights to the data stores unless you have to perform data repair.

Code changes

Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To resolve this problem, follow these steps:
  1. Change the code in the ValidateCapableToPromise function in the codeunit (99000886) as follows:
    Add the following parameter in the function:

    • VAR: Yes
    • Name: DueDateOfReqLine
    • DataType: Date

    Add the following local variable:
    • Name: Ok
    • DataType: Boolean
    Existing code
    ...
       END;
    // Delete the following line.
    EXIT(CheckDerivedDemandCTP(ReqLine,PeriodType)); 
    // End of the deleted line.
    ...
    Replacement code
    ...
      END;
    // Add the following lines.
    Ok := CheckDerivedDemandCTP(ReqLine,PeriodType); 
    IF Ok THEN 
      DueDateOfReqLine := ReqLine."Due Date"; 
    EXIT(Ok); 
    // End of the added lines.
    ...
  2. Change the code in the CalcCapableToPromise function in the codeunit (99000886) as follows:
    Add the following local variable:

    • Name: DueDateOfReqLine
    • DataType: Date
    Existing code 1
    ...
      IF NOT
       ValidateCapableToPromise(
        ItemNo,VariantCode,LocationCode,CalculationStartDate,
    // Delete the following line.
        NeededQty,UnitOfMeasure,"Order Promising ID",PeriodType) 
    // End of the deleted line. 
    ...
    Replacement code 1
    ...
       IF NOT
       ValidateCapableToPromise(
        ItemNo,VariantCode,LocationCode,CalculationStartDate,

    // Add the following line.
        NeededQty,UnitOfMeasure,"Order Promising ID",PeriodType,DueDateOfReqLine)
    ...
    Existing code 2
    ...
        RemoveReqLines("Order Promising ID","Source Line No.",OrderPromisingLineToSave,FALSE);

    // Delete the following lines.
       IsValid :=         ValidateCapableToPromise(ItemNo,VariantCode,LocationCode,CalculationStartDate, 
         NeededQty,UnitOfMeasure,"Order Promising ID",PeriodType); 
    // End of the deleted lines.   
    ...
    Replacement code 2
    ...
          RemoveReqLines("Order Promising ID","Source Line No.",OrderPromisingLineToSave,FALSE);

    // Add the following lines.
       IsValid := 
        ValidateCapableToPromise(ItemNo,VariantCode,LocationCode,CalculationStartDate, 
         NeededQty,UnitOfMeasure,"Order Promising ID",PeriodType,DueDateOfReqLine); 
    ...
    Existing code 3
    ...
          ValidateCapableToPromise(ItemNo,VariantCode,LocationCode,CapableToPromiseDate,

    // Delete the following line.
        NeededQty,UnitOfMeasure,"Order Promising ID",PeriodType); 
    // End of the deleted line.

      END;
      CalculationDialog.CLOSE;
    ...
    Replacement code 3
    ...
         ValidateCapableToPromise(ItemNo,VariantCode,LocationCode,CapableToPromiseDate,

    // Add the following line.
        NeededQty,UnitOfMeasure,"Order Promising ID",PeriodType,DueDateOfReqLine); 
    // End of the added line.

       END;
       CalculationDialog.CLOSE; 
    ...
    Existing code 4
    ...
       CapableToPromiseDate := CalculationStartDate;
     LastValidLine := GetNextOrderPromisingLineNo; 
    ...
    Replacement code 4
    ...
        CapableToPromiseDate := CalculationStartDate

    // Add the following lines.
    IF CapableToPromiseDate <> DueDateOfReqLine THEN 
      CapableToPromiseDate := DueDateOfReqLine; 
    // End of the added lines.
     
    LastValidLine := GetNextOrderPromisingLineNo; 
    ...
  3. Change the code in the CheckCompsCapableToPromise function in the codeunit (99000886) as follows:
    Add the following local variable:

    • Name: DueDateOfReqLine
    • DataType: Date
    Existing code
    ...
          ValidateCapableToPromise(
        "Item No.","Variant Code","Location Code","Due Date",

    // Delete the following line.
        "Expected Quantity","Unit of Measure Code",OrderPromisingID,PeriodType) 
    ...
    Replacement code
    ...
       ValidateCapableToPromise(
        "Item No.","Variant Code","Location Code","Due Date",

    // Add the following line.
        "Expected Quantity","Unit of Measure Code",OrderPromisingID,PeriodType,DueDateOfReqLine) 
    ...
  4. Change the code in the CheckTransferShptCTP function in the codeunit (99000886) as follows:
    Add the following local variable:

    • Name: DueDateOfReqLine
    • DataType: Date
    Existing code
    ...
          ValidateCapableToPromise(
        "No.","Variant Code","Transfer-from Code","Transfer Shipment Date",

    // Delete the following line.
         Quantity,"Unit of Measure Code",OrderPromisingID,PeriodType) 
    ...
    Replacement code
    ...
        ValidateCapableToPromise(
      "No.","Variant Code","Transfer-from Code","Transfer Shipment Date",

    // Add the following line.
       Quantity,"Unit of Measure Code",OrderPromisingID,PeriodType,DueDateOfReqLine)  
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1(SP1)
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 5.0 Service Pack 1(SP1)


Removal information

You cannot remove this hotfix.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

↑ Back to the top

Keywords: kbmbspartner, kbmbsmigrate, kbmbscodefix, kbqfe, kbsurveynew, kbmbsquickpub, kb

↑ Back to the top

Article Info
Article ID : 2646285
Revision : 1
Created on : 1/7/2017
Published on : 1/10/2012
Exists online : False
Views : 267