Workflow configuration for inbound IDOC

Hi,
i have designed a workflow for handling the errored idoc's.
workflow is triggering fine when i reprocess the idocs through the WE19.
but it is not triggering online...means the event inputerroroccured is not triggering whenever an idoc comes to sap system with error.
I searched the forum a lot to get the answer . i got the answer to to do the config in WE42 .and i went through aravind nagapal book to solve this.But i didn't get exact answer .
Please can any one help me in getting the solution to this problem.
regards
paveee.

Hi Praveen,
you try to start the workflow via event inputerroroccured.
You state that the event is triggered if you create a new IDOC via WE19.
- Have you switched on SWELS to be able to check it in SWEL?
- Have you check there is an event in TBD52 for your object?
- Runs your IDOc in immediate or background?
Ideally, for a processes code, whenever the idoc processing runs into error, the event specified in the transaction we42 (table tbd52) is raised. Can you please place a breakpoint in function module idoc_input_s1quotes_sd at statement
"IF i_edids IS INITIAL.". Thereafter reprocess the idoc for which the
event was not raised, and check if the workflow result is set to '99999'
when processing exits this function module. Please let me know what the
result of the above test is.
Regards
Tibor

Similar Messages

Step-by step procedure for INBOUND IDOC (VENDOR CREATE / CHANGE)

Hi ,
Can any body provide me the step-by-step procedure for Inbound IDOCS.
As i'm new to this i need the the clarification between Inbound & outbound idocs.
How can we differentiate both?
where to define outbound & where to define Inbound?
( If possible Please explain me the procedure for Vendor Create through INBOUND IDOCS )
Thanks in advance..

