Using the IDoc file interface to read and write an IDoc from a directory

Axel Angeli, Logosworld

Published: 23 Apr 2004

In order to use the IDoc file interface to read and write an IDoc from a directory, I already have configured the...

Step 2 of 2:

You forgot to provide an Email Address.

This email address doesn’t appear to be valid.

This email address is already registered. Please login.

You have exceeded the maximum character limit.

Please provide a Corporate E-mail Address.
- I agree to TechTarget’s Terms of Use, Privacy Policy, and the transfer of my information to the United States for processing to provide me with relevant information as described in our Privacy Policy.
Please check the box if you want to proceed.
- I agree to my information being processed by TechTarget and its Partners to contact me via phone, email, or other means regarding information relevant to my professional interests. I may unsubscribe at any time.
Please check the box if you want to proceed.

port (WE21) with: * physical directory (internal SAP) * inbound file

My question is, which function module do I have to choose at this screen or I should leave this option blank? I read that EDI_PATH_CREATE_CLIENT_DOCNUM was the best option, but I'm not sure.

Besides the file must be in any kind of file in particular (for example txt) or not.

The function module simply determines how the file name is created. You can create the filename from the DOCNUM (as above) or create it from the actual time stamp or give it a constant value. That is your proper decision which fits best in your application. The resulting file will always contain plain ASCII text with fixed record length. The file suffix (extension) depends on the requirement of your operating system. E.g. for Windows the recommended suffix would be indeed .DAT or .TXT, that allows you to easily open the file in a text editor, but if you give a fancy name like .IDOC it does not really make a difference, as long the receiving app understands it. Reading IDocs from a file is done via ABAP RSEINB00.

IDoc (intermediate document)

IDoc validation; populating in error tables from IDoc

IDocs for purchasing contracts

Blank value fields in IDocs

Please create a username to comment.

7 hurdles to using AI in accounting and finance

Take care of ERP data security when moving to the cloud

Solid growth helps IFS ERP take aim at top-tier vendors

Oracle Autonomous Database shifts IT focus to strategic planning

Oracle Autonomous Database features free DBAs from routine tasks

Oracle co-CEO Mark Hurd dead at 62, succession plan looms

Oracle Data Science efforts advance with new services

Data governance metrics: Data quality, data literacy and more

Snowflake raises $479 million to boost cloud data warehouse

Amazon grocery strategy could shake up food retail industry

Amazon's environmental impact delivers climate change concerns

New themed Amazon pop-up stores built on consumer data

MicroStrategy analytics suite fosters insurance co-op's growth

Yellowbrick Data, MicroStrategy partnership aims to enhance analytics

Ethical data collection in the spotlight over new regulations

Test yourself on the differences between SharePoint and OneDrive

Akeneo rolls out newest version of PIM software

Get to know 4 workflow automation tools

8 HR technology trends CHROs should investigate in 2020

How to attract top talent in a competitive hiring market

Federal workforce too reliant on degrees, says White House

Dig Deeper on SAP integration

IDoc (intermediate document)

IDoc validation; populating in error tables from IDoc

IDocs for purchasing contracts

Blank value fields in IDocs

Related Q&A from Axel Angeli

Start the conversation

0 comments

Register

Login

Forgot your password?

Your password has been sent to:

Please create a username to comment.