How To Fix MSPCIF020 - Selection of call object failed

SAP Error Message - Details

• Message type: E = Error

• Message class: MSPCIF -

• Message number: 020

• Message text: Selection of call object failed

What causes this issue?

Relationships between SAP SCM data and ERP data and the relationships
between ERP objects are maintained as described below:
The ERP revision has a reference to an SAP SCM slot.
Each ERP call object relevant for planning in SAP SCM has a reference to
an SAP SCM demand.
Each ERP call object relevant for planning in SAP SCM has a reference to
an ERP revision.
For the incoming data, the selection of call objects based on these
external/internal references has failed.
The problem occurred when the scheduling of the maintenance plan was
restarted (call objects with a future date were already released).
If there are revision deletion instructions from SAP SCM to ERP and the
revision call object selection has failed, it is ignored by the CIF
inbound program.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Adjust the synchronization point of the SAP SCM demands manually in the
maintenance and service planning board in SAP SCM by linking it to a
suitable call object in ERP.
Go to transaction SMQ1 in SAP SCM and delete any pending queue with the
queue name CFMW*, which leads to this error (as indicated in this
application log).
Restart the transfer of the plan in SAP SCM using transaction
/SAPAPO/C5.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MSPCIF020 - Selection of call object failed ?

  The SAP error message MSPCIF020: Selection of call object failed typically occurs in the context of the SAP Project System (PS) or when working with the Project Management (PM) module. This error indicates that the system was unable to select or retrieve the specified call object, which can be due to various reasons.
  Causes:
  
  Incorrect Object Type: The call object specified may not be valid or may not exist in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the specified object.
  Data Inconsistencies: There may be inconsistencies or corruption in the data related to the project or call object.
  Configuration Issues: The system configuration may not be set up correctly for the project or call object.
  Missing or Incomplete Data: Required fields or data for the call object may be missing or incomplete.
  
  Solutions:
  
  Check Object Validity: Verify that the call object you are trying to access exists and is valid. You can do this by checking the object in the relevant transaction (e.g., CJ20N for project management).
  Review Authorizations: Ensure that the user has the necessary authorizations to access the call object. This can be checked in the user roles and profiles.
  Data Consistency Check: Run consistency checks on the project data to identify and resolve any inconsistencies. You can use transaction codes like CJEN (for project structure) or other relevant tools.
  Configuration Review: Review the configuration settings related to the project and call object to ensure they are set up correctly.
  Check for Missing Data: Ensure that all required fields and data for the call object are filled out correctly. This may involve checking the project definition, WBS elements, or other related objects.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional troubleshooting steps.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJ01 (Create Work Breakdown Structure), and CJ02 (Change Work Breakdown Structure).
  SAP Documentation: Refer to the official SAP documentation for Project System and Project Management for detailed information on object handling and error messages.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  If the issue persists after trying the above solutions, it may be beneficial to involve your SAP Basis or technical team for further investigation, as they can analyze system logs and provide deeper insights into the error.