Objective: To understand and enhance header area of Web UI.

Header area in  CRM Web UI is defined by the layout component. To identify the different components which comprise the header, we can have a look at the Layout component.

Path - IMG > Customer Relationship management > UI Framework > Technical Role Definition > Define Layout Profile.

The Layout Profile would have all the layout components which comprises the Web UI page. This includes Logo Area, Header area and other layout components.

To further get the detailing of the layout component, drill down into the layout component WORKAREA_HEADER.

Path - IMG > Customer Relationship management > UI Framework > Technical Role Definition > Define Layout components.

This will contain the application ID or the Web UI component ID. In this case, component is CRM_WORKAREAHDR.

Component: CRM_WORKAREAHDR

This component contains the header area views and configuration. This component contains views UI_COMPONENT_1, UI_COMPONENT_2, UI_COMPONENT_3.

This UI component can also be used to align and position header elements such as working context, saved search etc.

The positioning, realignment and declaration of this elements is done in UI Configuration of the Component CRM_WORKAREAHDR.

For ex, To display Central Search on right hand side of header area i.e, UI_COMPONENT_3, declare as

UI_COMPONENT_3:Window=CRM_ALLSEARCHES.CRM_ALLSEARCHES/LauncherWindow;horizontalAlignment=right;

We can also provide other header area functionalities, width etc through this method.

These Release Notes focus on new features and enhancements delivered as part of the Web Client UI Framework EhP4 Support Package 02.

The WEBCUIF development team members are doing their best to provide those new developments on older releases. So if you are interested in a specific feature, verify its availability by checking the corresponding SAP Note.

New Features and Enhancements

Integration with the SAP Theme Designer

It is now possible to style the Web Client UI Framework using the SAP Theme Designer. See the How-To Guide for more details.

See SAP Note: 2232580

New Progress Indicator THTMLB Tag

A new THTMLB Tag, thtmlb:progressIndicator, allows you to easily display a percentage value or any kind of progress and enhance the user experience on your form. You can also use a new P-GETTER attribute in order to any inputfield into a progress indicator on a Configurable Form.

See SAP Note: 2174100 and 2239586

Floating Pager for the Table

It is now possible to have the table pager float. The floating pager will appear for tables that are partially in the viewport, thus the pager is always accessible and it is not required to scroll to the complete bottom of the table to navigate to another page of records. When floating, the pager will be semi-transparent; on hover, the semi-transparency will be removed.

See SAP Note: 2268797

Highlighting of Mandatory Fields

Mandatory fields are highlighted consistently in all skins. All mandatory fields have a border to emphasize their importance on a given form. The border color matches the color of the mandatory star.

See SAP Note: 2283068

If you missed them, check out the WEBCUIF EhP4 SP01 - Release Notes.

Overview:

Many times in our project we have requirement to trigger server side validation by Pressing TAB key (keyboard). Typically this is a demand from Customer who are usually new to SAP world. I myself had faced similar situation and convinced customer that it is required in SAP CRM to press "Enter" to get the error message aka validating the data.

In this blog I would explain how can we trigger Validation by pressing TAB key in SAP CRM Web UI.

Yes it is clear that we can also attach JavaScript (Attaching Java Script to a field in Table of SAP CRM Web UI) but complex validation logic (through BOL) is not possible or really complex.

Details:

By pressing Tab key on Web UI, it is actually fires client side event "Clientblur". We need to capture trigger event handler through JavaScript for the event Clientblur, and trigger server side event through BSP element <bsp: htmlbEvent>.

Step 1:

Copy CL_UIF_BP_SAMPLE_ITERATOR  class to Z Iterator class. In method "IF_HTMLB_TABLEVIEW_ITERATOR~RENDER_CELL_START" (is used for new column) we need to capture "Clientblur". Below is sample code:

DATA: lr_input TYPE REF TO cl_thtmlb_inputfield.

   CASE p_tableview_id.

     WHEN OTHERS.

       CASE p_column_key.

         WHEN 'ZZTEST'.     "CRM Web UI Field Name

*         Onclient functionality

           TRY .

               lr_input ?= p_replacement_bee.

               lr_input->onclientblur = 'return Testclientblur()'.

               p_replacement_bee ?= lr_input.

             CATCH cx_root.

               p_replacement_bee ?= p_replacement_bee.

           ENDTRY.

       ENDCASE.

   ENDCASE.

Step 2:

In .HTM page need to create an instance of created Iterator class:

DATA: gr_iterator TYPE REF TO ZCL_TEST_ITERATOR.

CREATE OBJECT gr_iterator.

In Tableview or Tablecellartor, need to use the before created custom Iterator class. Below sample code:

       iterator = "<%= gr_iterator %>"

Step 3:

In .HTM page after Tableview / Tablecellartor code declaration, need to declare BSP Element for event firing and JavaScript event handler method.

<bsp:htmlbEvent name = "DO_VALIDATE_INPUT"

                 id   = "DO_VALIDATE_INPUT" />

* Here DO_VALIDATE_INPUT is the name of method to handle the event in View Implementation class

* I have used standard method DO_VALIDATE_INPUT for testing purpose and can be best place to write validation for multipurpose uses.

Step 4:

In .HTM page after Tableview / Tablecellartor code and  BSP Event Element declaration, JavaScript event handler method should be written.

<script type="text/javascript">

function Testclientblur() {

DO_VALIDATE_INPUT();

}

</script>

* Here Testclientblur is the event handler for client side event "Clientblur", which we have declared in Step 1. In this event handler, it is calling Server Side Event and Event handler "Do handle event".

Test:

I have used for testing and Date field and by pressing the Tab key on Date field pops out error message "Date sdsd is invalid"

Summary:

I hope it would solve many business case problem where validation error by pressing Enter or Save button is too late. Please use the logic and if you have questions and / or comment, please add. Enjoy

Reference: CRM WebClient UI - Talking with Java Script - CRM - SCN Wiki

Objective : Change View settings such as showing certain buttons like EDIT based on current logged in Business role.

Current logged in Business role can be obtained using method GET_PROFILE of Class CL_CRM_UI_PROFILE. We can derive view changes based on Business roles as well.

For eg, If the need is to restrict the user to EDIT view only in a certain Business role. this can be achieved by adding the logic in the placeholder wherein the buttons are configured & a simple code snippet like below can derive that logic.

Sample code -

Data :  lr_profile type ref to CL_CRM_UI_PROFILE,

            lv_role type string.

lr_profile ?= CL_CRM_UI_PROFILE=>get_instance().

call method lr_profile->if_crm_ui_profile~get_profile

RECEIVING

     rv_result = lv_role.

If lv_role NE '<Z-Business role name>'.

         Delete  gt_button where on_click = 'EDIT'.

endif.

The Webclient UI Framework (a.k.a. WEBCUIF) is a large and complex product, always evolving thanks to the customers and the community feedback. Here are some resources that can help you stay ahead of the game:

• The SAP Enterprise Architecture Explorer will give you a concise overview of the Webclient UI Framework as well as other SAP UI technologies and clients.
• The SAP UI Technologies Road Map is regularly updated. You can find there recent and planned features of SAP UI Technologies.
• The WEBCUIF Release Notes keep a list of the new features and enhancement after each Support Package release.
• The SCN Webclient UI Framework space is the best place to ask questions and get support from the development community.
• The SAP Customer Influence program allows you to propose improvements for the Webclient UI Framework and work directly with developers through Customer Connection or other initiatives.

Do you use other channels or sources? Do you have other ideas for collaboration? Don't hesitate to start a discussion in the comments below.

Disclaimer:

          This blog is intended to share the accessibility project experience.

Important:

          Term ‘Users’ in this blog refer to visually challenged users, who have up to 90% visual challenge.

Background: As part of my previous projects, I got an opportunity to work for accessibility requirements for visually impaired users. This was an unique project experience working on different set of requirements. I had to first understand the business requirements from a different angle( interpret disability of user) and provide appropriate solution. As part of requirement gathering process, Identify the business processes, SAP CRM WEB UI screens navigated by user. Solution should simplify the WEB UI screens with less cluttered information for smooth navigation and uninterrupted process execution. On one project I worked with IS Utilities customer service adviser user, accepting inbound calls, making outbound calls and successfully making sales. On another project I worked with Grantor Funding officer working in back office reviewing customer applications and approving funds.

