P - Card in Classic Scenario

Hi Experts,
We are implementing Classic scenario, SAP SRM 7.O and ECC 6.0 with EHP4. Please let us know, If P - card Functionality is available with the above said Package?
The documents clearly mention P- card not supported for Classic Scenario in SAP SRM7.0.
Our client want P-cards Functionality in Classic Scenario Only. Client got very good back end ECC system. Client do not wish to go for Extended Classic.
Please let me know, how we can enhance the Classic Scenario to Support P - Cart.
Is there is Standard Enhancement Package is available from SAP to support P-card from classic scenario ?
Else How much approximate efforts needed to enhance to meet the above requirement ? (If some one already implemented P- card in Classic Scenario)
Please do the needful.
Even correct contact person to get the Quote for above requirement from SAP also helpful.
Thanks
Giri

Hello,
Setting Up Procurement Card Payment : In SAP Supplier Relationship Management (SAP SRM), you can specify procurement cards as the payment method when you purchase items, provided you are using the Materials Management functions in SAP SRM. In addition, you can manage settlements for purchases made using a procurement card. This means you can transfer the settlement file that the bank or card company sends you to SAP SRM to check that the contents are correct and specify account assignments.
Prerequisites
--> You are using the Materials Management functions in SAP SRM.
--> In the back-end system, Accounting is set up, and the card company is created as a supplier.
--> You have set up the ALE distribution model in Customizing for SAP Supplier Relationship Management under:
SRM Server --> Technical Basic Settings --> ALE Settings --> ALE Settings (Logical System)
Procedure
1. Enter your procurement card details using the Create User transaction.
The settlement files are transferred to the SAP SRM system, and invoices and transaction figures
are transferred from the SAP SRM system to the back-end system by the ALE interface.
Note ; You must set the procurement cards up so that the system can transfer the settlement information from the card company, and carry out updates in Accounting in the back-end system
2. If you want to create commitments, do so in Customizing for SAP Supplier Relationship Management under : SRM Server --> Procurement Card --> Manage Commitments
Perform the following activities in Customizing for SAP SRM:
--> SRM Server --> Procurement Card --> Process Procurement Card
> SRM Server> Procurement Card --> Define Number Ranges
--> SRM Server --> Procurement Card --> Allocate Company Code
--> SRM Server --> Procurement Card --> Define Card Company
--> SRM Server --> Procurement Card --> Define Blocking Reasons
Also refer to the below links for further help.
http://help.sap.com/saphelp_srm40/helpdata/en/61/2ff300787411d2b41d006094b92d37/content.htm
http://help.sap.com/saphelp_srm701/helpdata/en/45/f1c0f33b5406f7e10000000a155369/content.htm
http://help.sap.com/saphelp_srm50/helpdata/en/97/b71c4145a6f723e10000000a155106/content.htm
Hope this will help you to configure the P-Card.
Thanks & Best Regards,
Rahul

Similar Messages

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

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

About the Classic scenario,ERP PO number didn't return go Shopping card

About the Classic scenario,We create a shopping card,And approved,the follow document purchaser order create the ERP system,But the Purchaser order number didn't return to the shopping card follow document tab page.How can help me?

Dear Masa ,
Yeah,we schedule program BBP_GET_STATUS_2 and CLEAN_REQREQ_UP,Then have this issue,We didn't know why.

What is external classic scenario?

Gurus,
What is external classic scenario? Is this the other name for Plan driven procurement OR something else? Please clarify
Thanks,
Sid

Hi Siddarth,
This scenario is an extension of the classic scenario. Whereas in the classic scenario, goods and services are processed in the backend system, in the extended classic scenario, the procurement process takes place locally in SAP Enterprise Buyer and a copy of the data is replicated to the backend system. Communication between Enterprise Buyer and the backend system is via RFC. The purchase order is created locally in Enterprise Buyer.
If the data in the shopping cart is insufficient to generate a complete purchase order, you can supplement the data manually in SAP Enterprise Buyer before it is transferred to the backend system. The purchase order in SAP Enterprise Buyer is the leading purchase order. From SAP Enterprise Buyer Release 4.0 with an SAP backend system Release 4.6, the complete purchase order is replicated to the backend. It is a read-only copy and supplies the reference needed for the creation of goods receipts, service entry sheets, and invoices in the backend system. The plant is the criterion used for splitting shopping cart items into different purchase orders. This is because the purchasing organization is determined in the backend system based on he basis of the plant. Goods receipts (confirmations) and invoices can be pre-entered in Enterprise Buyer.
The following takes place in the Enterprise Buyer system:
Search for scource of supply, pricing, tax determination, commitments are updated in the backend system, account assignment and budget check are performed against the backend system.
Data for the Business Information Warehouse is updated partly from Enterprise Buyer and partly from the backend system: Purchase order data is updated from Enterprise Buyer, goods receipt and invoice data is updated from the backend system.
This scenario suits customers:
     Who want their purchasing department to save time and money by using the streamlined purchasing functionality of SAP Enterprise Buyer
     Who want to use the full sourcing capabilities SAP Enterprise Buyer offers, yet who also want to be able to confirm and invoice direct materials
     Who want the flexibility of being able to pre-enter confirmations and invoices in SAP Enterprise Buyer
The extended classic scenario does not support purchase orders based on limit shopping carts or procurement card functions, as these require the invoice to be local.
Hope this helps you.
Please Reward Points if useful..
Regards,
Sreenivas

Creation of Inbound delivery mandatory for ASN process in classic scenario?

Dear Experts,
We are going for classic scenario for our green field SRM implementation process. Our client is not using ASN process in their existing MM process. However, they are now looking for an oppurtunity to enable Suppliers to trigger ASN using SUS. In such case, is creation of inbound delivery from Buyer side a mandatory process?
Is the below the process correct?
PO -> ASN (Supplier using SUS) -> Inbound delivery (Optional) -> Goods Receipt (Mandatory) -> Invoicing.
Here, I understand that Goods receipt can be verified against the PO or via Inbound delivery to PO. ASN will inform the store keeper in advance about impending goods receipt and smoothen the confirmation process.
Could you please comment on the above process? Could you please suggest the best practices followed here?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hey Ranjan!,
You are on track.
The process flow you have shown is true. ASN is available as a standard as part of the MM-SUS process. It makes the buyer aware of any delays in delivery or to make arrangements on shipping docks to receive goods on a said date etc.
Regards,
Nikhil

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.

Backened documents are not getting updated in Classic Scenario

Hi,
We are using SRM 7.0 version and we are working on classic scenario where the shopping cart - RFX - Contract are created in SRM and the PO - GR - IR are created in ECC. The blackened documents which are created in ECC PO - GR and IR these documents are not getting updated in SRM system.
Is there any business functions to be activated.

Hi Sunil,
You manually run report ""BBP_GET_STATUS_2" after PO is created in MM. Then check if the follow-on-docs are updated in SC.
If it is working fine after you manully run report, you will have to properly set time to run this report automatically.
Best Regards,
Anu
Edited by: Anuradha UG on May 18, 2010 8:09 PM

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

SRM 7.0 Unable to create PO - Classic Scenario.

Hello,
We are able to successfully create the below scenario.
PR in ECC --> Get PR in SRM --> Start Collective processing -> Transfer to Central System (SC is created for the PR @ this time) --> Create RFx --> Rfx Response --> Create PO. (PO is created in ERP, Classic Scenario)
We are able to get the PR & we are able to create SC successfully and the PR/ SC is available in Sourcing cocpit.
Able to create RFx --> Rfx Response.
Now once the RFx Response is Accepted --> We go for creating PO.
Classic Scenario.
The error is due to pricing - debugged and checked as mentioned in my earlier message.
IPC pricing is switched off and the BADI for simple pricing is activated.
Error : " Message A BBP_PD 396 cannot be processed in plugin mode HTTP "
But this is due to pricing is what i guess.
Error is raised in FM "BBP_PDPRC_UPDATE".
Kindly Suggest.
Unable to Create PO
Regards.
Edited by: Purshothaman P on Jul 6, 2010 1:50 PM

Hi,
Please check and run the following reports (se38): BBP_CND_CUSTOMIZING_CHECK & RSVMCRT_HEALTH_CHECK and post back the results.
Note for BBP_CND_CUSTOMIZING_CHECK also run 'Simulation of Pricing with Manual Price' (scroll down after executing the report initially).
Also the badi information you activated tells us a lot. Although i take it that you executed and read everything that's included in the transaction information. The following sentence gives a prety doubtfull feeling for the CPPR scenario to work for your configuration:
SAP recommends using this BAdI only in exceptional cases and only after checking thoroughly if it is compatible with the Business Scenarios used.
Note: From what i've just read IPC has to be disabled, certain badi's etc. need to be disabled. And VMC (sap basis) has to be configured. Please view: [http://help.sap.com/SCENARIOS_BUS2008/helpdata/EN/9C/F90B7CB34A4889935D1733C6756D5B/content.htm]
Could you also please check and provide whether 'normal' SRM classic scenarios like: SC -> PO do run within your system. Also the error and information you have provided is very little.
Kind regards,
Tim

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

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

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

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

Creation of PO in Classic scenario.

Hi
i am using classic scenario.my problem is i have created shopping cart&approved.after approving this PR had been generated.
ok. now i want to create PO,GR &Invoice with PR.but i could not create with PR.
so please suggest me How to create PO, GR, Invoice with PR in Back end?
OR
Are these created automatically without PR in Backend?
could any one suggest the process.
BR
sss

Hi
This control settings available in SRM
SPRO
cross apllication settings..
Define Objects for Backend System
check this settings for your material group w.r.t external procurement.
is it PO creation or PR generate settings?
Is your Shopping cart has a valid source of supply.
if your cart is incomplete , PR only created, so check it up.
br
muthu

P - Card in Classic Scenario

Similar Messages

Maybe you are looking for