Idoc format

i have a sample asp.net project working that sends a test idoc that i acquired through examples.
the idoc is
EDI_DC40 0000000000000037249620 3012 EXCHANGE_RATE01 EXCHANGE_RATE EXCHANRBFILEPORTLS BTS2000 EXCHANSAPMBS LS BTS2000 20021014113506
E2EXCHANGE_RATE000 000000000000003724900000100000001 X
E2BP1093_0001 000000000000003724900000200000102M AED JPY 200210101.02 1 1 1.02 1 1
I am now trying to create my own SIMPLE text file for idoc EKSEKS01 I am trying to do a goods receipt transaction
I have used sap documentation from transaction we60
I am having trouble actually creating my own text file
What do i use for the idoc number?
Do i use E1PISTY segment to input the PO number and how does it look?
Do I use E1PISIT it input item number and how does it look?
Is there a way to actually create it in sap and then transport the text file to my desktop?
Any help will be greatly appreciated
Thanks in advance

Hello Janice!
This is a bit difficult to analyze remotely. I am only guessing here - but I assume that you haven't configured the ALE distribution correctly. Your IDocs cannont be sent unless you use the correct partner profile (transaction WE20) and port (transaction WE21). Then you have to send your IDocs to this partner (field EDIDC-RCVPRN in IDoc control structure).
You might find the ALE online help helpful:
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm">ALE online help</a>
Regards, Joerg

Similar Messages

Creating a flat file in the IDOC format

Hi everybody,
Need help.....urgently. Can somebody please tell me how to create a flat file in the IDOC format? I am creating a bill of lading/Documentary payments (EDI 858) and can't figure out a way to write the data generate through the report in a flat file in IDOC format. My deadline is right around the corner and I need help.
Thanks,
M

Hi Minal,
I still don't understand your question.
So, you have a report which selects data and puts it into an internal table. This part looks fine.
You want to create a flat file? Ok, to create a flat file on the application server then use the commands OPEN DATASET, TRANSFER, and CLOSE DATASET. To create a flat file on the presentation server then use the FM GUI_DOWNLOAD (or the GUI class, I forgets its name for the moment).
In both cases you should build up an internal table which has the exact structure required for your (EDIFACT?) EDI message, and then use the appropriate method to write the file.
If the following steps are manual then there is nothing more for you to do.
I don't see any need to use Idoc technology, or make any reference to it in your solution.
I hope that helps. If not, please be more specific when asking your questions.
Brad

Convert flat file to Idoc format

Due to some security reasons , the ALE scenario for material master is not allowed directly between 2 SAP systems
So the SAP system A is sending a flat file (not in Idoc format)
From SAP system B , we need to do an Inbound process to post the Idocs with following rough steps
1) Flat file upload
2) Flat file -> Idoc format conversion (EDI subsystem is not existing in this scenario and so this step has to be done within SAP)
3) Idoc processing
Even though this scenario can be accomplished without using Idocs ,
for better monitoring and reprocessing options it is required that Idocs need to be used.
Please explain the detailed steps for the above scenario

Hi,
This sounds very much lie complicating things unnecessary...Are this 2 SAP systems of the same company ?
Why would using IDOCS be more insecure then using flat files ?
If the purpose is to have a manual check before upload, you can achieve the same with IDOCS.
Please add some background to the process,
regards
Dirk

What is the IDOCs format

hi friends,
what is the IDOCs format?
where this IDOCs format comes into picture in SAP MDM?
which systems support this IDOCs format?
plz help me

Hi Rao,
IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system.
Please have a look on this link for IDoC:
http://searchsap.techtarget.com/sDefinition/0,,sid21_gci852485,00.html
1. What is the IDOCs format?
Ans: XML
2. Where this IDOCs format comes into picture in SAP MDM?
Ans: Idoc are used to interchange data from R3 to any external system or vice versa. As MDM stores different masters so that master data can come from an Idoc via Exchange Infrastructure (XI) or through MDM Generic Extractor or directly via an xml and xsd of an Idoc.
When we use XI or generic extractor in between MDM and R3 then we need to store Idocs scehma in to MDM for Idoc XML.
3. Which systems support this IDOCs format?
Ans: R3, XI, and some external third party systems support Idocs. Even MDM support Idoc XSD and XML.
Rewards if useful.
BR,
Alok Sharma

RFC - - Flat File (IDOC Format)

Hi,
I need flat file in IDOC(INVOIC02) format from the AR invoice in SAP R/3. We don't want to create IDOC's in SAP R/3. So We need to get the data from R/3 via RFC with EDIDC & EDIDD structures and map it to IDOC in XI. The second mapping would be from IDOC to Flat file.
Did anybody has done the mapping from EDIDD table to IDOC's? If so can you please share some mapping screen shots.
Thanks.
Srini

Hi,
As I have understood your scenario, you plan to send data from R3 in non-IDOC format, probably through RFC. This could be ABAP Proxy as well. And on receiver end, you need a flat structure file accepting this data.
For this case, you dont need two mappings as you mentioned. You could treat this as RFC - File scenario or Proxy - File scenario and perform the mapping accordingly.
Let me know if I have misunderstood your problem or if you need more elaboration on solution.
Thanks,
Bhavish
Reward points if comments are useful:-)

How to convert Flat file(.txt) data to an Idoc format(ORDERS05)

Hi,
How to convert Flat file(.txt) data to an Idoc format(ORDERS05). If any FM does the same work please let me know.
thanks in advance,
Chand
Moderator message : Duplicate post locked. Read forum rules before posting.
Edited by: Vinod Kumar on Jul 26, 2011 11:11 AM

Hi,
For more information, please check this link.
http://sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a
Have a look at the FM IDOC_XML_FROM_FILE. May be it helps...
Regards

IDOC to FTP keeping IDOC format

I am trying to ftp an IDOC to another server without it converting to XML format. I know there is a global setting to not convert for the IDOC adapter, but I do have 5 other scenarios that need the XML conversion. Is there a way to have a scenario that goes like the below...
IDOC -> XI -> FTP
and keep the actaul file in the IDOC format?
Thanks
Skip Ford

Hi,
have a look at this weblog to understand one
of the approaches:
/people/alessandro.guarneri/blog/2006/03/05/managing-bulky-flat-messages-with-sap-xi-tunneling-once-again--updated
the second approach is to use module IDX_XML_TO_IDOC
as described here:
https://websmp108.sap-ag.de/~sapdownload/011000358700001795162005E/HowToIDocXMLToFlat.pdf
these two should give you a good starting point:)
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI FAQ - Frequently Asked Questions</a>

ADP project - Gross Pay IDOC format - Urgent

Hi guys,
I'm working on an ADP project, and I really need to see a Gross Pay IDOC format to understand it, then, I will create a custom program to convert this format into EPIP
format.
So, I have 2 questions:
1) How SAP Created File with GROSS pay in IDOC ? Is any SAP standard program for this
2) I need a program to convert IDOC to EPIP format
If you know any thing of this please let me know ASAP, full 10 points will be given to any useful contribution. Thank you all!
Message was edited by:
Kevin Nguyen
null

Hi Venu,
Try with this code.
If vbrp-netwr = 0.
 WHEN 'E1EDP26.
CASE ta_e1edp26-qualf.
ta_e1edp26 = int_edidd-sdata.
WHEN '011'.
PERFORM append_int_edidd TABLES t_int_edidd
USING 'e1edp26'
ta_e1edp26.
int_edidd[] = t_int_edidd[].
ENDCASE.
ENDIF.
Thanks
Manju.

Conversion of EDI File format to IDOC format

We have a file in u201C.ediu201D format. We could not process this file with RSEINB00 ( IDoc inbound processing using file ) program.
1-) Could we directly do our process with this u201C.ediu201D file ? Or do we have to convert this u201C.ediu201D file to IDOC format?

If it's EDI format file (Ex: EDIFACT, X12 ...etc), we should convert the file to IDOc file by using mapping in subsystems like Gentran or TLe..etc. Conversion from edi format to idoc format will not be done in SAP.
Reddy

ADP project - Gross Pay IDOC format

