Configuration steps required in ID

Hello Experts,
I am new in XI/PI. Can anyone explain me the configuration steps required when we have one sender and multiple receiver.
I have a scenario having file as a sender and JDBC,File and JMS on receiver side.
If anyone have the screenshot for similer scenario will be more helpful.
Regards,
Jay.

Hi,
  in ID, you will need...
1) 1 receiver determiantion
2) 3 interface determination
3) 3 receiver agreement
4) 1 sender agreement
5) 1 sender and 3 receiver channel
Regds,
Pinangshuk.

Similar Messages

  • What are the configuration steps required ?

    Hi
    Gurus,
    Client requires:
    "We have construction going on at our warehouses and the projects are going
    to take about a year.  We need to track retainers on the payments we make to the contractor. 
    Payments are due in a couple of weeks and it is a priority to monitor progress on the construction."
    Example:
                                                                    GL Account#         
    Debit  Construction In Progress                      122000          100%
    Credit  Vendor                                                601095            90%
    Credit  Accounts Payable / Retainage            202000            10%
    At this time we have a request for a solution to process what is necessary
    to compile with the following scenarios.
    what are the configuration steps required.
    Thanks
    Anil

    Hi,
    Whether the contractors are treated as one time vendors or regular vendors. If you have to create new account group for subcontractors
    Does only one account group related vendors need the retainage analysis or for all the vendors. Will be mainly the general contractors at each location  One group is sufficient even they are at different location you can maintain the same in REGION
    Does only single partial payment exists and the remaining due amount to be treated as due on a particular date or multiple payments exists against the same invoice. The 10% must accumulate in a liability account over the life of the contract and is paid at the end. There may be multiple of payments which you need to knock off against the service entry sheet(study above reply)
    The construction cost which is treated as outstanding to Vendor to be exclusive of the cash expenditure made for such construction. Yes, but the entire 100% needs to debited to CIP Until and unless the work is not completed so how you can treat as outstanding payment to vendor. If you want you can maintain a provision for this
    Check with above and above replies.
    Regards,
    Sankar
    Edited by: Durgasankar.Innamuri on Jul 29, 2010 10:17 AM

  • CIN-MM Configuration steps required for First Stage Delaer purchases.

    Hi,
    I am looking for CIN-MM Configuration steps required for First Stage Delaer purchases.
    We have steps Configured for CIN-MM from Manufacturer for purchase of Materials and Capital Goods.
    Thanks in advance.
    Regards,
    Purna.

    Hi Purnachandrarao...  ,
    There is no seperate configuration required in dealer's case.
    For this you have to use zero Tax code.Material should be maintained in J1id.
    So that Tax % will be picked up from there.
    But at the time of GR you have to tick MRP indicator in excise tab.
    And also you have to change values of BED and cess as per vendor's invoice.
    So that value will be fetched at the time of invoice verification.
    Regards,
    Gitesh

  • Transportation Configuration Steps required:

    Hi Guru's
    I am new to this module, could you please show the configuration steps for the SD- Tranporrtation module please.
    sushil

    Hi Sushil,
    TMS Total steps:
    3.     Terminology:
    Mentioned below are some important terms used in Transportation:
    SAP Terminology:                Description
    1. Forwarding Agent:                Agent who provides the transportation
    2. Transportation Planning Point :      Org. unit responsible for planning shipments with particular features. E.g.: A company has different groups of shipping personnel responsible for organizing shipments by train or ship
    3. Shipment Document:     The document containing the details of the deliveries, service agents
    , routes, stages, planning and execution times.
    4. Shipment Type:     Shipment types contain all the essential control features for the shipment document such as number ranges, service level, and output and partner determination.
    5. Routes:     The route determines the itinerary and the means of transport in shipping, and influences transportation scheduling.
    6. Shipment Cost Document     The shipment cost document is the used for shipment cost processing. It contains the details related to accounting and the cost calculations.
    7.Shipment cost type and item categories     Shipment cost types and item categories contain all the important control features for the shipment cost document, such as number range, status requirements for the shipment documents, and parameters for shipment costing, parameters for shipment settlement.
    8. Master Data:
    Purchase Order is created for Vendor if the weekly or monthly orders are not created during the transaction by the system.
    Relevant pricing conditions are maintained.
    9. Customization:
    1. Transportation Relevance is marked for Delivery type, Delivery Item Type,   Route.
    2. Route Determination is active.
    3. Route is determined in the delivery document.
    4. Shipment types are created as desired.
    5. Shipment pricing procedure is in place.
    6. Shipment cost types are created and assigned to shipment types.
    7. Purchasing Data is assigned.
    8. G/L Account assignments are done.
    10. 1.Maintain Transportation Planning Point
    The transportation planning point represents a group of employees responsible for organizing transportation activities. Each shipment is assigned to a specific transportation planning point for transportation planning and shipment completion
    The transportation planning point is assigned at Co-Code level.
    Menu Path: Enterprise Settings > Definition > Logistics Execution > Maintain transportation planning point
    10.2.Define Routes
    The route determines the itinerary and the means of transport in shipping, and influences transportation scheduling. The description of routes, service agent, distance and lead times are defined in routes.
    Menu Path: Logistics Execution > Transport > Basic Transportation Functions > Routes > Define Routes > Define Routes And Stages
    10.3.Maintain Route Determination:
    Routes are determined depending on the following criteria:
    1.     Country and departure zone (departure zone of the shipping point)
    2.     Shipping conditions agreed in the sales order.
    The shipping condition is defined in shipping point determination.
    3.     Transportation group of the material
    4.     Country and transportation zone (receiving zone) of the ship-to party
    Menu Path: Logistics Execution > Transport > Basic Transportation Functions > Routes > Define Routes > Route Determination > Maintain Route Determination
    10.4Maintain Transportation Relevance
    Delivery types and delivery item categories for which transportation processing is to be carried out must be characterized as relevant for transportation.
    All routes that are to be used for the shipment must also be set as relevant for transportation.
    Menu Path: Logistics Execution > Transport > Shipments > Maintain Transportation Relevance
    10.5.Define Shipment Types:
    The shipment types represent the different forms of transportation processing in sales and distribution.
    The following forms of transportation processing are distinguished:
    1) Individual shipment, one or more deliveries are transported by a single mode of transport from one point of departure to one final destination.
    2) Collective shipment, one or more deliveries are transported by a single mode of transport from one or more points of departure to one or more final destinations.
    3) Multimodal shipment, deliveries are transported by several modes of transport between one or more points of departure and one or more final destinations.
    Menu Path: Logistics Execution > Transport > Shipments > Define Shipment Types
    10.6.Define Shipment Cost types
    10.7.Pricing
    Logistics Execution > Transport > Shipment Costs > Pricing > Pricing Control > Define And Assign Pricing Procedures
    10.8 Settlement

  • Scheduling Agreements configuration steps required Plz !

    Dear Sapients,
    I request you all to help me in providing the configuration steps for Scheduling Agreements and relevant Schedule lines configuration.
    Its urgent please help me !!
    Regards,
    Sreedhar.

    Hello,
    please have a look at the following links:
    http://help.sap.com/saphelp_media472/helpdata/EN/dd/56078c545a11d1a7020000e829fd11/frameset.htm
    and
    http://help.sap.com/saphelp_media472/helpdata/EN/da/76ab04ebea11d1954900a0c9306667/frameset.htm
    I hope that you find here all information which you want.
    Regards
    Claudia

  • Configuration steps for Extended Classic Scenario

    Hi All,
    Could you please let me know what are the configuration steps required for extended classic scenario.
    Thanks in advance

    Hi,
    Important Settings that Determine the Extended Classic Scenario
    The following settings are required for the extended classic scenario:
    u2022 At least one backend materials management system and accounting system is connected to the SAP SRM system and defined in the configuration setting Define Backend Systems.
    u2022 Product categories from the backend procurement system are replicated and used in the SAP SRM system.
    u2022 The target system for each product category is the backend system in the configuration setting Define Backend Systems for Product Category. Optionally, BADI BBP_DETERMINE_LOGSYS is implemented to determine the backend system.
    u2022 The extended classic scenario is activated in the configuration setting Activate Extended Classic Scenario. Alternatively, BAdI BBP_EXTLOCALPO_BADI is implemented to control the extended classic scenario based on customer defined rules.
    u2022 If the backend system is an SAP R/3 version lower than 4.6B, you must define local purchasing organizations and purchasing groups.
    u2022 If the backend system is an SAP R/3 version 4.6B or higher, you need to map the purchasing group used in the purchase order to the backend purchase group in one of the following ways:
    u2022 Use a backend purchasing organization and purchasing group in the shopping cart and purchase order.
    u2022 Use BAdI BBP_PGRP_FIND to determine a backend purchasing group in the shopping cart.
    u2022 If a local (created in SAP SRM without reference to a backend system) purchasing group and purchasing organization are used, then a valid backend purchasing group is assigned to the RFC user that created the backend purchase order. This assignment is made in the backend system using user parameter EKG in Transaction code SU01.
    u2022 Implement the user exit of the BAPIs BAPI_PO_CREATE1 (EXIT_SAPL2012_001 and EXIT_SAPL2012_003), and BAPI_PO_CHANGE (EXIT_SAPL2012_002 and EXIT_SAPL2012_004) to determine the purchasing group with a customer- specific logic.
    This is for your additional information.
    Hope this helps.
    Regards,
    Vikas

  • Configuration steps to Trigger IDOC from R/3 to XI

    Hi All,
    I have read several forums ,
    and i am in confusion to follow which one of them.
    Let me describe the process of configuration steps in r/3 and XI in step by step and correct me when i am wrong.
    Steps in R/3
    1)  Goto SALE.
       Basic settings->Logical Systems->Define logical system.
       Create two logical systems(one for XI and the other for R3)
       Basic settings->Logical Systems->Assign logical system to client.
       Assign the R3 logical system to respective client.
       Assign the XI logical system to respective client.
      Whether i need to create  logical sys name only for r/3 or both for r/3 and XI?
    2)Goto SM59.
       Create new RFC destination of type 3(Abap connection).
       Give a suitable name and description.
       Give the Ip address of the XI system.
       Give the system number.
       Give the gateway host name and gateway service (3300 + system number).
       Go to the logon security tab.
       Give the lang, client, username and password.
       Test connection and remote logon.
       Gateway service can be sapgw<sys number> or it should be 3300+sys number?
    3)Goto WE21.
        Create a port under transactional RFC.(R3->XI) 
        Designate the RFC destination created in prev step.
       Port name should be in the form of SAP+SID of XI or it can be anyting?
    4) Goto BD64.
       Click on Create model view.
       Add message type.
       Is it necessary to create a Distribution model and distribute it ?
    5) Goto WE20
        Goto WE20.
        Partner type LS.
        Create a partner profile
        Give the outbound or inbound message type based on the direction.
    Steps in XI
    1)  Goto SALE.
       Basic settings->Logical Systems->Define logical system.
       Create one logical systems(only for R3)
       Basic settings->Logical Systems->Assign logical system to client.
       Assign the R3 logical system to respective client.
      Whether i need to create once again logical sys name for r/3 ?
    2) Goto SM59
       Create new RFC destination of type 3(Abap connection).
       Give a suitable name and description.
       Give the Ip address of the XI system.
       Give the system number.
       Give the gateway host name and gateway service (3300 + system number).
       Go to the logon security tab.
       Give the lang, client, username and password.
       Test connection and remote logon.
       Gateway service can be sapgw<sys number> or it should be 3300+sys number?
    3)Goto IDX1.
        Create a port under transactional RFC.(XI->R3) 
        Designate the RFC destination created in prev step.
       Port name should be in the form of SAP+SID of R3 or it can be anyting?
    Step 4)Goto IDX2
      Create a new Meta data.
    Give the Idoc type.
    Select the created port.
    Is it neccessary to create a medata?
    Let me know the answers for my questions.
    Thanks
    Sai

    Not sure what you have referred till now but there are some excellent link that will close this for you.
    ALE configuration for pushing idocs from SAP to XI -
    ALE configuration for pushing idocs from SAP to XI
    Configuration steps required for posting idoc's(XI) -
    Configuration steps required for posting idoc's(XI)
    Wiki: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/sapR3%28Idocs%29ToXI--Steps+Summarized&

  • Application Group URL generation - config steps required

    Hi
    We have ECC6 and using Erecruitment release 603.
    I am seeking guidance on how to generate application group URLs ie the configurations steps required in order for the URL to be generated.
    many thanks
    Julie

    Hello Julie,
    basically the generation of URLs for application groups does not need any special configuration. It simply works without any settings. Only configuration which might effect the generation is the general requirement that the full qualified domain name must be set in system parameter icm/host_name_full for every e-rec server. Furthermore you can use table HTTPURLLOC to overwrite e-rec generated URLs for replacing internal server names. But both should not influence the URL generation in general.
    I referred to the reference code generation as this is (in sap standard) only possible for requisitions. The button for the generation is placed on view pinstDetails.bsp of BSP application hrrcf_pinst_mnt which is the detail view for publication maintenance in requisitions. The application group container sequence uses the view status.bsp of BSP application HRRCF_APPL_GRP. This view contains 3 fields reference code, status and the field to display the generated URL. If there is a button for the reference code generation or the view is completely different someone either included the wrong view in the container sequence or someone modified it.
    So first step should be to check if you are on the correct unmodified view.
    Could you please check if this and give a message about your result?
    Many Thanks
    Roman

  • Steps required for cin configuration

    hi,
    can anybody give me the steps required for cin configuration.

    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

  • OBIEE 11g installation failed multiple times at Distributing Repository Configuration Step

    Hi,
    I am getting the following error during the Distributing Repository Configuration step in the OBIEE 11g 11.1.1.7 enterprise installation in Windows 8 system.
    Severe: Element Type:Domain
    Element id: null
    Operation result: failed to obtain domain file lock
    Detail Message: java.util.concurrent.timeoutException.Timeout;
    waiting for lock: Domain config lock;
    c:\OBIEE\MIDDLE~1\USER_p~1\domains\EAM_DO~1\config\FMWCON~1\biee-config.lock;[121 secs]
    Step Distributing Repository failed
    Configuration Action 'Distributing Repository' has failed. Please check logs for details.
    Step Distributing repository failed
    I checked another blog for this https://forums.oracle.com/thread/2565716 and even there the explanation doesn't convince me.
    I tried to look at the Locale of my system where I am installing and I could see it is using Eng-Us by default. One way suggested to check the Unicode format from the web browser and I could check that too to be UTF-8 as suggested by someone on some other blog.
    I checked in the logs too as suggested by the Installation dialogue box but it didn't seem much conclusive too.
    Here is the snapshot of the log file which I could found.
    INFO: Current Inventory:
      Oracle Home: OraDb11g_home1
      This Oracle Home has not been changed in this session.
      Oracle Home: OH1858390736
      This Oracle Home has not been changed in this session.
      Oracle Home: OH440082373
      This Oracle Home has not been changed in this session.
      Oracle Home: OH440082374
      This Oracle Home has not been changed in this session.
      Oracle Home: OH1597391518
      This Oracle Home has not been changed in this session.
      Oracle Home: OH1285215443
      This Oracle Home has not been changed in this session.
    INFO: Ending the inventory Session
    INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
    INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
    INFO: Using an existing InstallAreaControl for this Inventory Session with existing access level 1
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    INFO: The ORACLE_CONFIG_HOME env var is set to
    Can someone please help me with this since I am stuck with for quite some time now.
    Is there any way to check in command prompt to check the locale as required by the system.
    What could be the issue here?
    Thanks,
    Nitin

    Hi all,
    We are able to resolve the above issue with the below solution.
    Root cause of the issue:
    You may have a temp directory in the path C:\Documents and Settings\user_name\Local Settings\Temp. You got the above mentioned exception because of the temp directory path having spaces_+ in it.
    Solution:
    1. Create a new directory called TEMP in a different location for ex: C:\TEMP
    2. Now, Right click on My computer --> Properties --> Advanced --> click on Environment Variables.
    3. You should be having TEMP and TMP as variables under user variables section pointing to the C:\Documents and Settings\user_name\Local Settings\Temp path.
    4. Edit the TEMP and TMP variables and mention C:\TEMP in the variable value.
    5. Deinstall and re-install OBIEE 11g.
    Happy OBIEE 11g installation!!
    Thanks,
    Rajesh Gurram

  • Configuration steps to create New Special GL

    HI,
    Can any one please send me configuration steps to create New Special GL. My client required to create new special GL for Rent Advance.
    NOTE: hear I am not asking how configuration steps for assigning GL accounts for existing Special GL. I want new Special GL to be Create for rent advance.
    It’s very urgent
    My mail id "[email protected]"
    Thank you
    mahesh

    Hi,
    go to transaction code fbzp where you assign GL account to the spl GL indicator.
    Go and create a new spl GL indicator there by clicking create new.
    Bye

  • Configuration Steps for Decentralized Adapter Engine

    Hi all,
    What all configuration steps are required to make Adapter Engine as
    Decentralized AE.
    I have made required changes in SLD DataSupplier in Visual Administrator.
    what more configurations have to be done? On SAP XI Server and Decentralized
    Adapter Engine.
    With regards
    Prasad

    Prasad,
    After configuring SLD data supplier in Visual Admin, you need to the following
    1) Configure the gateway service for the central integration server on adapter engine host.
    2) Perform Initial adapter engine cache refresh
    3) Trigger data transfer to SLD
    4) Check the connection parameters in exchangeProfile
    5) Create HTTP destination pmistore in java environment
    you have to go through all these tests for decentralized adapter engine. If you have XI configuration guide, it has all these steps in detail for you to configure
    --Archana

  • Risk Mgmnt COnfiguration steps

    Hello Friends
    Can anyone please tell me the complete steps to configure "Risk Management " with LoC (Letter of Credit) & what is the necessary data to be collected from the business, for configuring the same.
    Regards
    Sumanth.Gururaj

    Hi,
    The configuration steps for risk management
    How To Do Configuration For Credit Management
    Credit and risk management takes place in the credit control area. According to your corporate requirements, you can implement credit management that is centralized, decentralized, or somewhere in between. 
    An organizational unit that represents the area where customer credit is awarded and monitored.   This organizational unit can either be a single or several company codes, if credit control is performed across several company codes. One credit control area contains credit control information for each customer.
    For example, if your credit management is centralized, you can define one credit control area for all of your company codes. 
    If, on the other hand, your credit policy requires decentralized credit management, you can define credit control areas for each company code or each group of company codes. 
    Credit limits and credit exposure are managed at both credit control area and customer level.  You set up credit control areas and other data related to credit management in Customizing for Financial Accounting. The implementation guide is under Enterprise Structure -> Definition or Assignment -> Financial Accounting and then Maintain credit control area. You assign customers to specific credit control areas and specify the appropriate credit limits in the customer master record.
    Settings for determining the credit control area of a document.  The settings of items 1 - 4 are taken into account according to their priority.  The credit control area found is stored in field VBAK-KKBER.
    1. Transaction OB38
       Check which credit control area is assigned to the company code.
       Company code:
       Credit control area:
    2. Transaction OVFL
       Check which credit control area is assigned to the sales area.
       Sales area:
       Credit control area:
    3. Transaction XD02 or VD02
       Check which credit control area is assigned to the payer.
       Payer:
       Credit control area:
    4. Transaction SE37
       Is user exit EXIT_SAPV45K_001 being used?
    5. Transaction OBZK
       For the settings under items 2 - 4, field "All company codes" must be marked in Transaction
    OB45, or the credit control area must be entered under the relevant company code in table T001CM of the credit control areas allowed.
    Company code:
    Credit control areas allowed:
    6. Settings for the credit checks
    7. Transaction OVAK
       Which settings do exist for the sales document type used?
       Sales document:
    Check credit:
    Credit group:
    8. Transaction OVAD
       Which settings do exist for the delivery type used?
    Delivery type:
    Credit group for delivery:
    Credit group for goods issue:
    9. Transaction OB01
       Credit management/Change risk category
       Definition of the risk category for each credit control area. This risk category can be assigned to a credit account by using Transaction FD32.
    10. Transaction OVA8
        Here, the individual credit checks for key fields
        o credit control area
        o risk category
        o credit group are set. Take these key fields from the above settings and go to the detail screen. In particular, check whether fields "Reaction" and "Status/block" are set correctly. To carry out follow-up actions in case of a credit block, the credit check status must be set (field "Status/block").
    11. Transaction FD32
        Credit master data for the payer of the relevant document.
        Credit account:
        Credit limit:
        Risk category:
        Currency:
    12. Settings for updating the credit values Update of the credit values is required for the limit check (static or dynamic credit limit check).
    13. Transaction OVA7
        Update of the credit value is active for the corresponding item type if the check box is marked. This field corresponds to 
        field "Active receivable" in Transaction VOV7.
    Item type: 
    Active receivable:
    14. Transaction V/08, Pricing
        In the pricing procedure used for pricing, subtotal "A" must be entered in a line for determining the credit value (mark the pricing procedure and doubleclick on "Control").
    Usually, the net value plus taxes is used. This way the system is determined to use this subtotal for credit pricing. The credit price is stored in field VBAP-CMPRE and used for update and credit check.
    You can find the used pricing procedure of the order under "Item -> Condition -> Analysis".
    Pricing procedure:
    Line with subtotal = 'A':
    15. Transaction OB45
        Which update group (field "Update") do you use in the relevant credit control area? The default setting is "12". If you use another update group, check whether this is fine with you. If you open an OSS message, please tell us the alternative update group.
    Credit control area:
    Update:
    16. Transaction OMO1
        Which kind of update did you choose for structure S066? 
         In any case, "Synchronous update (1)" has to be chosen as the kind of update.  All other settings will lead to errors.
    Credit Management Reports
    The following table provides an overview of all the reports that are available for credit management:
    Program     Function
    RFDKLI10     Customers with Missing Credit Data
    Checks whether the data regarding credit limits is complete and issues relevant error lists. These enable you to maintain the relevant definitions either manually or with batch input.
    RFDKLI20     Reset Credit Limit for Customers
    Resets the credit limit information in the control areas.
    RFDKLI30     Credit Limit Overview
    Lists the central and control area data for each customer.
    RFDKLI40     Credit Overview
    Provides a comprehensive overview of the customeru2019s credit situation.
    RFDKLI41     Credit Master Sheet
    Displays and prints the customer master data for an individual account that is needed for credit management.
    RFDKLI42     Early Warning List
    Displays and prints customers in Credit Management who have been listed by the credit check as critical.
    RFDKLI50     Credit Limit Data Mass Change
    Changes all the credit management master data together.
    RFDKLIAB     Display Changes to Credit Management
    Displays the changes to credit management master data for all accounts.
    RVKRED06     Check Blocked Credit Documents
    Checks all the documents blocked for credit reasons. The report is started in the background and should run after the incoming payments programs.
    RVKRED77     Reorganize SD Credit Data
    Reorganizes open credit, delivery and billing values. It can be used in the event of an update error, for example.
    RVKRED08     Checking sales documents which reach the credit horizon
    Rechecks all sales documents that fall within the credit limit horizon of the dynamic credit limit check. The report is run at regular intervals and should be run at the start of each period. The system uses the current date and the period split for the open order values to propose the u2018next credit check dateu2019.
    RVKRED09     Check Credit Documentation Background
    Checks released documents whose validity period of the release has been exceeded (number of days).
    RVKRED88     Simulating Reorganization of SD Credit Data
    To run a report:
    1.     Choose System ® Services ® Reporting.
    2.     Enter the name of the report.
    3.     Choose Program ® Execute.
    4.     Enter your selection criteria.
    5.     Choose Program ® Execute or Program ® Execute and print.
    SAP SD Credit Management Tcodes
    All business have their own credit management needs, SAP allows you to specify your own automatic credit checks based on a variety of criteria.  You can also specify at which critical points in the sales and distribution cycle the system carries out these checks.
    SM30 - Table/View
    u2022     V_TVTW - Define Distribution Channel
    u2022     V_TVTA_KKB - Assign sales area to credit control area
    u2022     V_T014 - FI - Define Credit Control Area
    u2022     T001CM - FI - Assign Permitted Credit Control Area to company code
    OVXG - Set up Sales Areas
    e.g.  Sales Organization
                      Distribution Channel
                                  Division
                      Distribution Channel
                                  Division
    FD32 - Customer Credit Management
    OVAK - Define credit limit check by sales document type
    u2022     Check Credit
    o     A - Credit limit check and warning message
    o     B - Credit limit check and error message (no sales order can    be created)
    o     C - Credit limit check and delivery block (block delivery if hit   credit limit)
         Options B and C -> used for checking open order values (when you create/change the sales order)
    o     D - Automatic credit control with open order values
         More control in transaction OVA8 - Automatic credit control
         You check for open orders and deliveries, or just open deliveries.
         or open order values with other options
    u2022     Credit group
    o     Allows you to combine different sales document types for the credit limit check
    VKM1 - Blocked SD Documents - Finance have to released the delivery block
    OVAD - Define credit limit check by delivery order
    u2022     whether the automatic credit check occurs at the time of delivery creation and/or goods issue
    OVA7 - Define credit limit check by item category
    u2022     Set whether to include/exclude item category for credit limit check
    OVA6 - Define credit group. You can groups together different business transactions which should be dealt with in the same manner with regard to the credit check.
    You enter the credit groups when you configure the sales document types for credit management and define the (D - automatic credit check).
    u2022     SAP default credit groups
    o     01 - credit group for sales order
    o     02 - credit group for delivery
    o     03 - credit group for goods issue
    OVA8 - Automatic credit control - Double click on the line items
    You can have the followings credit limit check :-
    u2022     Static
    Depends on the customer total value of open orders, deliveries, billing documents and open items.
    u2022     Open items
    No of days open
    Overdue open items checks is based on the ratio of open items that are overdue by a certain number of days.
    Max open items %
    The customer balance must not exceed a certain percentage.
    u2022     Oldest open items
    If you don't want to deliver to the customer at all when even only 1 invoice is overdue.
    Tick the Check for Oldest Open Item and Set the field Days oldest item = 1.
    Dayu2019s oldest item
    No of days allowed for overdue or payment terms.
    Use of the credit checks Oldest Open Item. If a user attempts to alter the order quantity of a released sales document
    that was previously blocked, it would be re-blocked again by the system.  The system only re-blocks the sales document if the new order quantity is above a certain % amount.
    u2022     Released documents are still unchecked
    The preset % is whatever you want to set it as when configuring your automatic credit processing. You enter a deviation % and number of days,eg, you can set it so that an order can be changed by up to 10% within 30 days of original order entry date without it going back on credit block.
    u2022     Next Review Date
    If a customer has a credit limit of 1000 USD, and you would like to restrict this credit limit only to be available in current month (say March). If the document date is in April then the credit limit is zero.
    You can use the "NextReview date" and "Number of days" fields and combined it with the "Last int.review" field in customer credit master "Status" view (FD32).
    VOKR - Display of work list for credit management (configure the display variant)
    SIMPLE CREDIT CHECK:
    Tr.Code - FD32
    It Considers the Doc.Value + Open Items.
    Doc.Value: Sales Order has been saved but not delivered
    Open Item: Sales Order has been saved, Delivered, Billed & Transferred to FI, but not received the payment from the customer.
    Eg: Customer Credit Limit is Rs.1, 00,000/-
    Suppose Doc.Value + Open Item Value is Rs.1,10,000/-
    Here credit limit exceeds then system reacts.
    Options: A) Warning Message
    B) Error Message (Sales Order won't be saved)
    C) Error Message with Delivery Block
    AUTOMATIC CREDIT CHECK: Give extra credit facilities to the particular customer.
    STATIC CREDIT LIMIT DETERMINATION: Checking Group + Risk Category + Credit Control Area.
    A) Credit Checking Groups: Types of Checking Groups.
    01) Sales
    02) Deliveries
    03) Goods Issue
    At all the above 3 levels orders can be blocked.
    B) Risk Category: Based on the risk Categories Company decides how much credit has to give to the customer.
    HIGH RISK (0001) :      LOW CREDIT
    LOW RISK (0002) :      MORE CREDIT
    MEDIUM RISK(0003): AVERAGE CREDIT
    Static Credit Check it checks all these doc value & check with the credit limit
    1) Open Doc.Value / Sales Order Value: Which is save but not delivered
    2) Open Delivery Doc.Value: Which is delivered but not billed
    3) Open Billing Doc.Value: Which is billed but not posted to FI
    4) Open Item: Which is transferred to FI but not received from the customer.
    DYNAMIC CREDIT CHECK:
    1) Open Doc
    2) Open Delivery
    3) Open Billing
    4) Open Items
    5) Horizon Period = Eg.3Months
    Here the System will not consider the above 1,2,3& 4 values for the last 3 months
    Then assign the Sales Doc & Del Documents.
    Sales Doc.Type(OR) + credit Check (0) + Credit Group (01)
    Credit Limit Check for Delivery Type : Del.Type (LF) + Del Credit
    Group (02) + Goods Issue Credit Group (03)
    User Exits For Credit Checks And Risk Management
    Credit Check
    I hope this will resolve your issue
    Thanks
    Anil Hooda

  • Configuration steps for EBP to SUS

    Hi All,
       Can anybody please give EBP to  SUS configuration steps which is very urgently required .
    Thanks in Advance,
    Byomo

    Hi,
    Please find the Business Scenario Configuration Guide for Service Procurement.
    [http://service.sap.com/ibc-srm|http://service.sap.com/ibc-srm]
    Regards,
    Masa

  • Billing Type G2 configuration steps

    Hi,
    Can someone guide me through the configuration steps for creating a billing document type G2 for the following requirement.
    We have got negative quantity in the Invoice Receipt and for it we wish to post the Credit Memo (G2), and we will post this credit memo with reference to the Sales Order.  To achieve this solution i would like to have assistance on :
    1. How to configure the billing type "G2"
    2. How can this document type be listed in billing due list via VF04 ?
    3. How will the financial postings will effect after this invoice is generated ?
    Appreciate your kind help.
    Thanks
    Krishna

    Dear Krish,
    You are using credit memo type G2, which is not specifically made for third party item. Because the copy control settings that you need for this transaction are not available in OR-G2. In copy control OR-G2 at item category level TAN-G2N see the field billing qty.
    For third party scenerio, it should be 'IR qty/GI qty minus billed qty'.
    Now see the settings for OR-G2S copy control settings. TAS-TASG item category Billing qty field.
    As I told you before also. If you don't want to use G2S document, make a copy of it & then use it for credit processing. But don't make these changes for G2 doc type, because it is used for other process specifically return order, invoice correction request &  ... Changing in G2 will have adverse effects.
    You can't see status in order document as incomplete, but a negative Invoice Receipt Creates a billing index for credit memo.
    And then you can create the credit memo for customer. This is again based on the copy control settings.
    You can use report SDMFSTRP to create a list of all sales orders with third-party order items for which there are discrepancies between the quantities ordered, invoiced, canceled, or credited in Sales and the quantities ordered, invoiced or credited in Purchasing.
    To run this report, proceed as follows:
    Choose Tools -- ABAP/4 Workbench on the initial screen.
    Choose Development -- ABAP/4 Editor.
    Enter the report name SDMFSTRP in the program field and choose Execute.
    You reach the selection screen.
    Enter the interval of sales orders and the time period which you want to monitor.
    Choose Program-- Execute.
    Best Regards,
    Ravi

Maybe you are looking for