BBP_INB_DELIVERY_CREATE function is used for creating inbound delivery. Normaly created delivery number and error messages are returned, but sometimes function exports empty delivery number, inspite of return table without errors. In this case system actually creates delivery, if you query tables after commit, you will find delivery number.

Sytem Info that i faced the bug:

SAP ECC 6.0

DATA: _header    LIKE  bbp_inbd_l,

        _delivery  LIKE  likp-vbeln,

        _it_detail TYPE STANDARD TABLE OF bbp_inbd_d WITH HEADER LINE,

        _it_return TYPE STANDARD TABLE OF bapireturn WITH HEADER LINE.

  DATA: _vbeln TYPE ekes-vbeln.

  SELECT * FROM ekpo WHERE ebeln = 'PO Number'.

    _it_detail-material      = ekpo-matnr.

    _it_detail-matl_desc   = ekpo-txz01.

    _it_detail-deliv_qty     = ekpo-menge.

    _it_detail-unit             = ekpo-meins.

    _it_detail-po_number = ekpo-ebeln.

    _it_detail-po_item      = ekpo-ebelp.

    APPEND _it_detail.

    CLEAR _it_detail.

  ENDSELECT.

  _header-deliv_date = sy-datum.

  _header-deliv_time = sy-uzeit.

  CALL FUNCTION 'BBP_INB_DELIVERY_CREATE'

    EXPORTING

      is_inb_delivery_header = _header

    IMPORTING

      ef_delivery                    = _delivery

    TABLES

      it_inb_delivery_detail = _it_detail[]

      return                         = _it_return[].

  LOOP AT _it_return WHERE type = 'A'

                                          OR type = 'E'

                                          OR type = 'X'.

    EXIT.

  ENDLOOP.

  IF sy-subrc = 0.

    CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.

  ELSE.

    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

      EXPORTING

        wait = 'X'.

     IF _delivery IS INITIAL.

         SELECT SINGLE vbeln

         INTO _vbeln

         FROM ekes

         WHERE ebeln = p_ebeln

           AND ebtyp = 'LA'."Inbound Delivery

     ENDIF:

  ENDIF.

While designing new table, we often enable the initial value check to set the initial value for the field based on the datatype.

A field can also be created in the database as NOT NULL if the initial flag is not set in the ABAP Dictionary.

To see  the default value of each field check

Utilities ->Database object->Display in the maintenance screen of the corresponding table.

But in select query there are some impact

NULL means that physically nothing is stored in the database. If a database field is defined as CHAR with, say, 80 characters, the NULL value will not waste that space.

When NULL values are transfered from the database, they are converted to the ABAP initial value. But if existing database tables are extended appending new field(s), those fields get stored as NULL values for the existing database records. A WHERE <field> = SPACE will not retrieve the recors with NULL values for the field.

If such a null field is used in WHERE clause, no problem if specifying any values except initial.
If selection of records with initial fields is required  and  you do not know if NULL values exist, select

WHERE ( <field> = space or <field> is NULL ).

So we have to check this aspect of table while doing programming.

Functionality

Event 2638 is processed when an invoice with SUBINV item type is created. In this event, you have the option to change relevance (TOTALREL field) of SUBINV item.

If SUBINV item value of TOTALREL field is set to true item amount will be included in total amount of invoice and business partner is payment responsible for SUBINV item too. In this case source invoice shouldn’t be posting relevant, it will have informative purpose.

If SUBINV item value of TOTALREL field is set to false item amount will not be included in total amount, business partner isn’t payment responsible, item should not be posting relevant and it will have informative purpose.

Notes

The event is called at invoicing of the single invoicing document.

Programming Restrictions

To ensure the consistency of the system, note that you must not use the following language elements in events, unless they were explicitly declared to be allowed for the given event:

• COMMIT WORK
• ROLLBACK WORK
• CALL FUNCTION 'DEQUEUE ALL'
• Deletion of locks that you have not set yourself
• Implicit database commits triggered by RFC calls or by a WAIT statement

  If you update additional data in an event and use the construction PERFORM commit routine ON COMMIT, note that: 

• At the end of the commit routine, all internal tables from which data was updated must be initialized again to prevent a duplicate update in the next call.
• A PERFORM rollback routine ON ROLLBACK must also be called.
  In the rollback routine, initialize the same data that is initialized at the end of the commit routine.

If you want to carry out checks in an event, when you issue messages, note that warning messages cause background processing of the process to terminate. You should therefore avoid issuing warning messages if possible. At the most, issue warning messages if the value of SY-BATCH is initial.

Also avoid messages of type A (termination). In the course of background processing, such messages can be captured and processing can continue. However, at the same time the message triggers an implicit ROLLBACK WORK, which can cause data inconsistencies.

Introduction:

In this document we will work on printing a Data Matrix barcode (DMC) which is a 2D barcode not supported by SAP.

A 2D (two-dimensional) barcode is a graphical image that stores information both horizontally -- as one-dimensional bar codes do -- and vertically. As a result of that construction, 2D codes can store up to 7,089 characters and possibly more.

Below are some of the types of 2D barcodes

Requirement:

Print Data Matrix barcode (2D barcode) on zebra printers using Smartform.

* Similar approach can be followed for printing other 2D barcodes and the generic barcodes with specific height and width.

Issue:

SAP by default only supports PDF417 as 2D barcode and does not support Data Matrix and other 2D barcodes

Solution:

Printing other 2D barcodes which are not supported by SAP is possible by following the below steps

• Printer should supports the required barcode:We can check this online based on the printer model and make. Most probably you will find this information on the manufacturer’s website.

• Choose an appropriate device type for the printer:Selection of device type is based on the printer you are using.  IN this example we are using ZEBRA printer so the device type selction will be based on Zebra printer.This topic is dealt in more detail in the other document named ‘Working with Zebra Printers using Smartforms in SAP’ please refer to the same for additional documentation on selecting the device type for Zebra printers.  For Zebra printers we have the following device types LZEB* (* => 2/3/4) series or YZB# (# => 200/300/400) series based on the DPI resolution of the printer.

        For the demonstration as an example we will use LZEB2 device type from here on in this document.

• Create a system barcode of type UNDEF in SAP:For creating a system barcode go to transaction SE73.

          This will take you to the SAP script Font Maintenance: Initial screen

          Select System barcodes check box and click the change button. This will display a list of all the Barcodes on the SAP system.

          Click the Create button (Paper icon) at the top of the screen

          The Choose Bar Code Technology select box will now be displayed.

          The barcode we are adding is a new barcode symbology which is not supported by SAP, and the new barcode techcnology allows only specif types

          of barcodes symbologies to be created therefore we are going to use Old technology to create our new barcode as an undefined symbology.

          So Click on Old.

          The Create/Change System Bar Code settings screen will be displayed. For barcode type enter ‘UNDEF’ ( barcode not defined) as the data matrix

          barcode type is not defined in SAP. Also specify the height and width of the barcode.

          Then save the changes by clicking on the Ok button. Now the system barcode ZDMC is created.

• Create a printer barcode for the newly created system barcode with appropriate print control:

       For creating a system barcode go to transaction SE73. This will take you to the SAP script Font Maintenance: Initial screen

          Select printer barcodes check box and click the change button. This will display a list of device Types available in SAP system.

          In this case I am using device type LZEB2 so I will create a printer barcode for this device type. It is advisable to copy this device type to a new

             device type and then make changes to the new Z device type and use it for printing but for demonstration I am using the same device type.

             Double click on the device type to list the barcodes supported by this device type.

               Notice the Prefix and Suffix value ranges used for the barcodes. Here in this case the highest number used for prefix is SBP20 and is different

               for each barcode however the suffix is same for all the barcodes. These prefix and suffix are the print controls of the barcodes supported by

               the printer.

               Now select the create button on the top of the screen to add a new printer barcode. This will take you to the barcode selection screen.

               Select the system barcode you created earlier and enter the other values as shown in the screenshot above. For prefix we are entering SBP21

               because all the numbers from 1 -20 (SBP01 to SBP20) are already used so we are using the next available number SBP21 and the suffix number

               stays the same. We can use any number from 21-99 for prefix.

               Now the barcode is created for the device type (see screen shot  below)

               But the print control SBP21 is empty. For the barcode to work properly we have to add commands in the print control in ZPL-II language

               (printer language).

               Please find the online document named 'ZPL2 command book' . The site link for the same is

               http://www.zebra.com/id/zebra/na/en/documentlibrary/manuals/en/zpl_ii_programming2.File.tmp/45541L-002_RA.pdf

               It is adviced to have the document before we proceed further. This command book has all the commands for printing different types of

               barcodes on a printer ( only if the printer supports it )using the ZPL2 command Lanugage.

               Here we are adding the Data matrix barcode, and the printer command format for printing the data matrix is: ^BXo,h,s,c,r,f,g

               Command Parameters:

               O – Orientation

               H – Height

               S – Quality level

               C – Columns to encode

               R – Rows to encode

               F – Format ID

               G – Escape sequence control character

               Refer to the attached command book for accepted and default values for the above parameters and how to use the command.

           Below is an example of the post script language commands used for printing a DMC barcode on the printer.

            The printer command mainly needs to have 3 types of information

1.      Command to indicate the type of barcode to be printed ( Marked by ^BX in the command above)
2.        Command to indicator the start of data ( Marked by ^FD)
3.        Command to indicator the end of data (Marked by ^FS)

           When working with Smartforms the prefix print control in the printer barcodes screen should have both the commands for the type of barcode

               and the command for the start of datawhereas the suffix will only have the command to mark the end of data.

          Taking the above points into consideration we will have ^BXN,2,200,20,20,6,~,1^FDcommand in prefix and ^FS in suffix.  As the suffix is

             used to mark the end of data it is same for all the barcodes and hence maintained as default.

             Meanings of the command Parameters for prefix ^BXN,2,200,20,20,6,~,1^FD are:

              ^BX        The Data Matrix command

              N            The orientation is normal

              2              Dimensional height in dots of the individual symbol elements

              200         Quality ECC level (ECC 200)

              20           Columns to encode

              20           Rows to encode

              6              Data to be used (6 means full 256 ISO 8-bit data is used)

              ~             Escape sequence for control characters

              1              Square aspect ratio, if you required rectangle this will be 2

              ^FD        This is to mark the start of the field data to be encoded in the barcode

            Add the following command in the print control prefix:  ^BXN,2,200,20,20,6,~,1^FD

            Go to SE73 -> Select printer barcodes -> Change ->Select device type (in this case LZEB2) -> double click to display the list of barcodes supported

            by the device type.

              Select the new print control SBP21 (barcode prefix) and click on Maintain Print control button. Following popup will be displayed.

              Enter the command in the control characters sequence field and make sure the Hexadecimal switch is turned OFF. Then press enter.

              The print control is saved.

               The barcode suffix SBS00, which is default for all the barcodes holds the end of data command (see below)

               The configuration of the printer barcode is complete. Now we can use this barcode to print the Data Matrix barcode (2D barcode) from SAP.

               Note:

               There can be various combinations to the prefix command. If the barcode is not printed then you have to try changing the values for the height,

               rows and columns variables in the command. The prefix combination that worked for me is: ^BXN,3,200,,,6,~,1^FD

