PI setup for e-filing GB

[Stoo]

Hi,

Following our recent upgrade we now have to use XI (PI) for our e-filing instead of BC.

I have followed all the documentation and set up PI as instructed. All seems fine there.

However, when I try to send a message from the B2A Manager (txn PB2A) I get a communication error. Nothing gets to PI.

How does B2A Manager know it should be using PI? How does it know where it is? Should there be an RFC entry for PI? There is obviously some config somewhere I am missing.

[Baz]

Have you configured the connections in SXMB_ADM to XI and SM59?


also, run transaction SPROXY and check the error messages.

[Stoo]

I have just done that, but it doesn't appear to have made a difference. Just to confirm, then, here's what I did.

On the business system I ran SM59. I created a type H RFC connection called SAP_PI to the integration server. The connection test returns a HTTP 500 error (empty request), which I assume is normal.

Then in SXMB_ADM on the business system I ran the Integration Engine Configuration option. I set the Role to "Application Sysetm" and Corresponding Integ. Server to dest://SAP_PI

Is that all ok?

[Stoo]

When I run SPROXY, I get "No connection to ESR. Only local data are displayed."

Is that what I should be expecting?

[Baz]

You are part way there.

Follow the steps here to configure connection to the integration server...

http://www.saptechnical.com/Tutorials/X ... /page1.htm

[Stoo]

Great link. Thanks for that.

However, I'm stuck on item 3: "Connection between Business System and System Landscape Directory".
I have tried creating the two RFC enties but neither of them work. I have copied the details from the same entries on our PI box. The error says "ERROR: program LCRSAPRFC_PID not registered" if use the default gateway or "ERROR: service 'sapgw03' unknown" if I try to use the same gateway as PI.

[Baz]

Are you using the data from the PI Instance?

Or the ECC Instance?


this may help!

http://help.sap.com/saphelp_nw70/helpda ... ameset.htm



Use the default gateway and add the registered program into the Java Visual Admin Console.

[Stoo]

Morning Baz,

I'm still struggling with this. I've had a good read through that last document, and I'm still no the wiser. I think we're almost there though.

The PI server (sapdv3) can contact the SLD fine. Transaction SLDCHECK checks out fine.
Obviously, I need to put similar settings in our corresponding ECC server (sapdv5), right?

I've created the two type 'T' RFC connections exactly as they are on sapdv3 but neither of them work. The two servers use different gateways and it seems the registered server programs only exist on the gateway for sapdv3 (PI).

Now, should I create new registered server programs on the gateway for sapdv5 (ECC), and if so, how?
OR...
Do I somehow point sapdv5 at the gateway that sapddv3 is using? And how?

OR...
Am I talking complete nonsense?

[Stoo]

Hurrah!

I've now got messages hitting my PI queues!
Unfortunately I'm getting receiver determination errors on them all.

I've tested the configuration in the ID and it all works fine.

I think the problem is down to there being no sender being listed in the message

Code: Select all

<SAP:Sender>
  <SAP:Service />
  <SAP:Interface namespace="" />
  </SAP:Sender>

Any ideas?

[Baz]

Stoo

Sorry for not answering on friday! somehow I missed your posting!

Let me go back thorugh my documentation to check what is supposed to be happening here!

Just to confirm that when you run the data/XML through the "test configuration" function in the Integration Directory, everything completes successfully?

Can you paste the error message from the XML in sxmb_moni for this?

There will be no sender for this as it is "Vritual". It is being pushed from ECC rather than being pulled in, so there that is correct for the sender to be blank! This is the case for ABAP Proxies.

[Stoo]

Ah. So if there is no sender, how does XI know how to deal with the message?

Unfortunately, I can't get on the system at the moment, so I can't post the exact error from SXMB_MONI.
IIRC, the crucial part is something like "Receiver determination error". And something like RECEIVER_CASE_BE.
As soon as I get on I'll post it up.

[Stoo]

Here is the response message. I got this from SXMB_MONI on our business system as the PI server is currently down for maintenance.

Code: Select all

  <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!--  Inbound Message
  -->
- <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>SystemError</SAP:MessageClass>
  <SAP:ProcessingMode>synchronous</SAP:ProcessingMode>
  <SAP:MessageId>47F0C095-7B2C-3250-E100-00000A01C079</SAP:MessageId>
  <SAP:RefToMessageId>47EF5534-77DB-6A17-E100-00000A01C06C</SAP:RefToMessageId>
  <SAP:TimeSent>2008-03-31T12:50:01Z</SAP:TimeSent>
- <SAP:Sender>
  <SAP:Service />
  <SAP:Interface namespace="" />
  </SAP:Sender>
- <SAP:Receiver>
  <SAP:Party agency="" scheme="" />
  <SAP:Service>DV1_041</SAP:Service>
  <SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFO_EOYR_OUT</SAP:Interface>
  </SAP:Receiver>
  <SAP:Interface namespace="http://sap.com/xi/HR">HR_GB_EFO_EOYR_OUT</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>BestEffort</SAP:QualityOfService>
  </SAP:ReliableMessaging>
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>XIServer</SAP:Category>
  <SAP:Code area="RCVR_DETERMINATION">NO_RECEIVER_CASE_BE</SAP:Code>
  <SAP:P1 />
  <SAP:P2 />
  <SAP:P3 />
  <SAP:P4 />
  <SAP:AdditionalText />
  <SAP:ApplicationFaultMessage namespace="" />
  <SAP:Stack>No receiver could be determined</SAP:Stack>
  <SAP:Retry>M</SAP:Retry>
  </SAP:Error>
- <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="2008-03-31T12:50:37Z" wasRead="false">
  <SAP:Engine type="BS">DV1_041</SAP:Engine>
  <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
  <SAP:MessageId>47EF5534-77DB-6A17-E100-00000A01C06C</SAP:MessageId>
  <SAP:Info>3.0</SAP:Info>
  </SAP:Hop>
- <SAP:Hop timeStamp="2008-03-31T12:58:46Z" wasRead="false">
  <SAP:Engine type="IS">is.03.sapdv3</SAP:Engine>
  <SAP:Adapter namespace="http://sap.com/xi/XI/System">XI</SAP:Adapter>
  <SAP:MessageId>47EF5534-77DB-6A17-E100-00000A01C06C</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>20080401</SAP:Date>
  <SAP:Time>094216</SAP:Time>
  <SAP:Host>sapdv5</SAP:Host>
  <SAP:SystemId>DV1</SAP:SystemId>
  <SAP:SystemNr />
  <SAP:OS>SunOS</SAP:OS>
  <SAP:DB>ORACLE</SAP:DB>
  <SAP:Language />
  <SAP:ProcStatus>023</SAP:ProcStatus>
  <SAP:AdapterStatus>000</SAP:AdapterStatus>
  <SAP:User>CSMAYORS</SAP:User>
  <SAP:TraceLevel>1</SAP:TraceLevel>
  <SAP:LogSeqNbr>000</SAP:LogSeqNbr>
  <SAP:RetryLogSeqNbr>000</SAP:RetryLogSeqNbr>
  <SAP:PipelineIdInternal>SAP_SENDER</SAP:PipelineIdInternal>
  <SAP:PipelineIdExternal>SENDER</SAP:PipelineIdExternal>
  <SAP:PipelineElementId />
  <SAP:PipelineService />
  <SAP:QIdInternal />
  <SAP:CommitActor />
  <SAP:SplitNumber>0</SAP:SplitNumber>
  <SAP:NumberOfRetries>0</SAP:NumberOfRetries>
  <SAP:NumberOfManualRetries>0</SAP:NumberOfManualRetries>
  <SAP:TypeOfEngine client="" />
  <SAP:PlsrvExceptionCode />
  <SAP:EOReferenceRuntime type="TID" />
  <SAP:EOReferenceInbound type="TID" />
  <SAP:EOReferenceOutbound type="TID" />
  <SAP:MessageSizePayload>0</SAP:MessageSizePayload>
  <SAP:MessageSizeTotal>6348</SAP:MessageSizeTotal>
  <SAP:PayloadSizeRequest>0</SAP:PayloadSizeRequest>
  <SAP:PayloadSizeRequestMap>0</SAP:PayloadSizeRequestMap>
  <SAP:PayloadSizeResponse>0</SAP:PayloadSizeResponse>
  <SAP:PayloadSizeResponseMap>0</SAP:PayloadSizeResponseMap>
  <SAP:Reorganization>INI</SAP:Reorganization>
  <SAP:AdapterInbound>IENGINE</SAP:AdapterInbound>
  <SAP:AdapterOutbound>PROXY</SAP:AdapterOutbound>
  <SAP:InterfaceAction>INIT</SAP:InterfaceAction>
  <SAP:RandomNumber>00</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="CORE">INTEGRATION_ENGINE</SAP:Name>
  <SAP:Timestamp type="begin" host="sapdv5">20080331125037.380846</SAP:Timestamp>
  </SAP:RunTimeItem>
