Idoc not getiing processed

Hi,
While posting the PO from MM to SRM the following error message is coming and the idoc is not geting posted.
Error during syntax check of IDoc (outbound)
Please help in this regard.
Regards,
Manu

Hi,
Please go through below link
It is having step by step
which step u missed will be easily find out
http://searchsap.techtarget.com/tip/0,289483,sid21_gci1268508,00.html
Rewards welcome
Thanks & Regards
Swathi

Similar Messages

Idoc WPUWBW: Status 51 - IDoc not fully processed

Hi All!
Hi All!
This is regarding Goods Moment.
In Quality, Idoc is successfully generated at POSDM system and also in ECC system.
In Production, Idoc is successfully generated at POSDM, but in ECC it is failed (Idoc WPUWBW: Status 51-IDoc not fully processed).
So, at WPER it is showing as In deficit of stock. But stock is available.
Kindly suggest me how to close this issue.
Note: PFA Below. Its the screenshot of the error at WPER.
With Regards,
Yarnagula Sudhir.

Dear Venu
Difficult to answer with this limited information. If you share some more info will be easier to help
regards
Manish

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

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

Error:IDoc cannot be processed: Qualifier not supported.

Hi experts,
                         I got this error when executing the idoc
message type: dirdeb
basic type : pexr2003
error:Error during creation of internal payment order.
IDoc cannot be processed: Qualifier not supported.
Thanks
Saravanaperumal N

Hello,
001     Customer Purchase Order
002     Vendor Order
003     Customer Inquiry
004     Vendor Quotation
005     Customer Contract Number
006     Vendor Contract Number
007     Collective Number for Quotations
008     Last Purchase Order Number (SPEC2000 Acknowl.)
009     Invoice Number
010     Internal Number (Document)
011     Referenced Document Number
012     Delivery Note Number
013     Internal PO Number
014     Accounting Document
015     Billing Document Number of Invoicing Party
016     Number of Preceding Document
017     Assignment Number
018     Customer Order Number
019     ISR Number
020     Invoice List Number
021     ID for Cost Assignment
022     Payment Document Number
023     Banker's Acceptance
024     Matured Certificate of Deposit (CD)
025     Loan
026     Check Number
027     Foreign Exchange Contract Number
028     Credit Memo
029     Payment Advice Note Number
030     Original Purchase Order Number (ALE)
031     Return Leg Number
032     Reference Bank
033     Third-Party Reference Number
034     Reference Number of Beneficiary's Bank
035     Message Reference
036     Credit Card Number
037     Statement Number
038     Account Statement No. (Deposit No.)
039     Account Statement No. (Deposit Seq. No)
040     Payee Code
041     MICR Line
042     Imported Line
043     Vendor Contract Number
044     Ship-To Party's PO Order
045     Cost Center
046     Profitability Segment No.
047     Work Breakdown Structure Object
048     Profit Center
049     Business Area
050     Delivery Order
051     Delivery Order Route Number
052     Sequence Number
053     Scheduling Agreement Number
054     External Transaction
055     Promotion Number
056     Customer Quotation Number
057     Customer Buying Group
058     Customer Contract Number
059     Check Number from Check Register
060     JIT Call Number
061     Internal Delivery Note Number
062     Customer PO no. for consignment issue by ext. service agent
063     External Delivery Note Number
064     Goods Receipt/Issue Slip Number
065     Repetitive Wire Nummer
066     External Order Number
067     Quality Notification Number
068     External Inquiry Number
069     Business Partner Reference Key
070     Reference Text for Settled Items
071     Customer ID no.
072     Agreement Number
073     Credit Advice Number
074     Transfer Number
075     Check Number
076     Credit Posting Number
077     Transfer number (just transferred)
078     Delivering Profit Center
079     Batch Number
080     Certificate Profile
081     Collective Daily Delivery Note
082     Summarized JIT call
083     External Delivering Plant
084     Tax Number Tax Office §14
085     KANBAN ID
086     Kanban Control Cycle
087     Reference Document Number Billing Doc.
101     Resale Invoice No.
102     Resale Ship and Debit Agreement No.
103     Customer Claim Reference Number
104     Design Registration Number
105     TPOP Order Number
106     TPOP Reference Order Number
111     Partner Business Area
APY     Approval Year of Official Document Numbers
APN     Registration Number of Official Document Numbers
SNC     Serial Number of Statement
These are all the Value range for qualifier, use which one suits your requirement
Regards,
Abhishek

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 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.

IDoc not received in MII