• Use the barcode in the Smartform using a style:

       Please refer to online documentation for adding a barcode to a style in Smartform.

       After you have added the barcodes to one of the character formats of the style which is being used in the Smartform, we just have to use the

         newly created barcode type to display the 2D content as Data Matrix Barcode.

       See below screenshot for an example.

       As the example depicts, use a separate text node for the 2D barcode , keep all the 2D content in a variable or write it all down in the text node.

         Select the whole text and select the character format for the DMC barcode.

          At this point if you try to print the barcode it is expected to see the barcode on the printout, but you might not see the barcode printed on the

         printer, the reason as i understood is that based on the ZPL2 command the data should be marked with the start of data command and End of data

         command along with the type of barcode we are trying to print. so the commands should be inserted before and after the text node that holds

          the 2D data content. This will give the printer a command saying that the data between this is to be printed as the barcode symbology specified in

          the command, in our case Data Matrix.

          Note : Preview will not show the barcode because literally this barcode is not in SAP system and will only be printed on the printer. So anything

          concerning the barcode has to be tested on the actual printer not the preview because both the preview and the actual print will be a lot

          different.

• Create a command node before and after the text node that holds the 2D barcode content:

       See below screen shots for an example on how to create a command node.

        Then enter the prefix print control we created in the printer control input field (see below).

       Create one more command node under the 2d content text node and enter the enter the suffix print control in the printer control input

         field (see below)

        Now test the print on the Zebra printer, the barcode should be printed on the zebra printer as shown in the screen shot below. Now take the

        printout and scan the barcode with any of the android apps or any barcode reader that support DMC barcode. Please note that the printout taken

        on your local printer from a scanned document wont be readable, so it is advised to test the barcode scanning from the actual printout or from the

        Scanned document on your computer.

        After scanning, the barcode should display all the 2D content .

Alignment issues with the 2D barcode:

          After the barcode is printed you might notice alignment issues on the label. To solve the alignment issues the following approach can be used.

          Go to Smartstyle you have used in the Smartform, select the respective paragraph format node you have assigned for the barcode. Here try

          changing the alignment and spacing values (see screen shot below) and try giving it a few trials. You will be able to align barcodes after a few

          combinations.

               Note:

               Please make sure you have enough space for the barcode when designing the layout. I mean if you are planning to have a barcode of size

               1 CM * 1 CM then make use you have a separate window on the layout with space more than the barcode size.

                                                 ----------------  THE END  -----------------

Please note that the document is based on my personal experience and the online documentation i came across. So if there is any scope of improvements in this document you are most welcome.

MIRO T-code:

It is used for entering vendor invoice details received into SAP for incoming Invoice in SAP. All invoice details such as basic data, payment details, tax details etc. can be entered using this t-code. Once the user has input the details of the invoice at the basic data, he will go to the payment tab; there is a small icon to choose the bank account for the vendor.

Because of overlook of this icon (if there are multiple bank accounts or not), user may end up with failed wires (wrong currency paid to the bank account) and this may result in bad consequences as vendor received lesser $ for the exchange rate different.

Requirement:

To display a warning/information message if the vendor has more than one bank account, so that the user can select the correct bank account from payment tab.

Solution:

Once a user enters a Date, PO number and hits ENETER

• The system will check in background whether the relevant vendor has more than one bank account or not from Table LFBK

• If that vendor has more than one BANK account in table LFBK, a warning popup will be displayed.

For this the BADI ‘MRM_HEADER_CHECK’ was implemented.

MRM_HEADER_CHECK:

Along with the checks in the standard system when entering invoices in the Logistics Invoice Verification, you can use the BADI MRM_HEADER_CHECK to execute customer-specific checks for header and item data of an invoice document. Depending on the checks, the system may, for example, issue an error message or call other transactions.

Step 1:

Go to T-code se-18 and give the BADI name to be implemented.

Step 2:

Implement the BADI using Implementation option as below –

Step 3:

Implement the logic in your z implementation of BADI in following way –

The class has following parameters:

You can implement the logic in based on the vendor number (LIFNR) passed in I_RBKPV parameter.

·         Select the bank details from LFBK table based on LIFNR in an internal table.

·         Describe the internal table, if there are more than one no of lines, issue the relevant message.

Following is code implemented -

Result-

An information message is displayed if the vendor has more than one bank account as below:

Due to the warning message the user will be warned of existing accounts of vendor so that he can check if the correct currency paid to the bank account before final posting.

To tackle a real world problem of the hiring department performing a new hire instead of a rehire for seasonal contractors, I decided to implement the Jaro-Winkler algorithm in SAP.   Since there is a policy to not store key information on contractors (such as SSN), there is only the ability to match on a person’s name.  Unfortunately, the name is not always typed correctly which leads to the inability to find a previous hire and this leads to hiring a new contractor instead of rehiring a contractor.  Using the Jaro-Winkler algorithm, we are now able to suggest possible similar contractors based on the string comparison of first and last name.  Jaro-Winkler calculates the distance (a measure of similarity) between strings.  The measurement scale is 0.0 to 1.0, where 0.0 is the least likely and 1.0 is a positive match.  For our purposes, anything below a 0.8 is not considered useful.

“Jaro–Winkler distance (Winkler, 1990) is a measure of similarity between two strings”.

See Wiki link:  http://en.wikipedia.org/wiki/Jaro%E2%80%93Winkler_distance  for more in depth information.

The Class:  ZCL_JARO_WINKLER

Method: STRINGDISTANCE

method stringdistance.

  data: firstlen type i, secondlen type i, halflen type i, commonmatches type i, common1 type string, common2 type string.

  data: transpositions type i, i type i, j type i.

  if ( not ( firstword is initial ) and not ( secondword is initial ) ).

    if ( firstword eq secondword ).

      stringdistance = totalmatchscore.

    else.

      firstlen = strlen( firstword ).

      secondlen = strlen( secondword ).

      halflen = zcl_jaro_winkler=>math_min( num1 = firstlen num2 = secondlen ) / 2 + 1.

      common1 = zcl_jaro_winkler=>getcommoncharacters( firstword = firstword secondword = secondword distance = halflen ).

      commonmatches = strlen( common1 ).

      if ( commonmatches eq 0 ).

        stringdistance = totalmismatchscore.

      else.

        common2 = zcl_jaro_winkler=>getcommoncharacters( firstword = secondword secondword = firstword distance = halflen ).

        if ( commonmatches ne strlen( common2 ) ).

          stringdistance = totalmismatchscore.

        else.

          transpositions = 0.

          i = 0.

          while ( i lt commonmatches ).

            if ( common1+i(1) ne common2+i(1) ).

              transpositions = transpositions + 1.

            endif.

            i = i + 1.

          endwhile.

          transpositions = transpositions / 2.

          stringdistance

               = commonmatches / ( 3 * firstlen ) + commonmatches / ( 3 * secondlen ) + ( commonmatches -transpositions ) / ( 3 * commonmatches ).

        endif.

      endif.

    endif.

  else.

    stringdistance = totalmismatchscore.

  endif.

endmethod.

Method: GETCOMMONCHARACTERS

method getcommoncharacters.

  data: firstlen type i, secondlen type i, i type i, j type i, ch type c, foundit type c, secondword_copy type string.

  data: first_half type string, second_half type string, next_start_point type i, remaining_length type i.

  if ( not ( firstword is initial ) and not ( secondword is initial ) ).

    secondword_copy = secondword.

    firstlen = strlen( firstword ).

    secondlen = strlen( secondword ).

    i = 0.

    while i lt firstlen.

      ch = firstword+i(1).

      foundit = bool_false.

      j = zcl_jaro_winkler=>math_max( num1 = 0 num2 = ( i - distance ) ).

      while ( ( foundit = bool_false ) and ( j lt zcl_jaro_winkler=>math_min( num1 = ( i + distance ) num2 = secondlen ) ) ).

        if ( secondword_copy+j(1) eq ch ).

          foundit = bool_true.

          concatenate commons ch into commons.

          move secondword_copy+0(j) to first_half.

          remaining_length = ( secondlen - j ) - 1.

          next_start_point = j + 1.

          move secondword_copy+next_start_point(remaining_length) to second_half.

          concatenate first_half '#' second_half into secondword_copy.

        endif.

        j = j + 1.

      endwhile.

      i = i + 1.

    endwhile.

  else.

    clear commons.

  endif.

endmethod.

Creating a test program:

This test program requires that a first name and last name be input by the user and then these names are compared against every employee for possible matches.

    loop at t_pa0002 assigning <fs>.

      translate <fs>-nachn to upper case.

      translate <fs>-vorna to upper case.

      move <fs>-nachn to l_compare.

      call method zcl_jaro_winkler=>stringdistance

        exporting

          firstword      = s_nachn

          secondword     = l_compare

        receiving

          stringdistance = <fs>-nachn_score.

      move <fs>-vorna to l_compare.

      call method zcl_jaro_winkler=>stringdistance

        exporting

          firstword      = s_vorna

          secondword     = l_compare

        receiving

          stringdistance = <fs>-vorna_score.

      <fs>-total_score = <fs>-nachn_score + <fs>-vorna_score.

    endloop.

    sort t_pa0002 by total_score descending.

    format color col_normal.

    write: 80 'Total Score      ' color col_total.

    uline.

    loop at t_pa0002 assigning <fs>.

      write: / <fs>-nachn(20), <fs>-nachn_score, <fs>-vorna(20), <fs>-vorna_score.

      write 80 <fs>-total_score color col_total.

    endloop.

