web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics NAV (Archived)

dimension value code requirement

(0) ShareShare
ReportReport
Posted on by 65

Our process of posting our purchase orders require dimensions as well as tagging to what job no this transaction pertains to. In the purchase lines, we use G/L account type. In addition, we have defaulted in the G/L account cards a particular dimension which is DEPARTMENT. we indicated CODE MANDATORY in the default dimension table so as to require dimension value first before it can be posted as RECEIVE & INVOICE. however, we encounter error in posting the purchase orders. the error goes this way "SELECT A DIMENSION VALUE CODE FOR THE DIMENSION CODE DEPARTMENT FOR THE G/L ACCOUNT 78111006".

we have indicated  "G/L account" in the type field and "78111006" in the No. field. then the job no, job task no., job line type, job price, quantity, direct unit cost excl. of vat. then we also have indicated the dimensions both for purchase header and the purchase line. yet we still encounter this error. 

we have already isolated the problem only to posting the purchase order with mapping to jobs. coz we already tried posting purchase orders without mapping to jobs and it pushes through.

what could be the source of this problem? thanks   

*This post is locked for comments

I have the same question (0)
  • Daniel Rimmelzwaan Profile Picture
    3,485 on at

    Typically, a PO is assigned to a job in the header, and this flows into the lines. I believe that standard NAV does not like having different jobs in different lines for the same PO. AFAIK standard NAV does not even provide the job fields in the line form, so that seems to have been added to your system.

    What I would do is debug the process and see how your dimensions flow through the system, and try to discover why it is that they are not included when it gets to the error message. If I were to venture a wild guess I would say it's probably somewhere in a custom posting process, where a journal is filled without including dimensions.

  • Dhan Raj Bansal Profile Picture
    679 on at

     

    Daniel,

    Just wanted to mention that "Job No." field is there in Purchase Lines also..

  • Daniel Rimmelzwaan Profile Picture
    3,485 on at

    Sure, and I am saying that this was added by someone, because in my standard NAV database the Job number is not provided on the line.

    Did you debug the process yet?

  • emer ladines Profile Picture
    65 on at

    Hi Daniel!

     my teammates were able to find an article relating to this in the knowledgebase. it required to modify code unit 90 (Purch.-Post).

     it was really a bug.

     from the knowledgebase please refer to article 939462.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics NAV (Archived)

#1
HoangNam Profile Picture

HoangNam 7

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans