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

Similar Messages

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-SUS for Service Entry Sheets - Classic Scenario

Hi SRM Gurus,
Our client wants to use SRM-SUS for the Service Entry Sheets (to being with and then later expand more in other SRM areas). The lead system will be R/3 system.
We will be going with ECC 6.0 and SRM 5.0.
Service Order will be created in R/3 and replicated into SRM (SAP have said this is new functionality in SRM 2007 and SAP will provide us with this functionality in SRM 5.0 as well)
SAP are also recommending using MDM for hosting the catalogs for service entry sheets to enable vendors to selete their items during the confirmation / filling the service entry sheets. - they say this is mandatory
SAP are also asking for XI for the data to be transferred from R/3 to SRM (and may be vice versa) - they say this is mandatory.
Few questions:
1) What kind of hardware size are we talking about to have SRM-SUS, MDM, XI and Portal (PI)
2) Are MDM and XI mandatory as said by SAP and if yes, in what scenarios. What is they way around
3) How good is the functionality provided by SRM-SUS for Services? Is it as good as in R/3 (or even better)? We will be having complex Services in our scnearios.
4) What can be a typical time to install SRM-SUS, MDM, XI and Portal in the Dev environment to get moving onto the project?
An early response shall be highly appreciated.
Thanks in advance
Regards
Rahul

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

MM-SUS for the extended classic scenario

Hi,
I have done SUS-MM for the classic scenario.
Did anyone implement SUS-MM for the extended classic scenario ?
Did you face any problem or will it be same as 'classic' scenario ?
Please help
Thanks
Pranav

There shouldn't be any problem especially when the scenarios are concerned. Since the PO's moves from MM-SUS.
Regards, IA

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

Sourcing of GOA in Extended Classic Scenario

Hello all,
We are using the <u>extended classic scenario</u> with both Purchase Contracts and Global Outline agreements.
Is it possible to use the GOA in the back-end as a source of supply in the sourcing transaction in SRM? What setting do I have to use exactly?
Kind regards,
sander

Hi
Which SRM and R/3 versions are you using ?
I guess, the following threads will help.
<b>Source determination in backend (R/3) for distributed contract i.e. GOA
Transaction For Creating GOA
Distribution of GOA in R/3
FM or BADI s' used to create a GOA
GOA Distribution SRM 5.0-ECC 6.0 - Account Category & Multiple Distribution
Hope this will help.
Please reward full points, incase it suits your requirements.
Regards
- Atul

Tolerance key DQ in extended Classic scenario give Backen error message

Dear all,
I am using SRM 7.0, SP 9
Extended Classic Scenario.
I created a tolerance group and attached it to my user via TOG attribute in PPOMA_BBP. Tolerance key is DQ with $1000 and upper percentage 5%.
I also set up the ECC tolerances:
- Purchasing Value key with Tol. Overdelivery = 5.0 (in SPRO --> MM --> Purchasing --> Material Master --> Define Purchasing Value Keys)
And assigned that Purchasing Value Key to the material group I am using (via SPRO --> MM --> Purchasing --> Material Master --> Entry Aids for Items Without a Material Master)
- And I even set up tolerance key B1 (for error message) for my Company Code (in Spro -> MM --> IM and PI --> GR --> Set tolerance limits) with a upper limit of 5%
And even with this set up I still get the error message
u201CBackend Purchase Order quantity exceeded by 1 EAu201D
when I try to post a Confirmation with an overdelivery, even if the over delivery is only 0.1% of the total quantity 1000.
What Configuration am I missing?
Cheers
Ulrike

Dear Rahul,
Thanks for you input
Let me give you an example of the behaviour:
in PPOMA_BBP TOG assigned to user has : DQ with $1000 and upper percentage 5%.
User orders a PO with quantity=1000, price $100;
No additional tolerances assigned in the PO itself
User tries to enter confirmation with quantity 1001 (so qty variance converted to currency amount results in $100 over delivery) So the confirmation is under both the 5% and the $1000 limit.
In that case I donu2019t receive an error message from the SRM, but the error message u201CBackend Purchase Order quantity exceeded by 1 EAu201D from ECC still prevents me from posting the Confirmation. And this is the problem I havenu2019t been able to solve so far.
So I want the TOG tolerance to be used. And I am also happy with the absolute limit always having priority over percentage limit...
But I am trying to find a way to get rid of the back end message (with assigning a tolerance to the PO itself as the will get rid of the absolute limit see my previous post.)
Cheers
Ulrike

Extended classic scenario - PO print output