- <SAP:RunTimeItem>
  <SAP:Name type="CORE">INTEGRATION_ENGINE</SAP:Name>
  <SAP:Timestamp type="end" host="sapdv5">20080331125038.023299</SAP:Timestamp>
  </SAP:RunTimeItem>
- <SAP:RunTimeItem>
  <SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
  <SAP:Timestamp type="begin" host="sapdv5">20080331125038.276061</SAP:Timestamp>
  </SAP:RunTimeItem>
- <SAP:RunTimeItem>
  <SAP:Name type="PLSRV">HTTP_SEND</SAP:Name>
  <SAP:Timestamp type="begin" host="sapdv5">20080331125039.942199</SAP:Timestamp>
  </SAP:RunTimeItem>
- <SAP:RunTimeItem>
  <SAP:Name type="PLSRV">HTTP_SEND</SAP:Name>
  <SAP:Timestamp type="end" host="sapdv5">20080331125047.501629</SAP:Timestamp>
  </SAP:RunTimeItem>
- <SAP:RunTimeItem>
  <SAP:Name type="PLSRV">PLSRV_CALL_INTEGRATION_SERVER</SAP:Name>
  <SAP:Timestamp type="end" host="sapdv5">20080331125048.208346</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:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
  <Trace level="1" type="T">COMMIT is expected by application !</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 = DV1</Trace>
  <Trace level="1" type="T">client = 041</Trace>
  <Trace level="1" type="T">language = E</Trace>
  <Trace level="1" type="T">user = CSMAYORS</Trace>
  <Trace level="1" type="Timestamp">2008-03-31T12:50:38Z GMTUK</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 = 47EF553477DB6A17E10000000A01C06C</Trace>
  <Trace level="1" type="T">PLNAME = SENDER</Trace>
  <Trace level="1" type="T">QOS = BE</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- <!--  ************************************
  -->
  <Trace level="1" type="T">Get definition of external pipeline SENDER</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
  <Trace level="1" type="T">Corresponding internal pipeline SAP_SENDER</Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
- <Trace level="1" type="B" name="PLSRV_CALL_INTEGRATION_SERVER">
- <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="CL_XMS_PLSRV_IE_ADAPTER-ENTER_PLSRV">
  <Trace level="1" type="T">URL for integration server read from global configuration</Trace>
  <Trace level="1" type="T">URL= dest://SAP_PI</Trace>
- <Trace level="1" type="B" name="CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP">
  <Trace level="1" type="T">---------------------------------------------------</Trace>
  <Trace level="1" type="T">SSL not active</Trace>
  <Trace level="1" type="T">---------------------------------------------------</Trace>
  <Trace level="1" type="T">HTTP Multipart document length: 7044</Trace>
  </Trace>
  </Trace>
  </Trace>
  </Trace>
  </Trace>
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
  <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
  <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" />
  </SOAP:Body>
  </SOAP:Envelope>

[Baz]

Ah. So if there is no sender, how does XI know how to deal with the message?

Unfortunately, I can't get on the system at the moment, so I can't post the exact error from SXMB_MONI.
IIRC, the crucial part is something like "Receiver determination error". And something like RECEIVER_CASE_BE.
As soon as I get on I'll post it up.

the step are as follows:

Installation Activity Stages
Installation Location
1. Create a Product and a Product Version and add a Software Component and a Software Component Version
SLD ->Technical Systems
2. Download XI Content for Software Component
Versions
SAP Service Marketplace
3. Import and Activate Software Component Versions
IB -> Integration Repository
4. Create Parties for Components
IB -> Integration Directory
5. Create Business Services for Parties
IB -> Integration Directory
6. Implement Integration Scenario
IB -> Integration Directory
7. Determine Receiver Conditions (Outgoing only)
IB -> Integration Directory

[Baz]

Try checking the configuration in SXI_CACHE.

There may be a cache issue.

Also run the http://<host>.fqdn:5<sys#>00/CPACache/refresh?mode=full
using (PI)XIDIRUSER

[Stoo]

I think I have sorted it.
It's now working (almost) and I think it was down to me specifying a sender party in the receiver agreement.

Thanks for all your help.