Essential SAP IDoc transaction codes

Essential SAP IDoc transaction codes are primarily located under the WE transaction prefix, focused on monitoring, testing, and administration. Key tcodes include WE02/WE05 for displaying IDoc lists, WE19 for testing/debugging, and BD87 for reprocessing failed IDocs. 

Key IDoc Transaction Codes

• WE02 / WE05: Display/List IDocs (Most commonly used)
• WE19: IDoc Test Tool (Create/edit/debug)
• BD87: Reprocess failed IDocs (Status Monitor)
• WE20: Partner Profiles (Configure EDI/ALE)
• WE09: Search for IDocs by content/segment
• WE11: Delete IDocs
• WE21: Ports definition 

IDoc Administration & Development

• WE30: IDoc Types (Define structure)
• WE31: Create IDoc Segments
• WE81: Define Logical Message Types
• WE82: Assign Message Type to IDoc Type
• WE41/42: Inbound/Outbound Process Codes
• WE57: Assign FM to Log. Message and IDoc Type 

Master Data Sending (ALE) 

• BD10: Send Material
• BD12: Send Customer
• BD14: Send Vendor
• BD21: Create IDoc for Change Pointers
• BD64: Maintain Distribution Model 

Other Useful Tcodes

• WE06: Monitor Active IDocs
• WE07: IDoc Statistics
• WE60: Documentation for IDoc Type
• SALE: ALE Implementation Guide

How to run ABAP Z Transaction from SAP Fiori

Calling ABAP Z Transaction (ZQM_INSP_LOT) from SAP Fiori

This launches the transaction inside a Web Dynpro/GUI wrapper directly from the Fiori tile.

Steps:

Step 1 – Create a Target Mapping in FLP

1. Go to SAP Fiori Launchpad Designer (transaction /UI2/FLPCM_CONF)
2. Set the Transport request number. 
   Go to rupper right corner and foun CLIENT ALL. Click the setting
   
   
   
   
   
   
   
   
   
   
   
   Assign TR number
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
3. Navigate to your catalog → click "+" to add a Target Mapping
   Create Catalog.
   go to left lower corner
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
4. Configure Target Mapping
   Click Target Mapping
   
   
   
   
   
   
   
   
   
   
   Click lower menu 'Create Target Mapping'
   
   
   
   
   
   
   
   
   
   
5. Fill in:
   • Action: e.g. display
   • Semantic Object: e.g. ZQMInspLot
   • Application Type: Transaction
   • Transaction: ZQM_INSP_LOT

Step 2 – Create a Tile

1. In the same catalog, add a new tile
   
   
   
   
   
   
   
   
   
   

   Click 'App Launcher - Statis'
   
   
   
   
   
   
   
   
   
   
2. Set the Navigation Target to the semantic object + action you defined above
3. Give it a title, icon, and subtitle
   
   
   
   
   
   
   
   

Step 3 – Assign to a Group/Role

1. Create Group
   
   
   
   
   
   
   
   
   
   
   
   Click the Plus sign on lower left
   Name the group
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
2. Add catalog
   
   Double click on plus sign to add catalog
   
   
   Add the catalog 
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   

   

   
   
   
   
   
   
3. Assign the catalog to a Fiori role in transaction PFCG
   
   
   
   
   
   
   
   
   
   
   
   

   

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   

   

   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
4. Don't forget to add the User ID in tab User
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
5. Publish and transport

Step 4 – Test

1. Open the Fiori Launchpad
2. Find your tile and click it — it will open ZQM_INSP_LOT wrapped in a UI5 shell

SAP Fiori T-Codes You Should Know

 

SAP Fiori T-Codes You Should Know

Custom Print Program of T-Code F.62 (Print Journal Voucher)

Question:

I need to modify the data and the layout of transaction F.62 (Print Journal Voucher).  I have searched information from the web that it is possible to add a custom print program to modify the logic.  I would like to ask what is the transaction code in FI for configuring this Tcode F.62 to use this customize print program. (Like NACE for SD and MM modules). 

Answer:

Transaction OB98

SE38 for program ZFIRGB_0001 

SE71 for the SAPScript Form

How to Download Files from AL11?

SCN (SAP Community Network) regularly receives the question: how can be files downloaded from the R/3 server via transaction AL11?

Unfortunately there are no standard transactions or reports which could provide such functionality, but there are some "workarounds" which can help with that.
Let's not forget: transaction AL11 just shows the files available on the server, therefore the "workarounds" are simple: let's look for programs which allow downloading files from the server to the front end!

The following chart shows a simplified flow how you can find the ideal download tool - then you can read further information below.

Point 1 - First you need to find out whether component EA-APPL is installed on the SAP system.

This component provides some ready-to-use tools which you can use to easily download files.

The easy way to find this out is to go to menu System -> Status... in any window, then select button "Component information". If EA-APPL is installed, you can see it in the appearing list.

You can see an example here:

The "hard way" is to go to transaction SPAM and press button Package level. You can see EA-APPL here too if it is installed.

For example:

Point 2 - Use transaction CG3Y.

This transaction is easy to use: you just need to enter the path of the required file and the path where the file should be downloaded to the front end. Simple as that! Here is an example:

Point 3 - Use program CACS_FILE_COPY.

You can start it via transaction SE38 or SE80. In the program you can select "Applicn on Presentation Server", and set the Source and Target Files.

E.g.:

Point 4 - Download the file as a simple list.

When you open the file in transaction AL11, you can download it as a simple list via menu System -> List -> Save -> Local file (see the following image).

You can select "unconverted" to save the data as a regular file, or "spreadsheet" to save the data which can be used in Excel.

Point 5 - Problem: downloaded files are truncated.

When you save the file with the method from Point 4, it may happen that the files are truncated.

Read Wiki http://wiki.scn.sap.com/wiki/x/LIH-FQ for the solution.

Point 6 - Use function module ARCHIVFILE_SERVER_TO_CLIENT.

This is an unreleased function module which can be started from transaction SE37. Since this function module was intended for SAP-internal purposes, results may vary.

Starting ARCHIVFILE_SERVER_TO_CLIENT via testing in transaction SE37 looks like this:

Point 7 - Write your own program on OS level.
Unfortunately this point lies far outside the boundaries of this guide: this solution depends on the OS editions, used network protocol, firewall/security settings, etc.
This guide can't help here - however, the other Spaces on SCN might be a good place to start to collect ideas.

Ref: http://scn.sap.com/docs/DOC-55795