Process IDocs in Background

Hi,
What is the best possible way to process an IDoc (Message type: ORDERS/ORDCHG) in background in an Interactive report.
Thanks in advance.
Rgds,
AK

Hi AK
Here's the procedure to post IDocs in ALE inbound processing in background.
Inbound IDocs and IDoc packets are first saved in the database. IDoc packets are split into single IDocs beforehand.
The program RBDAPP01 later releases the saved IDocs for processing. Single IDocs can be put into packets and then processed.
Perform the following steps:
1. Set-up background processing (IDoc/ALE area menu):
IDoc Interface/ALE --> Administration --> Runtime Settings --> Partner Profiles (WE20)
Then the required setting is: In the detail screen Inbound Parameters select the option Trigger by background program.
2. Schedule posting (ALE customizing):
Transaction SALE --> Set-Up System Monitoring --> Posting IDocs in Recipient System --> Schedule
You can also process the IDocs manually by passing them to the posting function module. In ALE Administration choose Monitoring --> Status Monitor (BD87), select the IDocs and then select Process.
You should choose background processing, especially if large data volumes are to be distributed. System performance is better.
Packet Processing can be used to process individual inbound IDocs in the background.
Dont forget to reward, if it helps ;>)
Regards,
Rakesh.
Message was edited by: Rakesh

Similar Messages

Processing idoc in background

hi,
i want to process idoc in background means i don't want to use BD20 to process idoc having 51 status.at this time i first use t-code BD20 to process idoc and then i get the data . now i want that whenever idoc comes in folder they automatically processed in background without needing someone.
thanx/regards,
vaneet thakur