Users navigated through SAP CRM WEB UI screens using keyboard short cuts and with help of screen reading software.

WEB UI Navigation:

• Configure shortcuts for keyboard navigation
• Making sure each UI element can be navigated by using ‘TAB’ key
• Each UI element has appropriate text and can be read by the screen reading software
• Making sure all the required information for the user is present on the same WEB UI screen, preventing forward and back navigation.

Screen reading software:

• https://en.wikipedia.org/wiki/List_of_screen_readers
• JAWS
• VoiceOver
• Every screen reading software has it own pros and cons, based on the application and OS they are used with
• Internet Browser compatibility of screen reading software
• There are some scripts written for JAWS software, which will be triggered as user starts using the software. Its a local deployment.

Custom Development/Changes:

• Simplified UI screens, with only required information
• Default the information wherever possible
• Remove the hyper links

Challenges:

• SAP CRM WEB UI Tables and table line navigation
• Hyper links
• Transaction launchers
• Custom developed UI elements
• UI Screen in display and edit mode
• Attachments to SAP CRM Objects
• Data loss pop ups
• Screen reader software does not indicate the current position of the cursor
• Forward/backward Screen navigation from hyperlinks
• Un-necessary Messages (Error, Warning, Information)
• Flickering of UI screen as soon as the screen reader software is activated

High Contrast Screens: High contract UI, typical combinations

• White background and black text
• Yellow background and black text
• Pink background and black text
• Blue background and black text

New high contract skins were developed

Fonts: Large fonts

Multi lingual: Other than English

Links for additional reading

• https://help.sap.com/saphelp_nw70ehp2/helpdata/en/48/1625b8df754c1de10000000a42189b/content.htm
• https://scn.sap.com/thread/3801716
• http://scn.sap.com/docs/DOC-43952
• http://help.sap.com/saphelp_dm40/helpdata/en/fd/7c4a41edf0db2be10000000a1550b0/content.htm
• https://help.sap.com/saphelp_nw70/helpdata/en/fd/7c4a41edf0db2be10000000a1550b0/content.htm
• https://help.sap.com/saphelp_crm50/helpdata/en/fd/7c4a41edf0db2be10000000a1550b0/content.htm

Disclaimer: This blog is part of series

Background: As part of a project i got an opportunity to work on BP addresses. Address is very critical element while communicating with customers, across industry. SAP system should be configured to suit the business requirement while fully utilizing the capability provided by SAP. Address management is one of the efficiently designed features of SAP. I would like to share the behavior of address types based on configuration.

Business Requirement:  A customer can have multiple addresses based on context of business process and appropriate selection of address for correspondence is the key.

For Example to name a few:

Main Address - using which customer was registered or was acquired.

Correspondence address - To receive correspondences

Billing Address - To receive bills/invoices for services

Forwarding Address - To receive correspondence once customer has switched to new supplier

Standard SAP provides address type XXDEFAULT and you can configure custom address types under IMG path shown below in Figure 1 and Figure 2.

Figure. 1

Figure. 2

Marked Check box 'Several uses' for an address type enables business to enter multiple addresses. However, only one will be valid for correspondence at any point of time and end user will have the ability to switch between the addresses based on customer's request. Example shown below in Figure 3:

Figure. 3

Whereas, the address type where several use flag is not marked, then there can be only one address at any point of time. If end user enters another address for the same address type latest becomes the standard and valid for use. Though the previous address will be still exists, but without an address type association. Example shown below Figure 4.

Figure. 4

Now, how to identify standard/default address. As shown below there will not be a dustbin icon with standard address type (XXDEFAULT). This is the standard SAP feature.

Figure. 5

If end user enters another address with XXDEFAULT address type, automatically previous address will be marked with an end date system date - 1 and new address will have a start date of system date and end date as 31.12.9999. This can be seen screen shot given above Figure 5 and below Figure 6.

Figure. 6

Business processes should always look for the address type, standard flag and end date to pick correct address.

You work on the CRM WebUI, and a standard message is displayed after you perform an action, but the message text does not meet your requirement, and you want to replace the existing standard message with your own message.

CRM has the functionality that you can replace the existing message with your own messages that are created in your namespace. You can replace the existing message text with your own message text. The customizing path is:

SPRO -> Customer Relationship Management -> UI Framework -> UI Framework Definition -> Define Messages to Be Replaced

If this cann't fullfill your requirement, you may try BADI WCF_ALTER_UI_MESSAGES.

Application Enhancement Tool can be used for both Field and Table Enhancement. Recently We had a requirement in my project to enable AET for a Table .This blog would explain on how AET can be used for Table Enhancement.

Field Enhancement : AET Tool can be used to create,update and delete fields in the table that does not belong to standard Delivery.

Table Enhancement : AET Can be used to create,update and delete tables that does not belong to standard delivery , the same table can be linked with an existing table via Parent ID . This table can be made available in the CRM WEB UI as an Assignment Block or in Form View.

Requirement :

There is a Relationship Table which maintains the relationship between the entities .For example we have a Case and Person as two entities and the different relationships can be created between these two entities .For Example : Person can be related as Suspect to a case , or as an Victim.

The requirement was to enable AET for this relationship Table , so that customer can maintain there own fields in a new table and link with this relationship Table.

Customer should be able to create , update and delete entries in this new table from UI .

1) Enabling AET for a Table

  Call transaction AXTREG and create the Table Enhancement Place and also mention the required details like Application Group and the Parent ID .

Parent ID Data Element will be same as the Key field in the Parent Table.

Next step is to mention the Parent Business Object under which Extension BO will be created .

In the Transaction AXTREG , under Enhanced Business Objects select the Enhanced Business Object and the the part of Enhanced BO  under which Enhancement place will be included

Specify the Table Enhancement Place which was created in first step and also Select New Extensions allowed .

2) Creation of Extension Tables From UI

Steps to make Configuration Active

First Enable the Configuration from Personalize settings from the Web UI

Now go to the page from where Enhanced BO will be called ( For  which Table Enhancement Place is added  ) and select configuration from left Upper corner as shown below.

Then Select the particular Block and Display the enhancements .

From here , you can create a table and this will generate all the Extension BO's with the structure of Table mentioned by the user.

Table Created is as show below

Once we Create Table from UI , this will also generate the View under the  UI Component which is mentioned   while creating.

View will have Context node referring the Extension BO Object .

3) Enhance the Genil Class to show the Extension Bo's in BOL Model Brower.

Next step is to Enhance the Genil Class to show the Extension Bo's which will be created under this root Object.

Below Code can be put in the Get_model Method of Genil class of Parent Object

TRY.

      CALL METHOD cl_axt_extensibility_access=>get_extension_tables

        EXPORTING

          iv_appl_group = 'ICM'

          iv_ext_tplace = 'ICM_RELATION'

        IMPORTING

          et_model_il   = lt_model_id.

    CATCH cx_axt_runtime.

  ENDTRY.

  LOOP AT lt_model_id ASSIGNING <fs_model_id>.

    MOVE-CORRESPONDING <fs_model_id> TO ls_relation_det.

    INSERT ls_relation_det INTO TABLE rt_relation_det.

  ENDLOOP.

This will add all the extension BO's to the Model as shown below.

4) Create new Genil Class for Handling CRUD Operation on the new Extension BO's

Create New Genil Class for the New relation which is created and Read , Modify and Save Methods to handle CRUD operation on the new table.

API's of Standard class CL_AXT_TABLES_API ( Create,Change,Delete and Save Methods ) can be used for CRUD operations.

Adjust the Genil Class of Parent Object in such a way that New Genil Class will be called for CRUD operation on the new Table.

5) Enhance the Existing UI with the View Created for Table

Creation of a Table would have generated the new view as mentioned in the step 2 . This view can be used in the Existing View for enabling CRUD operation from UI by a User.

This completes the End to End Implementation of AET Enhancement for Table.

Hope this Blog helps the people dealing with AET.

Thank You,

Jayashree

I have been working as a Fiori application developer in SAP for almost two years, which means now I use Chrome development tool in my daily work for trouble shooting instead of ABAP debugger when I was working using CRM WebUI.

Yesterday I was assigned with an incident about CRM Lead application in WebUI, and I am glad to figure out that Chrome development tool can also do me a great favor for my trouble shooting in WebUI issue. I share with my experience learned in this blog.

Issue description

The incident complains that when a given row in Products assignment block is selected and Delete button in toolbar is clicked, nothing occurs.

My issue analysis process

I located the event handler of this delete button in toolbar:

And I find out that get_marked in line 21 return an empty BOL entity collection.

I debugged into get_marked, this method will only return those BOL entities as marked whose SELECTED equals to true.

For Lead application, all the BOL entities which represent table entries in assignment block has SELECTED as false, as a result no BOL entity is returned - so nothing to be deleted.

However I have checked Opportunity application, the deletion works. The attribute for BOL entity is set as abap_true as expected.

What is the reason of this different behavior?

Research how WebUI passes table selected row information to ABAP backend via Chrome development tool

In WebUI I selected first row in table and click delete button in toolbar, then I observe this selected information is passed to ABAP backend via field name as C34_W111_V113_V120_prodtable_selectedRows and value as 1.

And in ABAP backend, all these http form fields passed from frontend UI are received and stored in variable lt_fields in line 25.

I download the content of lt_fields as excel and highlight the field for selected row index:

Then in ABAP backend, it is expected to populate the string "C34_W111_V113_V120_prodtable_selectedRows" to get the index by field name. From the code below we get: "C34_W111_V113_V120_prodtable"

The left string fragment "selectedRows" comes from constant gc_selected_rows. Now the selected row index is get by field name in line 14.

The original issue is: although we have table id "prodtable",

however a wrong default id "Table" is passed in via iv_id and thus wrong field name is generated, so based on this wrong field name, no selected index could be queried:

The issue is already fixed via SAP note 2331513.

The naming convention of capital characters in lv_name:

• C: component
• W: window
• V: view

You can also find such id in generated html source code via Chrome development tool in Element tab: first click the small icon highlighted below and then click the UI area you would like to inspect:

Then in Elements tab, the html source code of the selected UI area will be displayed for you:

Further reading

• Chrome Development Tool tips used in my daily work 
• My UI5 debugging tips and experience collection - how to resolve UI5 issues through debugging by yourself

Overview:

In this blog posting I would cover scenario of replicating price agreement from SAP CRM to ERP. Price Agreement is very vital of Sales Contract, which influence the further documents in ERP including Sales Order and Billing.

In this scenario we worked was one of difficult scenarios as condition types were created in ERP but Price Agreement (Condition Record) was created in CRM Sales Contract. In following sections I would write down necessary required steps.

Maintain Structure:

Append the structure CND_MAPT_ACS_REM_CUST with the Custom fields (Z) and the standard field which are not available in CRM field catalog. Here remember the field name and data element name should be same with ECC. Please check condition table, field names before appending.

Maintain Field Catalog

Maintain the added fields in field catalog, following is the path:

Maintain Custom Key Fields

Maintain all the Custom (Z field) field which are part of key combination of condition table, which is assigned to condition type. Following is the menu:

Here maintaining CRM_ITEM_GUID to an external field (fictitious) is must as ECC does not understand GUID. For example:

Initial Download of Condition Type:

Through transaction R3AS and objects DNL_CUST_CND, DNL_CUST_CNDALL all relevant customizing and condition types were loaded in CRM

Impement BADI:

1. Implement BADI "/SAPCND/ROLLNAME" and put e_excuted to 'X' for following methods a. FIELD_CHECK b. ATTRIBUTE_CONVERSION c. F4_HELP

         It is required to give provision for the condition type to create Price Agreement in SAP CRM

    2. Implement BADI "CND_MAP_CNV_FIELD" with filter CRM_ITEM_GUID. In this implementation (Conversion Method) Item GUID must be properly divided to Document and Item Number combination, because in ECC GUID does not exist.

       Like as :  CONCATENATE lg_vbeln lg_posnr INTO ev_target_value.

Maintain Condition Types to Allow Price Agreement replication (ECC):

Maintain the relevant condition types in customizing which are used in Price Agreements. This customizing is done to allow the price agreement to be replicated into relevant ECC condition tables. With this entries ECC understand that data is coming from CRM and not created in ECC. Following is the path:

Summary:

After all the steps are performed, create a price agreement with an Item of released status. Check the BDOC is green and there is no error. Check the relevant condition table in CRM for example CNCCRMPRCUS780 and correspoding ECC Table A780 for entries.

Also check Sales Contract Item in ECC that price agreement is displayed. If not, please check the check box "condition index" at condition type customizing.

Hi All,

One of the interesting requirement I recently had was to set the priority of incoming e-mails based on different conditions. Conditions were, if user has marked the email as 'High importance' or the email subject contains some words like 'Urgent', 'Last reminder' etc. As usual the first place for getting something for this requirement was SCN. Though I didn't get a complete solution, I got something from one of the threads.

First I checked whether it's possible to set the priority like this. Yes..It's possible manually via transaction code SWI1 and changing the priority. Now how to automate this.

For debugging an incoming email, we can set the debugging parameter in the following path,

SPRO->Customer Relationship Management->E-mail response management system->Define Repository or transaction CRMC_ERMS_REPOSITORY. For context ERMS, insert a property 'DEBUG' and value as 'X'. This is a SAP hard-coded break that stops the routing and waits for you in sm50 to debug. Now you can debug in SM50.

Following are the steps I found after some debugging and analysis.

1. Go to tcode SWO1 and create a sub object for ERMSSUPRT2.

2. Redefine the method RuleExecution in the Z-object.

3. Now this method is the place where you have to make the code changes.

In our case, we created a custom table where we can store the words which needs to be considered as high priority. This allows if in case tomorrow we need some extra words also to be considered.

Insert following code here,

*   Get specific words from customizing table     SELECT *       FROM ZPRIORITY_WORDS       INTO TABLE lt_prio_key.     IF sy-subrc = 0.
 *     Loop to check if subject contains any string from the table maintained values.       LOOP AT lt_prio_key INTO ls_prio_key.         TRANSLATE ls_prio_key-key_string TO UPPER CASE.         lv_sub_upper = sub .         TRANSLATE lv_sub_upper TO UPPER CASE.         IF lv_sub_upper CS ls_prio_key-key_string.           lv_wi_text_import = 1.           EXIT.         ENDIF.       ENDLOOP.   ENDIF.    

Now we got whether there are any words which is to be set to high. We need to check whether the email was sent with high priority also. Hence, add the following code.

      lt_factbase =  service_manager->factbase.
 *     Get priority email setting       CALL METHOD lt_factbase->get_by_xpath         EXPORTING           id_xpath  = '/parts/EMAIL/PRIORITY/text()'         RECEIVING           rd_result = lv_prio.

Considering the values found from above, we have to set the priority of email. Hence, use the FM "SAP_WAPI_CHANGE_WORKITEM_PRIO" for setting the priority.

IF lv_wi_text_import EQ 1 OR lv_prio EQ 1.
 *       Change priority         CALL FUNCTION 'SAP_WAPI_CHANGE_WORKITEM_PRIO'           EXPORTING             workitem_id = flowitemid             priority    = '4'             language    = sy-langu.       ENDIF.     ENDIF.

4. We are done with coding part now. The next is to set the z-bject type is released.

5. And the last step is making the z-object as the delegated type for ERMSSUPRT2. This is to be done in SWO6 transaction.

Now go to your inbox and see whether the email with 'High importance' has come with priority 'High'.

Please let me know if you have any queries.

Thanks,

Faisal

IDOC or Intermediate Documents are commonly used in case of data migration between SAP systems or between SAP and legacy system or vice versa.This blog details the steps involved in configuring a new IDOC and also list's down the various transactions that are used while working with IDOCs.

IDOCs can be classified into two . Inbound IDOCs and Outbound IDOCs.

Inbound IDOC   : These are IDOCs which get the data into SAP system from external source i.e PI system  or any other external system.

Outbound IDOC: These are IDOCs which are sent out from SAP system to any other system. i.e PI system or any other external system.

Step 1 : We need to check the RFC connections to the target system , it can be PI system or any external system. If it is to a PI system then we need to check the connection under ABAP connections in SM59 transaction and for external system under HTTP Connections to External System.

Step 2: Create a port in transaction WE21 which shows the target system’s RFC destination.

