Pcard integration in Classic Scenario

Hi All
I learnt that it is possible to use pCard in Classic Scenario if a few customizations are made.
These customizations include adding a few custom fields in the shopping cart & ECC PO for Pcard Company, Pcard Number
and Validity date.
However once these customizations are done, would the reconciliation in SRM work as in ECS, or further code changes will be required?
Thanks
Kedar

KedarG wrote:
> Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
> Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
>
SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
and invoice anyways has workflows which you can use

Similar Messages

PCARDS in extended classic scenario

Is it possible to use PCARDS in extended classic scenario?

Madidipa-
True this is only available as a standard option with stand alone scenario. However it can be enabled with a a customized process, using customer fields. In fact this process was highlighted in a SAP Teched presentation a couple of years back.
In short we created customer defined fields to hold the pcard, linked to the pcard master data tables in EBP, and then when it goes to the R/3 we created an additional account assingment category to make R/3 happy and set it for no invoice.(the pcard data was transferred to R/3 as additional customer fields) As usual, with enough time and money most things are possible.
Regards-
b

SUS-MM integration in Classic Scenario for SRM

Hello All,
We are using SAP SRM in classic Scenario.
We also plan to integrate SUS with MM .
Looks like in the Classic Scenario with SRM , only the Direct material procurement is possible
using MM- SUS.
How would the SUS-MM integration work for Indirect PO's.
Our Process is as follows:
1) Shopping cart created in SRM for Indirect material & approved ( with cost assignment)
2) Classic PO created in backend & sent to SUS
After this step is it possible that the Vendor create the GR in SUS and it is sent to ECC for Approva through PI l??
Thanks
Kedar

KedarG wrote:
> Is it possible in Classic Scenario, to send the SUS confirmation to SRM instead and from there to ECC
NO. dont think of a situation like that. if it is classic scenario except SC every thing will in ECC. how do you think confirmation creation can be possible in SRM when PO is not present in SRM!!
> Can you provide some details on ECC workflows. I didn't find any thing on this. Does ECC even support workflows as SRM?
>
SRM is a kiddo infront of ECC, so workflows definitely are present in ECC(not BRFs but event driven wfs).
any ways, your solution would be a custom solution, implement MB_DOCUMENT_BADI, to trigger a custom WF from custom event. this can be used for notification and stuff. but it wont stop the execution, so, dig on it how to stop the GR post till the workflow is not over.
and invoice anyways has workflows which you can use

Extended Classic Scenario - how does the integration work ?

Hi,
Apologies for asking a basic question, but we are looking at requirements for integrating SRM with R/3 using the extended classic scenario and I need to understand how the integration actually works ? How is the data transferred between the 2 systems ? Does it use BADI's, idocs etc ?
Many thanks,
fiona

Hi Olaf,
I just wanted to give some precision on what you said (in the thread How to "see" PO in EBP ? also)
The Extended classic scenario only refers to the local PO creation replicated in R/3.
In this scenario, in the R/3 PO only the data not managed/sent from the SRM are available for modification (which depends on the SRM version you use)
The "PR transfer from R/3" is called "Plan driven procurement", and in this scenario only RFC is used, the qRFC are only used for BDocs of the CRM Middleware.
Regards.
Vadim

Does SRM 7 Extended Classic Scenario support PCards?

Does SRM 7 Extended Classic Scenario support PCards as standard? I know SRM 4 does not but wanted to know if that has changed.

Paul,
URL https://websmp208.sap-ag.de/support ( service.sap.com) ...on header
Go to 'Release& Upgrade Info' ..then sub item 'Release notes'....look for SAP Solutions on left scroll...then select SRM...
Open pdf file ' Release Notes SAP SRM 2007, SP00 - SP04 '...and look for pg # 40...
Let me know if you did not get it..
Thanks,
Rahul Mandale

In an extended classic scenario, how can we make few purchase orders to sta

Hi All,
In an extended classic scenario, how can we make few purchase orders to stay local (i.e. without copying it to the back end). The decision criteria to stay local is information other than product category, i.e. using pcard and the cart value.
Thanks
Murali

Murali,
As I said usually this integration is done using ALE - IDOCs. You can find the all the configuration do be done here.
http://www.sappro.com/downloads/OneClientDistribution.pdf
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
In this the filtering can be done at two levels.
1. Data Filtering
2. Segment Filtering
Data Filtering:
Data filtering can be done in dustribution model where you can restrict whole IDOCS or partials IDOCS to be send based on data in fields inside IDOC depending on whether the segment in which you filter is at the highest level or at a lower level. For example in MATMAS if you put a filter of E1MARCM for a particular plant , only data for this plant will go and other plants will be ignored.
Look at BD64 where you can do the config for data filtering.
Regards,
Ravi
Note : Please mark the helpful answers

Classic scenario service PO replication

Scenario:-
Classic Scenario
No PI(Process Integration)
No PDP (Plant Driven Procurement) process
Today we created new Service purchase requisition (which is never adopted for PO creation) which contains only one item(10), under this line item (10) five service Numbers…as 20000000(Line-10),20000021(Line-20),20000025(Line-30),20000033(Line-40),20000058(Line-50)
then
Our process:-
Purchase Requisition(Service) Transferred from ECC to SRM - >Purchase Requisition Converted in to shopping cart in SRM> Shopping Cart goes to sourcing -> buyer
creates RFx by adopting the Shopping Cart -> RFx is sent to bidder -> bidder will respond >RFx Response number will be created in SRM>Buyer will compare the RFx responses -> Buyer will click on the RFX response number of L1 vendor>in the RFX response screen when he will click on the “CREATE Purchase Order”
Issue:- why in Service PO items are splitted in to item-10,item-20,item-30,item-40 which is not same like in Service PR
Hope if above issue will solved below error message wont appear
Error Message:-
Materials of requisition 2100000654 item 00010 alr. ordered in full
Message no. 06076
Please Find the attached screen shot
Thanks
Madhu

Can you please elaborate more on this .
from what I understand you want the SC item to not split into different PO generally it spits based on different shipping address maintained . You can also check this in BADI ZBBP_GROUP_LOC_PO
Below is a sample code I found from one of the earlier threads as below :
http://scn.sap.com/message/2772557#2772557
http://scn.sap.com/message/3155145#3155145
http://scn.sap.com/message/2877448#2877448
http://scn.sap.com/message/2371974#2371974
https://scn.sap.com/thread/2026160
https://scn.sap.com/thread/54153
METHOD if_ex_bbp_group_loc_po~group_po. 
*------------------------------------------------------------------------------* 
* Exit Grouping of Items for Local Purchase Orders 
** Parameters 
*ITEM_DATA TYPE BBP_INT_ITEM_GROUP Item Data for Shopping Basket Item 
*It contains the most important item details of the shopping cart and 
*additionally in the field REFNUMBER a reference number for further 
*processing purposes 
*------------------------------------------------------------------------------* 
* Method used to group item before PO creation 
* How it work ? 
* 1/ Select extra colons from table ZPO_SPLIT_CRITER 
* 2/ Getting Compoents from existing type BBP_INT_ITEM_GROUP 
* 3/ For each line recalcul Refnumber 
********************************************************************** 
* Declarations 
********************************************************************** 
*--------------------------------------------------------------------* 
* Variable 
*--------------------------------------------------------------------* 
DATA: lt_zpo_split_criter TYPE TABLE OF zpo_split_criter 
 , ls_zpo_split_criter TYPE zpo_split_criter 
 , lo_struct TYPE REF TO cl_abap_structdescr 
 , lt_field_list TYPE ddfields 
 , ls_field_list TYPE dfies 
 . 
 
DATA: 
 lt_item_data TYPE bbp_int_item_group 
, ls_item_data TYPE bbp_int_item_groups 
, ls_back_data TYPE bbp_int_item_groups 
, ls_modi_data TYPE bbp_int_item_groups 
, l_fname TYPE fieldname 
, l_refnumber TYPE refnumber 
, l_tabix TYPE sytabix 
, l_not_empty TYPE c 
, l_act_not_empty TYPE c 
. 
*--------------------------------------------------------------------* 
* Field symbols 
*--------------------------------------------------------------------* 
FIELD-SYMBOLS: <lfs_refnumber> TYPE bbp_int_item_groups-refnumber 
 , <lfs_act_refnumber> TYPE bbp_int_item_groups-refnumber 
 , <lfs_field_value> TYPE ANY 
 , <lfs_act_field_value> TYPE ANY 
 . 
*--------------------------------------------------------------------* 
* Constants 
*--------------------------------------------------------------------* 
* CONSTANTS: 
* . 
********************************************************************** 
* Process 
********************************************************************** 
* 1/ Select extra colons from table ZPO_SPLIT_CRITER 
SELECT * FROM zpo_split_criter INTO TABLE lt_zpo_split_criter 
 WHERE split EQ 'X'. 
CHECK NOT lt_zpo_split_criter[] IS INITIAL. 
DELETE lt_zpo_split_criter WHERE fieldname = 'REFNUMBER'. 
 
* 2/ Getting Compoents from existing type 
lo_struct ?= cl_abap_typedescr=>describe_by_name( 'bbp_int_item_groups' ). 
CALL METHOD lo_struct->get_ddic_field_list 
 EXPORTING 
 p_langu = sy-langu 
 p_including_substructres = abap_true 
 RECEIVING 
 p_field_list = lt_field_list 
 EXCEPTIONS 
 not_found = 1 
 no_ddic_type = 2 
 OTHERS = 3. 
IF sy-subrc <> 0. 
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO 
* WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4. 
ENDIF. 
 
LOOP AT lt_zpo_split_criter INTO ls_zpo_split_criter. 
* Verify if field exist in table 
 READ TABLE lt_field_list 
 TRANSPORTING NO FIELDS 
 WITH KEY fieldname = ls_zpo_split_criter-fieldname. 
 CHECK sy-subrc EQ 0. 
 
* Copy table in internal 
 lt_item_data[] = item_data[]. 
 
* Sort table by REFNUMBER and fieldname 
 SORT lt_item_data 
 BY refnumber (ls_zpo_split_criter-fieldname) 
 ASCENDING. 
 
* Clear internal value. 
 CLEAR: l_refnumber 
 . 
 
 CONCATENATE 'LS_ITEM_DATA-' ls_zpo_split_criter-fieldname 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_act_field_value>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_BACK_DATA-' ls_zpo_split_criter-fieldname 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_field_value>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_ITEM_DATA-' 'REFNUMBER' 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_act_refnumber>. 
 CHECK sy-subrc = 0. 
 CONCATENATE 'LS_BACK_DATA-' 'REFNUMBER' 
 INTO l_fname. 
 ASSIGN (l_fname) TO <lfs_refnumber>. 
 CHECK sy-subrc = 0. 
 
 CLEAR: <lfs_refnumber> 
 , <lfs_field_value> 
 . 
 
* For each reccord in table, calculate new REFNUMBER 
 LOOP AT lt_item_data INTO ls_item_data. 
 MOVE sy-tabix TO l_tabix. 
 IF <lfs_act_field_value> IS INITIAL. 
 MOVE ' ' TO l_act_not_empty. 
 ENDIF. 
 
 IF ls_zpo_split_criter-as_not_blank IS INITIAL. 
* Case of each value on field create a new refnumber 
 IF <lfs_field_value> NE <lfs_act_field_value> OR 
 <lfs_refnumber> NE <lfs_act_refnumber> . 
 l_refnumber = l_refnumber + 1. 
 MOVE <lfs_act_field_value> TO <lfs_field_value>. 
 MOVE <lfs_act_refnumber> TO <lfs_refnumber>. 
 ENDIF. 
 ELSE. 
 IF l_not_empty NE l_act_not_empty OR 
 <lfs_refnumber> NE <lfs_act_refnumber> . 
 l_refnumber = l_refnumber + 1. 
 MOVE l_act_not_empty TO l_not_empty. 
 MOVE <lfs_act_refnumber> TO <lfs_refnumber>. 
 ENDIF. 
 
 ENDIF. 
 ls_modi_data = ls_item_data. 
 ls_modi_data-refnumber = l_refnumber. 
 
 MODIFY item_data FROM ls_modi_data INDEX l_tabix 
 TRANSPORTING refnumber. 
 ENDLOOP. 
ENDLOOP. 
 
ENDMETHOD.
 
 
 
It works with the table ZPO_SPLIT_CRITER as bellow: 
CLIENT MANDT 
FIELDNAME FIELDNAME 
SPLIT BOOLE_D 
AS_NOT_BLANK BOOLE_D 
 
If you need more information, contact me directly. 
Regards, 
 
David BOUTIER 
Consultant technique Sap Netweaver - KALYDIA 
8, rue Pasquier - 75008 Paris

SRM & SUS in Classic scenario

Hello SRM Gurus,
I would be great if you could give your overview for below my quires.
I have good idea of SRM with SUS for extended classic scenario. But how would be the communication between SRM and SUS in Classic scenario. Because the PO will be created in backend.
Now my question is in Classic scenario,
What is the use of SUS in classic scenario?
How the PO will be transfer to SUS system? Does the PO data from SRM or ECC?
What is the communication data between SRM and SUS?
Kindly provide me above information and also your thoughts.
Thanks.
Regards,
Magesh.

Hi Mahesh,
If you are using SRM7.0 & ECC EHP4 version with classic scenario then you can user configuration gudie "Plan-Driven Procurement with Supplier Integration: Configuration Guide" (Release SRM4.0).
But following keys points are to be noted for SRM7.0:
1. "PO" and "service entry confirmation" will be handled using XML messages.
2. To send PO's using XML messages to SUS from ECC activate the workflow in SWETYPV transaction by falging "Linkage activated" for object BUS2012(CHANGED & CREATED) for workflow ws3800008.
3. take the help of PI consulatant to enalbed the PI messages to send PO and Serivce confiramtion bewtween SUS and ECC.
ERP     PurchaseOrderERPRequest_out_V1                          PurchaseOrderERPRequest_In_V1                         SRM
SRM     PurchaseOrderERPConfirmation_Out_V1     PurchaseOrderERPConfirmation_In_V1                         ERP
SRM     ServiceAcknowledgementERPCreateRequest_Out     ServiceAcknowledgementERPCreateRequest_In     ERP
ERP     ServiceAcknowledgementERPConfirmation_Out     ServiceAcknowledgementERPConfirmation_In     SRM
ERP               ServiceAcknowledgementERPCancellationNotification_Out                                                                                    ServiceAcknowledgementERPCancellationNotification_In     SRM
With Regards
Manjunath

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

ASN for extended classic scenario

Hello all,
we have SRM with extended classic scenario (EBP-MM),
is it possible to use ASN (shipping notification) functionality in our system ?
Kind regards,
Arthur

Hi
ASN can be created by the vendor in SUS system for that XI mapping is required. ASn can be created in SUS by any vendor users. I guess it's not possible with ECS.
Please check the SAP Consulting Note 1026638 GR Output Integration with MM-SUS Scenario for R/3 <= 47
You need to have functional background for this:
To create an ASN against PO or SA release:
1. you need to compulsarily put how much qty you are sending against the reqd. qty(shown by PO / SA )
2. dispatch vehicle no. (optional)
3. road challan no. (optional)
4. one more optional entry ( sorry I forgot)
Useful related pointers ->
Re: how does the GR get into SUS---MM-SUS Sceanario
ASN in Extended Classic Scenario with SUS
SUS ASN & Invoice
The specified item was not found.
Do let me know.
Regards
- Atul

SUS-MM vs SUS-EBP (Extended CLassic Scenario)

Hi!
We have an extended classic scenario already up and running between ERP->EBP system without XI usage.
Now it is necessary to configure SUS integration for ASN creation purpose. As I can see SAP has 2 standard configuration guides: one for SUS-MM and another one for SUS-EBP, but they are not fully relevant for ECS.
Could anybody tell me please from what system EBP or ERP it is better to send PO to SUS system when we are using extended classic scenario? And what are advantages/disadvantages of this?
Thanks and Regards,
Siarhei

Hi Dinesh!
Thank you for your answer! It is clear that leading PO is in EBP, but why I can't use ORDERS and ORDCHG IDOCs to transfer PO and PO chnages to SUS?
One other question: do you know whether Configuration Guide for ECS exsits (like SUS-MM and SUS-EBP documents)?
BR,
SIarhei
Edited by: Siarhei Tsikhanenka on Apr 4, 2008 9:56 AM

PCard Configuration In ECS Scenario

Dear Gurus,
Greetings for the day,
We are currently in between Development of Procurement Card (PCARD) Deployment in our customer landscape. They have SRM 5.0 version with Extended Classic Scenario (ECS)
We have performed below Configurations from SRM point of View:
- Configuration of Number Range for Procurement Card
- Define Card Company
- Allocate Company Code (Mapping of Back end Vendor, Clearing Account & Account Type)
- Define Blocking Reasons
- Manage Procurement Card Commitments
- Process Procurement Card
Also User Authorization Prospective we have completed below activities:
- Provide Procurement Card role (SAP_CRM_PAYMENT_CARD)
- Add Profile (M_BBP_PC) to respective user
- Maintain Parameter ID's (PCC & PCI)
- Maintain Authorization value as "4" while creating Procurement Card Master
Issue: When we tried to raise an "Describe Request" shopping cart with this user we are unable to see "Procurement Card" field in Shopping Cart "Basis Data" tab.
Also i am unable to find any option to maintain "Product Categories" option under "Procurement Card" node. So in case of SRM 5.0 scenario this option is not available? please advice
If any one has suggestions please advise.
Thanks & Regards,
Manish

Dear Experts,
Kindly help me to resolve above issue on SRM PCard Deplyoment
Thanks & Regards,
Manish

SAP eSourcing with SRM Extended Classic Scenario

Hi Team,
We are using ECC 6.0 with eSourcing. Currently we use SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.5 to SRM 7.0 and want to do the Extended Classic Scenario. This will help us to do additional functionalities of SRM.
eSourcing can be used for Strategic RFx and CLM functionalities.
SRM can be used for SC, Operational Sourcing and PO. We can also use the SRM-SUS Scenario for PO confirmation and Invoices.
Have any one used eSourcing with SRM Extended Classic? In that case, please provide some light into how to use all these application to better streamline the overall Source to Procure strategy.
Also, do you think Classic is the way to go or Extended Classic is better? Any documents or pictures are greatly appreciated.
Thanks
Jogy

Hi
SAP provide standard integration b/w ECC and Esourcing/ CLM (PR (both inbound and outbound). However in case you decide to go with extended classic scenario,you might need e Sourcing/ CLM integration with SRM (since PO would be created in SRM) which is not provided out of the box by SAP. However custom interface (based on flat file transfer) can be built b/w SAP SRM and e Sourcing.
MM-SUS scenario is not much different from EBP-SUS scenario in terms of functionality.
Regards
Mudit Saini

MM-EBP-SUS in classic scenario

Hi,
We have classic scenario to be implemeted with EBP-MMsystems.
Please let me know if SUS is also involved in this landscape to send the PO to the suppliers online what will be the exact process flow
Can SUS be integrated with EBP in this scenario.
Pls advise
Thanks,
Manu

Manu
SAP Note 700350 will provide full details of the restrictions between the various SRM deployments and SUS.
In summary the procurement of materials in SRM-EBP with SUS integration is supported, (although there is always been some debate about this). The procurement of services is not supported, (unless you are on SRM 7.0 ramp-up), as it is not possible to replicate a SUS service confirmation back to SRM-EBP. SAP Consulting will provide a custom solution to overcome this restriction for a price, SAP Note 868192 describes.
Remember you will need to install and deploy XI to use SUS.
SRM 6.0 onwards only supports PI 7.1 not XI.
Regards
Mike

Currency configuration in classical scenario

Hi all,
I am working on a SRM 3.0 in a classical scenario. I checked at IMG (SAPWAS->General Settings->Currencies) that there are lots of customizing that can be done here (currency codes, decimal places, exchange rates, quotation, expiring curencies, etc...).
I want to know if it is required to set this customizing in a classical scenario or this should be done only in the backend. Also, please inform if there is a minimum config that can be done in EBP.
Very thanks in advance.
Renato Lazaro

Dear Experts,
Kindly help me to resolve above issue on SRM PCard Deplyoment
Thanks & Regards,
Manish

Pcard integration in Classic Scenario

Similar Messages

Maybe you are looking for