Idoc using inbound process

Hi,
my issue is regarding the Idoc using inbound process using the FM BAPI_IDOC_DISTRIBUTE_LIST1.
here the user wants the dhmt plant tobe refer instead of mirror plant.
can anybody help me regarding this or any doc regarding iDOCS inbound.

Seetha,
I have this already..
IDOCPACKET
Object type                         IDPKWMMBXY
End event                           MASSINPUTFINISHED
IDOC
Object type                         IDOCWMMBXY
Start event                         INPUTERROROCCURRED
End event                           INPUTFINISHED
Application object
Object type                         BUS2017
Start event

Similar Messages

IDOC: LOIPRO, inbound Process Code?

Hello everyone,
I'm trying to create a Production Order using IDOC: LOIPRO. I'm in the process of configuring the Partner Profile and I need to define the inbound Process Code for message type: LOIPRO. Does anyone know which Process Code to use for that message type?
Warm regards,
Glenn

Hi Glenn,
Message Type: LOIPRO
Receiver Port: The one created in step u201CDefining a Logical Portu201D
Basic Type: LOIPRO01
if want to more about it pls do chk this link
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/201769e0-3174-2910-e287-baa58d198246
if found wort pls do te req
Thanx
Sampath

Idoc's inbound process

Hi,
How to process the inbound Idoc?
How to call the 'Inbound_process_idoc'.
Thanks,
Rohit.

Hi Rohit
I am just making clear to as what Gordon sates.Firstly what message type are you using .Execute tcode:-BD87 give in your message type and basic type .Give in the changed time and execute check what is the satus 51(error,red) 64( accepted for processing,yellow) 53( sucess,green ) .
Check whether you have created in your partner profile for the message type which you are using(we20) .Check for your process code corresponding to your message type in (we42) .Process immediately.
Test your idoc using (we19) give in your idoc number and process standard inbound processing.This should show your partner profile found(green) and note down the standard inbound module.
Regards
Somnath

Processing large volume of idocs using BPM Processing

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

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

IDOC COND_A Inbound Processing

We are trying to update Condition Price using COND_A (COND_A03)IDOC. Our functional requirements are similar to transaction VK11/VK12. We store the Contract Price and Contract Number coming from an external system in Condition Texts:Internel Comments and Permits. These correspond to two structure fields LV70T.LTX01 and LV70T-LTX01.
I did not know what field in IDOC these correspond to. If anyone worked on Condition Prices please let me know asap.
Regards
Mike

Hi Mike,
I am not sure if there is a field in COND_A03 Idoc to store your condition texts corresponding to your sturcture fields.
The function module to process the incoming COND_A03 Idoc is "IDOC_INPUT_COND_A". You can view this function module using Tr.Code SE37 in R/3.
I would suggest debugging( in foreground )this function module using Tr. Code WE19 with a sample COND_A03 Idoc. Try to see if you can find any corresponding fields in the IDOC for your fields LV70T-LTX01 AND LV70T-LTX02.
If you can't find these fields in IDoc, this functional module also has a CUSTOMER-FUNCTION, where you should be able to write a custom user exit to populate the fields with custom or enhanced IDoc.
Hope this helps.
Regards,
Sam Raju

Material master iDOC for inbound process

Hi,
I am trying to post the Data to the inbound iDOC for material master and i want to set the KZKUP(coproduct Flag) in MARA table but there is no field in the E1MARAM segment of the MATMAS03 iDOC to set this flag. There is one field in the E1MARCM segment but setting that is not reflecting in the MARA table it is setting in the MARC table only.
So can anybody help me out in this.
Thanks.

Hi Dirk ,
Thanks for your reply . Can we use matmas03 for loading. What will be the differences between these two IDOCS.

Add new inbound process code we42

i am using we42 to add process code mbgm post goods movements identification appl_idoc_inputi for processing with ale service for processing by function mode
i am getting choose the key from the allowed namespace next to the process code.
I think i read that in transaction sm31 i need to look at table v_tbd51 so i did
i see function module appl_idoc_inputi
now what do i do?
the bottom line is when i go in bd87 i get function module not allowed so i am trying to correct this by adding a process code for mbgm

when i go into bd87 i see idoc 631763
idoc in inbound processing
application document not posted
mbgmcr
function module not allowed APPL_IDOC_INPUTI
when i go into we02 is see control rec idoc 631763 message MBGMCR02 i see several data records(6 segments)
when i go to performance assistant is says the following
1. Please check that the process code in the inbound partner profile is correct.
2. If this is the case, you should check the ALE inbound methods ALE inbound methods for the process code and see whether the specified function module and application object type are correct.
so i am trying to add to the message mbgmcr02 the process code mbgm
am i thinking correctly
how do i do this

Problem in Inbound Processing

Hi
I am using Inbound Processing using WE19.
It is showing "Partner profile not maintained". However I have maintained in WE20 & added Msg Type in Inbound Params.
After generating IDoc, in WE05 its showing status Red & showing message -
Partner profile inbound not available
Message no. E0337
Diagnosis
An inbound partner profile could not be found with the following key:
/PROCLNT100/LS//MATMAS01////
This involves the key fields of table EDP21.
I have checked in Table EDP21, entries for that Partner Profile exists.
Please help.

Hello Nikhil and other Experts,
I neeeeeed your guidances. Thank you all in advance. I am explaining what I have done so far in the following!!
Scenario: 1) Same system: T05
               2) Two clients: 454 and 455
               3) Two logical system for sure: T05CLNT454 and T05CLNT455
               4) Transfer Material Master Data from 455 to 454
Since I am a student and this system is actually for me to play around and practice, I did something crazy. I have been browsing so many forums and taking so many actions, but still I am having some issues.
What I have done:
1) Went to 'BD10' on 455 -> Tried to send material master data
2) 0 Communications generated for IDOCS
3) Googled the solutions and found out that it was due to filter setting.
4) Went to 'BD64'. Since message type for transferring Material Master is MATMAS, I went there trying to inactivate those annoying filters for message type MATMAS.
5) I could not inactivate those, so I deleted them intentionally, even though the system warned me not to delete so. The technical names of those two filters I deleted were 'MM-PUR1' and 'MM-PUR2'
6) Later, I created another filter, which was related to MATMAS, without activating it, or say without setting ANY filtering parameters.
7) I did the same things on 454. (Deleted two filters and created another one called TEST)
8) Went back to 455 and went to 'BD10' again.
9) 50 IDOCS generated.
10) Went to 454 and used 'BD11' to received material master data. Was not able to receive any.
11) Used 'WE02' on 454, and those IDOCS were all showing error 56. (Red message)
12) Used 'WE20' to define partner profiles on both clients, 454 and 455. (I actually just did whatever I felt like to do, since this system was only for me to practice. I don't mind messing it up. Haha~~)
13) Went to 455 again and used 'BD10' to send my materials again.
14) Back to 454 and used 'WE02'. This time, some (about 8 IDOCS) were green and 42 IDOCS were yellow with message 64 (IDOC ready to be transferred to application)
15) Executed 'BD11' on 454, and there were exactly 8 materials being transferred.
16) Re-did 'BD10' on 455 and 'BD11' on 454 many times, but it seemed that there were no chances to successfully receive 50 IDOCS on 454. In other words, there were still yellow messages each time.
Some suggestions from other forums said that we could increase the number of "dialog work process". I am just wondering is that the root cause to my situation now?
Any other clues from you experts? BTW, if some of you see what I was doing was crazy, please correct me as well. For example, step 5, deleted two filters directly without a doubt. Haha~~ (Maybe you can tell me how to inactivate them?) Thank you soooooo much in advance!!
Best best regards,
Alfred

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

Steps in Inbound Processing in ALE IDOC

Hi all,
Could anyone explain the steps to be followed in inbound processing in ALE Idoc.
I know we have to create a FM n then call that in a program. But still the detail steps are not clear.
An example will be really helpful.
Thanx

Hi
Outbound:
Step 1. Application document is created when transaction is saved.
         2. Message control is invoked.
         3. Messages are processed by system.
         4. Messages are Edited (if desired).
         5. Output (ALE / EDI) is checked
         6. Validate against Message control record from Partner Profile
         7. Application Document is saved.
         8. Entry NAST table is created for every selected output program
              along with Medium & Timing.
         9. Check for Process Immediately .
                 If (yes)
                   Determine Processing Program from TNAPR Table.
                 ELSE
                   Execute RSNASTED Program.
       10. Read Partner Profile to determine Process Code.
       11. Process Code points to the Function Module & Invoked.
       12. IDoc is generated.
       13. Check for ALE Request.
                    if (Yes)
                        Perform Filters, Conversions, Version Changes etc.
                    Else.
                        IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
        2.   Subsystem calls Functional Module                                 EDI_DATA_INCOMING from startRFC program.
         3. Data in Control Record is validate against the Partner                       Profile.
        4. IDoc is generated in Database and syntax check is                      carried out.
        5. IDoc file is deleted once file read.
        6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
                   7. Check for Process Immediately.
               If NO
                 Execute RBDAPP01 Program
               Else
                  Read Process Code from Partner Profile
                       Process Code Points to Function Module
                 Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Anji

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 to flat file using Integration process does not show up at all

Hello All,
I created a scenario IDOC to Flat File using Integration Process and one without IntegrationProcess. I am able to execute the one without Integration Process easily.
However when I send the IDOC from SAP then the Integration Process scenario just does not work.
I Checked SXMB_MONI There is no entry for the Integration Process.I can see entry for other without Integration Process.
SXI_CACHE : I can see my Integration Process active
SWEQADM : I have activated the Event Queue and Background job
SWF_XI_ADM_BPE : ALL BPE is showing green status.
All syntax check on IP are fine.
There is no Basis Help for me so there could be some additional basis steps which need to be configured. Has anyone faced such an issue with Integration Process?
Regards
Prashanta

