Re: Pricing Procedure -Print option

Hi
In Pricing Procedure - Print option what is the difference between X ,S and A.
Regards
Debasish

Dear Debashish,
I am sure you read the F1 help. but still would like to put my view in hope that it will resolve your problem.
As per my understanding of the explanation given there goes, these field follow a standard logic, which is already mentioned in F1 help. I will try to elaborate the same. and sure will make more sense.
if you leave it blank,
Point 1 : System will consider all the pricing conditions (e.g PR00 ),etc available in pricing and at the end of these conditions last condition will be determined with "X"
point 2 : all the condition values which are smaller than pricing (e.g PR00 value )will only be printed if the print field is marked either with "X"  or "S"
Point 3 : all the conditions which are greater than the pricing condition (e.g PR00) and are coming before the tax conditions the field will be automatically marked as "S" ( which is nothing but for totals of few conditins )
Poiint 4: all the tax conditions are always marked with "S"
Point 5 : if  you want to mark the field "s" it should fullfill criteria as
                         A) condition types which are non zero
                         B) are not tax conditions also,
             condition lines in pricing procedure which are not condition types e.g sub totals, you can mark the field as "X" or "S" but they will get printed only if the condition line has different value than the earlier condition line.
Please also read the next explanation given in F1 help will be useful.
Please close the thread if answered.
Regards,
Paresh

