x Want to participate? Join the group to interact
  • State Suggested Answer
  • +1 person also asked this people also asked this
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 138 subscribers
  • Views 1637 views
  • Users 0 members are here
Browse Forums
Announcements
237
topics
29
replies
General Discussion
5k
topics
13k
replies
Sage Data & Analytics
56
topics
95
replies
Sage Enterprise Intelligence
211
topics
418
replies
Sage Intelligence Reporting
121
topics
322
replies
Denise Hartman

Production Tracking Import

SUGGESTED
Posted By

I and working on a web service to create production tracking transactions in X3.  The standard X3 object as a web service does not work well, because it causes pop-ups that cause the web service call to fail.  So I'm doing import templates from the web service.  The problem is, for production tracking, it appears as though there is a separate import template for each of Operations Tracking, Production Tracking and Material Consumption.  As a result, the web service ends up creating 3 separate production tracking records instead of one.  I have tried using the import template in update mode, so I can re-use the first production tracking number created to add the materials, production, etc to an existing tracking, but that doesn't seem to work.  Am I missing something? Is there an import template that does all three?  I also made a copy of the standard import templates and changed the standard import template so update is allowed (it's unchecked by default), but that doesn't work either.

  • 0

    We ran into similar issue, and have not had any luck to accomplish what you are describing, but I want to share with you what we learned and hopefully it would help you further you search on a solution.

    When you are importing for production tracking, the system needs to know which entry transaction to use for the import. This setup is under generation parameter MKITRSNUM, MKMTRSNUM and MKOTRSNUM. If you look closely on the choices you have on these parameters, you will find that they are NOT entry transactions of the production tracking function, but entry transactions for "Production Tracking Plan", "Time Tracking Plan", and "Material Tracking Plan" functions. So when you using these MKM, MKI, MKO import templates, they are not mimicking the behavior of entering through the production tracking function, but mimicking the behavior of these "Tracking Plan" functions, which do not track anything other than what they are designed for. 

  • 0 in reply to Mike Tsai
    SUGGESTED

    Note you can trigger material backflush and automatic production tracking from the time tracking import (MKO). For this you need to adapt the setup of the time tracking plan used.

  • 0 in reply to Julien Patureau
    SUGGESTED

    That's a very good point. Thank you, Julian. Now that you mentioned this, instead of reporting production and time separately, we did eventually use MKO to report both Production and Time.  But since we want to track actual consumption, it has to be reported under a different tracking record. 

  • 0 in reply to Mike Tsai

    Yes, we also want to report actual production, so the automatic trigger doesn't work.

*Community Hub is the new name for Sage City