Backend Info Record data transfered to Shopping Cart

[Former Member]

We are using extended classic scenario, SRM 4.0 SRM Server 5.0.

In our backend R/3 system we have standard info records created with material #, vendor, price UOM etc. I would like to show the vendor, price, uom (from the backend info record)in the Source of Supply section of a shopping cart after entering the material # (product # in SRM language). Also transfer the price and vendor to the shopping cart if desired. Has anyone found a BADI or some other method to do this???

We do not use valuated materials so EPP_Get_Backend prices does not work for us.

Thanks in advance

Edited by: Rob Forrest on Apr 3, 2008 10:36 PM

Edited by: Rob Forrest on Apr 3, 2008 10:37 PM

[Former Member]

Hi,

Try to implement the BADI "BBP_SOS_BADI" in SRM to assign the inforecord to SOS.Use the FM "META_INFORECORD_GETLIST" to get the inforecord from R/3.

Please find the necassary documenation of the BADI - BBP_SOS_BADI for your reference.

-

---

>>>>>>>>>>> <<<<<<<<<<<----

---

HY SIMGBBP_SOS_BADI

____________________________________________________

Short Text

Find and Check Sources of Supply

Use

With the Business Add-In BBP_SOS_BADI, you can search for and check sources of supply according to your own rules. These sources of supply include contracts, vendor list entries and product linkages. For this, the customer fields of the shopping cart or purchase order are transferred to the BAdI.

Standard settings

The BAdI provides the following methods:

1. BBP_SOS_INDEX_UPDATE_CHECK

Use: Check and update contract items in the source of supply table.

2. BBP_SOS_SEARCH

Use: Search for sources of supply according to your own rules.

3. BBP_SOS_CHECK

Use: Check and filter the sources of supply found by the standard search according to your own rules.

4. BBP_SOS_PD_CHECK

Use: Carrying out your own additional checks when creating a shopping cart document item with an assigned contract.

Activities

Implement the BAdI if you wish to determine or check sources of supply according to your own rules.

-

---

>>>>>>>>>>> <<<<<<<<<<<----

---

Check Update of Items into Sourcing Table

Functionality

With method BBP_SOS_INDEX_UPDATE_CHECK, you can check whether a contract item in the sourcing table BBPD_PD_INDEX is to be updated or not.

Call time: When a contract is released

Parameters

Importing

IS_CONTRACT_ITEM

Structure contains all fields of the contract item

Exporting

EV_INDEX_UPDATE_ALLOWED

If the parameter contains an 'X', the item can be updated in the sourcing table BBPD_PD_INDEX.

-

---

>>>>>>>>>>> <<<<<<<<<<<----

---

Source Search According to User's Rules

Functionality

With method BBP_SOS_SEARCH, you can search for sources of supply according to your own rules.

Call time: Before the standard search and before pricing

Parameters

Importing

IV_TOLERANT_SEARCH

In the Sourcing application, users can repeat the search for sources of supply, omitting secondary criteria, if the first search with all the criteria did not return any results. If IV_TOLERANT_SEARCH = X, the BAdI ignores the secondary criteria in the search.

IS_SEARCH_CRITERIA

Search criteria including customer fields

Exporting

ET_FOUND_CONTRACT

Table with the determined contract items

ET_FOUND_VENDORLIST

Table with the determined items in the vendor list

ET_FOUND_INTERLINKAGE

Table with the determined product linkages.

ET_CUST_SOS_MESSAGES

Return table for error messages that can be freely defined in the customer system. The system also returns these messages in the Sourcing application, for example, "Contract XYZ does not meet all the required criteria".

Changing Parameter

CV_SEARCH_FOR_CONTRACT

CV_SEARCH_FOR_VENDORLIST

CV_SEARCH_FOR_INTERLINKAGE

The parameters define if contracts, vendor lists, and product linkages are to be sought. They are set by the searching application (shopping cart; purchase order).

Notes

If the appropriate standard search is not to be carried out after the method has run, the relevant parameter must remain emtpy.

-

---

>>>>>>>>>>> <<<<<<<<<<<----

---

Check and Filter Results of Standard Search

Functionality

With method BBP_SOS_CHECK, you can use your own rules to check and filter the sources of supply that have been found by the standard search.

Call time: After the standard search and before pricing

Parameters

Importing

IV_SEARCH_FOR_CONTRACT

IV_SEARCH_FOR_VENDORLIST

IV_SEARCH_FOR_INTERLINKAGE

IV_TOLERANT_SEARCH

In the Sourcing application, users can repeat the search for sources of supply omitting secondary criteria, if the first search with all criteria did not return any results. If IV_TOLERANT_SEARCH = X, the BAdI ignores the secondary criteria in the search.

These parameters define if contracts, vendor lists and product linkages

are to be sought. They are set by the searching application (shopping cart; purchase order).

IS_SEARCH_CRITERIA

Search criteria including the user-defined fields

Changing

CT_FOUND_CONTRACT

Table with the determined contract items

CT_FOUND_VENDORLIST

Table with the determined items in the vendor list

CT_FOUND_INTERLINKAGE:

Table with the determined product linkages

ET_CUST_SOS_MESSAGES

Return table for error messages that can be freely defined in the customer system. The system also returns these messages in the Sourcing application, for example, "Contract XYZ does not meet all the required criteria".

-

---

>>>>>>>>>>> <<<<<<<<<<<----

---

Check Contracts in Purchasing Document Items

Functionality

When you create a purchasing document item with assigned contract, the system always checks the following data:

Matching of the product

Matching of the product category

Matching of the quantity unit

With method BBP_SOS_PD_CHECK, you can carry out additional user-defined checks. The system returns error or warning messages to the application via the function module BBP_PD_MSG_ADD.

Call time: When you create a shopping cart or purchase order item

Parameters

Importing

IS_CONTRACT_ITEM

Contract item data

IS_PD_ITEM

Purchasing document item data (shopping cart, purchase order)

Changing

CV_NO_FURTHER_CHECKS

If this parameter is empty, the system checks (in the standard)

the catalog data in the item

the vendor product number

If these checks are not to be carried out, the parameter must contain an X. This value is set as default.

-

---

>>>>>>>>>>> <<<<<<<<<<<----

---

The FM -> META_INFORECORD_GETLIST uses Business Object- BUS3003 to accomplish this job.

codeHere is the sample code for the FM.

DATA lt_return TYPE TABLE OF bapireturn.

DATA ls_ctr_header_data TYPE bbp_pds_ctr_header_d.

CALL FUNCTION 'META_INFORECORD_GETLIST'

EXPORTING

info_type = '0'

purchorg_data = 'X'

general_data = 'X'

logical_system = ls_ctr_header_data-logsys_fi

TABLES

return = lt_return.

APPEND LINES OF lt_return TO ct_return.

FREE lt_return.

[/code]

BR,

Disha.

Do reward points for useful answers.

[Former Member]

this is a standard functionality of CLASSIC

SRM picks info record if maintained in ECC

also it can pick up contract if maintained in source list

any possibility to shift to classic?

BR

Dinesh