Diff, bet general SD pricing procedures and Internet Pricing procedure

Hi,
  Will any one give clear picture about the diff, between SAP SD pricing procedure and Internet Pricing Procedure? and what are the areas it differs?. If you mail me any URL / Doc regarding Internet Pricing Procedure  Configuration that will be of great help.
   [email protected]

I hope by internet pricing procedure you mean pricing procedure used in Internet Sales / CRM Online.
Basically, there are no differences. Structure is same. The way pricing procedure is defined & used is same. The only different I would say is, the way you write code for formula & requirements. Usability-wise, they both are same.
Hope it helps.
Regards,
Kaushal

Similar Messages

  • How can I deactivate the pricing date and material pricing group in VA01?

    Hello All,
    How can I deactivate (output only) the pricing date and material pricing group field in VA01/2, VA21/2, and VA41/2? What user exit can I use? Thanks in advance...
    PeeJay

    You can use the t.code SHD0, choose your transaction variant here, further choose your screen variant.
    Next select your screen variant and in the Menu bar select Variant> change with processing>Make repairs in foreign namespaces only if they are urgent> Continue(Enter)>again 'enter'>Object can only be created in SAP package>continue(enter)> Exit and save >This variant contains other screens, adopt these as well?>enter>enter>  scroll down to the entry 'pricing date' or VBKD-PRSDT make the necessary changes and save.
    The system will prompt to assign a package and request enter the necessary values.
    Your issue is sorted!!
    Regards,
    PATHIK

  • Difference between Sampling Procedure and Sample-drawing procedure

    Friends,
    I am new to QM and started learning QM Module. My doubt is what is the difference between Sampling Procedure and Sample-drawing procedure?
    The reason for my doubt is, we can determine the sample quantity with Sampling procedure itself. then what is the need of sample-drawing procedure?
    Also describe primary, pooled and reserved samples.
    Regards,
    IMIMINT

    Hi,
    Sampling Procedure 
    Definition
    A procedure that contains the rules for determining the sample size for an inspection. The sampling procedure also specifies the type of valuation to use for results recording (attributive, variable, or manual).
    Use
    You assign a sampling procedure to each characteristic in an inspection plan to calculate the sample size.
    Sample-Drawing Procedure 
    Definition
    A master data object in which you plan the drawing of physical samples. In the sample-drawing procedure, you specify:
    Which categories of physical samples must be drawn
    How many physical samples must drawn
    The size of each physical sample
    Whether the drawing of physical samples must be confirmed
    Use
    The system uses the information in the sample-drawing procedure together with the information in the inspection plan to calculate the physical sample sizes, and to create physical-sample records when an inspection lot is created.
    Primary Sample : It is the sample drawn from the lot directly.
    Pooled Sample : It is the sample whcih is combination of 2 or more primary samples.i.e. primary sample sfrom say 3 differetn drums is mixed and tested.
    Reserved Sample :sample which is preserved for the testing in future.
    or in other words
    Primary samples (1st stage)
    Physical samples drawn directly from a material or batch that will be inspected or used to create pooled samples.
    Pooled samples (2nd stage)
    Physical samples to be created by mixing the contents of two or more primary samples from the same material or batch.
    Reserve samples
    Primary physical samples drawn from a material or batch reserved for future inspection.
    Vishal
    Edited by: VISHAL JONNALWAR on Feb 4, 2010 6:43 AM

  • JoinFieldValue between Special Pricing Request and Special Pricing Product

    Hi,
    Can anyone please let me know if I want to Copy the Value of a Field in Special Pricing Product to a field in Special Pricing Request, is it possible? Does Join Field Value works between Special Pricing Requests and Special Pricing Products?
    Example: In the Special Pricing Product, the External ID field is populated with the Value: AAPA-5WZD64 I want to copy this value to the External ID field in Special Pricing Request. Can this be done in any way, apart from web services?
    Thanks

    Hi Bob,
    I have seen the thread.
    Even though the SPR (Special Pricing Request) and SPP (Special Pricing Product) are the PRM Objects, in my case, the vanilla Object Partner is of least significance, in terms of the existance of a JoinFieldValue function between SPR and SPP.
    Since this is not in the help file and also in Metalink/MOS, Can you please let me know if there is any way by which I can copy the value of a Field (External ID) in SPP to a corresponding Field (External ID) in SPR.
    Thanks.

  • Tax Procedures and MM pricing procedures

    Currently when creating a PO under the invoice tab you can input the Tax code and jurisdiction code.
    The tax code I am using is set up for a Canadian Tax procedure (TAXCAJ).
    The procedure is calling two tax condition types JC1E (GST) and JC1I (PST). They are both condition class D and they are the same accross other statistics but they differ in condition category. JC1E is condition category 1 and JC1I is condition category 2.
    JCIE uses account determination VST while JC1I uses NVV. JC1E needs to be posted to a seperate account as it is partially recoverable.
    The real underlying issue here is that tax condition type JC1I comes accross to teh MM condition tab under NAVS but JC1E does not. I need the value from JC1E to come over to the conditions tab as my PO print is driven by this.
    Any ideas how to get tax condition type JC1E (or its value) over to the conditions tab. I can make JC1E come over with JC1I but i need JC1E seperate. If you need clarification or more information just let me know.

    Hi,
    NAVS condition collects the non-deductible portion of the Tax Code and hence only showing JC1I which is a non-deductible condition type.  The logic behind this is non-deductible tax is part of cost, so for updating the stock account at the time of GR with base value + discounts and other pricing conditions + non-deductible tax, NAVS condition type is being used in PO pricing procedure.  JC1E is a deductible type tax and as not being a part of cost it is not updated in NAVS and hence the stock account at the time of GR.
    If you want all the tax amounts for PO printing purpose, use JEXS condition type and insert this at the last of the pricing procedure with statistical indicator.  Modify your print program to print value against JEXS instead of NAVS.
    regards,
    mallik

  • Number of procedures and linie in procedures.

    Hi,
    I have to know how many procedures and functions are in my database. Furthermore, how many lines they have together. Is that possible from Oracle system's views?
    Thanks for help.

    select owner, name, type, count(*) from all_source group by owner, name, type;
    user_source if you want to restrict to source owned by the schema.
    all_arguments/user_arguments if you want to see public procedures/functions and their arguments.

  • Support a singly report on SQL Stored Procedure and Oracle Stored Procedure

    Hi,
    I have a requirement in which I need to create a report that will run both on oracle and sql server.
    Report is designed as follows.
    Main report contain 2 sub-reports.Sub-reports are  based on stored procedure that takes three input parameters(beginDate,endDate and hostname which is a comma-separated string).
    Main report also have three parameters (beginDate,endDate and hostnameList) that I am linking with both sub-reports.
    Since the crystal picks the same name of the parameter as we define in procedure it showing '@' symbol in all the parameters when I change the datasoure from oracle to sql server and that's why sub reports defined in main report loose all the linking and same happens when I switch from sql to oracle since in case of oracle it does not have '@' symbol in variable name.
    How can I have one report that work with both DBs without loosing the links.
    Any help will be appreciated.
    Thanks,
    Amrita

    There is no way of doing this in CR. At least not that I've ever heard of anyway.
    If you REALLY need to make this work and it REALLY has to be just 1 report... Here is what I'd do...
    In the SQL Server database, add a new table that contains the same columns that are being returned by the sp's. If you can't add new tables to the database, use a different database or server...
    Create a Linked Server linking the Oracle db to SQL Server. (If you take the 3rd server rout, do the same with the SQL Server)
    Write a new sp that will accept the {?WhichServer} parameter and populate the new table with the result set.
    Then just query that table for your report.
    I know this probably isn't the rout you were wanting to take but it should work...
    Jason

  • 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

  • Relation between Tax procedure and Pricing procedure

    Dear All,
    I would like to get more clarity on Tax procedure, Pricing procedure.
    a) Why do we have Tax procedure and assigned to Country?
    b) If the tax procedure has been created and assigned to Country-IN (in FI module), then why do we need to create pricing procedure with same condition type for purchasing in MM module?  We are even creating lot of pricing procedure for Sales in SD module.
    Regards
    Manivannan R

    Hi
    Tax
    During SD document transactions, tax calculation procedure TAXUSX is only relevant to determine the tax liability accounts for output sales tax. Notice that in pricing procedure RVAXUS, the condition types XR1 - XR6 carry the tax rates and tax amounts - resulted from the external tax system calculation - which is posted to tax G/L accounts. However, the tax accounts are not specified in the pricing procedure but rather in the tax calculation procedure.
    Tax codes are the link between pricing procedure and tax calculation procedure.
    Pricing
    The primary job of a pricing procedure is to define a group of condition types in a particular sequence. The pricing procedure also determines:
    Which sub-totals appear during pricing
    To what extent pricing can be processed manually
    Which method the system uses to calculate percentage discounts and surcharges
    Which requirements for a particular condition type must be fulfilled before the system takes the condition into account
    Example
    Example of a Pricing Procedure
    If a sales department processes sales orders for a variety of foreign customers, the department can group the customers by country or region. A pricing procedure can then be defined for each group of customers. Each procedure can include condition types that determine, for example, country-specific taxes. In sales order processing, you can specify pricing procedures for specific customers and for sales document types. The system automatically determines which procedure to use.
    Pricing Procedures in the R/3 System
    The standard system contains pre-defined pricing procedures, which contain frequently used condition types along with their corresponding access sequences. You can, of course, modify these procedures or create your own from scratch.
    Creating and Maintaining Pricing Procedures
    You create or maintain pricing procedures in Customizing for Sales. For more information on creating pricing procedures, see the online Implementation Guide for Sales and Distribution.
    To reach the pricing procedure screen from SD Customizing:
       1. Choose Basic Functions
       2. ® Pricing ® Pricing control ® Define and assign pricing procedures.Select the transaction that you want to execute.

  • Diff bet BDC in appln & present

    Gud morning guys,
    hav a gr8 day
    Coul any1 of  u tel me diff bet BDC in application layer and presentation layer...
    cheers
    sakthi

    Hi
    Hope it will help you.
    Reward if help.
    BATCH DATA COMMUNICATION
    About Data Transfer In R/3 System
    When a company decides to implement the SAP R/3 to manage business-critical data, it usually does not start from a no-data situation. Normally, a SAP R/3 project comes into replace or complement existing application.
    In the process of replacing current applications and transferring application data, two situations might occur:
    • The first is when application data to be replaced is transferred at once, and only once.
    • The second situation is to transfer data periodically from external systems to SAP and vice versa.
    • There is a period of time when information has to be transferred from existing application, to SAP R/3, and often this process will be repetitive.
    The SAP system offers two primary methods for transferring data into SAP systems. From non-SAP systems or legacy system. These two methods are collectively called “batch input” or “batch data communication”.
    1. SESSION METHOD
    2. CALL TRANSACTION
    3. DIRECT INPUT
    Advantages offered by BATCH INPUT method:
    1. Can process large data volumes in batch.
    2. Can be planned and submitted in the background.
    3. No manual interaction is required when data is transferred.
    4. Data integrity is maintained as whatever data is transferred to the table is through transaction. Hence batch input data is submitted to all the checks and validations.
    To implement one of the supported data transfers, you must often write the program that exports the data from your non-SAP system. This program, known as a “data transfer” program must map the data from the external system into the data structure required by the SAP batch input program.
    The batch input program must build all of the input to execute the SAP transaction.
    Two main steps are required:
    • To build an internal table containing every screen and every field to be filled in during the execution of an SAP transaction.
    • To pass the table to SAP for processing.
    Prerequisite for Data Transfer Program
    Writing a Data Transfer Program involves following prerequisites:
    Analyzing data from local file
    Analyzing transaction
    Analyzing transaction involves following steps:
    • The transaction code, if you do not already know it.
    • Which fields require input i.e., mandatory.
    • Which fields can you allow to default to standard values.
    • The names, types, and lengths of the fields that are used by a transaction.
    • Screen number and Name of module pool program behind a particular transaction.
    To analyze a transaction::
    • Start the transaction by menu or by entering the transaction code in the command box.
    (You can determine the transaction name by choosing System – Status.)
    • Step through the transaction, entering the data will be required for processing your batch input data.
    • On each screen, note the program name and screen (dynpro) number.
    (dynpro = dyn + pro. Dyn = screen, pro = number)
    • Display these by choosing System – Status. The relevant fields are Program (dynpro) and Dynpro number. If pop-up windows occur during execution, you can get the program name and screen number by pressing F1 on any field or button on the screen.
    The technical info pop-up shows not only the field information but also the program and screen.
    • For each field, check box, and radio button on each screen, press F1 (help) and then choose Technical Info.
    Note the following information:
    - The field name for batch input, which you’ll find in its own box.
    - The length and data type of the field. You can display this information by double clicking on the Data Element field.
    • Find out the identification code for each function (button or menu) that you must execute to process the batch-input data (or to go to new screen).
    Place the cursor on the button or menu entry while holding down the left mouse button. Then press F1.
    In the pop-up window that follows, choose Technical info and note the code that is shown in the Function field.
    You can also run any function that is assigned to a function key by way of the function key number. To display the list of available function keys, click on the right mouse button. Note the key number that is assigned to the functions you want to run.
    Once you have program name, screen number, field name (screen field name), you can start writing.
    DATA TRANSFER program.
    Declaring internal table
    First Integral Table similar to structure like local file.
    Declaring internal table like BDCDATA
    The data from internal table is not transferred directly to database table, it has to go through transaction. You need to pass data to particular screen and to particular screen-field. Data is passed to transaction in particular format, hence there is a need for batch input structure.
    The batch input structure stores the data that is to be entered into SAP system and the actions that are necessary to process the data. The batch input structure is used by all of the batch input methods. You can use the same structure for all types of batch input, regardless of whether you are creating a session in the batch input queue or using CALL TRANSACTION.
    This structure is BDCDATA, which can contain the batch input data for only a single run of a transaction. The typical processing loop in a program is as follows:
    • Create a BDCDATA structure
    • Write the structure out to a session or process it with CALL TRANSACTION USING; and then
    • Create a BDCDATA structure for the next transaction that is to be processed.
    Within a BDCDATA structure, organize the data of screens in a transaction. Each screen that is processed in the course of a transaction must be identified with a BDCDATA record. This record uses the Program, Dynpro, and Dynbegin fields of the structure.
    The screen identifier record is followed by a separate BDCDATA record for each value, to be entered into a field. These records use the FNAM and FVAL fields of the BDCDATA structure. Values to be entered in a field can be any of the following:
    • Data that is entered into screen fields.
    • Function codes that are entered into the command field. Such function codes execute functions in a transaction, such as Save or Enter.
    The BDCDATA structure contains the following fields:
    • PROGRAM: Name of module pool program associated with the screen. Set this field only for the first record for the screen.
    • DYNPRO: Screen Number. Set this field only in the first record for the screen.
    • DYNBEGIN: Indicates the first record for the screen. Set this field to X, only for the first record for the screen. (Reset to ‘ ‘ (blank) for all other records.)
    • FNAM: Field Name. The FNAM field is not case-sensitive.
    • FVAL: Value for the field named in FNAM. The FVAL field is case-sensitive. Values assigned to this field are always padded on the right, if they are less than 132 characters. Values must be in character format.
    Transferring data from local file to internal table
    Data is uploaded to internal table by UPLOAD of WS_UPLOAD function.
    Population of BDCDATA
    For each record of internal table, you need to populate Internal table, which is similar to BDCDATA structure.
    All these five initial steps are necessary for any type of BDC interface.
    DATA TRANSFER program can call SESSION METHOD or CALL TRANSACTION. The initial steps for both the methods are same.
    First step for both the methods is to upload the data to internal table. From Internal Table, the data is transferred to database table by two ways i.e., Session method and Call transaction.
    SESSION METHOD
    About Session method
    In this method you transfer data from internal table to database table through sessions.
    In this method, an ABAP/4 program reads the external data that is to be entered in the SAP System and stores the data in session. A session stores the actions that are required to enter your data using normal SAP transaction i.e., Data is transferred to session which in turn transfers data to database table.
    Session is intermediate step between internal table and database table. Data along with its action is stored in session i.e., data for screen fields, to which screen it is passed, the program name behind it, and how the next screen is processed.
    When the program has finished generating the session, you can run the session to execute the SAP transactions in it. You can either explicitly start and monitor a session or have the session run in the background processing system.
    Unless session is processed, the data is not transferred to database table.
    BDC_OPEN_GROUP
    You create the session through program by BDC_OPEN_GROUP function.
    Parameters to this function are:
    • User Name: User name
    • Group: Name of the session
    • Lock Date: The date on which you want to process the session.
    • Keep: This parameter is passed as ‘X’ when you want to retain session after
    processing it or ‘ ‘ to delete it after processing.
    BDC_INSERT
    This function creates the session & data is transferred to Session.
    Parameters to this function are:
    • Tcode: Transaction Name
    • Dynprotab: BDC Data
    BDC_CLOSE_GROUP
    This function closes the BDC Group. No Parameters.
    Some additional information for session processing
    When the session is generated using the KEEP option within the BDC_OPEN_GROUP, the system always keeps the sessions in the queue, whether it has been processed successfully or not.
    However, if the session is processed, you have to delete it manually. When session processing is completed successfully while KEEP option was not set, it will be removed automatically from the session queue. Log is not removed for that session.
    If the batch-input session is terminated with errors, then it appears in the list of INCORRECT session and it can be processed again. To correct incorrect session, you can analyze the session. The Analysis function allows to determine which screen and value has produced the error. If you find small errors in data, you can correct them interactively, otherwise you need to modify batch input program, which has generated the session or many times even the data file.
    CALL TRANSACTION
    About CALL TRANSACTION
    A technique similar to SESSION method, while batch input is a two-step procedure, Call Transaction does both steps online, one after the other. In this method, you call a transaction from your program by
    Call transaction <tcode> using <BDCTAB>
    Mode <A/N/E>
    Update <S/A>
    Messages into <MSGTAB>.
    Parameter – 1 is transaction code.
    Parameter – 2 is name of BDCTAB table.
    Parameter – 3 here you are specifying mode in which you execute transaction
    A is all screen mode. All the screen of transaction are displayed.
    N is no screen mode. No screen is displayed when you execute the transaction.
    E is error screen. Only those screens are displayed wherein you have error record.
    Parameter – 4 here you are specifying update type by which database table is updated.
    S is for Synchronous update in which if you change data of one table then all the related Tables gets updated. And sy-subrc is returned i.e., sy-subrc is returned for once and all.
    A is for Asynchronous update. When you change data of one table, the sy-subrc is returned. And then updating of other affected tables takes place. So if system fails to update other tables, still sy-subrc returned is 0 (i.e., when first table gets updated).
    Parameter – 5 when you update database table, operation is either successful or unsuccessful or operation is successful with some warning. These messages are stored in internal table, which you specify along with MESSAGE statement. This internal table should be declared like BDCMSGCOLL, a structure available in ABAP/4. It contains the following fields:
    1. Tcode: Transaction code
    2. Dyname: Batch point module name
    3. Dynumb: Batch input Dyn number
    4. Msgtyp: Batch input message type (A/E/W/I/S)
    5. Msgspra: Batch input Lang, id of message
    6. Msgid: Message id
    7. MsgvN: Message variables (N = 1 - 4)
    For each entry, which is updated in database, table message is available in BDCMSGCOLL. As BDCMSGCOLL is structure, you need to declare a internal table which can contain multiple records (unlike structure).
    Steps for CALL TRANSACTION method
    1. Internal table for the data (structure similar to your local file)
    2. BDCTAB like BDCDATA
    3. UPLOAD or WS_UPLOAD function to upload the data from local file to itab. (Considering file is local file)
    4. Loop at itab.
    Populate BDCTAB table.
    Call transaction <tcode> using <BDCTAB>
    Mode <A/N/E>
    Update <S/A>.
    Refresh BDCTAB.
    Endloop.
    (To populate BDCTAB, You need to transfer each and every field)
    The major differences between Session method and Call transaction are as follows:
    SESSION METHOD CALL TRANSACTION
    1. Data is not updated in database table unless Session is processed. Immediate updation in database table.
    2. No sy-subrc is returned. Sy-subrc is returned.
    3. Error log is created for error records. Errors need to be handled explicitly
    4. Updation in database table is always synchronous Updation in database table can be synchronous Or Asynchronous.
    Error Handling in CALL TRANSACTION
    When Session Method updates the records in database table, error records are stored in the log file. In Call transaction there is no such log file available and error record is lost unless handled. Usually you need to give report of all the error records i.e., records which are not inserted or updated in the database table. This can be done by the following method:
    Steps for the error handling in CALL TRANSACTION
    1. Internal table for the data (structure similar to your local file)
    2. BDCTAB like BDCDATA
    3. Internal table BDCMSG like BDCMSGCOLL
    4. Internal table similar to Ist internal table
    (Third and fourth steps are for error handling)
    5. UPLOAD or WS_UPLOAD function to upload the data from the local file to itab. (Considering file is local file)
    6. Loop at itab.
    Populate BDCTAB table.
    Call transaction <tr.code> using <Bdctab>
    Mode <A/N/E>
    Update <S/A>
    Messages <BDCMSG>.
    Perform check.
    Refresh BDCTAB.
    Endloop.
    7 Form check.
    IF sy-subrc <> 0. (Call transaction returns the sy-subrc if updating is not successful).
    Call function Format_message.
    (This function is called to store the message given by system and to display it along with record)
    Append itab2.
    Display the record and message.
    DIRECT INPUT
    About Direct Input
    In contrast to batch input, this technique does not create sessions, but stores the data directly. It does not simulate the online transaction. To enter the data into the corresponding database tables directly, the system calls a number of function modules that execute any necessary checks. In case of errors, the direct input technique provides a restart mechanism. However, to be able to activate the restart mechanism, direct input programs must be executed in the background only. Direct input checks the data thoroughly and then updates the database directly.
    You can start a Direct Input program in two ways;
    Start the program directly
    This is the quickest way to see if the program works with your flat file. This option is possible with all direct input programs. If the program ends abnormally, you will not have any logs telling you what has or has not been posted. To minimize the chance of this happening, always use the check file option for the first run with your flat file. This allows you to detect format errors before transfer.
    Starting the program via the DI administration transaction
    This transaction restarts the processing, if the data transfer program aborts. Since DI document are immediately posted into the SAP D/B, the restart option prevents the duplicate document posting that occurs during a program restart (i.e., without adjusting your flat file).
    Direct input is usually done for standard data like material master, FI accounting document, SD sales order and Classification for which SAP has provided standard programs.
    First time you work with the Direct Input administration program, you will need to do some preparation before you can transfer data:
    - Create variant
    - Define job
    - Start job
    - Restart job
    Common batch input errors
    - The batch input BDCDATA structure tries to assign values to fields which do not exist in the current transaction screen.
    - The screen in the BDCDATA structure does not match the right sequence, or an intermediate screen is missing.
    - On exceptional occasions, the logic flow of batch input session does not exactly match that of manual online processing. Testing the sessions online can discover by this.
    - The BDCDATA structure contains fields, which are longer than the actual definition.
    - Authorization problems.
    RECORDING A BATCH INPUT
    A B recording allows you to record a R/3 transaction and generate a program that contains all screens and field information in the required BDC-DATA format.
    You can either use SHDB transaction for recording or
    SYSTEM ? SERVICES ? BATCH INPUT ? EDIT
    And from here click recording.
    Enter name for the recording.
    (Dates are optional)
    Click recording.
    Enter transaction code.
    Enter.
    Click Save button.
    You finally come to a screen where, you have all the information for each screen including BDC_OKCODE.
    • Click Get Transaction.
    • Return to BI.
    • Click overview.
    • Position the cursor on the just recorded entry and click generate program.
    • Enter program name.
    • Click enter
    The program is generated for the particular transaction.
    BACKGROUND PROCESSING
    Need for Background processing
    When a large volume of data is involved, usually all batch inputs are done in background.
    The R/3 system includes functions that allow users to work non-interactively or offline. The background processing systems handle these functions.
    Non-interactively means that instead of executing the ABAP/4 programs and waiting for an answer, user can submit those programs for execution at a more convenient planned time.
    There are several reasons to submit programs for background execution.
    • The maximum time allowed for online execution should not exceed 300 seconds. User gets TIMEOUT error and an aborted transaction, if time for execution exceeds 300 seconds. To avoid these types of error, you can submit jobs for background processing.
    • You can use the system while your program is executing.
    This does not mean that interactive or online work is not useful. Both type of processing have their own purposes. Online work is the most common one entering business data, displaying information, printing small reports, managing the system and so on. Background jobs are mainly used for the following tasks; to process large amount of data, to execute periodic jobs without human intervention, to run program at a more convenient, planned time other than during normal working hours i.e., Nights or weekends.
    The transaction for background processing is SM36.
    Or
    Tools ? Administration ? Jobs ? Define jobs
    Or
    System ? services ? Jobs
    Components of the background jobs
    A job in Background processing is a series of steps that can be scheduled and step is a program for background processing.
    • Job name. Define the name of assigned to the job. It identifies the job. You can specify up to 32 characters for the name.
    • Job class. Indicates the type of background processing priority assigned to the job.
    The job class determines the priority of a job. The background system admits three types of job classes: A B & C, which correspond to job priority.
    • Job steps. Parameters to be passed for this screen are as follows:
    Program name.
    Variant if it is report program
    Start criteria for the job: Option available for this are as follows:
    Immediate - allows you to start a job immediately.
    Date/Time - allows you to start a job at a specific name.
    After job - you can start a job after a particular job.
    After event - allows you to start a job after a particular event.
    At operation mode - allows you to start a job when the system switches to a particular operation mode.
    Defining Background jobs
    It is two step process: Firstly, you define the job and then release it.
    When users define a job and save it, they are actually scheduling the report i.e., specifying the job components, the steps, the start time.
    When users schedule program for background processing, they are instructing the system to execute an ABAP/4 report or an external program in the background. Scheduled jobs are not executed until they are released. When jobs are released, they are sent for execution to the background processing system at the specified start time. Both scheduling and releasing of jobs require authorizations.
    HANDLING OF POP UP SCREEN IN BDC
    Many times in transaction pop up screen appears and for this screen you don’t pass any record but some indication to system telling it to proceed further. For example: The following screen
    To handle such screen, system has provided a variable called BDC_CURSOR. You pass this variable to BDCDATA and process the screen.
    Usually such screen appears in many transactions, in this case you are just passing information, that YES you want to save the information, that means YES should be clicked. So you are transferring this information to BDCDATA i.e., field name of YES which is usually SPOT_OPTION. Instead of BDC_OKCODE, you are passing BDC_CURSOR.
    BDC_CURSOR is also used to place cursor on particular field.
    AN EXAMPLE WITH SESSION METHOD
    Following program demonstrates how data is passed from flat file to SAP transaction and further to database table by using SESSION method.
    The transaction is TFBA (to change customer).
    A simple transaction where you are entering customer number on first screen and on next screen data is displayed for the particular customer number. Field, which we are changing here, are name and city. When you click on save, the changed record gets saved.
    Prerequisite to write this BDC interface as indicated earlier is:
    1. To find screen number
    2. To find screen field names, type of the field and length of the field.
    3. To find BDC_OKCODE for each screen
    4. Create flat file.
    Flat file can be created in your hard disk as follows:
    1 Vinod   Hyderabad
    2 Kavitha Secunderabad
    3 Kishore Hyderabad
    (Where 1st character field is Customer number, 2nd field is Customer name and 3rd field is City.)
    To transfer this data to database table SCUSTOM following interface can be used.
    REPORT DEMO1.
    Following internal table is to upload flat file.
    DATA: BEGIN OF ITAB OCCURS 0,
    ID(10),
    NAME(25),
    CITY(25),
    END OF ITAB.
    *Following internal table BDCDATA is to pass date from internal table to session.
    DATA: BDCTAB LIKE BDCDATA OCCURS 0 WITH HEADER LINE.
    Variables
    DATA: DATE1 LIKE SY-DATUM. DATE1 = SY-DATUM - 1. “ This is for Hold Date
    To upload flat file to internal table.
    CALL FUNCTION UPLOAD
    EXPORTING
    FILE NAME = ‘C:\FF.TXT’
    FILE TYPE = ‘ASC”
    TABLES
    DATA_TAB = ITAB
    EXCEPTIONS
    CONVERSION_ERROR = 1
    INVALID_TABLE_WIDTH = 2
    INVALID_TYPE = 3
    NO_BATCH = 4
    UNKNOWN_ERROR = 5
    OTHERS = 6.
    If sy-subrc = 0.
    Calling Function to Create a Session
    CALL FUNCTION ‘BDC_OPEN_GROUP’
    EXPORTING
    CLIENT = SY-MANDT
    GROUP = ‘POTHURI’
    HOLDDATE = DATE1
    KEEP = ‘X’
    USER = SY-UNAME
    EXCEPTIONS
    CLIENT_INVALID = 1
    DESTINATION_INVALID = 2
    GROUP_INVALID = 3
    GROUP_IS_LOCKED = 4
    HOLDDATE_INVALID = 5
    INTERNAL_ERROR = 6
    QUEUE_ERROR = 7
    RUNNING = 8
    SYSTEM_LOCK_ERROR = 9
    USER_INVALID = 10
    OTHERS = 11.
    If sy-subrc = 0.
    *-- MAIN Logic--
    LOOP AT ITAB
    PERFORM GENERATE_DATA. “ Populating BDCDATA Table
    CALL FUNCTION ‘BDC_INSERT’
    EXPORTING
    TCODE = ‘TFBA’
    TABLES
    DYNPROTAB = BDCTAB
    EXCEPTIONS
    INTERNAL_ERROR = 1
    NOT_OPEN = 2
    QUEUE_ERROR = 3
    TCODE_INVALID = 4
    PRINTING_INVALID = 5
    POSTING_INVALID = 6
    OTHERS = 7.
    REFRESH BDCTAB
    ENDLOOP.
    Calling function to close the session
    CALL FUNCTION ‘BDC_CLOSE_GROUP’
    EXCEPTIONS
    NOT_OPEN = 1
    QUEUE_ERROR = 2
    OTHERS = 3.
    Endif.
    Endif.
    *& Form GENERATE_DATA
    Create BDC Data
    FORM GENERATE_DATA
    Passing information for 1st screen on BDCDATA
    BDCTAB-PROGRAM = ‘SAPMTFBA’.
    BDCTAX-DYNPRO = 100.
    BDCTAP-DYNBEGIN = ‘X’.
    APPEND BCDTAB.CLEAR BDCTAB.
    Passing field information to BDCDATA
    BDCTAB-FNAM = ‘SCUSTOM-ID’
    BDCTAB-FVAL = ITAB-ID.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing BDC_OKCODE to BDCDATA
    BDCTAB-FNAM = ‘BDC_OKCODE’.
    BDCTAB-FVAL = ‘/5’.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing screen information for next screen to BDCDATA
    BDCTAB-PROGRAM = ‘SAPMTFBA’.
    BDCTAB-DYNPRO = 200.
    BDCTAB-DYNBEGIN = ‘X’.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing screen information to BDCDATA
    BDCTAB-FNAM = ‘SCUSTOM-NAME’.
    BDCTAB-FVAL = ITAB-NAME.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing screen information to BDCDATA
    BDCTAB-FNAM = ‘SCUSTOM-CITY’.
    BDCTAB-FVAL = ITAB-CITY.
    APPEND BDCTAB.CLEAR BDCTAB.
    Passing BDC_OKCODE to BDCDATA
    BDCTAB-FNAM = ‘BDC_OKCODE’.
    BDCTAB-FVAL = ‘SAVE’.
    APPEND BDCTAB.CLEAR BDCTAB.
    ENDFORM. “GENERATE_DATA
    AN EXAMPLE WITH CALL TRANSACTION
    Same steps to be repeated for CALL TRANSACTION
    The only difference between the two types of interface is in Session method, you create session and store information about screen and data into session. When session is processed the data is transferred to database. While in CALL TRANSACTION, data is transferred directly to database table.
    REPORT DEMO1.
    Follow above Code till MAIN Logic. Even the Subroutine should be copied
    LOOP AT ITAB
    PERFORM GENERATE_DATA, “Populating BDCDATA Table
    Call transaction ‘TFBA’ using BCDDATA Mode ‘A’ Update ‘S’.
    REFRESH BDCTAB
    ENDLOOP.

  • Integration between Sales Pricing and Purchasing pricing

    Hi Experts,
    please can you tell me how it works the integration between Sales pricing (SD) and Purchasing pricing (MM)?.
    Are there specific pricing condition types to manage this integration?
    Thank you very much
    Kinad Regards
    Andrea

    There is no link between SD pricing and MM pricing. But there are some cases when the condition types maintained have to be referenced.
    in STO for example, the pricing procedure in MM may contain a condition type that will have a reference to a condition type maintained in Billing. This value is then used in the SD pricing procedure.
    YOu can do this by maintaining the RefConType in Define condition type in MM pricing determination.
    (SAP Customizing Implementation Guide --> Materials Management --> Purchasing --> Conditions --> Define Price Determination Process --> Define Condition Types)

  • Help on Procedure and trigger for updating(urgent please)

    SQL> / Table A
    CTUT_ID CTUT_COMPANY_NAME CURRT_USER_ID FMIS_ID CREATE_DA UPDATE_BY UPDATE_DATE
    1234 A 15-APR-03
    2222 B 15-APR-03
    3333 C 15-APR-03
    4444 D 15-APR-03
    5555 E 15-APR-03
    6666 F 15-APR-03
    150282 G oRACLE 23-APR-03
    1 H 15-APR-03
    2 I 15-APR-03
    3 J 15-APR-03
    150343 K TIGER 24-APR-03
    150305 L EXAMPLE 23-APR-03
    150342 M SCOTT 24-APR-03
    sQL >/ Table B
    Empno     Empname UPDATE_BY UPDATE_DATE
    1 AA
    2 BB
    3 CC
    4 DD
    What i need to do is i need to create an update trigger on both tables
    like create a procedure
    1)In procedure i need to check like
    IF TABLEA.CURRT_USER_ID = (SELECT USER FROM DUAL)
    THEN
    UPDATE_BY = (CURRENT_USER_ID of CTUT_ID)
    FOR EXAMPLE CURRENT USER_ID IS SCOTT THEN
    UPDATE_BY = 150342
    UPDATE_DATE = SYSDATE
    ELSIF
    UPDATE_BY <=> (CURRENT_USER_ID of CTUT_ID)
    THEN
    MESSAGE('USER IS NOT IN TABLE);
    END IF;
    and call that procedure in the update triggers
    FOR BOTH TABLES TABLEA,TABLEB
    i CREATED A PROCEDURE BUT IT IS NOT WORKING
    ANY HELP PLEASE
    CREATE OR REPLACE PROCEDURE UPDATE(
    UPDATE_DATE out DATE,
    UPDATE_BY out VARCHAR2)
    IS
    Uuser varchar2(20);
    Udate date;
    Ufound number(1);
    BEGIN
    SELECT USER,SYSDATE
    INTO Uuser,Udate from dual;
    SELECT count(*),CTUT_ID into Ufound,Uctut_id
    FROM TABLEA
    WHERE CURRT_USER_ID = Uuser
    Group by Ctut_id;
    IF (UFOUND = 1) THEN
    UPDATE_DATE := UDATE;
    UPDATE_BY := UCTUT_ID;
    END IF;
    EXCEPTION WHEN NO_DATA_FOUND THEN
    RAISE_APPLICATION_ERROR(-20001,'User Does not Exist');
    END UPD_CONSTITUENT;
    CREATE A TRIGGER :
    CREATE OR REPLACE TRIGGER TU
    BEFORE INSERT ON TABLEA
    FOR EACH ROW
    BEGIN      
    UPDATE(:NEW.update_date,
         :NEW.update_BY);
    END IF;      
    END;
    SQL> update TABLEA
    2 set CTUT_COMPANY_NAME = 'SCOTT TEST'
    3 WHERE FMIS_USER_ID = 'N';
    update TABLEA
    ERROR at line 1:
    ORA-04091: table TABLEA is mutating, trigger/function may not see it
    ORA-06512: at "UPDATE", line 12
    ORA-06512: at "TU", line 1
    ORA-04088: error during execution of trigger 'TU'

    Hi Mara,
    You are right thats what i want
    I have a table A
    EmpNo Empname Currtuser_id Update_date Updateby
    1 Denis Oracle
    2 Scott Scott
    3 Mara MMara
    1)what i need to do is when any user tries to update the table Table A
    Then the Trigger or procedure should check whether user is exits in table A in column currtuser_id
    If his user id exits in table A
    Then allow him to update the TABLE A
    and insert his EMPNO in UPDATE_BY
    and SYSDATE in UPDATE_BY
    He will do all this process using forms
    But i need to have trigger or procedure in database level for table
    2) I have another table like 10 tables
    Suppose TABLE B
    When user tries to update TABLE B
    Then the Trigger or procedure should check whether user is exits in table A in column currtuser_id
    If his user id exits in table A
    Then allow him to update the TABLE B
    and insert his EMPNO in UPDATE_BY
    and SYSDATE in UPDATE_BY
    3) I need to have a common Procedure and call that procedure in all tables in UPDATE TRIGGER
    Thanks for your help
    Thanks

  • Dynamically calling stored procedure and getting result set c++

    Hello,
    I am trying to write some c++ code that will dynamically bind values to a stored procedure and excute the procedure and get back a resultset. The problem I am running into is how to get back the resultset. Any help or example would be highly appreciated.

    int main(int argc, char* argv[])
    OCIError* pOciError;
    char* pConnectChar = "dbname";
    char* pUsernameChar = "scott";
    char* pPasswordChar = "tiger";
    int answer;
    OCIStmt* pOciStatement;
    char* sqlCharArray = "BEGIN :success := sp_ListEmp; END;";
    int id;
    char ename[40];
    OCIEnv* g_pOciEnvironment = NULL;
    OCIServer* g_pOciServer = NULL;
    OCISession* g_pOciSession = NULL;
    OCISvcCtx* g_pOciServiceContext = NULL;
    sb2* pIndicator=0;
    sb2* pIndicator2=0;
    sb2* pIndicator3=0;
    OCIDefine* pOciDefine;
    OCIDefine* pOciDefine2;
    OCIBind* pBind;
    OCIStmt* cursor;
    answer = OCIInitialize(OCI_THREADED, NULL, NULL, NULL, NULL);
    answer = OCIEnvInit(&g_pOciEnvironment, OCI_DEFAULT, 0, NULL);
    answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&pOciError, OCI_HTYPE_ERROR, 0, NULL);
    answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&g_pOciSession, OCI_HTYPE_SESSION, 0, NULL);
    answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&g_pOciServer, OCI_HTYPE_SERVER, 0, NULL);
    answer = OCIHandleAlloc(g_pOciEnvironment, (void **)&g_pOciServiceContext, OCI_HTYPE_SVCCTX, 0, NULL);
    answer = OCIServerAttach(g_pOciServer, pOciError, (unsigned char *)pConnectChar, strlen(pConnectChar),
    OCI_DEFAULT);
    answer = OCIAttrSet(g_pOciSession, OCI_HTYPE_SESSION, (unsigned char *)pUsernameChar, strlen(pUsernameChar),
    OCI_ATTR_USERNAME, pOciError);
    answer = OCIAttrSet(g_pOciSession, OCI_HTYPE_SESSION, (unsigned char *)pPasswordChar, strlen(pPasswordChar),
    OCI_ATTR_PASSWORD, pOciError);
    answer = OCIAttrSet(g_pOciServiceContext, OCI_HTYPE_SVCCTX, g_pOciServer, 0, OCI_ATTR_SERVER, pOciError);
    answer = OCIAttrSet(g_pOciServiceContext, OCI_HTYPE_SVCCTX, g_pOciSession, 0, OCI_ATTR_SESSION, pOciError);
    answer = OCISessionBegin(g_pOciServiceContext, pOciError, g_pOciSession, OCI_CRED_RDBMS, OCI_DEFAULT);
    answer = OCIHandleAlloc(g_pOciEnvironment, (void **)(&pOciStatement), OCI_HTYPE_STMT, 0, NULL);
    answer = OCIStmtPrepare(pOciStatement, pOciError, (unsigned char *)sqlCharArray, strlen(sqlCharArray),
    OCI_NTV_SYNTAX, OCI_DEFAULT);
    answer = OCIHandleAlloc(g_pOciEnvironment, (void **)(&cursor), OCI_HTYPE_STMT, 0, NULL);
    answer = OCIBindByPos(pOciStatement,&pBind, pOciError, 1, &cursor, 0,SQLT_RSET,
    pIndicator2, 0,NULL, 0,0,OCI_DEFAULT);
    answer = OCIStmtExecute(g_pOciServiceContext, pOciStatement, pOciError, 1, 0, NULL, NULL,
    OCI_COMMIT_ON_SUCCESS);
    answer = OCIDefineByPos(cursor,&pOciDefine, pOciError,2,&id,sizeof(int),
    SQLT_INT,pIndicator, 0, 0,OCI_DEFAULT);
    answer = OCIDefineByPos(cursor,&pOciDefine2, pOciError,1,ename,40,
    SQLT_STR,pIndicator3, 0, 0,OCI_DEFAULT);
    if (answer == 0)
    while ((answer = OCIStmtFetch(cursor,pOciError, 1,OCI_FETCH_NEXT,OCI_DEFAULT)) == 0)
    printf("fetched id %d and name %s\n",id,ename);
    answer = OCIHandleFree(pOciError, OCI_HTYPE_ERROR);
    return 0;

  • SPL determination procedure and  control procedure

    Hello all
    Can someone help me in understanding what  a determination procedure and a control procedure means during SPL screening  ? How these two are linked , during "configuring the SPL check algorithm" .?
    How is the spl determination procedure is linked to the document type ? ( As i see that there are already standard determiantion procedures for each service eg:   1 : lespl for SPL check
    2: leldt for licence det ..... etc 
    when a document is sent from R/3 to GTS how does the system identifies the procedure that it has to go with ?   for eg lespl or leldt..
    Thanks alot ..

    Hi
    Det Procedure
    We define the Det procedures  to use to determine the active legal regulations for a particular service like SPL. We define the determination stratgey for Det proc. to determine the Leg reg.
    Control Procedure  for Address comparison:
    We  define a control procedure to determine the rules according to which the system performs sanctioned party list (SPL) checks, this tell what exact detail has to be chekced for SPL like name , city and so  on in an address and set rule for how the string of address will be checked against SPL data.
    How is the spl determination procedure is linked to the document type ? ( As i see that there are already standard determiantion procedures for each service eg: 1 : lespl for SPL check
    2: leldt for licence det ..... etc
    Ans :
    SPL det Proc determines the Leg reg which can be for SPL or Embargo . And for each service we  like SPL  we have document type activated this was Det Proc get related to Doc type.
    when a document is sent from R/3 to GTS how does the system identifies the procedure that it has to go with ? for eg lespl or leldt..
    Ans:
    Each doc type coming from a Feeder system is assigned to Document type defined and activated for a particualr service like SPL , and also we actiavte Det Proc separatley for eac servces like SPL.
    When ever a doc comes to GTS it get determined to which  GTS doc type it is assigned and that  then it is determined under what service that GTS doc type is defined.
    Suppose OR is assigned to EXORD1 ( GTS doc type) and this doc type comes under SPL so now the configuration for SPL will have particualr Det Procedure actiavted.
    Hope this helps
    Kind Regards,
    Sammer

  • Diff between function,procedure/packages  and Diff bet delete,truncate,drop

    Dear all
    I am your pal ranga from IT capital bangalore india. I would like have detail discussion with respect to subject. Pls discuss
    Thanks and Regards
    B.Rangarajan

    Justin gave good advise but here is the short version of the answer just for the heck of it
    Function => stored code suitable for use in the select list of a query and in the where clause conditions that generally accepts one parameter and returns one value. Allows user to extend list of Oracle provided row queries.
    Procedure => stored code designed to return one or more values to the caller. Procedures are generally called from other stored code routines or directly from the user application and not as part of a query or DML statement.
    Package => a collection of stored procedures and functions
    Delete => DML row operation to remove rows from a table
    Truncate => DDL operation to quicky and with minimum overhead mark a table and its associated indexes as empty
    Drop => DDL operation to remove a table or other object from the database
    Maybe these definitions will help until you cover the reading. You can also learn this from the Concepts manual. If you are a DBA this manual is where you should start. For a Developer I would start with the Application Developers - Fundamentals.
    HTH -- Mark D Powell --

Maybe you are looking for

  • Wifi is unstable and can't connect to internet

    please help.other devices can connect easily but just recently this happens,others are normal and the same.the same number of users and good signal strength

  • BT Infinity evening and weekend speed drops

    Hi, I have a BT Business Hub 5 and Infinity package. My connection during the working week in the day is usually around:  27.95MB/s down, 4.63Mb/s up and a ping of around 20ms. Often in the evenings and on weekends the speed drops to around: 1.5MB/s

  • Just installed 10.6.4. Now clicking on Print&Fax crashes system preferences

    Hi all, Just installed Snow Leopard 10.6.4 and then couldn't print from my Kodak EasyShare 5300 printer. I installed updated software and firmware from Kodak. Still can't print and when I click on Print & Fax in system preferences it crashes system p

  • PB 12" 867 The battery is in, but the indicator in the menu bar says no

    Hi, My alubook has a strange problem. It is 2,5 years old and I had no battery problem during a long time. For the past 2 or 3 weeks, I have to use the powerbook with the power connected, the PB seems not to "see" that a battery is plugged whatever i

  • Bug in Oracle-grid/sapctl setup .. manually it works

    I want to protect the standalone enqueue server with Oracle cluster (11.2.0.2). Somehow the connection between crs and sapctl does not work properly - funny enough, the manual invocation of crssapactions.pl is successful (see below) . [root@rac11a ~]