XI, PIDX and RNIF.

We are very new to XI and we are looking to install XI and use PIDX RNIF 2.0 for one of our customer accounts. Our consultants for this project have asked us to pose some questions to SAP. I thought I might post them here and see if anyone can provide some feedback. Any information will be appreciated.
Here are the questions:
Requirement: We are planning to implement outbound PIDX (Petroleum Industry Data Exchange) transactions using PI(XI). SAP PI doesnt provide PIDX adapter. As PIDX is based on RNIF standards, We are trying to provide the solution using RNIF adapter. There are few settings provided in SAP note (Note 870270 - FAQ note for initiating Support related to ISpeak Adapters) for non-standard deviation in Industry adapters.
1) Does applying this note ensure that the message is PIDX compliant?
2) Also, since we have the requirement of sending attachments with outgoing PIDX message. RNIF adapter doesnt support attachments. Is enhancing RNIF module the only option for sending PIDX with attachments? I understand SAP doesnt have standard business content for PIDX, so mappings between PIDX messages and IDOCs have to be developed from scratch. Do guide us on how PIDX messages (with or without attachments) can be sent using RNIF adapter.
3) Are their any existing business packages for PIDX (similar to RNIF/CIDX)?
4) Are their any successful PIDX implementations and client references if any?
Thanks in advance.

Similar Messages

Issues with XI 3.0 CIDX Adapter

Hi folks,
We are doing an XI pilot project to replace our current SAP BC B2B environment which is using CIDX and RNIF 1.1 to exchange B2B information ( we build our own custom RNIF adapter on top of SAP BC ).
We have succesfully sent a message from XI towards our SAP BC ( temporarely used as our surrogate trade partners) using the CIDX adapter ( RNIF was okay and service-content extracted fine ).
The other way is giving us problems ... When we sent a CIDX RNIF message from SAP BC towards XI then we get the following nice dump message:
com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet#sap.com/com.sap.aii.af.ms.app#com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(HttpServletRequest, HttpServletResponse)#SDESAEGE#690##BEEVAXIT_XIT_9961950#Guest#108fc370f2e511d9a790001143e3179b#SAPEngine_Application_Thread[impl:3]_13##0#0#Warning##Java###Catching #1#java.lang.NullPointerException at com.sap.aii.af.sdk.cidx.impl.choreography.typing.CIDXTypeResolver$CIDXTypeDetector.findTypeFromMsgDetails(CIDXTypeResolver.java:170) at com.sap.aii.af.sdk.cidx.impl.choreography.typing.CIDXTypeResolver.ResolveType(CIDXTypeResolver.java:94) at ....
The strange thing here is that first I got an error because the from partner DUNS number was not recognised within the integration directory - this was correct as the partner did not exist yet.
After fixing that I got the mentioned error.
BUT if I put in a wrong DUNS number again then I still get the same error and not the previous one ...
We thought it was a cache problem so we cleared caches, restarted the J2EE instance but nothing helped ...
Anyone any ideas ?
Thanks,
Steven

Hi folks,
We are doing an XI pilot project to replace our current SAP BC B2B environment which is using CIDX and RNIF 1.1 to exchange B2B information ( we build our own custom RNIF adapter on top of SAP BC ).
We have succesfully sent a message from XI towards our SAP BC ( temporarely used as our surrogate trade partners) using the CIDX adapter ( RNIF was okay and service-content extracted fine ).
The other way is giving us problems ... When we sent a CIDX RNIF message from SAP BC towards XI then we get the following nice dump message:
com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet#sap.com/com.sap.aii.af.ms.app#com.sap.aii.af.ra.ms.impl.core.transport.http.MessagingServlet.doPost(HttpServletRequest, HttpServletResponse)#SDESAEGE#690##BEEVAXIT_XIT_9961950#Guest#108fc370f2e511d9a790001143e3179b#SAPEngine_Application_Thread[impl:3]_13##0#0#Warning##Java###Catching #1#java.lang.NullPointerException at com.sap.aii.af.sdk.cidx.impl.choreography.typing.CIDXTypeResolver$CIDXTypeDetector.findTypeFromMsgDetails(CIDXTypeResolver.java:170) at com.sap.aii.af.sdk.cidx.impl.choreography.typing.CIDXTypeResolver.ResolveType(CIDXTypeResolver.java:94) at ....
The strange thing here is that first I got an error because the from partner DUNS number was not recognised within the integration directory - this was correct as the partner did not exist yet.
After fixing that I got the mentioned error.
BUT if I put in a wrong DUNS number again then I still get the same error and not the previous one ...
We thought it was a cache problem so we cleared caches, restarted the J2EE instance but nothing helped ...
Anyone any ideas ?
Thanks,
Steven

Why Application ack not supported in Reciever adapters?

Hi All,
a.What is difference between Application and System acknowledgements ?
b. Why Application ack not supported in Reciever adapters (except for CIDX and RNIF)?
(as mentioned in http://help.sap.com/saphelp_nw70/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm)
c:http://help.sap.com/saphelp_nw70/helpdata/en/e1/091640a991c742e10000000a1550b0/content.htm
says If messages are sent from the PCK to the Integration Server, you must create a receiver XI adapter in the PCK.!!
Should not this be either way?
Regards
Guru

<b>a.</b> System acknowledgments used by the runtime environment to confirm that an asynchronous message has reached the receiver.
Application acknowledgments used to confirm that the asynchronous message has been successfully processed at the receiver.
http://help.sap.com/saphelp_nw2004s/helpdata/en/f4/8620c6b58c422c960c53f3ed71b432/content.htm
<b>c.</b> No
Message was edited by:
Prabhu S

Need Task list for starting a Rosettanet.

Hi,
Please let me know what are the intial steps to be done for setting up the XI and RNIF systems from XI point of view. Please reply with the task list.
Thanks & Regards,
Pragathi.

Hi,
1)First you need to identify which Rosettanet PIP messages your are going to use,identify and download the PIP messages from rosettanet org,already different version dtds available ,download the DTDs with version what you looking for.
2)Identify the who is the receiver , how to transform thsi structure in tro receiver format,you already have any standas receiver formats use it like IDocs(id your receiver is SAP ).
3)Thenu use Rosettanet adapter to read the message.
remaining steps all are same,refer any sample scenario,you wil understand.
Regards,
Raj

Changing namespace when calling OSB business service

Hello All,
I have a business service in OSB calling a BPEL process. The BPEL process returns values prefixing all the tags with name space "pidx". The name space definition is xmlns:pidx="http://www.api.org/pidXML/v1.2".
When I test the business service from the test console, I get the tags prefixed with a namespace v1. I see 2 name space definitions one with pidx and another with v1. any idea why there are duplicate namespace and why v1 namespace gets added?
v1:OrderCreate v1:transactionPurposeIndicator="Original" xmlns:pidx="http://www.api.org/pidXML/v1.2" xmlns="http://www.api.org/pidXML/v1.2" xmlns:v1="http://www.api.org/pidXML/v1.2">
Thanks,
Dwarak

The BPEL process returns multiple namespace xmlns:pidx="http://www.api.org/pidXML/v1.2" and xmlns="http://www.api.org/pidXML/v1.2". If i remove one of them, i get the right namespace prefixed with my tags. I had to convert the output of the BPEL process to a string, use a replace to remove the duplicate namespace, convert back to XML. I know this is not a clean way, but did not know an alternative.

SAP Webdispatcher protocols

Hi All,
Could you let me know what is the latest SAP Webdispatcher version currently available and what protocols it can handle.
Last I had heard they don't support SOAP calls but only HTTP(s). Does it now support SOAP ?
Also does it support RNIF ?
SAP Web Dispatcher protocols are determined by the parameter icm/server_port_x.
Thx in advance
Ravijeet

Hi Ravijeet
Please check the note #908097 SAP Web Dispatcher: Released releases and applying patches.
I don't think there are any restrictions with regards to SOAP and RNIF. You can use the Web Dispatcher with your PI system which can handle these protocols.
Regards
Mark

Inbound PIDX 1.2 With RNIF V2.0

Hi,
We are trying to configure an Inbound PIDX Invoice V1.2, with RNIF V2.0.
Here are my questions.
1. Can we read the PIDX invoice as a Generic File or should I need to get it over http or https? As per the documentation, RNIF is supposed to support multiple transport protocols.
2. I tried the file, by removing the RNIF wrappers, seems to be working fine. But, when I include the wrapper and at the From-TP level, I configure the listening channel to RNIF 2.0, Saved the Agreement, Validated and redeployed.
Wire Message :
Id     0A6066AF13553B45C60000004D1C7A4F
Message Id     0A6066AF13553B45BBB000004D1C7A4B
Refer To Message     Refer To Message
Sender Type     Name
Sender Value     GlobalChips
Receiver Type     Name
Receiver Value     Enterprise
Sender     GlobalChips
Receiver     Enterprise
Agreement Id
Agreement
Document Type     PayableInvoice
Document Protocol
Document Version
Message Type     REQ
Direction     INBOUND
State     MSG_ERROR
Acknowledgement Mode     NONE
Response Mode     ASYNC
Send Time Stamp     02/06/2012 11:27 AM
Receive Time Stamp     02/06/2012 11:27 AM
Document Retry Interval(Channel)     0
Document Remaining Retry(Channel)     0
Document Retry Interval(Agreement)
Document Remaining Retry(Agreement)
Native Message Size     194014
Translated Message Size
Business Action Name
Business Transaction Name
Xpath Name1
Xpath Value1
Xpath Expression1
Xpath Name2
Xpath Value2
Xpath Expression2
Xpath Name3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
Correlation To XPath Value
Correlation To XPath Expression
Wire Message     Wire Message
Application Message     Application Message
Payload Storage     Payload Storage
Attachment     Attachment
Label
Collaboration Id
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name     Generic File
Exchange Protocol Version     1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code     B2B-50083
Error Description     Machine Info: (zzzzzzzz.ttttt.com) Description: Document protocol identification error.
Error Level     ERROR_LEVEL_COLLABORATION
Error Severity     ERROR
Error Text     Document protocol identification error.
what I observed is packed message still has the rnif wrapper.
Any help is appreciated.
Thanks,
Sai.

Sai,
You can not create Listening Channels with channel protocol as RNIF 2.0. Only partner channel can be of type RosettaNet V02.00. Please refer -
http://docs.oracle.com/cd/E17904_01/integration.1111/e10229/bb_listen_chan.htm#BAJJICJJ
If you want B2B to handle the RNIF headers (as per RNIF specification) then use HTTP transport (RosettaNet V02.00 channel) otherwise if you will use Generic File then B2B will treat the incoming message as a normal XML/Flat File.
Regards,
Anuj

Delivery and Service Header Fields in RNIF Receiver Adapter for Rosettanet.

Hello all,
I need to populate the Delivery and Service header fields in Rosattenet MIME message in the receiver side.
For the sender side RNIF adapter, we can very well use the Adapter Specific message to get those fields from Rosattenet MIME message. But in my scenario, I need to use RNIF as the receiver, which will pick messages from other system and post it to RNIF.
Also, I have checked the receiver RNIF adapter, there I dont find any adapter specific messages to use.
Regards,
UP

Prasad
You have not mentioned which RNIF Adapter you are using whether 1.1 or 2.0. I will assume that you are using 2.0.
If you are using Single action responder the parameters you should configure is given here:
http://help.sap.com/saphelp_nw2004s/helpdata/en/70/d89d40c1252a54e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/fa/6b98403de08368e10000000a1550b0/content.htm
If you are using Two action responder the parameters you should configure is given here:
http://help.sap.com/saphelp_nw2004s/helpdata/en/6f/dc9d40759c2b54e10000000a1550b0/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/2c/7198403de08368e10000000a1550b0/content.htm
---Satish

PI B2B RNIF interface design and configuration

Hello All,
can anybody send me details of design steps and configuration steps in detail for RNIF 2.0 framework for PIPS
Preferably Rosettanet 7B1 WIP Tracking, Rosettanet 3B12 Shipping Request
thx
mike

Any body who can guide me the steps in ESR for RNIF PIP interfaces. I am expecting step by step instructions.
Thank you very much!!
mike

One pi system as rnif sender and receiver

Hi,
I'm trying to implement a RosettaNet test-scenario for PIP3B2 using PI 7.1. Is it possible to send a RosettaNet message from a PI to the very same PI and also get the receipt aknowledgement from it?
Is there anything special I have to do?
Thanks in advance
Michael Forster

Hi Guys,
Thank you for ur reply
I believe this is a temp solution before the real hardware arrives...
Hence, dev can be ready by then but the point is that ther is ERP for dev, ERp for QA and ERP for Prod...
How can i connect the same Pi system to three different erp s??
as all scenarios have proxy...
Can u pls throw light on this?
Regards,
Teja
Edited by: Ravindra Teja on Sep 29, 2009 7:42 AM

Configuring Oracle B2B to Receive Inbound PIDX invoices with RNIFV02.00

Hi,
I am trying to do an inbound PIDX Invoice Version 1.0 wrapped inside RNIF.
Steps that I have done so far.
1. Create a new Version under RosettaNet - V02.00
2. Create a new Document Definition PayableInvoice
3. Created a new Definition for PayableInvoiceTypeDef
4. We then create a new Agreement from the our FromTP to Our Client
5. Selected the RNIF Partner level channel for FromTP and configured the httpReceiver at the url level.
6. Save, Validate and Deploy.
When we do a post over http to the http Receiver, I am receiving the following error
Id     0A6066AF13676DBA690000005DEA5F61
Message Id     0A6066AF13676DBA5DF000005DEA5F5D
Refer To Message     Refer To Message
Sender Type
Sender Value
Receiver Type     Name
Receiver Value     Enterprise
Sender
Receiver     Enterprise
Agreement Id
Agreement
Document Type
Document Protocol
Document Version
Message Type     REQ
Direction     INBOUND
State     MSG_ERROR
Acknowledgement Mode     NONE
Response Mode     ASYNC
Send Time Stamp     04/03/2012 01:20 AM
Receive Time Stamp     04/03/2012 01:20 AM
Document Retry Interval(Channel)     0
Document Remaining Retry(Channel)     0
Document Retry Interval(Agreement)
Document Remaining Retry(Agreement)
Native Message Size     29464
Translated Message Size
Business Action Name
Business Transaction Name
Xpath Name1
Xpath Value1
Xpath Expression1
Xpath Name2
Xpath Value2
Xpath Expression2
Xpath Name3
Xpath Value3
Xpath Expression3
Correlation From XPath Name
Correlation From XPath Value
Correlation From XPath Expression
Correlation To XPath Name
Correlation To XPath Value
Correlation To XPath Expression
Wire Message     Wire Message
Application Message     Application Message
Payload Storage     Payload Storage
Attachment     Attachment
Label
Collaboration Id
Collabration Name
Collabration Version
Business Action Name
Exchange Protocol Name     Generic HTTP
Exchange Protocol Version     1.0
Interchange Control Number
Group Control Number
Transaction Set Control Number
Error Code     B2B-50083
Error Description     Machine Info: (bpmdev01.eprod.com) Description: Document protocol identification error.
Error Level     ERROR_LEVEL_COLLABORATION
Error Severity     ERROR
Error Text     Document protocol identification error.
Any Help Appreciated, thanks in Advance.
Vendor --> Client (our company) --> Inbound PIDX 1.0 Invoice, with RNIF V02.00 Header.
Regards,
Sai.

Sai,
Please log a SR with support to get a patch which will allow you to configure identification xpath expression and value for RosettaNet document definitions. After applying that patch, configure the identification xpath in document definition and then run a test.
This patch is already available so it won't take much time for support to provide you the same.
Regards,
Anuj

How to add/change missing header lines in RNIF B2B?

Hi all,
We are using RNIF exchange protocol. We have sent invoice from BPEL to B2B. The message invoice reaches the trading partner but they are unable to process it or sent ack back as few header lines are missing in the RNIF envelope.
Can anyone tell me or provide some pointers abt how to add/change missing header lines in B2B?
These are the headers missing:
Delivery header:
<locationID> <Value>HostTradingPartner</Value> </locationID>
Service Header:
<messageStandard>
<FreeFormText xml:lang="EN">PIDX</FreeFormText>
</messageStandard> <standardVersion>
<VersionIdentifier>1.0</VersionIdentifier>
</standardVersion>
Can anyone provide some inputs on this?

