Release Notes ______________________________________________________________

19.6 Excise Duty 19.6.1 Excise Duty Basic Data 19.6.1.1 Basic Settings Excise Duty Basic Data The basic settings for excise duty are made in these Customizing t ables in the client in which you are logged on, for exammple, the definition of the tax types u sed or reconciliation methods for master data in excise duty. Use Maintenance of the basic settings that are required for mapping ex cise duty.

19.6.1.2 Maintain Tax Types Definitions of the tax types for the excise duties. Here the new t ax types are defined and the material data that need to be maintained are determined The allowed tax types and their basic properties are defined here.

Recommendation To make the master data maintenance as easy and convenient as poss

ible, you should deactivate all data fields and levels you do not need any more.

______________________________________________________________ SAP AG 1

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.1.3 Additional Charges Use By means of the additional charge an additional amount can be calc ulated for an excise duty-relevant document. This amount is stored with the document an d the identification of the additional charge in the tax document. The additional charge in SA P Beverage is suited for all tax types that can be mapped as 'back-pack' taxes of an excise tax (e.g. packing tax).

19.6.1.4 Maintain Procurement Types Schema Use The allowed purchase types are defined and summarized in the purch ase type scheme. The

allowed material procurement indicators are assigned with the defi nition of the tax types. A scheme can be assigned to several tax types.

19.6.1.5 Assign Procurement Types to Schema Use Here the allowed purchase types are assigned to the purchase type schemes. Only the purchase types which are assigned to the purchase type scheme pertaining to the tax type here, can be entered at the company code level of the ExD material master.

______________________________________________________________ SAP AG 2

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.1.6 Maintain Tax Type Independent Material Groups Use Here the material groups for excise duty material subject to tax t

ype cross-assignment can be defined. The materials from different tax types can easily be summ arized for customer-specific evaluations because the information is stored with the ExD documen t. Requirements Assigning a material group to a material is not possible unless th e maintenance has been activated in the definition of the tax type.

Note The tax type independent material groups are only relevant for the excise duties, they do not affect any other area in R/3.

19.6.1.7 Maintain Tax Type Dependent Material Groups Use Here the material groups for excise duty material which have to be assigned dependent on the tax type, can be defined. The materials from different tax types c an easily be summarized for customer-specific evaluations because the information is stored wi th the ExD document. Requirements Assigning a material group to a material is not possible unless th e maintenance has been activated in the definition of the tax type.

Note The tax type independent material groups are only relevant for the excise duties, they do not affect any other area in R/3.

______________________________________________________________ SAP AG 3

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.2 Tax Warehouse 19.6.2.1 Define Tax Warehouse Tax warehouse This area includes all Customizing tables that affect tax warehous es. Use Creation and maintenance of the tax warehouse for excise duty.

19.6.2.2 Addresses for Tax Warehouse Use Address types with a postal address are created for an existing ta x warehouse.

Example The addresses are used mainly to print on the BVD/LDS form.

19.6.2.3 Settlement Unit

Maintenance of the settlement units dependent on the tax type and the tax warehouse Since the settlement units differ between the tax types and the of ficial authorities in charge require different levels of accuracy for the values that need to b e reported, flexible configuration is a necessity.

______________________________________________________________ SAP AG 4

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.2.4 Warehouse Assignment Use Assignment of R/3 storage locations to tax warehouses The storage locations may belong to different plants and company c odes. A storage location is only allowed to be assigned to one tax warehouse (to be more preci se: to one tax warehouse for each tax type).

19.6.2.5 List Header Use It is possible to indicate individual header lines for the list he ader of each tax warehouse. These header lines are output at the beginning of each new page left-ali gn in front of the header. For technical reasons the list header cannot be output on all ALV/ SLV lists (ALV=AbapListViewer).

______________________________________________________________ SAP AG 5

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.2.6 Shrinkage Settings 19.6.2.6.1 Define Storage Types

Shrinkage Settings Shrinkage is the loss of merchandise in the storage location durin g production or storage. Mapping shrinkage is relevant for German spirits tax, for example. Use The storage type is an identifier for a warehouse shrinkage rate t hat can be defined per tax type and storage location. When defining shrinkage rates for the s torage location, you can choose to enter the shrinkage rate directly or using the storage t ypes.

19.6.2.6.2 Shrinkage Storage Type Use Here, the annual shrinkage rate for warehouse shrinkage in % is de fined per storage type and tax warehouse.

19.6.2.6.3 Shrinkage Storage Location Use Here the annual shrinkage rate for warehouse shrinkage in % is def ined per storage location.

