13.02.2013 Page 1 of 3

SAP Note 1173815 - Purchase requisition instead ofpurchase order

Note Language: English Version: 3 Validity: Valid Since 29.05.2008

Summary

SymptomYou create a shopping cart in your SRM system and youexpect a purchase order or a reservation to be created in the back end.However, a purchase requisition is created instead.

Other termsShopping cart, shopping basket, SC, purchase order, PO, purchaserequisition,PReq, META_INTERPRETE_DATA, META_BAPI_DISPATCH, OMEF, OMEC

Reason and PrerequisitesThere is probably an error in your Customizing.

SolutionThe system determines the object type of the follow-on document after yousave the shopping cart. When determining the object type, the system checksSRM Customizing ('SPRO' -> 'Supplier Relationship Management' -> 'SRMServer' -> 'Cross Application Basic Settings' -> 'Define Objects (purchaserequisitions, reservations, purchase orders) in Backend System'), but theactual decision is made in the backend system. In the backend system, thesystem reads the SRM Customizing and the document data of the shoppingcart:

o The system first checks whether Customizing was created for thecurrent purchasing group or product category (Example forpurchasing group 'EKG1' and product category 'KATEGORIE1'):

Purchasing group Product category Sequence

EKG1 KATEGORIE1 1 * KATEGORIE1 2 EKG1 * 3 EKG1 KAT* 4 * * not allowed * KAT* not allowed EK* KATEGORIE1 not allowed

- The system always uses the first entry: If a valid entry isfound, the system does not check the next level (1..4).

- For Customizing entries that are not allowed, the systemautomatically converts the object type of the follow-ondocument to purchase requisition.

o The application data of the shopping cart is validated (SOS,material, ...) in the next step.

13.02.2013 Page 2 of 3

SAP Note 1173815 - Purchase requisition instead ofpurchase order

If the purchase order that was chosen in SRM Customizing cannot be createdin the backend system, the object type of the follow-on document isautomatically set to purchase requisition.

BAdI:The follow-on document type that is determined can be overridden by theBAdI BBP_TARGET_OBJTYP. After calling this BAdI, the system no longerchecks the document type against the backend system. If the overriddendocument type (reservation or purchase order) cannot be created in thebackend system, however, the system also does not create a purchaserequistion as an alternative. Instead, the system creates an entry in thealert monitor under 'Backend Application Errors'.

Troubleshooting:If the system creates a different follow-on object than expected, checkwhether Notes 140846 and 787045 are implemented in your backend system.

For the necessary Customizing settings, see Consulting Notes 157887 and336658. Check also in Customizing: SPRO -> 'Supplier RelationshipManagement' -> 'SRM Server' -> 'Technical Basic Settings' -> 'DefineBackend Systems' -> 'System Type' whether the release of the backend systemis the latest release.

Debugging:If you set the RFC user in the back end to dialog, you can debug thedetermination of the follow-on document yourself in the back end. For thedetermination, the SRM system calls the backend module'BBP_INTERPRETE_DATA' in the function module B31I_INTERPRETE_DATA at thefollowing point:

CALL FUNCTION 'BBP_INTERPRETE_DATA' DESTINATION destination TABLES procurement_item = lt_procurement_item procurement_account = procurement_account proc_customizing = proc_cust_backend return = return EXCEPTIONS communication_failure = 1 MESSAGE msg_text system_failure = 2 MESSAGE msg_text OTHERS = 3.

The result is returned in the field lt_procurement_item[]-OBJ_TO_GEN,whereby 1=reservation, 2=purchase requisition,3=purchase order._______________________________________________________________________Since the follow-on document determination depends on the Customizingsettings and application data, we regret that we are unable to providefurther support. We are responsible only for the provision of source codecorrections.

Header Data

Release Status: Released for Customer

13.02.2013 Page 3 of 3

SAP Note 1173815 - Purchase requisition instead ofpurchase order

Released on: 16.06.2008 07:36:36Master Language: GermanPriority: Recommendations/additional infoCategory: ConsultingPrimary Component: SRM-EBP-SHP Shopping Cart

Valid Releases

Software Component Release FromRelease

ToRelease

andSubsequent

SRM_SERVER 500 500 500

SRM_SERVER 550 550 550

SRM_SERVER 700 700 700 X

BBPCRM 4.0 400 400

Related Notes

Number Short Text

787045 Determination of subsequent object for a shopping cart item

336658 Purch req instead of purch order created in backend

157887 SAP BBP decision process: PO or PReq ?

140846 BBP: No purchase order generated although data complete