Deliberately misspelling my last name and shortening my first name:

Results:

I only show the top three results.  In fact, since I’m creating a combined score of two different measurements, I would likely consider anything below a 1.60 as not useful in real world.  So now we have a safeguard to alleviate hiring when we should be re-hiring.  Of course, there are many uses for this algorith, such as zip code verification for zip+4.  Also, another use is using as a dictionary check for valid words.

Following t-codes are available to use validation or substitution functions:

·         GGB0     Validation Maintenance

·         GGB1     Substitution Maintenance

·         GCVZ     Rule Maintenance

·         GGB4     Select action for validation/substitution, for example, activation of application areas, message usage or substituted fields

·         GCX2     Definition of Includes for User Exits

·         OB28     Activation of FI validations

·         OBBH     Activation of FI substitutions

·         OBBZ     Activation of cost of sales accounting substitution (in the FI area)

·         OKC7     Activation of CO validations

·         OKC9     Activation of CO substitutions

·         GCT9     Transport: Validations

·         GCT0     Transport: Substitutions

To add validation, we take GGB0 in account.

Scenario:

To display a warning/information message in f-43, if the vendor has more than one bank account, so that the user can select the correct bank account of vendor.

Step 1-

Go to GGB0 and create your validation. Here you have 3 things –

·         Prerequisite

·         Check

·         Message

You can relevant prerequisite for your validation, a check and the message you want to display on the check.

Following is the validation step for the taken scenario –

In financial accounting,

Select line item level and create validation

Step 2:

You can now implement your validation/exit through the program RGGBR000. For this, you should copy it into the customer namespace, for example ZGGBR000.

The length of the name you choose should not exceed 8 characters.

Step 3:

To define your new user exit, you have to enter your user exit in the form routine GET_EXIT_TITLES.

Step 4:

Implement your logic in your exit routine as below –

Step 5:

Once you have implemented your logic, you need to activate your exit and define a call up point (header or line item). This is done using t-code OB28 as shown below –

Once you validation has entry here, it will be triggered. In taken scenario, while posting in F-43,

If vendor has more than one bank account, a warning message should be displayed. For the applied logic, please see the result below.

This Documents Defines what is BOM and Creation of BOM in ECC (CS01) with sample Test Case.

Definition of BOM:

For manufacturing a product or assembling, list of several components (part of product) are needed.

A well-structured list of Items or Components is known as BOM - Bill of Material.

The list will contain object number of each components and its unit of measure with quantity.

A finished product is a combination of several different component parts or Materials.

Types of BOM available in SAP

You can create the following BOMs in the SAP system:

• Material BOMs
• Equipment BOMs
• Functional location BOMs
• Document structures
• Order BOM
• Work breakdown structure (WBS) BOM

BOM can be act as basic for several activities in Production department , some of the examples are :

1.MRP Department:

BOM data can be used to calculate cost-effective order quantities for materials.

2.Work scheduling department:

BOM data can be used for operation planning and control.

3.Production order management department:

          BOM data can be used to plan the provision of materials.

3. Sales Order

4. Reservation

5. Product Costing

BOM Usage :

It is a Key which defines different areas of a Company where the BOM can be used.

BOM Item Category :

Categorization of the items in a BOM according to set criteria, such as whether they refer to an object or whether they are kept in stock.

• This categorization allows you to process data that is relevant to the individual items in a BOM. The item category is used to control field selection, default values for BOM maintenance, triggering of specific system activities, and so on.

• For Example Documentation Item, Stock Item, Packing Item.

• SAP R/3 system allows you to create individual BOM depending upon the area in your company.

Define BOM Usages:

1. In Customizing for Production, define individual BOM usages for the different areas within your company by choosing Basic data -->Bill of Material --> General data -->BOM usage -->Define BOM usages.

You can define BOM usages for the following scenarios:

• You maintain separate BOMs for different areas within your company, such as design or production.
• You create just one BOM for all areas within your company.

Alternative BOM:

• Alt BOM is used to define BOM in a BOM group.

• By default system will consider next ALT. BOM Number if user won’t enter any Alt BOM Number.

• If user enter any Alt. BOM , then system will validate Alt BOM.

Structure of a BOM:

BOM data is structured as below,

BOM Header:

•      BOM Header consists of DATA Related to BOM, which consists of Plant, Material,Technical Type, Revision Label, etc…

•      BOM Header maintains data refer to entire object .

•      Refer to single Header Multiple BOM’s would be created which will be maintained by ALT BOM.

BOM Item :

Each part of a final Product is called BOM Item , A product is a collections BOM Items .It consists of Item Number, component Quantity , Item Category, Unit of Measure, Item id .

Sub Items:

Partial quantities of a BOM item may be installed at different points. Sub-items are used to describe the different installation points of these partial quantities. Sub-items have no operational function in the BOM.              

BOM Creation in SAP ECC

Transaction for BOM creation  is CS01 .

1.Initial Screen for BOM creation :

Mandatory Fields for entering into next screen are Material, Plant and BOM Usage as per Requirement and by default Alt will pick up as next value to available Alt BOM.

Click on Header Icon for header details :

As shown below by default system with Pick 1 as base Qty and Base UOM will be picked from Material Base UOM.

Create BOM Items :

Enter Item Components along with component Qty,UOM,Item Category as shown below.

BOM Creation Sample Code in ECC :

Scenario :

Create material  BOM along with items and define Procustion Version .

Define ztables and structure as per the requirement .

Create a class and method for BOM creation with Importing Parameters and exporting parameters as :

I_BOM HEADER

I_BOM_ITEMS

E_RETURN

*Data Declarations

  DATA : lit_bom_header     TYPE TABLE OF zsbom_header,

         wa_bom_header        TYPE zsbom_header,

         wa_bom_head           TYPE zsbom_header,

         lit_bom_head            TYPE TABLE OF zsbom_header,

         wa_bom_h                TYPE zsbom_header,

         lit_bom_items           TYPE TABLE OF ztbom_items,

         wa_bom_items         TYPE ztbom_items,

         wa_bom_i                 TYPE zsbom_items,

         lit_bom_items_table   TYPE TABLE OF zsbom_items,

         lit_bom_item_table     TYPE TABLE OF zsbom_items,

         wa_bom_item_table   LIKE LINE OF lit_bom_item_table,

         lit_cost_bom_items   TYPE TABLE OF ztt_bom_item,

         lit_bom_item             TYPE ztbom_items,

         i_mast              TYPE  TABLE OF mast,

         lv_role             TYPE zrole,

         lv_verid            TYPE mkal-verid,

         lv_verid1           TYPE mkal-verid,

         lv_bstma            TYPE char13,

         lv_bstmi            TYPE char13,

         lv_stlal            TYPE stlal,

         lv_idnrk            TYPE idnrk,

         lv_flag             TYPE char1,

         lv_phassign(4)      TYPE c,

         lv_ph_desc          TYPE string,

         wa_error            TYPE bapiret2,

         lit_error           TYPE TABLE OF bapiret2,

         persistent_ref      TYPE REF TO zcl_d_persist_bom,

         obj_ref             TYPE REF TO zcl_d_bom,

         l_msg               TYPE bapiret2-message,

         l_warnings          TYPE capiflag-flwarning,

         l_stpo              TYPE TABLE OF stpo_api02,

         wa_stpo             LIKE LINE OF l_stpo,

         l_stko              TYPE TABLE OF stko_api02,

         lv_matnr            TYPE csap_mbom-matnr,

         timestamp           TYPE tzonref-tstamps,

         obj_bom             TYPE REF TO zcl_d_bom.

  TYPES : BEGIN OF ty_mast,

              matnr TYPE mast-matnr,

              werks TYPE mast-werks,

              stlan TYPE mast-stlan,

              stlal TYPE mast-stlal,

            END OF ty_mast.

  DATA : lit_mast  TYPE STANDARD TABLE OF ty_mast,

         wa_mast   TYPE ty_mast,

         lit_mast1 TYPE TABLE OF mast,

         lv_index  TYPE sy-tabix,

         lv_itmid  TYPE bapi1080_itm_c-item_id.

  DATA : bom_items         TYPE STANDARD TABLE OF zsbom_items,

         lit_bom_item_temp TYPE  STANDARD TABLE OF zsbom_items.

  DATA : lit_stas  TYPE TABLE OF stas,

         wa_stas   TYPE stas,

         lit_ausp  TYPE TABLE OF ausp,

         wa_ausp   TYPE ausp,

         wa_mast1  TYPE mast,

         lit_stpo1 TYPE TABLE OF stpo,

         wa_stpo1  TYPE stpo,

         lit_inob  TYPE TABLE OF inob,

         wa_inob   TYPE inob.

  DATA : lv_objek   TYPE inob-objek,

         lv_date    TYPE rn1datum-datex,

         lv_stlnr   TYPE mast-stlnr,

         lv_counter TYPE i.

  DATA : lit_bom_hrep      TYPE TABLE OF ztbom_head_rep,    "Historical Report declarations

         wa_bom_hrep        TYPE ztbom_head_rep,

         wa_bom_hrep1       TYPE ztbom_head_rep,

         lit_bom_hist_temp  TYPE TABLE OF ztbom_head_rep,

         wa_bom_hist_temp  TYPE ztbom_head_rep,

         wa_bom_hist_temp1 TYPE ztbom_head_rep,

         lit_ampl          TYPE TABLE OF ampl,

         wa_ampl           TYPE ampl,

         lit_bom_irep      TYPE TABLE OF zsbom_i_report,

         wa_bom_irep       TYPE zsbom_i_report,

         wa_bom_itemrep    TYPE ztbom_item_rep,

         lit_hist_msg      type ztd_hist_msgs,

         wa_hist_msg       type ztd_hist_msgs.

