Sie sind auf Seite 1von 3

Overview of RFx:

An RFX can be thought of as a general mechanism that allows buyers and sellers to conduct business. often the exchange of specific items or services for a specific price, but also the exchange of information, such as capabilities or willingness. RFx is a general term used to represent different types of RFx: 1. Request for Information: Generally used to elicit information from market on a requirement. 2. Request for Proposal: Used for complex requirement and project where buyer outlines the requirement in an RFP and Supplier submit the Detail response for the same. 3. Request for Quotation: Used for Standard items and services where both buyer and supplier are clear about the specifications of the product.

Implementing RFx Functionality: Assumption: All Basic Settings of SAP SRM has already been done.
1. Number Range: Mainatain the number ranges using the menu path SPRO>>SAP Implementation Guide>>Supplier Relationship Management>>SRM Server>>Cross Application Basic Settings >>Number Ranges>>SRM Server Number Ranges>>Define Number Ranges for Local RFxs.

2. Define Transaction Type: Maintain Transaction types using menu path SPRO>>SAP Implementation Guide>>Supplier Performance Management>>SRM Server>>Cross Application Basic Settings>>Define Transaction Types.

3. Define Transaction type for RFx in organizational Plan: Using Transaction PPOMA_BBP, define the Transaction type for RFxs in the Organizational plan and assign the attributes TEND_TYPE to the responsible user.

4. Define Output settings: In order to emable the user to Print RFx, send them by email, and Fax them to bidders: >> Maintain Printer settings for the users in your system. >> Mainatin email-address and fax number of your bidders in the web interface of SAP Supplier Relationship management. >> Define processing types and forms that are used to output documents. Make Printer Settings: a) Run Tcode : PPOMA_BBP b) Select the users you require. c) Add value a PRI for Attribute "default Printer".

Make Email address and fax numbers of bidders: a) on the Web interface of SAP SRM, Choose Manage Business partner. b) Search for the bidders and enter their Fax number and Email-address. Define the processing types and forms that are used to output documents: Menu Path: SRM Server>>Cross Application Basic Settings>>Set output Actions and Output Format>>Define Actions for Document output.

5. Define Sourcing for Product Categories: Sourcing rules applicable for each product category is defined in menu path : SPRO>>SAP Implementation Guide>>Supplier Relationship Management>>SRM Server>>Sourcing>>Define Sourcing for Product Categories.

Sourcing Rules available in Settings: 1. Sourcing is never Carried out: if Source of Supplier does not exist in the requirement,then an incomplete Purchase order is created. 2. Sourcing is always carried out: All requirement are transferred to sourcing cockpit. 3. Sourcing is carried out for items without a source of supply: In absence of Source of supply, the requirement is transferred to the sourcing cockpit. 4. Sourcing Via automatic bid invitation for items without a source of supply: System create a bid invitation for all requirements that do not have a source of supply.

Adjust Roles: a) Adjust Roles for Internal Employees: In order to maintain the bidding functions of SAP Bidding Engine, one should maintain the roles responsible for RFx and RFX responses. Roles: /SAPSRM/OP_Purchaser -- Operational purchaser /SAPSRM/ST_Purchaser -- Strategic Purchaser b.) Adjust roles for External Business Partner: we can create companies and bidder contacts and assign them the role /SAPSRM/SUPPLIER. if we want to allow those external users to participate in strategic Sourcing events such as RFx and Auction we must assign them the role: /SAPSRM/BIDDER. Some Important Application Controlled workflow: WS79000002: One-Step approval for bid. WS14500026: Without approval for publication of RFx and its change version. WS14500027: One-Step approval for publication of RFx and its change version.