How To Fix GG785 - Check field &

SAP Error Message - Details

• Message type: E = Error

• Message class: GG - Messages for FI-SL customizing

• Message number: 785

• Message text: Check field &

What causes this issue?

You are using field &V1& in table &V2&. This field uses domain PS_POSNR.
This domain is used in the project system to represent WBS elements. In
this case the internal and external representations differ
significantly.
If you are using domain PS_POSNR and send the data of a ledger via ALE,
the target system will probably receive incorrect data because the
internal representation of an external circumstance is very likely to be
different. Furthermore, you have problems in the use of PS_POSNR
regarding the entry of the selection options in reporting or the
definition of sets.

System Response

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

How to fix this error?

Use data element PS_POSID (or the partner field PAR_POSID) with 24-place
external representation.
In addition to the limitations described in Note 25307 regarding sets
for fields with data element PS_POSNR, there may be additional problems
in rollup, allocation, and planning.
The only advantage gained by the use of PS_POSNR is being able to later
change the names of your WBS elements.
This advantage against the use of PS_POSID is usually insignificant in
practice, since the names are not normally changed.
However, if you do want to be able to change the project names, you MUST
use PS_POSNR with all its restrictions and potential problems.
<ZH>Notes on the Use of PS_POSID (Recommended External Representation)
</>
1) Before Release 4.6C, implement the program corrections in Note 372883
under Corrections.
2) For correct update of the WBS element from FI, add the following
entry to your field movement:
Rec.Field Sender tab. Send.Field Exit
IHR field name ACCIT_GLX PS_PSP_PNR S07
3) For correct update of the WBS element from CO, add the following
entry to your field movement:
Rec.Field Sender tab. Send.Field Exit
IHR field name COIOP PSPNR S07
4) For correct master data validation, add an entry for your summary
table and the field name for the WBS element in the integrated master
data (transaction GCS1).
You can select the correct entry with F4 on the field Exit/Table (Exit
18).
For the first higher-level field, enter RBUKRS for local tables or RCOMP
for global tables. Ignore the warning that the entry is not correct.
Also add the corresponding entry for summary table GLU1 so that master
data validation for SL document entry functions correctly.

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 GG785 - Check field & ?

  The SAP error message GG785 typically indicates that there is an issue with a specific field in a transaction or process. The message usually states something like "Check field &" where "&" represents the field name that is causing the issue. This error can occur in various contexts, such as during data entry, report generation, or when executing a transaction.
  Possible Causes:
  
  Missing or Incorrect Data: The field in question may be empty or contain invalid data that does not meet the required format or criteria.
  Configuration Issues: There may be a configuration problem in the system that affects how the field is processed.
  Authorization Issues: The user may not have the necessary permissions to access or modify the field.
  Data Consistency Issues: There may be inconsistencies in the data that are causing the system to reject the input.
  Custom Code or Enhancements: If there are custom developments or enhancements in the system, they may be interfering with standard processing.
  
  Solutions:
  
  Check Field Value: Review the value entered in the field and ensure it meets the required format and criteria. If the field is mandatory, ensure it is filled out.
  Review Configuration: Check the configuration settings related to the field in question. This may involve looking at the relevant customizing settings in SPRO.
  User Authorizations: Verify that the user has the necessary authorizations to access and modify the field. This can be checked in the user roles and profiles.
  Data Validation: Run data validation checks to identify any inconsistencies or errors in the data that may be causing the issue.
  Consult Documentation: Refer to SAP documentation or help resources for specific guidance related to the field and the error message.
  Debugging: If you have access to technical resources, consider debugging the transaction to identify where the error is occurring in the code.
  Contact Support: If the issue persists, consider reaching out to SAP support or your internal IT team for further assistance.
  
  Related Information:
  
  Transaction Codes: Depending on where the error occurs, you may want to check specific transaction codes related to the process you are working on.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional context.
  Community Forums: Check SAP community forums or other online resources where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the GG785 error and implement a solution.