Scheduling dates In Orders.

Dear SAP Gurus,
I have maintenance plan in which in scheduling parameter I  gave late completion Tolerance as 10% and early completion tolerance as 10%.Call Horizon is 90% and Scheduling period is 12 Months.The maintenances plan will be scheduled and I got order date as 2 days before the actual date and two date after the actual date.
In general If the actual date is 20; In order I will get Basic Start date as 18 and Basic Finish Date as 22.
My client wants same date i.e.20 as Basic Start and Finish Dates.So I have to remove the tolerances.I done it but still; the 2 days factor is there in every order.
Is there any setting to remove it? Wat can be the possible reason For It?
Please Comment as soon as possible.
Thanking You
Waiting for your reply.
With Best Regards
Pankaj U. Nimkar

Thank You Very Much RameshChandra and John;
With Your so may options I am able to solve the problems.
The Problem is solved now and the exact date is coming there as per requirement.
With Best Regards
Pankaj U. Nimkar.

Similar Messages

  • PO - Schedule Date

    HI all
    I have one query regading Schedule date (Purchase order).
    While creating PO , CUSTOMER fills the schedule Date for ITEMS to be delivered.
    Now when Vendor Sends confirmation,He states DELIVERY date in confirmation.
    How many days difference is possible/allowed in SCHEDULE DATE and DELIVERY date.
    For example: if SCHEDULE date is 12th NOVEMBER 2006
    WHAT could be last possible DELIVERY DATE that a vendor can fill while confirming for that PO?
    Thanks in Advance.
    Vijay Raheja

    Hi Viajay,
    I don't think SAP have any real control over the delivery date specified by the vendor.
    It can not be enforced in a standard system.We can use user exits to control this behavior.
    SAP has given the user exit to determine Earliest Delivery Date (GR Check (PO Only) ) EXIT_SAPLEINR_004 at the time of GR.
    Hope this helps you to some extend.
    Thank you.
    Regards,
    Karun.M

  • Sales order item data & sales order schedule data

    Hello,
    I have a Sales Orders cube which is pulling data from two DSOs (one for sales order item data and the other for sales order schedule data). The common fields between these two DSOs is the Sales Order number but in my cube I have dual entries for each Sales Order document (item and schedule info).
    Example of how the data looks now:
    Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . . Act GI Date
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10
    1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15
    2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 . . . . . . . . 01/02/2000
    How do I merge the data on the Sales Order number in the cube so it looks like below?
    Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . . Act GI Date
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10 . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15 . . . . . . . . . .2 . . . . . . . . 01/02/2000
    Many thanks,
    Matt

    > Hello,
    >
    > I have a Sales Orders cube which is pulling data from
    > two DSOs (one for sales order item data and the other
    > for sales order schedule data). The common fields
    > between these two DSOs is the Sales Order number but
    > in my cube I have dual entries for each Sales Order
    > document (item and schedule info).
    >
    Two previous remarks:
    1) If you need to report on very detailed data consider doing an info-set joining both datastores. 2 reasons why:
    - not a good idea to report on very detailed information (sales order, GI dates) on cube level, if you have a scenario with lots of data. You end up with big dimension tables a poor report times;
    - there are better alternatives, like drill-through from cube query to DS query with report to report interface or Datastore-based reporting...so...
    With this solution you do not need to change the data model, I think, but test to be sure. See if the reporting times are acceptable. If not...
    2) First confirm your requirements, because what you show in your example as "to-be" have details that do not make sense, probably..
    - if you have more that one schedule line for each item then you would have many times the item information like material/price;
    - if not or if you could cope with that, then you can consider:
    2.1) create a new DS that agregattes from the previous on, with the same key of sales order item; do you have schedule line kf's? if so you these KF's should be additive in DS update; But if you may have more one scheduled line for 1 item then you have to decide what to do with the GI data (keep the last one posted, use code..) and other characteristics.
    2.2) update the shedule line datasource to the sales order item DS; same comments apply.
    2.3) maintain the missing data in the cube update rules from sheduled lines DS. Using code, refer to the respective item in the order item ODS. You would have to make sure that DS's data are correctly activated before updating the infocube.
    What solutions to choose?
    2.1 is better in terms of flexibility and architecture...because you could re-arrange the new DS to answer future needs, without loosing the 1st line DS's data;
    2.2 choose if data volumes and disk space are a concern...
    or
    2.3 it's OK, but i do not like it because of what explained in point 1...
    Message was edited by:
            Miguel Costa

  • Sales order schedule dates

    Hai,
         I have created a sales order, whenever we created a SO it displays possible delivery dates, we enter that possible delivery date in delivery creation, I want to know where those schedule dates are getting stored when we save a sales order. I have seen for those in VBAK and VBAP tables but i havent found those schedule lines can anybody say where these dates are getting saved
                                                                                    Thank you in advance
                                                        Srinivas

    When the order quantity is available as on the delivery date and confirmed then there will be only one schedule line created. If stock is not available then as delivery date the confirmed quantity will be 0 and another schedule line will be created as on material availability date where the order quantity will be confirmed.
    Its not necessary that there are only one or two schedule lines...but there can be more than two also.
    Regards,
    GSL.

  • Sales order schedule date is a (working) day before Scheduled ship date

    In MRP/MPS planning, the forecast consumption is occuring for all sales orders at a date (sales order schedule date) which is always a working day before the Scheduled Ship Date (SSD). What is the logic?
    Time fences are not used.
    E.g. Sales order is scheduled to ship (SSD) on 30th Nov, in forecast set > Forecast items > Consumptiion > Detail, the sales order schedule date is a day before SSD.

    Hi,
    This is a complex issue; best solution is by using APO/GATP.
    If not, then in ERP only, the second best is:
    1) Work with assembly processing in SO, meaning that a production/planned order is automatically created in the customer order during order creation.
    2) Then, after the order is created it is scheduled, and the delivery date proposal is based on that.
    3) Now you can check in the order that there are no capacity overloads, and all capacity required to produce on the proposed date is available. If yes, you're done. If not, it gets a bit complex, since you actualy need to switch to capacity planning, do capacity leveling and dispatch (PP), and the you get a new feasible schedule proposal based on that.
    APO/GATP could do all that automatically!
    Regards,
    Mario

  • Sales Order Item Data & Sales Order Schedule Lines

    Hello,
    I have a Sales Orders cube which is pulling data from two DSOs (one for sales order item data and the other for sales order schedule data). The common fields between these two DSOs is the Sales Order number but in my cube I have dual entries for each Sales Order document (item and schedule info).
    Example of how the data looks now:
    <b>Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . .  Act GI Date</b>
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10  
    1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 . . . . . . . . 01/01/2000
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15  
    2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 . . . . . . . . 01/02/2000
    How do I merge the data on the Sales Order number in the cube so it looks like below?
    <b>Sales Order . . Item Cat. . . Article . . . Net Price . . . Delivery . . .  Act GI Date</b>
    1. . . . . . . . . ...TAN. . . . . ABC123. . . .10 . . . . . . . . . .1 . . . . . . . . 01/01/2000 
    2. . . . . . . . . ...TAN. . . . . CBA321. . . .15 . . . . . . . . . .2 . . . . . . . . 01/02/2000  
    Many thanks,
    Matt

    Hi Matt,
        Its no possible If you are maintaining data at Order Level.
    Try to introduce one more ODS/DSO in between ODS's and CUBE by keeping Sales Order only key field. Load data from both DSO's in required fields only. Then PUSH delta to CUBE. In this why you can maintain 1 record. Try to compress cube(with delete Zero Record Rows) to delete unnessasary records.
    Hope it Helps
    Srini

  • Scheduling Date issue in Assemble to Order Scenario

    Hi Friends,
    I am facing a Weird issue with Production order Scheduled dates created automatically after creation of Sales Order for configurable material.
    Our availability check is set to check  open Purchase orders, for one component the delivery date in the PO is 20.12.2011, currently at the time of creation of SO the availability check shows this component as a missing part and committed date as 20.12.2011.
    Now the issue is that for one type of customers when the SO is saved, the production order gets created with basic start and finish date of 20.12.2011 with a status CRTD PRC MACM SETC.
    But with another customer group it creates the Production order with today's date basic start and finish date, with a status CRTD MSPT PRC  SETC.
    Now since in both the cases the Material is same and also the components are exactly the same, the only difference is the customer, I am unable to make out why it is happening.
    I am basically a MM  Consultant so am unaware if there is any standard setting relating to customer or something relating to that which is causing such  a issue in scheduling date of the Production Order.
    Regards
    Chandra Shekhar

    Hi Vivek,
    Yes, the availability check is working in both the cases, when I create the sales order, I key in the Configurable material code, then do the configuration, after that system does availability check, in both the cases the result of availability check is same with one component marked as a missing part, available date as 20.12.2011.
    One more thing if I try to view the Production order at the time of SO creation before saving it, the Production order shows today's date, but when I save the SO, and do Credit release, the actual Production order gives different scheduling date based on customer. Just wondering what could be affecting based on Customer, is there any other field present in Customer master which could alter the date.
    I also saw today's scheduling note in some of the cases, but its not coming up in all of the orders created with today's date and moreover the same components are getting scheduled for 20.12.2011 also for diff customer.
    I am afraid I can't provide any screenshots for this as am not permitted to publish any screenshots of the client.
    Regards
    Chandra Shekhar

  • Basic and scheduling  dates & time calculation in process order creation

    Hi guru's,
    i have one requirement, i need to calculate and display the basic and scheduled dates & times based on the given input i.e material , plant , process order type , quantity , UOM and scheduling type ( for corresponding scheduling type user will provide either start date or finish date ) using RFC. can  u plz provide any function module for this purpose or logic for calculating the same  , as i am working on version 4.7ee .
    Awaiting for a quick response.
    Regards,
    Madan

    Dear Rohan,
    1.Check the length of break timings defined in the resource that is assigned in the phase.
    2.Check in OPUZ whether for the process order type and plant combination whether scheduling is to include the break time also
    (whether the check box for scheduling with breaks) is included.
    Check and revert back.
    Regards
    Mangalraj.S

  • Editing of scheduled dates in Process Order Operations

    Hello,
    I have a requirement, in which the client would like to change the Scheduled dates in the operation details of a process order.
    In the header screen of a process order, if we change the basic start / finish dates (depending on forward or backward scheduling), and reschedule the process order, the process order is rescheduled, with the new dates.
    The client's requirement is, they should be able to change the Scheduled dates in the tab "Operation - Dates", of the "Operation overview" screen, in a process order. Normally the field is not editable, and the system calculates the dates, based on the start / finish dates, entered in the process order header.
    I would like to know, what is the way out, to meet this requirement.
    Thanks.

    Hi,
    As every body else is explaining it is not possible for standard SAP ,  as of normal business or any business scenario why would a client want to change the operation dates from Production order ( still not understood.....)
    There are two options to do that:
    1) Copy the whole transaction ( programmes ) into some Z - transaction and in the programme you can change the object ( CO_VG_OPR_*) from being grayed out.
    This will alllow you to change the dates.
    2) you can go for enhancement with the following FM
        BAPI_ALM_ORDER_MAINTAIN
    I suggest you to clear these things with client.These things require more of ABAP work.
    And as said changing the standard behaviour of the system can cause performance issues.
    Please close the thread if satisfied.
    prakash

  • Updating Scheduling data for Purchase Order

    Hi,
    I need a function module which can update the scheduling data for purchase order in EKET table. Normally we create Purchase Order as a reference from purchase requisition through BAPI_PO_CREATE1. That time it takes care of all the scenarios. But as per the requirement I want to create a PO which is created from more than one Purchase Requistions so I can't use the said BAPI. But still I am using this BAPI and after creation is completed I am updating the Requistions. The same scenario is taken care in ME59N, but I can't copy that code because of some requirements. So could any one please give me the idea to replicate the same functionality with any function module or other ways.
    Thanks
    Somnath paul

    try to pass all u sheduling related fields to POSCHEDULE and make sure u have enabled POSCHEDULEX along with sheduling related fields .....also (if no changes  are there  leave it with space )...
    this will definetly update not only eket table ....it will update every table regarding to purchase order,ekpo,ekko,eket ...etc
    Example of population of BAPI interface in the Function
    Parameter: POHEADER
    COMP_CODE            =                    1000
    DOC_TYPE             =                    NB
    ITEM_INTVL           =                    00001
    VENDOR               =                    0000001000
    PMNTTRMS             =                     0001
    PURCH_ORG            =                     1000
    PUR_GROUP            =                     001
    CURRENCY             =                     EUR
    Parameter: POHEADERX
    COMP_CODE            =                     X
    DOC_TYPE             =                     X
    ITEM_INTVL           =                     X
    VENDOR               =                     X
    PMNTTRMS             =                     X
    PURCH_ORG            =                     X
    PUR_GROUP            =                     X
    Parameter: POITEM
    PO_ITEM              =                     00001
    MATERIAL             =                    100-100
    PLANT                =                    1000
    STGE_LOC             =                    0001
    QUANTITY             =                    15.000
    TAX_CODE             =                    V0
    ITEM_CAT             =                     0
    ACCTASSCAT           =                    K
      Parameter: POITEMX
      PO_ITEM              =                    00001
      MATERIAL             =                    X
      PLANT                =                    X
      STGE_LOC             =                    X
      QUANTITY             =                    X
      TAX_CODE             =                    X
      ITEM_CAT             =                    X
      ACCTASSCAT           =                    X
      Parameter: POSCHEDULE
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      DELIVERY_DATE        =                    02.12.2002
      QUANTITY             =                    6.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
      DELIVERY_DATE        =                    03.12.2002
      QUANTITY             =                    5.000
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0003
      DELIVERY_DATE        =                    04.12.2002
      QUANTITY             =                    4.000
      Parameter: POSCHEDULEX
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0001
      PO_ITEMX             =                    X
      SCHED_LINEX          =                    X
      DELIVERY_DATE        =                    X
      QUANTITY             =                    X
      PO_ITEM              =                    00001
      SCHED_LINE           =                    0002
    Parameter: POACCOUNT
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    15.000
    GL_ACCOUNT           =                    0000400000
    COSTCENTER           =                    0000001000
    CO_AREA              =                    1000
    Parameter: POACCOUNTX
    PO_ITEM              =                    00001
    SERIAL_NO            =                    01
    QUANTITY             =                    X
    GL_ACCOUNT           =                    X
    COSTCENTER           =                    X
    CO_AREA              =                    X
    Parameter: POCOND
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    001
    COND_TYPE            =                    PB00
    COND_VALUE           =                    79.900000000
    CURRENCY             =                    EUR
    CURRENCY_ISO         =                    EUR
    COND_UNIT            =                    KG
    COND_P_UNT           =                    1
    CHANGE_ID            =                    U
    Parameter: POCONDX
    ITM_NUMBER           =                    000001
    COND_ST_NO           =                    000
    ITM_NUMBERX          =                    X
    COND_TYPE            =                    X
    COND_VALUE           =                    X
    CURRENCY             =                    X
    CHANGE_ID            =                    X
    Parameter: POPARTNER
    PARTNERDESC          =                    OA
    LANGU                =                    EN
    BUSPARTNO            =                    0000001100
    PARTNERDESC          =                    GS
    LANGU                =                    EN
    BUSPARTNO            =                    0000001200
    PARTNERDESC          =                    PI
    LANGU                =                    EN
    BUSPARTNO            =                    0000001000
    reward points if helpful....

  • Basic / Scheduling dates are calculated for both main orders and Collective

    How the Basic / Scheduling dates are calculated for both main orders and Collective orders?
    when in master data we have given different value of in house production time for both the orders.

    Hi,
    The basic dates are calculated from the data mentioned in the Material Master - In-house production time days, either lot size dependent or lot size independent.
    The scheduled dates are calculated from the timings maintained in the routing.
    In the configuration for Scheduling parameters for the order type - Adjust scheduling - the dates can be adjusted.
    Kindly revert back if you need any further clarifications.
    Warm regards,
    Umesh Poojari

  • Scheduling dates from sales order not confirmed

    Hi All,
    I have configured CRM_APO_ECC integration in system. But getting few error on CR$M-APO side. Can you please sugest on these queries:
    1. order entered in CRM, ATP check is triggered in GATP & confirm dates & vendor (plant) populated with 2 schedule lines. But when I save the order, I get RED signal on item details tab, also I could not see order in RRP3.
    2. Second query is regarding RBA. I have configured location sub rule. But when the qty in initial plant is less, it does not give me the substitute location, rather it proposes me later date considering the checking horizon maintained in product master.
    But when I manipulate the same material with error (i.e. by removal of ATP group in product-loc master), and create order for same material, I can see the rule in place when ATP is triggered and can see 2 line items on ATP screen, first showing RED light (for which ATP grp isnt maintained) and 2nd is one with substitute location. In this case, it works. Where is my config missing?
    Please help me with these 2 situations.
    Many thanks,
    AP.

    Hi All,
    I got answer to this (i.e. query # 2), rule based plant was not available when triggered from CRM.
    Now i can see it, Solution is - Activation of preselection activation key. I activated it in APO Requirements profile for CRM & also in Check instructions.
    Thus I can see all sub plants.
    However, my 1st query is still under search. My scheduling dates are not getting confirmed. Following is the scenario:
    initial plant (USA1) has no stock in RRP3, but still showing green & accepting orders:
    When I chose alternative plant USA2 where I have stock, 2 scheduling lines are generated, 1 for initial plant & 2nd for USA2. There is no error message till then. And when I hit save, I get availability confirmation error, schedule line is not confirmed.
    After saving, only one line item remains, and plant is USA1, i.e. initial where there is not stock.
    Can you please suggest what config might be missing?
    Thansk,
    AP.

  • BAPI PROCESS ORDER Creation u2013 can the SCHEDULE Date/Time be specified?

    I am currently using BAPI_PROCORD_CREATE to create a Process Order from an inbound IDOC.  This works well, when I pass the following fields:
    BAPI Parameter ORDERDATA
    ORDER_NUMBER      Process Order number (EXTERNAL)
    MATERIAL      Material to be produced
    PLANT              Plant
    ORDER_TYPE      Order Type
    BASIC_START_DATE Start Date
    BASIC_START_TIME Start Time
    BASIC_END_DATE   Basic End Date
    BASIC_END_TIME   Basic End Time
    QUANTITY         Process Order Quantity
    QUANTITY_UOM     Quantity Unit of Measure
    However, I have a requirement to also specify the SCHEDULED Start Date (GSTRS) and End Dates (GLTRS), but the BAPI parameters do not the SCHEDULE Dates to be specified.
    I have also used the functions CLOI_CHANGES_UPL_31 and CLOI_CHANGES_UPL_45 to create Process Orders successfully, but neither of these allow for the SCHEDULE dates to be passed in.  
    Does anyone know how I might be able to achieve such a result?
    I am trying to avoid the use of CALL TRANSACTION on COR1, so would be grateful if anyone has any thoughts.   
    In the mean time, Iu2019ll ask the business if it would be possible to apply any rules by whereby if we specified a BASIC_START_DATE, whether it would be able to derive the correct schedule date accordingly.
    PPu2019s not one of my better modules, so apologies if whatu2019s been asked above is a stupid question!
    Alistair

    HI...
    Pls chk in scheduling control for detailed scheduling in T code OPUZ. and change the scheduling type forwards to forwards in time and backwards to backwards in time.
    Now when ever you would create the order system would ask the scheduling dates either start or finish in stead of Basic dates.
    Instead of using BAPI you could make a simple LSMW pogram. It would talk 5 min.
    This is a standard SAP functionality to select Basic dates because SAP consider all master data for scheduling like Schedule margin key.
    I think It would help you.
    Regards
    Vivek

  • Delivery schedule dates are coming in Past dates

    Hi Friends,
    In the Scheduling Agreements the delivery schedule dates are coming in the past dates even tough the scheduling agreements are having new schedules. There is also open quantities there for the scheduling agreements.
    please kindly explain me what is the delivery schedule date in Scheduling Agreement.
    Thanks in advance.
    Regards,
    Kannan M

    Hi Khan,
    Just check this thease might be the reasons to get correct the delivery schedule.
    To access a delivery schedule, mark a scheduling agreement item and choose Goto ® Item ® .
    The following data is displayed in the delivery schedule tabstrip:
    ·        Delivery schedule number and date
    ·        A wide range of standard cumulative quantities
    ·        Delivery information
    To display deliveries for the delivery schedule, choose Deliveries on the delivery schedule tabstrip.
    In scheduling agreements involving external agents, the system displays deliveries made to the customer by external agents as consignment issues.
    ·        Correction delivery information
    To display or create correction deliveries, choose Corr. delivery on the delivery schedule tabstrip.
    ·        An analysis function
    ·        Information at a glance
    To display a summary of delivery schedule data, choose Short disp. on the delivery schedule tabstrip.
    ·        Schedule lines
    Choose DlvSch.Hdr on the delivery schedule tabstrip to access the delivery schedule header. The following data is displayed here:
    ·        Information on quantities received by the customer
    ·        Information on the customer fiscal year and cumulative quantities reset due to a year change
    ·        A wide range of cumulative go-ahead quantities
    ·        Notes on the delivery schedule
    Correcting Cumulative Delivered Quantities
    Prerequisites
    You correct cumulative quantities in scheduling agreements:
    ·        In case of returns
    ·        When there has been a processing error
    ·        When there has been a year change
    ·        When you are transferring initial quantities from a legacy system into the SAP System
    To do this, you create a correction delivery within the delivery schedule itself. This delivery is not relevant for requirements planning, shipping, goods issue, or billing.
    Correct cumulative quantities only when the customer has not posted goods receipt.
    Procedure
    To create a correction delivery (document type LFKO):
           1.      Choose Corr. delivery on the delivery scheduletabstrip.
    The system displays a dialog box in which you enter a:
    -         Correction delivery date
    For help on deciding where you want to position the correction delivery, choose Display. The system lists delivery dates in chronological order.
    -         Correction quantity
    Enter a negative correction quantity by placing a minus sign after the quantity.
           2.      Choose Enter and save the scheduling agreement.
    Result
    When you save the correction delivery, the system updates the cumulative quantities in the delivery schedule.
    To display correction deliveries, choose Deliveries on the delivery schedule tabstrip, or  Environment ®  Display document flow.
    Example
    Your customer returns 200 pieces of material from a delivery made on 7/10 because of damage during transport. Several other deliveries have been made before you prepare the correction delivery, so you view a list and choose an appropriate date. In this case you decide on 7/14 because it occurs after the delivery on 7/10 and before the delivery on 7/15.
    Regards,
    Murthy V.N

  • Show Order Qty, Shipped out Qty, Open Qty for each SCHEDULE line of Orders?

    HI Experts,
    I need to show the
    Order Qty
    Shipped Qty
    OPEN quantities(Un Shipped quantities)
    at each SCHEDULE line level for all Sales orders.
    So, am pulling the date like,
    Order qty from VBEP-WMENG and
    Open Qta from VBBE-OMENG
    Then am calculating like,
    Shipped Qty =  VBEP-WMENG - VBBE-OMENG
    But, still some SCHEDULE lines r missing in VBBE table!!
    so, pls. let me know that,
    1) Is there any other alternative ideas for my requirement?
    2) Why some SCHEDULE lines r missing in VBBE table?
    thanq

    Try this function module:
      CALL FUNCTION 'RV_SHIPMENT_VIEW'
        EXPORTING
          shipment_number       = tknum
          option_tvtk           = 'X'
          option_ttds           = 'X'
          language              = sy-langu
          option_items          = 'X'
          option_stawn_read     = 'X'
          option_segments       = 'X'
          option_partners       = 'X'
          option_messages       = 'X'
          option_package_dialog = 'X'
          option_flow           = 'X'
          activity              = 'V'
        IMPORTING
          f_vttkvb              = vttkvb
          f_tvtk                = tvtk
          f_tvtkt               = tvtkt
          f_ttds                = ttds
          f_ttdst               = ttdst
        TABLES
          f_vttp                = i_vttpvb
          f_trlk                = i_vtrlk
          f_trlp                = i_vtrlp
          f_vtts                = i_vttsvb
          f_vtsp                = i_vtspvb
        EXCEPTIONS
          not_found             = 1
          delivery_missing      = 3
          OTHERS                = 99.

Maybe you are looking for