on 04-01-2008 10:17 AM
Hi!
We have an extended classic scenario already up and running between ERP->EBP system without XI usage. We are using BBP_EXTREQ_TRANSFER report. And we would like to Configure SUS system to make Suppliers able to see Sales Orders and create Confirmations and ASN for them.
Could anybody please tell me whether it is possible w/o XI usage? Or whether it is possible not to make harm to existed configuration if we will use XI for EBP->SUS and SUS->MM integration?
Thanks and Regards,
Siarhei
Hello,
By solution design SUS will only accept dat in XML.
Hence XI becomes mandatory for MM <--> SUS set up.
You will have to define various integrating parameters for XI
such as RFCs to integration server from the resp systems
integration repository and import the business scenarios in integration server.
XI consultant would be required for this job
BR
Dinehs
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you!
But what I also would like to know whether it is possible not to change configuration for extended classic scenario that we have done? Because now it is working w/o XI. And if I need XI for SUS integration how can I activate XI integration for EBP->SUS w/o any chnages for EBP->ERP integration?
Thanks and Regards,
Siarhei
hi,
there is no need to change any of the exisiting configurations between EBP-ERP.
there is no direct communication between ERP and SUS.
if you want to start using EBP-SUS scenario , you need to download Service_integration scneario in XI.
you need to follow the config guide and the master guide for the details.
Purchase order is the starting point for the SUS integration
so in your case
1) external requirement comes to sourcing.
2) You should use an supplier which is SUS-enabled for the creation of the purchase order.
3) purchase order will go to SUS -->and the vendor user will send the responses.
But also keep in mind , if you want to use SUS is ECS , there are many restrictions -->
please refer to the OSS note --->
Note 543544 - SUS: Extended Classic Scenario for EBP not supported
please also refer to OSS note --> 700350
Edited by: khan voyalpad usman on Apr 1, 2008 11:30 PM
Ok, as I can see in note 836200 it is no need to configure XI fully manually, but first it is necessary to import relevant Process Integration Content?
One additional question - now PO created in EBP and copied to ERP on 'Create PO' button in EBP system. How will PO go to SUS to create SO there?
Thanks and Regards,
Siarhei
Edited by: Siarhei Tsikhanenka on Apr 1, 2008 1:52 PM
Hi,
XI is mandatory component on the design of SUS and MM/EBP. Since the document exchange is done through XML.
But i wont say there no solution for it. Since there are few application in our business process running without XI (even though it is mandatory in SAP Design). This is our custom build application.
Cheers, Renga
***Award points for helpfull answers***
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you talking about ALE configuration? Will it not make harm to existed integration between EBP and ERP systems?
BR,
Siarhei
Edited by: Siarhei Tsikhanenka on Apr 1, 2008 2:22 PM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Khan!
Could you please add some more clarifications:
- whether XML message should go to XI system from EBP or ERP?
- if PO transferring to XI from EBP, could you please tell me how can I activate XML messages creation for POs in EBP?
Some words about scenario and goals:
-the main goal is to make suppliers able to create ASN from SUS. So I can see that SUS-MM scenario is relevant for us. Could you please tell me whether SAP plug-in installation is required in this case? And also whether it is technically possible to make this integration for extended classic scenario?
Thanks and Regards,
Siarhei
Edited by: Siarhei Tsikhanenka on Apr 2, 2008 2:24 PM
find the answers
1) XML message will go from EBP to SUS.
2) Number of settings needs to be done to enable XML message transfer
1) activate XI on both your EBP and SUS
2) output control for the vendor in EBP should be XML
3) content is available in XI with the required routing.
-
if you plan to use MM-SUS , there will be no EBP involed , direct flow of orders from MM to SUS
XI is mandatory for both the scnearios
EBP-SUS and MM-SUS
In EBP-SUS --> XML message goes to SUS through XI
In MM-SUS --> idoc is converted to XML by XI and send to SUS.
please refer to the OSS note 573383 to get more details about the deployment options.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Good, thank you!
BTW have any documention about this that could be more helpful that I have found on Service Market Place?
Thanks and Regards,
Siarhei
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.