Inforecord price for SRM originated orders - CLASSIC scenario

Hi! Few months' back, I have posted some questions re the behaviour of the price on the PO when orders are generated out of SRM in a classic scenarioI have just completed testing and ended up with the following results:
1. If I create a shopping cart with material number for direct consumption and have a vendor defaulted from vendor list, the price reflected in the PO is from the inforecord. So, effectively, I could have $1000 on my shopping cart but PO showing $950 as this is the value in the inforecord. The $1000 comes from the material condition record in SRM (extracted via EBP_GET_BACKEND_PRICES).
2. If I create a shopping cart with material number for STOCK and have a vendor defaulted from vendor list, the price reflected in the PO is that maintained on the shopping cart. Is this behaviour correct? Note that in this case, the master PO is in SRM even in a classic scenario and I wonder whether it is because of this that the pricing behaviour is different.
Other observation: For stock purchase, I know that if I have multiple vendors (from vendor list and some from inforecords) and if I picked one of the vendors, the price will be adopted at the point of shopping cart so that the user has a 'confirmed' view of the price and there should be no discrepancies of prices between the shopping cart and the PO.
Can someone please shed some lights as to what should the standard behaviour be?
Cheers!
SF

hello SF
rule :- shopping cart price is a material price and it comes from your report and prices are stored in COMMPR01 .( EBP_GET_BACKEND_PRICES BY this report).
really the prices are picked from source of suooly like infor record , vendor list or contract while creating the purchase order.
i create a shopping cart for 100 USD since material price is 100 usd but PO created for 75 USD.
since contract material price is 75 usd.
With regards to using report EBP_GET_BACKEND_PRICES to upload the
prices from the backend system into EBP. Please refer to the online
documentation of this report:
'Under "Price reference per product", you can specify if the average
value of all valuation groups/plants is to be calculated or if the
valuation price from the first valuation group/plant is to be used. If
the average value is to be calculated, choose "Average of all prices".
If you wish to use the first valuation price, choose "Use first price".
The standard setting calls for the "Average of all prices" to be
calculated.'
This is how this report works. If you want to take another price you
have to change the coding according your requirements.
You will need to debug into the backend through
RFC-Call for backend-table MBEW
CALL FUNCTION 'RFC_READ_TABLE' DESTINATION iv_rfcdest
in FORM read_mbew and see the select statement that reads this table.
The report is taking exactly one price out of the data
package extracted out of R/3. If this could also be a moving average
price is more a question which kind of data is extracted out of of R/3
and how the R/3 config looks like - and if this moving average is in thelist.

Similar Messages

SRM 7.0: Classic Scenario no PO is created only PR is generated

Hi Gurus,
I am working on SRM 7.0 - Classic scenario.
When a shopping cart is complete in terms of price, vendor (assigned) and other required data, item stays in transfer process.
If a SC is incomplete a PR document is created in backend without a problem but when a complete SC is oredered, the status of shopping cart remains I1111 i.e. item in transfer process. I can see in table BBP_PDBEI, backend object type (BE_OBJECT_TYPE) is correctly selected as BUS2012 and the document number of PO is also correctly selected.
This is the case even for the SC ordered using catalog materials.
I have checked following configuration and it seems to be ok.
1. 'Define objects in backend system's
2. Number ranges definition in SRM and ECC
3. Document type attribute -BSA in PPOMA_BBP
Configuraiton wise everything seems to be, I tried to manually transfer the SC using FM BBP_REQREQ_TRANSFER but it does not change the status of SC it remains I1111
RZ20 does not show any error for the SC with status I1111.
Is there any sepcial FM to push the SC in SRM 7.0?
Any help/tips would be highly appreciated. Thanks in advance.
Best Regards,
Amit

Hi Amit
what is the setting here
1. 'Define objects in backend system's
is it a prefered vendor or fixed vendor
update the partner function in bbp_pd here
if it is 39 - you wil recive pr
it is 19 you will get PO
i am afraid , you stated that catalog sc stoo this problem but during debugging check what is the partne rfunction...
there can be several reasons for creating PR instead of PO. Please see the FAQ note 1173815 for the possible reasons, and the guide for debugging under:
https://wiki.sdn.sap.com/wiki/display/SRM/Howtoanalyzethefollow-ondocumentdetermination
MOREOVER NOTE SAYS POSSIBLE REASONS ..
Note 336658 - Purch req instead of purch order created in backend
BR
Muthu

