About standard scenarios on SRM

Hi,
We are planning to install SRM 7.01 in its most general scenario.
Supliers will access Business Packages for SRM and BSP's for SUS via portal deployed on DMZ.
We need to know if its possible to deploy SRM Servers also in DMZ while leaving rest of systems on a inner securized network to avoid that if the WAS (WD a BSP) is hacked, the intruder has not direct access to the rest of systems in securized networks.
Thanks

Hi,
We have searched in official Master and Security Guide and other documentation and didn't find any explicit mention to the landscape I described.
Looking at diagrams we think it's possible but we will thank you any experienced on that.
Thanks

Similar Messages

Standard scenarios for Orchestrator

Hi all,
i've deployed SCO in new environment about 60 servers with Hyper-V cluster, VMM, CCM, SCOM, Exchange, .. ETC.
basically this is first time i'm dealing with SCO. i don't know the standard scenario i can do basic scenario and how i can apply that.
where i can get sample projects / deployments i can apply and how?
sorry for very basic questions!

These might get you started.
https://orchestrator.codeplex.com/releases/view/86195
Vaughn

The Problem is about Standard Back Button Function in Report Program

The Problem is about Standard Back Button Function in the Report Program.
In the Report,First call screen Then Using "write" output some information,That is ok. but In the GUI When I press back button that is standard button,it exit screen to program.
My question is how can i do When i press back button,the screen can be back forward first screen instand of exit screen to program. Thanks .

This problem is solution.I call screen using T-code and submit report In PAI,at last return to PAI.That is OK.

The Problem is about Standard Back Button Function in the Report Program.

The Problem is about Standard Back Button Function in the Report Program.
In the Report,First call screen Then Using "write" output some information,That is ok. but In the GUI When I press back button that is standard button,it exit screen to program.
My question is how can i do When i press back button,the screen can be back forward first screen instand of exit screen to program. Thanks .

Hi,
You can define your own PF-STATUS and in that assign the function code for BACK button anything except 'BACK'.
The code would somewhat look like this:
SET PF-STATUS 'TEST'.
write : itab-col1,
itab-col2.
in the PF-STATUS 'TEST', assign the function code to BACK button as 'BCK'.
Now in your program you can use the event AT USER-COMMAND.
In this you can handle the functionality of BACK button.
Hope this helps.
Regards,
Himanshu

Plant Driven Procurement scenario in SRM Throgh XI.

We are doing plant driven procurement scenario in SRM through XI7.0
(ECC 6.0 (MM)- XI7.0 -SRM5.0 SUS)
1.we downloaded XI Content for SRM Server 5.5 SP 12.But we are unable
to find out SAP ECC 6.0 Software component Versions or Product version
in SAP XI 7.0 SLD.
Please, Suggest the solution to solve this problem.

Hi Prateek,
I am doing Plant driven procurement service enablement scenario by using XI 7.0, for this,
we are integrating MM & SRM SUS Through XI 7.0 (MM -- XI-- SRM SUS).
For doing this Scenario,
1. Downloaded XI Content for SRM
2. Imported XI Content into the IR
3.After importing, Plan_Driven_Procurement_SupplierEnablement Scenario was enabled.
Here, MM side SWCV is R/3 4.6 is available by default. but in my case i need to change to ECC 6.0(bcoz,currently we r using ECC 6.0 version )
In SLD, there is no ECC 6.0 version.
So, how to solve this issue.
Thanks in Advance.
Mahesh

What are the main points to freeze technical scenario in SRM?VeryUrgent Pls

Hi SRM Guruu2019s,
What are the main points to freeze technical scenario in SRM?.
Please mention main points to select Classic Scenario and Extended Classic scenario individually.
I would really appreciate.
Regards,
John.
Edited by: johnmiller465 on Nov 12, 2009 3:30 PM

i believe what is your PPS version / SRM version
generally PPS works on EXtended Classic
http://wiki.sdn.sap.com/wiki/display/SRM/PPS-ProcurementforPublicSector-+enhancements#PPS-ProcurementforPublicSector-enhancements-PPSprocessisbasedinExtendedClassicscenario
Procurement for Public Sector - PPS1.0: An Overview
Ralf Wolfgang Geithner
Business Card
Company: SAP AG
Posted on Nov. 20, 2007 11:57 AM in Public Sector Subscribe
Print
Permalink
Introduction:
SAP PPS1.0 is an addon to SAP SRM5.0 addressing requirements of public sector procurement. SAP SRM is used as functional frontend to support the main procurement processes:
Public tendering
Awarding
Contract negotiation
Purchase order creation
SAP PPS1.0 has been designed to work in the extended classic scenario, where SAP ERP 2004 functions as backend supporting the processes:
Sales Order processing
Purchase Requisition processing
Goods Receipt processing
Invoice Receipt processing
Main Features:
PPS 1.0 features a couple of unique functions designed for the needs of public sector customers, namely:
Document Builder Integration
Records Management Integration
Smart document numbering
Funds Management integration
Acceptance at Origin
Central Contractor Registration (CCR)
Contract Tracking and Monitoring
Close Out Execution
Enhanced Versioning
FPDS Reporting
Guaranteed Minimum
Maximum Quantity per Period
Public Sector User Status
Reason Codes for Document Changes
Smart numbering of procurement documents
Selective Release
Sourcing Priorization
In the next couple of blog posts I want to describe the different features and give some guidelines for the implementation of the functionality.
What Next?
I plan to start with the smart numbering which is called as well "long procurement number"
Ralf Wolfgang Geithner is Senior Developer in Procurement for Public Sector core team

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

URGENT: advantages of scenarios in SRM

hi Everybody,
i want to know the advantages of technical scenarios like classic,extended classic,decoupled,standalone.....
why we r using these scenarios in SRM...........
pls let me know these wth suitable answers from ur side.so pls put an eye on this issues asap..............
warm regards
rakhi

Hi Rakhi,
SRM technical scenarios explain the possible variants how SRM can be deployed and used in integration with the backend system. The advantages can be outlined purely based on the business needs and their and process. Hence first outline your business needs then with that analyse which technical implementation would be ideal for your requirement.
At some cases Classic may be advantages and some other case it might not be. Hence this is completely dependent on your client/your business process.
Because this plays a key role in determining where the document gets created first (PO, Confirmation, Invocie etc).
More info on the scenarios at SDN wiki.
https://www.sdn.sap.com/irj/sdn/wiki?path=/display/srm/technical+scenarios&
Hope this answers your question.
Regards
Kathirvel

Hi all,i have some doubts about dis scenario

plz explain step by step about this scenario·
     1)Involved in two activities Monitoring and Production Support.
·     2)Actively and regularly involved in Load Monitoring of Daily, Weekly, and Monthly, Data Loads using Process Chains
·     3)Actively involved in Rectification of Load Failure Errors like Master Data Loads, Transaction Loads.
·     4)Supported the Client by providing Long-term solutions to the Tickets by doing Root Cause Analysis.
·     5)Monitoring of Info Packages and analyzing the reasons for frequent failures of Info Packages.

Hi,
Here, there are some responsibilities in Production System.
Answer for fist question is maintaining documentation (in ms word ) for all support related activities like
a) frequently occurred data load monitoring errors as part of process chains
b) how to analyze whether load is running for long time
c) what ever the tickets with proper priority we have to raise. ex: if a load cause affecting more reports , we have to raise p2 ticket . Depends upon the impact of loads on report availability.
Answer for second question :
In prod.support, we have to monitor info package groups or process chains because loads are automatized using pchains or ipgroups. . whenever a load failed as part of pchains or ipg's , we have to analyse the load why it is failed. Loads may be failed due to reasons like memory issues, attribute change run locking issues and sid issues etc.
Answer for third questions:
In perigreen ticketing tool, we can check tickets like system generated tickets and customer generated tickets . For example,. Tivoli tickets are system generated tickets because whenever pchain is not triggered or any process of pchain has failed, system automatically will raise the tickets.
Custom generated tickets means as part of daily loads, any failures happened, with proper priority ,we will raise the ticket to appropriate resolution groups. ( Incident management tickets )
Rms means Request management tickets are requests raised by client. For example if they want adhoc loads on the part of mexico markets, they will raise the Rm and sent it to the offshore queue.
Answer for fourth question:
We can maintain excel sheet, it comprises of what are the loads have failed with the error information as part of process chains or ipg's and maintain the logs for manual loads
daily how many loads are failed ,successful and what are the total loads , can check in RSMO.That information we can maintain in excel sheet.
Root cause Analysis is nothing but giving permanent solution to the frequent errors.
Ali.

