Two separate Print out while MIGO transaction

All,
While doing MIGO, internal batch numbers are generated .
While doing this transaction a GR slip is printed out with batch number , production date , expiry date , material code and many other informations with output type WE01.
Now business want while doing this transaction , a separate print out with only batch number , Production date and expiry date .
These two separate print outs should automatically come while MIGO transaction .
1. Is this possible ?
2. If possible , which output type will be for the 2nd print out .?
2. Any user exit required here?
Kindly advise.
regards

Hi Sandeep
1) Inventory Mgmt IMG->Output Determ..->Maintain output types
Copy WE01 and create a new output type ZWE01.
In processing routines, you need to change the program/form for your new output. Discuss with your ABAPer for this.
2) In 'Maintain Output determination procedure', insert this new output type in 'Control'
3) Maintain conditions as required
After this, use WE90 to print both outputs.
Best regards
Ramki

Similar Messages

Two side printing out of Acrobat?

does anyone happen to know how to get a two-sided print out of Acrobat X? i have a 295 page numbers help document i want to print out and i can't find this setting no matter how much i look. the Adobe forum seems to be somewhat "windows-centric" but i am going to ask there as well.
i also tried a "two sided printing" search in the Acrobat help and no results came up.
TIA for any help on this.

hi gents.
thank you.
i do in fact have a duplex unit the HP 8600 All in One. the driver section for this printer (accessed through the Print + Scan options in Preferences) shows up as "HP OfficeJet Pro 8600" and it has both the Duplexer option checked as well as the "Additional Paper Input Tray" checked. Driver version is 3.3.3. also, note that i DO print on two sides in some of my other software (including docs printing with/from iOS7 on my iPhone).
i guess i need to check to see if i have the correct driver (?) but can you help me with two things before we get there?
1. when i hit File > Print in Acrobat i get what looks like a "Mac" printer interface. it doesn't actually look like either of your screenshots (thanks) - even though i /think/ i have seen these before either on the laptop or on the desktop.
if i click on "Printer" in my dialog i then get a prompt (in this case with an adobe logo) that i have never understood: "The Print Setup dialog box is provided by the operating system. To ensure that you can use the full print capabilities of Acrobat, please set all print options from the Applications dialog box. Do you want to continue? Yes/No".
does anyone know what this means or what i am misunderstanding in all of this? seems totally bizarre to get the mac print dialog and then get into the Printer button and then get this option especially if i am running a print pulldown option from Acrobat...
2. i am having to /manually/ put paper tray with the proper paper size into my two tray Espon WF 7520. i want to say that i /don't/ have this problem with the HP 8600 but now that i think about it i am not sure i have ever tried the second paper tray on the 8600. HOWEVER, i /do/ see the Duplexer checkbox option in the Driver settings of the 8600 while i /don't/ see this setting in the Epson WF 7520.
does anyone know if this is likely (also?!) a DRIVER SIDE ISSUE with respect to not getting any of my software to print to the second tray on the Epson? i mean, if i sherlock holmes this i /could/ say that if i cannot print to the second tray it is likely a old or wrong driver issue or even a implementation that they did not build into the good driver - since i cannot get to the second tray from anything on anything? or would this be incorrect...?
THANKS

I am setting up for the first time, i didn't get the print out while setting up with my sign info

i am setting up for the first time, i didn't get the print out while setting up with my sign information. None of my email information or original password are working.

Hi there, what printer model do you own?
If my reply helped you, feel free to click on the Kudos button (hover over the "thumbs up").
If my reply solved your problem please click on the Accepted Solution button so other Forum users may benefit from viewing the post.
I am an HP employee.

Purchase order print out issue

hi,
we want to change the vendor address in purchase order address details, and that should printed out while taking PO. currently address is taken from vendor master. kindly assist.
regards
fozters

dear friend
this work can only be done by abap consultant.
in this po he change the address from adrc and adr6 tables
ask them to check and rectifie as specified table.
if you need the code pls keep in touch.
rewards are expecting,
yours
vivek

