How To Fix G5169 - Screen fields & are not open for posting entry

SAP Error Message - Details

• Message type: E = Error

• Message class: G5 - IS-Oil /Joint Venture/ Material transfer pricing

• Message number: 169

• Message text: Screen fields & are not open for posting entry

The field &V1& is configured to be suppressed for entry in both posting
status and field status.
To open the &V1& in field status (Note that the system will not look at
field status if the entry is asset transaction):
Go to IMG -> Financial Accounting -> Financial Accounting Global
Settings -> Document -> Line item -> Controls -> Allocate company code
to <DS:TRAN.OBC5>field status variant</>
Get the field status variant
Go to Accounting -> Financial Accounting -> General Ledger -> Master
Records -> Display <DS:TRAN.FS03>GL Account Master Data</>
Get the field status group
Go to IMG -> Financial Accounting -> Financial Accounting Global
Settings -> Document -> Line item -> Controls -> <DS:TRAN.OBC4>Maintain
field status variant</>
Use field status variant and field status group to get to the right
field status.
Change the status of &V2& to optional entry or require entry.
To open the &V1& in posting status:
Go to IMG -> Financial Accounting -> Financial Accounting Global
Settings -> Document -> Line item -> Controls -> <DS:TRAN.OB41>Define
posting keys</>
Double click on the posting keys for the expense/asset line.
Click on the field status button.
Change the status of &V2& to optional entry or require entry.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message G5169 - Screen fields & are not open for posting entry ?

  The SAP error message G5169, which states "Screen fields & are not open for posting entry," typically occurs when you are trying to post a transaction in SAP, but certain fields on the screen are not available for input. This can happen for a variety of reasons, and understanding the cause is essential for finding a solution.
  Causes:
  
  
  Field Status Group Settings: The field status group assigned to the account or transaction type may restrict input for certain fields. This is often configured in the Financial Accounting (FI) module.
  
  
  Document Type Configuration: The document type you are using may have specific settings that restrict input for certain fields.
  
  
  User Authorizations: The user may not have the necessary authorizations to enter data in the specified fields.
  
  
  Transaction Type Restrictions: Certain transaction types may have restrictions on what can be entered based on the configuration in the system.
  
  
  Posting Period: The posting period may be closed, preventing entries from being made in certain fields.
  
  
  Solutions:
  
  
  Check Field Status Group:
  
  Go to the configuration settings for the relevant account in the SAP system (Transaction code: OBC4).
  Review the field status group assigned to the account and ensure that the fields you are trying to enter data into are set to "optional" or "required."
  
  
  
  Review Document Type Settings:
  
  Check the configuration for the document type you are using (Transaction code: OBA7).
  Ensure that the fields you need are not set to "display only" or "not allowed."
  
  
  
  User Authorizations:
  
  Verify that the user has the necessary authorizations to post entries in the relevant fields. This can be checked with the help of your SAP security team.
  
  
  
  Check Transaction Type:
  
  Review the configuration for the transaction type you are using to ensure that it allows input for the fields in question.
  
  
  
  Open Posting Period:
  
  Ensure that the posting period is open for the transaction you are trying to post. You can check this in the transaction code OB52.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Review SAP documentation for field status groups and document types to understand how they affect posting entries.
  Testing: If possible, test the posting in a development or quality assurance environment to replicate the issue and identify the exact cause.
  
  If the issue persists after checking these areas, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the relevant module.