Change SO/PO Creation in NAV for Mileage and Storage

[nmfujimoto]

Estimate work required to change SO/PO creation in NAV to only send the mileage and storage values if the price/cost record for Mileage or Storage is added to a job.

When the user selects to add the price/cost Mileage or Storage charge code to a job, populate the quantity value with the current value for mileage or storage.

[nmfujimoto]

Mileage charge code contains "MIL" at the end, similar to Delivery charge containing "DEL" at the end.

Storage charge code contains "STO" at the end.

Do NOT create SO/PO line item for mileage or storage, just send the values in the SO/PO header. Need to verify with NAV consultant if we need to create the line item record for the mileage or storage.

[prashantaggarwal1999]

@nmfujimoto Estimate for this is 2 working days as we need to Handle Logic while creation of SO/PO and need to add condition on Storage and Milage Line Item add.

[nmfujimoto]

Please begin work and make the changes.

Thank you,

Nathan Fujimoto @.**@.> Business: (951) 268-2190 Cell: (951) 616-9271

[fm_meridian_branding_logo_filled_small_v1]

From: Prashant Aggarwal @.> Sent: Thursday, April 22, 2021 10:51 PM To: meridianww/M4PLBase @.> Cc: Nathan Fujimoto @.>; Mention @.> Subject: Re: [meridianww/M4PLBase] Change SO/PO Creation in NAV for Mileage and Storage (#502)

@nmfujimotohttps://github.com/nmfujimoto Estimate for this is 2 working days as we need to Handle Logic while creation of SO/PO and need to add condition on Storage and Milage Line Item add.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/meridianww/M4PLBase/issues/502#issuecomment-825405132, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AMAOXVF26VMHOWFGKOIDUF3TKEDD5ANCNFSM43LSWCZA. [ { @.": "http://schema.org", @.": "EmailMessage", "potentialAction": { @.": "ViewAction", "target": "https://github.com/meridianww/M4PLBase/issues/502#issuecomment-825405132", "url": "https://github.com/meridianww/M4PLBase/issues/502#issuecomment-825405132", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { @.": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

[prashantaggarwal1999]

@nmfujimoto changes are committed for this, Please review once and let us know for any change.

[nmfujimoto]

@prashantaggarwal1999 we need to discuss in our meeting.

Changes:

• Mileage, Storage and Quantity (Actual) will be sent in the header. For mileage and storage, only send in the header if the price/cost charge record exists.
• If a user adds a Mileage or Storage charge to a job set the Quantity field to read-only with the value of 1