Hope this might help you. when u configure an IDoc as Sender with BPM this is how you proceed.
1. let us split the scenario into two.
a. Sender to BPM ( Integration Process).
b. BPM to Receiver.
2. First let us configure the first Sender to BPM.
a. Sender Agreement( Not required ).
b. Receiver Agreement( NOT Required).
c. Receiver Determination( Sender Service, Outbound Interface, Receiver Service(Integration Process).
d. Interface Determination( Inbound Interface(Sender Abstract Interface), Message Mapping(NOT Required if your using transformation stepin Integration Process)).
3. Now let us configure the Second BPM to Receiver.
a. Sender Agreement( NOT Required)
b. Receiver Agreement( Sender Service(Integration process), Receiver Abstarct Interface,Receiver service, Inbound Interface).
c. Receiver Determination( Sender Service(Integration Process), Receiver Abstarct Interface,Receiver Service).
d. Interface Determination( Inbound Interface, Message Mapping(NOT Required)).
So Finally we have One Receiver Agreement, Two Receiver Determinations, Two Interface Determinations.
Please let me know if you have any more queries.
Regards
Gopi

File to idocs - sequence of inbound processing

Hi everybody,
we have a file to (2) idocs scenario. In XI we map the received data of vendors into two idocs (adrmas and cremas). After building the idocs we send them in that sequence to the reveiver systems (recommended). The problem is that in the receiver system very often the idoc cremas wants to be processed before adrmas is ready. This leads to the error "vendor xy is blocked by user sapale". Especially for massprocessing I get a lot of these error-messages in bd87. As workaround I processed all the error-idocs by the report rbdmani2. (First step adrmas - second step cremas) But then I face missing data in some cases in table lfa1 - which seems to me that the sequence of 1. adrmas and 2. cremas was not correct processed.
Is there a possibility for inbound processing with the rule process adrmas - wait until ready - process the associated cremas and so on?
I checked the sap-help article for seralisation - but we could not achieve a better result by queing the outgoing messages in the xi.
Thanks very much.
With kind regards
Jörg

You have to get a solution based on the following concepts
1. Do not use BPM it is not efficient
2. Understand what is the difference between an IDOC in received state and processed state. Received state mean IDOC is saved into IDOC table. Processed state mean IDOC processed into the business system.
3. You can ASK BASIS guy to turn on the immediate IDOC processing option in SAP system,so that SAP process the IDOC as soon as it arrive in IDOC table. This is not efficient, in case if your SAP system has to process SAP online client request and SAP document (inbound and outbound) same time.
4. Understand the concept of standard based integration, mean integration system provide the option to business parties to provide the successfull message transfer.
Based on all these points I recomend you to follow the steps below.
1. Extract each record from the input files into two idocs.
2. Send the first IDOC to the receiving system
3. Send the second IDOC to a ESB storage such as DATABASE, JMS Queue, MQ Series Q (if you have available) or even to another File.
4. Develop an RFC module to check the status of the IDOC being send to the receiving system. Status here mean whether the IDOC data processed into the business system. You can do this lookup using a custom RFC lookup using the attribute connecting the first IDOC record with second IDOC.
5. Process the records (second IDOC) from the intermediate storage using the RFC lookup into the business system updates its status as ready to deliver.
6. Using another process such as FILE to IDOC or JMS to IDOC or JDBC to IDOC send each record which are ready to process from intermediate storage to the receiving system.
7. Create a report using FILE or JMS, JDBC adaptor module to keep track of these three stage processing, so that in case an inconsistency happed you will have an auditing trace available.
This is the standard based integration approach.
ABAP guys, BASIS guys they may not get it when then repair a BMW in local auto workshop, cuz I had to fight with them 4 years ago to make it happen in Verizon supply chain project where I had to accomplish the same concept in SAME IDOCS you mentioned here.
BPM, turning on immediate processing of IDOCS etc will end up in buying another 16 CPU hardware and BASIS guys or ABAP guys running BAD record IDOC processing report for 350.00 hr consulting FEES.
SAP is a good company and XI is a good product, as long as it is being used as per right usage.

IDoc to Soap, with BPM - Permanent error in BPE inbound processing

Hi Experts,
IDoc to Soap, with BPM - > Permanent error in BPE inbound processing
How to rectify this any issue???
Thanks-
sk

Hi,
The inbound processing encountered a permanent error and the queue therefore stopped.
The error message "Permanent error in BPE inbound processing" may be caused by the following:
- At the start or when you process a process instance, the inbound processing encounters an exception that was not handled. This exception is triggered, for example, by a transformation step, a synchronous send step or a control step but it was not caught in an exception handler branch. If the exception that was not handled occurs in the first transaction of the started process instance, the system does not write the process instance to the database but it sets the queue that has this error message to the error status.
Refer to the help in Note 1082099
- The inbound processing triggers this error if the correlation evaluation shows that a message should be delivered to a process instance that has the status "error". Since delivery to process instances that contain errors is not permitted, the queue is stopped.
Use the simulation of the message delivery in the detail view of the relevant queue LUW to determine the relevant process instance for the affected message and use transaction SXMB_MONI_BPE "Continue Process Following Error" (or transaction SWF_XI_SWPR) to continue. If you cannot continue the process instance, check whether you can logically delete the instance. In this case, use the method that is described in Note 807906 to logically delete a process instance.
Check whether your system contains other process instances that have errors in order to detect similar problems. Use transaction SXMB_MONI_BPE "Continue Process Following Error" or transaction SWF_XI_SWPR.
Use the report RSWF_CRL_MAINTAIN to check all of the correlation instances in question or the relevant process instances that you can reach using "Display Work Item".
- Messages that cannot be delivered because no correlation instance can be found may lead to the error that is mentioned here. Check whether the causes that are outlined in Note 1094028 affect your case.
Hope this will help you.
Regards
Aashish Sinha
PS : reward points if helpful.

User Exit for Inbound Process - Changing IDOC control record

Hi,
I want to utilize the identification field (under details tab) of the IDOC Control Record. What is the suitable user exit for inbound process that i can use to change the IDOC control record?

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

Idoc using inbound process

Similar Messages

Maybe you are looking for