Prozessing of Idocs as background job

Hello everybody,
At first, I hope this is the correct thread for this posting.
I have a problem with processing the generated idocs.
I create Idocs for example for all Customers (message type DEBMAS) with the transaction bd12.
Afterwards I process the Idocs with the transaction WE14 (program RSEOUT00).
The parameters I set are for example the packages size (= 100) which is necessary to avoid a lock table overflow, the message type, receiver system and so on.
The jobs works fine and without errors and all Idocs will be process and receive a new Status.
I do this with a background job (sm36) and create for each programm a step.
The problem is, that if I start the transaction we14 inside the background job with this parameters the process use user dialog processes. This means that the process reserve all available user dialog process from the system.
I think it starts/reserve for each package which should be processed a new dialog process.
After a short time nobody can work longer with the system because no dialog processes are available.
Why use this process no background processes or why use this process dialog processes?
Is this possible to configure anywhere?
Regards
Christian

Where should I specify the package size?
If I create a new partner profile with we20, I get only following tabs:
- Post processing: permitted agent
- Classification
- Telphony
I can't insert a package size there.
If I add a new outbound parameters with Message Type DEBMAS, I can only choose between "Collect Idcos" or "Process Idocs immediately".
Maybe I must use a other type of receiver port?

Similar Messages

Inbound IDoc creating background job even for trigger immediately setup

All,
I have a very serious problem in our production system.
Scenario:
Vendor is chagend in system A (Outbound) and the same is interfaced to System B (Inbound) and i am using trigger immediately option, but still I am seeing a background job is created for 'RBDAPP01' and creating the spool request. The issue is I am sending 1000 of idocs and the spool number is increasing daily in system B.
So, can any one explain me why the background job is getting triggered even though I set the partner profile settings as 'Trigger Immediately'.
The above issue is not happening in our quality system it simply updagtes vendor information in system B with out creating any background job. Please note that the same settings are maintained in both the systems.
Your immediate inputs are really valuable for me.
Regards,
Suman

This is an performance issue on the receiving system. In case the system does not have enough resources to process the IDoc immediately it will always schedule a background job to ensure the processing of data.
You need to check whether the system has enough work processes available during the time when 1000 of IDocs are received or send the IDocs in packages with some time in between.
Regards,
Kai

Background job scheduling in idocs

Hi can u plz tell me like for a customized function module inorder to post and idoc .
variant should be created for function module or how does it go becoz we process the idoc through transaction we19?

In the receiving system, set inbound processing to Processing in background in the partner profiles with transaction WE20.
Schedule Report RBDAPP01 as a Background Job to process the IDocs (see also SAP Note 399271).
The report passes all inbound IDocs to the application for processing, if they meet the selection criteria, and have the following status:
Status 64, IDoc is ready for transfer to the application
Status 66, IDoc is waiting for preceding IDoc (Serialization).
http://help.sap.com/saphelp_sm32/helpdata/en/5f/45f93b4139b478e10000000a11402f/content.htm
Thanks

IDoc failure in background job

Hi,
I have developed a customized program and sending outbound IDocs to other SAP system using Function Module MASTER_IDOC_DISTRIBUTE. When I am running this program in background mode IDocs are failed with reason 'Entry in outbound table not found'.
But when I am running the same program in foreground then IDocs are getting posted properly. Partner Profile and port are set properly.
Please anyone could give me reason behind IDocs failure in background Job.
Many Thanks.

Hi,
Message Number for the message is "Entry in outbound table not found' E0 - 400. This Mesasge used
in the below programs.
Programs asying that there is no Entry in EDP13(Partner Profile : Outbound(Technical Parameters)) Table. Debugg the Background job in SM37 by entering JDBG in the command field then it will go to debugging mode. Then put break point for "MESSAGE".
Thanks,
Naresh Mochi

Submit RSEOUT00 as background job

Hi all,
Here is my requirement.There is a Z program from which RSEOUT00 program has to be called , so that it will change the Idoc status to '03'. I tried using Submit RSEOUT00..and return and also tried JOB_open and then SUBMIT rseout00 WITH docnum EQ p_idocno user sy-uname via job jobname number jobcount and return and then JOB_CLOSE .I checked SM37 also where i can see this job as finished..
I tried COMMIT WORK statement and also WAIT statement .
But still the idoc status wont change to '03' .
Can anyone plase advise on how to correct this .
Regards,
Sudheer

Hi,
I have created background job for RSEOUT00 and written the below code. It worked.
DATA: w_number           TYPE tbtcjob-jobcount,
           w_name              TYPE tbtcjob-jobname VALUE 'ZTEST_JOB'.
   CALL FUNCTION 'JOB_OPEN'
     EXPORTING
       jobname          = w_name
     IMPORTING
       jobcount         = w_number
     EXCEPTIONS
       cant_create_job = 1
       invalid_job_data = 2
       jobname_missing = 3
       OTHERS           = 4.
   IF sy-subrc = 0.
     SUBMIT rseout00 VIA JOB w_name NUMBER w_number AND RETURN.
     IF sy-subrc = 0.
       CALL FUNCTION 'JOB_CLOSE'
         EXPORTING
           jobcount             = w_number
           jobname              = w_name
           strtimmed            = 'X'
         EXCEPTIONS
           cant_start_immediate = 1
           invalid_startdate    = 2
           jobname_missing      = 3
           job_close_failed     = 4
           job_nosteps          = 5
           job_notex            = 6
           lock_failed          = 7
           OTHERS               = 8.
       IF sy-subrc <> 0.
       ENDIF.
     ENDIF.
   ENDIF.
Thanks,
Appanaboina

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

Background job is running for long tome in source system (ECC)

Hi All,
Background job is running for long tome in source system (ECC) while extracting data to PSA.
I checked in ECC system SM66,SM50 the job is still running
in SM37 the job is Active
There are only maximum 7000 records the extractor is 2LIS_02_ITM but it is taking 11 to 13 hours to load to PSA daily
I had checked enhancements every thing is correct.
Please help me on this how can I solve this issue.
Regards
Supraja K

Hi sudhi,
The difference between Call customer enhancement... and Result of customer enhancement:... is very less we can say this as a second.
The difference is between LUWs confirmed and 1 LUWs -
   and Call customer enhancement -
Please find the job log details below, and give me the solution to ressolve this
01:06:43 ***01:06:43 * ztta/roll_extension........... 2000000000                              *                 R8           050
                 R8           048
01:06:43 1 LUWs confirmed and 1 LUWs to be deleted with function module RSC2_QOUT_CONFIRM_DATA     RSQU          036
06:56:31 Call customer enhancement BW_BTE_CALL_BW204010_E (BTE) with 5.208 records                  R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 Call customer enhancement EXIT_SAPLRSAP_001 (CMOD) with 5.208 records                      R3           407
06:56:31 Result of customer enhancement: 5.208 records                                              R3           408
06:56:31 PSA=1 USING SMQS SCHEDULER / IF [tRFC=ON] STARTING qRFC ELSE STARTING SAPI                 R3           299
06:56:31 Synchronous send of data package 1 (0 parallel tasks)                                      R3           410
06:56:32 tRFC: Data Package = 0, TID = , Duration = 00:00:00, ARFCSTATE =                           R3           038
06:56:32 tRFC: Start = 00.00.0000 00:00:00, End = 00.00.0000 00:00:00                               R3           039
06:56:32 Synchronized transmission of info IDoc 3 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 3, IDoc No. 1549822, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Altogether, 0 records were filtered out through selection conditions                      RSQU          037
06:56:32 Synchronized transmission of info IDoc 4 (0 parallel tasks)                                R3           414
06:56:32 IDOC: Info IDoc 4, IDoc No. 1549823, Duration 00:00:00                                     R3           088
06:56:32 IDoc: Start = 04.10.2011 06:56:32, End = 04.10.2011 06:56:32                               R3           089
06:56:32 Job finished                                                                               00           517
Regards
Supraja

Schedule Background Job whenever new message WVINVE

Hi All,
I have following requirment:-
Schedule Background Job with a ABAP program,
whenever new message type WVINVE posted in SAP inbound.
I am confused in "Event" which i select in SM36.
Or, is there any other method to trigger a background report, whenever WVINVE03 IDOC posted in SAP system & create physical Inventory document.
regards
Umesh

For triggereing a background job, when ever a message type WVINVE is posted. You need to create a
Background Job with the the program and mark the Job Event periodic. Secondly you need to trigger that event from the Inbound processing program or Function module which processes the message type using the Function module <b>BP_EVENT_RAISE</b>. so when ever a message type is processed it will trigger the event which inturns trigger the Job.
Hope this will Help.

How to identify what are all the events are created in background jobs?

Hi all,
how to identify what are all the events are created for background jobs. And what events gets triggered for a particular job.
thanxs
haritha

Hi Haritha,
JOB is a program which starts to a determined point of time and executes some standard programs in the system. JOBs can be planed to a determined point of time on the regular basis (every night, for example) or to some discret time moments. So, the JOB can be planed and then will be started automatically without the manual start.
Realtime programs are understood in the most cases as actual program execution which is started by somebody to the actual moment of time.
Typically per JOBs some special processes will be started that should be executed automatically and regularly: for example, IDOC application, some correction reports, statistic updates etc.
Standard jobs are those background jobs that should be run regularly in a production SAP System These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
Use
As of Release 4.6C, the Job Definition transaction ( sm36 ) provides a list of important standard jobs, which you can schedule, monitor, and edit.
Standard jobs are those background jobs that should be run regularly in a production SAP System. These jobs are usually jobs that clean up parts of the system, such as by deleting old spool requests.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw70/helpdata/en/24/b884388b81ea55e10000009b38f842/frameset.htm
About Events:
Events have meaning only in the background processing system. You can use events only to start background jobs.
Triggering an event notifies the background processing system that a named condition has been reached. The background processing system reacts by starting any jobs that were waiting for the event.
Types of Events:
There are two types of events:
1.)System events are defined by SAP. These events are triggered automatically when such system changes as the activation of a new operation mode take place.
2.)User events are events that you define yourself. You must trigger these events yourself from ABAP or from external programs. You could, for example, signal the arrival of external data to be read into the SAP system by using an external program to trigger a background processing event.The event scheduler processes an event if the event is defined in the system.
For example, if a system (System 1) receives an event from another system (System 2), the event scheduler of System 1 processes the event only if it is defined in System 1. That event does not need to be defined in System 2 (the sending system).
You define an event by assigning a name (EVENTID) to it. When defining an event, you do not define the event arguments.
for more information you can go thru the following thread:
http://help.sap.com/saphelp_nw04s/helpdata/en/fa/096e2a543b11d1898e0000e8322d00/frameset.htm
When you schedule the process chain or infopackages the jobs associated with it run in the background mode. In case you want to create a job for a specific activity you can do so in SM36. You would be creating jobs that would get executed in any one of the options:
1. Immediate
2. Date & Time
3. After event.
4. After job.
5. At Operation mode.
In case you want to view the job logs go to sm37.
Also Pls check DB02 for database performance and ST03 for workload .
Analyse u will have an idea ,
*pls assign points,if info is useful**
Regards
CSM reddy
null

Background job requirement in Systems like MDM

Hi All,
We will like to know periodic background job requirements in systems like MDM. May be rough volume of these jobs (defination) will help.
Do these systems have process chains like BI and APO systems.
Also do these systems have some interfaces with ECC / R/3 systems to transfer the data. (for e.g. in APO we have CIF interface)
Thanks a lot for all your help.
Best Regards,
Vithal

Hi Zanwar,
my apologies for wrong answer.
as per my knowledge, i only know these things.
1. Periodic background job requirements in systems like MDM may be.
Ans: - seeing for MDM server heartbeat
        - Import & Syndication server start/stop process
        - MDM server performance
       - maintaning & cleaning log files
etc.
2. Do these systems have some interfaces with ECC / R/3 systems to transfer the data. (for e.g. in APO we have CIF interface)?
Ans: yes, MDM have Generic extractor (mdm_clnt_extr) and MDMGX to extract data from R3 systems.
- also you can use custom scenarios using XI as middleware
like: Proxies, Idocs.
- Abap apis is another method to integrate R3-MDM.
3. Do these systems have process chains like BI and APO systems?
Ans: i think mdm have but nort sure.
BR,
Alok
Edited by: Alok Sharma on Jan 30, 2008 12:35 PM

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.

DEBMDM Idoc in background

Dear All,
I would like to send DEBMDM idoc through Background prg.
i have a custom message type fro DEBMDM and currenly we are sending customer useing MDMC transaction .
we would like to do it automatically through background job,
Do any body have idea how to send custom message type for debmdm through background Job.
Thanks,
Gopan

You can use Change Pointer Concept and use the Programe RBDMIDOC and save a variant with the DEBMDM Message type
and schedule it as a background job

Reg : Background job

Hi Guru's
I am sending IDOC from R/3 System to APO System.when idoc reached APO system.its triggers immediately and creating one file in application server(APO).sometimes this process makes more than 10 to 15 hours so user dont know whether is executing or failed. so i gave one soltion to user that is creating background job while idoc is executing when its idoc is processed then the background job also shows that finished..i dont know how to write this background job code in IDOC function module and also i dont know its possible in IDOC. i dont have knowledge in IDOC..Please helpme on this issue.
anybody helpme on this issue.????
Regards
P.Senthil Kumar

Hi,
You have not to write Back Ground Code in FM of IDOC.
To Process Idoc in Back Ground do following Step
Go to T-CODE We20
Select Partner
Double Click on any IDOC Message type in Outbound Parameter like INVOIC
In Outbound Options Tab, at Output Mode select Collect Idoc Radio Button.
For Inbound parameterDouble Click on any Message type.
Select Trigger by BackGround Program Radio Button
Please use T-code SM36 to schedule program which process Idoc.
The Program used is,
RSEOUT00 : For Processing 30 Status IDocs For outbound Idoc
RBDAPP01 : For Processing 64 Status IDocs For Inbound Idocs
T-code BD87
To Refer more about IDOC,
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE%2CIDOC
https://wiki.sdn.sap.com/wiki/display/ABAP/ALE+IDOCS
Thanks & Regards,
ShreeMohan
Thanks & Regards,
ShreeMohan

Background Job table

Hi All,
I am new to ABAP. as per our client requirement we need to call background job though a abap code.
How can we retrive background jobs? where/in which tabl are names of backghround job saved?

