The above screen shows all the recording until now.

In the BDC process first you have to record the session. This collects all the t-code , input screens and variables etc,. for creating a program. Once the recording is completed you need to create a program or a  function moudle from the recorded session.  Then you can go inside the program and change the code to what ever way you want. This is a very easy way of creating a batch input mode.  Let us see one example how this works.

Let us assume the we have 10 BP records and we use BP t-code that we need to give input from a text file.

Recording:

Click on new recording on the above screen.  A pop up asks the details. See the following screen shot.

I selected the BP transaction.  Now click on the Start recording. It takes me to the Bp screen. I click on the person to create a person. See the following screen shots.

I just enter the first name and last name and click save. See the following screen shots. The control takes me back to the recording.

You can follow him at @ :  http://twitter.com/juanpedrov

His documentation goes as follows.

Finally let me tell you that in part got based in the explanation of this article: https://www.sdn.sap.com/irj/scn/wiki?path=/display/CRM/How+to+display+a+z-table+in+an+assignment+block

That article explain how to display a z table without using all the BOL concept that I’d like to understand. I tried to used a standard BOL (PRPAdvSearch) but it didn’t work. Maybe I should try creating my own BOL, maybe next time.

Overview: This document pretends to show how to add a new view at the BP_ACCOUNT factsheet. In particular, for this example, a table with the information of PPR (partner product rage) for a particular business partners (the one at the factsheet).

• 1) Create z structure and table with the fields needed to show at the factsheet

• 2) Create a new component

• 3) Add BP_APPL model at Runtime Repository Editor

• 4) Create a view with:
• a. BuilHeader model node.
• b. Value node.
• c. Model attributes: for this example only the BP number.
• d. Value attributes: select the fields wanted to show, indicate the z structure created at step 1.
• e. Select table type “Table view” with the value node.

 The usual way of programming is serial processing. The program executes one line at a time and if you call a function that will wait until the control returns from the function and executes the rest of the code. In some case you might be calling the same function again and again for different set of master data. You know that there wont be any conflict between the data and you would like to execute the same function multiple times with different set of data. We need to do this in parallel processing this way the process will be completed much faster with multiple processes in different servers. Let us see how we can achieve this with an example.

 Let us assume that we have 1 million BP and we need to check some condition and set a value Y or N according to that condition and this code is in a Z function which get input of 1000 BP at a time. Let write a program which can execute the same function multiple time until the process is ready.

I created a report in SE38 with name as  Z_TEST_PARALLEL .

 First we need to get the number of max resources available and number of resources free using the following sap standard function. Only initialize only once and next times use the SPBT_GET_CURR_RESOURCE_INFO function to get the available resources.
   SAP Function ‘SPBT_INITIALIZE’

    This will give you the information that we need to do the parallel processing. Now loop thru the data and gather the information that you want to process let us say like 1000 bp at a time and execute the z function with 1000 bp at a time. once you reached the max number of resource you need to wait until some resource is available and if the resource is available then continue and wait until all the process is completed. 
You have to call the function not using the regular call but using the new task call. See the following
CALL FUNCTION ‘Z***(your function name)’
      STARTING NEW TASK taskname
      DESTINATION IN GROUP srv_grp
      PERFORMING return_back_this_task
      ON END OF TASK
      EXPORTING
        …………………..
      TABLES
        ………………….
      EXCEPTIONS
        resource_failure      = 1
        system_failure        = 2
        communication_failure = 3
        OTHERS                = 4.
 

                                    The above function is called in the new task which process in a separate session. You call the above function multiple times with 1000 records at a time and wait for the process to be completed. On each task is completed the return_back_this_task perform is executed and the result will be received from that task. Once all the results are collected the process will be completed and the control will return back to the main program. See the following sample code for parallel processing.

To learn how to create search and result view Click Here.

Once you know created the search and result view now we need to create a search button. I added the following code in the srviewset.htm.

<%@page language=”abap” %>
<%@extension name=”htmlb” prefix=”htmlb” %>
<%@extension name=”xhtmlb” prefix=”xhtmlb” %>
<%@extension name=”thtmlb” prefix=”thtmlb” %>
<%@extension name=”crm_bsp_ic” prefix=”crmic” %>
<%@extension name=”bsp” prefix=”bsp” %>
<%@extension name=”chtmlb” prefix=”chtmlb” %>
<%
***  Determine if search is to be collapsed
DATA lv_show_fields TYPE string.
“  lv_show_fields = ’X’.
“  IF lv_show_fields EQ abap_false.
lv_show_fields = ‘true’.
“  ELSE.
“ lv_show_fields = ’false’.
“  ENDIF.
%>
<chtmlb:pageType type=“SEARCH” >
<thtmlb:searchFrame showSearchFields   = “<%= lv_show_fields %>”
onShowSearchFields = “TOGGLESEARCHDISPLAY”
onHideSearchFields = “TOGGLESEARCHDISPLAY” >
<thtmlb:searchCriteriaFrame>
<%
“  IF lv_show_fields EQ abap_false.
%>
<thtmlb:searchArea>
<thtmlb:searchTagArea>
<bsp:call comp_id = “<%= controller->GET_VIEWAREA_CONTENT_ID( ’SV’ ) %>”
url     = “<%= controller->GET_VIEWAREA_CONTENT_URL( ’SV’ ) %>” />
</thtmlb:searchTagArea>
<thtmlb:searchButtonsArea>
<thtmlb:button id = “SearchBtn”
design  = “EMPHASIZED”
onClick = “SEARCH”
text = “Search”
tooltip = “Search” />
<thtmlb:button id = “Clearbtn”
onClick = “CLEAR”
text = “Clear”
tooltip = “Clear” />
</thtmlb:searchButtonsArea>
</thtmlb:searchArea>
<%
“Endif.
%>
</thtmlb:searchCriteriaFrame>
<thtmlb:searchResultFrame>
<bsp:call comp_id = “<%= controller->GET_VIEWAREA_CONTENT_ID( ’RV’ ) %>”
url     = “<%= controller->GET_VIEWAREA_CONTENT_URL( ’RV’ ) %>” />
</thtmlb:searchResultFrame>
</thtmlb:searchFrame>
</chtmlb:pageType>

