How To Fix >1073 - Final character &1 / card type &2 / CoCode &3 / currency &4 are blocked

SAP Error Message - Details

• Message type: E = Error

• Message class: >1 - Shockwave SAPGUI message handling

• Message number: 073

• Message text: Final character &1 / card type &2 / CoCode &3 / currency &4 are blocked

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 >1073 - Final character &1 / card type &2 / CoCode &3 / currency &4 are blocked ?

  The SAP error message 1073 indicates that a specific final character (often related to a document or transaction) is blocked for a particular card type, company code (CoCode), and currency. This error typically arises in the context of financial transactions, such as when processing invoices, payments, or other financial documents.
  Cause:
  The error can occur due to several reasons:
  
  Blocking Configuration: The final character may be configured in the system to be blocked for certain transactions or conditions. This could be due to business rules or compliance requirements.
  Document Type Restrictions: The document type associated with the transaction may have restrictions that prevent the use of the specified final character.
  Currency Issues: The currency specified may not be allowed for the given card type or company code.
  Company Code Settings: The company code may have specific settings that restrict the use of certain final characters for transactions.
  
  Solution:
  To resolve the error, consider the following steps:
  
  
  Check Configuration:
  
  Review the configuration settings for the final character in the SAP system. This can be done in the customizing settings (transaction SPRO) under Financial Accounting (FI) settings.
  Ensure that the final character is not blocked for the specific card type, company code, and currency.
  
  
  
  Review Document Type:
  
  Check the document type settings to see if there are any restrictions related to the final character. You can do this in the document type configuration.
  
  
  
  Currency Validation:
  
  Verify that the currency being used is valid for the transaction and is allowed for the specified card type and company code.
  
  
  
  Consult with Business Users:
  
  Discuss with relevant business users or stakeholders to understand if there are any specific business rules that require the final character to be blocked.
  
  
  
  SAP Notes and Support:
  
  Check for any SAP Notes related to this error message. Sometimes, SAP provides patches or updates that can resolve specific issues.
  If the issue persists, consider reaching out to SAP support for further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like OBD2 (for document types) or OBY6 (for company code settings) to access the relevant configuration areas.
  Error Logs: Review the error logs or application logs (transaction SLG1) for more details on the error context.
  Testing: After making changes, perform testing to ensure that the issue is resolved and that the changes do not negatively impact other processes.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.