Open Forum

Expand all | Collapse all

Purchase Orders

  • 1.  Purchase Orders

    Posted 16 days ago
    Hello all!

    We feed our NAV information into several BI reports for operations. Our warehouse partner is asking us to note when we are sending stickered inventory to them so that it can be easily identified. Since the report for the warehouse partner pulls information from the purchase order lines (basically, it's a report telling them what you expect and when to expect it), I'm looking for a "throwaway" field on the purchase order lines that our ops person can enter to differentiate between the normal inventory and stickered inventory (it's the same EAN/Item No). It can't be in the header because our POs are for both stickered and non-stickered inventory.

    I don't want to use a field like Variant that would ever affect other areas, since our sales distributor does not tell us when stickered inventory versus non-stickered inventory sells in our sales import. I'm not sure how Bin No. works, but if it's like Variant, we will never receive reporting that indicates sales from a particular bin, and I also will never want to need to reconcile bins against each other and do inventory transfers between Bins and have cost differences and such.

    So does anyone have a good field to use? I know we can always use Dimensions if necessary, but it would be really nice to just populate a "regular" field on the purchase order line for data entry efficiency!

    Thanks!

    ------------------------------
    Kim Berardi
    McEvoy Group
    New York NY
    ------------------------------


  • 2.  RE: Purchase Orders

    TOP CONTRIBUTOR
    Posted 16 days ago
    Kim,

    You should add a new Boolean field: "Stickered".  You have a mostly unlimited number of User Defined fields.  By adding your own field you avoid the possibility of Microsoft removing or changing that field.  Shouldn't take more than 5 minutes to add the field, and a little bit longer to include it in what you send to your warehouse partner.

    ------------------------------
    Ben Baxter
    Consultant
    Accent Software, Inc.
    carmel IN
    ------------------------------



  • 3.  RE: Purchase Orders

    Posted 16 days ago
    Sorry, I should mention that we are using NAV 2017 in a hosted multi-tenant environment, so I don't think we are able to make those types of changes.

    ------------------------------
    Kim Berardi
    McEvoy Group
    New York NY
    ------------------------------



  • 4.  RE: Purchase Orders

    Posted 16 days ago
    Kim

    Do you have development access to the application database? if yes, then follow Ben's suggestion above. The thing about multi-tenant environments is the separating the application from the data. The objects live in the application database.

    Good Luck!

    ------------------------------
    Alfredo Zelaya
    Sr. Systems Analyst
    Megadyne Americas LLC
    Fairfield NJ
    ------------------------------



  • 5.  RE: Purchase Orders

    Posted 16 days ago
    I will check with our vendor, thank you!

    ------------------------------
    Kim Berardi
    McEvoy Group
    New York NY
    ------------------------------



  • 6.  RE: Purchase Orders

    TOP CONTRIBUTOR
    Posted 16 days ago
    Unfortunately, most all the fields on the purchase line table are used for specific purposes and trying to repurpose a field can lead to problems.  This is why Ben suggested the new field.  If that really is not possible, you might be able to use the "Purchasing Code" field to capture stickered product.  Just set up a code and leave the "Drop Shipment" and "Special Order" flags unchecked.  Then, you can add the new code to any lines where the product is stickered.  Unfortunately, this solution only works if you don't need the "Purchasing Code" to deal with drop shipments and/or special orders.  If your company does neither, than this approach may work.  If your company does either, the new field is still the best option.

    ------------------------------
    David Wiser
    Project Manager
    Tigunia
    Seattle WA
    ------------------------------



  • 7.  RE: Purchase Orders

    TOP CONTRIBUTOR
    Posted 16 days ago
    I agree with @david wiser so that no development is involved. Great idea David!​​

    ------------------------------
    Kim Dallefeld
    Kim@Dallefeld.com
    Dallefeld Consulting, LLC
    Member of Dynamics Consulting Group
    Ft. Worth, TX
    2019 NAVUG Board of Advisors
    Past NAVUG Board Chairman
    NAVUG Programming Committee
    ------------------------------



  • 8.  RE: Purchase Orders

    TOP CONTRIBUTOR
    Posted 15 days ago
    Use the line item notes. This will tie the note to the parent line for an easier tie to the parent line.



    Sent from my Verizon, Samsung Galaxy smartphone





  • 9.  RE: Purchase Orders

    Posted 15 days ago
    HI Kim,

    Adding new field will be a better solution,you can either ad option field or boolean field to differentiate.

    ------------------------------
    Maneesha Agrawal
    AlleTechnologies Inc.
    McLean
    ------------------------------



  • 10.  RE: Purchase Orders

    TOP CONTRIBUTOR
    Posted 13 days ago
    Just curious as to 'why' you would add a field versus using and existing field.

    ------------------------------
    Kim Dallefeld
    Kim@Dallefeld.com
    Dallefeld Consulting, LLC
    Member of Dynamics Consulting Group
    Ft. Worth, TX
    2019 NAVUG Board of Advisors
    Past NAVUG Board Chairman
    NAVUG Programming Committee
    ------------------------------



If you've found this thread useful, dive deeper into User Group community content by role