PO output status not processed

Hi,
I am trying to print PO using output type NEU and ZNEU (copy of the NEU) with medium 1-print, communication method filled with required information and also further data with 4-print immediately.
After saving it, the status of the PO in PO output showing yellow-not processed and also it is not seen in ME9F transaction without process/ with process.
Can any one help me understanding why it is happening. or any customization is required to avoid this situation.
Thanks in advance!
Karun

Hi Revi,
Thanks for the reply but what is the link of release strategy with PO output processing.
Best regards,
Karun

Similar Messages

Email/print in status "Not processed" when RFQ is published

Hello,
We are running SRM 5.0.
We have set up the event schema for BUS2200 (RFQ) to react on events: PUBLISHED, PUBLISHED_AGAIN etc. And assigned the event schema to RFQ's transaction types, eg BID.
However, when an RFQ is published, the email is not sent to vendor (whose default medium is MAI) or printed on vendor's default printer (if the medium is set to PRN). The output log under bidder/bids tab shows something like :
Status: Not processed
Medium: Print
When I clicked on the action button "Output pushbutton", the status would be changed to "Successful" and the email would be sent or the print job would be printed then.
I have checked the PPTTRIGG table and all the entries in there are of DISPATCH = 1 or 4. Not 3, which seems to indicate an "immediate processing".
My question is how I would configure the system so that the email/print when the RFQ is published could be processed immediately.
Thanks.

Hello Masa,
I realized it as well. I was then a little puzzled why SRM didn't allow "immediate processing" for the "processing time" parameter in the action definition. Do you know if there is a particular reason for that?
Thanks,

Condition-Dependent Output not processed

Hello,
I have configured conditions for output for purchase order documents (BUS2201) in the following path in SPRO > SAP Supplier Relationship Management > Cross-Application Basic Settings > Set Output Actions and Output Format > Condition-Dependent Document Output.
The purpose for this is to check the purchase order status prior to sending out the PO as to ensure that only successfully replicated POu2019s are sent to suppliers. When I create a PO that passes the conditions (iow the conditions are True), the output is generated in a Not Processed status. I have to now process the output manually or by running program RSPPFPROCESS. Once processed, output is successfully sent.
Note that the Time Of Processing setting is set as u201CProcessing when saving documentu201D. I would expect the output to be processed automatically by the system, but it is not.
If I create a purchase order that does not pass the condition (iow the conditions are false) an output is also generated with a Not Processed status, but I am unable to process it due to the conditions that are not met.
Please advise why the output that passes the condition is not processed automatically.
Kind Regards
Rene

Hi, If you want to work with Condition-Dependent PO Output, you have
to set the conditions for output in Define action for Purchase order
output. Under Action determination and Action summarization you can
choose from different option. Also clean-up customizing inconsistencies using transaction SPPFCADM and adjust to determination technology "Determination Using Conditions" to retest. Check note 564826 which may be helpful.
Best Regards
Lauren

OPP(Output Post Processor) not processing the report (XML Publisher)

Hi,
I have defined a concurrent program (XML Publisher report) then ran but failed with the errors below. I am running the report in Oracle E-Business Suite 11.5.10.2, thru a concurrent manager other than Standard Manager. My guess is that OPP(Output Post Processor) is not processing the request outputs coming from a different manager/work shift since requests ran thru Standard Managers are all OK.
In the OAM(Oracle Applications Manager)-> OPP, there is only 1 process allocated for both Actual and Target. If we increase the number of processes, will it work?
/home/app/oracle/prodcomn/temp/pasta19356_0.tmp:
/home/app/oracle/prodcomn/temp/pasta19356_1.tmp: No such file or directory
Pasta: Error: Print failed. Command=lp -c -dkonica4 /home/app/oracle/prodcomn/temp/pasta19356_1.tmp
Pasta: Error: Check printCommand/ntPrintCommand in pasta.cfg
Pasta: Error: Preprocess or Print command failed!!!
Anybody who has experienced similar issue?
Thanks in advance.
Rownald

Hello,
Just an additional tests info. We have 2 concurrent managers which I think is affecting the XML report output - Standard Manager(running 24 hours) and a Warehouse manager (9am-4:15pm).
When I run the report before or after the Warehouse manager workshift(9am-4:15pm), the output is fine - which means PDF is generated and Pasta printing is OK. However, when report is run between 9am-4:15pm, the report only shows XML output with an error in Pasta printing(above). I also found that re-opening the output(ran prior to Warehouse workshift) on the period between 9am-4:15pm would also result to just an XML output instead of the previous PDF.
Anybody who has experienced similar issue like this? Any idea? The report is not directly defined as "inclusion" in the Warehouse manager, only the program calling it. Any effect of multiple concurrent managers in the XML Publisher output?
Thanks in advance for your ideas..