Step 3 : In transaction WE20, create a partner profile and mention the message tpe details .In case of Oubound IDOC’s , mention the message types under Outbound Parameters.In case of Inbound IDOC’s , mention the message types under Inbound Parameters. For outbound parameters ,maintain port and IDOC details, because port describes to which system the IDOC has to flow. Whereas in Inbound IDOC,mention the process code details which determines the inbound function module for processing the data.

Step 4 : Message type SYNCH is the default message type for outbound parameters. Choose a particular message type and maintain the below settings. Under the receiver port mention the port created in transaction WE21. In Output mode, choose Transfer IDOC immediately. In IDOC type mention the IDOC associated with the Message Type.

Step 5: For Inbound IDOCs, mention the process code as APL1 and choose option Trigger Immediately under Processing by Function Module.

Step 6 : In transaction BDFG, we can see which ALE function module we need to enhance for our requirement. In case, we are working with Business Partner we can choose the FM as CRMXIF_PARTNER_SAVE and the Business Object Type as ‘BUS1006’. In IDOCs , SAP by standard provides us to exchange the business partner master data details , BP relationships and BP Hierarchies.

Step 7: In case we are working with Business Transactions we can choose the FM as CRMXIF_ORDER_SAVE and the Business Object Type as ‘BUS20001’.

Step 8 : In our example let us work upon Business Partners. Select the FM name and the Business Object type and click enter. By default all standard messages types would be displayed out.Now to create a new message type , click on Create button as shown below. You will get a popu where in you can enter a Z name.

Step 9 : Once the Z message type is created. Release it as shown.

Step 10 : Select  the  Z message type and click on the Display button to view the details.

Step 11 : With Z Message Type , Z FM’s for both Inbound and Outbound gets created.

Step 12 : In transaction WE30 we can check the IDOC  created.

Step 13 : In transaction WE31 we can check the IDOC  segment .

Step 14 : For Inbound IDOCs in transaction code WE42 , select the process code APL1 and click on display . Assign a Z Fm-ZAPPL_IDOC_INPUTI . Create a copy of the standard FM APPL_IDOC_INPUTI into ZAPPL_IDOC_INPUTI .

Step 15 : Under Logical Message , mention the Z message type created.

Step 16 :In  transaction WE81 , we can see the message type details.

Step 17 : In  transaction WE82 , we can see the message type and basic type details.

Step 18 : For outbound IDOCs in transaction BD64 , create a distribution model. Goto change mode and click on 'Create Model View'. Enter a description and Technical name.

Step 19 : Add the message type under the Distribution Model and maintain the sender and receiver system details.

Step 20 : In transaction BD82, generate the partner profile for the newly created distribution model.

Step 21 : In  transaction SMOEAC , we create the sites and subscriptions.Site is the destination where the data needs to be sent.Subsricption is to identify what is the object to be exchanged. (In case of BP data it will be All Business Partner MESG).Subscriptions are assigned under Sites. Type would vary based on our need.

Step 22 : In transaction CRMXIF_C1 , we maintain the message type details against the Site name.

Step 23 : We can even restrict an Outbound IDOC flow based on any condition to a particular Site. A times there could be multiple sites in a system , we can control the flow of IDOC here as well.This can be achieved by maintaining an entry in table - SMW3FDCUST, we assign a copy of standard FM - SMW3_OUTBOUNDADP_CALLADAPTERS against BDoc Type BUPA_MAIN,  which is  used to do any further customizations. We can do the same for other IDOC types.In the Z FM ,input parameter HEADER we get the Site ID details , based on that we can control the changing parameter - RECEPIENTS.

Step 24 : Apart from the above steps we can use Transaction WE02/WE05 to display any IDOC and WE60 for IDOC Documentation.To reprocess any IDOC use transaction WE19 adn inoput teh IDOC number, a new number gets generated.

Step 25 : Any IDOC has 3 records types - Control, Data and Status.Control Records displays the direction of the IDOC, message type/basic type details.

Data record display the data under multiple segments. In Status Record we can check the IDOC status whether it is a success or failure.

Tables for these 3 record types are as below.

Control Record - EDIDC

Data Records    - EDIDD

Status Record   - EDIDS