REQHEADER Location

 4 Replies
 0 Subscribed to this topic
 38 Subscribed to this forum
Sort:
Author
Messages
LisaLisa
Advanced Member
Posts: 31
Advanced Member

    I have several questions about the requisition tables in Lawson:

    1) Does the REQHEADER.ACCT_UNIT field contain the facility that made the request for an item?

    2) Does the REQHEADER.REQ_LOC field contain the department (within a facility) that made the request for an item?

    3) Does the REQLINE.FROM_LOCATION field contain the location in which the requested item came from?

    Thanks

    Kat V
    Veteran Member
    Posts: 1020
    Veteran Member
      REQHEADER.ACCT_UNIT - is the default value only. If the accounting unit is populated in RQ01 or if the user is manually populating it, then this is what the lines will default to. But the users can change it on the lines.

      REQHEADER.REQ_LOC - is the rq01 - so yes, for us at least, it's the department.

      REQLINE.FROM_LOCATION is also from the RQ01. It's the IC02 tied to the department on RQ01. And again, it can be overridden (mostly by templates) to request stock from other IC02 locations. In our case, it's the dock associated with the Req Loc.
      LisaLisa
      Advanced Member
      Posts: 31
      Advanced Member
        Ok. Thanks, Kat. I need to retreive 2 years of historical inventory data for store rooms that are directly stocked by a warehouse and/or a vendor. I believe the three fields (ACCT_UNIT, REQ_LOC, and FROM_LOCATION) will give me the information that I need; however, I wanted to get clarification on the meaning of the fields.
        Kat V
        Veteran Member
        Posts: 1020
        Veteran Member
          Then yes REQLINE.FROM_LOCATION is where it pulls from. If you also populate REQLINE.VENDOR - if vendor is populated, it was a replenishment order (you can also use create-po) if it is blank, it created a demand against the warehouse populating FROM-Location.
          LisaLisa
          Advanced Member
          Posts: 31
          Advanced Member
            Thanks, Kat!