* internal table that have to be passed to the bapi

          DATA :  lit_bomgroup TYPE STANDARD TABLE OF bapi1080_bgr_c,

                  wa_bomgroup   TYPE bapi1080_bgr_c,

                  lv_bom_text   TYPE string,

                  lv_plant      TYPE ztbom_header-werks,

                   lit_variants TYPE STANDARD TABLE OF bapi1080_bom_c,

                   wa_variants  TYPE bapi1080_bom_c,

                   lit_items    TYPE STANDARD TABLE OF bapi1080_itm_c,

                   wa_items     TYPE bapi1080_itm_c,

                   lit_matrel   TYPE STANDARD TABLE OF bapi1080_mbm_c,

                   wa_matrel    TYPE bapi1080_mbm_c,

                   lit_itemas   TYPE STANDARD TABLE OF bapi1080_rel_itm_bom_c,

                   wa_itemas    TYPE bapi1080_rel_itm_bom_c.

*-->Check BOM Existency

          CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'

            EXPORTING

              input  = i_bom_header-matnr

            IMPORTING

              output = lv_matnr.

          SELECT SINGLE stlnr FROM mast INTO lv_stlnr WHERE matnr = lv_matnr

AND werks = i_bom_header-werks

AND stlal = i_bom_header-stlal AND stlan = '1'.

          IF lv_stlnr IS  INITIAL.

*  assign bom usage to 1.

            IF wa_bom_h-stlan IS INITIAL.

              wa_bom_h-stlan = zif_d_constant=>c_production_bom_usg.

            ENDIF.

* assign bom text bases on condition

            lv_plant = wa_bom_h-werks.

            IF lv_plant+0(2) = '10'.

              CONCATENATE 'BOM For' wa_bom_h-maktx INTO lv_bom_text SEPARATED BY space.

            ELSE.

              lv_bom_text = ' ' .

            ENDIF.

wa_bomgroup-bom_group_identification = 'BAPI_SMP_COL1'.

            wa_bomgroup-object_type = 'BGR'.

            wa_bomgroup-object_id = 'SIMPLE1'.

            wa_bomgroup-bom_usage = wa_bom_h-stlan.

            wa_bomgroup-created_in_plant = wa_bom_h-werks.

            wa_bomgroup-ltxt_lang = sy-langu.

            wa_bomgroup-technical_type = ' '.

            wa_bomgroup-bom_text = lv_bom_text.

            APPEND wa_bomgroup TO lit_bomgroup.

            IF wa_bom_h-datuv IS INITIAL.

              wa_bom_h-datuv = sy-datum.

            ENDIF.

*UOM Conversion :

            CALL FUNCTION 'CONVERSION_EXIT_CUNIT_INPUT'

              EXPORTING

                input          = wa_bom_h-bmein

              IMPORTING

                output         = wa_bom_h-bmein

              EXCEPTIONS

                unit_not_found = 1

                OTHERS         = 2.

*Define Varaints

wa_variants-bom_group_identification = 'BAPI_SMP_COL1'.

            wa_variants-object_type              = 'BOM'.

            wa_variants-object_id                = 'SIMPLE1'.

            wa_variants-alternative_bom          = wa_bom_h-stlal.

            wa_variants-bom_status               = wa_bom_h-stlst.

            wa_variants-base_qty                 = wa_bom_h-bmeng.

            wa_variants-base_unit                = wa_bom_h-bmein. " base unit

            wa_variants-alt_text                 = wa_bom_h-alternate_text.   " alternative text

            wa_variants-valid_from_date          = wa_bom_h-datuv.

            wa_variants-function = 'NEW'.

            APPEND wa_variants TO lit_variants.

            CLEAR lv_itmid.

            LOOP AT bom_items INTO wa_bom_i.

              CLEAR wa_items.

              MOVE-CORRESPONDING wa_bom_i TO wa_bom_items.

              IF wa_bom_items-posnr IS INITIAL.

                wa_bom_items-posnr = '0010'.

              ENDIF.

              IF wa_bom_items-postp IS INITIAL.

                wa_bom_items-postp = 'L'.

              ENDIF.

              IF wa_bom_items-datuv IS INITIAL.

                wa_bom_items-datuv = sy-datum.

              ENDIF.

              CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'

                EXPORTING

                  input        = wa_bom_items-idnrk

                IMPORTING

                  output       = wa_bom_items-idnrk

                EXCEPTIONS

                  length_error = 1

                  OTHERS       = 2.

* Details of the items of the variants

*to convert the uom for bom item

              CALL FUNCTION 'CONVERSION_EXIT_CUNIT_INPUT'

                EXPORTING

                  input          = wa_bom_items-meins

                  language       = sy-langu

                IMPORTING

                  output         = wa_bom_items-meins

                EXCEPTIONS

                  unit_not_found = 1

                  OTHERS         = 2.

              CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'

                EXPORTING

                  input  = wa_bom_items-vendor_no

                IMPORTING

                  output = wa_bom_items-vendor_no.

              wa_items-bom_group_identification = 'BAPI_SMP_COL1'.

              wa_items-object_type              = 'ITM'.

              wa_items-object_id                = 'SIMPLE1'.

              wa_items-item_no                  = wa_bom_items-posnr.

              wa_items-item_cat                 = wa_bom_items-postp ."Item Category

              wa_items-comp_unit                = wa_bom_items-meins. " bom uom added

              wa_items-alt_item_prio            = wa_bom_items-alprf. " priority added

              wa_items-usage_prob               = wa_bom_items-ewahr. " usage probability added

*-->Sort String

              IF wa_bom_items-sortf IS NOT INITIAL.

                wa_items-sort_string              = wa_bom_items-sortf." sort string added

              ELSE.

                SPLIT wa_bom_items-zph_assign AT '-' INTO lv_phassign lv_ph_desc.

                CONDENSE lv_ph_desc.

                wa_items-sort_string              = lv_ph_desc .

              ENDIF.

*-->End of Sort String

              wa_items-component                = wa_bom_items-idnrk.

              wa_items-comp_qty                 = wa_bom_items-menge.

              wa_items-item_text1               = wa_bom_items-ktext. "Bom component description added

              wa_items-alt_item_group           = wa_bom_items-alpgr.  " Bom Alt Item Group

              wa_items-valid_from_date          = wa_bom_items-datuv.

              wa_items-iss_st_loc               = wa_bom_items-lgort."storage plant

*-->Alt Item Strategy

              IF wa_items-alt_item_group IS NOT INITIAL.

                wa_items-alt_item_strategy = '2'. "Alt Item Strategy

              ELSE.

                wa_items-alt_item_strategy = ' '.

              ENDIF.

              IF wa_bom_items-idnrk CP '35*'.

                wa_items-class_type        = '023'.

                wa_items-vendor_no         = wa_bom_items-vendor_no.

              ENDIF.

              APPEND wa_items TO lit_items.

              CLEAR  wa_items.

            ENDLOOP.

            CLEAR lv_itmid.

            CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'

              EXPORTING

                input        = wa_bom_h-matnr

              IMPORTING

                output       = wa_bom_h-matnr

              EXCEPTIONS

                length_error = 1

                OTHERS       = 2.

*creation of production BOM

            IF wa_bom_h-stlan IS INITIAL.

              wa_bom_h-stlan = 1.

            ENDIF.

*--From Lot size and to size------------*

            IF i_bom_header-werks CP '10*'.

              lv_bstmi = zif_d_constant=>c_bstmi.  "BASE QUANTITY

              lv_bstma = zif_d_constant=>c_bstma.

              CONDENSE lv_bstma.

              CONDENSE lv_bstmi.

            ELSE.

              lv_bstmi = zif_d_constant=>c_bstmi.

              lv_bstma = zif_d_constant=>c_bstma.

              CONDENSE lv_bstma.

              CONDENSE lv_bstmi.

            ENDIF.

* Details of the materials of the different variants

            wa_matrel-bom_group_identification = 'BAPI_SMP_COL1'.

            wa_matrel-material                 = wa_bom_h-matnr.

            wa_matrel-plant                    = wa_bom_h-werks.

            wa_matrel-bom_usage                = wa_bom_h-stlan.

            wa_matrel-alternative_bom          = wa_bom_h-stlal.

            wa_matrel-lot_size_from            = lv_bstmi.

            wa_matrel-lot_size_to              = lv_bstma.

            APPEND wa_matrel TO lit_matrel.

* Linking items to the corresponding variants

            wa_itemas-bom_group_identification = 'BAPI_SMP_COL1'.

            wa_itemas-sub_object_type          = 'ITM'.

            wa_itemas-sub_object_id            = 'SIMPLE1'.

            wa_itemas-super_object_type        = 'BOM'.

            wa_itemas-super_object_id          = 'SIMPLE1'.

            wa_itemas-valid_from_date          = wa_bom_items-datuv.

            wa_itemas-function                 = 'NEW'.

            APPEND wa_itemas TO lit_itemas.

* call function to create bill fo materail by using

* the previously declared local internal tables

            SORT lit_items BY object_id valid_from_date.

            CALL FUNCTION 'BAPI_MATERIAL_BOM_GROUP_CREATE'

              EXPORTING

                all_error         = 'X'

              TABLES

                bomgroup          = lit_bomgroup

                variants          = lit_variants

                items             = lit_items

                materialrelations = lit_matrel

                itemassignments   = lit_itemas

                return            = e_return.

            CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

*----END OF Production BOM CREATION-----------------------*

References:

http://braincybersolutions.com/sap-tutorials/pp/bom-in-sap-bill-of-material/

http://help.sap.com/saphelp_46c/helpdata/en/ea/e9af734c7211d189520000e829fbbd/frameset.htm

The purpose of this document is to compare the versions of smart forms in different servers. This document is highly beneficial for Developers in ABAP which explains a step by step procedure to compare the versions of the forms.

INTRODUCTION:

Smartform has only one active version, in the form of function module which is regenerated once you change and activate it. Since smartform is client Independent, it can be easily transported to other systems. There may be cases where we would require to compare the versions of the forms across different systems. Though it is not possible to compare the forms directly, it can be achieved to some extent by comparing the generated Function modules line by line, thereby capturing the changes. This can be done via the Transaction SE39-Split Screen editor.

Note that the generated Function Module names will not be same across all systems.

PROCEDURE:

Once the smartform is created and activated, a Function Module gets generated.

To open the Function Module in display mode, either execute the Smartform or go via Transaction SE37 by fetching the FM name from Environment menu.FM will be opened in display mode as follows.

Select the Attributes tab and double click on the program name.

The following screen appears with the list of file names. Select the required Include name under User defined Files.

Similarly, the include name is fetched from the other server that needs to be compared.

Now, go to transaction code SE39.The following screen appears.

Click on the option ‘Compare different Systems’.

Enter appropriate include names and details of the systems that needs to be compared.

Enter the logon details of the system to be compared.

Comparison screen appears. Click on the ‘Comparison On’ button to initiate the process.

Select ‘Next Difference from cursor ‘, Next Identical section from cursor’ options to analyze the variations and the same procedure is carried out till the end.           

There is no option to compare the forms directly. But, the entire list of requests available for a smartform can be obtained from which the number of changes done can be captured.

Go to transaction SE03. Select the option ‘Objects in Requests’.  Double click on Search for objects in Requests/Task.

The screen appears as below. In the Object Selection type, enter the Object type as ‘SSFO’ and give the smartformname and then Execute.

List of all the Requests related to that smartform are displayed from which the changes can be traced.

Summary

Shared Objects are objects in the shared memory. The shared memory is a memory area on an application server, which is accessed by all of this server’s ABAP programs. In this article I am giving a brief idea on Shared Memory-enabled Classes, ‘Create Data – Area Handle’ statement and read/write of shared objects. Sufficient screenshots and sample codes are also provided.

Author: Abyson Joseph Chavara         

Company: Applexus Technologies (P) LTD

Created on:  02 April 2012

Introduction

Shared Objects are objects in the shared memory. The shared memory is a memory area on an application server, which is accessed by all of this server’s ABAP programs. Before shared objects were implemented, ABAP programs could access this memory area using the EXPORT and IMPORT statements exclusively, but this method was very slow because the "sending" program had to copy variables from its memory to the shared memory, and the "receiving" program had to copy these variables from the shared memory into its own program memory. This generated two copies for basically nothing.  With the implementation of shared objects with Release 6.40, the shared memory was enhanced with the shared objects memory that stores shared objects. Shared objects are stored in what are called shared memory areas. You create and manage areas and their properties using Transaction SHMA.

The benefits of shared objects includes Copy-free: very fast access, version management, preloading, automatic propagation from a database, easy monitoring, etc. In this article I am giving a brief idea on Shared Memory-enabled Classes, ‘Create Data – Area Handle’ statement and read/write of shared objects. Sufficient screenshots and sample codes are also provided.

Shared Memory-enabled Classes

The prerequisite for storing an instance of a class in the shared memory is that the class of the object has to be defined with the SHARED MEMORY ENABLED addition of the CLASS statement, or that the property Shared memory-enabled has to be selected in the Class Builder. Each area is linked with what is called a global area root class, which can contain separate data and references to other instances of shared memory-enabled classes or to anonymous data objects in its own attributes.

Area Classes and Area Handles

When an area is defined in Transaction SHMA, a global and final area class with the same name is generated as a subclass of CL_SHM_AREA. Class CL_SHM_AREA itself is a direct subclass of CL_ABAP_MEMORY_AREA. In an ABAP program, an area is accessed exclusively using the methods of the generated area class. There are static methods for binding an ABAP program (or its internal session) to area instances in the shared memory (attach methods). Binding creates an instance of the area class as an area handle, and creates a lock at the same time. The ABAP program can access the bound area instance version using the area handle and thus access the shared objects that are stored there. The area handle also contains the methods for deleting the connection or the lock (detach methods).

CREATE DATA - AREA HANDLE

This statement creates an anonymous data object as shared object in the area instance version of the shared memory, which is bound to the area handle referenced by handle. For handle, an object reference variable must be specified; whose static type is CL_ABAP_MEMORY_AREA or one of its subclasses (area class). When the statement is executed, handle must point to an area handle and the area handle must be bound to an area instance version with a change lock. To create such a reference, you have the following options:

• Transfer of the return value of the methods ATTACH_FOR_WRITE or ATTACH_FOR_UPDATE of an area class created with SHMA.

• Transfer of the return value of the method GET_HANDLE_BY_OREF of any area class.

• Transfer of the return value of the method GET_IMODE_HANDLE of the predefined class CL_IMODE_AREA.

The latter is a reference to an area handle for the current internal mode and the statement CREATE DATA acts like without the addition AREA HANDLE.

Example 1

Here is a very simple example showing the steps to create the root class, shared area, and the use of CREATE DATA - AREA HANDLE statement.

Step 1: Creating Root class

First of all we have to create a Root class. Go to SE24 and create a new class. Here I have given the name 'ZCL_SHR_AREAHANDLE_ROOT'. Go to the properties tab and check the box Shared Memory -Enabled, as shown in the below image.

Step 2: creating attributes

Now go to the attributes tab and create 2 attributes. Here I have named as ‘id_num’, level as instance attribute, visibility as public, associated type as STRING and second one named as ‘dref’, level as instance attribute, visibility as public, associated type as DATA (for Area Handle).  See image below.

Step 3: Assign Interface.

Go to the tab interface and assign the interface “IF_SHM_BUILD_INSTANCE” and activate the class.

Step 4: Creating Area (SHMA)

Now run transaction SHMA and create a area named 'zcl_shr_areahandle_area'. Give 'zcl_shr_areahandle_root' as root class and constructor class. Check the box 'Aut. Area Creation' and 'With Versioning'. Select 'Displacement Not Possible' for 'Displacem. Type' field and 'Autostart for Read Request and Every Invalidation' for 'Area Structure' field. Screen shot shown below.

Step 5: attach_for_write( )

Now go to SE38 and create  a program, for eg. 'ZCL_SHR_AREAHANDLE_SET'. After creating an area handle referenced from 'v_area_handle', an instance of the area root class 'zcl_shr_areahandle_root' of the area is created. In area root class, we have already created a generically typed (using REF TO data) data reference variable named 'dref' as public attribute. With CREATE DATA, you create an anonymous data object in the area instance version, which is fed with a value after it has been assigned to a field symbol.  The sample code is given below.

REPORT  zcl_shr_areahandle_set.

DATA: v_area_handle TYPEREFTO zcl_shr_areahandle_area,
v_root        TYPEREFTO zcl_shr_areahandle_root.

FIELD-SYMBOLS <fs_data> TYPEANY.

TRY.
v_area_handle = zcl_shr_areahandle_area=>attach_for_write( ).

CREATE OBJECT v_root AREA HANDLE v_area_handle.

v_area_handle->set_root( v_root ).

*dref is the attribute created in root class.

CREATEDATA v_root->dref AREA HANDLE v_area_handle TYPE string.

ASSIGN v_root->dref->* TO<fs_data>.

<fs_data> = '700'.

v_area_handle->detach_commit( ).


CATCH cx_shm_external_type.

CATCH cx_shm_attach_error.

ENDTRY.

Step 6: attach_for_read( )

We can access the shared object, in another program. For that, create another program in SE38 named for eg. 'zcl_shr_areahandle_get'. Sample code given below.

REPORT  zcl_shr_areahandle_get.

DATA v_area_get TYPEREFTO zcl_shr_areahandle_area.

FIELD-SYMBOLS <fs_get> TYPEANY.

TRY.
v_area_get = zcl_shr_areahandle_area=>attach_for_read( ).

ASSIGN v_area_get->root->dref->* TO<fs_get>.


WRITE:/  <fs_get>.

v_area_get->detach( ).

CATCH cx_shm_attach_error.

ENDTRY.

You can see the output as displayed below.

Example 2

In the next example we will add two methods to the root class, for writing and reading values to the shared object.

Step1: Adding methods

Go to the methods tab of the root class. You can see method 'IF_SHM_BUILD_INSTANCE~BUILD' is added automatically. Create two more methods named 'GET_ID_NUM' and ‘SET_ID_NUM’. Set the level and visibility attributes as shown in the image below.

Step 2: Adding parameters to methods

Add a parameter l_msg to the method  'GET_ID_NUM’, type as Returning, as shown below.

Also add a parameter l_id_num to the method 'SET_ID_NUM', type as Import, and associated type as string.

Step 3:  Area constructor

Double click on the method 'IF_SHM_BUILD_INSTANCE~BUILD’ and add the following code between the 'method IF_SHM_BUILD_INSTANCE~BUILD' and 'endmethod' statements and save.

DATA: sh_area TYPEREFTO zcl_shr_areahandle_area,
sh_root TYPEREFTO zcl_shr_areahandle_root.

* Get a pointer to shared area
sh_area = zcl_shr_areahandle_area=>attach_for_write( ).

* Create an instance of the root
CREATE OBJECT sh_root AREA HANDLE sh_area.

* Sets Intial values
sh_root->set_id_num( '999' ).

* set the root back into the area
sh_area->set_root( sh_root ).

* Commit and detach
sh_area->detach_commit( ).

Step 4: Adding code lines in Methods.

Double click on the method 'SET_ID_NUM' and enter the following code between 'method SET_ID_NUM' and 'endmethod' statement and save.

id_num = l_id_num.

Next double click on the 'GET_ID_NUM' method and enter the following code between 'method GET_ID_NUM' and 'endmethod' statement, then save and activate.

DATA: lv_id_msg TYPE string.

* Concatenating a title to id_num.
CONCATENATE'Identification Number:' id_num
INTO lv_id_msg.
l_msg = lv_id_msg.

Step 5: 'attach_for_update( )'

Now we are going to set values to the memory by using the method 'attach_for_update'. (Remember we have already initialized the id_num using method 'attach_for_write' in the Area Constructor.) Go to SE38 and create a program named for eg. 'zcl_shr_areahandle_update' and enter the following code and execute.

REPORT zcl_shr_areahandle_update.

DATA: v_area TYPEREFTO zcl_shr_areahandle_area,
v_root TYPEREFTO zcl_shr_areahandle_root.

TRY.
v_area = zcl_shr_areahandle_area=>attach_for_update( ).

CATCH cx_shm_no_active_version.
WAITUPTO1 SECONDS.
v_area = zcl_shr_areahandle_area=>attach_for_update( ).

ENDTRY.

v_root ?= v_area->get_root( ).

IF v_root ISINITIAL.

CREATE OBJECT v_root AREA HANDLE v_area.

ENDIF.

v_root->set_id_num( '800' ).

v_area->set_root( v_root ).

v_area->detach_commit( ).

Step 6: ' attach_for_read ( )'

Now we can read the memory from another program. Go to SE38 and create a new program named for eg. 'zcl_shr_areahandle_read' and enter the following code and execute.

REPORT  zcl_shr_areahandle_read.

DATA: v_area1 TYPEREFTO zcl_shr_areahandle_area.

TRY.
v_area = zcl_shr_areahandle_area=>attach_for_read( ).
CATCH cx_shm_no_active_version.
WAITUPTO1 SECONDS.
v_area = zcl_shr_areahandle_area=>attach_for_read( ).
ENDTRY.

DATA: v_msg TYPE string,
l_msg TYPE string.
v_msg = v_area->root->get_id_num( ).

WRITE: / v_msg.

v_area->detach( ).

You can see that v_msg will print the previously updated value '800' along with the concatenated string 'Identification Number:'

Related Content

http://help.sap.com/saphelp_nw70/helpdata/en/c5/85634e53d422409f0975aa9a551297/content.htm

http://help.sap.com/abapdocu_70/en/ABAPCREATE_DATA_AREA_HANDLE.htm

http://help.sap.com/saphelp_nw70/helpdata/en/df/109b8b4b073b4c82da0f2296c3a974/content.htm

Please find as attachment, the source codeand find the user manual(with links to download) below.

Note:

1. Check this document regularly for latest version source code as the functionality of this tool being improved further.
2. Please, rate this document as it will help others to prioritize this among the other available alternative methods to search relationships, on Google search.
   

________________________________________________________________________________________________________________________________________

SAP is like an ocean and often an ABAP consultant looses much of the time in finding relationships among tables and searching for fields, which causeshim/her unnecessary delays. Even SAP quick viewer and other SAP standard search methods doesn't provide him/her with accurate results always and many times they propose very large result set, most of which are irrelevant solutions for the queried scenario. Some problems, an ABAP consultant would usually encounter are:

For example:

1. To search for direct relationships between tables 'EBAN' and 'T16FS', the easy method is to go for SAP Quick Viewer (SQVI). But SQVI shows relationships only if the field names, data elements or domains match. So, in this case it shows only one relationship i.e, between FRGGR fields of both the tables but it doesn't show relationship between fields FRGST and FRGSX of tables EBAN and T16FS respectively which can also be related, as both are ' Release strategies'.

2.  To search for indirect relationships (link tables) between two tables in the absence of direct relationships.For example, there are no direct relationships between tables 'VBAK' and 'EKKO' and there is no standard method or tool to find indirect relationships i.e., link tables between them than manually checking, which is cumbersome.

3. To search for the field with description 'Bill-to party', one usually goes for 'SE80' which is a case-sensitive search. That is, it would show only those fields with the given description in lower case alphabets when the search term is typed as 'bill-to party'. And most of the times a consultant would be aware of the field description but not the cases of alphabets in field description.

4. And moreover, with the usual standard methods an ABAPer uses,the result set would be huge with all SAP tables in which the relevant solutions for our scenario  is somewhere in the remote corner. It's like searching for 'Titanic' in Atlantic ocean. It would be more easy to search for 'Titanic' if the Atlantic would be of the size of Lake Superior. I.e., It would make the job of an ABAP consultant more easier if the search  can be carried out separately in each module or application area instead of all SAP.

                  With one and a half month effort I developed a tool (overcoming all these limitations and adding some more useful features) which I named as 'ABAPer's Tabloscope' can be a very useful assistant especially for an ABAP consultant.

                               USER MANUAL

