A very great document about employee self service process locates in SAP Help Portal. But I will use some actual screen shots to show this process.
Step 1. Create a Shopping Cart
choose product/service from catalog or use description to build the shopping cart. Fill the account assignment tab, e.g. Cost center:51502520 and G/L account 7783250.
Technical Information:
SAP utilizes OCI(Open Catalog Interface) to transfer product data back to SRM shopping cart.
Step 2. Checking Status and Approving
After user chooses save shopping cart, a approval workflow will be started. You can go to inbox to approve the shopping cart. After the shopping cart is approved, an purchase order will be created in the backend system.
Technical Information:
After the shopping cart is approved, the program will call function module BBP_PD_SC_TRANSFER to create purchase order in the backend system.
Step 3. Processing Purchase Orders
Step 4. Processing Confirmations
Step 5. Processing Invoices
SAP SRM uses workflow to implement approval process. Some workflows are absolutely essential for SRM while others can be used on an optional basis. Some are also provided as alternatives to others.
http://help.sap.com/saphelp_srm40/helpdata/en/8b/4fa9585db211d2b404006094b92d37/frameset.htm. Here list lots of standard workflows for approval process. You can also copy the standard WF out and change it according to your requirement. Below is primary steps.
Step 1. Copy a standard workflow, edit the copy, and activate the workflow.
Step 2. Go to Supplier Relationship Management->SRM Server->Cross-Application Basic Setting->SAP Business Workflow->Define Conditions for Starting Workflows. Here you can define start condition of these approval workflow.
These are some BADIs related to approval workflow:
BBP_WFL_APPROV_BADI – Determine Approver for n-Level. Dynamic Approval WFL
BBP_WFL_SECUR_BADI – SAP implementation: No restart in case of partial rejection
In SRM, when creating a shopping cart, we can modify the price of product. This price will be considered as an override price of standard price which calculated by info record and other condition. But when the shopping cart is converted into a sales order, the price will be recalculated and the changed price will be lost. The requirement is to keep the override price in the PO as well.
After debugging the SRM application, the standard logic will call BAPI “BAPI_PO_CREATE1″ to create PO according to the shopping cart in SRM. SAP Note 580225(Purchasing BAPIs: Conditions and pricing) provides an solution for this situation. If we set the field ‘PO_PRICE‘ in POITEM structure to 1, the gross price will be determined by the passed in net price which is override price in shopping cart. Below is from note 580225:
2. POITEM-PO_PRICE
You can use the PO_PRICE field to control, at item level, if the value should be copied from the POITEM-NET_PRICE field to the conditions. PO_PRICE can have the values ‘ ‘, ’1′ or ’2′ with the following meaning:
- PO_PRICE = ‘ ‘: The conditions are determined automatically, the value from the NET_PRICE field is only copied if the system cannot determine a condition.
- PO_PRICE = ’1′: The value transferred in field NET_PRICE is copied as a gross price that is, it is set with the condition type specified as base price in the calculation schema. In the SAP Standard System, these are condition types PB00 or PBXX. All other condition types remain unchanged. No conditions are copied from the last document.
- PO_PRICE = ’2′: The value transferred in field NET_PRICE is copied as a net price that is, it is set with the condition type specified as base price in the calculation procedure. All other condition types are deleted.
This post will list as many BADI in SAP SRM as I can. It will be updated once I encounter new one;-).
BBP_DET_TAXCODE_BADI Exit for Determination of Tax Code
You can extend the current determination (that occurs via the domestic/international indicator and category ID), deviating from the settings in table BBP_DET_TAX_CODE Determine Tax Code for Country/Product Category.
Organization Model displays the functional and reporting structure of an enterprise. Organizational units (departments), positions, and employees (or SAP users), are structured hierarchically in the organizational model.Organization model is widely used in SAP ERP, CRM and SRM. This post only deals with the organization model in SAP SRM.
Transaction in SRM organization model
PPOSA_BBP – Display organization model
PPOMA_BBP – Process organization model
Function Group Related to SRM organization model
BBP_OM_STRUCTURE
BBP_ATTR_PDORG
Function Module
BBP_OM_STRUC_GET_POS_FROM_USER – Get the postion according passed in system user id
BBP_READ_ATTRIBUTES – Read attribute of object in organization model
Object Type in SRM organization model
US = User
S = Position
BP = Business Partner
O = Organization Unit
Read more…