Source of supply (info record) in Shopping cart-extended classic

Hi experts,
We are on SRM 7.0.
We have changes from classic scenario to extended classic scenario, and after this a problem has come up?
When I create s a shopping cart for a product number, I have to allocate the vendor manually. If I activate the source of supply tab, I can't se the info record for the product number, which are created in the back-end.
I the classic scenarion is was working as this:
1. Create a shopping cart
2. Go to the tab 'source of supply'
3. Choose the vendor from different info records created in the back-end.
4. order the shopping cart
In the extended classic it is working as this:
1. Create a shopping cart
2. Go to the tab 'source of supply'
3. There are NO info record to choose from, even though I have created different info records in the back-end. I have to search for the vendor, and can't se any info record number. By this I can't get the right vendor assigned to the shopping cart???
Kim

Hi
in classic inforecord come as sos but not in EXTENDED CLASSIC.
in ecs inforecord is not a source of supply.
br
muthu

Similar Messages

Capturing Tax code from info record into shopping cart

We have a requirement where in we need to capture the tax code from the info record into the shopping cart in SRM .
If anyone has worked on a similar requirement , could you kindly share the details related to the solution.

Dear Poster
Your thread has had no response since it's creation over
2 weeks ago, therefore, I recommend that you either:
- Rephrase the question.
- Provide additional Information to prompt a response.
- Close the thread if the answer is already known.
Thank you for your compliance in this regard.
Jason Boggans
SAP SRM SDN Moderator

Source list is not getting in shopping cart

hi friends,
i am not getting the source list in the shopping cart for the particular material even though i am maintaining in backend and maintained in the web (vendors list) as a high priority vendor.To create a PO in the backend i need to maintain source of supply.so Anyone please give me the solution.
thanks
chakradhar

i think you can not use source list as source of supply in srm though you are in classic mode.
but you can refer the backend conract in the newly creating vendor list.
and select a backend system and search a contract.
and release a vendor list
br
Muthu

Difference between source list and info records

Dear All,
What is the difference between Source List and Info Records?
Thanks N Regards
Anandasiva

Hi,
The source list is the list which shows the sources from which you can procure the material. If you have ticked the source list requirement in the material master, then you can procure the material only from the vendors mentioned in the source list.
In Inf Record, you maintain the data for a material supplied by a vendor. e.g. Material price, tax code, other conditions,, buyer code, delivery & payment terms.
Hope your requirement is fulfilled.
Reward points if the answer is helpful.
Regards,
Prashant Kolhatkar

Is it possible to make Supplier field Mandatory in Shopping Cart (SRM7.0)?

Hi Experts,
We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario.
We are only using Shopping Cart functionality and most of the Material and services will have Contract & Pur. Info Records in ECC B/E system.
in SRM, if any Product don't have any SoS , then user can assign Supplier code and Price manually in S/C and Classic PO creates automatically. But if User missed to enter Supplier code then, in that case we neither want to sent the S/C to the Sourcing Cockpit nor want to create ECC PR from it.
If there is NO any SoS ( ECC Contract or Pur Info Record) exist , then user MUST have to enter Supplier code & price manually and so we want to set the fields SUPPLIER & PRICE MANDATORY.
Is it Possible ? if yes , then how this can be done ?
Thanks
NAP

>
NarendraPatil wrote:
> Hi Experts,
>
> We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario.
>
> We are only using Shopping Cart functionality and most of the Material and services will have Contract & Pur. Info Records in ECC B/E system.
>
> in SRM, if any Product don't have any SoS , then user can assign Supplier code and Price manually in S/C and Classic PO creates automatically. But if User missed to enter Supplier code then, in that case we neither want to sent the S/C to the Sourcing Cockpit nor want to create ECC PR from it. - If the REQUESTIONER enter prefered vendor - it can create only PR IF NO SOURCING . if REQUESTIOTIONER selected fixed vendor - Then PO created .
here you are giving more control to REQUISITIONER department than Purchasing department.
>
> If there is NO any SoS ( ECC Contract or Pur Info Record) exist , then user MUST have to enter Supplier code & price manually and so we want to set the fields SUPPLIER & PRICE MANDATORY.
you can validate any field to make mandatory...and spit error by doc check BADI.
>
> Is it Possible ? if yes , then how this can be done ?
>
> Thanks
> NAP
Though business allows REQUISITIONER wants to create PO directly from the shopping cart without BUYER intervention and WITHOUT Fixed vendor . no issues . Asimple logic to change preferred vendor 39 to fixed vendor 19 logic by doc change badi
so whenever REQUESTIONER assign a preffered vendor it can create a Purchase order.
Assigning source of supply decision is very critical to business . Business wants always it should be competetive best price.
Hope you understand ..

