EOIO with IDOC

Hello,
My simple scenario is IDOC -> XI -> IDOC
Is there a simple way to switch from EO to EOIO.
I need all idocs to be processed in order on both inbound and outbound sides
I am using XI 3.0 with SAP 4.7
Thanks
Vad
Message was edited by: Vad Vayntrub

Hi,
I have the same problem but I'm on SAP R/3 4.6C on both outbound an inbound.
In case of solve the problem from XI to the target system, how can I preserve the order in the outbound from the sender to XI (if there is a rfc connection error CPI-C, the retries of resending IDocs breaks the sequence, so we are loosing the order from the beginning of the interface).
Any idea??
Best regards

Similar Messages

Message with IDOC number, created by LSMW, missing in job log in SM37

Hi gurus,
We have a temporary interface which uses LSMW to create IDOCs and update in SAP. It's used for materials, BOMs and document info records. In LSMW we have defined standard message types MATMAS_BAPI, BOMMAT and DOCUMENT_LOAD for the IDOCs. All these have the same problem.
A background job runs and starts LSMW. In the job log in SM37 I want to see which IDOCs were created. For some reason this is different in my development system and my test system, and as far as I know all settings should be the same. In the test system LSMW creates more message lines in the job log, than it does in the dev system. Message number E0-097 is "IDOC XXXX added", and this is missing in the dev system.
This is what it looks like in the dev system:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW   509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW   502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW   513    I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')       /SAPDMC/LSMW 516    I
And this is what it looks like in the test system. More information, which is exactly what I want in dev system too:
Data transfer started for object 'MATMAS' (project 'X', subobject 'Y')             /SAPDMC/LSMW   501    I
Import program executed successfully                                                             /SAPDMC/LSMW 509    I
File 'XXX.lsmw.read' exists                                                                               /SAPDMC/LSMW 502    I
Conversion program executed successfully                                                    /SAPDMC/LSMW 513    I
File 'XXX.lsmw.conv' exists                                                                              /SAPDMC/LSMW   502   I
IDoc '0000000002489289' added                                                                      E0                         097   S
File 'XXX.lsmw.conv' transferred for IDoc generation                                      /SAPDMC/LSMW   812   I
Data transfer terminated for object 'MATMAS' (project 'X', subproject 'Y')      /SAPDMC/LSMW   516   I
In both cases the IDOC is created and update works fine.
My only issue is that I can't see the IDOC number in the dev system. I know I can get the IDOC number in WE02, but in this case we have program logic which reads the job log to be able to check IDOC status before sending OK message back to the other side of the interface.
I hope any of you can have an idea how I can update somewhere to get message E0-097 with IDOC number into the log.
Regards,
Lisbeth

Hi Arun,
If you want to show your messages in the job log you have to use the MESSAGE statement. In case you use WRITE statements an output list be created which can be found in the spool (there is an icon to go to the spool directly).
Regards,
John.

Problem with IDoc scenario - IDocs do not aarive to XI

Hi guys!
I have a problem with IDoc->XI->File scenario. Colleagues send IDocs from R/3 and they are not in the XI. In R/3 they look like if they were correctly sent, however, I can not see them in sxmb monitor. BUT, when they send them again explicitly from R/3 (t-code WE19), they arrive...
REALLY strange...
Any suggestions?
IDX2 metadata loaded.. I think, all needed settings are done.
Question - do I need to set up LS in XI ABAP part?
Thanx, Olian!
P.

Hi Olian ,
just check if u have followed all the following steps
SAP XI
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (IDX1)
a) Select create new button
b) Enter the port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Load Meta Data for IDOC (IDX2) a) Create new
b) IDOC Message Type
c) Enter port created in IDX1.
SAP R/3
1) RFC Destination (SM59)
a) Choose create.
b) Specify the name of the RFC destination
c) Select connection type as 3 and save
d) In the technical settings tab enter the details SAP SID/URL and system number#.
e) Enter the Gateway host as same details above SID/URL.
f) Gateway service is 3300+system number#.
g) In the Logon /Security tab, enter the client user & Password details of Destination system.
h) Test the connection and remote logon.
2) Create Port (We21)
a) First Select Transactional RFC and then click create button
b) Enter the destination port name as SAP+SID (The starting char should be SAP)
c) Enter the destination client.
d) Enter the RFC Destination created in SAP R/3 towards other system.
e) Save
3) Create Partner Profile (WE20)
a) Create New
b) Create the Partner no. name as same the logical system name of the destination system.
c) Select Partner type LS
d) Enter details for Type: US/USER, Agent, and Lang.
e) Click on the + button to select the message type.
f) Select Partner no. and LS which ever create above.
g) Select Message type
h) Select Process code related to the Message type.
I) save.
In SLD System Landscape Directory
TS for R/3 (Logical system):-Assign the client name created in R/3 as Logical system Name.
Ts for Third Party (Logical system):-
BS for SAP R/3 (Logical system):- Assign the client name created in R/3 as Logical system Name.
BS for Third Party (Logical system):-Enter the XI logical system name.
In Transaction SALE
Define and Assign the logical system name
Regards,
AshwinM

