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

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

Manufacturing Data collection (DC)

(0) ShareShare
ReportReport
Posted on by 190
In Manufacturing we are doing Manually DC to get information about Ok an 
Rejection work on each and every opertation with in a Routing. During this 
process i found that DC Activity not attached with my MO, for exemple 
1. I can enter any qty in Piece Ok or Rejected fields even if the Mo Qty 100 
but for the same MO Data Collection can be done for 1000pcs.
2. In data collection form no information about MO Quantities.
3. As my operations are based on piece work bases and each operation in 
routing have diffrent rates as well labor, so when I am entring the MO 
receipt entry again there is no link between data collection and MO Receipt 
entry. Logically here i want to receive only OK qty in my stock and rejection 
treatment seprately but with in MO qty i can receive any qty what ever i want 
(only not more then Mo Qty)
4. the Most serious effect is coming on costing, if the Mo qty is 100 and 
data collection is for 1000, the labor cost for one thousend will appear as 
collected cost and if my clerk will receive 100 pcs whole cost will be 
applied on these 100 pcs.

I am unable to understand this data collection what for? if it have no 
Quantitative link with MO? Is this possible that system restrict my clerk not 
receive more qty then the Ok pcs entered during DC and DC qty should not be 
more then MO qty either Ok or Rejected?
Pls guide us because we are facing problem in this regard

*This post is locked for comments

I have the same question (0)
  • Richard Whaley Profile Picture
    25,195 on at
    Re: Manufacturing Data collection (DC)

    In many manufacturing firms, MOs are over or under produced.  Thus it is necessary to allow an MO to be created for 100 pieces and allow the reporting at any step of any quantity.  Frequently shops will complete 110 in the first step, the 108 in the second, 105 in the third, and finally report 102 into inventory.  The losses are production errors and the system does not limit the reporting to the quantity ordered.  Some shops even produce more finished goods that the raw materials that are issued to the MO provides as they pick up scrap from the shop floor for small items.

    Costing is a more complex issue and depends on the valuation method you use.  What valuation method are you using?

    Paying Piece Work can be tricky.  Manufacturing concerns itself primarily with the collection of costs of building the final parts and not directly with paying people.  Your data collection raw transactions are recorded and perhaps you should be looking at the raw postings to determine who completed how many pieces.  You will need to perform the quality review of the work before posting the transaction to the router step as corrections are not tied to any particular initial transaction in GP.

    We have a book on Manufacturing Cost Accounting in Dynamics GP that explains how the system costs items.  It does not specifically cover paying piece workers but it will provide you an understanding of how the software works.

     

  • Suggested answer
    Redbeard Profile Picture
    12,931 on at
    RE: Manufacturing Data collection (DC)

    Malik - there is no setting in the preferences for this window to restrict users from entering pieces in excess of the required quantity on the work order.  This would require customization.  I would recommend any modification not prevent, but rather warn of the quantity required is exceeded (perhaps a tolerance allowing minor overruns). When we require improvements to GP Manufacturing windows, we use WilloWare.com.  They are very capable and understand the intricacies of Dynamics GP Manufacturing.  

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…

Abhilash Warrier – Community Spotlight

We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans