SRM Settings

1. Define Back end system

SAP Implementation Guide - SAP Supplier Relationship Management -> SRM Server -> Technical Basic Settings -> Define System Landscape

The same will be updated in the BBP_BACKEND_DEST

The field Integrated UI should be ticked to show the systems that participate in procure to pay scenario

1. Assign hierarchy template to transaction type

SAP Supplier Relationship management->SRM Server-> Cross Application    Basic Settings->Service Procurement->Activate Service Procurement

Assign HIER_SE template to the transaction types which needs to be displayed in CPPR application.

Settings in the SAP ERP System

1. Register SRM System :  In the T.Code OLME  choose Portalà System Land scape

1. Enable External Sourcing :
2. In the OLME Transaction choose Portal à Business Add-Ins for Purchasing Portal à BAdI: Activate Sending of Purchase Requisition to Ext. Procurement System

You must implement the BAdI ME_REQ_SOURCING_CUST. Note that this BAdI implementation is used for transferring external requirements to SRM sourcing using SOA services and also to create RFxs directly from CPPR.

1. Activate Event Linkage

In the T.Code SWETYPV maintain the entry

BO BOR Object Type BUS2105 RFXREQUESTED WS53800009

1. 4. UOM & ISO

Ensure that the UOM and ISO are replicated to SRM system

1. 5. Implementing BaDI for RFQ Request SUITE Request

In order to use the SOA RFQRequestSUITERequest message, you have to
implement the BaDI named BBP_EBPXML_OUT_BADI. Please create a BaDI
implementation for the interface: REQUESTFORQUOTE with the following
code:

METHOD if_ex_bbp_ebpxml_out_badi~requestforquote.

* use SOA system type to get the SOA interface
* from bbp_function_map.
cv_system_type = 'ESASAPXML1'.

ENDMETHOD

The behavior of add/delete functionality of Purchase Order Schedule Line  is explained below with screenshots to understand how the  PO document and DB tables are updated with the schedule lines information.

1. Add Schedule Line: Create a Purchase Order in SRM. Add  item. Add Schedule lines to item as  below. Order PO:

Go to transaction bbp_pd. Go to item details and copy item Guid.

Go to transaction me23n to view backend PO in ERP system:

The Schedule lines will be updated in backend table EKET.

2. Delete Schedule Line: In SRM Delete 1^st schedule line and order PO.

In SRM table , Schedule line Del_Ind will be set to true for the deleted schedule line.

In backend table, hard delete of schedule line will remove the deleted schedule line entry.

I have been thinking of writing this post for a long time as not many people in SRM make use of LSMW and other similar technologies for enabling faster upload of data . I have tried to include here some of my understanding of what LSMW is and how it is different from the other BDC  which enables both recording and generation of an ABAP code using the recording .

There is always a question if  LSMW is available for SRM as well for which we need to understand that all SAP releases have this functionality and since a very long time SAP system releases (as of SAP Web AS 6.20) have LSMW as  an 'integrated' solution . Thus, no need to install an LSMW as add-on because it is already available in the system.

We just need to try using Tcode LSMW to  be able to use it .

Try IT  My recommendation is whether you are Technical or not this has got nothing to do with it . There are a set of 14 steps initially to be followed without doing ANY coding  which you need to follow to be able to automate your tasks .

Why LSMW : We can use LSMW for a good amount of upload of data by just uploading the file and the system automatically processes it in the correct format and stores at the relevant place.

• It is faster and more reliable and very less efforts needed to setup the structure of your LSMW
• For transfer of data from Legacy to SAP R/3 as a one time activity during initial setup
• Periodic data transfer or upload of data
• No coding at all just basic Configuration steps

How it can be used

- IT can be used for filling data in standard Tcodes

- It can be used for Updating  ZTables

- It can be used for filling data when you know the FM to do automatic approval for multiple documents

- It may also come in handy when we have to run FM which do not accept multiple values in one go .

A similar approach like LSMW  is the BDC called via Tcode  SHDB and just create a new recording to get started. This helps to map the new recording correctly

Difference b/w LSMW and BDC : LSMW is mainly for uploading the file BUT one has to manually execute each step as shown below to carry out the automatic changes in system

BDC is used to put the recording into a program via automatic code so that an end user be able to do the same . (Generally an end user finds it difficult to get past all the steps of LSMW ).

I have an example below for LSMW steps used in an Implementation of SRM projects where the client wanted the vendors to be extended to another purchasing org .

Create LSMW :

We have these 14 steps primarily

Step1 : Maintain object attributes  Select the button to record your steps . I am using Ztable to fill the data

which has 4 fields Vendor ,  Pur Org  , Ref vendor , Ref pur org .

After you finish your recording I used it for a Ztable we have to use Tcode SM30 to enter the data in via table entry

After you click on ‘Default all’  you would see the fields are automatically recognized .Now select this recording via the search help  Do not type it  .

Now select this recording via the search help  Do not type it  .

Step 2 : Maintain Source Structures

Create a new one as shown below

Step 3 : Maintain source fields  we are filling in 4 fields at the first screen which helps in populating data in the table.

We add all 4 fields as shown below to map them to the source structure

Vendor number , Vendor new Org , Vendor reference number , Vendor old Org .

Step 4 : Maintain Structure Relations : Nothing to be done in this step just check the source gets mapped correctly

Step 5 : Map all the source fields created above by the correct numbers             

By clicking on the source fields it would show the filed which we created in Step 3 mark them to the fields shown here . These will be the fields which will be used to pass the data based on which the new entries would  be created in the table

Step 6 : Maintain Fixed Values, Translations, User-Defined Routines

Nothing to be done

Step 7 : Specify Files

We  specify the way In which we shall be uploading the data which means  we can either upload using a R/3 server or on the PC or some other options available as you can see below .I prefer to use a file created on my desktop to be used for running LSMW .

We would see the file uploaded correctly with all the data as shown below

Step 8  :Assign Files

Check if the file is shown here automatically if not then we need to Click on change and then create assignment , But ideally it should come on its own .

Step 9  Read Data

When we execute this line it gives a POP UP as shown it will give you the number

Of entries it can find in the program . I had only 1 entry so it reads that .

We are doing a trial with 1 entry and if it works we can upload multiple entries via file upload .

The number of entry shown here is same as what has been uploaded via the file .

Step 10 : Display Read Data

When you have seen the number of records and validated them then we would want the system to read the data now and see if it has read correctly . Double click on the line and you would see if the data has been set up correctly in the corresponding fields .

Double click on the line above which has contents ..Ensure the fields are coming up correctly against the different structures .

Step 11  Convert DATA :

Execute the Tcode below to convert the data  a next screen would show the summary of the data converted which should ideally be equal to the number of records .

Step 12: Display Converted data

Now we can display the converted data

Step 13 : Create Batch Input Session execute the below to generate a batch input session .

Step 14: Run Batch input session  Find the list of batch input sessions and identify your own one and click on process

After a while you can select the entry and click on Log to check the result , and then display to check hwo many vendors have been replicated or if any went into error status .

Go back and click again and you would see the entries have been created in the Table in SM30 …

Check the logs and see the number of success entries error etc would be shown .

Want to delete the LSMW ?

1. Goto >> Administration

2. Select your entry and click on Delete .

Hope it is found useful .

Now we can try creating another program using SHDB which is the BDC technique this however requires some basic level of coding technique to be able to

create a program but is also easy enough .

Everyone must have used the Tcode SW01 while testing to approve documents from backend

to be able to do the job quickly I have prepared an easy to use BDC program.

Create a recording for approving All PO using SWO1 Tcode by entering the GUID of the PO and clicking on the method SET_RELEASED.

Below shows the recording which has been created for the SWO1 Tcode by passing the GUID .

We ask the user to pass the PO number here as input by the user as seen in the selection screen below

- Based on which the GUID would be selected from the CRMD_ORDERADM_H table .

SELECT GUID OBJECT_ID from CRMD_ORDERADM_H INTO TABLE GT_GUID

WHERE OBJECT_ID in SO_PO

- Now check for this line Open_group and create a LOOP entry to carry out the recording for each GUID one after the other .

perform open_group.

LOOP AT GT_guid into wa_guid.

- Remember to replace the hardcoded GUID value from the recording and replace it with the value which you are passing .

perform bdc_field       using 'OBJID-VALUE(01)'

                              wa_guid-guid.   "'E42CF0634B9FA2F180CB005056922C81'.

- Now check for this line close_group and just before that ENDLOOP entry should be there

ENDLOOP .

perform close_group.

Now we can execute this program by passing the PO number and get it approved .

Instead of doing this activity repeatedly using SWO1 we can take the list and Pass it by the PO number to help do the job quickly .

There could be numerous other ways this could be used .

Sorry for the long document I hope some one tried these technologies  out with the help of my document .

Good read :

http://help.sap.com/saphelp_47x200/helpdata/en/67/42fcd8f61011d1bcf9080009b4534c/frameset.htm

http://wiki.scn.sap.com/wiki/display/ABAP/Batch+Input+-+BDC

http://wiki.scn.sap.com/wiki/display/ABAP/Batch+Input+FAQ

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/309cb157-738d-2910-7691-b74c4ddba3c7?QuickLink=index&overridelayout=true&10995116287984

LSMW for Functional Consultants in simple step-by-step way

http://scn.sap.com/docs/DOC-26159

Regards

Vinita

Dear ALL ,

This is one of the new things I came across which previously was being done by modifying the webdynpro in the SRM system .

The need of this change is to  define priority for many documents like SC and Vendor list in the SOCO where they are waiting to get converted to PO

and if there is a lot of such documents it is difficult to understand how to prioritize them .

The  pre requisite for doing so is the business function SRM_CROSS_INDUSTRY_1 as we see mentioned in the link .

and is mostly used where we also have PPS implemented .

http://help.sap.com/saphelp_srm703/helpdata/en/8a/c9d50a071d493f9d1ee8fd554ccca4/content.htm

However , I am not sure how many clients really have that switch activated as well as PPS implemented .

So  , I came across a similar option in  IMG at below place .

Just though to document it as it’s a relatively new feature and not sure if many people have used it as such ..

Be default :

For SC : BUS2121 these settings are not displayed

CHANGED VALUES:

Below values come automatically and you could add a new custom entry as needed in the list below .

We can add text or add an image as shown as well ..or delete the existing options ..

Case 1 : We can let the user add value in this field in the SC display as well ..

In the SPRO config add the standard field related to document priority and make it visible . editable

And required as needed .

This will show it up in the SC item details screen.

Case 2 : We can add the value to this field automatically in the DOC_CHANGE BADI or DOC_SAVE Badi

Based on the custom logic and NO need to show it in the portal for the end user to fill it .

LOOP AT et_item INTO ls_item WHERE del_ind IS INITIAL.
“Define custom logic to populate the field priority from backend”

     ls_item-doc_priority = ‘HIGH’.

  MODIFY et_item FROM ls_item TRANSPORTING
doc_priority.

    ENDLOOP.

     

Based on the value shown in the field it will automatically come in the result column as well as in the selection criteria in the SOCO screen

Result : The buyer or the Purchasing officer can then pick up those carts which are at a higher priority than the others from the list of carts and thus speed up the PO creation for them.

Note : This requirement has been asked by many clients I have worked with before and it generally use to require modifying the Webdynpro component

/SAPSRM/WDC_DO_SOCO_GAF_1  both its selection criteria and its result column section .

However now we can reduce the efforts by making use of this functionality in the config itself .

I have not used it for Vendor list as such but maybe someone else can try doing that and post a document for it here as well .

Thanks for your time to read through . Do let me know if this helps !

Regards

Vinita

Hello People,

I am working in to SAP MM- SRM Support services. Majority of what I do consists of reporting of various things according to user requirement. And most of what I do is to get certain data from one table pass it onto others and get some other data and join them into excel and present it to client.

For few weeks i use to do it Manually and didn't know that SAP has anything/program to help me get of exactly what I want.

Because most the system is customized and even for standard report and analysis was not producing the data my client required for further analysis.

So after few research here and there, reading many new functionalities and even understanding the creation of BAPIs for certain data creation and background jobs, but I was not satisfied as the client requirement would vary a lot on within few set of filters and stuff and I, being a Functional consultant side, didn't know on how to create BAPIs and it was also way smaller job so as to create a BAPI for the same.

But in all this mess of a research I came across the SAP Functionality of query Creation SQVI, It was exactly what i was looking for !!

THIS WORKS FOR SAP MM-SRM or any other tables. I am here taking an example for tables in SAP SRM.

It was simple to understand and easy to work with. Just few mins into the functionality and I know I have found my cancer's cure.

So for all those who are still suffering here is all you need to know for all the table related reports you were generating.

I would like to explain it with an example so for our better understanding.

My Client came up with the requirement that, they want a list of Shopping cart from the given list of PO in SAP SRM

MANUAL/PAST METHOD :

Into SE16 Transaction

PART 1: Insert PO data into table BBP_PDBEI

PART 2: Get 'Object GUID' from the above table and insert it in the table CRMD_ORDERADM_I

PART 3: Get '(Parent) Object GUID from the above table and insert it in the table CRMD_ORDERADM_H and get the list of required SC

PART 4: We have to combine all the sheets so as to know which Shopping Cart is for which Purchase Order, using VLOOKUP Functionality in Microsoft Excel.

Now instead we can use Transaction SQVI and proceed as follows:

1. Open the screen and in the "Quick View" Box, Enter the name of your query, can be anything, let say " PO_LIST_FROM_SC"

2. Click Create.

3. Choose a title. ( can be same PO_LIST_FRM_SC ). NOW CHOOSE "TABLE JOIN" in the data source, as we want to join few tables to get our report. and Basic or Layout mode choose any,

4, Now a blank screen will open with the title " Create QuickView ( your name of query, in our case PO_LIST_FRM_SC) : Choose data source

5. As you can see few icons on the top of the page, Click on the second Icon of "Insert Table". and insert the table you want to join, in our case ,

    "BBP_PDBEI".

    Repeat the process and insert the tables "CRMD_ORDERADM_I" and "CRMD_ORDERADM_H" as well.

    All the tables can be seen as a box in the screen with their titles

6. As you can see there is small link( thin black line) between the tables. This line is how the system would match the data between tables and would

    create a common table. see that there are no two lines in our case because we just want to match the list of 'Object GUID' into first two tables

    "BBP_PDBEI" and "CRMD_ORDERADM_I".

    If there are 2 lines then we can simply click one of them and right click and use "delete link" to delete the link. we can also pick and drop the link on the

    fields that we like to match between tables.

7. Now do the same between the tables "CRMD_ORDERADM_I" and "CRMD_ORDERADM_H" and join the "(Parent) Object GUID" from the first table to

    "Object GUID" in the second.

8. You can also click the first Icon on the menu bar and can check the link joined between all the tables are defined correctly or not.

    You can see the tables joined in the navigation view in the lower center of the screen and can also see the area covered by our screen.

9.  Now go press the back button and come on the initial screen. This screen is mainly divided into two parts, but basically both of them would perform the

     same thing to our table. i.e. that it would help us with the field that we want to be on display and the we fields we want to hide.

    As you can see on the LEFT hand side of the screen, the names of our tables listed , drop down them (double click) and choose the view that you want to

    be  it 'Listed' in the result and fields that are present to enter the data or selection fields.

    In our case the listed fields would be Shopping Cart numbers and Purchase order numbers

    And selection field would be Purchase order numbers.( we can use as many fields as we want from all the listed tables)

10. Execute and you would reach a new program. This is what we require.

Now insert the PO numbers and execute and you would get List of shopping cart related to it.

WE have to create only once this query and every one can use it from the 'SA38' - Program executor.

Please Note: For others to use the program, you need to write down the name of the program when you in step 10, in the above process and share it manually with everyone in the team for them to use it.

So this was a simplest example that I can come up with for using this extraordinary function " SQVI". You can join various tables and other data sources given in the option and explore this option.

It worked for me as a life saver from daily reporting of various things.

I hope it does the same for you.

Please share your thoughts and experiences on the using this function.

PS: Remember this, as only the user who have created the query can edit it into the system , no one else can. And also you can always use the same transaction 'SQVI' to make any changes in the queries you have created.

Workflow is not available for Purchase Requisitions(PR) which are transferred to SRM. The shopping carts created in SRM for those Purchase Requisitions are set to ordered status without workflow approvals.

Feature:

This feature allows you to use SAP Supplier Relationship Management (SRM) workflow for approval of external requirements. It is applicable for a purchase requisition which is created in the SAP ERP system and transferred to the SAP SRM system for sourcing using the report, BBP_EXTREQ_TRANSFER.

While creating the PR requester needs to be mentioned and the user mentioned as requester should be available in SRM organization structure. This is required to find the approver for the workflow process.If the document get rejected by the approver during the workflow process then the closed indicator is set in the PR.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_1 and then activate the Customizing switch External Approval of ERP Purchase Requisitions(SRM_701_PR_APPROVAL) under SRM Server-> Sourcing->Activate/Deactivate External Approval of ERP Purchase Requisitions.

For information related to External Approval of ERP Purchase Requisitions refer the note: 2258525

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

In case of commodity procurement most of the time the condition values are based on some formula such as average, median, etc of the commodity value. Hence there is a need for formula based condition types in SRM for calculating the condition values based on the formula.

Feature:

This feature allows the user to define a formula and associate it with a condition type. User can then click on the formula hyper link and determine the change of price for a purchase order or contract based on the condition type and the formula associated with it.

Formula based condition is enabled for:

     Purchase Order

     Central Contract

User can maintain the formula values by clicking on the Formula hyper link that appears against the condition type.

The values entered in the formula will decide the Condition amount.

Information:

To use this feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Formula Based Condition for PO and Contract(SRM_703_LDH_PO) under SRM Server-> Cross-Application Basic Settings->Pricing-> Activate/Deactivate Formula Based Condition for PO and Contract.

Formula can be defined using the transaction, /nbrfplus. Formula ID for a condition type needs to be created first using this transaction.

Formula can be associated to a condition type and business object( Contract or PO ) in SAP SRM under: SRM Server-> Cross-Application Basic Settings->Pricing-> Maintain Formula for Purchase Order and Contract

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

Subcontracting is a standard process in SAP ERP. But, this is not a core feature of SAP SRM but is a Procurement for Public Sector(PPS) solution.

Feature:

Subcontracting feature is retrofitted to SRM core. Subcontracting allows user to order a product from a supplier who requires certain components to manufacture the product. The components are provided by the ordering party. They are consumed or transformed during the production.

The subcontracting components you provide to the supplier are based on a Bill of Material(BOM) for the product that is stored in the SAP ERP system. Subcontracting in the SAP Supplier Relationship Management (SAP SRM) system is limited to fulfilling requirements that are based on purchase requisitions created in SAP ERP where the component data is available or creation of BOM from a central contract if it is not created in the SAP ERP system.

The component information is routed through the procurement process in SAP SRM. In sourcing, the subcontracting requisition can be sourced against a suitable subcontracting contract. Goods issue of the components as well as goods receipt for the product is carried out in the SAP ERP system.

User can create a BOM for a  product in the SAP ERP system. It automatically provides the components for a Subcontracting Purchase Requisition. The system routes the PR through procurement process in SRM if extended classic scenario with PPS functionality is used.

In SRM user can create a Contract line item as a subcontracting line item. This line item can then be used as a source of supply for subcontracting PR line item. The subcontracting components can be viewed in SRM but cannot be changed. User can create a BOM from a Central Contract at item level within SAP SRM if the BOM doesn't exists in SAP ERP. The data from the BOM gets updated in the SAP ERP system. User cannot update BOM once it is successfully replicated to SAP ERP system. After Purchase Order is successfully replicated to SAP ERP the follow on activities can be carried out there.

Information:

In the SAP ERP system:

• Activate the Customizing switch under SAP Customizing Implementation GuidePublic Sector ManagementActivate Functions for Procurement for Public Sector. Select the check box against SRM Government Procurement.

• Activate the customizing switch under SAP Customizing Implementation Guide Public Sector ManagementActivate restricted subcontracting. Execute the customizing and select the checkbox against the Subcontracting field

• Maintain profiles for procurement of external requirements under SAP Customizing Implementation GuideIntegration with other SAP components Supplier Relationship Management Plan Driven ProcurementMaintain Profiles for External Procurement. This allows transfer of purchase requisitions from the SAP ERP system to the SAP SRM system

• Maintain the combinations of material group and purchasing groups according to the profiles under SAP Customizing Implementation GuideIntegration with other SAP ComponentsSupplier Relationship Management Plan Driven Procurement Control External procurementIntegration with other SAP Components.

• Implement SAP Note 2200270.

In the SAP SRM system:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR3 and then activate the Customizing switch Subcontracting(CIF_702_SUBCONTRACTING) under SRM Server-> Cross-Application Basic Settings->Subcontracting-> Activate/Deactivate Subcontracting.

To enable creation of BOM from a central contract within SAP SRM activate the Customizing Switch under,SRM Server-> Cross-Application Basic Settings->Subcontracting-> Activate/Deactivate Creation of BOM from Contract.

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

There is no option for the user to trigger notification to supplier about the changes in Central Contract over a period of time.

Feature:

This feature allows user to trigger notifications when changes are made to a contract. The purchaser can choose to notify self and the supplier.

Report, /SAPSRM/CTR_CHANGE_PRT_NOTIFY enables this feature.

This report is used to notify supplier about the changes in Contract over a period of time. Information is sent as a PDF attachment to the supplier.

Enhancement spot,  /SAPSRM/ES_CTR_CHG_NOTIF can be used to change the following:

     Filter result list of Contract

     Change Smart Form

     Change the email id to which mail is sent

     Change subject and body of the email that is sent to supplier

     Change subject and body of email sent to user in case of errors

     Filter change document list

In case there are errors after executing the report, then the same can be displayed in SLG1 with object id, /SAPSRM/CTR_NOTIFY.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Notify Contract changes to Supplier(SRM_703_CTR_EDIT_NOTIFY) under SRM Server-> Continuous Improvement-> Activate/Deactivate Notify Changes to Contract.

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

It is possible to negotiate the items in a single Contract at a time.

Feature:

This function allows users to negotiate items from multiple contracts. User can select items from multiple contracts and create the follow-on bidding documents for items based on split criteria. For example, items can be split from multiple contracts based on suppliers, purchase organizations, and create the bidding documents accordingly.

In Contract Negotiation Cockpit, user can search for items in Contract. There is a default search criteria available. This criteria can be modified using the BAdI, /SAPSRM/BD_CTR_YEN_SEARCH. There is a pre defined result set which can also be modified using the same BAdI.

User can create an RFx by selecting the Contract items and clicking Create Draft button. There are four default options for creating an RFx:

     Create a single RFx

     RFx per Supplier

     RFx per Purchasing Organization

     RFx per Product Category

If the RFx is created from items from different Contracts belonging to different Purchasing Organization then in case of per Supplier/per RFx the header data is not copied to the RFx. If contract items belong to different suppliers then all the suppliers are copied to the RFx as bidders.

Use can process the selected draft RFx by choosing Process selected drafts or Process All drafts button. Draft RFx or items can be removed by clicking Remove button. The details of the selected draft can be seen in the Details of selected draft screen area.

If the threshold for the Contract Negotiation Cockpit exceeds the background threshold then the creation of RFx document(s) is carried out in background. A mail is sent to the Purchaser with the complete details of the Contracts and the created RFx with the item numbers.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Contract Negotiation Cockpit(SRM_703_CTR_YEAR_END_NEG) under SRM Server-> Cross-Application Basic Settings->Contract Negotiation Cockpit-> Activate/Deactivate Contract Negotiation Cockpit.

Grouping Criteria can be modified under SRM Server-> Cross-Application Basic Settings->Contract Negotiation Cockpit-> Maintain Grouping Criteria.

Background threshold can be maintained for Contract Negotiation Cockpit under SRM Server-> Cross-Application Basic Settings->Background Processing-> Define Threshold Value for Background Processing.

BAdI to modify search criteria and result list can be accessed under SRM Server-> Business Add-Ins->Contract Management-> BAdI: Enhance Search Criteria and Result.

BAdI to modify the grouping criteria can be access under SRM Server-> Business Add-Ins->Contract Management-> BAdI: Enhance Grouping Criteria.

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

As part of SAP SRM 7.03 SP11  the following features are delivered:

Undo Accept or Undo Reject a Bid:

     This feature enables the option to revert the acceptance or rejection of a RFx Response in bid decoupling scenario.

Generic Text Templates:

     This feature provides a central location to create or edit the text templates and use them across business objects.

Adoption of a Formula:

     This feature allows you to update the factors, value of the factors and the formula associated with a purchase order or a contract. This feature is an enhancement to the feature Formula based Condition for PO or Contract.

You can find detailed description about these features by following the links mentioned below:

Undo Accept or Undo Reject a Bid

Generic Text Templates

Adoption of a Formula

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

In Bid Decoupled scenario(Response outside firewall scenario) it is not possible to reverse the acceptance or rejection of a RFx Response. The buttons Undo Accept and Undo Reject are disabled in Response.

Feature:

This feature provides the option to revert the acceptance or rejection of a bid or an RFx response in the strategic sourcing with bid decoupling scenario. This is applicable for RFx response submission outside the firewall, that is in the supplier system.

Information:

The switch for RFx Response Submission Outside Firewall should be active: SAP Supplier Relationship Management-> Supplier Collaboration-> Activate/Deactivate RFx Response Submission Outside Firewall

Notes:

2223644 - Interface Note: Implementing Undo accept and Undo reject functionality for Bid decoupling scenario

2235000 - Implementation Note: Activation of Undo accept and Undo reject buttons for Bid decoupling

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

Feature, Text Templates is introduced in SAP SRM 713 SP09. This is an enhancement to this feature.

Feature:

This feature provides a central location to create or edit the text templates and use them across the following business objects:

• Shopping Cart
• Purchase Order
• RFx
• RFx Response
• Central Contract

The template created for one note type cannot be used for another note type.

Information:

To use the feature, you have to first activate the Business Function SRM_CONT_IMPR_3 and then activate the Customizing switch Text Templates for Notes(SRM_703_TEXT_TEMPLATE) under SRM Server Cross-Application Basic Settings Text TemplatesActivate/Deactivate Text Templates for Notes.

Text template feature for business objects can be enabled under the customizing: SRM Server Cross-Application Basic Settings Text Templates Define Business Objects for Text Templates.

For details related to Text Templates refer:Text Templates

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

Feature, Formula based Condition in PO and Contract is available from SAP SRM 713 SP10. Adoption of a Formula is an enhancement of this feature.

Feature:

This feature allows users to update the factors, value of the factors and the formula associated with a purchase order or a contract. The options that are maintained appear under the Adopt Formula button under a purchase order or a contract.

The button Adopt Formula will appear in Edit mode of the document.

User can define actions to adopt a Formula. The default actions that are provided are Assign, Adjust and Update.

Assign - allows to assign a formula to PO or Contract.

Update Formula Fields - Applies the changes in the fields associated with a formula

Adopt - Incorporates changes made to an existing formula

Information:

Actions can be defined under

SRM Server-> Cross-Application Basic Settings->Pricing-> Define Actions for Adoption of a Formula.

For details related to Formula based Condition in PO and Contract refer: Formula based Conditions for Purchase Order and Central Contract

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

Large Document Handling(LDH) is enabled for Central Contract and RFx in SAP SRM 713 SP07 and Purchase Order in SAP SRM 713 SP08.  In order to get an idea about Large Document Handling refer: Large Document Handling

In SP10 we have enabled LDH for RFx Response. All the features mentioned for LDH in general in the above mentioned document is applicable for RFx Response as well.

Feature:

When a Purchase Order is displayed in Large Document Handling mode, none of the items are loaded. User will be able to search for the desired items and work with that limited set of items. This helps in improving performance and also improves usability.

Following header actions are performed in background for Purchase Order displayed in LDH mode:

     Adopt, Print preview, Export, Import, Check, Submit, Reject, Accept, Publish to Catalog.

Following are the changes with respect to item actions:

     New Items are always added at the end of the list.

     Addition of expressive items for items in RFx is carried out in background.

     Deletion of newly added items in Response including expressive items is carried out in background.

     Pasting of copied items which are newly added in the Response is done at the end of the list.

Information:

To use the feature, you have to first activate the Business Function SRM_LDH_3 and then activate the Customizing switch Large Document Handling for RFx Response(SRM_703_LDH_RFX_RESP) under SRM Server-> Cross-Application Basic Settings->Large Document Handling-> Activate/Deactivate Large Document Handling for RFx Response.

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

As part of SAP SRM 7.03 SP10  the following features are delivered:

Contract Negotiation Cockpit:

     This feature introduces a new cockpit for users to select items from multiple contracts and create follow on bidding documents for those items based on grouping criteria.

Large Document Handling for RFx Response:

     In SP07 we have delivered Large Document Handling for Central Contract and RFx and in SP08 for Purchase Order. In SP10 we have delivered LDH for RFx Response.

Approve Purchase Requisition in SAP SRM:

     This feature allows users to use SAP Supplier Relationship Management (SRM) workflow for the approval of external requirements.

Formula based Conditions for PO and Contract:

     This feature allows users to create a formula and associate it with a condition type. User can click on the Formula hyper link and determine the change of price for a purchase order or contract based on the condition type and formula associated with it.

Subcontracting:

     This feature allows users to enable subcontracting in SAP SRM.

Notify changes to Contract:

     This feature allows user to trigger notifications to supplier when changes are made to a contract.

You can find detailed description about these features by following the links mentioned below:

Contract Negotiation Cockpit

Large Document Handling for RFx Response

Approve Purchase Requisitions in SAP SRM

Formula based Conditions for Purchase Order and Central Contract

Subcontracting

Notify Changes to Contract

For complete details about SAP SRM 7.03 refer: SAP SRM 7.03

SAP Supplier Relationship Management (SAP SRM) provides you with innovative methods to coordinate your business processes with your key suppliers and make them more effective. SAP SRM enables you to optimize your procurement strategy, to work more effectively with your supplier pool, and thus to gain long-term benefits from all your supplier relationships.

In this document you can find more information related to SAP SRM 703.

Details about SAP SRM 703

Support Package(SP) 01:

SP01 is available since August, 2013

Porting of SAP SRM to HANA database is done in this SP. For details related to SAP SRM 7.03 SP01 refer: SAP SRM 7.0 Enhancement Package 3 SP01

Support Package(SP) 02:

SP02 is Available since November, 2013

New features are introduced in this SP. The features are introduced as part of Customer Connection initiative. After having released the first set of Fiori Apps for the Shopping Cart, now with SRM 7.03 Support Package 2 the Fiori App for SRM Purchase Order Approval is delivered. For details related to SAP SRM 7.03 SP02 refer: SAP SRM 7.0 Enhancement Package 3 SP02

Support Package(SP) 03:

SP03 is Available since January, 2014

Performance optimizing of POWL by making use of HANA capabilities is done in this SP. For details related to SAP SRM 7.03 SP03 refer: SAP SRM 7.0 Enhancement Package 3 SP03

Support Package(SP) 04:

SP04 is available since April, 2014

Performance improvement is the key deliverable of SP04. For details related to SAP SRM 7.03 SP04 refer: SAP SRM 7.0 Enhancement Package 3 SP04

Support Package(SP) 06:

SP06 is Available since October, 2014

New features are introduced in this SP. The features are introduced as part of Customer Connection initiative. SRM Fiori Carry out Sourcing App is delivered in this SP. For details related to SAP SRM 7.03 SP06 refer: SAP SRM 7.0 Enhancement Package 3 SP06

Support Package(SP) 07:

SP07 is Available since January, 2015

New features are introduced in this SP. In addition to the features introduced as part of Customer Connection initiative several other features addressing the pain points of customers are also introduced.

For details related to SAP SRM 7.03 SP07 refer: SAP SRM 7.0 Enhancement Package 3 SP07

Support Package(SP) 08:

SP08 is Available since April, 2015

New features are introduced in this SP. Features  addressing the pain points of customers are introduced in this SP. For details related to SAP SRM 7.03 SP08 refer: SAP SRM 7.0 Enhancement Package 3 SP08

Support Package(SP) 09:

SP09 is Available since July, 2015

New features are introduced in this SP. Features addressing the pain points of customers are introduced in this SP. For details related to SAP SRM 7.03 SP09 refer: SAP SRM 7.0 Enhancement Package 3 SP09

Support Package(SP) 10:

SP10 is Available since October, 2015

New features are introduced in this SP. Features addressing the pain points of customers are also introduced in this SP. For details related to SAP SRM 7.03 SP10 refer: SAP SRM 7.0 Enhancement Package 3 SP10

Support Package(SP) 11:

SP10 is Available since January, 2016

New features are introduced in this SP. For details related to SAP SRM 7.03 SP11 refer: SAP SRM 7.0 Enhancement Package 3 SP11

Useful Links:

Link to RKT Material

SAP Enhancement Package 3 for SRM 7.0 Overview

SAP Enhancement Package 3 for SRM 7.0 SP Overview

In this document you learn how to add custom fields in the shopping cart. Then we will see how to add these fields in POWL.