SRM 7 PPS Classic Scenario with Plan Driven Procurement?

Hello experts, I want to know if the combination of SRM 7 PPS Classic Scenario with Plan Driven Procurement is possible? or if there any limitation to consider? Our client needs to create purchase requisition in ERP -> send this purchase requisitions to SRM (as shopping carts) create bids - > quotations - > create contract from accepted quotations and then from the contract we need to create purchase order but this one must be created in ERP (classic scenario) Someone has experimented the same situation? Best regards and thanks for your Help.
Liam

Hi Lima ,
Classic scenario wont support PPS .
        - Stand alone and classic scenario not supported
        - Shopping cart renamed to Purchase Requisition
        - Shopping cart generate (pre)commitment in funds management
        - Contract can create Funds Reservation (Earmarked Funds) in Funds Management as a Guarantee
        - Goods Receipt and Invoice created in ERP
        - Mixed PO: PO with lines that works like contract lines, a PO can be created from these lines
        - PO created from contracts or mixed-PO is named call-off PO. Only is a new name, is a "normal" SRM      PO
        - Goods receipt possible in SRM only in "easy" cases
Thanks & Regards
Pradeep Kumar Dondeti

SRM -MDM in classic scenario

Hi,
Please let me know if am using SRM MDM in classic scenario then
u2022If I create a shopping cart in SRM do I need to maintain the product category of the items selected from MDM in SRM as well.
u2022Also, if PO is created in MM then does it mean that all the products in MDM have to be created in MM as well. If not then what is the scenario like.
Thanks,
Manu
Edited by: Manu Agrawal on Apr 24, 2009 12:15 PM

Hi
If my understanding is correct ,i will reproduce your question again . If you create shopping cart from the supplier catalogue in a classic scenario how the Material group sync happens when PO is created in the Back end R/3.
My assumption and the practice followed generally is that a Fixed Material group is decided and automatically maintained via OCI interface when shopping cart is created .Which means we define the rule for all catalogue items to determine and populate respective material group automatically into shopping cart.
As shopping cart is created since for the catalogue items there will be contract and source assigned in the ERP ,as soon as PR is replicated to R/3 as per classic scenario , the PR will have supplier assignment and if you run auto order transaction code system will generate PO in R/3 and sent to the supplier based on the condition records.
For the Material group you will configure it in R/3 for all catalogue items and replicate it in SRM and also you will provide input for the BADI or FM which create shopping cart automatically from catalogue through OCI method.
Hope this helps..
regards
Narahari

Contract Creation in SRM 7.0 classic scenario

Hi All,
We are using SRM 7.0 Classic scenario with ECC 6.0 EHP 4 and CLM 2. We are creating contracts in SAP CLM and pushing into as Global outline agreement.
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
What are the mandatory fields required to transfer the CLM contracts contracts to ECC outline agreement - I know ,Vendor, Purchase org, Pur grp, company code are required - is product catagory is also a mandatory field.
Rgds/Pawan

Hi Pawan,
Please find the answered for your questions:
Question is -
1) Can we create contracts in SRM 7.0 Classic scenario ?
Mitesh: Yes we can very well create in Classic Scenario as well in SRM 7.0.SC can be pushed to SOCO based on the Prod Category configuration in SPRO.From SOCO PO, Contract and RFX can be created for SC.
2) Instead of transfering the ECC outline agreement to SRM , can we directly use ECC outline agreement as a source of supply in SRM while creating a SC.
Mitesh: I dont think we can use ECC outline agreement as source of supply in SRM while creating SC.Contract replication in SRM 7.0 with EHP 4 ECC is eSOA based and ONLY Outbound to SRM (inbound to ECC).Contract cannot be replicated from ECC to SRM.
3) How we can transfer the SAP CLM 2.0 contracts into SRM 7.0 and use a source of supply there while creating a SC ( Considereing that these CLM contratcs are also transfered to ECC as a outline agreement)
+Mitesh: Standard intergeration of CLM/ESO to SRM 7.0 is very much there in roadmap for future releases of SRM/ESO.+
+As of now there is a consulting solution available to integerate ECC and ESO/CLM.+
+This logic can be leveraged to integrate ESO/CLM to SMR 7.0 (or lower version) requiring Developement effort from SRM functional,SRM technical,PI, Basis,ESO and java consultants.+
+Such contracts can be forced to be used as Source of Supply or alternatively replicated to ECC Via standard repliation scenario.+
Hope this helps.
Regards,
Mitesh

Questions about SRM PO in Classic scenario

Hello All
I have a number of questions about the SRM PO in classic scenario.
1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
for the same?
We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
Our requirement is not have an approval initially once the PO is created, but only for the changes
2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
for this to happen. Should SAP XI be required for this?
3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit?
We are using SRM 7.0
Regards
Kedar

Hi,
1) If the Backend PO is changed in ECC i.e. if any quantity is added , can we have an approval workflow
for the same?
We currently have release strategies for other PO's in ECC. How do we accommodate the PO changes only?
Our requirement is not have an approval initially once the PO is created, but only for the changes
Sol: In ECC6.0 if the P.O is changed and release strategy is there in ECC6.0 then it follows the ECC6.0 Approval Route.
2) If the PO is sent as XML to the Vendor, is it possible to capture the PO response in ECC? What are the Pre-requisites
for this to happen. Should SAP XI be required for this?
XI is mandatory
3) In case the PO is cancelled/ reduced , does the Balance goes back to SRM sourcing cockpit.
Once P.O is created in ECC 6.0 for the P.R in Sourcing Cockpit, cancelling/reduction will not have a updation in the sourcing cockpit in SRM.
Eg 100 nos P.R is in SRM sourcing cockpit for which you have createdaa P.O for 40 nos is ECC6.0
for the remaining 60 nos PR ,you can create a P.O in ECC6.0
Regards
Ganesh

Does SRM 7 Extended Classic Scenario support PCards?

Does SRM 7 Extended Classic Scenario support PCards as standard? I know SRM 4 does not but wanted to know if that has changed.

Paul,
URL https://websmp208.sap-ag.de/support ( service.sap.com) ...on header
Go to 'Release& Upgrade Info' ..then sub item 'Release notes'....look for SAP Solutions on left scroll...then select SRM...
Open pdf file ' Release Notes SAP SRM 2007, SP00 - SP04 '...and look for pg # 40...
Let me know if you did not get it..
Thanks,
Rahul Mandale

Procurement Card in SRM 5.0 Classic Scenario

Dear Gurus,
We want to configure Procurement Card in SRM 5.0 Classic Scenario. Please help me with the following doubts:
1. Is it possible to configure P-card in Classic scenario?
2. If yes, then what are the steps involved to get P-card as payment option in SC and P-card settlement? (backend is ECC6.0)
3. Are there any enhancements/customizations required to get P-card in Classic scenario?
Will be grateful for a speedy answer.
Regards
Rajeev

Dear Gurus,
I am aware that Procurement card can be configued in SRM 5.0 Extended Classic Scenario. Can anyone tell me if it can also be done in Classic scenario?
Regards
Rajeev

Is B/E ECC SoS in Local SRM PO in Classic Scenario Possible ( SRM7.0) ?

Hi Experts,
We are configuring SRM7.0 with ECC6 ( Ehp4) having Classic Scenario .
Our Ultimate Aim is - To maintain SoS in ONE system only (i.e. ECC) & use the same SoS in both ECC & SRM system, for all documents ( ECC PR, ECC PO, RM S/C, Local SRM POu2026etc )
In Classic Scenario, B/E ECC SoS ( Supplier Contract & Pur. Info Record) are proposing in S/C ( Indirect Mat.) , but these B/E SoS NOT proposing while creating u201CLocal SRM POu201D which is by default Ext. Classic.
We are exploring new CCTR functionality ....but seems complicated and requiered PI...
1.By doing any enhancement , can we pull B/E ECC Contract and Pur. Info Record as a SoS while creating u201CLocal SRM POu201D ?, If it is possible , then we are ready to do any enhnacement and I'll be most happy
2. Which BADi is used while creating Local SRM PO ?
Can anyone suggest/confirm please.
Thanks
NAP

Hello,
In classic scenario, only backend contracts can be used as SOS.
In extended classic, local contracts can be adopted as SOS.
If you are using classic scenario, you should distribute local contracts to ECC. Then, while creating a shopping cart in classic scenario, ECC contracts (which have been distributed) will be considered as SOS.
Regards,
Ricardo

SRM 7.02 Classic Scenario - Transfer of Purchase Order to Backend

Good day,
I would really appreciate some assistance on the following matter:
We are implementing the classic scenario of SRM7.02 with ECC6.04 as backend.
Our process is as follows: Purchase
Requisitions are created in ECC and transferred to SRM by means of report BBP_EXTREQ_TRANSFER (we do not have PI/XI). These Purchase Requisitions are
converted to shopping carts in SRM and goes to the Sourcing Cockpit. RFX's are created and responses are entered on behalf of vendors. When I now want to
create a purchase order from the RFX response, I get a warning “PO xxxx is inthe process of transfer to backend system”.
When executing transaction SM21, I get a warning “XI unable to access SLD:"Could_not_determine_SLD_access_data". We do not have PI/XI and I would really
appreciate if somebody can assist me with the exact entries that must be maintained in table BBP_FUNCTION_MAP to transfer purchase orders from SRM to ECC.
I changed entries BUS2012 / CreateFromData1 /ERP_4.0/ERP_5.0 and ERP_6.0 from /SAPSRM/CL_SOA_ADPT_PO_CRT_ERP to L_BBP_BS_ADAPTER_PO_CRT_ERP10 and the PO replicated from SRM to ECC, but now in ECC, the purchase ordercannot be changed. It gives an error : Purchase Requisition xxxx can only be
ordered in system SRDxxxx (which is the SRM system).
Can somebody also please confirm that once Ihave replicated the Purchase order from SRM to ECC, the Purchase Order can be changed in ECC.
Thank you in advance,
Marinda

I managed to resolve this by changing the system landscape from ERP6.0 to ERP 6.02

R/3 Backend PO in SRM for Confirmation in Ext. classic scenario

Hi,
We are on SRM 4.0, Extended classic scenario
User created STO(Stock transport order) in backedn R/3(Not in SRM) and is visible in "Confirmation /GR services" in SRM.
But when user tries to do confirm it the items are not available and confirmation is not possible in SRM.
Is there anything missing in the system ? Please suggest
Best regards,
Sambit

it should be updated by running standard progarams which updated the status of the corresponding documents in R/3

Output(print out) in SRM for backend PO in Classic scenario

Hello,
My requirement is to take print out for the backend PO created thru shopping cart in classic scenario.
i know for extended classic scenario Actions works as in that case PO is created locally and then replicated.
But in the classic Scenario where the PO is in backend, can we take print out in SRM becasue the detials of that Po is available in SRM to in Fllow up documents in SRM 5.0.
is there any standard way available to achieve that.
Thanks
Robin

Hi Sarabjeet,
It does not make sense to print PO from SRM in classic scenario because there is no PO in SRM at all !
In classic scenario, PO is created only in the backend.
Only shopping cart is created in SRM.
Kind regards,
Yann

PI setting for transferring Contract from SRM to ECC - Classic scenario

Dear Experts
SRM 702
ECC 6.0 EHP6
SRM - Classic scenario
Need to understand PI setting for transferring Contract from SRM to ECC, as currently document Central Contract document getting created in SRM, but it is not getting transfer to ECC
No XML message getting triggered in ECC systm as well
can you help me in this
if any additional information needed, pls revert
Regards
Prashant K

Fully approve and release the contract. It will trigger the XML Message.
Go to https://websmp203.sap-ag.de/~form/handler?_APP=00200682500000002672&_EVENT=DISPLAY&_SCENARIO=01100035870000000122&_HIER_… and download the configuration guide & check the PI setting and required Software Components in PI.

SRM-SUS for Service Entry Sheets - Classic Scenario

Hi SRM Gurus,
Our client wants to use SRM-SUS for the Service Entry Sheets (to being with and then later expand more in other SRM areas). The lead system will be R/3 system.
We will be going with ECC 6.0 and SRM 5.0.
Service Order will be created in R/3 and replicated into SRM (SAP have said this is new functionality in SRM 2007 and SAP will provide us with this functionality in SRM 5.0 as well)
SAP are also recommending using MDM for hosting the catalogs for service entry sheets to enable vendors to selete their items during the confirmation / filling the service entry sheets. - they say this is mandatory
SAP are also asking for XI for the data to be transferred from R/3 to SRM (and may be vice versa) - they say this is mandatory.
Few questions:
1) What kind of hardware size are we talking about to have SRM-SUS, MDM, XI and Portal (PI)
2) Are MDM and XI mandatory as said by SAP and if yes, in what scenarios. What is they way around
3) How good is the functionality provided by SRM-SUS for Services? Is it as good as in R/3 (or even better)? We will be having complex Services in our scnearios.
4) What can be a typical time to install SRM-SUS, MDM, XI and Portal in the Dev environment to get moving onto the project?
An early response shall be highly appreciated.
Thanks in advance
Regards
Rahul