______________________________________________________________ SAP AG 6

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.2.6.4 Theoretical Shrinkage Use Definition of the theoretical shrinkage.

19.6.2.6.5 Actual Shrinkage Use Definition of the actual shrinkage.

19.6.3 Special Partner Types 19.6.3.1 Definition of Special Partner Types in Excise Duties Use By means of the special partner types the ship-to parties and the vendors can be grouped from the excise duty's point of view.

______________________________________________________________ SAP AG 7

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

Example Deliveries to foreign embassies shall be shown separately and be m ade subject to tax suspension.

19.6.3.2 Maintenance of Special Partner Types Allowed for Vendors Use Here it is defined which special partner types for which tax type can be assigned to the vendors. Assigning the special partner type to the respective vendor is mad e later by means of the master data maintenance .

19.6.3.3 Maintenance of Special Partner Types Allowed for Ship-To Part

ies Use Here it is defined which special partnertypes for which tax type can be assigned to the ship-to parties. Assigning the special partner type to the respective ship-to party is made later by means of the master data maintenance or by an assignment by means of the custo mer group (dependent on the basic settings in excise duties).

19.6.3.4 Assignment of Customer Group Ship-To Party to Special Partner

______________________________________________________________ SAP AG 8

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

Types Use Here the special partner types are assigned to the customer groups . Requirements

This setting is not permissible unless the special partner assignm ent for ship-tp parties has been set by means of the customer groups in the basic settings.

19.6.4 Stock Ledger Settings 19.6.4.1 Maintain Print Formats Use Settings for the fixed display, that is non-ALV lists: The print formats control the output of stock ledger lines in the single document overview.

19.6.4.2 Maintain Print Format Items Use Settings for fixed display, that is non-ALV list: In the print format items it is specified which fields are printed at which position in a print format. As soon as they are saved, all changes made to the print f ormats take immediate effect for all new stock ledgers. If you make changes to the print format items, it can therefore be helpful to test the effect of the changes on the stock ledger in a second session.

______________________________________________________________ SAP AG 9

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.4.3 ALV: Maintain Additional Fields Use Settings for flexible display (ALV list): Definition of additional fields to be shown in the flexible displa y (ALV) of the stock ledger. The additional fields will only be filled by the specified functio n module if a relevant fill condition has been created. Requirements - The structures and fields to be displayed must be created in th e Dictionary (transaction se11). - The function modules for filling the structure or the field are created as active in the ABAP Workbench using a relevant interface (transaction se37).

19.6.4.4 ALV: Conditions for Filling Additional Fields Use Settings for flexible display (ALV list): Specification of the conditions for when an additional field in th e stock ledger is filled using the specified function module.

______________________________________________________________ SAP AG 10

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.5 Movement Control 19.6.5.1 Movement Categories Movement Controlling In Excise Duty, a differentiation is made between SAP movement typ es, ED movement types and ED stock ledger groups. The SAP movement types are grouped together in ED movement categor ies. This ensures that customer-specific movement types can also be processed without cha nging the program. An ED movement category indicates the type of movement. The ED mov ement category decides on the method with which a document is analyzed to find out its im portance as regards taxation. Thus, for example, in the case of deliveries to a custom er, the ship-to-party is analyzed and in the case of stock tranfers, the corresponding plan t and storage location are analyzed. After the document has been analyzed, a document (provided it is r elevant to tax) is entered in the stock ledger. Here, the movements for a division (or possibly also a subdivision) are broken

down further into stock ledger groups (for example, Division 2: Sa le to customer, consumption or stock transfer subject to tax). Use Using this dialog you can define new movement categories for the e xcise duty. The ED movement categories group together SAP movement types, are delivered preset and generally do not need to be modified. Customer-specific movement types are only allowed in the range 900 - 999. They are used to assign SAP movements directly to a certain movement type for a sto ck ledger division, subdivision and group. You therefore need to enter the stock ledge r group for all movements in the range 900 - 999. Requirements Customer-specific movement categories are only intended for issue and receipt movement types. Stock transfer movement types can currently only be processed usin g the movement type provided for stock transfers. This 'Receipt' indicator can only be set for customer-specific mov ement categories (900 - 999). If this indicator is not set, a movement of this category will be interpreted as an issue.

______________________________________________________________ SAP AG 11

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.5.2 Movement Category for Tax Type Use Using this function, ED movement categories are authorized for use in the tax types. For movement categories in the range 300 # 399 and 900 # 999, you must specify a stock ledger group. All movements that are assigned to the ED movement c ategory by their movement type are assigned to this stock ledger group. These assig nments are delivered preset and generally do not need to be changed. If a movement category is entered without a tax type, the movement category can be used in all tax types. In the same way, the fixed assignment of the stock ledger group (f or movement categories in the ranges 300 # 399 and 900 # 999) can be overwritten with a new stock ledger group by specifying a tax type.

