Idoc is getting processed after 4 hrs?

Dear Gurus,
Idoc creation time and database updation time difference is 4 hrs..
why is it so?
Thanks in advance..

what IDOC is it?

Similar Messages

Article IDoc not getting processed in PI for particle article type

Hello All,
I have an strange behaviour in my system.
i.e 1, we are creating an article IDOC by using BD10 for particulat article type.
2, IDOC created succesfully , then
3, Process the IDOC in BD87 to push the IDOC to PI system .
4, But i could not see the message in PI that too only for one article type.
I'm wondering why this is not getting processed only for one article type and not for others.
we also checked the basic filter for the message type in dist model and even i could not see any condition in PI also,
Is there any thing else i should check? can you please help us on this.
Regards , Sethu.

Hi,
Try to reimport the metadata of IDOC into PI in idx2. Also check the port definition in ECC and whether the segment is released or not. Please go through the below discussions it may help you.
EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
IDoc 0000000000181226 was saved but cannot or should not be sent
Regards,
Priyanka

RSEOUT00 - Idoc not getting processed

Hi All,
I have few idocs in prod.system with status 30 and they are not getting processed using RSEOUT00.
I tried using back ground job / forgrond / BD87 also but they are not getting converted to 03 status.
receiver port is xmlgen.
Any thing like idoc lock ? or something other that is preventing it process ?
Please let me know if anything.

check out the multiple threads in SDN regarding this issue
idoc remains random in status 30
some of the common pointers looks to be locked IDOC (check in SM12), SM58 to see if anything is in the RFC queue (though I doubt that would be the case)..
How are you generating your idoc? standard FM or MASTER_IDOC_DISTRIBUTE?

ALE - Idoc not getting processed automatically, instead going fine in Debug

Hello All,
I have a problem with Inbound idoc processing.
IDoc settings were made 'immediate processing' in WE20, and the process code is set correctly and the attached of Z-Fun. module to process the idocs to process code.
The error in inbound side is as 'Function module not allowed: APPL_IDOC_INPUTI' 51 status. Am sure i have to do some thing with ALE settings.
Can some body help me with correction step or sequence of steps for this ALE process.
Thanks & Regards, Jilan

Hi Jilan,
Plz follow the steps:
ALE Configuration:
     WE30 - IDOC type creation
     WE31 - Create segment
     WE81 - Message type creation
     WE82 - Link IDOC type to Message type
     SE37   - Create Inbound Function Module
     BD51 - Maintain entry for Function Module
     WE57 - Maintain
     BD57 - Link Function Module, IDOC type and Message type
     WE42 Create Inbound Process Code
     BD67 - Link Process code to Function Module
     WE20 - Create Partner Profile
     BD64 - Display Distribution Model
     WE02 - IDoc List, Display all Inbound/Outbound IDocs
     WE14 - Outbound Processing of IDocs
     BD20 - Inbound Processing of IDocs
1st Step:   Create a Segment ( WE31)
         Segment is a structure for passing data in IDoc. It actually contains the IDoc data, just like the DDIC table/structure. Segment is created with all the required fields. Then Save it. But, to actually use this Segment, you have to Release the Segment, otherwise u cant use the Segment, by menu, EDIT--> Set Release.
         Now, if you want to do some change to this Segment, u cant, unless & until u Cancel the Release, by Edit--> Cancel Release.
2nd Step:   Create IDOC Type ( WE30 )
        After creating the Segment, now we have to create the IDoc Type. IDOC Type is like an envelop of a letter, which contains the data inside it, & also some more information like address. IDoc type can be Basic Or Extended.
       Basic IDoc Type: Using some SAP existing IDOC type (ex. MATMAS) or Custom IDOC type.
       Extension IDOC Type: When we need some fields extra to an existing IDOC type, then we can extend that Basic Idoc Type by another Segment. This is called Extended idoc type
3rd Step:   Create Message Type (WE81)
     Message Type is like the Postman for sending the Letter.
4th Step:   Attach Message Type to the IDOC Type (WE82)
5th Step:   Create a Function Module (SE37)
       Write the Processing logic in a Function Module.
6th Step:   Mention the IDOC Type, i.e, 0/1/2 (BD51)
7th Step:   Assign the Message Type, IDOC Type & Function Module (WE57)
8th Step:   Create a Custom Process Code (WE42)
9th Step:   Attach the Function Module to the Process Code (BD67)
10th Step: Execute Inbound IDOC s (WE19)
Example Function Module: IDOC_INPUT_ORDERS (Standard FM to create Sales Order).
reward is useful,
regards,
Tanmay

No Idocs were getting generated after the system Refresh

Hello Experts,
Recently my Sand box system has been refreshed with the Development system. (Its a system refresh and hence all the objects were also copied like Development).
After the refresh, we have performed the below activities --
BDLS to change the logical system
Maintained the LS in WE20
Partner Profiles from WE21 with proper settings with respect to the new logical system name. (Sand box).
RFC to myself source system and to the Flat File.
While executing a test load from Flat File the system is not able to generate any IDOCS in the system and failing with
"No Idocs generated; file system
Diagnosis
No IDocs have been created. With file systems as source systems, the IDocs are created in BI. As this did not happen, it is probable that there was a short dump in BI.
I dont see any short dumps in ST22 for this load and also any logs in SM21.
Any idea why the system is not able to generate IDOCS in the system?
We are planning to connect R/3 sandbox to BI sandbox once the Flat file load is running fine.
Thanks for your answers.
Raman

Hi ,
Hi
BD87 Update Idocs manually.
1. When you look in the Monitor screen for the first time on a day you mostly will see some Loads that have yellow traffic lights. When you click on the lowest line of the Load (with the time of Load start) you will get the next popup screen:
2. Here you can click on the "Yes" button. The Load specification window (right side of the screen) will now be filled with data.
3. You can now start the manual processing of the IDocs. You go to the "Details" tabpage of the right window. You right click on the line with the red traffic light stating "Request IDoc : IDoc ready to be transferred to application" on the "Details" tab page of the Load. In the option menu that appears choose the option "Update manually in OLTP" (click it).
4. You will get to the next screen (which is in fact a transaction in the source system (SAP R/3) where you can update the IDoc that is send by the source system)
5. Now click the "Excecute" button on the left of the screen (or press the F8 button on your keyboard). You will get to the next screen:
6. This states that the IDoc has been passed through to BW. You return to BW by clicking the "Back" button (or pressing the F3 button on your keyboard) twice. After the first time you will see the previous screen and after that the Monitor screen again.
7. You will now see that the Status of the Load has turned to yellow or green. When it is yellow you will have to wait a little time (the execution of the Load in BW is still running) and by clicking "Refresh Details" button on the left upper side of the screen (or pressing the F8 button on your keyboard) you will see the Load turn green.
Regards,
Rahul.

IDoc not getting processed in Real Time job

Hello,
The configurations are done as per the below link to receive iDoc from SAP in BODS.
How to Receive IDOC in BODS from SAP (Outbound to SAP)
An iDoc is sent and Real Time Services on management console shows that request is received successfully. But I cannot see output xml file created. When I checked the real time services and client interfaces, I could see all are in green.
But the real time job status shows its in running state. It has been in running state for 2 days. Trace shows as below. There is no error message.
14.2) 04-24-14 18:47:41 (18417:1140171104) JOB: Optimizing job <JOB_BODS_RT_IDocMatmas01>.
(14.2) 04-24-14 18:47:47 (18417:1140171104) JOB: Job <JOB_BODS_RT_IDocMatmas01> is started.
(14.2) 04-24-14 18:47:47 (18417:1140171104) DATAFLOW: Data flow <DF_RT_IDocMatmas01> is initialized.
(14.2) 04-24-14 18:47:47 (18417:1140171104) DATAFLOW: Data flow <DF_RT_IDocMatmas01> using IN MEMORY Cache.
(14.2) 04-24-14 18:47:48 (18417:1140171104) DATAFLOW: Data flow <ActaDefaultNotificationSender> is initialized.
(14.2) 04-24-14 18:47:49 (18417:1140171104) DATAFLOW: Data flow <ActaDefaultNotificationSender> using IN MEMORY Cache.
Can anyone please let me know if there is anything missing in the configuration? How do I resolve this issue?
DS version: 4.2

Hi,
Try to reimport the metadata of IDOC into PI in idx2. Also check the port definition in ECC and whether the segment is released or not. Please go through the below discussions it may help you.
EDISDEF: Port XXX segment defn E2EDK35 in IDoc type ORDERS05 CIM type
IDoc 0000000000181226 was saved but cannot or should not be sent
Regards,
Priyanka

IDOCS get created After one day?

Hello all,
the outbound idocs are get created after one day delay,
After uploading the materials the idocs have to generated through program RBDMIDOC and need to be posted immediately .
RBDMIDOC-scheduled at 10 mints .
but in our scenario the idocs are generated after one day delay..
what could be the reason?.
it's urgent .
Warm regards
Nandan
Edited by: Nandan ND on Feb 19, 2008 12:47 PM
Edited by: Nandan ND on Feb 19, 2008 1:35 PM
Edited by: Nandan ND on Feb 19, 2008 1:36 PM

Hi,
Check whether program RBDMIDOC is scheduled only once? If it is running only once then you this will happen.
And also schedule the job to execute only after your upload process is over.
Regards,
Ashok

IDOC status 64 not getting processed.

Hi Gurus,
      I have a problem where IDOC's with status 64 are not getting processed via background job. the IDOCs weere getting processed with the background job till today evening, but suddenly no changes were made and the processing of IDOC's with status 64 has stopped and they keep filling up, when i checked the log of the Background job it says finished, and the log has the following information,
17.09.2009 19:05:23 Job started                                                                   00           516          S
17.09.2009 19:05:23 Step 001 started (program RBDAPP01, variant POS_IDOCS, user ID SAPAUDIT)      00           550          S
17.09.2009 19:05:25 No data could be selected.                                                    B1           083          I
17.09.2009 19:05:25 Job finished                                                                  00           517          S
Kindly advise on this.
Regards,
Riaz.

When i process the IDOC's using BD87, they gets processed wiwth out aany issues no dump is displayed, idoc gets a status 53 after processing via BD87.
There is another problem how ever there are other jobs scheduled to run in the background other than this background job which are getting cancelled and have two different error logs for different jobs they are as follows.
1) 18.09.2009 02:00:06 Job started                                             00           516          S
18.09.2009 02:00:06 Logon not possible (error in license check)             00           179          E
18.09.2009 02:00:06 Job cancelled after system exception ERROR_MESSAGE      00           564          A
2) 18.09.2009 00:55:27 Job started                                                          00           516          S
18.09.2009 00:55:27 Step 001 started (program RSCOLL00, variant , user ID JGERARDO)      00           550          S
18.09.2009 00:55:29 Clean_Plan:Gestartet von RSDBPREV                                   DB6PM         000          S
18.09.2009 00:55:29 Clean_Plan:beendet                                                  DB6PM         000          S
18.09.2009 01:00:52 ABAP/4 processor: DBIF_RSQL_SQL_ERROR                                00           671          A
18.09.2009 01:00:52 Job cancelled                                                        00           518          A
This is a production server and the Licence is valid till 31.12.9999, and has no issues with the license.

"disp+work" process in not getting started after kernel upgradation

Hello Experts,
Good day…..,
I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
I have upgraded kernel version from 701 to 741, but the “disp+work” process is not getting started after kernel upgrade.
I have posted “dev_W0” log &
“disp+work” command result obtained in CMD prompt of respective server.
Please help me out in this. Thanks all in advance.
“dev_w0” Log”
trc file: "dev_w0", trc level: 1, release: "741"
* ACTIVE TRACE LEVEL           1
* ACTIVE TRACE COMPONENTS      all, MJ
M sysno      55
M sid        TNG
M systemid   562 (PC with Windows NT)
M relno      7410
M patchlevel 0
M patchno    42
M intno      20020600
M make multithreaded, Unicode, 64 bit, optimized
M profile D:\usr\sap\TNG\SYS\profile\TNG_DVEBMGS55_ABTHMSSB01
M pid        2392
M
M
M Wed Jul 23 02:04:35 2014
M kernel runs with dp version 208000(ext=117000) (@(#) DPLIB-INT-VERSION-208000-UC)
M length of sys_adm_ext is 500 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workp. 0 2392) [dpInit.c 731]
M DpCommonParamInit: rdisp/core_file_size = default --> no change
I MtxInit: 30000 0 0
M
M Wed Jul 23 02:04:36 2014
M DpIPCInit2: read dp-profile-values from sys_adm_ext
M DpShMCreate: alloate/attach shared memory (mode=ATTACH)
M DpShMCreate: sizeof(wp_adm)                         24288    (1104)
M DpShMCreate: sizeof(tm_adm)                          51472080             (256080)
M DpShMCreate: sizeof(ca_adm)                           432000 (72)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/16/7464064/7583152
M DpShMCreate: sizeof(comm_adm)                   7583152                (14904)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm)                      0              (296)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm)                         0              (80)
M DpSockTableSize: max/headSize/ftSize/tableSize=500/16/520064/520080
M DpShMCreate: sizeof(sock_adm)                       520080 (1016)
M DpShMCreate: sizeof(vmc_adm)                       0              (3208)
M DpShMCreate: sizeof(wall_adm)                        (ft=41664/fi=67472/hd=64/rec=192)
M DpShMCreate: sizeof(amc_rec_adm)                              (ft=86464/fi=67472/hd=64/rec=416)
M DpShMCreate: sizeof(websocket_adm)                         (ft=28864/hd=64/rec=272)
M DpShMCreate: sizeof(gw_adm)          64
M DpShMCreate: sizeof(j2ee_adm)       3936
M DpShMCreate: SHM_DP_ADM_KEY                  (addr: 00000000103D0050, size: 60433936
M DpShMCreate: allocated sys_adm at 00000000103D0250
M DpShMCreate: allocated wp_adm_list at 00000000103E20F0
M DpShMCreate: allocated wp_adm at 00000000103E2410
M DpShMCreate: allocated tm_adm_list at 00000000103E84F0
M DpShMCreate: allocated tm_adm at 00000000103E8730
M DpShMCreate: allocated ca_adm at 00000000134FF000
M DpShMCreate: allocated comm_adm at 0000000013568980
M DpShMCreate: system runs without slock table
M DpShMCreate: allocated sock_adm at 0000000013CA4130
M DpShMCreate: allocated vmc_adm_list at 0000000013D232C0
M DpShMCreate: system runs without VMC
M DpShMCreate: allocated gw_adm at 0000000013D23560
M DpShMCreate: allocated j2ee_adm at 0000000013D237A0
M DpShMCreate: allocated ca_info at 0000000013D24900
M DpShMCreate: allocated wall_adm (ft) at 0000000013D24B40
M DpShMCreate: allocated wall_adm (fi) at 0000000013D2F000
M DpShMCreate: allocated wall_adm (head) at 0000000013D3F990
M DpShMCreate: allocated amc_rec_adm (ft) at 0000000013D3FBD0
M DpShMCreate: allocated amc_rec_adm (fi) at 0000000013D54F90
M DpShMCreate: allocated amc_rec_adm (head) at 0000000013D65920
M DpShMCreate: allocated websocket_adm (ft) at 0000000013D65B60
M DpShMCreate: allocated websocket_adm (head) at 0000000013D6CE20
M DpShMCreate: initialized 21 eyes
M DpCommAttachTable: attached comm table (header=0000000013568980/ft=0000000013568990/fi=0000000013C86E10)
M DpSockAttachTable: attached sock table (header=0000000013CA4130/ft=0000000013CA4140)
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X <ES> EsILock: use Semphore 33 for locking
X Using implementation view
X <EsNT> Using memory model view.
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
X
X Wed Jul 23 02:04:37 2014
X mm.dump: set maximum dump mem to 96 MB
M ThStart: taskhandler started
M ThInit: initializing DIA work process W0
M
M Wed Jul 23 02:04:44 2014
M ThInit: running on host ABTHMSSB01
I MtxInit: 0 0 0
M
M Wed Jul 23 02:04:45 2014
M calling db_connect ...
B Loading DB library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' ...
B Library 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' loaded
B Version of 'D:\usr\sap\TNG\DVEBMGS55\exe\dboraslib.dll' is "741.10", patchlevel (0.42)
C Prepending D:\usr\sap\TNG\DVEBMGS55\exe to Path.
C Register application info.
C
C Wed Jul 23 02:04:47 2014
C Oracle client version: 10.2.0.4.0, (dbsl 741 040714, UNICODE[2])
C Detailed Oracle client (patch) info not available.
C *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
[dbsloci.c    2406]
C     Only Secure Connect method possible.
M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 76]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c   2281]
M Wed Jul 23 02:04:48 2014
M
M Info for wp 0
M
M    pid = 2392
M    severity = 0
M    status = 0
M    stat = WP_NEW
M    waiting_for = NO_WAITING
M    workerType = DP_WORKER_DIAWP
M    act_cs_count = 0
M    csTrack = 0
M    csTrackRwExcl = 0
M    csTrackRwShrd = 0
M mode_cleaned_counter = 0
M    control_flag = 0
M    report = > <
M    action = 0
M    tab_name = >                              <
M
M ThIErrHandle: no current incoming request
M
M
M *****************************************************************************
M *
M * LOCATION SAP-Server ABTHMSSB01_TNG_55 on host ABTHMSSB01 (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Wed Jul 23 02:04:48 2014
M * RELEASE 741
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 16797709
M * MODULE D:/depot/bas/741_REL/src/krn/si/th/thxxhead.c
M * LINE 2470
M * COUNTER 1
M *
M *****************************************************************************
M
M PfRejectStatistic: clear statistic record
M PfClearAllRec: clear statistic area
M PfClearAllRec: statRecordAction = STAT_RECORD_ACTION_REJECT
M Entering TH_CALLHOOKS
M ThCallHooks: call hooks for event BEFORE_DUMP
M ThIErrHandle: entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workp. 0 2392) [dpnttool.c 335]
“Desp+Work” Command result:
C:\Users\tngadm>disp+work
disp+work information
kernel release 741
kernel make variant 741_REL
compiled on NT 6.0 6002 x86 MS VC++ 16.00 for NTAMD64
compiled for                  64 BIT
compilation mode UNICODE
compile time Jul 9 2014 16:39:46
update level 0
patch number 42
source id 0.042
RKS compatibility level 0
supported environment
database (SAP, table SVERS) 700
710
701
702
703
                              711
720
730
731
732
738
740
operating system
Windows NT 5.1
Windows NT 5.2
Windows NT 6.0
Windows NT 6.1
Windows NT 6.2
Windows NT 6.3
C:\Users\tng

C *** ERROR => Connect via SAPUSER not supported for kernel >= 740.
[dbsloci.c    2406]
C     Only Secure Connect method possible.
For this issue you need to set up SSFS.
1639578 - SSFS as password storage for primary database connect
I am new to SAP. I installed SAP ECC6 EHP4 with default kernel version 701 and it was working fine.
I have upgraded kernel version from 701 to 741
Are you sure kernel 741 is compatible with an EHP 4 system ?
Read this SAP note
1969546 - Release Roadmap Kernel 740
Regards
RB

IDOCS Error - Not getting processed automatically

Hi All,
We are loading hierarchy for a Product from R/3 system using the standard datasource.
When we execute the info package, IDOCs are not getting processed automatically.
We are facing the below error message.
Error when updating Idocs in Business Information Warehouse
Diagnosis
Errors have been reported in Business Information Warehouse during IDoc update:
No status record was passed to ALE by the applicat
System Response
Some IDocs have error status.
Procedure
Check the IDocs in Business Information Warehouse . You do this using the extraction monitor.
Error handling:
How you resolve the errors depends on the error message you get.
But when we goto BD87 and process the IDOCs manually, these are getting posted and the hierarchy is loading.
Can someone please guide me on what is the issue with the IDOCs and how to make them to post automatically.
Thanks in Advance
Regards,
Sachin

Hi,
This will happen due to Non-updated IDOCu2019s in the Source system i.e., occurs whenever LUWu2019s are not transferred from the source system to the destination system. If you look at RSMO of the status tab, the error message would appear like u201CtRFC Error in Source Systemu201D or u201CtRFC Error in Data Warehouseu201D or simply u201CtRFC Erroru201D depending on the system from where data is being extracted. Sometimes IDOC are also stuck on R/3 side as there were no processors available to process them. The solution for this Execute LUWu2019s manually. Go to the menu Environment -> Transact. RFC -> In the Source System from RSMO which will asks to login into the source system. The u201CStatus Textu201D for stucked LUWu2019s may be Transaction Recorded or Transaction waiting. Once you encounter this type of status Execute LUWu2019s manually using u201CF6u201D or Editexecute LUWu2019s(F6).Just keep on refreshing until you get the status u201CTransaction is executingu201D in the Production system. We can even see the stuck IDOCu2019c in Transaction BD87 also.Now the data will be pulled into the BW.
Hope it helps a lot.
Thanks and Regards,
Kamesham

IDOC getting processed in reverse order

Hello All,
In our system whenever changes are made in the customer master an IDOC is generated.
In my scenario i have created a ship to party for which an IDOC got generated as say 10.
Now i add this ship to the sold to party due to which another IDOC got generated Say 20.
Now in the partner profile settings we ahve the customization setting to process the IDOC immedialtely.
So on saving a customer master automatically a IDOC with status '03' got generated.
At night program RBMOIND is executed to process the IDOC in status 03 to send to the subsystem and change the status to 12.
In this program data is retreived from the table EDIDS for the IDOC with status '03'.
We are selecting the field TID from the table EDIDS.
And then this field is split in the fields of structure arfctid.
Now a sort is done on the retrieved data.
In our scernario the value that got updated in TID field for the IDOC 20 is smaller as compared to IDOC 10.
So due to which the IDOC 20 got processed earlier than IDOC 10.
Can anybody please let me now why this particular problem is occuring.
At the same time can anybody tell me how the entry in the field TID of table EDIDS got updated.Is there any logic in program RSEOUT00 that change the status of IDOC from 30 to 03 written based on which it gets updated.
Thanks,
Mohit

Hello
Can anybody provide any input on this....
Mohit

XI getting slow after process very large message.

Hi All,
I had load data more than 50 MB after that I cannot access any function from browser(RWB,message monitoring,..) but in ABAP side that still work fine. I guess that j2ee engine still process the message that is a reason. So how I can stop the process when I load the the large files. I already try delete queue,delete workitem from SWWL,cancel the message. But nothing happen XI still very slow.
Do I have to only start/stop J2EE engine?
Could you please to advice?
Thanks
Park

HI Park Saeiam ,
in adition to Marcos
If the "browser" functions are not working it is possible that the java part of the XI just crashed and you have to restart the J2EE engine. your message may show error HTTP STATUS CODE 401 authorization error
this error generally occurs when java part of the XI crashes and server is unable to recognise your browser and your credentials.
In that case you need to restart J2EE engine and also you need to manually restart all asynchronous messages which will come in error due to restarting of J2EE engine.
I advise you not to create such huge messages.
also you may try to send this kind of huge message through IDOC package
IDocs are normally sent in packages between systems. You configure this within the IDoc configura-tion partner profile by specifying processing mode Collect IDocs and transfer. IDocs are then proc-essed by report RSEOUT00 in the sender system. During inbound processing in the IDoc adapter of the Integration Server, this IDoc package is split up into single XI messages. Therefore, an IDoc pack-age cannot be processed as one unit within XI. This also has an impact on performance.
In SP11, a solution will be available for IDoc adapter outbound processing to collect IDoc-XML mes-sages and transfer them as an IDoc package, as in the traditional IDoc world.
The IDoc adapter is designed to be able to process IDoc-XML structures that represent IDoc pack-ages.
for more help you can refer SAP XI TUNING GUIDE
Thanks
sandeep sharma
PS: if helpful Reward points

Processing large volume of idocs using BPM Processing

Hi,
I have a scenario in which SAP R/3 sends large volume say 30,000 DEBMAS Idocs to XI. XI then sends data to 3 legacy systems using jdbc adapter.
I created a BPM Process which waits for 4 hrs to collect all the idocs. This is what my BPM does:
1. Wait for 4 hrs Collect the idocs
2. For every idoc do a IDOC->JDBC Message transformation.
3. Append to a Big List
4. Loop at the Big list from step 4 and in the loop for
5. Start counter from 0 and increment. Append to a Small List.
6. if counter reaches 100 then send a Batch JDBC Message in send step.
7. Reset counter after every send.
8. Process remaining list i.e if there was an odd count of say 5300 idoc then the remaining 53 idocs will be sent in anther block.
After sending 5000 idocs to above BPM following problems are there:
1. I cannot read the workflow log as system does not respond.
2. In the For Each loop which loops through the big list of say 5000 idocs only first pass of 100 was processed after that the workflow item is not moving ahead. It remains in the status as "STARTED" but I do not see further processing.
Please tell me why certain Work Items are stuck is it becuase I have reached upper limit and is this the right approach? The Main BPM Process is also hanging from last 2 days.
I have concerns about using BPM for processing such high volume of idocs in production. Please advice and thanks in advance.
Regards
Ashish

