How To Fix WS730 - No authorization to generate follow-on document, contract type &1 (&2)

SAP Error Message - Details

• Message type: E = Error

• Message class: WS - Supplier Billing Document

• Message number: 730

• Message text: No authorization to generate follow-on document, contract type &1 (&2)

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 WS730 - No authorization to generate follow-on document, contract type &1 (&2) ?

  The SAP error message:
  WS730 No authorization to generate follow-on document, contract type &1 (&2)
  
  Meaning / Cause:
  This error occurs when a user tries to create a follow-on document (such as a delivery, billing document, or purchase order) from a contract, but does not have the necessary authorization to do so for the specified contract type.
  
  &1 = Contract type (e.g., MK, WK, etc.)
  &2 = Additional info, often the document type or related object
  
  In SAP, follow-on documents are created based on existing contracts or documents, and the system checks if the user has the required authorization to generate these documents. The authorization check is typically related to the authorization object V_VBAK_VKO (Sales Document: Authorization for Sales Document Types) or similar objects depending on the module (SD, MM, etc.).
  
  Common Causes:
  
  Missing or insufficient authorization for the user to create follow-on documents for the given contract type.
  The user’s role/profile does not include the required authorization objects or values.
  The contract type is restricted in the authorization settings.
  Customizing settings restrict follow-on document creation for certain contract types.
  
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction SU53 immediately after the error occurs to see which authorization check failed.
  Look for missing authorizations related to sales document types or contract types, such as:
  
  Authorization object V_VBAK_VKO (Sales Document: Authorization for Sales Document Types)
  Authorization object V_VBKA_VKO (Sales Document: Authorization for Sales Document Header)
  Authorization object V_VBFA_VKO (Follow-on Document Authorization)
  
  
  For MM contracts, check authorization objects related to purchasing documents.
  
  
  
  Adjust Roles/Profiles:
  
  Update the user’s role(s) in transaction PFCG to include the necessary authorization values for the contract type and follow-on document type.
  Ensure the user has authorization for the specific contract type (&1) and the follow-on document type (&2).
  
  
  
  Check Customizing:
  
  Verify in SPRO under Sales and Distribution ? Sales ? Sales Documents ? Sales Document Header ? Define Sales Document Types that the contract type is correctly configured.
  Check if any restrictions exist on follow-on document creation for the contract type.
  
  
  
  Testing:
  
  After updating authorizations, test the creation of the follow-on document again.
  Use SU53 to confirm no further authorization errors.
  
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU53 – Display last authorization check
  PFCG – Role maintenance
  VA43 – Display contract
  VA01 – Create sales order (follow-on document)
  ME33K – Display contract (MM Purchasing)
  ME21N – Create Purchase Order (follow-on document)
  
  
  
  Authorization Objects:
  
  V_VBAK_VKO – Sales Document: Authorization for Sales Document Types
  V_VBFA_VKO – Follow-on Document Authorization
  M_EINK_FRG – Release authorization for purchasing documents (MM)
  
  
  
  Notes and SAP Help:
  
  Check SAP Notes related to authorization issues for contract follow-on documents.
  SAP Help Portal for Sales and Distribution authorization concepts.
  
  
  
  
  Summary:
  The WS730 error indicates a missing authorization for generating a follow-on document from a contract of a certain type. The solution involves identifying the missing authorization via SU53, updating the user’s roles to include the necessary authorizations for the contract and follow-on document types, and verifying the customizing settings for contract types.
  
  If you provide the exact contract type and follow-on document type, I can help you identify the precise authorization objects and values to check.