How To Fix 3G199 - Company code &1 is invalid; see the long text

SAP Error Message - Details

• Message type: E = Error

• Message class: 3G - Payroll: International

• Message number: 199

• Message text: Company code &1 is invalid; see the long text

What causes this issue?

The payroll result, feature
<DS:HRDS.DSYSLO_ECI549B_DTAKTAAAAAAAAAAAAAAA___0VVV>DTAKT</>
<LS>(Sender Account Number for Data Medium Exchange)</>, or the
employee's master data include company code &v1&. This company code
does not exist.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

<ZH>Note</>
When you effect the wage and salary payment, the system determines the
company code using the last record of table WPBP <LS>(Work Center/Basic
Pay)</> in the employee's payroll result. The system also checks
whether you have specified a different paying company code in feature
DTAKT for any of the payments. If you effect an advance payment from
master data, the system determines the paying company code using
infotype 0001 <LS>Organizational Assignment</>.

System Response

INCLUDE HRDME_ERROR_REJECT_PERNR OBJECT DOKU ID TX

How to fix this error?

This error can have two causes:
The company code determined by the system is incorrect.
If the error occurs when a wage and salary payment is effected, you
must correct the master data and payroll results of the employees
concerned or the settings for feature DTAKT.
If the error occurs when an advance payment from master data is
effected, you must correct the master data of the employees concerned
or the settings for feature DTAKT.
Customizing lacks the settings for company code &v1& and personnel
subarea &v2& (table T001P). If this is the case, you must enter the
settings required in Customizing.
The following applies to both situations:
INCLUDE HRDME_ERROR_REPEATE_DTA OBJECT DOKU ID TX

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 3G199 - Company code &1 is invalid; see the long text ?

  The SAP error message 3G199 indicates that the company code specified in a transaction or process is invalid. This error typically arises when the company code does not exist in the system or is not properly configured.
  Cause:
  
  Non-existent Company Code: The company code you are trying to use does not exist in the SAP system.
  Inactive Company Code: The company code may exist but is not active or has been marked for deletion.
  Authorization Issues: The user may not have the necessary authorizations to access the specified company code.
  Configuration Issues: There may be issues with the configuration of the company code in the system.
  
  Solution:
  
  Verify Company Code: Check if the company code exists in the system. You can do this by navigating to the transaction code OBY6 (or SPRO -> Financial Accounting -> General Ledger Accounting -> Master Data -> G/L Accounts -> Edit, Delete, or Display G/L Account) and looking for the company code.
  Check Activation Status: If the company code exists, ensure that it is active. You can check this in the same configuration area.
  User Authorizations: Ensure that the user has the necessary authorizations to access the company code. This can be checked with the help of your SAP security team.
  Review Configuration: If the company code is supposed to be valid, review the configuration settings to ensure everything is set up correctly.
  Consult Long Text: The error message suggests checking the long text for more details. You can do this by clicking on the error message or using transaction SE91 to look up the message class and number for additional context.
  
  Related Information:
  
  Transaction Codes: 
  
  OBY6: To view and manage company codes.
  SE91: To view message classes and long texts.
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to SAP Help documentation for more details on company code configuration and management.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP Basis or functional team for further investigation.