IDOC Inbound processing and Locks

Hi there,
we are trying to process an incoming idoc. But all the time we get an error: Immediately processing not possible: EDI: IDOC "XYZ" is currently locked.
There is an lock entry for this IDOC in table EDIDC. We get this error while calling the FM IDOC_STATUS_WRITE_TO_DATABASE with status 52 (application doucument not fully posted).
What can we do?

Exactly why are you trying to write the IDoc status to the database?
It sounds like you have written a custom IDoc. If this is so, you would pass the IDoc status back in table IDOC_STATUS, and it will get updated automatically by SAP.
When SAP extracts the IDoc data, it places an Enqueue lock on the IDOC. That is why you are getting the error message.
HTH,
John

Similar Messages

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

IDOC Inbound Processing and updating DN

Hi,
I'm unfamiliar to inbound processing (i just understand the basics). I've dealt with outbound processing and user exits associated with that.
I have a specific client requirement: an Inbound IDOC is to be processed and update a delivery note. Some field of some segment within this inbound idoc will carry some information which I need to extract and update a field in the Delivery Note with. How could I do this?
Inbound message type is DESADV. Does my requirement need user exit programming or can I set up some kind of a batch job process?
Thanks in advance,
Risad

HI,
For processing inbound idoc one process code attached in the partner profile. From this process code you can find out the function module attached to it.
Inside function module use can check for exit or badi to modify DN or write your custom logic. If you already have the test data you can check it from we19. Here you need to select standard inbound.
Thanks
Subhankar

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

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

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

CATS IDoc inbound problem - Transaction lock, LR002