Implementation ESS standard scenario

Hi,
I want to use the ESS Standard scenario for personal administration. I've read, that the Webdynpro-Applikation and the iView exists in the SAP Business Package. Now I ask to myself what I have to do, to use the application in the NetWeaver Portal. I think, I must edit the JCo connections, I must edit the iView's, what else?
Can you give me a short listing of the steps I have to do?

Hello Stefan,
When you say :
I want to use the ESS Standard scenario for personal administration
I hope you mean you wish to modify existing functionality of "personal Information" adapt it as per your use....right ?
Well you can personalize it as defined in SAP note 1234273.
Second you can make modification without any changes in code at Java level :
You can refer :
http://wiki.sdn.sap.com/wiki/display/profile/ESSPersonalInformationUIenhancementwithoutmodification
Third you can modify Java level code changes ...for that you need to refer below SAP note :
872892...in this note refer to NWDI.Zip attachment.
Additionally you can refer below forum thread....
ESS standard Application modification

EDI Standard used in SRM-SUS for Purchaser - Vendor Document Exchange?

Hi Forum,
For exchange of electronic documents like ASN, PO, PO Response, Confirmations etc. between buyer and seller, which EDI standard is used in SRM-SUS?
Say there are two different vendors one from North America using ANSI X 12 as EDI Standard and other from Europe using EDIFACT, how is the document exchange handled for these two different seller / edi standard in same SUS system?
Thanks,
Anubhav

Hi,
I am not sure what standard SAP uses, but it is not really relevant. At least not for the SUS scenarios. The IDOCs from ECC will be sent to the PI system which will convert them to XML format and send it to the SUS system. Since both PI and ECC system are from SAP, they will speak the same EDI standard for sure.
For SUS we have two scenarios, SRM-SUS and MM-SUS. In SRM-SUS the PO is created in an SRM system locally and sent to SUS. All communication will take place between these two system via XML messages on both sides (of course a PI system is mandatory in this case as well).
In the MM-SUS scenario the PO will be created in ECC and transferred to SUS. Depending on ECC release there are two different possibilities for this, either the ECC system sends EDI IDOCs or it sends XML messages directly. IDOCs will be mapped to XML by PI in all cases, as the SUS system will always receive and send XML messages only.
regards
Zoltan

Scenario in SRM

Hi
Please suggest how to find out that customer hase created PO in which scenario either classic, extended classic or local.
Thanks
Preeti Khurana

Hi,
How about BBP_PD transaction?
If there is no PO in SRM -> Classic
If there is PO in SRM -> Extended Classic or Local
Check the document status in BBP_PD. If there is status transfered or transfer is failed, It is Extended Classic.
Regards,
Masa

BBPSC18 - Request for external staff - Classic Scenario in SRM 5.0 possible

Hello Community,
one of my customers wants to use "Reqest for External Staff". As far as I remember, in SRM 5.0 it is only possible in "Standalone Scenario".
Is this assumption correct? So not possible in Classic Scenario?
How about "Extended Classic"? Probably not possible either, right?
Thanks for any help or input!
Cheers, Julian

Hi Rahul,
thanks for your answer!
Actually I am only looking into the part "Request for External Staff" - "Acceppt Bid" - "Create PO (Classic in ERP)".
I have seen that this part works in SRM 7.01.
But currently we are not planning to upgrade. We are still on 5.0.
I tested the abovementioned process in our DEV-System. I behaves fine, no error messages. But when I want to create the PO out of the "Check Status" (yes, in SRM 5.0 this was possible), the system pretends to create a PO but it never gets created. So I just wonder if I missed some customizing, or if this also only works in Standalone or if there maybe is a smart technical workaround (some custom coding etc...).
Cheers, Julian

