WorkTask Repsting in IFS10 | IFS Community
Solved

WorkTask Repsting in IFS10

  • 13 November 2020
  • 10 replies
  • 384 views

Userlevel 6
Badge +13

Hi Team,

There is new new functionality of re-posting in Maintenance module in work task.

This functionality trigger TP3 posting after Invoices gets matched, Is there is an option not to use/stop this re-posting functionality in Work Task.

Regards,

Mukesh Gupta

icon

Best answer by MKG019 14 November 2020, 07:16

View original

10 replies

Userlevel 6
Badge +13

Able to manage and resolved internally.

Userlevel 5
Badge +9

Hi, are you able to provide some info about how you managed to resolve it? Our finance team have also noticed the new reposting and its making life pretty hard, filling the GL with literal thousands of lines...

Userlevel 7

Hi, are you able to provide some info about how you managed to resolve it? Our finance team have also noticed the new reposting and its making life pretty hard, filling the GL with literal thousands of lines...

This will only happen if you use WIP handling on the work tasks. I’m guessing you have setup Task Cost Codes with at least one used as WIP code? 

Userlevel 5
Badge +9

Hi @anmise we don’t seem to have any WTCC’s. Also seem to have no WIP vouchers in the system either.

We do have someone looking at it I think, but its been an ongoing issue for a little bit without any answers yet.

Userlevel 7

Hi @anmise we don’t seem to have any WTCC’s. Also seem to have no WIP vouchers in the system either.

We do have someone looking at it I think, but its been an ongoing issue for a little bit without any answers yet.

Is that your only company? What did you then mean that finance has raised as an issue?

From help:

 

Transfer work task transactions with transaction type; and transaction status: Reposted or Overtake.

  • Work task transactions of type Reposting is a result of a transactions which has been reposted and requires to be transferred to finance.
  • Work task transactions of type Overtake is a result of a work task transaction which has been created and where the original posting has been reversed and overtaken by a work task posting type. This is used for postings which hasn't a work task specific posting type for its orginal transaction. A work task transaction that has been overtaken is required to be transferred to finance.
Userlevel 5
Badge +8

Hi, are you able to provide some info about how you managed to resolve it? Our finance team have also noticed the new reposting and its making life pretty hard, filling the GL with literal thousands of lines...

This will only happen if you use WIP handling on the work tasks. I’m guessing you have setup Task Cost Codes with at least one used as WIP code? 

Can we eliminate this reposting functionality my removing Task Cost Codes with WIP codes?

Userlevel 6
Badge +8

Hi Team,

There is new new functionality of re-posting in Maintenance module in work task.

This functionality trigger TP3 posting after Invoices gets matched, Is there is an option not to use/stop this re-posting functionality in Work Task.

Regards,

Mukesh Gupta

@MKG019 Could you kindly explain the new functionality of -re posting in Maintenance module in work task  ? Because, I am searching an account for map TP3 and the business scenario is not clear for me . Please help .

 

Thanks in advance

Badge

Hi, are you able to provide some info about how you managed to resolve it? Our finance team have also noticed the new reposting and its making life pretty hard, filling the GL with literal thousands of lines...

We have got the same issue, IFSAPP10, upd10. Many lines reposted, but there was no change in the preposting of those worktasks. Anyone find out how this is caused meanwhile?

Userlevel 6
Badge +8

@SNBLAVA ,

 

Hi, After Analysis Following are observation found. As per the functionality in IFS Apps 10, when the No Part lines/Non Inventory parts are purchased and received from the work order requisition, then a work task posting lines with Transaction status Not applicable will be triggered with No posting type. Parallelly a Purchase transaction posting type M91 and M92 is triggered. Once the Supplier invoice is matched against that PO and made it to posted status, then the work task transaction which was Not applicable will be Overtaken. This means the Posting type M93 which was created during matching of PO in manual supplier invoice is being overtaken by Work task posting type TP3. So ideally posting type TP3 needs to be setup for Non inventory purchases from work task.

Userlevel 2
Badge +3

@SNBLAVA ,

 

Hi, After Analysis Following are observation found. As per the functionality in IFS Apps 10, when the No Part lines/Non Inventory parts are purchased and received from the work order requisition, then a work task posting lines with Transaction status Not applicable will be triggered with No posting type. Parallelly a Purchase transaction posting type M91 and M92 is triggered. Once the Supplier invoice is matched against that PO and made it to posted status, then the work task transaction which was Not applicable will be Overtaken. This means the Posting type M93 which was created during matching of PO in manual supplier invoice is being overtaken by Work task posting type TP3. So ideally posting type TP3 needs to be setup for Non inventory purchases from work task.

@XitThejaG:

This works perfectly if the Work Order and Work Task are still open, but not if they have been closed and have the “Finally Posted” tickbox ticked. We often invoice the Work Order to the customer (and then close down the Work Order) before the Supplier Invoice is received. This results in the “Finally Posted” tickbox being ticked on the Work Task Transaction, which means that there is no TP3 Posting that takes place.

Is this something you have come across before/are you able to offer any advice please?

Reply