idoc format

[Former Member]

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

[Former Member]

Hi Janice,

My best guess would be to try it the other way around. Create a file send port in the SAP backend system, use WE19 or a similar transaction to generate an IDoc of the required type and send it to that port.

This process should create a text file in the required format. You can then analyze it and simply exchange the data as needed.

Also, I do not think you can submit an external IDoc number (at least in JAVA, you can't). The IDoc number is an internal number as far as I know. I am not shure whether you would need to supply one - but I'm afraid you'd have to test that.

Hope this helps, Joerg

[christian_wohlfahrt]

Hi Janice!

Basically you don't start with a file - it's horror to type all the spaces to match the structure manually.

Either start (as Joerg already said) with an outbound or start from scratch in WE19 or write a small report, where you have access to the SAP structures.

With IDOC_INBOUND_SINGLE you can simulate the inbound interface for every IDOC.

But most important: use IDOC MBGMCR02 or MBGMCR03, depending on your release. EKSEKS01 is something else, but goods movements are definitely done with MBGMCR02 or BAPI_GOODSMVT_CREATE.

Regards,

Christian

[Former Member]

thank you guys so much

i actually created the idoc with we19 and this works great

one question though

how do i export it as a text file so that it is in idoc format

when i export as a rich text format i get a report not an actual idoc text file

[Former Member]

Hi Janice!

Just use transaction WE21 to create a new file send port. There you can enter a file name and directory where the IDoc subsystem will place your file.

You can use a FM to create a filename with a timestamp etc.

Hope this helps,

Joerg

[Former Member]

Hi Joerg

i created a file send port called INTERNAL that points to a d:\idocs area that is a shared folder.

when i run transaction we19 the try idoc(i am trying ekseks01 for now may have to change the idoc per above)

i push the inbound file button and i get the following

idoc saved to file and idoc and file forwarded to idoc inbound processing but i do not see the file in the d:\idocs area.

am i supposed to do the inbound file or outbound processing and should the file be in the d:\idocs area

[ferry_lianto]

Hi Janice,

I don't think so you can send the IDoc to desktop/PC server. It has to go to application server i.e UNIX then you can browse the IDoc file using transaction code AL11.

Regards,

Ferry Lianto

[Former Member]

that is the application server

there is a folder called idocs on the application server in d

i map a network drive there and i can see my other files but not that one

is that where it is going since i have the port internal set up to point to d:\idocs file name abc.txt

also i tried to use al11 to look but i do not know how to get to the d:\idocs folder

[ferry_lianto]

Hi Janice,

Would you be able to do 'Access Test' (Outbound File tab) in transaction WE21 for directory d:\idocs ?

If you are able then SAP should be able to generate IDoc file in above directory otherwise you may try to pick any directory from AL11 (make sure you acccess) and replace d:\idocs with it then do testing again via WE19.

Regards,

Ferry Lianto

[Former Member]

when i try to access in we21 it says access to directory possible from current application server so i assume that it is okay

i think when i try to send it gives an error

so maybe this is why not send

thank you

[Former Member]

Hello Janice,

I think there might be a problem with the distribution model and/or the partner profile. Have you checked the IDoc trace / status transactions whether the IDoc is actually sent correctly?

Regards, Joerg

[Former Member]

Hi..

Use transaction WE14 to convert Idoc to file at the location specified in WE21.

You can then view the file in AL11.

If you want it on your desktop you can download the file from application server using Tcode CG3Y.

Hope this helps you..

Meena

[Former Member]

hi

i am still confused

in we02 selected idocs is see idoc number 630789 with status 37 which is idoc added correctly but it says entry in outbound table not found what is that?

the direction is outbox and the port is internal which is the name of the file port that i described in we21 which should be the d:/idocs folder.(on the application server)

since it is added correctly should not it be in my d:/idocs folder as a text file?

also in transaction we14 is says no idoc is ready for processing how can i get it ready?

[Former Member]

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 <b>WE20</b>) <i>and</i> port (transaction <b>WE21</b>). Then you have to send your IDocs to this partner (field <b>EDIDC-RCVPRN</b> 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

[Former Member]

okay i do not have the partner set up

so i went to transaction sale and set up

ls type partner abc01 and abc02(i go back and see them in the list)

now i go into we20 and go under ls partner types and i do not see them so i guess i missed something i think what i need to do is to tell the partner abc01 to be able to use message type eksek but i guess i do not know how

can you direct me

thank you soooooooooo much

[Former Member]

Hi Janice!

To cut things short - could you just make some hardcopies of the settings in transaction <b>WE20</b> and <b>WE21</b> and send them to me? Please use the eMail adress <u>joergloosen(at)hotmail.com</u>.

I'll have a look at it.

Regards, Joerg