3755320 - Service Document Posting Creates Intercompany Posting

• When posting a service document in one company code, the system also picks a second company code and performs an intercompany posting.
• There is no visible reference to the second company code in the service document.
• The “Automatic Account Determination” setup for intercompany clearing does not explain why the expense is selected.

• The resource/employee used in the service confirmation is assigned to a cost center that belongs to a different company code than the receiving service order, which causes a real-time cross-company controlling posting and intercompany clearing.
• The expense G/L is the primary cost element on the service confirmation expense item, so the posting is driven directly by the confirmation item and not by automatic account determination.

To analyze and correct the posting behavior, proceed as follows:

1. Review the service confirmation and identify the expense item that posts to the travel expense G/L account.
   Verify that the assigned G/L account is maintained as a primary cost element.

2. Check the resource or employee used in the service confirmation.
   From the corresponding master data, determine the assigned sender cost center and its company code.

3. Compare the company code of the sender cost center with the company code of the receiving service order.
   If the company codes are different, the system creates a cross-company CO posting. In such cases, intercompany clearing is required and a corresponding cross-company posting document may be generated.

4. If cross-company posting is not expected in the business scenario, use one of the following options:

   • Reassign the resource or employee to a cost center that belongs to the same company code as the receiving service order.
   • Use another resource whose cost center is assigned to the same company code as the receiving service order.
   • Change the receiving object, for example the service order, so that it is assigned to the same company code as the resource, if this is consistent with the business requirement.

5. If cross-company posting is expected, keep the current organizational assignment and ensure that SSCUI / configuration activity Assign Intercompany Clearing Accounts for Actual Postings is properly maintained for the relevant company code pairs.

6. Post a new test service confirmation to confirm that the posting result is consistent with the intended company code setup.

Intercompany, Service Order, G/L account, Account determination group , KBA , CRM-S4-SRV-SVO-2CL , S4CRM: Service Order (Public Cloud) , Problem