Output 'incorrectly processed', 'output could not be issued'

Hi,
We trying to trigger a Bill of Lading custom Z print output type. This output was working correctly for some time and now it has started failing. When we try to issue the output through screen option it gives message 'output could not be issued'. But we are not able to figure it out as why this message is appearing even though all output configuration is good. The same output is triggering if we make some changes in the shipment change transaction(although changes are not relevent for the output parameters) but this behaviour is not constant as output triggers some time after the changes and some time may not.
When we try to retrigger the output type using messages option on the shipment, error appears as 'incorrectly processed'.
Please suggest as why this output type is behaving like this. Any help will be highly appreciated.
Thanks,
Sharan

if it worked well in the past, then I would check if there was a change in the print program or in the form or in customizing, further I would investigate if this could be triggered from "outside" e.g. implementing OSS notes, activate business functions etc.
If you know the date when it started failing, then checking the transports of changes prior to this event in SE10 could be a good starting point.

IDOC is not processing in R/3 with status 64(Urgent)--Production issue.

Dear Folks,
Here we are implementing MIRROR sytem for data extraction in to BIW.
I had gone through the steps in PDF file(How to minimize down thime for Delta Initialization) which has given by SAP.
These are following steps I had performed in BW production
1. Using RSADMIN transcation- Assigned one user as a Debugging user.
2. With the Debugging user Created one infopackage on Purhcasing ITM datasource--
    In data selection tab, I given date as from 2002 to 2003
    In Update tab, I selected update mode as Initialize Delta process-               without data transfer and Uncheck Update Data in master   system immediately
   In schedule tab I selected option Start Data load immediately then Start extraction.
3.Data was requested and It was intialized properly with green status 1 from 1 Records.
4. In details tab Request, Extraction, transfer(IDOC and TRFC), Processing everything in Green color.
5.As per document I have checked in R/3 for IDOC with status 64 using transaction BD87/WE05
Problem is that IDOC is not processing in R/3 system. for that IDOC I have checked in BW montior screen using the option <b>IDOC list in Source sytem</b>, here also it is not showing any IDOCs.
Please let me know why BW sytem is not sending any IDOCs to source sytem.Is there any settings I could have miss in BW aswell as in R/3 system.
Note: In BW production I successfully loaded master data from R/3. aswell as I triggered infopackage-Initialization with data transfer, it is showing IDOC number properly in R/3 system.
Points is Assured for all replies.

Hi,
- check you RFC destination (normal test + authorization test)
- Check you partner profiles in WE20 and its ports WE21
- from the source system tree (RSA13) right click your source system and perform a check
- the best is to restore your source R/3 source system from BW (right click on it ans select RESTORE); you'll need to be able to log in the source system as an admin as well as opening the source system for customizing in SCC4 so that BW can recreate the correct partner parameters automatically; the best is to do that with your basis group.
hope this helps,
Olivier.

Idoc in 53 status but not processed completely. Missing authorisation error

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
These IDOCu2019s are processed via user background. Not sure why we have authorisation issues as this user has SAPALL. Any ideas?
Thanks
Deepthi.

done.

DLV status not updated in Process order

Hi guys,
I did GR and got goods receipt documents but system is not updating DLV status in process order.
Actually i have by-product and co-products as components in order. I did posting of by-product from Confirmation screen COR6N and for co-products i did MB31 and goods movement doc. get generated. Qty. is also updated in order but NOT the dlv status.
Pl.suggest

Dear,
This is System status and you cannnot maintain it manually once that Business Transaction(FULL Delivery) happens System will automatically sets that status.
DLV status updated once Del completed tick is activated in order header, This tick will get uodated once you do GR for complete qty.
You need to Final confirm (CNF) the Order to get the DLV Status.
Or if the Delivery completed indicator is set in the Process Order, then also th System status will be DLV.
If you want to make it manually then goto co02, enter the order, goto goods receipt tab page and activate delivery completed tick and save...DLV is activated in the head as status.
Please check in BS22-I0012
Regards,
R.Brahmankar

SQL Developer, Deploy Cloud Cart Status is at Approved for a long time and not moving forward i.e. not processing.

SQL Developer, Deploy Cloud Cart Status is at Approved for a long time and not moving forward i.e. not processing.
Please help.
Thanks
Srinivas