The BADI(Business Add-in's) is an object-oriented enhancement option. The BADI defines an interface that can be implemented by BADI-implementations that are transport objects of their own. The new BADI or Kernel BADI is fully integrated into the Enhancement Framework. Within the Enhancement Framework a BADI is an enhancement option or an anchor point for an object plug-in.

Kernel BAdI's Features

• Are integrated directly in the ABAP Language/Runtime
• Improved filter support allows non-character filter types and complex filter conditions
• Enable reusable implementation instances (Stateful BAdI)
• Control of the lifetime of implementations (BAdI-context)
• Allow for inheritance of implementations
• Can be switched by the Switch Framework

In this document, I have demonstrated the various steps for creating a Kernel BADI and calling it in our own Custom program.

1. First  create a  Enhancement spot from SE18. Kernel Badi's belong to an enhancement spot.

Enhancement spots carry information about the positions at which enhancement options were created. One enhancement spot can manage several enhancement options of a Repository object. Conversely, several enhancement spots can be assigned to one enhancement option.

Enter the description and if you want you can assign the new enhancement spot to a composite enhancement spot. Composite enhancement spots are used for the semantic grouping of simple enhancement spots. A composite enhancement spot contains either one or more simple enhancement spots and/or one or more composite enhancement spots of the relevant type. You can use composite enhancement spots to combine simple enhancement spots into meaningful units.

2. On creating the Enhancement spot, you will be directed to Enhancement Spot Editor. Now we need to create a new BADI Definition.

3. Click on the create BADI button.

4. You will find certain options for the BADI definitions as below.

5. Now we need to add an interface to the BADI. Expand the Node of BADI definition name and double click on node Interface. You can either add existing interface or will be prompted to create.

6. On clicking ‘Yes’, you will be navigated to the below screen, where you can add a method to the new interface.

Save, activate and comeback to the BADI definition screen and activate the Enhancement Spot.

7. Next we need to implement the Enhancement spot and BADI. Right click on the BADI definition and select Create BADI Implementation.

8. First the system will ask for enhancement implantation name. Please enter a name and description.

9. Next it will ask for BADI Implementation name and Class name for implementing BADI. Enter the names and click ok.

10. Next we have to implement the interface method. Expand the BADI Definition name and double click on BADI implementation.

11. You will be directed to the enhancement implementation screen, shown below. Double click on the Interface method and you will be prompted to create implementation for the method.

12. On clicking yes, you will be navigated to editor for the method. Add the following code for showing a message or anything as per your requirement. Save it and activate.

So the BADI definition and implementation part is complete.

Next we will see how we can call this Kernel BADI in our Custom program.

13. Create or open an existing program in SE38. Point to the line where you need to add enhancement option. Right click and select Create Option.

14. Give an Enhancement point or section name and Enhancement spot implementation name. Here I have opted an Enhancement point and have entered Enhancement spot implementation name as ‘ZENH_IMP_TEST’ (which we have created before).

A new line will be added to the existing code as shown below.

15. Then add the below code which is shown in the red box below.

Apart from Classic BADI’s which are been called by Proxy class cl_exithandler, Kernel BADI’s are called directly with the reference to the BADI definition via GET BADI and CALL BADI statements.  That is one of the reasons why Kernel BADI is faster than classic BADI. Also in Classic BADI, while we call it via cl_exithandler,  we use the reference to the interface rather than BADI definition

16. Now activate the program and execute it. When the cursor reaches the enhancement point, where the BADI is called it will trigger all the active implementations of that BADI. Here we have only one implementation and that will be triggered, which shows the below message as we have written in the BADI implementation.

If the program fails to trigger the BADI implementation, please recheck whether everything associated with it is ‘Activated’ after the creation.

Thank You.

Objective: To generate the formatted excel file which can be send or download as per below requirement.

1: User should able to download excel file when using GUI and execute in foreground mode.

2: When sending the email in foreground as well as if email is send in with background job.

3:When the ECC transaction is use as transaction launcher in SAP CRM the excel file should get generated same as it is working in SAP ECC, as in case of Transaction launcher it works as web page.

Advantage of using XML over OLE: As we can use the OLE method in ABAP to generate formatted excel but its work only in GUI foreground mode, where as we can use ‘xml’ concept in foreground as well as in background jobs for sending email etc.

Example:  I have made the transaction in ECC which takes input as Year and display all the dates with weekday and in case of weekly off i.e Saturday and Sunday the background color of the cell will be green.

If user select the first option ‘Download Excel’ system will generate the excel file, presently I have kept the excel file in temp folder and same I have executed if file save successfully and in case of ‘Send email’ system will send the same file as email attachment.

Note :  1:We cannot save the file in any PC folder in background but we can save on app. Server using open data set method.

             2: I have not added the code for email in my example we can check demo program BCS_EXAMPLE_7 to send file as email attachment.

             3: I have made this program by refereeing the existing SDN doc.   

http://wiki.scn.sap.com/wiki/display/Snippets/Formatted+Excel+as+Email+Attachment, I have use same for downloading the file in ECC frontend as well as when same is used in CRM WEB UI as transaction launcher.

              4: For checking this you can upload the attach program in your system and can check the same.

Output:

Find here the attach file of program.

Scope :

The purpose of this document is to display radio buttons in ALV grid.

Business requirement :

Consider a scenario where the screen needs to be displayed with a list of accounting document numbers, fiscal year and company code. By Selecting one option at a time, it should navigate to the next screen (FB03) with the corresponding details of that selected accounting document number.

SAP ALV Limitation :

As radio button is nowhere included in as a genuine feature of ALV grid, it is a bit tricky. We can implement the same by using the corresponding ICON and HOTSPOT_CLICK event.

Workaround:

In this case from a report program we are calling screen where ALV Grid is displayed.

In the report program write the below code:

1. 1. Declaration:

Create a top include in the report program. Add below lines of code:

TYPE-POOLS: slis.

INCLUDE <icon>.

Internal table structure:

As mentioned in the scenario with accounting document number, fiscal year and company code, radio button should be get displayed. So in top of program only structure of internal table will be of following type:

TYPES:BEGIN OF ty_view,
        bukrs TYPE bukrs,
        belnr TYPE belnr_d,
        gjahr TYPE gjahr,
        radio(4) TYPE c,
        handle_style  TYPE lvc_t_styl,
        END OF ty_view.

Make this field (RADIO) as both hot-spot and be active on double click. Then using the corresponding icons and the HOTSPOT_CLICK event it works like a radio button. For achieving our goal we have to use local class and methods in our report program.

Define and implement event handler class

Define a local class and declare two methods one for handling hotspot and other one for handling double click.

    CLASS lcl_event_handler DEFINITION FINAL.

          PUBLIC SECTION.

          METHODS: handle_double_click  FOR EVENT double_click OF cl_gui_alv_grid

IMPORTING e_row e_column,

                     handle_hotspot_click FOR EVENT hotspot_click OF cl_gui_alv_grid

IMPORTING e_row_id
                                                          e_column_id
                                                    es_row_no
                                                    sender.

     ENDCLASS.                   

Write implementation of that class with implementation of the method.

CLASS lcl_event_handler IMPLEMENTATION.

  METHOD: handle_double_click.
    CALL METHOD g_grid3->get_selected_rows
      IMPORTING
        et_index_rows = lt_selected_rows.
  ENDMETHOD.                   

  METHOD: handle_hotspot_click.
    FIELD-SYMBOLS:<ls_entry> TYPE ty_view,
                             <ld_fld>   TYPE ANY.
    LOOP AT gt_view ASSIGNING <ls_entry>.
      IF sy-tabix EQ es_row_no-row_id.
        ASSIGN COMPONENT e_column_id-fieldname OF STRUCTURE <ls_entry>
        TO <ld_fld>.
        IF ( <ld_fld> IS ASSIGNED ). * Set selected radio button "selected".
          <ld_fld> = icon_radiobutton.
        ENDIF.
      ELSE.

1. Module Pool:

            Open the screen where ALV grid with radio button needs to be displayed (For example screen number is 1000) and create a custom control in that. Suppose the name of the custom control is C_CUST_CONT3.

PBO

1. Now in PBO of module pool program. Our aim to display ALV grid with radio button in screen.

  Structure of field catalog and layout will be of type: lvc_t_fcat and lvc_s_layo. 

Initialy ALV will be displayed with one radio button as set.

So for setting a radio button we can just by default set 1^st row as set.

Gf_view-radio = icon_radiobutton.  “It will tell selected radio button.

And for other entries set them as unselected for that pass

gf_view-radio = icon_wd_radio_button_empty.

2. While building fieldcatalog for that radio field we have to pass below 2 fields :

  gf_fieldcat1-icon       = 'X'.

gf_fieldcat1-hotspot = 'X'.

3. While creating layout of the ALV table we need to pass stylefname with:

  gf_lay-stylefname = 'HANDLE_STYLE'. 

4. To handle events we have to create event handler.

CREATE OBJECT go_handler .
    SET HANDLER:

    go_handler->handle_double_click  FOR g_grid3,
    go_handler->handle_hotspot_click FOR g_grid3.

    CALL METHOD cl_gui_control=>set_focus
      EXPORTING
        control = g_grid3.

To display output:

*-To display output.
    CALL METHOD g_grid3->set_table_for_first_display
      EXPORTING
        is_layout                     = gf_lay
      CHANGING
        it_outtab                     = gt_view
        it_fieldcatalog               = gt_fieldcat1
      EXCEPTIONS
        invalid_parameter_combination = 1
        program_error                 = 2
        too_many_lines                = 3
        OTHERS                        = 4.

If it is not for first time then we need to check change data and refresh ALV data

          CALL METHOD g_grid3->check_changed_data.
          CALL METHOD g_grid3->refresh_table_display.

          CALL METHOD cl_gui_control=>set_focus
          EXPORTING
          control = g_grid3.

PAI :

The below code has to be written for ‘REFRESH’ OKCODE.

Refresh table display after switching the radiobuttons

  DATA: ls_stable TYPE lvc_s_stbl.
  ls_stable-row = abap_true.
  ls_stable-col = abap_true.

  CALL METHOD g_grid3->refresh_table_display
    EXPORTING
      is_stable = ls_stable
    EXCEPTIONS
      finished  = 1
      OTHERS    = 2.

  gx_fresh =

'X'.

In PAI of the screen read internal table where for field radio button icon is set like

READ TABLE gt_view INTO gf_view WITH KEY radio = icon_radiobutton.

After that call transaction FB03 and skip first screen.

The screen will look as below:

The screen navigates to the accounting document screen transaction FB03.

Conclusion: Thus the radio buttons could be included in ALV grid display using ICON and HOTSPOT_CLICK event.

Lets use FORM get_cache_data:

FORM loop_with_cache .

  DATA: t01 TYPE i ,
        t02 TYPE i ,
        dif TYPE i .

  DATA: it_sflight TYPE TABLE OF sflight .
  FIELD-SYMBOLS: <st_sflight> LIKE LINE OF it_sflight .

  DATA: st_scarr TYPE scarr .

  SELECT * FROM sflight INTO TABLE it_sflight .

  SORT it_sflight BY fldate .

  GET RUN TIME FIELD t01.

  LOOP AT it_sflight ASSIGNING <st_sflight> .

* For each row we go and ask for a record from the cache
    PERFORM get_cache_data
     USING
       <st_sflight>-carrid
    CHANGING
       st_scarr .

  ENDLOOP .

  GET RUN TIME FIELD t02 . dif = t02 - t01.

  WRITE: / 'loop_with_cache:' , dif .

ENDFORM .                    "loop_with_cache

Maximum positive value that can be stored by integer type variable in ABAP is 2147483647.

For values beyond maximum limit of integer variable, workarounds can be used.

One such example is discussion MOD operation fail for large numbers started by Starlet Abraham

I was able to calculate correct result of 512^17 MOD 2773 using the methods detailed below.

I have written this program to do following operations on large integers.

• Addition
• Subtraction
• Multiplication
• Division
• Mod
• Power

Full code snippet is posted at the end of this document.

Program has its flaws, but it works.

I would briefly go through how the logic works.

How are big numbers stored?

Local class lcl_bignum has instance attributes that store big numbers.

LV_STRING - Number stored as string type.

LT_INT - an internal table of integers. The string is broken into substrings of size 4 (base 10000), and those substrings ( as int4 ) are stored in internal table.

LV_SIGN - integer type to store the sign of number. +1 for positive, -1 for negative.

For example, number 1234567890 will be stored in internal table as

Why is number broken into base 10000?

Base 10000 is safe considering the capacity of integer variable type in ABAP.

Computing 9999 * 9999 results in 99980001, which is within the limits of integer type.

On the other hand, 99999 * 99999 results in 999980001, which would lead to overflow exception.

How to create instance and store big number?

Below code snippets can be used to create instance of big number.

The constructor parameters are options.

CREATE OBJECT lr3.

--

Above code will create instance with zero value in it.

CREATE OBJECT lr2
  EXPORTING
    i_value = '533335555511111'.

--

Above code will create instance and populate lv_string and lt_int by breaking down input string.

Sign of number is positive by default.

Input string should have only numbers in it.

CREATE OBJECT lr1
  EXPORTING
    i_value = '6584389034291301828999'
    i_negative = 'X'.

--

Using above code, 'X' can be passed i_negative flag if we have a negative number.

How to add numbers?

Instance method Add( ) can be used for adding numbers.

It accepts 2 object reference that need to be added, and result is stored in object whose method gets called.

We are adding the numbers starting lowest weightage (LT_INT[1]), and carrying forward extra in case of overflow.

For example, we add 12345678 and 22223333. Program would add (5678,3333) first, and then (1234,2222).

For A = B + C, below code can be used.

lr3->add( i_obj1 = lr1
          i_obj2 = lr2 ).

--

For A = A + B, below code can be used.

lr3->add( i_obj1 = lr3
          i_obj2 = lr2 ).

--

How to subtract numbers?

Instance method Subtract( ) can be used for subtracting numbers.

The usage is same as Add( ) method.

Looking at code, you would see that Add( ) and Subtract( ) are calling each other.

It is done the tackle how absolute values are treated depending on their sign.

For example, A = B + C, the values of B and C will be added, and common sign will be retained if B and C have same sign. Both positive, or both negative.

If the signs of B and C are different, we essentially have to keep sign of B, and calculate |B| - |C| (absolute values).

How to multiply numbers?

Instance method Multiply( ) can be used.

It accepts 2 object references, and stores result in calling object.

I would explain the logic using example. It is similar to the method used in elementary school.

For elementary example of multiplying 123 and 456, below logic is used.

123

456

===

3*6 + (3*5+2*6) + (3*4+2*5+1*6) + (2*4+1*5) + 1*4

Same thing is done in program at base 10000 level.

At every stage we are carrying forward the overflow value.

How to divide numbers?

For division, I am guessing the answer by multiplying.

Something like binary search, I start with 1 as answer, keep on multiplying it by 10000 still answer crosses dividend.

Once the guess surpasses dividend, I take a step back, and start multiplying by square root of 10000.

A point comes when multiplier is reduced to 1, and multiplication can no longer be used to get closer to answer.

I then use addition to get closer to answer. Instead of square root, divide by 2 to get next "jump value".

A dry run using elementary example would be something like this.

451

4

---

How to do calculate remainder (MOD operation)

Instance method Mod( ) can be used, which internally uses Divide( ), Multiply( ) and Subtract( ).

To calculate A = B MOD C, program does something like:

A = B - C * ( B DIV C )

Here we are reusing the code written in previous methods.

How to calculate Power?

Instance method Power( ) can be used, which internally uses Multiply( ) and Subtract( ).

For calculating A = B POWER C, program starts with 1 as answer, uses loop to multiply B to answer, C number of times.

Full code snippet

Handling Customer Fields in BAPIs which doesn't have Extension Structure

Scenario:

        You have identified a BAPI for a certain SAP process creation, the standard SAP Process has customer fields to be filled in too. But the BAPI doesn’t have an extension structure to update the Customer Fields involved in it. And your client mandates against the use of BDC.

Illustration:

     As an example the BAPI to create a Notification BAPI_ALM_NOTIF_CREATE (which doesn’t have an extension structure), equivalent to the transaction IW21, is considered.

     The QMEL structure has been enhanced with an Append Structure with custom fields in it.

IW21 is configured such that the added customer fields are linked to the VIQMEL structure (QMEL’s View).

     In this case there is no direct approach to fill in the customer field data into the BAPI BAPI_ALM_NOTIF_CREATE, as it doesn’t have the QMEL structure in the either the import or the table parameters.

     To address these scenarios SAP has been providing Customer Exits which could handle the Structures which hold the Customer fields to be update in the Standard Transaction.

     In our scenario, analyzing the flow of the BAPI BAPI_ALM_NOTIF_CREATE, lead to identify a customer exit QQMA0025 with the exit FM EXIT_SAPLIQS0_017 which handles the structure VIMEL in the importing and

exporting parameters as below

So in order to solve this scenario, follow the below steps,

·         -->Implement the customer exit which is identified to handle the customized structure (VIQMEL in our case)

·         -->In the source program where in the BAPI BAPI_ALM_NOTIF_CREATE is used to create a Notification,EXPORT the customer data in to Memory ID.

·         -->In the implemented customer exit, IMPORT the Customer Field data from the Memory ID.

·         -->Fill the imported data to the corresponding fields of the VIQMEL structure.

This approach will help us in preventing the issues which could arise in implementing a BDC call for such scenarios. BDC calls are prone to issue relating to the Changes in Screen Configuration and Enhancement Pack related changes.

Hi,

sometimes you must implement modification for multi sales deal terms in VB21 by screen 123 (Dialog Box for Overlapping Dates) off.

So You must modify 2 programs:

1. 1.  MV13AF0G

*----------------------------------------------------------------------*

*       FORM  GUELTIGKEIT_PRUEFEN_AGREEMENT                            *

*----------------------------------------------------------------------*

*       The validity periods for condition records in sales deals may  *

*       not overlap in any way with condition records with the same    *

*       condition type and variable key but on a different agreement.  *

*----------------------------------------------------------------------*

FORM gueltigkeit_pruefen_verkaufsak USING all

                                          sichern

                                 CHANGING value(gp_subrc).

"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""$"$\SE:(1) Form GUELTIGKEIT_PRUEFEN_VERKAUFSAK, Start A

*$*$-Start: (1)---------------------------------------------------------------------------------$*$*

ENHANCEMENT 1  Z_MV13AFOG.    "active version

DATA: BEGIN OF S_KNUMH OCCURS 0,

        KNUMH TYPE KNUMH,

        datab TYPE kodatab,

        datbi TYPE kodatbi,

        ANSWER,

      END OF S_KNUMH.

IF sy-ucomm = 'SICH'.

   IMPORT s_knumh TO s_knumh FROM MEMORY ID 'KNUMH'.

ENDIF.

RANGES s_ucomm FOR sy-ucomm.

s_ucomm-sign = 'I'.

s_ucomm-option = 'EQ'.

s_ucomm-low = 'SICH'.

APPEND s_ucomm.

s_ucomm-sign = 'I'.

s_ucomm-option = 'EQ'.

s_ucomm-low = 'ABRE'.

APPEND s_ucomm.

s_ucomm-sign = 'I'.

s_ucomm-option = 'EQ'.

s_ucomm-low = 'SIC1'.

APPEND s_ucomm.

s_ucomm-sign = 'I'.

s_ucomm-option = 'EQ'.

s_ucomm-low = 'OPT1'.

APPEND s_ucomm.

s_ucomm-sign = 'I'.

s_ucomm-option = 'EQ'.

s_ucomm-low = 'ENT1'.

APPEND s_ucomm.

s_ucomm-sign = 'I'.

s_ucomm-option = 'EQ'.

s_ucomm-low = 'OPT1'.

APPEND s_ucomm.

SORT s_ucomm BY low ASCENDING.

IF fcode = 'ENT1'.

   sy-ucomm = 'ENT1'.

ENDIF.

IF sy-ucomm IN s_ucomm AND sy-tcode = 'VB21'.

   DATA: lv_ksdat            LIKE t681-ksdat,

         lv_flag             TYPE flag,

         lv_no_popup         TYPE flag,

         lv_new_flag         TYPE flag,

         lv_old_flag         TYPE flag,

         lv_new_rec          TYPE flag,

         lv_zvflg_save_deal  TYPE zvflg_save_deal,

         lv_title(30),

         lv_answer,

         lv_question(400),

         lv_matnr            TYPE matnr,

         lv_knuma_ag         TYPE knuma_ag,

         lv_new_datab        TYPE kodatab,     " nowa data poczatkowa obowiazywania warunku

         lv_new_datbi        TYPE kodatbi,     " nowa data koncowa obowiazywania warunku

         lv_old_datab        TYPE kodatab,     " aktualna data poczatkowa obowiazywania warunku

         lv_old_datbi        TYPE kodatbi.     " aktualna data koncowa obowiazywania warunku

   DATA : BEGIN OF s_komg .

           INCLUDE STRUCTURE komg.

   DATA : END OF  s_komg .

   IMPORT lv_popup TO lv_no_popup FROM MEMORY ID sy-uname.

   PERFORM time_vake_akt_fill(sapmv130) USING no.

*if not TIME_VAKE_AKT[] is INITIAL.

*    READ TABLE time_vake_akt INDEX 1

**  TCTRL_FAST_ENTRY-CURRENT_LINE

*    .

*

*    IF sy-subrc = 0.

   LOOP AT  time_vake_akt.

         PERFORM vake_next(sapmv130) USING yes.

         IF NOT rv13a-datab = '00000000'.

           lv_new_datab = rv13a-datab.

         ELSE.

           lv_new_datab = rv130-datab.

         ENDIF.

         IF NOT rv13a-datbi = '00000000'.

           lv_new_datbi = rv13a-datbi.

         ELSE.

           lv_new_datbi = rv130-datbi.

         ENDIF.

     READ TABLE S_KNUMH WITH KEY KNUMH = time_vake_akt-knumh

                                 DATAB = lv_new_datab

                                 DATBI = lv_new_datBI.

     IF NOT SY-SUBRC = 0.

       CALL FUNCTION 'SD_CONDITION_KOMG_FILL'

         EXPORTING

           p_kotabnr = time_vake_akt-kotabnr

           p_kvewe   = time_vake_akt-kvewe

           p_vakey   = time_vake_akt-vakey

         IMPORTING

           p_komg    = s_komg.

       SELECT SINGLE zvflg_save_deal FROM zpon INTO lv_zvflg_save_deal

         WHERE vkorg = kona-vkorg

           AND vtweg = kona-vtweg

           AND spart = kona-spart

           AND kunnr = s_komg-kunnr.

       IF NOT sy-subrc = 0.

         SELECT SINGLE zvflg_save_deal FROM zpon INTO lv_zvflg_save_deal

          WHERE vkorg = kona-vkorg

            AND vtweg = kona-vtweg

            AND spart = kona-spart.

         IF NOT sy-subrc = 0.

           EXIT.

         ENDIF.

       ENDIF.

       IF lv_zvflg_save_deal = 'X'.

         lv_old_datab = time_vake_akt-datab.

         lv_old_datbi = time_vake_akt-datbi.

         lv_matnr = s_komg-matnr.

         SELECT SINGLE knuma_ag FROM konp INTO lv_knuma_ag

           WHERE knumh = time_vake_akt-knumh.

*    ENDIF.

*if not lv_new_rec = 'X'.

         IF ( ( lv_new_datab = '00000000' ) AND ( lv_new_datbi = '00000000' ) ).

           lv_new_flag = ''.

         ENDIF.

         IF ( ( lv_old_datab = '00000000' ) AND ( lv_old_datbi = '00000000' ) ).

           lv_old_flag = ''.

         ENDIF.

         IF ( lv_new_datbi = lv_old_datbi ) AND ( lv_old_datab BETWEEN lv_new_datab AND lv_new_datbi ).

           lv_old_flag = 'X'.

         ENDIF.

         IF ( lv_new_datbi = lv_old_datab ) AND ( lv_new_datab < lv_old_datab ).

           lv_old_flag = 'X'.

         ENDIF.

         IF ( lv_new_datab = lv_old_datab ) AND ( lv_new_datbi BETWEEN lv_old_datab AND lv_old_datbi ).

           lv_new_flag = 'X'.

         ENDIF.

         IF ( lv_new_datbi > lv_old_datbi ) AND ( lv_new_datab BETWEEN lv_old_datab AND lv_old_datbi ).

           lv_new_flag = 'X'.

         ENDIF.

         IF ( lv_new_datab < lv_old_datab ) AND ( lv_new_datbi BETWEEN lv_old_datab AND lv_old_datbi ).

           lv_new_flag = 'X'.

         ENDIF.

         IF ( lv_new_datbi = lv_old_datbi ) AND ( lv_new_datab BETWEEN lv_old_datab AND lv_old_datbi ).

           lv_new_flag = 'X'.

         ENDIF.

         IF ( lv_new_datab = lv_old_datab ) AND ( lv_old_datbi BETWEEN lv_new_datab AND lv_new_datbi ).

           lv_new_flag = ''.

         ENDIF.

         IF ( lv_new_datbi = lv_old_datbi ) AND ( lv_new_datab BETWEEN lv_old_datab AND lv_old_datbi ).

           lv_old_flag = 'X'.

         ENDIF.

         IF ( lv_new_datab = lv_old_datbi ) AND ( lv_new_datbi > lv_old_datbi ).

           lv_new_flag = 'X'.

         ENDIF.

*    IF ( ( lv_new_datab BETWEEN lv_old_datab AND lv_old_datbi ) AND ( lv_new_datbi BETWEEN lv_old_datab AND lv_old_datbi ) ).

IF ( ( lv_new_datab > lv_old_datab AND lv_new_datab < lv_old_datbi ) AND ( lv_new_datbi < lv_old_datbi  AND lv_new_datbi > lv_old_datab ) ).

           lv_old_flag = ''.

           lv_new_flag = ''.

         ENDIF.

* IF ( ( lv_old_datab BETWEEN lv_new_datab AND lv_new_datbi ) AND ( lv_old_datbi BETWEEN lv_new_datab AND lv_new_datbi ) ).

if ( lv_old_datab > lv_new_datab ) and ( LV_OLD_DATBI < LV_new_DATBI ).

*           lv_old_flag = ''.

           lv_old_flag = 'X'.

*           lv_new_flag = ''.

         ENDIF.

         IF lv_new_flag = 'X' OR lv_old_flag = 'X'.

*      IF ( NOT lv_new_datab = lv_old_datab ) and ( NOT lv_new_datbi = lv_old_datbi ).

* if ( ( not lv_new_datab BETWEEN lv_old_datab and lv_old_datbi ) and ( not lv_new_datbi BETWEEN lv_old_datab and lv_old_datbi ) ).

           lv_flag = 'X'.

CONCATENATE 'The validity period of new condition overlaps with different conditions. These conditions will be edited when you save! Material:' lv_matnr

           ', Old Sales Deal:' lv_knuma_ag

           ', New beginnig date: ' lv_new_datab ', New end date: '

           lv_new_datbi '. Old beginning date: '

           lv_old_datab ', Old end date: ' lv_old_datbi '. Are You Sure?' INTO lv_question.