To learn about Custom BOL for a Z Table Click here.

Click Here to Go thru that post to understand how to create a New component and the new view.

Pre request. A new Component and a BOL object. Use the above link to learn about that before start going forward.

OK now you have a component. Let us go thru and see how we can create a search and result views.

For search you need to have 3 views one is search view and another is result view and a third view is the View set. In this view set you combine the view one and two. We are going to use the ZTBOL as our BOL object for this example.

Component Initial Preparation for Search and Result View creation

First we need to link the custom BOL object to this Component. Go to the Runtime Repository Editor and click on the edit. Now add the ztbol to this component.  See the following screen shot.

Now the custom BOL component (ZTBOL) is added to our search and result component. Make sure you save this. 

Search View

Create a view with the MODEL Node using the custom BOL.

Now click  on the browser component structure tab and go to the ZSRCMP component. Click on the View and right click to create a view. The Create New View Wizard will popup and continue the process. See the following screen shots for the process.

The Above is the name of the View.

In the above screen you need to enter the name for the model nodes(like a abap structure name) and the BOL entity that you created during the Custom BOL creation( for more info Click here for custom BOL)

Select the TestSearchAdv structure that we need for the search view. TestResult structure will be used for the result view. Now let us go to the next screen in the wizard .  Now we need to identify the attributes fields that we need to use for this model nodes.  So go to model attributes screen. Skip the value node screen. In the Add Model Attributes to Modell Node click on the + sign to add the attributes. See the following screen shot.

To setup the jobs click here.

first setup the job as mentioned in the above link. Once the job is setup go to SM37. You should see the job that you setup in sm37. See the following screen shot.

Now the job is setup and not released.

Now select the job and enter JDBG in the command center with out /n. See the following screen shot.

Once you click enter press F7  until control goes to your Z code. This is important else you will have some issues.

* Cancelled jobs can also be debugged in this way.
But please keep in mind, this is no simulation. All updates, deletes or whatever else is done in this job will be executed !

Thanks to  Sadananda Chinnahalli  who provided this information. He is one of the best programmer that I know and very good  knowledge in SAP.

In this post let us see how to configure a new IDOC message type in the SAP system.

The Main SAP Transaction for IDOC processing is WEDI. AS soon as you go there you will see all the t-code associated with the IDOC will appear. This contains all the IDOC t-codes  from creating to processing to configuration.

Here we are going to look in to a business case and see how we can configure the IDOC and how to process the IDOC.  We have a Text file coming from a 3rd party with customer first name, last name and Age.

We need to create a new message type and store this information as idoc. Once we received this IDOC we need to process the data and load this data to a table(real life we call a SAP BAPI or sap function module normally BP create).

The text file format is as follows

First name char(20), last name char(20) and age number (3).

All of the following things are transportable. Save the transports. You can move the same config and the data from one system to another using this transport.

Create and/or Configure New IDOC segments:

T-Code is WE31.

Create a new Segment type ZTEST_CUST. See the following screen shot. 

Click create and see the following  screen shot. Now the Segment is created we are ready to create Idoc types and Message type.

Create and/or Configure New IDOC types:

T-Code is WE31.

Create a new IDOC type ZTEST_IDOC_TYPE.

Click create that will take you to the next screen. see the screen shot.

Click on the create segment. A pop-up will display. See the following screen shot. Select the created segment type and click continue.

Now click save and save the IDOC type. Now we have a IDOC structure that can have the first,last name and the age.Now let us go to the message type.

Create and/or Configure New Message types:

T-Code is WE81.

Go to the screen click on edit/change and add new entries and add a new message type ZTEST_MES_TYPE. See the following screen shot.

Now the new message type is created.

Configure the New Message type and the New IDOC Type:

 T-Code is WE82.

Now connect the Message type and the IDOC type. Go to the screen click on edit/change and add new entries and add the ZTEST_MES_TYPE ,ZTEST_IDOC_TYPE and version  as 46C or any SAP valid Version. Save the data and store the transport. See  the following screen shot.

Now Assign a function module to this new message type.

Create and/or Configure New Message types / Application Object :

T-Code is WE57.

