How To Fix /PRA/ACCOUNTING660 - Job could not be opened for some companies


SAP Error Message - Details

  • Message type: E = Error

  • Message class: /PRA/ACCOUNTING -

  • Message number: 660

  • Message text: Job could not be opened for some companies

  • Show details Hide details


  • 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 /PRA/ACCOUNTING660 - Job could not be opened for some companies ?

    The SAP error message /PRA/ACCOUNTING660 Job could not be opened for some companies typically indicates that there is an issue with the job scheduling or processing for specific companies in the SAP system. This error can arise due to various reasons, and here are some common causes, potential solutions, and related information:

    Causes:

    1. Missing Authorizations: The user may not have the necessary authorizations to access or execute the job for certain companies.
    2. Job Configuration Issues: The job may not be properly configured for the specific company codes, leading to it being unable to open.
    3. Company Code Settings: There may be specific settings or configurations for the company codes that prevent the job from being executed.
    4. Technical Issues: There could be underlying technical issues, such as database locks, system performance problems, or other system errors.
    5. Job Scheduling Conflicts: The job may be scheduled at a time when other jobs are running, causing conflicts.

    Solutions:

    1. Check Authorizations: Ensure that the user executing the job has the necessary authorizations for all relevant company codes. This can be done by reviewing the user roles and permissions.
    2. Review Job Configuration: Check the job configuration in transaction SM37 (Job Monitoring) or SM36 (Job Scheduling) to ensure that it is set up correctly for the companies in question.
    3. Verify Company Code Settings: Review the settings for the affected company codes in the configuration to ensure that they are correctly set up for the job being executed.
    4. Check for Technical Issues: Look for any system logs or error messages that might indicate technical issues. You can use transaction SM21 (System Log) to check for any relevant errors.
    5. Reschedule Jobs: If there are scheduling conflicts, consider rescheduling the job to a different time when other jobs are not running.
    6. Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that might address this specific error message or provide additional troubleshooting steps.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as SM37 (Job Monitoring), SM36 (Job Scheduling), and SM21 (System Log) for monitoring and troubleshooting jobs.
    • SAP Documentation: Refer to SAP Help documentation for detailed information on job scheduling and error handling.
    • SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.

    If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation and resolution.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker