SRM 7.0 with PDP scenario

Dear Experts,
In SRM 7.0 with PDP scenario which BADI should be used in order to replace the RFC user to the original requestor ?
Thanks and Regards,
Venkata Koppisetti.

Hi Manjunat
His requirement is very clear.
All the PDP scenarion PR converted to shopping cart - good recipient as a RFC user but he wanted to transfer really who created a request in ECC ( if venkat created a PR means VENKAT name shown as Good recipient). I think this is one of crucial request most BUYER requirement since BUYER has to see who really created this request if any clarification of the request BUYER needs to refer backend system as well. this creates some conflict on auditing as well.otherwise BUYER has to refer Purchase request and needs to log in ECC who created this request .Buyer community wants to work only in Web front end not with stone age Dialog screens.

Similar Messages

SRM Extended Classic with eSourcing

Hi Team,
We are using ECC 6.0 with eSourcing and SRM 5.0 with Classic Scenario.
Now we are planning an upgrade from SRM 5.0 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

SAP SRM 7.0 with ECC EHP 4 components to execute scenario

Hi All,
I am new to SAP SRM 7.0.Could you please let me know that what are all the components needs to be in place to execute the technical scenarios and business scenarios.I had an hands on experience on SAP SRM 5.0 with ECC 6.0 backend.
Some where i read that there are lot of configuration changes when we integrate SRM 7 with ECC EHP 4.Do we need to have PI 7 for executing Centralized contract and plan driven procurement scenario?Please guide me to have some exposure towards higher version.Thank you in advance.
Best Regards,
praveen

Hello,
You can refer the INSTALLATION AND UPGRADE INFORMATION , Master guides etc maintained at the below mentioned location which will answer all your query's here.
Goto URL http://service.sap.com/srm-inst and then navigate to SAP SRM --> SAP SRM Server 7.0 .
Best Regards,
Rahul

Direct material procurement in PDP scenario for classic mode

Dear Gurus,
We have configured classic scenario in our SRM 7.01 with backend system ECC 6.0 Enhpk 5. We have PDP scenario for direct material as one of the requirement. The requirement generated in MRP in the ECC backend system will be sent to SRM SOCO for sourcing. Once the right source of supply is found, the follow-on purchase order needs to be created in the ECC backend system in direct material mode.
However, the SAP SRM standard supports only indirect material procurement in PDP scneario for classic mode. How to enable the direct material procurement? Could you suggest any BAdi to be used here?
Thanks and regards,
Ranjan
Ranjan Sutradhar

Hello,
You need to activate the Bsdi 'ME_REQ_SOURCING_CUST' for transferring the purchase requisitions from ERP to SAP SRM.
Some details about the method involved for the same are mentioned below :
Mehtod : IF_EX_ME_REQ_SOURCE_CUST~ACTIVE
->when parameter CV_AUT_SOURCING is set to true, external sourcing (e.g. SRM system) is active in ERP system
->when parameter CV_EXT_RFX_IND is set to true, RFx can be created out of PR directly from ERP system using application CPPR
->when parameter CV_EXT_SC_IND is set to true, PR in ERP system will be transferred to SRM using application CPPR
Method b. IF_EX_ME_REQ_SOURCE_CUST~CHECK_EXTERNAL_SOURCE
Here you need to maintain the logic / condition for which PR has to be transfered to SOCO.
Example
IF ( is_req_item-ekgrp = 'SRM' AND is_req_item-matkl = '100' )
cv_ext_sourcing = cl_mmpur_constants=>yes.
ENDIF.
When this BADI is active whenever you save a PR with say the purchasing group as SRM and material group is 100 (as per sample code above), system automatically triggers the PR transfer from ERP to SRM by xml's.
Best Regards,
Rahul

Question on PDP scenario?

Hi Friends
Why SRM 7.0 doesnt support PDP with standalone scenario. What settings need to be done inorder to enable PDP with standalone scnario in SRM 7.0
Regards
Akhila

Hi,
MRP, PS(project System), PM(Plant Maintenance) are in ERP side.
Do you expect those in SRM server? What is your expectation and business process?
Regards,
Masa

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 7.0 with Document Builder

Hi Experts,
We have a SRM 7.0 with PPS. We want to use Document Builder function. We could find the Document Builder node in IMG (tcd spro).
According to the Business Scenario Configuration Guide of SAP Document Builder, it seems we need install PSDOCB 300 add-on. But I couldn't find the PSDOCB 300 add-on in SMP( no authorization?).
Should I install PSDOCB 300 or Document Builder is already build-in?
If I should install PSDOCB 300,where I can find it, pls show me the download path?
If Document Builder is already build-in, what should I do to show the node in IMG?
Thanks!
SRM 7.0
NW7.01
PPS is actived

Hi Jay,
I made a double check, there is no Document Builder node under IMG >>Cross-application Components in our SRM system.
Is there any components we didn't install?
BTW : we have Integration with SAP Document Builder node .
The following is installed sofeware components in our SRM system:
SAP_ABA             701     0007     SAPKA70107     Cross-Application Component
SAP_BASIS             701     0007     SAPKB70107     SAP Basis Component
PI_BASIS             701     0007     SAPK-70107INPIBASIS     Basis Plug-In
ST-PI         2008_1_700     0000     -     SAP Solution Tools Plug-In
SAP_BS_FND       701     0008     SAPK-70108INSAPBSFND SAP Business Suite Foundation
SAP_BW             701     0007     SAPKW70107     SAP Business Warehouse
SAP_AP             700     0021     SAPKNA7021     SAP Application Platform
SRM_PLUS             700     0009     SAPKIBK209                          SRM_PLUS for mySAP SRM
SRM_SERVER      700     0009     SAPKIBKV09     SRM_SERVER
SRM_EXPL             700     0009     SAPK-70009INSRMEXPL     SRM Extended Functionality for SRM_PLUS including PPS
SRM_EXT             700     0009     SAPK-70009INSRMEXT     SRM Extended Functionality for SRM_SERVER including PPS
VIRSANH          530_700     0011     SAPK-53311INVIRSANH     SAP GRC Access Controls 5.3 for 700 HR a

Approval for SC created through ECC PR in PDP scenario

Hi All,
We are implementing SRM 7.13 and have enable PDP scenario without PI.As per standard configuration SRM SC is created in APPROVED status and is available in SOCO for buyer. In our case we have a requirement that SC should be created in Awaiting Approval and follow the Approval process.
Please share your exeperience and let me know the object we have to customized for this.
Thanks,
Ankur

Hi ankur
You would have to do the customization for this in your system
BADI ME_REQ_SOURCING_CUST holds the logic for the PR transfer to SRM.
You may refer to the link below in all these and confirm .
http://help.sap.com/saphelp_srm40/helpdata/en/99/8afc524b07574fa215b32f1da9ddd4/content.htm
http://scn.sap.com/thread/324350
http://scn.sap.com/thread/1625682
http://scn.sap.com/thread/1608535
I am also pasting a link below and you should check the same it would be helpful much in achieving what you need .
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5082a622-7310-2c10-1a9b-ef31dd69a770?quicklink=index&…

IDOCs not generating with classic scenario

Hi,
We are with SRM 7 with Classic Scenario.
Issue : SRM Org. structure is replicated from ECC system through IDOCS. But, suddently, no IDOCs are getting generated in SRM after we run PFAL in ECC.
IDOC is getting created in ECC after we run PFAL but not creating in SRM.
Your inputs are appreciated.
Thanks
Nag

Hi,
We have faced same issue.
You first check with tcode WE05 in both SRM & ECC. You will get to know which idocs present (transferred).
You can process unexecuted idocs using tcode BD87.
After processing idocs you must run distribution model.
This way we resolved our issue.
Regards,

SRM 7.0 for Standalone Scenario

Hi ,
We are planning to implement SRM 7.0 for Standalone Scenario. Is there any document or help to getting start this requirement? is it possible to create PO and other follow on documents in SRM and replicate them to legacy system in Standalone Scenario? you help will be great and thankful..
Jr.SRM

Hello,
You should start with downloading the configuration guide from [http://service.sap.com/instguides]. An installation guide for BASIS can be found here aswell.
I think that your requirement can definetly be covered, srm standalone <> legacy back-end. The method(s) (RFC/iDOC/XML cq PI) used depends on your landscape and how you design this.
You've got a big but nice challenge ahead of you. Good luck!
Kind regards,
Tim

Detailed Design Architecture of SRM 5.5 with all components with interfaces

Hi All,
I am implementing SRM 5.5. Extended Classic Scenario with all Business Scenario's. We are using components are
1)      SRM, Bidding Engine and LAC in one server.
2)      SUS, Supplier Registration, cFolders in one server.
3)     SRM-MDM Server.
My Question is. I would like to know detailed Architecture of all the components and how it is integrating each other servers.
Is there any Interface between supplier registration and suppliers?, If yes, what is that and what for it.
If anyone has detailed Architecture design please share with me.
Highly appreciate for your help......
Awaiting for quick response.........
Thanks & Regards,
John.
Edited by: johnmiller465 on Aug 20, 2009 2:33 AM

Hi Masa,
Thanks for your response and awarded points. and I have another question.
We are Implementing SRM 5.5, Extended Classic Scenario for Goods and Services (Stock and Consumables).
I have 400 cost centers. How to assign G/L Accounts to multiple cost centers, in Define G/L Accounts for Account assignment category and Product category?.
I guess, By using BADI - BBP_DETERMINE_ACCT. If this is correct, Do we have to develop any ZTABLE for this. Or only BADI enough?.
Please anyone explain details.
Thanks in Advance.
Thanks & Regards,
John.

SRM 5.0 with XI 3.0

Hi ,
Can I integrate SRM 5.0 with XI 3.0.
Thanks & Regards,
krian.
Edited by: Kiran Ponnam on Jan 14, 2008 8:57 PM

Hi,
The Discussion will help you
SRM AND SAP XI
XI with SRM 4.0
Regards
Agasthuri Doss

SRM 4.0 (with SRM Server 5.0) ---- XI 3.0-------R/3

Hello Friends
Iam also working in SRM. I want to integrate SRM and XI for sending a PO from SRM to third party system through XI. I already have a PO created in SRM and I want to send it through XI to Third party system and then want to create corresponding Sales Order in that system.
We are using SRM 4.0(with SRM Server5.0)and XI 3.0.
Thanks in Advance........

Hi <b>Narayana</b>!!
Treat SRM as another R/3 system and use the general flow logic. Create a Sender RFC to send the PO that you have created from SRM system using RFC sender adapter to XI.
Another way:
You can create a work flow which will trigger an IDOC once your PO is created and the IDOC will reach XI using ALE. You need to configure RFC destinations and partner Profiles etc.
Once your PO informations reaches XI you have to configure reciver adapter based on your third Party.
Lets say your third party system is a J2ee application or another R/3 system then you have to configure either a reciver http adapter or a Reciever RFC adapter.
I know this is quite generic......
Cheers!!
AnuraG

How to implement a Copy or Create with Reference scenario

