Extended classic scenario in SRM 7.1

Hi colleagues,
we want top use SRM 7.1 with extended classic scenario and we want to create POs in SRM and reflect them in ERP backend. The question is it possible somehow to change those POs aftewards (e.q. add confirmations, transportation costs, etc...) in ERP? Or is there any way to trasnfer POs in hold status from SRM to ERP and then change them in ERP?
Thanks and regards, Anton

Hi Anton,
PO is created a in SRM as local and a copy( copy does not contain the entire PO info, only the useful for the backend) is being sent to R3.
DO NOT try to search a workaround for modification in the backend..sooner or later you will be incurring in incosisnten data and misalignmentes.
SRM is the PO golden source.
Thanks and Regards,
Abraham

Similar Messages

PO text transfer to Back-end in case of Extended Classic Scenario in SRM 4.

Dear experts,
My system is in SRM 4.0 in Extended Classic Scenario. We use in the PO internal note text and vendor But thses texts are not transfered to Back-end.
Is it normal?
Do I need to customize something?
Can it be achieved by BADi? How then?
OR is it only possible from SRM 5.0?
Thanks in advance
RD

Yes you can do this. Implement BADI BBP_CREATE_BE_PO_NEW, Refer parameter IS_SC_DOCUMENT>LONGTEXT, and CS_PO_DOCUMENT>IT_PO_ITEM_TEXT. Map the exact text-id of the R/3.
Note: if this BADI is not present, use BBP_CREATE_PO_BACK
Regards, IA

P-card process available for SRM 5.0 extended classic scenario

Hello,
I didn't find the information, so I'm posting this message.
Is the p-card functionality available for the extended classic scenario in SRM 5.0 ?

Hi,
Use of Procurement Cards are supported in Extended calssic scenario from SRM 2007 ..onwards
HTH
Rajesh

PO output for Extended classic Scenario from the R/3 backend

Hi,
1) Does the PO output (ignoring the config maintained in SRM server 5.5 for the output) through R/3 backend is standard or it is mandatory to give local outputs from SRM only incase of Extended classic scenario?
Regards,
DV

Hi Anil,
We are working on extended classic scenario with SRM 5.0 & ECC6.0.
Please explain how we can take "PO output for Extended classic Scenario from the R/3 backend ".
Please send the related document to [email protected]
Thanks in advance
Ashutosh

Status I1113 missing in SC in Extended classic scenario using TA BBP_POC

Hi all,
I am using SRM in extended classic scenario (ECS) (SRM Server 5.5) SP09.
1. Scenario (without any problems)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
No problems at all using standard Sourcing Cockpit -> POs are replicated to R/3, status correctly transfered into Shopping Carts (Status I1113 after creating a PO out of SC).
2. Scenario (problems concerning Status I1113 in SC)
Shopping carts have been succesfully replicated from R/3 with standard report
BBP_EXTREQ_TRANSFER.
transfered to Sourcing Cockpit.
Shopping carts are manually transfered into a local PO by using standard transaction BBP_POC (create PO) -> function "Add shopping cart item" within item data
Local PO is created without any problem, sucessfully replicated to R/3 and if I start the Monitor for shopping carts I get all the detailed information (follow on documents) -> PO number etc.
Problem: If I use TA BBP_POC and add these shopping carts to PO positions, the status I1113 is not written to SC after executing BBP_GET_STATUS_2 and CLEAN_REQREQ_UP .
The SC remains in Status I1106 (Shopping Cart ordered) / I1129 (approved)
I cant find any entries in table BBP_DOCUMENT_TAB and the shopping carts have been removed from SoCo after creating a PO out of it...
Does anybody uses Transaction BBP_POC in ECS and adds Shopping Carts to POs?
Any Idea why the status for these SCs is just I1106 "Shopping Cart ordered" but status I1113 "Follow-on Document Created" is missing/not updated?
Best regards,
Andreas

Hi
<b>Please go through the SAP OSS Notes below -></b>
Note 1053433 Extended classic: Incorrect status shown in check status
Note 730239 Check status: Missing Backend reference
Note 819094 shopping cart monitor:Update status after resubmit shop.cart
Note 825761 Report program for shopp. cart status update after resubmit
Note 768164 Multiple SCs via SoCo are processed incorrectly
Note 729967 Shoppng cart:Status I1111,no follow-on docs->analysis report
Note 728536 Shopping cart: Follow-on docs => analysis-/correction report
Note 704941 EBP 3.0: Status error in SC extractor
Note 486246 Incorrect shopping carts offered for confirmation
<u>Do let me know.</u>
Regards
- Atul

Convert classic in extended classic scenario

hai,
i wanted to convert classis scenario into extended classic scenario.what are all the steps that i needed to be follow.does it require any implementation of badi?how the po will be sent to the r3 in display mode?
could anyone give the solution
Edited by: chakradhar nannapaneni on May 11, 2009 12:45 PM

Hi,
1.     Activate the extended classic scenario
When the extended classic scenario is set, SRM generates a local purchase order for each item in the shopping cart. All follow-on documents are created in the backend system as well as locally in the SRM
2.     Activate IPC pricing
Since SRM 3.5 IPC (Internet Pricing Configurator) pricing is mandatory for extended classic implementations.
In the classic scenario you can replace the IPC by the simplified pricing
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Cross-Application Basic Settings  Activate Extended Classic Scenario
IMG SRM: Sap Implementation Guide  Supplier Relationship Management SRM Server  Business Add-ins for SRM Pricing
Check whether the BAdIs relevant for the pricing are activated correctly and filled with the correct coding:
BAdI                                     I            PC Pricing (Extended)          Simplified Pricing (Classic)
BAdI: BBP_PRICEDATA_READ
Implementation:. BBP_PRODUCT_PRICE                     Not active         Active
*BAdI: PRODUCT_UPDATE2
Implementation. IPC_UPD_PROD_BUFFER2     Active         Not active
Regards,
Abraham

Completion workflow in extended classic scenario

Hi gurus,
We use extended classic scenario with SRM Server 5.5.
In ppoma, each purch org and purch groups has the local and the backend. Vendors are replicated to backend purch org and then also to the local purch org.
I have seen that in classic scenario purchasers should be assigned to the local purch org. however, completion workflow only determine the agent (purchaser) if it is in the backend purch org.
The problem is that then this purchasers cannot manage any business partner.
How can I solve it?
I have seen other clients that the completion workflow determine the agents in the local purch org...
Many thanks!!!
Regards
Patrícia

Hi,
In the Extended classic scenario, local purchasing organisation and purchasing groups are required to create shopping carts and purchase orders. in this scenario, when
the vendors are replicated from the SAP back-end using BBPGETVD,BBPUPDVD program or vendor-synchronization programs, the vendor update in SRM is only for the R/3 purchasing organizations. because the local purchasing organisations are required in SRM for the Extended Classic or standalone scenario, these replicated vendors needs to be extended to the local purchasing organisations.
organizations can use Tx. BBP_UPDATE_PORG for extending the vendors to the local purchasing organiztion.
see OSS Note 390546 for more info.
Regards
vasanth

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

Extended Classic Scenarios Basic Queries

Dear SRM Experts,
I am working in the demo of extended classic scenario in SRM 7.0. I have some basic questions on it, Kindly reply for my doubts :
1. Do SRM-SUS Scenario applicable for all three procurements
     a. Self-Service Procurement
     b. Plan Driven Procurement
     c. Service Procurement.
or applicatbility only for Service Procurement .
2. Is it necessary to implement MM-SUS (Classic Scenario) first before implement of SRM-SUS? (Setting UP IDocs etc)
while i will only use XML Communication in XI(will select the Service_Procurement_Supplier_Enablement configuration scenario)
3. Is the configuration for Distribution Model and Partner Profiles necessary between SRM and SUS Communication in extended classic scenario?
Thanks.
Regards
Pawan

Hi Pawan,
Pl go through the following links for better understanding
difference between MM-SUS and SRM-SUS
SRM 7.0 SUS with ECS
Supplier Self Service (SRM-SUS)
Regards,
Nikhil

SRM: Extended Classic scenario: Request your help.

