Prices in PO items in classic scenario

Hi,
When I create a SC in SRM and select a material the price is selected automatically from Master data maintained in SRM for the material.However, when the PO is created in MM as aresu;lt of the SC in SRM, the price gets changed to anothe value.i checked if the info record is maintained in MM for that material then prices are picked fro the Info record.But in cease conditions are not maintained in info records from where the prices are getting picked from in PO in MM.
Also, when we replicate the materials from MM to SRM are the prices replicated automatically or there is some other way for this.Also can I create a filter to replicate only thos items fow rhic pricea rae maintained in Material Master in MM.
Pls advise.
Thanks,
Manu

Hi,
Which SRM version are you working on??
There is a Consulting note 883693 might help - we use it to allow EDI output of our catalog POs in R/3.
The note 883693 in which the steps are explained to use R/3 output when using ECS, however this is only valid for SRM 4.0 (SRM_SERVER 5.0).So it wont be helpful for you if you are on release SRM 5.0.
Another workaround would be to implement the BADI BBP_PO_INBOUND_BADI in ECC.In ECC BAdi BBP_PO_INBOUND_BADI, method BBP_MAP_BEFORE_BAPI ,you and write custom code to generate output for SRM copy PO .
Hope this helps .
BR,
Disha.
Do reward points for useful answers.

Similar Messages

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.

Free Item ticked in R/3 PO - Extended Classic Scenario

Hi All,
We are working in SRM4.0 , Exteneded Classic Scenario, Its a catalgoue item, In SC# its having a Net Value say $3,500, but when i checked PO in the R/3 , it shows the Net price is 0.0 (zero) and Free Item is ticked.
Why the PO shows net value as 0.0 and from where the PO picks the Free item Tick.
Answers will be Rewarded,
Thanks & Regards,
Gopal

Hi
Incase you have implemented BBP_DOC_CHANGE_BADI or BBP_CREATE_PO_BACK BADI, then you can overwrite this flag as per your requirements.
Refer to the following links as well.
Re: How to do Free of Charge Goods
Where is the Free Item field from a Purchase Order stored?
ECS SRM 4 price zero in local PO
Hope this will help.
Please reward suitable points, incase it suits your requirements.
Regards
- Atul

Extended Classic Scenario - Free Items?

Does SAP support PO's in Extended Classic Scenario with a zero price (free items)?
My client is switching from classic to extended classic scenario and they require to be able to creaet PO's that have a zero price like they have in the classic scenario.
We are currently getting an error that we need a price with the IR flag, but I would expect the system to automatically unflag the IR flag for a free item?

Hi Jay,
Thanks for your response. There are two problems with your soluiton. First the shopping cart doesn't have the IR flag on it and can't be changed by the user and we have PO's created directly from SC's and go out to the vendor.
Second, In extended classic scenario it apprears that the system doesn't allow you to change the ir flag on the PO and make the cooresponding change in the ERP PO.

SC with Limit Item using Extended Classic Scenario?

Hello,
Can we implement SC with Limit Item using Extended Classic Scenario.
I mention that we replicate the Product Categories from R/3 backend.
We have tried to create a SC with Limit item, but the data on Quantity, Price and Tax is not picked up at PO level.
Regards,
Shaiek

Hi
Please try out this.
For the time-being,
Try de-activating all the custom BADI Implementations and check, what is happening, in the standard SRM system. How does it behave incase of limit item ?
Incase it works fine, without any Custom Implementation active in the system, I suspect there is something wrong in your current deactivated BADI Implementation.
Since i don't have access to your system , Please paste the code here.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Item in Transfer - classic scenario!!

Hi experts,
I am in SRM server 5.0 using the classic scenario. In a particular case a Shopping cart has been approved but not transferred to the backend system. There were no alerts in RZ20,ST22 & SM21 when checked at that time.
I have also analyzed and found that there is a table entry in the table BBP_DOCUMENT_TAB for the corresponding Shopping Cart and a PO number has been generated.In the details of that entry I find that the object GUID is 00000.
The checkbox is marked as X while the X flag field is blank.
So, under normal circumstance I understand that if entry exist in this table chk whether PO number exits in REF Object no.Then in SE38 run clean REQREQ up and input the logical system name and SC No. and execute. I had run the same but still the status of the Shopping Cart remains Item in Transfer Process.
I even tried to resubmit the SC by using function module BP_PD_SC_RESUBMIT and in the field OBJECTKEY, I put the backend object ID I got from table BBP_PDBEI (PO ID) which should retry to create the backend doc, and then create an entry in BBP_DOCUMENT_TAB, ready for CLEAN_REQREQ_UP.
But even after that the status remained same.
Now atlast I have got an alert in BBP_PD for the SC which states that the
" Shopping Cart ( value of PO ID ) does not exist "
Can anyone guide me as to why this occured and how can I transfer the PO to the backend system ?
Looking forward for your expert Comments and solution..
Thanks in Advance,
Rajesh Rajendran

Hi Marcin,
Sorry for the delay!!! Thanks for the info but i checked up and found that the number range interval has been maintained in the SRM server when i checked through - transaction SPRO -> SRM -> Cross-Application Basic Settings -> Number Ranges - Define Number Rang. per backend System for Follow-on Docs.
But for the backsystem when i went into transaction SPRO->Cross Application Components - > General Application Functions ->Cross Application Document Numbering -> Maintain Number ranges.. when i executed the same I got an error pop up stating " For the object J_1AOFFDOC no sub-object was defined ".
What does this mean ? This should not be the case else all the Classic PO's would not go to backend ..
Can you clarify ?
Thanks & Regards,
Rajesh Rajendran

Limit items on extended classic scenario.

Hi everybody.
We are working in SRM 4.0 with extended classic scenario.
We are testing limit items (not service items), but I can not understand the limit item functionality.
In SC, we can assign contracts form limit items. But when we create PO from the SC, there is not any relationship between PO and contract. Moreover when I create a PO (limit item) from null, I can not assign any contract (field is not available).
In the other hand, in SC (limit item), I can select Follow-Up Actions as Confirmation and Invoice or Invoice. If I select Confirmation and Invoice, when I create a PO, ECC return me a message error, because in ECC, good receives are not allowed for PO with limit item category.
So, I have some questions:
1. Can I use limit items in PO with contract reference?
2. If yes, how can I do it? If not, what is the tab contracts functionality in SC with limit items?
3. What is the functionality to allow confirmations in SC with limit items?
4. Is there any documentation about limit item functionality?
Thanks and regards.
Raúl Moncada.

Hello,
As far as I know, this is a technical limitation. A work around would affect other functionalities.
Note 1358679 corrected such issue.
Regards,
Ricardo

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

PO is not generated for completed SC in SRM.70 classic scenario.

Hi,
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. even we are adding items from catalog.
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 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.
Thanks,
Ravi

learnt that PO number has generated in SRM and the same PO number not exist in ECC.
check SM58 , rz20 log or Application monitor for the shopping cart.
or monitor shopping cart click the icon follow on document and errror message must throw in 1 minutes.
let us see .
1. what is the settings in define backend OBJECTS
2. check all basic data in the shopping cart - especially org data
3. run bbp_check_consistancy report for your id?
4. every user has the same issue?
SEE THE RICHARDO technique
http://wiki.sdn.sap.com/wiki/display/SRM/ShoppingCartStatusI1111-+Resubmit
Muthu
Report BBP_ALERT_SB_NOTTRANSFERED is available to change the status of the shopping cart item from I1111 to 'Error in transmission' (I1112) and later on, it is possible to retransfer this shopping cart from Application Monitor/Monitor Shopping Cart transactions.
1480994 How to process a shopping cart with status I1111
Edited by: Muthuraman Govindasamy on Jul 16, 2010 11:31 PM

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

Use of Purchase info records in SRM SC in Extended Classic scenario

Hi All,
We have implemented SRM 7.13 with Extended classic scenario. If we have Purchase info record in SAP ECC for the material, it gets populated in SRM SC in Source of supply Tab but the price of Purchase info record does not get updated in the SC line item.
Can anyone let me know which configurations is required to fetch the Purchase info record price or we need to have a customization to achieve this.
Thanks,
Ankur

HI Ankur
when you say the price did not get updated did you check the sequence which is used for price determination ?
1. User entry
2. Contracts
3. Info record
If still you think it is an issue please check the report EBP_GET_BACKEND_PRICES and let me know if your problem gets fixed?
Regards
Vinita

Sourcing in extended classic scenario

Hello, all
We are using the extended classic scenario in SRM 5.0.
In sourcing cockpit I have the following problem. In spro Supplier Relationship Management/SRM/Server/Sourcing/Define Sourcing for Product Categories I set Sourcing Always Carried Out. From a shopping cart the purchase order is created automatically as the data complete, but I'd like to sent shopping cart to the sourcing, where from a shopping cart create bid invitation or purchase order. How do it?
Please help,
Best regards,
Guzal

Hi Guzal,
As informed by Claudia, Incomplete mainly means no vendor assignment, no price etc.
If the vendor is assigned at the shopping cart level by means of a contract the shopping cart (details) is complete. Even in this case the SC should go to Sourcing cockpit in case of "Sourcing Always carried out" is chosen in the sourcing column.
In the above case the P.O gets directly created from SC only when the options
" Sourcing never carried out" & " Sourcing carried out for items w/o assigned source of supply" were chosen.
Hope you will be more clear on this issue. Any clarifications always welcome.
Rgds,
Teja

Tolerance key DQ in extended Classic scenario give Backen error message

Dear all,
I am using SRM 7.0, SP 9
Extended Classic Scenario.
I created a tolerance group and attached it to my user via TOG attribute in PPOMA_BBP. Tolerance key is DQ with $1000 and upper percentage 5%.
I also set up the ECC tolerances:
- Purchasing Value key with Tol. Overdelivery = 5.0 (in SPRO --> MM --> Purchasing --> Material Master --> Define Purchasing Value Keys)
And assigned that Purchasing Value Key to the material group I am using (via SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
- And I even set up tolerance key B1 (for error message) for my Company Code (in Spro -> MM --> IM and PI --> GR --> Set tolerance limits) with a upper limit of 5%
And even with this set up I still get the error message
u201CBackend Purchase Order quantity exceeded by 1 EAu201D
when I try to post a Confirmation with an overdelivery, even if the over delivery is only 0.1% of the total quantity 1000.
What Configuration am I missing?
Cheers
Ulrike

Dear Rahul,
Thanks for you input
Let me give you an example of the behaviour:
in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
User orders a PO with quantity=1000, price $100;
No additional tolerances assigned in the PO itself
User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
Cheers
Ulrike

Difference between Classic Scenario and Extended Classic Scenario

Hi Expers,
I need your help again........:-)
I just want to know what is the differne between classic and Extended Classic Scenario.
Points will be rewarded
Thank you
sam

Hi Sam,
(explaination frm a previous thread)
Difference between scenarios
WIth classic scenario, the SC following document is to be created in your R/3 backend(s). Thus you can get an PO, a PR or a stock reservation in R/3.
With extended classic the following document is to be found in SRM itself. Thus from a SC item you can get a complete PO, an incomplete PO or depending on your customizing a Sourcing cockpit (now called Sourcing Application) requirement. Additional FM are called when you tick the box "Enable Extended classic" in the IMG activity, enabling you to get a local PD.
If you need to get a stock reservation in R/3 with extended classic, you will have to switch back to classic scenario for the particular category or product with a dedicated BADI ("Control extended classic ").
Be aware that with extended classic, the PO created in R/3 is not exactly a replication. That is a "copy" with that crucial difference that the SRM PO will use a different Purchase Organization that of R/3. It enables you to centralize your purchasing. In SRM you can create a "local" Purch. Org for EMEA zone for instance while in R/3 that is rare you can purchasing above a country (because in the backend you have to produce legal documents related to one company). Those "local" (=SRM) Purch. Org. are required to enable extended classic and it makes simpler Contract management for instance (in classic scenario contracts may need to be replicated to your R/3 back end and adjusted for each back end and each Purch Org in R/3, and even for each plants).
In a nutshell with extended classic you have a PO in SRM, and this PO is assigned to a different Purch Org that of R/3. Purch Org in R/3 are determined on the basis of the "LOcation" (R/3 plant you have replicated from your backent into SRM).
Extended classic is required for service purchasing when you want your requesters to be able to adjust the PO price while they can not access R3. In extended classic, PO is issued from SRM and not from R3.
Please check this too:
http://help.sap.com/saphelp_srm40/helpdata/en/e9/d0fc3729b5db48e10000009b38f842/content.htm
BR,
Disha.

Extended classic scenario clarification

Hello
I have a question in case of a extended classic scenario.
Shopping cart is created by a employee and approved by a manager. But still no vendor exists in the shopping cart after approval. Now how the PO is created in SRM.
Note sourcing is activated, strategic and operational purchasers exits. How the process is implemented. Will the purchasers get informed via work items? Will they get shopping cart work items or incomplete PO work items.
Could any of you please give clarity on this.
Thanks in advance.

Hi
Once the shopping cart is created, based on sourcing config and also based on Purchase group responsibility the respective shopping cart flows in to the 'sourcing cockpit'(SOCO). Buyers/Purchasers will see all the open shopping carts and in SOCO there are multiple options available for purchasers to do. Such as creation of PO by just adding the vendor and right price/ creation of Bid or Auction or contract/ group the similiar requirements into one requirement create PO etc.
If the follow on document is chosen to be a PO or Contract then the shopping cart will go out of the SOCO once the PO/contract created. If at all the SC is considered for Bid/Auction process then the SC remains in SOCO till the Bid/Acution process is completed. Hope this helps
You can also look at SAP application help for SRM sourcing
http://help.sap.com/saphelp_srm702/helpdata/EN/d8/33ec56f17f4404806072749f7e764f/frameset.htm
Rgds/Kiran

Prices in PO items in classic scenario

Similar Messages

Maybe you are looking for