Supplier not transferred from shopping cart to PO

HI,
We are on SRM 7.1 ECS.
The issue we are facing is with the presferred supplier value enetred
in shoping cart.When a shopping cart which has a preferread supplier
enetred in shopping cart appears in sourcing cockpit and when the cart
is converted to PO in sourcing,the supplier/vendor ID disappears from
the shopping cart and the corrresponding warning message can be seen in
sourcing application and error message in PO aplication .
This issue doeasnt happen if the supplier is eneterd in soucing.
Any idea what is the fix for this issue?
Edited by: cg_srm on Oct 19, 2011 8:37 PM

Hello Lisa,
We have the exact problem described above and applied 1656774 but did not resolve the issue. You indicated that there is a prerequisite. And wow do we find out the prerequisites?
While apply the following errror was being noticed
Syntax error
Class /SAPSRM/CL_CH_WD_DOM_SOSCO_GAF2, Method REFRESH_ROWS
FORMAL parameter “IV_NO_EXTN_FIELDS” does not exist.
Detail
Erros Description Formal parameter “IV_NO_EXTN_FIELDS” does not exist
Error Description Formal parameter “IV_NO_EXTN_FIELDS” does not exist
May 1st, 2012 - Update 2:16 CDT
Okay – this is an update – The fix would work but you want to make sure that 1576240 has to be first implemented and then only you can implement 1656774. The issue is resolved.

Source list without info record

Dear.
Can I create a source list (ME01 trx.) without the info record ?
Thanks.

In what system are you? still in SAP ECC6 or in an earlier release?
How do you maintain the source list, copying or manual entry?
is your source just an external vendor, or is it a vendor with plant assignment, or do you just enter a plant number as source?
Can it be that you set the indicator for fixed source or MRP relevant? in this case you have to have an info record, as a source assignment will be done from MRP run and can be used for auto PO creation.

Generate Source List - Including Info Records

Hi!
I am generating source lists. Does anyone have an understanding of the "Including Info Records" check box on that screen. I was told not to check it, but I can't help be curious as to what happens if I do or don't check it.
Regards,
Judi

Hi,
the system will check for info records and if it finds one, the source will be added to the source list.
It is normally flagged because this is exactly what you want to do. (i.e. generate the source lists on the basis of the info records athat are there)
If you leave it unflagged then only outline agreements etc. will be added to the source list.
Steve B

Unable to create a PO from a shopping cart in classic scenerio

Hi Experts,
I tried creating a PO from the Shopping cart, but i am getting an error Number range 70 doesnt exist. Whereas
when i tried creating a PO from Rfx, PO is getting created. Can somebody suggest what would have went wrong.
Regards,
Santhosh

Hi Santosh,
It could be possible that the number ranges are not defined or altered. Please check the path in SPRO(in SRM) for the number range of backend follow-on-documents.
IMG : Supplier Relationship Management -> SRM server-> Cross Application Basic Settings->Number Ranges-> SRM server number ranges->Define Number ranges for shopping carts and follow on documents.
Please check if number ranges are maintained properly for PO. After maintaining the details, try to push the shopping cart again. Check in RZ20 for the error details further(if it occurs again).
Hope it helps.
Regards
Bash

Shopping Cart Extended View Button...

Hi All,
     i am working an issue which is in shopping cart screen default frame.
   <b>after logon into shopping cart screen, you can see 'EXTENDED DETAILS' button. once you click 'EXTENDED DETAILS' button that will change as 'Simplify button' along with some more fields add into shopping cart screen( say for example custom fields).
   my requirement is when ever user log on and clicked shopping cart create button. the shopping cart screen should display as 'Simplify button' along with all fields ( say for example custom fields) instead of click 'EXTENDED DETAILS' button and see all the custom fields.</b>
