Posting time across company codes

Question

I have a question around timesheets accross different company codes. My example is:
Company A wins the work with the external customer, who they will invoice and recognise the revenue for using RA. They are unable to complete the work so purchase the service of an employee within Company B. Normally this would mean raising a PO from Company A to Company B. The employee (who has a HR record within company B), then raises a Project & SO within company B and posts his time to it. He then invocies Company A.
It would be very easy just to then service receipt the PO in company A, and post the invocie from company B. However we want to be able to action this via timesheets. The only solution we can come up with is to have the employee in company B to also have an external HR record in company A. This will then allow him to also enter time in the Company A project, and using CATM create the SES on the PO.
However this means the employee is keying in 2 timesheet records. We can eliminate the records by the employee number range, but sometimes an entry could be missed.
So how do others cross book accross company codes with timesheets. Bear in mind Company A wants to recognise all the Revenue for their project, and company B will also want to see the time postings in their company code.
Any ideas?

Answer 1

Okay, clear on your comment, and appreciate that.This comment fascinates me though, "In the scenario the project will consist of top level WBS billing element linked to sales order with customer and then another WBS belonging to the supplying company code in the lower hierarchy linked to sales order to the internal customer". In order to get RRICB to be read correctly in DP93 taking into consideration proper set up of DIP profile, etc. you need to have account assignment "E' in play. This prevents the use of a WBS on the contract and subsequently the sales order. Your suggested model is very different from what SAP documentation suggests for ECC 6.0. Again, not questioning you, just interested to know more as I have spent a lot of time recently modeling things in our sandbox environment, and have poured over the documentation many times.
My conclusion at this point is RRICB works, and works well. BUT, there are limitations in terms of how things are accounted for at the end of the day. If the gap between the business requirement and the system standard doesn't cut it, not much you can do - really the essence of OSS NOTE 1341136.
I am equally confused at item 6 (SAP documentation, not me). Further confusion in the fact you are suggesting the creation of a WBS at lower level, and SAP documentation suggesting there is no need for a project in this relationship. I have the suggested model in the link I posted previously working in our sandbox environment and admittedly I like what I see, just running into issues as the level of accounting that plays out in the scenario doesn't meet our the business requirement.
We spent a lot of time trying to resolve our profit center dilemma via EXIT_SAPLV46H_001, but couldn't get it to take. Our code was successful in deriving what we were looking for, but seemed to get trumped later on in the process.
Useful notes on the collective process I found ...
352261      VA01: Error message KI100
815972      PCA substitution for cross-company-code sale
916973      Part PCtr incorr in interco bill before ext billing
1410850    DP93: Service order on selection screen leads to VPK1 310
1341136    RRICB, classic FI, new G/L, CO and PCA
643838      Billing between company codes: Expense Reports and so on.
Any further insights are welcomed.
Thanks again,
Jason