Add the new function module to this message type so that when ever we get a new IDOC data then the SAP will call this function module where we need to put the code in for what ever process we need to do.(usually decode the idoc and validate the data and post the data in the system).

Go in to this transaction and go to change mode and add new entries. See the following screen shots.

In the new entry screen add the function module that you want to execute for this IDOC data. See the following screen shot.

Now setup the Inbound processing code. It is in WE42. Go to BD51 and add your function module.

go to WE42 and add your input processing code. See the following screen shot.

Now go to the Partner function and add this IDOC. So that for the same data type we can control what function we need to do if that comes from different partners.

Create and/or Configure Partner Profile:

T-Code is WE20.

Go to this transaction and setup this Message type to the partner that are sending the data to the SAP system. Our message is inbound so add this to the inbound parameters. See the following screen shot.

Hope this helps.  Let me know if you have any questions.

What is a IDOC?

    IDOC is a Intermediate DOCument[IDOC] that is used in SAP. The best way to import data from Any system to SAP is thru IDOC. Once the data is in the IDOC format SAP can read the information and store the data in that as IDOC which it stores in the database and will be available for processing and posting the data in the SAP system.

Each IDOC has a message type by which we can group a particular type of data by a message type and message code. We can make the IDOC process immediately by the Message type and Message code.

Let us see some basic function of how to look in to a IDOC and how the IDOC data looks and how to process the idoc.

View the existing IDOC:

use WE05 or WE02 to get the list of IDOC. In this example let us select all the message type ORDERS. Look the following Screen shot for the IDOC selection List.

Click execute the next screen will show all the IDOC for Orders in the system. I removed the date in the selection else it will select only for current day. (I created 4 order IDOCS). See the following screen shot.

Double click on the IDOC number that will take you to that single IDOC where you can see the segments of the IDOC. See the following screen shot.

Each IDOC has a segment and each segment has fields and values. SAP stores all the value information in the sdata format and when every we use this tool that will map the data and show it to us in the readable format.

Now we have the data you need to have a function module to process this IDOC. That function module can do any thing from validation this data to post the data in to the SAP system. In this example this is a Purchase order. We need to execute this idoc and post this purchase order in the system. Let us see how to execute this IDOC.

You can execute this IDOC as soon as you created by batch process or Manually using WE19 or take a existing IDOC and USE DB87 to process the idoc. Remember if you use WE19 and view a existing IDOC and process that IDOC SAP will create a NEW IDOC with the same data and process the new idoc only not the one you want to do. For processing a existing IDOC use BD87.

Create a new and Process immediately using WE19:

Click on create (F8) that will take you to the following screen. Where you need to enter all the necessary data in the segment fields.

Click on the right hand side a pop-up will show with the fields and the values (as blank) will appear. See the screen shot as follows.

Enter all the necessary values for the Order processing or the values that is minimum needed for the order processing. Once the data is entered we can process directly from here. When you process directly from here that will create the IDOC and process the data or you can just store the data.

When you click on standard Inbound or the standard outbound then the system will consider as a inbound data or outbound data and store the idoc data. If you want to process the idoc then click on the inbound function module and select the function module that you want this idoc to execute that will create the idoc and execute the function module and show you the status as success or error.

see the following screen shot.

Select the function module and click execute that will give you error or process successfully.

Process IDOC using BD87:

In bd87 you can take a existing IDOC and process. See the following screen shot. You no need to select the function module to execute. SAP will get that information from the configuration.

See the following screen shots.

select the idoc and click process that will take care of the processing.

This is how you can view or create or process a idoc.

Please click here for IDOC Configuration.

Hope this helps. Click here to find the transaction code for any modules.

Common way to get the T-CODE Information (user table TSTC) 
E*EDM*   — This will give all about the EDM in TSTC 
WE* –  All about IDOC in TSTC 
SW*  — All about Work Flow in TSTC 

Transaction Code (Generation and maintenance) Description
/nSE93     Transaction codes
 
 
Table and data objects Description
/nSE16           Table and data browser
/nSE11           Create/Maintain data Objects
/nSM30          Maintain Table Views.
/nSE14           Adjust DB Tables
Program Run and Edit Description
/nSE37                 Abap Functions
/nSE38                 Abap Reports / Programs
/nSE24                 Class Builder
/nSE80                 Abap Editor for all programs
/nSE71                 SAP Scripts
/nSMARTFORMS   Smart Forms
Abap program Debug T-Codes Description
/H if you use this code before running any program then you can debug the code step by step
/nST05       Trace the SQL statement
/nST01       SQL Trace
General – ABAP Description
/nSE91       Message Maintenance
/nSHDB      BDC Transaction Recorder
 

IDOC Edit run and select Description
/nBD87        Process IDOC
/nWE02        Select IDOC
/nWE05        Select IDOC
/nWE19       Edit IDOC

New IDOC Configuration Description
/nWEDI        IDOC and EDI Basis
/nWE81       Message Types
WE30           IDoc Types
WE82           IDoc Type / Message
WE57           Message / Application Object
WE20           Partner Profile
WE42           Inbound Process Code
WE31           IDoc Segments
 
Short Dump Description
/nST22 Dump Analysis
User Information Description
/nSU01D     User Display
/nSU53        Evaluation of Authorization Check- Display user Auth for a program or transaction
Work Flow Description
/nSWDD     Work Flow
SAP Queries Description
/nSQ01     SAP Query: Maintain queries
/nSQ02     SAP Query: Maintain InfoSet
/nSQ03     SAP Query: Maintain user groups
Transport Information Description
/nSE09     Transport organizer
/nSE10     Transport organizer
/nSE01     Transport organizer
Back Ground Jobs Description
/nSM37       Monitor Job
/nSM36       Create Job
/nSM35       Batch Input

Server Process Overview Description
/nSM50      Process overview Dialog and Background

Number Range Description
SNRO                   Number range object maintenance
SNUM                  Number range object maintenance
EN00                   IS-U print documents number range object intervals
 
Business Object Repository (BOR) – BAPI Explorer Description
/nSWO1 
ISU-BillPrint Description
EFRM             Billprint form Maintenance
EA29             Create batch job for bill print
EA60             Print documents
Data Migration Workbench – ISU Description
EMIGALL        Data Transfer from Legacy Systems for CCS
LSMW            ALL Master Data Transfer
ISU – Billing/Invoicing Description
EA00       Billing All events or Display bill document
EA40       Display print Document
EA15       Invoicing document Reversal
EA19       Creating a invoice
EASIBI      Billing and Invoicing
FPL9        Display Account payment details
FPB0        Post Payments
EA38       Create batch job for billing
EA26       Create batch job for invoice
ISU-Dunning Description
FPVA              Create batch job for dunning proposal
FPVB              Create batch job for dunning activity
FPCOPARA     Create batch job for dunning correspondence
FPM*             Dunning related t-codes
Other Transactions Description
NACE                           Conditions for output control
DMWB                          Document Modeling Workbench
ABAPDOCU                  ABAP documentation
SEARCH_SAP_MENU     Search for sap transaction codes
SLG*                             Application log transactions

Workflow Description
PFCP  General Task Maintenance
PFTC  General Task Maintenance
PFTC*  All others related to task
/nSWDC 

Transaction Code :

   This is the code which is used in SAP modules to go to a certain program and execute that code easily instead of going thru the menu. This is very helpful if certain people are doing a certain set of jobs then they can go to the process by this code.

   The short form of this is T-Code.

Look at the following example which will show you what is the t-code and how to use the t-code and how to find the t-code.

suppose I want to see a some code for a function module in the editor. We have a t-code for that with out t-code I need to go to the menu. see the screen shot for menu and t-code.

In the above screen I have to drill down 3 or 4 deep to go to that function and I need to execute. Instead of that I know the t-code (SE37) just type on the left hand top corner box (line lotus 123 command) then you no need to do all this you are right there. see the following screen shot.

I enter the t-code and click enter or click the green check mark button then I am right there.

How to find out a t-code for a program.

you can use se93 and click F4 and click on information system and search for *Function* in the description all the t-code which are related to function is displayed. With in this I can select what ever I want. See the following screen shot.

The Other way is go to SE16(table browser) and type in tstct and find the t-code. This is the table where the t-code is stored. See the following screen shot.

Hope this helps. if you have any question please let me know.