give me some suggestion to figure out this issue and is there any OSS notes avaliable.
thanks,
Saran.

Hi
Which SRM Version are you using ?
<u>As soon as you add customer fields (Refer SAP OSS Notes 672960 and 485891) to the Shopping cart (say at Item Level ) these fields are displayed in the the Basic data section (Item level) as well as the Search Criteria (in Extended search) functionality automatically.</u>
As per your business requirement, when ever user log on and clicked shopping cart create button, then the shopping cart screen should display 'EXTENDED DETAILS' view which contains the custom fields instead of 'Simplify details' view.
<b>This is Standard SAP functionality. These changes are not possible until we do modification to the HTML Templates in the Internet Service (BBPSC01) using SE80 Transaction.</b>
I have not tried the same, but i don't think it possible (or might be - not sure), as there is a maximum limit of displaying fields in the Shopping cart Basic Data / Search functionality section.
You must have noticed as soon as the number of fields displayed on the Shopping cart exceeds (say more than 10 fields - including Standard and custom fields), there is automatically a button feature ">>" / "<<" gets enabled to either go forward to the next page or come back from to the previous page for display of fields. <u>Therefore, as per my view, you can change the text lable of the 'EXTENDED DETAILS' button / 'Simplify details' button, but this might not help. Moreover, this might cause side-affects to the existing Shopping cart functionality. So be very sure, before making changes to the respective HTML Templates involved in this case.</u>
Incase this does not help / need more details, please raise a Customer OSS message with SAP to get precise details before making Template changes.
Do let me know. Hope this will help.
Regards
- Atul

Shopping Carts from Classic to Extended Classic

We are contemplating to move from Classic 5.0 to Extended Classic 5.0 scenario, would like to know on the Shopping Carts created in Classic scenario behave when copied into new carts in ECS?
Will all the previously created shopping carts be available in ECS?
Can user copy/edit/approve the previously created shopping carts which are yet to be approved in Classic scenario?
Will Buyer be able to create PO in ECS for the shopping carts which are in approved status in Classic scenario?
Thanks
KB

Dear Kiran,
as the scenario is determined only in the SC transfer, you won't have problem neiter with the approval of the existing SCs, nor with the copy of the old SCs.
The SCs which were created before the change and have already the status transfered (I1111) will stay the classic scenario, the rest will be (after the change) extended.
Kind regards,
Peter

SRM-How to disable Supplier Product Number in shopping cart portal

Dear SAP,
We have "Supplier Product Number" field exist in SRM portal but it is used for catalog PO.
And, we would like to disable the field for free description SC. which means we allow the user to view the field but not editable.
Please advise.
Thank you.
Regards,
William

Hi,
Look at the below blog. it might help you
Web UI modifications in SRM7
thanks,
sankar.

Backend Info Record data transfered to Shopping Cart

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

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.

Import multiple info records for 1 material item in repository

Hi Guys,
I have got sort of a puzzle I can not solve at the moment, maybe some one can help me to solve it. The situation in our system landscape is as follows:
Systems:
SRM 5.0 (Classic implementation scenario)
ECC 6.0
SRM-MDM 2.0
PI 2005
Material master is maintained in R/3 and the materials are replicated to SRM. From SRM we replicate all materials to the catalog repository in SRM-MDM.
As the material master in R/3 is vendor independent, the materials replicated to SRM also have no vendor attached. For the first initial material replication from SRM to the catalog SRM-MDM this also means that the products in the main table of the repository, u2018catalog positionsu2019, will not have a vendor or vendor number attached (i.e. no reference to a source of supply).
To assign a source of supply in the repository to a product (record) we will use info records which are replicated from R/3 to SRM-MDM. The mapping for this in the Import Manager can only be based on the product number. As this is the only unique value available which can map a info record to a already existing (but vendor less) ptoduct item in the catalog.
As long as every item in the repository has only one unique info record, meaning one source of supply with a specific price, there is no issue in the above scenario. Based on the product-id, the info record data will be matched with the material item in the catalog.
The issue for me arises when multiple info records exists for the same material. The info records can heave different vendors and different prices. All possible vendors should be available in the catalog for the same material (at least this is the requirement ).
At this point the product-id will no longer be an unique value. Importing the info records will cause problems, as only one material record is available in the repository for the specific product-id (remember that when doing a initial replication of the material master to the catalog, no vendor data is replicated).
Does anyone had this issue before, and knows a solution? Is it for example possible during the import of the info records in the Import manager, to duplicate material records in the destination data, based on the number of info records available in the source data for the same product-id. Or is there an other solution that I am missing?
Your help would be appreciated!
Regards,
Skander