Hi,
check this link.
Link:[http://help.sap.com/saphelp_sm32/helpdata/en/5f/45f93b4139b478e10000000a11402f/content.htm]
hope it'll give some idea.
Regards,
Sneha.

Problems with processing outbound IDocs in background processes

Hello everybody,
I have a question for working with ABAP-PSS Ports.
The behvaiour is that I want to send master data, for example customers, to a function module. This function module works like an converter which process and writes the files in the filesystem.
Following situation:
- I have defined a partner System with different message types, for example DEBMAS and everthing what is necessary to replicate data to partner systems.
- I have defined also a Port like ABAP-PPS Port for calling my own function module.
- If I runs the program I process only 50 Idocs per process because otherwise i can happen that there are to many look entries in the system and the job crashs. (For example all customers are around 50000 Idocs).
Now my problem is that the worker for processing idocs starts each process in the foreground and in parallel.
But this is very strange! Because then all dialog processes are reserved and the system will be very slow!
How can I configure the Port or what have I to implement in my fucntion module to start processing in background (this is the very important point) and maybe allow the program only to use one or two process at the same time?
I have found on the function module EDI_DOCUMENT_CLOSE_PROCESS which I the parameter "Background". What thas this mean? I have set B for this but it has no effect!
Regards
Christian

I know that for inbound interface it is possible to define if in foreground or background and if parallel processing is allowed.
Who knows how I can do this also for outbond?

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?

Process Idoc in Batch

Hi all,
I want to process an inbound IDOC in background mode, but the program that generates the IDOC is running in foreground (ie, the FM 'IDOC_INBOUND_SINGLE' is only called in certain cases depending on user input).
There is no schedule or anything of the sort to trigger an IDOC being processed. Any idea how I can accomplish this?

Hi Sandra,
You can change the inbound partner profile of a correspondence message type (t/code WE20) to trigger by background program (under Processing by Function Module area).
Then you can schedule a job to run program <b>RBDAPP01</b> to process the inbound IDocs with status 64.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Timeout when processing IDocs

Hi,
I have a problem when I process IDocs in CRM 5.0 system. The IDocs of BP are sent via middleware into my system. When I use BD87 to select some IDocs, it often to be timeout. And if I use report RBDAPP01 to process IDocs as a background job, it often took long time and not finished.
I have looked at process via SM51, and found the progress seems to stay at program "SAPLBUBA_4" or "SAPLBUD_MEM".
Do anyone know the cause of this problem? And how to solve it?
Thank you very much for your help!
Best regards,
Long

Hi,
Instaed of sending bulk of idocs ,break them and schedule the program RBDAPP01..say there are 2000 idocs to be processed..
For exmaple create a variant of say 1 to 1000 and then schedule the program RBDAPP01 and once again crerate another variant with 1001 TO 2000 and then once again schedule RBDAPP01..Now in this case 2 jobs will shedule with 1000 idocs...
Regards,
Nagaraj

RBDAPP01 is not processing Idoc's

Hi,
We are facing an issue that the RBDAPP01 program scheduled to process inbound Idoc's is not picking Idoc's for posting and running for ever with out processing Idoc's.
Please let me know what could be the reason for this kind of behavior.
Regards,
Cheritha

Hi ,
Check your idoc is in 64 status ? If it in 64 process then process with RBDAPP01 in background or Put that idoc in BD87 and process in foreground.
Thanks,
Asit Purbey

How to find process chain using background job in sm37

How to find process chain using background job in sm37

Better is to select the job.
Select (Define) Step (s) or F6.
Select the line and Menu Goto>Variant.
The variant contains the name of the CHAIN and its VARIANT.
Success
We faced an old job and via job monitoring we were informed about a cancelled job every 'interval'.
We noticed that the related chain was deleted but still the job was scheduled each interval again and was cancelled because an event was missing
We could not find the scheduled job via SM37.
Via view V_OP, view over tbtco abd tbtcp, we find the related entry.
We delete these entries via function BP_JOB_DELETE....
Edited by: Jack Otten on Jul 9, 2010 2:50 PM

Scheduling of process chain with background job

Hello All,
I have scheduled the process chains through background jobs. I have copied the meta chain and created seven background jobs that is from Monday till sunday. The problem is most frequently the job gets cancelled with the message
Process CHAIN, variant PAA1_GS001 is not scheduled waiting for event RSPROCESS 44NRPDWZ7CQUJ92ATDTY6368H.
This is the variant for the next process after the start process. I tried by giving merge active versions, but one day the background job runs fine , but the next day it gets cancelled.
If anyone has faced this issue before kindly let me know.
Regards,
Karthik.

Hi,
It seems to be there may be in probelm in Varients, so create a separate Varient for each PC and then activate the PC and execute.
Thanks
Reddy

Contracts - 'Document still being processed in the background; try again la

Hello,
When trying to make adjustments to multiple contracts we are receiving the error message 'Document is still being processed in the background; try again later.' We have tried again later to no effect.
Ultimately, this means that these contracts (30 altogether) cannot be altered in anyway i.e. held, deleted, released, approved and it means that they just sit there.
This also has implications when raising another contract to replace these contracts. For example if you want to use the same vendor this will cause great confusion for our users when trying to select the correct correct to spend money against when raising purchase orders. Often the result is the user selecting the wrong contract.
Have you any suggestions on why this error message is appearing?
Many Thanks,
Sarah

1465740 - SRM document is stuck in the approval process
Symptom
Workflow hangs.
Workflow gets stuck.
SRM document in status waiting.
Approval process cannot continue.
SRM document frozen in status 'awaiting approval'.
BBP_PD 443 Document is still being processed in the background; Try again later
BBP_ICON_TEXTS 049 No workflow started. Application error occurred
Environment
SAP Supplier Relationship Management
Reproducing the Issue
Create or change a document in SRM.
Cause
*Not possible to identify root cause without further deeper analysis
Resolution
Find the object guid of your SRM document via transaction BBP_PD.
Then display the relevant workflow instance via transaction SWI6 using the following steps:
Select BOR object type.
Enter your object type.
Enter your guid (or document number in the case of shopping cart) in the Key field.
Select variant All Instances.
Select selection period All.
Hit execute.
Click on icon 'Display workflow log'.
Click on icon 'List with technical details'.
Click on icon 'Print Log'.
Record the date and time of the very last step in the workflow log.
Using the date and time of the last workflow step, here are some transactions that can be used to investigate the root cause of the problem.
SM58 - check for stuck remote function calls
ST22 - check for system dumps
SM13 - check for stuck update requests
SM21 - check in the system log for anything unusual
SWUD - run a consistency check on the workflow
Enter the task number and hit enter e.g. 14000044
Choose 'Test Environment' and flag 'Including parts'
Execute
Choose 'Consistency check for components' and flag 'Including subworkflows'
Execute
Red lights indicate an error in the definition.
Header Data
Released on 05.05.2010 09:53:08
Release status Released to Customer
Component SRM-EBP-WFL Workflow
Priority Normal
Category Problem

How to process Idoc status file within Sap?

Hi All,
We would like to process received status file to update the sent IDOC's. Our current setup is that we send/push the Outbound Idoc to external EDI sub system and pull the status file for processed Idoc from external EDI system to our R/3 server.
Sap Documentation explains the scenario, where this process is triggered from external system using startrfc program, whereas our scenario is to trigger the status update process, once the file is pulled to our system from unix using edi_status_incoming function module.
Your anwers are much appreciated.
Kind Regards,
Sandhya

Hi Sandhya,
Once the Idocs are sent to the EDI Subsystem, the SAP will have the status that the Idoc has reached the partner sub system. I hope, the workflow should be able to trigger back the status file to the SAP System after the Idoc is processed at the EDI Subsystem.
Please check with the workflow that is attached.
Else, if this is using the FM or Message Control, then check the configuration under MN04.
I'm also trying to find the solution for the same.
Regards,
-Syed.

What is the Successfull processed IDOC status number?

Hi Experts
What is the Successfull processed IDOC status number?
arjent Please.
Thanks in advance
Sekhar

Hi Chandra,
Below are IDoc Process Codes
For outboud Idocs:
1 IDoc created
2 Error passing data to port
3 Data passed to port OK
4 Error within control information of EDI subsystem
5 Error during translation
6 Translation OK
7 Error during syntax check
8 Syntax check OK
9 Error during interchange handling
10 Interchange handling OK
11 Error during dispatch
12 Dispatch OK
13 Retransmission OK
14 Interchange Acknowledgement positive
15 Interchange Acknowledgement negative
16 Functional Acknowledgement positive
17 Functional Acknowledgement negative
18 Triggering EDI subsystem OK
19 Data transfer for test OK
20 Error triggering EDI subsystem
21 Error passing data for test
22 Dispatch OK, acknowledgement still due
23 Error during retransmission
24 Control information of EDI subsystem OK
25 Processing despite syntax error (outbound)
26 Error during syntax check of IDoc (outbound)
27 Error in dispatch level (ALE service)
28 Not used
29 Error in ALE service
30 IDoc ready for dispatch (ALE service)
31 Error - no further processing
32 IDoc was edited
33 Original of an IDoc which was edited
34 Error in control record of IDoc
35 IDoc reloaded from archive
36 Electronic signature not performed (timeout)
37 IDoc added incorrectly
38 IDoc archived
39 IDoc is in the receiving system (ALE service)
40 Application document not created in receiving system
41 Application document created in receiving system
42 IDoc was created by test transaction
50 IDoc added
For Inound Idocs
51 Error: Application document not posted
52 Application document not fully posted
53 Application document posted
54 Error during formal application check
55 Formal application check OK
56 IDoc with errors added
57 Test IDoc: Error during application check
58 IDoc-Copy from an R/2 connection
59 Not used
60 Error during syntax check of IDoc (inbound)
61 Processing despite syntax error (inbound)
62 IDoc passed to application
63 Error passing IDoc to application
64 IDoc ready to be transferred to application
65 Error in ALE service
66 IDoc is waiting for predecessor IDoc (serialization)
67 Not used
68 Error - no further processing
69 IDoc was edited
70 Original of an IDoc which was edited
71 IDoc reloaded from archive
72 Not used, only R/2
73 IDoc archived
74 IDoc was created by test transaction
Regards,
Satish

Essbase process started in background is going on "In Queue" State

Hello,
I am using 11.1.2.1. Any Essbase process started in background is going on "In Queue" State. And the process never starts.
Any help would be appreciated.

Hi,
Try the following steps..
1. Stop EAS
2. Delete all the contents of WebLogic temp folder
Location: EPM_ORACLE_INSTANCE/../domains/EPMSystem/servers/EssbaseAdminServices0/tmp/ --> delete all the content under this folder
3. Start EAS server
Hope it helps...
KosuruS

Document is still being processed in the background

Hi guys.
I receive this error when wanting to Change a purchase order in SRM. The PO is already in R/3, and the user has tried to make the GR in SRM. This GR then failed in R/3 because of incorrect accounting data, so I changed this in SRM. Then the PO changed to status Awaiting Approval, but we do not use any workflow for approving POs. Plus when trying to change the PO I get the message Document is still being processed in the background; please try again later. Well, this has been there for over a week now, and I have searched both this forum and also SAP Notes, but cannot seem to find anything that helps me.
There are no locked entries in the BBP_WFLOCK table, just as there don't seem to be anything in the RFC queues. I have checked the SC, PO and Confirmation in the BBP_PD, but no news here.
Something that interested me though is that in BBP_PD for the PO it seems that there are 2 active versions...?
Any other idea as to how I can "release" this Purchase order again?
Thanks for info.
DM

Hi,
Let me know the following things.
1. Do you see any approver in the approval preview of the purchase order , you have told that you are not using any workflows , but i wanted to make sure.
2.When do you get the message"document is still being processed in the background" ? is it when you change the purhcase order?
3) please have a look at the workflow log using the transaction 'SWI6', use the object type as bus2200 , use purchase order GUID and then see wether the setreleased has been run for the purchase order.
4) if the setreleased is not done , then you have to run the setreleased method for the purchase order.
award points if usefull
Message was edited by:
khan voyalpad usman

While processing Idoc -error

Hi ,
While processing Idocs we are facing with 2 error can any one help me out.
1.Order 123 does not exist
2.Error in document: BKPFF $ DR0CLNT400
Message no. RW609
Diagnosis
Errors occurred when checking or posting the document
Reference type = BKPFF
Reference key = $
Logical system = DR0CLNT400
You can find the errors in the log
Thanks and Regards
Sri

HI,
Please go to transaction WE02 and look at the IDOC.
The IDOC will have a STATUS section. when you expand it, it will give you a log with error status. Double click to look at the detailed error.
Looking at the error it looks like you are bringing in an IDOC from another SAP system to this SAP system. The order # 123 against which IDOC is for, doesn't seem to exist in the receiving SAP system.
Regards

Process IDocs in Background

Similar Messages

Maybe you are looking for