With the above html I added the search button on the viewset. The button code is placed in between the view.

See the following screen shot for the button.

Now we have the button. We need to add the search event on the viewset as well as in the search view. See the following screen shots for event creation.

Add the following code in the searchadv view on the event handler.

METHOD eh_onsearch.
DATA: query_service TYPE REF TO cl_crm_bol_dquery_service.
DATA: result TYPE REF TO if_bol_bo_col.

query_service ?= me->typed_context->TestSearch->collection_wrapper->get_current( ).
result = query_service->get_query_result( ).

me->typed_context->testresult->collection_wrapper->clear( ).

me->typed_context->testresult->set_collection( result ).
ENDMETHOD.

Once the code is added  your component should trigger when ever you click on the search and get the result and show in the result view.

Now we need to add some code in the DO_HANDLE_EVENT method of the implementation class of srviewset view. In that method you are asking the event to be raised for the searchadv view, so that the code in the advsearch will be called. You can directly put the code in the viewset so you no need to do the above.

Add the following code in the DO_HANDLE_EVENT method of the ZL_ZSRCMP1_SRVIEWSET_IMPL.

METHOD do_handle_event.
* Eventhandler dispatching
DATA: lv_viewname TYPE string,
lr_viewctrl TYPE REF TO cl_bsp_wd_view_controller.
CASE htmlb_event_ex->event_server_name.

*     Added by wizard
**      WHEN ’SEARCH’.                                        ”#EC NOTEXT
*        EH_ONSEARCH( htmlb_event    = htmlb_event
*                    htmlb_event_ex = htmlb_event_ex ).

WHEN OTHERS.
lv_viewname = me->get_viewarea_content( ‘SV’ ).       “#EC NOTEXT
IF lv_viewname IS NOT INITIAL.
lr_viewctrl = me->get_subcontroller_by_viewname( lv_viewname ).
IF lr_viewctrl IS BOUND.
TRY.
CALL METHOD lr_viewctrl->(‘DO_HANDLE_EVENT’)
EXPORTING
event = event
htmlb_event     = htmlb_event
htmlb_event_ex  = htmlb_event_ex
global_messages = global_messages
RECEIVING
global_event    = global_event.

CATCH cx_sy_dyn_call_error.
RETURN.
ENDTRY.
ENDIF.
ENDIF.
ENDCASE.

ENDMETHOD.

Now your code is ready to execute had show the results. See the following screen shot.

Now you get the result in the result view. Let me know if you have any questions.

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.

In this post let us see how we can create custom webic component.

Go to the workbench using the t-code BSP_WD_CMPWB. See the screen shots.

Now  create a ztestcmp as follows.

Click OK and it will ask for the package and transport to store the information in the system. Just go thru that and give the necessary information according to your system.

Once your component is created just click on test you should see your component launch on the browser. If there is no issue you should see an empty screen. See the following screen shot.

 Now let us create a view with some input like first name , last name and city of birth and  display the input on the screen.

Let us create the first view(fview). Right click on the views and click create a wizard will popup. See the following screen shot.

If we create a view in the web ic the view will look like as follows.

You have only two tabs on the right hand side of the screen. This way you cannot do a drag and drop the field in the screen. You need to make the screen configurable. There is no check box or any radio button that you can click and make them config. You have to go in to the HTML code and add some code that will make them config.

Double click on the fview .htm file. That will take you to a html editor. See the following screen shot.

Replace the above code with the following code.

<%@page language=”abap” %>
<%@extension name=”htmlb” prefix=”htmlb” %>
<%@extension name=”xhtmlb” prefix=”xhtmlb” %>
<%@extension name=”crm_bsp_ic” prefix=”crmic” %>
<%@extension name=”bsp” prefix=”bsp” %>
<%@extension name=”chtmlb” prefix=”chtmlb” %>
<%@extension name=”thtmlb” prefix=”thtmlb” %>
<%
  DATA:
  lv_xml    TYPE string.
  lv_xml = controller->configuration_descr->get_config_data( ).
%>

<chtmlb:overviewFormConfig xml  = “<%= lv_xml %>”
               mode = “RUNTIME” />

Now activate this html and double click on the view name. You should able to see different tab with name as configuration. see the screen shot below.

 Now click on the new configuration and click on the show avaliable fields that will show all the fields avaliable to add to the screen. See the screen shot.

To see all the jobs that is in the SAP system use SM37 see the screen shot below.

Here you can search by Job name or the user who created the job or if you know the SAP report name (Program Name)  you can look in to the job. As soon as you setup the job the job will be in the scheduled state. As soon as the time comes(you assigned time for the job execution) the job will change in to released and it will show active and show as finished. If there is any error in the job then it will show as the job canceled.

To setup up the job in the SAP system you can do that in two ways. One is by using SM36. See the following screen shots.

after you click the save it will take you to the next screen see the following screen shot.

Once you are back click on the condition and set up when and how often you want to run the job. see the screen shot.

Save the job now your job is ready to run.

 The other way to setup the job is from se38 where you can setup the job directly. See the following screen shot.

From the above menu you can setup the job immediately.

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.