Prerequisites for Purchase Order Processing
In the Backend System
· In the backend system, you have to implement the standard components Financial Accounting (FI) and Controlling (CO), or the appropriate functions of another ERP system.
· For commitment management in the backend system, the purchase order data must exist in the format of the IDoc BBPCO01.
In the Enterprise Buyer System
You have defined the following:
· Follow-On Documents
For example, in the case of local procurement, you have defined that the system creates purchase orders and follow-on documents locally in SAP Enterprise Buyer.
For more information, see the Supplier Relationship Management Implementation Guide (IMG): SRM Server ® Technical Basic Settings ® Define Backend Systems
· Purchasing group responsibility
In the organizational plan, the purchase order responsibility of each employee group must be assigned to each purchasing group, see Modeling the Purchasing Organization in the Organizational Plan
· Number range for purchase orders
See the path in the IMG: SRM Server ® Cross-Application Basic Settings ® Number Ranges.
· Transaction type for purchase orders
See the path in the IMG: SRM Server ® Cross-Application Basic Settings ® Define Transaction Types
· Vendor master records
You have replicated these from the backend system (see also Business Partner) or created them using the application Managing External Business Partners.
· Grouping criteria for local purchase orders
You can use a Business Add-In to aggregate shopping cart items in one purchase order (for example a purchase order from several shopping cart items without source of supply) or to separate shopping cart items that Enterprise Buyer would otherwise combine in one purchase order.
See the path in the IMG: SRM Server ® Business Add-Ins for Enterprise Buyer (BAdIs) ® Define Grouping Criteria for Local Purchase Orders
· Account assignment categories
You have mapped the account assignment categories that are used in Enterprise Buyer and in the backend system to each other.
See the path in the IMG: SRM Server ® Cross-Application Basic Settings ® Account Assignment ® Define Account Assignment Categories
· G/L account in Financial Accounting of the backend system
You have specified the G/L account that is to be posted to dependent on the product category and the account assignment category.
See the path in the IMG: SRM Server ® Cross-Application Basic Settings ® Account Assignment ® Define G/L Account for Product Category and Account Assignment Category
Alternatively, you can use the Business Add-In Determine G/L Account. See the path in the IMG: SRM Server ® Business Add-Ins for Enterprise Buyer (BAdIs) ® Account Assignment ® Determine G/L Acct
· Terms of payment
If you wish to use your own payment conditions independent of the backend system.
See the path in the IMG: SRM Server ® Cross-Application Basic Settings ® Create Payment Conditions
· Product categories
For more information, see Product Categories and Category Hierarchies in the CRM documentation.
· SAP BW
To be able to display BW evaluations (for example, a vendor evaluation) in Enterprise Buyer, you have connected a SAP Business Information Warehouse (SAP BW) with Release 3.0 or higher that is supplied with vendor data.
· SAP Exchange Infrastructure
You have this installed if you are using XML as an output medium. For more information, see the documentation on SAP Exchange Infrastructure.
· Purchase order output form and output medium
If you want to use your own form for purchase order output (for example, with your company logo), you will have already defined this. This is not relevant for purchase order output via XML.
See the path in the SAP menu: Tools ® Form Printing ® Smart Forms. (Transaction name: smartforms)
When defining forms, note the following:
· Copy one of the forms shipped by SAP and change the copy The SAP forms are called BBP_PO_PRN (printer), BBP_PO_FAX (fax), BBP_PO_MAIL (E-mail)
· Do not change the form interface or the global definitions You should only change the formatting of the contents, the positioning of the windows and the embedded graphics
Once you have created and activated your own form for purchase order output, you have defined for which output medium the form is valid.
See the path in the IMG: SRM Server ® Cross-Application Basic Settings ® Set Output Actions and Output Format ® Define Actions for Purchase Order Output
See also: