Extended classic

Hi ppl,
I have two basic question:
What is the need of having extended classic scenario?
From a business perspective,in what scenarios will a company want the PO to be created in the SRM System, and the rest of the documents in the back end?Why cant they simply go for a classic then?
In a external punch-out catalog scenario,what is the configuration done in SRM?What will the vendor be responsible for?Will the vendor have a catalog for every customer separately?
Please share your thoughts.
Thanks
Sam

Hi Sam,
1- ECS vs classic
Scenario chosen by the customer are usually determined during blueprint phase based on customer requirements and constraints. Here are a non exhaustive list of questions :
- user acceptance : SRM user friendly interface or R/3 ?
- functionnality matrix of SRM vs R/3
- user tool : where are purchasing or recipient users going to work : SRM tool or R/3 ? does it depends on purchase category, on... ?
- What is the prefered purchasing channel : SRM or R/3 ?
- if multiple backend are connected to one SRM : do you need a single purchasing channel in SRM, and one connectivity channel for suppliers ?...
Kind regards,
Yann

Similar Messages

POR transferred into MM(Backend) system in Extended Classic Scenario

I am working on standard EBP-SUS Extended Classic Scenario. We have SRM Server 7.0 SP9
As we are successfully send PO from EBP to SUS.
Issue : On working to Purchase Order Response,i am getting POR sent by SUS to EBP but we are not getting it replicated to MM.
Our Concerns about is it need extra configuration required or need to have apply some note to getting replicated POR in MM from EBP or have to configure some XI Scenario to replicate POR from SRM EBP to MM.
As we know that Extended Classic Scenario supports till Purchase Order Response still we are not getting Purchase Order Response in MM.
Please tell us, Provided Solution will be really appreaciated.
Thanks.
Regards,
Pawan Keshwani

hi,
Pls see the foll notes:
Note 576349 - Terms of payment in the ECS
Note 541934 - Modification note: Copying base date from T052
Note 953999 - ECS: Terms of Payment values not in PO header
Note 940453 - Backend payment term data not updated in the extended PO
Note 945018 - Incoterms data not transferred to the back end
BR,
Disha.
Pls reward points for useful answers.

How to close extended classic PO in ECC...

Hi Friends...
We are in SRM 7.02 and ECC 6.05 in Extended Classic Scenario. One PO had been created for 1 Quantity 3 years ago. There was no GR/IR document posted against that PO. Now that PO had been archieved from SRM. But still PO is available in ECC with open quantity and also its appearing in the open PO report. Now requester wanted, the PO to be closed in ECC and shouldnot appear in the open PO list.
How to handle this situation.. How to close the extended classic PO in ECC at this scenario. As PO not available in SRM, we can not do anything from SRM side.
Your inputs are appreciated....
Regards
Sivakumar Kandasamy

Hi Sivakumar,
If you mean how to archive PO in MM side, please refer to the following info:
====
In ECC system, if you want to archive a MM PO, please use transaction
SARA->archive object MM_EKKO.
456129 FAQ: Archiving in purchasing
401318 Archiving: Additional information
====
If you want to delete this ECC PO, please use BAPI_PO_CHANGE and
refer to the following test data:
Parameters:    PURCHASEORDER      = XXXXXXXXX
Parameters:    POITEM
PO_ITEM                        = 00010
DELETE_IND                     = X
Parameters:    POITEMX
PO_ITEM                        = 00010
PO_ITEMX                       = X
DELETE_IND                     = X
You also need to run BAPI_TRANSACTION_COMMIT after BAPI_PO_CHANGE for updating the change.
Regards,
Ivy

Error while creating Manual Service PO in Extended Classic Scenario

Hi Experts,
Extended Classic scenario (SRM 7.0 with ECC 6.0) While Creating Manual Service PO in SRM i am getting the below mentioned error messages. Can any one suggest what could be the problem.
Error Msgs:
1. Backend Error:In case of account assignment, please enter acc. assignment data for item
2. Backend Error:Purchase order still contains faulty items
Regards,
Mohan

Hi,
Yes i given all CC and GL information properly in Purchase Order Document for Service.. Still finding the error for Service PO alone.
Pl do the needful
Regards,
Mohan

Error while changing PO in SRM extended classic Version 5.0

Hi Guys,
we are facing issue while changing PO in SRM , this is extended classic with version 5.0.
The system status is active() is error message and PO remains unchanged. Kindly help to resolve this issue. we have an approval for even PO if a user changes the qty in the PO then it calls the approval WF logic.
Thanks
Srujank

Hello Srujan,
Go through the following thread:
Re: PO status change
Hope it helps.
Thanks,
Neelima

PO error - extended classic scenario

Hi Guys,
I'm using SRM 5.0 with extended classic scenario...
During creation of the purchase order locally (in SRM) I got the "error in process" status.
My means of T-code RZ20 I got the following info to ithis error:
context:B2B Procurement
object name:Purchase Order
short name: Backend application errors
status: Active
Alert text: PO 700..1: Call of a method or kernel Method that has not been implemented
using Transaction BBP_PD I got the following status:
Status: I1080
Description: in transfer to execution system
Do you have any idea what should I do in order to resolve this outstanding issue?
many thanks in advance for your help.
regards,
Piotrek

Hi
Go to transaction - SPAM to get all the required Patch levels and other required system version details.
Meanwhile, try the following SAP OSS Notes as well ->
Note 508972 - Error during transfer of extended purchase orders
Note 881650 - Duplicate transfer/output of the purchase order
PO status in " error In Process ".
Error in Transfer Process (Urgent )
FOLLOW ON DOCUMENT NOT CREATED ( ERROR IN PROCESS)
Hope this will help.
Regards
- Atul

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

No GR on Confirmation Approval in Extended Classic Scenario

Hi all gurus out there,
We are trying to implement confirmation approval workflow in our SRM system. Our SRM version is SRM 3.0 or EBP 4.0 and we are operating in extended classic scenario.
We implement the approval workflow WS10400002 (1-step approval) and WS10400010 (no approval). WS10400002 is used in situation when an administrator does the confirmation and will go to the requestor for approval. Here, when the requestor approves the confirmation, the status is updated correctly to 'Approved' but no goods receipt is triggered by the system. We looked at the workflow and found that there is no task/activity to do the post goods receipt in the backend system.
Can someone please confirm whether these are the correct workflows that I should be using and that it is not a bug? I just want to make sure it is not as a result of a standard limitation before going back to SAP.
Cheers!
Siow Fong

Hi Guys,
I checked with SAP on this and found out that the standard codes would have created the goods receipt. This creation is no longer coded in the workflow itself (like the old workflow used to be). The reason why it was not working for us was a piece of code being added that prevented the creation of the goods receipt.
Regards
Siow Fong

IR_IND indicator in purchase order - Extended Classic

Hi All,
We have a scenario where we purchase free item from vendors. We reset IR_IND in SRM PO then replicate into backend where IR receipt is reset and Free item is set. We have implemented badi BBP_DOC_CHANGE_BADI and BBP_ESC_PO_OUT to do so but POs always in held status and fail to replicate into backend. Our abaper found the changes in BADI has been overwritten by standard code - system will overwrite it with vendor data. Also we found relevant note 1260486 that stated this is truth - our badi changes will not be kept.
For this case, can anyone help/advice how can we purchase free item in extended classic scenario? thank you.
regards,
glen

Hello,
Not sure if I follow exactly the comments about being overwritten from the partner data, but we do this successfully in an implementation of BADI BBP_ECS_PO_OUT_BADI. In particular in our case we set the GR/IR flags based on a couple of criteria like the document type and amount; I don't recall all the technical details of the structure elements in the subsequent BAPI calls to create or change the PO (BAPI_PO_CREATE1 and BAPI_PO_CHANGE) regarding the free goods flag (UMSON) in the ECC PO, but FYI it is mutually exclusive to try and set the IR flag on a free goods item, the BAPI ignores it if IR is set as I remember.
Hope this helps a little
Cheers
MC

Problem in Extended Classic Scenario related to PO

hi,
we are using Extended classic scenario in our client. User has created a SC .when we are going to create a PO system is showing an error Purchase Group B01 does not exist.
This Purchase group is not created in R3 or neither replicated to SRM.and it is not assigned in the Org structure.
Kindly Let me know from where the purchase Group might be Picked apart from the org Structure.
regards
subhash

Hi
Can you check your SC how this Purchase group picked form your basic data ?
since this purchase group is existing in srm thats why it picked while create sc right?
regards
Muthu

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

Freight is not updated in R/3 in the Extended Classic scenario

Friends,
Freight is not updated in R/3 in the Extended Classic scenario.
Once a PO is ordered, if a freight condition in SRM is applied, it does not get updated in R/3.
We have created a condition for Freight (Value and Percentage)in Create
Payment Conditions using the following menu path:
spro
--> Supplier Relationship Management
--> SRM Server
--> Cross-Application Basic Settings
--> Pricing
--> Process Payment Conditions
When creating a Purchase Order in SRM in the "Item Data" tab, there is
a"Pricing" option. Choose "Pricing" and select "Add Further Conditions"
from the drop down menu. Here Freight is available. Add Freight and
the PO record in SRM is updated with the Freight Condition. However,
upon ordering, the Freight condition does not transfer to the PO
recordin R/3.
We've heard this can be achieved by enhancement: only ie by implementing
set of BADIs.. But does anyone know WHICH BADIs we need? Or how we could find out? Thanks.