This can also be applied to other business objects.

Adding the custom field in SC

Go to the following path in SPRO:

SAP Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Extensions and Field Control (Personalization)

Define customer fields at Header Level.

Within Configure Customer Fields -> Define Customer Fields on Header Level we need to add the field in two places:

Append the field first in Append for Customer Cross-Document Database Fields on Header. Create a new Append Structure if you have not any:

Add the field you want (should start with ZZ) in my case I have created a data element that is a CHAR 4 with a domain with some values.

Don’t active the structure yet, we need to add the field in another structure and it takes a lot of time in the activation so we are going to active both structures at the same time.

Append the field also in Append for Customer Fields on Shopping Cart Header you need to create also another Append Structure if you have not any.

Now, active both structures don’t worry it takes a lot of time.

Configure field control.

For display the field we need to add it in Configure Field Control -> Configure Control for Fields on Header Level -> Metadata for Fields on Document Headers

Add a new entry for BUS2121 and mark it as Enabled and Visible:

At this point you can define a dynamic class and method for control de visualization of the field. For this example is not necessary but if you want only need to create a class with Super Class /SAPSRM/CL_PDO_DYN_META_FIELD and a method with the following parameters:

With the parameter CS_METADATA you can modify the visualization of the field dynamically.

Now the field is displayed:

Now the objective is add this field as selection criteria in POWL:

Adding the custom field in POWL

Add the field in DB Criteria

Now we need to add this field also in the view /SAPSRM/V_SRC_CR. So go to SM30 and add the field:

We need to know which the feeder is used for SC for continue.

Go to the following path in SPRO:

SAP Supplier Relationship Management à SRM Server à Cross-Application Basic Settings à POWL and Advanced Search.

Enter in Define Default POWL Application for Advanced Searchand look up the Query Id for the object type BUS2121. We can see that is SAPSRM_AL_PURCHASING_02_01.

Now go to the transaction POWL_QUERYand find this Query Id.

Do double-click there and you can see what the feeder is.

Ok, return to SPRO and go to Adjust POWL Layout, Search Criteria, and Pushbuttons (transaction /SAPSRM/POWL_CUST).

Find the feeder type and select DB Criteria and add a new line with the field. At this point you can assign the search help used for this field in POWL.

Now, if you go to POWL you don’t see the field yet. Why?. You need to ‘refresh’ the Query. For do that go to se38 to the program POWL_D01set your user and mark Display. Then choose the correct feeder and use the Delete query button.

Now the field is displayed.

Add the field in result list

If you also want to display the field in the result list is necessary to add it in the structure /SAPSRM/S_POWL_RESULT_SC_ITM. There is an include reserved for this purpose INCL_EEW_PD_SEARCH_HDR_CSF_SC“Cust.Enhancements in Shoppg Cart Header: Search Results”. Create an Append structure in this structure and add the field.

Return to SPRO Adjust POWL Layout, Search Criteria, and Pushbuttons  or transaction /SAPSRM/POWL_CUSTand add the field.

Refresh the query with the program POWL_D01and now the field is also displayed in the result list.

    Change POWL dinamically

Within the enhancement spot /SAPSRM/BD_CLL_POWL_FEEDERyou have four Badi Definitions for change the behavior of POWL.

Let see a tiny example of use of one of these BADI definitions, goto SE18 and choose Display.

Expand the node /SAPSRM/BD_POWL_CHNG_SELCRIT and choose Create BADI implementation.

First, create the Enhancement implementation. Choose “New” and create a new one.

Then choose it and push Ok:

Now, create the BADI Implementation:

Now, if you want you can define a filter for specify with wich feeder the badi will be triggerd, is good to do it but in this case is not necessary we’re going to control it by code. So, go to the implementing class:

In the signature of the method you have the parameters you need to know the feeder and application ID.

Let’s see a sample code for hide the field or change the search help is used:

  DATA: ls_selcriteria LIKE LINE OF ct_selcriteria.  IF iv_flt_powl_type   EQ 'SAPSRM_FEEDER_SC_PROF'.    READ TABLE ct_selcriteria INTO ls_selcriteria WITH KEY selname = 'ZZ_CUSTOM_FLD'.    IF sy-langu EQ 'ES'. "Put here the condition you want...      ls_selcriteria-hidden = 'X'.    ELSE.      ls_selcriteria-ddic_shlp = 'ZZ_OTHER_DDIC_SHELP'.      ls_selcriteria-mandatory = 'X'.    ENDIF.    MODIFY ct_selcriteria FROM ls_selcriteria INDEX sy-tabix.  ENDIF.

Related Content

http://wiki.sdn.sap.com/wiki/display/WDABAP/Documentation+Information+about+POWL

http://wiki.sdn.sap.com/wiki/display/WDABAP/POWL

http://wiki.sdn.sap.com/wiki/display/WDABAP/FAQ+ABOUT+POWL