Happy New Year to all. This New year and coming new years will definitely bring all your wishes come true. 

              It is been almost two months since I posted any thing. I had some good food and very good get together with friends and family. Today is my Daughter’s First birthday. So I am going to celebrate that first and I will start writing some posts .

Thanks,   kumar.

BPM — > Business Process Management.

I was in Las Vegas for the SAP Tech Ed 2008. The Next new thing in the SAP world is the SAP CE and SAP BI.

The following are my understanding.

SAP is building this CE to manage the Business process. Any Functional or Business person can build a business process and the Technical or Functional person can tie each business process to the technical object.

So in my understanding this is a very fancy work flow but outside the R3 system(stand alone server). This work flow can be integrated with other System to complete a business process.

This Work flow can call a any system from like R3, web service(third party ) and other software(.net, oracle or  other home grown) with in the organization.

I started downloading this CE7. I am going to play around with this and start writing about this in coming days.

You can also download this and start playing around with this. If you know little bit java then it will be more helpful. CE is only in Java web dynpro(ABAP is not available as of now).

https://www.sdn.sap.com/irj/sdn/downloads?rid=/library/uuid/00846edd-355b-2b10-f38c-df94ec96eb74

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. I will write about IDOC configuration in another post.

Access:

  You need to have IC manager  in your profile. This scripting is configuration only. You can customize this and do some coding. But for a plain vanilla you really no need to do that. See the following screen shot for the menu.

 

Use of the interactive script:

             Interactive script is used to navigate the screen in a particular way how business wants. If the call center agent needs to work on 10 screen and by asking questions he/she has to determine which screen he/she needs to go. Some time the agent can go to the wrong screen. By scripting we can navigate to the right screen with the answer provided by the customer.

In this post I am going to do a sample as follows.

           We are going to create a script with welcome script and go to a  Identification screen and go to good bye screen.

We need to do the following two steps.

step 1. Create all the dialoge that needed for the scripting.

step 2. Create the script and use the already created dialogue.

Step I. Create Dialogues.

  See the following screen in the script editor to create a dialogue.

 Click on the question and give a question ID and description on the bottom of the screen and enter a question. See the following screen shot.

once the question is entered now you need to add the button area for yes or no question on the script. see the following screen shot.

As soon as you click on the button you will see the following box apper(button box).  see the following screen shot.

Now let us add Yes and No button. Drag and Drop the button from the right hand side to this box. See the following screen.

Click save and your Dialogue is saved. Now create a good bye dialouge like the above one.

Create one more dialogue as above for good bye.

Let us create a new dialogue as

We are ready to create the dialogue.

Step II. Create script

Let us create the script and put the dialogue in an sequence.

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 

Create Campaign Function / Class Moduel in Batch process:

If you have a text file or the data in a table read the information in a internal table and now we need to loop thru the internal table(this is regular abap coding I am not going to explain that over here).

Inside this loop you need to use the following class and method to create the campaign.

      check if the campaign is already created , if there is no campaign then do the following

      Class name cl_crm_mktpl_appl_base->ELEMENT_CREATE.

      then call cl_crm_mktpl_appl_base->save

      and cl_crm_mktpl_appl_base->commit of this class.

      If you have BW and  want to sync with the system then

     call cl_crm_mktpl_appl_base->after_commit.

  if the campaign is already created then

       read the campaign using

       cl_crm_mktpl_appl_base->Element_read

       cl_crm_mktpl_appl_base->Element_change

         then call cl_crm_mktpl_appl_base->save

         and cl_crm_mktpl_appl_base->commit of this class.

         If you have BW and  want to sync with the system then

         call cl_crm_mktpl_appl_base->after_commit.

end the loop.

The above is the pseudo code for the batch process.

Element_create  can be used for all types of marketing element creation like Marketing plan, Campaign, Promotion and trade promo. The important thing is you need to mention the Object_type and and Object_class and if this element has a parent then mention the parent GUI. Look at the following screen shot for the different object class and the object type with in that class

All the above information is stored in CRM_MKTPL_OBJCL table. So the above explains us the campaign has two types one is campaign and another is campaign element under campaign, this is same for other elements.

See the following source code for campaign creation or update depending on the situation.

