Mix B2B and A2A in integration scenario

Hello XI experts,
I'm trying to build an integration scenario in the repository that I want to import later on into the directory for automatic configuration.
The scenario is HTTP -> XI -> RFC. On the sender side I would like to use a business service, so I selected 'External party with B2B communication' for the sending application component. On the receiver side I would like to use a SAP business system, so I didn't select that option there.
Now, if I import into the directory, this doesn't work as expected. I can select my business service for the sender side, this works. However, for the receiver side I always have to specify a virtual receiver service and my receiver determination and interface determination are created with a virtual receiver service in it.
Is there any way to avoid the virtual receiver? Any help is appreciated!
Best regards,
Matthias

Hello Aamir,
you are right, I don't need virtual receivers for my scenaro and I also don't want to use them.
However, when modelling my scenario with an integration scenario in the design, I'm forced to do this and I would like to know whether there is any way to avoid this.
In order to be able to use a business service on the sender side, it seems I have to select the checkbox 'External party with B2B communication' in my integration scenario. When importing & configuring the scenario in the directory, I am then able to select by business service for the sender side. However, for the receiver side I have to specify a virtual receiver, otherwise I cannot finish the config wizard.
Any more ideas?
Best regards,
Matthias

Similar Messages

Differentiation between B2B and A2A

Hi,
Can anybody give me a real time example between B2B and A2A in general and XI Perspective?
Points Assured
Regards,
B.Anandh

Anandha Krishnan
Here is some more info to top up
Think, Company A is dealing only with Legacy Systems or Java Based applications, but Company B cannot directly understand COmpany A's format. So the Integration Broker like XI will come into picture. While integrating Company A should know how feasible it can communicate with Company B.. More in technical, is thru WebServices Industry Standard Adapters(Seeburger EDI)/(SOAP)/Java Applications(JavaProxy)/.net Applications etc..
Thanks 2 Krishnamoorthy P
Also Check the following help doc
http://help.sap.com/saphelp_nw04s/helpdata/en/15/5f934249c30c31e10000000a1550b0/frameset.htm
regards
krishna

ALE/IDOC and RFC/BAPI Integration Scenarios with SAP DS for ESA v3

Hi,
we are planning two PoCs of Integration Plattforms. One of our major requirement set is SAP Integration into our existing SOA.
Because we also have R/3 4.7 Systems in production, we are planning to test ALE/IDOC and RFC/BAPI Integration scenarios with these Integration Plattforms.
My question is:
We are looking for are smart solution to get a SAP Test Environment, where we can test ALE/IDOC und RFC/BAPI Integration scenarios.
It is possible to do this with SAP DS for ESA v3 or shall we better use IDES for that purpose?
Best regards,
Steven

Hi Abhishek,
This is our scenario. We are doing an integration of SAP HR r/3 system with the CRM system. We need housing information details of the employees which we have in custom infotype 9310 in SAP HR system and we need those details in the CRM system. So am planning out for an ALE/IDOC approach for the integration and gonna maintain the 9310 details in a custom table. In the CRM system, we gonna build a BOL layer for accessing the 9310 details. Also i'm preparing a HLD for this process. I wanna read and go through few same HLD's before i submit my proposal to my client. Please suggest me and help me out.
Thanks in advance.
Regards,
Arunmozhi.

B2B and A2A

Hi,
Explain B2B and A2A concepts.Do we need more than one one SLD when it is B2B?

Wrong forum.

CCM and R/3 integration scenario through XI

hello People,
We need to take the material master data from R/3 to CCM.
IS there any XI scenario available for this?
If Yes...where can i find it?
IF No...How much time will it take to develop such a scenario?
Regards
Abhishek.

Hi,
I have emailed this to you.
The senario you want in MasterDataInclusionInCaralogOnWAS700 (or 640 dependant).
Once the material have been replicated from R3 you run transaction BP_CCM_TRANSFER to transfer these to CCM. This then goes through XI into your CCM catalog, and in need you can publish these automatically.
Regards
Rob

To SAP-XI Product Developement... Bug in Integration Scenario, swimlanes..?

Hi,
I am not sure whether such questions can be posted in this forum or not.. but i have no other alternative. If this is not the right forum i will not post such queries again.
I have posted a query reg "Integration Scenario, swimlane diagrams" in XI Forum, but there were no replies to that. So i like to forward the same to the Product Develpment team and like to know if this is a bug or things do work like this..?
I have designed my Integration Scenario in Design Time, imported the same into configuraton time so that the Configuration Objects (Receiver Determination, Interface Determinaiton, Receiver agreements) are automatically created. I tried the sacenario and its working fine.
In my scenario, i have 3 swimlanes corresponding systems, Sys1, sys2, sys3.
In Run1, a connection is made b/n sys1's and sys2's actions. Imported into Configuration, Configuration objects created,(Rx Determination Created) scenario working properly.
In Run2, another connection is made b/n sys1 and sys3's actions (sys1 and sys2 still remain connected). Imported into Configuration, receiver determinaition changed according to the scenario, scenario working properly.
In Run3, the connection b/n sys1 and sys2 is removed and again imported into configuration, but the receiver determination is not changed to cater to the scenario in design time. The old receiver determinaiton is not getting deleted/chaged). The receiver deteminaiton reused instead of being changed, which is incorrect according to the scenario.
Is this a bug in the software or do things work like this only... U can reach me at Siva_Maranani(at)satyam(dot)com
Cheers,
Siva Maranani.

Hello Aamir,
you are right, I don't need virtual receivers for my scenaro and I also don't want to use them.
However, when modelling my scenario with an integration scenario in the design, I'm forced to do this and I would like to know whether there is any way to avoid this.
In order to be able to use a business service on the sender side, it seems I have to select the checkbox 'External party with B2B communication' in my integration scenario. When importing & configuring the scenario in the directory, I am then able to select by business service for the sender side. However, for the receiver side I have to specify a virtual receiver, otherwise I cannot finish the config wizard.
Any more ideas?
Best regards,
Matthias

SCENARIO CREATION IN INTEGRATION SCENARIO

hi
I have one sender and two receivers. I am creating integration scenario in repository. in integration scenario creation i have to create three swim lanes or
two swim lanes? can i add both receivers in one swim lane? and how will i made
connection between sender and both receivers?
can any one please help me?
thanks&regards
venkat

Hi Venky,
I guess you will be sending the same data to both receivers.
So you do not have to use 3 swim lanes. Create only 2 swim lane.
1. One for Sender
2. Second one for Receiver (no need to think here for 2 receivers, think it when you do receiver determination)
Now, Making a connection will be very easy, just select the ACTION of Sender and Receiver and right click and say create connections.
For creating and working with integration scenario just go through the below link:
/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi
/people/venkat.donela/blog/2006/02/17/companion-guide-to-integration-scenario
/people/shailesh.mane/blog/2006/06/27/b2b-configuration-part-i--creating-an-integration-scenario
/people/shailesh.mane/blog/2006/06/29/b2b-configuration-part-ii--creating-the-configuration-using-the-automated-configuration-tool
If need more help, just reply back.
Regards,
Sarvesh
****Reward Points if it helped you.
Message was edited by:
Sarvesh Singh

Integration Scenario Configurator

Hello!
I want to generate the receiver determination for an integration process on XI 3.0 SP10 with the Integration Scenario Configurator.
I have created an Integration Scenario in the Integration Repository, there are no errors when checking with F7.
If I open it in the Integration Directory and go to Integration Scenario Configurator -> Check Configurability I get the following error message:
"Component View /Role <my Integration Process>: Only connections with interfaces that belong to the integration process interface are permitted"
What does the error message mean? What do I need to change to eliminate this error message?
The connections point to interfaces I have defined in the same software component as the integration scenario and process. For the integration process I have created abstract interfaces.
Regards, Tanja

Hi Simon!
I was able to solve this problem some weeks ago but thanks for your hint anyway.
As you have mentioned the problem was that in the Integration Repository the integration scenario was not consistent with the used integration process as it contained a wrong interface.
After I have corrected the integration process in the Integration Repository and updated the changes in the Integration Directory the generation with the Integration Scenario Configurator worked without any problems and the status of the process changed to 0 in SXI_CACHE.
Regards, Tanja

Integration Scenario

Hi All,
I am new to XI. I need to know about Integration Scenario. What is it? Why we are using Integration Scenario? How it differs from Integration Process? and how to use Integration Scenario? Give a simple example (like file to file using Integration Scenario).
Thanks and Regards,
Nithya

Hi,
>>>Integration Scenario,Why we are using Integration Scenario,how to use Integration Scenario
Integration scenario is used to logically relate all XI objects for a particular scenario. It also eases the creation of configuration objects.
You use an integration scenario to define the message exchange and message flow for collaborative processes. Normally, these are processes between different business partners that are generally coupled by the exchange of messages.
The integration scenario provides you with a central point of access for all objects that you require for semantic and technical integration, for example interfaces, mappings, and software components.
You can integrate an executable integration process into an integration scenario.
Follow the blogs for more details:
/people/siva.maranani/blog/2005/08/27/modeling-integration-scenario146s-in-xi
/people/venkat.donela/blog/2006/02/17/companion-guide-to-integration-scenario
http://help.sap.com/saphelp_nw2004s/helpdata/en/88/7adb7a030b424b8ef29b99461e52a8/content.htm
Modelling Integration Scenarios in XI
Integration Scenario
Integration Scenario
>>> Integration Process
An integration process is an executable, cross-system process for processing messages. In an integration process you define all the process steps that are to be executed and the parameters relevant for controlling the process.
You implement integration processes when you want to define, control, and monitor complex integration processes that extend across enterprise and application boundaries. The design and processing of integration processes is also known as cross-component Business Process Management (cross-component BPM, ccBPM).
Please refer http://help.sap.com/saphelp_nw04/helpdata/en/3c/831620a4f1044dba38b370f77835cc/content.htm
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful

BI7.0 and MDM(sp06) Integration

Hi,
I am working on BI7 and MDM(sp06) integration scenario through ABAP APIs. For this scenario which support packs and API's need to install in BI server and where can I found complete information about integration..... plzz provide some documentation and some links which can guide me..
Thanx in Advance.
Rgds,
Ram

Hi Reddy,
Go to [http://service.sap.com/swdc] --> Support packages and patches --> Entry by application group --> SAP NetWeaver --> SAP MDM
You will get JAVA APIs and Portal Content there.
go through this link...
[How to define portal system to access MDM server;
For a pretty good introduction to MDM workflow, see the following article: [https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/9180cbaf-0801-0010-f882-f2af6dc975d0.]
[MDM Workflow - Please help a student!;
regards,
NR

Integration Scenario Configuator and Business Services (B2B)

We use Business Services to define the services provided by our external business partners (e.g. a transport organization has defined some webservices to which we connect to).
The reason why we use Business Services is that we don't have to define them in the SLD. And we understand from the documentation that external business systems should be defined as Business Services and not Business Systems.
Now we want to use the Integration Scenario Configurator, but when we define a B2B service in the Integation Scenario, we cannot create the communication channels with the wizard. Futhermore the other object (receiver determination etc.) is also not created for the business service.
When we take a look at the definition of a B2B scenario in the SAP documentation, the documentation describes a complete different use of B2B. We understand from the documentation that B2B is a cross company XI landscape where all partners have there own XI system. This also explains the behavure in the configurator since one party cannot access its own business systems.
This leaves us with the following questions:
1. Is B2B only possible for XI to XI scenario's?
2. Is a service provided by a partner a business system?
3. And do we have to include all communication end point in the SLD?
Kind regards,
Christiaan Schaake

Dear Christiaan,
I encountered the same problem. What I did was that I created a party for the external business partner and assigned a business service to it. Beside this you have to check the box (ext. party w. B2B comm) under communication type in the application component in the integration scenario.
When you have done this you can create comm. channel with the wizard and also the other objects.
see: http://help.sap.com/saphelp_nw2004s/helpdata/en/e6/908d3f7057eb0ce10000000a114084/content.htm
Regarding your questions: depending on the way we think, we can come up with different answers. I don't think this is what you're looking for.
Maybe someone else can give you a clear answer.
Kind Regards
Ron van Steen

Urgent : Search a Demo with B2B and Ebiz integration

Hi all,
I'm in a search for a Demo with a scenario for outbound or inbound flows, integrating Oracle B2B and Ebiz, if the Ebiz Adapter is used it will be great.
Thanks for your help.

If you are an Oracle employee then please get in touch with B2B PM's otherwise drop a note to my id (in my profile)
Regards,
Anuj

Integration between B2B and ESB error (DOM Parsing Exception in translator)

Hello,
We have configured a circuit that has the objective of sending a message to B2B and then the ESB dequeues that message from the IP_IN_QUEUE.
The problem is that for some reason, the ESB cannot read message using the AQ Adapter object.
The error is the following:
DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
The trace is the following:
ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:139) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1609) at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1514) at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1447) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1286) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:134) ... 8 more
The Payload is the following:
<?xml version="1.0" ?><OMG_O19 xmlns="urn:oracle:integration:b2b:C023D5B231EF45519AA3D9929B4990E1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.4" CreatedDate="2007-07-17T17:10:43" CreatedBy="ECXEngine_837" GUID="{D16D28B9-3821-4BCC-B4D9-0D92F8611BB5}"><Internal-Properties><Data-Structure Name="Message"><Lookup Name="MessageSendingApp">ALERT</Lookup><Lookup Name="MessageSendingAppUniversalID"></Lookup><Lookup Name="MessageSendingAppUniversalIDType"></Lookup><Lookup Name="MessageSendingFacility">CHVNG</Lookup><Lookup Name="MessageSendingFacilityUniversalID"></Lookup><Lookup Name="MessageSendingFacilityUniversalIDType"></Lookup><Lookup Name="MessageReceivingApp">RADIO</Lookup><Lookup Name="MessageReceivingAppUniversalID"></Lookup><Lookup Name="MessageReceivingAppUniversalIDType"></Lookup><Lookup Name="MessageReceivingFacility">CHVNG</Lookup><Lookup Name="MessageReceivingFacilityUniversalID"></Lookup><Lookup Name="MessageReceivingFacilityUniversalIDType"></Lookup><Lookup Name="MessageCode">OMG</Lookup><Lookup Name="TriggerEvent">O19</Lookup><Lookup Name="MessageStructure">OMG_O19</Lookup><Lookup Name="MessageVersion">2.4</Lookup><Lookup Name="InternatCodeID"></Lookup><Lookup Name="InternatCodeText"></Lookup><Lookup Name="InternatCodeSystem"></Lookup><Lookup Name="InternatCodeAlternateID"></Lookup><Lookup Name="InternatCodeAlternateText"></Lookup><Lookup Name="InternatCodeAlternateSystem"></Lookup><Lookup Name="InternationalVersionID"></Lookup><Lookup Name="InternationalVersionIDText"></Lookup><Lookup Name="InternationalVersionIDSystem"></Lookup><Lookup Name="InternationalVersionIDAlternateID"></Lookup><Lookup Name="InternationalVersionIDAlternateText"></Lookup><Lookup Name="InternationalVersionIDAlternateSystem"></Lookup><Lookup Name="Standard">HL7</Lookup><Property Name="MessageEncodingCharacters">^~\&</Property><Property Name="MessageSendingApp">ALERT</Property><Property Name="MessageSendingAppUniversalID"></Property><Property Name="MessageSendingAppUniversalIDType"></Property><Property Name="MessageSendingFacility">CHVNG</Property><Property Name="MessageSendingFacilityUniversalID"></Property><Property Name="MessageSendingFacilityUniversalIDType"></Property><Property Name="MessageReceivingApp">RADIO</Property><Property Name="MessageReceivingAppUniversalID"></Property><Property Name="MessageReceivingAppUniversalIDType"></Property><Property Name="MessageReceivingFacility">CHVNG</Property><Property Name="MessageReceivingFacilityUniversalID"></Property><Property Name="MessageReceivingFacilityUniversalIDType"></Property><Property Name="MessageDate">20070705161247+0000</Property><Property Name="MessageDateTimePrecision"></Property><Property Name="MessageSecurity"></Property><Property Name="MessageCode">OMG</Property><Property Name="TriggerEvent">O19</Property><Property Name="MessageStructure">OMG_O19</Property><Property Name="MessageControlID">1709</Property><Property Name="ProcessingID">P</Property><Property Name="ProcessingMode"></Property><Property Name="MessageVersion">2.4</Property><Property Name="InternatCodeID"></Property><Property Name="InternatCodeText"></Property><Property Name="InternatCodeSystem"></Property><Property Name="InternatCodeAlternateID"></Property><Property Name="InternatCodeAlternateText"></Property><Property Name="InternatCodeAlternateSystem"></Property><Property Name="InternationalVersionID"></Property><Property Name="InternationalVersionIDText"></Property><Property Name="InternationalVersionIDSystem"></Property><Property Name="InternationalVersionIDAlternateID"></Property><Property Name="InternationalVersionIDAlternateText"></Property><Property Name="InternationalVersionIDAlternateSystem"></Property><Property Name="SequenceNumber"></Property><Property Name="ContinuationPointer"></Property><Property Name="AcceptAckType"></Property><Property Name="AppAckType"></Property><Property Name="CountryCode"></Property><Property Name="CharacterSet"></Property><Property Name="LanguageID"></Property><Property Name="LanguageText"></Property><Property Name="LanguageSystem"></Property><Property Name="LanguageAlternateID"></Property><Property Name="LanguageAlternateText"></Property><Property Name="LanguageAlternateSystem"></Property><Property Name="AlternateCharacterSetSchema"></Property><Property Name="ConformanceStatementID"></Property><Property Name="MessageProfileNamespaceID"></Property><Property Name="MessageProfileUniversalID"></Property><Property Name="MessageProfileUniversalIDType"></Property><Property Name="DecimalSeparator"></Property><Property Name="ElementDelimiter">0x7c</Property><Property Name="ReleaseCharacter">0x5c</Property><Property Name="RepeatingSeparator">0x7e</Property><Property Name="SegmentDelimiter">0xd</Property><Property Name="SubcomponentDelimiter">0x26</Property><Property Name="SubelementDelimiter">0x5e</Property></Data-Structure></Internal-Properties><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>ALERT</HD.1></MSH.3><MSH.4><HD.1>CHVNG</HD.1></MSH.4><MSH.5><HD.1>RADIO</HD.1></MSH.5><MSH.6><HD.1>CHVNG</HD.1></MSH.6><MSH.7><TS.1>20070705161247+0000</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>OMG</MSG.1><MSG.2>O19</MSG.2><MSG.3>OMG_O19</MSG.3></MSH.9><MSH.10>1709</MSH.10><MSH.11><PT.1>P</PT.1></MSH.11><MSH.12><VID.1>2.4</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13></MSH><Extra-
PID><Extra-
PID.1 xsi:nil="true"></Extra-
PID.1><Extra-
PID.2 xsi:nil="true"></Extra-
PID.2><Extra-
PID.3><Extra-
PID.3.1>390971</Extra-
PID.3.1><Extra-
PID.3.2 xsi:nil="true"></Extra-
PID.3.2><Extra-
PID.3.3 xsi:nil="true"></Extra-
PID.3.3><Extra-
PID.3.4>CHVNG</Extra-
PID.3.4><Extra-
PID.3.5>NS</Extra-
PID.3.5></Extra-
PID.3><Extra-
PID.4 xsi:nil="true"></Extra-
PID.4><Extra-
PID.5><Extra-
PID.5.1>Santos</Extra-
PID.5.1><Extra-
PID.5.2>Paula</Extra-
PID.5.2><Extra-
PID.5.3>Cristina Silva Lopes</Extra-
PID.5.3></Extra-
PID.5><Extra-
PID.6 xsi:nil="true"></Extra-
PID.6><Extra-
PID.7>19720117000000+0000</Extra-
PID.7><Extra-
PID.8 xsi:nil="true"></Extra-
PID.8><Extra-
PID.9 xsi:nil="true"></Extra-
PID.9><Extra-
PID.10 xsi:nil="true"></Extra-
PID.10><Extra-
PID.11><Extra-
PID.11.1>R Bernardino Costa 358 Bl D Hab 04</Extra-
PID.11.1><Extra-
PID.11.2 xsi:nil="true"></Extra-
PID.11.2><Extra-
PID.11.3>Valadares</Extra-
PID.11.3><Extra-
PID.11.4 xsi:nil="true"></Extra-
PID.11.4><Extra-
PID.11.5>4405</Extra-
PID.11.5></Extra-
PID.11><Extra-
PID.12 xsi:nil="true"></Extra-
PID.12><Extra-
PID.13 xsi:nil="true"></Extra-
PID.13><Extra-
PID.14 xsi:nil="true"></Extra-
PID.14><Extra-
PID.15 xsi:nil="true"></Extra-
PID.15><Extra-
PID.16 xsi:nil="true"></Extra-
PID.16><Extra-
PID.17 xsi:nil="true"></Extra-
PID.17><Extra-
PID.18>7011588</Extra-
PID.18><Extra-
PID.19 xsi:nil="true"></Extra-
PID.19></Extra-
PID><Extra-
PV1><Extra-
PV1.1 xsi:nil="true"></Extra-
PV1.1><Extra-
PV1.2>URG</Extra-
PV1.2><Extra-
PV1.3><Extra-
PV1.3.1>1</Extra-
PV1.3.1><Extra-
PV1.3.2 xsi:nil="true"></Extra-
PV1.3.2><Extra-
PV1.3.3 xsi:nil="true"></Extra-
PV1.3.3><Extra-
PV1.3.4>CHVNG</Extra-
PV1.3.4></Extra-
PV1.3><Extra-
PV1.4 xsi:nil="true"></Extra-
PV1.4><Extra-
PV1.5 xsi:nil="true"></Extra-
PV1.5><Extra-
PV1.6 xsi:nil="true"></Extra-
PV1.6><Extra-
PV1.7 xsi:nil="true"></Extra-
PV1.7><Extra-
PV1.8 xsi:nil="true"></Extra-
PV1.8><Extra-
PV1.9 xsi:nil="true"></Extra-
PV1.9><Extra-
PV1.10 xsi:nil="true"></Extra-
PV1.10><Extra-
PV1.11 xsi:nil="true"></Extra-
PV1.11><Extra-
PV1.12 xsi:nil="true"></Extra-
PV1.12><Extra-
PV1.13 xsi:nil="true"></Extra-
PV1.13><Extra-
PV1.14 xsi:nil="true"></Extra-
PV1.14><Extra-
PV1.15 xsi:nil="true"></Extra-
PV1.15><Extra-
PV1.16 xsi:nil="true"></Extra-
PV1.16><Extra-
PV1.17 xsi:nil="true"></Extra-
PV1.17><Extra-
PV1.18>URG</Extra-
PV1.18><Extra-
PV1.19><Extra-
PV1.19.1>7088430</Extra-
PV1.19.1><Extra-
PV1.19.2 xsi:nil="true"></Extra-
PV1.19.2><Extra-
PV1.19.3 xsi:nil="true"></Extra-
PV1.19.3><Extra-
PV1.19.4>SONHO</Extra-
PV1.19.4></Extra-
PV1.19><Extra-
PV1.20 xsi:nil="true"></Extra-
PV1.20><Extra-
PV1.21 xsi:nil="true"></Extra-
PV1.21><Extra-
PV1.22 xsi:nil="true"></Extra-
PV1.22><Extra-
PV1.23 xsi:nil="true"></Extra-
PV1.23><Extra-
PV1.24 xsi:nil="true"></Extra-
PV1.24><Extra-
PV1.25 xsi:nil="true"></Extra-
PV1.25><Extra-
PV1.26 xsi:nil="true"></Extra-
PV1.26><Extra-
PV1.27 xsi:nil="true"></Extra-
PV1.27><Extra-
PV1.28 xsi:nil="true"></Extra-
PV1.28><Extra-
PV1.29 xsi:nil="true"></Extra-
PV1.29><Extra-
PV1.30 xsi:nil="true"></Extra-
PV1.30><Extra-
PV1.31 xsi:nil="true"></Extra-
PV1.31><Extra-
PV1.32 xsi:nil="true"></Extra-
PV1.32><Extra-
PV1.33 xsi:nil="true"></Extra-
PV1.33><Extra-
PV1.34 xsi:nil="true"></Extra-
PV1.34><Extra-
PV1.35 xsi:nil="true"></Extra-
PV1.35><Extra-
PV1.36 xsi:nil="true"></Extra-
PV1.36><Extra-
PV1.37 xsi:nil="true"></Extra-
PV1.37><Extra-
PV1.38 xsi:nil="true"></Extra-
PV1.38><Extra-
PV1.39 xsi:nil="true"></Extra-
PV1.39><Extra-
PV1.40 xsi:nil="true"></Extra-
PV1.40><Extra-
PV1.41 xsi:nil="true"></Extra-
PV1.41><Extra-
PV1.42 xsi:nil="true"></Extra-
PV1.42><Extra-
PV1.43 xsi:nil="true"></Extra-
PV1.43><Extra-
PV1.44>20070705154838+0000</Extra-
PV1.44><Extra-
PV1.45 xsi:nil="true"></Extra-
PV1.45><Extra-
PV1.46 xsi:nil="true"></Extra-
PV1.46><Extra-
PV1.47 xsi:nil="true"></Extra-
PV1.47><Extra-
PV1.48 xsi:nil="true"></Extra-
PV1.48><Extra-
PV1.49 xsi:nil="true"></Extra-
PV1.49><Extra-
PV1.50 xsi:nil="true"></Extra-
PV1.50><Extra-
PV1.51>V</Extra-
PV1.51><Extra-
PV1.52 xsi:nil="true"></Extra-
PV1.52></Extra-
PV1><Extra-
ORC><Extra-
ORC.1>NW</Extra-
ORC.1><Extra-
ORC.2><Extra-
ORC.2.1>19013</Extra-
ORC.2.1><Extra-
ORC.2.2>ALERT</Extra-
ORC.2.2></Extra-
ORC.2><Extra-
ORC.3 xsi:nil="true"></Extra-
ORC.3><Extra-
ORC.4 xsi:nil="true"></Extra-
ORC.4><Extra-
ORC.5>NW</Extra-
ORC.5><Extra-
ORC.6 xsi:nil="true"></Extra-
ORC.6><Extra-
ORC.7 xsi:nil="true"></Extra-
ORC.7><Extra-
ORC.8 xsi:nil="true"></Extra-
ORC.8><Extra-
ORC.9 xsi:nil="true"></Extra-
ORC.9><Extra-
ORC.10 xsi:nil="true"></Extra-
ORC.10><Extra-
ORC.11 xsi:nil="true"></Extra-
ORC.11><Extra-
ORC.12><Extra-
ORC.12.1>4292</Extra-
ORC.12.1><Extra-
ORC.12.2>Martinez</Extra-
ORC.12.2><Extra-
ORC.12.3>Cristina</Extra-
ORC.12.3></Extra-
ORC.12><Extra-
ORC.13 xsi:nil="true"></Extra-
ORC.13></Extra-
ORC><Extra-
OBR><Extra-
OBR.1>1</Extra-
OBR.1><Extra-
OBR.2><Extra-
OBR.2.1>19013</Extra-
OBR.2.1><Extra-
OBR.2.2>ALERT</Extra-
OBR.2.2></Extra-
OBR.2><Extra-
OBR.3 xsi:nil="true"></Extra-
OBR.3><Extra-
OBR.4><Extra-
OBR.4.1>10781</Extra-
OBR.4.1><Extra-
OBR.4.2>M<escape V="XE3"/>o direita, duas incid<escape V="XEA"/>ncias</Extra-
OBR.4.2><Extra-
OBR.4.3>CHVNG</Extra-
OBR.4.3></Extra-
OBR.4><Extra-
OBR.5 xsi:nil="true"></Extra-
OBR.5><Extra-
OBR.6 xsi:nil="true"></Extra-
OBR.6><Extra-
OBR.7 xsi:nil="true"></Extra-
OBR.7><Extra-
OBR.8 xsi:nil="true"></Extra-
OBR.8><Extra-
OBR.9 xsi:nil="true"></Extra-
OBR.9><Extra-
OBR.10 xsi:nil="true"></Extra-
OBR.10><Extra-
OBR.11 xsi:nil="true"></Extra-
OBR.11><Extra-
OBR.12 xsi:nil="true"></Extra-
OBR.12><Extra-
OBR.13 xsi:nil="true"></Extra-
OBR.13><Extra-
OBR.14 xsi:nil="true"></Extra-
OBR.14><Extra-
OBR.15 xsi:nil="true"></Extra-
OBR.15><Extra-
OBR.16><Extra-
OBR.16.1>4292</Extra-
OBR.16.1><Extra-
OBR.16.2>Martinez</Extra-
OBR.16.2><Extra-
OBR.16.3>Cristina</Extra-
OBR.16.3></Extra-
OBR.16><Extra-
OBR.17 xsi:nil="true"></Extra-
OBR.17><Extra-
OBR.18 xsi:nil="true"></Extra-
OBR.18><Extra-
OBR.19 xsi:nil="true"></Extra-
OBR.19><Extra-
OBR.20 xsi:nil="true"></Extra-
OBR.20><Extra-
OBR.21 xsi:nil="true"></Extra-
OBR.21><Extra-
OBR.22 xsi:nil="true"></Extra-
OBR.22><Extra-
OBR.23 xsi:nil="true"></Extra-
OBR.23><Extra-
OBR.24 xsi:nil="true"></Extra-
OBR.24><Extra-
OBR.25 xsi:nil="true"></Extra-
OBR.25><Extra-
OBR.26 xsi:nil="true"></Extra-
OBR.26><Extra-
OBR.27><Extra-
OBR.27.1 xsi:nil="true"></Extra-
OBR.27.1><Extra-
OBR.27.2 xsi:nil="true"></Extra-
OBR.27.2><Extra-
OBR.27.3 xsi:nil="true"></Extra-
OBR.27.3><Extra-
OBR.27.4>20070705161237+0000</Extra-
OBR.27.4></Extra-
OBR.27><Extra-
OBR.28 xsi:nil="true"></Extra-
OBR.28></Extra-
OBR><Extra-
NTE><Extra-
NTE.1>1</Extra-
NTE.1><Extra-
NTE.2 xsi:nil="true"></Extra-
NTE.2></Extra-
NTE><Extra-
DG1><Extra-
DG1.1>1</Extra-
DG1.1><Extra-
DG1.2 xsi:nil="true"></Extra-
DG1.2><Extra-
DG1.3><Extra-
DG1.3.1>9233</Extra-
DG1.3.1><Extra-
DG1.3.2>Contusao De Dedo Da Mao</Extra-
DG1.3.2><Extra-
DG1.3.3>ICD9</Extra-
DG1.3.3></Extra-
DG1.3><Extra-
DG1.4 xsi:nil="true"></Extra-
DG1.4><Extra-
DG1.5 xsi:nil="true"></Extra-
DG1.5><Extra-
DG1.6>D</Extra-
DG1.6></Extra-
DG1></OMG_O19>
I think that the problem should be because of the "Extra" (eg. <Extra-
PID.1 xsi:nil="true">) word that B2B puts in every tag.
The strange thing is that, this already worked until two days ago....
What could it be?
Thanks for your help.
Best Regards,
Nuno Fernandes

Hello,
We have configured a circuit that has the objective of sending a message to B2B and then the ESB dequeues that message from the IP_IN_QUEUE.
The problem is that for some reason, the ESB cannot read message using the AQ Adapter object.
The error is the following:
DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable.
The trace is the following:
ORABPEL-11211 DOM Parsing Exception in translator. DOM parsing exception in inbound XSD translator while parsing InputStream. Check the error stack and fix the cause of the error. Contact oracle support if error is not fixable. at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:139) at oracle.tip.adapter.aq.database.MessageReader.translateFromNative(MessageReader.java:1179) at oracle.tip.adapter.aq.database.MessageReader.readMessage(MessageReader.java:533) at oracle.tip.adapter.aq.inbound.AQActivationSpecDequeuer.run(AQActivationSpecDequeuer.java:189) at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242) at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215) at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190) at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819) at java.lang.Thread.run(Thread.java:595) Caused by: oracle.xml.parser.v2.XMLParseException: '=' missing in attribute. at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:320) at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1609) at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1514) at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1447) at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1286) at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:336) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:303) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:291) at oracle.tip.pc.services.translation.xlators.xsd.XSDTranslator.translateFromNative(XSDTranslator.java:134) ... 8 more
The Payload is the following:
<?xml version="1.0" ?><OMG_O19 xmlns="urn:oracle:integration:b2b:C023D5B231EF45519AA3D9929B4990E1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" XDataVersion="2.0" Standard="HL7" Version="2.4" CreatedDate="2007-07-17T17:10:43" CreatedBy="ECXEngine_837" GUID="{D16D28B9-3821-4BCC-B4D9-0D92F8611BB5}"><Internal-Properties><Data-Structure Name="Message"><Lookup Name="MessageSendingApp">ALERT</Lookup><Lookup Name="MessageSendingAppUniversalID"></Lookup><Lookup Name="MessageSendingAppUniversalIDType"></Lookup><Lookup Name="MessageSendingFacility">CHVNG</Lookup><Lookup Name="MessageSendingFacilityUniversalID"></Lookup><Lookup Name="MessageSendingFacilityUniversalIDType"></Lookup><Lookup Name="MessageReceivingApp">RADIO</Lookup><Lookup Name="MessageReceivingAppUniversalID"></Lookup><Lookup Name="MessageReceivingAppUniversalIDType"></Lookup><Lookup Name="MessageReceivingFacility">CHVNG</Lookup><Lookup Name="MessageReceivingFacilityUniversalID"></Lookup><Lookup Name="MessageReceivingFacilityUniversalIDType"></Lookup><Lookup Name="MessageCode">OMG</Lookup><Lookup Name="TriggerEvent">O19</Lookup><Lookup Name="MessageStructure">OMG_O19</Lookup><Lookup Name="MessageVersion">2.4</Lookup><Lookup Name="InternatCodeID"></Lookup><Lookup Name="InternatCodeText"></Lookup><Lookup Name="InternatCodeSystem"></Lookup><Lookup Name="InternatCodeAlternateID"></Lookup><Lookup Name="InternatCodeAlternateText"></Lookup><Lookup Name="InternatCodeAlternateSystem"></Lookup><Lookup Name="InternationalVersionID"></Lookup><Lookup Name="InternationalVersionIDText"></Lookup><Lookup Name="InternationalVersionIDSystem"></Lookup><Lookup Name="InternationalVersionIDAlternateID"></Lookup><Lookup Name="InternationalVersionIDAlternateText"></Lookup><Lookup Name="InternationalVersionIDAlternateSystem"></Lookup><Lookup Name="Standard">HL7</Lookup><Property Name="MessageEncodingCharacters">^~\&</Property><Property Name="MessageSendingApp">ALERT</Property><Property Name="MessageSendingAppUniversalID"></Property><Property Name="MessageSendingAppUniversalIDType"></Property><Property Name="MessageSendingFacility">CHVNG</Property><Property Name="MessageSendingFacilityUniversalID"></Property><Property Name="MessageSendingFacilityUniversalIDType"></Property><Property Name="MessageReceivingApp">RADIO</Property><Property Name="MessageReceivingAppUniversalID"></Property><Property Name="MessageReceivingAppUniversalIDType"></Property><Property Name="MessageReceivingFacility">CHVNG</Property><Property Name="MessageReceivingFacilityUniversalID"></Property><Property Name="MessageReceivingFacilityUniversalIDType"></Property><Property Name="MessageDate">20070705161247+0000</Property><Property Name="MessageDateTimePrecision"></Property><Property Name="MessageSecurity"></Property><Property Name="MessageCode">OMG</Property><Property Name="TriggerEvent">O19</Property><Property Name="MessageStructure">OMG_O19</Property><Property Name="MessageControlID">1709</Property><Property Name="ProcessingID">P</Property><Property Name="ProcessingMode"></Property><Property Name="MessageVersion">2.4</Property><Property Name="InternatCodeID"></Property><Property Name="InternatCodeText"></Property><Property Name="InternatCodeSystem"></Property><Property Name="InternatCodeAlternateID"></Property><Property Name="InternatCodeAlternateText"></Property><Property Name="InternatCodeAlternateSystem"></Property><Property Name="InternationalVersionID"></Property><Property Name="InternationalVersionIDText"></Property><Property Name="InternationalVersionIDSystem"></Property><Property Name="InternationalVersionIDAlternateID"></Property><Property Name="InternationalVersionIDAlternateText"></Property><Property Name="InternationalVersionIDAlternateSystem"></Property><Property Name="SequenceNumber"></Property><Property Name="ContinuationPointer"></Property><Property Name="AcceptAckType"></Property><Property Name="AppAckType"></Property><Property Name="CountryCode"></Property><Property Name="CharacterSet"></Property><Property Name="LanguageID"></Property><Property Name="LanguageText"></Property><Property Name="LanguageSystem"></Property><Property Name="LanguageAlternateID"></Property><Property Name="LanguageAlternateText"></Property><Property Name="LanguageAlternateSystem"></Property><Property Name="AlternateCharacterSetSchema"></Property><Property Name="ConformanceStatementID"></Property><Property Name="MessageProfileNamespaceID"></Property><Property Name="MessageProfileUniversalID"></Property><Property Name="MessageProfileUniversalIDType"></Property><Property Name="DecimalSeparator"></Property><Property Name="ElementDelimiter">0x7c</Property><Property Name="ReleaseCharacter">0x5c</Property><Property Name="RepeatingSeparator">0x7e</Property><Property Name="SegmentDelimiter">0xd</Property><Property Name="SubcomponentDelimiter">0x26</Property><Property Name="SubelementDelimiter">0x5e</Property></Data-Structure></Internal-Properties><MSH><MSH.1>|</MSH.1><MSH.2>^~\&</MSH.2><MSH.3><HD.1>ALERT</HD.1></MSH.3><MSH.4><HD.1>CHVNG</HD.1></MSH.4><MSH.5><HD.1>RADIO</HD.1></MSH.5><MSH.6><HD.1>CHVNG</HD.1></MSH.6><MSH.7><TS.1>20070705161247+0000</TS.1></MSH.7><MSH.8 xsi:nil="true"></MSH.8><MSH.9><MSG.1>OMG</MSG.1><MSG.2>O19</MSG.2><MSG.3>OMG_O19</MSG.3></MSH.9><MSH.10>1709</MSH.10><MSH.11><PT.1>P</PT.1></MSH.11><MSH.12><VID.1>2.4</VID.1></MSH.12><MSH.13 xsi:nil="true"></MSH.13></MSH><Extra-
PID><Extra-
PID.1 xsi:nil="true"></Extra-
PID.1><Extra-
PID.2 xsi:nil="true"></Extra-
PID.2><Extra-
PID.3><Extra-
PID.3.1>390971</Extra-
PID.3.1><Extra-
PID.3.2 xsi:nil="true"></Extra-
PID.3.2><Extra-
PID.3.3 xsi:nil="true"></Extra-
PID.3.3><Extra-
PID.3.4>CHVNG</Extra-
PID.3.4><Extra-
PID.3.5>NS</Extra-
PID.3.5></Extra-
PID.3><Extra-
PID.4 xsi:nil="true"></Extra-
PID.4><Extra-
PID.5><Extra-
PID.5.1>Santos</Extra-
PID.5.1><Extra-
PID.5.2>Paula</Extra-
PID.5.2><Extra-
PID.5.3>Cristina Silva Lopes</Extra-
PID.5.3></Extra-
PID.5><Extra-
PID.6 xsi:nil="true"></Extra-
PID.6><Extra-
PID.7>19720117000000+0000</Extra-
PID.7><Extra-
PID.8 xsi:nil="true"></Extra-
PID.8><Extra-
PID.9 xsi:nil="true"></Extra-
PID.9><Extra-
PID.10 xsi:nil="true"></Extra-
PID.10><Extra-
PID.11><Extra-
PID.11.1>R Bernardino Costa 358 Bl D Hab 04</Extra-
PID.11.1><Extra-
PID.11.2 xsi:nil="true"></Extra-
PID.11.2><Extra-
PID.11.3>Valadares</Extra-
PID.11.3><Extra-
PID.11.4 xsi:nil="true"></Extra-
PID.11.4><Extra-
PID.11.5>4405</Extra-
PID.11.5></Extra-
PID.11><Extra-
PID.12 xsi:nil="true"></Extra-
PID.12><Extra-
PID.13 xsi:nil="true"></Extra-
PID.13><Extra-
PID.14 xsi:nil="true"></Extra-
PID.14><Extra-
PID.15 xsi:nil="true"></Extra-
PID.15><Extra-
PID.16 xsi:nil="true"></Extra-
PID.16><Extra-
PID.17 xsi:nil="true"></Extra-
PID.17><Extra-
PID.18>7011588</Extra-
PID.18><Extra-
PID.19 xsi:nil="true"></Extra-
PID.19></Extra-
PID><Extra-
PV1><Extra-
PV1.1 xsi:nil="true"></Extra-
PV1.1><Extra-
PV1.2>URG</Extra-
PV1.2><Extra-
PV1.3><Extra-
PV1.3.1>1</Extra-
PV1.3.1><Extra-
PV1.3.2 xsi:nil="true"></Extra-
PV1.3.2><Extra-
PV1.3.3 xsi:nil="true"></Extra-
PV1.3.3><Extra-
PV1.3.4>CHVNG</Extra-
PV1.3.4></Extra-
PV1.3><Extra-
PV1.4 xsi:nil="true"></Extra-
PV1.4><Extra-
PV1.5 xsi:nil="true"></Extra-
PV1.5><Extra-
PV1.6 xsi:nil="true"></Extra-
PV1.6><Extra-
PV1.7 xsi:nil="true"></Extra-
PV1.7><Extra-
PV1.8 xsi:nil="true"></Extra-
PV1.8><Extra-
PV1.9 xsi:nil="true"></Extra-
PV1.9><Extra-
PV1.10 xsi:nil="true"></Extra-
PV1.10><Extra-
PV1.11 xsi:nil="true"></Extra-
PV1.11><Extra-
PV1.12 xsi:nil="true"></Extra-
PV1.12><Extra-
PV1.13 xsi:nil="true"></Extra-
PV1.13><Extra-
PV1.14 xsi:nil="true"></Extra-
PV1.14><Extra-
PV1.15 xsi:nil="true"></Extra-
PV1.15><Extra-
PV1.16 xsi:nil="true"></Extra-
PV1.16><Extra-
PV1.17 xsi:nil="true"></Extra-
PV1.17><Extra-
PV1.18>URG</Extra-
PV1.18><Extra-
PV1.19><Extra-
PV1.19.1>7088430</Extra-
PV1.19.1><Extra-
PV1.19.2 xsi:nil="true"></Extra-
PV1.19.2><Extra-
PV1.19.3 xsi:nil="true"></Extra-
PV1.19.3><Extra-
PV1.19.4>SONHO</Extra-
PV1.19.4></Extra-
PV1.19><Extra-
PV1.20 xsi:nil="true"></Extra-
PV1.20><Extra-
PV1.21 xsi:nil="true"></Extra-
PV1.21><Extra-
PV1.22 xsi:nil="true"></Extra-
PV1.22><Extra-
PV1.23 xsi:nil="true"></Extra-
PV1.23><Extra-
PV1.24 xsi:nil="true"></Extra-
PV1.24><Extra-
PV1.25 xsi:nil="true"></Extra-
PV1.25><Extra-
PV1.26 xsi:nil="true"></Extra-
PV1.26><Extra-
PV1.27 xsi:nil="true"></Extra-
PV1.27><Extra-
PV1.28 xsi:nil="true"></Extra-
PV1.28><Extra-
PV1.29 xsi:nil="true"></Extra-
PV1.29><Extra-
PV1.30 xsi:nil="true"></Extra-
PV1.30><Extra-
PV1.31 xsi:nil="true"></Extra-
PV1.31><Extra-
PV1.32 xsi:nil="true"></Extra-
PV1.32><Extra-
PV1.33 xsi:nil="true"></Extra-
PV1.33><Extra-
PV1.34 xsi:nil="true"></Extra-
PV1.34><Extra-
PV1.35 xsi:nil="true"></Extra-
PV1.35><Extra-
PV1.36 xsi:nil="true"></Extra-
PV1.36><Extra-
PV1.37 xsi:nil="true"></Extra-
PV1.37><Extra-
PV1.38 xsi:nil="true"></Extra-
PV1.38><Extra-
PV1.39 xsi:nil="true"></Extra-
PV1.39><Extra-
PV1.40 xsi:nil="true"></Extra-
PV1.40><Extra-
PV1.41 xsi:nil="true"></Extra-
PV1.41><Extra-
PV1.42 xsi:nil="true"></Extra-
PV1.42><Extra-
PV1.43 xsi:nil="true"></Extra-
PV1.43><Extra-
PV1.44>20070705154838+0000</Extra-
PV1.44><Extra-
PV1.45 xsi:nil="true"></Extra-
PV1.45><Extra-
PV1.46 xsi:nil="true"></Extra-
PV1.46><Extra-
PV1.47 xsi:nil="true"></Extra-
PV1.47><Extra-
PV1.48 xsi:nil="true"></Extra-
PV1.48><Extra-
PV1.49 xsi:nil="true"></Extra-
PV1.49><Extra-
PV1.50 xsi:nil="true"></Extra-
PV1.50><Extra-
PV1.51>V</Extra-
PV1.51><Extra-
PV1.52 xsi:nil="true"></Extra-
PV1.52></Extra-
PV1><Extra-
ORC><Extra-
ORC.1>NW</Extra-
ORC.1><Extra-
ORC.2><Extra-
ORC.2.1>19013</Extra-
ORC.2.1><Extra-
ORC.2.2>ALERT</Extra-
ORC.2.2></Extra-
ORC.2><Extra-
ORC.3 xsi:nil="true"></Extra-
ORC.3><Extra-
ORC.4 xsi:nil="true"></Extra-
ORC.4><Extra-
ORC.5>NW</Extra-
ORC.5><Extra-
ORC.6 xsi:nil="true"></Extra-
ORC.6><Extra-
ORC.7 xsi:nil="true"></Extra-
ORC.7><Extra-
ORC.8 xsi:nil="true"></Extra-
ORC.8><Extra-
ORC.9 xsi:nil="true"></Extra-
ORC.9><Extra-
ORC.10 xsi:nil="true"></Extra-
ORC.10><Extra-
ORC.11 xsi:nil="true"></Extra-
ORC.11><Extra-
ORC.12><Extra-
ORC.12.1>4292</Extra-
ORC.12.1><Extra-
ORC.12.2>Martinez</Extra-
ORC.12.2><Extra-
ORC.12.3>Cristina</Extra-
ORC.12.3></Extra-
ORC.12><Extra-
ORC.13 xsi:nil="true"></Extra-
ORC.13></Extra-
ORC><Extra-
OBR><Extra-
OBR.1>1</Extra-
OBR.1><Extra-
OBR.2><Extra-
OBR.2.1>19013</Extra-
OBR.2.1><Extra-
OBR.2.2>ALERT</Extra-
OBR.2.2></Extra-
OBR.2><Extra-
OBR.3 xsi:nil="true"></Extra-
OBR.3><Extra-
OBR.4><Extra-
OBR.4.1>10781</Extra-
OBR.4.1><Extra-
OBR.4.2>M<escape V="XE3"/>o direita, duas incid<escape V="XEA"/>ncias</Extra-
OBR.4.2><Extra-
OBR.4.3>CHVNG</Extra-
OBR.4.3></Extra-
OBR.4><Extra-
OBR.5 xsi:nil="true"></Extra-
OBR.5><Extra-
OBR.6 xsi:nil="true"></Extra-
OBR.6><Extra-
OBR.7 xsi:nil="true"></Extra-
OBR.7><Extra-
OBR.8 xsi:nil="true"></Extra-
OBR.8><Extra-
OBR.9 xsi:nil="true"></Extra-
OBR.9><Extra-
OBR.10 xsi:nil="true"></Extra-
OBR.10><Extra-
OBR.11 xsi:nil="true"></Extra-
OBR.11><Extra-
OBR.12 xsi:nil="true"></Extra-
OBR.12><Extra-
OBR.13 xsi:nil="true"></Extra-
OBR.13><Extra-
OBR.14 xsi:nil="true"></Extra-
OBR.14><Extra-
OBR.15 xsi:nil="true"></Extra-
OBR.15><Extra-
OBR.16><Extra-
OBR.16.1>4292</Extra-
OBR.16.1><Extra-
OBR.16.2>Martinez</Extra-
OBR.16.2><Extra-
OBR.16.3>Cristina</Extra-
OBR.16.3></Extra-
OBR.16><Extra-
OBR.17 xsi:nil="true"></Extra-
OBR.17><Extra-
OBR.18 xsi:nil="true"></Extra-
OBR.18><Extra-
OBR.19 xsi:nil="true"></Extra-
OBR.19><Extra-
OBR.20 xsi:nil="true"></Extra-
OBR.20><Extra-
OBR.21 xsi:nil="true"></Extra-
OBR.21><Extra-
OBR.22 xsi:nil="true"></Extra-
OBR.22><Extra-
OBR.23 xsi:nil="true"></Extra-
OBR.23><Extra-
OBR.24 xsi:nil="true"></Extra-
OBR.24><Extra-
OBR.25 xsi:nil="true"></Extra-
OBR.25><Extra-
OBR.26 xsi:nil="true"></Extra-
OBR.26><Extra-
OBR.27><Extra-
OBR.27.1 xsi:nil="true"></Extra-
OBR.27.1><Extra-
OBR.27.2 xsi:nil="true"></Extra-
OBR.27.2><Extra-
OBR.27.3 xsi:nil="true"></Extra-
OBR.27.3><Extra-
OBR.27.4>20070705161237+0000</Extra-
OBR.27.4></Extra-
OBR.27><Extra-
OBR.28 xsi:nil="true"></Extra-
OBR.28></Extra-
OBR><Extra-
NTE><Extra-
NTE.1>1</Extra-
NTE.1><Extra-
NTE.2 xsi:nil="true"></Extra-
NTE.2></Extra-
NTE><Extra-
DG1><Extra-
DG1.1>1</Extra-
DG1.1><Extra-
DG1.2 xsi:nil="true"></Extra-
DG1.2><Extra-
DG1.3><Extra-
DG1.3.1>9233</Extra-
DG1.3.1><Extra-
DG1.3.2>Contusao De Dedo Da Mao</Extra-
DG1.3.2><Extra-
DG1.3.3>ICD9</Extra-
DG1.3.3></Extra-
DG1.3><Extra-
DG1.4 xsi:nil="true"></Extra-
DG1.4><Extra-
DG1.5 xsi:nil="true"></Extra-
DG1.5><Extra-
DG1.6>D</Extra-
DG1.6></Extra-
DG1></OMG_O19>
I think that the problem should be because of the "Extra" (eg. <Extra-
PID.1 xsi:nil="true">) word that B2B puts in every tag.
The strange thing is that, this already worked until two days ago....
What could it be?
Thanks for your help.
Best Regards,
Nuno Fernandes

Integration scenario for Centralized Emergency Access and Helpdesk / CHARM

Hi,
Is any of you aware of a scenario doc between GRC and SOLMAN? Since Change Requests are referred in GRC, I assume there is an integrated scenario...
Thanks in advance,
Best regards,
Ádá

Can Firefighter logon using the Netweaver Business Client to launch Firefighter ID?
- No, GRAC_SPM is the way to go.
Is that mandate to use GRC system to launch Firefighter ID using GRAC_SPM transaction code? or can the user logon to local system as well?
- Yes. However, the option would be nice to have a workaround in case GRC is down
What about Portal based system Firefighting functionality? Can we have Firefighter IDs on Netweaver Java system?
- As far as I know only for transactional SAP systems.
Will I be able to grant a Firefighter ID to a Firefighter User on hourly basis?
- Same as answered already - no.
For initial setup , how the initial data load of Firefighter Ids Owners, Controllers and Firefighter Users can be done? Are there options like load from Excel or CSV available as part of setup toolset?
- Same as answered already - no.

Integration scenario and configuration scenario - is it madatory

Hi,
Integration Scenarios are not mandatory, the reason for creating them is given in the blog you mentioned:
The advantages of defining integration scenarios in the Integration Builder (design tool) are as follows:
· The integration scenario provides you with an overview of the process and the process flow
· The integration scenario club together all objects like SWVC,Interface objects, mapping objects,integration processes.You can access all of these objects from the integration scenario.
· The integration scenario gives you the design time information which is required for its configuration.
The configurtation items are getting created.
Regards
Patrick

Hi Priya,
There are two things here.
1) Create the Integration Scenario in the IR.
2) Use the wizard to configure the integration scenario in ID.
The Integration scenario created in the IR acts as a template to create the configuration objects in ID.
The wizard will create the actual configuration objects only (not just documentation).
But creating integration scenarios is not mandatory.
YOu can as well create all the configuration objects manually.
Generally, you will go for Integration scenarios if you are building a general purpose product (Product based ).
If it is a project that you are building for a particular customer, you can chose to create the configuration objects using the configuration scenario approach.
Regards,
Ravi kanth talagana

Mix B2B and A2A in integration scenario

Similar Messages

Maybe you are looking for