Tag Archives: SAP

Earlier this week I finally completed the full version of the ‘Beginners Guide To ABAP‘. I decided to give the course its own website so not to get muddled up with the mixed bad of SAP content here.

Lots of people jumped on-board when I released it which I am super happy about. The course ended up taking me around 1 year to complete. This is way longer than I thought it would. Partly due  to work commitments, well actually a lot due to work commitments, but also down to underestimating just how much work is involved in producing a quality training product.

Whilst making the videos and editing afterwards there was lots of content that was given the axe for all sorts of reason.

1. Poor video.
2. Poor Sound.
3. What I recorded didn’t make sense!!
4. I could go on and on.

Goal #1 Achieved

When I finally finished editing the last video I thought… finally the job is done. That feeling didn’t last long. Then came to realisation that I had another job – building a website to house the course.

After a bit of domain name searching I came upon abapcourse.com. Then got my WordPress coding hat on and went to work. The website took me about 2 weeks to complete. It may sound a long time but I had to figure out the payment processing, membership system etc…

Anyway, it’s done. Now I can relax a little and I hope the students who are taking the course really apply themselves and learn ABAP well. The course has taken a lot of work on my part and I have put my heart and soul into making it the most affordable and high quality course on SAP ABAP on the interwebs.

I would love to know your thoughts and if you have any questions just let me know. Heck, hit me up on Skype if you want … pete_m1 (no spam please).

In this seventh video of module 2 we finally get to see the data we have entered into out table and take a look at some of the useful SAP data dictionary tools we have available.

In a previous article we have seen how to create a simple SAP Web Dynpro ABAP application with only one view. Now, in this article we modify that application by adding one more view and learn how to navigate between two views using inbound and outbound plugs.

Step 1. Adding Views

1.1 Go to Transaction SE80, choose Web-Dynpro-Comp. / Intf. in the object list and enter the name of your Web Dynpro application (Y_FIRST_WEBDYNPRO) and click on Display.

Concept Of A Fiscal Year

Every business has to follow a certain accounting cycle in order to record the business transactions. Some businesses follow a January to December cycle while other businesses may follow an April to March cycle. The choice of the accounting year or the fiscal year depends on the business requirements. The fiscal year is usually a 12 month period over which all the business transactions are recorded. At the end of this period financial statements are prepared to review the performance of the business. These business requirements for the accounting year can be mapped into SAP by using a two alphabet identifier called the fiscal year variant.

A posting period is a period contained in the fiscal year over which transactions are recorded and clubbed together. Every transaction that is recorded in SAP has to be assigned to a posting period. Normally, every month is considered as a posting period which results in a total of 12 posting periods in a financial year. The special periods are meant for the year-end closing transactions. It provides flexibility to the accounting department to make adjustment entries while executing the year-end closing process.

The fiscal year variant can be used to define the following:

• Number of normal posting periods available in a financial year.
• Number of special posting periods available in a financial year.
• The duration of the accounting cycle i.e. a complete fiscal year or a shortened fiscal year.
• Whether the fiscal year is the same as the calendar year.
• Procedure to determine the current period while posting.

The fiscal year variant is defined at the client level and is therefore available to all the company codes in the client. If there is more than one company code which uses the same fiscal year configuration, then the configuration need not be defined again and again for each of the company codes. The settings can be defined one as once as a fiscal year variant and can then be assigned to multiple company codes. This saves time during new implementations and also reduces the errors that may happen due to repeated manual entry. The fiscal year variant is first defined and then it is assigned to the company codes for which it is to be used.

The fiscal year variant is one of the first configurations that is needed to be done while setting up the organizational structure in SAP. No transactions can be recorded without defining the fiscal year variant and assigning it to the company code. The fiscal year variant is used to define the normal and the special posting periods that are available for posting business transactions in a company code and the posting period variant is used to control which of these periods is open for posting.

Navigate to the implementation guide menu as shown in the screenshot below or execute the transaction code OB29 from the SAP Easy access menu display the fiscal year variant configuration screen.

Now our table has been created we can enter records directly into it using some of the SAP ABAP Workbench tools for data entry. This video shows how to navigate to the data entry options and a few tips on screen set-up. For Reference You can get the the data entry screen through your ABAP […]

Summary:

Custom time functions are required when the standard functions and PCRs (Personal Calculation Rule) are not able to fulfill the complex business requirements. This tutorial explains the step-by-step process to create a custom time function to fulfill those complex business requirements. But, before we start the step-by step process we will see what are Schema and Time Functions?

Schema and Time Functions: When Time evaluation report is executed, employee’s working and absence times are evaluated, the individual processing steps in this valuation are executed in a specific order. This specific sequence is known as Schema, and the individual processing steps are known as Functions.

Schema in time management determines the sequence in which the functions (individual processing step) are executed in time evaluation. With the help of functions data is either provided back to the internal tables in time evaluation or sets a switch which is then used to determine whether or not to process any activity.

Step-by-step process to create custom Time (PT) function

Step 1. Go to transaction code PE04. In the ‘Name’ field, give a name to your custom time function, then select ‘Time management’ radio button from the Object class tab, and then select ‘Function radio button from the Object Type tab. Finally, click on the create button.

You will see a pop-up message, stating that the function can only be created in SAP package. Accept by clicking on “Continue”    button.

Step 2. Now, enter a description for your function and select the radio button ‘Standard name’ from the ‘Name of form routine’ tab. You can also define a custom name by selecting the ‘Self-defined’ radio button.

Select ‘Other Counties’ checkbox from the Country assignment tab.

Concept Of A Customer Master

All the data pertaining to a particular customer is stored in the customer master in SAP. This data is made available to other transactions and modules as and when required. The customer master contains the following data sets:

• GENERAL DATA:The general data consists of the customer address, country, contact person, etc.
• COMPANY CODE DATA: The company code data contains the data specific to a company code like the payment terms, payment methods, dunning procedures, etc.
• SALES DATA: The sales area data contains information like the sales organization, division, pricing, billing details, shipping details, etc.

The customer master is extremely important for the Sales and Distribution as well as the Financial Accounting module. The details of the customer such as the payment terms, address, sales area, division, paying bank, payment methods, etc. are picked up from the customer master and provided to the other modules as and when necessary.

The total data for a customer master is stored in multiple tables. The General data pertaining to a customer is stored in the KNA1 table while the company code data is stored in the KNB1 table. The sales data for a customer is stored in the KNVV table. All these tables are accessed for information about the customer by the FI and the S&D module.

Concept Of A Customer Account Group

A customer account group is used to group together customers by some criteria. For e.g. a business may have different account groups for international and domestic customers.

The customer account groups define the following features for every customer assigned to them: