Suspense processing helps in booking costs while the final equity share hasn’t been finalized or there is a dispute about something.
We can suspend a wbs element, cost center, equity group, etc. All these work in a similar way.
All the billable costs that are posted to the suspended object are picked up and become non-billable when the program runs.
Suspense processing consists of two tcodes. The first step is to put the cost object, JV, etc. in suspense.
The second step is to run GJ17 which will pick up all the billable costs and make them non-billable.
Let’s suspend a cost center using the menu below.
Enter the company code
In the suspense table, enter the company code, the cost center that you are suspending, check the suspense flag, enter the period and year in which you are suspending.
click on save
Make a billable posting, and we can see how running the suspense program affects it.
The posting below is billable as the cost center is billable.
If we run cutback in a test run, we will see that this cost is picked up.
Make a note of the venture and the equity group. You can also click on the spool to see the detailed posting.
Our test is to ensure that this same cost isn’t picked up after this goes through the suspense program.
The next step is to change all the BI postings to be suspended(non-billable)
In the configuration, we need to have a suspense recovery indicator for our billable recovery indicators.
The suspense program will pick up the billable posting and reverse them and book them with the suspense recovery indicator.
Access the step with the path below or via tcode GJ17.
Enter the company code, venture, and other info.
Keep the test run on when you run it initially to ensure there are no errors.
Click on the spool to view the details of this posting.
Look at the suspense reporting section. It is telling us that the recovery indicator BI is becoming SU.
Below is the configuration where BI is linked to SU.
If this needs to happen for other recovery indicators, enter similar info for them as well.
Remove the test run and run it again.
There is now a JV document that is posted.
You can view the JV document to see the details of how the BI posting was reversed, and the postings now have an SU recovery indicator.
If you run cutback now
there is nothing to pick up
previously cutback was picking up this document, but since the recovery indicator is now SU which is nonbillable, nothing is there for the cutback to pick up.