Hi Shai & Ravi,
Thanks for your answers. The MDM version which we are using is 5.5 - currently on SP6
@ Shai: you are right; the standard SRM-MDM 2.0 catalog repository has a qualified lookup table u2018priceu2019, in which itu2019s possible to store the info record data. The standard fields in this sub-table are: Purchase Org, Amount, Currency Lower B, PIR-ID, price based quantity and Price based quantity UoM.
I added some extra fields (non qualified), to accompany the remaining info record data (product no. u2013 vendor id u2013 product category) which is exported/imported, via the standard extraction program in R/3: Tcode MECCM
I tried the solution Ravi proposed. This scenario works fine when, for example you want to maintain multiple info records for one specific material record in the main table (all info records related to the same source of supply, i.e. vendor). But as I described, the info records we import for one product can have different vendors.
The source of supply (vendor) in the shopping cart of SRM is determined via the u2018supplieru2019 field in the main repository table (which is in itself a flat lookup table ). What happens now is that all related info records are added to the u2018price informationu2019 field of the specific product record in the main table. Thus info records which have different suppliers are attached to a record in the main table which will have one specific supplier in the u2018supplieru2019 field. So from my point of view this will not work.
I am still stuck with the situation that the material master import will only import one record for every distinct product, which can have multiple info records. The info records can/will have different vendors. As the supplier field in the main table determines the source of supply in the shopping cartu2026. Iu2019am seeking for a solution which will duplicate the material records in the main table, based on the amount of imported info records for that specific material record, that have distinct vendors.
Shai, if you have some useful info on how you accomplished this requirement on a previous version of SRM-MDM, it would be greatly appreciated if you can share it..
Thx.
Skander

Sourcing - Sources of supply.

Hello Experts
Could you all please tell what are the different source of supply can be used in classic, extended classic and standalone scenario.
Also let me know, what are the sources of supply can be replicated from the backends and their respective programs.
Thanks in advance.

Hi Santosh,
In SRM source of supply will be assigned in shopping cart level, sourcing cockpit or in PO if a PO created directly without SC (possible only for a professional purchaser role) based on the implementation scenario here is the details information:
Extended classic Scenario:
Source of supply in SC:
1. Source will be copied from catalog if you add shopping carts from catalog
2. Source will be prompted in shopping cart if there is already a contract available for that product category
3. If SC is not soco relevant then after approval PO will be created in held status, where buyer can assign vendor
Sourcing cockpit:
1. Buyer can assign a vendor
2. Buyer can assign a contract
3. Buyer can create a RFx (bid / auction) with reference to SC and later that can be converted into a PO / contract
Sourcing in PO (In case PO is created directly)
Here buyer can assign a vendor
Buyer can enter vendor & contract if contract is available (should be created for same vendor / location & product category combination)
Classic Scenario:
SRM shopping cart:
1. Source will be copied from catalog if you add shopping carts from catalog
2. Source will be prompted in shopping cart if there is already a contract available for that product category
PR / PO in ECC:
1. If a supplier list is maintained then supplier / contract will be picked from the supplier list
2. Buyers can process the PR / PO and assign a source of supply
Standalone / Local scenario:
Same as Extended classic scenario (source of supply assignment)
Replication:
Except the local scenario: Vendor master data can be replicated / update from ECC to SRM using BBPGETVD / BBPUPVD programs
Contracts can be maintained in SRM (contract management) and same can be used as a source of supply in SRM / ECC (SRM 7.0 central contract) or separate contacts for SRM i.e. local contract & ECC i.e. GOA's (In case of SRM 5.0 version)
Also, you can import the contract from ECC to SRM via initial upload program.
Hope above information will provide an overview about the source assignment / replication process.
Regards,
Krish
<div id="isChromeWebToolbarDiv" style="display:none"></div>

Source of supply (info record) in Shopping cart-extended classic

Similar Messages

Maybe you are looking for