IDOC Inbound processing error

Hi Experts
While IDOC posting i m encountering an error with status 64 (<b>No resources, Immed. processing not possible. Quota for rdispirfc_max_own_used_wp wxceed</b> )
Can anyone explain the reason behind this.
Regards
DhanyaR Nair

Hi,
This has nothing to do with your IDOC and ideally should not happen on a production system at all.
The work processes processes different tasks in the system like executing programs, background jobs. And you need to have enough for the same.
From a IDOC stand point, you shouldn't be worrying about it.
Regards,
Ravi
Note : Please mark all the helpful answers

Similar Messages

Error : Pre Settings for IDoc inbound processing are missing error

Hi Experts,
There is a CRM job which executes LSMW and I am facing a strange problem during the IDOC posting the error "Pre Settings for IDoc inbound processing are missing error". Can anyone please tell me how to correct this error?
Thanks in advance.
Madhurima.

I'd start with the following document, with one modification. At step 12 after typing GEARAspiWDM press the Enter/Return key once prior to clicking OK. (Pressing Return adds a carriage return in the field and is important.)
[iTunes for Windows: "Registry settings" warning when opening iTunes|http://support.apple.com/kb/TS3299]

LSMW idoc Inbound Processing settings

Hi,
We have done LSMW with BAPI method to create Bank master.
In Idoc Inbound Processing settings -
We created partner type as 'B' i.e, for BANK
While creating Partner Number it is not allowing to create Partner Number. The error is "Enter a permissible partner number"
Please let me know what would be the problem.
Regards,
Hari
Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AM

Hi,
Use patner type as US only and LSMW as Patner number.
this will surely solve your problem .
plz do this way :
The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
Port: LSMW
Name: Legacy System Migration Workbench
Version: 3 (IDoc record types SAP Release 4.x)
Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
SAP recommends:
Port: assigned by the system
Version: 3 (IDoc record types SAP Release 4.x)
RFC destination: Name of R/3 System
Name of port: Legacy System Migration Workbench.
Then the partner type should be defined or selected. SAP recommends:
Partner type: "US" (User)
As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
Partner type: Create US
Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine: READ_USER
Short description: any.
Finally a partner number should be defined or selected. SAP recommends:
Partner number: LSMW
Partner type: US
Partner status: A (active)
Type: US
Language: DE or EN
Person in charge: Your user ID.
Activate IDoc inbound processing
reference : help.sap
thanx.
Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM

IDoc Inbound Processing for CREMDM & DEBMDM

Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.

Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh

Permanent error in BPE inbound processing error

Hi guys...
i am having a problem in my scenario which is involving BPM.
The problem is when i execute the interface it is showing green flag aginst PE in sxmb_moni and in smq2 one queue is showing with sysfail and BPM: Permanent error in BPE inbound processing error.
yes..i searched on SDN and found resources like Note number 1126656
i checked al the steps which were earlier mentioned posts like:
SWWL: there are no entries existing
SMQ2: cleared the queues ,regenerated but still no luck.
My undertsanding is no work is being generated at all .
I checked BPM with F7 : its correct no errors
BPM has return code of 0 in sxi_cache
In ID BPM is latest and refreshed.
Is there any way i can overcome this problem.
Your inputs will be of real help.
Thanks in advance.
Regards,
Seshagiri.

Hi Praveen,
If the BPM goes in error due to "The incoming payload structure is incorrect (not matching message type structure of abstract interface)" , is there any work around?
Currently in my scenario BPM goes into error due to incorrect structure , error show up in SMQ2 . And the subsequent message also get stuck. What I have to do is to delete the queue in error and reactivate the queue manually.
Is there any way we can avoid this situation.
Thanks,
Pankaj

ALE IDOC Inbound processing using IDOC_INPUT_ORDERS

Hi experts,
I am stuck up with IDOC inbound processing.
Can you please let me know about the process in Receiving Purchase Order from the customer system and creating Sales Order in the SAP system? using FM IDOC_INPUT_ORDERS. I have an Idea about WE20, NACE etc.
Can you please explain me about the process on how to go about it?
Kind regards,
Shiva.

Hi,
I have moved this thread from [ABAP, General Forum |ABAP Development; to [Data Transfers Forum|ABAP Connectivity;.
The forum Data Transfer is the place to discuss LSMW, ALE, BDC, Data Transfer Techniques, Batch Data Communication, Legacy System Migration Workbench, Application Link Enabling, IDOCs, BAPIs.
Please, the next time check the most appropriated forum category before posting. Thus you have more chance to have your question answered !
Best Regards.
Marcelo Ramos

Activate IDoc Inbound Processing in LSMW

Hi Gurus,
Why do we need to activate the IDoc Inbound Processing in LSMW if we are going to use BAPI or IDoc in LSMW?
Thanks and Regards,

Hello Paulo
Recently I implemented an ALE scenario where the sending and receiving logical system are the same.
Purchase orders are sent to SAP-XI which returns the IDoc to the same logical system als sales order IDoc.
Thus, our logical system has the ORDERS message type as outbound and inbound parameter. SAP-XI is the other receiving and sending logical system.
The easies way is the "Copy&Paste" approach. Look into your system for existing inbound IDocs and compare their control record with the one of your test IDoc.
Regards
Uwe

What is IDOC Inbound process and Outbound Process?

What is IDOC Inbound process and Outbound Process?
can any one explain about the inbound and outbound process step by step?
Tks in advance,
Phanikumar

Hi,
Inbound means transfer legacy data to SAP system and
outbound means transfer SAP system data to legacy system.
Regards,
Prashant

Inbound Processing : Error when changing a BOM

Hi Experts,
I have the following error when I send a BOMMAT IDoc in "Change" Mode (Editing the BOM, to recreate the History inthe Target system) :
Start processing in API: CSAP_MAT_BOM_MAINTAIN
Group BOM
Changes to the BOM exist after 03.11.2008
Date 03.11.2008 copied from change number
Item (1) 0040 L 000000001084237016 000000000000000000000000 cannot be uniquely identified
Item (3) 0100 L 000000001084237021 000000000000000000000000 cannot be uniquely identified
Item (6) 0200 L 000000000768041196 000000000000000000000000 cannot be uniquely identified
End of processing in API: CSAP_MAT_BOM_MAINTAIN
Any idea ?
Regards,
David

Hi Gordon,
I think I found something.
When I create a BOM with ALE in the Target, no problem. Then when I want to update it, I've got this error ...
In the Source, we're working with Text Object for Text Item (INCLUDE Text ID). But in the Target, Text Object doesn't exist, and when we update or modify the BOM via ALE, the Inbound Process try to find the old Text Object before updating it with the new one ...
I think the solution is to create all Text Object/ID (Ta SO10) in the Target ... I don't understand why the ALE Inbound Process doesn't create Text Objects if they don't exist...
Regards,
David

Inbound Processing Error ?

I create an outbpund idoc as a file on a file port : FILEIN.
FILEIN port is defined as a file port with Dir parameter set as : /tmp/
and FM parameter set as : EDI_PATH_CREATE_DATE_TIME . No parameters are maintained for Inbound file .
I create outbound idoc with :
Reciever Port FILEIN and Sender port A00001 (defined as a trfc port ).
The Idocs are generated in the specified directory .
Now i want to process these idocs with RSEINB00 Program .
I give the filename and Port name : FILEIN to the program .
The partner profile is maintained for the inbound processing .
But I somehow recieve the error : '56 : Reciever port in control record is invalid. '
How can this be solved ? DO i need to maintain the Inbound file parameters too in the File port . ?

Hi,
You should first turn your output IDoc file to an Inbound IDoc file. use the transaction code we12 to that.
Following is the more info on Using We12.
We12 - IDoc testing tool which will emulate an EDI subsystem, by taking a outbound text file IDoc previously generated by SAP and use it to create and process an inbound IDoc. It is also possible to create an outbound IDoc from an inbound IDoc as well. Commonly referred to as the Turn-around program
Field level documentation on each field on the We12 screen..
Source:
Directory + file: The field contains the path and filename of the existing IDoc text file at the operating system level.
Target:
Directory + file: the target fields contain the path and filename of the IDoc text file that is to be created. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (see WE46 for IDoc Administration; WE 21 for Port Definition).
Sender:
Partner Number: Customer or Vendor number of the sender - when testing inbound messages, this partner number must exist as a valid inbound partner (transaction WE20).
Partner Type: Code, which identifies the type of sender (i.e. LI Vendor; KU Customer).
Partn.function: Code, which identifies role of the partner (i.e. SH Ship-to).
Message type: Code, which identifies the type of data, based on the EDI message type (i.e. ORDERS, INVOIC).
Variant: Code, which further subdivides the type of message (i.e. MM or FI for a logical message type of INVOIC).
Function: Code, which defines the function of the message with regard to its transmission.
Test: Flag indicating that this is a test message. This is one of the keys to finding the inbound partner profile.
Port: Logical ID of the sending system. Enter the logical name of the receiving as defined in the transaction WE21. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (WE46).
Recipient:
Partner Number: Customer or Vendor number of the receiver.
Partner Type: Code, which identifies the type of receiver (i.e. LI - Vendor; KU - Customer).
Partn.function: Code, which identifies role of the partner (i.e. SH - Ship-to).
Direction: The direction that the newly created IDoc will be assuming -1 for outbound, 2 for inbound. Default is 2.
Client: The client that the newly created IDoc will be processed in. The default is the client that the user is logged into when executing this transaction.
Port: Logical ID of the receiving system. Enter the logical name of the receiving system in the form 'SAPxxx'. 'xxx' stands for the ID of the SAP System. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (WE46).
Turn-around program examples: When taking an outbound purchase order IDoc (which was generated via MM purchase order create) and turning it around to test inbound SD sales order creation via EDI, the Sender would be a customer while the Receiver would be a vendor. If using an outbound advanced ship notice IDoc (generated via SD delivery processing) and turning it around to test inbound shipping notification, the Sender would be a vendor, and the Receiver would be a customer. If using an outbound invoice IDoc (generated via SD invoicing) and turning it around to test inbound EDI invoice processing, the Sender would be a vendor, and the Receiver
Hope this helps.
Mark the Helpful answerers..
Regards,
Nagaraju Chidurupalli

IDOC inbound Posting Error no 51

Hi Friends,
I am triggering Inbound error using XI.
I am getting Error no 51(Application document notposted), when i am checking in WE05.
Can any one guide me how to trace further error???
Cause of Error????
If data is incorrect in IDOC how can i check, that error is due which field record????
Please guide me and give some T.Codes to trace error in inbound IDOCs
Thanks & Regards
Umesh

the hint with the status record is correct: If you double-click it, you may have a button 'application log' - but only if the inbound processing creates a log.
SAP knows thousands of IDOC basic types, message types, process codes and almost nothing is handled the same way.
So first get the details about Idoc and message types, find out how the inbound IDOC is processed, get the function modules name, use the debugger to see where what error is issued.
You may also have a look at the IDOC's segments contents and see if some data is obviously wrong.
Or just tell the readers here what business process you try to handle using what IDOC - experience may be just one click away.
regards,
Clemens

Test IDOC inbound processing in WE19

Hello,
I want to test an inbound processing for an IDOC in WE19. I don't have any message so i enter 'via message type' in the initial screen.
Then i fill the segments/fields of the presented segments that i think are necessary and also some data in the 'Edit control record fields'.
But when i click on button 'Standard inbound' i receive the error message 'Initial recipient partner type'. Please note I don't fill any parameter in the control fields for receiver, but even if I enter a value in 'partner type' for receiver I got the same error. If I need to fill this parameter I don't know what should it contains.
Does anyone have an idea about what could be the reason of this error ?
Thanks is advance,
Paulo Sousa

Hello Paulo
Recently I implemented an ALE scenario where the sending and receiving logical system are the same.
Purchase orders are sent to SAP-XI which returns the IDoc to the same logical system als sales order IDoc.
Thus, our logical system has the ORDERS message type as outbound and inbound parameter. SAP-XI is the other receiving and sending logical system.
The easies way is the "Copy&Paste" approach. Look into your system for existing inbound IDocs and compare their control record with the one of your test IDoc.
Regards
Uwe

Permenant error in bpm inbound processing error in inbound queue of pi7.1

Hi Experts,
In E filling scenario in SAPPI7.1, iam facing a problem. i.e In sxmb_moni message monitoring, the message was schedule at outbound side.when i extend that, the message was stuck in smq2 with "permenant error in bpm inbound processing".can any one please tell me how to relove this issue.
Thanks & Regards,
Giri.

Hello
Check the note #1126656 BPE-TS: Permanent errors in the BPE inbound processing. This describes some possible causes and solutions for this error.
Regards
Mark

Idoc inbound processing? from non-sap system?

Hi experts,
I'm confused with some functions below:
IDOC_INBOUND_SYNCHRONOUS
INBOUND_IDOC_PROCESS
IDOC_INBOUND_SINGLE
IDOC_INBOUND_ASYNCHRONOUS
can you tell me what are the differences? when to use them?
for sap outbound processing, we can only call function master_idoc_distribute to generate idoc or use message control to trigger outbound idoc. no other options, correct?
for sap inbound processing, if we use message control for automatical posting, we have process code which read the inbound idoc file and do the sap posting. when to use those functions above?
does the middlewares like seeburger, GIS call those functions to generate idocs at SAP side?
in what scenarios can we use those functions? read directly non-sap file into sap internal table then call the functions to create inbound idoc? how about the posting? call inbound processe code function after the functions above?
in case the interface between sap and legacy system is using above functions to build inbound idoc in sap and sap use process code for inbound posing, sap can monitor all inbound process using idoc, but how can the legacy system mornitor the interface?
Thanks.
Legend.
Edited by: legend li on Dec 21, 2010 4:58 PM
Edited by: legend li on Dec 21, 2010 5:40 PM

Hi Christophe,
Awesome!!!!!! it worked, You are the best.
I could able to create a sales order in CRM,but below are the valid data I passed in the respective segment fields.Except for first 3 values rest all did not get reflected in teh Sales order.I feel i am missing some qualifiers.
Can you kindly share the IDoc data to be passed in...along with respective segments and fields:
Segment                                                 Field
E101CRMXIF_BUSTRANS     OBJECT_TASK
E101CRMXIF_BUSTRANS     PROCESS_TYPE
E101CRMXIF_BUSTRANS     POSTING_DATE
E101CRMXIF_PARTNER                          PARTNER_NO
E101CRMXIF_PARTNER                RELATION_PARTNER_NO
E101CRMXIF_ORGMAN         SALES_ORG
E101CRMXIF_ORGMAN          DIS_CHANNEL
E101CRMXIF_ORGMAN         DIVISION
E101CRMXIF_SALES             PO_NUMBER_SOLD
E101CRMXIF_SALES            YOUR_REF_SOLD
E101CRMXIF_SALES            PO_NUMBER_SHIP
E101CRMXIF_BUSTRANS_ITEM     ITEM_NUMBER
E101CRMXIF_BUSTRANS_ITEM     ITEM_TYPE
E101CRMXIF_BUSTRANS_ITEM     ORDERED_PRODUCT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT
E101CRMXIF_PRODUCT_I     PROCESS_QTY_UNIT_ISO
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT
E101CRMXIF_PRODUCT_I     BASE_QTY_UNIT_ISO
E101CRMXIF_SCHEDLIN_I     ORDER_QTY
Thanks a ton in advance .
Vijay

IDOC inbound processing ( Function module Rquired )

Hi,
I am working on IDOC inbound, I am looking for a standard FM for Production order confirmation which i need to assign in WE57 along with the standard Message type(Production order confirmation).
Could you please let me know where i can get the standard inbound function modules for the standard idoc types,
for eg: IDOC_INPUT_ORDERS for sales order.
Thanks.
Krishnakumar

Hi,
Go to WE42 for inbound processing codes and WE41 for outbound.
OR
We have WE19 which is a test tool for IDOC processing.
Provide the IDOC number then press F8, then in the next screen , you will have inbound function module.
Click that button. Then enter the text in search criteria.
Then you can get related function module.
Reward points if helpful.
Thanks and Regards

IDOC Inbound processing error

Similar Messages

Maybe you are looking for