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

*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" ?>

- <!-- Call Integration Server

-->

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

SAP Managed Tags:
SAP Process Integration

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (0)

Answers (3)

HI,

Look out for the log in SLG1 of SRM System. Probably it will give you some idea. Check if some settings are missing in SRM.

Are you using XI proxy in sender side? if yes, no need to use it.. No sender com channel and sender agreement needed. Create an XI Proxy receiver Communication channel for ECC.

I hope you already create the SM59 RFC destination for SRM system in PI and vice versa.

Regards

Aashish Sinha

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks Aashish .

I checked SLG1 and error message for my Contract as below

Recipient not found

Message no. BBP_EXC004

The error ocurred by processing event RELEASED_NEWLY with GUID E0460004EF852FF182AD005056A12FA9 and object_id= 4400000037

Message no. BBP_EXC000

What could be the reason ?

Thanks

NAP

HI All,

I'm working on this scenarion from PI side with Narendra,

we have done all the setting suggested in this thread.

We are now getting following error,

XML tag Main/@versionMajor has incorrect value 002; expected value is 003.

Thanks,

Venu and Narendra.

Hi Venu & Narendra,

@ Narendra : You probably be getting this error because of some missing settings in SRM side. Can you please look out or ask your functional consultant.

@Venu : Please post the detailed error, that where are you getting this error. if in SRM - SXMB_MONI, please let me know the exact text as well as if you getting it in PI.

Regards

Aashish Sinha

Hi Venu,

For this error, Regenerate the proxy, the error has occured due to proxy incorrect version (there might have been some modifications in data structure and configuration.)

Cheers,

Nipun

Hi Ashish

This is Venu ......

When the SRM scenario has been triggered, the message got stuck in SRM queue(SMQ2), after excuting the queue we are gettting following error,

*XI error ITEM_UNEXPECTED.PARSER: Queue Stopped*

*and after thgis when we check the SRM SXMB_MONI ,,,,,,we are getting the following error*

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Integration Server

-->

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

Venu & Abhishek

Hi Aashish ,

1.CCR Document is okay in SRM and it do not shows any error log in the SRM Application Monitor, in the RZ20 as well as in the BBP_PD. Even I am craeting Contract independently in ECC woth same data to that of CCR in SRM and it don;t have issue.

Regards

NAP

Hi Venu/Abhishek,

As per the conversations, I beleive the config in ECC and PI is absolutely OK (even if you create a comm channel and agreement for sender, which are not required, that should not have any impact on the error). Since the processing is successful in ECC system, I would recommend doing a simple test in the ID of PI using Test Configuration tool. Use the data which is passed as input. This will second the fact that everything is OK from PI side also.

Then, you can check whether the data sent from SRM is as per expectations. I think the problem might be due to missing mapping or wrong conditions for key fields etc.

Check the link: http://forums.sdn.sap.com/click.jspa?searchID=70621600&messageID=4708465

Hope this helps.

Regards,

Souvik

Hi Abhishek/Venu

This error is coming because SRM Application using ABAP Proxies tries to communicate with AAE using SOAP Adapter with XI Protocol. But this communication results in error. This exception is thrown by AAE SOAP Adapter used with XI protocol.

The error message could also be similar to the following: XML tag Main/@versionMajor has incorrect value 002; expected value is 003. As you were getting this error message earlier also.

Have a look into below SAP Notes. It will fix your problem.

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1349125 (SMP Login required)

SAP note number : 1349125

Regards

Aashish Sinha

Narendra,

I too agree with Aashish the problem you are facing is of incorrect Transport Protocol, correct the transport ptrocol and regrenerate the proxy, the problem should go this time.

Regards,

Nipun

HI Aashish,

Thanks for the useful information, will try applying the note.

Do you recommend using the SOAP sender adapter in this case?

I have tried initially with the SOAP adapter, but since it was not working, I have deleted the sender agreement and from the receiver side I have used the XI receiver adapter.

Thanks,

Venu.

Hi venu

If you have check the SRM generated XML messgages in XI ->ID->Test scenario...and if that is working fine ....

then there is problem with SRM ....which is not able to push the XML data to XI (as is it using push mechanish (not pulled by XI))

using proxy ...

Check all the settind done by SRM-PI conectivity , seems like a proble there ...

try to troubleshoot to release the queue fro SRM

Thanks

Hi,

No, the way you sending data from SRM to SAP PI is looks fine to me, no need to use SOAP Adapter in between. Please apply the note, and i hope it will fix the problem.

Regards

Aashish Sinha

HI Aashish

The note suggests doing following things,

u2022 Changes in SOAP adapter

u2022 Apply further notes: 1334174, 1332856

u2022 Applying SP patches

I understood from your mail that it will not be required to use the soap adapter.

Could you please suggest just applying notes and apply SP patches are enough from this point of time?

Thanks,

Venu.

Hi Aashish,

After implemnenting above notes is it mandatory to use the AAE features or can I continue using the classic configuration in PI?

Does AAE setting suggest any modification at Application level (SRM or ECC) apart from PI ?

Please suggest.

Thanks,

Venu.

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" ?>

- <!-- Call Inbound Proxy

-->

- <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="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="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">Message-GUID = E04BAF35835783F182AD005056A12FA9</Trace>

<Trace level="1" type="T">PLNAME = RECEIVER</Trace>

<Trace level="1" type="T">Queue-Id = CCR4400000066</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>

<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="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">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="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="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="T">Corresponding internal pipeline SAP_RECEIVER</Trace>

- <!-- ************************************

-->

- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">

- <!-- ************************************

-->

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

- <!-- ************************************

-->

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

Hi All

The messages are coming sucessfully from SRM to PI , message are going sucessfully from PI ,

but if we check in SXMB_MONI of ECC , the error is coming as communication error.

Please advise...

Thank s

Hi Narendra,

I Understand that you scenario is SRM(Proxy)--> PI --> ECC 6.0 EHP 4, if this is the case you actually don't require any XI Sender Adapter when using a client Proxy.

Regards,

Nipun

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hi ,

At what level interface failed in MONI(check pipe line steps),i think SRP data not matiching with your structure what you have defined.might be XSD wrong.

Regards,

Raj

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Hey Raja

It is pre-configured scenario..every thing is standard including Function Module also ...

Problem is whe we check the SXMB_mONI message ststus ..the below mention message we are getting...

sender Adapter is XI Adapter (Proxy). Message are Getting failed in SRM Box only .....

Thanks

Abhishek Agrahari

hi,

you're probably missing the fault message type in your service interface definition. go to the esr to the SI definition and add a fault message and try again

>> sender Adapter is XI Adapter (Proxy). Message are Getting failed in SRM Box only .....

Hope below steps might help...

a) Sender side proxy then you dont need cllient proxy adapter.

b) Check proxy configuration between SRM and PI. (if messges are getting failed in SRM Box only...)

c) Also make sure ID objects are properly configured with sender business system (ABAP type) in Receiver determination, Interface determination, Receiver agreement etc

d) in your case you dont need sender comm channel and sender agreement.

e) Check proxy structure on the client side matches with PI source data structure. If there is mismatch , regenerate outbound proxy side in SRM and do the coding...

Ask a Question

Top Q&A Solution Author

User

Count