Hi guys,
I'm working on an ADP project, and I really need to see a Gross Pay IDOC format to understand it, then, I will create a custom program to convert this format into EPIP
format.
If you know any thing of this please let me know as soon as possible, full points will be given to any useful contribution. Thank you all!

Here are errors:
----jGRASP exec: javac -g E:\java\Payroll3.java
Payroll3.java:33: cannot find symbol
symbol : variable payroll
location: class Payroll3
 while (payroll.hasNext())
 ^
Payroll3.java:35: inputData(java.lang.StringBuffer,DoubleClass,DoubleClass,DoubleClass,double,double,double) in Payroll3 cannot be applied to (java.lang.StringBuffer,DoubleClass,DoubleClass,DoubleClass,double,double)
 inputData(employeeName, hourlyRate, hoursWorked, taxRate, grossAmount, netAmount);
 ^
Payroll3.java:71: operator > cannot be applied to DoubleClass,double
 if (hoursWorked > FULL_TIME)
 ^
Payroll3.java:77: double cannot be dereferenced
 System.out.println(String.format("%-20s%10.2f%10.2f%10.2f%10.2f%9.2f%4s",employeeName, hourlyRate, hoursWorked, taxRate, grossAmount.getNum(), netAmount.getNum(),overTime));
 ^
Payroll3.java:77: double cannot be dereferenced
 System.out.println(String.format("%-20s%10.2f%10.2f%10.2f%10.2f%9.2f%4s",employeeName, hourlyRate, hoursWorked, taxRate, grossAmount.getNum(), netAmount.getNum(),overTime));
 ^
Payroll3.java:83: cannot find symbol
symbol : variable inFile
location: class Payroll3
 employeeName = inFile.next();
 ^
Payroll3.java:84: cannot find symbol
symbol : variable inFile
location: class Payroll3
 hourlyRate = inFile.nextDouble();
 ^
Payroll3.java:85: cannot find symbol
symbol : variable inFile
location: class Payroll3
 hoursWorked = inFile.nextDouble;
 ^
Payroll3.java:86: cannot find symbol
symbol : variable inFile
location: class Payroll3
 taxRate = inFile.nextDouble;
 ^
Payroll3.java:87: double cannot be dereferenced
 grossAmount.setNum();
 ^
Payroll3.java:88: double cannot be dereferenced
 netAmount.setNum();
 ^
11 errors
----jGRASP wedge2: exit code for process is 1.
----jGRASP: operation complete.

How to send delivery status by idoc format from EWM system?

Hi gurus,
You know we can send GR(posted) from EWM to R3 system, while in our scenario, we also need to send inbound delivery status( including posting, posted) from EWM to Non-SAP system via PI.
Can we implement that by idoc? Do we have to use PPF? How to develop in PPF to send message to PI?
Thanks in advance.

Hi kishore,
Thanks for your reply.
I tried to find how SPPFCADM send idoc in ther relevant method, but you know it's just some object oriented code which is not easy to understand and I couldn't find where send idoc and where can be enhanced.
I found that /SCWM/ERP_MAPOUT is the implementation name for the method of inbound delivery to ERP system, also there is an action "XI Message:lieferinfo:inbound delivery", can it be used to send idoc to PI/XI system?
Thanks.

Inbound IDOC Format (Flat File)

Hi,
I'm using SAP CRM Middleware for communication between CRM and Legacy System.
I have configured Outbound IDOCs and I see something like this:
EDI_DC40 2200000000000000023700 3012 CRMXIF_PARTNER_SAVE_M01                                     CRMXIF_PARTNER_SAVE_M
E201CRMXIF_PARTNER_COMPLEX000 220000000000000002300000100000001CRMXIF_PARTNER_COMPLEX
E201CRMXIF_PARTNER_HEADER000 220000000000000002300000200000102CRMXIF_PARTNER_HEADER         BusinessPartner                 U
E201CRMXIF_PARTNER_KEYS000    220000000000000002300000300000203CRMXIF_PARTNER_KEYS           0000000014488DDB8AD891249EE10080010A6CA883
The questions are:
I need to know how do the following information must be filled in an Inbound IDOC:
The first characters I understand that corresponds to the Structure name, IDOC Number, IDOC Line...
So I need how do fields like IDOC number must be filled in an Inbound IDOC
Thanx in advance..
BTW. I'm expecting IDOCs as flat files so I need to explain to the Legacy Technician how to fill this fields.

