ABAP, NetWeaver, ERP Tutorial » ABAP

SAP FI – Deductible and Non-deductible Tax

Andy — Mon, 06 Feb 2012 07:39:29 +0000

Non-deductible taxes are taxes that are not allowable when calculating a taxable income. They are taxes that have been paid in the process of generating income or purchasing items, but they are not subtracted from the final taxable income. For example,

VAT 14% non-deductible 50%

100 EUR invoice (account 5080)
7 EUR VAT goes to the VAT account
7 EUR VAT goes back to the Expense account (5080)
Total invoice 107.00
Total VAT 7.00

How to configuration this scenario in SAP?

In Tax code A2, Enter 7% in condition type MWAS and 7% in condition type MWVZ.

SAP FI – Coding Block

Andy — Thu, 02 Feb 2012 09:18:02 +0000

In the coding block of the system you can create your own fields. The new coding fields can then be used in FI General Ledger accounts, MM Inventory Management and MM Purchasing, and are also updated in the line items created in the Controlling applications.

If you have created customer fields, they are updated by the system during automatic postings. To enable you to post these fields in the Enjoy transactions manually, you must assign the fields to the entry variants in the Enjoy posting transactions. To do this, choose Include Customer Fields in Enjoy Transactions.

Requirements

You require a test system in order to include coding fields.

The changes are recorded in the test system in a transport request and can thus be transported into other systems. To include coding fields, you require the following authorizations:

New field inclusion in coding block X_COBLMOD

Maintenance of cross-client tables S_TABU_CLI

Dictionary authorization S_DEVELOP

Transport authorization S_TRANSPRT

How to hide SAP standard button in standard transaction

Andy — Thu, 02 Feb 2012 06:30:52 +0000

Business user might need to hide some buttons in SAP standard transaction code because they don’t want there functions to be abused. We assume there function couldn’t be controlled by authorization objects. SAP provides transaction variant to change SAP standard UI.

Transaction variants can simplify transaction runs as they allow you to:

Preassign values to fields

Hide and change the 'ready for input' status of fields

Hide and change table control column attributes

Hide menu functions

Hide entire screens

In particular, hiding fields in connection with screen compression, and hiding screens, can result in greater clarity and simplicity.

Transaction variants are made up of a sequence of screen variants. The field values and field attributes for the individual screens found in transaction variants are stored in screen variants. Each of these variants is assigned to a specific transaction, can, however, also contain values for screens in other transactions if this is required by transaction flow. The transaction that the variant is assigned to serves as initial transaction when the variant is called.

For example, if we need to hide button ‘Reject document’ in tcode VA02. Below are the detail steps.

SAP ABAP – Transfer number to chinese character function module

jackingyu — Mon, 09 Jan 2012 15:12:04 +0000

abap function module,number to chinese character

ABAP Programming – ABAP General

Andy — Wed, 04 Jan 2012 06:31:47 +0000

The following diagram shows the components of SAP ABAP. Generally speaking, it contains the ABAP language, development environment, runtime environment, technologies that based on ABAP and other tools & services. All these components forms the ABAP (Advanced Business Application Programming).

In order to be a senior ABAP consultant, you should have a good command of all these components. I wants to share my personal experience on all these topics.

ABAP Objects – Event and Observer Pattern

Andy — Tue, 03 Jan 2012 07:52:54 +0000

In ABAP Objects programming, event handling – event trigger and event handler means that certain methods act as triggers and trigger events, to which other methods - the handlers - react. This means that the handler methods are executed when the event occurs. This works exactly like the delegates and events in C#.

Both ABAP and C# programming language supports the event programming from language level. This feature can be used to implement observer pattern easily. The observer pattern (a subset of the publish/subscribe pattern) is a software design pattern in which an object, called the subject, maintains a list of its dependents, called observers, and notifies them automatically of any state changes, usually by calling one of their methods. Below diagram illustrate the class diagram of observer pattern.

SAP ALV – ALV Samples in SAP (cl_salv_table and cl_gui_alv_grid)

jackingyu — Thu, 22 Dec 2011 06:09:45 +0000

slis,cl_salv_table,drag and drop effects alv,init data of ALV_T_T2

SAP ALV- Control negative sign display for currency fields

jackingyu — Mon, 05 Dec 2011 06:11:54 +0000

ALV,set_edit_mask

Changes and Transports for Client-Specific Objects

Andy — Mon, 21 Nov 2011 09:28:11 +0000

In a typical SAP system landscape, you will have about 4-5 SAP clients for different purpose, such as sandbox client, development client, QA client, production client and training client. Each client has to have different client-specific settings on the client-specific objects changes and transports.

Go to tcode SCC4, you will find a list of clients on this system. Double click one client entry and you will enter below screen. You can maintain the client specific settings here.

SAP BAPI – BAPI_MATERIAL_SAVEDATA

Andy — Mon, 21 Nov 2011 08:35:43 +0000

SAP BAPI – BAPI_MATERIAL_SAVEDATA is the standard API to create/update the material master data. When creating material master data, you must transfer the material number, the material type, and the industry sector to the method. You must also enter a material description and its language. When changing material master data, you need enter only the material number. For detailed information on how to use this API, please refer to the function module documentation.