Hi,
Ale Technology is SAPu2019s technology to support distributed yet integrated processes across several SAP systems.
Outbound Process:
ALE Outbound Process in SAP sends data to one or more SAP Systems. It involves four steps.
1. Identify the need of IDoc: This step starts upon creating a application document, can relate to a change to a master data object.
2. Generate the Master IDoc: The document or master data to be sent is read from the database and formatted into an IDoc format. This IDoc is called as a Master IDoc.
3. Generate the Communication IDoc: The ALE Service layer generates a separate IDoc from the Master IDoc for each recipient who is interested in the data. Separate IDocs are generated because each recipient might demand a different version or a subset of the Master IDoc. These recipient-specific IDocs are called Communication IDocs and are stored in the database.
4. Deliver the Communication IDoc: The IDoc is delivered to the recipients using an asynchronous communication method. This allows the sending system to continue its processing without having to wait for the destination system to receiver or process the IDoc.
Inbound Process:
The inbound process receives an IDoc and creates a document in the system.
1. Store the IDoc in the database: The IDoc is received from the sending system and stored in the database. Then the IDoc goes through a basic integrity check and syntax check.
2. Invoke the Posting Module: The control information in the IDoc and configuration tables are read to determine the posting program. The IDoc is then transferred to its posting program.
3. Create the Document: The posting program reads the IDoc data and then creates a document in the system. The results are logged in the IDoc.
Over view of IDocs:
IDoc is a container that is used to exchange data between any two processes. The document represented in an IDoc is independent of the complex structure SAP uses to store application data. This type of flexibility enables SAP to rearrange its internal structure without affecting the existing interface.
IDoc interface represents an IDoc Type or IDoc data. IDoc Type represents IDocu2019s definition and IDoc Data is an instance of the IDoc Type.
IDoc Types:
IDoc type structure can consist of several segments, and each segment can consist of several data fields. The IDoc structure defines the syntax of the data by specifying a list of permitted segments and arrangement of the segments. Segments define a set of fields and their format.
An IDoc is an instance of an IDoc Type and consists of three types of records.
i. One Control record: each IDoc has only one control record. The control record contains all the control information about an IDoc, including the IDoc number, the sender and recipient information, and information such as the message type it represents and IDoc type. The control record structure is same for all IDocs.
ii. One or Many Data records: An IDoc can have multiple data records, as defined by the IDoc structure. Segments translate into data records, which store application data, such as purchase order header information and purchase order detail lines.
iii. One or Many Status records: An IDoc can have multiple status records. Status record helps to determine whether an IDoc has any error.
Message in IDoc Type:
A Message represents a specific type of document transmitted between two partners.
Outbound Process in IDocs:
Outbound process used the following components to generate an IDoc. A customer model, and IDoc structure, selection programs, filter objects, conversion rules, a port definition, an RFC destination, a partner profile, service programs, and configuration tables.
The Customer Model:
A customer model is used to model a distribution scenario. In a customer model, you identify the systems involved in a distribution scenario and the message exchanged between the systems.
Message control:
Message control is a cross application technology used in pricing, account determination, material determination, and output determination. The output determination technique of Message control triggers the ALE for a business document. Message control separates the logic of generating IDocs from the application logic.
Change Pointers:
The change pointers technique is based on the change document technique, which tracks changes made to key documents in SAP, such as the material master, customer master and sales order.
Changes made to a document are recorded in the change document header table CDHDR, and additional change pointers are written in the BDCP table for the changes relevant to ALE.
IDoc Structure:
A message is defined for data that is exchanged between two systems. The message type is based on one or more IDoc structures.
Selection Program:
Is typically implemented as function modules, are designed to extract application data and create a master IDoc. A selection program exists for each message type. A selection programu2019s design depends on the triggering mechanism used in the process.
Filter Objects;
Filter Objects remove unwanted data for each recipient of the data basing on the recipients requirement.
Port Definition:
A port is used in an outbound process to define the medium in which documents are transferred to the destination system. ALE used a Transactional RFC port, which transfers data in memory buffers.
RFC Destination:
The RFC destination is a logical name used to define the characteristics of a communication link to a remote system on which a function needs to be executed.
Partner Profile:
A partner profile specifies the components used in an outbound process(logical name of the remote SAP system, IDoc Type, message type, TRFC port), an IDocu2019s packet size, the mode in which the process sends an IDoc (batch versus immediate), and the person to be notified in case of error.
Service Programs and Configuration Tables:
The outbound process, being asynchronous, is essentially a sequence of several processes that work together. SAP provides service programs and configuration tables to link these programs and provide customizing options for an outbound process.
Process flow for Distributing Transactional Data:
Transactional data is distributed using two techniques: with Message control and without message control.
Process flow for Distributing Master Data:
Master data between SAP systems is distributed using two techniques: Stand alone Programs and Change Pointers.
Triggering the Outbound Process via Stand-Alone Programs:
Stand-Alone programs are started explicitly by a user to transmit data from one SAP system to another. Standard Programs for several master data objects exist in SAP. Ex. The material master data can be transferred using the RBDSEMAT program or transaction BD10.
The stand-alone programs provide a selection screen to specify the objects to be transferred and the receiving system. After the stand-alone program is executed, it calls the IDoc selection program with the specified parameters.
Triggering the Outbound Process via Change Pointers:
The change pointer technique is used to initiate the outbound process automatically when master data is created or changed.
A standard program, RBDMIDOC, is scheduled to run on a periodic basis to evaluate the change pointers for a message type and start the ALE process for distributing the master data to the appropriate destination. The RBDMIDOC program reads the table TBDME to determine the IDoc selection program for a message type.
Processing in the Application Layer:
The customer distribution model is consulted to make sure that a receiver has been defined for the message to be transmitted. If not, processing ends. If at least one receiver exists, the IDoc selection program reads the master data object from the database and creates a master IDoc from it. The master IDoc is stored in memory. The program then calls the ALE service layer by using the function module MASTER_IDOC_DISTRIBUTE, passing the master IDoc and the receiver information.
Processing in the ALE Interface Layer:
Processing in the ALE Layer consists of the following steps:
u2022 Receiver Determination: The determination of the receiver is done through Customer Distribution Model.
u2022 IDoc Filtering: if an IDoc filter is specified in the distribution model for a receiver, values in the filter are compared against the values in the IDoc data records. If a data record does not meet the filter criteria, it is dropped.
u2022 Segment Filtering: For each sender and receiver combination, a set of segments that are not required can be filtered out.
u2022 Field conversion: Field values in data records are converted by using the conversion rules specified for the segment.
u2022 Version change for segments: Segments are version-controlled. A new version of a segment always contains fields from the preceding version and fields added for the new version. Release in IDoc type field of the partner profile to determine the version of the segment to be generated.
u2022 Version change for IDocs: IDocs are also version controlled. The version is determined from the Basic Type field of the partner profile.
u2022 Communication IDocs generated: The final IDoc generated for a receiver after all the conversions and filtering operations is the communication IDoc. One master IDoc can have multiple communication IDocs depending on the number of receivers identified and the filter operations performed. IDoc gets the status record with a status code of 01 (IDoc Created).
u2022 Syntax check performed: IDoc goes through a syntax check and data integrity validation. If errors found the IDoc get the status of 26 (error during syntax check of IDoc u2013 Outbound). If no errors found the IDoc gets the status 30 (IDoc ready for dispatch u2013 ALE Service).
u2022 IDoc dispatched to the communication Layer: In the ALE process, IDocs are dispatched using the asynchronous RFC method, which means that the sending system does not await for data to be received or processed on the destination system. After IDocs have been transferred to the communication layer, they get a status code 01 (Data Passed to Port OK).
Processing in the Communication Layer:
To dispatch an IDoc to a destination system, the system reads the port definition specified in the partner profile to determine the destination system, which is then used to read the RFC destination. The RFC destination contains communication settings to log o to the remote SAP system. The sending system calls the INBOUND_IDOC_PROCESS function module asynchronously on the destination system and passes the IDoc data via the memory buffers.
Inbound Process in IDocs:
An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.
Posting Program:
Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.
Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.
Workflow:
A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.
Partner Profile;
A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.
Process flow for the Inbound process via a Function Module:
In this process, IDocs are received from another system and passed to the posting function module directly.
1. Processing in the communication Layer:
The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.
2. Processing in the ALE/EDI Interface Layer:
u2022 Basic integrity check: A basic integrity check is performed on the control record.
u2022 Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.
u2022 Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc u2013 Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).
u2022 IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).
u2022 IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.
3. Processing in the Posting Module:
The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.
The results of execution are passed back via the function moduleu2019s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Partner profile for INBOUND IDOC

Dear experts,
Need your help to define partner profile for inbound idoc to R/3 system. There is a third party (Non SAP) based application from which idocs need to be sent to the R/3 system. There is no need to send an outbound idoc from the R/3 system. Can some one please suggest what are the steps to be taken to b configure the partner profile in the R/3 system for the inbound idoc?
Thanks,
Priyanka

Hi
This is not the right location to post this question.
You got to post this query in Data transfers section of SDN ABAP Development forums
Now regarding your question,
You need to create a Logical System with the help of the transaction SALE.
Assign the created LS to the client with the help of same transaction
Go to WE20 and create the partner with the same Logical System name
Now..as you are recieving the Inbound Idoc from external Non-SAP System, you need to maintain the message type in the Inbound Parameters by clicking on ADD Icon over there.
Before doing the above step, you got to create the connection between SAP and Non-SAP System.
Use transaction SM59 to do this. Type of connection would be R/3 I guess
Thanks
Hope it helps.

Process code for inbound idoc's

hi friend,
i want to create a zprocess code for inbound idoc's pls i want to step or code.
regrads and thanks

Hi
Are you using the customised idoc i:e message type .I hope most of the data transfer techniques always has a standard message type and if you are using one such than you can check in transaction we42(inbound process code) .All the steps have been rightly been mentioned for this querry of yours if you can clearly explain as to what message type are you using and for what purpose i can send you with documentation with steps to you.At the end of the day you will be posting idocs so that the data is being reflected in the segments .The things to be noted down is :-
1.Maintain Partner Profile(we20) which is the sender system are you using ?
2.If the satus is 53 it is sucess(green ) else 64(being processed-yellow) or 51(error-red)
3.If you trigger by workflow than you have to use Message Variant .
If you are ok or incase do face any issues please do reply to the forum.
Regards
Somnath

EOIO should be enabled for Inbound IDocs to SAP

Hi All,
My Interface requirement:
i want to send my IDoC's to SAP ECC from SAP PI using IDoc Adapter in EOIO manner. so i have followed the below link.
http://help.sap.com/saphelp_nwpi71/helpdata/EN/96/791c42375d5033e10000000a155106/frameset.htm
1)I have have enabled EOIO in sender File adapter.
2)i have checked the Queue Processing in IDoC adapter.
assumed that IDocs are processing in EOIO manner. for proving the same, i have stopped the RFCUSER which is in ECC to process the IDOCs to SAP.
but still messages are stuck in Trfc queue, so i am thinking that EOIO is not enabled as messages are not stuck in SMQ1.
how to achive EOIO for inbound IDoCS??
Thank You,
Madhav

Hi
It's fine that messages are not stuck in smq2 on PI side. You set in smq1 system, connection and assing connetion pool numer and meesage is transfered to Ecc using common connection. On target Ecc check tcode WEINBQUEUE.
Br
Maciej

ALE Configuration for PEXR2002 IDoc and PAYEXT message type sending to XI

Hi all,
I need ALE Configuration for PEXR2002(Basic Type) IDoc , it's message type PAYEXT.
I don't know ALE Configuration for sending data from SAP IDS to SAP XI.????
I need ALE Configuration doc/pdf??
Please give me some guidline for this..
Regards,
Umesh

Umesh,
I was wondering if you have had any luck creating the configuration for PEXR2002 Idoc, PAYEXT message types, and sending the result set to XI.
I need to perform the same task within our R3 environment using the FTP protocol in XI to send the file to the Bank to be processed.
Any help or direction would be great.
Thanks,
Dave

ALE configuration for Outbound Idoc - Help me

Hi Experts,
I am newbee in SAP and XI. I was trying to send MATMAS Idoc from R3 and i was running into some issues. So i would appreciate if someone can help me.
I am using following link as reference. /people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi
I did all the steps mentioned in the above link ( Creating Logical Systems, Assigning Client and RFC destnations, Creating distribution models ..... etc)
and then everything went well and i saw success messags in all the steps.
I used BD10 to send material and it went well. But when i check TRFC queue, i see some error messages; "No service for system SAPRDI, client 800 in Integrion Directory"
And all the messages are hanging in the TRFC queue.
Note: I havent configured anything in XI yet. I wanted to make sure IDoc gets to XI client first.
Thank you in advance. Pls help me its very urgent.
Thanks,
Surya

I created RFC destination (SM59) and Port (IDX1)
Then i sent another material (BD10) and checked tRFC queue. i found bunch of error in the Queue.
1.connection to host 10.4.23.120, service sapgw00 timed out / CPI-C error C
No service for system SAPRDI, client 800 in Integration Directory
partner not reached (host 10.16.176.29, service sapgw00) / CPI-C error CM
connection to host 10.16.136.127, service sapgw58 timed out / CPI-C error
Note: i have noticed entries for R3 in SLD as below
System Name: RDI ( not SAPRDI as mentioned in the error message)
System Home: r3ides
That might be reason. If so, how to change it in R3 box? Any suggestions?
Please send me if you guys have any links or docs to address this issue.
Thanks,
Surya

User exit for inbound idoc

could anyone please tell the user exit for inbound idoc : ACC_POSTING_GL01

I thnk the inbound idoc name is ACC_GL_POSTING01. User Exit for this is EXIT_SAPLACC4_001.
*****Reward points if useful
Regards,
Kiran Bobbala

How can delayed delivery update be configured for Inbound delivery ?

Hi All,
How can delayed delivery update be configured for Inbound delivery ?
There is setting for Outbound delivery delayed delivery update but how the same functionality be used for Inbound delivery?
Regards
Jimmi

Hello Jimmi,
Unfortunately I must confirm that the Delayed delivery update is only available for outbound deliveries. Please see below note for further details
664316 Tips for the delayed delivery update for TO
I hope this information helps!
Martin

Sample files for inbound IDOC's( EDI)

Hi All,
I am trying to get idoc's into system using EDI , wanted sample files for inbound idocs using EDI.
If someone could send the files please.
rgds
Ajay Sharma