Hi All,
I am using SAP MII 12.1.5 Build 87.
I am facing problem with iDoc Listner we have configured iDoc Listner properly in SAP ERP, SAP NW and in SAP MII.
We are able to send iDoc from SAP but we are not able to receive same in MII.
Port and iDoc Server is giving status connected previously it was working fine in SAP MII 12.1.5 Build 83.
Following are the log details for SAP MII Logger as well as SAP NW Log.
SAP NW Log:
Error processing JRA IDOC message
SAP MII Log:
Error processing JRA IDOC message
Error processing JRA IDOC message [server=xxx, client=xxx]
[EXCEPTION]
java.lang.NullPointerException
at com.sap.xmii.ejb.JRAListenerBean.onMessage(JRAListenerBean.java:130)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sap.engine.services.ejb3.runtime.impl.RequestInvocationContext.proceedFinal(RequestInvocationContext.java:46)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:166)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatesTransition.invoke(Interceptors_StatesTransition.java:19)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Resource.invoke(Interceptors_Resource.java:71)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_MessageListenerType.invoke(Interceptors_MessageListenerType.java:110)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:189)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_StatelessInstanceGetter.invoke(Interceptors_StatelessInstanceGetter.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_SecurityCheck.invoke(Interceptors_SecurityCheck.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_ExceptionTracer.invoke(Interceptors_ExceptionTracer.java:16)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.Interceptors_Lock.invoke(Interceptors_Lock.java:21)
at com.sap.engine.services.ejb3.runtime.impl.AbstractInvocationContext.proceed(AbstractInvocationContext.java:177)
at com.sap.engine.services.ejb3.runtime.impl.DefaultInvocationChainsManager.startChain(DefaultInvocationChainsManager.java:133)
at com.sap.engine.services.ejb3.runtime.impl.DefaultEJBProxyInvocationHandler.invoke(DefaultEJBProxyInvocationHandler.java:164)
at com.sap.engine.services.ejb3.runtime.impl.MDBProxyInvocationHandler.invoke(MDBProxyInvocationHandler.java:77)
at $Proxy943.onMessage(Unknown Source)
at com.sap.mw.jco.jra.idoc.JRAIDocExtension$IDocMessageHandler.onMessage(JRAIDocExtension.java:72)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendDirectToMdb(JRA.java:6641)
at com.sap.mw.jco.jra.JRA$ReaderThread.sendAsynchRequest(JRA.java:6601)
at com.sap.mw.jco.jra.JRA$ReaderThread.handleRequest(JRA.java:6771)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:989)
at com.sap.conn.jco.rt.DefaultServerWorker$RequestDispatcher.handleRequest(DefaultServerWorker.java:967)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatchRequest(DefaultServerWorker.java:142)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.dispatchRequest(MiddlewareJavaRfc.java:2927)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.executePlayback(MiddlewareJavaRfc.java:2659)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.playbackTRfc(MiddlewareJavaRfc.java:2478)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.handletRfcRequest(MiddlewareJavaRfc.java:2362)
at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcServer.listen(MiddlewareJavaRfc.java:2207)
at com.sap.conn.jco.rt.DefaultServerWorker.dispatch(DefaultServerWorker.java:259)
at com.sap.conn.jco.rt.DefaultServerWorker.loop(DefaultServerWorker.java:322)
at com.sap.conn.jco.rt.DefaultServerWorker.run(DefaultServerWorker.java:220)
at com.sap.mw.jco.jra.JRA$ReaderThread.run(JRA.java:7260)
at com.sap.engine.services.connector.jca15.work.TaskImpl.run(TaskImpl.java:255)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:115)
at com.sap.engine.core.thread.execution.Executable.run(Executable.java:96)
at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:314)
Please help me out on this issue.
Regards,
Manoj Bilthare
Edited by: Manoj Bilthare on May 19, 2010 12:57 PM

Hi Manoj,
Once you have configured your Listener have you checked pressing the update button and i dont want to ask you which version of NW SP you have installed as you said it was working for you with Build 83, but nevertheless NW SP Level should not be not less than SP3.
If this doesn't help you,please try restarting your server again.
How about the credential editor have you configured this as well?
Regards,
Sudhir Kumar
Edited by: Sudhir Kumar Shambana on May 19, 2010 10:46 AM

Idoc not seen in XI...sent successfully from R/3

hi guys
i have a scenario where i am emulating the outbound idoc process in a user exit. i use the FM IDOC_OUTPUT_INOTIF and it does the required work to send the idoc out. now i can see the idoc sent successfully in R/3 with a status 3, but it cant be seen in XI. now if i use that idoc number and run it thru we19, the idoc reaches XI. can someone tell me what i am missing. i have a feeling that the data is getting stuck somewhere. ironically R/3 is showing me a successful "Data sent to port OK".
please can someone put some more light on this.
Thanks everyone...

