Proxy messgs on ECC in scheduled status - released for processing (PI 7.1)

Hi guys,
I have set up a scenario (ABAP Proxy(ECC)->(using WS adapter)PI7.1->SOAP) and the outbound messages on the ECC remain in the scheduled status (green flag) saying "Released for processing (WS)". Why? Must there be some processing be executed? Manual? Or job?
Any help on this appreciated, Olian

Hi Olian
Try applying the solution in the SAP note #1129614 SP2: WSRM sequences process only the first 3 messages.
Regards
Mark

Similar Messages

Cant set status released for Generation Variant for report category IBD_MSD

Dear EH&S people,
I am trying to upload a vendor MSDS'. I am not succesfull in this. The reason is that the status of the generation variant is not "Released".
I am not able to set the status released in the Generation variant. I am using report category IBD_MSD which should be the standerd one for Vendor MSDS.
Together with an abap consultant we found via debugging of the matchcoded of the search of the status that he takes the DMS document type SBR as a basis. It should however be IBD.
Has somebody encounter this problem before and have a solution for this?
Is there somewhere customizing which controls for a certain category which DMS document type to use?
Thanks in advance for your answer.
Regards,
Pascal

Hi All,
I found the solution.
I looked at the detailed customizing of the document type SBR. Note 1091699 explained detailed settings of the different document types.
SBR was not correct customized.
It sounds strange that SBR is used for the report generation status for Vendor MSDS. I think it is because SAP treads it as if it is a raw version. So that could be an explenation why it searches for the status of that document type.
After I updated the SBR-type correctly, I was succesfull in uploading Vendor MSDS. The DMS type which was used to save the document was IBD.
Thanks all for your help.
Issue closed.
Regards,
Pascal

Scheduled finish date for process orders not updating in BW

We are having problems with the scheduled finish date (GLTRS) for process orders. When the process order is already released, changes done in R/3 on the scheduled finish date will not result to a delta hence data in BW is not updated. Table AFKO, where data is coming from, is always updated with the changes though. 2LIS_04_P_MATNR is used in extracting the data.
Has anyone experienced the same problem? We are looking for possible ways on how to have a delta whenever there are changes on the process order even after it is already released.
Any help would be greatly appreciated...

Hi Donna,
If I've understood your problem correctly, you can increase the load frequency as Sriee has pointed out.
If you want latest data frequently and if you are on BI 7.0 then you can look at Real Time Data Acquisition(RDA)
Regards,
Tom.

User Status Profile for Process Order Operations

Hello Experts.
I have a need to set up a User Status at the Process Order Operation level that will prevent operation confirmation when the status is Active .
I have been successful at the following:
   --- Created a new Status Profile (transaction BS02),
   --- Creating a u201CHoldu201D status,
   --- Defined the Influence on Business Transactions,
   --- Set the allowed Object Types for the profile.
   --- In an individual Process Order operation, I can now select the Status Profile, and set the Hold status, and it functions correctly.
My problem is that I canu2019t figure out how to set my new profile as a default for Process Order Operations. For Production Orders, this is done in the IMG definition for the Order Type (transaction OPJH), updating field T003O-VRG_STSMA. However the Order Type definition for Process orders (transaction CORN) only has a field for a status profile at the header level. Iu2019ve searched through Configuration and the Recipe, and the Production Version, and the Control Key, but can find no where to set the default status profile for a Process Order Operation..
As a final desperate act, I manually edited a T003O record for a Process Order Type in our test system, but even this failed to set a default Operation Status Profile for subsequently created Process Orders.
If you have any knowledge about this, then please help.

As of this date, we have still not implemented a fix, but I did get some information from someone else who has.
I'll post his information here for all to see. Hope you find it helpful.
From: Joe
Yes we managed to do it.
After several false starts and CMOD/projects which suffered because only the default keys (for order number, aufpl etc) were in place and not the actual, we coded up the IN_UPDATE method in the WORKORDER_UPDATE badi. This gives us the final format after the DB save (but before the commit). The update of the STATUS using the SAP std function module was actioned successfully but the status profile was not actually passed through. We assumed that this was because of the update task - so we introduced an INSERT into JSTO instead (a bit naughty I know, but desperate needs etc). If you require anything more let me know.
Best Regards
Joe

Partal release for process order

Hi,
My scenario is like the below.
I have one operation in my operation in my master recipe.So all the materials with the requirement quantity wll be assigned to that operation. Now I have created a order with 20 FG quantity.But I have RMPM according to FG quantity of 10 as per BOM.I want that the system will allow me to release the order partially for that 10 Fg quantity.
Waiting for your kind reply.
regards,
kaushik

Hi,
Partial conversion is already considered but the issue with the same is explained below.
Suppose you have an order for 50.the minimun lot size is 30.You have RM in stock for 35.Now according to you my planned order should be partially converted and the remaining planned order will be of 15 kg which is unconveratble.Now i can change the error msg of conversion of planned order lower than lot size maintained in production version.But this will violate the business requirement.
I think the problem is clear with you now.
regards,
kaushik

Scheduled Status in Message Monitoring

Hi All,
We have a scenario from DB- DB using Java Proxies. The Message interfaces are defined as Asynchornously with EO mode.
Usually the sender channel picks data and tirggers Java Proxy. Proxy process all records and send the status back to sender in 5 mins.
But when I started multiple interfaces at the same time, I observe that one interface is taking 15 min and while that interface is in processing state, the other interface which started at that time are also in Scheduled status. But the sender channel picks data for every 5 mins, which is creating duplicate records.
The interfaces which are in Scheduled status are getting processed only after that interface ( taking 15 min) gets processed.
Why is this dependency on other interfaces and is there any way to avoid this dependency?
Please suggest.
Regards,
Srini

you can do queue/message prioritization.
but I suggest to use one status field in DB, when you are polling DB to select records , immidiately change staus to picked and after processing successfully change it to processed.

Manage Queues - Messages are in Schedule status after upgrade to ERP2004

Hi,
We upgraded SAP to version ERP2004. ABAP proxy XI messages are in schedule status even though we deregister and register & activated all queues.
When I click on the queues it is in running status.
Does anyone has any idea where should I look?
Thanks in advance!
Mrudula

Hi,
my scenario is file to idoc....
I have set paraemter in SXMB_ADM as below.
Category Parameters CurrentValue DefaultValue
RUNTIME HTTP_TIMEOUT 100000 0
I have gone through as you suggested still when i double click on message in SXMB_MONI...i am getting Runtime Error (TIME_OUT).
Please do help me..
Thanks in advance.
Krish

Difference between Scheduled and released with respect to process chains

HI All,
I am Creating a cube in whcih I want to upload the current status of the process chain.
And the requirement is not to take those process chains whcih are scheduled and not released( only take those process chains whcih have status released)
for the same I dont know what is the difference between Scheduled and Released in respect of process Chains and also from whcih Database table I can get this information.
Please help.
Regards,
Ujjwal

Hi,
Job Status Scheduled means a job has been created and is ready to run but has not yet been triggered.
A release status means the created job has been triggered and is waiting for the opportunity to run. A job can be in released status when it is a periodic Job ( Where once the job is completed it goes to release status), when it is slated for future execution, or when there is a delay due to database overload.
Regards,
Pramod

Schedule line Release with help of release creation profile.

Hello,
Is it possible to create the schedule line release for scehule line automaticaly by heuristcs run with the help of release creation profile of external procurement relationship ?
We can release the schedule line in product view.
What is other way release the schedule line?

Hi,
Credit check is done to see if the customer has crossed his credit limit or not. Incase you want to forcefully release order we use [VKM1]. What is this got to do with the schedule lines??? Irrespective of whether the order is under credit hold or no the schedule line are determined the same way. Didnt understand the connection.
Regards
Nadarajah Pratheb

Undefined status for process chains

Hello,
- when do you choose undefined status (grey) for process chains? (in what cases)
Thanks

Hi ,
when you are defining the Pc in planning view , then the color will be grey . In checking view - it will be green ( Successful ) , Yellow ( warnings) Or Red ( Failure) .
In the joboverview also , above discussed colors are stated for the Pc 's accordingly ..
Hope this helps out

Proxy messages are stucked in SMQ2 as scheduled status

