MDB and MessageConsumer Queue Questions
(1) Does a MessageConsumer object, when called on its onMessage() method, provide the same JMS queue processing as a Message Driven Bean (MDB) called on it's onMessage() method? That is, the message remains on the queue until the onMessage() method completes in both cases.
(2) Does the same apply to a MessageConsumer's receive() method? That is, the message remains on the queue until the next receive is called?
Thanks
Unfortunately, MDBs do not currently support running on a separate queue. They run on
the default queue.
-- Rob
Nicole wrote:
Hi Folks,
as we got problems on thread deadlocks using JMS, we decided to define our own thread
queue to be used by our application. In the documentation it is described, that you
need to generate all your EJBs with java weblogic.ejbc -dispatchPolicy xyz. By this
you connect your EJB to the named thread queue, which you will need to add to your
config.xml.
What I could find out was, that this works fine for stateful or stateless session
beans, but it looks like message driven beans do ignore this option.
So here are my questions:
Which thread queue is used by message driven beans?
How can I change the thread queue?
Many thanks,
Nicole
Similar Messages
-
Creating a MDB and Distributed Queue in Clustered env in weblogic 9.2
I have created 3 managed servers and all these managed servers are in the cluster.
Now i create JMS module for this cluster and create the Connection factory 'QUEUE_CF_8' and distributed Queue 'DIS_QUEUE_8' targeting to the cluster.
I create a MDB and JMS client and deploy them in the cluster.JMS client sends the message to the distributed queue and MDB is listening to the distributed queue
When i deploy the MDB , it is deploys perfectly . But when i run the client it fails with the following exception
[java] javax.naming.NameNotFoundException: Unable to resolve 'QUEUE_CF_8'. Resolved '' [Root exception is javax.naming.NameNotFoundException: Unable to resolve 'QUEUE_CF_8'. Resolved '']; remaining name 'QUEUE_CF_8'
When i view the JNDI tree for all the managed servers , i can see the Connection factory and the distributed queue.
Also i deploy the MDB to the cluster and no submoduletargets are specified.
Let me know what is that iam missing.<?xml version='1.0' encoding='UTF-8'?>
<weblogic-jms xmlns="http://www.bea.com/ns/weblogic/90" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/920 http://www.bea.com/ns/weblogic/920.xsd">
<connection-factory name="Queue_CF_8">
<sub-deployment-name>Server_group_4</sub-deployment-name>
<jndi-name>QUEUE_CF_8</jndi-name>
<security-params>
<attach-jmsx-user-id>false</attach-jmsx-user-id>
</security-params>
</connection-factory>
<uniform-distributed-queue name="DIS_QUEUE_8">
<sub-deployment-name>Server_group_4</sub-deployment-name>
<jndi-name>DIS_QUEUE_8</jndi-name>
<load-balancing-policy>Round-Robin</load-balancing-policy>
</uniform-distributed-queue>
</weblogic-jms>
But the problem was with the clustering.
Thanks for your time.. -
Hi Folks,
as we got problems on thread deadlocks using JMS, we decided to define our own thread
queue to be used by our application. In the documentation it is described, that you
need to generate all your EJBs with java weblogic.ejbc -dispatchPolicy xyz. By this
you connect your EJB to the named thread queue, which you will need to add to your
config.xml.
What I could find out was, that this works fine for stateful or stateless session
beans, but it looks like message driven beans do ignore this option.
So here are my questions:
Which thread queue is used by message driven beans?
How can I change the thread queue?
Many thanks,
NicoleUnfortunately, MDBs do not currently support running on a separate queue. They run on
the default queue.
-- Rob
Nicole wrote:
Hi Folks,
as we got problems on thread deadlocks using JMS, we decided to define our own thread
queue to be used by our application. In the documentation it is described, that you
need to generate all your EJBs with java weblogic.ejbc -dispatchPolicy xyz. By this
you connect your EJB to the named thread queue, which you will need to add to your
config.xml.
What I could find out was, that this works fine for stateful or stateless session
beans, but it looks like message driven beans do ignore this option.
So here are my questions:
Which thread queue is used by message driven beans?
How can I change the thread queue?
Many thanks,
Nicole -
Authentication problem w MDB on WL8.1 and JMS Queue on WL6.1
Hi,
I'm having problems with a MessageDrivenBean that is deployed on a Weblogic 8.1
server. It listens to a JMS Queue on a Weblogic 6.1 server.
I'm getting the following error message upon deployment:
[java.lang.SecurityException: Authentication for user system denied in realm wl_realm
I've made sure that both servers are installed with the user "system" and a password
of "password".
This worked fine for two WL6.1 servers.
Here's my ejb-jar.xml:
<!DOCTYPE ejb-jar PUBLIC
'-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<enterprise-beans>
<message-driven>
<ejb-name>WebResponseJMSBean</ejb-name>
<ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
</message-driven-destination>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<description>Transaction attributes for 'WebResponseJMSBean' methods</description>
<method>
<ejb-name>WebResponseJMSBean</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
Here's my weblogic-ejb-jar.xml:
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC
'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>WebResponseJMSBean</ejb-name>
<message-driven-descriptor>
<destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
<provider-url>t3://localhost:7003</provider-url>
<connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
</message-driven-descriptor>
<jndi-name>ejb/WebResponseJMSBean</jndi-name>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
Can anyone give me any suggestions?
Thanks in advance,
-Ben
We are facing a similar issue, between MDB's and JMS Queues on 2 separated WebLogic
8.1 domains. What I will test next week are:
1. In the domain where my MDB's are deployed, configure Foreign JMS Servers/Connection
Factories/Queues, for which passwords can be specified (not possible in weblogic-ejb-jar.xml)
2. If No.1 does not work, I will add CredentialGenerated="false" in <SecurityConfiguration>
in config.xml in both domains
3. If No. 2 still does not work, I will specify run-as principal and security-role
in my MDB DD files, and specify CredentialMapping via the WebLogic admin console.
Maybe you can try the same?
Eric Ma
"B Liu" <[email protected]> wrote:
>
>Hi,
>
>I'm having problems with a MessageDrivenBean that is deployed on a Weblogic
>8.1
>server. It listens to a JMS Queue on a Weblogic 6.1 server.
>
>I'm getting the following error message upon deployment:
>
>[java.lang.SecurityException: Authentication for user system denied in
>realm wl_realm
>
>I've made sure that both servers are installed with the user "system"
>and a password
>of "password".
>
>This worked fine for two WL6.1 servers.
>
>Here's my ejb-jar.xml:
>
><!DOCTYPE ejb-jar PUBLIC
>
>'-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN'
>
>'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
>
>
><ejb-jar>
>
> <enterprise-beans>
>
> <message-driven>
>
> <ejb-name>WebResponseJMSBean</ejb-name>
> <ejb-class>com.ditech.webresponse.jms.WebResponseJMSBean</ejb-class>
> <transaction-type>Container</transaction-type>
> <message-driven-destination>
> <destination-type>javax.jms.Queue</destination-type>
> </message-driven-destination>
>
> </message-driven>
>
> </enterprise-beans>
>
> <assembly-descriptor>
>
> <container-transaction>
>
> <description>Transaction attributes for 'WebResponseJMSBean'
>methods</description>
> <method>
> <ejb-name>WebResponseJMSBean</ejb-name>
> <method-name>*</method-name>
> </method>
> <trans-attribute>NotSupported</trans-attribute>
>
> </container-transaction>
>
> </assembly-descriptor>
>
></ejb-jar>
>
>Here's my weblogic-ejb-jar.xml:
>
><?xml version="1.0"?>
>
>
>
><!DOCTYPE weblogic-ejb-jar PUBLIC
>
>'-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN'
>
>'http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd'>
>
>
><weblogic-ejb-jar>
>
> <weblogic-enterprise-bean>
>
> <ejb-name>WebResponseJMSBean</ejb-name>
>
> <message-driven-descriptor>
>
> <destination-jndi-name>com.ditech.jms.CowResponseQueue</destination-jndi-name>
> <provider-url>t3://localhost:7003</provider-url>
> <connection-factory-jndi-name>com.ptp.jms.AppOnlineConnectionFactory</connection-factory-jndi-name>
> </message-driven-descriptor>
>
> <jndi-name>ejb/WebResponseJMSBean</jndi-name>
>
> </weblogic-enterprise-bean>
>
></weblogic-ejb-jar>
>
>
>Can anyone give me any suggestions?
>
>Thanks in advance,
>-Ben
>
-
Distributed Destinations and Error Queues
I have a distributed queue - distqueue which is configured with two queue members
- srvr1q
and srvr2q. srvr1q is a physical queue destination that is running on JMSServer1
on one instance in a cluster. srvr2q is a physical queue destination that is running
on JMSServer2 on another instance in the cluster. I have two errorqueues - srvr1errq
and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively. I have configured
the srvr1q to the following:
Redelivery Delay Override: 10000
Redelivery Limit: 3
Error Destination: srvr1errq
Also the srvr2q is configured to the following:
Redelivery Delay Override: 10000
Redelivery Limit: 3
Error Destination: srvr2errq
There is an MDB listening to each one of these local queues. The MDB is programmed
to throw a null pointer exception (to simulate business logic processing failures)
My expectations are : the message goes to one of the local queues. Null Pointer
exception is thrown. After 10 seconds the message is resent to the same queue
with a similar fate. After the third attempt, the message is moved to the error
queue of the corresponding local queue.
What I see is the following:
When I send a message I do see a Null Pointer Exception, but it occurs only once
and I dont see the message going to the error queue. Since my Load Balancing policy
is Round-Robin on the distqueue, the local queues receive the message every other
time with the same result - Null Pointer Exception thrown only once.
I also have JMSStores configured so the messages are persistent.
Can someone explain to me what I am doing wrong?
Thanks.
"Prakash Muthukrishnan" <[email protected]> wrote:
>
>Hi Tom
> Thanks again for the reply. I do use a tx MDB. I have set the transaction-type
>to Container in the message-driven stanza in ejb-jar.xml. And also the
>trans-attribute
>for that EJB in the container-transaction stanza, I have used Required.
>Do I need
>to setup anything else ?
I don't think so.
> The transaction descriptor element in the weblogic-enterprise-bean
>stanza in weblogic-ejb-jar.xml for that MDB is empty.
Not sure what you mean?
> Am I missing anything
>else?
Container & Required is all that is needed
If you like, post your ejb descriptor xml file, and I'll take a quick
look to double-check.
>-Prakash
>
>Tom Barnes <[email protected]> wrote:
>>Hi Prakash,
>>
>>A runtime exception should force a rollback for tx MDBs, and
>>a recover for non-tx MDBs. If you are seeing different
>>behavior there may be a bug in WL.
>>
>>Since MDBs do not log an exception when the app throws
>>a Runtime exception, I often recommend wrapping the
>>application code in a try catch anyhow
>> try {
>> } catch (Throwable t) {
>> log
>> force rollback
>> }
>>I think there are plans to provide a configurable that
>>optionally does something similar in the next release (no guarantees).
>>(The problem is that some apps throw a runtime on purpose, and
>>could quickly flood the log if such runtimes were logged per message.)
>>
>>Tom
>>
>>Prakash Muthukrishnan wrote:
>>> Tom
>>> Thanks for the suggestion. Using the setRollbackOnly method did the
>>trick. This
>>> brings up
>>> a related question: What if a run time exception was thrown during
>>the processing
>>> in an MDB?
>>> Is it not retried and ultimately shoved into the error queue?
>>> Thanks again.
>>> -Prakash
>>>
>>>
>>> Tom Barnes <[email protected]> wrote:
>>>
>>>>Hi Prakash,
>>>>
>>>>At first glance, it doesn't seem like your doing anything wrong.
>>>>Could you post your release and SP level, as well as your config.xml?
>>>>
>>>>How many messages did you send through?
>>>>
>>>>Note that for transactional MDBs it is best to call "setRollbackOnly"
>>>>on the EJB context rather than throwing an NPE. This is because
>>>>throwing a runtime exception forces the MDB to destroy itself and
>>>>get re-initialized (pretty high overhead). For non-transactional
>>>>MDBs, throwing a runtime exception is your only option.
>>>>
>>>>Tom, BEA
>>>>
>>>>Prakash Muthukrishnan wrote:
>>>>
>>>>
>>>>>I have a distributed queue - distqueue which is configured with two
>>>>
>>>>queue members
>>>>
>>>>>- srvr1q
>>>>>and srvr2q. srvr1q is a physical queue destination that is running
>>>>
>>>>on JMSServer1
>>>>
>>>>>on one instance in a cluster. srvr2q is a physical queue destination
>>>>
>>>>that is running
>>>>
>>>>>on JMSServer2 on another instance in the cluster. I have two errorqueues
>>>>
>>>>- srvr1errq
>>>>
>>>>>and srvr2errq - deployed on JMSServer1 and JMSServer2 respectively.
>>>>
>>>>I have configured
>>>>
>>>>>the srvr1q to the following:
>>>>>
>>>>>Redelivery Delay Override: 10000
>>>>>Redelivery Limit: 3
>>>>>Error Destination: srvr1errq
>>>>>
>>>>>Also the srvr2q is configured to the following:
>>>>>Redelivery Delay Override: 10000
>>>>>Redelivery Limit: 3
>>>>>Error Destination: srvr2errq
>>>>>
>>>>>There is an MDB listening to each one of these local queues. The
>MDB
>>>>
>>>>is programmed
>>>>
>>>>>to throw a null pointer exception (to simulate business logic processing
>>>>
>>>>failures)
>>>>
>>>>>My expectations are : the message goes to one of the local queues.
>>>>
>>>>Null Pointer
>>>>
>>>>>exception is thrown. After 10 seconds the message is resent to the
>>>>
>>>>same queue
>>>>
>>>>>with a similar fate. After the third attempt, the message is moved
>>>>
>>>>to the error
>>>>
>>>>>queue of the corresponding local queue.
>>>>>
>>>>>What I see is the following:
>>>>>When I send a message I do see a Null Pointer Exception, but it occurs
>>>>
>>>>only once
>>>>
>>>>>and I dont see the message going to the error queue. Since my Load
>>>>
>>>>Balancing policy
>>>>
>>>>>is Round-Robin on the distqueue, the local queues receive the message
>>>>
>>>>every other
>>>>
>>>>>time with the same result - Null Pointer Exception thrown only once.
>>>>>
>>>>>I also have JMSStores configured so the messages are persistent.
>>>>>
>>>>>Can someone explain to me what I am doing wrong?
>>>>>Thanks.
>>>>
>>>
>>
>
-
JMS and advanced Queues - how to dequeue?
Hi,
I've recently built a MDB that listens to an Oracle Queue (9.0.4) via JMS . Everything works fine, the only thing is that the rows that have been enqueued are not deleted (dequeued) from the queue table once the MDB has picked them up.
This only causes a problem when the database re-starts as the MDB picks up all the messages again. And also is a problem as the table will keep growing with all the messages.
Can you tell me what I should do to dequeue the messages? Should this be a trigger of some sort or is there something I can do from within the bean to dequeue the message once it has been consumed? Or is there another way of handling this?
Appreciate your help.
Cheers.Hello,
Great! I need that solution :)
Can you point out how you connected the MDB to the AQ? What software or adapter did you use?
I have the vice versa problem.
The MDB always deletes the message in the queue table, but a rollback never works.
Did you enable transactions by the following settings in ejb-jar.xml:
<container-transaction >
<method >
<ejb-name>MyMdb</ejb-name>
<method-name>*</method-name>
</method>
<trans-attribute>Required</trans-attribute>
</container-transaction>
I use BEA to deploy the MDB and Dips xa-compliant StartupClass package to register the AQ Connection Factory to in the JNDI tree.
Regards
Thomas -
MDB and JMS on different servers
Hi,
My MDB is deployed on a different domain from the JMS server. Both are on weblogic.
While deploying weblogic, I m getting an error: Unable to create a connection.
Can anyone give pointers?
I have ensured the following:
1. The JMS server starts before the MDB server
2. The following data is mentioned in weblogic-ejb-jar.xml:
jndi name of the remote queue
provider url--- t3://hostName:port
jndi name of the remote connection factory
is there anyting else that i m missing ?
thanx and regards
Shivraman GiriHi,
Thanx for responding.
I will keep in mind these points when I use a foreign JMS provider. T
Right now I m getting problem when the JMS provider is remote but native ie. MDB and JMS are both on Weblogic. This obviates the need to mention Initial Context. Only the provider URL is to be specified.
Can you suggest a reason as to why i my EJB container (first weblogic ) is unable to connect to JMS provider (another weblogic)
regards
S.G -
We are using Weblogic SP2 with MQ Series and MDBs. We have MDBs reading the queues
and calling Clarify application APIs (Clarify Business Objects). Everything works
fine on low volumes, but as the number of messages increase, weblogic stops responding
and the beans hang. There is no error or exception!
We have MDBS configured at 1min and 8max. Also, Java APIs have synchronized methods
to provide thread-safe access.
Any ideas?Start by taking periodic thread thumbs and go from there... Most likely
cause is deadlock:(
"Prashant" <[email protected]> wrote in message
news:[email protected]..
>
We are using Weblogic SP2 with MQ Series and MDBs. We have MDBs readingthe queues
and calling Clarify application APIs (Clarify Business Objects).Everything works
fine on low volumes, but as the number of messages increase, weblogicstops responding
and the beans hang. There is no error or exception!
We have MDBS configured at 1min and 8max. Also, Java APIs havesynchronized methods
to provide thread-safe access.
Any ideas? -
MDB/Topic/WLS cluster question
Hi
I was going through some WLS 8.1 docs on JMS and had a question abt Topics & WLS
in cluster config where say I have 3 servers with say server#1 hosting the Topic
[not a distributed destination]. I have an an ear file containing an MDB with
no pool size limit. After deploying the ear in the cluster - lets say that each
server on the cluster has 5 instances of the MDB [just an example] and a message
is published on the Topic.
Q1>Will all the 3 servers get a [one and only one] copy of that message? [my guess
is yes]
Q2>Only 1 instance [out of 5] of the MDB/per server will get the message - right?
Q3> Had I had a separate deployment of the same MDB class in the EAR file for
the same Topic - thats just going to get treated as a completely separate subscriber
independent of the first MDB though the implementing class is the same - right?
thanks
Anamitra
Anamitra wrote:
> Hi
> I was going through some WLS 8.1 docs on JMS and had a question abt Topics & WLS
> in cluster config where say I have 3 servers with say server#1 hosting the Topic
> [not a distributed destination]. I have an an ear file containing an MDB with
> no pool size limit. After deploying the ear in the cluster - lets say that each
> server on the cluster has 5 instances of the MDB [just an example] and a message
> is published on the Topic.
>
> Q1>Will all the 3 servers get a [one and only one] copy of that message? [my guess
> is yes]
Yes.
> Q2>Only 1 instance [out of 5] of the MDB/per server will get the message - right?
Yes.
> Q3> Had I had a separate deployment of the same MDB class in the EAR file for
> the same Topic - thats just going to get treated as a completely separate subscriber
> independent of the first MDB though the implementing class is the same - right?
Yes.
>
> thanks
> Anamitra
>
For a little more information, I'm attaching notes on durable
subscriber MDBs.
A JMS durable subscription is uniquely identified within a cluster by a combination of "connection-id" and "subscription-id". Only one active connection may use a particular "connection-id" within a WebLogic cluster.
In WebLogic 8.1 and previous, a durable topic subscriber MDB uses its name to generate its client-id. Since JMS enforces uniqueness on this client-id, this means that if a durable subscriber MDB is deployed to multiple servers only one server will be able to connect. Some applications want a different behavior where
each MDB pool on each server gets its own durable subscription.
The MDB connection id, which is unique within a cluster, comes from:
1) The "ClientId" attribute configured on the WebLogic connection factory.
This defaults to null. Note that if the ClientId is set on a connection
factory, only one connection created by the factory
may be active at a time.
2) If (1) is not set, then, as with the subscriber-id,
the connection-id is derived from jms-client-id descriptor attribute:
<jms-client-id>MyClientID</jms-client-id>
(the weblogic dtd)
3) If (1) and (2) are not set, then, as with the subscriber-id,
the connection-id is derived from the ejb name.
The MDB durable subscription id, which must be unique on its topic, comes from:
1) <jms-client-id>MyClientID</jms-client-id>
(the weblogic dtd)
2) if (1) is not set then the client-id
comes from the ejb name.
The above prevents a durable topic subscriber MDB from running on multiple servers. When an instance of the MDB starts on another server, it deploys successfully, but a conflict is detected and the MDB fails to fully connect to JMS. The work-around is the following:
A) Create a custom connection-factory for each server:
1) configure "JNDIName" to the same value across all servers
("myMDBCF" in this example)
2) configure "ClientId" to a unique value per server
3) enable "UserTransactionsEnabled"
4) enable "XAConnectionFactoryEnabled"
5) set "AcknowledgePolicy" to "ACKNOWLEDGE_PREVIOUS"
6) target the CF at a single WebLogic server
(Number 5 is required for non-transactional topic MDBs)
B) In the MDB's weblogic-ejb-jar.xml descriptor, set the MDB's connection
factory to the JNDI name of the custom connection factories configured in
(A). Optionally, also specify the subscriber-id via the jms-client-id
attribute.
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>exampleBean</ejb-name>
<message-driven-descriptor>
<connection-factory-jndi-name>myMDBCF</connection-factory-jndi-name>
<jms-client-id>myClientID</jms-client-id>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
C) Target the application at the same servers that have the custom connection
factories targeted at them.
Notes/Limitations:
1) If the MDB is moved from one server to another, the MDB's corresponding
connection-factory must be moved with it.
2) This work-around will not work if the destination is not in the same
cluster as the MDB. (The MDB can not use the local connection factory, which
contains the connection-id, as connection factories do not work unless they
are in the same cluster as the destination.)
3) This work-around will not work for non-WebLogic JMS topics.
4) A copy of each message is sent to each to each server's MDB pool.
-
I have a simple question. Why are the XBTO* and XBTS* queues shown in the SMQ2 (Inbound Queue Monitor) when these are actuallly Outbound and should have been shown under SMQ1 (Outbound Queue Monitor) ?
Thanks,
BadariDear Badari,
in context of PI it is important to make clear whether you are talking about qRfc queues or PI queues.
Let me start with some words on pipeline processing: The pipeline for asynchronous message processing in the Integration Server mainly consists of 2 parts. When a message is received by the Integration Server the inbound handler does some initial checks, creates an XI message object, serializes the same and schedules the message for asynchronous pipeline processing. During part 1of pipeline processing the receiver determination, interface determination and message split take place. Then the message object is serialized and again it is scheduled for asynchronous processing. During part 2 of pipeline processing the mapping and outbound binding is executed before invoking the adapter for sending the message to the receiver.
Part 1 of pipeline processing is named the "inbound" while the second part is called "outbound". Consequently PI refers to queues of part 1 as to "PI inbound queues" and all queues used by part 2 of pipeline processing are called "PI outbound queues".
And here is comes the crucial point: Both PI inbound queues and PI outbound queues are technically implemented as qRfc inbound queues.
Due to this reason you will find PI queues in SMQ2 only.
Best regards,
Harald Keimer -
Ok,
I am bit confused with how exactly MDBs work with Transactions.
For example,
suppose we have a simple standalone java message producer which sends a message to a Queue. A MDB's onMessage() picks it up.
Let's say the MDB makes some updates to the database and then invokes a method on a stateless session bean which also updates a database.
By default the transaction attribute of the MDB and stateless session bean would be REQUIRED.
If the stateless session bean database update fails, I presume the MDB's database updates also get rolled back.
But, does the message get rolled back? If not when would the message be rolled back?
Does it make any difference if the MDB is a topic or a queue? Does it make any difference if the message producer is a standalone client or
a stateless session bean with it's own transactional behaviour?
Any help appreciated.
Thanks.The general principle is: if you have a MDB which consumes a message in a transaction, and that transaction is rolled back, then the message is "rolled back". This means that it is put back on the queue or topic. It will then be delivered to the MDB again.
If your MDB calls a session bean then the two can share the same global transaction as you suggest.
Note however that the transaction which consumes the message is completely separate from any transaction which placed the message on the queue in the first place. JMS completely decouples the two steps. Once the message is added to the queue the producer is irrelevant.
Nigel -
My iPod touch wont let me buy anything, i've beem using this account for a couple of years and now it says that this is the first ime this id has been used on my device... it's not.... and to sign in and answer security questions. i cant remember the answers to the questions. How can i fix this without making a new account and losing all my stuff???
From a Kappy post
The Three Best Alternatives for Security Questions and Rescue Mail
1. Use Apple's Express Lane.
Go to https://expresslane.apple.com ; click 'See all products and services' at the
bottom of the page. In the next page click 'More Products and Services, then
'Apple ID'. In the next page select 'Other Apple ID Topics' then 'Forgotten Apple
ID security questions' and click 'Continue'. Please be patient waiting for the return
phone call. It will come in time depending on how heavily the servers are being hit.
2. Call Apple Support in your country: Customer Service: Contact Apple support.
3. Rescue email address and how to reset Apple ID security questions.
A substitute for using the security questions is to use 2-step verification:
Two-step verification FAQ Get answers to frequently asked questions about two-step verification for Apple ID. -
I've forgotten my Apple ID and my security question. I've tried to receive the Apple ID through email but I never receive the email.
The Best Alternatives for Security Questions and Rescue Mail
a. Send Apple an email request at: Apple - Support - iTunes Store - Contact Us.
b. Call Apple Support in your country: Customer Service: Contact Apple support.
c. Rescue email address and how to reset Apple ID security questions. -
When I try to setup my new iPad air, I go through all the steps for the iCloud sign-in and choosing security questions and what not. But after I hit the agree to the terms and conditions... It says Apple ID could not be created because of a server error. Have no clue what to do... I've restarted the iPad and get the same message. But my internet works just fine.
1. Turn router off for 30 seconds and on again
2. Settings>General>Reset>Reset Network Settings -
XML Publisher nested grouping, sum and order by question
Please help in nested group by, sum and order by question
My Data look like this:
<Header>
<Line1>
<Part Number></Part Number>
<Component>
<Component1></Component1>
<Component1 Amount></Component1 Amount>
</Component>
<Component>
<Component2></Component2>
<Component2 Amount></Component2 Amount>
</Component>
</Line1>
<Line2>
<Part Number></Part Number>
<Component>
<Component1></Component1>
<Component1 Amount></Component1 Amount >
</Component>
<Component>
<Component2></Component2>
<Component2 Amount ></Component2 Amount >
</Component>
</Line2>
</Header>
I want to print report which is:
1. Group by part number, component and sum the amount for a part number/component
2. Order by part number, component
Here is rtf file for XML publisher report
<?for-each-group:G_LINES;PART_NUMBER?>
<?sort:G_LINES;PART_NUMBER;'ascending';data-type='text'?>
<?if:BREAKDOWN_COUNT>0?>
Part Number: <?PART_NUMBER?> Quantity: <?sum (current-group()/SHIP_QTY)?> Part Count:<?count(current-group()/PART_NUMBER)?> Breakdown Count:<?count(G_BREAKDOWN/COMPONENT)?>
<?for-each:current-group()?>
<?for-each-group:G_BREAKDOWN;COMPONENT?>
Component: <?COMPONENT?> Price: <?COMPONENT_PRICE?>
<?end-for-each?>
<?end-for-each?>
<?end if?>
<?end-for-each?>
If I add <?sort:G_BREAKDOWN;COMPONENT;'ascending';data-type='text'?> inside G_BREAKDOWN grouping it gives error.
My XML data file
<?xml version="1.0"?>
<!-- Generated by Oracle Reports version 6.0.8.25.0 -->
<NI_COMMERCIAL_INVOICE_XMLP>
<LIST_G_HEADER>
<G_HEADER>
<COMM_INV_NUMBER>C/901000598</COMM_INV_NUMBER>
<COMM_INV_VERSION_NUMBER>1</COMM_INV_VERSION_NUMBER>
<SHIP_FROM_NAME>National Instruments Europe Corp.</SHIP_FROM_NAME>
<SHIP_FROM_ADDR>H-4031, Debrecen, Hatar ut 1/A</SHIP_FROM_ADDR>
<SHIP_FROM_CITY></SHIP_FROM_CITY>
<SHIP_FROM_STATE></SHIP_FROM_STATE>
<SHIP_FROM_POSTAL_CODE></SHIP_FROM_POSTAL_CODE>
<SHIP_FROM_COUNTRY>Hungary</SHIP_FROM_COUNTRY>
<SHIP_TO_NAME>National Instruments Corporation (NIEC)</SHIP_TO_NAME>
<FORMATTED_SHIP_TO_ADDR>11500 N Mopac Expwy
Austin, TX 78759-3504
United States</FORMATTED_SHIP_TO_ADDR>
<SHIP_TO_ADDR1>11500 N Mopac Expwy</SHIP_TO_ADDR1>
<SHIP_TO_ADDR2></SHIP_TO_ADDR2>
<SHIP_TO_ADDR3></SHIP_TO_ADDR3>
<SHIP_TO_ADDR4></SHIP_TO_ADDR4>
<SHIP_TO_CITY>Austin</SHIP_TO_CITY>
<SHIP_TO_STATE>TX </SHIP_TO_STATE>
<SHIP_TO_POSTAL_CODE>78759-3504</SHIP_TO_POSTAL_CODE>
<SHIP_TO_COUNTRY>US</SHIP_TO_COUNTRY>
<SHIP_TO_EMAIL_ADDR></SHIP_TO_EMAIL_ADDR>
<BILL_TO_ORG_ID>807737</BILL_TO_ORG_ID>
<SHIPPED_VIA>UPS</SHIPPED_VIA>
<DELIVERY_TERM>DDU</DELIVERY_TERM>
<TEXT_FILE_SEPARATOR></TEXT_FILE_SEPARATOR>
<DELIVERY_COUNT>4</DELIVERY_COUNT>
<HEADER_WAYBILL></HEADER_WAYBILL>
<LIST_G_LINES>
<G_LINES>
<DELIVERY_ID>2629769</DELIVERY_ID>
<ORDER_HEADER_ID>1431282</ORDER_HEADER_ID>
<ORDER_NUMBER>10004434</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-387</CUST_PO_NUMBER>
<ORDER_LINE_ID>4565737</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>26818</INVENTORY_ITEM_ID>
<PART_NUMBER>777459-23</PART_NUMBER>
<PART_DESC>SCC-AI04, 2-CHANNEL ISOLATED ANALOG INPUT</PART_DESC>
<PART_CUSTOM_DESC>SCC-AI04, Automatic Data Processing Plug-In Board</PART_CUSTOM_DESC>
<PLANNER_CODE>SCXIH-MPS</PLANNER_CODE>
<HTS_CODE>8471.80.9000</HTS_CODE>
<TARIC_CODE>8471.80.0000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>158</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>4</ORIG_SHIP_QTY>
<UNIT_PRICE>158</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>158</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>4</SHIP_QTY>
<EXTENDED_PRICE>632</EXTENDED_PRICE>
<UNIT_WEIGHT>.16</UNIT_WEIGHT>
<NET_WEIGHT>.64</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/01 NIC</WAYBILL>
<BREAKDOWN_COUNT>0</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE></BREAKDOWN_TYPE>
<BREAKDOWN_VALUE></BREAKDOWN_VALUE>
<COMPONENT></COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE></COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO></COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2629769</DELIVERY_ID>
<ORDER_HEADER_ID>1431282</ORDER_HEADER_ID>
<ORDER_NUMBER>10004434</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-387</CUST_PO_NUMBER>
<ORDER_LINE_ID>4579950</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>143949</INVENTORY_ITEM_ID>
<PART_NUMBER>779475-01</PART_NUMBER>
<PART_DESC>SCC-68 I/O CONNECTOR BLOCK WITH 4 SCC SIGNAL CONDITIONING MODULE SLOTS</PART_DESC>
<PART_CUSTOM_DESC>SCC-68, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>DAQH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>144</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>10</ORIG_SHIP_QTY>
<UNIT_PRICE>144</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>144</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>10</SHIP_QTY>
<EXTENDED_PRICE>1440</EXTENDED_PRICE>
<UNIT_WEIGHT>1.06</UNIT_WEIGHT>
<NET_WEIGHT>10.6</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/01 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>50</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>10</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>20</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>1370</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2629822</DELIVERY_ID>
<ORDER_HEADER_ID>1425429</ORDER_HEADER_ID>
<ORDER_NUMBER>10004365</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-372</CUST_PO_NUMBER>
<ORDER_LINE_ID>4579940</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>22643</INVENTORY_ITEM_ID>
<PART_NUMBER>777687-20</PART_NUMBER>
<PART_DESC>SCXI-1320 TEMPERATURE SENSOR TERMINAL BLOCK, CAST</PART_DESC>
<PART_CUSTOM_DESC>SCXI-1320, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>SCXIH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>82</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>1</ORIG_SHIP_QTY>
<UNIT_PRICE>82</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>82</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>1</SHIP_QTY>
<EXTENDED_PRICE>82</EXTENDED_PRICE>
<UNIT_WEIGHT>.57</UNIT_WEIGHT>
<NET_WEIGHT>.57</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/02 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>5</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>1</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>2</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>75</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2629822</DELIVERY_ID>
<ORDER_HEADER_ID>1427673</ORDER_HEADER_ID>
<ORDER_NUMBER>10004391</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-377</CUST_PO_NUMBER>
<ORDER_LINE_ID>4579948</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>143949</INVENTORY_ITEM_ID>
<PART_NUMBER>779475-01</PART_NUMBER>
<PART_DESC>SCC-68 I/O CONNECTOR BLOCK WITH 4 SCC SIGNAL CONDITIONING MODULE SLOTS</PART_DESC>
<PART_CUSTOM_DESC>SCC-68, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>DAQH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>144</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>13</ORIG_SHIP_QTY>
<UNIT_PRICE>144</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>144</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>13</SHIP_QTY>
<EXTENDED_PRICE>1872</EXTENDED_PRICE>
<UNIT_WEIGHT>1.06</UNIT_WEIGHT>
<NET_WEIGHT>13.78</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/02 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>65</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>13</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>26</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>1781</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2630021</DELIVERY_ID>
<ORDER_HEADER_ID>1429687</ORDER_HEADER_ID>
<ORDER_NUMBER>10004410</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-383</CUST_PO_NUMBER>
<ORDER_LINE_ID>4578220</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>61816</INVENTORY_ITEM_ID>
<PART_NUMBER>777687-14</PART_NUMBER>
<PART_DESC>SCXI-1314 FRONT MOUNTING TERMINAL BLOCK</PART_DESC>
<PART_CUSTOM_DESC>SCXI-1314, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>SCXIH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>120</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>4</ORIG_SHIP_QTY>
<UNIT_PRICE>120</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>120</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>4</SHIP_QTY>
<EXTENDED_PRICE>480</EXTENDED_PRICE>
<UNIT_WEIGHT>.68</UNIT_WEIGHT>
<NET_WEIGHT>2.72</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/03 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>20</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>4</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>452</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>8</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2630054</DELIVERY_ID>
<ORDER_HEADER_ID>1435114</ORDER_HEADER_ID>
<ORDER_NUMBER>10004463</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-396</CUST_PO_NUMBER>
<ORDER_LINE_ID>4580160</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>96909</INVENTORY_ITEM_ID>
<PART_NUMBER>778729-01</PART_NUMBER>
<PART_DESC>NI PCI-4474, 4 INPUTS, 24-BIT DYNAMIC SIGNAL ACQUISITION</PART_DESC>
<PART_CUSTOM_DESC>PCI-4474, Automatic Data Processing Plug-In Board</PART_CUSTOM_DESC>
<PLANNER_CODE>INSTRHMPS</PLANNER_CODE>
<HTS_CODE>8471.80.4000</HTS_CODE>
<TARIC_CODE>8471.80.0000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>960</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>4</ORIG_SHIP_QTY>
<UNIT_PRICE>960</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>960</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>4</SHIP_QTY>
<EXTENDED_PRICE>3840</EXTENDED_PRICE>
<UNIT_WEIGHT>.68</UNIT_WEIGHT>
<NET_WEIGHT>2.72</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/04 NIC</WAYBILL>
<BREAKDOWN_COUNT>0</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE></BREAKDOWN_TYPE>
<BREAKDOWN_VALUE></BREAKDOWN_VALUE>
<COMPONENT></COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE></COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO></COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
</LIST_G_LINES>
</G_HEADER>
</LIST_G_HEADER>
</NI_COMMERCIAL_INVOICE_XMLP>
I want my report for part number (which has multiple component) look like:
Part Number: 779475-01 Quantity: 23 Part Count:2 Breakdown Count:6
Component: CD Amount: 115
Component: IP Amount: 3151
Component: Paper Amount: 46
Any help or suggestion is appreciated
RK Shah
[email protected]I am using the latest 10.1.3.2.1 build 87.
The output that I see is :
Part Number: 777687-14 Quantity: 4 Part Count:1 Breakdown Count:3
Component: CD
Count: 4
Sum of Component Price: 20
Component: IP
Count: 0
Sum of Component Price: 452
Component: Paper
Count: 0
Sum of Component Price: 8
Part Number: 777687-20 Quantity: 1 Part Count:1 Breakdown Count:3
Component: CD
Count: 1
Sum of Component Price: 5
Component: Paper
Count: 0
Sum of Component Price: 2
Component: IP
Count: 0
Sum of Component Price: 75
Part Number: 779475-01 Quantity: 23 Part Count:2 Breakdown Count:3
Component: CD
Count: 23
Sum of Component Price: 115
Component: Paper
Count: 0
Sum of Component Price: 46
Component: IP
Count: 0
Sum of Component Price: 3151
and the XML data that I used is :
<?xml version="1.0"?>
<!-- Generated by Oracle Reports version 6.0.8.25.0 -->
<NI_COMMERCIAL_INVOICE_XMLP>
<LIST_G_HEADER>
<G_HEADER>
<COMM_INV_NUMBER>C/901000598</COMM_INV_NUMBER>
<COMM_INV_VERSION_NUMBER>1</COMM_INV_VERSION_NUMBER>
<SHIP_FROM_NAME>National Instruments Europe Corp.</SHIP_FROM_NAME>
<SHIP_FROM_ADDR>H-4031, Debrecen, Hatar ut 1/A</SHIP_FROM_ADDR>
<SHIP_FROM_CITY></SHIP_FROM_CITY>
<SHIP_FROM_STATE></SHIP_FROM_STATE>
<SHIP_FROM_POSTAL_CODE></SHIP_FROM_POSTAL_CODE>
<SHIP_FROM_COUNTRY>Hungary</SHIP_FROM_COUNTRY>
<SHIP_TO_NAME>National Instruments Corporation (NIEC)</SHIP_TO_NAME>
<FORMATTED_SHIP_TO_ADDR>11500 N Mopac Expwy
Austin, TX 78759-3504
United States</FORMATTED_SHIP_TO_ADDR>
<SHIP_TO_ADDR1>11500 N Mopac Expwy</SHIP_TO_ADDR1>
<SHIP_TO_ADDR2></SHIP_TO_ADDR2>
<SHIP_TO_ADDR3></SHIP_TO_ADDR3>
<SHIP_TO_ADDR4></SHIP_TO_ADDR4>
<SHIP_TO_CITY>Austin</SHIP_TO_CITY>
<SHIP_TO_STATE>TX </SHIP_TO_STATE>
<SHIP_TO_POSTAL_CODE>78759-3504</SHIP_TO_POSTAL_CODE>
<SHIP_TO_COUNTRY>US</SHIP_TO_COUNTRY>
<SHIP_TO_EMAIL_ADDR></SHIP_TO_EMAIL_ADDR>
<BILL_TO_ORG_ID>807737</BILL_TO_ORG_ID>
<SHIPPED_VIA>UPS</SHIPPED_VIA>
<DELIVERY_TERM>DDU</DELIVERY_TERM>
<TEXT_FILE_SEPARATOR></TEXT_FILE_SEPARATOR>
<DELIVERY_COUNT>4</DELIVERY_COUNT>
<HEADER_WAYBILL></HEADER_WAYBILL>
<LIST_G_LINES>
<G_LINES>
<DELIVERY_ID>2629769</DELIVERY_ID>
<ORDER_HEADER_ID>1431282</ORDER_HEADER_ID>
<ORDER_NUMBER>10004434</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-387</CUST_PO_NUMBER>
<ORDER_LINE_ID>4565737</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>26818</INVENTORY_ITEM_ID>
<PART_NUMBER>777459-23</PART_NUMBER>
<PART_DESC>SCC-AI04, 2-CHANNEL ISOLATED ANALOG INPUT</PART_DESC>
<PART_CUSTOM_DESC>SCC-AI04, Automatic Data Processing Plug-In Board</PART_CUSTOM_DESC>
<PLANNER_CODE>SCXIH-MPS</PLANNER_CODE>
<HTS_CODE>8471.80.9000</HTS_CODE>
<TARIC_CODE>8471.80.0000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>158</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>4</ORIG_SHIP_QTY>
<UNIT_PRICE>158</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>158</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>4</SHIP_QTY>
<EXTENDED_PRICE>632</EXTENDED_PRICE>
<UNIT_WEIGHT>.16</UNIT_WEIGHT>
<NET_WEIGHT>.64</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/01 NIC</WAYBILL>
<BREAKDOWN_COUNT>0</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE></BREAKDOWN_TYPE>
<BREAKDOWN_VALUE></BREAKDOWN_VALUE>
<COMPONENT></COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE></COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO></COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2629769</DELIVERY_ID>
<ORDER_HEADER_ID>1431282</ORDER_HEADER_ID>
<ORDER_NUMBER>10004434</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-387</CUST_PO_NUMBER>
<ORDER_LINE_ID>4579950</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>143949</INVENTORY_ITEM_ID>
<PART_NUMBER>779475-01</PART_NUMBER>
<PART_DESC>SCC-68 I/O CONNECTOR BLOCK WITH 4 SCC SIGNAL CONDITIONING MODULE SLOTS</PART_DESC>
<PART_CUSTOM_DESC>SCC-68, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>DAQH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>144</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>10</ORIG_SHIP_QTY>
<UNIT_PRICE>144</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>144</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>10</SHIP_QTY>
<EXTENDED_PRICE>1440</EXTENDED_PRICE>
<UNIT_WEIGHT>1.06</UNIT_WEIGHT>
<NET_WEIGHT>10.6</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/01 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>50</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>10</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>20</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>1370</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2629822</DELIVERY_ID>
<ORDER_HEADER_ID>1425429</ORDER_HEADER_ID>
<ORDER_NUMBER>10004365</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-372</CUST_PO_NUMBER>
<ORDER_LINE_ID>4579940</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>22643</INVENTORY_ITEM_ID>
<PART_NUMBER>777687-20</PART_NUMBER>
<PART_DESC>SCXI-1320 TEMPERATURE SENSOR TERMINAL BLOCK, CAST</PART_DESC>
<PART_CUSTOM_DESC>SCXI-1320, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>SCXIH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>82</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>1</ORIG_SHIP_QTY>
<UNIT_PRICE>82</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>82</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>1</SHIP_QTY>
<EXTENDED_PRICE>82</EXTENDED_PRICE>
<UNIT_WEIGHT>.57</UNIT_WEIGHT>
<NET_WEIGHT>.57</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/02 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>5</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>1</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>2</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>75</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2629822</DELIVERY_ID>
<ORDER_HEADER_ID>1427673</ORDER_HEADER_ID>
<ORDER_NUMBER>10004391</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-377</CUST_PO_NUMBER>
<ORDER_LINE_ID>4579948</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>143949</INVENTORY_ITEM_ID>
<PART_NUMBER>779475-01</PART_NUMBER>
<PART_DESC>SCC-68 I/O CONNECTOR BLOCK WITH 4 SCC SIGNAL CONDITIONING MODULE SLOTS</PART_DESC>
<PART_CUSTOM_DESC>SCC-68, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>DAQH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>144</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>13</ORIG_SHIP_QTY>
<UNIT_PRICE>144</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>144</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>13</SHIP_QTY>
<EXTENDED_PRICE>1872</EXTENDED_PRICE>
<UNIT_WEIGHT>1.06</UNIT_WEIGHT>
<NET_WEIGHT>13.78</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/02 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>65</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>13</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>26</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>1781</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2630021</DELIVERY_ID>
<ORDER_HEADER_ID>1429687</ORDER_HEADER_ID>
<ORDER_NUMBER>10004410</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-383</CUST_PO_NUMBER>
<ORDER_LINE_ID>4578220</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>61816</INVENTORY_ITEM_ID>
<PART_NUMBER>777687-14</PART_NUMBER>
<PART_DESC>SCXI-1314 FRONT MOUNTING TERMINAL BLOCK</PART_DESC>
<PART_CUSTOM_DESC>SCXI-1314, Screw Terminals</PART_CUSTOM_DESC>
<PLANNER_CODE>SCXIH-MPS</PLANNER_CODE>
<HTS_CODE>8536.90.4000</HTS_CODE>
<TARIC_CODE>8536.90.1000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>120</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>4</ORIG_SHIP_QTY>
<UNIT_PRICE>120</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>120</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>4</SHIP_QTY>
<EXTENDED_PRICE>480</EXTENDED_PRICE>
<UNIT_WEIGHT>.68</UNIT_WEIGHT>
<NET_WEIGHT>2.72</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/03 NIC</WAYBILL>
<BREAKDOWN_COUNT>3</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>CD</COMPONENT>
<COMPONENT_DESC>Test1</COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>20</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2803.00.0050</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE>Test1</COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY>4</COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>IP</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>452</COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE>HTS CODE</BREAKDOWN_TYPE>
<BREAKDOWN_VALUE>8536.90.4000</BREAKDOWN_VALUE>
<COMPONENT>Paper</COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE>8</COMPONENT_PRICE>
<COMPONENT_HTS_CODE>2839.90.0000</COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO>HU</COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
<G_LINES>
<DELIVERY_ID>2630054</DELIVERY_ID>
<ORDER_HEADER_ID>1435114</ORDER_HEADER_ID>
<ORDER_NUMBER>10004463</ORDER_NUMBER>
<CUST_PO_NUMBER>310986-396</CUST_PO_NUMBER>
<ORDER_LINE_ID>4580160</ORDER_LINE_ID>
<INVENTORY_ITEM_ID>96909</INVENTORY_ITEM_ID>
<PART_NUMBER>778729-01</PART_NUMBER>
<PART_DESC>NI PCI-4474, 4 INPUTS, 24-BIT DYNAMIC SIGNAL ACQUISITION</PART_DESC>
<PART_CUSTOM_DESC>PCI-4474, Automatic Data Processing Plug-In Board</PART_CUSTOM_DESC>
<PLANNER_CODE>INSTRHMPS</PLANNER_CODE>
<HTS_CODE>8471.80.4000</HTS_CODE>
<TARIC_CODE>8471.80.0000</TARIC_CODE>
<COUNTRY_OF_ORIGIN>HU</COUNTRY_OF_ORIGIN>
<ORDER_CURRENCY_CODE>USD</ORDER_CURRENCY_CODE>
<ORIG_UNIT_PRICE>960</ORIG_UNIT_PRICE>
<ORIG_SHIP_QTY>4</ORIG_SHIP_QTY>
<UNIT_PRICE>960</UNIT_PRICE>
<PRICE_CALC_STEP_NUMBER>100</PRICE_CALC_STEP_NUMBER>
<PRICE_CALC_CURRENCY_CODE>USD</PRICE_CALC_CURRENCY_CODE>
<PRICE_CALC_UNIT_PRICE>960</PRICE_CALC_UNIT_PRICE>
<PRICE_CALC_CONV_RATE>1</PRICE_CALC_CONV_RATE>
<SHIP_QTY>4</SHIP_QTY>
<EXTENDED_PRICE>3840</EXTENDED_PRICE>
<UNIT_WEIGHT>.68</UNIT_WEIGHT>
<NET_WEIGHT>2.72</NET_WEIGHT>
<ACQ_SOURCE_CODE></ACQ_SOURCE_CODE>
<ACQ_ORDER_NUMBER></ACQ_ORDER_NUMBER>
<ACQ_SOURCE_ORDER_NUMBER></ACQ_SOURCE_ORDER_NUMBER>
<ACQ_SELLING_PRICE>0</ACQ_SELLING_PRICE>
<SUBINVENTORY>NIEC Stage</SUBINVENTORY>
<SHIP_TO_SITE_USE_ID>807736</SHIP_TO_SITE_USE_ID>
<FREIGHT_COST>0</FREIGHT_COST>
<PAYMENT_TERMS>NIH InterCo</PAYMENT_TERMS>
<WAYBILL>901000598/04 NIC</WAYBILL>
<BREAKDOWN_COUNT>0</BREAKDOWN_COUNT>
<LIST_G_BREAKDOWN>
<G_BREAKDOWN>
<BREAKDOWN_TYPE></BREAKDOWN_TYPE>
<BREAKDOWN_VALUE></BREAKDOWN_VALUE>
<COMPONENT></COMPONENT>
<COMPONENT_DESC></COMPONENT_DESC>
<COMPONENT_CUSTOM_DESC></COMPONENT_CUSTOM_DESC>
<COMPONENT_PRICE></COMPONENT_PRICE>
<COMPONENT_HTS_CODE></COMPONENT_HTS_CODE>
<COMPONENT_TARIC_CODE></COMPONENT_TARIC_CODE>
<COMPONENT_COO></COMPONENT_COO>
<COMPONENT_QTY></COMPONENT_QTY>
</G_BREAKDOWN>
</LIST_G_BREAKDOWN>
</G_LINES>
</LIST_G_LINES>
</G_HEADER>
</LIST_G_HEADER>
</NI_COMMERCIAL_INVOICE_XMLP>
Maybe you are looking for
-
Hi, I recently upgraded my Mac Mini SL server to Lion server ... after having some troubles I reinstalled it. I configured the drives (2x500GB) to be in a raid array (mirror). Is it possible to remove the raid easily? i was thinking of: - Superduper
-
Query - Price list report by Customer
Hi, Can I please be advised on Query to obtain result = when reporting on a specific BP customer and to list items with applicable price (as per assigned price list). eg. Customer A (assigned to Pricelist 1) - item X $100.00 - Item Y $150.00 (above
-
Any problems having Admin Optimization and Proactive caching run concurrently
Hi, We've recently enabled proactive caching refreshing every 10 minutes and have seen data in locked versions changing after Full Admin Optimization runs. Given how the data reverts back to a prior submitted number, I suspect having proactive cachin
-
Hello, I am generating my own geometry and I want some parts of it to be partly transparent. For example, I want a quadrilateral with one corner 50% transparent and the others opaque, so that it fades from transparent to opaque. I tried using Color4f
-
HT204088 Purchased items not showing up...How do I fix this??!!
I want to access my purchased music and not all of my purchased items are showing up. Only my most recent purchases are there. How do I fix this??!!