IDoc processing issue

Hello,
I have a customer defined idoc, when it comes into the inbound queue it get's status 64 - "IDoc ready to be transferred to application", and a job is generated for the processing instead of just immidiate processing.
It's important to mention that the partner profile configuration is set to immidiate processing.
Why does this happen and how do I change this situation ?
Thanks,
Elad.

Hi,
As you have mentioned that you are using custom defined iDoc, you might be using a custom defined BAPI to receive the data from the iDoc.
As you have said that the status is 64, your iDoc has entered the system & it has failed only when the data being sent to the application.
kindly, check if the custom defined BAPI or RFC is working fine & whether it updates the status record or not? because you custom BAPI will be receiving the data from the iDoc.
Also, test the scenario using the transaction WE19.
or else you can use manual processing of iDoc using T.code - BD87.
kind regards,
Thangesh

Similar Messages

Inbound Idoc processing issues - Partner Profiles - error status 56

Hello All,
I'm having a little difficulty posting an idoc coming from MDM. It's a CREMDM04 xml coming from an MDM system. It is getting mapped through PI and is being split into ADRMAS02 and CREMAS04 Idocs. The message is being passed through XI and being posted to the ECC system, but certain fields in the EDI_DC40 header table are not being populated correctly (i believe). I'm using nothing but standard mapping/material from the SAP Business Content for XI. After looking through the standard XSLTs i cannot find the field-to-field mapping where the fields below are being populated.
The RCVPOR value (SAP[SID]) is correct when i view it in SOAP Header, but does not appear in the remote system under the receiver port for the inbound idoc.
The RCVPRN value ([String Value]) is incorrect in the SOAP Header and does appear in the remote system under the receiver partner number for the inbound idoc. How is the RCVPRN value being populated?
SOAP Header in IDocOutbound tag
<SAP:RCVPOR>SAP[SID]</SAP:RCVPOR>
<SAP:RCVPRN>[String Value]</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
I've been trying to trace down the string value for the RCVPRN, but i cannot find it anywhere. Perhaps i'm just overlooking it?
When i set the proper values (port = SAP<SIDofECC> and partner number = <LSnameof ECC>) using WE19 in the remote system then the partner profile is found and i'm left with different error to please specify an address group.
Any help is very much appreciated! :-D

Hi Jason ,
Just check out if you have done the following steps most of us make minor mistake here ....... I think this would solve your problem
To Configure the IDOC SCENARIOS ,PROCEED AS FOLLOWS
STEP 1:ALE SETTINGS TO POST IDOC INTO SAP R/3
We need to do the following settings in XI
1) Create an RFC Destination to the Receiving System in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both should be succesful
2) Create Port Using Transaction Code IDX1
a) Select Create New button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client
d) Enter the RFC Destination created in XI towards R/3
e) Save
3) Load Meta Data for IDOC Using transaction Using Transaction (IDX2)
a) Create new
b) IDOC Message Type
c) Enter port created in IDX1
SETTINGS IN SAP R/3
We need to do the following settings in R/3
Logon to Sap R/3 System
1) Create an RFC Destination to XI in transaction code (SM59)
a) Choose create
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#
e) Enter the Gateway host as same details above SID/URL
f) Gateway service is 3300+system number#
g) In the Logon /Security tab, enter the client, user & Password details of Destination system
h) Test the connection and remote logon.Both must be succesful
2) Create communication Port for Idoc processing Using Transaction(We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile with Inbound Parameters (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang
Then Save
e) Select Partner no. and LS which were create above
f) Now we have to give some Inbound Parameters.So click on ADD TO Create Inbound Parameter
g) Select Message type
h) Double click on Message Type and Then Enter the details for Message Type and Process Code.
I) save
4) In Transaction SALE, Create Logical System
a). Go to Basic Settings-> First Define logical systems
and then assign logical systems
b) Double click on Define the logical systems
c) Give data for your Logicaal System and Name
d) Now click on Save.Here one window may appear just click on Continue.Now the Logical System name is ready
e) Assign the logical system name to the client
do let me know if it helped
Edited by: Tom Jose on Feb 21, 2008 9:04 AM

Idoc processing issues

Hi,
can anyone please thorw some ligh on issues faced while processing IDOC either by edi or ale, specially in SD and MM?
Thanks
Rahul

No, I am not facing any issues. What I wish to know is what type of errors/issues do we get once start processing with IDOC.
Regards
Rahul

Desadv idoc processing issue

Hi All,
We are facing issue, when vendor send a two desadv idoc for packing delivery.
First idoc correctly pack the delivery and change the packing status to completely packed.
Processing second Idoc get fails but create a dummy handling unit. It delete one handling unit from the handling unit table VEKP but the trace remains in document flow table VBFA.
This does not happen in all the cases and we are not able to reproduce in Quality system to debug.
Does anybody faced the same issue earlier, and what could be the possible root cause and solution for this.
Please help.
Thanks in Advance
Ankit Gupta

