We're creating API-powered remote data collection for a client with multi-logistics single finance environment. We've successfully created API script for one of the logistics company which only uses hours backflushing. No problem there. However, the other logistics company here uses material backflush on top of hours backflush.
The problem with trying to automate the material backflush is that whether through the Report Operations Completed (tisfc0102m000), Report Orders Completed (tisfc0202m000), or Backflush Materials and Hours (tisfc0220m000), they run Issue Inventory (tisfc0208s000) in the background. tisfc0208m000 shares one program script with tisfc0207m000 and tisfc0207s000. They are 3 sessions with the same name. And when successfully executing them, somehow a report must be printed.
For now, I see 2 options:
- Don't run backflush under API if Backflush Materials flag is set to Yes in production order (eg stpapi.enum.answer("tisfc0102m000","tisfc02023","2") )
- Modify the tisfc0207 script so that it automatically send that rather unnecessary report to a text file without even bothering to ask for printer (using brp.open(spool.report, spool.device, 0) )
I looked through this API forum and only saw threads discussing hours backflush. Anyone can help me with the material backflush, please?