Similar Messages

  • Standard Pricing Procedure Control Options

    Hi,
    Need to know the use of columns in control tab of the pricing procedure like: counter,  From & To with an example.
    Say i have 10 - 100 steps ....
    In the 50th step i have From as 10 and To as 40......what will happen for the 50 th step condition value....Also, in the 50 th step you have condition type and condition records are maintained.......
    Regards

    Hi,
    Hope the below reply helps you.
    Step:
    Number that determines the sequence of the conditions with in a procedure.
    It indicates the position of the condition type in pricing procedure.
    Ex.: 10, 15 etc.
    Counter:
    System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
    Access number of the conditions with in a step in the pricing procedure.
    During automatic pricing, the system takes into account the sequence specified by the counter.
    Condition Type:
    It represents pricing element in pricing procedure as a base price, discount, freight and tax.
    The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
    Ex.: PR00 - Price
    K004 - Material Discount
    K005 - Customer/Material Discount
    K007 - Customer Discount.
    Description:
    System copies description of condition type from its description (V/06).
    From and To:
        1. From: This can be used as a base to the condition type for calculating further value.
        2. From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
    Manual:
    This indicator specifies whether the specific condition type can be determined manually during sales order processing.
    If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
    For Base Price and Taxes, the entry should be automatic.
    For Discounts and Freights, The entry should be manual.
    If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
    If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
    Mandatory:
    This indicator specifies that particular condition type is mandatory in the pricing procedure.
    If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
    If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
    Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
    If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
    Statistical:
    This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    It is used only for information purposes only.
    This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    This is commonly used for condition types
    SKTO - Cash Discount
    VPRS - Cost (Moving average price/Standard Price).
    Print:
    The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
    Subtotal:
    The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
    Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
    If the same fields are used to store different condition amounts, the system totals the individual amounts.
    These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
    Requirement:
    It is a routine that is written by an ABAP consultant according to the business requirement.
    By defining Requirement in condition technique we can restrict the access of condition type.
    To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    This Requirement will ensure that these condition types will appear only during the billing document processing.
    If new Requirements are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Requirements" in the top menu and then click on "pricing".
    We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    And we assign the application type like V - Sales/Distribution etc.
    AltCty - Condition formula for alternative calculation type:
    It is again a Routine that is written by ABAP Consultant.
    It is an alternative formula for the condition type that can be used instead of standard formulas.
    For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
    Ex.: 950 0 Profit Margin 11.
    So we assign 11 - Profit Margin.
    If new routines are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Formulas" and then on the "Condition Values".
    We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    And we assign the application type.
    AltCBV - Alternative formula for condition base value:
    Formula for determining the condition basis as an alternative to the standard.
    It is again a Routine that is written by ABAP Consultant.
    It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
    Ex.: Freight - KF00.
    Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
    In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
    During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
    Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
    AcyKy - Account Key/ Accrls - Accruals:
    The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
    In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    ERB Rebate sales deduct.
    ERF Freight revenue
    ERL Revenue
    ERS Sales deductions
    ERU Rebate accruals
    For Ex.,
    For all Price condition types like PR00 etc. we assign ERL - Revenue.
    For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
    This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
    This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.

  • Pricing procedure print field

    hi,
    in v/08 pricing procedure what is the use of print indicator
    .1 Where the condition line gets printed is it in printout
    2 condition line means is it value & cindition type
    Pl suggest

    Hi,
    Print ID for condition lines
    Controls issue of condition lines when printing documents such as order confirmations or invoices.
    In releases previous to 4.0, the following print indicators are available :
    ' ' : Condition line is not printed
    'X' : Condition line is printed at item level
    'S' : Condition line is printed in totals block
    The following standard logic is set out for these printing indicators:
    Item POS of the last condition line is determined with 'X'.
    All condition lines that contain an item smaller than POS in the pricing procedure are only printed if print indicators 'X' or 'S' are set.
    All condition lines that contain an item larger than POS in the pricing procedure, that come before the first tax condition line and which have a non-statistical VAT condition, receive printing indicator 'S'. The same applies for condition lines that contain an item larger than POS in the pricing procedure, that come after the first tax condition line and an active non-statistical VAT condition.
    Condition lines that represent a tax condition type are always printed in totals blocks with print indicator 'S' (set internally or externally).
    Condition lines that represent a condition type that is not a tax condition type are only printed with print indicator 'S' (set externally or internally) if the condition value of the condition line is not zero. Condition lines that do not represent a condition type (i.e. subtotals) are only printed with print indicator 'S' or 'X' (set externally or internally) if the condition value of the condition line is different from the condition value of the previous condition line in the pricing procedure.
    To provide a better overview of this process, 8 more print parameters are available as of Release 4.0. These print indicators cannot, however be mixed with the three previous print indicators ' ', 'X' and 'S' in the pricing procedure. This means that the new indicators are only taken into account if a no condition lines in the pricing procedure contain printing indicators 'X' or 'S'.
    The new printing indicators have the following settings, and corresponding influence on processing.
    regards,
    US

  • Pricing procedure Print ID

    Hi friends,
    There is print field in pricing procedure called "a". If the Condition Type = 0 would it still be printed? If not is there a nother oppetunity to see "0" on the print?
    Thanks.

    Hello,
    This is the explanation as I have found it a couple of times:
    Controls issue of condition lines when printing documents such as order confirmations or invoices.
    Use
    In releases previous to 4.0, the following print indicators are available :
    o   ' ' : Condition line is not printed
    o   'X' : Condition line is printed at item level
    o   'S' : Condition line is printed in totals block
    The following standard logic is set out for these printing indicators:
    -     Item POS of the last condition line is determined with 'X'.
    -     All condition lines that contain an item smaller than POS in the pricing procedure are only printed if print indicators 'X' or 'S' are set.
    -     All condition lines that contain an item larger than POS in the pricing procedure, that come before the first tax condition line and which have a non-statistical VAT condition, receive printing indicator 'S'. The same applies for condition lines that contain an item larger than POS in the pricing procedure, that come after the first tax condition line and an active non-statistical VAT condition.
    -     Condition lines that represent a tax condition type are always printed in totals blocks with print indicator 'S' (set internally or externally).
    -     Condition lines that represent a condition type that is not a tax condition type are only printed with print indicator 'S' (set externally or internally) if the condition value of the condition line is not zero. Condition lines that do not represent a condition type (i.e. subtotals) are only printed with print indicator 'S' or 'X' (set externally or internally) if the condition value of the condition line is different from the condition value of the previous condition line in the pricing procedure.
    To provide a better overview of this process, 8 more print parameters are available as of Release 4.0. These print indicators cannot, however be mixed with the three previous print indicators ' ', 'X' and 'S' in the pricing procedure. This means that the new indicators are only taken into account if a no condition lines in the pricing procedure contain printing indicators 'X' or 'S'.
    The new printing indicators have the following settings, and corresponding influence on processing.
    -   'A' : in total: general
    -   'B' : in total: if value <> zero
    -   'C' : in total: if value <> value of predecessor
    -   'D' : in total: if value <> zero and value <> value of predecessor
    -   'a' : at item : general
    -   'b' : at item : if value <> zero
    -   'c' : at item : if value <> value of predecessor
    -   'd' : at item : if value <> zero and value <> value of predecessor
    Trust this helps.
    Regards,
    Jan Pel

  • Pricing condition type with print option

    I have a special requirement.  Printing option "b" maintained for condition type in pricing procedure.  Example ZR00.  For some customers this should not print and should allow only for specific customers.
    Any clue will appreciated.
    Please don't send the links.
    Suddu

    hi,
    is it that those conditons that are printed are only applicable to a particular customer.
    or
    though a conditoin is applicable but still you dont want to show.
    However my observation is, it requires some enhancement of Z table kind of thing. Reason is a discount which needs to be printed today may not be required tomorrow to be printed or the other way round. It depends on the customers business nature with your client. In such case it has to be part of master data where the enduser should have an option to make the necessary entries from time to time.
    If we hard code in the print program initially it can work. It will check the customer and print only those discounts but tomorrow if there is a change we have move a request to the print program again which is not the right approach.
    regards
    sadhu kishore

  • In pricing procedure In  What is use of printing  Indater  telme exactly

    Hi
    This is Mallik I ahve one question that In pricing procesure in 16 steps there is Printing  colum As per my knowledge this print particular condition type value in the document , but for Pr00 we will not assign Print option still it is prting in doc , tell me the exact use of this printing option

    Hi,
    your understanding is exactly correct..
    The print ID is used to specify the whether the condition amount will be printed or not.. and if printed at item level or at total column...
    coming to your second question.. in standard SAP PR00 is not used in printing.. we are printing only gross price which is calculated from PR00.. i will give you the reason why we are printing gross price instead of PR00.. sometimes we may need to give PB00 - manual gross price... if we give this condition type.. price will be taken from this condition type instead of PR00... at this time we need to print PB00 value instead of PR00.. so in standard they created a line gross price and printed the same...
    Hope you understand..
    if you still having doubt let me know...
    reward if helpful
    Muthupandiyan

  • Please explain the implication print ID in pricing procedure

    F1 help for Print Id in pricing procedure is confusing, can someone explain me please

    Hi,
    Print ID for condition lines
    Controls issue of condition lines when printing documents such as order confirmations or invoices.
    Use
    In releases previous to 4.0, the following print indicators are available :
    ' ' : Condition line is not printed
    'X' : Condition line is printed at item level
    'S' : Condition line is printed in totals block
    The following standard logic is set out for these printing indicators:
    Item POS of the last condition line is determined with 'X'.
    All condition lines that contain an item smaller than POS in the pricing procedure are only printed if print indicators 'X' or 'S' are set.
    All condition lines that contain an item larger than POS in the pricing procedure, that come before the first tax condition line and which have a non-statistical VAT condition, receive printing indicator 'S'. The same applies for condition lines that contain an item larger than POS in the pricing procedure, that come after the first tax condition line and an active non-statistical VAT condition.
    Condition lines that represent a tax condition type are always printed in totals blocks with print indicator 'S' (set internally or externally).
    Condition lines that represent a condition type that is not a tax condition type are only printed with print indicator 'S' (set externally or internally) if the condition value of the condition line is not zero. Condition lines that do not represent a condition type (i.e. subtotals) are only printed with print indicator 'S' or 'X' (set externally or internally) if the condition value of the condition line is different from the condition value of the previous condition line in the pricing procedure.
    To provide a better overview of this process, 8 more print parameters are available as of Release 4.0. These print indicators cannot, however be mixed with the three previous print indicators ' ', 'X' and 'S' in the pricing procedure. This means that the new indicators are only taken into account if a no condition lines in the pricing procedure contain printing indicators 'X' or 'S'.
    Kapil

  • Pricing procedure and CIN master

    Hi MM Gurus,
         I need one simple procedure for creating Pricing Procedure.........and ......creating Excise details and relating  and can anybody show how the pricing procedure and excise (CIN) is related .
    Regards,
    Girish.C.M

    Hi,
    CIN Setting:
    Check Calculation Procedure
    In this activity, you can check and, if necessary, change existing procedures for tax calculation.
    Standard settings
    Calculation procedures containing the necessary specifications for the calculation and posting of taxes on sales/purchases have already been defined in the standard SAP system for certain countries. Every calculation procedure groups several tax types together into a condition type (for example, output tax or input tax) in the calculation procedure, and determines calculation rules for it.
    The calculation procedure determines for which amount the individual condition types are to be calculated. This can be the base amount (total of the expense items and the revenue items) or a subtotal. The entry in column FrmLvl, determines for which amount tax is calculated.
    Note
    In this activity, the condition types for the check and the possible change provided in the standard system are also displayed. Here, for example, the condition calculation rule, or for which base amount the tax is calculated is determined (= condition type).
    Recommendation
    If possible, do not change the condition types and calculation procedures provided in the standard system. Only check the standard condition types and calculation procedures regarding whether you can use them for your requirements. If necessary, make changes.
    Activities
    If you cannot use the standard settings, change the condition types and calculation procedures delivered to meet your requirements.
    Procedure (pricing, output control, acct. det., costing,...)
    Specifies the conditions that are allowed for a document and defines the sequence in which they are used.
    Example
    Procedures are used, for example, in the following applications:
    · Pricing in sales and distribution
    · Applying overhead in Product Costing (costing sheets) and for CO internal orders
    · Calculating accrued costs in Profitability Analysis
    · Output control (printed confirmations, EDI messages, electronic mail)
    · Account determination
    · Calculating taxes on sales/purchases
    · Calculating accruals in Cost Center Accounting
    · Pricing for resource planning
    Definition: condition type
    Controlling (CO)
    A distinction, in overhead calculation, is made between:
    · Base condition types, which determine the object for which the overhead is to be calculated
    · Overhead condition types, which define the percentage overhead to be applied
    In resource planning, a condition type determines the types of resource prices that are stored in the SAP System. These can be absolute or percentage values, for example.
    Real Estate Management (RE)
    An exact definition of a condition that specifies the amount paid for a specific service.
    Condition types include:
    · Basic rent
    · Advance payment for operating costs
    · Pest control
    Sales and Distribution (SD)
    A characteristic of a condition.
    For example, in pricing, different condition types are used to distinguish between a discount that refers to a net price and a discount that refers to a gross price.
    Treasury (TR)
    A characteristic of a condition used to classify financial transactions.
    Typical examples of condition types are interest, dividends, or full repayment upon maturity. The various parameters specified for the individual condition types determine how the flows are calculated in the cash flow.
    Return ->
    Definition: condition_type
    Condition type
    The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
    Access sequence
    With the access sequence you define
    · the condition tables used to access the condition records
    · the sequence of the condition tables
    · which field contents are the criteria for reading the tables
    Assign Country to Calculation Procedure
    In this activity, you enter the key for the calculation procedure which determines the conditions which are allowed per document and which defines the sequence of the conditions in the document for each country.
    Requirements
    Each calculation procedure which you enter must contain the necessary specifications for calculating and posting the taxes on sales/purchases. For more information on this, read the chapter "Create calculation procedure".
    Activities
    1. Assign a procedure for tax calculation to every country with which your company has business dealings.
    2. Make sure that the corresponding data for calculating taxes is stored for each calculation procedure which you enter here.
    Check and Change Settings for Tax Processing
    In this activity you make the necessary specifications for posting taxes. In doing this you specify under a process key the following indicators:
    · Tax type
    Output tax, input tax, additional taxes, or "not tax-relevant" can be specified as the tax type.
    · Nondeductibility of tax amounts
    For this, tax amounts are marked as not deductible.
    · Posting indicator
    Here you specify whether the tax amount is posted separately or distributed to expense or revenue items.
    · Tax not relevant to cash discount (Not discount relevant)
    This indicator is set only for Canada. If you select it, the system does not take into account the corresponding tax amount when determining the tax base.
    Standard settings
    Process keys with the most important characteristics for tax amounts have already been set in the standard SAP system.
    Recommendation
    Do not change the standard settings. Check whether you can use these process keys for your company, making changes only if necessary.
    Activities
    If you cannot use the standard settings, use new process keys and enter them in your calculation procedure. Do not change the standard SAP process keys.
    Note
    You must make enhancements to the standard settings if you want to specify a new account key in the "Create calculation procedure" activity. You must create and maintain this key beforehand in the "Settings for tax processing" activity.
    Internal processing key
    The internal processing keys are used by the system to determine accounts or posting keys for line items which are created automatically.
    The processing keys are defined in the system and cannot be changed by the user.
    Definition: posting key
    Financial Accounting (FI)
    A two-digit numerical key that determines the way line items are posted.
    This key determines several factors including the:
    · Account type
    · Type of posting (debit or credit)
    · Layout of entry screens
    Return ->
    Definition: posting_key
    Maintain Excise Registrations
    Use
    In this IMG activity, you maintain the data relating to your excise registrations.
    Activities
    Enter each of your excise registrations, specifying a four-character code for each.
    Definition: excise registration
    Financial Accounting (FI)
    An entity in India that is entitled by law to produce any goods liable to excise.
    Each entity is assigned its own excise registration number.
    Every factory that manufactures excisable goods is required to register separately, so that a business with seven factories requires seven registrations.
    Return ->
    Definition: excise registration
    Maintain Company Code Settings
    Use
    In this IMG activity, you maintain the data relating to your company codes.
    Maintain Plant Settings
    Use
    In this IMG activity, you maintain excise information relating to your plants.
    Maintain Excise Groups
    Use
    In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
    Definition: excise group
    Financial Accounting (FI)
    A unit within an excise registration, in India, which keeps its own set of excise records.
    Whereas the excise registration reports to the excise authorities, the excise group is a purely internal organizational unit. Each excise group keeps records of all transactions that have to be reported to the excise authorities. When the time comes to present these records to the authorities, the excise registration compiles the information from all of its excise groups.
    Return ->
    Definition: excise group
    Maintain Series Groups
    Use
    In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
    Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    Activities
    · Define excise series groups based on type of outgoing document
    · Assign series group to excise registration ID
    · If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    · If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
    Example
    You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    Maintain Excise Duty Indicators
    Use
    In this IMG activity, you maintain the excise duty indicators.
    Maintain Postal Addresses
    Use
    In this IMG activity, you maintain the addresses of various customs and excise organizations that your company deals with.
    You use these addresses in the ARE Documents functions. When you create an ARE-1 or ARE-3, you enter the address of the excise department and the customs department involved in the export process. The system then prints their names and addresses on the AREs.
    You can then define a default local excise department for each excise group and a default customs department for each series group.
    Definition: ARE-1 document
    Logistics - General (LO)
    A form, in India, that companies have to fill out when they remove excisable goods from their manufacturing plants for export.
    The form exempts them from paying excise duty when they remove the goods from their premises.
    Return ->
    Definition: ARE-1 document
    Definition: ARE-3 document
    Logistics - General (LO)
    A form, in India, that allows companies to sell otherwise excisable goods from their premises without paying basic excise duty. The buyer of the goods must be in possession of a deemed export license.
    The ARE-3 states what goods are being removed and which deemed excise license covers it.
    Return ->
    Definition: ARE-3 document
    Maintain Subtransaction Type with Text
    Sub Transaction Type
    Sub transaction type is used for multiple purposes
    Subcontracting:
    It determines the subcontracting attributes and determines the accounts for the posting while doing a sub contracting transaction.
    Excise removals
    Sub transaction type is also used for determining the accounts while doing excise removals.
    With in CIN the account determination is based on the transaction type. So normally you can have a single set of accounts for Excise utilization. In case you need alternate account determination for handling various scenarios you can define sub transaction types. The sub transaction types and corresponding account assignments needs to be maintained in CIN customization
    Select Tax Calculation Procedure
    Use
    In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
    · If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    · If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
    This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
    We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
    Definition: condition-based excise determination
    Logistics - General (LO
    A method that the system uses of determining excise duty in India.
    This method requires you to create condition records for each combination of vendor or customer and material (and possibly other conditions).
    When you create a purchasing document, the system calls the tax procedure assigned to India. The tax procedure finds all of the condition records that you have created for that combination of vendor and material.
    When you create a sales document, the excise duties and sales taxes are determined by the pricing procedure (not the tax procedure).
    Return ->
    Definition: condition-based excise determination
    Definition: formula-based excise determination
    Logistics - General (LO)
    A method that the system uses of determining excise duty in India.
    This method was used in the Country Version India Add-On and requires you to maintain additional data in the Excise Rate Maintenance transaction, J1ID.
    When you create a purchasing document, the system calls the tax procedure assigned to India. Each of the excise duties in the tax procedure has its own condition types, and each condition type is assigned to a formula. This formula instructs the system to calculate the excise duty using the data that you have maintained in the Excise Rate Maintenance transaction.
    When you create a sales document, the system determines the excise duties and sales taxes using the pricing procedure (not the tax procedure).
    Return ->
    Definition: formula-based excise determination
    Maintain Excise Defaults
    Use
    In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
    Activities
    If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
    If you use formula-based excise determination, fill out all of the fields as follows:
    · Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    · Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    · Specify the conditions in the sales order that are used for excise rates.
    · Specify the countervailing duty condition type used for import purchase orders.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
    Definition: basic excise duty
    Financial Accounting (FI)
    The main type of excise duty in India.
    It is levied on a wide range of products, for example, foodstuffs, metals, jewellery, leather goods, and machinery.
    Return ->
    Definition: basic excise duty
    Definition: additional excise duty
    Financial Accounting (FI)
    A form of excise duty, in India, levied on a select range of products, for the most part, textiles.
    Return ->
    Definition: additional excise duty
    Definition: special excise duty
    Financial Accounting (FI)
    A form of excise duty in India on a limited number of goods, mostly luxury goods, including pan masala, sparkling waters, furs, and yachts.
    Return ->
    Definition: special excise duty
    Definition: cess
    Financial Accounting (FI)
    In India, a tax on the manufacture of certain products, mostly foodstuffs.
    Return ->
    Definition: cess
    Definition: countervailing duty
    Financial Accounting (FI)
    A form of excise duty imposed on imports that are subsidized by the country in which they were manufactured.
    Countervailing duty (also known as CVD) is intended to make the imports more expensive, thereby redressing any competitive advantage they might have over goods produced locally.
    Return ->
    Definition: countervailing duty
    Define Tax Code for Purchasing Documents
    Use
    In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
    Only carry out this activity if you use condition-based excise determination.
    Activities
    Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Deter
    Sales Tax Code
    The tax code represents a tax category which must be taken into consideration when making a tax return to the tax authorities.
    Tax codes are unique per country. The tax rate calculation rules and further features are stored in a table for each tax code.
    Procedure
    For tax-exempt or non-taxable transactions, you should use tax codes with a 0 percentage rate if the corresponding transactions are to be displayed in the tax returns.
    Note
    You must define new tax codes if tax rates are changed by the state. The old codes with the old tax rates must remain in the system until no more open items which use this tax code exist.
    Definition: tax code
    Financial Accounting (FI)
    A two-digit code that represents the specifications used for calculating and displaying tax.
    Examples of the specifications defined under the tax code are:
    · Tax rate
    · Type of tax (input tax or output tax)
    · Calculation method (percentage included or percentage separate)
    Return ->
    Definition: tax_code
    Definition: tax rate
    Financial Accounting (FI)
    The percentage rate used to calculate the tax amount.
    Return ->
    Definition: tax_rate
    Assign Tax Code to Company Codes
    Use
    In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
    Only carry out this activity if you use condition-based excise determination.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination
    Classify Condition Types
    Use
    In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
    The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
    In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
    · For taxes on purchases, use the condition types contained in the tax procedure.
    · For taxes on sales, use the condition types contained in the pricing procedures.
    Standard settings
    The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
    Use these settings as a basis for your own.
    Maintain Chapter IDs
    Use
    In this IMG activity, you maintain the chapter IDs and the corresponding descriptions as per the schedules published by the Central Board of Excise and Customs.
    Definition: chapter ID
    Logistics - General (LO)
    The number given to a material in the schedules of materials published by the government of India.
    The schedule lists all materials involved in manufacturing, input materials and output materials alike. It shows how much excise duty is levied on each material.
    Each material in the schedule is assigned its own identification code, called "chapter ID."
    Example
    The schedule contains an entry for ceramic roofing tiles, which are liable to basic excise duty at 16%. The chapter ID associated with these tiles is 6903.10.
    Return ->
    Definition: chapter ID
    Assign Users to Material Master Screen Sequence for Excise D
    Use
    In this IMG activity, you customize the material master data so that it shows the information relating to excise duty.
    Standard settings
    Country Version India comes with a screen sequence (IN) that shows the excise duty fields. You have to assign it to each of your users.
    Activities
    1. Double-click User Screen Reference.
    2. Assign all users who need to see the excise duty information to the screen reference IN.
    Example
    Name Screen Reference
    MISHRA IN
    Screen Sequence Number
    Alphanumeric key identifying the screen sequence. The screen sequence defines the sequence of information units in the material master dialog. A screen sequence is made up of data screens. For information on the screen sequences defined in the standard R/3 system, see the IMG documentation Configuring the Material Master.
    Note
    When creating a screen sequence, use an alphanumeric key beginning with the letter Y or Z (customer name range). This key cannot subsequently be changed.
    Dependencies
    You can assign screen sequences to users in the IMG activity Assign Screen Sequences to Users/Material Types/Transactions/Industry Sectors.
    Screen reference depending on the user
    Grouping of users that determines what screens are displayed in accordance with the user master record when you maintain material master records. It also determines the order in which the screens appear.
    Definition: user master record
    User and Authorization Management (BC-SEC-USR)
    Record that contains important master data for a user in the SAP System.
    The user master record contains the assignment of one or more roles to the user. This is how a user menu and the corresponding authorizations for the activities contained in the user menu are assigned to the user. Only users who have a user master record can log on to the system.
    Return ->
    Definition: user_master_record
    Define Form Types
    Use
    In this IMG activity, you define which form types you want to record in the system. You can only use form tracking for the form types that you enter here.
    Example
    · Form type: CT3
    · Form description: Concessional tax form
    · Status: Receive
    Define G/L Accounts for Taxes
    Use
    In this IMG activity, you specify which G/L accounts you will use to record which taxes.
    Requirements
    You have set up G/L accounts for each of the processing keys listed below.
    Activities
    Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
    · VS1 (basic excise duty)
    · VS2 (additional excise duty)
    · VS3 (special excise duty)
    · VS5 (sales tax setoff)
    · MWS (central sales tax)
    · MW3 (local sales tax)
    · ESA (service tax)
    · ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction
    Use
    In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
    If you use subtransaction types, enter the accounts for each subtransaction type as well.
    Activities
    Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
    The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
    Example
    Excise TT DC ind Account name
    GRPO CR CENVAT clearing account
    GRPO CR RG 23 BED account
    GRPO DR CENVAT on hold account
    Specify G/L Accounts per Excise Transaction
    Use
    In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
    When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
    · Excise group
    · Company code
    · Chart of accounts
    Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
    Requirements
    You have already:
    · Defined the G/L accounts
    · Defined the excise groups
    · Maintained the transaction accounts
    Activities
    For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
    Note
    You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
    Define Processing Modes Per Transaction
    Use
    In this IMG activity, you specify which processing modes the user can use in the various Incoming Excise Invoice transactions.
    This way, you can tailor the transaction to what your users have to do.
    Standard settings
    The system comes with three standard transactions relating to the Incoming Excise Invoices function (those that are included in the role SAP_CIN). The processing modes available in these transactions are as follows:
    · J1IEX_C
    This transaction is for excise clerks: users of this transaction can only capture and display excise invoices.
    · J1IEX_P
    This transaction is for excise supervisors: they can change, display, cancel, and post excise invoices.
    · J1IEX
    In this transaction, users can capture and post excise invoices, as well as displaying, changing, and canceling them.
    Activities
    If the standard settings meet your requirements, do not do anything.
    Otherwise, you can adjust the standard settings or you can create your own transactions. To do so:
    1. In Maintain Transaction, create a new transaction by making a copy of one of the standard transactions. Give the new transaction a transaction code of your choice.
    2. In this activity, enter data as follows:
    o Tcode: The transaction code that you have just created.
    o Proc. mode: Specify what the users of the transaction will do with the excise invoices.
    o Active: Select this indicator to activate the setting.
    Example
    You might want to create a transaction that only allows users to display excise invoices.
    Define Reference Documents Per Transaction
    Use
    In this IMG activity, you specify for each combination of transaction and processing mode which reference documents you want the users to be able to use.
    Activities
    If the standard settings meet your requirements, you do not have to do anything.
    Otherwise, add the entries that you need to the table: For each transaction, make one entry per combination of processing mode and reference document. Activate each entry for it to work.
    Definition: excise invoice reference document
    Logistics - General (LO)
    A document, in India, that you refer to when you enter an incoming excise invoice.
    If you have already posted the goods receipt, you can use the goods receipt document as the reference document. Otherwise, you can use the purchase order (or another purchasing document, such as a be a contract or a scheduling agreement).
    Example
    In the SAP System, you create a purchase order for 100 bags of sand and send the order to your vendor. Two weeks later, the vendor delivers the sand, accompanied by an excise invoice.
    When you enter the excise invoice in the system, you specify the number of the original purchase order: this is the reference document.
    Return ->
    Definition: excise invoice reference document
    Maintain Rejection Codes
    Use
    In this IMG activity, you define the rejection codes that are used in the Incoming Excise Invoices transaction.
    Activities
    For each rejection code, enter a code and a description. You can also specify whether the excise duty in the invoice is to be posted to the CENVAT on hold account, instead of the CENVAT clearing account.
    Specify Which Movement Types Involve Excise InvoicesUse
    In this IMG activity, you specify which movement types relating to goods receipts involve excise invoices.
    The system uses this information during the goods receipt procedure. When you post a goods receipt using one of the moevement types that you have specified here, the system prompts you to enter the excise invoice number.
    Note
    This option cannot be used for processing goods receipts without purchase orders.
    Maintain Default Excise Groups and Series Groups
    Use
    In this IMG activity, you specify which excise group and series group you want to appear in these fields by default. You can make separate settings for different combinations of sales organization, distribution channel, division, and shipping point.
    Activities
    This activity is optional, unless you want the system to automatically create outgoing excise invoices when you create a customer invoice.
    In this case, you must also make the appropriate setting in Customizing for Excise Duty, by choosing Basic Subcontracting Attributes
    Use
    The subcontracting attributes help determine conditions for a combination of an excise group, a transaction type, and a subtransaction type.
    The conditions such as the number of excise items per subcontracting challan, if the nonexciseable materials have to be filtered or not when the subcontracting challan is created, the movement type groups for issues and receipts and the hierarchy of determining the excise base value are mentioned here.
    Requirements
    Before you continue with this activity, work through the following activities:
    · Materials Management -> Inventory Management and Physical Inventory -> Goods Issue / Transfer Postings -> Define Screen Layout.
    For the movement type 541, maintain the field Purchase Order as an optional entry or as a required entry.
    · Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Maintain OutputTypes.
    Maintain the output type. On the Default Values tab, maintain the dispatch time and the transmission medium. Maintain the print parameter on the Print tab. This output type has to be maintained in this activity here.
    · Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Assign Forms andPrograms.
    Maintain the Program, FORM routine, and the form for the output type.
    · Materials Management -> Inventory Management and Physical Inventory -> Output Determination ->Printer Determination -> Printer Determination by Plant / Storage Location.
    Enter the output device that you use.
    Settings -> Maintain Excise Groups, and selecting Create EI (Create Excise Invoice Automatically).
    Maintain Movement Type Groups
    Use
    In this IMG activity, you group movement types together to form movement type groups.
    Definition: movement type
    Inventory Management (MM-IM)
    A classification key indicating the type of material movement (for example, goods receipt, goods issue, physical stock transfer).
    The movement type enables the system to find predefined posting rules determining how the accounts of the financial accounting system (stock and consumption accounts) are to be posted and how the stock fields in the material master record are to be updated.
    Return ->
    Definition: movement type
    Utilization Determination
    Use
    In this IMG activity, you specify which CENVAT accounts are to be debited by the Fortnight Utilization of CENVAT report: When the report calculates how much excise duty you must remit, it automatically proposes which CENVAT accounts the duty should be debited to. Here, you specify those defaults.
    You can either:
    · Debit all the excise duty to one account
    · Debit the excise duty to more than one account, in which case you specify which percentage is to be debited to each account
    Example
    If you want 50% of basic excise duty (BED) to be debited to the RG 23A account and the remaining 50% to the RG 23C account, you would make the following settings:
    Acct name BED perc.
    RG 23A BED account 50
    RG 23C BED account 50
    Alternatively, to debit all of the BED to the RG 23A account, and then RG 23C account, if there is not enough in the RG 23A account, you would make the following settings:
    Acct name BED perc. +
    RG 23A BED account X
    RG 23C BED account X
    When you come to run the report, the system takes the RG 23A account because it is the first one you have entered. If this account does not cover the BED, the system takes the RG 23C account instead.
    Maintain Minimum Balances for Excise Accounts
    Use
    In this IMG activity, you can maintain minimum balances in your excise accounts. When the balance in these accounts during utilization falls below this level, the system automatically utilizes funds in the PLA account.
    Activities
    Maintain the minimum balance amount for the excise accounts. If you have more than one excise group, you can maintain different minimum balances.
    Specify SAPscript Forms
    Use
    In this IMG activity, for each of your company codes, you specify which SAPscript forms the system prints the excise registers with.
    Standard settings
    Country Version India includes a number of sample SAPscript forms and printing programs, which you can use as follows:
    Reg. name Lay. no. Form Tcode/Prog
    RG 23A Part I 1 J_2IRG23A_PART1 J_2IRAP1
    RG 23C Part I 1 J_2IRG23C_PART1 J_2IRCP1
    RG 23A Part II 1 J_2IRG23A_PART2 J_2IRAP2
    RG 23C Part II 1 J_2IRG23C_PART2 J_2IRCP2
    PLA 1 J_2I_PLA J_2IPLA
    RG 23 D 1 J_2I_RG23D J_2IRG23
    RG 1 1 J_2I_RG1 J_2IRRG1
    RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
    RT 12 1 J_2I_RT12_ABSTRA J_2IRT12
    RT 12 1 J_2I_RT12_3 J_2IRT12
    The layout description can be left blank or an appropriate description maybe filled in. You may not change the register name. You can have your own layouts and maintain the name here. If the output device and number of copies are maintained it is automatically picked up for printing.
    Number Ranges
    You can maintain the number ranges for all CIN Number range objects using this transaction
    Activities
    Please maintain the number ranges for the folllowing objects The no nr has to be '01' for all
    1. j_1iintnum
    At an Excise group
    1. j_1irg23a1
    2. j_1irg23a2
    3. j_1iRG1
    4. j_1irg23c1
    5. j_1irg23c2
    6. j_1ipla2
    7. j_1iintpr2
    8. j_1irg23d
    9. j_1irg1_t ( material level)
    10. j_1iconpla ( if Consolidated PLA is used )
    At Series group
    1. j_1iexcloc
    2. j_1iexcexp
    3. j_1idepinv
    4. j_1i57Fc ( 57F Challans )
    Rewards if Helpful
    regards
    rb

  • Function module to pricing procedure calculation

    hi,
    I want to know whether any function modules available to get as I see in  Invoice ->
    select item level conditions.
    Where i can see the basic price ,discount, etc as defined in the corresponding pricing procedure.
    i have tried with
    RV_INVOICE_PRICE_PBO
    PRICING_SUBSCREEN_SET_DATA
    here i get only the records which have condition type,
    similarly for P.O. we have
    ME_SWP_SIC_GET_PRICING_INFO
    regards,
    Prabhu
    Points assured.

    REPORT  zmm_pvr.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                     TYPE-POOLS                                          *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    TYPE-POOLS slis.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                       TABLES                                            *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    TABLES: mara,                         " General Material Data
            marc,                         " Plant Data for Material
            ekko,                         " Purchasing Document Header
            ekpo,                         " Purchasing Document Item
            lfa1,                         " Vendor Master (General Section)
            konv,                         " Conditions (Transaction Data)
            mbew,                         " Material Valuation
            makt.                         " Material Descriptions
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                    DATA DECLARATION                                     *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    DATA: BEGIN OF i_mat OCCURS 1,
            matnr LIKE mara-matnr,
            mtart LIKE mara-mtart,
            werks LIKE marc-werks,
            abcin LIKE marc-abcin,
          END OF i_mat.
    DATA: BEGIN OF itab OCCURS 1,
            ebeln LIKE ekko-ebeln,
            bedat LIKE ekko-bedat,
            lifnr LIKE ekko-lifnr,
            waers LIKE ekko-waers,
            bukrs LIKE ekko-bukrs,
            ekorg LIKE ekko-ekorg,
            name1 LIKE lfa1-name1,
            werks LIKE ekpo-werks,
            menge LIKE ekpo-menge,
            meins LIKE ekpo-meins,
            netpr LIKE ekpo-netpr,
            netwr LIKE ekpo-netwr,
            menge1(16),
            netpr1(16),
            menge2  TYPE string,
            netpr2 TYPE string,
            lrate TYPE p DECIMALS 2,
            stax LIKE ekpo-netwr,
            exbed LIKE ekpo-netwr,
            dcost LIKE konv-kwert,
            nomvl LIKE ekpo-netwr,
            nomrt LIKE ekpo-netwr,
            zplp1 LIKE mbew-zplp1,
            verpr LIKE mbew-verpr,
            bgval LIKE ekpo-netwr,
            varnc LIKE ekpo-netwr,
            maktx LIKE makt-maktx,
            knumv LIKE ekko-knumv,
            ebelp LIKE ekpo-ebelp,
            matnr LIKE ekpo-matnr,
            matkl LIKE ekpo-matkl,
            mtart LIKE ekpo-mtart,
            bprme LIKE ekpo-bprme,
            txz01 LIKE ekpo-txz01,
            mwskz LIKE ekpo-mwskz,
            prdat LIKE ekpo-prdat,
          END OF itab.
    DATA: wtab LIKE itab.
    DATA: v_steuc TYPE marc-steuc.
    DATA: v_brsch TYPE lfa1-brsch.
    DATA: wa_komk TYPE komk.
    DATA: wa_komp TYPE komp.
    DATA: it_komv TYPE TABLE OF komv.
    DATA: wa_komv TYPE komv.
    DATA : wa_fieldcat TYPE  slis_fieldcat_alv,
           gt_fieldcat TYPE  slis_t_fieldcat_alv,
           wa_layout   TYPE  slis_layout_alv,
           lt_sort     TYPE  slis_t_sortinfo_alv,
           i LIKE sy-tabix.
    DATA: gt_events     TYPE slis_t_event.
    DATA: gd_prntparams TYPE slis_print_alv.
    DATA: it_color TYPE   slis_t_specialcol_alv.
    DATA: wa_color TYPE   slis_specialcol_alv.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          Begin Of Selection Screen                      *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    SELECTION-SCREEN BEGIN OF BLOCK pas WITH FRAME TITLE text-001.
    SELECT-OPTIONS s_matnr FOR  ekpo-matnr.
    SELECT-OPTIONS s_werks FOR  ekpo-werks.
    SELECT-OPTIONS s_bedat FOR  ekko-bedat.
    PARAMETERS     p_abcin LIKE marc-abcin OBLIGATORY.
    SELECTION-SCREEN END OF BLOCK pas.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                           INITIALIZATION                                *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    INITIALIZATION.
      IF sy-datum+4(2) GE 4.
        s_bedat-low+6(2) = 01.
        s_bedat-low+4(2) = 04.
        s_bedat-low(4) = sy-datum(4).
      ENDIF.
      IF sy-datum+4(2) LT 4.
        s_bedat-low+6(2) = 01.
        s_bedat-low+4(2) = 04.
        s_bedat-low(4) = sy-datum(4) - 1.
      ENDIF.
      s_bedat-high   = sy-datum.
      APPEND s_bedat.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                        AT Selection Screen Output                       *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    AT SELECTION-SCREEN.
    Check for Material Type
      SELECT amatnr amtart bwerks babcin INTO CORRESPONDING FIELDS OF TABLE i_mat
      FROM mara AS a INNER JOIN marc AS b
           ON amatnr = bmatnr
      WHERE a~matnr IN s_matnr
        AND ( amtart = 'IRAM' OR amtart = 'IPAM' OR amtart = 'PRAM' OR amtart = 'PPAM' )
        AND b~werks IN s_werks
        AND b~abcin = p_abcin.
      SORT i_mat BY matnr werks.
      CHECK NOT i_mat[] IS INITIAL.
      READ TABLE i_mat INDEX 1.
      IF sy-subrc <> 0.
        MESSAGE e006(zmm).
        LEAVE LIST-PROCESSING.
      ENDIF.
    Check for Date
      IF ( s_bedat-low IS INITIAL AND s_bedat-high IS INITIAL ).
        s_bedat-sign   = 'I'.
        s_bedat-option = 'BT'.
        IF sy-datum+4(2) GE 4.
          s_bedat-low+6(2) = 01.
          s_bedat-low+4(2) = 04.
          s_bedat-low(4) = sy-datum(4).
        ENDIF.
        IF sy-datum+4(2) LT 4.
          s_bedat-low+6(2) = 01.
          s_bedat-low+4(2) = 04.
          s_bedat-low(4) = sy-datum(4) - 1.
        ENDIF.
        s_bedat-high   = sy-datum.
      ELSEIF ( s_bedat-low IS NOT INITIAL AND s_bedat-high IS INITIAL ).
        s_bedat-low6(2) = s_bedat-low6(2).
        s_bedat-low4(2) = s_bedat-low4(2).
        s_bedat-low(4)   = s_bedat-low(4).
      ELSEIF ( s_bedat-low IS NOT INITIAL AND s_bedat-high IS NOT INITIAL ).
        s_bedat-sign   = 'I'.
        s_bedat-option = 'BT'.
        s_bedat-low6(2) = s_bedat-low6(2).
        s_bedat-low4(2) = s_bedat-low4(2).
        s_bedat-low(4)   = s_bedat-low(4).
        s_bedat-high6(2) = s_bedat-high6(2).
        s_bedat-high4(2) = s_bedat-high4(2).
        s_bedat-high(4)   = s_bedat-high(4).
      ENDIF.
      APPEND s_bedat.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                            START OF SELECTION                           *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    START-OF-SELECTION.
    *----- Get all PO for given selection criteria.
    LOOP AT i_mat.
      SELECT
        aebeln abedat alifnr aknumv awaers abukrs a~ekorg
        bebelp bmatnr bmatkl bnetpr bbprme btxz01 bwerks bmenge bmeins bnetwr bmtart bmwskz b~prdat
      FROM ( ekko AS a INNER JOIN ekpo AS b ON  amandt = bmandt AND aebeln = bebeln )
      INTO CORRESPONDING FIELDS OF TABLE itab
      FOR ALL ENTRIES IN i_mat
      WHERE a~bedat IN s_bedat
       AND  a~loekz = ''
       AND  b~matnr = i_mat-matnr
       AND  b~werks = i_mat-werks
       AND  b~loekz = ''
       AND  b~pstyp = '0'
       AND  b~bstyp = 'F'
       AND  b~knttp = ''.
    ENDLOOP.            " END OF i_mat
      CHECK NOT itab[] IS INITIAL.
      SORT itab BY ebeln ebelp.
    *----- Calculating The DCOST -- Delivery Cost
      DATA: BEGIN OF i_konv OCCURS 0,
             knumv LIKE konv-knumv,
             kposn LIKE konv-kposn,
             stunr LIKE konv-stunr,
             zaehk LIKE konv-zaehk,
             kschl LIKE konv-kschl,
             kbetr LIKE konv-kbetr,
             kwert LIKE konv-kwert,
           END OF i_konv.
      SELECT knumv kposn stunr zaehk kschl kbetr kwert
      FROM konv
      INTO CORRESPONDING FIELDS OF TABLE i_konv
      FOR ALL ENTRIES IN itab
      WHERE knumv = itab-knumv
       AND kposn = itab-ebelp
        AND ( kschl   = 'ZFC3' OR kschl   = 'ZQIQ'
           OR kschl   = 'ZQIV' OR kschl   = 'ZFA3'
           OR kschl   = 'ZFB3' OR kschl   = 'ZPF2'
           OR kschl   = 'ZPQ2' OR kschl   = 'ZPV2'
           OR kschl   = 'ZOCP' OR kschl   = 'ZOCQ'
           OR kschl   = 'ZOCV' OR kschl   = 'ZMT1'
           OR kschl   = 'ZIN2' OR kschl   = 'ZIQ2'
           OR kschl   = 'ZIV2' OR kschl   = 'ZBK1'
           OR kschl   = 'ZBKQ' OR kschl   = 'ZBKV' ).
      SORT i_konv BY knumv kposn stunr zaehk kschl .
      DELETE ADJACENT DUPLICATES FROM i_konv.
      DELETE i_konv WHERE kbetr = 0.
      DATA: BEGIN OF i_knumv OCCURS 0,
              knumv LIKE konv-knumv,
              kwert LIKE konv-kwert,
            END OF i_knumv.
      LOOP AT i_konv.
        MOVE i_konv-knumv TO i_knumv-knumv.
        MOVE i_konv-kwert TO i_knumv-kwert.
        COLLECT i_knumv.
      ENDLOOP.
      CLEAR i_konv.
      CLEAR i_knumv.
      LOOP AT itab INTO wtab.
        READ TABLE i_knumv WITH KEY knumv = wtab-knumv.
        IF sy-subrc = 0.
          wtab-dcost = i_knumv-kwert.
          MODIFY itab FROM wtab.
        ENDIF.
      ENDLOOP.
      CLEAR i_knumv.
      CLEAR itab.
    *----- Get the vendor name.
      LOOP AT itab.
        SELECT SINGLE name1 FROM lfa1 INTO itab-name1
                                        WHERE lifnr = itab-lifnr.
        MODIFY itab INDEX sy-tabix TRANSPORTING name1.
      ENDLOOP.
    *----- Calculate Excise Duty, Educat. cess, Sec edu. cess, sales tax
      CLEAR: wa_komk, wa_komp.
    Selecting The Value Of STEUC (Controlling Code)
      CLEAR itab.
      LOOP AT itab.
        SELECT SINGLE steuc
          FROM marc
          INTO v_steuc
         WHERE matnr = itab-matnr
           AND werks = itab-werks.
    Selecting The Value Of BRSCH (Industry key)
        SELECT SINGLE brsch
          FROM lfa1
          INTO v_brsch
         WHERE lifnr = itab-lifnr.
    Filling KOMK (Header Structure)
        wa_komk-kappl     = 'TX'.
        wa_komk-kalsm     = 'TAXINN'.
        wa_komk-lifnr     = itab-lifnr.
        wa_komk-waerk     = itab-waers.
        wa_komk-aland     = 'IN'.
        wa_komk-hwaer     = 'INR'.
        wa_komk-bukrs     = itab-bukrs.
        wa_komk-brsch     = v_brsch.
        wa_komk-prsdt     = itab-bedat.
        wa_komk-ekorg     = itab-ekorg.
        wa_komk-mwskz     = itab-mwskz.
    Filling KOMP (Details Structure)
        wa_komp-kposn     = itab-ebelp.
        wa_komp-matnr     = itab-matnr.
        wa_komp-werks     = itab-werks.
        wa_komp-matkl     = itab-matkl.
        wa_komp-meins     = itab-meins.
        wa_komp-vrkme     = itab-bprme.
        wa_komp-netwr     = itab-netwr.
        wa_komp-wrbtr     = itab-netwr.
        wa_komp-mwskz     = itab-mwskz.
        wa_komp-netpr     = itab-netpr.
        wa_komp-mtart     = itab-mtart.
        wa_komp-kursk_dat = itab-prdat.
        wa_komp-steuc     = v_steuc.
        wa_komp-mgame     = itab-menge.
        wa_komp-mglme     = itab-menge.
        FREE it_komv.
    Calling The Pricing Function To Get GR EXCISE, GR ECES, GR VAT/CST
        CALL FUNCTION 'PRICING'
          EXPORTING
            calculation_type = 'B'
            comm_head_i      = wa_komk
            comm_item_i      = wa_komp
          TABLES
            tkomv            = it_komv.
    Calculating The Excise --excise duty
        DATA: l_kbetr        TYPE komv-kbetr.
        DATA: l_gr_excise    TYPE ekpo-brtwr.
        DATA: l_basic_gr_val TYPE ekpo-netpr.
        l_basic_gr_val = itab-netwr.
        CLEAR: l_kbetr, l_gr_excise.
        LOOP AT it_komv INTO wa_komv WHERE kschl = 'JMOP'
                                        OR kschl = 'JAOP'
                                        OR kschl = 'JMIP'
                                        OR kschl = 'JAOQ'.
          l_kbetr     = ( wa_komv-kbetr / 10 ).
          l_gr_excise = ( l_kbetr * l_basic_gr_val ) / 100.
        ENDLOOP.
        LOOP AT it_komv INTO wa_komv WHERE kschl = 'JAIP'
                                        OR kschl = 'JAIQ'
                                        OR kschl = 'JMIQ'
                                        OR kschl = 'JMOQ'.
          l_gr_excise = ( wa_komv-kbetr * l_basic_gr_val ).
        ENDLOOP.
    Calculating The ECES -- Educational Cess
        DATA l_gr_eces      TYPE ekpo-netpr.
        CLEAR: l_kbetr, l_gr_eces.
        LOOP AT it_komv INTO wa_komv WHERE kschl = 'ZECE'
                                        OR kschl = 'ZECN'.
          l_kbetr     = ( wa_komv-kbetr / 10 ).
          l_gr_eces   = ( l_kbetr * l_gr_excise ) / 100.
        ENDLOOP.
    Calculating The SECES -- Sec. Educational Cess
        DATA l_gr_secs      TYPE ekpo-netpr.
        CLEAR: l_kbetr, l_gr_secs.
        LOOP AT it_komv INTO wa_komv WHERE kschl = 'JSEP'
                                        OR kschl = 'JSEI'.
          l_kbetr     = ( wa_komv-kbetr / 10 ).
          l_gr_secs   = ( l_kbetr * l_gr_excise ) / 100.
        ENDLOOP.
    Calculating The VAT/CST --Sales Tax
        DATA l_gr_vatcst    TYPE ekpo-netpr.
        CLEAR: l_kbetr, l_gr_vatcst.
        LOOP AT it_komv INTO wa_komv WHERE kschl = 'JVRN'
                                        OR kschl = 'JVRD'
                                        OR kschl = 'JVCS'
                                        OR kschl = 'JVCD'
                                        OR kschl = 'JVCN'
                                        OR kschl = 'JIPS'
                                        OR kschl = 'JIPC'
                                        OR kschl = 'JIPL'.
          l_kbetr     = ( wa_komv-kbetr / 10 ).
          l_gr_vatcst = ( ( l_basic_gr_val + l_gr_excise + l_gr_eces + l_gr_secs ) * l_kbetr ) / 100.
        ENDLOOP.
    Calculating The NOMVL & NOMVR -- NOM Value (Setoff / Inventory ) & NOM Rate
        DATA: l_netpr TYPE ekpo-netpr,
              l_menge TYPE ekpo-menge,
              l_dcost TYPE ekpo-netwr,
              l_nomvl TYPE ekpo-netwr,
              l_nomrt TYPE ekpo-netwr.
        l_netpr = itab-netpr.
        l_menge = itab-menge.
        l_dcost = itab-dcost.
        CLEAR: l_nomvl, l_nomrt.
        LOOP AT it_komv INTO wa_komv WHERE kschl = 'JMOP'                        "------setoff
                                        OR kschl = 'ZECE'
                                        OR kschl = 'JSEP'.
          l_nomvl = ( l_netpr * l_menge ) + l_gr_vatcst + l_dcost - ( l_gr_excise + l_gr_eces + l_gr_secs ).
          l_nomrt =  l_nomvl / l_menge.
        ENDLOOP.
        LOOP AT it_komv INTO wa_komv WHERE kschl = 'JMIP'                        "-------inventory
                                        OR kschl = 'ZECN'
                                        OR kschl = 'JSEI'.
          l_nomvl = ( l_netpr * l_menge ) + l_gr_vatcst + l_dcost.
          l_nomrt =  l_nomvl / l_menge.
        ENDLOOP.
        itab-exbed = l_gr_excise + l_gr_eces + l_gr_secs.
        itab-stax  = l_gr_vatcst.
        itab-nomvl = l_nomvl.
        itab-nomrt = l_nomrt.
        MODIFY itab .
        CLEAR itab.
      ENDLOOP.           " end of itab
      LOOP AT itab WHERE exbed = 0.
        itab-nomvl = ( itab-netpr * itab-menge ) + itab-stax + itab-dcost.
        itab-nomrt = itab-nomvl / itab-menge.
        MODIFY itab INDEX sy-tabix TRANSPORTING nomvl nomrt.
      ENDLOOP.
    *----- Calculating The Budget Rate, Moving Average Price, Landed Rate & Material Description
      DATA: verp(15).
      DATA: matdes(40).
      LOOP AT itab.
        SELECT SINGLE zplp1 FROM mbew INTO itab-zplp1
                                        WHERE matnr = itab-matnr AND bwkey = itab-werks.
        SELECT SINGLE verpr FROM mbew INTO itab-verpr
                                        WHERE matnr = itab-matnr AND bwkey = itab-werks.
        itab-lrate = itab-netwr / itab-menge.
        SELECT SINGLE maktx FROM makt INTO itab-maktx
                                        WHERE matnr = itab-matnr AND spras = 'EN'.
        MODIFY itab INDEX sy-tabix TRANSPORTING zplp1 verpr lrate maktx.
        verp = itab-verpr.
        matdes = itab-maktx.
      ENDLOOP.
    *----- Calculating The Budget Value & Variance
      LOOP AT itab.
        itab-bgval = itab-zplp1 * itab-menge.
        itab-varnc = itab-bgval - itab-nomvl.
        MODIFY itab INDEX sy-tabix TRANSPORTING bgval varnc.
      ENDLOOP.
    *------ Calculating Total of Quantity
      DATA: BEGIN OF i_quan OCCURS 1,
               quant LIKE ekpo-menge,
               unit LIKE ekpo-meins,
               nomvl LIKE ekpo-netwr,
               curr LIKE ekko-waers,
               varnc LIKE ekpo-netwr,
               bgval LIKE ekpo-netwr,
             END OF i_quan.
      LOOP AT itab.
        MOVE itab-menge TO i_quan-quant.
        MOVE itab-meins TO i_quan-unit.
        MOVE itab-nomvl TO i_quan-nomvl.
        MOVE itab-waers TO i_quan-curr.
        MOVE itab-varnc TO i_quan-varnc.
        MOVE itab-bgval TO i_quan-bgval.
        COLLECT i_quan.
      ENDLOOP.
      CLEAR itab.
      CLEAR i_quan.
      DATA: qty(15).
      DATA: unt(3).
      DATA: wtd TYPE p DECIMALS 2.
      DATA: wtd2(15).
      DATA: cur(3).
      DATA: var(15).
      DATA: nomvl(15).
      DATA: bgval(15).
      DATA: bgv TYPE p DECIMALS 2.
      DATA: bgv2(15).
      LOOP AT i_quan.
        qty = i_quan-quant.
        unt = i_quan-unit.
        cur = i_quan-curr.
        var = i_quan-varnc.
        bgval = i_quan-bgval.
        nomvl = i_quan-nomvl.
        wtd = nomvl / qty.
        bgv = bgval / qty.
      ENDLOOP.
      CLEAR i_quan.
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                          DATA DISPLAY                                   *
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      wa_fieldcat-fieldname  = 'EBELN'.
      wa_fieldcat-seltext_l  = 'Purchase Order'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 1.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'BEDAT'.
      wa_fieldcat-seltext_l  = 'PO Date'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 2.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'NAME1'.
      wa_fieldcat-seltext_l  = 'Vendor Name'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 3.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'WERKS'.
      wa_fieldcat-seltext_l  = 'Plant'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 4.
      APPEND wa_fieldcat TO gt_fieldcat.
    wa_fieldcat-fieldname  = 'MENGE2'.
      wa_fieldcat-fieldname  = 'MENGE'.
      wa_fieldcat-seltext_l  = 'Quantity'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 5.
      wa_fieldcat-do_sum     = 'X'.
      APPEND wa_fieldcat TO gt_fieldcat.
    wa_fieldcat-fieldname  = 'NETPR2'.
      wa_fieldcat-fieldname  = 'NETPR'.
      wa_fieldcat-seltext_l  = 'Basic Rate'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 6.
      wa_fieldcat-do_sum     = ' '.
      APPEND wa_fieldcat TO gt_fieldcat.
    wa_fieldcat-fieldname  = 'EXBED'.
    wa_fieldcat-seltext_l  = 'Excise'.
    wa_fieldcat-tabname    = 'ITAB'.
    wa_fieldcat-row_pos    = 1.
    wa_fieldcat-col_pos    = 7.
    APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'STAX'.
      wa_fieldcat-seltext_l  = 'Sale Tax'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 7.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'DCOST'.
      wa_fieldcat-seltext_l  = 'Delivery Cost'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 8.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'NETWR'.
      wa_fieldcat-seltext_l  = 'Landed Value'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 9.
      wa_fieldcat-do_sum     = 'X'.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'LRATE'.
      wa_fieldcat-seltext_l  = 'Landed Rate'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 10.
      wa_fieldcat-do_sum     = ' '.
      APPEND wa_fieldcat TO gt_fieldcat.
    wa_fieldcat-fieldname  = 'NOMVL'.
    wa_fieldcat-seltext_l  = 'NOM Value'.
    wa_fieldcat-tabname    = 'ITAB'.
    wa_fieldcat-row_pos    = 1.
    wa_fieldcat-col_pos    = 12.
    wa_fieldcat-do_sum     = 'X'.
    APPEND wa_fieldcat TO gt_fieldcat.
    wa_fieldcat-fieldname  = 'NOMRT'.
    wa_fieldcat-seltext_l  = 'NOM Rate'.
    wa_fieldcat-tabname    = 'ITAB'.
    wa_fieldcat-row_pos    = 1.
    wa_fieldcat-col_pos    = 13.
    wa_fieldcat-do_sum     = ' '.
    APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'BGVAL'.
      wa_fieldcat-seltext_l  = 'Budget Value'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 11.
      wa_fieldcat-do_sum     = 'X'.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'ZPLP1'.
      wa_fieldcat-seltext_l  = 'Budget Rate'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 12.
      wa_fieldcat-do_sum     = ' '.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_fieldcat-fieldname  = 'VARNC'.
      wa_fieldcat-seltext_l  = 'Variance'.
      wa_fieldcat-tabname    = 'ITAB'.
      wa_fieldcat-row_pos    = 1.
      wa_fieldcat-col_pos    = 13.
      wa_fieldcat-do_sum     = 'X'.
      APPEND wa_fieldcat TO gt_fieldcat.
      wa_layout-colwidth_optimize = 'X'.
      wa_layout-zebra = ' '.
      DATA: ls_event TYPE slis_alv_event.
      CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
        EXPORTING
          i_list_type = 0
        IMPORTING
          et_events   = gt_events[].
      READ TABLE gt_events WITH KEY name =  slis_ev_end_of_page
                               INTO ls_event.
      IF sy-subrc = 0.
        MOVE 'END_OF_PAGE' TO ls_event-form.
        APPEND ls_event TO gt_events.
      ENDIF.
      READ TABLE gt_events WITH KEY name =  slis_ev_end_of_list
                             INTO ls_event.
      IF sy-subrc = 0.
        MOVE 'END_OF_LIST' TO ls_event-form.
        APPEND ls_event TO gt_events.
      ENDIF.
      gd_prntparams-reserve_lines = '7'.   "Lines reserved for footer
      gd_prntparams-no_coverpage = 'X'.
      CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
       EXPORTING
      I_INTERFACE_CHECK                 = ' '
      I_BYPASSING_BUFFER                = ' '
      I_BUFFER_ACTIVE                   = ' '
                i_callback_program        = sy-repid
      I_CALLBACK_PF_STATUS_SET          = ' '
      I_CALLBACK_USER_COMMAND           = ' '
           i_callback_top_of_page            = 'TOP-OF-PAGE'
      I_CALLBACK_HTML_TOP_OF_PAGE       = ' '
      i_callback_html_end_of_list           = 'END_OF_LIST_HTML'
      I_STRUCTURE_NAME                  =
      I_BACKGROUND_ID                   = ' '
      I_GRID_TITLE                      =
      I_GRID_SETTINGS                   =
                is_layout                 = wa_layout
                it_fieldcat               = gt_fieldcat
      IT_EXCLUDING                      =
      IT_SPECIAL_GROUPS                 =
      IT_SORT                           =
      IT_FILTER                         =
      IS_SEL_HIDE                       =
             i_default                    = 'X'
             i_save                       = 'X'
      IS_VARIANT                        =
       it_events                         = gt_events
      IT_EVENT_EXIT                     =
      is_print                          = gd_prntparams
      IS_REPREP_ID                      =
      I_SCREEN_START_COLUMN             = 0
      I_SCREEN_START_LINE               = 0
      I_SCREEN_END_COLUMN               = 0
      I_SCREEN_END_LINE                 = 0
      I_HTML_HEIGHT_TOP                 = 0
      I_HTML_HEIGHT_END                 = 0
      IT_ALV_GRAPHICS                   =
      IT_HYPERLINK                      =
      IT_ADD_FIELDCAT                   =
      IT_EXCEPT_QINFO                   =
      IR_SALV_FULLSCREEN_ADAPTER        =
    IMPORTING
      E_EXIT_CAUSED_BY_CALLER           =
      ES_EXIT_CAUSED_BY_USER            =
        TABLES
          t_outtab                          = itab
       EXCEPTIONS
         program_error                     = 1
         OTHERS                            = 2
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
    *&      Form  top-of-page
          text
    -->  p1        text
    <--  p2        text
    FORM top-of-page .
    ALV Header Declarations
      DATA: t_header TYPE slis_t_listheader,
            wa_header  TYPE slis_listheader,
           wa_header1 TYPE slis_listheader,
           wa_header2 TYPE slis_listheader,
           wa_header3 TYPE slis_listheader,
            wa_header4 TYPE slis_listheader.
    Title
      wa_header-typ = 'H'.
      wa_header-info = 'Purchase Variance Report'.
      APPEND wa_header TO t_header.
      CLEAR wa_header.
    Material
    SHIFT p_matnr LEFT DELETING LEADING '0'.
    wa_header1-typ = 'S'.
    wa_header1-info = ' '.
    CONCATENATE 'Material : ' p_matnr matdes INTO wa_header1-info SEPARATED BY space.
    APPEND wa_header1 TO t_header.
    CLEAR wa_header1.
    Plant
    IF ( s_werks-low IS NOT INITIAL AND s_werks-high IS NOT INITIAL ).
       wa_header2-typ = 'S'.
       wa_header2-info = ' '.
       CONCATENATE 'Plant : ' s_werks-low 'to' s_werks-high INTO wa_header2-info SEPARATED BY space.
       APPEND wa_header2 TO t_header.
       CLEAR wa_header2.
    ELSEIF ( s_werks-low IS NOT INITIAL AND s_werks-high IS INITIAL ).
       wa_header2-typ = 'S'.
       wa_header2-info = ' '.
       CONCATENATE 'Plant : ' s_werks-low INTO wa_header2-info SEPARATED BY space.
       APPEND wa_header2 TO t_header.
       CLEAR wa_header2.
    ELSEIF ( s_werks-low IS INITIAL AND s_werks-high IS INITIAL ).
       EXIT.
    ENDIF.
    Period
      IF ( s_bedat-low IS NOT INITIAL AND s_bedat-high IS INITIAL ).
        wa_header4-typ = 'S'.
        wa_header4-info = ' '.
        CONCATENATE 'Period : '
                    s_bedat-low+6(2) '.'
                    s_bedat-low+4(2) '.'
                    s_bedat-low(4) INTO wa_header4-info SEPARATED BY space.
        APPEND wa_header4 TO t_header.
        CLEAR wa_header4.
      ELSE.
    IF ( s_bedat-low IS INITIAL AND s_bedat-high IS INITIAL ).
        wa_header4-typ = 'S'.
        wa_header4-info = ' '.
        CONCATENATE 'Period : '
                    s_bedat-low+6(2) '.'
                    s_bedat-low+4(2) '.'
                    s_bedat-low(4)
                    'to'
                    s_bedat-high+6(2) '.'
                    s_bedat-high+4(2) '.'
                    s_bedat-high(4) INTO wa_header4-info SEPARATED BY space.
        APPEND wa_header4 TO t_header.
        CLEAR wa_header4.
      ENDIF.
      CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
        EXPORTING
          it_list_commentary = t_header.
      I_LOGO                   =
      I_END_OF_LIST_GRID       =
      I_ALV_FORM               =
    ENDFORM.                    " top-of-page
    *&      Form  end_of_list_html
          output at the end of the list - not in printed output       *
    FORM end_of_list_html USING end TYPE REF TO cl_dd_document.
      DATA: ls_text TYPE sdydo_text_element,
            l_grid     TYPE REF TO cl_gui_alv_grid,
            f(14) TYPE c VALUE 'SET_ROW_HEIGHT'.
      DATA: qty1 TYPE sdydo_text_element.
      DATA: unt1 TYPE sdydo_text_element.
      DATA: wtd1 TYPE sdydo_text_element.
      DATA: cur1 TYPE sdydo_text_element.
      DATA: var1 TYPE sdydo_text_element.
      DATA: verp1 TYPE sdydo_text_element.
      DATA: bgv1 TYPE sdydo_text_element.
      qty1 = qty.
      unt1 = unt.
      wtd1 = wtd.
      cur1 = cur.
      var1 = var.
      verp1 = verp.
      bgv1 = bgv.
      ls_text = 'SUMMARY'.
      CALL METHOD end->add_text
        EXPORTING
          text         = ls_text
          sap_emphasis = 'strong'.
    Total Qty Bought (start new line)
      CALL METHOD end->new_line.
      CALL METHOD end->add_text
        EXPORTING
          text = 'Total Qty Bought : '.
      CALL METHOD end->add_text
        EXPORTING
          text = qty1.
      CALL METHOD end->add_text
        EXPORTING
          text = unt1.
    Wtd. Avg. Purchase Rate
      CALL METHOD end->new_line.
      CALL METHOD end->add_text
        EXPORTING
          text = 'Wtd. Avg. Purchase Rate : '.
      CALL METHOD end->add_text
        EXPORTING
          text = cur1.
      CALL METHOD end->add_text
        EXPORTING
          text = wtd1.
    Wtd. Avg. Budget Rate
      CALL METHOD end->new_line.
      CALL METHOD end->add_text
        EXPORTING
          text = 'Wtd. Avg. Budget Rate : '.
      CALL METHOD end->add_text
        EXPORTING
          text = cur1.
      CALL METHOD end->add_text
        EXPORTING
          text = bgv1.
    Gain / Loss
      CALL METHOD end->new_line.
      CALL METHOD end->add_text
        EXPORTING
          text = 'Gain / Loss : '.
      CALL METHOD end->add_text
        EXPORTING
          text = cur1.
      CALL METHOD end->add_text
        EXPORTING
          text = var1.
    MAP ( Moving Average Price )
      CALL METHOD end->new_line.
      CALL METHOD end->add_text
        EXPORTING
          text = 'Mov Avg Price : '.
      CALL METHOD end->add_text
        EXPORTING
          text = cur1.
      CALL METHOD end->add_text
        EXPORTING
          text = verp1.
    ENDFORM. "end_of_list_html.
    *&      Form  END_OF_PAGE
    FORM end_of_page.
      DATA: listwidth TYPE i,
            ld_pagepos(10) TYPE c,
            ld_page(10)    TYPE c.
      wtd2 = wtd.
      bgv2 = bgv.
      CONDENSE qty.
      CONDENSE unt.
      CONDENSE wtd2.
      CONDENSE bgv2.
      CONDENSE var.
      CONDENSE verp.
      SKIP.
      WRITE:/ 'SUMMARY:'.
    write:/ sy-uline(7).
      WRITE:/ 'Total Qty Bought        : ', qty, unt.
      WRITE:/ 'Wtd. Avg. Purchase Rate : ', wtd2, cur.
      WRITE:/ 'Wtd. Avg. Budget Rate   : ', bgv2, cur.
      WRITE:/ 'Gain / Loss             : ', var, cur.
      WRITE:/ 'Mov Avg Price           : ', verp, cur.
    ENDFORM.                    "END_OF_PAGE
    *&      Form  END_OF_LIST
    FORM end_of_list.
      DATA: listwidth TYPE i,
            ld_pagepos(10) TYPE c,
            ld_page(10)    TYPE c.
      wtd2 = wtd.
      bgv2 = bgv.
      CONDENSE qty.
      CONDENSE unt.
      CONDENSE wtd2.
      CONDENSE bgv2.
      CONDENSE var.
      CONDENSE verp.
      SKIP.
      WRITE:/ 'SUMMARY:'.
    write:/ sy-uline(7).
      WRITE:/ 'Total Qty Bought        : ', qty, unt.
      WRITE:/ 'Wtd. Avg. Purchase Rate : ', wtd2, cur.
      WRITE:/ 'Wtd. Avg. Budget Rate   : ', bgv2, cur.
      WRITE:/ 'Gain / Loss             : ', var, cur.
      WRITE:/ 'Mov Avg Price           : ', verp, cur.

  • Columns in Pricing Procedure

    Hi..
    What is the meaning of this column in the pricing procedure?
    Regds
    Shriniwas

    hi
    https://www.sdn.sap.com/irj/sdn/wiki?path=/display/erplo/16FieldsDescriptioninPricing+Procedure&
    16 columns - Define Pricing Procedure
    •     Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
    •     Highlight it and double click the Control icon in the LHS screen.
    •     We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
    •     The detail description of each column is given below.
    <b>Step</b>:
    •     Number that determines the sequence of theconditionswithin a procedure.
    •     It indicates the position of the condition type in pricing procedure.
    •     Ex.: 10, 15 etc.
    <b>Counter</b>:
    •     System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
    •     Access number of the conditionswithin a step in the pricing procedure.
    •     During automatic pricing, the system takes into account the sequence specified by the counter.
    <b>Condition Type</b>:
    •     It represents pricing element in pricing procedure as a base price, discount, freight and tax.
    •     The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
    •     Ex.: PR00 - Price
    K004 - Material Discount
    K005 - Customer/Material Discount
    K007 - Customer Discount.
    <b>Description</b>:
    •     System copies description of condition type from its description (V/06).
    <b>From and To</b>:
    1.     From:This can be used as a base to the condition type for calculating further value.
    1.     {}From and To: The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
    <b>Manual</b>:
    •     This indicator specifies whether the specific condition type can be determined manually during sales order processing.
    •     If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
    •     For Base Price and Taxes, the entry should be automatic.
    •     For Discounts and Freights, The entry should be manual.
    •     If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
    •     If we uncheck the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
    <b>Mandatory</b>:
    •     This indicator specifies that particular condition type is mandatory in the pricing procedure.
    •     If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
    •     If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
    •     Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
    •     If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
    <b>Statistical</b>:
    •     This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    •     It is used only for information purposes only.
    •     This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    •     This is commonly used for condition types
    o     SKTO - Cash Discount
    o     VPRS - Cost (Moving average price/Standard Price).
    <b>Print</b>:
    •     The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
    <b>Subtotal</b>:
    •     The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
    •     Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
    •     If the same fields are used to store different condition amounts, the system totals the individual amounts.
    •     These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
    <b>Requirement</b>:
    •     It is a routine that is written by an ABAP consultant according to the business requirement.
    •     By defining Requirement in condition technique we can restrict the access of condition type.
    •     To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    •     For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    •     This Requirement will ensure that these condition types will appear only during the billing document processing.
    •     If new Requirements are to be defined we follow the procedure given below.
    o     Go to T.Code: VOFM. - Maintain Requirements & Formulas
    o     Click on the "Requirements" in the top menu and then click on "pricing".
    o     We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    o     And we assign the application type like V - Sales/Distribution etc.
    <b>AltCty - Condition formula for alternative calculation type</b>:
    •     It is again a Routine that is written by ABAP Consultant.
    •     It is an alternative formula for the condition type that can be used instead of standard formulas.
    •     For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
    •     Ex.: 950 0 Profit Margin 11.
    •     So we assign 11 - Profit Margin.
    •     If new routines are to be defined we follow the procedure given below.
    o     Go to T.Code: VOFM. - Maintain Requirements & Formulas
    o     Click on the "Formulas" and then on the "Condition Values".
    o     We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    o     And we assign the application type.
    AltCBV - Alternative formula for condition base value:
    •     Formula for determining the condition basis as an alternative to the standard.
    •     It is again a Routine that is written by ABAP Consultant.
    •     It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
    •     Ex.: Freight - KF00.
    •     Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
    •     In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
    •     During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
    •     Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
    <b>AcyKy - Account Key/ Accrls - Accruals</b>:
    •     The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
    •     In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    o     ERB Rebate sales deduct.
    o     ERF Freight revenue
    o     ERL Revenue
    o     ERS Sales deductions
    o     ERU Rebate accruals
    •     For Ex.,
    o     For all Price condition types like PR00 etc. we assign ERL - Revenue.
    o     For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    o     For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    o     For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
    •     This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
    •     This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
    Reward if USeful
    Thanx & Regards
    Naren..

  • Pricing procedure+TAXINN

    Pl. give me configuration documents on Pricing +TAXINN procedure.
    E mail [email protected]
    Thanks
    Vaibhav

    In Indian Taxing procedure, Excise Duty plays a vital role in manufacturing cenario's. Excise related configuration is known as CIN configuration. CIN Configuration is a topic in itself.
    Some info on CIN Configuration (it may not appear as understandable below, but if you check on screen, it will be understood better):
    Country Version India comes with four pricing procedures as follows:
    1. JINFAC (Sales from manufacturing plants)
    2. JINEXP (Export sales)
    3. JINDEP (Sales from depots)
    4. JINSTK (Stock transfers
    CIN:
    IMG > Logistics - General > Tax on Goods Movement > India > Basic Settings >
    Maintain Excise Registrations
    Use
    In this IMG activity, you maintain the data relating to your excise registrations.
    Enter each of your excise registrations, specifying a four-character code for each Excise Registration IDs
    In this activity, you maintain excise registration IDs. You create one ID for each of your business's excise registrations.
    Activities
    For each excise registration in your business create a registration ID, and state:
    1. Which taxes the registration covers (additional excise duty, special excise duty, and cess)Fields for any taxes that are not covered will be hidden in transactions involving excise duty.
    2. The maximum number of items to be printed on each excise invoice
    3. Whether you are allowed partial CENVAT credits
    Maintain Registration ID NUMBER, Excise code number, excise registration number
    Excise Registration Number
    A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
    Every entity with an excise registration number is required to keep its own excise books.
    ECC Number
    Specifies the organization's ECC number.
    Excise Registration Number
    A number assigned to each premises or location that has registered as a manufacturer with the excise authorities.
    Every entity with an excise registration number is required to keep its own excise books.
    Excise range: Specifies the excise range in whose area the excise registration is located.
    Excise Division
    Specifies the excise division in whose area the excise registration is located.
    Excise Collectorate
    The code of the excise collectorate in whose area the excise registration is located.
    Indicator for confirming AED usage
    Additional Excise duty Percentage. These are leviable under the additional duties of excise act. These duties are in addition to basic excise duty and special excise duty.
    Example
    Additional Excise duty is leviable in case of textile products, tobacco and sugar.
    Similarly for SED CESS
    Number of Items in Excise Invoice
    Shows the maximum number of line items that the authorities allow per excise invoice.
    This information is used when you create an excise invoice in Sales and Distribution (SD) for factory sales and for other movements.
    This information is used to split the transfer postings' items into multiple subcontracting challans.
    Excise register set description
    Description of the excise registers set.
    Partial CENVAT Credit
    Indicates that the excise registration ID is allowed to credit only a portion of its input excise duty to its CENVAT account.
    Dependencies
    When you post a goods receipt, the system splits the input excise duty on the material into its deductible and nondeductible amounts. It posts the deductible duty to the appropriate CENVAT account, and adds the nondeductible duty to the material value.
    This information is also shown when you post the vendor's excise invoice.
    Maintain Company Code Settings
    Use
    In this IMG activity, you maintain the data relating to your company codes.
    Document Type for CENVAT Postings
    It controls, which document type the system uses when making CENVAT postings in Financial Accounting (FI). Here ED is document type for cenvat posting.
    Indicator for providing debit account overwriting
    Debit Account Overwrite Indicator. X - Indicates debit accounts can be overwritten. Use In excise journal voucher transaction. It provides the flexibility to the user to enter the debit account of his choice depending on the nature of transaction.
    Automatic balance Indicator
    Excise year start month
    The calendar month marking the beginning of the excise year
    Use
    This start month represents the month for the start of the excise invoice number range. The month 04 is entered here indicating April of the calendar year as the start month for excise invoices. Any change by the Excise authorities regarding start month should be taken care of by an entry in this field and initialization.
    Excise invoice selection procedure
    Excise invoice selection type. To indicate the method opted by the company for selecting the excise invoice. It can be either earliest or latest invoices that were received.
    Number of excise invoices to be selected
    Indicates the number of excise invoices that needs to be selected in the excise invoice selection.
    Days to be considered for excise invoice selection
    Number of days from document date for excise invoice selection.
    Example
    If the value of this field is 20 and today is 28-03-97. The excise
    invoice selection will show the related invoices only for the
    period 08-03-97 to 28-03-97.
    Document type for TDS FI posting
    Financial accounting document type for TDS posting.
    Document type for FI posting on Utilisation
    Financial accounting document type for TDS posting.
    Indicator for item level excise duty round off
    This indicator is to be used for deciding whether Item level excise duty amount rounding off is required during procurement cycle. If marked 'X' then the excise duty amount will be rounded off to the nearest rupee at the Purchase order level. This will not round off the CENVAT credit to be taken. If the duty amount is less than one rupee then no rounding is done
    Rounding off of Excise duty for outgoing excise invoice
    You can round off the Excise amount to be paid during an outgoing Excise invoice by marking this indicator as 'X'. The rounding is done at the item level for each item where the amount is greater than 1 Rupee.
    Immediate Credit on Capital Goods
    Instructs the system, when you verify a goods receipt for capital goods, to immediately post half of the input excise duty to the appropriate CENVAT accounts.
    The rest is posted the CENVAT on hold account, for use in the following year.
    CVD Clearing Account
    Specifies which G/L account the system credits when you take a CENVAT credit on countervailing duty in the Incoming Excise Invoices transaction.
    Exchange rate type
    Key representing a type of exchange rate in the system.
    Use
    You enter the exchange rate type to store different exchange rates.
    Example
    You can use the exchange rate type to define a buying rate, selling rate, or average rate for translating foreign currency amounts. You can use the average rate for the currency translation, and the bank buying and selling rates for valuation of foreign currency amounts.
    Exchange rate type to be used for Export excise duty converts
    When you are creating an Excise invoice for export sales then the exchange rate for duty calculation will be picked up using this Exchange rate type.
    Maintain Plant Settings
    Use
    In this IMG activity, you maintain excise information relating to your plants.
    Plant Settings
    In this activity, you maintain excise information relating to your plants.
    Activities
    For each plant:
    1. Specify whether it is a manufacturing site or a depot.
    2. Assign it an excise registration ID.
    You can assign the same ID to more than one plant, if required.
    Depot
    Indicates that the plant in question is a depot.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    Number of goods receipt per excise invoice.
    Multiple GR for one excise invoice, Single credit
    Multiple GR for one excise invoice, Multiple credit
    Maintain Excise Groups
    Use
    In this IMG activity, you define your excise groups. For each excise group, you can also control how various excise invoice transactions will work.
    Excise Groups
    In this activity, you define excise groups. An excise group allows you to maintain a separate set of excise registers and excise accounts. The RG 23A, RG 23C and PLA serial numbers are created for an excise group.
    Recommendation
    Under normal circumstances, excise authorities require every business to maintain only one set of excise registers and one set of accounts. But through exemption from the authorities, multiple books can be maintained.
    If your company has only one set of excise registers, then you need to maintain only one excise group.
    Activities
    1. Create one excise group for each set of registers that you need to keep.
    1. Assign the excise groups to plants.
    2. Maintain whether this Excise group is for a depot or not.
    3. If you receive only one consignment for an Excise challan then you can leave GR's per EI as blank. If you receive multiple GR's for a given Excise challan and would like to avail multiple credit mark the GRs per EI as 'Multiple GR's for one excise invoice, multiple credit'. Alternatively if you want to availa the credit only after all the goods receipts have been made mark it as ' Multiple GR for one excise invoice, single credit'.
    4. If you want to automatically create Excise invoice during Sales cycle at the time of billing the tick the indicator 'Create EI'
    5. During depot sales if you do not want to do RG23D selection and posting separately and would like to complete RG23D selection in one step mark the indicator 'RG23D Auto post'. This will post the selected records into RG23D automatically. You cannot cancel the selection later.
    6. If the indicator 'Default GR qty' is marked system will default the Excise challan quantity on to the Goods receipt if the Excise invoice number is given in the pop-up.
    7. If the indicator 'Folio no create' is marked system will generate Folio numbers for RG23D during receipt of excise invoice into depot.
    8. 'Automatic posting' when ticked will post the Excise invoice other movements automatically along with creation in single step.
    9. 'Create Part1 for Block Stock' when marked will create a Part1 during the receipt of material into Blocked stock .
    10. 'Create Part1 for STO' when marked will create a Part1 during the receipt of material through inter plant transfers.
    11. 'Create Part1 for consumption stock' when marked will create a Part1 during the receipt of material into consumption stock.
    • Excise Group
    Governs which set of excise registers a business transaction will be included in.
    Following is the relation between excise group, plant and registration.
    Dependencies
    In define excise groups in Customizing.
    Then, in transactions involving excise duty, for example, when you post a vendor's excise invoice, you specify which excise group you are using. This information tells the system which G/L accounts to post the excise to.
    At the end of the period, when you come to prepare your excise registers, you create different sets for each excise group.
    Indicates that the plant in question is a depot.
    Dependencies
    Depots are required to prepare register RG 23D, and follow different procedures for goods receipt and invoice generation.
    GR Per Excise Invoice
    Multiple GR for one excise invoice , Multiple credit
    Multiple GR for one excise invoice , Single Credit
    Create Excise Invoice Automatically
    Instructs the system to automatically create a Sales and Distribution (SD) excise invoice immediately you create a commercial invoice or a pro forma invoice.
    The excise invoice is created in the background.
    If you want to make use of this function, you must also define the default plant, excise group, and series groups in Customizing for Sales and Distribution (SD), by choosing Excise Group - Series Group Determination.
    RG23D Sales Creation and posting option
    RG23D Automatic Option if selected will create Depot excise invoice by posting the selection of excise invoices in single step.
    If this is not selected then you need to separately do RG23D selection followed by PGI and then RG23D verification and posting.
    If you need automatic posting of RG23D selection then the Post Goods Issue should have been completed before running RG23D selection.
    Default excise qty in GR
    If this indicator is ticked then while doing Goods Receipt using 'MB01' system will default the excise invoice quantity on to the Goods receipt document.
    Folio number for depo
    Posting
    If this indicator is marked then while creating Excise invoice for other movements system automatically does the Verify and Post. You need not separately Post the excise invoice
    Also we can set indicator for creation of part 1 for:
    Blocked stock
    Stock transport order
    Consignment stock
    Maintain Series Groups
    Use
    In this IMG activity, you define the different excise series groups within your company. Series groups allow you to maintain multiple number ranges for the outgoing excise documents.
    Based on excise regulations and exemptions from the authorities you can maintain multiple number series for outgoing documents. But each of these series has to be declared to the excise authorities.
    Activities
    1. Define excise series groups based on type of outgoing document
    2. Assign series group to excise registration ID
    3. If no financial postings are required for an Excise invoice in this seris group then you tick the 'No utilization' indicator.
    4. If the CENVAT has to be paid immediately and you need not wait for the Fort nightly payment then mark the 'Immediate Utilization' indicator.
    Example
    You could define two series groups, group 001 for excise invoices, and group 002 for 57 F4 documents.
    No account postings for CENVAT in sales cycle
    No utilization Flag
    If you do not need any CENVAT utilization for an excise invoice but would like to just generate an excise invoice then you need to mark this indicator.
    IF the flag is checked then system will create an Excise invoice in the given Series group but there will not be any account postings or Part2 postings.
    Immediate Utilization of CENVAT
    Specifies that when you create an excise invoice, the system immediately pays the amount from CENVAT and creates the Part II entry. Such invoices will not be listed for fortnightly utilization.
    If you have both fortnightly and immediate utilization for the same excise group, the account determination within CIN IMG should point to the ED interim account.
    Account determination for immediate payment will be done exactly the same as being done for fortnightly utilization program.
    Maintain Excise Duty Indicators
    Use
    In this IMG activity, you maintain the excise duty indicators.
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
    Select Tax Calculation Procedure
    In this IMG activity, you specify which tax procedure you want to use for determining excise duties and sales taxes on input materials in India.
    1. If you use condition-based excise determination, use a copy of the tax procedure TAXINN.
    2. If you use formula-based excise determination, use a copy of the tax procedure TAXINJ.
    This tax procedure also supports condition-based excise determination, so that you can work with both concurrently.
    We strongly recommend that new customers use condition-based excise determination. Note that once you have started using a tax procedure, you cannot switch to another one, otherwise you will not be able to display old documents.
    Maintain Excise Defaults
    Use
    In this IMG activity, you define which tax procedure and pricing condition types are used in calculating excise taxes using formula-based excise determination.
    Activities
    If you use condition-based excise determination, fill out the CVD cond. field and leave all the others blank.
    If you use formula-based excise determination, fill out all of the fields as follows:
    1. Enter the tax procedure and the pricing conditions that are relevant for excise tax processing.
    2. Specify the purchasing and sales conditions types used for basic excise duty, additional excise duty, special excise duty, and cess.
    3. Specify the conditions in the sales order that are used for excise rates.
    4. Specify the countervailing duty condition type used for import purchase orders.
    See also
    SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management (MM) -> Condition-Based Excise Determination and -> Formula-Based Excise Determination.
    IMG > Logistics - General > Tax On Goods Movement > India > Basic Settings > Determination of Excise Duty >
    Condition-Based Excise Determination
    Use
    When you enter a purchasing document, for example, a purchase order, the R/3 System automatically calculates the applicable excise duties using the condition technique.
    Features
    The standard system comes with two tax calculation procedures. TAXINN is only supports condition-based excise determination, whereas TAXINJ supports condition-based excise determination and formula-based excise determination. Both tax procedures contain condition types that cover all of the excise duties and sales taxes applicable.
    Since the exact rates of excise duty can vary on a large number of factors, such as which vendor you purchase a material from, or which chapter ID the vendor stocks the material under, you create condition records for every sort of excise duty.
    When you come to enter a purchasing document, the system applies the excise duty at the rates you have entered in the condition records.
    Activities
    Customizing
    Make the settings in Customizing Basic? India?for Logistics - General, by choosing Taxes on Goods Movements Account? Excise Duties Using Condition Technique and ...?Settings Determination.
    These activities include one activity where you define a tax code for condition-based excise determination.
    Master Data
    Create condition records for all excise duties that apply, and enter the tax code for condition-based excise determination in each.
    Day-to-Day Activities
    When you enter a purchase order or other purchasing document, enter the tax code for condition-based excise determination in each line item. The system then calculates the excise duties using the condition records you have created.
    When the ordered materials arrive, you post the goods receipt and the excise invoice. The system posts the excise duty to the appropriate accounts for deductible input taxes when you enter the excise invoice.
    Creating Condition Records for Excise Duty
    1. In the command field, enter FV11 and choose .
    2. Enter the condition type that you want to create a condition record for and choose .
    The Key Combination dialog box appears.
    3. Select the combination of objects that you want to create the condition record for.
    On the dialog box, Control Code means "chapter ID."
    So, for example, to create a condition record for a tax that applies to a combination of country, plant, and chapter ID, select Country/Plant/Control Code.
    4. Choose .
    5. Enter data as required.
    In the Tax Code field, enter the dummy tax code that you have defined.
    6. Save the condition record.
    Formula-Based Excise Determination
    Use
    When you execute a business transaction involving materials that are subject to excise duty, the system automatically calculates the duty for you.
    Prerequisites
    In order for the system to be able to determine which rate of excise duty to apply, you must have maintained all the data on the Excise Rate Maintenance screen, which you can Master Data?access from the SAP Easy Access screen by choosing Indirect Taxes Excise Rate Maintenance.?
    You maintain the following types of data:
    1. Plant master data
    You assign each of your plants an excise duty indicator. You can use the same indicator for all the plants with the same excise status from a legal point of view, such as all those that are in an exempt zone.
    See also the information about manufacturers that are only entitled to deduct a certain portion of the duty (see Partial CENVAT Credit).
    2. Vendor master data
    For each of your vendors with the same excise status from a legal perspective, you define an excise duty indicator. You must also specify the vendor type - for example, whether the vendor is a manufacturer, a depot, or a first-stage dealer. You must also stipulate if the vendor qualifies as a small-scale industry.
    For each permutation of plant indicator and vendor indicator, you then create a final excise duty indicator.
    3. Customer master data
    Similarly, you assign the same excise duty indicator to each of your customers that share the same legal excise status.
    Again, for each permutation of plant indicator and customer indicator, you then create a final excise duty indicator.
    4. Material master data
    Each material is assigned a chapter ID.
    5. Excise tax rate
    For every chapter ID and final excise duty indicator, you maintain the rate of excise duty.
    If your business only qualifies for partial CENVAT credit, you must customize your system accordingly.
    Activities
    Let us consider an example to illustrate how the system determines which rate of excise duty to apply to a material. Assume you are posting a sale of ball bearings to a customer. The system automatically determines the rate of excise duty as follows:
    1. Looks up the customer master data to see what status you have assigned the customer.
    Let's assume you've assigned the customer status 3.
    2. Looks up the plant master data to see what status you have assigned the plant.
    Similarly, your plant has status 2.
    3. The system looks up the table under Excise Indicator for Plant and Customer to see what the final excise duty indictor is for customer status 3 and plant status 2: It is 7.
    4. The system determines the chapter ID of the ball bearing for the plant.
    Let's assume the chapter ID at plant for the ball bearings is 1000.01.
    5. Finally, the system looks up the table under Excise Tax Rate to see what rate of duty applies to chapter ID 1000.01 under status 7.
    Define Tax Code for Purchasing Documents
    In this IMG activity, you define a tax code for the purposes of calculating excise duty when you enter purchasing documents.
    Only carry out this activity if you use condition-based excise determination.
    Activities: Create a new tax code, and set the tax code type to V (input tax). Do not make any other settings for it.
    Assign Tax Code to Company Codes
    Use
    In this IMG activity, assign the tax code for purchasing documents to the company codes where it will be used.
    Only carry out this activity if you use condition-based excise determination.
    Classify Condition Types
    In this IMG activity, you specify which condition types you use for which sort of tax. Note that this only applies to condition types that you use with the new excise determination method.
    The system uses this information when you create a document from another one. For example, when you enter an incoming excise invoice from a purchase order, or when you create an outgoing excise invoice from a sales order, the system determines the various excise duties in the excise invoice using the information that you have entered here.
    In addition, when you create a purchasing document, the system only uses the condition types that you enter here.
    1. For taxes on purchases, use the condition types contained in the tax procedure.
    2. For taxes on sales, use the condition types contained in the pricing procedures.
    Standard settings
    The standard system comes with sample settings for the tax calculation procedures and pricing procedures.
    Use these settings as a basis for your own.
    IMG > Logistics - General > Tax On Goods Movement > India > Account Determination
    Define G/L Accounts for Taxes
    In this IMG activity, you specify which G/L accounts you will use to record which taxes. You have set up G/L accounts for each of the processing keys listed below.
    Assign an account to each of the following posting keys. The accounts for VS1, VS2, and VS3 are used as clearing accounts during excise invoice verification.
    1. VS1 (basic excise duty)
    2. VS2 (additional excise duty)
    3. VS3 (special excise duty)
    4. VS5 (sales tax setoff)
    5. MWS (central sales tax)
    6. MW3 (local sales tax)
    7. ESA (service tax)
    8. ESE (service tax expense)
    Specify Excise Accounts per Excise Transaction
    In this IMG activity, you specify which excise accounts (for excise duty and CENVAT) are to be posted to for the various transaction types. Enter all the accounts that are affected by each transaction type.
    If you use subtransaction types, enter the accounts for each subtransaction type as well.
    Activities
    Transaction type UTLZ is used for determining accounts only while posting excise JVs and also if the payment of excise duty has to be done fortnightly.
    The fortnightly CENVAT payment utility picks up the credit side accounts from the transaction types of GRPO, EWPO, and TR6C for determining the CENVAT and PLA accounts. There is no separate transaction type for fortnightly payment.
    Example
    Excise TT DC ind Account name
    GRPO CR CENVAT clearing account
    GRPO CR RG 23 BED account
    GRPO DR CENVAT on hld account
    Specify G/L Accounts per Excise Transaction
    In this IMG activity, you assign the excise and CENVAT accounts to G/L accounts.
    When you come to execute the various transactions, the system determines which G/L accounts to post to by looking at the:
    1. Excise group
    2. Company code
    3. Chart of accounts
    Furthermore, if you want separate account determination settings within an excise group, you can also use sub transaction types.
    Requirements
    You have already:
    1. Defined the G/L accounts
    2. Defined the excise groups
    3. Maintained the transaction accounts
    Activities
    For each excise group, assign the excise and CENVAT accounts to G/L accounts. For most businesses, one set of accounts will suffice for alltransactions.
    Note
    You need not remit the CENVAT to the excise department immediately, so maintain the credit account for transaction type DLFC as an excise duty interim account. This will be set off when you remit the duty.
    Config setting needed to be done in order to get the Excise Details Screen in Material Master.
    Even though this functionality is available in enterprise version, a small config step has to be made in Screen Sequences for Material Master.
    Following document helps you to do this configuration.
    ? Material Master ? Logistics General ?1. Go to IMG Define Structure of Data Screen for each?Configuring the Material master Screen Sequence.
    2. Select your screen sequence. Usually it would be 21. Select the same and click on Data Screen in the left frame.
    3. Once the data screens are exhibited, select data screen no. 15, ie. SSq. 21and Scrn 15, which is "Foreign Trade: Import Data". Select the same and click on Subscreens in the left frame.
    4. Go to the last sub screen i.e. 21-15-6 - SAPLMGD1- 0001 and select the same. Click on tab view subscreen and ensure that the subscreen is blank.
    5. Now in the last sub screen i.e. no.6 you delete SAPLMGD1 - 0001 and instead add SAPLJ1I_MATERIAL_MASTER and in the screen no. 2205.
    6. Save the setting.
    7. Create a Material Master and check whether in Screen Foreign Trade - Import, Excise related subscreen appears.
    Reward points if helpful,
    Rewards,
    Archit

  • Pricing procedure(Condition technique)

    Hi All
    Can someone provide me all the configuration steps in pricing procedure in MM...

    Select the pricing procedure which is the standard and copy it and create our own pricing procedure.
    Highlight it and double click the Control icon in the LHS screen.
    We can see that there are 16 columns in the pricing procedure, these are going to be used by the system to control the condition types.
    The detail description of each column is given below.
    Step:
    Number that determines the sequence of the conditions with in a procedure.
    It indicates the position of the condition type in pricing procedure.
    Ex.: 10, 15 etc.
    Counter:
    System uses the counter to count the steps and also it can be used to count mini steps of same condition types. So that number of steps can be reduced in the pricing procedure and hence enhancing the system performance.
    Access number of the conditions with in a step in the pricing procedure.
    During automatic pricing, the system takes into account the sequence specified by the counter.
    Condition Type:
    It represents pricing element in pricing procedure as a base price, discount, freight and tax.
    The condition type is used for different functions. In pricing, for example, the condition type lets you differentiate between different kinds of discount; in output determination, between different output types such as order confirmation or delivery note; in batch determination, between different strategy types.
    Ex.: PR00 - Price
    K004 - Material Discount
    K005 - Customer/Material Discount
    K007 - Customer Discount.
    Description:
    System copies description of condition type from its description (V/06).
    From and To:
    1.From: This can be used as a base to the condition type for calculating further value.
    1.{+}From and To: + The range between the steps from and to can be used to specify the range between same condition types. So that depending upon the condition type, the system deducts or adds the total value of those condition types from specific common source.
    Manual:
    This indicator specifies whether the specific condition type can be determined manually during sales order processing.
    If we check the box then the entry is going to be manual, if we uncheck it, it is going to be automatic.
    For Base Price and Taxes, the entry should be automatic.
    For Discounts and Freights, The entry should be manual.
    If we check the box, in VA01 when we go to conditions at the header/item level, the condition type will not be listed. If we require we will have to manually enter it.
    If we un-check the box, in VA01 when we go to conditions at the header/item level, the condition type will be listed.
    Mandatory:
    This indicator specifies that particular condition type is mandatory in the pricing procedure.
    If we check the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will not allow us to do it and throws an error.
    If we uncheck the box, then in VA01 at the header/item level in the conditions tab, if we delete the value in the condition type and try to save the document then system will allow us to save it, without giving any error.
    Mandatory check box should be checked in condition types which are compulsorily required in pricing procedure. Ex.: PR00, MWST.
    If the condition type is checked with mandatory option, then value should be maintained for that condition type, otherwise the system will not allow the user to process the document.
    Statistical:
    This indicator if it is activated will not allow the value of the condition type to be taken into net value calculation.
    It is used only for information purposes only.
    This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value).
    This is commonly used for condition types
    SKTO - Cash Discount
    VPRS - Cost (Moving average price/Standard Price).
    Print:
    The value of this field specifies whether line item can be printed or not in the sales document and at what level it is to be printed.
    Subtotal:
    The value of this field determines where the values of subtotals to be captured i.e. in which table and which field.
    Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored.
    If the same fields are used to store different condition amounts, the system totals the individual amounts.
    These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order.
    Requirement:
    It is a routine that is written by an ABAP consultant according to the business requirement.
    By defining Requirement in condition technique we can restrict the access of condition type.
    To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
    For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
    This Requirement will ensure that these condition types will appear only during the billing document processing.
    If new Requirements are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Requirements" in the top menu and then click on "pricing".
    We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
    And we assign the application type like V - Sales/Distribution etc.
    AltCty - Condition formula for alternative calculation type:
    It is again a Routine that is written by ABAP Consultant.
    It is an alternative formula for the condition type that can be used instead of standard formulas.
    For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
    Ex.: 950 0 Profit Margin 11.
    So we assign 11 - Profit Margin.
    If new routines are to be defined we follow the procedure given below.
    Go to T.Code: VOFM. - Maintain Requirements & Formulas
    Click on the "Formulas" and then on the "Condition Values".
    We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
    And we assign the application type.
    AltCBV - Alternative formula for condition base value:
    Formula for determining the condition basis as an alternative to the standard.
    It is again a Routine that is written by ABAP Consultant.
    It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
    Ex.: Freight - KF00.
    Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
    In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
    During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
    Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
    AcyKy - Account Key/ Accrls - Accruals:
    The values of the Sales Revenues, Sales Deductions, Freight Revenues, Tax Revenues, and Rebate Accruals etc. are going to be posted in the respective G/L accounts in Fi Module.
    In order to do this we assign account keys/ accruals to the different condition types based on their classification. The classification shown below.
    ERB Rebate sales deduct.
    ERF Freight revenue
    ERL Revenue
    ERS Sales deductions
    ERU Rebate accruals
    For Ex.,
    For all Price condition types like PR00 etc. we assign ERL - Revenue.
    For all Discount condition types like K004, K005 etc. we assign ERS - Sales Deductions.
    For all Freight condition types KF00 etc. we assign ERF - Freight Revenues.
    For all Rebates condition types BO01 to BO05 we assign in Account key ERB - Rebates Sales deductions and for Accruals ERU - Rebate Accruals.
    This account keys and accruals are in turn assigned to respective G/L accounts. So the system posts respective values in respective G/L accounts in Fi-Co Module.
    This also one of the areas of SD - Fi Integration. SD consultants assign the account keys and Fi Consultants assign the respective G/L accounts in T.Code:VKOA.
    or
    Hi,
    Pricing Procedure in MM
    The steps are:
    SPRO->MM->Purchasing->Conditions->Define Price dertermination process
    1. Define Condition Table:
    2.Define Acces Sequence,
    3.Define Condition Type,
    4.Define Claculatin Schema,
    5.Assign Calulation Schema,Acces Sequence and Condition Type,
    6.Define Schema Group Of Vendor,
    7. Define Schema Group Of Purchasing Organisation,
    8.Assign Schema Group Of Vendor to Purchasing Organisation,
    9.Assignment of Schema Group Of Vendor ,Schema Group Purchasing Organisation and Calculation Schema.
    10.Assign Vendor to Schema Group Of Vendor (XK02)
    11.Maintain Condition record(MEK1)
    Edited by: MANI ROOPA SD/MM on Apr 17, 2008 8:44 AM

  • Download Pricing Procedure into XL or RTF file.

    Hi all
    Can anyone please explain how to use table T683S to download the pricing procedure.I mean please elaborate the path / Tx Code a little.Same thread was solved by Sachin Nagpal today, but a little explanation is needed.
    thanx well in advance
    regards
    vikas chhabra

    Hi vikas chhabra,
    for your requirement follow me:
    1). use t.code v/08, select your pricing procedure and select the control
    2). go to Table View  shift+F1 (select the Print Option)
    3).then u can able to see the pricing procedure ,
    4). and find the icon spread sheet (CTRLSHIFTF7)
    5).and select the table option and select the microsoft excel
    6). then save it as loval file on your desktop
    Hope this Helps, if it is pls REWARD ME
    Thanks&Regards
    Venkat.Dhanemkula

  • Download pricing procedure into excel file or Rtf file ?? urgent pls

    Hi All,
    How can I download pricing procedure into local disk.
    Thanks
    Venkat
    Message was edited by:
            venkat Kumbham

    Hi venkat Kumbham , 
    for your requirement follow me:
    1). use t.code v/08, select your pricing procedure and select the control
    2). go to Table View shift+F1 (select the Print Option)
    3).then u can able to see the pricing procedure ,
    4). and find the icon spread sheet (CTRLSHIFTF7)
    5).and select the table option and select the microsoft excel
    6). then save it as loval file on your desktop
    Hope this Helps, if it is pls REWARD ME
    Thanks&Regards
    Venkat.Dhanemkula

  • Problem with new pricing procedure - free of cost

    i set up a new pricing procedure where i have zsed (special excise duty) and zmws (sales tax) set as manual, it's not valid on some free sample orders. but when i goto create order it does not show up under conditions, even though i've maintained it for that material in vk11. and when i click on condition type in conditions, it doesn't show up in the drop down either (at the order level). if i just type zsed it says zsed cannot be processed manually.
    but if i change the pricing procedure and take off the manual check mark, the tax shows up on the same order automatically (from vk11) but i can't delete it there.
    suggestions? i need for it to show up or have an option where if it shows up i can delete it. thanks!

    fyi,
    If you set the "Manual" indicator in pricing procedure against to any condition type, then you can enter this condition type value in particular transaction. ( But for this condition type details, " changes can be made- setting maintain as "D" not possible to process manuall). Same "manual" logic in the pricing procedure will not work.
                  Because controls in Condition type has priority than anyother.
    Now coming to your question,
               If I understood it properly,
    ZSED is not applicable to every free of cost order, but it may be applicable to other orders ( excl: FOC orders). Expecting ZSED Condition type maintained in both pricing procedures ( FOC sales pricing procedure & non FOC sales procedure).
    if you set the " Manual entries has priority"/ tick mark delete check box in ZSED, then it will allow to enter manually/delete the condition type in FOC order as well as non FOC orders too.
    Then there could be chance that user may delete/manually enter ZSED in non FOC sales.
    better way would be, create new conditiont table by including Sales document type ( assume you created new document type for FOC sales) with other required fields ( eg: customer/material etc..,).
    assign this condition table in top of all the accesses in ZSED's access sequence.
    Maintain Condition record.
    By doing so, Condition record is applicable only to FOC doc type sales- if maintained , else it will search next condition record.
    which will not effect the non FOC sales & user cant delete ZSED from non FOC sales.
    Hope it helps

Maybe you are looking for

  • Display error message in ALV grid  using OOPS

    Hi, I have a requirement to display report in ALV. I have created ALV grid using OOPS with three editable cells and 1 button on toolbar. When user enter values in Ediatble cell  and click on the Toolbar button, sales order item should be assigned to

  • Problem in new 8.1 update

    Hello! I get a update of 8.1 for my Lumia 520. I did settings >application >store> download update only via WiFi... After that I give a update to apps it showing ready to download over WiFi.. I connected my phone wth high speed WiFi it was downloadin

  • Regarding idoc adapter

    hi experts, Is Synchronous IDOC possible,how.we have to configure? Regards, tahir

  • Report script to have attributes

    Hi, I am developing a report script to extract the base dimension members as well as some of the attributes in the columns, followed by the last data column. I have the product dimension with 2 attributes (Brand and Origin). However, when I put all t

  • Why is my safari deal slow?

    Why has my safari suddenly slowed down.  I cannot even type anything without having to wait for a long time.