Hi Gustavo,
It appears your Service SFTP user was not created correctly. Please contact support and mention the fact that your Service SFTP user appears on Security/Users tab and not on Security/SFTP Users tab.
Vlad

RFQ Msg Status is "Not Processed"

HI
If the message was processed successfully, the status is set to '1' and if an error occurs, the status is set to '2'. Status '0' usually means that the processing program has not yet been started (if the message is to be processed manually, for example).
In my RFQ the processing status is "0" means " Not Processed"
In the msg status a "traingle button" is thr instead of the "Green Button"
How to make this processsed...
Vijay

Hello,
Print the RFQ in ME9A transaction.
Regards,
Shailesh

Idocs neding in 64 status and not processed further

Hi
We have inbound idocs of FIDCC2 message type, which are set to be triggered immediately. However we have noticed that sometimes (not always) these idocs are in 64 status and are not processed further. We have to manually reprocess them.
What could be the problem? Where should we start investigating?
Any help would be appreciated.
Thanks
Mick

I think the comment by Gautham Vangaveti is probably correct.
We hit the same issue occassionally. We have IDOCS as trigger immediately, but at the time they try to process, there are no available work processes which can handle the IDOC and they sit at status 64.
There is an oss note 1333417 which describes the situation
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1333417
And unhelpfully suggests changing over to processing by batch job, which is not always appropriate.
It may be worth enlisting help from you Basis team to try and indentify if those going to status 64 are occuring at the same time each day, and maybe looking to see what other processes are running at that time. If the load on the system can be managed then the problem may go away, it did for us.
Otherwise, Basis may be able to increase the number of work process which may also resolve the issue.

Output message of PO in ECC not processed automatically after order released in GTS

Dear Experts
PO created in cobalt was blocked in GTS due to legal control. output message of PO was blocked, after the PO was manually released by the user next day, AU open the PO and saved it. output message got processed.
Can you please let me know, why system is not processing the output automatically after the PO is released in GTS.
Is this the standard process?
Thanks
Kiran

Hi Kiran,
This is called follow on function in GTS.
When document is released, you could trigger background job regularly to process these document.
Open the area menu for SAP GRC Global Trade Services in your feeder system (with transaction code/SAPSLL/MENU_LEGALR3) and choose Recovery Follow-On Functions in Feeder System .
Choose one of the following entries to configure the follow-on functions for the selected application level: Materials Management Trigger Follow-On Functions for Purchasing Documents
Check more details in help document.
Trigging Follow-On Functions after Document Release in SAP GTS - System Administration - SAP Library
Best regards,
Vincent

Report RBDAPP01 not processing IDocs in status 51

Hello guys,
I have a problem with the execution of some Inbound Idocs using program RBDAPP01.
Now the Idoc is executed in background with a job. Sometimes we have some locks because we receive idocs going to the same order, and then remain in status 51.
In the variant of the job we filled to execute Idocs with status 64 and 51, but the idocs that remain in status 51 are not processed, at the end we have to do it manually.
There is no parallel processo to avoid the locks.
Do you know how we can solve it?
Many thans in advance.
Regards,
Xavi.

i do have the same problem. is there an solution to this?

Idoc in 53 status but not processed completely.

Hi ,
Some of the ORDER Idocs are in 53 status, but the orders are not processed successfully and no PO created for these Idocs.
They got below warning message when I checked in WPER transaction code.
" Missing authorization: Purchase Order Create Purchasing Grou 110 " - "Workitems (tasks) were created for this IDoc"
This is happening once in a while for some of the idocs. Remaining all idocs are posting successfully.
Any idea what might be the reason?
Thanks
Deepthi.

Hello,
This seems to be an Authorisation issue, Kindly check for Purchasing Group 110, who are all assigned Buyers...
Then for those Buyers.. you can check what authorization is missing from Su53..
Compare with those who has authorisation to create PO Vs who does not have ..
you will have to provide the same authorisation to those users
Thanks and regards
PJ

Check Deposit List - cannot post Processing status not correct

Hi Expert,
I was trying the edit a check deposit list and I encountered error message during save.
"Cannot post. processing status not correct."
Procedure: Go into statement/list processing and save again. The processing status is then changed to 3 (revised).
How to go to statement/list processing to change to status to 3?
thank you

Hi,
Use T Code FF67,
Select the Check deposit list and click enter. Now go to Settings > Specifications
Here you will find the "Processing Status" for you to continue.
Regards
AKV

PO output status not processed

Similar Messages

Maybe you are looking for