Future Date Restriction in Transaction J2I5

Hi,
Is there a possibility to restrict "Excise Register Extraction" for Future Dates in J2I5 T code?
Please assist on this...

Issue resolved by ABAP changes

Similar Messages

  • How to put data restrictions in transaction: GR55

    Hi,
    When I run a report with gr55 it shows figures for all profit center.I have defined a role which has profit centers restriction .
    but when ever user run gr55 he can see the data for the all proit center.
    How can i put data restriction on GR55.
    Anybody?
    Best regards,
    Bhavesh

    Hi,
    You can create a selection group that will serve as parameter in your GR55 report. Go to transaction code GRR2 and edit your form. You can set/tick the hierarchy node or variable in the profit center characteristic.

  • Restricting the Travel expense claims for future date

    Hi,
    We are configuring the BPs for ESS & MSS.  Currently we are on NW portal 7.0 ,SPS15 and ECC6.0 at the backend.
    Can anyone suggest us, how to restrict the users NOT to apply the Travel expense claims for the future dates (i.e.the portal system is expected to allow the users for the claims, till the current date or any past date but not any future date)  through portal.
    Currently, the system is allowing the users to apply the Travel Expense claims for the future dates also.
    Any help on this will be appreciated.
    Regards,
    Venu

    Hi Venu,
    I am not sure whether there is any configuration through which it can be achieved or not. But you can use Badi TRIP_WEB_CHECK for WebDynpro.
    Hope this will help.
    Thanks & regards
    Arun

  • Restrict Time Entry for Future Date in Portal

    Hi Gurus,
    My scenario is to restrict users from entering future date attendance in Portal.
    I know the configurations for restrictiong the user from scrolling to future week.
    But in my scenario users will be able to scroll to future weeks but should be restricted with an error message while trying to enter future time.
    Please let me know if you have any suggestions.
    Thanks.
    Regards
    Sairam Maharaj S
    Please search in the ESS forum as I remember responding to a similar scenario some time back. Thread is moved.
    ~Suresh

    Hi Srini,
    Thanks for your reply.
    I have achieved this by deselcting Release Future Time option. But user wants the future time to be restricted even from getting saved. Can I make changes to the default information message "1 out of 1 future time not released" to an error message so that the user will not be able to save. If so please let me know if this can be achieved from any configuration of messages or it should be done from the programming side.
    Thanks.
    Regards
    Sairam Maharaj S

  • Restrict posting in future date

    Dear All,
    During VL01N,VF01 system is allowign me to post documents in future date than the current system date.
    i want to put validation in system that it should not allow future posting date than current system date.
    pls guide.

    1)  To implement lock in Delivery
    The BADI definition name is LE_SHP_DELIVERY_PROC method name is CHANGE_DELIVERY_HEADER.  Here consider the field "Actual GI Date"
    2)  To implement lock in Billing
    Go to VTFL, select your item category for the combination of your delivery type and billing type and assign routine 11  for the field "Data: VBRK/VBRP"
    thanks
    G. Lakshmipathi

  • GRs created for schedule line of future date

    While making Goods Receipts using MIGO transaction, we are seeing tha GRs can be done for scheduling agreements having schedule line of future dates. Is there some way of restricting the GR upto to current date only. Meaning suppose if I have the following schedule lines:
    category of delivery date         delivery-date           schedule quantity
    M                                               01.2010                   100
    M                                               02.2010                    200
    M                                               03.2010                    150
    Currently the system is allowing to do GRs of quantity = 450 (100 + 200 + 150) in the month of February, 2010.
    But I want that while doing a GR in February, 2010 the system should allow to do GR of quantity 300 only (100 + 200). Please let me know how we can do so in the system.
    Regards,
    Pratima.

    Dear Veer,
    Your answer has helped in the MIGO transaction. Please let me know if something similar is possible for inbound deliveries also. Meaning like in MIGO transaction, I should not be able to make inbound deliveries (in xns VL31N) for schedule lines of future dates / months.
    Regards,
    Pratima.

  • Goods Receipt in future Date

    Hi,
    Please tell me if i can restrict the production order for doing GR for a future date???
    If today is 22/10/2009, and i am trying to give the posting date in MIGO as 25/10/2009 then system should restrict it.
    Thanks

    HI
    Check this Badi   WORKORDER_GOODSMVT
    In REM  i have achieved the same with the help of BAdi RM_BFLUSH_GOODSMVT.
    Check the first one with the help of ABAPer
    Regards
    Anupam Sharma

  • Posting in future date

    Dear expert,
        In our client , one of our user has accidently posted certain document in future date. Since the period are open for 2 months so any one can post the document in any of the date. I want to restrict user so that he will not be able to post the document in future date.
    Regards,
    Kapil.

    Dear sir,
    For that u  have to use the BADI.
    Badi to control the future posing date in migo : MB_MIGO_BADI.
    create in this badi it will work. in that interface you have to use is : STATUS_AND_HEADER.
    and write below code in the interface : STATUS_AND_HEADER.
    method IF_EX_MB_MIGO_BADI~STATUS_AND_HEADER.
    data : v_date like is_gohead-budat.
    if sy-tcode = 'MIGO'.
    v_date = is_gohead-budat.
    check v_date GT sy-datum.
    message : 'posting Date is future than system date' type 'E'.
    endif.
    endmethod.
    if any clarification please let me know.
    regards
    jrp

  • Stop Creation of Billing Document in Future date

    Hi Experts
    We create Billing Document in VF01 on basis of Outbound delivery, system create Billing Document in current date.
    but when we choose future date that time also system create billing Document l in future date .
    Issue : While create Billing Document in future date system should not allow to do the same.System should give error message while creating Billing document in future date.
    please reply as early as possible
    Regards
    Pash@SD

    Hello
    Refer following link:
    - Restrict from entering future billing date
    Thanks & Regards
    JP

  • SAP Posting to Future Date

    Dear Gurus
    SAP as an standard allows posting to a future date. Our client requirement is that we need to restrict the same so that  no user can post to a future date. What is the setting required to be done for the same?
    Regards
    Rahul Taneja

    Hello,
    There is no setting as such, unless you open 365 posting periods, which is not feasible, due to high maintenance.
    You can write a validation in the system GGB0 saying that (at document header)
    Posting data not greater than system date, say otherwise give ERROR.
    Assign this validation in OB28 for your company code.
    Hope this will solve your issue.
    Regards,
    Ravi

  • Set List datefield to future date and disable all date behind current date?

    Is it possible to set date to future date (atleast 2 week) and all prior  date should be grayed out . User will not able to select behind current. 
    Is it possible with OOB option. JQuery work around also fine.
    ItsMeSri SP 2013 Foundation
    ItsMeSri SP 2013 Foundation

    FutureDate - datatype will be Datetype as Calculated column formula 'Today+14'
    please 'Propose as answer' if it help you, also de-mark it if it didn't. Thank you!
    Also Place a validation rule as below which will restrict all previous date
    [FutureDate] > (Today()+14)
    User cant save that item if future date is not greater that today play another 14 days.
    Hope this will help !
    please 'Propose as answer' if it help you, also de-mark it if it didn't. Thank you!

  • How to restrict the transaction OB52 ?

    Hi guys.
    I need to restrict the transaction OB52 for Company Code. By default the transaction OB52 has no authority object to restrict it to the company code. Try it by adding the SU24 transaction object F_BKPF_BUK (check / maintain). When I create the security role by adding the transaction OB52, lifts my perfectly F_BKPF_BUK authorization object, added the company you will have the authorization, but does not work when I assign the Role to the user. The user will still leave change all companies and not the company you want to restrict.
    Thanks guys for the help.
    Desirée.

    Hi,
    Take the below into consideration for restricting table views for transaction like OB51, OB52 etc.... For your particular case I guess when user is running OB52 then it is providing data from table V_T001B
    First level authorization check will be S_TABU_DIS for access to table. Auth group will be FC31
    Now to drill down further restriction on line level for above table you need to use objects S_TABU_LIN. To use this object consider have look into the documentation for this object and 2nd step to read documentation in following path.
    SPRO --> Display IMG --> SAP Web Application Server --> System Administration --> Line-oriented Authorizations --> Define organizational criteria/Active organizational criteria
    Now in SPRO when you will create organization criteria then create it for field Posting Period Variant (BUKRS). This is one of the field for table V_T001B.
    Now activate it for table views V_T001B
    Now run OB52 again and it will ask for additional authorization for object S_TABU_LIN. In ORG_CRIT put the name of organization criteria you have created and in ORG_FIELD1 maintain value for relevent company code.
    This way will see only those lines where value for BUKRS will match with his/her user master for S_TABU_LIN
    This is quite big post. Will suggest you to go through documentation thoroughly rest are self explanatory.
    Arpan
    Edited by: Julius Bussche on Mar 28, 2010 10:22 AM
    Formatting fixed - please use "quote" tags and not "code" tags.

  • Bill Date restrict

    Hi,
    I need the billing date to be only in the current month period
    i.e. the user can create billing doc only in the current months period range if he wants to.
    ALso if this is not possible i need to restrict the user to not create the billing doc. in the future date
    but if he wants to do the billing doc in the past it should be from the current month date range
    Rgds

    Hi Laxmipathi,
    Thanks but this routine will give the inv date only as current date what i want is
    that the billing date should not be in the "future date" and if its in back date it
    should be only upto in the current month
    eg:Suppose today is 10th of september then user can't enter billing date as 11 or 12 sept
    but he can enter date upto 1st of september.
    I wanna map this in SAP.
    Rgds & thanks again

  • Provisioning a user in future date

    Hello,
    Creating a new user and provisioned to OID work properly.
    Now I would like to create a user with start date in the future. OIM when the value USR_START_DATE is on the future it update the USR_PROVISIONING_DATE too on the same future date but not execute the provisioning to OID and the USR_STATUS is "Disabled Until Start Date"
    If there any way to update the USR_START_DATE with a different USR_PROVISIONING_DATE and do the provioning as normal and keep USR_STATUS as Active.
    thanks
    TG
    Edited by: TG on 1-Nov-2010 9:48 AM

    Hello again,
    i'm using the Thor.API.Operations.tcUserOperationsIntf.createUser((java.util.Map arg0).
    arg0 will contain USR_PROVISIONING_DATE=today date and USR_START_DATE = to the future date.
    I apply what your propose and push the USR_PROVISIONING_DATE=today date and put it on the pre-insert in Users form.
    sorry it did not work, it change the value in USR_PROVISIONING_DATE to put the USR_START_DATE value and didn't provisioned
    thanks
    TG
    Edited by: TG on 1-Nov-2010 10:47 AM

  • The system failed to flush data to the transaction log. Corruption may occur.

    We have a windows server 2008 R2 Virtual machine and we are getting the following Warning Event.
    Event 51 Volmgr
    The system failed to flush data to the transaction log.  Corruption may occur.
    Any idea what is wrong with this server? Why this event is occurring?

    Hi Jitender KT,
    Before going further, would you please let me know the complete error message that you can find (such as a
    screenshot if you can provide)? Please check and confirm in Event Viewer if there other related event you can find, such as Event 57 and so on. Meanwhile, can you remember what operations you have done before the warning occurred?
    Based on current message that you provided, please run
    Chkdsk command to check if you can find error. The issue seems to be related to the storage device. Please refer to the following similar question.
    http://social.technet.microsoft.com/Forums/windowsserver/en-US/044b10af-c253-46de-b40d-ce9d128b83d7/event-id-57-source-volmgr?forum=winservergen
    In addition, please also refer to the following link. It should be helpful.
    http://www.eventid.net/display-eventid-57-source-volmgr-eventno-8865-phase-1.htm
    Hope this helps.
    Best regards,
    Justin Gu

Maybe you are looking for