Get Idoc Types Processed by Jobs Running Programs RBDAPP01 or RBDMANI2

Hi Everyone! I would just like to ask if there is a way I can identify all background jobs which are processing a specific idoc type in SAP?
For example, I want to get the Jobs that are processing inbound idoc type WMMBXY using program RBDAPP01 or RBDMANI2.
Is there a way to extract this information?
Thanks in advance!

Vincent, we have a conservative approach RE those programs that re-process IDOCs in pending or error status : we do not define those jobs with open selections, instead we are specific in terms of message type and partner where applicable. We also set a limit in the number or attempts on a failed IDOC by setting a 'rolling start date' (like current date - 7). Besides audit considerations about lingering processes, you also need to take into account the impact of this process on the tale size. Each time the job runs and the IDOC fails, a status record will be added to the EDIDS table for each of those IDOC. If you do not pay attention, you may end up with large amounts of data. This is not only going to unplease your BASIS and DB administrator but eventually put in jeopardy your archiving process (wchich could lead to a system crash !!).
We usually aslo complement those jobs with a status change step (moving from error to no further processing) ; the date parameter can be set to something like anythiing with a creation date > current date + 3 months
To come back to your question : SM37 using the program name as parameter will help you find the associated jobs, but you might need to look into the step(s) and associated variant to get the messages those jobs / steps are processing

Similar Messages

Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 ,214

Hi friends,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender)., 214 (Shipment Status )
For shipement status i got trxstc01 for idoc type .. but its only before 4.6 version ..for 4.7 its not there .. please give the alternate for that ...
Thanks in Advance ....
If any one is provide exact answer i will give Max marks ..
Edited by: ajay KOLLA on Aug 6, 2009 8:04 AM

Hi,
Have you resolved this issue. If yes, can you please let me know. Im actually looking for same for EDI 867 (guess it is for summary report and need to know message type, Idoc type associated with this).
Rgds
Sudhanshu

Message type ,IDOC TYPE , PROCESS CODE for Edi 990

Hi ,
Please provide the Message type ,IDOC TYPE , PROCESS CODE for Edi 990 (Response to a Load Tender).
Thanks in Advance.
Ajay Kolla

Hi
Pls check the below links
1. http://www.erpgenie.com/sap/sapedi/ansi.htm
2. http://www.erpgenie.com/sap-technical/ale-edi-b2b/master-data-message-types-idoc-types
Hope this may helps you.
Regards
Sirigiri

How to get the list of batch jobs running in a specific application server

Hi Team,
I am trying to check in SM37 if there is any specific condition to get the list of batch jobs assigned to a specific target server but cant find any.
Is there is way to find the list of batch jobs assigned to run in one specific application server.( Target server specified in SM36 while job creation)

Hello,
This is what you can do in SM37.
Execute the list of batch jobs, when the result appears on the screen edit the ALV grid via CTRL+F7.
Now add the following columns "TargetServ" and "Executing server".
You will now have two extra columns in your result list.
TargetServr contains the value of the application server where the job should run when you have explicitely filled it in.
Often this is empty, this means that at runtime SAP will determine itself on which application server the job will run (depending of course where the BGD processes are defined).
Executing server is filled in always for all executed jobs, this is the actual application server where the job has run.
You can also add these two fields in your initial selection screen of SM37 by using the "Extended job selection" button.
I hope this isusefull.
Wim

Idoc processing best practices - use of RBDAPP01 and RBDMANI2

We are having performance problems in the processing of inbound idocs. The message type is SHPCON, and transaction volume is very high. I am a functional consultant, not an ABAP developer, but will try my best to explain our current setup.
1)     We have a number of message variants for the inbound SHPCON message, almost all of which are set to trigger immediately upon receipt under the Processing by Function Module setting.
2)      For messages that fail to process on the first try, we have a batch job running frequently using RBDMANI2.
We are having some instances of the RBDMANI2 almost every day which get stuck running for a very long period of time. We frequently have multiple SHPCON idocs coming in containing the same material number, and frequently have idocs fail because the material in the idoc has become locked. Once the stuck batch job is cancelled and the job starts running again normally, the materials unlock and the failed idocs begin processing. The variant for the RBDMANI2 batch job is currently set with a packet size of 1 and without parallel processing enabled.
I am trying to determine the best practice for processing inbound idocs such as this for maximum performance in a very high volume system. I know that RBDAPP01 processes idocs in status 64 and 66, and RBDMANI2 is used to reprocess idocs in all statuses. I have been told that setting the messages to trigger immediately in WE20 can result in poor performance. So I am wondering if the best practice is to:
1)     Set messages in WE20 to Trigger by background program
2)     Have a batch job running RBDAPP01 to process inbound idocs waiting in status 64
3)     Have a periodic batch job running RBDMANI2 to try and clean up any failed messages that can be processed
I would be grateful if somebody more knowledgeable than myself on this can confirm the best practice for this process and comment on the correct packet size in the program variant and whether or not parallel processing is desirable. Because of the material locking issue, I felt that parallel processing was not desirable and may actually increase the material locking problem. I would welcome any comments.
This appeared to be the correct area for this discussion based upon other discussions. If this is not the correct area for this discussion, then I would be grateful if the moderator could re-assign this discussion to the correct area (if possible) or let me know the best place to post it. Thank you for your help.

Hi Bob,
Not sure if there is an official best practice, but the note 1333417 - Performance problems when processing IDocs immediately does state that for the high volume the immediate processing is not a good option.
I'm hoping that for SHPCON there is no dependency in the IDoc processing (i.e. it's not important if they're processed in the same sequence or not), otherwise it'd add another complexity level.
In the past for the high volume IDoc processing we scheduled a background job with RBDAPP01 (with parallel processing) and RBDMANIN as a second step in the same job to re-process the IDocs with errors due to locking issues. RBDMANI2 has a parallel processing option, but it was not needed in our case (actually we specifically wouldn't want to parallel-process the errors to avoid running into a lock issue again). In short, your steps 1-3 are correct but 2 and 3 should rather be in the same job.
Also I believe we had a designated server for the background jobs, which helped with the resource availability.
As a side note, you might want to confirm that the performance issues are caused only by the high volume. An ABAPer or a Basis admin should be able to run a performance trace. There might be an inefficiency in the process that could be adding to the performance issue as well.
Hope this helps.

IDOC - sequential processing

Hello,
I hope someone can help me with this problem concerning the processing of IDOCS.
We got an Warhouse management system connected as a subsystem to ERP6.0.
First we get a WHSCON for a return shipment (stocktyp R). The subsystems sends directly after the WHSCON an WMMBID02 to transfer the stocks from R to free.
The WHSCON locks the system and the WMMBID coming in directly after it can not be processed.
So how can I enforce the system to process the second IDOC in sequence only when the delivery is not locked?
Thanks
Christian

Hello Christian,
without much effort, you can try to solve you problem with following solution.
Change IDoc processing (WE20) for second (or both) IDoc from "Trigger immedeately" to "Trigger by background program".
Schedule batch job for program RBDAPP01 (without parallel processing).
Best Regards, Dirk

Background job is taking lot of time for processing the job.

One background job - which is processing Idocs is processing a job for more than 2000+ seconds.. and completed tho.
But this is happening for the past few days.. is there any way to trouble shoot, or find from any logs of this completed job, to find out why it was taking lot of time for processing.
Can you please tell me the steps of analyzing / trouble shooting why it was taking lot of time daily.
Regards,
Satish.

Hi Satish,
Run DB stat from db13 it will improve the performance.
Check number of idocs. You can send part by part, instead of sending huge data.
Check SM58 logs
Suman

Exception "Cannot run program" while using ProcessBuilder class

Hi Java-Folks,
I try to start a program within a Java application using the ProcessBuilder class. This is the first time I use ProcessBuilder so I do not have any deep knowledge of it. Here is a snippet of my code:
static void connectToHost(String Host) {
ProcessBuilder pb = new ProcessBuilder("connect.exe"), Host);
Map<String, String> env = pb.environment();
env.put("SHELLWIDTH", "64");
pb.directory(new File("C:\\MyProgram\\ExApp\\shell"));
try (
Process p = pb.start();
} catch (IOException ex) {
Logger.getLogger(ShellUtil.class.getName()).log(Level.SEVERE, null, ex);
}Using this method I get an IOException which says *"Cannot run program "connect.exe" (in directory "C:\MyProgram\ExApp\shell"): CreateProcess error=2, The system couldn't find the specified file"*
Does anybody have an idea why this is not working? I tried to start another application like "notepad.exe" and that works fine. So it seems related to the fact
that the program I want to start is only available in a certain directory and not via the PATH env-variable.
I would appreciate any help or hint :-)
Regards,
Lemmy

Okay I guess I misinterpreted the JavaDocs regarding the directory method. The exception message is a little bit confusing too, because it seems like Java tries to find the Application within the specified
working directory.
I tried to use the full path with the ProcessBuilder constructor and it looks like this variant is working. I still have some trouble with the application itself but I was able to start another program which is
not in the PATH var, using the full path to the executable.
Thanks for the help so far.
Bye
Lemmy

Outbound idoc types in XI

I was creating partner profile using we20 in XI to send and receives idoc of type ORDERS and ORDRSP. In the outbound parmtrs section I am not seeing ORDERS type. I clicked the + sign under the outbound parmtrs, it opened a new page to create a outbound paramets. I did not see ORDERS message type, so I created a message type called ORDERS and ORDRSP using we81. When I came back, I do see the message type I created. Now, I need to select the basic idoc type in the outbound options but I am not seeing ORDERS or ORDERS05 to select. Why isn't XI have the basic IDOCs for ORDERS.
Am I missing something?

Hi,
WE81 is the transaction for creating Logical Messag types in SAP R/3. Since XI is one of the R/3 product, you have an option to create the message types.
normally, Partner Profiles are maintained for Business communication in R/3 using EDI media. I am not sure, if at all XI will be used as a business partner as it is a middle layer kind of environment giving an interface facility to R/3 to the outside environment.
Coming to your question, XI need not to have all the message types/IDOC types as we see in R/3. IDOC Type definitions will be downloaded into XI for making it available for data transmission using the transaction IDX2 and is also known as IDOC CACHE.
To be able to help you out, let us know your scenario in which you are using XI as a business partner.
Further, Default Outbound parameters will not be available when a partner profile is created. You have to assign the business rules to it so called MESSAGE TYPES, IDOC TYPES, PROCESS CODES, RFCDESTINATIONS/PORTS, PACKET SIZES, MESSAGE CONTROLS. etc.,
What have you done? You have created a message type ORDERS/ORDERSP thru WE81, but no IDOC types are created.
Normal flow:
MESSAGE TYPE-->IDOCTYPE, PROCESS CODE
IDOC TYPE --> SEGEMENT TYPES
IDOC records are of three types. 1)Control Record holds the Sender/REceiver info, data header etc.,
2) Data record holds the data or body of message
3) Status record to hold the message status pre and post transmission.
All these makes a full cycle and is not an easy job to do buddy.
I am sure, nobody would want to create these in XI.
Let us all know what you were trying to achieve.
Good Luck,
Srini.

Multiple idocs in Single Job behaves differently (RBDAPP01)

Hi,
How to debug the background Job for Program RBDAPP01 which already posted the Idocs in 53 status from 64.
I wanted to analyze why multiple idocs in same job behave differently than the single idoc in a job. In case of multiple idocs in a single job i put packet size 1, but no help.
Thanks,
Asit Purbey.

I found the solution, so closing this Post.

Runn time error "CNTL_ERROR" for batch job created for program RBDAPP01

We have encounter run time error and the batch job for program RBDAPP01 was terminated.
Information on where terminated
    Termination occurred in the ABAP program "CL_GUI_CUSTOM_CONTAINER=======CP" -
     in "CONSTRUCTOR".
    The main program was "RBDAPP01 ".
    In the source code you have the termination point in line 62
    of the (Include) program "CL_GUI_CUSTOM_CONTAINER=======CM001".
    The program "CL_GUI_CUSTOM_CONTAINER=======CP" was started as a background job.
Can any member reachout help in identifying the reason.

Hi Amol,
Check the following link.
Call Transaction 'VL32N' in background: termination with Exception
Regards,
Raju.

IDOC Types for Purchase Orders, Vendor Master and Goods Receipt

Hello All,
Can any have idea about the IDOC Types that can be used for triggering when the actions creation/change/deletion on Purchase Orders or Vendor Master or Goods Receipt is performed?
Please let me know the names of IDOC Type, Process Codes, message type... and all the other required information...
Thanks in Advance,
Kumar.

Hello Ferry,
Thanks again for the IDOC Types. I have another question. Can we use those IDOC types for creating/changing/deletion of Purchase orders or Vendor Master or Goods Receipt happens? I mean can we configure in such a way that when ever there is a change or deletion of PO or VM or GR happens?
I have got to know about the IDOC PORDCH01 which can be used for Purchase Order. Can u suggest me which can be used for PO's?
Regards,
Phani.
Message was edited by:
Sivapuram Phani Kumar