Hi Guru's,
We are implementing the EXTENDED CLASSIC SCENARIO in our project. kindly request your help.
in our project the SRM box is : G3OSBSR102.
R/3 backend Box is : RCHSBR3142.
Now when i create a shopping cart it should create the Purchase order In SRM( G3OSBSR102) and also copy the created purcahse order in teh backend system : RCHSBR3142.
The issue here is which Logical system should be populated in the field at item level when creating the shopping cart :BE_LOG_SYSTEM.
1) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: G3OSBSR102., then it will consider the Business object type as : BUS2201and creates the local Po but while transfering this local created document(PO) to R/3 system is loosing the Logical system at the item level of the PO.
If i populate this field at the item level via DEBUGG mode then system is sucessfull in transferring the document to R/3.
2) In this field: BE_LOG_SYSTEM.
If i populate the SRM local: RCHSBR3142, then it will consider the Business object type as : BUS2012 and creates the purchase order in R/3 system and will not create teh local purchase order.
Kindly request your help for any further settings if i did miss.Appreciate your help in this regards.
Many Thanks,
Prasad NN.

Dear Prasad,
To work on Extended Classic Scenario, you just have to maintain the following configuration in SPRO:
>SAP Supplier Relationship Management
>SRM Server
>Cross-Application Basic Settings
>Activate Extended Classic Scenario
Check the flag "Extended Classic Scenario Active".
You dont have to manipulate "BE_LOG_SYSTEM" field to choose your scenario.
Regards
Thiago Salvador

SRM Extended Classic Scenario

HI,
Please let me know in the extended classic scenario when the PO is created in SRM does the same PO number gets created in the backend system.Also is the PO created in the Backend system can be opened in transaction ME21N or it can be viewed only in ME22N transaction.
Thanks,
Manu

While configuring consultant has to maintain the same number range in both systems. This way the PO number created in SRM system remains the same as in backend ECC system.
This PO is only readable in backend system. Only ME23.. transactions can be used to view this. If user is allowed to modiify this PO in backend system it will lead to inconsistency between the systems.

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

Attachment transfer of PO from SRM to Back end for extended classic scenario

Hi Experts,
We are using the SRM 7.0 with EHP 701 and ECC 6 , we have a SRM requirement where we need to transfer the attachment of a PO to back end ECC. I tried to implement the note 1594966 , but it doesn't work . we are using Extended classic scenario. Please suggest some SAP notes or the procedure to be followed to achieve this.
Thanks ,
Aishwarya.M

As far as I am aware this functionality of transferring attachment is not supported in Ext classic scneario
http://scn.sap.com/thread/1873708
Also I suggest you should debug and see if its sending attachment from SRM if yes then
could be something missing at ECC side , To debug use this
http://wiki.scn.sap.com/wiki/pages/viewpage.action?pageId=340264144
You may also check in SXI_monitor and see if attachment is being recieved and sent from SRM and ECC respectively
Are you configuring this for the 1 st time or its an error which u encountered?
You must raise a NOte to SAP for the same till a solution is found .
This one is another which you can check ..
http://wiki.scn.sap.com/wiki/display/SRM/Transfering+shopping+cart+attachments+to+the+backend+system

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

Tolerances in SRM extended classic scenario

Hi all,
I have a question regarding tolerances in extended classic scenario and I hope that somebody could help me.
We use extended classic scenario. The tolerance group is attached to TOG attribute in PPOMA_BBP, tolerance key is DQ.
We also tried to use tolerance key CF, but it seems as if CF is not applicable for GR?
However, whenever we try to confirm more than PO quantity, we get an error message. PO Ordered quantity exceeded by 1 EA
It seems so that SRM has a double tolerance check
one in SRM against defined tolerance (via attribute TOG)
one in R/3 against the PO tolerance
Now my question: Is this the expected behaviour or a bug? We do not want to maintain two tolerances. And furthermore most of the time we have POs without a material master. Are there any possibilities to skip the PO tolerance check?
Thanks for your help,
Martina
Edited by: Martina A. on Jan 15, 2008 1:13 PM

Hi
Depending on the SRM version you are using, Please go through the links, which will definitely help ->
Condition Type SRM - ECC
Tolerance in SRM and ECC (BE R/3)
Tolerance
Re: SC Budget check without SAP Fund Mgmt
TOG parameter and tolerance checks better understanding
Setting EKPO-UNTTO with BAPI_PO_Create
Re: SRM: many confirmation for PO
Please maintain the "TOG" attribute in PPOMABBP transaction in SRM.._
Do let me know.
Regards
- Atul

Extended classic scenario in SRM 7.1

Similar Messages

Maybe you are looking for