Adobe reader 7.0 prints out jibberish text

I printed out 3 documents all of the same type/format except that some of the words were different.
The first document printed out just fine. However, the next two documents printed out and the text was definitely not English and did not look like any other language either. It was just a bunch of jibberish. What would cause this behavior and how can it be prevented?

One likely cause is that the author used fonts that you don't have in your system and he failed to embed them properly.

MIGO GR Print Out

Dear Guru's,
I am facing problem while checking collective issue tick in MIGO via Display Material Document. When I click on collective issue message appears Output save and when I press enter it resets that check.
Wats the actual problem. We are not facing this earlier. GR document and Movement Type are same as earlier and we take print out through MB90 by doing same as above.
Also I have noticed that through MB02 material document contains that check (collective issue).
This is really strange. I did not understand what is the problem. Can any1 help?
Regards,
RM

Hi,
This Problem can be overided by Maintaining the output messages in MN21
Enter the Following Data
Message type -- your Print Message type
transaction event key.--We good receipt ,WA --issue etc...
Print Version--Individual or collective
Print Item--.Material Document(1)
Partner Function -- VN
medium--Print (1)
DAte and time -- 4 (if you want immediately after Posting..
Lanuage EN.
KNow after double click on the item..or select the Item and click on the communication tab presnt at the top left hand corner.
and enter your printer details and check the print immediately option.
Hope so it helps
Regards
Anjanna

MIGO Print out

Hello,
I want to take printout of MIGO how to do this? is there any customizing needed for the same?

If you have Maintained Condition records in MN21 then you can take print out using MB90.
Please go thru the procedure and ensure you have done all the settings properly.
Output and Printer Determination For PO and GR
How to configure the output determination and printer determination for both PO and GR?
The steps are as follows:
Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
*4. Message Determination Schemas*
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Output of GR
After setting table, access sequence and output type for GR,run MB02 transaction, enter material document number. Double click one line item and select messages. Separate screen will be opened to configure outputs. Give the required fields and save the document.
Now Run MB90, you can take printout. Output Type: WE03 or WE01 or WE02
Regards,
Ashok

Problem with HP 1220c USB printer - two-sided print greyed-out

My client has a Powerbook G4 550MHz with Tiger 10.4 installed and I installed the latest HP 1220c driver.
When my client attempted to configure the printer via the printer setup page under 'layout' the two-sided print is greyed-out. Why?
My client has admin rights.

The layout of the print window is not the same as OS 9.x and prior. There will not be a choice for double sided printing as there was pre OS X unless the printer comes with an automatic duplexer.
You will have to figure out how to print odds and evens in separate jobs and do it manually.
Matt

¿Why Print out message in Migo get duplicateg when event 4 in MN22 is selected?

Hello,
I am not able to find out why the print out message get duplicate when I change event 3 to event 4 in MN22.
when I do Good issues in MIGO and the message "ZVAL" is set in event 3 "Send with application own transaction" only one type of message is been trigger in , but if I change event 3 to 4 "Send immediately (when saving the application)" in MN22 all the message get duplicated.
Thanks
Jorge G

Hi,
If you are using your own program in the processing routines for output type, then change it to standard program and form routine in NACE as shown below and test the scenario again. Also check whether any routine is assigned against the output type in the procedure - if so, remove the routine also.
Revert back with the result. If its working fine in this case, you need to check the custom program with the help of your technical team.
Regards,
AKPT

ABAP DUMP While doing GI Through Zmovement type in MIGO Transaction

Hi ,
We have migrated from FM FBS to BCS from 12.01.2015.
And we are using 101 profile with GR and IR update.
We received blow ABAP Dump while doing the GI through MIGO Transaction.
Can you please help on this.
Dump detatils
Category               ABAP Programming Error
Runtime Errors         MESSAGE_TYPE_X
ABAP Program           CL_BUAVC_ENTRY================CP
Application Component PSM-FM-BCS-AC
Date and Time          13.01.2015 09:10:00
Operating system..... "AIX 1 6, AIX 1 7"                                                      |
|                                                                                                  |
|    Memory consumption                                                                            |
|    Roll.... 0                                                                                    |
|    EM...... 33518336                                                                             |
|    Heap.... 0                                                                                    |
|    Page.... 196608                                                                               |
|    MM Used. 21989120                                                                             |
|    MM Free. 3145840                                                                              |
|User and Transaction                                                                              |
|    Client.............. 256                                                                      |
|    User................ "MM_BUX00_ZZ"                                                            |
|    Language key........ "R"                                                                      |
|    Transaction......... "MIGO_GI "                                                               |
|    Transaction ID...... "54AEDD9E3EE60710E10080000A15C616"                                       |
|                                                                                                  |
|    EPP Whole Context ID.... "54B35F7088300910E10080000A15C616"                                   |
|    EPP Connection ID....... 00000000000000000000000000000000                                     |
|    EPP Caller Counter...... 0                                                                    |
|                                                                                                  |
|    Program............. "CL_BUAVC_ENTRY================CP"                                       |
|    Screen.............. "SAPLMIGO 0001"                                                          |
|    Screen Line......... 18                                                                       |
|    Debugger Active..... "none"                                                                   |
|Information on where terminated                                                                   |
|    Termination occurred in the ABAP program "CL_BUAVC_ENTRY================CP" -                 |
|     in "POST".                                                                                   |
|    The main program was "SAPLMIGO ".                                                             |
|                                                                                                  |
|    In the source code you have the termination point in line 82                                  |
|    of the (Include) program "CL_BUAVC_ENTRY================CM00J".                               |
|Source Code Extract                                                                               |
|Line |SourceCde                                                                                   |
|   52|*--- method has provided some errors!):                                                     |
|   53|                                                                                            |
|   54|* Note 1499464:                                                                             |
|   55|*      IF cl_abap_aab_utilities=>is_active( id = 'BUAVC_GROUP'                              |
|   56|*       mode_assert_dump = 'X' ) = 'X'.                                                     |
|   57|      MOVE 'X' TO l_flg_dump.                                                               |
|   58|*      ENDIF.                                                                               |
|   59|                                                                                            |
|   60|*--- Check if the entry buffer of the AVC ledger contains data records                      |
|   61|*--- from previous COLLECT events:                                                          |
|   62|      IF ( l_f_avc_ledger-ref_ledger->entry_buffer_lines_count( ) > 0 ).                    |
|   63|*--- Sorry, must dump:                                                                      |
|   64|        ASSERT ID buavc_group                                                               |
|   65|               FIELDS c_avc_text 'POSTING_NOT_ALLOWED'                                      |
|   66|               CONDITION l_flg_dump <> 'X'.                                                 |
|   67|        IF l_flg_dump = 'X'.                                                                |
|   68|          MESSAGE x002(buavc) WITH c_avc_text space                                         |
|   69|                                   'POSTING_NOT_ALLOWED' space.                             |
|   70|        ENDIF.                                                                              |
|   71|      ENDIF.                                                                                |
|   72|    ENDIF.                                                                                  |
|   73|*----------------------------------------------------------------------                     |
|   74|* Note 1666556:                                                                             |
|   75|    IF me->g_commit_before_post EQ 'X'.                                                     |
|   76|*--- An unauthorized COMMIT WORK occurred before calling this POST                          |
|   77|*--- method. This COMMIT WORK has refreshed the AVC entry buffer and                        |
|   78|*--- would thus create a database inconsistency!                                            |
|   79|      MOVE 'X' TO l_flg_dump.                                                               |
|   80|      IF l_flg_dump = 'X'.                                                                  |
|   81|*--- Sorry, must dump (see note 1666556):                                                   |
|>>>>>|        MESSAGE x002(buavc) WITH c_avc_text space                                           |
|   83|                                 'INVALID_COMMIT' space.                                    |
|   84|      ENDIF.                                                                                |
|   85|    ENDIF.                                                                                  |
|   86|*----------------------------------------------------------------------                     |
|   87|                                                                                            |
|   88|                                                                                            |
|   89|*--- Call the POST method of the corresponding ledger instance:                             |
|   90|    CALL METHOD l_f_avc_ledger-ref_ledger->post                                             |
|   91|      EXPORTING                                                                             |
|   92|        i_ref_appl_log = me->g_ref_appl_log                                                 |
|   93|        i_doc_ref      = i_doc_ref.                                                         |
|   94|                                                                                            |
|   95| ENDLOOP.                                                                                  |
|   96|
Thanks Advance.
SAM

Hi Sam,
Please check if there is any commit statement written in badi or enhancement before calling this method for posting which is leading to update termination.
Regards,
Prakash.

Service tax value required updating while posting GR in MIGO transaction

Dear Friends,
We have a following scenario where service tax value required updating while posting Goods Receipt MIGO transaction.
1. Purchase Order created for first line item where Qty. 1 and Net Rate Rs.1000/- so total Gross value will be Rs.1000/- example Vendor XYZ
2. Freight condition type maintained for the first line item for Rs.500/- and assigned to Transportation vendor ABC.
3. When Goods Receipt Posted for the Material against PO first line item, the material value updates Rs.1500/- (Material value as
    per PO + Freight Charges)
4. After posting GR while making Invoice verification through MIRO transaction against the PO GR/IR clearance will be done for
    Material vendor XYZ. For transportation Vendor ABC Planned delivery cost indicator will be select and since service tax is
    applicable Service tax code will also select.
Here the values of Service tax if the Material available in Stock it will be inventories. If stock consumed before making the Invoice verification for Transportation vendor ABC, then the Service tax values update to PRD account.
We know that in PO, tax code can be select for first line item (Raw Material) Vendor XYZ and if transportation charge condition type maintained for same first line item and assigned to Vendor ABC and there is no provision to maintain Service tax. So the service tax will get inventories while posting Invoice Verification for the transportation vendor.
We want the values of Service tax to update while posting Goods Receipt in MIGO transaction.
Thanks & regards
Dhanu