Hi Sanket;
Did you try looking in transaction IDX5 in XI? It is the IDoc adapter monitoring tool. It can show you IDocs that were received from R/3 but are not yet processed. Also, check out this artice I submitted awhile ago. It describes the process of troubleshooting IDocs through XI to AII. The first part discusses trouble shooting methods between R/3 and XI.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/technologies/rfid/sap rfid troubleshooting while uploading documents to aii.doc
Cheers,
John

Idocs not coming to XI

Hi,
In our landscape developers are trying to send Idoc from R/3 to XI system.
We have created RFC_XI as RFC connection, which they are using to trigger IDoc from R/3 to XI. Now IDocs are getting triggered from R/3 without any error, but they are not coming to XI.
Now when I checked Inbound queues in XI and found that all queues start with XBTI* are stuck with SYSFAIL error.
Through SXMB_ADM I have tried to register and activate queue for XBTI* but it gives error as below:
Error while activating queue XBTI*
Message no. XMS_ADM610
Can anyone help me regarding this so that IDocs can be processes between these systems.
How can we see wats the issue while activating Queues?
Is there anything else needs to be configured between these two systems?
Thanks & Regards,
Manish

Hi,
First of all thanks for so quick reply.
I have checked at XI Side:
In IDX2 in loaded meta data, two types of Idocs are showing
ORDERS02 and CREMAS01
In IDX1, Partner port and RFC have been configured.
at R/3 side:
RFC is checked its working fine.
Using WE20 and WE21, Partner profile and port been configured already.
In SMQS below is the status:
<R/3 Client> RFC_XI R 10 60 INACTIVE 0 <R/3 HOST NAME>
Register the destination in QOUT scheduler (SMQS) and make it as active
Destination is there (as per above) I hope entries are correct but its showing INACTIVE. How to activate it?
Select the queue from WEOUTQUEUE transaction and start the queue processing; now you can see that your XI starts receiving the Idocs
In WEOUTQUEUE when trying to see IDocs using Reciever Port as RFC_XI its showing nothing.
While I checked sent IDoc status using WE05, previously it was taking port as RFC_XI for sent IDoc but now its taking port SAPID6 after I defined port in XI for R/3 using IDX1.
For SYSFAIL Status, further message is as below:
XI restart in qRFC not allowed
Any more ideas or help? Will appreciate if anything step wise can be refer to check and rectify this error.
Thanks & Regards
Manish

IDOC -- File:(R/3-- XI) : Idocs not reaching XI. Where to check for error

Hi,
I have completed the config for IDOC to XI (R/3-->XI) scenario based on various weblogs available on Sdn.
For testing, I am using we19 to trigger the outbound idoc from R/3. But when I look in IDX5 in XI or message monitor, I do not see any message or IDOC there. Even SXMB_MONI in XI does not have any message.
What could be the potential issue for this behaviour. Is there a way where I could debug or any steps that could tell me where to look for the error.
So far only odd behaviour I have observed is:
When in WE19 I trigger the IDOC for outbound processing, XI login screen pops up, where I need to enter password. Once I click enter the screen disappears and the message, IDOC sucessfully sent to external system/Port appears.
Appreciate your help.
Thanks
Shirin

Hi,
I checked SM58 and teher indeed are errors saying
"Name or Password is incorrect (repeat logon) "
So which connection is having incorrect password in SM59?
I checked and I have a working RFC connection (TYpe 3) in SM59 for XI.
Just to add TCP/IP connection(Type T) has 2 connections not working. They are LCRSAPRFC and SAPSLDAPI.
So what should be my next step in correcting this error as I am not sure which RFC connection user-id is responsible for SM58 errors.
Any feedback is welcome.
Thanks
Shirin

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

Idoc not moved to application and status not updated

Hi Guys,
<b>I am facing one issue in our system for message type DESADV (inbound). please read through </b>
When an IDoc is pushed in from the external EDI system & even though the inbound Partner Profile is set to immediate processing mode:
The IDoc stays in status 64 - 'IDoc ready to be transferred to application'. This assumes that the IDoc has not been processed yet
and still needs to be processed with program RBDAPP01 (or via the process button in BD87).
The issue can not be replicated in test mode i.e. using WE19 to copy and process an IDoc, as it has been found that when using WE19 and processing is set to be immediate, the inbound update is fully completed and the IDoc status is set to 53 - Application document posted.
The issue occurs when an IDoc is pushed into SAP from the external EDI system. "
Please help.

Ramandeep28 wrote:
But still I am not able to make any call.
To/within which country?
TIME ZONE - US EASTERN. LOCATION - PHILADELPHIA, PA, USA.
I recommend that you always run the latest Skype version: Windows & Mac
If my advice helped to fix your issue please mark it as a solution to help others.
Please note that I generally don't respond to unsolicited Private Messages. Thank you.

Idoc not getiing processed

Similar Messages

Maybe you are looking for