Inbound process

how many types of inbound process r there for idoc?

HI ,
Inbound IDOC is nothing but a incoming IDOC or a document.
Say there are two systems sender and reciver system.
The document sent to the reviever will be inbound to the reciever and outbound to the sender and vice versa.
regards,
Sharath

Similar Messages

Error while creating inbound process code

Hi gurus,Iam creating a custom idoc.
800 -> sender
810 -> Receiver
i have completed outbound processing on 800.
On 810, completed following steps for inbound processing.
1.) I have added my Inbound FM in BD51.
2 ) Assigned my FM to Message type and Idoc type in WE57.
3 ) When adding my FM to process code in BD67, it is showing error that
Entry ZSATPC does not exist in TEDE2 - check your entry.
{ zsatpc is my custom process code }.
4) While Creating Process Code in WE42 with options [processing with ale service / Processing
by FM] and saving it is giving error that
" " is not a valid language.
And when I saw help (?) regarding this error, the following text appeared in a window.
Diagnosis
A key with language "" "" was specified for table "EDE2T". This is not a valid language.
This applies to field "LANGUA"
System Response
The system rejects the key.
Procedure
Enter a valid language. This is usually the language you logged on in.
You logged on in language "EN".
Table T002 contains a list of valid languages.
Please solve this error. Give me steps to create inbound process code.
thanx in advance. Hoping replies soon........
Satish.

Dear Satish,
Very peculiar. The language should come from your log on language. Try to login into the system again. Call we42 again and see if it works.
Regards, Rakesh

Inbound Processing with reference to user defined Message type

Respected Readers,
I have created a segment with fields
Matnr
mbrsh
mtart
vpsta
maktx
meins
matkl(Total 7 fields)
I have created a idoc also and a message type and assign the idoc with message type.
Now i have set the communication partners also and created the distribution model with my message type and distributed also to the reciver side.
Now as it is not the standard message type like MATMAS so we cannot use the tcode BD10 to send the material.Instead of it i have to write the program to create the idoc for sending it.
So i have created the program for the generation of IDOC.
Upto here picture is clear.
In the case of Inbound in standard we use the tcode BD11 to get material but same thing as we are not using the Standard Message type we have to create our program.
Now in this case i have written a function module and that function module is attached to the process code and process code is attached to the message type and message type is attached to the partner profile.
i have done the assignments in we57 and bd51 also.
Now idoc is created in the inbound side with status 70.
but i am not getting how to upload this data in standard tables Mara and Makt.
So that if i go to tcode MM02 and give the respective Matnr ,it should display that material.
First tell me what i have done is the right procedure or i have to make somechanges somewhere .
Secondly if you please give me the function module code for inbound processing to upload the data in this standard table( mara ,makt) so that material is created in the reciver side also.i will be very thankful to you.
I am only using seven fields in creating the material.
Please kindly send your answers and not links .
Thanks

i have done the same thing and used same parameter in import ,export ,tables and exception tab.
i have written some code also .
But i am not getting the code to upload the data in the standard tables so that material should be get created automatically as soon as the data get uploaded
in tables.
Somewhere i have read that you have to use the BDC concept Call transaction method to upload the data.
But how to use the BDC code in Function module , i am not getting.
Please can you send any example of code for this task.

BPM Error Permanent Error in BPE inbound processing

Hi
I require some urgent help on this BPM issue.
We are trying to integrate SRM PO being directly sent to Vendors using HTTP. We are getting an error saying Permanent Error in BPE inbound processing. The scenario works like this.
SRM system would sent PO using the SRM Standard interface PurchaseOrderRequest_Out. We need to transform the message into cXML format and send it to the vendors using HTTP adapter. Using the HTTP response we need to trigger an email to the business process team.
The SRM interface is under the software component SAP SRM Server 5.5 and our mapping is being done in a common software component and for the vendor interface we have another software component. We have created a relationship in the SLD by making the common SWC as dependent software component to SAP SRM Server and Vendor Software Component. So in the integration repository we are able to get the interfaces for the SAP SRM Server and Vendor Software Component under the common software component. The receive step for this BPM is a copy of the standard SRM interface PurchaseOrderRequest_Out(as the standard interface is an asynchronous interface) and we would require an abstract interface for the BPM. We have checked the semantics for the BPM and its fine. The related ID development is in place. When the message is being triggered, it gives us this above mentioned error. When we go to the QRFC monitor we are able to check the details.
Regards,
Indranil

Hi Indranil,
     You don't see you BPM....
First go to SXI_CACHE and check that your BPM is listed there and that the compilation has been completed succesfully.
Is this the first time the BPM is being used? If so check if has been configured. For example, go to RWB->Component Monitoring->BPE in <SYSID>
and check if any error is listed there.
In order to check what is going on in your BPM you can trace it:
                  SXMB_MONI_BPE->Diagnosis Processes with Errors
                  SXMB_MONI->Process, get your msg and click on 'PE'. You should see the workitems and see if there is any error.
         Hope this helps you....
         Regards,
            Encinas.

IDOC failure in R/3 Inbound processing

Hi
I was able to successfully generate XML files from Syndicator, but when it comes for processing in R/3 side it get fails all the time with the IDOC err msg : "IDoc included in IDoc packet containing an error: transfer it separate ".
Kindly adivce how to solve the same.
thanks in adv
Alexander