As per RNIF standard, all these header elements (locationID in Delivery Header & messageStandard and standardVersion in Service Header) are optional. As you are using RossettNet over RNIF, so Oracle B2B might not be setting these headers.
I do not have a 10g setup here so cann't test it. I would suggest you to raise a case with Oracle Support because PIDX is a non-RossettaNet standard and it's implementation in Oracle B2B will be different to RossettaNet implementation. Meanwhile, I would try the same in B2B 11g setup.
Regards,
Anuj

RNIF Adapter is only for B2B..?

Hi Experts,
In ongoing Project we have a requirement sending ABAP Proxy with PDF attachment from SAP ECC to PI and then Tibco i'e..SAP ECC>PI>Tibco.Am sending PIDX xmlAttachment to Tibco from PI, Tibco is also in our internal landscape and data is Industry specific, for that am using RNIF adapter.Can i use PIDX xmlAttachment using Reciver RNIF adapter as A2A or B2B?..
Appriciate your Inputs..
Regards,
Narayana.

Hi Narayana,
IF you want to exchange message with RosettaNet compliant system then we use RNIF adapter in B2B environment .
RNIF adapter supports PIP message format as per me experience,
better to read help documentation you wil get more info
http://help.sap.com/saphelp_nwpi71/helpdata/EN/45/99743f3d4b0866e10000000a114084/frameset.htm
Regards,
Raj

CIDX and RosettaNet Adapters?

Hi All,
I want to know about the following adapters in detail? can anyone suggest me some weblogs for these adapters?
What adpater is used while communicationg with Siebel System and any weblogs then send it to me?
Rgds
Faisal

Hi abdul,
pls do chk this linksit gives clear picture of Rosettanet and its standards
http://help.sap.com/saphelp_nw04/helpdata/en/1f/4c531f04c07a428964175147017fc8/frameset.htm
RosettaNet and the role of RNIF in XI
'Close Encounters' with the Rosettanet STK
Service-enabling RosettaNet business processes
CIDX Adapter :
The CIDX adapter enables the execution of business transactions between CIDX trading partners based on Chem eStandards specifications.
The adapter implements the transport, packaging, and routing of CIDX business messages and signals as defined in the Chem eStandards envelope and security specifications (based on RNIF 1.1 specifications; for more information, see cidx.org).
Transport protocols to be used are HTTPS and HTTP. With HTTPS, client authentication is possible for sender party and receiver party.
The adapter supports the security functions of the RNIF 1.1 business transaction dialog: authentication, authorization, and non-repudiation. Confidentiality should be ensured by using transport-level encryption, for example, HTTPS.
pls do chk this links
http://help.sap.com/saphelp_nw04/helpdata/en/1f/4c531f04c07a428964175147017fc8/frameset.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70d58f84-628c-2a10-349c-89f32fcaf6c8
PIDX Adapter:
pls do chk this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/90406c4d-fd57-2a10-e08f-887c52ce8547
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/40b9c897-28a8-2a10-8c9f-d3177a94d7e3
regards
srinivas

RNIF Angled brackets in the Content Id in the attachment

Hello All,
I'm working on an RNIF interface with a PIDX message and an attachment . Everything is working fine until this new requirement came up . The partner that we are communicating with needs the content-id of the attachment to be enclosed in angled brackets <>. I know that this issue has been resolved in PI 7.1 EHP1 , but we are on PI 7.0 .
Please let me know if there is a support pack in 7.0 for this and if so which one . Thanks.

Hi
The parameter is not available for SP14. Note #1554216 is a relatively new note. SAP will generally provide fixes for the previous 3 SP releases (e.g. SP24, SP23 and SP22 in this case).
It looks like this specific fix was provided for a customer on SP12. I guess you will need to request they do the same for your SP14 release (if upgrading is not an option for you).
Regards
Mark

XI, PIDX and RNIF.

Similar Messages

Maybe you are looking for