Hi,
I am doing File(FCC) >PI 7.0>ABAP proxy. (ECC) Scenario.
Once i pick and process the file, the resultant message is updating the table in ECC through ABAP proxy. These messages are getting stucked in queues (SMQ2) in ECC. My message is not having much data , it is very less in size.
And there is no messages in Queue.
I register all queues in SMQR in PI and ECC.
Does I need to do any activity in ECC or PI? What could be a problem. Please suggest .
Thanks
Ayub

Hi Venkata,
Thanks for very quick replay.
Are the messages stuck with any error?--> First I can see the Green Color Flag as scheduled status, I open the message I can see there is no error message.Bt when I have look at end of the message in SXMB_MONI at Q.Status , I can see Message Has error
In SMQ2 -->
Cl. Queue Name               Entries    Status   Date 1     Time 1   NxtDate           NxtTim                  Sender ID                        Wait for queue
200 XBTR0009                         1 SYSFAIL 24.02.2012 10:53:34 24.02.2012 10:53:34      R3DEVQA_RDV_01
And when I double click the XBTR009 I can see the below message :
Cl.       User                  Function Module                 Queue Name                Date        Time                       StatusText
200 ALEREMOTE    SXMS_ASYNC_EXEC                 XBTR0009                  24.02.2012 10:53:34 Screen output without connection to user.
This are status of the messages. Please help me.
Regards,
Ahmed

Send Commit to message stuck in "Message Scheduled" status

Hello,
I generated some messages using ABAP Proxy. However, the commit work never happened in the program that created the message. Now these messages are stuck in "Message Scheduled" status. How can I push the message forward. Can I trigger a commit? If so, how?
Regards
Cerish

Hi Cerish,
Are you getting this status in the XI ? If so, go to Queue Monitor and try to activate the same.
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Also check the SXMB_MONI of Application System(R/3) if you have a access about is proxy message is executed or not .
If the status is restart not possible, then you need to reprocess that.
Hope this helps,
regards,
moorthy

Messages in Schedule status in SXMB_MONI and going into queue in SMQ2.

Hi Experts,
All messages in XI going to schedule status in SXMB_MONI. When i check in SMQ2 to release after some time the messages are going to "SYSFAIL (Time limit exceeded)" status.
When i double click on the message in SXMB_MONI, the system is going to "Runtime Error (TIME_OUT)".
Could anyone please help me how to fix this issue.
Thanks in advance,
GRK

Hi,
my scenario is file to idoc....
I have set paraemter in SXMB_ADM as below.
Category Parameters CurrentValue DefaultValue
RUNTIME HTTP_TIMEOUT 100000 0
I have gone through as you suggested still when i double click on message in SXMB_MONI...i am getting Runtime Error (TIME_OUT).
Please do help me..
Thanks in advance.
Krish

XML file getting stucked in queue in ECC preventing material status in MDM.

XML file getting stuck in queue in ECC preventing material status in MDM to be changed.
Hi SAP Experts,
We have an issue regarding XML messages getting stuck in queue in ECC preventing the material status in SAP MDM to be changed from "Approved" to "Updated/Posted".
Checking in transaction SXI_MONITOR the status of the XML Messages are Scheduled or Green Flagged, looking at the time started it has been an hour and it is not yet processed successfully; and also checking the queues XBTR* (XBTR0001, XBTR0002 and ETC.) via transaction SMQ2 have stopped.
We need to manual process the XML messages for it to be processed successfully.
I'm unable to understand why these files are getting stuck in Queue's.
Many thanks in advance and have an awesome day ahead.
Regards,
Aeron Merc

Hi Aeron,
Check whether the Queue XBTR* (XBTR0001, XBTR0002 and ETC.) is Unregistered in SMQR.
If it is so you can see as U in the Queue type.
Try to register by selecting the queue and click on Registration button and activate.
Then check your message in MONI, hope this should solve your problem.
Thanks
Sai.

SM37 - Scheduled and Released.

Hi All,
In SM37 (Simple Job Selection Screen) what is the difference between Scheduled and Released status??
Regards.

Hi Kumar,
Scheduled -> means the job has been triggered
check this link ...
http://help.sap.com/saphelp_nw04/helpdata/en/c4/3a8016505211d189550000e829fbbd/content.htm
Hope this helps,
Sudhakar.

Proxy messgs on ECC in scheduled status - released for processing (PI 7.1)

Similar Messages

Maybe you are looking for