Mapping Problem with IDOC HRMD_A05

Hi All,
When i am mapping source structure with IDOC HRMD_A05 i am getting Mapping not sufficiently defined...
The idoc is used to change the address of employee(infotype 0006)..
my source structure is
EMPADDR_MT
   EmpAddr1
     Trans_INFTY *
    Address1
      AddressType *
      PERNR       *
      EFdate      *
      Addr1       *
      Addr2       *
      ADDR4       *
      City        *
      Country     *
      state       *
      Postalcode *
the fields to be mapped
So can any one help me out what r fields to be maintained for <b>HRMD_A05</b>...
Regards,
Sridhar
Message was edited by: sridhar reddy kondam

All the required fields & segments(shown red in mapping editor or min occurence:1) of idoc need to be mapped.If any of the fields are not available in your source for mapping..map those fields with empty constants using constant option of the mapping editor.

How to start with Idocs??

Hi,
I am a novice in sap. Can you please guide me how to start working with IDocs?? I know the basics about ale, edi, message type, idoc type and transactions associated with it.
Essentially, Can I have sample problems to practice IDocs so that i could become confident in this topic??? Plz. give hints as well...... to avoid getting bothered with further queries.
Thanks
Gaurav.

Hi Gaurav,
Check this info.
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
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
Also check this links for additional information.
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
Hope this resolves your query.
Reward all the helpful answers.
Regards

Idoc to idoc scenario with idoc tunneling

IN idoc to idoc scenario with idoc tunneling the XML_CONVERSION parameter to value 2 is set whish means An IDoc is converted to IDoc-XML if requested by the service
I want to know where we specify this and how we specify?

1. /people/michal.krawczyk2/blog/2005/11/21/xi-idoc-to-idoc-tunneling--how-fast-and-easy-can-you-get
2. /people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
ref these weblogs.
It is given under;
<i>TCODE - SXMB_ADM
- Integration Engine configuration
- set the XML_CONVERSION parameter to value 2</i>

EOIO for IDOCs to XI

Hi,
My scenario is IDOC ---> xi ---> File.
Need to implement EOIO(serialization) for IDOCs coming from ECC.
Checked "Queue Processing" and assigned rule "FIRST_16_OF_MESTYP".
When I send the IDOC using WE19, I get message "IDocs are stored in the queue".
But, IDOCs are not coming to XI. Please help.
Versions: ECC 6.0 & PI 7.0 SPS 13.
Also, do I need to maintain an entry in IDXQUEUE table?

Hi
use similar thread
How to implement IDOC Serialization(EOIO) using IDOC Adapter
Re: Posting idocs in sequence in SAP from file (without BPM)

Check in BAdi if delivery processed with IDOC or with transaction

Hello to everyone!
I have encountered an issue and hopefully you could help me in solving this.
I have developed an enhancement (BAdi) in delivery processing.
Every time delivery is being changed - method is triggered and line item is being validated against some conditions
But now I would like to prevend BAdi from being launched when delivery comes in IDOC.
For this purpose I just put a simple condition in BAdi method:
IF sy-batch NE 'X'.
//here perform validation.
ENDIF.
Unfortunately validation is still performed. Looks like when IDOC is being sent to ECC from PI, sy-batch is empty.
I would also like to prevent validation from being launched when IDOC re-processed manually (BD87 or sth.)
But then sy-batch is also empty.
Could you please advise some solution for this?
How to check in BAdi if delivery is being processed with IDOC or with transaction (VL32N, VL31N, VL32, ...)
I would appreciate every comment on this.
Kind Regards,
P.
Edited by: Piotr Wojciechowski on Jul 28, 2011 8:59 PM

Hi Max,
Thanks a lot for your reply!
Yes, indeed, IDOC is processed by FModule IDOC_INPUT_DELVRY.
You mean I should for example
find some place in this FModule (exit/enhancement point/...) where I could put-Z-code
and raise a delivery number (or just some flag) to memory (EXPORT TO MEMORY..)
and later on catch it from memory in my BAdi method (IMPORT FROM MEMORY ...)
to check if delivery processed by IDOC/not IDOC ?
Kind Regards,
Piotr.
PS. Maybe you also have some idea how to debug such communication triggered from PI to ECC?
I have posted this in separate [thread|PI-ECC connection (IDOC scenario), how to debug? (External BP);.

Store order offline with IDoc WGSREQ

Hi all
Does anybody know how to mark for deletion purchase order item with IDoc WGSREQ (Store Order functionality in IS-Retail)?
I have succesfully created PO and PO with return items, but I could not mark for deletion items with E1WGRP1-ACTION='003' (Item cancelled).
regards,
Novomir

Deletion functionality never work for WGSREQ since it has several design errors in source code of FM VWWS_STORD_DISPATCHER and VWWS_STORD_DELETE_DOCUMENT. I hope that SAP will do correction soon.

Create Info record with IDOC

Hi gurus,
I would like to create info records from external system through IDOC. Can someone help me with this?
Regards,
Marina

Thanks for the fast answer.
We are trying to make Info record with IDOC INFREC (function module idoc_input_infrec). We create successfully info record, but the problem is that the NETPRICE = 0 and also VALID TO DATE = 31129999 (because no price).
Please, if you need some more details, let me know.
Thanks!
Marina

Problem with idoc DEBMAS

Hi everybody.
We have a problem with idoc DEBMAS.
This idoc is sent from R3 to PI throw change pointers then the idoc is field only with the data modified in the master custumer.
We need the information fill it in the segment /IDOC/E1KNA1M/E1KNVVM to determine the receiver determination but this segment is not always sent.
What can be done in R3 to send always this segment.
We dont want to sent the whole data but always this segment.
Any idea???
Thanks a lot!!!!!

Hi,
As E1KNVVM segement is not mandatory, when you are triggering IDoc based on change poitner data might not populted in the E1KNVVM segment until some sales data is changed.
if you need that segement always just copy the Idoc type and make it mandaotry field.
otherwise yoy can populate some fields like STDVRS with the reruried constant and can use in your receiver determination.
Regards,
Suresh

Confirm sales order with idoc ORDERS05

Hi everybody.
I´d like to know if it´s possible to confirm a sales orders with idoc ORDERS05 and message type ORDCHG and posting FM IDOC_INPUT_ORDCHG_VMI.
How would I have to fill the idoc data??
Thanks a lot

Hi,
For inbound idoc you can use the message Orders , process code ORDE and the function mdoule IDOC_INPUT_ORDERS to create a sales order.
Regards,
Nagaraj

Posting Subsequent Adjustment (MB04) with idoc WMMBXY

Hi,
I need to receive goods movement from a supplier who does subcontracting with idoc WMMBXY that contains wastes related to a specific PO. Tha waste quantities arrive at the end of production, so they're not related to a finished product quantity.
I've tried with two positions, one for mvt 121, quantity 0 for the finished product and one for mvt 543, quantity xx for the component, but the system doesn't allow me to put null quantities.
Then I've tried only with the second one, but the system blocks the post saying special stocks not supported.
Have any of you tried this management and tell me which field must be filled and how or can suggest another one way to do this with idocs?
Thank you very much for your suggestions
Anna

Ok, I've found where's the problem is.
During the checks, the system can't correlate through line_id and parent_id the connection between finished product and its components.
How can I indicate the relationship in the idoc?
Here's the point in FM MB_CREATE_GOODS_MOVEMENT where the check is done:
Analyze IMSEG for document structure and assign LINE_IDs if necessary
CALL METHOD cl_mmim_line_id_manager=>analyze_mb_create
Thanks again!

Data transfer with IDoc

Hi All,
Can any one please explain me about "Data transfer with IDoc".

Dear Prasad,
Using the IDoc option , you will not have a staging in BW like PSA were you can do corrections if required,
We can use IDOC option when we are very sure that data we are loading is error free,
and in older versions we are forced to use only IDOC option when doing hierarchy loads and its ruled out now,
Data transfer with IDoc
The data is packed into IDocs by the source system and sent to the Business Information Warehouse. In BW your data is saved persistently and intransparently in the IDoc store. From there the IDocs can be updated in the IDocs manually or automatically.
It is used for hierarchies load Limitations with IDoc is:
transfer structure must not have more than 1000 Bytes in the character format.
If it is a critical data we can use IDocs it can't be modified here. In case the load fails we need to load data from source system.
http://help.sap.com/saphelp_nw04/helpdata/en/7d/724d3caa70ea6fe10000000a114084/frameset.htm
Hope this helps u..
Best Regards,
VVenkat.
Edited by: Venkata Narayana Jakkampudi on Dec 23, 2008 12:03 PM

Add new bank account in master data client with idoc DEBMAS.

Hi friends,
I have an issue.
I am trying to add new bank account in master data client with idoc DEBMAS.
But when I submit, then just overwrite the bank data but not add.
I try playing with MSGFN code with value '009' or '004' but nothing done.
Someone has met this issue ?
Thanks for your answers.

Thanks,
But what do you mean ? where can I find this path , in img ?
Fields->Set Qualified Update ->Append Option
I think we have to use another idoc :
BUPA_C_BANKDETAIL_ADD01 SAP BP, BAPI: Add Bank Details
I'll try...

EOIO with IDOC

Similar Messages

Maybe you are looking for