How To Fix WS073 - No authorization '&' for settlement document type & (&) in company code &

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 073

• Message text: No authorization '&' for settlement document type & (&) in company code &

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 WS073 - No authorization '&' for settlement document type & (&) in company code & ?

  Certainly! Here's a detailed explanation of the SAP error message:
  
  SAP Error Message:
  WS073 No authorization '&' for settlement document type & (&) in company code &
  
  Meaning / Cause:
  This error occurs when a user tries to perform a settlement posting or related activity in SAP, but does not have the required authorization for the specific settlement document type in the specified company code.
  
  The placeholders & in the message are replaced by actual values at runtime, such as the missing authorization object, the settlement document type, and the company code.
  Settlement document types control the type of settlement postings (e.g., internal orders, WBS elements, cost centers).
  SAP uses authorization objects to restrict access to certain document types and company codes.
  The user’s assigned roles or profiles do not include the necessary authorization to post or process settlement documents of the indicated type in the given company code.
  
  
  Typical Authorization Object Involved:
  
  F_BKPF_BUP (Authorization for document types and company codes)
  F_BKPF_BUK (Authorization for company codes)
  F_BKPF_GSB (Authorization for business areas)
  F_BKPF_KOA (Authorization for account types)
  F_BKPF_KOA or F_BKPF_BUP are often relevant for settlement document types.
  
  
  How to Identify the Missing Authorization:
  
  Check the exact authorization object and field values missing from the error message (the first &).
  Use transaction SU53 immediately after the error occurs to see the last failed authorization check.
  Review the user’s roles and profiles in SU01 or PFCG.
  Check the authorization objects related to settlement document types and company codes.
  
  
  Solution:
  
  Grant the required authorization:
  
  Identify the authorization object and field values needed (e.g., settlement document type, company code).
  Update the user’s role(s) in transaction PFCG to include the missing authorization.
  For example, add the settlement document type and company code to the authorization object F_BKPF_BUP or relevant object.
  
  
  Test the authorization:
  
  After updating the roles, have the user log off and log back in.
  Retry the settlement posting to confirm the error is resolved.
  
  
  If unsure about the required values:
  
  Consult with the functional consultant or check configuration for settlement document types in SPRO under Controlling ? Internal Orders ? Settle ? Define Settlement Document Types.
  
  
  Check for any custom authorization checks:
  
  Sometimes, custom code or user-exits may enforce additional authorization checks.
  
  
  
  
  Additional Information:
  
  Settlement document types are configured in Controlling (CO) and linked to specific settlement rules.
  Proper segregation of duties should be maintained when granting authorizations.
  If the user needs only temporary access, consider using transaction SU56 to monitor authorizations or assign a temporary role.
  Always follow your organization’s security policies when modifying authorizations.
  
  
  Summary:
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  User lacks authorization for the settlement document type in the specified company code.
  
  
  Authorization Object
  Typically F_BKPF_BUP or related objects controlling document type and company code.
  
  
  Solution
  Add the missing authorization to the user’s role/profile via PFCG.
  
  
  Check Tools
  Use SU53 to identify missing authorizations after the error occurs.
  
  
  
  
  If you need help with the exact authorization object or role maintenance steps, feel free to ask!