Issue regarding condition pricing date as system date for some condition types in sales order

Hi
I have already created a sales order on 30.04.2014. Today I am adding new line item to sales order in VA02 transaction. in this order new line items condition pricing date for conditions JEX2,JECX should show as 12.06.2014. But currently it is showing as 30.04.2014. I need condition pricing date as system date for above conditions.
Regards
prashant

Hi
When I am changing pricing date VBKD-PRSDT in sales order header . It is changing the condition pricing date for all. Sales order is created on 04.06.2014. I have added line item 150 on 14.06.2014.
After adding line item 150 , there I have changed the pricing date as 14.06.2014. in sales A tab of item 150. But still it is taking from Sales order header date as 04.06.2014 for all conditions. But my requirement is for line item it should take as system date for some conditions like JEX2,JECX& JA1Y but for other conditions it will take as Order creation date. Please suggest. I have also attached screen shot below. please go through it.
Regards
PK
Sales order header change mode VA02
Here pricing date VBKD-PRSDT = 04.06.2016
Item change mode
I have added new line item 150 on 14.06.2014
Changed the condition pricing date to 14.06.2014 & saved
After saving I have gone to Va02 screen of line item 150
& there I have gone to condition pricing date field from item condition tab
for JEX2 condition type but still here condition pricing date is showing as
04.06.2014 as below.
Condition pricing date
My requirement is like this
For some particular conditions like JEX2  condition pricing date will take as system
date instead sales order creation date when I will add a new item 150 on
14.06.2014.but for other conditions it will show as order creation date for the
same line item 150 .

Similar Messages

  • Defaulting the Document date to system date while GR cancelation via MIGO

    Hi All,
    While canceling a GR via MIGO transaction, i manually change the Document date to system date, but after posting still the document date is showing the original document date when is was posted.
    Is this is the standard behavior?
    I have a requirement to make this date default to system date. But it is not considering the date which we centered in the screen.
    Kindly help me to resolve this issue.
    Srinu Kaduri

    Hi,
    while doing GR cancellation,system will take only system date for example today will be in the document date.
    With Regards,
    Jaheer

  • Purchase Requistion Relase Date as System Date.

    Dear Experts,
    I need some information on purchase requisitions.
    1.our users are changing  release date manually  the date which they are releasing the Purchase requisition.
    can we make the release date as system date,what type of configuration i needed to do that..
    2.mass un release of purchase requisitions.
    3.mass deletion of purchase requisition and mass deletion of purchase requisition line items
    please suggest me
    Thanks in advance
    Regards,
    Varun

    1) In spro first check the Field selection group assigned with PR document type...in most of the cases it is NBB...now go to spro@mm@PR@Define screen layout at document level@double click on NBB@double click on Deadline monitoring@here make Release date as display so that user will not be able to change it in PR.
    2) Check if the same is possible in ME55 or BAPI for release with object type BUS2105
    3) Check of BAPI for pr with function module BAPI_REQUISITION_DELETE with your ABAP person.
    Regards,
    Indranil

  • MIR7  changing posting date to system date when period is closed

    Dear Experts,
    For FI park document, there is a setting in customising to set the posting date to system date during posting when the posting period in FI is closed. Is there a way to do  this in LIV for MIR7 to set posting date to system date when the MM period is closed?
    Amit

    Hi,
    Please, have a try to use the following BAdi:
    MRM_HEADER_DEFAULT
    Transaction CODES: MIRO, MIR7 and MIRA.
    Detailed description of this BAdi can be found in IMG Help.
    (SPRO -> Materials Management -> Logistics Invoice Verification -> Maintain Customer Exits and Business Add-Ins -> Maintain Business Add-Ins for Invoice Verification)
    Hope it helps.
    Regards,
    w

  • Purchase Requistion release date as system date

    Dear Experts,
    Our Requirement is the top management want to know time taken to release a purchase requisition,means the duration
    between purchase requisition creation date to release date.
    here user are manually changing the release date to system date to know duration exact time duration between the creation date  and release date,so user requirement is the release date should be system date so he can easily understand when the requisition is released.
    we are thinking that,if we make the release date as system date,please suggest me.
    Thanks in Advance.
    Varun

    Dear Madhu,
    1.)     Whenever you are creating a new PR system will automatically take that PR creation date as system date.
    2.)     All the releases in SAP System will be recorded  as Item/Header change and system will maintain their history in Item/Header change details
    3.)     If your requirement is to track the duration between creation, release of levels it can be very much possible by creating a quary it self.
    Regardsu2026
    Srini Rao

  • Load Grid with data from System.Data.DataTable

    Hi all.
    A have a System.Data.DataTable e need load a grid with data from this DataTable.
    How Load a Grid with data from System.Data.DataTable?

    Hi Francisco,
    actually i don't think that you can use a .NET datatable to fill a business one grid.
    the business one has it's own datatable.
    in c# it would look like this:
    oForm.DataSources.DataTables.Add("MyDataTable");
    ((SAPbouiCOM.Grid)(oForm.Items.Item("grid").Specific)).DataTable = oForm.DataSources.DataTables.Item("MyDataTable");
    oForm.DataSources.DataTables.Item(0).ExecuteQuery("SELECT Field FROM [dbname].dbo.TABLE");
    ((SAPbouiCOM.Grid)(oForm.Items.Item("grid").Specific)).CollapseLevel = 1;
    ((SAPbouiCOM.Grid)(oForm.Items.Item("grid").Specific)).AutoResizeColumns();
    ((SAPbouiCOM.Grid)(oForm.Items.Item("grid").Specific)).SelectionMode = SAPbouiCOM.BoMatrixSelect.ms_Single;
    good night
    lg David

  • How to Avoid Duplicate Pricing Condition Types In  Sales Order and Billing

    Hi SAP Gurus
    I have a requirement in Pricing (Sales and Distribution). We have  issue duplicated condition types in Sales order and it causes wrong posting in to accounts.
    I want make them inactive duplicated Condition type in Sales order and Billing Documents.
    Please advice me how to make inactive status to duplicated Condition types
    Thanks  in Advance.
    Ravikanth

    Hi
    You can use Exclusion Group
    You can define 2 Groups and include 1 condition type in each
    and define exlusion procedure
    A   Best condition between condition types                
    B   Best condition within the condition type              
    C   Best condition between the two exclusion groups       
    D   Exclusive                                             
    E   Least favorable within the condition type             
    F   Least favorable betweent the two exclusion groups     
    you can use Exclusive to set your condition type or as per your requirement
    Regards
    Jitesh

  • Forgot to put ZPNT (Penalty condition type) in sales order

    Dear Expert,
    We have created sales order and billing document has been sent to customer,after that we came to know tht we forgot to put ZPNT Condition type in sales order. Now i want to create another sales document with reference to billing document, in which only ZPNT Condition type will be appear (not other condition) and thn will create billing document with reference to new sales order so that ZPNT amount goes to the right ledger A/C......Is it the right process to solve this problem if yes thn please advise me how to fonfigure the system.
    Regards
    Parul Deshwal

    hi Parul,
    rather than doing this which is quite complecated process
    saying complecated because, when u do Copy from billing to sales document all condition will appear and might be there r some mandatory conditions in pricing procedure which you can not remove.
    Above all, IF your condition ZPNT value is based on some other conditions then also it will not be possible for you to calculate it correctly.
    there is one more possible way by creating DEBIT NOTE with reference to sales order but again you might have to face above mentioned problems
    So better you follow standard and easy method
    1. Reverse the billing document if PAYMENT is not posted
    2. Reverse the Delivery (if any)
    3. add your condition type to sales order for line item and create it
    Regards

  • About hide special condition type in sales order condition screen

    Hi all,
        I have such requirement:
        Customer want to hide some condition type in sales order condition screen.
        I have tried the authrization object :V_KOND_VEA  but it only controll the master data level
        and the special still show on the condition table.
        I have also find any user exit in SD module:
        USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
        But it looks like a system modification, and need the modification key.
        So, is there any solution such as enhancement or configuration to meet this requirement?
    Many , thanks.

    Check this thread where similar requirement was discussed
    [Condition Type |Condition Type]
    thanks
    G. Lakshmipathi

  • Manual Condition type in Sales Order

    Hi,
    i need to enter a manual condition type in sales order which should come in % and the value should not come or it should come as zero, Is there any way to make that manual condition value as Zero in sales order.
    Ragu

    Raghu,
    Pls check the OSS notes 392668, that will solve your problem.
    The same pasted here for your reference. However, I advise you to download it and then read due to inconsistent formatting here.
    Reward if this helps.
    When you create documents in which the standard pricing is used to determine condition records as well as to calculate a pricing result, the display and entry of manual entries is not clear in the relevant condition screen (screen 6201 in the SAPLV69A or SAPMV61A programs for releases prior to 4.6A).
    This note explains the interaction of manual entries with the attributes maintained in the pricing procedure and in Customizing of the condition type.
    Other terms
    KAUTO, V/06, V/08, KAEND fields, KOZGF, PRICING_CHECK, LV61AU08, XKOMV_ERGAENZEN_MANUELLE, LV61AA53, manual entries, MANU
    Reason and Prerequisites
    In the pricing Customizing, the following fields affect the manual entry of complete condition lines or individual condition rates:
      Description        Technical name              Maintenance transaction in SD
      Access sequence    KOZGF                  V/06 and V/07
      'Manu'            KAUTO                  V/08
    Depending on the characteristic of the mentioned fields, the pricing condition screen appears as follows:
      KAUTO   | KOZGF    | Condition record existing on DB? | Result
      Initial | Initial   | -                                | (1)
      Initial | Existing  | No                              | (2)
      Initial | Existing  | Yes                              | (3)
      Set     | Initial   | -                                | (2)
      Set     | Existing  | No                              | (2)
      Set     | Existing  | Yes                              | (4)
    Result (1)
    A condition line is set for the relevant condition type [KSCHL]. The 'Condition rate' field [KBETR] does not contain a value, but is ready for input. The displayed line serves as an input help or a template for the manual entry.
    Result (2)
    No relevant condition line is set on the pricing condition screen, in other words, the condition type is missing.
    If you enter the condition type manually without entering a condition rate in the same processing step, you get a 'template line' as described in (1).
    Result (3)
    A suitable condition record that exists on the database is set with amount (= normal, automatic determination).
    Both the 'Condition origin' indicator [KHERK] and the 'Condition control' indicator [KSTEU] are set to 'A'.
    If you create another line with this condition type and enter a condition rate not equal to zero, a line is set with this condition rate.
    The 'Condition origin' indicator [KHERK] as well as the 'Condition control' indicator [KSTEU] has characteristic 'C'.
    If, on the other hand, you create another line and enter a condition rate of zero (or do not enter any condition rate) and the condition record that exists on the database has a scale, the system sets the condition rate according to the achieved scale level. If zero is to be set as the condition rate even if scales exist, then use modification Note 179354. If no scale is maintained, then the system always sets zero as the condition rate.
    In these cases, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] characteristic 'A'.
    Result (4)
    No relevant condition line is set on the condition screen, even though a condition record suitable for the access sequence exists on the database. The pricing analysis displays the message "Manual condition (Condition record exists)". If you enter the condition type manually without entering a condition rate in the same processing step, the record that exists on the database is set. If a condition record has a scale, the system sets the condition rate of the first scale level independently of the achieved scale level.
    In this case, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] has characteristic 'A'.
    Thus, the setting variant leading to result (4) serves to suppress the setting of automatically found condition records into a pricing result. However, you can add the maintained record to the already determined pricing result by entering the relevant condition key.

  • Flowing of the Condition  type from Sales Order to invoice

    Dear All,
    I'm facing a problme in the copying the condition types from Sales order to Invoice.
    The details are as mentioed below:
    I have a Condition type CONC and made the Copy of the Condition typs as ZDIS.So that CONC's value will be debited and ZDIS' value will be credited in the FI..
    But ALL the condition types which i have mentioed including tax and discounts condition types are copying from Sales order to invoice.Except CONC.
    I have checked all the copy controls,i'm sure those are OK.Bcoz other condition types are working perfectly fine.
    What could be the reason for this???
    Will be any setting for on condition type level for copy controls???
    Please Guide me its URGENT.
    Thanks
    Vinay

    hi
    from which condition type u have copied this CONC , can u pl elaborate more on this.
    and just write what is exact scenario and whats going wrong?
    in copy controls check for pricing source and pricing type.
    regards
    mandar

  • User Exit for eliminating double condition type in sales order

    Sir,
    In SE38,  Program SAPMV45A,  I am using user exit ( Userexit_pricing_prepare_tKomp )  to avoid double entry
    of condition type like PR00 in sales order . But i am not getting how to write code.
    Please, help me how to write code in user exit.
    thanks,
    Manoj.

    Thanks for replay.
    Sir, I want to impliment it in sales order (VA01 OR VA02 )
    for pricing  . Here I want to avoide double  condition types like PR00, packing forwarding, frieght ....etc
    in  sales order pricing.
    Here i want to give logic that codition type is already exit and you canot enter same condition type
    again. means if condition type is already exit then system should not allowed to enter again the same condition type
    in sales order pricing.
    Thanks
    Manoj.

  • How can prevent duplication of condition types in sales order??

    How can prevent duplication of condition types in sales order.
    While we want Amount field Changeable by user.
    Please give me solution.

    Dear Rohit,
    Can you explain your scenario in detail with an example or any screen shot so that we will help you in easy way ...
    Regards,
    C.B Reddy

  • Condition recordscoz for some condition type4s

    hi all,
    how can we maintain condition records for some condition types,For eg...
    MWST
    SKTO
    FRA1
    ZA01
    RA01
    HB01
    RB00..etc..apart from MEK1..coz for some condition types this t.code dose`nt work
    Edited by: MANI ROOPA SD/MM on Feb 28, 2008 12:06 PM

    Hi,
    The condition types you have mentioned are supplimentary conditon types and they afre dependent on the main conditons ( Like PB00 ), so they don not have any access sequence.
    Regards
    Reward Points if useful

  • How to compare a given date with System date?

    The date input for me is of type String and it is in the format
    String s = "1900-00-00 00:00:00.000";
    I need a helper method that will take the above string as input and it should return Boolean value depending on the following condition.
    Date should be less than or equal to current date and greater than the date prior to the date 50 years of current date.
    Thanks in advance...

    I got it.
    String date = "3000-03-19 12:34:56.000";
    Calendar c = Calendar.getInstance();
    Calendar c1 = Calendar.getInstance();
    Calendar c2 = Calendar.getInstance();
    Date d = new Date();
    Date d1 = new Date();
    Date d2 = new Date();
    c1.set(Integer.parseInt(date.substring(0,4)),Integer.parseInt(date.substring(5,7)),Integer.parseInt(date.substring(8,10)),Integer.parseInt(date.substring(11,13)),Integer.parseInt(date.substring(14,16)),Integer.parseInt(date.substring(17,19)));
    c2.set(1,c.get(1)-125);
    d = c.getTime();
    d1 = c1.getTime();
    d2 = c2.getTime();
    System.out.println(d1.compareTo(d));
    System.out.println(d2.compareTo(d1));
    System.out.println(".....");
    System.out.println(d1.compareTo(d));
    System.out.println(d1.compareTo(d2));
    if(d1.compareTo(d)<=0 && d2.compareTo(d1)<=0)
    System.out.println("Success");
    }

Maybe you are looking for