Hi all,
Please help me. We have SRM 5.5 (SAPKIBT11) the extended classic scenario.
Could you please tell me Can I print the PO from Web GUI?
If in the Web GUI Output area in PO I set indicator Printer, and to set in Output Pushbutton, in Log I have status - Successfully processed. In trx SP01 the spool status - Compl. But the PO smartforms don't print.
PS: from Output Preview button I can to print the PO smartforms, but I need to print from Output area through the Output Pushbutton. (in the trx BBP_POC or BBP_PPF).
Best regards
Guzal.

Hi, Masa,
Thank you for your advice,
I set the method U:Print Using Berkeley Protocol, after that
in trx. SP01 I have the Error Status on Composite Document -
Status Incorrect (Reason Unknown).
Best regards,
Guzal.

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

Can we use the Extended Classic Scenario with MM-SUS

HI, expert :
    In extended classic scenario ,the PO created in SRM system ,and then replicated into the MM system .You can't change it in MM system .
    So, in this situation ,I want to know the MM-SUS can be suitable or not ?The PO can transfer from ECC to SUS ?
   If I use the decoupled scenario ,which one I can select ?MM-SUS or EBP -sus ?
   BR !
Alex!

Hi Alex,
as noted by Bill, in MM-SUS is the extended classic not possible at all.
By default it's also not supported in the SRM-SUS. Please see the note 543544. If you would like to activate this, you need to pay a consulting fee for SAP:
"Please note that the full scenario can be enabled by a consulting solution, compare OSS note 700350."
Regards,
Peter

Use the MM-SUS in Extended Classic Scenario

HI,my experts :
    The standard function doesn't support the MM-SUS in Extended Classic Scenario .Now I may have two questions about it .
1、 I have one ECC system .I need handle the invice in the ECC system .In other word ,the invoice rcreated in the SUS should transfer to the MM system .But in EBP-SUS ,the invoice is transfered to the SRM system .What can I do now ?
2、 If I want to use the decoupled scenario ,some POs are create in EBP ,and others are created in MM .Now ,which sus I should select ? EBP-SUS or MM-SUS?
   Or some detail document about it .
BR!
   Alex!
Edited by: Alex on May 25, 2010 9:17 AM

Khan has explained most of the things.
The external web service I meant is actually OPI catalog which you need to maintain.
The same has to be entered in the attribute CAT of the EBP purchaser.
To maintain the call structure of this catalog
Get the URL from SE80->BSP appln->ros_prescreen->controller->main.do
then give the client no of yr ROS client
the RFC user user ID from EBP to ROS
it's password
sap-sessioncmd=open
sap-language=sy-langu
the operational purchaser role in EBP (sap_EC_BBP_OP_PURCHASER) should be linked with
the same in ROS via role menu->business partner->screen supplier->right click->change details
->sap-client=ROS client no
The administrator & op purchaser should be present in ROS org structure also
& should have same userID & password as EBP
you have to define the vendor root, the root of the purchasing organization and the currency in
table BBP_MARKETP_INFO in the SRM System (Enterprise Buyer client).
BR
Dinesh

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.

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

Material PO confirmation at supplier side (SUS) not taking place in SRM SUS Extended classic scenario

We have configured extended classic scenario SRM with SUS, and all functions are working fine. However, at the time of PO confirmation of material item at the Supplier side (SUS), the material line item disappears when we click on the Create Confirmation button in SUS. The functionality is working fine for Service Items. The total value of PO is also displayed correctly in the Items overview section.
Please provide some help in solving this issue.

Hello,
This is the correct behaviour of SUS - confirmations can only be created for service items which in turn create service entry sheets (Trx: ML81N in ECC). And accepting the SES in ML81N will generate GR posting.
For material items, you have to create ASN which will in turn create inbound delivery in ECC which you can post and will generate goods movement documents.
So basically, for service items you create confirmation and for materials you create ASN.
Regards,
Prasanna

SUS / no goods receipt doc to backend in extended classic scenario?

Hello
have you any find a solution for problem
in SRM/SUS and goods receipt in extended classic scenario. Gr remains only in SRM not going to backend...
Brg Harri
Message was edited by: Harri Harkonen
Message was edited by: Harri Harkonen

Hi Christophe,
We also have this issue. Goods Receipt from SUS is created in SRM but is not posted in backend (we have implemented extended classic scenario).
I tried to use the BBP_DOC_SAVE_BADI to created an idoc which posts the material document in backend system (using fm IDOC_GR_CREATE).
The goods receipt is posted in backend this way.
Unfortunately we are not able to cancel or make a return delivery on this GR.
I am very interest in your FM. Could you please share this, or tell me what changes you made to the GR in SRM.
Thanks in advance.
Rgds,
Martijn

SRM SUS using PI in Extended Classic Scenario

Similar Messages

Maybe you are looking for