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

Similar Messages

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

SRM with PPS = Extended Classic Scenario

Does SRM Procurement for Public Sector (PPS) require Extended Classic Scenario? If so, could some one refer me to an official documentation that states such? Thanks.

http://wiki.sdn.sap.com/wiki/display/SRM/PPS-ProcurementforPublicSector-+enhancements
PPS is only possible by ECS only.
Muthu

Sharing attachment documents (e.g. for P.O.) in extended classic scenario

Dear SAP SRM gurus
in the SAP SRM extended classic scenarios (rel. 7.0) attachments of Purchase Order can be viewed also in the backend SAP ECC 6.0 as per SAP Notes n. 1582690 and 1057932 . But I am not sure if attachments are phiysically transmitted from SAP SRM to ECC or only document url is passed even though, as per SAP note n.1357551 it seems that only url is passed.
My customer wants to know if there is the possibility of not replicating them.
Any suggestions will be appreciated.
Many thanks in advance
Best regards
Gianluigi Brenna
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 2:56 PM
Edited by: GIANLUIGI BRENNA on Jul 29, 2011 3:08 PM

Hello,
In extended classic scenario the attachments arent transferred to ECC as the source document is in SRM. The document in ECC is only a copy and it cant be modified also.
If we have to transfer attachments, then probably implicit enhancements to standard logic might be needed.
Regards,
Prasanna

POR (BUS2209) in SRM 5.0 (Extended Classic scenario)

Hi Experts,
I configured the BUS2209 transaction type (Purchase Order Response) and it is working fine in SRM 5.0 -> i am able to create POR for a PO. But when i check the PO in ECC, the "Delivery Date" field updated with the confirmed date from POR in SRM.
In this flow I would like to have an "AB - Order Acknowledgmenet" in ECC PO at "Confirmations" tab and I don't want the system to update the original "Delivery Date" in ECC PO.
Is there any standard solution for my problem or I should consider a development here?
Thanks in advance for your help!
Best Regards,
Attila

Hi Manjunath,
The functionality of POR is fine in SRM. Our requirement is when a POR is generated in SRM and the information is sent to ECC (to update the PO) we do not want the system to update the "Delivery Date" field in the ECC PO automaticaly. In this case we would like the system to create one line in the "Confirmations" tab in ECC PO, because in this case we can monitor the delay between the expected delivery date and the confirmed delivery date (we have some reports in ECC which should consider the data from ECC -> when the confirmation is done directly in ECC that's fine...but now we have to figure out this "problem")
Thanks for your help!
Regards,
Attila

PO approval process in ECC for extended classic scenario

Hi All,
At this moment we are using SAP ECC for procure to pay process. In the existing system set up, our ECC purchase order goes for approval via SAP enterprise portal(EP). We are planing to implement SRM 7.0 Extended classic scenario, so that user can take the advantage of creating PO in their web portal. We don't want to disturb our existing ECC PO approval process at this point of time.
So our requirement is :
User will create PO in SRM. Same PO will replicated in ECC and the PO will goes for approval in in ECC and the PO output will generate in ECC. Can it me possible in extended classic scenario ?
Thanks in advance.
Regards,
Jennifer
Edited by: Jennifer Batty on Aug 8, 2011 5:08 PM

Hi Jennifer,
Since SRM PO will be leading PO in extended classic scenario, why donot you design the process controlled workflow in line with the existing release strategy that you are using for ECC PO?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Service base IV flag need to be set for SRM PO u2013 SRM 7.0 Extended classic

Hello
We are on SRM 7.0 Extended classic scenario - business have following requirement with Service PO
Invoice need to be posted with reference to conformation (SES) u2013 While creating a service PO when user maintain GR required flag , u201CConfirmation-Based Invoice Verificationu201D flag get automatically set but when PO replicated in ECC, it has only GR base IV flag ticked and not the Service base IV which is required from Invoicing perspective
On SRM PO unlike ECC PO there is only provision to maintained GR base IV and not SR base IV. So how can we achieve this
Can we do it via BBP_DOC_CHANGE_BADI.
Note : SR base IV flag cannot be maintained in Vendor master in ECC because of business constrain so it has to be pass from SRM PO only

Hello,
Make some tests using R/3 BAdI BBP_PO_INBOUND_BADI.
Nevertheless, only BBP_MAP_BEFORE_BAPI method has field SRV_BASED_IV in changing parameter BAPI_POITEM.
Regards.
Laurent.

Extended Classic Scenario Pricing issue, can I over come by using SRM-MDM?.

Hi SRM GURU'S,
I am using ECC 6.0, SRM 5.5, SUS, LAC, cFolders and SRM-MDM with Extended Classic Scenario.
My Question is : In case of Extended classic scenario, there is issue with Pricing and conditions. Is there any possibility to overcome this issue by using SRM-MDM. Or do I have to go for IPC. My client has not brought IPC. I have to cover Pricing with the above components.
Anyone suggest me, how to proceed. Thanks in Advance. Awaiting for quick response.
Thanks & Regards,
John.

Hi Masa,
We can maintain Price and conditions as a record in CCM for Particular Material or Vendor. When you add that record to shopping cart it will update. I mean, If the provision is available in MDM, I don't want to use the Two components for same functionality.
If I use IPC, Is there separate license for that. What else need to be updated to use IPC (Patches etc).
If you have IPC configuration material, could you please share with me? How to bridge the SRM Conditions and ECC Conditions?
Please clearly give me details. I really appreciate you.
Regards,
John.

SRM 7 : Vendor record replication in backend with Extended Classic Scenario

Hello,
We are implementing SRM 7 with Extended Classic Scenario and Supplier Self-registration.
Can you explain what is to be configured to get the new vendors replicated to the backend?
Thanks in advance.

Hi,
It is possible to transfer suppliers to ERP system, if you use 'Supplier registration with ERP' scenario. After registration and acceptance, newly registered suppliers would appear on supplier monitor from where you can transfer them to backend system.
Check the below link for more details:
http://help.sap.com/saphelp_srm50/helpdata/en/cf/35074152aff323e10000000a155106/frameset.htm
Regards,
Sanjeev

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

SRM 7.0 extended classic possible for multiple backends?

Hi all,
I know that SRM 7.0 can be set up for multiple backends in the classic scenario.
And i assume it is also possible to do so in the EXTENDED classic scenario.
Could somebody please confrim that this is possible?
Has somesone already set up this landscape and any recommendations, advice, hits, do's and dont's?
Cheers
Ulrike

Hi Ulrike,
SRM 7.0 supports ECS for multiple backends. We are using it now.

Procurement Card in SRM 7.0 Extended Classic with PPS

Could sometime tell me if we can implement Procurement Card functionality when you have SAP SRM 7.0 Extended Classic with PPS enabled. Appreciate any help in this regard. Thanks, Alisetty

Gurus:
Anyone have any idea about using Procurement Card when you have SRM7.0 Extended Classic with PPS.
I didn't find any lead on this and appreciate your inputs.
Regards,
Vijay Alisetty

SRM SUS using PI in Extended Classic Scenario

Hi SRM Gurus,
We are in SRM 5.0 ,extended classic scenrio and plan to implement SUS for PO create/Change,PO response and
ASN.We plan to use PI for this integration and as per Note 573383 our IT team plans to use two different client
(one for EBP) and other for SUS.Does anyone have a config guide for this scenario??
In this scenario what all configuration are to be done on SRM(EBP) side??Do I need to configure PO/PO response and ASN number ranges for SUS?
Do I need to create a new vendor org structure in SUS client so that I can replicate SRM/EBP vendor to SUS??
What all settings are to be done on PI side.
Any help/documentation in this direction would be appreciated.
Kind Regards,
Priya

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..

SRM 7.0 extended classic - attachments to backend

Hi,
We are in SRM 7.0 and have a requirement to store SRM attachments in the backend ERP.
This is for the extended scenario going through Badi BBP_ECS_PO_OUT.
Has anyone got a solution for moving the attachments to the backend?
Kind regards,
Alexander

Hi,
The purchase order in the Extended Classic Scenario is transferred to the backend system with different Function Modules. The
attachment transfer logic was only implemented in the Classic Scenario.
One reason for this decision was, that the leading Purchase Order in the extended classic scenario is the local one, and in the local purchase order the attachments are available.
At the moment it is not planned to support the attachment transfer in the Extended Classic Scenario. The transfer of attachments to backend PO is developed only for Classic Scenario.
I am sorry that this is not the result that you wanted. This also explains why in the ECS PO transfer BADI BBP_ECS_PO_OUT_BADI does not have the parameters for attachments where as the Classic PO transfer
BADI does (BBP_CREATE_BE_PO_NEW).
We have some notes related to SC and POR reporting issues when transferring attachments to ECC side, but ther are related to Classic scenario:
1400088: SC attachments transferred to ECC PR are lost on EHP upgrade
1413792 Attachment deleted after changing purchase order
Ihope this information help you to understand this issue,
Kind Regards,
Rafael Rhoden

BADI for Classic and Extended Classic Scenario

Hi,
   Please   provide list of Reports and BADI's for
       Classic and Extended Classic Scenario.
Thanks,
Srini

Hi,
In SRM there will be a number of BADI's are Available, We can utilize them according to the requirements
As per the request few important BAID are provided below..
Workflows
1). BBP_CHNG_AGNT_ALLOW:          Allow / Allow Change/Add Approver
This BADI is implemented not to allow users to change the approvers in the workflow.
2). BBP_WFL_SECUR_BADI:          Overwrites the authorization level of the approver
This BADI controls the restart of the workflow
Purchasing Related
1). BBP_PGRP_FIND:               Shopping Cart: Determine Responsible Purchasing Group(s)
This determines the responsible purchasing group for the shopping carts.
Shopping Cart Related
1). BBP_SC_MODIFY_UI:          BADI to Change Shopping Cart Layout
2). BBP_GROUP_LOC_PO:          Exit Grouping of Items for Local Purchase Orders
This splits local PO if more than one contract in a PO.
3). BBP_TARGET_OBJECTS:          Exit while determining target objects in backend
4). BBP_WF_LIST:               Change Worklists and Search Results Lists
This is used to restrict the search results for the user.
5). BBP_CTR_BE_CREATE:          Exit when Creating a Contract in the Backend System
6). BBP_CREATE_PO_BACK:          Exit while creating a purchase order in the backend system
This BADI is used to add the shopping carts attachments to the PO and also to make adjustments in payment terms, currency etcu2026
7). BBP_DOC_CHECK_BADI:     General BAdI in Cross-Check for Message Returns
8). BBP_DOC_CHANGE_BADI:     BAdI for Changing EBP Purchasing Documents
9). BBP_ECS_PO_OUT_BADI:     ECS: PO Transfer to Logistics Backend
Thanks
prasad .s

P-card process available for SRM 5.0 extended classic scenario

Similar Messages

Maybe you are looking for