Hi Ashish,
Please read SAPs Checklist for proper usage of BPMs: http://help.sap.com/saphelp_nw04/helpdata/en/43/d92e428819da2ce10000000a1550b0/content.htm
One point i'm wondering about is why do you send the IDocs out of R/3 one by one and don't use packaging there? From a performance stand point this is much better than a bpm.
The SAP Checklist states the following:
<i>"No Replacement for Mass Interfaces
Check whether it would not be better to execute particular processing steps, for example, collecting messages, on the sender or receiver system.
If you only want to collect the messages from one business system to forward them together to a second business system, you should do so by using a mass interface and not an integration process.
If you want to split a message up into lots of individual messages, also use a mass interface instead of an integration process. A mass interface requires only a fraction of the back-end system and Integration-Server resources that an integration process would require to carry out the same task. "</i>
Also you might want to have a look at the IDoc packaging capabilities within XI (available since SP14 i believe): http://help.sap.com/saphelp_nw04/helpdata/en/7a/00143f011f4b2ee10000000a114084/content.htm
And here is Sravyas good blog about this topic: /people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
If for whatever reason you can't or don't want to use the IDoc packets from R/3 or XI there are other points on which you can focus for optimizing your process:
In the section "Using the Integration Server Efficiently" there is an overview on which steps are costly and which steps are not so costly in their resource consumption. Mappings are one of the steps that tend to consume a lot of resources and unless it is a multi mapping that can not be executed outside a BPM there is always the option to do the mapping in the interface determination either before or after the BPM. So i would sugges if your step 2 is not a multi mapping you should try to execute it before entering the BPM and just handle the JDBC Messages in the BPM.
Wait steps are also costly steps, so reducing the time in your wait step could potentially lead to better performance. Or if possible you could omitt the wait step and just create a process that waits for 100 messages and then processes them.
Regards
Christine

Inbound IDocs will only process immediately

Hello. I have been having an issue with our inbound INVOIC02 IDocs coming from our EDI server. We are processing a high number of invoices and I wanted to change the processing from immediate to collective. The immediate processing is causing a strain on our EDI server. I would like the IDocs to come into the SAP system, but stay in a status 64 until a background job runs to process them. I changed the partner profile for the vendor from Trigger immediately to Trigger by background program. For some reason, the IDocs are still processing immediately.
Here are some of my settings:
EDI side Function Module: IDOC_INBOUND_ASYNCHRONOUS
SAP side Function Module: IDOC_INPUT_INVOIC_MRM
Partner profile setup:
Partner no: (vendor #)
Partn. type: LI (vendor)
Message type: INVOIC
Process code: INVL
Processing by function module: Trigger by background program.
Please let me know if you have any recommendations as to how I can get these IDocs to process from a background program instead of immediately. Am I missing another setting for this?
Thanks,
Lisa

Hi Klaus,
form the mentioned options, I would give enqueue / dequeue a second try.
I would use customer (/sender) as key field for your locking object.
If you try to set the lock right in the beginning of your FM, whole customer should be locked for processing. Second test is of course, if already a sales order exists.
Maybe here the problem occurs: when you have some parts in update task, select for sales order is not successful for some (micro-)seconds.
Solution for this part: use synchronic booking / commit work and wait. Maybe make a test with a select for VBAK in the end of your FM to test existence -> if not successfull, you know you identified your problem.
If this is your problem, you should make a new enqueue after commit (because it will be deleted by commit) and wait until DB gives you new VBAK entry.
I would start with a test, why all this different locking options don't work (instead of looking for a different locking option): make a select after your sales order creation. If this is not successfull, then here is your starting point.
Regards,
Christian

EREC: Multipal IDOC are getting created in receiver system for one IDOC

Hello Experts,
I ran in to one wearied issue in IDOC creation in Receiver system. I am running PFAL in sender system for only Person but 10 IDOC are getting created in receiver system. I don't know why is this happening.
This issue started popping up after we ran RBDAPP01-Inbound Processing of IDocs Ready for Transfer. We ran this to change IDOC to 53 status. Now I don't know what went wrong but Perner distribution is behaving
Appreciate your help.
Regards,
Krishna Bidwai
Losangeles USA.
818 527 0204.

Yes, employee is getting created after adding 0003 into the filter, but can u please answer my another question, i.e. PERNR in sender and receiver system should be same.
So in Receiver system (ECC) do i need to maintain external number range for PERNR?
Thanks

Idoc is getting processed after 4 hrs?

Similar Messages

Maybe you are looking for