How To Fix NJIT_MSG704 - No Edit Authorization for the current Ship-To-Party-Sales Ar. Combination

SAP Error Message - Details

• Message type: E = Error

• Message class: NJIT_MSG - NJIT Inbound message class

• Message number: 704

• Message text: No Edit Authorization for the current Ship-To-Party-Sales Ar. Combination

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 NJIT_MSG704 - No Edit Authorization for the current Ship-To-Party-Sales Ar. Combination ?

  The SAP error message NJIT_MSG704 indicates that there is no edit authorization for the current Ship-To-Party and Sales Area combination. This typically occurs when a user attempts to make changes to a sales document or master data related to a specific Ship-To-Party but lacks the necessary permissions.
  Cause:
  
  Authorization Issues: The user does not have the required authorization to edit the data for the specified Ship-To-Party and Sales Area.
  Configuration Settings: The system may be configured to restrict access to certain Ship-To-Parties based on user roles or organizational structure.
  Master Data Restrictions: The Ship-To-Party may have specific restrictions or settings that prevent editing by certain users.
  
  Solution:
  
  
  Check User Authorizations:
  
  Verify the user's roles and authorizations in the SAP system. This can be done by checking the user's profile in transaction code SU01 or PFCG.
  Ensure that the user has the necessary authorizations for the relevant transaction codes and objects related to Sales and Distribution (SD).
  
  
  
  Review Authorization Objects:
  
  Check the relevant authorization objects, such as V_VBAK_VKO (Sales Document: Authorization for Sales Organization) and V_VBAK_VKORG (Sales Document: Authorization for Sales Area).
  Make sure that the user has the appropriate authorizations for the specific Sales Area and Ship-To-Party.
  
  
  
  Consult with Security Team:
  
  If the user lacks the necessary authorizations, consult with your SAP security team to request the required access or to understand the restrictions in place.
  
  
  
  Check Configuration:
  
  Review the configuration settings for the Sales and Distribution module to ensure that there are no restrictions set for the Ship-To-Party in question.
  This may involve checking the settings in transaction codes like OVK1 (Define Sales Areas) or OVK2 (Assign Sales Areas).
  
  
  
  Testing:
  
  After making any changes to authorizations or configurations, test the scenario again to ensure that the error is resolved.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  SU01 - User Maintenance
  PFCG - Role Maintenance
  OVK1 - Define Sales Areas
  OVK2 - Assign Sales Areas
  
  
  Authorization Objects: 
  
  V_VBAK_VKO - Sales Document: Authorization for Sales Organization
  V_VBAK_VKORG - Sales Document: Authorization for Sales Area
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  If the issue persists after following these steps, it may be beneficial to consult SAP support or your internal SAP team for further assistance.