HI,
Here one sample file.U need to change the sender/receiver ID's accordingly to the setup at ur EDI subsystem.This 850 i/b file will create an ORDERS idoc in SAP.
ISA³00³ ³00³ ³01³006906614GE ³01³040986076 ³060714³0640³U³00401³000012157³1³P³>~
GS³PO³006906614GE³040986076³20060714³0640³5008³X³004010~
ST³850³020700691~
BEG³00³NE³020700691³³20060714~
N1³BS³ABC PHOENIX DIVISION³11³RA0290837~
N1³SU³³11³II7930501~
PO1³1³12³EA³123.45³³ND³0469520260~
PO1³2³24³EA³190.23³³ND³0469520211~
CTT³2~
SE³8³020700691~
ST³850³057796284~
BEG³00³NE³057796284³³20060714~
N1³BS³ABC RALEIGH DIVISION³11³RA0289036~
N1³SU³³11³II7930501~
PO1³1³48³EA³61.72³³ND³0469520230~
PO1³2³12³EA³123.45³³ND³0469520260~
PO1³3³6³EA³190.23³³ND³0469520211~
CTT³3~
SE³9³057796284~
GE³2³5008~
IEA³1³000012157~
Also u can check in the system and find some ORDERS
idocs and u can retrigger that from WE19.
reward if helpfulll
ram

Workflow for inbound idoc failures

Hi Gurus,
Can anybody please point me to a place where i can start to see how i can setup workflow to notify users via SBWP whenver there is an inbound idoc error happens. We want to derive the standard functionality to its fullest even before thinking of putting any custom code. I'm specifically looking for hte order acknowledgemetns and shiipping notifications errors of idocs coming from the vendor
Thanks
anusha
Edited by: anusha vemulapati on Jul 2, 2011 4:43 PM

Hi Anusha,
The simplest way is to link the partner profile to a specific user ID. This is done in trs WE20 - you have the link to the WF recipient both generally for the partner (on the initial screen of WE20 when the partner has been selected) and specifically for the different message types - double-click on the inbound message type and choose the tab "Post processing - permitted agent".
You link the partner profile to a specific user by choosing the user type = "US" (user") and then specifying the user name below it. If you want several users to receive the same WF, you can link the partner profile to another user type, e.g. O = Organisational unit. Then you link the users to the organisational unit in trs PPOME.
As far as I remember, the WF for IDoc's in error is activated in the standard system, i.e. the setting above shall be sufficient.
BR
Raf

Workflow for INBOUND IDOC

Hi,
I want to set you a workflow for one IBOUND idoc coming via edi partner. I want to use the organization units and then assign the user to it. what are the steps required for setting up a new workflow totally from the start for a IDOC / Message type and config.
Thanks in adv
/Manik

STEP 1.       USE   SALE -> Error Handling
STEP 2.   Go To Basic Workflow Settings.Use Auto-customise button to allow the system to configure most of the options.
STEP 3
a)Go to SAP MENU -> TOOLS-> BUSINESS WORKFLOW ->
DEVELOPMENT ->DEFINITION TOOLS->TASKS
b) Create a customised task putting IDOCCLFMAS for example   as object type and    INPUTFOREGROUND as object method.
c)Associate the triggring event InputErrorOccurred with the standard task.
d)Associate the terminating event InputFinished with the standard task
e) Assign appropiate agent to the customised task. For this GO TO
     Additional data -> Agent assignment -> Maintain
STEP 4 -- Go to transaction WE20.In the partner profile of the message type CLFMAS enter for the post processing permitted agent.Enter the agent type (Organisational unit,Workcenter,Job,Person,Position or User),agentId and the language.
STEP 5- In case of any error in processing of Idoc a workflow notification is sent to concerned agents.The message is sent to the inboxes of concerned persons which indicates which interface has erred,the associated IDOC number ,status of the IDOC and the date and time of error.
Regarding the complete set up you can check the workflow tutorial in help.sap.com.
regards
Aveek

Handling of Error(s) for Inbound IDOCs

Hi Gurus,
I have an requirement where we need to handle and correct the error if inbound IDOC fails. This inbound will be for Account Document posting.
Please let me know how to handle this issue.
Thanks in advance.
Regards,
Gajanan

Hi,
smells like workflow task.
DI Information
Message type
INVOIC
IDOC type
INVOIC01, INVOIC02
X12 transaction set
810
Edifact message type
INVOIC
Workflow in case of error
TS 0000 8056
Executable program
IDOC_INPUT_INVOIC_FI
Regards,
Clemens

