SRM-XI-SUS Integration issue.

hi
Anyone help me in SRM-XI-SUS Integration.
My Requirement is
1)       Purchase Order
2)       Confirmation
3)       Shipping Notification etc. from SRM to SUS Through XI.
Please it is urgent.
Thanks

Kalam,
Check this thread for various questions on this integration:
https://www.sdn.sap.com/irj/sdn/advancedsearch?query=srm-xi-sus%20&cat=sdn_all
---Satish

Similar Messages

Help me in SRM-XI-SUS Integration .

hi
Can anybody Send me Complete Procedure for SRM-XI-SUS Integration.
Thanks

HI
Refer this realtive thread from jin shin
Re: Http server code 401 reason Unauthorized explanation Unauthorized

SRM-PI-ECC Integration issue

Hey All
There is some issue coming in Central Contact management scenario.
SRM 7.0
ECC 6.0 EHP 4
PI
*below is the error details we get in SXMB_MONI of SRM Sytem* <REMOVED BY MODERATOR>
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIProtocol</SAP:Category>
<SAP:Code area="PARSER">ITEM_UNEXPECTED</SAP:Code>
<SAP:P1><></SAP:P1>
<SAP:P2><Fault></SAP:P2>
<SAP:P3 />
<SAP:P4>ST: ST_XMS_MSGHDR30_SOAP_FAULT</SAP:P4>
<SAP:AdditionalText>System expected the element 'Fault'</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Unexpected XML element <>; <Fault> was expected System expected the element 'Fault'</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Thanks
Narender
Edited by: Prateek Raj Srivastava on Mar 5, 2011 4:49 PM

Thanks Buddy.
We have some progress. Now data passed from SRM to PI and now stucked in ECC. The XML file in SXMB_MONI in ECC, shows the staus "Transfer to External Application" and in ECC SMQ2 Queue XBQRCCR4400000066 stucked with status "STOP".
While dubugging the relevant we are getting the error '"COMMNICUTION_FAILURE"
And the Payload .xml file is as below :
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SOAP:Header>
- <SAP:Main xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" versionMajor="003" versionMinor="000" SOAP:mustUnderstand="1" wsu:Id="wsuid-main-92ABE13F5C59AB7FE10000000A1551F7">
<SAP:MessageClass>ApplicationMessage</SAP:MessageClass>
<SAP:ProcessingMode>asynchronous</SAP:ProcessingMode>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:TimeSent>2011-03-11T07:14:32Z</SAP:TimeSent>
- <SAP:Sender>
<SAP:Service>SS1CLNT200</SAP:Service>
<SAP:Interface namespace="" />
</SAP:Sender>
- <SAP:Receiver>
<SAP:Party agency="" scheme="" />
<SAP:Service>ES1CLNT200</SAP:Service>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Receiver>
<SAP:Interface namespace="http://sap.com/xi/APPL/Global2">PurchasingContractSRMReplicationRequest_In</SAP:Interface>
</SAP:Main>
- <SAP:ReliableMessaging xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:QualityOfService>ExactlyOnceInOrder</SAP:QualityOfService>
<SAP:QueueId>CCR4400000066</SAP:QueueId>
</SAP:ReliableMessaging>
- <SAP:HopList xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="BS">SS1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:32Z" wasRead="false">
<SAP:Engine type="IS">is.01.auvimel00s971</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
- <SAP:Hop timeStamp="2011-03-11T07:14:33Z" wasRead="false">
<SAP:Engine type="BS">ES1CLNT200</SAP:Engine>
<SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
<SAP:MessageId>E04BAF35-8357-83F1-82AD-005056A12FA9</SAP:MessageId>
<SAP:Info>3.0</SAP:Info>
</SAP:Hop>
</SAP:HopList>
- <SAP:RunTime xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SAP:Date>20110311</SAP:Date>
<SAP:Time>181433</SAP:Time>
<SAP:Host>AUVIMEL00S962</SAP:Host>
<SAP:SystemId>ES1</SAP:SystemId>
<SAP:SystemNr>00</SAP:SystemNr>
<SAP:OS>Windows NT</SAP:OS>
<SAP:DB>MSSQL</SAP:DB>
<SAP:Language />
<SAP:ProcStatus>003</SAP:ProcStatus>
<SAP:AdapterStatus>007</SAP:AdapterStatus>
<SAP:User>RFCUSER</SAP:User>
<SAP:TraceLevel>1</SAP:TraceLevel>
<SAP:LogSeqNbr>001</SAP:LogSeqNbr>
<SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
<SAP:PipelineIdInternal>SAP_RECEIVER</SAP:PipelineIdInternal>
<SAP:PipelineIdExternal>RECEIVER</SAP:PipelineIdExternal>
<SAP:PipelineElementId>1DC6B93B44BBA66BE10000000A1148F5</SAP:PipelineElementId>
<SAP:PipelineService>PLSRV_CALL_INBOUND_PROXY</SAP:PipelineService>
<SAP:QIdInternal>XBQRCCR4400000066</SAP:QIdInternal>
<SAP:CommitActor>X</SAP:CommitActor>
<SAP:SplitNumber>0</SAP:SplitNumber>
<SAP:NumberOfRetries>0</SAP:NumberOfRetries>
<SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
<SAP:TypeOfEngine client="200">SND_CENTR</SAP:TypeOfEngine>
<SAP:PlsrvExceptionCode />
<SAP:EOReferenceRuntime type="TID">AC1E020C11E44D79CBD9E0A7</SAP:EOReferenceRuntime>
<SAP:EOReferenceInbound type="TID" />
<SAP:EOReferenceOutbound type="MSGID">E04BAF35835783F182AD005056A12FA9</SAP:EOReferenceOutbound>
<SAP:MessageSizePayload>2929</SAP:MessageSizePayload>
<SAP:MessageSizeTotal>11916</SAP:MessageSizeTotal>
<SAP:PayloadSizeRequest>2929</SAP:PayloadSizeRequest>
<SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
<SAP:PayloadSizeResponse>258</SAP:PayloadSizeResponse>
<SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
<SAP:Reorganization>INI</SAP:Reorganization>
<SAP:AdapterInbound>IENGINE</SAP:AdapterInbound>
<SAP:AdapterOutbound>PROXY</SAP:AdapterOutbound>
<SAP:InterfaceAction>DEL</SAP:InterfaceAction>
<SAP:RandomNumber>57</SAP:RandomNumber>
<SAP:AckStatus>000</SAP:AckStatus>
<SAP:SkipReceiverDetermination />
</SAP:RunTime>
- <SAP:PerformanceHeader xmlns:SAP="http://sap.com/xi/XI/Message/30">
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.211</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="ADAPTER_IN">INTEGRATION_ENGINE_HTTP_ENTRY</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.256</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.257</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.274</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="DBQUEUE">DB_ENTRY_QUEUING</SAP:Name>
<SAP:Timestamp type="end" host="AUVIMEL00S962">20110311071433.387</SAP:Timestamp>
</SAP:RunTimeItem>
- <SAP:RunTimeItem>
<SAP:Name type="PLSRV">PLSRV_CALL_INBOUND_PROXY</SAP:Name>
<SAP:Timestamp type="begin" host="AUVIMEL00S962">20110311071433.39</SAP:Timestamp>
</SAP:RunTimeItem>
</SAP:PerformanceHeader>
- <SAP:Diagnostic xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:TraceLevel>Information</SAP:TraceLevel>
<SAP:Logging>Off</SAP:Logging>
</SAP:Diagnostic>
- <SAP:System xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Record namespace="http://www.sap.com/webas/712/soap/features/runtime/metering/" name="CallingType">SA</SAP:Record>
</SAP:System>
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/XI/engine/?type=entry</Trace>
<Trace level="1" type="T">Work Process ID: 4580</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = E04BAF35835783F182AD005056A12FA9</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EOIO</Trace>
<Trace level="1" type="T">Queue-Id = CCR4400000066</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBQRCCR4400000066</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBQRCCR4400000066</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start determination of sender interface action</Trace>
<Trace level="1" type="T">select interface</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">--start determination of receiver interface action</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface PurchasingContractSRMReplicationRequest_In</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/APPL/Global2</Trace>
<Trace level="1" type="T">--no interface action for sender or receiver found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Work Process ID: 2348</Trace>
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">----
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC">
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">ROLLBACK WORK requested by application</Trace>
</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">Async processing completed OK.</Trace>
<Trace level="1" type="T">system-ID = ES1</Trace>
<Trace level="1" type="T">client = 200</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RFCUSER</Trace>
<Trace level="1" type="Timestamp">2011-03-11T07:14:33Z AUSVIC</Trace>
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
</SOAP:Header>
- <SOAP:Body>
- <SAP:Manifest xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7">
- <SAP:Payload xlink:href="cid:payload-E04BAF31EF9CE7F189DE005056A10467sap.com">
<SAP:Name>MainDocument</SAP:Name>
<SAP:Description />
<SAP:Type>Application</SAP:Type>
</SAP:Payload>
</SAP:Manifest>
</SOAP:Body>
</SOAP:Envelope>
Can anyone suggest what can be issue ?
Thanks
NAP

EBP - SUS integration

Hi experts,
I m new to SRM5.0. Can any one explain me abt EBP-SUS integration? Wt is the need of this integration? wt r the prerequisites to this? I m using EBP4.0 and SRM5.0.
Kindly help me on this.
Regards
Raaams.

hi,
in EBP -SUS scenario --> three systems are involved.
1) EBP(SRM) System ( CLIENT xxx)
2) SUS System ( CLIENT yyy)
3) XI System ( CLIENT zzz).
EBP(SRM) system client can be on the same server as SUS System client.
It is also possible to have these SRM (EBP) and SUS Clients on different servers.
It is also possible to have one client scenario ( EBP and SUS ) in the same client , But SAP Recommends this not to be used for productive use and to be used for demo purpose.
XI system is required to integrate SRM and SUS , this is to transfer documents ( in the form XML Messages ) from one system to another.
proxies are used in this scenario.

SRM and XI Integration

hi,
can anyone provide me some good links,docs and blogs about SRM XI integration please.
and what would be the scenarios with SRM integrations?I mean are they like
SAP SRM -XI-R/3(or ECC)
SAP SRM -
XI----non SAP systems(i have read onb sdn SUS,EBS systems)
non SAP---XI---SAP SRM
SAP r/3(or)ECC--XI--SAP SRM?
what we need to use on SRM side (sender/Receiver)are they Idocs/RFC/proxies?and what we need to use on SAP R/3 side and thirdparty systems?
please clear me?
thank you,
babu

Hi Babu
SAP deliver a lot of XI contents for SRM.
For this have a look at service.sap.com/xi --> Business content --> SAP XI Content --> XI content delivered by SAP --> mySAP SRM
Also refer this realtive thread from jin shin
Re: Http server code 401 reason Unauthorized explanation Unauthorized
There are business package available for the standard SRM and XI integration. For this you can download from the service market place and you can make use of the standard SAP delivered objects.
Most of the time senario involves Idoc/RFC and Proxy here
Some of the docs from SAP service market place are-
go to https://websmp101.sap-ag.de/ibc -
>mySAP SRM-->and search
http://service.sap.com/~sapidb/011000358700002897342004E/CCMConfig10_01_05.pdf
http://service.sap.com/~sapidb/011000358700003992672005E/Config_Guide_CCM200_640doc.pdf
http://service.sap.com/~sapidb/011000358700002897402004E/ServiceProcurementNEW.pdf
http://service.sap.com/~sapidb/011000358700002897382004E/Plan-DrivenwithSInew.pdf
Cheers..
Vasu
Reward Points if found useful **

Reports 6i and WeBDB 2.2 Integration Issues

1. I have installed reports6i andintegrated with WebDB 2.2 by running the fo
llo
wingScripts:
oracle_home\report60\server\security\rwwwvins.sql webdb and
\oracle_home\report60\server\security\rwenable.sql
as described in the webdb& reports6i integration issues document in oracle r
epo
rts6i beta site.
Afterinstalling, when i logged to webdb as webdb user, i was able to see sev
er
access and rdf access options in webdb 2.2
However, when i log as an userwhere i have created forms components i am una
ble
to access the abovecomponents. (there is no documentation on what privileg
es
needs to be providedto the user., however i had given grants to following ro
les
withRW_ADMINISTRATOR, RW_POWER_USER, RW_DEVELOPER AND RW_BASIC_USer
null

Hi Matt,
You didn't mention but do you also wish to install the database(8i) on the same machine ?
I am also trying to install all these products(+8i and designer 6i) on the same box but I am concerned more about the min. resources needed before I get started.(I put up a question about it on the 6i Forum, but nobody has answered yet !)
The correct install order should be Forms/Reports 6i then Forms/Reports 6i Server and then WebDb 2.2.
Forms /reports server needs a http listener and installs en configures the WebDb listener for the job.(you are prompted for this during tho have the install process).This is handy if you are intending to use WebDb anyway. When you install Webdb it detects the already installed WebDb listener and does not reinstall.
You do have the SYS password on the database you will use to stored the WDK and WebDb schema.
About installing the demo.....
I dont' think there are any special issues.I have never done it.
If you are intending to install an 8i database on the same box there are some important things to consider with respect to the install order and what products in which Oracle home must be installed.
1.Forms/Reports first in the default_oracle
home.
2.Then Oracle 8i in a 2nd oracle home call
it ora81 for example.
3.Then WebDb in the non oracle 8i home !!
This is just a quick summary.
If you run into any problems let me know
Good Luck.
Dave.

OIM - SOA 11g R1 Integration Issue

Hi ,
I am facing an integration issue in my newly set up Dev environment .
We have single node OIM and SOA environment . I was executing the basic connectivity checks to ensure that the environment is good and ready for use .
When I ran the SOA-OIM Configuration test (http://i.tinyuploads.com/M1zyaP.jpg ) in the environment from Diagnostic Dashboard, it failed .
I have verified the URLs from EM and also in MDS (in oim-config.xml) file . All entries seem to be there , not sure why its failing ? Any pointers ??
I have checked the rmi and soap urls here Application Defined MBeans ->oracle.iam->Server (OIM ServerName)->Application:oim->XML Config->Config->XMLConfig.SOAConfig->SOAConfig and they looked perfectly fine .
Any clues ??
Regards
Suren

did you tried accessing the oim and soa urls:
1. http://<hostname>:<port>/oim (login with xelsysadm user)
2. http://<hostname>:<port>/soa-infra (login with weblogic user)
Are you able to login to both urls.

Vendor replication and exchange documents from SRM to SUS (using PI)

Hi Gurus,
We are implementing scenario plan driven procurement with suppllier collaboration on SRM 7.0.
Our architecture involve:
A server machine with SRM 7.0 (SRM server and SUS components both in this machine)
A server machine with Netweaver PI 7.0
A server machine with EP 7.0
A server machine with SAP R/3 4.6C
Now we are working on vendor replication process in order to carry out vendors from R/3 to SUS (on portal enviroment) and we made following steps:
- Replication of vendor from R/3 to SRM by mean tx BBPGETVD: OK
- Replication of vendor from SRM to SUS (on portal enviroment) by mean tx BBP_SP_SUPP_INI:
In this step we put the BP (created with tx BBPGETVD) on field "Supplier" but we obtained the Message no. BBP_XP004
"No vendor allowed for vendor portal"
So we want to know, in connection with mentioned architecture, the way to perform this activity in order to replicate the suppliers in SUS.
Is possible perform activities related to exchange documents (by mean Netweaver PI) between SRM and SUS (as necessary for our implementation scenario) if these mentioned components are installed and configured on the same phisical server machine?
What is the best recommendation about installation of SRM and SUS? A unique server machine or separated server machines?
Is there any inconvenience or technical reason having SRM and SUS in the same server machine?
Thanks in advance.
Regards,
Horacio

Hi Nikhil,
Thanks for your soon response.
Our process involve PR and PO manual creation in MM and then PO (with ALE message type) is routed to a supplier in SUS via XI. We could achieve that steps succsesfully.
We don´t have in scope neither use SRM for sourcing nor PO creation (via IDOC) in MM.
In connection with my previous explanation; Would you say that our process is MM-SUS?.
If yes, can I follow the steps mentioned in below link described at point u201CProcess Flow Without Supplier Registrationu201D?. What´s the difference between creating and replicating bussiness partner data?.
http://help.sap.com/saphelp_srm40/helpdata/en/c0/7a0859ee91d54aa48a69fb5d2c4089/content.htm
Thanks in advance.
Regards,
Horacio

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

SRM B2B - OCI integration.

Hellow Team,
We are implementing SRM B2B - OCI integration to a third party intenet order system. We are planning to use the add on component of SRM server in ECC6.0 ( integrated SRM server).
Please let me know if any body done this kind of integration using the integrated SRM server.
Any inputs and suggestions for this kind of integration will be very much appreciated.
Thanks in advance,
Best regards,
Madhu

Hi Rafael,
The ISA Development and extension guide talks about OCI. I've also seen a printout of some info from help.sap.com about how to use OCI but don't have a link to it unfortunately.
Thanks,
Gareth.

Photoshop Fill - A major integration issue?

For the first time in a production environment, I was ready
to use FW CS3 to slice and dice a colleague's PSD. I opened it in
Photoshop and then in Fireworks for comparison - the two looked
nothing alike.
This particular colleague likes to take advantage of PS's
Fill setting (as opposed to opacity and I can understand why in
certain situations) - but Fireworks has no understanding of this
Fill concept so every layer that uses it is darker in FW. So what's
a guy to do?
Is this a known integration issue? Will there be a solution
for CS4? Can I wait that long? Is it ever really worth trying to
open a PSD in Fireworks?
I'm more than a little disappointed...
Matt
Firewoiks

I haven't tried this yet, but here's a thought:
PS is layer based, FW is object bases. As a result, in FW you
can
control the opacity of layers AND objects. Is it similar
enough to
Photoshop's Fill and Opacity in a layer? Maybe adjusting the
opacity of
the object will get you what you need? It might impact the
stroke on the
object, but you could possibly duplicate the object and
remove/mask it's
fill, so the solid stroke remains.
It's a workaround, and a bit more work, but it might solve
the problem
for now.
Jim Babbage - .:Community MX:. & .:Adobe Community
Expert:.
Extending Knowledge, Daily
http://www.communityMX.com/
CommunityMX - Free Resources:
http://www.communitymx.com/free.cfm
.:Adobe Community Expert for Fireworks:.
news://forums.macromedia.com/macromedia.fireworks
news://forums.macromedia.com/macromedia.dreamweaver
Stowball wrote:
> Linda
>
> The problem is not caused by any colour mode or embedded
profiles - it's
> caused by Fireworks' lack of support for Photoshop's
Fill feature.
>
> The Fill feature is useful, because you can change the
opacity of the actual
> fill, without changing the opacity of any effects - like
strokes - that are
> applied to the layer.
>
> My colleague uses this method frequently in his his
designs.
>
> This PNG demonstrates it perfectly:
>
http://www.mattstow.com/downloads/fill_test.png
>
> And the original PSD can be found here:
>
http://www.mattstow.com/downloads/fill_test.psd
>
> This is a real issue for PS->FW interoperability - I
basically could not use
> FW for the task of preparing a design for the web.
>
> I'd be interested to hear how this will affect other
users.
>
> Regards
>
> Matt
>

Lync 2013 Outlook Integration Issues

I have a client that is having Exchange Outlook Integration issues when trying to set up Lync 2013.
The email address is [email protected] The sip address is
[email protected] But the Lync server is lync.domain.local. Client is on Exchange 2010.
The address book is not downloading and the outlook integration issue error icon appears on the bottom right.
If the client is set manually to [email protected] the address book downloads.
But can Lync work in the long run set up like this?

Hi,
Did you solve the issue with the help of Andrew provided?
Which sip domain name did you use for default SIP domain ([email protected] or
[email protected])?
Did the issue happen internal or external?
For the issue of cannot download address book, please check the External Base URL on Lync topology with the help of the link below:
http://ucken.blogspot.in/2011/07/configuring-lync-for-external-access.html
For the issue of Lync and Exchange integration you can refer to the link below:
http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/
Note: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there.
Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

MM-SUS Scenario - Issue in vendor replication

Hi Gurus,
We are implementing MM-SUS scenario on SRM 7.0 interacting with a system R/3 4.6C and NW PI 7.0.
Now we are workking on the vendor replication from R/3 by mean tx BD14. So we performed all neccesary configuration and functional steps on R/3 system and on SRM to be able to execute BD14
After execution we obtain messages about succesfully IDoc creation for vendor data transmission and we see in tx WE02 that everything was OK, current status=03 (data passed to port OK).
But when we login on SRM, we dont' found the correspondent business partner in tx. BP and neither his connection with central vendor group in tx PPOMV_BBP and user/password generation to be sended by automatic email to supplier.
Can anybody help me with this issue?.Thanks in advance.
Regards,
Horacio

Hi,
We have been investigated the issue and for some similar issues the procedure to
delete the entried in VENMAP table and after to do the replication again
have solved the issue.
The steps to delete the entry from VENMAP:
- Goto to transaction SE16
- Open 'VENMAP' table
- Type in the vendor number under 'VENDOR_NO' field, which you
   need to delete.
- Select the record and open in display mode (or just double
   click on the record)
- In the 'Table VENMAP Display' screen, on the transaction bar,
   type '/h' and press enter.
- Click on the screen and press enter.
- You will be in the debug mode. Change the 'code' value to 'DELE'.
- Press F8 and execute the program. Now you will find a 'Delete Entry'
   button.
- Click on the 'Delete Entry' button and remove the entry from VENMAP.
Once this is done, run BBPGETVD transaction and unset 'Address
Comparison to Identify Duplicates'.
We can do other test, Would it be possible to you enter the supplier
data to the BUT000 table manually for the currupted business Partener ?
Partner GUID, Partner can be taken from the VENMAP table.
Please test both procedure and update me if it solve the issue for
the Partner.
Please check the note 548862 FAQ: EBP user administration, topics 2
and 3 about how you can check all EBP users and about BUP_BUPA_DELETE.
We hope this information can help you.
Kind Regards,
Edel.

Error updating vendor from SRM to SUS

Hi All
We are using SRM 4.0 in Extended classic scenario, alongwith SUS.
We have a nightly batch run & vendor changes from ECC are updated in SRM.
For Vendors marked as Portal vendors, there is a real time interface between EBP and SUS (thru XI), which updates the vendor in SUS.
However some of the updates are failing in SUS. The error message in SXMB_MONI, trace is as follows.
<FAULT_TEXT>An error occured within an XI interface: Exception occurredE:R1:479 -Address still in use; change to validity not allowed Programm: CX_BBP_BD_ERROR===============CP; Include: CX_BBP_BD_ERROR===============CM002; Line: 57</FAULT_TEXT>
We are not able to determine which address and how exactly it i in use??
Regards
Kedar

Thanks for the Reply
When I restarted the messages in SXMB_MONI, the errors have gone now, but I still see failures in SLG1.
here is the complete description:
Don't know if it is processed or not?
Address still in use; change to validity not allowed
Message no. R1479
Diagnosis
You have attempted to restrict the validity period of a BP address. However, this BP address is still being used, which means that you cannot make this change.
System response
The system issues an error message. The validity of the address is not changed.
Procedure
Display the where-used list for the BP address. If you still want to change the validity of the address, then change the address reference for the applications in question.
In most cases, if other applications are affected, you can navigate from the where-used list directly to the corresponding application in which you call up the context menu.
Then try again to change the validity of the BP address.

User synchronization SUS-BW issue.

Hello Experts,
Your help is required for the following issue.
One of our clients is implementing SRM-SUS 7.02 and would like to synchronize users (and information regarding BP) to their BW system 7.3
Configuration so far is as follows: SPRO -> SAP SRM -> Supplier Self-Services -> Master Data -> Maintain systems for Synchronization of User Data.
Parameters:
System Name: BW DEV
FM BPID: RS_BW_BCT_SRM_SUS_USER_BPID
Role: <blank>
F Mod.: Create User: BAPI_USER_CREATE
F Mod.: Change User: BAPI_USER_CHANGE
F Mod.: Delete User: BAPI_USER_DELETE
"Roles in external system" have been mapped.
Now, when a user (vendor contact person) is created in SUS, it's SU01 user is created correctly in BW. No problems here.
However, when I check table SRM_USER_SUPBPID in BW system, there are ZERO entries.
I guess I am missing something here.
I checked BADI SMUM_USR_CREATE_POST, and implementation RSSBR_SMUM_CRM_SUS is Active.
Should an entry exist in table SMUM_BSAPP? If so, what should I type in "BSID" field.
Any light on this matter is greatly appreciated.
Regards,
Gilberto Gallardo

Did you ever get this resolved? having a similar issue

SRM-XI-SUS Integration issue.

Similar Messages

Maybe you are looking for