Hi
 You can either of these BADIs to handlwe the scenario.
BBP_CREATE_BE_PO_NEW Exit while creating a purchase order in the backend system
BBP_CREATE_PO_BACK OLD Exit while creating a PO in the backend system
BBP_ECS_PO_OUT_BADI ECS: PO Transfer to Logistics Backend
BBP_EXTLOCALPO_BADI Control Extended Classic Scenario
Hope this will help.
Please reward suitable points.
Regards
- Atul

Extended Classic Scenario, BADI for PO creation in R/3

Hi,
We are using the extended classic scenario. When the PO gets replicated from SRM to R/3, right now the field CATALOGID is not being transmitted to the backend R/3 system.
1) What BADI should I implement (and the method) to transmit the CATALOGID to R/3?
2) After implementing the BADI, do I also have to change the BAPI?
3) Is the BAPI used to transfer data from SRM to R/3, BAPI_PO_CREATE?
Thanks and Regards,
Peter

Hi Peter,
1-You can use BBP_ECS_PO_OUT_BADI for ECS scenario.
Since the R3 PO does not have field for catalog id, the EKKO- BEDNR (Tracking Number) field can been used for example to store this information. In this BADI all the items are identified and their tracking number field is populated with a catalogue id value.
2-If you use the tracking number field, no use of R/3 BADI is required.
3-BAPI_PO_CREATE1
Please check my answers in this post :
catalogid field not going in R3 backend
Kind regards
Yann
Message was edited by: Yann Bouillut
Message was edited by: Yann Bouillut

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.

Extended Classic- GOA to backend-SOS

Hi All,
We are working in extended classic scenario. SRM 5.0 with backend as ECC6.0. We want to distribute GOA as a contract to backend. Also, we want to use backend contract as a source of supply in shopping cart and then in PO. How can it be done? Is that possible to distibute GOA as a local contract in SRM and in backend too? I know in the standard system it can only be distributed to backend but is there any way of doing it? It is quite urgent. Every useful reply will be rewarded with full points.
Regards
Kapil

Hi Kapil,
Just a thought, you can upload the same contract from back end to SRM using a report BBP_CONTRACT_INITIAL_UPLOAD and can be used for procurement in SRM.
Rgds,
Teja

Anybody ever created multple PO doc type/number ranges in extended classic?

I have searched this forum, and found plenty of useful threads which would help me determine different document types/number ranges for back-end purchase orders in a classic scenario. (And I have done something similar many years ago on a classic EBP 3.0 implementation)
However, I have a customer who has an SRM 5 extended classic implementation, and who (Based on certain simple criteria) requires a different PO number range to identify certain types of indirect orders. (They also have direct materials procured using doc type ECDP, but that's not relevant to this requirement)
This would obviously have to apply to the local PO in SRM, as well as the backend ECC PO.
It would also need to be derived for orders created automatically via approved shopping carts, as well as those orders that are created via sourcing.
I've copied ECPO via define transaction types IMG step, as well as assigned a new number range.
Just to test, I've also added the second doc type in the BSA attribute for a particular test user - just initially see if it was possible to manually choose when creating a PO in sourcing. However, I could only get ECDP and ECPO.
I have looked at various BADIs to see if I can determine doc type or number range somewhere in the PO creation, but as far as I can see, they either:
- Seem to apply only to the object type (PO, requisition, reservation etc) rather than the transaction type within that object.
- Or look like they are too late in the process to influence the doc type and number range (BBP_DOC_CHANGE_BADI?) ... which doesn't seem to have those doc type or PO number fields available anyway
- Or I doesn't seem to be trigerred at all when turning requirement into Po and ordering via sourcing. (tried break-point & endless loop in implemnetation of BBP_CREATE_BE_PO_NEW, but nothing happened. In any case the PO number was alreadya ssigned)
If anybody has ever managed this before, or can tell me that I am definitely barking up the wrong tree, it would be gratefully appreciated. The document type is actually lesss important than the different number range... and was really just an attempt to trigger a different number. I'm starting to think that this sort of thing may only be possible in a classic implemntation.
What I need ideally, would have been some kind of 'local PO' equivelent of the BADI that enables you to determine transaction type for a bid.
Regards,
Vince
Edited by: Vincent White on Dec 6, 2010 5:13 PM

Hi. Not sure on this, but I can tell you that with extended classic it is BADI BBP_ECS_PO_OUT_BADI that is called for the backend PO instead of the CREATEPO_BACK BADI.
You can have a look in BBP_ECS_PO_OUT_BADI and see if that helps?
Don't think it will influence the PO in SRM at all though.
Have you tried the number range / grouping BADIs? They definitly work for changing the number range for classic POs.
Regards,
Dave.

Extended classic

Similar Messages

Maybe you are looking for