*&———————————————————————*
*& Report  ZER_TEST_CAMPAIGN
*&———————————————————————*
REPORT  ZER_TEST_CAMPAIGN.
DATA: zobj TYPE CGPL_OBJECT_TYPE,
zmkt TYPE CRM_MKTPL_MKTELEMENT,
ext_id type CRM_BSP_MKTPL_EXT_ID,
et_campaign_id type table of CGPL_WORKLIST_ITEM,
es_campaign_id type cgpl_worklist_item,
zcpg TYPE CGPL_GUID16,
zcpt TYPE CGPL_GUID16,
rec type ref to CL_CGPL_HIERARCHY_NODE.

zobj = ‘CPG’.
ext_id  = ‘Z_TEST_SE38_013′.
zmkt-EXTERNAL_ID =  ext_id.
zmkt-TEXT1 = zmkt-EXTERNAL_ID.
zmkt-OBJECT_TYPE = ‘CPG’.
zmkt-OBJECT_CLASS = ‘CP’. “Tells us this is campaign
zmkt-LANGU = ‘EN’.

DATA: lr_appl_base TYPE REF TO cl_crm_mktpl_appl_base,
      lv_subrc           TYPE sysubrc.

lr_appl_base = cl_crm_mktpl_appl_base=>get_instance( ).

* check if the Campaign is already created with the external id
SELECT guid external_id INTO CORRESPONDING FIELDS OF TABLE et_campaign_id
   FROM cgpl_project WHERE object_type = ‘CPG’
    and external_id = zmkt-EXTERNAL_ID.

if sy-subrc = 4. “ No campaign found
  CALL METHOD lr_appl_base->ELEMENT_CREATE
    EXPORTING
*    IM_MKTELEMENT_GUID         =
      IM_OBJECT_TYPE             = zobj
      IM_ATTRIBUTES              = zmkt
*    IV_USE_EXTERNAL_ATTRIBUTES =
*    IM_TEXTS                   =
*    IM_PARENT                  =
*    IM_CHECK_ATTRIBUTES        =
*    IT_SETTYPE_VALUES          =
*    IV_DEFAULTING              = ’X’
*    IV_SUPPRESS_PARDET         = SPACE
    RECEIVING
      RE_NODE                    = rec
    EXCEPTIONS
      GUID_EXISTS                = 1
      INCONSISTENT_DATA          = 2
      PARENT_OBJECT_LOCKED       = 3
      others                     = 4
          .
  IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
               WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ENDIF.
  rec->GET_GUID_OF_NODE( receiving RE_GUID = zcpg  ).
  CALL METHOD lr_appl_base->save
    EXCEPTIONS
      failed = 1
      OTHERS = 2.
  CALL METHOD lr_appl_base->commit.
*– after commit ——————————————————-
  CALL METHOD lr_appl_base->after_commit
    IMPORTING
      ev_bw_subrc = lv_subrc.
    CALL METHOD lr_appl_base->commit.
*– after commit ——————————————————-
    CALL METHOD lr_appl_base->after_commit
      IMPORTING
        ev_bw_subrc = lv_subrc.
  write ‘ Marketing Campaign created’.

  endif.
else.
  write ‘Aleady exist’.
* raise CPG_Create_ERROR.
* Read the element and change the data.
  Data: l_attributes type CRM_MKTPL_MKTELEMENT.
  read table et_campaign_id into es_campaign_id index 1.
  CALL METHOD lr_appl_base->ELEMENT_READ
    EXPORTING
      IM_MKTELEMENT_GUID         = es_campaign_id-GUID
*    IM_CHANGE_MODE             = ’X’
*    IM_RELOAD                  =
*    IM_READ_ARCHIVE            = ’X’
*    IM_RAISE_EVENT             = ’X’
*    IV_USE_EXTERNAL_ATTRIBUTES =
  IMPORTING
     EX_ATTRIBUTES              = l_attributes
*    EX_R3_ATTRIBUTES           =
*    EX_PARENT_GUID             =
*    EX_TEXTS                   =
*    EX_NODE                    =
*    ET_SETTYPE_VALUES          =
*    EX_EEW                     =
*    EX_CHANGE_MODE_FAILED      =
  EXCEPTIONS
    NOT_FOUND                  = 1
    others                     = 2.