few answers to your questions
1) what is the release of SRM you want to work with?
2) services in SUS is not available as standard , and will be provided by SAP as consulting up on request.
3) for hardware requirements , please refer to the master guide for the srm release you will be working on -->
and also you can refer to the software component matrix in master guide --> to see if any component is mandatory..
4) XI and MDM as far as i know is mandatory for SRM 6.0 and above , But in SRM 5.0 , XI is compulsory.
5) so xi is mandatory in anyway in SUS as different systems are involved and therefore is required for routing the documents correctly.
6) time for installation again depends on your supplier base , and your level of expertise.
7) it is not always recommended to compare between two different systems , R/3 and SUS are different and so functionality will not be the same
8) but as far as i know R/3 is stronger functioanlly..

Info Record Not Appearing for all materials in classic scenario.

HI ALL,
 I am working on Classic Scenario and all the follow-on documents are getting created properly. But the problem is With SOS. Currently i am able to view the info record for only one of my material, I am also referring backend contracts through vendor list. The contracts are visible in SOS.
 Can somebody pls put a light as to why for other materials the info records is not displayed in SOS, is there a report which has to be run to get the info record into SRM from ECC. If not then how does the system bring these contracts and info record from ECC to SRM.
 I am working on SRM 5.0 and ECC 5.0.
THANKS AND REGARDS
Debu

Hi
Please read this as well.
You have created sources of supply. These could be:
-> Contract items in Enterprise Buyer
-> Vendor-specific prices
For this, you have created Product Linkages in the SRM System with vendor-specific prices via the SAP Menu Master Data -> Products -> Process Products.
-> Entries in the vendor list of Enterprise Buyer
In Customizing you have assigned product categories to which the system is to automatically group requirements and you have scheduled report BP_SC_TRANSFER_GROUPED to run periodically.
For more information, see the Supplier Relationship Management Implementation Guide (IMG): SRM Server -> Sourcing -> Define Interactive Sourcing for Product Categories.
Sourcing is completely integrated with the global availability check in SAP APO and executes a vendor search. You can activate third-party order processing in the check instructions by choosing how you want the system to start sourcing and which sourcing method you want to use for it. There are two different options here:
○ If you want the products to be delivered exclusively by external vendors, the system performs sourcing directly at the external vendors without evaluating internal locations. For this, SAP APO requires corresponding purchasing records, delivery plans and contracts that are transferred from SAP ECC.
○ If you only want to have products delivered by external vendors occasionally, that is to say, if you are unable to deliver the product from your own warehouse stock, choose an ATP profile in which both internal and external vendors are evaluated. In this case, the external vendor is treated like an internal location in SAP APO, and is integrated into location determination in the rule-based availability check.
You can also choose the vendor manually. If you have already specified a vendor as the source of supply in SAP CRM, SAP SCM does not carry out any further sourcing. In this case, SAP SCM merely checks the validity of this vendor and confirms the requirement in its full amount if the vendor is valid.
For more information, see SAP Library for SAP SCM at SAP Advanced Planning and Optimization (SAP APO) -> Global Available-to-Promise (Global ATP) -> Advanced Availability Check Methods -> Third-Party Order Processing in the Global ATP -> Sourcing in Third-Party Order Processing.
Refer these links for more details ->
Assignment of Existing Sources of Supply
http://help.sap.com/saphelp_srm50/helpdata/en/25/40f23a53cd0e04e10000000a11402f/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/55/4af548688211d4977e0004ac962ee6/frameset.htm
http://help.sap.com/saphelp_crm50/helpdata/en/fa/84944279c0c66ae10000000a155106/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/18/db183d30805c59e10000000a114084/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/63/36f2323326da4da25d9d0a06f550a0/frameset.htm
Processing Contracts
http://help.sap.com/saphelp_srm50/helpdata/en/43/0f234a9e242a8be10000000a1553f6/frameset.htm
http://help.sap.com/saphelp_srm50/helpdata/en/5a/4cc5376848616ae10000009b38f889/frameset.htm
See alsoSAP Note 519794 EBP: Replication of Materials exclusively for Purchasing
SAP Note 505030 (Restrictions for the integration of external requirements).
Regards
- Atul

Inforecord price for SRM originated orders - CLASSIC scenario

Similar Messages

Maybe you are looking for