How To Fix J+068 - Asset/liability indic. & not appropriate for forward securities trans.

SAP Error Message - Details

• Message type: E = Error

• Message class: J+ -

• Message number: 068

• Message text: Asset/liability indic. & not appropriate for forward securities trans.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message J+068 - Asset/liability indic. & not appropriate for forward securities trans. ?

  The SAP error message J+068 indicates that there is an issue with the asset/liability indicator in the context of forward securities transactions. This error typically arises when the system detects that the asset/liability indicator assigned to a security does not align with the requirements for processing forward transactions.
  Cause:
  
  Incorrect Asset/Liability Indicator: The asset/liability indicator assigned to the security may not be appropriate for forward transactions. This can happen if the indicator is set to a value that does not allow for forward securities transactions.
  Configuration Issues: There may be configuration settings in the SAP system that do not support the type of transaction you are trying to execute.
  Transaction Type Mismatch: The transaction type being used may not be compatible with the asset/liability indicator set for the security.
  
  Solution:
  
  
  Check Asset/Liability Indicator:
  
  Navigate to the security master data in SAP and verify the asset/liability indicator assigned to the security.
  Ensure that the indicator is appropriate for forward transactions. You may need to consult your financial or accounting team to determine the correct indicator.
  
  
  
  Review Configuration Settings:
  
  Check the configuration settings in the SAP system related to securities and forward transactions. This can typically be done in the SPRO transaction under Financial Accounting (FI) or Treasury settings.
  Ensure that the settings for asset/liability indicators and transaction types are correctly configured to allow for forward securities transactions.
  
  
  
  Adjust Transaction Type:
  
  If the transaction type you are using is not compatible with the asset/liability indicator, consider using a different transaction type that aligns with the indicator.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or help resources related to securities transactions and asset/liability indicators for further guidance.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for assistance. They may provide insights specific to your system configuration and version.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as:
  
  SE16N: For viewing table entries related to securities.
  SPRO: For accessing configuration settings.
  
  
  SAP Notes: Search for SAP Notes related to error J+068 for any patches or updates that may address the issue.
  User Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.