* chagne the data  Here I am just changing the description
  concatenate l_attributes-TEXT1 ‘_Test01′ into l_attributes-TEXT1 .
  CALL METHOD lr_appl_base->ELEMENT_CHANGE
      EXPORTING
        IM_MKTELEMENT_GUID          = l_attributes-guid
        IM_ATTRIBUTES               = l_attributes
*      IV_USE_EXTERNAL_ATTRIBUTES  =
*      IM_TEXTS                    =
*      IT_SETTYPE_VALUES           =
*      IV_DEACTIVATE_CUST_DEFAULTS = SPACE
*      IV_SUPPRESS_PARDET          = SPACE
      EXCEPTIONS
        NOT_FOUND                   = 1
        OBJECT_LOCKED               = 2
        others                      = 3.
  IF SY-SUBRC <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
  ENDIF.
  CALL METHOD lr_appl_base->save
    EXCEPTIONS
      failed = 1
      OTHERS = 2.
  CALL METHOD lr_appl_base->commit.
endif.

If you have any question please let me know.  

You have to have a role of Marketing Position assigned to your profile, then only you can able to see the marketing information on the screen. Look at the following screen for the Menu on the web-ic for campaign creation.

All the submenus which ends with s are always search menus. If you click on the Campaigns then that will take you to the search. If you click on the camping then this will take you to the create.

Marketing elements has the following hierarchy.

Marketing plan >> Campaign>> Campaign Element >> Product.

Marketing Plan is Optional. This is used to tie all the campaign and the financial that is spent on the Campaign and gives a idea of how much the campaign cost.

 Campaign can directly contain Products or can have Campaign element(promo)(the next level — child for campaign) with product.

This all Marketing Element created depending upon your business need. Now let us see how we can create a campaign on the web ic and attach Product to the campaign and make this campaign ready for the process.

Let us assume the following example and work on that example:

   Requirement  We need to create a Campaign for a credit card company  for all the international travelers and provide a product (travel insurance 10$ for a trip).  

      So I am creating 10 Customers with the marketing attributes z_intl_trvl with value y for 6 of them and N to the rest 4 of them. Click here to see how to create marketing attributes and assign to the customer(BP). I am going to use the ELM to load the data so that I no need to one customer at a time. Click here to see how to load the data using ELM.

       Let us create a campaign for all the customers who are international travelers and send a email for them with product travel insurance. Let us see how to create a campaign and send a mail or fax or email and make our CRM system ready so that when the customer call us back and enquire or we can sell them the product. In this post I will only write about the campaign information . I another post I will take you thru the selling process and product creation.

   1. Create a Marketing Attribute so that we can capture the value (International traveler(Yes) or not(No)). (Click Here) Load the customer (BP) (Click here) or use the existing customer and assign this attribute to the BP data and assign the value Y to the customer(BP).

   2. Create a Profile and Target Group. (Click Here)

   3. Create a campaign using WEB-IC and attach the Product to the Campaign and Execute the Campaign ( start and make the Campaign Ready for selling the product) (Click Here).

 Now your campaign process is ready. Let us discuss about the campaign element and sales in another post.

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.

Use any of the following transaction and go in to the abap work bench.

SE38 –> Report

SE37 –> Function Builder

SE24 –> Class Builder

SE80 –> you can edit all programs from report to class module.

First on in to any one of the above transaction and click on the utilities–>Settings. See the following screen shot for old and new version.

The old abap editor config has only two editor styles but with the new one net weaver we have a new editor which is pretty good. See the difference in the following screen shot.

Old Version and the new version

the new version on sap has a new front end editor which has source code reference and key word highlight and all other futures. I really like this editor. I just want you know this is very good option and you can collapse the code between block of statement. you should try this out.

Debug Mode: See the following screen shot which is very useful and new in this editor if there is a running program and you want to stop the code in between you can do that by activation the flag. This will sync immediately as soon as you put a break point and if there is a running program that will stop for this break point. I think this is very useful if there is a big job that you started and want to see where the program is and how many records are processed.

Click on the following link and see if all the available options on the abap editor and on the ABAP work bench.

http://help.sap.com/saphelp_crm50/helpdata/EN/ca/c035baa6c611d1b4790000e8a52bed/frameset.htm

http://help.sap.com/saphelp_nw04/helpdata/EN/ef/d94b78ebf811d295b100a0c94260a5/frameset.htm

There are lot of new options that is pretty straight forward and pretty cool and useful. Please try it out.

Let me know if you have any questions.