Hi,
Go to transaction WE30 and give the IDoc basictype name CRMXIF_PARTNER_REL_SAVE_M01 and press the view-button (or press F7 key).
This information you will need.
The records are builded using the following structure:
1st record contains control record information and follows the structure of table EDIDC.
Starting at where "220" is given (this is the CLIENT), it is followed by the IDoc number field DOCNUM (16 digits) and so on. Not all fields must be filled, only those that are used for inbound messaging. Keep here in mind: Less fields filled will probably work better (because SAP will add its own details on arrival of the IDoc).
All following records follow the structure of table EDID4 upto the field: HLEVEL (Hierarchy level, identical to the level found in WE30).
Thereafter it is followed by the name of the segment (including spaces) and after this it will follow the exact structure of the segment.
To view a sample, just generate a dummy (test) IDoc and use transaction WE19 to fill in the fields after changing to the correct IDoc type.
Hope this helps you out.
Regards,
Rob.

IDOC format for ORDERS05

Hi all,
I have search through the web and in sap.com and I haven´t found the specification (details of fields and their meanings) for the standart idoc ORDERS05.
Does anyone on the forum knows where i can find this information?
(I have no access to a SAP system).
Thanks for all.

Structure of basic type ORDERS05
Purchasing/Sales
E1EDK01 : IDoc: Document header general data
Status: Required , min. number : 1 , max. number : 1
Structure
E1EDK14 : IDoc: Document Header Organizational Data
Status: Optional , min. number : 1 , max. number : 12
Structure
E1EDK03 : IDoc: Document header date segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK04 : IDoc: Document header taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK05 : IDoc: Document header conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDKA1 : IDoc: Document Header Partner Information
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKA3 : IDoc: Document Header Partner Information Additional Data
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDK02 : IDoc: Document header reference data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDK17 : IDoc: Document Header Terms of Delivery
Status: Optional , min. number : 1 , max. number : 4
Structure
E1EDK18 : IDoc: Document Header Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDK35 : IDoc: Document Header Additional Data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDK36 : IDOC: Doc.header payment cards
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKT1 : IDoc: Document Header Text Identification
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDKT2 : IDoc: Document Header Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDP01 : IDoc: Document Item General Data
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDP02 : IDoc: Document Item Reference Data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1CUREF : CU: Reference order item / instance in configuration
Status: Optional , min. number : 1 , max. number : 1
Structure
E1ADDI1 : IDoc: Additionals
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDP03 : IDoc: Document Item Date Segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDP04 : IDoc: Document Item Taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDP05 : IDoc: Document Item Conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDPS5 : A&D: Price Scale (Quantity)
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDP20 : IDoc schedule lines
Status: Optional , min. number : 1 , max. number : 9999
Structure
E1EDPA1 : IDoc: Doc.item partner information
Status: Optional , min. number : 1 , max. number : 8
Structure
E1EDPA3 : IDoc: Document Item Partner Information Additional Data
Status: Optional , min. number : 1 , max. number : 99
Structure
E1EDP19 : IDoc: Document Item Object Identification
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDPAD : A&D: Material Exchange
Status: Optional , min. number : 1 , max. number : 1
Structure
E1TXTH1 : General Text Header
Status: Optional , min. number : 1 , max. number : 1
Structure
E1TXTP1 : General Text Segment
Status: Optional , min. number : 1 , max. number : 100
Structure
E1EDP17 : IDoc: Document item terms of delivery
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDP18 : IDoc: Document Item Terms of Payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDP35 : IDoc: Document Item Additional Data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDPT1 : IDoc: Document Item Text Identification
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDPT2 : IDoc: Document Item Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDC01 : SS: Service specifications general data
Status: Optional , min. number : 1 , max. number : 9999999
Structure
E1EDC02 : SS item: Reference data
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC03 : SS item: Date segment
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC04 : SS item: Taxes
Status: Optional , min. number : 1 , max. number : 10
Structure
E1EDC05 : SS item: Conditions
Status: Optional , min. number : 1 , max. number : 16
Structure
E1EDC06 : Service line formula fields
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDC07 : Service line user fields
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDCA1 : SS items: Partner information
Status: Optional , min. number : 1 , max. number : 8
Structure
E1EDC19 : SS items: Object identification
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDC17 : SS items: Terms of delivery
Status: Optional , min. number : 1 , max. number : 5
Structure
E1EDC18 : SS items: Terms of payment
Status: Optional , min. number : 1 , max. number : 3
Structure
E1EDCT1 : SS items: Text identification
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1EDCT2 : SS items: Texts
Status: Optional , min. number : 1 , max. number : 9999999999
Structure
E1CUCFG : CU: Configuration data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUINS : CU: Instance data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUPRT : CU: part-of data
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUVAL : CU: Characteristic valuation
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1CUBLB : CU: Configuration BLOB (SCE)
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDL37 : Handling unit header
Status: Optional , min. number : 1 , max. number : 999999
Structure
E1EDL39 : Control Segment for Handling Units
Status: Optional , min. number : 1 , max. number : 9
Structure
E1EDL38 : Handling Unit Header Descriptions
Status: Optional , min. number : 1 , max. number : 1
Structure
E1EDL44 : IDoc: Handling Unit Item (Delivery)
Status: Optional , min. number : 1 , max. number : 99999
Structure
E1EDS01 : IDoc: Summary segment general
Status: Optional , min. number : 1 , max. number : 5