Queue configuration for Particular Idoc

Hi Expert,
We have the requirement where in SA related outbound idoc(DESADV) should go in a particular Queue in other words (Queue sequencing).
Through Queue rules WE85 i can do it & in partner profile i need to assign the rule for that Idoc.
Function module :IDOC_QUEUE_NAME_MESTYP creates the queue names from part of the logical message type name.
Has anybody done it in their project?
How do i go about? In PI what all configuration i need to do so that this Queue will be mapped thier and in SNC system Inbound Queue will be of that particualr Queue.
In Function module IDOC_QUEUE_NAME_MESTYP what all code i need to write so that particular Queue (XBTR*) should get executed for Idoc DESADV.
If any thread is avaialble please provide the link
Regards
shailesh

Also Kcr, pls check this.
Assumin your instance number is 00
ABAP Port : 8000
JAVA Port: 50000
What is to be undwerstand here is the role of your port here, if you want to acess any Xi component residing on the Java stacj you will use 50000, since SLD and rwd are on the java stack you cannot have different port to acess them.
similary for ABAP Stack 8000 is used.....
inaddition to this you will also have the trfc Port for IDOC communication port,
you can check the abap port by SMICMgotoservices......
kindly reward if found helpful.
cheers,
Hema.

Using Oracle SAP Adapter and IBSE for inbound IDOCs

I have been able to successfully use the Oracle SAP Adapter (e.g., IWAY) using the IWAY Business Services Engine (IBSE) to call a BAPI and have information returned. This use case is well documented and seems to be reliable.
However, I have had difficulty finding any examples where IBSE is used with IDOCS. In my case, I would like to have SAP send an IDOC and receive this IDOC in a Fusion 11g environment. I see conflicting statements in the document. On one hand, Section 3 of this document
http://download.oracle.com/docs/cd/E15523_01/doc.1111/e17057/config.htm#BABBGAAH
States "Events are not applicable when using a BSE configuration."
On the other hand, I see lots of documentation that says that you need to configure an Event in order for the IDOC to be sent to the proper destination. IBSE gives the ability to define events for IDOCs but the events are limited to either RMI or JMS. I have looked at the format of the JMS message and it looks extremely difficult to setup.
Has anyone done this before?

Let me try what ever I can to answer.
Loss of IDOCS should not happen. Are you starting the channels in iWay test tools while the JCA adapter is also running?. That should not be the case. iWay Test tools is only for design time purpose. It is not required for runtime. ie. Create channels and test the IDOCS being received. After that stop the channel and start running the server.
I suspect that starting channel in iWay test tools and JCA adapter/BPEL simultaneously will definitely result in IDOCS loss. Some of the IDOCS will come to iWay test tool while others will go to JCA/BPEL.
Regarding 2, lets us discuss this after this loss of messages is solved.
"Another issue that we have with the JCA approach is the requirement to have have a separate channel and a separate program ID for every IDOC. In our SAP system, we have thousands of IDOCS so having to setup a different channel and program ID for each one is going to be a difficult task".Yes. Initial versions of adapter used to support receiving all idocs on same channel. In your case MATMAS05/IORDER01 are received on same programID and customers used has logic to identify what idoc was coming. It was observed that complexity of the application increases exponentially with increased idocs and the debugging effort.And also the interface is not clean. That is the JCA end point cannot be assocaited with a specific WSDL so you will not what you will receive and of what type. To ease this, later version of adapter supported this feature that each idoc type is assocaited with a specific program ID. MATAS05--PID1, IORDER01--PID2. Adapter will ignore if MATMAS05 is sent on PID2.
In OSB we have concept of AnyXML service but I doubt if BPEL has such concept. If I remember OSB smart connect supported your exact use-case, but in later version it was decided to discontinue AnyXML inbounds.
Are you really planning to use hundreds of IDOCS on same PID?. Did you think of debugging complexity in such application? If you really think this need to be supported, please raise an enhancement request with Support. Product management will review your request for further action.
Thanks
Manoj

Workflow configuration for inbound IDOC

Similar Messages

Maybe you are looking for