Customer is posting CATS records via interface from externa system to IDoc for CATS processing. Either the create BAPI (BAPI_...) is used or if there is a change to an already existing posting (BAPI_...). For his i have slightly modified the SAP standard existing FM for CATS inbound processing (IDOC_) to handle both scenarios, create and change. I basically examine CATS data from external system and if it is already existing then I call the change BAPI and if not found the I call the create BAPI.
We have no problem posting with these BAPIs when there postings are imported one by one. But, when several CATS postings arrive at the same second then not all postings are handled correctly. We receive error message "Transaction locked by user XXX" (error message e002(lr)) and XXX is the background communication user. No luck using "Where used" for error 002 in message class LR either. Also tried tracing with trans SE30 but no luck there either. Data is always different but can be for the same personell number. User is correct and not locked - it is the transaction (like CAT2) thats SAP standard reports as locked. Some postings go through alright but then after a few corrrect posting this problem pops up. Very frustating.
Code is correct as it seems only to be a "overflow" problem. Config and data is also correct. Customer was also facing the very same error using the same BAPIs called via RFC and not via IDoc.
Reason to change to IDoc was of course to set the posting as synchronous thus avoiding this "overflow" problem. In standard SAP is IDocs processed in parallell which is fine in many circumstances but not here. Or it might be OK as long as this error don't occur but have found no way so far. Customer is in production and this must be solved. We also tried this in a band new upgraded ECC 6.0 EhP5 system as customer is in the process of upgrading. Same error.
I have found very few hints when searching through Google, SAPNet, SDN etc. This is one of the very few links I found: [Locking problem with FM EDI_DATA_INCOMING;
So I checked this in trans WE46 but as customer is running ECC 6.0 EhP3 we have no such option. Then tried trans nOYEAn setting the parameter "Synchronous processing" but I do not understand how this is supposed to work. Problem stills remains. The values are stored in table EDICONFIG and here parameter INBSYNC is used for the synchrounous setting as of my understanding but we only have this for a user called EDIADMIN and that is certainly not our background user. I don't understand how to set this parameter correctly I guess. SAP help doen't give more insight either - at least not for me.
Does anyone have a suggestion how to solve this problem? Anyone solved this before and willing to share a solution?
<< Moderator message - Please do not promise points >>
I maybe beed to send this to SAP OSS but trying this option first.
To me this is puzzling. Find very few references which normally means few have encountered this. Strange. CATS BAPI interfacing must be used by a lot of companies.
BR, Johan
Edited by: Rob Burbank on Nov 7, 2011 2:36 PM

Hi Johan,
These kind of problems arise when there is a very little time gap between two successive postings. So put a 'WAIT UP TO 2 SECONDS' between each of the postings. This will give time for the previous posting to perform the updates even before the next posting hits the same transaction. This will solve your problem.

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

[HELP] ALE inbound process and Workflow handling problem

Hello,
first of all, i have to apologize about my english level. I will try to explain my problem (thanks for your patience ).
Well, I'm implementing an ALE inbound interface. My development at this point are:
- Customer Idoc Inbound function (with correct interface).
- Customer Basic Type
- Customer Message Type and correct assignment to the Basic Type (Tx WE81 and WE82)
- Customer Object Type (Subtype of IDOCAPPL)
- On BD51 I put "1" for my function.
- On WE57 I put this:
Processing by --> My function and type "F"
IDOC type --> My Basic type (without any extension)
Message --> My message type (without any message code or msg. function)
Object --> My object type (subtype of IDOCAPPL)
Direction --> "2" (Inbound)
- I created a process code for this interface (on WE42):
It is processed with ALE service and by a function module (my function).
On "Module(Inboud)" part I put my function and maximun number of repeats "0". On IDOC part I put my Object type with start event "INPUTERROROCURRED" and end event "INPUTFINISHED".
On application objet I put my Object type.
Rests of fields are blank.
- I defined a partner (WE20) with this new message type and process code.
- Also I created a Task (PFTC) for handle exceptions in inbound process. It has a rule for agent determinate.
I think it is all.
My problem is: when I process an IDOC (from WE19 for example) and it gets 51 status (error), it has to launch an event that trigger my task, is this way? Well I'm not getting any event.
I have all Workflow customizations OK (in this systems are running some Workflows).
In my function code, when I detect any error I put an error in the status table and put in WORKFLOW_RESULT the number '99999'.
Why I'm not getting any event? What I'm doing wrong?
Thanks in advance. Regards.

Hello again,
finally I've solved the problem. The solution for me, was a config on tx. WE42 and some missing code in the function, I only fill WORKFLOW_RESULT with '9999', but I didn't add any register to RETURN_VARIABLES table.
Regards.

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

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

Idoc inbound process

HI
IDocs can be passed to the application either immediately on arrival or can follow in batch.
I can post an inbound IDoc by calling a function module directly: A function is called that imports the IDoc directly.
Can anyone tell how to do this which function module i have to choose and how to create process code for inbound process?
thanks

Hi,
If you are using your own Z function module
create that entries for you FM using the BD51 else if you are using
idoc_input_matmas01 which is sap provide which you can already exist in this list
if you run BD51.
Now go to WE57 and assign the Direction as '2' ( For Inbound processing)
Basic TYpe , Message type and If you have Mess code also then also assign here.
Now go to WE42 ( For Process Code ) create new entires for Process code
in Identification assign your FM.
Now go to WE20 and selct tyour Partner type and
on the left side of screen you will se Inbound parameters there create the enteris
and assign the Process code.
thanks
PK

Monitoring inbound processing and Sync/ Async communication on PI7.11

Hi All,
I am new to PI. We have following two requirements to be done on PI 7.11
1)     Monitoring inbound processing (Txn Code SWF_INB_MON)
2)     Monitoring Sync/ Async communication (Txn Code SXMS_SAMON)
Kindly let me know how should I proceed or what document should I follow or any scenario is to be configured.

Hi,
    1. Start inbound processing monitoring with transaction SWF_INB_MON or SWF_INB_ADM.
           Note that you require administrator authorization for transaction SWF_INB_ADM
    2. You can monitor the throughput of the inbound processing either on the basis of individual process system or system-wide. In this way you can display the throughput figures in any discrete time range, right down to seconds. A similar display for message packages allows you to monitor inbound processing with the same detail."
     3. You can display runtime information about individual messages, for example, the total runtime of a message in inbound processing or just the runtime of a specific section of the inbound processing. For monitoring individual messages click on "Display Message Packages".
regards,
ganesh.

IDOC Inbound processing and Locks

Similar Messages

Maybe you are looking for