IDoc file format that corresponds to BAPI_ACC_DOCUMENT_POST

I have developed an ABAP program that reads data from a file exported from a non-SAP system and post G/L documents in SAP with BAPI_ACC_DOCUMENT_POST.
Now, I would like to rewrite the interface with corresponding IDoc. What is the inbound IDOC format file, which corresponds to BAPI_ACC_DOCUMENT_POST. Can you explain how to write this file?
Best Regards
Serena
Moderator message: please do more research before asking, show what you have tried so far when posting.
Edited by: Thomas Zloch on Jan 24, 2012

Hi Dewang,
I'm not sure what the reason behind the different exchange rate, but from what I understand, most of our treasury transaction using flat rate. meaning, they agree and sign contract with bank to use certain rate for a range of period. so, during that period, all the posting will use this flat rate instead of SAP TCURR.
I have tried to manipulate the internal table for currency amount for afew scenario but still cannot pass the exact rate and the amount for document and local like what in upload file. my last choice is to use BDC, but for recording wise, hard for me to simulate for all scneario; WHT, additional info, cost center etc.. fyi, I have tried to create simple BDC for txn F-02 and it is working for my case: passing exact exchange rate, doc amt and locl amt.
i still hope for the BAPI to cater for my case, sure got hidden technique or tips to manipulate the exchange rate.
for those who want to help, you may use below upload sample:
COMP DOC_TYPE DOC_CURR DOC_AMT LOCL_CURR LOC_AMT EXCHANGE_RT POSTING_KEY
A200 KR USD 100 RM 321.56 3.33 31

IDOC file format supported ? but how?

hi all,
i am trying to achieve to read an idoc file with soa suit. but i can not find how to handle this data structure.
can anyone give me a hint to documentation where this is described?
regards chris

hi manoj,
in our environment we are used to changing IDOC structures one a almost daily basis.
iway has two crucial problems for us:
1) it is not possible to receive generic idocs as IDOC_INBOUND_ASYNCHRONOUS s SAP designed it supports. idocs that are received by iway therefore always must be typed and "well known" by the receiver. so iway is not idoc agnostic and is not able to update its idoc structures without rebooting to get the format "well known". as far as we understand it. for us having to reboot a SOA system on a almost daily basis that should be 99.999 % available is not an option. at least for us.
2) iway is very lets say work intensive for configuration/administration if you have to deal with let's say 30 -100 SAP systems.
therefore we think about not using iway at all but doing everything by file (IDOC format EDI) and hope to at least get rid of point 2. if we get rid of point 1 is still open to the implemenation of the third party library.
regards chris

Idoc format

Similar Messages

Maybe you are looking for