For business objects, you might want to implement a Copy or Create with Reference scenario. The following procedure describes the UI configuration that you need if you want to place a copy button (in our example on an OWL) that starts a quick activity floorplan (on the same BO = Copy, or a different BO = Create with Reference). Pre-requisie in the target BO: The target BO requires a BO element SourceBOID and a Copy action that reads the SourceBO by SourceBOID by query, and copies the elements from the source to the target BO.
The UI configuration in the target floor plan is:
1. Open the QAF floor plan of the target BO (target floor plan).
2. In the DataModel view of the target floor plan, select the Root entry and select Add Data Field from the context menu. Rename the created data element to OBN_OriginBOID.
3. Choose the Controller tap, and select INPORTS and choose ADD INPORT from the context menu. A new in-port is created. Rename the in-port, for example to Copy.
4. In the in-port maintenance form, activate the check box OBN INPORT.
5. Select the namespace of your solution and the target business object.
6. In the input field SELECT OPERATION enter Copy. A new select operation is created. The combination of business object name (including namespace), business object node and operation identifies the in-port and therefore the related floor plan as navigation target.
7. Select the port type package /SAP_BYD_UI/SystemPortTypes.PTP.uicomponent.
8. In the PARAMETERS section of the form, click the ADD button. Maintain the binding of the created parameter to /Root/OBN_OriginBOID. Based on this configuration, the system will transfer the parameter of the in-port to the element in the data model when the OBN is executed.
9. In the Properties view, select the drop-down list box of the property EVENTS u2022 ONFIRE. Scroll down and select the entry u2026 NEW EVENT HANDLER u2026. The system starts the maintenance window for event handlers. Rename the event handler to CopyIn.
10. In the OPERATIONS table of the maintenance window for event handlers, select type: BUSINESS OBJECT OPERATION. In the form below the table select the value CREATE for the input field BUSINESS OBJECT OPERATION TYPE. This operation will create a BO instance in the backend when the OBN is executed.
11. In the OPERATIONS table, create a new operation of type: DATAOPERATION. In the configuration of the data operation, select the operation type ASSIGN, source expression /Root/OBN_OriginBOID and target expression /Root/<BO>/OriginBOID.
12. Create a third operation of type: BUSINESS OBJECT ACTION. Select the Copy action of the target business object and click the BIND button. Note: This action enforces another roundtrip to the backend. The Copy action must be implemented so that it will read the origin BO and copy selected data from the origin to the newly created object.
13. Test the changes in the preview. If no error message is issued, save and activate the floor plan.
The following procedure describes the configuration in the source floor plan (e.g. OWL floorplan ):
1. Open the Source BO OWL floor plan (source floor plan).
2. In the Designer view, place cursor the on the toolbar area and select ADD u2022 APPLICATION-SPECIFIC BUTTON u2022 MY BUTTON from a context menu. Rename the new button to Copy.
3. In the Properties view, select the drop-down list box of the property MENU INFORMATION u2022 NAVIGATION. The system launches the maintenance window for OBN configuration.
4. Select the in-port of the target floor plan by selecting the target business object (with namespace and name) the target business object node and the target operation, and the operation Copy.
5. Choose the navigation style NEWWINDOW.
6. Close the OBN configuration maintenance window by clicking the OK button. The system creates the OBN configuration, an out-port, that is used by the OBN configuration, and an event handler that uses the out-port and that is assigned to the button (see Properties view, EVENTS u2022 ONFIRE).
7. Go to the Controller view and rename the OBN configuration to Copy, the new out port to Copy and the new event handler to CopyOut.
8. Check that the event handler CopyOut fires the out-port Copy.
9. In the Parameters section of the out-port maintenance form, click the ADD button. Maintain the binding of the created parameter as /Root/<BO>/<BO>ID. Based on this configuration, the system will transfer the identifier of the selected source BO to the out-port data structure when the OBN is executed.
10. In the Operations table, select type: FIREOUTPORT. In the form below the table select the out-port CopyOut.
11. Test the changes in the preview. If no error message is issued, save and activate the floor plan.

Hi Dries-
There are no pre-packaged solutions with BADIs since they are, by definition, custom development. If that's the path you need to go down then consider the following high level alternatives:
Incorporate custom code into the BPC Write Back BADI. You can restrict the execution of the BADI using filters on the BADI definition, so that the BADI execution only occurs when a data manager package is called, and only for some defined combination of applications/appsets. Utilized the standard copy/move functions delivered in Data Manager. When the BADI is called, interrogate each record being processed (table CT_ARRAY) and determine if the record has a value you want to process (i.e. save to the target application). Skip any record that has a zero value.
Another alternative is to develop the BADI as custom logic. Data Manager parameters can be picked up in Script Logic and the values can be sent to the BADI by adding parameters. Please see an example of parmater use in the "How To" document for Destination App at:
[EPM How To Guides|https://wiki.sdn.sap.com/wiki/display/BPX/Enterprise%20Performance%20Management%20%28EPM%29%20How-to%20Guides] > "How-to Desitnation App"
Regards,
Sheldon

Central contract in SRM 7.0 with ECC 6.0

Hi
We are using SRM 7.0 with ECC 6.0
When we create contract in SRM 7.0 & Trying to distribute to Backend as Contract, It is showing error in BBP_PD as below
HEADER I1015 Awaiting Approval
HEADER I1021 Created
HEADER I1038 Complete
HEADER I1141 Released
HEADER I1180 Document Completed
HEADER I1193 In Distribution
HEADER I1195 Distribution Incorrect
0000000001 I1143 Item is Active
Badi BBP_DETERMINE_LOGSY is activated to define backend system
No IDOC is also generated.
No errors in MOnitor also
Not sure what is message type needs to define & what else is needed
Regards,
NNK

HI
Need to do following
1. Keep conidtion types in ECC & SRM same for contract.
2. Also Add message types BLAORD & COND_A manually in ECC in WE20.
Then only it works
Regards,
NNK

SRM 7.0 with PDP scenario

Similar Messages

Maybe you are looking for