Doubts about BP number in SRM and SUS

Hello everyone,
I have some doubts about the BP number, especially for Vendors.
I am working with the implementation of SRM 5.0 with SUS in an extended classic scenario. We will use one server for SRM and other for SUS. We will use the self registration for vendor (in SUS). My questions are:
- Can I have the same BP number in SRM and SUS?? Or is it going to be different??
- When a vendor accesses at the site to make a self registration in SUS, the information is sent to SRM as prospect (by XI) and there the prospect is changed as vendor? After that, is it necessary to send something from SRM to SUS again? (to change the prospect to vendor)
- When is it necessary to replicate vendors from SRM to SUS??
Thanks
Ivá

Dear Ivan,
Here is answer to all your questions. Follow these steps for ROS configuration:
Pls note:
1. No need to have seperate clients for ROS and SUS. Create two clients for EBP and (SUS+ROS).
2. No need of XI to transfer new registered vendor from ROS to EBP
Steps to configure scenario:
1. Make entries in SPRO --> "Define backend system" on both clients.
    You will ahev specify logical systems of both the clients (ROS as well as EBP)
2. Create RFCs on both clients to communicate with each other
3. In ROS client create Service User for supplier registration service with roles:
    SAP_EC_BBP_CREATEUSER
    SAP_EC_BBP_CREATEVENDOR
    Grant u201CS_A.SCONu201D profile to the user.
4. Maintain service user in u201CLogon Datau201D tab of service : ros_self_reg in ROS client
5. Create Purchasing and vendor Organizational Structure in EBP client and maintain necessary
    attributes. create vendor org structure in ROS client
6. Create your ROS registration questionnaires and assign to product categories- in ROS client
7. To transfer suppliers from registration system to EBP/Bidding system, Supplier pre-screening has to be
    defined as supplier directory in SRM server - EBP client.
    Maintain your prescreen catalog in IMG --> Supplier Relationship Management u2192 SRM Server u2192
    Master Data u2192 Define External Web Services (Catalogs, Vendor Lists etc.)
8. Maintain this catalog Id in purchasing org structure under attribure "CAT" - in EBP client
9. Modify purchaser role in EBP client:
    Open node for u201CROS_PRESCREENu201D and maintain parameter "sap-client" and ROS client number
10.Maintain organizational data in make settings for business partner
Supplier Relationship Management -> Supplier Self-Services -> Master Data -> Make Settings for the Business Partners. This information is actually getting getting stored in table BBP_MARKETP_INFO.
11. Using manage Business partner node with purchasers login (BBPMAININT), newly registsred vendors are pulled from Pre-screen catalog and BP is created in EBP client. If you you have SUS scenario, ensure to maintain "portal vendor" role here.
I hope this clarifies all your doubts.
Pls reward points for helpful answers
Regards,
Prashant

Standard Scenario?

I've got zero experience with KM so, sorry for the newbie question but I need to know if this scenario is achievable using standard tools:
1 - Creation/upload of document in some folders needs to go through an approval process. Each folder has a person who is responsible for approval. The document is only visible to other users after approval.
2 - People with write permission in the folder can checkout document, upload a new version. KM retains different versions.
3 - People subscribe to folders and receive notifications for new documents, or new versions of existing documents.
After reading the help for NW 04 I believe this is available, but I want to confirm that it is achievable in EP 7.0.
Thanks in Advance.

Hi
the points what u had mentioned are all scenerios of KM.
After reading the help for NW 04 I believe this is available, but I want to confirm that it is achievable in EP 7.0.
if u want to know in general about these functionalities in EP 7 then in your browser replace nw04 with nwo4s or nw07 then u can browse the same scenerio with different version of ep.
i hope u r following help.sap.com
note nw04s=nw07
I've got zero experience with KM so, sorry for the newbie question but I need to know if this scenario is achievable using standard tools:
everybody is newbie at the begining but what i found good is that u had taken effect to read the scenerio and post the question here
if u have any further queries with the scenerio u r most welcome
Regards,
Vijay.

About standard scenarios on SRM

Similar Messages

Maybe you are looking for