hi,
Please note at the time of MIGO Servecie tax value does not appear, it will appear at the tiem of Invoice only.
Regards,
Rama Mohan Bangaru

Javax.transaction.SystemException: Timed out while in 'Logging' state!!!!

Hello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
     - locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
     at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
     at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
     at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
     at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
     at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
     at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
     at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
     at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
     at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
     at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AM

Hello, we have an OracleWeblogic 10.3.2 running on a Solaris OS.
In this AppServer we have a FullStack J2EE Application executing distributed transactions that involve 3 manageable resources:
TxDatasource (EJB),
NonTxDatasource with enableTwoPhaseCommit and
JMS
Some of the transactions are timing out while in 'Logging' state and I just cant figure out what the root cause is. As a defensive action I lowered the JTA Timeout seconds because I noticed the 'Logging' phase was taking too long and then timing out. Idea here was not to have too many threads hanging in Logging state and therefore use the JTA Timeout to overcome this problem and minimize impact.
Below, I'm posting a few exceptions thrown in applicaiton log. Any help is very appreciated.
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '175' for queue: 'weblogic.kernel.Default (self-tuning)'> <JG47515> <> <> <1313163611120> <BEA-010026> <Exception occurred during commit of transaction Name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)],Xid=BEA1-7DB913B4CB2B36D47CB7(1248714554),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=82,seconds left=60,XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),properties=({weblogic.transaction.name=[EJB com.citicorp.fx.credit.CreditServiceBean.askCreditQuery(com.citicorp.fx.credit.data.CreditQueryRequestData)]}),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
... 2 more
.>
####<Aug 12, 2011 11:40:11 AM EDT> <Error> <EJB> <brzfxap1> <FefxServer> <[ACTIVE] ExecuteThread: '154' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <> <1313163611119> <BEA-010026> <Exception occurred during commit of transaction Xid=BEA1-7DBB13B4CB2B36D47CB7(977835896),Status=Rolled back. [Reason=javax.transaction.SystemException: Timed out while in 'Logging' state],numRepliesOwedMe=0,numRepliesOwedOthers=0,seconds since begin=60,seconds left=60,XAServerResourceInfo[WLStore_fefx_FefxFileStore]=(ServerResourceInfo[WLStore_fefx_FefxFileStore]=(state=rolledback,assigned=FefxServer),xar=WLStore_fefx_FefxFileStore1032009487,re-Registered = false),XAServerResourceInfo[TWOraDS_fefx]=(ServerResourceInfo[TWOraDS_fefx]=(state=rolledback,assigned=FefxServer),xar=TWOraDS,re-Registered = false),SCInfo[fefx+FefxServer]=(state=rolledback),local properties=({weblogic.jdbc.jta.TWOraDS=[ No XAConnection is attached to this TxInfo ]}),OwnerTransactionManager=ServerTM[ServerCoordinatorDescriptor=(CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+, XAResources={WLStore_fefx_FefxFileStore, TWOraDS_fefx, WLStore_fefx__WLS_FefxServer, weblogic.jdbc.wrapper.JTSXAResourceImpl, WSATGatewayRM_FefxServer_fefx},NonXAResources={})],CoordinatorURL=FefxServer+169.193.4.91:8107+fefx+t3+): weblogic.transaction.RollbackException: Timed out while in 'Logging' state
at weblogic.transaction.internal.TransactionImpl.throwRollbackException(TransactionImpl.java:1848)
at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:339)
at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
at weblogic.ejb.container.internal.MDListener.execute(MDListener.java:500)
at weblogic.ejb.container.internal.MDListener.transactionalOnMessage(MDListener.java:371)
at weblogic.ejb.container.internal.MDListener.onMessage(MDListener.java:327)
at weblogic.jms.client.JMSSession.onMessage(JMSSession.java:4585)
at weblogic.jms.client.JMSSession.execute(JMSSession.java:4271)
at weblogic.jms.client.JMSSession.executeMessage(JMSSession.java:3747)
at weblogic.jms.client.JMSSession.access$000(JMSSession.java:114)
at weblogic.jms.client.JMSSession$UseForRunnable.run(JMSSession.java:5096)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.transaction.SystemException: Timed out while in 'Logging' state
at weblogic.transaction.internal.ServerTransactionImpl.wakeUp(ServerTransactionImpl.java:1797)
at weblogic.transaction.internal.ServerTransactionManagerImpl.processTimedOutTransactions(ServerTransactionManagerImpl.java:1609)
at weblogic.transaction.internal.TransactionManagerImpl.wakeUp(TransactionManagerImpl.java:1885)
at weblogic.transaction.internal.ServerTransactionManagerImpl.wakeUp(ServerTransactionManagerImpl.java:1519)
at weblogic.transaction.internal.WLSTimer.timerExpired(WLSTimer.java:35)
at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
... 3 more
.>
This is the stack trace of the thread that hangs while waiting for the lock to write in the transaction file:
"[ACTIVE] ExecuteThread: '64' for queue: 'weblogic.kernel.Default (self-tuning)'" daemon prio=3 tid=0x000000010dea3000 nid=0x1e2 in Object.wait() [0xfffffffda03ff000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
     at java.lang.Object.wait(Native Method)
     at weblogic.transaction.internal.ServerTransactionImpl.log(ServerTransactionImpl.java:2005)
     - locked <0xfffffffe64964b30> (a weblogic.transaction.internal.ServerTransactionImpl)
     at weblogic.transaction.internal.ServerTransactionImpl.globalPrepare(ServerTransactionImpl.java:2320)
     at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:273)
     at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:233)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvoke1(BaseRemoteObject.java:621)
     at weblogic.ejb.container.internal.StatelessRemoteObject.postInvoke1(StatelessRemoteObject.java:60)
     at weblogic.ejb.container.internal.BaseRemoteObject.postInvokeTxRetry(BaseRemoteObject.java:441)
     at com.citicorp.fx.credit.CreditService_6w08fk_EOImpl.askCreditQuery(CreditService_6w08fk_EOImpl.java:75)
     at com.citicorp.fx.client.creditquery.QueryProcessor.handleEvent(QueryProcessor.java:77)
     at org.jac.creation.ProcessorAction.handleEvent(ProcessorAction.java:64)
     at org.jac.runtime.AbstractAction.handleSecuredEvent(AbstractAction.java:73)
     at org.jac.runtime.StateImpl.handleEvent(StateImpl.java:66)
     at org.jac.runtime.ControllerImpl.handleEvent(ControllerImpl.java:123)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:55)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.session.SessionImpl.handleEvent(SessionImpl.java:78)
     - locked <0xfffffffe0860e618> (a org.jac.session.SessionImpl)
     at org.jac.creation.JacImpl.handleEvent(JacImpl.java:53)
     at org.jac.runtime.JACExecutor.handleEvent(JACExecutor.java:111)
     at org.jac.runtime.JACExecutor.handleEventBySessionID(JACExecutor.java:103)
     at org.jac.http.ControllerFilter.doFilter(ControllerFilter.java:63)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.fx.util.compression.CompressionFilter.doFilter(CompressionFilter.java:189)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at com.citicorp.security.web.WebLogicSiteminderAuthenticationFilter.doFilter(WebLogicSiteminderAuthenticationFilter.java:65)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3592)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2202)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2108)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1432)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: user8727499 on Aug 12, 2011 11:57 AM

Two sided print option is grey out

Recently, I noticed that when I need to print two-sided documents, the "two-sided" print option is greyed out. I have gone into System Preferences Printers & Scanners- and under "options" for the printer enabled the HP Two-sided Printing Accesory (Duplexer). This button continues to disengage (won't remain enabled) and each time I need to print two-sided, I have to repeat the above process. Please help

Hi,Try resetting the printing system and check if that may help:*Be aware that resetting the printer system will remove any existing print queue and reset any customized driver settings.
Click the Apple menu, and then click System Preferences .
Select Printers & Scanners.
Right-click (or Ctrl + click) your product in the Printers list in the left panel, and then click Reset printing system .
Click OK to confirm the reset.
Type your user Name and Password .
Click OK . The printing system resets. Next click the plus sign and select the listed printer. Within the Use drop down menu select the printer model and press the Add button. Hope that may help,Shlomi

While doing MIGO transaction system showing error: Check table169P the entr

Hi experts,
while doing MIGO transaction system showing error: Check table169P the entry BP01 does not exit.
pls do needful.
Thanks&Regards
sreenivas.p

Hi,
Please specify Whether you are doing Blocking of Invoices or what?
As the T169P is A Parameters Invoice Verification, so you can check the values for T169P table in SE16 so that you will get Clear idea regarding company code BP01 in which the stochastic block is active with Threshold value for stochastic block...
Please check....
For maintaining Entries please go to OMRG maintain Company code and Threshold value as per client requirement so that This will specifies the degree of probability that an invoice is stochastically blocked.
Regards,
Ninad Kshirsagar

Two-sided printing greyed out (Phaser 6300)

So, in our office, there is only one Mac out of four that can access the two-sided printing options for our Xerox Phaser 6300. On all the other Macs, that option is greyed out. Yes, I've gone and made sure they all have the latest drivers installed etc. Anyone know what in the world might be missing, or needs to be done here?

Nevermind! I just figured it out. Apparently the same printer has two listings in the printer selection dialog. I just chose the other one and the option came back.
Lesson learned.

Two separate Print out while MIGO transaction

Similar Messages

Maybe you are looking for