E-Commerce and ERP.

E-Commerce has become the buzz word of entire business community in the recent times. There are lot of scope for acquiring new customers with Low cost using the E-Commerce plat form. The challenge comes when the business tries to integrate the E-commerce sites with the existing business. Especially for the business houses where ERP is already in place.

Lot of people are working towards the seamless integration of e-commerce platform to their ERP system. Before a year or two, the E-Commerce segment was traditionally dominated by the E-Commerce companies. Now the trend is changing. Though, by Volume, still the E-Commerce companies dominate the segment globally, there are lot of traditional production businesses looking at the implementation of E-Commerce sites to directly sell the products to their end users.

E-Commerce sites will be traditionally focused on Business to Customers segment. But for a traditional production based Business houses they can use the E-Commerce to target any of the below user groups below.

1)      Business to Business – To their corporate customers.

2)      Business to Business – To their Dealers.

3)      Business to Customer – To their End user.

Advantages of E-Commerce in Production houses.

                The main advantage of ERP in Production houses is the cost involved in the acquisition of new customer. When they directly connect with any of the customers above, there is a high chance that they can avoid middle layers which will have its own cost for handling and commission etc. Though there are lot of other media available to show case their products online, E-Commerce is the best way to showcase their product and arrive at a deal online.

Advantages of integrating it with ERP

                When you integrate the E-Commerce with the ERP in the production houses. All the Orders from the E-Commerce will be placed directly in your ERP. And there is no manual activities involved. This approach will reduce the time involved. And if you are in male to order model, you directly send the notification to the production floor which will save precious time. And you can ship the product As early as Possible.

We will continue to discuss about this in the further articles.

Basics of ABAP : Creating T-Code for a Table maintenance generator

Create a transaction code to run the table maintenance generator.
Go to Tcode SE93
Transaction code: ZTAB
Short text: Test Table Maintenance Events
Start Object: Transaction with parameters (Parameter Transaction) 

Transaction: SM30
Skip first Screen: Check ON
Default Values:
View Name      ZTAB
Update           X

Execute the transaction code:

Execute the transaction code ZTAB and click on New Entries button. 

Now press the new entries button, You can able to enter the new entries into the table.

Basics of ABAP- Adding Custom Events in Table maintenance generator

While creating the tables, sometimes we may need to update the table fields in the background. For example, if we create a table with 10 fields and in those 10 fields there are 2 fields which are User name and the Date, these 2 fields should update automatically when a record Inserted/Updated in the table. It also can be used when we want provide various validations on creating, changing or saving entries in a table.

Event Handling

When we provide event handling on table maintenance, table fields will be updated automatically when a new record inserted into the table or an existed record changes through the table maintenance generator.

To achieve the event handling in table maintenance, we need to create a table maintenance generator and then create events. Process is as follows:

Create a table maintenance generator for the table:

To create table maintenance generator go Utilities -> Table Maintenance Generator and provide following information:

Authorization Group: &NC&

Function group: Any suitable FC 

Maintenance type: Two Step

Maint. screen no: Overview screen 8005

                             Single screen    8006

Click on Create. 

Create Events for table Maintenance:

To create events on table maintenance go to Environment -> Modification -> Events -> New Entries 

List of events available:

Choose maintenance event 05-Creating New Entry and provide a name of the event (This will become perform/subroutine).

Click on Editor Button to provide event handling code. 

A popup will be appear, It will ask to create an include program, in which we'll write the event handling code.
Click on continue.

 

Write the code in include for the event in the include created

Basics of ABAP : Table Maintenance Generator and Its Events

Table maintenance generator is a user interface tool which is used to change the entry of the table or delete an entry from the table or create an entry for the table. Without Table maintenance generator, we cant' change the table entries directly in the system. we can change the data in a table only through the program.

While creating the database table, we need to maintain the flag in the  'Delivery and Maintenance' tab, the 'Table View Maint.' should have the "Maintenance allowed" property defined.

 

Creating TMG (Table maintenance generator):

Go to SE11 and create a table with the fields as per the requirement.

In table change mode, click on Utilities and then click on Table maintenance generator.

Implementation of table maintenance generator for a custom table:

 
Go to SE11 and create a table with the fields as per the requirement.
In table change mode, click on Utilities and then click on Table maintenance generator. 

Following screen will be displayed for setting up the Maintenance generator

Following are the available options available for the users

Authorization Group: this option is to provide authority to certain users to maintain the data, if it is not needed fill it as NC.
 

Function group  this is the function group under which the maintenance function module will be generated.

    
Maintenance screens:  Maintenance can be done in 2 ways
 1. Maintenance and Overview both on one screen
 2. Maintenance on one screen and Overview on another screen.

Maint. Screen number : A screen number should be given, if it is a single screen, only one screen is enough. If there are 2 screens you need to provide 2 screen numbers.

Please note that when this table maintenance generated, It will generate screens under the function group hence the screen number should not be utilised already in the function group.

Dialogue data Transport details.

There are 2 options one is standard recording routine and the user recording routine,

If you select the standard record routine then you will get a option of storing the data under the transport request and move it across the system.  

After saving the changes, go to SM30 for maintaining the table.