Open to Buy configuration steps in SAP IS Retail

Hi Guru's,
Let me know about open to buy configuration steps in SAP IS Retail.
Thanks in advance.
Regards,
SP

Hello All,
Delete the plant / Site complete details and put in one transport and do the import & export.
Thanks.
Edited by: krishna cherry on Jul 26, 2010 3:28 PM

Similar Messages

  • Explain withholding tax partial pament configuration steps in sap

    Hi,
    This ramu .explain withholding tax partial pament configuration steps in sap .

    Hi,
         Please follow the steps for tds-partial payments
    In the following activities you make the settings for withholding tax. (SPRO-F.AC(NEW)-F.AC.GLBSETTINGS-WITHHOLDINGTAX-EXTENDED WITHOLDING TAX.
    The SAP R/3 System provides you with two procedures for processing withholding tax:
    "Standard" and extended withholding tax.
    "Standard" withholding tax is the procedure that has always been supported by the system. It offers you the following features:
    Withholding tax for accounts payable
    Withholding tax calculation during payment
    Withholding tax code per vendor line item
    Extended withholding tax provides the following additional features:
    Multiple withholding taxes per customer or vendor line item
    Withholding tax calculation for partial payments
    Enhancements in withholding tax calculation
    Withholding tax calculation during invoice entry and during payment
    Regards
    Sridharshetty

  • Help me Bonus Buy configuration STEPS

    Hi
    Friends
    send me bonus buy configuration steps ineed to configur to my  client
    Regards
    Suresh

    Hi Suresh,
    Step by step procedure for configuring Bonus Buy:
    follow the condition technique for this.
    1. Maintain the condition table.
    2. Maintain access sequence and assign the condition table to the access sequence.
    3. Maintain the condition type and assign the access sequence to the condition type.
    4. Maintain pricing schema - this is nothing but the procedure for bonus buy.
    5. Activation of bonus buy determination - as per sales area, DPP and CPP. Same like pricing procedure.
    6. Maintain the condition record for bonus buy.
    If you go transaction VBK1 you can create Bonus Buy based on the below mentioned std discount types
    BB01-Bonus Buy :Price
    BB02-Bonus Buy : Absolute Discount
    BB03-Bonus Buy : % Discount
    BB04-Bonus Buy : Free Goods
    From SD point of view
    In the SPRO path Go to Sales and Distribution>Basic Functions>Bonus Buy
    Reward points pls.
    Regards,
    Govind.

  • Error at DB downtime configuration step in SAP installation

    Hello Gurus,
                  While installing CRM IDES  5.0 I am stuck at DB downtime configuration (step 9). After shutting down MSSQL server services are not automatically started. In usual case it should be. Its giving "could not start the MSSQLSERVER" service on host. And my MSSQL services are not starting either it is giving Named pipes provider, error:40 - could not open a connection to SQL Server. If any one faced similar kind of problems sugguest on this.
    Regards,
    Murali

    Check your event log why your database is not coming up.
    Markus

  • Okb9 configuration step

    < MODERATOR:  Message locked.  Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. try and search first.>
    hi guys,
    pls send okb9 configuration step in sap r/3 6.0 version.
    step by step.
    thanks
    rohit agrawal

    < MODERATOR:  Excellent answer. >
    Hi,
    Actually, there are not so many 'steps'. Just go to OKB9 and define your default CO objects for the G/L accounts.
    Regards,
    Eli

  • SAP Netweaver 7.3 PI Configuration Steps

    Hi all,
            We have installed SAP Netweaver 7.3 PI in a separate server with server configuration of ,
           Windows 2008 64-BIT Server Enterprise edition.
           MS SQL Server 2008
           SAP Netweaver 7.3 PI
           24 GB RAM & 500 GB HDD.
           I request you to provide us the configuration steps for PI 7.3.
    Regards,
    Gopinath M.L

    Hi Gopinath,
    I am not sure if I got the point, but you can perform the post installation automatically by executing templates within NWA. But of course there is also a detailled description available how to do it manually (eg in case of problems). You can find these documentation under:
    http://help.sap.com/saphelp_nw73/helpdata/en/48/a9b8c87e28674be10000000a421937/content.htm
    Was this what you are searching for?
    best regards,
    Markus

  • Configuration steps SAP NW04 - BW 3.5

    Hi,
    Beside the material found in the SAP NW04 installation master guides, I would like to draw an exhaustive list of the required steps to configure a brand new SAP BW 3.5 system.
    Assuming that one has just finished the technical installation, what are the necessary configuration steps and tips?
    Any help on that topic would be greatly appreciated and rewarded - needless to say!
    Best regards,
    LauQ

    Hi!
    sap* is mostly used for installation steps and not for system copy..
    if your system is just newlyinstalled and if you have no clients in your system other then the one delivered by sap like 000 .....then you need to copy 0000 via SCCL and then start doing tasks in this new client with a user who has simmilar authorizations as sap*
    so you will maintian profile parameters only after the copy...and then define logical system
    <i>"actually these steps are more clearly explained in installation guide for 3.0 than in instguid for 3.5"</i>
    hope it helps
    with regards
    ashwin
    Message was edited by: Ashwin Kumar Gadi

  • SAP DBM Configuration Steps

    Hey Experts
    Please let me know the basic configuration steps involved in SAP DBM. I'm from SD background and new to DBM.

    Hi Hussain,
    for needed settings in a DBM system find details in the configuration guide for DBM 8.0 which is the newest DBM version.
    In online help DBM you can find more informations as installation master guide, release strategy note and application help and the configuration guide:
    SAP Dealer Business Management 8.0 – SAP Help Portal Page
    Best regards
    Joachim

  • Step by step complete configuration document for SAP PM module

    Can any body send me step by step complete configuration document for SAP PM module. If possible screen shots also. I will be highly obliged.
    Indranil Chatterjee
    Thanks in Advance.

    Indranil,
    It is not permitted for forum members to send documents to one another.
    It is also expected that members will first perform their own research before asking for help.  Did you search through SAP Help?
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/b2/4df35d51b811d192fb0000e829fbc6/frameset.htm
    Best practices? 
    http://help.sap.com/bp_bl604/BL_IN/html/Content_Library_BL_EN_IN.htm
    Best Regards,
    DB49

  • SAP CIN configuration step - by- step material.

    Dear Experts,
    could you provide SAP CIN configuration step - by- step material.
    thanks & regards,
    vijay

    Hi,
    Please provide the same for me. I m also new in this.
    Thanks
    Kavita

  • How to configure oracle to SAP NETWEAVER DEVELOPER STUDIO STEP RAGARDING

    hi
    can u help me on this
    i got problem
    regarding configuring oracle to sap NetWeaver developer studio what i have deployed any thing studio
    that would reflected to database
    bye

    Hi,
    Check this,
    WebDynpro and Oracle Connection
    WebDynpro and Oracle Connection
    Regards,
    Vijayakhanna Raman

  • 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

  • Proxy configuration steps

    hai all,
    if anyone have the proxy configuration steps please explain step by step.
    Thanks
    Sam

    Hi,
    R3 side
    SLDCHECK
      Use this transaction to access the SLD of R3.
    If SLDCHECK runs into error check following RFC destinations in SM59
      To connect to the SLD you need 2 types of TCP/IP connections.
      1)LCRSAPRFC:-
          In this you require the gateway host(ip address) and gatewayservice(sapgw[system no.])
          You also need to give Program ID.
          Entry of corresponding Program ID must be maintained in SMGW.
          IN SMGW Click GoTo->logged on Clients.
          If entry is not there for corresponding XI.
          Create a communication channel in XI, pointing to R3 and give a Program ID
          in the channel. Once the channel is activated, corresponding Program ID will
          appear in SMGW.
      2)SAPSLDAPI:-
       In this case follow the same porcedure as for LCRSAPRFC.
       As far as the Program ID is concerned te procedure mentioned above is for
       Customized RFC's
       The RFC destinations mentioned here are both standard RFC's
       Hence for these two RFC's no need to Create Program ID's. you just need to
       change the System ID of the Program ID.
       Both these RFC's are maintained in the J2ee server of XI.
    SLDAPICUST
      Create an entry for respective XI server
      requires hostname, port username and ip.
      Can have multiple enteries for different servers.
      But you can check only one entry.
      based on the entry that is checked, respective SLD API will be triggered from
      SLDCHECK.
    SPROXY.
       In this transcation you can check the Proxies.
       If the proxies are not activated (i.e. if the message interfaces are not active)
       then you need to maintain one G type RFC destination pointing the resepctive XI server.
       In the G tpye RFC destination give the Ip adress of the XI server in the target
       host and set the path prefix as /rep.
       Goto SPROXY->Goto->connection test-> click on the table SPROXSET.
       In this table maintain enteries for ADDRESS_ONLY_FROM_SPROXSET and IFR_HTTP_DEST
       The values corresponding to these enteries will be the G tpye RFC destination.
    In order to connect R3 to the Integaration server you need to maintain H type
    The default RFC is XI_INTEGRATIONSERVER. In you need to give the Target host entry as the
    Ip address and Path Prefic as.../sap/XI/engine/?type=entry (this you can get from SXMB_ADM of XI)
    You can also create the H type RFc of your own.
    goto SXMB_ADM(r3) and open Integration engine configuration.
    Goto edit->change global configuration and give the RFC dest name like this:-
    Corresponding Integration server:- dest://{h-type rfc destination}
    If you do not want to create RFC destination you can directly give
    the Integration server address(that you can obtain from SXMB_ADM of XI) in the
    Corresponding Integration server field.
    Regards,
    Sami.

  • Error while creating and opening a ERP sales order in SAP CRM

    Hi,
    I am getting an error while creating or opening a ERP sales order from SAP CRM.
    "Creation of the ERP Transaction failed" this is the error i'm getting while creating. when i try to open an existing sales order I'm getting a dump.
    Attached the dump screen shot. From the dump analyasis it seems the transactions are not loaded through LORD framework.
    The RFC connection seems to fine as i have tested accessing an ECC RFC FM through a sample program and its successful..
    please help..
    Thanks
    Krishna

    Hello Krishna,
    Did you get a solution to this? I have the same dump message.
    As a matter of fact, we already use ERP Sales Order and it works fine. But I have recently configured a new sales order document type, and the dump occurs only for this new Z order type.
    Thanks a lot,
    Luis.

  • 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

Maybe you are looking for