19.6.5.3 Movement Category for Movement Type Use Every combination of SAP movement type and SAP movement indicator defined in R/3 must be assigned an ED movement category. The ED movement category is assigned for all tax types and tax war ehouses. It is also possible to set this on an individual basis using additional entries specif ying the tax type and/or tax warehouse. If you want to subdivide by cost center, the relevant indicator ne eds to be set here.

______________________________________________________________ SAP AG 12

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.5.4 Movement Category for Cost Center Use Some SAP movement types are posted to cost centers. For these move ment types, a separate movement category can be assigned to each cost center. If no cost center is entered, the movement type stored for the movement category applies.

19.6.5.5 Stock Ledger Groups 19.6.5.5.1 Create New Stock Ledger Groups Stock Ledger Groups Movements that are the same from a tax point of view are grouped t ogether in stock ledger groups. Using stock ledger groups, individual tax operations can b e blocked or released depending on the tax type and tax warehouse (for example, the purc

hase of taxed goods from another country within the EU). Stock ledger groups are also used to control the representation of movements in the stock ledger. Since a very detailed breakdown of the tax operations is n ot generally required, stock ledger groups can be combined. Use If the stock ledger groups supplied are not sufficient, you can cr eate new stock ledger groups here, which are then assigned to tax types and tax warehouses usin g the Maintain Stock Ledger Groups Attributes function. Possible reasons for creating new stock ledger groups: - The existing stock ledger groups need to be combined under a di fferent heading - The movements need to be divided into more groups than are prov ided in the standard delivery. (Movements can be divided up using both the ED moveme nt types and by replacing stock ledger groups.)

______________________________________________________________ SAP AG 13

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.5.5.2 Maintain Characteristics of Stock Ledger Groups Use The properties of the stock ledger groups defined in this table de termine for each tax warehouse: - The movements that are locked for materials with certain materi al procurement IDs. - The movements that are entered in the official stock ledger, th e extended stock ledger, or that are not entered in any stock ledger. - The stock ledger departments (sub departments), in which the mo vements of customer-specific stock ledger groups are entered. - The print format used in the stock ledger for printing single d ocuments. - The relevance of the movements for retrograde shrinkage settlem ent. - Whether stock ledger groups should be combined.

19.6.5.5.3 Replace Stock Ledger Groups Use Using this function you can change the stock ledger groups and the ir assignments to the stock ledger division that are determined by document selection. This ca n, for example, be necessary

______________________________________________________________ SAP AG 14

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

if the main customs office responsible for a tax warehouse wants t he movements to be assigned differently. (Unfortunately there is no standard practice at prese nt.) The entry in this table ensures that the deviation from the functi on (described in this documentation) is documented and can be viewed at any time. As certain operations in SAP R/3 are linked to predefined movement types (for example, retrograde withdrawals for production, issues and receipts for sto ck transfer orders), movements that are classified differently from a tax point of view in R/3 ma y have to be mapped using identical operations. Document selection cannot differentiate betw een these operations. It can therefore become necessary to make a customer-specific change to t he stock ledger group assignment. With the setting described here, it is possible to divide up the s tock ledger group determined by document selection according to defined criteria. To do this, the stock ledger entry that needs changing is first entered in the conversion table. Blank fields ar e not checked during selection. The replacement of stock ledger groups is only carried out by the document selection once for each time and document. It is therefore not possible to replace a replaced entry at the same point in time. The entries in this table do not have any effect on movements that have already been assigned to a stock ledger group by the document selection and saved.

19.6.5.5.4 Maintain Block Schema for Stock Ledger Groups Use Using a block schema, certain tax movements (= stock ledger groups ) for materials can be blocked according to their ED procurement type. This means, for ex ample, that you can set document selection to refuse receipts in the tax warehouse from pu rchasing if the material is flagged as an own brand product in excise duty. Another option is to prevent the receipt of externally produced goods that have already been taxed. The block schemas are stored with the stock ledger groups. The block schemas are tax type independent. In a block schema, the procurement types are stored with reference to the procurement type schema. The procurem ent type schema is then assigned to tax types. When checking whether a movement in the stock ledger group is bloc ked, the block schema belonging to the tax type is determined first of all. A check is t hen run to see whether an entry with the ED procurement type of the material exists for this schema in the block schema. A separate block schema needs to be created for every combination of procurement types to be blocked.

______________________________________________________________ SAP AG 15

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.5.5.5 Assign Procurement Types to Block Schema Use In this table, the procurement types that are blocked by the block schema are defined. The procurement types are always stored with reference to the accompan ying procurement type schema.

19.6.5.6 Permissible Subsequent Postings Use After consultation with custom offices, it is possible to post cer tain movements, such as German beer tax, after the close of a taxation period. If subsequent postings are carried out in a closed taxation period for which the stock ledger division/subdivision is not entered here, the material document wi ll be flagged as incorrect.

19.6.6 Country-Specific Adjustments 19.6.6.1 Maintenance of EU-Affiliated Non-EU Countries

______________________________________________________________ SAP AG 16

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

Use Here settings are made for countries outside the EU, which from th e point of view of excise tax are assigned to an EU country and therefore are to be regarded as EU inland traffic countries. Examples are: Locations in Kleinwalsertal to Germany, the Isle of Man to Great Britain, San Marino to Italy, Andorra to Spain.

19.6.7 Print control Use The standard values for printouts of excise duties are entered in print control. It is possible to arrange a separate print control for each user for each list evalu ation per tax warehouse. If you do not want to enter a value for a field at a certain level, you c an enter '*' in the field. The entry '*' means that this field is maintained at the superordinate level. You cannot enter '*' in the fields Number of Copies, Spool Retention Period, Number of Ro ws, List Width (as they are numeric fields). If an immediate printout is required for a list evaluation, it is recommended that you enter '*' in the field Format, or an output format such as X_65_80, X_65_13 2.

19.6.8 Archiving 19.6.8.1 Maintain List Types for Optical Archiving Optical Archiving In excise duty, lists (simple lists, ALV lists, forms) can be arch ived and reissued as originals at a later point in time.

______________________________________________________________ SAP AG 17

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

Use The lists are grouped to ensure they can be found from the archive again from the point of view of excise duty.

19.6.8.2 Maintain Parameters for Optical Archiving Maintenance of the archiving parameters for the optical archiving in Excise Duties. A valid entry for each list output that shall be archived in Excise Duties

needs to be stored here.

19.6.9 Customer-Specific Texts 19.6.9.1 Inserted Sheets in Collective Filing Customer-Specific Texts Here, customer-specific texts can be stored for certain areas. Onl y inserted sheets for the collective filing are currently supported. Use A text can be stored here for each tax type. If the field for the tax warehouse is left blank, the text is valid for all tax warehouses of the tax type. If a tax warehouse is specified, the specific text overrides the general text.

______________________________________________________________ SAP AG 18

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

19.6.10 Tax rates Definition of the tax rates for Excise Duties. At least one tax ra te must exist for each tax type. The field "tax warehouse" may usually remain initial.

19.6.11 More 19.6.11.1 Replace ED Standard Programs Use Using this table, standard reports for excise duty can be replaced with tax-specific or customer-specific programs. The replacement can be general, by tax type or by tax warehouse. The replacement programs created here are supplied with the same p arameters as the original programs. The authorization check must be carried out in the repla cement programs. The data in these tables is not changed by standard deliveries. If program names are changed, this table also needs to be updated accordingly.

19.6.11.2 Replace ED Standard Forms (SmartForms) Use Using this SmartForms table, the standard forms supplied for excis e duty can be replaced with

______________________________________________________________

SAP AG

19

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

customer-specific forms. It may make sense to replace the forms if the authorities responsible want to use a different form or will not accept the standard form. The interface (communication structure) of the customer-specific f orm must be identical to the standard form. The data in these tables is not changed by standard deliveries, it is merely enhanced. If the names of forms change at a later date, the table also needs to be updated with these changes.

19.6.11.3 Replace ED Standard Forms (SAP Script) Use Using this table for SAP Script, standard forms supplied for excis e duty can be replaced with customer-specific forms. It may make sense to replace the forms if the authorities responsible want to use a different form or will not accept the standard form. The interface (communication data structure), names of the pages, window, page window and elements of the customer-specific forms must be identical to the s tandard form. If the required changes cannot be made due to this, the standard program controlli ng form output can be copied, changed and replaced (see Replacing ED standard programs). The data in these tables is not replaced by standard deliveries, b ut are merely enhanced. If the

names of forms are changed at a later date, the relevant table als o needs to be updated accordingly.

19.6.11.4 Database Adjustment ED Read Operations Use Elimination of runtime problems for critical database accesses in the component Excise Duties. The access method can be influenced by database-dependent notes to the DB optimizer. You can either indicate these notes directly there or by means of an accor dingly created view for the table.

______________________________________________________________ SAP AG 20

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

By means of the notes the optimizer can be instructed to use a spe cific index. Requirements Before you have made the entries here you should make a comprehens ive analysis of the data distribution and the data base accesses existing in the component Excise Duties.

Warning Fehlerhafte DB-Optimiererhinweise knnen zum Programmabbruch fhren.

19.6.11.5 Error messages Use Here you find the short description of the reasons for rejection r egarding the rejected documents. You also have the option to determine whether a rejected document shall be reset by a document seletion to be reanalyzed in the next corresponding docum ent selection.

Activities Usually adjustments are not required in this context.

19.6.11.6 Report Thresholds Use Definition of the message thresholds.

______________________________________________________________ SAP AG 21

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes ______________________________________________________________

Activities Adjustments are not required.

______________________________________________________________ SAP AG 22

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Excise Duty

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

______________________________________________________________

Copyright Copyright(c) 2012 SAP AG. All rights reserved. Neither this document nor any part of it may be copied or reproduced i n any form or by any means or translated into another language, without the prior consent of SAP AG. The information contained in this document is subject to chang e without notice. SAP is a registered trademark of SAP AG. All other products which are mentioned in this documentation are regis tered or not registered trademarks of their respective companies.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes Table of Contents SAP AG ______________________________________________________________

19.6 19.6.1 19.6.1.1 19.6.1.2 19.6.1.3

Excise Duty Excise Duty Basic Data Basic Settings Maintain Tax Types Additional Charges

1 1 1 1 1

19.6.1.4 19.6.1.5 19.6.1.6 19.6.1.7 19.6.2 19.6.2.1 19.6.2.2 19.6.2.3 19.6.2.4 19.6.2.5 19.6.2.6 19.6.2.6.1 19.6.2.6.2 19.6.2.6.3 19.6.2.6.4 19.6.2.6.5 19.6.3 19.6.3.1 19.6.3.2 8 19.6.3.3 19.6.3.4 19.6.4 19.6.4.1 19.6.4.2 19.6.4.3 19.6.4.4 19.6.5 19.6.5.1 19.6.5.2 19.6.5.3 19.6.5.4 19.6.5.5 19.6.5.5.1 19.6.5.5.2

Maintain Procurement Types Schema 2 Assign Procurement Types to Schema 2 Maintain Tax Type Independent Material Groups 3 Maintain Tax Type Dependent Material Groups 3 Tax Warehouse 4 Define Tax Warehouse 4 Addresses for Tax Warehouse Settlement Unit Warehouse Assignment List Header Shrinkage Settings Define Storage Types 4 4 5 5 5 5

Shrinkage Storage Type 6 Shrinkage Storage Location 6 Theoretical Shrinkage 7 Actual Shrinkage 7 Special Partner Types 7 Definition of Special Partner Types in Excise Duties 7 Maintenance of Special Partner Types Allowed for Vendors Maintenance of Special Partner Types Allowed for Ship-To Parties 8 Assignment of Customer Group Ship-To Party to Special Partner Types 8 Stock Ledger Settings 9 Maintain Print Formats 9 Maintain Print Format Items 9 ALV: Maintain Additional Fields 10 ALV: Conditions for Filling Additional Fields 10 Movement Control 10 Movement Categories 10 Movement Category for Tax Type Movement Category for Movement Type Movement Category for Cost Center Stock Ledger Groups Create New Stock Ledger Groups Maintain Characteristics of Stock Ledger 11 12 12 13 13 Groups 14 14

19.6.5.5.3 Replace Stock Ledger Groups

______________________________________________________________ SAP AG iii

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Release Notes Table of Contents SAP AG ______________________________________________________________

19.6.5.5.4 19.6.5.5.5 19.6.5.6 19.6.6 19.6.6.1 19.6.7 19.6.8 19.6.8.1 19.6.8.2 19.6.9 19.6.9.1 19.6.10 19.6.11 19.6.11.1 19.6.11.2 19.6.11.3

Maintain Block Schema for Stock Ledger Groups 15 Assign Procurement Types to Block Schema 16 Permissible Subsequent Postings 16 Country-Specific Adjustments 16 Maintenance of EU-Affiliated Non-EU Countries 16 Print control 17 Archiving 17 Maintain List Types for Optical Archiving 17 Maintain Parameters for Optical Archiving 18 Customer-Specific Texts 18 Inserted Sheets in Collective Filing Tax rates More Replace ED Standard Programs Replace ED Standard Forms (SmartForms) Replace ED Standard Forms (SAP Script) 18 19 19 19 19 20 20 21 21

19.6.11.4 Database Adjustment ED Read Operations 19.6.11.5 Error messages 19.6.11.6 Report Thresholds

______________________________________________________________ SAP AG iv

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~