Hi,
please check out the below link it will help you
http://help.sap.com/saphelp_46c/helpdata/en/73/69ef3d55bb11d189680000e829fbbd/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/4a/2d513897110872e10000009b38f889/content.htm
http://www.finance.utoronto.ca/fast/qrg/nav/commonrptfcns/runrptbackgr.htm
the following list is the available system tables
ADCP Person/Address assignment (central address administration)
ADIRACCESS Table to store keys for TADIR objects
ADR2 Telephone numbers (central address admin.)
ADRP Persons (central address administration)
APQD DATA DEFINITION Queue
APQI Queue info definition
D010SINF ABAP- Information about ABAP program source code
E071 Change and Transport System- Object Entries of Requests/Tasks
E07T Change and Transport System- Short Texts for Requests/Tasks
ENLFDIR Additional Attributes for Function Modules
INDX System table INDX
NAST Message Status
STXH STXD SAPscript text file header
T005 Countries
T005S Taxes- Region (Province) Key
T005U Taxes- Region Key- Texts
T006 Units of Measurement
T015M Names of the months
T247 Month name and short text
T777A Building Addresses
TADIR Directory of Repository Objects
TBTCO Job status overview table
TBTCP Batch job step overview
TFDIR Function Module
TFTIT Function Module Short Text
TSP03L Spool- Long device names
TSTC SAP Transaction Codes
TSTCT Transaction Code Texts
TUTYP User Types in Current Price List in SAP System
TUZUS Special versions
TVARV Table of variables in selection criteria
TVDIR View Directory
US930 Data Relevant to Measurement for User Master Record
USR01 User master record (runtime data)
USR02 Logon data
USR04 User master authorizations
USR06 Additional Data per User
USR14 Surchargeable Language Versions per User
USR21 Assign user name address key
ARCH_OBJ Objects for archiving and reorganization
BTCUED Description of user event IDs for background processing
BTXSUPB BSI- Upgrade-Information
CCCFLOW Client Copy Control Flow
DBSTATC DB Optimizer Control (Statistics Creation)
DEVACCESS Table for development users
DEVL OBSOLETE- Do not use (See TCETRAL)
E070 Change and Transport System- Header of Requests/Tasks
E070L CTS- Index for Assigning Numbers to Requests/Tasks
INSTVERS Documentation for installation Status and History
PAT03 Patch Directory
SDBAC DBA Action Table
T100 Messages
TAPLT Program Application Long Texts
TASYS OBSOLETE- Do not use, see TCEDELI
TDEVC Development Classes
TEMSE Temp Sequential table.
TLOCK Change and Transport System- Lock Table
TNAPR Processing programs for output. Can be very handy to find the print program for a SAPScript.
TNAST Printed output control table
TPFET Table of profile parameters
TPFHT Profile header, administration data for profiles in DB
TPROT Table contains all DD tables to be logged
TRBAT Communication Table for Transport Control
TRDIRT Title texts for programs in TRDIR
TRESN Table of Naming Conventions in ABAP Workbench
TRJOB Job ID for Coordinating Batch-ABAP/UNIX for Transports
TSP03C Spool- Device Description Extension
TST03 TemSe data
TSYST OBSOLETE- Do not use (see TCESYST)
TWSYS OBSOLETE- Do not use (See TCETRAL)
USOBT Relation transaction - authorization object
USR03 User address data
USR05 User Master Parameter ID
USR12 User master authorization values
USR40 Table for illegal passwords
USR41 User master- Additional data
UST04 User masters
VARIT Variant texts
VARID Variant directory
D010TAB Table for Use Report---Tables
DD02L SAP tables
DD02T R/3 DD- SAP table texts
DD03L Table Fields
DD03T DD- Texts for fields (language dependent)
EDIDC IDOC Control Records
EDIDOT Short description of IDoc types
EDID2 IDOC segments (version 3.1)
EDID4 IDOC segments (version 4.6)
EDSEA EDI- Table of all segments of current release
VRSX2 Central Table for Version Management (Report Source)
TSE05 Can add parameters to the INSERT COMMAND (IC). Then, when you insert command, your info appears in the editor. Useful for comment blocks, common section of code, etc.
CDPOS Change document items
CDHDR Change document header
T529A governs the foreground sequence of infotypes the system will use to prompt the user during online and batch processing. You will have to code your BDC to follow that sequence of creating infotypes.
T588Z governs the dynamic event processing that will only take place during online user inputs. For BDC's you will have to create separate BDC's to handle any infotypes that are inserted dynamically by this table.
T588M Infotype Screen Control
***********please reward points if the information is helpful to you*************

Sales Order confirmation through standard IDoc in Background

Hi all,
I want to send Order confirmation throough standard or existing IDoc.
Can you please help me the steps to configure the IDoc
and also the standard program to fill the IDoc with the data and send as background job.
It is also the case for
Invoice
and Shipping
Can you please send me the steps to configure and standard program to fill the IDoc with data.
Hope you would respond me ASAP.
Thanks and Regards,
Shalem.

Hi,
After the sales order has been created, an ORDRSP IDoc is automatically created using message control. This IDoc is sent from the vendor system to the retail system, which means that the outbound IDoc can usually be found in the vendor system and the inbound IDoc in the retail system.
SAP menu -> Tools -> Business Communication -> IDoc Basis -> WE02 > Display IDoc.
Before this you need to complete NACE configuration Part.
If you want to send the IDocs automatically while creating sales order, you can configure it using message control. The process code will be SD10, which is for sales order confirmation (called as EDI 855).
Use NACE transaction to create output/message type with program as RSNASTED and form routine as EDI_PROCESSING and configure the condition record for your partner (profile). Also configure the same in your partner profile.
<i>Hope This Info Helps YOU.</i>
Regards,
Raghav

Prozessing of Idocs as background job

Similar Messages

Maybe you are looking for