IDOC Information on IFR


SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

 

As I was writing my 3-Part Series of weblogs, I discovered I needed information on a specific field of an IDOC. As you may recall, I mapped an Open Applications Group (OAG) ProcessPurchaseOrder BOD to an SAP ORDERS.ORDERS05 IDOC. Of course, if you have access to an SAP ERP system, you can go directly to transaction WE60. One other means of getting some IDOC information when access to an SAP ERP system is not convenient, is via the IFR. (http://ifr.sap.com).
In the end, I wanted more information on the field ACTION on the E1EDP01 segment.
Here’s how to get there:

SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

  1. Navigate to the http://ifr.sap.com/
    image
  2. Click the Enter link…
  3. Select Components Tab
  4. Expand the SAP LO (Logistics) node.
    image
  5. Select your specific release (ex: Release 46C)
  6. Select Electronic Data Interchange (EDI)
  7. Select ORDERS
    image
  8. Select ORDERS05
  9. Navigate to the Segment E1EDP01
  10. Read the Definition of the ACTION Field
    image

So now you know what the field means, unfortunately, the IFR does not have the code list of permitted values for the fields that are defined.
image
So, the IFR is particularly useful if you want to clarify the definition of a specific IDOC field. Unfortunately, for clarification on the permitted/valid values for these fields you’ll have to go to your trusty old ERP system.

UPDATE 01.11.2007: Please see this blog. The IFR has been retired in 2007.

SAP PI Interview Questions and SAP PI Tutorials

SAP PI Interview Questions and SAP PI Tutorials

Share this:
Share this page via Email Share this page via Stumble Upon Share this page via Digg this Share this page via Facebook Share this page via Twitter
en.pdf24.org    Send article as PDF   
This entry was posted in Uncategorized. Bookmark the permalink.

Leave a Reply

Your email address will not be published. Required fields are marked *