Skip to main content
Solved

Project Budget consumption for Purchase Order generating for Shop Order outside operation

  • December 21, 2024
  • 1 reply
  • 76 views

Abdul
Superhero (Partner)
Forum|alt.badge.img+14
  • Superhero (Partner)
  • 256 replies

Dear experts,

We are in the process to implement Project Budget (Forecast) functionality for one of our client who is in Project based manufacturing business.

I understand that Project Budget functionality only controls Procurement related transactions against a pre-defined active budget, however, system is not checking Project budget for Purchase Order/Purchase Requisitions generating for outside operation on Shop Order releasing.

Though, system properly updating Planned Committed Cost, Committed Cost for Shop Order but not updating Purchase Order related cost on project.

Not sure whether I am missing some setup.

@Marcel.Ausan  ​@Buddhika Kurera ​@matt.watters 

Best answer by dameenda

When a Shop Order is connected to a Project, the Shop order transactions will be pre posted for the project,

Similarly any subcontracting cost incurred for the Shop order are also pre posted to project through shop order SUBCONTR Transactions.,

If we allow the purchasing transactions to be pre posted. it will cause the subcontracting costs to be posted twice.

 

Because when an outside operation is completed,

First it creates corresponding ARR-NONINV transactions in the Purchase Transaction history

Then these Transactions are copied to Operation History as SUBCONTR transactions with identical Costs , these are the transactions responsible for Shop Order WIP.

 

If we allow Pre-postings for Outside Purchase Order;

We will end up with 2 sets of Transactions with Identical value for the same receipt as below;

 

1, SUBCONTR Transactions in Operation History

2. ARR-NONINV transactions created in the “Purchase Transaction History”

 

To avoid this, it had been decided only to pre-post the Transactions created in the Operation history.

This decision was implemented by BUG 66431 in APP7 Track by 19-10-2007

View original
Did this topic help you find an answer to your question?

1 reply

Forum|alt.badge.img+10
  • Hero (Employee)
  • 208 replies
  • Answer
  • January 6, 2025

When a Shop Order is connected to a Project, the Shop order transactions will be pre posted for the project,

Similarly any subcontracting cost incurred for the Shop order are also pre posted to project through shop order SUBCONTR Transactions.,

If we allow the purchasing transactions to be pre posted. it will cause the subcontracting costs to be posted twice.

 

Because when an outside operation is completed,

First it creates corresponding ARR-NONINV transactions in the Purchase Transaction history

Then these Transactions are copied to Operation History as SUBCONTR transactions with identical Costs , these are the transactions responsible for Shop Order WIP.

 

If we allow Pre-postings for Outside Purchase Order;

We will end up with 2 sets of Transactions with Identical value for the same receipt as below;

 

1, SUBCONTR Transactions in Operation History

2. ARR-NONINV transactions created in the “Purchase Transaction History”

 

To avoid this, it had been decided only to pre-post the Transactions created in the Operation history.

This decision was implemented by BUG 66431 in APP7 Track by 19-10-2007


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings