Sales Deal - release status

Hi,
I have a question about the Sales Deals in SAP.
When we create a sales deal and release this sales deal it is not possible to change this status.
Is it normal that a Deal Status cannot be changed once it has ben released?
Or is this a customizing setting?
Kind regards,
Debby

No, you can't change it via config.
However the default value for release status  (when deal is created) is controlled via config, you can change it to start with A-Blocked, for example and then change it to released later, that's possible. The T code for Sales Deal config to change the default is VB(9.
However I guess you are more interested in the underlying condition records and not the 'deal' itself. If you want to change the status of condition records them separately, you can do so provided :
                                             1)   the condition record has release status in the key
                                             2)   the agreement has the release status released
Go through these documentation pieces:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/72/6e032d214411d29a0d0000e8a5bd28/frameset.htm
http://help.sap.com/erp2005_ehp_04/helpdata/EN/a4/af9e78e69611d2ace10000e8a5bd28/frameset.htm
Hope this helps.

Similar Messages

  • Release status for Sales deals

    Where do you set a release status for a sales deal, in the condition record or in the condition type. I was not able to find it in both the places?

    condition type.
    e.g K007 [customer with release status]
         KA00 = Cust/material with release status
    HTH

  • What's the status of the Sales Deal(KONA-BOSTA:Status of the agreement)?

    Hi Experts,
    I have a requirement that the status of the Sales Deal must be equal to "D" (Final settlement of agreement already carried out). Who can tell me how to implement this?
    Thanks & Regards.
    Kelvin

    Hello,
    The Agreement Status (KONA-BOSTA ) field can be set manually by the     
    user. The user can manually change the status field to 'A' or 'B'.       
    But the status  'C' or 'D' cannot be set manually.                                                                               
    Let me explain the flow :-                                               
    1) When the agreement is created , the  Agreement Status (KONA-BOSTA)    
    field is empty.                                                          
    2)If the user wants to go for settlement , then the status can be        
    directly changed to 'B' which means now the agreement is ready for       
    settlement.                                                              
    3)Now once the credit memo request (for settlement ) is created , the    
    Agreement Status (KONA-BOSTA) becomes automatically to 'C'. User cannot  
    manually change it to 'C' .                                              
    4)After that creation of final settlement invoice document , the         
    Agreement Status (KONA-BOSTA) becomes automatically to 'D'.User cannot   
    manually change it to 'D'.                                                                               
    It can be viewed as                                                       
    1) Agreement created   > Agreement Status     Open                        
    2)User can manually change to 'B'   > Agreement Status     'B'            
    3)Creation of CREDIT MEMO REQUEST    > System automatically changes the   
    Agreement Status     'C'.                                                 
    4)Creation of Final Settlement Invoice    > System automatically changes  
    Agreement Status     'D'.                                                                               
    User can only put 'A' or 'B' manually.                                    
    'A' is just for  check of settlemnt before release.                       
    I hope that the information are helpful.
    Regards
    Claudia
    If you are satisfied with the answer, please give Reward Points.

  • Reg.Sale order release from completed status

    Dear Experts
    We create new order type DOM for domestic sales and configured. And made one despatch for part quantity after despatching which got delevery completed automatically.I found it in sale order header "Status " tab.
    How to solve this problem. I want to make further despatch. Pls help
    thanks
    Rajakumar.K

    hi,
    if you have billed that partial quantity the system will show that
    the delivery is 'completed', but in order status it will be 'being processed' as
    u still have open items yet to be delivered.
    regards,
    anand

  • Condition Records in Sales Deal are displayed wrongly as u201CBlockedu201D

    Dear expert I need your help on issue
    Example Sales Deal # 123456:
    If Sales Deal is opened with transaction VB22 (e.g. to add a condition record or to amend one), then all condition records appear first as released (blank in column u201CSu201D status and u201CPu201D processing status):
    But just after a slight scroll within the screen, both columns get a value (u201CAu201D in column u201CSu201D and u201CDu201D in column u201CPu201D) and therefore appear as u201CBlockedu201D and u201CDouble Check Neededu201D:
    But if the SAVE button is pressed, then the system reports, that no changes have been done:
    Actually when we enter with transaction VB22, condition records are not blocked, but released:
    But when we scroll then changes happened even we scroll in Vk12 or VB22
    Condition validity u2013is 10.04.2008 to 25.05.2008
    Regds
    Alicia K

    I know it is late but still iam replying as i got a similar error as it might help others in the future.
    On Creation of VA01 the Condition records were not populate KONV is blank and so when i update condition records on an item i get an error as above. I first updated pricing Conditions on all the corresponding line items and then did the save in VA02 and the SO saved.

  • Sales deal

    hi
    Mine client is dealing with sale sdeal
    i am facing a small error
    when i am going to Vb22 for changing sales deal
    mine client is facing error as
    If Sales Deal is opened with transaction VB22 (e.g. to add a condition record or to amend one), then all condition records appear first as released (blank in column u201CSu201D status and u201CPu201D processing status):
    suppose if i make any changes and go to save this
    the message come
    But just after a slight scroll within the screen, both columns get a value (u201CAu201D in column u201CSu201D and u201CDu201D in column u201CPu201D) and therefore appear as u201CBlockedu201D and u201CDouble Check Neededu201D:
    But if the SAVE button is pressed, then the system reports, that no changes have been done
    Can u plz help me out
    if u dont understand plz give me ur amil id i will forward the screen shot on it
    Regards
    Powar

    Dear Tanveer,
    Sales deal is a Scheme (within the validity period of Promotion) which is being announced based on the Promotion announced by the company. As the company is dealing with a wide range of products you might have different range of discounts based on the type of product and the market demand. Sales deal baiscally helps you to map this.
    A sales deal defines a marketing deal for a certain product, depending on the setting it can be allcated to a higher level promotion.
    Special condition records can be allocated to sales deal, and if relevant the records also contain the number of promotion allocated to that sales deal.
    so basically u can assign no of promotions to a sales deal.
    lets say u have a Promotion called Winter sales:
    So to this Promotion you can attach couple of sales deal with Product line 1 ( jackets) and Product line 2 ( Sweaters)
    and to this Sales deals you can individually assign the Material discounts( like for wollen its 5% discounts, for Jeans its 2% discount)
    Hope this example clears your doubts on it.
    Regards,
    Rakesh

  • Condition Tables with Release status

    When we create condition tables, we have the option of creating them with release status or without release status. What is the difference? What is release status?
    Thanks,
    Venkat

    hi,
    The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
    Release status has the following characteristics:
    no entry: released
    A: blocked
    B: released for price simulation
    C: released for price simulation and planning
    The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
    Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
    When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
    A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
    The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
    If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
    The release status of conditions in an agreement can only be changed, if
    the condition record has release status in the key
    the agreement has the release status released
    Otherwise the condition record always has the release status of the agreement.
    The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
    If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
    The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
    source : Library.
    regards

  • Hai release status

    what is this release status in the condition table creation what does it indicate
    In pricing procedure det we found condition type  field what is the purpose of this
    thanks

    Hi Kishore,
    The release status for condition records in a sales deal enables you to limit the use of records that have already been created.
    Release status has the following characteristics:
    • no entry: released
    • A: blocked
    • B: released for price simulation
    • C: released for price simulation and planning
    The amount and significance of individual characteristics is defined using domain fixed values and can not be maintained.
    Maintenance of the release status is carried out in the sales deal itself (in the proposed values block), is transferred over to the condition records concerned and can then not be changed for these records.
    When setting up a new sales deal (with copy), a proposed value is suggested for the release status, which can be set up in Customizing for the agreement type.
    A record blocked for an application is treated in the access, as though it has been identified with a deletion indicator. It can however be recognized and displayed as such via the log functionality in Pricing.
    The characteristic Pricing Simulation is only used in the report SDNETPRO, which gives a net price list.
    If when maintaining individual condition records a sales deal is assigned to the condition record using the transaction VK12, the release status from the sales deal is used for this record. When changing the release status using this sales deal or changes to the sales deal, the user will be notified of any changes to the status.
    The release status of conditions in an agreement can only be changed, if
    • the condition record has release status in the key
    • the agreement has the release status released
    Otherwise the condition record always has the release status of the agreement.
    The processing status is always directly assigned to a release status. If conditions are assigned to an agreement, the agreement passes the release status on to all related conditions. The related processing status is then set accordingly.
    If you have several processing statuses assigned to a release status, the condition record receives the first (alphabetical) suitable entry as a processing status.
    The processing status, which the conditions have received indirectly from an agreement via the release status, can only be changed in the case of released agreements.
    In pricing, only those conditions are used, those have the release status 'released'.
    Reward points if it helpful
    Cheers,
    Govind.

  • What is the purpose of the release status in creating condition table

    hi gurus,
    can you please tell me the purpose of the release status and validity date in creating condition table for pricing?
    thanks,
    Paul

    Dear John
    The release status controls in which scenarios the condition records are found.
    If the status is set at 'B', for example, then the corresponding records  are taken into account during a pricing simulation, but are not used in current documents.
    The release status can only be maintained directly for agreements (sales deals). For condition records, this is done via the processing status.
    thanks
    G. Lakshmipathi

  • Planned value and Basis in Sales Deal VK11/12/13

    Hi Friends,
    I am creating Sale Deals condition type record in transaction VK11. I attached material in deal condition and when I go to "Detail" of that attached material item I am not able to see "Planned Values" frame and its component in screen. Could you please help solve this problem?
    Steps for Reconstruction                
    1. Execute transaction VK11
    2. Enter condition type as "Sales Deal" (KA00)
    3. In next screen enter appropriate " Sales Org", "DC", and "Customer"
    4. In the same screen look at "Customer/Material with release status" frame of table control
    5. Enter appropriate material and amount and hit <Enter>
    6. Select the item/row of the entered material and hit <F6> or click <Detail> icon in application toolbar.
    7. In the next screen the frame < Planned Values> and its fields like <Planned Basis> and < Planned Value> are missing.
    Does anyone know about this situation and can help on this?
    Thanks and Best Regards, Manoj

    Hi,
    Try this..Go to t-code V/04 -Change condition table of ur appropriate access sequence..input ur Table number which description u want to change and press enter...
    inside u can see table number on top and its description..near to this description u can find "propose/maintain text icon" enter ur description and save...
    Now try in VK11..
    Reg
    JJ
    Edited by: Jagsap on Jul 14, 2009 10:52 AM

  • How the sales order header status update?

    Hello,
    In the sales order header "STATUS" tab is there, under this status tab we can find OBJECT status if we click that object status it shows the Object number,Object category,status profile and status with status no. on which bases this status will update in the sales order header?
    my case is Status "10-xxxx" set automatically for some orders.
    Could you plz let me know on which bases, the status will be updated in the sales order?
    Regards|KS

    Hi
    SAPu2019S GENERAL STATUS MANAGEMENT FUNCTIONALITY
    General Status Management replaced order status management functionality in recent SAP releases (4.6C).  This discussion will address general status management, as this is how SAP allows user statuses for controlling objects in this and future releases.
    General Status Management applies to internal orders, project definitions, WBS elements, production orders and many other objects in SAP.  For the purposes of this discussion we will concentrate on status management for internal orders and WBS elements.  A list of all objects relevant for status management will be made available upon request.
    A status is an indicator that fulfills two functions.  First, it informs you that a particular status has been reached.  For example, an internal order has been created and released; a settlement rule has been entered; a particular business transaction has been executed, etc.  Second, it influences the business transactions you can perform for a particular status.  A status can allow a business transaction; allow a business transaction but issue a warning message; or prohibit a business transaction altogether.  If a warning message is issued it is up to the user whether the business transaction is carried out or not.
    Statuses can be used to control and communicate.  Statuses can be used in reporting (show me a report of all internal orders with a status of TECO, or technically complete).  Statuses can be used as selection criteria (select all internal orders with a status of CLSD, or closed).  Statuses can communicate the state of an object (ready for archiving, not ready for settlement execution).
    There are SAP standard delivered statuses that apply to all object types.  These are known as SYSTEM STATUSES.  CRTD, REL, SETC, TECO are examples of SAP standard system statuses.  SAP standard system statuses cannot be removed from use.  You cannot override the SAP system status with a user status.  You cannot change the behavior of an SAP system status.
    User statuses (or user defined statuses) exist in addition to SAP standard statuses.  User statuses are intended to augment or refine SAP standard statuses, not replace them.  There is no limitation to the number of user statuses that can be created.  Both system and user statuses influence business transactions in the same way.
    An object can have multiple statuses active at the same time.  A plant maintenance order can have released, preliminarily costed, work order printed and confirmed statuses all at the same time.  For SAP display purposes only one status can be displayed on the status line in master data screens, but it is possible to see all active statuses for an object at one time by drilling down into the master data screens.
    A STATUS PROFILE, or user status profile, contains individual user statuses and the business transaction rules defined for those statuses.  There is no limit to the number of user status profiles that can be maintained in SAP.  A user status profile is assigned to an order type or a project profile in configuration.  This user status profile is then defaulted into all objects that reference that order type or project profile.  A users status profile can be overwritten (or deleted) in an individual object (via native master data screens), but only if a user status has yet to be activated for that particular object.  Once a user status has been activated for that object the user status profile cannot be changed.
    HOW STATUS MANAGEMENT WORKS
    When an object (internal order, WBS element, production order) is created SAP assigns the system status CRTD.  MIT automatically releases the order, so the system status REL is also activated.  If there is a user status profile defined in the order type (or project profile) this is carried over into the internal order (or WBS element).  If not, only the SAP system statuses will apply to this object.
    When a user executes a business transaction for this object, SAP checks the user status to see if that business transaction can be executed without any additional influence from a user status, can be executed but with a warning message being issued, or cannot be executed at all.  SAP also checks whether the business transaction sets or deletes any other user statuses within the user status profile.
    A user status may also be maintained directly in the object master data.  Accessing the master data screens allows a user to manually maintain user statuses.  If necessary, an authorization code can be assigned to a user status to ensure that no unauthorized persons can change the status of an object.  Once changed, the new user status is fully active and acts no differently than if a business transaction set the user status.
    Status management and business transaction control only work with standard SAP transactions.  Z transactions will not show up on the business transaction list for an object.  The business transaction table is configurable, but SAP strongly recommends not changing that table.  SAP directly updates that table via support packs and it is often impacted during upgrades.
    Authorization codes / keys are available in user statuses.  The authorization code is checked only when user statuses are being set manually, from within the objectu2019s master data screens.  This ensures the user has the proper authorization to set that status for that particular object.  However, it is important to understand that SAP sets a user status in reaction to a business transaction it does not perform an authorization check.

  • Sales deal condition records creation

    I want create condition records in existing Sales deal.  I am getting data in the file format from other system.
    BAPI_PRICES_CONDITIONS is giving some problems and also it is not released, so we have thought not to use it.
    Can you please suggest any BAPI / program / FM to add conditions in sales deal.

    Hi,
    Sales deal condition records creation,
    Regarding on this query, follow this below link
    Link of Sales Deal to Condition records
    The above link will helps to your requirement
    Regards,
    Sekhar

  • Sales order released from Credit block, but Purchase Requistion not created

    Hi,
    In third party sales scenario based on Scheduline Line category configuration purchase requistion creates when the order is created. If order is blocked for credit check then purchase requistion will not be created until order released from credit.
    Here my scenario is
    I have two users like A and B. When A releases the order from credit block by using transaction VKM1, Sales order releasing from credit and creating Purchase requistion. But, if the order is released by B, Sales order is getting released from credit but purchase requstion is not getting created.
    There is no issue from security side, we activated trace and analysed everything it is not security issue.
    Thanks and Regards
    Alokam Chandra Sekhar

    Hi Lakshmi,
    Thanks for reply. I followed your instructions, pls find my observations below.
    1. Can you check the below settings:
    What is the Credit status in the header status tab page of the sales order for the B's sales order?
    Is it "Not approved or releasedu201D If it is not approved, you might have released the sales order in VKM3, but you might not have saved it.
    Reply: We are releasing order through VKM1 and after releasing the order the status is showing as "Released".
    2. Did you use the same material for B's Sales order? If it a different material check the Item category and Schedule line category whether these are same with A's sales order.
    Reply: Both the orders has same information, like material Item category and scheduline category
    3. Check in the Schedule line tab page --> Procurement button whether you have maintain vendor, Source determination and Info record.
    Source list has been verified through ME03 transaction and vendor data maintained correctly.
    I really appreciate your time and efforts on this.. looking forward some more suggestions...
    Thanks and Regards
    Alokam Chandra Sekhar

  • Problem in data upload using pricing conditions with sales deal

    hi...
    i have to upload following fields -
    Condition Type
    Condition Table
    Valid from
    Valid to
    Sales deal
    Amount/Rate
    Currency / %
    Pricing Unit
    Pricing UoM
    Sales organization
    Distribution channel
    Sold to Party
    Material Number
    Material Pricing Grp
    Batch number
    Buying Group of Sold-to
    Customer
    Customer Group
    CustomerHierarchy 01
    CustomerHierarchy 02
    CustomerHierarchy 03
    CustomerHierarchy 04
    CustomerHierarchy 05
    Division
    Sales Order Type
    Sales Document Type
    End user
    Material Group
    Tax Classification Material
    Payer
    Plant
    Price Group
    Price list type
    Pricing reference material
    Prod. Hier -1
    Prod. Hier -2
    Prod. Hier -3
    Prod. Hier -4
    Prod. Hier -5
    Product hierarchy
    Region of Dly Plant
    Sales district
    Sales group
    Sales office
    Sales unit
    Ship-To
    Shipping point
    Buying Group of end user
    Tax classification for customer
    Type of Transaction
    Scale Basis1
    Scale Rate1
    Scale Basis2
    Scale Rate2
    Scale Basis3
    Scale Rate3
    Scale Basis4
    Scale Rate4
    using  XK15  t-code and SALES DEAL is the major concern.
    1)  First i used   RV14 BTCI , that is a standard report for uploading the pricing conditions. But by using this all fields are updating except SALES DEAL becoz this is not present in the structures (like- BKOND-1, BKOND-2, BKOND-3 etc) that is used in RV14BTCI program. I searched other structures also but SALES DEAL is not present there.
    2) Second i tried to find out some Function module that is containg SALES DEAL and i found two FMs - IDOC_INPUT_COND_A and BAPI_PRICES_CONDITIONS.....but
    a) the FM - IDOC_INPUT_COND_A is used with ALE and where third party is involved, so we require control data and status data for  this I dont have this. so we cant use it.
    b) and the FM BAPI_PRICES_CONDITIONS is also not working for SALES DEAL....by using this it is also not uploaded becoz some mandatory information related to sales deal like- sales organisation, distribution channel are not present in this FM.
    3) to upload this we can use the BDC recording method.....but the problem is - there are almost 15 condition types and based on these conditions almost 20 - 25 condition tables are there for every condition and based on the every table different screen sequence are there.....so if we go for BDC recording...than we have to make 325 recordings.....also not feasible solution.
    so plz give the suggestions for this problem and check my efforts also may be i missed something that can be a solution.
    Thanx in advance for all.......plz help.....

    Hi Jitendra,
    Goto RSA3 trans in the source system. Check if are able to extract the data.
    If so then replicate the DS once in BW system. Activate all the DS, transfer rules etc & try to load it again.
    Hope this will solve your problem!
    Regards,
    Pavan

  • Release status for condition records

    Hello,
    When ever a user changes the price in the condition record, I want the price to be in blocked status initially. Sales document should only pick tht price when it is release by the concerned person.
    Could you tell me how is the authorization given to some users based on the processing status.
    Thanks and Regards,
    Pavan P.

    I tried to make the Processing status as blank and tried to save it and assigned the release status "Blocked". This doesn't seem to work. Any other ideas?

Maybe you are looking for