Child pages
  • SRM PO Error Analysis Checklist
Skip to end of metadata
Go to start of metadata

Purpose

This page helps you to understand and analyze Purchase Order related error messages in your SRM system.

Overview

When you receive an explicit error message during Purchase Order processing, you can go through the below steps to gather more information about the problem root cause.

Analysis Steps

  1. Check the transaction BBP_PD and click on "Check" button to see whether the error is coming directly from SRM - backend errors are not shown here. 
  2. If you don't have the error message number, check the table "T100" to find the full error number. Search by message text, if necessary. You can check the message by number in the t-code SE91, too. 
  3. If you receive a Backend Error: please provide test data from the BAPI. For Purchase Order creation, please get test data from BAPI_PO_CREATE1, for PO change, get test data from Function BAPI_PO_CHANGE. More information on how to get test data can be found under the following link: How To Create BAPI Test Data 
  4. Debug BBP_PD_MSG_ADD Almost all errors are called in the Function Module BBP_PD_MSG_ADD. If you'd like to see from where the error comes, set a breakpoint in the Function BBP_PD_MSG_ADD in t-code SE37. Then carry out the problematic process : the system will stop every time a message is issued to the given PO. Once the debugger stops, click on „Locals” to see which error has been called. By pressing „F7” you can check which code called the message function and which error message is displayed.

 

Related Content

Related Documents

Creating test data for ECC backend purchasing documents

Related SAP Notes/KBAs

SAP KBA: 2126366 - SAP customer's guide: How to create support incidents for SRM-EBP-POR