Hi Ravi
Let me explain in detail.
From R/3 to MDM --> All materials in one XML file.
while from MDM to R/3 --> 3 diiferent IDOC am able to
see, one for each material in Inbound Processing.
kindly advice me how to fix the same.
thanks
Alexander

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

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

Permanent error in BPE inbound processing

Hi all,
We have recently migrated are XI scenarios to a new server.
In one of the file to rfc scenario whenver a file is processed i get the error in smq2: Permanent error in BPE inbound processing.
The chances of BPM and mapping error are less as the BPM is working live in another server.
What could be the other problems.
REgards
Edited by: Vinithra Iyangar on Feb 26, 2009 10:36 AM

Dear Vinithra,
Its highly improbable for this error to occur because of transports going wrong. There is one more case which i am sure is the cause why you are getting this error.
"This behavior is when we place the files in the respective folders both the files are picked up by the file adapter. Process instance is generated for BPM. First receive step is encountered and the file is received by it. But due to the wait step the second receive step is not open and hence the second file cannot be delivered to it. Unlike the first case, in this case as the buffering is deactivated the file is not buffered and hence the inbound processing of BPM fails for the second receive step."
Please check if something like this is happening.
Refer : /people/milan.thaker/blog/2008/07/04/delivery-modes-in-bpm
Rgds
joel

Permanent error in BPE inbound processing for BPM Mesg Split

Hi Friends,
i have done the below scenario. i had done everything what theys mentioned in the blog but i am getting the error in smq2 as "Permanent error in BPE inbound processing" sysfail please helpme on this issue.
Illustration of Multi-Mapping and Message Split using BPM in SAP Exchange Infrastructure

Hi Uday,
Please check this blog for your error, This is really interesting. Permanent solution for your question.
Delivery Modes in BPM.
Thanks!

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.

Need of Process code in ALE Inbound Processing?

Hi All,
What is the need of process code in ALE Inbound Processing? Why do we need to reach the function module through process code? we can as well directly point to function module.

Hi Ravi,
Please chcek this link perhaps it may help.
http://help.sap.com/saphelp_erp2005/helpdata/en/dc/6b804043d711d1893e0000e8323c4f/frameset.htm
Regards,
Ferry Lianto

How to handle xml message in proxy inbound processing?

Hi Experts,
I have a scenario that is SOAP Client====>XI===>ECC.
But i don't need to use the XI mapping,i skip mapping
in XI and use the generated proxy inbound processing.
Here is a message structure as below.
<commodityList>
■<commodity>
■■<detailNo>303303</detailNo>
■■<makerName>sony</makerName>
■■<ChargeInfoList>
■■■<productId>aaaa</productId>
■■■<name>bbb</name>
■■</ChargeInfoList>
■</commodity>
</commodityList>
When i sent the message without field entry of <productId>
and <name> i got the response in soap client as below.
<commodityList>
■<commodity>
■■<detailNo>303303</detailNo>
■■<makerName>sony</makerName>
■</commodity>
</commodityList>
The field tag <ChargeInfoList> doesn't display.
But i want it to display as below.
<commodityList>
■<commodity>
■■<detailNo>303303</detailNo>
■■<makerName>sony</makerName>
■■<ChargeInfoList>
■</commodity>
</commodityList>
In case of field entry is empty,how to let the response
contains tag?
As i know ,there is a CONTROLLER in proxy .
But i don't know if it is relevant to this
case and i don't know how to handle it.
Brand

Hi Mrudula,
As far as i know there are no content conversion methodology for HTTPS as the recevier adapter.
Also you can read through these links to confirm the same:
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/content.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/v6rxmx/index.jsp?topic=/com.ibm.wbia_adapters.doc/doc/sap_xi/sapximst30.htm
SAP NetWeaver - XML Communication Interface (CA-XML) [original link is broken]
Regards,
abhy
note: reward the helpful.

BPM workflow "In Process"-Queue "Permanent error in BPE inbound processing"

Hi All,
I am trying to collect messages from 2 different interfaces into BPM( Integration Process).
when I checked in sxmb_moni , i found the error on outbound status & BPM workflow has stuck with status "In Process".
it is not showing any error in Workflow, how to solve the issue.
due to the above error, other messages are stuck in Queue stating "Permanent error in BPE inbound processing".
Please help.
-Jyoti

Hi Jyoti,
Goto T.Code swwl, in that clear all fields and choose from date as 1 month ago and try to execute. Then, delete all entries there. And re-execute your scenario.
In this case, please see SAP Note 1126656.
Please see the below blog, it might be helpful to you.
/people/henrike.kaiser/blog/2009/02/03/how-to-analyze-stopped-queues-in-xi-ccbpm
Regards,
Rajesh

BPM: Permanent error in BPE inbound processing

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

My undertsanding is no work is being generated at all .
If you are getting the error for Source ---> BPM flow then there is a possibility that the ID objects (RD, Interface determination) are to be blamed.
1) Recreate these particular ID objects/ make some dummy changes
2) Activate and ensure that Cache is refreshed
3) Delete the entry in the queue (or delete the queue)....do this only if the XI system is not of Quality, production
4) some times the BPM cannot be triggered from sending a test message from RWB .... so make a testing from the source application .... this particular case has heppened to me and hence suggesting to you.
Regards,
Abhishek.

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

Inbound process

Similar Messages

Maybe you are looking for