How to reduce excessive job run time

Hi all,
please any one let me know how to reduce excessive job run time

What you exactly mean by excessive run time? Job runtime is due to many factors like data to be processed , many jobs running same time , waiting for another jobs , hardware bottleneck etc etc ...
If this is not looking for please explain your question a bit more
Thanks
Prince Jose

Error with Run Program Service in invoke runbook.

I made main runbook (it do some things) and on the end i pute invoke runbook. In this child runbook i have
Run Program activities with Java srcipt.
When started this rb finaly i get error Could
not start Orchestrator Run Program Service service on 10.56.7.17 - Access is denied. (code 5),
but when manually i run this child runbook with any chaneges and this same date it works well.
In this Run Program i set that it ryn from admin acount but that don't nothing changes.
Where is problem?

When you run it manually (with Runbook tester I assume) the Runbook will use
your admin credentials to perform all of the actions. When it runs scheduled or with an invoke from somewhere else it will use the credentials of the user account you've assigned to the Runbook service.
As a test, check which user is assigned to the service (via services.msc) and make that one a temporary local admin on the target machine. If it works, then you know it's permissions related to that specific account.
I give up ;), Yes, I testing by Runbook tester. But not shure that we understand :)
I have two scenarios (i can't put images, i need to verify my account).
1) One runbook. Exp. name" child. Inside is Run Program, that program is on different server.
Its work only when in options this activity i set local admin account from that server.
2). I created new runbook - parent. In this I put invoke runbook linked to that child. I do not change anything else. Now i will try run it (from tester, web console or scheduled) i get error
Could not start Orchestrator Run Program Service service on 10.56.7.17 - Access is denied. (code 5).
What I do wrong, what I think wrong?

Getting the variant name when the report program is run in background

Hi All,
How to get the variant name for the report program when run in background? My requirement is to create an email attachement with the name 'variant.XLS', where variant = selection screen variant, when the report program is run in background. The system field SY-SLSET holds the variant name only when run online.
Any pointers to this will be highly appreciated.
Thanks and regards,
Nilesh.

Hello Nilesh,
Please find the algo:
1. Call the FM: GET_JOB_RUNTIME_INFO to get the background job details.
2. Select data from TBTCP using these details:
DATA:
FP_EVENTID TYPE BTCEVENTID
FP_EVTPARM TYPE BTCEVTPARM
FP_ACTIVE TYPE BTCXPGFLAG
FP_JOBCNT TYPE BTCJOBCNT
FP_JOBNM TYPE BTCJOB
FP_STEPCNT TYPE BTCSTEPCNT.
CALL FUNCTION 'GET_JOB_RUNTIME_INFO'
 IMPORTING
 EVENTID = FP_EVENTID
 EVENTPARM = FP_EVTPARM
 EXTERNAL_PROGRAM_ACTIVE = FP_ACTIVE
 JOBCOUNT = FP_JOBCNT
 JOBNAME = FP_JOBNM
 STEPCOUNT = FP_STEPCNT
 EXCEPTIONS
 NO_RUNTIME_INFO = 1
 OTHERS = 2.
IF SY-SUBRC <> 0.
* Error calling FM: GET_JOB_RUNTIME_INFO
ENDIF.
DATA: FP_VARIANT TYPE BTCVARIANT.
SELECT JOBNAME JOBCOUNT STEPCOUNT VARIANT
FROM TBTCP
INTO TABLE L_IT_TBTCP
WHERE JOBNAME = FP_JOBNM
AND JOBCOUNT = FP_JOBCNT
AND STEPCOUNT = FP_STEPCNT.
IF SY-SUBRC = 0.
 SORT L_IT_TBTCP BY JOBNM JOBCNT STEPCNT.
 READ TABLE L_IT_TBTCP INTO L_WA_TBTCP INDEX 1.
 IF SY-SUBRC = 0.
 FP_VARIANT = L_WA_TBTCP-VARIANT.
 ENDIF.
ENDIF.
Hope this helps.
BR,
Suhas

Get Idoc Types Processed by Jobs Running Programs RBDAPP01 or RBDMANI2

Similar Messages

Maybe you are looking for