Hi,
As you have mentioned that you are using custom defined iDoc, you might be using a custom defined BAPI to receive the data from the iDoc.
As you have said that the status is 64, your iDoc has entered the system & it has failed only when the data being sent to the application.
kindly, check if the custom defined BAPI or RFC is working fine & whether it updates the status record or not? because you custom BAPI will be receiving the data from the iDoc.
Also, test the scenario using the transaction WE19.
or else you can use manual processing of iDoc using T.code - BD87.
kind regards,
Thangesh

Test tool for IDOC processing issue

Hi
I am doing a IDOC to File Scenario
Please clarify me
The RFC destination and Port which I have created in ECC I am getting the same in the "Edit Control Record Fields Receiver Tab"
But
The RFC destination and Port I have created in XI is not appearing in the "Edit Control Record Fields Sender Tab" (when I pressF4)
where I should have to check for this errors.
Please check this link
http://www.flickr.com/photos/33169400@N05/3097589223/
thanks
manian

Thanks Creasy for your reply
Actually I am following the below link.
Pls refer Step4 Page 6. He has selected tRFC
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/soa-middleware/soa-management/exchange-infrastructure/a%20step-by-step%20guide%20on%20idoc-to-file%20using%20business%20service%20in%20the%20exchange%20infrastructure%20integration%20directory.pdf
thanks
manian

ORDERS05 (CRM) IDOC processing issues when blocking items on the order

We're successfully loading Sales orders from IDOC type ORDERS05. There are certain checks carried out against a customer contract reference (if supplied) which could require the item in question to be blocked/rejected. I can achieve this okay, but when an item is blocked the Qty against the item is Zeroised, and I notice that the schedule line for the item also has a Zero qty, depsite a schedule line segment appearing on the IDOC with a Qty. If I don't block the item, by removing the checking code, then the qty against the item shows exactly as identified in the schedule (E1EDP05) segment.
Has anyone else had this problem and if so how did you get around it.
I've tried duplicating the schedule for the item, thinking that just the first schedule record is zeroised, but it would seem that all scheuled lines are zeroised if the item is block, although that's not what happens if you enter an order manually.
Regards

Tx: CRMXIF_C1
Set Download to Full

MIRO / F-53 in IDOC process

we have a requirement where in we need to post invoice using idoc_input_invoic_mrm FM (coming as INVOIC02 IDoc) and once posted successfully, immediately clear the document using F-53..
What is the best approach to do this?
1) clone IDOC FM and call BAPI to post F-53? Do we need to issue COmmit work before F-53 to ensure that invoice posting is commited?
Or this is not feasible?

Generally inbound IDocs handler FM is called by number of ALE layer FMs which manage also commit to data base.
The call stack for immediate IDoc processing:
- program RBDAPP01
- FM APPLICATION_IDOC_POST_IMMEDIAT
- IDOC_START_INBOUND
- IDOC_INPUT
-- form IDOCS_PROCESS (here customizing is resolved and actual IDoc handler FM is dynamically called)
--- FM TRANSACTION_END with actual COMMIT WORK
This is an example which shows that you have to do your own commit after calling IDOC_INPUT_INVOIC_MRM and before document clearing. In addition all "create" routines inside IDOC_INPUT_INVOIC_MRM are called with addition ON COMMIT - so actual commit is out of control of IDOC_INPUT_INVOIC_MRM.
Regards,
Maxim.

Strange result of IDoc processing in the LSMW

Hi
I am using MATMAS_MASS_BAPI IDoc in the LSMW to transfer material master data into client's SAP system. After IDoc processing I got green message with text that application document was successfully processed (IDoc
status = 53). But I can't view created materials using MM03 transaction. Then, records number in the MARA table before and after launching of LSMW is equal. What may be a reason of this situation? How to solve this problem?
Edited by: Marat on Nov 4, 2008 5:24 PM

Hi there
take a look at the Idoc overview, there should be a t100 message in there if there is a data issue with the idoc BAPI load. However this could be something inconclusive such as 'Inconsistent characteristics' or suchlike. In which case you'll have to check the data and that it matches the requirement for the object

IDoc Processing in SAP

Hi Team,
I have question about SAP Idoc processing ,
1) How does SAP process Idocs when it gets around 20 Idocs all in a fraction of secodes for same Idoc/process code and message type . Will SAP process them one by one , or it will process them all together in parallel processing. Please help me out with this.
2) We have SAP 3.1 released used for creating delivery when an Inbound Idoc get in to SAP. Most of the time we see Idocs creating delivery but some time Idocs does not create delivery in production, we never had this issue in quality. What can be probale cause of this isse?
3) We are facing a strange problem , We have one Inbound Idoc which perform following activity :
1.       Change delivery (Already created Delivery )
2.       MB1C (add Inventory )
3.       Picking
4.       PGI
In the above flow next step will be executed only when preceding steps is successful .Every process is doing itu2019s job in Test /Quality /Production system as expected . But in production some time we are getting some problem while performing Change delivery / Picking . I would like to know from you people have you ever came across such scenario or you have something to add to the process then please share the approach to minimizes the cause.
Please share your views.
Thanks,
Raj

Hi,
The no of IDocs processed at a time is based on the Packet Size that is specified in the configuration of the Partner Profile(WE20). Likewise the specification of the Output Mode is given as either Transfer IDocs Immediately or Collect IDocs in which case the IDoc would go to 30 status and it would have to be processed using RSEOUT00.
Thanks
Krithika

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 serilization issue

Hi Guys,
I have a issue that Incoming IDOCS process out of order after XI outage. So for that I can searilize them. But with that, if error occurs with 1 idoc, the subsequent idocs will not processed, until the failed one is resolved.
If an IDOC was in error couldn't we continue to process the remaining one's in order? Is there any way around?
Thanks,
Vineet

Hi Vineet,
In fact, this is why you serialize IDocs: to have them processed in a specific order, and only process further ones if preceding ones are all processed successfully. So basically they should be processed in receiver system in the same order they left sender system. If this is not what you require, simply turn off the serialization and you'll be fine
Hope this helps,
Greg

Tax Segments in IDOC Processing

Hello,
For intercompany postings of the Sales and corresponding Purchsing invoices we have set up the IDOC process.
In this porcess, once we post the Billing Document then an IDOC posts the corresponding Purchasing Invoice with MIRO.
We have also set up the OBCD customizing for the Input and Output Tax Code conversion.
But because of the Tax conversion issues we face as the PO has different tax code than maintained in the OBCD, we have filtered the Tax Segments E1EDK04 and E1EDP04 with customizing with BD56 and removed all the entries for the specific country eg. Austria.
Now when we process the Billing Document with zero percent Output Tax Rate then the corresponding Purchasing Invoice is created successfully with the IDOC. But when we use a different Output Tax Rate other than zero, then the IDOC gets the error status because of Balance not being zero and the difference amount is equal to the Tax amount.
Is this because of we have filtered the Tax Segements from the IDOCS or the standard IDOC processing program needs to have these segments? Can anybody please help on this issue?
Thanks & Regards,
Vikrant Patil

HI goutham,
I think that process is filtering the segments by manual.
But I need at run time for ex:
Open BD10àpass any material.
WE05à take that idoc number.
We19à Run that idoc number.
So here automatically it need to show only one segment. It shouldnt show more than 1 segments.

Using ABAP memory during IDOC processing

What are implications , issues of using ABAP memory in IDOC processing i.e. let say in inbound FM , I create implicit enhancement and I submit a report and return and pass data to this report via abap memory. What are implications ? Is it recommended to use this approach since many number of IDOCs are hitting the system and orders are getting posted.
Please suggest . Thanks in advance.

Hello Jürgen,
Thanks a lot for this OSS Note. So it seems the issue is some kind of a program error that requires source code correction. I am in process of getting this note applied in our SAP environment. Hopefully, it solves my problem. I will definitely keep you posted.
Thanks again for your quick help.
Regards,
EssKay

Messages from IDoc processing can be found in application log

We are using the IDOC_INPUT_INVOIC_MRM Function Module to post Inbound Vendor EDI Invoices. During testing, we sometimes see the error "Messages from IDoc processing can be found in application log". We then have to check transaction SLG1 to ascertain the 'real' issue, e.g. "No GR documents found". In a Production environment however, this will be very inconvenient. Our business users process their own iDoc errors according to the iDoc Status, so to have to call up another transaction, and select the correct Application Log to find the true error, is not a process I would feel comfortable with for our users.
My question is, can we configure/determine which messages are passed to the iDoc Status, or redirect Application Log messages ? Might a Z version of FM IDOC_INPUT_INVOIC_MRM be the way forward ?
Many thanks,
Paul.

Hi,
Just monitor your error idocs in WE20 transaction. Give idoc number here then execute, you can see the all three records(control, data, status). Click on status record node then double click
on status number(e.g 51), it will take you to another screen there you click on "application log" button on application toolbar. This is the standard way finding the application log of an idoc, even i am finding the application log on production server like this.
Thanks,
Asit Purbey.

IDOC processing speed

Dear All
Anyone have any idea how we can improve IDOC processing speed
And what are the factor that have affect IDOC processing speed
Thanks & Regards
Amit Shivhare

Hi,
1. data which is posted thru idoc
finally goes thru some standard bapi,
which ultimately posts the data.
2. bapis are standard sap code,
which do a lot of vlaidations
before putting data into tables.
3. Hence, i don't think,
we can much upon their improvement !
what are the factor that have affect IDOC processing speed?
Re: Issue of grouping IDOC segments in huge loads
Idoc Segment limit ?
It is the standard program flow of transaction WE02 which checks the number of segments.if the count is more than 1000,it creates a another group and displays it for the sake of readability.
Anyway it does not affect the inbound processing of the IDOC.
<b>Reward points</b>
Regards

IDoc processing issue

Similar Messages

Maybe you are looking for