Material Staging date and Committed Date

Deal all,
At the outset,Wish you a very happy new year.
As per my understanding the material staging date should always be equal to Committed date in the Delivery schedule of the PO. Also the pick date in the delivery would be the staging date of the PO.
In which scenario, the staging date could differ to the committed date? What may be the reasons to have different staging and committed date in PO?
Appreciate your speedy responce.
Regards,
Shashidhar

it would not make much sense to have 2 fields for staging date and committed date if they should  always be equal.
The F1 help of each field describes it already a little bit more.
Staging date is the date by which sufficient quantities of the item must be available for picking to begin.
Dependend on the volume that must be picked and staged it can take days to have everything in the staging area so that it can be delivered from there.
In the customizing of shipping point you can enter days/hours needed for picking and packing.

Similar Messages

  • Statistics-relevant delivery date and Committed date in Stock Transport Ord

    Dear Friends,
    Kindly tell me how the System Calculate  the Statistics-relevant delivery date and Committed date in Stock Transport Order.
    Thanks & Regards
    T.Arulvanan

    Hi Jürgen,
    in the Include MM06EFET_ETT_FUELLEN there is following coding:
    IF NOT im_sd_scheduling IS INITIAL.
            PERFORM ett_sd_scheduling USING 'X' 'X' eket *eket
                                      CHANGING eketdata_sd.
    In the FORM ETT_SD_SCHEDULING
    there is the following coding:
    Datum oder Uhrzeit geändert --> Versandterminierungsdaten zurücksetzen
      CLEAR c_eketdata_sd.
    Lieferdatum und Uhrzeit setzen
      c_eketdata_sd-eindt = i_eketn-eindt.
      c_eketdata_sd-uzeit = i_eketn-uzeit.
    So the internal table c_eketdata_sd is cleared and only the delivery date and time are updated, but not the statistc relevant date.
    It seems to me like standard behaviour of SAP.
    Best regards
    Georg

  • Doubts in statistic Delivery Date and Commited Date in STO PO

    Hi,
    I would like to know statistic delivery date and Commited Delivery date in STO PO.
    2 different type of date is displaying STO PO like;
    1. We are getting statistic delivery as "09.02.9999" and Commited Date as "09.02.2011"
    2. 1. We are getting statistic delivery as "09.02.9999" and Commited Date as "09.02.9999"
    Could you explain, where we are maintiang those date and how it is displaying in PO Delivery schedule line?
    Thanks.
    Dhanush.

    When you create a PO, then the statistical delivery date is set equally to the delivery date.
    the statistical delivery date is automatically changed if you change the delivery date before you have outputted the PO.
    After you outputted the PO, the statistical delivery date has to be changed manually by the user if he changes the delivery date.
    the idea behind this is because of the vendor evaluation, the vendor evaluation is done with the statistical delivery date.
    as long you have not printed/faxed/mailed the PO to your vendor, then the statistical delivery date is changed automatically with a delivery date change.
    But after a transmission you always have to ask yourself, who is responsible for the change in the delivery date.
    If it is you, then you have to change the statistical delivery date to the new delivery date manually, to avoid that the vendor gets valuated against the wrong delivery date. But if it is because the vendor cannot meet the delivery date, then you change the delivery date to have an accuracy for planning, but you keep the old date in the statistical delivery date to valuate the vendor against it.

  • Confirm date and Commitment date

    Hi all,
    What is Commitment date and Confirm date and what are the differences between both .
    Thanks in advance
    Regards
    SK

    Commitment date is the date on which the goods or materials have been promised/committed to deliver.
    Confirmed date is the date on which the goods/materails was delivered or received.
    Hope this helps.
    Reward points for all helpful answers.
    Thanks,
    Balaji

  • SAP Inter company PO Checking rule and commitment date

    Hello there,
    I am trying to understand the commitment Qty and commitment Date on the NB type PO between two different plants.
    I have a setup where my Plant1 buys from Plant2 and Plant1 takes 100 days to get it from Plant2.
    Plant2 will source it from Vendor1 and takes 200 days for the Vendor1 to supply to Plant2.
    Plant 2 does not have any stock today, the stock from Vendor 1 will arrive only on 6/10/2015, there is an Open PO for Vendor2 for GR will be done on 6/10/2015. So on 6/10/2015, there will be a stock of 2500 units.
    No other requirement exists in MD04 for this material in Plant 2.
    Plant1 is raising a PO for Vendor Plant2 on 3/27/2015 for 1000 units. The planned delivery date is 100 days on Plant1 Material Master. So the delivery day is shown on PO is 100 days from now which is 7/5/2015.
    Considering the fact that Plant2 is receiving 2500 on 6/10/2015, why wont SAP commit to the Qty. When I do the availability check, it does not consider the 2500 units coming in from PO and from CO09. The checking rule does not consider the Purchase Order Qty.
    Now, here is where I need clarification.
    The checking rule says not to consider Purchase Order in the in/out movement, So when I play around with this check I was able to commit the Qty on the PO. When I take out the check it will not commit the Qty and puts the commitment date based on the Plant 2 planned delivery time ( the time Plant 2 takes to buy it from the supplier).
    It makes sense so far, however when excluding Purchase order to be considered for my purchase order availability check and when I remove the 200 days from Plant2 material masters planned delivery date and then create a purchase order, my PO is committing the QTY, how is this explained? or am i having some bad setup somewhere.
    Same exact checking rule i.e excluding purchase order, everything else constant.
    Scenario 1: Qty committed on PO when Planned Delivery time on Plant2 is zero days
    Scenario 2: Qty not committed on PO when Planned Delivery time on Plant2 is 200 days
    Can someone assist me to understand this. thank you

    Anyone thoughts? thanks

  • Regarding : Material document data and PO data do not match (Plant)

    Hi Gurus,
    Please go through this BAPI program.
    While uploading it is giving an error ' Material document data and PO data do not match (Plant) '.
    Please help regarding this issue.For all Other moment types it is working fine except this 351 moment type.
    dATA: i_excel TYPE truxs_t_text_data. "work table for excel upload
    DATA: BEGIN OF it_itab OCCURS 100,
          docdate(10),
          postdate(10),
          mvt_type(3), "Movement Type
          plant(4), "Plant
          lgort(4),
          pur_doc(10), "Purchase Document No
          po_item(3), "Purchase Document Item No
          material(18), "Material Number
         delnote(16),
          erfmg(13),
          uom(3),
         lfmng(13), "Quantity
          batch(10) TYPE c,
          vfdat TYPE vfdat,
          END OF it_itab.
    DATA: it_goodsmvt_head TYPE TABLE OF bapi2017_gm_head_01      INITIAL SIZE 100,
          it_goodsmvt_code TYPE TABLE OF bapi2017_gm_code         INITIAL SIZE 100,
          it_goodsmvt_item TYPE TABLE OF bapi2017_gm_item_create  INITIAL SIZE 100.
    DATA: wa_goodsmvt_head LIKE LINE OF it_goodsmvt_head,
          wa_goodsmvt_code LIKE LINE OF it_goodsmvt_code,
          wa_goodsmvt_item LIKE LINE OF it_goodsmvt_item.
    DATA: w_mat_doc  TYPE bapi2017_gm_head_ret-mat_doc,
          w_year     TYPE bapi2017_gm_head_ret-doc_year.
    DATA: BEGIN OF it_errmsg_goodsmvt OCCURS 10.
            INCLUDE STRUCTURE bapiret2.
    DATA: END OF it_errmsg_goodsmvt.
    DATA : obj_type LIKE bapiache09-obj_type,
           obj_key  LIKE bapiache09-obj_key,
           obj_sys  LIKE bapiache09-obj_sys.
    DATA: v_date1 TYPE sy-datum.
    DATA: v_date2 TYPE sy-datum.
    DATA: w_lines TYPE i.
    DATA: errflag.
    SELECTION-SCREEN BEGIN OF BLOCK bk1 WITH FRAME TITLE text-100.
    PARAMETERS: p_file TYPE  rlgrap-filename.
    SELECTION-SCREEN END OF BLOCK bk1.
    AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_file.
      CALL FUNCTION 'F4_FILENAME'
        EXPORTING
          field_name = 'P_FILE'
        IMPORTING
          file_name  = p_file.
    Start-of-selection processing
    START-OF-SELECTION.
      CALL FUNCTION 'TEXT_CONVERT_XLS_TO_SAP'
        EXPORTING
          i_line_header        = 'X'
          i_tab_raw_data       = i_excel
          i_filename           = p_file
        TABLES
          i_tab_converted_data = it_itab[]
        EXCEPTIONS
          conversion_failed    = 1
          OTHERS               = 2.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      LOOP AT it_itab.
        REFRESH it_goodsmvt_head.
        REFRESH it_goodsmvt_item.
        CONCATENATE it_itab-docdate6(4) it_itab-docdate3(2) it_itab-docdate+0(2) INTO v_date1.
        CONCATENATE it_itab-postdate6(4) it_itab-postdate3(2) it_itab-postdate+0(2) INTO v_date2.
        wa_goodsmvt_head-pstng_date = v_date2.
        wa_goodsmvt_head-doc_date   = v_date1.
       wa_goodsmvt_head-ref_doc_no = it_itab-delnote.
    wa_goodsmvt_head-pr_uname   = sy-uname.
        APPEND wa_goodsmvt_head TO it_goodsmvt_head.
    Maintain it_goodsmvt_code
        wa_goodsmvt_code-gm_code    = '04'.
    Maintain it_goodsmvt_item
    *LOOP AT it_itab.
    IF wa_goodsmvt_item-po_number IS INITIAL.
        wa_goodsmvt_item-po_number    = it_itab-pur_doc.
        wa_goodsmvt_item-move_type    = it_itab-mvt_type.
        wa_goodsmvt_item-MOVE_PLANT      = it_itab-plant.
        CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
          EXPORTING
            input  = it_itab-material
          IMPORTING
            output = it_itab-material.
        wa_goodsmvt_item-material     = it_itab-material.
        wa_goodsmvt_item-stge_loc     = it_itab-lgort.
        wa_goodsmvt_item-po_item      = it_itab-po_item.
        wa_goodsmvt_item-entry_qnt    = it_itab-erfmg.
        wa_goodsmvt_item-ENTRY_UOM_ISO    = it_itab-uom.
       wa_goodsmvt_item-po_pr_qnt    = it_itab-lfmng.
        wa_goodsmvt_item-batch        = it_itab-batch.
        wa_goodsmvt_item-expirydate   = it_itab-vfdat.
       wa_goodsmvt_item-NO_MORE_GR   = 'X'.
        wa_goodsmvt_item-mvt_ind      = 'B'.
        APPEND wa_goodsmvt_item TO it_goodsmvt_item.
        CALL FUNCTION 'BAPI_GOODSMVT_CREATE'
          EXPORTING
            goodsmvt_header  = wa_goodsmvt_head
            goodsmvt_code    = wa_goodsmvt_code
          IMPORTING
            materialdocument = w_mat_doc
          TABLES
            goodsmvt_item    = it_goodsmvt_item
            return           = it_errmsg_goodsmvt.
    Process of commit work
        IF it_goodsmvt_head[] IS NOT INITIAL.
          DESCRIBE TABLE it_goodsmvt_head LINES w_lines.
        ENDIF.
        IF it_goodsmvt_item[] IS NOT INITIAL.
          DESCRIBE TABLE it_goodsmvt_item LINES w_lines.
          CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
            EXPORTING
              wait = 'X'.
        IMPORTING
        RETURN        =
          CLEAR errflag.
          READ TABLE it_errmsg_goodsmvt INDEX 1.
          IF it_errmsg_goodsmvt-type EQ 'E'.
            WRITE:/'Error in function', it_errmsg_goodsmvt-message.
            errflag = 'X'.
          ELSE.
            WRITE:/ it_errmsg_goodsmvt-message.
          ENDIF.
          IF errflag IS INITIAL.
            COMMIT WORK AND WAIT.
            IF sy-subrc NE 0.
              WRITE:/ 'Error in updating'.
              EXIT.
            ELSE.
              WRITE:/ 'Material Document created successfully and the Document Number for the Material',
                      wa_goodsmvt_item-material,'is:', w_mat_doc, w_year.
            ENDIF.
          ENDIF.
        ENDIF.
      ENDLOOP.

    Hey,
    Just wanted to post that in my case this was the error of MVT_IND field in item table. When I made it from 'B' to blank then it worked.
    Mine is solved....
    Thanks

  • T code for Material,plant, stock and price data in std sap

    Dear All,
    In Std SAP is der any t-code to get Material,plant, stock and price data in 1 go..
    waiting for ur early reply
    Regards
    Nainesh

    Hi,
    Try T.Code: MC.9 and MC.5 etc. These reports will give you total value of the stock but not unit price.
    If you are looking at unit price please write a small query using SQVI or append the relevant info structure.
    Regards
    Srinivas.P

  • Status 51 material document data and po data do not match(vendor)

    i am using we19 to try an inbound idoc mbgmcr(receipt for po)
    i put in gm_code 01
    movement indicator B(goods receipt for po)
    vendor 3815
    PO 4500015241
    PO Order Item 00030
    Movement type 101
    qty in unit of entry  1
    iso code unit of measurement pc
    on the po screen i see the po item and qty to be delivered is 75
    when i run the inbound idoc i get
    status 51 material document data and po data do not match(vendor) but as i say on the po inquiry screen i see the po vendor item with 75 to be delivered
    what am i missing????????????????

    thank you
    i put in the leading zeros and got rid of that problem
    now i am getting status 51
    posting only possible in 2004/07 and 2004/06
    but in the posting date i use 07/02/2004  i have tried several dates in the period but get the same error
    any ideas?
    thanks you

  • Diff B/W master data and transaction data

    Hi all,
    What is the main Diff B/W master data and transaction data.  give me some example ?
    Thanks in Advance
    Krish...

    hi krish,
    MASTER Data is the data that exists in the organization like employee details, material master, customer master, vendor master etc. These are generally created once.
    Master data are distributed throughout the company, they are often not standardised and often redundant. As a result it is very costly to offer efficient customer service, keep track of supply chains and make strategic decisions. With SAP Master Data Management (SAP MDM) these important business data from across the company can be brought together, harmonised and made accessible to all staff and business partners. As a key component of SAP NetWeaver, SAP MDM ensures data integrity via all IT systems.
    Regardless of the industry, companies often work with different ERP and Legacy systems. The result: the business processes are based on information about customers, partners and products which is displayed in different ways in the systems. If the data are recorded manually, there are more inconsistencies: some data sets are entered several times, others cannot be retrieved by all divisions of the company.
    As corporate applications are becoming increasingly complex and produce ever greater amounts of data, the problem is intensified further. Nevertheless, your employees must work with the inconsistent data and make decisions on this basis. The lack of standardised master data easily leads to wrong decisions, which restrict efficiency and threaten customer satisfaction and profitability.
    In a word: in order to save costs and ensure your company’s success it is necessary to consolidate master data about customers, partners and products, make them available to all employees beyond system boundaries and use attributes valid company-wide for the purpose of description.
    TRASNACTION Data - These are the business documents that you create using the master data - Purchase orders, sales orders etc
    http://help.sap.com/saphelp_nw2004s/helpdata/en/9d/193e4045796913e10000000a1550b0/content.htm
    Regards,
    GNK.

  • Req. delivery date and Delivery date should be same in a sales order

    Hi experts,
    We need a customization for getting Requested delivery date, Material Availability date and Delivery date should be same.
    Example if I keep request delivery date as 12/12/2012, system should consider same dates for MAD and Delivery and confirm the requested quantity.
    How to achieve this customization..
    Thanks,
    Bala.

    system should consider same dates for MAD and Delivery and confirm the requested quantity
    What you are going to achieve by this?  Hope you know the concept of MAD and confirmed quantity fields.  Let us assume, if stock is not there for a material for which sale order is created, can you let me know, you want the system still to confirm the quantity? You can post the goods issue only if system confirms the quantity in schedule line which is possible, only if stock is made available.  If client asks something which is not possible in SAP, think in a logical way how SAP works and convince them accordingly. 
    G. Lakshmipathi

  • Add new payment term base on sales order contract date and shipment date

    Dear Sir/Madam,
    My company need to create new payment term base on sales order's contract date and shipment date.
    the first time is 30% made in T/T within 30days from contract signed date.
    the second time is 70% made in T/T before shipment.
    I don't know how to configuration this payment term base on that both date, who can tell me ,thanks very much!
    Best Regards
    Danny Zhang

    Hi,
    You have to define the PAYMENT TERMS as per days and Percentage.
    Define the Payment terms in the transaction OBB8 and assign this payment terms in the CUSTOMER MASTER and will be copied to the SALES ORDER from the customer master
    In the MATERIAL MASTER in the SALES ORG 1 view you have to check the field CAHS DISCOUNT In the Pricing procedure you can defin the CASH DISCOUNT condition type ( in standard there are two SKTV & SKTO)
    Now process the sales order and check
    regards,

  • CRM-ISU: Need to change the END date and Start Date for contract items

    Hi,
    There is an old contract item for which  I need to change the end date
    and there is a new contract item for which I need to change the start date.
    I need to change the contract item end date and start date using some function module in IS-U system (may be as RFC to CRM).Pleaselet me know if any body is ware of this functionality?
    I am aware of a FM EECRM_CONTRACT_DATE_CHANGE which may be used for changing End Date
    but how to change the start date of a new contract item?
    Please let me know if any body is aware of this?
    Thanks

    Hi,
    Hope you can solve it by this [Link1|Re: Function modules; [link2|CRM material;.
    Regards,
    Surjith

  • What is the Sequence of Master data and Transaction data R/3 to APO

    Hi guys,
    What is the Sequence of Master data and Transaction data R/3 to APO  through CIF?

    Hi,
    Master data,
    Material Indipendent data can be sent without any dependency.
    Material Dependent data sequence is as follow.
    Plant,
    MRP areas,
    Supply area,
    Material,
    MRP area material,
    planning material,
    ATP check,
    Purchase info recards,
    schedule agg,
    PPM or PDS (But before PPM or PDS  work center should send to apo) If PDS is sending then BOM should send before PDS.
    Transaction data.
    As per the business requirement what is planning in apo.
    Regards,
    Kishore Reddy.

  • How we will display the header data and item data seperately in lists

    how we will display the header data and item data seperately in lists

    REPORT z_alv_list_block.
    TYPE-POOLS: slis. " ALV Global types
    SELECTION-SCREEN :
    SKIP,
    BEGIN OF LINE,
    COMMENT 5(27) v_1 FOR FIELD p_max. "#EC NEEDED
    PARAMETERS p_max(2) TYPE n DEFAULT '02' OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    DATA:
    1st Table
    BEGIN OF gt_kna1 OCCURS 0, " Data displayed
    kunnr LIKE kna1-kunnr, " Customer number
    ernam LIKE kna1-ernam, " Name of Person who Created
    erdat LIKE kna1-erdat, " Creation date
    name1 LIKE kna1-name1, " Name 1
    END OF gt_kna1,
    2nd Table
    BEGIN OF gt_mara OCCURS 0,
    ernam LIKE mara-ernam, " Name of Person who Created
    matnr LIKE mara-matnr, " Material number
    ersda LIKE mara-e rsda, " Creation date
    brgew LIKE mara-brgew, " Gross weight
    END OF gt_mara,
    3rd Table
    BEGIN OF gt_vbak OCCURS 0,
    vkorg LIKE vbak-vkorg, " Sales organization
    kunnr LIKE vbak-kunnr, " Sold-to party
    vbeln LIKE vbak-vbeln, " Sales document
    netwr LIKE vbak-netwr, " Net Value of the Sales Order
    waerk LIKE vbak-waerk, " SD document currency
    END OF gt_vbak.
    INITIALIZATION.
    v_1 = 'Maximum of records to read'.
    START-OF-SELECTION.
    Read data
    SELECT * FROM kna1
    UP TO p_max ROWS
    INTO CORRESPONDING FIELDS OF TABLE gt_kna1.
    SELECT * FROM mara
    UP TO p_max ROWS
    INTO CORRESPONDING FIELDS OF TABLE gt_mara.
    SELECT * FROM vbak
    UP TO p_max ROWS
    INTO CORRESPONDING FIELDS OF TABLE gt_vbak.
    CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_INIT'
    EXPORTING
    i_callback_program = sy-cprog
    i_callback_user_command = 'USER_COMMAND'.
    PERFORM list_append TABLES gt_kna1
    USING '1'
    'GT_KNA1'.
    PERFORM list_append TABLES gt_mara
    USING '2'
    'GT_MARA'.
    PERFORM list_append TABLES gt_vbak
    USING '3'
    'GT_VBAK'.
    PERFORM f_list_display.
    FORM USER_COMMAND *
    FORM user_command USING i_ucomm LIKE sy-ucomm
    is_selfield TYPE slis_selfield. "#EC CALLED
    CASE i_ucomm.
    WHEN '&IC1'. " Pick
    CASE is_selfield-tabname.
    WHEN 'GT_MARA'.
    WHEN 'GT_KNA1'.
    WHEN 'GT_VBAK'.
    READ TABLE gt_vbak INDEX is_selfield-tabindex.
    IF sy-subrc EQ 0.
    Sales order number
    SET PARAMETER ID 'AUN' FIELD gt_vbak-vbeln.
    Display Sales Order
    CALL TRANSACTION 'VA03' AND SKIP FIRST SCREEN.
    ENDIF.
    ENDCASE.
    ENDCASE.
    ENDFORM. " USER_COMMAND
    ----< /div>
    Form list_append
    FORM list_append TABLES ut_table
    USING u_no TYPE char1
    u_tabname TYPE slis_tabname.
    Macro definition
    DEFINE m_fieldcat.
    ls_fieldcat-fieldname = &1.
    ls_fieldcat-ref_tabname = &2.
    append ls_fieldcat to lt_fieldcat.
    END-OF-DEFINITION.
    DEFINE m_sort.
    ls_sort-fieldname = &1.
    ls_sort-up = 'X'.
    append ls_sort to lt_sort.
    END-OF-DEFINITION.
    DATA :
    ls_fieldcat TYPE slis_fieldcat_alv,
    lt_fieldcat TYPE slis_t_fieldcat_alv, " Field catalog
    ls_sort TYPE slis_sortinfo_alv,
    lt_sort TYPE slis_t_sortinfo_alv. " Sort table
    DATA:
    lt_events TYPE slis_t_event,
    ls_event TYPE slis_alv_event,
    ls_layout TYPE slis_layout_alv.
    ls_layout-group_change_edit = 'X'.
    ls_layout-colwidth_optimize = 'X'.
    ls_layout-zebra = 'X'.
    ls_layout-detail_popup = 'X'.
    ls_layout-get_selinfos = 'X'.
    ls_layout-max_linesize = '200'.
    CASE u_no.
    WHEN '1'.
    Build field catalog and sort table
    m_fieldcat 'KUNNR' 'KNA1'.
    m_fieldcat 'ERNAM' 'KNA1'.
    m_fieldcat 'ERDAT' 'KNA1'.
    m_fieldcat 'NAME1' 'KNA1'.
    m_sort 'KUNNR'.
    WHEN '2'.
    m_fieldcat 'MATNR' 'MARA'.
    m_fieldcat 'ERNAM' 'MARA'.
    m_fieldcat 'ERSDA' 'MARA'.
    m_fieldcat 'BRGEW' 'MARA'.
    m_sort 'MATNR'.
    WHEN '3'.
    m_fieldcat 'VBELN' 'VBAK'.
    m_fieldcat 'VKORG' 'VBAK'.
    m_fieldcat 'KUNNR' 'VBAK'.
    m_fieldcat 'NETWR' 'VBAK'.
    m_fieldcat 'WAERK' 'VBAK'.
    m_sort 'VBELN'.
    ENDCASE.
    IF u_no CA '13'.
    MOVE 'TOP_OF_PAGE' TO ls_event-name.
    CONCATENATE 'TOP_OF_PAGE' u_no INTO ls_event-form.
    APPEND ls_event TO lt_events.
    ELSE.
    MOVE 'TOP_OF_LIST' TO ls_event-name.
    CONCATENATE 'TOP_OF_LIST' u_no INTO ls_event-form.
    APPEND ls_event TO lt_events.
    ENDIF.
    CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_APPEND'
    EXPORTING
    it_fieldcat = lt_fieldcat
    is_layout = ls_layout
    i_tabname = u_tabname
    it_events = lt_events
    it_sort = lt_sort
    i_text =
    TABLES
    t_outtab = ut_table
    EXCEPTIONS
    program_error = 1
    maximum_of_appends_reached = 2
    OTHERS = 3.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    ENDFORM. " LIST_APPEND
    Form f_list_display
    FORM f_list_display.
    DATA ls_print TYPE slis_print_alv.
    ls_print-no_print_selinfos = 'X'. " Display no selection infos
    ls_print-no_print_listinfos = 'X'. " Display no listinfos
    ls_print-reserve_lines = 2. " Lines reserved for end of page
    CALL FUNCTION 'REUSE_ALV_BLOCK_LIST_DISPLAY'
    EXPORTING
    i_interface_check = ' '
    is_print = ls_print
    EXCEPTIONS
    program_error = 1
    OTHERS = 2.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    ENDFORM. " F_LIST_DISPLAY
    FORM top_of_page1 *
    FORM top_of_page1. "#EC CALLED
    PERFORM top_of_page.
    ENDFORM.
    FORM top_of_page3 *
    FORM top_of_page3. "#EC CALLED
    PERFORM top_of_page.
    ENDFORM.
    FORM top_of_page *
    FORM top_of_page.
    ULINE.
    WRITE : sy-uname, sy-title(56) CENTERED, sy-datum.
    ULINE.
    ENDFORM.
    FORM top_of_list2 *
    FORM top_of_list2. "#EC CALLED
    WRITE 'TOP OF LIST2'.
    ENDFORM.
    END OF PROGRAM Z_ALV_LIST_BLOCK ***********************

  • Completion Data and Resume Data

    Again, it seems there is yet another Completion Data and Resume Data question... sorry.
    My issue is that completion data isn't always being sent from my SCORM material to my LMS. I know there is a setting to set the completion data at X percent, but even then I would like to have something a bit more trusting on it. Is there a way (and I'm no developer/program/IT guy so please help in detail) to make so that on X slide that completion data is forced to be sent?
    This also plays into my next question: is there a way to force resume data on every page, every load? The bookmark feature is nice thank you Adobe staff for adding that, but its reliability for what my company is using is questionable at best. If there is no progress made within the lesson the resume data after having used it once isn't sent again - I need this to be sent on every slide upon entering or even better at a preset time on the slide, and always be sent regardless of number of accesses. Is this possible? It would solve a whole host of problems one being that we need to have the test scores entered into our LMS after a successful completion, and then have the slide fade out so the user cannot re-access, redo, copy, etc the quizzes.
    Thank you for the help,
    -Joseph

    I can't really help you with most of your questions, but I can confirm that a slide needs to be viewed 100% from start to end of the timeline before Captivate treats it as "read/viewed". It's the same problem when you are using the TOC - it will not get the check mark until the slide has played from A-Z, which is really annoying.
    /Michael
    Visit my Captivate blog with tips & tricks, tutorials and Widgets.

Maybe you are looking for